id
int64
name
string
name_abbreviation
string
decision_date
string
docket_number
string
court
string
casebody
string
judge1
string
judge2
string
judge3
string
exactly_three_caps
int64
extra_judges
string
judge_designations
string
opinions_count
int64
majority_count
int64
dissent_count
int64
concurrence_count
int64
other_count
int64
primary_citation
string
reporter
string
volume
null
resource_url
string
precedential_status
string
010combined_count
int64
020lead_count
int64
030concurrence_count
int64
035concurrenceinpart_count
int64
040dissent_count
int64
year
int64
month
int64
messages
list
4,579,021
Larry BLUE, Petitioner, Appellant, v. Sean MEDEIROS, Respondent, Appellee.
Blue v. Medeiros
2019-01-04
18-1066P
U.S. Court of Appeals for the First Circuit
{"judges": "Thompson, Selya, Lipez", "parties": "", "opinions": [{"author": "THOMPSON, Circuit Judge.", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1066\n\n LARRY BLUE,\n\n Petitioner, Appellant,\n\n v.\n\n SEAN MEDEIROS,\n\n Respondent, Appellee.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Allison D. Burroughs, U.S. District Judge]\n\n\n Before\n\n Thompson, Selya, and Lipez,\n Circuit Judges.\n\n\n Ashley P. Allen, with whom Patricia A. DeJuneas and Sibbison\n& DeJuneas were on brief, for appellant.\n Eva M. Badway, Assistant Attorney General, with whom Maura\nHealey, Attorney General, was on brief, for appellee.\n\n\n January 4, 2019\n\f THOMPSON, Circuit Judge.\n\n The Antiterrorism and Effective Death Penalty Act of\n\n1996 (\"AEDPA\"), 28 U.S.C. § 2244(d)(1), establishes a one-year\n\nstatute of limitations for a state prisoner to file a federal\n\nhabeas corpus petition under 28 U.S.C. § 2254. The one-year period\n\ngenerally starts when a prisoner's conviction becomes final, but\n\nmay be tolled, pursuant to the statute, during the time in \"which\n\na properly filed application for State post-conviction or other\n\ncollateral review with respect to the pertinent judgment or claim\n\nis pending.\" Id. § 2244(d)(2).\n\n Petitioner Larry Blue, a Massachusetts prison inmate,\n\nfiled a petition for habeas corpus relief which the district court\n\ndismissed as time-barred under AEDPA's statute of limitations.\n\nPetitioner now seeks reconsideration of that ruling based on two\n\ntolling theories. First, Petitioner argues that the statute of\n\nlimitations should be statutorily tolled during the month-plus-\n\nlong pendency of his motion to stay the execution of his sentence,\n\nbecause that motion, he urges, constitutes an application for\n\ncollateral review under § 2244(d)(2). Second, Petitioner argues,\n\nessentially, that unique circumstances surrounding his conviction\n\njustify equitable tolling of the time between the finality of his\n\nCommonwealth convictions and the filing of his habeas petition.\n\nFor reasons explained below, we reject these arguments and affirm\n\nthe dismissal of Petitioner's habeas corpus petition.\n - 2 -\n\f I. Background\n\n Because dates are crucial to our evaluation of\n\nPetitioner's claims, we ask the reader's patience as we detail the\n\ntravel of the proceedings below. On August 18, 2010, following a\n\ntrial by jury, Petitioner was convicted of multiple Massachusetts\n\nstate law crimes, including drug trafficking, drug possession, and\n\nunlicensed firearm and ammunition possession. Thereafter, he\n\npleaded guilty to additional related charges and was handed a\n\ncumulative sentence of up to ten years and a day to serve.\n\n Petitioner pursued various avenues of post-conviction\n\nrelief in the Commonwealth courts.1 On June 14, 2012, Petitioner\n\nfiled a direct appeal of his convictions, based in part on\n\narguments previously raised and rejected by the trial court that\n\nthere were defects in the search warrants that led to his arrest.\n\nAdditionally, Petitioner premiered a new argument challenging the\n\nconstitutionality of Massachusetts's gun licensing regime.\n\n While Petitioner's appeal was pending, revelations of\n\nwidespread misconduct at the Commonwealth's crime lab, the William\n\nA. Hinton State Laboratory Institute, came to light with state-\n\nemployed chemist Annie Dookhan in the maelstrom of the scandal.\n\nIn response to these disclosures, in August 2012, Massachusetts's\n\n\n 1\n First, he filed a motion for a new trial, based on his\nassertion that the court reporter was unable to produce a full\ntranscript of his trial. This motion was denied the following day\nwhen the parties collaborated to reconstruct the missing record.\n - 3 -\n\fgovernor shuttered the lab and ordered an independent\n\ninvestigation.2 Dookhan, after being hit with multiple indictments\n\nfor falsifying drug test results, lying about her credentials, and\n\nperjuring herself in court (including during Petitioner's trial),\n\neventually pled guilty to twenty-seven counts on November 22, 2013.\n\n Meanwhile, the Appeals Court of Massachusetts denied\n\nPetitioner's direct appeal on September 27, 2013. Commonwealth v.\n\nBlue, 994 N.E.2d 817 (Table), 2013 WL 5377118 (Mass. App. Ct.\n\n2013). First, it cited its agreement with the trial court's\n\nreasoning for the denial of Petitioner's search warrant\n\nsuppression motions. And next, it pointed out the futility of\n\nPetitioner's constitutional challenge, noting the state's gun\n\nlicensing regime had already been given the green light by the\n\nMassachusetts Supreme Judicial Court (\"SJC\"). Id. Hoping to\n\nchange minds, Petitioner filed a motion for rehearing, but the\n\nappeals court promptly denied it.\n\n Soldiering on, Petitioner sought further appellate\n\nreview with the SJC in October 2013. However, that application\n\nwas summarily denied without discussion on November 21, 2013.\n\nCommonwealth v. Blue, 998 N.E.2d 342 (Mass. 2013) (Table). Ninety\n\n\n\n 2 Not long after the Dookhan misconduct was made public, an\nentry in the trial court docket reflects that Petitioner filed a\nmotion to stay the execution of his sentence on March 12, 2013.\nThe docket notation reads \"(Drug Lab)\"; the motion was withdrawn\nin June 2013.\n - 4 -\n\fdays later, on February 19, 2014, Petitioner's convictions became\n\nfinal; that is the moment the AEDPA statute of limitations clock\n\nbegan to tick.3\n\n In the wake of the Dookhan fiasco, Petitioner filed with\n\nthe trial court a second motion to stay the execution of his\n\nsentence, pursuant to Massachusetts Rule of Criminal Procedure 31\n\n(\"Rule 31\").4 In that February 21, 2014 filing he asserted his\n\nbelief that Dookhan's misconduct would likely result in the grant\n\nof a new trial on all charges given (1) the unreliability of the\n\nlaboratory testing supporting his drug convictions and (2) the\n\noverall taint Dookhan's perjured testimony cast on his\n\nconvictions, due to the prosecutor weaving together the drug\n\ndealing and the gun possession throughout the trial. In a\n\nmemorandum in support of his stay motion, Petitioner announced his\n\nintention to file a renewed motion for a new trial \"shortly,\" based\n\non Dookhan's perjury and other grounds.\n\n\n\n\n 3 Cordle v. Guarino, 428 F.3d 46, 48 (1st Cir. 2005) (\"The\nSJC affirmed [the] convictions on March 11, 1992; her convictions\nbecame final ninety days thereafter.\").\n 4 The Commonwealth's investigation into the Hinton Lab came\nto an end, concluding that, while Dookhan was \"the sole bad actor\"\nat the lab, poor and inadequate training, protocols, and management\nhad allowed her conduct to go undetected for years. It was\nconservatively estimated that Dookhan worked on close to 34,000\ncases during her years at the lab. Commonwealth v. Charles, 992\nN.E.2d 999, 1003 (Mass. 2013).\n - 5 -\n\f Back at the SJC, while Petitioner's motion to stay was\n\npending, the Commonwealth high court weighed in on the Dookhan\n\ndebacle: in cases where Dookhan had served as a primary or\n\nsecondary chemist for drug analysis, all defendants were entitled\n\nto a conclusive presumption that her conduct was egregious and\n\nattributable to the Commonwealth. Commonwealth v. Scott, 5 N.E.3d\n\n530, 535 (Mass. 2014). That presumption notwithstanding, soon\n\nafter the Scott opinion issued, Petitioner's motion for a stay of\n\nthe execution of his sentence was denied on March 27, 2014. The\n\ntrial court found that Petitioner's firearms convictions were\n\nunaffected by Dookhan's misconduct and as such, he was unlikely to\n\nreceive a new trial.\n\n Undeterred, on May 5, 2014, Petitioner filed a second\n\nmotion for a new trial based on two theories. First, he framed\n\nthe revelation of Dookhan's perjury as \"newly-discovered\n\nevidence,\" casting doubt on the fairness of his conviction. (For\n\nall intents and purposes, this taint argument is the same one that\n\nhad just been rejected by the court in response to his stay\n\nmotion.) His second argument, ineffective assistance of counsel,\n\nwas essentially a repackaging of the earlier defective search\n\nwarrant claims.5\n\n\n\n 5Petitioner alleged that the warrants failed to establish\ntimely probable cause because of their technical shortcomings, and\nthat his attorney was ineffective for failing to properly argue\n - 6 -\n\f On January 20, 2015, acting on Petitioner's new trial\n\nmotion, the trial court granted it as to the drug charges, and\n\ndenied it as to the gun charges. Commenting on the drug\n\nconvictions, the court conceded that, even though extensive\n\nevidence supported Petitioner's drug charges aside from Dookhan's\n\nperjured testimony, her testimony had, nonetheless, tainted the\n\ndrug convictions. As for the gun charges, the court found no\n\nconnection between Dookhan's testimony and those convictions.\n\nFinally, the trial court dismissed the ineffective assistance\n\nclaim, describing it as not distinct from Petitioner's prior search\n\nwarrant claims, and writing:\n\n [T]he Appeals Court implicitly rejected the defendant's\n instant claim . . . and made rejection explicit when it\n refused the defendant's petition for rehearing. The\n issue is settled and need not be considered on its merits\n here.\n\nTwo days later Petitioner appealed the partial denial to the\n\nappellate court, and sought further review after this first appeal\n\nwas denied. Commonwealth v. Blue, 46 N.E.3d 114 (Table), 2016 WL\n\n757758 (Mass. App. Ct. 2016). The Commonwealth nolle prossed the\n\ndrug charges at the end of January 2015.6 And, on April 27, 2016,\n\n\n\nthe defects -- an interpretive gloss that he had not explicitly\nraised before.\n\n 6 \"Nolle prossed\" comes from the Latin phrase \"nolle\nprosequi,\" translated as \"we shall no longer prosecute.\" In this\ncontext, it means that the Commonwealth dropped all the drug\ncharges against Petitioner.\n\n - 7 -\n\fthe SJC entered a final denial of Petitioner's application for\n\nfurther appellate review of his motion for a new trial.7\n\n Almost eleven months8 later, on March 20, 2017,\n\nPetitioner filed his federal petition for a writ of habeas corpus,\n\npremised solely on his allegations of ineffective assistance of\n\ncounsel.9 On the motion of Respondent Norfolk prison\n\nsuperintendent Sean Medeiros, the district court dismissed the\n\npetition as time-barred under AEDPA. Blue v. Medeiros, No. 17-\n\ncv-10464-ADB, 2017 WL 5297910, at *1 (D. Mass. Nov. 13, 2017). In\n\nso doing the district court held that Petitioner's motion to stay\n\nthe execution of his sentence did not toll AEDPA's one-year time\n\nlimit, under 28 U.S.C. § 2244(d)(2), because it was not an\n\n\"application for . . . collateral review.\" The court held further\n\nthat Petitioner was not entitled to equitable tolling because the\n\nissues created by the Hinton Lab misconduct did not impose a bar\n\n\n\n 7 There is no dispute that the AEDPA statute of limitations\nwas tolled for the almost two-year period that his motion for a\nnew trial was pending, from May 5, 2014, through April 27, 2016.\n\n 8 327 days, to be precise.\n 9 Again, Petitioner alleged that the search warrants\nunderlying his arrest and conviction failed to establish probable\ncause, and that trial counsel failed to argue this effectively.\nThese arguments are not before us in this appeal. Peralta v.\nUnited States, 597 F.3d 74, 83 (1st Cir. 2010) (general rule is\nthat \"a court of appeals should not consider the merits of an issue\nadvanced by a habeas petitioner unless a COA [certificate of\nappealability] first has been obtained with respect to that issue\"\n(quoting Bui v. DiPaolo, 170 F.3d 232, 237 (1st Cir. 1999))).\n - 8 -\n\fto Petitioner filing a motion for a new trial concurrently with\n\nhis motion for stay of execution (recall Petitioner's stay motion\n\nwas filed on February 21, 2014, while his new trial motion was not\n\nfiled until May 5, 2014); and because, even after his motion for\n\na new trial was denied and the Commonwealth had abandoned the drug\n\ncharges, Petitioner allowed eleven months to pass by before filing\n\nthe petition for the writ of habeas corpus.\n\n In his present appeal, Petitioner advances two\n\narguments relative to the timeliness of his habeas petition; we\n\ntake each in turn. Because the district court denied Petitioner\n\nrelief \"on a procedural ground without taking evidence,\" we apply\n\nde novo review. Holmes v. Spencer (Holmes I), 685 F.3d 51, 58\n\n(1st Cir. 2012) (quoting Wood v. Spencer, 487 F.3d 1, 3 (1st Cir.\n\n2007)).\n\n II. Statutory Tolling\n\n First, Petitioner argues that his motion to stay the\n\nexecution of his sentence tolled AEDPA's statute of limitations,\n\nbecause it is a properly filed application for \"collateral review\"\n\nas contemplated by 28 U.S.C. § 2244(d)(2). In support of his\n\nassertion that \"the plain meaning\" of AEDPA's tolling provision\n\n\"includes post-conviction motions [like a motion to stay] heard by\n\nthe trial judge,\" Petitioner cites Wall v. Kholi (Kholi III), 562\n\nU.S. 545 (2011). To better understand Petitioner's argument, a\n\nbrief discussion of Kholi is in order.\n - 9 -\n\f Khalil Kholi was convicted by the Rhode Island Superior\n\nCourt of repeated acts of sexual assault on his two young step-\n\ndaughters and received two consecutive life sentences. He appealed\n\nthe convictions and simultaneously filed a motion to reduce his\n\nsentence; both were unsuccessful. State v. Kholi, 706 A.2d 1326\n\n(R.I. 1998); State v. Kholi, 672 A.2d 429 (R.I. 1996).\n\n Kholi then filed a petition for a writ of habeas corpus\n\nin the federal district court, which denied relief after finding\n\nthe petition time-barred by AEDPA. Kholi v. Wall (Kholi I), No.\n\n07-346S, 2008 WL 60194 (D.R.I. Jan. 3, 2008). In so concluding,\n\nthe court held that Kholi's motion to reduce his sentence, brought\n\npursuant to Rule 35 of Rhode Island's criminal procedure rules,10\n\ndid not constitute an application for \"collateral review\" under\n\nAEDPA, and thus did not toll the limitations period. Instead, the\n\ncourt reasoned that \"a motion for correction or reduction of\n\nsentence contemplates the defendant returning to the same court,\n\nand pleading for mercy before the same judge that imposed the\n\noriginal sentence and thus, is not 'collateral' within the meaning\n\nof AEDPA.\" Id. at *3 (citing Walkowiak v. Haines, 272 F.3d 234,\n\n237-38 (4th Cir. 2001)).\n\n Kholi appealed and we reversed, holding that \"a state\n\npost-conviction motion for a sentence reduction, in the nature of\n\n\n\n 10 R.I. Super. Ct. R. Crim. P. 35 (a).\n - 10 -\n\fa plea for discretionary leniency, comes within the [AEDPA]\n\nstatutory sweep.\" Kholi v. Wall (Kholi II), 582 F.3d 147, 156\n\n(1st Cir. 2009). In reaching this conclusion, we stressed the\n\nimportance of encouraging state prisoners to exhaust state court\n\nremedies before seeking federal habeas review. Id. at 155.\n\n The state of Rhode Island sought further review and the\n\nSupreme Court granted certiorari. Kholi III, 562 U.S. at 551-53.\n\nIn affirming our ruling the Court carefully parsed the AEDPA\n\ntolling language. Defining the phrase \"collateral review\" in the\n\nAEDPA context, the Court stated, \"[v]iewed as a whole, then,\n\n'collateral review' of a judgment or claim means a judicial\n\nreexamination of a judgment or claim in a proceeding outside of\n\nthe direct review process.\" Id. at 553. In considering whether a\n\nRule 35 motion would trigger collateral review, the Supreme Court\n\nanalyzed the meanings of the words \"collateral\" and \"review.\" Id.\n\nat 555-56.\n\n Reasoning that a motion to reduce the sentence was\n\ntraditionally viewed as a collateral challenge, and was in no\n\ninstance a part of the direct review process, the Court quickly\n\ndetermined that the motion was collateral. Id. at 555. The Court\n\nthen moved on to examine its understanding of the word \"review.\"\n\nBased on the operation of the state's criminal rule, the motion\n\nwould require a \"judicial reexamination of the sentence to\n\ndetermine whether a more lenient sentence is proper\" and it\n - 11 -\n\ftherefore resulted in a review. Id. Consequently, the Court\n\ndetermined that Kholi's motion to reduce his sentence constituted\n\nan application for collateral review which triggered AEDPA's\n\ntolling provision. Id. at 556; see also Holmes I, 685 F.3d at 60;\n\nKholi II, 582 F.3d at 153 (\"Taking into account this quotidian\n\nunderstanding, it seems self-evident that a motion for a sentence\n\nreduction in the nature of a plea for discretionary leniency is a\n\nmotion that seeks post-conviction 'review' of a sentence and, thus,\n\nis a motion that falls squarely within the plain meaning of section\n\n2244(d)(2).\").\n\n As our Petitioner would have it, his Massachusetts Rule\n\n31 motion to stay execution of sentence is no different from the\n\nRule 35 motion discussed in Kholi III, and as such the district\n\ncourt erred when it deemed AEDPA's tolling provision not triggered.\n\nHowever, while we agree with Petitioner that his motion is,\n\nassuredly, a collateral one, we find it does not have the power to\n\ngenerate a review. As the government correctly suggests, we must\n\nturn to Massachusetts law to explain why. Carey v. Saffold, 536\n\nU.S. 214, 223 (2002) (\"[F]or purposes of applying a federal statute\n\nthat interacts with state procedural rules, we look to how a state\n\nprocedure functions . . . .\"); Lewis v. Jeffers, 497 U.S. 764,\n\n780-81 (1990) (urging deference to a state court's \"application of\n\nits own law\" in habeas context).\n\n\n - 12 -\n\f Rule 31 allows a trial judge or a single justice of the\n\nCommonwealth's appellate court to make a discretionary ruling\n\nstaying the imposition of a sentence during the pendency of an\n\nappeal.11 While the ruling on the stay will not be reversed absent\n\nan abuse of discretion, the judge generally requires a\n\ndemonstration that the defendant has a reasonable likelihood of\n\nsuccess on appeal. See Commonwealth v. Levin, 388 N.E.2d 1207,\n\n1208 (Mass. App. Ct. 1979). That means evaluating whether or not\n\nthe appeal is frivolous, or whether it is \"an appeal which presents\n\nan issue which is worthy of presentation to an appellate court,\n\none which offers some reasonable possibility of a successful\n\ndecision in the appeal.\" Id. at 1209. More recently, the SJC has\n\ndescribed this analysis as a \"pure question of law or legal\n\njudgment,\" which in no way prejudges \"the merits of the defendant's\n\ndirect appeal.\" Commonwealth v. Mattier, 49 N.E.3d 227, 228-29\n\n(Mass. 2016) (quoting Commonwealth v. Allen, 392 N.E.2d 1027, 1033\n\n(Mass. 1979)).12\n\n We have noted in the past that not all filings by a\n\ncriminal defendant which seek to advance a challenge to a judgment\n\n\n 11 The order is temporary and automatically expires upon\naffirmation of the conviction, unless it is extended by the\nappellate court. It may also be revoked. Rule 31(a), (b).\n 12 In addition to the merits evaluation, the judge\nentertaining the motion must also consider issues relating to\nsecurity, such as the defendant's risk of flight or likelihood of\ncommitting new criminal acts. Levin, 388 N.E.2d at 1210.\n - 13 -\n\fof conviction constitute a collateral review for AEDPA purposes.\n\nRodriguez v. Spencer, 412 F.3d 29, 37 (1st Cir. 2005) (petition\n\nfor extraordinary relief not application for collateral review);\n\nVoravongsa v. Wall, 349 F.3d 1, 7 (1st Cir. 2003) (pro se motion\n\nfor appointment of state post-conviction counsel not collateral\n\nreview); see also Bridges v. Johnson, 284 F.3d 1201, 1203 (11th\n\nCir. 2002) (application before a state sentence review panel not\n\ncollateral review); Adeline v. Stinson, 206 F.3d 249, 252 (2d Cir.\n\n2000) (motion to revive an appeal not collateral review).\n\nSimilarly here, from our perspective, the Rule 31 screening process\n\nlacks the indicia of a \"review\" for this reason: Even though a\n\njudge must take a peek at the underlying claim to see if the merits\n\nare hopeless, she has no authority to either alter the judgment or\n\nchange the sentence. See Kholi II, 582 F.3d at 151 (in the typical\n\ncase, application for post-conviction relief that \"does not seek\n\nto alter (or even to reexamine) the judgment\" does not toll\n\nstatute).\n\n For these reasons, after a fresh review of Petitioner's\n\nclaims, we hold that a motion to stay the execution of a sentence,\n\nunder Rule 31, does not constitute a motion for collateral review,\n\nand its filing does not trigger AEDPA's tolling provisions.13\n\n\n 13\n Even if the statute of limitations were tolled during the\npendency of his motion to stay the execution of his sentence, he\nstill goes over the statutory time limit. He has a short two\ndays between the date his convictions became final and the date he\n - 14 -\n\f III. Equitable Tolling\n\n Petitioner's second argument -- that equitable tolling\n\napplies to his habeas filing -- is grounded in principles of equity\n\nand fairness, and is primarily focused on the disruption in the\n\nCommonwealth's administration of justice caused by Dookhan's\n\ndeceitful misconduct.14 In claiming that his petition for habeas\n\ncorpus relief should be permitted to go forward, Petitioner offers\n\nthe following argument: \"The lower court presumed that equitable\n\ntolling can only apply to the time immediately preceding the filing\n\nof the habeas corpus petition, rather than to any period of time\n\nafter a conviction becomes final. . . .As far as petitioner is\n\naware, there is no requirement that the petitioner show a permanent\n\nimpediment from filing or to justify the year in which petitioner\n\nhas to file his application for a writ of habeas corpus.\"\n\nPetitioner's argument, then, seems to have two parts which go like\n\nthis. First, he says that the 75 days between February 19, 2014,\n\nthe date his convictions became final, up to May 5, 2014, when he\n\nfiled his motion for a new trial, must be equitably tolled because\n\n\n\n\nfiled his motion for a stay. Then, 39 days elapse between the\ndenial of his motion to stay and the filing of his motion for a\nnew trial. If you add those 41 days to the 327 days he waited\nbetween the final exhaustion of all state court review and the\ndate he filed the present writ, you get 368 days -- three days\nover the statutory time limit.\n 14\n As mentioned earlier, based on Scott, 5 N.E.3d at 535, this\nconduct may be attributed to the Commonwealth.\n - 15 -\n\fduring this time he was diligently pursuing state-court relief,\n\nand yet was thwarted by the difficulties posed by the Hinton Lab\n\ninvestigation. As he tells it: \"The magnitude of the problem\n\neffectively reopened and called into question thousands of\n\nconvictions. What followed were delays in post-conviction\n\nhearings, discovery issues, and an on-going, ultimately fifteen-\n\nmonth, investigation by the Office of the Inspector General into\n\nthe Hinton State Drug Laboratory that concluded on March 4, 2014.\"\n\n Second, as for the time from April 27, 2016 to March 20,\n\n2017, when Petitioner filed his habeas petition, he seems to be\n\ncontending that this period should be excluded altogether from our\n\nequitable tolling analysis. We consider Petitioner's contentions,\n\nkeeping in mind the guiding principles discussed next.\n\n To establish a basis for equitable tolling, a habeas\n\npetitioner must demonstrate that he or she has diligently pursued\n\nher rights, but some extraordinary circumstance, or obstacle,\n\nprevented timely filing. Holland v. Florida, 560 U.S. 631, 649\n\n(2010); Holmes I, 685 F.3d at 62. The diligence prong covers those\n\naffairs within the petitioner's control, while the extraordinary-\n\ncircumstances prong covers matters outside his control. Menominee\n\nIndian Tribe of Wis. v. United States, 136 S. Ct. 750, 755-57\n\n(2016). It is up to the petitioner to establish \"a causal\n\nrelationship between the extraordinary circumstances on which the\n\nclaim for equitable tolling rests and the lateness of his filing.\"\n - 16 -\n\fValverde v. Stinson, 224 F.3d 129, 134 (2d Cir. 2000).\n\nAdditionally, \"we apply equitable tolling on a case-by-case basis,\n\navoiding mechanical rules and favoring flexibility.\" Ortega\n\nCandelaria v. Orthobiologics LLC, 661 F.3d 675, 680 (1st Cir.\n\n2011). That said, equitable tolling is applied infrequently,\n\nHolmes I, 685 F.3d at 62, and abuse-of-discretion is the lens\n\nthrough which we review an equitable tolling decision, Holmes v.\n\nSpencer (Holmes II), 822 F.3d 609, 612 (1st Cir. 2016). This\n\nstandard of review is nuanced; \"within it, abstract questions of\n\nlaw are reviewed de novo, findings of raw fact are reviewed for\n\nclear error, and judgment calls receive a classically deferential\n\nreception.\" Holmes I, 685 F.3d at 62 (quoting Riva v. Ficco, 615\n\nF.3d 35, 40 (1st Cir. 2010)).\n\n In support of his two-part equitable tolling theory (to\n\nremind the reader: the period between the date of his final\n\nconviction and the date he filed his motion for a new trial should\n\nbe equitably tolled in full, and the eleven-month post new trial\n\ndenial period should be ignored altogether), Petitioner cites to\n\nHolmes I. Accordingly, closer scrutiny of that case is warranted.\n\n In Holmes I, habeas petitioner Holmes sought both\n\nstatutory and equitable tolling: statutory for a period during\n\n\n\n\n - 17 -\n\fwhich his motion to revise or revoke his sentence was pending;15\n\nequitable for the same period based on the obstacles imposed by\n\nhis incarceration, and by the incorrect legal filing he made in\n\nreliance on misleading advice from his lawyer during plea\n\nbargaining. Holmes I, 685 F.3d at 55-56. On appeal this court\n\naffirmed the district court in part, agreeing that, while Holmes's\n\nmotion to revise or revoke his sentence was in fact an application\n\nfor collateral review under AEDPA (based on the newly-minted Kholi\n\nIII decision), it still was not \"properly\" filed under\n\nMassachusetts law (his filing did not specify the grounds upon\n\nwhich the motion was based as Rule 29 requires)16 and so did not\n\ntrigger the statutory tolling mechanism within the meaning of 28\n\nU.S.C. § 2244(d)(2). Id. at 60-61. However, we remanded the\n\nmatter to the district court to review its equitable tolling\n\nruling, pointing out that Holmes's belief that he had in fact\n\nproperly filed his motion to revise or revoke his sentence might,\n\n\n\n\n 15\n Holmes's motion was brought pursuant to Massachusetts Rule\nof Criminal Procedure 29, a rule indistinguishable from Rhode\nIsland's Rule 35 discussed in Kholi III.\n 16\n An application is \"properly filed\" for AEDPA purposes \"when\nits delivery and acceptance are in compliance with the applicable\nlaws and rules governing filings.\" Holmes I, 685 F.3d at 67\n(quoting Artuz v. Bennett, 531 U.S. 4, 8 (2000)).\n\n - 18 -\n\fafter Kholi III, provide an equitable basis for excluding the time\n\nthe motion was pending.17 Id. at 63-66.\n\n Petitioner is correct that our Holmes I decision spends\n\nmuch time and analysis scrutinizing the almost nine-year period\n\nbetween Holmes's guilty plea and the final denial of\n\nreconsideration from the Commonwealth court, during which time he\n\nargued that he faced extraordinary obstacles (a lot was going on\n\nduring those nine years). Then, extrapolating from the focus of\n\nthat discussion, Petitioner posits that the additional seven-month\n\nperiod between the final ruling by the Commonwealth court and the\n\ndate Holmes filed his petition for habeas corpus must not have\n\nbeen relevant to our equitable tolling analysis. \"There was no\n\nweight given to, or even mention of, the seven months it took\n\n[Holmes] to file his habeas petition after his conviction became\n\nfinal,\" Petitioner writes in his brief. Therefore, according to\n\nPetitioner, it logically follows that in his case, the eleven-\n\nmonth period between the conclusion of the Commonwealth court\n\nreview and the filing of his habeas petition is not relevant to\n\n\n\n\n 17This court rejected Holmes's arguments that allegedly bad\nadvice from his lawyer, coupled with the disadvantages of\nincarceration, justified equitable tolling, suggesting sua sponte\na third ground for equitable tolling instead. As it turned out,\non remand, the district court held that there was no basis for\nequitable tolling and again denied Holmes's petition as untimely.\nThe ruling was affirmed by this court in Holmes II. 822 F.3d at\n612.\n - 19 -\n\four assessment of extraordinary circumstances or diligence when it\n\ncomes to an equitable tolling analysis.\n\n Unfortunately, Petitioner misconstrues our Holmes I\n\nrationale. A careful read makes it clear that we considered the\n\nentire period leading up to the filing of the habeas petition when\n\nwe wrote, \"[t]he timeliness of Holmes's federal habeas petition,\n\nthen, hinges on whether there are any grounds for excluding at\n\nleast twenty-two of the remaining thirty-four unaccounted months\n\nbetween May 1, 1998 [the date of Holmes's guilty plea] and April\n\n9, 2008 [the filing date of the habeas petition].\" Id. at 57. Of\n\ncourse, given the procedural intricacies that animated Holmes's\n\njourney through the Commonwealth criminal justice system, we had\n\nreason to more closely examine the months during which Holmes\n\nclaimed he was prevented by circumstances outside of his control\n\nfrom filing his habeas petition; but unquestionably, as clearly\n\nnoted in our decision, the full period was taken into account in\n\ncalculating the operation of the AEDPA time limit. Id. at 57-61.\n\nThus, with Holmes I's timing calculus properly understood, we\n\nreturn to Petitioner's argument.\n\n To briefly recap the timeline: approximately three\n\nyears and a month went by between the date Petitioner's convictions\n\nbecame final and the date he filed his habeas petition.18 After\n\n\n 18In its argument on equitable tolling, the government comes\nup with a different set of calculations. The government starts\n - 20 -\n\fPetitioner's motion for a new trial was finally denied, eleven\n\nmonths went by before the present motion got filed. Even if we\n\nwere to accept Petitioner's argument that the entire Dookhan\n\ndebacle posed an insurmountable obstacle to Petitioner's filing a\n\ntimely habeas proceeding prior to the SJC's final resolution of\n\nhis motion for a new trial on April 27, 2016, he nevertheless can\n\npoint to no fact which demonstrates any obstacle, extraordinary or\n\notherwise, that hindered his filing of a habeas petition during\n\nthe final eleven months. Nor can he point to any behavior on his\n\npart that would demonstrate reasonable diligence in pursuing his\n\nrights during the final eleven months. When Petitioner's motion\n\nfor a new trial was denied, it should have been clear to him that\n\nall state-court avenues for relief had been exhausted. That is\n\nthe moment he needed to move swiftly to preserve his federal rights\n\nas the Hinton Lab misconduct could no longer be described as\n\n\n\n\nthe clock on November 21, 2013, the date that Petitioner's\napplication for further state-level appellate review was denied.\nThe government concludes then that 165 days elapsed before\nPetitioner filed his motion for a new trial. This court has\ngenerally determined that the judgment becomes final after an\nadditional ninety days have elapsed to allow for the filing of a\npetition for certiorari, see Neverson v. Farquharson, 366 F.3d 32,\n36 (1st Cir. 2004), starting the AEDPA clock then after that\nninety-day period. With its argument, the government seeks to\nunderscore that the Petitioner also had this ninety-day period\navailable during which he might have filed his motion for a new\ntrial, thereby undermining Petitioner's diligence argument. The\ngovernment does not press an argument about this clock-starting\ndate, and, in any case, this discrepancy is not determinative of\nthe outcome.\n - 21 -\n\fimpeding his ability to seek post-conviction review. See Neverson\n\nv. Farquharson, 366 F.3d 32, 44 (1st Cir. 2004). As the government\n\ncorrectly points out, the Commonwealth nolle prossed Petitioner's\n\ndrug charges in January 2015. As these were the only charges\n\ndirectly affected by Dookhan's malfeasance, the putative obstacle\n\nposed by the Hinton Lab issues dematerialized over a year before\n\nhis motion for a new trial was denied. Petitioner's argument that\n\nthe gun-related convictions were tainted by the prosecutor's\n\nclosing remarks at trial (connecting the drugs with the gun) had\n\nbeen repeatedly rejected by the Commonwealth courts by April 2016\n\n-- twice by the trial court, once by the appellate court, and\n\nfinally by the SJC. As a result, Petitioner's hope, or misguided\n\nbelief, that this theory might provide him a lifeline could no\n\nlonger be reasonably understood as an obstacle preventing him from\n\npursuing his federal remedy.\n\n IV. Conclusion\n\n Because we find that Petitioner's motion to stay the\n\nexecution of his sentence was not a request for collateral review\n\nand so did not toll the one-year statute of limitations in the\n\nAntiterrorism and Effective Death Penalty Act, and because we find\n\nno reason to disrupt the district court's discretionary ruling on\n\nequitable tolling, we affirm the dismissal of Petitioner's\n\npetition for a writ of habeas corpus as time-barred.\n\n\n - 22 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356274/", "author_raw": "THOMPSON, Circuit Judge."}]}
THOMPSON
SELYA
LIPEZ
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579021/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Larry BLUE, Petitioner, Appellant, v. Sean MEDEIROS, Respondent, Appellee.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-04\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1066\n\n LARRY BLUE,\n\n Petitioner, Appellant,\n\n v.\n\n SEAN MEDEIROS,\n\n Respondent, Appellee.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Allison D. Burroughs, U.S. District Judge]\n\n\n Before\n\n Thompson, Selya, and Lipez,\n Circuit Judges.\n\n\n Ashley P. Allen, with whom Patricia A. DeJuneas and Sibbison\n& DeJuneas were on brief, for appellant.\n Eva M. Badway, Assistant Attorney General, with whom Maura\nHealey, Attorney General, was on brief, for appellee.\n\n\n January 4, 2019\n\f THOMPSON, Circuit Judge.\n\n The Antiterrorism and Effective Death Penalty Act of\n\n1996 (\"AEDPA\"), 28 U.S.C. § 2244(d)(1), establishes a one-year\n\nstatute of limitations for a state prisoner to file a federal\n\nhabeas corpus petition under 28 U.S.C. § 2254. The one-year period\n\ngenerally starts when a prisoner's conviction becomes final, but\n\nmay be tolled, pursuant to the statute, during the time in \"which\n\na properly filed application for State post-conviction or other\n\ncollateral review with respect to the pertinent judgment or claim\n\nis pending.\" Id. § 2244(d)(2).\n\n Petitioner Larry Blue, a Massachusetts prison inmate,\n\nfiled a petition for habeas corpus relief which the district court\n\ndismissed as time-barred under AEDPA's statute of limitations.\n\nPetitioner now seeks reconsideration of that ruling based on two\n\ntolling theories. First, Petitioner argues that the statute of\n\nlimitations should be statutorily tolled during the month-plus-\n\nlong pendency of his motion to stay the execution of his sentence,\n\nbecause that motion, he urges, constitutes an application for\n\ncollateral review under § 2244(d)(2). Second, Petitioner argues,\n\nessentially, that unique circumstances surrounding his conviction\n\njustify equitable tolling of the time between the finality of his\n\nCommonwealth convictions and the filing of his habeas petition.\n\nFor reasons explained below, we reject these arguments and affirm\n\nthe dismissal of Petitioner's habeas corpus petition.\n - 2 -\n\f I. Background\n\n Because dates are crucial to our evaluation of\n\nPetitioner's claims, we ask the reader's patience as we detail the\n\ntravel of the proceedings below. On August 18, 2010, following a\n\ntrial by jury, Petitioner was convicted of multiple Massachusetts\n\nstate law crimes, including drug trafficking, drug possession, and\n\nunlicensed firearm and ammunition possession. Thereafter, he\n\npleaded guilty to additional related charges and was handed a\n\ncumulative sentence of up to ten years and a day to serve.\n\n Petitioner pursued various avenues of post-conviction\n\nrelief in the Commonwealth courts.1 On June 14, 2012, Petitioner\n\nfiled a direct appeal of his convictions, based in part on\n\narguments previously raised and rejected by the trial court that\n\nthere were defects in the search warrants that led to his arrest.\n\nAdditionally, Petitioner premiered a new argument challenging the\n\nconstitutionality of Massachusetts's gun licensing regime.\n\n While Petitioner's appeal was pending, revelations of\n\nwidespread misconduct at the Commonwealth's crime lab, the William\n\nA. Hinton State Laboratory Institute, came to light with state-\n\nemployed chemist Annie Dookhan in the maelstrom of the scandal.\n\nIn response to these disclosures, in August 2012, Massachusetts's\n\n\n 1\n First, he filed a motion for a new trial, based on his\nassertion that the court reporter was unable to produce a full\ntranscript of his trial. This motion was denied the following day\nwhen the parties collaborated to reconstruct the missing record.\n - 3 -\n\fgovernor shuttered the lab and ordered an independent\n\ninvestigation.2 Dookhan, after being hit with multiple indictments\n\nfor falsifying drug test results, lying about her credentials, and\n\nperjuring herself in court (including during Petitioner's trial),\n\neventually pled guilty to twenty-seven counts on November 22, 2013.\n\n Meanwhile, the Appeals Court of Massachusetts denied\n\nPetitioner's direct appeal on September 27, 2013. Commonwealth v.\n\nBlue, 994 N.E.2d 817 (Table), 2013 WL 5377118 (Mass. App. Ct.\n\n2013). First, it cited its agreement with the trial court's\n\nreasoning for the denial of Petitioner's search warrant\n\nsuppression motions. And next, it pointed out the futility of\n\nPetitioner's constitutional challenge, noting the state's gun\n\nlicensing regime had already been given the green light by the\n\nMassachusetts Supreme Judicial Court (\"SJC\"). Id. Hoping to\n\nchange minds, Petitioner filed a motion for rehearing, but the\n\nappeals court promptly denied it.\n\n Soldiering on, Petitioner sought further appellate\n\nreview with the SJC in October 2013. However, that application\n\nwas summarily denied without discussion on November 21, 2013.\n\nCommonwealth v. Blue, 998 N.E.2d 342 (Mass. 2013) (Table). Ninety\n\n\n\n 2 Not long after the Dookhan misconduct was made public, an\nentry in the trial court docket reflects that Petitioner filed a\nmotion to stay the execution of his sentence on March 12, 2013.\nThe docket notation reads \"(Drug Lab)\"; the motion was withdrawn\nin June 2013.\n - 4 -\n\fdays later, on February 19, 2014, Petitioner's convictions became\n\nfinal; that is the moment the AEDPA statute of limitations clock\n\nbegan to tick.3\n\n In the wake of the Dookhan fiasco, Petitioner filed with\n\nthe trial court a second motion to stay the execution of his\n\nsentence, pursuant to Massachusetts Rule of Criminal Procedure 31\n\n(\"Rule 31\").4 In that February 21, 2014 filing he asserted his\n\nbelief that Dookhan's misconduct would likely result in the grant\n\nof a new trial on all charges given (1) the unreliability of the\n\nlaboratory testing supporting his drug convictions and (2) the\n\noverall taint Dookhan's perjured testimony cast on his\n\nconvictions, due to the prosecutor weaving together the drug\n\ndealing and the gun possession throughout the trial. In a\n\nmemorandum in support of his stay motion, Petitioner announced his\n\nintention to file a renewed motion for a new trial \"shortly,\" based\n\non Dookhan's perjury and other grounds.\n\n\n\n\n 3 Cordle v. Guarino, 428 F.3d 46, 48 (1st Cir. 2005) (\"The\nSJC affirmed [the] convictions on March 11, 1992; her convictions\nbecame final ninety days thereafter.\").\n 4 The Commonwealth's investigation into the Hinton Lab came\nto an end, concluding that, while Dookhan was \"the sole bad actor\"\nat the lab, poor and inadequate training, protocols, and management\nhad allowed her conduct to go undetected for years. It was\nconservatively estimated that Dookhan worked on close to 34,000\ncases during her years at the lab. Commonwealth v. Charles, 992\nN.E.2d 999, 1003 (Mass. 2013).\n - 5 -\n\f Back at the SJC, while Petitioner's motion to stay was\n\npending, the Commonwealth high court weighed in on the Dookhan\n\ndebacle: in cases where Dookhan had served as a primary or\n\nsecondary chemist for drug analysis, all defendants were entitled\n\nto a conclusive presumption that her conduct was egregious and\n\nattributable to the Commonwealth. Commonwealth v. Scott, 5 N.E.3d\n\n530, 535 (Mass. 2014). That presumption notwithstanding, soon\n\nafter the Scott opinion issued, Petitioner's motion for a stay of\n\nthe execution of his sentence was denied on March 27, 2014. The\n\ntrial court found that Petitioner's firearms convictions were\n\nunaffected by Dookhan's misconduct and as such, he was unlikely to\n\nreceive a new trial.\n\n Undeterred, on May 5, 2014, Petitioner filed a second\n\nmotion for a new trial based on two theories. First, he framed\n\nthe revelation of Dookhan's perjury as \"newly-discovered\n\nevidence,\" casting doubt on the fairness of his conviction. (For\n\nall intents and purposes, this taint argument is the same one that\n\nhad just been rejected by the court in response to his stay\n\nmotion.) His second argument, ineffective assistance of counsel,\n\nwas essentially a repackaging of the earlier defective search\n\nwarrant claims.5\n\n\n\n 5Petitioner alleged that the warrants failed to establish\ntimely probable cause because of their technical shortcomings, and\nthat his attorney was ineffective for failing to properly argue\n - 6 -\n\f On January 20, 2015, acting on Petitioner's new trial\n\nmotion, the trial court granted it as to the drug charges, and\n\ndenied it as to the gun charges. Commenting on the drug\n\nconvictions, the court conceded that, even though extensive\n\nevidence supported Petitioner's drug charges aside from Dookhan's\n\nperjured testimony, her testimony had, nonetheless, tainted the\n\ndrug convictions. As for the gun charges, the court found no\n\nconnection between Dookhan's testimony and those convictions.\n\nFinally, the trial court dismissed the ineffective assistance\n\nclaim, describing it as not distinct from Petitioner's prior search\n\nwarrant claims, and writing:\n\n [T]he Appeals Court implicitly rejected the defendant's\n instant claim . . . and made rejection explicit when it\n refused the defendant's petition for rehearing. The\n issue is settled and need not be considered on its merits\n here.\n\nTwo days later Petitioner appealed the partial denial to the\n\nappellate court, and sought further review after this first appeal\n\nwas denied. Commonwealth v. Blue, 46 N.E.3d 114 (Table), 2016 WL\n\n757758 (Mass. App. Ct. 2016). The Commonwealth nolle prossed the\n\ndrug charges at the end of January 2015.6 And, on April 27, 2016,\n\n\n\nthe defects -- an interpretive gloss that he had not explicitly\nraised before.\n\n 6 \"Nolle prossed\" comes from the Latin phrase \"nolle\nprosequi,\" translated as \"we shall no longer prosecute.\" In this\ncontext, it means that the Commonwealth dropped all the drug\ncharges against Petitioner.\n\n - 7 -\n\fthe SJC entered a final denial of Petitioner's application for\n\nfurther appellate review of his motion for a new trial.7\n\n Almost eleven months8 later, on March 20, 2017,\n\nPetitioner filed his federal petition for a writ of habeas corpus,\n\npremised solely on his allegations of ineffective assistance of\n\ncounsel.9 On the motion of Respondent Norfolk prison\n\nsuperintendent Sean Medeiros, the district court dismissed the\n\npetition as time-barred under AEDPA. Blue v. Medeiros, No. 17-\n\ncv-10464-ADB, 2017 WL 5297910, at *1 (D. Mass. Nov. 13, 2017). In\n\nso doing the district court held that Petitioner's motion to stay\n\nthe execution of his sentence did not toll AEDPA's one-year time\n\nlimit, under 28 U.S.C. § 2244(d)(2), because it was not an\n\n\"application for . . . collateral review.\" The court held further\n\nthat Petitioner was not entitled to equitable tolling because the\n\nissues created by the Hinton Lab misconduct did not impose a bar\n\n\n\n 7 There is no dispute that the AEDPA statute of limitations\nwas tolled for the almost two-year period that his motion for a\nnew trial was pending, from May 5, 2014, through April 27, 2016.\n\n 8 327 days, to be precise.\n 9 Again, Petitioner alleged that the search warrants\nunderlying his arrest and conviction failed to establish probable\ncause, and that trial counsel failed to argue this effectively.\nThese arguments are not before us in this appeal. Peralta v.\nUnited States, 597 F.3d 74, 83 (1st Cir. 2010) (general rule is\nthat \"a court of appeals should not consider the merits of an issue\nadvanced by a habeas petitioner unless a COA [certificate of\nappealability] first has been obtained with respect to that issue\"\n(quoting Bui v. DiPaolo, 170 F.3d 232, 237 (1st Cir. 1999))).\n - 8 -\n\fto Petitioner filing a motion for a new trial concurrently with\n\nhis motion for stay of execution (recall Petitioner's stay motion\n\nwas filed on February 21, 2014, while his new trial motion was not\n\nfiled until May 5, 2014); and because, even after his motion for\n\na new trial was denied and the Commonwealth had abandoned the drug\n\ncharges, Petitioner allowed eleven months to pass by before filing\n\nthe petition for the writ of habeas corpus.\n\n In his present appeal, Petitioner advances two\n\narguments relative to the timeliness of his habeas petition; we\n\ntake each in turn. Because the district court denied Petitioner\n\nrelief \"on a procedural ground without taking evidence,\" we apply\n\nde novo review. Holmes v. Spencer (Holmes I), 685 F.3d 51, 58\n\n(1st Cir. 2012) (quoting Wood v. Spencer, 487 F.3d 1, 3 (1st Cir.\n\n2007)).\n\n II. Statutory Tolling\n\n First, Petitioner argues that his motion to stay the\n\nexecution of his sentence tolled AEDPA's statute of limitations,\n\nbecause it is a properly filed application for \"collateral review\"\n\nas contemplated by 28 U.S.C. § 2244(d)(2). In support of his\n\nassertion that \"the plain meaning\" of AEDPA's tolling provision\n\n\"includes post-conviction motions [like a motion to stay] heard by\n\nthe trial judge,\" Petitioner cites Wall v. Kholi (Kholi III), 562\n\nU.S. 545 (2011). To better understand Petitioner's argument, a\n\nbrief discussion of Kholi is in order.\n - 9 -\n\f Khalil Kholi was convicted by the Rhode Island Superior\n\nCourt of repeated acts of sexual assault on his two young step-\n\ndaughters and received two consecutive life sentences. He appealed\n\nthe convictions and simultaneously filed a motion to reduce his\n\nsentence; both were unsuccessful. State v. Kholi, 706 A.2d 1326\n\n(R.I. 1998); State v. Kholi, 672 A.2d 429 (R.I. 1996).\n\n Kholi then filed a petition for a writ of habeas corpus\n\nin the federal district court, which denied relief after finding\n\nthe petition time-barred by AEDPA. Kholi v. Wall (Kholi I), No.\n\n07-346S, 2008 WL 60194 (D.R.I. Jan. 3, 2008). In so concluding,\n\nthe court held that Kholi's motion to reduce his sentence, brought\n\npursuant to Rule 35 of Rhode Island's criminal procedure rules,10\n\ndid not constitute an application for \"collateral review\" under\n\nAEDPA, and thus did not toll the limitations period. Instead, the\n\ncourt reasoned that \"a motion for correction or reduction of\n\nsentence contemplates the defendant returning to the same court,\n\nand pleading for mercy before the same judge that imposed the\n\noriginal sentence and thus, is not 'collateral' within the meaning\n\nof AEDPA.\" Id. at *3 (citing Walkowiak v. Haines, 272 F.3d 234,\n\n237-38 (4th Cir. 2001)).\n\n Kholi appealed and we reversed, holding that \"a state\n\npost-conviction motion for a sentence reduction, in the nature of\n\n\n\n 10 R.I. Super. Ct. R. Crim. P. 35 (a).\n - 10 -\n\fa plea for discretionary leniency, comes within the [AEDPA]\n\nstatutory sweep.\" Kholi v. Wall (Kholi II), 582 F.3d 147, 156\n\n(1st Cir. 2009). In reaching this conclusion, we stressed the\n\nimportance of encouraging state prisoners to exhaust state court\n\nremedies before seeking federal habeas review. Id. at 155.\n\n The state of Rhode Island sought further review and the\n\nSupreme Court granted certiorari. Kholi III, 562 U.S. at 551-53.\n\nIn affirming our ruling the Court carefully parsed the AEDPA\n\ntolling language. Defining the phrase \"collateral review\" in the\n\nAEDPA context, the Court stated, \"[v]iewed as a whole, then,\n\n'collateral review' of a judgment or claim means a judicial\n\nreexamination of a judgment or claim in a proceeding outside of\n\nthe direct review process.\" Id. at 553. In considering whether a\n\nRule 35 motion would trigger collateral review, the Supreme Court\n\nanalyzed the meanings of the words \"collateral\" and \"review.\" Id.\n\nat 555-56.\n\n Reasoning that a motion to reduce the sentence was\n\ntraditionally viewed as a collateral challenge, and was in no\n\ninstance a part of the direct review process, the Court quickly\n\ndetermined that the motion was collateral. Id. at 555. The Court\n\nthen moved on to examine its understanding of the word \"review.\"\n\nBased on the operation of the state's criminal rule, the motion\n\nwould require a \"judicial reexamination of the sentence to\n\ndetermine whether a more lenient sentence is proper\" and it\n - 11 -\n\ftherefore resulted in a review. Id. Consequently, the Court\n\ndetermined that Kholi's motion to reduce his sentence constituted\n\nan application for collateral review which triggered AEDPA's\n\ntolling provision. Id. at 556; see also Holmes I, 685 F.3d at 60;\n\nKholi II, 582 F.3d at 153 (\"Taking into account this quotidian\n\nunderstanding, it seems self-evident that a motion for a sentence\n\nreduction in the nature of a plea for discretionary leniency is a\n\nmotion that seeks post-conviction 'review' of a sentence and, thus,\n\nis a motion that falls squarely within the plain meaning of section\n\n2244(d)(2).\").\n\n As our Petitioner would have it, his Massachusetts Rule\n\n31 motion to stay execution of sentence is no different from the\n\nRule 35 motion discussed in Kholi III, and as such the district\n\ncourt erred when it deemed AEDPA's tolling provision not triggered.\n\nHowever, while we agree with Petitioner that his motion is,\n\nassuredly, a collateral one, we find it does not have the power to\n\ngenerate a review. As the government correctly suggests, we must\n\nturn to Massachusetts law to explain why. Carey v. Saffold, 536\n\nU.S. 214, 223 (2002) (\"[F]or purposes of applying a federal statute\n\nthat interacts with state procedural rules, we look to how a state\n\nprocedure functions . . . .\"); Lewis v. Jeffers, 497 U.S. 764,\n\n780-81 (1990) (urging deference to a state court's \"application of\n\nits own law\" in habeas context).\n\n\n - 12 -\n\f Rule 31 allows a trial judge or a single justice of the\n\nCommonwealth's appellate court to make a discretionary ruling\n\nstaying the imposition of a sentence during the pendency of an\n\nappeal.11 While the ruling on the stay will not be reversed absent\n\nan abuse of discretion, the judge generally requires a\n\ndemonstration that the defendant has a reasonable likelihood of\n\nsuccess on appeal. See Commonwealth v. Levin, 388 N.E.2d 1207,\n\n1208 (Mass. App. Ct. 1979). That means evaluating whether or not\n\nthe appeal is frivolous, or whether it is \"an appeal which presents\n\nan issue which is worthy of presentation to an appellate court,\n\none which offers some reasonable possibility of a successful\n\ndecision in the appeal.\" Id. at 1209. More recently, the SJC has\n\ndescribed this analysis as a \"pure question of law or legal\n\njudgment,\" which in no way prejudges \"the merits of the defendant's\n\ndirect appeal.\" Commonwealth v. Mattier, 49 N.E.3d 227, 228-29\n\n(Mass. 2016) (quoting Commonwealth v. Allen, 392 N.E.2d 1027, 1033\n\n(Mass. 1979)).12\n\n We have noted in the past that not all filings by a\n\ncriminal defendant which seek to advance a challenge to a judgment\n\n\n 11 The order is temporary and automatically expires upon\naffirmation of the conviction, unless it is extended by the\nappellate court. It may also be revoked. Rule 31(a), (b).\n 12 In addition to the merits evaluation, the judge\nentertaining the motion must also consider issues relating to\nsecurity, such as the defendant's risk of flight or likelihood of\ncommitting new criminal acts. Levin, 388 N.E.2d at 1210.\n - 13 -\n\fof conviction constitute a collateral review for AEDPA purposes.\n\nRodriguez v. Spencer, 412 F.3d 29, 37 (1st Cir. 2005) (petition\n\nfor extraordinary relief not application for collateral review);\n\nVoravongsa v. Wall, 349 F.3d 1, 7 (1st Cir. 2003) (pro se motion\n\nfor appointment of state post-conviction counsel not collateral\n\nreview); see also Bridges v. Johnson, 284 F.3d 1201, 1203 (11th\n\nCir. 2002) (application before a state sentence review panel not\n\ncollateral review); Adeline v. Stinson, 206 F.3d 249, 252 (2d Cir.\n\n2000) (motion to revive an appeal not collateral review).\n\nSimilarly here, from our perspective, the Rule 31 screening process\n\nlacks the indicia of a \"review\" for this reason: Even though a\n\njudge must take a peek at the underlying claim to see if the merits\n\nare hopeless, she has no authority to either alter the judgment or\n\nchange the sentence. See Kholi II, 582 F.3d at 151 (in the typical\n\ncase, application for post-conviction relief that \"does not seek\n\nto alter (or even to reexamine) the judgment\" does not toll\n\nstatute).\n\n For these reasons, after a fresh review of Petitioner's\n\nclaims, we hold that a motion to stay the execution of a sentence,\n\nunder Rule 31, does not constitute a motion for collateral review,\n\nand its filing does not trigger AEDPA's tolling provisions.13\n\n\n 13\n Even if the statute of limitations were tolled during the\npendency of his motion to stay the execution of his sentence, he\nstill goes over the statutory time limit. He has a short two\ndays between the date his convictions became final and the date he\n - 14 -\n\f III. Equitable Tolling\n\n Petitioner's second argument -- that equitable tolling\n\napplies to his habeas filing -- is grounded in principles of equity\n\nand fairness, and is primarily focused on the disruption in the\n\nCommonwealth's administration of justice caused by Dookhan's\n\ndeceitful misconduct.14 In claiming that his petition for habeas\n\ncorpus relief should be permitted to go forward, Petitioner offers\n\nthe following argument: \"The lower court presumed that equitable\n\ntolling can only apply to the time immediately preceding the filing\n\nof the habeas corpus petition, rather than to any period of time\n\nafter a conviction becomes final. . . .As far as petitioner is\n\naware, there is no requirement that the petitioner show a permanent\n\nimpediment from filing or to justify the year in which petitioner\n\nhas to file his application for a writ of habeas corpus.\"\n\nPetitioner's argument, then, seems to have two parts which go like\n\nthis. First, he says that the 75 days between February 19, 2014,\n\nthe date his convictions became final, up to May 5, 2014, when he\n\nfiled his motion for a new trial, must be equitably tolled because\n\n\n\n\nfiled his motion for a stay. Then, 39 days elapse between the\ndenial of his motion to stay and the filing of his motion for a\nnew trial. If you add those 41 days to the 327 days he waited\nbetween the final exhaustion of all state court review and the\ndate he filed the present writ, you get 368 days -- three days\nover the statutory time limit.\n 14\n As mentioned earlier, based on Scott, 5 N.E.3d at 535, this\nconduct may be attributed to the Commonwealth.\n - 15 -\n\fduring this time he was diligently pursuing state-court relief,\n\nand yet was thwarted by the difficulties posed by the Hinton Lab\n\ninvestigation. As he tells it: \"The magnitude of the problem\n\neffectively reopened and called into question thousands of\n\nconvictions. What followed were delays in post-conviction\n\nhearings, discovery issues, and an on-going, ultimately fifteen-\n\nmonth, investigation by the Office of the Inspector General into\n\nthe Hinton State Drug Laboratory that concluded on March 4, 2014.\"\n\n Second, as for the time from April 27, 2016 to March 20,\n\n2017, when Petitioner filed his habeas petition, he seems to be\n\ncontending that this period should be excluded altogether from our\n\nequitable tolling analysis. We consider Petitioner's contentions,\n\nkeeping in mind the guiding principles discussed next.\n\n To establish a basis for equitable tolling, a habeas\n\npetitioner must demonstrate that he or she has diligently pursued\n\nher rights, but some extraordinary circumstance, or obstacle,\n\nprevented timely filing. Holland v. Florida, 560 U.S. 631, 649\n\n(2010); Holmes I, 685 F.3d at 62. The diligence prong covers those\n\naffairs within the petitioner's control, while the extraordinary-\n\ncircumstances prong covers matters outside his control. Menominee\n\nIndian Tribe of Wis. v. United States, 136 S. Ct. 750, 755-57\n\n(2016). It is up to the petitioner to establish \"a causal\n\nrelationship between the extraordinary circumstances on which the\n\nclaim for equitable tolling rests and the lateness of his filing.\"\n - 16 -\n\fValverde v. Stinson, 224 F.3d 129, 134 (2d Cir. 2000).\n\nAdditionally, \"we apply equitable tolling on a case-by-case basis,\n\navoiding mechanical rules and favoring flexibility.\" Ortega\n\nCandelaria v. Orthobiologics LLC, 661 F.3d 675, 680 (1st Cir.\n\n2011). That said, equitable tolling is applied infrequently,\n\nHolmes I, 685 F.3d at 62, and abuse-of-discretion is the lens\n\nthrough which we review an equitable tolling decision, Holmes v.\n\nSpencer (Holmes II), 822 F.3d 609, 612 (1st Cir. 2016). This\n\nstandard of review is nuanced; \"within it, abstract questions of\n\nlaw are reviewed de novo, findings of raw fact are reviewed for\n\nclear error, and judgment calls receive a classically deferential\n\nreception.\" Holmes I, 685 F.3d at 62 (quoting Riva v. Ficco, 615\n\nF.3d 35, 40 (1st Cir. 2010)).\n\n In support of his two-part equitable tolling theory (to\n\nremind the reader: the period between the date of his final\n\nconviction and the date he filed his motion for a new trial should\n\nbe equitably tolled in full, and the eleven-month post new trial\n\ndenial period should be ignored altogether), Petitioner cites to\n\nHolmes I. Accordingly, closer scrutiny of that case is warranted.\n\n In Holmes I, habeas petitioner Holmes sought both\n\nstatutory and equitable tolling: statutory for a period during\n\n\n\n\n - 17 -\n\fwhich his motion to revise or revoke his sentence was pending;15\n\nequitable for the same period based on the obstacles imposed by\n\nhis incarceration, and by the incorrect legal filing he made in\n\nreliance on misleading advice from his lawyer during plea\n\nbargaining. Holmes I, 685 F.3d at 55-56. On appeal this court\n\naffirmed the district court in part, agreeing that, while Holmes's\n\nmotion to revise or revoke his sentence was in fact an application\n\nfor collateral review under AEDPA (based on the newly-minted Kholi\n\nIII decision), it still was not \"properly\" filed under\n\nMassachusetts law (his filing did not specify the grounds upon\n\nwhich the motion was based as Rule 29 requires)16 and so did not\n\ntrigger the statutory tolling mechanism within the meaning of 28\n\nU.S.C. § 2244(d)(2). Id. at 60-61. However, we remanded the\n\nmatter to the district court to review its equitable tolling\n\nruling, pointing out that Holmes's belief that he had in fact\n\nproperly filed his motion to revise or revoke his sentence might,\n\n\n\n\n 15\n Holmes's motion was brought pursuant to Massachusetts Rule\nof Criminal Procedure 29, a rule indistinguishable from Rhode\nIsland's Rule 35 discussed in Kholi III.\n 16\n An application is \"properly filed\" for AEDPA purposes \"when\nits delivery and acceptance are in compliance with the applicable\nlaws and rules governing filings.\" Holmes I, 685 F.3d at 67\n(quoting Artuz v. Bennett, 531 U.S. 4, 8 (2000)).\n\n - 18 -\n\fafter Kholi III, provide an equitable basis for excluding the time\n\nthe motion was pending.17 Id. at 63-66.\n\n Petitioner is correct that our Holmes I decision spends\n\nmuch time and analysis scrutinizing the almost nine-year period\n\nbetween Holmes's guilty plea and the final denial of\n\nreconsideration from the Commonwealth court, during which time he\n\nargued that he faced extraordinary obstacles (a lot was going on\n\nduring those nine years). Then, extrapolating from the focus of\n\nthat discussion, Petitioner posits that the additional seven-month\n\nperiod between the final ruling by the Commonwealth court and the\n\ndate Holmes filed his petition for habeas corpus must not have\n\nbeen relevant to our equitable tolling analysis. \"There was no\n\nweight given to, or even mention of, the seven months it took\n\n[Holmes] to file his habeas petition after his conviction became\n\nfinal,\" Petitioner writes in his brief. Therefore, according to\n\nPetitioner, it logically follows that in his case, the eleven-\n\nmonth period between the conclusion of the Commonwealth court\n\nreview and the filing of his habeas petition is not relevant to\n\n\n\n\n 17This court rejected Holmes's arguments that allegedly bad\nadvice from his lawyer, coupled with the disadvantages of\nincarceration, justified equitable tolling, suggesting sua sponte\na third ground for equitable tolling instead. As it turned out,\non remand, the district court held that there was no basis for\nequitable tolling and again denied Holmes's petition as untimely.\nThe ruling was affirmed by this court in Holmes II. 822 F.3d at\n612.\n - 19 -\n\four assessment of extraordinary circumstances or diligence when it\n\ncomes to an equitable tolling analysis.\n\n Unfortunately, Petitioner misconstrues our Holmes I\n\nrationale. A careful read makes it clear that we considered the\n\nentire period leading up to the filing of the habeas petition when\n\nwe wrote, \"[t]he timeliness of Holmes's federal habeas petition,\n\nthen, hinges on whether there are any grounds for excluding at\n\nleast twenty-two of the remaining thirty-four unaccounted months\n\nbetween May 1, 1998 [the date of Holmes's guilty plea] and April\n\n9, 2008 [the filing date of the habeas petition].\" Id. at 57. Of\n\ncourse, given the procedural intricacies that animated Holmes's\n\njourney through the Commonwealth criminal justice system, we had\n\nreason to more closely examine the months during which Holmes\n\nclaimed he was prevented by circumstances outside of his control\n\nfrom filing his habeas petition; but unquestionably, as clearly\n\nnoted in our decision, the full period was taken into account in\n\ncalculating the operation of the AEDPA time limit. Id. at 57-61.\n\nThus, with Holmes I's timing calculus properly understood, we\n\nreturn to Petitioner's argument.\n\n To briefly recap the timeline: approximately three\n\nyears and a month went by between the date Petitioner's convictions\n\nbecame final and the date he filed his habeas petition.18 After\n\n\n 18In its argument on equitable tolling, the government comes\nup with a different set of calculations. The government starts\n - 20 -\n\fPetitioner's motion for a new trial was finally denied, eleven\n\nmonths went by before the present motion got filed. Even if we\n\nwere to accept Petitioner's argument that the entire Dookhan\n\ndebacle posed an insurmountable obstacle to Petitioner's filing a\n\ntimely habeas proceeding prior to the SJC's final resolution of\n\nhis motion for a new trial on April 27, 2016, he nevertheless can\n\npoint to no fact which demonstrates any obstacle, extraordinary or\n\notherwise, that hindered his filing of a habeas petition during\n\nthe final eleven months. Nor can he point to any behavior on his\n\npart that would demonstrate reasonable diligence in pursuing his\n\nrights during the final eleven months. When Petitioner's motion\n\nfor a new trial was denied, it should have been clear to him that\n\nall state-court avenues for relief had been exhausted. That is\n\nthe moment he needed to move swiftly to preserve his federal rights\n\nas the Hinton Lab misconduct could no longer be described as\n\n\n\n\nthe clock on November 21, 2013, the date that Petitioner's\napplication for further state-level appellate review was denied.\nThe government concludes then that 165 days elapsed before\nPetitioner filed his motion for a new trial. This court has\ngenerally determined that the judgment becomes final after an\nadditional ninety days have elapsed to allow for the filing of a\npetition for certiorari, see Neverson v. Farquharson, 366 F.3d 32,\n36 (1st Cir. 2004), starting the AEDPA clock then after that\nninety-day period. With its argument, the government seeks to\nunderscore that the Petitioner also had this ninety-day period\navailable during which he might have filed his motion for a new\ntrial, thereby undermining Petitioner's diligence argument. The\ngovernment does not press an argument about this clock-starting\ndate, and, in any case, this discrepancy is not determinative of\nthe outcome.\n - 21 -\n\fimpeding his ability to seek post-conviction review. See Neverson\n\nv. Farquharson, 366 F.3d 32, 44 (1st Cir. 2004). As the government\n\ncorrectly points out, the Commonwealth nolle prossed Petitioner's\n\ndrug charges in January 2015. As these were the only charges\n\ndirectly affected by Dookhan's malfeasance, the putative obstacle\n\nposed by the Hinton Lab issues dematerialized over a year before\n\nhis motion for a new trial was denied. Petitioner's argument that\n\nthe gun-related convictions were tainted by the prosecutor's\n\nclosing remarks at trial (connecting the drugs with the gun) had\n\nbeen repeatedly rejected by the Commonwealth courts by April 2016\n\n-- twice by the trial court, once by the appellate court, and\n\nfinally by the SJC. As a result, Petitioner's hope, or misguided\n\nbelief, that this theory might provide him a lifeline could no\n\nlonger be reasonably understood as an obstacle preventing him from\n\npursuing his federal remedy.\n\n IV. Conclusion\n\n Because we find that Petitioner's motion to stay the\n\nexecution of his sentence was not a request for collateral review\n\nand so did not toll the one-year statute of limitations in the\n\nAntiterrorism and Effective Death Penalty Act, and because we find\n\nno reason to disrupt the district court's discretionary ruling on\n\nequitable tolling, we affirm the dismissal of Petitioner's\n\npetition for a writ of habeas corpus as time-barred.\n\n\n - 22 -\n[END_CASE]", "role": "user" } ]
4,579,761
PREP TOURS, INC., Plaintiff-Appellant, v. AMERICAN YOUTH SOCCER ORGANIZATION; Downey AYSO Region 24; Armando Rodríguez, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Ramón Aguilar, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Carl Jackson, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Alicia Ramírez, in Her Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; John Doe; Richard Doe; Bob Doe; Insurance Company A; Insurance Company B, Defendants-Appellees.
PREP Tours Inc. v. American Youth Soccer Org.
2019-01-08
17-1223P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Lipez, Barron", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887836/", "author_raw": ""}, {"author": "", "type": "040dissent", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887837/", "author_raw": ""}, {"author": "BARRON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1223\n\n PREP TOURS, INC.,\n\n Plaintiff-Appellant,\n\n v.\n\n AMERICAN YOUTH SOCCER ORGANIZATION; DOWNEY AYSO REGION 24;\n ARMANDO RODRÍGUEZ, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; RAMÓN AGUILAR, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; CARL JACKSON, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; ALICIA RAMÍREZ, in her capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; JOHN DOE; RICHARD DOE; BOB DOE;\n INSURANCE COMPANY A; INSURANCE COMPANY B,\n\n Defendants-Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Pedro A. Delgado-Hernández, U.S. District Judge]\n\n\n Before\n\n Torruella, Lipez, and Barron,\n Circuit Judges.\n\n\n Steven J. Torres, with whom Brooks L. Glahn, Torres Scammon\nHincks & Day LLP, Darío Rivera-Carrasquillo, Giancarlo Font, and\nRivera-Carrasquillo, Martínez & Font were on brief, for appellant.\n Alan P. Dagen, with whom The Law Offices of Seda & Alan P.\nDagen, P.A., Luis A. Oliver-Fraticelli, and Adsuar Muñiz Goyco\n\nPérez-Ochoa, P.S.C. were on brief, for appellees.\n\n\n January 8, 2019\n\n BARRON, Circuit Judge. This appeal raises a now familiar\n\nissue: when do remote communications by email and telephone give\n\nrise to the kind of connection to a forum state or territory that\n\njustifies the exercise of personal jurisdiction in that forum over\n\nan out-of-forum defendant? The issue comes to us in this case via\n\nthe diversity suit in the United States District of Puerto Rico\n\nthat a Puerto Rico tour company brought against a California youth\n\nsoccer organization and related defendants. The tour company\n\nalleges in this suit that the defendants, by first requesting that\n\nthe tour company make an offer for a potential soccer trip to\n\nPuerto Rico for some of the organization's teams and their families\n\nbut then declining after further communications to book the tour,\n\nbreached duties that the organization owed to it under Puerto Rico\n\ncontract and tort law. In response to the defendants' motion, the\n\nDistrict Court dismissed both the contract and tort claims for\n\nlack of personal jurisdiction. We now affirm that order.\n\n I.\n\n American Youth Soccer Organization (\"AYSO\") is a\n\nnonprofit entity incorporated and headquartered in California.1\n\n\n\n\n 1 \"We derive our recitation of the case's facts from [the\nplaintiff's] properly documented evidentiary proffers and from\nthose portions of the defendants' proffers that are undisputed.\"\nCopia Commc'ns, LLC v. Amresorts, LP, 812 F.3d 1, 2 (1st Cir.\n2016).\n\n\n - 3 -\n\nThe other defendants are Downey AYSO Region 24 (\"Region 24\") and\n\nfour volunteers for Region 24.\n\n Region 24 is a regional chapter of AYSO from Downey,\n\nCalifornia. Region 24 is not a separate legal entity from AYSO.\n\n The four Region 24 volunteers served at all relevant\n\ntimes as, respectively, Region 24's commissioner (Armando\n\nRodríguez), assistant commissioner (Ramón Aguilar), treasurer\n\n(Carl Jackson), and volunteer coordinator (Alicia Ramírez). All\n\nfour individuals are residents of California.\n\n PREP TOURS, Inc. (\"PREP Tours\") is the plaintiff.2 It\n\nis a Puerto Rico corporation that, according to the complaint,\n\n\"specializes in student cultural immersion educational field\n\ntrips\" and is \"dedicated to servicing and organizing educational\n\nsoccer tours for student athletes and soccer clubs focusing on\n\nfriendly soccer games in Puerto Rico.\"\n\n On Friday, November 2, 2012, Ramírez emailed PREP Tours\n\nfrom California to ask for a price quote and for what the company\n\ncould \"offer\" regarding an all-inclusive trip to Puerto Rico for\n\n\"[a]pproximately 60 players and their families.\" Ramírez informed\n\nthe tour company in that email that Region 24 was also gathering\n\n\n 2\n The covers of PREP Tours's briefs list additional\nplaintiffs, but neither the complaint nor the District Court's\njudgment identifies any additional plaintiff other than PREP\nTours. And the notice of appeal specifies only PREP Tours as the\nparty taking this appeal. See Rosario-Torres v. Hernandez-Colon,\n889 F.2d 314, 316-17 (1st Cir. 1989).\n\n\n - 4 -\n\ninformation about alternative destinations, like Hawaii and\n\nMexico.\n\n PREP Tours responded that very same Friday by sending\n\nvia email a promotional brochure regarding the \"unique soccer\n\nprogram\" in the Puerto Rico cities of San Juan and Rincón that it\n\noffered visiting youth soccer teams. The tour company also emailed\n\nRamírez, after the weekend, a proposed itinerary based on the San\n\nJuan and Rincón tour described in the brochure, which PREP Tours\n\ndescribed as \"a tentative rough draft.\" There followed,\n\nintermittently over the next four months, emails and telephone\n\ncalls, as well as at least one text message, between the parties\n\nconcerning the possible trip. During these ensuing\n\ncommunications, Ramírez informed PREP Tours that Region 24 was\n\nconsidering competing offers on a possible trip to Puerto Rico\n\nfrom three alternative travel agencies, at least one of which was\n\nnot based in Puerto Rico.\n\n Before Region 24 made a decision about the trip, a travel\n\nagency in Florida, Hakuna Matata Group Tours, LLC, contacted\n\nRamírez by email concerning possible flights. The complaint says\n\nthat Hakuna Matata was \"designated by PREP Tours\" to handle the\n\nsoccer teams' flight arrangements.\n\n Hakuna Matata later emailed Ramírez with information for\n\nwiring it money as a deposit on the airline flights. Region 24's\n\ntreasurer, Jackson, thereafter emailed Hakuna Matata to say that\n\n\n - 5 -\n\nhe could wire transfer the money to Hakuna Matata's account the\n\nnext day, January 25.\n\n Jackson did not wire the money. Ramírez did write PREP\n\nTours on January 25, however, to say that the commissioner,\n\nassistant commissioner, and treasurer of Region 24 still had \"to\n\ngo through everything with a fine tooth-comb.\"\n\n The record references no further communications between\n\nany of the parties until the ones that were made on February 25,\n\n2013. On that day, PREP Tours emailed Region 24's commissioner,\n\nassistant commissioner, and treasurer to follow up on the status\n\nof its offer.\n\n The commissioner, Rodríguez, responded that same day\n\nwith an email telling PREP Tours that the assistant commissioner,\n\nAguilar, was \"still working on logistics.\" He then sent a later\n\nemail that instructed PREP Tours to disregard this first email.\n\nAguilar had responded in the interim by informing PREP Tours that\n\n\"[a]fter reviewing all proposals from the 3 compan[ies] we decided\n\nto go with a local company.\"\n\n Just short of two years later, PREP Tours sued AYSO,\n\nRegion 24, and the four volunteers in the United States District\n\nCourt for the District of Puerto Rico, seeking a minimum of\n\n$640,000 in damages. The complaint alleged that the defendants\n\nwere liable under the Puerto Rico tort doctrine of culpa in\n\ncontrahendo, \"which requires parties to negotiate in good faith.\"\n\n\n - 6 -\n\nYsiem Corp. v. Commercial Net Lease Realty, Inc., 328 F.3d 20, 23\n\n(1st Cir. 2003) (citation omitted). The complaint also alleged a\n\nbreach-of-contract claim under Puerto Rico law. The complaint\n\nasserted that the contract was created by: (1) the email from\n\nRegion 24's treasurer to Hakuna Matata in Florida, saying that he\n\ncould wire money to that third-party travel agency in order to\n\nmake a deposit on the airline flights; and (2) other\n\n\"representations\" made by the defendants. The complaint did not\n\nallege what the contract's terms were, but it did allege that the\n\ndefendants were in breach of the contract.\n\n The defendants moved to dismiss PREP Tours's claims\n\nunder Federal Rule of Civil Procedure 12(b)(2) for lack of personal\n\njurisdiction, and the defendants submitted affidavits with their\n\nmotion. An affidavit from AYSO's deputy executive director as\n\nwell as affidavits from the individual defendants each averred\n\nthat the \"only contacts\" that existed between the defendants and\n\nPREP Tours consisted of \"the preliminary communications between\n\nsome of [the Region 24] volunteers and the travel agency with whom\n\nthey communicated in an effort to obtain pricing and information\n\nfor a potential trip for some of [Region 24's] youth soccer teams.\"\n\n PREP Tours's brief in opposition to the defendants'\n\nmotion to dismiss included a number of evidentiary submissions\n\nattached as exhibits. The submissions included copies of the\n\n\n\n\n - 7 -\n\ncommunications exchanged between the parties during the relevant\n\nfour-month period.\n\n Neither party requested an evidentiary hearing following\n\nthe defendants' motion challenging personal jurisdiction, nor did\n\nthe District Court conduct one. The District Court instead used\n\nwhat we have referred to as \"the prima facie standard\" to assess\n\nwhether PREP Tours had met its burden to justify the exercise of\n\npersonal jurisdiction in Puerto Rico over the defendants. Boit v.\n\nGar-Tec Prods., Inc., 967 F.2d 671, 675-76 (1st Cir. 1992)\n\n(emphasis omitted); see also A Corp. v. All Am. Plumbing, Inc.,\n\n812 F.3d 54, 58 (1st Cir. 2016) (explaining that the plaintiff\n\nbears the burden to establish that personal jurisdiction exists\n\nover the defendant).\n\n Under this standard, a district court \"consider[s] only\n\nwhether the plaintiff has proffered evidence that, if credited, is\n\nenough to support findings of all facts essential to personal\n\njurisdiction.\" Boit, 967 F.2d at 675. \"To make a prima facie\n\nshowing of this calib[er], the plaintiff ordinarily cannot rest\n\nupon the pleadings, but is obliged to adduce evidence of specific\n\nfacts.\" Foster-Miller, Inc. v. Babcock & Wilcox Can., 46 F.3d\n\n138, 145 (1st Cir. 1995) (citing Boit, 967 F.2d at 675).\n\n In July of 2016, the District Court granted the\n\ndefendants' motion to dismiss PREP Tours's claims without\n\nprejudice for lack of personal jurisdiction. The District Court\n\n\n - 8 -\n\nreasoned that, although the defendants reached out to PREP Tours\n\nregarding the trip, they \"repeatedly communicated to [PREP Tours]\n\nthat officials had not made a final decision in regards to the\n\ntrip\" and that the \"unilateral\" actions undertaken by PREP Tours\n\nin Puerto Rico in response were insufficient to establish personal\n\njurisdiction over the defendants as to any of PREP Tours's claims.\n\n PREP Tours now appeals. Our review of the District\n\nCourt's judgment is de novo. See Boit, 967 F.2d at 675. \"Reviewing\n\na decision made under the prima facie standard, we must accept\n\n[the plaintiff's] properly documented evidentiary proffers as true\n\nand construe them in the light most favorable to [the plaintiff's]\n\njurisdictional claim.\" A Corp., 812 F.3d at 58 (citing Phillips\n\nv. Prairie Eye Ctr., 530 F.3d 22, 26 (1st Cir. 2008)). \"But we\n\nwill also consider facts offered by [the defendants], to the extent\n\nthat they are not disputed.\" Id. (citing Daynard v. Ness, Motley,\n\nLoadholt, Richardson & Poole, P.A., 290 F.3d 42, 51 (1st Cir.\n\n2002)).\n\n II.\n\n PREP Tours conceded below, as it must, that the District\n\nCourt lacks general jurisdiction over the defendants because the\n\ndefendants do not have \"continuous and systematic\" contacts with\n\nPuerto Rico. Goodyear Dunlop Tires Operations, S.A. v. Brown, 564\n\nU.S. 915, 919 (2011). PREP Tours nevertheless contends that the\n\nDistrict Court erred in dismissing its claims because the District\n\n\n - 9 -\n\nCourt does have \"specific or case-linked\" jurisdiction over the\n\ndefendants as to both of its claims. Id. Jurisdiction on this\n\nbasis \"depends on an affiliatio[n] between the forum and the . .\n\n. controversy\" underlying the plaintiff's claims. Id. (alteration\n\nin original) (internal quotation marks omitted).\n\n \"When . . . the lens of judicial inquiry narrows to focus\n\non specific jurisdiction . . . . the applicable constitutional\n\nlimits assume critical importance.\" Foster-Miller, 46 F.3d at\n\n144. Those limits, arising from the Due Process Clause of the\n\nFourteenth Amendment to the United States Constitution, permit a\n\ncourt to exercise jurisdiction over an out-of-forum defendant only\n\nif, with respect to the claims at issue, the defendant has \"certain\n\nminimum contacts with [the forum] such that the maintenance of the\n\nsuit does not offend 'traditional notions of fair play and\n\nsubstantial justice.'\" Int'l Shoe Co. v. Washington, 326 U.S.\n\n310, 316 (1945) (quoting Milliken v. Meyer, 311 U.S. 457, 463\n\n(1940)).3\n\n\n\n\n 3\n \"The requirements of International Shoe . . . must be met\nas to each defendant over whom a state court exercises\njurisdiction.\" Rush v. Savchuk, 444 U.S. 320, 332 (1980). The\nparties dispute whether, under the facts of this case, we may\nattribute the various defendants' combined forum contacts to each\nindividual defendant for the purposes of the personal jurisdiction\nanalysis. Because even the combined forum contacts are\nconstitutionally insufficient, however, we need not decide who is\nright.\n\n\n - 10 -\n\n To determine whether the exercise of specific\n\njurisdiction in the forum over an out-of-forum defendant conforms\n\nto that federal constitutional test, three requirements must be\n\nmet:\n\n First, the claim underlying the litigation\n must directly arise out of, or relate to, the\n defendant's forum-state activities. Second,\n the defendant's in-state contacts must\n represent a purposeful availment of the\n privilege of conducting activities in the\n forum state, thereby invoking the benefits and\n protections of that state's laws and making\n the defendant's involuntary presence before\n the state's courts foreseeable. Third, the\n exercise of jurisdiction must . . . be\n reasonable.\n\nUnited Elec., Radio & Mach. Workers of Am. v. 163 Pleasant St.\n\nCorp., 960 F.2d 1080, 1089 (1st Cir. 1992).\n\n This inquiry is highly \"fact-specific.\" Id. As the\n\nSupreme Court has explained, the constitutional test is \"not\n\nsusceptible of mechanical application; rather, the facts of each\n\ncase must be weighed to determine whether the requisite\n\n'affiliating circumstances' are present.\" Kulko v. Superior Court\n\nof Cal., 436 U.S. 84, 92 (1978) (quoting Hanson v. Denckla, 357\n\nU.S. 235, 246 (1958)). Moreover, \"this determination is one in\n\nwhich few answers will be written 'in black and white. The greys\n\nare dominant and even among them the shades are innumerable.'\"\n\nId. (quoting Estin v. Estin, 334 U.S. 541, 545 (1948)).\n\n\n\n\n - 11 -\n\n III.\n\n We begin with the requirement that PREP Tours's claims\n\nmust relate to the defendants' contacts with Puerto Rico. This\n\n\"flexible, relaxed standard\" for assessing relatedness requires\n\nthat there be only a \"demonstrable nexus\" between the complaint's\n\nclaims and the activities in the forum that properly may be\n\nattributed to the defendants, such that \"the litigation itself is\n\nfounded directly on those activities.\" Adelson v. Hananel, 652\n\nF.3d 75, 81 (1st Cir. 2011) (quoting N. Laminate Sales, Inc. v.\n\nDavis, 403 F.3d 14, 25 (1st Cir. 2005); Hannon v. Beard, 524 F.3d\n\n275, 279-80 (1st Cir. 2008)).\n\n PREP Tours contends that, as to each of its claims, the\n\ndefendants' \"related\" forum contacts are the defendants' remote\n\ncommunications with the Puerto Rico-based tour company during the\n\nfour-month period beginning with Ramírez's initial inquiry email\n\nand the activities that PREP Tours undertook from Puerto Rico\n\nduring those four months in response to those communications.4\n\nPREP Tours contends that its tort claim alleging that the\n\ndefendants negotiated in bad faith arises from the defendants'\n\n\n\n 4\n PREP Tours does point out that the AYSO teams eventually\ntraveled to Puerto Rico in July of 2013. But, this trip occurred\nseveral months after the communications between the parties from\nwhich PREP Tours asserts that their claims arise, and PREP Tours\nmakes no argument that their claims also arise from this trip.\nSee Carreras v. PMG Collins, LLC, 660 F.3d 549, 554 (1st Cir.\n2011).\n\n\n - 12 -\n\ncontacts with Puerto Rico because it was through the defendants'\n\nremote communications with the tour company that the defendants\n\nacted in bad faith, resulting in harm to the tour company in Puerto\n\nRico in consequence of, at least in part, the activities that PREP\n\nTours undertook in Puerto Rico in response to those communications.\n\nPREP Tours contends that its breach-of-contract claim arises from\n\nthese same set of contacts, as the remote communications between\n\nthe parties and the actions that the tour company undertook in\n\nresponse to them provide the basis for the claim that the\n\ndefendants reached into Puerto Rico to enter into the alleged\n\ncontract and then breached it. See Daynard, 290 F.3d at 52\n\n(explaining that, with respect to a breach-of-contract claim, we\n\nfocus on \"the parties' 'prior negotiations and contemplated future\n\nconsequences, along with the terms of the contract and the parties'\n\nactual course of dealing'\" (quoting Burger King Corp. v. Rudzewicz,\n\n471 U.S. 462, 479 (1985))).\n\n The defendants counter that PREP Tours's claims do not\n\nin fact arise from their remote communications with the tour\n\ncompany or the activities in Puerto Rico that PREP Tours claims to\n\nhave taken in response to those communications. The defendants\n\ncontend that their conduct that allegedly breached both their duty\n\nto negotiate in good faith and their alleged contract with PREP\n\nTours was their decision to book the trip through a different\n\ncompany, which was a decision that they made outside of Puerto\n\n\n - 13 -\n\nRico. Moreover, as far as the breach-of-contract claim is\n\nconcerned, the defendants point out that the complaint's only non-\n\nconclusory allegation that a contract existed between the parties\n\nis based on an email that was sent by Region 24's treasurer in\n\nCalifornia to a travel agency, Hakuna Matata, that is located in\n\nFlorida and that has no connection to Puerto Rico.\n\n The District Court agreed with PREP Tours that the\n\nrelatedness requirement for case-linked jurisdiction is met as to\n\nboth the tort and contract claims, but we need not decide whether\n\nthe District Court was right. Even if the defendants' remote\n\ncommunications with PREP Tours and PREP Tours's activities in\n\nPuerto Rico in response relate to PREP Tours's claims, PREP Tours\n\nmust also show that the defendants purposefully availed themselves\n\nof the privilege of conducting activities in Puerto Rico through\n\nthese contacts. See United Elec., 960 F.2d at 1089. And, as we\n\nnext explain, the District Court rightly concluded that PREP Tours\n\nfailed to do so. Accordingly, we turn to the purposeful availment\n\ninquiry, assuming that the contacts that PREP Tours identifies as\n\nbeing related to its claims are in fact related to them.5\n\n\n 5 Given this conclusion, we also do not need to reach the\nreasonableness requirement of the due process analysis. Nor do we\nneed to reach the issue of whether personal jurisdiction is\npermitted under Puerto Rico's long-arm statute. See Ticketmaster-\nN.Y., Inc. v. Alioto, 26 F.3d 201, 204 (1st Cir. 1994) (explaining\nthat, in order to assert specific jurisdiction over an out-of-\nforum defendant, a federal court sitting in diversity \"must find\n\n\n\n - 14 -\n\n IV.\n\n To explain why we agree with the District Court that\n\nPREP Tours has not satisfied the purposeful availment requirement\n\nas to any of its claims, we first need to describe that requirement\n\nin more detail. With that legal background in place, we then can\n\nexplain why we conclude that PREP Tours, on this record, fails to\n\nmake the requisite showing.\n\n A.\n\n To show that the defendants purposefully availed\n\nthemselves of the privilege of conducting activities in the forum,\n\nPREP Tours must demonstrate that the defendants established a\n\n\"substantial connection\" with Puerto Rico. Burger King, 471 U.S.\n\nat 475 (quoting McGee v. Int'l Life Ins. Co., 355 U.S. 220, 223\n\n(1957)). Put otherwise, PREP Tours must point to \"some act by\n\nwhich the defendant[s] purposefully avail[ed] [them]sel[ves] of\n\nthe privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Id.\n\n(quoting Hanson, 357 U.S. at 253).\n\n By requiring the plaintiff to establish such a\n\nsubstantial connection between the out-of-forum defendant and the\n\nforum, we ensure that it is \"fair to require defense of the action\n\nin the forum.\" Kulko, 436 U.S. at 91 (citing Milliken, 311 U.S.\n\n\ncontacts that, in the aggregate, satisfy the requirements of both\nthe forum state's long-arm statute and the Fourteenth Amendment\").\n\n\n - 15 -\n\nat 463-64). The purposeful availment requirement in this way\n\n\"represents a rough quid pro quo: when a defendant deliberately\n\ntargets its behavior toward the society or economy of a particular\n\nforum, the forum should have the power to subject the defendant to\n\njudgment regarding that behavior.\" Carreras, 660 F.3d at 555\n\n(citing J. McIntyre Mach., Ltd. v. Nicastro, 564 U.S. 873, 879\n\n(2011) (plurality op.)).\n\n The flip side of this deal, however, is that when the\n\nout-of-forum defendant has not \"manifestly . . . availed himself\n\nof the privilege of conducting business there,\" it would be\n\n\"unreasonable to require [the defendant] to submit to the burdens\n\nof litigation in that forum[.]\" Burger King, 471 U.S. at 476.\n\nAnd, in accord with this understanding of the purposeful availment\n\nrequirement, we have explained that \"the two cornerstones of\n\npurposeful availment\" are \"voluntariness\" and \"foreseeability.\"\n\nTicketmaster-N.Y., 26 F.3d at 207.\n\n \"Voluntariness requires that the defendant's contacts\n\nwith the forum state 'proximately result from actions by the\n\ndefendant himself.'\" Phillips, 530 F.3d at 28 (quoting Burger\n\nKing, 471 U.S. at 475). Accordingly, the Supreme Court has\n\nexplained that any contacts that cannot be attributed\n\n\"proximately\" to the defendant's own activities constitute\n\n\"unilateral\" activity that cannot establish purposeful availment.\n\nSee Burger King, 471 U.S. at 475.\n\n\n - 16 -\n\n In addition, the Supreme Court has described the\n\n\"benchmark\" for purposeful availment in terms of a particular \"kind\n\nof foreseeability.\" Id. at 474 (quoting World-Wide Volkswagen\n\nCorp. v. Woodson, 444 U.S. 286, 295 (1980)); see also Donatelli v.\n\nNat'l Hockey League, 893 F.2d 459, 464 (1st Cir. 1990) (discussing\n\nthe Court's introduction of this \"explicit 'foreseeability'\n\nelement into the liturgy of minimum contacts\"). Specifically, the\n\nSupreme Court has explained that \"the foreseeability that is\n\ncritical to due process analysis . . . is that the defendant's\n\nconduct and connection with the forum State are such that he should\n\nreasonably anticipate being haled into court there.\" Burger King,\n\n471 U.S. at 474 (quoting World-Wide Volkswagen, 444 U.S. at 297).\n\nFor this reason, too, a plaintiff's \"unilateral activity\" cannot\n\nestablish the requisite connection between the defendants and the\n\nforum jurisdiction. Id. at 474-75 (quoting Hanson, 357 U.S. at\n\n253).\n\n There is good reason to focus on whether out-of-forum\n\ndefendants could foresee being haled into a court in the forum\n\nfrom the connection that they are said to have with the forum.\n\nSuch a focus for the inquiry \"gives a degree of predictability to\n\nthe legal system\" because it \"allows potential defendants to\n\nstructure their primary conduct with some minimum assurance as to\n\nwhere that conduct will and will not render them liable to suit.\"\n\nWorld-Wide Volkswagen, 444 U.S. at 297.\n\n\n - 17 -\n\n Notably, the fact that a defendant directly contacted\n\nthe plaintiff in the forum only remotely by Internet or telephone,\n\nas allegedly happened here, does not preclude the defendant from\n\nhaving the substantial connection to the forum that is necessary\n\nto satisfy the purposeful availment requirement. See Burger King,\n\n471 U.S. at 476. Such remote communications are often the primary\n\nmeans by which business relationships are forged and conducted.\n\nSee id.\n\n But, as the Supreme Court has noted, the application of\n\nthe rule prohibiting a plaintiff's unilateral activity from\n\nestablishing the requisite foreseeable substantial connection\n\nbetween the defendant and the forum \"will vary with the quality\n\nand nature of the defendant's activity.\" Id. at 474-75 (quoting\n\nHanson, 357 U.S. at 253). Thus, the fact that the communications\n\noccurred remotely may well be relevant to the inquiry. And, to\n\nthat very point, we have recently observed that three factors have\n\nbeen the \"hing[e]\" in our past assessment of purposeful availment\n\nin cases in which remote communications supplied the predicate for\n\nthe contacts that ground specific or case-linked personal\n\njurisdiction over an out-of-forum defendant: \"the defendant's in-\n\nforum solicitation of the plaintiff's services, the defendant's\n\nanticipation of the plaintiff's in-forum services, and the\n\nplaintiff's actual performance of extensive in-forum services.\"\n\nCopia, 812 F.3d at 6 (emphasis added) (describing the factors from\n\n\n - 18 -\n\nC.W. Downer & Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59\n\n(1st Cir. 2014), and Cossart v. United Excel Corp., 804 F.3d 13\n\n(1st Cir. 2015)).\n\n B.\n\n Against this background, we now must assess whether the\n\nshowing that PREP Tours has made regarding both the nature and\n\nquality of the defendants' activities and the activities that PREP\n\nTours engaged in that relate to the contract and tort claims at\n\nissue satisfies the purposeful availment requirement. PREP Tours\n\nrelies on the three factors identified in Copia in asserting that\n\nits showing as to these activities does suffice. And so we need\n\nto address what PREP Tours has to say about how these activities\n\nrelate to each of these factors.6\n\n\n 6 The dissent suggests that it is focusing only on the\nplaintiff's tort claim because it \"reveals so clearly the error in\nthe majority's purposeful availment analysis and unfairness of the\noutcome.\" See Diss. Op. 44 n.27. But, we do not see how the\ndistinction between the tort claim and the contract claim matters\nto the purposeful availment inquiry, or how the focus on the tort\nclaim reveals any unfairness with respect to the lack of personal\njurisdiction over the defendant in Puerto Rico that would not be\nequally evident if we focused on the contract claim. After all,\nwhile the dissent cites to much precedent explicating Puerto Rico\ntort law, the purposeful availment test does not derive its content\nfrom local law. It derives its content from the requirements of\na federal constitutional protection. And Copia holds that this\nprotection requires a showing that the out-of-forum defendant,\nthrough voluntary contacts making the forum's assertion of\njurisdiction over him foreseeable, has established a greater tie\nto that forum than was determined to be present there. See 812\nF.3d at 6. Nothing in the way that Puerto Rico has chosen to\ndefine the elements of this tort claim, therefore, can permit us\n\n\n\n - 19 -\n\n PREP Tours does point to aspects of the record that bear\n\non each one of these three factors. As to solicitation, we agree\n\nwith PREP Tours that the record shows that one of the Region 24\n\nvolunteers, Ramírez, voluntarily reached out (remotely) from\n\n\n\nto conclude that a lesser tie than was present in Copia may suffice\nto satisfy the federal constitutional minimum that we discerned in\nthat case. And the dissent cites no case indicating to the\ncontrary.\n Of course, in some cases, the defendant's contacts with the\nforum jurisdiction that are related to a plaintiff's tort claim\nmight differ from those related to its contract claim, such that\nthe purposeful availment inquiry with respect to each claim might\nrequire an assessment of distinct contacts. See Phillips Exeter\nAcad. v. Howard Phillips Fund, 196 F.3d 284, 288-89 (1st Cir. 1999)\n(explaining that the relatedness inquiry is done \"on a claim-by-\nclaim basis\" because it depends on the nexus between the alleged\nin-forum contacts and the \"elements of the cause of action\"). In\nCopia, for example, because the plaintiffs pressed a contract\nclaim, we only considered the defendants' \"relevant, i.e.,\ncontract-related, dealings with\" the plaintiff for the purposeful\navailment analysis. 812 F.3d at 5. But, as we have explained,\nsee supra p.14, and as the dissent acknowledges, see Diss. Op. 44\nn.27, we are proceeding on the assumption in this case that the\ncontract and tort claims arise from the same alleged \"activity or\n. . . occurrence[] . . . in the forum State,\" Goodyear, 564 U.S.\nat 919, and thus we consider precisely the same set of contacts as\nto both claims. Accordingly, our purposeful availment analysis is\nprecisely the same as to both claims, nor does the plaintiff ask\nus to proceed otherwise.\n Thus, we must decide whether those contacts suffice to\nestablish a more substantial connection between the defendants and\nthe forum here than Copia found to be present there. In doing so,\nhowever, we do not thereby purport to address the merits of either\nthe contract or the tort claim, as our inquiry concerns only the\nlegal propriety of making Puerto Rico the forum jurisdiction for\nthe claims. And, with respect to that inquiry, the \"fairness\"\nconcern that matters relates not to how Puerto Rico defines its\ntort law, but to how the relevant precedents construe the Due\nProcess Clause to define purposeful availment.\n\n\n\n - 20 -\n\nCalifornia to PREP Tours in Puerto Rico in order to ask for a price\n\nquote and for what the company could \"offer\" as a proposed trip\n\nfor roughly sixty soccer players and their families. We can also\n\nagree that the defendants should have reasonably anticipated that\n\nsome action would be undertaken by PREP Tours in Puerto Rico in\n\nresponse to that inquiry -- such as replying with a proposed\n\nitinerary -- given that the defendants knew that PREP Tours was\n\nlocated there. And, finally, we can see no reason to doubt that\n\nsome foreseeable action was then actually undertaken by PREP Tours\n\nin Puerto Rico.\n\n But, even granting all that, as we will next explain,\n\nthe factors that we identified in Copia are not present here \"to\n\nremotely the same degree\" as they were in our other cases on which\n\nPREP Tours relies in arguing that the purposeful availment\n\nrequirement is met. Copia, 812 F.3d at 6. And, in light of that\n\nfact and our review of the relevant contacts as a whole, we\n\nconclude, as we did in Copia itself, that the in-forum plaintiff\n\ndid not meet its burden to satisfy the purposeful availment\n\nrequirement as to any of its claims.7\n\n\n 7\n In arguing that the purposeful availment requirement is\nsatisfied, PREP Tours asserts on appeal that the parties had forged\na contract because the defendants ultimately \"agreed on a final\nitinerary and cost . . . and agreed to proceed with the trip that\nPREP Tours had planned at the Defendants' request.\" But, in making\nthat conclusory assertion on appeal, PREP Tours does not develop\nany challenge to the District Court's ruling below in which the\n\n\n\n - 21 -\n\n 1.\n\n We start by considering the showing that PREP Tours made\n\nregarding the nature and quality of the defendants' activities in\n\nthe forum as they relate to the Copia factors. Those in-forum\n\ndefendant activities consist exclusively of the defendants' remote\n\ncommunications with PREP Tours concerning the trip.\n\n\n\n\nDistrict Court rejected PREP Tours's contention that the Region 24\ntreasurer's email with a third party -- Hakuna Matata -- could\nshow that a contract existed between PREP Tours and the defendants.\nNor does PREP Tours point on appeal to any non-conclusory\nallegation in the complaint (or the record) showing that a contract\ndid exist between the parties. See Soto-Torres v. Fraticelli, 654\nF.3d 153, 156 (1st Cir. 2011).\n Moreover, PREP Tours also does not develop any argument about\nhow the alleged contract bears on the purposeful availment inquiry\nas to the assertion of personal jurisdiction with respect to either\nthe contract or tort claims. For example, PREP Tours does not\nargue to us -- and did not argue below -- that purposeful availment\nexists due to services that the tour company would foreseeably\nprovide in the forum under the contract, or due to any other\n\"contemplated future consequences\" under the contract. Daynard,\n290 F.3d at 52 (quoting Burger King, 471 U.S. at 479). In fact,\nPREP Tours nowhere alleges -- either below or on appeal -- what\nthe terms of the purported contract even were. We have repeatedly\nmade clear, however, that an out-of-forum party's contract with an\nin-forum party is not in and of itself sufficient to establish\npersonal jurisdiction over the out-of-forum party, even where the\nplaintiff's claims include non-contract claims. See United States\nv. Swiss Am. Bank, Ltd., 274 F.3d 610, 621 (1st Cir. 2001) (quoting\nGanis Corp. of Cal. v. Jackson, 822 F.2d 194, 197-98 (1st Cir.\n1987)). Thus, PREP Tours's failure to develop any such argument\non appeal is problematic, insofar as PREP Tours means to contend\nthat the alleged contract alone enables PREP Tours to satisfy the\npurposeful availment requirement for its claims even if the other\ncontacts with Puerto Rico that it attributes to the defendants\n(and which the analysis that follows addresses) otherwise would\nnot suffice.\n\n\n\n - 22 -\n\n The communications began, the evidentiary submissions\n\nshow, when one of the Region 24 volunteers, Ramírez, asked PREP\n\nTours via email from California for a price quote and for what the\n\ncompany could \"offer\" regarding a potential trip by some of Region\n\n24's teams to Puerto Rico. The evidentiary submissions also show\n\nthat this same volunteer later asked via electronic means from\n\nCalifornia that PREP Tours modify the offer that she had earlier\n\nrequested in light of new specifications that she gave regarding\n\nthat potential trip.\n\n We cannot reasonably infer, however, from these\n\ncommunications alone that the defendants (a number of whom had no\n\ncontact directly with PREP Tours at all),8 or even Ramírez in\n\nparticular, believed themselves to be asking for the type of\n\ninformation that would require a self-described \"speciali[st]\" in\n\nsuch trips to engage in extensive trip-planning activities in the\n\nforum prior to an agreement being reached with the \"speciali[st].\"\n\nNor can we reasonably infer from these communications alone that\n\nthe purposeful availment requirement is met on the ground that\n\nthey show that the defendants were contemplating the kind of\n\n\n 8 As far as the evidentiary submissions indicate, over the\ncourse of the relevant four-month period, the two entity\ndefendants, AYSO and Region 24, had no direct communications with\nPREP Tours. Nor did Region 24's treasurer, Jackson. Region 24's\ncommissioner (Rodríguez) and assistant commissioner (Aguilar),\nmoreover, together sent only three emails to PREP Tours, all on\nthe same day, solely to apprise PREP Tours of the status of its\noffer in response to PREP Tours's own query.\n\n\n - 23 -\n\nongoing and close-working relationship with PREP Tours that could\n\nestablish the requisite substantial connection between the\n\ndefendants and the forum. See Cossart, 804 F.3d at 21; C.W.\n\nDowner, 771 F.3d at 67.\n\n Ramírez made clear in her initial inquiry email to PREP\n\nTours that no decision had even been made for the soccer teams to\n\ngo to Puerto Rico, as the email expressly stated that Region 24\n\nwas also gathering information about alternative destinations,\n\nlike Hawaii and Mexico. And, in her email replying to PREP Tours's\n\nresponse to that initial inquiry, Ramírez noted that \"[a]s soon as\n\n[Region 24's] decision is made, I will let you know,\" thereby\n\nreinforcing the preliminary nature of her inquiry and diminishing\n\nthe foreseeability of PREP Tours undertaking extensive in-forum\n\nactivities in response or the parties having an ongoing and close-\n\nworking relationship.\n\n PREP Tours's complaint does assert that PREP Tours\n\n\"continuously receiv[ed] requests by e-mail and telephone calls\"\n\nfrom Ramírez \"to amend different areas of the proposal in order to\n\naccommodate the needs of the group\" and that these requests\n\nresulted in \"multiple requirements\" with which PREP Tours's offer\n\nhad to comply.9 But, while communications of that type certainly\n\n\n 9 The complaint alleges that requests were also received\n\"later on\" from the Region 24 treasurer, Jackson. However, the\nonly communication by Jackson that PREP Tours's papers reference\nwas his email to the third-party travel agency located in Florida.\n\n\n - 24 -\n\ndo bear on the Copia factors of solicitation and anticipation, the\n\nproperly documented communications call into question PREP Tours's\n\ncharacterization of the nature of these communications. Instead,\n\nthe record shows only the following.\n\n Ramírez asked by email for PREP Tours to \"tweak\" -- her\n\nwording in the email -- the \"tentative rough draft\" itinerary that\n\nPREP Tours had initially sent, which resulted in what PREP Tours\n\ndescribed in an email to Ramírez as a \"new itinerary almost\n\nidentical to the original itinerary that we first sent you.\"10\n\nRamírez did so, moreover, while also informing PREP Tours that\n\nRegion 24 was contacting three alternative travel agencies for\n\ncompeting offers on the possible trip to Puerto Rico.\n\n The evidentiary submissions also show that Ramírez later\n\nsent an email asking whether PREP Tours could accommodate specific\n\ndates for a possible trip that incorporated the prior \"tweak\" along\n\n\n\n 10 The requested \"tweak\" was to include all-inclusive hotels,\ntwo to three matches per team, two to three excursions, free time\nfor families, and a cost of about $2,000 per person. PREP Tours\nrejected the request for all-inclusive hotels, explaining that it\nwould not be cost-effective. Thus, PREP Tours stuck with hotels\nthat it had already identified when it sent the original itinerary\nto Ramírez. The revised itinerary also did not list any additional\nlocal teams that would participate in the friendly soccer matches.\nFinally, the revised itinerary removed some activities that PREP\nTours had originally proposed while adding some additional\nactivities that Ramírez's email had not requested (such as a tour\nof a Bacardi rum plant). These changes reduced the estimated price\nrange from $1,495-$1,595 to $1,275-$1,375 per person without\nairfare.\n\n\n\n - 25 -\n\nwith arguably some minimal changes to it.11 But, Ramírez stated\n\nin that email once again that Region 24 had not yet decided on a\n\ntravel agency, though she did at that point state (for the first\n\ntime) that the trip would be to Puerto Rico.\n\n Finally, the record shows that, following this email\n\nfrom Ramírez, PREP Tours sent her a revised itinerary reflecting\n\nminimal changes and pushed Ramírez for more details about the\n\nnumber of persons who might be on the trip. And, as the record\n\nshows, Ramírez thereafter sent PREP Tours a one-line email\n\nattaching a document listing a \"breakdown of our team going to\n\nPuerto Rico,\" which consisted of some seventy names of players and\n\ncoaches.12\n\n But, in sending along that partial list of potential\n\ntravelers, Ramírez was responding to a request for information\n\nfrom PREP Tours. That is, Ramírez provided the partial list in\n\nresponse to a unilateral act by PREP Tours. Furthermore, in\n\nproviding that response, Ramírez did not state that Region 24 had\n\n\n 11 Ramírez inquired about specific dates for a ten-day trip\nthat -- roughly consistent with the earlier \"tweak\" she had already\nrequested that had resulted in the \"almost identical\" revised\nitinerary -- would consist of only three matches per team, include\nfree time, and cost no more than $2,000. The itinerary she\nreceived back from PREP Tours a week later removed or rendered\n\"optional\" some of the activities. The estimated price was $1,995\nper adult and $1,695 per child with airfare.\n 12Although the attached \"breakdown\" listed the names of only\nsome seventy players and coaches, it indicated that 252 people\nwould be on the trip.\n\n\n - 26 -\n\nmade a decision to book the trip through PREP Tours, nor did she\n\nmake any request of PREP Tours to take any actions in light of the\n\nlist that she had sent. In fact, in her last email to PREP Tours\n\nin the record, Ramírez communicated that Region 24's officers still\n\nhad \"to go through everything with a fine tooth-comb.\"\n\n Thus, as the District Court emphasized, PREP Tours's own\n\nevidentiary submissions show that, in the few substantive inquiry\n\nemails from Ramírez to PREP Tours -- out of what the defendants\n\nsay, without any challenge by PREP Tours, is \"a sum total of nine\"\n\nemails from her -- she consistently communicated the preliminary\n\nand limited nature of her inquiry.13 And, given that the nature\n\nand quality of the defendants' solicitation of in-forum activity\n\nwas preliminary and limited, the defendants' own forum-related\n\nactivity is a far cry from that of the defendants in C.W. Downer\n\nand Cossart, which are among the chief precedents of ours on which\n\nPREP Tours relies.14\n\n\n 13 Several, if not most, of the nine emails were sent in\nresponse to emails from PREP Tours itself simply in order to\nacknowledge the receipt of PREP Tours's messages. And, in the\nsubstantive emails among these nine, Ramírez referred to her\n\"delays\" in responding to PREP Tours's \"quote,\" further indicating\nthe intermittent nature of her communications.\n 14 We agree with the dissent that negotiations \"preliminary\"\nto a formal agreement are the foundation of a bad-faith tort claim.\nSee Diss. Op. 53. But, we highlight the preliminary nature of the\nparties' negotiations with respect to our analysis of purposeful\navailment as to both the tort and contract claims. And we do so\nnot to cast doubt on the merits of either of those claims but\ninstead because the preliminary nature of those contacts is\n\n\n\n - 27 -\n\n In C.W. Downer, for example, the out-of-forum defendant\n\nwas a Canadian corporation that had engaged an investment bank\n\nlocated in Massachusetts to sell the corporation, which the\n\ninvestment bank then spent four years trying to do before the deal\n\nfell apart and the investment bank sued the corporation in\n\nMassachusetts. 771 F.3d at 67. And, in Cossart, the out-of-forum\n\ndefendant was a firm based in Kansas that had hired an employee\n\nlocated in Massachusetts to work for the firm, which the employee\n\ndid for a \"period of years\" before suing the employer in\n\nMassachusetts for wage law violations. 804 F.3d at 18.\n\n Of course, neither C.W. Downer nor Cossart purported to\n\nestablish the minimum connection to the forum that must be shown\n\nto establish personal jurisdiction. But, none of our other cases\n\non which PREP Tours relies supports the proposition that an out-\n\nof-forum defendant would foresee being haled into court in that\n\nforum on the basis of having made the preliminary and limited type\n\n\n\ndirectly relevant to the component of the purposeful availment\ninquiry that requires us to assess whether the in-forum actions\nthat PREP Tours took in response to the defendants' contacts were\n\"foreseeable\" to the defendants or were instead \"unilaterally\"\nundertaken by the plaintiff itself. Moreover, the preliminary\nnature of contacts is also directly relevant to PREP Tours's\ncontention that the contacts show that the defendants contemplated\nan ongoing relationship with PREP Tours and that there was in fact\nsuch a relationship. In this regard, our concern is not with\nwhether the conduct alleged is tortious, but with whether that\nconduct is of a type that permits the forum to be the jurisdiction\nin which that determination is made.\n\n\n\n - 28 -\n\nof information requests to a forum-based service provider that\n\nwere made here.15 Nor are we aware of any such supporting\n\nauthority.\n\n In fact, this case in some respects provides even less\n\nbasis for finding the requisite \"substantial connection\" to the\n\nforum than did Copia, in which we found no purposeful availment.\n\n812 F.3d at 5-6. There, we rejected the contention that a Jamaica-\n\nbased resort operator purposefully availed itself of the privilege\n\nof conducting activities in Massachusetts as a result of the\n\nnegotiation and performance of a contract between the resort\n\noperator and a Massachusetts-based internet services provider.\n\nSee id. We did so even though the resort operator had voluntarily\n\nnegotiated with the provider remotely, including via emails that\n\nthe chief executive officer of the Massachusetts-based internet\n\nservices provider \"may have sent or received . . . while in\n\n\n 15\n See, e.g., Baskin-Robbins Franchising LLC v. Alpenrose\nDairy, Inc., 825 F.3d 28, 36-40 (1st Cir. 2016) (finding purposeful\navailment where an out-of-forum franchisee twice renewed its\ncontract with an in-forum franchisor, with which it had a multi-\nyear business relationship and to which it mailed 180 royalty\nchecks and delivered quarterly samples of its product); Adelson,\n652 F.3d at 79, 82-83 (finding purposeful availment where an out-\nof-forum employee \"directed regular administrative and financial\nconduct\" toward his employer's offices in the forum during multiple\nyears of employment, after he had sought out the employment\ncontract); Daynard, 290 F.3d at 46, 61-62 (finding purposeful\navailment in part because of an out-of-forum law firm's \"properly\nattributed\" \"ongoing relationship\" with an in-forum lawyer who was\nallegedly \"central\" to the firm's \"titanic recoveries\" in a complex\nlitigation).\n\n\n\n - 29 -\n\nMassachusetts\" and via meetings in Jamaica. Id. at 2-3.16 And,\n\nwe did so even though, under the contract that the parties\n\neventually concluded, in addition to providing certain services in\n\nJamaica, the provider shipped equipment from Massachusetts to the\n\nresort operator in Jamaica. Id. at 3.\n\n We explained that the resort operator's anticipation of\n\nthe \"provi[sion of] equipment and services\" by a party known to be\n\nin Massachusetts did not \"represent[] the type of purposeful\n\navailment of the privilege of conducting business in Massachusetts\n\nthat would have made it reasonably foreseeable that [the out-of-\n\nforum company] could be 'haled into court' in Massachusetts[.]\"\n\nId. at 6 (quoting Burger King, 471 U.S. at 486).17 And, in so\n\nconcluding, we emphasized that there was \"no evidence that the\n\n[resort operator] cared about the geographic origin of the\n\n\n\n\n 16\n The district court's opinion in Copia, which reviewed the\nevidentiary record in detail, noted that the Chief Executive\nOfficer of the Massachusetts-based internet services provider\n\"received emails in the course of the negotiations (and later the\nrelationship) some of which he may have read at Copia's principal\nplace of business in Massachusetts.\" Copia Commc'ns, LLC v.\nAmresorts, LP, No. 14-13056, 2015 WL 7621480, at *1 (D. Mass. Feb.\n5, 2015). And, as the District Court noted, the Chief Executive\nOfficer represented that, \"[o]n occasion, communications via\ntelephone or e-mail were sent and received while [the Chief\nExecutive Officer] was in Massachusetts.\" Id. at *3.\n 17The resort operator knew that the internet services\nprovider was based in Massachusetts because it \"addressed payment\nto [the internet services provider's] Massachusetts address.\"\nCopia, 812 F.3d at 3.\n\n\n - 30 -\n\nshipments\" of the equipment for which the resort operator had\n\ncontracted. Id. at 5.\n\n PREP Tours does assert on appeal that Ramírez reached\n\nout to PREP Tours specifically because it could undertake \"local\n\nefforts\" in Puerto Rico (as opposed to, say, the fact that it\n\nspecialized in soccer trips to that locale). But, the tour company\n\nneither alleges such in its complaint nor points to any evidence\n\nin the record to support this assertion. In fact, the record shows\n\nthat Region 24 contacted multiple travel agencies, not all of which\n\nwere located in Puerto Rico, and that Region 24 ultimately procured\n\na California-based travel agency to book its trip to Puerto Rico.18\n\n To be sure, as PREP Tours points out, one of the\n\ndefendants, Ramírez, initiated the contact with the in-forum\n\nparty, PREP Tours. And that was not the case in Copia. There,\n\nthe in-forum plaintiff initiated the negotiations that we found\n\ninsufficient to demonstrate purposeful availment there. See id.\n\nat 6. But, negotiations involving numerous contacts between the\n\nparties -- some made in the forum -- to secure an ongoing services\n\nrelationship there did then ensue. In that respect, we do not\n\n\n\n 18 PREP Tours does suggest on appeal that the defendants\nprocured this California-based company's services only after\n\"misstat[ing] their intentions to PREP Tours to enable them to get\nthe benefit of PREP Tours' local efforts.\" But, that assertion\ndoes little to show purposeful availment on the defendants' part,\nas that inquiry still turns on whether the defendants anticipated\nthat PREP Tours would undertake \"local efforts.\"\n\n\n - 31 -\n\nthink that the out-of-forum party in Copia had less substantial\n\ncontacts over the course of the relationship with the in-forum\n\nparty than the defendants did in this case.\n\n Moreover, the Supreme Court made clear in Kulko that\n\neven where it is the out-of-forum defendant who voluntarily and\n\nknowingly establishes some contacts with the forum, specific\n\njurisdiction over the defendant may still be lacking if the\n\nprospect of in-forum litigation was not foreseeable in light of\n\nthe nature and quality of that contact with the forum. See 436\n\nU.S. at 94, 97-98. And, given the preliminary and limited nature\n\nand quality of that initial inquiry to PREP Tours from Ramírez and\n\nof the defendants' other ensuing communications with the tour\n\ncompany, we conclude that this one feature of the case does not\n\nsuffice to support the conclusion that the defendants' activities\n\nestablished a \"substantial connection\" between the defendants and\n\nthe forum. Burger King, 471 U.S. at 475; cf. Sandstrom v. ChemLawn\n\nCorp., 904 F.2d 83, 89 (1st Cir. 1990) (holding that general\n\njurisdiction was lacking over an out-of-forum defendant that was\n\nlicensed to do business in the forum and had engaged in non-\n\nsubstantial advertising in the forum, and explaining that\n\n\"preparations to do business at an indeterminate future date,\n\nwithout more, cannot be confused with actually doing business\").\n\n\n\n\n - 32 -\n\n 2.\n\n PREP Tours contends, however, that, to assess purposeful\n\navailment, we must consider not only the defendants' own\n\nactivities, as reflected in the defendants' remote communications\n\nwith PREP Tours, but also the \"extensive\" activities that the tour\n\ncompany undertook in response. And we agree, consistent with\n\nCopia's recognition of the import of the factors of anticipation\n\nand performance.\n\n But, we conclude, consideration of PREP Tours's own\n\nactivities, even in combination with those undertaken by the\n\ndefendants, does not require a different conclusion from the one\n\nthat the District Court reached as to purposeful availment. And\n\nthat is both because of what the record shows about the actual\n\nactivities PREP Tours undertook and because those activities must\n\nbe considered in light of the nature of the communications that\n\nthe defendants made prior to PREP Tours having undertaken those\n\nactivities. See Burger King, 471 U.S. at 474 (\"The unilateral\n\nactivity of those who claim some relationship with a nonresident\n\ndefendant cannot satisfy the requirement of contact with the forum\n\nState.\" (quoting Hanson, 357 U.S. at 253)).\n\n In its brief on appeal, PREP Tours asserts that, in\n\nresponding to the defendants' inquiries regarding the possible\n\ntrip, it foreseeably undertook \"dozens of contacts\" in the forum\n\non the defendants' behalf that should be attributed to the\n\n\n - 33 -\n\ndefendants for jurisdictional purposes. According to PREP Tours's\n\nbrief, those contacts include \"contacting Puerto Rico-based\n\nhotels, restaurants, soccer teams, business owners, and travel\n\nagents.\"\n\n PREP Tours's complaint, however, does not allege that\n\nPREP Tours contacted a single other business, soccer team, or any\n\nperson who did not work for PREP Tours in response to the\n\ndefendants' inquiry.19 See Doyle v. Hasbro, Inc., 103 F.3d 186,\n\n190 (1st Cir. 1996) (\"In conducting our review of the case, we are\n\nlimited to those allegations contained in the amended\n\ncomplaint.\"). Nor did PREP Tours expressly rely below on any such\n\ncontacts by the tour company in its argument to the District Court\n\nthat there was personal jurisdiction over the defendants. Cf.\n\nMcCoy v. Massachusetts Inst. of Technology, 950 F.2d 13, 22 (1st\n\nCir. 1991) (\"It is hornbook law that theories not raised squarely\n\n\n\n 19 The dissent concludes that we may infer that \"each new\nitinerary involved re-engaging with service providers to discuss\nnew costs and timing (including booking hotels and flights)[.]\"\nDiss. Op. 51. But, we do not see how we may make such an inference\nwhen the plaintiff's own complaint does not make any allegation\nthat it engaged with any service providers in response to the\ndefendants' requests, let alone any allegation that they re-\nengaged with them every time the defendants made a new request.\nThe absence of such allegations from the complaint is especially\nconspicuous given that they concern the plaintiff's own conduct.\nSee Gianfrancesco v. Town of Wrentham, 712 F.3d 634, 639-40 (1st\nCir. 2013) (upholding dismissal of claims where there was \"no\nsuggestion\" that the \"missing facts should be beyond [plaintiff's]\nreach\" or that the plaintiff \"lack[ed] the information needed to\"\nallege such facts).\n\n\n - 34 -\n\nin the district court cannot be surfaced for the first time on\n\nappeal.\").\n\n PREP Tours's evidentiary submissions do show, as its\n\ncomplaint alleges, that it sent Ramírez a \"tentative rough draft\"\n\nitinerary from Puerto Rico a few days after she made her initial\n\ninquiry about the trip and that PREP Tours then modified the\n\nitinerary in some respects while in Puerto Rico. In that regard,\n\nthe properly documented actions that PREP Tours undertook in the\n\nforum in response to the defendants' inquiry were not entirely\n\n\"unilateral,\" as the District Court suggested.\n\n But, even accepting that point, we do not see how we may\n\nreasonably infer from the showing that PREP Tours makes regarding\n\nthe itinerary that it foreseeably undertook the kind of \"extensive\"\n\nactivities in response to Ramírez's remote communications that the\n\ntour company asserts on appeal that it undertook in order to put\n\ntogether and modify this proposal. After all, the promotional\n\nbrochure that PREP Tours sent to Ramírez on the very day that she\n\nfirst inquired for an offer described a pre-existing \"unique soccer\n\nprogram\" based in San Juan and Rincón that PREP Tours offered to\n\nvisiting youth soccer teams.\n\n The record does also show that PREP Tours then sent\n\nRamírez a \"tentative rough draft\" itinerary a few days later. But,\n\nthe record does not show (nor does the complaint allege) what work\n\nin Puerto Rico was done by PREP Tours in order to put together\n\n\n - 35 -\n\nthat itinerary or that there is a basis for inferring that the\n\ndefendants anticipated that PREP Tours would on the basis of their\n\ninitial request for information engage in extensive in-forum\n\nactivity.\n\n Nor, as far as the record reveals, did PREP Tours add\n\nany newly identified hotels, restaurants, or local soccer teams to\n\nthat \"tentative rough draft\" of the itinerary over the course of\n\nthe ensuing months.20 In fact, in an email to Ramírez after the\n\nlargest, albeit still quite modest, round of documented changes to\n\nthe \"tentative rough draft\" itinerary, PREP Tours itself called\n\n\"the new itinerary almost identical to the original itinerary that\n\nwe first sent you.\"\n\n We also cannot reasonably infer that the defendants\n\ncould have foreseen the type of \"extensive\" activities that PREP\n\nTours asserts to us on appeal that it undertook beyond the sending\n\nof a pre-existing tentative itinerary. PREP Tours's evidentiary\n\nsubmissions do show in this regard that the tour company sent an\n\nemail to Ramírez that mentions that it had contacted hotels in\n\nPuerto Rico after Ramírez had reached out to the tour company and\n\nthat these hotels then placed courtesy holds on certain rooms. In\n\naddition, we can reasonably infer from the email that Hakuna\n\n\n 20 The dissent states that PREP Tours \"proceeded to make\nconcrete arrangements with other businesses, including flight and\nhotel reservations.\" Diss. Op. 52. But, the complaint itself\nmakes no such allegation.\n\n\n - 36 -\n\nMatata, the third-party travel agency in Florida, sent to the\n\ndefendants regarding possibly arranging flights for them that PREP\n\nTours had at some point contacted Hakuna Matata from within Puerto\n\nRico to ask Hakuna Matata to do so.21 But, the record does not\n\nshow that the defendants had actually requested that PREP Tours\n\narrange for the courtesy holds on the hotel rooms. Rather, the\n\nrecord reveals that the defendants asked only in general and\n\ntentative terms about what PREP Tours, which represents itself as\n\na \"speciali[st]\" in such soccer tours, could \"offer.\"\n\n In fact, the record does not show that the defendants\n\never asked PREP Tours to contact any entity or person in Puerto\n\nRico on their behalf. Nor does the record show that they ever\n\nrequested any particular hotel, restaurant, soccer team, or\n\nbusiness to be included in the proposed itinerary.22 And we see\n\nno basis for concluding -- nor does PREP Tours appear to even argue\n\n-- that the defendants should \"reasonably have anticipated being\n\n'haled before a [Puerto Rico] court'\" simply in consequence of\n\n\n\n 21PREP Tours had at one point also emailed Ramírez a menu of\npossible flights, but PREP Tours acknowledged in a later email\nthat it did not book any flights on AYSO's behalf because it did\nnot yet have a sufficient indication from AYSO that the\norganization wished to proceed with the flights.\n 22 The record does show that in her email requesting a \"tweak\"\nto the \"tentative rough draft\" itinerary, Ramírez asked if it would\nbe possible to include \"all-inclusive hotels.\" PREP Tours\nexpressly rejected that request, however, explaining that it would\nnot be cost-effective to stay in all-inclusive hotels.\n\n\n - 37 -\n\nPREP Tours's efforts to obtain preliminary information about the\n\ncost and availability of hotels in Puerto Rico for the trip's\n\npossible dates, or its efforts to contact a travel agency located\n\noutside the forum regarding possible flights. Kulko, 436 U.S. at\n\n97-98 (quoting Shaffer v. Heitner, 433 U.S. 186, 216 (1977)).\n\n PREP Tours does assert in its appellate brief that AYSO\n\nhad taken similar cultural immersion trips in the past. PREP Tours\n\nthus reasons that the defendants should have reasonably foreseen\n\nthe extent of activities in Puerto Rico that would have been\n\nnecessary to produce a proposed itinerary for such a trip.23 But,\n\nwe cannot see how it would be reasonable to infer from the mere\n\nfact of this past experience that the organization would foresee\n\nthat a tour company that \"specializes\" in such trips would\n\nundertake \"extensive\" activities in Puerto Rico simply to prepare\n\na price quote and proposed itinerary for its regularly offered\n\nservice in response to a preliminary request for that information\n\nfrom a group that consistently made clear that it was considering\n\nusing other travel agencies.\n\n For all of these reasons, this case is not at all like\n\nthe imputed-contacts cases on which PREP Tours relies, namely C.W.\n\nDowner and Cossart. In C.W. Downer, the out-of-forum defendant\n\n\n 23\n Although the complaint does not allege that AYSO took\nsimilar trips in the past, one of Ramírez's emails in the record\nindicates that AYSO's teams had traveled to Costa Rica and Hawaii\nin prior years.\n\n\n - 38 -\n\ncorporation had specifically engaged the in-forum investment bank\n\nto sell the company, thus making foreseeable the fact that the\n\nbank \"contacted hundreds of potential buyers on [the\n\ncorporation's] behalf.\" 771 F.3d at 67. Likewise, in Cossart,\n\nthe out-of-forum firm had hired the employee to do the kind of\n\nwork that would make it foreseeable that he would have \"made\n\nhundreds of telephone calls and sent hundreds of e-mails on behalf\n\nof [the employer]\" from the forum. 804 F.3d at 17.\n\n Again, neither of those cases purports to set the minimum\n\nthreshold for establishing personal jurisdiction on the basis of\n\nthe activities of an in-forum plaintiff that may be imputed to an\n\nout-of-forum defendant. But, PREP Tours identifies no other\n\nprecedents that would support the conclusion that, given the\n\ncontext in which the inquiry about the trip was made, the tour\n\ncompany's properly documented activities that reasonably may be\n\nattributed to the defendants are of a nature and quality to show\n\nthat they should have reasonably anticipated being haled into court\n\nin Puerto Rico as a result. Nor, we note, does the dissent.\n\n V.\n\n Questions of purposeful availment are often, like those\n\npresented here, necessarily fact-dependent. In this area, as the\n\nSupreme Court has cautioned, there are no mathematical formulas\n\nupon which to rely. And the hues are more \"grey[]\" than \"black\n\nand white.\" See Kulko, 436 U.S. at 92 (quoting Estin, 334 U.S. at\n\n\n - 39 -\n\n545). But, in light of Copia, and the other precedents bearing on\n\nthese questions, we conclude that on this record -- especially\n\ngiven that what is missing consists of information fully known to\n\nthe in-forum party asserting jurisdiction -- there is no basis for\n\nfinding the purposeful availment requirement met for either of the\n\nplaintiff's claims.\n\n The judgment of the District Court is affirmed.\n\n\n\n - Dissenting Opinion Follows -\n\n\n\n\n - 40 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357014/", "author_raw": "BARRON, Circuit Judge"}, {"author": "LIPEZ, Circuit Judge, dissenting", "type": "dissent", "text": "LIPEZ, Circuit Judge, dissenting. In concluding that\n\nthe federal court in Puerto Rico lacks personal jurisdiction over\n\nthe defendants in this case, the majority downplays the\n\nsignificance of the bad-faith negotiations claim and fails to view\n\nthe facts alleged in the light most favorable to the plaintiff.\n\nProperly evaluated, however, those facts establish the elements of\n\npersonal jurisdiction for PREP Tours' lawsuit against three of the\n\ndefendants.24 Given these circumstances, I cannot join my\n\ncolleagues in affirming dismissal of PREP Tours' complaint.\n\n I.\n\nA. Overview\n\n My disagreement with the majority stems primarily from\n\ntheir depiction of the facts proffered by PREP Tours in support of\n\njurisdiction.25 In brief summary, defendants asked PREP Tours to\n\n\n 24I agree that dismissal is proper for Armando Rodríguez,\nRamón Aguilar, and Carl Jackson, but conclude that the case should\nproceed against the American Youth Soccer Organization (\"AYSO\"),\nits regional affiliate (\"Region 24\"), and a Region 24 volunteer,\nAlicia Ramírez (collectively, \"defendants\"). For simplicity, I\nassume that Ramírez was an agent of AYSO and Region 24 and, thus,\nthat these three defendants are in the same position vis-à-vis\nPREP Tours.\n 25\n The district court chose the \"prima facie\" method -- \"the\nleast taxing\" standard for a plaintiff -- to determine whether\nPREP Tours had met its personal jurisdiction burden. Phillips v.\nPrairie Eye Ctr., 530 F.3d 22, 26 (1st Cir. 2008) (quoting\nRodriguez v. Fullerton Tires Corp., 115 F.3d 81, 83 (1st Cir.\n1997)). In line with that method, the facts on which I rely are\ndrawn from PREP Tours' complaint and the supplemental materials\ncontained in the record. See Baskin–Robbins Franchising LLC v.\nAlpenrose Dairy, Inc., 825 F.3d 28, 34 (1st Cir. 2016) (noting\n\n\n\n - 41 -\n\nplan a soccer tour in Puerto Rico for more than 250 people. Then,\n\non the brink of formalizing an agreement based on PREP Tours'\n\nconsiderable efforts, defendants made a last-minute switch to a\n\ndifferent tour company. Contrary to my colleagues' depiction of\n\nthe parties' relationship as undeveloped and \"preliminary,\" the\n\nrecord demonstrates an increasingly solid commitment by defendants\n\nto do business with PREP Tours. Defendants' sudden abandonment of\n\nPREP Tours after the company invested substantial resources to\n\ncreate defendants' desired itinerary permits a plausible inference\n\nof bad faith, a key component of PREP Tours' contention that it\n\nwas harmed by defendants' actions.\n\nB. Culpa in Contrahendo\n\n Under Puerto Rico law, the obligation to negotiate\n\ncontracts in good faith is known as the culpa in contrahendo\n\ndoctrine. See Advanced Flexible Circuits, Inc. v. GE Sensing &\n\nInspection Techs. GmbH, 781 F.3d 510, 516 (1st Cir. 2015). The\n\ndoctrine varies from the common law requirement of good-faith\n\nnegotiation not only because it sounds in tort rather than\n\ncontract, but also because it encompasses a broader range of\n\n\n\nthat when conducting a personal jurisdiction analysis under the\nprima facie standard, a court must \"take the facts from the\npleadings and whatever supplemental filings (such as affidavits)\nare contained in the record\"); see also Sawtelle v. Farrell, 70\nF.3d 1381, 1385-86 (1st Cir. 1995) (explaining that in assessing\na motion to dismiss based on lack of personal jurisdiction, the\ncourt may consider supplemental materials such as affidavits).\n\n\n - 42 -\n\nconduct. See Ysiem Corp. v. Commercial Net Lease Realty, Inc.,\n\n328 F.3d 20, 24 (1st Cir. 2003). In general, the culpa in\n\ncontrahendo doctrine is \"used to compensate a party for the\n\nexpenses it incurred in reliance on the other party's offer to\n\nform a contract when the contract negotiations break down.\"\n\nVelázquez Casillas v. Forest Labs., Inc., 90 F. Supp. 2d 161, 166\n\n(D.P.R. 2000). We have explained that \"[a] party's withdrawal\n\nfrom contractual negotiations may be considered a violation of the\n\nduty of good faith if: (1) the withdrawal was arbitrary or without\n\njustification; and (2) the other party had a reasonable expectation\n\nthat a contractual agreement would be consummated.\" Advanced\n\nFlexible Circuits, 781 F.3d at 516-17.26\n\n PREP Tours' complaint alleges a classic instance of\n\nfrustrated expectations, with defendants taking the parties'\n\nnegotiations to the brink of a formal agreement before pulling\n\n\n\n 26\n Some jurisdictions have similarly found a duty to negotiate\nin good faith after the parties have negotiated important terms in\na potential contract but other terms remain open. See, e.g.,\nFlight Sys., Inc. v. Elec. Data Sys. Corp., 112 F.3d 124, 130 (3d\nCir. 1997) (Pennsylvania); Sunnyside Cogeneration Assocs. v. Cent.\nVt. Pub. Serv. Corp., 915 F. Supp. 675, 680 (D. Vt. 1996); Teachers\nIns. & Annuity Ass'n of Am. v. Tribune Co., 670 F. Supp. 491, 498\n(S.D.N.Y. 1987); Markov v. ABC Transfer & Storage Co., 457 P.2d\n535, 539-40 (Wash. 1969). Moreover, other jurisdictions have\nacknowledged some pre-contractual liability when the parties\nstarted negotiations toward a contract but for some reason an\nagreement could not be reached. See, e.g., Chrysler Corp. v.\nQuimby, 144 A.2d 123, 128-29 (Del. 1958); Hoffman v. Red Owl\nStores, Inc., 133 N.W.2d 267, 274-75 (Wis. 1965).\n\n\n\n - 43 -\n\nout. The culpa in contrahendo tort claim must thus be at the fore\n\nof the evaluation of personal jurisdiction.27 Cf. Copia Commc'ns,\n\nLLC v. AMResorts, L.P., 812 F.3d 1, 4 n.2 (1st Cir. 2016) (noting\n\nthat \"[b]ecause all of [plaintiff]'s claims are entwined in its\n\ncontract claims, none demands separate analysis\").\n\n II.\n\n As the majority opinion sets out, the constitutional\n\ninquiry for specific personal jurisdiction consists of three\n\nprongs: relatedness, purposeful availment, and reasonableness.\n\nSee Daynard v. Ness, Motley, Loadholt, Richardson & Poole, P.A.,\n\n290 F.3d 42, 60 (1st Cir. 2002); Phillips Exeter Acad. v. Howard\n\nPhillips Fund, 196 F.3d 284, 288 (1st Cir. 1999).28 The majority\n\nconsiders only the purposeful availment prong and, concluding that\n\n\n\n 27\n By focusing on the tort claim, I am not suggesting that the\npurposeful availment analysis varies from cause of action to cause\nof action when the same contacts are asserted as the basis for\npersonal jurisdiction. Nonetheless, \"[q]uestions of specific\njurisdiction are always tied to the particular claims asserted,\"\nPhillips Exeter Acad. v. Howard Phillips Fund, 196 F.3d 284, 289\n(1st Cir. 1999), and \"the quality and nature of the defendant's\nactivity\" is part of the calculus, Harlow v. Children's Hosp., 432\nF.3d 50, 58 (1st Cir. 2005) (quoting Hanson v. Denckla, 357 U.S.\n235, 253 (1958)). I highlight the bad-faith claim because -- given\nthe nature of defendants' contacts with PREP Tours -- the tort\nclaim reveals so clearly the error in the majority's purposeful\navailment analysis and the unfairness of the outcome.\n 28Where a state's long-arm statute extends to the\nconstitutional limit, as in Puerto Rico, we may address the\nstatute's requirements by conducting the constitutional due\nprocess analysis. See Dalmau Rodriguez v. Hughes Aircraft Co.,\n781 F.2d 9, 12 (1st Cir. 1986).\n\n\n - 44 -\n\nit does not support personal jurisdiction, does not address the\n\nother two prongs. Accordingly, I, too, primarily focus on\n\npurposeful availment.\n\n The purposeful availment inquiry requires us to\n\ndetermine whether the defendants have targeted their conduct\n\n\"toward the society or economy of a particular forum [such that]\n\nthe forum should have the power to subject the defendant to\n\njudgment regarding that behavior.\" Baskin-Robbins Franchising LLC\n\nv. Alpenrose Dairy, Inc., 825 F.3d 28, 36 (1st Cir. 2016) (quoting\n\nCarreras v. PMG Collins, LLC, 660 F.3d 549, 555 (1st Cir. 2011))\n\n(alteration in original). This assessment ensures that personal\n\njurisdiction is not premised solely on defendants' \"'random,\n\nisolated or fortuitous contacts' with the forum state.\" Adelson\n\nv. Hananel, 510 F.3d 43, 50 (1st Cir. 2007) (quoting Sawtelle v.\n\nFarrell, 70 F.3d 1381, 1391 (1st Cir. 1995)).\n\n The \"cornerstones\" of purposeful availment are\n\nvoluntariness and foreseeability. Daynard, 290 F.3d at 61 (quoting\n\nSawtelle, 70 F.3d at 1391). Voluntariness means that a defendant's\n\n\"contacts with the forum state 'proximately result from actions by\n\nthe defendant himself.'\" Phillips v. Prairie Eye Ctr., 530 F.3d\n\n22, 28 (1st Cir. 2008) (quoting Burger King Corp. v. Rudzewicz,\n\n471 U.S. 462, 475 (1985)). Foreseeability means that \"the\n\ndefendant's conduct and connection with the forum state are such\n\n\n\n\n - 45 -\n\nthat he should reasonably anticipate being haled into court there.\"\n\nWorld-Wide Volkswagen Corp. v. Woodson, 444 U.S. 286, 297 (1980).\n\n The majority relies heavily on our decision in Copia,\n\n812 F.3d at 5-6, in concluding that defendants' actions in dealing\n\nwith PREP Tours are insufficient to satisfy the purposeful\n\navailment requirement. Given Copia's importance to the majority's\n\nanalysis, describing the case in some detail helps to explain why\n\nour court's rejection of personal jurisdiction there does not\n\ncontrol the outcome here.\n\n In Copia, the plaintiff was a Massachusetts company that\n\nbrought suit in Massachusetts against a Jamaican resort operator\n\nand its Pennsylvania alter ego for an alleged breach of contract.\n\nThe Jamaican company had virtually no connection with\n\nMassachusetts. The negotiations between the parties were\n\ninitiated by the plaintiff, not the defendant -- i.e., the parties'\n\nrelationship began with the Massachusetts plaintiff reaching out\n\nto the defendant in Jamaica. The contract at issue was for\n\nservices to be performed in Jamaica, with Jamaican employees, and\n\nunder Jamaican law. The defendant's only Massachusetts contacts\n\nconsisted of sending a few emails to plaintiff's CEO in\n\nMassachusetts and receiving equipment shipped from there.\n\n Unsurprisingly, the Copia panel held that the Jamaican\n\nresort could not be haled into court in Massachusetts to defend\n\nthe breach of contract claim. Copia, 812 F.3d at 6. Drawing on\n\n\n - 46 -\n\nearlier precedents of our court, we noted three factors as relevant\n\nto purposeful availment: \"the defendant's in-forum solicitation of\n\nthe plaintiff's services, the defendant's anticipation of the\n\nplaintiff's in-forum services, and the plaintiff's actual\n\nperformance of extensive in-forum services.\"29 Id. The panel\n\nfound that the plaintiff failed to satisfy any of the three\n\nfactors. First, the Jamaican resort had not solicited services\n\nfrom the plaintiff; rather, the plaintiff had contacted the resort.\n\nSecond, the Jamaican resort would not have anticipated that\n\nservices under the contract would be performed in Massachusetts\n\ngiven that the contract was for services to be performed in\n\nJamaica. Third, the services under the contract were actually\n\nperformed in Jamaica, excepting some \"insubstantial contacts that\n\nanyone would have when buying goods and services from a company\n\nthat itself happens to be in Massachusetts.\" Id.30\n\n\n\n 29 These factors were previously applied in two cases where\nthe out-of-forum defendants' contacts occurred primarily through\nremote communications. See Cossart v. United Excel Corp., 804\nF.3d 13, 21 (1st Cir. 2015); C.W. Downer & Co. v. Bioriginal Food\n& Sci. Corp., 771 F.3d 59, 66-67 (1st Cir. 2014). Although the\nfocus on these factors may not be suited for all remote\ncommunications cases -- particularly where the plaintiff's claims\nsound primarily in tort -- focusing on them here is appropriate to\nhighlight the differences between my view of the facts and the\nmajority's view.\n 30Although some equipment was shipped from Massachusetts, the\ncontract did not require shipment from any particular location.\nSee Copia, 812 F.3d at 5.\n\n\n\n - 47 -\n\n Here, by contrast, there are far more substantial\n\nconnections between defendants and the forum. Indeed, applying\n\nthe Copia factors to the facts of this case reveals the error in\n\nthe majority's analysis.31\n\nA. Solicitation of plaintiff's services\n\n It is difficult to imagine a more clear-cut instance of\n\nan out-of-forum defendant voluntarily and directly soliciting an\n\nin-forum plaintiff's services. In November 2012, defendants\n\ncommenced a four-month period of communications with PREP Tours,\n\ninitially seeking information about options available in Puerto\n\nRico for their soccer group's possible tour. PREP Tours first\n\nresponded with a standard promotional brochure describing a youth\n\nsoccer program available in Puerto Rico. Defendants' initial\n\ninquiry unquestionably was preliminary -- it did not even identify\n\nPuerto Rico as the confirmed destination -- and PREP Tours'\n\nresponse likewise involved no individualized effort on behalf of\n\ndefendants. However, even though defendants' initial contact\n\nmerely opened the door to a possible business relationship with\n\n\n\n 31 The majority also contrasts the facts here with the two\nprimary cases on which PREP Tours relies to argue that personal\njurisdiction is appropriate: Downer, 771 F.3d at 67, and Cossart,\n804 F.3d at 21. As the majority acknowledges, however, Downer and\nCossart do not \"purpor[t] to establish the minimum connection to\nthe forum that must be shown to establish personal jurisdiction.\"\nHence, I see no need to compare the facts here with those cases to\nshow that PREP Tours has shown the requisite connection.\n\n\n\n - 48 -\n\nPREP Tours in Puerto Rico, that first step acquired greater\n\nsignificance when the defendants subsequently started to solidify\n\ntheir plans with PREP Tours for a trip to Puerto Rico. Without\n\nquestion, Copia's solicitation prong is satisfied.\n\nB. Defendants' anticipation of in-forum services and plaintiff's\nactual performance of in-forum services32\n\n The parties' relationship progressed rapidly after\n\ndefendants' initial inquiry. PREP Tours prepared a proposed\n\nitinerary, and the parties thereafter engaged in an exchange of\n\nemails in which defendants requested changes, PREP Tours responded\n\nwith revisions, and the agency reserved hotels and flights. In\n\ntheir first round of requests, defendants asked PREP Tours to\n\nschedule two or three soccer games, two or three excursions for\n\nplayers and parents, and \"free time for families to go on their\n\nown,\" all while keeping the cost to $2,000 per person, including\n\nairfare. PREP Tours complied and sent a revised itinerary to\n\ndefendants.\n\n Unsatisfied with the revised itinerary, defendants\n\nrequested further modifications and specifications in late\n\nDecember 2012, including: (1) extending the length of the trip and\n\nscheduling it for July 8-18, with specific arrival and departure\n\ndates for various components of the tour; (2) scheduling three\n\n\n\n 32The second and third Copia factors substantially overlap,\nand I will therefore analyze them together.\n\n\n - 49 -\n\nlocal soccer games (i.e., specifying three, rather than possibly\n\ntwo, games); (3) and, again, directing that the overall cost of\n\nthe trip remain at or below $2,000 per person. PREP Tours again\n\ncomplied, producing a third itinerary. Meanwhile, as PREP Tours\n\nworked to accommodate defendants' requests, defendants expressed\n\nsatisfaction with PREP Tours' efforts and an intention to move\n\nforward with the trip arranged by PREP Tours. Defendants stated\n\nin a December email that they \"loved [PREP Tours'] itinerary as\n\nopposed to [another] agency\" and wanted to \"seal the deal\" so that\n\nthe parents could start \"pay[ing] the agency.\"\n\n Any remaining doubt about defendants' commitment to PREP\n\nTours was dispelled by the parties' communications in January 2013.\n\nDefendants sent PREP Tours a list of trip participants with ages\n\nand desired hotel accommodations. One of defendants' last emails\n\nto PREP Tours stated that AYSO's Region 24 board members would be\n\ncontacting PREP Tours \"for the financial part\" and that, barring\n\nany \"red flags,\" everything was going to \"run smoothly.\" In a\n\nseparate email thread, Hakuna Matata, the travel agency engaged by\n\nPREP Tours, contacted defendants seeking payment for the reserved\n\nflights.\n\n Given these interactions, defendants had to understand\n\nthat PREP Tours was taking significant steps to create an itinerary\n\nto satisfy their specific, changing requirements. Nevertheless,\n\nmy colleagues question PREP Tours' allegation that it expended\n\n\n - 50 -\n\nconsiderable effort to meet defendants' demands, maintaining that\n\ndefendants' communications sought only \"tweak[s]\" to the initial\n\nitinerary.33 In addition, my colleagues state that a self-\n\nproclaimed tour \"specialist\" would not need much effort to plan\n\nsuch a tour. This speculative depiction of the record, suggesting\n\nthat the series of requested revisions required minimal, if any,\n\nwork by PREP Tours, fails to draw all reasonable inferences in\n\nPREP Tours' favor. See Carreras, 660 F.3d at 552 (noting that, in\n\nassessing specific jurisdiction, the court must view the evidence\n\n\"in the light most favorable to the plaintiff and draw all\n\nreasonable inferences therefrom in the plaintiff's favor\"). To\n\nthe contrary, it is reasonable to infer that drafting each new\n\nitinerary involved re-engaging with service providers to discuss\n\nnew costs and timing (including booking hotels and flights), and\n\nreconfiguring the tour to satisfy defendants' specific budget and\n\nschedule demands.34\n\n\n\n 33\n In one of their emails, defendants referred to PREP Tours'\nmodifications of the itinerary as \"tweaks.\"\n 34In support of this inference, PREP Tours alleges in its\ncomplaint that defendants \"caused [PREP Tours] to invest an\nenormous time and effort into preparing a package for [the tour]\n. . . according to defendants' specifications.\" The parties'\nsupplemental filings support that PREP Tours reached out to other\nPuerto Rico companies on defendants' behalf. In one email\nreporting revisions to the itinerary, PREP Tours emphasized \"the\ndue diligence, dedication, research, hotel, transportation and\nschedule planning devoted to [defendants'] requests.\"\n\n\n\n - 51 -\n\n Moreover, the proposed trip was a major undertaking,\n\ninvolving travel, accommodations, meals, and activities for a\n\ngroup of 252 people, and represented an estimated half million\n\ndollars in business for PREP Tours and additional revenue for other\n\nPuerto Rico businesses. A trip of such magnitude inevitably would\n\ntake substantial effort to plan and execute. And, indeed, the\n\nrecord confirms that PREP Tours did make considerable efforts on\n\ndefendants' behalf. In addition to the work designing and\n\nreconfiguring the itineraries described above -- and with\n\ndefendants' acknowledgement that they were close to formally\n\nengaging PREP Tours -- the company proceeded to make concrete\n\narrangements with other businesses, including flight and hotel\n\nreservations.\n\n The majority appears to contend that PREP Tours'\n\nprovision of in-forum services must be viewed as largely unilateral\n\n-- and thus irrelevant to the question of whether defendants could\n\nforesee being haled into court in Puerto Rico. The suggestion of\n\none-sided activity is unsupportable, however, given defendants'\n\n\n The majority states that PREP Tours did not allege that it\n\"contacted a single other business, soccer team, or person who did\nnot work for PREP Tours in response to the defendants' inquiry.\"\n(Emphasis added.) If the majority is suggesting that PREP Tours\ndid not contact anyone with whom they had no prior dealings, I\nfail to see the relevance of that fact. Even if some of these\nbusinesses had previously given a quote, it is a reasonable\ninference that PREP Tours had to contact them again each time\ndefendants asked to modify the itinerary.\n\n\n\n - 52 -\n\nseries of emails expressly asking PREP Tours to develop itineraries\n\nwith specified requests.35 It should have been obvious to\n\ndefendants that PREP Tours could not respond to their inquiries\n\nwithout engaging with local companies -- repeatedly -- to ensure\n\navailability at the requested times and to determine the tour's\n\ncost.\n\n Despite these extensive and extended interactions,\n\ndriven by defendants' repeated requests, my colleagues also\n\ncharacterize the negotiations between the parties as \"preliminary\"\n\nin an effort to minimize the scope and quality of PREP Tours'\n\nefforts. Yet, negotiations prior to a formal agreement are always\n\npreliminary in a sequential sense. Here, the pre-contractual\n\nnegotiations went well beyond the \"just inquiring\" phase to the\n\nbrink of an agreement. Thus, discounting the extent of PREP Tours'\n\nin-forum activities because they were preliminary to a formal\n\nagreement unfairly ignores the significance of those activities\n\nfor the purposeful availment inquiry. Put another way, defendants'\n\ncontacts with PREP Tours forged a business relationship that was\n\n\n\n 35\n My colleagues, for example, state that PREP Tours was\n\"push[ing]\" defendants for more details when the company asked for\nthe number of trip participants, which prompted Ramírez to send a\ndocument listing the names of players and coaches and indicating\nthat a total of 252 people would be on the trip. Taken in the\nlight most favorable to PREP Tours, however, the inquiry about\nparticipants was in fact a response to defendants' request to\nprovide a quote for the tour that did not go above $2,000 per\nperson.\n\n\n - 53 -\n\nsufficiently developed to \"cross[] the purposeful availment\n\nthreshold.\" Baskin-Robbins, 825 F.3d at 39.\n\nC. Summary\n\n The circumstances here differ markedly from those in\n\nCopia. The facts alleged by PREP Tours, together with the\n\nreasonable inferences drawn therefrom, show that defendants\n\ntargeted their conduct toward Puerto Rico and Puerto Rico\n\nbusinesses such that they should have foreseen the likelihood of\n\nbeing haled into court in Puerto Rico if a business dispute arose.\n\nSee Burger King, 471 U.S. at 474. The primary products of a tour\n\ncompany include its ability to design an attractive itinerary\n\nsuited to travelers' specified needs, and its capacity to reduce\n\nthat itinerary to a confirmed plan with service providers. PREP\n\nTours moved forward with that process, urged on by defendants'\n\nexpression of satisfaction and indications that defendants were\n\nready to \"seal the deal.\" The flight and hotel reservations that\n\nPREP Tours secured reflect the firmness of the arrangements.\n\n The fact that no contract ultimately was signed, and\n\nthat the services performed therefore did not lead to additional\n\nactivity by PREP Tours, does not diminish the extent of the work\n\nPREP Tours had performed when defendants abruptly pulled out of\n\nthe relationship. Indeed, the essence of PREP Tours' tort claim\n\nis that the defendants unfairly ended the relationship, denying\n\nPREP Tours the opportunity to perform additional, compensable work\n\n\n - 54 -\n\nthat should have been the return on their pre-contractual\n\ninvestment of time and resources.36\n\n Moreover, the abrupt termination of the negotiations\n\npermits a reasonable inference that defendants strung PREP Tours\n\nalong to extract, at no cost, the maximum advantage from its local\n\nknowledge and contacts, with the intent to pass along that\n\ninformation to the company that would ultimately be providing the\n\nPuerto Rico tour. Contrary to the scenario in Copia, the\n\ndefendants' contacts with the forum were far from \"random, isolated\n\nor fortuitous,\" Adelson, 510 F.3d at 50 (quoting Sawtelle, 70 F.3d\n\nat 1391), and the Puerto Rico district court \"should have the power\n\nto subject [] defendant[s] to judgment regarding th[eir]\n\nbehavior,\" Baskin-Robbins, 825 F.3d at 36 (quoting Carreras, 660\n\nF.3d at 555).\n\n III.\n\n Having thus explained why PREP Tours has satisfied the\n\npurposeful availment prong of the personal jurisdiction inquiry,\n\n\n\n 36\n In maintaining that the defendants' contacts here were less\nsubstantial than those found inadequate in Copia, the majority\npoints out that the Copia negotiations involved \"numerous contacts\nbetween the parties to secure an ongoing services relationship.\"\nBut the quantity of contacts was not the problem in Copia; rather,\nthe contacts were not sufficiently connected to the forum. Here,\nby contrast, every communication between the parties was sent to\nor from Puerto Rico, and each related to services to be performed\nin Puerto Rico. Hence, the substance of the contacts here -- i.e.,\nthe direct link to Puerto Rico -- carries far more weight in\nshowing purposeful availment.\n\n\n - 55 -\n\nI turn to the remaining components: relatedness and\n\nreasonableness.\n\nA. Relatedness\n\n The relatedness prong \"focuses on the nexus between the\n\ndefendant's contacts and the plaintiff's cause of action.\"\n\nTicketmaster-N.Y., Inc. v. Alioto, 26 F.3d 201, 206 (1st Cir.\n\n1994). Specifically with reference to PREP Tours' tort claim, it\n\nis apparent that the contacts described above -- i.e., the ongoing\n\ninteractions between defendants and PREP Tours to plan the soccer\n\ntour to Puerto Rico -- are the core of the alleged bad-faith\n\nnegotiations cause of action. Furthermore, the injury to PREP\n\nTours from defendants' alleged freeloading was foreseeable to\n\ndefendants, who misused a \"product\" -- the development of a\n\nspecialized local itinerary -- that PREP Tours was selling.\n\n Although defendants argue that the alleged injury\n\noccurred elsewhere -- i.e., in California, where they ultimately\n\ncontracted with a local company -- the asserted tortious conduct\n\nwas directed at Puerto Rico and the alleged harm occurred there.\n\nWhere a defendant's contacts primarily consist of remote\n\ncommunications, we necessarily focus on the target of the\n\ncommunications and the effects in that forum. See Calder v. Jones,\n\n465 U.S. 783, 789 (1984) (holding that jurisdiction in California\n\nwas proper when the effects of defendants' intentional conduct in\n\nFlorida were felt, and caused a tortious injury, in California).\n\n\n - 56 -\n\nAccordingly, defendants' substantial contacts with Puerto Rico\n\nclearly relate to the culpa in contrahendo tort claim.\n\nB. Reasonableness\n\n After a plaintiff has satisfied the relatedness and\n\npurposeful availment prongs of the personal jurisdiction analysis,\n\ndefendants may nonetheless show that it would be unreasonable for\n\nthe plaintiff's chosen forum to exercise jurisdiction over them.\n\nCourts have identified five so-called \"gestalt factors\" that \"put\n\ninto sharper perspective the reasonableness and fundamental\n\nfairness of exercising jurisdiction in particular situations.\"\n\nPritzker v. Yari, 42 F.3d 53, 64 (1st Cir. 1994). Those factors\n\nare:\n\n (1) the defendant's burden of appearing, (2)\n the forum state's interest in adjudicating the\n dispute, (3) the plaintiff's interest in\n obtaining convenient and effective relief, (4)\n the judicial system's interest in obtaining\n the most effective resolution of the\n controversy, and (5) the common interests of\n all sovereigns in promoting substantive social\n policies.\n\nAdelson, 510 F.3d at 51 (quoting United Elec. Radio & Mach. Workers\n\nof Am. v. 163 Pleasant St. Corp., 960 F.2d 1080, 1088 (1st Cir.\n\n1992)).\n\n Here, the factors inescapably weigh in favor of finding\n\njurisdiction in Puerto Rico. First, despite defendants' assertion\n\nthat it would be costly and burdensome for a non-profit\n\norganization located in California to litigate in Puerto Rico,\n\n\n - 57 -\n\nlitigants can electronically submit filings to a court and video-\n\nconference from anywhere in the country, reducing the need to\n\ntravel. Absent a \"special or unusual burden,\" Pritzker, 42 F.3d\n\nat 64, defendants cannot assert distance as a barrier. Second, as\n\nto the forum state's interest, Puerto Rico has a clear interest in\n\nprotecting its residents from conduct that targets and injures\n\nthem. See, e.g., McGee v. Int'l Life Ins. Co., 355 U.S. 220, 223\n\n(1957) (noting a state's \"manifest interest in providing effective\n\nmeans of redress for its residents when\" they are injured by an\n\nout-of-state party). Third, PREP Tours' interest in resolving the\n\ndispute in Puerto Rico is obvious, and we have held that a\n\nplaintiff's choice of forum must be afforded a degree of deference.\n\nSee Ticketmaster, 26 F.3d at 211. Fourth, we have observed that\n\nall sovereigns share an interest in \"ensuring that [the\n\nsovereign's] companies have easy access to a forum when their\n\ncommercial contracts are said to be breached by out-of-state\n\ndefendants.\" Downer, 771 F.3d at 70. Puerto Rico's culpa in\n\ncontrahendo doctrine reflects this interest in ensuring that\n\ninjuries arising from pre-contractual relationships are\n\nconveniently redressed.37\n\n\n 37\n The fifth factor, the judicial system's interest, has no\nparticular significance here. Although this litigation is already\nunderway in Puerto Rico, and starting the suit anew in California\nwould involve another court system, that situation presumably\nwould exist in every case in which personal jurisdiction is\nchallenged.\n\n\n - 58 -\n\n In sum, the gestalt factors do not even remotely show\n\nthat it would be unfair for defendants to be \"haled into court\" in\n\nPuerto Rico to respond to PREP Tours' allegations. World-Wide\n\nVolkswagen, 444 U.S. at 297.\n\n IV.\n\n Fairly read, with inferences properly drawn in favor of\n\nPREP Tours, the record reveals that personal jurisdiction over\n\ndefendants is proper in Puerto Rico, PREP Tours' chosen forum.\n\nAccordingly, this case should not have been dismissed, and I\n\ntherefore respectfully dissent.\n\n\n\n\n - 59 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357014/", "author_raw": "LIPEZ, Circuit Judge, dissenting"}]}
TORRUELLA
LIPEZ
BARRON
1
{}
4
0
2
0
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4579761/
Published
1
1
0
0
1
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: PREP TOURS, INC., Plaintiff-Appellant, v. AMERICAN YOUTH SOCCER ORGANIZATION; Downey AYSO Region 24; Armando Rodríguez, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Ramón Aguilar, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Carl Jackson, in His Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; Alicia Ramírez, in Her Capacity as Director and/or Officer and/or Member of the Board of Directors of Downey AYSO Region 24; John Doe; Richard Doe; Bob Doe; Insurance Company A; Insurance Company B, Defendants-Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1223\n\n PREP TOURS, INC.,\n\n Plaintiff-Appellant,\n\n v.\n\n AMERICAN YOUTH SOCCER ORGANIZATION; DOWNEY AYSO REGION 24;\n ARMANDO RODRÍGUEZ, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; RAMÓN AGUILAR, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; CARL JACKSON, in his capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; ALICIA RAMÍREZ, in her capacity as Director and/or Officer\n and/or member of the Board of Directors of Downey AYSO Region\n 24; JOHN DOE; RICHARD DOE; BOB DOE;\n INSURANCE COMPANY A; INSURANCE COMPANY B,\n\n Defendants-Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Pedro A. Delgado-Hernández, U.S. District Judge]\n\n\n Before\n\n Torruella, Lipez, and Barron,\n Circuit Judges.\n\n\n Steven J. Torres, with whom Brooks L. Glahn, Torres Scammon\nHincks & Day LLP, Darío Rivera-Carrasquillo, Giancarlo Font, and\nRivera-Carrasquillo, Martínez & Font were on brief, for appellant.\n Alan P. Dagen, with whom The Law Offices of Seda & Alan P.\nDagen, P.A., Luis A. Oliver-Fraticelli, and Adsuar Muñiz Goyco\n\nPérez-Ochoa, P.S.C. were on brief, for appellees.\n\n\n January 8, 2019\n\n BARRON, Circuit Judge. This appeal raises a now familiar\n\nissue: when do remote communications by email and telephone give\n\nrise to the kind of connection to a forum state or territory that\n\njustifies the exercise of personal jurisdiction in that forum over\n\nan out-of-forum defendant? The issue comes to us in this case via\n\nthe diversity suit in the United States District of Puerto Rico\n\nthat a Puerto Rico tour company brought against a California youth\n\nsoccer organization and related defendants. The tour company\n\nalleges in this suit that the defendants, by first requesting that\n\nthe tour company make an offer for a potential soccer trip to\n\nPuerto Rico for some of the organization's teams and their families\n\nbut then declining after further communications to book the tour,\n\nbreached duties that the organization owed to it under Puerto Rico\n\ncontract and tort law. In response to the defendants' motion, the\n\nDistrict Court dismissed both the contract and tort claims for\n\nlack of personal jurisdiction. We now affirm that order.\n\n I.\n\n American Youth Soccer Organization (\"AYSO\") is a\n\nnonprofit entity incorporated and headquartered in California.1\n\n\n\n\n 1 \"We derive our recitation of the case's facts from [the\nplaintiff's] properly documented evidentiary proffers and from\nthose portions of the defendants' proffers that are undisputed.\"\nCopia Commc'ns, LLC v. Amresorts, LP, 812 F.3d 1, 2 (1st Cir.\n2016).\n\n\n - 3 -\n\nThe other defendants are Downey AYSO Region 24 (\"Region 24\") and\n\nfour volunteers for Region 24.\n\n Region 24 is a regional chapter of AYSO from Downey,\n\nCalifornia. Region 24 is not a separate legal entity from AYSO.\n\n The four Region 24 volunteers served at all relevant\n\ntimes as, respectively, Region 24's commissioner (Armando\n\nRodríguez), assistant commissioner (Ramón Aguilar), treasurer\n\n(Carl Jackson), and volunteer coordinator (Alicia Ramírez). All\n\nfour individuals are residents of California.\n\n PREP TOURS, Inc. (\"PREP Tours\") is the plaintiff.2 It\n\nis a Puerto Rico corporation that, according to the complaint,\n\n\"specializes in student cultural immersion educational field\n\ntrips\" and is \"dedicated to servicing and organizing educational\n\nsoccer tours for student athletes and soccer clubs focusing on\n\nfriendly soccer games in Puerto Rico.\"\n\n On Friday, November 2, 2012, Ramírez emailed PREP Tours\n\nfrom California to ask for a price quote and for what the company\n\ncould \"offer\" regarding an all-inclusive trip to Puerto Rico for\n\n\"[a]pproximately 60 players and their families.\" Ramírez informed\n\nthe tour company in that email that Region 24 was also gathering\n\n\n 2\n The covers of PREP Tours's briefs list additional\nplaintiffs, but neither the complaint nor the District Court's\njudgment identifies any additional plaintiff other than PREP\nTours. And the notice of appeal specifies only PREP Tours as the\nparty taking this appeal. See Rosario-Torres v. Hernandez-Colon,\n889 F.2d 314, 316-17 (1st Cir. 1989).\n\n\n - 4 -\n\ninformation about alternative destinations, like Hawaii and\n\nMexico.\n\n PREP Tours responded that very same Friday by sending\n\nvia email a promotional brochure regarding the \"unique soccer\n\nprogram\" in the Puerto Rico cities of San Juan and Rincón that it\n\noffered visiting youth soccer teams. The tour company also emailed\n\nRamírez, after the weekend, a proposed itinerary based on the San\n\nJuan and Rincón tour described in the brochure, which PREP Tours\n\ndescribed as \"a tentative rough draft.\" There followed,\n\nintermittently over the next four months, emails and telephone\n\ncalls, as well as at least one text message, between the parties\n\nconcerning the possible trip. During these ensuing\n\ncommunications, Ramírez informed PREP Tours that Region 24 was\n\nconsidering competing offers on a possible trip to Puerto Rico\n\nfrom three alternative travel agencies, at least one of which was\n\nnot based in Puerto Rico.\n\n Before Region 24 made a decision about the trip, a travel\n\nagency in Florida, Hakuna Matata Group Tours, LLC, contacted\n\nRamírez by email concerning possible flights. The complaint says\n\nthat Hakuna Matata was \"designated by PREP Tours\" to handle the\n\nsoccer teams' flight arrangements.\n\n Hakuna Matata later emailed Ramírez with information for\n\nwiring it money as a deposit on the airline flights. Region 24's\n\ntreasurer, Jackson, thereafter emailed Hakuna Matata to say that\n\n\n - 5 -\n\nhe could wire transfer the money to Hakuna Matata's account the\n\nnext day, January 25.\n\n Jackson did not wire the money. Ramírez did write PREP\n\nTours on January 25, however, to say that the commissioner,\n\nassistant commissioner, and treasurer of Region 24 still had \"to\n\ngo through everything with a fine tooth-comb.\"\n\n The record references no further communications between\n\nany of the parties until the ones that were made on February 25,\n\n2013. On that day, PREP Tours emailed Region 24's commissioner,\n\nassistant commissioner, and treasurer to follow up on the status\n\nof its offer.\n\n The commissioner, Rodríguez, responded that same day\n\nwith an email telling PREP Tours that the assistant commissioner,\n\nAguilar, was \"still working on logistics.\" He then sent a later\n\nemail that instructed PREP Tours to disregard this first email.\n\nAguilar had responded in the interim by informing PREP Tours that\n\n\"[a]fter reviewing all proposals from the 3 compan[ies] we decided\n\nto go with a local company.\"\n\n Just short of two years later, PREP Tours sued AYSO,\n\nRegion 24, and the four volunteers in the United States District\n\nCourt for the District of Puerto Rico, seeking a minimum of\n\n$640,000 in damages. The complaint alleged that the defendants\n\nwere liable under the Puerto Rico tort doctrine of culpa in\n\ncontrahendo, \"which requires parties to negotiate in good faith.\"\n\n\n - 6 -\n\nYsiem Corp. v. Commercial Net Lease Realty, Inc., 328 F.3d 20, 23\n\n(1st Cir. 2003) (citation omitted). The complaint also alleged a\n\nbreach-of-contract claim under Puerto Rico law. The complaint\n\nasserted that the contract was created by: (1) the email from\n\nRegion 24's treasurer to Hakuna Matata in Florida, saying that he\n\ncould wire money to that third-party travel agency in order to\n\nmake a deposit on the airline flights; and (2) other\n\n\"representations\" made by the defendants. The complaint did not\n\nallege what the contract's terms were, but it did allege that the\n\ndefendants were in breach of the contract.\n\n The defendants moved to dismiss PREP Tours's claims\n\nunder Federal Rule of Civil Procedure 12(b)(2) for lack of personal\n\njurisdiction, and the defendants submitted affidavits with their\n\nmotion. An affidavit from AYSO's deputy executive director as\n\nwell as affidavits from the individual defendants each averred\n\nthat the \"only contacts\" that existed between the defendants and\n\nPREP Tours consisted of \"the preliminary communications between\n\nsome of [the Region 24] volunteers and the travel agency with whom\n\nthey communicated in an effort to obtain pricing and information\n\nfor a potential trip for some of [Region 24's] youth soccer teams.\"\n\n PREP Tours's brief in opposition to the defendants'\n\nmotion to dismiss included a number of evidentiary submissions\n\nattached as exhibits. The submissions included copies of the\n\n\n\n\n - 7 -\n\ncommunications exchanged between the parties during the relevant\n\nfour-month period.\n\n Neither party requested an evidentiary hearing following\n\nthe defendants' motion challenging personal jurisdiction, nor did\n\nthe District Court conduct one. The District Court instead used\n\nwhat we have referred to as \"the prima facie standard\" to assess\n\nwhether PREP Tours had met its burden to justify the exercise of\n\npersonal jurisdiction in Puerto Rico over the defendants. Boit v.\n\nGar-Tec Prods., Inc., 967 F.2d 671, 675-76 (1st Cir. 1992)\n\n(emphasis omitted); see also A Corp. v. All Am. Plumbing, Inc.,\n\n812 F.3d 54, 58 (1st Cir. 2016) (explaining that the plaintiff\n\nbears the burden to establish that personal jurisdiction exists\n\nover the defendant).\n\n Under this standard, a district court \"consider[s] only\n\nwhether the plaintiff has proffered evidence that, if credited, is\n\nenough to support findings of all facts essential to personal\n\njurisdiction.\" Boit, 967 F.2d at 675. \"To make a prima facie\n\nshowing of this calib[er], the plaintiff ordinarily cannot rest\n\nupon the pleadings, but is obliged to adduce evidence of specific\n\nfacts.\" Foster-Miller, Inc. v. Babcock & Wilcox Can., 46 F.3d\n\n138, 145 (1st Cir. 1995) (citing Boit, 967 F.2d at 675).\n\n In July of 2016, the District Court granted the\n\ndefendants' motion to dismiss PREP Tours's claims without\n\nprejudice for lack of personal jurisdiction. The District Court\n\n\n - 8 -\n\nreasoned that, although the defendants reached out to PREP Tours\n\nregarding the trip, they \"repeatedly communicated to [PREP Tours]\n\nthat officials had not made a final decision in regards to the\n\ntrip\" and that the \"unilateral\" actions undertaken by PREP Tours\n\nin Puerto Rico in response were insufficient to establish personal\n\njurisdiction over the defendants as to any of PREP Tours's claims.\n\n PREP Tours now appeals. Our review of the District\n\nCourt's judgment is de novo. See Boit, 967 F.2d at 675. \"Reviewing\n\na decision made under the prima facie standard, we must accept\n\n[the plaintiff's] properly documented evidentiary proffers as true\n\nand construe them in the light most favorable to [the plaintiff's]\n\njurisdictional claim.\" A Corp., 812 F.3d at 58 (citing Phillips\n\nv. Prairie Eye Ctr., 530 F.3d 22, 26 (1st Cir. 2008)). \"But we\n\nwill also consider facts offered by [the defendants], to the extent\n\nthat they are not disputed.\" Id. (citing Daynard v. Ness, Motley,\n\nLoadholt, Richardson & Poole, P.A., 290 F.3d 42, 51 (1st Cir.\n\n2002)).\n\n II.\n\n PREP Tours conceded below, as it must, that the District\n\nCourt lacks general jurisdiction over the defendants because the\n\ndefendants do not have \"continuous and systematic\" contacts with\n\nPuerto Rico. Goodyear Dunlop Tires Operations, S.A. v. Brown, 564\n\nU.S. 915, 919 (2011). PREP Tours nevertheless contends that the\n\nDistrict Court erred in dismissing its claims because the District\n\n\n - 9 -\n\nCourt does have \"specific or case-linked\" jurisdiction over the\n\ndefendants as to both of its claims. Id. Jurisdiction on this\n\nbasis \"depends on an affiliatio[n] between the forum and the . .\n\n. controversy\" underlying the plaintiff's claims. Id. (alteration\n\nin original) (internal quotation marks omitted).\n\n \"When . . . the lens of judicial inquiry narrows to focus\n\non specific jurisdiction . . . . the applicable constitutional\n\nlimits assume critical importance.\" Foster-Miller, 46 F.3d at\n\n144. Those limits, arising from the Due Process Clause of the\n\nFourteenth Amendment to the United States Constitution, permit a\n\ncourt to exercise jurisdiction over an out-of-forum defendant only\n\nif, with respect to the claims at issue, the defendant has \"certain\n\nminimum contacts with [the forum] such that the maintenance of the\n\nsuit does not offend 'traditional notions of fair play and\n\nsubstantial justice.'\" Int'l Shoe Co. v. Washington, 326 U.S.\n\n310, 316 (1945) (quoting Milliken v. Meyer, 311 U.S. 457, 463\n\n(1940)).3\n\n\n\n\n 3\n \"The requirements of International Shoe . . . must be met\nas to each defendant over whom a state court exercises\njurisdiction.\" Rush v. Savchuk, 444 U.S. 320, 332 (1980). The\nparties dispute whether, under the facts of this case, we may\nattribute the various defendants' combined forum contacts to each\nindividual defendant for the purposes of the personal jurisdiction\nanalysis. Because even the combined forum contacts are\nconstitutionally insufficient, however, we need not decide who is\nright.\n\n\n - 10 -\n\n To determine whether the exercise of specific\n\njurisdiction in the forum over an out-of-forum defendant conforms\n\nto that federal constitutional test, three requirements must be\n\nmet:\n\n First, the claim underlying the litigation\n must directly arise out of, or relate to, the\n defendant's forum-state activities. Second,\n the defendant's in-state contacts must\n represent a purposeful availment of the\n privilege of conducting activities in the\n forum state, thereby invoking the benefits and\n protections of that state's laws and making\n the defendant's involuntary presence before\n the state's courts foreseeable. Third, the\n exercise of jurisdiction must . . . be\n reasonable.\n\nUnited Elec., Radio & Mach. Workers of Am. v. 163 Pleasant St.\n\nCorp., 960 F.2d 1080, 1089 (1st Cir. 1992).\n\n This inquiry is highly \"fact-specific.\" Id. As the\n\nSupreme Court has explained, the constitutional test is \"not\n\nsusceptible of mechanical application; rather, the facts of each\n\ncase must be weighed to determine whether the requisite\n\n'affiliating circumstances' are present.\" Kulko v. Superior Court\n\nof Cal., 436 U.S. 84, 92 (1978) (quoting Hanson v. Denckla, 357\n\nU.S. 235, 246 (1958)). Moreover, \"this determination is one in\n\nwhich few answers will be written 'in black and white. The greys\n\nare dominant and even among them the shades are innumerable.'\"\n\nId. (quoting Estin v. Estin, 334 U.S. 541, 545 (1948)).\n\n\n\n\n - 11 -\n\n III.\n\n We begin with the requirement that PREP Tours's claims\n\nmust relate to the defendants' contacts with Puerto Rico. This\n\n\"flexible, relaxed standard\" for assessing relatedness requires\n\nthat there be only a \"demonstrable nexus\" between the complaint's\n\nclaims and the activities in the forum that properly may be\n\nattributed to the defendants, such that \"the litigation itself is\n\nfounded directly on those activities.\" Adelson v. Hananel, 652\n\nF.3d 75, 81 (1st Cir. 2011) (quoting N. Laminate Sales, Inc. v.\n\nDavis, 403 F.3d 14, 25 (1st Cir. 2005); Hannon v. Beard, 524 F.3d\n\n275, 279-80 (1st Cir. 2008)).\n\n PREP Tours contends that, as to each of its claims, the\n\ndefendants' \"related\" forum contacts are the defendants' remote\n\ncommunications with the Puerto Rico-based tour company during the\n\nfour-month period beginning with Ramírez's initial inquiry email\n\nand the activities that PREP Tours undertook from Puerto Rico\n\nduring those four months in response to those communications.4\n\nPREP Tours contends that its tort claim alleging that the\n\ndefendants negotiated in bad faith arises from the defendants'\n\n\n\n 4\n PREP Tours does point out that the AYSO teams eventually\ntraveled to Puerto Rico in July of 2013. But, this trip occurred\nseveral months after the communications between the parties from\nwhich PREP Tours asserts that their claims arise, and PREP Tours\nmakes no argument that their claims also arise from this trip.\nSee Carreras v. PMG Collins, LLC, 660 F.3d 549, 554 (1st Cir.\n2011).\n\n\n - 12 -\n\ncontacts with Puerto Rico because it was through the defendants'\n\nremote communications with the tour company that the defendants\n\nacted in bad faith, resulting in harm to the tour company in Puerto\n\nRico in consequence of, at least in part, the activities that PREP\n\nTours undertook in Puerto Rico in response to those communications.\n\nPREP Tours contends that its breach-of-contract claim arises from\n\nthese same set of contacts, as the remote communications between\n\nthe parties and the actions that the tour company undertook in\n\nresponse to them provide the basis for the claim that the\n\ndefendants reached into Puerto Rico to enter into the alleged\n\ncontract and then breached it. See Daynard, 290 F.3d at 52\n\n(explaining that, with respect to a breach-of-contract claim, we\n\nfocus on \"the parties' 'prior negotiations and contemplated future\n\nconsequences, along with the terms of the contract and the parties'\n\nactual course of dealing'\" (quoting Burger King Corp. v. Rudzewicz,\n\n471 U.S. 462, 479 (1985))).\n\n The defendants counter that PREP Tours's claims do not\n\nin fact arise from their remote communications with the tour\n\ncompany or the activities in Puerto Rico that PREP Tours claims to\n\nhave taken in response to those communications. The defendants\n\ncontend that their conduct that allegedly breached both their duty\n\nto negotiate in good faith and their alleged contract with PREP\n\nTours was their decision to book the trip through a different\n\ncompany, which was a decision that they made outside of Puerto\n\n\n - 13 -\n\nRico. Moreover, as far as the breach-of-contract claim is\n\nconcerned, the defendants point out that the complaint's only non-\n\nconclusory allegation that a contract existed between the parties\n\nis based on an email that was sent by Region 24's treasurer in\n\nCalifornia to a travel agency, Hakuna Matata, that is located in\n\nFlorida and that has no connection to Puerto Rico.\n\n The District Court agreed with PREP Tours that the\n\nrelatedness requirement for case-linked jurisdiction is met as to\n\nboth the tort and contract claims, but we need not decide whether\n\nthe District Court was right. Even if the defendants' remote\n\ncommunications with PREP Tours and PREP Tours's activities in\n\nPuerto Rico in response relate to PREP Tours's claims, PREP Tours\n\nmust also show that the defendants purposefully availed themselves\n\nof the privilege of conducting activities in Puerto Rico through\n\nthese contacts. See United Elec., 960 F.2d at 1089. And, as we\n\nnext explain, the District Court rightly concluded that PREP Tours\n\nfailed to do so. Accordingly, we turn to the purposeful availment\n\ninquiry, assuming that the contacts that PREP Tours identifies as\n\nbeing related to its claims are in fact related to them.5\n\n\n 5 Given this conclusion, we also do not need to reach the\nreasonableness requirement of the due process analysis. Nor do we\nneed to reach the issue of whether personal jurisdiction is\npermitted under Puerto Rico's long-arm statute. See Ticketmaster-\nN.Y., Inc. v. Alioto, 26 F.3d 201, 204 (1st Cir. 1994) (explaining\nthat, in order to assert specific jurisdiction over an out-of-\nforum defendant, a federal court sitting in diversity \"must find\n\n\n\n - 14 -\n\n IV.\n\n To explain why we agree with the District Court that\n\nPREP Tours has not satisfied the purposeful availment requirement\n\nas to any of its claims, we first need to describe that requirement\n\nin more detail. With that legal background in place, we then can\n\nexplain why we conclude that PREP Tours, on this record, fails to\n\nmake the requisite showing.\n\n A.\n\n To show that the defendants purposefully availed\n\nthemselves of the privilege of conducting activities in the forum,\n\nPREP Tours must demonstrate that the defendants established a\n\n\"substantial connection\" with Puerto Rico. Burger King, 471 U.S.\n\nat 475 (quoting McGee v. Int'l Life Ins. Co., 355 U.S. 220, 223\n\n(1957)). Put otherwise, PREP Tours must point to \"some act by\n\nwhich the defendant[s] purposefully avail[ed] [them]sel[ves] of\n\nthe privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Id.\n\n(quoting Hanson, 357 U.S. at 253).\n\n By requiring the plaintiff to establish such a\n\nsubstantial connection between the out-of-forum defendant and the\n\nforum, we ensure that it is \"fair to require defense of the action\n\nin the forum.\" Kulko, 436 U.S. at 91 (citing Milliken, 311 U.S.\n\n\ncontacts that, in the aggregate, satisfy the requirements of both\nthe forum state's long-arm statute and the Fourteenth Amendment\").\n\n\n - 15 -\n\nat 463-64). The purposeful availment requirement in this way\n\n\"represents a rough quid pro quo: when a defendant deliberately\n\ntargets its behavior toward the society or economy of a particular\n\nforum, the forum should have the power to subject the defendant to\n\njudgment regarding that behavior.\" Carreras, 660 F.3d at 555\n\n(citing J. McIntyre Mach., Ltd. v. Nicastro, 564 U.S. 873, 879\n\n(2011) (plurality op.)).\n\n The flip side of this deal, however, is that when the\n\nout-of-forum defendant has not \"manifestly . . . availed himself\n\nof the privilege of conducting business there,\" it would be\n\n\"unreasonable to require [the defendant] to submit to the burdens\n\nof litigation in that forum[.]\" Burger King, 471 U.S. at 476.\n\nAnd, in accord with this understanding of the purposeful availment\n\nrequirement, we have explained that \"the two cornerstones of\n\npurposeful availment\" are \"voluntariness\" and \"foreseeability.\"\n\nTicketmaster-N.Y., 26 F.3d at 207.\n\n \"Voluntariness requires that the defendant's contacts\n\nwith the forum state 'proximately result from actions by the\n\ndefendant himself.'\" Phillips, 530 F.3d at 28 (quoting Burger\n\nKing, 471 U.S. at 475). Accordingly, the Supreme Court has\n\nexplained that any contacts that cannot be attributed\n\n\"proximately\" to the defendant's own activities constitute\n\n\"unilateral\" activity that cannot establish purposeful availment.\n\nSee Burger King, 471 U.S. at 475.\n\n\n - 16 -\n\n In addition, the Supreme Court has described the\n\n\"benchmark\" for purposeful availment in terms of a particular \"kind\n\nof foreseeability.\" Id. at 474 (quoting World-Wide Volkswagen\n\nCorp. v. Woodson, 444 U.S. 286, 295 (1980)); see also Donatelli v.\n\nNat'l Hockey League, 893 F.2d 459, 464 (1st Cir. 1990) (discussing\n\nthe Court's introduction of this \"explicit 'foreseeability'\n\nelement into the liturgy of minimum contacts\"). Specifically, the\n\nSupreme Court has explained that \"the foreseeability that is\n\ncritical to due process analysis . . . is that the defendant's\n\nconduct and connection with the forum State are such that he should\n\nreasonably anticipate being haled into court there.\" Burger King,\n\n471 U.S. at 474 (quoting World-Wide Volkswagen, 444 U.S. at 297).\n\nFor this reason, too, a plaintiff's \"unilateral activity\" cannot\n\nestablish the requisite connection between the defendants and the\n\nforum jurisdiction. Id. at 474-75 (quoting Hanson, 357 U.S. at\n\n253).\n\n There is good reason to focus on whether out-of-forum\n\ndefendants could foresee being haled into a court in the forum\n\nfrom the connection that they are said to have with the forum.\n\nSuch a focus for the inquiry \"gives a degree of predictability to\n\nthe legal system\" because it \"allows potential defendants to\n\nstructure their primary conduct with some minimum assurance as to\n\nwhere that conduct will and will not render them liable to suit.\"\n\nWorld-Wide Volkswagen, 444 U.S. at 297.\n\n\n - 17 -\n\n Notably, the fact that a defendant directly contacted\n\nthe plaintiff in the forum only remotely by Internet or telephone,\n\nas allegedly happened here, does not preclude the defendant from\n\nhaving the substantial connection to the forum that is necessary\n\nto satisfy the purposeful availment requirement. See Burger King,\n\n471 U.S. at 476. Such remote communications are often the primary\n\nmeans by which business relationships are forged and conducted.\n\nSee id.\n\n But, as the Supreme Court has noted, the application of\n\nthe rule prohibiting a plaintiff's unilateral activity from\n\nestablishing the requisite foreseeable substantial connection\n\nbetween the defendant and the forum \"will vary with the quality\n\nand nature of the defendant's activity.\" Id. at 474-75 (quoting\n\nHanson, 357 U.S. at 253). Thus, the fact that the communications\n\noccurred remotely may well be relevant to the inquiry. And, to\n\nthat very point, we have recently observed that three factors have\n\nbeen the \"hing[e]\" in our past assessment of purposeful availment\n\nin cases in which remote communications supplied the predicate for\n\nthe contacts that ground specific or case-linked personal\n\njurisdiction over an out-of-forum defendant: \"the defendant's in-\n\nforum solicitation of the plaintiff's services, the defendant's\n\nanticipation of the plaintiff's in-forum services, and the\n\nplaintiff's actual performance of extensive in-forum services.\"\n\nCopia, 812 F.3d at 6 (emphasis added) (describing the factors from\n\n\n - 18 -\n\nC.W. Downer & Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59\n\n(1st Cir. 2014), and Cossart v. United Excel Corp., 804 F.3d 13\n\n(1st Cir. 2015)).\n\n B.\n\n Against this background, we now must assess whether the\n\nshowing that PREP Tours has made regarding both the nature and\n\nquality of the defendants' activities and the activities that PREP\n\nTours engaged in that relate to the contract and tort claims at\n\nissue satisfies the purposeful availment requirement. PREP Tours\n\nrelies on the three factors identified in Copia in asserting that\n\nits showing as to these activities does suffice. And so we need\n\nto address what PREP Tours has to say about how these activities\n\nrelate to each of these factors.6\n\n\n 6 The dissent suggests that it is focusing only on the\nplaintiff's tort claim because it \"reveals so clearly the error in\nthe majority's purposeful availment analysis and unfairness of the\noutcome.\" See Diss. Op. 44 n.27. But, we do not see how the\ndistinction between the tort claim and the contract claim matters\nto the purposeful availment inquiry, or how the focus on the tort\nclaim reveals any unfairness with respect to the lack of personal\njurisdiction over the defendant in Puerto Rico that would not be\nequally evident if we focused on the contract claim. After all,\nwhile the dissent cites to much precedent explicating Puerto Rico\ntort law, the purposeful availment test does not derive its content\nfrom local law. It derives its content from the requirements of\na federal constitutional protection. And Copia holds that this\nprotection requires a showing that the out-of-forum defendant,\nthrough voluntary contacts making the forum's assertion of\njurisdiction over him foreseeable, has established a greater tie\nto that forum than was determined to be present there. See 812\nF.3d at 6. Nothing in the way that Puerto Rico has chosen to\ndefine the elements of this tort claim, therefore, can permit us\n\n\n\n - 19 -\n\n PREP Tours does point to aspects of the record that bear\n\non each one of these three factors. As to solicitation, we agree\n\nwith PREP Tours that the record shows that one of the Region 24\n\nvolunteers, Ramírez, voluntarily reached out (remotely) from\n\n\n\nto conclude that a lesser tie than was present in Copia may suffice\nto satisfy the federal constitutional minimum that we discerned in\nthat case. And the dissent cites no case indicating to the\ncontrary.\n Of course, in some cases, the defendant's contacts with the\nforum jurisdiction that are related to a plaintiff's tort claim\nmight differ from those related to its contract claim, such that\nthe purposeful availment inquiry with respect to each claim might\nrequire an assessment of distinct contacts. See Phillips Exeter\nAcad. v. Howard Phillips Fund, 196 F.3d 284, 288-89 (1st Cir. 1999)\n(explaining that the relatedness inquiry is done \"on a claim-by-\nclaim basis\" because it depends on the nexus between the alleged\nin-forum contacts and the \"elements of the cause of action\"). In\nCopia, for example, because the plaintiffs pressed a contract\nclaim, we only considered the defendants' \"relevant, i.e.,\ncontract-related, dealings with\" the plaintiff for the purposeful\navailment analysis. 812 F.3d at 5. But, as we have explained,\nsee supra p.14, and as the dissent acknowledges, see Diss. Op. 44\nn.27, we are proceeding on the assumption in this case that the\ncontract and tort claims arise from the same alleged \"activity or\n. . . occurrence[] . . . in the forum State,\" Goodyear, 564 U.S.\nat 919, and thus we consider precisely the same set of contacts as\nto both claims. Accordingly, our purposeful availment analysis is\nprecisely the same as to both claims, nor does the plaintiff ask\nus to proceed otherwise.\n Thus, we must decide whether those contacts suffice to\nestablish a more substantial connection between the defendants and\nthe forum here than Copia found to be present there. In doing so,\nhowever, we do not thereby purport to address the merits of either\nthe contract or the tort claim, as our inquiry concerns only the\nlegal propriety of making Puerto Rico the forum jurisdiction for\nthe claims. And, with respect to that inquiry, the \"fairness\"\nconcern that matters relates not to how Puerto Rico defines its\ntort law, but to how the relevant precedents construe the Due\nProcess Clause to define purposeful availment.\n\n\n\n - 20 -\n\nCalifornia to PREP Tours in Puerto Rico in order to ask for a price\n\nquote and for what the company could \"offer\" as a proposed trip\n\nfor roughly sixty soccer players and their families. We can also\n\nagree that the defendants should have reasonably anticipated that\n\nsome action would be undertaken by PREP Tours in Puerto Rico in\n\nresponse to that inquiry -- such as replying with a proposed\n\nitinerary -- given that the defendants knew that PREP Tours was\n\nlocated there. And, finally, we can see no reason to doubt that\n\nsome foreseeable action was then actually undertaken by PREP Tours\n\nin Puerto Rico.\n\n But, even granting all that, as we will next explain,\n\nthe factors that we identified in Copia are not present here \"to\n\nremotely the same degree\" as they were in our other cases on which\n\nPREP Tours relies in arguing that the purposeful availment\n\nrequirement is met. Copia, 812 F.3d at 6. And, in light of that\n\nfact and our review of the relevant contacts as a whole, we\n\nconclude, as we did in Copia itself, that the in-forum plaintiff\n\ndid not meet its burden to satisfy the purposeful availment\n\nrequirement as to any of its claims.7\n\n\n 7\n In arguing that the purposeful availment requirement is\nsatisfied, PREP Tours asserts on appeal that the parties had forged\na contract because the defendants ultimately \"agreed on a final\nitinerary and cost . . . and agreed to proceed with the trip that\nPREP Tours had planned at the Defendants' request.\" But, in making\nthat conclusory assertion on appeal, PREP Tours does not develop\nany challenge to the District Court's ruling below in which the\n\n\n\n - 21 -\n\n 1.\n\n We start by considering the showing that PREP Tours made\n\nregarding the nature and quality of the defendants' activities in\n\nthe forum as they relate to the Copia factors. Those in-forum\n\ndefendant activities consist exclusively of the defendants' remote\n\ncommunications with PREP Tours concerning the trip.\n\n\n\n\nDistrict Court rejected PREP Tours's contention that the Region 24\ntreasurer's email with a third party -- Hakuna Matata -- could\nshow that a contract existed between PREP Tours and the defendants.\nNor does PREP Tours point on appeal to any non-conclusory\nallegation in the complaint (or the record) showing that a contract\ndid exist between the parties. See Soto-Torres v. Fraticelli, 654\nF.3d 153, 156 (1st Cir. 2011).\n Moreover, PREP Tours also does not develop any argument about\nhow the alleged contract bears on the purposeful availment inquiry\nas to the assertion of personal jurisdiction with respect to either\nthe contract or tort claims. For example, PREP Tours does not\nargue to us -- and did not argue below -- that purposeful availment\nexists due to services that the tour company would foreseeably\nprovide in the forum under the contract, or due to any other\n\"contemplated future consequences\" under the contract. Daynard,\n290 F.3d at 52 (quoting Burger King, 471 U.S. at 479). In fact,\nPREP Tours nowhere alleges -- either below or on appeal -- what\nthe terms of the purported contract even were. We have repeatedly\nmade clear, however, that an out-of-forum party's contract with an\nin-forum party is not in and of itself sufficient to establish\npersonal jurisdiction over the out-of-forum party, even where the\nplaintiff's claims include non-contract claims. See United States\nv. Swiss Am. Bank, Ltd., 274 F.3d 610, 621 (1st Cir. 2001) (quoting\nGanis Corp. of Cal. v. Jackson, 822 F.2d 194, 197-98 (1st Cir.\n1987)). Thus, PREP Tours's failure to develop any such argument\non appeal is problematic, insofar as PREP Tours means to contend\nthat the alleged contract alone enables PREP Tours to satisfy the\npurposeful availment requirement for its claims even if the other\ncontacts with Puerto Rico that it attributes to the defendants\n(and which the analysis that follows addresses) otherwise would\nnot suffice.\n\n\n\n - 22 -\n\n The communications began, the evidentiary submissions\n\nshow, when one of the Region 24 volunteers, Ramírez, asked PREP\n\nTours via email from California for a price quote and for what the\n\ncompany could \"offer\" regarding a potential trip by some of Region\n\n24's teams to Puerto Rico. The evidentiary submissions also show\n\nthat this same volunteer later asked via electronic means from\n\nCalifornia that PREP Tours modify the offer that she had earlier\n\nrequested in light of new specifications that she gave regarding\n\nthat potential trip.\n\n We cannot reasonably infer, however, from these\n\ncommunications alone that the defendants (a number of whom had no\n\ncontact directly with PREP Tours at all),8 or even Ramírez in\n\nparticular, believed themselves to be asking for the type of\n\ninformation that would require a self-described \"speciali[st]\" in\n\nsuch trips to engage in extensive trip-planning activities in the\n\nforum prior to an agreement being reached with the \"speciali[st].\"\n\nNor can we reasonably infer from these communications alone that\n\nthe purposeful availment requirement is met on the ground that\n\nthey show that the defendants were contemplating the kind of\n\n\n 8 As far as the evidentiary submissions indicate, over the\ncourse of the relevant four-month period, the two entity\ndefendants, AYSO and Region 24, had no direct communications with\nPREP Tours. Nor did Region 24's treasurer, Jackson. Region 24's\ncommissioner (Rodríguez) and assistant commissioner (Aguilar),\nmoreover, together sent only three emails to PREP Tours, all on\nthe same day, solely to apprise PREP Tours of the status of its\noffer in response to PREP Tours's own query.\n\n\n - 23 -\n\nongoing and close-working relationship with PREP Tours that could\n\nestablish the requisite substantial connection between the\n\ndefendants and the forum. See Cossart, 804 F.3d at 21; C.W.\n\nDowner, 771 F.3d at 67.\n\n Ramírez made clear in her initial inquiry email to PREP\n\nTours that no decision had even been made for the soccer teams to\n\ngo to Puerto Rico, as the email expressly stated that Region 24\n\nwas also gathering information about alternative destinations,\n\nlike Hawaii and Mexico. And, in her email replying to PREP Tours's\n\nresponse to that initial inquiry, Ramírez noted that \"[a]s soon as\n\n[Region 24's] decision is made, I will let you know,\" thereby\n\nreinforcing the preliminary nature of her inquiry and diminishing\n\nthe foreseeability of PREP Tours undertaking extensive in-forum\n\nactivities in response or the parties having an ongoing and close-\n\nworking relationship.\n\n PREP Tours's complaint does assert that PREP Tours\n\n\"continuously receiv[ed] requests by e-mail and telephone calls\"\n\nfrom Ramírez \"to amend different areas of the proposal in order to\n\naccommodate the needs of the group\" and that these requests\n\nresulted in \"multiple requirements\" with which PREP Tours's offer\n\nhad to comply.9 But, while communications of that type certainly\n\n\n 9 The complaint alleges that requests were also received\n\"later on\" from the Region 24 treasurer, Jackson. However, the\nonly communication by Jackson that PREP Tours's papers reference\nwas his email to the third-party travel agency located in Florida.\n\n\n - 24 -\n\ndo bear on the Copia factors of solicitation and anticipation, the\n\nproperly documented communications call into question PREP Tours's\n\ncharacterization of the nature of these communications. Instead,\n\nthe record shows only the following.\n\n Ramírez asked by email for PREP Tours to \"tweak\" -- her\n\nwording in the email -- the \"tentative rough draft\" itinerary that\n\nPREP Tours had initially sent, which resulted in what PREP Tours\n\ndescribed in an email to Ramírez as a \"new itinerary almost\n\nidentical to the original itinerary that we first sent you.\"10\n\nRamírez did so, moreover, while also informing PREP Tours that\n\nRegion 24 was contacting three alternative travel agencies for\n\ncompeting offers on the possible trip to Puerto Rico.\n\n The evidentiary submissions also show that Ramírez later\n\nsent an email asking whether PREP Tours could accommodate specific\n\ndates for a possible trip that incorporated the prior \"tweak\" along\n\n\n\n 10 The requested \"tweak\" was to include all-inclusive hotels,\ntwo to three matches per team, two to three excursions, free time\nfor families, and a cost of about $2,000 per person. PREP Tours\nrejected the request for all-inclusive hotels, explaining that it\nwould not be cost-effective. Thus, PREP Tours stuck with hotels\nthat it had already identified when it sent the original itinerary\nto Ramírez. The revised itinerary also did not list any additional\nlocal teams that would participate in the friendly soccer matches.\nFinally, the revised itinerary removed some activities that PREP\nTours had originally proposed while adding some additional\nactivities that Ramírez's email had not requested (such as a tour\nof a Bacardi rum plant). These changes reduced the estimated price\nrange from $1,495-$1,595 to $1,275-$1,375 per person without\nairfare.\n\n\n\n - 25 -\n\nwith arguably some minimal changes to it.11 But, Ramírez stated\n\nin that email once again that Region 24 had not yet decided on a\n\ntravel agency, though she did at that point state (for the first\n\ntime) that the trip would be to Puerto Rico.\n\n Finally, the record shows that, following this email\n\nfrom Ramírez, PREP Tours sent her a revised itinerary reflecting\n\nminimal changes and pushed Ramírez for more details about the\n\nnumber of persons who might be on the trip. And, as the record\n\nshows, Ramírez thereafter sent PREP Tours a one-line email\n\nattaching a document listing a \"breakdown of our team going to\n\nPuerto Rico,\" which consisted of some seventy names of players and\n\ncoaches.12\n\n But, in sending along that partial list of potential\n\ntravelers, Ramírez was responding to a request for information\n\nfrom PREP Tours. That is, Ramírez provided the partial list in\n\nresponse to a unilateral act by PREP Tours. Furthermore, in\n\nproviding that response, Ramírez did not state that Region 24 had\n\n\n 11 Ramírez inquired about specific dates for a ten-day trip\nthat -- roughly consistent with the earlier \"tweak\" she had already\nrequested that had resulted in the \"almost identical\" revised\nitinerary -- would consist of only three matches per team, include\nfree time, and cost no more than $2,000. The itinerary she\nreceived back from PREP Tours a week later removed or rendered\n\"optional\" some of the activities. The estimated price was $1,995\nper adult and $1,695 per child with airfare.\n 12Although the attached \"breakdown\" listed the names of only\nsome seventy players and coaches, it indicated that 252 people\nwould be on the trip.\n\n\n - 26 -\n\nmade a decision to book the trip through PREP Tours, nor did she\n\nmake any request of PREP Tours to take any actions in light of the\n\nlist that she had sent. In fact, in her last email to PREP Tours\n\nin the record, Ramírez communicated that Region 24's officers still\n\nhad \"to go through everything with a fine tooth-comb.\"\n\n Thus, as the District Court emphasized, PREP Tours's own\n\nevidentiary submissions show that, in the few substantive inquiry\n\nemails from Ramírez to PREP Tours -- out of what the defendants\n\nsay, without any challenge by PREP Tours, is \"a sum total of nine\"\n\nemails from her -- she consistently communicated the preliminary\n\nand limited nature of her inquiry.13 And, given that the nature\n\nand quality of the defendants' solicitation of in-forum activity\n\nwas preliminary and limited, the defendants' own forum-related\n\nactivity is a far cry from that of the defendants in C.W. Downer\n\nand Cossart, which are among the chief precedents of ours on which\n\nPREP Tours relies.14\n\n\n 13 Several, if not most, of the nine emails were sent in\nresponse to emails from PREP Tours itself simply in order to\nacknowledge the receipt of PREP Tours's messages. And, in the\nsubstantive emails among these nine, Ramírez referred to her\n\"delays\" in responding to PREP Tours's \"quote,\" further indicating\nthe intermittent nature of her communications.\n 14 We agree with the dissent that negotiations \"preliminary\"\nto a formal agreement are the foundation of a bad-faith tort claim.\nSee Diss. Op. 53. But, we highlight the preliminary nature of the\nparties' negotiations with respect to our analysis of purposeful\navailment as to both the tort and contract claims. And we do so\nnot to cast doubt on the merits of either of those claims but\ninstead because the preliminary nature of those contacts is\n\n\n\n - 27 -\n\n In C.W. Downer, for example, the out-of-forum defendant\n\nwas a Canadian corporation that had engaged an investment bank\n\nlocated in Massachusetts to sell the corporation, which the\n\ninvestment bank then spent four years trying to do before the deal\n\nfell apart and the investment bank sued the corporation in\n\nMassachusetts. 771 F.3d at 67. And, in Cossart, the out-of-forum\n\ndefendant was a firm based in Kansas that had hired an employee\n\nlocated in Massachusetts to work for the firm, which the employee\n\ndid for a \"period of years\" before suing the employer in\n\nMassachusetts for wage law violations. 804 F.3d at 18.\n\n Of course, neither C.W. Downer nor Cossart purported to\n\nestablish the minimum connection to the forum that must be shown\n\nto establish personal jurisdiction. But, none of our other cases\n\non which PREP Tours relies supports the proposition that an out-\n\nof-forum defendant would foresee being haled into court in that\n\nforum on the basis of having made the preliminary and limited type\n\n\n\ndirectly relevant to the component of the purposeful availment\ninquiry that requires us to assess whether the in-forum actions\nthat PREP Tours took in response to the defendants' contacts were\n\"foreseeable\" to the defendants or were instead \"unilaterally\"\nundertaken by the plaintiff itself. Moreover, the preliminary\nnature of contacts is also directly relevant to PREP Tours's\ncontention that the contacts show that the defendants contemplated\nan ongoing relationship with PREP Tours and that there was in fact\nsuch a relationship. In this regard, our concern is not with\nwhether the conduct alleged is tortious, but with whether that\nconduct is of a type that permits the forum to be the jurisdiction\nin which that determination is made.\n\n\n\n - 28 -\n\nof information requests to a forum-based service provider that\n\nwere made here.15 Nor are we aware of any such supporting\n\nauthority.\n\n In fact, this case in some respects provides even less\n\nbasis for finding the requisite \"substantial connection\" to the\n\nforum than did Copia, in which we found no purposeful availment.\n\n812 F.3d at 5-6. There, we rejected the contention that a Jamaica-\n\nbased resort operator purposefully availed itself of the privilege\n\nof conducting activities in Massachusetts as a result of the\n\nnegotiation and performance of a contract between the resort\n\noperator and a Massachusetts-based internet services provider.\n\nSee id. We did so even though the resort operator had voluntarily\n\nnegotiated with the provider remotely, including via emails that\n\nthe chief executive officer of the Massachusetts-based internet\n\nservices provider \"may have sent or received . . . while in\n\n\n 15\n See, e.g., Baskin-Robbins Franchising LLC v. Alpenrose\nDairy, Inc., 825 F.3d 28, 36-40 (1st Cir. 2016) (finding purposeful\navailment where an out-of-forum franchisee twice renewed its\ncontract with an in-forum franchisor, with which it had a multi-\nyear business relationship and to which it mailed 180 royalty\nchecks and delivered quarterly samples of its product); Adelson,\n652 F.3d at 79, 82-83 (finding purposeful availment where an out-\nof-forum employee \"directed regular administrative and financial\nconduct\" toward his employer's offices in the forum during multiple\nyears of employment, after he had sought out the employment\ncontract); Daynard, 290 F.3d at 46, 61-62 (finding purposeful\navailment in part because of an out-of-forum law firm's \"properly\nattributed\" \"ongoing relationship\" with an in-forum lawyer who was\nallegedly \"central\" to the firm's \"titanic recoveries\" in a complex\nlitigation).\n\n\n\n - 29 -\n\nMassachusetts\" and via meetings in Jamaica. Id. at 2-3.16 And,\n\nwe did so even though, under the contract that the parties\n\neventually concluded, in addition to providing certain services in\n\nJamaica, the provider shipped equipment from Massachusetts to the\n\nresort operator in Jamaica. Id. at 3.\n\n We explained that the resort operator's anticipation of\n\nthe \"provi[sion of] equipment and services\" by a party known to be\n\nin Massachusetts did not \"represent[] the type of purposeful\n\navailment of the privilege of conducting business in Massachusetts\n\nthat would have made it reasonably foreseeable that [the out-of-\n\nforum company] could be 'haled into court' in Massachusetts[.]\"\n\nId. at 6 (quoting Burger King, 471 U.S. at 486).17 And, in so\n\nconcluding, we emphasized that there was \"no evidence that the\n\n[resort operator] cared about the geographic origin of the\n\n\n\n\n 16\n The district court's opinion in Copia, which reviewed the\nevidentiary record in detail, noted that the Chief Executive\nOfficer of the Massachusetts-based internet services provider\n\"received emails in the course of the negotiations (and later the\nrelationship) some of which he may have read at Copia's principal\nplace of business in Massachusetts.\" Copia Commc'ns, LLC v.\nAmresorts, LP, No. 14-13056, 2015 WL 7621480, at *1 (D. Mass. Feb.\n5, 2015). And, as the District Court noted, the Chief Executive\nOfficer represented that, \"[o]n occasion, communications via\ntelephone or e-mail were sent and received while [the Chief\nExecutive Officer] was in Massachusetts.\" Id. at *3.\n 17The resort operator knew that the internet services\nprovider was based in Massachusetts because it \"addressed payment\nto [the internet services provider's] Massachusetts address.\"\nCopia, 812 F.3d at 3.\n\n\n - 30 -\n\nshipments\" of the equipment for which the resort operator had\n\ncontracted. Id. at 5.\n\n PREP Tours does assert on appeal that Ramírez reached\n\nout to PREP Tours specifically because it could undertake \"local\n\nefforts\" in Puerto Rico (as opposed to, say, the fact that it\n\nspecialized in soccer trips to that locale). But, the tour company\n\nneither alleges such in its complaint nor points to any evidence\n\nin the record to support this assertion. In fact, the record shows\n\nthat Region 24 contacted multiple travel agencies, not all of which\n\nwere located in Puerto Rico, and that Region 24 ultimately procured\n\na California-based travel agency to book its trip to Puerto Rico.18\n\n To be sure, as PREP Tours points out, one of the\n\ndefendants, Ramírez, initiated the contact with the in-forum\n\nparty, PREP Tours. And that was not the case in Copia. There,\n\nthe in-forum plaintiff initiated the negotiations that we found\n\ninsufficient to demonstrate purposeful availment there. See id.\n\nat 6. But, negotiations involving numerous contacts between the\n\nparties -- some made in the forum -- to secure an ongoing services\n\nrelationship there did then ensue. In that respect, we do not\n\n\n\n 18 PREP Tours does suggest on appeal that the defendants\nprocured this California-based company's services only after\n\"misstat[ing] their intentions to PREP Tours to enable them to get\nthe benefit of PREP Tours' local efforts.\" But, that assertion\ndoes little to show purposeful availment on the defendants' part,\nas that inquiry still turns on whether the defendants anticipated\nthat PREP Tours would undertake \"local efforts.\"\n\n\n - 31 -\n\nthink that the out-of-forum party in Copia had less substantial\n\ncontacts over the course of the relationship with the in-forum\n\nparty than the defendants did in this case.\n\n Moreover, the Supreme Court made clear in Kulko that\n\neven where it is the out-of-forum defendant who voluntarily and\n\nknowingly establishes some contacts with the forum, specific\n\njurisdiction over the defendant may still be lacking if the\n\nprospect of in-forum litigation was not foreseeable in light of\n\nthe nature and quality of that contact with the forum. See 436\n\nU.S. at 94, 97-98. And, given the preliminary and limited nature\n\nand quality of that initial inquiry to PREP Tours from Ramírez and\n\nof the defendants' other ensuing communications with the tour\n\ncompany, we conclude that this one feature of the case does not\n\nsuffice to support the conclusion that the defendants' activities\n\nestablished a \"substantial connection\" between the defendants and\n\nthe forum. Burger King, 471 U.S. at 475; cf. Sandstrom v. ChemLawn\n\nCorp., 904 F.2d 83, 89 (1st Cir. 1990) (holding that general\n\njurisdiction was lacking over an out-of-forum defendant that was\n\nlicensed to do business in the forum and had engaged in non-\n\nsubstantial advertising in the forum, and explaining that\n\n\"preparations to do business at an indeterminate future date,\n\nwithout more, cannot be confused with actually doing business\").\n\n\n\n\n - 32 -\n\n 2.\n\n PREP Tours contends, however, that, to assess purposeful\n\navailment, we must consider not only the defendants' own\n\nactivities, as reflected in the defendants' remote communications\n\nwith PREP Tours, but also the \"extensive\" activities that the tour\n\ncompany undertook in response. And we agree, consistent with\n\nCopia's recognition of the import of the factors of anticipation\n\nand performance.\n\n But, we conclude, consideration of PREP Tours's own\n\nactivities, even in combination with those undertaken by the\n\ndefendants, does not require a different conclusion from the one\n\nthat the District Court reached as to purposeful availment. And\n\nthat is both because of what the record shows about the actual\n\nactivities PREP Tours undertook and because those activities must\n\nbe considered in light of the nature of the communications that\n\nthe defendants made prior to PREP Tours having undertaken those\n\nactivities. See Burger King, 471 U.S. at 474 (\"The unilateral\n\nactivity of those who claim some relationship with a nonresident\n\ndefendant cannot satisfy the requirement of contact with the forum\n\nState.\" (quoting Hanson, 357 U.S. at 253)).\n\n In its brief on appeal, PREP Tours asserts that, in\n\nresponding to the defendants' inquiries regarding the possible\n\ntrip, it foreseeably undertook \"dozens of contacts\" in the forum\n\non the defendants' behalf that should be attributed to the\n\n\n - 33 -\n\ndefendants for jurisdictional purposes. According to PREP Tours's\n\nbrief, those contacts include \"contacting Puerto Rico-based\n\nhotels, restaurants, soccer teams, business owners, and travel\n\nagents.\"\n\n PREP Tours's complaint, however, does not allege that\n\nPREP Tours contacted a single other business, soccer team, or any\n\nperson who did not work for PREP Tours in response to the\n\ndefendants' inquiry.19 See Doyle v. Hasbro, Inc., 103 F.3d 186,\n\n190 (1st Cir. 1996) (\"In conducting our review of the case, we are\n\nlimited to those allegations contained in the amended\n\ncomplaint.\"). Nor did PREP Tours expressly rely below on any such\n\ncontacts by the tour company in its argument to the District Court\n\nthat there was personal jurisdiction over the defendants. Cf.\n\nMcCoy v. Massachusetts Inst. of Technology, 950 F.2d 13, 22 (1st\n\nCir. 1991) (\"It is hornbook law that theories not raised squarely\n\n\n\n 19 The dissent concludes that we may infer that \"each new\nitinerary involved re-engaging with service providers to discuss\nnew costs and timing (including booking hotels and flights)[.]\"\nDiss. Op. 51. But, we do not see how we may make such an inference\nwhen the plaintiff's own complaint does not make any allegation\nthat it engaged with any service providers in response to the\ndefendants' requests, let alone any allegation that they re-\nengaged with them every time the defendants made a new request.\nThe absence of such allegations from the complaint is especially\nconspicuous given that they concern the plaintiff's own conduct.\nSee Gianfrancesco v. Town of Wrentham, 712 F.3d 634, 639-40 (1st\nCir. 2013) (upholding dismissal of claims where there was \"no\nsuggestion\" that the \"missing facts should be beyond [plaintiff's]\nreach\" or that the plaintiff \"lack[ed] the information needed to\"\nallege such facts).\n\n\n - 34 -\n\nin the district court cannot be surfaced for the first time on\n\nappeal.\").\n\n PREP Tours's evidentiary submissions do show, as its\n\ncomplaint alleges, that it sent Ramírez a \"tentative rough draft\"\n\nitinerary from Puerto Rico a few days after she made her initial\n\ninquiry about the trip and that PREP Tours then modified the\n\nitinerary in some respects while in Puerto Rico. In that regard,\n\nthe properly documented actions that PREP Tours undertook in the\n\nforum in response to the defendants' inquiry were not entirely\n\n\"unilateral,\" as the District Court suggested.\n\n But, even accepting that point, we do not see how we may\n\nreasonably infer from the showing that PREP Tours makes regarding\n\nthe itinerary that it foreseeably undertook the kind of \"extensive\"\n\nactivities in response to Ramírez's remote communications that the\n\ntour company asserts on appeal that it undertook in order to put\n\ntogether and modify this proposal. After all, the promotional\n\nbrochure that PREP Tours sent to Ramírez on the very day that she\n\nfirst inquired for an offer described a pre-existing \"unique soccer\n\nprogram\" based in San Juan and Rincón that PREP Tours offered to\n\nvisiting youth soccer teams.\n\n The record does also show that PREP Tours then sent\n\nRamírez a \"tentative rough draft\" itinerary a few days later. But,\n\nthe record does not show (nor does the complaint allege) what work\n\nin Puerto Rico was done by PREP Tours in order to put together\n\n\n - 35 -\n\nthat itinerary or that there is a basis for inferring that the\n\ndefendants anticipated that PREP Tours would on the basis of their\n\ninitial request for information engage in extensive in-forum\n\nactivity.\n\n Nor, as far as the record reveals, did PREP Tours add\n\nany newly identified hotels, restaurants, or local soccer teams to\n\nthat \"tentative rough draft\" of the itinerary over the course of\n\nthe ensuing months.20 In fact, in an email to Ramírez after the\n\nlargest, albeit still quite modest, round of documented changes to\n\nthe \"tentative rough draft\" itinerary, PREP Tours itself called\n\n\"the new itinerary almost identical to the original itinerary that\n\nwe first sent you.\"\n\n We also cannot reasonably infer that the defendants\n\ncould have foreseen the type of \"extensive\" activities that PREP\n\nTours asserts to us on appeal that it undertook beyond the sending\n\nof a pre-existing tentative itinerary. PREP Tours's evidentiary\n\nsubmissions do show in this regard that the tour company sent an\n\nemail to Ramírez that mentions that it had contacted hotels in\n\nPuerto Rico after Ramírez had reached out to the tour company and\n\nthat these hotels then placed courtesy holds on certain rooms. In\n\naddition, we can reasonably infer from the email that Hakuna\n\n\n 20 The dissent states that PREP Tours \"proceeded to make\nconcrete arrangements with other businesses, including flight and\nhotel reservations.\" Diss. Op. 52. But, the complaint itself\nmakes no such allegation.\n\n\n - 36 -\n\nMatata, the third-party travel agency in Florida, sent to the\n\ndefendants regarding possibly arranging flights for them that PREP\n\nTours had at some point contacted Hakuna Matata from within Puerto\n\nRico to ask Hakuna Matata to do so.21 But, the record does not\n\nshow that the defendants had actually requested that PREP Tours\n\narrange for the courtesy holds on the hotel rooms. Rather, the\n\nrecord reveals that the defendants asked only in general and\n\ntentative terms about what PREP Tours, which represents itself as\n\na \"speciali[st]\" in such soccer tours, could \"offer.\"\n\n In fact, the record does not show that the defendants\n\never asked PREP Tours to contact any entity or person in Puerto\n\nRico on their behalf. Nor does the record show that they ever\n\nrequested any particular hotel, restaurant, soccer team, or\n\nbusiness to be included in the proposed itinerary.22 And we see\n\nno basis for concluding -- nor does PREP Tours appear to even argue\n\n-- that the defendants should \"reasonably have anticipated being\n\n'haled before a [Puerto Rico] court'\" simply in consequence of\n\n\n\n 21PREP Tours had at one point also emailed Ramírez a menu of\npossible flights, but PREP Tours acknowledged in a later email\nthat it did not book any flights on AYSO's behalf because it did\nnot yet have a sufficient indication from AYSO that the\norganization wished to proceed with the flights.\n 22 The record does show that in her email requesting a \"tweak\"\nto the \"tentative rough draft\" itinerary, Ramírez asked if it would\nbe possible to include \"all-inclusive hotels.\" PREP Tours\nexpressly rejected that request, however, explaining that it would\nnot be cost-effective to stay in all-inclusive hotels.\n\n\n - 37 -\n\nPREP Tours's efforts to obtain preliminary information about the\n\ncost and availability of hotels in Puerto Rico for the trip's\n\npossible dates, or its efforts to contact a travel agency located\n\noutside the forum regarding possible flights. Kulko, 436 U.S. at\n\n97-98 (quoting Shaffer v. Heitner, 433 U.S. 186, 216 (1977)).\n\n PREP Tours does assert in its appellate brief that AYSO\n\nhad taken similar cultural immersion trips in the past. PREP Tours\n\nthus reasons that the defendants should have reasonably foreseen\n\nthe extent of activities in Puerto Rico that would have been\n\nnecessary to produce a proposed itinerary for such a trip.23 But,\n\nwe cannot see how it would be reasonable to infer from the mere\n\nfact of this past experience that the organization would foresee\n\nthat a tour company that \"specializes\" in such trips would\n\nundertake \"extensive\" activities in Puerto Rico simply to prepare\n\na price quote and proposed itinerary for its regularly offered\n\nservice in response to a preliminary request for that information\n\nfrom a group that consistently made clear that it was considering\n\nusing other travel agencies.\n\n For all of these reasons, this case is not at all like\n\nthe imputed-contacts cases on which PREP Tours relies, namely C.W.\n\nDowner and Cossart. In C.W. Downer, the out-of-forum defendant\n\n\n 23\n Although the complaint does not allege that AYSO took\nsimilar trips in the past, one of Ramírez's emails in the record\nindicates that AYSO's teams had traveled to Costa Rica and Hawaii\nin prior years.\n\n\n - 38 -\n\ncorporation had specifically engaged the in-forum investment bank\n\nto sell the company, thus making foreseeable the fact that the\n\nbank \"contacted hundreds of potential buyers on [the\n\ncorporation's] behalf.\" 771 F.3d at 67. Likewise, in Cossart,\n\nthe out-of-forum firm had hired the employee to do the kind of\n\nwork that would make it foreseeable that he would have \"made\n\nhundreds of telephone calls and sent hundreds of e-mails on behalf\n\nof [the employer]\" from the forum. 804 F.3d at 17.\n\n Again, neither of those cases purports to set the minimum\n\nthreshold for establishing personal jurisdiction on the basis of\n\nthe activities of an in-forum plaintiff that may be imputed to an\n\nout-of-forum defendant. But, PREP Tours identifies no other\n\nprecedents that would support the conclusion that, given the\n\ncontext in which the inquiry about the trip was made, the tour\n\ncompany's properly documented activities that reasonably may be\n\nattributed to the defendants are of a nature and quality to show\n\nthat they should have reasonably anticipated being haled into court\n\nin Puerto Rico as a result. Nor, we note, does the dissent.\n\n V.\n\n Questions of purposeful availment are often, like those\n\npresented here, necessarily fact-dependent. In this area, as the\n\nSupreme Court has cautioned, there are no mathematical formulas\n\nupon which to rely. And the hues are more \"grey[]\" than \"black\n\nand white.\" See Kulko, 436 U.S. at 92 (quoting Estin, 334 U.S. at\n\n\n - 39 -\n\n545). But, in light of Copia, and the other precedents bearing on\n\nthese questions, we conclude that on this record -- especially\n\ngiven that what is missing consists of information fully known to\n\nthe in-forum party asserting jurisdiction -- there is no basis for\n\nfinding the purposeful availment requirement met for either of the\n\nplaintiff's claims.\n\n The judgment of the District Court is affirmed.\n\n\n\n - Dissenting Opinion Follows -\n\n\n\n\n - 40 -\n[END_CASE]", "role": "user" } ]
4,580,183
UNITED STATES of America, Appellee, v. Hilton RÍOS-RIVERA, Defendant, Appellant.
United States v. Rios-Rivera
2019-01-09
15-2116P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Thompson, Barron", "parties": "", "opinions": [{"author": "HOWARD, Chief Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 15-2116\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n HILTON RÍOS-RIVERA,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Aida M. Delgado-Colón, Chief U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Thompson and Barron, Circuit Judges.\n\n\n Alejandra Bird Lopez for appellant.\n Julia M. Meconiates, Assistant United States Attorney, with\nwhom Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, were on brief for appellee.\n\n\n January 9, 2019\n\f HOWARD, Chief Judge. Hilton Ríos-Rivera pled guilty to\n\ntransporting a minor to a hotel in Puerto Rico with the intent to\n\nengage in criminal sexual activity with her, in violation of the\n\nMann Act, 18 U.S.C. § 2423(a). After accepting his plea, the\n\ndistrict court sentenced Ríos to an above-guidelines incarcerative\n\nterm of 216 months. Ríos now challenges both Congress's authority\n\nto criminalize his conduct and the district court's sentence. For\n\nthe reasons discussed below, we affirm Ríos's conviction and his\n\nsentence.\n\n I.\n\n The parties do not dispute the events leading to this\n\nprosecution. All of the material conduct took place within Puerto\n\nRico. In early April 2013, Ríos, a fifty-year-old man, met the\n\nfourteen-year-old victim at a bar where he was performing with his\n\nband. While the victim's mother was in the restroom, he gave the\n\nvictim his band's compact disc and his business card and asked her\n\nto contact him. The following day, the victim's mother discovered\n\na text message from Ríos on her daughter's phone. She called Ríos\n\nto inform him of her daughter's age and warned him not to contact\n\nher daughter again. Despite those admonitions, Ríos continued\n\ncontacting the victim. In one conversation, Ríos asked the victim\n\nif she was fourteen, to which the victim responded affirmatively.\n\nIn a subsequent conversation on April 8, 2013, Ríos asked the\n\nvictim where she went to school. The victim told Ríos the name of\n\n\n - 2 -\n\fher middle school, and he arranged to pick her up during her lunch\n\nperiod the next day.\n\n On April 9, 2013, Ríos drove to the victim's middle\n\nschool. The middle school had a sign clearly labeling it as such,\n\nand its students wore school uniforms. Ríos met the victim at a\n\ngas station across the street from her school and took her to a\n\nmotel, where he had sexual intercourse with her. Ríos repeated\n\nthis behavior the next day. On April 11, at 8:00 a.m., Ríos once\n\nmore met the victim at the gas station near her middle school. He\n\nagain took her to a motel where he had sexual intercourse with her\n\nand then dropped her off at 3:00 p.m. at the bus stop near her\n\nhouse.\n\n After an investigation, in August 2013 the Puerto Rican\n\nauthorities charged Ríos with three counts of sexual assault. In\n\nFebruary 2014, a federal grand jury indicted Ríos for three\n\nviolations of § 2423(a), which prohibits \"knowingly\n\ntransport[ing]\" a minor \"in any commonwealth, territory or\n\npossession of the United States, with intent that the individual\n\nengage . . . in any sexual activity for which any person can be\n\ncharged with a criminal offense.\" Before trial, Ríos entered into\n\na plea agreement with the government. In exchange for the\n\ngovernment dropping two counts of the three-count indictment, Ríos\n\npled guilty to one count and waived his right to appeal so long as\n\n\n\n\n - 3 -\n\fthe district court sentenced him within a certain range calculated\n\nin accordance with the sentencing guidelines.\n\n The district court calculated the sentencing guidelines\n\nrange as the plea agreement suggested, but declined to sentence\n\nRíos within that range. It found that Ríos's statements at\n\nsentencing were \"geared to minimize his responsibility.\"1 During\n\nhis hearing, Ríos protested that the victim and her mother\n\nmisrepresented her age to him. These assertions contradicted not\n\nonly the victim's and her mother's statements to the probation\n\nofficer, but also the recitations in the plea agreement. The\n\ndistrict court also expressed concern that the presentence\n\ninvestigation report revealed that Ríos had been previously\n\ncharged with five counts of sexually assaulting his stepdaughter,\n\nalthough he ultimately pled guilty to one count of aggravated\n\nassault. Further, the district court noted that one of Ríos's\n\nneighbors told probation officers that Ríos \"always [had] young\n\ngirlfriends who looked to be 18 or 19 years of age.\" The district\n\ncourt also cited what it characterized as Ríos's manipulative\n\nbehavior and the government's unrebutted evidence that the victim\n\nsuffered psychological harm as a result of it. After considering\n\nthis evidence in light of the 18 U.S.C. § 3553(a) sentencing\n\n\n\n 1 The district court followed the plea agreement's\nrecommendation to reduce Ríos's offense level by three levels for\nacceptance of responsibility, pursuant to U.S.S.G. §3E1.1(b).\n\n\n - 4 -\n\ffactors, the district court announced that it would \"depart\" from\n\nthe sentencing guidelines' recommendation and sentence Ríos to 196\n\nmonths. Shortly afterward, the court corrected a mathematical\n\nerror in its initial calculation and clarified that Ríos was\n\nsentenced to 216 months, which was \"in essence . . . a variance of\n\n2.5 years.\"\n\n Ríos timely appealed. For the first time, he challenges\n\nthe constitutionality of his conviction on the grounds that\n\nCongress lacked the authority to enact § 2423(a) and that the\n\nstatute impermissibly discriminates against Puerto Ricans in\n\nviolation of the equal protection component of the Fifth\n\nAmendment's Due Process Clause. He also claims that his sentence\n\nwas procedurally and substantively unreasonable.\n\n II.\n\n As an initial matter, Ríos has forfeited his challenges\n\nto the constitutionality of § 2423(a). After his indictment, Ríos\n\nagreed to plead guilty without ever contesting the indictment in\n\nthe district court. Ríos cannot point to any instances in the\n\nrecord where he so much as hinted at the constitutional arguments\n\nhe seeks to raise here. Moreover, his plea agreement does not\n\nrefer to any potential constitutional qualms.\n\n At the time that Ríos lodged this appeal, in our circuit\n\nthis conduct would waive -- not forfeit -- Ríos's right to argue\n\non appeal that § 2423(a) is unconstitutional. See, e.g., United\n\n\n - 5 -\n\fStates v. Martinez-Martinez, 69 F.3d 1215, 1224 (1st Cir. 1995).\n\nBut the Supreme Court's decision in Class v. United States\n\nestablished that such challenges are not waived by a guilty plea\n\nalone. 138 S. Ct. 798, 803 (2018) (citing Blackledge v. Perry,\n\n417 U.S. 21 (1974) (allowing challenge to vindictive prosecution\n\nto proceed after guilty plea); Menna v. New York, 423 U.S. 61\n\n(1975) (per curiam) (permitting double jeopardy claim after guilty\n\nplea)). Because the government conceded in a Federal Rule of\n\nAppellate Procedure 28(j) letter that Class permits Ríos to raise\n\nhis arguments that his prosecution is unconstitutional, we\n\nconsider them below.\n\n Nevertheless, even if Ríos may object to his\n\nprosecution's constitutionality for the first time on appeal, his\n\ndecision not to press these arguments before the district court\n\neffects a forfeiture, even after Class. In Class, the Supreme\n\nCourt only decided that a guilty plea alone does not waive claims\n\nthat the government could not \"constitutionally prosecute\" the\n\ndefendant. 138 S. Ct. at 804 (quoting Menna, 423 U.S. at 62 n.2).\n\nNowhere in Class did the Court say that a defendant could never\n\nforfeit such \"Blackledge-Menna\" claims. It had no need to reach\n\nthe forfeiture issue because the defendant in Class had moved in\n\nthe district court to dismiss his indictment on the same\n\nconstitutional grounds that he then sought to raise on appeal.\n\n138 U.S. at 802. Class therefore does not require us to reconsider\n\n\n - 6 -\n\four prior case law and excuse a defendant's failure to preserve\n\nBlackledge-Menna arguments below. See United States v.\n\nStefanidakis, 678 F.3d 96, 99 (1st Cir. 2012) (finding forfeited\n\nappellant's double jeopardy claim and applying plain error\n\nreview).\n\n Blackledge-Menna claims are not objections to the\n\ncourt's Article III jurisdiction, and are thus not of the type\n\nthat we review de novo whenever they are brought. See United\n\nStates v. Cordero, 42 F.3d 697, 699 (1st Cir. 1994). Rather, such\n\nclaims relate to the government's authority to prosecute a\n\ndefendant, not to the court's authority to adjudicate a case. See\n\nSteel Co. v. Citizens for a Better Env't, 523 U.S. 83, 89 (1998)\n\n(\"[T]he absence of a valid (as opposed to arguable) cause of action\n\ndoes not implicate subject-matter jurisdiction, i.e., the courts'\n\nstatutory or constitutional power to adjudicate the case.\"); see\n\nalso United States v. De Vaughn, 694 F.3d 1141, 1152–53 (10th Cir.\n\n2012) (observing that if the Supreme Court had resolved Blackledge\n\nand Menna on jurisdictional grounds then the Court would have\n\ndismissed them for lack of subject matter jurisdiction).\n\n Furthermore, to the extent that the Class Court said\n\nanything about this issue, it suggested that Blackledge-Menna\n\nclaims are nonjurisdictional. For instance, the Class Court relied\n\non the fact that the advisory committee notes to Federal Rule of\n\nCriminal Procedure 11(a)(2) indicate that both jurisdictional and\n\n\n - 7 -\n\fBlackledge-Menna claims are not subject to its preservation\n\nrequirements. Class, 138 S. Ct. at 806. If Blackledge-Menna\n\nclaims were jurisdictional, then their specific inclusion -- both\n\nin the advisory committee notes and in Class -- would be\n\nsurplusage. See Nat'l Ass'n of Mfrs. v. Dep't of Def., 138 S. Ct.\n\n617, 632 (2018); In re Montreal, Me. & Atl. Ry., Ltd., 799 F.3d 1,\n\n9 (1st Cir. 2015).\n\n United States v. DiSanto does not require a different\n\nconclusion. 86 F.3d 1238 (1st Cir. 1996). There, we assumed for\n\nthe sake of argument that we review de novo an unpreserved\n\nchallenge to the statute of conviction's constitutionality. Id.\n\nat 1244. We later described that assumption as dicta and held\n\nthat constitutional challenges of the type that Ríos presents do\n\nnot relate to the court's jurisdiction. See United States v.\n\nCarrasquillo-Peñaloza, 826 F.3d 590, 593 n.3 (1st Cir. 2016) (\"[T]o\n\nthe extent that DiSanto suggests that a constitutional challenge\n\nto a statute of conviction is jurisdictional, it is dicta.\").\n\nPrior panel decisions generally bind us unless a Supreme Court\n\nopinion, en banc ruling, or statute undermines the panel decision.\n\nWilliams v. Ashland Eng'g Co., 45 F.3d 588, 592 (1st Cir. 1995).\n\nAnd, as explained above, Class does not contradict our\n\ncharacterization of DiSanto in Carrasquillo-Peñaloza.\n\n At least one other circuit, the Sixth Circuit, has\n\nreckoned with Class's impact on unpreserved constitutional\n\n\n - 8 -\n\fchallenges, and that court's interpretation of Class comports with\n\nours. See United States v. Bacon, 884 F.3d 605, 610-11 (6th Cir.\n\n2018) (applying plain error review to a constitutional challenge\n\nraised for the first time on appeal); cf. United States v. St.\n\nHubert, 909 F.3d 335, 339, 341, 344-46 (11th Cir. 2018) (applying\n\nde novo review to a preserved constitutional challenge after an\n\nunconditional guilty plea). Because nothing in Class undermines\n\nthe application of our forfeiture doctrine here, we apply it to\n\nRíos's unpreserved constitutional arguments.\n\n III.\n\n Ríos's constitutional arguments cannot surmount the high\n\nbar of plain error review applicable to forfeited claims. To show\n\nplain error, the appellant must meet a demanding four-prong test.\n\nUnited States v. Padilla, 415 F.3d 211, 218 (1st Cir. 2005) (en\n\nbanc). In particular, Ríos cannot show \"clear or obvious\" error\n\nfor any of his constitutional arguments, and he thus falters at\n\nthe test's second prong. United States v. Pabon, 819 F.3d 26, 34\n\n(1st Cir. 2016). For an error to be clear and obvious, we require\n\nan \"'indisputable' error by the judge 'given controlling\n\nprecedent.'\" United States v. Morosco, 822 F.3d 1, 21 (1st Cir.\n\n2016) (quoting United States v. Correa-Osorio, 784 F.3d 11, 22\n\n(1st Cir. 2015)).\n\n Here, Ríos makes two constitutional claims. First, he\n\nasserts that Puerto Rico's commonwealth status precludes Congress\n\n\n - 9 -\n\ffrom relying on its plenary authority to govern territories under\n\nthe Territorial Clause. See U.S. Const. art IV, § 3, cl. 2. Ríos\n\ncontends that Congress was required to promulgate § 2423(a) under\n\na different enumerated power and that the only power that might\n\njustify it, the authority to regulate interstate and international\n\ncommerce, does not. See U.S. Const. art I, § 8, cl. 3. Yet he\n\nidentifies no precedent ruling out Congress's authority to rely on\n\nthe Territorial Clause to legislate for Puerto Rico; in fact, Ríos\n\ninvites us to answer what is at best an open question of\n\nconstitutional law. As such, it was not plainly erroneous for the\n\ndistrict court to have concluded that § 2423(a) was a valid\n\nexercise of the Territorial Clause.2\n\n Second, Ríos suggests that the Mann Act's different\n\ntreatment of conduct occurring wholly within Puerto Rico from that\n\noccurring wholly within one of the fifty states violates the equal\n\nprotection component of the Fifth Amendment's Due Process Clause.\n\nHe urges us to disregard Supreme Court precedent applying rational\n\nbasis review to such claims and to instead apply heightened\n\n\n 2 None of the cases mentioned by the parties that discuss\nPuerto Rican \"sovereignty\" applied that concept to decide\nconstitutional questions about Congress's powers. See, e.g.,\nUnited States v. Quinones, 758 F.2d 40, 42 (1st Cir. 1985). We do\nnot address whether the dicta in those cases is correct, except to\nobserve that those cases do not explain how the statutes enabling\nand approving the Puerto Rican Constitution bind future\nCongresses, notwithstanding the principle that normal-course\nlegislation generally may be repealed by future Congresses. See\nUnited States v. Winstar Corp., 518 U.S. 839, 872-74 (1996).\n\n\n - 10 -\n\fscrutiny. See Harris v. Rosario, 446 U.S. 651 (1980) (per curiam);\n\nCalifano v. Torres, 435 U.S. 1, 4-5 (1978) (per curiam). We\n\ndecline the invitation; it cannot be obvious error for a district\n\nto fail to apply, sua sponte, a doctrine that would be inconsistent\n\nwith Supreme Court precedent.\n\n In the alternative, Ríos argues that § 2423(a) fails\n\nrational basis review because it prohibits only\n\nintrajurisdictional transportation of a minor for the purpose of\n\ncommitting a sex crime within \"any commonwealth, territory, or\n\npossession,\" but not a state. Congress does not plainly lack\n\nplenary power under the Territorial Clause to criminalize certain\n\nintrajurisdictional activity in those jurisdictions simply because\n\nit may not do so under the Commerce Clause within the fifty states.\n\nSee United States v. Morrison, 529 U.S. 598, 617-18 (2000). Ríos\n\ndoes not seriously challenge the notion that Congress may have\n\nlimited the Mann Act's applicability within the fifty states\n\nbecause it implicitly recognized potential constitutional limits\n\non its power. Indeed, Ríos argues that \"the federal government\n\nhas no general police . . . power\" and that Congress could not\n\ncriminalize this conduct within any one of the fifty states. He\n\nsimply asserts that § 2423(a) is irrational because Congress never\n\nexplained its justification for treating trafficking within Puerto\n\nRico differently from interstate trafficking. But there is no\n\nrequirement that Congress state its reasons for enacting a statute\n\n\n - 11 -\n\fin order for it to survive rational basis review. See U.S. R.R.\n\nRet. Bd. v. Fritz, 449 U.S. 166, 179 (1980). Because Ríos has not\n\nshown a clear or obvious error, both of his constitutional\n\nchallenges fail.3\n\n IV.\n\n Nor do Ríos's sentencing arguments warrant relief. We\n\ngenerally review preserved claims of error in the district court's\n\nimposition of a sentence \"under a deferential abuse-of-discretion\n\nstandard.\" United States v. Fuentes-Echevarria, 856 F.3d 22, 25\n\n(1st Cir. 2017) (quoting United States v. Martin, 520 F.3d 87, 92\n\n(1st Cir. 2008)). The district court's legal conclusions receive\n\nde novo review, while we evaluate its fact-finding for clear error.\n\nUnited States v. Rossignol, 780 F.3d 475, 477 (1st Cir. 2015).\n\n We turn first to Ríos's procedural challenge. At the\n\noutset, we note that Ríos forfeited any possible procedural\n\nobjection. Despite having ample opportunity to take exception to\n\nthe district court's sentence at his sentencing hearing, Ríos did\n\nnot. The district court recited the sentencing factors and the\n\nevidence that it considered before it pronounced Ríos's sentence.\n\nRíos did not object during that recitation. Moreover, after\n\nannouncing Ríos's sentence, the district court asked if there was\n\n\n 3\n Ríos does not argue that § 2423(a) fails rational basis\nreview because it is motivated by animus. See United States v.\nWindsor, 570 U.S. 744, 770 (2013). As a result, he has waived any\nsuch argument.\n\n\n - 12 -\n\f\"[a]nything else\" counsel wished to discuss, and defense counsel\n\nreplied, \"That is all.\" Consequently, Ríos forfeited his arguments\n\nthat the district court failed to provide him with notice of a\n\npossible departure sentence or to follow a departure guideline.\n\nSee United States v. Perretta, 804 F.3d 53, 57 (1st Cir. 2015).\n\nAccordingly, we review Ríos's challenge for plain error.\n\n Ríos posits that the district court committed a\n\nprocedural error because it failed to provide him with \"reasonable\n\nnotice\" before imposing a departure sentence. See Fed. R. Crim.\n\nP. 32(h). He asserts that the district court improperly issued an\n\nabove guidelines sentence based on his criminal history category's\n\nfailure to adequately represent the seriousness of his past\n\nconvictions. See U.S.S.G. §4A1.3(a)(1). This assertion is\n\nmisguided. Recently, we observed that there is no discernible\n\ndifference between departure and variance sentences. See United\n\nStates v. Santini-Santiago, 846 F.3d 487, 489-90 (1st Cir. 2017).\n\nBefore United States v. Booker, 543 U.S. 220 (2005), district\n\ncourts needed to justify deviations from the guidelines by citing\n\na departure provision. See Santini-Santiago, 846 F.3d at 490\n\n(citing Booker, 543 U.S. at 259-60). After Booker, district courts\n\ncan rely on the 18 U.S.C. § 3553(a) sentencing factors instead.\n\nBecause the guidelines' departure provisions fit neatly into the\n\n§ 3553(a) sentencing factors, we have noted that Rule 32(h)\n\n\n\n\n - 13 -\n\fcurrently \"serves no substantive purpose at all.\" See Santini-\n\nSantiago, 846 F.3d at 490.\n\n Ríos protests that at least where, as here, the district\n\ncourt said that it would \"depart\" -- as opposed to vary -- from\n\nthe sentencing guidelines, the district court must hew to Rule\n\n32(h). Nevertheless, we need not resolve whether the district\n\ncourt had to comply with Rule 32(h) or §4A1.3 here because the\n\ndistrict court imposed a variant sentence, not a departure\n\nsentence.\n\n Ríos asks us to focus on one fact in isolation, the\n\ndistrict court's stray use of the word \"depart.\" But it is clear\n\nin context that the district court misspoke and corrected itself.\n\nImmediately before announcing its intention to \"depart\" from the\n\nguidelines, the district court analyzed the § 3553(a) factors.\n\nSubsequently, in the course of correcting its calculation of the\n\nsentence's length, the district court pronounced that the sentence\n\nwas \"in essence . . . a variance.\" See United States v. Nelson,\n\n793 F.3d 202, 206-07 (1st Cir. 2015) (characterizing an above\n\nguidelines sentence as a variance despite district court's stray\n\nuse of the word \"depart\"). Therefore, the district court gave a\n\nvariant sentence and had no need to follow Rule 32(h) or §4A1.3.\n\n Next, Ríos contends that his sentence was substantively\n\nunreasonable. Ríos failed, as he did for his procedural\n\nreasonableness claim, to object to the substantive reasonableness\n\n\n - 14 -\n\fof his sentence during his sentencing hearing. As we have before,\n\nwe decline to resolve whether a defendant must preserve a\n\nsubstantive challenge to his sentence, and we assume, favorably to\n\nRíos, that he was not required to do so. See United States v.\n\nRuiz-Huertas, 792 F.3d 223, 228 (1st Cir. 2015).\n\n We accordingly review the substantive reasonableness of\n\nRíos's sentence under the abuse-of-discretion framework recited\n\nabove. Ríos contends that his 216-month (eighteen years) sentence\n\nwas disproportionate for two reasons. First, he posits that his\n\nconduct was less severe than the prototypical Mann Act violation\n\n(i.e. border-crossing human trafficking). Second, he suggests\n\nthat some states punish conduct similar to his with significantly\n\nshorter prison terms.4 Ríos's reasons are unconvincing. We defer\n\nto the district court's sentencing determinations and affirm\n\nsentences that are based on \"a plausible sentencing rationale\" and\n\nthat reflect \"a defensible result.\" United States v. Martin, 520\n\nF.3d 87, 96 (1st Cir. 2008). Moreover, when a district court\n\nchooses to impose a variant sentence, we only require that its\n\n\"plausible rationale . . . justif[ies] a variance of the magnitude\n\n\n 4For the first time in his reply brief, Ríos argues that his\nsentence was substantively unreasonable because the district court\ncalculated his offense level using the guideline applicable to\ninterjurisdictional human trafficking as opposed to the guideline\nfor statutory rape. Compare U.S.S.G. §2G1.3, with §2A3.2. We do\nnot address this argument because arguments raised only in reply\nare waived. United States v. Hall, 557 F.3d 15, 20 n.3 (1st Cir.\n2009).\n\n\n - 15 -\n\fin question.\" See United States v. Gallardo-Ortiz, 666 F.3d 808,\n\n812 (1st Cir. 2012) (quoting Martin, 520 F.3d at 91). In reviewing\n\na variant sentence, we consider the variance's magnitude but will\n\nnot conclude from the variance's size alone that the sentence was\n\nsubstantively unreasonable. Instead, we \"give due deference to\n\nthe district court's decision that the § 3553(a) factors, on a\n\nwhole, justify the extent of the variance.\" Gall v. United States,\n\n552 U.S. 38, 51 (2007).\n\n As such, we have upheld a sentence \"well-above the top\"\n\nof the guidelines range where the district court cited \"the\n\nseriousness of the defendant's criminal conduct, the defendant's\n\npast history and likelihood of recidivism, and the need for\n\ndeterrence.\" United States v. Flores-Machicote, 706 F.3d 16, 25\n\n(1st Cir. 2013); see also Gallardo-Ortiz, 666 F.3d at 817\n\n(reasoning that the district court's weighing of the § 3553(a)\n\nfactors could not provide grounds for finding a substantially\n\nabove-guidelines sentence substantively unreasonable).\n\n Here, the district court provided a plausible rationale\n\nand a defensible result. It noted Ríos's seeming lack of remorse\n\nand his decision to downplay his criminal activity. The district\n\ncourt also cited Ríos's past aggravated assault conviction\n\nstemming from his alleged rapes of his stepdaughter. Furthermore,\n\nthe district court considered Ríos's manipulative behavior to\n\npersuade the victim to engage in sexual activity. Ríos's arguments\n\n\n - 16 -\n\fdo not undermine the plausibility of this reasoning; they at most\n\nonly show that the \"universe of reasonable sentencing outcomes\"\n\nmay include a shorter sentence. See Ruiz-Huertas, 792 F.3d at\n\n229.\n\n Ríos insists that other jurisdictions' shorter sentences\n\nfor similar conduct shows the substantive unreasonableness of his\n\nsentence. Far from it. Ríos cites no case indicating that\n\nsentences in other jurisdictions set a baseline for the substantive\n\nreasonableness of federal sentences. And even if we assumed that\n\nthey do -- a problematic assumption -- Ríos fails to acknowledge\n\nthat many jurisdictions impose similar or longer sentences than\n\nthe sentence that he received. Compare, e.g., Cal. Penal Code §\n\n261.5(d) (permitting sentence up to four years), with Mass. Gen.\n\nLaws ch. 265, § 23A (mandating a minimum sentence of ten years\n\nwith a maximum of life).5 Accordingly, Ríos's sentence was\n\nsubstantively reasonable.\n\n V.\n\n For the foregoing reasons, we AFFIRM Ríos's conviction\n\nand sentence.\n\n\n\n\n 5\n Ríos's brief cites a different Massachusetts statute that\nimposes a three-year maximum incarcerative sentence. See Mass.\nGen. Laws ch. 272, § 4. Rhode Island penalizes conduct analogous\nto Ríos's conduct more harshly than Massachusetts does. See R.I.\nGen. Laws §§ 11-37-8.1, 8.2 (minimum of twenty-five years, maximum\nof life).\n\n\n - 17 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357436/", "author_raw": "HOWARD, Chief Judge"}]}
HOWARD
THOMPSON
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580183/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Hilton RÍOS-RIVERA, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 15-2116\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n HILTON RÍOS-RIVERA,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Aida M. Delgado-Colón, Chief U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Thompson and Barron, Circuit Judges.\n\n\n Alejandra Bird Lopez for appellant.\n Julia M. Meconiates, Assistant United States Attorney, with\nwhom Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, were on brief for appellee.\n\n\n January 9, 2019\n\f HOWARD, Chief Judge. Hilton Ríos-Rivera pled guilty to\n\ntransporting a minor to a hotel in Puerto Rico with the intent to\n\nengage in criminal sexual activity with her, in violation of the\n\nMann Act, 18 U.S.C. § 2423(a). After accepting his plea, the\n\ndistrict court sentenced Ríos to an above-guidelines incarcerative\n\nterm of 216 months. Ríos now challenges both Congress's authority\n\nto criminalize his conduct and the district court's sentence. For\n\nthe reasons discussed below, we affirm Ríos's conviction and his\n\nsentence.\n\n I.\n\n The parties do not dispute the events leading to this\n\nprosecution. All of the material conduct took place within Puerto\n\nRico. In early April 2013, Ríos, a fifty-year-old man, met the\n\nfourteen-year-old victim at a bar where he was performing with his\n\nband. While the victim's mother was in the restroom, he gave the\n\nvictim his band's compact disc and his business card and asked her\n\nto contact him. The following day, the victim's mother discovered\n\na text message from Ríos on her daughter's phone. She called Ríos\n\nto inform him of her daughter's age and warned him not to contact\n\nher daughter again. Despite those admonitions, Ríos continued\n\ncontacting the victim. In one conversation, Ríos asked the victim\n\nif she was fourteen, to which the victim responded affirmatively.\n\nIn a subsequent conversation on April 8, 2013, Ríos asked the\n\nvictim where she went to school. The victim told Ríos the name of\n\n\n - 2 -\n\fher middle school, and he arranged to pick her up during her lunch\n\nperiod the next day.\n\n On April 9, 2013, Ríos drove to the victim's middle\n\nschool. The middle school had a sign clearly labeling it as such,\n\nand its students wore school uniforms. Ríos met the victim at a\n\ngas station across the street from her school and took her to a\n\nmotel, where he had sexual intercourse with her. Ríos repeated\n\nthis behavior the next day. On April 11, at 8:00 a.m., Ríos once\n\nmore met the victim at the gas station near her middle school. He\n\nagain took her to a motel where he had sexual intercourse with her\n\nand then dropped her off at 3:00 p.m. at the bus stop near her\n\nhouse.\n\n After an investigation, in August 2013 the Puerto Rican\n\nauthorities charged Ríos with three counts of sexual assault. In\n\nFebruary 2014, a federal grand jury indicted Ríos for three\n\nviolations of § 2423(a), which prohibits \"knowingly\n\ntransport[ing]\" a minor \"in any commonwealth, territory or\n\npossession of the United States, with intent that the individual\n\nengage . . . in any sexual activity for which any person can be\n\ncharged with a criminal offense.\" Before trial, Ríos entered into\n\na plea agreement with the government. In exchange for the\n\ngovernment dropping two counts of the three-count indictment, Ríos\n\npled guilty to one count and waived his right to appeal so long as\n\n\n\n\n - 3 -\n\fthe district court sentenced him within a certain range calculated\n\nin accordance with the sentencing guidelines.\n\n The district court calculated the sentencing guidelines\n\nrange as the plea agreement suggested, but declined to sentence\n\nRíos within that range. It found that Ríos's statements at\n\nsentencing were \"geared to minimize his responsibility.\"1 During\n\nhis hearing, Ríos protested that the victim and her mother\n\nmisrepresented her age to him. These assertions contradicted not\n\nonly the victim's and her mother's statements to the probation\n\nofficer, but also the recitations in the plea agreement. The\n\ndistrict court also expressed concern that the presentence\n\ninvestigation report revealed that Ríos had been previously\n\ncharged with five counts of sexually assaulting his stepdaughter,\n\nalthough he ultimately pled guilty to one count of aggravated\n\nassault. Further, the district court noted that one of Ríos's\n\nneighbors told probation officers that Ríos \"always [had] young\n\ngirlfriends who looked to be 18 or 19 years of age.\" The district\n\ncourt also cited what it characterized as Ríos's manipulative\n\nbehavior and the government's unrebutted evidence that the victim\n\nsuffered psychological harm as a result of it. After considering\n\nthis evidence in light of the 18 U.S.C. § 3553(a) sentencing\n\n\n\n 1 The district court followed the plea agreement's\nrecommendation to reduce Ríos's offense level by three levels for\nacceptance of responsibility, pursuant to U.S.S.G. §3E1.1(b).\n\n\n - 4 -\n\ffactors, the district court announced that it would \"depart\" from\n\nthe sentencing guidelines' recommendation and sentence Ríos to 196\n\nmonths. Shortly afterward, the court corrected a mathematical\n\nerror in its initial calculation and clarified that Ríos was\n\nsentenced to 216 months, which was \"in essence . . . a variance of\n\n2.5 years.\"\n\n Ríos timely appealed. For the first time, he challenges\n\nthe constitutionality of his conviction on the grounds that\n\nCongress lacked the authority to enact § 2423(a) and that the\n\nstatute impermissibly discriminates against Puerto Ricans in\n\nviolation of the equal protection component of the Fifth\n\nAmendment's Due Process Clause. He also claims that his sentence\n\nwas procedurally and substantively unreasonable.\n\n II.\n\n As an initial matter, Ríos has forfeited his challenges\n\nto the constitutionality of § 2423(a). After his indictment, Ríos\n\nagreed to plead guilty without ever contesting the indictment in\n\nthe district court. Ríos cannot point to any instances in the\n\nrecord where he so much as hinted at the constitutional arguments\n\nhe seeks to raise here. Moreover, his plea agreement does not\n\nrefer to any potential constitutional qualms.\n\n At the time that Ríos lodged this appeal, in our circuit\n\nthis conduct would waive -- not forfeit -- Ríos's right to argue\n\non appeal that § 2423(a) is unconstitutional. See, e.g., United\n\n\n - 5 -\n\fStates v. Martinez-Martinez, 69 F.3d 1215, 1224 (1st Cir. 1995).\n\nBut the Supreme Court's decision in Class v. United States\n\nestablished that such challenges are not waived by a guilty plea\n\nalone. 138 S. Ct. 798, 803 (2018) (citing Blackledge v. Perry,\n\n417 U.S. 21 (1974) (allowing challenge to vindictive prosecution\n\nto proceed after guilty plea); Menna v. New York, 423 U.S. 61\n\n(1975) (per curiam) (permitting double jeopardy claim after guilty\n\nplea)). Because the government conceded in a Federal Rule of\n\nAppellate Procedure 28(j) letter that Class permits Ríos to raise\n\nhis arguments that his prosecution is unconstitutional, we\n\nconsider them below.\n\n Nevertheless, even if Ríos may object to his\n\nprosecution's constitutionality for the first time on appeal, his\n\ndecision not to press these arguments before the district court\n\neffects a forfeiture, even after Class. In Class, the Supreme\n\nCourt only decided that a guilty plea alone does not waive claims\n\nthat the government could not \"constitutionally prosecute\" the\n\ndefendant. 138 S. Ct. at 804 (quoting Menna, 423 U.S. at 62 n.2).\n\nNowhere in Class did the Court say that a defendant could never\n\nforfeit such \"Blackledge-Menna\" claims. It had no need to reach\n\nthe forfeiture issue because the defendant in Class had moved in\n\nthe district court to dismiss his indictment on the same\n\nconstitutional grounds that he then sought to raise on appeal.\n\n138 U.S. at 802. Class therefore does not require us to reconsider\n\n\n - 6 -\n\four prior case law and excuse a defendant's failure to preserve\n\nBlackledge-Menna arguments below. See United States v.\n\nStefanidakis, 678 F.3d 96, 99 (1st Cir. 2012) (finding forfeited\n\nappellant's double jeopardy claim and applying plain error\n\nreview).\n\n Blackledge-Menna claims are not objections to the\n\ncourt's Article III jurisdiction, and are thus not of the type\n\nthat we review de novo whenever they are brought. See United\n\nStates v. Cordero, 42 F.3d 697, 699 (1st Cir. 1994). Rather, such\n\nclaims relate to the government's authority to prosecute a\n\ndefendant, not to the court's authority to adjudicate a case. See\n\nSteel Co. v. Citizens for a Better Env't, 523 U.S. 83, 89 (1998)\n\n(\"[T]he absence of a valid (as opposed to arguable) cause of action\n\ndoes not implicate subject-matter jurisdiction, i.e., the courts'\n\nstatutory or constitutional power to adjudicate the case.\"); see\n\nalso United States v. De Vaughn, 694 F.3d 1141, 1152–53 (10th Cir.\n\n2012) (observing that if the Supreme Court had resolved Blackledge\n\nand Menna on jurisdictional grounds then the Court would have\n\ndismissed them for lack of subject matter jurisdiction).\n\n Furthermore, to the extent that the Class Court said\n\nanything about this issue, it suggested that Blackledge-Menna\n\nclaims are nonjurisdictional. For instance, the Class Court relied\n\non the fact that the advisory committee notes to Federal Rule of\n\nCriminal Procedure 11(a)(2) indicate that both jurisdictional and\n\n\n - 7 -\n\fBlackledge-Menna claims are not subject to its preservation\n\nrequirements. Class, 138 S. Ct. at 806. If Blackledge-Menna\n\nclaims were jurisdictional, then their specific inclusion -- both\n\nin the advisory committee notes and in Class -- would be\n\nsurplusage. See Nat'l Ass'n of Mfrs. v. Dep't of Def., 138 S. Ct.\n\n617, 632 (2018); In re Montreal, Me. & Atl. Ry., Ltd., 799 F.3d 1,\n\n9 (1st Cir. 2015).\n\n United States v. DiSanto does not require a different\n\nconclusion. 86 F.3d 1238 (1st Cir. 1996). There, we assumed for\n\nthe sake of argument that we review de novo an unpreserved\n\nchallenge to the statute of conviction's constitutionality. Id.\n\nat 1244. We later described that assumption as dicta and held\n\nthat constitutional challenges of the type that Ríos presents do\n\nnot relate to the court's jurisdiction. See United States v.\n\nCarrasquillo-Peñaloza, 826 F.3d 590, 593 n.3 (1st Cir. 2016) (\"[T]o\n\nthe extent that DiSanto suggests that a constitutional challenge\n\nto a statute of conviction is jurisdictional, it is dicta.\").\n\nPrior panel decisions generally bind us unless a Supreme Court\n\nopinion, en banc ruling, or statute undermines the panel decision.\n\nWilliams v. Ashland Eng'g Co., 45 F.3d 588, 592 (1st Cir. 1995).\n\nAnd, as explained above, Class does not contradict our\n\ncharacterization of DiSanto in Carrasquillo-Peñaloza.\n\n At least one other circuit, the Sixth Circuit, has\n\nreckoned with Class's impact on unpreserved constitutional\n\n\n - 8 -\n\fchallenges, and that court's interpretation of Class comports with\n\nours. See United States v. Bacon, 884 F.3d 605, 610-11 (6th Cir.\n\n2018) (applying plain error review to a constitutional challenge\n\nraised for the first time on appeal); cf. United States v. St.\n\nHubert, 909 F.3d 335, 339, 341, 344-46 (11th Cir. 2018) (applying\n\nde novo review to a preserved constitutional challenge after an\n\nunconditional guilty plea). Because nothing in Class undermines\n\nthe application of our forfeiture doctrine here, we apply it to\n\nRíos's unpreserved constitutional arguments.\n\n III.\n\n Ríos's constitutional arguments cannot surmount the high\n\nbar of plain error review applicable to forfeited claims. To show\n\nplain error, the appellant must meet a demanding four-prong test.\n\nUnited States v. Padilla, 415 F.3d 211, 218 (1st Cir. 2005) (en\n\nbanc). In particular, Ríos cannot show \"clear or obvious\" error\n\nfor any of his constitutional arguments, and he thus falters at\n\nthe test's second prong. United States v. Pabon, 819 F.3d 26, 34\n\n(1st Cir. 2016). For an error to be clear and obvious, we require\n\nan \"'indisputable' error by the judge 'given controlling\n\nprecedent.'\" United States v. Morosco, 822 F.3d 1, 21 (1st Cir.\n\n2016) (quoting United States v. Correa-Osorio, 784 F.3d 11, 22\n\n(1st Cir. 2015)).\n\n Here, Ríos makes two constitutional claims. First, he\n\nasserts that Puerto Rico's commonwealth status precludes Congress\n\n\n - 9 -\n\ffrom relying on its plenary authority to govern territories under\n\nthe Territorial Clause. See U.S. Const. art IV, § 3, cl. 2. Ríos\n\ncontends that Congress was required to promulgate § 2423(a) under\n\na different enumerated power and that the only power that might\n\njustify it, the authority to regulate interstate and international\n\ncommerce, does not. See U.S. Const. art I, § 8, cl. 3. Yet he\n\nidentifies no precedent ruling out Congress's authority to rely on\n\nthe Territorial Clause to legislate for Puerto Rico; in fact, Ríos\n\ninvites us to answer what is at best an open question of\n\nconstitutional law. As such, it was not plainly erroneous for the\n\ndistrict court to have concluded that § 2423(a) was a valid\n\nexercise of the Territorial Clause.2\n\n Second, Ríos suggests that the Mann Act's different\n\ntreatment of conduct occurring wholly within Puerto Rico from that\n\noccurring wholly within one of the fifty states violates the equal\n\nprotection component of the Fifth Amendment's Due Process Clause.\n\nHe urges us to disregard Supreme Court precedent applying rational\n\nbasis review to such claims and to instead apply heightened\n\n\n 2 None of the cases mentioned by the parties that discuss\nPuerto Rican \"sovereignty\" applied that concept to decide\nconstitutional questions about Congress's powers. See, e.g.,\nUnited States v. Quinones, 758 F.2d 40, 42 (1st Cir. 1985). We do\nnot address whether the dicta in those cases is correct, except to\nobserve that those cases do not explain how the statutes enabling\nand approving the Puerto Rican Constitution bind future\nCongresses, notwithstanding the principle that normal-course\nlegislation generally may be repealed by future Congresses. See\nUnited States v. Winstar Corp., 518 U.S. 839, 872-74 (1996).\n\n\n - 10 -\n\fscrutiny. See Harris v. Rosario, 446 U.S. 651 (1980) (per curiam);\n\nCalifano v. Torres, 435 U.S. 1, 4-5 (1978) (per curiam). We\n\ndecline the invitation; it cannot be obvious error for a district\n\nto fail to apply, sua sponte, a doctrine that would be inconsistent\n\nwith Supreme Court precedent.\n\n In the alternative, Ríos argues that § 2423(a) fails\n\nrational basis review because it prohibits only\n\nintrajurisdictional transportation of a minor for the purpose of\n\ncommitting a sex crime within \"any commonwealth, territory, or\n\npossession,\" but not a state. Congress does not plainly lack\n\nplenary power under the Territorial Clause to criminalize certain\n\nintrajurisdictional activity in those jurisdictions simply because\n\nit may not do so under the Commerce Clause within the fifty states.\n\nSee United States v. Morrison, 529 U.S. 598, 617-18 (2000). Ríos\n\ndoes not seriously challenge the notion that Congress may have\n\nlimited the Mann Act's applicability within the fifty states\n\nbecause it implicitly recognized potential constitutional limits\n\non its power. Indeed, Ríos argues that \"the federal government\n\nhas no general police . . . power\" and that Congress could not\n\ncriminalize this conduct within any one of the fifty states. He\n\nsimply asserts that § 2423(a) is irrational because Congress never\n\nexplained its justification for treating trafficking within Puerto\n\nRico differently from interstate trafficking. But there is no\n\nrequirement that Congress state its reasons for enacting a statute\n\n\n - 11 -\n\fin order for it to survive rational basis review. See U.S. R.R.\n\nRet. Bd. v. Fritz, 449 U.S. 166, 179 (1980). Because Ríos has not\n\nshown a clear or obvious error, both of his constitutional\n\nchallenges fail.3\n\n IV.\n\n Nor do Ríos's sentencing arguments warrant relief. We\n\ngenerally review preserved claims of error in the district court's\n\nimposition of a sentence \"under a deferential abuse-of-discretion\n\nstandard.\" United States v. Fuentes-Echevarria, 856 F.3d 22, 25\n\n(1st Cir. 2017) (quoting United States v. Martin, 520 F.3d 87, 92\n\n(1st Cir. 2008)). The district court's legal conclusions receive\n\nde novo review, while we evaluate its fact-finding for clear error.\n\nUnited States v. Rossignol, 780 F.3d 475, 477 (1st Cir. 2015).\n\n We turn first to Ríos's procedural challenge. At the\n\noutset, we note that Ríos forfeited any possible procedural\n\nobjection. Despite having ample opportunity to take exception to\n\nthe district court's sentence at his sentencing hearing, Ríos did\n\nnot. The district court recited the sentencing factors and the\n\nevidence that it considered before it pronounced Ríos's sentence.\n\nRíos did not object during that recitation. Moreover, after\n\nannouncing Ríos's sentence, the district court asked if there was\n\n\n 3\n Ríos does not argue that § 2423(a) fails rational basis\nreview because it is motivated by animus. See United States v.\nWindsor, 570 U.S. 744, 770 (2013). As a result, he has waived any\nsuch argument.\n\n\n - 12 -\n\f\"[a]nything else\" counsel wished to discuss, and defense counsel\n\nreplied, \"That is all.\" Consequently, Ríos forfeited his arguments\n\nthat the district court failed to provide him with notice of a\n\npossible departure sentence or to follow a departure guideline.\n\nSee United States v. Perretta, 804 F.3d 53, 57 (1st Cir. 2015).\n\nAccordingly, we review Ríos's challenge for plain error.\n\n Ríos posits that the district court committed a\n\nprocedural error because it failed to provide him with \"reasonable\n\nnotice\" before imposing a departure sentence. See Fed. R. Crim.\n\nP. 32(h). He asserts that the district court improperly issued an\n\nabove guidelines sentence based on his criminal history category's\n\nfailure to adequately represent the seriousness of his past\n\nconvictions. See U.S.S.G. §4A1.3(a)(1). This assertion is\n\nmisguided. Recently, we observed that there is no discernible\n\ndifference between departure and variance sentences. See United\n\nStates v. Santini-Santiago, 846 F.3d 487, 489-90 (1st Cir. 2017).\n\nBefore United States v. Booker, 543 U.S. 220 (2005), district\n\ncourts needed to justify deviations from the guidelines by citing\n\na departure provision. See Santini-Santiago, 846 F.3d at 490\n\n(citing Booker, 543 U.S. at 259-60). After Booker, district courts\n\ncan rely on the 18 U.S.C. § 3553(a) sentencing factors instead.\n\nBecause the guidelines' departure provisions fit neatly into the\n\n§ 3553(a) sentencing factors, we have noted that Rule 32(h)\n\n\n\n\n - 13 -\n\fcurrently \"serves no substantive purpose at all.\" See Santini-\n\nSantiago, 846 F.3d at 490.\n\n Ríos protests that at least where, as here, the district\n\ncourt said that it would \"depart\" -- as opposed to vary -- from\n\nthe sentencing guidelines, the district court must hew to Rule\n\n32(h). Nevertheless, we need not resolve whether the district\n\ncourt had to comply with Rule 32(h) or §4A1.3 here because the\n\ndistrict court imposed a variant sentence, not a departure\n\nsentence.\n\n Ríos asks us to focus on one fact in isolation, the\n\ndistrict court's stray use of the word \"depart.\" But it is clear\n\nin context that the district court misspoke and corrected itself.\n\nImmediately before announcing its intention to \"depart\" from the\n\nguidelines, the district court analyzed the § 3553(a) factors.\n\nSubsequently, in the course of correcting its calculation of the\n\nsentence's length, the district court pronounced that the sentence\n\nwas \"in essence . . . a variance.\" See United States v. Nelson,\n\n793 F.3d 202, 206-07 (1st Cir. 2015) (characterizing an above\n\nguidelines sentence as a variance despite district court's stray\n\nuse of the word \"depart\"). Therefore, the district court gave a\n\nvariant sentence and had no need to follow Rule 32(h) or §4A1.3.\n\n Next, Ríos contends that his sentence was substantively\n\nunreasonable. Ríos failed, as he did for his procedural\n\nreasonableness claim, to object to the substantive reasonableness\n\n\n - 14 -\n\fof his sentence during his sentencing hearing. As we have before,\n\nwe decline to resolve whether a defendant must preserve a\n\nsubstantive challenge to his sentence, and we assume, favorably to\n\nRíos, that he was not required to do so. See United States v.\n\nRuiz-Huertas, 792 F.3d 223, 228 (1st Cir. 2015).\n\n We accordingly review the substantive reasonableness of\n\nRíos's sentence under the abuse-of-discretion framework recited\n\nabove. Ríos contends that his 216-month (eighteen years) sentence\n\nwas disproportionate for two reasons. First, he posits that his\n\nconduct was less severe than the prototypical Mann Act violation\n\n(i.e. border-crossing human trafficking). Second, he suggests\n\nthat some states punish conduct similar to his with significantly\n\nshorter prison terms.4 Ríos's reasons are unconvincing. We defer\n\nto the district court's sentencing determinations and affirm\n\nsentences that are based on \"a plausible sentencing rationale\" and\n\nthat reflect \"a defensible result.\" United States v. Martin, 520\n\nF.3d 87, 96 (1st Cir. 2008). Moreover, when a district court\n\nchooses to impose a variant sentence, we only require that its\n\n\"plausible rationale . . . justif[ies] a variance of the magnitude\n\n\n 4For the first time in his reply brief, Ríos argues that his\nsentence was substantively unreasonable because the district court\ncalculated his offense level using the guideline applicable to\ninterjurisdictional human trafficking as opposed to the guideline\nfor statutory rape. Compare U.S.S.G. §2G1.3, with §2A3.2. We do\nnot address this argument because arguments raised only in reply\nare waived. United States v. Hall, 557 F.3d 15, 20 n.3 (1st Cir.\n2009).\n\n\n - 15 -\n\fin question.\" See United States v. Gallardo-Ortiz, 666 F.3d 808,\n\n812 (1st Cir. 2012) (quoting Martin, 520 F.3d at 91). In reviewing\n\na variant sentence, we consider the variance's magnitude but will\n\nnot conclude from the variance's size alone that the sentence was\n\nsubstantively unreasonable. Instead, we \"give due deference to\n\nthe district court's decision that the § 3553(a) factors, on a\n\nwhole, justify the extent of the variance.\" Gall v. United States,\n\n552 U.S. 38, 51 (2007).\n\n As such, we have upheld a sentence \"well-above the top\"\n\nof the guidelines range where the district court cited \"the\n\nseriousness of the defendant's criminal conduct, the defendant's\n\npast history and likelihood of recidivism, and the need for\n\ndeterrence.\" United States v. Flores-Machicote, 706 F.3d 16, 25\n\n(1st Cir. 2013); see also Gallardo-Ortiz, 666 F.3d at 817\n\n(reasoning that the district court's weighing of the § 3553(a)\n\nfactors could not provide grounds for finding a substantially\n\nabove-guidelines sentence substantively unreasonable).\n\n Here, the district court provided a plausible rationale\n\nand a defensible result. It noted Ríos's seeming lack of remorse\n\nand his decision to downplay his criminal activity. The district\n\ncourt also cited Ríos's past aggravated assault conviction\n\nstemming from his alleged rapes of his stepdaughter. Furthermore,\n\nthe district court considered Ríos's manipulative behavior to\n\npersuade the victim to engage in sexual activity. Ríos's arguments\n\n\n - 16 -\n\fdo not undermine the plausibility of this reasoning; they at most\n\nonly show that the \"universe of reasonable sentencing outcomes\"\n\nmay include a shorter sentence. See Ruiz-Huertas, 792 F.3d at\n\n229.\n\n Ríos insists that other jurisdictions' shorter sentences\n\nfor similar conduct shows the substantive unreasonableness of his\n\nsentence. Far from it. Ríos cites no case indicating that\n\nsentences in other jurisdictions set a baseline for the substantive\n\nreasonableness of federal sentences. And even if we assumed that\n\nthey do -- a problematic assumption -- Ríos fails to acknowledge\n\nthat many jurisdictions impose similar or longer sentences than\n\nthe sentence that he received. Compare, e.g., Cal. Penal Code §\n\n261.5(d) (permitting sentence up to four years), with Mass. Gen.\n\nLaws ch. 265, § 23A (mandating a minimum sentence of ten years\n\nwith a maximum of life).5 Accordingly, Ríos's sentence was\n\nsubstantively reasonable.\n\n V.\n\n For the foregoing reasons, we AFFIRM Ríos's conviction\n\nand sentence.\n\n\n\n\n 5\n Ríos's brief cites a different Massachusetts statute that\nimposes a three-year maximum incarcerative sentence. See Mass.\nGen. Laws ch. 272, § 4. Rhode Island penalizes conduct analogous\nto Ríos's conduct more harshly than Massachusetts does. See R.I.\nGen. Laws §§ 11-37-8.1, 8.2 (minimum of twenty-five years, maximum\nof life).\n\n\n - 17 -\n[END_CASE]", "role": "user" } ]
4,580,184
UNITED STATES of America, Appellee, v. Enrico M. PONZO, A/K/A Henry Ponzo, A/K/A Michael P. Petrillo, A/K/A Rico, A/K/A Joey, A/K/A Jeffrey John Shaw, A/K/A Jay Shaw, Defendant, Appellant.
United States v. Ponzo
2019-01-09
17-2153P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Barron", "parties": "", "opinions": [{"author": "BARRON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNos. 17-2153, 17-2154, 17-2188\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n ENRICO M. PONZO, a/k/a HENRY PONZO, a/k/a MICHAEL P. PETRILLO,\na/k/a RICO, a/k/a JOEY, a/k/a JEFFREY JOHN SHAW, a/k/a JAY SHAW,\n\n Defendant, Appellant.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Allison Koury, on brief for appellant.\n Andrew E. Lelling, United States Attorney, Dustin M. Chao,\nAssistant U.S. Attorney, Brian A. Benczkowski, Assistant Attorney\nGeneral, Matthew S. Miner, Deputy Assistant Attorney General,\nWilliam A. Glaser, Attorney, Appellate Section, Criminal Division\non brief for appellee.\n\n\n January 9, 2019\n\f BARRON, Circuit Judge. In 2014, Enrico Ponzo was\n\nconvicted on twelve federal criminal counts -- including\n\nconspiracy to commit murder in aid of racketeering, in violation\n\nof 18 U.S.C. § 1959(a)(5) -- in the District of Massachusetts.\n\nThe convictions arose from his role in the late 1980s and early\n\n1990s in a large criminal organization called \"La Cosa Nostra.\"\n\nThe District Court imposed a lengthy prison sentence and also\n\nentered a $2.25 million money judgment forfeiture. Ponzo appealed\n\nthe convictions, his sentence, and the money judgment forfeiture.\n\nWe affirmed. See United States v. Ponzo, 853 F.3d 558 (1st Cir.\n\n2017).\n\n On November 28, 2016, Ponzo moved for a new trial under\n\nFederal Rule of Criminal Procedure 33 on the basis of evidence\n\nthat he claims is newly discovered. He also moved for an\n\nevidentiary hearing to support this motion. The District Court\n\ndenied both motions without issuing an opinion. Then, in 2017,\n\nthe District Court ordered the forfeiture of a gold ring in partial\n\nsatisfaction of the previously ordered money judgment forfeiture.\n\nIn the consolidated appeals that are now before us, Ponzo\n\nchallenges all three of these orders by the District Court. None\n\nof his challenges have merit. We thus affirm.1\n\n\n 1\n With respect to Ponzo's appeal from the District Court's\ndenial of his motion for an evidentiary hearing on his motion for\na new trial, we affirm the denial of that motion without further\n\n\n\n - 2 -\n\f I.\n\n Under Rule 33, a defendant who has been convicted of a\n\nfederal offense may move for a new trial within three years on the\n\nbasis of newly discovered evidence. Fed. R. Crim. P. 33(b)(1).\n\nTo succeed on such a motion, the defendant must show (1) that \"the\n\nevidence was unknown or unavailable to the defendant at the time\n\nof trial;\" (2) that the defendant's \"failure to learn of the\n\nevidence was not due to lack of diligence by the defendant;\" (3)\n\nthat \"the evidence is material, and not merely cumulative or\n\nimpeaching;\" and (4) that the evidence \"will probably result in an\n\nacquittal upon retrial.\" United States v. Flores-Rivera, 787 F.3d\n\n1, 15 (1st Cir. 2015) (quoting United States v. González-González,\n\n258 F.3d 16, 20 (1st Cir. 2001)).\n\n If the newly discovered evidence involves impeachment\n\nevidence withheld in violation of Giglio v. United States, 405\n\nU.S. 150 (1972), then \"a 'more defendant-friendly' standard\n\napplies to the prejudice inquiry encompassed by the third and\n\nfourth prongs.\" United States v. Calderón, 829 F.3d 84, 90 (1st\n\nCir. 2016) (quoting Flores-Rivera, 787 F.3d at 15). In such a\n\ncase, a defendant \"must establish only a 'reasonable probability'\n\nof a different outcome if the government had disclosed the evidence\n\nprior to trial.\" Id. (quoting Flores-Rivera, 787 F.3d at 15-16).\n\n\ndiscussion, as Ponzo's brief to us does not address it. See United\nStates v. Zannino, 895 F.2d 1, 17 (1st Cir. 1990).\n\n\n - 3 -\n\f With respect to a preserved challenge to the denial of\n\nsuch a motion, our review is for \"manifest abuse of discretion.\"\n\nId. (quoting United States v. Alverio–Meléndez, 640 F.3d 412, 423\n\n(1st Cir. 2011)). We review unpreserved challenges only for plain\n\nerror. United States v. Scott, 877 F.3d 30, 37 (1st Cir. 2017).\n\n A.\n\n Ponzo first contends that he is entitled to a new trial\n\non the basis of a report by the Federal Bureau of Investigation\n\n(\"FBI\") that he contends was not disclosed by the government. He\n\nclaims the report indicates that the FBI had filmed a search\n\nconducted of the curtilage of a cabin in Idaho in which Ponzo had\n\nbeen living under an alias for several years prior to his arrest\n\nthere.\n\n We laid out in some detail the set of events that led to\n\nand included Ponzo's indictment, flight from Massachusetts to\n\nIdaho, arrest in Idaho, and eventual conviction and sentencing in\n\nour prior opinion. See Ponzo, 853 F.3d at 565-72. We see no need\n\nto repeat those facts here. Suffice it to say, in Ponzo's view,\n\nhis discovery of the FBI report supports his Rule 33 motion for\n\nthe following reasons.\n\n On February 7, 2011, members of a fugitive task force\n\nrun by the United States Marshals service (the \"Task Force\")\n\narrested Ponzo outside the Idaho cabin and proceeded to conduct a\n\nwarrantless search of the cabin's curtilage. An application for\n\n\n - 4 -\n\fa subsequent search warrant claimed that, during the search of the\n\ncabin's curtilage, the members of the Task Force looked through\n\nthe cabin's window and saw what appeared to be a rifle. And that\n\nwarrant in turn led to the discovery of evidence that was used\n\nagainst him at trial.2\n\n Ponzo claims that the film referenced in the FBI report\n\nexists and would show that the curtains on the window were closed\n\nat the time of the search. He thus contends that the film would\n\nreveal that the Task Force members could not have seen the rifle.\n\nThus, Ponzo claims, he is entitled, on the basis of the FBI report,\n\nto a new trial under Rule 33 due to the prejudice traceable to its\n\nnon-disclosure, given that he contends that the film would have\n\npermitted him successfully to have moved to suppress critical\n\nevidence supporting the government's case against Ponzo.\n\n Even if we assume that we must use the prejudice standard\n\nthat applies for Giglio material, we still must conclude that the\n\nDistrict Court did not abuse its discretion in rejecting this\n\nground for granting Ponzo's Rule 33 motion for a new trial. In\n\naddition to vigorously disputing Ponzo's assertion that the film\n\neven exists,3 the government contends that Ponzo has not offered\n\n\n\n 2 Ponzo contends that this was, in fact, an \"air rifle,\" but\nthis factual dispute is irrelevant to this appeal.\n 3 The government claims that the report that Ponzo cites is\nmistaken and notes that the FBI agent who prepared that report has\n\n\n\n - 5 -\n\fanything other than unfounded speculation to support his\n\ncontention that any such film -- if it did, in fact, exist -- would\n\nshow that the rifle at issue could not have been seen through the\n\nwindow during the search. And, the government's characterization\n\nof the basis for Ponzo's contention that the alleged film would\n\naid his cause -- namely, that his contention in is founded on\n\nnothing more than his own unsubstantiated speculation -- is\n\nentirely fair. After all, Ponzo points to nothing in the record\n\nto support his claims about what the film -- insofar as there even\n\nis a film -- would show. Accordingly, we cannot conclude that the\n\nDistrict Court manifestly abused its discretion in rejecting\n\nPonzo's claim that this report provides a basis for granting his\n\nRule 33 motion. See United States v. Natanel, 938 F.2d 302, 314\n\n(1st Cir. 1991) (denying a motion for a new trial on the basis of\n\nthe \"record as a whole, not on the basis of wishful thinking, rank\n\nconjecture, or unsupportable surmise\").\n\n B.\n\n Ponzo separately contends that a second FBI report,\n\nwhich he also contends was not provided to him during discovery,\n\nentitles him to a new trial, also pursuant to Rule 33. Ponzo\n\nclaims that this second report shows that FBI agents had \"actual\n\nknowledge that on the day of his arrest, Ponzo's children were\n\n\nsince sworn in an affidavit that that the report was incorrect and\nthat no such film was ever made.\n\n\n - 6 -\n\fwith their mother in Utah\" and not at the cabin in Idaho that was\n\nsearched. And, Ponzo contends, the FBI report therefore supports\n\nhis Rule 33 motion in the following way.\n\n Ponzo reasons that, if he had been aware of this aspect\n\nof the report, then he would have been able to make the case that\n\nthe initial, warrantless search of the curtilage of the cabin in\n\nIdaho amounted to an unlawful ruse. Specifically, he contends\n\nthat law enforcement falsely represented to the magistrate that\n\nthey undertook the warrantless search in order \"to make sure that\n\nthe children were not left alone.\" Because the fruits of that\n\nwarrantless search were used to obtain the subsequent search\n\nwarrant, Ponzo argues that the report would have permitted him to\n\nsuccessfully move to suppress the evidence that the government\n\nacquired during the search conducted pursuant to that warrant.\n\n In opposing Ponzo's Rule 33 motion, however, the\n\ngovernment argued to the District Court that, even if the initial\n\nwarrantless search was unlawful, its fruits were unnecessary to\n\nshow probable cause for the subsequent search warrant.\n\nAccordingly, the government contended, the fruits of the search\n\nbased on that warrant were admissible under the independent source\n\nrule and thus Ponzo's claim of prejudice based on the report's\n\nnon-disclosure is baseless.\n\n At that time, Ponzo's appeal of his convictions to our\n\nCourt was still pending. But, in rejecting Ponzo's appeal, we\n\n\n - 7 -\n\freached that same conclusion about the admissibility of the fruits\n\nof that search under the independent source rule that the\n\ngovernment asked the District Court to reach in arguing that\n\nPonzo's Rule 33 motion should be denied. Ponzo, 853 F.3d. at 573.\n\nThus, Ponzo is not free to contend otherwise now. See United\n\nStates v. Medina-Villegas, 700 F.3d 580, 585 (1st Cir. 2012) (\"The\n\nlaw of the case doctrine bars a party from resurrecting issues\n\nthat either were, or could have been, decided on an earlier\n\nappeal.\" (quotation marks and citation omitted)). Accordingly,\n\nPonzo's contention that the second FBI report might call into\n\nquestion the legality of the initial, warrantless search fails to\n\ndemonstrate that it was a \"manifest abuse of discretion\" for the\n\nDistrict Court to deny Ponzo's Rule 33 motion. United States v.\n\nJosleyn, 206 F.3d 144, 151 (1st Cir. 2000).\n\n Ponzo separately argues that this second FBI report\n\nshows that the FBI agents made false statements about the\n\nwhereabouts of Ponzo's children in an affidavit supporting the\n\napplication for the first warrant to search Ponzo's house. And,\n\nPonzo contends, \"[h]ad this information been properly disclosed,\n\nthe outcome of the District Court's ruling on the Motion to\n\n\n\n\n - 8 -\n\fSuppress [evidence from the search conducted pursuant to that\n\nwarrant]\" would have been different.4\n\n But, Ponzo did not argue to the District Court, in\n\nsupport of his Rule 33 motion, that the motion to suppress the\n\nfruits of that search would have been granted if he could have\n\nshown -- based on this second FBI report -- that the warrant was\n\nissued based on false statements to the District Court about the\n\nchildren's location at the relevant time. Thus, our review is\n\nonly for plain error. See Scott, 877 F.3d at 37. And, as Ponzo\n\nfails to argue that he can meet that demanding standard, we cannot\n\nconclude that the District Court plainly erred in denying Ponzo's\n\nmotion for a new trial on the basis of the prejudice that he\n\ncontends may be traced to the non-disclosure of this second FBI\n\nreport. Calderón, 829 F.3d at 90.5\n\n\n\n\n 4 Ponzo does note that he was denied an evidentiary hearing\non his motion to suppress and suggests, without citing any\nauthority, that the newly discovered evidence would entitle him to\nsuch a hearing. But, he does not explain how the denial of an\nevidentiary hearing on his motion to suppress suffices to show the\nprejudice that he must demonstrate under Rule 33, and no such\nargument occurs to us on this record.\n 5 In any event, we note that, as the government points out,\nthe report states, in relevant part, that Cara Pace, the children's\nmother and Ponzo's then-common law wife, \"left Ponzo with their\ntwo children.\" The report thus does not make clear whether she\nbrought the children with her when she left or whether she instead\nleft them behind with Ponzo.\n\n\n - 9 -\n\f C.\n\n We now turn to Ponzo's final ground for challenging the\n\nDistrict Court's denial of his Rule 33 motion. This challenge\n\nrests on Ponzo's allegations concerning reward money that the FBI\n\npaid to two confidential witnesses in connection with information\n\nthat led to his arrest. In particular, Ponzo contends, he\n\ndiscovered post-trial that this reward money went both to Cara\n\nPace and to her father. Ponzo thus claims that the government, by\n\nwithholding this information, prejudiced his ability to cross-\n\nexamine Cara Pace at trial, both about whether she did, in fact,\n\nreceive any of the reward money and about whether she was biased\n\nin favor of the government because of the reward.\n\n Even if we apply the more defendant-friendly Giglio-\n\nbased prejudice standard, Ponzo's challenge still fails. Flores-\n\nRivera, 787 F.3d at 15. In asserting without any substantiation\n\nthat Cara Pace did receive the reward along with her father (an\n\nassertion that the government disputes), Ponzo merely states that,\n\nif he had possessed the alleged evidence showing that Cara Pace\n\nhad received that money, then he would have been well-positioned\n\nto impeach her testimony against him at trial. But, Ponzo does\n\nnot explain how such impeachment would in and of itself show a\n\nreasonable probability of a different outcome at trial. And,\n\nnotably, Ponzo did not file a reply brief, even though the\n\ngovernment explains at some length in its responsive brief that\n\n\n - 10 -\n\fCara Pace's testimony was only relevant to \"two money laundering\n\ncounts, unlawful flight to avoid prosecution, and witness\n\ntampering\" and that her testimony was not necessary to sustain a\n\nconviction on any of these counts, given the other evidence that\n\nwas in the record. Thus, we reject Ponzo's contention that the\n\nDistrict Court's denial of his Rule 33 motion is a manifest abuse\n\nof discretion. Calderón, 829 F.3d at 90.\n\n II.\n\n We turn, finally, to Ponzo's appeal of the District\n\nCourt's November 8, 2017 order requiring forfeiture of a gold ring\n\nas partial satisfaction of the money judgment forfeiture that had\n\nbeen previously ordered. Ponzo challenges this ruling on the basis\n\nof United States v. Cunan, 156 F.3d 110, 114 (1st Cir. 1998), as\n\nhe argues that the doctrine of res judicata precludes the District\n\nCourt's ruling. Because this is a challenge to a legal conclusion,\n\nour review is de novo. United States v. George, 886 F.3d 31, 39\n\n(1st Cir. 2018).\n\n Ponzo bases his res judicata argument on the fact the\n\nring had previously been subject to a civil forfeiture action in\n\nthe District of Idaho and that this action was dismissed on March\n\n14, 2017. Ponzo contends, based on Cunan, that a criminal\n\nforfeiture action is an identical proceeding for purposes of res\n\njudicata and thus that the dismissal of the civil forfeiture action\n\n\n\n\n - 11 -\n\fin the District of Idaho is preclusive of the order of forfeiture\n\nof the gold ring in the criminal forfeiture action.\n\n The government rightly responds, however, that the rule\n\nin Cunan does not apply here because the dismissal by the District\n\nCourt in Idaho was without prejudice and a dismissal without\n\nprejudice does not carry preclusive effect. Cunan, 156 F.3d at\n\n120 (\"[R]es judicata bars a criminal forfeiture following\n\ndismissal with prejudice of a prior civil forfeiture proceeding\n\ninvolving the same property.\"); see García-Goyco v. Law Envtl.\n\nConsultants, Inc., 428 F.3d 14, 19 (1st Cir. 2005) (recognizing\n\nthat dismissal without prejudice does not have a preclusive\n\neffect). The order from the District Court of Idaho that dismissed\n\nthe civil forfeiture action granted the government's motion for\n\nvoluntary dismissal. And, Rule 41(a)(2) makes clear that a\n\nvoluntary dismissal is \"without prejudice\" unless \"state[d]\n\notherwise.\" Fed. R. Civ. P. 41(a)(2).\n\n Ponzo nevertheless contends that the dismissal was with\n\nprejudice because the order of dismissal stated that \"[the gold\n\nring] be returned to Ponzo[.]\" United States v. Real Prop. Located\n\nat 6107 Hogg Rd., Marsing, Owyhee Cty., Idaho, No. 1:11-cv-00300-\n\nCWD, slip op. at 10 (D. Idaho Mar. 14, 2017). But, read in context,\n\nthe language by the district court in Idaho that Ponzo seizes upon\n\nclearly does not constitute a statement that the dismissal is with\n\nprejudice. In moving for a voluntary dismissal pursuant to Rule\n\n\n - 12 -\n\f41(a)(2), the government expressly requested the dismissal of the\n\ncivil forfeiture action with respect to the gold ring and other\n\npersonal property in order \"to allow [it] to be available for\n\nsatisfaction of prior pending legal obligations related to the\n\ncriminal judgment of the . . . District of Massachusetts.\" Motion\n\nfor Voluntary Dismissal at 1, United States v. Real Prop. Located\n\nat 6107 Hogg Rd., Marsing, Owyhee Cty., Idaho, No. 1:11-cv-00300-\n\nCWD (D. Idaho Nov. 10, 2016). The ruling by the district court in\n\nIdaho granting that motion then expressly stated that the civil\n\nforfeiture action was being dismissed \"to allow [the gold ring] to\n\nbe applied to satisfaction of prior pending legal obligations of\n\nPonzo in the Boston criminal judgment . . . .\" Real Prop. Located\n\nat 6107 Hogg Rd., slip op. at 18. Accordingly, we reject Ponzo's\n\nchallenge to the order of forfeiture of the gold ring.\n\n III.\n\n For the foregoing reasons, the judgment below is\n\naffirmed.\n\n\n\n\n - 13 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357437/", "author_raw": "BARRON, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580184/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Enrico M. PONZO, A/K/A Henry Ponzo, A/K/A Michael P. Petrillo, A/K/A Rico, A/K/A Joey, A/K/A Jeffrey John Shaw, A/K/A Jay Shaw, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNos. 17-2153, 17-2154, 17-2188\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n ENRICO M. PONZO, a/k/a HENRY PONZO, a/k/a MICHAEL P. PETRILLO,\na/k/a RICO, a/k/a JOEY, a/k/a JEFFREY JOHN SHAW, a/k/a JAY SHAW,\n\n Defendant, Appellant.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Allison Koury, on brief for appellant.\n Andrew E. Lelling, United States Attorney, Dustin M. Chao,\nAssistant U.S. Attorney, Brian A. Benczkowski, Assistant Attorney\nGeneral, Matthew S. Miner, Deputy Assistant Attorney General,\nWilliam A. Glaser, Attorney, Appellate Section, Criminal Division\non brief for appellee.\n\n\n January 9, 2019\n\f BARRON, Circuit Judge. In 2014, Enrico Ponzo was\n\nconvicted on twelve federal criminal counts -- including\n\nconspiracy to commit murder in aid of racketeering, in violation\n\nof 18 U.S.C. § 1959(a)(5) -- in the District of Massachusetts.\n\nThe convictions arose from his role in the late 1980s and early\n\n1990s in a large criminal organization called \"La Cosa Nostra.\"\n\nThe District Court imposed a lengthy prison sentence and also\n\nentered a $2.25 million money judgment forfeiture. Ponzo appealed\n\nthe convictions, his sentence, and the money judgment forfeiture.\n\nWe affirmed. See United States v. Ponzo, 853 F.3d 558 (1st Cir.\n\n2017).\n\n On November 28, 2016, Ponzo moved for a new trial under\n\nFederal Rule of Criminal Procedure 33 on the basis of evidence\n\nthat he claims is newly discovered. He also moved for an\n\nevidentiary hearing to support this motion. The District Court\n\ndenied both motions without issuing an opinion. Then, in 2017,\n\nthe District Court ordered the forfeiture of a gold ring in partial\n\nsatisfaction of the previously ordered money judgment forfeiture.\n\nIn the consolidated appeals that are now before us, Ponzo\n\nchallenges all three of these orders by the District Court. None\n\nof his challenges have merit. We thus affirm.1\n\n\n 1\n With respect to Ponzo's appeal from the District Court's\ndenial of his motion for an evidentiary hearing on his motion for\na new trial, we affirm the denial of that motion without further\n\n\n\n - 2 -\n\f I.\n\n Under Rule 33, a defendant who has been convicted of a\n\nfederal offense may move for a new trial within three years on the\n\nbasis of newly discovered evidence. Fed. R. Crim. P. 33(b)(1).\n\nTo succeed on such a motion, the defendant must show (1) that \"the\n\nevidence was unknown or unavailable to the defendant at the time\n\nof trial;\" (2) that the defendant's \"failure to learn of the\n\nevidence was not due to lack of diligence by the defendant;\" (3)\n\nthat \"the evidence is material, and not merely cumulative or\n\nimpeaching;\" and (4) that the evidence \"will probably result in an\n\nacquittal upon retrial.\" United States v. Flores-Rivera, 787 F.3d\n\n1, 15 (1st Cir. 2015) (quoting United States v. González-González,\n\n258 F.3d 16, 20 (1st Cir. 2001)).\n\n If the newly discovered evidence involves impeachment\n\nevidence withheld in violation of Giglio v. United States, 405\n\nU.S. 150 (1972), then \"a 'more defendant-friendly' standard\n\napplies to the prejudice inquiry encompassed by the third and\n\nfourth prongs.\" United States v. Calderón, 829 F.3d 84, 90 (1st\n\nCir. 2016) (quoting Flores-Rivera, 787 F.3d at 15). In such a\n\ncase, a defendant \"must establish only a 'reasonable probability'\n\nof a different outcome if the government had disclosed the evidence\n\nprior to trial.\" Id. (quoting Flores-Rivera, 787 F.3d at 15-16).\n\n\ndiscussion, as Ponzo's brief to us does not address it. See United\nStates v. Zannino, 895 F.2d 1, 17 (1st Cir. 1990).\n\n\n - 3 -\n\f With respect to a preserved challenge to the denial of\n\nsuch a motion, our review is for \"manifest abuse of discretion.\"\n\nId. (quoting United States v. Alverio–Meléndez, 640 F.3d 412, 423\n\n(1st Cir. 2011)). We review unpreserved challenges only for plain\n\nerror. United States v. Scott, 877 F.3d 30, 37 (1st Cir. 2017).\n\n A.\n\n Ponzo first contends that he is entitled to a new trial\n\non the basis of a report by the Federal Bureau of Investigation\n\n(\"FBI\") that he contends was not disclosed by the government. He\n\nclaims the report indicates that the FBI had filmed a search\n\nconducted of the curtilage of a cabin in Idaho in which Ponzo had\n\nbeen living under an alias for several years prior to his arrest\n\nthere.\n\n We laid out in some detail the set of events that led to\n\nand included Ponzo's indictment, flight from Massachusetts to\n\nIdaho, arrest in Idaho, and eventual conviction and sentencing in\n\nour prior opinion. See Ponzo, 853 F.3d at 565-72. We see no need\n\nto repeat those facts here. Suffice it to say, in Ponzo's view,\n\nhis discovery of the FBI report supports his Rule 33 motion for\n\nthe following reasons.\n\n On February 7, 2011, members of a fugitive task force\n\nrun by the United States Marshals service (the \"Task Force\")\n\narrested Ponzo outside the Idaho cabin and proceeded to conduct a\n\nwarrantless search of the cabin's curtilage. An application for\n\n\n - 4 -\n\fa subsequent search warrant claimed that, during the search of the\n\ncabin's curtilage, the members of the Task Force looked through\n\nthe cabin's window and saw what appeared to be a rifle. And that\n\nwarrant in turn led to the discovery of evidence that was used\n\nagainst him at trial.2\n\n Ponzo claims that the film referenced in the FBI report\n\nexists and would show that the curtains on the window were closed\n\nat the time of the search. He thus contends that the film would\n\nreveal that the Task Force members could not have seen the rifle.\n\nThus, Ponzo claims, he is entitled, on the basis of the FBI report,\n\nto a new trial under Rule 33 due to the prejudice traceable to its\n\nnon-disclosure, given that he contends that the film would have\n\npermitted him successfully to have moved to suppress critical\n\nevidence supporting the government's case against Ponzo.\n\n Even if we assume that we must use the prejudice standard\n\nthat applies for Giglio material, we still must conclude that the\n\nDistrict Court did not abuse its discretion in rejecting this\n\nground for granting Ponzo's Rule 33 motion for a new trial. In\n\naddition to vigorously disputing Ponzo's assertion that the film\n\neven exists,3 the government contends that Ponzo has not offered\n\n\n\n 2 Ponzo contends that this was, in fact, an \"air rifle,\" but\nthis factual dispute is irrelevant to this appeal.\n 3 The government claims that the report that Ponzo cites is\nmistaken and notes that the FBI agent who prepared that report has\n\n\n\n - 5 -\n\fanything other than unfounded speculation to support his\n\ncontention that any such film -- if it did, in fact, exist -- would\n\nshow that the rifle at issue could not have been seen through the\n\nwindow during the search. And, the government's characterization\n\nof the basis for Ponzo's contention that the alleged film would\n\naid his cause -- namely, that his contention in is founded on\n\nnothing more than his own unsubstantiated speculation -- is\n\nentirely fair. After all, Ponzo points to nothing in the record\n\nto support his claims about what the film -- insofar as there even\n\nis a film -- would show. Accordingly, we cannot conclude that the\n\nDistrict Court manifestly abused its discretion in rejecting\n\nPonzo's claim that this report provides a basis for granting his\n\nRule 33 motion. See United States v. Natanel, 938 F.2d 302, 314\n\n(1st Cir. 1991) (denying a motion for a new trial on the basis of\n\nthe \"record as a whole, not on the basis of wishful thinking, rank\n\nconjecture, or unsupportable surmise\").\n\n B.\n\n Ponzo separately contends that a second FBI report,\n\nwhich he also contends was not provided to him during discovery,\n\nentitles him to a new trial, also pursuant to Rule 33. Ponzo\n\nclaims that this second report shows that FBI agents had \"actual\n\nknowledge that on the day of his arrest, Ponzo's children were\n\n\nsince sworn in an affidavit that that the report was incorrect and\nthat no such film was ever made.\n\n\n - 6 -\n\fwith their mother in Utah\" and not at the cabin in Idaho that was\n\nsearched. And, Ponzo contends, the FBI report therefore supports\n\nhis Rule 33 motion in the following way.\n\n Ponzo reasons that, if he had been aware of this aspect\n\nof the report, then he would have been able to make the case that\n\nthe initial, warrantless search of the curtilage of the cabin in\n\nIdaho amounted to an unlawful ruse. Specifically, he contends\n\nthat law enforcement falsely represented to the magistrate that\n\nthey undertook the warrantless search in order \"to make sure that\n\nthe children were not left alone.\" Because the fruits of that\n\nwarrantless search were used to obtain the subsequent search\n\nwarrant, Ponzo argues that the report would have permitted him to\n\nsuccessfully move to suppress the evidence that the government\n\nacquired during the search conducted pursuant to that warrant.\n\n In opposing Ponzo's Rule 33 motion, however, the\n\ngovernment argued to the District Court that, even if the initial\n\nwarrantless search was unlawful, its fruits were unnecessary to\n\nshow probable cause for the subsequent search warrant.\n\nAccordingly, the government contended, the fruits of the search\n\nbased on that warrant were admissible under the independent source\n\nrule and thus Ponzo's claim of prejudice based on the report's\n\nnon-disclosure is baseless.\n\n At that time, Ponzo's appeal of his convictions to our\n\nCourt was still pending. But, in rejecting Ponzo's appeal, we\n\n\n - 7 -\n\freached that same conclusion about the admissibility of the fruits\n\nof that search under the independent source rule that the\n\ngovernment asked the District Court to reach in arguing that\n\nPonzo's Rule 33 motion should be denied. Ponzo, 853 F.3d. at 573.\n\nThus, Ponzo is not free to contend otherwise now. See United\n\nStates v. Medina-Villegas, 700 F.3d 580, 585 (1st Cir. 2012) (\"The\n\nlaw of the case doctrine bars a party from resurrecting issues\n\nthat either were, or could have been, decided on an earlier\n\nappeal.\" (quotation marks and citation omitted)). Accordingly,\n\nPonzo's contention that the second FBI report might call into\n\nquestion the legality of the initial, warrantless search fails to\n\ndemonstrate that it was a \"manifest abuse of discretion\" for the\n\nDistrict Court to deny Ponzo's Rule 33 motion. United States v.\n\nJosleyn, 206 F.3d 144, 151 (1st Cir. 2000).\n\n Ponzo separately argues that this second FBI report\n\nshows that the FBI agents made false statements about the\n\nwhereabouts of Ponzo's children in an affidavit supporting the\n\napplication for the first warrant to search Ponzo's house. And,\n\nPonzo contends, \"[h]ad this information been properly disclosed,\n\nthe outcome of the District Court's ruling on the Motion to\n\n\n\n\n - 8 -\n\fSuppress [evidence from the search conducted pursuant to that\n\nwarrant]\" would have been different.4\n\n But, Ponzo did not argue to the District Court, in\n\nsupport of his Rule 33 motion, that the motion to suppress the\n\nfruits of that search would have been granted if he could have\n\nshown -- based on this second FBI report -- that the warrant was\n\nissued based on false statements to the District Court about the\n\nchildren's location at the relevant time. Thus, our review is\n\nonly for plain error. See Scott, 877 F.3d at 37. And, as Ponzo\n\nfails to argue that he can meet that demanding standard, we cannot\n\nconclude that the District Court plainly erred in denying Ponzo's\n\nmotion for a new trial on the basis of the prejudice that he\n\ncontends may be traced to the non-disclosure of this second FBI\n\nreport. Calderón, 829 F.3d at 90.5\n\n\n\n\n 4 Ponzo does note that he was denied an evidentiary hearing\non his motion to suppress and suggests, without citing any\nauthority, that the newly discovered evidence would entitle him to\nsuch a hearing. But, he does not explain how the denial of an\nevidentiary hearing on his motion to suppress suffices to show the\nprejudice that he must demonstrate under Rule 33, and no such\nargument occurs to us on this record.\n 5 In any event, we note that, as the government points out,\nthe report states, in relevant part, that Cara Pace, the children's\nmother and Ponzo's then-common law wife, \"left Ponzo with their\ntwo children.\" The report thus does not make clear whether she\nbrought the children with her when she left or whether she instead\nleft them behind with Ponzo.\n\n\n - 9 -\n\f C.\n\n We now turn to Ponzo's final ground for challenging the\n\nDistrict Court's denial of his Rule 33 motion. This challenge\n\nrests on Ponzo's allegations concerning reward money that the FBI\n\npaid to two confidential witnesses in connection with information\n\nthat led to his arrest. In particular, Ponzo contends, he\n\ndiscovered post-trial that this reward money went both to Cara\n\nPace and to her father. Ponzo thus claims that the government, by\n\nwithholding this information, prejudiced his ability to cross-\n\nexamine Cara Pace at trial, both about whether she did, in fact,\n\nreceive any of the reward money and about whether she was biased\n\nin favor of the government because of the reward.\n\n Even if we apply the more defendant-friendly Giglio-\n\nbased prejudice standard, Ponzo's challenge still fails. Flores-\n\nRivera, 787 F.3d at 15. In asserting without any substantiation\n\nthat Cara Pace did receive the reward along with her father (an\n\nassertion that the government disputes), Ponzo merely states that,\n\nif he had possessed the alleged evidence showing that Cara Pace\n\nhad received that money, then he would have been well-positioned\n\nto impeach her testimony against him at trial. But, Ponzo does\n\nnot explain how such impeachment would in and of itself show a\n\nreasonable probability of a different outcome at trial. And,\n\nnotably, Ponzo did not file a reply brief, even though the\n\ngovernment explains at some length in its responsive brief that\n\n\n - 10 -\n\fCara Pace's testimony was only relevant to \"two money laundering\n\ncounts, unlawful flight to avoid prosecution, and witness\n\ntampering\" and that her testimony was not necessary to sustain a\n\nconviction on any of these counts, given the other evidence that\n\nwas in the record. Thus, we reject Ponzo's contention that the\n\nDistrict Court's denial of his Rule 33 motion is a manifest abuse\n\nof discretion. Calderón, 829 F.3d at 90.\n\n II.\n\n We turn, finally, to Ponzo's appeal of the District\n\nCourt's November 8, 2017 order requiring forfeiture of a gold ring\n\nas partial satisfaction of the money judgment forfeiture that had\n\nbeen previously ordered. Ponzo challenges this ruling on the basis\n\nof United States v. Cunan, 156 F.3d 110, 114 (1st Cir. 1998), as\n\nhe argues that the doctrine of res judicata precludes the District\n\nCourt's ruling. Because this is a challenge to a legal conclusion,\n\nour review is de novo. United States v. George, 886 F.3d 31, 39\n\n(1st Cir. 2018).\n\n Ponzo bases his res judicata argument on the fact the\n\nring had previously been subject to a civil forfeiture action in\n\nthe District of Idaho and that this action was dismissed on March\n\n14, 2017. Ponzo contends, based on Cunan, that a criminal\n\nforfeiture action is an identical proceeding for purposes of res\n\njudicata and thus that the dismissal of the civil forfeiture action\n\n\n\n\n - 11 -\n\fin the District of Idaho is preclusive of the order of forfeiture\n\nof the gold ring in the criminal forfeiture action.\n\n The government rightly responds, however, that the rule\n\nin Cunan does not apply here because the dismissal by the District\n\nCourt in Idaho was without prejudice and a dismissal without\n\nprejudice does not carry preclusive effect. Cunan, 156 F.3d at\n\n120 (\"[R]es judicata bars a criminal forfeiture following\n\ndismissal with prejudice of a prior civil forfeiture proceeding\n\ninvolving the same property.\"); see García-Goyco v. Law Envtl.\n\nConsultants, Inc., 428 F.3d 14, 19 (1st Cir. 2005) (recognizing\n\nthat dismissal without prejudice does not have a preclusive\n\neffect). The order from the District Court of Idaho that dismissed\n\nthe civil forfeiture action granted the government's motion for\n\nvoluntary dismissal. And, Rule 41(a)(2) makes clear that a\n\nvoluntary dismissal is \"without prejudice\" unless \"state[d]\n\notherwise.\" Fed. R. Civ. P. 41(a)(2).\n\n Ponzo nevertheless contends that the dismissal was with\n\nprejudice because the order of dismissal stated that \"[the gold\n\nring] be returned to Ponzo[.]\" United States v. Real Prop. Located\n\nat 6107 Hogg Rd., Marsing, Owyhee Cty., Idaho, No. 1:11-cv-00300-\n\nCWD, slip op. at 10 (D. Idaho Mar. 14, 2017). But, read in context,\n\nthe language by the district court in Idaho that Ponzo seizes upon\n\nclearly does not constitute a statement that the dismissal is with\n\nprejudice. In moving for a voluntary dismissal pursuant to Rule\n\n\n - 12 -\n\f41(a)(2), the government expressly requested the dismissal of the\n\ncivil forfeiture action with respect to the gold ring and other\n\npersonal property in order \"to allow [it] to be available for\n\nsatisfaction of prior pending legal obligations related to the\n\ncriminal judgment of the . . . District of Massachusetts.\" Motion\n\nfor Voluntary Dismissal at 1, United States v. Real Prop. Located\n\nat 6107 Hogg Rd., Marsing, Owyhee Cty., Idaho, No. 1:11-cv-00300-\n\nCWD (D. Idaho Nov. 10, 2016). The ruling by the district court in\n\nIdaho granting that motion then expressly stated that the civil\n\nforfeiture action was being dismissed \"to allow [the gold ring] to\n\nbe applied to satisfaction of prior pending legal obligations of\n\nPonzo in the Boston criminal judgment . . . .\" Real Prop. Located\n\nat 6107 Hogg Rd., slip op. at 18. Accordingly, we reject Ponzo's\n\nchallenge to the order of forfeiture of the gold ring.\n\n III.\n\n For the foregoing reasons, the judgment below is\n\naffirmed.\n\n\n\n\n - 13 -\n[END_CASE]", "role": "user" } ]
4,580,185
UNITED STATES of America, Appellee, v. Johvanny AYBAR-ULLOA, Defendant, Appellant.
United States v. Aybar-Ulloa
2019-01-09
15-2377P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Lynch, Barron", "parties": "", "opinions": [{"author": "BARRON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 15-2377\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOHVANNY AYBAR-ULLOA,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Jay A. García-Gregory, U.S. District Judge]\n\n\n Before\n\n Torruella, Lynch, and Barron,\n Circuit Judges.\n\n\n Heather Clark, with whom Clark Law Office was on brief, for\nappellant.\n Margaret Upshaw, with whom Rosa Emilia Rodríguez-Vélez,\nUnited States Attorney, Mariana E. Bauzá-Almonte, Assistant United\nStates Attorney, Chief, Appellate Division, and John A. Mathews\nII, Assistant United States Attorney, were on brief, for appellee.\n\n\n January 9, 2019\n\n BARRON, Circuit Judge. Johvanny Aybar-Ulloa (\"Aybar\")\n\npleaded guilty in 2015 to two counts of drug trafficking in\n\ninternational waters while aboard a \"stateless\" vessel in\n\nviolation of the Maritime Drug Law Enforcement Act (\"MDLEA\"), 46\n\nU.S.C. §§ 70501-08. He now challenges those convictions on the\n\nground that Congress lacks the authority under Article I, Section\n\n8, Clause 10 of the United States Constitution to criminalize his\n\nconduct, given that he contends that the conduct for which he was\n\nconvicted lacks any nexus to the United States. Aybar separately\n\nchallenges the sentence that he received for those convictions.\n\nFor the reasons that follow, we affirm the convictions but vacate\n\nthe sentence.\n\n I.\n\n At the change of plea hearing, the government described,\n\nand Aybar does not dispute, the following events as having occurred\n\non August 9, 2013. HMS Lancaster, a foreign warship, was on patrol\n\nin the Caribbean Sea and launched a helicopter that spotted a small\n\nvessel dead in the water. The vessel was located in international\n\nwaters at the time and contained \"numerous packages.\"\n\n HMS Lancaster launched a small boat in order to conduct\n\na right-of-visit approach. During this approach, Aybar and his\n\nco-defendant, who were aboard the vessel with the packages, claimed\n\nto be citizens of the Dominican Republic, although the vessel bore\n\n\"no indicia of nationality.\"\n\n\n - 2 -\n\n Law enforcement personnel aboard the small boat\n\nconducting the approach then determined that the vessel was\n\n\"without nationality,\" as Aybar conceded to the District Court was\n\ntrue, and boarded it.1 The men on board the vessel, including\n\nAybar, were transferred to HMS Lancaster along with the packages\n\nthat were taken from the vessel.\n\n A narcotics field test performed on board HMS Lancaster\n\nconfirmed that the packages contained cocaine. At this point,\n\nAybar was transferred to a United States Coast Guard vessel and\n\ntransported to Puerto Rico, where he was held in custody by United\n\nStates law enforcement.\n\n On August 13, 2013, a federal grand jury in the District\n\nof Puerto Rico returned an indictment against Aybar. The\n\nindictment charged him under the MDLEA with conspiring to possess\n\nwith intent to distribute cocaine on board a vessel subject to the\n\njurisdiction of the United States, in violation of 46 U.S.C.\n\n§ 70506(b) (count one), and aiding and abetting possession with\n\nintent to distribute cocaine on board a vessel subject to the\n\njurisdiction of the United States, in violation of 46 U.S.C.\n\n§§ 70502(c)(1)(A), 70503(a)(1), 70504(b)(1), 70506(a), and 18\n\n\n\n 1The government represented in a filing in the District Court\nthat the law enforcement personnel were United States Coast Guard\nmembers who were embarked on HMS Lancaster. However, the\ngovernment did not mention this allegation while describing the\nfactual basis for the convictions at the change of plea hearing.\n\n\n - 3 -\n\nU.S.C. § 2 (count two). A forfeiture allegation, under 46 U.S.C.\n\n§ 70507, was also made against Aybar.\n\n The MDLEA provides in part: \"While on board a covered\n\nvessel, an individual may not knowingly or intentionally . . .\n\nmanufacture or distribute, or possess with intent to manufacture\n\nor distribute, a controlled substance . . . .\" 46 U.S.C.\n\n§ 70503(a)(1). A \"covered vessel\" includes \"a vessel subject to\n\nthe jurisdiction of the United States.\" Id. § 70503(e)(1). A\n\n\"vessel subject to the jurisdiction of the United States\" is in\n\nturn defined to include \"a vessel without nationality.\" Id.\n\n§ 70502(c)(1)(A). And, as we mentioned, Aybar conceded below that\n\nhe was on board a vessel \"without nationality\" at the time he was\n\napprehended.\n\n On October 2, 2014, Aybar filed a motion to dismiss the\n\nindictment for lack of jurisdiction. He argued that Congress\n\nlacked the power to criminalize his conduct, given the lack of\n\nwhat Aybar claimed to be any constitutionally sufficient nexus\n\nbetween his charged conduct and the United States, because\n\nCongress's power under Article I of the Constitution \"[t]o define\n\nand punish Piracies and Felonies committed on the high Seas, and\n\nOffences against the Law of Nations,\" U.S. Const. art. I, § 8, cl.\n\n10, did not extend to his conduct in such circumstances.\n\n The government opposed Aybar's motion. The District\n\nCourt denied Aybar's motion on December 22, 2014 and issued a nunc\n\n\n - 4 -\n\npro tunc opinion and order on January 5, 2015. The District Court\n\nacknowledged that the vessel was not a \"vessel of the United\n\nStates\" within the meaning of the MDLEA, 46 U.S.C. § 70503(e)(1);\n\nthat Aybar was not a citizen of the United States; and that the\n\nother members of the crew were not either. But, the District Court\n\nreasoned, because \"international law allows the United States 'to\n\ntreat stateless vessels as if they were its own,'\" it followed\n\nthat \"persons navigating the high seas aboard a vessel without\n\nnationality have effectively waived their rights to object to the\n\nexercise of jurisdiction over them by the United States.\" The\n\nDistrict Court therefore concluded that Aybar's \"as-applied\n\nconstitutional challenge fails\" because his vessel was stateless.\n\n Following a change of plea hearing, Aybar entered a\n\nguilty plea to all charges on March 11, 2015. At that hearing,\n\nAybar engaged in the following colloquy with the Magistrate Judge:\n\n The Magistrate: Now, do you admit that in\n addition to the conspiracy you actually and\n the other co-defendants possessed with the\n intent to distribute these substances, this\n cocaine?\n\n Aybar: Yes, Your Honor.\n\n The Magistrate: In the same circumstances on\n board this vessel without nationality and\n therefore subject to jurisdiction of the\n United States?\n\n Aybar: Yes, Your Honor.\n\n\n\n\n - 5 -\n\n The District Court accepted Aybar's guilty plea, and the\n\ncase proceeded to sentencing. A probation officer prepared a\n\npresentence report (\"PSR\") using the 2014 United States Sentencing\n\nGuidelines Manual. The PSR assigned Aybar a base offense level of\n\nthirty-eight under the United States Sentencing Guidelines. After\n\nreceiving the PSR, Aybar filed an objection in which he argued\n\nthat two levels should be subtracted from his offense level under\n\n§ 3B1.2(b) of the Guidelines because he was a minor participant.\n\n At sentencing, the District Court declined to reduce his\n\noffense level as Aybar had argued and sentenced Aybar to 135 months\n\nin prison. Aybar timely filed a notice appealing the judgment\n\nentered against him.\n\n II.\n\n In prior cases in our circuit that have presented\n\nconstitutional challenges to MDLEA convictions not unlike the one\n\nthat Aybar now makes to us, the defendant had either waived or\n\nforfeited the constitutional argument challenging the scope of\n\nCongress's power under Article I to criminalize conduct supposedly\n\nlacking a sufficient nexus to the United States. See, e.g., United\n\nStates v. Diaz-Doncel, 811 F.3d 517 (1st Cir. 2016) (waived);\n\nUnited States v. Nueci-Peña, 711 F.3d 191 (1st Cir. 2013)\n\n\n\n\n - 6 -\n\n(forfeited).2 But that is not the case here. Aybar timely raised\n\nbelow the challenge that he now makes on appeal. And while Aybar\n\ndid plead guilty to the offenses that underlie the convictions\n\nthat he challenges on appeal, the government concedes that, in\n\nconsequence of the Supreme Court's holding in Class v. United\n\nStates, 138 S. Ct. 798 (2018), Aybar's guilty plea does not bar\n\nhim from challenging Congress's constitutional power to\n\ncriminalize his conduct pursuant to its Article I powers.\n\n The government does separately argue that Aybar waived\n\nhis right to bring this challenge because he conceded in the plea\n\ncolloquy that the vessel he was on board was \"without nationality\"\n\n-- which is one of the MDLEA's definitions for a \"vessel subject\n\nto the jurisdiction of the United States.\" 46 U.S.C.\n\n§ 70502(c)(1)(A). But, as we read the record, Aybar conceded only\n\nthat his conduct fell within the MDLEA's scope and not that the\n\nMDLEA was a valid exercise of Congress's constitutional power under\n\nArticle I insofar as it covered his conduct.\n\n\n\n\n 2 We rejected a similar as-applied challenge to the\nconstitutionality of the MDLEA under the Define and Punish Clause\non plain error review in Nueci-Peña. See 711 F.3d at 196-98. In\ndoing so, we noted that of all the circuits to have addressed the\nargument that this Clause \"does not authorize Congress to enact\nthe MDLEA, which punishes conduct without a connection to the\nUnited States,\" at least one has squarely rejected that argument,\nand none has held otherwise. Id. at 198 (citing United States v.\nEstupinan, 453 F.3d 1336, 1338-39 (11th Cir. 2006)).\n\n\n - 7 -\n\n Thus, we review de novo the district court's rejection\n\nof Aybar's constitutional challenge to Congress's power to\n\ncriminalize the conduct for which he was convicted. See United\n\nStates v. Bravo, 489 F.3d 1, 6 (1st Cir. 2007). Nevertheless, as\n\nwe will explain, the particular constitutional challenge to\n\nCongress's power that Aybar develops fails because, although we\n\nhave not had occasion directly to address it before, related\n\nprecedent from our circuit precludes us from accepting the premise\n\nconcerning international law on which his constitutional challenge\n\nto congressional power rests.\n\n A.\n\n Aybar contends that Congress exceeded its authority\n\nunder Article I in criminalizing his conduct under the MDLEA\n\nbecause Congress lacked the necessary power to criminalize such\n\nconduct under the Define and Punish Clause. That Clause gives\n\nCongress the power \"[t]o define and punish Piracies and Felonies\n\ncommitted on the high Seas, and Offences against the Law of\n\nNations.\" U.S. Const. art. I, § 8, cl. 10. In responding to\n\nAybar's constitutional challenge, the government does not identify\n\nany other source of constitutional authority pursuant to which\n\nCongress may criminalize Aybar's conduct. We thus focus here\n\nsolely on the dispute between the parties regarding the scope of\n\nthe power that the Define and Punish Clause affords Congress to\n\ncriminalize Aybar's conduct.\n\n\n - 8 -\n\n Aybar's constitutional challenge relies heavily on Judge\n\nTorruella's dissent in United States v. Cardales-Luna, 632 F.3d\n\n731 (1st Cir. 2011).3 Aybar first contends, by quoting Judge\n\nTorruella's dissent, that \"piracy\" under international law is only\n\n\"robbery when committed upon the sea\" and thus does not encompass\n\ndrug trafficking. Id. at 745 (Torruella, J., dissenting). For\n\nthat reason, he contends that Congress has no power to criminalize\n\nhis conduct pursuant to the \"Piracies\" component of the Clause in\n\nquestion.\n\n Aybar further contends, again by quoting the following\n\nportion of Judge Torruella's Cardales-Luna dissent, that the \"'Law\n\nof Nations' is generally understood to be the eighteenth and\n\nnineteenth-century term for 'customary international law'\" and\n\nthat customary international law does not recognize drug\n\ntrafficking as an offense against the law of nations. Id. at 745-\n\n47. Thus, Aybar contends, the \"law of nations\" component of the\n\nClause at issue also does not give Congress the power to\n\ncriminalize the conduct for which he was convicted.\n\n\n\n 3 The defendant in Cardales-Luna did not raise a\nconstitutional challenge to Congress's power under Article I to\nregulate conduct aboard stateless vessels on the high seas absent\nany nexus between that conduct and the United States. 632 F.3d at\n737. Judge Torruella nevertheless addressed this issue in his\ndissent because he concluded that this constitutional challenge\nimplicated the court's subject matter jurisdiction. Id. The\nmajority disagreed, however, and thus declined to address the issue\nsua sponte. Id.\n\n\n - 9 -\n\n Of course, Aybar recognizes that, even if these\n\narguments are right, he still must show that Congress could not\n\ncriminalize his conduct pursuant to its power to define and punish\n\n\"Felonies\" committed on the high seas. He acknowledges, as\n\nprecedent compels him to do, that this portion of the Clause gives\n\nCongress an independent source of power to define and punish\n\nconduct on the high seas, separate and apart from the power that\n\nCongress has under the other portions of the Clause that we have\n\njust discussed. See United States v. Smith, 18 U.S. 153, 158-59\n\n(1820).\n\n In arguing that the portion of the Clause that empowers\n\nCongress to punish \"Felonies\" on the high seas does not permit\n\nCongress to criminalize his conduct, Aybar contends that Congress\n\ncannot define and punish his conduct as a \"Felon[y]\" within the\n\nmeaning of Article I, Section 8, Clause 10, because there was no\n\nnexus between that conduct and the United States.4 And Aybar bases\n\nthat argument entirely on an assertion about the way that\n\ninternational law -- which he appears to treat as having been\n\n\n\n 4Specifically, Aybar asserts the following: He was\n\"interdicted in a vessel in international waters\"; \"no offense\noccurred within the territorial jurisdiction of the United\nStates\"; his vessel neither departed from nor was bound for the\nUnited States; \"there is no evidence that the cocaine aboard the\nvessel was intended for distribution\" in the United States; he\n\"did not commit any offense against a vessel of the United States\";\nand he was \"located by and taken in custody aboard\" a foreign\nwarship.\n\n\n - 10 -\n\ninvariant in the relevant respect from the Founding to the present\n\n-- treats drug trafficking and a nation's power to prosecute it in\n\ncircumstances like those involved here.\n\n We note that, in advancing this argument about the\n\ncontent of international law, Aybar is less than clear in\n\nexplaining the precise extent to which, in his view, international\n\nlaw reflects limits on national power that the Constitution\n\nincorporates in the portion of Article I that empowers Congress to\n\ndefine and punish \"Felonies\" committed on the high seas. But, be\n\nthat as it may, it is at least clear that Aybar's constitutional\n\ncontention with respect to the scope of Congress's power under\n\nthis part of Article I is necessarily premised on the underlying\n\nassertion that he makes about the content of international law as\n\nit relates to a nation's ability to criminalize conduct on the\n\nhigh seas where there is no more connection between that conduct\n\nand the United States than there is here. And so we now turn to\n\na consideration of that international-law-based premise for his\n\nconstitutional argument concerning Congress's power, for, unless\n\nwe accept that premise, his constitutional challenge must fail.5\n\n\n 5 We note that the Supreme Court addressed Congress's\nconstitutional power to define and punish piracies and felonies in\na series of cases in the early nineteenth century. See United\nStates v. Furlong, 18 U.S. (5 Wheat.) 184, 195-98 (1820); Smith,\n18 U.S. (5 Wheat.) at 158-60; United States v. Palmer, 16 U.S. (3\nWheat.) 610, 630 (1818); cf. United States v. Holmes, 18 U.S. (5\nWheat.) 412 (1820); United States v. Klintock, 18 U.S. (5 Wheat.)\n\n\n\n - 11 -\n\n B.\n\n In asserting this premise, Aybar again relies heavily on\n\nthe reasoning set forth in portions of Judge Torruella's dissent\n\nin Cardales-Luna. Aybar begins by quoting Judge Torruella's\n\nconclusion that, \"under the international law doctrine of\n\nuniversal jurisdiction (UJ), a nation may prosecute certain\n\nserious offenses even though they have no nexus to its territory\n\nor its nationals, and no impact on its territory or its citizens.\"\n\nCardales-Luna, 632 F.3d at 740. But, Aybar goes on to contend,\n\nonce again by quoting Judge Torruella's dissent in Cardales-Luna,\n\nthat \"[o]ther than in the case of those limited crimes, there is\n\nno general authority to regulate purely foreign criminal conduct\n\nthat does not have a demonstrable connection with the United\n\nStates.\" Id. at 741. Aybar then ties up his constitutional\n\nargument by asserting (yet again by quoting Judge Torruella's\n\ndissent in Cardales-Luna) that, because \"[d]rug trafficking is not\n\nrecognized in customary international law as a universally\n\ncognizable offense,\" id. at 745, the MDLEA may not afford universal\n\njurisdiction for drug trafficking as a \"Felon[y]\" within the\n\nmeaning of Article I, Section 8, Clause 10 of the Constitution in\n\na case in which the defendant's conduct did not have any more nexus\n\nto the United States than was present here.\n\n\n144 (1820). But, Aybar makes no argument that these cases resolved\nhis constitutional argument in his favor.\n\n\n - 12 -\n\n The problem for Aybar in advancing this argument is that,\n\nnotwithstanding his contention that international law does not\n\nauthorize the United States to prosecute conduct like his own due\n\nto what he claims to be the lack of any nexus between that conduct\n\nand the United States, we set forth a contrary view of\n\ninternational law in United States v. Victoria, 876 F.2d 1009 (1st\n\nCir. 1989) (Breyer, J.). There, we considered a challenge to a\n\nconviction for possessing marijuana under a predecessor statute to\n\nthe MDLEA based on conduct aboard a stateless vessel that was\n\ncaptured off the coast of Colombia. Id. at 1009-10. And, in the\n\ncourse of rejecting that defendant's challenge to his drug\n\nconviction, we explained first that \"international law . . . gives\n\nthe United States . . . authority to treat stateless vessels as if\n\nthey were its own.\" Id. at 1010 (second omission in original)\n\n(quoting United States v. Smith, 680 F.2d 255, 258 (1st Cir.\n\n1982)). Then, on the basis of that understanding of international\n\nlaw's treatment of stateless vessels, we concluded: \"Thus the\n\nUnited States, as a matter of international law, may prosecute\n\ndrug offenders on stateless ships found on the high seas.\" Id.6\n\n\n 6At oral argument, when asked why our holding in Victoria\nwas not dispositive, Aybar's counsel responded that Victoria did\nnot address the distinction between statelessness under the MDLEA\nand statelessness for the purposes of international law. But,\nwhile Aybar's brief asserts in a footnote that the MDLEA's\ndefinition of statelessness is broader than international law's,\nhe does not develop any argument for distinguishing Victoria on\n\n\n\n - 13 -\n\n To be sure, Victoria did not fully spell out why its\n\nconclusion that international law authorizes the United States to\n\ntreat a stateless vessel as its own means that, as a matter of\n\ninternational law, the United States could prosecute a person on\n\nboard such a vessel for a drug offense. Victoria nevertheless\n\nmade it clear that its ruling was definitive as to this point\n\nthrough its approving and extensive references to out-of-circuit\n\nprecedents holding similarly and \"explain[ing] in detail why this\n\nis so.\" Id. at 1011 (citing United States v. Alvarez-Mena, 765\n\nF.2d 1259, 1265-66 (5th Cir. 1985); United States v. Pinto-Mejia,\n\n720 F.2d 248, 260-61 (2d Cir. 1983); United States v. Marino-\n\nGarcia, 679 F.2d 1373, 1382-83 (11th Cir. 1982); United States v.\n\nRubies, 612 F.2d 397, 402-03 (9th Cir. 1979); United States v.\n\nCortes, 588 F.2d 106, 110 (5th Cir. 1979)).7\n\n\nthis basis. See United States v. Zannino, 895 F.2d 1, 17 (1st\nCir. 1990).\n 7 For this reason, we do not find significant the fact, not\nmentioned by the defendant here, that there was some evidence in\nVictoria -- as there is not here -- that the vessel in that case\nwas potentially bound for the United States. See 876 F.2d at 1010.\nIn fact, there is no indication in Victoria that the statute at\nissue made proof of such a tie between the defendant's conduct and\nthe United States necessary to convict the defendant. Nor did we\nqualify our holding that \"the United States, as a matter of\ninternational law, may prosecute drug offenders on stateless ships\nfound on the high seas\" in light of that evidence. Id. We also\nnote that Victoria, in asserting the United States' broad authority\nunder international law to prosecute persons who are not citizens\nof the United States for drug trafficking on a stateless vessel in\ninternational waters, made no reference to our decision the year\nbefore in United States v. Robinson, 843 F.2d 1, 3-4 (1st Cir.\n\n\n\n - 14 -\n\n We do recognize that Victoria did not consider a\n\nconstitutional challenge to Congress's power under Article I, such\n\nas Aybar now makes to us. In Victoria, the defendant argued merely\n\nthat the statute there at issue did not reach his conduct in light\n\nof the Charming Betsy canon, see Murray v. The Schooner Charming\n\nBetsy, 6 U.S. (2 Cranch) 64, 118 (1804) (reasoning that \"an act of\n\nCongress ought never to be construed to violate the law of nations\n\nif any other possible construction remains\"), given that he claimed\n\nthat \"international law would not permit the United States to\n\nconvict him for possessing marijuana . . . so far from the United\n\nStates.\" Victoria, 876 F.2d at 1010. But, even though our ruling\n\nin Victoria did not purport to address the constitutional question\n\nof congressional power that Aybar now raises, its reasoning is no\n\nless dispositive as to the assertion about international law that\n\nsupplies the premise for the constitutional argument that Aybar\n\ndoes make. Accordingly, because Aybar's constitutional challenge\n\nrests on an assertion about the content of international law that,\n\nas a panel, we are not free to accept in light of our prior\n\nprecedent, we must reject his constitutional contention regarding\n\n\n\n1988), in which we observed in dicta that there was a \"forceful\"\nargument to be made that international law would not justify the\nUnited States' prosecution of drug offenders on a foreign-flagged\nship found on the high seas where there was no clear proof that\nthe ship was bound for the United States and where the United\nStates acted without the flag state's consent.\n\n\n\n - 15 -\n\nthe scope of Congress's power. See United States v. Wurie, 867\n\nF.3d 28, 34 (1st Cir. 2017) (explaining the law of the circuit\n\nrule). And, on that basis, we affirm his convictions.8\n\n\n 8 The dissent disputes the merits of Victoria's holding as to\ninternational law, as well as the necessity of Victoria having\nresolved the Charming Betsy issue on the basis of that\nunderstanding of international law. See Diss. Op. 30-33. But,\nunder the law of the circuit doctrine, what matters is simply\nwhether Victoria did rely on that proposition for its holding that\nthe Charming Betsy canon did not require a narrower construction\nof the MDLEA, and it is clear that Victoria did. In fact, in\ndefending that view of international law, Victoria cited\nextensively to out-of-circuit precedent and included\nparentheticals in which those circuits set forth that very\nproposition of international law. See Victoria, 876 F.2d at 1011.\nWe thus are not free to treat that aspect of the Victoria decision\nas mere dicta. We note, too, that other circuits, since Victoria,\nhave continued to rule the same way. See, e.g., United States v.\nCampbell, 743 F.3d 802, 809-12 (11th Cir. 2014); United States v.\nCaicedo, 47 F.3d 370, 372-73 (9th Cir. 1995); United States v.\nMartinez-Hidalgo, 993 F.2d 1052, 1056-57 (3d Cir. 1993).\n The dissent also observes that Smith, 680 F.2d 255, a decision\nthat predates Victoria, indicates that Victoria's view of\ninternational law is mistaken. See Diss. Op. 31-32. The dissent\nfurther notes that Victoria relied on Smith. See id. However, as\nthe dissent itself points out, Victoria did not cite the full\npassage from Smith that the dissent contends is at odds with\nVictoria's assertion about international law. See Victoria, 876\nF.2d at 1010. And, the particular part of that passage from Smith\nthat Victoria did cite does not support the dissent's view. Nor\ndoes the dissent contend that it does. See Diss. Op. 31-32. In\nany event, we do not read even the full passage from Smith to\nsupport the dissent's view of it. See Diss. Op. 31. In that\npassage, Smith concludes that \"[the United States] has the\nauthority to treat stateless vessels as if they were its own,\" 680\nF.2d at 258, and then follows that conclusion by emphasizing the\ncircumstances of the case in front of it, stating that the United\nStates \"has [that] authority . . ., particularly when engaged in\nconduct affecting United States vessels and having an effect within\nthe jurisdiction of the United States,\" id. (emphasis added). Read\nas a whole, therefore, the passage from Smith on which the dissent\nplaces much weight suggests that evidence of a nexus between the\n\n\n\n - 16 -\n\n There is, in addition to Victoria, another of our\n\nprecedents that is at odds with Aybar's contention that\n\ninternational law of its own force requires there to be more of a\n\nnexus between a person charged with drug trafficking and the nation\n\nthat wishes to criminally prosecute it than is present here. That\n\nprecedent is United States v. Cardales, 168 F.3d 548 (1st Cir.\n\n1999), which concerned the application of the MDLEA to drug\n\nsmugglers on the high seas (there, on a foreign-flagged ship).\n\nId. at 551-52.\n\n In Cardales, the defendants argued that the Due Process\n\nClause, rather than the Define and Punish Clause, \"requires the\n\ngovernment to prove a nexus between their criminal conduct and the\n\nUnited States in a prosecution for violating the MDLEA,\" 168 F.3d\n\nat 552, which is an argument that we rejected there, id. at 553,\n\nand that Aybar does not press here.9 Moreover, Cardales, unlike\n\nAybar's case, involved a foreign-flagged vessel, id. at 552, and\n\nwe noted that the flag nation had consented to the assertion of\n\n\nconduct at issue and the United States is not necessary in order\nfor the United States to exercise the authority that Smith\nrecognizes.\n 9 We note that Aybar's brief mentions that the warship that\nintercepted the stateless vessel on which he was aboard was a\nforeign one. That was not the case in either Victoria or Cardales\n(a point Aybar does not himself point out), but Aybar makes no\nargument as to why this difference should matter with respect to\nwhether the exercise of United States jurisdiction over his conduct\naboard the stateless vessel was consistent with international law.\nSee Zannino, 895 F.2d at 17.\n\n\n - 17 -\n\njurisdiction by the United States, id., which we identified as key\n\nto our holding rejecting Cardales's due process challenge on ground\n\nof a lack of any nexus.\n\n But, apart from that aspect of our ruling, we also stated\n\nin Cardales that the application of the MDLEA in that case was\n\nconsistent with the \"protective principle\" of international law,\n\nwhich permits a nation \"to assert jurisdiction over a person whose\n\nconduct outside the nation's territory threatens the nation's\n\nsecurity.\" Id. at 553 (quoting Robinson, 843 F.2d at 3). And, in\n\nso concluding, Cardales relied on a congressional finding in the\n\nMDLEA that \"trafficking in controlled substances aboard vessels is\n\na serious international problem and is universally condemned[,\n\nand] . . . presents a specific threat to the security . . . of the\n\nUnited States.\" Id. (alteration and omissions in original)\n\n(quoting 46 U.S.C. app. § 1902). Cardales then explained that\n\n\"application of the MDLEA to the defendants is consistent with the\n\nprotective principle of international law because Congress has\n\ndetermined that all drug trafficking aboard vessels threatens our\n\nnation's security.\" Id. (emphasis added).\n\n There is no indication in this aspect of Cardales's\n\nreasoning that its broad assertion regarding the United States'\n\nentitlement to assert protective jurisdiction, under international\n\nlaw, was limited only to cases in which the flag nation has\n\nconsented to the United States' assertion of jurisdiction over a\n\n\n - 18 -\n\nvessel and those on board it. See id. at 553. Thus, the language\n\non this point in Cardales is, like the language referenced in\n\nVictoria concerning international law that we have described\n\nabove, directly contrary to Aybar's sole constitutional\n\ncontention, given the assertion about international law on which\n\nhis contention rests.\n\n Moreover, Aybar makes no argument as to why,\n\nnotwithstanding our conclusion to the contrary in Cardales, his\n\nconduct does not fall within the United States' protective\n\njurisdiction. He instead contends only that his crime of drug\n\ntrafficking is outside the United States' universal jurisdiction.\n\nHe thus develops no argument for reconsidering our statement in\n\nCardales concluding that the scope of protective jurisdiction\n\nencompasses conduct of the kind present here. See Zannino, 895\n\nF.2d at 17.\n\n III.\n\n Aybar next argues that the District Court erroneously\n\ndenied him a minor participant reduction under § 3B1.2(b) of the\n\nSentencing Guidelines based on five factors that he contends show\n\nthat he was a minor participant. That guideline provides that\n\n\"[i]f the defendant was a minor participant in any criminal\n\nactivity, decrease by 2 levels.\" U.S. Sentencing Guidelines Manual\n\n§ 3B1.2(b) (2014).\n\n\n\n\n - 19 -\n\n Application Note 3(C) of the November 2015 edition of\n\nthe Sentencing Guidelines sets forth the five factors on which\n\nAybar relies in challenging his sentence. U.S. Sentencing\n\nGuidelines Manual § 3B1.2, cmt. n.3(C) (2015). But, as the\n\ngovernment points out, he was sentenced according to the November\n\n2014 edition of the Guidelines in effect at the time of his October\n\n21, 2015 sentencing, and the application note to the minor-role\n\nguideline in that edition did not include those specific factors.\n\n Nevertheless, Aybar did file a letter under Rule 28(j)\n\ncalling our attention to our ruling in the companion case to this\n\none, United States v. Sarmiento-Palacios, 885 F.3d 1, 6 (1st Cir.\n\n2018), which we decided after all briefing was complete in this\n\ncase. See Fed. R. App. P. 28(j). Sarmiento held that Amendment\n\n794 to the Sentencing Guidelines, which added the five factors to\n\nthe application note, clarifies the Commission's original intent\n\nregarding § 3B1.2 and therefore that it does apply retroactively.\n\nId. And, in Sarmiento we therefore vacated the sentence and\n\nremanded for resentencing, so that the District Court could have\n\nan opportunity to apply the new factors. Id.\n\n The government argues that vacating the sentence and\n\nremanding for resentencing is not appropriate here, because, even\n\nunder the factors set out in Amendment 794, Aybar would still have\n\nbeen denied the minor-role reduction. But the same argument was\n\n\n\n\n - 20 -\n\nunsuccessful in Sarmiento, and we reject it for the same reasons\n\nthat we did there:\n\n we think it prudent to leave that\n determination in the hands of the able\n district court judge. Accordingly, a remand\n is justified to allow the sentencing court the\n opportunity to consider the \"Commission's\n current policy position[,] . . . [which] may\n have some influence on the judge's ultimate\n discretionary choice of sentence.\"\n\nId. (alterations and omission in original) (quoting United States\n\nv. Ahrendt, 560 F.3d 69, 79 (1st Cir. 2009)).\n\n IV.\n\n We therefore affirm the convictions. But we vacate the\n\nDistrict Court's sentence and remand for resentencing under the\n\nCommission's clarified guidance, as reflected in Amendment 794.\n\n\n\n - Separate Opinion Follows -\n\n\n\n\n - 21 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357438/", "author_raw": "BARRON, Circuit Judge"}, {"author": "TORRUELLA, Circuit Judge, joining in part and dissenting", "type": "dissent", "text": "TORRUELLA, Circuit Judge, joining in part and dissenting\n\nin part. I join the majority with respect to Aybar's sentencing\n\nappeal in light of our recent decision in Sarmiento-Palacios, 885\n\nF.3d at 6. I respectfully dissent, however, from the majority's\n\nconclusion that our precedent requires us to affirm Aybar's\n\nconviction. As the majority notes, none of this Court's precedent\n\ndirectly considered a constitutional challenge to Congress's power\n\nto criminalize conduct pursuant to Article I, section 8, clause\n\n10. Therefore, that precedent should not bind this panel.\n\nMoreover, the related but non-binding precedent upon which the\n\nmajority relies diverges from international and constitutional law\n\nprinciples governing Congress' powers to criminalize the conduct\n\nin Aybar's case. These principles, as explained below, lead to\n\nthe conclusion that the application of the MDLEA to Aybar was\n\nunconstitutional.\n\n The majority correctly identifies that Aybar's\n\nconviction hinges on the provision of the Define and Punish clause\n\nwhich gives Congress the authority to define and punish \"Felonies\"\n\non the high seas. See Smith, 18 U.S. at 159; U.S. Const. art. I,\n\n§ 8, cl. 10. But as explained below, the majority's reliance and\n\napplication of this court's precedent to the issues in Aybar's\n\ncase is inapt.\n\n The majority opinion relies to a great degree upon the\n\nrationale in Cardales, 168 F.3d at 553. See Maj. Op. 17-19. But,\n\n\n - 22 -\n\nas the majority in this case concedes, the facts and issues before\n\nthe court in Cardales were quite different than those in the\n\npresent case. The holding in Cardales relied only on the flag\n\nnation's consent in concluding that no nexus was required under\n\nthe Due Process Clause. 168 F.3d at 553 (\"[D]ue process does not\n\nrequire the government to prove a nexus between a defendant's\n\ncriminal conduct and the United States in a prosecution under the\n\nMDLEA when the flag nation has consented to the application of\n\nUnited States law to the defendants. . . . We therefore hold that\n\nwhen individuals engage in drug trafficking aboard a vessel, due\n\nprocess is satisfied when the foreign nation in which the vessel\n\nis registered authorizes the application of United States law to\n\nthe persons on board the vessel.\"(emphasis added)).10 That holding\n\nis inapplicable to the case at hand, in which there is no such\n\nconsent, and the majority's reliance on it is therefore erroneous.\n\nThe Cardales defendants did not raise a challenge to Congress's\n\nconstitutional authority to enact the MDLEA as applied to them,\n\nand, by arguing that due process required proof of a nexus between\n\ntheir conduct and the United States, see id. at 552-53, inherently\n\naccepted that the enacting authority had the constitutional power\n\nto create the law under which those due process rights arise. Not\n\nso in our case.\n\n\n 10 Consent, after all, is the cornerstone of international\nlaw. See generally The Paquete Habana, 175 U.S. 677 (1900).\n\n\n - 23 -\n\n Notably, the Cardales court discussed international law\n\nprinciples in dicta for the sole purpose of explaining why that\n\ncourt's application of the MDLEA to the facts in that case did not\n\nviolate the precepts of due process. In its superfluous discussion\n\nof international law's protective principle, the Cardales court\n\nlooked to a presumptuous Congressional statement that \"trafficking\n\nin controlled substances aboard vessels is a serious international\n\nproblem and . . . presents a specific threat to the security . . .\n\nof the United States.\" Id. (second alteration in original)\n\n(quoting 46 U.S.C. app. § 1902). The Cardales court leaned on\n\nthis Congressional statement for support that \"application of the\n\nMDLEA is consistent with the protective principle of international\n\nlaw.\" Id. (citing United States v. Martinez-Hidalgo, 993 F.2d\n\n1052, 1056 (3d Cir. 1993)). The majority here leans almost as\n\nheavily on this statement. But, the accompanying parenthetical in\n\nCardales, in expressing that the application of the MDLEA to drug\n\ntrafficking on the high seas is not \"fundamentally unfair,\" id.\n\n(quoting Martinez-Hidalgo, 993 F.2d at 1056), makes clear that the\n\nCardales court's dicta regarding international law was used only\n\nto support its due process analysis. While the logic of Cardales\n\nmay be persuasive to some, that case's conclusion is not binding\n\nto the as-applied constitutional challenge that Aybar raises here.\n\n I pause for a moment to note that the Congressional\n\nstatement relied upon by the Cardales court does not make an\n\n\n - 24 -\n\napplication of the MDLEA to entirely foreign nationals and foreign\n\nconduct, with no nexus to the United States, consistent with the\n\n\"protective principle\" of international law. The protective\n\nprinciple of international law requires a showing that the\n\nregulated conduct has some nexus or effect on the prosecuting\n\nnation; the protective principle cannot be invoked simply through\n\na blanket assertion that some disfavored conduct creates a\n\n\"specific threat to the security\" of that nation. Id. (quoting 46\n\nU.S.C. app. § 1902). As I discussed in my dissent in United States\n\nv. Angulo-Hernández, some sort of actual cognizable threat to the\n\nnation is required under international law for an assertion of the\n\nprotective principle. 576 F.3d 59, 61 (1st Cir. 2009) (Torruella,\n\nJ., dissenting).\n\n A broad grant of power to the executive branch to\n\nprosecute any and all vessels carrying illegal substances that are\n\nnot in the United States' waters, are not headed for or departing\n\nfrom the United States, are not flying the United States' flag,\n\nand are not carrying United States nationals, is plainly\n\ninconsistent with international law. Id. (citing Restatement\n\n(Third) of U.S. Foreign Relations Law § 402 cmt. f). Allowing a\n\nnation to make such a broad assertion under the guise of the\n\nprotective principle with no substantial showing of a nexus to\n\nthat nation would render the protective principle coterminous with\n\nthe doctrine of universal jurisdiction. Id. And, while there may\n\n\n - 25 -\n\nbe a global consensus about the negative effects of drug\n\ntrafficking, it is not a universal crime -- despite vigorous\n\nattempts by the United States at international law forums to make\n\nit one11 -- and cannot be prosecuted under the \"universality\n\nprinciple\" of international law.\n\n Having established that our precedent does not compel us\n\nto reject Aybar's as-applied constitutional challenge, I next\n\naddress the constitutional limitations of Congress' ability to\n\nregulate Felonies on the high seas under the mandates of\n\nconstitutional and international law. I am emphatically of the\n\nview that doing so requires us to hold that Congress' power under\n\nthis clause is necessarily limited to instances where there is a\n\nnexus between the conduct underlying the felony and the United\n\nStates. See Cardales-Luna, 632 F.3d at 739 (Torruella, J.,\n\ndissenting); Angulo-Hernández, 576 F.3d at 62 (Torruella, J.,\n\ndissenting); cf. United States v. James-Robinson, 515 F. Supp.\n\n1340, 1346 (S.D. Fla. 1981) (holding that the court did not have\n\nsubject matter jurisdiction because the defendant's conduct had no\n\n\"effect whatsoever\" on the U.S.); United States v. Angola, 514 F.\n\n\n 11\n See United States v. Bellaizac-Hurtado 700 F.3d 1245, 1256\n(11th Cir. 2012) (\"The negotiators of the Rome Statute repeatedly\nreferred to drug crimes as 'treaty crimes' only . . . [a]nd several\ndelegates expressed the opinion that drug crimes had no place in\na statute dealing with international crimes and should be addressed\nat the national level.\" (internal quotation marks and citation\nomitted)); see also Cardales-Luna, 632 F.3d at 745 (Torruella, J.,\ndissenting).\n\n\n - 26 -\n\nSupp. 933, 936 (S.D. Fla. 1981) (asserting that jurisdiction was\n\nvalid under the protective principle because the ship was close\n\nenough to the U.S. to assume a \"real, not an imaginary, potential\n\nfor harm\" to U.S. narcotics laws). Because Congress cannot grant\n\nthe government the authority to prosecute conduct beyond that which\n\nthe Define and Punish clause allows Congress to regulate, see\n\nUnited States v. Furlong, 18 U.S. (5 Wheat) 184, 196-97 (1820),\n\nand the Define and Punish clause does not give Congress the ability\n\nto regulate Felonies on the high seas having no nexus to the United\n\nStates, Congress cannot create laws -- such as the MDLEA --\n\ngranting the government the authority to prosecute conduct by\n\nforeign individuals on the high seas that has no nexus to the\n\nUnited States. See Eugene Kontorovich, Beyond the Article I\n\nHorizon: Congress's Enumerated Powers and Universal Jurisdiction\n\nover Drug Crimes, 93 Minn. L. Rev. 1191, 1212 (2009). \"[S]uch\n\ngeneral jurisdiction over high seas offenses had never been\n\nsuggested . . . [nor] intended,\" and if the Constitution did not\n\nexplicitly forbid Congress from legislating against foreign\n\nconduct, it was \"only because it was too silly for the Framers to\n\nhave contemplated.\" Id. (citing Hon. John Marshall, Speech\n\nDelivered in the House of Representatives, in 4 The Papers of John\n\nMarshall, 92-93, 96, 102 (Charles T. Cullen & Leslie Tobias eds.,\n\n1984)); cf. Furlong, 18 U.S. at 196-97. Just as Congress cannot\n\ncreate criminal laws regulating the conduct of foreign nationals\n\n\n - 27 -\n\nin foreign countries with no effect on the United States, see\n\nUnited States v. Nippon Paper Industries Co., Ltd., 109 F.3d 1, 4-\n\n9 (1st Cir. 1997); Restatement (Third) of U.S. Foreign Relations\n\nLaw § 402(1)(c), Congress cannot create laws regulating the\n\nconduct of foreign nationals on foreign vessels over which the\n\nUnited States has no jurisdiction because those vessels are\n\nnavigating on international waters, and there is no indication\n\nthat they have either left from the United States or are headed\n\nthereto.\n\n Early Supreme Court cases support the requirement of\n\nsuch a nexus. When first faced with the opportunity to determine\n\nthe scope of Congress's ability to legislate extraterritorially,\n\nthe Supreme Court held that, aside from universal jurisdiction\n\ncrimes (that is, certain serious offenses recognized by\n\ninternational law that all nations may prosecute even without a\n\nnexus or impact to that nation's territory or citizens), there\n\nmust be a nexus between the United States and the regulated\n\nconduct. See United States v. Klintock, 18 U.S. (5 Wheat) 144,\n\n151-52 (1820). This principle has been continually upheld, see\n\nUnited States v. Pizzarusso, 388 F.2d 8, 10 (2d Cir. 1968) (\"Acts\n\ndone outside a jurisdiction, but intended to produce . . .\n\ndetrimental effects within it, justify a state in punishing the\n\ncause of the harm.\" (emphasis added) (quoting Strassheim v. Daily,\n\n221 U.S. 280, 285 (1911) (Holmes, J.))); see also United States v.\n\n\n - 28 -\n\nColumba-Colella, 604 F.2d 356, 358 (5th Cir. 1979) (\"When an\n\nallegedly criminal act is performed by an alien on foreign soil[,]\n\ncourts in the United States have long held that if jurisdiction is\n\nto be extended over that act, it must be supported by either the\n\nProtective or Objective territorial theory.\"), including in cases\n\ninvolving early interpretations of anti-drug trafficking laws\n\nsimilar to the MDLEA in situations involving stateless vessels.\n\nSee e.g., United States v. Smith, 680 F.2d 255, 257-258 (1st Cir.\n\n1982); James-Robinson, 515 F. Supp. at 1346-1347; Angola, 514 F.\n\nSupp. at 935.\n\n Here, Aybar was interdicted on a vessel in international\n\nwaters, far from the United States. His vessel did not depart\n\nfrom the United States nor was there any evidence that it was bound\n\nfor the United States. No concrete evidence suggests that the\n\ndrugs aboard this specific vessel were intended for distribution\n\nin the United States. Aybar did not commit any offense against a\n\nvessel or citizen of the United States, or within the United\n\nStates' territory. Save for the fact that he was intercepted by\n\nofficers of the United States Coast Guard, who in fact were aboard\n\na foreign vessel, there is absolutely nothing connecting Aybar to\n\nthe United States. The United States nexus was artificially\n\nprovided by the actions of the United States, a unique condition\n\nunheard of in the criminal law -- in which it is the government\n\nthat provides one of the elements of the crime that is charged.\n\n\n - 29 -\n\nGiven this lack of nexus, the Felonies provision of the Define and\n\nPunish clause does not give Congress the authority to create laws\n\ncriminalizing Aybar's conduct.\n\n Because Cardales did not address the issues presented in\n\nthis case, and constitutional and international law do not support\n\nthe conclusion that the majority reaches, this Court need not and\n\nshould not adopt the rationale in Cardales to reject Aybar's\n\nconstitutional challenge. See United States v. Irizarry-Colón,\n\n848 F.3d 61, 69 (1st Cir. 2017) (declaring that the district court\n\nwas \"led astray\" by a prior panel's statement concerning an issue\n\nnot before that prior panel); see also Cohens v. Virginia, 19 U.S.\n\n(6 Wheat) 264, 399 (1821) (\"It is a maxim not to be disregarded,\n\nthat general expressions, in every opinion, are to be taken in\n\nconnection with the case in which those expressions are used. If\n\nthey go beyond the case, they may be respected, but ought not to\n\ncontrol the judgment in a subsequent suit when the very point is\n\npresented for decision.\"). The logical force of the Cardales dicta\n\nis insufficient to govern this Court's decision when the opposite\n\nconclusion is consistent with constitutional and international law\n\nprinciples.\n\n Nor does Aybar's admission that he was aboard a vessel\n\nwithout nationality provide a nexus to give the United States\n\nprescriptive jurisdiction to prosecute his conduct under its\n\ndomestic laws. The majority points to Victoria, in which this\n\n\n - 30 -\n\nCourt broadly stated that \"as United States courts have interpreted\n\ninternational law, that law gives the 'United States . . .\n\nauthority to treat stateless vessels as if they were its own.\"\n\n876 F.2d at 1010 (quoting Smith, 680 F.2d at 248). See Maj. Op.\n\n14. But, for the following reasons, this court should not rely\n\ntoo heavily on that statement.\n\n First, in Victoria, there was evidence of a nexus between\n\nthe conduct on the stateless vessel and the United States. 876\n\nF.2d at 1010 (noting that \"the Coast Guard found . . . navigational\n\ncharts indicating a course for the . . . southern tip of Florida\").\n\nTherefore, the Victoria court did not need to consider whether the\n\nUnited States could in fact treat stateless vessels as its own\n\nwhen there was no nexus between the conduct at issue and the United\n\nStates, for the charts provided evidence of a U.S. nexus. Second,\n\nthe full quotation from Smith, only part of which the Victoria\n\ncourt cited,12 itself actually supports the existence of a nexus\n\nrequirement. See Smith, 680 F.2d at 258 (stating that the United\n\nStates \"has authority to treat stateless vessels as if they were\n\nits own, particularly when engaged in conduct affecting United\n\n\n\n\n 12\n Victoria, 876 F.2d at 1010 (\"[A]s United States courts have\ninterpreted international law, that law gives the 'United States\n. . . authority to treat stateless vessels as if they were its\nown.'\" (second alteration in the original) (quoting Smith, 680\nF.2d at 258)).\n\n\n - 31 -\n\nStates vessels and having an effect within the jurisdiction of the\n\nUnited States\" (emphasis added)).\n\n Third, like in Cardales, the defendant in Victoria\n\nappealed his conviction on grounds not at issue here. The Victoria\n\ndefendant partly based his argument on the Charming Betsy canon,\n\nin with the Supreme Court stated that \"an act of Congress ought\n\nnever to be construed to violate the law of nations if any other\n\npossible construction remains.\" Murray v. The Schooner Charming\n\nBetsy, 6 U.S. (2 Cranch) 64, 118 (1804). As the majority\n\nrecognizes, the defendant in Victoria asserted that Congress did\n\nnot intend for the MDLEA to apply extraterritoriality, implicit in\n\nwhich is acceptance of Congress' authority to enact such a law.\n\nSee 876 F.2d at 1010. Unlike the Victoria defendant, Aybar asserts\n\nthat Congress did not have the authority under the Define and\n\nPunish clause to apply the MDLEA to regulate extraterritorial\n\nconduct having no nexus to the United States. Furthermore, the\n\nstatement from Victoria, if read to foreclose any nexus requirement\n\nother than a defendant's presence aboard a stateless vessel, would\n\nrun afoul of international law (and therefore the Charming Betsy\n\ncannon), which is clear that it allows countries to prescribe law\n\nextraterritorially only when there is some connection between the\n\nconduct and that country. See Restatement (Third) of U.S. Foreign\n\nRelations Law § 402. Therefore, the majority in this case\n\n\n\n\n - 32 -\n\noverstates the extent to which Victoria forecloses the argument\n\nthat Aybar presents.\n\n Before moving forward, I must fall on my own sword and\n\nrecognize that I, like the Victoria court and the majority here,\n\nhave made too broad an assertion. See Sarmiento-Palacios, 885\n\nF.3d at 7 (Torruella, J., concurring) (\"And while the United States\n\n(like all nations) does have universal jurisdiction over stateless\n\nvessels . . . .\"); Cardales-Luna, 632 F.3d at 747 (\"These\n\nprinciples regarding [universal] jurisdiction have been relaxed to\n\ninclude . . . stateless vessels.\"). But, \"it is never too late to\n\n'surrende[r] former views to a better considered position.'\" South\n\nDakota v. Wayfair, Inc., 138 S. Ct. 2080, 2100 (2018) (Thomas, J.,\n\nconcurring) (quoting McGrath v. Kristensen, 340 U.S. 162, 178\n\n(1950) (Jackson, J., concurring)). And, upon further reflection,\n\nI now realize that international law's allowance of any nation to\n\nprevent the operation of stateless vessels does not confer\n\njurisdiction on that nation to prosecute the individuals aboard\n\nthose vessels under that nation's domestic criminal codes.\n\n It is widely accepted that international law confers the\n\nright of any nation to approach and \"visit\" a vessel if it is\n\nsuspected that the vessel is stateless. See United Nations\n\nConvention on the Law of the Sea [hereinafter \"UNCLOS\"] art. 110,\n\nDec. 10, 1982, 1833 U.N.T.S. 397. But, international law\n\ndistinguishes between a nation's authority to prescribe law\n\n\n - 33 -\n\nextraterritorially as to the conduct of foreign persons and its\n\nauthority to interfere with the navigation of a vessel encountered\n\non the high seas. Although stateless vessels enjoy no diplomatic\n\nprotections and thus are subject to being stopped and boarded by\n\nany other nation's vessels, it does not follow that this \"right to\n\nvisit\" confers jurisdiction on the boarding vessel's nation to\n\nprosecute the occupants of the stateless vessel -- who continue to\n\nenjoy diplomatic protection from their nation -- under the visiting\n\nnation's substantive criminal laws without some nexus between\n\ntheir conduct and the boarding nation. See James-Robinson, 515 F.\n\nSupp. at 1343 n.5 (explaining that the issue before the court was\n\nnot whether the United States had jurisdiction over a stateless\n\nship, but whether it had jurisdiction \"over the foreign citizen\n\ncrewmembers of such a stateless ship\"); see also Ted L. McDorman,\n\nStateless Fishing Vessels, Int'l Law, and the U.N. High Seas\n\nFisheries Conference, 25 J. Mar. L & Com. 531, 540 (1994)\n\n(discussing the views of D. O'Connell, 2 The Int'l Law of the Sea\n\n75 (Oxford University Press, Inc., 1984) and H. Meyers, The\n\nNationality of Ships 318-321 (Martinus Nijhoff, 1967) (noting that\n\nindividuals aboard stateless vessels \"retain their nationality\"\n\nand may thus be prosecuted by their home country under\n\ninternational law); see, e.g., Robin R. Churchill & Alan V. Lowe,\n\nThe Law of the Sea 172 (1988) (arguing that a vessel's\n\n\"'statelessness' will not, of itself, entitle each and every State\n\n\n - 34 -\n\nto assert jurisdiction over [its occupants], for there is not in\n\nevery case any recognized basis, such as nationality or\n\nterritoriality, upon which jurisdiction can be asserted over them\n\nwhile they are on the high seas . . . . [T]here is a need for\n\nsome jurisdictional nexus in order that a State may extend its\n\nlaws to those on board a stateless ship and enforce the laws\n\nagainst them\").\n\n A review of customary international law reveals that\n\nin all instances for which a state may interfere with the right of\n\npassage of another vessel, aside from the universal jurisdiction\n\ncrimes of piracy and slave trading, international law requires\n\nsome independent nexus between the visiting state and the suspected\n\nbasis for the interference. See UNCLOS at art. 110. For example,\n\ncustomary international law allows a State to board a foreign\n\nvessel on the high seas if the State has reason to believe that\n\nthe foreign vessel is engaged in unauthorized broadcasting.13 Id.\n\nat art. 110(c). But that State may only prosecute those\n\nindividuals engaged in that unauthorized broadcasting if that\n\nState has an independent basis for asserting jurisdiction over\n\nthose individuals or that conduct. See id. at art. 109(3),\n\n\n 13\n UNCLOS defines \"unauthorized broadcasting\" as \"the\ntransmission of sound radio or television broadcasts from a ship\nor installation on the high seas intended for reception by the\ngeneral public contrary to international regulations, but\nexcluding the transmission of distress calls.\" UNCLOS at art.\n109(2).\n\n\n - 35 -\n\n110(1)(c). Similarly, while any nation may board and prevent\n\nnavigation of a suspected stateless vessel under international\n\nlaw, that nation must have a nexus to the vessel's occupants or to\n\nthose occupant's conduct to assert jurisdiction to prosecute those\n\naboard the stateless vessel for a violation of its domestic laws\n\n-- such as drug trafficking under the MDLEA. The application of\n\nthat nation's domestic laws to a stateless vessel's occupants\n\nwithout a nexus unilaterally extends that nation's sovereignty\n\nover the high seas, in violation of customary international law.\n\nSee UNCLOS at art. 89.\n\n Moreover, allowing all nations to prosecute crewmembers\n\naboard stateless vessels under that nation's own domestic laws\n\nsimply because of their presence aboard that stateless vessel would\n\nconvert the operation of a stateless vessel into a universal\n\njurisdiction crime. \"There are two premises underlying universal\n\njurisdiction. The first involves the gravity of the crime. . . .\n\nThe second involves the locus delicti (place of the act).\"\n\nBellaizac-Hurtado, 700 F.3d at 1260 (Barkett, J., concurring)\n\n(quoting Michael P. Scharf, Application of Treaty-Based Universal\n\nJurisdiction to Nationals of Non-Party States, 35 New Eng. L. Rev.\n\n363, 368-69 (2001)). But, piloting a stateless vessel is not of\n\nthe same heinous nature as those universal jurisdiction crimes\n\n(piracy, slavery and genocide) and has not been recognized as a\n\nuniversal crime under international law. See UNCLOS; Allyson\n\n\n - 36 -\n\nBennett, That Sinking Feeling: Stateless Ships, Universal\n\nJurisdiction, and the Drug Trafficking Vessel Interdiction Act, 37\n\nYale J. Int'l L. 433, 448-50 (2012) (explaining that universal\n\ncrimes are those agreed upon by the international community to be\n\n\"so heinous . . . that they offend the interest of all humanity,\"\n\nsuch as genocide, and noting that statelessness is not listed as\n\na universal jurisdiction crime under UNCLOS). In fact, I have\n\nbeen unable to find any federal statute or regulation making\n\npiloting a stateless vessel a crime under the laws of the United\n\nStates. Because being aboard a stateless vessel does not meet the\n\nsubstantive component (the gravity of the crime) of universal\n\njurisdiction, and is not a universal crime, it follows that nations\n\ncannot apply their domestic laws to an individual simply by the\n\nfact that they are aboard a vessel without nationality.\n\n Just as Congress cannot pass legislation \"attempting to\n\napply the criminal laws of the United States, with the Bolivian\n\ngovernment's consent, to the conduct of Colombian nationals in\n\nBolivia,\" Cardales-Luna, 632 F.3d at 741 (Torruella, J.,\n\ndissenting), it cannot punish foreign nationals aboard foreign\n\nvessels. See, e.g., Furlong, 18 U.S. at 197-98; Klintock, 18 U.S.\n\nat 151. And, for the reasons explained in this dissent, the same\n\nmust be true even if those foreign nationals were aboard stateless\n\nvessels. If any state can assert its own laws based purely on a\n\nvessel's statelessness, then it follows that a United States\n\n\n - 37 -\n\ncitizen aboard a stateless vessel can be prosecuted under any\n\nforeign country's domestic laws even if the regulation of such\n\nconduct would be considered absurd in the United States. Common\n\nsense dictates that this is not and cannot be the case.\n\n There is no denying that most circuits, including our\n\nown, have upheld the application of the MDLEA to the crews of\n\nstateless vessels. However, this Court has not yet directly\n\naddressed the exact constitutional challenge Aybar has raised, and\n\nwe need not be constrained by related but non-binding precedent.\n\nAnd because the Felonies provision of the Define and Punish clause\n\nrequires that there be a nexus between the conduct and the United\n\nStates to pass constitutional muster, and no such nexus has been\n\nshown here, Aybar's conviction must be overturned. For the\n\nforegoing reasons, I respectfully dissent.\n\n\n\n\n - 38 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357438/", "author_raw": "TORRUELLA, Circuit Judge, joining in part and dissenting"}]}
TORRUELLA
LYNCH
BARRON
1
{}
2
0
1
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580185/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Johvanny AYBAR-ULLOA, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 15-2377\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOHVANNY AYBAR-ULLOA,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Jay A. García-Gregory, U.S. District Judge]\n\n\n Before\n\n Torruella, Lynch, and Barron,\n Circuit Judges.\n\n\n Heather Clark, with whom Clark Law Office was on brief, for\nappellant.\n Margaret Upshaw, with whom Rosa Emilia Rodríguez-Vélez,\nUnited States Attorney, Mariana E. Bauzá-Almonte, Assistant United\nStates Attorney, Chief, Appellate Division, and John A. Mathews\nII, Assistant United States Attorney, were on brief, for appellee.\n\n\n January 9, 2019\n\n BARRON, Circuit Judge. Johvanny Aybar-Ulloa (\"Aybar\")\n\npleaded guilty in 2015 to two counts of drug trafficking in\n\ninternational waters while aboard a \"stateless\" vessel in\n\nviolation of the Maritime Drug Law Enforcement Act (\"MDLEA\"), 46\n\nU.S.C. §§ 70501-08. He now challenges those convictions on the\n\nground that Congress lacks the authority under Article I, Section\n\n8, Clause 10 of the United States Constitution to criminalize his\n\nconduct, given that he contends that the conduct for which he was\n\nconvicted lacks any nexus to the United States. Aybar separately\n\nchallenges the sentence that he received for those convictions.\n\nFor the reasons that follow, we affirm the convictions but vacate\n\nthe sentence.\n\n I.\n\n At the change of plea hearing, the government described,\n\nand Aybar does not dispute, the following events as having occurred\n\non August 9, 2013. HMS Lancaster, a foreign warship, was on patrol\n\nin the Caribbean Sea and launched a helicopter that spotted a small\n\nvessel dead in the water. The vessel was located in international\n\nwaters at the time and contained \"numerous packages.\"\n\n HMS Lancaster launched a small boat in order to conduct\n\na right-of-visit approach. During this approach, Aybar and his\n\nco-defendant, who were aboard the vessel with the packages, claimed\n\nto be citizens of the Dominican Republic, although the vessel bore\n\n\"no indicia of nationality.\"\n\n\n - 2 -\n\n Law enforcement personnel aboard the small boat\n\nconducting the approach then determined that the vessel was\n\n\"without nationality,\" as Aybar conceded to the District Court was\n\ntrue, and boarded it.1 The men on board the vessel, including\n\nAybar, were transferred to HMS Lancaster along with the packages\n\nthat were taken from the vessel.\n\n A narcotics field test performed on board HMS Lancaster\n\nconfirmed that the packages contained cocaine. At this point,\n\nAybar was transferred to a United States Coast Guard vessel and\n\ntransported to Puerto Rico, where he was held in custody by United\n\nStates law enforcement.\n\n On August 13, 2013, a federal grand jury in the District\n\nof Puerto Rico returned an indictment against Aybar. The\n\nindictment charged him under the MDLEA with conspiring to possess\n\nwith intent to distribute cocaine on board a vessel subject to the\n\njurisdiction of the United States, in violation of 46 U.S.C.\n\n§ 70506(b) (count one), and aiding and abetting possession with\n\nintent to distribute cocaine on board a vessel subject to the\n\njurisdiction of the United States, in violation of 46 U.S.C.\n\n§§ 70502(c)(1)(A), 70503(a)(1), 70504(b)(1), 70506(a), and 18\n\n\n\n 1The government represented in a filing in the District Court\nthat the law enforcement personnel were United States Coast Guard\nmembers who were embarked on HMS Lancaster. However, the\ngovernment did not mention this allegation while describing the\nfactual basis for the convictions at the change of plea hearing.\n\n\n - 3 -\n\nU.S.C. § 2 (count two). A forfeiture allegation, under 46 U.S.C.\n\n§ 70507, was also made against Aybar.\n\n The MDLEA provides in part: \"While on board a covered\n\nvessel, an individual may not knowingly or intentionally . . .\n\nmanufacture or distribute, or possess with intent to manufacture\n\nor distribute, a controlled substance . . . .\" 46 U.S.C.\n\n§ 70503(a)(1). A \"covered vessel\" includes \"a vessel subject to\n\nthe jurisdiction of the United States.\" Id. § 70503(e)(1). A\n\n\"vessel subject to the jurisdiction of the United States\" is in\n\nturn defined to include \"a vessel without nationality.\" Id.\n\n§ 70502(c)(1)(A). And, as we mentioned, Aybar conceded below that\n\nhe was on board a vessel \"without nationality\" at the time he was\n\napprehended.\n\n On October 2, 2014, Aybar filed a motion to dismiss the\n\nindictment for lack of jurisdiction. He argued that Congress\n\nlacked the power to criminalize his conduct, given the lack of\n\nwhat Aybar claimed to be any constitutionally sufficient nexus\n\nbetween his charged conduct and the United States, because\n\nCongress's power under Article I of the Constitution \"[t]o define\n\nand punish Piracies and Felonies committed on the high Seas, and\n\nOffences against the Law of Nations,\" U.S. Const. art. I, § 8, cl.\n\n10, did not extend to his conduct in such circumstances.\n\n The government opposed Aybar's motion. The District\n\nCourt denied Aybar's motion on December 22, 2014 and issued a nunc\n\n\n - 4 -\n\npro tunc opinion and order on January 5, 2015. The District Court\n\nacknowledged that the vessel was not a \"vessel of the United\n\nStates\" within the meaning of the MDLEA, 46 U.S.C. § 70503(e)(1);\n\nthat Aybar was not a citizen of the United States; and that the\n\nother members of the crew were not either. But, the District Court\n\nreasoned, because \"international law allows the United States 'to\n\ntreat stateless vessels as if they were its own,'\" it followed\n\nthat \"persons navigating the high seas aboard a vessel without\n\nnationality have effectively waived their rights to object to the\n\nexercise of jurisdiction over them by the United States.\" The\n\nDistrict Court therefore concluded that Aybar's \"as-applied\n\nconstitutional challenge fails\" because his vessel was stateless.\n\n Following a change of plea hearing, Aybar entered a\n\nguilty plea to all charges on March 11, 2015. At that hearing,\n\nAybar engaged in the following colloquy with the Magistrate Judge:\n\n The Magistrate: Now, do you admit that in\n addition to the conspiracy you actually and\n the other co-defendants possessed with the\n intent to distribute these substances, this\n cocaine?\n\n Aybar: Yes, Your Honor.\n\n The Magistrate: In the same circumstances on\n board this vessel without nationality and\n therefore subject to jurisdiction of the\n United States?\n\n Aybar: Yes, Your Honor.\n\n\n\n\n - 5 -\n\n The District Court accepted Aybar's guilty plea, and the\n\ncase proceeded to sentencing. A probation officer prepared a\n\npresentence report (\"PSR\") using the 2014 United States Sentencing\n\nGuidelines Manual. The PSR assigned Aybar a base offense level of\n\nthirty-eight under the United States Sentencing Guidelines. After\n\nreceiving the PSR, Aybar filed an objection in which he argued\n\nthat two levels should be subtracted from his offense level under\n\n§ 3B1.2(b) of the Guidelines because he was a minor participant.\n\n At sentencing, the District Court declined to reduce his\n\noffense level as Aybar had argued and sentenced Aybar to 135 months\n\nin prison. Aybar timely filed a notice appealing the judgment\n\nentered against him.\n\n II.\n\n In prior cases in our circuit that have presented\n\nconstitutional challenges to MDLEA convictions not unlike the one\n\nthat Aybar now makes to us, the defendant had either waived or\n\nforfeited the constitutional argument challenging the scope of\n\nCongress's power under Article I to criminalize conduct supposedly\n\nlacking a sufficient nexus to the United States. See, e.g., United\n\nStates v. Diaz-Doncel, 811 F.3d 517 (1st Cir. 2016) (waived);\n\nUnited States v. Nueci-Peña, 711 F.3d 191 (1st Cir. 2013)\n\n\n\n\n - 6 -\n\n(forfeited).2 But that is not the case here. Aybar timely raised\n\nbelow the challenge that he now makes on appeal. And while Aybar\n\ndid plead guilty to the offenses that underlie the convictions\n\nthat he challenges on appeal, the government concedes that, in\n\nconsequence of the Supreme Court's holding in Class v. United\n\nStates, 138 S. Ct. 798 (2018), Aybar's guilty plea does not bar\n\nhim from challenging Congress's constitutional power to\n\ncriminalize his conduct pursuant to its Article I powers.\n\n The government does separately argue that Aybar waived\n\nhis right to bring this challenge because he conceded in the plea\n\ncolloquy that the vessel he was on board was \"without nationality\"\n\n-- which is one of the MDLEA's definitions for a \"vessel subject\n\nto the jurisdiction of the United States.\" 46 U.S.C.\n\n§ 70502(c)(1)(A). But, as we read the record, Aybar conceded only\n\nthat his conduct fell within the MDLEA's scope and not that the\n\nMDLEA was a valid exercise of Congress's constitutional power under\n\nArticle I insofar as it covered his conduct.\n\n\n\n\n 2 We rejected a similar as-applied challenge to the\nconstitutionality of the MDLEA under the Define and Punish Clause\non plain error review in Nueci-Peña. See 711 F.3d at 196-98. In\ndoing so, we noted that of all the circuits to have addressed the\nargument that this Clause \"does not authorize Congress to enact\nthe MDLEA, which punishes conduct without a connection to the\nUnited States,\" at least one has squarely rejected that argument,\nand none has held otherwise. Id. at 198 (citing United States v.\nEstupinan, 453 F.3d 1336, 1338-39 (11th Cir. 2006)).\n\n\n - 7 -\n\n Thus, we review de novo the district court's rejection\n\nof Aybar's constitutional challenge to Congress's power to\n\ncriminalize the conduct for which he was convicted. See United\n\nStates v. Bravo, 489 F.3d 1, 6 (1st Cir. 2007). Nevertheless, as\n\nwe will explain, the particular constitutional challenge to\n\nCongress's power that Aybar develops fails because, although we\n\nhave not had occasion directly to address it before, related\n\nprecedent from our circuit precludes us from accepting the premise\n\nconcerning international law on which his constitutional challenge\n\nto congressional power rests.\n\n A.\n\n Aybar contends that Congress exceeded its authority\n\nunder Article I in criminalizing his conduct under the MDLEA\n\nbecause Congress lacked the necessary power to criminalize such\n\nconduct under the Define and Punish Clause. That Clause gives\n\nCongress the power \"[t]o define and punish Piracies and Felonies\n\ncommitted on the high Seas, and Offences against the Law of\n\nNations.\" U.S. Const. art. I, § 8, cl. 10. In responding to\n\nAybar's constitutional challenge, the government does not identify\n\nany other source of constitutional authority pursuant to which\n\nCongress may criminalize Aybar's conduct. We thus focus here\n\nsolely on the dispute between the parties regarding the scope of\n\nthe power that the Define and Punish Clause affords Congress to\n\ncriminalize Aybar's conduct.\n\n\n - 8 -\n\n Aybar's constitutional challenge relies heavily on Judge\n\nTorruella's dissent in United States v. Cardales-Luna, 632 F.3d\n\n731 (1st Cir. 2011).3 Aybar first contends, by quoting Judge\n\nTorruella's dissent, that \"piracy\" under international law is only\n\n\"robbery when committed upon the sea\" and thus does not encompass\n\ndrug trafficking. Id. at 745 (Torruella, J., dissenting). For\n\nthat reason, he contends that Congress has no power to criminalize\n\nhis conduct pursuant to the \"Piracies\" component of the Clause in\n\nquestion.\n\n Aybar further contends, again by quoting the following\n\nportion of Judge Torruella's Cardales-Luna dissent, that the \"'Law\n\nof Nations' is generally understood to be the eighteenth and\n\nnineteenth-century term for 'customary international law'\" and\n\nthat customary international law does not recognize drug\n\ntrafficking as an offense against the law of nations. Id. at 745-\n\n47. Thus, Aybar contends, the \"law of nations\" component of the\n\nClause at issue also does not give Congress the power to\n\ncriminalize the conduct for which he was convicted.\n\n\n\n 3 The defendant in Cardales-Luna did not raise a\nconstitutional challenge to Congress's power under Article I to\nregulate conduct aboard stateless vessels on the high seas absent\nany nexus between that conduct and the United States. 632 F.3d at\n737. Judge Torruella nevertheless addressed this issue in his\ndissent because he concluded that this constitutional challenge\nimplicated the court's subject matter jurisdiction. Id. The\nmajority disagreed, however, and thus declined to address the issue\nsua sponte. Id.\n\n\n - 9 -\n\n Of course, Aybar recognizes that, even if these\n\narguments are right, he still must show that Congress could not\n\ncriminalize his conduct pursuant to its power to define and punish\n\n\"Felonies\" committed on the high seas. He acknowledges, as\n\nprecedent compels him to do, that this portion of the Clause gives\n\nCongress an independent source of power to define and punish\n\nconduct on the high seas, separate and apart from the power that\n\nCongress has under the other portions of the Clause that we have\n\njust discussed. See United States v. Smith, 18 U.S. 153, 158-59\n\n(1820).\n\n In arguing that the portion of the Clause that empowers\n\nCongress to punish \"Felonies\" on the high seas does not permit\n\nCongress to criminalize his conduct, Aybar contends that Congress\n\ncannot define and punish his conduct as a \"Felon[y]\" within the\n\nmeaning of Article I, Section 8, Clause 10, because there was no\n\nnexus between that conduct and the United States.4 And Aybar bases\n\nthat argument entirely on an assertion about the way that\n\ninternational law -- which he appears to treat as having been\n\n\n\n 4Specifically, Aybar asserts the following: He was\n\"interdicted in a vessel in international waters\"; \"no offense\noccurred within the territorial jurisdiction of the United\nStates\"; his vessel neither departed from nor was bound for the\nUnited States; \"there is no evidence that the cocaine aboard the\nvessel was intended for distribution\" in the United States; he\n\"did not commit any offense against a vessel of the United States\";\nand he was \"located by and taken in custody aboard\" a foreign\nwarship.\n\n\n - 10 -\n\ninvariant in the relevant respect from the Founding to the present\n\n-- treats drug trafficking and a nation's power to prosecute it in\n\ncircumstances like those involved here.\n\n We note that, in advancing this argument about the\n\ncontent of international law, Aybar is less than clear in\n\nexplaining the precise extent to which, in his view, international\n\nlaw reflects limits on national power that the Constitution\n\nincorporates in the portion of Article I that empowers Congress to\n\ndefine and punish \"Felonies\" committed on the high seas. But, be\n\nthat as it may, it is at least clear that Aybar's constitutional\n\ncontention with respect to the scope of Congress's power under\n\nthis part of Article I is necessarily premised on the underlying\n\nassertion that he makes about the content of international law as\n\nit relates to a nation's ability to criminalize conduct on the\n\nhigh seas where there is no more connection between that conduct\n\nand the United States than there is here. And so we now turn to\n\na consideration of that international-law-based premise for his\n\nconstitutional argument concerning Congress's power, for, unless\n\nwe accept that premise, his constitutional challenge must fail.5\n\n\n 5 We note that the Supreme Court addressed Congress's\nconstitutional power to define and punish piracies and felonies in\na series of cases in the early nineteenth century. See United\nStates v. Furlong, 18 U.S. (5 Wheat.) 184, 195-98 (1820); Smith,\n18 U.S. (5 Wheat.) at 158-60; United States v. Palmer, 16 U.S. (3\nWheat.) 610, 630 (1818); cf. United States v. Holmes, 18 U.S. (5\nWheat.) 412 (1820); United States v. Klintock, 18 U.S. (5 Wheat.)\n\n\n\n - 11 -\n\n B.\n\n In asserting this premise, Aybar again relies heavily on\n\nthe reasoning set forth in portions of Judge Torruella's dissent\n\nin Cardales-Luna. Aybar begins by quoting Judge Torruella's\n\nconclusion that, \"under the international law doctrine of\n\nuniversal jurisdiction (UJ), a nation may prosecute certain\n\nserious offenses even though they have no nexus to its territory\n\nor its nationals, and no impact on its territory or its citizens.\"\n\nCardales-Luna, 632 F.3d at 740. But, Aybar goes on to contend,\n\nonce again by quoting Judge Torruella's dissent in Cardales-Luna,\n\nthat \"[o]ther than in the case of those limited crimes, there is\n\nno general authority to regulate purely foreign criminal conduct\n\nthat does not have a demonstrable connection with the United\n\nStates.\" Id. at 741. Aybar then ties up his constitutional\n\nargument by asserting (yet again by quoting Judge Torruella's\n\ndissent in Cardales-Luna) that, because \"[d]rug trafficking is not\n\nrecognized in customary international law as a universally\n\ncognizable offense,\" id. at 745, the MDLEA may not afford universal\n\njurisdiction for drug trafficking as a \"Felon[y]\" within the\n\nmeaning of Article I, Section 8, Clause 10 of the Constitution in\n\na case in which the defendant's conduct did not have any more nexus\n\nto the United States than was present here.\n\n\n144 (1820). But, Aybar makes no argument that these cases resolved\nhis constitutional argument in his favor.\n\n\n - 12 -\n\n The problem for Aybar in advancing this argument is that,\n\nnotwithstanding his contention that international law does not\n\nauthorize the United States to prosecute conduct like his own due\n\nto what he claims to be the lack of any nexus between that conduct\n\nand the United States, we set forth a contrary view of\n\ninternational law in United States v. Victoria, 876 F.2d 1009 (1st\n\nCir. 1989) (Breyer, J.). There, we considered a challenge to a\n\nconviction for possessing marijuana under a predecessor statute to\n\nthe MDLEA based on conduct aboard a stateless vessel that was\n\ncaptured off the coast of Colombia. Id. at 1009-10. And, in the\n\ncourse of rejecting that defendant's challenge to his drug\n\nconviction, we explained first that \"international law . . . gives\n\nthe United States . . . authority to treat stateless vessels as if\n\nthey were its own.\" Id. at 1010 (second omission in original)\n\n(quoting United States v. Smith, 680 F.2d 255, 258 (1st Cir.\n\n1982)). Then, on the basis of that understanding of international\n\nlaw's treatment of stateless vessels, we concluded: \"Thus the\n\nUnited States, as a matter of international law, may prosecute\n\ndrug offenders on stateless ships found on the high seas.\" Id.6\n\n\n 6At oral argument, when asked why our holding in Victoria\nwas not dispositive, Aybar's counsel responded that Victoria did\nnot address the distinction between statelessness under the MDLEA\nand statelessness for the purposes of international law. But,\nwhile Aybar's brief asserts in a footnote that the MDLEA's\ndefinition of statelessness is broader than international law's,\nhe does not develop any argument for distinguishing Victoria on\n\n\n\n - 13 -\n\n To be sure, Victoria did not fully spell out why its\n\nconclusion that international law authorizes the United States to\n\ntreat a stateless vessel as its own means that, as a matter of\n\ninternational law, the United States could prosecute a person on\n\nboard such a vessel for a drug offense. Victoria nevertheless\n\nmade it clear that its ruling was definitive as to this point\n\nthrough its approving and extensive references to out-of-circuit\n\nprecedents holding similarly and \"explain[ing] in detail why this\n\nis so.\" Id. at 1011 (citing United States v. Alvarez-Mena, 765\n\nF.2d 1259, 1265-66 (5th Cir. 1985); United States v. Pinto-Mejia,\n\n720 F.2d 248, 260-61 (2d Cir. 1983); United States v. Marino-\n\nGarcia, 679 F.2d 1373, 1382-83 (11th Cir. 1982); United States v.\n\nRubies, 612 F.2d 397, 402-03 (9th Cir. 1979); United States v.\n\nCortes, 588 F.2d 106, 110 (5th Cir. 1979)).7\n\n\nthis basis. See United States v. Zannino, 895 F.2d 1, 17 (1st\nCir. 1990).\n 7 For this reason, we do not find significant the fact, not\nmentioned by the defendant here, that there was some evidence in\nVictoria -- as there is not here -- that the vessel in that case\nwas potentially bound for the United States. See 876 F.2d at 1010.\nIn fact, there is no indication in Victoria that the statute at\nissue made proof of such a tie between the defendant's conduct and\nthe United States necessary to convict the defendant. Nor did we\nqualify our holding that \"the United States, as a matter of\ninternational law, may prosecute drug offenders on stateless ships\nfound on the high seas\" in light of that evidence. Id. We also\nnote that Victoria, in asserting the United States' broad authority\nunder international law to prosecute persons who are not citizens\nof the United States for drug trafficking on a stateless vessel in\ninternational waters, made no reference to our decision the year\nbefore in United States v. Robinson, 843 F.2d 1, 3-4 (1st Cir.\n\n\n\n - 14 -\n\n We do recognize that Victoria did not consider a\n\nconstitutional challenge to Congress's power under Article I, such\n\nas Aybar now makes to us. In Victoria, the defendant argued merely\n\nthat the statute there at issue did not reach his conduct in light\n\nof the Charming Betsy canon, see Murray v. The Schooner Charming\n\nBetsy, 6 U.S. (2 Cranch) 64, 118 (1804) (reasoning that \"an act of\n\nCongress ought never to be construed to violate the law of nations\n\nif any other possible construction remains\"), given that he claimed\n\nthat \"international law would not permit the United States to\n\nconvict him for possessing marijuana . . . so far from the United\n\nStates.\" Victoria, 876 F.2d at 1010. But, even though our ruling\n\nin Victoria did not purport to address the constitutional question\n\nof congressional power that Aybar now raises, its reasoning is no\n\nless dispositive as to the assertion about international law that\n\nsupplies the premise for the constitutional argument that Aybar\n\ndoes make. Accordingly, because Aybar's constitutional challenge\n\nrests on an assertion about the content of international law that,\n\nas a panel, we are not free to accept in light of our prior\n\nprecedent, we must reject his constitutional contention regarding\n\n\n\n1988), in which we observed in dicta that there was a \"forceful\"\nargument to be made that international law would not justify the\nUnited States' prosecution of drug offenders on a foreign-flagged\nship found on the high seas where there was no clear proof that\nthe ship was bound for the United States and where the United\nStates acted without the flag state's consent.\n\n\n\n - 15 -\n\nthe scope of Congress's power. See United States v. Wurie, 867\n\nF.3d 28, 34 (1st Cir. 2017) (explaining the law of the circuit\n\nrule). And, on that basis, we affirm his convictions.8\n\n\n 8 The dissent disputes the merits of Victoria's holding as to\ninternational law, as well as the necessity of Victoria having\nresolved the Charming Betsy issue on the basis of that\nunderstanding of international law. See Diss. Op. 30-33. But,\nunder the law of the circuit doctrine, what matters is simply\nwhether Victoria did rely on that proposition for its holding that\nthe Charming Betsy canon did not require a narrower construction\nof the MDLEA, and it is clear that Victoria did. In fact, in\ndefending that view of international law, Victoria cited\nextensively to out-of-circuit precedent and included\nparentheticals in which those circuits set forth that very\nproposition of international law. See Victoria, 876 F.2d at 1011.\nWe thus are not free to treat that aspect of the Victoria decision\nas mere dicta. We note, too, that other circuits, since Victoria,\nhave continued to rule the same way. See, e.g., United States v.\nCampbell, 743 F.3d 802, 809-12 (11th Cir. 2014); United States v.\nCaicedo, 47 F.3d 370, 372-73 (9th Cir. 1995); United States v.\nMartinez-Hidalgo, 993 F.2d 1052, 1056-57 (3d Cir. 1993).\n The dissent also observes that Smith, 680 F.2d 255, a decision\nthat predates Victoria, indicates that Victoria's view of\ninternational law is mistaken. See Diss. Op. 31-32. The dissent\nfurther notes that Victoria relied on Smith. See id. However, as\nthe dissent itself points out, Victoria did not cite the full\npassage from Smith that the dissent contends is at odds with\nVictoria's assertion about international law. See Victoria, 876\nF.2d at 1010. And, the particular part of that passage from Smith\nthat Victoria did cite does not support the dissent's view. Nor\ndoes the dissent contend that it does. See Diss. Op. 31-32. In\nany event, we do not read even the full passage from Smith to\nsupport the dissent's view of it. See Diss. Op. 31. In that\npassage, Smith concludes that \"[the United States] has the\nauthority to treat stateless vessels as if they were its own,\" 680\nF.2d at 258, and then follows that conclusion by emphasizing the\ncircumstances of the case in front of it, stating that the United\nStates \"has [that] authority . . ., particularly when engaged in\nconduct affecting United States vessels and having an effect within\nthe jurisdiction of the United States,\" id. (emphasis added). Read\nas a whole, therefore, the passage from Smith on which the dissent\nplaces much weight suggests that evidence of a nexus between the\n\n\n\n - 16 -\n\n There is, in addition to Victoria, another of our\n\nprecedents that is at odds with Aybar's contention that\n\ninternational law of its own force requires there to be more of a\n\nnexus between a person charged with drug trafficking and the nation\n\nthat wishes to criminally prosecute it than is present here. That\n\nprecedent is United States v. Cardales, 168 F.3d 548 (1st Cir.\n\n1999), which concerned the application of the MDLEA to drug\n\nsmugglers on the high seas (there, on a foreign-flagged ship).\n\nId. at 551-52.\n\n In Cardales, the defendants argued that the Due Process\n\nClause, rather than the Define and Punish Clause, \"requires the\n\ngovernment to prove a nexus between their criminal conduct and the\n\nUnited States in a prosecution for violating the MDLEA,\" 168 F.3d\n\nat 552, which is an argument that we rejected there, id. at 553,\n\nand that Aybar does not press here.9 Moreover, Cardales, unlike\n\nAybar's case, involved a foreign-flagged vessel, id. at 552, and\n\nwe noted that the flag nation had consented to the assertion of\n\n\nconduct at issue and the United States is not necessary in order\nfor the United States to exercise the authority that Smith\nrecognizes.\n 9 We note that Aybar's brief mentions that the warship that\nintercepted the stateless vessel on which he was aboard was a\nforeign one. That was not the case in either Victoria or Cardales\n(a point Aybar does not himself point out), but Aybar makes no\nargument as to why this difference should matter with respect to\nwhether the exercise of United States jurisdiction over his conduct\naboard the stateless vessel was consistent with international law.\nSee Zannino, 895 F.2d at 17.\n\n\n - 17 -\n\njurisdiction by the United States, id., which we identified as key\n\nto our holding rejecting Cardales's due process challenge on ground\n\nof a lack of any nexus.\n\n But, apart from that aspect of our ruling, we also stated\n\nin Cardales that the application of the MDLEA in that case was\n\nconsistent with the \"protective principle\" of international law,\n\nwhich permits a nation \"to assert jurisdiction over a person whose\n\nconduct outside the nation's territory threatens the nation's\n\nsecurity.\" Id. at 553 (quoting Robinson, 843 F.2d at 3). And, in\n\nso concluding, Cardales relied on a congressional finding in the\n\nMDLEA that \"trafficking in controlled substances aboard vessels is\n\na serious international problem and is universally condemned[,\n\nand] . . . presents a specific threat to the security . . . of the\n\nUnited States.\" Id. (alteration and omissions in original)\n\n(quoting 46 U.S.C. app. § 1902). Cardales then explained that\n\n\"application of the MDLEA to the defendants is consistent with the\n\nprotective principle of international law because Congress has\n\ndetermined that all drug trafficking aboard vessels threatens our\n\nnation's security.\" Id. (emphasis added).\n\n There is no indication in this aspect of Cardales's\n\nreasoning that its broad assertion regarding the United States'\n\nentitlement to assert protective jurisdiction, under international\n\nlaw, was limited only to cases in which the flag nation has\n\nconsented to the United States' assertion of jurisdiction over a\n\n\n - 18 -\n\nvessel and those on board it. See id. at 553. Thus, the language\n\non this point in Cardales is, like the language referenced in\n\nVictoria concerning international law that we have described\n\nabove, directly contrary to Aybar's sole constitutional\n\ncontention, given the assertion about international law on which\n\nhis contention rests.\n\n Moreover, Aybar makes no argument as to why,\n\nnotwithstanding our conclusion to the contrary in Cardales, his\n\nconduct does not fall within the United States' protective\n\njurisdiction. He instead contends only that his crime of drug\n\ntrafficking is outside the United States' universal jurisdiction.\n\nHe thus develops no argument for reconsidering our statement in\n\nCardales concluding that the scope of protective jurisdiction\n\nencompasses conduct of the kind present here. See Zannino, 895\n\nF.2d at 17.\n\n III.\n\n Aybar next argues that the District Court erroneously\n\ndenied him a minor participant reduction under § 3B1.2(b) of the\n\nSentencing Guidelines based on five factors that he contends show\n\nthat he was a minor participant. That guideline provides that\n\n\"[i]f the defendant was a minor participant in any criminal\n\nactivity, decrease by 2 levels.\" U.S. Sentencing Guidelines Manual\n\n§ 3B1.2(b) (2014).\n\n\n\n\n - 19 -\n\n Application Note 3(C) of the November 2015 edition of\n\nthe Sentencing Guidelines sets forth the five factors on which\n\nAybar relies in challenging his sentence. U.S. Sentencing\n\nGuidelines Manual § 3B1.2, cmt. n.3(C) (2015). But, as the\n\ngovernment points out, he was sentenced according to the November\n\n2014 edition of the Guidelines in effect at the time of his October\n\n21, 2015 sentencing, and the application note to the minor-role\n\nguideline in that edition did not include those specific factors.\n\n Nevertheless, Aybar did file a letter under Rule 28(j)\n\ncalling our attention to our ruling in the companion case to this\n\none, United States v. Sarmiento-Palacios, 885 F.3d 1, 6 (1st Cir.\n\n2018), which we decided after all briefing was complete in this\n\ncase. See Fed. R. App. P. 28(j). Sarmiento held that Amendment\n\n794 to the Sentencing Guidelines, which added the five factors to\n\nthe application note, clarifies the Commission's original intent\n\nregarding § 3B1.2 and therefore that it does apply retroactively.\n\nId. And, in Sarmiento we therefore vacated the sentence and\n\nremanded for resentencing, so that the District Court could have\n\nan opportunity to apply the new factors. Id.\n\n The government argues that vacating the sentence and\n\nremanding for resentencing is not appropriate here, because, even\n\nunder the factors set out in Amendment 794, Aybar would still have\n\nbeen denied the minor-role reduction. But the same argument was\n\n\n\n\n - 20 -\n\nunsuccessful in Sarmiento, and we reject it for the same reasons\n\nthat we did there:\n\n we think it prudent to leave that\n determination in the hands of the able\n district court judge. Accordingly, a remand\n is justified to allow the sentencing court the\n opportunity to consider the \"Commission's\n current policy position[,] . . . [which] may\n have some influence on the judge's ultimate\n discretionary choice of sentence.\"\n\nId. (alterations and omission in original) (quoting United States\n\nv. Ahrendt, 560 F.3d 69, 79 (1st Cir. 2009)).\n\n IV.\n\n We therefore affirm the convictions. But we vacate the\n\nDistrict Court's sentence and remand for resentencing under the\n\nCommission's clarified guidance, as reflected in Amendment 794.\n\n\n\n - Separate Opinion Follows -\n\n\n\n\n - 21 -\n[END_CASE]", "role": "user" } ]
4,580,620
UNITED STATES, Appellee, v. Aletsys CALDERÓN-LOZANO, Defendant, Appellant.
United States v. Calderon-Lozano
2019-01-10
17-1977P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Lipez, Katzmann", "parties": "", "opinions": [{"author": "KATZMANN, Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1977\n\n UNITED STATES,\n\n Appellee,\n\n v.\n\n ALETSYS CALDERÓN-LOZANO,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Lynch and Lipez, Circuit Judges,\n and Katzmann, Judge.\n\n\n Davis Ramos Pagan, was on brief, for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and B. Kathryn Debrason, Assistant United\nStates Attorney, on brief, for appellee.\n\n\n January 10, 2019\n\n\n\n\n \n Of the United States Court of International Trade, sitting\nby designation.\n\f KATZMANN, Judge. Aletsys Calderón-Lozano (“Calderón-\n\nLozano”) received a guideline sentence of 46 months of imprisonment\n\nfor conspiracy to launder monetary instruments in violation of 18\n\nU.S.C. § 1956(h). On appeal, Calderón-Lozano challenges the\n\nprocedural and substantive reasonableness of his sentence. We\n\naffirm the district court’s sentence.\n\n Between February 25 and 26, 2016, Calderón-Lozano and an\n\nundercover Homeland Security Investigations (“HSI”) agent arranged\n\na meeting to deliver money. As agreed, Calderón-Lozano sent his\n\nassociate (and co-defendant) to deliver $80,000 to the agent. The\n\n$80,000 was then deposited into a bank account and divided between\n\ntwo accounts in the amount of $52,000 and $23,080 respectively.\n\nOn March 23, 2016, Calderón-Lozano arranged another money delivery\n\nwith the undercover agent. This time, Calderón-Lozano himself\n\ndelivered $100,000. The money was again deposited and divided\n\nbetween two bank accounts, in the amount of $59,951 and $34,067\n\nrespectively. After his arrest, Calderón-Lozano told\n\ninvestigative agents that “his job in Puerto Rico is to collect\n\nmoney from drug sales and deliver it to people.” When Calderón-\n\nLozano entered a straight guilty plea to the conspiracy count, his\n\nlawyer stated that the defendant was not pleading guilty to the\n\nspecific unlawful activity of drug importation. The district\n\ncourt, although noting that the defendant had admitted to his\n\n\n\n\n - 2 -\n\finvolvement in the drug trafficking deliveries to agents,\n\nindicated that it would decide the issue at sentencing.\n\n The third and final amended presentence report (“PSR”)\n\nprovided an imprisonment range of 87 to 108 months under the U.S.\n\nFederal Sentencing Guidelines (“Guidelines”). This calculation\n\nincluded a six-level enhancement for knowing or believing that the\n\nlaundered funds were drug proceeds pursuant to U.S.S.G.\n\n§ 2S1.1(b)(1).\n\n In his sentencing memorandum, Calderón-Lozano discussed\n\nhis difficult childhood and current familial ties. He also\n\nrequested a variant sentence, stating that “[a]lthough there is no\n\ncooperation agreement in this case, the Court should consider the\n\ninformation [he] provided to federal agents when he was arrested.”\n\nCalderón-Lozano did not object to the PSR’s six-level increase for\n\nknowing or believing that the laundered funds were drug proceeds\n\npursuant to U.S.S.G. § 2S1.1(b)(1).\n\n At sentencing, Calderón-Lozano again argued for a\n\nvariant sentence. Calderón-Lozano urged the district court to\n\ndisregard his statements to HSI agents in assessing whether he\n\nknew that the money was from drug trafficking. Calderón-Lozano\n\nconceded that he told the agents that “his job in Puerto Rico is\n\nto collect money from drug sales and deliver it to people.” He\n\nalso conceded that he does not have a proffer letter, that the\n\n“government is legally and rightfully using” his “post-arrest,\n\n\n - 3 -\n\fpre-counsel statements, and that these statements are sufficient\n\nto prove the six-point enhancement.” He later clarified that he\n\nwas “not objecting to the fact that there is a factual basis for\n\nthe six point enhancement [as] [t]here clearly is,” but instead\n\nwas “making an equity argument.” He argued for a sentence within\n\nthe total offense level (“TOL”) of 17 for a guideline range of 24\n\nto 30 months.\n\n The United States (“the government”) opposed a variance.\n\nThe government argued that Calderón-Lozano failed to object to the\n\nsix-level enhancement in the PSR and that the statements are post-\n\narrest statements, not part of a cooperation agreement. Noting\n\nthat “Mr. Calderón[-Lozano] was approached on numerous times to\n\nsee if he wanted to sit down and cooperate, and on each occasion,\n\nhe declined,” the government asserted that “[t]here is simply just\n\nno authority to argue that a post-arrest statement should qualify\n\nfor a variant sentence.” Finally, the government argued that\n\nCalderón-Lozano’s statements were not useful and “led to nothing.”\n\nAccordingly, the government recommended a sentence of 46 to 57\n\nmonths, within the guideline range for a TOL of 23.\n\n Ultimately, the district court followed the guideline\n\ncalculations in the PSR and calculated a TOL of 23, which included\n\nthe six-level drug-trafficking enhancement. The district court\n\nfound specifically that “[b]ecause Mr. Calderón[-Lozano] knew or\n\nbelieved that the laundered funds were the proceeds of or were\n\n\n - 4 -\n\fintended to promote an offense involving the manufacture,\n\nimportation, or distribution of controlled substances, the offense\n\nlevel is increased by another six levels pursuant to sentencing\n\nguideline section 2S1.1(b)(1).” With a TOL of 23 and a criminal\n\nhistory category of I, the district court calculated Calderón-\n\nLozano’s guideline sentencing range to be 46 to 57 months of\n\nimprisonment. Before imposing his sentence, the district court\n\nexpressly stated that it considered the relevant 18 U.S.C.\n\n§ 3553(a) sentencing factors. Reiterating that the six-level\n\nenhancement applied because Calderón-Lozano’s statements were\n\nmerely unhelpful post-arrest statements, the district court\n\nsentenced Calderón-Lozano to a low-end guideline sentence of 46\n\nmonths of imprisonment. Calderón-Lozano objected to the district\n\ncourt’s denial of his variance request and objected to the sentence\n\nas procedurally and substantively unreasonable. This appeal\n\nensued.\n\n I.\n\n Calderón-Lozano argues that the district court abused\n\nits discretion by applying a six-level enhancement pursuant to\n\nU.S.S.G. § 2S1.1(b)(1) when it was not proven that he knew that\n\nhis crime involved drug trafficking proceeds.\n\n This Court reviews criminal sentences for abuse of\n\ndiscretion. United States v. Flores-Machicote, 706 F.3d 16, 20\n\n(1st Cir. 2013). “[W]here there is more than one plausible view\n\n\n - 5 -\n\fof the circumstances, the sentencing court’s choice among\n\nsupportable alternatives cannot be clearly erroneous.” United\n\nStates v. Dunston, 851 F.3d 91, 101-02 (1st Cir. 2017) (quoting\n\nUnited States v. Ruiz, 905 F.2d 499, 508 (1st Cir. 1990)). We\n\nreview unpreserved challenges to guideline calculations under the\n\nmore daunting plain error standard. United States v. Arsenault,\n\n833 F.3d 24, 28 (1st Cir. 2016). Because Calderón-Lozano twice\n\nfailed to object to the factual basis for the enhancement by not\n\nobjecting to the PSR and at the sentencing hearing, he did not\n\npreserve his challenge to the guideline calculations, and his claim\n\ncan be reviewed under the plain error standard.\n\n In any event, the district court did not err, much less\n\nplainly err, in applying the six-level drug-trafficking proceeds\n\nenhancement pursuant to U.S.S.G. § 2S1.1(b)(1) because there was\n\nsufficient evidence that Calderón-Lozano knew that the sentencing\n\ncourt is entitled to rely on the uncontested facts in the PSR.\n\nUnited States v. González, 857 F.3d 46, 61-62 (1st Cir. 2017)\n\n(internal quotations and citations omitted). The PSR included\n\ninformation that Calderón-Lozano gave to the HSI agents showing he\n\nhad knowledge that the laundered funds were proceeds of an offense\n\ninvolving narcotics. Calderón-Lozano admitted to the HSI agents\n\n“that his job in Puerto Rico . . . was to collect money from drug\n\nsales and deliver it to people that would launder the money and\n\nwire transfer it to different parts of the world.” He also\n\n\n - 6 -\n\f“admitted that his roommate in Puerto Rico would coordinate the\n\ndrug shipments from Saint Maarten, and that he was present during\n\nsaid coordination.” He further “admitted that once the drugs came\n\nin, he was responsible for picking up the money and delivering it\n\nto associates with capacity to launder the drug proceeds.” These\n\nuncontested admissions, as listed in the PSR, provided the district\n\ncourt ample evidence to establish by a preponderance of the\n\nevidence that Calderón-Lozano knew that the laundered funds were\n\ndrug-trafficking proceeds.1 See United States v. Dixon, 449 F.3d\n\n194, 200-01 (1st. Cir. 2006).\n\n II.\n\n Calderón-Lozano also asserts that his 46-month sentence\n\nis both procedurally and substantively unreasonable.\n\n We review preserved claims of sentencing error for abuse\n\nof discretion. United States v. Córtes-Medina, 819 F.3d 566, 569\n\n(1st Cir. 2016). “In reviewing a sentence, [this Court] seek[s]\n\nto ensure that it is both procedurally sound and substantively\n\nreasonable.” United States v. Dávila-González, 595 F.3d 42, 47\n\n\n\n1\n Calderón-Lozano’s assertion that “the PSR also states that\n[he] made no statements as to the relation of said money with drug\ntrafficking (PSR29),” is misleading. Paragraph 29 states that\nCalderón-Lozano made no such statements during his acceptance-of-\nresponsibility interview on June 27, 2017, but does not address\nthe interview that Calderón-Lozano conducted with HSI agents.\nAccording to PSR Paragraph 23, Calderón-Lozano’s statements to HSI\nagents “showed his knowledge that the laundered funds were proceeds\nof an offense involving narcotics.”\n\n\n - 7 -\n\f(1st Cir. 2010). Procedural errors include “failing to calculate\n\n(or improperly calculating) the Guidelines range, treating the\n\nGuidelines as mandatory, failing to consider the [18 U.S.C.]\n\n§ 3553(a) factors, selecting a sentence based on clearly erroneous\n\nfacts, or failing to adequately explain the chosen sentence . . .\n\n.” Gall v. United States, 552 U.S. 38, 45-46 (2007). When\n\nreviewing a sentence, we remain “mindful that deference to the\n\ntrial court is a lineament of appellate review of federal criminal\n\nsentences.” United States v. Del Valle-Rodríguez, 761 F.3d 171,\n\n176 (1st Cir. 2014). Because Calderón-Lozano objected to the\n\ndistrict court’s denial of his variance request based on its\n\nalleged failure to consider his willingness to cooperate, he\n\npreserved this issue for appeal. Accordingly, this claim is\n\nreviewed for abuse of discretion. See Córtes-Medina, 819 F.3d at\n\n569.\n\n The district court did not abuse its discretion because\n\nit considered all relevant § 3553(a) sentencing factors, including\n\nCalderón-Lozano’s alleged attempts to cooperate with the\n\ngovernment. Section 3553(a) requires the sentencing court to\n\n“impose a sentence sufficient, but not greater than necessary,” to\n\ndeter criminal conduct, protect the public from the defendant’s\n\nfuture crimes, and meet the defendant’s educational and medical\n\nneeds. The district court, however, “is not required to address\n\n[each] factor[], one by one, in some sort of rote incantation when\n\n\n - 8 -\n\fexplicating its sentencing decision.” Dixon, 449 F.3d at 205.\n\nMoreover, “[a] criminal defendant is entitled to a weighing of the\n\nsection 3553(a) factors that are relevant to [his] case, not to a\n\nparticular result.” United States v. Carrasco-De-Jesús, 589 F.3d\n\n22, 29 (1st Cir. 2009). In imposing the low-end guideline\n\nsentence, the district court expressly stated that it considered\n\nthe “nature and circumstances” of the offense as well as “the other\n\nsentencing factors set forth in Title 18, United States Code\n\nsection 3553(a).” A district court’s explicit statement that it\n\nconsidered the § 3553(a) factors is “entitled to significant\n\nweight.” United States v. Arroyo-Maldonado, 791 F.3d 193, 199\n\n(1st Cir. 2015) (citing United States v. Santiago-Rivera, 744 F.3d\n\n229, 233 (1st Cir. 2014)). The district court weighed those\n\nmitigating factors against Calderón-Lozano’s participation in the\n\ninstant offense, which was “the coordination of a $100,000 pickup,\n\nand delivery and pick up of $80,000 [of] . . . laundered funds\n\nwhich were proceeds of . . . distribution of narcotics.” Noting\n\nCalderón-Lozano’s admissions to the HSI agents, the district court\n\nfound that he knew the money laundered was the proceeds of drug\n\ntrafficking. Rather than viewing his post-arrest statements as\n\nmitigation, as Calderón-Lozano suggests, the district court\n\nproperly factored Calderón-Lozano’s admissions into his role in\n\nthe offense. The district court expressly referenced its\n\nconsideration of these statements during its § 3553(a) analysis.\n\n\n - 9 -\n\fThe district court also considered the government’s argument that\n\nalthough Calderón-Lozano had several opportunities to cooperate,\n\nhe declined to do so, and thus declined to take advantage of a\n\ncooperation agreement.\n\n Nor is there any evidence that the district court\n\nmisunderstood its discretion to consider Calderón-Lozano’s alleged\n\ncooperation. See United States v. Landrón-Class, 696 F.3d 62, 77-\n\n78 (1st Cir. 2012). Calderón-Lozano’s post-arrest statements here\n\nwere “vehemently argued by [both] counsel[s] and specifically\n\nacknowledged by the court immediately before it imposed sentence.”\n\nUnited States v. Ruiz-Huertas, 792 F.3d 223, 227 (1st Cir. 2015).\n\nSee also Landrón-Class, 696 F.3d at 77-78. Thus, the district\n\ncourt properly weighed the § 3553(a) sentencing factors and did\n\nnot abuse its discretion in imposing a 46-month imprisonment\n\nsentence.\n\n Calderón-Lozano’s sentence is also substantively\n\nreasonable because the district court provided “a plausible\n\nsentencing rationale and a defensible result,” United States v.\n\nMartin, 520 F.3d 87, 96 (1st Cir. 2008), considering the severity\n\nof the instant offense and that Calderón-Lozano’s sentence is well\n\nbelow the statutory maximum of 20 years of imprisonment. Moreover,\n\nbecause Calderón-Lozano’s sentence is at the low end of the\n\nproperly calculated guideline sentencing range, it “deserves ‘a\n\npresumption of reasonableness.’” United States v. Llanos-Falero,\n\n\n - 10 -\n\f847 F.3d 29, 36 (1st Cir. 2017), cert. denied, 137 S. Ct. 2229\n\n(2017) (quoting Cortés-Medina, 819 F.3d at 572). Thus, Calderón-\n\nLozano’s 46-month sentence was “not greater than necessary,”\n\n§ 3553(a), but rather, was “within the wide universe of reasonable\n\nsentences.” See United States v. Rivera-Berríos, 902 F.3d 20, 27\n\n(1st Cir. 2018).\n\n The sentence is affirmed.\n\n\n\n\n - 11 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357873/", "author_raw": "KATZMANN, Judge"}]}
LYNCH
LIPEZ
KATZMANN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580620/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES, Appellee, v. Aletsys CALDERÓN-LOZANO, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1977\n\n UNITED STATES,\n\n Appellee,\n\n v.\n\n ALETSYS CALDERÓN-LOZANO,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Lynch and Lipez, Circuit Judges,\n and Katzmann, Judge.\n\n\n Davis Ramos Pagan, was on brief, for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and B. Kathryn Debrason, Assistant United\nStates Attorney, on brief, for appellee.\n\n\n January 10, 2019\n\n\n\n\n \n Of the United States Court of International Trade, sitting\nby designation.\n\f KATZMANN, Judge. Aletsys Calderón-Lozano (“Calderón-\n\nLozano”) received a guideline sentence of 46 months of imprisonment\n\nfor conspiracy to launder monetary instruments in violation of 18\n\nU.S.C. § 1956(h). On appeal, Calderón-Lozano challenges the\n\nprocedural and substantive reasonableness of his sentence. We\n\naffirm the district court’s sentence.\n\n Between February 25 and 26, 2016, Calderón-Lozano and an\n\nundercover Homeland Security Investigations (“HSI”) agent arranged\n\na meeting to deliver money. As agreed, Calderón-Lozano sent his\n\nassociate (and co-defendant) to deliver $80,000 to the agent. The\n\n$80,000 was then deposited into a bank account and divided between\n\ntwo accounts in the amount of $52,000 and $23,080 respectively.\n\nOn March 23, 2016, Calderón-Lozano arranged another money delivery\n\nwith the undercover agent. This time, Calderón-Lozano himself\n\ndelivered $100,000. The money was again deposited and divided\n\nbetween two bank accounts, in the amount of $59,951 and $34,067\n\nrespectively. After his arrest, Calderón-Lozano told\n\ninvestigative agents that “his job in Puerto Rico is to collect\n\nmoney from drug sales and deliver it to people.” When Calderón-\n\nLozano entered a straight guilty plea to the conspiracy count, his\n\nlawyer stated that the defendant was not pleading guilty to the\n\nspecific unlawful activity of drug importation. The district\n\ncourt, although noting that the defendant had admitted to his\n\n\n\n\n - 2 -\n\finvolvement in the drug trafficking deliveries to agents,\n\nindicated that it would decide the issue at sentencing.\n\n The third and final amended presentence report (“PSR”)\n\nprovided an imprisonment range of 87 to 108 months under the U.S.\n\nFederal Sentencing Guidelines (“Guidelines”). This calculation\n\nincluded a six-level enhancement for knowing or believing that the\n\nlaundered funds were drug proceeds pursuant to U.S.S.G.\n\n§ 2S1.1(b)(1).\n\n In his sentencing memorandum, Calderón-Lozano discussed\n\nhis difficult childhood and current familial ties. He also\n\nrequested a variant sentence, stating that “[a]lthough there is no\n\ncooperation agreement in this case, the Court should consider the\n\ninformation [he] provided to federal agents when he was arrested.”\n\nCalderón-Lozano did not object to the PSR’s six-level increase for\n\nknowing or believing that the laundered funds were drug proceeds\n\npursuant to U.S.S.G. § 2S1.1(b)(1).\n\n At sentencing, Calderón-Lozano again argued for a\n\nvariant sentence. Calderón-Lozano urged the district court to\n\ndisregard his statements to HSI agents in assessing whether he\n\nknew that the money was from drug trafficking. Calderón-Lozano\n\nconceded that he told the agents that “his job in Puerto Rico is\n\nto collect money from drug sales and deliver it to people.” He\n\nalso conceded that he does not have a proffer letter, that the\n\n“government is legally and rightfully using” his “post-arrest,\n\n\n - 3 -\n\fpre-counsel statements, and that these statements are sufficient\n\nto prove the six-point enhancement.” He later clarified that he\n\nwas “not objecting to the fact that there is a factual basis for\n\nthe six point enhancement [as] [t]here clearly is,” but instead\n\nwas “making an equity argument.” He argued for a sentence within\n\nthe total offense level (“TOL”) of 17 for a guideline range of 24\n\nto 30 months.\n\n The United States (“the government”) opposed a variance.\n\nThe government argued that Calderón-Lozano failed to object to the\n\nsix-level enhancement in the PSR and that the statements are post-\n\narrest statements, not part of a cooperation agreement. Noting\n\nthat “Mr. Calderón[-Lozano] was approached on numerous times to\n\nsee if he wanted to sit down and cooperate, and on each occasion,\n\nhe declined,” the government asserted that “[t]here is simply just\n\nno authority to argue that a post-arrest statement should qualify\n\nfor a variant sentence.” Finally, the government argued that\n\nCalderón-Lozano’s statements were not useful and “led to nothing.”\n\nAccordingly, the government recommended a sentence of 46 to 57\n\nmonths, within the guideline range for a TOL of 23.\n\n Ultimately, the district court followed the guideline\n\ncalculations in the PSR and calculated a TOL of 23, which included\n\nthe six-level drug-trafficking enhancement. The district court\n\nfound specifically that “[b]ecause Mr. Calderón[-Lozano] knew or\n\nbelieved that the laundered funds were the proceeds of or were\n\n\n - 4 -\n\fintended to promote an offense involving the manufacture,\n\nimportation, or distribution of controlled substances, the offense\n\nlevel is increased by another six levels pursuant to sentencing\n\nguideline section 2S1.1(b)(1).” With a TOL of 23 and a criminal\n\nhistory category of I, the district court calculated Calderón-\n\nLozano’s guideline sentencing range to be 46 to 57 months of\n\nimprisonment. Before imposing his sentence, the district court\n\nexpressly stated that it considered the relevant 18 U.S.C.\n\n§ 3553(a) sentencing factors. Reiterating that the six-level\n\nenhancement applied because Calderón-Lozano’s statements were\n\nmerely unhelpful post-arrest statements, the district court\n\nsentenced Calderón-Lozano to a low-end guideline sentence of 46\n\nmonths of imprisonment. Calderón-Lozano objected to the district\n\ncourt’s denial of his variance request and objected to the sentence\n\nas procedurally and substantively unreasonable. This appeal\n\nensued.\n\n I.\n\n Calderón-Lozano argues that the district court abused\n\nits discretion by applying a six-level enhancement pursuant to\n\nU.S.S.G. § 2S1.1(b)(1) when it was not proven that he knew that\n\nhis crime involved drug trafficking proceeds.\n\n This Court reviews criminal sentences for abuse of\n\ndiscretion. United States v. Flores-Machicote, 706 F.3d 16, 20\n\n(1st Cir. 2013). “[W]here there is more than one plausible view\n\n\n - 5 -\n\fof the circumstances, the sentencing court’s choice among\n\nsupportable alternatives cannot be clearly erroneous.” United\n\nStates v. Dunston, 851 F.3d 91, 101-02 (1st Cir. 2017) (quoting\n\nUnited States v. Ruiz, 905 F.2d 499, 508 (1st Cir. 1990)). We\n\nreview unpreserved challenges to guideline calculations under the\n\nmore daunting plain error standard. United States v. Arsenault,\n\n833 F.3d 24, 28 (1st Cir. 2016). Because Calderón-Lozano twice\n\nfailed to object to the factual basis for the enhancement by not\n\nobjecting to the PSR and at the sentencing hearing, he did not\n\npreserve his challenge to the guideline calculations, and his claim\n\ncan be reviewed under the plain error standard.\n\n In any event, the district court did not err, much less\n\nplainly err, in applying the six-level drug-trafficking proceeds\n\nenhancement pursuant to U.S.S.G. § 2S1.1(b)(1) because there was\n\nsufficient evidence that Calderón-Lozano knew that the sentencing\n\ncourt is entitled to rely on the uncontested facts in the PSR.\n\nUnited States v. González, 857 F.3d 46, 61-62 (1st Cir. 2017)\n\n(internal quotations and citations omitted). The PSR included\n\ninformation that Calderón-Lozano gave to the HSI agents showing he\n\nhad knowledge that the laundered funds were proceeds of an offense\n\ninvolving narcotics. Calderón-Lozano admitted to the HSI agents\n\n“that his job in Puerto Rico . . . was to collect money from drug\n\nsales and deliver it to people that would launder the money and\n\nwire transfer it to different parts of the world.” He also\n\n\n - 6 -\n\f“admitted that his roommate in Puerto Rico would coordinate the\n\ndrug shipments from Saint Maarten, and that he was present during\n\nsaid coordination.” He further “admitted that once the drugs came\n\nin, he was responsible for picking up the money and delivering it\n\nto associates with capacity to launder the drug proceeds.” These\n\nuncontested admissions, as listed in the PSR, provided the district\n\ncourt ample evidence to establish by a preponderance of the\n\nevidence that Calderón-Lozano knew that the laundered funds were\n\ndrug-trafficking proceeds.1 See United States v. Dixon, 449 F.3d\n\n194, 200-01 (1st. Cir. 2006).\n\n II.\n\n Calderón-Lozano also asserts that his 46-month sentence\n\nis both procedurally and substantively unreasonable.\n\n We review preserved claims of sentencing error for abuse\n\nof discretion. United States v. Córtes-Medina, 819 F.3d 566, 569\n\n(1st Cir. 2016). “In reviewing a sentence, [this Court] seek[s]\n\nto ensure that it is both procedurally sound and substantively\n\nreasonable.” United States v. Dávila-González, 595 F.3d 42, 47\n\n\n\n1\n Calderón-Lozano’s assertion that “the PSR also states that\n[he] made no statements as to the relation of said money with drug\ntrafficking (PSR29),” is misleading. Paragraph 29 states that\nCalderón-Lozano made no such statements during his acceptance-of-\nresponsibility interview on June 27, 2017, but does not address\nthe interview that Calderón-Lozano conducted with HSI agents.\nAccording to PSR Paragraph 23, Calderón-Lozano’s statements to HSI\nagents “showed his knowledge that the laundered funds were proceeds\nof an offense involving narcotics.”\n\n\n - 7 -\n\f(1st Cir. 2010). Procedural errors include “failing to calculate\n\n(or improperly calculating) the Guidelines range, treating the\n\nGuidelines as mandatory, failing to consider the [18 U.S.C.]\n\n§ 3553(a) factors, selecting a sentence based on clearly erroneous\n\nfacts, or failing to adequately explain the chosen sentence . . .\n\n.” Gall v. United States, 552 U.S. 38, 45-46 (2007). When\n\nreviewing a sentence, we remain “mindful that deference to the\n\ntrial court is a lineament of appellate review of federal criminal\n\nsentences.” United States v. Del Valle-Rodríguez, 761 F.3d 171,\n\n176 (1st Cir. 2014). Because Calderón-Lozano objected to the\n\ndistrict court’s denial of his variance request based on its\n\nalleged failure to consider his willingness to cooperate, he\n\npreserved this issue for appeal. Accordingly, this claim is\n\nreviewed for abuse of discretion. See Córtes-Medina, 819 F.3d at\n\n569.\n\n The district court did not abuse its discretion because\n\nit considered all relevant § 3553(a) sentencing factors, including\n\nCalderón-Lozano’s alleged attempts to cooperate with the\n\ngovernment. Section 3553(a) requires the sentencing court to\n\n“impose a sentence sufficient, but not greater than necessary,” to\n\ndeter criminal conduct, protect the public from the defendant’s\n\nfuture crimes, and meet the defendant’s educational and medical\n\nneeds. The district court, however, “is not required to address\n\n[each] factor[], one by one, in some sort of rote incantation when\n\n\n - 8 -\n\fexplicating its sentencing decision.” Dixon, 449 F.3d at 205.\n\nMoreover, “[a] criminal defendant is entitled to a weighing of the\n\nsection 3553(a) factors that are relevant to [his] case, not to a\n\nparticular result.” United States v. Carrasco-De-Jesús, 589 F.3d\n\n22, 29 (1st Cir. 2009). In imposing the low-end guideline\n\nsentence, the district court expressly stated that it considered\n\nthe “nature and circumstances” of the offense as well as “the other\n\nsentencing factors set forth in Title 18, United States Code\n\nsection 3553(a).” A district court’s explicit statement that it\n\nconsidered the § 3553(a) factors is “entitled to significant\n\nweight.” United States v. Arroyo-Maldonado, 791 F.3d 193, 199\n\n(1st Cir. 2015) (citing United States v. Santiago-Rivera, 744 F.3d\n\n229, 233 (1st Cir. 2014)). The district court weighed those\n\nmitigating factors against Calderón-Lozano’s participation in the\n\ninstant offense, which was “the coordination of a $100,000 pickup,\n\nand delivery and pick up of $80,000 [of] . . . laundered funds\n\nwhich were proceeds of . . . distribution of narcotics.” Noting\n\nCalderón-Lozano’s admissions to the HSI agents, the district court\n\nfound that he knew the money laundered was the proceeds of drug\n\ntrafficking. Rather than viewing his post-arrest statements as\n\nmitigation, as Calderón-Lozano suggests, the district court\n\nproperly factored Calderón-Lozano’s admissions into his role in\n\nthe offense. The district court expressly referenced its\n\nconsideration of these statements during its § 3553(a) analysis.\n\n\n - 9 -\n\fThe district court also considered the government’s argument that\n\nalthough Calderón-Lozano had several opportunities to cooperate,\n\nhe declined to do so, and thus declined to take advantage of a\n\ncooperation agreement.\n\n Nor is there any evidence that the district court\n\nmisunderstood its discretion to consider Calderón-Lozano’s alleged\n\ncooperation. See United States v. Landrón-Class, 696 F.3d 62, 77-\n\n78 (1st Cir. 2012). Calderón-Lozano’s post-arrest statements here\n\nwere “vehemently argued by [both] counsel[s] and specifically\n\nacknowledged by the court immediately before it imposed sentence.”\n\nUnited States v. Ruiz-Huertas, 792 F.3d 223, 227 (1st Cir. 2015).\n\nSee also Landrón-Class, 696 F.3d at 77-78. Thus, the district\n\ncourt properly weighed the § 3553(a) sentencing factors and did\n\nnot abuse its discretion in imposing a 46-month imprisonment\n\nsentence.\n\n Calderón-Lozano’s sentence is also substantively\n\nreasonable because the district court provided “a plausible\n\nsentencing rationale and a defensible result,” United States v.\n\nMartin, 520 F.3d 87, 96 (1st Cir. 2008), considering the severity\n\nof the instant offense and that Calderón-Lozano’s sentence is well\n\nbelow the statutory maximum of 20 years of imprisonment. Moreover,\n\nbecause Calderón-Lozano’s sentence is at the low end of the\n\nproperly calculated guideline sentencing range, it “deserves ‘a\n\npresumption of reasonableness.’” United States v. Llanos-Falero,\n\n\n - 10 -\n\f847 F.3d 29, 36 (1st Cir. 2017), cert. denied, 137 S. Ct. 2229\n\n(2017) (quoting Cortés-Medina, 819 F.3d at 572). Thus, Calderón-\n\nLozano’s 46-month sentence was “not greater than necessary,”\n\n§ 3553(a), but rather, was “within the wide universe of reasonable\n\nsentences.” See United States v. Rivera-Berríos, 902 F.3d 20, 27\n\n(1st Cir. 2018).\n\n The sentence is affirmed.\n\n\n\n\n - 11 -\n[END_CASE]", "role": "user" } ]
4,580,621
Amma Adu GYAMFI, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.
Gyamfi v. Whitaker
2019-01-10
18-1093P
U.S. Court of Appeals for the First Circuit
{"judges": "Thompson, Kayatta, Barron", "parties": "", "opinions": [{"author": "THOMPSON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1093\n\n AMMA ADU GYAMFI,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Thompson, Kayatta, and Barron,\n Circuit Judges.\n\n\n Saher Joseph Macarius, Audrey Botros, and Law Offices of Saher\nJoseph Macarius LLC on brief for petitioner.\n Chad A. Readler, Acting Assistant Attorney General, Civil\nDivision, M. Jocelyn Lopez Wright, Senior Litigation Counsel,\nOffice of Immigration Litigation, and Anna Juarez, Trial Attorney,\nOffice of Immigration Litigation, on brief for respondent.\n\n\n January 10, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney General\nMatthew G. Whitaker has been substituted for former Attorney\nGeneral Jefferson B. Sessions, III as the respondent.\n\f THOMPSON, Circuit Judge. Petitioner Amma Adu Gyamfi\n\n(\"Gyamfi\") challenges the Board of Immigration Appeals's (\"BIA\")\n\ndenial of her motion to reopen and its decision not to exercise\n\nits sua sponte authority to reopen her case and grant her request\n\nfor an adjustment of status. For the reasons we detail below, we\n\ndeny and dismiss Gyamfi's petition.\n\n BACKGROUND\n\n In March of 2004, Gyamfi, a native of Ghana and resident\n\nof Italy from 1992 until 2004, arrived in the U.S. on a\n\nnonimmigrant B-2 visa that granted her a six-month stay here.\n\nGyamfi didn't leave after her permissible time here expired, and\n\nin November 2007, she married a U.S. citizen, Mark Parrish. That\n\nfollowing April, Parrish filed an I-130 petition1 to get Gyamfi\n\ngreen-card status as the spouse of a U.S. citizen, but when the\n\nDepartment of Homeland Security (\"DHS\") issued a notice of intent\n\nto deny the petition (because the newlyweds hadn't demonstrated\n\nthe legitimacy of their marriage), Parrish wound up admitting in\n\na 2009 DHS interview that he had made the petition as \"a favor\" to\n\nGyamfi. Consequently, he withdrew the petition, and DHS denied\n\nGyamfi's application for adjustment of status in April 2009.\n\n\n\n\n1 An I-130 petition allows a U.S. citizen or lawful permanent\nresident to sponsor an alien relative's application for permanent\nresident status.\n\n\n - 2 -\n\f A month later, DHS initiated removal proceedings against\n\nGyamfi: she was charged with removability as an alien who remained\n\nin the U.S. for a time longer than permitted after being admitted\n\nas a nonimmigrant visitor (8 U.S.C. § 1227(a)(1)(B)).2 Over the\n\ncourse of a couple of years (2009-2010) and a few hearings before\n\nan immigration judge (\"IJ\"), Gyamfi would first pursue a new I-\n\n130 petition, then withdraw it, and in the end, seek asylum\n\nprotection.3\n\n Unpersuaded by her arguments and testimony relative to\n\nher lamentations of persecution, in March 2013, the IJ ordered her\n\nremoved.4 The BIA affirmed the IJ and, in July 2014, dismissed\n\nthe appeal. Gyamfi did not seek judicial review of that decision.\n\n Fast-forward three years to August 31, 2017: in light\n\nof an I-130 petition filed in November 2015 on her behalf by her\n\nrecently naturalized U.S. citizen daughter5 (and which was approved\n\n\n2 Gyamfi also was charged as an alien who was inadmissible at the\ntime of entry because she procured, or sought to procure, an\nimmigration benefit by fraud or by willfully misrepresenting a\nmaterial fact, 8 U.S.C. § 1227(a)(1)(A), but that was later\nwithdrawn.\n3 She testified at a September 2010 hearing that she never applied\n\nfor asylum in Italy, her home for thirteen years after leaving\nGhana in 1992. As for why she never mentioned harboring any fear\nof returning to Ghana between her 2004 arrival in the U.S. and the\nSeptember 2010 hearing, she testified she had hoped to adjust\nstatus through Parrish.\n4 During the proceedings before the IJ, Gyamfi conceded\nremovability only as an alien who overstayed her visitor's visa.\n5 Gyamfi has six children, five of whom are U.S. citizens and live\n\nin the United States. Her eldest child, now 28 years old, is a\ncitizen of Ghana residing there. Her next two eldest, now 25 and\n\n\n - 3 -\n\fby DHS in April 2016), Gyamfi sought to adjust her status. She\n\nmoved to reopen her case and also requested sua sponte (\"on its\n\nown motion\") reopening by the BIA premised on the hardship her\n\nremoval would have on her children. In response, DHS filed an\n\nopposition to the motion, albeit late.\n\n The BIA denied Gyamfi's motion as untimely (the final\n\nadministrative order entered in July of 2014, and the BIA didn't\n\nreceive the motion to reopen until August 2017) and not falling\n\nwithin any exception to the ninety-day window to file a motion to\n\nreopen. See 8 U.S.C. § 1229a(c)(7)(C)(i); 8 C.F.R.\n\n§§ 1003.2(c)(2), 1003(c)(3)(i)-(iv). In addition, the BIA\n\ndeclined to exercise its discretionary authority to reopen the\n\nproceedings sua sponte, finding that Gyamfi failed to demonstrate\n\nan exceptional situation that would warrant the exercise of its\n\nsua sponte power, and she alleged \"no current health issues\n\nregarding [her I-130-petitioning daughter] or her other United\n\nStates citizen children that might warrant a finding of exceptional\n\ncircumstances.\"\n\n Gyamfi timely petitioned this court for review.\n\n ANALYSIS\n\n Gyamfi offers up a smorgasbord of appellate contentions,\n\n\n\n\n21 years old, were born in Italy, but are U.S. citizens residing\nhere. And she has three minor U.S. citizen children (ages 17, 12,\nand 10), all of whom were born in the U.S. and live here now.\n\n\n - 4 -\n\fbut distilling those arguments to their core essence as best we\n\ncan, we think they primarily fit under two main headings: (1) the\n\nBIA abused its discretion by denying her motion to reopen; or, in\n\nthe alternative, (2) the BIA should have deployed its discretionary\n\nauthority to reopen the proceedings sua sponte. She advances\n\nvarious arguments in support of these two issues, which we will\n\nexplore in turn.\n\n And as we review Gyamfi's contestations, we necessarily\n\nbear in mind our familiar standard: to the extent we have\n\njurisdiction, \"[b]ecause a motion to reopen removal proceedings is\n\na disfavored tool, given the threat it poses to finality, the BIA\n\nhas a fair amount of latitude to grant or deny the motion and our\n\nreview is for abuse of discretion only.\" Mazariegos v. Lynch, 790\n\nF.3d 280, 285 (1st Cir. 2015) (citing Perez v. Holder, 740 F.3d\n\n57, 61 (1st Cir. 2014)); see also Sihotang v. Sessions, 900 F.3d\n\n46, 48 (1st Cir. 2018) (\"Motions to reopen -- especially untimely\n\nmotions to reopen -- are disfavored in immigration cases.\n\nConsequently, an alien who seeks to reopen removal proceedings out\n\nof time ordinarily faces a steep uphill climb.\"). Unless a\n\npetitioner can show that the BIA either committed a material error\n\nof law or exercised its authority arbitrarily, capriciously, or\n\nirrationally, we will uphold the BIA's decision. See Bbale v.\n\nLynch, 840 F.3d 63, 66 (1st Cir. 2016) (citing Rosa v. Gonzales,\n\n484 F.3d 125, 127 (1st Cir. 2007)).\n\n\n - 5 -\n\f Before diving into Gyamfi's argument, saying a bit more\n\nabout the pertinent aspects of the ninety-day rule would be\n\nhelpful.6 Pursuant to 8 U.S.C. § 1229a(c)(7)(C)(i), an alien is\n\nentitled to file one motion to reopen removal proceedings within\n\nninety days after the final order of removal. See id. (instructing\n\nthat, unless an exception applies, \"the motion to reopen shall be\n\nfiled within 90 days of the date of entry of a final administrative\n\norder of removal\"); see also 8 C.F.R. § 1003.2(c)(2) (stating that,\n\nsave for specified exceptions, \"an alien may file only one motion\n\nto reopen removal proceedings (whether before the Board or the\n\nImmigration Judge) and that motion must be filed no later than 90\n\ndays after the date on which the final administrative decision was\n\nrendered in the proceeding sought to be reopened\"); Neves v.\n\nHolder, 613 F.3d 30, 32-33 (1st Cir. 2010)(per curiam). As for\n\n\n\n\n6 We note here that Gyamfi makes the assertion that a petitioner\ncan file a motion to reopen either within ninety days of the final\nadministrative order or within 180 days due to exceptional\ncircumstances, citing INA § 240(b)(5)(c)(i), (e)(6)(C) -- this\nprovision has been repealed, and its replacement is codified at 8\nU.S.C. § 1229a(b)(5)(C)(i). There, the reference to 180 days\nconcerns rescission of an order of removal issued because of an\nalien's failure to appear: such a removal order can be rescinded\nif an alien files a motion to reopen \"within 180 days after the\ndate of the order of removal if the alien demonstrates that the\nfailure to appear was because of exceptional circumstances\n. . . .\" Sec. 1229a(b)(5)(C)(i). This is not in play in\nGyamfi's case, thus the 180-day cut-off is not applicable.\n\n\n - 6 -\n\fthe exceptions, Congress enacted a limited list. See 8 U.S.C. §\n\n1229a(c)(7)(C)(ii)-(iv); 8 C.F.R. § 1003.2(c)(3).7\n\n 1. Did the BIA abuse its discretion?8\n\n a. The Ninety-Day Rule\n\n Gyamfi claims the BIA abused its discretion when it\n\ndeclined to grant her motion to reopen. She does not dispute that\n\nher August 2017 filing missed the deadline -- the BIA's final\n\n\n\n\n7 For example, 8 C.F.R. § 1003.2(c)(3) instructs that the ninety-\nday rule\n\n [s]hall not apply to a motion to reopen proceedings:\n\n . . .\n\n (ii) To apply or reapply for asylum or withholding of\n deportation based on changed circumstances arising in\n the country of nationality or in the country to which\n deportation has been ordered, if such evidence is\n material and was not available and could not have been\n discovered or presented at the previous hearing;\n\n (iii) Agreed upon by all parties and jointly filed.\n Notwithstanding such agreement, the parties may contest\n the issues in a reopened proceeding[.]\n\n8 As a threshold matter, Gyamfi submits that the BIA stumbled out\nof the starting gate when it deemed her motion opposed. Recall\nthat DHS's opposition to Gyamfi's motion to reopen was filed out\nof time -- Gyamfi submitted a response to that late filing. But\nwe espy no error of law or abuse of discretion. As the government\ncorrectly points out, considering a late-filed brief is not\nproscribed, see 8 C.F.R. § 1003.2(g)(3), and regardless, the BIA\nis duty-bound to use its independent judgment when facing these\nmotions, 8 C.F.R. § 1003.1(d)(1)(ii). And besides, Gyamfi does\nnot even argue that the BIA improperly based its denial of her\nmotion on the substantive arguments in DHS's papers. This\nargument, then, is a nonstarter, so we move on to her primary\nchallenges.\n\n\n - 7 -\n\fadministrative order was issued on July 17, 2014 and October 13,\n\n2014 (ninety days later) was the last day Gyamfi could have filed\n\nher motion. However, she asserts that because she was \"prima\n\nfacie\" eligible for status adjustment as a result of the previously\n\nunavailable evidence (the I-130 visa her daughter filed on her\n\nbehalf long after the expiration of the ninety-day limit), the BIA\n\nshould have ruled differently on 8 U.S.C. § 1229a(c)(7)(C)(i)'s\n\nninety-day bar.\n\n The government disagrees, and its position is simple:\n\nthe ninety-day limit expired and no exception applies. Indeed,\n\nthe government points out that Gyamfi cannot be \"prima facie\"\n\neligible for status adjustment given the untimeliness of her\n\nmotion.\n\n In support of her claim of \"prima facie\" eligibility\n\nGyamfi cites to Matter of Garcia, 16 I. & N. Dec. 653, 654 (B.I.A.\n\n1978), a case wherein the BIA explained the appropriateness of\n\nexercising its discretion (at least at that time) to reopen\n\nimmigration proceedings during the pendency of adjustment of\n\nstatus applications of prima facie eligible movants. But her\n\nreliance on this case is misplaced. Garcia was decided before\n\nCongress enacted time and number bars on motions to reopen, Lemus\n\nv. Sessions, 900 F.3d 15, 19 (1st Cir. 2018) (citing Dada v.\n\nMukasey, 554 U.S. 1, 13 (2008) (outlining that history)), and\n\nwhat's more, the BIA, itself, has moved away from its Garcia\n\n\n - 8 -\n\fholding, see id. (collecting BIA cases). Given this evolution\n\n(and as we have previously noted), our confidence in Garcia's\n\ncontinuing applicability has been undercut. Id. But whether or\n\nnot viable, Garcia's recognition of the IJ's discretionary\n\nauthority is not a rule mandating the exercise of same.\n\n Accordingly, we believe the government has the better\n\nargument on the application of the ninety-day rule. Though Gyamfi\n\ntells us she can present new evidence, clearly the new evidence\n\nshe offers, an I-130 visa, is not a statutory exception to the\n\nrule. See 8 U.S.C. § 1229a(c)(7)(C); 8 C.F.R. § 1003.2(c)(3)(i)-\n\n(iv). And absent an exception operating to prevent the ninety-\n\nday rule from applying (Gyamfi doesn't actually argue that one\n\ndoes), motions to reopen are subject to the ninety-day rule and\n\nGyamfi missed it. We see no abuse of discretion.\n\n b. Equitable Tolling\n\n Alternatively, Gyamfi argues the BIA erred in not\n\nreopening her removal proceedings because she established \"unusual\n\nfacts and exceptional circumstances\" meriting the equitable\n\ntolling of the ninety-day deadline for filing such motions.\n\nGyamfi submits that she's made the equitable tolling showing by,\n\nfirst, demonstrating that she couldn't have known about her new I-\n\n130 beneficiary status within ninety days of her original\n\nproceedings and as such, her ignorance of what the future actually\n\nwould bring constitutes an extraordinary circumstance. As she\n\n\n - 9 -\n\fputs it, \"applying this statutory deadline does not serve the\n\ninterests of justice in this case.\" Second, she puts into the\n\n\"extraordinary circumstances\" basket the BIA's alleged error in\n\nneglecting to consider any factors besides the health of her\n\nchildren.9 In particular, she emphasizes the hardship her removal\n\nwill have on her kids: if they return to Ghana with Gyamfi, they\n\nwill not enjoy a U.S. education, and Ghanaian high crime and\n\nmortality rates, for example, would negatively affect them; and if\n\nthey stay in the U.S. without her, this also would negatively\n\nimpact them. The government responds that even if equitable\n\ntolling was a viable avenue to relief in the immigration context,\n\nthe BIA did not abuse its discretion in finding that Gyamfi has\n\nnot made the requisite showing to support its use. Once again, we\n\nagree with the government.\n\n Equitable tolling \"extends statutory deadlines in\n\nextraordinary circumstances for parties who were prevented from\n\ncomplying with them through no fault or lack of diligence of their\n\nown.\" Neves, 613 F.3d at 36 (citing Fustaguio Do Nascimento v.\n\nMukasey, 549 F.3d 12, 18-19 (1st Cir. 2008)). So the party seeking\n\nto toll the deadline bears the burden of showing: \"(1) that he has\n\n\n9 Gyamfi also points to the \"five factors\" laid out in Matter of\nJ-J-, 21 I. & N. Dec. 976 (B.I.A. 1997), saying the BIA's failure\nto consider these factors constitutes legal error. To the extent\nshe means to argue that case to support her equitable tolling\nargument, we fail to see its relevance -- Matter of J-J- does not\ntouch on equitable tolling.\n\n\n - 10 -\n\fbeen pursuing his rights diligently, and (2) that some\n\nextraordinary circumstance stood in his way.\" Id. (quoting Pace\n\nv. DiGuglielmo, 544 U.S. 408, 418 (2005)). We are mindful, though,\n\nthat equitable tolling \"is a rare remedy to be applied in unusual\n\ncircumstances, not a cure-all for an entirely common state of\n\naffairs.\" Id. (quoting Wallace v. Kato, 549 U.S. 384, 396 (2007)).\n\nFurthermore, the decision to apply equitable tolling is a judgment\n\ncall, see Cordle v. Guarino, 428 F.3d 46, 48 (1st Cir. 2005)\n\n(applying the abuse of discretion standard to the district court's\n\ndecision regarding equitable tolling), so the BIA's decision \"will\n\nstand unless [its] resolution rests on a material error of law or\n\na manifestly arbitrary exercise of judgment,\" Meng Hua Wan v.\n\nHolder, 776 F.3d 52, 56 (1st Cir. 2015) (citing Fustaguio Do\n\nNascimento, 549 F.3d at 18-19).\n\n This court has not decided whether equitable tolling may\n\napply in this context.10 See, e.g., Neves, 613 F.3d at 36; Chedid\n\nv. Holder, 573 F.3d 33, 37 (1st Cir. 2009); see also Mata v. Lynch,\n\n135 S. Ct. 2150, 2156 n.3 (2015) (noting that the Court had \"no\n\nopinion as to whether or when the INA allows the Board to equitably\n\ntoll the 90–day period to file a motion to reopen\"). We take our\n\n\n\n\n10 Gyamfi tells us that we have previously \"indicated that [we]\nwould follow the Ninth and Second Circuits[']\" lead and apply\nequitable tolling in this context, citing our opinion in Jobe v.\nINS, 238 F.3d 96 (1st Cir. 2001) (en banc). Simply put, this is\nnot true, and we need not say more than that.\n\n\n - 11 -\n\fcue from decisions past and assume, without deciding, that the\n\nninety-day rule is subject to equitable tolling. See Neves, 613\n\nF.3d at 36 (citing Chedid, 573 F.3d at 37).\n\n Even giving Gyamfi the benefit of that assumption, she\n\ncannot prevail. First, Gyamfi failed to meet the extraordinary\n\ncircumstances prong. She points us to no authority to support her\n\nsupposition that the existence of new evidence (the I-130) is an\n\nextraordinary circumstance. Indeed, an unforeseeable future\n\noccurrence cannot logically be viewed as an influence on past\n\nconduct. Same goes for her contention about the detrimental impact\n\nof her removal on her children. The horrors she portrays as\n\nbefalling her children should she be required to depart the country\n\nare little different today as during the ninety-day window.\n\nTherefore, neither of Gyamfi's reasons for not timely filing can\n\nbe characterized as an extraordinary circumstance that \"stood in\n\nher way\" when it came to meeting the statutory deadline. Jobe,\n\n238 F.3d at 100 (\"The fundamental principle is that equitable\n\ntolling 'is appropriate only when the circumstances that cause a\n\n[party] to miss a filing deadline are out of [her] hands.'\"\n\n(alteration in original) (quoting Salois v. Dime Sav. Bank, 128\n\nF.3d 20, 25 (1st Cir. 1997))).\n\n In any event, even if we were to assume Gyamfi has\n\ndemonstrated an extraordinary circumstance, she nonetheless fails\n\nto show how she diligently pursued her rights during the ninety-\n\n\n - 12 -\n\fday window or the sixteen months that followed the I-130's\n\napproval. Indeed, even overlooking the ninety-day period (during\n\nwhich she had no reason to seek to reopen as the I-130 was not yet\n\nin play, though she could have brought up the hardship-to-the-\n\nchildren argument), she still has a sixteen-month due diligence\n\nissue for which she has no convincing explanation. Gyamfi's\n\nargument is that she did her due diligence by getting a lawyer\n\n(the same one she'd had throughout, we note) and by submitting her\n\nmotion to reopen once the I-130 was approved. But neither action\n\naccounts for the sixteen-month delay following the I-130's\n\napproval. See, e.g., Dawoud v. Holder, 561 F.3d 31, 36 (1st Cir.\n\n2009) (assuming equitable tolling was available but concluding\n\nnevertheless that a motion to reopen filed out of time (two years\n\npost-final decision and eleven months post-I-130 approval) did not\n\nwarrant equitable tolling); Chedid, 573 F.3d at 37 (holding that\n\nwhen petitioner failed to \"provide[] [any] information whatsoever\n\nregarding the actions he took during the one-year period\n\nimmediately following\" the original order, he failed to\n\ndemonstrate due diligence).\n\n In sum, Gyamfi fails to demonstrate how the BIA abused\n\nits discretion in any way, and having failed to do so, she is bound\n\nby the ninety-day rule, which expired long before she filed her\n\nmotion to reopen.\n\n\n\n\n - 13 -\n\f 2. Do we lack jurisdiction to review the BIA's decision not to\n exercise its sua sponte authority to reopen the proceedings in\n this case?\n\n Absent an abuse of discretion by the BIA in its decision\n\nto deny Gyamfi's motion to reopen, we know that a motion to reopen\n\ncan be granted only if the BIA exercises its sua sponte authority\n\nto reopen the proceedings -- something the BIA was asked to do\n\nhere but did not. Gyamfi contends this was error, specifically,\n\nconstitutional due process error. Peppering this section of her\n\nbriefing with conclusory arguments that appear to be offered in\n\nsupport of her constitutional claim, her primary bone of contention\n\nseems to be that the BIA impermissibly ignored factors she says\n\nshould have been considered as delineated in Matter of J-J-, 21 I.\n\n& N. Dec. 97611 (she lists the following factors: hardship to a\n\npetitioner and her family; a petitioner's criminal history; the\n\nseverity and number of immigration violations; the petitioner's\n\ncooperation with law enforcement; and whether removal would\n\ncomport with the government's policy objectives), thus depriving\n\nher of due process. The government responds by challenging our\n\njurisdiction to entertain Gyamfi's protestations. Therefore,\n\nlet's first discuss the converging dynamic of the BIA's sua sponte\n\nauthority to reopen and our jurisdiction over its use of that\n\nauthority -- to the extent it exists.\n\n\n11This is the same case Gyamfi mysteriously cited in support of\nher equitable tolling claim.\n\n\n - 14 -\n\f In past cases, \"we have repeatedly held that we do not\n\nhave jurisdiction to review challenges to the BIA's failure to\n\nexercise its sua sponte authority because such decisions are\n\n'committed to its unfettered discretion.'\" Matias v. Sessions,\n\n871 F.3d 65, 68 (1st Cir. 2017) (quoting Luis v. INS, 196 F.3d 36,\n\n40 (1st Cir. 1999)); see also Reyes v. Sessions, 886 F.3d 184, 188\n\n(1st Cir. 2018) (quoting Charuc v. Holder, 737 F.3d 113, 115 (1st\n\nCir. 2013)). As rationale for so holding, we explained, \"no\n\njudicially manageable standards are available for judging how and\n\nwhen [the BIA] should exercise its discretion,\" making it\n\n\"impossible to evaluate [the] agency action for 'abuse of\n\ndiscretion'\"; so \"the very nature of the claim renders it not\n\nsubject to judicial review.\" Luis, 196 F.3d at 40 (citations\n\nomitted); see also Neves, 613 F.3d at 35.\n\n In an effort to convince us that we do in fact have\n\njurisdiction, Gyamfi directs us to 8 U.S.C. § 1252(a)(2)(D), which\n\nreads in pertinent part: \"Nothing in subparagraph (B) or (C), or\n\nin any other provision of this chapter (other than this section)\n\nwhich limits or eliminates judicial review, shall be construed as\n\nprecluding review of constitutional claims or questions of law\n\nraised upon a petition for review filed with an appropriate court\n\nof appeals in accordance with this section.\" 8 U.S.C.\n\n§ 1252(a)(2)(D). But this court has yet to rule on whether\n\n§ 1252(a)(2)(D) gives us jurisdiction to review (under certain\n\n\n - 15 -\n\fcircumstances) the BIA's decision not to reopen sua sponte. See\n\nLemus, 900 F.3d at 19 (citing Reyes, 886 F.3d at 188).\n\n Last year, in Matias, we carefully surveyed the\n\nlandscape against which this argument plays out, noting that \"[o]ur\n\nno-jurisdiction rule originated with Luis, 196 F.3d at 40,\" but\n\nrecognizing that Luis \"was decided years before the 2005 passage\n\nof § 1252(a)(2)(D), so the fact that we announced such a blanket\n\nrule then does not decide whether § 1252(a)(2)(D) gives us\n\njurisdiction today.\" Matias, 871 F.3d at 68. And we also observed\n\nthat \"we have previously identified § 1252(a)(2)(D) as a potential\n\njurisdiction-restorer over constitutional claims brought in\n\nmotions for sua sponte relief.\" Id. at 68-69 (citing Guerrero v.\n\nHolder, 766 F.3d 122, 126 n.12 (1st Cir. 2014)). However, \"whether\n\n§ 1252(a)(2)(D) has any effect on Luis's no-jurisdiction rule,\" as\n\nnoted, remains an open question. Id. at 69.\n\n Some of our sister circuits have tackled § 1252(a)(2)(D)\n\nin this context. For example, the Seventh Circuit concluded that\n\n§ 1252(a)(2)(D) gives it jurisdiction to consider legal and\n\nconstitutional claims presented in appeals to the BIA's sua sponte\n\nauthority. Cevilla v. Gonzales, 446 F.3d 658, 660 (7th Cir. 2006)\n\n(reasoning that \"the general 'no law to apply' principle of\n\njudicial review of administrative action has been superseded in\n\nthe immigration context by 8 U.S.C. § 1252(a)(2)[(D)]\"). So in\n\nthe Seventh Circuit, appellate jurisdiction \"extends to the\n\n\n - 16 -\n\fBoard's refusal to reopen . . . removal proceedings sua sponte\"\n\nwhen a constitutional claim or legal question is raised relevant\n\nto an underlying order of removal in the immigration context.\n\nZambrano-Reyes v. Holder, 725 F.3d 744, 751 (7th Cir. 2013).12\n\nOther circuits, however, have a different take: in the Sixth\n\nCircuit, for instance, § 1252(a)(2)(D) was found not to confer\n\njurisdiction in the constitutional-claim context. See, e.g., Rais\n\nv. Holder, 768 F.3d 453, 464 (6th Cir. 2014) (explaining that\n\n§ 1252(a)(2)(D) \"has no bearing on the question of whether courts\n\nmay review the BIA's exercise of its sua sponte authority, for\n\nwhich no chapter of any legislation provides\"); see also Zakar v.\n\nSessions, 739 Fed. Appx. 774, 778 (6th Cir. 2018); Gor v. Holder,\n\n607 F.3d 180, 188 (6th Cir. 2010).\n\n So, all told, some jurisdictions have found\n\n§ 1252(a)(2)(D) to be a game-changer; others have not. But when\n\nfaced with the same argument in both Lemus, 900 F.3d at 19, and\n\nReyes, 886 F.3d at 188, we declined to decide this issue, and we\n\n\n\n\n12 Some other circuits agree. See, e.g., Bonilla v. Lynch, 840\nF.3d 575, 588 (9th Cir. 2016) (deciding that the court \"has\njurisdiction to review [BIA] decisions denying sua sponte\nreopening for the limited purpose of reviewing the reasoning behind\nthe decisions for legal or constitutional error\"); Nawaz v. Holder,\n314 Fed. Appx. 736, 737 (5th Cir. 2009) (per curiam) (concluding\nthat the court did not have jurisdiction to review sua sponte\ndenial unless \"constitutional challenges . . . were raised before\nthe BIA\"); Tamenut v. Mukasey, 521 F.3d 1000, 1005 (8th Cir. 2008)\n(per curiam) (same).\n\n\n\n - 17 -\n\fdo so again today. That is because § 1252(a)(2)(D) \"only arguably\n\napplies to a petitioner's constitutional or legal challenges if\n\nthey are colorable,\" Lemus, 900 F.3d at 19 (citing Ayeni v. Holder,\n\n617 F.3d 67, 71 (1st Cir. 2010)), and here, even if § 1252(a)(2)(D)\n\nserves as a basis for jurisdiction, Gyamfi has not set forth any\n\ncolorable claims. We explain.\n\n As we said in Lemus, a due process claim can succeed\n\nonly if there is a \"cognizable liberty interest.\" 900 F.3d at 19\n\n(quoting Matias, 871 F.3d at 72). We have further pointed out\n\nthat the BIA's decision whether to exercise its \"purely\n\ndiscretionary\" sua sponte authority \"does not create a cognizable\n\nliberty interest.\" Matias, 871 F.3d at 72 (quoting Mejia-\n\nOrellana v. Gonzales, 502 F.3d 13, 17 (1st Cir. 2007)). And aside\n\nfrom faulting the BIA for not exercising its discretionary\n\nauthority to reopen her removal proceedings, Gyamfi has not\n\nidentified any other cognizable liberty interest. In fact, Gyamfi\n\ndrops the phrase \"due process\" one single time in her brief, and\n\nher points purportedly in support of her due-process claim\n\n(relating to the hardship to be suffered by her children) do not\n\nsupport the outcome she seeks and are not buttressed by controlling\n\nauthority. We have said -- and now repeat -- that \"'[a] bare\n\nallegation of either a constitutional shortfall or legal error'\n\nwill not suffice,\" Rivera v. Sessions, 903 F.3d 147, 150 (1st Cir.\n\n2018) (quoting Ayeni v. Holder, 617 F.3d 67, 71 (1st Cir. 2010)),\n\n\n - 18 -\n\fand \"mere 'invocation of the Due Process Clause does not create a\n\nconstitutional claim for the purpose of 8 U.S.C. § 1252(a)(2)(D),'\"\n\nid. (quoting Cruz-Orellana v. Sessions, 878 F.3d 1, 5 (1st Cir.\n\n2017)).\n\n Meanwhile, Gyamfi's reliance on Matter of J-J-, 21 I.\n\n& N. Dec. 976, is misplaced and unpersuasive (and downright odd):\n\nthe factors Gyamfi complains were ignored by the BIA (hardship to\n\na petitioner and his/her family, a petitioner's criminal history,\n\nthe severity and number of immigration missteps) nowhere appear in\n\nMatter of J-J-, and we are unable to find any authority (and Gyamfi\n\npoints to no other) that establishes that the BIA's failure to\n\nmention these factors constitutes a violation of due process.13\n\n In sum, Gyamfi cannot prevail -- even if § 1252(a)(2)(D)\n\nwere to provide an arguable basis for jurisdiction over\n\n\n\n\n13 We are baffled by Gyamfi's reading of Matter of J-J-. That\ncase makes no mention of a due process limitation to the BIA's\ndiscretion to reopen removal proceedings, much less articulates a\nfive-factor test for the supposed limitation. Rather, it is\nevident from our own research that the factors Gyamfi recites are\nborrowed from a 2001 INS directive. See Memorandum regarding\nMotions to Reopen for Consideration of Adjustment of Status from\nBo Cooper, General Counsel for Immigration and Naturalization\nService, to Regional Counsel (May 17, 2001),\nhttps://www.aila.org/infonet/ins-standards-to-join-a-motion-to-\nreopen. Far from governing the BIA's discretion to reopen a case\nsua sponte, the factors listed in this memorandum guide DHS's\ndiscretion in deciding whether to join a petitioner in her motion\nto reopen. Id. This is not a matter of concern for the court,\nand that Gyamfi would lure us into this investigative rabbit hole\nat all is troublesome.\n\n\n - 19 -\n\fconstitutional claims, Gyamfi has no colorable constitutional or\n\nlegal claim on which we might base jurisdiction.\n\n CONCLUSION\n\n Gyamfi's petition for review is denied as to her\n\nchallenge to the BIA's determination that the motion to reopen was\n\nuntimely, and it is dismissed for lack of jurisdiction as to her\n\nchallenge to the BIA's decision to not exercise its authority to\n\nreopen sua sponte.\n\n\n\n\n - 20 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357874/", "author_raw": "THOMPSON, Circuit Judge"}]}
THOMPSON
KAYATTA
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580621/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Amma Adu GYAMFI, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1093\n\n AMMA ADU GYAMFI,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Thompson, Kayatta, and Barron,\n Circuit Judges.\n\n\n Saher Joseph Macarius, Audrey Botros, and Law Offices of Saher\nJoseph Macarius LLC on brief for petitioner.\n Chad A. Readler, Acting Assistant Attorney General, Civil\nDivision, M. Jocelyn Lopez Wright, Senior Litigation Counsel,\nOffice of Immigration Litigation, and Anna Juarez, Trial Attorney,\nOffice of Immigration Litigation, on brief for respondent.\n\n\n January 10, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney General\nMatthew G. Whitaker has been substituted for former Attorney\nGeneral Jefferson B. Sessions, III as the respondent.\n\f THOMPSON, Circuit Judge. Petitioner Amma Adu Gyamfi\n\n(\"Gyamfi\") challenges the Board of Immigration Appeals's (\"BIA\")\n\ndenial of her motion to reopen and its decision not to exercise\n\nits sua sponte authority to reopen her case and grant her request\n\nfor an adjustment of status. For the reasons we detail below, we\n\ndeny and dismiss Gyamfi's petition.\n\n BACKGROUND\n\n In March of 2004, Gyamfi, a native of Ghana and resident\n\nof Italy from 1992 until 2004, arrived in the U.S. on a\n\nnonimmigrant B-2 visa that granted her a six-month stay here.\n\nGyamfi didn't leave after her permissible time here expired, and\n\nin November 2007, she married a U.S. citizen, Mark Parrish. That\n\nfollowing April, Parrish filed an I-130 petition1 to get Gyamfi\n\ngreen-card status as the spouse of a U.S. citizen, but when the\n\nDepartment of Homeland Security (\"DHS\") issued a notice of intent\n\nto deny the petition (because the newlyweds hadn't demonstrated\n\nthe legitimacy of their marriage), Parrish wound up admitting in\n\na 2009 DHS interview that he had made the petition as \"a favor\" to\n\nGyamfi. Consequently, he withdrew the petition, and DHS denied\n\nGyamfi's application for adjustment of status in April 2009.\n\n\n\n\n1 An I-130 petition allows a U.S. citizen or lawful permanent\nresident to sponsor an alien relative's application for permanent\nresident status.\n\n\n - 2 -\n\f A month later, DHS initiated removal proceedings against\n\nGyamfi: she was charged with removability as an alien who remained\n\nin the U.S. for a time longer than permitted after being admitted\n\nas a nonimmigrant visitor (8 U.S.C. § 1227(a)(1)(B)).2 Over the\n\ncourse of a couple of years (2009-2010) and a few hearings before\n\nan immigration judge (\"IJ\"), Gyamfi would first pursue a new I-\n\n130 petition, then withdraw it, and in the end, seek asylum\n\nprotection.3\n\n Unpersuaded by her arguments and testimony relative to\n\nher lamentations of persecution, in March 2013, the IJ ordered her\n\nremoved.4 The BIA affirmed the IJ and, in July 2014, dismissed\n\nthe appeal. Gyamfi did not seek judicial review of that decision.\n\n Fast-forward three years to August 31, 2017: in light\n\nof an I-130 petition filed in November 2015 on her behalf by her\n\nrecently naturalized U.S. citizen daughter5 (and which was approved\n\n\n2 Gyamfi also was charged as an alien who was inadmissible at the\ntime of entry because she procured, or sought to procure, an\nimmigration benefit by fraud or by willfully misrepresenting a\nmaterial fact, 8 U.S.C. § 1227(a)(1)(A), but that was later\nwithdrawn.\n3 She testified at a September 2010 hearing that she never applied\n\nfor asylum in Italy, her home for thirteen years after leaving\nGhana in 1992. As for why she never mentioned harboring any fear\nof returning to Ghana between her 2004 arrival in the U.S. and the\nSeptember 2010 hearing, she testified she had hoped to adjust\nstatus through Parrish.\n4 During the proceedings before the IJ, Gyamfi conceded\nremovability only as an alien who overstayed her visitor's visa.\n5 Gyamfi has six children, five of whom are U.S. citizens and live\n\nin the United States. Her eldest child, now 28 years old, is a\ncitizen of Ghana residing there. Her next two eldest, now 25 and\n\n\n - 3 -\n\fby DHS in April 2016), Gyamfi sought to adjust her status. She\n\nmoved to reopen her case and also requested sua sponte (\"on its\n\nown motion\") reopening by the BIA premised on the hardship her\n\nremoval would have on her children. In response, DHS filed an\n\nopposition to the motion, albeit late.\n\n The BIA denied Gyamfi's motion as untimely (the final\n\nadministrative order entered in July of 2014, and the BIA didn't\n\nreceive the motion to reopen until August 2017) and not falling\n\nwithin any exception to the ninety-day window to file a motion to\n\nreopen. See 8 U.S.C. § 1229a(c)(7)(C)(i); 8 C.F.R.\n\n§§ 1003.2(c)(2), 1003(c)(3)(i)-(iv). In addition, the BIA\n\ndeclined to exercise its discretionary authority to reopen the\n\nproceedings sua sponte, finding that Gyamfi failed to demonstrate\n\nan exceptional situation that would warrant the exercise of its\n\nsua sponte power, and she alleged \"no current health issues\n\nregarding [her I-130-petitioning daughter] or her other United\n\nStates citizen children that might warrant a finding of exceptional\n\ncircumstances.\"\n\n Gyamfi timely petitioned this court for review.\n\n ANALYSIS\n\n Gyamfi offers up a smorgasbord of appellate contentions,\n\n\n\n\n21 years old, were born in Italy, but are U.S. citizens residing\nhere. And she has three minor U.S. citizen children (ages 17, 12,\nand 10), all of whom were born in the U.S. and live here now.\n\n\n - 4 -\n\fbut distilling those arguments to their core essence as best we\n\ncan, we think they primarily fit under two main headings: (1) the\n\nBIA abused its discretion by denying her motion to reopen; or, in\n\nthe alternative, (2) the BIA should have deployed its discretionary\n\nauthority to reopen the proceedings sua sponte. She advances\n\nvarious arguments in support of these two issues, which we will\n\nexplore in turn.\n\n And as we review Gyamfi's contestations, we necessarily\n\nbear in mind our familiar standard: to the extent we have\n\njurisdiction, \"[b]ecause a motion to reopen removal proceedings is\n\na disfavored tool, given the threat it poses to finality, the BIA\n\nhas a fair amount of latitude to grant or deny the motion and our\n\nreview is for abuse of discretion only.\" Mazariegos v. Lynch, 790\n\nF.3d 280, 285 (1st Cir. 2015) (citing Perez v. Holder, 740 F.3d\n\n57, 61 (1st Cir. 2014)); see also Sihotang v. Sessions, 900 F.3d\n\n46, 48 (1st Cir. 2018) (\"Motions to reopen -- especially untimely\n\nmotions to reopen -- are disfavored in immigration cases.\n\nConsequently, an alien who seeks to reopen removal proceedings out\n\nof time ordinarily faces a steep uphill climb.\"). Unless a\n\npetitioner can show that the BIA either committed a material error\n\nof law or exercised its authority arbitrarily, capriciously, or\n\nirrationally, we will uphold the BIA's decision. See Bbale v.\n\nLynch, 840 F.3d 63, 66 (1st Cir. 2016) (citing Rosa v. Gonzales,\n\n484 F.3d 125, 127 (1st Cir. 2007)).\n\n\n - 5 -\n\f Before diving into Gyamfi's argument, saying a bit more\n\nabout the pertinent aspects of the ninety-day rule would be\n\nhelpful.6 Pursuant to 8 U.S.C. § 1229a(c)(7)(C)(i), an alien is\n\nentitled to file one motion to reopen removal proceedings within\n\nninety days after the final order of removal. See id. (instructing\n\nthat, unless an exception applies, \"the motion to reopen shall be\n\nfiled within 90 days of the date of entry of a final administrative\n\norder of removal\"); see also 8 C.F.R. § 1003.2(c)(2) (stating that,\n\nsave for specified exceptions, \"an alien may file only one motion\n\nto reopen removal proceedings (whether before the Board or the\n\nImmigration Judge) and that motion must be filed no later than 90\n\ndays after the date on which the final administrative decision was\n\nrendered in the proceeding sought to be reopened\"); Neves v.\n\nHolder, 613 F.3d 30, 32-33 (1st Cir. 2010)(per curiam). As for\n\n\n\n\n6 We note here that Gyamfi makes the assertion that a petitioner\ncan file a motion to reopen either within ninety days of the final\nadministrative order or within 180 days due to exceptional\ncircumstances, citing INA § 240(b)(5)(c)(i), (e)(6)(C) -- this\nprovision has been repealed, and its replacement is codified at 8\nU.S.C. § 1229a(b)(5)(C)(i). There, the reference to 180 days\nconcerns rescission of an order of removal issued because of an\nalien's failure to appear: such a removal order can be rescinded\nif an alien files a motion to reopen \"within 180 days after the\ndate of the order of removal if the alien demonstrates that the\nfailure to appear was because of exceptional circumstances\n. . . .\" Sec. 1229a(b)(5)(C)(i). This is not in play in\nGyamfi's case, thus the 180-day cut-off is not applicable.\n\n\n - 6 -\n\fthe exceptions, Congress enacted a limited list. See 8 U.S.C. §\n\n1229a(c)(7)(C)(ii)-(iv); 8 C.F.R. § 1003.2(c)(3).7\n\n 1. Did the BIA abuse its discretion?8\n\n a. The Ninety-Day Rule\n\n Gyamfi claims the BIA abused its discretion when it\n\ndeclined to grant her motion to reopen. She does not dispute that\n\nher August 2017 filing missed the deadline -- the BIA's final\n\n\n\n\n7 For example, 8 C.F.R. § 1003.2(c)(3) instructs that the ninety-\nday rule\n\n [s]hall not apply to a motion to reopen proceedings:\n\n . . .\n\n (ii) To apply or reapply for asylum or withholding of\n deportation based on changed circumstances arising in\n the country of nationality or in the country to which\n deportation has been ordered, if such evidence is\n material and was not available and could not have been\n discovered or presented at the previous hearing;\n\n (iii) Agreed upon by all parties and jointly filed.\n Notwithstanding such agreement, the parties may contest\n the issues in a reopened proceeding[.]\n\n8 As a threshold matter, Gyamfi submits that the BIA stumbled out\nof the starting gate when it deemed her motion opposed. Recall\nthat DHS's opposition to Gyamfi's motion to reopen was filed out\nof time -- Gyamfi submitted a response to that late filing. But\nwe espy no error of law or abuse of discretion. As the government\ncorrectly points out, considering a late-filed brief is not\nproscribed, see 8 C.F.R. § 1003.2(g)(3), and regardless, the BIA\nis duty-bound to use its independent judgment when facing these\nmotions, 8 C.F.R. § 1003.1(d)(1)(ii). And besides, Gyamfi does\nnot even argue that the BIA improperly based its denial of her\nmotion on the substantive arguments in DHS's papers. This\nargument, then, is a nonstarter, so we move on to her primary\nchallenges.\n\n\n - 7 -\n\fadministrative order was issued on July 17, 2014 and October 13,\n\n2014 (ninety days later) was the last day Gyamfi could have filed\n\nher motion. However, she asserts that because she was \"prima\n\nfacie\" eligible for status adjustment as a result of the previously\n\nunavailable evidence (the I-130 visa her daughter filed on her\n\nbehalf long after the expiration of the ninety-day limit), the BIA\n\nshould have ruled differently on 8 U.S.C. § 1229a(c)(7)(C)(i)'s\n\nninety-day bar.\n\n The government disagrees, and its position is simple:\n\nthe ninety-day limit expired and no exception applies. Indeed,\n\nthe government points out that Gyamfi cannot be \"prima facie\"\n\neligible for status adjustment given the untimeliness of her\n\nmotion.\n\n In support of her claim of \"prima facie\" eligibility\n\nGyamfi cites to Matter of Garcia, 16 I. & N. Dec. 653, 654 (B.I.A.\n\n1978), a case wherein the BIA explained the appropriateness of\n\nexercising its discretion (at least at that time) to reopen\n\nimmigration proceedings during the pendency of adjustment of\n\nstatus applications of prima facie eligible movants. But her\n\nreliance on this case is misplaced. Garcia was decided before\n\nCongress enacted time and number bars on motions to reopen, Lemus\n\nv. Sessions, 900 F.3d 15, 19 (1st Cir. 2018) (citing Dada v.\n\nMukasey, 554 U.S. 1, 13 (2008) (outlining that history)), and\n\nwhat's more, the BIA, itself, has moved away from its Garcia\n\n\n - 8 -\n\fholding, see id. (collecting BIA cases). Given this evolution\n\n(and as we have previously noted), our confidence in Garcia's\n\ncontinuing applicability has been undercut. Id. But whether or\n\nnot viable, Garcia's recognition of the IJ's discretionary\n\nauthority is not a rule mandating the exercise of same.\n\n Accordingly, we believe the government has the better\n\nargument on the application of the ninety-day rule. Though Gyamfi\n\ntells us she can present new evidence, clearly the new evidence\n\nshe offers, an I-130 visa, is not a statutory exception to the\n\nrule. See 8 U.S.C. § 1229a(c)(7)(C); 8 C.F.R. § 1003.2(c)(3)(i)-\n\n(iv). And absent an exception operating to prevent the ninety-\n\nday rule from applying (Gyamfi doesn't actually argue that one\n\ndoes), motions to reopen are subject to the ninety-day rule and\n\nGyamfi missed it. We see no abuse of discretion.\n\n b. Equitable Tolling\n\n Alternatively, Gyamfi argues the BIA erred in not\n\nreopening her removal proceedings because she established \"unusual\n\nfacts and exceptional circumstances\" meriting the equitable\n\ntolling of the ninety-day deadline for filing such motions.\n\nGyamfi submits that she's made the equitable tolling showing by,\n\nfirst, demonstrating that she couldn't have known about her new I-\n\n130 beneficiary status within ninety days of her original\n\nproceedings and as such, her ignorance of what the future actually\n\nwould bring constitutes an extraordinary circumstance. As she\n\n\n - 9 -\n\fputs it, \"applying this statutory deadline does not serve the\n\ninterests of justice in this case.\" Second, she puts into the\n\n\"extraordinary circumstances\" basket the BIA's alleged error in\n\nneglecting to consider any factors besides the health of her\n\nchildren.9 In particular, she emphasizes the hardship her removal\n\nwill have on her kids: if they return to Ghana with Gyamfi, they\n\nwill not enjoy a U.S. education, and Ghanaian high crime and\n\nmortality rates, for example, would negatively affect them; and if\n\nthey stay in the U.S. without her, this also would negatively\n\nimpact them. The government responds that even if equitable\n\ntolling was a viable avenue to relief in the immigration context,\n\nthe BIA did not abuse its discretion in finding that Gyamfi has\n\nnot made the requisite showing to support its use. Once again, we\n\nagree with the government.\n\n Equitable tolling \"extends statutory deadlines in\n\nextraordinary circumstances for parties who were prevented from\n\ncomplying with them through no fault or lack of diligence of their\n\nown.\" Neves, 613 F.3d at 36 (citing Fustaguio Do Nascimento v.\n\nMukasey, 549 F.3d 12, 18-19 (1st Cir. 2008)). So the party seeking\n\nto toll the deadline bears the burden of showing: \"(1) that he has\n\n\n9 Gyamfi also points to the \"five factors\" laid out in Matter of\nJ-J-, 21 I. & N. Dec. 976 (B.I.A. 1997), saying the BIA's failure\nto consider these factors constitutes legal error. To the extent\nshe means to argue that case to support her equitable tolling\nargument, we fail to see its relevance -- Matter of J-J- does not\ntouch on equitable tolling.\n\n\n - 10 -\n\fbeen pursuing his rights diligently, and (2) that some\n\nextraordinary circumstance stood in his way.\" Id. (quoting Pace\n\nv. DiGuglielmo, 544 U.S. 408, 418 (2005)). We are mindful, though,\n\nthat equitable tolling \"is a rare remedy to be applied in unusual\n\ncircumstances, not a cure-all for an entirely common state of\n\naffairs.\" Id. (quoting Wallace v. Kato, 549 U.S. 384, 396 (2007)).\n\nFurthermore, the decision to apply equitable tolling is a judgment\n\ncall, see Cordle v. Guarino, 428 F.3d 46, 48 (1st Cir. 2005)\n\n(applying the abuse of discretion standard to the district court's\n\ndecision regarding equitable tolling), so the BIA's decision \"will\n\nstand unless [its] resolution rests on a material error of law or\n\na manifestly arbitrary exercise of judgment,\" Meng Hua Wan v.\n\nHolder, 776 F.3d 52, 56 (1st Cir. 2015) (citing Fustaguio Do\n\nNascimento, 549 F.3d at 18-19).\n\n This court has not decided whether equitable tolling may\n\napply in this context.10 See, e.g., Neves, 613 F.3d at 36; Chedid\n\nv. Holder, 573 F.3d 33, 37 (1st Cir. 2009); see also Mata v. Lynch,\n\n135 S. Ct. 2150, 2156 n.3 (2015) (noting that the Court had \"no\n\nopinion as to whether or when the INA allows the Board to equitably\n\ntoll the 90–day period to file a motion to reopen\"). We take our\n\n\n\n\n10 Gyamfi tells us that we have previously \"indicated that [we]\nwould follow the Ninth and Second Circuits[']\" lead and apply\nequitable tolling in this context, citing our opinion in Jobe v.\nINS, 238 F.3d 96 (1st Cir. 2001) (en banc). Simply put, this is\nnot true, and we need not say more than that.\n\n\n - 11 -\n\fcue from decisions past and assume, without deciding, that the\n\nninety-day rule is subject to equitable tolling. See Neves, 613\n\nF.3d at 36 (citing Chedid, 573 F.3d at 37).\n\n Even giving Gyamfi the benefit of that assumption, she\n\ncannot prevail. First, Gyamfi failed to meet the extraordinary\n\ncircumstances prong. She points us to no authority to support her\n\nsupposition that the existence of new evidence (the I-130) is an\n\nextraordinary circumstance. Indeed, an unforeseeable future\n\noccurrence cannot logically be viewed as an influence on past\n\nconduct. Same goes for her contention about the detrimental impact\n\nof her removal on her children. The horrors she portrays as\n\nbefalling her children should she be required to depart the country\n\nare little different today as during the ninety-day window.\n\nTherefore, neither of Gyamfi's reasons for not timely filing can\n\nbe characterized as an extraordinary circumstance that \"stood in\n\nher way\" when it came to meeting the statutory deadline. Jobe,\n\n238 F.3d at 100 (\"The fundamental principle is that equitable\n\ntolling 'is appropriate only when the circumstances that cause a\n\n[party] to miss a filing deadline are out of [her] hands.'\"\n\n(alteration in original) (quoting Salois v. Dime Sav. Bank, 128\n\nF.3d 20, 25 (1st Cir. 1997))).\n\n In any event, even if we were to assume Gyamfi has\n\ndemonstrated an extraordinary circumstance, she nonetheless fails\n\nto show how she diligently pursued her rights during the ninety-\n\n\n - 12 -\n\fday window or the sixteen months that followed the I-130's\n\napproval. Indeed, even overlooking the ninety-day period (during\n\nwhich she had no reason to seek to reopen as the I-130 was not yet\n\nin play, though she could have brought up the hardship-to-the-\n\nchildren argument), she still has a sixteen-month due diligence\n\nissue for which she has no convincing explanation. Gyamfi's\n\nargument is that she did her due diligence by getting a lawyer\n\n(the same one she'd had throughout, we note) and by submitting her\n\nmotion to reopen once the I-130 was approved. But neither action\n\naccounts for the sixteen-month delay following the I-130's\n\napproval. See, e.g., Dawoud v. Holder, 561 F.3d 31, 36 (1st Cir.\n\n2009) (assuming equitable tolling was available but concluding\n\nnevertheless that a motion to reopen filed out of time (two years\n\npost-final decision and eleven months post-I-130 approval) did not\n\nwarrant equitable tolling); Chedid, 573 F.3d at 37 (holding that\n\nwhen petitioner failed to \"provide[] [any] information whatsoever\n\nregarding the actions he took during the one-year period\n\nimmediately following\" the original order, he failed to\n\ndemonstrate due diligence).\n\n In sum, Gyamfi fails to demonstrate how the BIA abused\n\nits discretion in any way, and having failed to do so, she is bound\n\nby the ninety-day rule, which expired long before she filed her\n\nmotion to reopen.\n\n\n\n\n - 13 -\n\f 2. Do we lack jurisdiction to review the BIA's decision not to\n exercise its sua sponte authority to reopen the proceedings in\n this case?\n\n Absent an abuse of discretion by the BIA in its decision\n\nto deny Gyamfi's motion to reopen, we know that a motion to reopen\n\ncan be granted only if the BIA exercises its sua sponte authority\n\nto reopen the proceedings -- something the BIA was asked to do\n\nhere but did not. Gyamfi contends this was error, specifically,\n\nconstitutional due process error. Peppering this section of her\n\nbriefing with conclusory arguments that appear to be offered in\n\nsupport of her constitutional claim, her primary bone of contention\n\nseems to be that the BIA impermissibly ignored factors she says\n\nshould have been considered as delineated in Matter of J-J-, 21 I.\n\n& N. Dec. 97611 (she lists the following factors: hardship to a\n\npetitioner and her family; a petitioner's criminal history; the\n\nseverity and number of immigration violations; the petitioner's\n\ncooperation with law enforcement; and whether removal would\n\ncomport with the government's policy objectives), thus depriving\n\nher of due process. The government responds by challenging our\n\njurisdiction to entertain Gyamfi's protestations. Therefore,\n\nlet's first discuss the converging dynamic of the BIA's sua sponte\n\nauthority to reopen and our jurisdiction over its use of that\n\nauthority -- to the extent it exists.\n\n\n11This is the same case Gyamfi mysteriously cited in support of\nher equitable tolling claim.\n\n\n - 14 -\n\f In past cases, \"we have repeatedly held that we do not\n\nhave jurisdiction to review challenges to the BIA's failure to\n\nexercise its sua sponte authority because such decisions are\n\n'committed to its unfettered discretion.'\" Matias v. Sessions,\n\n871 F.3d 65, 68 (1st Cir. 2017) (quoting Luis v. INS, 196 F.3d 36,\n\n40 (1st Cir. 1999)); see also Reyes v. Sessions, 886 F.3d 184, 188\n\n(1st Cir. 2018) (quoting Charuc v. Holder, 737 F.3d 113, 115 (1st\n\nCir. 2013)). As rationale for so holding, we explained, \"no\n\njudicially manageable standards are available for judging how and\n\nwhen [the BIA] should exercise its discretion,\" making it\n\n\"impossible to evaluate [the] agency action for 'abuse of\n\ndiscretion'\"; so \"the very nature of the claim renders it not\n\nsubject to judicial review.\" Luis, 196 F.3d at 40 (citations\n\nomitted); see also Neves, 613 F.3d at 35.\n\n In an effort to convince us that we do in fact have\n\njurisdiction, Gyamfi directs us to 8 U.S.C. § 1252(a)(2)(D), which\n\nreads in pertinent part: \"Nothing in subparagraph (B) or (C), or\n\nin any other provision of this chapter (other than this section)\n\nwhich limits or eliminates judicial review, shall be construed as\n\nprecluding review of constitutional claims or questions of law\n\nraised upon a petition for review filed with an appropriate court\n\nof appeals in accordance with this section.\" 8 U.S.C.\n\n§ 1252(a)(2)(D). But this court has yet to rule on whether\n\n§ 1252(a)(2)(D) gives us jurisdiction to review (under certain\n\n\n - 15 -\n\fcircumstances) the BIA's decision not to reopen sua sponte. See\n\nLemus, 900 F.3d at 19 (citing Reyes, 886 F.3d at 188).\n\n Last year, in Matias, we carefully surveyed the\n\nlandscape against which this argument plays out, noting that \"[o]ur\n\nno-jurisdiction rule originated with Luis, 196 F.3d at 40,\" but\n\nrecognizing that Luis \"was decided years before the 2005 passage\n\nof § 1252(a)(2)(D), so the fact that we announced such a blanket\n\nrule then does not decide whether § 1252(a)(2)(D) gives us\n\njurisdiction today.\" Matias, 871 F.3d at 68. And we also observed\n\nthat \"we have previously identified § 1252(a)(2)(D) as a potential\n\njurisdiction-restorer over constitutional claims brought in\n\nmotions for sua sponte relief.\" Id. at 68-69 (citing Guerrero v.\n\nHolder, 766 F.3d 122, 126 n.12 (1st Cir. 2014)). However, \"whether\n\n§ 1252(a)(2)(D) has any effect on Luis's no-jurisdiction rule,\" as\n\nnoted, remains an open question. Id. at 69.\n\n Some of our sister circuits have tackled § 1252(a)(2)(D)\n\nin this context. For example, the Seventh Circuit concluded that\n\n§ 1252(a)(2)(D) gives it jurisdiction to consider legal and\n\nconstitutional claims presented in appeals to the BIA's sua sponte\n\nauthority. Cevilla v. Gonzales, 446 F.3d 658, 660 (7th Cir. 2006)\n\n(reasoning that \"the general 'no law to apply' principle of\n\njudicial review of administrative action has been superseded in\n\nthe immigration context by 8 U.S.C. § 1252(a)(2)[(D)]\"). So in\n\nthe Seventh Circuit, appellate jurisdiction \"extends to the\n\n\n - 16 -\n\fBoard's refusal to reopen . . . removal proceedings sua sponte\"\n\nwhen a constitutional claim or legal question is raised relevant\n\nto an underlying order of removal in the immigration context.\n\nZambrano-Reyes v. Holder, 725 F.3d 744, 751 (7th Cir. 2013).12\n\nOther circuits, however, have a different take: in the Sixth\n\nCircuit, for instance, § 1252(a)(2)(D) was found not to confer\n\njurisdiction in the constitutional-claim context. See, e.g., Rais\n\nv. Holder, 768 F.3d 453, 464 (6th Cir. 2014) (explaining that\n\n§ 1252(a)(2)(D) \"has no bearing on the question of whether courts\n\nmay review the BIA's exercise of its sua sponte authority, for\n\nwhich no chapter of any legislation provides\"); see also Zakar v.\n\nSessions, 739 Fed. Appx. 774, 778 (6th Cir. 2018); Gor v. Holder,\n\n607 F.3d 180, 188 (6th Cir. 2010).\n\n So, all told, some jurisdictions have found\n\n§ 1252(a)(2)(D) to be a game-changer; others have not. But when\n\nfaced with the same argument in both Lemus, 900 F.3d at 19, and\n\nReyes, 886 F.3d at 188, we declined to decide this issue, and we\n\n\n\n\n12 Some other circuits agree. See, e.g., Bonilla v. Lynch, 840\nF.3d 575, 588 (9th Cir. 2016) (deciding that the court \"has\njurisdiction to review [BIA] decisions denying sua sponte\nreopening for the limited purpose of reviewing the reasoning behind\nthe decisions for legal or constitutional error\"); Nawaz v. Holder,\n314 Fed. Appx. 736, 737 (5th Cir. 2009) (per curiam) (concluding\nthat the court did not have jurisdiction to review sua sponte\ndenial unless \"constitutional challenges . . . were raised before\nthe BIA\"); Tamenut v. Mukasey, 521 F.3d 1000, 1005 (8th Cir. 2008)\n(per curiam) (same).\n\n\n\n - 17 -\n\fdo so again today. That is because § 1252(a)(2)(D) \"only arguably\n\napplies to a petitioner's constitutional or legal challenges if\n\nthey are colorable,\" Lemus, 900 F.3d at 19 (citing Ayeni v. Holder,\n\n617 F.3d 67, 71 (1st Cir. 2010)), and here, even if § 1252(a)(2)(D)\n\nserves as a basis for jurisdiction, Gyamfi has not set forth any\n\ncolorable claims. We explain.\n\n As we said in Lemus, a due process claim can succeed\n\nonly if there is a \"cognizable liberty interest.\" 900 F.3d at 19\n\n(quoting Matias, 871 F.3d at 72). We have further pointed out\n\nthat the BIA's decision whether to exercise its \"purely\n\ndiscretionary\" sua sponte authority \"does not create a cognizable\n\nliberty interest.\" Matias, 871 F.3d at 72 (quoting Mejia-\n\nOrellana v. Gonzales, 502 F.3d 13, 17 (1st Cir. 2007)). And aside\n\nfrom faulting the BIA for not exercising its discretionary\n\nauthority to reopen her removal proceedings, Gyamfi has not\n\nidentified any other cognizable liberty interest. In fact, Gyamfi\n\ndrops the phrase \"due process\" one single time in her brief, and\n\nher points purportedly in support of her due-process claim\n\n(relating to the hardship to be suffered by her children) do not\n\nsupport the outcome she seeks and are not buttressed by controlling\n\nauthority. We have said -- and now repeat -- that \"'[a] bare\n\nallegation of either a constitutional shortfall or legal error'\n\nwill not suffice,\" Rivera v. Sessions, 903 F.3d 147, 150 (1st Cir.\n\n2018) (quoting Ayeni v. Holder, 617 F.3d 67, 71 (1st Cir. 2010)),\n\n\n - 18 -\n\fand \"mere 'invocation of the Due Process Clause does not create a\n\nconstitutional claim for the purpose of 8 U.S.C. § 1252(a)(2)(D),'\"\n\nid. (quoting Cruz-Orellana v. Sessions, 878 F.3d 1, 5 (1st Cir.\n\n2017)).\n\n Meanwhile, Gyamfi's reliance on Matter of J-J-, 21 I.\n\n& N. Dec. 976, is misplaced and unpersuasive (and downright odd):\n\nthe factors Gyamfi complains were ignored by the BIA (hardship to\n\na petitioner and his/her family, a petitioner's criminal history,\n\nthe severity and number of immigration missteps) nowhere appear in\n\nMatter of J-J-, and we are unable to find any authority (and Gyamfi\n\npoints to no other) that establishes that the BIA's failure to\n\nmention these factors constitutes a violation of due process.13\n\n In sum, Gyamfi cannot prevail -- even if § 1252(a)(2)(D)\n\nwere to provide an arguable basis for jurisdiction over\n\n\n\n\n13 We are baffled by Gyamfi's reading of Matter of J-J-. That\ncase makes no mention of a due process limitation to the BIA's\ndiscretion to reopen removal proceedings, much less articulates a\nfive-factor test for the supposed limitation. Rather, it is\nevident from our own research that the factors Gyamfi recites are\nborrowed from a 2001 INS directive. See Memorandum regarding\nMotions to Reopen for Consideration of Adjustment of Status from\nBo Cooper, General Counsel for Immigration and Naturalization\nService, to Regional Counsel (May 17, 2001),\nhttps://www.aila.org/infonet/ins-standards-to-join-a-motion-to-\nreopen. Far from governing the BIA's discretion to reopen a case\nsua sponte, the factors listed in this memorandum guide DHS's\ndiscretion in deciding whether to join a petitioner in her motion\nto reopen. Id. This is not a matter of concern for the court,\nand that Gyamfi would lure us into this investigative rabbit hole\nat all is troublesome.\n\n\n - 19 -\n\fconstitutional claims, Gyamfi has no colorable constitutional or\n\nlegal claim on which we might base jurisdiction.\n\n CONCLUSION\n\n Gyamfi's petition for review is denied as to her\n\nchallenge to the BIA's determination that the motion to reopen was\n\nuntimely, and it is dismissed for lack of jurisdiction as to her\n\nchallenge to the BIA's decision to not exercise its authority to\n\nreopen sua sponte.\n\n\n\n\n - 20 -\n[END_CASE]", "role": "user" } ]
4,581,697
Thomas GUILFOILE, Plaintiff, Appellant, v. John M. SHIELDS, Sr.; Shields Pharmacy, LLC, D/B/A Shields Health Solutions; UMass Memorial Shields Pharmacy, LLC, D/B/A Shields Health Solutions; Shields Pharmacy Equity, LLC, D/B/A Shields Health Solutions; Shields Specialty Pharmacy Holdings, LLC, D/B/A Shields Health Solutions, Defendants, Appellees.
Guilfoile v. Shields
2019-01-15
17-1610P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Lipez, Barron", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887866/", "author_raw": ""}, {"author": "", "type": "035concurrenceinpart", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887867/", "author_raw": ""}, {"author": "LIPEZ, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1610\n\n THOMAS GUILFOILE,\n\n Plaintiff, Appellant,\n\n v.\n\n JOHN M. SHIELDS, SR.; SHIELDS PHARMACY, LLC, d/b/a Shields\n Health Solutions; UMASS MEMORIAL SHIELDS PHARMACY, LLC, d/b/a\n Shields Health Solutions; SHIELDS PHARMACY EQUITY, LLC, d/b/a\n Shields Health Solutions; SHIELDS SPECIALTY PHARMACY HOLDINGS,\n LLC, d/b/a Shields Health Solutions,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Denise J. Casper, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Lipez and Barron, Circuit Judges.\n\n\n Paul W. Mollica, with whom Tammy T. Marzigliano and Outten &\nGolden LLP were on brief, for appellant.\n Brian J. Leske for appellees.\n Michael J. Sullivan and Ashcroft Law Firm, LLC on brief for\n appellee John M. Shields.\n Walter B. Prince, William A. Worth, and Prince Lobel Tye LLP\non brief for appellees Shields Pharmacy, LLC, and Shields Pharmacy\nEquity, LLC.\n David C. Casey, Stephen T. Melnick, and Littler Mendelson PC\non brief for appellees UMass Memorial Shields Pharmacy, LLC, and\nShields Specialty Pharmacy Holdings, LLC.\n\nJanuary 15, 2019\n\n LIPEZ, Circuit Judge. In alleged violation of the False\n\nClaims Act, appellant Thomas Guilfoile claims he was fired from\n\nhis job in retaliation for accusing his employer of violating the\n\nAnti-Kickback Statute and making false representations in customer\n\ncontracts. See 31 U.S.C. § 3730(h); 42 U.S.C. § 1320a-7b(b). The\n\ndistrict court dismissed his complaint on the ground that Guilfoile\n\ndid not allege sufficient facts to show he was engaged in protected\n\nconduct within the meaning of the retaliation provision of the\n\nFalse Claims Act. After careful review of the complaint and the\n\nlaw, we affirm as to the contractual language claim but vacate and\n\nremand as to the claim involving the Anti-Kickback Statute.\n\n I.\n\nA. Factual Background\n\n Because this appeal follows the grant of a motion to\n\ndismiss pursuant to Federal Rule of Civil Procedure 12(b)(6), we\n\nrecite the facts as alleged in the amended complaint. See\n\nDavis v. Coakley, 802 F.3d 128, 130 (1st Cir. 2015). We include\n\nonly those facts relevant to the issues on appeal.\n\n Appellant Guilfoile is a seasoned management\n\nprofessional with 30 years of finance and operations experience.\n\nAppellee John Shields, Guilfoile's employer during the period\n\nrelevant to this case, is the CEO of a collection of health care\n\nLLCs, joint ventures, and holding companies that operate in concert\n\nas a single integrated entity (the \"Integrated Entity\"). The\n\n\n - 3 -\n\ncomponent businesses of the Integrated Entity include appellees\n\nShields Pharmacy, LLC; UMass Memorial Shields Pharmacy, LLC;\n\nShields Pharmacy Equity, LLC; and Shields Specialty Pharmacy\n\nHoldings, LLC.1\n\n The Integrated Entity partners with hospitals to provide\n\nspecialty pharmacy services for chronically ill patients by either\n\noperating a pharmacy directly in the hospital or by filling\n\nspecialty prescriptions through an off-site location. The\n\nIntegrated Entity processes the prescriptions, bills the patient's\n\ninsurance, provides patients with financial advice, and follows up\n\nwith patients to ensure their adherence to complex medication\n\nregimens. The Integrated Entity regularly bills federal insurance\n\nprograms, including Medicaid and Medicare, for the services it\n\nprovides to patients covered by those programs. As a secondary\n\nline of business, the Integrated Entity also runs home infusion\n\nand high-risk care management programs.\n\n After years of providing free business advice to his\n\nlong-time friend and neighbor Shields, Guilfoile began to consult\n\nfor the Integrated Entity in April 2013 and officially joined the\n\nIntegrated Entity full-time as president in August of that year.\n\n\n 1 All four component corporations are closely-held\ncorporations with a shared principal place of business at an office\nin Quincy, Massachusetts. Two of the corporations are incorporated\nin Massachusetts and two are incorporated in Delaware. Shields is\nthe sole manager registered with the Secretary of the Commonwealth\nof Massachusetts for all four corporations.\n\n\n - 4 -\n\nGuilfoile's employment contract included terms governing salary,\n\nbonuses, an equity stake in the Integrated Entity's joint ventures,\n\nan equity vesting schedule, and protocols in the event of\n\ntermination. Shields was Guilfoile's immediate supervisor. The\n\ncomplaint alleges that during Guilfoile's tenure, Shields\n\nSpecialty Pharmacy Holdings and UMass Memorial Shields Pharmacy\n\nhad boards of directors composed of Shields, Guilfoile, and the\n\nsame two other individuals.2\n\n Under Guilfoile's leadership, the Integrated Entity grew\n\nfrom a start-up to a successful operation generating millions of\n\ndollars in profit. The Integrated Entity enjoyed overwhelmingly\n\npositive feedback from patients, providers, and employees, and\n\nGuilfoile's leadership was appreciated by Shields and the\n\nIntegrated Entity.\n\n However, in the fall of 2015, Guilfoile became concerned\n\nthat the Integrated Entity was violating the law. At that time,\n\nhe learned that Shields had previously entered into a contract on\n\nbehalf of the Integrated Entity with Michael Greene,3 Shields's\n\nlong-time friend and a consultant whom several New Jersey hospitals\n\n\n 2 The complaint does not shed much further light on the\nIntegrated Entity's management structure. For ease of reference,\nwe join the parties and refer to the two boards of directors\nidentified in the complaint as \"the Board.\"\n\n 3 The pleadings, briefs, and the district court's order\nsometimes spell the consultant's surname as \"Green,\" but we follow\nthe spelling suggested by appellant and supported by the record.\n\n\n - 5 -\n\npaid for financial advice. The contract obligated the Integrated\n\nEntity to, among other things, pay Greene's consulting firm, the\n\nAyrault Group, $35,000 per quarter for each hospital contract that\n\nGreene successfully referred to the Integrated Entity,\n\nspecifically targeting two hospitals that Greene was working for\n\nas a paid consultant: Newark Beth Israel Medical Center (\"NBIMC\")\n\nand University Hospital (\"University\"). The Integrated Entity,\n\nwith assistance from Greene, eventually entered into contracts for\n\nspecialty pharmacy services with both NBIMC and University, and\n\nthe Integrated Entity paid Greene \"referral fees.\" Guilfoile\n\nbelieved that these payments \"had improperly induced [Greene] to\n\nsteer [the] hospital contracts to the Integrated Entity.\"\n\n Guilfoile conferred with the Integrated Entity's\n\ncounsel, who agreed that Guilfoile had valid concerns about the\n\ncontract with Greene. Guilfoile notified Shields that he believed\n\nthe contract violated the federal Anti-Kickback Statute because\n\nthe Integrated Entity had paid Greene to secure contracts with\n\nhospitals that would result in the Integrated Entity making claims\n\nfor payment to federal insurance programs. Such payments are\n\nprohibited by the statute, as explained in greater detail below.\n\nGuilfoile was especially concerned about the implications of the\n\nkickback scheme for the contract with University, which he believed\n\nwas government owned.\n\n\n\n\n - 6 -\n\n At Guilfoile's insistence, Shields ultimately approached\n\nGreene to discuss voiding Greene's contract with the Integrated\n\nEntity and obtaining refunds of any payments to the Ayrault Group.\n\nAfter an apparent negotiation, Shields revealed to Guilfoile that\n\nGreene agreed to waive payments yet to be made for the University\n\nreferral but refused to return the money that the Integrated Entity\n\nhad already paid for the NBIMC referral. Guilfoile believed that\n\nby letting the NBIMC payment stand, the Integrated Entity still\n\nmay have violated the Anti-Kickback Statute. He therefore urged\n\nShields to reveal the matter to the Board and offered to make the\n\ndisclosure jointly. Shields refused.\n\n In December 2015, Guilfoile learned that the contracts\n\nthe Integrated Entity had used to form partnerships with hospitals\n\ncontained a false representation that the Integrated Entity\n\nmaintained \"a fully staffed 24/7 [c]all [c]enter in Quincy,\n\nMassachusetts.\" The Integrated Entity at the time did not have\n\nsuch a center.4 Guilfoile believed that making false\n\nrepresentations to government-owned hospitals, like University,\n\nabout medication management services for chronically ill patients\n\nwith serious medical conditions was contract fraud and posed a\n\nserious threat to public health and safety.\n\n\n 4 The complaint is unclear as to whether the Integrated\nEntity operated a call center that did not conform with the\ndescription in the contracts, or if the Integrated Entity did not\noperate a call center at all.\n\n\n - 7 -\n\n Despite Guilfoile's insistence that the Integrated\n\nEntity either amend the contracts to remove the representation or\n\ncreate a fully-staffed 24/7 call center, Shields refused to take\n\naction or notify the Board. Instead, Shields suggested that the\n\nIntegrated Entity should address the issue only if a customer\n\ncomplained about the breach. In an effort to bring the Integrated\n\nEntity into compliance with the contractual language, Guilfoile\n\nalerted the Human Resources department and the Director of\n\nOperations that they should prepare to hire enough staff to operate\n\na 24/7 call center.\n\n On December 22, 2015, Shields asked Guilfoile to come\n\nto his home office, where Shields expressed his concern about\n\nGuilfoile \"going over his head\" and \"airing his dirty laundry\" to\n\nthe Board. Shields told Guilfoile that he viewed the Board as a\n\n\"third rail\" -- i.e., an entity that should be approached with\n\ncaution -- to which Guilfoile was getting too close. Shields also\n\nexplained that he felt he \"had to protect his interests and his\n\nfamily\" and that he could not risk a vote by the Board against\n\nhim. After Guilfoile rejected Shields's suggestion that the two\n\nof them consider \"parting ways,\" the meeting ended without a\n\nconcrete resolution. Shields stated that he would give the matter\n\nadditional thought.\n\n A week later, on December 28, Shields terminated\n\nGuilfoile's employment in a phone call without further\n\n\n - 8 -\n\nexplanation. The following day, Shields emailed Guilfoile to\n\nconfirm that his employment was terminated. Shields did not\n\nprovide any reason for the termination and did not refer to\n\nGuilfoile's performance or possible misconduct as a basis for the\n\ntermination. Guilfoile then received a written notice stating\n\nthat his termination was retroactive to December 22. The letter\n\ndid not state that he was being terminated for cause.\n\n After his termination, Guilfoile notified the Board that\n\nShields had terminated him because he feared that Guilfoile would\n\nreport the suspected violations of law to the Board. Guilfoile\n\nsubsequently forwarded a letter to the Board memorializing his\n\nconcerns. Following these disclosures, Shields made repeated\n\nthreats to file suit against Guilfoile for defamation and tortious\n\ninterference, which he in fact subsequently did. On February 26,\n\n2016, Guilfoile received a letter from the Integrated Entity\n\ndiscussing its purported right to repurchase Guilfoile's vested\n\nequity for a total of $15. The letter stated, for the first time,\n\nthat Guilfoile had been \"terminated for cause.\"\n\nB. Procedural Background\n\n On April 1, 2016, Guilfoile filed this action against\n\nthe Integrated Entity and Shields alleging \"whistleblower\n\nretaliation\" in violation of the False Claims Act and a variety of\n\nstate law employment, wage, contract, and tort claims. In the\n\noperative amended complaint (\"the complaint\"), filed after\n\n\n - 9 -\n\ndefendants filed motions to dismiss, Guilfoile alleges that the\n\nIntegrated Entity retaliated against him for his \"efforts to stop\n\nviolations of the [False Claims Act],\" specifically his\n\n\"disclosures . . . related to the kickbacks [the Integrated Entity]\n\npaid Mr. Green[e] in exchange for referrals of federally insured\n\npatients, and disclosures related to contracts the Integrated\n\nEntity entered into with government-owned hospitals even though\n\nthe Integrated Entity knew the contracts included fraudulent\n\nterms.\"\n\n Regarding the payments to the Ayrault Group, the\n\ncomplaint alleges that Guilfoile reasonably believed the payments\n\nto be \"violations of the [Anti-Kickback Statute], a per se\n\nviolation of the [False Claims Act], resulting in the submission\n\nof fraudulent claims to the government,\" and that \"[t]he Integrated\n\nEntity violated the [Anti-Kickback Statute] and the [False Claims\n\nAct] by willfully paying remuneration to induce a person [Greene]\n\nto refer patients for the furnishing of a service for which the\n\nIntegrated Entity knew payment would be made under federal health\n\ncare programs.\" Finally, the complaint alleges that the Integrated\n\nEntity retaliated against Guilfoile by terminating his employment,\n\n\"threatening to sue him, fabricating an after-the-fact contention\n\nas to 'cause,' attempting to repurchase his equity for the amount\n\n\n\n\n - 10 -\n\nof $15, and then making good on their threat to sue him after he\n\ninstituted this law suit.\"5\n\n Following oral argument on defendants' motions to\n\ndismiss, Guilfoile requested leave to file a memorandum \"in\n\nresponse to legal authority and factual allegations that\n\n[d]efendants raised for the first time during oral argument.\" The\n\nlast sentence of the brief accompanying the request stated, \"If\n\nthis [c]ourt determines . . . that the present [a]mended\n\n[c]omplaint does not adequately plead a cause of action under the\n\nanti-retaliation provision of the [False Claims Act], plaintiff\n\nrespectfully requests that the [c]ourt allow him the opportunity\n\nto file a second amended complaint alleging additional facts, like\n\nthose set forth in this memorandum and supporting affidavit.\"\n\nGuilfoile's \"supporting affidavit\" alleged additional facts\n\nconcerning the Integrated Entity's business, Greene's role in\n\nrecommending the Integrated Entity to the hospitals for the\n\nprovision of pharmacy services, and the nature of the 24/7 call\n\ncenter service.\n\n In granting the motions to dismiss, the district court\n\ndetermined that Guilfoile had failed to adequately plead that he\n\nwas engaged in protected conduct, the first element of a False\n\n\n 5The complaint alleges that \"four days after Mr. Guilfoile\ninitiated this action in federal court . . . Mr. Shields filed\nsuit against [him] in state court, bringing claims for defamation\nand tortious interference.\"\n\n\n - 11 -\n\nClaims Act retaliation claim. The court therefore dismissed the\n\nretaliation count without analyzing the other elements of the\n\nclaim. The court then declined to exercise supplemental\n\njurisdiction over the state law claims and dismissed them without\n\nprejudice. In a footnote, the court granted in part and denied in\n\npart Guilfoile's request to provide a response to defendants'\n\npurportedly new theories and factual allegations presented at oral\n\nargument. The court stated that it had considered his briefing as\n\nto the legal authority first raised at oral argument, but had not\n\nconsidered factual assertions outside the complaint, presumably\n\nincluding the factual assertions in the \"supporting affidavit.\"\n\nThe court did not respond to Guilfoile's suggestion in his motion\n\nthat he be allowed to file a second amended complaint if the court\n\nfound the operative complaint lacking.\n\n Guilfoile subsequently filed a \"Motion to Vacate\n\nJudgment and For Leave to Amend the Complaint\" pursuant to Federal\n\nRules of Civil Procedure 59(e) and 15(a). After the district court\n\ndenied the motion, Guilfoile timely appealed both the dismissal of\n\nhis complaint and the denial of his post-judgment motion.\n\n II.\n\nA. Standard of Review\n\n We review de novo a district court's grant of a motion\n\nto dismiss pursuant to Federal Rule of Civil Procedure 12(b)(6).\n\nHaley v. City of Boston, 657 F.3d 39, 46 (1st Cir. 2011). We must\n\n\n - 12 -\n\nevaluate whether the complaint adequately pleads facts that \"state\n\na claim to relief that is plausible on its face.\" Bell Atl. Corp.\n\nv. Twombly, 550 U.S. 544, 570 (2007). In performing this\n\nevaluation, we \"assume the truth of all well-pleaded facts and\n\ngive the plaintiff the benefit of all reasonable inferences\n\ntherefrom.\" Thomas v. Rhode Island, 542 F.3d 944, 948 (1st Cir.\n\n2008). However, we do not \"draw unreasonable inferences or credit\n\nbald assertions [or] empty conclusions.\" Theriault v. Genesis\n\nHealthCare LLC, 890 F.3d 342, 348 (1st Cir. 2018) (alteration in\n\noriginal) (internal quotation marks omitted). A suit is properly\n\ndismissed \"if the complaint does not set forth factual allegations,\n\neither direct or inferential, respecting each material element\n\nnecessary to sustain recovery under some actionable legal theory.\"\n\nU.S. ex rel. Hutcheson v. Blackstone Med., Inc., 647 F.3d 377, 384\n\n(1st Cir. 2011) (emphasis added) (internal quotation marks\n\nomitted). Before reviewing the sufficiency of the complaint under\n\nthis standard, we provide a brief overview of the pertinent\n\nstatutes.\n\nB. False Claims Act\n\n The False Claims Act (\"FCA\"), 31 U.S.C. §§ 3729-3733,\n\nprohibits, in relevant part, any person from \"knowingly\n\npresent[ing], or caus[ing] to be presented, a false or fraudulent\n\nclaim\" to the federal government. 31 U.S.C. § 3729(a)(1)(A)\n\n(emphasis added); see Universal Health Servs., Inc. v. United\n\n\n - 13 -\n\nStates ex rel. Escobar, 136 S. Ct. 1989, 1996 (2016) (explaining\n\nthat the FCA is focused \"on those who present or directly induce\n\nthe submission of false or fraudulent claims\").6 For purposes of\n\nthe statute, \"a 'claim' . . . includes direct requests to the\n\n[g]overnment for payment as well as reimbursement requests made to\n\nthe recipients of federal funds under federal benefit programs.\"\n\nEscobar, 136 S. Ct. at 1996 (citing 31 U.S.C. § 3729(b)(2)(A)).\n\nThe FCA includes a scienter requirement that the false claim be\n\nsubmitted \"knowingly.\" 31 U.S.C. § 3729(a)(1), (b)(1). A \"non-\n\nsubmitting\" entity that knowingly causes the submission of a false\n\nclaim may be liable under the FCA even if the entity directly\n\nsubmitting the claim to the government lacks the requisite mental\n\nstate. See Hutcheson, 647 F.3d at 389-90.\n\n The FCA is also \"subject to a judicially-imposed\n\nrequirement that the allegedly false claim . . . be material.\"\n\nUnited States ex rel. Loughren v. Unum Grp., 613 F.3d 300, 307\n\n(1st Cir. 2010).7 The falsity of a claim is \"material\" if it has\n\n\n\n 6 The FCA does not define \"false or fraudulent.\" However,\nthe Supreme Court has held that the phrase encompasses\n\"misrepresentations by omission\" in addition to \"express\nfalsehoods.\" Escobar, 136 S. Ct. at 1999.\n 7 The FCA defines and uses \"material.\" See 31 U.S.C.\n§ 3729(a)(1)(B), (G), (b)(4). However, § 3729(a)(1)(A), which\nprohibits the knowing submission of false claims, does not contain\nthe term. We have therefore described the \"materiality\"\nrequirement in regard to § 3729(a)(1)(A) as judicially created\nbecause it derives from a general reading of materiality into all\nsections of the FCA rather than from the statutory language. See\n\n\n - 14 -\n\n\"a natural tendency to influence or was capable of influencing the\n\n[government]'s decision\" whether to pay or reimburse the claim.\n\nId. The Supreme Court has emphasized that the FCA's \"materiality\n\nstandard is demanding,\" and a plaintiff directly alleging the\n\nsubmission of a false claim8 must plead facts to support\n\nallegations of materiality with \"plausibility and particularity.\"\n\nEscobar, 136 S. Ct. at 2003, 2004 n.6. Whether an express or\n\nimplied false representation of compliance with statutes or\n\nregulations is \"material\" is ordinarily \"a fact-intensive and\n\ncontext-specific inquiry.\" New York v. Amgen Inc., 652 F.3d 103,\n\n111 (1st Cir. 2011).\n\n In addition to prohibiting the submission of false\n\nclaims, the FCA bars an employer from retaliating against an\n\nemployee \"because of lawful acts done . . . in furtherance of an\n\naction under this section or other efforts to stop 1 or more\n\nviolations of [the FCA].\" 31 U.S.C. § 3730(h)(1). To prevail on\n\nan FCA retaliation claim, \"a plaintiff must show that 1) the\n\nemployee's conduct was protected under the FCA; 2) the employer\n\n\n\nHutcheson, 647 F.3d at 388 n.13. Indeed, the Supreme Court has\ndeclined to decide \"whether § 3729(a)(1)(A)'s materiality\nrequirement is governed by § 3729(b)(4) [the statutory definition\nof \"materiality\"] or derived directly from the common law.\"\nEscobar, 136 S. Ct. at 2002.\n\n 8 The False Claims Act's \"qui tam\" provisions authorize\nprivate individuals, known as \"relators,\" to bring suit on the\ngovernment's behalf based on the submission of false claims to the\ngovernment. See 31 U.S.C. § 3730(b).\n\n\n - 15 -\n\nknew that the employee was engaged in such conduct; and 3) the\n\nemployer discharged or discriminated against the employee because\n\nof his or her protected conduct.\" United States ex rel. Karvelas\n\nv. Melrose-Wakefield Hosp., 360 F.3d 220, 235 (1st Cir. 2004),\n\nabrogated on other grounds by Allison Engine Co., Inc. v. United\n\nStates ex rel. Sanders, 553 U.S. 662 (2008). In general, \"proving\n\na violation of § 3729 [the false claims provision] is not an\n\nelement of a § 3730(h) [retaliation] cause of action.\" Graham\n\nCty. Soil & Water Conservation Dist. v. United States ex rel.\n\nWilson, 545 U.S. 409, 416 n.1 (2005).\n\n The pleading standards for actions directly alleging the\n\nsubmission of false claims, such as qui tam actions pursuant to 31\n\nU.S.C. § 3730(b), and the pleading standards for actions alleging\n\nretaliation, differ in crucial ways. In a suit directly alleging\n\nthe submission of a false claim, a plaintiff must sufficiently\n\nplead facts supporting the existence of an actual false claim.\n\nSee Karvelas, 360 F.3d at 225 (\"Evidence of an actual false claim\n\nis the sine qua non of a False Claims Act violation.\" (internal\n\nquotation marks omitted)). However, in a suit alleging retaliation\n\nunder the FCA, a plaintiff must sufficiently plead that he or she\n\nwas retaliated against based on \"conduct that reasonably could\n\nlead to a viable FCA action.\" Id. at 236. We have further\n\nexplained that \"conduct protected under\" the FCA retaliation\n\nprovision encompasses an employee's \"investigations, inquiries,\n\n\n - 16 -\n\ntestimonies or other activities that concern the employer's\n\nknowing submission of false or fraudulent claims for payment to\n\nthe government.\" United States ex rel. Booker v. Pfizer, Inc.,\n\n847 F.3d 52, 59 (1st Cir. 2017) (quoting Karvelas, 360 F.3d at\n\n237).9 This standard is consistent with the legislative intent\n\nthat \"[p]rotected activity [for purposes of an FCA retaliation\n\nclaim] should . . . be interpreted broadly.\" Karvelas, 360 F.3d\n\nat 236 (quoting S. Rep. No. 99–345, at 34 (1986), reprinted in\n\n1986 U.S.C.C.A.N. 5266, 5299). Because an FCA retaliation claim\n\n\"does not require a showing of fraud,\" a plaintiff alleging\n\nretaliation \"need not meet the heightened pleading requirements of\n\n[Federal Rule of Civil Procedure] 9(b).\" Id. at 238 n.23.10\n\n\n\n\n 9 We derived the \"reasonably could lead\" standard from the\nstatutory language prohibiting retaliation by an employer \"because\nof lawful acts done by the employee . . . in furtherance of an\n[FCA] action.\" See Karvelas, 360 F.3d at 235-36 (quoting 31 U.S.C.\n§ 3730(h)(1)). Therefore, a court must consider whether the\nconduct of the employee who was allegedly retaliated against --\nthat is, the employee's whistleblowing or investigative activities\n-- reasonably could lead to an FCA action. Of course, the question\nof whether the employer engaged in conduct that could run afoul of\nthe FCA is a necessary component of this inquiry. After all, the\nemployee's conduct must \"concern the employer's knowing submission\nof false . . . claims . . . because only such conduct reasonably\ncould lead to an FCA action.\" Booker, 847 F.3d at 59-60 (internal\nquotation marks omitted).\n\n 10 Conversely, because a direct FCA claim does require a\nshowing of fraud, a qui tam plaintiff must \"meet the Rule 9(b)\npleading standards.\" Karvelas, 360 F.3d at 238.\n\n\n - 17 -\n\nC. Anti-Kickback Statute\n\n The Anti-Kickback Statute (\"AKS\") criminalizes, in\n\nrelevant part, the \"knowing[] and willful[]\" offer or payment of\n\n\"any remuneration (including any kickback, bribe, or rebate)\" to\n\ninduce a person to \"recommend . . . ordering any . . . service\n\n. . . for which payment may be made in whole or in part under a\n\n[f]ederal health care program.\" 42 U.S.C. § 1320a-7b(b)(2)(B).\n\nRelevant considerations for identifying an unlawful kickback\n\ninclude: (1) whether the person being paid the alleged kickback is\n\n\"in a position to generate [f]ederal health care program business\"\n\nand (2) whether at least one purpose of the payment could be \"to\n\ninduce or reward the referral or recommendation of business payable\n\nin whole or in part by a [f]ederal health care program.\" OIG\n\nSupplemental Compliance Program Guidance for Hospitals, 70 Fed.\n\nReg. 4858, 4864 (Jan. 31, 2005). Essentially, the AKS targets any\n\nremunerative scheme through which a person is \"paid 'in return\n\nfor' referrals\" to a program under which payments may be made from\n\nfederal funds. United States v. Patel, 778 F.3d 607, 618 (7th\n\nCir. 2015) (quoting 42 U.S.C. § 1320a-7b(b)(1)(A)).\n\nIn 2010, the AKS was amended to create an express link to the FCA.\n\nThe AKS now provides that \"a claim that includes items or services\n\nresulting from a violation of this section constitutes a false or\n\nfraudulent claim for purposes of [the FCA].\" 42 U.S.C.\n\n\n\n\n - 18 -\n\n§ 1320a-7b(g), as amended by the Patient Protection and Affordable\n\nCare Act, Pub. L. No. 1110148, 124 Stat. 119 (2010).\n\n III.\n\n Appellant contends that he was retaliated against within\n\nthe meaning of the FCA anti-retaliation provision when he was fired\n\nafter raising concerns to Shields and others about (1) the alleged\n\nkickbacks to Greene and (2) the contractual misrepresentations\n\nregarding a 24/7 call center. Although appellees attack the\n\nsufficiency of the complaint on several grounds, the district court\n\ndismissed the FCA claims on the basis that Guilfoile had not\n\nplausibly pleaded that he had engaged in protected conduct. Our\n\nanalysis begins with this first element of an FCA retaliation\n\nclaim.\n\nA. Payments to Greene/Ayrault Group\n\n The district court concluded that Guilfoile had failed\n\nto adequately plead that his actions in raising concerns about the\n\npayments to Greene and the Ayrault Group reasonably could have led\n\nto an FCA action. Specifically, the district court reasoned that\n\nGuilfoile failed to adequately plead an AKS violation, and that\n\neven if he had adequately pleaded an AKS violation, he failed to\n\nconnect any such violation to a potential false claim within the\n\nmeaning of the FCA. We disagree with the district court's approach\n\nand its conclusion.\n\n\n\n\n - 19 -\n\n Guilfoile has brought an FCA retaliation claim, not a\n\n\"direct\" claim of an FCA violation. As discussed above, adequately\n\npleading an FCA retaliation claim does not require adequately\n\npleading the submission of a false claim or meeting the Rule 9(b)\n\nstandards for pleading fraud. See Graham Cty., 545 U.S. at 416 &\n\nn.1; Karvelas, 360 F.3d at 238 n.23; see also United States ex\n\nrel. Grenadyor v. Ukrainian Vill. Pharmacy, Inc., 772 F.3d 1102,\n\n1108-09 (7th Cir. 2014) (affirming dismissal of qui tam claim for\n\nfailure to plead kickbacks with particularity but reversing\n\ndismissal of retaliation claim based on internal reporting of\n\nalleged kickbacks). Rather, plaintiffs like Guilfoile need only\n\nplead that their actions in reporting or raising concerns about\n\ntheir employer's conduct \"reasonably could lead to an FCA action.\"\n\nBooker, 847 F.3d at 59 (internal quotation marks omitted). Put\n\ncolloquially, rather than plausibly pleading the existence of a\n\nfire -- the actual submission of a false claim -- a plaintiff\n\nalleging FCA retaliation need only plausibly plead a reasonable\n\namount of smoke -- conduct that could reasonably lead to an FCA\n\naction based on the submission of a false claim.\n\n Because this case involves an alleged violation of the\n\nAKS, we consider the 2010 amendment to the AKS stating that \"a\n\nclaim that includes items or services resulting from a violation\n\nof this section constitutes a false or fraudulent claim for\n\npurposes of [the FCA.]\" 42 U.S.C. § 1320a-7b(g). We have\n\n\n - 20 -\n\npreviously declined to directly address the impact of\n\n§ 1320a-7b(g) on FCA actions, see Hutcheson, 647 F.3d at 379 n.1,\n\nand we do not attempt to assess the full implications of the AKS\n\nprovision today. We need not do so because the issue before us is\n\nnot the standard for proving an FCA violation based on the AKS,\n\nbut rather the requirements for pleading an FCA retaliation claim.\n\nFor our present purposes, it is enough to say that in light of\n\n§ 1320a-7b(g), \"[a]n AKS violation that results in a federal health\n\ncare payment is a per se false claim under the FCA.\" United States\n\nex rel. Lutz v. United States, 853 F.3d 131, 135 (4th Cir. 2017).\n\nThat is, drawing on the \"resulting from\" language of the 2010\n\namendment, if there is a sufficient causal connection between an\n\nAKS violation and a claim submitted to the federal government,\n\nthat claim is false within the meaning of the FCA. See United\n\nStates ex rel. Greenfield v. Medco Health Sols., Inc., 880 F.3d\n\n89, 96-98 (3d Cir. 2018) (discussing causal connection issue);11\n\nUnited States ex rel. Bawduniak v. Biogen Idec, Inc., No. 12-CV-\n\n10601-IT, 2018 WL 1996829, at *5-6 (D. Mass. Apr. 27, 2018) (same).\n\n We further read the AKS amendment as obviating the need\n\nfor a plaintiff to plead materiality -- that is, to plead that\n\n\n\n\n 11 We note that Greenfield involved a qui tam suit directly\nalleging an FCA claim based on a violation of the AKS and\nultimately turned on the standard for proving such claims at\nsummary judgment. See Greenfield, 880 F.3d at 98.\n\n\n - 21 -\n\ncompliance with the AKS was material to the government's decision\n\nto pay any specific claim. This construction inescapably follows\n\nfrom the statute's plain language stating that a claim resulting\n\nfrom a violation of the AKS \"constitutes a false or fraudulent\n\nclaim.\" 42 U.S.C. § 1320a-7b(g). The statute's use of the term\n\n\"constitutes\" would be meaningless if courts had to engage in a\n\nmateriality analysis -- for example, by inquiring into whether the\n\nentity submitting the claim had certified its compliance with the\n\nAKS -- after establishing that a claim resulted from an AKS\n\nviolation. See, e.g., United States v. Catholic Health\n\nInitiatives, 312 F. Supp. 3d 584, 594 (S.D. Tex. 2018) (\"Due to\n\n[§ 1320a–7b(g)], liability under the FCA for AKS violations does\n\nnot require the defendants to have expressly certified their\n\ncompliance with the AKS.\"); United States ex rel. Kester v.\n\nNovartis Pharm. Corp., 43 F. Supp. 3d 332, 364 (S.D.N.Y. 2014)\n\n(stating that \"from and after [the AKS amendment,] the act of\n\nsubmitting a claim . . . itself implie[d] compliance with the AKS,\n\neven in [the] absence of any express certification of compliance.\"\n\n(second alteration in original) (internal quotation marks and\n\ncitation omitted)).\n\n Our reading of § 1320a-7b(g) is consistent with the\n\nlegislative history, which indicates Congress's intent to \"ensure\n\nthat all claims resulting from illegal kickbacks are 'false and\n\nfraudulent'\" and to \"strengthen [] whistleblower actions based on\n\n\n - 22 -\n\nmedical care kickbacks . . . [b]y making all claims that stem from\n\nan illegal kickback subject to the False Claims Act.\" 155 Cong.\n\nRec. S10852-01, S10853 (daily ed. Oct. 28, 2009) (statement of\n\nSen. Kaufman). If a plaintiff must plead and prove that compliance\n\nwith the AKS was \"material\" to a claim \"resulting from\" an AKS\n\nviolation, § 1320a-7b(g) would not represent the strengthening of\n\nwhistleblower actions that Congress intended. Moreover,\n\n§ 1320a-7b(g)'s obviation of the \"materiality\" inquiry essentially\n\ncodifies the long-standing view that AKS violations are \"material\"\n\nin the FCA context.12 This codification has the benefit, however,\n\nof bypassing judicially created theories of materiality, such as\n\nexpress or implied certification, that \"do more to obscure than\n\n\n 12 Prior to the 2010 AKS amendment, courts had consistently\nheld that compliance with the AKS (or the lack thereof) was\n\"material\" to the government's decision to pay a given claim based\non the theory that the government's payment was contingent on the\nsubmitting entity's express or implied certification that it had\ncomplied with the AKS. See, e.g., Amgen, 652 F.3d at 110; United\nStates ex rel. Wilkins v. United Health Grp., Inc., 659 F.3d 295,\n314 (3rd Cir. 2011), abrogated on other grounds by Escobar, 136 S.\nCt. 1989; United States v. Rogan, 517 F.3d 449, 452-53 (7th Cir.\n2008); United States ex rel. Westmoreland v. Amgen, Inc., 812 F.\nSupp. 2d 39, 52 (D. Mass. 2011); United States ex rel. Lisitza v.\nJohnson & Johnson, 765 F. Supp. 2d 112, 127-28 (D. Mass. 2011)\n(citing cases). The legislative history suggests that the 2010\namendment was intended to codify the link between AKS violations\nand false claims within the meaning of the FCA as well as to\ncorrect one district court case holding that claims for payment\nresulting from AKS violations could be \"laundered\" if the claims\nwere submitted to the government by a party who was unaware that\na kickback had occurred. See 155 Cong. Rec. S10852-01, S10853-54\n(daily ed. Oct. 28, 2009) (statements of Sens. Kaufman and Leahy);\nKester, 41 F. Supp. 3d at 332-35 (discussing the 2010 amendment's\nlegislative history).\n\n\n - 23 -\n\nclarify the issues before\" a court considering an FCA claim.\n\nHutcheson, 647 F.3d at 385–86.\n\n With this understanding of the AKS amendment in mind, we\n\nconsider whether Guilfoile has plausibly pleaded that the concerns\n\nhe raised about the payments to Greene reasonably could have led\n\nto an FCA action. The allegations in the complaint, coupled with\n\nthe reasonable inferences we must draw from them, plausibly pleaded\n\nthat claims for payment were, or were going to be, submitted to\n\nthe government in connection with the Integrated Entity's work\n\nwith the New Jersey hospitals. Specifically, the complaint alleges\n\nthat the Integrated Entity \"regularly bills federal insurance\n\nprograms[,] including[] Medicaid [and] Medicare,\" and that\n\nGuilfoile \"believed the contract with Mr. Green[e] violated the\n\nfederal AKS because the Integrated Entity had paid illegal\n\nkickbacks to secure a contract at hospitals where it billed to\n\nfederal insurance programs.\" (Emphasis added.) These allegations\n\nsupport the reasonable inference that the government was being\n\nbilled for services provided by the Integrated Entity in connection\n\nwith its contracts with the hospitals.\n\n Guilfoile has also plausibly alleged a sufficient causal\n\nconnection between any submitted claims and the payments to Greene.\n\nSpecifically, the complaint alleges that the Integrated Entity\n\nentered into an agreement to pay Greene\n\n\"for each hospital contract that [he] successfully referred to the\n\n\n - 24 -\n\nIntegrated Entity, specifically targeting two hospitals that [he]\n\nwas working for as a paid consultant\"; that the Integrated Entity\n\nentered into contracts with those two hospitals; and that the\n\nIntegrated Entity in fact paid him \"referral fees.\" The allegation\n\nthat Greene was paid pursuant to the agreement supports the\n\nreasonable inference that Greene was responsible for connecting\n\nthe Integrated Entity with the New Jersey hospitals. In other\n\nwords, we reasonably infer from the complaint's allegations that\n\nthe Integrated Entity paid Greene to induce him to use his position\n\nwith the hospitals to influence them to select the Integrated\n\nEntity for the contracts at issue. Further, the complaint permits\n\nthe reasonable inference that, if not for the agreement with\n\nGreene, the Integrated Entity would not have been in a position to\n\nbenefit from federal health care payments arising from its work\n\nwith the hospitals. See supra 5-6.13\n\n Finally, Guilfoile has plausibly alleged that the\n\npayments to Greene were a violation of the AKS. The relationship\n\nbetween the Integrated Entity and Greene -- payment to induce the\n\n\n 13 In addition to the allegation that Greene was paid for\nreferring the hospitals to the Integrated Entity, the complaint\nalleges that Greene advised the Integrated Entity on how to bid\nfor the hospital contracts. Contrary to the suggestion by\nappellees, and drawing all reasonable inferences in Guilfoile's\nfavor, we simply do not read the complaint to allege that the\nextent of Greene's assistance to the Integrated Entity was\nproviding insider information about the hospitals' bidding\nprocess.\n\n\n\n - 25 -\n\ngeneration of federal health care program business -- has the\n\nhallmarks of a kickback scheme. See 42 U.S.C. § 1320a-7b(b)(2)(B)\n\n(criminalizing payments to \"induce [a] person . . . to . . .\n\nrecommend purchasing, leasing, or ordering any good, facility,\n\nservice, or item for which payment may be made in whole or in part\n\nunder a [f]ederal health care program\"). Importantly, the nature\n\nof the alleged scheme is materially indistinguishable from the\n\nscheme in United States v. Bay State Ambulance & Hospital Rental\n\nService, Inc., 874 F.2d 20 (1st Cir. 1989), which involved a\n\ncriminal conviction under the AKS. In Bay State, a hospital\n\nemployee, who was on an advisory committee charged with advising\n\nthe hospital on accepting bids for an ambulance services contract,\n\nwas paid by an ambulance company to induce him to recommend that\n\nthe hospital enter into a contract for ambulance services with\n\nthat company. See 874 F.2d at 22. There was no allegation that\n\nthe hospital employee was paid to refer individual patients for\n\nindividual ambulance trips or that the federal government would\n\npay the hospital simply for entering into the contract with the\n\nambulance company, which contract was the direct outcome of the\n\nillegal remuneration scheme. Yet, we held that a crime had\n\noccurred under the AKS once the person who was in a position to\n\ninfluence the hospital was paid to use his influence to win the\n\ncontract for the ambulance company. See id.\n\n\n\n\n - 26 -\n\n The dissent's concern with the \"attenuated\" nature of\n\nthe AKS scheme alleged in the complaint is misplaced.14 First,\n\nalthough we can see how our colleague drew his interpretation from\n\nthe language of the AKS, we are bound by Bay State, as the dissent\n\nrecognizes. Appellees point to no authority for the contention\n\nthat the AKS scheme as pleaded is materially distinguishable from\n\nthe scheme in Bay State and outside the compass of the AKS. The\n\ndissent's attempt to factually distinguish Bay State is also\n\nunconvincing. Any suggestion in the dissent that the nature of\n\nthe kickback scheme is more speculative than the scheme in Bay\n\nState fails to adequately recognize the difference between\n\npleading standards for an FCA retaliation claim, at issue here,\n\nand standards of proof for a criminal conviction under the AKS, at\n\nissue in Bay State. Second, but equally as important, this case\n\ngives us no reason to question Bay State. The type of scheme\n\nproven in Bay State and alleged in the present case is in the\n\nheartland of what the AKS is intended to prevent -- the use of\n\npayments to improperly influence decisions on the provision of\n\n\n 14As our dissenting colleague articulates his concern:\n\"There is . . . a fair amount of attenuation between the actual\ntransactions that Greene was allegedly induced to 'arrange for'\n(the hospitals' 'purchas[es]' or 'order[s]' of the Integrated\nEntity's general pharmacy services) and the transactions 'for\nwhich payment may be made . . . under a Federal health care program'\n(some unknown purchases from an Integrated Entity-run pharmacy of\nsome unknown drugs by some unknown patients who happened to be\neligible for reimbursement under a federal health care program).\"\n\n\n\n - 27 -\n\nhealth care that lead to claims for payment to federal health care\n\nprograms.15 Accepting our colleague's contention -- that there is\n\ntoo great a distance between the Integrated Entity's payments to\n\nGreene to capture the hospital contracts and the submission of\n\nclaims to federal insurance programs, which is the unmistakable\n\nobjective of the contracts -- would leave a hole in the statutory\n\nscheme and essentially permit pay-offs to capture federal health\n\ncare funds. See OIG Supplemental Guidance, 70 Fed. Reg. at 4864\n\n(an illegal kickback is a payment whose purpose, at least in part,\n\nis \"to induce or reward the referral or recommendation of business\n\npayable in whole or in part by a [f]ederal health care program\").\n\n Further, we disagree with our dissenting colleague that\n\nour interpretation of the FCA and the AKS, and our application of\n\nthe statutory language to the alleged facts in light of our\n\nprecedent, is foreclosed by the manner in which Guilfoile presented\n\n\n\n\n 15 We also disagree with the dissent that we should consider\nhere arguments not raised in Bay State that would challenge the\nviability of that decision. Unlike in United States v. DiPina,\n178 F.3d 68, 73 (1st Cir. 1999), where we acknowledged that we are\nnot bound by dicta in a prior opinion, accepting the appellees'\narguments about attenuation in this case would mean that the\nholding in Bay State was incorrect and that the case was therefore\nwrongly decided. The similar facts in Bay State and this case are\nnot \"background facts.\" They are facts that implicate the\napplicability of the AKS in both cases. It is a fundamental\nprinciple that a newly constituted appellate panel cannot overrule\na prior panel in the absence of newly announced Supreme Court law,\nan intervening en banc opinion of this court, a statutory\noverruling, or developments in the law. See Lassend v. United\nStates, 898 F.3d 115, 124-25 & n.6 (1st Cir. 2018).\n\n\n - 28 -\n\nhis arguments before us or before the district court. This is not\n\na case where an appellant has tried to introduce on appeal an issue\n\nthat was never before the district court or to otherwise \"sand\n\nbag\" the other side. Although Guilfoile may not have consistently\n\nraised certain arguments, the core issue of whether the payment\n\nscheme as pleaded falls within the compass of the AKS was before\n\nthe district court and is at the core of his appeal. Before the\n\ndistrict court and before us, Guilfoile consistently argued that\n\nhe has adequately alleged an AKS violation for purposes of pleading\n\nan FCA retaliation claim. The fact that he did not rely on Bay\n\nState or did not consistently present a \"market access\" theory to\n\nsupport the AKS violation in no way precludes us from reaching our\n\nresult. In the context of a de novo review necessitating our\n\ninterpretation of a statute, we routinely employ rationales that\n\nhave been less than satisfactorily presented by the parties if\n\nthat is the correct way of resolving the issue under the applicable\n\nlaw. We cannot allow our responsibility to articulate the most\n\nsensible resolution of an issue, especially, as here, an issue of\n\nstatutory interpretation involving our own precedent, to be\n\nunreasonably circumscribed by the parties' arguments.\n\n Hence, in summary, after drawing all reasonable\n\ninferences in Guilfoile's favor and considering the effect of the\n\nstatutory language drawing a connection between AKS violations and\n\nFCA actions, we conclude Guilfoile has plausibly pleaded that he\n\n\n - 29 -\n\nengaged in protected conduct within the meaning of an FCA\n\nretaliation claim. That is, when Guilfoile raised concerns about\n\nthe payments to Greene he was engaging in conduct that \"reasonably\n\ncould lead to an FCA action,\" Booker, 847 F.3d at 59 (internal\n\nquotation marks omitted), specifically, an FCA action based on the\n\nsubmission of claims resulting from an AKS violation.16\n\n In view of its conclusion that Guilfoile had not\n\nadequately pleaded that he engaged in protected conduct, the\n\ndistrict court did not go on to analyze the other two elements of\n\nGuilfoile's FCA retaliation claim: specifically, that (1) his\n\nemployer knew that he was engaged in protected conduct and (2) his\n\nemployer retaliated against him because of that conduct. See\n\nKarvelas, 360 F.3d at 235. However, we readily conclude that\n\nGuilfoile has plausibly alleged that the Integrated Entity knew\n\nthat he was engaging in protected conduct. Guilfoile specifically\n\n\n\n\n 16 Many of the cases cited by appellees for the proposition\nthat the complaint does not adequately plead an FCA retaliation\nclaim are clearly inapposite because they apply standards for\ndirectly pleading violations of the AKS and FCA, see, e.g., United\nStates ex rel. Kalec v. NuWave Monitoring, LLC, 84 F. Supp. 3d 793\n(N.D. Ill. 2015); standards for proving AKS and FCA claims on\nsummary judgment, see, e.g., United States ex rel. Perales v. St.\nMargaret's Hosp., 243 F. Supp. 2d 843 (C.D. Ill. 2003); standards\nfor assessing criminal conviction under the AKS, see, e.g., Patel,\n778 F.3d 607; or standards for evaluating FCA retaliation claims\nthat we do not follow, see, e.g., United States ex rel. Uhlig v.\nFluor Corp., 839 F.3d 628, 635 (7th Cir. 2016). The case of United\nStates ex rel. Rost v. Pfizer, Inc., 736 F. Supp. 2d 367 (D. Mass.\n2010), predates the 2010 amendment to the AKS and applies an\noutmoded theory of implied certification.\n\n\n - 30 -\n\nalleged that \"he notified Mr. Shields . . . that he believed the\n\ncontract with Mr. Green[e] violated the federal AKS because the\n\nIntegrated Entity had paid illegal kickbacks to secure a contract\n\nat hospitals where it billed federal insurance programs.\"\n\n Guilfoile also has plausibly pleaded that he was\n\nretaliated against because of his protected conduct, given the\n\nclose temporal proximity -- about a week -- of his termination to\n\nhis final conversation with Shields about the payments to Greene.\n\nSee Harrington v. Aggregate Indus. Ne. Region, Inc., 668 F.3d 25,\n\n32 (1st Cir. 2012) (suggesting that a plaintiff can satisfy the\n\nthird element of a prima facie retaliation case by plausibly\n\npleading temporal proximity where the retaliatory action occurred\n\ntwo months after the protected conduct). To the extent appellees\n\ncontend that the complaint does not adequately allege that\n\nGuilfoile informed Shields that he was concerned about fraud on\n\nthe government, see, e.g., McKenzie v. BellSouth Telecomms., Inc.,\n\n219 F.3d 508, 516 (6th Cir. 2000), we disagree. The complaint\n\nexplicitly alleges, for example, that Guilfoile \"notified []\n\nShields . . . that he believed the contract with [] Green[e]\n\nviolated the federal AKS because the Integrated Entity had paid\n\nillegal kickbacks to secure a contract at hospitals where it billed\n\nto federal insurance programs.\"\n\n\n\n\n - 31 -\n\nB. The 24/7 Call Center\n\n We agree with the district court that Guilfoile has not\n\nsufficiently pleaded a connection between the 24/7 call center\n\ncontractual terms and the submission of any claim.17 In general,\n\n\"[i]t is not the case that any breach of contract, or violation of\n\nregulations or law, or receipt of money from the government where\n\none is not entitled to receive the money, automatically gives rise\n\nto a claim under the FCA.\" United States ex rel. Hopper v. Anton,\n\n91 F.3d 1261, 1265 (9th Cir. 1996). Even in the FCA retaliation\n\ncontext, there must be a reasonable connection between the alleged\n\nconduct and the submission of claims within the purview of the\n\nFCA.\n\n For a plaintiff to adequately plead that a contractual\n\nbreach could reasonably lead to an FCA action, he or she must\n\n\n\n\n 17 Anticipating this possible outcome of our review,\nGuilfoile asserts that the district court erred by twice rejecting\nhis requests to amend the complaint to correct any pleading\ndeficiencies. But he has not demonstrated that the court abused\nits discretion and committed a manifest error of law in denying\nhis motion to vacate the judgment and amend the complaint. See\nMarkel Am. Ins. Co. v. Díaz-Santiago, 674 F.3d 21, 32 (1st Cir.\n2012) (stating that we \"review[] the district court's denial of\npost-judgment relief under Rule 59(e) for abuse of discretion,\"\nand that, \"[g]enerally, to prevail on a Rule 59(e) motion, the\nmoving party must . . . clearly establish a manifest error of law.\"\n(internal quotation marks omitted)); Maldonado v. Dominguez, 137\nF.3d 1, 11 (1st Cir. 1998) (\"[A] district court cannot allow an\namended pleading where a final judgment has been rendered unless\nthat judgment is first set aside or vacated pursuant to Fed. R.\nCiv. P. 59 or 60.\").\n\n\n\n - 32 -\n\nadequately plead causation and materiality. See D'Agostino v.\n\nev3, Inc., 845 F.3d 1, 7-8 (1st Cir. 2016). With respect to the\n\n24/7 call center contractual term, Guilfoile has not pleaded any\n\nplausible connection between the alleged contractual breach and\n\nthe submission of claims to the government, or how the contractual\n\nbreach would have been material to the payment of any claims. For\n\nthis reason, the district court correctly dismissed Guilfoile's\n\nFCA retaliation claim to the extent it relied on his activities\n\nconcerning the 24/7 call center.18\n\n IV.\n\n For the foregoing reasons, we affirm dismissal of the\n\ncomplaint as to the 24/7 call center issue but vacate and remand\n\nas to the retaliation claim involving a potential violation of the\n\nAnti-Kickback Statute. Given this disposition, the district court\n\nmay need to reconsider its decision to decline supplemental\n\njurisdiction over Guilfoile's state law claims.\n\n So ordered. Costs to appellant.\n\n - Concurring and Dissenting Opinion Follows -\n\n\n 18Our reasoning and conclusion would be the same if Guilfoile\nhad alleged that the Integrated Entity violated any statute or\nregulation by not having a 24/7 call center or by falsely stating\nin its contracts that it had a 24/7 call center. See Booker, 847\nF.3d at 60. However, we do not read the complaint to plausibly\nallege that the Integrated Entity violated any statutes or\nregulations despite Guilfoile's subjective belief that the alleged\nfalse representation \"posed a serious threat to public health and\nsafety.\"\n\n\n\n - 33 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358950/", "author_raw": "LIPEZ, Circuit Judge"}, {"author": "BARRON, Circuit Judge, concurring", "type": "concurrence", "text": "BARRON, Circuit Judge, concurring in part and dissenting\n\nin part. To plead a viable retaliation claim under the False\n\nClaims Act (\"FCA\"), 31 U.S.C. § 3730(h)(1), a plaintiff must allege\n\nthat the conduct that he reported to his employer and that resulted\n\nin his termination was \"calculated, or reasonably could lead, to\n\na viable FCA action.\" United States ex rel. Karvelas v. Melrose-\n\nWakefield Hosp., 360 F.3d 220, 236 (1st Cir. 2004) (internal\n\nquotation marks omitted). Thus, when an FCA retaliation claim\n\nrelies on a report of a violation of the Anti-Kickback Statute\n\n(\"AKS\"), 42 U.S.C. § 1320a-7b(g), as is the case here, the\n\nplaintiff needs to allege facts that would suffice to show that\n\nthe conduct that he reported to his employer is of a kind that is\n\nactionable under the AKS. See Karvelas, 360 F.3d at 237 (holding\n\nthat \"protected\" activities must \"concern the employer's knowing\n\nsubmission of false or fraudulent claims for payment to the\n\ngovernment\" (emphasis added)).\n\n To be clear, the plaintiff in such a case need not prove\n\nat the pleading stage that what he complained to his employer about\n\nwas an actual AKS violation. But, the plaintiff must sufficiently\n\nallege that \"his reports concerned FCA-violating activity such as\n\nthe submission of false claims\" resulting from conduct that could\n\nconstitute a violation of the AKS. United States ex rel. Booker\n\nv. Pfizer, Inc., 847 F.3d 52, 60 (1st Cir. 2017). And, for that\n\nreason, the allegation in Thomas Guilfoile's complaint in this\n\n\n - 34 -\n\ncase that \"he reasonably believed\" that the conduct that he was\n\nreporting to his employer prior to his termination revealed a\n\n\"violation[] of the AKS . . . resulting in the submission of\n\nfraudulent claims to the government\" is not itself of any\n\nsignificance. Guilfoile must do more than assert a \"legal\n\nconclusion couched as a factual allegation\" to satisfy his burden\n\nat the pleading stage. Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009)\n\n(quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555 (2007));\n\nsee also Karvelas, 360 F.3d at 224 (setting aside \"bald assertions\"\n\nor \"unsupportable conclusions\" in an FCA complaint). The crucial\n\nquestion that we must resolve, therefore, is whether, taking as\n\ntrue the complaint's factual allegations about the conduct that\n\nGuilfoile reported to his employer, Guilfoile has satisfied his\n\nburden to show that the conduct that he allegedly reported is at\n\nleast of a kind that falls within the scope of the AKS. For, if\n\nthat conduct alleged is not even of that kind, then I do not see\n\nhow his FCA retaliation claim -- insofar as it is premised on the\n\nreport of an AKS violation -- may survive a motion to dismiss.\n\n I.\n\n Guilfoile alleges in his complaint that his employer --\n\nseveral general pharmacy services providers operating as a single\n\nintegrated entity (the \"Integrated Entity\") -- was bidding for\n\nhospital contracts with the assistance of a financial consultant,\n\nMichael Greene, who was simultaneously serving as a financial\n\n\n - 35 -\n\nadvisor to those hospitals. I agree with the majority that\n\nGuilfoile sufficiently alleges in his complaint that he was fired\n\nby his employer after reporting that it was making payments to the\n\nconsultant in order to induce him to use his position at the\n\nhospitals to steer the hospital contracts the Integrated Entity's\n\nway. See Maj. Op. 25. I also agree that these allegations of\n\nemployer-induced double-dealing are concerning.\n\n Nevertheless, the District Court found those factual\n\nallegations -- even if taken as true -- to be legally wanting.\n\nThe District Court did so because it interpreted the AKS to\n\nprohibit only payments made to induce \"other providers or\n\nindividuals [to] directly refer[] or recommend[] patients to\n\nspecific services\" to be paid for with federal health care funds.\n\nThe District Court then concluded that Guilfoile has not alleged\n\nfacts sufficient to show that Greene \"could or did play a role in\n\nreferring or recommending federal program patients to Defendants\n\nthrough his financial consultant work with Defendants.\"\n\n In reaching that conclusion, the District Court rejected\n\nGuilfoile's argument that Greene's facilitation of general\n\ncontracts between the Integrated Entity and the hospitals for\n\ngeneral pharmacy services that created the opportunity for\n\n\"general access to patients amounts to a referral or\n\nrecommendation\" within the meaning of the AKS. The District Court\n\nappears to have relied for that determination on the attenuated\n\n\n - 36 -\n\nrelationship between two things: (1) the general contracts for\n\npharmacy services that Greene allegedly arranged between the\n\nIntegrated Entity and the hospitals; and (2) the particular\n\npurchases by particular buyers of drugs from the pharmacies set up\n\nby the Integrated Entity in the hospitals.\n\n I see how the text of the AKS lends support to the\n\nDistrict Court's logic. As relevant here, the AKS prohibits\n\npayments \"to induce\" the recipient of the payments \"to purchase,\n\nlease, order, or arrange for or recommend purchasing, leasing, or\n\nordering any good, facility, service, or item for which payment\n\nmay be made in whole or in part under a Federal health care\n\nprogram[.]\" 42 U.S.C. § 1320a-7b(b)(2)(B). The only transactions\n\nthat Guilfoile has alleged that the Integrated Entity paid Greene\n\nto induce him to \"arrange for or recommend\" directly, however, are\n\nthe \"purchas[es]\" or \"order[s]\" by the hospitals of the specialty\n\npharmacy services provided by the Integrated Entity via the\n\ncontracts allegedly facilitated by Greene's paid work for\n\nIntegrated Entity. But, \"payment . . . under a Federal health\n\ncare program\" is not made for those general services. Rather,\n\npayment is only made from a federal health care program in\n\nconsequence of the particular purchases by particular buyers of\n\ndrugs from the pharmacies set up by the Integrated Entity in the\n\nhospitals.\n\n\n\n\n - 37 -\n\n There is, then, necessarily a fair amount of\n\nattenuation between the actual transactions that Greene was\n\nallegedly induced to \"arrange for\" (the hospitals' \"purchas[es]\"\n\nor \"order[s]\" of the Integrated Entity's general pharmacy\n\nservices) and the transactions \"for which payment may be made . .\n\n. under a Federal health care program\" (some unknown purchases\n\nfrom an Integrated Entity-run pharmacy of some unknown drugs by\n\nsome unknown patients who happened to be eligible for reimbursement\n\nunder a federal health care program). Moreover, that degree of\n\nattenuation appears to inhere in the conduct that Guilfoile's\n\ncomplaint alleges took place, given the middleman nature of the\n\ngeneral pharmacy services that the Integrated Entity retained\n\nGreene to assist it in offering to the hospitals. Thus, nothing\n\nabout Guilfoile's allegations concerning his report of that\n\nconduct to his employer indicates that the progression of the case\n\nwill reveal the attenuation that concerned the District Court to\n\nbe any less substantial than it now appears to be.\n\n II.\n\n The majority rejects the District Court's reasoning\n\nregarding the attenuation problem. The majority concludes that\n\nUnited States v. Bay State Ambulance & Hosp. Rental Serv., Inc.,\n\n874 F.2d 20 (1st Cir. 1989), compels us to construe the AKS to\n\nencompass situations with this degree of attenuation between\n\ngeneral services contracts and any federal payment from a federal\n\n\n - 38 -\n\nhealth care program that would result from particular purchases by\n\nparticular patients availing themselves of those services. See\n\nMaj. Op. 26-27. It is true that Bay State did uphold the AKS\n\nconviction of an ambulance services company and its president for\n\npaying kickbacks to a hospital employee. Bay State did so,\n\nmoreover, even though that employee \"arrange[d] for\" only a general\n\nambulance services contract between the hospital and the ambulance\n\nservices provider, and not any particular purchase of ambulance\n\nservices by a patient for which the federal government would make\n\na payment. See id. at 25-26, 36.\n\n In my view, however, Bay State is not so clearly\n\ncontrolling a precedent on the attenuation issue as the majority\n\nconcludes that it is. That is so for three reasons.\n\n First, the attenuation issue was not raised in Bay State.\n\nAnd thus, Bay State did not need to address -- and did not in fact\n\naddress -- whether what the kickback recipient \"arrange[d] for or\n\nrecommend[ed]\" fell within the scope of the AKS or was instead too\n\nattenuated from any payment from a federal healthcare program to\n\ndo so because the parties made no such argument. See Gately v.\n\nCom. of Mass., 2 F.3d 1221, 1226 (1st Cir. 1993) (describing the\n\n\"essential principles of stare decisis\" to include \"(1) an issue\n\nof law must have been heard and decided\" and \"(2) if an issue is\n\nnot argued, or though argued is ignored by the court, or is\n\nreserved, the decision does not constitute a precedent to be\n\n\n - 39 -\n\nfollowed\"); United States v. DiPina, 178 F.3d 68, 73 (1st Cir.\n\n1999) (\"Where, in a prior decision, we have not considered an issue\n\ndirectly and assessed the arguments of parties with an interest in\n\nits resolution, that decision does not bind us in a subsequent\n\ncase where the issue is adequately presented and squarely before\n\nus, merely because some of the background facts are the same.\").\n\n Second, Bay State is in some respects an easier case in\n\nwhich to find the nexus that the text of the AKS demands between\n\nthe payment from a federal health care program and the transaction\n\nthat the payment recipient \"arrange[d] for\" than this one is. The\n\nambulance services eventually purchased by patients in Bay State\n\nwere clearly reimbursable under a federal health care program. By\n\ncontrast, it is less clear to me that the specialty pharmacy\n\nservice (as opposed to the drugs purchased by patients) is itself\n\nreimbursable, thereby making the attenuation issue that concerned\n\nthe District Court all the more acute. And Guilfoile's complaint\n\ndoes nothing to supply useful clarification.19\n\n\n 19 Contraryto the majority's suggestion that this distinction\nis insignificant, see Maj. Op. 27-28, it seems to me that the fact\nthat the contracts between the Integrated Entity and the hospitals\ncontemplate the provision of a general service that is not itself\nreimbursable under a federal healthcare program should give us\npause. The text of the relevant AKS provision requires that the\n\"good, facility, service, or item\" at issue be one \"for which\npayment may be made in whole or in part under a Federal health\ncare program[.]\" 42 U.S.C. § 1320a-7b(b)(2)(B). And I have found\nno authority -- nor does Guilfoile identify any -- that suggests\nthat the AKS does encompass conduct predicated on the defendant's\noffering of middleman services of this type. See, e.g., United\n\n\n - 40 -\n\n Finally, we should, in my view, be wary of extending Bay\n\nState in construing the AKS to reach the conduct alleged here.\n\nCongress passed the AKS to address a form of corruption that\n\nthreatens to cheat federal taxpayers and that might also pose a\n\nrisk to public health. See, e.g., Medicare-Medicaid Anti–Fraud\n\nand Abuse Amendments, Pub. L. 95-142, 91 Stat. 1183 (1977)\n\n(describing the act as one \"to strengthen the capability of the\n\nGovernment to detect, prosecute, and punish fraudulent activities\n\nunder the [M]edicare and [M]edicaid programs\"); United States v.\n\nHancock, 604 F.2d 999, 1001 (7th Cir. 1979) (identifying the \"evils\n\nCongress sought to prevent by enacting the kickback statutes\" to\n\ninclude the \"potential for increased costs to the Medicare-\n\nMedicaid system and misapplication of federal funds\"). In fact,\n\nCongress was so concerned about this form of corruption that it\n\neven made it a felony to engage in the conduct that the AKS covers.\n\nSee Pub. L. 95-142 (upgrading an AKS violation to a felony).\n\n\n\nStates v. Polin, 194 F.3d 863, 864-65 (7th Cir. 1999) (upholding\nconvictions of a doctor and nurse who paid a pacemaker company\nsales representative a fee for each patient he \"referred\" to the\ncompany for pacemaker monitoring services); United States v.\nVernon, 723 F.3d 1234, 1254-55 (11th Cir. 2013) (upholding\nconviction of specialty pharmacy executive who paid a patient\nadvocate a 45% commission for each prescription that her patients\nfilled at the pharmacy to induce the patient advocate to refer her\npatients to the pharmacy); United States v. Shoemaker, 746 F.3d\n614 (5th Cir. 2014) (upholding conviction of nursing staffing\ncompany executive who paid a hospital's board chair $5 for each\nstaffing hour that the hospital purchased from the nursing company\nto induce the chair to recommend to the hospital's COO that the\nhospital increase its hours from the nursing company).\n\n\n - 41 -\n\n But, the AKS, like any statute that addresses an\n\nimportant public problem, does not have limitless reach. And, as\n\nwith any statute that imposes criminal liability, as the AKS does,\n\nwe must be careful to construe its reach in a manner that ensures\n\nthat it affords those subject to it with due notice and in\n\naccordance with the principle that only Congress may impose\n\ncriminal liability. See Liporata v. United States, 471 U.S. 419,\n\n427 (1985).\n\n I recognize that we would not need to worry about\n\ntransgressing those interpretive principles here if, as the\n\nmajority concludes, this case concerns the alleged reporting of\n\nconduct that falls within the AKS's \"heartland.\" See Maj. Op. 27.\n\nBut, I do not see how we could so conclude, no matter how broad\n\nthe AKS may seem to be. In fact, if the conduct alleged in the\n\ncomplaint before us constitutes conduct that is of a kind that\n\nfalls within the AKS's heartland, then I would be hard-pressed to\n\nconjure the kind of conduct that would reside on its outskirts.\n\n Of course, statutes that have cores also have\n\nperipheries. And conduct that falls within the periphery of a\n\nstatute's scope is no less unlawful than conduct that falls within\n\nits core. At the same time, conduct that lies outside even the\n\nperiphery -- as measured, most clearly, by the words that Congress\n\nchose to denominate the statute's bounds -- is not conduct that\n\nmay give rise to liability. And that is so no matter how much\n\n\n - 42 -\n\nsuch conduct may seem to be concerning in its own right and no\n\nmatter how much that kind of conduct may even bear some resemblance\n\nto the kind of conduct that plainly does falls within the statute's\n\nscope.\n\n For all of these reasons, then, Bay State does not, in\n\nmy view, dictate the outcome in this case. And that matters\n\nbecause, although we are generally free to affirm a judgment below\n\non any ground manifest in the record, see MacDonald v. Town of\n\nEastham, 745 F.3d 8, 11 (1st Cir. 2014), we are not equally free\n\nto reverse one on a ground that the appellant does not raise on\n\nappeal. Yet while Guilfoile did cite Bay State in a footnote in\n\nhis filings below to support the proposition that \"paying\n\ninducements for referrals to access markets in order to bill\n\nfederal health care programs is a cognizable violation of the AKS,\n\nand therefore the FCA,\" he has inexplicably, as the Integrated\n\nEntity points out, abandoned that market access argument on\n\nappeal.20 See Igartúa v. United States, 626 F.3d 592, 603 (1st\n\n\n\n\n 20\n I note that Guilfoile does cite Bay State on appeal, but\nonly in support of the separate points that he adequately alleged\nthat Greene's position as a financial advisor at the hospitals put\nhim on sufficient footing to steer the hospital contracts to the\nIntegrated Entity and that he does not need to show that the\nalleged arrangement resulted in a drain on the public fisc.\nGuilfoile does not, however, make any argument on appeal as to how\nBay State resolves the attenuation issue in his favor. See\nGonzález v. Vélez, 864 F.3d 45, 56 n.7 (1st Cir. 2017) (\"On appeal,\n. . . claims are deemed abandoned unless they are, at a minimum,\naccompanied by some developed argumentation.\").\n\n\n - 43 -\n\nCir. 2010) (noting that \"[a]rguments that are intentionally\n\nrelinquished or abandoned\" or \"raised in a perfunctory or not\n\nserious manner [are] waived\").\n\n Having abandoned that theory for why the attenuation\n\ninherent in the conduct that he alleged poses no concern, Guilfoile\n\nengages with the attenuation issue on appeal only by invoking cases\n\nthat discuss whether the plaintiff has sufficiently made out a\n\nfalse claim under the FCA. See, e.g., U.S. ex rel. Hutcheson v.\n\nBlackstone Med., Inc., 647 F.3d 377, 383 (1st Cir. 2011) (holding\n\nthat hospitals' claims for reimbursement of doctor's services\n\nusing medical devices were \"false\" under the FCA where the doctors\n\nhad accepted kickbacks from the medical device manufacturer);\n\nUnited States ex rel. Yesudian v. Howard Univ., 153 F.3d 731, 740\n\n(D.C. Cir. 1998) (holding that plaintiff had \"a good faith basis\n\nfor going forward at the time of retaliation\" as to the\n\n\"[]submission of a false claim to the federal government\" element\n\nwhere the plaintiff knew that 80% of the defendant's money came\n\nfrom the federal government). But, those cases bear only on the\n\nseparate element of an FCA action that a \"false or fraudulent\n\nclaim\" be submitted to the federal government. See 31 U.S.C. §§\n\n3729(a)(1),(b)(2). Given that Guilfoile's FCA retaliation claim\n\nis premised only on the theory that the conduct that he reported\n\nto his employer was prohibited by the AKS, see 42 U.S.C. § 1320a-\n\n7b(g), that separate issue takes on significance only if Guilfoile\n\n\n - 44 -\n\nhas sufficiently alleged as a threshold matter that the conduct\n\nthat he was reporting was of a kind that violates the AKS.\n\n III.\n\n Because I do not believe that Bay State is controlling\n\non the critical issue of attenuation, and because Guilfoile has\n\ndropped the market access theory that he pressed below, I see no\n\nviable basis on appeal for rejecting the District Court's\n\nconclusion that Guilfoile \"has not set forth sufficient factual\n\nallegations to support a plausible anti-kickback statute\n\nviolation.\" To excuse the waiver here is to deprive the appellees\n\nof their judgment based on an argument that Guilfoile -- by\n\nabandoning that argument on appeal -- gave them no reason to think\n\nthat they needed to confront and that, understandably, they did\n\nnot. Accordingly, I see no reason to decide, without adequate\n\nbriefing from the parties, the open interpretive question\n\nconcerning the scope of what constitutes conduct that is of a kind\n\nthe AKS encompasses on which Guilfoile's retaliation claim\n\nnecessarily depends. And so, given the posture of this case -- a\n\nposture that is of Guilfoile's own making on appeal -- I conclude\n\nthat we must affirm the District Court's decision.\n\n I therefore respectfully dissent.\n\n\n\n\n - 45 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358950/", "author_raw": "BARRON, Circuit Judge, concurring"}]}
HOWARD
LIPEZ
BARRON
1
{}
4
0
0
2
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4581697/
Published
1
1
0
1
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Thomas GUILFOILE, Plaintiff, Appellant, v. John M. SHIELDS, Sr.; Shields Pharmacy, LLC, D/B/A Shields Health Solutions; UMass Memorial Shields Pharmacy, LLC, D/B/A Shields Health Solutions; Shields Pharmacy Equity, LLC, D/B/A Shields Health Solutions; Shields Specialty Pharmacy Holdings, LLC, D/B/A Shields Health Solutions, Defendants, Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-15\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1610\n\n THOMAS GUILFOILE,\n\n Plaintiff, Appellant,\n\n v.\n\n JOHN M. SHIELDS, SR.; SHIELDS PHARMACY, LLC, d/b/a Shields\n Health Solutions; UMASS MEMORIAL SHIELDS PHARMACY, LLC, d/b/a\n Shields Health Solutions; SHIELDS PHARMACY EQUITY, LLC, d/b/a\n Shields Health Solutions; SHIELDS SPECIALTY PHARMACY HOLDINGS,\n LLC, d/b/a Shields Health Solutions,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Denise J. Casper, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Lipez and Barron, Circuit Judges.\n\n\n Paul W. Mollica, with whom Tammy T. Marzigliano and Outten &\nGolden LLP were on brief, for appellant.\n Brian J. Leske for appellees.\n Michael J. Sullivan and Ashcroft Law Firm, LLC on brief for\n appellee John M. Shields.\n Walter B. Prince, William A. Worth, and Prince Lobel Tye LLP\non brief for appellees Shields Pharmacy, LLC, and Shields Pharmacy\nEquity, LLC.\n David C. Casey, Stephen T. Melnick, and Littler Mendelson PC\non brief for appellees UMass Memorial Shields Pharmacy, LLC, and\nShields Specialty Pharmacy Holdings, LLC.\n\nJanuary 15, 2019\n\n LIPEZ, Circuit Judge. In alleged violation of the False\n\nClaims Act, appellant Thomas Guilfoile claims he was fired from\n\nhis job in retaliation for accusing his employer of violating the\n\nAnti-Kickback Statute and making false representations in customer\n\ncontracts. See 31 U.S.C. § 3730(h); 42 U.S.C. § 1320a-7b(b). The\n\ndistrict court dismissed his complaint on the ground that Guilfoile\n\ndid not allege sufficient facts to show he was engaged in protected\n\nconduct within the meaning of the retaliation provision of the\n\nFalse Claims Act. After careful review of the complaint and the\n\nlaw, we affirm as to the contractual language claim but vacate and\n\nremand as to the claim involving the Anti-Kickback Statute.\n\n I.\n\nA. Factual Background\n\n Because this appeal follows the grant of a motion to\n\ndismiss pursuant to Federal Rule of Civil Procedure 12(b)(6), we\n\nrecite the facts as alleged in the amended complaint. See\n\nDavis v. Coakley, 802 F.3d 128, 130 (1st Cir. 2015). We include\n\nonly those facts relevant to the issues on appeal.\n\n Appellant Guilfoile is a seasoned management\n\nprofessional with 30 years of finance and operations experience.\n\nAppellee John Shields, Guilfoile's employer during the period\n\nrelevant to this case, is the CEO of a collection of health care\n\nLLCs, joint ventures, and holding companies that operate in concert\n\nas a single integrated entity (the \"Integrated Entity\"). The\n\n\n - 3 -\n\ncomponent businesses of the Integrated Entity include appellees\n\nShields Pharmacy, LLC; UMass Memorial Shields Pharmacy, LLC;\n\nShields Pharmacy Equity, LLC; and Shields Specialty Pharmacy\n\nHoldings, LLC.1\n\n The Integrated Entity partners with hospitals to provide\n\nspecialty pharmacy services for chronically ill patients by either\n\noperating a pharmacy directly in the hospital or by filling\n\nspecialty prescriptions through an off-site location. The\n\nIntegrated Entity processes the prescriptions, bills the patient's\n\ninsurance, provides patients with financial advice, and follows up\n\nwith patients to ensure their adherence to complex medication\n\nregimens. The Integrated Entity regularly bills federal insurance\n\nprograms, including Medicaid and Medicare, for the services it\n\nprovides to patients covered by those programs. As a secondary\n\nline of business, the Integrated Entity also runs home infusion\n\nand high-risk care management programs.\n\n After years of providing free business advice to his\n\nlong-time friend and neighbor Shields, Guilfoile began to consult\n\nfor the Integrated Entity in April 2013 and officially joined the\n\nIntegrated Entity full-time as president in August of that year.\n\n\n 1 All four component corporations are closely-held\ncorporations with a shared principal place of business at an office\nin Quincy, Massachusetts. Two of the corporations are incorporated\nin Massachusetts and two are incorporated in Delaware. Shields is\nthe sole manager registered with the Secretary of the Commonwealth\nof Massachusetts for all four corporations.\n\n\n - 4 -\n\nGuilfoile's employment contract included terms governing salary,\n\nbonuses, an equity stake in the Integrated Entity's joint ventures,\n\nan equity vesting schedule, and protocols in the event of\n\ntermination. Shields was Guilfoile's immediate supervisor. The\n\ncomplaint alleges that during Guilfoile's tenure, Shields\n\nSpecialty Pharmacy Holdings and UMass Memorial Shields Pharmacy\n\nhad boards of directors composed of Shields, Guilfoile, and the\n\nsame two other individuals.2\n\n Under Guilfoile's leadership, the Integrated Entity grew\n\nfrom a start-up to a successful operation generating millions of\n\ndollars in profit. The Integrated Entity enjoyed overwhelmingly\n\npositive feedback from patients, providers, and employees, and\n\nGuilfoile's leadership was appreciated by Shields and the\n\nIntegrated Entity.\n\n However, in the fall of 2015, Guilfoile became concerned\n\nthat the Integrated Entity was violating the law. At that time,\n\nhe learned that Shields had previously entered into a contract on\n\nbehalf of the Integrated Entity with Michael Greene,3 Shields's\n\nlong-time friend and a consultant whom several New Jersey hospitals\n\n\n 2 The complaint does not shed much further light on the\nIntegrated Entity's management structure. For ease of reference,\nwe join the parties and refer to the two boards of directors\nidentified in the complaint as \"the Board.\"\n\n 3 The pleadings, briefs, and the district court's order\nsometimes spell the consultant's surname as \"Green,\" but we follow\nthe spelling suggested by appellant and supported by the record.\n\n\n - 5 -\n\npaid for financial advice. The contract obligated the Integrated\n\nEntity to, among other things, pay Greene's consulting firm, the\n\nAyrault Group, $35,000 per quarter for each hospital contract that\n\nGreene successfully referred to the Integrated Entity,\n\nspecifically targeting two hospitals that Greene was working for\n\nas a paid consultant: Newark Beth Israel Medical Center (\"NBIMC\")\n\nand University Hospital (\"University\"). The Integrated Entity,\n\nwith assistance from Greene, eventually entered into contracts for\n\nspecialty pharmacy services with both NBIMC and University, and\n\nthe Integrated Entity paid Greene \"referral fees.\" Guilfoile\n\nbelieved that these payments \"had improperly induced [Greene] to\n\nsteer [the] hospital contracts to the Integrated Entity.\"\n\n Guilfoile conferred with the Integrated Entity's\n\ncounsel, who agreed that Guilfoile had valid concerns about the\n\ncontract with Greene. Guilfoile notified Shields that he believed\n\nthe contract violated the federal Anti-Kickback Statute because\n\nthe Integrated Entity had paid Greene to secure contracts with\n\nhospitals that would result in the Integrated Entity making claims\n\nfor payment to federal insurance programs. Such payments are\n\nprohibited by the statute, as explained in greater detail below.\n\nGuilfoile was especially concerned about the implications of the\n\nkickback scheme for the contract with University, which he believed\n\nwas government owned.\n\n\n\n\n - 6 -\n\n At Guilfoile's insistence, Shields ultimately approached\n\nGreene to discuss voiding Greene's contract with the Integrated\n\nEntity and obtaining refunds of any payments to the Ayrault Group.\n\nAfter an apparent negotiation, Shields revealed to Guilfoile that\n\nGreene agreed to waive payments yet to be made for the University\n\nreferral but refused to return the money that the Integrated Entity\n\nhad already paid for the NBIMC referral. Guilfoile believed that\n\nby letting the NBIMC payment stand, the Integrated Entity still\n\nmay have violated the Anti-Kickback Statute. He therefore urged\n\nShields to reveal the matter to the Board and offered to make the\n\ndisclosure jointly. Shields refused.\n\n In December 2015, Guilfoile learned that the contracts\n\nthe Integrated Entity had used to form partnerships with hospitals\n\ncontained a false representation that the Integrated Entity\n\nmaintained \"a fully staffed 24/7 [c]all [c]enter in Quincy,\n\nMassachusetts.\" The Integrated Entity at the time did not have\n\nsuch a center.4 Guilfoile believed that making false\n\nrepresentations to government-owned hospitals, like University,\n\nabout medication management services for chronically ill patients\n\nwith serious medical conditions was contract fraud and posed a\n\nserious threat to public health and safety.\n\n\n 4 The complaint is unclear as to whether the Integrated\nEntity operated a call center that did not conform with the\ndescription in the contracts, or if the Integrated Entity did not\noperate a call center at all.\n\n\n - 7 -\n\n Despite Guilfoile's insistence that the Integrated\n\nEntity either amend the contracts to remove the representation or\n\ncreate a fully-staffed 24/7 call center, Shields refused to take\n\naction or notify the Board. Instead, Shields suggested that the\n\nIntegrated Entity should address the issue only if a customer\n\ncomplained about the breach. In an effort to bring the Integrated\n\nEntity into compliance with the contractual language, Guilfoile\n\nalerted the Human Resources department and the Director of\n\nOperations that they should prepare to hire enough staff to operate\n\na 24/7 call center.\n\n On December 22, 2015, Shields asked Guilfoile to come\n\nto his home office, where Shields expressed his concern about\n\nGuilfoile \"going over his head\" and \"airing his dirty laundry\" to\n\nthe Board. Shields told Guilfoile that he viewed the Board as a\n\n\"third rail\" -- i.e., an entity that should be approached with\n\ncaution -- to which Guilfoile was getting too close. Shields also\n\nexplained that he felt he \"had to protect his interests and his\n\nfamily\" and that he could not risk a vote by the Board against\n\nhim. After Guilfoile rejected Shields's suggestion that the two\n\nof them consider \"parting ways,\" the meeting ended without a\n\nconcrete resolution. Shields stated that he would give the matter\n\nadditional thought.\n\n A week later, on December 28, Shields terminated\n\nGuilfoile's employment in a phone call without further\n\n\n - 8 -\n\nexplanation. The following day, Shields emailed Guilfoile to\n\nconfirm that his employment was terminated. Shields did not\n\nprovide any reason for the termination and did not refer to\n\nGuilfoile's performance or possible misconduct as a basis for the\n\ntermination. Guilfoile then received a written notice stating\n\nthat his termination was retroactive to December 22. The letter\n\ndid not state that he was being terminated for cause.\n\n After his termination, Guilfoile notified the Board that\n\nShields had terminated him because he feared that Guilfoile would\n\nreport the suspected violations of law to the Board. Guilfoile\n\nsubsequently forwarded a letter to the Board memorializing his\n\nconcerns. Following these disclosures, Shields made repeated\n\nthreats to file suit against Guilfoile for defamation and tortious\n\ninterference, which he in fact subsequently did. On February 26,\n\n2016, Guilfoile received a letter from the Integrated Entity\n\ndiscussing its purported right to repurchase Guilfoile's vested\n\nequity for a total of $15. The letter stated, for the first time,\n\nthat Guilfoile had been \"terminated for cause.\"\n\nB. Procedural Background\n\n On April 1, 2016, Guilfoile filed this action against\n\nthe Integrated Entity and Shields alleging \"whistleblower\n\nretaliation\" in violation of the False Claims Act and a variety of\n\nstate law employment, wage, contract, and tort claims. In the\n\noperative amended complaint (\"the complaint\"), filed after\n\n\n - 9 -\n\ndefendants filed motions to dismiss, Guilfoile alleges that the\n\nIntegrated Entity retaliated against him for his \"efforts to stop\n\nviolations of the [False Claims Act],\" specifically his\n\n\"disclosures . . . related to the kickbacks [the Integrated Entity]\n\npaid Mr. Green[e] in exchange for referrals of federally insured\n\npatients, and disclosures related to contracts the Integrated\n\nEntity entered into with government-owned hospitals even though\n\nthe Integrated Entity knew the contracts included fraudulent\n\nterms.\"\n\n Regarding the payments to the Ayrault Group, the\n\ncomplaint alleges that Guilfoile reasonably believed the payments\n\nto be \"violations of the [Anti-Kickback Statute], a per se\n\nviolation of the [False Claims Act], resulting in the submission\n\nof fraudulent claims to the government,\" and that \"[t]he Integrated\n\nEntity violated the [Anti-Kickback Statute] and the [False Claims\n\nAct] by willfully paying remuneration to induce a person [Greene]\n\nto refer patients for the furnishing of a service for which the\n\nIntegrated Entity knew payment would be made under federal health\n\ncare programs.\" Finally, the complaint alleges that the Integrated\n\nEntity retaliated against Guilfoile by terminating his employment,\n\n\"threatening to sue him, fabricating an after-the-fact contention\n\nas to 'cause,' attempting to repurchase his equity for the amount\n\n\n\n\n - 10 -\n\nof $15, and then making good on their threat to sue him after he\n\ninstituted this law suit.\"5\n\n Following oral argument on defendants' motions to\n\ndismiss, Guilfoile requested leave to file a memorandum \"in\n\nresponse to legal authority and factual allegations that\n\n[d]efendants raised for the first time during oral argument.\" The\n\nlast sentence of the brief accompanying the request stated, \"If\n\nthis [c]ourt determines . . . that the present [a]mended\n\n[c]omplaint does not adequately plead a cause of action under the\n\nanti-retaliation provision of the [False Claims Act], plaintiff\n\nrespectfully requests that the [c]ourt allow him the opportunity\n\nto file a second amended complaint alleging additional facts, like\n\nthose set forth in this memorandum and supporting affidavit.\"\n\nGuilfoile's \"supporting affidavit\" alleged additional facts\n\nconcerning the Integrated Entity's business, Greene's role in\n\nrecommending the Integrated Entity to the hospitals for the\n\nprovision of pharmacy services, and the nature of the 24/7 call\n\ncenter service.\n\n In granting the motions to dismiss, the district court\n\ndetermined that Guilfoile had failed to adequately plead that he\n\nwas engaged in protected conduct, the first element of a False\n\n\n 5The complaint alleges that \"four days after Mr. Guilfoile\ninitiated this action in federal court . . . Mr. Shields filed\nsuit against [him] in state court, bringing claims for defamation\nand tortious interference.\"\n\n\n - 11 -\n\nClaims Act retaliation claim. The court therefore dismissed the\n\nretaliation count without analyzing the other elements of the\n\nclaim. The court then declined to exercise supplemental\n\njurisdiction over the state law claims and dismissed them without\n\nprejudice. In a footnote, the court granted in part and denied in\n\npart Guilfoile's request to provide a response to defendants'\n\npurportedly new theories and factual allegations presented at oral\n\nargument. The court stated that it had considered his briefing as\n\nto the legal authority first raised at oral argument, but had not\n\nconsidered factual assertions outside the complaint, presumably\n\nincluding the factual assertions in the \"supporting affidavit.\"\n\nThe court did not respond to Guilfoile's suggestion in his motion\n\nthat he be allowed to file a second amended complaint if the court\n\nfound the operative complaint lacking.\n\n Guilfoile subsequently filed a \"Motion to Vacate\n\nJudgment and For Leave to Amend the Complaint\" pursuant to Federal\n\nRules of Civil Procedure 59(e) and 15(a). After the district court\n\ndenied the motion, Guilfoile timely appealed both the dismissal of\n\nhis complaint and the denial of his post-judgment motion.\n\n II.\n\nA. Standard of Review\n\n We review de novo a district court's grant of a motion\n\nto dismiss pursuant to Federal Rule of Civil Procedure 12(b)(6).\n\nHaley v. City of Boston, 657 F.3d 39, 46 (1st Cir. 2011). We must\n\n\n - 12 -\n\nevaluate whether the complaint adequately pleads facts that \"state\n\na claim to relief that is plausible on its face.\" Bell Atl. Corp.\n\nv. Twombly, 550 U.S. 544, 570 (2007). In performing this\n\nevaluation, we \"assume the truth of all well-pleaded facts and\n\ngive the plaintiff the benefit of all reasonable inferences\n\ntherefrom.\" Thomas v. Rhode Island, 542 F.3d 944, 948 (1st Cir.\n\n2008). However, we do not \"draw unreasonable inferences or credit\n\nbald assertions [or] empty conclusions.\" Theriault v. Genesis\n\nHealthCare LLC, 890 F.3d 342, 348 (1st Cir. 2018) (alteration in\n\noriginal) (internal quotation marks omitted). A suit is properly\n\ndismissed \"if the complaint does not set forth factual allegations,\n\neither direct or inferential, respecting each material element\n\nnecessary to sustain recovery under some actionable legal theory.\"\n\nU.S. ex rel. Hutcheson v. Blackstone Med., Inc., 647 F.3d 377, 384\n\n(1st Cir. 2011) (emphasis added) (internal quotation marks\n\nomitted). Before reviewing the sufficiency of the complaint under\n\nthis standard, we provide a brief overview of the pertinent\n\nstatutes.\n\nB. False Claims Act\n\n The False Claims Act (\"FCA\"), 31 U.S.C. §§ 3729-3733,\n\nprohibits, in relevant part, any person from \"knowingly\n\npresent[ing], or caus[ing] to be presented, a false or fraudulent\n\nclaim\" to the federal government. 31 U.S.C. § 3729(a)(1)(A)\n\n(emphasis added); see Universal Health Servs., Inc. v. United\n\n\n - 13 -\n\nStates ex rel. Escobar, 136 S. Ct. 1989, 1996 (2016) (explaining\n\nthat the FCA is focused \"on those who present or directly induce\n\nthe submission of false or fraudulent claims\").6 For purposes of\n\nthe statute, \"a 'claim' . . . includes direct requests to the\n\n[g]overnment for payment as well as reimbursement requests made to\n\nthe recipients of federal funds under federal benefit programs.\"\n\nEscobar, 136 S. Ct. at 1996 (citing 31 U.S.C. § 3729(b)(2)(A)).\n\nThe FCA includes a scienter requirement that the false claim be\n\nsubmitted \"knowingly.\" 31 U.S.C. § 3729(a)(1), (b)(1). A \"non-\n\nsubmitting\" entity that knowingly causes the submission of a false\n\nclaim may be liable under the FCA even if the entity directly\n\nsubmitting the claim to the government lacks the requisite mental\n\nstate. See Hutcheson, 647 F.3d at 389-90.\n\n The FCA is also \"subject to a judicially-imposed\n\nrequirement that the allegedly false claim . . . be material.\"\n\nUnited States ex rel. Loughren v. Unum Grp., 613 F.3d 300, 307\n\n(1st Cir. 2010).7 The falsity of a claim is \"material\" if it has\n\n\n\n 6 The FCA does not define \"false or fraudulent.\" However,\nthe Supreme Court has held that the phrase encompasses\n\"misrepresentations by omission\" in addition to \"express\nfalsehoods.\" Escobar, 136 S. Ct. at 1999.\n 7 The FCA defines and uses \"material.\" See 31 U.S.C.\n§ 3729(a)(1)(B), (G), (b)(4). However, § 3729(a)(1)(A), which\nprohibits the knowing submission of false claims, does not contain\nthe term. We have therefore described the \"materiality\"\nrequirement in regard to § 3729(a)(1)(A) as judicially created\nbecause it derives from a general reading of materiality into all\nsections of the FCA rather than from the statutory language. See\n\n\n - 14 -\n\n\"a natural tendency to influence or was capable of influencing the\n\n[government]'s decision\" whether to pay or reimburse the claim.\n\nId. The Supreme Court has emphasized that the FCA's \"materiality\n\nstandard is demanding,\" and a plaintiff directly alleging the\n\nsubmission of a false claim8 must plead facts to support\n\nallegations of materiality with \"plausibility and particularity.\"\n\nEscobar, 136 S. Ct. at 2003, 2004 n.6. Whether an express or\n\nimplied false representation of compliance with statutes or\n\nregulations is \"material\" is ordinarily \"a fact-intensive and\n\ncontext-specific inquiry.\" New York v. Amgen Inc., 652 F.3d 103,\n\n111 (1st Cir. 2011).\n\n In addition to prohibiting the submission of false\n\nclaims, the FCA bars an employer from retaliating against an\n\nemployee \"because of lawful acts done . . . in furtherance of an\n\naction under this section or other efforts to stop 1 or more\n\nviolations of [the FCA].\" 31 U.S.C. § 3730(h)(1). To prevail on\n\nan FCA retaliation claim, \"a plaintiff must show that 1) the\n\nemployee's conduct was protected under the FCA; 2) the employer\n\n\n\nHutcheson, 647 F.3d at 388 n.13. Indeed, the Supreme Court has\ndeclined to decide \"whether § 3729(a)(1)(A)'s materiality\nrequirement is governed by § 3729(b)(4) [the statutory definition\nof \"materiality\"] or derived directly from the common law.\"\nEscobar, 136 S. Ct. at 2002.\n\n 8 The False Claims Act's \"qui tam\" provisions authorize\nprivate individuals, known as \"relators,\" to bring suit on the\ngovernment's behalf based on the submission of false claims to the\ngovernment. See 31 U.S.C. § 3730(b).\n\n\n - 15 -\n\nknew that the employee was engaged in such conduct; and 3) the\n\nemployer discharged or discriminated against the employee because\n\nof his or her protected conduct.\" United States ex rel. Karvelas\n\nv. Melrose-Wakefield Hosp., 360 F.3d 220, 235 (1st Cir. 2004),\n\nabrogated on other grounds by Allison Engine Co., Inc. v. United\n\nStates ex rel. Sanders, 553 U.S. 662 (2008). In general, \"proving\n\na violation of § 3729 [the false claims provision] is not an\n\nelement of a § 3730(h) [retaliation] cause of action.\" Graham\n\nCty. Soil & Water Conservation Dist. v. United States ex rel.\n\nWilson, 545 U.S. 409, 416 n.1 (2005).\n\n The pleading standards for actions directly alleging the\n\nsubmission of false claims, such as qui tam actions pursuant to 31\n\nU.S.C. § 3730(b), and the pleading standards for actions alleging\n\nretaliation, differ in crucial ways. In a suit directly alleging\n\nthe submission of a false claim, a plaintiff must sufficiently\n\nplead facts supporting the existence of an actual false claim.\n\nSee Karvelas, 360 F.3d at 225 (\"Evidence of an actual false claim\n\nis the sine qua non of a False Claims Act violation.\" (internal\n\nquotation marks omitted)). However, in a suit alleging retaliation\n\nunder the FCA, a plaintiff must sufficiently plead that he or she\n\nwas retaliated against based on \"conduct that reasonably could\n\nlead to a viable FCA action.\" Id. at 236. We have further\n\nexplained that \"conduct protected under\" the FCA retaliation\n\nprovision encompasses an employee's \"investigations, inquiries,\n\n\n - 16 -\n\ntestimonies or other activities that concern the employer's\n\nknowing submission of false or fraudulent claims for payment to\n\nthe government.\" United States ex rel. Booker v. Pfizer, Inc.,\n\n847 F.3d 52, 59 (1st Cir. 2017) (quoting Karvelas, 360 F.3d at\n\n237).9 This standard is consistent with the legislative intent\n\nthat \"[p]rotected activity [for purposes of an FCA retaliation\n\nclaim] should . . . be interpreted broadly.\" Karvelas, 360 F.3d\n\nat 236 (quoting S. Rep. No. 99–345, at 34 (1986), reprinted in\n\n1986 U.S.C.C.A.N. 5266, 5299). Because an FCA retaliation claim\n\n\"does not require a showing of fraud,\" a plaintiff alleging\n\nretaliation \"need not meet the heightened pleading requirements of\n\n[Federal Rule of Civil Procedure] 9(b).\" Id. at 238 n.23.10\n\n\n\n\n 9 We derived the \"reasonably could lead\" standard from the\nstatutory language prohibiting retaliation by an employer \"because\nof lawful acts done by the employee . . . in furtherance of an\n[FCA] action.\" See Karvelas, 360 F.3d at 235-36 (quoting 31 U.S.C.\n§ 3730(h)(1)). Therefore, a court must consider whether the\nconduct of the employee who was allegedly retaliated against --\nthat is, the employee's whistleblowing or investigative activities\n-- reasonably could lead to an FCA action. Of course, the question\nof whether the employer engaged in conduct that could run afoul of\nthe FCA is a necessary component of this inquiry. After all, the\nemployee's conduct must \"concern the employer's knowing submission\nof false . . . claims . . . because only such conduct reasonably\ncould lead to an FCA action.\" Booker, 847 F.3d at 59-60 (internal\nquotation marks omitted).\n\n 10 Conversely, because a direct FCA claim does require a\nshowing of fraud, a qui tam plaintiff must \"meet the Rule 9(b)\npleading standards.\" Karvelas, 360 F.3d at 238.\n\n\n - 17 -\n\nC. Anti-Kickback Statute\n\n The Anti-Kickback Statute (\"AKS\") criminalizes, in\n\nrelevant part, the \"knowing[] and willful[]\" offer or payment of\n\n\"any remuneration (including any kickback, bribe, or rebate)\" to\n\ninduce a person to \"recommend . . . ordering any . . . service\n\n. . . for which payment may be made in whole or in part under a\n\n[f]ederal health care program.\" 42 U.S.C. § 1320a-7b(b)(2)(B).\n\nRelevant considerations for identifying an unlawful kickback\n\ninclude: (1) whether the person being paid the alleged kickback is\n\n\"in a position to generate [f]ederal health care program business\"\n\nand (2) whether at least one purpose of the payment could be \"to\n\ninduce or reward the referral or recommendation of business payable\n\nin whole or in part by a [f]ederal health care program.\" OIG\n\nSupplemental Compliance Program Guidance for Hospitals, 70 Fed.\n\nReg. 4858, 4864 (Jan. 31, 2005). Essentially, the AKS targets any\n\nremunerative scheme through which a person is \"paid 'in return\n\nfor' referrals\" to a program under which payments may be made from\n\nfederal funds. United States v. Patel, 778 F.3d 607, 618 (7th\n\nCir. 2015) (quoting 42 U.S.C. § 1320a-7b(b)(1)(A)).\n\nIn 2010, the AKS was amended to create an express link to the FCA.\n\nThe AKS now provides that \"a claim that includes items or services\n\nresulting from a violation of this section constitutes a false or\n\nfraudulent claim for purposes of [the FCA].\" 42 U.S.C.\n\n\n\n\n - 18 -\n\n§ 1320a-7b(g), as amended by the Patient Protection and Affordable\n\nCare Act, Pub. L. No. 1110148, 124 Stat. 119 (2010).\n\n III.\n\n Appellant contends that he was retaliated against within\n\nthe meaning of the FCA anti-retaliation provision when he was fired\n\nafter raising concerns to Shields and others about (1) the alleged\n\nkickbacks to Greene and (2) the contractual misrepresentations\n\nregarding a 24/7 call center. Although appellees attack the\n\nsufficiency of the complaint on several grounds, the district court\n\ndismissed the FCA claims on the basis that Guilfoile had not\n\nplausibly pleaded that he had engaged in protected conduct. Our\n\nanalysis begins with this first element of an FCA retaliation\n\nclaim.\n\nA. Payments to Greene/Ayrault Group\n\n The district court concluded that Guilfoile had failed\n\nto adequately plead that his actions in raising concerns about the\n\npayments to Greene and the Ayrault Group reasonably could have led\n\nto an FCA action. Specifically, the district court reasoned that\n\nGuilfoile failed to adequately plead an AKS violation, and that\n\neven if he had adequately pleaded an AKS violation, he failed to\n\nconnect any such violation to a potential false claim within the\n\nmeaning of the FCA. We disagree with the district court's approach\n\nand its conclusion.\n\n\n\n\n - 19 -\n\n Guilfoile has brought an FCA retaliation claim, not a\n\n\"direct\" claim of an FCA violation. As discussed above, adequately\n\npleading an FCA retaliation claim does not require adequately\n\npleading the submission of a false claim or meeting the Rule 9(b)\n\nstandards for pleading fraud. See Graham Cty., 545 U.S. at 416 &\n\nn.1; Karvelas, 360 F.3d at 238 n.23; see also United States ex\n\nrel. Grenadyor v. Ukrainian Vill. Pharmacy, Inc., 772 F.3d 1102,\n\n1108-09 (7th Cir. 2014) (affirming dismissal of qui tam claim for\n\nfailure to plead kickbacks with particularity but reversing\n\ndismissal of retaliation claim based on internal reporting of\n\nalleged kickbacks). Rather, plaintiffs like Guilfoile need only\n\nplead that their actions in reporting or raising concerns about\n\ntheir employer's conduct \"reasonably could lead to an FCA action.\"\n\nBooker, 847 F.3d at 59 (internal quotation marks omitted). Put\n\ncolloquially, rather than plausibly pleading the existence of a\n\nfire -- the actual submission of a false claim -- a plaintiff\n\nalleging FCA retaliation need only plausibly plead a reasonable\n\namount of smoke -- conduct that could reasonably lead to an FCA\n\naction based on the submission of a false claim.\n\n Because this case involves an alleged violation of the\n\nAKS, we consider the 2010 amendment to the AKS stating that \"a\n\nclaim that includes items or services resulting from a violation\n\nof this section constitutes a false or fraudulent claim for\n\npurposes of [the FCA.]\" 42 U.S.C. § 1320a-7b(g). We have\n\n\n - 20 -\n\npreviously declined to directly address the impact of\n\n§ 1320a-7b(g) on FCA actions, see Hutcheson, 647 F.3d at 379 n.1,\n\nand we do not attempt to assess the full implications of the AKS\n\nprovision today. We need not do so because the issue before us is\n\nnot the standard for proving an FCA violation based on the AKS,\n\nbut rather the requirements for pleading an FCA retaliation claim.\n\nFor our present purposes, it is enough to say that in light of\n\n§ 1320a-7b(g), \"[a]n AKS violation that results in a federal health\n\ncare payment is a per se false claim under the FCA.\" United States\n\nex rel. Lutz v. United States, 853 F.3d 131, 135 (4th Cir. 2017).\n\nThat is, drawing on the \"resulting from\" language of the 2010\n\namendment, if there is a sufficient causal connection between an\n\nAKS violation and a claim submitted to the federal government,\n\nthat claim is false within the meaning of the FCA. See United\n\nStates ex rel. Greenfield v. Medco Health Sols., Inc., 880 F.3d\n\n89, 96-98 (3d Cir. 2018) (discussing causal connection issue);11\n\nUnited States ex rel. Bawduniak v. Biogen Idec, Inc., No. 12-CV-\n\n10601-IT, 2018 WL 1996829, at *5-6 (D. Mass. Apr. 27, 2018) (same).\n\n We further read the AKS amendment as obviating the need\n\nfor a plaintiff to plead materiality -- that is, to plead that\n\n\n\n\n 11 We note that Greenfield involved a qui tam suit directly\nalleging an FCA claim based on a violation of the AKS and\nultimately turned on the standard for proving such claims at\nsummary judgment. See Greenfield, 880 F.3d at 98.\n\n\n - 21 -\n\ncompliance with the AKS was material to the government's decision\n\nto pay any specific claim. This construction inescapably follows\n\nfrom the statute's plain language stating that a claim resulting\n\nfrom a violation of the AKS \"constitutes a false or fraudulent\n\nclaim.\" 42 U.S.C. § 1320a-7b(g). The statute's use of the term\n\n\"constitutes\" would be meaningless if courts had to engage in a\n\nmateriality analysis -- for example, by inquiring into whether the\n\nentity submitting the claim had certified its compliance with the\n\nAKS -- after establishing that a claim resulted from an AKS\n\nviolation. See, e.g., United States v. Catholic Health\n\nInitiatives, 312 F. Supp. 3d 584, 594 (S.D. Tex. 2018) (\"Due to\n\n[§ 1320a–7b(g)], liability under the FCA for AKS violations does\n\nnot require the defendants to have expressly certified their\n\ncompliance with the AKS.\"); United States ex rel. Kester v.\n\nNovartis Pharm. Corp., 43 F. Supp. 3d 332, 364 (S.D.N.Y. 2014)\n\n(stating that \"from and after [the AKS amendment,] the act of\n\nsubmitting a claim . . . itself implie[d] compliance with the AKS,\n\neven in [the] absence of any express certification of compliance.\"\n\n(second alteration in original) (internal quotation marks and\n\ncitation omitted)).\n\n Our reading of § 1320a-7b(g) is consistent with the\n\nlegislative history, which indicates Congress's intent to \"ensure\n\nthat all claims resulting from illegal kickbacks are 'false and\n\nfraudulent'\" and to \"strengthen [] whistleblower actions based on\n\n\n - 22 -\n\nmedical care kickbacks . . . [b]y making all claims that stem from\n\nan illegal kickback subject to the False Claims Act.\" 155 Cong.\n\nRec. S10852-01, S10853 (daily ed. Oct. 28, 2009) (statement of\n\nSen. Kaufman). If a plaintiff must plead and prove that compliance\n\nwith the AKS was \"material\" to a claim \"resulting from\" an AKS\n\nviolation, § 1320a-7b(g) would not represent the strengthening of\n\nwhistleblower actions that Congress intended. Moreover,\n\n§ 1320a-7b(g)'s obviation of the \"materiality\" inquiry essentially\n\ncodifies the long-standing view that AKS violations are \"material\"\n\nin the FCA context.12 This codification has the benefit, however,\n\nof bypassing judicially created theories of materiality, such as\n\nexpress or implied certification, that \"do more to obscure than\n\n\n 12 Prior to the 2010 AKS amendment, courts had consistently\nheld that compliance with the AKS (or the lack thereof) was\n\"material\" to the government's decision to pay a given claim based\non the theory that the government's payment was contingent on the\nsubmitting entity's express or implied certification that it had\ncomplied with the AKS. See, e.g., Amgen, 652 F.3d at 110; United\nStates ex rel. Wilkins v. United Health Grp., Inc., 659 F.3d 295,\n314 (3rd Cir. 2011), abrogated on other grounds by Escobar, 136 S.\nCt. 1989; United States v. Rogan, 517 F.3d 449, 452-53 (7th Cir.\n2008); United States ex rel. Westmoreland v. Amgen, Inc., 812 F.\nSupp. 2d 39, 52 (D. Mass. 2011); United States ex rel. Lisitza v.\nJohnson & Johnson, 765 F. Supp. 2d 112, 127-28 (D. Mass. 2011)\n(citing cases). The legislative history suggests that the 2010\namendment was intended to codify the link between AKS violations\nand false claims within the meaning of the FCA as well as to\ncorrect one district court case holding that claims for payment\nresulting from AKS violations could be \"laundered\" if the claims\nwere submitted to the government by a party who was unaware that\na kickback had occurred. See 155 Cong. Rec. S10852-01, S10853-54\n(daily ed. Oct. 28, 2009) (statements of Sens. Kaufman and Leahy);\nKester, 41 F. Supp. 3d at 332-35 (discussing the 2010 amendment's\nlegislative history).\n\n\n - 23 -\n\nclarify the issues before\" a court considering an FCA claim.\n\nHutcheson, 647 F.3d at 385–86.\n\n With this understanding of the AKS amendment in mind, we\n\nconsider whether Guilfoile has plausibly pleaded that the concerns\n\nhe raised about the payments to Greene reasonably could have led\n\nto an FCA action. The allegations in the complaint, coupled with\n\nthe reasonable inferences we must draw from them, plausibly pleaded\n\nthat claims for payment were, or were going to be, submitted to\n\nthe government in connection with the Integrated Entity's work\n\nwith the New Jersey hospitals. Specifically, the complaint alleges\n\nthat the Integrated Entity \"regularly bills federal insurance\n\nprograms[,] including[] Medicaid [and] Medicare,\" and that\n\nGuilfoile \"believed the contract with Mr. Green[e] violated the\n\nfederal AKS because the Integrated Entity had paid illegal\n\nkickbacks to secure a contract at hospitals where it billed to\n\nfederal insurance programs.\" (Emphasis added.) These allegations\n\nsupport the reasonable inference that the government was being\n\nbilled for services provided by the Integrated Entity in connection\n\nwith its contracts with the hospitals.\n\n Guilfoile has also plausibly alleged a sufficient causal\n\nconnection between any submitted claims and the payments to Greene.\n\nSpecifically, the complaint alleges that the Integrated Entity\n\nentered into an agreement to pay Greene\n\n\"for each hospital contract that [he] successfully referred to the\n\n\n - 24 -\n\nIntegrated Entity, specifically targeting two hospitals that [he]\n\nwas working for as a paid consultant\"; that the Integrated Entity\n\nentered into contracts with those two hospitals; and that the\n\nIntegrated Entity in fact paid him \"referral fees.\" The allegation\n\nthat Greene was paid pursuant to the agreement supports the\n\nreasonable inference that Greene was responsible for connecting\n\nthe Integrated Entity with the New Jersey hospitals. In other\n\nwords, we reasonably infer from the complaint's allegations that\n\nthe Integrated Entity paid Greene to induce him to use his position\n\nwith the hospitals to influence them to select the Integrated\n\nEntity for the contracts at issue. Further, the complaint permits\n\nthe reasonable inference that, if not for the agreement with\n\nGreene, the Integrated Entity would not have been in a position to\n\nbenefit from federal health care payments arising from its work\n\nwith the hospitals. See supra 5-6.13\n\n Finally, Guilfoile has plausibly alleged that the\n\npayments to Greene were a violation of the AKS. The relationship\n\nbetween the Integrated Entity and Greene -- payment to induce the\n\n\n 13 In addition to the allegation that Greene was paid for\nreferring the hospitals to the Integrated Entity, the complaint\nalleges that Greene advised the Integrated Entity on how to bid\nfor the hospital contracts. Contrary to the suggestion by\nappellees, and drawing all reasonable inferences in Guilfoile's\nfavor, we simply do not read the complaint to allege that the\nextent of Greene's assistance to the Integrated Entity was\nproviding insider information about the hospitals' bidding\nprocess.\n\n\n\n - 25 -\n\ngeneration of federal health care program business -- has the\n\nhallmarks of a kickback scheme. See 42 U.S.C. § 1320a-7b(b)(2)(B)\n\n(criminalizing payments to \"induce [a] person . . . to . . .\n\nrecommend purchasing, leasing, or ordering any good, facility,\n\nservice, or item for which payment may be made in whole or in part\n\nunder a [f]ederal health care program\"). Importantly, the nature\n\nof the alleged scheme is materially indistinguishable from the\n\nscheme in United States v. Bay State Ambulance & Hospital Rental\n\nService, Inc., 874 F.2d 20 (1st Cir. 1989), which involved a\n\ncriminal conviction under the AKS. In Bay State, a hospital\n\nemployee, who was on an advisory committee charged with advising\n\nthe hospital on accepting bids for an ambulance services contract,\n\nwas paid by an ambulance company to induce him to recommend that\n\nthe hospital enter into a contract for ambulance services with\n\nthat company. See 874 F.2d at 22. There was no allegation that\n\nthe hospital employee was paid to refer individual patients for\n\nindividual ambulance trips or that the federal government would\n\npay the hospital simply for entering into the contract with the\n\nambulance company, which contract was the direct outcome of the\n\nillegal remuneration scheme. Yet, we held that a crime had\n\noccurred under the AKS once the person who was in a position to\n\ninfluence the hospital was paid to use his influence to win the\n\ncontract for the ambulance company. See id.\n\n\n\n\n - 26 -\n\n The dissent's concern with the \"attenuated\" nature of\n\nthe AKS scheme alleged in the complaint is misplaced.14 First,\n\nalthough we can see how our colleague drew his interpretation from\n\nthe language of the AKS, we are bound by Bay State, as the dissent\n\nrecognizes. Appellees point to no authority for the contention\n\nthat the AKS scheme as pleaded is materially distinguishable from\n\nthe scheme in Bay State and outside the compass of the AKS. The\n\ndissent's attempt to factually distinguish Bay State is also\n\nunconvincing. Any suggestion in the dissent that the nature of\n\nthe kickback scheme is more speculative than the scheme in Bay\n\nState fails to adequately recognize the difference between\n\npleading standards for an FCA retaliation claim, at issue here,\n\nand standards of proof for a criminal conviction under the AKS, at\n\nissue in Bay State. Second, but equally as important, this case\n\ngives us no reason to question Bay State. The type of scheme\n\nproven in Bay State and alleged in the present case is in the\n\nheartland of what the AKS is intended to prevent -- the use of\n\npayments to improperly influence decisions on the provision of\n\n\n 14As our dissenting colleague articulates his concern:\n\"There is . . . a fair amount of attenuation between the actual\ntransactions that Greene was allegedly induced to 'arrange for'\n(the hospitals' 'purchas[es]' or 'order[s]' of the Integrated\nEntity's general pharmacy services) and the transactions 'for\nwhich payment may be made . . . under a Federal health care program'\n(some unknown purchases from an Integrated Entity-run pharmacy of\nsome unknown drugs by some unknown patients who happened to be\neligible for reimbursement under a federal health care program).\"\n\n\n\n - 27 -\n\nhealth care that lead to claims for payment to federal health care\n\nprograms.15 Accepting our colleague's contention -- that there is\n\ntoo great a distance between the Integrated Entity's payments to\n\nGreene to capture the hospital contracts and the submission of\n\nclaims to federal insurance programs, which is the unmistakable\n\nobjective of the contracts -- would leave a hole in the statutory\n\nscheme and essentially permit pay-offs to capture federal health\n\ncare funds. See OIG Supplemental Guidance, 70 Fed. Reg. at 4864\n\n(an illegal kickback is a payment whose purpose, at least in part,\n\nis \"to induce or reward the referral or recommendation of business\n\npayable in whole or in part by a [f]ederal health care program\").\n\n Further, we disagree with our dissenting colleague that\n\nour interpretation of the FCA and the AKS, and our application of\n\nthe statutory language to the alleged facts in light of our\n\nprecedent, is foreclosed by the manner in which Guilfoile presented\n\n\n\n\n 15 We also disagree with the dissent that we should consider\nhere arguments not raised in Bay State that would challenge the\nviability of that decision. Unlike in United States v. DiPina,\n178 F.3d 68, 73 (1st Cir. 1999), where we acknowledged that we are\nnot bound by dicta in a prior opinion, accepting the appellees'\narguments about attenuation in this case would mean that the\nholding in Bay State was incorrect and that the case was therefore\nwrongly decided. The similar facts in Bay State and this case are\nnot \"background facts.\" They are facts that implicate the\napplicability of the AKS in both cases. It is a fundamental\nprinciple that a newly constituted appellate panel cannot overrule\na prior panel in the absence of newly announced Supreme Court law,\nan intervening en banc opinion of this court, a statutory\noverruling, or developments in the law. See Lassend v. United\nStates, 898 F.3d 115, 124-25 & n.6 (1st Cir. 2018).\n\n\n - 28 -\n\nhis arguments before us or before the district court. This is not\n\na case where an appellant has tried to introduce on appeal an issue\n\nthat was never before the district court or to otherwise \"sand\n\nbag\" the other side. Although Guilfoile may not have consistently\n\nraised certain arguments, the core issue of whether the payment\n\nscheme as pleaded falls within the compass of the AKS was before\n\nthe district court and is at the core of his appeal. Before the\n\ndistrict court and before us, Guilfoile consistently argued that\n\nhe has adequately alleged an AKS violation for purposes of pleading\n\nan FCA retaliation claim. The fact that he did not rely on Bay\n\nState or did not consistently present a \"market access\" theory to\n\nsupport the AKS violation in no way precludes us from reaching our\n\nresult. In the context of a de novo review necessitating our\n\ninterpretation of a statute, we routinely employ rationales that\n\nhave been less than satisfactorily presented by the parties if\n\nthat is the correct way of resolving the issue under the applicable\n\nlaw. We cannot allow our responsibility to articulate the most\n\nsensible resolution of an issue, especially, as here, an issue of\n\nstatutory interpretation involving our own precedent, to be\n\nunreasonably circumscribed by the parties' arguments.\n\n Hence, in summary, after drawing all reasonable\n\ninferences in Guilfoile's favor and considering the effect of the\n\nstatutory language drawing a connection between AKS violations and\n\nFCA actions, we conclude Guilfoile has plausibly pleaded that he\n\n\n - 29 -\n\nengaged in protected conduct within the meaning of an FCA\n\nretaliation claim. That is, when Guilfoile raised concerns about\n\nthe payments to Greene he was engaging in conduct that \"reasonably\n\ncould lead to an FCA action,\" Booker, 847 F.3d at 59 (internal\n\nquotation marks omitted), specifically, an FCA action based on the\n\nsubmission of claims resulting from an AKS violation.16\n\n In view of its conclusion that Guilfoile had not\n\nadequately pleaded that he engaged in protected conduct, the\n\ndistrict court did not go on to analyze the other two elements of\n\nGuilfoile's FCA retaliation claim: specifically, that (1) his\n\nemployer knew that he was engaged in protected conduct and (2) his\n\nemployer retaliated against him because of that conduct. See\n\nKarvelas, 360 F.3d at 235. However, we readily conclude that\n\nGuilfoile has plausibly alleged that the Integrated Entity knew\n\nthat he was engaging in protected conduct. Guilfoile specifically\n\n\n\n\n 16 Many of the cases cited by appellees for the proposition\nthat the complaint does not adequately plead an FCA retaliation\nclaim are clearly inapposite because they apply standards for\ndirectly pleading violations of the AKS and FCA, see, e.g., United\nStates ex rel. Kalec v. NuWave Monitoring, LLC, 84 F. Supp. 3d 793\n(N.D. Ill. 2015); standards for proving AKS and FCA claims on\nsummary judgment, see, e.g., United States ex rel. Perales v. St.\nMargaret's Hosp., 243 F. Supp. 2d 843 (C.D. Ill. 2003); standards\nfor assessing criminal conviction under the AKS, see, e.g., Patel,\n778 F.3d 607; or standards for evaluating FCA retaliation claims\nthat we do not follow, see, e.g., United States ex rel. Uhlig v.\nFluor Corp., 839 F.3d 628, 635 (7th Cir. 2016). The case of United\nStates ex rel. Rost v. Pfizer, Inc., 736 F. Supp. 2d 367 (D. Mass.\n2010), predates the 2010 amendment to the AKS and applies an\noutmoded theory of implied certification.\n\n\n - 30 -\n\nalleged that \"he notified Mr. Shields . . . that he believed the\n\ncontract with Mr. Green[e] violated the federal AKS because the\n\nIntegrated Entity had paid illegal kickbacks to secure a contract\n\nat hospitals where it billed federal insurance programs.\"\n\n Guilfoile also has plausibly pleaded that he was\n\nretaliated against because of his protected conduct, given the\n\nclose temporal proximity -- about a week -- of his termination to\n\nhis final conversation with Shields about the payments to Greene.\n\nSee Harrington v. Aggregate Indus. Ne. Region, Inc., 668 F.3d 25,\n\n32 (1st Cir. 2012) (suggesting that a plaintiff can satisfy the\n\nthird element of a prima facie retaliation case by plausibly\n\npleading temporal proximity where the retaliatory action occurred\n\ntwo months after the protected conduct). To the extent appellees\n\ncontend that the complaint does not adequately allege that\n\nGuilfoile informed Shields that he was concerned about fraud on\n\nthe government, see, e.g., McKenzie v. BellSouth Telecomms., Inc.,\n\n219 F.3d 508, 516 (6th Cir. 2000), we disagree. The complaint\n\nexplicitly alleges, for example, that Guilfoile \"notified []\n\nShields . . . that he believed the contract with [] Green[e]\n\nviolated the federal AKS because the Integrated Entity had paid\n\nillegal kickbacks to secure a contract at hospitals where it billed\n\nto federal insurance programs.\"\n\n\n\n\n - 31 -\n\nB. The 24/7 Call Center\n\n We agree with the district court that Guilfoile has not\n\nsufficiently pleaded a connection between the 24/7 call center\n\ncontractual terms and the submission of any claim.17 In general,\n\n\"[i]t is not the case that any breach of contract, or violation of\n\nregulations or law, or receipt of money from the government where\n\none is not entitled to receive the money, automatically gives rise\n\nto a claim under the FCA.\" United States ex rel. Hopper v. Anton,\n\n91 F.3d 1261, 1265 (9th Cir. 1996). Even in the FCA retaliation\n\ncontext, there must be a reasonable connection between the alleged\n\nconduct and the submission of claims within the purview of the\n\nFCA.\n\n For a plaintiff to adequately plead that a contractual\n\nbreach could reasonably lead to an FCA action, he or she must\n\n\n\n\n 17 Anticipating this possible outcome of our review,\nGuilfoile asserts that the district court erred by twice rejecting\nhis requests to amend the complaint to correct any pleading\ndeficiencies. But he has not demonstrated that the court abused\nits discretion and committed a manifest error of law in denying\nhis motion to vacate the judgment and amend the complaint. See\nMarkel Am. Ins. Co. v. Díaz-Santiago, 674 F.3d 21, 32 (1st Cir.\n2012) (stating that we \"review[] the district court's denial of\npost-judgment relief under Rule 59(e) for abuse of discretion,\"\nand that, \"[g]enerally, to prevail on a Rule 59(e) motion, the\nmoving party must . . . clearly establish a manifest error of law.\"\n(internal quotation marks omitted)); Maldonado v. Dominguez, 137\nF.3d 1, 11 (1st Cir. 1998) (\"[A] district court cannot allow an\namended pleading where a final judgment has been rendered unless\nthat judgment is first set aside or vacated pursuant to Fed. R.\nCiv. P. 59 or 60.\").\n\n\n\n - 32 -\n\nadequately plead causation and materiality. See D'Agostino v.\n\nev3, Inc., 845 F.3d 1, 7-8 (1st Cir. 2016). With respect to the\n\n24/7 call center contractual term, Guilfoile has not pleaded any\n\nplausible connection between the alleged contractual breach and\n\nthe submission of claims to the government, or how the contractual\n\nbreach would have been material to the payment of any claims. For\n\nthis reason, the district court correctly dismissed Guilfoile's\n\nFCA retaliation claim to the extent it relied on his activities\n\nconcerning the 24/7 call center.18\n\n IV.\n\n For the foregoing reasons, we affirm dismissal of the\n\ncomplaint as to the 24/7 call center issue but vacate and remand\n\nas to the retaliation claim involving a potential violation of the\n\nAnti-Kickback Statute. Given this disposition, the district court\n\nmay need to reconsider its decision to decline supplemental\n\njurisdiction over Guilfoile's state law claims.\n\n So ordered. Costs to appellant.\n\n - Concurring and Dissenting Opinion Follows -\n\n\n 18Our reasoning and conclusion would be the same if Guilfoile\nhad alleged that the Integrated Entity violated any statute or\nregulation by not having a 24/7 call center or by falsely stating\nin its contracts that it had a 24/7 call center. See Booker, 847\nF.3d at 60. However, we do not read the complaint to plausibly\nallege that the Integrated Entity violated any statutes or\nregulations despite Guilfoile's subjective belief that the alleged\nfalse representation \"posed a serious threat to public health and\nsafety.\"\n\n\n\n - 33 -\n[END_CASE]", "role": "user" } ]
4,582,212
SCOTTSDALE INSURANCE COMPANY, Plaintiff, Appellant, v. Timothy L. BYRNE, as Co-Chairman of the Board of Trustees for the Plumbers and Pipefitters Local 51 Pension and Annuity Funds; Robert Bolton, as Co-Chairman of the Board of Trustees for the Plumbers and Pipefitters Local 51 Pension and Annuity Funds, Defendants, Appellees.
Scottsdale Insurance Company v. Byrne
2019-01-16
18-1526P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Barron", "parties": "", "opinions": [{"author": "STAHL, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1526\n\n SCOTTSDALE INSURANCE COMPANY,\n\n Plaintiff, Appellant,\n\n v.\n\n TIMOTHY L. BYRNE, as Co-Chairman of the Board of Trustees for\nthe Plumbers and Pipefitters Local 51 Pension and Annuity Funds;\n ROBERT BOLTON, as Co-Chairman of the Board of Trustees for the\n Plumbers and Pipefitters Local 51 Pension and Annuity Funds,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. F. Dennis Saylor, IV, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Alexis J. Rogoski, with whom Edward C. Carleton and Skarzynski\nBlack LLC were on brief, for appellant.\n Miranda S. Jones, with whom O'Reilly, Grosso, Gross & Jones,\nP.C. was on brief, for appellee.\n\n\n January 16, 2019\n\f STAHL, Circuit Judge. In late 2014, the appellees in\n\nthis case brought suit against Wellesley Advisory Reality Fund I,\n\nLLC (\"WARF\"). Acting in their capacity as representatives of the\n\nBoard of Trustees for the Plumbers and Pipefitters Local 51 Pension\n\nand Annuity Funds (the \"Funds\"), Appellees alleged that WARF had\n\nmismanaged and squandered money that the Funds had invested in\n\nthat entity. Following entry of default judgment against WARF in\n\nthat case, WARF assigned the Funds its rights in WARF's insurance\n\npolicy with Appellant Scottsdale Insurance Company (\"Scottsdale\"),\n\nwhich had declined to defend WARF on the basis of several\n\nexceptions within the policy.\n\n Scottsdale brought an action against Appellees seeking\n\na declaration that it did not owe WARF a duty to defend or indemnify\n\nunder the policy and so owed the Funds nothing, and the Funds\n\ncounterclaimed. On cross-motions for summary judgment, the United\n\nStates District Court for the District of Massachusetts ruled that\n\nthe exclusions in Scottsdale's policies did not relieve the insurer\n\nof its duty to defend WARF in the prior action. In a subsequent\n\norder, the district court awarded the Funds $3 million, the full\n\nlimits of the insurance policy, plus post-judgment interest.\n\n Scottsdale appeals, arguing both that it did not breach\n\nits duty to defend under the policy under Massachusetts law and\n\nthat, even if it did, damages should be limited to the costs of\n\nthe defense. After careful consideration, we affirm.\n\n\n - 2 -\n\f I.\n\n A. The Policy\n\n The dispute in this appeal stems from a \"Business and\n\nManagement Indemnity Policy\" (the \"Policy\") issued by Scottsdale\n\nto WARF, a real estate investment vehicle developed by Wellesley\n\nAdvisors.1 The Policy covered the period from November 15, 2013,\n\nto December 15, 2014,2 and carries a coverage limit of $3 million.\n\nThe Policy contains the following coverage clauses:\n\n 1. The Insurer shall pay the Loss of the\n Management Insureds for which the Management\n Insureds are not indemnified by the [Company\n and] which the Management Insureds have become\n legally obligated to pay by reason of a Claim\n first made against the Management Insureds\n during the Policy Period . . . and reported to\n the Insurer . . . for any Wrongful Act taking\n place prior to the end of the Policy Period.\n\n 2. The Insurer shall pay the Loss of the\n Company for which the Company has indemnified\n the Management Insureds and which the\n Management Insureds have become legally\n obligated to pay by reason of a Claim first\n [made against] the Management Insureds during\n the Policy Period . . . and reported to the\n Insurer . . . for any Wrongful Act taking place\n prior to the end of the Policy Period.\n\n 3. The Insurer shall pay the Loss of the\n Company which the Company becomes legally\n\n\n 1 The Policy names Wellesley Advisors as the insured, and\nexplicitly added WARF as an insured \"parent company\" in an\nendorsement dated November 15, 2013. The parties do not dispute\nthat WARF was an insured under the Policy.\n 2 Initially, the policy period was set to expire on November\n15, 2014. Scottsdale and WARF subsequently extended this period\nby one month.\n\n\n - 3 -\n\f obligated to pay by reason of a [Claim first]\n made against the Company during the Policy\n Period . . . and reported to the Insurer . . .\n for any Wrongful Act taking place prior to the\n end of the Policy Period.\n\nAs relevant here, the Policy defines \"Claim\" as \"a civil proceeding\n\nagainst any Insured seeking monetary damages or non-monetary or\n\ninjunctive relief . . . .\" \"Loss\" is defined as \"damages,\n\njudgments, settlements, pre-judgment or post-judgment interest\n\nawarded by a court, and Costs, Charges, and Expenses incurred by\"\n\nthe entities covered under the Policy. \"Wrongful Act\" is defined\n\nas \"any actual or alleged error, omission, misleading statement,\n\nmisstatement, neglect, breach of duty or act allegedly committed\n\nor attempted by\" the insured entities.\n\n The Policy contains a number of exclusions, three of\n\nwhich are claimed to be relevant to the present appeal. First,\n\nthe Policy includes a \"Professional Services Exclusion\" which\n\nstates:\n\n Insurer is not liable for Loss . . . on account\n of any Claim[] alleging, based upon, arising\n out of, attributable to, directly or\n indirectly resulting from, in consequence of,\n or in any way involving the rendering or\n failure to render Professional Services. . . .\n\n Solely for purposes of this exclusion,\n Professional Services means services as a real\n estate broker or agent, multiple listing\n agent, real estate appraiser, title agent,\n title abstractor or searcher, escrow agent,\n real estate developer, real estate consultant,\n property manager, real estate inspector, or\n construction manager. Such services shall\n\n\n - 4 -\n\f include, without limitation, the purchase,\n sale, rental, leasing or valuation of real\n property; the arrangement of financing on real\n property; or any advice proffered by an\n Insured in connection with any of the\n foregoing.\n\nSecond, the Policy provides an \"ERISA Exclusion\" which states that\n\nScottsdale\n\n shall not be liable for Loss . . . on account\n of any Claim . . . for any actual or alleged\n violation of the responsibilities,\n obligations or duties imposed by [the]\n Employee Retirement Income Security Act of\n 1974, as amended [\"ERISA\"], or any rules or\n regulations promulgated thereunder, or\n similar provisions of any federal, state or\n local statutory or common law[.]\n\nFinally, the Policy provides a \"Conduct Exclusion\" which excludes\n\ncoverage for\n\n Loss . . . on account of any Claim . . .\n alleging, based upon, arising out of,\n attributable to, directly or indirectly\n resulting from, in consequence of, or in any\n way involving:\n\n . . .\n\n ii. the gaining of any profit, remuneration\n or financial advantage to [which any]\n Management Insureds were not legally entitled;\n provided, however this exclusion [] shall not\n apply unless and until there is a final\n judgment against such Management Insureds as\n to such conduct.\n\n\n\n\n - 5 -\n\f B. The Underlying Action\n\n On November 10, 2014, Appellees filed suit against WARF3\n\nin the United States District Court for the District of\n\nMassachusetts seeking damages and injunctive relief (the\n\n\"Underlying Action\"). Appellees claimed that, in 2005, they\n\ninvested $5 million with WARF, which WARF subsequently used to\n\n\"invest in various real estate parcels . . . .\" Specifically, the\n\ncomplaint avers that WARF purchased \"The Stone House,\" a hotel in\n\nLittle Compton, Rhode Island; a residential condominium called\n\n\"Eastbourne Lodge\" in Newport, Rhode Island; and a housing\n\ndevelopment in North Attleboro, Massachusetts.\n\n As to The Stone House, Appellees averred that WARF\n\nentered into several mortgages on the property to fund renovations\n\ntherein. Appellees claimed that, despite this debt, WARF retained\n\nall revenue from hotel operations at The Stone House as a \"'fee'\n\nfor managing the property for [t]he Funds[].\" WARF failed to make\n\nrequired periodic payments on The Stone House mortgages, and the\n\nmortgagee sued for more than $5.6 million to enforce the mortgages\n\nagainst The Stone House.\n\n\n\n\n 3 The complaint in that action addresses allegations to both\n\"Wellesley Advisors\" and \"Wellesley Advisors Realty Fund I, LLC,\"\nseemingly interchangeably. This appears to be a distinction\nwithout a difference, and the parties do not attach any\nsignificance to that point. Accordingly, we refer to allegations\nas against WARF for clarity.\n\n\n - 6 -\n\f Separately, the complaint averred that \"a sister or\n\nparent company\" of WARF received notice from a different mortgagee\n\nof its intent to foreclose on and sell the North Attleboro property\n\ndue to an unspecified \"breach of the conditions of [that]\n\nmortgage.\"\n\n Through these actions, Appellees averred that WARF\n\n\"squandered the entire [$5 million] investment,\" and that \"[t]he\n\nproperties were either lost to foreclosure or written down to a\n\nzero value because of taxes or mortgages owed.\"\n\n Based on these allegations, the Funds brought two claims\n\nin state court against WARF for negligence and violations of ERISA,\n\nrespectively. Under the first of these claims, the complaint\n\ncontends that WARF was negligent in overleveraging the properties\n\nin excess of their value, failing to pay property taxes, and\n\nretaining income from the investment properties, especially from\n\nThe Stone House, for its own use. The second, ERISA-based count\n\nclaims that, through its retention of revenues from The Stone\n\nHouse, WARF took on fiduciary duties to the Funds, which it\n\nsubsequently violated through \"self-dealing and mismanagement of\n\n[the properties.]\"\n\n WARF notified Scottsdale of the Funds' lawsuits against\n\nit on November 14, 2014. Scottsdale replied verbally (and, later,\n\nin writing) that the Funds' claims were excluded from coverage\n\nbased on the ERISA and Professional Services Exclusions.\n\n\n - 7 -\n\fAccordingly, Scottsdale refused to either defend or indemnify WARF\n\nas to the Funds' claims. WARF went into receivership and did not\n\ncontest the Underlying Action thereafter.\n\n On November 25, 2015, the district court entered default\n\njudgment in the Underlying Action in favor of Appellees, awarding\n\nthem $5,005,422.12.4 On May 15, 2016, WARF assigned to Appellees\n\nall rights and claims that it held against Scottsdale.\n\n C. Procedural History\n\n Scottsdale brought the instant action on July 8, 2016,\n\nin the District Court for the District of Massachusetts, seeking\n\ndeclaratory judgment that Appellees' claims in the Underlying\n\nAction were not covered under the Policy and so that Scottsdale\n\nwas not obligated to make any payments on the judgment in that\n\ncase. Appellees included in their answer several counterclaims,\n\nincluding as relevant here claims that Scottsdale breached its\n\nduty to defend and to indemnify WARF in the Underlying Action.\n\nAppellees sought payment of the entire amount of the judgment in\n\nthe Underlying Action plus post-judgment interest. The parties\n\ncross-moved for summary judgment.\n\n On March 1, 2018, the district court denied Scottsdale's\n\nmotion and granted partial summary judgment to Appellees. The\n\ncourt found that the allegations raised in the Underlying Action\n\n\n 4\n This amount includes both the principal amount claimed\n($5 million) as well as costs and attorneys' fees.\n\n\n - 8 -\n\fwere not \"clearly excluded\" from coverage under the policy and so\n\nScottsdale had, at minimum, a duty to defend WARF against those\n\nclaims. Based on Scottsdale's uncontested failure to take up\n\nWARF's legal defense in the Underlying Action, the court concluded\n\nthat Scottsdale was liable to Appellees and required the parties\n\nto file \"motions concerning the form of the judgment,\" which it\n\nsaid would \"[p]resumably . . . be awarded [in] the amount of the\n\ncoverage limit.\" After the parties submitted the required\n\nmotions,5 the court entered judgment for Appellees on May 8, 2015,\n\nin the amount of $3,038,081.10, consisting of the policy limit of\n\n$3 million plus post-judgment interest calculated at the statutory\n\nrate. Scottsdale timely appealed the district court's judgment.\n\n II.\n\n On appeal, Scottsdale argues that the district court\n\nerred in concluding that it had a duty to defend the Underlying\n\nAction. It points to the Policy's Professional Services and ERISA\n\nExclusions, contending that each of those exclusions clearly\n\napplies to the claims asserted in the Underlying Action and\n\n\n\n 5\n In its motion, Scottsdale also moved for clarification of\nthe summary judgment order, seeking dismissal of Appellees'\ncounterclaims for breaches of the implied covenant of good faith\nand fair dealing, and violation of the Massachusetts consumer\nprotection statute, which the district court initially failed to\naddress. Appellees, on the other hand, sought entry of judgment\nin the full amount of damages in the Underlying Action. The court\ndismissed the remaining claims and denied the motion for damages\nin excess of the policy limit plus interest.\n\n\n - 9 -\n\findependently provides a basis for denying coverage. In the\n\nalternative, Scottsdale contends that it is only liable for the\n\ncosts of defending the Underlying Action —— not the entire policy\n\nlimit —— because the claims are excluded by the Policy's Conduct\n\nExclusion. We examine these arguments separately and find no\n\nreason to reverse the district court's determination.\n\n A. Standard of Review\n\n Review of the district court's grant of summary judgment\n\nis de novo. Barrett Paving Materials, Inc. v. Continental Ins.\n\nCo., 488 F.3d 59, 63 (1st Cir. 2007). Where, as here, there is no\n\ndispute regarding the material facts, the only issue is whether\n\nthe moving party is entitled to judgment as a matter of law. Id.\n\n(citation omitted).\n\n This case comes before us based on our diversity\n\njurisdiction, and the parties agree that Massachusetts provides\n\nthe substantive law to be applied. \"The interpretation of an\n\ninsurance policy is a question of law for the court.\" Valley Forge\n\nIns. Co. v. Field, 670 F.3d 93, 97 (1st Cir. 2012) (citation\n\nomitted). \"Under Massachusetts law, [the court] construe[s] an\n\ninsurance policy under the general rules of contract\n\ninterpretation. . . . begin[ning] with the actual language of the\n\npolicies, given its plain and ordinary meaning.\" Brazas Sporting\n\nArms, Inc. v. Am. Empire Surplus Lines Ins. Co., 220 F.3d 1, 4\n\n(1st Cir. 2000) (citations omitted).\n\n\n - 10 -\n\f The \"insurer's duty to defend is independent from, and\n\nbroader than, its duty to indemnify,\" Metro. Prop. & Cas. Ins. Co.\n\nv. Morrison, 951 N.E.2d 662, 667 (Mass. 2011) (internal quotation\n\nmarks and citation omitted), and insurers \"owe[] a duty to defend\n\n[their insured] if the allegations in the underlying lawsuit are\n\nreasonably susceptible to an interpretation that they state a claim\n\ncovered by [the] policy,\" Scottsdale Ins. Co. v. Torres, 561 F.3d\n\n74, 77 (1st Cir. 2009) (citation omitted); see also Billings v.\n\nCommerce Ins. Co., 936 N.E.2d 408, 414 (Mass. 2010) (\"An insurer\n\nhas a duty to defend an insured when the allegations in a complaint\n\nare reasonably susceptible of an interpretation that states or\n\nroughly sketches a claim covered by the policy terms.\" (footnote\n\nand citation omitted)). Said somewhat differently, \"[i]n order\n\nfor the duty of defense to arise, the underlying complaint need\n\nonly show, through general allegations, a possibility that the\n\nliability claim falls within the insurance coverage. There is no\n\nrequirement that the facts alleged in the complaint specifically\n\nand unequivocally make out a claim within the coverage.\" Sterilite\n\nCorp. v. Cont'l Cas. Co., 458 N.E.2d 338, 341 (Mass. App. Ct. 1983)\n\n(internal quotation marks and citation omitted). Courts look to\n\n\"the source from which the plaintiff's personal injury originates\n\nrather than the specific theories of liability alleged in the\n\ncomplaint\" to determine whether the policy covers the claim under\n\nthis standard. Bagley v. Monticello Ins. Co., 720 N.E.2d 813, 817\n\n\n - 11 -\n\f(Mass. 1999) (internal quotation marks, citation, and emphasis\n\nomitted).\n\n Where, as here, an insurer asserts that it is not\n\nobligated to defend due to some policy exclusion or exclusions, it\n\nbears the initial burden of demonstrating that the exclusion\n\napplies.6 See Saint Consulting Grp., Inc. v. Endurance Am. Spec.\n\nIns. Co., Inc., 699 F.3d 544, 550 (1st Cir. 2012) (citation\n\nomitted). In order to meet this requirement, \"the facts alleged\n\nin the third-party complaint must establish that the exclusion\n\napplies to all potential liability as matter of law.\" Norfolk &\n\nDedham Mut. Fire Ins. Co. v. Cleary Consultants, Inc., 958 N.E.2d\n\n853, 862 (Mass. App. Ct. 2011) (citation omitted); see also Saint\n\nConsulting Grp., 699 F.3d at 550 (\"If even one of the counts in\n\neither of the complaints falls within the coverage provisions but\n\noutside any exclusion, [the insurer] would have a duty to defend\n\nthe entire lawsuit.\"). \"[W]hether an exclusion applies to relieve\n\nan insurer of its duty to defend [] depend[s] on whether the\n\ninsured would have reasonably understood the exclusion to bar\n\n\n\n\n 6 Generally, the insured bears the initial burden of \"showing\nthat the overall coverage provisions of the insurance policy\napply[.]\" Clark Sch. for Creative Learning, Inc. v. Phila. Indem.\nIns. Co., 734 F.3d 51, 55 n.1 (1st Cir. 2013). Where, as here,\nthe dispute centers only on the effect of coverage exclusions, the\ncourt can bypass this initial showing and proceed directly to\nevaluating the reach of those exclusions. See id. at 55.\n\n\n - 12 -\n\fcoverage.\" Essex Ins. Co. v. BloomSouth Flooring Corp., 562 F.3d\n\n399, 404 (1st Cir. 2009).\n\n B. The Professional Services Exclusion\n\n Scottsdale first contends that all of the allegations in\n\nthe Underlying Action fall within the purview of the Professional\n\nServices Exclusion. In particular, it contends that all of the\n\nallegations in that case \"arose out of\" or \"involved\" \"real estate\n\ndevelopment, property management, the purchase of real property,\n\nor the arrangement of financing on real property,\" all of which\n\nScottsdale argues fall \"within the plain meaning of the\n\nProfessional Services Exclusion.\" In support of this position,\n\nScottsdale relies on the broad readings afforded by Massachusetts\n\nlaw to the terms \"arising out of\" and \"in any way involving,\" both\n\nof which are used to preface the substantive scope of the\n\nProfessional Services Exclusion (as well as the other relevant\n\nexclusions). See Bagley, 720 N.E.2d at 816 (explaining that the\n\nphrase \"arising out of\" \"must be read expansively, incorporating\n\na greater range of causation than that encompassed by proximate\n\ncause under tort law\" (citations omitted)); Clark Sch. for Creative\n\nLearning, 734 F.3d at 56 (holding that \"in any way involving\" acts\n\nas a \"mop-up clause, intended to exclude anything not already\n\nexcluded by the other clauses,\" including \"arising out of\").\n\n Scottsdale's argument fails, however, to account for all\n\nof the claims raised in the Underlying Action. As noted above,\n\n\n - 13 -\n\fthe Underlying Action concerned losses stemming from WARF's\n\ninvestment in three properties: The Stone House, and properties in\n\nNorth Attleboro and Newport. Were those allegations limited to\n\nclaims regarding the mismanagement of The Stone House, we might\n\nagree: claims stemming from WARF's renovation of that property and\n\nretention of revenues from its operation of the hotel as a\n\n\"management\" fee fit seemingly well within the exclusion for\n\nactions taken \"as a . . . real estate developer [or] . . . property\n\nmanager.\" As Appellees observed at oral argument, however, the\n\ncomplaint offers no similar allegations that WARF was developing,\n\nimproving, or managing operations at the investment properties in\n\nNorth Attleboro or Newport. Beyond alleging that WARF invested in\n\nthose parcels, the only additional claims are that the properties\n\nwere \"lost to foreclosure or written down to a zero value because\n\nof tax or mortgages owed\" and, generally, that WARF \"engaged in\n\nself-dealing by retaining investment income from the properties\n\nfor its own use.\" These limited allegations preclude any\n\nmeaningful evaluation of whether the loss of the Newport and North\n\nAttleboro properties was attributable to WARF's actions as a\n\nproperty manager, developer, investor, or otherwise. As the\n\ndistrict court observed, \"[a]t the very least, it is ambiguous\n\nwhether in fact all of WARF's purported misconduct stemmed from\"\n\nWARF's provision of professional services. Thus, the allegations\n\nconcerning the Newport and North Attleboro properties are not\n\n\n - 14 -\n\fclearly within the Professional Services Exclusion, and, where\n\nthere is ambiguity, there is a duty to defend.\n\n Scottsdale attempts to argue around this shortcoming,\n\nclaiming that all of the allegations fall within the broad\n\ndefinition of \"services\" —— especially the \"arrangement of\n\nfinancing on real property\" —— included in the Professional\n\nServices Exclusion. Scottsdale misreads its own policy, however:\n\nthe plain language of the Policy is clear that, in order to fall\n\nwithin the Professional Services Exclusion, the \"services\" as\n\ndefined must be provided \"as a real estate broker or agent,\"\n\n\"property manager,\" or another of that exclusion's enumerated\n\nroles. As noted above, the allegations set forth in the Underlying\n\nAction do not offer any meaningful basis from which we can conclude\n\nthat WARF was acting in any one of those roles with respect to\n\neither the North Attleboro or Newport properties.\n\n We therefore conclude that Scottsdale failed to meet its\n\nburden of establishing that the Professional Services Exclusion\n\napplies to all claims of liability within the Underlying Action.\n\n C. The ERISA Exclusion\n\n Scottsdale next turns to the ERISA Exclusion. As\n\ndiscussed, the Underlying Action asserted both a negligence claim\n\nand, separately, a claim that WARF's actions violated duties\n\nimposed by ERISA. The parties do not dispute that the latter of\n\nthese claims falls outside of the Policy's coverage, and that count\n\n\n - 15 -\n\fis not at issue here. Scottsdale goes a step further, however,\n\ncontending that because the negligence and ERISA claims arise from\n\nthe same set of facts, the negligence claim is therefore preempted\n\nby ERISA.\n\n At the outset, we note that none of the categories of\n\nexcluded \"Claims\" —— \"actual or alleged violations\" of (1) ERISA;\n\n(2) \"rules or regulations promulgated\" pursuant to ERISA; or (3)\n\n\"similar provisions of federal, state or local statutory or common\n\nlaw\" —— explicitly remove \"preempted\" state law claims from the\n\nPolicy's coverage. Recognizing this shortcoming, Scottsdale\n\nattempts to shoehorn preempted state-law claims into this clause\n\nas a \"similar provision[] of . . . state . . . common law.\" In\n\nour view, however, the question of whether that language could\n\nextend to a common law action for negligence, stated without\n\nreference to ERISA-like fiduciary duties, is ambiguous at best.\n\nThat observation alone settles the issue before us: Scottsdale has\n\nthe burden of demonstrating the exclusion's application to the\n\nUnderlying Action, and all ambiguities must be read against the\n\ninsurer. See Valley Forge Ins. Co., 670 F.3d at 97. Accordingly,\n\nwe see no basis for excusing Scottsdale from its duty to defend\n\nbased on the ERISA Exclusion.7\n\n\n\n\n 7 Because we find that neither of the exclusions cited by\nScottsdale excuse it from its duty to defend, we do not reach\nAppellees' alternate argument that, under its terms, the Policy's\n\n\n - 16 -\n\f D. The Conduct Exclusion\n\n In its final argument, Scottsdale contends that its\n\nliability is limited by the Policy's Conduct Exclusion. Unlike\n\nthe Professional Services and ERISA Exclusions, Scottsdale does\n\nnot claim that the Conduct Exclusion excuses it from its duty to\n\ndefend: by its terms, that exclusion is not implicated \"unless\n\nand until there is a final judgment against [the] . . . Insureds\n\n. . . .\" Rather, Scottsdale contends that, even if it breached\n\nthe duty to defend, it should be permitted to contest and limit\n\nits indemnity obligation based on that exclusion's application to\n\nfinancial gains to which WARF was not entitled, specifically WARF's\n\nalleged retention of \"investment income from the properties\" at\n\nissue in the Underlying Action.\n\n An insurer's breach of its duty to defend \"may also\n\ntrigger a duty to indemnify because an insurer in breach of its\n\nduty to defend is bound by the result of the underlying action as\n\nto all matters therein decided which are material to recovery by\n\nthe insured in an action on the policy.\" Metro Prop. & Cas. Ins.,\n\n951 N.E.2d at 669 (internal quotation marks, alterations, and\n\ncitation omitted); see also Liberty Mut. Ins. Co. v. Metro. Life\n\nIns. Co., 260 F.3d 54, 63 (1st Cir. 2001) (\"[T]he general rule\n\nunder Massachusetts law is that if the insurer fails to defend the\n\n\nexclusions do not relieve the insurer of its duty to defend in any\nevent.\n\n\n - 17 -\n\flawsuit, it is liable for all defense costs and (assuming policy\n\ncoverage) the entire resulting judgment or settlement, unless\n\nliability can be allocated among covered and uncovered claims.\")\n\n(citations omitted). \"Where [the insured] defendant defaults, the\n\nfactual allegations in the complaint as to liability are deemed to\n\nbe admitted . . . and treated as if they are true\" as to both the\n\ndefendant and those insurers who wrongfully decline to defend the\n\ncase. Metro. Prop. & Cas. Ins., 951 N.E.2d at 669.\n\n Subject to these provisos, \"insurer[s] that wrongfully\n\ndecline[] to defend a claim\" may contest their indemnity under\n\ntheir policy, provided, however, that they \"have the burden of\n\nproving that the claim was not within [the] policy's coverage.\"\n\nPolaroid Corp. v. Travelers Indem. Co., 610 N.E.2d 912, 922\n\n(Mass. 1993). Moreover, where some of the claims fall within a\n\npolicy's coverage and others do not, \"an insurer that breaches its\n\nduty to defend bears the burden of allocating a judgment against\n\nits insured between covered and noncovered claims.\" Palermo v.\n\nFireman's Fund Ins. Co., 676 N.E.2d 1158, 1163 (Mass. App. Ct.\n\n1997); see also Liquor Liab. Joint Underwriting Ass'n of Mass. v.\n\nHermitage Ins. Co., 644 N.E.2d 964, 968-69 (Mass. 1995).\n\n Similar to the Professional Services Exclusion,\n\nScottsdale's attempt to escape its indemnity obligation fails to\n\naccount for all of the claims made in the Underlying Action.\n\nScottsdale maintains a narrow focus on allegations that WARF\n\n\n - 18 -\n\fengaged in self-dealing when it retained fees from the investment\n\nproperties. Self-dealing, however, is just one component of the\n\nmany allegations in the Underlying Action. Much of the complaint\n\nis concerned not with WARF's improper gain or pecuniary advantage,\n\nbut rather the squandering of Appellees' investment through, among\n\nother things, negligently overleveraging and failing to pay taxes\n\nand service mortgages on the properties.8 Those allegations were\n\n\"conclusively establishe[d]\" by the entry of default as to\n\nScottsdale, Metro. Prop. & Cas. Ins., 951 N.E.2d at 669, and they\n\noffer a theory of Appellees' loss that is entirely separate from\n\nany improper gain by WARF. Scottsdale provides no basis from which\n\nwe could conclude that the Conduct Exclusion covers all of the\n\nmaterial allegations established in the Underlying Action, and it\n\nfurther fails to demonstrate any grounds for allocating the\n\njudgment award between portions attributable to WARF's improper\n\n\n 8 Scottsdale's reliance on Winbrook Communication Services\nInc. v. United States Liability Insurance Company, 52 N.E.3d 195\n(Mass. App. Ct. 2016), is misplaced. There, the insured company's\nnegligent misstatements about its own financial stability induced\nthe judgment creditor to provide a benefit in the form of services\nfor which it was never paid. Id. at 197. Examining a conduct\nexclusion similar to that in the Policy, the court concluded that\nevidence in the record indicated that, through its\nmisrepresentations, the insured might have \"received goods or\nservices that created an opportunity for gain or advantage . . . .\n[such as] credit, investors, or customers.\" Id. at 203. In other\nwords, the insured's negligence might have directly contributed to\nits receipt of an advantage to which it was not legally entitled.\nIn this case, however, we see no basis to conclude that WARF's\nnegligence in squandering Appellees' investment led to any\ndemonstrable gain.\n\n\n - 19 -\n\fgains and negligent losses. As such, we see no basis from which\n\nto relieve Scottsdale of its obligation to pay the policy limit.9\n\n III.\n\n The judgment of the district court is AFFIRMED.\n\n\n\n\n 9 In their opposition brief, Appellees hint that the district\ncourt erred in limiting their recovery to the policy limits, rather\nthan the full judgment. Because Appellees failed to cross-appeal\non that issue, we do not address the merits of their claim. See\nJennings v. Stephens, __ U.S. __, 135 S. Ct. 793, 798 (2015) (\"[A]n\nappellee who does not cross-appeal may not attack the [judgment of\nthe lower court] with a view either to enlarging his own rights\nthereunder or lessening the rights of his adversary.\" (internal\nquotation marks and citation omitted)).\n\n\n - 20 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359465/", "author_raw": "STAHL, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582212/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: SCOTTSDALE INSURANCE COMPANY, Plaintiff, Appellant, v. Timothy L. BYRNE, as Co-Chairman of the Board of Trustees for the Plumbers and Pipefitters Local 51 Pension and Annuity Funds; Robert Bolton, as Co-Chairman of the Board of Trustees for the Plumbers and Pipefitters Local 51 Pension and Annuity Funds, Defendants, Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1526\n\n SCOTTSDALE INSURANCE COMPANY,\n\n Plaintiff, Appellant,\n\n v.\n\n TIMOTHY L. BYRNE, as Co-Chairman of the Board of Trustees for\nthe Plumbers and Pipefitters Local 51 Pension and Annuity Funds;\n ROBERT BOLTON, as Co-Chairman of the Board of Trustees for the\n Plumbers and Pipefitters Local 51 Pension and Annuity Funds,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. F. Dennis Saylor, IV, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Alexis J. Rogoski, with whom Edward C. Carleton and Skarzynski\nBlack LLC were on brief, for appellant.\n Miranda S. Jones, with whom O'Reilly, Grosso, Gross & Jones,\nP.C. was on brief, for appellee.\n\n\n January 16, 2019\n\f STAHL, Circuit Judge. In late 2014, the appellees in\n\nthis case brought suit against Wellesley Advisory Reality Fund I,\n\nLLC (\"WARF\"). Acting in their capacity as representatives of the\n\nBoard of Trustees for the Plumbers and Pipefitters Local 51 Pension\n\nand Annuity Funds (the \"Funds\"), Appellees alleged that WARF had\n\nmismanaged and squandered money that the Funds had invested in\n\nthat entity. Following entry of default judgment against WARF in\n\nthat case, WARF assigned the Funds its rights in WARF's insurance\n\npolicy with Appellant Scottsdale Insurance Company (\"Scottsdale\"),\n\nwhich had declined to defend WARF on the basis of several\n\nexceptions within the policy.\n\n Scottsdale brought an action against Appellees seeking\n\na declaration that it did not owe WARF a duty to defend or indemnify\n\nunder the policy and so owed the Funds nothing, and the Funds\n\ncounterclaimed. On cross-motions for summary judgment, the United\n\nStates District Court for the District of Massachusetts ruled that\n\nthe exclusions in Scottsdale's policies did not relieve the insurer\n\nof its duty to defend WARF in the prior action. In a subsequent\n\norder, the district court awarded the Funds $3 million, the full\n\nlimits of the insurance policy, plus post-judgment interest.\n\n Scottsdale appeals, arguing both that it did not breach\n\nits duty to defend under the policy under Massachusetts law and\n\nthat, even if it did, damages should be limited to the costs of\n\nthe defense. After careful consideration, we affirm.\n\n\n - 2 -\n\f I.\n\n A. The Policy\n\n The dispute in this appeal stems from a \"Business and\n\nManagement Indemnity Policy\" (the \"Policy\") issued by Scottsdale\n\nto WARF, a real estate investment vehicle developed by Wellesley\n\nAdvisors.1 The Policy covered the period from November 15, 2013,\n\nto December 15, 2014,2 and carries a coverage limit of $3 million.\n\nThe Policy contains the following coverage clauses:\n\n 1. The Insurer shall pay the Loss of the\n Management Insureds for which the Management\n Insureds are not indemnified by the [Company\n and] which the Management Insureds have become\n legally obligated to pay by reason of a Claim\n first made against the Management Insureds\n during the Policy Period . . . and reported to\n the Insurer . . . for any Wrongful Act taking\n place prior to the end of the Policy Period.\n\n 2. The Insurer shall pay the Loss of the\n Company for which the Company has indemnified\n the Management Insureds and which the\n Management Insureds have become legally\n obligated to pay by reason of a Claim first\n [made against] the Management Insureds during\n the Policy Period . . . and reported to the\n Insurer . . . for any Wrongful Act taking place\n prior to the end of the Policy Period.\n\n 3. The Insurer shall pay the Loss of the\n Company which the Company becomes legally\n\n\n 1 The Policy names Wellesley Advisors as the insured, and\nexplicitly added WARF as an insured \"parent company\" in an\nendorsement dated November 15, 2013. The parties do not dispute\nthat WARF was an insured under the Policy.\n 2 Initially, the policy period was set to expire on November\n15, 2014. Scottsdale and WARF subsequently extended this period\nby one month.\n\n\n - 3 -\n\f obligated to pay by reason of a [Claim first]\n made against the Company during the Policy\n Period . . . and reported to the Insurer . . .\n for any Wrongful Act taking place prior to the\n end of the Policy Period.\n\nAs relevant here, the Policy defines \"Claim\" as \"a civil proceeding\n\nagainst any Insured seeking monetary damages or non-monetary or\n\ninjunctive relief . . . .\" \"Loss\" is defined as \"damages,\n\njudgments, settlements, pre-judgment or post-judgment interest\n\nawarded by a court, and Costs, Charges, and Expenses incurred by\"\n\nthe entities covered under the Policy. \"Wrongful Act\" is defined\n\nas \"any actual or alleged error, omission, misleading statement,\n\nmisstatement, neglect, breach of duty or act allegedly committed\n\nor attempted by\" the insured entities.\n\n The Policy contains a number of exclusions, three of\n\nwhich are claimed to be relevant to the present appeal. First,\n\nthe Policy includes a \"Professional Services Exclusion\" which\n\nstates:\n\n Insurer is not liable for Loss . . . on account\n of any Claim[] alleging, based upon, arising\n out of, attributable to, directly or\n indirectly resulting from, in consequence of,\n or in any way involving the rendering or\n failure to render Professional Services. . . .\n\n Solely for purposes of this exclusion,\n Professional Services means services as a real\n estate broker or agent, multiple listing\n agent, real estate appraiser, title agent,\n title abstractor or searcher, escrow agent,\n real estate developer, real estate consultant,\n property manager, real estate inspector, or\n construction manager. Such services shall\n\n\n - 4 -\n\f include, without limitation, the purchase,\n sale, rental, leasing or valuation of real\n property; the arrangement of financing on real\n property; or any advice proffered by an\n Insured in connection with any of the\n foregoing.\n\nSecond, the Policy provides an \"ERISA Exclusion\" which states that\n\nScottsdale\n\n shall not be liable for Loss . . . on account\n of any Claim . . . for any actual or alleged\n violation of the responsibilities,\n obligations or duties imposed by [the]\n Employee Retirement Income Security Act of\n 1974, as amended [\"ERISA\"], or any rules or\n regulations promulgated thereunder, or\n similar provisions of any federal, state or\n local statutory or common law[.]\n\nFinally, the Policy provides a \"Conduct Exclusion\" which excludes\n\ncoverage for\n\n Loss . . . on account of any Claim . . .\n alleging, based upon, arising out of,\n attributable to, directly or indirectly\n resulting from, in consequence of, or in any\n way involving:\n\n . . .\n\n ii. the gaining of any profit, remuneration\n or financial advantage to [which any]\n Management Insureds were not legally entitled;\n provided, however this exclusion [] shall not\n apply unless and until there is a final\n judgment against such Management Insureds as\n to such conduct.\n\n\n\n\n - 5 -\n\f B. The Underlying Action\n\n On November 10, 2014, Appellees filed suit against WARF3\n\nin the United States District Court for the District of\n\nMassachusetts seeking damages and injunctive relief (the\n\n\"Underlying Action\"). Appellees claimed that, in 2005, they\n\ninvested $5 million with WARF, which WARF subsequently used to\n\n\"invest in various real estate parcels . . . .\" Specifically, the\n\ncomplaint avers that WARF purchased \"The Stone House,\" a hotel in\n\nLittle Compton, Rhode Island; a residential condominium called\n\n\"Eastbourne Lodge\" in Newport, Rhode Island; and a housing\n\ndevelopment in North Attleboro, Massachusetts.\n\n As to The Stone House, Appellees averred that WARF\n\nentered into several mortgages on the property to fund renovations\n\ntherein. Appellees claimed that, despite this debt, WARF retained\n\nall revenue from hotel operations at The Stone House as a \"'fee'\n\nfor managing the property for [t]he Funds[].\" WARF failed to make\n\nrequired periodic payments on The Stone House mortgages, and the\n\nmortgagee sued for more than $5.6 million to enforce the mortgages\n\nagainst The Stone House.\n\n\n\n\n 3 The complaint in that action addresses allegations to both\n\"Wellesley Advisors\" and \"Wellesley Advisors Realty Fund I, LLC,\"\nseemingly interchangeably. This appears to be a distinction\nwithout a difference, and the parties do not attach any\nsignificance to that point. Accordingly, we refer to allegations\nas against WARF for clarity.\n\n\n - 6 -\n\f Separately, the complaint averred that \"a sister or\n\nparent company\" of WARF received notice from a different mortgagee\n\nof its intent to foreclose on and sell the North Attleboro property\n\ndue to an unspecified \"breach of the conditions of [that]\n\nmortgage.\"\n\n Through these actions, Appellees averred that WARF\n\n\"squandered the entire [$5 million] investment,\" and that \"[t]he\n\nproperties were either lost to foreclosure or written down to a\n\nzero value because of taxes or mortgages owed.\"\n\n Based on these allegations, the Funds brought two claims\n\nin state court against WARF for negligence and violations of ERISA,\n\nrespectively. Under the first of these claims, the complaint\n\ncontends that WARF was negligent in overleveraging the properties\n\nin excess of their value, failing to pay property taxes, and\n\nretaining income from the investment properties, especially from\n\nThe Stone House, for its own use. The second, ERISA-based count\n\nclaims that, through its retention of revenues from The Stone\n\nHouse, WARF took on fiduciary duties to the Funds, which it\n\nsubsequently violated through \"self-dealing and mismanagement of\n\n[the properties.]\"\n\n WARF notified Scottsdale of the Funds' lawsuits against\n\nit on November 14, 2014. Scottsdale replied verbally (and, later,\n\nin writing) that the Funds' claims were excluded from coverage\n\nbased on the ERISA and Professional Services Exclusions.\n\n\n - 7 -\n\fAccordingly, Scottsdale refused to either defend or indemnify WARF\n\nas to the Funds' claims. WARF went into receivership and did not\n\ncontest the Underlying Action thereafter.\n\n On November 25, 2015, the district court entered default\n\njudgment in the Underlying Action in favor of Appellees, awarding\n\nthem $5,005,422.12.4 On May 15, 2016, WARF assigned to Appellees\n\nall rights and claims that it held against Scottsdale.\n\n C. Procedural History\n\n Scottsdale brought the instant action on July 8, 2016,\n\nin the District Court for the District of Massachusetts, seeking\n\ndeclaratory judgment that Appellees' claims in the Underlying\n\nAction were not covered under the Policy and so that Scottsdale\n\nwas not obligated to make any payments on the judgment in that\n\ncase. Appellees included in their answer several counterclaims,\n\nincluding as relevant here claims that Scottsdale breached its\n\nduty to defend and to indemnify WARF in the Underlying Action.\n\nAppellees sought payment of the entire amount of the judgment in\n\nthe Underlying Action plus post-judgment interest. The parties\n\ncross-moved for summary judgment.\n\n On March 1, 2018, the district court denied Scottsdale's\n\nmotion and granted partial summary judgment to Appellees. The\n\ncourt found that the allegations raised in the Underlying Action\n\n\n 4\n This amount includes both the principal amount claimed\n($5 million) as well as costs and attorneys' fees.\n\n\n - 8 -\n\fwere not \"clearly excluded\" from coverage under the policy and so\n\nScottsdale had, at minimum, a duty to defend WARF against those\n\nclaims. Based on Scottsdale's uncontested failure to take up\n\nWARF's legal defense in the Underlying Action, the court concluded\n\nthat Scottsdale was liable to Appellees and required the parties\n\nto file \"motions concerning the form of the judgment,\" which it\n\nsaid would \"[p]resumably . . . be awarded [in] the amount of the\n\ncoverage limit.\" After the parties submitted the required\n\nmotions,5 the court entered judgment for Appellees on May 8, 2015,\n\nin the amount of $3,038,081.10, consisting of the policy limit of\n\n$3 million plus post-judgment interest calculated at the statutory\n\nrate. Scottsdale timely appealed the district court's judgment.\n\n II.\n\n On appeal, Scottsdale argues that the district court\n\nerred in concluding that it had a duty to defend the Underlying\n\nAction. It points to the Policy's Professional Services and ERISA\n\nExclusions, contending that each of those exclusions clearly\n\napplies to the claims asserted in the Underlying Action and\n\n\n\n 5\n In its motion, Scottsdale also moved for clarification of\nthe summary judgment order, seeking dismissal of Appellees'\ncounterclaims for breaches of the implied covenant of good faith\nand fair dealing, and violation of the Massachusetts consumer\nprotection statute, which the district court initially failed to\naddress. Appellees, on the other hand, sought entry of judgment\nin the full amount of damages in the Underlying Action. The court\ndismissed the remaining claims and denied the motion for damages\nin excess of the policy limit plus interest.\n\n\n - 9 -\n\findependently provides a basis for denying coverage. In the\n\nalternative, Scottsdale contends that it is only liable for the\n\ncosts of defending the Underlying Action —— not the entire policy\n\nlimit —— because the claims are excluded by the Policy's Conduct\n\nExclusion. We examine these arguments separately and find no\n\nreason to reverse the district court's determination.\n\n A. Standard of Review\n\n Review of the district court's grant of summary judgment\n\nis de novo. Barrett Paving Materials, Inc. v. Continental Ins.\n\nCo., 488 F.3d 59, 63 (1st Cir. 2007). Where, as here, there is no\n\ndispute regarding the material facts, the only issue is whether\n\nthe moving party is entitled to judgment as a matter of law. Id.\n\n(citation omitted).\n\n This case comes before us based on our diversity\n\njurisdiction, and the parties agree that Massachusetts provides\n\nthe substantive law to be applied. \"The interpretation of an\n\ninsurance policy is a question of law for the court.\" Valley Forge\n\nIns. Co. v. Field, 670 F.3d 93, 97 (1st Cir. 2012) (citation\n\nomitted). \"Under Massachusetts law, [the court] construe[s] an\n\ninsurance policy under the general rules of contract\n\ninterpretation. . . . begin[ning] with the actual language of the\n\npolicies, given its plain and ordinary meaning.\" Brazas Sporting\n\nArms, Inc. v. Am. Empire Surplus Lines Ins. Co., 220 F.3d 1, 4\n\n(1st Cir. 2000) (citations omitted).\n\n\n - 10 -\n\f The \"insurer's duty to defend is independent from, and\n\nbroader than, its duty to indemnify,\" Metro. Prop. & Cas. Ins. Co.\n\nv. Morrison, 951 N.E.2d 662, 667 (Mass. 2011) (internal quotation\n\nmarks and citation omitted), and insurers \"owe[] a duty to defend\n\n[their insured] if the allegations in the underlying lawsuit are\n\nreasonably susceptible to an interpretation that they state a claim\n\ncovered by [the] policy,\" Scottsdale Ins. Co. v. Torres, 561 F.3d\n\n74, 77 (1st Cir. 2009) (citation omitted); see also Billings v.\n\nCommerce Ins. Co., 936 N.E.2d 408, 414 (Mass. 2010) (\"An insurer\n\nhas a duty to defend an insured when the allegations in a complaint\n\nare reasonably susceptible of an interpretation that states or\n\nroughly sketches a claim covered by the policy terms.\" (footnote\n\nand citation omitted)). Said somewhat differently, \"[i]n order\n\nfor the duty of defense to arise, the underlying complaint need\n\nonly show, through general allegations, a possibility that the\n\nliability claim falls within the insurance coverage. There is no\n\nrequirement that the facts alleged in the complaint specifically\n\nand unequivocally make out a claim within the coverage.\" Sterilite\n\nCorp. v. Cont'l Cas. Co., 458 N.E.2d 338, 341 (Mass. App. Ct. 1983)\n\n(internal quotation marks and citation omitted). Courts look to\n\n\"the source from which the plaintiff's personal injury originates\n\nrather than the specific theories of liability alleged in the\n\ncomplaint\" to determine whether the policy covers the claim under\n\nthis standard. Bagley v. Monticello Ins. Co., 720 N.E.2d 813, 817\n\n\n - 11 -\n\f(Mass. 1999) (internal quotation marks, citation, and emphasis\n\nomitted).\n\n Where, as here, an insurer asserts that it is not\n\nobligated to defend due to some policy exclusion or exclusions, it\n\nbears the initial burden of demonstrating that the exclusion\n\napplies.6 See Saint Consulting Grp., Inc. v. Endurance Am. Spec.\n\nIns. Co., Inc., 699 F.3d 544, 550 (1st Cir. 2012) (citation\n\nomitted). In order to meet this requirement, \"the facts alleged\n\nin the third-party complaint must establish that the exclusion\n\napplies to all potential liability as matter of law.\" Norfolk &\n\nDedham Mut. Fire Ins. Co. v. Cleary Consultants, Inc., 958 N.E.2d\n\n853, 862 (Mass. App. Ct. 2011) (citation omitted); see also Saint\n\nConsulting Grp., 699 F.3d at 550 (\"If even one of the counts in\n\neither of the complaints falls within the coverage provisions but\n\noutside any exclusion, [the insurer] would have a duty to defend\n\nthe entire lawsuit.\"). \"[W]hether an exclusion applies to relieve\n\nan insurer of its duty to defend [] depend[s] on whether the\n\ninsured would have reasonably understood the exclusion to bar\n\n\n\n\n 6 Generally, the insured bears the initial burden of \"showing\nthat the overall coverage provisions of the insurance policy\napply[.]\" Clark Sch. for Creative Learning, Inc. v. Phila. Indem.\nIns. Co., 734 F.3d 51, 55 n.1 (1st Cir. 2013). Where, as here,\nthe dispute centers only on the effect of coverage exclusions, the\ncourt can bypass this initial showing and proceed directly to\nevaluating the reach of those exclusions. See id. at 55.\n\n\n - 12 -\n\fcoverage.\" Essex Ins. Co. v. BloomSouth Flooring Corp., 562 F.3d\n\n399, 404 (1st Cir. 2009).\n\n B. The Professional Services Exclusion\n\n Scottsdale first contends that all of the allegations in\n\nthe Underlying Action fall within the purview of the Professional\n\nServices Exclusion. In particular, it contends that all of the\n\nallegations in that case \"arose out of\" or \"involved\" \"real estate\n\ndevelopment, property management, the purchase of real property,\n\nor the arrangement of financing on real property,\" all of which\n\nScottsdale argues fall \"within the plain meaning of the\n\nProfessional Services Exclusion.\" In support of this position,\n\nScottsdale relies on the broad readings afforded by Massachusetts\n\nlaw to the terms \"arising out of\" and \"in any way involving,\" both\n\nof which are used to preface the substantive scope of the\n\nProfessional Services Exclusion (as well as the other relevant\n\nexclusions). See Bagley, 720 N.E.2d at 816 (explaining that the\n\nphrase \"arising out of\" \"must be read expansively, incorporating\n\na greater range of causation than that encompassed by proximate\n\ncause under tort law\" (citations omitted)); Clark Sch. for Creative\n\nLearning, 734 F.3d at 56 (holding that \"in any way involving\" acts\n\nas a \"mop-up clause, intended to exclude anything not already\n\nexcluded by the other clauses,\" including \"arising out of\").\n\n Scottsdale's argument fails, however, to account for all\n\nof the claims raised in the Underlying Action. As noted above,\n\n\n - 13 -\n\fthe Underlying Action concerned losses stemming from WARF's\n\ninvestment in three properties: The Stone House, and properties in\n\nNorth Attleboro and Newport. Were those allegations limited to\n\nclaims regarding the mismanagement of The Stone House, we might\n\nagree: claims stemming from WARF's renovation of that property and\n\nretention of revenues from its operation of the hotel as a\n\n\"management\" fee fit seemingly well within the exclusion for\n\nactions taken \"as a . . . real estate developer [or] . . . property\n\nmanager.\" As Appellees observed at oral argument, however, the\n\ncomplaint offers no similar allegations that WARF was developing,\n\nimproving, or managing operations at the investment properties in\n\nNorth Attleboro or Newport. Beyond alleging that WARF invested in\n\nthose parcels, the only additional claims are that the properties\n\nwere \"lost to foreclosure or written down to a zero value because\n\nof tax or mortgages owed\" and, generally, that WARF \"engaged in\n\nself-dealing by retaining investment income from the properties\n\nfor its own use.\" These limited allegations preclude any\n\nmeaningful evaluation of whether the loss of the Newport and North\n\nAttleboro properties was attributable to WARF's actions as a\n\nproperty manager, developer, investor, or otherwise. As the\n\ndistrict court observed, \"[a]t the very least, it is ambiguous\n\nwhether in fact all of WARF's purported misconduct stemmed from\"\n\nWARF's provision of professional services. Thus, the allegations\n\nconcerning the Newport and North Attleboro properties are not\n\n\n - 14 -\n\fclearly within the Professional Services Exclusion, and, where\n\nthere is ambiguity, there is a duty to defend.\n\n Scottsdale attempts to argue around this shortcoming,\n\nclaiming that all of the allegations fall within the broad\n\ndefinition of \"services\" —— especially the \"arrangement of\n\nfinancing on real property\" —— included in the Professional\n\nServices Exclusion. Scottsdale misreads its own policy, however:\n\nthe plain language of the Policy is clear that, in order to fall\n\nwithin the Professional Services Exclusion, the \"services\" as\n\ndefined must be provided \"as a real estate broker or agent,\"\n\n\"property manager,\" or another of that exclusion's enumerated\n\nroles. As noted above, the allegations set forth in the Underlying\n\nAction do not offer any meaningful basis from which we can conclude\n\nthat WARF was acting in any one of those roles with respect to\n\neither the North Attleboro or Newport properties.\n\n We therefore conclude that Scottsdale failed to meet its\n\nburden of establishing that the Professional Services Exclusion\n\napplies to all claims of liability within the Underlying Action.\n\n C. The ERISA Exclusion\n\n Scottsdale next turns to the ERISA Exclusion. As\n\ndiscussed, the Underlying Action asserted both a negligence claim\n\nand, separately, a claim that WARF's actions violated duties\n\nimposed by ERISA. The parties do not dispute that the latter of\n\nthese claims falls outside of the Policy's coverage, and that count\n\n\n - 15 -\n\fis not at issue here. Scottsdale goes a step further, however,\n\ncontending that because the negligence and ERISA claims arise from\n\nthe same set of facts, the negligence claim is therefore preempted\n\nby ERISA.\n\n At the outset, we note that none of the categories of\n\nexcluded \"Claims\" —— \"actual or alleged violations\" of (1) ERISA;\n\n(2) \"rules or regulations promulgated\" pursuant to ERISA; or (3)\n\n\"similar provisions of federal, state or local statutory or common\n\nlaw\" —— explicitly remove \"preempted\" state law claims from the\n\nPolicy's coverage. Recognizing this shortcoming, Scottsdale\n\nattempts to shoehorn preempted state-law claims into this clause\n\nas a \"similar provision[] of . . . state . . . common law.\" In\n\nour view, however, the question of whether that language could\n\nextend to a common law action for negligence, stated without\n\nreference to ERISA-like fiduciary duties, is ambiguous at best.\n\nThat observation alone settles the issue before us: Scottsdale has\n\nthe burden of demonstrating the exclusion's application to the\n\nUnderlying Action, and all ambiguities must be read against the\n\ninsurer. See Valley Forge Ins. Co., 670 F.3d at 97. Accordingly,\n\nwe see no basis for excusing Scottsdale from its duty to defend\n\nbased on the ERISA Exclusion.7\n\n\n\n\n 7 Because we find that neither of the exclusions cited by\nScottsdale excuse it from its duty to defend, we do not reach\nAppellees' alternate argument that, under its terms, the Policy's\n\n\n - 16 -\n\f D. The Conduct Exclusion\n\n In its final argument, Scottsdale contends that its\n\nliability is limited by the Policy's Conduct Exclusion. Unlike\n\nthe Professional Services and ERISA Exclusions, Scottsdale does\n\nnot claim that the Conduct Exclusion excuses it from its duty to\n\ndefend: by its terms, that exclusion is not implicated \"unless\n\nand until there is a final judgment against [the] . . . Insureds\n\n. . . .\" Rather, Scottsdale contends that, even if it breached\n\nthe duty to defend, it should be permitted to contest and limit\n\nits indemnity obligation based on that exclusion's application to\n\nfinancial gains to which WARF was not entitled, specifically WARF's\n\nalleged retention of \"investment income from the properties\" at\n\nissue in the Underlying Action.\n\n An insurer's breach of its duty to defend \"may also\n\ntrigger a duty to indemnify because an insurer in breach of its\n\nduty to defend is bound by the result of the underlying action as\n\nto all matters therein decided which are material to recovery by\n\nthe insured in an action on the policy.\" Metro Prop. & Cas. Ins.,\n\n951 N.E.2d at 669 (internal quotation marks, alterations, and\n\ncitation omitted); see also Liberty Mut. Ins. Co. v. Metro. Life\n\nIns. Co., 260 F.3d 54, 63 (1st Cir. 2001) (\"[T]he general rule\n\nunder Massachusetts law is that if the insurer fails to defend the\n\n\nexclusions do not relieve the insurer of its duty to defend in any\nevent.\n\n\n - 17 -\n\flawsuit, it is liable for all defense costs and (assuming policy\n\ncoverage) the entire resulting judgment or settlement, unless\n\nliability can be allocated among covered and uncovered claims.\")\n\n(citations omitted). \"Where [the insured] defendant defaults, the\n\nfactual allegations in the complaint as to liability are deemed to\n\nbe admitted . . . and treated as if they are true\" as to both the\n\ndefendant and those insurers who wrongfully decline to defend the\n\ncase. Metro. Prop. & Cas. Ins., 951 N.E.2d at 669.\n\n Subject to these provisos, \"insurer[s] that wrongfully\n\ndecline[] to defend a claim\" may contest their indemnity under\n\ntheir policy, provided, however, that they \"have the burden of\n\nproving that the claim was not within [the] policy's coverage.\"\n\nPolaroid Corp. v. Travelers Indem. Co., 610 N.E.2d 912, 922\n\n(Mass. 1993). Moreover, where some of the claims fall within a\n\npolicy's coverage and others do not, \"an insurer that breaches its\n\nduty to defend bears the burden of allocating a judgment against\n\nits insured between covered and noncovered claims.\" Palermo v.\n\nFireman's Fund Ins. Co., 676 N.E.2d 1158, 1163 (Mass. App. Ct.\n\n1997); see also Liquor Liab. Joint Underwriting Ass'n of Mass. v.\n\nHermitage Ins. Co., 644 N.E.2d 964, 968-69 (Mass. 1995).\n\n Similar to the Professional Services Exclusion,\n\nScottsdale's attempt to escape its indemnity obligation fails to\n\naccount for all of the claims made in the Underlying Action.\n\nScottsdale maintains a narrow focus on allegations that WARF\n\n\n - 18 -\n\fengaged in self-dealing when it retained fees from the investment\n\nproperties. Self-dealing, however, is just one component of the\n\nmany allegations in the Underlying Action. Much of the complaint\n\nis concerned not with WARF's improper gain or pecuniary advantage,\n\nbut rather the squandering of Appellees' investment through, among\n\nother things, negligently overleveraging and failing to pay taxes\n\nand service mortgages on the properties.8 Those allegations were\n\n\"conclusively establishe[d]\" by the entry of default as to\n\nScottsdale, Metro. Prop. & Cas. Ins., 951 N.E.2d at 669, and they\n\noffer a theory of Appellees' loss that is entirely separate from\n\nany improper gain by WARF. Scottsdale provides no basis from which\n\nwe could conclude that the Conduct Exclusion covers all of the\n\nmaterial allegations established in the Underlying Action, and it\n\nfurther fails to demonstrate any grounds for allocating the\n\njudgment award between portions attributable to WARF's improper\n\n\n 8 Scottsdale's reliance on Winbrook Communication Services\nInc. v. United States Liability Insurance Company, 52 N.E.3d 195\n(Mass. App. Ct. 2016), is misplaced. There, the insured company's\nnegligent misstatements about its own financial stability induced\nthe judgment creditor to provide a benefit in the form of services\nfor which it was never paid. Id. at 197. Examining a conduct\nexclusion similar to that in the Policy, the court concluded that\nevidence in the record indicated that, through its\nmisrepresentations, the insured might have \"received goods or\nservices that created an opportunity for gain or advantage . . . .\n[such as] credit, investors, or customers.\" Id. at 203. In other\nwords, the insured's negligence might have directly contributed to\nits receipt of an advantage to which it was not legally entitled.\nIn this case, however, we see no basis to conclude that WARF's\nnegligence in squandering Appellees' investment led to any\ndemonstrable gain.\n\n\n - 19 -\n\fgains and negligent losses. As such, we see no basis from which\n\nto relieve Scottsdale of its obligation to pay the policy limit.9\n\n III.\n\n The judgment of the district court is AFFIRMED.\n\n\n\n\n 9 In their opposition brief, Appellees hint that the district\ncourt erred in limiting their recovery to the policy limits, rather\nthan the full judgment. Because Appellees failed to cross-appeal\non that issue, we do not address the merits of their claim. See\nJennings v. Stephens, __ U.S. __, 135 S. Ct. 793, 798 (2015) (\"[A]n\nappellee who does not cross-appeal may not attack the [judgment of\nthe lower court] with a view either to enlarging his own rights\nthereunder or lessening the rights of his adversary.\" (internal\nquotation marks and citation omitted)).\n\n\n - 20 -\n[END_CASE]", "role": "user" } ]
4,582,213
Nereida RIVERA-COLÓN, Plaintiff, Appellant, v. AT&T MOBILITY PUERTO RICO, INC.; Ángel Couvertier-López; Carlos Deliz; Victor Pabón, Defendants, Appellees, Companies X, Y, Z; Jane Does; John Does; Insurance Companies A, B, C, Defendants.
Rivera-Colon v. AT&T Mobility Puerto Rico, Inc
2019-01-16
17-2036P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Torruella, Thompson", "parties": "", "opinions": [{"author": "THOMPSON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-2036\n\n NEREIDA RIVERA-COLÓN,\n\n Plaintiff, Appellant,\n\n v.\n\n AT&T MOBILITY PUERTO RICO, INC.; ÁNGEL COUVERTIER-LÓPEZ;\n CARLOS DELIZ; VICTOR PABÓN,\n\n Defendants, Appellees,\n\n COMPANIES X, Y, Z; JANE DOES; JOHN DOES;\n INSURANCE COMPANIES A, B, C,\n\n Defendants.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Thompson, Circuit Judges.\n\n\n Rubén T. Nigaglioni, with whom Nigaglioni Law Offices P.S.C.\nwas on brief, for appellant.\n Kenneth W. Gage, with whom Sara B. Tomezsko, Paul Hastings\nLLP, José F. Benítez-Mier, Iván Santos-Castaldo, and O'Neill &\nBorges LLC were on brief, for appellees.\n\fJanuary 16, 2019\n\f THOMPSON, Circuit Judge. Nereida Rivera-Colón\n\n(\"Rivera\") filed suit against her former employer, AT&T Mobility\n\nPuerto Rico, Inc. (\"AT&T\"),1 alleging age discrimination and\n\nwrongful termination. After AT&T pulled out its arbitration\n\nagreement with Rivera, the district court sent the parties packing\n\nto arbitrate. Rivera now asks us to flip the district court's\n\norder and allow her to slug it out with AT&T in court. She says\n\nthat she shouldn't have to arbitrate her claims because she never\n\naccepted AT&T's offer to arbitrate legal grievances in the first\n\nplace. But because we conclude that she manifested her intent to\n\naccept the agreement as per Puerto Rico law, we affirm.\n\n BACKGROUND\n\n We start with a chronicle of the parties’ relationship\n\nand how they ended up here, diving into some detail (for reasons\n\nthat will become apparent later).2\n\n\n\n\n 1 She also sued some of her supervisors, who are the other\ndefendant-appellees, Ángel Couvertier-López, Carlos Deliz, and\nVictor Pabón. But they raise the same arguments as AT&T, so we\njust loop them in collectively with their employer, and call them\nAT&T.\n 2 Where, as here, the motion to compel arbitration was made\n\nas part of a motion to dismiss or stay, \"we glean the relevant\nfacts from the operative complaint and the documents submitted to\nthe district court in support of the motion.\" Oliveira v. New\nPrime, Inc., 857 F.3d 7, 9 n.1 (1st Cir. 2017), aff’d, ____ S. Ct.\n____, No. 17-340, 2019 WL 189342 (U.S. Jan. 15, 2019).\n\n\n - 3 -\n\f A. Rivera's Employment\n\n Their story begins in December 1997, when Rivera (then\n\nin her late twenties) began her twenty years' tenure as an employee\n\nof AT&T in Puerto Rico. By 2006, she had worked her way up the\n\ncorporate ladder to become an Assistant Store Manager in AT&T's\n\nretail location in Mayagüez, Puerto Rico. There she supervised a\n\nsmall team of employees who sold cell phones, service plans, and\n\nall the like. For the majority of her time with AT&T, she says\n\nall went well. She consistently received high performance ratings\n\nand was praised by her superiors.\n\n But Rivera says everything changed beginning in 2015.\n\nOut of the blue, she was transferred from her home base in Mayagüez\n\nafter twelve years there--even though she had seniority over the\n\nother assistant manager, and even though transfers were supposed\n\nto be based on seniority. AT&T stationed her at another retail\n\nlocation, this one a kiosk at the Aguadilla Mall, about an hour\n\ndrive from her home. She says this transfer was really a demotion.\n\nThe Aguadilla kiosk had lower sales (which means lower\n\ncommissions), worse hours, and less opportunity for promotion.\n\nAnd, to boot, she says her supervision in Aguadilla was a far throw\n\naway from congenial. Now 49 years old, Rivera was supervised by\n\na manager fifteen years her junior who, according to her, placed\n\nher on a performance improvement plan for no legitimate reason,\n\nand harassed her because of her age.\n\n\n - 4 -\n\f B. Rolling Out the Arbitration Agreement\n\n A few years before things turned sour, though, AT&T\n\nrolled out an arbitration program to a large chunk of its\n\nemployees, including Rivera.3 On November 30, 2011, AT&T sent\n\nRivera an email (on her company email account with unique username\n\nand password) informing her of the proposed change. The email\n\ntold Rivera that under the program, \"employees and the company\n\nwould use independent, third-party arbitration rather than courts\n\nor juries to resolve legal disputes.\" But unlike some other\n\narbitration programs, AT&T's wasn't mandatory. Instead, AT&T said\n\nthat \"[t]he decision on whether or not to participate [was\n\nRivera's] to make,\" and that if she didn't want to participate in\n\nthis alternative dispute resolution mechanism, she could opt out\n\nby following two links: one in the email, and one in the webpage\n\nthe email link opened. There were no consequences for opting out\n\n(except, of course, that Rivera couldn't force AT&T to arbitrate\n\nits claims against her).\n\n The offer came with a proviso, though: if Rivera didn't\n\nopt out by the end of the day on February 6, 2012 (giving Rivera\n\nsixty-eight days to respond), AT&T would take it as though she\n\nopted in. The email told her: \"[i]f you do not opt out by the\n\n\n\n\n 3\n Before 2011, AT&T didn't have an independent arbitration\nagreement with Rivera, or an arbitration provision in Rivera's\nemployment contract.\n\n\n - 5 -\n\fdeadline, you are agreeing to the arbitration process as set forth\n\nin the Agreement. This means that you and AT&T are giving up the\n\nright to a court or jury trial on claims covered by the Agreement.\"\n\nThe email advised Rivera to review the agreement before making a\n\ndecision and instructed that if she wished to opt out, she needed\n\nto open the agreement and \"follow the link provided there to the\n\nsite where [she would] be able to electronically register [her]\n\ndecision to opt out.\" AT&T sent the same email to Rivera twice\n\nmore--once in December 2011, and once in January 2012. All three\n\nemails included instructions on how to opt out.\n\n Opting out of the agreement required two steps. First,\n\nas the email said, Rivera would need to open the agreement and\n\nacknowledge that she read it. Every employee was required to\n\nconduct this first step regardless of whether they chose to opt\n\nout. To complete this step, the employee needed to follow the\n\nlink provided in the email, which led to a webpage that contained\n\nthe full text of the agreement. On that page, there was a button\n\nmarked \"Review Completed\" in the upper-left-hand corner of the\n\npage.\n\n According to AT&T's records (and she doesn't contend\n\notherwise), Rivera completed this step and acknowledged that she\n\nread the agreement. Indeed, according to AT&T's internal records\n\nof website traffic, Rivera viewed the arbitration agreement twice.\n\nThe first time was in December 2011, although she didn't click the\n\n\n - 6 -\n\facknowledgement button then. And on round two, she clicked the\n\nacknowledgement button less than an hour after the January 17,\n\n2012 follow-up email was sent. Rivera doesn't dispute that it was\n\nshe who clicked \"Review Completed,\" nor does she argue that she\n\nclicked the acknowledgement button at the top of the page without\n\nscrolling down to read the agreement.4\n\n Step two of the opt-out procedure: the employee had to\n\nclick one additional link--this one in paragraph four of the\n\nagreement on that webpage. This paragraph, just a few lines into\n\nthe agreement, discussed the opportunity to opt out and laid out\n\nthe mechanism to do so: \"[i]f you choose to opt out, use this\n\nlink . . . which will take you to the site where you can\n\nelectronically register your decision to opt out. That site will\n\ngenerate and send you a written confirmation of your decision to\n\nopt out.\" And, according to AT&T, a cohort of thousands of\n\nRivera's colleagues followed that link and opted out of the\n\narbitration agreement.\n\n\n 4\n The placement of the \"Review Completed\" button at the top\nof the agreement makes it a type of \"clickwrap\" agreement where\nthe party doesn't need to actually scroll through the agreement\nbefore accepting it. See Cullinane v. Uber Techs., Inc., 893 F.3d\n53, 61 n.1 (1st Cir. 2018) (quoting Berkson v. Gogo LLC, 97\nF. Supp. 3d 359, 394 (E.D.N.Y. 2015)) (discussing the different\ntypes of acceptance processes for online agreements). So,\ntechnically, Rivera could have acknowledged the agreement without\never scrolling through to read it in its entirety. But because\nshe doesn't argue that she never read the agreement, this case\nisn't really about the new questions internet-based contracts like\nthese have raised, so we need not get into the weeds on that front.\n\n\n - 7 -\n\f Rivera has never argued, either to the district court or\n\nto us, that she did follow that link and tried to opt out but that\n\nthe company just didn't register her decision. Nor has she argued\n\nthat the opt-out procedure was confusing, or that she couldn't\n\nfind how to opt out. In other words, she makes no argument that\n\nshe affirmatively chose to opt out--or even wanted to do so--at\n\nthe time the agreement was offered to her.\n\n C. Their Litigation\n\n Eventually, AT&T fired Rivera in May 2016, and replaced\n\nher with a 34-year-old. Taking issue with the way things went\n\ndown, Rivera sued AT&T, her supervisors, and some other unnamed\n\nparties (the last of which don't appear here) in the U.S. District\n\nCourt for the District of Puerto Rico. She brought an array of\n\nclaims for violations of her civil rights, alleging that AT&T\n\ndiscriminated against her for her age, in violation of Title VII\n\nof the Civil Rights Act, 42 U.S.C. §§ 2000e, et seq.; Puerto Rico\n\nLaw 100, P.R. Laws Ann. tit. 29, §§ 146, et seq.; and Puerto Rico\n\nLaw 69, P.R. Laws Ann. tit. 29, §§ 1321, et seq. She also alleged\n\nwrongful termination under Puerto Rico Law 80, P.R. Laws Ann. tit.\n\n29, §§ 185, et seq.\n\n Not so fast, said AT&T. It entered a special appearance\n\nand moved to stay the proceedings and compel arbitration, reminding\n\nRivera that she agreed to arbitrate these kinds of claims, not\n\nbring them in court. So AT&T asked the court to force Rivera to\n\n\n - 8 -\n\fgo to arbitration, thus stripping the district court of\n\njurisdiction to hear the merits of the case. To support this\n\nresult, AT&T submitted hundreds of pages of affidavits and exhibits\n\nto show that Rivera read the agreement and didn't opt out, and\n\ntherefore accepted it.\n\n Determined to stay where she was, Rivera opposed AT&T's\n\nattempt to push her into arbitration, maintaining that there was\n\nno valid arbitration agreement to begin with. She argued that\n\nPuerto Rico law requires acceptance of a contract, and that her\n\nmere failure to opt out can't meet the acceptance standard under\n\nthe Commonwealth's laws.\n\n Rejecting Rivera's contentions, the district court\n\nagreed with AT&T and said the arbitration agreement was\n\nenforceable. See Rivera-Colón v. AT&T Mobility P.R., Inc., 261\n\nF. Supp. 3d 251, 256 (D.P.R. 2017). The judge looked to AT&T's\n\nsubmitted evidence, which showed that Rivera received the emails\n\nnotifying her of the arbitration agreement and that she\n\nacknowledged that she read the agreement. And, given that\n\nevidence, the judge thought it clear that \"AT&T gave [Rivera]\n\nexplicit notice that all disputes would be solved by arbitration\"\n\nso he granted AT&T's motion to compel arbitration and dismissed\n\nRivera's suit.5 See id. at 255-56.\n\n\n 5 Although AT&T moved to stay the proceedings pending\narbitration of the claims, the district judge elected to dismiss\n\n\n - 9 -\n\f Clinging to the assertions she advanced below, and\n\nrepeats here on appeal, Rivera says the district court got it all\n\nwrong and asks us to reverse and give her the green light to\n\nlitigate her claims in court.\n\n DISCUSSION\n\n A. Standard of Review\n\n Generally, we review an order compelling arbitration on\n\na spectrum of interwoven standards. At one end, when the appeal\n\nraises \"solely legal issues as to the enforceability of an\n\narbitration clause,\" we look at it with a clean slate, or de novo.\n\nPelletier v. Yellow Transp., Inc., 549 F.3d 578, 580 (1st Cir.\n\n2008); see also Britto v. Prospect Chartercare SJHSRI, LLC, 909\n\nF.3d 506, 511 (1st Cir. 2018) (explaining de novo review in this\n\ncontext). The same de novo review applies when the facts\n\nsurrounding the agreement are undisputed and the only question is\n\nwhether they contractually bound themselves to arbitration on\n\nthose undisputed facts. See Cullinane v. Uber Techs., Inc., 893\n\nF.3d 53, 60 (1st Cir. 2018).6 And given that the facts here are\n\n\n\nthe proceedings. See, e.g., Next Step Med. Co. v. Johnson &\nJohnson Int'l, 619 F.3d 67, 71 (1st Cir. 2010) (noting that, in\nthis circuit, a district court has discretion \"to dismiss the law\nsuit, if all claims asserted in the case are found arbitrable\").\nThe parties do not appeal this exercise of discretion.\n 6 Although not applicable here, for the sake of thoroughness\n\nwe remind the careful reader that were the facts in dispute, we\nwould review the district court's determinations on a \"sliding\nscale.\" See Quint v. A.E. Staley Mfg. Co., 246 F.3d 11, 14 (1st\nCir. 2001). That is, \"[t]he more the district court's conclusions\n\n\n - 10 -\n\fundisputed the only question that remains is whether those facts\n\nshow that Rivera accepted the agreement as a matter of Puerto Rico\n\nlaw. So, we review that determination of the district court de\n\nnovo. See Cullinane, 893 F.3d at 60. That means we don't give\n\nany deference to the district court's conclusion and look at the\n\nlegal issues with clear eyes. See In re Extradition of Howard,\n\n996 F.2d 1320, 1327 (1st Cir. 1993). And it also means that we\n\n\"can affirm on any ground appearing in the record--including one\n\nthat the [district] judge did not rely on.\" See Lang v. Wal-Mart\n\nStores E., L.P., 813 F.3d 447, 454 (1st Cir. 2016) (citing Collazo-\n\nRosado v. Univ. of P.R., 765 F.3d 86, 91 (1st Cir. 2014)).\n\n Bearing in mind this appellate lens, we return to the\n\nlegal issue before us.\n\n B. A Primer on the Law\n\n For reasons that will become clear in the next section,\n\na legal primer will help frame our discussion. So, we ask the\n\npatient reader to bear with us as we lay it out.\n\n With the Federal Arbitration Act (\"FAA\"), Congress set\n\na \"liberal federal policy favoring arbitration.\" AT&T Mobility\n\nLLC v. Concepcion, 563 U.S. 333, 346 (2011) (quoting Moses H. Cone\n\nMemorial Hosp. v. Mercury Constr. Corp., 460 U.S. 1, 24 (1983)).\n\n\n\nare characterized as factual conclusions, the more our review of\nthose facts is for clear error; the more the district court's\nconclusions are conclusions of law, the more independent review we\ngive.\" Id.\n\n\n - 11 -\n\fThe FAA allows one party to an arbitration agreement to ask the\n\ncourt to put the litigation on hold and force the other party to\n\narbitrate the disputes. See 9 U.S.C. § 4. At base, it respects\n\narbitration as \"a matter of contract\" between parties and doesn't\n\nallow courts to jump in when the parties agreed to keep the courts\n\nout of the mix. See Henry Schein, Inc. v. Archer & White Sales,\n\nInc., ____ S. Ct. ____, No. 17-1272, 2019 WL 122164, at *3 (U.S.\n\nJan. 8, 2019). It \"places arbitration agreements on equal footing\n\nwith all other contracts,\" Buckeye Check Cashing, Inc. v. Cardegna,\n\n546 U.S. 440, 443 (2006), which means that courts can invalidate\n\narbitration agreements only on the same \"generally applicable\n\ncontract defense[]\" grounds that would apply to all other\n\ncontracts, Doctor's Assocs., Inc. v. Casarotto, 517 U.S. 681, 687\n\n(1996).\n\n But as a corollary to its contract-based philosophy, the\n\nFAA's \"liberal policy\" is only triggered when the parties actually\n\nagreed to arbitrate. It \"does not require parties to arbitrate\n\nwhen they have not agreed to do so.\" Volt Info. Scis., Inc. v.\n\nBd. of Trs. of Leland Stanford Jr. Univ., 489 U.S. 468, 478 (1989).\n\nSo, the existence of an enforceable agreement to arbitrate is the\n\nfirst needed step to trigger the FAA's protective reach. See Nat'l\n\nFed'n of the Blind v. The Container Store, Inc., 904 F.3d 70, 80\n\n(1st Cir. 2018) (noting that \"a court should not compel arbitration\n\nunless and until it determines that the parties entered into a\n\n\n - 12 -\n\fvalidly formed and legally enforceable agreement covering the\n\nunderlying claims\" (quoting Escobar-Noble v. Luxury Hotels Int'l\n\nof P.R., Inc., 680 F.3d 118, 121 (1st Cir. 2012))). And the party\n\nseeking to compel arbitration (here, that's AT&T) bears the burden\n\nof clearing that hurdle and \"demonstrat[ing] that a valid agreement\n\nto arbitrate exists.\" Soto-Fonalledas v. Ritz-Carlton San Juan\n\nHotel Spa & Casino, 640 F.3d 471, 474 (1st Cir. 2011) (quoting\n\nInterGen N.V. v. Grina, 344 F.3d 134, 142 (1st Cir. 2003))\n\n(internal quotation marks omitted).\n\n Because arbitration is a creature of contract,\n\n\"principles of state contract law control the determination of\n\nwhether a valid agreement to arbitrate exists.\" Id. at 475\n\n(quoting Campbell v. Gen. Dynamics Gov't Sys. Corp., 407 F.3d 546,\n\n552 (1st Cir. 2005)). Rivera and AT&T assume that Puerto Rico law\n\napplies--a rational choice we won't disturb here given that Rivera\n\nwas employed in the Commonwealth. See, e.g., Rodríguez v. United\n\nStates, 54 F.3d 41, 44 (1st Cir. 1995) (assuming that Puerto Rico\n\nlaw applies when the parties assumed so and there was a \"reasonable\n\nrelation\" between the cause of action and Puerto Rico). So, if an\n\nenforceable contract exists under Puerto Rico law, we must enforce\n\nthat agreement \"save upon such grounds as exist at law or in equity\n\nfor the revocation of any contract,\" 9 U.S.C. § 2, and send the\n\nparties off to arbitrate.\n\n\n\n\n - 13 -\n\f This brings us to the skirmish the parties are waging\n\nbefore us today. Put simply: if Rivera never agreed to arbitrate\n\nher claims against AT&T, she's free to pursue them in court; but\n\nif she did agree to arbitrate her claims against AT&T, she's bound\n\nby her contract and she must resolve those claims through\n\narbitration. So, this is all we need to decide here. See Dean\n\nWitter Reynolds, Inc. v. Byrd, 470 U.S. 213, 218 (1985) (noting\n\nthat the FAA \"mandates that district courts shall direct the\n\nparties to proceed to arbitration on issues as to which an\n\narbitration agreement has been signed\"); see also Escobar-Noble,\n\n680 F.3d at 122. The merits of her employment-based claims against\n\nAT&T are left for another day, another umpire, and another ballpark\n\n(whether judicial or arbitral).\n\n C. The Arguments\n\n Against this backdrop, the parties argue primarily over\n\nthe application of Puerto Rico contract law. Unsurprisingly, they\n\ndon't see eye to eye on how that law applies to the situation here.\n\n Rivera argues there's no enforceable agreement to\n\narbitrate because she never accepted AT&T's unsolicited offer. As\n\nbest we can tell, she makes this omnibus argument in what breaks\n\ndown into three waves. First, according to her, Puerto Rico law\n\ndoesn't construe an offeree's silence or inaction as acceptance to\n\na contract offer when that offer was made at the offeror's sole\n\ninitiative. She says that there was no bargaining between her and\n\n\n - 14 -\n\fAT&T about the arbitration agreement, so she had no obligation to\n\nrespond to say yes or no to its offer. And, she argues that under\n\nPuerto Rico law, an offeror cannot impose on the offeree an\n\nobligation to respond to an unsolicited offer. That is, if AT&T\n\nmakes an unsolicited offer, it can't force Rivera to respond and\n\nsay no, or to stipulate that her lack of response will be\n\ninterpreted as saying yes.\n\n Wave two is a rebuttal point. She says that even if she\n\ncould accept with her silence, the facts here don't unequivocally\n\nshow her intent to accept the contract, so she didn't accept this\n\nagreement. And in wave three, she adds two alternative arguments:\n\nthat this arbitration agreement is both a waiver of substantive\n\nrights and a type of forum selection clause--both of which require\n\na heightened standard of acceptance under Puerto Rico law, which\n\ncan't be met here.\n\n AT&T, for its part, says that Puerto Rico law permits\n\nsilence as an avenue to acceptance of a contract, although it\n\nacknowledges that there's no Puerto Rico precedent directly on\n\npoint. But it says that under the limited precedent we have, the\n\nfacts of this case show that Rivera knew that her silence and\n\ncontinued employment would constitute acceptance of the\n\narbitration agreement--and that her actions show that she\n\nwillfully accepted. It says that she acknowledged that she read\n\nthe provision that stipulated that her continued employment and\n\n\n - 15 -\n\ffailure to opt out of the agreement would constitute her\n\nacceptance. And, her inaction coupled with her continued\n\nemployment shows that her conduct was informed and voluntary. So,\n\nRivera demonstrated her will to accept AT&T's offer, and is bound\n\nby the arbitration agreement.\n\n ANALYSIS\n\n A. The Framework\n\n To assess these arguments, we first must look to the\n\nframework of Puerto Rico contract law, and note some guideposts of\n\nPuerto Rico law that shape our analysis.\n\n Puerto Rico is unique in many ways, its legal system\n\njust one of them. As a civil law jurisdiction, \"Puerto Rico\n\neschews common law principles of contract interpretation in favor\n\nof its own civil code derived from Spanish law.\" Borschow Hosp.\n\n& Med. Supplies v. Cesar Castillo Inc., 96 F.3d 10, 15 (1st Cir.\n\n1996) (citing Guevara v. Dorsey Labs., Div. of Sandoz, Inc., 845\n\nF.2d 364, 366 (1st Cir. 1988)). So we can't use stateside common\n\nlaw to \"fill[] gaps in the civil law system\" unless the Civil Code\n\nand the Supreme Court of Puerto Rico are silent on the issue.\n\nGuevara, 845 F.2d at 366 (citing Valle v. Am. Int'l Ins. Co., 108\n\nD.P.R. 692, 696-97, 8 P.R. Offic. Trans. 735 (1979)). We turn\n\nfirst to those sources.\n\n\n\n\n - 16 -\n\f To form a valid contract under Puerto Rico law, both\n\nparties must consent to it. See P.R. Laws Ann. tit. 31, § 3391.7\n\nThat consent \"is shown by the concurrence of the offer and\n\nacceptance of the thing and the cause which are to constitute the\n\ncontract.\" P.R. Laws Ann. tit. 31, § 3401. In simple terms:\n\n\"acceptance of an offer is . . . the normal procedure to perfect\n\na contract.\" Producciones Tommy Muñiz Inc. v. Comité Organizador\n\nde Los VIII Panamericanos (COPAN), 113 D.P.R. 517, 13 P.R. Offic.\n\nTrans. 664, 670 (1982). But \"[c]onsent given by error, under\n\nviolence, by intimidation, or deceit shall be void.\" P.R. Laws\n\nAnn. tit. 31, § 3404; see also Dialysis Access Ctr., LLC v. RMS\n\nLifeline, Inc., 638 F.3d 367, 378 (1st Cir. 2011) (discussing how\n\nconsent may be void under Puerto Rico law).\n\n This case presents a twist on the normal question,\n\nthough. In the more typical case, the employee accepts the\n\ncontract by signing on the dotted line, thus leaving little doubt\n\nthat she accepted the agreement. But we consider here whether\n\nRivera accepted the agreement by doing nothing--through her\n\ninaction or silence.8\n\n\n\n\n 7\n You also need to have \"[a] definite object which may be the\nsubject of the contract,\" and \"[t]he cause for the obligation which\nmay be established.\" P.R. Laws Ann. tit. 31, § 3391. But that's\nnot what the parties are arguing about here.\n 8 We note that AT&T doesn't argue that Rivera accepted the\n\nagreement when she acknowledged that she read it. It says that\nshe accepted it when she did not opt out and continued to work.\n\n\n - 17 -\n\f Although that brand of acceptance doesn't find its own\n\ndistinct provision in the Puerto Rican Civil Code, the Supreme\n\nCourt of Puerto Rico has recognized that not all acceptances are\n\nin writing--implied consent to a contract is enough to meet the\n\nPuerto Rico definition of acceptance. See Teachers Annuity & Ret.\n\nSys. v. Sociedad de Gananciales, 115 D.P.R. 277, 15 P.R. Offic.\n\nTrans. 372, 386-87 (1984); see also Colón Gutiérrez v. Registrador,\n\n114 D.P.R. 850, 14 P.R. Offic. Trans. 1095, 1110 (1983) (noting\n\nthat consent to an agreement can be given \"expressly or\n\nimpliedly\"). When it comes to this type of implied consent, \"the\n\ndetermining element . . . is the person's conduct and not the words\n\nused to express such consent.\" Teachers Annuity & Ret. Sys., 115\n\nD.P.R. 277, 15 P.R. Offic. Trans. at 387. That conduct \"should\n\ninequivocally [sic] show the will to consent,\" and the facts\n\n\"cannot be compatible with, another intent, or be subject to many\n\ndifferent interpretations.\" Id. 115 D.P.R. 277, 15 P.R. Offic.\n\nTrans. at 387-88. And the party accepting must have \"adequate\n\nknowledge of the scope of [her] statement\" to be able to adequately\n\nevidence her consent. See Colón Gutiérrez, 114 D.P.R. 850, 14\n\nP.R. Offic. Trans. at 1111. But on the precise question here\n\n(whether silence is acceptance when the offeror conditions that it\n\nwill be), the Supreme Court of Puerto Rico has not spoken.\n\n When the Civil Code and the Supreme Court of Puerto Rico\n\nare silent on an issue, we may forgo the traditional prohibition\n\n\n - 18 -\n\fon use of common law principles and \"employ the common law in its\n\nmultiple and rich versions . . . as a point of reference for\n\ncomparative law.\" Valle, 108 D.P.R. 692, 8 P.R. Offic. Trans. at\n\n738; see also Guevara, 845 F.2d at 366 (applying stateside common\n\nlaw principles when \"useful and persuasive\" and when we \"believe[d]\n\nthe Supreme Court of Puerto Rico would follow essentially the same\n\npath\"). That is particularly true when the Supreme Court of Puerto\n\nRico has, on a particular subject, \"conformed its . . .\n\njurisprudence to common law principles.\" Rodríguez, 54 F.3d at\n\n45. And in the contract-acceptance context, Puerto Rico law\n\n\"mimics the general law of contracts,\" Satellite Broad. Cable,\n\nInc. v. Telefónica de España, S.A., 807 F. Supp. 210, 216 (D.P.R.\n\n1992), and operates in the same way as the \"governing rule in the\n\nUnited States,\" see COPAN, 113 D.P.R. 517, 13 P.R. Offic. Trans.\n\nat 672 (referencing U.S. treatises Williston on Contracts and\n\nCorbin on Contracts). Which is all a long explanation of why we\n\nwill, at times, look to those stateside treatise sources to fill\n\nin the gap here.\n\n B. Addressing Those Arguments\n\n Wave I: Assessing Rivera's Intent in Silence\n\n With that legal outline in mind, we turn to the core of\n\nthis case: do the (undisputed) facts unequivocally show that\n\nRivera manifested her intent to accept AT&T's arbitration\n\nagreement?\n\n\n - 19 -\n\f To tackle that question, we begin with a recount of one\n\nof our prior cases, the closest we've gone to addressing an issue\n\nlike this under Puerto Rico law, which will prove instructive in\n\nassessing the one before us now. In Marrero-García v. Irizzary,\n\n33 F.3d 117 (1st Cir. 1994), we discussed a similar, albeit\n\ndistinct, issue. There, a utility company argued that residents\n\nof a condominium complex impliedly accepted a contract to pay for\n\nwater services that the utility had already begun providing to\n\nthem. See 33 F.3d at 122. The utility company \"repeatedly\n\nrequested the Condominium to place a bond and to register an\n\naccount,\" and informed the residents they needed to take these\n\nactions to become \"registered users.\"9 Id. But when the residents\n\nnever posted a bond or registered with the utility company, the\n\nutility company set up an account for them and started sending\n\nbills for water. The utility company then sued when the residents\n\nrefused to pay. We rejected the utility company's implied-\n\nacceptance argument, holding that the residents' refusal to\n\nregister was not implied consent to the agreement to pay for water\n\nservices, but rather a rejection of that offer. And the key\n\ntakeaway we reap from this case is that \"[a]n offeree's inaction\n\nor 'silence in the face of the offer to sell goods is not ordinarily\n\nan acceptance, because the offeror has no reason to believe from\n\n\n 9\n The utility company didn't add a proviso deeming silence as\nacceptance, like AT&T did here.\n\n\n - 20 -\n\fthe offeree's silence that the offeree promises to buy.'\" Id.\n\n(quoting Farnsworth on Contracts § 3.15).\n\n To be sure, the facts of Rivera's case add a wrinkle to\n\na Marrero-García-style analysis: AT&T specified that Rivera's\n\nsilence would constitute acceptance. Rivera thinks this wrinkle\n\nwill cut in her direction. She's correct that it makes all the\n\ndifference here, but it makes all the difference in a way she\n\ndoesn't imagine: it is actually AT&T's stipulation of silence as\n\nacceptance that tilts the scale away from Rivera's position, and\n\nleads us to the opposite of the conclusion we reached in Marrero-\n\nGarcía. Let us explain.\n\n Of course, as Rivera reminds us, it's basic contract law\n\nthat an offeror cannot unilaterally impose on another party the\n\nobligation to respond and reject their offer. See, e.g., 1 Corbin\n\non Contracts § 3.19 (2018) (\"It should here be plainly set forth\n\nthat an offeror has no power to cause the silence of the offeree\n\nto operate as an acceptance when the offeree does not intend it to\n\ndo so.\"); 2 Williston on Contracts § 6:50 (4th ed. 1993) (\"Merely\n\nsending an unsolicited offer does not impose upon the party\n\nreceiving it any duty to speak or deprive the party of its\n\nprivilege of remaining silent without accepting.\"). But this\n\ngeneral statement of the law is just that--a generality. There\n\nare, as always, exceptions. Indeed, the Restatement (which Rivera\n\ncites in her brief) makes it clear that silence can operate as\n\n\n - 21 -\n\facceptance \"[w]here the offeror has stated or given the offeree\n\nreason to understand that assent may be manifested by silence or\n\ninaction, and the offeree in remaining silent and inactive intends\n\nto accept the offer.\" Restatement (Second) of Contracts\n\n§ 69(1)(b); see also 2 Williston on Contracts § 6:53 (\"If the\n\nsituation for any reason is such that a reasonable person would\n\nconstrue silence as necessarily indicating assent, the offeree who\n\nkeeps silent, knowing that its silence will be misinterpreted,\n\nshould not be allowed to deny the natural interpretation of its\n\nconduct.\"). This aligns with the notion in Puerto Rico that\n\n\"silence could imply the tacit acceptance of an offer when,\n\npursuant to a prior relationship between the parties, the\n\nresponsibility arises for the one receiving the offer to take\n\naffirmative action to reject it.\" Danosa Caribbean, Inc. v.\n\nSantiago Metal Mfg. Corp., 179 D.P.R. 40, No. CC-2008-882, slip\n\nop. at 21 (2010) (Rodríguez Rodríguez, J., dissenting) (citing\n\nCarlos Lasarte, 3 Principios del Derecho Civil 63 (4th ed. 1996)).10\n\n And that's where the scale flips away from Rivera. AT&T\n\nstipulated that if Rivera didn't opt out, it would take it as\n\nthough she opted in. Rivera acknowledged that she read that\n\nprovision (both here in litigation, and when she acknowledged that\n\n\n\n\n 10We requested that the parties file a certified translation\nof this otherwise-untranslated case from the Supreme Court of\nPuerto Rico.\n\n\n - 22 -\n\fshe read the agreement back in 2012). It was laid out nose-to-\n\nface plain and simple in the emails AT&T sent her, as well as in\n\nthe arbitration agreement that she confirmed she received and read.\n\nSo, by acknowledging that she read that proviso, she actually gave\n\nAT&T \"reason to believe from [her] silence that [she] promise[d]\"\n\nto arbitrate her claims, unlike the residents in Marrero-García.\n\nSee 33 F.3d at 122 (quoting Farnsworth on Contracts § 3.15). Thus,\n\nthese facts evidence Rivera's intent to accept the agreement.\n\n Wave II: Was That Intent Unequivocal?\n\n So we move on to wave two of her argument: that even if\n\nshe could accept with her silence in these circumstances,11 the\n\nfacts here don't unequivocally show her intent to accept the\n\ncontract.\n\n Under Puerto Rico law, the facts \"should inequivocally\n\n[sic] show the will to consent . . . [and] cannot be compatible\n\nwith, another intent, or be subject to many different\n\ninterpretations.\" Teachers Annuity & Ret. Sys., 115 D.P.R. 277,\n\n15 P.R. Offic. Trans. at 387-88. Rivera (quite obviously) argues\n\nthat her actions here don't unequivocally show her will to consent.\n\nHer position is twofold. First, she says that \"there is no\n\nscintilla of evidence on the record that [she] ever intended to\n\naccept the offer. In fact, the opposite holds true. When [AT&T]\n\n\n 11\n Indeed, Rivera acknowledges that silence can, \"in certain\ncircumstances,\" constitute acceptance.\n\n\n - 23 -\n\fattempted to enforce the 'contract,' [she] opposed.\" And second\n\nis that the facts only show that she \"acknowledge[d] having\n\nreviewed the document\"; not that she intended to accept it.\n\nAddressing these arguments in turn, they both fail.\n\n First, her objection to arbitration when this litigation\n\ncommenced in 2017 has no bearing on whether she manifested her\n\nintent to accept the agreement back in 2012. We say that for two\n\nreasons: one legal and one logical. On the legal side, it doesn't\n\ncarry weight because it misses the operative timeframe for\n\nassessing her intent. It's basic Puerto Rico contract law that\n\ncontracts are formed and valid \"from the moment\" consent is given.\n\nSee P.R. Laws Ann. tit. 31, §§ 3371, 3375. So, the question is\n\nwhether she manifested her intent to accept the agreement way back\n\nin 2012 when she didn't opt out; not what happened in 2017. Which\n\nis all to say that this argument doesn't get her anywhere. And\n\nthat's not to mention that the logical side of her argument is\n\nbaffling. Disputes of this sort arise in litigation precisely\n\nbecause a party later disputes whether they intended to accept a\n\ncontract. So, if a party's later disavowment of their intent to\n\naccept a contract bore any decisive weight (as Rivera seems to\n\nsuggest it should), it would make analysis unnecessary. This would\n\nmake the cases we just discussed pure excess--which they are not.\n\nCf. generally Teachers Annuity & Ret. Sys., 115 D.P.R. 277, 15\n\nP.R. Offic. Trans. at 387-88 (looking to the facts at the time of\n\n\n - 24 -\n\fthe purported contract formation to determine if implied consent\n\nexisted even though the party later disputed their consent in\n\nlitigation); Cemex De P.R., Inc. v. Ductor, Inc., No. CIV.A. 09-\n\n2254 (GAG), 2010 WL 1727834, at *1 (D.P.R. Apr. 26, 2010) (finding\n\nthat plaintiff sufficiently alleged implied consent even when the\n\nparty later disputed the consent during litigation).\n\n And her second argument (that her intent in clicking the\n\nreview completed button was to show only that she acknowledged\n\nreading the agreement)12 is even more troubling and actually self-\n\ndefeating. Again, it is critical to note that Rivera doesn't\n\nattempt to say that she didn't know her silence would be treated\n\nas opting in. Instead of confronting this head on, though, her\n\nargument tries to leapfrog over her contractual obligations by\n\nrelying on a general rule that AT&T couldn't make her respond.13\n\n\n 12 In the same vein of this argument, Rivera also proposes a\nnew standard we should apply. She says that if AT&T wanted an\narbitration agreement with her, it should have made it so that she\n\"would have taken affirmative steps to clearly and unmistakenly\n[sic] affirm her intent to be bound by an agreement to arbitrate.\"\nBut imposing that requirement would force us to ignore the Supreme\nCourt of Puerto Rico's clear instruction that a contract can be\nformed with implied consent. See generally Teachers Annuity &\nRet. Sys., 115 D.P.R. 277, 15 P.R. Offic. Trans. 372. And we\ncannot do so. See, e.g., Wainwright v. Goode, 464 U.S. 78, 84\n(1983) (\"[T]he views of the state's highest court with respect to\nstate law are binding on the federal courts.\"); Rochester Lincoln-\nMercury, Inc. v. Ford Motor Co., 248 F.3d 46, 48 (1st Cir. 2001)\n(same).\n 13 To support this argument, Rivera provides us with one- or\n\ntwo-sentence excerpts from three Spanish commentators about\nsilence as a mode of acceptance under the Spanish Civil Code.\nInitially, the translations were made only by her counsel, which\n\n\n - 25 -\n\fBut this argument strikes out just as quickly as the first, because\n\nit glances over the exception (rooted in notions of good faith)\n\nthat aims to root out the type of maneuvers she's trying to make\n\nhere: \"the offeree who keeps silent, knowing that [her] silence\n\nwill be misinterpreted, should not be allowed to deny the natural\n\ninterpretation of [her] conduct.\" 2 Williston on Contracts § 6:53.\n\n That exception is especially pertinent in situations\n\nlike this (just as the Restatement, Corbin, and Williston have\n\nnoted14), where \"given a certain relationship between two people,\n\nthe current way of proceeding implies the duty to speak.\" Danosa\n\n\n\n\nwas out of compliance with our Local Rule requiring certified\ntranslations of Spanish documents. See 1st Cir. Local R. 30.0(e).\nIn her reply brief, Rivera provided certified translations of those\nthree snippets, but not the broader context from which they came.\nAnd, as we've said in the past, isolated excerpts from treatises\nnot translated into English are not useful support. See, e.g.,\nUnited States v. Ramos-González, 775 F.3d 483, 505 & n.26 (1st\nCir. 2015) (noting that a counsel-translated sentence from a\nSpanish-language treatise on Puerto Rico's penal code, not\notherwise available in English, is not \"useful support\" for an\nargument). Especially given the potential for these excerpts to\nbe read out of context, we decline to use them here.\n 14 See Restatement (Second) of Contracts § 69(1)(c) (noting\n\nthe exception where silence is acceptance \"because of previous\ndealings or otherwise, it is reasonable that the offeree should\nnotify the offeror if he does not intend to accept\"); 1 Corbin on\nContracts § 3.18 (\"Often, however, silence coupled with conduct or\nwith expectations engendered by a prior relationship can\nreasonably be understood by the offeror as an acceptance.\"); 2\nWilliston on Contracts § 6:50 (noting that \"the relationship\nbetween the parties or other circumstances surrounding the\ntransaction may be such as to justify the offeror in expecting a\nreply, and, therefore, in assuming that silence in fact does\nindicate assent to its proposal\").\n\n\n - 26 -\n\fCaribbean, 179 D.P.R. 40, slip op. at 21 (Rodríguez Rodríguez, J.,\n\ndissenting) (quoting Lasarte, 3 Principios del Derecho Civil 63).\n\n Unlike the unsolicited offer-by-mail to which Rivera\n\ntries to liken this case, this wasn't an offer made by a stranger.\n\nRivera and AT&T were engaged in a long-standing, close legal\n\nrelationship as employee and employer. That relationship--one in\n\nwhich AT&T and its employees regularly communicated company\n\nbusiness with one another via email15--implicates Rivera's\n\nknowledge that she had the duty to speak and that her choice not\n\nto would be reasonably interpreted by AT&T as acceptance. Cf.\n\nCircuit City Stores, Inc. v. Najd, 294 F.3d 1104, 1109 (9th Cir.\n\n2002) (O'Scannlain, J.) (noting in a very similar context under\n\nCalifornia law that the employee and employer \"were not two typical\n\nparties contracting at arm's length,\" and that the employee had a\n\nresponsibility to affirmatively opt out if he didn't want to\n\naccept). And when \"the one who can and should speak does not do\n\nso, it must be deemed that [s]he consents for the sake of good\n\nfaith . . . because in such cases, it is natural and normal to\n\nmanifest dissent.\" Danosa Caribbean, 179 D.P.R. 40, slip op. at\n\n21 (Rodríguez Rodríguez, J., dissenting) (emphasis added) (quoting\n\nLasarte, 3 Principios del Derecho Civil 63). So absent her\n\ndissent, the natural interpretation of her conduct is that she\n\n\n 15\n AT&T communicated at least twenty corporate policies to its\nemployees in the year prior to the arbitration proposal.\n\n\n - 27 -\n\faccepted. And that must stand. Thus, we agree with the district\n\ncourt that Rivera impliedly accepted this arbitration agreement\n\nand is bound by it.\n\n Wave III: A Heightened Standard of Acceptance\n\n But wait, Rivera has two alternative arguments to try to\n\nsteer us back to her side. She calls this agreement both a waiver\n\nof substantive rights and a forum selection clause. And she\n\ncontends that under Puerto Rico law, this means that a heightened\n\nstandard of acceptance should apply to the agreement. That is,\n\nstandard modes of consent aren't enough to accept this type of\n\nagreement. But unfortunately for Rivera, these arguments don't\n\nmove the needle in her direction.\n\n First, she argues that a heightened standard of contract\n\nacceptance should apply here because the agreement is a waiver of\n\na substantive right (the substantive right being her right to a\n\njury trial). And, under Puerto Rico law, \"such renunciation[s] of\n\nrights . . . must be clear, conclusive, express, and unequivocal.\"\n\nQuiñones Quiñones v. Quiñones Irizarry, 91 D.P.R. 225, 91 P.R.R.\n\n217, 257 (1964).\n\n But even assuming she waived a substantive right with\n\nthis agreement--and a jury trial is decidedly a procedural right,\n\nsee, e.g., Libretti v. United States, 516 U.S. 29, 53-54 (1995)\n\n(Souter, J., concurring) (recognizing the right to a jury trial is\n\na procedural right)--her argument smacks up against one of the\n\n\n - 28 -\n\fcore principles of the FAA: a state (or territory) cannot apply\n\nany standard to an arbitration agreement that it does not apply to\n\ncontracts in general, see Soto v. State Indus. Prods., Inc., 642\n\nF.3d 67, 74 (1st Cir. 2011) (\"[W]hile Puerto Rico may impose\n\nspecial restrictions on noncompetition agreements, it is preempted\n\nfrom imposing special restrictions on arbitration agreements.\");\n\nsee also Doctor's Assocs., Inc., 517 U.S. at 687 (noting that with\n\nthe FAA, \"Congress precluded States from singling out arbitration\n\nprovisions for suspect status, requiring instead that such\n\nprovisions be placed 'upon the same footing as other contracts'\").\n\n And that Supreme Court command also torpedoes her second\n\nargument that this supposed \"forum selection\" agreement16\n\nmanifesting as an arbitration agreement can be void for public\n\npolicy. She says that in Puerto Rico, forum selection agreements\n\nare unenforceable if: \"(1) they were not freely negotiated or\n\nwere the result of overweening bargaining power; or (2) they\n\ncontravene a strong public policy.\" But again, even assuming for\n\nthe sake of argument that Rivera can meet one of these grounds,\n\nunder the FAA's protective grasp, an arbitration agreement can be\n\nvoided only on \"generally applicable contract defense[]\" grounds\n\nthat would apply to all other contracts. Doctor's Assocs., Inc.,\n\n\n\n\n 16 By this, we mean an agreement between parties specifying\nwhere they'll duke out their legal disputes. See, e.g., Marra v.\nPapandreou, 216 F.3d 1119, 1123 (D.C. Cir. 2000).\n\n\n - 29 -\n\f517 U.S. at 687. And although Puerto Rico can hold forum selection\n\nclauses to a higher standard, it \"is preempted from imposing\n\nspecial restrictions on arbitration agreements.\" See Soto, 642\n\nF.3d at 74. So her final argument falls flat.\n\n C. Postscript\n\n Before we sum up, we add one last point. The careful\n\nreader will notice that we reach our ultimate conclusion on the\n\nkey issue here (whether Rivera impliedly consented to the\n\narbitration agreement) under a different legal standard than the\n\ndistrict court.17 And on that subject, we add a postscript.\n\n The district court judge said the focal point of the\n\nlegal question was \"whether AT&T gave [Rivera] explicit notice\n\nthat all disputes would be solved by arbitration.\" Rivera-Colón,\n\n261 F. Supp. 3d at 256 (citing García-Clara v. AIG Ins. Co. P.R.,\n\nNo. CV 15-1784CCC, 2016 WL 1261058 (D.P.R. 2016)). That test, in\n\nour view, misses the point. The contract formation question here\n\nis whether Rivera accepted the contract--not whether she was merely\n\non notice of the contract's existence.\n\n The district court (and the García-Clara court on which\n\nit relied) seems to have misconstrued our holdings in Campbell v.\n\nGeneral Dynamics Government Systems Corp., 407 F.3d 546 (1st Cir.\n\n\n 17Again, we're free to take this different route under de\nnovo review because we're free to \"affirm on any ground appearing\nin the record--including one that the [district court] judge did\nnot rely on.\" Lang, 813 F.3d at 454.\n\n\n - 30 -\n\f2005), and Rosenberg v. Merrill Lynch, Pierce, Fenner & Smith,\n\nInc., 170 F.3d 1 (1st Cir. 1999). In those cases, the question\n\nwas, in fact, one of notice. They turned on whether the employer\n\ngave the employees sufficient notice that certain statutory claims\n\n(those under the Americans with Disabilities Act, 42 U.S.C.\n\n§§ 12101, et seq.) would be covered under an arbitration agreement.\n\nAnd that was so important because the ADA has a specific provision\n\nthat limits arbitration of claims to situations when it would be\n\n\"appropriate.\" See 42 U.S.C. § 12212. So that was relevant to\n\nthe arbitrability of the particular claims at issue there, not the\n\narbitrability of all claims under the sun. But here, the parties\n\ndon't dispute that the particular claims are arbitrable. The only\n\nquestion is whether a valid arbitration agreement existed in the\n\nfirst place, which means that the question is one of contract\n\nacceptance--not notice. See Campbell, 407 F.3d at 554 (explaining\n\nthat the questions of whether there was a valid arbitration\n\nagreement and whether the parties had notice that ADA claims were\n\ncovered under it were \"independent, yet overlapping, issues\").\n\n WRAP-UP\n\n Our work done, and finding, as we do, that the district\n\ncourt got the outcome right, we affirm the order compelling\n\narbitration. Costs to appellees. See Fed. R. App. P. 39(a)(2).\n\n\n\n\n - 31 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359466/", "author_raw": "THOMPSON, Circuit Judge"}]}
HOWARD
TORRUELLA
THOMPSON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582213/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Nereida RIVERA-COLÓN, Plaintiff, Appellant, v. AT&T MOBILITY PUERTO RICO, INC.; Ángel Couvertier-López; Carlos Deliz; Victor Pabón, Defendants, Appellees, Companies X, Y, Z; Jane Does; John Does; Insurance Companies A, B, C, Defendants.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-2036\n\n NEREIDA RIVERA-COLÓN,\n\n Plaintiff, Appellant,\n\n v.\n\n AT&T MOBILITY PUERTO RICO, INC.; ÁNGEL COUVERTIER-LÓPEZ;\n CARLOS DELIZ; VICTOR PABÓN,\n\n Defendants, Appellees,\n\n COMPANIES X, Y, Z; JANE DOES; JOHN DOES;\n INSURANCE COMPANIES A, B, C,\n\n Defendants.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Thompson, Circuit Judges.\n\n\n Rubén T. Nigaglioni, with whom Nigaglioni Law Offices P.S.C.\nwas on brief, for appellant.\n Kenneth W. Gage, with whom Sara B. Tomezsko, Paul Hastings\nLLP, José F. Benítez-Mier, Iván Santos-Castaldo, and O'Neill &\nBorges LLC were on brief, for appellees.\n\fJanuary 16, 2019\n\f THOMPSON, Circuit Judge. Nereida Rivera-Colón\n\n(\"Rivera\") filed suit against her former employer, AT&T Mobility\n\nPuerto Rico, Inc. (\"AT&T\"),1 alleging age discrimination and\n\nwrongful termination. After AT&T pulled out its arbitration\n\nagreement with Rivera, the district court sent the parties packing\n\nto arbitrate. Rivera now asks us to flip the district court's\n\norder and allow her to slug it out with AT&T in court. She says\n\nthat she shouldn't have to arbitrate her claims because she never\n\naccepted AT&T's offer to arbitrate legal grievances in the first\n\nplace. But because we conclude that she manifested her intent to\n\naccept the agreement as per Puerto Rico law, we affirm.\n\n BACKGROUND\n\n We start with a chronicle of the parties’ relationship\n\nand how they ended up here, diving into some detail (for reasons\n\nthat will become apparent later).2\n\n\n\n\n 1 She also sued some of her supervisors, who are the other\ndefendant-appellees, Ángel Couvertier-López, Carlos Deliz, and\nVictor Pabón. But they raise the same arguments as AT&T, so we\njust loop them in collectively with their employer, and call them\nAT&T.\n 2 Where, as here, the motion to compel arbitration was made\n\nas part of a motion to dismiss or stay, \"we glean the relevant\nfacts from the operative complaint and the documents submitted to\nthe district court in support of the motion.\" Oliveira v. New\nPrime, Inc., 857 F.3d 7, 9 n.1 (1st Cir. 2017), aff’d, ____ S. Ct.\n____, No. 17-340, 2019 WL 189342 (U.S. Jan. 15, 2019).\n\n\n - 3 -\n\f A. Rivera's Employment\n\n Their story begins in December 1997, when Rivera (then\n\nin her late twenties) began her twenty years' tenure as an employee\n\nof AT&T in Puerto Rico. By 2006, she had worked her way up the\n\ncorporate ladder to become an Assistant Store Manager in AT&T's\n\nretail location in Mayagüez, Puerto Rico. There she supervised a\n\nsmall team of employees who sold cell phones, service plans, and\n\nall the like. For the majority of her time with AT&T, she says\n\nall went well. She consistently received high performance ratings\n\nand was praised by her superiors.\n\n But Rivera says everything changed beginning in 2015.\n\nOut of the blue, she was transferred from her home base in Mayagüez\n\nafter twelve years there--even though she had seniority over the\n\nother assistant manager, and even though transfers were supposed\n\nto be based on seniority. AT&T stationed her at another retail\n\nlocation, this one a kiosk at the Aguadilla Mall, about an hour\n\ndrive from her home. She says this transfer was really a demotion.\n\nThe Aguadilla kiosk had lower sales (which means lower\n\ncommissions), worse hours, and less opportunity for promotion.\n\nAnd, to boot, she says her supervision in Aguadilla was a far throw\n\naway from congenial. Now 49 years old, Rivera was supervised by\n\na manager fifteen years her junior who, according to her, placed\n\nher on a performance improvement plan for no legitimate reason,\n\nand harassed her because of her age.\n\n\n - 4 -\n\f B. Rolling Out the Arbitration Agreement\n\n A few years before things turned sour, though, AT&T\n\nrolled out an arbitration program to a large chunk of its\n\nemployees, including Rivera.3 On November 30, 2011, AT&T sent\n\nRivera an email (on her company email account with unique username\n\nand password) informing her of the proposed change. The email\n\ntold Rivera that under the program, \"employees and the company\n\nwould use independent, third-party arbitration rather than courts\n\nor juries to resolve legal disputes.\" But unlike some other\n\narbitration programs, AT&T's wasn't mandatory. Instead, AT&T said\n\nthat \"[t]he decision on whether or not to participate [was\n\nRivera's] to make,\" and that if she didn't want to participate in\n\nthis alternative dispute resolution mechanism, she could opt out\n\nby following two links: one in the email, and one in the webpage\n\nthe email link opened. There were no consequences for opting out\n\n(except, of course, that Rivera couldn't force AT&T to arbitrate\n\nits claims against her).\n\n The offer came with a proviso, though: if Rivera didn't\n\nopt out by the end of the day on February 6, 2012 (giving Rivera\n\nsixty-eight days to respond), AT&T would take it as though she\n\nopted in. The email told her: \"[i]f you do not opt out by the\n\n\n\n\n 3\n Before 2011, AT&T didn't have an independent arbitration\nagreement with Rivera, or an arbitration provision in Rivera's\nemployment contract.\n\n\n - 5 -\n\fdeadline, you are agreeing to the arbitration process as set forth\n\nin the Agreement. This means that you and AT&T are giving up the\n\nright to a court or jury trial on claims covered by the Agreement.\"\n\nThe email advised Rivera to review the agreement before making a\n\ndecision and instructed that if she wished to opt out, she needed\n\nto open the agreement and \"follow the link provided there to the\n\nsite where [she would] be able to electronically register [her]\n\ndecision to opt out.\" AT&T sent the same email to Rivera twice\n\nmore--once in December 2011, and once in January 2012. All three\n\nemails included instructions on how to opt out.\n\n Opting out of the agreement required two steps. First,\n\nas the email said, Rivera would need to open the agreement and\n\nacknowledge that she read it. Every employee was required to\n\nconduct this first step regardless of whether they chose to opt\n\nout. To complete this step, the employee needed to follow the\n\nlink provided in the email, which led to a webpage that contained\n\nthe full text of the agreement. On that page, there was a button\n\nmarked \"Review Completed\" in the upper-left-hand corner of the\n\npage.\n\n According to AT&T's records (and she doesn't contend\n\notherwise), Rivera completed this step and acknowledged that she\n\nread the agreement. Indeed, according to AT&T's internal records\n\nof website traffic, Rivera viewed the arbitration agreement twice.\n\nThe first time was in December 2011, although she didn't click the\n\n\n - 6 -\n\facknowledgement button then. And on round two, she clicked the\n\nacknowledgement button less than an hour after the January 17,\n\n2012 follow-up email was sent. Rivera doesn't dispute that it was\n\nshe who clicked \"Review Completed,\" nor does she argue that she\n\nclicked the acknowledgement button at the top of the page without\n\nscrolling down to read the agreement.4\n\n Step two of the opt-out procedure: the employee had to\n\nclick one additional link--this one in paragraph four of the\n\nagreement on that webpage. This paragraph, just a few lines into\n\nthe agreement, discussed the opportunity to opt out and laid out\n\nthe mechanism to do so: \"[i]f you choose to opt out, use this\n\nlink . . . which will take you to the site where you can\n\nelectronically register your decision to opt out. That site will\n\ngenerate and send you a written confirmation of your decision to\n\nopt out.\" And, according to AT&T, a cohort of thousands of\n\nRivera's colleagues followed that link and opted out of the\n\narbitration agreement.\n\n\n 4\n The placement of the \"Review Completed\" button at the top\nof the agreement makes it a type of \"clickwrap\" agreement where\nthe party doesn't need to actually scroll through the agreement\nbefore accepting it. See Cullinane v. Uber Techs., Inc., 893 F.3d\n53, 61 n.1 (1st Cir. 2018) (quoting Berkson v. Gogo LLC, 97\nF. Supp. 3d 359, 394 (E.D.N.Y. 2015)) (discussing the different\ntypes of acceptance processes for online agreements). So,\ntechnically, Rivera could have acknowledged the agreement without\never scrolling through to read it in its entirety. But because\nshe doesn't argue that she never read the agreement, this case\nisn't really about the new questions internet-based contracts like\nthese have raised, so we need not get into the weeds on that front.\n\n\n - 7 -\n\f Rivera has never argued, either to the district court or\n\nto us, that she did follow that link and tried to opt out but that\n\nthe company just didn't register her decision. Nor has she argued\n\nthat the opt-out procedure was confusing, or that she couldn't\n\nfind how to opt out. In other words, she makes no argument that\n\nshe affirmatively chose to opt out--or even wanted to do so--at\n\nthe time the agreement was offered to her.\n\n C. Their Litigation\n\n Eventually, AT&T fired Rivera in May 2016, and replaced\n\nher with a 34-year-old. Taking issue with the way things went\n\ndown, Rivera sued AT&T, her supervisors, and some other unnamed\n\nparties (the last of which don't appear here) in the U.S. District\n\nCourt for the District of Puerto Rico. She brought an array of\n\nclaims for violations of her civil rights, alleging that AT&T\n\ndiscriminated against her for her age, in violation of Title VII\n\nof the Civil Rights Act, 42 U.S.C. §§ 2000e, et seq.; Puerto Rico\n\nLaw 100, P.R. Laws Ann. tit. 29, §§ 146, et seq.; and Puerto Rico\n\nLaw 69, P.R. Laws Ann. tit. 29, §§ 1321, et seq. She also alleged\n\nwrongful termination under Puerto Rico Law 80, P.R. Laws Ann. tit.\n\n29, §§ 185, et seq.\n\n Not so fast, said AT&T. It entered a special appearance\n\nand moved to stay the proceedings and compel arbitration, reminding\n\nRivera that she agreed to arbitrate these kinds of claims, not\n\nbring them in court. So AT&T asked the court to force Rivera to\n\n\n - 8 -\n\fgo to arbitration, thus stripping the district court of\n\njurisdiction to hear the merits of the case. To support this\n\nresult, AT&T submitted hundreds of pages of affidavits and exhibits\n\nto show that Rivera read the agreement and didn't opt out, and\n\ntherefore accepted it.\n\n Determined to stay where she was, Rivera opposed AT&T's\n\nattempt to push her into arbitration, maintaining that there was\n\nno valid arbitration agreement to begin with. She argued that\n\nPuerto Rico law requires acceptance of a contract, and that her\n\nmere failure to opt out can't meet the acceptance standard under\n\nthe Commonwealth's laws.\n\n Rejecting Rivera's contentions, the district court\n\nagreed with AT&T and said the arbitration agreement was\n\nenforceable. See Rivera-Colón v. AT&T Mobility P.R., Inc., 261\n\nF. Supp. 3d 251, 256 (D.P.R. 2017). The judge looked to AT&T's\n\nsubmitted evidence, which showed that Rivera received the emails\n\nnotifying her of the arbitration agreement and that she\n\nacknowledged that she read the agreement. And, given that\n\nevidence, the judge thought it clear that \"AT&T gave [Rivera]\n\nexplicit notice that all disputes would be solved by arbitration\"\n\nso he granted AT&T's motion to compel arbitration and dismissed\n\nRivera's suit.5 See id. at 255-56.\n\n\n 5 Although AT&T moved to stay the proceedings pending\narbitration of the claims, the district judge elected to dismiss\n\n\n - 9 -\n\f Clinging to the assertions she advanced below, and\n\nrepeats here on appeal, Rivera says the district court got it all\n\nwrong and asks us to reverse and give her the green light to\n\nlitigate her claims in court.\n\n DISCUSSION\n\n A. Standard of Review\n\n Generally, we review an order compelling arbitration on\n\na spectrum of interwoven standards. At one end, when the appeal\n\nraises \"solely legal issues as to the enforceability of an\n\narbitration clause,\" we look at it with a clean slate, or de novo.\n\nPelletier v. Yellow Transp., Inc., 549 F.3d 578, 580 (1st Cir.\n\n2008); see also Britto v. Prospect Chartercare SJHSRI, LLC, 909\n\nF.3d 506, 511 (1st Cir. 2018) (explaining de novo review in this\n\ncontext). The same de novo review applies when the facts\n\nsurrounding the agreement are undisputed and the only question is\n\nwhether they contractually bound themselves to arbitration on\n\nthose undisputed facts. See Cullinane v. Uber Techs., Inc., 893\n\nF.3d 53, 60 (1st Cir. 2018).6 And given that the facts here are\n\n\n\nthe proceedings. See, e.g., Next Step Med. Co. v. Johnson &\nJohnson Int'l, 619 F.3d 67, 71 (1st Cir. 2010) (noting that, in\nthis circuit, a district court has discretion \"to dismiss the law\nsuit, if all claims asserted in the case are found arbitrable\").\nThe parties do not appeal this exercise of discretion.\n 6 Although not applicable here, for the sake of thoroughness\n\nwe remind the careful reader that were the facts in dispute, we\nwould review the district court's determinations on a \"sliding\nscale.\" See Quint v. A.E. Staley Mfg. Co., 246 F.3d 11, 14 (1st\nCir. 2001). That is, \"[t]he more the district court's conclusions\n\n\n - 10 -\n\fundisputed the only question that remains is whether those facts\n\nshow that Rivera accepted the agreement as a matter of Puerto Rico\n\nlaw. So, we review that determination of the district court de\n\nnovo. See Cullinane, 893 F.3d at 60. That means we don't give\n\nany deference to the district court's conclusion and look at the\n\nlegal issues with clear eyes. See In re Extradition of Howard,\n\n996 F.2d 1320, 1327 (1st Cir. 1993). And it also means that we\n\n\"can affirm on any ground appearing in the record--including one\n\nthat the [district] judge did not rely on.\" See Lang v. Wal-Mart\n\nStores E., L.P., 813 F.3d 447, 454 (1st Cir. 2016) (citing Collazo-\n\nRosado v. Univ. of P.R., 765 F.3d 86, 91 (1st Cir. 2014)).\n\n Bearing in mind this appellate lens, we return to the\n\nlegal issue before us.\n\n B. A Primer on the Law\n\n For reasons that will become clear in the next section,\n\na legal primer will help frame our discussion. So, we ask the\n\npatient reader to bear with us as we lay it out.\n\n With the Federal Arbitration Act (\"FAA\"), Congress set\n\na \"liberal federal policy favoring arbitration.\" AT&T Mobility\n\nLLC v. Concepcion, 563 U.S. 333, 346 (2011) (quoting Moses H. Cone\n\nMemorial Hosp. v. Mercury Constr. Corp., 460 U.S. 1, 24 (1983)).\n\n\n\nare characterized as factual conclusions, the more our review of\nthose facts is for clear error; the more the district court's\nconclusions are conclusions of law, the more independent review we\ngive.\" Id.\n\n\n - 11 -\n\fThe FAA allows one party to an arbitration agreement to ask the\n\ncourt to put the litigation on hold and force the other party to\n\narbitrate the disputes. See 9 U.S.C. § 4. At base, it respects\n\narbitration as \"a matter of contract\" between parties and doesn't\n\nallow courts to jump in when the parties agreed to keep the courts\n\nout of the mix. See Henry Schein, Inc. v. Archer & White Sales,\n\nInc., ____ S. Ct. ____, No. 17-1272, 2019 WL 122164, at *3 (U.S.\n\nJan. 8, 2019). It \"places arbitration agreements on equal footing\n\nwith all other contracts,\" Buckeye Check Cashing, Inc. v. Cardegna,\n\n546 U.S. 440, 443 (2006), which means that courts can invalidate\n\narbitration agreements only on the same \"generally applicable\n\ncontract defense[]\" grounds that would apply to all other\n\ncontracts, Doctor's Assocs., Inc. v. Casarotto, 517 U.S. 681, 687\n\n(1996).\n\n But as a corollary to its contract-based philosophy, the\n\nFAA's \"liberal policy\" is only triggered when the parties actually\n\nagreed to arbitrate. It \"does not require parties to arbitrate\n\nwhen they have not agreed to do so.\" Volt Info. Scis., Inc. v.\n\nBd. of Trs. of Leland Stanford Jr. Univ., 489 U.S. 468, 478 (1989).\n\nSo, the existence of an enforceable agreement to arbitrate is the\n\nfirst needed step to trigger the FAA's protective reach. See Nat'l\n\nFed'n of the Blind v. The Container Store, Inc., 904 F.3d 70, 80\n\n(1st Cir. 2018) (noting that \"a court should not compel arbitration\n\nunless and until it determines that the parties entered into a\n\n\n - 12 -\n\fvalidly formed and legally enforceable agreement covering the\n\nunderlying claims\" (quoting Escobar-Noble v. Luxury Hotels Int'l\n\nof P.R., Inc., 680 F.3d 118, 121 (1st Cir. 2012))). And the party\n\nseeking to compel arbitration (here, that's AT&T) bears the burden\n\nof clearing that hurdle and \"demonstrat[ing] that a valid agreement\n\nto arbitrate exists.\" Soto-Fonalledas v. Ritz-Carlton San Juan\n\nHotel Spa & Casino, 640 F.3d 471, 474 (1st Cir. 2011) (quoting\n\nInterGen N.V. v. Grina, 344 F.3d 134, 142 (1st Cir. 2003))\n\n(internal quotation marks omitted).\n\n Because arbitration is a creature of contract,\n\n\"principles of state contract law control the determination of\n\nwhether a valid agreement to arbitrate exists.\" Id. at 475\n\n(quoting Campbell v. Gen. Dynamics Gov't Sys. Corp., 407 F.3d 546,\n\n552 (1st Cir. 2005)). Rivera and AT&T assume that Puerto Rico law\n\napplies--a rational choice we won't disturb here given that Rivera\n\nwas employed in the Commonwealth. See, e.g., Rodríguez v. United\n\nStates, 54 F.3d 41, 44 (1st Cir. 1995) (assuming that Puerto Rico\n\nlaw applies when the parties assumed so and there was a \"reasonable\n\nrelation\" between the cause of action and Puerto Rico). So, if an\n\nenforceable contract exists under Puerto Rico law, we must enforce\n\nthat agreement \"save upon such grounds as exist at law or in equity\n\nfor the revocation of any contract,\" 9 U.S.C. § 2, and send the\n\nparties off to arbitrate.\n\n\n\n\n - 13 -\n\f This brings us to the skirmish the parties are waging\n\nbefore us today. Put simply: if Rivera never agreed to arbitrate\n\nher claims against AT&T, she's free to pursue them in court; but\n\nif she did agree to arbitrate her claims against AT&T, she's bound\n\nby her contract and she must resolve those claims through\n\narbitration. So, this is all we need to decide here. See Dean\n\nWitter Reynolds, Inc. v. Byrd, 470 U.S. 213, 218 (1985) (noting\n\nthat the FAA \"mandates that district courts shall direct the\n\nparties to proceed to arbitration on issues as to which an\n\narbitration agreement has been signed\"); see also Escobar-Noble,\n\n680 F.3d at 122. The merits of her employment-based claims against\n\nAT&T are left for another day, another umpire, and another ballpark\n\n(whether judicial or arbitral).\n\n C. The Arguments\n\n Against this backdrop, the parties argue primarily over\n\nthe application of Puerto Rico contract law. Unsurprisingly, they\n\ndon't see eye to eye on how that law applies to the situation here.\n\n Rivera argues there's no enforceable agreement to\n\narbitrate because she never accepted AT&T's unsolicited offer. As\n\nbest we can tell, she makes this omnibus argument in what breaks\n\ndown into three waves. First, according to her, Puerto Rico law\n\ndoesn't construe an offeree's silence or inaction as acceptance to\n\na contract offer when that offer was made at the offeror's sole\n\ninitiative. She says that there was no bargaining between her and\n\n\n - 14 -\n\fAT&T about the arbitration agreement, so she had no obligation to\n\nrespond to say yes or no to its offer. And, she argues that under\n\nPuerto Rico law, an offeror cannot impose on the offeree an\n\nobligation to respond to an unsolicited offer. That is, if AT&T\n\nmakes an unsolicited offer, it can't force Rivera to respond and\n\nsay no, or to stipulate that her lack of response will be\n\ninterpreted as saying yes.\n\n Wave two is a rebuttal point. She says that even if she\n\ncould accept with her silence, the facts here don't unequivocally\n\nshow her intent to accept the contract, so she didn't accept this\n\nagreement. And in wave three, she adds two alternative arguments:\n\nthat this arbitration agreement is both a waiver of substantive\n\nrights and a type of forum selection clause--both of which require\n\na heightened standard of acceptance under Puerto Rico law, which\n\ncan't be met here.\n\n AT&T, for its part, says that Puerto Rico law permits\n\nsilence as an avenue to acceptance of a contract, although it\n\nacknowledges that there's no Puerto Rico precedent directly on\n\npoint. But it says that under the limited precedent we have, the\n\nfacts of this case show that Rivera knew that her silence and\n\ncontinued employment would constitute acceptance of the\n\narbitration agreement--and that her actions show that she\n\nwillfully accepted. It says that she acknowledged that she read\n\nthe provision that stipulated that her continued employment and\n\n\n - 15 -\n\ffailure to opt out of the agreement would constitute her\n\nacceptance. And, her inaction coupled with her continued\n\nemployment shows that her conduct was informed and voluntary. So,\n\nRivera demonstrated her will to accept AT&T's offer, and is bound\n\nby the arbitration agreement.\n\n ANALYSIS\n\n A. The Framework\n\n To assess these arguments, we first must look to the\n\nframework of Puerto Rico contract law, and note some guideposts of\n\nPuerto Rico law that shape our analysis.\n\n Puerto Rico is unique in many ways, its legal system\n\njust one of them. As a civil law jurisdiction, \"Puerto Rico\n\neschews common law principles of contract interpretation in favor\n\nof its own civil code derived from Spanish law.\" Borschow Hosp.\n\n& Med. Supplies v. Cesar Castillo Inc., 96 F.3d 10, 15 (1st Cir.\n\n1996) (citing Guevara v. Dorsey Labs., Div. of Sandoz, Inc., 845\n\nF.2d 364, 366 (1st Cir. 1988)). So we can't use stateside common\n\nlaw to \"fill[] gaps in the civil law system\" unless the Civil Code\n\nand the Supreme Court of Puerto Rico are silent on the issue.\n\nGuevara, 845 F.2d at 366 (citing Valle v. Am. Int'l Ins. Co., 108\n\nD.P.R. 692, 696-97, 8 P.R. Offic. Trans. 735 (1979)). We turn\n\nfirst to those sources.\n\n\n\n\n - 16 -\n\f To form a valid contract under Puerto Rico law, both\n\nparties must consent to it. See P.R. Laws Ann. tit. 31, § 3391.7\n\nThat consent \"is shown by the concurrence of the offer and\n\nacceptance of the thing and the cause which are to constitute the\n\ncontract.\" P.R. Laws Ann. tit. 31, § 3401. In simple terms:\n\n\"acceptance of an offer is . . . the normal procedure to perfect\n\na contract.\" Producciones Tommy Muñiz Inc. v. Comité Organizador\n\nde Los VIII Panamericanos (COPAN), 113 D.P.R. 517, 13 P.R. Offic.\n\nTrans. 664, 670 (1982). But \"[c]onsent given by error, under\n\nviolence, by intimidation, or deceit shall be void.\" P.R. Laws\n\nAnn. tit. 31, § 3404; see also Dialysis Access Ctr., LLC v. RMS\n\nLifeline, Inc., 638 F.3d 367, 378 (1st Cir. 2011) (discussing how\n\nconsent may be void under Puerto Rico law).\n\n This case presents a twist on the normal question,\n\nthough. In the more typical case, the employee accepts the\n\ncontract by signing on the dotted line, thus leaving little doubt\n\nthat she accepted the agreement. But we consider here whether\n\nRivera accepted the agreement by doing nothing--through her\n\ninaction or silence.8\n\n\n\n\n 7\n You also need to have \"[a] definite object which may be the\nsubject of the contract,\" and \"[t]he cause for the obligation which\nmay be established.\" P.R. Laws Ann. tit. 31, § 3391. But that's\nnot what the parties are arguing about here.\n 8 We note that AT&T doesn't argue that Rivera accepted the\n\nagreement when she acknowledged that she read it. It says that\nshe accepted it when she did not opt out and continued to work.\n\n\n - 17 -\n\f Although that brand of acceptance doesn't find its own\n\ndistinct provision in the Puerto Rican Civil Code, the Supreme\n\nCourt of Puerto Rico has recognized that not all acceptances are\n\nin writing--implied consent to a contract is enough to meet the\n\nPuerto Rico definition of acceptance. See Teachers Annuity & Ret.\n\nSys. v. Sociedad de Gananciales, 115 D.P.R. 277, 15 P.R. Offic.\n\nTrans. 372, 386-87 (1984); see also Colón Gutiérrez v. Registrador,\n\n114 D.P.R. 850, 14 P.R. Offic. Trans. 1095, 1110 (1983) (noting\n\nthat consent to an agreement can be given \"expressly or\n\nimpliedly\"). When it comes to this type of implied consent, \"the\n\ndetermining element . . . is the person's conduct and not the words\n\nused to express such consent.\" Teachers Annuity & Ret. Sys., 115\n\nD.P.R. 277, 15 P.R. Offic. Trans. at 387. That conduct \"should\n\ninequivocally [sic] show the will to consent,\" and the facts\n\n\"cannot be compatible with, another intent, or be subject to many\n\ndifferent interpretations.\" Id. 115 D.P.R. 277, 15 P.R. Offic.\n\nTrans. at 387-88. And the party accepting must have \"adequate\n\nknowledge of the scope of [her] statement\" to be able to adequately\n\nevidence her consent. See Colón Gutiérrez, 114 D.P.R. 850, 14\n\nP.R. Offic. Trans. at 1111. But on the precise question here\n\n(whether silence is acceptance when the offeror conditions that it\n\nwill be), the Supreme Court of Puerto Rico has not spoken.\n\n When the Civil Code and the Supreme Court of Puerto Rico\n\nare silent on an issue, we may forgo the traditional prohibition\n\n\n - 18 -\n\fon use of common law principles and \"employ the common law in its\n\nmultiple and rich versions . . . as a point of reference for\n\ncomparative law.\" Valle, 108 D.P.R. 692, 8 P.R. Offic. Trans. at\n\n738; see also Guevara, 845 F.2d at 366 (applying stateside common\n\nlaw principles when \"useful and persuasive\" and when we \"believe[d]\n\nthe Supreme Court of Puerto Rico would follow essentially the same\n\npath\"). That is particularly true when the Supreme Court of Puerto\n\nRico has, on a particular subject, \"conformed its . . .\n\njurisprudence to common law principles.\" Rodríguez, 54 F.3d at\n\n45. And in the contract-acceptance context, Puerto Rico law\n\n\"mimics the general law of contracts,\" Satellite Broad. Cable,\n\nInc. v. Telefónica de España, S.A., 807 F. Supp. 210, 216 (D.P.R.\n\n1992), and operates in the same way as the \"governing rule in the\n\nUnited States,\" see COPAN, 113 D.P.R. 517, 13 P.R. Offic. Trans.\n\nat 672 (referencing U.S. treatises Williston on Contracts and\n\nCorbin on Contracts). Which is all a long explanation of why we\n\nwill, at times, look to those stateside treatise sources to fill\n\nin the gap here.\n\n B. Addressing Those Arguments\n\n Wave I: Assessing Rivera's Intent in Silence\n\n With that legal outline in mind, we turn to the core of\n\nthis case: do the (undisputed) facts unequivocally show that\n\nRivera manifested her intent to accept AT&T's arbitration\n\nagreement?\n\n\n - 19 -\n\f To tackle that question, we begin with a recount of one\n\nof our prior cases, the closest we've gone to addressing an issue\n\nlike this under Puerto Rico law, which will prove instructive in\n\nassessing the one before us now. In Marrero-García v. Irizzary,\n\n33 F.3d 117 (1st Cir. 1994), we discussed a similar, albeit\n\ndistinct, issue. There, a utility company argued that residents\n\nof a condominium complex impliedly accepted a contract to pay for\n\nwater services that the utility had already begun providing to\n\nthem. See 33 F.3d at 122. The utility company \"repeatedly\n\nrequested the Condominium to place a bond and to register an\n\naccount,\" and informed the residents they needed to take these\n\nactions to become \"registered users.\"9 Id. But when the residents\n\nnever posted a bond or registered with the utility company, the\n\nutility company set up an account for them and started sending\n\nbills for water. The utility company then sued when the residents\n\nrefused to pay. We rejected the utility company's implied-\n\nacceptance argument, holding that the residents' refusal to\n\nregister was not implied consent to the agreement to pay for water\n\nservices, but rather a rejection of that offer. And the key\n\ntakeaway we reap from this case is that \"[a]n offeree's inaction\n\nor 'silence in the face of the offer to sell goods is not ordinarily\n\nan acceptance, because the offeror has no reason to believe from\n\n\n 9\n The utility company didn't add a proviso deeming silence as\nacceptance, like AT&T did here.\n\n\n - 20 -\n\fthe offeree's silence that the offeree promises to buy.'\" Id.\n\n(quoting Farnsworth on Contracts § 3.15).\n\n To be sure, the facts of Rivera's case add a wrinkle to\n\na Marrero-García-style analysis: AT&T specified that Rivera's\n\nsilence would constitute acceptance. Rivera thinks this wrinkle\n\nwill cut in her direction. She's correct that it makes all the\n\ndifference here, but it makes all the difference in a way she\n\ndoesn't imagine: it is actually AT&T's stipulation of silence as\n\nacceptance that tilts the scale away from Rivera's position, and\n\nleads us to the opposite of the conclusion we reached in Marrero-\n\nGarcía. Let us explain.\n\n Of course, as Rivera reminds us, it's basic contract law\n\nthat an offeror cannot unilaterally impose on another party the\n\nobligation to respond and reject their offer. See, e.g., 1 Corbin\n\non Contracts § 3.19 (2018) (\"It should here be plainly set forth\n\nthat an offeror has no power to cause the silence of the offeree\n\nto operate as an acceptance when the offeree does not intend it to\n\ndo so.\"); 2 Williston on Contracts § 6:50 (4th ed. 1993) (\"Merely\n\nsending an unsolicited offer does not impose upon the party\n\nreceiving it any duty to speak or deprive the party of its\n\nprivilege of remaining silent without accepting.\"). But this\n\ngeneral statement of the law is just that--a generality. There\n\nare, as always, exceptions. Indeed, the Restatement (which Rivera\n\ncites in her brief) makes it clear that silence can operate as\n\n\n - 21 -\n\facceptance \"[w]here the offeror has stated or given the offeree\n\nreason to understand that assent may be manifested by silence or\n\ninaction, and the offeree in remaining silent and inactive intends\n\nto accept the offer.\" Restatement (Second) of Contracts\n\n§ 69(1)(b); see also 2 Williston on Contracts § 6:53 (\"If the\n\nsituation for any reason is such that a reasonable person would\n\nconstrue silence as necessarily indicating assent, the offeree who\n\nkeeps silent, knowing that its silence will be misinterpreted,\n\nshould not be allowed to deny the natural interpretation of its\n\nconduct.\"). This aligns with the notion in Puerto Rico that\n\n\"silence could imply the tacit acceptance of an offer when,\n\npursuant to a prior relationship between the parties, the\n\nresponsibility arises for the one receiving the offer to take\n\naffirmative action to reject it.\" Danosa Caribbean, Inc. v.\n\nSantiago Metal Mfg. Corp., 179 D.P.R. 40, No. CC-2008-882, slip\n\nop. at 21 (2010) (Rodríguez Rodríguez, J., dissenting) (citing\n\nCarlos Lasarte, 3 Principios del Derecho Civil 63 (4th ed. 1996)).10\n\n And that's where the scale flips away from Rivera. AT&T\n\nstipulated that if Rivera didn't opt out, it would take it as\n\nthough she opted in. Rivera acknowledged that she read that\n\nprovision (both here in litigation, and when she acknowledged that\n\n\n\n\n 10We requested that the parties file a certified translation\nof this otherwise-untranslated case from the Supreme Court of\nPuerto Rico.\n\n\n - 22 -\n\fshe read the agreement back in 2012). It was laid out nose-to-\n\nface plain and simple in the emails AT&T sent her, as well as in\n\nthe arbitration agreement that she confirmed she received and read.\n\nSo, by acknowledging that she read that proviso, she actually gave\n\nAT&T \"reason to believe from [her] silence that [she] promise[d]\"\n\nto arbitrate her claims, unlike the residents in Marrero-García.\n\nSee 33 F.3d at 122 (quoting Farnsworth on Contracts § 3.15). Thus,\n\nthese facts evidence Rivera's intent to accept the agreement.\n\n Wave II: Was That Intent Unequivocal?\n\n So we move on to wave two of her argument: that even if\n\nshe could accept with her silence in these circumstances,11 the\n\nfacts here don't unequivocally show her intent to accept the\n\ncontract.\n\n Under Puerto Rico law, the facts \"should inequivocally\n\n[sic] show the will to consent . . . [and] cannot be compatible\n\nwith, another intent, or be subject to many different\n\ninterpretations.\" Teachers Annuity & Ret. Sys., 115 D.P.R. 277,\n\n15 P.R. Offic. Trans. at 387-88. Rivera (quite obviously) argues\n\nthat her actions here don't unequivocally show her will to consent.\n\nHer position is twofold. First, she says that \"there is no\n\nscintilla of evidence on the record that [she] ever intended to\n\naccept the offer. In fact, the opposite holds true. When [AT&T]\n\n\n 11\n Indeed, Rivera acknowledges that silence can, \"in certain\ncircumstances,\" constitute acceptance.\n\n\n - 23 -\n\fattempted to enforce the 'contract,' [she] opposed.\" And second\n\nis that the facts only show that she \"acknowledge[d] having\n\nreviewed the document\"; not that she intended to accept it.\n\nAddressing these arguments in turn, they both fail.\n\n First, her objection to arbitration when this litigation\n\ncommenced in 2017 has no bearing on whether she manifested her\n\nintent to accept the agreement back in 2012. We say that for two\n\nreasons: one legal and one logical. On the legal side, it doesn't\n\ncarry weight because it misses the operative timeframe for\n\nassessing her intent. It's basic Puerto Rico contract law that\n\ncontracts are formed and valid \"from the moment\" consent is given.\n\nSee P.R. Laws Ann. tit. 31, §§ 3371, 3375. So, the question is\n\nwhether she manifested her intent to accept the agreement way back\n\nin 2012 when she didn't opt out; not what happened in 2017. Which\n\nis all to say that this argument doesn't get her anywhere. And\n\nthat's not to mention that the logical side of her argument is\n\nbaffling. Disputes of this sort arise in litigation precisely\n\nbecause a party later disputes whether they intended to accept a\n\ncontract. So, if a party's later disavowment of their intent to\n\naccept a contract bore any decisive weight (as Rivera seems to\n\nsuggest it should), it would make analysis unnecessary. This would\n\nmake the cases we just discussed pure excess--which they are not.\n\nCf. generally Teachers Annuity & Ret. Sys., 115 D.P.R. 277, 15\n\nP.R. Offic. Trans. at 387-88 (looking to the facts at the time of\n\n\n - 24 -\n\fthe purported contract formation to determine if implied consent\n\nexisted even though the party later disputed their consent in\n\nlitigation); Cemex De P.R., Inc. v. Ductor, Inc., No. CIV.A. 09-\n\n2254 (GAG), 2010 WL 1727834, at *1 (D.P.R. Apr. 26, 2010) (finding\n\nthat plaintiff sufficiently alleged implied consent even when the\n\nparty later disputed the consent during litigation).\n\n And her second argument (that her intent in clicking the\n\nreview completed button was to show only that she acknowledged\n\nreading the agreement)12 is even more troubling and actually self-\n\ndefeating. Again, it is critical to note that Rivera doesn't\n\nattempt to say that she didn't know her silence would be treated\n\nas opting in. Instead of confronting this head on, though, her\n\nargument tries to leapfrog over her contractual obligations by\n\nrelying on a general rule that AT&T couldn't make her respond.13\n\n\n 12 In the same vein of this argument, Rivera also proposes a\nnew standard we should apply. She says that if AT&T wanted an\narbitration agreement with her, it should have made it so that she\n\"would have taken affirmative steps to clearly and unmistakenly\n[sic] affirm her intent to be bound by an agreement to arbitrate.\"\nBut imposing that requirement would force us to ignore the Supreme\nCourt of Puerto Rico's clear instruction that a contract can be\nformed with implied consent. See generally Teachers Annuity &\nRet. Sys., 115 D.P.R. 277, 15 P.R. Offic. Trans. 372. And we\ncannot do so. See, e.g., Wainwright v. Goode, 464 U.S. 78, 84\n(1983) (\"[T]he views of the state's highest court with respect to\nstate law are binding on the federal courts.\"); Rochester Lincoln-\nMercury, Inc. v. Ford Motor Co., 248 F.3d 46, 48 (1st Cir. 2001)\n(same).\n 13 To support this argument, Rivera provides us with one- or\n\ntwo-sentence excerpts from three Spanish commentators about\nsilence as a mode of acceptance under the Spanish Civil Code.\nInitially, the translations were made only by her counsel, which\n\n\n - 25 -\n\fBut this argument strikes out just as quickly as the first, because\n\nit glances over the exception (rooted in notions of good faith)\n\nthat aims to root out the type of maneuvers she's trying to make\n\nhere: \"the offeree who keeps silent, knowing that [her] silence\n\nwill be misinterpreted, should not be allowed to deny the natural\n\ninterpretation of [her] conduct.\" 2 Williston on Contracts § 6:53.\n\n That exception is especially pertinent in situations\n\nlike this (just as the Restatement, Corbin, and Williston have\n\nnoted14), where \"given a certain relationship between two people,\n\nthe current way of proceeding implies the duty to speak.\" Danosa\n\n\n\n\nwas out of compliance with our Local Rule requiring certified\ntranslations of Spanish documents. See 1st Cir. Local R. 30.0(e).\nIn her reply brief, Rivera provided certified translations of those\nthree snippets, but not the broader context from which they came.\nAnd, as we've said in the past, isolated excerpts from treatises\nnot translated into English are not useful support. See, e.g.,\nUnited States v. Ramos-González, 775 F.3d 483, 505 & n.26 (1st\nCir. 2015) (noting that a counsel-translated sentence from a\nSpanish-language treatise on Puerto Rico's penal code, not\notherwise available in English, is not \"useful support\" for an\nargument). Especially given the potential for these excerpts to\nbe read out of context, we decline to use them here.\n 14 See Restatement (Second) of Contracts § 69(1)(c) (noting\n\nthe exception where silence is acceptance \"because of previous\ndealings or otherwise, it is reasonable that the offeree should\nnotify the offeror if he does not intend to accept\"); 1 Corbin on\nContracts § 3.18 (\"Often, however, silence coupled with conduct or\nwith expectations engendered by a prior relationship can\nreasonably be understood by the offeror as an acceptance.\"); 2\nWilliston on Contracts § 6:50 (noting that \"the relationship\nbetween the parties or other circumstances surrounding the\ntransaction may be such as to justify the offeror in expecting a\nreply, and, therefore, in assuming that silence in fact does\nindicate assent to its proposal\").\n\n\n - 26 -\n\fCaribbean, 179 D.P.R. 40, slip op. at 21 (Rodríguez Rodríguez, J.,\n\ndissenting) (quoting Lasarte, 3 Principios del Derecho Civil 63).\n\n Unlike the unsolicited offer-by-mail to which Rivera\n\ntries to liken this case, this wasn't an offer made by a stranger.\n\nRivera and AT&T were engaged in a long-standing, close legal\n\nrelationship as employee and employer. That relationship--one in\n\nwhich AT&T and its employees regularly communicated company\n\nbusiness with one another via email15--implicates Rivera's\n\nknowledge that she had the duty to speak and that her choice not\n\nto would be reasonably interpreted by AT&T as acceptance. Cf.\n\nCircuit City Stores, Inc. v. Najd, 294 F.3d 1104, 1109 (9th Cir.\n\n2002) (O'Scannlain, J.) (noting in a very similar context under\n\nCalifornia law that the employee and employer \"were not two typical\n\nparties contracting at arm's length,\" and that the employee had a\n\nresponsibility to affirmatively opt out if he didn't want to\n\naccept). And when \"the one who can and should speak does not do\n\nso, it must be deemed that [s]he consents for the sake of good\n\nfaith . . . because in such cases, it is natural and normal to\n\nmanifest dissent.\" Danosa Caribbean, 179 D.P.R. 40, slip op. at\n\n21 (Rodríguez Rodríguez, J., dissenting) (emphasis added) (quoting\n\nLasarte, 3 Principios del Derecho Civil 63). So absent her\n\ndissent, the natural interpretation of her conduct is that she\n\n\n 15\n AT&T communicated at least twenty corporate policies to its\nemployees in the year prior to the arbitration proposal.\n\n\n - 27 -\n\faccepted. And that must stand. Thus, we agree with the district\n\ncourt that Rivera impliedly accepted this arbitration agreement\n\nand is bound by it.\n\n Wave III: A Heightened Standard of Acceptance\n\n But wait, Rivera has two alternative arguments to try to\n\nsteer us back to her side. She calls this agreement both a waiver\n\nof substantive rights and a forum selection clause. And she\n\ncontends that under Puerto Rico law, this means that a heightened\n\nstandard of acceptance should apply to the agreement. That is,\n\nstandard modes of consent aren't enough to accept this type of\n\nagreement. But unfortunately for Rivera, these arguments don't\n\nmove the needle in her direction.\n\n First, she argues that a heightened standard of contract\n\nacceptance should apply here because the agreement is a waiver of\n\na substantive right (the substantive right being her right to a\n\njury trial). And, under Puerto Rico law, \"such renunciation[s] of\n\nrights . . . must be clear, conclusive, express, and unequivocal.\"\n\nQuiñones Quiñones v. Quiñones Irizarry, 91 D.P.R. 225, 91 P.R.R.\n\n217, 257 (1964).\n\n But even assuming she waived a substantive right with\n\nthis agreement--and a jury trial is decidedly a procedural right,\n\nsee, e.g., Libretti v. United States, 516 U.S. 29, 53-54 (1995)\n\n(Souter, J., concurring) (recognizing the right to a jury trial is\n\na procedural right)--her argument smacks up against one of the\n\n\n - 28 -\n\fcore principles of the FAA: a state (or territory) cannot apply\n\nany standard to an arbitration agreement that it does not apply to\n\ncontracts in general, see Soto v. State Indus. Prods., Inc., 642\n\nF.3d 67, 74 (1st Cir. 2011) (\"[W]hile Puerto Rico may impose\n\nspecial restrictions on noncompetition agreements, it is preempted\n\nfrom imposing special restrictions on arbitration agreements.\");\n\nsee also Doctor's Assocs., Inc., 517 U.S. at 687 (noting that with\n\nthe FAA, \"Congress precluded States from singling out arbitration\n\nprovisions for suspect status, requiring instead that such\n\nprovisions be placed 'upon the same footing as other contracts'\").\n\n And that Supreme Court command also torpedoes her second\n\nargument that this supposed \"forum selection\" agreement16\n\nmanifesting as an arbitration agreement can be void for public\n\npolicy. She says that in Puerto Rico, forum selection agreements\n\nare unenforceable if: \"(1) they were not freely negotiated or\n\nwere the result of overweening bargaining power; or (2) they\n\ncontravene a strong public policy.\" But again, even assuming for\n\nthe sake of argument that Rivera can meet one of these grounds,\n\nunder the FAA's protective grasp, an arbitration agreement can be\n\nvoided only on \"generally applicable contract defense[]\" grounds\n\nthat would apply to all other contracts. Doctor's Assocs., Inc.,\n\n\n\n\n 16 By this, we mean an agreement between parties specifying\nwhere they'll duke out their legal disputes. See, e.g., Marra v.\nPapandreou, 216 F.3d 1119, 1123 (D.C. Cir. 2000).\n\n\n - 29 -\n\f517 U.S. at 687. And although Puerto Rico can hold forum selection\n\nclauses to a higher standard, it \"is preempted from imposing\n\nspecial restrictions on arbitration agreements.\" See Soto, 642\n\nF.3d at 74. So her final argument falls flat.\n\n C. Postscript\n\n Before we sum up, we add one last point. The careful\n\nreader will notice that we reach our ultimate conclusion on the\n\nkey issue here (whether Rivera impliedly consented to the\n\narbitration agreement) under a different legal standard than the\n\ndistrict court.17 And on that subject, we add a postscript.\n\n The district court judge said the focal point of the\n\nlegal question was \"whether AT&T gave [Rivera] explicit notice\n\nthat all disputes would be solved by arbitration.\" Rivera-Colón,\n\n261 F. Supp. 3d at 256 (citing García-Clara v. AIG Ins. Co. P.R.,\n\nNo. CV 15-1784CCC, 2016 WL 1261058 (D.P.R. 2016)). That test, in\n\nour view, misses the point. The contract formation question here\n\nis whether Rivera accepted the contract--not whether she was merely\n\non notice of the contract's existence.\n\n The district court (and the García-Clara court on which\n\nit relied) seems to have misconstrued our holdings in Campbell v.\n\nGeneral Dynamics Government Systems Corp., 407 F.3d 546 (1st Cir.\n\n\n 17Again, we're free to take this different route under de\nnovo review because we're free to \"affirm on any ground appearing\nin the record--including one that the [district court] judge did\nnot rely on.\" Lang, 813 F.3d at 454.\n\n\n - 30 -\n\f2005), and Rosenberg v. Merrill Lynch, Pierce, Fenner & Smith,\n\nInc., 170 F.3d 1 (1st Cir. 1999). In those cases, the question\n\nwas, in fact, one of notice. They turned on whether the employer\n\ngave the employees sufficient notice that certain statutory claims\n\n(those under the Americans with Disabilities Act, 42 U.S.C.\n\n§§ 12101, et seq.) would be covered under an arbitration agreement.\n\nAnd that was so important because the ADA has a specific provision\n\nthat limits arbitration of claims to situations when it would be\n\n\"appropriate.\" See 42 U.S.C. § 12212. So that was relevant to\n\nthe arbitrability of the particular claims at issue there, not the\n\narbitrability of all claims under the sun. But here, the parties\n\ndon't dispute that the particular claims are arbitrable. The only\n\nquestion is whether a valid arbitration agreement existed in the\n\nfirst place, which means that the question is one of contract\n\nacceptance--not notice. See Campbell, 407 F.3d at 554 (explaining\n\nthat the questions of whether there was a valid arbitration\n\nagreement and whether the parties had notice that ADA claims were\n\ncovered under it were \"independent, yet overlapping, issues\").\n\n WRAP-UP\n\n Our work done, and finding, as we do, that the district\n\ncourt got the outcome right, we affirm the order compelling\n\narbitration. Costs to appellees. See Fed. R. App. P. 39(a)(2).\n\n\n\n\n - 31 -\n[END_CASE]", "role": "user" } ]
4,582,214
Maria Leticia GARCIA-AGUILAR, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.
Garcia-Aguilar v. Sessions
2019-01-16
18-1086P
U.S. Court of Appeals for the First Circuit
{"judges": "Thompson, Selya, Barron", "parties": "", "opinions": [{"author": "SELYA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1086\n\n MARIA LETICIA GARCIA-AGUILAR,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Thompson, Selya, and Barron,\n Circuit Judges.\n\n\n Randy Olen on brief for petitioner.\n Joseph H. Hunt, Assistant Attorney General, Civil Division,\nErnesto H. Molina, Jr., Deputy Director, Office of Immigration\nLitigation, and Nancy N. Safavi, Trial Attorney, Office of\nImmigration Litigation, on brief for respondent.\n\n\n January 16, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions, III as the respondent.\n\f SELYA, Circuit Judge. The petitioner, Maria Leticia\n\nGarcia-Aguilar, is a Mexican national. She seeks judicial review\n\nof a decision of the Board of Immigration Appeals (BIA) denying\n\nher untimely motion to reopen removal proceedings — a motion\n\ngrounded upon her claim that country conditions in her native land\n\nhad materially changed, thus making her newly eligible for asylum.\n\nAfter careful consideration, we deny the petition.\n\n We set the stage. The petitioner entered the United\n\nStates illegally in 2005 near El Paso, Texas. Following a 2007\n\nraid at the factory where she worked, the Department of Homeland\n\nSecurity initiated removal proceedings against her. The\n\npetitioner denied the factual allegations underpinning the\n\ngovernment's case for removal. Relatedly, she moved to suppress\n\nsome of the evidence upon which the government sought to rely,\n\nclaiming that the evidence had been procured in violation of her\n\nconstitutional rights.\n\n On August 11, 2009, the petitioner's first merits\n\nhearing was held before an immigration judge (IJ). The IJ denied\n\nthe motion to suppress, ordered the petitioner removed to Mexico,\n\nand granted her the privilege of voluntary departure. The\n\npetitioner appealed to the BIA, which vacated the IJ's decision\n\nand remanded the case for reconsideration of the motion to\n\nsuppress, including the underlying constitutional issues.\n\n\n\n\n - 2 -\n\f The petitioner had another merits hearing on February\n\n17, 2012. The IJ reconsidered facts pertinent to the petitioner's\n\nmotion to suppress and determined that the evidence used against\n\nher was admissible. In the end, the results of this second merits\n\nhearing reprised the results of the petitioner's first merits\n\nhearing: on February 1, 2013, the IJ denied the petitioner's motion\n\nto suppress, ordered her removed, and granted voluntary departure.\n\n Once again, the petitioner appealed the IJ's decision to\n\nthe BIA. Nearly a year later, the BIA upheld the IJ's decision.\n\nUndaunted, the petitioner sought judicial review. See 8 U.S.C.\n\n§ 1252(b)(4). On November 25, 2015, we denied her petition. See\n\nGarcia-Aguilar v. Lynch, 806 F.3d 671, 677 (1st Cir. 2015).\n\n The matter did not end there. Almost two years later\n\n(on August 28, 2017), the petitioner filed a motion to reopen,\n\narguing that a dramatic shift in conditions in Mexico —\n\nspecifically, an increase in kidnappings and murders due to\n\nviolence associated with drug cartels and gangs — made her newly\n\neligible for asylum. In support of her nascent asylum claim, she\n\nalleged a fear of persecution based on her imputed \"American\n\nnationality.\" To flesh out this claim, she further alleged that\n\nshe had lived in the United States since 2005; that she was the\n\nmother of an American-born child; and that she had an older child\n\nwho, though born in Mexico, had resided in the United States since\n\ninfancy.\n\n\n - 3 -\n\f The BIA denied the motion to reopen. It noted that the\n\nmotion was untimely and went on to hold that the evidence that the\n\npetitioner submitted failed to achieve the level of proof needed\n\nfor the granting of an untimely motion to reopen. In the BIA's\n\nview, the submitted evidence did \"not establish materially changed\n\ncircumstances or changed country conditions arising in Mexico\n\nsince [the petitioner's] merits hearing below.\" Taking a belt-\n\nand-suspenders approach, the BIA also concluded that the\n\npetitioner had failed to explain how her imputed American\n\nnationality would make her risk of persecution different from that\n\nof the general population in Mexico. So, too, the BIA concluded\n\nthat the petitioner had failed to show a nexus between the\n\npersecution that she allegedly feared and a statutorily protected\n\nground for asylum. See 8 U.S.C. § 1158(b)(1)(B)(i).\n\n This timely petition for judicial review ensued. In it,\n\nthe petitioner seeks review only of the BIA's denial of her motion\n\nto reopen.\n\n Motions to reopen are disfavored in immigration\n\npractice. See Sihotang v. Sessions, 900 F.3d 46, 48 (1st Cir.\n\n2018); Xiao He Chen v. Lynch, 825 F.3d 83, 86 (1st Cir. 2016).\n\nAfter all, reopening a proceeding is \"contrary to 'the compelling\n\npublic interests in finality and the expeditious processing of\n\n[removal] proceedings.'\" Raza v. Gonzales, 484 F.3d 125, 127 (1st\n\nCir. 2007) (quoting Roberts v. Gonzales, 422 F.3d 33, 35 (1st Cir.\n\n\n - 4 -\n\f2005)). Despite these drawbacks, motions to reopen are allowed\n\nunder some circumstances. See 8 U.S.C. § 1229a(c)(7).\n\n Withal, those circumstances are narrowly circumscribed.\n\nOf particular pertinence for present purposes, motions to reopen\n\nare time-limited in immigration cases. See id. § 1229a(c)(7)(C)(i)\n\n(providing that such a motion ordinarily must be filed within 90\n\ndays of the final order in the proceeding sought to be reopened);\n\nsee also 8 C.F.R. § 1003.2(c)(2).\n\n The uphill climb that a petitioner faces when seeking to\n\nreopen removal proceedings — steep in any event — is steeper still\n\nwhere, as here, she seeks to reopen after the time for moving to\n\nreopen has expired. See Sihotang, 900 F.3d at 48. In such\n\ncircumstances, the petitioner must jump through two hoops. First,\n\nshe must adduce material evidence, previously unavailable, showing\n\nchanged country conditions in her homeland. See 8 C.F.R.\n\n§ 1003.2(c)(3)(ii); Sugiarto v. Holder, 761 F.3d 102, 103 (1st\n\nCir. 2014). Second, she must make out a prima facie case of\n\neligibility for the substantive relief sought. See Sihotang, 900\n\nF.3d at 50.\n\n \"We afford the BIA 'wide latitude in deciding whether to\n\ngrant or deny such a motion'\" and review its decision only for\n\nabuse of discretion. Id. at 49 (quoting Bbale v. Lynch, 840 F.3d\n\n63, 66 (1st Cir. 2016)). To prevail under this deferential\n\nstandard, \"the petitioner must show that the BIA either 'committed\n\n\n - 5 -\n\fan error of law or exercised its judgment in an arbitrary,\n\ncapricious, or irrational manner.'\" Id. at 50 (quoting Bbale, 840\n\nF.3d at 66).\n\n Here, the final agency order was dated January 15, 2014,\n\nand the motion to reopen was filed more than three years later.\n\nThus, the motion to reopen was well out of time. See 8 U.S.C.\n\n§ 1229a(c)(7)(C)(i); 8 C.F.R. § 1003.2(c)(2).\n\n To satisfy the first requirement, the petitioner — who\n\nbears the burden of proof — must submit evidence of changed country\n\nconditions material to the underlying substantive relief that she\n\nseeks; show that such evidence was unavailable or undiscoverable\n\nduring the prior proceedings; and show that the change was more\n\nthan a continuation of previously existing conditions. See Xiao\n\nHe Chen, 825 F.3d at 86-87; see also Raza, 484 F.3d at 127. To\n\ndetermine whether the petitioner has carried this multifaceted\n\nburden, the BIA is obligated to compare \"evidence of country\n\nconditions submitted with the motion to those that existed at the\n\ntime of the merits hearing.\" Sihotang, 900 F.3d at 50 (quoting\n\nSánchez-Romero v. Sessions, 865 F.3d 43, 46 (1st Cir. 2017)).\n\n Here, however, there is a stumbling block: before\n\nembarking upon our analysis, we must identify the particular merits\n\nhearing that forms the baseline for assessing the existence vel\n\nnon of changed country conditions. This uncertainty arises out of\n\nthe fact that the petitioner had two separate merits hearings\n\n\n - 6 -\n\fbefore the IJ, resulting in two separate decisions. Her first\n\nmerits hearing took place in 2009 and her second merits hearing\n\ntook place in 2012. Each of these hearings culminated in an order\n\nof removal. When it denied the petitioner's motion to reopen, the\n\nBIA did not distinguish between these two merits hearings but,\n\nrather, referred generically to the \"merits hearing below.\" By\n\nthe same token, the petitioner does not identify which hearing she\n\nviews as the operative one.\n\n Logic suggests that the more recent (2012) merits\n\nhearing should establish the baseline for the petitioner's motion\n\nto reopen. The government agrees: its brief leaves no doubt that\n\nit considers the 2012 hearing as the baseline hearing. Indeed,\n\nits brief does not so much as mention the 2009 merits hearing.\n\nThe petitioner had an opportunity to file a reply brief contesting\n\nthis view, see Fed. R. App. P. 31(a)(1), but she chose not to do\n\nso. What is more, she acknowledges that the overwhelming bulk of\n\nthe country conditions information submitted to the BIA depicts\n\nchanges in Mexico that have taken place during the five years next\n\npreceding — a time span roughly equivalent to the period beginning\n\nwith the 2012 merits hearing and ending with the filing of the\n\n2017 motion to reopen. Against this backdrop, we conclude that\n\nthe 2012 merits hearing sets the baseline for the \"changed country\n\nconditions\" inquiry.\n\n\n\n\n - 7 -\n\f With this baseline in place, we turn to the petitioner's\n\nmotion to reopen. In that motion, the petitioner indicated that\n\nthe substantive relief sought was asylum. The fact that she had\n\nnot sought asylum during the earlier removal proceedings does not,\n\nin and of itself, pretermit her claim. After all, an alien may\n\n\"apply or reapply for asylum\" in a motion to reopen. 8 C.F.R.\n\n§ 1003.2(c)(3)(ii). It follows that the petitioner had a right to\n\nadvance her claim for asylum for the first time in her motion to\n\nreopen. See Smith v. Holder, 627 F.3d 427, 439 n.13 (1st Cir.\n\n2010).\n\n Because the petitioner did not seek asylum at all during\n\nthe 2012 merits hearing, the record of that hearing contains no\n\ndirect evidence of country conditions then existing in Mexico.\n\nThis does not mean, though, that such evidence was either\n\nunavailable or undiscoverable. Indeed, the petitioner has not\n\nsuggested that accurate information concerning country conditions\n\nin Mexico was either unavailable to her or undiscoverable by her\n\nat the time of the 2012 merits hearing. And in any event, the\n\npetitioner's 2017 submissions to the BIA indicate with sufficient\n\nclarity that gang and drug-cartel violence (including murders and\n\nkidnappings) in Mexico was both prevalent and well-publicized at\n\nand before the time of the 2012 merits hearing.1\n\n\n 1\n It is true that many of the reports and articles proffered\nby the petitioner were published in 2014 or thereafter. But\n\n\n - 8 -\n\f Nor does the petitioner deny that conditions in Mexico\n\nwere going downhill as early as 2011. Rather, she argues that\n\ncountry conditions grew increasingly grim between the date of the\n\n2012 merits hearing and the date on which she moved to reopen. To\n\nbuttress her contention that conditions in Mexico deteriorated\n\nduring the relevant period, the petitioner submitted an array of\n\nreports from government agencies and advocacy groups, along with\n\nmedia articles. These materials, collectively, describe the\n\nparlous conditions resulting from drug and gang violence in Mexico.\n\n This proffer falls short. Although some of the submitted\n\ndocuments depict an increase in the rate of murders and kidnappings\n\nbeginning around 2015, others describe the violence as\n\nintensifying around 2011 and persisting since that time. For\n\nexample, one such article not only noted an uptick in murders in\n\n2016 but also noted that the rate of killings was lower than it\n\nwas \"in the first halves of 2011 and 2012, when the drug war's\n\nviolence\" peaked. Other articles support this statement, relating\n\nthat there were 27,213 murders in 2011, 20,670 murders in 2014,\n\nand around 23,000 murders in 2016. So, too, with respect to\n\nkidnappings, another report, published in March of 2017, commented\n\nthat \"Mexico has consistently featured in the top kidnapping\n\n\nnothing indicates that the facts summarized in those reports and\narticles, insofar as they reflect conditions existing in and around\n2012, were either unavailable or undiscoverable at the time of the\npetitioner's 2012 merits hearing.\n\n\n - 9 -\n\fhotspots globally for several years.\" Here, as in Sánchez-Romero\n\n— a case that also considered evidence of gang-related violence in\n\nMexico — the proffered documents do not clearly \"take us out of\n\nthe realm of bad conditions that persist and into the realm of\n\nchanged conditions.\" 865 F.3d at 47.\n\n We add a coda. Even though there may have been an uptick\n\nin violence between 2012 and 2017, the petitioner's burden was to\n\nshow more than just an incremental change in country conditions:\n\nshe had to show a material change in country conditions. See\n\nMejía-Ramaja v. Lynch, 806 F.3d 19, 21 (1st Cir. 2015); Haizem Liu\n\nv. Holder, 727 F.3d 53, 57 (1st Cir. 2013); Smith, 627 F.3d at\n\n435-36. In this regard, materiality has two dimensions. First,\n\nthe evidence must show a degree of change that is sufficiently\n\nsubstantial to be material. See Tawadrous v. Holder, 565 F.3d 35,\n\n38 (1st Cir. 2009). Second, the evidence must be such as to\n\ndemonstrate a change that is material to the underlying substantive\n\nrelief that the petitioner seeks (here, asylum). See Raza, 484\n\nF.3d at 127.\n\n On this record, it was within the BIA's discretion to\n\nconclude that the petitioner had not carried either aspect of her\n\nburden. To satisfy the first aspect, she would have had to show\n\na material increase in the incidence of violence, see Sánchez-\n\nRomero, 865 F.3d at 46-47, and the BIA found (at least implicitly)\n\nthat she failed to do so. To satisfy the second aspect, the\n\n\n - 10 -\n\fpetitioner would need to show that any change in country conditions\n\nwould impact her uniquely because of her imputed American\n\nnationality. See Smith, 627 F.3d at 435-36; Raza, 484 F.3d at\n\n127-28. Here, however, her submissions wholly fail to make such\n\na showing. As late as 2017, the State Department Country\n\nConditions Report, introduced by the petitioner, noted the absence\n\nof any \"evidence that criminal organizations have targeted U.S.\n\ncitizens based on their nationality.\"\n\n In sum, we discern neither an error of law nor an abuse\n\nof the BIA's wide discretion. The documents that the petitioner\n\nproffered plausibly may be read to suggest \"a persistent problem\n\nrather than a recent change.\" Sugiarto, 761 F.3d at 104.\n\nMoreover, those documents do not forge anything resembling a solid\n\nlink between an alleged change in country conditions and the\n\npetitioner's underlying claim for asylum. For these reasons, we\n\ncannot say that the BIA acted erroneously, arbitrarily,\n\ncapriciously, or irrationally in determining that the petitioner\n\nfailed to demonstrate a material change in country conditions.\n\n In an effort to blunt the force of this reasoning, the\n\npetitioner asserts that the BIA ignored her evidentiary\n\nsubmissions. In her counsel's words, the BIA \"offer[ed] no\n\nindication that the evidence was considered carefully, or even at\n\nall.\"\n\n\n\n\n - 11 -\n\f We do not agree. An agency is not required to parse an\n\nalien's submissions one by one and cite book and verse when\n\nrejecting the alien's conclusions. See Raza, 484 F.3d at 128. As\n\nrelevant here, the BIA was under no obligation to dismantle the\n\npetitioner's proffer and separately analyze the component parts of\n\nthat proffer. See Sugiarto, 761 F.3d at 104. \"It is enough if\n\nthe agency fairly considers the points raised by the complainant\n\nand articulates its decision in terms adequate to allow a reviewing\n\ncourt to conclude that the agency has thought about the evidence\n\nand the issues and reached a reasoned conclusion.\" Raza, 484 F.3d\n\nat 128; cf. Fen Tjong Lie v. Holder, 729 F.3d 28, 30 (1st Cir.\n\n2013) (observing that even though \"[t]he BIA's decision was concise\n\n. . . that does not make it cursory\").\n\n The BIA's decision passes muster under this standard.\n\nIts decision refers explicitly to various items of evidence\n\nsubmitted by the petitioner and offers a reasoned basis for denying\n\nthe motion. On this record, it is rank speculation to assert that\n\nthe BIA failed to consider the materials submitted by the\n\npetitioner. And it is equally speculative to assert that the BIA\n\nrejected the petitioner's argument for any reason other than its\n\nconclusion that the argument was unpersuasive. No more was\n\nexigible.\n\n\n\n\n - 12 -\n\f We need go no further.2 For the reasons elucidated\n\nabove, the petition for judicial review is\n\n\n\nDenied.\n\n\n\n\n 2 Because the BIA supportably found that the petitioner failed\nto carry her threshold burden of showing materially changed country\nconditions, we need not reach other issues such as those pertaining\nto the petitioner's \"nexus\" showing and her prima facie case for\nasylum.\n\n\n - 13 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359467/", "author_raw": "SELYA, Circuit Judge"}]}
THOMPSON
SELYA
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582214/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Maria Leticia GARCIA-AGUILAR, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1086\n\n MARIA LETICIA GARCIA-AGUILAR,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Thompson, Selya, and Barron,\n Circuit Judges.\n\n\n Randy Olen on brief for petitioner.\n Joseph H. Hunt, Assistant Attorney General, Civil Division,\nErnesto H. Molina, Jr., Deputy Director, Office of Immigration\nLitigation, and Nancy N. Safavi, Trial Attorney, Office of\nImmigration Litigation, on brief for respondent.\n\n\n January 16, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions, III as the respondent.\n\f SELYA, Circuit Judge. The petitioner, Maria Leticia\n\nGarcia-Aguilar, is a Mexican national. She seeks judicial review\n\nof a decision of the Board of Immigration Appeals (BIA) denying\n\nher untimely motion to reopen removal proceedings — a motion\n\ngrounded upon her claim that country conditions in her native land\n\nhad materially changed, thus making her newly eligible for asylum.\n\nAfter careful consideration, we deny the petition.\n\n We set the stage. The petitioner entered the United\n\nStates illegally in 2005 near El Paso, Texas. Following a 2007\n\nraid at the factory where she worked, the Department of Homeland\n\nSecurity initiated removal proceedings against her. The\n\npetitioner denied the factual allegations underpinning the\n\ngovernment's case for removal. Relatedly, she moved to suppress\n\nsome of the evidence upon which the government sought to rely,\n\nclaiming that the evidence had been procured in violation of her\n\nconstitutional rights.\n\n On August 11, 2009, the petitioner's first merits\n\nhearing was held before an immigration judge (IJ). The IJ denied\n\nthe motion to suppress, ordered the petitioner removed to Mexico,\n\nand granted her the privilege of voluntary departure. The\n\npetitioner appealed to the BIA, which vacated the IJ's decision\n\nand remanded the case for reconsideration of the motion to\n\nsuppress, including the underlying constitutional issues.\n\n\n\n\n - 2 -\n\f The petitioner had another merits hearing on February\n\n17, 2012. The IJ reconsidered facts pertinent to the petitioner's\n\nmotion to suppress and determined that the evidence used against\n\nher was admissible. In the end, the results of this second merits\n\nhearing reprised the results of the petitioner's first merits\n\nhearing: on February 1, 2013, the IJ denied the petitioner's motion\n\nto suppress, ordered her removed, and granted voluntary departure.\n\n Once again, the petitioner appealed the IJ's decision to\n\nthe BIA. Nearly a year later, the BIA upheld the IJ's decision.\n\nUndaunted, the petitioner sought judicial review. See 8 U.S.C.\n\n§ 1252(b)(4). On November 25, 2015, we denied her petition. See\n\nGarcia-Aguilar v. Lynch, 806 F.3d 671, 677 (1st Cir. 2015).\n\n The matter did not end there. Almost two years later\n\n(on August 28, 2017), the petitioner filed a motion to reopen,\n\narguing that a dramatic shift in conditions in Mexico —\n\nspecifically, an increase in kidnappings and murders due to\n\nviolence associated with drug cartels and gangs — made her newly\n\neligible for asylum. In support of her nascent asylum claim, she\n\nalleged a fear of persecution based on her imputed \"American\n\nnationality.\" To flesh out this claim, she further alleged that\n\nshe had lived in the United States since 2005; that she was the\n\nmother of an American-born child; and that she had an older child\n\nwho, though born in Mexico, had resided in the United States since\n\ninfancy.\n\n\n - 3 -\n\f The BIA denied the motion to reopen. It noted that the\n\nmotion was untimely and went on to hold that the evidence that the\n\npetitioner submitted failed to achieve the level of proof needed\n\nfor the granting of an untimely motion to reopen. In the BIA's\n\nview, the submitted evidence did \"not establish materially changed\n\ncircumstances or changed country conditions arising in Mexico\n\nsince [the petitioner's] merits hearing below.\" Taking a belt-\n\nand-suspenders approach, the BIA also concluded that the\n\npetitioner had failed to explain how her imputed American\n\nnationality would make her risk of persecution different from that\n\nof the general population in Mexico. So, too, the BIA concluded\n\nthat the petitioner had failed to show a nexus between the\n\npersecution that she allegedly feared and a statutorily protected\n\nground for asylum. See 8 U.S.C. § 1158(b)(1)(B)(i).\n\n This timely petition for judicial review ensued. In it,\n\nthe petitioner seeks review only of the BIA's denial of her motion\n\nto reopen.\n\n Motions to reopen are disfavored in immigration\n\npractice. See Sihotang v. Sessions, 900 F.3d 46, 48 (1st Cir.\n\n2018); Xiao He Chen v. Lynch, 825 F.3d 83, 86 (1st Cir. 2016).\n\nAfter all, reopening a proceeding is \"contrary to 'the compelling\n\npublic interests in finality and the expeditious processing of\n\n[removal] proceedings.'\" Raza v. Gonzales, 484 F.3d 125, 127 (1st\n\nCir. 2007) (quoting Roberts v. Gonzales, 422 F.3d 33, 35 (1st Cir.\n\n\n - 4 -\n\f2005)). Despite these drawbacks, motions to reopen are allowed\n\nunder some circumstances. See 8 U.S.C. § 1229a(c)(7).\n\n Withal, those circumstances are narrowly circumscribed.\n\nOf particular pertinence for present purposes, motions to reopen\n\nare time-limited in immigration cases. See id. § 1229a(c)(7)(C)(i)\n\n(providing that such a motion ordinarily must be filed within 90\n\ndays of the final order in the proceeding sought to be reopened);\n\nsee also 8 C.F.R. § 1003.2(c)(2).\n\n The uphill climb that a petitioner faces when seeking to\n\nreopen removal proceedings — steep in any event — is steeper still\n\nwhere, as here, she seeks to reopen after the time for moving to\n\nreopen has expired. See Sihotang, 900 F.3d at 48. In such\n\ncircumstances, the petitioner must jump through two hoops. First,\n\nshe must adduce material evidence, previously unavailable, showing\n\nchanged country conditions in her homeland. See 8 C.F.R.\n\n§ 1003.2(c)(3)(ii); Sugiarto v. Holder, 761 F.3d 102, 103 (1st\n\nCir. 2014). Second, she must make out a prima facie case of\n\neligibility for the substantive relief sought. See Sihotang, 900\n\nF.3d at 50.\n\n \"We afford the BIA 'wide latitude in deciding whether to\n\ngrant or deny such a motion'\" and review its decision only for\n\nabuse of discretion. Id. at 49 (quoting Bbale v. Lynch, 840 F.3d\n\n63, 66 (1st Cir. 2016)). To prevail under this deferential\n\nstandard, \"the petitioner must show that the BIA either 'committed\n\n\n - 5 -\n\fan error of law or exercised its judgment in an arbitrary,\n\ncapricious, or irrational manner.'\" Id. at 50 (quoting Bbale, 840\n\nF.3d at 66).\n\n Here, the final agency order was dated January 15, 2014,\n\nand the motion to reopen was filed more than three years later.\n\nThus, the motion to reopen was well out of time. See 8 U.S.C.\n\n§ 1229a(c)(7)(C)(i); 8 C.F.R. § 1003.2(c)(2).\n\n To satisfy the first requirement, the petitioner — who\n\nbears the burden of proof — must submit evidence of changed country\n\nconditions material to the underlying substantive relief that she\n\nseeks; show that such evidence was unavailable or undiscoverable\n\nduring the prior proceedings; and show that the change was more\n\nthan a continuation of previously existing conditions. See Xiao\n\nHe Chen, 825 F.3d at 86-87; see also Raza, 484 F.3d at 127. To\n\ndetermine whether the petitioner has carried this multifaceted\n\nburden, the BIA is obligated to compare \"evidence of country\n\nconditions submitted with the motion to those that existed at the\n\ntime of the merits hearing.\" Sihotang, 900 F.3d at 50 (quoting\n\nSánchez-Romero v. Sessions, 865 F.3d 43, 46 (1st Cir. 2017)).\n\n Here, however, there is a stumbling block: before\n\nembarking upon our analysis, we must identify the particular merits\n\nhearing that forms the baseline for assessing the existence vel\n\nnon of changed country conditions. This uncertainty arises out of\n\nthe fact that the petitioner had two separate merits hearings\n\n\n - 6 -\n\fbefore the IJ, resulting in two separate decisions. Her first\n\nmerits hearing took place in 2009 and her second merits hearing\n\ntook place in 2012. Each of these hearings culminated in an order\n\nof removal. When it denied the petitioner's motion to reopen, the\n\nBIA did not distinguish between these two merits hearings but,\n\nrather, referred generically to the \"merits hearing below.\" By\n\nthe same token, the petitioner does not identify which hearing she\n\nviews as the operative one.\n\n Logic suggests that the more recent (2012) merits\n\nhearing should establish the baseline for the petitioner's motion\n\nto reopen. The government agrees: its brief leaves no doubt that\n\nit considers the 2012 hearing as the baseline hearing. Indeed,\n\nits brief does not so much as mention the 2009 merits hearing.\n\nThe petitioner had an opportunity to file a reply brief contesting\n\nthis view, see Fed. R. App. P. 31(a)(1), but she chose not to do\n\nso. What is more, she acknowledges that the overwhelming bulk of\n\nthe country conditions information submitted to the BIA depicts\n\nchanges in Mexico that have taken place during the five years next\n\npreceding — a time span roughly equivalent to the period beginning\n\nwith the 2012 merits hearing and ending with the filing of the\n\n2017 motion to reopen. Against this backdrop, we conclude that\n\nthe 2012 merits hearing sets the baseline for the \"changed country\n\nconditions\" inquiry.\n\n\n\n\n - 7 -\n\f With this baseline in place, we turn to the petitioner's\n\nmotion to reopen. In that motion, the petitioner indicated that\n\nthe substantive relief sought was asylum. The fact that she had\n\nnot sought asylum during the earlier removal proceedings does not,\n\nin and of itself, pretermit her claim. After all, an alien may\n\n\"apply or reapply for asylum\" in a motion to reopen. 8 C.F.R.\n\n§ 1003.2(c)(3)(ii). It follows that the petitioner had a right to\n\nadvance her claim for asylum for the first time in her motion to\n\nreopen. See Smith v. Holder, 627 F.3d 427, 439 n.13 (1st Cir.\n\n2010).\n\n Because the petitioner did not seek asylum at all during\n\nthe 2012 merits hearing, the record of that hearing contains no\n\ndirect evidence of country conditions then existing in Mexico.\n\nThis does not mean, though, that such evidence was either\n\nunavailable or undiscoverable. Indeed, the petitioner has not\n\nsuggested that accurate information concerning country conditions\n\nin Mexico was either unavailable to her or undiscoverable by her\n\nat the time of the 2012 merits hearing. And in any event, the\n\npetitioner's 2017 submissions to the BIA indicate with sufficient\n\nclarity that gang and drug-cartel violence (including murders and\n\nkidnappings) in Mexico was both prevalent and well-publicized at\n\nand before the time of the 2012 merits hearing.1\n\n\n 1\n It is true that many of the reports and articles proffered\nby the petitioner were published in 2014 or thereafter. But\n\n\n - 8 -\n\f Nor does the petitioner deny that conditions in Mexico\n\nwere going downhill as early as 2011. Rather, she argues that\n\ncountry conditions grew increasingly grim between the date of the\n\n2012 merits hearing and the date on which she moved to reopen. To\n\nbuttress her contention that conditions in Mexico deteriorated\n\nduring the relevant period, the petitioner submitted an array of\n\nreports from government agencies and advocacy groups, along with\n\nmedia articles. These materials, collectively, describe the\n\nparlous conditions resulting from drug and gang violence in Mexico.\n\n This proffer falls short. Although some of the submitted\n\ndocuments depict an increase in the rate of murders and kidnappings\n\nbeginning around 2015, others describe the violence as\n\nintensifying around 2011 and persisting since that time. For\n\nexample, one such article not only noted an uptick in murders in\n\n2016 but also noted that the rate of killings was lower than it\n\nwas \"in the first halves of 2011 and 2012, when the drug war's\n\nviolence\" peaked. Other articles support this statement, relating\n\nthat there were 27,213 murders in 2011, 20,670 murders in 2014,\n\nand around 23,000 murders in 2016. So, too, with respect to\n\nkidnappings, another report, published in March of 2017, commented\n\nthat \"Mexico has consistently featured in the top kidnapping\n\n\nnothing indicates that the facts summarized in those reports and\narticles, insofar as they reflect conditions existing in and around\n2012, were either unavailable or undiscoverable at the time of the\npetitioner's 2012 merits hearing.\n\n\n - 9 -\n\fhotspots globally for several years.\" Here, as in Sánchez-Romero\n\n— a case that also considered evidence of gang-related violence in\n\nMexico — the proffered documents do not clearly \"take us out of\n\nthe realm of bad conditions that persist and into the realm of\n\nchanged conditions.\" 865 F.3d at 47.\n\n We add a coda. Even though there may have been an uptick\n\nin violence between 2012 and 2017, the petitioner's burden was to\n\nshow more than just an incremental change in country conditions:\n\nshe had to show a material change in country conditions. See\n\nMejía-Ramaja v. Lynch, 806 F.3d 19, 21 (1st Cir. 2015); Haizem Liu\n\nv. Holder, 727 F.3d 53, 57 (1st Cir. 2013); Smith, 627 F.3d at\n\n435-36. In this regard, materiality has two dimensions. First,\n\nthe evidence must show a degree of change that is sufficiently\n\nsubstantial to be material. See Tawadrous v. Holder, 565 F.3d 35,\n\n38 (1st Cir. 2009). Second, the evidence must be such as to\n\ndemonstrate a change that is material to the underlying substantive\n\nrelief that the petitioner seeks (here, asylum). See Raza, 484\n\nF.3d at 127.\n\n On this record, it was within the BIA's discretion to\n\nconclude that the petitioner had not carried either aspect of her\n\nburden. To satisfy the first aspect, she would have had to show\n\na material increase in the incidence of violence, see Sánchez-\n\nRomero, 865 F.3d at 46-47, and the BIA found (at least implicitly)\n\nthat she failed to do so. To satisfy the second aspect, the\n\n\n - 10 -\n\fpetitioner would need to show that any change in country conditions\n\nwould impact her uniquely because of her imputed American\n\nnationality. See Smith, 627 F.3d at 435-36; Raza, 484 F.3d at\n\n127-28. Here, however, her submissions wholly fail to make such\n\na showing. As late as 2017, the State Department Country\n\nConditions Report, introduced by the petitioner, noted the absence\n\nof any \"evidence that criminal organizations have targeted U.S.\n\ncitizens based on their nationality.\"\n\n In sum, we discern neither an error of law nor an abuse\n\nof the BIA's wide discretion. The documents that the petitioner\n\nproffered plausibly may be read to suggest \"a persistent problem\n\nrather than a recent change.\" Sugiarto, 761 F.3d at 104.\n\nMoreover, those documents do not forge anything resembling a solid\n\nlink between an alleged change in country conditions and the\n\npetitioner's underlying claim for asylum. For these reasons, we\n\ncannot say that the BIA acted erroneously, arbitrarily,\n\ncapriciously, or irrationally in determining that the petitioner\n\nfailed to demonstrate a material change in country conditions.\n\n In an effort to blunt the force of this reasoning, the\n\npetitioner asserts that the BIA ignored her evidentiary\n\nsubmissions. In her counsel's words, the BIA \"offer[ed] no\n\nindication that the evidence was considered carefully, or even at\n\nall.\"\n\n\n\n\n - 11 -\n\f We do not agree. An agency is not required to parse an\n\nalien's submissions one by one and cite book and verse when\n\nrejecting the alien's conclusions. See Raza, 484 F.3d at 128. As\n\nrelevant here, the BIA was under no obligation to dismantle the\n\npetitioner's proffer and separately analyze the component parts of\n\nthat proffer. See Sugiarto, 761 F.3d at 104. \"It is enough if\n\nthe agency fairly considers the points raised by the complainant\n\nand articulates its decision in terms adequate to allow a reviewing\n\ncourt to conclude that the agency has thought about the evidence\n\nand the issues and reached a reasoned conclusion.\" Raza, 484 F.3d\n\nat 128; cf. Fen Tjong Lie v. Holder, 729 F.3d 28, 30 (1st Cir.\n\n2013) (observing that even though \"[t]he BIA's decision was concise\n\n. . . that does not make it cursory\").\n\n The BIA's decision passes muster under this standard.\n\nIts decision refers explicitly to various items of evidence\n\nsubmitted by the petitioner and offers a reasoned basis for denying\n\nthe motion. On this record, it is rank speculation to assert that\n\nthe BIA failed to consider the materials submitted by the\n\npetitioner. And it is equally speculative to assert that the BIA\n\nrejected the petitioner's argument for any reason other than its\n\nconclusion that the argument was unpersuasive. No more was\n\nexigible.\n\n\n\n\n - 12 -\n\f We need go no further.2 For the reasons elucidated\n\nabove, the petition for judicial review is\n\n\n\nDenied.\n\n\n\n\n 2 Because the BIA supportably found that the petitioner failed\nto carry her threshold burden of showing materially changed country\nconditions, we need not reach other issues such as those pertaining\nto the petitioner's \"nexus\" showing and her prima facie case for\nasylum.\n\n\n - 13 -\n[END_CASE]", "role": "user" } ]
4,582,651
UNITED STATES of America, Appellee, v. Juan BRAVO-FERNÁNDEZ, Defendant, Appellant. United States of America, Appellee, v. Héctor Martínez-Maldonado, Defendant, Appellant.
United States v. Martinez-Maldonado
2019-01-17
18-1358P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Torruella, Kayatta", "parties": "", "opinions": [{"author": "TORRUELLA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1358\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JUAN BRAVO-FERNÁNDEZ,\n\n Defendant, Appellant.\n ____________________\n\nNo. 18-1370\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n HÉCTOR MARTÍNEZ-MALDONADO,\n\n Defendant, Appellant.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n Martin G. Weinberg, with whom Kimberly Homan, were on brief,\nfor appellant Bravo-Fernández.\n\f Abbe David Lowell, with whom Christopher D. Man and Winston\n& Strawn LLP were on brief, for appellant Martínez-Maldonado.\n Vijay Shanker, U.S. Department of Justice, Criminal Division,\nAppellate Section, with whom Brian A. Benczkowski, Assistant\nAttorney General, Matthew S. Miner, Deputy Assistant Attorney\nGeneral, Peter M. Koski, Public Integrity Section, and Gwendolyn\nAmelia Stamper, Public Integrity Section, were on brief, for\nappellee.\n\n\n\n January 17, 2019\n\n\n\n\n -2-\n\f TORRUELLA, Circuit Judge. Because everything old is new\n\nagain, 1 Defendants Juan Bravo-Fernández (\"Bravo\") and Héctor\n\nMartínez-Maldonado (\"Martínez\") come before us for a third time.\n\nSee United States v. Bravo-Fernández, 790 F.3d 41 (1st Cir. 2015);\n\nUnited States v. Fernández, 722 F.3d 1 (1st Cir. 2013). In this\n\nappeal, they seek to overturn their 2017 convictions for federal\n\nprogram bribery under 18 U.S.C. § 666, arguing primarily that\n\nevidence stipulated to early in the proceedings was insufficient\n\nto convict.\n\n Among the elements of § 666, the government was required\n\nto establish that the entity Martínez represented as an agent, in\n\nthis case the Commonwealth of Puerto Rico, received at least\n\n$10,000 in federal \"benefits\" within the meaning of that statute.\n\nThe government did not meet this burden. Accordingly, we must\n\nreverse defendants' convictions for federal program bribery.\n\n I.\n\n The pertinent facts and procedural background are\n\nexamined in detail in Bravo-Fernández, 790 F.3d at 43-45, and\n\nFernández, 722 F.3d at 6-8, for which we only sketch a high-level\n\noverview of that account here.\n\n\n\n\n1 Peter Allen, Everything Old Is New Again, in Continental\nAmerican (A&M Records 1974).\n\n\n -3-\n\f This case traces its origin to 2010, when Bravo and\n\nMartínez were charged with federal program bribery in violation of\n\n§ 666, among other things. The charges stemmed from payments that\n\nBravo made in 2005 involving a trip to Las Vegas to which he\n\ninvited Martínez, then a Puerto Rico senator. According to the\n\ngovernment, Bravo used the trip to bribe Martínez in exchange for\n\nhis support of pending legislation that would have favored Bravo's\n\nbusiness, Ranger American, a local security company.\n\n Bravo and Martínez were first tried and found guilty of\n\nfederal program bribery in 2011, an outcome which they successfully\n\nchallenged before this court. See Fernández, 722 F.3d at 6, 39.\n\nIn that initial appeal, we ruled that § 666 only criminalizes\n\nbribery, not gratuities, and that the evidence presented at trial,\n\ntogether with the jury instructions, could have led the jury to\n\nimproperly convict on either a \"bribery\" or \"gratuity\" theory.\n\nId. 16-17, 23-26. Because it was insufficiently clear to discern\n\nwhich theory the jury relied on to reach its verdict, we vacated\n\ndefendants' convictions on the § 666 counts and remanded for\n\npotential re-prosecution. Id. at 26-28, 39.\n\n On remand, Bravo and Martínez moved for judgment of\n\nacquittal, arguing that double jeopardy barred their renewed\n\nprosecution. Bravo-Fernández, 790 F.3d at 43, 49. The district\n\ncourt rejected this contention, after which defendants sought\n\n\n -4-\n\frefuge before our court once again. Id. at 43. This time,\n\nhowever, defendants' appeal was unsuccessful and we affirmed the\n\ndistrict court's decision on the double jeopardy issue. Id.\n\nDefendants' further appellate endeavor before the Supreme Court\n\nreached a similar result. See Bravo-Fernández v. United States,\n\n137 S. Ct. 352 (2016).\n\n Bravo and Martínez faced their second trial in May 2017,\n\nand once again a jury found them guilty of federal program bribery\n\nunder § 666. Those proceedings devolved into the instant appeal,\n\nthe latest stage in this case's arduous journey.\n\n II.\n\n We are able to reduce the several questions that have\n\nbeen raised before us2 to the only one that merits our decisional\n\nattention and mandates the outcome of this appeal: Whether the\n\ngovernment introduced evidence at trial to satisfy the\n\njurisdictional element under 18 U.S.C. § 666(b) that the government\n\nentity involved received \"benefits in excess of $10,000 under a\n\nFederal program.\" (emphasis added). Where, as here, defendants\n\nhave preserved a sufficiency challenge, we review de novo a\n\n\n2 Defendants also challenge, among other things, the sufficiency\nof the evidence other than that presented to satisfy the\njurisdictional element, the propriety of the jury instructions,\nsome of the district court's evidentiary rulings, and their\nsentences. Our decision on the sufficiency issue makes it\nunnecessary to reach the merits of such challenges.\n\n\n -5-\n\fdistrict court's denial of their motion for judgment of acquittal.\n\nUnited States v. Acevedo-Hernández, 898 F.3d 150, 161 (1st Cir.\n\n2018).\n\n To maintain a conviction for federal program bribery,\n\nthe government must prove beyond a reasonable doubt that the party\n\nreceiving the bribe was an agent of an entity that \"receives, in\n\nany one year period, benefits in excess of $10,000 under a Federal\n\nprogram involving a grant, contract, subsidy, loan, guarantee,\n\ninsurance, or other form of Federal assistance.\" 18 U.S.C.\n\n§ 666(b). This requirement is often referred to as the\n\n\"jurisdictional element\" of § 666. See, e.g., United States v.\n\nMcLean, 802 F.3d 1228, 1240 (11th Cir. 2015). And not all federal\n\nfunds constitute \"benefits\" under the statute. See Fischer v.\n\nUnited States, 529 U.S. 667, 681 (2000) (\"Any receipt of federal\n\nfunds can, at some level of generality, be characterized as a\n\nbenefit. The statute does not employ this broad, almost limitless\n\nuse of the term.\"); see also United States v. Dubón-Otero, 292\n\nF.3d 1, 7 n.7 (1st Cir. 2002) (acknowledging that there exists\n\n\"compensation of the type excluded by § 666 (c)\" including\n\nsalaries, wages and expenses paid in the usual course of business).\n\nIn Fischer, the Supreme Court explained that only federal monies\n\nthat \"promote[] well-being,\" such as those which provide\n\nindividuals with \"financial help in time of sickness, old age, or\n\n\n -6-\n\funemployment,\" may qualify as \"benefits.\" Fischer, 529 U.S. at\n\n677 (citing Webster's Third New International Dictionary 204\n\n(1971)). Critically, \"[t]o determine whether an organization\n\nparticipating in a federal assistance program receives 'benefits,'\n\nan examination must be undertaken of the program's structure,\n\noperation, and purpose.\" Id. at 681. The government has the\n\nburden of producing adequate evidence for this examination to\n\noccur.\n\n In resolving if the § 666(b) jurisdictional element was\n\nsatisfied, we find it instructive to begin by comparing the\n\nevidence that the government offered on this key element during\n\nthe 2011 trial with that it presented in the 2017 proceedings\n\nleading to this appeal.\n\n At defendants' first trial, the government introduced\n\nevidence specifically tailored to establishing the § 666\n\njurisdictional requirement. An employee of the Puerto Rico\n\nTreasury Department testified for the government that \"the Senate\n\nof Puerto Rico childcare program (known as the Food Program for\n\nthe Care of Children and Adults) receive[d] funding from the\n\nGovernment of the United States.\" United States v. Bravo-\n\nFernández, 828 F. Supp. 2d 441, 455 (D.P.R. 2011), rev'd in part,\n\nvacated in part sub nom. United States v. Fernández, 722 F.3d 1\n\n(1st Cir. 2013). The witness further averred, with the support\n\n\n -7-\n\fof documentation also admitted into evidence, that the Puerto Rico\n\nSenate annually received around $20,000 in federal funds for the\n\nchildcare program during the relevant period. Id. at 456. This\n\nprovided the basis for the district court to conclude in its\n\nresolution of the Rule 29 motion for judgment of acquittal that\n\n\"[t]he federal assistance received by the Senate of Puerto Rico\n\nfor [its] childcare program clearly qualifies as a 'benefit'\n\nprovided under a federal program\" for purposes of § 666(b). Id.\n\n In contrast, the record of the second trial is barren of\n\nevidence showing disbursement of federal \"benefits\" to the Senate\n\nof Puerto Rico or even to the Commonwealth as a whole. All we\n\nhave is a stipulation the parties accorded prior to trial providing\n\nthat \"in fiscal year 2005[,] the Commonwealth of Puerto Rico\n\nreceived more than $10,000 in federal funding. Specifically, from\n\nOctober 1, 2004, to September 30, 2005, the Commonwealth of Puerto\n\nRico received over $4.7 billion in federal funds.\" (emphasis added)\n\nLater, on the first day of trial during a conference about\n\npreliminary jury instructions, the district judge asked counsel\n\nwhether this stipulation allowed him to inform jurors that the\n\n§ 666 jurisdictional element had been met. Counsel for defendant\n\nMartínez responded that the court should not instruct so because\n\n\"the . . . law . . . doesn't equate funds with benefits, and the\n\nstatute says benefits. . . . We have stipulated to the amount of\n\n\n -8-\n\fmoney, but not that [the jurisdictional] element has been\n\nsatisfied.\" Incredibly, this clear warning of things to come went\n\nunattended and the government proceeded to present its case in\n\nchief without introducing any evidence to cover this gaping hole\n\nin its case.\n\n Following the close of the government's case, defendants\n\nmade a Rule 29 motion for a verdict of acquittal in which they\n\nspecifically argued that the government failed to establish the\n\nexistence of $10,000 in benefits under a federal program. The\n\ndistrict court denied this motion without explanation. In\n\ncharging the jury, the district court stated that § 666 only\n\nrequired jurors to find that the Commonwealth received federal\n\n\"funds of more than $10,000.\" No instruction was given on what\n\nconstitutes a benefit, and the word \"benefits\" does not appear\n\neven once throughout the instructions. Counsel for defendant\n\nMartínez objected to the instruction's language, but that\n\nobjection was summarily overruled by the district court.\n\n Given the foregoing, and in keeping with our own\n\nprecedent and that of the Supreme Court, we can only conclude that\n\nthe government failed to meet its burden of establishing that the\n\nentity Martínez represented as an agent received the amount of\n\nbenefits required under § 666(b). The government's arguments to\n\nthe contrary are futile.\n\n\n -9-\n\f First, the government directs us to a paragraph in our\n\n2013 opinion in Fernández, which examined defendants' 2011 trial\n\nand noted that:\n\n [D]uring 2005 -- the year of the charged conduct -- the\n Commonwealth received over $4.7 billion in federal\n funds. Because Martínez . . . [is an] agent[] of the\n Commonwealth, the evidence was sufficient to show that\n [he is an] agent[] of a \"government . . . [that]\n receives, in any one year period, benefits in excess\n of $10,000 under a Federal program.\"\n\n722 F.3d at 9 (quoting 18 U.S.C. § 666(b)). This statement that\n\nthe jurisdictional element was satisfied in defendants' first\n\ntrial, the government purports, should also control here because\n\nof the law of the case doctrine, which \"bars a party from\n\nresurrecting issues that either were, or could have been, decided\n\non an earlier appeal.\" United States v. Matthews, 643 F.3d 9, 12-\n\n13 (1st Cir. 2011) (citation omitted). But our statement in\n\nFernández is not dispositive as it was neither essential to our\n\nholding there nor could the issue now before us have been decided\n\nin that initial appeal. Contrary to what the government contends,\n\ndefendants did not argue about the funds-benefits distinction in\n\ntheir first appeal. See Brief for Appellant Bravo at 25-27, United\n\nStates v. Fernández, 722 F.3d 1 (1st Cir. 2013)(No. 12-1289); Brief\n\nfor Appellant Martínez at 25-28, United States v. Fernández, 722\n\nF.3d 1 (1st Cir. 2013)(No. 12-1290). And they had no reason to\n\ndo so because, as explained above, the government introduced\n\n\n -10-\n\fspecific evidence at that first trial to establish the existence\n\nof the requisite amount of federal benefits. The issue before us\n\nin that case was whether Martínez was an \"agent\" of the\n\nCommonwealth, not whether \"benefits\" as used in the statute were\n\nreceived. Thus, the statement from Fernández the government\n\nrelies on is nothing but dicta that \"lack[s] any binding or\n\npreclusive effect.\" Sexual Minorities Uganda v. Lively, 899 F.3d\n\n24, 29 (1st Cir. 2018).\n\n Second, the government contends that both the Supreme\n\nCourt in Fischer and our decision in Dubón-Otero, 292 F.3d at 4,\n\ncommand an inquiry into the nature of federal funds to determine\n\nif they are benefits under § 666 only when the payments are\n\ndisbursed \"indirectly\" to the receiving entity. This argument is\n\nalso without merit. In fact, the one reference we made in Dubón-\n\nOtero to the distinction between entities that receive payments\n\ndirectly from the federal government and those that do not was\n\nthat \"[i]t makes no difference [whether an agency] received this\n\nmoney indirectly. It is now well established that benefits under\n\n§ 666 are not limited solely to primary target recipients or\n\nbeneficiaries.\" 292 F.3d at 9 (citing United States v. Fischer,\n\n168 F.3d 1273, 1278 (11th Cir. 1999) (\"[T]he plain language of\n\n§ 666(b) does not distinguish between an organization . . . that\n\nreceives 'benefits' directly under a federal program and an\n\n\n -11-\n\forganization . . . that receives 'benefits' as an assignee under\n\na federal program.\")). Indisputably, this language affords no\n\ncredit to the government's theory. Moreover, the reach of Fischer\n\nis not limited to only those cases involving indirect receipt of\n\nfederal monies. To the contrary, the Supreme Court's reasoning\n\nin Fischer, particularly its concern for the proper federal balance\n\nin this type of case, is by its very nature generally applicable.\n\nSee Fischer, 529 U.S. at 681.\n\n In a final attempt to save a sinking ship, the government\n\nasserts that the stipulation specifying the amount of federal funds\n\nreceived by the Commonwealth was sufficient to satisfy the § 666\n\njurisdictional element. The government takes the position that a\n\n\"jury, exercising common sense and relying on general knowledge,\n\ncan reasonably infer that the federal funds constituted\n\n'benefits.'\" It is tempting to agree with the government here.\n\nAs judges who hear cases arising out of federal benefit programs\n\nand who are familiar with how such programs are funded, we are\n\ncertain that there are federal benefit programs that provide far\n\nmore than $10,000 to the Commonwealth and its instrumentalities.\n\nThe question remains, however, whether those programs are funded\n\nby the $4.7 billion in federal funds that go directly to the\n\nCommonwealth. Perhaps the federal benefit programs enjoyed in\n\nPuerto Rico are financed through other federal monies, leaving the\n\n\n -12-\n\f$4.7 billion to be spent on infrastructure, salaries, and other\n\nexpenditures that may or may not constitute \"benefits\" under\n\nFischer? In any event, we see nothing in the record that tells\n\nus whether any juror would certainly know the answer to these\n\nquestions, nor did the government secure a stipulation supplying\n\nsuch answers.\n\n It is unclear, too, where we would stop if we accept the\n\ngovernment's invitation to rely on jurors' knowledge of federal\n\nfunding to fill gaps in the government's proof. Suppose the\n\ngovernment puts in no evidence about any federal funds at all.\n\nCould jurors simply fill-in the gap based on their \"common sense\"\n\nand \"general knowledge\" that large amounts of federal funds are\n\nsent to the Commonwealth government each year?\n\n Under the government's approach, the jurisdictional\n\nelement in many federal criminal cases could be satisfied by\n\nsimilar reliance on jurors' extra-record knowledge. For example,\n\none could claim that any juror would know that all banks are\n\nengaged in, or at least affect, interstate commerce, or that a\n\nbank is likely FDIC insured. Yet, the failure to offer any actual\n\nproof of these relatively obvious jurisdictional facts has\n\nrepeatedly proved fatal to criminal prosecutions. See United\n\nStates v. Leslie, 103 F.3d 1093, 1102-3 (2d Cir. 1997) (reversing\n\nconviction because government \"did not provide even the slenderest\n\n\n -13-\n\fof threads\" upon which to hang the interstate commerce\n\njurisdictional element); United States v. Sliker, 751 F.2d 477,\n\n484 (2d Cir. 1984) (affirming conviction based on oral testimony\n\nof FDIC-insured status, but warning the government of failure to\n\n\"ask the simple question that would avoid the need for judicial\n\nconsideration of what should be a non-problem\"); see also United\n\nStates v. Davis, 726 F.3d 357, 366-7 (2d Cir. 2013) (holding that\n\nthe government had failed to meet its burden by assuming that a\n\nfederal installation on federal land automatically came within\n\nfederal jurisdiction, but affirming after taking judicial notice\n\nof the fact at the government's behest).\n\n We have considered the Third Circuit's recent decision\n\nin United States v. Willis, 844 F.3d 155 (3d Cir. 2016), in which\n\nthe government relied on proof that the Government of the Virgin\n\nIslands received $150 million in federal funds. The Willis court\n\ntook a different route than that urged by the government in this\n\ncase. Rather than relying on juror common sense, the court in\n\nWillis held that federal funds paid to a territorial government\n\nwere a benefit to that government because they \"significantly\n\nsupported the government.\" Id. at 168. We do not see, though, how\n\nthat type of financial support to a local government equates to a\n\n\"benefit\" of the type required by Fischer. As in this case, it\n\ndoes not appear that any federal program was specifically\n\n\n -14-\n\fidentified in Willis, prohibiting the ability to determine, under\n\nFischer's \"benefits\" analysis, whether the funds received by the\n\nGovernment of the Virgin Islands were used for such promotion of\n\nwell-being.\n\n Despite its insistence that the Fischer analysis need\n\nonly be applied if it is \"difficult\" to determine whether the\n\nfederal payments were benefits, the government seems blind to the\n\nfact that without reference to a specific federal program it is\n\nnot only difficult but impossible to make such a determination.\n\nAgain, the stipulation entered between the parties made no\n\nreference to \"benefits\" or, for that matter, to any federal\n\nprogram. The stipulation also did not provide information\n\nregarding the intended or actual use of any portion of the $4.7\n\nbillion in federal funds. It only provided that the \"Commonwealth\n\nof Puerto Rico received over $4.7 billion in federal funds\" during\n\nthe relevant time period. Concluding that such a stipulation\n\nsufficed to satisfy the jurisdictional element would counter the\n\nplain language of § 666(b) requiring proof that the government\n\nentity involved received \"benefits in excess of $10,000 under a\n\nFederal program.\" It would also contravene the government's\n\nburden to put forth evidence about the federal program's\n\n\"structure, operation, and purpose\" in order to make ascertainable\n\nwhether an entity received \"benefits\" under § 666(b). Fischer,\n\n\n -15-\n\f529 U.S. at 681. Most of our sister circuits to have addressed\n\nthis issue agree.3 To hold otherwise and conclude that any receipt\n\nof federal funds is enough to satisfy the jurisdictional element\n\nwould transmute § 666 into the general bribery statute that the\n\nFischer court warned against and \"upset[] the proper federal\n\nbalance.\" Id.\n\n III.\n\n For the reasons explained above, we conclude that the\n\ngovernment failed to establish an essential element of the crime\n\nit charged defendants with. We need not go further and hereby\n\nreverse Bravo's and Martínez's § 666 convictions. We direct the\n\ndistrict court to enter a judgment of acquittal on both charges.\n\n\n\n3 See, e.g., United States v. Paixao, 885 F.3d 1203, 1206 (9th\nCir. 2018) (\"[N]ot all payments under federal programs qualify as\n'benefits' . . . . [T]he inquiry turns on the attributes of the\nfederal program[.]\") (citation omitted); United States v. Pinson,\n860 F.3d 152, 166 (4th Cir. 2017) (\"Because any receipt of federal\nfunds could 'at some level of generality' be characterized as a\nbenefit, . . . the Court provided guidelines to distinguish between\ncovered federal payments ('benefits') and non-covered payments.\");\nUnited States v. McLean, 802 F.3d 1228, 1237 (11th Cir. 2015)\n(\"[T]he government must prove beyond a reasonable doubt that the\nindividual worked for an entit[y] which receive[d] . . . funds\n. . . in connection with programs defined by a sufficiently\ncomprehensive structure, operation, and purpose to merit\ncharacterization of the funds as benefits under § 666(b).\"\n(citation and internal quotation marks omitted)); United States v.\nZyskind, 118 F.3d 113, 115 (2d. Cir. 1997) (\"[T]here must exist a\nspecific statutory scheme authorizing the Federal assistance in\norder to promote or achieve certain policy objectives.\") (quoting\nS. Rep. No. 98-225, at 370 (1983)).\n\n\n -16-", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359904/", "author_raw": "TORRUELLA, Circuit Judge"}]}
HOWARD
TORRUELLA
KAYATTA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582651/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Juan BRAVO-FERNÁNDEZ, Defendant, Appellant. United States of America, Appellee, v. Héctor Martínez-Maldonado, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-17\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1358\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JUAN BRAVO-FERNÁNDEZ,\n\n Defendant, Appellant.\n ____________________\n\nNo. 18-1370\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n HÉCTOR MARTÍNEZ-MALDONADO,\n\n Defendant, Appellant.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n Martin G. Weinberg, with whom Kimberly Homan, were on brief,\nfor appellant Bravo-Fernández.\n\f Abbe David Lowell, with whom Christopher D. Man and Winston\n& Strawn LLP were on brief, for appellant Martínez-Maldonado.\n Vijay Shanker, U.S. Department of Justice, Criminal Division,\nAppellate Section, with whom Brian A. Benczkowski, Assistant\nAttorney General, Matthew S. Miner, Deputy Assistant Attorney\nGeneral, Peter M. Koski, Public Integrity Section, and Gwendolyn\nAmelia Stamper, Public Integrity Section, were on brief, for\nappellee.\n\n\n\n January 17, 2019\n\n\n\n\n -2-\n\f TORRUELLA, Circuit Judge. Because everything old is new\n\nagain, 1 Defendants Juan Bravo-Fernández (\"Bravo\") and Héctor\n\nMartínez-Maldonado (\"Martínez\") come before us for a third time.\n\nSee United States v. Bravo-Fernández, 790 F.3d 41 (1st Cir. 2015);\n\nUnited States v. Fernández, 722 F.3d 1 (1st Cir. 2013). In this\n\nappeal, they seek to overturn their 2017 convictions for federal\n\nprogram bribery under 18 U.S.C. § 666, arguing primarily that\n\nevidence stipulated to early in the proceedings was insufficient\n\nto convict.\n\n Among the elements of § 666, the government was required\n\nto establish that the entity Martínez represented as an agent, in\n\nthis case the Commonwealth of Puerto Rico, received at least\n\n$10,000 in federal \"benefits\" within the meaning of that statute.\n\nThe government did not meet this burden. Accordingly, we must\n\nreverse defendants' convictions for federal program bribery.\n\n I.\n\n The pertinent facts and procedural background are\n\nexamined in detail in Bravo-Fernández, 790 F.3d at 43-45, and\n\nFernández, 722 F.3d at 6-8, for which we only sketch a high-level\n\noverview of that account here.\n\n\n\n\n1 Peter Allen, Everything Old Is New Again, in Continental\nAmerican (A&M Records 1974).\n\n\n -3-\n\f This case traces its origin to 2010, when Bravo and\n\nMartínez were charged with federal program bribery in violation of\n\n§ 666, among other things. The charges stemmed from payments that\n\nBravo made in 2005 involving a trip to Las Vegas to which he\n\ninvited Martínez, then a Puerto Rico senator. According to the\n\ngovernment, Bravo used the trip to bribe Martínez in exchange for\n\nhis support of pending legislation that would have favored Bravo's\n\nbusiness, Ranger American, a local security company.\n\n Bravo and Martínez were first tried and found guilty of\n\nfederal program bribery in 2011, an outcome which they successfully\n\nchallenged before this court. See Fernández, 722 F.3d at 6, 39.\n\nIn that initial appeal, we ruled that § 666 only criminalizes\n\nbribery, not gratuities, and that the evidence presented at trial,\n\ntogether with the jury instructions, could have led the jury to\n\nimproperly convict on either a \"bribery\" or \"gratuity\" theory.\n\nId. 16-17, 23-26. Because it was insufficiently clear to discern\n\nwhich theory the jury relied on to reach its verdict, we vacated\n\ndefendants' convictions on the § 666 counts and remanded for\n\npotential re-prosecution. Id. at 26-28, 39.\n\n On remand, Bravo and Martínez moved for judgment of\n\nacquittal, arguing that double jeopardy barred their renewed\n\nprosecution. Bravo-Fernández, 790 F.3d at 43, 49. The district\n\ncourt rejected this contention, after which defendants sought\n\n\n -4-\n\frefuge before our court once again. Id. at 43. This time,\n\nhowever, defendants' appeal was unsuccessful and we affirmed the\n\ndistrict court's decision on the double jeopardy issue. Id.\n\nDefendants' further appellate endeavor before the Supreme Court\n\nreached a similar result. See Bravo-Fernández v. United States,\n\n137 S. Ct. 352 (2016).\n\n Bravo and Martínez faced their second trial in May 2017,\n\nand once again a jury found them guilty of federal program bribery\n\nunder § 666. Those proceedings devolved into the instant appeal,\n\nthe latest stage in this case's arduous journey.\n\n II.\n\n We are able to reduce the several questions that have\n\nbeen raised before us2 to the only one that merits our decisional\n\nattention and mandates the outcome of this appeal: Whether the\n\ngovernment introduced evidence at trial to satisfy the\n\njurisdictional element under 18 U.S.C. § 666(b) that the government\n\nentity involved received \"benefits in excess of $10,000 under a\n\nFederal program.\" (emphasis added). Where, as here, defendants\n\nhave preserved a sufficiency challenge, we review de novo a\n\n\n2 Defendants also challenge, among other things, the sufficiency\nof the evidence other than that presented to satisfy the\njurisdictional element, the propriety of the jury instructions,\nsome of the district court's evidentiary rulings, and their\nsentences. Our decision on the sufficiency issue makes it\nunnecessary to reach the merits of such challenges.\n\n\n -5-\n\fdistrict court's denial of their motion for judgment of acquittal.\n\nUnited States v. Acevedo-Hernández, 898 F.3d 150, 161 (1st Cir.\n\n2018).\n\n To maintain a conviction for federal program bribery,\n\nthe government must prove beyond a reasonable doubt that the party\n\nreceiving the bribe was an agent of an entity that \"receives, in\n\nany one year period, benefits in excess of $10,000 under a Federal\n\nprogram involving a grant, contract, subsidy, loan, guarantee,\n\ninsurance, or other form of Federal assistance.\" 18 U.S.C.\n\n§ 666(b). This requirement is often referred to as the\n\n\"jurisdictional element\" of § 666. See, e.g., United States v.\n\nMcLean, 802 F.3d 1228, 1240 (11th Cir. 2015). And not all federal\n\nfunds constitute \"benefits\" under the statute. See Fischer v.\n\nUnited States, 529 U.S. 667, 681 (2000) (\"Any receipt of federal\n\nfunds can, at some level of generality, be characterized as a\n\nbenefit. The statute does not employ this broad, almost limitless\n\nuse of the term.\"); see also United States v. Dubón-Otero, 292\n\nF.3d 1, 7 n.7 (1st Cir. 2002) (acknowledging that there exists\n\n\"compensation of the type excluded by § 666 (c)\" including\n\nsalaries, wages and expenses paid in the usual course of business).\n\nIn Fischer, the Supreme Court explained that only federal monies\n\nthat \"promote[] well-being,\" such as those which provide\n\nindividuals with \"financial help in time of sickness, old age, or\n\n\n -6-\n\funemployment,\" may qualify as \"benefits.\" Fischer, 529 U.S. at\n\n677 (citing Webster's Third New International Dictionary 204\n\n(1971)). Critically, \"[t]o determine whether an organization\n\nparticipating in a federal assistance program receives 'benefits,'\n\nan examination must be undertaken of the program's structure,\n\noperation, and purpose.\" Id. at 681. The government has the\n\nburden of producing adequate evidence for this examination to\n\noccur.\n\n In resolving if the § 666(b) jurisdictional element was\n\nsatisfied, we find it instructive to begin by comparing the\n\nevidence that the government offered on this key element during\n\nthe 2011 trial with that it presented in the 2017 proceedings\n\nleading to this appeal.\n\n At defendants' first trial, the government introduced\n\nevidence specifically tailored to establishing the § 666\n\njurisdictional requirement. An employee of the Puerto Rico\n\nTreasury Department testified for the government that \"the Senate\n\nof Puerto Rico childcare program (known as the Food Program for\n\nthe Care of Children and Adults) receive[d] funding from the\n\nGovernment of the United States.\" United States v. Bravo-\n\nFernández, 828 F. Supp. 2d 441, 455 (D.P.R. 2011), rev'd in part,\n\nvacated in part sub nom. United States v. Fernández, 722 F.3d 1\n\n(1st Cir. 2013). The witness further averred, with the support\n\n\n -7-\n\fof documentation also admitted into evidence, that the Puerto Rico\n\nSenate annually received around $20,000 in federal funds for the\n\nchildcare program during the relevant period. Id. at 456. This\n\nprovided the basis for the district court to conclude in its\n\nresolution of the Rule 29 motion for judgment of acquittal that\n\n\"[t]he federal assistance received by the Senate of Puerto Rico\n\nfor [its] childcare program clearly qualifies as a 'benefit'\n\nprovided under a federal program\" for purposes of § 666(b). Id.\n\n In contrast, the record of the second trial is barren of\n\nevidence showing disbursement of federal \"benefits\" to the Senate\n\nof Puerto Rico or even to the Commonwealth as a whole. All we\n\nhave is a stipulation the parties accorded prior to trial providing\n\nthat \"in fiscal year 2005[,] the Commonwealth of Puerto Rico\n\nreceived more than $10,000 in federal funding. Specifically, from\n\nOctober 1, 2004, to September 30, 2005, the Commonwealth of Puerto\n\nRico received over $4.7 billion in federal funds.\" (emphasis added)\n\nLater, on the first day of trial during a conference about\n\npreliminary jury instructions, the district judge asked counsel\n\nwhether this stipulation allowed him to inform jurors that the\n\n§ 666 jurisdictional element had been met. Counsel for defendant\n\nMartínez responded that the court should not instruct so because\n\n\"the . . . law . . . doesn't equate funds with benefits, and the\n\nstatute says benefits. . . . We have stipulated to the amount of\n\n\n -8-\n\fmoney, but not that [the jurisdictional] element has been\n\nsatisfied.\" Incredibly, this clear warning of things to come went\n\nunattended and the government proceeded to present its case in\n\nchief without introducing any evidence to cover this gaping hole\n\nin its case.\n\n Following the close of the government's case, defendants\n\nmade a Rule 29 motion for a verdict of acquittal in which they\n\nspecifically argued that the government failed to establish the\n\nexistence of $10,000 in benefits under a federal program. The\n\ndistrict court denied this motion without explanation. In\n\ncharging the jury, the district court stated that § 666 only\n\nrequired jurors to find that the Commonwealth received federal\n\n\"funds of more than $10,000.\" No instruction was given on what\n\nconstitutes a benefit, and the word \"benefits\" does not appear\n\neven once throughout the instructions. Counsel for defendant\n\nMartínez objected to the instruction's language, but that\n\nobjection was summarily overruled by the district court.\n\n Given the foregoing, and in keeping with our own\n\nprecedent and that of the Supreme Court, we can only conclude that\n\nthe government failed to meet its burden of establishing that the\n\nentity Martínez represented as an agent received the amount of\n\nbenefits required under § 666(b). The government's arguments to\n\nthe contrary are futile.\n\n\n -9-\n\f First, the government directs us to a paragraph in our\n\n2013 opinion in Fernández, which examined defendants' 2011 trial\n\nand noted that:\n\n [D]uring 2005 -- the year of the charged conduct -- the\n Commonwealth received over $4.7 billion in federal\n funds. Because Martínez . . . [is an] agent[] of the\n Commonwealth, the evidence was sufficient to show that\n [he is an] agent[] of a \"government . . . [that]\n receives, in any one year period, benefits in excess\n of $10,000 under a Federal program.\"\n\n722 F.3d at 9 (quoting 18 U.S.C. § 666(b)). This statement that\n\nthe jurisdictional element was satisfied in defendants' first\n\ntrial, the government purports, should also control here because\n\nof the law of the case doctrine, which \"bars a party from\n\nresurrecting issues that either were, or could have been, decided\n\non an earlier appeal.\" United States v. Matthews, 643 F.3d 9, 12-\n\n13 (1st Cir. 2011) (citation omitted). But our statement in\n\nFernández is not dispositive as it was neither essential to our\n\nholding there nor could the issue now before us have been decided\n\nin that initial appeal. Contrary to what the government contends,\n\ndefendants did not argue about the funds-benefits distinction in\n\ntheir first appeal. See Brief for Appellant Bravo at 25-27, United\n\nStates v. Fernández, 722 F.3d 1 (1st Cir. 2013)(No. 12-1289); Brief\n\nfor Appellant Martínez at 25-28, United States v. Fernández, 722\n\nF.3d 1 (1st Cir. 2013)(No. 12-1290). And they had no reason to\n\ndo so because, as explained above, the government introduced\n\n\n -10-\n\fspecific evidence at that first trial to establish the existence\n\nof the requisite amount of federal benefits. The issue before us\n\nin that case was whether Martínez was an \"agent\" of the\n\nCommonwealth, not whether \"benefits\" as used in the statute were\n\nreceived. Thus, the statement from Fernández the government\n\nrelies on is nothing but dicta that \"lack[s] any binding or\n\npreclusive effect.\" Sexual Minorities Uganda v. Lively, 899 F.3d\n\n24, 29 (1st Cir. 2018).\n\n Second, the government contends that both the Supreme\n\nCourt in Fischer and our decision in Dubón-Otero, 292 F.3d at 4,\n\ncommand an inquiry into the nature of federal funds to determine\n\nif they are benefits under § 666 only when the payments are\n\ndisbursed \"indirectly\" to the receiving entity. This argument is\n\nalso without merit. In fact, the one reference we made in Dubón-\n\nOtero to the distinction between entities that receive payments\n\ndirectly from the federal government and those that do not was\n\nthat \"[i]t makes no difference [whether an agency] received this\n\nmoney indirectly. It is now well established that benefits under\n\n§ 666 are not limited solely to primary target recipients or\n\nbeneficiaries.\" 292 F.3d at 9 (citing United States v. Fischer,\n\n168 F.3d 1273, 1278 (11th Cir. 1999) (\"[T]he plain language of\n\n§ 666(b) does not distinguish between an organization . . . that\n\nreceives 'benefits' directly under a federal program and an\n\n\n -11-\n\forganization . . . that receives 'benefits' as an assignee under\n\na federal program.\")). Indisputably, this language affords no\n\ncredit to the government's theory. Moreover, the reach of Fischer\n\nis not limited to only those cases involving indirect receipt of\n\nfederal monies. To the contrary, the Supreme Court's reasoning\n\nin Fischer, particularly its concern for the proper federal balance\n\nin this type of case, is by its very nature generally applicable.\n\nSee Fischer, 529 U.S. at 681.\n\n In a final attempt to save a sinking ship, the government\n\nasserts that the stipulation specifying the amount of federal funds\n\nreceived by the Commonwealth was sufficient to satisfy the § 666\n\njurisdictional element. The government takes the position that a\n\n\"jury, exercising common sense and relying on general knowledge,\n\ncan reasonably infer that the federal funds constituted\n\n'benefits.'\" It is tempting to agree with the government here.\n\nAs judges who hear cases arising out of federal benefit programs\n\nand who are familiar with how such programs are funded, we are\n\ncertain that there are federal benefit programs that provide far\n\nmore than $10,000 to the Commonwealth and its instrumentalities.\n\nThe question remains, however, whether those programs are funded\n\nby the $4.7 billion in federal funds that go directly to the\n\nCommonwealth. Perhaps the federal benefit programs enjoyed in\n\nPuerto Rico are financed through other federal monies, leaving the\n\n\n -12-\n\f$4.7 billion to be spent on infrastructure, salaries, and other\n\nexpenditures that may or may not constitute \"benefits\" under\n\nFischer? In any event, we see nothing in the record that tells\n\nus whether any juror would certainly know the answer to these\n\nquestions, nor did the government secure a stipulation supplying\n\nsuch answers.\n\n It is unclear, too, where we would stop if we accept the\n\ngovernment's invitation to rely on jurors' knowledge of federal\n\nfunding to fill gaps in the government's proof. Suppose the\n\ngovernment puts in no evidence about any federal funds at all.\n\nCould jurors simply fill-in the gap based on their \"common sense\"\n\nand \"general knowledge\" that large amounts of federal funds are\n\nsent to the Commonwealth government each year?\n\n Under the government's approach, the jurisdictional\n\nelement in many federal criminal cases could be satisfied by\n\nsimilar reliance on jurors' extra-record knowledge. For example,\n\none could claim that any juror would know that all banks are\n\nengaged in, or at least affect, interstate commerce, or that a\n\nbank is likely FDIC insured. Yet, the failure to offer any actual\n\nproof of these relatively obvious jurisdictional facts has\n\nrepeatedly proved fatal to criminal prosecutions. See United\n\nStates v. Leslie, 103 F.3d 1093, 1102-3 (2d Cir. 1997) (reversing\n\nconviction because government \"did not provide even the slenderest\n\n\n -13-\n\fof threads\" upon which to hang the interstate commerce\n\njurisdictional element); United States v. Sliker, 751 F.2d 477,\n\n484 (2d Cir. 1984) (affirming conviction based on oral testimony\n\nof FDIC-insured status, but warning the government of failure to\n\n\"ask the simple question that would avoid the need for judicial\n\nconsideration of what should be a non-problem\"); see also United\n\nStates v. Davis, 726 F.3d 357, 366-7 (2d Cir. 2013) (holding that\n\nthe government had failed to meet its burden by assuming that a\n\nfederal installation on federal land automatically came within\n\nfederal jurisdiction, but affirming after taking judicial notice\n\nof the fact at the government's behest).\n\n We have considered the Third Circuit's recent decision\n\nin United States v. Willis, 844 F.3d 155 (3d Cir. 2016), in which\n\nthe government relied on proof that the Government of the Virgin\n\nIslands received $150 million in federal funds. The Willis court\n\ntook a different route than that urged by the government in this\n\ncase. Rather than relying on juror common sense, the court in\n\nWillis held that federal funds paid to a territorial government\n\nwere a benefit to that government because they \"significantly\n\nsupported the government.\" Id. at 168. We do not see, though, how\n\nthat type of financial support to a local government equates to a\n\n\"benefit\" of the type required by Fischer. As in this case, it\n\ndoes not appear that any federal program was specifically\n\n\n -14-\n\fidentified in Willis, prohibiting the ability to determine, under\n\nFischer's \"benefits\" analysis, whether the funds received by the\n\nGovernment of the Virgin Islands were used for such promotion of\n\nwell-being.\n\n Despite its insistence that the Fischer analysis need\n\nonly be applied if it is \"difficult\" to determine whether the\n\nfederal payments were benefits, the government seems blind to the\n\nfact that without reference to a specific federal program it is\n\nnot only difficult but impossible to make such a determination.\n\nAgain, the stipulation entered between the parties made no\n\nreference to \"benefits\" or, for that matter, to any federal\n\nprogram. The stipulation also did not provide information\n\nregarding the intended or actual use of any portion of the $4.7\n\nbillion in federal funds. It only provided that the \"Commonwealth\n\nof Puerto Rico received over $4.7 billion in federal funds\" during\n\nthe relevant time period. Concluding that such a stipulation\n\nsufficed to satisfy the jurisdictional element would counter the\n\nplain language of § 666(b) requiring proof that the government\n\nentity involved received \"benefits in excess of $10,000 under a\n\nFederal program.\" It would also contravene the government's\n\nburden to put forth evidence about the federal program's\n\n\"structure, operation, and purpose\" in order to make ascertainable\n\nwhether an entity received \"benefits\" under § 666(b). Fischer,\n\n\n -15-\n\f529 U.S. at 681. Most of our sister circuits to have addressed\n\nthis issue agree.3 To hold otherwise and conclude that any receipt\n\nof federal funds is enough to satisfy the jurisdictional element\n\nwould transmute § 666 into the general bribery statute that the\n\nFischer court warned against and \"upset[] the proper federal\n\nbalance.\" Id.\n\n III.\n\n For the reasons explained above, we conclude that the\n\ngovernment failed to establish an essential element of the crime\n\nit charged defendants with. We need not go further and hereby\n\nreverse Bravo's and Martínez's § 666 convictions. We direct the\n\ndistrict court to enter a judgment of acquittal on both charges.\n\n\n\n3 See, e.g., United States v. Paixao, 885 F.3d 1203, 1206 (9th\nCir. 2018) (\"[N]ot all payments under federal programs qualify as\n'benefits' . . . . [T]he inquiry turns on the attributes of the\nfederal program[.]\") (citation omitted); United States v. Pinson,\n860 F.3d 152, 166 (4th Cir. 2017) (\"Because any receipt of federal\nfunds could 'at some level of generality' be characterized as a\nbenefit, . . . the Court provided guidelines to distinguish between\ncovered federal payments ('benefits') and non-covered payments.\");\nUnited States v. McLean, 802 F.3d 1228, 1237 (11th Cir. 2015)\n(\"[T]he government must prove beyond a reasonable doubt that the\nindividual worked for an entit[y] which receive[d] . . . funds\n. . . in connection with programs defined by a sufficiently\ncomprehensive structure, operation, and purpose to merit\ncharacterization of the funds as benefits under § 666(b).\"\n(citation and internal quotation marks omitted)); United States v.\nZyskind, 118 F.3d 113, 115 (2d. Cir. 1997) (\"[T]here must exist a\nspecific statutory scheme authorizing the Federal assistance in\norder to promote or achieve certain policy objectives.\") (quoting\nS. Rep. No. 98-225, at 370 (1983)).\n\n\n -16-\n[END_CASE]", "role": "user" } ]
4,582,652
UNITED STATES of America, Appellee, v. Angel Rafael CONTRERAS-DELGADO, Defendant, Appellant.
United States v. Contreras-Delgado
2019-01-17
17-1962P
U.S. Court of Appeals for the First Circuit
{"judges": "Barron, Selya, Katzmann", "parties": "", "opinions": [{"author": "KATZMANN, Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1962\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n ANGEL RAFAEL CONTRERAS-DELGADO,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Barron and Selya, Circuit Judges,\n and Katzmann,* Judge.\n\n\n Marie L. Cortés Cortés, was on brief for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Mainon A. Schwartz, Assistant United\nStates Attorney, on brief for appellee.\n\n\n January 17, 2019\n\n\n\n\n * Of the United States Court of International Trade, sitting\nby designation.\n\f KATZMANN, Judge. After pleading guilty to a charge of\n\npossessing a machine gun in violation of 18 U.S.C. § 922(o), the\n\nuncontested presentence report(“PSR”) placed defendant-appellant\n\nAngel Rafael Contreras-Delgado (“Contreras-Delgado”) in a federal\n\nguideline sentencing range (“GSR”) of 24 to 30 months’\n\nimprisonment. The district court judge sentenced him to 46 months.\n\nClaiming that this variant sentence is procedurally flawed and\n\nsubstantively unreasonable, Contreras-Delgado now appeals. We\n\naffirm.\n\n I. BACKGROUND.\n\n Because this appeal follows a guilty plea, we draw the\n\nfacts from the change-of-plea colloquy, the undisputed portions of\n\nthe PSR, and the transcript of the sentencing hearing. United\n\nStates v. Arias-Mercedes, 901 F.3d 1, 4 (1st Cir. 2018). In\n\nJanuary 2017, undercover police officers saw a man, later\n\nidentified as Contreras-Delgado, standing outside one of the\n\napartments in a public housing project in Bayamón, Puerto Rico.\n\nContreras-Delgado looked at the officers, asked “What’s going on\n\nMan” (translation from Spanish), and lifted his arms, which exposed\n\na black gun with an extended magazine in his waistband. The\n\nofficers identified themselves and asked if Contreras-Delgado had\n\na firearms license; he replied that he did not. The officers\n\narrested Contreras and seized the gun. The gun —- a Glock 9-\n\nmillimeter (“mm”) pistol -— had been modified to fire multiple\n\n\n - 2 -\n\frounds with a single pull of the trigger and was fully loaded with\n\na 31-round extended magazine. At the time of arrest, the officers\n\nfound two more 9-mm magazines next to Contreras-Delgado: another\n\nfully loaded 31-round magazine and a 17-round magazine with 15\n\nrounds of ammunition.\n\n Federal agents questioned Contreras-Delgado after\n\nreading him his rights. Contreras-Delgado admitted that he sold\n\ndrugs and had purchased the gun that was in his waistband “for\n\nprotection.” He told the agents he knew the pistol was modified\n\nto fire automatically “because he specifically asked for it to be\n\nfully auto when he purchased it.” The firearm also had an\n\naftermarket barrel installed, was equipped with a high-capacity\n\n31-round magazine, and incorporated a machine gun conversion\n\ndevice designed to make semiautomatic Glock pistols fire\n\nautomatically. No ownership records for the gun could be found.\n\n Contreras-Delgado was indicted for possessing a machine\n\ngun, in violation of 18 U.S.C. § 922(o). He knowingly and\n\nvoluntarily entered a straight plea of guilty to possessing a\n\nmachine gun as alleged in the indictment. At the change-of-plea\n\nhearing, Contreras-Delgado told the district court of his current\n\ntreatment for depression, though he remained competent to plead.\n\nHe also indicated that he understood that sentencing would be in\n\nthe discretion of the court and could differ from the guidelines\n\nand/or the parties’ sentencing recommendations. Upon Contreras-\n\n\n - 3 -\n\fDelgado’s motion, the judge issued an order permitting evaluation\n\nof him by a clinical psychologist, Dr. Alexandra Ramos (“Dr.\n\nRamos”), in support of mitigation of sentence.\n\n The U.S. Probation Office prepared a PSR1 that outlined\n\nthe offense conduct described above. Possession of a machine gun\n\ncarried a base offense level of 20; the PSR subtracted 3 levels\n\nfor acceptance of responsibility, yielding a total offense level\n\nof 17.\n\n Contreras-Delgado was twenty-two years old when he was\n\narrested for the instant offense. By that time, he had two\n\njuvenile adjudications: one for pointing a bladed weapon at four\n\nother children and threatening to stab them, and another for\n\nstealing from his mother and threatening to kill both her and his\n\ngrandmother. He had also been arrested as an adult for two counts\n\nof distributing a controlled substance, but those charges were\n\ndismissed pursuant to Puerto Rico’s Speedy Trial Act. None of\n\nthese events counted for criminal history points under the\n\nguidelines. Accordingly, the PSR used a Criminal History Category\n\nof I, and calculated Contreras-Delgado’s GSR as 24 to 30 months’\n\nimprisonment. Under the guidelines, Contreras-Delgado was\n\nineligible for probation. See U.S.S.G. § 5B1.1.\n\n\n\n\n1 All references herein are to the amended PSR, filed on June 23,\n2017, which contained some factual updates from the first PSR,\nfiled two weeks prior.\n\n\n - 4 -\n\f The PSR then set forth at length Contreras-Delgado’s\n\npersonal history and characteristics, including his family\n\nhistory, and his mother’s impression of his treatment needs: his\n\n“volatile nature” plus “hyperactivity disorder . . . when combined\n\nwith his drug use, results in violent behavior. If he is under\n\ntreatment, he can control his impulses.” The PSR also included a\n\ndetailed summary of Contreras-Delgado’s mental and emotional\n\nhealth, including a 2012 evaluation by a clinical psychologist and\n\n2017 findings by the Bureau of Prisons Psychology Services.\n\n In its concluding paragraph, the PSR noted that the\n\ndistrict court could “consider the following factors to impose a\n\nsentence outside the advisory [g]uideline[]s”: Contreras-Delgado’s\n\nhistory of substance abuse, his juvenile record, the fully loaded\n\nweapon and additional magazines he possessed during the instant\n\noffense, his admissions that he had sought out a fully automatic\n\nfirearm and that he sold drugs, and finally, that he was arrested\n\nas part of an operation targeting drug point activities in a public\n\nhousing project.\n\n Contreras-Delgado did not object to any portion of the\n\nPSR. He did, however, submit a sentencing memorandum urging the\n\ndistrict court to focus on Contreras-Delgado’s rehabilitative\n\npotential and recommending a non-GSR “alternative sentence,”\n\ncombining incarceration, probation, and supervised release.\n\n\n\n\n - 5 -\n\f At sentencing, Contreras-Delgado sought to present\n\nbriefly the testimony of Dr. Ramos, the clinical psychologist who\n\nevaluated him while he was in jail. The United States (“the\n\ngovernment”) offered instead to stipulate to the contents of the\n\nreport prepared by Dr. Ramos and its recommendation that Contreras-\n\nDelgado receive substance abuse treatment. The district court\n\napproved the stipulations and ruled that there was no need for Dr.\n\nRamos to testify. The district court summarized Dr. Ramos’s\n\nrecommendation –- that Contreras-Delgado “receive substance abuse\n\ntreatment to address his problems with addiction and to prevent\n\nrelapses” -- and directed that the whole report be added to the\n\nPSR. The district court also instructed that the PSR be modified\n\nto include mental health treatment as one of the conditions.\n\n Contreras-Delgado argued that a prolonged sentence of\n\nimprisonment would not facilitate his rehabilitation. He\n\nparticularly “highlight[ed] from the sentencing memo [] the idea\n\nthat because of [his] age, a prolonged sentence of imprisonment\n\nmay not actually contribute to his rehabilitation.” The district\n\ncourt pointed out that Dr. Ramos’s report contradicted that\n\nstatement: “[Dr.] Ramos says that he is in remission because of\n\nhis incarceration.” Contreras-Delgado disagreed and argued that\n\n“it’s about all the environmental factors that go into what would\n\nhelp someone rehabilitate.” The government agreed that Contreras-\n\nDelgado did “do well under a controlled environment,” but indicated\n\n\n - 6 -\n\fthat a “controlled environment” could be obtained in prison. The\n\ngovernment also explained that other sentencing factors strongly\n\nfavored a sentence of imprisonment, particularly the serious\n\nnature of Contreras-Delgado’s offense and his prior offenses\n\ninvolving threats of violence.\n\n The parties agreed that Contreras-Delgado’s total\n\noffense level was 17. The court then recounted the facts of\n\nContreras-Delgado’s juvenile offenses involving threats of\n\nviolence and noted Contreras-Delgado’s 2014 arrest for a\n\ncontrolled substance offense. As the PSR explained, this meant\n\nthat Contreras-Delgado had no criminal history points. His GSR was\n\nthus 24 to 30 months. Contreras-Delgado asked the court to depart\n\nor vary downward from imposing a sentence of incarceration and\n\ninstead impose a combination of incarceration and home\n\nconfinement. The government, noting that Contreras-Delgado had a\n\nmachine gun in his waist and had prior contacts with the law,\n\nrecommended that the court impose a sentence of incarceration\n\nwithin the GSR. The government indicated that the Bureau of\n\nPrisons could provide a controlled environment as well as mental\n\nhealth and substance abuse treatment.\n\n Stating that it had considered the facts of Contreras-\n\nDelgado’s offense as well as the other sentencing factors set forth\n\nin 18 U.S.C. § 3553(a), the district court determined that a\n\nsentence above the GSR was appropriate. Specifically, the district\n\n\n - 7 -\n\fcourt noted Contreras-Delgado’s age, employment, and substance\n\nabuse history, reiterated the parties’ sentencing recommendations,\n\nand explained that it had considered Contreras-Delgado’s “personal\n\ncharacteristics, as well as the nature of the offense.” Contreras-\n\nDelgado’s machine gun “was loaded with a 31-round high capacity\n\nmagazine,” he had additional high-capacity magazines, he admitted\n\nthat he requested a fully automatic gun when he purchased it, and\n\nhe confessed to selling drugs. Those facts, plus Contreras-\n\nDelgado’s prior violent threats and the fact that he had not\n\nreformed despite prior leniency, “move[d] the Court to impart a\n\nsentence above the guideline range” to “reflect[] the seriousness\n\nof the offense, promote[] respect for the law, protect[] the public\n\nfrom further crimes by Mr. Contreras[-Delgado], and address[] the\n\nissues of deterrence and punishment.” Accordingly, the court\n\nsentenced Contreras-Delgado to 46 months’ imprisonment and three\n\nyears’ supervised release.\n\n This appeal ensued.\n\n II. DISCUSSION\n\n A. Basic Principles.\n\n As we detail below, Contreras-Delgado contends that the\n\n46-month variant incarceration sentence was both procedurally and\n\nsubstantively unreasonable. “We review sentencing decisions\n\nimposed under the advisory Guidelines, whether outside or inside\n\nthe applicable GSR, for reasonableness.” United States v.\n\n\n - 8 -\n\fPantojas-Cruz, 800 F.3d 54, 58 (1st Cir. 2015) (citing United\n\nStates v. Turbides-Leonardo, 468 F.3d 34, 40 (1st Cir. 2006)).\n\nThis review incorporates two components directed at the appraisal\n\nof procedural soundness and then substantive reasonableness of the\n\nsentence. See Gall v. United States, 552 U.S. 38, 51 (2007);\n\nUnited States v. Cox, 851 F.3d 113, 119-20 (1st Cir. 2017); United\n\nStates v. Gallardo-Ortiz, 666 F.3d 808, 811 (1st Cir. 2012). Thus,\n\nfirst, we examine whether in arriving at the sentence, the district\n\ncourt committed any procedural errors. United States v. Rossignol,\n\n780 F.3d 475, 477 (1st Cir. 2015); Gallardo-Ortiz, 66 F.3d at 811.\n\nSuch missteps include “failing to calculate (or improperly\n\ncalculating) the Guidelines range, treating the Guidelines as\n\nmandatory, failing to consider the § 3553(a) factors, selecting a\n\nsentence based on clearly erroneous facts, or failing to adequately\n\nexplain the chosen sentence — including an explanation for any\n\ndeviation from the Guidelines range.” Gall, 552 U.S. at 51. “We\n\nhave described our abuse of discretion standard in this context as\n\n‘multifaceted,’ as we apply clear error review to factual findings,\n\nde novo review to interpretations and applications of the\n\nguidelines, and abuse of discretion review to judgment calls.”\n\nUnited States v. Nieves-Mercado, 847 F.3d 37, 42 (1st Cir. 2017).\n\nWhile this court generally applies “the deferential abuse of\n\ndiscretion standard to preserved challenges to the procedural\n\nreasonableness of a sentence, . . . when a defendant fails to\n\n\n - 9 -\n\fpreserve an objection to the procedural reasonableness below [of\n\nthe sentence but asserts it on appeal], the plain error standard\n\nsupplants that customary standard of review.” United States v.\n\nGierbolini-Rivera, 900 F.3d 7, 12 (1st Cir. 2018); see United\n\nStates v. Ruiz-Huertas, 792 F.3d 223, 226 (1st Cir. 2015). The\n\nplain error standard “is not easy to meet, because it requires\n\nerror, plainness, prejudice to the defendant and the threat of a\n\nmiscarriage of justice.” United States v. Torres-Rosario, 658\n\nF.3d 110, 116 (1st Cir. 2011) (citing United States v. Olano, 507\n\nU.S. 725, 732-36 (1993)).\n\n If procedural soundness is established, we then proceed\n\nto the second phase of our review, assessing the substantive\n\nreasonableness of the sentence, “tak[ing] into account the\n\ntotality of the circumstances, including the extent of any variance\n\nfrom the Guidelines range.” United States v. Bermúdez-Meléndez,\n\n827 F.3d 160, 163 (1st Cir. 2016) (alteration in original) (quoting\n\nGall, 552 U.S. at 51). “In determining substantive reasonableness,\n\nsubstantial respect is due to the sentencing court’s discretion.”\n\nId. This deferential approach recognizes that although “[a]\n\nsentencing court is under a mandate to consider a myriad of\n\nrelevant factors, . . . the weighting of those factors is largely\n\nwithin the court’s informed discretion.” United States v.\n\nClogston, 662 F.3d 588, 593 (1st Cir. 2011). For substantive\n\nreasonableness, the linchpin is “a plausible sentencing rationale\n\n\n - 10 -\n\fand a defensible result.” United States v. Pol-Flores, 644 F.3d\n\n1, 4-5 (1st Cir. 2011) (quoting United States v. Martin, 520 F.3d\n\n87, 96 (1st Cir. 2008)). Hence, “we limit our review to the\n\nquestion of whether the sentence, in light of the totality of the\n\ncircumstances, resides within the expansive universe of reasonable\n\nsentences.” United States v. King, 741 F.3d 305, 308 (1st Cir.\n\n2014). While some circuits have found substantive reasonableness\n\nclaims preserved despite a lack of objection in the lower court,\n\nand thus not reviewed for plain error, see United States v.\n\nHernández-Maldonado, 793 F.3d 223, 227 (1st Cir. 2015), in our\n\ncircuit the question remains open. See United States v. Rondón-\n\nGarcía, 886 F.3d 14, 26 (1st Cir. 2018); United States v.\n\nArsenault, 833 F.3d 24, 29 (1st Cir. 2016).\n\n Even if plain error is not applied, considerable\n\ndeference must still be given to the district court’s judgment.\n\nClogston, 662 F.3d at 593. This “highly deferential . . . standard\n\nremains in full force” even if the sentence is outside the\n\napplicable GSR. United States v. Vázquez-Martínez, 812 F.3d 18,\n\n26 (1st Cir. 2016) (quoting United States v. Santiago-Rivera, 744\n\nF.3d 229, 234 (1st Cir. 2014)); see also Gallardo-Ortiz, 666 F.3d\n\nat 811 (“A dramatic variance . . . cannot unduly influence our\n\nreview of substantive reasonableness.”). Accordingly, even when\n\nthe district court imposes a variant sentence, this court affords\n\n“due deference to the district court’s decision that the § 3553(a)\n\n\n - 11 -\n\ffactors, on a whole, justify the extent of the variance.” Gall,\n\n552 U.S. at 51.\n\n B. Procedural Reasonableness.\n\n Contreras-Delgado argues on appeal that the district court\n\nabused its discretion in denying his request to present the live\n\ntestimony of Dr. Ramos, the clinical psychologist who had evaluated\n\nhim while he was in jail, and that this denial constitutes\n\nprocedural error because he was precluded from presenting\n\n“information relevant to recidivism and rehabilitation . . . as\n\npart of § 3553(a)’s sentencing factors.” He also asserts that\n\nthe court “overstated” the evidence of his prior violent threats.\n\nContreras-Delgado argues generally that the court did not\n\nappropriately balance the § 3553(a) factors, thereby violating the\n\nparsimony principle – the statutory directive that sentences\n\nshould be no higher than necessary to achieve the statutory goals\n\nof sentencing. Specifically, Contreras-Delgado complains that the\n\ncourt did not mention Contreras-Delgado’s mental characteristics,\n\nsuch as depression and attention deficit hyperactivity disorder.\n\n 1.\n\n Contreras-Delgado contends that the district court\n\nabused its discretion when it did not allow the testimony of Dr.\n\nRamos at the sentencing hearing and further failed to consider\n\n§ 3353(a) sentencing factors. The government counters that\n\nContreras-Delgado did not object to this denial and, thus, the\n\n\n - 12 -\n\fappropriate standard of review is for plain error. It is well\n\nestablished that articulating an objection is required in order to\n\npreserve the most generous standard for a defendant. This not\n\nonly protects the interests of the defendant but also provides the\n\ngovernment with an opportunity to respond. Proper objection also\n\nfurthers the interests of judicial economy in that it assists\n\njudicial decision-making. To be sure, the record would have been\n\ncleaner if the talismanic “I object” formulation had been uttered.\n\nAt the same time, a review of the record leaves little doubt that\n\ncounsel sought to present the live testimony of the witness and\n\npersisted in explaining why it was necessary even after it had\n\nbeen denied. In any event, whether the standard of review be abuse\n\nof discretion or plain error, we conclude that Contreras-Delgado’s\n\nclaim of procedural error cannot succeed.\n\n First, we note that while a defendant enjoys a right to\n\ndue process at sentencing, United States v. Stile, 845 F.3d 425,\n\n430 (1st Cir. 2017), and the right “to speak or present any\n\ninformation to mitigate the sentence,” Fed. R. Crim. P.\n\n32(i)(4)(A)(ii); see also Irizarry v. United States, 553 U.S. 708,\n\n715 (2008), “a defendant has no right to insist on calling other\n\nwitnesses on his behalf.” Stile, 845 F.3d at 430. See United\n\nStates v. Cruzado-Laureano, 527 F.3d 231, 238 (1st Cir. 2008);\n\nUnited States v. Heller, 797 F.2d 41, 43 (1st Cir. 1986). “The\n\nrule only requires the court to allow the defendant and his\n\n\n - 13 -\n\fattorney to speak.” Cruzado-Laureano, 527 F.3d at 238 (citing\n\nFed. R. Crim. P. 32(i)(4)(A)(i), (ii); United States v. Rodriguez,\n\n336 F.3d 67, 70 (1st Cir. 2003)).\n\n Here, the district court not only reviewed Dr. Ramos’s\n\nreport from the bench, but it summarized her recommendations and,\n\nas reflected in the district court’s correction of counsel’s\n\ninterpretation, demonstrated command of its contents. Moreover,\n\nDr. Ramos’s entire report was included in the PSR, where, as the\n\ndistrict court noted, it could guide the Bureau of Prisons and\n\nProbation as they determined appropriate treatment. Further,\n\nContreras-Delgado’s counsel fully explained to the court his view\n\nthat Dr. Ramos’s report supported a mitigation of the sentence\n\nbelow the GSR. In sum, under any standard of review, Contreras-\n\nDelgado’s claim that substitution of Dr. Ramos’s report in lieu of\n\ntestimony constituted procedural error is not meritorious.2\n\n 2.\n\n Contrary to Contreras-Delgado’s assertion, the district\n\ncourt properly considered the § 3553(a) sentencing factors,\n\n\n\n\n2 We note that the government also argues that Contreras-Delgado\nconsented to the substitution of Dr. Ramos’s report in lieu of her\nlive testimony, and that this consent constituted waiver, instead\nof forfeiture, such that he may not revive his waived argument on\nappeal. See generally United States v. Delgado-Sánchez, 849 F.3d\n1, 6-7 (1st Cir. 2017) (reviewing waiver and forfeiture standards).\nThe record is open to a different interpretation. In any event,\nwe need not resolve the issue because, as we have indicated,\nContreras-Delgado’s claim fails. Id. at 7.\n\n\n - 14 -\n\fincluding relevant mitigating and aggravating factors; its\n\nweighing of those factors was well within its discretion. While\n\na sentencing court must consider all the incorporated § 3553(a)\n\nfactors, it “need not verbalize its evaluation of each and every\n\n[§] 3553(a) factor.” United States v. Reyes-Rivera, 812 F.3d 79,\n\n89 (1st Cir. 2016). Moreover, it “is not required to address the\n\n§ 3553(a) factors one by one, in some sort of rote incantation\n\nwhen explicating its sentencing decision, nor must the court afford\n\neach of the § 3553(a) factors equal prominence.” United States v.\n\nSosa-González, 900 F.3d 1, 5 (1st Cir. 2018) (quoting United States\n\nv. Vázquez-Vázquez, 852 F.3d 62, 66 (1st Cir. 2017)). Here, the\n\ncourt expressly stated that it had considered the § 3553(a)\n\nsentencing factors. That statement is “entitled to significant\n\nweight.” United States v. Caballero-Vázquez, 896 F.3d 115, 120\n\n(1st Cir. 2018) (quoting Santiago-Rivera, 744 F.3d at 233). It\n\nalso implicitly acknowledges awareness of and accordance with the\n\nparsimony principle. Turbides-Leonardo, 468 F.3d at 41 (“[T]he\n\nsentencing court in this case acknowledged its awareness of the\n\nparsimony principle during the disposition hearing, stating that\n\nit had taken [§] 3553(a) into account in arriving at the 48-month\n\nsentence. On these facts, no more is exigible.”).\n\n Moreover, the district court discussed the relevant\n\nsentencing factors on the record. First, the district court\n\nexpressly considered Contreras-Delgado’s history and\n\n\n - 15 -\n\fcharacteristics, including his age, employment, and substance\n\nabuse history. Then, the court specified the facts it found\n\nwarranted a sentence above the applicable GSR: Contreras-Delgado’s\n\nautomatic weapon was loaded with a 31-round high-capacity magazine\n\nand 31 rounds of ammunition; Contreras-Delgado had a second 31-\n\nround high-capacity magazine, also fully loaded with 9-mm\n\nammunition for the automatic weapon; Contreras-Delgado had a third\n\nhigh-capacity magazine, this one with 15 rounds of 9-mm ammunition;\n\nContreras-Delgado not only knew the weapon was fully automatic,\n\nbut specifically requested that modification when he purchased it;\n\nContreras-Delgado had previously benefited from leniency and the\n\n“probation and programs offered by the Commonwealth of Puerto Rico\n\nand the Court of Juvenile Affairs”; Contreras-Delgado admitted\n\nselling drugs and had in fact been arrested -- though not convicted\n\n-- for possession with intent to distribute marijuana and cocaine;\n\nand Contreras-Delgado’s criminal history included “threatening to\n\nkill children with a knife and threatening to kill his mother.”\n\nContreras-Delgado’s suggestion that the district court somehow\n\nerred by characterizing these violent threats as violent behavior\n\nis unavailing. See, e.g., United States v. Harden, 866 F.3d 768,\n\n774 (7th Cir. 2017) (noting that a statutory “definition of violent\n\noffense comports with a common-sense understanding of violent\n\nconduct as the use or threat of physical force against another and\n\n\n\n\n - 16 -\n\fis relevant as a guidepost as to a common definition of\n\n‘violence.’” (emphasis added)).\n\n These are all statutorily authorized sentencing\n\nconsiderations; each of these facts relates to the nature and\n\ncircumstances of the offense (especially those not already\n\naccounted for by the guidelines) or to Contreras-Delgado’s history\n\nand characteristics. See 18 U.S.C. § 3553(a)(1). Basing\n\nContreras-Delgado’s sentences on these factors cannot constitute\n\nprocedural error, nor will this court “disturb a well-reasoned\n\ndecision” -- including the one here -- “to give greater weight to\n\nparticular sentencing factors over others.” United States v.\n\nSantini-Santiago, 846 F.3d 487, 492 (1st Cir. 2017) (quoting United\n\nStates v. Gibbons, 553 F.3d 40, 47 (1st Cir. 2009)).\n\n The district court expressly found that a sentence above\n\nthe GSR was further supported by the statutory sentencing\n\nconsiderations of: “reflect[ing] the seriousness of the offense,\n\npromot[ing] respect for the law, protect[ing] the public from\n\nfurther crimes by Mr. Contreras[-Delgado], and address[ing] the\n\nissues of deterrence and punishment.” That finding must be\n\nafforded a high level of deference on appeal, regardless of the\n\nstandard of review applied. See Vázquez-Martínez, 812 F.3d at 26.\n\n Contreras-Delgado’s claim “that the court erred by\n\nrelying on [negative factors] excessively” thus simply “amounts to\n\na disagreement with the district court’s weighing of the different\n\n\n - 17 -\n\fsentencing factors.” United States v. Cruz-Vázquez, 841 F.3d 546,\n\n550 (1st Cir. 2016). That the district court -- after careful\n\nconsideration of the statutory factors and explanation of its\n\nreasoning -- weighed the factors differently than Contreras-\n\nDelgado is not error. United States v. Carrasco-de-Jesus, 589\n\nF.3d 22, 29 (1st Cir. 2009).\n\n All the potentially mitigating factors Contreras-Delgado\n\nidentifies on appeal were discussed in the PSR, in Contreras-\n\nDelgado’s sentencing memorandum, and/or at sentencing. “The\n\npotentially mitigating factors [the defendant] identifies on\n\nappeal were thoroughly discussed in the presentence report; that\n\nthe district court did not explicitly mention them during the\n\nsentencing hearing suggests they were unconvincing, not ignored.”\n\nUnited States v. Lozada-Aponte, 689 F.3d 791, 793 (1st Cir. 2012).\n\n Moreover, although the district court did not recite\n\nContreras-Delgado’s mental health history, it did review Dr.\n\nRamos’s report and direct that it be added to the PSR, which\n\nsignals consideration of its contents. “The record . . . supports\n\nthe conclusion that the District Court simply focused on other\n\nconsiderations that it implicitly deemed more important, including\n\nthe defendant’s history of violent behavior.” United States v.\n\nOcchiuto, 784 F.3d 862, 869 (1st Cir. 2015). The fact that\n\nContreras-Delgado would have preferred that greater weight be\n\ngiven to his psychological issues rather than to the seriousness\n\n\n - 18 -\n\fof his criminal behavior is not a reason to vacate his sentence.\n\nSee, e.g., United States v. Arroyo-Maldonado, 791 F.3d 193, 201\n\n(1st Cir. 2015) (finding no error where the defendant sought to\n\nsubstitute his judgment for that of the sentencing court).\n\n Regarding Contreras-Delgado’s prior behavior, the\n\ndistrict court did include a factually accurate comment that\n\nContreras-Delgado had been arrested, but not convicted, of\n\npossessing drugs with intent to distribute them at the state level.\n\nContreras-Delgado separately admitted that he “sells drugs . . .\n\nto make a living,” so it is undisputed that he committed drug\n\ntrafficking offenses not reflected in his criminal history score.\n\nThus, the district court did not run afoul of this court’s\n\nadmonition not to use mere arrests to “infer unlawful behavior\n\nunless there is proof by a preponderance of the evidence of the\n\nconduct” those charges allege. Rondón-García, 886 F.3d at 25)\n\n(citing United States v. Cortés-Medina, 819 F.3d 566, 570 (1st\n\nCir. 2016)). The district court’s use of the phrase “[a]s usual”\n\nto describe the dismissal of those drug-distribution charges did\n\nnot render Contreras-Delgado’s underrepresented criminal history\n\nan impermissible consideration. See 18 U.S.C. § 3553.\n\n Accordingly, Contreras-Delgado’s claim fails under any\n\nstandard of review. Even under the more defendant-friendly abuse\n\nof discretion standard, Contreras-Delgado’s arguments fail because\n\nhis sentence was properly based on permissible § 3553(a) sentencing\n\n\n - 19 -\n\ffactors, and the allegedly mitigating factors were considered by\n\nthe district court. See Arroyo-Maldonado, 791 F.3d at 201.3\n\n C. Substantive Reasonableness.\n\n An inquiry into the substantive reasonableness of a\n\nsentence must “take into account the totality of the circumstances,\n\nincluding the extent of any variance from the Guidelines range.”\n\nGall, 552 U.S. at 51. “The hallmarks of a substantively reasonable\n\nsentence are ‘a plausible sentencing rationale and a defensible\n\nresult.’” United States v. Zapata-Vázquez, 778 F.3d 21, 24 (1st\n\nCir. 2015) (quoting Martin, 520 F.3d at 96). Under the totality\n\nof the circumstances here, Contreras-Delgado’s 46-month sentence\n\nwas substantively reasonable.\n\n As has been noted, it is clear from the record that the\n\ndistrict court sufficiently considered the relevant § 3553\n\nsentencing factors. See supra pp. 15-20. The court assessed the\n\ndangerous nature and circumstances of the offense of conviction,\n\nincluding the fact that the machine gun possession offense also\n\ninvolved a substantial amount of ammunition and multiple high-\n\ncapacity magazines, heightening the risk posed to the public.\n\n\n\n\n3 Because Contreras-Delgado’s improper-weight arguments fail\nregardless of the standard of review, it is immaterial whether\nthey are characterized as procedural or substantive arguments.\nCf. Caballero-Vázquez, 896 F.3d at 120 n.1 (noting that First\nCircuit “precedent is less-than-clear as to whether a sentencing\ncourt’s weighing of mitigating factors implicates procedural or\nsubstantive reasonableness”).\n\n\n - 20 -\n\fMoreover, Contreras-Delgado admitted committing other crimes\n\n(specifically, selling drugs) for which he had never been punished,\n\ndespite having been previously arrested. That, as well as the\n\nfact that Contreras-Delgado’s prior juvenile convictions for\n\nthreats of violence resulted in no criminal history points, support\n\nthe conclusion that the district court was well within its\n\ndiscretion to believe that the GSR underrepresented Contreras-\n\nDelgado’s criminal history. “[A] district court may vary a\n\nsentence upward in an effort to reflect past leniency.” United\n\nStates v. Santiago-González, 825 F.3d 41, 49 (1st Cir. 2016)\n\n(citing United States v. Flores-Machicote, 706 F.3d 16, 21 (1st\n\nCir. 2013)). Indeed, the district court noted that despite his\n\nprior brushes with the law, Contreras-Delgado had “benefited from\n\nprobation and programs” instead of imprisonment. The court thus\n\nacted within the bounds of its discretion when it determined that\n\nContreras-Delgado’s offense —- when viewed in light of his history\n\n—- warranted a variant sentence. See United States v. Romero-\n\nGalindez, 782 F.3d 63, 71-72 (1st Cir. 2015). “[D]eviation[s]\n\nfrom the Guidelines ‘should typically be rooted either in the\n\nnature and circumstances of the offense or the characteristics of\n\nthe offender.’” Id. (quoting Martin, 520 F.3d at 91)). Here,\n\nthe district court rooted its variant sentence in both.\n\n We further note that the length of the sentence does not\n\nmake it per se unreasonable. “The district court evaluated the\n\n\n - 21 -\n\ffactors provided under 18 U.S.C. § 3553(a) and determined that an\n\nabove-guidelines sentence was appropriate.” Santini-Santiago, 846\n\nF.3d at 492 (upholding a district court’s 18-month variance above\n\nan applicable GSR of 12 to 18 months, partly due to the weight the\n\ndistrict court placed on the seriousness of the offense).\n\nContreras-Delgado’s sentence falls well within the “expansive\n\nuniverse of substantively reasonable sentences.” United States v.\n\nMatos-de-Jesús, 856 F.3d 174, 180 (1st Cir. 2017) (upholding a\n\nsentence 15 months longer than the top end of the GSR). “Decisions\n\nlike these are within the sound discretion of sentencing courts,\n\nand [this court] ‘will not disturb a well-reasoned decision to\n\ngive greater weight to particular sentencing factors over\n\nothers.’” Santini-Santiago, 846 F.3d at 492 (quoting Gibbons, 553\n\nF.3d at 47).\n\n In this case, Contreras-Delgado faced a statutory\n\nmaximum sentence of up to ten years of imprisonment. See 18 U.S.C.\n\n§ 922(o). His actual sentence of less than four years is not only\n\ndefensibly within “the expansive boundaries of [the] universe” of\n\nreasonable sentences, but also well within the statutory bounds of\n\nthe district court’s discretion, and represents a fraction of\n\nContreras-Delgado’s exposure. Martin, 520 F.3d at 92; see also\n\nUnited States v. Díaz-Bermúdez, 778 F.3d 309, 313-14 (1st Cir.\n\n2015) (comparing sentence to statutory maximum, and collecting\n\ncases upholding variances several years above the guidelines).\n\n\n - 22 -\n\f“[A]n increased sentence is necessarily a judgment call and, within\n\nwide limits, deference is due to the trier’s on-the-spot\n\nperceptions.” Arroyo-Maldonado, 791 F.3d at 198 (quoting United\n\nStates v. Vargas-Dávila, 649 F.3d 129, 131 (1st Cir. 2011)). We\n\nthus defer to the district court’s reasoned decision that, under\n\nthe circumstances, Contreras-Delgado’s behavior warranted a 46-\n\nmonth sentence.\n\n III. CONCLUSION\n\n In sum, a sentence should be left intact so long as it\n\nis procedurally sound and there is “a plausible sentencing\n\nrationale and a defensible result.” Martin, 520 F.3d at 96; Gall,\n\n552 U.S. at 49-50 (requiring individualized consideration and\n\nadequate explanation for variances). The district court provided\n\nindividualized assessments of Contreras-Delgado’s conduct as well\n\nas the other § 3553 factors, and reasonably explained the basis\n\nfor the sentence imposed.\n\n We conclude that Contreras-Delgado’s sentence was\n\nprocedurally and substantively reasonable.\n\n The sentence is affirmed.\n\n\n\n\n - 23 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359905/", "author_raw": "KATZMANN, Judge"}]}
BARRON
SELYA
KATZMANN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582652/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Angel Rafael CONTRERAS-DELGADO, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-17\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1962\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n ANGEL RAFAEL CONTRERAS-DELGADO,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Barron and Selya, Circuit Judges,\n and Katzmann,* Judge.\n\n\n Marie L. Cortés Cortés, was on brief for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Mainon A. Schwartz, Assistant United\nStates Attorney, on brief for appellee.\n\n\n January 17, 2019\n\n\n\n\n * Of the United States Court of International Trade, sitting\nby designation.\n\f KATZMANN, Judge. After pleading guilty to a charge of\n\npossessing a machine gun in violation of 18 U.S.C. § 922(o), the\n\nuncontested presentence report(“PSR”) placed defendant-appellant\n\nAngel Rafael Contreras-Delgado (“Contreras-Delgado”) in a federal\n\nguideline sentencing range (“GSR”) of 24 to 30 months’\n\nimprisonment. The district court judge sentenced him to 46 months.\n\nClaiming that this variant sentence is procedurally flawed and\n\nsubstantively unreasonable, Contreras-Delgado now appeals. We\n\naffirm.\n\n I. BACKGROUND.\n\n Because this appeal follows a guilty plea, we draw the\n\nfacts from the change-of-plea colloquy, the undisputed portions of\n\nthe PSR, and the transcript of the sentencing hearing. United\n\nStates v. Arias-Mercedes, 901 F.3d 1, 4 (1st Cir. 2018). In\n\nJanuary 2017, undercover police officers saw a man, later\n\nidentified as Contreras-Delgado, standing outside one of the\n\napartments in a public housing project in Bayamón, Puerto Rico.\n\nContreras-Delgado looked at the officers, asked “What’s going on\n\nMan” (translation from Spanish), and lifted his arms, which exposed\n\na black gun with an extended magazine in his waistband. The\n\nofficers identified themselves and asked if Contreras-Delgado had\n\na firearms license; he replied that he did not. The officers\n\narrested Contreras and seized the gun. The gun —- a Glock 9-\n\nmillimeter (“mm”) pistol -— had been modified to fire multiple\n\n\n - 2 -\n\frounds with a single pull of the trigger and was fully loaded with\n\na 31-round extended magazine. At the time of arrest, the officers\n\nfound two more 9-mm magazines next to Contreras-Delgado: another\n\nfully loaded 31-round magazine and a 17-round magazine with 15\n\nrounds of ammunition.\n\n Federal agents questioned Contreras-Delgado after\n\nreading him his rights. Contreras-Delgado admitted that he sold\n\ndrugs and had purchased the gun that was in his waistband “for\n\nprotection.” He told the agents he knew the pistol was modified\n\nto fire automatically “because he specifically asked for it to be\n\nfully auto when he purchased it.” The firearm also had an\n\naftermarket barrel installed, was equipped with a high-capacity\n\n31-round magazine, and incorporated a machine gun conversion\n\ndevice designed to make semiautomatic Glock pistols fire\n\nautomatically. No ownership records for the gun could be found.\n\n Contreras-Delgado was indicted for possessing a machine\n\ngun, in violation of 18 U.S.C. § 922(o). He knowingly and\n\nvoluntarily entered a straight plea of guilty to possessing a\n\nmachine gun as alleged in the indictment. At the change-of-plea\n\nhearing, Contreras-Delgado told the district court of his current\n\ntreatment for depression, though he remained competent to plead.\n\nHe also indicated that he understood that sentencing would be in\n\nthe discretion of the court and could differ from the guidelines\n\nand/or the parties’ sentencing recommendations. Upon Contreras-\n\n\n - 3 -\n\fDelgado’s motion, the judge issued an order permitting evaluation\n\nof him by a clinical psychologist, Dr. Alexandra Ramos (“Dr.\n\nRamos”), in support of mitigation of sentence.\n\n The U.S. Probation Office prepared a PSR1 that outlined\n\nthe offense conduct described above. Possession of a machine gun\n\ncarried a base offense level of 20; the PSR subtracted 3 levels\n\nfor acceptance of responsibility, yielding a total offense level\n\nof 17.\n\n Contreras-Delgado was twenty-two years old when he was\n\narrested for the instant offense. By that time, he had two\n\njuvenile adjudications: one for pointing a bladed weapon at four\n\nother children and threatening to stab them, and another for\n\nstealing from his mother and threatening to kill both her and his\n\ngrandmother. He had also been arrested as an adult for two counts\n\nof distributing a controlled substance, but those charges were\n\ndismissed pursuant to Puerto Rico’s Speedy Trial Act. None of\n\nthese events counted for criminal history points under the\n\nguidelines. Accordingly, the PSR used a Criminal History Category\n\nof I, and calculated Contreras-Delgado’s GSR as 24 to 30 months’\n\nimprisonment. Under the guidelines, Contreras-Delgado was\n\nineligible for probation. See U.S.S.G. § 5B1.1.\n\n\n\n\n1 All references herein are to the amended PSR, filed on June 23,\n2017, which contained some factual updates from the first PSR,\nfiled two weeks prior.\n\n\n - 4 -\n\f The PSR then set forth at length Contreras-Delgado’s\n\npersonal history and characteristics, including his family\n\nhistory, and his mother’s impression of his treatment needs: his\n\n“volatile nature” plus “hyperactivity disorder . . . when combined\n\nwith his drug use, results in violent behavior. If he is under\n\ntreatment, he can control his impulses.” The PSR also included a\n\ndetailed summary of Contreras-Delgado’s mental and emotional\n\nhealth, including a 2012 evaluation by a clinical psychologist and\n\n2017 findings by the Bureau of Prisons Psychology Services.\n\n In its concluding paragraph, the PSR noted that the\n\ndistrict court could “consider the following factors to impose a\n\nsentence outside the advisory [g]uideline[]s”: Contreras-Delgado’s\n\nhistory of substance abuse, his juvenile record, the fully loaded\n\nweapon and additional magazines he possessed during the instant\n\noffense, his admissions that he had sought out a fully automatic\n\nfirearm and that he sold drugs, and finally, that he was arrested\n\nas part of an operation targeting drug point activities in a public\n\nhousing project.\n\n Contreras-Delgado did not object to any portion of the\n\nPSR. He did, however, submit a sentencing memorandum urging the\n\ndistrict court to focus on Contreras-Delgado’s rehabilitative\n\npotential and recommending a non-GSR “alternative sentence,”\n\ncombining incarceration, probation, and supervised release.\n\n\n\n\n - 5 -\n\f At sentencing, Contreras-Delgado sought to present\n\nbriefly the testimony of Dr. Ramos, the clinical psychologist who\n\nevaluated him while he was in jail. The United States (“the\n\ngovernment”) offered instead to stipulate to the contents of the\n\nreport prepared by Dr. Ramos and its recommendation that Contreras-\n\nDelgado receive substance abuse treatment. The district court\n\napproved the stipulations and ruled that there was no need for Dr.\n\nRamos to testify. The district court summarized Dr. Ramos’s\n\nrecommendation –- that Contreras-Delgado “receive substance abuse\n\ntreatment to address his problems with addiction and to prevent\n\nrelapses” -- and directed that the whole report be added to the\n\nPSR. The district court also instructed that the PSR be modified\n\nto include mental health treatment as one of the conditions.\n\n Contreras-Delgado argued that a prolonged sentence of\n\nimprisonment would not facilitate his rehabilitation. He\n\nparticularly “highlight[ed] from the sentencing memo [] the idea\n\nthat because of [his] age, a prolonged sentence of imprisonment\n\nmay not actually contribute to his rehabilitation.” The district\n\ncourt pointed out that Dr. Ramos’s report contradicted that\n\nstatement: “[Dr.] Ramos says that he is in remission because of\n\nhis incarceration.” Contreras-Delgado disagreed and argued that\n\n“it’s about all the environmental factors that go into what would\n\nhelp someone rehabilitate.” The government agreed that Contreras-\n\nDelgado did “do well under a controlled environment,” but indicated\n\n\n - 6 -\n\fthat a “controlled environment” could be obtained in prison. The\n\ngovernment also explained that other sentencing factors strongly\n\nfavored a sentence of imprisonment, particularly the serious\n\nnature of Contreras-Delgado’s offense and his prior offenses\n\ninvolving threats of violence.\n\n The parties agreed that Contreras-Delgado’s total\n\noffense level was 17. The court then recounted the facts of\n\nContreras-Delgado’s juvenile offenses involving threats of\n\nviolence and noted Contreras-Delgado’s 2014 arrest for a\n\ncontrolled substance offense. As the PSR explained, this meant\n\nthat Contreras-Delgado had no criminal history points. His GSR was\n\nthus 24 to 30 months. Contreras-Delgado asked the court to depart\n\nor vary downward from imposing a sentence of incarceration and\n\ninstead impose a combination of incarceration and home\n\nconfinement. The government, noting that Contreras-Delgado had a\n\nmachine gun in his waist and had prior contacts with the law,\n\nrecommended that the court impose a sentence of incarceration\n\nwithin the GSR. The government indicated that the Bureau of\n\nPrisons could provide a controlled environment as well as mental\n\nhealth and substance abuse treatment.\n\n Stating that it had considered the facts of Contreras-\n\nDelgado’s offense as well as the other sentencing factors set forth\n\nin 18 U.S.C. § 3553(a), the district court determined that a\n\nsentence above the GSR was appropriate. Specifically, the district\n\n\n - 7 -\n\fcourt noted Contreras-Delgado’s age, employment, and substance\n\nabuse history, reiterated the parties’ sentencing recommendations,\n\nand explained that it had considered Contreras-Delgado’s “personal\n\ncharacteristics, as well as the nature of the offense.” Contreras-\n\nDelgado’s machine gun “was loaded with a 31-round high capacity\n\nmagazine,” he had additional high-capacity magazines, he admitted\n\nthat he requested a fully automatic gun when he purchased it, and\n\nhe confessed to selling drugs. Those facts, plus Contreras-\n\nDelgado’s prior violent threats and the fact that he had not\n\nreformed despite prior leniency, “move[d] the Court to impart a\n\nsentence above the guideline range” to “reflect[] the seriousness\n\nof the offense, promote[] respect for the law, protect[] the public\n\nfrom further crimes by Mr. Contreras[-Delgado], and address[] the\n\nissues of deterrence and punishment.” Accordingly, the court\n\nsentenced Contreras-Delgado to 46 months’ imprisonment and three\n\nyears’ supervised release.\n\n This appeal ensued.\n\n II. DISCUSSION\n\n A. Basic Principles.\n\n As we detail below, Contreras-Delgado contends that the\n\n46-month variant incarceration sentence was both procedurally and\n\nsubstantively unreasonable. “We review sentencing decisions\n\nimposed under the advisory Guidelines, whether outside or inside\n\nthe applicable GSR, for reasonableness.” United States v.\n\n\n - 8 -\n\fPantojas-Cruz, 800 F.3d 54, 58 (1st Cir. 2015) (citing United\n\nStates v. Turbides-Leonardo, 468 F.3d 34, 40 (1st Cir. 2006)).\n\nThis review incorporates two components directed at the appraisal\n\nof procedural soundness and then substantive reasonableness of the\n\nsentence. See Gall v. United States, 552 U.S. 38, 51 (2007);\n\nUnited States v. Cox, 851 F.3d 113, 119-20 (1st Cir. 2017); United\n\nStates v. Gallardo-Ortiz, 666 F.3d 808, 811 (1st Cir. 2012). Thus,\n\nfirst, we examine whether in arriving at the sentence, the district\n\ncourt committed any procedural errors. United States v. Rossignol,\n\n780 F.3d 475, 477 (1st Cir. 2015); Gallardo-Ortiz, 66 F.3d at 811.\n\nSuch missteps include “failing to calculate (or improperly\n\ncalculating) the Guidelines range, treating the Guidelines as\n\nmandatory, failing to consider the § 3553(a) factors, selecting a\n\nsentence based on clearly erroneous facts, or failing to adequately\n\nexplain the chosen sentence — including an explanation for any\n\ndeviation from the Guidelines range.” Gall, 552 U.S. at 51. “We\n\nhave described our abuse of discretion standard in this context as\n\n‘multifaceted,’ as we apply clear error review to factual findings,\n\nde novo review to interpretations and applications of the\n\nguidelines, and abuse of discretion review to judgment calls.”\n\nUnited States v. Nieves-Mercado, 847 F.3d 37, 42 (1st Cir. 2017).\n\nWhile this court generally applies “the deferential abuse of\n\ndiscretion standard to preserved challenges to the procedural\n\nreasonableness of a sentence, . . . when a defendant fails to\n\n\n - 9 -\n\fpreserve an objection to the procedural reasonableness below [of\n\nthe sentence but asserts it on appeal], the plain error standard\n\nsupplants that customary standard of review.” United States v.\n\nGierbolini-Rivera, 900 F.3d 7, 12 (1st Cir. 2018); see United\n\nStates v. Ruiz-Huertas, 792 F.3d 223, 226 (1st Cir. 2015). The\n\nplain error standard “is not easy to meet, because it requires\n\nerror, plainness, prejudice to the defendant and the threat of a\n\nmiscarriage of justice.” United States v. Torres-Rosario, 658\n\nF.3d 110, 116 (1st Cir. 2011) (citing United States v. Olano, 507\n\nU.S. 725, 732-36 (1993)).\n\n If procedural soundness is established, we then proceed\n\nto the second phase of our review, assessing the substantive\n\nreasonableness of the sentence, “tak[ing] into account the\n\ntotality of the circumstances, including the extent of any variance\n\nfrom the Guidelines range.” United States v. Bermúdez-Meléndez,\n\n827 F.3d 160, 163 (1st Cir. 2016) (alteration in original) (quoting\n\nGall, 552 U.S. at 51). “In determining substantive reasonableness,\n\nsubstantial respect is due to the sentencing court’s discretion.”\n\nId. This deferential approach recognizes that although “[a]\n\nsentencing court is under a mandate to consider a myriad of\n\nrelevant factors, . . . the weighting of those factors is largely\n\nwithin the court’s informed discretion.” United States v.\n\nClogston, 662 F.3d 588, 593 (1st Cir. 2011). For substantive\n\nreasonableness, the linchpin is “a plausible sentencing rationale\n\n\n - 10 -\n\fand a defensible result.” United States v. Pol-Flores, 644 F.3d\n\n1, 4-5 (1st Cir. 2011) (quoting United States v. Martin, 520 F.3d\n\n87, 96 (1st Cir. 2008)). Hence, “we limit our review to the\n\nquestion of whether the sentence, in light of the totality of the\n\ncircumstances, resides within the expansive universe of reasonable\n\nsentences.” United States v. King, 741 F.3d 305, 308 (1st Cir.\n\n2014). While some circuits have found substantive reasonableness\n\nclaims preserved despite a lack of objection in the lower court,\n\nand thus not reviewed for plain error, see United States v.\n\nHernández-Maldonado, 793 F.3d 223, 227 (1st Cir. 2015), in our\n\ncircuit the question remains open. See United States v. Rondón-\n\nGarcía, 886 F.3d 14, 26 (1st Cir. 2018); United States v.\n\nArsenault, 833 F.3d 24, 29 (1st Cir. 2016).\n\n Even if plain error is not applied, considerable\n\ndeference must still be given to the district court’s judgment.\n\nClogston, 662 F.3d at 593. This “highly deferential . . . standard\n\nremains in full force” even if the sentence is outside the\n\napplicable GSR. United States v. Vázquez-Martínez, 812 F.3d 18,\n\n26 (1st Cir. 2016) (quoting United States v. Santiago-Rivera, 744\n\nF.3d 229, 234 (1st Cir. 2014)); see also Gallardo-Ortiz, 666 F.3d\n\nat 811 (“A dramatic variance . . . cannot unduly influence our\n\nreview of substantive reasonableness.”). Accordingly, even when\n\nthe district court imposes a variant sentence, this court affords\n\n“due deference to the district court’s decision that the § 3553(a)\n\n\n - 11 -\n\ffactors, on a whole, justify the extent of the variance.” Gall,\n\n552 U.S. at 51.\n\n B. Procedural Reasonableness.\n\n Contreras-Delgado argues on appeal that the district court\n\nabused its discretion in denying his request to present the live\n\ntestimony of Dr. Ramos, the clinical psychologist who had evaluated\n\nhim while he was in jail, and that this denial constitutes\n\nprocedural error because he was precluded from presenting\n\n“information relevant to recidivism and rehabilitation . . . as\n\npart of § 3553(a)’s sentencing factors.” He also asserts that\n\nthe court “overstated” the evidence of his prior violent threats.\n\nContreras-Delgado argues generally that the court did not\n\nappropriately balance the § 3553(a) factors, thereby violating the\n\nparsimony principle – the statutory directive that sentences\n\nshould be no higher than necessary to achieve the statutory goals\n\nof sentencing. Specifically, Contreras-Delgado complains that the\n\ncourt did not mention Contreras-Delgado’s mental characteristics,\n\nsuch as depression and attention deficit hyperactivity disorder.\n\n 1.\n\n Contreras-Delgado contends that the district court\n\nabused its discretion when it did not allow the testimony of Dr.\n\nRamos at the sentencing hearing and further failed to consider\n\n§ 3353(a) sentencing factors. The government counters that\n\nContreras-Delgado did not object to this denial and, thus, the\n\n\n - 12 -\n\fappropriate standard of review is for plain error. It is well\n\nestablished that articulating an objection is required in order to\n\npreserve the most generous standard for a defendant. This not\n\nonly protects the interests of the defendant but also provides the\n\ngovernment with an opportunity to respond. Proper objection also\n\nfurthers the interests of judicial economy in that it assists\n\njudicial decision-making. To be sure, the record would have been\n\ncleaner if the talismanic “I object” formulation had been uttered.\n\nAt the same time, a review of the record leaves little doubt that\n\ncounsel sought to present the live testimony of the witness and\n\npersisted in explaining why it was necessary even after it had\n\nbeen denied. In any event, whether the standard of review be abuse\n\nof discretion or plain error, we conclude that Contreras-Delgado’s\n\nclaim of procedural error cannot succeed.\n\n First, we note that while a defendant enjoys a right to\n\ndue process at sentencing, United States v. Stile, 845 F.3d 425,\n\n430 (1st Cir. 2017), and the right “to speak or present any\n\ninformation to mitigate the sentence,” Fed. R. Crim. P.\n\n32(i)(4)(A)(ii); see also Irizarry v. United States, 553 U.S. 708,\n\n715 (2008), “a defendant has no right to insist on calling other\n\nwitnesses on his behalf.” Stile, 845 F.3d at 430. See United\n\nStates v. Cruzado-Laureano, 527 F.3d 231, 238 (1st Cir. 2008);\n\nUnited States v. Heller, 797 F.2d 41, 43 (1st Cir. 1986). “The\n\nrule only requires the court to allow the defendant and his\n\n\n - 13 -\n\fattorney to speak.” Cruzado-Laureano, 527 F.3d at 238 (citing\n\nFed. R. Crim. P. 32(i)(4)(A)(i), (ii); United States v. Rodriguez,\n\n336 F.3d 67, 70 (1st Cir. 2003)).\n\n Here, the district court not only reviewed Dr. Ramos’s\n\nreport from the bench, but it summarized her recommendations and,\n\nas reflected in the district court’s correction of counsel’s\n\ninterpretation, demonstrated command of its contents. Moreover,\n\nDr. Ramos’s entire report was included in the PSR, where, as the\n\ndistrict court noted, it could guide the Bureau of Prisons and\n\nProbation as they determined appropriate treatment. Further,\n\nContreras-Delgado’s counsel fully explained to the court his view\n\nthat Dr. Ramos’s report supported a mitigation of the sentence\n\nbelow the GSR. In sum, under any standard of review, Contreras-\n\nDelgado’s claim that substitution of Dr. Ramos’s report in lieu of\n\ntestimony constituted procedural error is not meritorious.2\n\n 2.\n\n Contrary to Contreras-Delgado’s assertion, the district\n\ncourt properly considered the § 3553(a) sentencing factors,\n\n\n\n\n2 We note that the government also argues that Contreras-Delgado\nconsented to the substitution of Dr. Ramos’s report in lieu of her\nlive testimony, and that this consent constituted waiver, instead\nof forfeiture, such that he may not revive his waived argument on\nappeal. See generally United States v. Delgado-Sánchez, 849 F.3d\n1, 6-7 (1st Cir. 2017) (reviewing waiver and forfeiture standards).\nThe record is open to a different interpretation. In any event,\nwe need not resolve the issue because, as we have indicated,\nContreras-Delgado’s claim fails. Id. at 7.\n\n\n - 14 -\n\fincluding relevant mitigating and aggravating factors; its\n\nweighing of those factors was well within its discretion. While\n\na sentencing court must consider all the incorporated § 3553(a)\n\nfactors, it “need not verbalize its evaluation of each and every\n\n[§] 3553(a) factor.” United States v. Reyes-Rivera, 812 F.3d 79,\n\n89 (1st Cir. 2016). Moreover, it “is not required to address the\n\n§ 3553(a) factors one by one, in some sort of rote incantation\n\nwhen explicating its sentencing decision, nor must the court afford\n\neach of the § 3553(a) factors equal prominence.” United States v.\n\nSosa-González, 900 F.3d 1, 5 (1st Cir. 2018) (quoting United States\n\nv. Vázquez-Vázquez, 852 F.3d 62, 66 (1st Cir. 2017)). Here, the\n\ncourt expressly stated that it had considered the § 3553(a)\n\nsentencing factors. That statement is “entitled to significant\n\nweight.” United States v. Caballero-Vázquez, 896 F.3d 115, 120\n\n(1st Cir. 2018) (quoting Santiago-Rivera, 744 F.3d at 233). It\n\nalso implicitly acknowledges awareness of and accordance with the\n\nparsimony principle. Turbides-Leonardo, 468 F.3d at 41 (“[T]he\n\nsentencing court in this case acknowledged its awareness of the\n\nparsimony principle during the disposition hearing, stating that\n\nit had taken [§] 3553(a) into account in arriving at the 48-month\n\nsentence. On these facts, no more is exigible.”).\n\n Moreover, the district court discussed the relevant\n\nsentencing factors on the record. First, the district court\n\nexpressly considered Contreras-Delgado’s history and\n\n\n - 15 -\n\fcharacteristics, including his age, employment, and substance\n\nabuse history. Then, the court specified the facts it found\n\nwarranted a sentence above the applicable GSR: Contreras-Delgado’s\n\nautomatic weapon was loaded with a 31-round high-capacity magazine\n\nand 31 rounds of ammunition; Contreras-Delgado had a second 31-\n\nround high-capacity magazine, also fully loaded with 9-mm\n\nammunition for the automatic weapon; Contreras-Delgado had a third\n\nhigh-capacity magazine, this one with 15 rounds of 9-mm ammunition;\n\nContreras-Delgado not only knew the weapon was fully automatic,\n\nbut specifically requested that modification when he purchased it;\n\nContreras-Delgado had previously benefited from leniency and the\n\n“probation and programs offered by the Commonwealth of Puerto Rico\n\nand the Court of Juvenile Affairs”; Contreras-Delgado admitted\n\nselling drugs and had in fact been arrested -- though not convicted\n\n-- for possession with intent to distribute marijuana and cocaine;\n\nand Contreras-Delgado’s criminal history included “threatening to\n\nkill children with a knife and threatening to kill his mother.”\n\nContreras-Delgado’s suggestion that the district court somehow\n\nerred by characterizing these violent threats as violent behavior\n\nis unavailing. See, e.g., United States v. Harden, 866 F.3d 768,\n\n774 (7th Cir. 2017) (noting that a statutory “definition of violent\n\noffense comports with a common-sense understanding of violent\n\nconduct as the use or threat of physical force against another and\n\n\n\n\n - 16 -\n\fis relevant as a guidepost as to a common definition of\n\n‘violence.’” (emphasis added)).\n\n These are all statutorily authorized sentencing\n\nconsiderations; each of these facts relates to the nature and\n\ncircumstances of the offense (especially those not already\n\naccounted for by the guidelines) or to Contreras-Delgado’s history\n\nand characteristics. See 18 U.S.C. § 3553(a)(1). Basing\n\nContreras-Delgado’s sentences on these factors cannot constitute\n\nprocedural error, nor will this court “disturb a well-reasoned\n\ndecision” -- including the one here -- “to give greater weight to\n\nparticular sentencing factors over others.” United States v.\n\nSantini-Santiago, 846 F.3d 487, 492 (1st Cir. 2017) (quoting United\n\nStates v. Gibbons, 553 F.3d 40, 47 (1st Cir. 2009)).\n\n The district court expressly found that a sentence above\n\nthe GSR was further supported by the statutory sentencing\n\nconsiderations of: “reflect[ing] the seriousness of the offense,\n\npromot[ing] respect for the law, protect[ing] the public from\n\nfurther crimes by Mr. Contreras[-Delgado], and address[ing] the\n\nissues of deterrence and punishment.” That finding must be\n\nafforded a high level of deference on appeal, regardless of the\n\nstandard of review applied. See Vázquez-Martínez, 812 F.3d at 26.\n\n Contreras-Delgado’s claim “that the court erred by\n\nrelying on [negative factors] excessively” thus simply “amounts to\n\na disagreement with the district court’s weighing of the different\n\n\n - 17 -\n\fsentencing factors.” United States v. Cruz-Vázquez, 841 F.3d 546,\n\n550 (1st Cir. 2016). That the district court -- after careful\n\nconsideration of the statutory factors and explanation of its\n\nreasoning -- weighed the factors differently than Contreras-\n\nDelgado is not error. United States v. Carrasco-de-Jesus, 589\n\nF.3d 22, 29 (1st Cir. 2009).\n\n All the potentially mitigating factors Contreras-Delgado\n\nidentifies on appeal were discussed in the PSR, in Contreras-\n\nDelgado’s sentencing memorandum, and/or at sentencing. “The\n\npotentially mitigating factors [the defendant] identifies on\n\nappeal were thoroughly discussed in the presentence report; that\n\nthe district court did not explicitly mention them during the\n\nsentencing hearing suggests they were unconvincing, not ignored.”\n\nUnited States v. Lozada-Aponte, 689 F.3d 791, 793 (1st Cir. 2012).\n\n Moreover, although the district court did not recite\n\nContreras-Delgado’s mental health history, it did review Dr.\n\nRamos’s report and direct that it be added to the PSR, which\n\nsignals consideration of its contents. “The record . . . supports\n\nthe conclusion that the District Court simply focused on other\n\nconsiderations that it implicitly deemed more important, including\n\nthe defendant’s history of violent behavior.” United States v.\n\nOcchiuto, 784 F.3d 862, 869 (1st Cir. 2015). The fact that\n\nContreras-Delgado would have preferred that greater weight be\n\ngiven to his psychological issues rather than to the seriousness\n\n\n - 18 -\n\fof his criminal behavior is not a reason to vacate his sentence.\n\nSee, e.g., United States v. Arroyo-Maldonado, 791 F.3d 193, 201\n\n(1st Cir. 2015) (finding no error where the defendant sought to\n\nsubstitute his judgment for that of the sentencing court).\n\n Regarding Contreras-Delgado’s prior behavior, the\n\ndistrict court did include a factually accurate comment that\n\nContreras-Delgado had been arrested, but not convicted, of\n\npossessing drugs with intent to distribute them at the state level.\n\nContreras-Delgado separately admitted that he “sells drugs . . .\n\nto make a living,” so it is undisputed that he committed drug\n\ntrafficking offenses not reflected in his criminal history score.\n\nThus, the district court did not run afoul of this court’s\n\nadmonition not to use mere arrests to “infer unlawful behavior\n\nunless there is proof by a preponderance of the evidence of the\n\nconduct” those charges allege. Rondón-García, 886 F.3d at 25)\n\n(citing United States v. Cortés-Medina, 819 F.3d 566, 570 (1st\n\nCir. 2016)). The district court’s use of the phrase “[a]s usual”\n\nto describe the dismissal of those drug-distribution charges did\n\nnot render Contreras-Delgado’s underrepresented criminal history\n\nan impermissible consideration. See 18 U.S.C. § 3553.\n\n Accordingly, Contreras-Delgado’s claim fails under any\n\nstandard of review. Even under the more defendant-friendly abuse\n\nof discretion standard, Contreras-Delgado’s arguments fail because\n\nhis sentence was properly based on permissible § 3553(a) sentencing\n\n\n - 19 -\n\ffactors, and the allegedly mitigating factors were considered by\n\nthe district court. See Arroyo-Maldonado, 791 F.3d at 201.3\n\n C. Substantive Reasonableness.\n\n An inquiry into the substantive reasonableness of a\n\nsentence must “take into account the totality of the circumstances,\n\nincluding the extent of any variance from the Guidelines range.”\n\nGall, 552 U.S. at 51. “The hallmarks of a substantively reasonable\n\nsentence are ‘a plausible sentencing rationale and a defensible\n\nresult.’” United States v. Zapata-Vázquez, 778 F.3d 21, 24 (1st\n\nCir. 2015) (quoting Martin, 520 F.3d at 96). Under the totality\n\nof the circumstances here, Contreras-Delgado’s 46-month sentence\n\nwas substantively reasonable.\n\n As has been noted, it is clear from the record that the\n\ndistrict court sufficiently considered the relevant § 3553\n\nsentencing factors. See supra pp. 15-20. The court assessed the\n\ndangerous nature and circumstances of the offense of conviction,\n\nincluding the fact that the machine gun possession offense also\n\ninvolved a substantial amount of ammunition and multiple high-\n\ncapacity magazines, heightening the risk posed to the public.\n\n\n\n\n3 Because Contreras-Delgado’s improper-weight arguments fail\nregardless of the standard of review, it is immaterial whether\nthey are characterized as procedural or substantive arguments.\nCf. Caballero-Vázquez, 896 F.3d at 120 n.1 (noting that First\nCircuit “precedent is less-than-clear as to whether a sentencing\ncourt’s weighing of mitigating factors implicates procedural or\nsubstantive reasonableness”).\n\n\n - 20 -\n\fMoreover, Contreras-Delgado admitted committing other crimes\n\n(specifically, selling drugs) for which he had never been punished,\n\ndespite having been previously arrested. That, as well as the\n\nfact that Contreras-Delgado’s prior juvenile convictions for\n\nthreats of violence resulted in no criminal history points, support\n\nthe conclusion that the district court was well within its\n\ndiscretion to believe that the GSR underrepresented Contreras-\n\nDelgado’s criminal history. “[A] district court may vary a\n\nsentence upward in an effort to reflect past leniency.” United\n\nStates v. Santiago-González, 825 F.3d 41, 49 (1st Cir. 2016)\n\n(citing United States v. Flores-Machicote, 706 F.3d 16, 21 (1st\n\nCir. 2013)). Indeed, the district court noted that despite his\n\nprior brushes with the law, Contreras-Delgado had “benefited from\n\nprobation and programs” instead of imprisonment. The court thus\n\nacted within the bounds of its discretion when it determined that\n\nContreras-Delgado’s offense —- when viewed in light of his history\n\n—- warranted a variant sentence. See United States v. Romero-\n\nGalindez, 782 F.3d 63, 71-72 (1st Cir. 2015). “[D]eviation[s]\n\nfrom the Guidelines ‘should typically be rooted either in the\n\nnature and circumstances of the offense or the characteristics of\n\nthe offender.’” Id. (quoting Martin, 520 F.3d at 91)). Here,\n\nthe district court rooted its variant sentence in both.\n\n We further note that the length of the sentence does not\n\nmake it per se unreasonable. “The district court evaluated the\n\n\n - 21 -\n\ffactors provided under 18 U.S.C. § 3553(a) and determined that an\n\nabove-guidelines sentence was appropriate.” Santini-Santiago, 846\n\nF.3d at 492 (upholding a district court’s 18-month variance above\n\nan applicable GSR of 12 to 18 months, partly due to the weight the\n\ndistrict court placed on the seriousness of the offense).\n\nContreras-Delgado’s sentence falls well within the “expansive\n\nuniverse of substantively reasonable sentences.” United States v.\n\nMatos-de-Jesús, 856 F.3d 174, 180 (1st Cir. 2017) (upholding a\n\nsentence 15 months longer than the top end of the GSR). “Decisions\n\nlike these are within the sound discretion of sentencing courts,\n\nand [this court] ‘will not disturb a well-reasoned decision to\n\ngive greater weight to particular sentencing factors over\n\nothers.’” Santini-Santiago, 846 F.3d at 492 (quoting Gibbons, 553\n\nF.3d at 47).\n\n In this case, Contreras-Delgado faced a statutory\n\nmaximum sentence of up to ten years of imprisonment. See 18 U.S.C.\n\n§ 922(o). His actual sentence of less than four years is not only\n\ndefensibly within “the expansive boundaries of [the] universe” of\n\nreasonable sentences, but also well within the statutory bounds of\n\nthe district court’s discretion, and represents a fraction of\n\nContreras-Delgado’s exposure. Martin, 520 F.3d at 92; see also\n\nUnited States v. Díaz-Bermúdez, 778 F.3d 309, 313-14 (1st Cir.\n\n2015) (comparing sentence to statutory maximum, and collecting\n\ncases upholding variances several years above the guidelines).\n\n\n - 22 -\n\f“[A]n increased sentence is necessarily a judgment call and, within\n\nwide limits, deference is due to the trier’s on-the-spot\n\nperceptions.” Arroyo-Maldonado, 791 F.3d at 198 (quoting United\n\nStates v. Vargas-Dávila, 649 F.3d 129, 131 (1st Cir. 2011)). We\n\nthus defer to the district court’s reasoned decision that, under\n\nthe circumstances, Contreras-Delgado’s behavior warranted a 46-\n\nmonth sentence.\n\n III. CONCLUSION\n\n In sum, a sentence should be left intact so long as it\n\nis procedurally sound and there is “a plausible sentencing\n\nrationale and a defensible result.” Martin, 520 F.3d at 96; Gall,\n\n552 U.S. at 49-50 (requiring individualized consideration and\n\nadequate explanation for variances). The district court provided\n\nindividualized assessments of Contreras-Delgado’s conduct as well\n\nas the other § 3553 factors, and reasonably explained the basis\n\nfor the sentence imposed.\n\n We conclude that Contreras-Delgado’s sentence was\n\nprocedurally and substantively reasonable.\n\n The sentence is affirmed.\n\n\n\n\n - 23 -\n[END_CASE]", "role": "user" } ]
4,583,006
UNITED STATES of America, v. Glenn A. CHIN, Defendant. Trustees of Boston University, Owner of the Radio Station WBUR (WBUR), Intervenor, Appellant.
United States v. Chin
2019-01-18
17-2048P
U.S. Court of Appeals for the First Circuit
{"judges": "Barron, Selya, Katzmann", "parties": "", "opinions": [{"author": "and Katzmann, Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-2048\n\n UNITED STATES OF AMERICA,\n\n v.\n\n GLENN A. CHIN,\n\n Defendant.\n\n\n TRUSTEES OF BOSTON UNIVERSITY,\n OWNER OF THE RADIO STATION WBUR (WBUR),\n\n Intervenor, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Richard G. Stearns, U.S. District Judge]\n\n\n Before\n\n Barron and Selya, Circuit Judges,\n and Katzmann, Judge.*\n\n\n Jeffrey J. Pyle, with whom Prince Lobel Tye LLP was on brief,\nfor appellant.\n Gregory Dubinsky, with whom Evan H. Stein and Holwell, Shuster\n& Goldberg LLP were on brief, for Court-appointed amicus curiae in\nsupport of affirmance.\n Nashwa Gewaily, New England First Amendment Coalition,\nSigmund D. Schutz, and Preti, Flaherty, Beliveau & Pachios, LLP,\non brief as amici curiae in support of appellant.\n\n * Of the United States Court of International Trade, sitting\nby designation.\n\fJanuary 18, 2019\n\f BARRON, Circuit Judge. This case concerns an appeal by\n\nthe Trustees of Boston University, as owners of WBUR, which is a\n\npublic radio station in Boston, Massachusetts. We will refer to\n\nthe appellant by the radio station's name, WBUR.\n\n The issue that we must decide arises from WBUR's motion\n\nin the fall of 2017 to intervene in a then still-ongoing criminal\n\ntrial in the United States District Court for the District of\n\nMassachusetts. In that motion, WBUR also requested that the\n\nDistrict Court unseal the names and addresses of the jurors in the\n\ncriminal case and provide that information to WBUR \"as soon as\n\npossible\" after the announcement of the jury's verdict.\n\n The District Court granted the motion to intervene but\n\notherwise denied in substantial part the motion to unseal the\n\nrequested information. We now vacate and remand.\n\n I.\n\n WBUR filed this motion in the criminal case against New\n\nEngland Compounding Center (\"NECC\") supervisory pharmacist Glenn\n\nChin. He had been charged with committing mail fraud and violating\n\nthe Racketeer Influenced and Corrupt Organizations Act (\"RICO\"),\n\n18 U.S.C. §§ 1961–1968, based on, among other things, twenty-five\n\npredicate acts of second-degree murder, in connection with a\n\nnationwide distribution of contaminated medications that caused a\n\nfatal outbreak of fungal meningitis.\n\n\n\n\n - 3 -\n\f Chin's trial began in federal district court in Boston\n\non September 19, 2017. It ended a little more than a month later,\n\non October 25, 2017, when the jury found Chin guilty of mail fraud\n\nand lesser predicate offenses under RICO but not guilty of the\n\ntwenty-five predicate acts of second-degree murder.\n\n A week before the trial ended, on October 18, 2017, WBUR\n\nfiled its motion both to intervene in the criminal case and to\n\nobtain \"as soon as possible after the verdict is announced\" the\n\nnames and addresses of the then-deliberating jurors. On October\n\n27, 2017 -- just two days after the jury had returned its verdict\n\n-- the District Court issued an order allowing intervention in the\n\ncriminal case by WBUR but denying, without prejudice, its motion\n\nregarding the disclosure of juror names and addresses.\n\n The District Court stated in that order that it would\n\n\"release\" juror names and hometowns, but not addresses, and that\n\nit would do so only after Chin's sentencing, which was scheduled\n\nfor January 30, 2018.1 The District Court did note in its order,\n\n\n 1 One of Chin's co-defendants was Barry Cadden, the owner of\nNECC, whose case had gone to trial in federal district court in\nBoston six months earlier. At Cadden's trial, the jury returned\na verdict sheet suggesting that the jurors had not voted\nunanimously to acquit Cadden of second-degree murder, even though\nthe not-guilty verdict required unanimity. WBUR filed a motion\nfor immediate access to juror names and addresses, and the District\nCourt ruled that it would release a list of each juror's name and\nhometown, though not each juror's address, only after sentencing,\nwhich was to occur three months later. WBUR, though unable to\nidentify every juror even after receiving the jurors' names and\nhometowns, ultimately interviewed two jurors from the Cadden trial\n\n - 4 -\n\fhowever, that it would \"consider an earlier release of the juror\n\nlist upon submission by [WBUR] of an appropriate protective order\n\nthat is . . . crafted to insure against any unnecessary\n\ndissemination of the jurors' personal identification in the news\n\nmedia or over the internet (without the juror's express assent).\"\n\n The District Court based this possible condition on\n\nrelease on a protective order requirement that Judge Young had\n\nimposed one week earlier in a similar ruling regarding WBUR's\n\nrequest for disclosure of juror names and addresses in another\n\ncase in the District of Massachusetts: United States v. Wright,\n\nNo. 15-cr-10153-WGY (D. Mass. Oct. 20, 2017), ECF No. 357. Judge\n\nYoung withdrew the protective order requirement in Wright on\n\nNovember 3, 2017, however, after WBUR challenged that requirement\n\non the grounds that it would be impractical and perhaps\n\nunconstitutional.\n\n A little less than two weeks later, on November 16, 2017,\n\nWBUR appealed from the District Court's order denying its request\n\nin Chin. The next day, the District Court issued an \"Amended Order\n\non Motion of [WBUR] to Unseal Juror Names and Addresses,\" which,\n\njust as Judge Young had done in Wright, withdrew the protective\n\norder requirement. In the amended order, the District Court\n\nreiterated that it would \"release\" a list of the Chin jurors' names\n\n\nand aired a report stating that those two jurors did not understand\nthat not-guilty verdicts required unanimity.\n\n\n - 5 -\n\fand hometowns, but not addresses, and that it would do so only\n\nafter sentencing.\n\n In accord with the initial order, on January 31, 2018,\n\nthe day after the sentencing proceedings in Chin's case ended, the\n\nDistrict Court issued an unsealed order containing a list of the\n\njurors' names and their hometowns, but not their addresses.\n\nBecause neither the government nor Chin opposes WBUR's motion on\n\nappeal, we ordered the appointment of amicus counsel (\"Court-\n\nappointed amicus\") to represent the position reflected in the\n\nDistrict Court's order denying WBUR's motion in substantial part,\n\na task that the amicus has ably performed.2\n\n II.\n\n We begin by addressing our jurisdiction to hear this\n\nappeal, which turns out to be a task that is not without its\n\ncomplexities. The most prominent jurisdictional question that we\n\nconfront concerns the possibility that this appeal has been mooted\n\nby the District Court's granting of partial relief to WBUR and the\n\nfact that Chin's sentencing has already occurred. But, before we\n\nget to that jurisdictional question, we address two others, the\n\nfirst of which relates to the appellant's status as an intervenor.\n\n We stated in In re Globe Newspaper Co., 920 F.2d 88, 90\n\n(1st Cir. 1990), that \"the right of a non-party to intervene in a\n\n\n 2 We also acknowledge the helpful amicus brief filed by the\nNew England First Amendment Coalition, et al.\n\n\n - 6 -\n\fcriminal proceeding is doubtful.\" But, we nonetheless concluded\n\n-- even without finding that the appellant there could intervene\n\n-- that we had jurisdiction over the appeal under the All Writs\n\nAct, 28 U.S.C. § 1651. See In re Providence Journal Co., Inc.,\n\n293 F.3d 1, 9 (1st Cir. 2002) (explaining that the All Writs Act\n\ngives \"[a] federal court of appeals . . . the power to treat an\n\nattempted appeal from an unappealable (or possibly unappealable)\n\norder as a petition for a writ of mandamus\" (quoting United States\n\nv. Horn, 29 F.3d 754, 769 (1st Cir. 1994))).\n\n Here, however, the District Court did grant WBUR's\n\nmotion to intervene. And, because that \"legal decision\" to grant\n\nWBUR's motion remained \"unchallenged in [this] appeal despite the\n\nexistence of ample opportunity to [challenge it],\" it is now \"law\n\nof the case for future stages of the same litigation\" and therefore\n\n\"should continue to govern the same issues.\" United States v.\n\nMatthews, 643 F.3d 9, 12 (1st Cir. 2011) (citations omitted).\n\nThus, as an intervenor, WBUR may appeal the District Court's order\n\ndenying its request for the disclosure of juror names and\n\naddresses, which WBUR filed before sentencing and thus before the\n\nmatter had concluded -- assuming, that is, the appeal is not moot.\n\nSee United States v. Blagojevich, 612 F.3d 558, 560 (7th Cir. 2010)\n\n\n\n\n - 7 -\n\f(applying the collateral order doctrine in finding jurisdiction\n\nover an appeal by an intervenor in a similar case).3\n\n The next jurisdictional wrinkle that we must iron out\n\nconcerns the timing of the appeal relative to the issuance of the\n\nDistrict Court's amended order in this case. Neither WBUR nor\n\nCourt-appointed amicus makes anything of the fact that the District\n\nCourt issued its amended order the day after WBUR filed its notice\n\nof appeal. But, the general rule is that \"[t]he filing of a notice\n\nof appeal is an event of jurisdictional significance -- it confers\n\njurisdiction on the court of appeals and divests the district court\n\nof its control over those aspects of the case involved in the\n\nappeal.\" Griggs v. Provident Consumer Discount Co., 459 U.S. 56,\n\n58 (1982).\n\n Nevertheless, \"this circuit and others have recognized\n\nlimited exceptions to this judge-made rule.\" United States v.\n\nTorres-Oliveras, 583 F.3d 37, 44 (1st Cir. 2009) (citing 16A\n\nCharles A. Wright, et al., Federal Practice and Procedure § 3949.1\n\n(4th ed. 2009); United States v. Ortega, 859 F.2d 327, 334–35 (5th\n\nCir. 1988)). And, arguably, the District Court's amended order\n\nhere falls within one of the recognized exceptions because it does\n\n\n\n 3 Nor do we think that the fact that the motion to unseal the\njuror names and addresses was denied \"without prejudice\" is of\njurisdictional significance, under the collateral order doctrine,\ngiven that the request was for the release of the jurors'\nidentifying information \"as soon as possible\" post-verdict.\n\n\n - 8 -\n\fnot \"alter the substance of the decision\" to release juror names\n\nand hometowns after sentencing. See Wright, et al. § 3949.1.\n\n In any event, we will treat the District Court's November\n\n17, 2017 order as though it were an indicative ruling regarding\n\nthe withdrawal of the protective order requirement. Cf. United\n\nStates v. Maldonado-Rios, 790 F.3d 62, 65 (1st Cir. 2015) (per\n\ncuriam) (treating a sentencing court's grant of a motion filed\n\nduring the pendency of appeal as an indicative ruling under Federal\n\nRule of Appellate Procedure 12.1). And, even if we consider on\n\nappeal only the District Court's October 27, 2017 order, our\n\nanalysis of the merits is not affected. See Torres-Oliveras, 583\n\nF.3d at 44.\n\n We come, then, to the main potential jurisdictional\n\nobstacle to our reaching the merits of this appeal. Court-\n\nappointed amicus contends that the appeal is moot in its entirety,\n\nand thus no longer a live case or controversy requiring resolution,\n\nbecause the District Court released the names and hometowns of the\n\nChin jurors on January 31, 2018.\n\n \"The burden of establishing mootness rests with the\n\nparty invoking the doctrine.\" ACLU of Mass. v. U.S. Conference of\n\nCatholic Bishops, 705 F.3d 44, 52 (1st Cir. 2013). Because no\n\nfactual findings bear on the matter, we decide the legal issue de\n\nnovo. See id.\n\n\n\n\n - 9 -\n\f As to WBUR's appeal of the denial of its request for the\n\njurors' addresses, Court-appointed amicus argues that the access\n\nto names and hometowns that the District Court provided is\n\nsufficient for WBUR to identify the jurors and thus renders any\n\nopinion ordering the release of juror addresses \"merely advisory.\"\n\nSee Mangual v. Rotger-Sabat, 317 F.3d 45, 60 (1st Cir. 2003) (\"If\n\nevents have transpired to render a court opinion merely advisory,\n\nArticle III considerations require dismissal of the case.\").\n\nAccordingly, Court-appointed amicus contends that this aspect of\n\nWBUR's appeal is moot.\n\n But, the District Court has not unsealed some of the\n\ninformation that WBUR sought in its motion -- namely, the addresses\n\nof the jurors. And, it is undisputed that WBUR has not been able\n\nto contact all twelve jurors in the Chin trial, even though the\n\nDistrict Court provided WBUR with access to their names and\n\nhometowns. Consequently, the unsealing of the requested\n\naddresses, even at this point, would provide \"effectual relief\" to\n\nWBUR with respect to its appeal of the District Court's order\n\ndenying its motion requesting the information that thus far has\n\nbeen withheld. ACLU of Mass., 705 F.3d at 52. This aspect of the\n\nappeal, therefore, is not moot.\n\n The mootness question is not quite so easily resolved\n\nwith respect to WBUR's appeal of the District Court's denial of\n\nthe request to release the jurors' identifying information post-\n\n\n - 10 -\n\fverdict, rather than post-sentencing. The sentencing occurred\n\nnearly a year ago. There is no way to turn back the clock. Thus,\n\nthere is some force to the suggestion of mootness by Court-\n\nappointed amicus as to the aspect of WBUR's appeal that concerns\n\nthe timing of the release of the requested information.\n\n Nevertheless, in contending that this aspect of its\n\nappeal also is not moot, WBUR relies on an exception to the\n\nmootness doctrine that exists for a controversy that is \"capable\n\nof repetition, yet evading review.\" Kingdomware Technologies,\n\nInc. v. United States, 136 S. Ct. 1969, 1976 (2016) (quoting\n\nSpencer v. Kemna, 523 U.S. 1, 17 (1998)). In particular, WBUR\n\nargues that, although sentencing has already occurred, WBUR likely\n\n\"will again be subjected to the alleged illegality\" because that\n\n\"alleged illegality\" is capable of repetition and would continue\n\nto evade review. Murphy v. Hunt, 455 U.S. 478, 483 (1982) (per\n\ncuriam); ACLU of Mass., 705 F.3d at 57 (emphasis omitted) (quoting\n\nCity of Los Angeles v. Lyons, 461 U.S. 95, 109 (1983)).\n\n To qualify for this exception to the mootness doctrine,\n\nWBUR bears the burden of showing that \"(1) the challenged action\n\nwas in its duration too short to be fully litigated prior to its\n\ncessation or expiration, and (2) there was a reasonable expectation\n\nthat the same complaining party would be subjected to the same\n\naction again.\" Gulf of Maine Fisherman's All. v. Daley, 292 F.3d\n\n84, 89 (1st Cir. 2002) (quoting Weinstein v. Bradford, 423 U.S.\n\n\n - 11 -\n\f147, 149 (1975)). We conclude that WBUR has made the required\n\nshowing.\n\n About three months elapsed between the verdict and\n\nsentencing in Chin. That period of time is \"too short\" to complete\n\nlitigation, given that the appeal process often takes longer than\n\na few months. Id. But, that fact should not preclude WBUR's\n\nchallenge to a delay in the disclosure of the requested information\n\nthat, though shorter than the time frame for most litigation, was\n\nstill significant enough to affect WBUR's reporting. WBUR has\n\nalso shown that it frequently requests that the District of\n\nMassachusetts unseal jury lists as soon as possible following a\n\nverdict in order to obtain information that would enable it to\n\nreport on cases in the District. And, WBUR has shown that, in a\n\nnumber of instances, judges in the District have waited until after\n\nsentencing to release the requested juror information.\n\n Therefore, we conclude that WBUR has met its burden under\n\nthe exception to the mootness doctrine on which it relies in asking\n\nus to consider its appeal with respect to the timing issue. And\n\nso, satisfied that WBUR's appeal is not moot, and having disposed\n\nof the other possible jurisdictional issues that might have cut\n\nshort our consideration of this appeal, we now turn to the merits\n\nof the case.\n\n\n\n\n - 12 -\n\f III.\n\n In considering the merits, we direct our attention\n\nchiefly to one of our prior precedents: In re Globe Newspaper Co.,\n\n920 F.2d 88 (1st Cir. 1990). We do so because WBUR's appeal is\n\npremised in part on a contention about what that precedent holds.\n\n WBUR stated in its motion requesting the disclosure of\n\nthe juror information -- just as it now asserts on appeal -- that,\n\n\"under controlling precedent, the identities of the jurors 'must\n\nbe made public' after a verdict is rendered, unless the Court makes\n\n'particularized findings reasonably justifying nondisclosure.'\"\n\nThe assertedly \"controlling precedent\" that WBUR identifies is In\n\nre Globe. Because the interpretation of that precedent presents\n\na purely legal question, our review of whether In re Globe controls\n\nthe outcome here -- as WBUR contends that it does -- is de novo.\n\nSee United States v. Mayendía-Blanco, 905 F.3d 26, 34 (1st Cir.\n\n2018). If we conclude that In re Globe does control here, then we\n\nmust consider Court-appointed amicus's alternative argument that\n\nwe should revisit that holding in light of changes in technology\n\nover the past thirty years since In re Globe was decided.\n\n A.\n\n WBUR is right that, insofar as In re Globe requires a\n\ndistrict court in a particular case to disclose juror names and\n\naddresses post-trial, but pre-sentencing, In re Globe allows for\n\nan exception to that requirement only if the district court makes\n\n\n - 13 -\n\f\"particularized findings reasonably justifying non-disclosure.\"\n\nSee In re Globe, 920 F.2d at 98. WBUR is also right that such\n\n\"finding[s] of exceptional circumstances [must be] peculiar to the\n\ncase.\" Id. at 97. Moreover, In re Globe provides examples of\n\n\"[s]uch circumstances,\" and they include \"a credible threat of\n\njury tampering, a risk of personal harm to individual jurors, and\n\nother evils affecting the administration of justice.\" Id.\n\n Here, the District Court did not make any\n\n\"particularized findings\" regarding such exceptional circumstances\n\nthat were peculiar to this case. Nor does Court-appointed amicus\n\nsuggest that the District Court did so when denying in substantial\n\npart WBUR's motion to release the requested information. Instead,\n\nthe District Court in its amended order recounted the jury's\n\nhistorical role to explain, in part, its decision not to release\n\nany of the requested information to WBUR until after sentencing\n\nand not to release the jurors' addresses even then. The District\n\nCourt also placed great emphasis in its initial order on the\n\ntechnological realities that supply the present context for WBUR's\n\nrequest for juror information. As the District Court put it in\n\nits initial order:\n\n While the court respects the role of the media\n in promoting \"the public's long-term interest\n in maintaining an open judicial process,\" [In\n re Globe, 920 F.2d at 91], it will not release\n jurors' home addresses. . . . [T]his is . .\n . a necessary precaution in an age in which\n traditional boundaries of personal privacy are\n\n\n - 14 -\n\f under assault. While jurors serve in an\n important public capacity, it is a role thrust\n upon them as a duty of citizenship. The extent\n to which such service might compromise a\n juror's personal life once that service is\n concluded should be a matter in which the\n juror has the maximum say constitutionally\n possible.\n\n Thus, the first question before us is whether In re Globe\n\ndoes indeed require, as WBUR contends, the requested disclosure of\n\njuror addresses (as opposed to merely hometowns) post-trial,\n\nabsent the requisite \"particularized findings\" described above.\n\nThe second question that we must consider is whether In re Globe\n\nrequires the requested disclosure to occur \"as soon as possible\"\n\npost-verdict, absent \"particularized findings\" to justify a delay\n\nin the release of juror identities until after sentencing, which\n\nhere occurred three months after trial. For, if In re Globe does\n\nimpose either disclosure requirement in the absence of such\n\nfindings, then the order partially denying WBUR's motion did not\n\ncomply with that prior precedent. We thus now review what we said\n\nin In re Globe.\n\n B.\n\n The case arose out of the Globe Newspaper Company's\n\nrequest for access to the names and addresses of the jurors who\n\nhad participated in a then-just-completed criminal trial in a\n\nfederal district court in Boston. Id. at 90. The underlying\n\n\n\n\n - 15 -\n\fcriminal case concerned an alleged conspiracy to conceal illegal\n\ndrug profits involving three defendants. Id.\n\n The jury there had found two defendants guilty and one\n\nnot guilty. Id. On the same day that the verdict was rendered\n\nand the jury was discharged, \"Globe reporters sought access to the\n\ncourt's record of the juror names and addresses.\" Id.\n\n When the district court in that case refused to grant\n\nthe reporters the requested access, the newspaper company moved to\n\nintervene and to request access to the court's record of the juror\n\nnames and addresses. Id. That motion was denied, and the ensuing\n\nappeal by the newspaper company led to our decision in In re Globe.\n\n In reversing the ruling below, we recognized the\n\ncompeting interests, constitutional and otherwise, implicated by\n\nthe newspaper company's request for access to the names and\n\naddresses of jurors -– \"the press's First Amendment right of access\n\nto criminal trials[,] the defendant's Sixth Amendment right to a\n\nfair trial[, and] the jurors['] interest in having their privacy\n\nprotected.\" Id. at 93 (citations omitted). We also noted that\n\n\"[k]nowledge of juror identities allows the public to verify the\n\nimpartiality of key participants in the administration of justice,\n\nand thereby ensures fairness, the appearance of fairness and public\n\nconfidence in that system.\" Id. at 94. And, too, we noted, the\n\npublic disclosure of juror identities serves many of the same\n\n\n\n\n - 16 -\n\fpurposes of \"open justice\" that are protected by the First\n\nAmendment to the United States Constitution. Id.\n\n We chose, however, not to rest our decision reversing\n\nthe ruling below on a constitutional holding rooted in the First\n\nAmendment. Instead, we based our decision on a construction of\n\nwhat was then § 10(c) of the District of Massachusetts Plan for\n\nRandom Selection of Jurors (\"Jury Plan\"), which the District had\n\nadopted pursuant to the Jury Selection and Service Act of 1968, 28\n\nU.S.C. §§ 1861-1874 (1982) (\"the Act\").\n\n In construing those texts, we noted at the outset that,\n\nalthough the language of the Act and of the Jury Plan make no\n\nspecific distinction between pre-verdict and post-verdict\n\ndisclosure of juror identities, \"[t]he court's right to [keep names\n\nand addresses of jurors confidential] during the trial [was] not\n\nan issue in [In re Globe].\" In re Globe, 920 F.2d at 90. We\n\nobserved as well that \"[n]o doubt stronger reasons to withhold\n\njuror names and addresses will often exist during trial than after\n\na verdict is rendered\" and stated that \"[t]o justify impoundment\n\nafter the trial has ended, the court must find a significant threat\n\nto the judicial process itself.\" Id. at 91 (emphasis in original).\n\n Against that background understanding, we then construed\n\nthe Jury Plan in light of the newspaper company's request for post-\n\nverdict disclosure of juror identities. In doing so, we noted\n\nthat the Jury Plan's relevant provision barred the disclosure of\n\n\n - 17 -\n\fjuror names until the jurors \"have appeared, or failed to appear,\n\nin response to the summons.\" In re Globe, 920 F.2d at 92 & n.4\n\n(quoting Jury Plan § 10(c)). We noted as well that this same\n\nprovision then went on to state that \"[a]ny judge of this Court\n\nmay order that the names of jurors remain confidential even\n\nthereafter if the interests of justice so require.\" Id. (emphasis\n\nomitted) (quoting Jury Plan § 10(c)).4\n\n With those observations in place, we then \"construe[d]\n\nthe § 10(c) interests-of-justice exception as contemplating the\n\n[post-verdict] withholding of juror identities only upon a finding\n\nof exceptional circumstances peculiar to the case\" and thus \"h[e]ld\n\nthat, given the absence [in In re Globe's case] of particularized\n\nfindings reasonably justifying non-disclosure, the juror names and\n\naddresses must be made public.\" Id. at 97-98. Moreover, we\n\nexplained that \"we construe ['names' in § 1863(b)(7) of the Act]\n\nto encompass [jurors'] addresses\" because addresses might be\n\n\n\n 4The Act, § 1863(b)(7) provides:\n Among other things, such plan shall—\n (7) fix the time when the names drawn from the qualified\n jury wheel shall be disclosed to parties and to the\n public. If the plan permits these names to be made\n public, it may nevertheless permit the chief judge of\n the district court, or such other district court judge\n as the plan may provide, to keep these names confidential\n in any case where the interests of justice so require.\nAlthough this provision of the Act \"suggest[s] that a local [jury]\nplan might optionally decline not to permit juror names to be made\npublic at all,\" the District of Massachusetts's Jury Plan clearly\ndoes so permit. See In re Globe, 920 F.2d at 92.\n\n\n - 18 -\n\fnecessary to identify an individual with a common name. Id. at 93\n\nn.6.5 Thus, we concluded \"that addresses as well as names are\n\npresumptively available to the public under the [Jury Plan],\" and\n\nthus that juror \"[a]ddresses as well as names may be withheld by\n\ncourt order where the interests of justice so require, e.g., where\n\nsecurity considerations or matters of similar import are\n\ninvolved.\" Id.6\n\n Despite these seemingly definitive statements about the\n\nrequirement to disclose the requested information, Court-appointed\n\namicus argues that, with respect to the disclosure of juror\n\naddresses, In re Globe at most sets forth dicta that does not bind\n\nus here. To support this contention, Court-appointed amicus both\n\nasserts that In re Globe \"did not address the precise issue before\n\n\n\n\n 5\n The Jury Plan implements the Act, and therefore, the\nreference to \"names\" in § 10(c) of the Jury Plan, like the\nreference to \"names\" in the Act, is construed to include addresses.\nSee id. at 93 n.6.\n 6\n The Jury Plan was revised in 2015 to include a new summoning\nand qualification procedure. In that revision, the text of what\nwas § 10(c) in 1990, when In re Globe was decided, is now included\nverbatim in § 10(a). And it is that provision in the revised Jury\nPlan that is now in place. The parties do not argue that this\nchange in the location of the relevant text makes In re Globe's\nconstruction of the same operative language any less binding on us\nthan it would be if the Jury Plan that was before the court in In\nre Globe was still in place. And we see no reason to conclude\notherwise. Thus, this feature of our case supplies no reason for\nconcluding that In re Globe does not bind us.\n\n\n\n\n - 19 -\n\fthis panel\" and then characterizes that issue as being whether\n\nhometowns would suffice to identify jurors.\n\n The issue that we must decide, however, is not whether,\n\nin principle, addresses are necessary in order to identify jurors.\n\nThe issue is whether In re Globe, in construing the same language\n\nin the Jury Plan that is at issue here, holds that, presumptively,\n\nthey are. And, we conclude that In re Globe most certainly does\n\nso hold, as the review of that precedent that we have set forth\n\nabove reveals.\n\n The requirement that addresses must be disclosed so that\n\njurors may be identified is expressly part of In re Globe's\n\ninstructions to the district court in that case. Id. at 98. In\n\naddition, In re Globe explains its reasoning on that score as\n\nfollows: \"an address as well as the name is necessary to identify\n\nthe individual [in some cases]\" and \"therefore, . . . addresses as\n\nwell as names are presumptively available to the public under the\n\n[Jury Plan].\" Id. at 93 n.6 (emphasis added).\n\n Nor does In re Globe's use of the qualifier\n\n\"presumptively\" before the word \"available\" support the view put\n\nforth by Court-appointed amicus. See id. That qualifier,\n\nconsidered in context, merely reflects In re Globe's conclusion\n\nthat, in light of the principles that favor the disclosure of juror\n\nidentities, the obligation to disclose imposed by the language of\n\n§ 10(c) may be overcome with respect to the release of juror\n\n\n - 20 -\n\faddresses only if a district court makes the requisite\n\n\"particularized findings.\" See id. at 98.\n\n Thus, we reject Court-appointed amicus's contention that\n\nIn re Globe does not render a holding on whether juror addresses\n\nmay be withheld post-verdict. It clearly does, as it holds that,\n\nsave for such findings, the addresses may not be so withheld. See\n\nArcam Pharm. Corp. v. Faría, 513 F.3d 1, 3 (1st Cir. 2007) (\"We\n\nhave held that 'when a statement in a judicial decision is\n\nessential to the result reached in the case, it becomes part of\n\nthe court's holding.' The result, along with those portions of\n\nthe opinion necessary to the result, are binding, whereas dicta is\n\nnot.\" (quoting Rossiter v. Potter, 357 F.3d 26, 31 (1st Cir. 2004))\n\n(citation omitted)). And, we note, WBUR has represented that\n\naddresses are necessary to identify some jurors in this case.\n\n We next must consider whether In re Globe also holds\n\nthat the timing of the disclosure of the requested juror\n\ninformation may not be delayed until after sentencing. Here, too,\n\nwe conclude that In re Globe does so hold.\n\n In re Globe makes clear that it is deciding \"the right\n\nof access to juror names and addresses following a trial\" rather\n\nthan during a trial, id. at 95, and that it is holding that, after\n\na trial is complete, \"juror names and addresses must be made\n\npublic\" in \"the absence . . . of particularized findings reasonably\n\njustifying non-disclosure,\" id. at 98. The logic of In re Globe\n\n\n - 21 -\n\fthus requires that any delay in post-verdict disclosure be\n\njustified by the requisite \"particularized findings.\"\n\n After all, In re Globe sets no limit for what would\n\namount to an acceptable delay without such findings. Rather, it\n\nclearly states, \"[t]o justify impoundment after the trial has\n\nended, the court must find a significant threat to the judicial\n\nprocess itself.\" Id. at 91. Accordingly, we reject the contention\n\nthat In re Globe addresses only the issue of whether the permanent\n\nimpoundment of the relevant juror information is permissible.\n\n To be sure, In re Globe does, as Court-appointed amicus\n\nnotes, cite favorably to United States v. Doherty, 675 F. Supp.\n\n719 (D. Mass. 1987), in which the court delayed the release of\n\njuror identities until one week after trial. The Doherty court\n\nreasoned that such a delay would \"not injure the values to be\n\nfurthered by a searching press inquiry into the lives of the\n\njurors\" while at the same time affording jurors, among other\n\nthings, \"a short breathing space to reflect on the experience of\n\njury service and, after consultation with family and friends,\n\ndetermine what, if anything, the juror wishes to discuss with the\n\npress.\" Id. at 725.\n\n But, even assuming that In re Globe's citation of Doherty\n\nindicates that there is some such brief time period that could\n\nconstitute an acceptable delay, the three-month delay in this case\n\nfar outstrips such a period. And so, once again, we reject the\n\n\n - 22 -\n\fcontention of Court-appointed amicus that In re Globe sets forth\n\nno holding on the relevant point.\n\n C.\n\n We recognize, of course, that In re Globe was decided\n\ndecades ago and thus well before the first tweet was tweeted. As\n\nthe District Court emphasized, there is now a greater potential\n\nfor the public release of a juror's name, and, especially, a\n\njuror's address, to be more intrusive and concerning than would\n\nhave been the case in an era in which social media was unknown.\n\n But, these technological changes have by no means\n\ndiminished the need for accountability and transparency in our\n\nsystem of justice that In re Globe treats as relevant in construing\n\nthe critical provision of the Jury Plan. Nor is In re Globe\n\ndogmatic in reading that Jury Plan language to favor, on balance,\n\ndisclosure. Rather, it construes the Jury Plan's relevant text to\n\npermit nondisclosure in cases of individualized and adequately\n\ndemonstrated need.\n\n In any event, for present purposes, what matters is not\n\nhow, all things considered, one might now choose to strike the\n\nbalance that In re Globe holds that the Jury Plan's key provision\n\nhad struck. What matters is that In re Globe does render a holding\n\nabout that balance and that \"[i]n a multi-panel circuit, newly\n\nconstituted panels are, for the most part, bound by prior panel\n\n\n\n\n - 23 -\n\fdecisions closely on point.\" Williams v. Ashland Eng'g Co., 45\n\nF.3d 588, 592 (1st Cir. 1995).\n\n \"This tenet embodies what has come to be known as\n\nthe law of the circuit doctrine, which is a 'subset of stare\n\ndecisis' [and] one of the sturdiest 'building blocks on which the\n\nfederal judicial system rests.'\" United States v. Barbosa, 896\n\nF.3d 60, 74 (1st Cir. 2018) (quoting San Juan Cable LLC v. P.R.\n\nTel. Co., 612 F.3d 25, 33 (1st Cir. 2010)). And while there are\n\nexceptions to this doctrine that account for the circumstance when\n\nthere has been intervening precedent, id., those exceptions do not\n\napply here, nor does Court-appointed amicus or the District Court\n\noffer any basis for concluding otherwise.\n\n As a result, we are bound, under the law of the circuit\n\ndoctrine, to construe the operative language of the Jury Plan that\n\nis at issue in this case in the same manner that we construed the\n\nexact same language in In re Globe. And, for that reason, we\n\ncannot accept the District Court's legal conclusion that \"concerns\n\nfor juror privacy and a lack of precedent requiring the disclosure\n\nof jurors' home addresses\" provide a justification for a\n\ngeneralized ruling that \"a release of jurors' names, together with\n\ntheir home towns, at the appropriate time (after sentencing),\n\nstrikes the proper balance between the public right of access and\n\nthe juror right to privacy.\"\n\n\n\n\n - 24 -\n\f Moreover, we note that a district court's \"supervisory\n\npower does not license it to ignore an otherwise valid existing\n\njury plan or to bypass the mechanism provided by statute to alter\n\nsuch plan [because] '[t]o allow otherwise \"would confer on the\n\njudiciary discretionary power to disregard the considered\n\nlimitations of the law it is charged with enforcing.\"'\" In re\n\nUnited States, 426 F.3d 1, 9 (1st Cir. 2005) (quoting Bank of Nova\n\nScotia v. United States, 487 U.S. 250, 254 (1988)). Thus, in\n\nlight of In re Globe's holding about the meaning of the text of\n\nthe Jury Plan that is at issue and the law of the circuit doctrine,\n\nthe proper way for concerns about juror privacy to be addressed is\n\nthrough the process of amending the Jury Plan itself, insofar as\n\nany such amendment to the Jury Plan would be lawful -- a question\n\nthat we do not purport to address here.7\n\n\n\n 7 The District Court concluded its amended order by stating:\n\"The court would also suggest that any judge evaluating this same\nissue consider whether he or [she] would disclose his or her home\naddress when issuing orders or rulings.\" Here, we must rule as we\ndo in consequence of our prior holding in In re Globe and the law\nof the circuit doctrine. We do note, though, that, in construing\nthe Jury Plan to require the disclosure of juror names and\naddresses post-verdict absent the requisite \"particularized\nfindings,\" In re Globe emphasizes that jurors are not otherwise\nsufficiently identifiable to the press and public. See In re\nGlobe, 920 F.2d at 93 n.6, 97-98. That reasoning does not apply\nto judges. It also bears mentioning that it would be impossible\nfor judges to keep their addresses confidential during trials in\nwhich they presided if they were required to disclose them post-\nverdict, given that a judge is, by design, the quintessential\nrepeat player. No equivalent conundrum presents itself with\nrespect to jurors.\n\n\n - 25 -\n\f IV.\n\n The obligation of jury service is one of the most\n\nimportant that our government imposes on its citizens. It is,\n\ntherefore, important to ensure that the fulfillment of this\n\nobligation is not made so burdensome that it becomes more than a\n\ncitizen should have to bear. It is important to ensure as well,\n\nthough, that our system of justice remains accountable to the\n\nbroader public that it serves.\n\n The District of Massachusetts Jury Plan reconciles these\n\ncompeting concerns through the language now set forth in § 10(a).\n\nThis Court, nearly three decades ago, construed that exact same\n\nlanguage to require the post-verdict disclosure of juror names and\n\naddresses, absent a district court having made the requisite\n\n\"particularized findings\" to justify either nondisclosure or a\n\ndelay in disclosure. No precedent of this Court or the Supreme\n\nCourt has come down in the interim that in any way calls In re\n\nGlobe's holding about how that language must be construed into\n\nquestion. Thus, In re Globe dictates the outcome that we reach\n\nhere and thus precludes us from affirming the contrary one reached\n\nby the District Court.\n\n Nevertheless, it would be imprudent to prevent the\n\nDistrict Court from considering on remand what it concluded that\n\nit was not required to consider -- namely, whether this particular\n\ncase presents the kind of \"exceptional circumstances\" that In re\n\n\n - 26 -\n\fGlobe contemplates.8 Thus, we instruct the District Court on\n\nremand to follow the rule set forth in In re Globe and to unseal\n\nthe list of juror names and addresses as WBUR requested in its\n\nmotion, unless the District Court first makes the kind of\n\n\"particularized findings\" that could justify either the\n\nnondisclosure of that information or the disclosure of it only\n\nwith lawful conditions tailored to those findings. Accordingly,\n\nthe District Court's order is vacated and remanded for proceedings\n\nconsistent with this opinion.\n\n\n\n\n 8 WBUR asserted in its motion that, \"[u]nder the standards\nset forth by the First Circuit, no such findings can be made here.\"\nBut, rather than develop any argument as to this issue on appeal,\nWBUR simply states that \"this case [does not] present any of the\nkinds of factors that, in the unusual case, could present 'specific\nand convincing reasons' for withholding juror identities.\" Thus,\nthe argument that no such findings can be made is waived. See\nUnited States v. Zannino, 895 F.2d 1, 17 (1st Cir. 1990)\n(explaining that \"issues adverted to in a perfunctory manner,\nunaccompanied by some effort at developed argumentation, are\ndeemed waived\").\n\n\n - 27 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360259/", "author_raw": "and Katzmann, Judge"}]}
BARRON
SELYA
KATZMANN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583006/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, v. Glenn A. CHIN, Defendant. Trustees of Boston University, Owner of the Radio Station WBUR (WBUR), Intervenor, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-2048\n\n UNITED STATES OF AMERICA,\n\n v.\n\n GLENN A. CHIN,\n\n Defendant.\n\n\n TRUSTEES OF BOSTON UNIVERSITY,\n OWNER OF THE RADIO STATION WBUR (WBUR),\n\n Intervenor, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Richard G. Stearns, U.S. District Judge]\n\n\n Before\n\n Barron and Selya, Circuit Judges,\n and Katzmann, Judge.*\n\n\n Jeffrey J. Pyle, with whom Prince Lobel Tye LLP was on brief,\nfor appellant.\n Gregory Dubinsky, with whom Evan H. Stein and Holwell, Shuster\n& Goldberg LLP were on brief, for Court-appointed amicus curiae in\nsupport of affirmance.\n Nashwa Gewaily, New England First Amendment Coalition,\nSigmund D. Schutz, and Preti, Flaherty, Beliveau & Pachios, LLP,\non brief as amici curiae in support of appellant.\n\n * Of the United States Court of International Trade, sitting\nby designation.\n\fJanuary 18, 2019\n\f BARRON, Circuit Judge. This case concerns an appeal by\n\nthe Trustees of Boston University, as owners of WBUR, which is a\n\npublic radio station in Boston, Massachusetts. We will refer to\n\nthe appellant by the radio station's name, WBUR.\n\n The issue that we must decide arises from WBUR's motion\n\nin the fall of 2017 to intervene in a then still-ongoing criminal\n\ntrial in the United States District Court for the District of\n\nMassachusetts. In that motion, WBUR also requested that the\n\nDistrict Court unseal the names and addresses of the jurors in the\n\ncriminal case and provide that information to WBUR \"as soon as\n\npossible\" after the announcement of the jury's verdict.\n\n The District Court granted the motion to intervene but\n\notherwise denied in substantial part the motion to unseal the\n\nrequested information. We now vacate and remand.\n\n I.\n\n WBUR filed this motion in the criminal case against New\n\nEngland Compounding Center (\"NECC\") supervisory pharmacist Glenn\n\nChin. He had been charged with committing mail fraud and violating\n\nthe Racketeer Influenced and Corrupt Organizations Act (\"RICO\"),\n\n18 U.S.C. §§ 1961–1968, based on, among other things, twenty-five\n\npredicate acts of second-degree murder, in connection with a\n\nnationwide distribution of contaminated medications that caused a\n\nfatal outbreak of fungal meningitis.\n\n\n\n\n - 3 -\n\f Chin's trial began in federal district court in Boston\n\non September 19, 2017. It ended a little more than a month later,\n\non October 25, 2017, when the jury found Chin guilty of mail fraud\n\nand lesser predicate offenses under RICO but not guilty of the\n\ntwenty-five predicate acts of second-degree murder.\n\n A week before the trial ended, on October 18, 2017, WBUR\n\nfiled its motion both to intervene in the criminal case and to\n\nobtain \"as soon as possible after the verdict is announced\" the\n\nnames and addresses of the then-deliberating jurors. On October\n\n27, 2017 -- just two days after the jury had returned its verdict\n\n-- the District Court issued an order allowing intervention in the\n\ncriminal case by WBUR but denying, without prejudice, its motion\n\nregarding the disclosure of juror names and addresses.\n\n The District Court stated in that order that it would\n\n\"release\" juror names and hometowns, but not addresses, and that\n\nit would do so only after Chin's sentencing, which was scheduled\n\nfor January 30, 2018.1 The District Court did note in its order,\n\n\n 1 One of Chin's co-defendants was Barry Cadden, the owner of\nNECC, whose case had gone to trial in federal district court in\nBoston six months earlier. At Cadden's trial, the jury returned\na verdict sheet suggesting that the jurors had not voted\nunanimously to acquit Cadden of second-degree murder, even though\nthe not-guilty verdict required unanimity. WBUR filed a motion\nfor immediate access to juror names and addresses, and the District\nCourt ruled that it would release a list of each juror's name and\nhometown, though not each juror's address, only after sentencing,\nwhich was to occur three months later. WBUR, though unable to\nidentify every juror even after receiving the jurors' names and\nhometowns, ultimately interviewed two jurors from the Cadden trial\n\n - 4 -\n\fhowever, that it would \"consider an earlier release of the juror\n\nlist upon submission by [WBUR] of an appropriate protective order\n\nthat is . . . crafted to insure against any unnecessary\n\ndissemination of the jurors' personal identification in the news\n\nmedia or over the internet (without the juror's express assent).\"\n\n The District Court based this possible condition on\n\nrelease on a protective order requirement that Judge Young had\n\nimposed one week earlier in a similar ruling regarding WBUR's\n\nrequest for disclosure of juror names and addresses in another\n\ncase in the District of Massachusetts: United States v. Wright,\n\nNo. 15-cr-10153-WGY (D. Mass. Oct. 20, 2017), ECF No. 357. Judge\n\nYoung withdrew the protective order requirement in Wright on\n\nNovember 3, 2017, however, after WBUR challenged that requirement\n\non the grounds that it would be impractical and perhaps\n\nunconstitutional.\n\n A little less than two weeks later, on November 16, 2017,\n\nWBUR appealed from the District Court's order denying its request\n\nin Chin. The next day, the District Court issued an \"Amended Order\n\non Motion of [WBUR] to Unseal Juror Names and Addresses,\" which,\n\njust as Judge Young had done in Wright, withdrew the protective\n\norder requirement. In the amended order, the District Court\n\nreiterated that it would \"release\" a list of the Chin jurors' names\n\n\nand aired a report stating that those two jurors did not understand\nthat not-guilty verdicts required unanimity.\n\n\n - 5 -\n\fand hometowns, but not addresses, and that it would do so only\n\nafter sentencing.\n\n In accord with the initial order, on January 31, 2018,\n\nthe day after the sentencing proceedings in Chin's case ended, the\n\nDistrict Court issued an unsealed order containing a list of the\n\njurors' names and their hometowns, but not their addresses.\n\nBecause neither the government nor Chin opposes WBUR's motion on\n\nappeal, we ordered the appointment of amicus counsel (\"Court-\n\nappointed amicus\") to represent the position reflected in the\n\nDistrict Court's order denying WBUR's motion in substantial part,\n\na task that the amicus has ably performed.2\n\n II.\n\n We begin by addressing our jurisdiction to hear this\n\nappeal, which turns out to be a task that is not without its\n\ncomplexities. The most prominent jurisdictional question that we\n\nconfront concerns the possibility that this appeal has been mooted\n\nby the District Court's granting of partial relief to WBUR and the\n\nfact that Chin's sentencing has already occurred. But, before we\n\nget to that jurisdictional question, we address two others, the\n\nfirst of which relates to the appellant's status as an intervenor.\n\n We stated in In re Globe Newspaper Co., 920 F.2d 88, 90\n\n(1st Cir. 1990), that \"the right of a non-party to intervene in a\n\n\n 2 We also acknowledge the helpful amicus brief filed by the\nNew England First Amendment Coalition, et al.\n\n\n - 6 -\n\fcriminal proceeding is doubtful.\" But, we nonetheless concluded\n\n-- even without finding that the appellant there could intervene\n\n-- that we had jurisdiction over the appeal under the All Writs\n\nAct, 28 U.S.C. § 1651. See In re Providence Journal Co., Inc.,\n\n293 F.3d 1, 9 (1st Cir. 2002) (explaining that the All Writs Act\n\ngives \"[a] federal court of appeals . . . the power to treat an\n\nattempted appeal from an unappealable (or possibly unappealable)\n\norder as a petition for a writ of mandamus\" (quoting United States\n\nv. Horn, 29 F.3d 754, 769 (1st Cir. 1994))).\n\n Here, however, the District Court did grant WBUR's\n\nmotion to intervene. And, because that \"legal decision\" to grant\n\nWBUR's motion remained \"unchallenged in [this] appeal despite the\n\nexistence of ample opportunity to [challenge it],\" it is now \"law\n\nof the case for future stages of the same litigation\" and therefore\n\n\"should continue to govern the same issues.\" United States v.\n\nMatthews, 643 F.3d 9, 12 (1st Cir. 2011) (citations omitted).\n\nThus, as an intervenor, WBUR may appeal the District Court's order\n\ndenying its request for the disclosure of juror names and\n\naddresses, which WBUR filed before sentencing and thus before the\n\nmatter had concluded -- assuming, that is, the appeal is not moot.\n\nSee United States v. Blagojevich, 612 F.3d 558, 560 (7th Cir. 2010)\n\n\n\n\n - 7 -\n\f(applying the collateral order doctrine in finding jurisdiction\n\nover an appeal by an intervenor in a similar case).3\n\n The next jurisdictional wrinkle that we must iron out\n\nconcerns the timing of the appeal relative to the issuance of the\n\nDistrict Court's amended order in this case. Neither WBUR nor\n\nCourt-appointed amicus makes anything of the fact that the District\n\nCourt issued its amended order the day after WBUR filed its notice\n\nof appeal. But, the general rule is that \"[t]he filing of a notice\n\nof appeal is an event of jurisdictional significance -- it confers\n\njurisdiction on the court of appeals and divests the district court\n\nof its control over those aspects of the case involved in the\n\nappeal.\" Griggs v. Provident Consumer Discount Co., 459 U.S. 56,\n\n58 (1982).\n\n Nevertheless, \"this circuit and others have recognized\n\nlimited exceptions to this judge-made rule.\" United States v.\n\nTorres-Oliveras, 583 F.3d 37, 44 (1st Cir. 2009) (citing 16A\n\nCharles A. Wright, et al., Federal Practice and Procedure § 3949.1\n\n(4th ed. 2009); United States v. Ortega, 859 F.2d 327, 334–35 (5th\n\nCir. 1988)). And, arguably, the District Court's amended order\n\nhere falls within one of the recognized exceptions because it does\n\n\n\n 3 Nor do we think that the fact that the motion to unseal the\njuror names and addresses was denied \"without prejudice\" is of\njurisdictional significance, under the collateral order doctrine,\ngiven that the request was for the release of the jurors'\nidentifying information \"as soon as possible\" post-verdict.\n\n\n - 8 -\n\fnot \"alter the substance of the decision\" to release juror names\n\nand hometowns after sentencing. See Wright, et al. § 3949.1.\n\n In any event, we will treat the District Court's November\n\n17, 2017 order as though it were an indicative ruling regarding\n\nthe withdrawal of the protective order requirement. Cf. United\n\nStates v. Maldonado-Rios, 790 F.3d 62, 65 (1st Cir. 2015) (per\n\ncuriam) (treating a sentencing court's grant of a motion filed\n\nduring the pendency of appeal as an indicative ruling under Federal\n\nRule of Appellate Procedure 12.1). And, even if we consider on\n\nappeal only the District Court's October 27, 2017 order, our\n\nanalysis of the merits is not affected. See Torres-Oliveras, 583\n\nF.3d at 44.\n\n We come, then, to the main potential jurisdictional\n\nobstacle to our reaching the merits of this appeal. Court-\n\nappointed amicus contends that the appeal is moot in its entirety,\n\nand thus no longer a live case or controversy requiring resolution,\n\nbecause the District Court released the names and hometowns of the\n\nChin jurors on January 31, 2018.\n\n \"The burden of establishing mootness rests with the\n\nparty invoking the doctrine.\" ACLU of Mass. v. U.S. Conference of\n\nCatholic Bishops, 705 F.3d 44, 52 (1st Cir. 2013). Because no\n\nfactual findings bear on the matter, we decide the legal issue de\n\nnovo. See id.\n\n\n\n\n - 9 -\n\f As to WBUR's appeal of the denial of its request for the\n\njurors' addresses, Court-appointed amicus argues that the access\n\nto names and hometowns that the District Court provided is\n\nsufficient for WBUR to identify the jurors and thus renders any\n\nopinion ordering the release of juror addresses \"merely advisory.\"\n\nSee Mangual v. Rotger-Sabat, 317 F.3d 45, 60 (1st Cir. 2003) (\"If\n\nevents have transpired to render a court opinion merely advisory,\n\nArticle III considerations require dismissal of the case.\").\n\nAccordingly, Court-appointed amicus contends that this aspect of\n\nWBUR's appeal is moot.\n\n But, the District Court has not unsealed some of the\n\ninformation that WBUR sought in its motion -- namely, the addresses\n\nof the jurors. And, it is undisputed that WBUR has not been able\n\nto contact all twelve jurors in the Chin trial, even though the\n\nDistrict Court provided WBUR with access to their names and\n\nhometowns. Consequently, the unsealing of the requested\n\naddresses, even at this point, would provide \"effectual relief\" to\n\nWBUR with respect to its appeal of the District Court's order\n\ndenying its motion requesting the information that thus far has\n\nbeen withheld. ACLU of Mass., 705 F.3d at 52. This aspect of the\n\nappeal, therefore, is not moot.\n\n The mootness question is not quite so easily resolved\n\nwith respect to WBUR's appeal of the District Court's denial of\n\nthe request to release the jurors' identifying information post-\n\n\n - 10 -\n\fverdict, rather than post-sentencing. The sentencing occurred\n\nnearly a year ago. There is no way to turn back the clock. Thus,\n\nthere is some force to the suggestion of mootness by Court-\n\nappointed amicus as to the aspect of WBUR's appeal that concerns\n\nthe timing of the release of the requested information.\n\n Nevertheless, in contending that this aspect of its\n\nappeal also is not moot, WBUR relies on an exception to the\n\nmootness doctrine that exists for a controversy that is \"capable\n\nof repetition, yet evading review.\" Kingdomware Technologies,\n\nInc. v. United States, 136 S. Ct. 1969, 1976 (2016) (quoting\n\nSpencer v. Kemna, 523 U.S. 1, 17 (1998)). In particular, WBUR\n\nargues that, although sentencing has already occurred, WBUR likely\n\n\"will again be subjected to the alleged illegality\" because that\n\n\"alleged illegality\" is capable of repetition and would continue\n\nto evade review. Murphy v. Hunt, 455 U.S. 478, 483 (1982) (per\n\ncuriam); ACLU of Mass., 705 F.3d at 57 (emphasis omitted) (quoting\n\nCity of Los Angeles v. Lyons, 461 U.S. 95, 109 (1983)).\n\n To qualify for this exception to the mootness doctrine,\n\nWBUR bears the burden of showing that \"(1) the challenged action\n\nwas in its duration too short to be fully litigated prior to its\n\ncessation or expiration, and (2) there was a reasonable expectation\n\nthat the same complaining party would be subjected to the same\n\naction again.\" Gulf of Maine Fisherman's All. v. Daley, 292 F.3d\n\n84, 89 (1st Cir. 2002) (quoting Weinstein v. Bradford, 423 U.S.\n\n\n - 11 -\n\f147, 149 (1975)). We conclude that WBUR has made the required\n\nshowing.\n\n About three months elapsed between the verdict and\n\nsentencing in Chin. That period of time is \"too short\" to complete\n\nlitigation, given that the appeal process often takes longer than\n\na few months. Id. But, that fact should not preclude WBUR's\n\nchallenge to a delay in the disclosure of the requested information\n\nthat, though shorter than the time frame for most litigation, was\n\nstill significant enough to affect WBUR's reporting. WBUR has\n\nalso shown that it frequently requests that the District of\n\nMassachusetts unseal jury lists as soon as possible following a\n\nverdict in order to obtain information that would enable it to\n\nreport on cases in the District. And, WBUR has shown that, in a\n\nnumber of instances, judges in the District have waited until after\n\nsentencing to release the requested juror information.\n\n Therefore, we conclude that WBUR has met its burden under\n\nthe exception to the mootness doctrine on which it relies in asking\n\nus to consider its appeal with respect to the timing issue. And\n\nso, satisfied that WBUR's appeal is not moot, and having disposed\n\nof the other possible jurisdictional issues that might have cut\n\nshort our consideration of this appeal, we now turn to the merits\n\nof the case.\n\n\n\n\n - 12 -\n\f III.\n\n In considering the merits, we direct our attention\n\nchiefly to one of our prior precedents: In re Globe Newspaper Co.,\n\n920 F.2d 88 (1st Cir. 1990). We do so because WBUR's appeal is\n\npremised in part on a contention about what that precedent holds.\n\n WBUR stated in its motion requesting the disclosure of\n\nthe juror information -- just as it now asserts on appeal -- that,\n\n\"under controlling precedent, the identities of the jurors 'must\n\nbe made public' after a verdict is rendered, unless the Court makes\n\n'particularized findings reasonably justifying nondisclosure.'\"\n\nThe assertedly \"controlling precedent\" that WBUR identifies is In\n\nre Globe. Because the interpretation of that precedent presents\n\na purely legal question, our review of whether In re Globe controls\n\nthe outcome here -- as WBUR contends that it does -- is de novo.\n\nSee United States v. Mayendía-Blanco, 905 F.3d 26, 34 (1st Cir.\n\n2018). If we conclude that In re Globe does control here, then we\n\nmust consider Court-appointed amicus's alternative argument that\n\nwe should revisit that holding in light of changes in technology\n\nover the past thirty years since In re Globe was decided.\n\n A.\n\n WBUR is right that, insofar as In re Globe requires a\n\ndistrict court in a particular case to disclose juror names and\n\naddresses post-trial, but pre-sentencing, In re Globe allows for\n\nan exception to that requirement only if the district court makes\n\n\n - 13 -\n\f\"particularized findings reasonably justifying non-disclosure.\"\n\nSee In re Globe, 920 F.2d at 98. WBUR is also right that such\n\n\"finding[s] of exceptional circumstances [must be] peculiar to the\n\ncase.\" Id. at 97. Moreover, In re Globe provides examples of\n\n\"[s]uch circumstances,\" and they include \"a credible threat of\n\njury tampering, a risk of personal harm to individual jurors, and\n\nother evils affecting the administration of justice.\" Id.\n\n Here, the District Court did not make any\n\n\"particularized findings\" regarding such exceptional circumstances\n\nthat were peculiar to this case. Nor does Court-appointed amicus\n\nsuggest that the District Court did so when denying in substantial\n\npart WBUR's motion to release the requested information. Instead,\n\nthe District Court in its amended order recounted the jury's\n\nhistorical role to explain, in part, its decision not to release\n\nany of the requested information to WBUR until after sentencing\n\nand not to release the jurors' addresses even then. The District\n\nCourt also placed great emphasis in its initial order on the\n\ntechnological realities that supply the present context for WBUR's\n\nrequest for juror information. As the District Court put it in\n\nits initial order:\n\n While the court respects the role of the media\n in promoting \"the public's long-term interest\n in maintaining an open judicial process,\" [In\n re Globe, 920 F.2d at 91], it will not release\n jurors' home addresses. . . . [T]his is . .\n . a necessary precaution in an age in which\n traditional boundaries of personal privacy are\n\n\n - 14 -\n\f under assault. While jurors serve in an\n important public capacity, it is a role thrust\n upon them as a duty of citizenship. The extent\n to which such service might compromise a\n juror's personal life once that service is\n concluded should be a matter in which the\n juror has the maximum say constitutionally\n possible.\n\n Thus, the first question before us is whether In re Globe\n\ndoes indeed require, as WBUR contends, the requested disclosure of\n\njuror addresses (as opposed to merely hometowns) post-trial,\n\nabsent the requisite \"particularized findings\" described above.\n\nThe second question that we must consider is whether In re Globe\n\nrequires the requested disclosure to occur \"as soon as possible\"\n\npost-verdict, absent \"particularized findings\" to justify a delay\n\nin the release of juror identities until after sentencing, which\n\nhere occurred three months after trial. For, if In re Globe does\n\nimpose either disclosure requirement in the absence of such\n\nfindings, then the order partially denying WBUR's motion did not\n\ncomply with that prior precedent. We thus now review what we said\n\nin In re Globe.\n\n B.\n\n The case arose out of the Globe Newspaper Company's\n\nrequest for access to the names and addresses of the jurors who\n\nhad participated in a then-just-completed criminal trial in a\n\nfederal district court in Boston. Id. at 90. The underlying\n\n\n\n\n - 15 -\n\fcriminal case concerned an alleged conspiracy to conceal illegal\n\ndrug profits involving three defendants. Id.\n\n The jury there had found two defendants guilty and one\n\nnot guilty. Id. On the same day that the verdict was rendered\n\nand the jury was discharged, \"Globe reporters sought access to the\n\ncourt's record of the juror names and addresses.\" Id.\n\n When the district court in that case refused to grant\n\nthe reporters the requested access, the newspaper company moved to\n\nintervene and to request access to the court's record of the juror\n\nnames and addresses. Id. That motion was denied, and the ensuing\n\nappeal by the newspaper company led to our decision in In re Globe.\n\n In reversing the ruling below, we recognized the\n\ncompeting interests, constitutional and otherwise, implicated by\n\nthe newspaper company's request for access to the names and\n\naddresses of jurors -– \"the press's First Amendment right of access\n\nto criminal trials[,] the defendant's Sixth Amendment right to a\n\nfair trial[, and] the jurors['] interest in having their privacy\n\nprotected.\" Id. at 93 (citations omitted). We also noted that\n\n\"[k]nowledge of juror identities allows the public to verify the\n\nimpartiality of key participants in the administration of justice,\n\nand thereby ensures fairness, the appearance of fairness and public\n\nconfidence in that system.\" Id. at 94. And, too, we noted, the\n\npublic disclosure of juror identities serves many of the same\n\n\n\n\n - 16 -\n\fpurposes of \"open justice\" that are protected by the First\n\nAmendment to the United States Constitution. Id.\n\n We chose, however, not to rest our decision reversing\n\nthe ruling below on a constitutional holding rooted in the First\n\nAmendment. Instead, we based our decision on a construction of\n\nwhat was then § 10(c) of the District of Massachusetts Plan for\n\nRandom Selection of Jurors (\"Jury Plan\"), which the District had\n\nadopted pursuant to the Jury Selection and Service Act of 1968, 28\n\nU.S.C. §§ 1861-1874 (1982) (\"the Act\").\n\n In construing those texts, we noted at the outset that,\n\nalthough the language of the Act and of the Jury Plan make no\n\nspecific distinction between pre-verdict and post-verdict\n\ndisclosure of juror identities, \"[t]he court's right to [keep names\n\nand addresses of jurors confidential] during the trial [was] not\n\nan issue in [In re Globe].\" In re Globe, 920 F.2d at 90. We\n\nobserved as well that \"[n]o doubt stronger reasons to withhold\n\njuror names and addresses will often exist during trial than after\n\na verdict is rendered\" and stated that \"[t]o justify impoundment\n\nafter the trial has ended, the court must find a significant threat\n\nto the judicial process itself.\" Id. at 91 (emphasis in original).\n\n Against that background understanding, we then construed\n\nthe Jury Plan in light of the newspaper company's request for post-\n\nverdict disclosure of juror identities. In doing so, we noted\n\nthat the Jury Plan's relevant provision barred the disclosure of\n\n\n - 17 -\n\fjuror names until the jurors \"have appeared, or failed to appear,\n\nin response to the summons.\" In re Globe, 920 F.2d at 92 & n.4\n\n(quoting Jury Plan § 10(c)). We noted as well that this same\n\nprovision then went on to state that \"[a]ny judge of this Court\n\nmay order that the names of jurors remain confidential even\n\nthereafter if the interests of justice so require.\" Id. (emphasis\n\nomitted) (quoting Jury Plan § 10(c)).4\n\n With those observations in place, we then \"construe[d]\n\nthe § 10(c) interests-of-justice exception as contemplating the\n\n[post-verdict] withholding of juror identities only upon a finding\n\nof exceptional circumstances peculiar to the case\" and thus \"h[e]ld\n\nthat, given the absence [in In re Globe's case] of particularized\n\nfindings reasonably justifying non-disclosure, the juror names and\n\naddresses must be made public.\" Id. at 97-98. Moreover, we\n\nexplained that \"we construe ['names' in § 1863(b)(7) of the Act]\n\nto encompass [jurors'] addresses\" because addresses might be\n\n\n\n 4The Act, § 1863(b)(7) provides:\n Among other things, such plan shall—\n (7) fix the time when the names drawn from the qualified\n jury wheel shall be disclosed to parties and to the\n public. If the plan permits these names to be made\n public, it may nevertheless permit the chief judge of\n the district court, or such other district court judge\n as the plan may provide, to keep these names confidential\n in any case where the interests of justice so require.\nAlthough this provision of the Act \"suggest[s] that a local [jury]\nplan might optionally decline not to permit juror names to be made\npublic at all,\" the District of Massachusetts's Jury Plan clearly\ndoes so permit. See In re Globe, 920 F.2d at 92.\n\n\n - 18 -\n\fnecessary to identify an individual with a common name. Id. at 93\n\nn.6.5 Thus, we concluded \"that addresses as well as names are\n\npresumptively available to the public under the [Jury Plan],\" and\n\nthus that juror \"[a]ddresses as well as names may be withheld by\n\ncourt order where the interests of justice so require, e.g., where\n\nsecurity considerations or matters of similar import are\n\ninvolved.\" Id.6\n\n Despite these seemingly definitive statements about the\n\nrequirement to disclose the requested information, Court-appointed\n\namicus argues that, with respect to the disclosure of juror\n\naddresses, In re Globe at most sets forth dicta that does not bind\n\nus here. To support this contention, Court-appointed amicus both\n\nasserts that In re Globe \"did not address the precise issue before\n\n\n\n\n 5\n The Jury Plan implements the Act, and therefore, the\nreference to \"names\" in § 10(c) of the Jury Plan, like the\nreference to \"names\" in the Act, is construed to include addresses.\nSee id. at 93 n.6.\n 6\n The Jury Plan was revised in 2015 to include a new summoning\nand qualification procedure. In that revision, the text of what\nwas § 10(c) in 1990, when In re Globe was decided, is now included\nverbatim in § 10(a). And it is that provision in the revised Jury\nPlan that is now in place. The parties do not argue that this\nchange in the location of the relevant text makes In re Globe's\nconstruction of the same operative language any less binding on us\nthan it would be if the Jury Plan that was before the court in In\nre Globe was still in place. And we see no reason to conclude\notherwise. Thus, this feature of our case supplies no reason for\nconcluding that In re Globe does not bind us.\n\n\n\n\n - 19 -\n\fthis panel\" and then characterizes that issue as being whether\n\nhometowns would suffice to identify jurors.\n\n The issue that we must decide, however, is not whether,\n\nin principle, addresses are necessary in order to identify jurors.\n\nThe issue is whether In re Globe, in construing the same language\n\nin the Jury Plan that is at issue here, holds that, presumptively,\n\nthey are. And, we conclude that In re Globe most certainly does\n\nso hold, as the review of that precedent that we have set forth\n\nabove reveals.\n\n The requirement that addresses must be disclosed so that\n\njurors may be identified is expressly part of In re Globe's\n\ninstructions to the district court in that case. Id. at 98. In\n\naddition, In re Globe explains its reasoning on that score as\n\nfollows: \"an address as well as the name is necessary to identify\n\nthe individual [in some cases]\" and \"therefore, . . . addresses as\n\nwell as names are presumptively available to the public under the\n\n[Jury Plan].\" Id. at 93 n.6 (emphasis added).\n\n Nor does In re Globe's use of the qualifier\n\n\"presumptively\" before the word \"available\" support the view put\n\nforth by Court-appointed amicus. See id. That qualifier,\n\nconsidered in context, merely reflects In re Globe's conclusion\n\nthat, in light of the principles that favor the disclosure of juror\n\nidentities, the obligation to disclose imposed by the language of\n\n§ 10(c) may be overcome with respect to the release of juror\n\n\n - 20 -\n\faddresses only if a district court makes the requisite\n\n\"particularized findings.\" See id. at 98.\n\n Thus, we reject Court-appointed amicus's contention that\n\nIn re Globe does not render a holding on whether juror addresses\n\nmay be withheld post-verdict. It clearly does, as it holds that,\n\nsave for such findings, the addresses may not be so withheld. See\n\nArcam Pharm. Corp. v. Faría, 513 F.3d 1, 3 (1st Cir. 2007) (\"We\n\nhave held that 'when a statement in a judicial decision is\n\nessential to the result reached in the case, it becomes part of\n\nthe court's holding.' The result, along with those portions of\n\nthe opinion necessary to the result, are binding, whereas dicta is\n\nnot.\" (quoting Rossiter v. Potter, 357 F.3d 26, 31 (1st Cir. 2004))\n\n(citation omitted)). And, we note, WBUR has represented that\n\naddresses are necessary to identify some jurors in this case.\n\n We next must consider whether In re Globe also holds\n\nthat the timing of the disclosure of the requested juror\n\ninformation may not be delayed until after sentencing. Here, too,\n\nwe conclude that In re Globe does so hold.\n\n In re Globe makes clear that it is deciding \"the right\n\nof access to juror names and addresses following a trial\" rather\n\nthan during a trial, id. at 95, and that it is holding that, after\n\na trial is complete, \"juror names and addresses must be made\n\npublic\" in \"the absence . . . of particularized findings reasonably\n\njustifying non-disclosure,\" id. at 98. The logic of In re Globe\n\n\n - 21 -\n\fthus requires that any delay in post-verdict disclosure be\n\njustified by the requisite \"particularized findings.\"\n\n After all, In re Globe sets no limit for what would\n\namount to an acceptable delay without such findings. Rather, it\n\nclearly states, \"[t]o justify impoundment after the trial has\n\nended, the court must find a significant threat to the judicial\n\nprocess itself.\" Id. at 91. Accordingly, we reject the contention\n\nthat In re Globe addresses only the issue of whether the permanent\n\nimpoundment of the relevant juror information is permissible.\n\n To be sure, In re Globe does, as Court-appointed amicus\n\nnotes, cite favorably to United States v. Doherty, 675 F. Supp.\n\n719 (D. Mass. 1987), in which the court delayed the release of\n\njuror identities until one week after trial. The Doherty court\n\nreasoned that such a delay would \"not injure the values to be\n\nfurthered by a searching press inquiry into the lives of the\n\njurors\" while at the same time affording jurors, among other\n\nthings, \"a short breathing space to reflect on the experience of\n\njury service and, after consultation with family and friends,\n\ndetermine what, if anything, the juror wishes to discuss with the\n\npress.\" Id. at 725.\n\n But, even assuming that In re Globe's citation of Doherty\n\nindicates that there is some such brief time period that could\n\nconstitute an acceptable delay, the three-month delay in this case\n\nfar outstrips such a period. And so, once again, we reject the\n\n\n - 22 -\n\fcontention of Court-appointed amicus that In re Globe sets forth\n\nno holding on the relevant point.\n\n C.\n\n We recognize, of course, that In re Globe was decided\n\ndecades ago and thus well before the first tweet was tweeted. As\n\nthe District Court emphasized, there is now a greater potential\n\nfor the public release of a juror's name, and, especially, a\n\njuror's address, to be more intrusive and concerning than would\n\nhave been the case in an era in which social media was unknown.\n\n But, these technological changes have by no means\n\ndiminished the need for accountability and transparency in our\n\nsystem of justice that In re Globe treats as relevant in construing\n\nthe critical provision of the Jury Plan. Nor is In re Globe\n\ndogmatic in reading that Jury Plan language to favor, on balance,\n\ndisclosure. Rather, it construes the Jury Plan's relevant text to\n\npermit nondisclosure in cases of individualized and adequately\n\ndemonstrated need.\n\n In any event, for present purposes, what matters is not\n\nhow, all things considered, one might now choose to strike the\n\nbalance that In re Globe holds that the Jury Plan's key provision\n\nhad struck. What matters is that In re Globe does render a holding\n\nabout that balance and that \"[i]n a multi-panel circuit, newly\n\nconstituted panels are, for the most part, bound by prior panel\n\n\n\n\n - 23 -\n\fdecisions closely on point.\" Williams v. Ashland Eng'g Co., 45\n\nF.3d 588, 592 (1st Cir. 1995).\n\n \"This tenet embodies what has come to be known as\n\nthe law of the circuit doctrine, which is a 'subset of stare\n\ndecisis' [and] one of the sturdiest 'building blocks on which the\n\nfederal judicial system rests.'\" United States v. Barbosa, 896\n\nF.3d 60, 74 (1st Cir. 2018) (quoting San Juan Cable LLC v. P.R.\n\nTel. Co., 612 F.3d 25, 33 (1st Cir. 2010)). And while there are\n\nexceptions to this doctrine that account for the circumstance when\n\nthere has been intervening precedent, id., those exceptions do not\n\napply here, nor does Court-appointed amicus or the District Court\n\noffer any basis for concluding otherwise.\n\n As a result, we are bound, under the law of the circuit\n\ndoctrine, to construe the operative language of the Jury Plan that\n\nis at issue in this case in the same manner that we construed the\n\nexact same language in In re Globe. And, for that reason, we\n\ncannot accept the District Court's legal conclusion that \"concerns\n\nfor juror privacy and a lack of precedent requiring the disclosure\n\nof jurors' home addresses\" provide a justification for a\n\ngeneralized ruling that \"a release of jurors' names, together with\n\ntheir home towns, at the appropriate time (after sentencing),\n\nstrikes the proper balance between the public right of access and\n\nthe juror right to privacy.\"\n\n\n\n\n - 24 -\n\f Moreover, we note that a district court's \"supervisory\n\npower does not license it to ignore an otherwise valid existing\n\njury plan or to bypass the mechanism provided by statute to alter\n\nsuch plan [because] '[t]o allow otherwise \"would confer on the\n\njudiciary discretionary power to disregard the considered\n\nlimitations of the law it is charged with enforcing.\"'\" In re\n\nUnited States, 426 F.3d 1, 9 (1st Cir. 2005) (quoting Bank of Nova\n\nScotia v. United States, 487 U.S. 250, 254 (1988)). Thus, in\n\nlight of In re Globe's holding about the meaning of the text of\n\nthe Jury Plan that is at issue and the law of the circuit doctrine,\n\nthe proper way for concerns about juror privacy to be addressed is\n\nthrough the process of amending the Jury Plan itself, insofar as\n\nany such amendment to the Jury Plan would be lawful -- a question\n\nthat we do not purport to address here.7\n\n\n\n 7 The District Court concluded its amended order by stating:\n\"The court would also suggest that any judge evaluating this same\nissue consider whether he or [she] would disclose his or her home\naddress when issuing orders or rulings.\" Here, we must rule as we\ndo in consequence of our prior holding in In re Globe and the law\nof the circuit doctrine. We do note, though, that, in construing\nthe Jury Plan to require the disclosure of juror names and\naddresses post-verdict absent the requisite \"particularized\nfindings,\" In re Globe emphasizes that jurors are not otherwise\nsufficiently identifiable to the press and public. See In re\nGlobe, 920 F.2d at 93 n.6, 97-98. That reasoning does not apply\nto judges. It also bears mentioning that it would be impossible\nfor judges to keep their addresses confidential during trials in\nwhich they presided if they were required to disclose them post-\nverdict, given that a judge is, by design, the quintessential\nrepeat player. No equivalent conundrum presents itself with\nrespect to jurors.\n\n\n - 25 -\n\f IV.\n\n The obligation of jury service is one of the most\n\nimportant that our government imposes on its citizens. It is,\n\ntherefore, important to ensure that the fulfillment of this\n\nobligation is not made so burdensome that it becomes more than a\n\ncitizen should have to bear. It is important to ensure as well,\n\nthough, that our system of justice remains accountable to the\n\nbroader public that it serves.\n\n The District of Massachusetts Jury Plan reconciles these\n\ncompeting concerns through the language now set forth in § 10(a).\n\nThis Court, nearly three decades ago, construed that exact same\n\nlanguage to require the post-verdict disclosure of juror names and\n\naddresses, absent a district court having made the requisite\n\n\"particularized findings\" to justify either nondisclosure or a\n\ndelay in disclosure. No precedent of this Court or the Supreme\n\nCourt has come down in the interim that in any way calls In re\n\nGlobe's holding about how that language must be construed into\n\nquestion. Thus, In re Globe dictates the outcome that we reach\n\nhere and thus precludes us from affirming the contrary one reached\n\nby the District Court.\n\n Nevertheless, it would be imprudent to prevent the\n\nDistrict Court from considering on remand what it concluded that\n\nit was not required to consider -- namely, whether this particular\n\ncase presents the kind of \"exceptional circumstances\" that In re\n\n\n - 26 -\n\fGlobe contemplates.8 Thus, we instruct the District Court on\n\nremand to follow the rule set forth in In re Globe and to unseal\n\nthe list of juror names and addresses as WBUR requested in its\n\nmotion, unless the District Court first makes the kind of\n\n\"particularized findings\" that could justify either the\n\nnondisclosure of that information or the disclosure of it only\n\nwith lawful conditions tailored to those findings. Accordingly,\n\nthe District Court's order is vacated and remanded for proceedings\n\nconsistent with this opinion.\n\n\n\n\n 8 WBUR asserted in its motion that, \"[u]nder the standards\nset forth by the First Circuit, no such findings can be made here.\"\nBut, rather than develop any argument as to this issue on appeal,\nWBUR simply states that \"this case [does not] present any of the\nkinds of factors that, in the unusual case, could present 'specific\nand convincing reasons' for withholding juror identities.\" Thus,\nthe argument that no such findings can be made is waived. See\nUnited States v. Zannino, 895 F.2d 1, 17 (1st Cir. 1990)\n(explaining that \"issues adverted to in a perfunctory manner,\nunaccompanied by some effort at developed argumentation, are\ndeemed waived\").\n\n\n - 27 -\n[END_CASE]", "role": "user" } ]
4,583,440
Jose Alberto MEDINA, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.
Medina v. Whitaker
2019-01-22
18-1138P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Kayatta", "parties": "", "opinions": [{"author": "STAHL, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1138\n\n JOSE ALBERTO MEDINA,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,*\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Lynch, Stahl, and Kayatta,\n Circuit Judges.\n\n\n Randy Olen on brief for petitioner.\n Virginia L. Gordon, Trial Attorney, Civil Division, U.S.\nDepartment of Justice, Joseph H. Hunt, Assistant Attorney General,\nCivil Division, and Leslie McKay, Senior Litigation Counsel,\nOffice of Immigration Litigation, on brief for respondent.\n\n\n January 22, 2019\n\n\n\n\n * Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions, III as the respondent.\n\f STAHL, Circuit Judge. Petitioner Jose Alberto Medina\n\n(\"Medina\"), a native and citizen of Guatemala, appeals an order of\n\nthe Board of Immigration Appeals (\"BIA\") denying his motion to\n\nreopen his immigration proceedings as untimely. Medina concedes\n\nthat the motion, which was filed nearly five years after the BIA\n\nordered his removal, fell outside the 90-day limitations period\n\nset forth by statute and regulation. See 8 U.S.C. §\n\n1229a(c)(7)(C)(i); 8 C.F.R. § 1003.2(c)(2). However, he asks this\n\ncourt to find that the BIA abused its discretion in rejecting his\n\nequitable tolling argument which was meant to render his motion\n\ntimely. For the following reasons, we deny the petition.\n\n I. Factual and Procedural Background\n\n Medina entered the United States near San Ysidro,\n\nCalifornia, on February 5, 1993. In the summer of 1993, he filed\n\nan application for asylum with the Immigration and Naturalization\n\nService (\"INS\").1\n\n On May 23, 2007,2 INS began removal proceedings against\n\nMedina. In his written pleadings, Medina stated that he was\n\nseeking asylum, withholding of removal, and relief under the\n\n\n\n 1\n \"The INS's enforcement functions have since been transferred\nto the Department of Homeland Security (DHS) . . . .\" Chedid v.\nHolder, 573 F.3d 33, 34 n.1 (1st Cir. 2009).\n 2The record does not explain why no action was taken for\nfourteen years until April 10, 2007, when Medina was interviewed\nby an INS agent.\n\n\n - 2 -\n\fConvention Against Torture (\"CAT\"). In the alternative, he sought\n\nvoluntary departure. He appeared with his first counsel, Lidia\n\nSanchez (\"Sanchez\"), before an Immigration Judge (\"IJ\") at a\n\nhearing on October 10, 2007.3 At the hearing, counsel stated that\n\nMedina sought asylum and withholding of removal, and in the\n\nalternative, cancellation of removal, but expressly disavowed any\n\nclaim for relief under the CAT. The IJ then continued the hearing\n\nto July 7, 2008.\n\n Because of multiple continuances, the hearing did not\n\nresume until June 16, 2011. On that date, Sanchez represented\n\nthat Medina conceded removability but still sought cancellation of\n\nremoval or, in the alternative, voluntary departure. Counsel\n\nfurther stated that Medina wished to withdraw his applications for\n\nasylum and withholding of removal. The IJ asked counsel to affirm\n\nthat Medina understood that his withdrawal of those applications\n\nwould be with prejudice, and she affirmed that he did so\n\nunderstand. Thereafter, Medina provided oral testimony, the\n\ncontent of which is not relevant for resolving this appeal. No\n\nother witnesses testified at the hearing.\n\n\n\n\n 3\n The hearing was initially scheduled for October 3, 2007.\nHowever, the IJ postponed it one week because the parties had\nwaited an hour-and-a-half for his counsel to arrive, and the \"[IJ]\nha[d] too many cases on [that day] to wait for [Medina's]\nattorney.\"\n\n\n - 3 -\n\f On October 6, 2011, the IJ denied Medina's application\n\nfor cancellation of removal but granted a 60-day voluntary\n\ndeparture period. In short, the IJ found that Medina had failed\n\nto corroborate his credible testimony and failed to demonstrate\n\nthat his removal would cause \"exceptional and extremely unusual\n\nhardship,\" as required to obtain cancellation of removal, for him\n\nand his family, including two daughters who were U.S. citizens.\n\n On November 4, 2011, with the assistance of a new\n\nattorney, Medina filed a notice of appeal with the BIA. In a brief\n\ndated March 7, 2012, Medina raised several claims, arguing that he\n\nwas unprepared for his prior hearing, that the IJ failed to provide\n\nhim an opportunity to show that corroborating evidence could not\n\nbe reasonably obtained, and that his first counsel's decision to\n\nwithdraw his asylum claim was \"suspect.\"\n\n The BIA dismissed the appeal on October 23, 2012, finding\n\nthat Medina failed to meet his burden of \"demonstrat[ing]\n\neligibility for cancellation of removal.\" Because the 60-day\n\nperiod for voluntary departure provided by the IJ had passed, the\n\nBIA ordered Medina removed from the United States. Despite the\n\nremoval order, however, it appears that Medina neither left the\n\nUnited States nor sought judicial review of the removal order.\n\n On August 21, 2017, with the assistance of his third\n\n(and current) counsel, Medina filed a motion to reopen his removal\n\nproceedings with the BIA. In his brief, he alleged that Sanchez\n\n\n - 4 -\n\frendered ineffective assistance when she withdrew his applications\n\nfor asylum, withholding of removal, and protection under the CAT.\n\nHe theorized that this was because she had been unprepared to\n\n\"prosecute\" his claims. He further represented that he had\n\ncomplied with the requirements of Matter of Lozada, 19 I&N Dec.\n\n637 (BIA 1988) for filing a motion to motion to reopen.4 On that\n\nbasis, Medina sought to reopen his removal proceedings, or\n\nalternatively, equitably toll the 90-day limitations period for\n\nfiling a motion to reopen. In response, Sanchez submitted an\n\naffidavit refuting Medina's allegations.\n\n On January 26, 2018, the BIA denied the motion to reopen\n\nas untimely. See 8 C.F.R. § 1003.2(c)(2). It noted that Medina\n\nhad waited for nearly five years after the BIA originally ordered\n\nhim removed before filing the motion. In addition, the BIA stated\n\n\n\n\n 4 \"Under Lozada, a valid motion to reopen based on ineffective\nassistance of counsel must be supported by:\n (1) an affidavit explaining the petitioner's\n agreement with counsel regarding legal\n representation; (2) evidence that counsel has\n been informed of the allegations of\n ineffective assistance and has had an\n opportunity to respond; and (3) if it is\n asserted that counsel's handling of the case\n involved a violation of ethical or legal\n responsibilities, a complaint against the\n attorney filed with disciplinary authorities\n or, in the alternative, an explanation for why\n such a complaint has not been filed.\"\nGarcía v. Lynch, 821 F.3d 178, 180 n.2 (1st Cir. 2016).\n\n\n - 5 -\n\fthat Medina had not demonstrated that he \"pursued his ineffective\n\nassistance of counsel claim with the requisite due diligence[,]\"\n\nand thus the 90-day limitations period for filing such a motion\n\nwould not be equitably tolled. The BIA further declined to\n\nexercise its discretionary authority to reopen Medina's\n\nproceedings sua sponte. This petition for judicial review\n\nfollowed.5\n\n II. Analysis\n\n \"Because a motion to reopen removal proceedings is a\n\ndisfavored tool, given the threat it poses to finality, the BIA\n\nhas a fair amount of latitude to grant or deny the motion and our\n\nreview is for abuse of discretion only.\" Mazariegos v. Lynch, 790\n\nF.3d 280, 285 (1st Cir. 2015) (citing Perez v. Holder, 740 F.3d\n\n57, 61 (1st Cir. 2014)). To prevail, the petitioner must show\n\nthat the \"BIA committed an error of law or exercised its judgment\n\nin an arbitrary, capricious, or irrational way.\" Id. (quoting\n\nRaza v. Gonzales, 484 F.3d 125, 127 (1st Cir. 2007)) (internal\n\nquotation marks omitted).\n\n A motion to reopen \"shall be filed within 90 days of the\n\ndate of entry of a final administrative order of removal.\" 8\n\n\n 5 In his brief, Medina does not seek review of the BIA's\nOctober 23, 2012 order dismissing his appeal of the IJ's decision.\nNor does he challenge the BIA's decision not to reopen his\nproceedings sua sponte. Accordingly, our review is limited to the\nBIA's January 26, 2018 denial of Medina's request for equitable\ntolling. See Ouk v. Keisler, 505 F.3d 63, 66 n.3 (1st Cir. 2007).\n\n\n - 6 -\n\fU.S.C. § 1229a(c)(7)(C)(i); see also 8 C.F.R § 1003.2(c)(2). The\n\nquestion of whether equitable tolling applies to motions to reopen\n\nremains \"an open question in the First Circuit.\" Pineda v.\n\nWhitaker, 908 F.3d 836, 841 (1st Cir. 2018) (citing Xue Su Wang v.\n\nHolder, 750 F.3d 87, 90 (1st Cir. 2014)).\n\n We need not resolve that question today, however,\n\nbecause \"even assuming equitable tolling were available, we could\n\nonly reach the merits . . . if the Board abused its discretion in\n\nfinding that [petitioner] had not exercised the 'due diligence'\n\nrequired by our case law.\" Chedid v. Holder, 573 F.3d 33, 37 (1st\n\nCir. 2009); see also Pineda, 908 F.3d at 841. We have also held\n\nthat \"even if equitable tolling were available . . . the doctrine\n\nshould be 'sparingly invoked[.]'\" Chedid, 573 F.3d at 37 (quoting\n\nJobe v. INS, 238 F.3d 96, 100 (1st Cir. 2001) (en banc)).\n\n \"For equitable tolling to apply, a party must establish\n\n'(1) that he has been pursuing his rights diligently, and (2) that\n\nsome extraordinary circumstance stood in his way.'\" Xue Su Wang,\n\n750 F.3d at 90 (quoting Neves v. Holder, 613 F.3d 30, 36 (1st Cir.\n\n2010) (per curiam)). Furthermore, the party \"must have diligently\n\npursued his rights for the entire period he seeks tolled, not\n\nmerely once he discovers the underlying circumstance warranting\n\ntolling.\" Neves, 613 F.3d at 36.\n\n Here, Medina provided the BIA no evidence that he\n\ncontinuously pursued his rights. The administrative record only\n\n\n - 7 -\n\fshows that Medina filed an affidavit dated March 8, 2016, stating\n\n\"[f]or the past 3 years, I have stayed in touch with my attorneys.\"\n\nThis hardly constitutes the \"specific details\" we have required.6\n\nId. at 37.\n\n In addition, his affidavit only covers the period\n\nbetween March 2013 and March 2016. This leaves another 21 months\n\nunaccounted for, including the period from October 2012, when the\n\nBIA dismissed his appeal, to March 2013, and the period from March\n\n2016 to August 2017, when Medina filed the motion to reopen. See\n\nJobe, 238 F.3d at 100 n.8 (noting that petitioner must fill in any\n\ngaps in the timeline). Therefore, the BIA cannot be said to have\n\nabused its discretion in declining to apply equitable tolling.\n\nPineda, 908 F.3d at 842.\n\n In his brief, Medina also suggests that he was unaware\n\nof his ineffective assistance of counsel claim until his present\n\ncounsel reviewed his case. However, that contention does not\n\n\n\n 6 Medina also relies on two out-of-circuit cases in support\nof his equitable tolling argument. This reliance is misplaced.\nIn Avagyan v. Holder, the Ninth Circuit held that the petitioner\nhad diligently pursued relief when she filed a motion to reopen\nwithin 90 days of learning of her prior counsel's incorrect advice.\n646 F.3d 672, 682 (9th Cir. 2011). Similarly, in Gordillo v.\nHolder, the Sixth Circuit held that the petitioners had diligently\npursued relief because they had given up their claims only after\nbeing repeatedly told by multiple lawyers that they did not have\nany rights. 640 F.3d 700, 705 (6th Cir. 2011). By contrast, in\nthis case Medina fails to explain his five-year delay before filing\nthe motion to reopen, let alone provide the \"specific details\"\nrequired by this circuit. See Neves, 613 F.3d at 37.\n\n\n - 8 -\n\fcomport with the record. For example, there is evidence that\n\nMedina was on notice of a potential ineffective assistance of\n\ncounsel claim from as early as March 2012, five years before filing\n\nthe motion to reopen. At that time, his then-counsel wrote in a\n\nbrief to the BIA that \"the withdrawal of the asylum application is\n\nsuspect in that [first counsel] indicated [initially] that she was\n\nproceeding on the [asylum] application and then, without\n\nconsultation . . . withdr[e]w the [asylum] application with\n\nprejudice.\" And, by Medina's own admission, the latest he became\n\naware of the potential claim was March 8, 2016, when he signed the\n\naffidavit claiming that Sanchez's assistance was defective. But,\n\nMedina fails to explain why he took no action seeking relief until\n\nAugust 2017, fifteen months later.\n\n Thus, even assuming equitable tolling could apply to\n\nmotions to reopen, Medina fails to show that he acted with the\n\ndiligence required to obtain such relief. Accordingly, the BIA\n\ndid not abuse its discretion in denying his motion to reopen.\n\n III. Conclusion\n\n For the foregoing reasons, the petition for review is\n\nDENIED.\n\n\n\n\n - 9 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360693/", "author_raw": "STAHL, Circuit Judge"}]}
LYNCH
STAHL
KAYATTA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583440/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Jose Alberto MEDINA, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-22\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1138\n\n JOSE ALBERTO MEDINA,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,*\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Lynch, Stahl, and Kayatta,\n Circuit Judges.\n\n\n Randy Olen on brief for petitioner.\n Virginia L. Gordon, Trial Attorney, Civil Division, U.S.\nDepartment of Justice, Joseph H. Hunt, Assistant Attorney General,\nCivil Division, and Leslie McKay, Senior Litigation Counsel,\nOffice of Immigration Litigation, on brief for respondent.\n\n\n January 22, 2019\n\n\n\n\n * Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions, III as the respondent.\n\f STAHL, Circuit Judge. Petitioner Jose Alberto Medina\n\n(\"Medina\"), a native and citizen of Guatemala, appeals an order of\n\nthe Board of Immigration Appeals (\"BIA\") denying his motion to\n\nreopen his immigration proceedings as untimely. Medina concedes\n\nthat the motion, which was filed nearly five years after the BIA\n\nordered his removal, fell outside the 90-day limitations period\n\nset forth by statute and regulation. See 8 U.S.C. §\n\n1229a(c)(7)(C)(i); 8 C.F.R. § 1003.2(c)(2). However, he asks this\n\ncourt to find that the BIA abused its discretion in rejecting his\n\nequitable tolling argument which was meant to render his motion\n\ntimely. For the following reasons, we deny the petition.\n\n I. Factual and Procedural Background\n\n Medina entered the United States near San Ysidro,\n\nCalifornia, on February 5, 1993. In the summer of 1993, he filed\n\nan application for asylum with the Immigration and Naturalization\n\nService (\"INS\").1\n\n On May 23, 2007,2 INS began removal proceedings against\n\nMedina. In his written pleadings, Medina stated that he was\n\nseeking asylum, withholding of removal, and relief under the\n\n\n\n 1\n \"The INS's enforcement functions have since been transferred\nto the Department of Homeland Security (DHS) . . . .\" Chedid v.\nHolder, 573 F.3d 33, 34 n.1 (1st Cir. 2009).\n 2The record does not explain why no action was taken for\nfourteen years until April 10, 2007, when Medina was interviewed\nby an INS agent.\n\n\n - 2 -\n\fConvention Against Torture (\"CAT\"). In the alternative, he sought\n\nvoluntary departure. He appeared with his first counsel, Lidia\n\nSanchez (\"Sanchez\"), before an Immigration Judge (\"IJ\") at a\n\nhearing on October 10, 2007.3 At the hearing, counsel stated that\n\nMedina sought asylum and withholding of removal, and in the\n\nalternative, cancellation of removal, but expressly disavowed any\n\nclaim for relief under the CAT. The IJ then continued the hearing\n\nto July 7, 2008.\n\n Because of multiple continuances, the hearing did not\n\nresume until June 16, 2011. On that date, Sanchez represented\n\nthat Medina conceded removability but still sought cancellation of\n\nremoval or, in the alternative, voluntary departure. Counsel\n\nfurther stated that Medina wished to withdraw his applications for\n\nasylum and withholding of removal. The IJ asked counsel to affirm\n\nthat Medina understood that his withdrawal of those applications\n\nwould be with prejudice, and she affirmed that he did so\n\nunderstand. Thereafter, Medina provided oral testimony, the\n\ncontent of which is not relevant for resolving this appeal. No\n\nother witnesses testified at the hearing.\n\n\n\n\n 3\n The hearing was initially scheduled for October 3, 2007.\nHowever, the IJ postponed it one week because the parties had\nwaited an hour-and-a-half for his counsel to arrive, and the \"[IJ]\nha[d] too many cases on [that day] to wait for [Medina's]\nattorney.\"\n\n\n - 3 -\n\f On October 6, 2011, the IJ denied Medina's application\n\nfor cancellation of removal but granted a 60-day voluntary\n\ndeparture period. In short, the IJ found that Medina had failed\n\nto corroborate his credible testimony and failed to demonstrate\n\nthat his removal would cause \"exceptional and extremely unusual\n\nhardship,\" as required to obtain cancellation of removal, for him\n\nand his family, including two daughters who were U.S. citizens.\n\n On November 4, 2011, with the assistance of a new\n\nattorney, Medina filed a notice of appeal with the BIA. In a brief\n\ndated March 7, 2012, Medina raised several claims, arguing that he\n\nwas unprepared for his prior hearing, that the IJ failed to provide\n\nhim an opportunity to show that corroborating evidence could not\n\nbe reasonably obtained, and that his first counsel's decision to\n\nwithdraw his asylum claim was \"suspect.\"\n\n The BIA dismissed the appeal on October 23, 2012, finding\n\nthat Medina failed to meet his burden of \"demonstrat[ing]\n\neligibility for cancellation of removal.\" Because the 60-day\n\nperiod for voluntary departure provided by the IJ had passed, the\n\nBIA ordered Medina removed from the United States. Despite the\n\nremoval order, however, it appears that Medina neither left the\n\nUnited States nor sought judicial review of the removal order.\n\n On August 21, 2017, with the assistance of his third\n\n(and current) counsel, Medina filed a motion to reopen his removal\n\nproceedings with the BIA. In his brief, he alleged that Sanchez\n\n\n - 4 -\n\frendered ineffective assistance when she withdrew his applications\n\nfor asylum, withholding of removal, and protection under the CAT.\n\nHe theorized that this was because she had been unprepared to\n\n\"prosecute\" his claims. He further represented that he had\n\ncomplied with the requirements of Matter of Lozada, 19 I&N Dec.\n\n637 (BIA 1988) for filing a motion to motion to reopen.4 On that\n\nbasis, Medina sought to reopen his removal proceedings, or\n\nalternatively, equitably toll the 90-day limitations period for\n\nfiling a motion to reopen. In response, Sanchez submitted an\n\naffidavit refuting Medina's allegations.\n\n On January 26, 2018, the BIA denied the motion to reopen\n\nas untimely. See 8 C.F.R. § 1003.2(c)(2). It noted that Medina\n\nhad waited for nearly five years after the BIA originally ordered\n\nhim removed before filing the motion. In addition, the BIA stated\n\n\n\n\n 4 \"Under Lozada, a valid motion to reopen based on ineffective\nassistance of counsel must be supported by:\n (1) an affidavit explaining the petitioner's\n agreement with counsel regarding legal\n representation; (2) evidence that counsel has\n been informed of the allegations of\n ineffective assistance and has had an\n opportunity to respond; and (3) if it is\n asserted that counsel's handling of the case\n involved a violation of ethical or legal\n responsibilities, a complaint against the\n attorney filed with disciplinary authorities\n or, in the alternative, an explanation for why\n such a complaint has not been filed.\"\nGarcía v. Lynch, 821 F.3d 178, 180 n.2 (1st Cir. 2016).\n\n\n - 5 -\n\fthat Medina had not demonstrated that he \"pursued his ineffective\n\nassistance of counsel claim with the requisite due diligence[,]\"\n\nand thus the 90-day limitations period for filing such a motion\n\nwould not be equitably tolled. The BIA further declined to\n\nexercise its discretionary authority to reopen Medina's\n\nproceedings sua sponte. This petition for judicial review\n\nfollowed.5\n\n II. Analysis\n\n \"Because a motion to reopen removal proceedings is a\n\ndisfavored tool, given the threat it poses to finality, the BIA\n\nhas a fair amount of latitude to grant or deny the motion and our\n\nreview is for abuse of discretion only.\" Mazariegos v. Lynch, 790\n\nF.3d 280, 285 (1st Cir. 2015) (citing Perez v. Holder, 740 F.3d\n\n57, 61 (1st Cir. 2014)). To prevail, the petitioner must show\n\nthat the \"BIA committed an error of law or exercised its judgment\n\nin an arbitrary, capricious, or irrational way.\" Id. (quoting\n\nRaza v. Gonzales, 484 F.3d 125, 127 (1st Cir. 2007)) (internal\n\nquotation marks omitted).\n\n A motion to reopen \"shall be filed within 90 days of the\n\ndate of entry of a final administrative order of removal.\" 8\n\n\n 5 In his brief, Medina does not seek review of the BIA's\nOctober 23, 2012 order dismissing his appeal of the IJ's decision.\nNor does he challenge the BIA's decision not to reopen his\nproceedings sua sponte. Accordingly, our review is limited to the\nBIA's January 26, 2018 denial of Medina's request for equitable\ntolling. See Ouk v. Keisler, 505 F.3d 63, 66 n.3 (1st Cir. 2007).\n\n\n - 6 -\n\fU.S.C. § 1229a(c)(7)(C)(i); see also 8 C.F.R § 1003.2(c)(2). The\n\nquestion of whether equitable tolling applies to motions to reopen\n\nremains \"an open question in the First Circuit.\" Pineda v.\n\nWhitaker, 908 F.3d 836, 841 (1st Cir. 2018) (citing Xue Su Wang v.\n\nHolder, 750 F.3d 87, 90 (1st Cir. 2014)).\n\n We need not resolve that question today, however,\n\nbecause \"even assuming equitable tolling were available, we could\n\nonly reach the merits . . . if the Board abused its discretion in\n\nfinding that [petitioner] had not exercised the 'due diligence'\n\nrequired by our case law.\" Chedid v. Holder, 573 F.3d 33, 37 (1st\n\nCir. 2009); see also Pineda, 908 F.3d at 841. We have also held\n\nthat \"even if equitable tolling were available . . . the doctrine\n\nshould be 'sparingly invoked[.]'\" Chedid, 573 F.3d at 37 (quoting\n\nJobe v. INS, 238 F.3d 96, 100 (1st Cir. 2001) (en banc)).\n\n \"For equitable tolling to apply, a party must establish\n\n'(1) that he has been pursuing his rights diligently, and (2) that\n\nsome extraordinary circumstance stood in his way.'\" Xue Su Wang,\n\n750 F.3d at 90 (quoting Neves v. Holder, 613 F.3d 30, 36 (1st Cir.\n\n2010) (per curiam)). Furthermore, the party \"must have diligently\n\npursued his rights for the entire period he seeks tolled, not\n\nmerely once he discovers the underlying circumstance warranting\n\ntolling.\" Neves, 613 F.3d at 36.\n\n Here, Medina provided the BIA no evidence that he\n\ncontinuously pursued his rights. The administrative record only\n\n\n - 7 -\n\fshows that Medina filed an affidavit dated March 8, 2016, stating\n\n\"[f]or the past 3 years, I have stayed in touch with my attorneys.\"\n\nThis hardly constitutes the \"specific details\" we have required.6\n\nId. at 37.\n\n In addition, his affidavit only covers the period\n\nbetween March 2013 and March 2016. This leaves another 21 months\n\nunaccounted for, including the period from October 2012, when the\n\nBIA dismissed his appeal, to March 2013, and the period from March\n\n2016 to August 2017, when Medina filed the motion to reopen. See\n\nJobe, 238 F.3d at 100 n.8 (noting that petitioner must fill in any\n\ngaps in the timeline). Therefore, the BIA cannot be said to have\n\nabused its discretion in declining to apply equitable tolling.\n\nPineda, 908 F.3d at 842.\n\n In his brief, Medina also suggests that he was unaware\n\nof his ineffective assistance of counsel claim until his present\n\ncounsel reviewed his case. However, that contention does not\n\n\n\n 6 Medina also relies on two out-of-circuit cases in support\nof his equitable tolling argument. This reliance is misplaced.\nIn Avagyan v. Holder, the Ninth Circuit held that the petitioner\nhad diligently pursued relief when she filed a motion to reopen\nwithin 90 days of learning of her prior counsel's incorrect advice.\n646 F.3d 672, 682 (9th Cir. 2011). Similarly, in Gordillo v.\nHolder, the Sixth Circuit held that the petitioners had diligently\npursued relief because they had given up their claims only after\nbeing repeatedly told by multiple lawyers that they did not have\nany rights. 640 F.3d 700, 705 (6th Cir. 2011). By contrast, in\nthis case Medina fails to explain his five-year delay before filing\nthe motion to reopen, let alone provide the \"specific details\"\nrequired by this circuit. See Neves, 613 F.3d at 37.\n\n\n - 8 -\n\fcomport with the record. For example, there is evidence that\n\nMedina was on notice of a potential ineffective assistance of\n\ncounsel claim from as early as March 2012, five years before filing\n\nthe motion to reopen. At that time, his then-counsel wrote in a\n\nbrief to the BIA that \"the withdrawal of the asylum application is\n\nsuspect in that [first counsel] indicated [initially] that she was\n\nproceeding on the [asylum] application and then, without\n\nconsultation . . . withdr[e]w the [asylum] application with\n\nprejudice.\" And, by Medina's own admission, the latest he became\n\naware of the potential claim was March 8, 2016, when he signed the\n\naffidavit claiming that Sanchez's assistance was defective. But,\n\nMedina fails to explain why he took no action seeking relief until\n\nAugust 2017, fifteen months later.\n\n Thus, even assuming equitable tolling could apply to\n\nmotions to reopen, Medina fails to show that he acted with the\n\ndiligence required to obtain such relief. Accordingly, the BIA\n\ndid not abuse its discretion in denying his motion to reopen.\n\n III. Conclusion\n\n For the foregoing reasons, the petition for review is\n\nDENIED.\n\n\n\n\n - 9 -\n[END_CASE]", "role": "user" } ]
4,584,528
United States v. Martinez-Benitez
2019-01-24
17-1393P
U.S. Court of Appeals for the First Circuit
{"judges": "Before Lynch, Thompson, and Barron, Circuit Judges.", "parties": "", "opinions": [{"author": "THOMPSON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1393\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOSÉ G. MARTÍNEZ-BENÍTEZ,\n\n Defendant, Appellant.\n\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Lynch, Thompson, and Barron,\n Circuit Judges.\n\n\n\n Jóse Luis Novas-Debien for appellant.\n Jonathan L. Gottfried, Assistant United States Attorney, with\nwhom Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Julia M. Meconiates, Assistant United\nStates Attorney, were on brief, for appellee.\n\n\n\n\n January 24, 2019\n\f THOMPSON, Circuit Judge. At stake today is whether\n\nfederal prosecutors proved José Martínez Benítez's prior Puerto\n\nRico-law conviction (described below) is a \"controlled substance\n\noffense\" for federal-sentencing purposes. Concluding they did\n\nnot, we vacate his sentence and remand for resentencing consistent\n\nwith this opinion.\n\n How Martínez's Case Got Here1\n\n Martínez pled guilty in federal court to possessing a\n\nfirearm despite his status as a felon. See 18 U.S.C. § 922(g)(1).\n\nHis was a \"straight plea,\" meaning he and the government did not\n\nenter into any plea agreement. As for how things shook out at\n\nsentencing, this is what you need to know.2\n\n\n\n 1 According to Spanish naming conventions, if a person has\ntwo surnames, the first (which is the father's last name) is\nprimary and the second (which is the mother's maiden name) is\nsubordinate. Which is why we use \"Martínez\" for the rest of the\nopinion.\n 2 First, though, a quick heads-up for the lay readers out\nthere: Sentencing under the federal sentencing guidelines starts\nwith the base offense level — i.e., a point score for a specified\noffense or group of offenses. See, e.g., United States v. Serrano-\nMercado, 784 F.3d 838, 840 (1st Cir. 2015). The guidelines then\nmake adjustments for any aggravating or mitigating factors in the\ndefendant's case, thus arriving at a total offense level. See id.\nThe guidelines also assign points based on the defendant's criminal\nhistory — points that get converted into various criminal history\ncategories, designated by Roman numerals I through VI. Id. Armed\nwith this info, the judge turns to the guidelines's sentencing\ntable. Id. And by plotting the defendant's total offense level\nalong the table's vertical axis and his criminal history category\nalong the table's horizontal axis, the judge ends up with an\nadvisory prison range. Id. From there, the judge sees if any\n - 2 -\n\f The sentencing guidelines apply an enhanced base offense\n\nlevel of 20 for firearm offenses preceded by one felony conviction\n\nfor a \"controlled substance offense,\" see U.S.S.G.\n\n§ 2K2.1(a)(4)(A) — a phrase that pertinently covers a state-law\n\ncrime, \"punishable by imprisonment for a term exceeding one year,\n\nthat prohibits . . . the possession of a controlled substance . . .\n\nwith intent to . . . distribute,\" id. § 4B1.2(b); see also id.\n\n§ 2K2.1 cmt. n.1 (referring the reader to § 4B1.2(b) and its\n\naccompanying application note 1 for a definition of a \"[c]ontrolled\n\nsubstance offense\").3 And the phrase covers as well \"the offenses\n\nof aiding and abetting, conspiring, and attempting to commit such\n\noffenses.\" Id. § 4B1.2 cmt. n.1. Also of prime importance to the\n\npresent controversy, the government has \"the burden of\n\nestablishing\" by a preponderance of the evidence \"that a prior\n\n\ndepartures are called for, considers various sentencing factors,\nand determines what sentence (whether within, above, or below the\nsuggested range) seems appropriate. See, e.g., United States v.\nDávila-González, 595 F.3d 42, 46 (1st Cir. 2010).\n 3No one argues that Puerto Rico is unlike a state for\n§ 4B1.2(b) purposes. See generally United States v. Torres-Rosa,\n209 F.3d 4, 8 (1st Cir. 2000) (concluding that \"because the\n[defendant] had not shown\" that the guidelines \"'meant to exclude\nfelony convictions in Puerto Rico Commonwealth Courts for\nenhancement purposes,' no plain error inhered\" (quoting United\nStates v. Morales-Diaz, 925 F.2d 535, 540 (1st Cir. 1991));\nMorales-Diaz, 925 F.2d at 540 (rejecting the defendant's\nunpreserved suggestion that \"because Puerto Rico is not a state,\"\nthe Puerto Rico conviction in play there was not a state-law\noffense \"under § 4B1.2\" (internal quotation marks omitted)). So\nwe say no more about that subject.\n - 3 -\n\fconviction qualifies as a predicate offense for sentencing\n\nenhancement purposes.\" United States v. Dávila-Félix, 667 F.3d\n\n47, 55 (1st Cir. 2011); United States v. Bryant, 571 F.3d 147, 153\n\n(1st Cir. 2009).\n\n From the documents presented by prosecutors at\n\nsentencing, the district judge learned that years before his run-\n\nin with the feds, Puerto Rico authorities had charged Martínez\n\nwith knowingly or intentionally possessing heroin with intent to\n\ndistribute, in violation of Puerto Rico's Controlled Substances\n\nAct (\"CSA\"), see P.R. Laws Ann. tit. 24, § 2401 — a law commonly\n\ncalled \"Article 401.\" As relevant here, Article 401 criminalizes\n\nthe possession of certain controlled substances (including heroin)\n\nwith intent to \"manufacture, distribute, dispense, transport or\n\nconceal,\" see id. § 2401(a)(1), and calls for a \"fixed\" prison\n\n\"term\" of 20 years, which may be increased to a 30-year \"maximum\"\n\nterm or decreased to a 10-year \"minimum\" term, if \"aggravating\" or\n\n\"extenuating\" circumstances exist, see id. § 2401(b)(1)(A). We\n\nhave dealt with Article 401 before, for instance in an opinion\n\nholding that \"intent to conceal\" is \"a non-predicate offense\" under\n\n§ 4B1.2(b). See Dávila-Félix, 667 F.3d at 56 (concluding that\n\n\"concealment of a controlled substance\" is \"not commonly\n\nconsidered [a] drug trafficking offense[]\").\n\n\n\n - 4 -\n\f Anyway, Martínez pled guilty to a \"reclassified\" charge\n\nof \"attempt[ing] or conspir[ing] to commit\" an \"offense\" under\n\nPuerto Rico's CSA, see P.R. Laws Ann. tit. 24, § 2406 — a provision\n\ncolloquially called \"Article 406,\" the penalty for which \"shall\n\nnot exceed\" the penalty for the substantive \"offense\" that \"was\n\nthe object of the attempt or conspiracy.\" By doing so, he avoided\n\na fixed mandatory 20-year prison term and made himself eligible\n\nfor a suspended sentence. See P.R. Laws Ann. tit. 34, § 1027; see\n\nalso P.R. Laws Ann. tit. 24, § 2414.4 And ultimately, the Puerto\n\nRico court gave him a 3-year suspended sentence —— a sentence that\n\nhas special significance as to the nature of the offense.\n\n You should know too (because it affects the case's\n\noutcome, for reasons explained presently) that Puerto Rico's CSA\n\n\n\n 4 The first statute authorizes the Puerto Rico \"Court of First\nInstance\" to\n suspend the effect of the sentence of imprisonment in\n all cases of felonies . . . other than . . . [o]ne of\n the following felonies under the [CSA]: § 2401\n (prohibited acts); § 2405 (distribution to persons under\n eighteen . . . years of age); § 2411 (employment of\n minors); § 2411a (introduction of drugs to schools and\n institutions), all of Title 24.\nP.R. Laws Ann. tit. 34, § 1027(6). The second statute says that\n\"[t]he provisions on suspended sentence\" are not \"applicable to\"\npersons \"convicted of violating §§ 2401(a), 2405, 2411 and 2411a\nof this title when the distribution, sale, introduction,\ndispensing or possession and transportation for the purpose of\ndistribution is involved, except in those cases in which the\nprovisions of §§ 1042 and 1043 of Title 34 are applicable.\" P.R.\nLaws Ann. tit. 24, § 2414.\n - 5 -\n\fbans not only possession-with-intent-to-distribute offenses\n\ncovered by Article 401, but also (among other things) simple-\n\npossession offenses (i.e., offenses involving possession of drugs\n\nnot prescribed, with no intent to distribute), see P.R. Laws Ann.\n\ntit. 24, § 2404 — a law widely referred to as \"Article 404,\" which\n\noutlaws the knowing or intentional possession of \"any controlled\n\nsubstance, unless such substance was obtained directly, or\n\npursuant to a valid prescription or order from a practitioner,\n\nwhile acting in the course of his professional practice, or except\n\nas authorized by this chapter.\" Article 404 calls for a \"fixed\"\n\n3-year prison \"term,\" which may be increased to a 5-year \"maximum\"\n\nterm or decreased to a 2-year \"minimum\" term, if \"aggravating\" or\n\n\"extenuating\" circumstances exist. We are also no strangers to\n\nArticle 404 — just consider United States v. Román-Huertas, 848\n\nF.3d 72 (1st Cir. 2017), which holds that an Article 404 \"mere\n\npossession offense[]\" does not count as a qualifying predicate\n\nunder § 4B1.2(b). Id. at 77; see also United States v. Ramos-\n\nGonzález, 775 F.3d 483, 507 n.27 (1st Cir. 2015).\n\n Kicking off the sentencing in the federal case, the\n\ndistrict judge noted that while the charging document in the Puerto\n\nRico case listed Martínez's crime as an Article 401 possession-\n\nwith-intent-to-distribute offense, the judgment showed that he had\n\npled to an Article 406 attempt-or-conspiracy offense. Then relying\n\n - 6 -\n\fon a footnote in Puerto Rico v. Ramos Rivas, 2007 TSPR 138, 171\n\nD.P.R. 826, 2007 WL 2079844, at *1 n.1 (P.R. 2007) — which says\n\nthat if an Article 401 charge is reclassified as an Article 406\n\noffense, a court \"must refer\" back to Article 401 to determine the\n\nproper \"penalty\" — the judge ruled that Martínez's Article 406\n\nconviction was for an \"attempted conspiracy to distribute\n\ncontrolled substances.\"5 So the judge concluded that the Article\n\n406 conviction amounted to a \"controlled substance offense\" under\n\nthe guidelines and increased Martínez's base offense level\n\naccordingly — from 14 to 20, which helped set his recommended\n\nguidelines range at 30 to 37 months. And when all was said and\n\ndone, the judge sentenced him to 34 months in prison.\n\n Unhappy with this outcome, Martínez now appeals.\n\n Jurisdiction and Standard of Review\n\n The district judge had original jurisdiction under 18\n\nU.S.C. § 3231. We have appellate jurisdiction under 28 U.S.C.\n\n\n\n\n 5 The Ramos Rivas footnote reads in relevant part:\n [Article] 406 of the Puerto Rico Controlled Substances\n Act . . . punishes the attempt or conspiracy to commit\n any of the crimes defined in the act. The [article]\n refers to base offenses, the attempt or conspiracy to\n commit which gave rise to the sentence imposed.\n Consequently, in this case we must refer to [Article]\n 401 . . . insofar as it concerns the penalty imposed.\n - 7 -\n\f§ 1291. And we review the judge's legal analysis de novo, see\n\nDávila-Félix, 667 F.3d at 54, noting additional details as needed.\n\n Summary of the Parties' Main Arguments\n\n Attacking the district judge's work, Martínez contends\n\nthat none of the government-provided documents showed his Article\n\n406 conviction was for attempt/conspiracy to possess heroin with\n\nintent to distribute (with Article 401 being the object of the\n\nattempt/conspiracy), rather than, say, attempt/conspiracy to\n\npossess heroin without intent to distribute (with Article 404 being\n\nthe object of the attempt/conspiracy) — the first is a § 4B1.2-\n\nqualifying predicate, he quickly reminds us; the second is not.\n\nAs for the judge's reliance on Ramos Rivas, Martínez claims that\n\nthis decision has zero relevance because (in his words) Ramos Rivas\n\ndoes not hold that \"all Article 406 convictions . . . reclassified\n\nfrom Article 401 are drug trafficking offenses.\"\n\n The government, contrastingly, argues that the district\n\njudge got everything exactly right. Puerto Rico law, the\n\ngovernment writes, directs courts to \"tie\" a defendant's Article\n\n406 attempt/conspiracy conviction to a substantive \"base offense\"\n\nunder Puerto Rico's CSA \"to determine the fixed penalty\" and then\n\nto pick \"a penalty not to exceed that maximum.\" To help with this\n\ntask, the government continues, Ramos Rivas requires courts to\n\n\"refer[] to the offense in the charging document[]\" to discern the\n\n - 8 -\n\fsubstantive offense underlying an Article 406 conviction \"that\n\n[was] reclassified from [another] charge[].\" Putting these points\n\ntogether, the government repeats that Martínez's plea resulted\n\nfrom an Article 401 possession-with-intent-to-distribute charge\n\nthat got \"reclassified to Article 406.\" And given the charging\n\ndocument, the judge rightly ruled that Martínez's Article 406\n\nguilty-plea conviction was \"for attempting or conspiring to\n\npossess\" heroin \"with intent to distribute\" — or so the government\n\ninsists, noting too that Martínez's 3-year suspended sentence did\n\nnot \"exceed\" the pertinent 20-year maximum penalty in Article 401.\n\nErgo, the government concludes, the judge rightly found that\n\nMartínez's conviction was a § 4B1.2-qualifying predicate.\n\n As a fallback, the government contends that even if we\n\nthink Martínez pled guilty to attempting/conspiring to violate\n\nArticle 401 by means other than possessing heroin with distributive\n\nintent — like, for example, by possessing heroin with intent to\n\nconceal — we should still affirm his sentence. And that is\n\nbecause, in the government's view, even though our Dávila-Félix\n\nopinion says Article 401 \"criminalizes actions . . . not commonly\n\nconsidered drug trafficking offenses, such as concealment of a\n\ncontrolled substance,\" see 667 F.3d at 56, a Puerto Rico Supreme\n\nCourt case predating Dávila-Félix — Puerto Rico v. Rosario Cintrón,\n\n2 P.R. Offic. Trans. 107, 102 D.P.R. 82 (1974) — holds otherwise.\n\n - 9 -\n\fThus, according to the government, we as a panel must overrule\n\nDávila-Félix. Martínez, for his part, claims that the government\n\nwaived this argument by not raising it in the district court — a\n\ncontention the government disputes.\n\n Our Take\n\n To state the obvious, Martínez's federal sentence can\n\nstand only if his Article 406 attempt/conspiracy conviction\n\nconstitutes a controlled substance offense under the guidelines —\n\nan issue (we say again) that the government had the burden of\n\nproving. See Dávila–Félix, 667 F.3d at 55. As the parties agree,\n\nArticle 406 covers separate crimes with separate elements — some\n\nof which qualify as controlled substance offenses, like\n\nattempt/conspiracy to possess heroin with distributive intent; and\n\nothers of which do not, like attempt/conspiracy to possess heroin\n\nwithout distributive intent. See Román-Huertas, 848 F.3d at 77.\n\nSo, in legalese, Article 406 is a \"divisible\" statute. See Mathis\n\nv. United States, 136 S. Ct. 2243, 2249 (2016). Which means we\n\nmust apply what is called the \"modified categorical approach,\" a\n\nprocedure that lets judges look at a narrow set of documents from\n\na defendant's conviction — like \"the indictment, jury\n\ninstructions, or plea agreement and colloquy\" — to see what crime\n\nhe committed. Id. (citing Shepard v. United States, 544 U.S. 13,\n\n\n\n - 10 -\n\f26 (2005), and Taylor v. United States, 495 U.S. 575, 602 (1990));\n\nsee also Román-Huertas, 848 F.3d at 77.\n\n Back again then to the government-filed papers. The\n\ncharging document in Martínez's Puerto Rico case accused him of\n\npossessing heroin with intent to distribute, in violation of\n\nArticle 401. And the sentencing document shows he later pled\n\nguilty to an Article 406 attempt/conspiracy crime, reclassified\n\nfrom the Article 401 charge. Unfortunately for us, however, the\n\ndocuments do not say what he pled guilty to attempting/conspiring\n\nto do: possessing heroin with intent to distribute (an Article\n\n401 substantive offense), perhaps — a qualifying predicate under\n\n§ 4B1.2; or perhaps possessing heroin without intent to distribute\n\n(an Article 404 substantive offense) — a non-qualifying predicate\n\nunder § 4B1.2. And that failure devastates the government's theory\n\nhere, as we now explain.\n\n The 3-year suspended sentence Martínez received is\n\ncertainly consistent with his having pled to attempting/conspiring\n\nto possess heroin without distributive intent. But it is equally\n\nconsistent with his having pled to attempting/conspiring to\n\npossess heroin with distributive intent. We say that because the\n\n3-year suspended sentence does not exceed the pertinent maximum\n\npenalties under Article 404 and Article 401. Remember: Article\n\n404 calls for a \"fixed\" 3-year prison \"term\" for simple possession\n\n - 11 -\n\f(which the court can raise to a 5-year \"maximum\" term or drop to\n\na 2-year \"minimum\" term, if \"aggravating\" or \"extenuating\" factors\n\nexist). See P.R. Laws Ann. tit. 24, § 2404. And Article 401 calls\n\nfor a \"fixed\" prison \"term\" of 20 years for (among other things)\n\npossession with intent to distribute (which the court can raise to\n\na 30-year \"maximum\" term or drop to a 10-year \"minimum\" term, if\n\n\"aggravating\" or \"extenuating\" circumstances exist). See P.R.\n\nLaws Ann. tit. 24, § 2401.\n\n Hoping to get to the bottom of things, we asked the\n\ngovernment's lawyer at oral argument if a defendant charged with\n\nan Article 401 possession-with-intent-to-distribute offense could\n\ncop to an Article 404 simple-possession offense, which could then\n\nserve as the substantive offense underlying an Article 406\n\nattempt/conspiracy guilty-plea conviction. Yes, the lawyer said.6\n\nWhich makes sense given that \"[d]efendants are frequently charged\n\nfor crimes different from those they are ultimately convicted of.\"\n\nSee United States v. Bravo-García, No. 16-1258, slip op. at 3 (1st\n\nCir. July 10, 2017) (judgment). And based on this truism, we have\n\n\n\n\n 6\n Possession without distributive intent is a lesser-included\noffense of possession with distributive intent — a point the\ngovernment does not dispute. See generally Ramos-González, 775\nF.3d at 507 (mentioning how a \"police complaint\" accused a\ndefendant of possessing cocaine with distributive intent, \"a\nviolation of Article 401,\" but the defendant later pled \"guilty to\na [simple] possession crime\" under \"Article 404\").\n - 12 -\n\fsaid that a sentencing order \"stating that [the defendant's]\n\nArticle 406 offense was 'reclassified' from Article 401, on its\n\nown, . . . fails to justify a finding that [her] conviction is\n\nactually under Article 401\" instead of some other article. See\n\nid., slip. op. at 2 n.3.\n\n Seeking a way around these obstacles, the government's\n\nattorney basically fell back on an argument made in his brief:\n\ni.e., that because Martínez pled guilty to an Article 406\n\nattempt/conspiracy crime, reclassified from an Article 401\n\npossession-with-intent-to-distribute charge, then under Ramos\n\nRivas the Article 401 offense is considered the \"object\" of the\n\nattempt or conspiracy — meaning, at least according to the\n\ngovernment, Martínez pled guilty to attempting/conspiring to\n\npossess a controlled substance with intent to distribute, which\n\nmakes his Article 406 conviction a qualifying predicate offense\n\nfor a guidelines enhancement. But the government reads way too\n\nmuch into Ramos Rivas.\n\n Charged with violating Article 401 by possessing cocaine\n\nwith distributive intent, the Ramos Rivas defendant pled guilty to\n\ninfracting Article 406. See 2007 TSPR at ___, 171 D.P.R. at ___,\n\n2007 WL 2079844, at *1. Noting that she had two prior Article 404\n\nconvictions, the lower court imposed a 20-year sentence under a\n\nrecidivist statute in Puerto Rico's Penal Code. Id. Displeased,\n\n - 13 -\n\fthe defendant argued on appeal that because her earlier convictions\n\nwere for violating Puerto Rico's CSA, the court should have instead\n\nsentenced her under the less-onerous recidivist provision in\n\nArticle 401 of the CSA. See 2007 TSPR at ___, 171 D.P.R. at ___,\n\n2007 WL 2079844, at *1-2.7 The Commonwealth's position was\n\nessentially no harm, no foul because the sentence fell \"within the\n\nparameters\" of Article 401's recidivist provision. See 2007 TSPR\n\nat ___, 171 D.P.R. at ___, 2007 WL 2079844, at *7. Given the Ramos\n\nRivas parties' laser-like focus on Article 401 in framing the\n\nissue, it makes perfect sense that the Puerto Rico Supreme Court\n\nwould say (in the now-much discussed footnote) that \"in this case\"\n\n(meaning the Ramos Rivas case) one had to \"refer to [Article] 401\n\n. . . insofar as it concerns the penalty imposed.\" See 2007 TSPR\n\nat ___, 171 D.P.R. at ___, 2007 WL 2079844, at *1 n.1 (emphasis\n\nadded).8\n\n\n 7 According to Ramos Rivas, the CSA\n is a special law that provides that a certain type of\n conduct (such as violating [Article] 401 of said act and\n having two or more previous felony convictions under\n this act) [triggers] the recidivism provision of this\n law. In turn, the Penal Code contains a \"generic\"\n recidivism provision under which it penalizes those who\n have committed a felony and have two or more previous\n felony convictions, regardless of the statute they\n violated.\n2007 TSPR at ___, 171 D.P.R. at ___, 2007 WL 2079844, at *7\n(quotation marks omitted and second bracket in original).\n 8\n For those wondering what happened to the Ramos Rivas\ndefendant: The Puerto Rico Supreme Court concluded that the\n - 14 -\n\f Viewed against this backdrop, one thing is transparently\n\nclear: Despite what the government suggests, Ramos Rivas did not\n\nestablish a general rule that if a defendant pleads guilty to an\n\nArticle 406 attempt/conspiracy violation following an Article 401\n\npossession-with-intent-to-distribute charge, then it always means\n\nhe stands convicted of attempt/conspiracy to possess drugs with\n\ndistributive intent. Instead, Ramos Rivas is a narrow decision\n\nholding that in the idiosyncratic circumstances of that case, one\n\nhad to look to Article 401 given the parties' apparent agreement\n\nthat Article 401 was the substantive offense underlying the Article\n\n406 attempt/conspiracy conviction — and not some other article,\n\nlike Article 404. And that situation is worlds apart from\n\nMartínez's. Which undercuts the government's Ramos Rivas-based\n\ntheory.\n\n Still trying to convince us that \"Martínez's Article 406\n\nconviction was for the attempt/conspiracy to commit an Article 401\n\n\n\n\nspecific recidivist provision in Article 401 controlled over the\ngeneral recidivist provision in the Penal Code. 2007 TSPR at ___,\n171 D.P.R. at ___, 2007 WL 2079844, at *7-8. And noting that a\n\"sentence imposed under\" the Penal Code's recidivist provision \"is\nmore onerous than a sentence imposed under the\" CSA's recidivist\nprovision (because, for example, a sentence handed down under the\nPenal Code's recidivist provision \"does not qualify\" a defendant\n\"to receive credits\" for good conduct and the like), the high court\nrejected the Commonwealth's no-harm-no-foul argument and remanded\nfor resentencing. See 2007 TSPR at ___, 171 D.P.R. at ___, 2007\nWL 2079844, at *7-9.\n - 15 -\n\fviolation\" — namely, possessing heroin with intent to distribute\n\n— the government talks up two decisions by the Puerto Rico Circuit\n\nCourt of Appeals: Puerto Rico v. Ramírez Santiago, KLCE201701670,\n\n2017 WL 6884475 (P.R. Cir. Nov. 29, 2017) (certified translation\n\nprovided by the government), and Puerto Rico v. Collazo Ortiz,\n\nKLCE201700104, 2017 WL 1906428 (P.R. Cir. Mar. 30, 2017) (certified\n\ntranslation provided by the government). In both cases, the\n\ndefendants stood accused of violating Article 401; the charges got\n\nreclassified to Article 406 offenses, to which they pled guilty;\n\nand the intermediate appellate court rejected their claims that\n\ntheir sentences — 9 years in Ramírez Santiago, and 8 years in\n\nCollazo Ortiz — were too stiff, noting how the time they received\n\ndid not exceed the 20-year fixed penalty in Article 401. As in\n\nRamos Rivas, none of the parties in Ramírez Santiago or Collazo\n\nOrtiz disputed that Article 401 was the substantive offense\n\nunderlying the Article 406 attempt/conspiracy convictions. So\n\nRamírez Santiago and Collazo Ortiz are of no help to the\n\ngovernment.\n\n And there is more that cuts against the government's\n\nposition. Responding to other questions at oral argument, the\n\ngovernment's lawyer also conceded that Martínez could have pled\n\nguilty during the plea colloquy in the Puerto Rico case to an\n\nArticle 404 simple-possession offense, which could then serve as\n\n - 16 -\n\fthe substantive crime behind the Article 406 attempt/conspiracy\n\nconviction — even if Article 404 was not mentioned in the judgment\n\nof conviction. Given how Article 404 is not a \"controlled\n\nsubstance offense\" for guidelines purposes, see Román-Huertas, 848\n\nF.3d at 77, the government's concession is fatal to its defense of\n\nthe judge's work.\n\n Perhaps sensing the difficulties in his position, the\n\ngovernment's attorney added that while the plea colloquy might\n\n\"clarify\" what Martínez pled to, it also might not — we do not\n\nknow, because prosecutors did not provide the plea-colloquy\n\ntranscript at his federal-sentencing hearing. But this goes to\n\nshow only that the government has not met its burden of proving\n\nexactly what the substantive crime undergirding Martínez's Article\n\n406 conviction was.\n\n That leaves one matter the government presents on appeal\n\n— that we as a panel should use the Puerto Rico Supreme Court's\n\nopinion in Rosario Cintrón to overrule language in our Dávila-\n\nFélix opinion that Article 401 \"criminalizes actions . . . not\n\ncommonly considered drug trafficking offenses, such as concealment\n\nof a controlled substance.\" Assuming without deciding that the\n\ngovernment preserved the claim, given how the government-filed\n\npapers leave up in the air what offense Martínez pled guilty to\n\nattempting/conspiring to commit — simple possession under Article\n\n - 17 -\n\f404 is a possibility, as the government's lawyer confirmed at oral\n\nargument — we have no need to resolve the government's fallback\n\nArticle 401 argument today.\n\n Final Words\n\n To hammer the key point of our opinion home: The 3-year\n\nsuspended sentence Martínez got for his Puerto Rico drug conviction\n\nis at least equally consistent with his having pled to\n\nattempting/conspiring to commit simple drug possession (which,\n\ndon't forget, is not a \"controlled substance offense\" under the\n\nguidelines). And prosecutors never introduced the Puerto Rico\n\nplea colloquy to show that simple possession was not (in Article\n\n406 lingo) \"the object of the attempt or conspiracy.\" So ours is\n\na fact-specific holding, declaring that the government — in the\n\nparticular circumstances presented here — failed to shoulder its\n\nburden of showing what Martínez pled to, which requires us to\n\nvacate his sentence and remand for resentencing. We add a caveat,\n\nhowever. The government had every incentive — and opportunity —\n\nto present sufficient proof to support its requested \"controlled\n\nsubstance offense\" enhancement. But it did not do so, as we have\n\nseen. Thus the government may not present new evidence of\n\nMartínez's prior conviction at resentencing. See, e.g., Román-\n\nHuertas, 848 F.3d at 78.\n\n VACATED AND REMANDED, WITH INSTRUCTIONS.\n\n - 18 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361781/", "author_raw": "THOMPSON, Circuit Judge"}]}
LYNCH
THOMPSON
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584528/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Martinez-Benitez\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-24\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1393\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOSÉ G. MARTÍNEZ-BENÍTEZ,\n\n Defendant, Appellant.\n\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Lynch, Thompson, and Barron,\n Circuit Judges.\n\n\n\n Jóse Luis Novas-Debien for appellant.\n Jonathan L. Gottfried, Assistant United States Attorney, with\nwhom Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Julia M. Meconiates, Assistant United\nStates Attorney, were on brief, for appellee.\n\n\n\n\n January 24, 2019\n\f THOMPSON, Circuit Judge. At stake today is whether\n\nfederal prosecutors proved José Martínez Benítez's prior Puerto\n\nRico-law conviction (described below) is a \"controlled substance\n\noffense\" for federal-sentencing purposes. Concluding they did\n\nnot, we vacate his sentence and remand for resentencing consistent\n\nwith this opinion.\n\n How Martínez's Case Got Here1\n\n Martínez pled guilty in federal court to possessing a\n\nfirearm despite his status as a felon. See 18 U.S.C. § 922(g)(1).\n\nHis was a \"straight plea,\" meaning he and the government did not\n\nenter into any plea agreement. As for how things shook out at\n\nsentencing, this is what you need to know.2\n\n\n\n 1 According to Spanish naming conventions, if a person has\ntwo surnames, the first (which is the father's last name) is\nprimary and the second (which is the mother's maiden name) is\nsubordinate. Which is why we use \"Martínez\" for the rest of the\nopinion.\n 2 First, though, a quick heads-up for the lay readers out\nthere: Sentencing under the federal sentencing guidelines starts\nwith the base offense level — i.e., a point score for a specified\noffense or group of offenses. See, e.g., United States v. Serrano-\nMercado, 784 F.3d 838, 840 (1st Cir. 2015). The guidelines then\nmake adjustments for any aggravating or mitigating factors in the\ndefendant's case, thus arriving at a total offense level. See id.\nThe guidelines also assign points based on the defendant's criminal\nhistory — points that get converted into various criminal history\ncategories, designated by Roman numerals I through VI. Id. Armed\nwith this info, the judge turns to the guidelines's sentencing\ntable. Id. And by plotting the defendant's total offense level\nalong the table's vertical axis and his criminal history category\nalong the table's horizontal axis, the judge ends up with an\nadvisory prison range. Id. From there, the judge sees if any\n - 2 -\n\f The sentencing guidelines apply an enhanced base offense\n\nlevel of 20 for firearm offenses preceded by one felony conviction\n\nfor a \"controlled substance offense,\" see U.S.S.G.\n\n§ 2K2.1(a)(4)(A) — a phrase that pertinently covers a state-law\n\ncrime, \"punishable by imprisonment for a term exceeding one year,\n\nthat prohibits . . . the possession of a controlled substance . . .\n\nwith intent to . . . distribute,\" id. § 4B1.2(b); see also id.\n\n§ 2K2.1 cmt. n.1 (referring the reader to § 4B1.2(b) and its\n\naccompanying application note 1 for a definition of a \"[c]ontrolled\n\nsubstance offense\").3 And the phrase covers as well \"the offenses\n\nof aiding and abetting, conspiring, and attempting to commit such\n\noffenses.\" Id. § 4B1.2 cmt. n.1. Also of prime importance to the\n\npresent controversy, the government has \"the burden of\n\nestablishing\" by a preponderance of the evidence \"that a prior\n\n\ndepartures are called for, considers various sentencing factors,\nand determines what sentence (whether within, above, or below the\nsuggested range) seems appropriate. See, e.g., United States v.\nDávila-González, 595 F.3d 42, 46 (1st Cir. 2010).\n 3No one argues that Puerto Rico is unlike a state for\n§ 4B1.2(b) purposes. See generally United States v. Torres-Rosa,\n209 F.3d 4, 8 (1st Cir. 2000) (concluding that \"because the\n[defendant] had not shown\" that the guidelines \"'meant to exclude\nfelony convictions in Puerto Rico Commonwealth Courts for\nenhancement purposes,' no plain error inhered\" (quoting United\nStates v. Morales-Diaz, 925 F.2d 535, 540 (1st Cir. 1991));\nMorales-Diaz, 925 F.2d at 540 (rejecting the defendant's\nunpreserved suggestion that \"because Puerto Rico is not a state,\"\nthe Puerto Rico conviction in play there was not a state-law\noffense \"under § 4B1.2\" (internal quotation marks omitted)). So\nwe say no more about that subject.\n - 3 -\n\fconviction qualifies as a predicate offense for sentencing\n\nenhancement purposes.\" United States v. Dávila-Félix, 667 F.3d\n\n47, 55 (1st Cir. 2011); United States v. Bryant, 571 F.3d 147, 153\n\n(1st Cir. 2009).\n\n From the documents presented by prosecutors at\n\nsentencing, the district judge learned that years before his run-\n\nin with the feds, Puerto Rico authorities had charged Martínez\n\nwith knowingly or intentionally possessing heroin with intent to\n\ndistribute, in violation of Puerto Rico's Controlled Substances\n\nAct (\"CSA\"), see P.R. Laws Ann. tit. 24, § 2401 — a law commonly\n\ncalled \"Article 401.\" As relevant here, Article 401 criminalizes\n\nthe possession of certain controlled substances (including heroin)\n\nwith intent to \"manufacture, distribute, dispense, transport or\n\nconceal,\" see id. § 2401(a)(1), and calls for a \"fixed\" prison\n\n\"term\" of 20 years, which may be increased to a 30-year \"maximum\"\n\nterm or decreased to a 10-year \"minimum\" term, if \"aggravating\" or\n\n\"extenuating\" circumstances exist, see id. § 2401(b)(1)(A). We\n\nhave dealt with Article 401 before, for instance in an opinion\n\nholding that \"intent to conceal\" is \"a non-predicate offense\" under\n\n§ 4B1.2(b). See Dávila-Félix, 667 F.3d at 56 (concluding that\n\n\"concealment of a controlled substance\" is \"not commonly\n\nconsidered [a] drug trafficking offense[]\").\n\n\n\n - 4 -\n\f Anyway, Martínez pled guilty to a \"reclassified\" charge\n\nof \"attempt[ing] or conspir[ing] to commit\" an \"offense\" under\n\nPuerto Rico's CSA, see P.R. Laws Ann. tit. 24, § 2406 — a provision\n\ncolloquially called \"Article 406,\" the penalty for which \"shall\n\nnot exceed\" the penalty for the substantive \"offense\" that \"was\n\nthe object of the attempt or conspiracy.\" By doing so, he avoided\n\na fixed mandatory 20-year prison term and made himself eligible\n\nfor a suspended sentence. See P.R. Laws Ann. tit. 34, § 1027; see\n\nalso P.R. Laws Ann. tit. 24, § 2414.4 And ultimately, the Puerto\n\nRico court gave him a 3-year suspended sentence —— a sentence that\n\nhas special significance as to the nature of the offense.\n\n You should know too (because it affects the case's\n\noutcome, for reasons explained presently) that Puerto Rico's CSA\n\n\n\n 4 The first statute authorizes the Puerto Rico \"Court of First\nInstance\" to\n suspend the effect of the sentence of imprisonment in\n all cases of felonies . . . other than . . . [o]ne of\n the following felonies under the [CSA]: § 2401\n (prohibited acts); § 2405 (distribution to persons under\n eighteen . . . years of age); § 2411 (employment of\n minors); § 2411a (introduction of drugs to schools and\n institutions), all of Title 24.\nP.R. Laws Ann. tit. 34, § 1027(6). The second statute says that\n\"[t]he provisions on suspended sentence\" are not \"applicable to\"\npersons \"convicted of violating §§ 2401(a), 2405, 2411 and 2411a\nof this title when the distribution, sale, introduction,\ndispensing or possession and transportation for the purpose of\ndistribution is involved, except in those cases in which the\nprovisions of §§ 1042 and 1043 of Title 34 are applicable.\" P.R.\nLaws Ann. tit. 24, § 2414.\n - 5 -\n\fbans not only possession-with-intent-to-distribute offenses\n\ncovered by Article 401, but also (among other things) simple-\n\npossession offenses (i.e., offenses involving possession of drugs\n\nnot prescribed, with no intent to distribute), see P.R. Laws Ann.\n\ntit. 24, § 2404 — a law widely referred to as \"Article 404,\" which\n\noutlaws the knowing or intentional possession of \"any controlled\n\nsubstance, unless such substance was obtained directly, or\n\npursuant to a valid prescription or order from a practitioner,\n\nwhile acting in the course of his professional practice, or except\n\nas authorized by this chapter.\" Article 404 calls for a \"fixed\"\n\n3-year prison \"term,\" which may be increased to a 5-year \"maximum\"\n\nterm or decreased to a 2-year \"minimum\" term, if \"aggravating\" or\n\n\"extenuating\" circumstances exist. We are also no strangers to\n\nArticle 404 — just consider United States v. Román-Huertas, 848\n\nF.3d 72 (1st Cir. 2017), which holds that an Article 404 \"mere\n\npossession offense[]\" does not count as a qualifying predicate\n\nunder § 4B1.2(b). Id. at 77; see also United States v. Ramos-\n\nGonzález, 775 F.3d 483, 507 n.27 (1st Cir. 2015).\n\n Kicking off the sentencing in the federal case, the\n\ndistrict judge noted that while the charging document in the Puerto\n\nRico case listed Martínez's crime as an Article 401 possession-\n\nwith-intent-to-distribute offense, the judgment showed that he had\n\npled to an Article 406 attempt-or-conspiracy offense. Then relying\n\n - 6 -\n\fon a footnote in Puerto Rico v. Ramos Rivas, 2007 TSPR 138, 171\n\nD.P.R. 826, 2007 WL 2079844, at *1 n.1 (P.R. 2007) — which says\n\nthat if an Article 401 charge is reclassified as an Article 406\n\noffense, a court \"must refer\" back to Article 401 to determine the\n\nproper \"penalty\" — the judge ruled that Martínez's Article 406\n\nconviction was for an \"attempted conspiracy to distribute\n\ncontrolled substances.\"5 So the judge concluded that the Article\n\n406 conviction amounted to a \"controlled substance offense\" under\n\nthe guidelines and increased Martínez's base offense level\n\naccordingly — from 14 to 20, which helped set his recommended\n\nguidelines range at 30 to 37 months. And when all was said and\n\ndone, the judge sentenced him to 34 months in prison.\n\n Unhappy with this outcome, Martínez now appeals.\n\n Jurisdiction and Standard of Review\n\n The district judge had original jurisdiction under 18\n\nU.S.C. § 3231. We have appellate jurisdiction under 28 U.S.C.\n\n\n\n\n 5 The Ramos Rivas footnote reads in relevant part:\n [Article] 406 of the Puerto Rico Controlled Substances\n Act . . . punishes the attempt or conspiracy to commit\n any of the crimes defined in the act. The [article]\n refers to base offenses, the attempt or conspiracy to\n commit which gave rise to the sentence imposed.\n Consequently, in this case we must refer to [Article]\n 401 . . . insofar as it concerns the penalty imposed.\n - 7 -\n\f§ 1291. And we review the judge's legal analysis de novo, see\n\nDávila-Félix, 667 F.3d at 54, noting additional details as needed.\n\n Summary of the Parties' Main Arguments\n\n Attacking the district judge's work, Martínez contends\n\nthat none of the government-provided documents showed his Article\n\n406 conviction was for attempt/conspiracy to possess heroin with\n\nintent to distribute (with Article 401 being the object of the\n\nattempt/conspiracy), rather than, say, attempt/conspiracy to\n\npossess heroin without intent to distribute (with Article 404 being\n\nthe object of the attempt/conspiracy) — the first is a § 4B1.2-\n\nqualifying predicate, he quickly reminds us; the second is not.\n\nAs for the judge's reliance on Ramos Rivas, Martínez claims that\n\nthis decision has zero relevance because (in his words) Ramos Rivas\n\ndoes not hold that \"all Article 406 convictions . . . reclassified\n\nfrom Article 401 are drug trafficking offenses.\"\n\n The government, contrastingly, argues that the district\n\njudge got everything exactly right. Puerto Rico law, the\n\ngovernment writes, directs courts to \"tie\" a defendant's Article\n\n406 attempt/conspiracy conviction to a substantive \"base offense\"\n\nunder Puerto Rico's CSA \"to determine the fixed penalty\" and then\n\nto pick \"a penalty not to exceed that maximum.\" To help with this\n\ntask, the government continues, Ramos Rivas requires courts to\n\n\"refer[] to the offense in the charging document[]\" to discern the\n\n - 8 -\n\fsubstantive offense underlying an Article 406 conviction \"that\n\n[was] reclassified from [another] charge[].\" Putting these points\n\ntogether, the government repeats that Martínez's plea resulted\n\nfrom an Article 401 possession-with-intent-to-distribute charge\n\nthat got \"reclassified to Article 406.\" And given the charging\n\ndocument, the judge rightly ruled that Martínez's Article 406\n\nguilty-plea conviction was \"for attempting or conspiring to\n\npossess\" heroin \"with intent to distribute\" — or so the government\n\ninsists, noting too that Martínez's 3-year suspended sentence did\n\nnot \"exceed\" the pertinent 20-year maximum penalty in Article 401.\n\nErgo, the government concludes, the judge rightly found that\n\nMartínez's conviction was a § 4B1.2-qualifying predicate.\n\n As a fallback, the government contends that even if we\n\nthink Martínez pled guilty to attempting/conspiring to violate\n\nArticle 401 by means other than possessing heroin with distributive\n\nintent — like, for example, by possessing heroin with intent to\n\nconceal — we should still affirm his sentence. And that is\n\nbecause, in the government's view, even though our Dávila-Félix\n\nopinion says Article 401 \"criminalizes actions . . . not commonly\n\nconsidered drug trafficking offenses, such as concealment of a\n\ncontrolled substance,\" see 667 F.3d at 56, a Puerto Rico Supreme\n\nCourt case predating Dávila-Félix — Puerto Rico v. Rosario Cintrón,\n\n2 P.R. Offic. Trans. 107, 102 D.P.R. 82 (1974) — holds otherwise.\n\n - 9 -\n\fThus, according to the government, we as a panel must overrule\n\nDávila-Félix. Martínez, for his part, claims that the government\n\nwaived this argument by not raising it in the district court — a\n\ncontention the government disputes.\n\n Our Take\n\n To state the obvious, Martínez's federal sentence can\n\nstand only if his Article 406 attempt/conspiracy conviction\n\nconstitutes a controlled substance offense under the guidelines —\n\nan issue (we say again) that the government had the burden of\n\nproving. See Dávila–Félix, 667 F.3d at 55. As the parties agree,\n\nArticle 406 covers separate crimes with separate elements — some\n\nof which qualify as controlled substance offenses, like\n\nattempt/conspiracy to possess heroin with distributive intent; and\n\nothers of which do not, like attempt/conspiracy to possess heroin\n\nwithout distributive intent. See Román-Huertas, 848 F.3d at 77.\n\nSo, in legalese, Article 406 is a \"divisible\" statute. See Mathis\n\nv. United States, 136 S. Ct. 2243, 2249 (2016). Which means we\n\nmust apply what is called the \"modified categorical approach,\" a\n\nprocedure that lets judges look at a narrow set of documents from\n\na defendant's conviction — like \"the indictment, jury\n\ninstructions, or plea agreement and colloquy\" — to see what crime\n\nhe committed. Id. (citing Shepard v. United States, 544 U.S. 13,\n\n\n\n - 10 -\n\f26 (2005), and Taylor v. United States, 495 U.S. 575, 602 (1990));\n\nsee also Román-Huertas, 848 F.3d at 77.\n\n Back again then to the government-filed papers. The\n\ncharging document in Martínez's Puerto Rico case accused him of\n\npossessing heroin with intent to distribute, in violation of\n\nArticle 401. And the sentencing document shows he later pled\n\nguilty to an Article 406 attempt/conspiracy crime, reclassified\n\nfrom the Article 401 charge. Unfortunately for us, however, the\n\ndocuments do not say what he pled guilty to attempting/conspiring\n\nto do: possessing heroin with intent to distribute (an Article\n\n401 substantive offense), perhaps — a qualifying predicate under\n\n§ 4B1.2; or perhaps possessing heroin without intent to distribute\n\n(an Article 404 substantive offense) — a non-qualifying predicate\n\nunder § 4B1.2. And that failure devastates the government's theory\n\nhere, as we now explain.\n\n The 3-year suspended sentence Martínez received is\n\ncertainly consistent with his having pled to attempting/conspiring\n\nto possess heroin without distributive intent. But it is equally\n\nconsistent with his having pled to attempting/conspiring to\n\npossess heroin with distributive intent. We say that because the\n\n3-year suspended sentence does not exceed the pertinent maximum\n\npenalties under Article 404 and Article 401. Remember: Article\n\n404 calls for a \"fixed\" 3-year prison \"term\" for simple possession\n\n - 11 -\n\f(which the court can raise to a 5-year \"maximum\" term or drop to\n\na 2-year \"minimum\" term, if \"aggravating\" or \"extenuating\" factors\n\nexist). See P.R. Laws Ann. tit. 24, § 2404. And Article 401 calls\n\nfor a \"fixed\" prison \"term\" of 20 years for (among other things)\n\npossession with intent to distribute (which the court can raise to\n\na 30-year \"maximum\" term or drop to a 10-year \"minimum\" term, if\n\n\"aggravating\" or \"extenuating\" circumstances exist). See P.R.\n\nLaws Ann. tit. 24, § 2401.\n\n Hoping to get to the bottom of things, we asked the\n\ngovernment's lawyer at oral argument if a defendant charged with\n\nan Article 401 possession-with-intent-to-distribute offense could\n\ncop to an Article 404 simple-possession offense, which could then\n\nserve as the substantive offense underlying an Article 406\n\nattempt/conspiracy guilty-plea conviction. Yes, the lawyer said.6\n\nWhich makes sense given that \"[d]efendants are frequently charged\n\nfor crimes different from those they are ultimately convicted of.\"\n\nSee United States v. Bravo-García, No. 16-1258, slip op. at 3 (1st\n\nCir. July 10, 2017) (judgment). And based on this truism, we have\n\n\n\n\n 6\n Possession without distributive intent is a lesser-included\noffense of possession with distributive intent — a point the\ngovernment does not dispute. See generally Ramos-González, 775\nF.3d at 507 (mentioning how a \"police complaint\" accused a\ndefendant of possessing cocaine with distributive intent, \"a\nviolation of Article 401,\" but the defendant later pled \"guilty to\na [simple] possession crime\" under \"Article 404\").\n - 12 -\n\fsaid that a sentencing order \"stating that [the defendant's]\n\nArticle 406 offense was 'reclassified' from Article 401, on its\n\nown, . . . fails to justify a finding that [her] conviction is\n\nactually under Article 401\" instead of some other article. See\n\nid., slip. op. at 2 n.3.\n\n Seeking a way around these obstacles, the government's\n\nattorney basically fell back on an argument made in his brief:\n\ni.e., that because Martínez pled guilty to an Article 406\n\nattempt/conspiracy crime, reclassified from an Article 401\n\npossession-with-intent-to-distribute charge, then under Ramos\n\nRivas the Article 401 offense is considered the \"object\" of the\n\nattempt or conspiracy — meaning, at least according to the\n\ngovernment, Martínez pled guilty to attempting/conspiring to\n\npossess a controlled substance with intent to distribute, which\n\nmakes his Article 406 conviction a qualifying predicate offense\n\nfor a guidelines enhancement. But the government reads way too\n\nmuch into Ramos Rivas.\n\n Charged with violating Article 401 by possessing cocaine\n\nwith distributive intent, the Ramos Rivas defendant pled guilty to\n\ninfracting Article 406. See 2007 TSPR at ___, 171 D.P.R. at ___,\n\n2007 WL 2079844, at *1. Noting that she had two prior Article 404\n\nconvictions, the lower court imposed a 20-year sentence under a\n\nrecidivist statute in Puerto Rico's Penal Code. Id. Displeased,\n\n - 13 -\n\fthe defendant argued on appeal that because her earlier convictions\n\nwere for violating Puerto Rico's CSA, the court should have instead\n\nsentenced her under the less-onerous recidivist provision in\n\nArticle 401 of the CSA. See 2007 TSPR at ___, 171 D.P.R. at ___,\n\n2007 WL 2079844, at *1-2.7 The Commonwealth's position was\n\nessentially no harm, no foul because the sentence fell \"within the\n\nparameters\" of Article 401's recidivist provision. See 2007 TSPR\n\nat ___, 171 D.P.R. at ___, 2007 WL 2079844, at *7. Given the Ramos\n\nRivas parties' laser-like focus on Article 401 in framing the\n\nissue, it makes perfect sense that the Puerto Rico Supreme Court\n\nwould say (in the now-much discussed footnote) that \"in this case\"\n\n(meaning the Ramos Rivas case) one had to \"refer to [Article] 401\n\n. . . insofar as it concerns the penalty imposed.\" See 2007 TSPR\n\nat ___, 171 D.P.R. at ___, 2007 WL 2079844, at *1 n.1 (emphasis\n\nadded).8\n\n\n 7 According to Ramos Rivas, the CSA\n is a special law that provides that a certain type of\n conduct (such as violating [Article] 401 of said act and\n having two or more previous felony convictions under\n this act) [triggers] the recidivism provision of this\n law. In turn, the Penal Code contains a \"generic\"\n recidivism provision under which it penalizes those who\n have committed a felony and have two or more previous\n felony convictions, regardless of the statute they\n violated.\n2007 TSPR at ___, 171 D.P.R. at ___, 2007 WL 2079844, at *7\n(quotation marks omitted and second bracket in original).\n 8\n For those wondering what happened to the Ramos Rivas\ndefendant: The Puerto Rico Supreme Court concluded that the\n - 14 -\n\f Viewed against this backdrop, one thing is transparently\n\nclear: Despite what the government suggests, Ramos Rivas did not\n\nestablish a general rule that if a defendant pleads guilty to an\n\nArticle 406 attempt/conspiracy violation following an Article 401\n\npossession-with-intent-to-distribute charge, then it always means\n\nhe stands convicted of attempt/conspiracy to possess drugs with\n\ndistributive intent. Instead, Ramos Rivas is a narrow decision\n\nholding that in the idiosyncratic circumstances of that case, one\n\nhad to look to Article 401 given the parties' apparent agreement\n\nthat Article 401 was the substantive offense underlying the Article\n\n406 attempt/conspiracy conviction — and not some other article,\n\nlike Article 404. And that situation is worlds apart from\n\nMartínez's. Which undercuts the government's Ramos Rivas-based\n\ntheory.\n\n Still trying to convince us that \"Martínez's Article 406\n\nconviction was for the attempt/conspiracy to commit an Article 401\n\n\n\n\nspecific recidivist provision in Article 401 controlled over the\ngeneral recidivist provision in the Penal Code. 2007 TSPR at ___,\n171 D.P.R. at ___, 2007 WL 2079844, at *7-8. And noting that a\n\"sentence imposed under\" the Penal Code's recidivist provision \"is\nmore onerous than a sentence imposed under the\" CSA's recidivist\nprovision (because, for example, a sentence handed down under the\nPenal Code's recidivist provision \"does not qualify\" a defendant\n\"to receive credits\" for good conduct and the like), the high court\nrejected the Commonwealth's no-harm-no-foul argument and remanded\nfor resentencing. See 2007 TSPR at ___, 171 D.P.R. at ___, 2007\nWL 2079844, at *7-9.\n - 15 -\n\fviolation\" — namely, possessing heroin with intent to distribute\n\n— the government talks up two decisions by the Puerto Rico Circuit\n\nCourt of Appeals: Puerto Rico v. Ramírez Santiago, KLCE201701670,\n\n2017 WL 6884475 (P.R. Cir. Nov. 29, 2017) (certified translation\n\nprovided by the government), and Puerto Rico v. Collazo Ortiz,\n\nKLCE201700104, 2017 WL 1906428 (P.R. Cir. Mar. 30, 2017) (certified\n\ntranslation provided by the government). In both cases, the\n\ndefendants stood accused of violating Article 401; the charges got\n\nreclassified to Article 406 offenses, to which they pled guilty;\n\nand the intermediate appellate court rejected their claims that\n\ntheir sentences — 9 years in Ramírez Santiago, and 8 years in\n\nCollazo Ortiz — were too stiff, noting how the time they received\n\ndid not exceed the 20-year fixed penalty in Article 401. As in\n\nRamos Rivas, none of the parties in Ramírez Santiago or Collazo\n\nOrtiz disputed that Article 401 was the substantive offense\n\nunderlying the Article 406 attempt/conspiracy convictions. So\n\nRamírez Santiago and Collazo Ortiz are of no help to the\n\ngovernment.\n\n And there is more that cuts against the government's\n\nposition. Responding to other questions at oral argument, the\n\ngovernment's lawyer also conceded that Martínez could have pled\n\nguilty during the plea colloquy in the Puerto Rico case to an\n\nArticle 404 simple-possession offense, which could then serve as\n\n - 16 -\n\fthe substantive crime behind the Article 406 attempt/conspiracy\n\nconviction — even if Article 404 was not mentioned in the judgment\n\nof conviction. Given how Article 404 is not a \"controlled\n\nsubstance offense\" for guidelines purposes, see Román-Huertas, 848\n\nF.3d at 77, the government's concession is fatal to its defense of\n\nthe judge's work.\n\n Perhaps sensing the difficulties in his position, the\n\ngovernment's attorney added that while the plea colloquy might\n\n\"clarify\" what Martínez pled to, it also might not — we do not\n\nknow, because prosecutors did not provide the plea-colloquy\n\ntranscript at his federal-sentencing hearing. But this goes to\n\nshow only that the government has not met its burden of proving\n\nexactly what the substantive crime undergirding Martínez's Article\n\n406 conviction was.\n\n That leaves one matter the government presents on appeal\n\n— that we as a panel should use the Puerto Rico Supreme Court's\n\nopinion in Rosario Cintrón to overrule language in our Dávila-\n\nFélix opinion that Article 401 \"criminalizes actions . . . not\n\ncommonly considered drug trafficking offenses, such as concealment\n\nof a controlled substance.\" Assuming without deciding that the\n\ngovernment preserved the claim, given how the government-filed\n\npapers leave up in the air what offense Martínez pled guilty to\n\nattempting/conspiring to commit — simple possession under Article\n\n - 17 -\n\f404 is a possibility, as the government's lawyer confirmed at oral\n\nargument — we have no need to resolve the government's fallback\n\nArticle 401 argument today.\n\n Final Words\n\n To hammer the key point of our opinion home: The 3-year\n\nsuspended sentence Martínez got for his Puerto Rico drug conviction\n\nis at least equally consistent with his having pled to\n\nattempting/conspiring to commit simple drug possession (which,\n\ndon't forget, is not a \"controlled substance offense\" under the\n\nguidelines). And prosecutors never introduced the Puerto Rico\n\nplea colloquy to show that simple possession was not (in Article\n\n406 lingo) \"the object of the attempt or conspiracy.\" So ours is\n\na fact-specific holding, declaring that the government — in the\n\nparticular circumstances presented here — failed to shoulder its\n\nburden of showing what Martínez pled to, which requires us to\n\nvacate his sentence and remand for resentencing. We add a caveat,\n\nhowever. The government had every incentive — and opportunity —\n\nto present sufficient proof to support its requested \"controlled\n\nsubstance offense\" enhancement. But it did not do so, as we have\n\nseen. Thus the government may not present new evidence of\n\nMartínez's prior conviction at resentencing. See, e.g., Román-\n\nHuertas, 848 F.3d at 78.\n\n VACATED AND REMANDED, WITH INSTRUCTIONS.\n\n - 18 -\n[END_CASE]", "role": "user" } ]
4,584,530
Jose M. ALVARADO, Petitioner, v. Matthew WHITAKER, Acting United States Attorney General, Respondent.
Alvarado v. Whitaker
2019-01-24
17-1572P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Lipez, Thompson", "parties": "", "opinions": [{"author": "LIPEZ, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n No. 17-1572\n\n JOSE M. ALVARADO,\n\n Petitioner,\n\n v.\n\n MATTHEW WHITAKER,*\n ACTING UNITED STATES ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF\n THE BOARD OF IMMIGRATION APPEALS\n\n\n Before\n Torruella, Lipez, and Thompson,\n Circuit Judges.\n\n\n Matthew S. Cameron for petitioner.\n Paul F. Stone, Senior Counsel for National Security Unit,\nOffice of Immigration Litigation, Civil Division, U.S. Department\nof Justice, with whom Chad A. Readler, Principal Deputy Assistant\nAttorney General, Civil Division, and Ethan B. Kanter, Acting\nChief, National Security Unit, Office of Immigration Litigation,\nwere on brief, for respondent.\n Sayoni Maitra, Karen Musalo, Eunice Lee, and Center for Gender\n& Refugee Studies were on brief for amicus curiae Center for Gender\n& Refugee Studies.\n\n\n January 24, 2019\n\n\n * Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions III as the respondent.\n\f LIPEZ, Circuit Judge. This case requires us to decide,\n\nas a question of first impression for our court, whether the\n\n\"persecutor bar\" -- which disqualifies certain persons from\n\nimmigration relief -- applies to an applicant who assisted or\n\nparticipated in persecution but acted without a personal motive to\n\ndo so. The petitioner in this case, Jose Alvarado, is a Salvadoran\n\nnative and citizen who concedes standing guard for his superiors\n\nwhile they engaged in an act of persecution. He denies, however,\n\nthat he shared their motive to persecute.\n\n An immigration judge (\"IJ\") granted Alvarado\n\ncancellation of removal under the Nicaraguan Adjustment and\n\nCentral American Relief Act (\"NACARA\") after concluding that the\n\npersecutor bar does not apply to Alvarado because he lacked a\n\nmotive to persecute. The Board of Immigration Appeals (\"BIA\")\n\nreversed the IJ's order, finding the persecutor bar applicable\n\ndespite the absence of such a motive.\n\n Alvarado seeks review of the decision of the BIA. After\n\ncareful consideration, we hold that a motive to persecute by an\n\napplicant who assisted or otherwise participated in persecution is\n\nnot required for application of the persecutor bar. Accordingly,\n\nwe deny Alvarado's petition.\n\n\n\n\n - 2 -\n\f I.\n\nA. Factual Background\n\n We draw the following facts from Alvarado's testimony\n\nbefore the IJ, which the IJ found to be credible.1 From 1981 to\n\n1984, during El Salvador's Civil War, Alvarado served in the\n\nSalvadoran National Guard (the \"National Guard\"), which he joined\n\n\"out of economic necessity\" because of the lack of employment\n\nopportunities. As a member of the National Guard, Alvarado \"could\n\nearn enough . . . to just get by.\"\n\n Alvarado's role in the National Guard was to patrol and\n\nprovide security. The specific incident at issue here occurred\n\nwhen Alvarado was patrolling a town. Alvarado stopped a man and\n\nasked him for identification. He then began to question the man.\n\nAlvarado's supervisors soon arrived at the scene, took over the\n\nquestioning, and eventually moved the man to a different location\n\nfor interrogation as a suspected guerilla. During the\n\ninterrogation, Alvarado stood guard while his superiors hit the\n\nman and placed needles under his fingernails.2\n\n\n 1The IJ noted \"inconsistencies\" in Alvarado's testimony,\nparticularly in his description of the incident at issue. However,\nthe IJ credited Alvarado's explanation for the inconsistencies:\nanxiety, depression, and Post-Traumatic Stress Disorder, causing\nmemory loss, confusion, and nervousness.\n 2Alvarado testified inconsistently as to what he saw or how\nmany interrogations he witnessed. At one point, he testified that\nhe did not witness the interrogation of any suspected guerillas by\nhis superiors. At another point, he testified that he provided\nsecurity for at least five interrogations, including the incident\n\n\n - 3 -\n\fB. Applicable Law\n\n NACARA provides, in relevant part, that Salvadoran\n\ncitizens living in the United States are eligible for various forms\n\nof immigration benefits and relief from deportation, including\n\n\"Special Rule Cancellation of Removal,\" if they meet certain\n\nrequirements. See 8 U.S.C. § 1229b. However, a person otherwise\n\neligible for cancellation of removal under NACARA is ineligible if\n\nhe \"ordered, incited, assisted, or otherwise participated in the\n\npersecution of an individual because of the individual's race,\n\nreligion, nationality, membership in a particular social group, or\n\npolitical opinion.\" 8 U.S.C. § 1231(b)(3)(B)(i) (emphasis added).\n\nThis restriction is referred to as the \"persecutor bar.\"\n\n We have noted that, although the persecutor bar has a\n\n\"smooth surface,\" beneath it \"lie a series of rocks\" creating\n\ninterpretive problems, including \"the nature of the acts and\n\nmotivations that comprise persecution, the role of scienter,\n\nwhether and when inaction may suffice, and the kind of connection\n\nwith persecution by others that constitutes 'assistance.'\"\n\n\n\n\nwhen he witnessed his superiors hit and put needles under the\nfingernails of a man he had detained. From Alvarado's varying\ntestimony, the IJ concluded that \"roughly five times . . .\n[Alvarado's] superiors took an individual from [Alvarado's]\ncustody\" and \"on one of those occasions [Alvarado] witness[ed] his\nsuperiors place needles under a detainee's nails during an\ninterrogation.\" The IJ relied on this single incident to find\nthat Alvarado had participated in persecutory conduct.\n\n\n - 4 -\n\fCastañeda-Castillo v. Gonzales, 488 F.3d 17, 20 (1st Cir. 2007)\n\n(en banc).\n\n In Castañeda-Castillo, we addressed one of these\n\ninquiries -- the role of scienter. See id. That case concerned\n\nan applicant for asylum who had participated in a military\n\noperation during which civilian villagers were massacred. See id.\n\nat 19. The applicant testified that, although his military unit\n\nparticipated in the operation, his squad was located miles away\n\nfrom the site of the massacre, and he had no knowledge of the\n\nmassacre until three weeks after it had occurred. Id. Because\n\nCastañeda testified that he had no prior or contemporaneous\n\nknowledge of the village massacre, relief under NACARA hinged on\n\nwhether the persecutor bar may apply to an alien whose conduct had\n\nthe \"objective effect\" of aiding persecution but who had no prior\n\nor contemporaneous knowledge of the persecution. Id. at 20.\n\nAnswering only this question, we held the persecutor bar\n\n\"presumptively\" inapplicable to an applicant who had no prior or\n\ncontemporaneous knowledge of the persecution.3 Id. at 22. We\n\nreasoned that such an interpretation was consistent with the\n\nmeaning of the term persecution, which \"strongly implies both\n\nscienter and illicit motivation,\" and common sense notions of\n\n\n 3We noted there may be \"gray-area cases where less than full\nand detailed knowledge may suffice\" for the persecutor bar to\napply, such as \"cases of willful blindness or strong suspicions.\"\nCastañeda-Castillo, 488 F.3d at 21.\n\n\n - 5 -\n\fculpability, which dictate that a person is not accountable for\n\nwrongdoing of which he has no knowledge. Id. at 20.\n\nC. The IJ's Decision\n\n Before the IJ, the government, citing Castañeda-\n\nCastillo, argued that the persecutor bar applied to Alvarado\n\nbecause he knowingly assisted or participated in the persecution\n\nof an individual because of that individual's political opinions.\n\nIn turn, Alvarado, also citing Castañeda-Castillo, pointed to our\n\nstatement there that \"'persecution' strongly implies both scienter\n\nand illicit motivation,\" id. at 20, and contended that the bar was\n\ninapplicable to him because our precedent made persecutory motive\n\na prerequisite for application of the bar.\n\n In a written decision, the IJ found the persecutor bar\n\ninapplicable. Although the IJ found that Alvarado knowingly4\n\nparticipated in the persecution of the detainee, she cited the\n\n\"illicit motivation\" language in Castañeda-Castillo, and found\n\nthat Alvarado's actions did not amount to \"persecution\" because\n\nAlvarado was not personally motivated by the victim's political\n\nbeliefs. She credited Alvarado's testimony that \"he captured\n\ndetainees on the orders of his superiors as a consequence of his\n\n\n\n 4 In support of the conclusion that Alvarado had prior or\ncontemporaneous knowledge, the IJ cited the closing argument of\ncounsel for Alvarado at the hearing, where counsel stated that\nAlvarado's \"testimony establishes contemporaneous knowledge.\"\nIt is not clear whether Alvarado conceded prior knowledge.\n\n\n - 6 -\n\femployment,\" and found that his actions were not motivated by a\n\ndesire to persecute a detained guerilla on account of his political\n\nbeliefs.\n\n After finding that Alvarado met NACARA's remaining\n\nrequirements, the IJ granted him special rule cancellation of\n\nremoval.\n\nD. The BIA's Decision\n\n In an appeal to the BIA, the government argued that the\n\npersecutor bar applies to Alvarado and that persecutory motive is\n\nnot required for application of the bar to an individual who\n\nassisted or otherwise participated in the persecution. The BIA,\n\nnoting that Alvarado \"does not contest that he 'assisted' his\n\nsuperiors' actions and that their acts were committed on account\n\nof the victim's political opinion,\" or that he had \"'prior or\n\ncontemporaneous knowledge'\" of those acts,5 framed the critical\n\nquestion in this case as whether Alvarado \"was required to have a\n\n\n 5 Although Alvarado contends in his petition for review to us\nthat he has always contested whether he \"assisted . . . or\notherwise participated\" in the interrogation tactics of his\nsuperiors, Alvarado did not address this question before the BIA.\nNor did he dispute the IJ's finding that he had prior or\ncontemporaneous knowledge. Indeed, in his brief to the BIA, he\nconceded that this element was met because he \"witnessed the acts.\"\nAlvarado cannot \"leapfrog over the BIA\" by raising these arguments\nnow. Ramirez-Matias v. Holder, 778 F.3d 322, 327 (1st Cir. 2015).\nIn immigration cases, \"a failure to present developed\nargumentation to the BIA on a particular theory amounts to a\nfailure to exhaust administrative remedies as to that theory.\"\nId. Accordingly, we lack jurisdiction to review his claims\nconcerning assistance and knowledge. See 8 U.S.C. § 1252(d)(1).\n\n\n - 7 -\n\fpersecutory motive when he assisted in the persecution of the\n\ndetainee.\"\n\n The BIA emphasized NACARA's plain language barring\n\nrelief for an alien who \"assisted . . . in the persecution of an\n\nindividual because of the individual's . . . political opinion.\"\n\n8 U.S.C. § 1231(b)(3)(B)(i). The BIA reasoned that the phrase\n\n\"because of\" in the statute is best read to refer to the motivation\n\nof the persecutors -- not that of the alien-applicant who assisted\n\nthe persecutors. Matter of J.M. Alvarado, 27 I. & N. Dec. 27, 29\n\n(BIA 2017) (citing Bah v. Ashcroft, 341 F.3d 348, 351 (5th Cir.\n\n2003)). The BIA concluded that, if Alvarado participated in\n\npersecution that occurred because of an individual's political\n\nopinions, his personal motivation was irrelevant to the\n\napplication of the persecutor bar. Because it was undisputed that\n\nthe conduct of Alvarado's superiors was based on the victim's\n\npolitical opinion, the BIA held that the persecutor bar applied to\n\nAlvarado, precluding NACARA relief. The BIA accordingly ordered\n\nAlvarado removed to El Salvador.\n\n II.\n\n Because the BIA has conducted its own analysis, \"we focus\n\nour review on the decision of the BIA.\" Gonzalez v. Holder, 673\n\nF.3d 35, 38 (1st Cir. 2012). Our review of a decision invoking\n\nspecial rule cancellation of removal under NACARA is limited to\n\n\"constitutional claims and questions of law.\" Gonzalez-Ruano v.\n\n\n - 8 -\n\fHolder, 662 F.3d 59, 63 (1st Cir. 2011). Here, we are presented\n\nwith a legal question, i.e., the meaning of the persecutor bar.\n\nWe review the BIA's legal conclusions de novo. McCreath v. Holder,\n\n573 F.3d 38, 41 (1st Cir. 2009).\n\n Alvarado argues that Castañeda-Castillo controls the\n\noutcome of this case, citing our discussion of the meaning of\n\n\"persecution\" in that decision, where we said \"the term\n\n'persecution' strongly implies both scienter and illicit\n\nmotivation.\" See 488 F.3d at 20. However, Alvarado is wrong about\n\nthe import of the \"illicit motivation\" language for two reasons.\n\nFirst, although we said in Castañeda-Castillo that \"the term\n\n'persecution' strongly implies both scienter and illicit\n\nmotivation,\" that decision focused on the role of knowledge in the\n\npersecutor bar, not on motive. See id.; see also id. at 22 (\"This\n\nwould be a different case if the evidence clearly established that\n\nCastañeda had guilty knowledge[.]\"); cf. Negusie v. Holder, 555\n\nU.S. 511, 528 (2009)(Scalia, J., concurring) (finding no reason\n\nwhy the BIA cannot consider questions of knowledge \"separate and\n\napart\" from questions of motive). Castañeda conceded that \"had\n\n[he] been aware in advance of a plan to murder civilians, his role\n\n. . . could be treated as culpable assistance.\" Castañeda-\n\nCastillo, 488 F.3d at 20. For this reason, we addressed only the\n\n\"narrow[]\" inquiry of \"whether the persecutor bar would apply to\n\n\n\n\n - 9 -\n\fCastañeda if he had no prior or contemporaneous knowledge of the\n\nmurder of civilians.\" Id. at 20 (emphasis added).\n\n Second, the language Alvarado cites concerns the meaning\n\nof \"persecution,\" rather than \"assist[ance]\" or \"participat[ion].\"\n\nSee id. at 20 (describing persecution as \"impl[ying] both scienter\n\nand illicit motivation\"); id. at 20 n.1 (citing Random House\n\nDictionary of the English Language (2d ed. unabr. 1987) (\"The\n\ndictionary defines 'persecute' as 'to pursue with harassing or\n\noppressive treatment, esp. because of religion, race, or\n\nbeliefs[.]'\")). Plainly, persecution requires illicit motivation,\n\nas the persecutor bar itself requires. See 8 U.S.C. §\n\n1231(b)(3)(B)(i) (requiring that persecution be on account of\n\n\"race, religion, nationality, membership in a particular social\n\ngroup, or political opinion\"). Hence, there is nothing at all\n\nsurprising about the reference in Castañeda-Castillo to illicit\n\nmotive when discussing the meaning of persecution, even though the\n\nquestion of the motive of the persecution was never at issue.\n\nRather, the question was the link between knowledge and culpability\n\nwithin the meaning of the persecutor bar.\n\n Now faced with the question of the link between motive\n\nand culpability, we agree with the BIA that the persecutor bar\n\napplies to an alien who knowingly and willingly aided in\n\npersecution, but did so without a persecutory motivation. First,\n\nas the BIA explained, the syntax of the persecutor bar supports\n\n\n - 10 -\n\fthe agency's interpretation. The statute bars from relief an alien\n\nwho \"ordered, incited, assisted, or otherwise participated\" in\n\n\"persecution . . . because of\" enumerated protected grounds. As\n\na general rule, a modifier -- that is, a word or clause that limits\n\nor adds to the meaning of another word -- is adjacent to the word\n\nit modifies or describes.6 See Jane Straus, et al., The Blue Book\n\nof Grammar and Punctuation 23 (\"Place descriptive words and phrases\n\nas close as is practical to the words they modify.\") (11th Ed.\n\n2014). Thus, here, \"because of\" modifies \"persecution,\"\n\nindicating that the pertinent inquiry is whether the persecution\n\nwas motivated by protected grounds. By contrast, no such\n\nlimitation is attached to the actions of the person who assists.\n\nRather, the persecutor bar by its terms applies to any \"alien who\n\n. . . assisted, or otherwise participated\" in the persecutory\n\nconduct. Consequently, the structure of the subsection indicates\n\nthat, although the persecutors must be motivated by a protected\n\nground, the participation of the alien need not be so motivated.\n\n\n\n\n 6To demonstrate, consider the two sentences: (1) Mary saw\nthe dog that used to be hers behind the house. (2) Mary saw the\ndog behind the house that used to be hers. In the first sentence,\n\"that used to be hers\" modifies \"dog,\" indicating that the dog was\nformerly Mary's. In the second sentence, \"that used to be hers\"\nmodifies \"house,\" indicating that Mary had formerly owned the\nhouse.\n\n\n - 11 -\n\fSee Bah, 341 F.3d at 351 (employing similar reasoning);7 accord\n\nSingh v. Gonzales, 417 F.3d 736, 740 (7th Cir. 2005).\n\n Second, Alvarado relies on a much too narrow view of\n\nculpability. A person who knowingly and voluntarily8 participates\n\nin persecution is sufficiently culpable to be held accountable\n\nunder the persecutor bar.9 To hold otherwise, would create\n\n\n 7\n In its decision, the BIA cited Bah, 341 F.d at 351, as\nconsistent with its decision. See Matter of J.M. Alvarado, 27 I.\n& N. Dec. 27, 29 (BIA 2017). Alvarado contends that this reliance\nwas error because Bah is no longer good law in light of Negusie v.\nHolder, 555 U.S. 511 (2009). We disagree that Bah is no longer\ngood law. In Negusie, the Court held its interpretation of the\nDisplaced Person Act does not compel an interpretation of identical\nlanguage in the persecutor bar. See id. at 519-20. Bah did not\nfind its interpretation of the persecutor bar to be compelled.\nSee 341 F.3d at 351.\n 8\n This decision does not preclude an applicant from raising a\nwell-developed argument that he or she knowingly aided in\npersecution but did so only because of duress or coercion. Cf.\nNegusie, 555 U.S. at 515 (concerning alien who, at the command of\nsuperior officers, assisted in persecution but did so only under\nduress). Alvarado has never made such an argument.\n 9\n Alvarado contends that decisions of the Second, Fourth,\nEighth, and Ninth Circuits all support his view of the persecutor\nbar. But the cases cited by Alvarado do not interpret the\npersecutor bar to require illicit motive to persecute; rather,\nthey are in accordance with this court's decision in Castañeda-\nCastillo, requiring culpable knowledge. See Quitanilla v. Holder,\n758 F.3d 570 (4th Cir. 2014) (requiring some level of \"culpable\nknowledge\"); Parlak v. Holder, 578 F.3d 457, 470 (6th Cir. 2009)\n(finding petitioner acted \"voluntarily and knowingly\"); Xu Sheng\nGao v. U.S. Atty. Gen., 500 F.3d 93, 103 (2d Cir. 2007) (requiring\n\"culpable knowledge\"); Xie v. I.N.S., 434 F.3d 136, 144 (2d Cir.\n2006) (culpability established by awareness). Alvarado also cites\nseveral cases that discuss what conduct constitutes \"assistance.\"\nSee Hernandez v. Reno, 258 F.3d 806, 813-15 (8th Cir. 2001);\nMiranda-Alvarado v. Gonzales, 449 F.3d 915, 925-30. These cases\nlikewise do not address the issue of motivation. Alvarado cites\nno cases supporting the view that the persecutor bar requires a\n\n\n - 12 -\n\fanomalous results. For instance, under Alvarado's view of the\n\npersecutor bar, an alien applicant who repeatedly and voluntarily\n\nbussed innocent Sikhs to a police station, knowing they would be\n\nbeaten, see Singh, 417 F.3d at 740, would bear no responsibility\n\nunder the bar -- no matter how brutal the police's conduct -- as\n\nlong as he did so for a reason other than a personal motive to\n\npersecute.\n\n That result would also be contrary to common notions of\n\nculpability, which dictate that a person is responsible when she\n\nacts knowingly and voluntarily. Although this is not a criminal\n\ncase, principles of criminal law illustrate the point. Motive is\n\ngenerally not an element of a criminal offense unless specifically\n\nstated. See Jerome Hall, General Principles of Criminal Law 88\n\n(2d ed. 1960) (\"[H]ardly any part of penal law is more definitely\n\nsettled than that motive is irrelevant.\"); James Fitzjames\n\nStephen, 3 A History of the Criminal Law of England 18 (1883)\n\n(\"[T]he motives of the offender ought never . . . enter into the\n\ndefinition of an offence . . . because they do not affect the\n\npublic danger or actual mischief of the crimes which they cause.\");\n\nsee also United States v. White, 766 F.2d 22, 24 (1st Cir. 1985)\n\n(\"[E]vidence of a 'good' motive for violating the law is\n\nirrelevant[.]\").\n\n\nfinding of illicit motive to persecute on the part of the alien\nwho assists or otherwise participates in the persecution.\n\n\n - 13 -\n\f Finally, Alvarado contends that reading the persecutor\n\nbar to apply to aliens who did not share the illicit motive to\n\npersecute contravenes the purpose of the persecutor bar and asylum\n\nlaw generally. To the contrary, applying the persecutor bar to a\n\nperson who knowingly and voluntarily participated in persecution\n\nis a policy choice consistent with a body of law that was designed\n\nto shelter the persecuted.\n\n III.\n\n In sum, the persecutor bar does not require a showing\n\nthat the alien shared the motive of the persecutors whom he\n\nassisted. This interpretation of the bar is consistent with the\n\nplain language of the statute, our precedent, the decisions of\n\nother courts, and common notions of culpability. Accordingly, the\n\npetition for review is denied.\n\n So ordered.\n\n\n\n\n - 14 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361783/", "author_raw": "LIPEZ, Circuit Judge"}]}
TORRUELLA
LIPEZ
THOMPSON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584530/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Jose M. ALVARADO, Petitioner, v. Matthew WHITAKER, Acting United States Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-24\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n No. 17-1572\n\n JOSE M. ALVARADO,\n\n Petitioner,\n\n v.\n\n MATTHEW WHITAKER,*\n ACTING UNITED STATES ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF\n THE BOARD OF IMMIGRATION APPEALS\n\n\n Before\n Torruella, Lipez, and Thompson,\n Circuit Judges.\n\n\n Matthew S. Cameron for petitioner.\n Paul F. Stone, Senior Counsel for National Security Unit,\nOffice of Immigration Litigation, Civil Division, U.S. Department\nof Justice, with whom Chad A. Readler, Principal Deputy Assistant\nAttorney General, Civil Division, and Ethan B. Kanter, Acting\nChief, National Security Unit, Office of Immigration Litigation,\nwere on brief, for respondent.\n Sayoni Maitra, Karen Musalo, Eunice Lee, and Center for Gender\n& Refugee Studies were on brief for amicus curiae Center for Gender\n& Refugee Studies.\n\n\n January 24, 2019\n\n\n * Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions III as the respondent.\n\f LIPEZ, Circuit Judge. This case requires us to decide,\n\nas a question of first impression for our court, whether the\n\n\"persecutor bar\" -- which disqualifies certain persons from\n\nimmigration relief -- applies to an applicant who assisted or\n\nparticipated in persecution but acted without a personal motive to\n\ndo so. The petitioner in this case, Jose Alvarado, is a Salvadoran\n\nnative and citizen who concedes standing guard for his superiors\n\nwhile they engaged in an act of persecution. He denies, however,\n\nthat he shared their motive to persecute.\n\n An immigration judge (\"IJ\") granted Alvarado\n\ncancellation of removal under the Nicaraguan Adjustment and\n\nCentral American Relief Act (\"NACARA\") after concluding that the\n\npersecutor bar does not apply to Alvarado because he lacked a\n\nmotive to persecute. The Board of Immigration Appeals (\"BIA\")\n\nreversed the IJ's order, finding the persecutor bar applicable\n\ndespite the absence of such a motive.\n\n Alvarado seeks review of the decision of the BIA. After\n\ncareful consideration, we hold that a motive to persecute by an\n\napplicant who assisted or otherwise participated in persecution is\n\nnot required for application of the persecutor bar. Accordingly,\n\nwe deny Alvarado's petition.\n\n\n\n\n - 2 -\n\f I.\n\nA. Factual Background\n\n We draw the following facts from Alvarado's testimony\n\nbefore the IJ, which the IJ found to be credible.1 From 1981 to\n\n1984, during El Salvador's Civil War, Alvarado served in the\n\nSalvadoran National Guard (the \"National Guard\"), which he joined\n\n\"out of economic necessity\" because of the lack of employment\n\nopportunities. As a member of the National Guard, Alvarado \"could\n\nearn enough . . . to just get by.\"\n\n Alvarado's role in the National Guard was to patrol and\n\nprovide security. The specific incident at issue here occurred\n\nwhen Alvarado was patrolling a town. Alvarado stopped a man and\n\nasked him for identification. He then began to question the man.\n\nAlvarado's supervisors soon arrived at the scene, took over the\n\nquestioning, and eventually moved the man to a different location\n\nfor interrogation as a suspected guerilla. During the\n\ninterrogation, Alvarado stood guard while his superiors hit the\n\nman and placed needles under his fingernails.2\n\n\n 1The IJ noted \"inconsistencies\" in Alvarado's testimony,\nparticularly in his description of the incident at issue. However,\nthe IJ credited Alvarado's explanation for the inconsistencies:\nanxiety, depression, and Post-Traumatic Stress Disorder, causing\nmemory loss, confusion, and nervousness.\n 2Alvarado testified inconsistently as to what he saw or how\nmany interrogations he witnessed. At one point, he testified that\nhe did not witness the interrogation of any suspected guerillas by\nhis superiors. At another point, he testified that he provided\nsecurity for at least five interrogations, including the incident\n\n\n - 3 -\n\fB. Applicable Law\n\n NACARA provides, in relevant part, that Salvadoran\n\ncitizens living in the United States are eligible for various forms\n\nof immigration benefits and relief from deportation, including\n\n\"Special Rule Cancellation of Removal,\" if they meet certain\n\nrequirements. See 8 U.S.C. § 1229b. However, a person otherwise\n\neligible for cancellation of removal under NACARA is ineligible if\n\nhe \"ordered, incited, assisted, or otherwise participated in the\n\npersecution of an individual because of the individual's race,\n\nreligion, nationality, membership in a particular social group, or\n\npolitical opinion.\" 8 U.S.C. § 1231(b)(3)(B)(i) (emphasis added).\n\nThis restriction is referred to as the \"persecutor bar.\"\n\n We have noted that, although the persecutor bar has a\n\n\"smooth surface,\" beneath it \"lie a series of rocks\" creating\n\ninterpretive problems, including \"the nature of the acts and\n\nmotivations that comprise persecution, the role of scienter,\n\nwhether and when inaction may suffice, and the kind of connection\n\nwith persecution by others that constitutes 'assistance.'\"\n\n\n\n\nwhen he witnessed his superiors hit and put needles under the\nfingernails of a man he had detained. From Alvarado's varying\ntestimony, the IJ concluded that \"roughly five times . . .\n[Alvarado's] superiors took an individual from [Alvarado's]\ncustody\" and \"on one of those occasions [Alvarado] witness[ed] his\nsuperiors place needles under a detainee's nails during an\ninterrogation.\" The IJ relied on this single incident to find\nthat Alvarado had participated in persecutory conduct.\n\n\n - 4 -\n\fCastañeda-Castillo v. Gonzales, 488 F.3d 17, 20 (1st Cir. 2007)\n\n(en banc).\n\n In Castañeda-Castillo, we addressed one of these\n\ninquiries -- the role of scienter. See id. That case concerned\n\nan applicant for asylum who had participated in a military\n\noperation during which civilian villagers were massacred. See id.\n\nat 19. The applicant testified that, although his military unit\n\nparticipated in the operation, his squad was located miles away\n\nfrom the site of the massacre, and he had no knowledge of the\n\nmassacre until three weeks after it had occurred. Id. Because\n\nCastañeda testified that he had no prior or contemporaneous\n\nknowledge of the village massacre, relief under NACARA hinged on\n\nwhether the persecutor bar may apply to an alien whose conduct had\n\nthe \"objective effect\" of aiding persecution but who had no prior\n\nor contemporaneous knowledge of the persecution. Id. at 20.\n\nAnswering only this question, we held the persecutor bar\n\n\"presumptively\" inapplicable to an applicant who had no prior or\n\ncontemporaneous knowledge of the persecution.3 Id. at 22. We\n\nreasoned that such an interpretation was consistent with the\n\nmeaning of the term persecution, which \"strongly implies both\n\nscienter and illicit motivation,\" and common sense notions of\n\n\n 3We noted there may be \"gray-area cases where less than full\nand detailed knowledge may suffice\" for the persecutor bar to\napply, such as \"cases of willful blindness or strong suspicions.\"\nCastañeda-Castillo, 488 F.3d at 21.\n\n\n - 5 -\n\fculpability, which dictate that a person is not accountable for\n\nwrongdoing of which he has no knowledge. Id. at 20.\n\nC. The IJ's Decision\n\n Before the IJ, the government, citing Castañeda-\n\nCastillo, argued that the persecutor bar applied to Alvarado\n\nbecause he knowingly assisted or participated in the persecution\n\nof an individual because of that individual's political opinions.\n\nIn turn, Alvarado, also citing Castañeda-Castillo, pointed to our\n\nstatement there that \"'persecution' strongly implies both scienter\n\nand illicit motivation,\" id. at 20, and contended that the bar was\n\ninapplicable to him because our precedent made persecutory motive\n\na prerequisite for application of the bar.\n\n In a written decision, the IJ found the persecutor bar\n\ninapplicable. Although the IJ found that Alvarado knowingly4\n\nparticipated in the persecution of the detainee, she cited the\n\n\"illicit motivation\" language in Castañeda-Castillo, and found\n\nthat Alvarado's actions did not amount to \"persecution\" because\n\nAlvarado was not personally motivated by the victim's political\n\nbeliefs. She credited Alvarado's testimony that \"he captured\n\ndetainees on the orders of his superiors as a consequence of his\n\n\n\n 4 In support of the conclusion that Alvarado had prior or\ncontemporaneous knowledge, the IJ cited the closing argument of\ncounsel for Alvarado at the hearing, where counsel stated that\nAlvarado's \"testimony establishes contemporaneous knowledge.\"\nIt is not clear whether Alvarado conceded prior knowledge.\n\n\n - 6 -\n\femployment,\" and found that his actions were not motivated by a\n\ndesire to persecute a detained guerilla on account of his political\n\nbeliefs.\n\n After finding that Alvarado met NACARA's remaining\n\nrequirements, the IJ granted him special rule cancellation of\n\nremoval.\n\nD. The BIA's Decision\n\n In an appeal to the BIA, the government argued that the\n\npersecutor bar applies to Alvarado and that persecutory motive is\n\nnot required for application of the bar to an individual who\n\nassisted or otherwise participated in the persecution. The BIA,\n\nnoting that Alvarado \"does not contest that he 'assisted' his\n\nsuperiors' actions and that their acts were committed on account\n\nof the victim's political opinion,\" or that he had \"'prior or\n\ncontemporaneous knowledge'\" of those acts,5 framed the critical\n\nquestion in this case as whether Alvarado \"was required to have a\n\n\n 5 Although Alvarado contends in his petition for review to us\nthat he has always contested whether he \"assisted . . . or\notherwise participated\" in the interrogation tactics of his\nsuperiors, Alvarado did not address this question before the BIA.\nNor did he dispute the IJ's finding that he had prior or\ncontemporaneous knowledge. Indeed, in his brief to the BIA, he\nconceded that this element was met because he \"witnessed the acts.\"\nAlvarado cannot \"leapfrog over the BIA\" by raising these arguments\nnow. Ramirez-Matias v. Holder, 778 F.3d 322, 327 (1st Cir. 2015).\nIn immigration cases, \"a failure to present developed\nargumentation to the BIA on a particular theory amounts to a\nfailure to exhaust administrative remedies as to that theory.\"\nId. Accordingly, we lack jurisdiction to review his claims\nconcerning assistance and knowledge. See 8 U.S.C. § 1252(d)(1).\n\n\n - 7 -\n\fpersecutory motive when he assisted in the persecution of the\n\ndetainee.\"\n\n The BIA emphasized NACARA's plain language barring\n\nrelief for an alien who \"assisted . . . in the persecution of an\n\nindividual because of the individual's . . . political opinion.\"\n\n8 U.S.C. § 1231(b)(3)(B)(i). The BIA reasoned that the phrase\n\n\"because of\" in the statute is best read to refer to the motivation\n\nof the persecutors -- not that of the alien-applicant who assisted\n\nthe persecutors. Matter of J.M. Alvarado, 27 I. & N. Dec. 27, 29\n\n(BIA 2017) (citing Bah v. Ashcroft, 341 F.3d 348, 351 (5th Cir.\n\n2003)). The BIA concluded that, if Alvarado participated in\n\npersecution that occurred because of an individual's political\n\nopinions, his personal motivation was irrelevant to the\n\napplication of the persecutor bar. Because it was undisputed that\n\nthe conduct of Alvarado's superiors was based on the victim's\n\npolitical opinion, the BIA held that the persecutor bar applied to\n\nAlvarado, precluding NACARA relief. The BIA accordingly ordered\n\nAlvarado removed to El Salvador.\n\n II.\n\n Because the BIA has conducted its own analysis, \"we focus\n\nour review on the decision of the BIA.\" Gonzalez v. Holder, 673\n\nF.3d 35, 38 (1st Cir. 2012). Our review of a decision invoking\n\nspecial rule cancellation of removal under NACARA is limited to\n\n\"constitutional claims and questions of law.\" Gonzalez-Ruano v.\n\n\n - 8 -\n\fHolder, 662 F.3d 59, 63 (1st Cir. 2011). Here, we are presented\n\nwith a legal question, i.e., the meaning of the persecutor bar.\n\nWe review the BIA's legal conclusions de novo. McCreath v. Holder,\n\n573 F.3d 38, 41 (1st Cir. 2009).\n\n Alvarado argues that Castañeda-Castillo controls the\n\noutcome of this case, citing our discussion of the meaning of\n\n\"persecution\" in that decision, where we said \"the term\n\n'persecution' strongly implies both scienter and illicit\n\nmotivation.\" See 488 F.3d at 20. However, Alvarado is wrong about\n\nthe import of the \"illicit motivation\" language for two reasons.\n\nFirst, although we said in Castañeda-Castillo that \"the term\n\n'persecution' strongly implies both scienter and illicit\n\nmotivation,\" that decision focused on the role of knowledge in the\n\npersecutor bar, not on motive. See id.; see also id. at 22 (\"This\n\nwould be a different case if the evidence clearly established that\n\nCastañeda had guilty knowledge[.]\"); cf. Negusie v. Holder, 555\n\nU.S. 511, 528 (2009)(Scalia, J., concurring) (finding no reason\n\nwhy the BIA cannot consider questions of knowledge \"separate and\n\napart\" from questions of motive). Castañeda conceded that \"had\n\n[he] been aware in advance of a plan to murder civilians, his role\n\n. . . could be treated as culpable assistance.\" Castañeda-\n\nCastillo, 488 F.3d at 20. For this reason, we addressed only the\n\n\"narrow[]\" inquiry of \"whether the persecutor bar would apply to\n\n\n\n\n - 9 -\n\fCastañeda if he had no prior or contemporaneous knowledge of the\n\nmurder of civilians.\" Id. at 20 (emphasis added).\n\n Second, the language Alvarado cites concerns the meaning\n\nof \"persecution,\" rather than \"assist[ance]\" or \"participat[ion].\"\n\nSee id. at 20 (describing persecution as \"impl[ying] both scienter\n\nand illicit motivation\"); id. at 20 n.1 (citing Random House\n\nDictionary of the English Language (2d ed. unabr. 1987) (\"The\n\ndictionary defines 'persecute' as 'to pursue with harassing or\n\noppressive treatment, esp. because of religion, race, or\n\nbeliefs[.]'\")). Plainly, persecution requires illicit motivation,\n\nas the persecutor bar itself requires. See 8 U.S.C. §\n\n1231(b)(3)(B)(i) (requiring that persecution be on account of\n\n\"race, religion, nationality, membership in a particular social\n\ngroup, or political opinion\"). Hence, there is nothing at all\n\nsurprising about the reference in Castañeda-Castillo to illicit\n\nmotive when discussing the meaning of persecution, even though the\n\nquestion of the motive of the persecution was never at issue.\n\nRather, the question was the link between knowledge and culpability\n\nwithin the meaning of the persecutor bar.\n\n Now faced with the question of the link between motive\n\nand culpability, we agree with the BIA that the persecutor bar\n\napplies to an alien who knowingly and willingly aided in\n\npersecution, but did so without a persecutory motivation. First,\n\nas the BIA explained, the syntax of the persecutor bar supports\n\n\n - 10 -\n\fthe agency's interpretation. The statute bars from relief an alien\n\nwho \"ordered, incited, assisted, or otherwise participated\" in\n\n\"persecution . . . because of\" enumerated protected grounds. As\n\na general rule, a modifier -- that is, a word or clause that limits\n\nor adds to the meaning of another word -- is adjacent to the word\n\nit modifies or describes.6 See Jane Straus, et al., The Blue Book\n\nof Grammar and Punctuation 23 (\"Place descriptive words and phrases\n\nas close as is practical to the words they modify.\") (11th Ed.\n\n2014). Thus, here, \"because of\" modifies \"persecution,\"\n\nindicating that the pertinent inquiry is whether the persecution\n\nwas motivated by protected grounds. By contrast, no such\n\nlimitation is attached to the actions of the person who assists.\n\nRather, the persecutor bar by its terms applies to any \"alien who\n\n. . . assisted, or otherwise participated\" in the persecutory\n\nconduct. Consequently, the structure of the subsection indicates\n\nthat, although the persecutors must be motivated by a protected\n\nground, the participation of the alien need not be so motivated.\n\n\n\n\n 6To demonstrate, consider the two sentences: (1) Mary saw\nthe dog that used to be hers behind the house. (2) Mary saw the\ndog behind the house that used to be hers. In the first sentence,\n\"that used to be hers\" modifies \"dog,\" indicating that the dog was\nformerly Mary's. In the second sentence, \"that used to be hers\"\nmodifies \"house,\" indicating that Mary had formerly owned the\nhouse.\n\n\n - 11 -\n\fSee Bah, 341 F.3d at 351 (employing similar reasoning);7 accord\n\nSingh v. Gonzales, 417 F.3d 736, 740 (7th Cir. 2005).\n\n Second, Alvarado relies on a much too narrow view of\n\nculpability. A person who knowingly and voluntarily8 participates\n\nin persecution is sufficiently culpable to be held accountable\n\nunder the persecutor bar.9 To hold otherwise, would create\n\n\n 7\n In its decision, the BIA cited Bah, 341 F.d at 351, as\nconsistent with its decision. See Matter of J.M. Alvarado, 27 I.\n& N. Dec. 27, 29 (BIA 2017). Alvarado contends that this reliance\nwas error because Bah is no longer good law in light of Negusie v.\nHolder, 555 U.S. 511 (2009). We disagree that Bah is no longer\ngood law. In Negusie, the Court held its interpretation of the\nDisplaced Person Act does not compel an interpretation of identical\nlanguage in the persecutor bar. See id. at 519-20. Bah did not\nfind its interpretation of the persecutor bar to be compelled.\nSee 341 F.3d at 351.\n 8\n This decision does not preclude an applicant from raising a\nwell-developed argument that he or she knowingly aided in\npersecution but did so only because of duress or coercion. Cf.\nNegusie, 555 U.S. at 515 (concerning alien who, at the command of\nsuperior officers, assisted in persecution but did so only under\nduress). Alvarado has never made such an argument.\n 9\n Alvarado contends that decisions of the Second, Fourth,\nEighth, and Ninth Circuits all support his view of the persecutor\nbar. But the cases cited by Alvarado do not interpret the\npersecutor bar to require illicit motive to persecute; rather,\nthey are in accordance with this court's decision in Castañeda-\nCastillo, requiring culpable knowledge. See Quitanilla v. Holder,\n758 F.3d 570 (4th Cir. 2014) (requiring some level of \"culpable\nknowledge\"); Parlak v. Holder, 578 F.3d 457, 470 (6th Cir. 2009)\n(finding petitioner acted \"voluntarily and knowingly\"); Xu Sheng\nGao v. U.S. Atty. Gen., 500 F.3d 93, 103 (2d Cir. 2007) (requiring\n\"culpable knowledge\"); Xie v. I.N.S., 434 F.3d 136, 144 (2d Cir.\n2006) (culpability established by awareness). Alvarado also cites\nseveral cases that discuss what conduct constitutes \"assistance.\"\nSee Hernandez v. Reno, 258 F.3d 806, 813-15 (8th Cir. 2001);\nMiranda-Alvarado v. Gonzales, 449 F.3d 915, 925-30. These cases\nlikewise do not address the issue of motivation. Alvarado cites\nno cases supporting the view that the persecutor bar requires a\n\n\n - 12 -\n\fanomalous results. For instance, under Alvarado's view of the\n\npersecutor bar, an alien applicant who repeatedly and voluntarily\n\nbussed innocent Sikhs to a police station, knowing they would be\n\nbeaten, see Singh, 417 F.3d at 740, would bear no responsibility\n\nunder the bar -- no matter how brutal the police's conduct -- as\n\nlong as he did so for a reason other than a personal motive to\n\npersecute.\n\n That result would also be contrary to common notions of\n\nculpability, which dictate that a person is responsible when she\n\nacts knowingly and voluntarily. Although this is not a criminal\n\ncase, principles of criminal law illustrate the point. Motive is\n\ngenerally not an element of a criminal offense unless specifically\n\nstated. See Jerome Hall, General Principles of Criminal Law 88\n\n(2d ed. 1960) (\"[H]ardly any part of penal law is more definitely\n\nsettled than that motive is irrelevant.\"); James Fitzjames\n\nStephen, 3 A History of the Criminal Law of England 18 (1883)\n\n(\"[T]he motives of the offender ought never . . . enter into the\n\ndefinition of an offence . . . because they do not affect the\n\npublic danger or actual mischief of the crimes which they cause.\");\n\nsee also United States v. White, 766 F.2d 22, 24 (1st Cir. 1985)\n\n(\"[E]vidence of a 'good' motive for violating the law is\n\nirrelevant[.]\").\n\n\nfinding of illicit motive to persecute on the part of the alien\nwho assists or otherwise participates in the persecution.\n\n\n - 13 -\n\f Finally, Alvarado contends that reading the persecutor\n\nbar to apply to aliens who did not share the illicit motive to\n\npersecute contravenes the purpose of the persecutor bar and asylum\n\nlaw generally. To the contrary, applying the persecutor bar to a\n\nperson who knowingly and voluntarily participated in persecution\n\nis a policy choice consistent with a body of law that was designed\n\nto shelter the persecuted.\n\n III.\n\n In sum, the persecutor bar does not require a showing\n\nthat the alien shared the motive of the persecutors whom he\n\nassisted. This interpretation of the bar is consistent with the\n\nplain language of the statute, our precedent, the decisions of\n\nother courts, and common notions of culpability. Accordingly, the\n\npetition for review is denied.\n\n So ordered.\n\n\n\n\n - 14 -\n[END_CASE]", "role": "user" } ]
8,619,563
United States v. José G. MARTÍNEZ-BENÍTEZ
United States v. Martínez-Benítez
2019-01-24
No. 17-1393
U.S. Court of Appeals for the First Circuit
{"judges": "Barron, Lynch, Thompson", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8598813/", "author_raw": ""}]}
BARRON
LYNCH
THOMPSON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8619563/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. José G. MARTÍNEZ-BENÍTEZ\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-24\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,584,942
UNITED STATES, Appellant, v. Daniel E. MUSSO, Sr., Defendant, Appellee.
United States v. Musso
2019-01-25
18-1260P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Barron", "parties": "", "opinions": [{"author": "LYNCH, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1260\n\n UNITED STATES,\n\n Appellant,\n\n v.\n\n DANIEL E. MUSSO, SR.,\n\n Defendant, Appellee.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF NEW HAMPSHIRE\n\n [Hon. Joseph A. DiClerico, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Matthew T. Hunter, Special Assistant U.S. Attorney, with whom\nScott W. Murray, United States Attorney, Seth R. Aframe, Assistant\nU.S. Attorney, and John S. Davis, Assistant U.S. Attorney, were on\nbrief, for appellant.\n Penny S. Dean for appellee.\n\n\n January 25, 2019\n\f LYNCH, Circuit Judge. The government appeals from the\n\ndistrict court's pretrial dismissal of four charges of violations\n\nof the National Firearms Act (NFA), 26 U.S.C. § 5801 et seq.,\n\nbrought against Daniel Musso. Musso bought four military M67\n\nfragmentation grenades from an FBI agent during an undercover sting\n\noperation. The FBI had obtained the grenades used in the sting\n\nfrom the U.S. Marine Corps. M67 grenades are issued to Marines\n\nfor combat. Before the sale to Musso, the FBI had replaced each\n\ngrenade's original, operable fuze with an identical but inoperable\n\none. The district court agreed with Musso that, because the\n\noperable fuzes had been removed and replaced with inoperable fuzes,\n\nthe grenades were not \"explosive grenades\" under the NFA. United\n\nStates v. Musso, No. 16-CR-033-JD, 2018 WL 1313977, at *8 (D.N.H.\n\nMar. 9, 2018).\n\n For purposes of the motion to dismiss, Musso admitted,\n\namong other things, that each grenade was still armed with its\n\noriginal explosive charge: 6.5 ounces of Composition B high\n\nexplosives. Composition B is a mixture of TNT and RDX that, when\n\nin the amount included in an M67 grenade, has a killing radius of\n\nabout five meters (just over sixteen feet). The motion further\n\nadmitted that each grenade could be made to explode by reinserting\n\na live fuze or by a \"commercial/military/improvised detonator.\"\n\n Based on the admitted facts and on the complete text,\n\nstatutory context, and Congress's intent in enacting the\n\n\n - 2 -\n\f\"explosive grenade\" provision of the NFA, we reverse and hold that\n\neach grenade, as purchased by Musso, was an \"explosive grenade.\"\n\n I.\n\nA. The National Firearms Act, 26 U.S.C. § 5801, et seq.\n\n The NFA makes it a crime to receive or possess an\n\nunregistered \"firearm.\" 26 U.S.C. § 5861(d). There is no dispute\n\nthat the grenades here were \"unregistered.\" Under the NFA, the\n\ndefinition of the term \"firearm\" includes a \"destructive device.\"\n\nId. § 5845(a)(8). The act later, in Section 5845(f)(1), defines\n\na \"destructive device\" as\n\n (1) any explosive, incendiary, or poison gas\n (A) bomb,\n (B) grenade,\n (C) rocket having a propellent [sic]\n charge of more than four ounces,\n (D) missile having an explosive or\n incendiary charge of more than one-\n quarter ounce,\n (E) mine, or\n (F) similar device . . . .\n\nId. § 5845(f)(1). The government relies on this definition. We\n\nnote that the NFA does not define the terms \"explosive\" or\n\n\"grenade.\"\n\n Section 5845(f) has two later sections that include\n\nother things as destructive devices:\n\n (2) any type of weapon by whatever name known\n which will, or which may be readily converted\n to, expel a projectile by the action of an\n explosive or other propellant, the barrel or\n barrels of which have a bore of more than one-\n half inch in diameter, except a shotgun or\n\n\n - 3 -\n\f shotgun shell which the Secretary finds is\n generally recognized as particularly suitable\n for sporting purposes; and\n (3) any combination of parts either designed\n or intended for use in converting any device\n into a destructive device as defined in\n subparagraphs (1) and (2) and from which a\n destructive device may be readily assembled.\n\nId. § 5845(f)(2)-(3).\n\n Following these terms, the statute has a separate\n\nsentence that excludes \"any device which is neither designed nor\n\nredesigned for use as a weapon\" and \"any device, although\n\noriginally designed for use as a weapon, which is redesigned for\n\nuse as a signaling, pyrotechnic, line throwing, safety, or similar\n\ndevice.\" Id. Those exclusions present affirmative defenses; they\n\ndo not define elements of the substantive offense. United States\n\nv. Beason, 690 F.2d 439, 445 (5th Cir. 1982).\n\n The NFA was not the first statute to deal with devices\n\nlike those at issue here. In April 1968, six months before\n\nCongress enacted the above \"destructive device\" provision,\n\nCongress made it a crime to, among other things, teach the \"use,\n\napplication, or making of any firearm or explosive or incendiary\n\ndevice.\" 18 U.S.C. § 231(a)(1). One such \"explosive or incendiary\n\ndevice\" is an \"explosive . . . grenade.\" 18 U.S.C. § 232(5)(B).\n\nCongress again addressed these devices when it enacted a\n\n\"destructive device\" provision as part of the gun control\n\nprovisions of the Omnibus Crime Control and Safe Streets Act of\n\n\n\n\n - 4 -\n\f1968. See Pub. L. No. 90-351, § 921(a)(4). Congress shortly\n\nthereafter added the same \"destructive device\" provision to the\n\nNFA with the Gun Control Act of 1968 (GCA). See United States v.\n\nOba, 448 F.2d 892, 893-94 (9th Cir. 1971).\n\n The GCA's purpose was \"to provide support to Federal,\n\nState, and local law enforcement officials in their fight against\n\ncrime and violence.\" Pub. L. No. 90-618, § 101. It represented\n\n\"a Congressional attempt to stem the traffic in dangerous weapons\n\nbeing used in an increasing number of crimes involving personal\n\ninjury.\" United States v. Posnjak, 457 F.2d 1110, 1113 (2d Cir.\n\n1972). And, in the GCA, Congress included the \"destructive device\"\n\nprovision at issue here to cover \"military-type weapons,\" id. at\n\n1115 (citing S. Rep. No. 90-1501, at 25, 30 (1968)), and\n\n\"objectively identifiable weapons of war,\" id. at 1116.\n\n Unlike with many other crimes, Congress chose not to\n\ncriminalize attempts to violate the GCA's destructive device\n\nprovision. A practical consequence of that decision is that agents\n\nengaged in undercover sting operations actually pass destructive\n\ndevices like explosive grenades to the target, which runs some\n\noperational risks. Law enforcement tries to reduce those risks to\n\nagents, targets, and the public by removing fuzes from otherwise\n\nlive grenades.\n\n\n\n\n - 5 -\n\fB. Background\n\n The essential facts are undisputed for our purposes and\n\nare worth repeating. The FBI replaced the grenades' original fuzes\n\nwith mechanically and visually identical, but inoperable, fuzes\n\nbefore giving them to Musso. Each grenade was, however, armed\n\nwith its original explosive charge of Composition B.1 Each grenade\n\ncould be made to explode by, for example, replacing the inoperable\n\nfuze with an operable one, by using a commercial or homemade\n\ndetonator, or by a sufficient impact. The government concedes\n\nthat the grenades as purchased by Musso would not have detonated\n\nabsent these other circumstances had Musso or anyone else merely\n\npulled their pins. A search of Musso's property following his\n\narrest did not turn up any fuzes or other detonators.\n\nC. Procedural History\n\n Musso moved to dismiss four counts of the resulting\n\nindictment, arguing that the grenades he received were not\n\n\"explosive grenades\" and so were not destructive devices under the\n\nNFA. On March 9, 2018, the district court granted Musso's motion\n\nto dismiss those counts. Musso, 2018 WL 1313977, at *8.\n\n\n\n\n 1 We deem Musso to have admitted this for purposes of the\nmotion to dismiss. We note that he has not pleaded guilty to the\nfifth count of his underlying indictment, which charges him with\nknowingly receiving \"approximately 26 ounces of Composition B high\nexplosive, contained within four grenades.\"\n\n\n - 6 -\n\f The district court consulted several dictionaries and\n\nconcluded that \"the ordinary meaning of 'grenade' implies a device\n\nthat contains not only explosive material but also a means of\n\ndetonating that explosive material.\" Id. at *5. The district\n\ncourt next reasoned that \"explosive,\" when modifying \"grenade,\"\n\nnecessarily implied that the grenade \"must, in fact, be capable of\n\nexploding.\" Id. Combining these understandings, the district\n\ncourt found that \"the ordinary meaning of the phrase 'explosive\n\ngrenade' . . . is a device that is in and of itself capable of\n\nexploding.\" Id. The district court then dismissed the counts.\n\nId. at *8.\n\n II.\n\n We clear away a preliminary procedural issue. Although\n\nwe have not before addressed the issue, other \"circuit courts have\n\nalmost uniformly concluded\" that, under Federal Rule of Criminal\n\nProcedure 12(b)(1), \"a district court may consider a pretrial\n\nmotion to dismiss an indictment where the government does not\n\ndispute the ability of the court to reach the motion and proffers,\n\nstipulates, or otherwise does not dispute the pertinent facts.\"\n\nUnited States v. Weaver, 659 F.3d 353, 355 n* (4th Cir. 2011)\n\n(collecting cases). We join this consensus.\n\n The facts necessary to resolve the issue now on appeal\n\nare not in dispute, and the government had requested that the\n\ndistrict court resolve the issue. We review the district court's\n\n\n - 7 -\n\fconclusion de novo, id. at 356, and determine that the court erred\n\nand so reverse.\n\n III.\n\n As framed, on admitted facts, the question before us is\n\nan issue of law. The government bears the burden of establishing\n\nthat the grenades here met the definition of \"explosive grenades.\"\n\nMusso, in turn, bears the burden as to whether the grenades fall\n\nwithin the exclusionary clause. On the facts presented, we reject\n\nMusso's definitional argument as well as his argument, based on\n\nthe exclusionary clause, that the FBI's removal of the grenades'\n\nfuzes means the grenades are not \"designed\" as weapons. In\n\naddressing his argument based on the exclusionary clause, we treat\n\nMusso as having raised that affirmative defense and bypass any\n\npotential forfeiture resulting from his failure to pursue that\n\nargument in his motion to dismiss.\n\n We begin, as always, with the statutory text concerning\n\n\"explosive grenades.\" The NFA definitional section requires that\n\nto be a \"destructive device,\" a grenade must be an \"explosive,\n\nincendiary, or poison gas . . . grenade.\" 26 U.S.C. § 5845(f).\n\nAnd an NFA \"destructive device\" must have been \"designed [or]\n\nredesigned for use as a weapon,\" and not, if originally designed\n\nas a weapon, \"redesigned for use as a signaling, pyrotechnic, line\n\nthrowing, safety, or similar device.\" Id. No issue is before us\n\nof the interpretation of other parts of the statute concerned with\n\n\n - 8 -\n\fother destructive devices or with the clause in Section 5845(f)(3)\n\nconcerning \"any combination of parts . . . from which a destructive\n\ndevice may be readily assembled.\"2\n\n We dispose of Musso's argument based on the statutory\n\nexclusion first. On these facts, we reject the argument that\n\nbecause the grenades' fuzes were inoperable, that meant the\n\ngrenades were \"redesigned\" so as not to be weapons. Congress only\n\nexcluded certain \"redesigned\" devices: those that have been\n\n\"redesigned for use as a signaling, pyrotechnic, line throwing,\n\nsafety, or similar device.\" 26 U.S.C. § 5845(f). There is no\n\ncontention here that Musso's devices were redesigned for any of\n\nthose purposes.\n\n Musso's grenades were designed as weapons. Each M67\n\ngrenade sold to Musso was a standard-issue Marine Corps weapon.\n\nThat the grenades were inoperable when purchased by Musso does not\n\nchange the fact that they were \"designed\" as weapons. Cf. United\n\nStates v. Rivera, 415 F.3d 284, 286 (2d Cir. 2005) (\"Where a weapon\n\ndesigned to fire a projectile is rendered inoperable, whether on\n\npurpose or by accident, . . . it continues to be 'designed' to\n\nfire a projectile.\"). We conclude that Musso's explosive grenades\n\nwere each \"designed . . . for use as a weapon,\" 26 U.S.C.\n\n§ 5845(f), and so were not excluded from the NFA's coverage.\n\n\n 2 Cases construing that clause, like United States v.\nPosnjak, 457 F.2d 1110 (2d Cir. 1972), are not relevant here.\n\n\n - 9 -\n\f We turn to the definitional arguments. Congress did\n\nnot, in the NFA, define the term \"explosive grenade.\" When\n\nCongress uses words that it does not define, \"we assume those words\n\n'carry their plain and ordinary meaning.'\" United States v.\n\nGordon, 875 F.3d 26, 33 (1st Cir. 2017) (quoting Stornawaye Fin.\n\nCorp. v. Hill (In re Hill), 562 F.3d 29, 32 (1st Cir. 2009)). The\n\ndistrict court reasoned \"that the ordinary meaning of the phrase\n\n'explosive grenade' in [Section] 5845(f) is a device that is in\n\nand of itself capable of exploding,\" Musso, 2018 WL 1313977, at\n\n*5, and \"that a destructive device must contain certain essential\n\ncomponents\" -- namely, a working fuze, id. at *6.\n\n The government challenges the district court's plain-\n\ntext reading here. We find that the plain meaning of the words\n\n\"explosive\" and \"grenade\" do not clearly exclude the devices Musso\n\npurchased -- M67 grenades with inoperable fuzes. We then assume\n\narguendo that the plain meaning of those words does not resolve\n\nthis case in the government's favor and so we turn to other\n\ntraditional tools of statutory interpretation. See Yates v. United\n\nStates, 135 S. Ct. 1074, 1081 (2015) (noting that the meaning of\n\na statutory term \"does not turn solely on dictionary definitions\n\nof [that term's] component words\"). We ultimately reject the\n\ndistrict court's glosses on the term \"explosive grenade\" because\n\nthey do not come from the NFA's text, \"and we may not engraft our\n\nown exceptions onto the statutory text.\" Henry Schein, Inc. v.\n\n\n - 10 -\n\fArcher & White Sales, Inc., No. 17-1272, 2019 WL 122164, at *5\n\n(U.S. Jan. 8, 2019). We conclude, looking to statutory context,\n\nthat Congress intended that the term \"explosive grenade\" include\n\nthe grenades as purchased by Musso.\n\n Where Congress wanted to define a device by its\n\ncapability, it said so explicitly. Under Section 5845(f)(2), a\n\nweapon with a \"bore of more than one-half inch in diameter\" is a\n\ndestructive device if it \"will, or . . . may be readily converted\n\nto, expel a projectile by the action of an explosive or other\n\npropellant.\" 26 U.S.C. § 5845(f)(2) (emphasis added). This is a\n\n\"test of objective capability,\" United States v. Crooker, 608 F.3d\n\n94, 98 & n.2 (1st Cir. 2010), and it is not unique to Section\n\n5845(f)(2). For instance, Section 5845(b) defines a machinegun as\n\n\"any weapon which shoots, is designed to shoot, or can be readily\n\nrestored to shoot, automatically more than one shot, without manual\n\nreloading, by a single function of the trigger.\" 26 U.S.C.\n\n§ 5845(b) (emphasis added). From the presence of capability\n\nrequirements throughout Section 5845, and particularly in Section\n\n5845(f)(2), we conclude that the absence of such a requirement in\n\nSection 5845(f)(1), the \"explosive grenade\" provision, is\n\nintentional. See New Prime Inc. v. Oliveira, No. 17-340, 2019 WL\n\n189342, at *7 (U.S. Jan. 15, 2019) (drawing a negative inference\n\nfrom word choices made in \"a neighboring term in the statutory\n\ntext\").\n\n\n - 11 -\n\f Next, the language of Section 5845(f) does not require\n\nthat an \"explosive grenade\" have specific parts, like a working\n\nfuze. Context immediately reinforces this conclusion: Under\n\nSection 5845(f)(1)(c), which directly follows the \"explosive\n\ngrenade\" provision, a rocket only qualifies as a destructive device\n\nif it has \"a propellent [sic] charge of more than four ounces.\"\n\n26 U.S.C. § 5845(f)(1)(C). And right after that, Congress required\n\nthat a missile have \"an explosive or incendiary charge of more\n\nthan one-quarter ounce.\" Id. § 5845(f)(1)(D). Section 5845 is\n\nfilled with similar requirements: A shotgun must have \"a barrel\n\nor barrels of less than 18 inches in length.\" Id. § 5845(a)(1).\n\nAnd a rifle must have \"a barrel or barrels of less than 16 inches\n\nin length.\" Id. § 5845(a)(3). Congress could easily have required\n\nthat an \"explosive grenade\" have a working fuze. We conclude that\n\nthe absence of any such requirement was intentional.\n\n We also consider the \"destructive device\" provision in\n\nthe sequence in which Congress wrote Section 5845(f). See New\n\nPrime, 2019 WL 189342, at *4 (analyzing a statute based on its\n\n\"terms and sequencing\"). Section 5845(f)(1) first covers a bomb,\n\ngrenade, rocket, missile, mine, or \"similar device.\" 26 U.S.C.\n\n§ 5845(f)(1). Section 5845(f)(2) then covers a weapon, \"by\n\nwhatever name known,\" that meets the capability test outlined\n\nabove. Id. § 5845(f)(2). And finally, Section 5845(f)(3) covers\n\n\"any combination of parts\" that can be \"readily assembled\" into\n\n\n - 12 -\n\fone of the devices described in the previous two sections. This\n\nsequence highlights that Section 5845(f)(1) was meant to cover\n\nweapons with evident, descriptive names, while 5845(f)(2) and\n\n(f)(3) are more in the nature of catch-all provisions meant to\n\nensure coverage where intended beyond the named devices in\n\n5845(f)(1). Because \"explosive grenade\" is sufficiently\n\ndescriptive to limit that provision's coverage, Congress did not\n\nadd a capability requirement or a parts requirement.\n\n Were there any doubt left, we would also note that\n\nSections 5845(f)(2) and (f)(3) include language like \"readily\n\nassembled\" or \"readily converted.\" The functional cast of that\n\nlanguage fits in those later catch-all provisions, which deal with\n\nall manner of weapons that have no evident name. But for Section\n\n5845(f)(1), no such modifying language was necessary.\n\n The district court's contrary view has further problems:\n\nIt reads the term \"explosive\" outside of its direct context. Our\n\ninterpretation avoids this problem. Looking again to neighboring\n\nterms, we conclude that \"explosive\" describes a category of\n\ngrenade. Section 5845(f)(1) prohibits the unregistered receipt or\n\npossession of not only an \"explosive . . . grenade,\" but also an\n\n\"incendiary . . . grenade\" or a \"poison gas . . . grenade.\" 26\n\nU.S.C. § 5845(f)(1)(B). The natural reading is that \"explosive\"\n\ndistinguishes one category of grenade covered by the statute from\n\nother categories of grenades, either within the statute (like\n\n\n - 13 -\n\fpoison gas grenades) or outside the statute's reach (like, perhaps,\n\nsmoke grenades). Cf. United States v. Williams, 553 U.S. 285, 294\n\n(2008) (\"[A] word is given more precise content by the neighboring\n\nwords with which it is associated.\"). On the facts presented here,\n\nthe district court's reading of the term \"explosive\" violates the\n\n\"fundamental principle of statutory construction . . . that the\n\nmeaning of a word cannot be determined in isolation.\" Yates, 135\n\nS. Ct. at 1082 (quoting Deal v. United States, 508 U.S. 129, 132\n\n(1993)).\n\n The reasoning we have provided suffices to support our\n\nconclusion that Musso's devices were \"explosive grenades,\" as\n\nCongress intended that term to be understood.3\n\n The district court attempted to support its\n\ninterpretation of \"explosive grenade\" by pointing to out-of-\n\ncircuit precedent. But none of the cases the court cited were\n\ndecided under Section 5845(f)(1)(b), the provision at issue here,\n\nand none involved grenades armed with their original explosive\n\ncharges. In United States v. Malone, 546 F.2d 1182 (5th Cir.\n\n1977), the defendant did not have, either in his possession or in\n\n\n 3 Musso argues that we should apply the rule of lenity.\nBut this rule \"applies only if, 'after considering text, structure,\nhistory and purpose, there remains a grievous ambiguity or\nuncertainty in the statute such that the Court must simply guess\nas to what Congress intended.'\" Abramski v. United States, 573\nU.S. 169, 188 n.10 (2014) (quoting Maracich v. Spears, 570 U.S.\n48, 76 (2013)). There is no grievous uncertainty here, so lenity\ndoes not apply.\n\n\n - 14 -\n\fthe devices at issue, any explosive material. Id. at 1184. In\n\nUnited States v. Blackburn, 940 F.2d 107 (4th Cir. 1991), a\n\nsentencing appeal following a guilty plea, there were twenty-eight\n\ninert grenade hulls that contained no explosive material. Id. at\n\n109. There was no proof there that the explosive charge within\n\ntwo live grenades could have been redistributed to make all thirty\n\ngrenades there active, and the quantity of destructive devices was\n\na factor in a sentencing enhancement. Id. at 110. And in United\n\nStates v. Osuna, 189 F.3d 1289 (10th Cir. 1999), the Tenth Circuit\n\nmerely accepted the government's concession that \"inert\" grenades\n\ndid not qualify as destructive devices (without defining \"inert\")\n\nand so did not support a sentencing enhancement. Id. at 1295.\n\nThese cases say nothing about whether Musso's grenades fall under\n\nthe statute.\n\n Further, United States v. Sheehan, 838 F.3d 109 (2d Cir.\n\n2016), supports our reasoning.4 The Second Circuit there held that\n\na nonfunctioning homemade bomb that contained an explosive charge\n\nbut had an inoperable fuze was an \"explosive bomb\" because it\n\n\n\n 4 We acknowledge that Sheehan involved the \"destructive\ndevice\" provision at 18 U.S.C. § 921(a)(4), enacted by the Omnibus\nCrime Control and Safe Streets Act of 1968. But Congress, when it\nadded the \"destructive device\" provision here to the NFA, copied\nthat earlier provision verbatim. And when a term \"is obviously\ntransplanted from another legal source, whether the common law or\nother legislation, it brings the old soil with it.\" Stokeling v.\nUnited States, No. 17-5554, 2019 WL 189343, at *5 (U.S. Jan. 15,\n2019) (quoting Hall v. Hall, 138 S. Ct. 1118, 1128 (2018)).\n\n\n - 15 -\n\fremained capable of detonating by other means. Id. at 119-20.\n\nThat the device \"could not explode in the way its maker might have\n\nassumed was the ordinary or even only way in which it could be\n\ndetonated -- i.e., via the fuzing system -- because it lacked a\n\nparticular component of which such a device is ordinarily composed\"\n\nwas \"irrelevant\" there. Id. So too here.5\n\n IV.\n\n With the NFA, Congress aimed to decrease threats to\n\npublic safety from destructive devices. These devices have been\n\nused for criminal conduct that has included robbery, S. Rep. No.\n\n90-1097, at 78 (1968) (describing the use of a \"Finnish Lahti\n\nantitank gun . . . in the robbery of a Brinks Co. installation\"),\n\nand the \"attempted assassination of a United States Attorney,\"\n\nUnited States v. Hamrick, 43 F.3d 877, 886 (4th Cir. 1995). And\n\nwhile we have no need to resort to legislative history, there is\n\ncongressional history \"to the effect that Congress intended to\n\nproscribe the activities generally associated with armed groups\n\ndevoted to disruption of public authority.\" Posnjak, 457 F.2d at\n\n\n\n 5 We do not rely on United States v. Rushcamp, 526 F.3d\n1380 (6th Cir. 1975), which the government cites. There, the Sixth\nCircuit concluded that an inoperable military munition -- a rocket\nlauncher with a broken firing mechanism -- was a destructive\ndevice. But that case turned on the language of Section (f)(2),\nwhich defines a rocket launcher as a destructive device if it \"may\nbe readily converted to, expel a projectile by action of an\nexplosive or other propellant,\" id. at 1382, and not the Section\nat issue here.\n\n\n - 16 -\n\f1120. But the district court's order would require agents\n\nconducting an undercover sting operation to give fully functional\n\n\"weapons of war,\" id. at 1116, like explosive grenades, to\n\npotential felons.\n\n The result reached by the district court is contrary to\n\nthe complete text and context of the NFA and is not what Congress\n\nintended. We reverse the dismissal of the counts against Musso,\n\nreinstate them, and remand for further proceedings consistent with\n\nthis opinion.\n\n\n\n\n - 17 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362195/", "author_raw": "LYNCH, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584942/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES, Appellant, v. Daniel E. MUSSO, Sr., Defendant, Appellee.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1260\n\n UNITED STATES,\n\n Appellant,\n\n v.\n\n DANIEL E. MUSSO, SR.,\n\n Defendant, Appellee.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF NEW HAMPSHIRE\n\n [Hon. Joseph A. DiClerico, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Matthew T. Hunter, Special Assistant U.S. Attorney, with whom\nScott W. Murray, United States Attorney, Seth R. Aframe, Assistant\nU.S. Attorney, and John S. Davis, Assistant U.S. Attorney, were on\nbrief, for appellant.\n Penny S. Dean for appellee.\n\n\n January 25, 2019\n\f LYNCH, Circuit Judge. The government appeals from the\n\ndistrict court's pretrial dismissal of four charges of violations\n\nof the National Firearms Act (NFA), 26 U.S.C. § 5801 et seq.,\n\nbrought against Daniel Musso. Musso bought four military M67\n\nfragmentation grenades from an FBI agent during an undercover sting\n\noperation. The FBI had obtained the grenades used in the sting\n\nfrom the U.S. Marine Corps. M67 grenades are issued to Marines\n\nfor combat. Before the sale to Musso, the FBI had replaced each\n\ngrenade's original, operable fuze with an identical but inoperable\n\none. The district court agreed with Musso that, because the\n\noperable fuzes had been removed and replaced with inoperable fuzes,\n\nthe grenades were not \"explosive grenades\" under the NFA. United\n\nStates v. Musso, No. 16-CR-033-JD, 2018 WL 1313977, at *8 (D.N.H.\n\nMar. 9, 2018).\n\n For purposes of the motion to dismiss, Musso admitted,\n\namong other things, that each grenade was still armed with its\n\noriginal explosive charge: 6.5 ounces of Composition B high\n\nexplosives. Composition B is a mixture of TNT and RDX that, when\n\nin the amount included in an M67 grenade, has a killing radius of\n\nabout five meters (just over sixteen feet). The motion further\n\nadmitted that each grenade could be made to explode by reinserting\n\na live fuze or by a \"commercial/military/improvised detonator.\"\n\n Based on the admitted facts and on the complete text,\n\nstatutory context, and Congress's intent in enacting the\n\n\n - 2 -\n\f\"explosive grenade\" provision of the NFA, we reverse and hold that\n\neach grenade, as purchased by Musso, was an \"explosive grenade.\"\n\n I.\n\nA. The National Firearms Act, 26 U.S.C. § 5801, et seq.\n\n The NFA makes it a crime to receive or possess an\n\nunregistered \"firearm.\" 26 U.S.C. § 5861(d). There is no dispute\n\nthat the grenades here were \"unregistered.\" Under the NFA, the\n\ndefinition of the term \"firearm\" includes a \"destructive device.\"\n\nId. § 5845(a)(8). The act later, in Section 5845(f)(1), defines\n\na \"destructive device\" as\n\n (1) any explosive, incendiary, or poison gas\n (A) bomb,\n (B) grenade,\n (C) rocket having a propellent [sic]\n charge of more than four ounces,\n (D) missile having an explosive or\n incendiary charge of more than one-\n quarter ounce,\n (E) mine, or\n (F) similar device . . . .\n\nId. § 5845(f)(1). The government relies on this definition. We\n\nnote that the NFA does not define the terms \"explosive\" or\n\n\"grenade.\"\n\n Section 5845(f) has two later sections that include\n\nother things as destructive devices:\n\n (2) any type of weapon by whatever name known\n which will, or which may be readily converted\n to, expel a projectile by the action of an\n explosive or other propellant, the barrel or\n barrels of which have a bore of more than one-\n half inch in diameter, except a shotgun or\n\n\n - 3 -\n\f shotgun shell which the Secretary finds is\n generally recognized as particularly suitable\n for sporting purposes; and\n (3) any combination of parts either designed\n or intended for use in converting any device\n into a destructive device as defined in\n subparagraphs (1) and (2) and from which a\n destructive device may be readily assembled.\n\nId. § 5845(f)(2)-(3).\n\n Following these terms, the statute has a separate\n\nsentence that excludes \"any device which is neither designed nor\n\nredesigned for use as a weapon\" and \"any device, although\n\noriginally designed for use as a weapon, which is redesigned for\n\nuse as a signaling, pyrotechnic, line throwing, safety, or similar\n\ndevice.\" Id. Those exclusions present affirmative defenses; they\n\ndo not define elements of the substantive offense. United States\n\nv. Beason, 690 F.2d 439, 445 (5th Cir. 1982).\n\n The NFA was not the first statute to deal with devices\n\nlike those at issue here. In April 1968, six months before\n\nCongress enacted the above \"destructive device\" provision,\n\nCongress made it a crime to, among other things, teach the \"use,\n\napplication, or making of any firearm or explosive or incendiary\n\ndevice.\" 18 U.S.C. § 231(a)(1). One such \"explosive or incendiary\n\ndevice\" is an \"explosive . . . grenade.\" 18 U.S.C. § 232(5)(B).\n\nCongress again addressed these devices when it enacted a\n\n\"destructive device\" provision as part of the gun control\n\nprovisions of the Omnibus Crime Control and Safe Streets Act of\n\n\n\n\n - 4 -\n\f1968. See Pub. L. No. 90-351, § 921(a)(4). Congress shortly\n\nthereafter added the same \"destructive device\" provision to the\n\nNFA with the Gun Control Act of 1968 (GCA). See United States v.\n\nOba, 448 F.2d 892, 893-94 (9th Cir. 1971).\n\n The GCA's purpose was \"to provide support to Federal,\n\nState, and local law enforcement officials in their fight against\n\ncrime and violence.\" Pub. L. No. 90-618, § 101. It represented\n\n\"a Congressional attempt to stem the traffic in dangerous weapons\n\nbeing used in an increasing number of crimes involving personal\n\ninjury.\" United States v. Posnjak, 457 F.2d 1110, 1113 (2d Cir.\n\n1972). And, in the GCA, Congress included the \"destructive device\"\n\nprovision at issue here to cover \"military-type weapons,\" id. at\n\n1115 (citing S. Rep. No. 90-1501, at 25, 30 (1968)), and\n\n\"objectively identifiable weapons of war,\" id. at 1116.\n\n Unlike with many other crimes, Congress chose not to\n\ncriminalize attempts to violate the GCA's destructive device\n\nprovision. A practical consequence of that decision is that agents\n\nengaged in undercover sting operations actually pass destructive\n\ndevices like explosive grenades to the target, which runs some\n\noperational risks. Law enforcement tries to reduce those risks to\n\nagents, targets, and the public by removing fuzes from otherwise\n\nlive grenades.\n\n\n\n\n - 5 -\n\fB. Background\n\n The essential facts are undisputed for our purposes and\n\nare worth repeating. The FBI replaced the grenades' original fuzes\n\nwith mechanically and visually identical, but inoperable, fuzes\n\nbefore giving them to Musso. Each grenade was, however, armed\n\nwith its original explosive charge of Composition B.1 Each grenade\n\ncould be made to explode by, for example, replacing the inoperable\n\nfuze with an operable one, by using a commercial or homemade\n\ndetonator, or by a sufficient impact. The government concedes\n\nthat the grenades as purchased by Musso would not have detonated\n\nabsent these other circumstances had Musso or anyone else merely\n\npulled their pins. A search of Musso's property following his\n\narrest did not turn up any fuzes or other detonators.\n\nC. Procedural History\n\n Musso moved to dismiss four counts of the resulting\n\nindictment, arguing that the grenades he received were not\n\n\"explosive grenades\" and so were not destructive devices under the\n\nNFA. On March 9, 2018, the district court granted Musso's motion\n\nto dismiss those counts. Musso, 2018 WL 1313977, at *8.\n\n\n\n\n 1 We deem Musso to have admitted this for purposes of the\nmotion to dismiss. We note that he has not pleaded guilty to the\nfifth count of his underlying indictment, which charges him with\nknowingly receiving \"approximately 26 ounces of Composition B high\nexplosive, contained within four grenades.\"\n\n\n - 6 -\n\f The district court consulted several dictionaries and\n\nconcluded that \"the ordinary meaning of 'grenade' implies a device\n\nthat contains not only explosive material but also a means of\n\ndetonating that explosive material.\" Id. at *5. The district\n\ncourt next reasoned that \"explosive,\" when modifying \"grenade,\"\n\nnecessarily implied that the grenade \"must, in fact, be capable of\n\nexploding.\" Id. Combining these understandings, the district\n\ncourt found that \"the ordinary meaning of the phrase 'explosive\n\ngrenade' . . . is a device that is in and of itself capable of\n\nexploding.\" Id. The district court then dismissed the counts.\n\nId. at *8.\n\n II.\n\n We clear away a preliminary procedural issue. Although\n\nwe have not before addressed the issue, other \"circuit courts have\n\nalmost uniformly concluded\" that, under Federal Rule of Criminal\n\nProcedure 12(b)(1), \"a district court may consider a pretrial\n\nmotion to dismiss an indictment where the government does not\n\ndispute the ability of the court to reach the motion and proffers,\n\nstipulates, or otherwise does not dispute the pertinent facts.\"\n\nUnited States v. Weaver, 659 F.3d 353, 355 n* (4th Cir. 2011)\n\n(collecting cases). We join this consensus.\n\n The facts necessary to resolve the issue now on appeal\n\nare not in dispute, and the government had requested that the\n\ndistrict court resolve the issue. We review the district court's\n\n\n - 7 -\n\fconclusion de novo, id. at 356, and determine that the court erred\n\nand so reverse.\n\n III.\n\n As framed, on admitted facts, the question before us is\n\nan issue of law. The government bears the burden of establishing\n\nthat the grenades here met the definition of \"explosive grenades.\"\n\nMusso, in turn, bears the burden as to whether the grenades fall\n\nwithin the exclusionary clause. On the facts presented, we reject\n\nMusso's definitional argument as well as his argument, based on\n\nthe exclusionary clause, that the FBI's removal of the grenades'\n\nfuzes means the grenades are not \"designed\" as weapons. In\n\naddressing his argument based on the exclusionary clause, we treat\n\nMusso as having raised that affirmative defense and bypass any\n\npotential forfeiture resulting from his failure to pursue that\n\nargument in his motion to dismiss.\n\n We begin, as always, with the statutory text concerning\n\n\"explosive grenades.\" The NFA definitional section requires that\n\nto be a \"destructive device,\" a grenade must be an \"explosive,\n\nincendiary, or poison gas . . . grenade.\" 26 U.S.C. § 5845(f).\n\nAnd an NFA \"destructive device\" must have been \"designed [or]\n\nredesigned for use as a weapon,\" and not, if originally designed\n\nas a weapon, \"redesigned for use as a signaling, pyrotechnic, line\n\nthrowing, safety, or similar device.\" Id. No issue is before us\n\nof the interpretation of other parts of the statute concerned with\n\n\n - 8 -\n\fother destructive devices or with the clause in Section 5845(f)(3)\n\nconcerning \"any combination of parts . . . from which a destructive\n\ndevice may be readily assembled.\"2\n\n We dispose of Musso's argument based on the statutory\n\nexclusion first. On these facts, we reject the argument that\n\nbecause the grenades' fuzes were inoperable, that meant the\n\ngrenades were \"redesigned\" so as not to be weapons. Congress only\n\nexcluded certain \"redesigned\" devices: those that have been\n\n\"redesigned for use as a signaling, pyrotechnic, line throwing,\n\nsafety, or similar device.\" 26 U.S.C. § 5845(f). There is no\n\ncontention here that Musso's devices were redesigned for any of\n\nthose purposes.\n\n Musso's grenades were designed as weapons. Each M67\n\ngrenade sold to Musso was a standard-issue Marine Corps weapon.\n\nThat the grenades were inoperable when purchased by Musso does not\n\nchange the fact that they were \"designed\" as weapons. Cf. United\n\nStates v. Rivera, 415 F.3d 284, 286 (2d Cir. 2005) (\"Where a weapon\n\ndesigned to fire a projectile is rendered inoperable, whether on\n\npurpose or by accident, . . . it continues to be 'designed' to\n\nfire a projectile.\"). We conclude that Musso's explosive grenades\n\nwere each \"designed . . . for use as a weapon,\" 26 U.S.C.\n\n§ 5845(f), and so were not excluded from the NFA's coverage.\n\n\n 2 Cases construing that clause, like United States v.\nPosnjak, 457 F.2d 1110 (2d Cir. 1972), are not relevant here.\n\n\n - 9 -\n\f We turn to the definitional arguments. Congress did\n\nnot, in the NFA, define the term \"explosive grenade.\" When\n\nCongress uses words that it does not define, \"we assume those words\n\n'carry their plain and ordinary meaning.'\" United States v.\n\nGordon, 875 F.3d 26, 33 (1st Cir. 2017) (quoting Stornawaye Fin.\n\nCorp. v. Hill (In re Hill), 562 F.3d 29, 32 (1st Cir. 2009)). The\n\ndistrict court reasoned \"that the ordinary meaning of the phrase\n\n'explosive grenade' in [Section] 5845(f) is a device that is in\n\nand of itself capable of exploding,\" Musso, 2018 WL 1313977, at\n\n*5, and \"that a destructive device must contain certain essential\n\ncomponents\" -- namely, a working fuze, id. at *6.\n\n The government challenges the district court's plain-\n\ntext reading here. We find that the plain meaning of the words\n\n\"explosive\" and \"grenade\" do not clearly exclude the devices Musso\n\npurchased -- M67 grenades with inoperable fuzes. We then assume\n\narguendo that the plain meaning of those words does not resolve\n\nthis case in the government's favor and so we turn to other\n\ntraditional tools of statutory interpretation. See Yates v. United\n\nStates, 135 S. Ct. 1074, 1081 (2015) (noting that the meaning of\n\na statutory term \"does not turn solely on dictionary definitions\n\nof [that term's] component words\"). We ultimately reject the\n\ndistrict court's glosses on the term \"explosive grenade\" because\n\nthey do not come from the NFA's text, \"and we may not engraft our\n\nown exceptions onto the statutory text.\" Henry Schein, Inc. v.\n\n\n - 10 -\n\fArcher & White Sales, Inc., No. 17-1272, 2019 WL 122164, at *5\n\n(U.S. Jan. 8, 2019). We conclude, looking to statutory context,\n\nthat Congress intended that the term \"explosive grenade\" include\n\nthe grenades as purchased by Musso.\n\n Where Congress wanted to define a device by its\n\ncapability, it said so explicitly. Under Section 5845(f)(2), a\n\nweapon with a \"bore of more than one-half inch in diameter\" is a\n\ndestructive device if it \"will, or . . . may be readily converted\n\nto, expel a projectile by the action of an explosive or other\n\npropellant.\" 26 U.S.C. § 5845(f)(2) (emphasis added). This is a\n\n\"test of objective capability,\" United States v. Crooker, 608 F.3d\n\n94, 98 & n.2 (1st Cir. 2010), and it is not unique to Section\n\n5845(f)(2). For instance, Section 5845(b) defines a machinegun as\n\n\"any weapon which shoots, is designed to shoot, or can be readily\n\nrestored to shoot, automatically more than one shot, without manual\n\nreloading, by a single function of the trigger.\" 26 U.S.C.\n\n§ 5845(b) (emphasis added). From the presence of capability\n\nrequirements throughout Section 5845, and particularly in Section\n\n5845(f)(2), we conclude that the absence of such a requirement in\n\nSection 5845(f)(1), the \"explosive grenade\" provision, is\n\nintentional. See New Prime Inc. v. Oliveira, No. 17-340, 2019 WL\n\n189342, at *7 (U.S. Jan. 15, 2019) (drawing a negative inference\n\nfrom word choices made in \"a neighboring term in the statutory\n\ntext\").\n\n\n - 11 -\n\f Next, the language of Section 5845(f) does not require\n\nthat an \"explosive grenade\" have specific parts, like a working\n\nfuze. Context immediately reinforces this conclusion: Under\n\nSection 5845(f)(1)(c), which directly follows the \"explosive\n\ngrenade\" provision, a rocket only qualifies as a destructive device\n\nif it has \"a propellent [sic] charge of more than four ounces.\"\n\n26 U.S.C. § 5845(f)(1)(C). And right after that, Congress required\n\nthat a missile have \"an explosive or incendiary charge of more\n\nthan one-quarter ounce.\" Id. § 5845(f)(1)(D). Section 5845 is\n\nfilled with similar requirements: A shotgun must have \"a barrel\n\nor barrels of less than 18 inches in length.\" Id. § 5845(a)(1).\n\nAnd a rifle must have \"a barrel or barrels of less than 16 inches\n\nin length.\" Id. § 5845(a)(3). Congress could easily have required\n\nthat an \"explosive grenade\" have a working fuze. We conclude that\n\nthe absence of any such requirement was intentional.\n\n We also consider the \"destructive device\" provision in\n\nthe sequence in which Congress wrote Section 5845(f). See New\n\nPrime, 2019 WL 189342, at *4 (analyzing a statute based on its\n\n\"terms and sequencing\"). Section 5845(f)(1) first covers a bomb,\n\ngrenade, rocket, missile, mine, or \"similar device.\" 26 U.S.C.\n\n§ 5845(f)(1). Section 5845(f)(2) then covers a weapon, \"by\n\nwhatever name known,\" that meets the capability test outlined\n\nabove. Id. § 5845(f)(2). And finally, Section 5845(f)(3) covers\n\n\"any combination of parts\" that can be \"readily assembled\" into\n\n\n - 12 -\n\fone of the devices described in the previous two sections. This\n\nsequence highlights that Section 5845(f)(1) was meant to cover\n\nweapons with evident, descriptive names, while 5845(f)(2) and\n\n(f)(3) are more in the nature of catch-all provisions meant to\n\nensure coverage where intended beyond the named devices in\n\n5845(f)(1). Because \"explosive grenade\" is sufficiently\n\ndescriptive to limit that provision's coverage, Congress did not\n\nadd a capability requirement or a parts requirement.\n\n Were there any doubt left, we would also note that\n\nSections 5845(f)(2) and (f)(3) include language like \"readily\n\nassembled\" or \"readily converted.\" The functional cast of that\n\nlanguage fits in those later catch-all provisions, which deal with\n\nall manner of weapons that have no evident name. But for Section\n\n5845(f)(1), no such modifying language was necessary.\n\n The district court's contrary view has further problems:\n\nIt reads the term \"explosive\" outside of its direct context. Our\n\ninterpretation avoids this problem. Looking again to neighboring\n\nterms, we conclude that \"explosive\" describes a category of\n\ngrenade. Section 5845(f)(1) prohibits the unregistered receipt or\n\npossession of not only an \"explosive . . . grenade,\" but also an\n\n\"incendiary . . . grenade\" or a \"poison gas . . . grenade.\" 26\n\nU.S.C. § 5845(f)(1)(B). The natural reading is that \"explosive\"\n\ndistinguishes one category of grenade covered by the statute from\n\nother categories of grenades, either within the statute (like\n\n\n - 13 -\n\fpoison gas grenades) or outside the statute's reach (like, perhaps,\n\nsmoke grenades). Cf. United States v. Williams, 553 U.S. 285, 294\n\n(2008) (\"[A] word is given more precise content by the neighboring\n\nwords with which it is associated.\"). On the facts presented here,\n\nthe district court's reading of the term \"explosive\" violates the\n\n\"fundamental principle of statutory construction . . . that the\n\nmeaning of a word cannot be determined in isolation.\" Yates, 135\n\nS. Ct. at 1082 (quoting Deal v. United States, 508 U.S. 129, 132\n\n(1993)).\n\n The reasoning we have provided suffices to support our\n\nconclusion that Musso's devices were \"explosive grenades,\" as\n\nCongress intended that term to be understood.3\n\n The district court attempted to support its\n\ninterpretation of \"explosive grenade\" by pointing to out-of-\n\ncircuit precedent. But none of the cases the court cited were\n\ndecided under Section 5845(f)(1)(b), the provision at issue here,\n\nand none involved grenades armed with their original explosive\n\ncharges. In United States v. Malone, 546 F.2d 1182 (5th Cir.\n\n1977), the defendant did not have, either in his possession or in\n\n\n 3 Musso argues that we should apply the rule of lenity.\nBut this rule \"applies only if, 'after considering text, structure,\nhistory and purpose, there remains a grievous ambiguity or\nuncertainty in the statute such that the Court must simply guess\nas to what Congress intended.'\" Abramski v. United States, 573\nU.S. 169, 188 n.10 (2014) (quoting Maracich v. Spears, 570 U.S.\n48, 76 (2013)). There is no grievous uncertainty here, so lenity\ndoes not apply.\n\n\n - 14 -\n\fthe devices at issue, any explosive material. Id. at 1184. In\n\nUnited States v. Blackburn, 940 F.2d 107 (4th Cir. 1991), a\n\nsentencing appeal following a guilty plea, there were twenty-eight\n\ninert grenade hulls that contained no explosive material. Id. at\n\n109. There was no proof there that the explosive charge within\n\ntwo live grenades could have been redistributed to make all thirty\n\ngrenades there active, and the quantity of destructive devices was\n\na factor in a sentencing enhancement. Id. at 110. And in United\n\nStates v. Osuna, 189 F.3d 1289 (10th Cir. 1999), the Tenth Circuit\n\nmerely accepted the government's concession that \"inert\" grenades\n\ndid not qualify as destructive devices (without defining \"inert\")\n\nand so did not support a sentencing enhancement. Id. at 1295.\n\nThese cases say nothing about whether Musso's grenades fall under\n\nthe statute.\n\n Further, United States v. Sheehan, 838 F.3d 109 (2d Cir.\n\n2016), supports our reasoning.4 The Second Circuit there held that\n\na nonfunctioning homemade bomb that contained an explosive charge\n\nbut had an inoperable fuze was an \"explosive bomb\" because it\n\n\n\n 4 We acknowledge that Sheehan involved the \"destructive\ndevice\" provision at 18 U.S.C. § 921(a)(4), enacted by the Omnibus\nCrime Control and Safe Streets Act of 1968. But Congress, when it\nadded the \"destructive device\" provision here to the NFA, copied\nthat earlier provision verbatim. And when a term \"is obviously\ntransplanted from another legal source, whether the common law or\nother legislation, it brings the old soil with it.\" Stokeling v.\nUnited States, No. 17-5554, 2019 WL 189343, at *5 (U.S. Jan. 15,\n2019) (quoting Hall v. Hall, 138 S. Ct. 1118, 1128 (2018)).\n\n\n - 15 -\n\fremained capable of detonating by other means. Id. at 119-20.\n\nThat the device \"could not explode in the way its maker might have\n\nassumed was the ordinary or even only way in which it could be\n\ndetonated -- i.e., via the fuzing system -- because it lacked a\n\nparticular component of which such a device is ordinarily composed\"\n\nwas \"irrelevant\" there. Id. So too here.5\n\n IV.\n\n With the NFA, Congress aimed to decrease threats to\n\npublic safety from destructive devices. These devices have been\n\nused for criminal conduct that has included robbery, S. Rep. No.\n\n90-1097, at 78 (1968) (describing the use of a \"Finnish Lahti\n\nantitank gun . . . in the robbery of a Brinks Co. installation\"),\n\nand the \"attempted assassination of a United States Attorney,\"\n\nUnited States v. Hamrick, 43 F.3d 877, 886 (4th Cir. 1995). And\n\nwhile we have no need to resort to legislative history, there is\n\ncongressional history \"to the effect that Congress intended to\n\nproscribe the activities generally associated with armed groups\n\ndevoted to disruption of public authority.\" Posnjak, 457 F.2d at\n\n\n\n 5 We do not rely on United States v. Rushcamp, 526 F.3d\n1380 (6th Cir. 1975), which the government cites. There, the Sixth\nCircuit concluded that an inoperable military munition -- a rocket\nlauncher with a broken firing mechanism -- was a destructive\ndevice. But that case turned on the language of Section (f)(2),\nwhich defines a rocket launcher as a destructive device if it \"may\nbe readily converted to, expel a projectile by action of an\nexplosive or other propellant,\" id. at 1382, and not the Section\nat issue here.\n\n\n - 16 -\n\f1120. But the district court's order would require agents\n\nconducting an undercover sting operation to give fully functional\n\n\"weapons of war,\" id. at 1116, like explosive grenades, to\n\npotential felons.\n\n The result reached by the district court is contrary to\n\nthe complete text and context of the NFA and is not what Congress\n\nintended. We reverse the dismissal of the counts against Musso,\n\nreinstate them, and remand for further proceedings consistent with\n\nthis opinion.\n\n\n\n\n - 17 -\n[END_CASE]", "role": "user" } ]
4,584,943
UNITED STATES of America, Appellee, v. Josue MARRERO-PÉREZ, Defendant, Appellant.
United States v. Marrero-Perez
2019-01-25
17-1346P
U.S. Court of Appeals for the First Circuit
{"judges": "Barron, Boudin, Torruella", "parties": "", "opinions": [{"author": "BOUDIN, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1346\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOSUE MARRERO-PÉREZ,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Torruella, Boudin, and Barron,\n Circuit Judges.\n\n\n Rick Nemcik-Cruz on brief for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Julia M. Meconiates, Assistant United\nStates Attorney, on brief for appellee.\n\n\n January 25, 2019\n\f BOUDIN, Circuit Judge. Police officers in Puerto Rico\n\nreceived a tip as to the whereabouts of Josue Marrero-Pérez\n\n(\"Marrero\"), who had left Delaware to evade arrest on an\n\noutstanding warrant. Locating him at his premises in Puerto Rico,\n\nthey discovered in plain view in the building a Glock pistol and\n\na Smith & Wesson semiautomatic pistol, each loaded with ammunition.\n\nThey arrested him and a grand jury indicted him on two counts of\n\npossessing a firearm while prohibited from doing so because of a\n\nprior felony conviction, 18 U.S.C. § 922(g)(1), and because of his\n\nfugitive status, id. § 922(g)(2).\n\n Without a plea bargain, Marrero pled guilty to both\n\ncharges. The final presentence investigation report (\"PSR\")\n\nrecommended that the guidelines range be fixed at 37-46 months in\n\nprison, based on a recommended total offense level of 17 and a\n\nrecommended criminal history category of IV. The probation\n\nofficer's report set out an ominous criminal record, some of whose\n\ndetail and characterizations Marrero disputes in this appeal.\n\nAccording to the report, as a juvenile Marrero behaved violently\n\nand was arrested regularly, and as an adult he had been convicted\n\ntwenty times including for assault, drug violations, resisting\n\narrests and possessing a firearm with an obliterated serial number.\n\n The PSR advised that Marrero's category IV designation\n\nsubstantially understated his criminal history and likelihood of\n\nfurther crimes, suggesting as options an upward departure or a\n\n\n - 2 -\n\fvariant sentence. The PSR had been available to Marrero and his\n\nlawyer but no objection was made to the report, and at sentencing\n\ndefense counsel stated that he had reviewed the PSR prior to that\n\nhearing. He did not object to the report at any time before the\n\nsentence.\n\n At sentencing, after hearing Marrero's allocution and\n\nhis lawyer's request for a sentence at the lower end of the\n\nproposed range, the court said that Marrero's record called for an\n\nupward departure. See U.S.S.G. § 4A1.3(a)(1). As the judge\n\nconcluded at sentencing,\n\n Mr. Marrero's vast prior record, as reflected in the\n pre-sentence investigation report and history of\n convictions, indicates that his Criminal History\n Category substantially underrepresents the seriousness\n of his offense or the likelihood that he will commit\n other crimes. . . . Mr. Marrero has been arrested at\n least 44 times during his life . . . . As an adult, Mr.\n Marrero has more than 20 convictions . . . . According\n to documentation received from the probation officer, in\n the District of Delaware, Mr. Marrero has the following\n known history of warrants: 25 failure to appear, 13\n violations of probation, and 28 failures to pay, all of\n which is consistent with Mr. Marrero's utter disregard\n for the law and high[] likelihood of recidivism.\n\n The district court imposed a variant sentence of 72\n\nmonths, itself in excess of the 60-month upward variance proposed\n\nby the government. The most difficult issue on this appeal\n\nconcerns the possibility that the judge at sentencing relied in\n\nhis upward variance on prior arrests of the defendant which did\n\n\n\n\n - 3 -\n\fnot result in convictions; Marrero also objects to a lack of detail\n\nin other cases where the conviction is conceded.\n\n In addition to the PSR, documents concerning\n\noutstanding warrants in Delaware were apparently provided by the\n\nprobation officer to the court; this information was not included\n\nin the PSR but was referred to by the court at sentencing. Marrero\n\nnow suggests that it is a \"fair inference\" from the sentencing\n\ntranscript that these documents were provided to the court ex parte\n\nand should have been tested at a hearing.\n\n Marrero's strongest arguments are that the sentencing\n\njudge (1) relied on past arrests listed in the PSR (usually\n\ninvolving at worst trivial conduct), many of which did not result\n\nin prosecution or conviction, and (2) relied on ex parte documents\n\nwhich were not timely disclosed to the defense.\n\n We agree that as a matter of judicial policy, in this\n\ncase and henceforth, no weight should be given in sentencing to\n\narrests not buttressed by convictions or independent proof of\n\nconduct. See U.S.S.G. § 4A1.3(a)(3). In certain perhaps rare\n\ncases, a reasonable person might in particular circumstances\n\nassign some weight to a collection of arrests, but no such argument\n\nis made or available here. To rely on acquitted conduct in\n\nsentencing was troublesome enough even where the government needed\n\nto provide only preponderant proof rather than proof beyond a\n\n\n\n\n - 4 -\n\freasonable doubt, see United States v. Watts, 519 U.S. 148, 152\n\n(1997) (per curiam); proof only of an arrest is no proof of guilt.\n\n As for lack of detail, the PSR offers nothing as to the\n\nsubstance of the juvenile conduct for seven of the ten arrests;\n\nand no facts are provided for ten of the twenty adult convictions\n\nbeyond the fact of conviction; whether in most cases more is\n\nrequired is more doubtful. But other arrests resulted in\n\nproceedings that were nolle prossed or otherwise terminated\n\nwithout a trial or a guilty plea.\n\n Subtracting allegations in the PSR for which there are\n\nno detailed records or for which no conviction resulted, much\n\nremains that is unhelpful to Marrero, and serious prior crimes and\n\nrecidivist behavior are of course proper considerations at\n\nsentencing. 18 U.S.C. § 3553(a)(1)-(2)(C). How unhelpful is a\n\njudgment call largely confided to the sentencing judge, who is in\n\na good position to make such individualized assessments. See Gall\n\nv. United States, 552 U.S. 38, 51-52 (2007).\n\n Reliance on arrests alone or other dubious inferences to\n\nenhance a criminal sentence might be thought to offend the often\n\ninvoked \"presumption of innocence,\" but historically the\n\npresumption has governed only the trial itself. United States v.\n\nDoyle, 348 F.2d 715, 721 (2d Cir. 1965) (Friendly, J.). Thus, at\n\nsentencing judges have long been free to rely on anything useful\n\n\n\n\n - 5 -\n\fthat is established by a preponderance of the evidence, without\n\nregard to ordinary rules of trial evidence.1\n\n The line between the criminal trial itself and almost\n\neverything afterwards is sharp, enshrining the care and protection\n\nafforded to the defendant at the trial. The comparative\n\ninformality of everything after the guilty verdict has practical\n\nadvantages and is too well settled for debate. The Supreme Court\n\nmay on a rare occasion arguably seem to extend the presumption of\n\ninnocence beyond its historical core, see, e.g., Nelson v.\n\nColorado, 137 S. Ct. 1249 (2017), but not yet in any discernable\n\npattern directly relevant to a sentencing hearing.\n\n Marrero's failure to object to the sentence based on\n\nthe judge's possible reliance on arrests not resulting in\n\nconviction does not insulate the district judge's purported error\n\nfrom review by this court--even under the plain error test--and\n\nthis circuit has several times warned over a three-year period\n\nagainst reliance on arrests as a proxy for criminal culpability or\n\nthe likelihood of recidivism. United States v. Rondón-García, 886\n\nF.3d 14, 25-26 (1st Cir. 2018); United States v. Delgado-Sánchez,\n\n849 F.3d 1, 13 (1st Cir. 2017); United States v. Cortés-Medina,\n\n\n 1See McMillan v. Pennsylvania, 477 U.S. 79, 91 (1986); Taylor\nv. Kentucky, 436 U.S. 478, 483 n.12 (1978); United States v.\nGonzalez-Vazquez, 34 F.3d 19, 25 (1st Cir. 1994); see also In re\nWhitney, 421 F.2d 337, 338 (1st Cir. 1970) (presumption of\ninnocence does not apply to probation revocation).\n\n\n\n - 6 -\n\f819 F.3d 566, 570 (1st Cir. 2016). In sum, to equate arrest with\n\nguilt is by now both error and obviously so.\n\n Material about past offenses may be furnished wholesale\n\nto the probation officer by the government's lawyer and probably\n\nas often adopted by the probation officer without much scrutiny--\n\ncounting on defense counsel to object if warranted. So far as\n\nappears, no such objection was advanced here, so the judge ended\n\nup with a package of allegations, correctly believing that defense\n\ncounsel never disputed the underlying facts or the negative\n\ninferences one might draw from them. The crimes proved by adult\n\nconvictions, without more, may well have justified an upward\n\nvariance. U.S.S.G. § 4A1.3(a)(1). This is a classic issue for the\n\ndistrict judge and would be tested, even if the objection had been\n\nmade and preserved, only for abuse of discretion. See United\n\nStates v. Vázquez-Martínez, 812 F.3d 18, 26 (1st Cir. 2016).\n\n Given the lack of objection, the ordinary test is for\n\nplain error, United States v. Sosa-González, 900 F.3d 1, 4 (1st\n\nCir. 2018), which requires that a defendant show that (1) an error\n\noccurred, (2) the error was obvious, (3) the error affected\n\nsubstantial rights, and (4) the error seriously impaired the\n\nfairness, integrity, or public reputation of judicial proceedings,\n\nsee Constant v. United States, 814 F.3d 570, 580 (1st Cir. 2016).\n\nOther statements by this court stress particular aspects of the\n\n\n\n\n - 7 -\n\ftest pertinent to the case at hand, but the stress is almost always\n\non one or more of the factors set forth in Constant.2\n\n Applying the Constant formulation, we think that an\n\nerror occurs when a district judge relies on an arrest report,\n\nwithout some greater indicia of reliability that the conduct\n\nunderlying the arrest took place; the \"obviousness\" of the error\n\nis a matter of degree but becomes greater with every new case;\n\nwhether the error affects the outcome depends on the facts peculiar\n\nto the case (e.g., the presence or absence of corroborating\n\nevidence in the record concerning the conduct underlying the\n\narrests without convictions); and the fourth factor--the\n\n\"miscarriage of justice\" standard, Alicea, 205 F.3d at 484--is\n\nimplicated if the sentence has truly been altered by the arrests,\n\nitself a matter that the district judge can readily lay to rest on\n\nremand.\n\n While the record permitted a variance upward on the basis\n\nof convictions, we think that Marrero has made a strong enough\n\ncase that the sentencing judge relied on these past arrests in\n\n\n\n\n 2 See Rondón-García, 886 F.3d at 24 (noting that for an error\nto have affected a defendant's substantial rights, a defendant\nmust show that there is a \"reasonable probability that, but for\nthe error, the district court would have imposed a more favorable\nsentence\" (internal quotation marks omitted)); United States v.\nSaxena, 229 F.3d 1, 5 (1st Cir. 2000) (describing the final prong\nof the plain error test as a \"miscarriage-of-justice standard\"\n(citing United States v. Alicea, 205 F.3d 480, 484 (1st Cir.\n2000))).\n\n\n - 8 -\n\fdetermining the sentence. Here, the specific conduct underlying\n\nthe dismissed charges was not, as sometimes happens, set forth in\n\nundisputed portions the PSR. See Mercer v. United States, 834\n\nF.3d 39, 50 (1st Cir. 2016). Finally, the sentencing judge stated\n\non the record that \"Mr. Marrero's vast prior record\" and the fact\n\nthat he \"has been arrested at least 44 times during his life,\"\n\nalong with other factors, were \"consistent with [his] utter\n\ndisregard for the law and high[] likelihood of recidivism.\"\n\n It is enough to warrant a remand that the reliance on\n\nsuch arrests--now an obvious error--\"set the wrong framework for\n\nthe sentencing proceedings,\" Molina-Martinez v. United States, 136\n\nS. Ct. 1338, 1345 (2016). Marrero is not in turn required to show\n\nthat this obvious error in fact influenced the length of the\n\nsentence, a showing that in most cases will be nearly impossible\n\nfor a defendant to make given the kitchen-sink approach to\n\nsentencing pronouncements adopted by many judges. Cf. id. at 1347.\n\n While the lack of objections throughout usually would\n\ndefeat a defendant's effort to seek a remand, this course would\n\nmerely defer the matter to a likely habeas proceeding directed at\n\ntrial counsel's competence. A predictable habeas petition would\n\nprolong and further complicate proceedings and ultimately cost\n\ntime and trouble for judge and counsel alike, and the defendant\n\nwould already be serving his sentence when, a year or two later,\n\nhe would discover its duration.\n\n\n - 9 -\n\f Our concerns are reinforced not by the lack of detail\n\nregarding the facts underlying the convictions--that is common,\n\nsee, e.g., United States v. Turbides-Leonardo, 468 F.3d 34, 37\n\n(1st Cir. 2006), and only occasionally troublesome--but by the\n\nsecond argument raised by Marrero, that is, the still not fully\n\nexplained material submitted ex parte by the probation officer to\n\nthe court concerning certain outstanding warrants in Delaware.\n\nThe record is not clear on this point, but it appears that defense\n\ncounsel did not object at the sentencing hearing. Rather, at the\n\nend of miscellany (e.g., which prison the judge might recommend\n\nfor Marrero), defense counsel said only that he wanted some\n\ndocumentation that the probation officer had employed (it appears\n\nthat defense counsel had declined earlier to review it). He did\n\nask for his own copy at the end of the hearing and this the court\n\ngranted.\n\n A remanding appeals court has authority to shape a remand\n\nas circumstances warrant, see United States v. Correy, 570 F.3d\n\n373, 378 (1st Cir. 2009). Whether or not the conduct underlying\n\nthe prior arrests can be shown by a preponderance of the evidence\n\n--and whether that matters to the district judge--is for him to\n\nsay on remand, but either way public confidence will be served by\n\nan explicit answer. The defendant can also pursue the issue of\n\nthe basis and impact of the ex parte material; but here the\n\n\n\n\n - 10 -\n\fdistrict judge is free to take into account the lack of timely\n\nobjection.\n\n Ex parte communication between the probation officer and\n\nthe court is usually permissible where the court is merely seeking\n\nadvice or analysis, United States v. Bramley, 847 F.3d 1, 7 (1st\n\nCir. 2017); to some extent the probation office is an extension of\n\nthe district court, see United States v. Saxena, 229 F.3d 1, 5 n.1\n\n(1st Cir. 2000), and the probation officer and the court may\n\nconsult privately about certain issues incident to criminal\n\nsentencing, see United States v. Fraza, 106 F.3d 1050, 1056 (1st\n\nCir. 1997). But where the probation officer discloses new facts\n\nthat bear on the judge's sentencing calculus, cf. United States v.\n\nCraven, 239 F.3d 91, 102 (1st Cir. 2001), the general rule requires\n\ndisclosure to the defense in advance of the sentencing hearing and\n\nan opportunity to subject the new material \"to whatever adversarial\n\ntesting may be appropriate,\" Bramley, 847 F.3d at 7.\n\n The ex parte material in this case, the outstanding\n\nwarrants in Delaware, are pretty thin as against defendant's own\n\ncriminal record but might suggest a proclivity for lawlessness or\n\nat best a disrespect for the court system. If the information\n\nabout the warrants was not included elsewhere in the record or\n\nmade known to Marrero prior to sentencing, reliance on this\n\ninformation at sentencing would also have been error. See United\n\nStates v. Millán-Isaac, 749 F.3d 57, 70 (1st Cir. 2014).\n\n\n - 11 -\n\f Marrero's counsel may well have received adequate\n\nadvanced notice of the ex parte material and simply declined to\n\nreview it, as was true with other material; Marrero says only that\n\nit is a \"fair inference\" from the sentencing transcript that the\n\nmaterial was provided ex parte. Whatever happened, the facts and\n\nthe consequences are for the district court's consideration on\n\nremand.\n\n The sentence is vacated and the matter remanded for\n\nresentencing in accordance with this decision. It is so ordered.\n\n\n\n\n - 12 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362196/", "author_raw": "BOUDIN, Circuit Judge"}]}
BARRON
BOUDIN
TORRUELLA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584943/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellee, v. Josue MARRERO-PÉREZ, Defendant, Appellant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 17-1346\n\n UNITED STATES OF AMERICA,\n\n Appellee,\n\n v.\n\n JOSUE MARRERO-PÉREZ,\n\n Defendant, Appellant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Francisco A. Besosa, U.S. District Judge]\n\n\n Before\n\n Torruella, Boudin, and Barron,\n Circuit Judges.\n\n\n Rick Nemcik-Cruz on brief for appellant.\n Rosa Emilia Rodríguez-Vélez, United States Attorney, Mariana\nE. Bauzá-Almonte, Assistant United States Attorney, Chief,\nAppellate Division, and Julia M. Meconiates, Assistant United\nStates Attorney, on brief for appellee.\n\n\n January 25, 2019\n\f BOUDIN, Circuit Judge. Police officers in Puerto Rico\n\nreceived a tip as to the whereabouts of Josue Marrero-Pérez\n\n(\"Marrero\"), who had left Delaware to evade arrest on an\n\noutstanding warrant. Locating him at his premises in Puerto Rico,\n\nthey discovered in plain view in the building a Glock pistol and\n\na Smith & Wesson semiautomatic pistol, each loaded with ammunition.\n\nThey arrested him and a grand jury indicted him on two counts of\n\npossessing a firearm while prohibited from doing so because of a\n\nprior felony conviction, 18 U.S.C. § 922(g)(1), and because of his\n\nfugitive status, id. § 922(g)(2).\n\n Without a plea bargain, Marrero pled guilty to both\n\ncharges. The final presentence investigation report (\"PSR\")\n\nrecommended that the guidelines range be fixed at 37-46 months in\n\nprison, based on a recommended total offense level of 17 and a\n\nrecommended criminal history category of IV. The probation\n\nofficer's report set out an ominous criminal record, some of whose\n\ndetail and characterizations Marrero disputes in this appeal.\n\nAccording to the report, as a juvenile Marrero behaved violently\n\nand was arrested regularly, and as an adult he had been convicted\n\ntwenty times including for assault, drug violations, resisting\n\narrests and possessing a firearm with an obliterated serial number.\n\n The PSR advised that Marrero's category IV designation\n\nsubstantially understated his criminal history and likelihood of\n\nfurther crimes, suggesting as options an upward departure or a\n\n\n - 2 -\n\fvariant sentence. The PSR had been available to Marrero and his\n\nlawyer but no objection was made to the report, and at sentencing\n\ndefense counsel stated that he had reviewed the PSR prior to that\n\nhearing. He did not object to the report at any time before the\n\nsentence.\n\n At sentencing, after hearing Marrero's allocution and\n\nhis lawyer's request for a sentence at the lower end of the\n\nproposed range, the court said that Marrero's record called for an\n\nupward departure. See U.S.S.G. § 4A1.3(a)(1). As the judge\n\nconcluded at sentencing,\n\n Mr. Marrero's vast prior record, as reflected in the\n pre-sentence investigation report and history of\n convictions, indicates that his Criminal History\n Category substantially underrepresents the seriousness\n of his offense or the likelihood that he will commit\n other crimes. . . . Mr. Marrero has been arrested at\n least 44 times during his life . . . . As an adult, Mr.\n Marrero has more than 20 convictions . . . . According\n to documentation received from the probation officer, in\n the District of Delaware, Mr. Marrero has the following\n known history of warrants: 25 failure to appear, 13\n violations of probation, and 28 failures to pay, all of\n which is consistent with Mr. Marrero's utter disregard\n for the law and high[] likelihood of recidivism.\n\n The district court imposed a variant sentence of 72\n\nmonths, itself in excess of the 60-month upward variance proposed\n\nby the government. The most difficult issue on this appeal\n\nconcerns the possibility that the judge at sentencing relied in\n\nhis upward variance on prior arrests of the defendant which did\n\n\n\n\n - 3 -\n\fnot result in convictions; Marrero also objects to a lack of detail\n\nin other cases where the conviction is conceded.\n\n In addition to the PSR, documents concerning\n\noutstanding warrants in Delaware were apparently provided by the\n\nprobation officer to the court; this information was not included\n\nin the PSR but was referred to by the court at sentencing. Marrero\n\nnow suggests that it is a \"fair inference\" from the sentencing\n\ntranscript that these documents were provided to the court ex parte\n\nand should have been tested at a hearing.\n\n Marrero's strongest arguments are that the sentencing\n\njudge (1) relied on past arrests listed in the PSR (usually\n\ninvolving at worst trivial conduct), many of which did not result\n\nin prosecution or conviction, and (2) relied on ex parte documents\n\nwhich were not timely disclosed to the defense.\n\n We agree that as a matter of judicial policy, in this\n\ncase and henceforth, no weight should be given in sentencing to\n\narrests not buttressed by convictions or independent proof of\n\nconduct. See U.S.S.G. § 4A1.3(a)(3). In certain perhaps rare\n\ncases, a reasonable person might in particular circumstances\n\nassign some weight to a collection of arrests, but no such argument\n\nis made or available here. To rely on acquitted conduct in\n\nsentencing was troublesome enough even where the government needed\n\nto provide only preponderant proof rather than proof beyond a\n\n\n\n\n - 4 -\n\freasonable doubt, see United States v. Watts, 519 U.S. 148, 152\n\n(1997) (per curiam); proof only of an arrest is no proof of guilt.\n\n As for lack of detail, the PSR offers nothing as to the\n\nsubstance of the juvenile conduct for seven of the ten arrests;\n\nand no facts are provided for ten of the twenty adult convictions\n\nbeyond the fact of conviction; whether in most cases more is\n\nrequired is more doubtful. But other arrests resulted in\n\nproceedings that were nolle prossed or otherwise terminated\n\nwithout a trial or a guilty plea.\n\n Subtracting allegations in the PSR for which there are\n\nno detailed records or for which no conviction resulted, much\n\nremains that is unhelpful to Marrero, and serious prior crimes and\n\nrecidivist behavior are of course proper considerations at\n\nsentencing. 18 U.S.C. § 3553(a)(1)-(2)(C). How unhelpful is a\n\njudgment call largely confided to the sentencing judge, who is in\n\na good position to make such individualized assessments. See Gall\n\nv. United States, 552 U.S. 38, 51-52 (2007).\n\n Reliance on arrests alone or other dubious inferences to\n\nenhance a criminal sentence might be thought to offend the often\n\ninvoked \"presumption of innocence,\" but historically the\n\npresumption has governed only the trial itself. United States v.\n\nDoyle, 348 F.2d 715, 721 (2d Cir. 1965) (Friendly, J.). Thus, at\n\nsentencing judges have long been free to rely on anything useful\n\n\n\n\n - 5 -\n\fthat is established by a preponderance of the evidence, without\n\nregard to ordinary rules of trial evidence.1\n\n The line between the criminal trial itself and almost\n\neverything afterwards is sharp, enshrining the care and protection\n\nafforded to the defendant at the trial. The comparative\n\ninformality of everything after the guilty verdict has practical\n\nadvantages and is too well settled for debate. The Supreme Court\n\nmay on a rare occasion arguably seem to extend the presumption of\n\ninnocence beyond its historical core, see, e.g., Nelson v.\n\nColorado, 137 S. Ct. 1249 (2017), but not yet in any discernable\n\npattern directly relevant to a sentencing hearing.\n\n Marrero's failure to object to the sentence based on\n\nthe judge's possible reliance on arrests not resulting in\n\nconviction does not insulate the district judge's purported error\n\nfrom review by this court--even under the plain error test--and\n\nthis circuit has several times warned over a three-year period\n\nagainst reliance on arrests as a proxy for criminal culpability or\n\nthe likelihood of recidivism. United States v. Rondón-García, 886\n\nF.3d 14, 25-26 (1st Cir. 2018); United States v. Delgado-Sánchez,\n\n849 F.3d 1, 13 (1st Cir. 2017); United States v. Cortés-Medina,\n\n\n 1See McMillan v. Pennsylvania, 477 U.S. 79, 91 (1986); Taylor\nv. Kentucky, 436 U.S. 478, 483 n.12 (1978); United States v.\nGonzalez-Vazquez, 34 F.3d 19, 25 (1st Cir. 1994); see also In re\nWhitney, 421 F.2d 337, 338 (1st Cir. 1970) (presumption of\ninnocence does not apply to probation revocation).\n\n\n\n - 6 -\n\f819 F.3d 566, 570 (1st Cir. 2016). In sum, to equate arrest with\n\nguilt is by now both error and obviously so.\n\n Material about past offenses may be furnished wholesale\n\nto the probation officer by the government's lawyer and probably\n\nas often adopted by the probation officer without much scrutiny--\n\ncounting on defense counsel to object if warranted. So far as\n\nappears, no such objection was advanced here, so the judge ended\n\nup with a package of allegations, correctly believing that defense\n\ncounsel never disputed the underlying facts or the negative\n\ninferences one might draw from them. The crimes proved by adult\n\nconvictions, without more, may well have justified an upward\n\nvariance. U.S.S.G. § 4A1.3(a)(1). This is a classic issue for the\n\ndistrict judge and would be tested, even if the objection had been\n\nmade and preserved, only for abuse of discretion. See United\n\nStates v. Vázquez-Martínez, 812 F.3d 18, 26 (1st Cir. 2016).\n\n Given the lack of objection, the ordinary test is for\n\nplain error, United States v. Sosa-González, 900 F.3d 1, 4 (1st\n\nCir. 2018), which requires that a defendant show that (1) an error\n\noccurred, (2) the error was obvious, (3) the error affected\n\nsubstantial rights, and (4) the error seriously impaired the\n\nfairness, integrity, or public reputation of judicial proceedings,\n\nsee Constant v. United States, 814 F.3d 570, 580 (1st Cir. 2016).\n\nOther statements by this court stress particular aspects of the\n\n\n\n\n - 7 -\n\ftest pertinent to the case at hand, but the stress is almost always\n\non one or more of the factors set forth in Constant.2\n\n Applying the Constant formulation, we think that an\n\nerror occurs when a district judge relies on an arrest report,\n\nwithout some greater indicia of reliability that the conduct\n\nunderlying the arrest took place; the \"obviousness\" of the error\n\nis a matter of degree but becomes greater with every new case;\n\nwhether the error affects the outcome depends on the facts peculiar\n\nto the case (e.g., the presence or absence of corroborating\n\nevidence in the record concerning the conduct underlying the\n\narrests without convictions); and the fourth factor--the\n\n\"miscarriage of justice\" standard, Alicea, 205 F.3d at 484--is\n\nimplicated if the sentence has truly been altered by the arrests,\n\nitself a matter that the district judge can readily lay to rest on\n\nremand.\n\n While the record permitted a variance upward on the basis\n\nof convictions, we think that Marrero has made a strong enough\n\ncase that the sentencing judge relied on these past arrests in\n\n\n\n\n 2 See Rondón-García, 886 F.3d at 24 (noting that for an error\nto have affected a defendant's substantial rights, a defendant\nmust show that there is a \"reasonable probability that, but for\nthe error, the district court would have imposed a more favorable\nsentence\" (internal quotation marks omitted)); United States v.\nSaxena, 229 F.3d 1, 5 (1st Cir. 2000) (describing the final prong\nof the plain error test as a \"miscarriage-of-justice standard\"\n(citing United States v. Alicea, 205 F.3d 480, 484 (1st Cir.\n2000))).\n\n\n - 8 -\n\fdetermining the sentence. Here, the specific conduct underlying\n\nthe dismissed charges was not, as sometimes happens, set forth in\n\nundisputed portions the PSR. See Mercer v. United States, 834\n\nF.3d 39, 50 (1st Cir. 2016). Finally, the sentencing judge stated\n\non the record that \"Mr. Marrero's vast prior record\" and the fact\n\nthat he \"has been arrested at least 44 times during his life,\"\n\nalong with other factors, were \"consistent with [his] utter\n\ndisregard for the law and high[] likelihood of recidivism.\"\n\n It is enough to warrant a remand that the reliance on\n\nsuch arrests--now an obvious error--\"set the wrong framework for\n\nthe sentencing proceedings,\" Molina-Martinez v. United States, 136\n\nS. Ct. 1338, 1345 (2016). Marrero is not in turn required to show\n\nthat this obvious error in fact influenced the length of the\n\nsentence, a showing that in most cases will be nearly impossible\n\nfor a defendant to make given the kitchen-sink approach to\n\nsentencing pronouncements adopted by many judges. Cf. id. at 1347.\n\n While the lack of objections throughout usually would\n\ndefeat a defendant's effort to seek a remand, this course would\n\nmerely defer the matter to a likely habeas proceeding directed at\n\ntrial counsel's competence. A predictable habeas petition would\n\nprolong and further complicate proceedings and ultimately cost\n\ntime and trouble for judge and counsel alike, and the defendant\n\nwould already be serving his sentence when, a year or two later,\n\nhe would discover its duration.\n\n\n - 9 -\n\f Our concerns are reinforced not by the lack of detail\n\nregarding the facts underlying the convictions--that is common,\n\nsee, e.g., United States v. Turbides-Leonardo, 468 F.3d 34, 37\n\n(1st Cir. 2006), and only occasionally troublesome--but by the\n\nsecond argument raised by Marrero, that is, the still not fully\n\nexplained material submitted ex parte by the probation officer to\n\nthe court concerning certain outstanding warrants in Delaware.\n\nThe record is not clear on this point, but it appears that defense\n\ncounsel did not object at the sentencing hearing. Rather, at the\n\nend of miscellany (e.g., which prison the judge might recommend\n\nfor Marrero), defense counsel said only that he wanted some\n\ndocumentation that the probation officer had employed (it appears\n\nthat defense counsel had declined earlier to review it). He did\n\nask for his own copy at the end of the hearing and this the court\n\ngranted.\n\n A remanding appeals court has authority to shape a remand\n\nas circumstances warrant, see United States v. Correy, 570 F.3d\n\n373, 378 (1st Cir. 2009). Whether or not the conduct underlying\n\nthe prior arrests can be shown by a preponderance of the evidence\n\n--and whether that matters to the district judge--is for him to\n\nsay on remand, but either way public confidence will be served by\n\nan explicit answer. The defendant can also pursue the issue of\n\nthe basis and impact of the ex parte material; but here the\n\n\n\n\n - 10 -\n\fdistrict judge is free to take into account the lack of timely\n\nobjection.\n\n Ex parte communication between the probation officer and\n\nthe court is usually permissible where the court is merely seeking\n\nadvice or analysis, United States v. Bramley, 847 F.3d 1, 7 (1st\n\nCir. 2017); to some extent the probation office is an extension of\n\nthe district court, see United States v. Saxena, 229 F.3d 1, 5 n.1\n\n(1st Cir. 2000), and the probation officer and the court may\n\nconsult privately about certain issues incident to criminal\n\nsentencing, see United States v. Fraza, 106 F.3d 1050, 1056 (1st\n\nCir. 1997). But where the probation officer discloses new facts\n\nthat bear on the judge's sentencing calculus, cf. United States v.\n\nCraven, 239 F.3d 91, 102 (1st Cir. 2001), the general rule requires\n\ndisclosure to the defense in advance of the sentencing hearing and\n\nan opportunity to subject the new material \"to whatever adversarial\n\ntesting may be appropriate,\" Bramley, 847 F.3d at 7.\n\n The ex parte material in this case, the outstanding\n\nwarrants in Delaware, are pretty thin as against defendant's own\n\ncriminal record but might suggest a proclivity for lawlessness or\n\nat best a disrespect for the court system. If the information\n\nabout the warrants was not included elsewhere in the record or\n\nmade known to Marrero prior to sentencing, reliance on this\n\ninformation at sentencing would also have been error. See United\n\nStates v. Millán-Isaac, 749 F.3d 57, 70 (1st Cir. 2014).\n\n\n - 11 -\n\f Marrero's counsel may well have received adequate\n\nadvanced notice of the ex parte material and simply declined to\n\nreview it, as was true with other material; Marrero says only that\n\nit is a \"fair inference\" from the sentencing transcript that the\n\nmaterial was provided ex parte. Whatever happened, the facts and\n\nthe consequences are for the district court's consideration on\n\nremand.\n\n The sentence is vacated and the matter remanded for\n\nresentencing in accordance with this decision. It is so ordered.\n\n\n\n\n - 12 -\n[END_CASE]", "role": "user" } ]
4,584,944
Olga TORRES; Pedro Bonilla, Plaintiffs, Appellants, v. BELLA VISTA HOSPITAL, INC. ; Banco Popular De Puerto Rico; The Watson Wyatt Company; Rubén Peréz; Johana Doe 1; Conjugal Partnership Peréz-Doe 1, Defendants, Appellees, the Antillian Union Conference of the Seven Day Adventist; The Retirement Committee of the General Conference of the Seventh Day Adventists Interamerican Division; The General Conference of the Seventh Day Adventist; Bella Vista Pension Plan and Trust; The Adventist of the Seventh Day Interamerican Division Retirement Plan; Bella Vista Hospital, Inc. 401k Plan and Trust; Pannell Kerr & Foster, L.L.P.; Miguel Ramos; Johana Doe; Conjugal Partnership Ramos-Doe, Defendants.
Torres v. Bella Vista Hospital, Inc.
2019-01-25
16-2316P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Boudin, Barron", "parties": "", "opinions": [{"author": "BOUDIN, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 16-2316\n\n OLGA TORRES; PEDRO BONILLA,\n\n Plaintiffs, Appellants,\n\n v.\n\n BELLA VISTA HOSPITAL, INC.; BANCO POPULAR DE PUERTO RICO;\n THE WATSON WYATT COMPANY; RUBÉN PERÉZ; JOHANA DOE 1;\n CONJUGAL PARTNERSHIP PERÉZ-DOE 1,\n\n Defendants, Appellees,\n\n THE ANTILLIAN UNION CONFERENCE OF THE SEVEN DAY ADVENTIST; THE\n RETIREMENT COMMITTEE OF THE GENERAL CONFERENCE OF THE SEVENTH\nDAY ADVENTISTS INTERAMERICAN DIVISION; THE GENERAL CONFERENCE OF\n THE SEVENTH DAY ADVENTIST; BELLA VISTA PENSION PLAN AND TRUST;\n THE ADVENTIST OF THE SEVENTH DAY INTERAMERICAN DIVISION\nRETIREMENT PLAN; BELLA VISTA HOSPITAL, INC. 401K PLAN AND TRUST;\n PANNELL KERR & FOSTER, L.L.P.; MIGUEL RAMOS; JOHANA DOE;\n CONJUGAL PARTNERSHIP RAMOS-DOE,\n\n Defendants.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Jay A. García-Gregory, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Boudin and Barron, Circuit Judges.\n\n\n Luis A. Vivaldi Oliver on brief for appellants.\n Carlos G. Martínez-Vivas on brief for appellees Bella Vista\n\fHospital, Inc.; Ruben Perez; Johana Doe 1; and Conjugal Partnership\nPerez-Doe 1.\n Cristina S. Belaval-Burger on brief for appellee Banco\nPopular de Puerto Rico.\n Juan A. Marqués-Díaz, Sonia M. López del Valle-Carrera, and\nMcConnell Valdés LLC, on brief for appellee Watson Wyatt Company.\n\n\n\n\n January 25, 2019\n\f BOUDIN, Circuit Judge. Olga Torres and Pedro Bonilla\n\nare former employees of Bella Vista Hospital (\"Bella Vista\"), a\n\nMayaguez, Puerto Rico-based hospital operated by the General\n\nConference of Seventh Day Adventist Church. In 1982, the hospital\n\ncreated a pension program, advising its employees that the plan\n\nwas subject to the Employee Retirement Income Security Act of 1974\n\n(\"ERISA\"), 29 U.S.C. §§ 1001-1461. ERISA is a federal statute\n\nimposing obligations on private employers offering pension plans.\n\nSee Advocate Health Care Network v. Stapleton, 137 S. Ct. 1652,\n\n1656 (2017).\n\n Certain types of plans are exempt from ERISA's\n\nrequirements, including plans which meet the statutory definition\n\nof \"church plan,\" 29 U.S.C. § 1003(b)(2). In 2000, the Internal\n\nRevenue Service, which is empowered to issue rulings to parties as\n\nto the status of their plans, advised Bella Vista that its pension\n\nplan met the definition of \"church plan\" and so was exempt from\n\nERISA. In 2003, Bella Vista terminated the plan. Torres and\n\nBonilla had become disabled some years earlier, and certain\n\nbenefits they were receiving from the hospital ended. In November\n\n2006, Torres and Bonilla sued in federal district court in Puerto\n\nRico to recover lost benefits.1\n\n\n 1 Torres and Bonilla had initially sued in a local Puerto Rico\ncourt in 2004, naming not only the hospital but also others as\ndefendants. The local case was suspended to await the outcome of\nthe federal case. Defendants in addition to the hospital were\n\n\n - 3 -\n\f Although the plaintiffs claimed federal subject matter\n\njurisdiction under ERISA, the district court found that the church\n\nplan exception applied so ERISA did not govern the hospital's\n\npension regime. The court granted summary judgment in favor of\n\nthe defendants, dismissing the case on May 21, 2009, for lack of\n\nsubject matter jurisdiction--there being no federal claim in the\n\ncase outside of the purported ERISA count. Torres and Bonilla did\n\nnot appeal that decision and took no further action in court for\n\nfive years.\n\n On November 24, 2014, Torres and Bonilla filed a motion\n\nin the district court to set aside the 2009 judgment, invoking the\n\ncourt's authority to vacate a judgment procured by \"fraud on the\n\ncourt.\" Although such an action is recognized in the rules, Fed.\n\nR. Civ. P. 60(d)(3), the power of federal courts, both trial and\n\nappellate, to set aside or alter prior judgments obtained by fraud\n\nantedates the rules' adoption in 1938 and is a long-settled\n\nequitable power of the federal courts not constrained by any\n\nstatute of limitations, Hazel-Atlas Glass Co. v. Hartford-Empire\n\nCo., 322 U.S. 238, 244-45 (1944).\n\n This drastic remedy is hedged with restrictions. Here,\n\nplaintiffs claimed that in the original federal action they brought\n\n\n\nalso named in the federal case but were dismissed prior to this\nappeal, with two exceptions: Banco Popular de Puerto Rico and\nWatson Wyatt Company. Each has filed its own brief here.\n\n\n - 4 -\n\fin 2006, various defendants made deliberate material misstatements\n\nin their answers and various sworn statements. After referring\n\nthe reopening request to a magistrate judge, the district court in\n\nSeptember 2015, in agreement with the magistrate judge, rejected\n\nthe request as not coming even close to the level of \"fraud on the\n\ncourt.\"\n\n The plaintiffs moved for reconsideration citing evidence\n\nunearthed during the state-court proceeding, which had resumed\n\nfollowing the 2009 dismissal order in the federal case. The\n\ndistrict court denied the motion, and this appeal followed. The\n\nappeal is hopeless on the merits; but the defendants raise\n\nthreshold objections that they argue divest this court of authority\n\nover the appeal, namely (1) that the appeal is untimely, and (2)\n\nthat the notice of appeal is insufficient.\n\n \"'Jurisdiction' is a term used multiple ways,\" McKenna\n\nv. Wells Fargo Bank, N.A., 693 F.3d 207, 213 (1st Cir. 2012); not\n\nevery rule governing the timing of appeals can be said to be\n\n\"jurisdictional,\" only those accorded that status by statute,\n\nHamer v. Neighborhood Housing Services of Chicago, 138 S. Ct. 13,\n\n17 (2017), or where Congress has otherwise made a \"clear\n\nindication\" of its desire to treat a particular rule as having\n\n\"jurisdictional attributes.\" Henderson ex rel. Henderson v.\n\nShinseki, 562 U.S. 428, 439 (2011).\n\n\n\n\n - 5 -\n\f In all events, Supreme Court precedent generally\n\ncontemplates that a federal appeals court consider the timeliness\n\nof the appeal before proceeding to the merits, Bowles v. Russell,\n\n551 U.S. 205, 213-14 (2007), even where the merits issue is\n\nstraightforward and where the same party would lose under either\n\na jurisdictional or a merits ruling. Steel Co. v. Citizens for a\n\nBetter Env't, 523 U.S. 83, 94–95 (1998); see also McKenna, 693\n\nF.3d at 213 (\"[I]t is settled that a civil appeal filed out of\n\ntime is barred, that the error in timing cannot be waived, and\n\nthat circuit courts are expected to notice the error sua sponte\n\n. . .\").\n\n In the nineteenth century and well into the twentieth,\n\nsome courts including this one (1) accepted that even\n\njurisdictional objections could be deemed waived if not raised\n\nearly in a lawsuit, and (2) often reached the merits of certain\n\ndisputes without deciding jurisdiction where the result would have\n\nbeen unchanged. E.g., Carter v. Bennett, 56 U.S. 354, 357 (1853);\n\nUnited States v. Parcel of Land With Bldg., Appurtenances &\n\nImprovements, Known as Woburn City Athletic Club, Inc., 928 F.2d\n\n1, 4 (1st Cir. 1991).\n\n Steel Co. has ended this debate, see Hart & Wechsler,\n\nThe Federal Courts and the Federal System 1412 (6th ed. 2009), at\n\nleast with respect to Article III jurisdiction. But the timeliness\n\nof an appeal or its scope do not turn on the \"arising under\"\n\n\n - 6 -\n\flanguage of Article III or the scope of diversity jurisdiction.\n\nIt depends on whether the appeal was filed within the proper time\n\nor encompasses the issue sought to be raised.\n\n In our case the district judge dismissed the plaintiffs'\n\nreopening motion on the merits on September 30, 2015, holding that\n\nthe allegations by plaintiffs even if factually supported did not\n\nconstitute fraud on the court. Plaintiffs then moved for\n\nreconsideration on October 8, 2015, within the required time period\n\nof twenty-eight days, see Fed. R. Civ. P. 59(e). The district\n\ncourt denied the motion for reconsideration on September 19, 2016;\n\na notice of appeal from that order was then filed within the\n\nrequired thirty-day period. Fed. R. App. P. 4(a)(1)(A).\n\n Although a timely motion for reconsideration normally\n\ntolls the running of the time to appeal, Fed. R. App. P.\n\n4(a)(4)(A)(iv), various defendants argue here that this is not\n\ntrue of where, without bringing anything new to the table, the\n\nmotion repeats claims already disposed of by the dismissal order,\n\nJohnson v. Teamsters Local 559, 102 F.3d 21, 29–30 (1st Cir. 1996),\n\nor is merely an eleventh-hour effort to undo the party's procedural\n\nfailures, Marks 3 Zet-Ernst Marks GmBh & Co. KG v. Presstek, Inc.,\n\n455 F.3d 7, 15-16 (1st Cir. 2006). But here plaintiffs did offer\n\nsomething not previously advanced, namely, evidence unearthed\n\nduring the state proceeding, so the present appeal is thus timely.\n\n\n\n\n - 7 -\n\f Alternatively, defendants argue that the notice of\n\nappeal identifies only the September 19, 2016, denial of the motion\n\nfor reconsideration and that this court therefore lacks authority\n\nto consider the original September 30, 2015, dismissal of their\n\nfraud claim. See Fed. R. App. P. 3(c)(1)(B) (requiring that the\n\nnotice of appeal \"designate the judgment, order, or part thereof\n\nbeing appealed\"). But, as this court said in McKenna,\n\n Technically, an appeal that attacks only an order\n denying reconsideration can fairly be limited by\n the court solely to issues raised in the\n reconsideration motion; but so long as that order\n is timely appealed, courts have some latitude to\n consider other grounds originally urged against the\n underlying dismissal, especially where the issues\n on original dismissal and the reconsideration order\n overlap or are intertwined.\n\n693 F.3d at 213.\n\n In this case the only substantive issue on which Torres\n\nand Bonilla seek review is the district court's denial of their\n\neffort to set aside the 2009 judgment based on alleged fraud on\n\nthe court; so we exercise our discretion to review that ruling\n\nnotwithstanding the lack of clarity in the notice of appeal,\n\nChamorro v. Puerto Rican Cars, Inc., 304 F.3d 1, 3 (1st Cir. 2002)\n\n(explaining that notices of appeal should be \"construe[d] . . .\n\nliberally\" and \"examine[d] . . . in the context of the record as\n\na whole\").\n\n Turning to the merits, claims of false statements by\n\nlawyers or parties are a serious matter and might meet some\n\n\n - 8 -\n\fdefinitions of \"fraud,\" but the phrase \"fraud on the court\" has a\n\nspecial, well-understood and limited office. Inaccurate\n\nassertions in lawsuits are commonplace and to allow all such claims\n\nto be presented as \"fraud on the court,\" with no time limit, would\n\nundermine the finality of judgments and the need for all litigation\n\nto come to an end, cf. Klimowicz v. Deutsche Bank Nat'l Trust Co.,\n\n907 F.3d 61, 67 (1st Cir. 2018).\n\n Thus \"fraud on the court\" is limited to fraud that\n\n\"'seriously' affects the integrity of the normal process of\n\nadjudication,\" \"defile[s] the court itself,\" and prevents \"the\n\njudicial machinery\" from performing its usual function--for\n\nexample, bribery of a judge or jury tampering. 12 Moore's Federal\n\nPractice § 60.21[4][a] (2018); see also George P. Reintjes Co. v.\n\nRiley Stoker Corp., 71 F.3d 44, 48 n.5 (1st Cir. 1995). Nothing\n\nof this severity is present in the plaintiffs' allegations.\n\n Plaintiffs' mainly contend that Banco Popular de Puerto\n\nRico and Bella Vista and their agents committed perjury by denying\n\nthe existence of an ERISA-covered 401(k) plan and covered up the\n\ntransfer of funds between the liquidated employee benefits plan\n\nand the 401(k) plan. Even assuming the truth of these allegations,\n\n\"perjury alone . . . has never been sufficient\" to constitute\n\n\"fraud upon the court.\" George P. Reintjes Co., 71 F.3d at 49.\n\n\n\n\n - 9 -\n\f Sorry though one may be about the plight of the\n\nplaintiffs, the fraud on the court claim is hopeless. The 2006\n\nlitigation is at an end.\n\n Affirmed.\n\n\n\n\n - 10 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362197/", "author_raw": "BOUDIN, Circuit Judge"}]}
HOWARD
BOUDIN
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584944/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Olga TORRES; Pedro Bonilla, Plaintiffs, Appellants, v. BELLA VISTA HOSPITAL, INC. ; Banco Popular De Puerto Rico; The Watson Wyatt Company; Rubén Peréz; Johana Doe 1; Conjugal Partnership Peréz-Doe 1, Defendants, Appellees, the Antillian Union Conference of the Seven Day Adventist; The Retirement Committee of the General Conference of the Seventh Day Adventists Interamerican Division; The General Conference of the Seventh Day Adventist; Bella Vista Pension Plan and Trust; The Adventist of the Seventh Day Interamerican Division Retirement Plan; Bella Vista Hospital, Inc. 401k Plan and Trust; Pannell Kerr & Foster, L.L.P.; Miguel Ramos; Johana Doe; Conjugal Partnership Ramos-Doe, Defendants.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 16-2316\n\n OLGA TORRES; PEDRO BONILLA,\n\n Plaintiffs, Appellants,\n\n v.\n\n BELLA VISTA HOSPITAL, INC.; BANCO POPULAR DE PUERTO RICO;\n THE WATSON WYATT COMPANY; RUBÉN PERÉZ; JOHANA DOE 1;\n CONJUGAL PARTNERSHIP PERÉZ-DOE 1,\n\n Defendants, Appellees,\n\n THE ANTILLIAN UNION CONFERENCE OF THE SEVEN DAY ADVENTIST; THE\n RETIREMENT COMMITTEE OF THE GENERAL CONFERENCE OF THE SEVENTH\nDAY ADVENTISTS INTERAMERICAN DIVISION; THE GENERAL CONFERENCE OF\n THE SEVENTH DAY ADVENTIST; BELLA VISTA PENSION PLAN AND TRUST;\n THE ADVENTIST OF THE SEVENTH DAY INTERAMERICAN DIVISION\nRETIREMENT PLAN; BELLA VISTA HOSPITAL, INC. 401K PLAN AND TRUST;\n PANNELL KERR & FOSTER, L.L.P.; MIGUEL RAMOS; JOHANA DOE;\n CONJUGAL PARTNERSHIP RAMOS-DOE,\n\n Defendants.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Jay A. García-Gregory, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Boudin and Barron, Circuit Judges.\n\n\n Luis A. Vivaldi Oliver on brief for appellants.\n Carlos G. Martínez-Vivas on brief for appellees Bella Vista\n\fHospital, Inc.; Ruben Perez; Johana Doe 1; and Conjugal Partnership\nPerez-Doe 1.\n Cristina S. Belaval-Burger on brief for appellee Banco\nPopular de Puerto Rico.\n Juan A. Marqués-Díaz, Sonia M. López del Valle-Carrera, and\nMcConnell Valdés LLC, on brief for appellee Watson Wyatt Company.\n\n\n\n\n January 25, 2019\n\f BOUDIN, Circuit Judge. Olga Torres and Pedro Bonilla\n\nare former employees of Bella Vista Hospital (\"Bella Vista\"), a\n\nMayaguez, Puerto Rico-based hospital operated by the General\n\nConference of Seventh Day Adventist Church. In 1982, the hospital\n\ncreated a pension program, advising its employees that the plan\n\nwas subject to the Employee Retirement Income Security Act of 1974\n\n(\"ERISA\"), 29 U.S.C. §§ 1001-1461. ERISA is a federal statute\n\nimposing obligations on private employers offering pension plans.\n\nSee Advocate Health Care Network v. Stapleton, 137 S. Ct. 1652,\n\n1656 (2017).\n\n Certain types of plans are exempt from ERISA's\n\nrequirements, including plans which meet the statutory definition\n\nof \"church plan,\" 29 U.S.C. § 1003(b)(2). In 2000, the Internal\n\nRevenue Service, which is empowered to issue rulings to parties as\n\nto the status of their plans, advised Bella Vista that its pension\n\nplan met the definition of \"church plan\" and so was exempt from\n\nERISA. In 2003, Bella Vista terminated the plan. Torres and\n\nBonilla had become disabled some years earlier, and certain\n\nbenefits they were receiving from the hospital ended. In November\n\n2006, Torres and Bonilla sued in federal district court in Puerto\n\nRico to recover lost benefits.1\n\n\n 1 Torres and Bonilla had initially sued in a local Puerto Rico\ncourt in 2004, naming not only the hospital but also others as\ndefendants. The local case was suspended to await the outcome of\nthe federal case. Defendants in addition to the hospital were\n\n\n - 3 -\n\f Although the plaintiffs claimed federal subject matter\n\njurisdiction under ERISA, the district court found that the church\n\nplan exception applied so ERISA did not govern the hospital's\n\npension regime. The court granted summary judgment in favor of\n\nthe defendants, dismissing the case on May 21, 2009, for lack of\n\nsubject matter jurisdiction--there being no federal claim in the\n\ncase outside of the purported ERISA count. Torres and Bonilla did\n\nnot appeal that decision and took no further action in court for\n\nfive years.\n\n On November 24, 2014, Torres and Bonilla filed a motion\n\nin the district court to set aside the 2009 judgment, invoking the\n\ncourt's authority to vacate a judgment procured by \"fraud on the\n\ncourt.\" Although such an action is recognized in the rules, Fed.\n\nR. Civ. P. 60(d)(3), the power of federal courts, both trial and\n\nappellate, to set aside or alter prior judgments obtained by fraud\n\nantedates the rules' adoption in 1938 and is a long-settled\n\nequitable power of the federal courts not constrained by any\n\nstatute of limitations, Hazel-Atlas Glass Co. v. Hartford-Empire\n\nCo., 322 U.S. 238, 244-45 (1944).\n\n This drastic remedy is hedged with restrictions. Here,\n\nplaintiffs claimed that in the original federal action they brought\n\n\n\nalso named in the federal case but were dismissed prior to this\nappeal, with two exceptions: Banco Popular de Puerto Rico and\nWatson Wyatt Company. Each has filed its own brief here.\n\n\n - 4 -\n\fin 2006, various defendants made deliberate material misstatements\n\nin their answers and various sworn statements. After referring\n\nthe reopening request to a magistrate judge, the district court in\n\nSeptember 2015, in agreement with the magistrate judge, rejected\n\nthe request as not coming even close to the level of \"fraud on the\n\ncourt.\"\n\n The plaintiffs moved for reconsideration citing evidence\n\nunearthed during the state-court proceeding, which had resumed\n\nfollowing the 2009 dismissal order in the federal case. The\n\ndistrict court denied the motion, and this appeal followed. The\n\nappeal is hopeless on the merits; but the defendants raise\n\nthreshold objections that they argue divest this court of authority\n\nover the appeal, namely (1) that the appeal is untimely, and (2)\n\nthat the notice of appeal is insufficient.\n\n \"'Jurisdiction' is a term used multiple ways,\" McKenna\n\nv. Wells Fargo Bank, N.A., 693 F.3d 207, 213 (1st Cir. 2012); not\n\nevery rule governing the timing of appeals can be said to be\n\n\"jurisdictional,\" only those accorded that status by statute,\n\nHamer v. Neighborhood Housing Services of Chicago, 138 S. Ct. 13,\n\n17 (2017), or where Congress has otherwise made a \"clear\n\nindication\" of its desire to treat a particular rule as having\n\n\"jurisdictional attributes.\" Henderson ex rel. Henderson v.\n\nShinseki, 562 U.S. 428, 439 (2011).\n\n\n\n\n - 5 -\n\f In all events, Supreme Court precedent generally\n\ncontemplates that a federal appeals court consider the timeliness\n\nof the appeal before proceeding to the merits, Bowles v. Russell,\n\n551 U.S. 205, 213-14 (2007), even where the merits issue is\n\nstraightforward and where the same party would lose under either\n\na jurisdictional or a merits ruling. Steel Co. v. Citizens for a\n\nBetter Env't, 523 U.S. 83, 94–95 (1998); see also McKenna, 693\n\nF.3d at 213 (\"[I]t is settled that a civil appeal filed out of\n\ntime is barred, that the error in timing cannot be waived, and\n\nthat circuit courts are expected to notice the error sua sponte\n\n. . .\").\n\n In the nineteenth century and well into the twentieth,\n\nsome courts including this one (1) accepted that even\n\njurisdictional objections could be deemed waived if not raised\n\nearly in a lawsuit, and (2) often reached the merits of certain\n\ndisputes without deciding jurisdiction where the result would have\n\nbeen unchanged. E.g., Carter v. Bennett, 56 U.S. 354, 357 (1853);\n\nUnited States v. Parcel of Land With Bldg., Appurtenances &\n\nImprovements, Known as Woburn City Athletic Club, Inc., 928 F.2d\n\n1, 4 (1st Cir. 1991).\n\n Steel Co. has ended this debate, see Hart & Wechsler,\n\nThe Federal Courts and the Federal System 1412 (6th ed. 2009), at\n\nleast with respect to Article III jurisdiction. But the timeliness\n\nof an appeal or its scope do not turn on the \"arising under\"\n\n\n - 6 -\n\flanguage of Article III or the scope of diversity jurisdiction.\n\nIt depends on whether the appeal was filed within the proper time\n\nor encompasses the issue sought to be raised.\n\n In our case the district judge dismissed the plaintiffs'\n\nreopening motion on the merits on September 30, 2015, holding that\n\nthe allegations by plaintiffs even if factually supported did not\n\nconstitute fraud on the court. Plaintiffs then moved for\n\nreconsideration on October 8, 2015, within the required time period\n\nof twenty-eight days, see Fed. R. Civ. P. 59(e). The district\n\ncourt denied the motion for reconsideration on September 19, 2016;\n\na notice of appeal from that order was then filed within the\n\nrequired thirty-day period. Fed. R. App. P. 4(a)(1)(A).\n\n Although a timely motion for reconsideration normally\n\ntolls the running of the time to appeal, Fed. R. App. P.\n\n4(a)(4)(A)(iv), various defendants argue here that this is not\n\ntrue of where, without bringing anything new to the table, the\n\nmotion repeats claims already disposed of by the dismissal order,\n\nJohnson v. Teamsters Local 559, 102 F.3d 21, 29–30 (1st Cir. 1996),\n\nor is merely an eleventh-hour effort to undo the party's procedural\n\nfailures, Marks 3 Zet-Ernst Marks GmBh & Co. KG v. Presstek, Inc.,\n\n455 F.3d 7, 15-16 (1st Cir. 2006). But here plaintiffs did offer\n\nsomething not previously advanced, namely, evidence unearthed\n\nduring the state proceeding, so the present appeal is thus timely.\n\n\n\n\n - 7 -\n\f Alternatively, defendants argue that the notice of\n\nappeal identifies only the September 19, 2016, denial of the motion\n\nfor reconsideration and that this court therefore lacks authority\n\nto consider the original September 30, 2015, dismissal of their\n\nfraud claim. See Fed. R. App. P. 3(c)(1)(B) (requiring that the\n\nnotice of appeal \"designate the judgment, order, or part thereof\n\nbeing appealed\"). But, as this court said in McKenna,\n\n Technically, an appeal that attacks only an order\n denying reconsideration can fairly be limited by\n the court solely to issues raised in the\n reconsideration motion; but so long as that order\n is timely appealed, courts have some latitude to\n consider other grounds originally urged against the\n underlying dismissal, especially where the issues\n on original dismissal and the reconsideration order\n overlap or are intertwined.\n\n693 F.3d at 213.\n\n In this case the only substantive issue on which Torres\n\nand Bonilla seek review is the district court's denial of their\n\neffort to set aside the 2009 judgment based on alleged fraud on\n\nthe court; so we exercise our discretion to review that ruling\n\nnotwithstanding the lack of clarity in the notice of appeal,\n\nChamorro v. Puerto Rican Cars, Inc., 304 F.3d 1, 3 (1st Cir. 2002)\n\n(explaining that notices of appeal should be \"construe[d] . . .\n\nliberally\" and \"examine[d] . . . in the context of the record as\n\na whole\").\n\n Turning to the merits, claims of false statements by\n\nlawyers or parties are a serious matter and might meet some\n\n\n - 8 -\n\fdefinitions of \"fraud,\" but the phrase \"fraud on the court\" has a\n\nspecial, well-understood and limited office. Inaccurate\n\nassertions in lawsuits are commonplace and to allow all such claims\n\nto be presented as \"fraud on the court,\" with no time limit, would\n\nundermine the finality of judgments and the need for all litigation\n\nto come to an end, cf. Klimowicz v. Deutsche Bank Nat'l Trust Co.,\n\n907 F.3d 61, 67 (1st Cir. 2018).\n\n Thus \"fraud on the court\" is limited to fraud that\n\n\"'seriously' affects the integrity of the normal process of\n\nadjudication,\" \"defile[s] the court itself,\" and prevents \"the\n\njudicial machinery\" from performing its usual function--for\n\nexample, bribery of a judge or jury tampering. 12 Moore's Federal\n\nPractice § 60.21[4][a] (2018); see also George P. Reintjes Co. v.\n\nRiley Stoker Corp., 71 F.3d 44, 48 n.5 (1st Cir. 1995). Nothing\n\nof this severity is present in the plaintiffs' allegations.\n\n Plaintiffs' mainly contend that Banco Popular de Puerto\n\nRico and Bella Vista and their agents committed perjury by denying\n\nthe existence of an ERISA-covered 401(k) plan and covered up the\n\ntransfer of funds between the liquidated employee benefits plan\n\nand the 401(k) plan. Even assuming the truth of these allegations,\n\n\"perjury alone . . . has never been sufficient\" to constitute\n\n\"fraud upon the court.\" George P. Reintjes Co., 71 F.3d at 49.\n\n\n\n\n - 9 -\n\f Sorry though one may be about the plight of the\n\nplaintiffs, the fraud on the court claim is hopeless. The 2006\n\nlitigation is at an end.\n\n Affirmed.\n\n\n\n\n - 10 -\n[END_CASE]", "role": "user" } ]
4,584,945
Paradise HOGAN, on Behalf of Himself and All Others Similarly Situated, Plaintiff, Appellee, v. SPAR GROUP, INC., Defendant, Appellant, SPAR Business Services, Inc., Defendant.
Hogan v. SPAR Group, Inc.
2019-01-25
18-1286P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Kayatta, Barron", "parties": "", "opinions": [{"author": "TORRUELLA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\nNo. 18-1286\n\n PARADISE HOGAN,\n on behalf of himself and all others similarly situated,\n\n Plaintiff, Appellee,\n\n v.\n\n SPAR GROUP, INC.,\n\n Defendant, Appellant,\n\n SPAR BUSINESS SERVICES, INC.,\n\n Defendant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Leo T. Sorokin, U.S. District Judge]\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n James M. Nicholas, with whom Jillian M. Collins and Foley &\nLardner LLP were on brief, for appellant.\n Brook S. Lane, with whom Hillary Schwab and Fair Work, P.C.\nwere on brief, for appellee.\n\n\n January 25, 2019\n\f TORRUELLA, Circuit Judge. SPAR Group, Inc. (\"SPAR\")\n\nappeals from the district court's denial of its motion to compel\n\narbitration. SPAR, a retail services provider, obtains most of\n\nits personnel from a staffing company named SPAR Business Services,\n\nInc. (\"SBS\"). SBS engaged plaintiff-appellee Paradise Hogan\n\n(\"Hogan\") as an independent contractor and assigned him to perform\n\nservices for SPAR. Hogan and SBS entered into an \"Independent\n\nContractor Master Agreement\" to which SPAR was not a party.\n\nSubsequently, Hogan sued SBS and SPAR, and both sought to compel\n\narbitration invoking an arbitration clause in the Independent\n\nContractor Master Agreement. The district court compelled\n\narbitration as to Hogan's claims against SBS, but found that SPAR\n\nhad no legal basis to compel Hogan to arbitration.\n\n SPAR appealed, pressing two alternate theories for why\n\nit can compel Hogan to arbitrate despite not being a party to the\n\nagreement containing the arbitration clause. A review of the\n\nfacts here mandates the conclusion that \"the obvious bar to\n\narbitrability is the abecedarian tenet that a party cannot be\n\nforced to arbitrate if it has not agreed to do so.\" InterGen N.V.\n\nv. Grina, 344 F.3d 134, 137 (1st Cir. 2003). We affirm.\n\n I. Background\n\n Because SPAR's request \"to compel arbitration was made\n\nin connection with a motion to dismiss or stay, we draw the\n\n\n -2-\n\frelevant facts from the operative complaint and the documents\n\nsubmitted to the district court in support of the motion to compel\n\narbitration.\" Cullinane v. Uber Techs., Inc., 893 F.3d 53, 55\n\n(1st Cir. 2018).\n\nA. Factual Background\n\n SBS is a staffing company that provides personnel to\n\nvarious retail services providers, including SPAR. SPAR executes\n\nfield merchandising, auditing, and assembly services for retailers\n\nthrough personnel referred to as \"Field Specialists,\"\n\nsubstantially all of whom are supplied by SBS. SBS is\n\n\"affiliate[d]\" to SPAR \"but is not a subsidiary of or controlled\n\nby SPAR.\"1 SBS classifies the Field Specialists it provides to\n\nSPAR as independent contractors.\n\n Paradise Hogan entered into an \"Independent Contractor\n\nMaster Agreement\" (the \"Master Agreement\") with SBS, which SBS\n\nrequires all Field Specialists to sign.2 Paragraph twenty of the\n\n\n\n\n1 The Amended Complaint does not specify the exact relationship\nbetween SBS and Spar.\n2 The Agreement reflects an \"[e]lectronic [a]cceptance by\nIndependent Contractor\" on April 19, 2016. Yet, the Amended\nComplaint states that SBS assigned Hogan to work for Spar \"in or\nabout May 2015\" and that the Agreement was signed \"[p]rior to\ncommencing his employment with SBS and SPAR.\" In any case, the\ninconsistency is not material to the controversies at issue here.\n\n\n -3-\n\fMaster Agreement requires its parties to resolve disputes through\n\narbitration:\n\n Any dispute between the Parties relating to this\n Master Agreement or otherwise arising out of their\n relationship under its terms, including but not\n limited to any disputes over rights provided by\n federal, state, or local statutes, regulations,\n ordinances, and/or common law, shall be determined by\n arbitration. . . . The Parties acknowledge the Master\n Agreement evidences a transaction involving\n interstate commerce, and the arbitration shall be\n governed by the United States Federal Arbitration Act\n (9 U.S.C., Sections 1-16) (\"FAA\").\n\nParagraph twenty of the Master Agreement also states that \"[t]he\n\nParties agree that any claim shall be brought solely in the\n\nindividual capacity of SBS or the Independent Contractor, and not\n\nas a representative of any other persons or any class.\" SPAR is\n\nnot a party to the Master Agreement.\n\n In or about May 2015, SBS assigned Hogan to perform Field\n\nSpecialist duties for SPAR. Neither SBS nor SPAR reimbursed Hogan\n\nor other Field Specialists for costs or expenses incurred in the\n\nperformance of their assignments. While SBS required Hogan and\n\nother Field Specialists to acquire general liability and workers'\n\ncompensation insurance, neither SBS nor SPAR paid for or\n\ncontributed to these expenses. Hogan's regular hourly rate for\n\nperforming services as a Field Specialist was minimum wage.\n\n\t\n\n\n\n\n -4-\n\fB. Procedural Background\n\n On January 6, 2017, Hogan filed a putative class action\n\ncomplaint against both SBS and SPAR essentially alleging that they\n\nmisclassified him and other Field Specialists as independent\n\ncontractors rather than employees, such that they avoid paying\n\nmandated expenses and cause them to earn less than minimum wage.\n\nHogan asserted various causes of action, including breach of\n\ncontract, unjust enrichment, and violations to the Fair Labor\n\nStandards Act and Massachusetts wage and hour statutes.\n\n On May 2, 2017, after SBS and SPAR moved to compel\n\narbitration or dismiss for failure to state a claim, Hogan\n\nrequested to amend the complaint to \"narrow the scope of his\n\nclaims.\" The district court allowed Hogan's request and denied\n\nas moot defendants' motion to compel arbitration. On May 17,\n\n2017, Hogan filed \"Plaintiff's First Amended Class Action\n\nComplaint and Demand for Jury Trial\" (the \"Amended Complaint\"),\n\nabandoning all but his claims pursuant to the Massachusetts Wage\n\nAct, Mass. Gen. Laws ch. 149, §§ 148, 150, and the Massachusetts\n\nIndependent Contractor Statute, Mass. Gen. Laws ch. 149, § 148B.\n\n In response, SBS and SPAR renewed their request to compel\n\narbitration. In essence, they argued that both were shielded by\n\nthe Master Agreement's arbitration provision (although SPAR was\n\nnot a signatory) and that Hogan's consent to waive class and\n\n\n -5-\n\frepresentative actions was valid and enforceable. In the\n\nalternative, they moved to dismiss the Amended Complaint under\n\nFed. R. Civ. P. 12(b)(6).\n\n On March 12, 2018, the district court denied the motion\n\nto compel arbitration as to SPAR, finding that it had no legal\n\nbasis to compel Hogan to arbitration. As to SBS, the district\n\ncourt noted that Hogan was not contesting that his claims were\n\nsubject to arbitration, but rather that the court was barred from\n\nenforcing the arbitration agreement pursuant to the National Labor\n\nRelations Act because it precluded him from pursuing class remedies\n\nin legal proceedings. Because a similar issue was before the U.S.\n\nSupreme Court at the time, the district court stayed Hogan's case\n\nas to SBS to await the ruling in Lewis v. Epic Sys. Corp., 823\n\nF.3d 1147 (7th Cir. 2016), cert. granted, 137 S. Ct. 809 (2017).\n\nFinally, the district court denied the Fed. R. Civ. P. 12(b)(6)\n\ndismissal request. On April 4, 2018, SPAR filed a notice of appeal.3\n\n After SPAR filed its notice of appeal, the Supreme Court\n\ndecided in Epic Sys. Corp. v. Lewis, 138 S. Ct. 1612, 1632 (2018),\n\nthat employees' arbitration agreements waiving class and\n\n\n3 Although generally, interlocutory orders are not immediately\nappealable, see 28 U.S.C. § 1291, the Federal Arbitration Act\ncreates an exception for orders denying petitions to compel\narbitration, see 9 U.S.C. § 16(a)(1)(B). Campbell v. Gen.\nDynamics Gov't Sys. Corp., 407 F.3d 546, 550 (1st Cir. 2005) (so\nnoting).\n\n\n -6-\n\fcollective action procedures are enforceable, as pertinent here.\n\nIn response, the district court dismissed Hogan's claims against\n\nSBS, compelling arbitration of those claims.\n\n II. Analysis\n\n \"We review de novo a district court's interpretation of\n\nan arbitration agreement and its decision regarding whether or not\n\nto compel arbitration.\" Ouadani v. TF Final Mile LLC, 876 F.3d\n\n31, 36 (1st Cir. 2017) (citing S. Bay Bos. Mgmt. v. Unite Here,\n\nLocal 26, 587 F.3d 35, 42 (1st Cir. 2009)).\n\n \"[A]rbitration is a matter of contract and a party cannot\n\nbe required to submit to arbitration any dispute which [it] has\n\nnot agreed so to submit.\" McCarthy v. Azure, 22 F.3d 351, 354\n\n(1st Cir. 1994) (quoting AT&T Techs., Inc. v. Commc'ns Workers,\n\n475 U.S. 643, 648 (1986)). Thus, a party that attempts to compel\n\narbitration \"must show [1] that a valid agreement to arbitrate\n\nexists, [2] that the movant is entitled to invoke the arbitration\n\nclause, [3] that the other party is bound by that clause, and [4]\n\nthat the claim asserted comes within the clause's scope.\"\n\nOuadani, 876 F.3d at 36 (quoting InterGen, 344 F.3d at 142).\n\n While SPAR invokes the \"federal policy favoring\n\narbitration,\" such policy \"presumes proof of a preexisting\n\nagreement to arbitrate disputes arising between the protagonists.\"\n\nMcCarthy, 22 F.3d at 355. As this court has highlighted,\n\n\n -7-\n\f\"arbitration is a matter of consent, not coercion.\" Ouadani, 876\n\nF.3d at 36 (quoting Stolt-Nielsen S.A. v. AnimalFeeds Int'l Corp.,\n\n559 U.S. 662, 681 (2010)).\n\n Here, SPAR faces a steep climb, as it concedes that it\n\nis not a party to the Master Agreement it invokes. Indeed, the\n\nMaster Agreement's first sentence clearly establishes Hogan and\n\nSBS (not SPAR) as the only parties: \"[t]his Independent Contractor\n\nMaster Agreement ('Master Agreement') is entered into between\n\nHogan Paradise ('Independent Contractor') and SPAR Business\n\nServices, Inc. ('SBS').\" Most crucially, the Master Agreement's\n\narbitration clause specifically limits its applicability to \"the\n\nParties.\" It states that: \"[a]ny dispute between the Parties\n\nrelating to this Master Agreement or otherwise arising out of their\n\nrelationship under its terms . . . shall be determined by\n\narbitration.\" (Emphasis added).\n\n Nonetheless, SPAR claims that despite not being a party\n\nto the Master Agreement, it is \"entitled to invoke the arbitration\n\nclause.\" It posits that: (1) it is a third-party beneficiary of\n\nthe agreement between Hogan and SBS; and (2) Hogan is equitably\n\nestopped from avoiding arbitration of his claims against SPAR.4\n\n\n4 Hogan argues that Spar waived its equitable estoppel and third-\nparty beneficiary arguments because they were insufficiently\nraised at the district court level. Because the district court\nunderstood it had enough material to rule on those issues, we will\nnot deem them waived. See Rodríguez-López v. Triple-S Vida, Inc.,\n\n -8-\n\fThis Circuit has recognized that in certain exceptional\n\nsituations, a nonsignatory to an agreement may invoke an\n\narbitration clause. See Grand Wireless, Inc. v. Verizon Wireless,\n\nInc., 748 F.3d 1, 9-10 (1st Cir. 2014) (applying principles of\n\nagency to find that employees, acting within the scope of their\n\nemployment, can invoke an arbitration provision adopted by their\n\nemployer). This is not such a case.5\n\nA. SPAR is not a third-party beneficiary of the Independent\n Contractor Master Agreement\n\n \"As is generally the case in matters of contract\n\ninterpretation, '[t]he crux in third-party beneficiary analysis\n\n. . . is the intent of the parties.'\" McCarthy, 22 F.3d at 362\n\n(alterations in original) (quoting Mowbray v. Moseley, Hallgarten,\n\n\n\n\n850 F.3d 14, 21 n.3 (1st Cir. 2017) (\"We note that the district\ncourt found Rodríguez had sufficiently preserved her . . .\nargument, and we find so as well.\").\n5 The district court applied federal common law to evaluate\nwhether a non-signatory can invoke an arbitration provision,\n\"absent any contention from Hogan.\" On appeal, the parties do not\ncontest this. See Sourcing Unlimited, Inc. v. Asimco Int'l, Inc.,\n526 F.3d 38, 46 (1st Cir. 2008) (\"In the absence of any contention\nfrom the parties to the contrary, we apply federal common law to\nresolve the issues.\" (citing InterGen, 344 F.3d at 143)); see also\nOuadani, 876 F.3d at 37 (looking to \"federal common law, which\nincorporates 'general principles of contract and agency law,'\" to\ndetermine whether a nonsignatory to an arbitration agreement was\nbound to arbitrate his claim (citing InterGen, 344 F.3d at 144)).\nBut see Grand Wireless, 748 F.3d at 11-12 (calling into question\nthe propriety of using federal law to determine whether a non-\nparty to an arbitration agreement can assert its protection).\n\n\n -9-\n\fEstabrook & Weeden, 795 F.2d 1111, 1117 (1st Cir. 1986)). A third-\n\nparty beneficiary must demonstrate with \"special clarity that the\n\ncontracting parties intended to confer a benefit on him,\"\n\nconsidering that such status is \"an exception to the general rule\n\nthat a contract does not grant enforceable rights to\n\nnonsignatories.\" Id. In evaluating whether such \"special clarity\"\n\nexists, a court should focus on the \"specific terms\" of the\n\nagreement at issue, being mindful that it \"ought not to distort\n\nthe clear intention of contracting parties or reach conclusions at\n\nodds with the unambiguous language of a contract.\" InterGen, 344\n\nF.3d at 146 (citing EEOC v. Waffle House, Inc., 534 U.S. 279, 294\n\n(2002)).\n\n SPAR concedes that it is not named in the Master\n\nAgreement, but essentially argues that it is a third-party\n\nbeneficiary because the Master Agreement confers upon it, \"as a\n\ncustomer of SBS,\" the right to dictate certain work requirements\n\nto the independent contractor. We gather that SPAR refers to\n\nparagraph nine of the Master Agreement, yet that clause merely\n\nstates that SBS would convey to Hogan scheduling and assignment\n\nrequirements, if any, that it received from its customers, which\n\ninclude SPAR. At best, this is a tenuous grant of a vague benefit.\n\nIt does not come close to showing the requisite \"special clarity.\"\n\nMoreover, even if SPAR could be said to benefit from the clause,\n\n\n -10-\n\f\"a mere benefit to the nonsignatory resulting from a signatory's\n\nexercise of its contractual rights is not enough.\" Ouadani, 876\n\nF.3d at 39 (1st Cir. 2017) (citing InterGen, 344 F.3d at 146-47).\n\nRather, the contract must \"mention [or] manifest an intent to\n\nconfer specific legal rights upon [SPAR],\" and the contract\n\nlanguage that SPAR points us to does not make the cut. InterGen,\n\n344 F.3d at 147.\n\n Finally, even if SPAR could show an intent of the parties\n\nto confer upon it some benefit unrelated to arbitration, the\n\nlanguage of the arbitration clause would still be dispositive. As\n\nmentioned earlier, the arbitration clause limits its applicability\n\nto the signatories by only covering disputes \"between the Parties,\"\n\nso it is clear that it does not confer arbitration rights to SPAR\n\nor any third party.\n\n Our conclusion is reinforced by the fact that the Master\n\nAgreement references SBS's \"customers\" in other sections, yet\n\nomits that reference in the arbitration clause. SBS could have\n\neasily modified the arbitration clause to make it applicable to\n\n\"[a]ny dispute between the Parties [and/or any SBS customer]\n\nrelating to this Master Agreement,\" but it did not. See Mowbray,\n\n795 F.2d at 1118 (finding persuasive the appellants' argument that\n\ngiven \"the probable sophistication of the drafters of the\n\nagreement, . . . the omission of defendants from the arbitration\n\n\n -11-\n\fclause must be regarded as purposeful\"); see also Cortés-Ramos v.\n\nMartin-Morales, 894 F.3d 55, 59-60 (1st Cir. 2018) (holding that\n\nnonsignatory singer, Ricky Martin, could not compel arbitration\n\nbased on an agreement that referenced him in certain provisions\n\nbut did not in its arbitration clause).\n\n Finally, the Agreement has an integration clause that\n\nreads:\n\n This Master Agreement constitutes the complete,\n integrated agreement of Independent Contractor and\n SBS and supersedes all prior written and oral\n agreements, negotiations, promises, and\n representations, if any. Nothing contained in this\n Master Agreement may be modified in any way except\n through a written agreement signed by Independent\n Contractor and Mr. Robert Brown of SBS.\n\nThis language accentuates the parties' intent to confine to its\n\nsignatories the right to invoke the Master Agreement's arbitration\n\nclause. See McCarthy v. Azure, 22 F.3d 351, 358 (1st Cir. 1994)\n\n(stating that \"[t]he intent to limit arbitral rights to signatories\n\nis also made manifest by the inclusion of an integration clause\").\n\n Thus, a review of the language of the Master Agreement,\n\nand more particularly its arbitration clause, shows that SPAR was\n\nnot an intended third-party beneficiary of the signatories'\n\nagreement to arbitrate. See InterGen, 344 F.3d at 146 (declining\n\nto read into agreement \"rights and obligations that the contracting\n\nparties did not see fit to include\").\n\n\n\n -12-\n\fB. Hogan is not equitably estopped from avoiding arbitration of\n his claims against SPAR\n\n SPAR propounds that, even if it is not a signatory to\n\nthe Agreement, Hogan is nevertheless equitably estopped from\n\navoiding arbitration because his claims against SPAR are\n\n\"intertwined\" with the Master Agreement and because SPAR and SBS,\n\nwhich is a signatory to the Agreement, are \"closely related.\"\n\nSPAR primarily relies on Sourcing Unlimited, Inc. v. Asimco Int'l,\n\nInc., 526 F.3d 38 (1st Cir. 2008).\n\n \"[E]quitable estoppel precludes a party from enjoying\n\nrights and benefits under a contract while at the same time\n\navoiding its burdens and obligations.\" InterGen, 344 F.3d at 145.\n\nGenerally, federal courts \"have been willing to estop a signatory\n\nfrom avoiding arbitration with a nonsignatory when the issues . . .\n\nto resolve in arbitration are intertwined with the agreement that\n\nthe estopped party has signed.\" Ouadani, 876 F.3d at 38 (second\n\nemphasis added) (quoting InterGen, 344 F.3d at 145).\n\n In Sourcing Unlimited, 526 F.3d at 46-48, this court\n\napplied equitable estoppel to hold that the plaintiff, a corporate\n\nsignatory to a partnership agreement, was compelled to arbitrate\n\nits claims against a non-signatory defendant. The court found\n\nthat the plaintiff's claims were \"sufficiently intertwined\" with\n\nthe agreement that the plaintiff had signed with the defendant's\n\nparent company. Id. at 47. Hence, it reversed and remanded with\n\n -13-\n\finstructions to the district court to compel arbitration. Id. at\n\n48.\n\n We find Sourcing Unlimited distinguishable from the case\n\nat hand. First, prior to considering the \"intertwined\"\n\nrequirement, we must step back and once again recur to the language\n\nof the arbitration clauses. In Sourcing Unlimited, the \"broadly-\n\nworded\" arbitration clause stated: \"[a]ny action to enforce,\n\narising out of, or relating in any way to, any of the provisions\n\nof this agreement shall be brought in front of a P.R. China\n\narbitration body.\" Id. at 41 (emphasis added). Having the\n\nplaintiff consented to arbitrate any action \"arising out of, or\n\nrelating in any way to\" the agreement, the court applied the\n\nequitable estoppel doctrine to enforce arbitration of claims that\n\nfell within the scope of the arbitration clause and were\n\nintertwined with the agreement but were brought against a non-\n\nsignatory subsidiary. Id. at 48.\n\n Unlike Sourcing Unlimited, the arbitration provision\n\nhere cabins its scope to disputes \"between the Parties\" to the\n\nMaster Agreement, with the \"Parties\" unambiguously defined as SBS\n\nand Hogan. While one could say that arbitrating a dispute relating\n\nto the contract against an affiliated third-party was within the\n\nscope of what the plaintiff consented to in Sourcing Unlimited,\n\n\n\n\n -14-\n\fthe same cannot be said here. Hogan clearly and unambiguously\n\nconsented to arbitrate only claims between him and SBS.6\n\n And while SPAR alleges that its \"close relationship\"7\n\nwith SBS should bind Hogan, we need not delve into the nature of\n\n\n\n6 Similarly, Spar cites Herrera-Gollo v. Seaborne Puerto Rico,\nLLC, Civil No. 15-1771(JAG), 2017 WL 657430 (D.P.R. Feb. 17, 2017)\nand Ragone v. Atl. Video at Manhattan Ctr., 595 F.3d 115 (2d Cir.\n2010) as persuasive authority. Irrespective of whether we agree\nwith their outcome and analysis, which we need not discuss now,\nthose cases are distinguishable due to the broad reach of the\narbitration clauses at issue therein.\n\nIn Herrera-Gollo, the plaintiff argued that defendant Seaborne\nPuerto Rico could not invoke the arbitration clause because the\nagreement was signed by Seaborne Virgin Islands, Inc., but the\narbitration provision covered \"all claims, controversies, or\ndisputes . . . against the Company, its shareholders or subsidiary\nor parent or affiliated companies . . . arising out of or in any\nway relating to [plaintiff's] application for employment.\"\nHerrera-Gollo, 2017 WL 657430, at *3 (emphasis added) (emphasis in\noriginal omitted). The court concluded that \"the language evinces\na broad intent that Plaintiff be required to arbitrate claims\nagainst a variety of entities associated with Seaborne Virgin\nIslands, not just that specific entity\" and compelled plaintiff to\narbitrate his claims against Seaborne Puerto Rico even though it\nhad not signed the agreement. Id. at *7. The same intent is not\nevidenced by the language of the Master Agreement.\n\nIn Ragone, the court compelled plaintiff Rita Ragone to arbitrate\nher employment discrimination claims against her direct employer,\nAtlantic Video (\"AVI\"), and ESPN, for whom she provided services\nthrough AVI, finding that she was equitably estopped from avoiding\narbitration as to ESPN. Nevertheless, once again, the pertinent\narbitration clause there was broader, as she had agreed to\narbitrate \"any and all claims or controversies arising out of [her]\nemployment or its termination.\" Ragone, 595 F.3d at 118.\n\nLikewise, the other non-binding cases that Spar cites do not\npersuade us to alter our reasoning here.\n7 According to the Amended Complaint, \"SBS is an affiliate of\n\n -15-\n\ftheir relationship, as irrespective of it, SPAR has not shown any\n\nintent on behalf of Hogan to arbitrate with any entity other than\n\nSBS. See Sokol Holdings, Inc. v. BMB Munai, Inc., 542 F.3d 354,\n\n361–62 (2d Cir. 2008) (noting that any relationship among parties\n\nmust support the conclusion that the signatory \"consented to extend\n\nits agreement to arbitrate\" to the nonsignatory). SBS and SPAR\n\nare sophisticated commercial players that chose to conduct their\n\nbusiness as separate corporate structures, and we see no reason to\n\nignore the legal scheme that they constructed. Hence, SPAR has\n\nnot put forth any convincing argument or authority establishing\n\nthat the equitable estoppel doctrine is applicable when the\n\nlanguage of the contract is so clearly limiting, and we find no\n\nlegal basis for forcing Hogan to arbitrate his claims against SPAR\n\nwhen he demonstrated no intent to do so.\n\n In any case, a review of the facts here shows that SPAR\n\ncould not establish the \"intertwined\" requirement for purposes of\n\napplying equitable estoppel. In Sourcing Unlimited the court\n\nconcluded that the plaintiff's claims were \"sufficiently\n\nintertwined\" with the agreement because they \"either directly or\n\nindirectly invoke[d] the terms of the\" agreement, id. at 47, and\n\nthey \"ultimately derive[d] from benefits\" the plaintiff alleged\n\n\n\n\nSPAR but is not a subsidiary of or controlled by SPAR . . . .\"\n\n\n -16-\n\fwere due under the agreement, id. at 48. Moreover, the court\n\nnoted that if the agreement were to become void, the plaintiff's\n\nobligations under a side-contract with defendant \"would be\n\nmeaningless.\" Id.\n\n Here, Hogan's claims against SPAR are premised upon\n\nMassachusetts wage and hour law, not the Master Agreement between\n\nSBS and Hogan: he seeks a remedy for \"unpaid wages and benefits\"\n\nwhich he alleges he has a right to pursuant to Massachusetts law.\n\nMoreover, Hogan's claims would exist even if the Master Agreement\n\nwere declared void, as they are based on the nature of the services\n\nthat Hogan provided to SPAR. Finally, as the Amended Complaint\n\nshows, Hogan does not claim any benefit or right from SPAR arising\n\nfrom the Master Agreement. See Sourcing Unlimited, 526 F.3d at\n\n47 (\"The [signatory] plaintiff's actual dependence on the\n\nunderlying contract in making out the claim against the\n\nnonsignatory defendant is therefore always the sine qua non of an\n\nappropriate situation for applying equitable estoppel [against the\n\nplaintiff].\" (alteration in original) (quoting In re Humana Inc.\n\nManaged Care Litig., 285 F.3d 971, 976 (11th Cir. 2002), rev'd on\n\nother grounds sub nom. PacifiCare Health Sys., Inc. v. Book, 538\n\nU.S. 401 (2003))). There is therefore no cognizable basis for\n\napplying equitable estoppel here.\n\n\t\n\n\n -17-\n\f III. Conclusion\n\n We find no legal basis to compel Hogan to arbitration,\n\nas the clear terms of the Master Agreement show that he did not\n\nconsent to arbitrate his claims against SPAR. The district\n\ncourt's judgment is therefore affirmed.\n\n Affirmed.\n\n\n\n\n -18-", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362198/", "author_raw": "TORRUELLA, Circuit Judge"}]}
TORRUELLA
KAYATTA
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584945/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Paradise HOGAN, on Behalf of Himself and All Others Similarly Situated, Plaintiff, Appellee, v. SPAR GROUP, INC., Defendant, Appellant, SPAR Business Services, Inc., Defendant.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\nNo. 18-1286\n\n PARADISE HOGAN,\n on behalf of himself and all others similarly situated,\n\n Plaintiff, Appellee,\n\n v.\n\n SPAR GROUP, INC.,\n\n Defendant, Appellant,\n\n SPAR BUSINESS SERVICES, INC.,\n\n Defendant.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Leo T. Sorokin, U.S. District Judge]\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n James M. Nicholas, with whom Jillian M. Collins and Foley &\nLardner LLP were on brief, for appellant.\n Brook S. Lane, with whom Hillary Schwab and Fair Work, P.C.\nwere on brief, for appellee.\n\n\n January 25, 2019\n\f TORRUELLA, Circuit Judge. SPAR Group, Inc. (\"SPAR\")\n\nappeals from the district court's denial of its motion to compel\n\narbitration. SPAR, a retail services provider, obtains most of\n\nits personnel from a staffing company named SPAR Business Services,\n\nInc. (\"SBS\"). SBS engaged plaintiff-appellee Paradise Hogan\n\n(\"Hogan\") as an independent contractor and assigned him to perform\n\nservices for SPAR. Hogan and SBS entered into an \"Independent\n\nContractor Master Agreement\" to which SPAR was not a party.\n\nSubsequently, Hogan sued SBS and SPAR, and both sought to compel\n\narbitration invoking an arbitration clause in the Independent\n\nContractor Master Agreement. The district court compelled\n\narbitration as to Hogan's claims against SBS, but found that SPAR\n\nhad no legal basis to compel Hogan to arbitration.\n\n SPAR appealed, pressing two alternate theories for why\n\nit can compel Hogan to arbitrate despite not being a party to the\n\nagreement containing the arbitration clause. A review of the\n\nfacts here mandates the conclusion that \"the obvious bar to\n\narbitrability is the abecedarian tenet that a party cannot be\n\nforced to arbitrate if it has not agreed to do so.\" InterGen N.V.\n\nv. Grina, 344 F.3d 134, 137 (1st Cir. 2003). We affirm.\n\n I. Background\n\n Because SPAR's request \"to compel arbitration was made\n\nin connection with a motion to dismiss or stay, we draw the\n\n\n -2-\n\frelevant facts from the operative complaint and the documents\n\nsubmitted to the district court in support of the motion to compel\n\narbitration.\" Cullinane v. Uber Techs., Inc., 893 F.3d 53, 55\n\n(1st Cir. 2018).\n\nA. Factual Background\n\n SBS is a staffing company that provides personnel to\n\nvarious retail services providers, including SPAR. SPAR executes\n\nfield merchandising, auditing, and assembly services for retailers\n\nthrough personnel referred to as \"Field Specialists,\"\n\nsubstantially all of whom are supplied by SBS. SBS is\n\n\"affiliate[d]\" to SPAR \"but is not a subsidiary of or controlled\n\nby SPAR.\"1 SBS classifies the Field Specialists it provides to\n\nSPAR as independent contractors.\n\n Paradise Hogan entered into an \"Independent Contractor\n\nMaster Agreement\" (the \"Master Agreement\") with SBS, which SBS\n\nrequires all Field Specialists to sign.2 Paragraph twenty of the\n\n\n\n\n1 The Amended Complaint does not specify the exact relationship\nbetween SBS and Spar.\n2 The Agreement reflects an \"[e]lectronic [a]cceptance by\nIndependent Contractor\" on April 19, 2016. Yet, the Amended\nComplaint states that SBS assigned Hogan to work for Spar \"in or\nabout May 2015\" and that the Agreement was signed \"[p]rior to\ncommencing his employment with SBS and SPAR.\" In any case, the\ninconsistency is not material to the controversies at issue here.\n\n\n -3-\n\fMaster Agreement requires its parties to resolve disputes through\n\narbitration:\n\n Any dispute between the Parties relating to this\n Master Agreement or otherwise arising out of their\n relationship under its terms, including but not\n limited to any disputes over rights provided by\n federal, state, or local statutes, regulations,\n ordinances, and/or common law, shall be determined by\n arbitration. . . . The Parties acknowledge the Master\n Agreement evidences a transaction involving\n interstate commerce, and the arbitration shall be\n governed by the United States Federal Arbitration Act\n (9 U.S.C., Sections 1-16) (\"FAA\").\n\nParagraph twenty of the Master Agreement also states that \"[t]he\n\nParties agree that any claim shall be brought solely in the\n\nindividual capacity of SBS or the Independent Contractor, and not\n\nas a representative of any other persons or any class.\" SPAR is\n\nnot a party to the Master Agreement.\n\n In or about May 2015, SBS assigned Hogan to perform Field\n\nSpecialist duties for SPAR. Neither SBS nor SPAR reimbursed Hogan\n\nor other Field Specialists for costs or expenses incurred in the\n\nperformance of their assignments. While SBS required Hogan and\n\nother Field Specialists to acquire general liability and workers'\n\ncompensation insurance, neither SBS nor SPAR paid for or\n\ncontributed to these expenses. Hogan's regular hourly rate for\n\nperforming services as a Field Specialist was minimum wage.\n\n\t\n\n\n\n\n -4-\n\fB. Procedural Background\n\n On January 6, 2017, Hogan filed a putative class action\n\ncomplaint against both SBS and SPAR essentially alleging that they\n\nmisclassified him and other Field Specialists as independent\n\ncontractors rather than employees, such that they avoid paying\n\nmandated expenses and cause them to earn less than minimum wage.\n\nHogan asserted various causes of action, including breach of\n\ncontract, unjust enrichment, and violations to the Fair Labor\n\nStandards Act and Massachusetts wage and hour statutes.\n\n On May 2, 2017, after SBS and SPAR moved to compel\n\narbitration or dismiss for failure to state a claim, Hogan\n\nrequested to amend the complaint to \"narrow the scope of his\n\nclaims.\" The district court allowed Hogan's request and denied\n\nas moot defendants' motion to compel arbitration. On May 17,\n\n2017, Hogan filed \"Plaintiff's First Amended Class Action\n\nComplaint and Demand for Jury Trial\" (the \"Amended Complaint\"),\n\nabandoning all but his claims pursuant to the Massachusetts Wage\n\nAct, Mass. Gen. Laws ch. 149, §§ 148, 150, and the Massachusetts\n\nIndependent Contractor Statute, Mass. Gen. Laws ch. 149, § 148B.\n\n In response, SBS and SPAR renewed their request to compel\n\narbitration. In essence, they argued that both were shielded by\n\nthe Master Agreement's arbitration provision (although SPAR was\n\nnot a signatory) and that Hogan's consent to waive class and\n\n\n -5-\n\frepresentative actions was valid and enforceable. In the\n\nalternative, they moved to dismiss the Amended Complaint under\n\nFed. R. Civ. P. 12(b)(6).\n\n On March 12, 2018, the district court denied the motion\n\nto compel arbitration as to SPAR, finding that it had no legal\n\nbasis to compel Hogan to arbitration. As to SBS, the district\n\ncourt noted that Hogan was not contesting that his claims were\n\nsubject to arbitration, but rather that the court was barred from\n\nenforcing the arbitration agreement pursuant to the National Labor\n\nRelations Act because it precluded him from pursuing class remedies\n\nin legal proceedings. Because a similar issue was before the U.S.\n\nSupreme Court at the time, the district court stayed Hogan's case\n\nas to SBS to await the ruling in Lewis v. Epic Sys. Corp., 823\n\nF.3d 1147 (7th Cir. 2016), cert. granted, 137 S. Ct. 809 (2017).\n\nFinally, the district court denied the Fed. R. Civ. P. 12(b)(6)\n\ndismissal request. On April 4, 2018, SPAR filed a notice of appeal.3\n\n After SPAR filed its notice of appeal, the Supreme Court\n\ndecided in Epic Sys. Corp. v. Lewis, 138 S. Ct. 1612, 1632 (2018),\n\nthat employees' arbitration agreements waiving class and\n\n\n3 Although generally, interlocutory orders are not immediately\nappealable, see 28 U.S.C. § 1291, the Federal Arbitration Act\ncreates an exception for orders denying petitions to compel\narbitration, see 9 U.S.C. § 16(a)(1)(B). Campbell v. Gen.\nDynamics Gov't Sys. Corp., 407 F.3d 546, 550 (1st Cir. 2005) (so\nnoting).\n\n\n -6-\n\fcollective action procedures are enforceable, as pertinent here.\n\nIn response, the district court dismissed Hogan's claims against\n\nSBS, compelling arbitration of those claims.\n\n II. Analysis\n\n \"We review de novo a district court's interpretation of\n\nan arbitration agreement and its decision regarding whether or not\n\nto compel arbitration.\" Ouadani v. TF Final Mile LLC, 876 F.3d\n\n31, 36 (1st Cir. 2017) (citing S. Bay Bos. Mgmt. v. Unite Here,\n\nLocal 26, 587 F.3d 35, 42 (1st Cir. 2009)).\n\n \"[A]rbitration is a matter of contract and a party cannot\n\nbe required to submit to arbitration any dispute which [it] has\n\nnot agreed so to submit.\" McCarthy v. Azure, 22 F.3d 351, 354\n\n(1st Cir. 1994) (quoting AT&T Techs., Inc. v. Commc'ns Workers,\n\n475 U.S. 643, 648 (1986)). Thus, a party that attempts to compel\n\narbitration \"must show [1] that a valid agreement to arbitrate\n\nexists, [2] that the movant is entitled to invoke the arbitration\n\nclause, [3] that the other party is bound by that clause, and [4]\n\nthat the claim asserted comes within the clause's scope.\"\n\nOuadani, 876 F.3d at 36 (quoting InterGen, 344 F.3d at 142).\n\n While SPAR invokes the \"federal policy favoring\n\narbitration,\" such policy \"presumes proof of a preexisting\n\nagreement to arbitrate disputes arising between the protagonists.\"\n\nMcCarthy, 22 F.3d at 355. As this court has highlighted,\n\n\n -7-\n\f\"arbitration is a matter of consent, not coercion.\" Ouadani, 876\n\nF.3d at 36 (quoting Stolt-Nielsen S.A. v. AnimalFeeds Int'l Corp.,\n\n559 U.S. 662, 681 (2010)).\n\n Here, SPAR faces a steep climb, as it concedes that it\n\nis not a party to the Master Agreement it invokes. Indeed, the\n\nMaster Agreement's first sentence clearly establishes Hogan and\n\nSBS (not SPAR) as the only parties: \"[t]his Independent Contractor\n\nMaster Agreement ('Master Agreement') is entered into between\n\nHogan Paradise ('Independent Contractor') and SPAR Business\n\nServices, Inc. ('SBS').\" Most crucially, the Master Agreement's\n\narbitration clause specifically limits its applicability to \"the\n\nParties.\" It states that: \"[a]ny dispute between the Parties\n\nrelating to this Master Agreement or otherwise arising out of their\n\nrelationship under its terms . . . shall be determined by\n\narbitration.\" (Emphasis added).\n\n Nonetheless, SPAR claims that despite not being a party\n\nto the Master Agreement, it is \"entitled to invoke the arbitration\n\nclause.\" It posits that: (1) it is a third-party beneficiary of\n\nthe agreement between Hogan and SBS; and (2) Hogan is equitably\n\nestopped from avoiding arbitration of his claims against SPAR.4\n\n\n4 Hogan argues that Spar waived its equitable estoppel and third-\nparty beneficiary arguments because they were insufficiently\nraised at the district court level. Because the district court\nunderstood it had enough material to rule on those issues, we will\nnot deem them waived. See Rodríguez-López v. Triple-S Vida, Inc.,\n\n -8-\n\fThis Circuit has recognized that in certain exceptional\n\nsituations, a nonsignatory to an agreement may invoke an\n\narbitration clause. See Grand Wireless, Inc. v. Verizon Wireless,\n\nInc., 748 F.3d 1, 9-10 (1st Cir. 2014) (applying principles of\n\nagency to find that employees, acting within the scope of their\n\nemployment, can invoke an arbitration provision adopted by their\n\nemployer). This is not such a case.5\n\nA. SPAR is not a third-party beneficiary of the Independent\n Contractor Master Agreement\n\n \"As is generally the case in matters of contract\n\ninterpretation, '[t]he crux in third-party beneficiary analysis\n\n. . . is the intent of the parties.'\" McCarthy, 22 F.3d at 362\n\n(alterations in original) (quoting Mowbray v. Moseley, Hallgarten,\n\n\n\n\n850 F.3d 14, 21 n.3 (1st Cir. 2017) (\"We note that the district\ncourt found Rodríguez had sufficiently preserved her . . .\nargument, and we find so as well.\").\n5 The district court applied federal common law to evaluate\nwhether a non-signatory can invoke an arbitration provision,\n\"absent any contention from Hogan.\" On appeal, the parties do not\ncontest this. See Sourcing Unlimited, Inc. v. Asimco Int'l, Inc.,\n526 F.3d 38, 46 (1st Cir. 2008) (\"In the absence of any contention\nfrom the parties to the contrary, we apply federal common law to\nresolve the issues.\" (citing InterGen, 344 F.3d at 143)); see also\nOuadani, 876 F.3d at 37 (looking to \"federal common law, which\nincorporates 'general principles of contract and agency law,'\" to\ndetermine whether a nonsignatory to an arbitration agreement was\nbound to arbitrate his claim (citing InterGen, 344 F.3d at 144)).\nBut see Grand Wireless, 748 F.3d at 11-12 (calling into question\nthe propriety of using federal law to determine whether a non-\nparty to an arbitration agreement can assert its protection).\n\n\n -9-\n\fEstabrook & Weeden, 795 F.2d 1111, 1117 (1st Cir. 1986)). A third-\n\nparty beneficiary must demonstrate with \"special clarity that the\n\ncontracting parties intended to confer a benefit on him,\"\n\nconsidering that such status is \"an exception to the general rule\n\nthat a contract does not grant enforceable rights to\n\nnonsignatories.\" Id. In evaluating whether such \"special clarity\"\n\nexists, a court should focus on the \"specific terms\" of the\n\nagreement at issue, being mindful that it \"ought not to distort\n\nthe clear intention of contracting parties or reach conclusions at\n\nodds with the unambiguous language of a contract.\" InterGen, 344\n\nF.3d at 146 (citing EEOC v. Waffle House, Inc., 534 U.S. 279, 294\n\n(2002)).\n\n SPAR concedes that it is not named in the Master\n\nAgreement, but essentially argues that it is a third-party\n\nbeneficiary because the Master Agreement confers upon it, \"as a\n\ncustomer of SBS,\" the right to dictate certain work requirements\n\nto the independent contractor. We gather that SPAR refers to\n\nparagraph nine of the Master Agreement, yet that clause merely\n\nstates that SBS would convey to Hogan scheduling and assignment\n\nrequirements, if any, that it received from its customers, which\n\ninclude SPAR. At best, this is a tenuous grant of a vague benefit.\n\nIt does not come close to showing the requisite \"special clarity.\"\n\nMoreover, even if SPAR could be said to benefit from the clause,\n\n\n -10-\n\f\"a mere benefit to the nonsignatory resulting from a signatory's\n\nexercise of its contractual rights is not enough.\" Ouadani, 876\n\nF.3d at 39 (1st Cir. 2017) (citing InterGen, 344 F.3d at 146-47).\n\nRather, the contract must \"mention [or] manifest an intent to\n\nconfer specific legal rights upon [SPAR],\" and the contract\n\nlanguage that SPAR points us to does not make the cut. InterGen,\n\n344 F.3d at 147.\n\n Finally, even if SPAR could show an intent of the parties\n\nto confer upon it some benefit unrelated to arbitration, the\n\nlanguage of the arbitration clause would still be dispositive. As\n\nmentioned earlier, the arbitration clause limits its applicability\n\nto the signatories by only covering disputes \"between the Parties,\"\n\nso it is clear that it does not confer arbitration rights to SPAR\n\nor any third party.\n\n Our conclusion is reinforced by the fact that the Master\n\nAgreement references SBS's \"customers\" in other sections, yet\n\nomits that reference in the arbitration clause. SBS could have\n\neasily modified the arbitration clause to make it applicable to\n\n\"[a]ny dispute between the Parties [and/or any SBS customer]\n\nrelating to this Master Agreement,\" but it did not. See Mowbray,\n\n795 F.2d at 1118 (finding persuasive the appellants' argument that\n\ngiven \"the probable sophistication of the drafters of the\n\nagreement, . . . the omission of defendants from the arbitration\n\n\n -11-\n\fclause must be regarded as purposeful\"); see also Cortés-Ramos v.\n\nMartin-Morales, 894 F.3d 55, 59-60 (1st Cir. 2018) (holding that\n\nnonsignatory singer, Ricky Martin, could not compel arbitration\n\nbased on an agreement that referenced him in certain provisions\n\nbut did not in its arbitration clause).\n\n Finally, the Agreement has an integration clause that\n\nreads:\n\n This Master Agreement constitutes the complete,\n integrated agreement of Independent Contractor and\n SBS and supersedes all prior written and oral\n agreements, negotiations, promises, and\n representations, if any. Nothing contained in this\n Master Agreement may be modified in any way except\n through a written agreement signed by Independent\n Contractor and Mr. Robert Brown of SBS.\n\nThis language accentuates the parties' intent to confine to its\n\nsignatories the right to invoke the Master Agreement's arbitration\n\nclause. See McCarthy v. Azure, 22 F.3d 351, 358 (1st Cir. 1994)\n\n(stating that \"[t]he intent to limit arbitral rights to signatories\n\nis also made manifest by the inclusion of an integration clause\").\n\n Thus, a review of the language of the Master Agreement,\n\nand more particularly its arbitration clause, shows that SPAR was\n\nnot an intended third-party beneficiary of the signatories'\n\nagreement to arbitrate. See InterGen, 344 F.3d at 146 (declining\n\nto read into agreement \"rights and obligations that the contracting\n\nparties did not see fit to include\").\n\n\n\n -12-\n\fB. Hogan is not equitably estopped from avoiding arbitration of\n his claims against SPAR\n\n SPAR propounds that, even if it is not a signatory to\n\nthe Agreement, Hogan is nevertheless equitably estopped from\n\navoiding arbitration because his claims against SPAR are\n\n\"intertwined\" with the Master Agreement and because SPAR and SBS,\n\nwhich is a signatory to the Agreement, are \"closely related.\"\n\nSPAR primarily relies on Sourcing Unlimited, Inc. v. Asimco Int'l,\n\nInc., 526 F.3d 38 (1st Cir. 2008).\n\n \"[E]quitable estoppel precludes a party from enjoying\n\nrights and benefits under a contract while at the same time\n\navoiding its burdens and obligations.\" InterGen, 344 F.3d at 145.\n\nGenerally, federal courts \"have been willing to estop a signatory\n\nfrom avoiding arbitration with a nonsignatory when the issues . . .\n\nto resolve in arbitration are intertwined with the agreement that\n\nthe estopped party has signed.\" Ouadani, 876 F.3d at 38 (second\n\nemphasis added) (quoting InterGen, 344 F.3d at 145).\n\n In Sourcing Unlimited, 526 F.3d at 46-48, this court\n\napplied equitable estoppel to hold that the plaintiff, a corporate\n\nsignatory to a partnership agreement, was compelled to arbitrate\n\nits claims against a non-signatory defendant. The court found\n\nthat the plaintiff's claims were \"sufficiently intertwined\" with\n\nthe agreement that the plaintiff had signed with the defendant's\n\nparent company. Id. at 47. Hence, it reversed and remanded with\n\n -13-\n\finstructions to the district court to compel arbitration. Id. at\n\n48.\n\n We find Sourcing Unlimited distinguishable from the case\n\nat hand. First, prior to considering the \"intertwined\"\n\nrequirement, we must step back and once again recur to the language\n\nof the arbitration clauses. In Sourcing Unlimited, the \"broadly-\n\nworded\" arbitration clause stated: \"[a]ny action to enforce,\n\narising out of, or relating in any way to, any of the provisions\n\nof this agreement shall be brought in front of a P.R. China\n\narbitration body.\" Id. at 41 (emphasis added). Having the\n\nplaintiff consented to arbitrate any action \"arising out of, or\n\nrelating in any way to\" the agreement, the court applied the\n\nequitable estoppel doctrine to enforce arbitration of claims that\n\nfell within the scope of the arbitration clause and were\n\nintertwined with the agreement but were brought against a non-\n\nsignatory subsidiary. Id. at 48.\n\n Unlike Sourcing Unlimited, the arbitration provision\n\nhere cabins its scope to disputes \"between the Parties\" to the\n\nMaster Agreement, with the \"Parties\" unambiguously defined as SBS\n\nand Hogan. While one could say that arbitrating a dispute relating\n\nto the contract against an affiliated third-party was within the\n\nscope of what the plaintiff consented to in Sourcing Unlimited,\n\n\n\n\n -14-\n\fthe same cannot be said here. Hogan clearly and unambiguously\n\nconsented to arbitrate only claims between him and SBS.6\n\n And while SPAR alleges that its \"close relationship\"7\n\nwith SBS should bind Hogan, we need not delve into the nature of\n\n\n\n6 Similarly, Spar cites Herrera-Gollo v. Seaborne Puerto Rico,\nLLC, Civil No. 15-1771(JAG), 2017 WL 657430 (D.P.R. Feb. 17, 2017)\nand Ragone v. Atl. Video at Manhattan Ctr., 595 F.3d 115 (2d Cir.\n2010) as persuasive authority. Irrespective of whether we agree\nwith their outcome and analysis, which we need not discuss now,\nthose cases are distinguishable due to the broad reach of the\narbitration clauses at issue therein.\n\nIn Herrera-Gollo, the plaintiff argued that defendant Seaborne\nPuerto Rico could not invoke the arbitration clause because the\nagreement was signed by Seaborne Virgin Islands, Inc., but the\narbitration provision covered \"all claims, controversies, or\ndisputes . . . against the Company, its shareholders or subsidiary\nor parent or affiliated companies . . . arising out of or in any\nway relating to [plaintiff's] application for employment.\"\nHerrera-Gollo, 2017 WL 657430, at *3 (emphasis added) (emphasis in\noriginal omitted). The court concluded that \"the language evinces\na broad intent that Plaintiff be required to arbitrate claims\nagainst a variety of entities associated with Seaborne Virgin\nIslands, not just that specific entity\" and compelled plaintiff to\narbitrate his claims against Seaborne Puerto Rico even though it\nhad not signed the agreement. Id. at *7. The same intent is not\nevidenced by the language of the Master Agreement.\n\nIn Ragone, the court compelled plaintiff Rita Ragone to arbitrate\nher employment discrimination claims against her direct employer,\nAtlantic Video (\"AVI\"), and ESPN, for whom she provided services\nthrough AVI, finding that she was equitably estopped from avoiding\narbitration as to ESPN. Nevertheless, once again, the pertinent\narbitration clause there was broader, as she had agreed to\narbitrate \"any and all claims or controversies arising out of [her]\nemployment or its termination.\" Ragone, 595 F.3d at 118.\n\nLikewise, the other non-binding cases that Spar cites do not\npersuade us to alter our reasoning here.\n7 According to the Amended Complaint, \"SBS is an affiliate of\n\n -15-\n\ftheir relationship, as irrespective of it, SPAR has not shown any\n\nintent on behalf of Hogan to arbitrate with any entity other than\n\nSBS. See Sokol Holdings, Inc. v. BMB Munai, Inc., 542 F.3d 354,\n\n361–62 (2d Cir. 2008) (noting that any relationship among parties\n\nmust support the conclusion that the signatory \"consented to extend\n\nits agreement to arbitrate\" to the nonsignatory). SBS and SPAR\n\nare sophisticated commercial players that chose to conduct their\n\nbusiness as separate corporate structures, and we see no reason to\n\nignore the legal scheme that they constructed. Hence, SPAR has\n\nnot put forth any convincing argument or authority establishing\n\nthat the equitable estoppel doctrine is applicable when the\n\nlanguage of the contract is so clearly limiting, and we find no\n\nlegal basis for forcing Hogan to arbitrate his claims against SPAR\n\nwhen he demonstrated no intent to do so.\n\n In any case, a review of the facts here shows that SPAR\n\ncould not establish the \"intertwined\" requirement for purposes of\n\napplying equitable estoppel. In Sourcing Unlimited the court\n\nconcluded that the plaintiff's claims were \"sufficiently\n\nintertwined\" with the agreement because they \"either directly or\n\nindirectly invoke[d] the terms of the\" agreement, id. at 47, and\n\nthey \"ultimately derive[d] from benefits\" the plaintiff alleged\n\n\n\n\nSPAR but is not a subsidiary of or controlled by SPAR . . . .\"\n\n\n -16-\n\fwere due under the agreement, id. at 48. Moreover, the court\n\nnoted that if the agreement were to become void, the plaintiff's\n\nobligations under a side-contract with defendant \"would be\n\nmeaningless.\" Id.\n\n Here, Hogan's claims against SPAR are premised upon\n\nMassachusetts wage and hour law, not the Master Agreement between\n\nSBS and Hogan: he seeks a remedy for \"unpaid wages and benefits\"\n\nwhich he alleges he has a right to pursuant to Massachusetts law.\n\nMoreover, Hogan's claims would exist even if the Master Agreement\n\nwere declared void, as they are based on the nature of the services\n\nthat Hogan provided to SPAR. Finally, as the Amended Complaint\n\nshows, Hogan does not claim any benefit or right from SPAR arising\n\nfrom the Master Agreement. See Sourcing Unlimited, 526 F.3d at\n\n47 (\"The [signatory] plaintiff's actual dependence on the\n\nunderlying contract in making out the claim against the\n\nnonsignatory defendant is therefore always the sine qua non of an\n\nappropriate situation for applying equitable estoppel [against the\n\nplaintiff].\" (alteration in original) (quoting In re Humana Inc.\n\nManaged Care Litig., 285 F.3d 971, 976 (11th Cir. 2002), rev'd on\n\nother grounds sub nom. PacifiCare Health Sys., Inc. v. Book, 538\n\nU.S. 401 (2003))). There is therefore no cognizable basis for\n\napplying equitable estoppel here.\n\n\t\n\n\n -17-\n\f III. Conclusion\n\n We find no legal basis to compel Hogan to arbitration,\n\nas the clear terms of the Master Agreement show that he did not\n\nconsent to arbitrate his claims against SPAR. The district\n\ncourt's judgment is therefore affirmed.\n\n Affirmed.\n\n\n\n\n -18-\n[END_CASE]", "role": "user" } ]
4,584,946
Jose Gilberto Batres AGUSTIN, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.
Batres Agustin v. Whitaker
2019-01-25
18-1469P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Kayatta, Barron", "parties": "", "opinions": [{"author": "BARRON, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1469\n\n JOSE GILBERTO BATRES AGUSTIN,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n Lidia M. Sanchez, on brief for petitioner.\n Walter Bocchini, Trial Attorney, Joseph H. Hunt, Assistant\nAttorney General, and Linda S. Wernery, Assistant Director, Office\nof Immigration Litigation, U.S. Department of Justice, on brief\nfor respondent.\n\n\n January 25, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions III as the respondent.\n\f BARRON, Circuit Judge. Jose Gilberto Batres Agustin\n\n(\"Batres Agustin\") is a Guatemalan national. He petitions for\n\nreview of the Board of Immigration Appeals' (\"BIA\") order, which\n\nupheld the Immigration Judge's (\"IJ\") denial of his application\n\nfor both withholding of removal under 8 U.S.C. § 1231(b)(3) and\n\nprotection under the Convention Against Torture (\"CAT\") under 8\n\nC.F.R. § 208.16(c)(4). We deny the petition.\n\n I.\n\n Batres Agustin entered the United States illegally in\n\nDecember of 1989. During his nearly thirty years in the United\n\nStates, Batres Agustin was convicted three times of driving under\n\nthe influence. After his most recent arrest in 2015 for driving\n\nunder the influence, he was taken into custody by the Department\n\nof Homeland Security (\"DHS\"), and, on December 2, 2015, DHS\n\ninitiated removal proceedings against him before an IJ in Boston,\n\nMassachusetts.\n\n Prior to those proceedings, Batres Agustin filed an I-\n\n589 Application for Asylum and Withholding of Removal under §\n\n241(b)(3) of the Immigration and Nationality Act (\"INA\"). He\n\nindicated in this application that he anticipated \"mistreatment at\n\nthe hands of the [gangs] and criminal elements in Guatemala\" were\n\nhe to return to his home country and that his brother and daughter\n\nhad experienced gang violence in Guatemala in the past when they\n\nrefused to comply with the gangs' extortionist demands. He further\n - 2 -\n\findicated that he sought withholding of removal based on\n\n\"membership in a particular social group\" and that he was not\n\nafraid of being subjected to torture if he returned to Guatemala.\n\n Batres Agustin's removal hearing was held on July 26,\n\n2017. In seeking asylum and withholding of removal, he testified\n\nthat he feared extortion and violence from local gangs were he to\n\nreturn to his home country. He also testified that his family had\n\nexperienced gang violence there in the past and noted that he was\n\nparticularly apprehensive, as someone returning from the United\n\nStates, because \"the [gangs] ask for money as soon as they know\n\nthat you're coming back from [the United States].\" When pressed\n\nby his attorney as to his precise fears regarding his return,\n\nBatres Agustin stated that he was \"accustomed\" to life in the\n\nUnited States and, for that reason, was afraid of \"start[ing] over\"\n\nin Guatemala.\n\n At the hearing's conclusion, the IJ ruled that the asylum\n\napplication was untimely and that Batres Agustin had failed to\n\nestablish a well-founded fear of persecution upon his return to\n\nGuatemala based on one of the five protected grounds enumerated in\n\n8 U.S.C. § 1231(b)(3)(A) and thus was not entitled to withholding\n\nof removal. Additionally, the IJ ruled that Batres Agustin was\n\n\n\n\n - 3 -\n\fnot entitled to protection under the CAT because he made no claim\n\nthat he would be tortured by anyone if he returned to Guatemala.1\n\n On August 24, 2017, Batres Agustin appealed the IJ's\n\ndecision to the BIA. In affirming the IJ's ruling on April 20,\n\n2018, the BIA found that Batres Agustin's application for asylum\n\nwas untimely because it was filed well after the one-year deadline.\n\nThe BIA also rejected his application for withholding of removal\n\nbecause he had failed to \"demonstrate past persecution or that any\n\nfeared harm would be on account of a protected ground.\" In so\n\nfinding, the BIA determined that the petitioner \"did not\n\ndemonstrate a pattern or practice of persecution of a group of\n\nsimilarly situated people\" due to any protected ground. Finally,\n\nthe BIA rejected Batres Agustin's CAT claim because he had failed\n\nto \"testify regarding any past torture or fear of future torture.\"\n\nBatres Agustin timely petitioned for review of the BIA's ruling on\n\nMay 18, 2018.\n\n II.\n\n Where, as here, the BIA issues its own opinion without\n\nadopting the IJ's rationale, we review the BIA's decision. See\n\nTouch v. Holder, 568 F.3d 32, 37-38 (1st Cir. 2009). Our review\n\n\n\n\n 1 Batres Agustin's I-589 Application did not purport to seek\nrelief under the CAT, and, therefore, it appears that the IJ\naddressed and rejected the prospect of CAT relief of its own\naccord.\n - 4 -\n\fof the BIA's denial of claims for withholding of removal and for\n\nCAT protection is for \"substantial evidence.\" Id. at 38 (quoting\n\nRashad v. Mukasey, 554 F.3d 1, 4 (1st Cir. 2009)). \"Under this\n\nstandard, we do not disturb [factual] findings if they are\n\n'supported by reasonable, substantial, and probative evidence on\n\nthe record considered as a whole.'\" Id. (quoting Segran v.\n\nMukasey, 511 F.3d 1, 5 (1st Cir. 2007)). \"We reverse only if 'any\n\nreasonable adjudicator would be compelled to conclude to the\n\ncontrary.'\" Id. (quoting Tobon-Marin v. Mukasey, 512 F.3d 28, 30\n\n(1st Cir. 2008)). We review purely legal questions, however, de\n\nnovo. Segran, 511 F.3d at 5.2\n\n To establish eligibility for withholding of removal, a\n\npetitioner must show \"a clear probability of persecution,\" Ang v.\n\nGonzales, 430 F.3d 50, 58 (1st Cir. 2005), based on \"race,\n\n\n\n\n 2\n Batres Agustin concedes that his asylum claim was untimely,\nbut he argues for the first time to us that he qualifies for an\nexception to the one-year filing window due to the District Court\nfor the Western District of Washington's recent decision in Rojas\nv. Johnson, 305 F. Supp. 3d 1176 (W.D. Wash. 2018). However, we\nare not bound by that precedent, and, insofar as Batres Agustin\nmeans to rely on the reasoning set forth in Rojas, the argument is\nwaived, as Batres Agustin did not raise that argument to the BIA.\nSee Vineberg v. Bissonnette, 548 F.3d 50, 57-58 (1st Cir. 2008).\nSeparately, Batres Agustin states in a sentence in a footnote in\nhis brief to us that the notice to appear that he received did not\ncomply with the requirements established by the Supreme Court in\nits recent opinion in Pereira v. Sessions, 138 S. Ct. 2105 (2018).\nBut this argument, too, is waived, as it is not adequately\ndeveloped. See United States v. Zannino, 895 F.2d 1, 17 (1st Cir.\n1990).\n - 5 -\n\freligion, nationality, membership in a particular social group, or\n\npolitical opinion,\" 8 U.S.C. § 1231(b)(3)(A). The BIA concluded,\n\nhowever, that Batres Agustin had not shown past persecution or\n\nthat \"any feared harm would be on account of a protected ground.\"\n\nIn so concluding, the BIA found that his general fear of civil\n\nunrest in Guatemala did not suffice to show a probable fear of\n\npersecution and that, to the extent that the particular social\n\ngroup to which he claimed to belong was \"wealthy individuals\n\nreturning from a lengthy stay in the United States,\" that class of\n\npersons did not constitute a protected social group under 8 U.S.C.\n\n§ 1231(b)(3)(A). The BIA also found that he \"did not demonstrate\n\na pattern or practice of persecution of a group of similarly\n\nsituated people\" due to any protected ground.\n\n Batres Agustin does not dispute that, as the BIA noted,\n\na consistent line of our precedent supports the conclusion that\n\nwealthy Guatemalans returning to Guatemala do not constitute a\n\nprotected social group. See, e.g., Sicaju-Diaz v. Holder, 663\n\nF.3d 1, 4 (1st Cir. 2011) (rejecting the claim that wealthy\n\nGuatemalans returning from the United States constitute a\n\nprotected social group); Garcia-Callejas v. Holder, 666 F.3d 828,\n\n830 (1st Cir. 2012) (holding the same for wealthy El Salvadorans);\n\nLópez-Castro v. Holder, 577 F.3d 49, 54 (1st Cir. 2009) (per\n\ncuriam) (\"A country-wide risk of victimization through economic\n\nterrorism is not the functional equivalent of a statutorily\n - 6 -\n\fprotected ground.\"). Nor does he dispute that, before the BIA,\n\nthe only social group to which he claimed to belong was one\n\ncomprised of wealthy individuals returning to Guatemala. But,\n\nBatres Agustin argues, our line of precedent on which the BIA\n\nrelied does not control here.\n\n Batres Agustin first attempts to distinguish his case by\n\ncontending that the record shows that his family has already\n\nexperienced the type of violence that he fears will befall him if\n\nhe returns. But, as Batres Agustin did not contend below -- and\n\ndoes not argue to us -- that he has been or would be targeted on\n\nthe basis of his family status, this contention does not undermine\n\nthe BIA's ruling that the only social group to which Batres Agustin\n\nclaimed to belong -- wealthy individuals returning to Guatemala\n\n-- was not a social group that the statute protected.\n\n Batres Agustin also contends that his case may be\n\ndistinguished because he is an elderly man with no \"social support\"\n\nin Guatemala. But, again, this assertion is beside the point, as\n\nit, too, fails to show that the only social group to which he\n\nclaimed to belong is a statutorily protected one.\n\n All that remains for us to consider, therefore, is Batres\n\nAgustin's challenge to the BIA's ruling that he is not entitled to\n\nprotection under the CAT. The BIA so ruled because it concluded\n\nthat Batres Agustin had failed to establish that he feared torture\n\n\"inflicted by, at the direction of, or with the acquiescence of\n - 7 -\n\fgovernment officials.\" Hincapie v. Gonzales, 494 F.3d 213, 221\n\n(1st Cir. 2007). Batres Agustin correctly points out that, even\n\nthough he did not raise a CAT claim before the IJ or the BIA, the\n\nIJ and the BIA each addressed it. And, he now contends, the BIA's\n\nrejection of it is not supported by substantial evidence because\n\nthe record suffices to show that his fear of gang violence stems\n\nfrom the fact that the Guatemalan government \"has been ineffective\n\nin controlling\" Guatemalan gangs. But, evidence of that general\n\nkind does not suffice to show that the BIA's finding is not\n\nsupported by substantial evidence. See Alvizures–Gomes v. Lynch,\n\n830 F.3d 49, 55 (1st Cir. 2016) (holding that generalized\n\nallegations of corruption in the Guatemalan government did not\n\nabsolve the petitioner of the requirement that he provide specific\n\nevidence that he faced a risk of torture as a direct result of\n\nthat corruption). Thus, this aspect of Batres Agustin's challenge\n\nfails as well.\n\n III.\n\n The petition for review is denied.\n\n\n\n\n - 8 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362199/", "author_raw": "BARRON, Circuit Judge"}]}
TORRUELLA
KAYATTA
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584946/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Jose Gilberto Batres AGUSTIN, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1469\n\n JOSE GILBERTO BATRES AGUSTIN,\n\n Petitioner,\n\n v.\n\n MATTHEW G. WHITAKER,\n ACTING ATTORNEY GENERAL,\n\n Respondent.\n\n\n PETITION FOR REVIEW OF AN ORDER OF THE\n BOARD OF IMMIGRATION APPEALS\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n Lidia M. Sanchez, on brief for petitioner.\n Walter Bocchini, Trial Attorney, Joseph H. Hunt, Assistant\nAttorney General, and Linda S. Wernery, Assistant Director, Office\nof Immigration Litigation, U.S. Department of Justice, on brief\nfor respondent.\n\n\n January 25, 2019\n\n\n\n\n \n Pursuant to Fed. R. App. P. 43(c)(2), Acting Attorney\nGeneral Matthew G. Whitaker has been substituted for former\nAttorney General Jefferson B. Sessions III as the respondent.\n\f BARRON, Circuit Judge. Jose Gilberto Batres Agustin\n\n(\"Batres Agustin\") is a Guatemalan national. He petitions for\n\nreview of the Board of Immigration Appeals' (\"BIA\") order, which\n\nupheld the Immigration Judge's (\"IJ\") denial of his application\n\nfor both withholding of removal under 8 U.S.C. § 1231(b)(3) and\n\nprotection under the Convention Against Torture (\"CAT\") under 8\n\nC.F.R. § 208.16(c)(4). We deny the petition.\n\n I.\n\n Batres Agustin entered the United States illegally in\n\nDecember of 1989. During his nearly thirty years in the United\n\nStates, Batres Agustin was convicted three times of driving under\n\nthe influence. After his most recent arrest in 2015 for driving\n\nunder the influence, he was taken into custody by the Department\n\nof Homeland Security (\"DHS\"), and, on December 2, 2015, DHS\n\ninitiated removal proceedings against him before an IJ in Boston,\n\nMassachusetts.\n\n Prior to those proceedings, Batres Agustin filed an I-\n\n589 Application for Asylum and Withholding of Removal under §\n\n241(b)(3) of the Immigration and Nationality Act (\"INA\"). He\n\nindicated in this application that he anticipated \"mistreatment at\n\nthe hands of the [gangs] and criminal elements in Guatemala\" were\n\nhe to return to his home country and that his brother and daughter\n\nhad experienced gang violence in Guatemala in the past when they\n\nrefused to comply with the gangs' extortionist demands. He further\n - 2 -\n\findicated that he sought withholding of removal based on\n\n\"membership in a particular social group\" and that he was not\n\nafraid of being subjected to torture if he returned to Guatemala.\n\n Batres Agustin's removal hearing was held on July 26,\n\n2017. In seeking asylum and withholding of removal, he testified\n\nthat he feared extortion and violence from local gangs were he to\n\nreturn to his home country. He also testified that his family had\n\nexperienced gang violence there in the past and noted that he was\n\nparticularly apprehensive, as someone returning from the United\n\nStates, because \"the [gangs] ask for money as soon as they know\n\nthat you're coming back from [the United States].\" When pressed\n\nby his attorney as to his precise fears regarding his return,\n\nBatres Agustin stated that he was \"accustomed\" to life in the\n\nUnited States and, for that reason, was afraid of \"start[ing] over\"\n\nin Guatemala.\n\n At the hearing's conclusion, the IJ ruled that the asylum\n\napplication was untimely and that Batres Agustin had failed to\n\nestablish a well-founded fear of persecution upon his return to\n\nGuatemala based on one of the five protected grounds enumerated in\n\n8 U.S.C. § 1231(b)(3)(A) and thus was not entitled to withholding\n\nof removal. Additionally, the IJ ruled that Batres Agustin was\n\n\n\n\n - 3 -\n\fnot entitled to protection under the CAT because he made no claim\n\nthat he would be tortured by anyone if he returned to Guatemala.1\n\n On August 24, 2017, Batres Agustin appealed the IJ's\n\ndecision to the BIA. In affirming the IJ's ruling on April 20,\n\n2018, the BIA found that Batres Agustin's application for asylum\n\nwas untimely because it was filed well after the one-year deadline.\n\nThe BIA also rejected his application for withholding of removal\n\nbecause he had failed to \"demonstrate past persecution or that any\n\nfeared harm would be on account of a protected ground.\" In so\n\nfinding, the BIA determined that the petitioner \"did not\n\ndemonstrate a pattern or practice of persecution of a group of\n\nsimilarly situated people\" due to any protected ground. Finally,\n\nthe BIA rejected Batres Agustin's CAT claim because he had failed\n\nto \"testify regarding any past torture or fear of future torture.\"\n\nBatres Agustin timely petitioned for review of the BIA's ruling on\n\nMay 18, 2018.\n\n II.\n\n Where, as here, the BIA issues its own opinion without\n\nadopting the IJ's rationale, we review the BIA's decision. See\n\nTouch v. Holder, 568 F.3d 32, 37-38 (1st Cir. 2009). Our review\n\n\n\n\n 1 Batres Agustin's I-589 Application did not purport to seek\nrelief under the CAT, and, therefore, it appears that the IJ\naddressed and rejected the prospect of CAT relief of its own\naccord.\n - 4 -\n\fof the BIA's denial of claims for withholding of removal and for\n\nCAT protection is for \"substantial evidence.\" Id. at 38 (quoting\n\nRashad v. Mukasey, 554 F.3d 1, 4 (1st Cir. 2009)). \"Under this\n\nstandard, we do not disturb [factual] findings if they are\n\n'supported by reasonable, substantial, and probative evidence on\n\nthe record considered as a whole.'\" Id. (quoting Segran v.\n\nMukasey, 511 F.3d 1, 5 (1st Cir. 2007)). \"We reverse only if 'any\n\nreasonable adjudicator would be compelled to conclude to the\n\ncontrary.'\" Id. (quoting Tobon-Marin v. Mukasey, 512 F.3d 28, 30\n\n(1st Cir. 2008)). We review purely legal questions, however, de\n\nnovo. Segran, 511 F.3d at 5.2\n\n To establish eligibility for withholding of removal, a\n\npetitioner must show \"a clear probability of persecution,\" Ang v.\n\nGonzales, 430 F.3d 50, 58 (1st Cir. 2005), based on \"race,\n\n\n\n\n 2\n Batres Agustin concedes that his asylum claim was untimely,\nbut he argues for the first time to us that he qualifies for an\nexception to the one-year filing window due to the District Court\nfor the Western District of Washington's recent decision in Rojas\nv. Johnson, 305 F. Supp. 3d 1176 (W.D. Wash. 2018). However, we\nare not bound by that precedent, and, insofar as Batres Agustin\nmeans to rely on the reasoning set forth in Rojas, the argument is\nwaived, as Batres Agustin did not raise that argument to the BIA.\nSee Vineberg v. Bissonnette, 548 F.3d 50, 57-58 (1st Cir. 2008).\nSeparately, Batres Agustin states in a sentence in a footnote in\nhis brief to us that the notice to appear that he received did not\ncomply with the requirements established by the Supreme Court in\nits recent opinion in Pereira v. Sessions, 138 S. Ct. 2105 (2018).\nBut this argument, too, is waived, as it is not adequately\ndeveloped. See United States v. Zannino, 895 F.2d 1, 17 (1st Cir.\n1990).\n - 5 -\n\freligion, nationality, membership in a particular social group, or\n\npolitical opinion,\" 8 U.S.C. § 1231(b)(3)(A). The BIA concluded,\n\nhowever, that Batres Agustin had not shown past persecution or\n\nthat \"any feared harm would be on account of a protected ground.\"\n\nIn so concluding, the BIA found that his general fear of civil\n\nunrest in Guatemala did not suffice to show a probable fear of\n\npersecution and that, to the extent that the particular social\n\ngroup to which he claimed to belong was \"wealthy individuals\n\nreturning from a lengthy stay in the United States,\" that class of\n\npersons did not constitute a protected social group under 8 U.S.C.\n\n§ 1231(b)(3)(A). The BIA also found that he \"did not demonstrate\n\na pattern or practice of persecution of a group of similarly\n\nsituated people\" due to any protected ground.\n\n Batres Agustin does not dispute that, as the BIA noted,\n\na consistent line of our precedent supports the conclusion that\n\nwealthy Guatemalans returning to Guatemala do not constitute a\n\nprotected social group. See, e.g., Sicaju-Diaz v. Holder, 663\n\nF.3d 1, 4 (1st Cir. 2011) (rejecting the claim that wealthy\n\nGuatemalans returning from the United States constitute a\n\nprotected social group); Garcia-Callejas v. Holder, 666 F.3d 828,\n\n830 (1st Cir. 2012) (holding the same for wealthy El Salvadorans);\n\nLópez-Castro v. Holder, 577 F.3d 49, 54 (1st Cir. 2009) (per\n\ncuriam) (\"A country-wide risk of victimization through economic\n\nterrorism is not the functional equivalent of a statutorily\n - 6 -\n\fprotected ground.\"). Nor does he dispute that, before the BIA,\n\nthe only social group to which he claimed to belong was one\n\ncomprised of wealthy individuals returning to Guatemala. But,\n\nBatres Agustin argues, our line of precedent on which the BIA\n\nrelied does not control here.\n\n Batres Agustin first attempts to distinguish his case by\n\ncontending that the record shows that his family has already\n\nexperienced the type of violence that he fears will befall him if\n\nhe returns. But, as Batres Agustin did not contend below -- and\n\ndoes not argue to us -- that he has been or would be targeted on\n\nthe basis of his family status, this contention does not undermine\n\nthe BIA's ruling that the only social group to which Batres Agustin\n\nclaimed to belong -- wealthy individuals returning to Guatemala\n\n-- was not a social group that the statute protected.\n\n Batres Agustin also contends that his case may be\n\ndistinguished because he is an elderly man with no \"social support\"\n\nin Guatemala. But, again, this assertion is beside the point, as\n\nit, too, fails to show that the only social group to which he\n\nclaimed to belong is a statutorily protected one.\n\n All that remains for us to consider, therefore, is Batres\n\nAgustin's challenge to the BIA's ruling that he is not entitled to\n\nprotection under the CAT. The BIA so ruled because it concluded\n\nthat Batres Agustin had failed to establish that he feared torture\n\n\"inflicted by, at the direction of, or with the acquiescence of\n - 7 -\n\fgovernment officials.\" Hincapie v. Gonzales, 494 F.3d 213, 221\n\n(1st Cir. 2007). Batres Agustin correctly points out that, even\n\nthough he did not raise a CAT claim before the IJ or the BIA, the\n\nIJ and the BIA each addressed it. And, he now contends, the BIA's\n\nrejection of it is not supported by substantial evidence because\n\nthe record suffices to show that his fear of gang violence stems\n\nfrom the fact that the Guatemalan government \"has been ineffective\n\nin controlling\" Guatemalan gangs. But, evidence of that general\n\nkind does not suffice to show that the BIA's finding is not\n\nsupported by substantial evidence. See Alvizures–Gomes v. Lynch,\n\n830 F.3d 49, 55 (1st Cir. 2016) (holding that generalized\n\nallegations of corruption in the Guatemalan government did not\n\nabsolve the petitioner of the requirement that he provide specific\n\nevidence that he faced a risk of torture as a direct result of\n\nthat corruption). Thus, this aspect of Batres Agustin's challenge\n\nfails as well.\n\n III.\n\n The petition for review is denied.\n\n\n\n\n - 8 -\n[END_CASE]", "role": "user" } ]
4,585,303
Heather TYLER, Plaintiff, Appellant, v. SUPREME JUDICIAL COURT OF MASSACHUSETTS; Hon. Ralph D. Gants; Hon. Elspeth B. Cypher; Hon. Barbara A. Lenk; Hon. Scott L. Kafker; Hon. Frank M. Gaziano; Hon. David A. Lowy; Hon. Kimberly S. Budd; Maura Healey, Attorney General for the Commonwealth, in Her Official Capacity, Defendants, Appellees.
Tyler v. Supreme Judicial Court of Mass.
2019-01-28
18-1256P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Kayatta, Barron", "parties": "", "opinions": [{"author": "KAYATTA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1256\n\n HEATHER TYLER,\n\n Plaintiff, Appellant,\n\n v.\n\n SUPREME JUDICIAL COURT OF MASSACHUSETTS; HON. RALPH D. GANTS;\n HON. ELSPETH B. CYPHER; HON. BARBARA A. LENK; HON. SCOTT L.\n KAFKER; HON. FRANK M. GAZIANO; HON. DAVID A. LOWY;\n HON. KIMBERLY S. BUDD; MAURA HEALEY, Attorney General for the\n Commonwealth, in her official capacity,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Douglas P. Woodlock, U.S. District Judge]\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n Wendy Murphy for appellant.\n Todd M. Blume, Assistant Attorney General, Criminal Bureau,\nwith whom Maura Healy, Attorney General, was on brief, for\nappellee.\n\n\n January 28, 2019\n\f KAYATTA, Circuit Judge. This appeal arises from Heather\n\nTyler's six-year-long legal battle to void two Massachusetts\n\nSuperior Court conditions of probation imposed on the adult male\n\nwho was convicted of statutory rape after impregnating her when\n\nshe was a minor. The district court found that Tyler's suit was,\n\nin essence, an appeal from a state-court judgment, and that the\n\ndistrict court therefore lacked jurisdiction to hear it under the\n\nRooker-Feldman doctrine.1 For the following reasons, we agree.\n\n I.\n\n In 2009, at age nineteen or twenty, Jamie Melendez\n\nimpregnated fourteen-year-old Heather Tyler.2 Tyler gave birth in\n\n2010. Upon pleading guilty in state court to the statutory rape\n\nof Tyler, Melendez received a sentence of sixteen years of\n\nprobation. As conditions of probation, the sentencing judge\n\nordered Melendez to acknowledge paternity of the child and abide\n\nby all orders of the Massachusetts Probate and Family Court.\n\n In August 2012, after learning that Melendez sought to\n\nobtain parental visitation rights in the Probate and Family Court,\n\nTyler filed a motion with the criminal sentencing judge seeking\n\nreversal of the conditions of probation mentioned above. She\n\n\n\n 1\n See Rooker v. Fid. Tr. Co., 263 U.S. 413 (1923); D.C. Court\nof Appeals v. Feldman, 460 U.S. 462 (1983).\n 2 The record is unclear as to Melendez's exact age at the\ntime.\n\n\n - 2 -\n\fobjected to the conditions on the grounds that Melendez's\n\ncompliance with them would bind her to an unwanted sixteen-year\n\nlegal relationship with Melendez in the Probate and Family Court.\n\nShe requested that Melendez instead pay criminal restitution,\n\nrather than child support, to relieve her of the burden of\n\ncontinued engagement with him in family court. The sentencing\n\ncourt denied Tyler's request. Tyler also sought relief from a\n\nsingle justice of the Supreme Judicial Court of Massachusetts (SJC)\n\npursuant to Mass. Gen. Laws ch. 211, § 3. After the single justice\n\ndenied Tyler's motion, and Tyler appealed, the full SJC held oral\n\nargument on Tyler's claims. The SJC affirmed the decision of the\n\nsingle justice on the grounds that, as a victim of a criminal\n\noffense, Tyler lacked standing to challenge Melendez's criminal\n\nsentence. See H.T. v. Commonwealth, 989 N.E.2d 424, 425 (Mass.\n\n2013). The SJC also advised that Tyler could \"raise any claim of\n\nerror, including any claim that the [Probate and Family Court]\n\nexceeded its lawful authority, in the ordinary appellate process.\"\n\nId. at 426.\n\n Tyler then filed an action under the Federal Civil Rights\n\nAct, 42 U.S.C. § 1983, in the District Court of Massachusetts,\n\nseeking review of substantially the same grievances. In November\n\n2013, the district court dismissed the action as barred by the\n\nEleventh Amendment. Tyler v. Massachusetts, 981 F. Supp. 2d 92,\n\n\n\n\n - 3 -\n\f96 (D. Mass. 2013). The court also noted that the Burford3 and\n\nYounger4 abstention doctrines counseled against adjudicating\n\nTyler's claims. Id. at 96–97. Tyler did not appeal.\n\n In November 2013, Tyler filed a motion in the Probate\n\nand Family Court seeking either to vacate the court's jurisdiction\n\nor to terminate Melendez's parental rights. She contended that an\n\nadult convicted of statutory rape should have no parental rights\n\nwith respect to a child born as a result of that crime. After the\n\nfamily court denied her motion, Tyler sought review in the Appeals\n\nCourt of Massachusetts. The Appeals Court affirmed, holding that\n\n\"nothing in the language of [the family court statute, Mass. Gen.\n\nLaws ch. 209C,] expressly limits its applicability solely to\n\nchildren born as a result of lawful intercourse.\" H.T. v. J.M.,\n\nNo. 15–P–1042, 2016 WL 7046435, at *2 (Mass. App. Ct. Dec. 5,\n\n2016), appeal denied, 75 N.E.3d 1130 (Mass. 2017). The Appeals\n\nCourt also discussed a 2014 amendment to the Massachusetts family\n\ncourt statute,5 reasoning that since it was \"apparent from [the\n\n\n\n 3 See Burford v. Sun Oil Co., 319 U.S. 315 (1943).\n 4 See Younger v. Harris, 401 U.S. 37 (1971).\n 5\n In 2014, the Massachusetts legislature amended the family\ncourt statute to specify that the family court should grant\nvisitation rights to a parent convicted of statutory rape only if\n\"visitation is in the best interest of the child\" and \"either the\nother parent of the child conceived during the commission of that\nrape has reached the age of 18 and said parent consents to such\nvisitation or the judge makes an independent determination that\nvisitation is in the best interest of the child.\" 2014 Mass.\n\n\n - 4 -\n\famendment's] language that it was designed to limit, rather than\n\nto expand, the court's existing authority,\" the statute must have\n\npreviously authorized family courts to adjudicate the parental\n\nrights of a parent convicted of statutory rape. Id. Finally, the\n\nAppeals Court denied Tyler's plea to vacate jurisdiction as a\n\nmatter of public policy, noting that \"the mother's desired\n\ndisposition [would] require us to treat the father more favorably\n\nthan other biological fathers, [and] it also would unfairly\n\ndisadvantage the child by depriving her of the right to receive\n\nfinancial support from both parents.\" Id. at *3. In 2017, the\n\nSJC denied Tyler's application for further appellate review. See\n\nH.T. v. J.M., 75 N.E.3d 1130 (Mass. 2017).\n\n Rather than seeking a writ of certiorari from the United\n\nStates Supreme Court, Tyler filed this action in the District of\n\nMassachusetts, alleging that the \"recent ruling of the\n\nMassachusetts Supreme Judicial Court\" violated her Fourth and\n\nFourteenth Amendment rights to due process, privacy, and equal\n\nprotection. She sought relief declaring the 2017 SJC decision\n\nunconstitutional and \"prevent[ing] all courts in the Commonwealth\n\n[of Massachusetts] from asserting jurisdiction on behalf of\n\nconvicted rapists who impregnate their victims.\" The district\n\ncourt decided that it did not have jurisdiction over the claims:\n\n\nLegis. Serv. ch. 260 (West) (codified as amended at Mass. Gen.\nLaws. ch. 209C, § 3(a)).\n\n\n - 5 -\n\f\"The Rooker-Feldman doctrine prevents consideration because\n\n[Tyler] present[s] a dispute brought by an unsuccessful litigant\n\nin the state courts seeking to have a lower federal court review\n\nand reject a state court judgment rendered before the federal\n\nlitigation commenced.\" Tyler v. Supreme Judicial Court of Mass.,\n\n292 F. Supp. 3d 555, 556 (D. Mass. 2018) (footnote omitted). This\n\nappeal followed.\n\n II.\n\n Under the Rooker-Feldman doctrine, \"lower federal courts\n\nare precluded from exercising appellate jurisdiction over final\n\nstate-court judgments.\" Lance v. Dennis, 546 U.S. 459, 463 (2006).\n\nThe idea is that -- absent exceptions not present here -- the only\n\nfederal court with statutory jurisdiction to review a state court's\n\ndecision is the Supreme Court, and \"an aggrieved litigant cannot\n\nbe permitted to do indirectly what he no longer can do directly.\"\n\nRooker, 263 U.S. at 416. The Rooker-Feldman doctrine bars\n\njurisdiction \"only in the 'limited circumstances' where 'the\n\nlosing party in state court filed suit in federal court after the\n\nstate proceedings ended, complaining of an injury caused by the\n\nstate-court judgment and seeking review and rejection of that\n\njudgment.'\" Federación de Maestros de P.R. v. Junta de Relaciones\n\ndel Trabajo de P.R., 410 F.3d 17, 23–24 (1st Cir. 2005) (quoting\n\nExxon Mobil Corp. v. Saudi Basic Indus. Corp., 544 U.S. 280, 291\n\n(2005)).\n\n\n - 6 -\n\f The record makes plain that Tyler came to federal court\n\nseeking an end-run around the SJC's 2017 decision allowing the\n\nProbate and Family Court to adjudicate Melendez's parental rights.\n\nTyler's brief to this court concedes that her complaint \"asks the\n\nfederal court to reverse the state court judgment.\" And the\n\ncomplaint does indeed request that the district court \"[d]eclar[e]\n\nthe Supreme Judicial Court's decision unconstitutional.\" The\n\ncomplaint also repeatedly identifies the SJC's 2017 decision as\n\nthe exclusive cause of Tyler's injury. After discussing the state-\n\ncourt proceedings culminating with the denial of her application\n\nfor further appellate review \"by the Supreme Judicial Court on\n\nJanuary 26, 2017,\" Tyler details three counts all challenging that\n\ndecision. Count I alleges that the \"ruling threatens Plaintiff's\n\nrights by exposing Plaintiff to an unlawful restraint on her\n\nliberty and a seizure of her person\"; Count II alleges that the\n\n\"ruling threatens Plaintiff's liberty and privacy\"; and Count III\n\nalleges that the \"decision violates Plaintiff's equal protection\n\nrights.\" \"Where federal relief can only be predicated upon a\n\nconviction that the state court was wrong, it is difficult to\n\nconceive the federal proceeding as, in substance, anything other\n\nthan a prohibited appeal of the state-court judgment.\" Hill v.\n\nTown of Conway, 193 F.3d 33, 39 (1st Cir. 1999) (quoting Pennzoil\n\nCo. v. Texaco, Inc., 481 U.S. 1, 25 (1987) (Marshall, J.,\n\nconcurring)).\n\n\n - 7 -\n\f Tyler seeks haven from the application of this doctrine\n\nby arguing that, \"[a]lthough [she] raised the federal issues in\n\nevery state court proceeding, Rooker-Feldman poses no bar because\n\nnone of her federal claims was actually decided by any state\n\ncourt.\" The record contradicts this assertion; in ruling against\n\nTyler, the Massachusetts Appeals Court wrote that it did not\n\n\"overlook[]\" any of her contentions, but rather found \"nothing in\n\nthem that require[d] discussion.\" H.T. v. J.M., 2016 WL 7046435,\n\nat *3 n.10 (quoting Dep't of Revenue v. Ryan R., 816 N.E.2d 1020,\n\n1027 (Mass. App. Ct. 2004)). Moreover, the Rooker-Feldman\n\njurisdictional bar \"is not contingent upon an identity between the\n\nissues actually litigated in the prior state-court proceedings and\n\nthe issues proffered in the subsequent federal suit. Instead, the\n\ncritical datum is whether the plaintiff's federal suit is, in\n\neffect, an end-run around a final state-court judgment.\" Klimowicz\n\nv. Deutsche Bank Nat'l Tr. Co., 907 F.3d 61, 66 (1st Cir. 2018)\n\n(citation omitted).\n\n Tyler counters that we should read the state court's\n\nstatement that her contentions did not require discussion to mean\n\nthat the state court believed that it lacked standing to entertain\n\nher federal claims on the merits. Hence, she argues, the state\n\ncourt arrived at no final judgment susceptible to challenge or\n\n\"end-run.\" We cannot agree. As the Appeals Court's opinion itself\n\nnotes, the 2013 SJC opinion rejecting for lack of standing Tyler's\n\n\n - 8 -\n\fattempt to intervene in the criminal proceeding declared that Tyler\n\nwould have standing to assert her claims in an appeal from an order\n\nof the Family and Probate Court. See H.T. v. Commonwealth, 989\n\nN.E.2d at 426; H.T. v. J.M., 2016 WL 7046435, at *1 (\"The [SJC]\n\nexplained . . . that it remained open to the mother to raise any\n\nclaim of error in the ordinary appellate process from proceedings\n\nin the Probate and Family Court.\"). It would therefore make no\n\nsense to interpret the Appeals Court's opinion in the appeal\n\narising out of the Probate and Family Court proceedings as\n\nincorporating the SJC's standing analysis from the prior criminal\n\ncase, barring her from taking the precise action blessed by the\n\nSJC. Besides, Tyler has given us no reason to believe that her\n\nstanding was even contested in either the Appeals Court case or\n\nthe 2017 SJC appeal. We therefore read the Appeals Court's\n\nfootnote to mean that it reached Tyler's federal constitutional\n\nclaims and summarily rejected them on their merits. So, when the\n\nSJC declined to review the Appeals Court's decision, the state-\n\ncourt system ruled finally on Tyler's constitutional claims.\n\n This analysis also disposes of Tyler's alternative\n\nargument: that she is not seeking a reversal of the state-court\n\njudgment, but rather presenting an independent, \"general challenge\n\nto the constitutionality of state law.\" It is true that the\n\nRooker-Feldman doctrine does not bar a \"general attack on the\n\nconstitutionality\" of a state law that \"do[es] not require review\n\n\n - 9 -\n\fof a judicial decision in a particular case.\" Feldman, 460 U.S.\n\nat 487. \"'If a federal plaintiff \"presents an independent claim,\"'\n\nit is not an impediment to the exercise of federal jurisdiction\n\nthat the 'same or a related question' was earlier aired between\n\nthe parties in state court.\" Skinner v. Switzer, 562 U.S. 521,\n\n532 (2011) (alterations omitted) (quoting Exxon Mobil Corp., 544\n\nU.S. at 292–93). But that exception does not apply \"if the relief\n\nsought in federal court is directed towards undoing the prior state\n\njudgment.\" Maymó-Meléndez v. Álvarez-Ramírez, 364 F.3d 27, 34\n\n(1st Cir. 2004). As we have explained, the relief Tyler seeks is\n\nentirely predicated on her insistence that the SJC erred in the\n\n2017 adjudication of her case. Her attempt to reframe the case as\n\nan independent challenge to the Massachusetts law is therefore\n\n\"felled by [her] own complaint.\" McKenna v. Curtin, 869 F.3d 44,\n\n48 (1st Cir. 2017).\n\n Finally, Tyler argues that \"the state proceedings have\n\nnot ended with regard to the federal issues [she] seeks to have\n\nreviewed in federal court.\" See Exxon Mobil Corp., 544 U.S. at\n\n291 (holding that the Rooker-Feldman doctrine only applies when\n\nthe losing party in state court files suit in federal court \"after\n\nthe state proceedings ended\"). In connection with this argument,\n\nshe observes that her family court matters \"will remain pending\n\nfor at least another ten years.\" But she offers no suggestion\n\nthat the family court will ever reconsider the federal claims she\n\n\n - 10 -\n\fpresses here. See Federación de Maestros, 410 F.3d at 25\n\n(observing that state proceedings have ended for purposes of the\n\nRooker-Feldman doctrine when \"the state court proceedings have\n\nfinally resolved all the federal questions in the litigation, but\n\nstate law or purely factual questions . . . remain to be\n\nlitigated\").\n\n In sum, Tyler is a \"losing party in state court [who]\n\nfiled suit in federal court after the state proceedings ended,\n\ncomplaining of an injury caused by the state-court judgment and\n\nseeking review and rejection of that judgment.\" Federación de\n\nMaestros, 410 F.3d at 24 (quoting Exxon Mobil Corp., 544 U.S. at\n\n291). The district court therefore correctly held that it lacked\n\njurisdiction to hear Tyler's claims.\n\n III.\n\n For the foregoing reasons, we affirm the district\n\ncourt's dismissal for want of jurisdiction.\n\n\n\n\n - 11 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362556/", "author_raw": "KAYATTA, Circuit Judge"}]}
TORRUELLA
KAYATTA
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4585303/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Heather TYLER, Plaintiff, Appellant, v. SUPREME JUDICIAL COURT OF MASSACHUSETTS; Hon. Ralph D. Gants; Hon. Elspeth B. Cypher; Hon. Barbara A. Lenk; Hon. Scott L. Kafker; Hon. Frank M. Gaziano; Hon. David A. Lowy; Hon. Kimberly S. Budd; Maura Healey, Attorney General for the Commonwealth, in Her Official Capacity, Defendants, Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-28\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1256\n\n HEATHER TYLER,\n\n Plaintiff, Appellant,\n\n v.\n\n SUPREME JUDICIAL COURT OF MASSACHUSETTS; HON. RALPH D. GANTS;\n HON. ELSPETH B. CYPHER; HON. BARBARA A. LENK; HON. SCOTT L.\n KAFKER; HON. FRANK M. GAZIANO; HON. DAVID A. LOWY;\n HON. KIMBERLY S. BUDD; MAURA HEALEY, Attorney General for the\n Commonwealth, in her official capacity,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Douglas P. Woodlock, U.S. District Judge]\n\n\n Before\n\n Torruella, Kayatta, and Barron,\n Circuit Judges.\n\n\n Wendy Murphy for appellant.\n Todd M. Blume, Assistant Attorney General, Criminal Bureau,\nwith whom Maura Healy, Attorney General, was on brief, for\nappellee.\n\n\n January 28, 2019\n\f KAYATTA, Circuit Judge. This appeal arises from Heather\n\nTyler's six-year-long legal battle to void two Massachusetts\n\nSuperior Court conditions of probation imposed on the adult male\n\nwho was convicted of statutory rape after impregnating her when\n\nshe was a minor. The district court found that Tyler's suit was,\n\nin essence, an appeal from a state-court judgment, and that the\n\ndistrict court therefore lacked jurisdiction to hear it under the\n\nRooker-Feldman doctrine.1 For the following reasons, we agree.\n\n I.\n\n In 2009, at age nineteen or twenty, Jamie Melendez\n\nimpregnated fourteen-year-old Heather Tyler.2 Tyler gave birth in\n\n2010. Upon pleading guilty in state court to the statutory rape\n\nof Tyler, Melendez received a sentence of sixteen years of\n\nprobation. As conditions of probation, the sentencing judge\n\nordered Melendez to acknowledge paternity of the child and abide\n\nby all orders of the Massachusetts Probate and Family Court.\n\n In August 2012, after learning that Melendez sought to\n\nobtain parental visitation rights in the Probate and Family Court,\n\nTyler filed a motion with the criminal sentencing judge seeking\n\nreversal of the conditions of probation mentioned above. She\n\n\n\n 1\n See Rooker v. Fid. Tr. Co., 263 U.S. 413 (1923); D.C. Court\nof Appeals v. Feldman, 460 U.S. 462 (1983).\n 2 The record is unclear as to Melendez's exact age at the\ntime.\n\n\n - 2 -\n\fobjected to the conditions on the grounds that Melendez's\n\ncompliance with them would bind her to an unwanted sixteen-year\n\nlegal relationship with Melendez in the Probate and Family Court.\n\nShe requested that Melendez instead pay criminal restitution,\n\nrather than child support, to relieve her of the burden of\n\ncontinued engagement with him in family court. The sentencing\n\ncourt denied Tyler's request. Tyler also sought relief from a\n\nsingle justice of the Supreme Judicial Court of Massachusetts (SJC)\n\npursuant to Mass. Gen. Laws ch. 211, § 3. After the single justice\n\ndenied Tyler's motion, and Tyler appealed, the full SJC held oral\n\nargument on Tyler's claims. The SJC affirmed the decision of the\n\nsingle justice on the grounds that, as a victim of a criminal\n\noffense, Tyler lacked standing to challenge Melendez's criminal\n\nsentence. See H.T. v. Commonwealth, 989 N.E.2d 424, 425 (Mass.\n\n2013). The SJC also advised that Tyler could \"raise any claim of\n\nerror, including any claim that the [Probate and Family Court]\n\nexceeded its lawful authority, in the ordinary appellate process.\"\n\nId. at 426.\n\n Tyler then filed an action under the Federal Civil Rights\n\nAct, 42 U.S.C. § 1983, in the District Court of Massachusetts,\n\nseeking review of substantially the same grievances. In November\n\n2013, the district court dismissed the action as barred by the\n\nEleventh Amendment. Tyler v. Massachusetts, 981 F. Supp. 2d 92,\n\n\n\n\n - 3 -\n\f96 (D. Mass. 2013). The court also noted that the Burford3 and\n\nYounger4 abstention doctrines counseled against adjudicating\n\nTyler's claims. Id. at 96–97. Tyler did not appeal.\n\n In November 2013, Tyler filed a motion in the Probate\n\nand Family Court seeking either to vacate the court's jurisdiction\n\nor to terminate Melendez's parental rights. She contended that an\n\nadult convicted of statutory rape should have no parental rights\n\nwith respect to a child born as a result of that crime. After the\n\nfamily court denied her motion, Tyler sought review in the Appeals\n\nCourt of Massachusetts. The Appeals Court affirmed, holding that\n\n\"nothing in the language of [the family court statute, Mass. Gen.\n\nLaws ch. 209C,] expressly limits its applicability solely to\n\nchildren born as a result of lawful intercourse.\" H.T. v. J.M.,\n\nNo. 15–P–1042, 2016 WL 7046435, at *2 (Mass. App. Ct. Dec. 5,\n\n2016), appeal denied, 75 N.E.3d 1130 (Mass. 2017). The Appeals\n\nCourt also discussed a 2014 amendment to the Massachusetts family\n\ncourt statute,5 reasoning that since it was \"apparent from [the\n\n\n\n 3 See Burford v. Sun Oil Co., 319 U.S. 315 (1943).\n 4 See Younger v. Harris, 401 U.S. 37 (1971).\n 5\n In 2014, the Massachusetts legislature amended the family\ncourt statute to specify that the family court should grant\nvisitation rights to a parent convicted of statutory rape only if\n\"visitation is in the best interest of the child\" and \"either the\nother parent of the child conceived during the commission of that\nrape has reached the age of 18 and said parent consents to such\nvisitation or the judge makes an independent determination that\nvisitation is in the best interest of the child.\" 2014 Mass.\n\n\n - 4 -\n\famendment's] language that it was designed to limit, rather than\n\nto expand, the court's existing authority,\" the statute must have\n\npreviously authorized family courts to adjudicate the parental\n\nrights of a parent convicted of statutory rape. Id. Finally, the\n\nAppeals Court denied Tyler's plea to vacate jurisdiction as a\n\nmatter of public policy, noting that \"the mother's desired\n\ndisposition [would] require us to treat the father more favorably\n\nthan other biological fathers, [and] it also would unfairly\n\ndisadvantage the child by depriving her of the right to receive\n\nfinancial support from both parents.\" Id. at *3. In 2017, the\n\nSJC denied Tyler's application for further appellate review. See\n\nH.T. v. J.M., 75 N.E.3d 1130 (Mass. 2017).\n\n Rather than seeking a writ of certiorari from the United\n\nStates Supreme Court, Tyler filed this action in the District of\n\nMassachusetts, alleging that the \"recent ruling of the\n\nMassachusetts Supreme Judicial Court\" violated her Fourth and\n\nFourteenth Amendment rights to due process, privacy, and equal\n\nprotection. She sought relief declaring the 2017 SJC decision\n\nunconstitutional and \"prevent[ing] all courts in the Commonwealth\n\n[of Massachusetts] from asserting jurisdiction on behalf of\n\nconvicted rapists who impregnate their victims.\" The district\n\ncourt decided that it did not have jurisdiction over the claims:\n\n\nLegis. Serv. ch. 260 (West) (codified as amended at Mass. Gen.\nLaws. ch. 209C, § 3(a)).\n\n\n - 5 -\n\f\"The Rooker-Feldman doctrine prevents consideration because\n\n[Tyler] present[s] a dispute brought by an unsuccessful litigant\n\nin the state courts seeking to have a lower federal court review\n\nand reject a state court judgment rendered before the federal\n\nlitigation commenced.\" Tyler v. Supreme Judicial Court of Mass.,\n\n292 F. Supp. 3d 555, 556 (D. Mass. 2018) (footnote omitted). This\n\nappeal followed.\n\n II.\n\n Under the Rooker-Feldman doctrine, \"lower federal courts\n\nare precluded from exercising appellate jurisdiction over final\n\nstate-court judgments.\" Lance v. Dennis, 546 U.S. 459, 463 (2006).\n\nThe idea is that -- absent exceptions not present here -- the only\n\nfederal court with statutory jurisdiction to review a state court's\n\ndecision is the Supreme Court, and \"an aggrieved litigant cannot\n\nbe permitted to do indirectly what he no longer can do directly.\"\n\nRooker, 263 U.S. at 416. The Rooker-Feldman doctrine bars\n\njurisdiction \"only in the 'limited circumstances' where 'the\n\nlosing party in state court filed suit in federal court after the\n\nstate proceedings ended, complaining of an injury caused by the\n\nstate-court judgment and seeking review and rejection of that\n\njudgment.'\" Federación de Maestros de P.R. v. Junta de Relaciones\n\ndel Trabajo de P.R., 410 F.3d 17, 23–24 (1st Cir. 2005) (quoting\n\nExxon Mobil Corp. v. Saudi Basic Indus. Corp., 544 U.S. 280, 291\n\n(2005)).\n\n\n - 6 -\n\f The record makes plain that Tyler came to federal court\n\nseeking an end-run around the SJC's 2017 decision allowing the\n\nProbate and Family Court to adjudicate Melendez's parental rights.\n\nTyler's brief to this court concedes that her complaint \"asks the\n\nfederal court to reverse the state court judgment.\" And the\n\ncomplaint does indeed request that the district court \"[d]eclar[e]\n\nthe Supreme Judicial Court's decision unconstitutional.\" The\n\ncomplaint also repeatedly identifies the SJC's 2017 decision as\n\nthe exclusive cause of Tyler's injury. After discussing the state-\n\ncourt proceedings culminating with the denial of her application\n\nfor further appellate review \"by the Supreme Judicial Court on\n\nJanuary 26, 2017,\" Tyler details three counts all challenging that\n\ndecision. Count I alleges that the \"ruling threatens Plaintiff's\n\nrights by exposing Plaintiff to an unlawful restraint on her\n\nliberty and a seizure of her person\"; Count II alleges that the\n\n\"ruling threatens Plaintiff's liberty and privacy\"; and Count III\n\nalleges that the \"decision violates Plaintiff's equal protection\n\nrights.\" \"Where federal relief can only be predicated upon a\n\nconviction that the state court was wrong, it is difficult to\n\nconceive the federal proceeding as, in substance, anything other\n\nthan a prohibited appeal of the state-court judgment.\" Hill v.\n\nTown of Conway, 193 F.3d 33, 39 (1st Cir. 1999) (quoting Pennzoil\n\nCo. v. Texaco, Inc., 481 U.S. 1, 25 (1987) (Marshall, J.,\n\nconcurring)).\n\n\n - 7 -\n\f Tyler seeks haven from the application of this doctrine\n\nby arguing that, \"[a]lthough [she] raised the federal issues in\n\nevery state court proceeding, Rooker-Feldman poses no bar because\n\nnone of her federal claims was actually decided by any state\n\ncourt.\" The record contradicts this assertion; in ruling against\n\nTyler, the Massachusetts Appeals Court wrote that it did not\n\n\"overlook[]\" any of her contentions, but rather found \"nothing in\n\nthem that require[d] discussion.\" H.T. v. J.M., 2016 WL 7046435,\n\nat *3 n.10 (quoting Dep't of Revenue v. Ryan R., 816 N.E.2d 1020,\n\n1027 (Mass. App. Ct. 2004)). Moreover, the Rooker-Feldman\n\njurisdictional bar \"is not contingent upon an identity between the\n\nissues actually litigated in the prior state-court proceedings and\n\nthe issues proffered in the subsequent federal suit. Instead, the\n\ncritical datum is whether the plaintiff's federal suit is, in\n\neffect, an end-run around a final state-court judgment.\" Klimowicz\n\nv. Deutsche Bank Nat'l Tr. Co., 907 F.3d 61, 66 (1st Cir. 2018)\n\n(citation omitted).\n\n Tyler counters that we should read the state court's\n\nstatement that her contentions did not require discussion to mean\n\nthat the state court believed that it lacked standing to entertain\n\nher federal claims on the merits. Hence, she argues, the state\n\ncourt arrived at no final judgment susceptible to challenge or\n\n\"end-run.\" We cannot agree. As the Appeals Court's opinion itself\n\nnotes, the 2013 SJC opinion rejecting for lack of standing Tyler's\n\n\n - 8 -\n\fattempt to intervene in the criminal proceeding declared that Tyler\n\nwould have standing to assert her claims in an appeal from an order\n\nof the Family and Probate Court. See H.T. v. Commonwealth, 989\n\nN.E.2d at 426; H.T. v. J.M., 2016 WL 7046435, at *1 (\"The [SJC]\n\nexplained . . . that it remained open to the mother to raise any\n\nclaim of error in the ordinary appellate process from proceedings\n\nin the Probate and Family Court.\"). It would therefore make no\n\nsense to interpret the Appeals Court's opinion in the appeal\n\narising out of the Probate and Family Court proceedings as\n\nincorporating the SJC's standing analysis from the prior criminal\n\ncase, barring her from taking the precise action blessed by the\n\nSJC. Besides, Tyler has given us no reason to believe that her\n\nstanding was even contested in either the Appeals Court case or\n\nthe 2017 SJC appeal. We therefore read the Appeals Court's\n\nfootnote to mean that it reached Tyler's federal constitutional\n\nclaims and summarily rejected them on their merits. So, when the\n\nSJC declined to review the Appeals Court's decision, the state-\n\ncourt system ruled finally on Tyler's constitutional claims.\n\n This analysis also disposes of Tyler's alternative\n\nargument: that she is not seeking a reversal of the state-court\n\njudgment, but rather presenting an independent, \"general challenge\n\nto the constitutionality of state law.\" It is true that the\n\nRooker-Feldman doctrine does not bar a \"general attack on the\n\nconstitutionality\" of a state law that \"do[es] not require review\n\n\n - 9 -\n\fof a judicial decision in a particular case.\" Feldman, 460 U.S.\n\nat 487. \"'If a federal plaintiff \"presents an independent claim,\"'\n\nit is not an impediment to the exercise of federal jurisdiction\n\nthat the 'same or a related question' was earlier aired between\n\nthe parties in state court.\" Skinner v. Switzer, 562 U.S. 521,\n\n532 (2011) (alterations omitted) (quoting Exxon Mobil Corp., 544\n\nU.S. at 292–93). But that exception does not apply \"if the relief\n\nsought in federal court is directed towards undoing the prior state\n\njudgment.\" Maymó-Meléndez v. Álvarez-Ramírez, 364 F.3d 27, 34\n\n(1st Cir. 2004). As we have explained, the relief Tyler seeks is\n\nentirely predicated on her insistence that the SJC erred in the\n\n2017 adjudication of her case. Her attempt to reframe the case as\n\nan independent challenge to the Massachusetts law is therefore\n\n\"felled by [her] own complaint.\" McKenna v. Curtin, 869 F.3d 44,\n\n48 (1st Cir. 2017).\n\n Finally, Tyler argues that \"the state proceedings have\n\nnot ended with regard to the federal issues [she] seeks to have\n\nreviewed in federal court.\" See Exxon Mobil Corp., 544 U.S. at\n\n291 (holding that the Rooker-Feldman doctrine only applies when\n\nthe losing party in state court files suit in federal court \"after\n\nthe state proceedings ended\"). In connection with this argument,\n\nshe observes that her family court matters \"will remain pending\n\nfor at least another ten years.\" But she offers no suggestion\n\nthat the family court will ever reconsider the federal claims she\n\n\n - 10 -\n\fpresses here. See Federación de Maestros, 410 F.3d at 25\n\n(observing that state proceedings have ended for purposes of the\n\nRooker-Feldman doctrine when \"the state court proceedings have\n\nfinally resolved all the federal questions in the litigation, but\n\nstate law or purely factual questions . . . remain to be\n\nlitigated\").\n\n In sum, Tyler is a \"losing party in state court [who]\n\nfiled suit in federal court after the state proceedings ended,\n\ncomplaining of an injury caused by the state-court judgment and\n\nseeking review and rejection of that judgment.\" Federación de\n\nMaestros, 410 F.3d at 24 (quoting Exxon Mobil Corp., 544 U.S. at\n\n291). The district court therefore correctly held that it lacked\n\njurisdiction to hear Tyler's claims.\n\n III.\n\n For the foregoing reasons, we affirm the district\n\ncourt's dismissal for want of jurisdiction.\n\n\n\n\n - 11 -\n[END_CASE]", "role": "user" } ]
4,585,304
Tara J. ROY, Plaintiff, Appellant, v. CORRECT CARE SOLUTIONS, LLC; State of Maine Department of Corrections; Rodney Bouffard, Individually; Troy Ross, Individually, Defendants, Appellees.
Roy v. Correct Care Solutions, LLC
2019-01-28
18-1313P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Barron", "parties": "", "opinions": [{"author": "LYNCH, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1313\n\n TARA J. ROY,\n\n Plaintiff, Appellant,\n\n v.\n\n CORRECT CARE SOLUTIONS, LLC; STATE OF MAINE DEPARTMENT OF\n CORRECTIONS; RODNEY BOUFFARD, individually; TROY ROSS,\n individually,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MAINE\n\n [Hon. Jon D. Levy, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n John P. Gause, with whom Eastern Maine Law, LLC was on brief,\nfor appellant.\n Gail S. Coleman, with whom James L. Lee, Deputy General\nCounsel, Jennifer S. Goldstein, Associate General Counsel, and\nElizabeth E. Theran, Assistant General Counsel, were on brief, for\nthe Equal Opportunity Employment Commission, amicus curiae.\n Barbra L. Archer Hirsch on brief for Maine Human Rights\nCommission, amicus curiae.\n Melinda J. Caterine, with whom Littler Mendelson, P.C. was on\nbrief, for appellee Correct Care Solutions, LLC.\n Valerie A. Wright, Assistant Attorney General, with whom\nSusan P. Herman, Deputy Attorney General, and Janet T. Mills,\nAttorney General of Maine, were on brief, for appellees State of\n\fMaine Department of Corrections, Bouffard, and Ross.\n\n\n January 28, 2019\n\n\n\n\t\n\f LYNCH, Circuit Judge. This case raises important issues\n\nabout employer liability for a hostile work environment created by\n\nthird parties and about non-employer liability for employment-\n\nrelated discrimination under the Maine Human Rights Act (MHRA).\n\nWe articulate here the rules which govern these claims.\n\n Tara Roy, the plaintiff, worked as a nurse, employed by\n\nCorrect Care Solutions, LLC (CCS), at a Maine Department of\n\nCorrections (MDOC) prison. After MDOC revoked her prison security\n\nclearance and CCS terminated her employment in October 2014, Roy\n\nsued three sets of defendants: CCS, the MDOC, and two individuals,\n\nthe prison's warden and deputy warden. She alleged that\n\ndiscrimination and sexual harassment by the prison's corrections\n\nofficers made her work environment hostile and that she was\n\nretaliated against for complaints about the hostile work\n\nenvironment and for other whistleblowing.\n\n Specifically, Roy alleged that CCS violated Title VII\n\nand § 4572 of the MHRA by not responding adequately to her\n\ncomplaints about the hostile work environment and by retaliating\n\nagainst her in terminating her employment for protected\n\ncomplaints. Her claims against MDOC under § 4633 of the MHRA\n\nalleged that MDOC interfered with her MHRA-protected right to work\n\nfree from discrimination and that MDOC's revocation of her security\n\nclearance was unlawful retaliation. Finally, against Rodney\n\nBouffard, the warden, and Troy Ross, the deputy warden, Roy brought\n\n\n - 3 -\n\fclaims under 42 U.S.C. § 1983 for violations of the Equal\n\nProtection Clause and the First Amendment.\n\n The district court granted summary judgment to all\n\ndefendants on all claims. See Roy v. Correct Care Solutions, LLC,\n\n321 F. Supp. 3d. 155, 160 (D. Me. 2018). We reverse as to CCS and\n\nMDOC and affirm as to Bouffard and Ross.\n\n After an overview of the facts, we first explain that a\n\njury could find that Roy's work environment was discriminatorily\n\nhostile. Having established this, we proceed to examine liability\n\nfor each defendant. We reverse summary judgment for MDOC, first\n\ndeciding an unresolved question of Maine law about the scope of\n\n§ 4633 non-employer liability for workplace harassment and then\n\nfinding disputes of material fact. Next, in reversing summary\n\njudgment for CCS, we explain that an employer can be liable for a\n\nhostile work environment created by non-employees as long as the\n\nemployer knew of the harassment and failed to take reasonable steps\n\nto address it. A jury could find CCS liable for failing to protect\n\nRoy from the harassment, as well as for retaliation. Finally, we\n\naffirm summary judgment for the warden and deputy warden. Ross\n\nand Bouffard receive qualified immunity, as reasonable officials\n\ncould have believed on these facts that no equal protection or\n\nFirst Amendment violations occurred.\n\n\n\n\n - 4 -\n\f I.\n\n We present the facts in the light most favorable to Roy\n\nand draw all reasonable inferences in her favor, as we must at\n\nsummary judgment. Pippin v. Boulevard Motel Corp., 835 F.3d 180,\n\n181 (1st Cir. 2016).\n\n Under a contract with MDOC, CCS operates and staffs the\n\nmedical facility at the Maine State Prison (MSP) in Warren, Maine.\n\nIn August 2012, CCS hired Roy to work as a licensed practical nurse\n\nat the MSP, where the medical facility consists of an infirmary\n\nand a clinic. Roy worked in the clinic, and primarily interacted\n\nwith the prison's corrections officers when they brought inmates\n\nin for treatment. As a safety measure, two officers were also\n\nspecifically assigned to the medical facility, one to the clinic\n\nand one to the infirmary.\n\n In late 2012, Davis Snow, the officer assigned to the\n\nclinic, made sexual jokes and degrading comments about women to\n\nRoy and made physical contact with Roy on two occasions. Snow's\n\nremarks were \"constant[].\" He said, for example, \"don't worry,\n\nit's because you are blonde. You wouldn't understand,\" and, \"I\n\nwouldn't expect someone like you to understand how things are\n\ndone.\" Snow also once squeezed and twisted Roy's wrist until she\n\ndropped to her knees in pain. And he once bent her over a chair\n\nand spanked her.\n\n\n\n\n - 5 -\n\f Roy complained to her CCS supervisors and MDOC about\n\nSnow in early 2013. After MDOC investigated these complaints,\n\nSnow was reassigned, away from the medical facility.\n\n About a year later, in the spring of 2014, Roy began\n\nworking with Donny Turner, who was often the corrections officer\n\nassigned to the medical clinic. Turner, like Snow, \"constantly\"\n\nmade derogatory jokes and comments about women. He said, \"[W]hy\n\ndo we have females when . . . men do everything,\" and that a\n\nwoman's \"job is to be at home.\" Turner continued his remarks even\n\nafter Roy told him that his comments were not funny.\n\n On June 20, 2014, Roy filed an Incident Report about\n\nTurner's degrading comments. The report also complained that\n\nTurner's behavior created health and safety risks. Roy explained\n\nthat Turner sometimes ignored her, left her alone in exam rooms\n\nwith inmates, and did not respond to her requests to bring sick or\n\ninjured inmates to the clinic.\n\n CCS employees were instructed to fill out MDOC Incident\n\nReports to provide information about any disruptions in the work\n\nof the clinic involving corrections officers. CCS says that\n\nreports by its employees about MDOC officers were usually submitted\n\nto CCS supervisors Elisabeth Lamson, CCS's administrator at the\n\nprison, and Robin Cross-Snell, the prison's head nurse. CCS also\n\nsays that such reports were then referred to MDOC within a day or\n\n\n\n\n - 6 -\n\ftwo for investigation, but the record suggests that this was not\n\nalways done.\n\n Outside of this formal Incident Report process,\n\nBouffard, the warden, and Ross, the deputy warden for operations,\n\nhad frequent contact with Cross-Snell and Lamson. The CCS\n\nsupervisors attended the prison's daily operations briefings, and\n\nLamson routinely spoke informally with MDOC officials about\n\nconcerns related to the medical facility.\n\n Roy's report on Turner went to Lamson, and Lamson\n\nbelieves she may have spoken with Turner about the report. But\n\nshe did not bring the issue to his supervisors, and there is no\n\nevidence that it was ever referred to or investigated by MDOC.\n\n Turner's behavior around Roy escalated after Roy filed\n\nthe Incident Report about him. Turner often left Roy alone with\n\ninmates, was frequently absent from his post in the clinic, talked\n\ndown to Roy, and worked slowly or ignored Roy when she needed\n\nsomething. It is considered a security risk for an officer at the\n\nmedical facility to leave his post, particularly when inmates are\n\naround.\n\n Roy continued to complain about Turner to her\n\nsupervisors, in person and by email. For example, on July 23, 24,\n\nand 31, 2014, Roy emailed Lamson saying that Turner was absent\n\nfrom his post in the clinic for as long as twenty minutes while\n\ninmates were there. Lamson forwarded at least one of Roy's emails\n\n\n - 7 -\n\fabout Turner to MDOC, but there is no evidence that MDOC\n\ninvestigated or acted on these reports by Roy about Turner, or\n\nthat CCS ever followed up.\n\n In early August 2014, Roy emailed Lamson about an\n\nincident with Officer Ernest Parrow. When Roy reminded Parrow\n\nabout the proper procedure for bringing sick inmates to the clinic,\n\nParrow told Roy to \"stop being a bitch.\" He added that he now\n\nunderstood why people hated her. Later that month, on August 26,\n\nRoy sent an Incident Report to Cross-Snell stating that she had\n\ncalled Parrow to ask him to bring an inmate to the clinic to sign\n\na form and that Parrow had responded by again calling her a \"bitch\"\n\nand then hanging up on her.\n\n Along with this August 26 Incident Report, Roy provided\n\nto CCS several sexually explicit text messages that Parrow had\n\nsent her earlier that summer. Parrow, who had previously had a\n\nbrief romantic relationship with Roy, texted her, \"There is still\n\na thing or two I didn't get to do to ya,\" and \"if you want me to\n\nbend you over let me know.\" Roy responded, \"U have a\n\n[girlfriend]!!!\" to the first message and ignored the second. She\n\ntold Cross-Snell that Parrow was angry with her in part because\n\nshe had rejected his advances.\n\n Cross-Snell verified that Parrow had called Roy a\n\n\"bitch\" twice and wrote an Incident Report, which she sent to MODC;\n\nCCS also gave MDOC the text messages between Parrow and Roy. CCS's\n\n\n - 8 -\n\fregional vice president, John Newby, who supervised Roy's\n\nsupervisors, learned that Parrow had called Roy a \"bitch\" twice\n\nand, on August 28, spoke with Ross, the deputy warden, about it.\n\nRoss says he then investigated Parrow's behavior, in part by\n\nreviewing the explicit text messages. Because of the alleged\n\nname-calling, Ross talked to Parrow about workplace\n\nprofessionalism.\n\n The text messages from Parrow reviewed by CCS and MDOC\n\nalso showed an exchange between Parrow and Roy on July 16, 2014,\n\nin which Parrow said Roy was \"being a shit\" after Roy refused to\n\nshare with him medical information that he wanted about an inmate.\n\nRoy said that the information, an inmate's prescribed medications,\n\nwas confidential by statute and that Parrow was not authorized to\n\nreceive it.\n\n Parrow was not the only officer asking Roy for\n\nconfidential medical information. Throughout July and August\n\n2014, Roy complained to her supervisors that she and other medical\n\nstaff were getting frequent calls from corrections officers\n\nrequesting confidential information. She said that officers\n\nresponded to her refusals to share it by calling her names,\n\nyelling, hanging up on her, and threatening to file grievances\n\nagainst her. At least four times during the summer of 2014, she\n\nemailed her supervisors reporting specific incidents. Roy says\n\nnothing was done by CCS or MDOC.\n\n\n - 9 -\n\f Roy also says that by mid-August multiple corrections\n\nofficers showed daily hostility toward her. Several of these\n\nofficers, including Parrow, Snow, Paul Dever, and Paul Garrido,\n\nalso filed Incident Reports complaining about Roy. For example,\n\nSnow filed a report stating that Roy had yelled at him. To Roy,\n\nthe officers' hostility and the filed Incident Reports constituted\n\nretaliation against her for her complaints about Snow, Turner,\n\nParrow, and their requests for confidential medical information.\n\nAt her deposition, Roy said, \"[W]ith the officers, when one is\n\nupset with somebody, they all are.\"\n\n Lamson and Cross-Snell met with Roy on August 14 about\n\nthe reports filed about her. Roy told her supervisors that the\n\nreports were false or exaggerated. Lamson and Cross-Snell warned\n\nRoy that she \"could be moved to another department\" if her behavior\n\ndid not change. At that point in August, CCS obviously\n\ncontemplated that it could move Roy to a different job within CCS.\n\nWeeks later, CCS's position changed, as we describe below.\n\n On September 12, Garrido told Roy that Officer Curtiss\n\nDoyle had said to him that an inmate needed to get sick so that\n\nthe ensuing emergency medical call would \"get Tara off her fat\n\nlazy ass.\" Roy filed another Incident Report that day saying that\n\nshe viewed this comment as sexual harassment. MDOC investigated\n\nthe incident in late September, days before Roy's employment was\n\nterminated.\n\n\n - 10 -\n\f Also on September 12, Roy emailed the CCS human resources\n\nspecialist, copying Cross-Snell, Lamson, and their supervisor\n\nNewby, asking for a transfer to a different CCS facility \"d[ue] to\n\nthe fact that I currently feel that my work site is bo[]rd[er]ing\n\non a hostile work environment.\" The record shows no response to\n\nRoy's email, and Roy does not remember getting one.\n\n That same week, Officer William DeGuisto messaged Roy on\n\nFacebook to say, \"You['re] lucky [Officer Paul] Dever is out on\n\nadmin leave[.] He was trying hard to get you fired.\" When Roy\n\nasked for more information, DeGuisto told her that Dever \"fucking\n\ncomplained to everyone you were picking on Turner and trying to\n\nget him fired\" and that Dever \"wrote a few reports on you.\" When\n\nRoy said that Dever \"does [not] have ANY reason to write reports\n\non me,\" DeGuisto offered, \"He says you have fucked everyone in the\n\nprison.\"\n\n DeGuisto then asked in a Facebook message if he could\n\ncall Roy, but she replied she would \"rather not\" give him her phone\n\nnumber. A few days later, he asked again if he could call her,\n\nand added, \"Please try to smile at my window and not look at me\n\nlike I'm the enemy.\" Four days after that, DeGuisto messaged her:\n\n\"Another report written against you today!!! And you still act\n\nlike you mad at my window[.] See you, I UN FRIEND YOU Tired of\n\nattitude.\"\n\n\n\n\n - 11 -\n\f Roy filed an Incident Report about DeGuisto's Facebook\n\nmessages, attaching the exchange about Dever and the later requests\n\nto call her. Lamson passed the report to her supervisor, Newby,\n\nand planned to discuss the report with Bouffard, the warden.\n\nAlthough MDOC says that it reviewed the allegations, Bouffard and\n\nRoss explained at their depositions that they did not act on the\n\ncomplaint because the interaction occurred on Facebook. Even\n\nthough Roy and DeGuisto's messages were about what Roy, DeGuisto,\n\nand Dever had done, said, and heard in the workplace, in Ross's\n\nview, \"The Facebook stuff, that's off-duty stuff. We don't do\n\nmuch with that.\" Similarly, Bouffard called the conversation\n\n\"something that was going on in their own private lives.\"\n\n After Roy filed the Incident Report about DeGuisto,\n\nLamson spoke to Roy about all the Incident Reports she had filed.\n\nWhat happened at the meeting is disputed. As Roy remembers it,\n\nLamson told Roy that she should not write any more reports about\n\ncorrections officers because Ross was upset with Roy's frequent\n\ncomplaints. As Lamson remembers it, she told Roy \"that the\n\nreport[s Roy files] should be of substance.\"\n\n About two weeks later, on September 26, 2014, Roy and\n\nanother nurse, Vanessa Reed-Chapman, were working in the clinic\n\nwhen Officer King was the correctional officer assigned to the\n\nclinic and Officer Snodgrass was assigned to the infirmary.\n\n(Turner was usually the officer assigned to the clinic, rather\n\n\n - 12 -\n\fthan King, and Snodgrass's typical assignment was the front desk.)\n\nAt about 10:00 that morning, a member of the medical staff was\n\ncalled to a medical emergency elsewhere in the prison. Protocol\n\nrequired the officer assigned to the infirmary to accompany the\n\nmedical staff member, as the infirmary could be locked to secure\n\nthe inmates there. That day, however, King was asked to respond\n\nto the call instead of Snodgrass.\n\n After King left, Roy and Reed-Chapman, who were then\n\nalone with three inmates in the medical clinic, called Snodgrass\n\nthree times to come over from the infirmary. If the medical clinic\n\nofficer was away, the infirmary officer was supposed to secure the\n\ninfirmary and come to the clinic. Surveillance footage shows\n\nSnodgrass asleep at his desk and unresponsive to the nurses' calls.\n\nEventually, Snodgrass did come over.\n\n Lamson learned of this incident from both Roy and Reed-\n\nChapman and called MDOC's Captain Melquist, who came to the clinic\n\nto speak with the nurses. Roy and Reed-Chapman each told Melquist\n\nthat the officer on duty in the clinic, King, had responded to a\n\ncall, that King had left Roy and Reed-Chapman with prisoners and\n\nwithout a corrections officer, and that the infirmary officer on\n\nduty, Snodgrass, did not arrive to cover the clinic for fifteen\n\nminutes.\n\n Although Melquist told Roy and Reed-Chapman to file\n\nIncident Reports, Roy did not do so because of what Lamson had\n\n\n - 13 -\n\ftold her about Ross not wanting Roy to file more reports. Reed-\n\nChapman did file an Incident Report, writing that King left at\n\n\"Approx 10[:]00\" with \"3 inmates still present in clinic with NO\n\nSupervision By DOC.\" She continued, \"[O]fficer did eventually\n\ncome to clinic @ 10[:]15. Safety Risk.\"\n\n Surveillance footage shows a different officer,\n\nTherrien, in the clinic thirty seconds after King left. The video\n\ndoes not show Therrien assuming King's duties or his post.\n\nTherrien was there letting inmates in and out of the clinic. The\n\nvideo also shows Snodgrass arriving about six minutes after King\n\nleft. Either Therrien or Snodgrass is on camera in the clinic for\n\nall but one minute and forty-nine seconds of the fifteen minutes\n\nafter King left. (MDOC says that Therrien never left the clinic,\n\nand only occasionally left the view of the camera.)\n\n That same afternoon, Lamson and Cross-Snell met with\n\nCaptain Melquist, Ross, and the MDOC human resources\n\nrepresentative. At the meeting, the captain expressed concern\n\nabout the discrepancies between the surveillance video and Roy and\n\nReed-Chapman's statements about being unattended for approximately\n\nfifteen minutes. Ross then said that he was frustrated that Roy\n\nwas involved in so many investigations, adding that he wanted to\n\n\"gate-close\" Roy -- that is, to revoke Roy's security clearance.\n\nRoss later said that he wanted to do this in part because of \"any\n\n[reports] that she may have been involved in.\"\n\n\n - 14 -\n\f The CCS Team Member Manual provides that employees like\n\nRoy are expected to maintain prison security clearances. At the\n\nMSP, clearances were controlled by MDOC, and Bouffard was the\n\nultimate decisionmaker.\n\n Although CCS was aware after the meeting that Roy's\n\nsecurity clearance was in limbo, there is no evidence that CCS had\n\nany discussions with MDOC about Roy after September 26. CCS did\n\nplace Roy on \"temporary suspended leave\" that day. Newby, the\n\nregional vice president, told Roy that he knew she had done nothing\n\nwrong and that the leave was merely a cooling off period. The\n\nleave was not temporary.\n\n A week later, on October 2, 2014, Bouffard emailed Newby\n\nstating, \"Effective immediately as a result of misconduct nurse\n\nTara Roy will no longer be allowed entrance to the facility.\n\nSpecifically, she misrepresented the truth and subsequently failed\n\nto follow a directive.\" Bouffard made this decision without\n\nspeaking to Roy or Reed-Chapman about the September 26 incident.\n\nIndeed, aside from the captain, who spoke to Roy and Reed-Chapman\n\non September 26, no one at MDOC inquired of them about their\n\nversion of events.\n\n MDOC did not revoke Reed-Chapman's security clearance,\n\nalthough she had made the same representations, or\n\n\"misrepresent[ations],\" as Roy. At deposition, Bouffard explained\n\nthat he chose not to revoke Reed-Chapman's clearance because she\n\n\n - 15 -\n\fwas a new employee who \"took direction\" from Roy. At the time,\n\nCCS did not ask MDOC to explain the discrepancy, nor did CCS\n\ndiscipline Reed-Chapman.\n\n CCS terminated Roy's employment the day MDOC revoked her\n\nclearance. Lamson told Roy that she could no longer work at the\n\nMSP because of the loss of her clearance and that CCS had no\n\nopenings at other facilities. CCS's two other sites in\n\nMaine -- the Androscoggin County Jail and the Two Bridges\n\nJail -- were not MDOC facilities and had security clearance systems\n\nseparate from the MSP's. Later, Lamson admitted that she had not\n\nlooked into and did not actually know on October 2 whether CCS had\n\nopenings at these facilities.\n\n II.\n\n We start with Roy's allegations that she was subjected\n\nto a hostile work environment in violation of Title VII, the MHRA,\n\nand the Equal Protection Clause. This allegation is an essential\n\ningredient of Roy's sexual harassment claims against all\n\ndefendants. We conclude that a reasonable jury could find that\n\nRoy's work environment was hostile, and we turn in later sections\n\nto the liability of each defendant.\n\n A hostile work environment is one \"permeated with\n\ndiscriminatory intimidation, ridicule, and insult, that is\n\nsufficiently severe or pervasive to alter the conditions of the\n\nvictim's employment.\" Harris v. Forklift Sys. Inc., 510 U.S. 17,\n\n\n - 16 -\n\f21 (1993) (internal quotations and citations omitted). To succeed\n\non a hostile work environment claim under Title VII, a plaintiff\n\nmust establish six elements:\n\n (1) that she (or he) is a member of a protected\n class; (2) that she was subjected to unwelcome\n sexual harassment; (3) that the harassment was\n based upon sex; (4) that the harassment was\n sufficiently severe or pervasive so as to\n alter the conditions of plaintiff's employment\n and create an abusive work environment;\n (5) that sexually objectionable conduct was\n both objectively and subjectively offensive,\n such that a reasonable person would find it\n hostile or abusive and the victim in fact did\n perceive it to be so; and (6) that some basis\n for employer liability has been established.\n\nO'Rourke v. City of Providence, 235 F.3d 713, 728 (1st Cir. 2001)\n\n(citing Faragher v. City of Boca Raton, 524 U.S. 775, 787-89\n\n(1998)). A hostile work environment claim under the MHRA is\n\n\"concurrent with Title VII.\" Watt v. UniFirst Corp., 969 A.2d\n\n897, 903 (Me. 2009). At issue now are whether the harassment was\n\nbased upon sex and whether it was sufficiently severe or pervasive.\n\nLater, we discuss the bases for liability.1\n\n\n\n\n 1 The other elements are not genuinely contested. CCS\ndoes offer a one-paragraph argument on appeal that Roy was not\nsubjectively offended. This argument is not well developed, and\nis waived. United States v. Zannino, 895 F.2d 1, 17 (1st Cir.\n1990). Nor is the argument convincing. Roy repeatedly asked the\ncorrections officers to stop their behavior and made formal\ncomplaints to her supervisors and MDOC, including a request to be\ntransferred.\n\n\n\n - 17 -\n\f The district court concluded that a hostile work\n\nenvironment did not exist.2 In ruling that much of the conduct\n\nRoy alleged was not based upon her sex and that the harassment she\n\nexperienced was not sufficiently severe or pervasive, the district\n\ncourt applied an erroneous legal standard and also erroneously\n\nresolved material disputes of fact. See Roy, 321 F. Supp. 3d at\n\n166-68.\n\n Roy must show that a jury could find the harassment she\n\nexperienced \"was based in part on her\" sex. Franchina v. City of\n\nProvidence, 881 F.3d 32, 54 (1st Cir. 2018). The district court\n\nerred when it suggested that Roy's sex must be the but-for cause\n\nor even the sole cause of each alleged harassing incident. Roy,\n\n321 F. Supp. 3d at 167. The Supreme Court has squarely rejected\n\nthese standards for hostile work environment claims. See Univ.\n\nof Texas Sw. Med. Ctr. v. Nassar, 570 U.S. 338, 343 (2013) (\"It\n\nsuffices . . . to show [on a hostile work environment claim] that\n\nthe motive to discriminate was one of the employer's\n\n\n\n 2 Roy has also appealed the district court's determination\nthat the allegations about Snow were untimely. \"This is a question\nthat need not be resolved here, as\" none of Roy's Title VII or\nMHRA claims \"turn[] on it.\" Maher v. Mass. Gen. Hosp. Long Term\nDisability Plan, 665 F.3d 289, 301 (1st Cir. 2011).\n Even so, the allegations against Snow may be considered\nas \"relevant background evidence to show that discriminatory\nanimus motivated the acts that occurred within\" the statutory time\nwindows. Malone v. Lockheed Martin Corp., 610 F.3d 16, 22 (1st\nCir. 2010) (citing Rathbun v. Autozone, Inc., 361 F.3d 62, 76 (1st\nCir. 2004)).\n\n\n - 18 -\n\fmotives . . . .\"); Price Waterhouse v. Hopkins, 490 U.S. 228, 240\n\n(1989) (plurality opinion) (\"To construe the words 'because of' as\n\ncolloquial shorthand for 'but-for causation' . . . is to\n\nmisunderstand them.\").3\n\n Much of the abuse Roy experienced was undoubtedly based\n\non her sex: Turner made constant derogatory comments about women;\n\nDeGuisto pestered her for her phone number in Facebook messages\n\nand conveyed that Dever was spreading rumors that she had \"fucked\"\n\neveryone in the prison;4 and Parrow sent her graphically sexual\n\ntext messages. The district court erred in disregarding three\n\nother allegations that it viewed as insufficiently \"connected to\n\nRoy's sex.\" Roy, 321 F. Supp. 3d at 167.\n\n\n 3 The Maine case cited by the district court is not to the\ncontrary. See Roy, 321 F. Supp. 3d at 167 (citing Bowen v. Dep't\nof Human Servs., 606 A.2d 1051, 1053-54 (Me. 1992)). That case\nsaid that but-for causation \"would be sufficient\" under the MHRA,\nnot that proof of but-for causation was necessary. Bowen, 606\nA.2d at 1053 (emphasis added).\n 4 CCS argues in a footnote that DeGuisto's Facebook\nmessages should be disregarded because they occurred outside of\nwork. But, as we have said before, \"Courts . . . permit evidence\nof non-workplace conduct to help determine the severity and\npervasiveness of the hostility in the workplace as well as to\nestablish that the conduct was motivated by gender.\" Crowley v.\nL.L. Bean, Inc., 303 F.3d 387, 409 (1st Cir. 2002). Furthermore,\nit is not clear at all that Facebook messages should be considered\nnon-workplace conduct where, as here, they were about workplace\nconduct, including Dever's reports and rumors, and were sent over\nsocial media by an officer who worked in Roy's workplace. Cf.\nFeminist Majority Found. v. Hurley, 911 F.3d 674, 688-89 (4th Cir.\n2018) (\"[W]e cannot conclude that [a university] could turn a blind\neye to the sexual harassment that pervaded and disrupted its campus\nsolely because the offending conduct took place through\ncyberspace.\").\n\n\n - 19 -\n\f First, there is no doubt that a jury could find that\n\nParrow calling Roy a \"bitch\" was connected to her sex. It does\n\nnot matter whether Parrow was motivated by \"anger resulting from\n\nthe breakup of their previous romantic relationship,\" as the\n\ndistrict court emphasized. Id. at 168. To distinguish between\n\nharassment motivated by sex and harassment motivated by anger after\n\na break up, as the district court did, \"establishes a false\n\ndichotomy\" between Roy's sex and Parrow's romantic interest in\n\nher, which are \"inextricably linked.\" Forrest v. Brinker Int'l.\n\nPayroll Co., 511 F.3d 225, 229 (1st Cir. 2007). Regardless of\n\nParrow's particular and subjective motives, \"the use of sexually\n\ndegrading, gender-specific epithets, such as . . . 'bitch,' . . .\n\nconstitute[s] harassment based upon sex.\" Id.\n\n Second, a reasonable jury could infer that the comment\n\nabout Roy's \"ass\" was made in part because of her sex, given the\n\ncontext. See, e.g., Tang v. Citizens Bank, N.A., 821 F.3d 206,\n\n216 (1st Cir. 2016) (considering context, use of word \"ass\" was\n\nbased on sex); McGullam v. Cedar Graphics, Inc., 609 F.3d 70, 85\n\n(2d Cir. 2010) (Calabresi, J., concurring) (viewing comment by\n\nmale co-worker about plaintiff's \"big fat ass\" to be based on sex).\n\nThat context includes Turner, Parrow, and Dever sexualizing Roy\n\nand officers like Snow emphasizing aspects of her appearance, such\n\nas her blonde hair.\n\n\n\n\n - 20 -\n\f Third, it was error for the district court to hold at\n\nsummary judgment that Roy's allegations of retaliatory conduct\n\nwere not sex-based. A jury could find on one of several theories\n\nthat officers put Roy at risk, treated her rudely, ignored her,\n\ndemeaned her, and filed reports complaining about her not only\n\nbecause of her whistleblowing but also because of her sex.\n\n A jury could see this degrading treatment as a form of\n\nsex-based discrimination. Responding disrespectfully or\n\ndismissively to women's requests, complaining about women's\n\nperformance, and ignoring or ostracizing women are paradigmatic\n\nways to communicate to women that they are less worthy than or\n\nless welcome than men in a workplace. See O’Rourke, 235 F.3d at\n\n730. Indeed, several of the remarks showed this sort of\n\nstereotyping (e.g., a woman's \"job is to be at home\"). A jury\n\ncould also find that the retaliation was motivated in part by sex\n\nbecause it was committed alongside overtly sexual harassment. See\n\nMarrero v. Goya of P.R., Inc., 304 F.3d 7, 20 (1st Cir. 2002)\n\n(considering sex-neutral conduct by a supervisor with his\n\nexplicitly sexual conduct); Rosario v. Dep't of Army, 607 F.3d\n\n241, 248 (1st Cir. 2010) (similar); Kaytor v. Elec. Boat Corp.,\n\n609 F.3d 537, 548 (2d Cir. 2010) (justifying this inference). Roy\n\nalleges that Turner, Dever, Snow, and Parrow, retaliated against\n\nher after her whistleblowing while also directing at her blatantly\n\nsexual comments, rumors, jokes, and epithets. As the Equal\n\n\n - 21 -\n\fOpportunity Employment Commission (EEOC), amicus here, urging\n\nreversal, says, \"it is impossible to tease out\" as a matter of law\n\n\"how much of the officers' conduct was based solely on Roy's\n\nwhistleblowing and how much was also infected with sex\n\ndiscrimination.\" This is an issue for the jury.\n\n Severity and pervasiveness were also issues for the\n\njury, and the district court erred in deciding as a matter of law\n\nthat the conduct was neither severe nor pervasive. Roy, 321 F.\n\nSupp. 3d at 168. A plaintiff need only show that her work\n\nenvironment was severe or that it was pervasive, Burns v. Johnson,\n\n829 F.3d 1, 18 (1st Cir. 2016), and a jury could find for Roy on\n\neither theory, or on both.\n\n On severity, a jury could find Turner's practice of\n\nabandoning his post so that Roy was left alone with inmates severe\n\nenough, on its own, to alter the terms and conditions of her\n\nemployment. Turner was assigned to the medical clinic to protect\n\nRoy and the other medical staff from inmates who were considered\n\ndangerous, and his absences placed Roy at risk of serious physical\n\nharm. Conduct that places a plaintiff in this sort of peril is\n\nsevere for purposes of a hostile work environment claim. See\n\nPatton v. Keystone RV Co., 455 F.3d 812, 818 (7th Cir. 2006)\n\n(holding that conduct that places the plaintiff in reasonable fear\n\nof serious physical harm suffices to show constructive discharge\n\nunder Title VII, a more difficult showing than severity); see also,\n\n\n - 22 -\n\fe.g., Gerald v. Univ. of P.R., 707 F.3d 7, 18 (1st Cir. 2013)\n\n(finding physically threatening behavior severe); Harris, 510 U.S.\n\nat 23 (including physically threatening behavior among indicators\n\nof a hostile work environment).\n\n On pervasiveness, there is evidence that Roy was\n\nsubjected to Turner's persistent derision and to several officers'\n\n\"daily\" retaliatory treatment, escalating from July to September\n\nof 2014. This environment was punctuated with the potentially\n\nhumiliating episodes involving Dever and Parrow. A jury could\n\nreasonably view this as frequent abuse and as a pattern of\n\nhostility, rather than as intermittent, isolated harassment. See,\n\ne.g., Tang, 821 F.3d at 217 (finding four incidents plus the\n\nplaintiff's allegation that the harassment occurred \"[e]very time\"\n\nthe harasser \"had a chance\" could be pervasive); Flood v. Bank of\n\nAm. Corp., 780 F.3d 1, 13 (1st Cir. 2015) (describing treatment by\n\nmultiple co-workers as a pattern of abuse); Hernandez-Loring v.\n\nUniversidad Metropolitana, 233 F.3d 49, 55 (1st Cir. 2000)\n\n(reversing entry of summary judgment on hostile work environment\n\nclaim based on two incidents and allegation that plaintiff was\n\n\"repeatedly asked [on] dates\").\n\n Finally, there is other evidence supporting Roy's claim\n\nof a hostile work environment. That officers complained about Roy\n\nand that she requested a transfer in mid-September could permit a\n\njury to find that the harassment was \"detract[ing] from [Roy's]\n\n\n - 23 -\n\fjob performance\" and \"discourag[ing] [her] from remaining on the\n\njob,\" both telltale signs of a \"discriminatorily abusive\"\n\nenvironment. Harris, 510 U.S. at 22.\n\n III.\n\n A jury could find that Roy endured a hostile work\n\nenvironment, so we proceed to evaluate the liability of each\n\ndefendant. We begin with the claims against MDOC, turn next to\n\nCCS, and finally to Ross and Bouffard.\n\nA. Claims against MDOC under Maine Law\n\n Roy alleges first that MDOC interfered with her MHRA-\n\nprotected right to work free from sex discrimination in violation\n\nof MHRA § 4633(2). Second, she alleges that MDOC's revocation of\n\nher security clearance was an act of retaliation, unlawful under\n\n§ 4633(1), for her MHRA-protected complaints about sexual\n\nharassment, about officers requesting inmate medical information\n\nmade confidential by statute, about officers ignoring her requests\n\nto bring inmates to the clinic, about officers leaving her alone\n\nwith potentially dangerous inmates, and about retaliation because\n\nof her reporting activity.5\n\n We address first whether § 4633 of the MHRA allows suits\n\nagainst non-employer third parties for discrimination that occurs\n\n\n\n 5 The MHRA makes it unlawful to discriminate in any \"matter\ndirectly or indirectly related to employment\" based on sex or on\ncertain whistleblower activity. Me. Rev. Stat. tit. 5,\n§ 4572(1)(A). Protected whistleblower activity is defined in the\n\n\n - 24 -\n\fin a workplace.6 The district court concluded, relying on the\n\nMaine Law Court's decision in Fuhrmann v. Staples Office Superstore\n\nEast, Inc., 58 A.3d 1083 (Me. 2012), that the MHRA allows\n\nemployment discrimination actions against employers only, and\n\nnever against \"non-employer entit[ies]\" like MDOC. Roy, 321 F.\n\nSupp. 3d at 164. We disagree and hold, based on the text and\n\nhistory of § 4633, that the provision allows Roy's claims.7\n\n 1. Section 4633\n\n The text of § 4633 encompasses both of Roy's claims\n\nagainst MDOC. Section 4633 reads:\n\n (1) Retaliation. A person may not\n discriminate against any individual because\n that individual has opposed any act or\n practice that is unlawful under this\n Act . . . .\n (2) Interference, coercion, or intimidation.\n It is unlawful for a person to coerce,\n intimidate, threaten or interfere with any\n individual in the exercise or enjoyment of the\n\n\n\nWhistleblower Protection Act (MWPA), which does not provide a cause\nof action separate from the MHRA's. See Me. Human Rights Comm'n\nv. Me. Dep't of Def. & Veterans' Servs., 627 A.2d 1005, 1007 n.8\n(Me. 1993).\n 6 At a hearing on the motions for summary judgment, the\ndistrict court asked the parties whether this question should be\ncertified to the Maine Law Court. See Transcript of Oral Argument\nat 51-54, Roy, 321 F. Supp. 3d 155 (No. 16-cv-00383). Roy's\ncounsel supported certification while MDOC did not, and the\ndistrict court ultimately decided not to certify the question. In\ntheir briefs on appeal, neither party has asked us to do so.\n 7 We do not have before us a claim against an individual\nsupervisor employed by the plaintiff's employer and take no\nposition on whether § 4633 would allow such a claim.\n\n\n - 25 -\n\f rights granted or protected by this\n Act . . . .\n\nMe. Rev. Stat. Ann. tit. 5, § 4633(1)-(2). This language\n\nprohibits any \"person\" 8 from hindering -- by \"[i]nterference,\n\ncoercion, or intimidation\" or by \"[r]etaliation\" -- the exercise\n\nof any \"rights granted or protected\" by the MHRA. Me. Rev. Stat.\n\nAnn. tit. 5, § 4633.\n\n The legislative history of § 4633 also supports our\n\nreading. The Maine legislature's summary of § 4633 at its\n\nenactment states that the provision \"makes clear that retaliation,\n\ninterference, coercion and intimidation . . . by any person\n\nbecause that individual engaged in activities related to rights\n\nprotected by the [MHRA] is a violation of the Act.\" Me. Pub. L.\n\n1993, ch. 303 § 3, Summary.\n\n Further, Maine's Human Rights Commission (MHRC), the\n\nagency that administers the MHRA, has long interpreted § 4633 to\n\nallow claims like Roy's against third parties whose actions impair\n\nworkers' MHRA-protected rights to be free from workplace\n\ndiscrimination. Indeed, in Maine Human Rights Comm'n v.\n\nSaddleback, Inc., No. CV-06-219, 2008 WL 6875449 (Me. Super. Ct.\n\nOct. 31, 2008), the Maine Superior Court agreed with the MHRC that\n\nSaddleback, a ski resort, violated § 4633 in demanding that a\n\n\n 8 MDOC is a \"person\" under the MHRA. See Me. Rev. Stat.\nAnn. tit. 5, § 4553(7) (defining \"person\" to \"include[] the State\nand all agencies thereof\").\n\n\n - 26 -\n\fconstruction contractor fire one of its employees because the\n\nemployee had reported safety violations at a Saddleback work site.\n\n As Saddleback makes clear, there is a key distinction\n\nbetween § 4633 and § 4572, the MHRA provision that prohibits\n\nunlawful employment discrimination. Section 4572 addresses\n\ndiscriminatory conduct by an employer, or employees or agents of\n\nthe employer, that occurs within the scope of a traditional\n\nemployment relationship. Section 4633 targets actions by third\n\nparties (not the employer, its employees, or agents) that hinder\n\nemployees' MHRA-protected rights to work free from discrimination.\n\n MDOC argues and the district court agreed that the Law\n\nCourt's decision in Fuhrmann precludes this reading of § 4633.\n\nNot so. In Fuhrmann, a Staples salesperson had her longstanding\n\nwork hours changed after she reported possible tax fraud at her\n\nstore. 58 A.3d at 1088. She sued Staples and her individual\n\nsupervisors, alleging retaliation under § 4572 of the MHRA for\n\nwhistleblower activity defined in § 833(1)(A) of the Maine\n\nWhistleblower Protection Act (MWPA). Id. at 1088-89. The Law\n\nCourt dismissed the claims against the individual supervisors,\n\nholding that \"[p]ursuant to either [the MHRA's or the MWPA's]\n\nstatutory definition of 'employer,' there is no individual\n\nsupervisor liability for employment discrimination.\" Id. at 1098.\n\n Fuhrmann does not control here. The issue before the\n\nLaw Court there was individual supervisor liability for a claim\n\n\n - 27 -\n\funder § 4572, and neither Fuhrmann's holding nor its reasoning\n\ntranslate to cases like this one involving third-party liability\n\nunder § 4633. Fuhrmann never mentioned § 4633, and several\n\nsignificant differences between § 4572 and § 4633 undercut MDOC's\n\nargument that Fuhrmann's holding extends to bar Roy's claims.\n\nFirst, § 4572 prohibits discrimination by an \"employer,\" and what\n\nFuhrmann interpreted was the MHRA's definition of that term. 58\n\nA.3d at 1094. In contrast, § 4633 prohibits discrimination by any\n\n\"person.\" Second, § 4633 appears in the miscellaneous section of\n\nthe MHRA, while Fuhrmann interpreted provisions in the MHRA's\n\nemployment discrimination section. Third, the provisions have\n\ndifferent histories, and the enactment of § 4633 more than twenty\n\nyears after § 4572 is a strong indication that the provisions have\n\ndifferent intents.\n\n Nevertheless, the district court reasoned that allowing\n\nRoy's § 4633 suit \"contradicts Fuhrmann's central\n\nrationale -- that the MHRA intends to hold employers liable for\n\nemployment discrimination.\" Roy, 321 F. Supp. 3d at 163. But\n\nFuhrmann assessed only whether the legislature intended to allow\n\nsuits against individual supervisors, not what it intended about\n\nsuits against non-employer third parties. To the Fuhrmann court,\n\nthe MHRA's incorporation of vicarious liability indicated a\n\nlegislative intent to hold employers, but not supervisors as\n\nindividuals, liable for supervisors' discriminatory conduct.\n\n\n - 28 -\n\fFuhrmann, 58 A.3d at 1097; see also Me. Rev. Stat. Ann. tit. 5,\n\n§ 4553(10)(E) (discussing vicarious liability). But vicarious\n\nliability is not relevant to claims like Roy's against third\n\nparties not alleged to be agents of the employer. Similarly,\n\nFuhrmann concluded that the remedies listed in the remedial\n\nprovision that applies to both § 4572 and § 4633 violations were\n\ndifficult to apply \"to individual supervisors in practice.\" 58\n\nA.3d at 1098. Fuhrmann said nothing about the application of the\n\nlisted remedies to third-party entities and did not explore the\n\nremedial provision's prefatory statement that \"remedies may\n\ninclude, but are not limited to\" those listed. Me. Rev. Stat.\n\nAnn. tit. 5, § 4613(2)(B). The district court erred in holding\n\nthat Fuhrmann bars Roy's claims against MDOC.\n\n 2. MDOC's Alternative Argument for Summary Judgment\n\n MDOC also argues that Roy has not offered evidence\n\nsufficient to push her § 4633 interference and retaliation claims\n\npast summary judgment. MDOC is plainly wrong.\n\n First, on the § 4633(2) interference claim, MDOC\n\ncontends only that we may affirm the grant of summary judgment\n\nbecause there was no hostile work environment. But, as explained,\n\na reasonable jury could conclude that Roy was subjected to a\n\nhostile work environment because of her sex in violation of the\n\nMHRA's protections against \"unlawful employment discrimination.\"\n\nSee Me. Rev. Stat. Ann. tit. 5, § 4572(1)(A).\n\n\n - 29 -\n\f Second, because we reject MDOC's arguments that Roy's\n\nconduct was not protected activity under the MHRA and the MWPA and\n\nthat it had non-pretextual reasons for revoking her security\n\nclearance, Roy's retaliation claim may go to the jury. MDOC says\n\nthat the facts show that Roy did not engage in protected activity.\n\nBut, with respect to Roy's complaints about the hostile work\n\nenvironment, MDOC appears to contend only that the reports are not\n\nprotected because the evidence did not suffice to show that the\n\nwork environment was hostile on the basis of sex. That contention\n\nis mistaken. Similarly, as we will explain with respect to CCS's\n\nliability under the MWPA, the arguments advanced by CCS and, by\n\nreference, MDOC, do not preclude Roy's other complaints from being\n\nfound to be protected whistleblower activity because they relate\n\nto potential violations of medical privacy laws, as well as to\n\nhealth and safety risks at the prison. See id. § 4572(1) (making\n\nunlawful discrimination based on whistleblower activity); Me. Rev.\n\nStat. Ann. tit. 26, § 833(1)(A)-(B) (defining protected\n\nwhistleblower activity as reporting \"a violation of a [state or\n\nfederal] law or rule\" or \"a condition or practice that would put\n\nat risk the health or safety of . . . [an] individual.\").\n\n MDOC next argues that Roy cannot show that MDOC's stated\n\nreasons for revoking the security clearance -- Roy's statements\n\nabout and her failure to file a report on the September 26\n\nincident -- were pretext for retaliation. But, based on numerous\n\n\n - 30 -\n\ffacts, of which we mention only a few, a jury could conclude that\n\nthose reasons were pretext. A jury could credit Ross's statements\n\nthat he was frustrated about Roy's involvement in so many\n\ninvestigations and that he wanted to \"gate-close\" Roy. And, even\n\nif the jury were to credit MDOC's stated reasons over Ross's\n\nstatements, a jury could find that Roy's actions did not jeopardize\n\nthe security of the prison and could not justify, on their own,\n\nthe revocation of her clearance.\n\n Further, there is the glaringly differential treatment\n\nof Roy and Reed-Chapman. Although Reed-Chapman, who had never\n\ncomplained before, also told the captain that she and Roy were\n\nunattended for approximately fifteen minutes, and then put that\n\nimpression in writing, in an Incident Report, MDOC did not revoke\n\nReed-Chapman's security clearance. Reed-Chapman did file a\n\nreport, as the captain had requested. But a jury could believe\n\nRoy's assertion that she had been told that Ross did not want her\n\nto file more reports. Or, a jury could decide that MDOC did not\n\nactually need a report from Roy once it had Reed-Chapman's.\n\n In sum, Roy's § 4633 interference and retaliation claims\n\ncan proceed to trial.\n\nB. Claims against CCS under Title VII and Maine Law\n\n Roy has also produced sufficient evidence for her sexual\n\nharassment and retaliation claims against CCS to reach a jury.\n\n\n\n\n - 31 -\n\f 1. Hostile Work Environment Claims against CCS\n\n An employer like CCS can be liable for a hostile work\n\nenvironment created by third parties like MDOC's employees. See\n\nMedina-Rivera v. MVM, Inc., 713 F.3d 132, 137 (1st Cir. 2013);\n\nRodriguez-Hernandez v. Miranda-Velez, 132 F.3d 848, 854-55 (1st\n\nCir. 1998) (using ratification theory); see also, e.g., Gardner v.\n\nCLC of Pascagoula, LLC, 894 F.3d 654, 657 (5th Cir. 2018) (\"Because\n\nthe ultimate focus of Title VII liability is on the employer's\n\nconduct[,] . . . nonemployees can be the source of the\n\nharassment.\"); Beckford v. Dep't of Corr., 605 F.3d 951, 957 (11th\n\nCir. 2010) (\"It is well established that employers may be liable\n\nfor failing to remedy the harassment of employees by third parties\n\nwho create a hostile work environment.\").9 In these situations,\n\na finding that the harassment was so severe or pervasive as to\n\nalter the terms and conditions of the plaintiff's employment is\n\nnot by itself enough to make the employer liable. Liability for\n\na discriminatory environment created by a non-employee \"depends on\n\nwhether the employer knew or should have known of the hostile work\n\nenvironment and took reasonable measures to try to abate it.\"\n\nGardner, 894 F.3d at 663; see also, e.g., Freeman v. Dal-Tile\n\n\n\n 9 Federal law guides interpretation of the MHRA, Cookson\nv. Brewer Sch. Dep't, 974 A.2d 276, 281 (Me. 2009), and we consider\nthe MHRA to be parallel with Title VII here, cf. Watt, 969 A.2d at\n904 (noting that the MHRA standard for employer liability for\nco-worker harassment has developed concurrently with federal law).\n\n\n - 32 -\n\fCorp., 750 F.3d 413, 423 (4th Cir. 2014) (holding that employer\n\nliability depends on employer knowledge and whether the employer\n\nresponse was \"reasonably calculated to end the harassment\"\n\n(internal quotation marks omitted)). Circuit courts addressing\n\nthe issue of employer liability for third-party harassment have\n\nuniformly applied this rule.10\n\n The district court never discussed whether there was a\n\nbasis for CCS's liability under Title VII and the MHRA, and CCS\n\ndoes not argue on appeal that there is no legal basis. 11 We\n\nconsider the issue, however, because of the unique nature of Roy's\n\nworkplace, where workers employed by multiple entities shared a\n\nworksite that did not belong to Roy's employer and where the\n\norganizational relationships afforded non-employers influence over\n\nemployment conditions and decisions. See Dallan F. Flake,\n\nEmployer Liability for Non-Employee Discrimination, 58 B.C. L.\n\n\n\n 10 See Gardner, 894 F.3d at 657; Freeman, 750 F.3d at 423;\nSumma v. Hofstra Univ., 708 F.3d 115, 124 (2d Cir. 2013); Beckford,\n605 F.3d at 958; Freitag v. Ayers, 468 F.3d 528, 538 (9th Cir.\n2006); Dunn v. Washington Cty. Hosp., 429 F.3d 689, 691 (7th Cir.\n2005); Slayton v. Ohio Dep't of Youth Servs., 206 F.3d 669, 677\n(6th Cir. 2000); Lockard v. Pizza Hut, Inc., 162 F.3d 1062, 1073-\n74 (10th Cir. 1998); Crist v. Focus Homes, Inc., 122 F.3d 1107,\n1111 (8th Cir. 1997); see also 29 C.F.R. 1604.11(e) (stating that\nemployer can be liable for harassment by third parties \"where the\nemployer . . . knows or should have known of the conduct and fails\nto take immediate and appropriate corrective action.\").\n 11 CCS did argue in the district court that there was no\nbasis for employer liability because it \"took prompt and effective\naction\" when it learned of Roy's complaints.\n\n\n - 33 -\n\fRev. 1170, 1178-81 (2017) (stating that such organizational\n\ncomplexity is increasingly common and analyzing the implications\n\nfor third-party harassment claims).\n\n Many third-party harassment cases involve less complex\n\narrangements: common are cases involving retail customers or\n\nhealthcare facility patients who harass employees at a store or\n\nhealthcare facility operated by the employer. See, e.g., Lockard\n\nv. Pizza Hut, Inc., 162 F.3d 1062, 1067 (10th Cir. 1998)\n\n(customers); Gardner, 894 F.3d at 657 (patient). But those cases\n\ndo not purport to limit an employer's duty to those situations.\n\nIn our view, the duty to try to protect employees from sexual\n\nharassment exists in other environments, even in environments that\n\nare, like MDOC's prison, \"inherently dangerous\" and difficult to\n\ncontrol. Freitag v. Ayers, 468 F.3d 528, 539 (9th Cir. 2006)\n\n(\"[E]ven in an inherently dangerous working environment, the focus\n\nremains on whether the employer took reasonable measures to make\n\nthe workplace as safe as possible.\" (quotation marks omitted));\n\nsee also Beckford, 605 F.3d at 958-59; Gardner, 894 F.3d at 663-\n\n64 (applying this to nursing homes with diminished-behavioral-\n\ncapacity patients). CCS had an obligation to try to protect Roy\n\nfrom a hostile work environment, and the reasonableness rule\n\nconsistently applied in third-party harassment claims is adequate\n\n\n\n\n - 34 -\n\fto account for the complexities of her workplace.12 Cf. Beckford,\n\n605 F.3d at 959 (holding this test adequate to account for the\n\ncomplexities of a work environment in a prison).\n\n Ultimately, a jury must decide Roy's hostile work\n\nenvironment claims against CCS. CCS plainly knew of the\n\nharassment.13 The reasonableness of CCS's response is an issue\n\nfor the jury. Although CCS did not employ the corrections officers\n\nor manage the prison, CCS was not helpless to influence the\n\nofficers, their supervisors, or the operation of the prison's\n\nmedical facility. CCS had formal and informal mechanisms for\n\nraising Roy's complaints and for pressing for remedies. This\n\ninfluence over the environment and the officers is evident in\n\ninstances when MDOC responded to CCS's efforts by investigating\n\nand acting, as with Parrow. But CCS did not always use the\n\navailable mechanisms. It forwarded some but not all of Roy's\n\ncomplaints. And when MDOC's responses were dismissive or\n\n\n\n 12 We do not address whether this test applies to all other\narrangements. There may be situations that require separate\nconsideration of an employer's level of control or authority over\nthe environment or over the entity that employs the harassers.\nSee 29 C.F.R. § 1604.11(e) (stating that the EEOC will also\nconsider \"the extent of the employer's control and any other legal\nresponsibility which the employer may have with respect to the\nconduct of such non-employees.\"); see also Summa, 708 F.3d at 124-\n25 (considering whether level of control was sufficient to support\nliability).\n 13 Because this is a case of actual knowledge, we do not\nexplore the \"should have known\" element.\n\n\n - 35 -\n\finadequate, CCS often did nothing. Even when Roy's physical\n\nsafety was threatened by Turner's and King's absences from the\n\nclinic when inmates were present, CCS either did not refer Roy's\n\ncomplaints or accepted MDOC's inaction or arguably inappropriate\n\nresponses, without question. See Lockard, 162 F.3d at 1075\n\n(finding basis for liability in part on employer's failure to\n\naddress a \"potentially dangerous situation\" created by non-\n\nemployees). To give just one example, there is no evidence that\n\nCCS suggested steps like reassigning Turner, disciplining him, or\n\nadding additional layers of security. See Beckford, 605 F.3d at\n\n959-60 (identifying possible measures for mitigating harassment of\n\ncorrections officers by inmates); Gardner, 894 F.3d at 663 (giving\n\nexamples of mitigation sufficient to avoid liability in a case of\n\nharassment by a nursing home patient).\n\n Apart from what CCS did or could have done to influence\n\nMDOC is the issue of what CCS could have done on its own. A jury\n\ncould see as unreasonable CCS's changing story about and seeming\n\nfailure to consider an obvious mitigating measure, and one\n\nrequested by Roy -- a transfer.\n\n Entry of summary judgment was error. Roy's hostile work\n\nenvironment claims against CCS should go to a jury.\n\n 2. Retaliation Claims against CCS\n\n In granting summary judgment for CCS on Roy's\n\nretaliation claims under Title VII and Maine law, the district\n\n\n - 36 -\n\fcourt ruled that Roy's complaints were not protected activity\n\nbecause, in its view, CCS lacked \"the ability and authority to\n\ncorrect\" the complained-of violations. Roy, 321 F. Supp. 3d at\n\n169. We reverse, for errors of law and fact, addressing first the\n\nclaims under Title VII and the MHRA that CCS retaliated against\n\nRoy for complaints about the hostile work environment and second\n\nthe whistleblower retaliation claim under the MHRA and the MWPA.\n\n a. Title VII and MHRA Retaliation\n\n The Maine case relied on by the district court for its\n\ndefinition of protected activity, Hickson v. Vescom Corp., 87 A.3d\n\n704 (Me. 2014), interpreted § 833(2) of the MWPA, and does not\n\ndefine protected activity for Roy's Title VII or MHRA claims. See\n\n87 A.3d at 710 (citing Me. Rev. Stat. Ann. tit. 26, § 833(2)).\n\nUnder both Title VII and the MHRA, a jury could find that Roy's\n\ncomplaints were protected because they reported activity that she\n\nhad a reasonable, good faith belief violated those statutes. See\n\nFantini v. Salem State Coll., 557 F.3d 22, 32 (1st Cir. 2009)\n\n(citing 42 U.S.C. § 2000e-3).\n\n CCS does not defend the district court's rationale. It\n\nurges us to affirm the entry of summary judgment on the grounds\n\nthat Roy cannot show that her complaints were what caused her\n\ntermination and cannot show that CCS's neutral reason for firing\n\nher -- MDOC's revocation of the security clearance -- was pretext.\n\n\n\n\n - 37 -\n\fFactual disputes here require a jury to decide causation and\n\npretext.14\n\n The causation element of a Title VII retaliation claim\n\nis not satisfied by evidence that retaliation was one motivating\n\nfactor in the adverse action. See Nassar, 570 U.S. at 362-63.\n\nInstead, Roy must show \"but-for\" causation -- that is, that she\n\n\"would not have [been terminated] in the absence of the\" protected\n\ncomplaints. Id. at 360. Emphasizing this standard, CCS argues\n\nthat the revocation of the clearance was the sole but-for cause of\n\nRoy's termination.\n\n Factual disputes preclude summary judgment on this\n\ntheory of causation. To start, CCS and Roy dispute whether the\n\nrevocation of the security clearance meant that CCS could no longer\n\nemploy Roy. If CCS could have transferred Roy to one of its other\n\nfacilities in Maine, as Roy says, then a jury could find that\n\nretaliatory animus was a but-for cause of CCS's decision to fire\n\nher rather than transfer her. Significantly, CCS has not produced\n\nevidence that a transfer was impossible. CCS does not even deny\n\nthat a transfer was possible, emphasizing instead that the burden\n\n\n\n\n 14 The familiar burden-shifting framework from McDonnell-\nDouglas Corp. v. Green, 411 U.S. 792 (1973), applies. The elements\nother than causation and pretext are easily settled in Roy's favor:\nAs we have said, Roy engaged in protected activity. She also\nsuffered an adverse employment action when she was fired.\n\n\n - 38 -\n\fwas on Roy to ask about other positions. But Roy did so, in mid-\n\nSeptember.\n\n Alternatively, a jury could conclude that MDOC's\n\nretaliatory animus caused the revocation of the security clearance\n\nand, in turn, caused Roy's termination. A third party's\n\nretaliatory or discriminatory animus can cause an employer's\n\nadverse action where, as a jury might find here, the employer knew\n\nthat animus motivated the third-party's actions or demands and\n\nsimply accepted those actions or demands. Cf. Rodriguez-\n\nHernandez, 132 F.3d at 854-55 (holding that customers'\n\ndiscriminatory preferences, where ratified by the employer, can\n\ncause Title VII discrimination); Tamosaitis v. URS Inc., 781 F.3d\n\n468, 482-83 (9th Cir. 2015) (holding that client's demand to remove\n\na whistleblowing employee from a project caused employer's adverse\n\naction under an analogous statute).\n\n Similar facts would permit a jury to find that CCS's\n\nstated reason was pretext for a retaliatory motive. See Billings\n\nv. Town of Grafton, 515 F.3d 39, 55 (1st Cir. 2008) (quoting\n\nHodgens v. Gen. Dynamics Corp., 144 F.3d 151, 168 (1st Cir. 1998))\n\n(explaining that pretext can be shown through facts that expose\n\n\"weaknesses, implausibilities, inconsistencies, incoherencies, or\n\ncontradictions in the employer's proffered legitimate reasons\").\n\nWe mention just a few. The facts about the possibility of transfer\n\nweaken CCS's insistence that the security clearance was the sole\n\n\n - 39 -\n\fand actual reason for the firing. That CCS put Roy on leave\n\n(telling her it was temporary) immediately after the September 26\n\nmeeting, a week before the clearance was revoked and her employment\n\nwas terminated, could undermine CCS's claim that it harbored no\n\ndesire to retaliate. Or a jury could infer from CCS's failure to\n\ndiscipline Reed-Chapman that CCS did not find discipline-worthy\n\nthe conduct that MDOC says led to the revocation of Roy's\n\nclearance. Yet CCS did not try to stop MDOC from using that\n\nconduct to \"gate-close\" Roy. To the contrary, CCS immediately,\n\nand apparently without question, fired Roy once she lost her\n\nclearance. A jury should evaluate the issue of pretext.\n\n b. Whistleblower Retaliation\n\n A jury should also decide Roy's whistleblower\n\nretaliation claim. As just discussed, whether Roy's complaints\n\ncaused her termination and whether CCS's stated reason is pretext\n\nare triable issues. The jury, if it sees a need to, can tease\n\napart the effects of the two sets of complaints -- those about\n\nsexual harassment and those about officers leaving Roy alone with\n\ninmates, asking for confidential inmate medical information, and\n\nrefusing to bring inmates to the clinic.\n\n Further, a jury could deem Roy's whistleblowing\n\ncomplaints protected activity, as they relate to potential\n\nviolations of medical privacy laws and to health and safety risks\n\nat the prison. See id. § 4572(1) (making unlawful discrimination\n\n\n - 40 -\n\fbased on protected whistleblower activity); Me. Rev. Stat. Ann.\n\ntit. 26, § 833(1)(A)-(B) (defining protected whistleblower\n\nactivity as reporting \"a violation of a [state or federal] law or\n\nrule\" or \"a condition or practice that would put at risk the health\n\nor safety of . . . [an] individual.\"). The district court erred\n\nin ruling that Roy's complaints were unprotected because CCS\n\nlacked, under Hickson, \"the ability and authority to correct\" the\n\ncomplained-of violations. Roy, 321 F. Supp. 3d at 169 (quoting\n\nHickson, 87 A.3d at 711).\n\n CCS argues, following the district court's reading, that\n\nHickson, and the MWPA provision it interpreted, require evidence\n\nof direct authority to correct the violations, as the employee in\n\nHickson, who complained about safety at a mill, was employed by\n\nthe company directly responsible for mill safety. 87 A.3d at 711.\n\nYet Hickson nowhere limited its interpretation of § 833(2) to those\n\nfacts. Nor does the language of the provision suggest that the\n\nemployer's corrective authority must be direct. It states that\n\nwhistleblower protection applies to an employee who \"has first\n\nbrought the alleged violation, condition or practice to the\n\nattention of a person having supervisory authority with the\n\nemployer and has allowed the employer a reasonable opportunity to\n\ncorrect that violation, condition or practice.\" Me. Rev. Stat.\n\nAnn. tit. 26, § 833(2). We see no reason why a jury could not\n\nfind \"ability and authority to correct,\" Hickson, 87 A.3d at 711,\n\n\n - 41 -\n\feven if that control is indirect. We have already established\n\nthat CCS had both formal and informal mechanisms for influencing\n\nMDOC, its officers, and the operation of the prison. Roy's\n\nwhistleblower retaliation claim should go to the jury.\n\nC. Claims against Ross and Bouffard under § 1983\n\n Roy alleges that Bouffard and Ross, the top prison\n\nofficials, failed to stop prison staff from sexually harassing her\n\nin violation of the Equal Protection Clause15 and that Bouffard and\n\nRoss revoked her security clearance because of her complaints, in\n\nviolation of the First Amendment. Qualified immunity protects\n\nRoss and Bouffard from suit because reasonable officials could\n\nhave believed \"on the[se] facts\" that no equal protection or First\n\nAmendment violation occurred.16 Dirrane v. Brookline Police Dep't,\n\n315 F.3d 65, 69 (1st Cir. 2002).\n\n Supervisors like Ross and Bouffard are liable under the\n\nEqual Protection Clause for a hostile work environment created by\n\ntheir subordinates in state government only if their \"link\" to the\n\n\n\n 15 Roy does not raise on appeal a second equal protection\nclaim, also rejected by the district court, that Bouffard, Ross,\nand the officers retaliated against her for complaining about the\nharassment. Roy, 321 F. Supp. 3d at 170.\n 16 The district court did not reach the qualified immunity\ndefense on the equal protection claim, holding simply that that\nRoy could not establish an equal protection violation. Roy, 321\nF. Supp. 3d at 170. On the First Amendment claim, the district\ncourt held that, even if there were a constitutional violation,\nthe officers would have qualified immunity. Id. at 173.\n\n\n - 42 -\n\funlawful harassment was one of \"'supervisory encouragement,\n\ncondonation, or acquiescence,' or 'gross negligence amounting to\n\ndeliberate indifference.'\" Lipsett, 864 F.2d at 902 (quoting\n\nBohen v. City of East Chicago, 799 F.2d 1180, 1189 (7th Cir.\n\n1986)). Two First Circuit cases apply this principle. In the\n\nsingle case finding supervisory liability under § 1983 for sexual\n\nharassment, the defendants knew of severe abuse but failed even to\n\ninvestigate. See id. at 890-93, 907. In the other case, which\n\nfound no supervisor liability, the defendant, the harasser's\n\nsupervisor, at first discouraged the plaintiff from filing a formal\n\ncomplaint but then actively encouraged her to do so. See Sanchez\n\nv. Alvarado, 101 F.3d 223, 225, 228-29 (1st Cir. 1996). Ross and\n\nBouffard's conduct falls somewhere between these guideposts.\n\nComplaints against Snow and Parrow were investigated and addressed\n\nwhile complaints about Turner, DeGuisto, and officers' retaliatory\n\nbehavior were not. \"[A]s is common where there is a lack of\n\nprecedent, this is not a case in which a reasonable officer must\n\nhave known that he was acting unconstitutionally.\" Dirrane, 315\n\nF.3d at 71 (footnote omitted).\n\n Ross and Bouffard also receive qualified immunity from\n\nthe First Amendment retaliation claim because reasonable officials\n\ncould have believed that revoking Roy's security clearance would\n\nnot violate the Constitution. To show a First Amendment\n\nviolation, one thing Roy must demonstrate is that she was speaking\n\n\n - 43 -\n\fas a private citizen on a matter of public concern.17 Complaints\n\nlike Roy's made to supervisors and public officials about sexual\n\nharassment and safety at public agencies can be protected citizen\n\nspeech on matters of public concern. See, e.g., Baron v. Suffolk\n\nCty. Sheriff's Dep't, 402 F.3d 225, 233 (1st Cir. 2005) (upholding\n\na jury verdict on a First Amendment claim by a corrections officer\n\nwho had complained internally about discrimination and operation\n\nof a prison); Campbell v. Galloway, 483 F.3d 258, 270 (4th Cir.\n\n2007) (holding that police officer's letter to police chief about\n\nsexual harassment was protected by the First Amendment). But we\n\ncannot say that a reasonable official must have known that Roy's\n\ncomplaints were constitutionally protected. Significantly, Roy\n\nonly complained internally. And, although the Supreme Court has\n\nestablished that form is never \"dispositive\" of the public concern\n\nquestion, Garcetti v. Ceballos, 547 U.S. 410, 420 (2006), it has\n\nsometimes seen a plaintiff's failure \"to inform the public\" about\n\nher concerns as cutting against First Amendment protection,\n\nConnick v. Myers, 461 U.S. 138, 148 (1983); see also, e.g., City\n\nof San Diego v. Roe, 543 U.S. 77, 84 (2004) (per curiam).\n\n\n 17 Roy must also show that her interests in speaking\noutweighed MDOC's interest in efficient public services, see\nPickering v. Board of Educ., 391 U.S. 563, 568 (1968), and that\nthe protected speech was a substantial or motivating factor in the\nadverse employment decision, see Mt. Healthy City Sch. Dist. Bd.\nEduc. v. Doyle, 429 U.S. 274, 287 (1977); see also, e.g., Decotiis\nv. Whittemore, 635 F.3d 22, 29-30 (1st Cir. 2011) (describing the\nwhole test).\n\n\n - 44 -\n\fReasonable officials in Ross and Bouffard's positions, then, could\n\nhave deemed Roy's complaints unprotected. As a result, even if\n\nRoy could ultimately make out a First Amendment violation, the\n\ndefendants receive qualified immunity.\n\n IV.\n\n We reverse summary judgment for MDOC and CCS and affirm\n\nsummary judgment for Ross and Bouffard. Costs are awarded to Roy.\n\n\n\n\n - 45 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362557/", "author_raw": "LYNCH, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4585304/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Tara J. ROY, Plaintiff, Appellant, v. CORRECT CARE SOLUTIONS, LLC; State of Maine Department of Corrections; Rodney Bouffard, Individually; Troy Ross, Individually, Defendants, Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-28\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1313\n\n TARA J. ROY,\n\n Plaintiff, Appellant,\n\n v.\n\n CORRECT CARE SOLUTIONS, LLC; STATE OF MAINE DEPARTMENT OF\n CORRECTIONS; RODNEY BOUFFARD, individually; TROY ROSS,\n individually,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MAINE\n\n [Hon. Jon D. Levy, U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n John P. Gause, with whom Eastern Maine Law, LLC was on brief,\nfor appellant.\n Gail S. Coleman, with whom James L. Lee, Deputy General\nCounsel, Jennifer S. Goldstein, Associate General Counsel, and\nElizabeth E. Theran, Assistant General Counsel, were on brief, for\nthe Equal Opportunity Employment Commission, amicus curiae.\n Barbra L. Archer Hirsch on brief for Maine Human Rights\nCommission, amicus curiae.\n Melinda J. Caterine, with whom Littler Mendelson, P.C. was on\nbrief, for appellee Correct Care Solutions, LLC.\n Valerie A. Wright, Assistant Attorney General, with whom\nSusan P. Herman, Deputy Attorney General, and Janet T. Mills,\nAttorney General of Maine, were on brief, for appellees State of\n\fMaine Department of Corrections, Bouffard, and Ross.\n\n\n January 28, 2019\n\n\n\n\t\n\f LYNCH, Circuit Judge. This case raises important issues\n\nabout employer liability for a hostile work environment created by\n\nthird parties and about non-employer liability for employment-\n\nrelated discrimination under the Maine Human Rights Act (MHRA).\n\nWe articulate here the rules which govern these claims.\n\n Tara Roy, the plaintiff, worked as a nurse, employed by\n\nCorrect Care Solutions, LLC (CCS), at a Maine Department of\n\nCorrections (MDOC) prison. After MDOC revoked her prison security\n\nclearance and CCS terminated her employment in October 2014, Roy\n\nsued three sets of defendants: CCS, the MDOC, and two individuals,\n\nthe prison's warden and deputy warden. She alleged that\n\ndiscrimination and sexual harassment by the prison's corrections\n\nofficers made her work environment hostile and that she was\n\nretaliated against for complaints about the hostile work\n\nenvironment and for other whistleblowing.\n\n Specifically, Roy alleged that CCS violated Title VII\n\nand § 4572 of the MHRA by not responding adequately to her\n\ncomplaints about the hostile work environment and by retaliating\n\nagainst her in terminating her employment for protected\n\ncomplaints. Her claims against MDOC under § 4633 of the MHRA\n\nalleged that MDOC interfered with her MHRA-protected right to work\n\nfree from discrimination and that MDOC's revocation of her security\n\nclearance was unlawful retaliation. Finally, against Rodney\n\nBouffard, the warden, and Troy Ross, the deputy warden, Roy brought\n\n\n - 3 -\n\fclaims under 42 U.S.C. § 1983 for violations of the Equal\n\nProtection Clause and the First Amendment.\n\n The district court granted summary judgment to all\n\ndefendants on all claims. See Roy v. Correct Care Solutions, LLC,\n\n321 F. Supp. 3d. 155, 160 (D. Me. 2018). We reverse as to CCS and\n\nMDOC and affirm as to Bouffard and Ross.\n\n After an overview of the facts, we first explain that a\n\njury could find that Roy's work environment was discriminatorily\n\nhostile. Having established this, we proceed to examine liability\n\nfor each defendant. We reverse summary judgment for MDOC, first\n\ndeciding an unresolved question of Maine law about the scope of\n\n§ 4633 non-employer liability for workplace harassment and then\n\nfinding disputes of material fact. Next, in reversing summary\n\njudgment for CCS, we explain that an employer can be liable for a\n\nhostile work environment created by non-employees as long as the\n\nemployer knew of the harassment and failed to take reasonable steps\n\nto address it. A jury could find CCS liable for failing to protect\n\nRoy from the harassment, as well as for retaliation. Finally, we\n\naffirm summary judgment for the warden and deputy warden. Ross\n\nand Bouffard receive qualified immunity, as reasonable officials\n\ncould have believed on these facts that no equal protection or\n\nFirst Amendment violations occurred.\n\n\n\n\n - 4 -\n\f I.\n\n We present the facts in the light most favorable to Roy\n\nand draw all reasonable inferences in her favor, as we must at\n\nsummary judgment. Pippin v. Boulevard Motel Corp., 835 F.3d 180,\n\n181 (1st Cir. 2016).\n\n Under a contract with MDOC, CCS operates and staffs the\n\nmedical facility at the Maine State Prison (MSP) in Warren, Maine.\n\nIn August 2012, CCS hired Roy to work as a licensed practical nurse\n\nat the MSP, where the medical facility consists of an infirmary\n\nand a clinic. Roy worked in the clinic, and primarily interacted\n\nwith the prison's corrections officers when they brought inmates\n\nin for treatment. As a safety measure, two officers were also\n\nspecifically assigned to the medical facility, one to the clinic\n\nand one to the infirmary.\n\n In late 2012, Davis Snow, the officer assigned to the\n\nclinic, made sexual jokes and degrading comments about women to\n\nRoy and made physical contact with Roy on two occasions. Snow's\n\nremarks were \"constant[].\" He said, for example, \"don't worry,\n\nit's because you are blonde. You wouldn't understand,\" and, \"I\n\nwouldn't expect someone like you to understand how things are\n\ndone.\" Snow also once squeezed and twisted Roy's wrist until she\n\ndropped to her knees in pain. And he once bent her over a chair\n\nand spanked her.\n\n\n\n\n - 5 -\n\f Roy complained to her CCS supervisors and MDOC about\n\nSnow in early 2013. After MDOC investigated these complaints,\n\nSnow was reassigned, away from the medical facility.\n\n About a year later, in the spring of 2014, Roy began\n\nworking with Donny Turner, who was often the corrections officer\n\nassigned to the medical clinic. Turner, like Snow, \"constantly\"\n\nmade derogatory jokes and comments about women. He said, \"[W]hy\n\ndo we have females when . . . men do everything,\" and that a\n\nwoman's \"job is to be at home.\" Turner continued his remarks even\n\nafter Roy told him that his comments were not funny.\n\n On June 20, 2014, Roy filed an Incident Report about\n\nTurner's degrading comments. The report also complained that\n\nTurner's behavior created health and safety risks. Roy explained\n\nthat Turner sometimes ignored her, left her alone in exam rooms\n\nwith inmates, and did not respond to her requests to bring sick or\n\ninjured inmates to the clinic.\n\n CCS employees were instructed to fill out MDOC Incident\n\nReports to provide information about any disruptions in the work\n\nof the clinic involving corrections officers. CCS says that\n\nreports by its employees about MDOC officers were usually submitted\n\nto CCS supervisors Elisabeth Lamson, CCS's administrator at the\n\nprison, and Robin Cross-Snell, the prison's head nurse. CCS also\n\nsays that such reports were then referred to MDOC within a day or\n\n\n\n\n - 6 -\n\ftwo for investigation, but the record suggests that this was not\n\nalways done.\n\n Outside of this formal Incident Report process,\n\nBouffard, the warden, and Ross, the deputy warden for operations,\n\nhad frequent contact with Cross-Snell and Lamson. The CCS\n\nsupervisors attended the prison's daily operations briefings, and\n\nLamson routinely spoke informally with MDOC officials about\n\nconcerns related to the medical facility.\n\n Roy's report on Turner went to Lamson, and Lamson\n\nbelieves she may have spoken with Turner about the report. But\n\nshe did not bring the issue to his supervisors, and there is no\n\nevidence that it was ever referred to or investigated by MDOC.\n\n Turner's behavior around Roy escalated after Roy filed\n\nthe Incident Report about him. Turner often left Roy alone with\n\ninmates, was frequently absent from his post in the clinic, talked\n\ndown to Roy, and worked slowly or ignored Roy when she needed\n\nsomething. It is considered a security risk for an officer at the\n\nmedical facility to leave his post, particularly when inmates are\n\naround.\n\n Roy continued to complain about Turner to her\n\nsupervisors, in person and by email. For example, on July 23, 24,\n\nand 31, 2014, Roy emailed Lamson saying that Turner was absent\n\nfrom his post in the clinic for as long as twenty minutes while\n\ninmates were there. Lamson forwarded at least one of Roy's emails\n\n\n - 7 -\n\fabout Turner to MDOC, but there is no evidence that MDOC\n\ninvestigated or acted on these reports by Roy about Turner, or\n\nthat CCS ever followed up.\n\n In early August 2014, Roy emailed Lamson about an\n\nincident with Officer Ernest Parrow. When Roy reminded Parrow\n\nabout the proper procedure for bringing sick inmates to the clinic,\n\nParrow told Roy to \"stop being a bitch.\" He added that he now\n\nunderstood why people hated her. Later that month, on August 26,\n\nRoy sent an Incident Report to Cross-Snell stating that she had\n\ncalled Parrow to ask him to bring an inmate to the clinic to sign\n\na form and that Parrow had responded by again calling her a \"bitch\"\n\nand then hanging up on her.\n\n Along with this August 26 Incident Report, Roy provided\n\nto CCS several sexually explicit text messages that Parrow had\n\nsent her earlier that summer. Parrow, who had previously had a\n\nbrief romantic relationship with Roy, texted her, \"There is still\n\na thing or two I didn't get to do to ya,\" and \"if you want me to\n\nbend you over let me know.\" Roy responded, \"U have a\n\n[girlfriend]!!!\" to the first message and ignored the second. She\n\ntold Cross-Snell that Parrow was angry with her in part because\n\nshe had rejected his advances.\n\n Cross-Snell verified that Parrow had called Roy a\n\n\"bitch\" twice and wrote an Incident Report, which she sent to MODC;\n\nCCS also gave MDOC the text messages between Parrow and Roy. CCS's\n\n\n - 8 -\n\fregional vice president, John Newby, who supervised Roy's\n\nsupervisors, learned that Parrow had called Roy a \"bitch\" twice\n\nand, on August 28, spoke with Ross, the deputy warden, about it.\n\nRoss says he then investigated Parrow's behavior, in part by\n\nreviewing the explicit text messages. Because of the alleged\n\nname-calling, Ross talked to Parrow about workplace\n\nprofessionalism.\n\n The text messages from Parrow reviewed by CCS and MDOC\n\nalso showed an exchange between Parrow and Roy on July 16, 2014,\n\nin which Parrow said Roy was \"being a shit\" after Roy refused to\n\nshare with him medical information that he wanted about an inmate.\n\nRoy said that the information, an inmate's prescribed medications,\n\nwas confidential by statute and that Parrow was not authorized to\n\nreceive it.\n\n Parrow was not the only officer asking Roy for\n\nconfidential medical information. Throughout July and August\n\n2014, Roy complained to her supervisors that she and other medical\n\nstaff were getting frequent calls from corrections officers\n\nrequesting confidential information. She said that officers\n\nresponded to her refusals to share it by calling her names,\n\nyelling, hanging up on her, and threatening to file grievances\n\nagainst her. At least four times during the summer of 2014, she\n\nemailed her supervisors reporting specific incidents. Roy says\n\nnothing was done by CCS or MDOC.\n\n\n - 9 -\n\f Roy also says that by mid-August multiple corrections\n\nofficers showed daily hostility toward her. Several of these\n\nofficers, including Parrow, Snow, Paul Dever, and Paul Garrido,\n\nalso filed Incident Reports complaining about Roy. For example,\n\nSnow filed a report stating that Roy had yelled at him. To Roy,\n\nthe officers' hostility and the filed Incident Reports constituted\n\nretaliation against her for her complaints about Snow, Turner,\n\nParrow, and their requests for confidential medical information.\n\nAt her deposition, Roy said, \"[W]ith the officers, when one is\n\nupset with somebody, they all are.\"\n\n Lamson and Cross-Snell met with Roy on August 14 about\n\nthe reports filed about her. Roy told her supervisors that the\n\nreports were false or exaggerated. Lamson and Cross-Snell warned\n\nRoy that she \"could be moved to another department\" if her behavior\n\ndid not change. At that point in August, CCS obviously\n\ncontemplated that it could move Roy to a different job within CCS.\n\nWeeks later, CCS's position changed, as we describe below.\n\n On September 12, Garrido told Roy that Officer Curtiss\n\nDoyle had said to him that an inmate needed to get sick so that\n\nthe ensuing emergency medical call would \"get Tara off her fat\n\nlazy ass.\" Roy filed another Incident Report that day saying that\n\nshe viewed this comment as sexual harassment. MDOC investigated\n\nthe incident in late September, days before Roy's employment was\n\nterminated.\n\n\n - 10 -\n\f Also on September 12, Roy emailed the CCS human resources\n\nspecialist, copying Cross-Snell, Lamson, and their supervisor\n\nNewby, asking for a transfer to a different CCS facility \"d[ue] to\n\nthe fact that I currently feel that my work site is bo[]rd[er]ing\n\non a hostile work environment.\" The record shows no response to\n\nRoy's email, and Roy does not remember getting one.\n\n That same week, Officer William DeGuisto messaged Roy on\n\nFacebook to say, \"You['re] lucky [Officer Paul] Dever is out on\n\nadmin leave[.] He was trying hard to get you fired.\" When Roy\n\nasked for more information, DeGuisto told her that Dever \"fucking\n\ncomplained to everyone you were picking on Turner and trying to\n\nget him fired\" and that Dever \"wrote a few reports on you.\" When\n\nRoy said that Dever \"does [not] have ANY reason to write reports\n\non me,\" DeGuisto offered, \"He says you have fucked everyone in the\n\nprison.\"\n\n DeGuisto then asked in a Facebook message if he could\n\ncall Roy, but she replied she would \"rather not\" give him her phone\n\nnumber. A few days later, he asked again if he could call her,\n\nand added, \"Please try to smile at my window and not look at me\n\nlike I'm the enemy.\" Four days after that, DeGuisto messaged her:\n\n\"Another report written against you today!!! And you still act\n\nlike you mad at my window[.] See you, I UN FRIEND YOU Tired of\n\nattitude.\"\n\n\n\n\n - 11 -\n\f Roy filed an Incident Report about DeGuisto's Facebook\n\nmessages, attaching the exchange about Dever and the later requests\n\nto call her. Lamson passed the report to her supervisor, Newby,\n\nand planned to discuss the report with Bouffard, the warden.\n\nAlthough MDOC says that it reviewed the allegations, Bouffard and\n\nRoss explained at their depositions that they did not act on the\n\ncomplaint because the interaction occurred on Facebook. Even\n\nthough Roy and DeGuisto's messages were about what Roy, DeGuisto,\n\nand Dever had done, said, and heard in the workplace, in Ross's\n\nview, \"The Facebook stuff, that's off-duty stuff. We don't do\n\nmuch with that.\" Similarly, Bouffard called the conversation\n\n\"something that was going on in their own private lives.\"\n\n After Roy filed the Incident Report about DeGuisto,\n\nLamson spoke to Roy about all the Incident Reports she had filed.\n\nWhat happened at the meeting is disputed. As Roy remembers it,\n\nLamson told Roy that she should not write any more reports about\n\ncorrections officers because Ross was upset with Roy's frequent\n\ncomplaints. As Lamson remembers it, she told Roy \"that the\n\nreport[s Roy files] should be of substance.\"\n\n About two weeks later, on September 26, 2014, Roy and\n\nanother nurse, Vanessa Reed-Chapman, were working in the clinic\n\nwhen Officer King was the correctional officer assigned to the\n\nclinic and Officer Snodgrass was assigned to the infirmary.\n\n(Turner was usually the officer assigned to the clinic, rather\n\n\n - 12 -\n\fthan King, and Snodgrass's typical assignment was the front desk.)\n\nAt about 10:00 that morning, a member of the medical staff was\n\ncalled to a medical emergency elsewhere in the prison. Protocol\n\nrequired the officer assigned to the infirmary to accompany the\n\nmedical staff member, as the infirmary could be locked to secure\n\nthe inmates there. That day, however, King was asked to respond\n\nto the call instead of Snodgrass.\n\n After King left, Roy and Reed-Chapman, who were then\n\nalone with three inmates in the medical clinic, called Snodgrass\n\nthree times to come over from the infirmary. If the medical clinic\n\nofficer was away, the infirmary officer was supposed to secure the\n\ninfirmary and come to the clinic. Surveillance footage shows\n\nSnodgrass asleep at his desk and unresponsive to the nurses' calls.\n\nEventually, Snodgrass did come over.\n\n Lamson learned of this incident from both Roy and Reed-\n\nChapman and called MDOC's Captain Melquist, who came to the clinic\n\nto speak with the nurses. Roy and Reed-Chapman each told Melquist\n\nthat the officer on duty in the clinic, King, had responded to a\n\ncall, that King had left Roy and Reed-Chapman with prisoners and\n\nwithout a corrections officer, and that the infirmary officer on\n\nduty, Snodgrass, did not arrive to cover the clinic for fifteen\n\nminutes.\n\n Although Melquist told Roy and Reed-Chapman to file\n\nIncident Reports, Roy did not do so because of what Lamson had\n\n\n - 13 -\n\ftold her about Ross not wanting Roy to file more reports. Reed-\n\nChapman did file an Incident Report, writing that King left at\n\n\"Approx 10[:]00\" with \"3 inmates still present in clinic with NO\n\nSupervision By DOC.\" She continued, \"[O]fficer did eventually\n\ncome to clinic @ 10[:]15. Safety Risk.\"\n\n Surveillance footage shows a different officer,\n\nTherrien, in the clinic thirty seconds after King left. The video\n\ndoes not show Therrien assuming King's duties or his post.\n\nTherrien was there letting inmates in and out of the clinic. The\n\nvideo also shows Snodgrass arriving about six minutes after King\n\nleft. Either Therrien or Snodgrass is on camera in the clinic for\n\nall but one minute and forty-nine seconds of the fifteen minutes\n\nafter King left. (MDOC says that Therrien never left the clinic,\n\nand only occasionally left the view of the camera.)\n\n That same afternoon, Lamson and Cross-Snell met with\n\nCaptain Melquist, Ross, and the MDOC human resources\n\nrepresentative. At the meeting, the captain expressed concern\n\nabout the discrepancies between the surveillance video and Roy and\n\nReed-Chapman's statements about being unattended for approximately\n\nfifteen minutes. Ross then said that he was frustrated that Roy\n\nwas involved in so many investigations, adding that he wanted to\n\n\"gate-close\" Roy -- that is, to revoke Roy's security clearance.\n\nRoss later said that he wanted to do this in part because of \"any\n\n[reports] that she may have been involved in.\"\n\n\n - 14 -\n\f The CCS Team Member Manual provides that employees like\n\nRoy are expected to maintain prison security clearances. At the\n\nMSP, clearances were controlled by MDOC, and Bouffard was the\n\nultimate decisionmaker.\n\n Although CCS was aware after the meeting that Roy's\n\nsecurity clearance was in limbo, there is no evidence that CCS had\n\nany discussions with MDOC about Roy after September 26. CCS did\n\nplace Roy on \"temporary suspended leave\" that day. Newby, the\n\nregional vice president, told Roy that he knew she had done nothing\n\nwrong and that the leave was merely a cooling off period. The\n\nleave was not temporary.\n\n A week later, on October 2, 2014, Bouffard emailed Newby\n\nstating, \"Effective immediately as a result of misconduct nurse\n\nTara Roy will no longer be allowed entrance to the facility.\n\nSpecifically, she misrepresented the truth and subsequently failed\n\nto follow a directive.\" Bouffard made this decision without\n\nspeaking to Roy or Reed-Chapman about the September 26 incident.\n\nIndeed, aside from the captain, who spoke to Roy and Reed-Chapman\n\non September 26, no one at MDOC inquired of them about their\n\nversion of events.\n\n MDOC did not revoke Reed-Chapman's security clearance,\n\nalthough she had made the same representations, or\n\n\"misrepresent[ations],\" as Roy. At deposition, Bouffard explained\n\nthat he chose not to revoke Reed-Chapman's clearance because she\n\n\n - 15 -\n\fwas a new employee who \"took direction\" from Roy. At the time,\n\nCCS did not ask MDOC to explain the discrepancy, nor did CCS\n\ndiscipline Reed-Chapman.\n\n CCS terminated Roy's employment the day MDOC revoked her\n\nclearance. Lamson told Roy that she could no longer work at the\n\nMSP because of the loss of her clearance and that CCS had no\n\nopenings at other facilities. CCS's two other sites in\n\nMaine -- the Androscoggin County Jail and the Two Bridges\n\nJail -- were not MDOC facilities and had security clearance systems\n\nseparate from the MSP's. Later, Lamson admitted that she had not\n\nlooked into and did not actually know on October 2 whether CCS had\n\nopenings at these facilities.\n\n II.\n\n We start with Roy's allegations that she was subjected\n\nto a hostile work environment in violation of Title VII, the MHRA,\n\nand the Equal Protection Clause. This allegation is an essential\n\ningredient of Roy's sexual harassment claims against all\n\ndefendants. We conclude that a reasonable jury could find that\n\nRoy's work environment was hostile, and we turn in later sections\n\nto the liability of each defendant.\n\n A hostile work environment is one \"permeated with\n\ndiscriminatory intimidation, ridicule, and insult, that is\n\nsufficiently severe or pervasive to alter the conditions of the\n\nvictim's employment.\" Harris v. Forklift Sys. Inc., 510 U.S. 17,\n\n\n - 16 -\n\f21 (1993) (internal quotations and citations omitted). To succeed\n\non a hostile work environment claim under Title VII, a plaintiff\n\nmust establish six elements:\n\n (1) that she (or he) is a member of a protected\n class; (2) that she was subjected to unwelcome\n sexual harassment; (3) that the harassment was\n based upon sex; (4) that the harassment was\n sufficiently severe or pervasive so as to\n alter the conditions of plaintiff's employment\n and create an abusive work environment;\n (5) that sexually objectionable conduct was\n both objectively and subjectively offensive,\n such that a reasonable person would find it\n hostile or abusive and the victim in fact did\n perceive it to be so; and (6) that some basis\n for employer liability has been established.\n\nO'Rourke v. City of Providence, 235 F.3d 713, 728 (1st Cir. 2001)\n\n(citing Faragher v. City of Boca Raton, 524 U.S. 775, 787-89\n\n(1998)). A hostile work environment claim under the MHRA is\n\n\"concurrent with Title VII.\" Watt v. UniFirst Corp., 969 A.2d\n\n897, 903 (Me. 2009). At issue now are whether the harassment was\n\nbased upon sex and whether it was sufficiently severe or pervasive.\n\nLater, we discuss the bases for liability.1\n\n\n\n\n 1 The other elements are not genuinely contested. CCS\ndoes offer a one-paragraph argument on appeal that Roy was not\nsubjectively offended. This argument is not well developed, and\nis waived. United States v. Zannino, 895 F.2d 1, 17 (1st Cir.\n1990). Nor is the argument convincing. Roy repeatedly asked the\ncorrections officers to stop their behavior and made formal\ncomplaints to her supervisors and MDOC, including a request to be\ntransferred.\n\n\n\n - 17 -\n\f The district court concluded that a hostile work\n\nenvironment did not exist.2 In ruling that much of the conduct\n\nRoy alleged was not based upon her sex and that the harassment she\n\nexperienced was not sufficiently severe or pervasive, the district\n\ncourt applied an erroneous legal standard and also erroneously\n\nresolved material disputes of fact. See Roy, 321 F. Supp. 3d at\n\n166-68.\n\n Roy must show that a jury could find the harassment she\n\nexperienced \"was based in part on her\" sex. Franchina v. City of\n\nProvidence, 881 F.3d 32, 54 (1st Cir. 2018). The district court\n\nerred when it suggested that Roy's sex must be the but-for cause\n\nor even the sole cause of each alleged harassing incident. Roy,\n\n321 F. Supp. 3d at 167. The Supreme Court has squarely rejected\n\nthese standards for hostile work environment claims. See Univ.\n\nof Texas Sw. Med. Ctr. v. Nassar, 570 U.S. 338, 343 (2013) (\"It\n\nsuffices . . . to show [on a hostile work environment claim] that\n\nthe motive to discriminate was one of the employer's\n\n\n\n 2 Roy has also appealed the district court's determination\nthat the allegations about Snow were untimely. \"This is a question\nthat need not be resolved here, as\" none of Roy's Title VII or\nMHRA claims \"turn[] on it.\" Maher v. Mass. Gen. Hosp. Long Term\nDisability Plan, 665 F.3d 289, 301 (1st Cir. 2011).\n Even so, the allegations against Snow may be considered\nas \"relevant background evidence to show that discriminatory\nanimus motivated the acts that occurred within\" the statutory time\nwindows. Malone v. Lockheed Martin Corp., 610 F.3d 16, 22 (1st\nCir. 2010) (citing Rathbun v. Autozone, Inc., 361 F.3d 62, 76 (1st\nCir. 2004)).\n\n\n - 18 -\n\fmotives . . . .\"); Price Waterhouse v. Hopkins, 490 U.S. 228, 240\n\n(1989) (plurality opinion) (\"To construe the words 'because of' as\n\ncolloquial shorthand for 'but-for causation' . . . is to\n\nmisunderstand them.\").3\n\n Much of the abuse Roy experienced was undoubtedly based\n\non her sex: Turner made constant derogatory comments about women;\n\nDeGuisto pestered her for her phone number in Facebook messages\n\nand conveyed that Dever was spreading rumors that she had \"fucked\"\n\neveryone in the prison;4 and Parrow sent her graphically sexual\n\ntext messages. The district court erred in disregarding three\n\nother allegations that it viewed as insufficiently \"connected to\n\nRoy's sex.\" Roy, 321 F. Supp. 3d at 167.\n\n\n 3 The Maine case cited by the district court is not to the\ncontrary. See Roy, 321 F. Supp. 3d at 167 (citing Bowen v. Dep't\nof Human Servs., 606 A.2d 1051, 1053-54 (Me. 1992)). That case\nsaid that but-for causation \"would be sufficient\" under the MHRA,\nnot that proof of but-for causation was necessary. Bowen, 606\nA.2d at 1053 (emphasis added).\n 4 CCS argues in a footnote that DeGuisto's Facebook\nmessages should be disregarded because they occurred outside of\nwork. But, as we have said before, \"Courts . . . permit evidence\nof non-workplace conduct to help determine the severity and\npervasiveness of the hostility in the workplace as well as to\nestablish that the conduct was motivated by gender.\" Crowley v.\nL.L. Bean, Inc., 303 F.3d 387, 409 (1st Cir. 2002). Furthermore,\nit is not clear at all that Facebook messages should be considered\nnon-workplace conduct where, as here, they were about workplace\nconduct, including Dever's reports and rumors, and were sent over\nsocial media by an officer who worked in Roy's workplace. Cf.\nFeminist Majority Found. v. Hurley, 911 F.3d 674, 688-89 (4th Cir.\n2018) (\"[W]e cannot conclude that [a university] could turn a blind\neye to the sexual harassment that pervaded and disrupted its campus\nsolely because the offending conduct took place through\ncyberspace.\").\n\n\n - 19 -\n\f First, there is no doubt that a jury could find that\n\nParrow calling Roy a \"bitch\" was connected to her sex. It does\n\nnot matter whether Parrow was motivated by \"anger resulting from\n\nthe breakup of their previous romantic relationship,\" as the\n\ndistrict court emphasized. Id. at 168. To distinguish between\n\nharassment motivated by sex and harassment motivated by anger after\n\na break up, as the district court did, \"establishes a false\n\ndichotomy\" between Roy's sex and Parrow's romantic interest in\n\nher, which are \"inextricably linked.\" Forrest v. Brinker Int'l.\n\nPayroll Co., 511 F.3d 225, 229 (1st Cir. 2007). Regardless of\n\nParrow's particular and subjective motives, \"the use of sexually\n\ndegrading, gender-specific epithets, such as . . . 'bitch,' . . .\n\nconstitute[s] harassment based upon sex.\" Id.\n\n Second, a reasonable jury could infer that the comment\n\nabout Roy's \"ass\" was made in part because of her sex, given the\n\ncontext. See, e.g., Tang v. Citizens Bank, N.A., 821 F.3d 206,\n\n216 (1st Cir. 2016) (considering context, use of word \"ass\" was\n\nbased on sex); McGullam v. Cedar Graphics, Inc., 609 F.3d 70, 85\n\n(2d Cir. 2010) (Calabresi, J., concurring) (viewing comment by\n\nmale co-worker about plaintiff's \"big fat ass\" to be based on sex).\n\nThat context includes Turner, Parrow, and Dever sexualizing Roy\n\nand officers like Snow emphasizing aspects of her appearance, such\n\nas her blonde hair.\n\n\n\n\n - 20 -\n\f Third, it was error for the district court to hold at\n\nsummary judgment that Roy's allegations of retaliatory conduct\n\nwere not sex-based. A jury could find on one of several theories\n\nthat officers put Roy at risk, treated her rudely, ignored her,\n\ndemeaned her, and filed reports complaining about her not only\n\nbecause of her whistleblowing but also because of her sex.\n\n A jury could see this degrading treatment as a form of\n\nsex-based discrimination. Responding disrespectfully or\n\ndismissively to women's requests, complaining about women's\n\nperformance, and ignoring or ostracizing women are paradigmatic\n\nways to communicate to women that they are less worthy than or\n\nless welcome than men in a workplace. See O’Rourke, 235 F.3d at\n\n730. Indeed, several of the remarks showed this sort of\n\nstereotyping (e.g., a woman's \"job is to be at home\"). A jury\n\ncould also find that the retaliation was motivated in part by sex\n\nbecause it was committed alongside overtly sexual harassment. See\n\nMarrero v. Goya of P.R., Inc., 304 F.3d 7, 20 (1st Cir. 2002)\n\n(considering sex-neutral conduct by a supervisor with his\n\nexplicitly sexual conduct); Rosario v. Dep't of Army, 607 F.3d\n\n241, 248 (1st Cir. 2010) (similar); Kaytor v. Elec. Boat Corp.,\n\n609 F.3d 537, 548 (2d Cir. 2010) (justifying this inference). Roy\n\nalleges that Turner, Dever, Snow, and Parrow, retaliated against\n\nher after her whistleblowing while also directing at her blatantly\n\nsexual comments, rumors, jokes, and epithets. As the Equal\n\n\n - 21 -\n\fOpportunity Employment Commission (EEOC), amicus here, urging\n\nreversal, says, \"it is impossible to tease out\" as a matter of law\n\n\"how much of the officers' conduct was based solely on Roy's\n\nwhistleblowing and how much was also infected with sex\n\ndiscrimination.\" This is an issue for the jury.\n\n Severity and pervasiveness were also issues for the\n\njury, and the district court erred in deciding as a matter of law\n\nthat the conduct was neither severe nor pervasive. Roy, 321 F.\n\nSupp. 3d at 168. A plaintiff need only show that her work\n\nenvironment was severe or that it was pervasive, Burns v. Johnson,\n\n829 F.3d 1, 18 (1st Cir. 2016), and a jury could find for Roy on\n\neither theory, or on both.\n\n On severity, a jury could find Turner's practice of\n\nabandoning his post so that Roy was left alone with inmates severe\n\nenough, on its own, to alter the terms and conditions of her\n\nemployment. Turner was assigned to the medical clinic to protect\n\nRoy and the other medical staff from inmates who were considered\n\ndangerous, and his absences placed Roy at risk of serious physical\n\nharm. Conduct that places a plaintiff in this sort of peril is\n\nsevere for purposes of a hostile work environment claim. See\n\nPatton v. Keystone RV Co., 455 F.3d 812, 818 (7th Cir. 2006)\n\n(holding that conduct that places the plaintiff in reasonable fear\n\nof serious physical harm suffices to show constructive discharge\n\nunder Title VII, a more difficult showing than severity); see also,\n\n\n - 22 -\n\fe.g., Gerald v. Univ. of P.R., 707 F.3d 7, 18 (1st Cir. 2013)\n\n(finding physically threatening behavior severe); Harris, 510 U.S.\n\nat 23 (including physically threatening behavior among indicators\n\nof a hostile work environment).\n\n On pervasiveness, there is evidence that Roy was\n\nsubjected to Turner's persistent derision and to several officers'\n\n\"daily\" retaliatory treatment, escalating from July to September\n\nof 2014. This environment was punctuated with the potentially\n\nhumiliating episodes involving Dever and Parrow. A jury could\n\nreasonably view this as frequent abuse and as a pattern of\n\nhostility, rather than as intermittent, isolated harassment. See,\n\ne.g., Tang, 821 F.3d at 217 (finding four incidents plus the\n\nplaintiff's allegation that the harassment occurred \"[e]very time\"\n\nthe harasser \"had a chance\" could be pervasive); Flood v. Bank of\n\nAm. Corp., 780 F.3d 1, 13 (1st Cir. 2015) (describing treatment by\n\nmultiple co-workers as a pattern of abuse); Hernandez-Loring v.\n\nUniversidad Metropolitana, 233 F.3d 49, 55 (1st Cir. 2000)\n\n(reversing entry of summary judgment on hostile work environment\n\nclaim based on two incidents and allegation that plaintiff was\n\n\"repeatedly asked [on] dates\").\n\n Finally, there is other evidence supporting Roy's claim\n\nof a hostile work environment. That officers complained about Roy\n\nand that she requested a transfer in mid-September could permit a\n\njury to find that the harassment was \"detract[ing] from [Roy's]\n\n\n - 23 -\n\fjob performance\" and \"discourag[ing] [her] from remaining on the\n\njob,\" both telltale signs of a \"discriminatorily abusive\"\n\nenvironment. Harris, 510 U.S. at 22.\n\n III.\n\n A jury could find that Roy endured a hostile work\n\nenvironment, so we proceed to evaluate the liability of each\n\ndefendant. We begin with the claims against MDOC, turn next to\n\nCCS, and finally to Ross and Bouffard.\n\nA. Claims against MDOC under Maine Law\n\n Roy alleges first that MDOC interfered with her MHRA-\n\nprotected right to work free from sex discrimination in violation\n\nof MHRA § 4633(2). Second, she alleges that MDOC's revocation of\n\nher security clearance was an act of retaliation, unlawful under\n\n§ 4633(1), for her MHRA-protected complaints about sexual\n\nharassment, about officers requesting inmate medical information\n\nmade confidential by statute, about officers ignoring her requests\n\nto bring inmates to the clinic, about officers leaving her alone\n\nwith potentially dangerous inmates, and about retaliation because\n\nof her reporting activity.5\n\n We address first whether § 4633 of the MHRA allows suits\n\nagainst non-employer third parties for discrimination that occurs\n\n\n\n 5 The MHRA makes it unlawful to discriminate in any \"matter\ndirectly or indirectly related to employment\" based on sex or on\ncertain whistleblower activity. Me. Rev. Stat. tit. 5,\n§ 4572(1)(A). Protected whistleblower activity is defined in the\n\n\n - 24 -\n\fin a workplace.6 The district court concluded, relying on the\n\nMaine Law Court's decision in Fuhrmann v. Staples Office Superstore\n\nEast, Inc., 58 A.3d 1083 (Me. 2012), that the MHRA allows\n\nemployment discrimination actions against employers only, and\n\nnever against \"non-employer entit[ies]\" like MDOC. Roy, 321 F.\n\nSupp. 3d at 164. We disagree and hold, based on the text and\n\nhistory of § 4633, that the provision allows Roy's claims.7\n\n 1. Section 4633\n\n The text of § 4633 encompasses both of Roy's claims\n\nagainst MDOC. Section 4633 reads:\n\n (1) Retaliation. A person may not\n discriminate against any individual because\n that individual has opposed any act or\n practice that is unlawful under this\n Act . . . .\n (2) Interference, coercion, or intimidation.\n It is unlawful for a person to coerce,\n intimidate, threaten or interfere with any\n individual in the exercise or enjoyment of the\n\n\n\nWhistleblower Protection Act (MWPA), which does not provide a cause\nof action separate from the MHRA's. See Me. Human Rights Comm'n\nv. Me. Dep't of Def. & Veterans' Servs., 627 A.2d 1005, 1007 n.8\n(Me. 1993).\n 6 At a hearing on the motions for summary judgment, the\ndistrict court asked the parties whether this question should be\ncertified to the Maine Law Court. See Transcript of Oral Argument\nat 51-54, Roy, 321 F. Supp. 3d 155 (No. 16-cv-00383). Roy's\ncounsel supported certification while MDOC did not, and the\ndistrict court ultimately decided not to certify the question. In\ntheir briefs on appeal, neither party has asked us to do so.\n 7 We do not have before us a claim against an individual\nsupervisor employed by the plaintiff's employer and take no\nposition on whether § 4633 would allow such a claim.\n\n\n - 25 -\n\f rights granted or protected by this\n Act . . . .\n\nMe. Rev. Stat. Ann. tit. 5, § 4633(1)-(2). This language\n\nprohibits any \"person\" 8 from hindering -- by \"[i]nterference,\n\ncoercion, or intimidation\" or by \"[r]etaliation\" -- the exercise\n\nof any \"rights granted or protected\" by the MHRA. Me. Rev. Stat.\n\nAnn. tit. 5, § 4633.\n\n The legislative history of § 4633 also supports our\n\nreading. The Maine legislature's summary of § 4633 at its\n\nenactment states that the provision \"makes clear that retaliation,\n\ninterference, coercion and intimidation . . . by any person\n\nbecause that individual engaged in activities related to rights\n\nprotected by the [MHRA] is a violation of the Act.\" Me. Pub. L.\n\n1993, ch. 303 § 3, Summary.\n\n Further, Maine's Human Rights Commission (MHRC), the\n\nagency that administers the MHRA, has long interpreted § 4633 to\n\nallow claims like Roy's against third parties whose actions impair\n\nworkers' MHRA-protected rights to be free from workplace\n\ndiscrimination. Indeed, in Maine Human Rights Comm'n v.\n\nSaddleback, Inc., No. CV-06-219, 2008 WL 6875449 (Me. Super. Ct.\n\nOct. 31, 2008), the Maine Superior Court agreed with the MHRC that\n\nSaddleback, a ski resort, violated § 4633 in demanding that a\n\n\n 8 MDOC is a \"person\" under the MHRA. See Me. Rev. Stat.\nAnn. tit. 5, § 4553(7) (defining \"person\" to \"include[] the State\nand all agencies thereof\").\n\n\n - 26 -\n\fconstruction contractor fire one of its employees because the\n\nemployee had reported safety violations at a Saddleback work site.\n\n As Saddleback makes clear, there is a key distinction\n\nbetween § 4633 and § 4572, the MHRA provision that prohibits\n\nunlawful employment discrimination. Section 4572 addresses\n\ndiscriminatory conduct by an employer, or employees or agents of\n\nthe employer, that occurs within the scope of a traditional\n\nemployment relationship. Section 4633 targets actions by third\n\nparties (not the employer, its employees, or agents) that hinder\n\nemployees' MHRA-protected rights to work free from discrimination.\n\n MDOC argues and the district court agreed that the Law\n\nCourt's decision in Fuhrmann precludes this reading of § 4633.\n\nNot so. In Fuhrmann, a Staples salesperson had her longstanding\n\nwork hours changed after she reported possible tax fraud at her\n\nstore. 58 A.3d at 1088. She sued Staples and her individual\n\nsupervisors, alleging retaliation under § 4572 of the MHRA for\n\nwhistleblower activity defined in § 833(1)(A) of the Maine\n\nWhistleblower Protection Act (MWPA). Id. at 1088-89. The Law\n\nCourt dismissed the claims against the individual supervisors,\n\nholding that \"[p]ursuant to either [the MHRA's or the MWPA's]\n\nstatutory definition of 'employer,' there is no individual\n\nsupervisor liability for employment discrimination.\" Id. at 1098.\n\n Fuhrmann does not control here. The issue before the\n\nLaw Court there was individual supervisor liability for a claim\n\n\n - 27 -\n\funder § 4572, and neither Fuhrmann's holding nor its reasoning\n\ntranslate to cases like this one involving third-party liability\n\nunder § 4633. Fuhrmann never mentioned § 4633, and several\n\nsignificant differences between § 4572 and § 4633 undercut MDOC's\n\nargument that Fuhrmann's holding extends to bar Roy's claims.\n\nFirst, § 4572 prohibits discrimination by an \"employer,\" and what\n\nFuhrmann interpreted was the MHRA's definition of that term. 58\n\nA.3d at 1094. In contrast, § 4633 prohibits discrimination by any\n\n\"person.\" Second, § 4633 appears in the miscellaneous section of\n\nthe MHRA, while Fuhrmann interpreted provisions in the MHRA's\n\nemployment discrimination section. Third, the provisions have\n\ndifferent histories, and the enactment of § 4633 more than twenty\n\nyears after § 4572 is a strong indication that the provisions have\n\ndifferent intents.\n\n Nevertheless, the district court reasoned that allowing\n\nRoy's § 4633 suit \"contradicts Fuhrmann's central\n\nrationale -- that the MHRA intends to hold employers liable for\n\nemployment discrimination.\" Roy, 321 F. Supp. 3d at 163. But\n\nFuhrmann assessed only whether the legislature intended to allow\n\nsuits against individual supervisors, not what it intended about\n\nsuits against non-employer third parties. To the Fuhrmann court,\n\nthe MHRA's incorporation of vicarious liability indicated a\n\nlegislative intent to hold employers, but not supervisors as\n\nindividuals, liable for supervisors' discriminatory conduct.\n\n\n - 28 -\n\fFuhrmann, 58 A.3d at 1097; see also Me. Rev. Stat. Ann. tit. 5,\n\n§ 4553(10)(E) (discussing vicarious liability). But vicarious\n\nliability is not relevant to claims like Roy's against third\n\nparties not alleged to be agents of the employer. Similarly,\n\nFuhrmann concluded that the remedies listed in the remedial\n\nprovision that applies to both § 4572 and § 4633 violations were\n\ndifficult to apply \"to individual supervisors in practice.\" 58\n\nA.3d at 1098. Fuhrmann said nothing about the application of the\n\nlisted remedies to third-party entities and did not explore the\n\nremedial provision's prefatory statement that \"remedies may\n\ninclude, but are not limited to\" those listed. Me. Rev. Stat.\n\nAnn. tit. 5, § 4613(2)(B). The district court erred in holding\n\nthat Fuhrmann bars Roy's claims against MDOC.\n\n 2. MDOC's Alternative Argument for Summary Judgment\n\n MDOC also argues that Roy has not offered evidence\n\nsufficient to push her § 4633 interference and retaliation claims\n\npast summary judgment. MDOC is plainly wrong.\n\n First, on the § 4633(2) interference claim, MDOC\n\ncontends only that we may affirm the grant of summary judgment\n\nbecause there was no hostile work environment. But, as explained,\n\na reasonable jury could conclude that Roy was subjected to a\n\nhostile work environment because of her sex in violation of the\n\nMHRA's protections against \"unlawful employment discrimination.\"\n\nSee Me. Rev. Stat. Ann. tit. 5, § 4572(1)(A).\n\n\n - 29 -\n\f Second, because we reject MDOC's arguments that Roy's\n\nconduct was not protected activity under the MHRA and the MWPA and\n\nthat it had non-pretextual reasons for revoking her security\n\nclearance, Roy's retaliation claim may go to the jury. MDOC says\n\nthat the facts show that Roy did not engage in protected activity.\n\nBut, with respect to Roy's complaints about the hostile work\n\nenvironment, MDOC appears to contend only that the reports are not\n\nprotected because the evidence did not suffice to show that the\n\nwork environment was hostile on the basis of sex. That contention\n\nis mistaken. Similarly, as we will explain with respect to CCS's\n\nliability under the MWPA, the arguments advanced by CCS and, by\n\nreference, MDOC, do not preclude Roy's other complaints from being\n\nfound to be protected whistleblower activity because they relate\n\nto potential violations of medical privacy laws, as well as to\n\nhealth and safety risks at the prison. See id. § 4572(1) (making\n\nunlawful discrimination based on whistleblower activity); Me. Rev.\n\nStat. Ann. tit. 26, § 833(1)(A)-(B) (defining protected\n\nwhistleblower activity as reporting \"a violation of a [state or\n\nfederal] law or rule\" or \"a condition or practice that would put\n\nat risk the health or safety of . . . [an] individual.\").\n\n MDOC next argues that Roy cannot show that MDOC's stated\n\nreasons for revoking the security clearance -- Roy's statements\n\nabout and her failure to file a report on the September 26\n\nincident -- were pretext for retaliation. But, based on numerous\n\n\n - 30 -\n\ffacts, of which we mention only a few, a jury could conclude that\n\nthose reasons were pretext. A jury could credit Ross's statements\n\nthat he was frustrated about Roy's involvement in so many\n\ninvestigations and that he wanted to \"gate-close\" Roy. And, even\n\nif the jury were to credit MDOC's stated reasons over Ross's\n\nstatements, a jury could find that Roy's actions did not jeopardize\n\nthe security of the prison and could not justify, on their own,\n\nthe revocation of her clearance.\n\n Further, there is the glaringly differential treatment\n\nof Roy and Reed-Chapman. Although Reed-Chapman, who had never\n\ncomplained before, also told the captain that she and Roy were\n\nunattended for approximately fifteen minutes, and then put that\n\nimpression in writing, in an Incident Report, MDOC did not revoke\n\nReed-Chapman's security clearance. Reed-Chapman did file a\n\nreport, as the captain had requested. But a jury could believe\n\nRoy's assertion that she had been told that Ross did not want her\n\nto file more reports. Or, a jury could decide that MDOC did not\n\nactually need a report from Roy once it had Reed-Chapman's.\n\n In sum, Roy's § 4633 interference and retaliation claims\n\ncan proceed to trial.\n\nB. Claims against CCS under Title VII and Maine Law\n\n Roy has also produced sufficient evidence for her sexual\n\nharassment and retaliation claims against CCS to reach a jury.\n\n\n\n\n - 31 -\n\f 1. Hostile Work Environment Claims against CCS\n\n An employer like CCS can be liable for a hostile work\n\nenvironment created by third parties like MDOC's employees. See\n\nMedina-Rivera v. MVM, Inc., 713 F.3d 132, 137 (1st Cir. 2013);\n\nRodriguez-Hernandez v. Miranda-Velez, 132 F.3d 848, 854-55 (1st\n\nCir. 1998) (using ratification theory); see also, e.g., Gardner v.\n\nCLC of Pascagoula, LLC, 894 F.3d 654, 657 (5th Cir. 2018) (\"Because\n\nthe ultimate focus of Title VII liability is on the employer's\n\nconduct[,] . . . nonemployees can be the source of the\n\nharassment.\"); Beckford v. Dep't of Corr., 605 F.3d 951, 957 (11th\n\nCir. 2010) (\"It is well established that employers may be liable\n\nfor failing to remedy the harassment of employees by third parties\n\nwho create a hostile work environment.\").9 In these situations,\n\na finding that the harassment was so severe or pervasive as to\n\nalter the terms and conditions of the plaintiff's employment is\n\nnot by itself enough to make the employer liable. Liability for\n\na discriminatory environment created by a non-employee \"depends on\n\nwhether the employer knew or should have known of the hostile work\n\nenvironment and took reasonable measures to try to abate it.\"\n\nGardner, 894 F.3d at 663; see also, e.g., Freeman v. Dal-Tile\n\n\n\n 9 Federal law guides interpretation of the MHRA, Cookson\nv. Brewer Sch. Dep't, 974 A.2d 276, 281 (Me. 2009), and we consider\nthe MHRA to be parallel with Title VII here, cf. Watt, 969 A.2d at\n904 (noting that the MHRA standard for employer liability for\nco-worker harassment has developed concurrently with federal law).\n\n\n - 32 -\n\fCorp., 750 F.3d 413, 423 (4th Cir. 2014) (holding that employer\n\nliability depends on employer knowledge and whether the employer\n\nresponse was \"reasonably calculated to end the harassment\"\n\n(internal quotation marks omitted)). Circuit courts addressing\n\nthe issue of employer liability for third-party harassment have\n\nuniformly applied this rule.10\n\n The district court never discussed whether there was a\n\nbasis for CCS's liability under Title VII and the MHRA, and CCS\n\ndoes not argue on appeal that there is no legal basis. 11 We\n\nconsider the issue, however, because of the unique nature of Roy's\n\nworkplace, where workers employed by multiple entities shared a\n\nworksite that did not belong to Roy's employer and where the\n\norganizational relationships afforded non-employers influence over\n\nemployment conditions and decisions. See Dallan F. Flake,\n\nEmployer Liability for Non-Employee Discrimination, 58 B.C. L.\n\n\n\n 10 See Gardner, 894 F.3d at 657; Freeman, 750 F.3d at 423;\nSumma v. Hofstra Univ., 708 F.3d 115, 124 (2d Cir. 2013); Beckford,\n605 F.3d at 958; Freitag v. Ayers, 468 F.3d 528, 538 (9th Cir.\n2006); Dunn v. Washington Cty. Hosp., 429 F.3d 689, 691 (7th Cir.\n2005); Slayton v. Ohio Dep't of Youth Servs., 206 F.3d 669, 677\n(6th Cir. 2000); Lockard v. Pizza Hut, Inc., 162 F.3d 1062, 1073-\n74 (10th Cir. 1998); Crist v. Focus Homes, Inc., 122 F.3d 1107,\n1111 (8th Cir. 1997); see also 29 C.F.R. 1604.11(e) (stating that\nemployer can be liable for harassment by third parties \"where the\nemployer . . . knows or should have known of the conduct and fails\nto take immediate and appropriate corrective action.\").\n 11 CCS did argue in the district court that there was no\nbasis for employer liability because it \"took prompt and effective\naction\" when it learned of Roy's complaints.\n\n\n - 33 -\n\fRev. 1170, 1178-81 (2017) (stating that such organizational\n\ncomplexity is increasingly common and analyzing the implications\n\nfor third-party harassment claims).\n\n Many third-party harassment cases involve less complex\n\narrangements: common are cases involving retail customers or\n\nhealthcare facility patients who harass employees at a store or\n\nhealthcare facility operated by the employer. See, e.g., Lockard\n\nv. Pizza Hut, Inc., 162 F.3d 1062, 1067 (10th Cir. 1998)\n\n(customers); Gardner, 894 F.3d at 657 (patient). But those cases\n\ndo not purport to limit an employer's duty to those situations.\n\nIn our view, the duty to try to protect employees from sexual\n\nharassment exists in other environments, even in environments that\n\nare, like MDOC's prison, \"inherently dangerous\" and difficult to\n\ncontrol. Freitag v. Ayers, 468 F.3d 528, 539 (9th Cir. 2006)\n\n(\"[E]ven in an inherently dangerous working environment, the focus\n\nremains on whether the employer took reasonable measures to make\n\nthe workplace as safe as possible.\" (quotation marks omitted));\n\nsee also Beckford, 605 F.3d at 958-59; Gardner, 894 F.3d at 663-\n\n64 (applying this to nursing homes with diminished-behavioral-\n\ncapacity patients). CCS had an obligation to try to protect Roy\n\nfrom a hostile work environment, and the reasonableness rule\n\nconsistently applied in third-party harassment claims is adequate\n\n\n\n\n - 34 -\n\fto account for the complexities of her workplace.12 Cf. Beckford,\n\n605 F.3d at 959 (holding this test adequate to account for the\n\ncomplexities of a work environment in a prison).\n\n Ultimately, a jury must decide Roy's hostile work\n\nenvironment claims against CCS. CCS plainly knew of the\n\nharassment.13 The reasonableness of CCS's response is an issue\n\nfor the jury. Although CCS did not employ the corrections officers\n\nor manage the prison, CCS was not helpless to influence the\n\nofficers, their supervisors, or the operation of the prison's\n\nmedical facility. CCS had formal and informal mechanisms for\n\nraising Roy's complaints and for pressing for remedies. This\n\ninfluence over the environment and the officers is evident in\n\ninstances when MDOC responded to CCS's efforts by investigating\n\nand acting, as with Parrow. But CCS did not always use the\n\navailable mechanisms. It forwarded some but not all of Roy's\n\ncomplaints. And when MDOC's responses were dismissive or\n\n\n\n 12 We do not address whether this test applies to all other\narrangements. There may be situations that require separate\nconsideration of an employer's level of control or authority over\nthe environment or over the entity that employs the harassers.\nSee 29 C.F.R. § 1604.11(e) (stating that the EEOC will also\nconsider \"the extent of the employer's control and any other legal\nresponsibility which the employer may have with respect to the\nconduct of such non-employees.\"); see also Summa, 708 F.3d at 124-\n25 (considering whether level of control was sufficient to support\nliability).\n 13 Because this is a case of actual knowledge, we do not\nexplore the \"should have known\" element.\n\n\n - 35 -\n\finadequate, CCS often did nothing. Even when Roy's physical\n\nsafety was threatened by Turner's and King's absences from the\n\nclinic when inmates were present, CCS either did not refer Roy's\n\ncomplaints or accepted MDOC's inaction or arguably inappropriate\n\nresponses, without question. See Lockard, 162 F.3d at 1075\n\n(finding basis for liability in part on employer's failure to\n\naddress a \"potentially dangerous situation\" created by non-\n\nemployees). To give just one example, there is no evidence that\n\nCCS suggested steps like reassigning Turner, disciplining him, or\n\nadding additional layers of security. See Beckford, 605 F.3d at\n\n959-60 (identifying possible measures for mitigating harassment of\n\ncorrections officers by inmates); Gardner, 894 F.3d at 663 (giving\n\nexamples of mitigation sufficient to avoid liability in a case of\n\nharassment by a nursing home patient).\n\n Apart from what CCS did or could have done to influence\n\nMDOC is the issue of what CCS could have done on its own. A jury\n\ncould see as unreasonable CCS's changing story about and seeming\n\nfailure to consider an obvious mitigating measure, and one\n\nrequested by Roy -- a transfer.\n\n Entry of summary judgment was error. Roy's hostile work\n\nenvironment claims against CCS should go to a jury.\n\n 2. Retaliation Claims against CCS\n\n In granting summary judgment for CCS on Roy's\n\nretaliation claims under Title VII and Maine law, the district\n\n\n - 36 -\n\fcourt ruled that Roy's complaints were not protected activity\n\nbecause, in its view, CCS lacked \"the ability and authority to\n\ncorrect\" the complained-of violations. Roy, 321 F. Supp. 3d at\n\n169. We reverse, for errors of law and fact, addressing first the\n\nclaims under Title VII and the MHRA that CCS retaliated against\n\nRoy for complaints about the hostile work environment and second\n\nthe whistleblower retaliation claim under the MHRA and the MWPA.\n\n a. Title VII and MHRA Retaliation\n\n The Maine case relied on by the district court for its\n\ndefinition of protected activity, Hickson v. Vescom Corp., 87 A.3d\n\n704 (Me. 2014), interpreted § 833(2) of the MWPA, and does not\n\ndefine protected activity for Roy's Title VII or MHRA claims. See\n\n87 A.3d at 710 (citing Me. Rev. Stat. Ann. tit. 26, § 833(2)).\n\nUnder both Title VII and the MHRA, a jury could find that Roy's\n\ncomplaints were protected because they reported activity that she\n\nhad a reasonable, good faith belief violated those statutes. See\n\nFantini v. Salem State Coll., 557 F.3d 22, 32 (1st Cir. 2009)\n\n(citing 42 U.S.C. § 2000e-3).\n\n CCS does not defend the district court's rationale. It\n\nurges us to affirm the entry of summary judgment on the grounds\n\nthat Roy cannot show that her complaints were what caused her\n\ntermination and cannot show that CCS's neutral reason for firing\n\nher -- MDOC's revocation of the security clearance -- was pretext.\n\n\n\n\n - 37 -\n\fFactual disputes here require a jury to decide causation and\n\npretext.14\n\n The causation element of a Title VII retaliation claim\n\nis not satisfied by evidence that retaliation was one motivating\n\nfactor in the adverse action. See Nassar, 570 U.S. at 362-63.\n\nInstead, Roy must show \"but-for\" causation -- that is, that she\n\n\"would not have [been terminated] in the absence of the\" protected\n\ncomplaints. Id. at 360. Emphasizing this standard, CCS argues\n\nthat the revocation of the clearance was the sole but-for cause of\n\nRoy's termination.\n\n Factual disputes preclude summary judgment on this\n\ntheory of causation. To start, CCS and Roy dispute whether the\n\nrevocation of the security clearance meant that CCS could no longer\n\nemploy Roy. If CCS could have transferred Roy to one of its other\n\nfacilities in Maine, as Roy says, then a jury could find that\n\nretaliatory animus was a but-for cause of CCS's decision to fire\n\nher rather than transfer her. Significantly, CCS has not produced\n\nevidence that a transfer was impossible. CCS does not even deny\n\nthat a transfer was possible, emphasizing instead that the burden\n\n\n\n\n 14 The familiar burden-shifting framework from McDonnell-\nDouglas Corp. v. Green, 411 U.S. 792 (1973), applies. The elements\nother than causation and pretext are easily settled in Roy's favor:\nAs we have said, Roy engaged in protected activity. She also\nsuffered an adverse employment action when she was fired.\n\n\n - 38 -\n\fwas on Roy to ask about other positions. But Roy did so, in mid-\n\nSeptember.\n\n Alternatively, a jury could conclude that MDOC's\n\nretaliatory animus caused the revocation of the security clearance\n\nand, in turn, caused Roy's termination. A third party's\n\nretaliatory or discriminatory animus can cause an employer's\n\nadverse action where, as a jury might find here, the employer knew\n\nthat animus motivated the third-party's actions or demands and\n\nsimply accepted those actions or demands. Cf. Rodriguez-\n\nHernandez, 132 F.3d at 854-55 (holding that customers'\n\ndiscriminatory preferences, where ratified by the employer, can\n\ncause Title VII discrimination); Tamosaitis v. URS Inc., 781 F.3d\n\n468, 482-83 (9th Cir. 2015) (holding that client's demand to remove\n\na whistleblowing employee from a project caused employer's adverse\n\naction under an analogous statute).\n\n Similar facts would permit a jury to find that CCS's\n\nstated reason was pretext for a retaliatory motive. See Billings\n\nv. Town of Grafton, 515 F.3d 39, 55 (1st Cir. 2008) (quoting\n\nHodgens v. Gen. Dynamics Corp., 144 F.3d 151, 168 (1st Cir. 1998))\n\n(explaining that pretext can be shown through facts that expose\n\n\"weaknesses, implausibilities, inconsistencies, incoherencies, or\n\ncontradictions in the employer's proffered legitimate reasons\").\n\nWe mention just a few. The facts about the possibility of transfer\n\nweaken CCS's insistence that the security clearance was the sole\n\n\n - 39 -\n\fand actual reason for the firing. That CCS put Roy on leave\n\n(telling her it was temporary) immediately after the September 26\n\nmeeting, a week before the clearance was revoked and her employment\n\nwas terminated, could undermine CCS's claim that it harbored no\n\ndesire to retaliate. Or a jury could infer from CCS's failure to\n\ndiscipline Reed-Chapman that CCS did not find discipline-worthy\n\nthe conduct that MDOC says led to the revocation of Roy's\n\nclearance. Yet CCS did not try to stop MDOC from using that\n\nconduct to \"gate-close\" Roy. To the contrary, CCS immediately,\n\nand apparently without question, fired Roy once she lost her\n\nclearance. A jury should evaluate the issue of pretext.\n\n b. Whistleblower Retaliation\n\n A jury should also decide Roy's whistleblower\n\nretaliation claim. As just discussed, whether Roy's complaints\n\ncaused her termination and whether CCS's stated reason is pretext\n\nare triable issues. The jury, if it sees a need to, can tease\n\napart the effects of the two sets of complaints -- those about\n\nsexual harassment and those about officers leaving Roy alone with\n\ninmates, asking for confidential inmate medical information, and\n\nrefusing to bring inmates to the clinic.\n\n Further, a jury could deem Roy's whistleblowing\n\ncomplaints protected activity, as they relate to potential\n\nviolations of medical privacy laws and to health and safety risks\n\nat the prison. See id. § 4572(1) (making unlawful discrimination\n\n\n - 40 -\n\fbased on protected whistleblower activity); Me. Rev. Stat. Ann.\n\ntit. 26, § 833(1)(A)-(B) (defining protected whistleblower\n\nactivity as reporting \"a violation of a [state or federal] law or\n\nrule\" or \"a condition or practice that would put at risk the health\n\nor safety of . . . [an] individual.\"). The district court erred\n\nin ruling that Roy's complaints were unprotected because CCS\n\nlacked, under Hickson, \"the ability and authority to correct\" the\n\ncomplained-of violations. Roy, 321 F. Supp. 3d at 169 (quoting\n\nHickson, 87 A.3d at 711).\n\n CCS argues, following the district court's reading, that\n\nHickson, and the MWPA provision it interpreted, require evidence\n\nof direct authority to correct the violations, as the employee in\n\nHickson, who complained about safety at a mill, was employed by\n\nthe company directly responsible for mill safety. 87 A.3d at 711.\n\nYet Hickson nowhere limited its interpretation of § 833(2) to those\n\nfacts. Nor does the language of the provision suggest that the\n\nemployer's corrective authority must be direct. It states that\n\nwhistleblower protection applies to an employee who \"has first\n\nbrought the alleged violation, condition or practice to the\n\nattention of a person having supervisory authority with the\n\nemployer and has allowed the employer a reasonable opportunity to\n\ncorrect that violation, condition or practice.\" Me. Rev. Stat.\n\nAnn. tit. 26, § 833(2). We see no reason why a jury could not\n\nfind \"ability and authority to correct,\" Hickson, 87 A.3d at 711,\n\n\n - 41 -\n\feven if that control is indirect. We have already established\n\nthat CCS had both formal and informal mechanisms for influencing\n\nMDOC, its officers, and the operation of the prison. Roy's\n\nwhistleblower retaliation claim should go to the jury.\n\nC. Claims against Ross and Bouffard under § 1983\n\n Roy alleges that Bouffard and Ross, the top prison\n\nofficials, failed to stop prison staff from sexually harassing her\n\nin violation of the Equal Protection Clause15 and that Bouffard and\n\nRoss revoked her security clearance because of her complaints, in\n\nviolation of the First Amendment. Qualified immunity protects\n\nRoss and Bouffard from suit because reasonable officials could\n\nhave believed \"on the[se] facts\" that no equal protection or First\n\nAmendment violation occurred.16 Dirrane v. Brookline Police Dep't,\n\n315 F.3d 65, 69 (1st Cir. 2002).\n\n Supervisors like Ross and Bouffard are liable under the\n\nEqual Protection Clause for a hostile work environment created by\n\ntheir subordinates in state government only if their \"link\" to the\n\n\n\n 15 Roy does not raise on appeal a second equal protection\nclaim, also rejected by the district court, that Bouffard, Ross,\nand the officers retaliated against her for complaining about the\nharassment. Roy, 321 F. Supp. 3d at 170.\n 16 The district court did not reach the qualified immunity\ndefense on the equal protection claim, holding simply that that\nRoy could not establish an equal protection violation. Roy, 321\nF. Supp. 3d at 170. On the First Amendment claim, the district\ncourt held that, even if there were a constitutional violation,\nthe officers would have qualified immunity. Id. at 173.\n\n\n - 42 -\n\funlawful harassment was one of \"'supervisory encouragement,\n\ncondonation, or acquiescence,' or 'gross negligence amounting to\n\ndeliberate indifference.'\" Lipsett, 864 F.2d at 902 (quoting\n\nBohen v. City of East Chicago, 799 F.2d 1180, 1189 (7th Cir.\n\n1986)). Two First Circuit cases apply this principle. In the\n\nsingle case finding supervisory liability under § 1983 for sexual\n\nharassment, the defendants knew of severe abuse but failed even to\n\ninvestigate. See id. at 890-93, 907. In the other case, which\n\nfound no supervisor liability, the defendant, the harasser's\n\nsupervisor, at first discouraged the plaintiff from filing a formal\n\ncomplaint but then actively encouraged her to do so. See Sanchez\n\nv. Alvarado, 101 F.3d 223, 225, 228-29 (1st Cir. 1996). Ross and\n\nBouffard's conduct falls somewhere between these guideposts.\n\nComplaints against Snow and Parrow were investigated and addressed\n\nwhile complaints about Turner, DeGuisto, and officers' retaliatory\n\nbehavior were not. \"[A]s is common where there is a lack of\n\nprecedent, this is not a case in which a reasonable officer must\n\nhave known that he was acting unconstitutionally.\" Dirrane, 315\n\nF.3d at 71 (footnote omitted).\n\n Ross and Bouffard also receive qualified immunity from\n\nthe First Amendment retaliation claim because reasonable officials\n\ncould have believed that revoking Roy's security clearance would\n\nnot violate the Constitution. To show a First Amendment\n\nviolation, one thing Roy must demonstrate is that she was speaking\n\n\n - 43 -\n\fas a private citizen on a matter of public concern.17 Complaints\n\nlike Roy's made to supervisors and public officials about sexual\n\nharassment and safety at public agencies can be protected citizen\n\nspeech on matters of public concern. See, e.g., Baron v. Suffolk\n\nCty. Sheriff's Dep't, 402 F.3d 225, 233 (1st Cir. 2005) (upholding\n\na jury verdict on a First Amendment claim by a corrections officer\n\nwho had complained internally about discrimination and operation\n\nof a prison); Campbell v. Galloway, 483 F.3d 258, 270 (4th Cir.\n\n2007) (holding that police officer's letter to police chief about\n\nsexual harassment was protected by the First Amendment). But we\n\ncannot say that a reasonable official must have known that Roy's\n\ncomplaints were constitutionally protected. Significantly, Roy\n\nonly complained internally. And, although the Supreme Court has\n\nestablished that form is never \"dispositive\" of the public concern\n\nquestion, Garcetti v. Ceballos, 547 U.S. 410, 420 (2006), it has\n\nsometimes seen a plaintiff's failure \"to inform the public\" about\n\nher concerns as cutting against First Amendment protection,\n\nConnick v. Myers, 461 U.S. 138, 148 (1983); see also, e.g., City\n\nof San Diego v. Roe, 543 U.S. 77, 84 (2004) (per curiam).\n\n\n 17 Roy must also show that her interests in speaking\noutweighed MDOC's interest in efficient public services, see\nPickering v. Board of Educ., 391 U.S. 563, 568 (1968), and that\nthe protected speech was a substantial or motivating factor in the\nadverse employment decision, see Mt. Healthy City Sch. Dist. Bd.\nEduc. v. Doyle, 429 U.S. 274, 287 (1977); see also, e.g., Decotiis\nv. Whittemore, 635 F.3d 22, 29-30 (1st Cir. 2011) (describing the\nwhole test).\n\n\n - 44 -\n\fReasonable officials in Ross and Bouffard's positions, then, could\n\nhave deemed Roy's complaints unprotected. As a result, even if\n\nRoy could ultimately make out a First Amendment violation, the\n\ndefendants receive qualified immunity.\n\n IV.\n\n We reverse summary judgment for MDOC and CCS and affirm\n\nsummary judgment for Ross and Bouffard. Costs are awarded to Roy.\n\n\n\n\n - 45 -\n[END_CASE]", "role": "user" } ]
4,585,305
Lauren MICELI, Plaintiff, Appellant, v. JETBLUE AIRWAYS CORP.; Mathew Bourgeois, Defendants, Appellees.
Miceli v. JetBlue Airways Corp.
2019-01-28
18-1345P
U.S. Court of Appeals for the First Circuit
{"judges": "Torruella, Selya, Lynch", "parties": "", "opinions": [{"author": "SELYA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1345\n\n LAUREN MICELI,\n\n Plaintiff, Appellant,\n\n v.\n\n JETBLUE AIRWAYS CORP.; MATHEW BOURGEOIS,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Richard G. Stearns, U.S. District Judge]\n\n\n Before\n\n Torruella, Selya, and Lynch,\n Circuit Judges.\n\n\n Christopher J. Trombetta and Law Office of Christopher J.\nTrombetta on brief for appellant.\n Samantha K. Abeysekera and Akerman LLP on brief for appellees.\n\n\n January 28, 2019\n\f SELYA, Circuit Judge. Plaintiff-appellant Lauren Miceli\n\nsued her quondam employer, JetBlue Airways Corp. (JetBlue), for\n\nhandicap discrimination and retaliation under Massachusetts state\n\nlaw.1 The appellant alleges that JetBlue fired her due to her\n\ndisability and not (as JetBlue maintains) because she flouted\n\ncompany policy on unexcused absences. She also alleges that\n\nJetBlue retaliated against her for filing a complaint with the\n\nMassachusetts Commission against Discrimination (MCAD). The\n\ndistrict court granted summary judgment in JetBlue's favor. See\n\nMiceli v. JetBlue Airways Corp., No. CV 16-12032, 2018 WL 1524539,\n\nat *6 (D. Mass. Mar. 28, 2018). Critical to the court's assessment\n\nwas the appellant's failure to use measures provided by JetBlue\n\nenabling an employee to challenge a suspension or termination.\n\nSee id. at *5.\n\n The appellant assigns error. Even when viewing the\n\nrecord in the light most favorable to the appellant, we detect no\n\nprobative evidence of discrimination or retaliation.\n\nConsequently, we affirm.\n\n\n\n\n 1\n The appellant's complaint named Mathew Bourgeois, JetBlue's\ninflight service manager, as a co-defendant. The parties and the\ndistrict court have treated JetBlue and Bourgeois as a unit. For\nease in exposition, then, we refer to JetBlue as if it were the\nsole defendant and appellee. Our decision, of course, binds all\nparties.\n\n\n - 2 -\n\fI. BACKGROUND\n\n We rehearse the facts \"in the light most agreeable to\n\nthe plaintiff, consistent with record support,\" Kouvchinov v.\n\nParametric Tech. Corp., 537 F.3d 62, 65 (1st Cir. 2008), and then\n\nrecount the travel of the case. We reserve \"more exegetic detail\n\nfor our analysis of the issues on appeal.\" Harrington v. Aggregate\n\nIndus. Ne. Region, Inc., 668 F.3d 25, 28 (1st Cir. 2012).\n\n Beginning in 2006, JetBlue employed the appellant as an\n\ninflight crew member, based in the Boston area. When hired, the\n\nappellant was given access to an employee handbook (the Blue Book),\n\nwhich outlined, inter alia, JetBlue's policies on attendance,\n\nleave, and reasonable accommodation. As her employment\n\nprogressed, the appellant began to suffer from health issues.\n\nWhile on duty in the fall of 2014, she experienced an ear injury.\n\nThe following spring, she was diagnosed through JetBlue's third-\n\nparty employee assistance program with post-traumatic stress\n\ndisorder (PTSD) and depression. The appellant sought and obtained\n\nleave with respect to these conditions under the Family and Medical\n\nLeave Act (FMLA), 29 U.S.C. § 2601.\n\n In administering its FMLA program, JetBlue contracts\n\nwith a third-party administrator, Metropolitan Life Insurance\n\nCompany (MetLife). JetBlue's protocol channels all matters\n\nregarding FMLA approval to MetLife. In order to obtain FMLA leave\n\nbased on an illness of her own, a crew member is required to\n\n\n - 3 -\n\ffurnish MetLife with substantiating documentation from her health\n\ncare provider (including a \"Certificate of Health Care Provider\"\n\nform). Unless such leave is granted, absences are denoted in the\n\ncrew member's schedule as \"unavailable for assignment\" (UNA).\n\n Under JetBlue's dependability guidelines policy, limned\n\nin a Blue Book supplement, UNA absences are assigned category codes\n\nand point values. The accrual of points within a twelve-month\n\nperiod triggers five stages of progressive guidance, culminating\n\nin an employment review upon the accumulation of twelve points.\n\nSuch a review may result in the crew member's termination.\n\n Starting in the fall of 2014, the appellant began to\n\naccrue UNA absences, which she traces to her health conditions.\n\nOn February 7, 2015, she received an initial progressive guidance\n\nbased on the accrual of six dependability points. In mid-March,\n\nthe appellant (upon submission of documentation from her health\n\ncare provider) was pre-approved for intermittent FMLA leave of one\n\noccurrence per month in increments of one day. The appellant\n\nreceived continued progressive guidance on May 28, 2015, for\n\nreaching eight dependability points. During the accompanying\n\nmeeting, the appellant lamented that many of her UNA absences from\n\nMarch to April (which exceeded her approved FMLA allotment) should\n\nhave been excused as FMLA leave. She also met with a supervisor\n\nto vent her frustration with what she perceived as a skeptical and\n\ncondescending tone in the progressive guidance meeting. Over a\n\n\n - 4 -\n\fmonth later, the appellant followed up on this discussion by\n\nsending an email memorializing her complaints.\n\n On June 18, 2015, the appellant submitted amended\n\ndocumentation in hopes of extending the approved increments of her\n\nintermittent FMLA leave from one day per occurrence to five days\n\nper occurrence. MetLife acceded to this request. Meanwhile, the\n\nappellant continued to accrue unexcused absences. On July 17,\n\n2015, she received a final progressive guidance (the penultimate\n\nwarning) based on her accrual of ten dependability points. The\n\nappellant alleges that she submitted documentation from her health\n\ncare provider in late July indicating that several of her unexcused\n\nabsences from March and May were related to her PTSD and/or her\n\ndepression. She urged unsuccessfully that these absences should\n\nbe recoded as FMLA occurrences.\n\n In the summer of 2015, the appellant was hospitalized\n\nseveral times due to mental health issues. She claims that she\n\nnotified both JetBlue and MetLife of her hospitalization and that\n\nshe requested FMLA and short-term disability leave by July 30,\n\n2015. MetLife asked for substantiating documentation, which the\n\nappellant subsequently provided. The appellant furnished\n\ndocumentation of hospitalization commencing on August 6, 2015, and\n\nher leave was approved from that date forward. Even so, an absence\n\ntwo days prior to this date was coded as UNA despite the fact that\n\nthe appellant appears to have been hospitalized on that date. This\n\n\n - 5 -\n\funexcused absence brought the appellant's total dependability\n\npoints to twelve, thus exposing her to suspension, employment\n\nreview, and possible dismissal.\n\n The appellant notified JetBlue on November 2, 2015, that\n\nshe had filed a complaint with the MCAD — a complaint alleging\n\nthat JetBlue had discriminated against her on the basis of her\n\nhandicap in violation of Chapter 151B of the Massachusetts General\n\nLaws. On November 17 (two days after the appellant returned from\n\nher approved disability leave), JetBlue suspended her. On December\n\n15, JetBlue, citing the appellant's numerous unexcused absences,\n\nterminated her employment.\n\n Chapter 151B entitles complainants to bring a civil\n\naction in a state court \"at the expiration of ninety days after\n\nthe filing of a complaint with the commission . . . but not later\n\nthan three years after the alleged unlawful practice occurred.\"\n\nMass. Gen. Laws ch. 151B, § 9. The appellant filed a timely suit\n\nin the Suffolk Superior Court, alleging not only discrimination\n\nbut also that JetBlue had retaliated against her for filing the\n\nMCAD complaint. Noting diversity of citizenship and the existence\n\nof a controversy in the requisite amount, JetBlue removed the suit\n\nto the federal district court. See 28 U.S.C. §§ 1332(a), 1441.\n\nNear the completion of discovery but after the expiration of the\n\ndeadlines set for amending the pleadings, see Fed R. Civ. P. 16(b),\n\nthe appellant sought to add an FMLA breach count. The district\n\n\n - 6 -\n\fcourt denied her motion to amend and likewise denied her motion\n\nfor reconsideration.\n\n In due course, JetBlue moved for summary judgment. See\n\nFed. R. Civ. P. 56(a). The appellant opposed the motion, but the\n\ndistrict court granted it. See Miceli, 2018 WL 1524539, at *6.\n\nThis timely appeal ensued.\n\nII. ANALYSIS\n\n The appellant assigns error to the district court's\n\nentry of summary judgment with respect to her state-law claims of\n\nboth handicap discrimination and retaliation.2 She also assigns\n\nerror to the denial of her motion to amend her complaint. We\n\naddress these claims of error sequentially.\n\n A. Summary Judgment.\n\n We review the grant of summary judgment de novo. See\n\nNoviello v. City of Bos., 398 F.3d 76, 84 (1st Cir. 2005). Summary\n\njudgment is warranted if the record, construed in the light most\n\nflattering to the nonmovant, \"presents no genuine issue as to any\n\nmaterial fact and reflects the movant's entitlement to judgment as\n\na matter of law.\" McKenney v. Mangino, 873 F.3d 75, 80 (1st Cir.\n\n2017), cert. denied, 138 S. Ct. 1311 (2018). When a plaintiff\n\n\n 2 Massachusetts state law refers to an individual's \"handicap\"\nrather than her \"disability\" — the term favored by the Americans\nwith Disabilities Act (ADA), 42 U.S.C. §§ 12101-12213. Since there\nis no substantive difference between the two terms, see Ocean Spray\nCranberries, Inc. v. MCAD, 808 N.E.2d 257, 263 n.6 (Mass. 2004),\nwe use them interchangeably.\n\n\n - 7 -\n\fopposes summary judgment, she bears \"the burden of producing\n\nspecific facts sufficient to deflect the swing of the summary\n\njudgment scythe.\" Mulvihill v. Top-Flite Golf Co., 335 F.3d 15,\n\n19 (1st Cir. 2003). For this purpose, she cannot rely on\n\n\"conclusory allegations, improbable inferences, acrimonious\n\ninvective, or rank speculation.\" Ahern v. Shinseki, 629 F.3d 49,\n\n54 (1st Cir. 2010).\n\n 1. Discriminatory Discharge. In Massachusetts, it is\n\nunlawful for an employer:\n\n . . . to dismiss from employment or refuse to\n hire, rehire or advance in employment or\n otherwise discriminate against, because of his\n handicap, any person alleging to be a\n qualified handicapped person, capable of\n performing the essential functions of the\n position involved with reasonable\n accommodation, unless the employer can\n demonstrate that the accommodation required to\n be made to the physical or mental limitations\n of the person would impose an undue hardship\n to the employer's business.\n\nMass. Gen. Laws ch. 151B, § 4(16). Massachusetts law supplies the\n\nsubstantive rules of decision in this diversity suit. See Sanders\n\nv. Phoenix Ins. Co., 843 F.3d 37, 42 (1st Cir. 2016). That state's\n\nhighest court, the Supreme Judicial Court (SJC), \"look[s] to the\n\nFederal cases decided under the ADA as a guide to the\n\ninterpretation of [chapter] 151B.\" Russell v. Cooley Dickinson\n\nHosp., Inc., 772 N.E.2d 1054, 1061 n.5 (Mass. 2002). The SJC,\n\nhowever, is not bound by federal interpretations of the ADA in\n\n\n\n\n - 8 -\n\fconstruing chapter 151B. See Mass. Elec. Co. v. MCAD, 375 N.E.2d\n\n1192, 1198 (Mass. 1978). Indeed, the SJC has, on occasion,\n\ndeparted from federal law in the area of disability discrimination.\n\nSee e.g., Gannon v. City of Bos., 73 N.E.3d 748, 760 n.10 (Mass.\n\n2017); Mammone v. President & Fellows of Harvard Coll., 847 N.E.2d\n\n276, 285 n.25 (Mass. 2006). We proceed accordingly.\n\n The McDonnell Douglas burden-shifting framework applies\n\nto the appellant's discriminatory discharge claim. See Gannon 73\n\nN.E.3d at 756 (citing McDonnell Douglas Corp. v. Green, 411 U.S.\n\n792, 802 (1973)); see also Henry v. United Bank, 686 F.3d 50, 59\n\n(1st Cir. 2012). At the first stage of this framework, the\n\nappellant bears the burden of showing a prima facie case of\n\ndiscrimination. See Gannon, 73 N.E.3d at 756. This requires a\n\nshowing that the appellant has a handicap; that she was nonetheless\n\nqualified to perform the essential functions of the job, with or\n\nwithout reasonable accommodation; and that, despite the foregoing,\n\nJetBlue discharged her. See Verdrager v. Mintz, Levin, Cohn,\n\nFerris, Glovsky & Popeo, P.C., 50 N.E.3d 778, 793 (Mass. 2016);\n\nGannon, 73 N.E.3d at 756. As a practical matter, we can safely\n\nassume (albeit for argument's sake) that the appellant has met the\n\nprima facie case requirement, thus creating \"a presumption of\n\ndiscrimination.\" Gillen v. Fallon Ambul. Serv., Inc., 283 F.3d\n\n11, 30 (1st Cir. 2002).\n\n\n\n\n - 9 -\n\f The burden of production thus shifts to JetBlue, which\n\nmust proffer a legitimate reason for the adverse employment action,\n\nsupported by credible evidence. See Abramian v. President &\n\nFellows of Harvard Coll., 731 N.E.2d 1075, 1084 (Mass. 2000); see\n\nalso Verdrager, 50 N.E.3d at 793. The proffered reason must be\n\none \"which, on its face, would justify a conclusion that the\n\nplaintiff was let go for a nondiscriminatory motive.\" Dávila v.\n\nCorporación De P.R. Para La Difusión Pública, 498 F.3d 9, 16 (1st\n\nCir. 2007); see Verdrager, 50 N.E.3d at 793. JetBlue has carried\n\nthis burden: it consistently has averred that it terminated the\n\nappellant's employment in accordance with its clearly delineated\n\nand neutrally applied corporate policy after she accrued twelve\n\ndependability points. And JetBlue has buttressed this averment\n\nwith documentation confirming the appellant's unexcused absences.\n\nUniform application of a facially neutral policy that proscribes\n\nunexcused absences is a legitimate, nondiscriminatory reason for\n\ntermination that is distinct from the employee's disability. See\n\nLeary v. Dalton, 58 F.3d 748, 754 (1st Cir. 1995); cf. Raytheon\n\nCo. v. Hernandez, 540 U.S. 44, 53 (2003) (holding, in ADA case,\n\nthat application of neutral, generally applicable policy\n\nconstituted legitimate nondiscriminatory reason for refusing to\n\nrehire employee).\n\n At the third stage of the McDonnell Douglas framework,\n\nthe burden reverts to the employee to show that the adverse\n\n\n - 10 -\n\femployment action was taken \"because of\" her handicap and \"not for\n\nthe reason proffered by the employer.\" Gannon, 73 N.E.3d at 756\n\n(quoting Mass. Gen. Laws ch. 151B, § 4(16)). In a Chapter 151B\n\ncase, an employee can survive summary judgment on this issue by\n\nshowing pretext, that is, \"that there are disputed issues of fact\n\nas to whether the employer's proffered reason was not the true\n\nreason\" for her termination. Id. at 757; see Verdrager, 50 N.E.3d\n\nat 794. Pretext may be demonstrated in a variety of ways, such as\n\nby exposing \"weaknesses, implausibilities, inconsistencies,\n\nincoherencies, or contradictions\" in the employer's proffered\n\nreason. Santiago-Ramos v. Centennial P.R. Wireless Corp., 217\n\nF.3d 46, 56 (1st Cir. 2000) (quoting Hodgens v. Gen. Dynamics\n\nCorp., 144 F.3d 151, 168 (1st Cir. 1998)); see Bulwer v. Mt. Auburn\n\nHosp., 46 N.E.3d 24, 35-38 (Mass. 2016).\n\n The appellant contends that JetBlue's proffered reason\n\nwas pretextual because JetBlue, despite alleged knowledge of her\n\ndisability, did not accommodate her disability in applying its\n\nattendance policy. While the appellant might perhaps be able to\n\ndemonstrate that the asserted basis for her termination was\n\npretextual were she able to show that she requested a reasonable\n\naccommodation that would have ensured her compliance with the\n\npolicy, cf. Barbuto v. Advantage Sale & Mktg., LLC, 78 N.E.3d 37,\n\n44 (Mass. 2017) (concluding that employee's request for\n\naccommodation as to her use of medical marijuana was not facially\n\n\n - 11 -\n\funreasonable and so termination for violating drug policy could\n\nhave been discriminatory); Evans v. Fed. Exp. Corp., 133 F.3d 137,\n\n140 (1st Cir. 1998) (\"If the employee had [requested an\n\naccommodation], the firing might still be regarded as one 'because'\n\nof a handicap or at least 'because' of the denial.\"), she has made\n\nno such showing here.\n\n \"[F]or an employee's actions to constitute a request for\n\naccommodation, they must make the employer aware that the employee\n\nis entitled to and needs accommodation.\" Ocean Spray Cranberries,\n\nInc. v. MCAD, 808 N.E.2d 257, 271 n.21 (Mass. 2004). If the\n\nrequested accommodation is not suitable or the request is otherwise\n\ninappropriate, the employer nonetheless \"must make a reasonable\n\neffort to determine the appropriate accommodation . . . through a\n\nflexible, interactive process that involves both the employer and\n\nthe qualified individual with a disability.\" Russell, 772 N.E.2d\n\nat 1065 (quoting 29 C.F.R. § 1630 App. (2001) (alteration in\n\noriginal)).\n\n Here, JetBlue offered its workforce specific avenues for\n\nrelaying requests for accommodations. To this end, it created an\n\nemail address and an online application directed to the company's\n\nhuman resources department. Information about these modalities\n\nwas in the Blue Book and was included in relevant paperwork\n\nfurnished to all crew members (such as progressive guidance\n\n\n\n\n - 12 -\n\fmaterials). Although the appellant had access to these materials,\n\nshe chose not to travel along either of the designated avenues.\n\n Even so, the appellant maintains that she requested\n\naccommodations. She locates her supposed requests for\n\naccommodation in progressive guidance meetings (in which she\n\nexpressed her frustration at MetLife's coding of her FMLA absences)\n\nand in related interactions with JetBlue employees. In particular,\n\nshe focuses on a July 2015 email to Bourgeois, see supra note 1,\n\nin which she referred to having a disability and expressed her\n\nhope \"for those of us with disabilities to be met with compassion\n\nand reasonable accommodations made if difficulties are faced.\"\n\nBut an employee who seeks an accommodation must be more\n\nforthcoming: a request for an accommodation must be reasonably\n\nspecific. See Jones v. Nationwide Life Ins. Co., 696 F.3d 78, 89\n\n(1st Cir. 2012). It must comprise more than a cryptic\n\ncommunication to be deciphered by the recipient. Importantly,\n\nsuch a request must illuminate the linkage between the requestor's\n\ndisability and the requested accommodation. See id.; Ocean Spray,\n\n808 N.E.2d at 271-72.\n\n In Ocean Spray, for instance, the employee had provided\n\nhis employer with three physician letters that supported his claim\n\nof disability and described his need for an accommodation in\n\nvarying levels of detail. See 808 N.E.2d at 271. The SJC concluded\n\nthat, in the ensemble, these letters \"constitute[d] substantial\n\n\n - 13 -\n\fevidence of an unmistakable request for accommodation.\" Id. The\n\ncourt indicated, though, that any one of these letters, standing\n\nalone, might well be insufficient to constitute a request for\n\naccommodation. See id. Viewed in this light, the appellant's\n\ncomplaints anent MetLife's alleged incorrect coding of her\n\nabsences and her email noting that people with disabilities are\n\nentitled to reasonable accommodation are far removed from any\n\nstatement that JetBlue could reasonably be expected to interpret\n\nas a request for a specific accommodation.\n\n Nor are the appellant's requests for FMLA and disability\n\nleave relevant to this inquiry. While such requests may be deemed\n\nrequests for accommodation \"in some circumstances,\" Echevarría v.\n\nAstraZeneca Pharm. LP, 856 F.3d 119, 128 (1st Cir. 2017) (quoting\n\nGarcía-Ayala v. Lederle Parenterals, Inc., 212 F.3d 638, 647 (1st\n\nCir. 2000)), the appellant's requests were wholly collateral to\n\nJetBlue's policy, which did not allocate dependability points on\n\nthe basis of absences stemming from either approved FMLA or\n\ndisability leaves. And in any event, those requests were granted.\n\n Finally, we are not persuaded by the appellant's\n\nattempts to locate pretext in JetBlue's failure to modify its\n\nattendance policy absent any requests for modification on the\n\nappellant's part. The SJC has concluded that Chapter 151B imposes\n\nno such unilateral responsibility upon employers. See Mammone,\n\n847 N.E.2d at 285 n.25.\n\n\n - 14 -\n\f That ends this aspect of the matter. We conclude that\n\nin as much as the appellant has not shown that she requested an\n\naccommodation as to JetBlue's attendance policy, she has failed to\n\ncast any shadow upon JetBlue's proffered reason for her\n\ntermination. Therefore, we agree with the district court that the\n\nappellant has not made out a genuine issue of material fact\n\nsufficient to avoid summary judgment.\n\n Of course, when an employer alleges that standard\n\npolicies underpin an adverse employment action against a person\n\nwith disabilities, that person may demonstrate pretext through a\n\nshowing that the employer has not applied those policies uniformly.\n\nSee Kouvchinov, 537 F.3d at 68; see also Acevedo-Parrilla v.\n\nNovartis Ex-Lax, Inc., 696 F.3d 128, 142 (1st Cir. 2012). This\n\nmay be accomplished by showing, say, that the adverse action\n\ndeparted from a clearly delineated policy, see Kouvchinov, 537\n\nF.3d at 68, or that the employer applied such a policy differently\n\nto similarly situated employees, see Verdrager, 50 N.E.3d at 795;\n\nBulwer, 46 N.E.3d at 36. Here, however, the theoretical\n\navailability of these alternative methods of showing pretext does\n\nnot improve the appellant's lot.\n\n To begin, the appellant has offered nothing to show that\n\nJetBlue applied its attendance policy disparately to similarly\n\nsituated employees. So, too, the appellant's attempt to base\n\nliability on a supposed departure from policy lacks force. In\n\n\n - 15 -\n\fthis respect, she alleges that MetLife miscoded her FMLA absences\n\ndespite receiving proper notice and necessary substantiation, and\n\nthat JetBlue fired her due to those miscoded absences.3 But a bare\n\nshowing of administrative error, without more, does not make out\n\na case of either pretext or discriminatory discharge. After all,\n\nChapter 151B was never intended to \"protect against all instances\n\nof arbitrary action or from poor managerial judgment.\" Wheelock\n\nColl. v. MCAD, 355 N.E.2d 309, 314 (Mass. 1976); cf. Kouvchinov,\n\n537 F.3d at 67 (\"[T]he anti-discrimination laws do not insure\n\nagainst inaccuracy or flawed business judgment on the employer's\n\npart.\"). Instead, the law was \"designed to protect against, and\n\nto prevent, actions spurred by some discriminatory animus.\"\n\nKouvchinov, 537 F.3d at 67.\n\n Last — but far from least — the appellant's claim of\n\npretext fails because she has adduced no evidence that JetBlue\n\nknew that there were errors in the coding of her absences when it\n\nterminated her employment. Nor has she adduced any evidence\n\nshowing that she engaged in the procedures established by JetBlue\n\nto prevent such bevues from leading to termination. Under\n\n\n 3The district court concluded that the appellant did not\nprovide sufficient evidence of the alleged coding errors at summary\njudgment. See Miceli, 2018 WL 1524539, at *3. Because we hold\nthat the appellant's claim of pretext would fail even if she had\nsupplied such evidence, we do not wade into the nitty-gritty of\nthese allegations. We do note, however, that the record indicates\nthat MetLife's operation had some serious, and seriously\nfrustrating, kinks.\n\n\n - 16 -\n\fJetBlue's standard policies, the appellant had several\n\nopportunities to challenge her unexcused absences, but she chose\n\nnot to avail herself of any of them. For example, the record makes\n\nmanifest that she neither reviewed nor responded to her final\n\nprogressive guidance. And she did not challenge (or even inquire\n\nabout) unexcused absences attributed to her when she was notified\n\nfirst of her suspension and later of her termination.\n\n The appellant's failure to pursue these remedial\n\nmeasures sinks her claim of pretext. Where, as here, an employee's\n\nconcerns about the handling of her employment are not raised\n\nthrough reasonable (and reasonably neutral) processes made\n\navailable by her employer and known to her, it is not appropriate\n\nfor a court to second-guess the fairness of individual attendance\n\ndeterminations. Cf. Mesnick, 950 F.2d at 825 (explaining, in\n\ndiscrimination case brought under federal law, that courts do not\n\n\"sit as super personnel departments\").\n\n To say more would be to paint the lily. We conclude\n\nthat the appellant has not satisfied her burden of adducing\n\nevidence sufficient to show that JetBlue's proffered reason for\n\nher dismissal was pretextual. Accordingly, we agree with the\n\ndistrict court that the appellant's handicap discrimination claims\n\ncannot survive summary judgment.\n\n 2. Retaliation. The district court also granted summary\n\njudgment as to the appellant's claim that JetBlue fired her in\n\n\n - 17 -\n\fretaliation for filing an MCAD complaint. See Miceli, 2018 WL\n\n1524539, at *5. Once again, we employ the McDonnell Douglas\n\nburden-shifting framework as an analytic tool. See Mole v. Univ.\n\nof Mass., 814 N.E.2d 329, 338 (Mass. 2004).\n\n Under applicable state law, see Mass. Gen. Laws ch. 151B,\n\n§ 4(4), a prima facie case of retaliation requires the claimant to\n\nshow that she engaged in protected activity; that she experienced\n\nsome adverse action; and that the protected activity was causally\n\nconnected to the adverse action, see Mole, 814 N.E.2d at 338-39.\n\nThe first and second elements are clearly present: filing an MCAD\n\ncomplaint is protected activity and termination of employment is\n\na classic example of an adverse employment action. See Clifton v.\n\nMass. Bay Transp. Auth., 839 N.E.2d 314, 318 (Mass. 2005); Mole,\n\n814 N.E2d at 338 n.13. The third element, though, is the sticking\n\npoint.\n\n In attempting to show the necessary causal connection\n\nbetween JetBlue's receipt of the MCAD complaint and its termination\n\nof her employment, the appellant relies exclusively on the timing\n\nand sequence of these two events. In the circumstances of this\n\ncase, her reliance is misplaced.\n\n To be sure, an inference of causation may be drawn \"if\n\nadverse action is taken against a satisfactorily performing\n\nemployee in the immediate aftermath of the employer's becoming\n\naware of the employee's protected activity.\" Mole, 814 N.E.2d at\n\n\n - 18 -\n\f339. But when \"problems with an employee predate any knowledge\n\nthat the employee has engaged in protected activity, it is not\n\npermissible to draw the inference that subsequent adverse actions,\n\ntaken after the employer acquires such knowledge, are motivated by\n\nretaliation.\" Id. at 340.\n\n Our decision in Pearson v. Mass. Bay Transp. Auth., 723\n\nF.3d 36 (1st Cir. 2013), illustrates this point. There, we held\n\nthat a plaintiff alleging retaliation under Chapter 151B failed to\n\nshow a sufficient causal connection at summary judgment because\n\nthe plaintiff's supervisors had recommended his termination before\n\nhe engaged in the protected activity. See id. at 42. Even though\n\nthe employer's final decision to discharge the plaintiff did not\n\noccur until after the protected activity, we concluded that the\n\nplaintiff would have had to show that the outcome would have\n\ndiffered if not for the employer's knowledge of the protected\n\nactivity. See id.\n\n The case at hand fits the Pearson model. At the time\n\nthat the appellant filed her MCAD complaint, she had already\n\naccrued twelve dependability points and, thus, was subject to\n\nsuspension and termination review. The appellant has offered\n\nnothing to suggest that, but for her protected activity, she would\n\nnot have been terminated as a result of this review. In the\n\ncircumstances of this case, timing and sequence, without more, are\n\nnot enough to ground an inference of causation. It follows that\n\n\n - 19 -\n\fthe district court did not err in granting summary judgment on the\n\nappellant's retaliation claim.\n\n B. Motion to Amend.\n\n There is one loose end: the appellant's challenge to\n\nthe district court's denial of her motion to amend her complaint.\n\nWe review orders granting or denying leave to amend for abuse of\n\ndiscretion. See U.S. ex rel. D'Agostino v. EV3, Inc., 802 F.3d\n\n188, 191 (1st Cir. 2015). Under this deferential standard, we\n\nwill affirm \"so long as the record evinces an arguably adequate\n\nbasis for the court's decision.\" Hatch v. Dep't of Children, Youth\n\n& Their Families, 274 F.3d 12, 19 (1st Cir. 2001).\n\n Where, as here, leave to amend is sought more than\n\ntwenty-one days after service of the complaint and the opposing\n\nparty has not consented, a complaint may be amended only by leave\n\nof court. See Fed. R. Civ. P. 15(a). In general, leave should be\n\nfreely given if, in the court's view, \"justice so requires.\" Id.\n\n15(a)(2). The standard may change, though, when — as in this case\n\n— the court has entered a scheduling order under Federal Rule of\n\nCivil Procedure 16(b), which contains, inter alia, a deadline for\n\namendment of the pleadings. In that event, a motion to amend filed\n\noutside the parameters set by the scheduling order will be granted\n\n\"only upon a showing of 'good cause.'\" D'Agostino, 802 F.3d at\n\n192 (quoting Rule 16(b)(4)); see Cruz v. Bristol-Myers Squibb Co.,\n\nPR, Inc., 699 F.3d 563, 569 (1st Cir. 2012). Such an elevated\n\n\n - 20 -\n\fstandard makes perfect sense: without it, \"scheduling orders would\n\nbe little more than aspirational statements, to be disregarded by\n\nthe parties whenever compliance proves inconvenient.\" D'Agostino,\n\n802 F.3d at 194.\n\n The \"good cause\" standard focuses on both the conduct of\n\nthe moving party and the prejudice, if any, to the nonmovant. See\n\nO'Connell v. Hyatt Hotels of P.R., 357 F.3d 152, 155 (1st Cir.\n\n2004). In the decisional calculus, the moving party's diligence\n\nor lack of diligence serves as the \"dominant criterion.\" Id.\n\n\"[T]he longer a plaintiff delays, the more likely the motion to\n\namend will be denied, as protracted delay, with its attendant\n\nburdens on the opponent and the court, is itself a sufficient\n\nreason for the court to withhold permission to amend.\" Steir v.\n\nGirl Scouts of the USA, 383 F.3d 7, 12 (1st Cir. 2004). Nor should\n\na court be expected to look kindly upon a plaintiff who seeks\n\nbelatedly to amend her complaint based on \"information that [she]\n\nhad or should have had from the outset of the case.\" Trans-Spec\n\nTruck Serv., Inc. v. Caterpillar Inc., 524 F.3d 315, 327 (1st Cir.\n\n2008).\n\n With these principles in mind, we turn to the appellant's\n\nmotion to amend. She filed that motion on July 17, 2017, seeking\n\nto add an FMLA claim approximately twelve months after she\n\ncommenced her civil action and approximately five months after the\n\nRule 16(b) deadline to amend had expired. JetBlue objected, and\n\n\n - 21 -\n\fthe district court denied the motion. It concluded that the\n\nappellant had failed to demonstrate good cause for the delay,\n\nparticularly given that she had referred to the possibility of an\n\nFMLA claim as early as her 2015 MCAD complaint.\n\n The appellant sought reconsideration. She asserted that\n\nshe had learned only during discovery that her termination was\n\npremised in part upon an August 4, 2015, UNA absence. Her new\n\nFMLA claim, she insisted, was spurred by this recently discovered\n\nevidence. The district court reaffirmed its earlier denial of\n\nleave to amend, concluding that the appellant had neither\n\nidentified any newly discovered evidence nor called attention to\n\nany error in the court's prior reasoning.\n\n Like the district court, we find the appellant's\n\nargument unpersuasive. Importantly, the MCAD complaint included\n\nallegations that JetBlue relied on miscoded FMLA absences in\n\nterminating the appellant's employment. Given those allegations,\n\nthere was nothing revelatory in the \"discovery\" of the August 4,\n\n2015, UNA absence. We hold, therefore, that the district court\n\ndid not abuse its discretion in concluding that the appellant\n\nfailed to show that new evidence justified the substantial delay\n\nin bringing her belated FMLA claim. That delay, in turn, lends\n\nweight to the district court's supportable conclusions that the\n\nappellant was not diligent in attempting to pursue her FMLA claim\n\nand, therefore, lacked \"good cause.\" See O'Connell, 357 F.3d at\n\n\n - 22 -\n\f155 (affirming \"good cause\" denial of motion to amend complaint\n\nfive months after scheduling order deadline); Sosa v. Airprint\n\nSys., Inc., 133 F.3d 1417, 1419 (11th Cir. 1998) (per curiam)\n\n(affirming denial of motion to amend because plaintiff, who had\n\nrelevant information \"even before she filed suit,\" lacked \"good\n\ncause\").\n\nIII. CONCLUSION\n\n We need go no further. For the reasons elucidated above,\n\nthe judgment of the district court is\n\n\n\nAffirmed.\n\n\n\n\n - 23 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362558/", "author_raw": "SELYA, Circuit Judge"}]}
TORRUELLA
SELYA
LYNCH
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4585305/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Lauren MICELI, Plaintiff, Appellant, v. JETBLUE AIRWAYS CORP.; Mathew Bourgeois, Defendants, Appellees.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-28\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNo. 18-1345\n\n LAUREN MICELI,\n\n Plaintiff, Appellant,\n\n v.\n\n JETBLUE AIRWAYS CORP.; MATHEW BOURGEOIS,\n\n Defendants, Appellees.\n\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Richard G. Stearns, U.S. District Judge]\n\n\n Before\n\n Torruella, Selya, and Lynch,\n Circuit Judges.\n\n\n Christopher J. Trombetta and Law Office of Christopher J.\nTrombetta on brief for appellant.\n Samantha K. Abeysekera and Akerman LLP on brief for appellees.\n\n\n January 28, 2019\n\f SELYA, Circuit Judge. Plaintiff-appellant Lauren Miceli\n\nsued her quondam employer, JetBlue Airways Corp. (JetBlue), for\n\nhandicap discrimination and retaliation under Massachusetts state\n\nlaw.1 The appellant alleges that JetBlue fired her due to her\n\ndisability and not (as JetBlue maintains) because she flouted\n\ncompany policy on unexcused absences. She also alleges that\n\nJetBlue retaliated against her for filing a complaint with the\n\nMassachusetts Commission against Discrimination (MCAD). The\n\ndistrict court granted summary judgment in JetBlue's favor. See\n\nMiceli v. JetBlue Airways Corp., No. CV 16-12032, 2018 WL 1524539,\n\nat *6 (D. Mass. Mar. 28, 2018). Critical to the court's assessment\n\nwas the appellant's failure to use measures provided by JetBlue\n\nenabling an employee to challenge a suspension or termination.\n\nSee id. at *5.\n\n The appellant assigns error. Even when viewing the\n\nrecord in the light most favorable to the appellant, we detect no\n\nprobative evidence of discrimination or retaliation.\n\nConsequently, we affirm.\n\n\n\n\n 1\n The appellant's complaint named Mathew Bourgeois, JetBlue's\ninflight service manager, as a co-defendant. The parties and the\ndistrict court have treated JetBlue and Bourgeois as a unit. For\nease in exposition, then, we refer to JetBlue as if it were the\nsole defendant and appellee. Our decision, of course, binds all\nparties.\n\n\n - 2 -\n\fI. BACKGROUND\n\n We rehearse the facts \"in the light most agreeable to\n\nthe plaintiff, consistent with record support,\" Kouvchinov v.\n\nParametric Tech. Corp., 537 F.3d 62, 65 (1st Cir. 2008), and then\n\nrecount the travel of the case. We reserve \"more exegetic detail\n\nfor our analysis of the issues on appeal.\" Harrington v. Aggregate\n\nIndus. Ne. Region, Inc., 668 F.3d 25, 28 (1st Cir. 2012).\n\n Beginning in 2006, JetBlue employed the appellant as an\n\ninflight crew member, based in the Boston area. When hired, the\n\nappellant was given access to an employee handbook (the Blue Book),\n\nwhich outlined, inter alia, JetBlue's policies on attendance,\n\nleave, and reasonable accommodation. As her employment\n\nprogressed, the appellant began to suffer from health issues.\n\nWhile on duty in the fall of 2014, she experienced an ear injury.\n\nThe following spring, she was diagnosed through JetBlue's third-\n\nparty employee assistance program with post-traumatic stress\n\ndisorder (PTSD) and depression. The appellant sought and obtained\n\nleave with respect to these conditions under the Family and Medical\n\nLeave Act (FMLA), 29 U.S.C. § 2601.\n\n In administering its FMLA program, JetBlue contracts\n\nwith a third-party administrator, Metropolitan Life Insurance\n\nCompany (MetLife). JetBlue's protocol channels all matters\n\nregarding FMLA approval to MetLife. In order to obtain FMLA leave\n\nbased on an illness of her own, a crew member is required to\n\n\n - 3 -\n\ffurnish MetLife with substantiating documentation from her health\n\ncare provider (including a \"Certificate of Health Care Provider\"\n\nform). Unless such leave is granted, absences are denoted in the\n\ncrew member's schedule as \"unavailable for assignment\" (UNA).\n\n Under JetBlue's dependability guidelines policy, limned\n\nin a Blue Book supplement, UNA absences are assigned category codes\n\nand point values. The accrual of points within a twelve-month\n\nperiod triggers five stages of progressive guidance, culminating\n\nin an employment review upon the accumulation of twelve points.\n\nSuch a review may result in the crew member's termination.\n\n Starting in the fall of 2014, the appellant began to\n\naccrue UNA absences, which she traces to her health conditions.\n\nOn February 7, 2015, she received an initial progressive guidance\n\nbased on the accrual of six dependability points. In mid-March,\n\nthe appellant (upon submission of documentation from her health\n\ncare provider) was pre-approved for intermittent FMLA leave of one\n\noccurrence per month in increments of one day. The appellant\n\nreceived continued progressive guidance on May 28, 2015, for\n\nreaching eight dependability points. During the accompanying\n\nmeeting, the appellant lamented that many of her UNA absences from\n\nMarch to April (which exceeded her approved FMLA allotment) should\n\nhave been excused as FMLA leave. She also met with a supervisor\n\nto vent her frustration with what she perceived as a skeptical and\n\ncondescending tone in the progressive guidance meeting. Over a\n\n\n - 4 -\n\fmonth later, the appellant followed up on this discussion by\n\nsending an email memorializing her complaints.\n\n On June 18, 2015, the appellant submitted amended\n\ndocumentation in hopes of extending the approved increments of her\n\nintermittent FMLA leave from one day per occurrence to five days\n\nper occurrence. MetLife acceded to this request. Meanwhile, the\n\nappellant continued to accrue unexcused absences. On July 17,\n\n2015, she received a final progressive guidance (the penultimate\n\nwarning) based on her accrual of ten dependability points. The\n\nappellant alleges that she submitted documentation from her health\n\ncare provider in late July indicating that several of her unexcused\n\nabsences from March and May were related to her PTSD and/or her\n\ndepression. She urged unsuccessfully that these absences should\n\nbe recoded as FMLA occurrences.\n\n In the summer of 2015, the appellant was hospitalized\n\nseveral times due to mental health issues. She claims that she\n\nnotified both JetBlue and MetLife of her hospitalization and that\n\nshe requested FMLA and short-term disability leave by July 30,\n\n2015. MetLife asked for substantiating documentation, which the\n\nappellant subsequently provided. The appellant furnished\n\ndocumentation of hospitalization commencing on August 6, 2015, and\n\nher leave was approved from that date forward. Even so, an absence\n\ntwo days prior to this date was coded as UNA despite the fact that\n\nthe appellant appears to have been hospitalized on that date. This\n\n\n - 5 -\n\funexcused absence brought the appellant's total dependability\n\npoints to twelve, thus exposing her to suspension, employment\n\nreview, and possible dismissal.\n\n The appellant notified JetBlue on November 2, 2015, that\n\nshe had filed a complaint with the MCAD — a complaint alleging\n\nthat JetBlue had discriminated against her on the basis of her\n\nhandicap in violation of Chapter 151B of the Massachusetts General\n\nLaws. On November 17 (two days after the appellant returned from\n\nher approved disability leave), JetBlue suspended her. On December\n\n15, JetBlue, citing the appellant's numerous unexcused absences,\n\nterminated her employment.\n\n Chapter 151B entitles complainants to bring a civil\n\naction in a state court \"at the expiration of ninety days after\n\nthe filing of a complaint with the commission . . . but not later\n\nthan three years after the alleged unlawful practice occurred.\"\n\nMass. Gen. Laws ch. 151B, § 9. The appellant filed a timely suit\n\nin the Suffolk Superior Court, alleging not only discrimination\n\nbut also that JetBlue had retaliated against her for filing the\n\nMCAD complaint. Noting diversity of citizenship and the existence\n\nof a controversy in the requisite amount, JetBlue removed the suit\n\nto the federal district court. See 28 U.S.C. §§ 1332(a), 1441.\n\nNear the completion of discovery but after the expiration of the\n\ndeadlines set for amending the pleadings, see Fed R. Civ. P. 16(b),\n\nthe appellant sought to add an FMLA breach count. The district\n\n\n - 6 -\n\fcourt denied her motion to amend and likewise denied her motion\n\nfor reconsideration.\n\n In due course, JetBlue moved for summary judgment. See\n\nFed. R. Civ. P. 56(a). The appellant opposed the motion, but the\n\ndistrict court granted it. See Miceli, 2018 WL 1524539, at *6.\n\nThis timely appeal ensued.\n\nII. ANALYSIS\n\n The appellant assigns error to the district court's\n\nentry of summary judgment with respect to her state-law claims of\n\nboth handicap discrimination and retaliation.2 She also assigns\n\nerror to the denial of her motion to amend her complaint. We\n\naddress these claims of error sequentially.\n\n A. Summary Judgment.\n\n We review the grant of summary judgment de novo. See\n\nNoviello v. City of Bos., 398 F.3d 76, 84 (1st Cir. 2005). Summary\n\njudgment is warranted if the record, construed in the light most\n\nflattering to the nonmovant, \"presents no genuine issue as to any\n\nmaterial fact and reflects the movant's entitlement to judgment as\n\na matter of law.\" McKenney v. Mangino, 873 F.3d 75, 80 (1st Cir.\n\n2017), cert. denied, 138 S. Ct. 1311 (2018). When a plaintiff\n\n\n 2 Massachusetts state law refers to an individual's \"handicap\"\nrather than her \"disability\" — the term favored by the Americans\nwith Disabilities Act (ADA), 42 U.S.C. §§ 12101-12213. Since there\nis no substantive difference between the two terms, see Ocean Spray\nCranberries, Inc. v. MCAD, 808 N.E.2d 257, 263 n.6 (Mass. 2004),\nwe use them interchangeably.\n\n\n - 7 -\n\fopposes summary judgment, she bears \"the burden of producing\n\nspecific facts sufficient to deflect the swing of the summary\n\njudgment scythe.\" Mulvihill v. Top-Flite Golf Co., 335 F.3d 15,\n\n19 (1st Cir. 2003). For this purpose, she cannot rely on\n\n\"conclusory allegations, improbable inferences, acrimonious\n\ninvective, or rank speculation.\" Ahern v. Shinseki, 629 F.3d 49,\n\n54 (1st Cir. 2010).\n\n 1. Discriminatory Discharge. In Massachusetts, it is\n\nunlawful for an employer:\n\n . . . to dismiss from employment or refuse to\n hire, rehire or advance in employment or\n otherwise discriminate against, because of his\n handicap, any person alleging to be a\n qualified handicapped person, capable of\n performing the essential functions of the\n position involved with reasonable\n accommodation, unless the employer can\n demonstrate that the accommodation required to\n be made to the physical or mental limitations\n of the person would impose an undue hardship\n to the employer's business.\n\nMass. Gen. Laws ch. 151B, § 4(16). Massachusetts law supplies the\n\nsubstantive rules of decision in this diversity suit. See Sanders\n\nv. Phoenix Ins. Co., 843 F.3d 37, 42 (1st Cir. 2016). That state's\n\nhighest court, the Supreme Judicial Court (SJC), \"look[s] to the\n\nFederal cases decided under the ADA as a guide to the\n\ninterpretation of [chapter] 151B.\" Russell v. Cooley Dickinson\n\nHosp., Inc., 772 N.E.2d 1054, 1061 n.5 (Mass. 2002). The SJC,\n\nhowever, is not bound by federal interpretations of the ADA in\n\n\n\n\n - 8 -\n\fconstruing chapter 151B. See Mass. Elec. Co. v. MCAD, 375 N.E.2d\n\n1192, 1198 (Mass. 1978). Indeed, the SJC has, on occasion,\n\ndeparted from federal law in the area of disability discrimination.\n\nSee e.g., Gannon v. City of Bos., 73 N.E.3d 748, 760 n.10 (Mass.\n\n2017); Mammone v. President & Fellows of Harvard Coll., 847 N.E.2d\n\n276, 285 n.25 (Mass. 2006). We proceed accordingly.\n\n The McDonnell Douglas burden-shifting framework applies\n\nto the appellant's discriminatory discharge claim. See Gannon 73\n\nN.E.3d at 756 (citing McDonnell Douglas Corp. v. Green, 411 U.S.\n\n792, 802 (1973)); see also Henry v. United Bank, 686 F.3d 50, 59\n\n(1st Cir. 2012). At the first stage of this framework, the\n\nappellant bears the burden of showing a prima facie case of\n\ndiscrimination. See Gannon, 73 N.E.3d at 756. This requires a\n\nshowing that the appellant has a handicap; that she was nonetheless\n\nqualified to perform the essential functions of the job, with or\n\nwithout reasonable accommodation; and that, despite the foregoing,\n\nJetBlue discharged her. See Verdrager v. Mintz, Levin, Cohn,\n\nFerris, Glovsky & Popeo, P.C., 50 N.E.3d 778, 793 (Mass. 2016);\n\nGannon, 73 N.E.3d at 756. As a practical matter, we can safely\n\nassume (albeit for argument's sake) that the appellant has met the\n\nprima facie case requirement, thus creating \"a presumption of\n\ndiscrimination.\" Gillen v. Fallon Ambul. Serv., Inc., 283 F.3d\n\n11, 30 (1st Cir. 2002).\n\n\n\n\n - 9 -\n\f The burden of production thus shifts to JetBlue, which\n\nmust proffer a legitimate reason for the adverse employment action,\n\nsupported by credible evidence. See Abramian v. President &\n\nFellows of Harvard Coll., 731 N.E.2d 1075, 1084 (Mass. 2000); see\n\nalso Verdrager, 50 N.E.3d at 793. The proffered reason must be\n\none \"which, on its face, would justify a conclusion that the\n\nplaintiff was let go for a nondiscriminatory motive.\" Dávila v.\n\nCorporación De P.R. Para La Difusión Pública, 498 F.3d 9, 16 (1st\n\nCir. 2007); see Verdrager, 50 N.E.3d at 793. JetBlue has carried\n\nthis burden: it consistently has averred that it terminated the\n\nappellant's employment in accordance with its clearly delineated\n\nand neutrally applied corporate policy after she accrued twelve\n\ndependability points. And JetBlue has buttressed this averment\n\nwith documentation confirming the appellant's unexcused absences.\n\nUniform application of a facially neutral policy that proscribes\n\nunexcused absences is a legitimate, nondiscriminatory reason for\n\ntermination that is distinct from the employee's disability. See\n\nLeary v. Dalton, 58 F.3d 748, 754 (1st Cir. 1995); cf. Raytheon\n\nCo. v. Hernandez, 540 U.S. 44, 53 (2003) (holding, in ADA case,\n\nthat application of neutral, generally applicable policy\n\nconstituted legitimate nondiscriminatory reason for refusing to\n\nrehire employee).\n\n At the third stage of the McDonnell Douglas framework,\n\nthe burden reverts to the employee to show that the adverse\n\n\n - 10 -\n\femployment action was taken \"because of\" her handicap and \"not for\n\nthe reason proffered by the employer.\" Gannon, 73 N.E.3d at 756\n\n(quoting Mass. Gen. Laws ch. 151B, § 4(16)). In a Chapter 151B\n\ncase, an employee can survive summary judgment on this issue by\n\nshowing pretext, that is, \"that there are disputed issues of fact\n\nas to whether the employer's proffered reason was not the true\n\nreason\" for her termination. Id. at 757; see Verdrager, 50 N.E.3d\n\nat 794. Pretext may be demonstrated in a variety of ways, such as\n\nby exposing \"weaknesses, implausibilities, inconsistencies,\n\nincoherencies, or contradictions\" in the employer's proffered\n\nreason. Santiago-Ramos v. Centennial P.R. Wireless Corp., 217\n\nF.3d 46, 56 (1st Cir. 2000) (quoting Hodgens v. Gen. Dynamics\n\nCorp., 144 F.3d 151, 168 (1st Cir. 1998)); see Bulwer v. Mt. Auburn\n\nHosp., 46 N.E.3d 24, 35-38 (Mass. 2016).\n\n The appellant contends that JetBlue's proffered reason\n\nwas pretextual because JetBlue, despite alleged knowledge of her\n\ndisability, did not accommodate her disability in applying its\n\nattendance policy. While the appellant might perhaps be able to\n\ndemonstrate that the asserted basis for her termination was\n\npretextual were she able to show that she requested a reasonable\n\naccommodation that would have ensured her compliance with the\n\npolicy, cf. Barbuto v. Advantage Sale & Mktg., LLC, 78 N.E.3d 37,\n\n44 (Mass. 2017) (concluding that employee's request for\n\naccommodation as to her use of medical marijuana was not facially\n\n\n - 11 -\n\funreasonable and so termination for violating drug policy could\n\nhave been discriminatory); Evans v. Fed. Exp. Corp., 133 F.3d 137,\n\n140 (1st Cir. 1998) (\"If the employee had [requested an\n\naccommodation], the firing might still be regarded as one 'because'\n\nof a handicap or at least 'because' of the denial.\"), she has made\n\nno such showing here.\n\n \"[F]or an employee's actions to constitute a request for\n\naccommodation, they must make the employer aware that the employee\n\nis entitled to and needs accommodation.\" Ocean Spray Cranberries,\n\nInc. v. MCAD, 808 N.E.2d 257, 271 n.21 (Mass. 2004). If the\n\nrequested accommodation is not suitable or the request is otherwise\n\ninappropriate, the employer nonetheless \"must make a reasonable\n\neffort to determine the appropriate accommodation . . . through a\n\nflexible, interactive process that involves both the employer and\n\nthe qualified individual with a disability.\" Russell, 772 N.E.2d\n\nat 1065 (quoting 29 C.F.R. § 1630 App. (2001) (alteration in\n\noriginal)).\n\n Here, JetBlue offered its workforce specific avenues for\n\nrelaying requests for accommodations. To this end, it created an\n\nemail address and an online application directed to the company's\n\nhuman resources department. Information about these modalities\n\nwas in the Blue Book and was included in relevant paperwork\n\nfurnished to all crew members (such as progressive guidance\n\n\n\n\n - 12 -\n\fmaterials). Although the appellant had access to these materials,\n\nshe chose not to travel along either of the designated avenues.\n\n Even so, the appellant maintains that she requested\n\naccommodations. She locates her supposed requests for\n\naccommodation in progressive guidance meetings (in which she\n\nexpressed her frustration at MetLife's coding of her FMLA absences)\n\nand in related interactions with JetBlue employees. In particular,\n\nshe focuses on a July 2015 email to Bourgeois, see supra note 1,\n\nin which she referred to having a disability and expressed her\n\nhope \"for those of us with disabilities to be met with compassion\n\nand reasonable accommodations made if difficulties are faced.\"\n\nBut an employee who seeks an accommodation must be more\n\nforthcoming: a request for an accommodation must be reasonably\n\nspecific. See Jones v. Nationwide Life Ins. Co., 696 F.3d 78, 89\n\n(1st Cir. 2012). It must comprise more than a cryptic\n\ncommunication to be deciphered by the recipient. Importantly,\n\nsuch a request must illuminate the linkage between the requestor's\n\ndisability and the requested accommodation. See id.; Ocean Spray,\n\n808 N.E.2d at 271-72.\n\n In Ocean Spray, for instance, the employee had provided\n\nhis employer with three physician letters that supported his claim\n\nof disability and described his need for an accommodation in\n\nvarying levels of detail. See 808 N.E.2d at 271. The SJC concluded\n\nthat, in the ensemble, these letters \"constitute[d] substantial\n\n\n - 13 -\n\fevidence of an unmistakable request for accommodation.\" Id. The\n\ncourt indicated, though, that any one of these letters, standing\n\nalone, might well be insufficient to constitute a request for\n\naccommodation. See id. Viewed in this light, the appellant's\n\ncomplaints anent MetLife's alleged incorrect coding of her\n\nabsences and her email noting that people with disabilities are\n\nentitled to reasonable accommodation are far removed from any\n\nstatement that JetBlue could reasonably be expected to interpret\n\nas a request for a specific accommodation.\n\n Nor are the appellant's requests for FMLA and disability\n\nleave relevant to this inquiry. While such requests may be deemed\n\nrequests for accommodation \"in some circumstances,\" Echevarría v.\n\nAstraZeneca Pharm. LP, 856 F.3d 119, 128 (1st Cir. 2017) (quoting\n\nGarcía-Ayala v. Lederle Parenterals, Inc., 212 F.3d 638, 647 (1st\n\nCir. 2000)), the appellant's requests were wholly collateral to\n\nJetBlue's policy, which did not allocate dependability points on\n\nthe basis of absences stemming from either approved FMLA or\n\ndisability leaves. And in any event, those requests were granted.\n\n Finally, we are not persuaded by the appellant's\n\nattempts to locate pretext in JetBlue's failure to modify its\n\nattendance policy absent any requests for modification on the\n\nappellant's part. The SJC has concluded that Chapter 151B imposes\n\nno such unilateral responsibility upon employers. See Mammone,\n\n847 N.E.2d at 285 n.25.\n\n\n - 14 -\n\f That ends this aspect of the matter. We conclude that\n\nin as much as the appellant has not shown that she requested an\n\naccommodation as to JetBlue's attendance policy, she has failed to\n\ncast any shadow upon JetBlue's proffered reason for her\n\ntermination. Therefore, we agree with the district court that the\n\nappellant has not made out a genuine issue of material fact\n\nsufficient to avoid summary judgment.\n\n Of course, when an employer alleges that standard\n\npolicies underpin an adverse employment action against a person\n\nwith disabilities, that person may demonstrate pretext through a\n\nshowing that the employer has not applied those policies uniformly.\n\nSee Kouvchinov, 537 F.3d at 68; see also Acevedo-Parrilla v.\n\nNovartis Ex-Lax, Inc., 696 F.3d 128, 142 (1st Cir. 2012). This\n\nmay be accomplished by showing, say, that the adverse action\n\ndeparted from a clearly delineated policy, see Kouvchinov, 537\n\nF.3d at 68, or that the employer applied such a policy differently\n\nto similarly situated employees, see Verdrager, 50 N.E.3d at 795;\n\nBulwer, 46 N.E.3d at 36. Here, however, the theoretical\n\navailability of these alternative methods of showing pretext does\n\nnot improve the appellant's lot.\n\n To begin, the appellant has offered nothing to show that\n\nJetBlue applied its attendance policy disparately to similarly\n\nsituated employees. So, too, the appellant's attempt to base\n\nliability on a supposed departure from policy lacks force. In\n\n\n - 15 -\n\fthis respect, she alleges that MetLife miscoded her FMLA absences\n\ndespite receiving proper notice and necessary substantiation, and\n\nthat JetBlue fired her due to those miscoded absences.3 But a bare\n\nshowing of administrative error, without more, does not make out\n\na case of either pretext or discriminatory discharge. After all,\n\nChapter 151B was never intended to \"protect against all instances\n\nof arbitrary action or from poor managerial judgment.\" Wheelock\n\nColl. v. MCAD, 355 N.E.2d 309, 314 (Mass. 1976); cf. Kouvchinov,\n\n537 F.3d at 67 (\"[T]he anti-discrimination laws do not insure\n\nagainst inaccuracy or flawed business judgment on the employer's\n\npart.\"). Instead, the law was \"designed to protect against, and\n\nto prevent, actions spurred by some discriminatory animus.\"\n\nKouvchinov, 537 F.3d at 67.\n\n Last — but far from least — the appellant's claim of\n\npretext fails because she has adduced no evidence that JetBlue\n\nknew that there were errors in the coding of her absences when it\n\nterminated her employment. Nor has she adduced any evidence\n\nshowing that she engaged in the procedures established by JetBlue\n\nto prevent such bevues from leading to termination. Under\n\n\n 3The district court concluded that the appellant did not\nprovide sufficient evidence of the alleged coding errors at summary\njudgment. See Miceli, 2018 WL 1524539, at *3. Because we hold\nthat the appellant's claim of pretext would fail even if she had\nsupplied such evidence, we do not wade into the nitty-gritty of\nthese allegations. We do note, however, that the record indicates\nthat MetLife's operation had some serious, and seriously\nfrustrating, kinks.\n\n\n - 16 -\n\fJetBlue's standard policies, the appellant had several\n\nopportunities to challenge her unexcused absences, but she chose\n\nnot to avail herself of any of them. For example, the record makes\n\nmanifest that she neither reviewed nor responded to her final\n\nprogressive guidance. And she did not challenge (or even inquire\n\nabout) unexcused absences attributed to her when she was notified\n\nfirst of her suspension and later of her termination.\n\n The appellant's failure to pursue these remedial\n\nmeasures sinks her claim of pretext. Where, as here, an employee's\n\nconcerns about the handling of her employment are not raised\n\nthrough reasonable (and reasonably neutral) processes made\n\navailable by her employer and known to her, it is not appropriate\n\nfor a court to second-guess the fairness of individual attendance\n\ndeterminations. Cf. Mesnick, 950 F.2d at 825 (explaining, in\n\ndiscrimination case brought under federal law, that courts do not\n\n\"sit as super personnel departments\").\n\n To say more would be to paint the lily. We conclude\n\nthat the appellant has not satisfied her burden of adducing\n\nevidence sufficient to show that JetBlue's proffered reason for\n\nher dismissal was pretextual. Accordingly, we agree with the\n\ndistrict court that the appellant's handicap discrimination claims\n\ncannot survive summary judgment.\n\n 2. Retaliation. The district court also granted summary\n\njudgment as to the appellant's claim that JetBlue fired her in\n\n\n - 17 -\n\fretaliation for filing an MCAD complaint. See Miceli, 2018 WL\n\n1524539, at *5. Once again, we employ the McDonnell Douglas\n\nburden-shifting framework as an analytic tool. See Mole v. Univ.\n\nof Mass., 814 N.E.2d 329, 338 (Mass. 2004).\n\n Under applicable state law, see Mass. Gen. Laws ch. 151B,\n\n§ 4(4), a prima facie case of retaliation requires the claimant to\n\nshow that she engaged in protected activity; that she experienced\n\nsome adverse action; and that the protected activity was causally\n\nconnected to the adverse action, see Mole, 814 N.E.2d at 338-39.\n\nThe first and second elements are clearly present: filing an MCAD\n\ncomplaint is protected activity and termination of employment is\n\na classic example of an adverse employment action. See Clifton v.\n\nMass. Bay Transp. Auth., 839 N.E.2d 314, 318 (Mass. 2005); Mole,\n\n814 N.E2d at 338 n.13. The third element, though, is the sticking\n\npoint.\n\n In attempting to show the necessary causal connection\n\nbetween JetBlue's receipt of the MCAD complaint and its termination\n\nof her employment, the appellant relies exclusively on the timing\n\nand sequence of these two events. In the circumstances of this\n\ncase, her reliance is misplaced.\n\n To be sure, an inference of causation may be drawn \"if\n\nadverse action is taken against a satisfactorily performing\n\nemployee in the immediate aftermath of the employer's becoming\n\naware of the employee's protected activity.\" Mole, 814 N.E.2d at\n\n\n - 18 -\n\f339. But when \"problems with an employee predate any knowledge\n\nthat the employee has engaged in protected activity, it is not\n\npermissible to draw the inference that subsequent adverse actions,\n\ntaken after the employer acquires such knowledge, are motivated by\n\nretaliation.\" Id. at 340.\n\n Our decision in Pearson v. Mass. Bay Transp. Auth., 723\n\nF.3d 36 (1st Cir. 2013), illustrates this point. There, we held\n\nthat a plaintiff alleging retaliation under Chapter 151B failed to\n\nshow a sufficient causal connection at summary judgment because\n\nthe plaintiff's supervisors had recommended his termination before\n\nhe engaged in the protected activity. See id. at 42. Even though\n\nthe employer's final decision to discharge the plaintiff did not\n\noccur until after the protected activity, we concluded that the\n\nplaintiff would have had to show that the outcome would have\n\ndiffered if not for the employer's knowledge of the protected\n\nactivity. See id.\n\n The case at hand fits the Pearson model. At the time\n\nthat the appellant filed her MCAD complaint, she had already\n\naccrued twelve dependability points and, thus, was subject to\n\nsuspension and termination review. The appellant has offered\n\nnothing to suggest that, but for her protected activity, she would\n\nnot have been terminated as a result of this review. In the\n\ncircumstances of this case, timing and sequence, without more, are\n\nnot enough to ground an inference of causation. It follows that\n\n\n - 19 -\n\fthe district court did not err in granting summary judgment on the\n\nappellant's retaliation claim.\n\n B. Motion to Amend.\n\n There is one loose end: the appellant's challenge to\n\nthe district court's denial of her motion to amend her complaint.\n\nWe review orders granting or denying leave to amend for abuse of\n\ndiscretion. See U.S. ex rel. D'Agostino v. EV3, Inc., 802 F.3d\n\n188, 191 (1st Cir. 2015). Under this deferential standard, we\n\nwill affirm \"so long as the record evinces an arguably adequate\n\nbasis for the court's decision.\" Hatch v. Dep't of Children, Youth\n\n& Their Families, 274 F.3d 12, 19 (1st Cir. 2001).\n\n Where, as here, leave to amend is sought more than\n\ntwenty-one days after service of the complaint and the opposing\n\nparty has not consented, a complaint may be amended only by leave\n\nof court. See Fed. R. Civ. P. 15(a). In general, leave should be\n\nfreely given if, in the court's view, \"justice so requires.\" Id.\n\n15(a)(2). The standard may change, though, when — as in this case\n\n— the court has entered a scheduling order under Federal Rule of\n\nCivil Procedure 16(b), which contains, inter alia, a deadline for\n\namendment of the pleadings. In that event, a motion to amend filed\n\noutside the parameters set by the scheduling order will be granted\n\n\"only upon a showing of 'good cause.'\" D'Agostino, 802 F.3d at\n\n192 (quoting Rule 16(b)(4)); see Cruz v. Bristol-Myers Squibb Co.,\n\nPR, Inc., 699 F.3d 563, 569 (1st Cir. 2012). Such an elevated\n\n\n - 20 -\n\fstandard makes perfect sense: without it, \"scheduling orders would\n\nbe little more than aspirational statements, to be disregarded by\n\nthe parties whenever compliance proves inconvenient.\" D'Agostino,\n\n802 F.3d at 194.\n\n The \"good cause\" standard focuses on both the conduct of\n\nthe moving party and the prejudice, if any, to the nonmovant. See\n\nO'Connell v. Hyatt Hotels of P.R., 357 F.3d 152, 155 (1st Cir.\n\n2004). In the decisional calculus, the moving party's diligence\n\nor lack of diligence serves as the \"dominant criterion.\" Id.\n\n\"[T]he longer a plaintiff delays, the more likely the motion to\n\namend will be denied, as protracted delay, with its attendant\n\nburdens on the opponent and the court, is itself a sufficient\n\nreason for the court to withhold permission to amend.\" Steir v.\n\nGirl Scouts of the USA, 383 F.3d 7, 12 (1st Cir. 2004). Nor should\n\na court be expected to look kindly upon a plaintiff who seeks\n\nbelatedly to amend her complaint based on \"information that [she]\n\nhad or should have had from the outset of the case.\" Trans-Spec\n\nTruck Serv., Inc. v. Caterpillar Inc., 524 F.3d 315, 327 (1st Cir.\n\n2008).\n\n With these principles in mind, we turn to the appellant's\n\nmotion to amend. She filed that motion on July 17, 2017, seeking\n\nto add an FMLA claim approximately twelve months after she\n\ncommenced her civil action and approximately five months after the\n\nRule 16(b) deadline to amend had expired. JetBlue objected, and\n\n\n - 21 -\n\fthe district court denied the motion. It concluded that the\n\nappellant had failed to demonstrate good cause for the delay,\n\nparticularly given that she had referred to the possibility of an\n\nFMLA claim as early as her 2015 MCAD complaint.\n\n The appellant sought reconsideration. She asserted that\n\nshe had learned only during discovery that her termination was\n\npremised in part upon an August 4, 2015, UNA absence. Her new\n\nFMLA claim, she insisted, was spurred by this recently discovered\n\nevidence. The district court reaffirmed its earlier denial of\n\nleave to amend, concluding that the appellant had neither\n\nidentified any newly discovered evidence nor called attention to\n\nany error in the court's prior reasoning.\n\n Like the district court, we find the appellant's\n\nargument unpersuasive. Importantly, the MCAD complaint included\n\nallegations that JetBlue relied on miscoded FMLA absences in\n\nterminating the appellant's employment. Given those allegations,\n\nthere was nothing revelatory in the \"discovery\" of the August 4,\n\n2015, UNA absence. We hold, therefore, that the district court\n\ndid not abuse its discretion in concluding that the appellant\n\nfailed to show that new evidence justified the substantial delay\n\nin bringing her belated FMLA claim. That delay, in turn, lends\n\nweight to the district court's supportable conclusions that the\n\nappellant was not diligent in attempting to pursue her FMLA claim\n\nand, therefore, lacked \"good cause.\" See O'Connell, 357 F.3d at\n\n\n - 22 -\n\f155 (affirming \"good cause\" denial of motion to amend complaint\n\nfive months after scheduling order deadline); Sosa v. Airprint\n\nSys., Inc., 133 F.3d 1417, 1419 (11th Cir. 1998) (per curiam)\n\n(affirming denial of motion to amend because plaintiff, who had\n\nrelevant information \"even before she filed suit,\" lacked \"good\n\ncause\").\n\nIII. CONCLUSION\n\n We need go no further. For the reasons elucidated above,\n\nthe judgment of the district court is\n\n\n\nAffirmed.\n\n\n\n\n - 23 -\n[END_CASE]", "role": "user" } ]
4,586,007
In RE: CELEXA AND LEXAPRO MARKETING AND SALES PRACTICES LITIGATION Painters and Allied Trades District Council 82 Health Care Fund ; Delana S. Kiossovski; Renee Ramirez, on Behalf of Herself and All Others Similarly Situated; Marlene T. Loconte, Plaintiffs, Appellants, Martha Palumbo, Individually and on Behalf of All Other Persons Similarly Situated; Peter Palumbo, Individually and on Behalf of All Other Persons Similarly Situated; Jayne Ehrlich, Individually and on Behalf of All Other Persons Similarly Situated; Anna Murret, Individually and on Behalf of All Other Persons Similarly Situated; Universal Care, Inc.; Angela Jaeckel; Melvin M. Fullmer, on Behalf of Himself and All Others Similarly Situated; New Mexico UFCW Union's and Employer's Health and Welfare Trust Fund, on Behalf of Itself and All Others Similarly Situated; Allied Services Division Welfare Fund, on Behalf of Itself and All Others Similarly Situated; Tara Johndrow, Individually and on Behalf of All Others Similarly Situated; Brian Anson, Individually and on Behalf of All Others Similarly Situated; Scott A. Wilcox, on Behalf of Himself and All Others Similarly Situated; Municipal Reinsurance Health Insurance Fund; Randy Marcus; Bonnie Marcus ; Ruth Dunham; Tanya Shippy; Jill Powell, Plaintiffs, v. Forest Pharmaceuticals, Inc.; Forest Laboratories, Inc.; Forest Laboratories, LLC, Successor in Interest to Forest Laboratories, Inc., Defendants, Appellees, Pfizer, Inc.; Warner Lambert Company, Defendants.
Painters & Allied Trades Dist. Council 82 Health Care Fund v. Forest Pharm., Inc. (In Re Celexa & Lexapro Mktg. & Sales Practices Litig.)
2019-01-30
18-1146P
U.S. Court of Appeals for the First Circuit
{"judges": "Howard, Torruella, Kayatta", "parties": "", "opinions": [{"author": "KAYATTA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\nNos. 18-1146, 18-1147\n\n IN RE: CELEXA AND LEXAPRO MARKETING AND\n SALES PRACTICES LITIGATION\n\n\nPAINTERS AND ALLIED TRADES DISTRICT COUNCIL 82 HEALTH CARE FUND;\n DELANA S. KIOSSOVSKI; RENEE RAMIREZ, on behalf of herself and\n all others similarly situated; MARLENE T. LOCONTE,\n\n Plaintiffs, Appellants,\n\n MARTHA PALUMBO, individually and on behalf of all other persons\nsimilarly situated; PETER PALUMBO, individually and on behalf of\n all other persons similarly situated; JAYNE EHRLICH,\n individually and on behalf of all other persons similarly\n situated; ANNA MURRET, individually and on behalf of all other\n persons similarly situated; UNIVERSAL CARE, INC.; ANGELA\n JAECKEL; MELVIN M. FULLMER, on behalf of himself and all others\n similarly situated; NEW MEXICO UFCW UNION'S AND EMPLOYER'S\n HEALTH AND WELFARE TRUST FUND, on behalf of itself and all\n others similarly situated; ALLIED SERVICES DIVISION WELFARE\n FUND, on behalf of itself and all others similarly situated;\n TARA JOHNDROW, individually and on behalf of all others\n similarly situated; BRIAN ANSON, individually and on behalf of\n all others similarly situated; SCOTT A. WILCOX, on behalf of\nhimself and all others similarly situated; MUNICIPAL REINSURANCE\nHEALTH INSURANCE FUND; RANDY MARCUS; BONNIE MARCUS; RUTH DUNHAM;\n TANYA SHIPPY; JILL POWELL,\n\n Plaintiffs,\n\n v.\n\n FOREST PHARMACEUTICALS, INC.; FOREST LABORATORIES, INC.; FOREST\nLABORATORIES, LLC, successor in interest to Forest Laboratories,\n Inc.,\n\n Defendants, Appellees,\n\n PFIZER, INC.; WARNER LAMBERT COMPANY,\n\f Defendants.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n R. Brent Wisner, with whom Michael L. Baum, Baum, Hedlund,\nAristei & Goldman, P.C., Christopher L. Coffin, and Pendley, Baudin\n& Coffin, LLP were on brief, for appellants.\n Andrew J. Ceresney, with whom Edwin G. Shallert, Kristin D.\nKiehn, J. Robert Abraham, Debevoise & Plimpton LLP, John G.\nO'Neill, and Sugarman, Rogers, Barshak & Cohen, P.C. were on brief,\nfor appellees.\n\n\n January 30, 2019\n\f KAYATTA, Circuit Judge. These consolidated appeals\n\narise out of two so-called \"off-label\" prescription-drug-marketing\n\ncases aggregated for pretrial proceedings in the District of\n\nMassachusetts by order of the multidistrict litigation panel.\n\nPlaintiffs claim that the defendants, Forest Pharmaceuticals, Inc.\n\nand Forest Laboratories, Inc. (collectively \"Forest\"), engaged in\n\nfraud to push their antidepressant drugs on unsuspecting minors\n\nfor whom the FDA had not approved the use of these medications.\n\nAs we will explain, we reverse the dismissal of the claims brought\n\nby two of the four plaintiffs, and we vacate the denial of\n\nplaintiffs' motion to compel the production of additional\n\ndocuments by Forest. We otherwise affirm the challenged district-\n\ncourt rulings, including the denial of class certification.\n\n I.\n\n We begin by summarizing the relevant statutory and\n\nregulatory framework and by reciting the facts relevant to the\n\nplaintiffs' summary-judgment appeal in the light most favorable to\n\nthe plaintiffs. See Boudreau v. Lussier, 901 F.3d 65, 71 (1st\n\nCir. 2018).\n\n A.\n\n The Federal Food, Drug, and Cosmetic Act (\"FDCA\")\n\nrequires drug manufacturers to obtain approval from the U.S. Food\n\nand Drug Administration (\"FDA\") before marketing a drug for a\n\nparticular medical use. 21 U.S.C. § 355(a); see also Mut. Pharm.\n\fCo., Inc. v. Bartlett, 570 U.S. 472, 476 (2013). To secure that\n\napproval, the drug manufacturer must submit to the FDA either a\n\nnew-drug application (\"NDA\") or a supplemental new-drug\n\napplication (\"sNDA\"), and the manufacturer must demonstrate the\n\ndrug's efficacy for the indicated use in at least two double-\n\nblind, randomized-controlled trials (\"DBRCTs\"). See In re\n\nNeurontin Mktg. & Sales Practices Litig. (Kaiser), No. 04-cv-\n\n10739-PBS, 2011 WL 3852254, at *5 (D. Mass. Aug. 31, 2011), aff'd,\n\n712 F.3d 21 (1st. Cir. 2013); see generally 21 C.F.R. § 314.105.\n\nThe FDCA creates both civil and criminal penalties for drug\n\nmanufacturers that promote the use of approved drugs for unapproved\n\nuses (referred to here as \"off-label\" uses). See 21 U.S.C.\n\n§§ 331(d), 333(a), 355(a); Lawton ex rel. United States v. Takeda\n\nPharm. Co., 842 F.3d 125, 128 n.4 (1st Cir. 2016). The FDCA,\n\nhowever, does not prohibit doctors from prescribing drugs for off-\n\nlabel uses. Lawton ex rel. United States, 842 F.3d at 128 n.4.\n\n B.\n\n Forest manufactures and markets prescription drugs,\n\nincluding the antidepressant medications Celexa and Lexapro.\n\nCelexa and Lexapro are chemically similar selective serotonin\n\nreuptake inhibitors (\"SSRIs\"), a class of antidepressants that\n\naffect a patient's mood by blocking the reabsorption of the\n\nneurotransmitter serotonin in the brain, Eli Lilly & Co. v. Teva\n\nPharm. USA, Inc., No. 05-1044, 2005 WL 1635262, at *1 (Fed. Cir.\n\fJuly 13, 2005). The FDA approved Celexa and Lexapro for the\n\ntreatment of major depressive disorder (\"MDD\") in adults (i.e.,\n\nindividuals aged eighteen or over) in 1998 and 2002, respectively.\n\nDrug manufacturers, including Forest, had difficulty demonstrating\n\nthat SSRIs were also effective in treating depression in children\n\nand adolescents. As of 2005, only Fluoxetine -- commercially known\n\nas Prozac -- had gained FDA approval for the treatment of pediatric\n\ndepression. In 2009, the FDA approved Lexapro for the treatment\n\nof depression in adolescents (i.e., individuals of ages twelve\n\nthrough seventeen). The FDA has never approved Celexa for any\n\npediatric use nor has it approved Lexapro as a treatment for\n\ndepression in children (i.e., individuals under the age of twelve).\n\n The record in this case nevertheless strongly suggests\n\nthat Forest engaged in a comprehensive off-label marketing scheme\n\nfrom 1998 through 2009 aimed at fraudulently inducing doctors to\n\nwrite pediatric prescriptions of Celexa and Lexapro when Forest\n\nhad insufficient reason to think that these drugs were effective\n\nfor the treatment of depression in children and adolescents.\n\nPlaintiffs have pointed to substantial evidence that Forest sought\n\nto achieve this illicit aim by: (1) promoting Celexa's efficacy\n\nfor the treatment of pediatric depression at medical conferences,\n\nat continuing-medical-education programs, and in press releases;\n\n(2) concealing negative clinical studies concerning Celexa's\n\nefficacy and safety; and (3) directly encouraging physicians to\n\fprescribe Celexa and Lexapro for the treatment of pediatric\n\ndepression.\n\n For years, Forest nevertheless denied that it was\n\nengaged in the off-label promotion of these drugs. Forest\n\nLaboratories' Executive Vice President, Dr. Lawrence Olanoff,\n\ntestified before Congress in 2004 that \"because the FDA has not\n\napproved pediatric labeling for our products, Forest has always\n\nbeen scrupulous about not promoting the pediatric use of our\n\nantidepressant drugs, Celexa and Lexapro. That is the law, and we\n\nfollow it.\" Publication and Disclosure Issues in Antidepressant\n\nPediatric Clinical Trials: Hearing Before the Subcomm. on\n\nOversight & Investigations of the Comm. on Energy & Commerce, 108th\n\nCong. 82 (2004) (statement of Dr. Lawrence Olanoff).\n\n Even before Dr. Olanoff assured Congress of Forest's\n\nscrupulousness, a whistleblower had commenced a qui tam action,\n\nalleging that Forest had violated the False Claims Act (\"FCA\"), 31\n\nU.S.C. § 3729(a), by fraudulently marketing and promoting Celexa\n\nand Lexapro for the off-label treatment of depression in pediatric\n\npatients. Complaint, Gobble v. Forest Labs., Inc., No. 03-10395-\n\nNMG (D. Mass. Mar. 4, 2003), ECF No. 1. The United States later\n\nintervened in that suit, and, in February 2009, the district court\n\nunsealed the United States' complaint. Order Granting Motion to\n\nUnseal, United States ex rel. Gobble, No. 03-10395-NMG (D. Mass.\n\nFeb. 24, 2009), ECF No. 64. The evidence belying Dr. Olanoff's\n\fassurances to Congress turned out to be quite substantial.\n\nUltimately, in September 2010, Forest paid a $39 million fine in\n\nconnection with pleading guilty to criminal violations of the FDCA\n\nfor its off-label promotion of Celexa between 1998 and 2002 and an\n\nadditional $149 million to the United States to settle civil claims\n\nthat Forest illegally promoted Celexa and Lexapro for pediatric\n\nuse in 2002 through 2005.\n\n C.\n\n Within the following four years, over a dozen consumers\n\nand entities who paid for prescription drugs filed the lawsuits\n\nthat led to this appeal. Initially, four plaintiffs joined in the\n\nnotice of appeal. Only two, Renee Ramirez and the Painters and\n\nAllied Trades District Council 82 Health Care Fund (\"Painters\")\n\nhave presented any argument on appeal. We refer to these two\n\ncollectively as \"plaintiffs.\"1 Ramirez purchased Celexa and\n\nLexapro for her young son from February 2003 through March 2010 on\n\nthe recommendation of her son's neurologist. Painters has\n\nreimbursed its pediatric insureds for off-label prescriptions of\n\nCelexa and Lexapro since early 1999. Plaintiffs together seek\n\n\n\n 1Marlene LoConte and Delena Kiossovski joined in the notice\nof appeal but subsequently filed no brief, and the single brief\nfiled by the other parties contains no argument at all for\nquestioning the grounds upon which the district court dismissed\nthe claims of LoConte and Kiossovski. We therefore deem their\nappeal of the judgments against them to be waived. See Vázquez-\nRivera v. Figueroa, 759 F.3d 44, 46-47 (1st Cir. 2014).\n\frecovery under the Racketeer Influenced and Corrupt Organizations\n\nAct (\"RICO\"), 18 U.S.C. § 1962(c)–(d), the Minnesota Consumer\n\nFraud Act, Minn. Stat. § 325F.69, and the Minnesota Unfair Trade\n\nPractices Act, Minn. Stat. § 325D.13, and for unjust enrichment.\n\n In June 2016, the district court denied Painters' motion\n\nto certify two nationwide classes of similarly situated health-\n\ninsurance companies and health plans that had paid for or\n\nreimbursed off-label pediatric prescriptions of Celexa or Lexapro.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig. (Painters I),\n\n315 F.R.D. 116, 131 (D. Mass. 2016).2 In rejecting class\n\ncertification, the court reasoned that while Painters had\n\nsatisfied the Rule 23(a) numerosity, commonality, typicality, and\n\nadequacy requirements, Painters had failed to establish that\n\ncommon questions of fact or law predominated over individual issues\n\nas required by Rule 23(b)(3). Id. at 123–31.\n\n Subsequently, in March 2017, a dispute arose as a result\n\nof Forest's apparently belated production of two internal\n\nmemoranda in advance of a deposition conducted by agreement after\n\ndiscovery had otherwise closed. The two documents contained\n\n\n\n 2Painters' motion for class certification provided no time\nperiod for the proposed Celexa class. At oral argument, however,\nplaintiffs' counsel clarified that plaintiffs only seek to\nchallenge manufacturer-induced prescriptions for off-label uses\nmade prior to the FDA's approval of Lexapro for adolescent use in\nMarch 2009. Thus, we construe Painters' appeal in accordance with\nthis statement.\n\fdetails regarding a study of Celexa's effectiveness. Forest\n\nrevealed that it had not sought any responsive documents from its\n\nClinical Supply Group in responding to Painters' discovery\n\nrequests. The district court nevertheless denied Painters' motion\n\nto compel Forest's supplemental production of documents from this\n\ngroup, concluding that any such production would be cumulative.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig.\n\n(Painters II), 288 F. Supp. 3d 483, 486–87 (D. Mass. 2018).\n\n In due course, after deeming discovery complete and\n\nruling on various interim motions, the district court entered\n\nsummary judgment for Forest on plaintiffs' RICO claims, holding\n\nthat neither Painters nor Ramirez could demonstrate injury. In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Painters III),\n\n289 F. Supp. 3d 247, 253–56 (D. Mass. 2018). The court then\n\nproceeded to dismiss plaintiffs’ state-based allegations as\n\nderiving from their noncognizable RICO claims. Id. at 258–59.\n\nThis appeal by Painters and Ramirez followed.\n\n II.\n\n Summary judgment is appropriate \"if the movant shows\n\nthat there is no genuine dispute as to any material fact and the\n\nmovant is entitled to judgment as a matter of law.\" Fed. R. Civ.\n\nP. 56(a). In granting summary judgment dismissing all of\n\nplaintiffs' claims, the district court concluded that plaintiffs\n\nhad no competent proof that either Celexa or Lexapro was\n\fineffective for treating depression in children or adolescents.\n\nWe review this conclusion de novo. Martinez v. Petrenko, 792 F.3d\n\n173, 179 (1st Cir. 2015).\n\n A.\n\n Prevailing on a RICO claim requires proof of an economic\n\ninjury. See 18 U.S.C. § 1964(c) (\"Any person injured in his\n\nbusiness or property by reason of a violation of section 1962 of\n\nthis chapter may sue therefor.\"). Plaintiffs allege injury in the\n\nform of payments made for ineffective drugs.3 The district court\n\ntherefore turned its attention to determining whether plaintiffs\n\nhad enough evidence to allow a jury to find Celexa and/or Lexapro\n\nineffective for treating pediatric depression. See Painters III,\n\n289 F. Supp. 3d at 253–56. Four clinical trials and the FDA's\n\n2009 approval of Lexapro for adolescents informed the district\n\ncourt's decision.\n\n Starting in 1997, Lundbeck -- the developer of Celexa -\n\n- began conducting Study 94404, which focused on Celexa's efficacy\n\nin treating depression in adolescents. The study produced across-\n\nthe-board negative results. Forest then conducted Study MD-18 in\n\nan attempt to demonstrate Celexa's effectiveness in both children\n\n\n 3 In its opposition to Forest's motion for summary judgment,\nPainters argued that it need not demonstrate that Celexa and\nLexapro are ineffective in treating pediatric depression to\nestablish RICO injury. The district court rejected this argument\nin its order granting Forest's motion, and Painters has not\ndeveloped any challenge to that ruling on this appeal.\n\fand adolescents. The efficacy results of MD-18 are difficult to\n\nassess because Forest bungled the study: Some participants\n\nrandomized into the active treatment group were dispensed\n\nnongeneric, pink tablets in one portion of the trial, potentially\n\nunblinding both the individuals who received these pills and the\n\nresearchers conducting the study. The MD-18 study only\n\ndemonstrated statistically positive results when these potentially\n\nunblinded participants were included. Finally, in 2002–2004 and\n\n2005-2007, Forest conducted two additional clinical trials. Study\n\nMD-15 examined Lexapro's efficacy in children and adolescents and\n\nachieved negative results. Study MD-32 set out to test Lexapro's\n\neffectiveness in treating only adolescents and achieved\n\nstatistically significant positive results.\n\n Based upon the results of MD-32 and the Celexa MD-18\n\nstudy, Forest submitted an sNDA to the FDA in 2008. In 2009, the\n\nFDA approved the application, allowing Forest to market Lexapro\n\nfor use in adolescents. Forest did not seek such approval for\n\nCelexa.\n\n Plaintiffs' evidence that Celexa and Lexapro were\n\nineffective for the pertinent indications consisted of the\n\nfollowing: The FDA has neither approved Celexa for treating\n\ndepression in children or adolescents nor has it approved Lexapro\n\nfor use in children; Study 94404 demonstrated only a detrimental\n\neffect of Celexa in treating depression in adolescents; Study MD-\n\f18 was corrupted and showed no beneficial effect in children and\n\nadolescents unless the potentially unblinded participants are\n\nincluded in the results; and Study MD-15 produced uniformly\n\nnegative results in testing Lexapro's efficacy in children and\n\nadolescents. In addition, plaintiffs produced expert testimony\n\nopining that the positive results in MD-32 were not of clinical\n\nsignificance and that MD-18 should properly be considered a\n\nnegative trial. Plaintiffs also provided the results of a\n\n2016 meta-analysis study that found that neither Celexa nor\n\nLexapro had any more beneficial effect than a placebo in treating\n\npediatric depression.\n\n There is also evidence in the record before us, however,\n\nthat cuts the other way. In September 2002, the FDA accepted\n\nStudy MD-18 as a positive trial that would support a determination\n\nof Celexa's effectiveness for the treatment of MDD in adolescent\n\npatients. And in January 2003, the FDA also stated that MD-18\n\ncould be employed to support an application for FDA approval \"for\n\nboth Celexa and Lexapro, in pediatric patients with [MDD].\" The\n\nFDA relied in part on these findings in approving Lexapro for the\n\ntreatment of depression in adolescents in March 2009. Further,\n\nForest points out that neither Painters nor Prime Therapeutics\n\n(\"Prime\"), Painters' pharmacy-benefits manager, has taken any\n\neffort to limit or remove from its formulary pediatric\n\nprescriptions of Celexa and Lexapro.\n\f This record raises two questions. First, do the FDA's\n\nvarious pronouncements or actions close the door on any effort to\n\nconvince a jury that either Celexa or Lexapro was ineffective?\n\nSecond, to the extent that the FDA's pronouncements and actions\n\nare not preclusive, is the evidence in this case nevertheless\n\ninsufficient to support a jury finding of ineffectiveness?\n\n 1.\n\n Forest claims that two of our recent decisions --\n\nD'Agostino v. ev3, Inc., 845 F.3d 1 (1st Cir. 2016), and In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Marcus), 779 F.3d\n\n34 (1st Cir. 2015) -- answer the first question in the affirmative\n\nby deeming FDA approval dispositive. Even were we to find it\n\nconvincing, this argument would not cover all the challenged uses\n\nat issue in this appeal. The FDA has never approved Celexa for\n\nany of the off-label uses for which Forest promoted it. Nor has\n\nit approved Lexapro for the treatment of MDD in children under the\n\nage of twelve. So Forest's reliance on actual FDA approval to\n\nforeclose a jury determination of inefficacy must be limited to\n\nForest's marketing of Lexapro for adolescent use and, perhaps as\n\nwell, to the question of how to construe MD-18.\n\n In any event, even as thus limited, we do not find\n\nForest's reliance on D'Agostino convincing. The claim in\n\nD'Agostino concerned the sale of medical devices after the FDA had\n\napproved the devices for the uses for which they were sold.\n\fD'Agostino, 845 F.3d at 3, 7–9. In rejecting a challenge to those\n\npost-approval sales under the False Claims Act based on alleged\n\npre-approval fraud on the FDA, we reasoned that \"[t]o rule\n\notherwise would be to turn the FCA into a tool with which a jury\n\nof six people could retroactively eliminate the value of FDA\n\napproval and effectively require that a product largely be\n\nwithdrawn from the market even when the FDA itself sees no reason\n\nto do so.\" Id. at 8. Here, by contrast, plaintiffs challenge\n\nonly the promotion of Celexa and Lexapro for uses that were off-\n\nlabel (i.e., not FDA-approved) at the time Forest promoted and\n\nsold the drugs.4 When Forest is said to have made those marketing\n\nefforts, it could not have pleaded reliance on FDA approval. If\n\na jury were to hold Forest liable for such pre-approval marketing,\n\nit would simply be telling Forest that it should not have marketed\n\nthat which Congress under the FDCA does not want it to market:\n\ndrugs for unapproved uses. We therefore see no reason to accord\n\nto Forest the preclusive protection for pre-approval promotion\n\nthat FDA approval provided the medical-device manufacturer for\n\npost-approval conduct in D'Agostino.5\n\n\n 4 Though plaintiffs' complaints do not explicitly limit their\nRICO and state-law claims to the period prior to FDA's March 2009\napproval of Lexapro, plaintiffs' counsel indicated at oral\nargument that plaintiffs do not challenge Forest's post-approval\nmarketing of Celexa and Lexapro.\n 5 For similar reasons, Forest's reliance on Buckman Co. v.\nPlaintiffs' Legal Comm., 531 U.S. 341, 348 (2001), in which the\nSupreme Court rejected as preempted state fraud-on-the-FDA claims,\n\f Nor does our opinion in Marcus aid Forest in this case.\n\nIn Marcus, we rejected a challenge to a drug label based on\n\ninformation that was \"plainly known to the FDA prior to approving\n\nthe label.\" 779 F.3d at 43. We made clear in doing so, however,\n\nthat we were merely applying the state-law preemption principles\n\nthe U.S. Supreme Court laid out in PLIVA, Inc. v. Mensing, 564\n\nU.S. 604 (2011), and Wyeth v. Levine, 555 U.S. 555 (2009). See\n\nMarcus, 779 F.3d at 40–43 (explaining that a drug manufacturer can\n\nonly be held liable under state law for inadequate warning in an\n\nFDA-approved label when the drug manufacturer can, \"of its own\n\nvolition, . . . strengthen its label in compliance with its state\n\ntort duty\" (quoting PLIVA, Inc., 564 U.S. at 624)). Marcus,\n\naccordingly, is inapposite.\n\n This is not to say that the FDA's 2009 approval of\n\nForest's sNDA for Lexapro is irrelevant to this case. Certainly\n\nthe approval and the FDA's reliance on MD-18 provide what many\n\njurors may view as strong evidence confirming that Lexapro, and\n\nperhaps Celexa as well, have always been efficacious in treating\n\npediatric depression. The common law has long recognized that\n\nagency approval of this type is relevant in tort suits. See\n\nRestatement (Third) of Torts: Prod. Liab. § 4 (Am. Law Inst. 1998)\n\n\nand its progeny is misplaced. Plaintiffs question the efficacy of\nCelexa and Lexapro only for off-label uses; their claims,\naccordingly, are not predicated on a fraud-on-the-FDA theory of\nliability.\n\f(\"[C]ompliance with an applicable product safety statute . . . is\n\nproperly considered in [a product defect case].\"). But the common\n\nlaw also recognizes that such evidence is not always preclusive.\n\nId. (\"[S]uch compliance does not preclude as a matter of law a\n\nfinding of product defect.\"). And while there are strong reasons\n\nfor treating such evidence as preclusive when the challenged sales\n\nare made in reliance on agency approval, those same reasons cut\n\nthe other way when the sales are made without approval, and\n\ncertainly when made unlawfully, as we must assume they were here.\n\n 2.\n\n Having decided that the FDA's subsequent approval of\n\nLexapro does not preclude proving that pre-approval uses of these\n\ndrugs were ineffective, we turn to addressing whether plaintiffs\n\nmay proceed with a claim based on product ineffectiveness when the\n\nevidence of efficacy is conflicting. This is more or less the\n\nquestion we left unanswered in Kaiser. See Kaiser, 712 F.3d at 49\n\n(declining to address what evidentiary standard would be needed to\n\ndemonstrate efficacy \"if the results of DBRCTs were equivocal\" or\n\n\"if there were a different mix of DBRCT and non-DBRCT evidence\").6\n\n\n 6 To advance its preferred interpretation of the term\n\"equivocal\" in Kaiser, each party dedicates a significant portion\nof its brief to sparring over whether the DBRCT evidence in the\nNeurontin cases was, in fact, mixed. We need not address this\nquestion because, as we explain, Painters' RICO claim survives\nsummary judgment even though the evidence of inefficacy is mixed.\nWe note, however, that the DBRCTs in the Neurontin case were not\nuniformly negative as Forest would have us believe. Rather, the\n\f Generally speaking, \"conflicting evidence\" is the\n\nhallmark of an issue that calls for factfinding, not summary\n\njudgment. See, e.g., Adria Int'l Grp. v. Ferre Dev., Inc., 241\n\nF.3d 103, 111 (1st Cir. 2001) (finding summary judgment\n\ninappropriate when evidence presented was \"contested and\n\ncontradictory\"); see also 10A Charles Alan Wright et al., Federal\n\nPractice and Procedure § 2712 (4th ed. 2018) (\"[S]ummary judgment\n\nis not a substitute for the trial of disputed fact issues.\"). We\n\nsee no reason to deviate from that general rule merely because the\n\nproduct marketed illegally is one that was later approved for\n\nlawful sales.7 In short, why should we forgo customary fact-\n\nfinding by the jury so as to reward unlawful conduct aimed at\n\ngetting children to consume unapproved drugs?\n\n Forest also argues that plaintiffs' evidence of\n\nineffectiveness falls short of proving injury because Painters has\n\nnot produced \"individualized\" proof that Celexa or Lexapro was\n\nineffective for any particular insured. By \"individualized\"\n\nproof, Forest appears to mean testimony from a patient (or from a\n\n\ndistrict court noted both positive and negative clinical studies\nin reviewing the parties' evidence of Neurontin's efficacy for the\nat-issue off-label conditions. See Kaiser, 2011 WL 3852254, at\n*34–46 (reviewing mixed DBRCT results).\n 7\n Nor is summary judgment for Forest warranted due to the fact\nthat Painters has not directed the removal of Celexa and Lexapro\nfor pediatric uses from its drug formulary. As we held in Kaiser,\nit is \"within the factfinder's province to weigh this evidence.\"\nKaiser, 712 F.3d at 41.\n\fdoctor concerning that patient) that the patient experienced no\n\nbeneficial effects from the drug. While evidence of that type\n\ncould be probative, certainly it is not the only way to prove that\n\na drug is ineffective. Indeed, given that (1) an ineffective drug\n\nmay trigger a placebo effect in a given individual and (2) an\n\neffective drug may not benefit all users, individualized proof\n\nmight well be less probative than the type of expert, study-based\n\ntestimony that plaintiffs have offered. In any event, as we\n\nalready held, such individualized proof is certainly not required.\n\nSee In re Neurontin Mtkg. & Sales Practices Litig. (Harden), 712\n\nF.3d 60, 69 (1st Cir. 2013) (\"[W]e reject Pfizer's position that\n\nthese plaintiffs must prove the individual, subjective\n\nineffectiveness of each off-label prescription in order to\n\nestablish injury. . . . The Harden plaintiffs have proffered\n\nclinical trial evidence that Neurontin is ineffective . . ., which\n\nis certainly enough to raise a genuine issue of fact on the\n\neffectiveness issue.\" (citation omitted)); In re Neurontin Mtkg.\n\n& Sales Practices Litig. (Aetna), 712 F.3d 51, 59–60 (1st Cir.\n\n2013).\n\n In sum, we hold that the FDA's 2009 approval of Lexapro\n\ndoes not preclude a jury from concluding that the off-label uses\n\nof Celexa and Lexapro at issue in this case were ineffective in\n\ntreating pediatric depression. Moreover, plaintiffs have provided\n\ncompetent and sufficient evidence -- through DBRCTs, expert\n\ftestimony, and peer-reviewed literature -- to raise a genuine issue\n\nof material fact as to the efficacy of these drugs for pediatric\n\nuse. Accordingly, the district court erred in granting summary\n\njudgment for Forest on plaintiffs' RICO and state-law claims on\n\nthis basis.\n\n B.\n\n In addition to demonstrating economic injury, a RICO\n\nplaintiff must prove that the defendant's racketeering conduct\n\ncaused her injury. 18 U.S.C. § 1964(c); Holmes v. Sec. Inv'r Prot.\n\nCorp., 503 U.S. 258, 268 (1992) (interpreting section 1964(c)'s\n\nlanguage to mean that a RICO plaintiff must show both but-for and\n\nproximate causation to establish standing). As we have already\n\nnoted, physicians can -- and do -- lawfully prescribe prescription\n\ndrugs for off-label uses, even though the manufacturer is barred\n\nby law from promoting such prescriptions. See Lawton ex rel.\n\nUnited States, 842 F.3d at 128 n.4. So for any given prescription\n\nin this case, one would reasonably ask whether Forest's efforts to\n\nprofit by illegally marketing drugs for pediatric use caused a\n\nparticular prescription to be made, or whether, instead, the doctor\n\nwrote a given prescription based on his or her own professional\n\nmedical judgment (perhaps reasoning that what works for an adult\n\npatient might also work for a younger patient).\n\n Forest therefore urges that, even if we disagree with\n\nthe district court on the issue of injury/efficacy, we should still\n\faffirm the entry of summary judgment due to Painters' lack of proof\n\nof but-for causation. While the district court did not consider\n\nthe issue of causation in its summary-judgment ruling, it did\n\nearlier assay Painters' causation evidence in ruling on Painters'\n\nmotion for class certification. The district court labeled the\n\nproof so \"insubstantial\" and \"fundamentally flawed\" \"as to\n\npreclude class certification.\" Painters I, 315 F.R.D. at 126–28.\n\nForest would have us interpret these pronouncements as a finding\n\nthat the evidence was insufficient as a matter of law to prove\n\nbut-for causation.\n\n We disagree. In the first place, it is unclear why the\n\ndistrict court gauged the substantiality or merit of plaintiffs'\n\nproof in the context of a Rule 23 motion. The central issue in\n\nthat context is not whether the method of proof would or could\n\nprevail. Rather, it is whether the method of proof would apply in\n\ncommon to all class members. See, e.g., Tyson Foods, Inc. v.\n\nBouaphakeo, 136 S. Ct. 1036, 1047 (2016) (\"When . . . 'the concern\n\nabout the proposed class is not . . . some fatal dissimilarity\n\nbut, rather, a fatal similarity -- [an alleged] failure of proof\n\nas to an element of the plaintiffs' cause of action -- courts\n\nshould engage that question as a matter of summary judgment, not\n\nclass certification.'\" (alteration in original) (quoting Richard\n\nA. Nagareda, Class Certification in the Age of Aggregate Proof, 84\n\nN.Y.U. L. Rev. 97, 107 (2009))).\n\f More substantively, Painters' evidence does not seem\n\nclearly insufficient. There is ample evidence that Forest spent\n\nmoney inducing doctors to prescribe its drugs to pediatric patients\n\nand that it would not have done so had the effort not been worth\n\nthe money. Two experts, Dr. Meredith Rosenthal and\n\nDr. Christopher Baum, also opined that Forest's spending on\n\npromotions in general correlated positively with sales. As the\n\ndistrict court pointed out, Painters' experts then assumed that\n\nthis same approximate correlation applied to off-label promotional\n\nspending and off-label sales. Painters I, 315 F.R.D. at 127. The\n\ndistrict court thought this assumption to be a \"fundamental flaw\"\n\nin the analysis. Id. Why, exactly, we are not sure. After all,\n\nwhy would Forest, which knew its markets better than anyone, have\n\nspent money on off-label marketing over the long term if it\n\ngenerated lower returns than would additional spending on less\n\nrisky, lawful marketing? Certainly there is room for reasonable\n\ndisagreement on the merits of Dr. Rosenthal and Dr. Baum's\n\nassumption.\n\n If the jury accepts this assumption as reasonable, and\n\nif it finds that the prescriptions that Painters paid for were\n\ntypical of those that the experts analyzed, jurors would then have\n\na fair path to finding that Forest's off-label marketing caused\n\nPainters to pay for ineffective drugs. The experts' interpretation\n\nof the data indicated that Forest's off-label promotions caused\n\f76% and 54% of all pediatric prescriptions of Celexa and Lexapro,\n\nrespectively. Dr. Rosenthal estimated that if Painters paid for\n\nas few as five independent prescriptions, there would be a 98%\n\nchance that at least one was the result of off-label marketing.\n\nIn fact, Painters likely paid for the Celexa or Lexapro\n\nprescriptions of more than five different patients.8 So the odds\n\nthat Painters was not harmed if the drugs were, indeed, ineffective\n\nwas likely infinitesimal (assuming the prescriptions were\n\nindependent of one another).9\n\n\n\n\n 8In its summary judgment order, the district judge observed\nthat Painters reimbursed sixteen of its pediatric insureds for\nseventy-two off-label prescriptions of Celexa from 1999 through\n2004, and thirty-one of its pediatric insureds for 234 off-label\nprescriptions of Lexapro from 2002 through early 2015. Painters\nIII, 289 F. Supp. 3d at 251. It is not clear from the record how\nmany of these Lexapro prescriptions were written prior to March\n2009. Viewing this evidence in the light most favorable to\nPainters, Ellis v. Fidelity Mgmt. Tr. Co., 883 F.3d 1, 3, (1st\nCir. 2018), and without any counter-argument on this point by\nForest, we assume for purposes of this appeal only that well more\nthan five of the aforementioned Lexapro prescriptions were filled\nprior to the FDA's 2009 approval of Lexapro.\n 9The statistical proof in this instance is being used only\nto prove that a group of prescriptions likely includes at least\none that a certain activity caused, and it is then being utilized\nto estimate the percentage of such causally connected\nprescriptions in that group. Painters proposes no use of the\nstatistical data to prove that Forest's off-label marketing caused\nany particular prescription to be written. See In re Asacol\nAntitrust Litig. (Asacol), 907 F.3d 42, 54 (1st Cir. 2018) (finding\nit \"far from self-evident\" that expert testimony opining that\n\"ninety percent of class members were injured\" would be \"sufficient\nto prove that any given individual class member was injured\").\n\f Nor is Painters' evidence limited to the thrust of its\n\nstatistics. Painters also has evidence that Forest sales\n\nrepresentatives called or visited at least two physicians who\n\nsubsequently ordered pediatric prescriptions of Celexa and Lexapro\n\nthat Painters reimbursed. In addition, Painters produced evidence\n\nsuggesting that Forest specifically targeted Painters' pharmacy-\n\nbenefits manager, Prime, and that Prime relied upon a misleading\n\nreport by Forest of Study MD-18 in managing Painters' formulary.\n\nAll together, this is surely enough to raise a triable issue of\n\nfact as to whether Forest's off-label marketing caused Painters to\n\npay for a prescription for which it would not have otherwise paid.\n\n This is not to say that Painters will ultimately prevail\n\non the issue of causation. The district court has not conducted\n\na Daubert analysis. And there may be other potential bones to\n\npick with the sufficiency of Painters' proof of causation. As the\n\nrecord now stands, though, we agree with Painters that we cannot\n\naffirm the summary judgment finding that its causation proof is\n\ninsufficient as a matter of law.\n\n As for Ramirez, Forest did not challenge her standing on\n\nthe basis of causation in its memorandum in support of its motion\n\nfor summary judgment. Accordingly, we express no opinion as to\n\nwhether Ramirez has raised a triable issue on RICO causation. See\n\nRosaura Bldg. Corp. v. Municipality of Mayagüez, 778 F.3d 55, 63\n\f(1st Cir. 2015) (\"Time and time again we have held that arguments\n\nnot advanced before the district court are waived.\").\n\n As for proximate causation, it is of no moment that\n\npediatricians were the immediate target of Forest's fraudulent\n\nmarketing. Here, as in Kaiser, a jury could find that Painters\n\nand Ramirez were \"the primary and intended victims of [Forest's]\n\nscheme to defraud.\" Kaiser, 712 F.3d at 37 (quoting Bridge v.\n\nPhx. Bond & Indem. Co., 553 U.S. 639, 650 (2008)). Moreover,\n\nPainters' and Ramirez's alleged harm (i.e., reimbursing or\n\npurchasing more pediatric prescriptions than they otherwise would\n\nhave) was a \"foreseeable and natural consequence\" of Forest's\n\nscheme. Bridge, 553 U.S. at 658. Indeed, it was precisely the\n\npoint.\n\n Accordingly, for the foregoing reasons, we reverse the\n\ndistrict court's entry of summary judgment for Forest on Painters'\n\nRICO and state-law claims and on Ramirez's RICO and unjust-\n\nenrichment claims.\n\n III.\n\n Early on in this litigation the district court denied\n\nPainters' motion to certify this case as a class action under\n\nFederal Rule of Civil Procedure 23(b)(3). In so ruling, the\n\ndistrict court reasoned that a variety of important issues,\n\nincluding causation and injury, would pose individual questions\n\nthat would need to be answered for each class member. Painters I,\n\f315 F.R.D. at 123–30. The presence of these individual questions,\n\nreasoned the district court, defeated Painters' effort to satisfy\n\nthe requirement of Rule 23(b)(3) that common issues must\n\npredominate. Id. Painters now appeals that ruling as it applies\n\nto classes consisting of third-party payors (\"TPP\") who paid for\n\nor reimbursed prescriptions of Celexa or Lexapro prior to early\n\n2009. It is not clear why those issues to which the district court\n\npointed would preclude certification of such a class. As we have\n\nalready explained, Painters' clinical and statistical evidence, if\n\nbelieved, could establish causation and injury at least for any\n\nTPP who paid for more than a handful of different patients'\n\nprescriptions. Nevertheless, as we will explain, it has become\n\napparent that the proper application of the statute of limitations,\n\nwhile preserving plaintiffs' individual claims, precludes\n\nPainters' attempt to maintain a class action.\n\n A.\n\n The parties agree that the applicable statutory\n\nlimitations period is four years. See Agency Holding Corp. v.\n\nMalley-Duff & Assocs., Inc., 483 U.S. 143, 156 (1987). That four-\n\nyear period began to run \"at the time [the] plaintiff knew or\n\nshould have known of his injury.\" Lares Grp., II v. Tobin, 221\n\nF.3d 41, 44 (1st Cir. 2000) (citing Rodriguez v. Banco Central,\n\n917 F.2d 664, 665 (1st Cir. 1990)). The injury here is the payment\n\nmade on account of off-label prescriptions that Forest induced.\n\fSee Kaiser, 712 F.3d at 39 (\"[E]conomic injury occur[s] when\n\n[plaintiff] paid for fraudulently induced [drug] prescriptions.\").\n\nSo, the key question becomes: By what date can we say, as a matter\n\nof law, that Painters knew or should have known that Forest was\n\npromoting the off-label, ineffective use of Celexa or Lexapro?\n\n The district court found that date to be no later than\n\nMarch of 2009. In re Celexa & Lexapro Mktg. & Sales Practices\n\nLitig., 65 F. Supp. 3d 283, 289 (D. Mass. 2014). In February of\n\nthat year, the United States unsealed its complaint against Forest\n\nin United States ex rel. Gobble, which detailed in thirty-three\n\npages how \"Forest engaged in a fraudulent scheme to market and\n\npromote Celexa . . . and Lexapro . . . off-label to treat\n\ndepression and other psychiatric conditions in pediatric\n\npatients.\" Complaint at 2, United States ex rel. Gobble, No. 03-\n\n10395-NMG (D. Mass. Feb. 13, 2009), ECF No. 61 [hereinafter United\n\nStates' Complaint]. Within weeks, two private class-action\n\ncomplaints followed, one in New York and another in Missouri, each\n\nalso alleging a fraudulent scheme to market Celexa and Lexapro for\n\nineffective, off-label uses. See Class Action Complaint,\n\nUniversal Care, Inc. v. Forest Pharm., Inc., No. 09-cv-11518-NMG\n\n(D. Mass. Mar. 20, 2009), ECF No. 1; Class Action Complaint, N.M.\n\nUFCW Union's & Emp'rs' Health & Welfare Tr. Fund v. Forest Labs.,\n\nInc., No. 09-cv-11524-NMG (D. Mass. Mar. 12, 2009), ECF No. 1.\n\nPainters never argued before the district court that it was unaware\n\fof the United States' complaint or the March 2009 lawsuits. Nor\n\ndoes it so argue on appeal. Rather, it argues that the lawsuits\n\ndid not provide enough notice that Forest had been promoting the\n\noff-label use of Celexa and Lexapro. Such notice, Painters says,\n\nwas not available until Forest's own public admission to that\n\neffect in November 2010, when it both pleaded guilty to criminal\n\nviolations of the FDCA and entered into a civil settlement\n\nagreement with the United States.\n\n Not surprisingly, Painters points to no case law holding\n\nthat a statutory limitations period does not start to run until\n\nthe potential defendant first delivers a gift-wrapped admission of\n\nits alleged wrongdoing. Were that the rule, very few limitations\n\nperiods would ever commence, much less conclude. Instead, as we\n\nhave explained in an analogous context, \"[w]e look first to whether\n\nsufficient facts were available to provoke a reasonable person in\n\nthe plaintiff's circumstances to inquire or investigate\n\nfurther. . . . Once a duty to inquire is established, the\n\nplaintiff is charged with the knowledge of what he or she would\n\nhave uncovered through a reasonably diligent investigation.\"\n\nMcIntyre v. United States, 367 F.3d 38, 52 (1st Cir. 2004); see\n\nalso Sanchez v. United States, 740 F.3d 47, 52 (1st Cir. 2014)\n\n(\"The discovery rule incorporates an objective standard. To delay\n\ncommencement of the running of the statute of limitations, 'the\n\nfactual basis for the cause of action must have been inherently\n\funknowable, [that is, not capable of detection through the exercise\n\nof reasonable diligence] at the time of injury.'\" (alteration in\n\noriginal) (quoting Gonzalez v. United States, 284 F.3d 281, 288–\n\n89 (1st Cir. 2002))). The same fundamental principle applies to\n\nRICO suits. See Rotella v. Wood, 528 U.S. 549, 555 (2000)\n\n(\"Federal courts . . . generally apply a discovery accrual rule\n\nwhen a statute is silent on the issue, as civil RICO is here. . . .\n\n[D]iscovery of the injury . . . is what starts the clock.\"\n\n(citations omitted)); Koch v. Christie's Int'l PLC, 699 F.3d 141,\n\n150–51 (2d Cir. 2012) (noting that a RICO claim does not accrue\n\nuntil a plaintiff has \"actual or inquiry notice of the injury\"\n\n(quoting In re Merrill Lynch Ltd. P'ships Litig., 154 F.3d 56, 60\n\n(2d Cir. 1998))).\n\n We agree with the district court that the unsealing of\n\nthe United States' complaint and the subsequent lawsuits filed in\n\nMarch 2009 were more than sufficient to put a TPP like Painters on\n\nnotice that Forest had likely been inducing off-label\n\nprescriptions of Celexa and Lexapro. The United States' complaint\n\nchronicled how Forest suppressed a negative study on Celexa while\n\npromoting a positive study (which conveniently neglected to\n\nmention the earlier, negative study). United States' Complaint at\n\n3, 14. The complaint quoted internal Forest communications and\n\nrecounted the precise details of Forest's unlawful promotional\n\nactivities. Id. at 15–22. It quoted Forest's physician-call notes\n\freporting on the efforts of Forest's sales representatives to\n\npromote the pediatric use of the drugs. E.g., id. at 20 (\"[F]ocus\n\non Lexapro efficacy at just 10 mg., great choice for\n\nchild/adolescents.\"). It also named Forest marketing executives,\n\ne.g., id. at 23, and outside physicians involved in the promotion\n\ncampaigns, e.g., id. at 21–22. It is inconceivable that any TPP\n\nlike Painters would not have found in the complaint a very strong\n\nprobability that Forest had systematically and fraudulently pushed\n\nits drugs on unsuspecting children.\n\n Nevertheless, we also agree with the district court that\n\nPainters survived Forest's statute-of-limitations defense because\n\nthe running of the limitations period was stayed for more than\n\neight months by the filing of the N.M. UFCW class action in March\n\n2009. See In re Celexa & Lexapro Mktg. & Sales Practices Litig.,\n\n65 F. Supp. 3d at 291. Painters was a member of the putative RICO\n\nclass action for which the N.M. UFCW complaint sought\n\ncertification. Under American Pipe & Construction Co. v. Utah,\n\n414 U.S. 538 (1974), the limitations period during which Painters\n\nmight sue on its own behalf was therefore tolled until the N.M.\n\nUFCW class action was dismissed in June 2010. Forest did not cross\n\nappeal the district court's application of American Pipe. Rather,\n\nForest argues only that the limitations period began running long\n\nbefore March of 2009 when plaintiffs first should have suspected\n\nthat Celexa and Lexapro were ineffective for pediatric use. We\n\freject that argument because the injury here is paying for\n\nunlawfully induced off-label prescriptions, not merely physician-\n\ndirected, off-label prescriptions.\n\n B.\n\n Even though plaintiffs can sue, thanks to American Pipe,\n\nPainters cannot parlay that dispensation into the much-delayed\n\nfiling of a class action. See China Agritech, Inc. v. Resh, 138\n\nS. Ct. 1800 (2018). In American Pipe, the Supreme Court held that\n\nthe \"commencement of [a putative class action] tolls the running\n\nof the statute for all purported members of the class who make\n\ntimely motions to intervene after the court has found the suit\n\ninappropriate for class action status.\" 414 U.S. at 552-53. China\n\nAgritech clarified that this tolling rule has limits: While a\n\nputative class member may join an existing suit or file an\n\nindividual action upon denial of class certification, a putative\n\nclass member may not commence a class action anew beyond the time\n\nallowed by the untolled statute of limitations. 138 S. Ct. at\n\n1807 (\"The 'efficiency and economy of litigation' that support\n\ntolling of individual claims do not support maintenance of untimely\n\nsuccessive class actions; any additional class filings should be\n\nmade early on, soon after the commencement of the first action\n\nseeking class certification.\" (citation omitted) (quoting Am.\n\nPipe, 414 U.S. at 553)).\n\f Painters argues that China Agritech is distinguishable\n\nfrom the case at hand because there was no substantive ruling on\n\nclass certification in N.M. UFCW; the first time any district court\n\naddressed class certification was in Painters' case. Painters'\n\nposition relies on an impermissibly narrow reading of the Court's\n\ndecision in China Agritech. Though the Supreme Court granted\n\ncertiorari in that case to answer the narrow question of whether\n\na putative class member may commence a class action beyond the\n\nlimitations period upon the district court's denial of a request\n\nfor class certification filed within the statute of limitations,\n\nid. at 1804, the Court proceeded to provide a broader answer: Its\n\nprecedents do not \"so much as hint[] that [American Pipe] tolling\n\nextends to otherwise time-barred class claims,\" id. at 1806. Thus,\n\nthe Court effectively ruled that the tolling effect of a motion to\n\ncertify a class applies only to individual claims, no matter how\n\nthe motion is ultimately resolved. To hold otherwise would be to\n\nallow a chain of withdrawn class-action suits to extend the\n\nlimitations period forever.\n\n For the foregoing reasons, the district court did not\n\nabuse its discretion in declining to certify Painters' proposed\n\nnationwide class of TPPs.\n\n IV.\n\n Finally, Painters also takes issue with the district\n\ncourt's denial of its motion to compel Forest's supplemental\n\fproduction of documents related to the MD-18 Study. This court\n\nreviews a district court's discovery decision for abuse of\n\ndiscretion, intervening \"only upon a clear showing of manifest\n\ninjustice, that is, where the lower court's discovery order was\n\nplainly wrong and resulted in substantial prejudice to the\n\naggrieved party.\" Pina v. Children's Place, 740 F.3d 785, 791\n\n(1st Cir. 2014) (quoting Dennis v. Osram Sylvania, Inc., 549 F.3d\n\n851, 859 (1st Cir. 2008)).\n\n Here, it is undisputed that Forest did not perform an\n\nexhaustive search in response to Painters' requests for documents\n\nrelated to the MD-18 Study: Indeed, Forest acknowledges\n\n(employing the passive voice) that \"files within the custody of\n\nthe Clinical Supply Group were not searched.\" Forest also does\n\nnot deny that its own preliminary search within this group -- after\n\ndiscovery had closed -- produced two responsive memoranda\n\nregarding the packaging error in the MD-18 Study. The only excuse\n\nForest provides is that \"[p]laintiffs were fully apprised of the\n\nscope of document collection and were aware that files within the\n\ncustody of the Clinical Supply Group were not searched.\" Forest,\n\nhowever, points us to nothing in the record demonstrating that\n\nPainters acquiesced to Forest's limiting the scope of its document\n\ncollection in this way. These admissions notwithstanding, the\n\ndistrict court denied Painters' Rule 37 motion to compel the\n\nsupplementary production of documents related to the MD-18 Study.\n\fIt reasoned that the Rule 26(e)(1) duty to supplement only applies\n\nwhen \"the supplemental material has not been otherwise made known\n\nto the requesting party\" and observed that Painters had already\n\nreceived \"substantial production of documents related to the\n\npackaging error\" such that any new production would be cumulative.\n\nPainters II, 288 F. Supp. 3d at 487.\n\n Rule 26(e)(1) requires that a party who has responded to\n\na request for production supplement its response in a timely manner\n\n\"if the party learns that in some material respect the . . .\n\nresponse is incomplete . . . and if the additional . . .\n\ninformation has not otherwise been made known to the other parties\n\nduring the discovery process.\" Fed. R. Civ. P. 26(e)(1). Whether\n\nor not \"information has not otherwise been made known\" -- and,\n\nthus, whether or not additional production would be cumulative --\n\nnecessarily hinges on the relevance that the additional production\n\nmight have for the requesting party's claims and the complexity of\n\nthe issue that the factfinder is tasked to resolve; clearly, a\n\nrelatively high degree of granularity in document production is to\n\nbe expected in technical matters of great significance to a party's\n\noverall claim.\n\n The district court viewed FDA approval as being\n\npreclusive as to the validity of Studies MD-18 and MD-32. See\n\nPainters III, 289 F. Supp. 3d at 255–56. It also viewed the\n\nvalidity of those two studies as fatal to plaintiffs' attempt to\n\fprove ineffectiveness with the type of evidence used in Neurontin.\n\nSee id. Given those views, the district court understandably\n\ndecided that further evidence on the question of effectiveness was\n\ncumulative and of no material import. See Painters II, 288 F.\n\nSupp. 3d at 487. Because we have now explained why the FDA's\n\napproval of Lexapro for its use in adolescents is not as preclusive\n\nas the district court might have reasonably thought, and because\n\nPainters and Ramirez have a live claim on the merits, one might\n\nreasonably expect Forest to search for responsive files within the\n\n\"Clinical Supply Group.\" Accordingly, we vacate the district\n\ncourt's discovery ruling so that on remand it can consider whether\n\nfurther discovery is called for in view of our decision in this\n\nappeal.\n\n V. Conclusion\n\n For the foregoing reasons, we reverse the district\n\ncourt's entry of summary judgment for Forest on Painters' and\n\nRamirez's RICO and state-law claims and vacate the district court's\n\ndenial of Painters' Rule 37 motion to compel supplemental\n\ndiscovery. At the same time, we affirm the district court's denial\n\nof Painters' motion for class certification. We award no costs to\n\nany party.", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363260/", "author_raw": "KAYATTA, Circuit Judge"}]}
HOWARD
TORRUELLA
KAYATTA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586007/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: In RE: CELEXA AND LEXAPRO MARKETING AND SALES PRACTICES LITIGATION Painters and Allied Trades District Council 82 Health Care Fund ; Delana S. Kiossovski; Renee Ramirez, on Behalf of Herself and All Others Similarly Situated; Marlene T. Loconte, Plaintiffs, Appellants, Martha Palumbo, Individually and on Behalf of All Other Persons Similarly Situated; Peter Palumbo, Individually and on Behalf of All Other Persons Similarly Situated; Jayne Ehrlich, Individually and on Behalf of All Other Persons Similarly Situated; Anna Murret, Individually and on Behalf of All Other Persons Similarly Situated; Universal Care, Inc.; Angela Jaeckel; Melvin M. Fullmer, on Behalf of Himself and All Others Similarly Situated; New Mexico UFCW Union's and Employer's Health and Welfare Trust Fund, on Behalf of Itself and All Others Similarly Situated; Allied Services Division Welfare Fund, on Behalf of Itself and All Others Similarly Situated; Tara Johndrow, Individually and on Behalf of All Others Similarly Situated; Brian Anson, Individually and on Behalf of All Others Similarly Situated; Scott A. Wilcox, on Behalf of Himself and All Others Similarly Situated; Municipal Reinsurance Health Insurance Fund; Randy Marcus; Bonnie Marcus ; Ruth Dunham; Tanya Shippy; Jill Powell, Plaintiffs, v. Forest Pharmaceuticals, Inc.; Forest Laboratories, Inc.; Forest Laboratories, LLC, Successor in Interest to Forest Laboratories, Inc., Defendants, Appellees, Pfizer, Inc.; Warner Lambert Company, Defendants.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\nNos. 18-1146, 18-1147\n\n IN RE: CELEXA AND LEXAPRO MARKETING AND\n SALES PRACTICES LITIGATION\n\n\nPAINTERS AND ALLIED TRADES DISTRICT COUNCIL 82 HEALTH CARE FUND;\n DELANA S. KIOSSOVSKI; RENEE RAMIREZ, on behalf of herself and\n all others similarly situated; MARLENE T. LOCONTE,\n\n Plaintiffs, Appellants,\n\n MARTHA PALUMBO, individually and on behalf of all other persons\nsimilarly situated; PETER PALUMBO, individually and on behalf of\n all other persons similarly situated; JAYNE EHRLICH,\n individually and on behalf of all other persons similarly\n situated; ANNA MURRET, individually and on behalf of all other\n persons similarly situated; UNIVERSAL CARE, INC.; ANGELA\n JAECKEL; MELVIN M. FULLMER, on behalf of himself and all others\n similarly situated; NEW MEXICO UFCW UNION'S AND EMPLOYER'S\n HEALTH AND WELFARE TRUST FUND, on behalf of itself and all\n others similarly situated; ALLIED SERVICES DIVISION WELFARE\n FUND, on behalf of itself and all others similarly situated;\n TARA JOHNDROW, individually and on behalf of all others\n similarly situated; BRIAN ANSON, individually and on behalf of\n all others similarly situated; SCOTT A. WILCOX, on behalf of\nhimself and all others similarly situated; MUNICIPAL REINSURANCE\nHEALTH INSURANCE FUND; RANDY MARCUS; BONNIE MARCUS; RUTH DUNHAM;\n TANYA SHIPPY; JILL POWELL,\n\n Plaintiffs,\n\n v.\n\n FOREST PHARMACEUTICALS, INC.; FOREST LABORATORIES, INC.; FOREST\nLABORATORIES, LLC, successor in interest to Forest Laboratories,\n Inc.,\n\n Defendants, Appellees,\n\n PFIZER, INC.; WARNER LAMBERT COMPANY,\n\f Defendants.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n R. Brent Wisner, with whom Michael L. Baum, Baum, Hedlund,\nAristei & Goldman, P.C., Christopher L. Coffin, and Pendley, Baudin\n& Coffin, LLP were on brief, for appellants.\n Andrew J. Ceresney, with whom Edwin G. Shallert, Kristin D.\nKiehn, J. Robert Abraham, Debevoise & Plimpton LLP, John G.\nO'Neill, and Sugarman, Rogers, Barshak & Cohen, P.C. were on brief,\nfor appellees.\n\n\n January 30, 2019\n\f KAYATTA, Circuit Judge. These consolidated appeals\n\narise out of two so-called \"off-label\" prescription-drug-marketing\n\ncases aggregated for pretrial proceedings in the District of\n\nMassachusetts by order of the multidistrict litigation panel.\n\nPlaintiffs claim that the defendants, Forest Pharmaceuticals, Inc.\n\nand Forest Laboratories, Inc. (collectively \"Forest\"), engaged in\n\nfraud to push their antidepressant drugs on unsuspecting minors\n\nfor whom the FDA had not approved the use of these medications.\n\nAs we will explain, we reverse the dismissal of the claims brought\n\nby two of the four plaintiffs, and we vacate the denial of\n\nplaintiffs' motion to compel the production of additional\n\ndocuments by Forest. We otherwise affirm the challenged district-\n\ncourt rulings, including the denial of class certification.\n\n I.\n\n We begin by summarizing the relevant statutory and\n\nregulatory framework and by reciting the facts relevant to the\n\nplaintiffs' summary-judgment appeal in the light most favorable to\n\nthe plaintiffs. See Boudreau v. Lussier, 901 F.3d 65, 71 (1st\n\nCir. 2018).\n\n A.\n\n The Federal Food, Drug, and Cosmetic Act (\"FDCA\")\n\nrequires drug manufacturers to obtain approval from the U.S. Food\n\nand Drug Administration (\"FDA\") before marketing a drug for a\n\nparticular medical use. 21 U.S.C. § 355(a); see also Mut. Pharm.\n\fCo., Inc. v. Bartlett, 570 U.S. 472, 476 (2013). To secure that\n\napproval, the drug manufacturer must submit to the FDA either a\n\nnew-drug application (\"NDA\") or a supplemental new-drug\n\napplication (\"sNDA\"), and the manufacturer must demonstrate the\n\ndrug's efficacy for the indicated use in at least two double-\n\nblind, randomized-controlled trials (\"DBRCTs\"). See In re\n\nNeurontin Mktg. & Sales Practices Litig. (Kaiser), No. 04-cv-\n\n10739-PBS, 2011 WL 3852254, at *5 (D. Mass. Aug. 31, 2011), aff'd,\n\n712 F.3d 21 (1st. Cir. 2013); see generally 21 C.F.R. § 314.105.\n\nThe FDCA creates both civil and criminal penalties for drug\n\nmanufacturers that promote the use of approved drugs for unapproved\n\nuses (referred to here as \"off-label\" uses). See 21 U.S.C.\n\n§§ 331(d), 333(a), 355(a); Lawton ex rel. United States v. Takeda\n\nPharm. Co., 842 F.3d 125, 128 n.4 (1st Cir. 2016). The FDCA,\n\nhowever, does not prohibit doctors from prescribing drugs for off-\n\nlabel uses. Lawton ex rel. United States, 842 F.3d at 128 n.4.\n\n B.\n\n Forest manufactures and markets prescription drugs,\n\nincluding the antidepressant medications Celexa and Lexapro.\n\nCelexa and Lexapro are chemically similar selective serotonin\n\nreuptake inhibitors (\"SSRIs\"), a class of antidepressants that\n\naffect a patient's mood by blocking the reabsorption of the\n\nneurotransmitter serotonin in the brain, Eli Lilly & Co. v. Teva\n\nPharm. USA, Inc., No. 05-1044, 2005 WL 1635262, at *1 (Fed. Cir.\n\fJuly 13, 2005). The FDA approved Celexa and Lexapro for the\n\ntreatment of major depressive disorder (\"MDD\") in adults (i.e.,\n\nindividuals aged eighteen or over) in 1998 and 2002, respectively.\n\nDrug manufacturers, including Forest, had difficulty demonstrating\n\nthat SSRIs were also effective in treating depression in children\n\nand adolescents. As of 2005, only Fluoxetine -- commercially known\n\nas Prozac -- had gained FDA approval for the treatment of pediatric\n\ndepression. In 2009, the FDA approved Lexapro for the treatment\n\nof depression in adolescents (i.e., individuals of ages twelve\n\nthrough seventeen). The FDA has never approved Celexa for any\n\npediatric use nor has it approved Lexapro as a treatment for\n\ndepression in children (i.e., individuals under the age of twelve).\n\n The record in this case nevertheless strongly suggests\n\nthat Forest engaged in a comprehensive off-label marketing scheme\n\nfrom 1998 through 2009 aimed at fraudulently inducing doctors to\n\nwrite pediatric prescriptions of Celexa and Lexapro when Forest\n\nhad insufficient reason to think that these drugs were effective\n\nfor the treatment of depression in children and adolescents.\n\nPlaintiffs have pointed to substantial evidence that Forest sought\n\nto achieve this illicit aim by: (1) promoting Celexa's efficacy\n\nfor the treatment of pediatric depression at medical conferences,\n\nat continuing-medical-education programs, and in press releases;\n\n(2) concealing negative clinical studies concerning Celexa's\n\nefficacy and safety; and (3) directly encouraging physicians to\n\fprescribe Celexa and Lexapro for the treatment of pediatric\n\ndepression.\n\n For years, Forest nevertheless denied that it was\n\nengaged in the off-label promotion of these drugs. Forest\n\nLaboratories' Executive Vice President, Dr. Lawrence Olanoff,\n\ntestified before Congress in 2004 that \"because the FDA has not\n\napproved pediatric labeling for our products, Forest has always\n\nbeen scrupulous about not promoting the pediatric use of our\n\nantidepressant drugs, Celexa and Lexapro. That is the law, and we\n\nfollow it.\" Publication and Disclosure Issues in Antidepressant\n\nPediatric Clinical Trials: Hearing Before the Subcomm. on\n\nOversight & Investigations of the Comm. on Energy & Commerce, 108th\n\nCong. 82 (2004) (statement of Dr. Lawrence Olanoff).\n\n Even before Dr. Olanoff assured Congress of Forest's\n\nscrupulousness, a whistleblower had commenced a qui tam action,\n\nalleging that Forest had violated the False Claims Act (\"FCA\"), 31\n\nU.S.C. § 3729(a), by fraudulently marketing and promoting Celexa\n\nand Lexapro for the off-label treatment of depression in pediatric\n\npatients. Complaint, Gobble v. Forest Labs., Inc., No. 03-10395-\n\nNMG (D. Mass. Mar. 4, 2003), ECF No. 1. The United States later\n\nintervened in that suit, and, in February 2009, the district court\n\nunsealed the United States' complaint. Order Granting Motion to\n\nUnseal, United States ex rel. Gobble, No. 03-10395-NMG (D. Mass.\n\nFeb. 24, 2009), ECF No. 64. The evidence belying Dr. Olanoff's\n\fassurances to Congress turned out to be quite substantial.\n\nUltimately, in September 2010, Forest paid a $39 million fine in\n\nconnection with pleading guilty to criminal violations of the FDCA\n\nfor its off-label promotion of Celexa between 1998 and 2002 and an\n\nadditional $149 million to the United States to settle civil claims\n\nthat Forest illegally promoted Celexa and Lexapro for pediatric\n\nuse in 2002 through 2005.\n\n C.\n\n Within the following four years, over a dozen consumers\n\nand entities who paid for prescription drugs filed the lawsuits\n\nthat led to this appeal. Initially, four plaintiffs joined in the\n\nnotice of appeal. Only two, Renee Ramirez and the Painters and\n\nAllied Trades District Council 82 Health Care Fund (\"Painters\")\n\nhave presented any argument on appeal. We refer to these two\n\ncollectively as \"plaintiffs.\"1 Ramirez purchased Celexa and\n\nLexapro for her young son from February 2003 through March 2010 on\n\nthe recommendation of her son's neurologist. Painters has\n\nreimbursed its pediatric insureds for off-label prescriptions of\n\nCelexa and Lexapro since early 1999. Plaintiffs together seek\n\n\n\n 1Marlene LoConte and Delena Kiossovski joined in the notice\nof appeal but subsequently filed no brief, and the single brief\nfiled by the other parties contains no argument at all for\nquestioning the grounds upon which the district court dismissed\nthe claims of LoConte and Kiossovski. We therefore deem their\nappeal of the judgments against them to be waived. See Vázquez-\nRivera v. Figueroa, 759 F.3d 44, 46-47 (1st Cir. 2014).\n\frecovery under the Racketeer Influenced and Corrupt Organizations\n\nAct (\"RICO\"), 18 U.S.C. § 1962(c)–(d), the Minnesota Consumer\n\nFraud Act, Minn. Stat. § 325F.69, and the Minnesota Unfair Trade\n\nPractices Act, Minn. Stat. § 325D.13, and for unjust enrichment.\n\n In June 2016, the district court denied Painters' motion\n\nto certify two nationwide classes of similarly situated health-\n\ninsurance companies and health plans that had paid for or\n\nreimbursed off-label pediatric prescriptions of Celexa or Lexapro.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig. (Painters I),\n\n315 F.R.D. 116, 131 (D. Mass. 2016).2 In rejecting class\n\ncertification, the court reasoned that while Painters had\n\nsatisfied the Rule 23(a) numerosity, commonality, typicality, and\n\nadequacy requirements, Painters had failed to establish that\n\ncommon questions of fact or law predominated over individual issues\n\nas required by Rule 23(b)(3). Id. at 123–31.\n\n Subsequently, in March 2017, a dispute arose as a result\n\nof Forest's apparently belated production of two internal\n\nmemoranda in advance of a deposition conducted by agreement after\n\ndiscovery had otherwise closed. The two documents contained\n\n\n\n 2Painters' motion for class certification provided no time\nperiod for the proposed Celexa class. At oral argument, however,\nplaintiffs' counsel clarified that plaintiffs only seek to\nchallenge manufacturer-induced prescriptions for off-label uses\nmade prior to the FDA's approval of Lexapro for adolescent use in\nMarch 2009. Thus, we construe Painters' appeal in accordance with\nthis statement.\n\fdetails regarding a study of Celexa's effectiveness. Forest\n\nrevealed that it had not sought any responsive documents from its\n\nClinical Supply Group in responding to Painters' discovery\n\nrequests. The district court nevertheless denied Painters' motion\n\nto compel Forest's supplemental production of documents from this\n\ngroup, concluding that any such production would be cumulative.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig.\n\n(Painters II), 288 F. Supp. 3d 483, 486–87 (D. Mass. 2018).\n\n In due course, after deeming discovery complete and\n\nruling on various interim motions, the district court entered\n\nsummary judgment for Forest on plaintiffs' RICO claims, holding\n\nthat neither Painters nor Ramirez could demonstrate injury. In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Painters III),\n\n289 F. Supp. 3d 247, 253–56 (D. Mass. 2018). The court then\n\nproceeded to dismiss plaintiffs’ state-based allegations as\n\nderiving from their noncognizable RICO claims. Id. at 258–59.\n\nThis appeal by Painters and Ramirez followed.\n\n II.\n\n Summary judgment is appropriate \"if the movant shows\n\nthat there is no genuine dispute as to any material fact and the\n\nmovant is entitled to judgment as a matter of law.\" Fed. R. Civ.\n\nP. 56(a). In granting summary judgment dismissing all of\n\nplaintiffs' claims, the district court concluded that plaintiffs\n\nhad no competent proof that either Celexa or Lexapro was\n\fineffective for treating depression in children or adolescents.\n\nWe review this conclusion de novo. Martinez v. Petrenko, 792 F.3d\n\n173, 179 (1st Cir. 2015).\n\n A.\n\n Prevailing on a RICO claim requires proof of an economic\n\ninjury. See 18 U.S.C. § 1964(c) (\"Any person injured in his\n\nbusiness or property by reason of a violation of section 1962 of\n\nthis chapter may sue therefor.\"). Plaintiffs allege injury in the\n\nform of payments made for ineffective drugs.3 The district court\n\ntherefore turned its attention to determining whether plaintiffs\n\nhad enough evidence to allow a jury to find Celexa and/or Lexapro\n\nineffective for treating pediatric depression. See Painters III,\n\n289 F. Supp. 3d at 253–56. Four clinical trials and the FDA's\n\n2009 approval of Lexapro for adolescents informed the district\n\ncourt's decision.\n\n Starting in 1997, Lundbeck -- the developer of Celexa -\n\n- began conducting Study 94404, which focused on Celexa's efficacy\n\nin treating depression in adolescents. The study produced across-\n\nthe-board negative results. Forest then conducted Study MD-18 in\n\nan attempt to demonstrate Celexa's effectiveness in both children\n\n\n 3 In its opposition to Forest's motion for summary judgment,\nPainters argued that it need not demonstrate that Celexa and\nLexapro are ineffective in treating pediatric depression to\nestablish RICO injury. The district court rejected this argument\nin its order granting Forest's motion, and Painters has not\ndeveloped any challenge to that ruling on this appeal.\n\fand adolescents. The efficacy results of MD-18 are difficult to\n\nassess because Forest bungled the study: Some participants\n\nrandomized into the active treatment group were dispensed\n\nnongeneric, pink tablets in one portion of the trial, potentially\n\nunblinding both the individuals who received these pills and the\n\nresearchers conducting the study. The MD-18 study only\n\ndemonstrated statistically positive results when these potentially\n\nunblinded participants were included. Finally, in 2002–2004 and\n\n2005-2007, Forest conducted two additional clinical trials. Study\n\nMD-15 examined Lexapro's efficacy in children and adolescents and\n\nachieved negative results. Study MD-32 set out to test Lexapro's\n\neffectiveness in treating only adolescents and achieved\n\nstatistically significant positive results.\n\n Based upon the results of MD-32 and the Celexa MD-18\n\nstudy, Forest submitted an sNDA to the FDA in 2008. In 2009, the\n\nFDA approved the application, allowing Forest to market Lexapro\n\nfor use in adolescents. Forest did not seek such approval for\n\nCelexa.\n\n Plaintiffs' evidence that Celexa and Lexapro were\n\nineffective for the pertinent indications consisted of the\n\nfollowing: The FDA has neither approved Celexa for treating\n\ndepression in children or adolescents nor has it approved Lexapro\n\nfor use in children; Study 94404 demonstrated only a detrimental\n\neffect of Celexa in treating depression in adolescents; Study MD-\n\f18 was corrupted and showed no beneficial effect in children and\n\nadolescents unless the potentially unblinded participants are\n\nincluded in the results; and Study MD-15 produced uniformly\n\nnegative results in testing Lexapro's efficacy in children and\n\nadolescents. In addition, plaintiffs produced expert testimony\n\nopining that the positive results in MD-32 were not of clinical\n\nsignificance and that MD-18 should properly be considered a\n\nnegative trial. Plaintiffs also provided the results of a\n\n2016 meta-analysis study that found that neither Celexa nor\n\nLexapro had any more beneficial effect than a placebo in treating\n\npediatric depression.\n\n There is also evidence in the record before us, however,\n\nthat cuts the other way. In September 2002, the FDA accepted\n\nStudy MD-18 as a positive trial that would support a determination\n\nof Celexa's effectiveness for the treatment of MDD in adolescent\n\npatients. And in January 2003, the FDA also stated that MD-18\n\ncould be employed to support an application for FDA approval \"for\n\nboth Celexa and Lexapro, in pediatric patients with [MDD].\" The\n\nFDA relied in part on these findings in approving Lexapro for the\n\ntreatment of depression in adolescents in March 2009. Further,\n\nForest points out that neither Painters nor Prime Therapeutics\n\n(\"Prime\"), Painters' pharmacy-benefits manager, has taken any\n\neffort to limit or remove from its formulary pediatric\n\nprescriptions of Celexa and Lexapro.\n\f This record raises two questions. First, do the FDA's\n\nvarious pronouncements or actions close the door on any effort to\n\nconvince a jury that either Celexa or Lexapro was ineffective?\n\nSecond, to the extent that the FDA's pronouncements and actions\n\nare not preclusive, is the evidence in this case nevertheless\n\ninsufficient to support a jury finding of ineffectiveness?\n\n 1.\n\n Forest claims that two of our recent decisions --\n\nD'Agostino v. ev3, Inc., 845 F.3d 1 (1st Cir. 2016), and In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Marcus), 779 F.3d\n\n34 (1st Cir. 2015) -- answer the first question in the affirmative\n\nby deeming FDA approval dispositive. Even were we to find it\n\nconvincing, this argument would not cover all the challenged uses\n\nat issue in this appeal. The FDA has never approved Celexa for\n\nany of the off-label uses for which Forest promoted it. Nor has\n\nit approved Lexapro for the treatment of MDD in children under the\n\nage of twelve. So Forest's reliance on actual FDA approval to\n\nforeclose a jury determination of inefficacy must be limited to\n\nForest's marketing of Lexapro for adolescent use and, perhaps as\n\nwell, to the question of how to construe MD-18.\n\n In any event, even as thus limited, we do not find\n\nForest's reliance on D'Agostino convincing. The claim in\n\nD'Agostino concerned the sale of medical devices after the FDA had\n\napproved the devices for the uses for which they were sold.\n\fD'Agostino, 845 F.3d at 3, 7–9. In rejecting a challenge to those\n\npost-approval sales under the False Claims Act based on alleged\n\npre-approval fraud on the FDA, we reasoned that \"[t]o rule\n\notherwise would be to turn the FCA into a tool with which a jury\n\nof six people could retroactively eliminate the value of FDA\n\napproval and effectively require that a product largely be\n\nwithdrawn from the market even when the FDA itself sees no reason\n\nto do so.\" Id. at 8. Here, by contrast, plaintiffs challenge\n\nonly the promotion of Celexa and Lexapro for uses that were off-\n\nlabel (i.e., not FDA-approved) at the time Forest promoted and\n\nsold the drugs.4 When Forest is said to have made those marketing\n\nefforts, it could not have pleaded reliance on FDA approval. If\n\na jury were to hold Forest liable for such pre-approval marketing,\n\nit would simply be telling Forest that it should not have marketed\n\nthat which Congress under the FDCA does not want it to market:\n\ndrugs for unapproved uses. We therefore see no reason to accord\n\nto Forest the preclusive protection for pre-approval promotion\n\nthat FDA approval provided the medical-device manufacturer for\n\npost-approval conduct in D'Agostino.5\n\n\n 4 Though plaintiffs' complaints do not explicitly limit their\nRICO and state-law claims to the period prior to FDA's March 2009\napproval of Lexapro, plaintiffs' counsel indicated at oral\nargument that plaintiffs do not challenge Forest's post-approval\nmarketing of Celexa and Lexapro.\n 5 For similar reasons, Forest's reliance on Buckman Co. v.\nPlaintiffs' Legal Comm., 531 U.S. 341, 348 (2001), in which the\nSupreme Court rejected as preempted state fraud-on-the-FDA claims,\n\f Nor does our opinion in Marcus aid Forest in this case.\n\nIn Marcus, we rejected a challenge to a drug label based on\n\ninformation that was \"plainly known to the FDA prior to approving\n\nthe label.\" 779 F.3d at 43. We made clear in doing so, however,\n\nthat we were merely applying the state-law preemption principles\n\nthe U.S. Supreme Court laid out in PLIVA, Inc. v. Mensing, 564\n\nU.S. 604 (2011), and Wyeth v. Levine, 555 U.S. 555 (2009). See\n\nMarcus, 779 F.3d at 40–43 (explaining that a drug manufacturer can\n\nonly be held liable under state law for inadequate warning in an\n\nFDA-approved label when the drug manufacturer can, \"of its own\n\nvolition, . . . strengthen its label in compliance with its state\n\ntort duty\" (quoting PLIVA, Inc., 564 U.S. at 624)). Marcus,\n\naccordingly, is inapposite.\n\n This is not to say that the FDA's 2009 approval of\n\nForest's sNDA for Lexapro is irrelevant to this case. Certainly\n\nthe approval and the FDA's reliance on MD-18 provide what many\n\njurors may view as strong evidence confirming that Lexapro, and\n\nperhaps Celexa as well, have always been efficacious in treating\n\npediatric depression. The common law has long recognized that\n\nagency approval of this type is relevant in tort suits. See\n\nRestatement (Third) of Torts: Prod. Liab. § 4 (Am. Law Inst. 1998)\n\n\nand its progeny is misplaced. Plaintiffs question the efficacy of\nCelexa and Lexapro only for off-label uses; their claims,\naccordingly, are not predicated on a fraud-on-the-FDA theory of\nliability.\n\f(\"[C]ompliance with an applicable product safety statute . . . is\n\nproperly considered in [a product defect case].\"). But the common\n\nlaw also recognizes that such evidence is not always preclusive.\n\nId. (\"[S]uch compliance does not preclude as a matter of law a\n\nfinding of product defect.\"). And while there are strong reasons\n\nfor treating such evidence as preclusive when the challenged sales\n\nare made in reliance on agency approval, those same reasons cut\n\nthe other way when the sales are made without approval, and\n\ncertainly when made unlawfully, as we must assume they were here.\n\n 2.\n\n Having decided that the FDA's subsequent approval of\n\nLexapro does not preclude proving that pre-approval uses of these\n\ndrugs were ineffective, we turn to addressing whether plaintiffs\n\nmay proceed with a claim based on product ineffectiveness when the\n\nevidence of efficacy is conflicting. This is more or less the\n\nquestion we left unanswered in Kaiser. See Kaiser, 712 F.3d at 49\n\n(declining to address what evidentiary standard would be needed to\n\ndemonstrate efficacy \"if the results of DBRCTs were equivocal\" or\n\n\"if there were a different mix of DBRCT and non-DBRCT evidence\").6\n\n\n 6 To advance its preferred interpretation of the term\n\"equivocal\" in Kaiser, each party dedicates a significant portion\nof its brief to sparring over whether the DBRCT evidence in the\nNeurontin cases was, in fact, mixed. We need not address this\nquestion because, as we explain, Painters' RICO claim survives\nsummary judgment even though the evidence of inefficacy is mixed.\nWe note, however, that the DBRCTs in the Neurontin case were not\nuniformly negative as Forest would have us believe. Rather, the\n\f Generally speaking, \"conflicting evidence\" is the\n\nhallmark of an issue that calls for factfinding, not summary\n\njudgment. See, e.g., Adria Int'l Grp. v. Ferre Dev., Inc., 241\n\nF.3d 103, 111 (1st Cir. 2001) (finding summary judgment\n\ninappropriate when evidence presented was \"contested and\n\ncontradictory\"); see also 10A Charles Alan Wright et al., Federal\n\nPractice and Procedure § 2712 (4th ed. 2018) (\"[S]ummary judgment\n\nis not a substitute for the trial of disputed fact issues.\"). We\n\nsee no reason to deviate from that general rule merely because the\n\nproduct marketed illegally is one that was later approved for\n\nlawful sales.7 In short, why should we forgo customary fact-\n\nfinding by the jury so as to reward unlawful conduct aimed at\n\ngetting children to consume unapproved drugs?\n\n Forest also argues that plaintiffs' evidence of\n\nineffectiveness falls short of proving injury because Painters has\n\nnot produced \"individualized\" proof that Celexa or Lexapro was\n\nineffective for any particular insured. By \"individualized\"\n\nproof, Forest appears to mean testimony from a patient (or from a\n\n\ndistrict court noted both positive and negative clinical studies\nin reviewing the parties' evidence of Neurontin's efficacy for the\nat-issue off-label conditions. See Kaiser, 2011 WL 3852254, at\n*34–46 (reviewing mixed DBRCT results).\n 7\n Nor is summary judgment for Forest warranted due to the fact\nthat Painters has not directed the removal of Celexa and Lexapro\nfor pediatric uses from its drug formulary. As we held in Kaiser,\nit is \"within the factfinder's province to weigh this evidence.\"\nKaiser, 712 F.3d at 41.\n\fdoctor concerning that patient) that the patient experienced no\n\nbeneficial effects from the drug. While evidence of that type\n\ncould be probative, certainly it is not the only way to prove that\n\na drug is ineffective. Indeed, given that (1) an ineffective drug\n\nmay trigger a placebo effect in a given individual and (2) an\n\neffective drug may not benefit all users, individualized proof\n\nmight well be less probative than the type of expert, study-based\n\ntestimony that plaintiffs have offered. In any event, as we\n\nalready held, such individualized proof is certainly not required.\n\nSee In re Neurontin Mtkg. & Sales Practices Litig. (Harden), 712\n\nF.3d 60, 69 (1st Cir. 2013) (\"[W]e reject Pfizer's position that\n\nthese plaintiffs must prove the individual, subjective\n\nineffectiveness of each off-label prescription in order to\n\nestablish injury. . . . The Harden plaintiffs have proffered\n\nclinical trial evidence that Neurontin is ineffective . . ., which\n\nis certainly enough to raise a genuine issue of fact on the\n\neffectiveness issue.\" (citation omitted)); In re Neurontin Mtkg.\n\n& Sales Practices Litig. (Aetna), 712 F.3d 51, 59–60 (1st Cir.\n\n2013).\n\n In sum, we hold that the FDA's 2009 approval of Lexapro\n\ndoes not preclude a jury from concluding that the off-label uses\n\nof Celexa and Lexapro at issue in this case were ineffective in\n\ntreating pediatric depression. Moreover, plaintiffs have provided\n\ncompetent and sufficient evidence -- through DBRCTs, expert\n\ftestimony, and peer-reviewed literature -- to raise a genuine issue\n\nof material fact as to the efficacy of these drugs for pediatric\n\nuse. Accordingly, the district court erred in granting summary\n\njudgment for Forest on plaintiffs' RICO and state-law claims on\n\nthis basis.\n\n B.\n\n In addition to demonstrating economic injury, a RICO\n\nplaintiff must prove that the defendant's racketeering conduct\n\ncaused her injury. 18 U.S.C. § 1964(c); Holmes v. Sec. Inv'r Prot.\n\nCorp., 503 U.S. 258, 268 (1992) (interpreting section 1964(c)'s\n\nlanguage to mean that a RICO plaintiff must show both but-for and\n\nproximate causation to establish standing). As we have already\n\nnoted, physicians can -- and do -- lawfully prescribe prescription\n\ndrugs for off-label uses, even though the manufacturer is barred\n\nby law from promoting such prescriptions. See Lawton ex rel.\n\nUnited States, 842 F.3d at 128 n.4. So for any given prescription\n\nin this case, one would reasonably ask whether Forest's efforts to\n\nprofit by illegally marketing drugs for pediatric use caused a\n\nparticular prescription to be made, or whether, instead, the doctor\n\nwrote a given prescription based on his or her own professional\n\nmedical judgment (perhaps reasoning that what works for an adult\n\npatient might also work for a younger patient).\n\n Forest therefore urges that, even if we disagree with\n\nthe district court on the issue of injury/efficacy, we should still\n\faffirm the entry of summary judgment due to Painters' lack of proof\n\nof but-for causation. While the district court did not consider\n\nthe issue of causation in its summary-judgment ruling, it did\n\nearlier assay Painters' causation evidence in ruling on Painters'\n\nmotion for class certification. The district court labeled the\n\nproof so \"insubstantial\" and \"fundamentally flawed\" \"as to\n\npreclude class certification.\" Painters I, 315 F.R.D. at 126–28.\n\nForest would have us interpret these pronouncements as a finding\n\nthat the evidence was insufficient as a matter of law to prove\n\nbut-for causation.\n\n We disagree. In the first place, it is unclear why the\n\ndistrict court gauged the substantiality or merit of plaintiffs'\n\nproof in the context of a Rule 23 motion. The central issue in\n\nthat context is not whether the method of proof would or could\n\nprevail. Rather, it is whether the method of proof would apply in\n\ncommon to all class members. See, e.g., Tyson Foods, Inc. v.\n\nBouaphakeo, 136 S. Ct. 1036, 1047 (2016) (\"When . . . 'the concern\n\nabout the proposed class is not . . . some fatal dissimilarity\n\nbut, rather, a fatal similarity -- [an alleged] failure of proof\n\nas to an element of the plaintiffs' cause of action -- courts\n\nshould engage that question as a matter of summary judgment, not\n\nclass certification.'\" (alteration in original) (quoting Richard\n\nA. Nagareda, Class Certification in the Age of Aggregate Proof, 84\n\nN.Y.U. L. Rev. 97, 107 (2009))).\n\f More substantively, Painters' evidence does not seem\n\nclearly insufficient. There is ample evidence that Forest spent\n\nmoney inducing doctors to prescribe its drugs to pediatric patients\n\nand that it would not have done so had the effort not been worth\n\nthe money. Two experts, Dr. Meredith Rosenthal and\n\nDr. Christopher Baum, also opined that Forest's spending on\n\npromotions in general correlated positively with sales. As the\n\ndistrict court pointed out, Painters' experts then assumed that\n\nthis same approximate correlation applied to off-label promotional\n\nspending and off-label sales. Painters I, 315 F.R.D. at 127. The\n\ndistrict court thought this assumption to be a \"fundamental flaw\"\n\nin the analysis. Id. Why, exactly, we are not sure. After all,\n\nwhy would Forest, which knew its markets better than anyone, have\n\nspent money on off-label marketing over the long term if it\n\ngenerated lower returns than would additional spending on less\n\nrisky, lawful marketing? Certainly there is room for reasonable\n\ndisagreement on the merits of Dr. Rosenthal and Dr. Baum's\n\nassumption.\n\n If the jury accepts this assumption as reasonable, and\n\nif it finds that the prescriptions that Painters paid for were\n\ntypical of those that the experts analyzed, jurors would then have\n\na fair path to finding that Forest's off-label marketing caused\n\nPainters to pay for ineffective drugs. The experts' interpretation\n\nof the data indicated that Forest's off-label promotions caused\n\f76% and 54% of all pediatric prescriptions of Celexa and Lexapro,\n\nrespectively. Dr. Rosenthal estimated that if Painters paid for\n\nas few as five independent prescriptions, there would be a 98%\n\nchance that at least one was the result of off-label marketing.\n\nIn fact, Painters likely paid for the Celexa or Lexapro\n\nprescriptions of more than five different patients.8 So the odds\n\nthat Painters was not harmed if the drugs were, indeed, ineffective\n\nwas likely infinitesimal (assuming the prescriptions were\n\nindependent of one another).9\n\n\n\n\n 8In its summary judgment order, the district judge observed\nthat Painters reimbursed sixteen of its pediatric insureds for\nseventy-two off-label prescriptions of Celexa from 1999 through\n2004, and thirty-one of its pediatric insureds for 234 off-label\nprescriptions of Lexapro from 2002 through early 2015. Painters\nIII, 289 F. Supp. 3d at 251. It is not clear from the record how\nmany of these Lexapro prescriptions were written prior to March\n2009. Viewing this evidence in the light most favorable to\nPainters, Ellis v. Fidelity Mgmt. Tr. Co., 883 F.3d 1, 3, (1st\nCir. 2018), and without any counter-argument on this point by\nForest, we assume for purposes of this appeal only that well more\nthan five of the aforementioned Lexapro prescriptions were filled\nprior to the FDA's 2009 approval of Lexapro.\n 9The statistical proof in this instance is being used only\nto prove that a group of prescriptions likely includes at least\none that a certain activity caused, and it is then being utilized\nto estimate the percentage of such causally connected\nprescriptions in that group. Painters proposes no use of the\nstatistical data to prove that Forest's off-label marketing caused\nany particular prescription to be written. See In re Asacol\nAntitrust Litig. (Asacol), 907 F.3d 42, 54 (1st Cir. 2018) (finding\nit \"far from self-evident\" that expert testimony opining that\n\"ninety percent of class members were injured\" would be \"sufficient\nto prove that any given individual class member was injured\").\n\f Nor is Painters' evidence limited to the thrust of its\n\nstatistics. Painters also has evidence that Forest sales\n\nrepresentatives called or visited at least two physicians who\n\nsubsequently ordered pediatric prescriptions of Celexa and Lexapro\n\nthat Painters reimbursed. In addition, Painters produced evidence\n\nsuggesting that Forest specifically targeted Painters' pharmacy-\n\nbenefits manager, Prime, and that Prime relied upon a misleading\n\nreport by Forest of Study MD-18 in managing Painters' formulary.\n\nAll together, this is surely enough to raise a triable issue of\n\nfact as to whether Forest's off-label marketing caused Painters to\n\npay for a prescription for which it would not have otherwise paid.\n\n This is not to say that Painters will ultimately prevail\n\non the issue of causation. The district court has not conducted\n\na Daubert analysis. And there may be other potential bones to\n\npick with the sufficiency of Painters' proof of causation. As the\n\nrecord now stands, though, we agree with Painters that we cannot\n\naffirm the summary judgment finding that its causation proof is\n\ninsufficient as a matter of law.\n\n As for Ramirez, Forest did not challenge her standing on\n\nthe basis of causation in its memorandum in support of its motion\n\nfor summary judgment. Accordingly, we express no opinion as to\n\nwhether Ramirez has raised a triable issue on RICO causation. See\n\nRosaura Bldg. Corp. v. Municipality of Mayagüez, 778 F.3d 55, 63\n\f(1st Cir. 2015) (\"Time and time again we have held that arguments\n\nnot advanced before the district court are waived.\").\n\n As for proximate causation, it is of no moment that\n\npediatricians were the immediate target of Forest's fraudulent\n\nmarketing. Here, as in Kaiser, a jury could find that Painters\n\nand Ramirez were \"the primary and intended victims of [Forest's]\n\nscheme to defraud.\" Kaiser, 712 F.3d at 37 (quoting Bridge v.\n\nPhx. Bond & Indem. Co., 553 U.S. 639, 650 (2008)). Moreover,\n\nPainters' and Ramirez's alleged harm (i.e., reimbursing or\n\npurchasing more pediatric prescriptions than they otherwise would\n\nhave) was a \"foreseeable and natural consequence\" of Forest's\n\nscheme. Bridge, 553 U.S. at 658. Indeed, it was precisely the\n\npoint.\n\n Accordingly, for the foregoing reasons, we reverse the\n\ndistrict court's entry of summary judgment for Forest on Painters'\n\nRICO and state-law claims and on Ramirez's RICO and unjust-\n\nenrichment claims.\n\n III.\n\n Early on in this litigation the district court denied\n\nPainters' motion to certify this case as a class action under\n\nFederal Rule of Civil Procedure 23(b)(3). In so ruling, the\n\ndistrict court reasoned that a variety of important issues,\n\nincluding causation and injury, would pose individual questions\n\nthat would need to be answered for each class member. Painters I,\n\f315 F.R.D. at 123–30. The presence of these individual questions,\n\nreasoned the district court, defeated Painters' effort to satisfy\n\nthe requirement of Rule 23(b)(3) that common issues must\n\npredominate. Id. Painters now appeals that ruling as it applies\n\nto classes consisting of third-party payors (\"TPP\") who paid for\n\nor reimbursed prescriptions of Celexa or Lexapro prior to early\n\n2009. It is not clear why those issues to which the district court\n\npointed would preclude certification of such a class. As we have\n\nalready explained, Painters' clinical and statistical evidence, if\n\nbelieved, could establish causation and injury at least for any\n\nTPP who paid for more than a handful of different patients'\n\nprescriptions. Nevertheless, as we will explain, it has become\n\napparent that the proper application of the statute of limitations,\n\nwhile preserving plaintiffs' individual claims, precludes\n\nPainters' attempt to maintain a class action.\n\n A.\n\n The parties agree that the applicable statutory\n\nlimitations period is four years. See Agency Holding Corp. v.\n\nMalley-Duff & Assocs., Inc., 483 U.S. 143, 156 (1987). That four-\n\nyear period began to run \"at the time [the] plaintiff knew or\n\nshould have known of his injury.\" Lares Grp., II v. Tobin, 221\n\nF.3d 41, 44 (1st Cir. 2000) (citing Rodriguez v. Banco Central,\n\n917 F.2d 664, 665 (1st Cir. 1990)). The injury here is the payment\n\nmade on account of off-label prescriptions that Forest induced.\n\fSee Kaiser, 712 F.3d at 39 (\"[E]conomic injury occur[s] when\n\n[plaintiff] paid for fraudulently induced [drug] prescriptions.\").\n\nSo, the key question becomes: By what date can we say, as a matter\n\nof law, that Painters knew or should have known that Forest was\n\npromoting the off-label, ineffective use of Celexa or Lexapro?\n\n The district court found that date to be no later than\n\nMarch of 2009. In re Celexa & Lexapro Mktg. & Sales Practices\n\nLitig., 65 F. Supp. 3d 283, 289 (D. Mass. 2014). In February of\n\nthat year, the United States unsealed its complaint against Forest\n\nin United States ex rel. Gobble, which detailed in thirty-three\n\npages how \"Forest engaged in a fraudulent scheme to market and\n\npromote Celexa . . . and Lexapro . . . off-label to treat\n\ndepression and other psychiatric conditions in pediatric\n\npatients.\" Complaint at 2, United States ex rel. Gobble, No. 03-\n\n10395-NMG (D. Mass. Feb. 13, 2009), ECF No. 61 [hereinafter United\n\nStates' Complaint]. Within weeks, two private class-action\n\ncomplaints followed, one in New York and another in Missouri, each\n\nalso alleging a fraudulent scheme to market Celexa and Lexapro for\n\nineffective, off-label uses. See Class Action Complaint,\n\nUniversal Care, Inc. v. Forest Pharm., Inc., No. 09-cv-11518-NMG\n\n(D. Mass. Mar. 20, 2009), ECF No. 1; Class Action Complaint, N.M.\n\nUFCW Union's & Emp'rs' Health & Welfare Tr. Fund v. Forest Labs.,\n\nInc., No. 09-cv-11524-NMG (D. Mass. Mar. 12, 2009), ECF No. 1.\n\nPainters never argued before the district court that it was unaware\n\fof the United States' complaint or the March 2009 lawsuits. Nor\n\ndoes it so argue on appeal. Rather, it argues that the lawsuits\n\ndid not provide enough notice that Forest had been promoting the\n\noff-label use of Celexa and Lexapro. Such notice, Painters says,\n\nwas not available until Forest's own public admission to that\n\neffect in November 2010, when it both pleaded guilty to criminal\n\nviolations of the FDCA and entered into a civil settlement\n\nagreement with the United States.\n\n Not surprisingly, Painters points to no case law holding\n\nthat a statutory limitations period does not start to run until\n\nthe potential defendant first delivers a gift-wrapped admission of\n\nits alleged wrongdoing. Were that the rule, very few limitations\n\nperiods would ever commence, much less conclude. Instead, as we\n\nhave explained in an analogous context, \"[w]e look first to whether\n\nsufficient facts were available to provoke a reasonable person in\n\nthe plaintiff's circumstances to inquire or investigate\n\nfurther. . . . Once a duty to inquire is established, the\n\nplaintiff is charged with the knowledge of what he or she would\n\nhave uncovered through a reasonably diligent investigation.\"\n\nMcIntyre v. United States, 367 F.3d 38, 52 (1st Cir. 2004); see\n\nalso Sanchez v. United States, 740 F.3d 47, 52 (1st Cir. 2014)\n\n(\"The discovery rule incorporates an objective standard. To delay\n\ncommencement of the running of the statute of limitations, 'the\n\nfactual basis for the cause of action must have been inherently\n\funknowable, [that is, not capable of detection through the exercise\n\nof reasonable diligence] at the time of injury.'\" (alteration in\n\noriginal) (quoting Gonzalez v. United States, 284 F.3d 281, 288–\n\n89 (1st Cir. 2002))). The same fundamental principle applies to\n\nRICO suits. See Rotella v. Wood, 528 U.S. 549, 555 (2000)\n\n(\"Federal courts . . . generally apply a discovery accrual rule\n\nwhen a statute is silent on the issue, as civil RICO is here. . . .\n\n[D]iscovery of the injury . . . is what starts the clock.\"\n\n(citations omitted)); Koch v. Christie's Int'l PLC, 699 F.3d 141,\n\n150–51 (2d Cir. 2012) (noting that a RICO claim does not accrue\n\nuntil a plaintiff has \"actual or inquiry notice of the injury\"\n\n(quoting In re Merrill Lynch Ltd. P'ships Litig., 154 F.3d 56, 60\n\n(2d Cir. 1998))).\n\n We agree with the district court that the unsealing of\n\nthe United States' complaint and the subsequent lawsuits filed in\n\nMarch 2009 were more than sufficient to put a TPP like Painters on\n\nnotice that Forest had likely been inducing off-label\n\nprescriptions of Celexa and Lexapro. The United States' complaint\n\nchronicled how Forest suppressed a negative study on Celexa while\n\npromoting a positive study (which conveniently neglected to\n\nmention the earlier, negative study). United States' Complaint at\n\n3, 14. The complaint quoted internal Forest communications and\n\nrecounted the precise details of Forest's unlawful promotional\n\nactivities. Id. at 15–22. It quoted Forest's physician-call notes\n\freporting on the efforts of Forest's sales representatives to\n\npromote the pediatric use of the drugs. E.g., id. at 20 (\"[F]ocus\n\non Lexapro efficacy at just 10 mg., great choice for\n\nchild/adolescents.\"). It also named Forest marketing executives,\n\ne.g., id. at 23, and outside physicians involved in the promotion\n\ncampaigns, e.g., id. at 21–22. It is inconceivable that any TPP\n\nlike Painters would not have found in the complaint a very strong\n\nprobability that Forest had systematically and fraudulently pushed\n\nits drugs on unsuspecting children.\n\n Nevertheless, we also agree with the district court that\n\nPainters survived Forest's statute-of-limitations defense because\n\nthe running of the limitations period was stayed for more than\n\neight months by the filing of the N.M. UFCW class action in March\n\n2009. See In re Celexa & Lexapro Mktg. & Sales Practices Litig.,\n\n65 F. Supp. 3d at 291. Painters was a member of the putative RICO\n\nclass action for which the N.M. UFCW complaint sought\n\ncertification. Under American Pipe & Construction Co. v. Utah,\n\n414 U.S. 538 (1974), the limitations period during which Painters\n\nmight sue on its own behalf was therefore tolled until the N.M.\n\nUFCW class action was dismissed in June 2010. Forest did not cross\n\nappeal the district court's application of American Pipe. Rather,\n\nForest argues only that the limitations period began running long\n\nbefore March of 2009 when plaintiffs first should have suspected\n\nthat Celexa and Lexapro were ineffective for pediatric use. We\n\freject that argument because the injury here is paying for\n\nunlawfully induced off-label prescriptions, not merely physician-\n\ndirected, off-label prescriptions.\n\n B.\n\n Even though plaintiffs can sue, thanks to American Pipe,\n\nPainters cannot parlay that dispensation into the much-delayed\n\nfiling of a class action. See China Agritech, Inc. v. Resh, 138\n\nS. Ct. 1800 (2018). In American Pipe, the Supreme Court held that\n\nthe \"commencement of [a putative class action] tolls the running\n\nof the statute for all purported members of the class who make\n\ntimely motions to intervene after the court has found the suit\n\ninappropriate for class action status.\" 414 U.S. at 552-53. China\n\nAgritech clarified that this tolling rule has limits: While a\n\nputative class member may join an existing suit or file an\n\nindividual action upon denial of class certification, a putative\n\nclass member may not commence a class action anew beyond the time\n\nallowed by the untolled statute of limitations. 138 S. Ct. at\n\n1807 (\"The 'efficiency and economy of litigation' that support\n\ntolling of individual claims do not support maintenance of untimely\n\nsuccessive class actions; any additional class filings should be\n\nmade early on, soon after the commencement of the first action\n\nseeking class certification.\" (citation omitted) (quoting Am.\n\nPipe, 414 U.S. at 553)).\n\f Painters argues that China Agritech is distinguishable\n\nfrom the case at hand because there was no substantive ruling on\n\nclass certification in N.M. UFCW; the first time any district court\n\naddressed class certification was in Painters' case. Painters'\n\nposition relies on an impermissibly narrow reading of the Court's\n\ndecision in China Agritech. Though the Supreme Court granted\n\ncertiorari in that case to answer the narrow question of whether\n\na putative class member may commence a class action beyond the\n\nlimitations period upon the district court's denial of a request\n\nfor class certification filed within the statute of limitations,\n\nid. at 1804, the Court proceeded to provide a broader answer: Its\n\nprecedents do not \"so much as hint[] that [American Pipe] tolling\n\nextends to otherwise time-barred class claims,\" id. at 1806. Thus,\n\nthe Court effectively ruled that the tolling effect of a motion to\n\ncertify a class applies only to individual claims, no matter how\n\nthe motion is ultimately resolved. To hold otherwise would be to\n\nallow a chain of withdrawn class-action suits to extend the\n\nlimitations period forever.\n\n For the foregoing reasons, the district court did not\n\nabuse its discretion in declining to certify Painters' proposed\n\nnationwide class of TPPs.\n\n IV.\n\n Finally, Painters also takes issue with the district\n\ncourt's denial of its motion to compel Forest's supplemental\n\fproduction of documents related to the MD-18 Study. This court\n\nreviews a district court's discovery decision for abuse of\n\ndiscretion, intervening \"only upon a clear showing of manifest\n\ninjustice, that is, where the lower court's discovery order was\n\nplainly wrong and resulted in substantial prejudice to the\n\naggrieved party.\" Pina v. Children's Place, 740 F.3d 785, 791\n\n(1st Cir. 2014) (quoting Dennis v. Osram Sylvania, Inc., 549 F.3d\n\n851, 859 (1st Cir. 2008)).\n\n Here, it is undisputed that Forest did not perform an\n\nexhaustive search in response to Painters' requests for documents\n\nrelated to the MD-18 Study: Indeed, Forest acknowledges\n\n(employing the passive voice) that \"files within the custody of\n\nthe Clinical Supply Group were not searched.\" Forest also does\n\nnot deny that its own preliminary search within this group -- after\n\ndiscovery had closed -- produced two responsive memoranda\n\nregarding the packaging error in the MD-18 Study. The only excuse\n\nForest provides is that \"[p]laintiffs were fully apprised of the\n\nscope of document collection and were aware that files within the\n\ncustody of the Clinical Supply Group were not searched.\" Forest,\n\nhowever, points us to nothing in the record demonstrating that\n\nPainters acquiesced to Forest's limiting the scope of its document\n\ncollection in this way. These admissions notwithstanding, the\n\ndistrict court denied Painters' Rule 37 motion to compel the\n\nsupplementary production of documents related to the MD-18 Study.\n\fIt reasoned that the Rule 26(e)(1) duty to supplement only applies\n\nwhen \"the supplemental material has not been otherwise made known\n\nto the requesting party\" and observed that Painters had already\n\nreceived \"substantial production of documents related to the\n\npackaging error\" such that any new production would be cumulative.\n\nPainters II, 288 F. Supp. 3d at 487.\n\n Rule 26(e)(1) requires that a party who has responded to\n\na request for production supplement its response in a timely manner\n\n\"if the party learns that in some material respect the . . .\n\nresponse is incomplete . . . and if the additional . . .\n\ninformation has not otherwise been made known to the other parties\n\nduring the discovery process.\" Fed. R. Civ. P. 26(e)(1). Whether\n\nor not \"information has not otherwise been made known\" -- and,\n\nthus, whether or not additional production would be cumulative --\n\nnecessarily hinges on the relevance that the additional production\n\nmight have for the requesting party's claims and the complexity of\n\nthe issue that the factfinder is tasked to resolve; clearly, a\n\nrelatively high degree of granularity in document production is to\n\nbe expected in technical matters of great significance to a party's\n\noverall claim.\n\n The district court viewed FDA approval as being\n\npreclusive as to the validity of Studies MD-18 and MD-32. See\n\nPainters III, 289 F. Supp. 3d at 255–56. It also viewed the\n\nvalidity of those two studies as fatal to plaintiffs' attempt to\n\fprove ineffectiveness with the type of evidence used in Neurontin.\n\nSee id. Given those views, the district court understandably\n\ndecided that further evidence on the question of effectiveness was\n\ncumulative and of no material import. See Painters II, 288 F.\n\nSupp. 3d at 487. Because we have now explained why the FDA's\n\napproval of Lexapro for its use in adolescents is not as preclusive\n\nas the district court might have reasonably thought, and because\n\nPainters and Ramirez have a live claim on the merits, one might\n\nreasonably expect Forest to search for responsive files within the\n\n\"Clinical Supply Group.\" Accordingly, we vacate the district\n\ncourt's discovery ruling so that on remand it can consider whether\n\nfurther discovery is called for in view of our decision in this\n\nappeal.\n\n V. Conclusion\n\n For the foregoing reasons, we reverse the district\n\ncourt's entry of summary judgment for Forest on Painters' and\n\nRamirez's RICO and state-law claims and vacate the district court's\n\ndenial of Painters' Rule 37 motion to compel supplemental\n\ndiscovery. At the same time, we affirm the district court's denial\n\nof Painters' motion for class certification. We award no costs to\n\nany party.\n[END_CASE]", "role": "user" } ]
4,586,008
PR AAA Portfolio Bond Fund v. Employees Retirement System
2019-01-30
18-1836P
U.S. Court of Appeals for the First Circuit
{"judges": "Before Lynch, Stahl, and Kayatta, Circuit Judges.", "parties": "", "opinions": [{"author": "LYNCH, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\nNos. 18-1836\n 18-1837\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE OPPORTUNITIES FUND IX\n (PARALLEL 2), L.P.; OAKTREE VALUE OPPORTUNITIES FUND, L.P.;\n OCHER ROSE, L.L.C.; SV CREDIT, L.P.,\n\n Movants, Appellants,\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n\f U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Movants, Appellees.\n\n\nNo. 18-1841\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n\f INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Movants, Appellants.\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\n L.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Movants, Appellees.\n\n\nNo. 18-1855\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n\f SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Plaintiff, Appellee,\n\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Interested Party, Appellee,\n\n v.\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\nGLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.,\n\n Defendants, Appellants,\n\n PUERTO RICO AAA PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA PORTFOLIO TARGET\n MATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND II, INC.;\nPUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO FIXED INCOME\n FUND V, INC.; PUERTO RICO FIXED INCOME FUND III, INC.; PUERTO\n RICO FIXED INCOME FUND, INC.; PUERTO RICO GNMA AND U.S.\n GOVERNMENT TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS\nBOND FUND I, INC.; PUERTO RICO INVESTORS TAX-FREE FUND II, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND III, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND IV, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND V, INC.; PUERTO RICO INVESTORS TAX-FREE FUND VI, INC.;\nPUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO MORTGAGE-\n BACKED & U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO\n RICO FUND II, INC.; TAX-FREE PUERTO RICO FUND, INC.; TAX-FREE\n PUERTO RICO TARGET MATURITY FUND, INC.; UBS IRA SELECT GROWTH &\n INCOME PUERTO RICO FUND,\n\f Defendants.\n\n\nNo. 18-1858\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Plaintiff, Appellee,\n\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Interested Party, Appellee,\n\n v.\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n\f U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Defendants, Appellants,\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\n L.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Defendants.\n\n\nNo. 18-1868\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n\fINVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\nFUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Movants, Appellants,\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\nGLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO; OFFICIAL COMMITTEE OF UNSECURED CREDITORS,\n\n Movants, Appellees.\n\n\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Laura Taylor Swain,* U.S. District Judge]\n\n\n\n\n * Of the Southern District of New York, sitting by\ndesignation.\n\f Before\n\n Lynch, Stahl, and Kayatta,\n Circuit Judges.\n\n\n Bruce Bennett, with whom Benjamin Rosenblum, James M. Gross,\nGeoffrey S. Stewart, Sparkle L. Sooknanan, Parker A. Rider-\nLongmaid, Jones Day, Alfredo Fernández-Martínez, and Delgado &\nFernández, LLC were on brief, for Altair Global Credit\nOpportunities Fund (A), LLC; Andalusian Global Designated Activity\nCompany; Glendon Opportunities Fund, LP; Mason Capital Master Fund\nLP; Nokota Capital Master Fund, L.P.; Oaktree-Forrest Multi-\nStrategy, L.L.C. (Series B); Oaktree Opportunities Fund IX, L.P.;\nOaktree Opportunities Fund IX, (Parallel 2), L.P.; Oaktree Value\nOpportunities Fund, L.P.; Ocher Rose, L.L.C; SV Credit, L.P.\n Jason N. Zakia, with whom Glenn M. Kurtz, John K. Cunningham,\nWhite & Case LLP, José C. Sánchez-Castro, Alicia I. Lavergne-\nRamírez, Maraliz Vázquez-Marrero, and Sanchez Pirillo LLC were on\nbrief, for Puerto Rico AAA Portfolio Bond Fund, Inc.; Puerto Rico\nAAA Portfolio Bond Fund II, Inc.; Puerto Rico AAA Portfolio Target\nMaturity Fund, Inc.; Puerto Rico Fixed Income Fund, Inc.; Puerto\nRico Fixed Income Fund II, Inc.; Puerto Rico Fixed Income Fund\nIII, Inc.; Puerto Rico Fixed Income Fund IV, Inc.; Puerto Rico\nFixed Income Fund V, Inc.; Puerto Rico GNMA and U.S. Government\nTarget Maturity Fund, Inc.; Puerto Rico Investors Bond Fund I,\nInc.; Puerto Rico Investors Tax-Free Fund, Inc.; Puerto Rico\nInvestors Tax-Free Fund II, Inc.; Puerto Rico Investors Tax-Free\nFund III, Inc.; Puerto Rico Investors Tax-Free Fund IV, Inc.;\nPuerto Rico Investors Tax-Free Fund V, Inc.; Puerto Rico Investors\nTax-Free Fund VI, Inc.; Puerto Rico Mortgage-Backed & U.S.\nGovernment Securities Fund, Inc.; Tax-Free Puerto Rico Fund, Inc.;\nTax-Free Puerto Rico Fund II, Inc.; Tax-Free Puerto Rico Target\nMaturity Fund, Inc.; UBS IRA Select Growth & Income Puerto Rico\nFund.\n Jeffrey W. Levitan, with whom Timothy W. Mungovan, John E.\nRoberts, Michael R. Hackett, William D. Dalsen, Martin J.\nBienenstock, Mark D. Harris, Kevin J. Perra, and Proskauer Rose\nLLP were on brief, for the Financial Oversight and Management Board\nfor Puerto Rico, as Representative for the Employees Retirement\nSystem of the Government of the Commonwealth of Puerto Rico.\n Richard B. Levin, with whom Catherine Steege, Melissa Root,\nIan Heath Gershengorn, Lindsay C. Harrison, William K. Dreher,\nRobert Gordon, Richard Levin, Jenner & Block LLP, A.J. Bennazar-\nZequeira, and Bennazar, García, & Milián, C.S.P. were on brief,\nfor the Official Committee of Retired Employees of the Commonwealth\nof Puerto Rico.\n\f Michael Shih, Appellate Division, Civil Staff, Joseph H.\nHunt, Assistant Attorney General, Mark R. Freeman, and Michael S.\nRaab, Appellate Division, Civil Staff, for the United States,\namicus curiae.\n\n\n\n January 30, 2019\n\f LYNCH, Circuit Judge. These appeals involve bonds\n\nissued in 2008 by the Employees Retirement System of the Government\n\nof the Commonwealth of Puerto Rico1 (the \"System\"), which were\n\nbought by bondholders (the \"Bondholders\"), the appellants here.\n\nThe bond documentation offered as security certain property\n\nbelonging or owed to the System, as defined in a \"Pension Funding\n\nBond Resolution.\" The Bondholders claim that they have a perfected\n\nsecurity interest in that property under Puerto Rico's version of\n\nthe Uniform Commercial Code (\"UCC\").\n\n Through the Financial Oversight and Management Board for\n\nPuerto Rico (the \"Oversight Board\"), the System filed suit in the\n\ndistrict court on July 21, 2017, seeking declaratory judgments on\n\nseveral issues related to the validity, breadth, and perfection of\n\nthe Bondholders' asserted security interest, and regarding the\n\nSystem's compliance with a stipulation between the parties (the\n\n\"January 2017 Stipulation\"). The Bondholders brought nine\n\ncounterclaims concerning their asserted security interest as well\n\nas an alleged violation of the January 2017 Stipulation. After\n\n\n\n 1 We use this name here rather than \"Retirement System for\nEmployees of the Government of the Commonwealth of Puerto Rico,\"\nbecause the System, through the Financial Oversight and Management\nBoard for Puerto Rico, filed its complaint in the district court\nunder this name and refers to itself by this name in its brief to\nthis court. In this opinion, the \"ERS name\" refers to the term\nbeginning with \"Employees Retirement System\"; the \"RSE name\"\nrefers to the term beginning with \"Retirement System for\nEmployees.\"\n\n\n - 10 -\n\fboth sides moved for summary judgment, the district court ruled in\n\nfavor of the System, finding that the Bondholders' interest was\n\nnot perfected and so could be avoided under 48 U.S.C. § 2161(a),\n\nthat there had been no violation of the January 2017 Stipulation,\n\nand that two of the Bondholders' counterclaims should be dismissed\n\nwith prejudice. The Fin. Oversight and Mgmt. Bd. for P.R. v.\n\nAltair Glob. Credit Opportunities Fund (a), LLC (In re: The Fin.\n\nOversight and Mgmt. Bd. for P.R.), 590 B.R. 577 (D.P.R. 2018). We\n\nare told the dollar value of the security for the bonds at stake\n\nis about $2.9 billion. The Bondholders appealed.\n\n We agree with the district court on the particular facts\n\nhere that the UCC financing statements filed in 2008 (the \"2008\n\nFinancing Statements\") did not perfect the Bondholders' security\n\ninterest, as they lacked a sufficient description of collateral.\n\nBut we find that the financing statement amendments filed in 2015\n\nand 2016 (together, the \"Financing Statement Amendments\")\n\nsatisfied the filing requirements for perfection when read in\n\nconjunction with the 2008 Financing Statements. We reverse the\n\ndistrict court's determination on the satisfaction of filing\n\nrequirements for perfection by amendment, and hold that the\n\nBondholders satisfied the filing requirements for perfection as of\n\nDecember 17, 2015.\n\n Because the Bondholders' security interest was\n\nperfected, this interest cannot be avoided under the Puerto Rico\n\n\n - 11 -\n\fOversight, Management, and Economic Stability Act's (\"PROMESA\")\n\nincorporation of parts of the Bankruptcy Code, including 11 U.S.C.\n\n§ 544(a), and so we do not reach the issue of whether PROMESA and\n\nother relevant Commonwealth law would allow for the retroactive\n\navoidance of unperfected liens.2 Accordingly, we vacate the\n\ndistrict court's holding on avoidance of the Bondholders' security\n\ninterest. We vacate the dismissal of two of the Bondholders'\n\ncounterclaims and remand to the district court for further\n\nproceedings in light of this opinion. Finally, we affirm the\n\ndismissal of the Bondholders' claim regarding the January 2017\n\nStipulation.\n\n As to the first issue, concerning the 2008 Financing\n\nStatements alone, we decide narrowly on the particular facts\n\npresented. As to the issue of perfection by amendment, also\n\nnarrowly decided, this case presents a unique confluence of\n\ncircumstances involving two languages and a translation,\n\nparticularly regarding the sufficient name of the System under\n\nArticle 9 of the UCC (Secured Transactions), as adopted by the\n\nCommonwealth. Puerto Rico recognizes two official statutory\n\nlanguages. P.R. Laws Ann. tit. 1, § 59. We face a statutory\n\namendment from 2013 (officially translated in 2014) that variously\n\n\n 2 Although we do not reach this issue, we acknowledge with\nappreciation the assistance provided by the United States\nDepartment of Justice in submitting a brief as amicus curiae in\nsupport of the appellees.\n\n\n - 12 -\n\fuses two English terms when translating the same unvaried Spanish\n\nterm for the name of the System. Id. tit. 3, §§ 761, 763. Further,\n\npast official translations, and the System itself, have\n\nconsistently used the ERS name (including in many court filings)\n\nfor over sixty years. We craft our holding narrowly to accommodate\n\nthe very unusual circumstances presented by a new translation that\n\nis, on its face, inconsistent, that varies from every other formal\n\nversion both before and after its presentation, and that arises in\n\na context in which there is no realistic likelihood that anyone\n\nwould search the Department of State of the Government of Puerto\n\nRico's (the \"P.R. Department of State\") records only under one of\n\nthe two forms of the name that appear in the English translation\n\nof the amended statute.\n\n I.\n\n The System is a trust and government agency created in\n\n1951 by an Act of the Commonwealth. Law No. 447 of May 15, 1951,\n\n1951 P.R. Laws 1298 (the \"1951 Enabling Act\") (codified as amended\n\nat P.R. Laws Ann. tit. 3, §§ 761 et seq.). The System is structured\n\nto provide pensions and other retirement benefits to employees and\n\nofficers of the Commonwealth government, members and employees of\n\nthe Commonwealth's Legislative Assembly, and officers and\n\nemployees of the Commonwealth's municipalities and public\n\ncorporations. P.R. Laws Ann. tit 3, § 764. It is designated as\n\n\"independent and separate\" from other Commonwealth agencies. Id.\n\n\n - 13 -\n\f§ 775. Until legislation that went into effect on July 1, 2017,\n\nthe System was funded by mandatory contributions from employees\n\nand employers, and by the System's investment earnings. See\n\nConcurrent Resolution 188 of the House of Representatives of the\n\nGovernment of Puerto Rico; Law No. 106 of August 23, 2017.\n\n As of 2008, the Enabling Act allowed the System to incur\n\ndebt when the Board of Trustees of the System so authorized. P.R.\n\nLaws Ann. tit. 3, § 779(d) (2008). Seeking to decrease an unfunded\n\nliability of approximately $9.9 billion, the Board of Trustees\n\nadopted a \"Pension Funding Bond Resolution\" (the \"Resolution\") on\n\nJanuary 24, 2008. The Resolution allowed for the issuance of about\n\n$2.9 billion in bonds. The Resolution was made publicly available\n\non several governmental websites, including on the Government\n\nDevelopment Bank for Puerto Rico's website and on the System's own\n\nwebsite.\n\n The Bondholders hold some of those bonds issued by the\n\nSystem. The System executed a security agreement (the \"Security\n\nAgreement\"), which purports to grant the Bondholders a security\n\ninterest in \"Pledged Property\" belonging or owed to the System.\n\n\"Pledged Property\" was defined in the Resolution but not in the\n\nSecurity Agreement. The Resolution's definition included the\n\nrequired employer contributions to the System and proceeds from\n\n\n\n\n - 14 -\n\fthese contributions.3 The Security Agreement did not itself define\n\nor otherwise describe \"Pledged Property.\" Rather, it stated that\n\n\"[a]ll capitalized words not defined herein shall have the meaning\n\nascribed to them in the Resolution.\" But the Resolution was not\n\nattached to the Security Agreement, and the Security Agreement did\n\nnot even say what types of property were pledged, whether the\n\nResolution was available to the public, or where the Resolution\n\n\n 3 The Resolution defined \"Pledged Property\" as:\n\n 1. All Revenues.\n 2. All right, title and interest of the\n System in and to Revenues, and all rights to\n receive the same.\n 3. The Funds, Accounts, and Subaccounts held\n by the Fiscal Agent, and moneys and securities\n and, in the case of the Debt Service Reserve\n Account, Reserve Account Cash Equivalents,\n from time to time held by the Fiscal Agent\n under the terms of this Resolution, subject to\n the application thereof as provided in this\n Resolution and to the provisions of Sections\n 1301 and 1303.\n 4. Any and all other rights and personal\n property of every kind and nature from time to\n time hereafter pledged and assigned by the\n System to the Fiscal Agent as and for\n additional security for the Bonds and Parity\n Obligations.\n 5. Any and all cash and non-cash proceeds,\n products, offspring, rents and profits from\n any of the Pledged Property mentioned\n described in paragraphs (1) through (4) above,\n including, without limitation, those from the\n sale, exchange, transfer, collection, loss,\n damage, disposition, substitution or\n replacement of any of the foregoing.\n\nThe Resolution's definition of \"Revenues\" included, among other\nthings, \"All Employers' Contributions.\"\n\n - 15 -\n\fcould be found.\n\n Security interests could be perfected by filing\n\nfinancing statements comporting with the requirements of Article\n\n9 of the UCC, as adopted by the Commonwealth. In 2008, those\n\nrequirements included, among other things, that a financing\n\nstatement \"contain[] a statement indicating the types, or\n\ndescribing the items, of collateral.\" P.R. Laws Ann. tit. 19,\n\n§ 2152(1) (2008).\n\n The Security Agreement specified that \"[the System]\n\nshall cause UCC financing and continuation statements to be filed,\n\nas appropriate, and the Secured Party shall not be responsible for\n\nany UCC filings.\" On or about June 24, 2008, and July 2, 2008,4\n\ntwo financing statements (the 2008 Financing Statements) related\n\nto the System's bonds, as described above, were filed with the\n\nP.R. Department of State. The 2008 Financing Statements each used\n\na standard \"Financing Statement\" form provided by the P.R.\n\nDepartment of State, where such statements are located. Initial\n\nfinancing statements are sometimes referred to as \"UCC-1\"\n\nstatements.\n\n The 2008 Financing Statements described the collateral\n\nas \"[t]he pledged property described in the Security Agreement\n\n\n\n 4 The listed dates -- June 24 and July 2 -- are the dates\nstamped on the documents by the filing officer. The same is true\nfor the listed dates for the Financing Statement Amendments.\n\n\n - 16 -\n\fattached as Exhibit A hereto and by reference made a part thereof.\"\n\nThe Security Agreement, Exhibit A, was attached to each of the\n\n2008 Financing Statements as filed but, as said, did not itself\n\ndescribe the \"Pledged Property\" except as it purported to do by\n\nreference to an unattached other document. That is, the\n\nResolution, which contained the full definition of \"Pledged\n\nProperty\" and other key terms, was not attached. The 2008\n\nFinancing Statements do not otherwise describe or define the\n\n\"Pledged Property\" (meaning the collateral). In short, the\n\ndocuments filed with the P.R. Department of State described the\n\ncollateral only by stating that it was \"Pledged Property\" described\n\nin a document that could only be found somewhere outside the P.R.\n\nDepartment of State.\n\n Between the filing of the 2008 Financing Statements and\n\nthe filing of the Financing Statement Amendments in 2015 and 2016,\n\nthe Commonwealth repealed its earlier version of Article 9 of the\n\nUCC and enacted a revised version, Law No. 21 of January 17, 2012,\n\n2012 P.R. Laws 162 (codified at P.R Laws Ann. tit. 19, §§ 2211-\n\n2409). The updated law went into effect on January 17, 2013, one\n\nyear after its approval. See P.R. Laws Ann. tit. 19, § 2211).\n\nThe new version of Article 9 made modest changes to the\n\nrequirements for financing statements, and made the effective life\n\nof financing statements five years rather than ten years.\n\n On or about December 17, 2015, and January 16, 2016, the\n\n\n - 17 -\n\ffour Financing Statement Amendments were filed. These filings all\n\nused a standard \"Financing Statement Amendment\" form provided by\n\nthe P.R. Department of State. The Financing Statement Amendments\n\ndescribe the collateral as \"[t]he Pledged Property and all proceeds\n\nthereof and all after-acquired property as described more fully in\n\nExhibit A attached hereto and incorporated by reference.\" Unlike\n\nthe 2008 Financing Statements, Exhibit A contained a full\n\ndefinition of \"Pledged Property\" drawn from the Resolution. The\n\nFinancing Statement Amendments provide, in the attached Exhibit A,\n\nthat the debtor is the \"Employees Retirement System of the\n\nGovernment of the Commonwealth of Puerto Rico.\" That naming of\n\nthe debtor is at issue in the argument concerning whether the\n\nFinancing Statement Amendments sufficed to satisfy the filing\n\nrequirements for perfection.5\n\n The P.R. Department of State certified in March 2017\n\nthat a search of the Commonwealth's UCC records under the name\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico\" revealed the 2008 Financing Statements and the\n\nFinancing Statement Amendments. A copy of a UCC search report\n\nfrom October 17, 2017, for a search performed by Wolters Kluwer on\n\nbehalf of the Bondholders, indicates the same. None of the 2008\n\n\n\n 5 The issue of the proper name of the System did not arise\nuntil February 28, 2014, when a translation of the 2013 amended\nEnabling Act was published.\n\n\n - 18 -\n\fFinancing Statements and the Financing Statement Amendments had\n\nbeen removed from the P.R. Department of State's records as of\n\nOctober 2017.\n\n After the filing of the 2008 Financing Statements and\n\nbefore the filing of the Financing Statement Amendments, the\n\nCommonwealth's legislature amended the Enabling Act in 2013. Law\n\nNo. 3 of April 4, 2013, 2013 P.R. Laws 39 (codified at P.R. Laws\n\nAnn. tit 3, § 761 et seq.). From the original Enabling Act in\n\n1951 until 2014, the English translation of the Enabling Act, as\n\ncodified, used \"Employees Retirement System\" as the first part of\n\nthe name of the System, when translating the Spanish term \"Sistema\n\nde Retiro de los Empleados.\" Compare Law No. 447 of May 15, 1951,\n\n1951 P.R. Laws 1298 (English, \"Employees Retirement System\") with\n\nid. at 1299 (Spanish, \"Sistema de Retiro de Los Empleados\"). The\n\nlegislature had amended the Enabling Act numerous times before\n\n2013, including changing the name of the System in 2004 by removing\n\n\"and its Instrumentalities\" and by replacing \"Government of Puerto\n\nRico\" with \"Government of the Commonwealth of Puerto Rico.\" See\n\nP.R. Laws Ann. tit. 3, § 761 (2006). But the English translation\n\nof the System as, in part, \"Employees Retirement System,\" remained\n\nthe same. See P.R. Laws Ann. tit. 3, § 761 (2011); P.R. Laws Ann.\n\ntit. 3, § 761 (2006); P.R. Laws Ann. tit. 3, § 761 (1988).\n\n The English language translation of the 2013 amended\n\nEnabling Act was published on February 28, 2014, more than ten\n\n\n - 19 -\n\fmonths after the 2013 Act's April 4, 2013, approval in Spanish and\n\nabout seven months after its effective date.6 As codified, the\n\ntranslation refers to the System as both \"Retirement System for\n\nEmployees of the Government of the Commonwealth of Puerto Rico\"\n\nand \"Employees Retirement System of the Government of the\n\nCommonwealth of Puerto Rico.\" P.R. Laws Ann. tit. 3, §§ 761,\n\n763(36). In many sections, the translation of the Enabling Act\n\ncontinues to use the prior version of the English name (\"Employees\n\nRetirement System of the Government of the Commonwealth of Puerto\n\nRico\"). Such continuity in the translation carries over to the\n\n\"Statement of Motives\" section and to the definition of the\n\nshorthand \"System,\" as well as to dozens of other sections. In\n\nSection 1-10, which describes how the System was \"to be\n\ndesignated,\" the translation uses the English formulation,\n\n\"Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico\" for the unchanged Spanish original,\n\n\"Sistema de Retiro de los Empleados del Gobierno del Estado Libre\n\nAsociado de Puerto Rico.\" Law No. 3 of April 4, 2013, 2013 P.R.\n\nLaws 64.\n\n Months after the Financing Statement Amendments were\n\n\n 6 Similar or lengthier gaps between the passage of laws\nand the promulgation of their official translations have occurred\nin the Commonwealth. For example, the official English translation\nof the 2004 amendment to the Enabling Act (passed on September 15,\n2004), Law No. 296 of September 15, 2004, was certified and\npublished on March 13, 2007.\n\n\n - 20 -\n\ffiled in late 2015 and early 2016, Congress enacted PROMESA, 48\n\nU.S.C. § 2101 et seq., on June 30, 2016. Among other things,\n\nPROMESA created the Oversight Board and granted the Board a range\n\nof powers over the Commonwealth's finances, see, e.g., id. §§ 2121-\n\n2129, including the general mandate to craft \"a method [for the\n\nCommonwealth] to achieve fiscal responsibility and access to the\n\ncapital markets,\" id. § 2121(a).\n\n PROMESA incorporated by reference certain provisions of\n\nthe Bankruptcy Code, id. § 2161(a), including the \"strong-arm\"\n\nprovision at 11 U.S.C. § 544(a).7 That provision \"set[s] out the\n\n\n 7 Section 544(a) provides:\n\n The trustee shall have, as of the commencement\n of the case, and without regard to any\n knowledge of the trustee or of any creditor,\n the rights and powers of, or may avoid any\n transfer of property of the debtor or any\n obligation incurred by the debtor that is\n voidable by —\n (1) a creditor that extends credit to\n the debtor at the time of the\n commencement of the case, and that\n obtains, at such time and with respect to\n such credit, a judicial lien on all\n property on which a creditor on a simple\n contract could have obtained such a\n judicial lien, whether or not such a\n creditor exists;\n (2) a creditor that extends credit to\n the debtor at the time of the\n commencement of the case, and obtains, at\n such time and with respect to such\n credit, an execution against the debtor\n that is returned unsatisfied at such\n time, whether or not such a creditor\n exists; or\n\n - 21 -\n\fcircumstances under which a trustee\" may permissibly \"pursue\n\navoidance\" of certain interests. Merit Mgmt. Grp., LP v. FTI\n\nConsulting, Inc., 138 S. Ct. 883, 888 (2018).\n\n Pursuant to Section 301(c)(7) of PROMESA, the Oversight\n\nBoard is the \"trustee\" as that term is defined in the Bankruptcy\n\nCode (except under one circumstance that is not relevant here, see\n\n11 U.S.C § 926). 48 U.S.C. § 2161(c)(7). PROMESA also provides\n\nthat \"Subchapters III and VI shall apply with respect to debts,\n\nclaims, and liens . . . created before, on, or after [June 30,\n\n2016].\" Id. § 2101(b)(2).\n\n PROMESA's enactment triggered an automatic temporary\n\nstay, under Section 405, on creditors' remedies against the\n\nCommonwealth and its property. Id. § 2194(a)-(b). The Bondholders\n\nmoved to lift that stay, but that motion was denied by the district\n\ncourt. See Peaje Invs. LLC v. García-Padilla, 845 F.3d 505, 510\n\n(1st Cir. 2017). This court vacated the district court's decision\n\nin part and remanded for further proceedings, id. at 516, and\n\n\n\n\n (3) a bona fide purchaser of real\n property, other than fixtures, from the\n debtor, against whom applicable law\n permits such transfer to be perfected,\n that obtains the status of a bona fide\n purchaser and has perfected such transfer\n at the time of the commencement of the\n case, whether or not such a purchaser\n exists.\n\n 11 U.S.C. § 544(a).\n\n\n - 22 -\n\fexpressed general concerns with the protection afforded for the\n\nBondholders' property, id. at 511-12.\n\n On remand, the System and the Bondholders entered into\n\nthe January 2017 Stipulation, in order to resolve Altair Global\n\nCredit Opportunities Fund (A), LLC v. García-Padilla, No. 16-cv-\n\n2696. The January 2017 Stipulation required, in relevant part,\n\nthat \"Employers' Contributions (as defined in the ERS Bond\n\nResolutions) received by the ERS during the pendency of the stay\n\nimposed pursuant to [PROMESA] § 405 shall be transferred by the\n\nERS to [a segregated account] for the benefit of the holders of\n\nthe ERS bonds.\"\n\n On May 3, 2017, the Oversight Board filed a petition\n\nunder Title III of PROMESA on behalf of the Commonwealth. On May\n\n21, 2017, the Oversight Board filed a Title III petition on behalf\n\nof the System, which triggered an automatic stay of litigation\n\nagainst the System. The Bondholders moved to lift the stay, and\n\nthe parties entered into a Joint Stipulation that resolved the\n\nBondholders' motion. The Joint Stipulation stated that an\n\nadversary proceeding would be filed by the System on or before\n\nJuly 21, 2017, and limited the scope of the proceeding to the\n\n\"validity, priority, extent and enforceability\" of the\n\nBondholders' claimed security interest and the System's rights\n\nregarding employer contributions received during May 2017, as well\n\nas relevant counterclaims by the Bondholders.\n\n\n - 23 -\n\f On July 21, 2017, the System, through the Oversight\n\nBoard, brought this case in federal district court against the\n\nBondholders, seeking declarations about the status, scope, and\n\nvalidity of the Bondholders' claimed security interest in the\n\n\"Pledged Property,\" and about the System's compliance with the\n\nJanuary 2017 Stipulation. See In re: Fin. Oversight & Mgmt. Bd.\n\nfor P.R., 590 B.R. at 583.8 The Bondholders asserted nine\n\ncounterclaims, requesting declarations concerning their asserted\n\nsecurity interest as well as an alleged violation of the January\n\n2017 Stipulation.\n\n The parties both moved for summary judgment. Id. The\n\nSystem sought judgment in its favor on its four claims; the\n\nBondholders sought the dismissal of all of the System's claims as\n\nwell as judgment in their favor on all of their counterclaims.\n\nId.\n\n On August 17, 2018, the district court granted the\n\nSystem's motion for summary judgment in part and denied the\n\nBondholders' cross-motion in its entirety. Id. at 599-600. The\n\n\n 8 In other litigation before the commencement of the\nSystem's Title III case, the System had stated that at least some\nof the Bondholders had \"valid and enforceable liens in over\nhundreds of millions of dollars of ERS revenue.\" Respondent\nEmployees Retirement System of the Government of Puerto Rico's\nBrief in Opposition to Motion for Relief from the PROMESA Automatic\nStay at 10, Altair Global Credit Opportunities Fund (A), LLC. v.\nGarcia Padílla, Case No. 3:16-cv-02696-FAB (D.P.R. Oct. 26, 2016).\nThe district court noted this acknowledgment. In re: Fin.\nOversight & Mgmt. Bd. for P.R., 590 B.R. at 587.\n\n\n - 24 -\n\fdistrict court held that any security interest the Bondholders\n\nmight possess had not been perfected by the 2008 Financing\n\nStatements, because those Statements did not contain an adequate\n\ndescription of the collateral as required under Article 9 in 2008.\n\nId. at 589 (citing P.R. Laws Ann. tit. 19, § 2152(1) (2008)). The\n\ndistrict court then determined that the Financing Statement\n\nAmendments did not perfect the Bondholders' security interest,\n\nbecause they did not identify the debtor by its correct legal name,\n\nwhich the court determined was the RSE name, as the court felt was\n\nrequired by the version of Article 9 operative in 2015 and 2016.\n\nId. at 592 (citing P.R. Laws Ann. tit. 19, § 2322(a)(1)).\n\n Starting from the determination that the Bondholders'\n\ninterest was unperfected when the Title III case began, the\n\ndistrict court then held that the Oversight Board, as trustee,\n\ncould avoid the liens under the strong-arm provision at 11 U.S.C.\n\n§ 544(a), which PROMESA incorporates, see 48 U.S.C. § 2161(a). In\n\nre: Fin. Oversight & Mgmt. Bd. for P.R., 590 B.R. at 592-98. That\n\nis, Commonwealth law did not prevent a hypothetical creditor from\n\nobtaining a judgment lien against the System's assets at the time\n\nwhen the Title III case commenced. Id. at 594. The district court\n\nthus invalidated the Bondholders' interests pursuant to Section\n\n544(a). The district court then held that the System did not\n\nviolate the January 2017 Stipulation because the adversary\n\nproceedings were limited to claims or counterclaims related to\n\n\n - 25 -\n\femployer contributions received during May of 2017, and the\n\nSystem's obligation to transfer such funds to a segregated account\n\nclearly ended with the PROMESA stay on May 1, 2017. Id. at 599.\n\n Following a joint response to an order to show cause as\n\nto why the Bondholders' counterclaims One through Four \"ought not\n\nto be dismissed for failure to state a claim upon which relief may\n\nbe granted,\" the district court dismissed the Bondholders'\n\ncounterclaims with prejudice on September 5, 2018.\n\n The Bondholders timely appealed, and this court granted\n\nmotions to consolidate these appeals.\n\n II.\n\n This case comes on summary judgment. In reviewing grants\n\nof summary judgment, \"we take as true the facts documented in the\n\nrecord below, resolving any factual conflicts or disparities in\n\nfavor of the nonmovant.\" Colt Def. LLC v. Bushmaster Firearms,\n\nInc., 486 F.3d 701, 705 (1st Cir. 2007). Nearly all of the\n\noperative facts are undisputed here, and the grant of summary\n\njudgment turns primarily on interpretations of law, which this\n\ncourt reviews de novo, or mixed questions of law and fact, for\n\nwhich \"we employ a degree-of-deference continuum, providing non-\n\ndeferential plenary review for law-dominated questions and\n\ndeferential review for fact-dominated questions.\" Johnson v. Bos.\n\nPub. Sch., 906 F.3d 182, 191 (1st Cir. 2018) (internal quotation\n\nmarks omitted).\n\n\n - 26 -\n\f We first consider perfection by the 2008 Financing\n\nStatements on their own, and then in conjunction with the later\n\nFinancing Statement Amendments, before briefly considering\n\navoidance under PROMESA. We then address the dismissal of two of\n\nthe Bondholders' counterclaims and the alleged violation of the\n\nJanuary 2017 Stipulation.\n\nA. Perfection by the 2008 Financing Statements\n\n The Bondholders argue that the initial 2008 Financing\n\nStatements perfected their security interest. Under the former\n\nversion of Article 9 operative in 2008,\n\n [a] financing statement is sufficient if it\n [1] gives the names of the debtor and the\n secured party, [2] is signed by the debtor,\n [3] gives an address of the secured party from\n which information concerning the security\n interest may be obtained, [4] gives a mailing\n address of the debtor and [5] contains a\n statement indicating the types, or describing\n the items, of collateral.\n\nP.R. Laws Ann. tit. 19, § 2152(1) (2008). There is no dispute\n\nthat the 2008 Financing Statements met the first four requirements\n\nat the time they were filed, and so those elements are not\n\nconsidered here. We also stress that the validity of the\n\nunderlying Security Agreement is not at issue. Security agreements\n\nare private contracts between parties and do not have the same\n\npublic notice purpose as financing statements. See Webb Co. v.\n\nFirst City Bank (In re Softalk Publ'g Co., Inc.), 856 F.2d 1328,\n\n1330 (9th Cir. 1988). Instead, our discussion is limited only to\n\n\n - 27 -\n\fwhether the 2008 Financing Statements \"contain[] a statement\n\nindicating the types, or describing the items, of collateral,\" as\n\nrequired by the then-existing statute. See P.R. Laws Ann. tit.\n\n19, § 2152(1) (2008).\n\n The Bondholders argue that we should adopt a lenient\n\nunderstanding of the collateral description requirement, such that\n\nthe mere reference in the Security Agreement to the definition of\n\n\"Pledged Property\" contained in a separate document, the\n\nResolution, constituted a sufficient description, even though the\n\nResolution, and thus its description of \"Pledged Property,\" was\n\nnot attached to the 2008 Financing Statements. The Bondholders\n\ncite a number of cases to argue that incorporation by reference is\n\nappropriate in this situation. They argue this is in part because\n\nthe collateral description in a financing statement is, in their\n\nview, only \"a starting point\" in providing notice to an interested\n\nparty. John Deere Co. of Balt. v. William C. Pahl Constr. Co., 34\n\nA.D.2d 85, 88 (N.Y. App. Div. 1970).\n\n The System, joined by the Committee of Retired Employees\n\nof the Commonwealth of Puerto Rico (the \"Committee\") by reference\n\nin its brief, counters that the UCC's goals, like public notice,\n\nrequire a strict rule that interested parties should not face the\n\nburden and potential risks of further searching for a collateral\n\ndescription not found within or appended to a financing statement.\n\n We clear away some arguments which are beside the point.\n\n\n - 28 -\n\fIt is not helpful for the parties to use terms such as \"liberal\"\n\nor \"strict\" construction of Article 9. And it is likely that on\n\nsome facts, incorporation by reference was permissible under the\n\nversion of Article 9 operative in the Commonwealth when the 2008\n\nFinancing Statements were filed. That principle is not really at\n\nissue. On the facts on this record, we, like the district court,\n\nconclude that the 2008 Financing Statements were insufficient to\n\nperfect the security interest under P.R. Laws Ann. tit. 19,\n\n§ 2152(1) (2008).9 There has been no literal compliance with this\n\nrule, and this provision should be interpreted consonant with the\n\ngoals of the UCC.\n\n Our holding of an insufficient collateral description\n\ndepends heavily on the facts, where a) the collateral is not\n\n\n\n\n 9 The Bondholders do not cite controlling authority on\nthis issue. In Chase Bank of Fla., N.A. v. Muscarella, 582 So. 2d\n1196 (Fla. Dist. Ct. App. 1991), part of the collateral -- the\n\"Partnership Interest\" -- was listed in the financing statement\nitself, see id. at 1197, and so we agree that the \"[Muscarella]\nopinion does not stand for the proposition that it is sufficient\nfor a financing statement to merely refer to the underlying\nsecurity agreement and thereby incorporate by reference that\ndocument's collateral description.\" First Midwest Bank v.\nReinbold (In re: I80 Equip., LLC), 591 B.R. 353, 361 (Bankr. C.D.\nIll. 2018). In Int'l Home Prod., Inc. v. First Bank of P.R., Inc.,\n495 B.R. 152 (D.P.R. 2013), the referenced document was attached\nto the financing statement rather than filed or accessible only\nelsewhere. Id. at 160 n.8.\n And the citation to John Deere is inapposite here,\nbecause the reference in that case to a \"starting point for\ninvestigation\" does not refer to a description of collateral. 34\nA.D.2d at 88.\n\n\n\n - 29 -\n\fdescribed, even by type(s), in the 2008 Financing Statements or\n\nattachments; b) the 2008 Financing Statements do not tell\n\ninterested parties where to find the referenced document (the\n\nResolution) which contains the fuller collateral description; and\n\nc) the Resolution is not at the UCC filing office.\n\n First, the 2008 Financing Statements do not describe\n\neven the type(s) of collateral, much less the items, at issue.\n\nCf. Elf Atochem N. Am., Inc. v. Celco, Inc., 927 P.2d 355, 363\n\n(Ariz. Ct. App. 1996) (finding sufficient a financing statement\n\nthat described the collateral as \"equipment,\" as further described\n\nin two specific but unattached sales orders). They also do not\n\nattach the document (the Resolution) referenced as describing the\n\ncollateral. Nor do those facts alone define the issue before us.\n\nIn addition, the referenced document -- the Resolution -- was held\n\nin a different location from the UCC filing office, and the 2008\n\nFinancing Statements (including the attached Security Agreement)\n\ncontain no indication of the referenced document's location or how\n\nto find it.\n\n This total combination of facts undercuts several key\n\ngoals of the UCC and its filing system. These goals include fair\n\nnotice to other creditors and the public of a security interest.\n\nSee UCC § 9-502 cmt. 2;10 Wheeling & Lake Erie Ry. Co. v. Keach (In\n\n\n 10 \"UCC Official Comments do not have the force of law, but\nare nonetheless the most useful of several aids to interpretation\n\n\n - 30 -\n\fre: Montreal, Me. & Atl. Ry., Ltd.), 799 F.3d 1, 11 (1st Cir. 2015)\n\n(\"[A] primary goal of both Article 9 and . . . perfection rules is\n\nto ensure that other creditors have notice of [a] security\n\ninterest.\"); In re Softalk Publ'g Co., 856 F.2d 1328, 1330 (9th\n\nCir. 1988) (\"The [UCC] financing statement serves to give notice\n\nto other creditors or potential creditors that the filing creditor\n\nmight have a security interest in certain assets of the named\n\ndebtor.\"); In re Cushman Bakery, 526 F.2d 23, 28 (1st Cir. 1975)\n\n(stating that \"the system of notice filing is designed to . . .\n\napprise creditors that the secured party may have a security\n\ninterest in the collateral described in the financing\n\nstatement\").11 Article 9 was also meant to facilitate the expansion\n\nof commercial practices. See P.R. Laws Ann. tit. 19, § 401(2).12\n\n\nand construction of the [UCC].\" JOM, Inc. v. Adell Plastics, Inc.,\n193 F.3d 47, 57 n.6 (1st Cir. 1999) (internal quotation marks\nomitted).\n 11 Several of the cases cited by the Bondholders consider\nsecurity agreements rather than financing statements. E.g. Nolden\nv. Plant Reclamation (In the matter of Amex-Protein Dev. Corp.),\n504 F.2d 1056 (9th Cir. 1974); Greenville Riverboat, LLC v. Less,\nGetz & Lipman, P.L.L.C., 131 F. Supp. 2d 842 (S.D. Miss. 2000).\nAs noted, security agreements are private contracts that do not\nhave the same public notice purpose as financing statements. See\nIn re Softalk Publ'g Co., 856 F.2d 1328, 1330 (9th Cir. 1988).\n 12 Where a referenced document is not in the UCC records\nand its location is not listed in the financing statement itself\n(nor how to find it), an interested party must do additional\nsearching at its own expense to determine the collateral at issue.\nThis remains true even where the extrinsic document is publicly\navailable elsewhere: The interested party still has to search\nbeyond where the initial financing statement has been filed, and\ndo so without any guidance. It may not have been difficult for\n\n\n - 31 -\n\f Here, as said, the 2008 Financing Statements do not\n\ndescribe even the type(s) of collateral; instead, they describe\n\nthe collateral only by reference to an extrinsic document located\n\noutside the UCC filing office, and that document's location is not\n\nlisted in the financing statement. This at best gives an\n\ninterested party notice about an interest in some undescribed\n\ncollateral, but does not adequately specify what collateral is\n\nencumbered. That is, an interested party knowing nothing more\n\nthan this does not have \"actual knowledge\" and has not \"received\n\na notice,\" see P.R. Laws Ann. tit. 19, § 451(25)(a)-(b) (2008), of\n\nthe collateral at issue. Requiring interested parties to contact\n\ndebtors at their own expense about encumbered collateral, with no\n\nguarantee of a timely or accurate answer, would run counter to the\n\nnotice purpose of the UCC.13 See, e.g., In re Quality Seafoods,\n\n\n\ninterested parties to find the Resolution here, but no party\ndisputes that additional searching would have been necessary.\n Interested parties doing such a search could well have\njustifiable concerns about the extrinsic referenced document.\nHow, for example, would an interested party know whether a\ndescription of collateral in the extrinsic document is the latest\noperative version (rather than a superseded version), whether that\ndocument is complete, or whether the document found on another\nwebsite or at another location is authentic rather than doctored\nin some way? Forcing interested parties to undertake additional\nwork and expense merely to find a basic collateral description\ncuts against the goal of expansion of commercial practices.\n 13 In re Cushman Bakery did not determine that further\ninquiry by interested parties regarding the specific encumbered\ncollateral was required under Article 9, but instead stated only\nthat \"further inquiry from the parties concerned [would] be\nnecessary to disclose the complete state of affairs\" around a\n\n\n - 32 -\n\fInc., 104 B.R. 560, 561 (Bankr. D. Mass. 1989).\n\n The UCC filing requirements are clear. See Uniroyal,\n\nInc. v. Universal Tire & Auto Supply Co., 557 F.2d 22, 23 (1st\n\nCir. 1977). It would not have been difficult whatsoever for the\n\n2008 Financing Statements to provide proper notice. The Resolution\n\ncould simply have been attached to these filings, as the Security\n\nAgreement was. Instead, as they stand, the 2008 Financing\n\nStatements would leave a reasonable creditor or interested party\n\nwith doubts as to the collateral at issue. We do not interpret\n\nthe former UCC provision in a way contrary to its purposes, above\n\nall notice, and so the description of collateral in the 2008\n\nFinancing Statements was insufficient.\n\n Having resolved the logically antecedent question\n\nconcerning the first UCC filings, we turn to the amendment issues.\n\nB. Lapse of 2008 Financing Statements\n\n The System and the Committee argue that the 2008\n\nFinancing Statements could not later satisfy the requirements for\n\nperfection, by amendment, because the 2008 Financing Statements\n\nhad lapsed by the time the Financing Statement Amendments were\n\nfiled in 2015 and 2016. The Commonwealth's enactment of a revised\n\nArticle 9, they argue, shortened the effective time period of an\n\ninitial financing statement from ten years to five years. Compare\n\n\n\ntransaction. 526 F.2d at 28-29 (emphasis added).\n\n\n - 33 -\n\fP.R. Laws Ann. tit. 19, § 2335(a) (five years) with id. § 2153(2)\n\n(2008) (ten years). Here, the Financing Statement Amendments were\n\nfiled about seven and a half years after the 2008 Financing\n\nStatements. Because lapsed financing statements are ineffective,\n\nsee P.R. Laws Ann. tit. 19, § 2335(c), the Committee argues that\n\nthe Amendments filed by the Bondholders could not have cured the\n\ndeficiencies as to the collateral description in the 2008 Financing\n\nStatements. In support of their view, the System and the Committee\n\nprimarily point to a transition provision, the \"Savings clause,\"\n\nin the revised Article 9, which states that \"[e]xcept as otherwise\n\nprovided in this subchapter, this act applies to a transaction or\n\nlien within its scope, even if the transaction or lien was entered\n\ninto or created before this act takes effect.\" Id. § 2402(a).\n\n This argument on lapse fails for several reasons. First,\n\nas to retroactivity, this Savings clause is not intended to apply\n\nto the separate provision that shortened the life of financing\n\nstatements on its effective date. The Commonwealth's Law 17 of\n\n2014, which clarified that the effective time period of financing\n\nstatements was five years, does not contain a statement concerning\n\nretroactivity. See Law No. 17 of January 16, 2014. And as a\n\ntextual matter, we would expect that a provision intended to apply\n\nretroactively to financing statements would directly mention\n\nfinancing statements, particularly given the Commonwealth's long-\n\nstanding requirement that a law must \"expressly so decree\" in order\n\n\n - 34 -\n\fto have retroactive effect. P.R. Laws Ann. tit. 31, § 3.\n\n Second, the P.R. Department of State, where UCC filings\n\nare made, considered the amendment to the time period \"for the\n\nlife of an initial financing statement\" and concluded that the\n\ndecrease to five years \"cannot be retroactive.\" P.R. Dept. of\n\nState, Circular 2014-01, Clarifications on Term for Filing\n\nContinuing Financing Statements Based on Law 17-2014 (Jan. 24,\n\n2014) (English trans.). That is, \"for initial financ[ing]\n\nstatements filed on or before January 15, 2014, [the] term is ten\n\n(10) years.\" Id. 14 Though this Circular does not have the force\n\nof law, it is informative on this issue. Consistent with this\n\nCircular, the Filing Office did not refuse to accept the Financing\n\nStatement Amendments, as it would have been required to do if the\n\n2008 Financing Statements had lapsed. See P.R. Laws Ann. tit. 19,\n\n§ 2336(b)(3)(B)(ii).\n\n Third, our conclusion comports with P.R. Laws Ann. tit.\n\n31, § 3, the general provision of the Commonwealth's Civil Code,\n\nwhich states that \"[i]n no case shall the retroactive effect of a\n\nlaw operate to the prejudice of rights acquired under previous\n\n\n\n\n 14At oral argument, counsel for the System suggested that\nthe P.R. Department of State's Circular applied only to perfected\ninterests. This is incorrect. The Circular refers to \"initial\nfinancing statements\" in bold text on both pages and does not limit\nits determination regarding retroactive effect to previously\nperfected interests.\n\n\n - 35 -\n\flegislative action.\"15 Acceptance of the System's position would\n\nrun afoul of this provision. The enactment of the old Article 9\n\ninto Commonwealth law was clearly a legislative action. Applying\n\nthe five-year rule retroactively would harm the rights of creditors\n\nholding perfected security interests through initial financing\n\nstatements that were between five and ten years old on January 16,\n\n2014, the effective date of the modified rule. See id. tit. 19,\n\n§ 2335(a). Nothing in the law on the effective time limit for\n\nfinancing statements suggests treating financing statements\n\ndifferently depending on perfection, and instead refers broadly to\n\n\"a filed financing statement\" and the \"date of filing,\" id.\n\n(emphasis added). So, the bar on retroactivity protects all filers\n\nin the time period at issue (which includes the Bondholders in\n\nthis case).\n\n The 2008 Financing Statements had not lapsed when the\n\nFinancing Statement Amendments were filed about seven and a half\n\nyears later, because the ten-year rule applied to the 2008\n\nFinancing Statements.\n\n\n\n\n 15 As a general matter, the Supreme Court of the\nCommonwealth of Puerto Rico has suggested, considering this law,\nthat it is \"highly desirable that . . . [a] new rule will have\nprospective effect; especially, when contractual or property\nrights are at stake.\" Almodóvar v. Róman, 125 P.R. Offic. Trans.\n218 (P.R. 1990).\n\n\n - 36 -\n\fC. Perfection by the Financing Statement Amendments in\n Conjunction with the 2008 Financing Statements\n\n We next consider whether the Financing Statement\n\nAmendments cured defects in the initial Statements, when these\n\nfilings are read together. See, e.g., P.R. Laws Ann. tit. 19,\n\n§ 2404(3)(B); see also Miami Valley Prod. Credit Ass'n v. Kimley,\n\n536 N.E.2d 1182, 1186 (Ohio Ct. App. 1987) (\"We are willing to\n\ntreat the two financing statements as a single financing statement\n\n. . . .\"). We do not reach the Bondholders' alternative argument\n\nthat the Financing Statement Amendments independently perfected\n\ntheir security interest, since we determine that the Financing\n\nStatement Amendments cured defects in the 2008 Financing\n\nStatements. Similarly, we do not reach the Bondholders' argument\n\nthat Section 2323 allows the use of \"other name[s]\" of a debtor,\n\nsee P.R. Laws Ann. tit. 19, § 2323(b)(1), as this would require a\n\nbroader consideration of aspects of Article 9 that are beyond the\n\nnecessary scope of this case.\n\n Article 9 contemplates situations where a financing\n\nstatement amendment \"cures\" an earlier financing statement by\n\nfixing outdated or incorrect information in the financing\n\nstatement, such as after a name change by a debtor. See, e.g.,\n\nid. § 2327(c). Under Article 9, \"[a] security interest . . . (3)\n\nbecomes perfected . . . (B) when the applicable requirements for\n\nperfection are satisfied.\" Id. § 2404(3)(B). As to these\n\n\n\n - 37 -\n\f\"applicable requirements,\" a financing statement is sufficient\n\nonly \"if it: (1) Provides the name of the debtor; (2) provides the\n\nname of the secured party or a representative of the secured party,\n\nand (3) indicates the collateral covered by the financing\n\nstatement.\" Id. § 2322(a). We now consider the Bondholders'\n\ncompliance with these requirements in the 2008 Financing\n\nStatements and the Financing Statement Amendments.\n\n 1. Name of the Secured Party and Collateral Description\n\n The Financing Statement Amendments sufficiently provide\n\nthe name of the secured party's agent in Exhibit A: \"The Bank of\n\nNew York Mellon, as Fiscal Agent,\" as required under Section\n\n2322(a)(2).16 No party disputes this clear point.\n\n As to the collateral description requirement, under the\n\nnew Article 9, a collateral description of personal property is\n\nsufficient \"whether or not it is specific, if it reasonably\n\nidentifies what is described,\" id. § 2218(a), but a \"[s]upergeneric\n\ndescription [is] not sufficient,\" id. § 2218(c). One of the\n\n\"[e]xamples of reasonable identification,\" id. § 2218(b), under\n\nArticle 9 is a \"[s]pecific listing\" of the collateral, id.\n\n§ 2218(b)(1).\n\n Here, the Financing Statement Amendments described the\n\ncollateral as \"[t]he Pledged Property and all proceeds thereof and\n\n\n 16 The 2008 Financing Statements also properly list the\nSecured Party as \"The Bank of New York, as fiscal agent[.]\"\n\n\n - 38 -\n\fall after-acquired property as described more fully in Exhibit A\n\nattached hereto and incorporated by reference.\" Exhibit A, in\n\nturn, contained a detailed definition of \"Pledged Property.\"17\n\nEach of the relevant capitalized terms in the definition of\n\n\"Pledged Property\" -- \"Revenues,\" \"Funds,\" \"Accounts,\"\n\n\"Subaccounts,\" \"Fiscal Agent,\" \"Debt Service Reserve Account,\" and\n\n\"Resolution\" -- is also defined in Exhibit A. The definition of\n\n\"Pledged Property\" satisfied one of the \"[e]xamples of reasonable\n\nidentification\" by providing a \"[s]pecific listing\" of the\n\ncollateral. Id. It therefore suffices as a description of\n\ncollateral.\n\n 2. Name of the Debtor\n\n We now turn to the key question of whether the Financing\n\nStatement Amendments contain a sufficient \"name of the debtor.\"\n\nArticle 9 contains different requirements for the names of\n\nregistered organizations and for the names of individuals. A\n\n\"[r]egistered organization\" is defined, in part, as \"an\n\norganization organized solely under the law of a single state or\n\nthe United States by the filing of a public organic record with,\n\nthe issuance of a public organic record by, or the enactment of\n\nlegislation by the state or United States.\" Id. § 2212(a)(71).\n\nThe System is a registered organization because it is an\n\n\n 17 The full definition of \"Pledged Property\" is the same as\nin the Resolution, and is reproduced in note 3, supra.\n\n\n - 39 -\n\forganization formed and organized by the Commonwealth's enactment\n\nof legislation: the 1951 Enabling Act. When a debtor is a\n\nregistered organization,\n\n [a] financing statement sufficiently provides\n the name of the debtor . . . only if the\n financing statement provides the name that is\n stated to be the registered organization's\n name on the public organic record most\n recently filed with or issued or enacted by\n the registered organization's jurisdiction of\n organization which purports to state, amend,\n or restate the registered organization's name.\n\nId. tit. 19, § 2323(a)(1). Though a financing statement that\n\n\"provides only the debtor's trade name does not sufficiently\n\nprovide the name of the debtor,\" id. § 2323(c), an otherwise\n\nsufficient financing statement, containing a correct name of the\n\ndebtor, is \"not rendered ineffective by the absence of . . . [a]\n\ntrade name or other name of the debtor,\" id. § 2323(b).18\n\n\n\n 18 Article 9 also provides a safe harbor provision for minor\nerrors or omissions: \"A financing statement substantially\nsatisfying the requirements of this subchapter is effective, even\nif it has minor errors or omissions, unless the errors or omissions\nmake the financing statement seriously misleading.\" P.R. Laws\nAnn. tit. 19, § 2326(a). For a name,\n\n if a search of the records of the filing office\n under the debtor's correct name, using the\n filing office's standard search logic, if any,\n would disclose a financing statement that\n fails sufficiently to provide the name of the\n debtor in accordance with § 2323 (a) of this\n title, the name provided does not make the\n financing statement seriously misleading.\n\nId. § 2326(c).\n\n\n - 40 -\n\f Like the 2008 Financing Statements, Exhibit A to the\n\nFinancing Statement Amendments stated the name of the debtor as\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico.\" The 2008 Financing Statements also stated the\n\n\"[e]ntity name\" of the debtor as \"Employees Retirement System of\n\nthe Government of the Commonwealth of Puerto Rico.\" The System\n\nand the Committee argue that, as of February 28, 2018, this became\n\nthe incorrect name because, in their view, the English translation\n\nof the 2013 amendment to the Enabling Act changed the System's\n\nEnglish name. Id. tit. 3, § 761. The English translation of that\n\nAct states that \"[a] retirement and benefit system to be designated\n\nas the 'Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico' . . . is hereby created.\" Law No. 3\n\nof April 4, 2013, 2013 P.R. Laws 64. In the System's view, the\n\n2013 amendment to the Enabling Act is the relevant \"public organic\n\nrecord most recently filed with or issued or enacted by the\n\nregistered organization's jurisdiction of organization.\" P.R.\n\nLaws Ann. tit. 19, § 2323(a)(1). The System argues that Section\n\n1-101, codified at P.R. Laws Ann. tit. 3, § 761, alone is the\n\nsection which \"state[s]\" the name of the System under Section\n\n2323(a)(1), and so concludes that the RSE name is the name for\n\nArticle 9 purposes. That is, the System argues that it is\n\nirrelevant that other sections of the Act use \"Employees Retirement\n\nSystem,\" see, e.g., id. § 763(36), because only Section 1-101 of\n\n\n - 41 -\n\fthe translation \"purports to state, amend, or restate the\n\nregistered organization's name,\" id. tit. 19, § 2323(a)(1). Even\n\nif this were a translation error, the System argues, \"that\n\nerroneous translation would nevertheless constitute [the System's]\n\nname for Article 9 purposes.\" The System argues that any UCC\n\nfiling (whether a financing statement or financing statement\n\namendment) under \"Employees Retirement System of the Government of\n\nthe Commonwealth of Puerto Rico\" does not state the correct name.\n\nOn this view, because a search under the correct name --\n\n\"Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico\" -- would not find such a UCC filing,\n\nuse of the ERS name is seriously misleading. P.R. Laws Ann. tit.\n\n19, § 2326(c).\n\n The Bondholders make numerous arguments in opposition\n\nregarding the sufficiency of the name used, some statutory and\n\nsome focused on the System's own conduct. We do not detail those\n\narguments further, but deal with them in our analysis.\n\n We resolve the merits of this matter on the record, which\n\nis adequate. Both the 2008 Financing Statements and the Financing\n\nStatement Amendments were filed in English. And so we look to the\n\n2014 English translation of the Enabling Act to determine whether\n\nthe Financing Statement Amendments comply with the UCC's reference\n\nto the \"public organic record most recently . . . enacted by the\n\n[System's] jurisdiction of organization which purports to state,\n\n\n - 42 -\n\famend, or restate the [System's] name.\" P.R. Laws Ann. tit. 19,\n\n§ 2323(a)(1). The \"to be designated as\" language codified at\n\nSection 761 does not mean that no other portion of the statute\n\n\"state[s]\" the name of the System for UCC purposes. The System\n\nmisconstrues the relevant UCC provision here, by suggesting that\n\nonly the first section of the Enabling Act \"purports to state,\n\namend, or restate the registered organization's name,\" id. tit.\n\n19, § 2323(a)(1), because that section uses the following\n\nlanguage: \"A retirement and benefit system to be designated as the\n\n'Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico,' . . . is hereby created.\" Id. tit.\n\n3, § 761. The requirement is that a filer \"provide the name that\n\nis stated\" in the \"public organic record . . . which purports to\n\nstate, amend, or restate the registered organization's name.\" Id.\n\n(emphasis added). The latter clause, starting with \"which\n\npurports,\" plainly modifies \"public organic record.\" So, it does\n\nnot follow that only one of many clauses in the statute must be\n\nall that can be considered when determining what \"name . . . is\n\nstated\" in the \"public organic record.\"19 Instead, this UCC\n\n\n 19 The System's argument by analogy to the UCC's provision,\nP.R. Laws Ann. tit. 19, § 2323(a)(4), regarding an individual's\nname on a driver's license, is unpersuasive. The System argues\nthat since an incorrect name on a driver's license must be used as\nthe party's name in a sufficient UCC filing, if the filing is made\nin the same state as the driver's license was issued, the RSE name\nmust be used here (whether or not it is a correct name). This\nargument by analogy is necessarily premised on the view that the\n\n\n - 43 -\n\fprovision directs focus to the entire \"public organic record which\n\npurports to state, amend, or restate the registered organization's\n\nname.\" Id. The fact that Section 1-101 of the English translation\n\nof the amended Enabling Act uses \"Retirement System for Employees\n\nof the Government of the Commonwealth of Puerto Rico\" does not end\n\nthe inquiry.\n\n The official English translation, on its face,\n\nrepeatedly translates the exact same Spanish name in two different\n\nways.20 Both \"Retirement System for Employees\" and \"Employees\n\nRetirement System,\" are used, seemingly interchangeably,\n\nthroughout the translated Act as codified. No provision of the\n\nAct states, nor even suggests, that the ERS name is used as a trade\n\n\n\n2013 amended Act states only the RSE name, whether or not it is a\ntranslation error. If, as we conclude, the amended Act states the\nERS name as a name for the System, a searcher can still rely only\non official records and there is no issue about a searcher having\nto use an \"incorrect\" name.\n More generally, the requirement for an individual with\na driver's license issued in the state is not relevant here, where\nwe consider a registered organization that is created and\ndesignated by statute.\n 20 The Spanish language at issue did not change in the 2013\namendment to the Enabling Act. The language translated as \"to be\ndesignated as the 'Retirement System for Employees,'\" is \"que se\ndenominará 'Sistema de Retiro de Los Empleados.\" Compare Law No.\n3 of April 4, 2013, 2013 P.R. Laws 39 with id. (Spanish). This is\nthe same Spanish language used after the last amendment to the\nEnabling Act in 2004. P.R. Leyes Ann. tit. 3, § 761 (2005). And\nindeed, the portion of the Spanish corresponding to the first part\nof the name of the System -- \"Sistema de Retiro de Los Empleados\"\n-- was the same in the original Enabling Act of 1951, and was\ntranslated there as \"Employees Retirement System.\" Compare Law\nNo. 447 of May 15, 1951, 1951 P.R. Laws 1298 with id. at 1299.\n\n\n - 44 -\n\fname or nickname rather than an official, legal name.21 We do not\n\nagree with the System that one English name (the RSE name) is\n\nofficial and the other (the ERS name) is merely a trade name, which\n\nwould be insufficient.\n\n The System's argument that the \"to be designated\" clause\n\nin Section 1-101 alone must control fails for a number of reasons.\n\nThe numerous clauses using the ERS name are hardly trivial. It is\n\ntrue that \"Retirement System for Employees\" is used three times in\n\nthe translated Act, as codified. Id. §§ 761, 763(1), 779.22 But\n\n\"Employees Retirement System\" is used far more often: by our count,\n\nmore than thirty-five times in the Act as codified. Perhaps most\n\nimportantly, \"Employees Retirement System\" is used in the primary\n\ndefinition of \"[s]ystem.\" Id. § 763(36) (\"System [s]hall mean the\n\nEmployees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico.\"). Other uses of the ERS name include in the\n\nheading of Section 1-101, id. § 761, as well as the headings of\n\n\n 21 We do not need to decide whether a translation error\noccurred in this instance. We do note that in the relevant portion\nof the Spanish version of the Act, the Spanish preposition most\ncommonly translated as \"for\" -- para -- is not used. See\nUniversity of Cambridge, Spanish-English Dictionary,\nhttp://dictionary.cambridge.org/dictionary/spanish-english,\n\"para.\"\n 22 It is not clear that the use in Section 779 refers to\nthe same System, though we assume it does. This provision in\nEnglish describes the \"Retirement System of the Employees of the\nGovernment and its Instrumentalities,\" P.R. Laws Ann. tit 3, §\n779, rather than \"Retirement System for Employees of the Government\nof the Commonwealth of Puerto Rico,\" id. § 761.\n\n\n - 45 -\n\fmany other sections, see id. §§ 761a, 762, 763, 764, 765, 765a,\n\n766, 766a, 766b, 766c, 766d, 768, 768a, 769, 769a, 770, 770a, 771,\n\n772, 773, 774, 775, 776, 777, 778, 779, 779a, 779b, 779c, 781a,\n\n782, 783, 784, 785, 786, 786a, 786b, 787, 788.\n\n The System and the Committee have offered no explanation\n\nas to why, when both terms are used, the ERS name should be\n\ndisregarded. It is difficult to discern why \"Retirement System\n\nfor Employees\" is used instead of \"Employees Retirement System\" in\n\nthe particular places where the RSE name is used. Nothing about\n\nthe context suggests that one or the other should be used, and the\n\nunderlying Spanish is the same.\n\n We think a reasonable creditor would be familiar with\n\nthe Commonwealth law that, in a case of a discrepancy between the\n\nEnglish and Spanish, when the legislation originated in Spanish\n\n\"the Spanish text shall be preferred to the English.\" P.R. Laws\n\nAnn. tit. 31, § 13; see Republic Sec. Corp. v. P.R. Aqueduct &\n\nSewer Auth., 674 F.2d 952, 956 (1st Cir. 1982) (\"[I]n cases of\n\ndiscrepancy 'the Spanish text shall be preferred.'\"). Further, we\n\nsee no evidence that the legislature of the Commonwealth intended\n\nto change the English name of the System to the RSE name and\n\nabandon the ERS name. We would expect to see a clear statement\n\nexpressing a desire to change the translation, and there is no\n\nsuch statement. This expectation is only reinforced by Section\n\n13, described above.\n\n\n - 46 -\n\f The legislature provided a Statement of Motives to the\n\n2013 amendment, which identified, for example, the fiscal crisis\n\nin Puerto Rico, the causes of the crisis, and the need to act\n\npromptly. Law No. 3 of April 4, 2013, 2013 P.R. Laws 39-64. And\n\nthe legislature then explained \"[e]ach one of the amendments,\" id.\n\nat 58, such as the \"[i]ncrease in the employee contribution\n\n[rate],\" id. at 59. There is no explanation in this section that\n\nthe 2013 amendment was meant to change the name of the System.\n\nEarlier name changes, including in 2004, demonstrate generally\n\nthat the legislature understands how to change the System's name\n\nwhen it wants to do so.\n\n It is also significant that the RSE name referenced in\n\nthe \"to be designated\" clause differs from prior longstanding\n\nofficial uses. From 1951 through 2012, translated versions of the\n\nEnabling Act used only \"Employees Retirement System\" in the first\n\nsection. See, e.g., Law No. 447 of May 15, 1951, 1951 P.R. Laws\n\n1298; P.R. Laws Ann. tit. 3, § 761 (1988); id. (2006), id. (2011).\n\nIt is only the translation of the 2013 amendment which breaks this\n\nconsistent pattern. Of course, a long-standing name of an\n\norganization or agency that is named by statute can be changed by\n\nstatute. Here, though, the legislature did change the System's\n\nname several times, including changing the name of the System in\n\n2004 by removing \"and its Instrumentalities\" (\"y sus\n\nInstrumentalidades\") from the end of the System's name and by\n\n\n - 47 -\n\freplacing \"Government of Puerto Rico\" with \"Government of the\n\nCommonwealth of Puerto Rico\" (\"Gobierno del Estado Libre Asociado\n\nde Puerto Rico\"). Law No. 296 of September 15, 2004, § 1-101;\n\nP.R. Laws Ann. tit. 3, § 761 (2006). But, with each of these\n\nchanges, the \"Employees Retirement System\" part of the name\n\nremained the same. Our conclusion that there was no legislative\n\nintent to change the System's name is also bolstered by post-2014\n\nlegislative action. Years after the 2014 translation of the\n\namended Enabling Act, the official translation of the Puerto Rico\n\nFinancial Emergency and Fiscal Responsibility Act of 2017 referred\n\nto the System in part as \"the Employees Retirement System.\" P.R.\n\nLaws Ann. tit. 3, § 9433(r).\n\n Further, the ERS name is the name consistently used by\n\nthe System itself, including in court filings, before and after\n\nthe translation of the amended Act in 2014. There are many\n\nexamples of this; we list only a few. In its complaint in this\n\ncase, the System referred to itself as \"the Employees Retirement\n\nSystem of the Government of the Commonwealth of Puerto Rico\" or\n\n\"ERS.\" The System referred to itself in the same way in its Answer\n\nto Defendant's Counterclaims. The System did not mention\n\n\"Retirement System for Employees\" or \"RSE\" in either document.\n\n Independently, in its Title III Petition form, dated May\n\n21, 2017, the ERS name was used under \"Debtor's name.\" In the box\n\non the Title III form asking for \"[a]ll other names Debtor used in\n\n\n - 48 -\n\fthe last five years [-] Include any assumed names, trade names,\n\nand doing business as names,\" only a Spanish name was listed,\n\n\"Adminstracion de los Sistemas de Retiro de los Empleados del\n\nGobierna y la Judicatura,\" with no mention of \"Retirement System\n\nfor Employees.\" Further, the System made no statement that\n\n\"Employees Retirement System\" was being used as a trade name.\n\nAgain, these are only a few of the many times that the System held\n\nitself out as the \"Employees Retirement System\" around the time of\n\nand after the translation of the amended Enabling Act was in\n\neffect. The district court determined, and the System now argues,\n\nthat the System used the ERS name simply as a trade name after\n\n2014. See In re: Fin. Oversight & Mgmt. Bd. for P.R., 590 B.R. at\n\n592. We disagree.\n\n Finally, there is no doubt that the ERS name was the\n\nofficial and only name of the System for over sixty years. So,\n\nany putative creditors would have had to search under that name to\n\nfind prior liens even if the System's name did change in 2014.\n\nSee P.R. Laws Ann. tit. 19, § 2327(c) (providing that a secured\n\nparty owning a lien on the debtor's property acquired prior to a\n\nname change is not required to file a new financing statement).\n\nThis observation adds further support to the central proposition\n\nthat any putative creditor who read the 2014 translation of the\n\nEnabling Act would conclude that, given the inconsistent use of\n\nboth the ERS and RSE names, it should at the very least search\n\n\n - 49 -\n\funder the long-standing ERS name.\n\n All of these reasons lead us to conclude that \"Employees\n\nRetirement System of the Government of the Commonwealth of Puerto\n\nRico\" remained a valid name for UCC purposes when the Financing\n\nStatement Amendments were filed.23 In our view, a searcher, whether\n\nanother creditor or merely an interested party, would conclude\n\nthat a search under the ERS name was required. Similarly, a\n\nreasonable filer would have concluded that the ERS name was a\n\ncorrect name for the debtor for UCC purposes.\n\n Because the Financing Statement Amendments used\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico,\" they contained an appropriate name of the debtor\n\nunder the Commonwealth's Article 9. See P.R. Laws Ann. tit. 19,\n\n§§ 2322(a), 2323(a)(1), 2404(3)(B). Taken together with the 2008\n\nFinancing Statements, the Financing Statement Amendments met the\n\nrequirements for perfection as of December 17, 2015. See id.\n\n§ 2322(a).\n\n\n\n\n 23 Even were we to accept that \"[t]he majority of cases\ndecided under . . . Article 9 are unforgiving of even minimal\nerrors [for the name of the debtor],\" In re John's Bean Farm of\nHomestead, Inc., 378 B.R. 385, 391 (Bankr. S.D. Fla. 2007), a\nfiling under the ERS name is not such an error. The situation\nhere is clearly unlike, for example, a filer misspelling the name\nof a tractor seller as \"Roger\" rather than \"Rodger.\" See Pankratz\nImplement Co. v. Citizens Nat. Bank, 130 P.3d 57, 59 (Kan. 2006).\n\n\n\n - 50 -\n\fD. Avoidance under PROMESA\n\n Because we determine that the Bondholders satisfied\n\nArticle 9's perfection requirements before the passage of PROMESA\n\non June 30, 2016, we do not consider whether PROMESA would allow\n\nretroactive avoidance of unperfected liens.24 The debtors do not\n\nargue that the strong-arm provision of the Bankruptcy Code,\n\nincorporated by reference in PROMESA, would allow them to avoid\n\nthe Bondholders' interest if the interest is perfected.\n\n And as a \"basic tenet of the law of secured\n\ntransactions,\" a \"perfected security interest prevails over a\n\nsubsequent lien creditor.\" Ledford v. Easy Living Furniture, 52\n\nB.R. 706, 710 (Bankr. S.D. Ohio 1985); accord Gen. Elec. Credit\n\nCorp. v. Nardulli & Sons, Inc., 836 F.2d 184, 189 (3d Cir. 1988)\n\n(holding that because the parties filed correctly and perfected\n\ntheir security interest, \"their rights as lienholders are superior\n\nto those of the trustee as a hypothetical lienholder under 11\n\nU.S.C. § 544\"). Commonwealth law recognizes this rule of priority\n\nby implication, in stating that a judicial creditor's lien is\n\n\n\n 24Similarly, we need not consider the System's argument\nthat the Bondholders' security interest was always inferior to\nsubsequent perfected security interests and judicial liens under\nthe UCC, see P.R. Laws Ann. tit. 19, §§ 2219(a)(1), 2212(52),\n2267(a)(2)(A), because this argument is necessarily premised on\nthe Bondholders having only an unperfected security interest. The\nSystem does not argue that the UCC would grant priority over a\npreviously perfected lien, and the statutory text is clear on this\nissue. Id. § 2267(a)(2)(A).\n\n\n\n - 51 -\n\fsuperior to a prior unperfected security interest. See P.R. Laws\n\nAnn. tit. 19, § 2267(a)(2)(A). \"Where a creditor has an\n\nunperfected lien on a debtor's property, the Bankruptcy Code\n\nempowers a trustee to avoid and preserve the lien for the benefit\n\nof the estate.\" DiGiacomo v. Traverse (In re Traverse), 753 F.3d\n\n19, 26 (1st Cir. 2014) (emphasis added).\n\nE. The Bondholders' Counterclaims\n\n The Bondholders also appeal the dismissal of their\n\nsecond and third counterclaims, both requests for declaratory\n\njudgment. Counterclaim Two sought a declaration stating that the\n\n\"Bondholders hold valid, enforceable, attached, perfected, first\n\npriority liens on and security interest in the Pledged Property\n\nwhether ERS became entitled to collect such property before or\n\nafter the commencement of ERS's Title III case.\" Counterclaim\n\nThree sought a declaration stating that \"because the employer\n\ncontributions constitute 'special revenues,' [Bondholders']\n\nsecurity interests in and liens on employer contributions received\n\nby the [System] after the Petition Date remain enforceable pursuant\n\nto 11 U.S.C. § 928(a).\" The Bondholders argue that the district\n\ncourt did not adequately address arguments for these\n\ncounterclaims.\n\n As to Counterclaim Two, the Bondholders acknowledged in\n\nthe district court that the \"[11 U.S.C.] section 552 issues need\n\nnot be reached in light of the Summary Judgment Decision,\" and did\n\n\n - 52 -\n\fnot provide \"any reason that the remaining aspects of Count Two\n\nshould be resolved differently from the Claims resolved by the\n\nSummary Judgment Decision.\" As to Counterclaim Three, the\n\nBondholders stipulated that \"in light of the Summary Judgement\n\ndecision [the Bondholders] are unable to identify any need for the\n\n[district court] to reach the alternative arguments.\"\n\n Because we find the 2008 Financing Statements effective\n\nas amended, we remand to the district court for further\n\nconsideration of the dismissals of these counterclaims in light of\n\nthis opinion.\n\nF. Violation of the January 2017 Stipulation\n\n Finally, the Bondholders argue that ERS violated the\n\nJanuary 2017 Stipulation between the parties, and the district\n\ncourt erred in determining that no violation occurred (or that it\n\nwas beyond the scope of the proceeding). Specifically, they assert\n\nthat the System violated that Stipulation because it requires that,\n\n\"[t]o the extent that ERS receives any Commonwealth central\n\ngovernment Employers' contributions, unless otherwise agreed in\n\nwriting by the undersigned parties, such contributions shall be\n\nretained in the Segregated Account pending further order of the\n\nCourt.\" The System points out that a Joint Stipulation between\n\nthe parties in this case limited claims or counterclaims on\n\nemployer contributions only to those received during May 2017.\n\n Even assuming the Bondholders have not waived this\n\n\n - 53 -\n\fargument,25 it fails. The Joint Stipulation shows that the parties\n\nagreed that the scope of the adversary proceedings at the district\n\ncourt would include \"ERS's rights with respect to employer\n\ncontributions received during the month of May 2017,\" and beyond\n\nsome other stipulated claims and counterclaims, \"no other claims\n\nmay be made by either side\" (emphasis added). So only the\n\ncontributions during the month of May 2017 are properly at issue\n\nhere. But as the district court correctly noted, In re: Fin.\n\nOversight & Mgmt. Bd. for P.R., 590 B.R. at 599, the Bondholders\n\nconceded in their Answer and Counterclaims below that \"ERS was\n\nobligated to place Employers' Contributions into the Segregated\n\nAccount only for the duration of the [PROMESA] Section 405 Stay,\"\n\nand the Section 405 stay expired as of May 1, 2017. The Bondholders\n\nhave not explained how their argument concerning the alleged\n\nviolation of the January 2017 Stipulation survives these\n\nadmissions, taking into account the stipulated scope of the\n\nadversary proceedings. The district court correctly dismissed the\n\nBondholders' claim regarding an alleged violation of the January\n\n2017 Stipulation.\n\n\n\n 25Neither opening brief from the Bondholders makes a full\nargument concerning the alleged violation of the January 2017\nStipulation. See United States v. Zannino, 895 F.2d 1, 17 (1st\nCir. 1990) (\"It is not enough merely to mention a possible argument\nin the most skeletal way, leaving the court to do counsel's work,\ncreate the ossature for the argument, and put flesh on its\nbones.\").\n\n\n - 54 -\n\f III.\n\n We affirm the district court's holding that the 2008\n\nFinancing Statements did not perfect the Bondholders' security\n\ninterest in the \"Pledged Property.\" We determine that the\n\nBondholders met the requirements for perfection beginning on\n\nDecember 17, 2015, and so reverse the district court. PROMESA's\n\nincorporation of the Bankruptcy code does not allow for the\n\navoidance of perfected liens, and so we vacate the district court's\n\nholding that the Bondholders' security interest can be avoided\n\nunder PROMESA. Concerning the district court's dismissal of the\n\nBondholders' second and third counterclaims with prejudice, we\n\nvacate and remand to the district court for further consideration\n\nin light of this opinion. We affirm the district court's dismissal\n\nof the Bondholders' claim regarding the January 2017 Stipulation.\n\nNo costs are awarded.\n\n\n\n\n - 55 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363261/", "author_raw": "LYNCH, Circuit Judge"}]}
LYNCH
STAHL
KAYATTA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586008/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: PR AAA Portfolio Bond Fund v. Employees Retirement System\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\nNos. 18-1836\n 18-1837\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE OPPORTUNITIES FUND IX\n (PARALLEL 2), L.P.; OAKTREE VALUE OPPORTUNITIES FUND, L.P.;\n OCHER ROSE, L.L.C.; SV CREDIT, L.P.,\n\n Movants, Appellants,\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n\f U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Movants, Appellees.\n\n\nNo. 18-1841\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n\f INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Movants, Appellants.\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\n L.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Movants, Appellees.\n\n\nNo. 18-1855\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n\f SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Plaintiff, Appellee,\n\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Interested Party, Appellee,\n\n v.\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\nGLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.,\n\n Defendants, Appellants,\n\n PUERTO RICO AAA PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA PORTFOLIO TARGET\n MATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND II, INC.;\nPUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO FIXED INCOME\n FUND V, INC.; PUERTO RICO FIXED INCOME FUND III, INC.; PUERTO\n RICO FIXED INCOME FUND, INC.; PUERTO RICO GNMA AND U.S.\n GOVERNMENT TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS\nBOND FUND I, INC.; PUERTO RICO INVESTORS TAX-FREE FUND II, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND III, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND IV, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND V, INC.; PUERTO RICO INVESTORS TAX-FREE FUND VI, INC.;\nPUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO MORTGAGE-\n BACKED & U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO\n RICO FUND II, INC.; TAX-FREE PUERTO RICO FUND, INC.; TAX-FREE\n PUERTO RICO TARGET MATURITY FUND, INC.; UBS IRA SELECT GROWTH &\n INCOME PUERTO RICO FUND,\n\f Defendants.\n\n\nNo. 18-1858\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Plaintiff, Appellee,\n\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO,\n\n Interested Party, Appellee,\n\n v.\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n INVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n\f U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\n FUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Defendants, Appellants,\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\n GLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\n L.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Defendants.\n\n\nNo. 18-1868\n\n IN RE: THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO\nRICO, AS REPRESENTATIVE FOR THE COMMONWEALTH OF PUERTO RICO; THE\n FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE PUERTO RICO HIGHWAYS AND TRANSPORTATION\n AUTHORITY; THE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR\n PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO ELECTRIC\n POWER AUTHORITY (PREPA); THE FINANCIAL OVERSIGHT AND MANAGEMENT\n BOARD FOR PUERTO RICO, AS REPRESENTATIVE FOR THE PUERTO RICO\n SALES TAX FINANCING CORPORATION, a/k/a Cofina; THE FINANCIAL\n OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtors.\n\n\n PUERTO RICO AAA PORTFOLIO BOND FUND, INC.; PUERTO RICO AAA\n PORTFOLIO BOND FUND II, INC.; PUERTO RICO AAA PORTFOLIO TARGET\nMATURITY FUND, INC.; PUERTO RICO FIXED INCOME FUND, INC.; PUERTO\n RICO FIXED INCOME FUND II, INC.; PUERTO RICO FIXED INCOME FUND\n III, INC.; PUERTO RICO FIXED INCOME FUND IV, INC.; PUERTO RICO\n FIXED INCOME FUND V, INC.; PUERTO RICO GNMA AND U.S. GOVERNMENT\n TARGET MATURITY FUND, INC.; PUERTO RICO INVESTORS BOND FUND I,\n INC.; PUERTO RICO INVESTORS TAX-FREE FUND, INC.; PUERTO RICO\nINVESTORS TAX-FREE FUND II, INC.; PUERTO RICO INVESTORS TAX-FREE\n FUND III, INC.; PUERTO RICO INVESTORS TAX-FREE FUND IV, INC.;\n PUERTO RICO INVESTORS TAX-FREE FUND V, INC.; PUERTO RICO\n\fINVESTORS TAX-FREE FUND VI, INC.; PUERTO RICO MORTGAGE-BACKED &\n U.S. GOVERNMENT SECURITIES FUND, INC.; TAX-FREE PUERTO RICO\nFUND, INC.; TAX-FREE PUERTO RICO FUND II, INC.; TAX-FREE PUERTO\n RICO TARGET MATURITY FUND, INC.,\n\n Movants, Appellants,\n\n ALTAIR GLOBAL CREDIT OPPORTUNITIES FUND (A), LLC; ANDALUSIAN\nGLOBAL DESIGNATED ACTIVITY COMPANY; GLENDON OPPORTUNITIES FUND,\n LP; MASON CAPITAL MASTER FUND LP; NOKOTA CAPITAL MASTER FUND,\nL.P.; OAKTREE OPPORTUNITIES FUND IX (PARALLEL 2), L.P.; OAKTREE\n OPPORTUNITIES FUND IX, L.P.; OAKTREE VALUE OPPORTUNITIES FUND,\n L.P.; OAKTREE-FORREST MULTI-STRATEGY, L.L.C. (SERIES B); OCHER\n ROSE, L.L.C.; SV CREDIT, L.P.; UBS IRA SELECT GROWTH & INCOME\n PUERTO RICO FUND,\n\n Movants,\n\n v.\n\nTHE FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, AS\n REPRESENTATIVE FOR THE EMPLOYEES RETIREMENT SYSTEM OF THE\n GOVERNMENT OF THE COMMONWEALTH OF PUERTO RICO,\n\n Debtor, Appellee,\n\n AMERICAN FEDERATION OF STATE COUNTY AND MUNICIPAL EMPLOYEES;\n OFFICIAL COMMITTEE OF RETIRED EMPLOYEES OF THE COMMONWEALTH OF\n PUERTO RICO; OFFICIAL COMMITTEE OF UNSECURED CREDITORS,\n\n Movants, Appellees.\n\n\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF PUERTO RICO\n\n [Hon. Laura Taylor Swain,* U.S. District Judge]\n\n\n\n\n * Of the Southern District of New York, sitting by\ndesignation.\n\f Before\n\n Lynch, Stahl, and Kayatta,\n Circuit Judges.\n\n\n Bruce Bennett, with whom Benjamin Rosenblum, James M. Gross,\nGeoffrey S. Stewart, Sparkle L. Sooknanan, Parker A. Rider-\nLongmaid, Jones Day, Alfredo Fernández-Martínez, and Delgado &\nFernández, LLC were on brief, for Altair Global Credit\nOpportunities Fund (A), LLC; Andalusian Global Designated Activity\nCompany; Glendon Opportunities Fund, LP; Mason Capital Master Fund\nLP; Nokota Capital Master Fund, L.P.; Oaktree-Forrest Multi-\nStrategy, L.L.C. (Series B); Oaktree Opportunities Fund IX, L.P.;\nOaktree Opportunities Fund IX, (Parallel 2), L.P.; Oaktree Value\nOpportunities Fund, L.P.; Ocher Rose, L.L.C; SV Credit, L.P.\n Jason N. Zakia, with whom Glenn M. Kurtz, John K. Cunningham,\nWhite & Case LLP, José C. Sánchez-Castro, Alicia I. Lavergne-\nRamírez, Maraliz Vázquez-Marrero, and Sanchez Pirillo LLC were on\nbrief, for Puerto Rico AAA Portfolio Bond Fund, Inc.; Puerto Rico\nAAA Portfolio Bond Fund II, Inc.; Puerto Rico AAA Portfolio Target\nMaturity Fund, Inc.; Puerto Rico Fixed Income Fund, Inc.; Puerto\nRico Fixed Income Fund II, Inc.; Puerto Rico Fixed Income Fund\nIII, Inc.; Puerto Rico Fixed Income Fund IV, Inc.; Puerto Rico\nFixed Income Fund V, Inc.; Puerto Rico GNMA and U.S. Government\nTarget Maturity Fund, Inc.; Puerto Rico Investors Bond Fund I,\nInc.; Puerto Rico Investors Tax-Free Fund, Inc.; Puerto Rico\nInvestors Tax-Free Fund II, Inc.; Puerto Rico Investors Tax-Free\nFund III, Inc.; Puerto Rico Investors Tax-Free Fund IV, Inc.;\nPuerto Rico Investors Tax-Free Fund V, Inc.; Puerto Rico Investors\nTax-Free Fund VI, Inc.; Puerto Rico Mortgage-Backed & U.S.\nGovernment Securities Fund, Inc.; Tax-Free Puerto Rico Fund, Inc.;\nTax-Free Puerto Rico Fund II, Inc.; Tax-Free Puerto Rico Target\nMaturity Fund, Inc.; UBS IRA Select Growth & Income Puerto Rico\nFund.\n Jeffrey W. Levitan, with whom Timothy W. Mungovan, John E.\nRoberts, Michael R. Hackett, William D. Dalsen, Martin J.\nBienenstock, Mark D. Harris, Kevin J. Perra, and Proskauer Rose\nLLP were on brief, for the Financial Oversight and Management Board\nfor Puerto Rico, as Representative for the Employees Retirement\nSystem of the Government of the Commonwealth of Puerto Rico.\n Richard B. Levin, with whom Catherine Steege, Melissa Root,\nIan Heath Gershengorn, Lindsay C. Harrison, William K. Dreher,\nRobert Gordon, Richard Levin, Jenner & Block LLP, A.J. Bennazar-\nZequeira, and Bennazar, García, & Milián, C.S.P. were on brief,\nfor the Official Committee of Retired Employees of the Commonwealth\nof Puerto Rico.\n\f Michael Shih, Appellate Division, Civil Staff, Joseph H.\nHunt, Assistant Attorney General, Mark R. Freeman, and Michael S.\nRaab, Appellate Division, Civil Staff, for the United States,\namicus curiae.\n\n\n\n January 30, 2019\n\f LYNCH, Circuit Judge. These appeals involve bonds\n\nissued in 2008 by the Employees Retirement System of the Government\n\nof the Commonwealth of Puerto Rico1 (the \"System\"), which were\n\nbought by bondholders (the \"Bondholders\"), the appellants here.\n\nThe bond documentation offered as security certain property\n\nbelonging or owed to the System, as defined in a \"Pension Funding\n\nBond Resolution.\" The Bondholders claim that they have a perfected\n\nsecurity interest in that property under Puerto Rico's version of\n\nthe Uniform Commercial Code (\"UCC\").\n\n Through the Financial Oversight and Management Board for\n\nPuerto Rico (the \"Oversight Board\"), the System filed suit in the\n\ndistrict court on July 21, 2017, seeking declaratory judgments on\n\nseveral issues related to the validity, breadth, and perfection of\n\nthe Bondholders' asserted security interest, and regarding the\n\nSystem's compliance with a stipulation between the parties (the\n\n\"January 2017 Stipulation\"). The Bondholders brought nine\n\ncounterclaims concerning their asserted security interest as well\n\nas an alleged violation of the January 2017 Stipulation. After\n\n\n\n 1 We use this name here rather than \"Retirement System for\nEmployees of the Government of the Commonwealth of Puerto Rico,\"\nbecause the System, through the Financial Oversight and Management\nBoard for Puerto Rico, filed its complaint in the district court\nunder this name and refers to itself by this name in its brief to\nthis court. In this opinion, the \"ERS name\" refers to the term\nbeginning with \"Employees Retirement System\"; the \"RSE name\"\nrefers to the term beginning with \"Retirement System for\nEmployees.\"\n\n\n - 10 -\n\fboth sides moved for summary judgment, the district court ruled in\n\nfavor of the System, finding that the Bondholders' interest was\n\nnot perfected and so could be avoided under 48 U.S.C. § 2161(a),\n\nthat there had been no violation of the January 2017 Stipulation,\n\nand that two of the Bondholders' counterclaims should be dismissed\n\nwith prejudice. The Fin. Oversight and Mgmt. Bd. for P.R. v.\n\nAltair Glob. Credit Opportunities Fund (a), LLC (In re: The Fin.\n\nOversight and Mgmt. Bd. for P.R.), 590 B.R. 577 (D.P.R. 2018). We\n\nare told the dollar value of the security for the bonds at stake\n\nis about $2.9 billion. The Bondholders appealed.\n\n We agree with the district court on the particular facts\n\nhere that the UCC financing statements filed in 2008 (the \"2008\n\nFinancing Statements\") did not perfect the Bondholders' security\n\ninterest, as they lacked a sufficient description of collateral.\n\nBut we find that the financing statement amendments filed in 2015\n\nand 2016 (together, the \"Financing Statement Amendments\")\n\nsatisfied the filing requirements for perfection when read in\n\nconjunction with the 2008 Financing Statements. We reverse the\n\ndistrict court's determination on the satisfaction of filing\n\nrequirements for perfection by amendment, and hold that the\n\nBondholders satisfied the filing requirements for perfection as of\n\nDecember 17, 2015.\n\n Because the Bondholders' security interest was\n\nperfected, this interest cannot be avoided under the Puerto Rico\n\n\n - 11 -\n\fOversight, Management, and Economic Stability Act's (\"PROMESA\")\n\nincorporation of parts of the Bankruptcy Code, including 11 U.S.C.\n\n§ 544(a), and so we do not reach the issue of whether PROMESA and\n\nother relevant Commonwealth law would allow for the retroactive\n\navoidance of unperfected liens.2 Accordingly, we vacate the\n\ndistrict court's holding on avoidance of the Bondholders' security\n\ninterest. We vacate the dismissal of two of the Bondholders'\n\ncounterclaims and remand to the district court for further\n\nproceedings in light of this opinion. Finally, we affirm the\n\ndismissal of the Bondholders' claim regarding the January 2017\n\nStipulation.\n\n As to the first issue, concerning the 2008 Financing\n\nStatements alone, we decide narrowly on the particular facts\n\npresented. As to the issue of perfection by amendment, also\n\nnarrowly decided, this case presents a unique confluence of\n\ncircumstances involving two languages and a translation,\n\nparticularly regarding the sufficient name of the System under\n\nArticle 9 of the UCC (Secured Transactions), as adopted by the\n\nCommonwealth. Puerto Rico recognizes two official statutory\n\nlanguages. P.R. Laws Ann. tit. 1, § 59. We face a statutory\n\namendment from 2013 (officially translated in 2014) that variously\n\n\n 2 Although we do not reach this issue, we acknowledge with\nappreciation the assistance provided by the United States\nDepartment of Justice in submitting a brief as amicus curiae in\nsupport of the appellees.\n\n\n - 12 -\n\fuses two English terms when translating the same unvaried Spanish\n\nterm for the name of the System. Id. tit. 3, §§ 761, 763. Further,\n\npast official translations, and the System itself, have\n\nconsistently used the ERS name (including in many court filings)\n\nfor over sixty years. We craft our holding narrowly to accommodate\n\nthe very unusual circumstances presented by a new translation that\n\nis, on its face, inconsistent, that varies from every other formal\n\nversion both before and after its presentation, and that arises in\n\na context in which there is no realistic likelihood that anyone\n\nwould search the Department of State of the Government of Puerto\n\nRico's (the \"P.R. Department of State\") records only under one of\n\nthe two forms of the name that appear in the English translation\n\nof the amended statute.\n\n I.\n\n The System is a trust and government agency created in\n\n1951 by an Act of the Commonwealth. Law No. 447 of May 15, 1951,\n\n1951 P.R. Laws 1298 (the \"1951 Enabling Act\") (codified as amended\n\nat P.R. Laws Ann. tit. 3, §§ 761 et seq.). The System is structured\n\nto provide pensions and other retirement benefits to employees and\n\nofficers of the Commonwealth government, members and employees of\n\nthe Commonwealth's Legislative Assembly, and officers and\n\nemployees of the Commonwealth's municipalities and public\n\ncorporations. P.R. Laws Ann. tit 3, § 764. It is designated as\n\n\"independent and separate\" from other Commonwealth agencies. Id.\n\n\n - 13 -\n\f§ 775. Until legislation that went into effect on July 1, 2017,\n\nthe System was funded by mandatory contributions from employees\n\nand employers, and by the System's investment earnings. See\n\nConcurrent Resolution 188 of the House of Representatives of the\n\nGovernment of Puerto Rico; Law No. 106 of August 23, 2017.\n\n As of 2008, the Enabling Act allowed the System to incur\n\ndebt when the Board of Trustees of the System so authorized. P.R.\n\nLaws Ann. tit. 3, § 779(d) (2008). Seeking to decrease an unfunded\n\nliability of approximately $9.9 billion, the Board of Trustees\n\nadopted a \"Pension Funding Bond Resolution\" (the \"Resolution\") on\n\nJanuary 24, 2008. The Resolution allowed for the issuance of about\n\n$2.9 billion in bonds. The Resolution was made publicly available\n\non several governmental websites, including on the Government\n\nDevelopment Bank for Puerto Rico's website and on the System's own\n\nwebsite.\n\n The Bondholders hold some of those bonds issued by the\n\nSystem. The System executed a security agreement (the \"Security\n\nAgreement\"), which purports to grant the Bondholders a security\n\ninterest in \"Pledged Property\" belonging or owed to the System.\n\n\"Pledged Property\" was defined in the Resolution but not in the\n\nSecurity Agreement. The Resolution's definition included the\n\nrequired employer contributions to the System and proceeds from\n\n\n\n\n - 14 -\n\fthese contributions.3 The Security Agreement did not itself define\n\nor otherwise describe \"Pledged Property.\" Rather, it stated that\n\n\"[a]ll capitalized words not defined herein shall have the meaning\n\nascribed to them in the Resolution.\" But the Resolution was not\n\nattached to the Security Agreement, and the Security Agreement did\n\nnot even say what types of property were pledged, whether the\n\nResolution was available to the public, or where the Resolution\n\n\n 3 The Resolution defined \"Pledged Property\" as:\n\n 1. All Revenues.\n 2. All right, title and interest of the\n System in and to Revenues, and all rights to\n receive the same.\n 3. The Funds, Accounts, and Subaccounts held\n by the Fiscal Agent, and moneys and securities\n and, in the case of the Debt Service Reserve\n Account, Reserve Account Cash Equivalents,\n from time to time held by the Fiscal Agent\n under the terms of this Resolution, subject to\n the application thereof as provided in this\n Resolution and to the provisions of Sections\n 1301 and 1303.\n 4. Any and all other rights and personal\n property of every kind and nature from time to\n time hereafter pledged and assigned by the\n System to the Fiscal Agent as and for\n additional security for the Bonds and Parity\n Obligations.\n 5. Any and all cash and non-cash proceeds,\n products, offspring, rents and profits from\n any of the Pledged Property mentioned\n described in paragraphs (1) through (4) above,\n including, without limitation, those from the\n sale, exchange, transfer, collection, loss,\n damage, disposition, substitution or\n replacement of any of the foregoing.\n\nThe Resolution's definition of \"Revenues\" included, among other\nthings, \"All Employers' Contributions.\"\n\n - 15 -\n\fcould be found.\n\n Security interests could be perfected by filing\n\nfinancing statements comporting with the requirements of Article\n\n9 of the UCC, as adopted by the Commonwealth. In 2008, those\n\nrequirements included, among other things, that a financing\n\nstatement \"contain[] a statement indicating the types, or\n\ndescribing the items, of collateral.\" P.R. Laws Ann. tit. 19,\n\n§ 2152(1) (2008).\n\n The Security Agreement specified that \"[the System]\n\nshall cause UCC financing and continuation statements to be filed,\n\nas appropriate, and the Secured Party shall not be responsible for\n\nany UCC filings.\" On or about June 24, 2008, and July 2, 2008,4\n\ntwo financing statements (the 2008 Financing Statements) related\n\nto the System's bonds, as described above, were filed with the\n\nP.R. Department of State. The 2008 Financing Statements each used\n\na standard \"Financing Statement\" form provided by the P.R.\n\nDepartment of State, where such statements are located. Initial\n\nfinancing statements are sometimes referred to as \"UCC-1\"\n\nstatements.\n\n The 2008 Financing Statements described the collateral\n\nas \"[t]he pledged property described in the Security Agreement\n\n\n\n 4 The listed dates -- June 24 and July 2 -- are the dates\nstamped on the documents by the filing officer. The same is true\nfor the listed dates for the Financing Statement Amendments.\n\n\n - 16 -\n\fattached as Exhibit A hereto and by reference made a part thereof.\"\n\nThe Security Agreement, Exhibit A, was attached to each of the\n\n2008 Financing Statements as filed but, as said, did not itself\n\ndescribe the \"Pledged Property\" except as it purported to do by\n\nreference to an unattached other document. That is, the\n\nResolution, which contained the full definition of \"Pledged\n\nProperty\" and other key terms, was not attached. The 2008\n\nFinancing Statements do not otherwise describe or define the\n\n\"Pledged Property\" (meaning the collateral). In short, the\n\ndocuments filed with the P.R. Department of State described the\n\ncollateral only by stating that it was \"Pledged Property\" described\n\nin a document that could only be found somewhere outside the P.R.\n\nDepartment of State.\n\n Between the filing of the 2008 Financing Statements and\n\nthe filing of the Financing Statement Amendments in 2015 and 2016,\n\nthe Commonwealth repealed its earlier version of Article 9 of the\n\nUCC and enacted a revised version, Law No. 21 of January 17, 2012,\n\n2012 P.R. Laws 162 (codified at P.R Laws Ann. tit. 19, §§ 2211-\n\n2409). The updated law went into effect on January 17, 2013, one\n\nyear after its approval. See P.R. Laws Ann. tit. 19, § 2211).\n\nThe new version of Article 9 made modest changes to the\n\nrequirements for financing statements, and made the effective life\n\nof financing statements five years rather than ten years.\n\n On or about December 17, 2015, and January 16, 2016, the\n\n\n - 17 -\n\ffour Financing Statement Amendments were filed. These filings all\n\nused a standard \"Financing Statement Amendment\" form provided by\n\nthe P.R. Department of State. The Financing Statement Amendments\n\ndescribe the collateral as \"[t]he Pledged Property and all proceeds\n\nthereof and all after-acquired property as described more fully in\n\nExhibit A attached hereto and incorporated by reference.\" Unlike\n\nthe 2008 Financing Statements, Exhibit A contained a full\n\ndefinition of \"Pledged Property\" drawn from the Resolution. The\n\nFinancing Statement Amendments provide, in the attached Exhibit A,\n\nthat the debtor is the \"Employees Retirement System of the\n\nGovernment of the Commonwealth of Puerto Rico.\" That naming of\n\nthe debtor is at issue in the argument concerning whether the\n\nFinancing Statement Amendments sufficed to satisfy the filing\n\nrequirements for perfection.5\n\n The P.R. Department of State certified in March 2017\n\nthat a search of the Commonwealth's UCC records under the name\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico\" revealed the 2008 Financing Statements and the\n\nFinancing Statement Amendments. A copy of a UCC search report\n\nfrom October 17, 2017, for a search performed by Wolters Kluwer on\n\nbehalf of the Bondholders, indicates the same. None of the 2008\n\n\n\n 5 The issue of the proper name of the System did not arise\nuntil February 28, 2014, when a translation of the 2013 amended\nEnabling Act was published.\n\n\n - 18 -\n\fFinancing Statements and the Financing Statement Amendments had\n\nbeen removed from the P.R. Department of State's records as of\n\nOctober 2017.\n\n After the filing of the 2008 Financing Statements and\n\nbefore the filing of the Financing Statement Amendments, the\n\nCommonwealth's legislature amended the Enabling Act in 2013. Law\n\nNo. 3 of April 4, 2013, 2013 P.R. Laws 39 (codified at P.R. Laws\n\nAnn. tit 3, § 761 et seq.). From the original Enabling Act in\n\n1951 until 2014, the English translation of the Enabling Act, as\n\ncodified, used \"Employees Retirement System\" as the first part of\n\nthe name of the System, when translating the Spanish term \"Sistema\n\nde Retiro de los Empleados.\" Compare Law No. 447 of May 15, 1951,\n\n1951 P.R. Laws 1298 (English, \"Employees Retirement System\") with\n\nid. at 1299 (Spanish, \"Sistema de Retiro de Los Empleados\"). The\n\nlegislature had amended the Enabling Act numerous times before\n\n2013, including changing the name of the System in 2004 by removing\n\n\"and its Instrumentalities\" and by replacing \"Government of Puerto\n\nRico\" with \"Government of the Commonwealth of Puerto Rico.\" See\n\nP.R. Laws Ann. tit. 3, § 761 (2006). But the English translation\n\nof the System as, in part, \"Employees Retirement System,\" remained\n\nthe same. See P.R. Laws Ann. tit. 3, § 761 (2011); P.R. Laws Ann.\n\ntit. 3, § 761 (2006); P.R. Laws Ann. tit. 3, § 761 (1988).\n\n The English language translation of the 2013 amended\n\nEnabling Act was published on February 28, 2014, more than ten\n\n\n - 19 -\n\fmonths after the 2013 Act's April 4, 2013, approval in Spanish and\n\nabout seven months after its effective date.6 As codified, the\n\ntranslation refers to the System as both \"Retirement System for\n\nEmployees of the Government of the Commonwealth of Puerto Rico\"\n\nand \"Employees Retirement System of the Government of the\n\nCommonwealth of Puerto Rico.\" P.R. Laws Ann. tit. 3, §§ 761,\n\n763(36). In many sections, the translation of the Enabling Act\n\ncontinues to use the prior version of the English name (\"Employees\n\nRetirement System of the Government of the Commonwealth of Puerto\n\nRico\"). Such continuity in the translation carries over to the\n\n\"Statement of Motives\" section and to the definition of the\n\nshorthand \"System,\" as well as to dozens of other sections. In\n\nSection 1-10, which describes how the System was \"to be\n\ndesignated,\" the translation uses the English formulation,\n\n\"Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico\" for the unchanged Spanish original,\n\n\"Sistema de Retiro de los Empleados del Gobierno del Estado Libre\n\nAsociado de Puerto Rico.\" Law No. 3 of April 4, 2013, 2013 P.R.\n\nLaws 64.\n\n Months after the Financing Statement Amendments were\n\n\n 6 Similar or lengthier gaps between the passage of laws\nand the promulgation of their official translations have occurred\nin the Commonwealth. For example, the official English translation\nof the 2004 amendment to the Enabling Act (passed on September 15,\n2004), Law No. 296 of September 15, 2004, was certified and\npublished on March 13, 2007.\n\n\n - 20 -\n\ffiled in late 2015 and early 2016, Congress enacted PROMESA, 48\n\nU.S.C. § 2101 et seq., on June 30, 2016. Among other things,\n\nPROMESA created the Oversight Board and granted the Board a range\n\nof powers over the Commonwealth's finances, see, e.g., id. §§ 2121-\n\n2129, including the general mandate to craft \"a method [for the\n\nCommonwealth] to achieve fiscal responsibility and access to the\n\ncapital markets,\" id. § 2121(a).\n\n PROMESA incorporated by reference certain provisions of\n\nthe Bankruptcy Code, id. § 2161(a), including the \"strong-arm\"\n\nprovision at 11 U.S.C. § 544(a).7 That provision \"set[s] out the\n\n\n 7 Section 544(a) provides:\n\n The trustee shall have, as of the commencement\n of the case, and without regard to any\n knowledge of the trustee or of any creditor,\n the rights and powers of, or may avoid any\n transfer of property of the debtor or any\n obligation incurred by the debtor that is\n voidable by —\n (1) a creditor that extends credit to\n the debtor at the time of the\n commencement of the case, and that\n obtains, at such time and with respect to\n such credit, a judicial lien on all\n property on which a creditor on a simple\n contract could have obtained such a\n judicial lien, whether or not such a\n creditor exists;\n (2) a creditor that extends credit to\n the debtor at the time of the\n commencement of the case, and obtains, at\n such time and with respect to such\n credit, an execution against the debtor\n that is returned unsatisfied at such\n time, whether or not such a creditor\n exists; or\n\n - 21 -\n\fcircumstances under which a trustee\" may permissibly \"pursue\n\navoidance\" of certain interests. Merit Mgmt. Grp., LP v. FTI\n\nConsulting, Inc., 138 S. Ct. 883, 888 (2018).\n\n Pursuant to Section 301(c)(7) of PROMESA, the Oversight\n\nBoard is the \"trustee\" as that term is defined in the Bankruptcy\n\nCode (except under one circumstance that is not relevant here, see\n\n11 U.S.C § 926). 48 U.S.C. § 2161(c)(7). PROMESA also provides\n\nthat \"Subchapters III and VI shall apply with respect to debts,\n\nclaims, and liens . . . created before, on, or after [June 30,\n\n2016].\" Id. § 2101(b)(2).\n\n PROMESA's enactment triggered an automatic temporary\n\nstay, under Section 405, on creditors' remedies against the\n\nCommonwealth and its property. Id. § 2194(a)-(b). The Bondholders\n\nmoved to lift that stay, but that motion was denied by the district\n\ncourt. See Peaje Invs. LLC v. García-Padilla, 845 F.3d 505, 510\n\n(1st Cir. 2017). This court vacated the district court's decision\n\nin part and remanded for further proceedings, id. at 516, and\n\n\n\n\n (3) a bona fide purchaser of real\n property, other than fixtures, from the\n debtor, against whom applicable law\n permits such transfer to be perfected,\n that obtains the status of a bona fide\n purchaser and has perfected such transfer\n at the time of the commencement of the\n case, whether or not such a purchaser\n exists.\n\n 11 U.S.C. § 544(a).\n\n\n - 22 -\n\fexpressed general concerns with the protection afforded for the\n\nBondholders' property, id. at 511-12.\n\n On remand, the System and the Bondholders entered into\n\nthe January 2017 Stipulation, in order to resolve Altair Global\n\nCredit Opportunities Fund (A), LLC v. García-Padilla, No. 16-cv-\n\n2696. The January 2017 Stipulation required, in relevant part,\n\nthat \"Employers' Contributions (as defined in the ERS Bond\n\nResolutions) received by the ERS during the pendency of the stay\n\nimposed pursuant to [PROMESA] § 405 shall be transferred by the\n\nERS to [a segregated account] for the benefit of the holders of\n\nthe ERS bonds.\"\n\n On May 3, 2017, the Oversight Board filed a petition\n\nunder Title III of PROMESA on behalf of the Commonwealth. On May\n\n21, 2017, the Oversight Board filed a Title III petition on behalf\n\nof the System, which triggered an automatic stay of litigation\n\nagainst the System. The Bondholders moved to lift the stay, and\n\nthe parties entered into a Joint Stipulation that resolved the\n\nBondholders' motion. The Joint Stipulation stated that an\n\nadversary proceeding would be filed by the System on or before\n\nJuly 21, 2017, and limited the scope of the proceeding to the\n\n\"validity, priority, extent and enforceability\" of the\n\nBondholders' claimed security interest and the System's rights\n\nregarding employer contributions received during May 2017, as well\n\nas relevant counterclaims by the Bondholders.\n\n\n - 23 -\n\f On July 21, 2017, the System, through the Oversight\n\nBoard, brought this case in federal district court against the\n\nBondholders, seeking declarations about the status, scope, and\n\nvalidity of the Bondholders' claimed security interest in the\n\n\"Pledged Property,\" and about the System's compliance with the\n\nJanuary 2017 Stipulation. See In re: Fin. Oversight & Mgmt. Bd.\n\nfor P.R., 590 B.R. at 583.8 The Bondholders asserted nine\n\ncounterclaims, requesting declarations concerning their asserted\n\nsecurity interest as well as an alleged violation of the January\n\n2017 Stipulation.\n\n The parties both moved for summary judgment. Id. The\n\nSystem sought judgment in its favor on its four claims; the\n\nBondholders sought the dismissal of all of the System's claims as\n\nwell as judgment in their favor on all of their counterclaims.\n\nId.\n\n On August 17, 2018, the district court granted the\n\nSystem's motion for summary judgment in part and denied the\n\nBondholders' cross-motion in its entirety. Id. at 599-600. The\n\n\n 8 In other litigation before the commencement of the\nSystem's Title III case, the System had stated that at least some\nof the Bondholders had \"valid and enforceable liens in over\nhundreds of millions of dollars of ERS revenue.\" Respondent\nEmployees Retirement System of the Government of Puerto Rico's\nBrief in Opposition to Motion for Relief from the PROMESA Automatic\nStay at 10, Altair Global Credit Opportunities Fund (A), LLC. v.\nGarcia Padílla, Case No. 3:16-cv-02696-FAB (D.P.R. Oct. 26, 2016).\nThe district court noted this acknowledgment. In re: Fin.\nOversight & Mgmt. Bd. for P.R., 590 B.R. at 587.\n\n\n - 24 -\n\fdistrict court held that any security interest the Bondholders\n\nmight possess had not been perfected by the 2008 Financing\n\nStatements, because those Statements did not contain an adequate\n\ndescription of the collateral as required under Article 9 in 2008.\n\nId. at 589 (citing P.R. Laws Ann. tit. 19, § 2152(1) (2008)). The\n\ndistrict court then determined that the Financing Statement\n\nAmendments did not perfect the Bondholders' security interest,\n\nbecause they did not identify the debtor by its correct legal name,\n\nwhich the court determined was the RSE name, as the court felt was\n\nrequired by the version of Article 9 operative in 2015 and 2016.\n\nId. at 592 (citing P.R. Laws Ann. tit. 19, § 2322(a)(1)).\n\n Starting from the determination that the Bondholders'\n\ninterest was unperfected when the Title III case began, the\n\ndistrict court then held that the Oversight Board, as trustee,\n\ncould avoid the liens under the strong-arm provision at 11 U.S.C.\n\n§ 544(a), which PROMESA incorporates, see 48 U.S.C. § 2161(a). In\n\nre: Fin. Oversight & Mgmt. Bd. for P.R., 590 B.R. at 592-98. That\n\nis, Commonwealth law did not prevent a hypothetical creditor from\n\nobtaining a judgment lien against the System's assets at the time\n\nwhen the Title III case commenced. Id. at 594. The district court\n\nthus invalidated the Bondholders' interests pursuant to Section\n\n544(a). The district court then held that the System did not\n\nviolate the January 2017 Stipulation because the adversary\n\nproceedings were limited to claims or counterclaims related to\n\n\n - 25 -\n\femployer contributions received during May of 2017, and the\n\nSystem's obligation to transfer such funds to a segregated account\n\nclearly ended with the PROMESA stay on May 1, 2017. Id. at 599.\n\n Following a joint response to an order to show cause as\n\nto why the Bondholders' counterclaims One through Four \"ought not\n\nto be dismissed for failure to state a claim upon which relief may\n\nbe granted,\" the district court dismissed the Bondholders'\n\ncounterclaims with prejudice on September 5, 2018.\n\n The Bondholders timely appealed, and this court granted\n\nmotions to consolidate these appeals.\n\n II.\n\n This case comes on summary judgment. In reviewing grants\n\nof summary judgment, \"we take as true the facts documented in the\n\nrecord below, resolving any factual conflicts or disparities in\n\nfavor of the nonmovant.\" Colt Def. LLC v. Bushmaster Firearms,\n\nInc., 486 F.3d 701, 705 (1st Cir. 2007). Nearly all of the\n\noperative facts are undisputed here, and the grant of summary\n\njudgment turns primarily on interpretations of law, which this\n\ncourt reviews de novo, or mixed questions of law and fact, for\n\nwhich \"we employ a degree-of-deference continuum, providing non-\n\ndeferential plenary review for law-dominated questions and\n\ndeferential review for fact-dominated questions.\" Johnson v. Bos.\n\nPub. Sch., 906 F.3d 182, 191 (1st Cir. 2018) (internal quotation\n\nmarks omitted).\n\n\n - 26 -\n\f We first consider perfection by the 2008 Financing\n\nStatements on their own, and then in conjunction with the later\n\nFinancing Statement Amendments, before briefly considering\n\navoidance under PROMESA. We then address the dismissal of two of\n\nthe Bondholders' counterclaims and the alleged violation of the\n\nJanuary 2017 Stipulation.\n\nA. Perfection by the 2008 Financing Statements\n\n The Bondholders argue that the initial 2008 Financing\n\nStatements perfected their security interest. Under the former\n\nversion of Article 9 operative in 2008,\n\n [a] financing statement is sufficient if it\n [1] gives the names of the debtor and the\n secured party, [2] is signed by the debtor,\n [3] gives an address of the secured party from\n which information concerning the security\n interest may be obtained, [4] gives a mailing\n address of the debtor and [5] contains a\n statement indicating the types, or describing\n the items, of collateral.\n\nP.R. Laws Ann. tit. 19, § 2152(1) (2008). There is no dispute\n\nthat the 2008 Financing Statements met the first four requirements\n\nat the time they were filed, and so those elements are not\n\nconsidered here. We also stress that the validity of the\n\nunderlying Security Agreement is not at issue. Security agreements\n\nare private contracts between parties and do not have the same\n\npublic notice purpose as financing statements. See Webb Co. v.\n\nFirst City Bank (In re Softalk Publ'g Co., Inc.), 856 F.2d 1328,\n\n1330 (9th Cir. 1988). Instead, our discussion is limited only to\n\n\n - 27 -\n\fwhether the 2008 Financing Statements \"contain[] a statement\n\nindicating the types, or describing the items, of collateral,\" as\n\nrequired by the then-existing statute. See P.R. Laws Ann. tit.\n\n19, § 2152(1) (2008).\n\n The Bondholders argue that we should adopt a lenient\n\nunderstanding of the collateral description requirement, such that\n\nthe mere reference in the Security Agreement to the definition of\n\n\"Pledged Property\" contained in a separate document, the\n\nResolution, constituted a sufficient description, even though the\n\nResolution, and thus its description of \"Pledged Property,\" was\n\nnot attached to the 2008 Financing Statements. The Bondholders\n\ncite a number of cases to argue that incorporation by reference is\n\nappropriate in this situation. They argue this is in part because\n\nthe collateral description in a financing statement is, in their\n\nview, only \"a starting point\" in providing notice to an interested\n\nparty. John Deere Co. of Balt. v. William C. Pahl Constr. Co., 34\n\nA.D.2d 85, 88 (N.Y. App. Div. 1970).\n\n The System, joined by the Committee of Retired Employees\n\nof the Commonwealth of Puerto Rico (the \"Committee\") by reference\n\nin its brief, counters that the UCC's goals, like public notice,\n\nrequire a strict rule that interested parties should not face the\n\nburden and potential risks of further searching for a collateral\n\ndescription not found within or appended to a financing statement.\n\n We clear away some arguments which are beside the point.\n\n\n - 28 -\n\fIt is not helpful for the parties to use terms such as \"liberal\"\n\nor \"strict\" construction of Article 9. And it is likely that on\n\nsome facts, incorporation by reference was permissible under the\n\nversion of Article 9 operative in the Commonwealth when the 2008\n\nFinancing Statements were filed. That principle is not really at\n\nissue. On the facts on this record, we, like the district court,\n\nconclude that the 2008 Financing Statements were insufficient to\n\nperfect the security interest under P.R. Laws Ann. tit. 19,\n\n§ 2152(1) (2008).9 There has been no literal compliance with this\n\nrule, and this provision should be interpreted consonant with the\n\ngoals of the UCC.\n\n Our holding of an insufficient collateral description\n\ndepends heavily on the facts, where a) the collateral is not\n\n\n\n\n 9 The Bondholders do not cite controlling authority on\nthis issue. In Chase Bank of Fla., N.A. v. Muscarella, 582 So. 2d\n1196 (Fla. Dist. Ct. App. 1991), part of the collateral -- the\n\"Partnership Interest\" -- was listed in the financing statement\nitself, see id. at 1197, and so we agree that the \"[Muscarella]\nopinion does not stand for the proposition that it is sufficient\nfor a financing statement to merely refer to the underlying\nsecurity agreement and thereby incorporate by reference that\ndocument's collateral description.\" First Midwest Bank v.\nReinbold (In re: I80 Equip., LLC), 591 B.R. 353, 361 (Bankr. C.D.\nIll. 2018). In Int'l Home Prod., Inc. v. First Bank of P.R., Inc.,\n495 B.R. 152 (D.P.R. 2013), the referenced document was attached\nto the financing statement rather than filed or accessible only\nelsewhere. Id. at 160 n.8.\n And the citation to John Deere is inapposite here,\nbecause the reference in that case to a \"starting point for\ninvestigation\" does not refer to a description of collateral. 34\nA.D.2d at 88.\n\n\n\n - 29 -\n\fdescribed, even by type(s), in the 2008 Financing Statements or\n\nattachments; b) the 2008 Financing Statements do not tell\n\ninterested parties where to find the referenced document (the\n\nResolution) which contains the fuller collateral description; and\n\nc) the Resolution is not at the UCC filing office.\n\n First, the 2008 Financing Statements do not describe\n\neven the type(s) of collateral, much less the items, at issue.\n\nCf. Elf Atochem N. Am., Inc. v. Celco, Inc., 927 P.2d 355, 363\n\n(Ariz. Ct. App. 1996) (finding sufficient a financing statement\n\nthat described the collateral as \"equipment,\" as further described\n\nin two specific but unattached sales orders). They also do not\n\nattach the document (the Resolution) referenced as describing the\n\ncollateral. Nor do those facts alone define the issue before us.\n\nIn addition, the referenced document -- the Resolution -- was held\n\nin a different location from the UCC filing office, and the 2008\n\nFinancing Statements (including the attached Security Agreement)\n\ncontain no indication of the referenced document's location or how\n\nto find it.\n\n This total combination of facts undercuts several key\n\ngoals of the UCC and its filing system. These goals include fair\n\nnotice to other creditors and the public of a security interest.\n\nSee UCC § 9-502 cmt. 2;10 Wheeling & Lake Erie Ry. Co. v. Keach (In\n\n\n 10 \"UCC Official Comments do not have the force of law, but\nare nonetheless the most useful of several aids to interpretation\n\n\n - 30 -\n\fre: Montreal, Me. & Atl. Ry., Ltd.), 799 F.3d 1, 11 (1st Cir. 2015)\n\n(\"[A] primary goal of both Article 9 and . . . perfection rules is\n\nto ensure that other creditors have notice of [a] security\n\ninterest.\"); In re Softalk Publ'g Co., 856 F.2d 1328, 1330 (9th\n\nCir. 1988) (\"The [UCC] financing statement serves to give notice\n\nto other creditors or potential creditors that the filing creditor\n\nmight have a security interest in certain assets of the named\n\ndebtor.\"); In re Cushman Bakery, 526 F.2d 23, 28 (1st Cir. 1975)\n\n(stating that \"the system of notice filing is designed to . . .\n\napprise creditors that the secured party may have a security\n\ninterest in the collateral described in the financing\n\nstatement\").11 Article 9 was also meant to facilitate the expansion\n\nof commercial practices. See P.R. Laws Ann. tit. 19, § 401(2).12\n\n\nand construction of the [UCC].\" JOM, Inc. v. Adell Plastics, Inc.,\n193 F.3d 47, 57 n.6 (1st Cir. 1999) (internal quotation marks\nomitted).\n 11 Several of the cases cited by the Bondholders consider\nsecurity agreements rather than financing statements. E.g. Nolden\nv. Plant Reclamation (In the matter of Amex-Protein Dev. Corp.),\n504 F.2d 1056 (9th Cir. 1974); Greenville Riverboat, LLC v. Less,\nGetz & Lipman, P.L.L.C., 131 F. Supp. 2d 842 (S.D. Miss. 2000).\nAs noted, security agreements are private contracts that do not\nhave the same public notice purpose as financing statements. See\nIn re Softalk Publ'g Co., 856 F.2d 1328, 1330 (9th Cir. 1988).\n 12 Where a referenced document is not in the UCC records\nand its location is not listed in the financing statement itself\n(nor how to find it), an interested party must do additional\nsearching at its own expense to determine the collateral at issue.\nThis remains true even where the extrinsic document is publicly\navailable elsewhere: The interested party still has to search\nbeyond where the initial financing statement has been filed, and\ndo so without any guidance. It may not have been difficult for\n\n\n - 31 -\n\f Here, as said, the 2008 Financing Statements do not\n\ndescribe even the type(s) of collateral; instead, they describe\n\nthe collateral only by reference to an extrinsic document located\n\noutside the UCC filing office, and that document's location is not\n\nlisted in the financing statement. This at best gives an\n\ninterested party notice about an interest in some undescribed\n\ncollateral, but does not adequately specify what collateral is\n\nencumbered. That is, an interested party knowing nothing more\n\nthan this does not have \"actual knowledge\" and has not \"received\n\na notice,\" see P.R. Laws Ann. tit. 19, § 451(25)(a)-(b) (2008), of\n\nthe collateral at issue. Requiring interested parties to contact\n\ndebtors at their own expense about encumbered collateral, with no\n\nguarantee of a timely or accurate answer, would run counter to the\n\nnotice purpose of the UCC.13 See, e.g., In re Quality Seafoods,\n\n\n\ninterested parties to find the Resolution here, but no party\ndisputes that additional searching would have been necessary.\n Interested parties doing such a search could well have\njustifiable concerns about the extrinsic referenced document.\nHow, for example, would an interested party know whether a\ndescription of collateral in the extrinsic document is the latest\noperative version (rather than a superseded version), whether that\ndocument is complete, or whether the document found on another\nwebsite or at another location is authentic rather than doctored\nin some way? Forcing interested parties to undertake additional\nwork and expense merely to find a basic collateral description\ncuts against the goal of expansion of commercial practices.\n 13 In re Cushman Bakery did not determine that further\ninquiry by interested parties regarding the specific encumbered\ncollateral was required under Article 9, but instead stated only\nthat \"further inquiry from the parties concerned [would] be\nnecessary to disclose the complete state of affairs\" around a\n\n\n - 32 -\n\fInc., 104 B.R. 560, 561 (Bankr. D. Mass. 1989).\n\n The UCC filing requirements are clear. See Uniroyal,\n\nInc. v. Universal Tire & Auto Supply Co., 557 F.2d 22, 23 (1st\n\nCir. 1977). It would not have been difficult whatsoever for the\n\n2008 Financing Statements to provide proper notice. The Resolution\n\ncould simply have been attached to these filings, as the Security\n\nAgreement was. Instead, as they stand, the 2008 Financing\n\nStatements would leave a reasonable creditor or interested party\n\nwith doubts as to the collateral at issue. We do not interpret\n\nthe former UCC provision in a way contrary to its purposes, above\n\nall notice, and so the description of collateral in the 2008\n\nFinancing Statements was insufficient.\n\n Having resolved the logically antecedent question\n\nconcerning the first UCC filings, we turn to the amendment issues.\n\nB. Lapse of 2008 Financing Statements\n\n The System and the Committee argue that the 2008\n\nFinancing Statements could not later satisfy the requirements for\n\nperfection, by amendment, because the 2008 Financing Statements\n\nhad lapsed by the time the Financing Statement Amendments were\n\nfiled in 2015 and 2016. The Commonwealth's enactment of a revised\n\nArticle 9, they argue, shortened the effective time period of an\n\ninitial financing statement from ten years to five years. Compare\n\n\n\ntransaction. 526 F.2d at 28-29 (emphasis added).\n\n\n - 33 -\n\fP.R. Laws Ann. tit. 19, § 2335(a) (five years) with id. § 2153(2)\n\n(2008) (ten years). Here, the Financing Statement Amendments were\n\nfiled about seven and a half years after the 2008 Financing\n\nStatements. Because lapsed financing statements are ineffective,\n\nsee P.R. Laws Ann. tit. 19, § 2335(c), the Committee argues that\n\nthe Amendments filed by the Bondholders could not have cured the\n\ndeficiencies as to the collateral description in the 2008 Financing\n\nStatements. In support of their view, the System and the Committee\n\nprimarily point to a transition provision, the \"Savings clause,\"\n\nin the revised Article 9, which states that \"[e]xcept as otherwise\n\nprovided in this subchapter, this act applies to a transaction or\n\nlien within its scope, even if the transaction or lien was entered\n\ninto or created before this act takes effect.\" Id. § 2402(a).\n\n This argument on lapse fails for several reasons. First,\n\nas to retroactivity, this Savings clause is not intended to apply\n\nto the separate provision that shortened the life of financing\n\nstatements on its effective date. The Commonwealth's Law 17 of\n\n2014, which clarified that the effective time period of financing\n\nstatements was five years, does not contain a statement concerning\n\nretroactivity. See Law No. 17 of January 16, 2014. And as a\n\ntextual matter, we would expect that a provision intended to apply\n\nretroactively to financing statements would directly mention\n\nfinancing statements, particularly given the Commonwealth's long-\n\nstanding requirement that a law must \"expressly so decree\" in order\n\n\n - 34 -\n\fto have retroactive effect. P.R. Laws Ann. tit. 31, § 3.\n\n Second, the P.R. Department of State, where UCC filings\n\nare made, considered the amendment to the time period \"for the\n\nlife of an initial financing statement\" and concluded that the\n\ndecrease to five years \"cannot be retroactive.\" P.R. Dept. of\n\nState, Circular 2014-01, Clarifications on Term for Filing\n\nContinuing Financing Statements Based on Law 17-2014 (Jan. 24,\n\n2014) (English trans.). That is, \"for initial financ[ing]\n\nstatements filed on or before January 15, 2014, [the] term is ten\n\n(10) years.\" Id. 14 Though this Circular does not have the force\n\nof law, it is informative on this issue. Consistent with this\n\nCircular, the Filing Office did not refuse to accept the Financing\n\nStatement Amendments, as it would have been required to do if the\n\n2008 Financing Statements had lapsed. See P.R. Laws Ann. tit. 19,\n\n§ 2336(b)(3)(B)(ii).\n\n Third, our conclusion comports with P.R. Laws Ann. tit.\n\n31, § 3, the general provision of the Commonwealth's Civil Code,\n\nwhich states that \"[i]n no case shall the retroactive effect of a\n\nlaw operate to the prejudice of rights acquired under previous\n\n\n\n\n 14At oral argument, counsel for the System suggested that\nthe P.R. Department of State's Circular applied only to perfected\ninterests. This is incorrect. The Circular refers to \"initial\nfinancing statements\" in bold text on both pages and does not limit\nits determination regarding retroactive effect to previously\nperfected interests.\n\n\n - 35 -\n\flegislative action.\"15 Acceptance of the System's position would\n\nrun afoul of this provision. The enactment of the old Article 9\n\ninto Commonwealth law was clearly a legislative action. Applying\n\nthe five-year rule retroactively would harm the rights of creditors\n\nholding perfected security interests through initial financing\n\nstatements that were between five and ten years old on January 16,\n\n2014, the effective date of the modified rule. See id. tit. 19,\n\n§ 2335(a). Nothing in the law on the effective time limit for\n\nfinancing statements suggests treating financing statements\n\ndifferently depending on perfection, and instead refers broadly to\n\n\"a filed financing statement\" and the \"date of filing,\" id.\n\n(emphasis added). So, the bar on retroactivity protects all filers\n\nin the time period at issue (which includes the Bondholders in\n\nthis case).\n\n The 2008 Financing Statements had not lapsed when the\n\nFinancing Statement Amendments were filed about seven and a half\n\nyears later, because the ten-year rule applied to the 2008\n\nFinancing Statements.\n\n\n\n\n 15 As a general matter, the Supreme Court of the\nCommonwealth of Puerto Rico has suggested, considering this law,\nthat it is \"highly desirable that . . . [a] new rule will have\nprospective effect; especially, when contractual or property\nrights are at stake.\" Almodóvar v. Róman, 125 P.R. Offic. Trans.\n218 (P.R. 1990).\n\n\n - 36 -\n\fC. Perfection by the Financing Statement Amendments in\n Conjunction with the 2008 Financing Statements\n\n We next consider whether the Financing Statement\n\nAmendments cured defects in the initial Statements, when these\n\nfilings are read together. See, e.g., P.R. Laws Ann. tit. 19,\n\n§ 2404(3)(B); see also Miami Valley Prod. Credit Ass'n v. Kimley,\n\n536 N.E.2d 1182, 1186 (Ohio Ct. App. 1987) (\"We are willing to\n\ntreat the two financing statements as a single financing statement\n\n. . . .\"). We do not reach the Bondholders' alternative argument\n\nthat the Financing Statement Amendments independently perfected\n\ntheir security interest, since we determine that the Financing\n\nStatement Amendments cured defects in the 2008 Financing\n\nStatements. Similarly, we do not reach the Bondholders' argument\n\nthat Section 2323 allows the use of \"other name[s]\" of a debtor,\n\nsee P.R. Laws Ann. tit. 19, § 2323(b)(1), as this would require a\n\nbroader consideration of aspects of Article 9 that are beyond the\n\nnecessary scope of this case.\n\n Article 9 contemplates situations where a financing\n\nstatement amendment \"cures\" an earlier financing statement by\n\nfixing outdated or incorrect information in the financing\n\nstatement, such as after a name change by a debtor. See, e.g.,\n\nid. § 2327(c). Under Article 9, \"[a] security interest . . . (3)\n\nbecomes perfected . . . (B) when the applicable requirements for\n\nperfection are satisfied.\" Id. § 2404(3)(B). As to these\n\n\n\n - 37 -\n\f\"applicable requirements,\" a financing statement is sufficient\n\nonly \"if it: (1) Provides the name of the debtor; (2) provides the\n\nname of the secured party or a representative of the secured party,\n\nand (3) indicates the collateral covered by the financing\n\nstatement.\" Id. § 2322(a). We now consider the Bondholders'\n\ncompliance with these requirements in the 2008 Financing\n\nStatements and the Financing Statement Amendments.\n\n 1. Name of the Secured Party and Collateral Description\n\n The Financing Statement Amendments sufficiently provide\n\nthe name of the secured party's agent in Exhibit A: \"The Bank of\n\nNew York Mellon, as Fiscal Agent,\" as required under Section\n\n2322(a)(2).16 No party disputes this clear point.\n\n As to the collateral description requirement, under the\n\nnew Article 9, a collateral description of personal property is\n\nsufficient \"whether or not it is specific, if it reasonably\n\nidentifies what is described,\" id. § 2218(a), but a \"[s]upergeneric\n\ndescription [is] not sufficient,\" id. § 2218(c). One of the\n\n\"[e]xamples of reasonable identification,\" id. § 2218(b), under\n\nArticle 9 is a \"[s]pecific listing\" of the collateral, id.\n\n§ 2218(b)(1).\n\n Here, the Financing Statement Amendments described the\n\ncollateral as \"[t]he Pledged Property and all proceeds thereof and\n\n\n 16 The 2008 Financing Statements also properly list the\nSecured Party as \"The Bank of New York, as fiscal agent[.]\"\n\n\n - 38 -\n\fall after-acquired property as described more fully in Exhibit A\n\nattached hereto and incorporated by reference.\" Exhibit A, in\n\nturn, contained a detailed definition of \"Pledged Property.\"17\n\nEach of the relevant capitalized terms in the definition of\n\n\"Pledged Property\" -- \"Revenues,\" \"Funds,\" \"Accounts,\"\n\n\"Subaccounts,\" \"Fiscal Agent,\" \"Debt Service Reserve Account,\" and\n\n\"Resolution\" -- is also defined in Exhibit A. The definition of\n\n\"Pledged Property\" satisfied one of the \"[e]xamples of reasonable\n\nidentification\" by providing a \"[s]pecific listing\" of the\n\ncollateral. Id. It therefore suffices as a description of\n\ncollateral.\n\n 2. Name of the Debtor\n\n We now turn to the key question of whether the Financing\n\nStatement Amendments contain a sufficient \"name of the debtor.\"\n\nArticle 9 contains different requirements for the names of\n\nregistered organizations and for the names of individuals. A\n\n\"[r]egistered organization\" is defined, in part, as \"an\n\norganization organized solely under the law of a single state or\n\nthe United States by the filing of a public organic record with,\n\nthe issuance of a public organic record by, or the enactment of\n\nlegislation by the state or United States.\" Id. § 2212(a)(71).\n\nThe System is a registered organization because it is an\n\n\n 17 The full definition of \"Pledged Property\" is the same as\nin the Resolution, and is reproduced in note 3, supra.\n\n\n - 39 -\n\forganization formed and organized by the Commonwealth's enactment\n\nof legislation: the 1951 Enabling Act. When a debtor is a\n\nregistered organization,\n\n [a] financing statement sufficiently provides\n the name of the debtor . . . only if the\n financing statement provides the name that is\n stated to be the registered organization's\n name on the public organic record most\n recently filed with or issued or enacted by\n the registered organization's jurisdiction of\n organization which purports to state, amend,\n or restate the registered organization's name.\n\nId. tit. 19, § 2323(a)(1). Though a financing statement that\n\n\"provides only the debtor's trade name does not sufficiently\n\nprovide the name of the debtor,\" id. § 2323(c), an otherwise\n\nsufficient financing statement, containing a correct name of the\n\ndebtor, is \"not rendered ineffective by the absence of . . . [a]\n\ntrade name or other name of the debtor,\" id. § 2323(b).18\n\n\n\n 18 Article 9 also provides a safe harbor provision for minor\nerrors or omissions: \"A financing statement substantially\nsatisfying the requirements of this subchapter is effective, even\nif it has minor errors or omissions, unless the errors or omissions\nmake the financing statement seriously misleading.\" P.R. Laws\nAnn. tit. 19, § 2326(a). For a name,\n\n if a search of the records of the filing office\n under the debtor's correct name, using the\n filing office's standard search logic, if any,\n would disclose a financing statement that\n fails sufficiently to provide the name of the\n debtor in accordance with § 2323 (a) of this\n title, the name provided does not make the\n financing statement seriously misleading.\n\nId. § 2326(c).\n\n\n - 40 -\n\f Like the 2008 Financing Statements, Exhibit A to the\n\nFinancing Statement Amendments stated the name of the debtor as\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico.\" The 2008 Financing Statements also stated the\n\n\"[e]ntity name\" of the debtor as \"Employees Retirement System of\n\nthe Government of the Commonwealth of Puerto Rico.\" The System\n\nand the Committee argue that, as of February 28, 2018, this became\n\nthe incorrect name because, in their view, the English translation\n\nof the 2013 amendment to the Enabling Act changed the System's\n\nEnglish name. Id. tit. 3, § 761. The English translation of that\n\nAct states that \"[a] retirement and benefit system to be designated\n\nas the 'Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico' . . . is hereby created.\" Law No. 3\n\nof April 4, 2013, 2013 P.R. Laws 64. In the System's view, the\n\n2013 amendment to the Enabling Act is the relevant \"public organic\n\nrecord most recently filed with or issued or enacted by the\n\nregistered organization's jurisdiction of organization.\" P.R.\n\nLaws Ann. tit. 19, § 2323(a)(1). The System argues that Section\n\n1-101, codified at P.R. Laws Ann. tit. 3, § 761, alone is the\n\nsection which \"state[s]\" the name of the System under Section\n\n2323(a)(1), and so concludes that the RSE name is the name for\n\nArticle 9 purposes. That is, the System argues that it is\n\nirrelevant that other sections of the Act use \"Employees Retirement\n\nSystem,\" see, e.g., id. § 763(36), because only Section 1-101 of\n\n\n - 41 -\n\fthe translation \"purports to state, amend, or restate the\n\nregistered organization's name,\" id. tit. 19, § 2323(a)(1). Even\n\nif this were a translation error, the System argues, \"that\n\nerroneous translation would nevertheless constitute [the System's]\n\nname for Article 9 purposes.\" The System argues that any UCC\n\nfiling (whether a financing statement or financing statement\n\namendment) under \"Employees Retirement System of the Government of\n\nthe Commonwealth of Puerto Rico\" does not state the correct name.\n\nOn this view, because a search under the correct name --\n\n\"Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico\" -- would not find such a UCC filing,\n\nuse of the ERS name is seriously misleading. P.R. Laws Ann. tit.\n\n19, § 2326(c).\n\n The Bondholders make numerous arguments in opposition\n\nregarding the sufficiency of the name used, some statutory and\n\nsome focused on the System's own conduct. We do not detail those\n\narguments further, but deal with them in our analysis.\n\n We resolve the merits of this matter on the record, which\n\nis adequate. Both the 2008 Financing Statements and the Financing\n\nStatement Amendments were filed in English. And so we look to the\n\n2014 English translation of the Enabling Act to determine whether\n\nthe Financing Statement Amendments comply with the UCC's reference\n\nto the \"public organic record most recently . . . enacted by the\n\n[System's] jurisdiction of organization which purports to state,\n\n\n - 42 -\n\famend, or restate the [System's] name.\" P.R. Laws Ann. tit. 19,\n\n§ 2323(a)(1). The \"to be designated as\" language codified at\n\nSection 761 does not mean that no other portion of the statute\n\n\"state[s]\" the name of the System for UCC purposes. The System\n\nmisconstrues the relevant UCC provision here, by suggesting that\n\nonly the first section of the Enabling Act \"purports to state,\n\namend, or restate the registered organization's name,\" id. tit.\n\n19, § 2323(a)(1), because that section uses the following\n\nlanguage: \"A retirement and benefit system to be designated as the\n\n'Retirement System for Employees of the Government of the\n\nCommonwealth of Puerto Rico,' . . . is hereby created.\" Id. tit.\n\n3, § 761. The requirement is that a filer \"provide the name that\n\nis stated\" in the \"public organic record . . . which purports to\n\nstate, amend, or restate the registered organization's name.\" Id.\n\n(emphasis added). The latter clause, starting with \"which\n\npurports,\" plainly modifies \"public organic record.\" So, it does\n\nnot follow that only one of many clauses in the statute must be\n\nall that can be considered when determining what \"name . . . is\n\nstated\" in the \"public organic record.\"19 Instead, this UCC\n\n\n 19 The System's argument by analogy to the UCC's provision,\nP.R. Laws Ann. tit. 19, § 2323(a)(4), regarding an individual's\nname on a driver's license, is unpersuasive. The System argues\nthat since an incorrect name on a driver's license must be used as\nthe party's name in a sufficient UCC filing, if the filing is made\nin the same state as the driver's license was issued, the RSE name\nmust be used here (whether or not it is a correct name). This\nargument by analogy is necessarily premised on the view that the\n\n\n - 43 -\n\fprovision directs focus to the entire \"public organic record which\n\npurports to state, amend, or restate the registered organization's\n\nname.\" Id. The fact that Section 1-101 of the English translation\n\nof the amended Enabling Act uses \"Retirement System for Employees\n\nof the Government of the Commonwealth of Puerto Rico\" does not end\n\nthe inquiry.\n\n The official English translation, on its face,\n\nrepeatedly translates the exact same Spanish name in two different\n\nways.20 Both \"Retirement System for Employees\" and \"Employees\n\nRetirement System,\" are used, seemingly interchangeably,\n\nthroughout the translated Act as codified. No provision of the\n\nAct states, nor even suggests, that the ERS name is used as a trade\n\n\n\n2013 amended Act states only the RSE name, whether or not it is a\ntranslation error. If, as we conclude, the amended Act states the\nERS name as a name for the System, a searcher can still rely only\non official records and there is no issue about a searcher having\nto use an \"incorrect\" name.\n More generally, the requirement for an individual with\na driver's license issued in the state is not relevant here, where\nwe consider a registered organization that is created and\ndesignated by statute.\n 20 The Spanish language at issue did not change in the 2013\namendment to the Enabling Act. The language translated as \"to be\ndesignated as the 'Retirement System for Employees,'\" is \"que se\ndenominará 'Sistema de Retiro de Los Empleados.\" Compare Law No.\n3 of April 4, 2013, 2013 P.R. Laws 39 with id. (Spanish). This is\nthe same Spanish language used after the last amendment to the\nEnabling Act in 2004. P.R. Leyes Ann. tit. 3, § 761 (2005). And\nindeed, the portion of the Spanish corresponding to the first part\nof the name of the System -- \"Sistema de Retiro de Los Empleados\"\n-- was the same in the original Enabling Act of 1951, and was\ntranslated there as \"Employees Retirement System.\" Compare Law\nNo. 447 of May 15, 1951, 1951 P.R. Laws 1298 with id. at 1299.\n\n\n - 44 -\n\fname or nickname rather than an official, legal name.21 We do not\n\nagree with the System that one English name (the RSE name) is\n\nofficial and the other (the ERS name) is merely a trade name, which\n\nwould be insufficient.\n\n The System's argument that the \"to be designated\" clause\n\nin Section 1-101 alone must control fails for a number of reasons.\n\nThe numerous clauses using the ERS name are hardly trivial. It is\n\ntrue that \"Retirement System for Employees\" is used three times in\n\nthe translated Act, as codified. Id. §§ 761, 763(1), 779.22 But\n\n\"Employees Retirement System\" is used far more often: by our count,\n\nmore than thirty-five times in the Act as codified. Perhaps most\n\nimportantly, \"Employees Retirement System\" is used in the primary\n\ndefinition of \"[s]ystem.\" Id. § 763(36) (\"System [s]hall mean the\n\nEmployees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico.\"). Other uses of the ERS name include in the\n\nheading of Section 1-101, id. § 761, as well as the headings of\n\n\n 21 We do not need to decide whether a translation error\noccurred in this instance. We do note that in the relevant portion\nof the Spanish version of the Act, the Spanish preposition most\ncommonly translated as \"for\" -- para -- is not used. See\nUniversity of Cambridge, Spanish-English Dictionary,\nhttp://dictionary.cambridge.org/dictionary/spanish-english,\n\"para.\"\n 22 It is not clear that the use in Section 779 refers to\nthe same System, though we assume it does. This provision in\nEnglish describes the \"Retirement System of the Employees of the\nGovernment and its Instrumentalities,\" P.R. Laws Ann. tit 3, §\n779, rather than \"Retirement System for Employees of the Government\nof the Commonwealth of Puerto Rico,\" id. § 761.\n\n\n - 45 -\n\fmany other sections, see id. §§ 761a, 762, 763, 764, 765, 765a,\n\n766, 766a, 766b, 766c, 766d, 768, 768a, 769, 769a, 770, 770a, 771,\n\n772, 773, 774, 775, 776, 777, 778, 779, 779a, 779b, 779c, 781a,\n\n782, 783, 784, 785, 786, 786a, 786b, 787, 788.\n\n The System and the Committee have offered no explanation\n\nas to why, when both terms are used, the ERS name should be\n\ndisregarded. It is difficult to discern why \"Retirement System\n\nfor Employees\" is used instead of \"Employees Retirement System\" in\n\nthe particular places where the RSE name is used. Nothing about\n\nthe context suggests that one or the other should be used, and the\n\nunderlying Spanish is the same.\n\n We think a reasonable creditor would be familiar with\n\nthe Commonwealth law that, in a case of a discrepancy between the\n\nEnglish and Spanish, when the legislation originated in Spanish\n\n\"the Spanish text shall be preferred to the English.\" P.R. Laws\n\nAnn. tit. 31, § 13; see Republic Sec. Corp. v. P.R. Aqueduct &\n\nSewer Auth., 674 F.2d 952, 956 (1st Cir. 1982) (\"[I]n cases of\n\ndiscrepancy 'the Spanish text shall be preferred.'\"). Further, we\n\nsee no evidence that the legislature of the Commonwealth intended\n\nto change the English name of the System to the RSE name and\n\nabandon the ERS name. We would expect to see a clear statement\n\nexpressing a desire to change the translation, and there is no\n\nsuch statement. This expectation is only reinforced by Section\n\n13, described above.\n\n\n - 46 -\n\f The legislature provided a Statement of Motives to the\n\n2013 amendment, which identified, for example, the fiscal crisis\n\nin Puerto Rico, the causes of the crisis, and the need to act\n\npromptly. Law No. 3 of April 4, 2013, 2013 P.R. Laws 39-64. And\n\nthe legislature then explained \"[e]ach one of the amendments,\" id.\n\nat 58, such as the \"[i]ncrease in the employee contribution\n\n[rate],\" id. at 59. There is no explanation in this section that\n\nthe 2013 amendment was meant to change the name of the System.\n\nEarlier name changes, including in 2004, demonstrate generally\n\nthat the legislature understands how to change the System's name\n\nwhen it wants to do so.\n\n It is also significant that the RSE name referenced in\n\nthe \"to be designated\" clause differs from prior longstanding\n\nofficial uses. From 1951 through 2012, translated versions of the\n\nEnabling Act used only \"Employees Retirement System\" in the first\n\nsection. See, e.g., Law No. 447 of May 15, 1951, 1951 P.R. Laws\n\n1298; P.R. Laws Ann. tit. 3, § 761 (1988); id. (2006), id. (2011).\n\nIt is only the translation of the 2013 amendment which breaks this\n\nconsistent pattern. Of course, a long-standing name of an\n\norganization or agency that is named by statute can be changed by\n\nstatute. Here, though, the legislature did change the System's\n\nname several times, including changing the name of the System in\n\n2004 by removing \"and its Instrumentalities\" (\"y sus\n\nInstrumentalidades\") from the end of the System's name and by\n\n\n - 47 -\n\freplacing \"Government of Puerto Rico\" with \"Government of the\n\nCommonwealth of Puerto Rico\" (\"Gobierno del Estado Libre Asociado\n\nde Puerto Rico\"). Law No. 296 of September 15, 2004, § 1-101;\n\nP.R. Laws Ann. tit. 3, § 761 (2006). But, with each of these\n\nchanges, the \"Employees Retirement System\" part of the name\n\nremained the same. Our conclusion that there was no legislative\n\nintent to change the System's name is also bolstered by post-2014\n\nlegislative action. Years after the 2014 translation of the\n\namended Enabling Act, the official translation of the Puerto Rico\n\nFinancial Emergency and Fiscal Responsibility Act of 2017 referred\n\nto the System in part as \"the Employees Retirement System.\" P.R.\n\nLaws Ann. tit. 3, § 9433(r).\n\n Further, the ERS name is the name consistently used by\n\nthe System itself, including in court filings, before and after\n\nthe translation of the amended Act in 2014. There are many\n\nexamples of this; we list only a few. In its complaint in this\n\ncase, the System referred to itself as \"the Employees Retirement\n\nSystem of the Government of the Commonwealth of Puerto Rico\" or\n\n\"ERS.\" The System referred to itself in the same way in its Answer\n\nto Defendant's Counterclaims. The System did not mention\n\n\"Retirement System for Employees\" or \"RSE\" in either document.\n\n Independently, in its Title III Petition form, dated May\n\n21, 2017, the ERS name was used under \"Debtor's name.\" In the box\n\non the Title III form asking for \"[a]ll other names Debtor used in\n\n\n - 48 -\n\fthe last five years [-] Include any assumed names, trade names,\n\nand doing business as names,\" only a Spanish name was listed,\n\n\"Adminstracion de los Sistemas de Retiro de los Empleados del\n\nGobierna y la Judicatura,\" with no mention of \"Retirement System\n\nfor Employees.\" Further, the System made no statement that\n\n\"Employees Retirement System\" was being used as a trade name.\n\nAgain, these are only a few of the many times that the System held\n\nitself out as the \"Employees Retirement System\" around the time of\n\nand after the translation of the amended Enabling Act was in\n\neffect. The district court determined, and the System now argues,\n\nthat the System used the ERS name simply as a trade name after\n\n2014. See In re: Fin. Oversight & Mgmt. Bd. for P.R., 590 B.R. at\n\n592. We disagree.\n\n Finally, there is no doubt that the ERS name was the\n\nofficial and only name of the System for over sixty years. So,\n\nany putative creditors would have had to search under that name to\n\nfind prior liens even if the System's name did change in 2014.\n\nSee P.R. Laws Ann. tit. 19, § 2327(c) (providing that a secured\n\nparty owning a lien on the debtor's property acquired prior to a\n\nname change is not required to file a new financing statement).\n\nThis observation adds further support to the central proposition\n\nthat any putative creditor who read the 2014 translation of the\n\nEnabling Act would conclude that, given the inconsistent use of\n\nboth the ERS and RSE names, it should at the very least search\n\n\n - 49 -\n\funder the long-standing ERS name.\n\n All of these reasons lead us to conclude that \"Employees\n\nRetirement System of the Government of the Commonwealth of Puerto\n\nRico\" remained a valid name for UCC purposes when the Financing\n\nStatement Amendments were filed.23 In our view, a searcher, whether\n\nanother creditor or merely an interested party, would conclude\n\nthat a search under the ERS name was required. Similarly, a\n\nreasonable filer would have concluded that the ERS name was a\n\ncorrect name for the debtor for UCC purposes.\n\n Because the Financing Statement Amendments used\n\n\"Employees Retirement System of the Government of the Commonwealth\n\nof Puerto Rico,\" they contained an appropriate name of the debtor\n\nunder the Commonwealth's Article 9. See P.R. Laws Ann. tit. 19,\n\n§§ 2322(a), 2323(a)(1), 2404(3)(B). Taken together with the 2008\n\nFinancing Statements, the Financing Statement Amendments met the\n\nrequirements for perfection as of December 17, 2015. See id.\n\n§ 2322(a).\n\n\n\n\n 23 Even were we to accept that \"[t]he majority of cases\ndecided under . . . Article 9 are unforgiving of even minimal\nerrors [for the name of the debtor],\" In re John's Bean Farm of\nHomestead, Inc., 378 B.R. 385, 391 (Bankr. S.D. Fla. 2007), a\nfiling under the ERS name is not such an error. The situation\nhere is clearly unlike, for example, a filer misspelling the name\nof a tractor seller as \"Roger\" rather than \"Rodger.\" See Pankratz\nImplement Co. v. Citizens Nat. Bank, 130 P.3d 57, 59 (Kan. 2006).\n\n\n\n - 50 -\n\fD. Avoidance under PROMESA\n\n Because we determine that the Bondholders satisfied\n\nArticle 9's perfection requirements before the passage of PROMESA\n\non June 30, 2016, we do not consider whether PROMESA would allow\n\nretroactive avoidance of unperfected liens.24 The debtors do not\n\nargue that the strong-arm provision of the Bankruptcy Code,\n\nincorporated by reference in PROMESA, would allow them to avoid\n\nthe Bondholders' interest if the interest is perfected.\n\n And as a \"basic tenet of the law of secured\n\ntransactions,\" a \"perfected security interest prevails over a\n\nsubsequent lien creditor.\" Ledford v. Easy Living Furniture, 52\n\nB.R. 706, 710 (Bankr. S.D. Ohio 1985); accord Gen. Elec. Credit\n\nCorp. v. Nardulli & Sons, Inc., 836 F.2d 184, 189 (3d Cir. 1988)\n\n(holding that because the parties filed correctly and perfected\n\ntheir security interest, \"their rights as lienholders are superior\n\nto those of the trustee as a hypothetical lienholder under 11\n\nU.S.C. § 544\"). Commonwealth law recognizes this rule of priority\n\nby implication, in stating that a judicial creditor's lien is\n\n\n\n 24Similarly, we need not consider the System's argument\nthat the Bondholders' security interest was always inferior to\nsubsequent perfected security interests and judicial liens under\nthe UCC, see P.R. Laws Ann. tit. 19, §§ 2219(a)(1), 2212(52),\n2267(a)(2)(A), because this argument is necessarily premised on\nthe Bondholders having only an unperfected security interest. The\nSystem does not argue that the UCC would grant priority over a\npreviously perfected lien, and the statutory text is clear on this\nissue. Id. § 2267(a)(2)(A).\n\n\n\n - 51 -\n\fsuperior to a prior unperfected security interest. See P.R. Laws\n\nAnn. tit. 19, § 2267(a)(2)(A). \"Where a creditor has an\n\nunperfected lien on a debtor's property, the Bankruptcy Code\n\nempowers a trustee to avoid and preserve the lien for the benefit\n\nof the estate.\" DiGiacomo v. Traverse (In re Traverse), 753 F.3d\n\n19, 26 (1st Cir. 2014) (emphasis added).\n\nE. The Bondholders' Counterclaims\n\n The Bondholders also appeal the dismissal of their\n\nsecond and third counterclaims, both requests for declaratory\n\njudgment. Counterclaim Two sought a declaration stating that the\n\n\"Bondholders hold valid, enforceable, attached, perfected, first\n\npriority liens on and security interest in the Pledged Property\n\nwhether ERS became entitled to collect such property before or\n\nafter the commencement of ERS's Title III case.\" Counterclaim\n\nThree sought a declaration stating that \"because the employer\n\ncontributions constitute 'special revenues,' [Bondholders']\n\nsecurity interests in and liens on employer contributions received\n\nby the [System] after the Petition Date remain enforceable pursuant\n\nto 11 U.S.C. § 928(a).\" The Bondholders argue that the district\n\ncourt did not adequately address arguments for these\n\ncounterclaims.\n\n As to Counterclaim Two, the Bondholders acknowledged in\n\nthe district court that the \"[11 U.S.C.] section 552 issues need\n\nnot be reached in light of the Summary Judgment Decision,\" and did\n\n\n - 52 -\n\fnot provide \"any reason that the remaining aspects of Count Two\n\nshould be resolved differently from the Claims resolved by the\n\nSummary Judgment Decision.\" As to Counterclaim Three, the\n\nBondholders stipulated that \"in light of the Summary Judgement\n\ndecision [the Bondholders] are unable to identify any need for the\n\n[district court] to reach the alternative arguments.\"\n\n Because we find the 2008 Financing Statements effective\n\nas amended, we remand to the district court for further\n\nconsideration of the dismissals of these counterclaims in light of\n\nthis opinion.\n\nF. Violation of the January 2017 Stipulation\n\n Finally, the Bondholders argue that ERS violated the\n\nJanuary 2017 Stipulation between the parties, and the district\n\ncourt erred in determining that no violation occurred (or that it\n\nwas beyond the scope of the proceeding). Specifically, they assert\n\nthat the System violated that Stipulation because it requires that,\n\n\"[t]o the extent that ERS receives any Commonwealth central\n\ngovernment Employers' contributions, unless otherwise agreed in\n\nwriting by the undersigned parties, such contributions shall be\n\nretained in the Segregated Account pending further order of the\n\nCourt.\" The System points out that a Joint Stipulation between\n\nthe parties in this case limited claims or counterclaims on\n\nemployer contributions only to those received during May 2017.\n\n Even assuming the Bondholders have not waived this\n\n\n - 53 -\n\fargument,25 it fails. The Joint Stipulation shows that the parties\n\nagreed that the scope of the adversary proceedings at the district\n\ncourt would include \"ERS's rights with respect to employer\n\ncontributions received during the month of May 2017,\" and beyond\n\nsome other stipulated claims and counterclaims, \"no other claims\n\nmay be made by either side\" (emphasis added). So only the\n\ncontributions during the month of May 2017 are properly at issue\n\nhere. But as the district court correctly noted, In re: Fin.\n\nOversight & Mgmt. Bd. for P.R., 590 B.R. at 599, the Bondholders\n\nconceded in their Answer and Counterclaims below that \"ERS was\n\nobligated to place Employers' Contributions into the Segregated\n\nAccount only for the duration of the [PROMESA] Section 405 Stay,\"\n\nand the Section 405 stay expired as of May 1, 2017. The Bondholders\n\nhave not explained how their argument concerning the alleged\n\nviolation of the January 2017 Stipulation survives these\n\nadmissions, taking into account the stipulated scope of the\n\nadversary proceedings. The district court correctly dismissed the\n\nBondholders' claim regarding an alleged violation of the January\n\n2017 Stipulation.\n\n\n\n 25Neither opening brief from the Bondholders makes a full\nargument concerning the alleged violation of the January 2017\nStipulation. See United States v. Zannino, 895 F.2d 1, 17 (1st\nCir. 1990) (\"It is not enough merely to mention a possible argument\nin the most skeletal way, leaving the court to do counsel's work,\ncreate the ossature for the argument, and put flesh on its\nbones.\").\n\n\n - 54 -\n\f III.\n\n We affirm the district court's holding that the 2008\n\nFinancing Statements did not perfect the Bondholders' security\n\ninterest in the \"Pledged Property.\" We determine that the\n\nBondholders met the requirements for perfection beginning on\n\nDecember 17, 2015, and so reverse the district court. PROMESA's\n\nincorporation of the Bankruptcy code does not allow for the\n\navoidance of perfected liens, and so we vacate the district court's\n\nholding that the Bondholders' security interest can be avoided\n\nunder PROMESA. Concerning the district court's dismissal of the\n\nBondholders' second and third counterclaims with prejudice, we\n\nvacate and remand to the district court for further consideration\n\nin light of this opinion. We affirm the district court's dismissal\n\nof the Bondholders' claim regarding the January 2017 Stipulation.\n\nNo costs are awarded.\n\n\n\n\n - 55 -\n[END_CASE]", "role": "user" } ]
4,586,009
Stephen D. KNOX; Jean Knox, Plaintiffs, Appellants, v. METALFORMING, INC., Defendant, Appellant, Schechtl Maschinenbau GmbH, Defendant, Appellee.
MetalForming, Inc. v. Schechtl Maschinenbau Gmbh
2019-01-30
18-1550P
U.S. Court of Appeals for the First Circuit
{"judges": "Lynch, Stahl, Barron", "parties": "", "opinions": [{"author": "LYNCH, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNos. 18-1550\n 18-1551\n\n STEPHEN D. KNOX; JEAN KNOX,\n\n Plaintiffs, Appellants,\n\n v.\n\n METALFORMING, INC.,\n\n Defendant, Appellant,\n\n SCHECHTL MASCHINENBAU GMBH,\n\n Defendant, Appellee.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. George A. O'Toole, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Benjamin R. Zimmermann, with whom Stacey L. Pietrowicz and\nSugarman and Sugarman, P.C. were on brief, for Stephen and Jean\nKnox.\n Javier F. Flores, with whom Eric V. Skelly, Thaddeus M.\nLenkiewicz, and Manning Gross & Massenburg LLP, were on brief, for\nMetalForming, Inc.\n Frederick W. Reif, with whom Marie E. Chafe, Cornell & Gollub,\nDebra Tama, and Wilson Elser Moskowitz Edelman & Dicker, LLP, were\non brief, for Schechtl Maschinenbau GmbH.\n\fJanuary 30, 2019\n\f LYNCH, Circuit Judge. Stephen Knox's hand was badly\n\ninjured at his work at Cape Cod Copper (CCC) in October 2016 when\n\nhe operated a machine that was manufactured by defendant Schechtl\n\nMaschinenbau GmbH, a German company. The machine had been sold to\n\nCCC by defendant MetalForming, Inc., an American company located\n\nin Georgia and Schechtl's U.S. distributor.\n\n The question on appeal is whether there is personal\n\njurisdiction over Schechtl, named as a defendant by Knox and as a\n\ncross-claim defendant by MetalForming. The district court\n\ndismissed the claims against Schechtl, finding that Schechtl had\n\nnot purposefully availed itself of the privilege of doing business\n\nin Massachusetts. Knox v. MetalForming, Inc., 303 F. Supp. 3d\n\n179, 184 (D. Mass. 2018).\n\n We reverse.\n\n I.\n\nA. Background\n\n The district court did not permit jurisdictional\n\ndiscovery. Id. at 187. The following facts are undisputed.\n\n In October 2016, Stephen D. Knox, plaintiff here along\n\nwith his wife, Jean, was injured while using a Schechtl MAX 310,1\n\na motor-driven metal-bending machine. The injury occurred at CCC,\n\n\n\n 1 Although some materials refer to the machine as a\n\"MAX3100 FOLDER,\" the parties refer to it as a \"MAX 310,\" and we\nwill do the same.\n\fKnox's place of employment, located in Lakeville, Massachusetts.\n\nWhen Knox inadvertently hit the foot pedal of CCC's MAX 310, the\n\nmachine activated, crushing his left hand.\n\n Schechtl, the manufacturer of the MAX 310, is\n\nheadquartered in Edling, Germany and maintains no operations in\n\nthe United States. The company's marketing materials say that\n\nSchechtl manufactures the \"most popular architectural sheet metal\n\nfolders in the world.\"\n\n Schechtl sells its machines to United States customers\n\nthrough MetalForming, a separate and independently owned U.S.\n\ndistribution company. Schechtl's distribution agreement (\"the\n\nagreement\") with MetalForming gives MetalForming the exclusive\n\nright to distribute Schechtl's products in the \"Contract\n\nTerritory,\" which comprises Canada, the United States, and Mexico.\n\n The agreement outlines the procedure for selling\n\nSchechtl's machinery. The purchasing end user (\"the purchaser\")\n\nplaces an order with MetalForming, which in turn acquires the\n\nmachine from Schechtl. MetalForming then sends a purchase order,\n\nnaming the purchaser, to Schechtl in Germany. Under the agreement,\n\nMetalForming must include \"technical and other data\" in the\n\npurchase order, because that information is \"of importance for the\n\nordered product, the supply contract, and its performance.\"\n\n Schechtl then chooses whether to accept the purchase\n\norder. If it does accept, it issues a written order confirmation,\n\fwhich \"govern[s] the product to be delivered, its technical\n\nqualities, the delivery price, the place of delivery, the time of\n\ndelivery as well as all other relevant contractual provisions.\"\n\n Schechtl then manufactures the machine to the\n\npurchaser's specifications. The agreement provides that Schechtl\n\n\"reserves the right, in the exercise of its sole discretion, to\n\ndiscontinue the manufacture or distribution of any Product without\n\nincurring any obligation to [MetalForming].\"\n\n When the machine is ready, Schechtl delivers it to a\n\n\"freight forwarder or other transport agency\" in Germany, at which\n\npoint ownership passes to MetalForming. The record does not detail\n\nthe ordinary shipment process after that point, but, as we describe\n\nbelow, it does show how the MAX 310 that injured Knox came to CCC.\n\n Under the agreement, MetalForming is responsible for\n\ninstallation at the purchaser's site and for training the\n\npurchaser's personnel in the proper use of the machine. The\n\nagreement does, however, provide that it may \"become necessary\n\nthat installation work be conducted under the direction of a\"\n\nSchechtl technician. And there is somewhat different information\n\nas to training contained in the information manual, as noted below.\n\n The agreement also requires that MetalForming \"provide\n\nany and all warranty services for the\" Schechtl products. Schechtl\n\nprovides a one-year warranty \"to the end users for all of its\n\nmachines, machine parts, tools, spare parts, and accessories.\"\n\f MetalForming must also, under the agreement, \"pass along\n\nto customers information received from [Schechtl]\" regarding the\n\nproducts and their proper use. This information is packaged in\n\nwith each machine when it is delivered to the purchaser. The\n\nenclosed material includes a declaration that the machine had been\n\n\"developed, designed and manufactured in compliance with\"\n\napplicable European safety directives. It also includes\n\ninstruction manuals and safety instructions for each machine.\n\n The instruction manual includes an \"Instruction for\n\nInquiries and Spare Part Orders,\" which directs purchasers to\n\ncontact Schechtl (and not MetalForming) for inquiries and for\n\nadditional machine parts. A later troubleshooting section of that\n\nmanual also instructs that operators experiencing a problem\n\nshould, \"[i]f it is not possible to correct the malfunction with\n\nthe aid of the following tables, contact the Schechtl Maschinenbau\n\nGmbH Service department.\" It does not instruct the\n\noperator/purchaser to contact MetalForming. The manual also\n\noffers that \"[t]he operating company may receive extensive machine\n\ntraining by Schechtl Maschinenbau GmbH upon request . . . at\n\n[Schechtl's] facilities or at the operating company's facilities.\"\n\nThere is no evidence as to whether any Massachusetts purchaser\n\nmade such a request.\n\n The materials provided to the purchasers of Schechtl\n\nmachines contain Schechtl's direct contact information, including\n\fits phone and fax numbers and its mail and email addresses.\n\nSchechtl also operates a website that instructs purchasers of its\n\nmachines to contact Schechtl directly for frequently asked\n\nquestions, sales, parts, and other information relating to its\n\nmachines. See Schechtl, http://www.schechtl.biz/index_e.htm (last\n\nvisited Jan. 24, 2019).\n\n Schechtl has provided MetalForming with advertising\n\nmaterials to market Schechtl products in the United States.\n\nMetalForming has promoted Schechtl machines in national trade\n\npublications and at industry trade shows. There is no record\n\nevidence as to the Massachusetts recipients of those trade\n\npublications. And while the record shows that Schechtl\n\nrepresentatives attended several trade shows in the United States\n\nwith MetalForming, there is no evidence that any of those shows\n\nwere in Massachusetts.\n\n Between 2000 and September 2017, MetalForming sold 2,639\n\nSchechtl sheet metal machines throughout the United States, at a\n\nvalue of just over $97 million. Between July 2001 and September\n\n2017, MetalForming sold to purchasers in Massachusetts forty-five\n\nSchechtl machines and 234 Schechtl parts, at a value of nearly\n\n$1.5 million (about $1.3 million for the machines and $176,752 for\n\nthe parts). Schechtl's Massachusetts machine sales appear to\n\nconstitute 1.35% of its United States machine sales. The record\n\ndoes not reveal Schechtl's total parts sales in the U.S.\n\f Schechtl sold the MAX 310 which injured Knox to\n\nMetalForming in April 2001. MetalForming took delivery in Georgia.\n\nIn August, four months after the initial sale, MetalForming shipped\n\nthe machine to CCC, with CCC taking ownership of the machine in\n\nGeorgia. The respective purchase orders show that MetalForming\n\npurchased the machine from Schechtl for $25,830 and sold it to CCC\n\nfor $38,950. The purchase order from MetalForming to Schechtl\n\nidentified the purchaser as CCC but did not give CCC's location.\n\nThe purchase order from MetalForming to CCC shows that the machine\n\ncame with a one-year Schechtl warranty and that the price included\n\na \"Schechtl Installation Charge\" and a \"Schechtl Freight Charge\"\n\nto the purchaser, but no party explains what these last two terms\n\nmean or who receives the payment.\n\nB. Procedural History\n\n The Knoxes sued both Schechtl and MetalForming in\n\nMassachusetts state court. They alleged negligence, breach of\n\nwarranty, loss of consortium, and violation of the Massachusetts\n\nconsumer protection statute, Mass. Gen. Laws ch. 93A. MetalForming\n\nremoved the case to Massachusetts federal district court and filed\n\ncrossclaims against Schechtl for indemnification, contribution,\n\nand breach of contract. Schechtl moved to dismiss the claims\n\nagainst it for lack of personal jurisdiction. Both the Knoxes and\n\nMetalForming opposed Schechtl's motion.\n\f The district court, after finding that the terms of\n\nMassachusetts's long-arm statute were \"easily . . . satisfied,\"\n\nKnox, 303 F. Supp. 3d at 183, nonetheless granted Schechtl's motion\n\nto dismiss, id. at 188. The court reasoned that, even though\n\n\"Schechtl ha[d] derived . . . 'substantial revenue' from\n\nMetalForming's sales of Schechtl equipment to Massachusetts\n\ncustomers,\" id. at 186, Schechtl had not purposefully availed\n\nitself of the privilege of doing business in Massachusetts, id. at\n\n187. The court added that there was \"[n]o Massachusetts-specific\n\n'plus' factor,\" like \"'special state-related design, advertising,\n\nadvice, marketing,' etc.\" Id. at 186 (quoting J. McIntyre Mach.,\n\nLtd. v. Nicastro, 564 U.S. 873, 889 (2011) (Breyer, J.,\n\nconcurring)). The court did not mention either the instructions\n\nor the warranties that Schechtl provided to the purchasers in\n\nMassachusetts.\n\n This appeal followed.\n\n II.\n\n The district court held that MetalForming had not made\n\na prima facie showing of personal jurisdiction. See id. at 184.\n\nOn prima facie review, the plaintiffs' burden is to proffer\n\nevidence \"sufficient to support findings of all facts essential to\n\npersonal jurisdiction\" without relying on unsupported allegations.\n\nA Corp. v. All Am. Plumbing, Inc., 812 F.3d 54, 58 (1st Cir. 2016).\n\nWe construe these facts \"in the light most congenial to the\n\fplaintiff's jurisdictional claim.\" Mass. Sch. of Law at Andover,\n\nInc. v. Am. Bar Ass'n, 142 F.3d 26, 34 (1st Cir. 1998). \"Our\n\nreview is de novo.\" LP Sols. LLC v. Duchossois, 907 F.3d 95, 102\n\n(1st Cir. 2018).\n\n In a diversity jurisdiction case like this one, \"a\n\nplaintiff must satisfy both the forum state's long-arm statute and\n\nthe Due Process Clause of the Fourteenth Amendment.\" C.W. Downer\n\n& Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59, 65 (1st Cir.\n\n2014). Compliance with the terms of the Massachusetts long-arm\n\nstatute is not contested here. Schechtl proceeds directly to the\n\nfederal constitutional analysis; we will do so as well.\n\n For the exercise of personal jurisdiction to be\n\nconstitutional, a defendant must have \"certain minimum contacts\n\nwith [the forum state] such that the maintenance of the suit does\n\nnot offend 'traditional notions of fair play and substantial\n\njustice.'\" Int'l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945)\n\n(quoting Milliken v. Meyer, 311 U.S. 457, 463 (1940)). The\n\nconstitutional \"inquiry is highly 'fact-specific.'\" PREP Tours,\n\nInc. v. Am. Youth Soccer Org., No. 17-1223, 2019 WL 126221, at *4\n\n(1st Cir. Jan. 8, 2019) (quoting United Elec., Radio & Mach.\n\nWorkers of Am. v. 163 Pleasant St. Corp., 960 F.2d 1080, 1089 (1st\n\nCir. 1992)). Importantly, the \"test is 'not susceptible of\n\nmechanical application; rather, the facts of each case must be\n\fweighed.'\" Id. (quoting Kulko v. Superior Ct. of Cal., 436 U.S.\n\n84, 92 (1978)).\n\n The Knoxes and MetalForming have asserted specific\n\npersonal jurisdiction over Schechtl, so the constitutional\n\nanalysis here has three components: relatedness, purposeful\n\navailment, and reasonableness. Plixer Int'l, Inc. v. Scrutinizer\n\nGmbH, 905 F.3d 1, 7 (1st Cir. 2018). That is, the plaintiffs must\n\nshow that (1) their claims directly arise out of or relate to the\n\ndefendant's forum activities; (2) the defendant's forum contacts\n\nrepresent a purposeful availment of the privilege of conducting\n\nactivities in that forum, thus invoking the benefits and\n\nprotections of the forum's laws and rendering the defendant's\n\ninvoluntary presence in the forum's courts foreseeable; and\n\n(3) the exercise of jurisdiction is reasonable. Id. The Knoxes\n\nand MetalForming must meet all three requirements to establish\n\npersonal jurisdiction. Id. We hold that they have.\n\n The district court reached only the issue of purposeful\n\navailment. But at oral argument Schechtl's counsel conceded that\n\nthe other two requirements are met. We briefly explain below why\n\nwe agree and address the main issue of purposeful availment.\n\nA. Relatedness\n\n To show relatedness, the Knoxes and MetalForming must\n\ndemonstrate that their \"cause of action either arises directly out\n\nof, or is related to, the defendant's forum-based contacts.\"\n\fHarlow v. Children's Hosp., 432 F.3d 50, 61 (1st Cir. 2005) (citing\n\n163 Pleasant St., 960 F.2d at 1088-89). This \"flexible, relaxed\n\nstandard,\" N. Laminate Sales, Inc. v. Davis, 403 F.3d 14, 25 (1st\n\nCir. 2005) (quoting Pritzker v. Yari, 42 F.3d 53, 61 (1st Cir.\n\n1994)), requires only that the claim have a \"demonstrable nexus\"\n\nto the defendant's forum contacts, Mass. Sch. of Law, 142 F.3d at\n\n34. This requirement is easily met here.\n\nB. Purposeful Availment\n\n The case turns on the purposeful availment prong. To\n\nmeet this requirement, the Knoxes and MetalForming bear the burden\n\nof demonstrating that Schechtl has \"purposefully avail[ed] itself\n\nof the privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Hanson\n\nv. Denckla, 357 U.S. 235, 253 (1958).\n\n The purposeful availment requirement ensures that the\n\nexercise of jurisdiction is essentially voluntary and foreseeable,\n\nC.W. Downer, 771 F.3d at 66, and is not premised on a defendant's\n\n\"random, fortuitous, or attenuated contacts,\" Carreras v. PMG\n\nCollins, LLC, 660 F.3d 549, 555 (1st Cir. 2011) (quoting Burger\n\nKing Corp. v. Rudzewicz, 471 U.S. 462, 475 (1985)). \"[T]he Supreme\n\nCourt has explained that 'the foreseeability that is critical to\n\ndue process analysis . . . is that the defendant's conduct and\n\nconnection with the forum State are such that he should reasonably\n\nanticipate being haled into court there.'\" PREP Tours, 2019 WL\n\f126221, at *6 (quoting Burger King, 471 U.S. at 474). This\n\nrequirement applies equally to foreign defendants. Plixer, 905\n\nF.3d at 7.\n\n Each side asserts that the Supreme Court's decision in\n\nJ. McIntyre Machinery, Limited v. Nicastro supports its view. Like\n\nother circuits, we have held that the narrowest, and thus binding,\n\nopinion from the \"fragmented Court\" in that case was Justice\n\nBreyer's. Plixer, 905 F.3d at 10 (quoting Marks v. United States,\n\n430 U.S. 188, 193 (1977)); accord Williams v. Romarm, SA, 756 F.3d\n\n777, 784 (D.C. Cir. 2014) (finding Justice Breyer's concurring\n\nopinion controlling under Marks); Ainsworth v. Moffett Eng'g,\n\nLtd., 716 F.3d 174, 178 & n.14 (5th Cir. 2013) (same); AFTG-TG,\n\nLLC v. Nuvoton Tech. Corp., 689 F.3d 1358, 1363 (Fed. Cir. 2012)\n\n(same). In the end we do not think that this case, on the facts\n\nhere, fails the personal jurisdiction tests articulated by either\n\nJustice Breyer's concurring opinion or the plurality opinion in\n\nNicastro.\n\n The district court found that Schechtl had not\n\ndesignated Massachusetts \"for special attention\" and had not\n\n\"target[ed] buyers within\" Massachusetts. Knox, 303 F. Supp. 3d\n\nat 186. Using those tests, the district court held that Schechtl\n\nhad not purposefully availed itself of the privilege of conducting\n\fbusiness in the Commonwealth. Id.2 Those, as our Plixer decision\n\nlater made explicit, are not the exclusive tests to establish\n\npurposeful availment.\n\n In Plixer we concluded that \"Supreme Court precedent\n\ndoes not establish specific targeting of a forum as the only means\n\nof showing that the purposeful availment test has been met.\" 905\n\nF.3d at 9 (emphasis added). Depending on the facts, a defendant's\n\n\"'regular flow or regular course of sale' in the [forum]\" could\n\nmake the exercise of jurisdiction foreseeable to the defendant.\n\nId. at 10. And, again depending on the facts, jurisdiction could\n\nbe foreseeable based on \"something more\" than this, evidencing an\n\nintent to serve the forum. Id. (citing Asahi Metal Indus. Co.,\n\nLtd. v. Superior Court of Cal., 480 U.S. 102, 111-12 (1987)\n\n(opinion of O'Connor, J.)). Justice O'Connor's plurality opinion\n\nin Asahi, endorsed by the plurality opinion in Nicastro, see 564\n\nU.S. at 885 (plurality opinion), says that \"something more\" may\n\ninclude, \"for example, designing the product for the market in the\n\nforum State, advertising in the forum State, establishing channels\n\nfor providing regular advice to customers in the forum State, or\n\nmarketing the product through a distributor who has agreed to serve\n\n\n\n\n 2 To be clear, there is no argument that a producer like\nSchechtl is subject to jurisdiction solely because it knows that\nits products might be sold in Massachusetts. See Nicastro, 564\nU.S. at 891 (Breyer, J., concurring) (rejecting such a standard).\n\fas the sales agent in the forum State.\" Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.).\n\n Specific jurisdiction must rest on a defendant's\n\nvoluntary contact with the forum and not on \"the 'unilateral\n\nactivity of another party or a third person.'\" Burger King, 471\n\nU.S. at 475 (quoting Helicopteros Nacionales de Colombia, S.A. v.\n\nHall, 466 U.S. 408, 417 (1984)). The argument for jurisdiction\n\nhere does not rest on MetalForming's Massachusetts activities. It\n\nrests instead on the totality of Schechtl's activities,\n\nvoluntarily undertaken, that connect the German company to\n\nMassachusetts.\n\n These voluntary acts on Schechtl's part led to a \"regular\n\nflow or regular course of sales,\" and more than that, in the\n\nCommonwealth. Over sixteen years, Schechtl, through MetalForming,\n\nsold forty-five machines (an average of close to three machines in\n\neach of those sixteen years). It also provided 234 parts to\n\npurchasers in Massachusetts. Those parts and machines led to\n\nnearly $1.5 million of Massachusetts sales for Schechtl.\n\n We compare this case to Plixer, in which we upheld the\n\nexercise of jurisdiction over a defendant who, over three-and-a-\n\nhalf years, served 156 forum customers, generating about $200,000\n\nin business. See 905 F.3d at 4-5; see also id. at 11 (describing\n\npost-Nicastro rulings upholding the exercise of jurisdiction based\n\non \"a regular course of sales\"). And we compare Schechtl to the\n\fdefendant in Nicastro, who Justice Breyer described as having made\n\n\"a single isolated sale\" into the forum. 564 U.S. at 888 (Breyer,\n\nJ., concurring). Schechtl certainly does not fall into the\n\ncategory of manufacturer, \"small\" in \"shape[] and size[],\"\n\ndescribed by Justice Breyer in Nicastro. Id. at 892 (Breyer, J.,\n\nconcurring).\n\n Schechtl argues that we should discount its\n\nMassachusetts sales because those sales were part of a nationwide\n\nsales effort. But the question is not whether a defendant sells\n\nits product across the U.S.; it is instead whether a defendant's\n\nforum connection is such \"that the exercise of jurisdiction is\n\nessentially voluntary and foreseeable.\" Plixer, 905 F.3d at 7\n\n(citing C.W. Downer, 771 F.3d at 66); see Ainsworth, 716 F.3d at\n\n179 (upholding the exercise of jurisdiction based on substantial\n\nin-forum sales, even though the defendant's forum sales\n\nrepresented only 1.55% of its nationwide sales during the relevant\n\nperiod). And we note that the use of a nationwide distributor\n\ndoes not automatically preclude the exercise of jurisdiction. See\n\nAinsworth, 716 F.3d at 179 (upholding the exercise of jurisdiction\n\nover a manufacturer even though the manufacturer employed a\n\nnationwide distributor).\n\n To be clear, we do not hold that the mere volume of\n\nSchechtl's sales in Massachusetts over sixteen years standing\n\falone would suffice (a hypothetical situation we need not address).\n\nThere is more here.\n\n Schechtl individually approved and manufactured\n\naccording to purchaser-provided specifications each of the nearly\n\nfifty machines it sent to Massachusetts purchasers. See In re\n\nChinese-Manufactured Drywall Prods. Liab. Litig., 742 F.3d 576,\n\n589 (5th Cir. 2014) (upholding the exercise of personal\n\njurisdiction based in part on the defendant's fulfilling product\n\norders on a \"made-to-order basis\"); cf. Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.) (adding that \"designing the product for\n\nthe market in the forum State\" may be \"additional conduct\"\n\nnecessary to make the exercise of jurisdiction constitutional).\n\n Schechtl's relationship with purchasers in Massachusetts\n\ndid not end when Schechtl accepted the purchase order and\n\nmanufactured the machine. Schechtl required that MetalForming\n\ninclude, with each machine, materials that instructed that\n\npurchaser to contact Schechtl directly, whether to purchase\n\nreplacement parts or to obtain assistance with troubleshooting and\n\nfixing problems. From the fact that hundreds of Schechtl parts\n\nwere delivered to Massachusetts, the inference is entirely\n\nplausible that Massachusetts purchasers did use the channels\n\nSchechtl established both as to spare parts and as to\n\ntroubleshooting.\n\f Schechtl's channels to Massachusetts purchasers\n\nconstitute efforts to continue -- and perhaps to expand -- its\n\nrelationship with Massachusetts purchasers. Those deliberately\n\nopened channels, kept open over many years and presumably used,\n\nare relevant to the jurisdictional analysis. See Asahi, 480 U.S.\n\nat 112 (opinion of O'Connor, J.) (noting that \"establishing\n\nchannels for providing regular advice to customers in the forum\n\nState\" may be \"something more\" in support of jurisdiction). Those\n\nchannels established a direct link between Schechtl and its\n\npurchasers. Here that means that Schechtl voluntarily opened at\n\nleast forty-five such direct links with Massachusetts purchasers.\n\nSchechtl's long service of purchasers in Massachusetts through at\n\nleast its spare parts sales bolsters our conclusion that the\n\nexercise of jurisdiction here is foreseeable.3\n\n Purposeful availment analysis \"'will vary with the\n\nquality and the nature of the defendant's activity.'\" PREP Tours,\n\n2019 WL 126221, at *6 (quoting Burger King, 471 U.S. at 474-75).\n\nThis case involves a manufacturer which can direct where its\n\nproducts go, which sold dozens of expensive products into the forum\n\n\n 3 Schechtl argues that it did not know that CCC was located\nin Massachusetts. Even if that contention were correct, we would\nnot consider it dispositive given all the other facts here. We do\nnot comment on MetalForming's argument that Schechtl should have\nknown CCC's location.\n We also do not rest on, or even reach, the argument that\nSchechtl made no effort to exclude Massachusetts purchasers from\nits American market. Cf. Ainsworth, 716 F.3d at 179.\n\fover nearly two decades, and which initiated an ongoing\n\nrelationship with its in-forum purchasers. Nicastro, by contrast,\n\ninvolved a manufacturer which lacked any similar ability to control\n\nthe end location of its products, see 564 U.S. at 878 (plurality\n\nopinion) (noting that there was \"no allegation that the distributor\n\nwas under [the defendant's] control\"), and which had no other\n\nrelationship with the forum, see id. at 886. The defendant there\n\nknew only \"that its products are distributed through a nationwide\n\ndistribution system that might lead to those products being sold\n\nin any of the fifty states.\" Id. at 879 (internal quotation marks\n\nomitted). None of the opinions from Nicastro require that we\n\naccept Schechtl's arguments on appeal.\n\n Schechtl's only remaining argument is that MetalForming\n\ntakes title to the Schechtl products in Germany. First Circuit\n\nlaw has long found this argument irrelevant to the jurisdictional\n\nanalysis. See Benitez-Allende v. Alcan Aluminio do Brasil, S.A.,\n\n857 F.2d 26, 30 (1st Cir. 1988) (Breyer, J.) (\"The fact that title\n\nto the [products] passed in [a foreign country] is beside the\n\npoint, for '[i]f International Shoe stands for anything, however,\n\nit is that a truly interstate business may not shield itself from\n\nsuit by a careful but formalistic structuring of its business\n\ndealings.'\" (quoting Vencedor Mfg. Co., Inc. v. Gougler Indus.,\n\nInc., 557 F.2d 886, 891 (1st Cir. 1977))). The same is true for\n\nan international business.\n\fC. Reasonableness\n\n We explain briefly why we consider the exercise of\n\njurisdiction to be reasonable under the five \"gestalt\" factors:\n\n (1) the defendant's burden of appearing [in\n the forum], (2) the forum state's interest in\n adjudicating the dispute, (3) the plaintiff's\n interest in obtaining convenient and effective\n relief, (4) the judicial system's interest in\n obtaining the most effective resolution of the\n controversy, and (5) the common interests of\n all sovereigns in promoting substantive social\n policies.\n\n\nTicketmaster-N.Y., Inc. v. Alioto, 26 F.3d 201, 209 (1st Cir. 1994)\n\n(citing Burger King, 471 U.S. at 477). Schechtl in its briefs,\n\nbut not at oral argument, argues that Massachusetts litigation\n\nwould be burdensome because it is a German company with German\n\nemployees, and that cross-Atlantic travel and communications would\n\nimpose burdens on its employees. That there is some burden on\n\nSchechtl (which can be mitigated) is not enough on the facts here\n\nto make the exercise of jurisdiction unreasonable. See Plixer,\n\n905 F.3d at 13 (noting that \"'[w]hen minimum contacts have been\n\nestablished, often the interests of the plaintiff and the forum in\n\nthe exercise of jurisdiction will justify even the serious burdens\n\nplaced on the alien defendant'\" (quoting Asahi, 480 U.S. at 114\n\n(opinion of O'Connor, J.)); see also C.W. Downer, 771 F.3d at 70\n\n(noting that many of the case's logistical challenges \"can be\n\nresolved through the use of affidavits and video devices\").\n\f III.\n\n We conclude that the exercise of personal jurisdiction\n\nover Schechtl comports with due process. We reverse and remand\n\nfor further proceedings consistent with this opinion.", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363262/", "author_raw": "LYNCH, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586009/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Stephen D. KNOX; Jean Knox, Plaintiffs, Appellants, v. METALFORMING, INC., Defendant, Appellant, Schechtl Maschinenbau GmbH, Defendant, Appellee.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNos. 18-1550\n 18-1551\n\n STEPHEN D. KNOX; JEAN KNOX,\n\n Plaintiffs, Appellants,\n\n v.\n\n METALFORMING, INC.,\n\n Defendant, Appellant,\n\n SCHECHTL MASCHINENBAU GMBH,\n\n Defendant, Appellee.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. George A. O'Toole, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Benjamin R. Zimmermann, with whom Stacey L. Pietrowicz and\nSugarman and Sugarman, P.C. were on brief, for Stephen and Jean\nKnox.\n Javier F. Flores, with whom Eric V. Skelly, Thaddeus M.\nLenkiewicz, and Manning Gross & Massenburg LLP, were on brief, for\nMetalForming, Inc.\n Frederick W. Reif, with whom Marie E. Chafe, Cornell & Gollub,\nDebra Tama, and Wilson Elser Moskowitz Edelman & Dicker, LLP, were\non brief, for Schechtl Maschinenbau GmbH.\n\fJanuary 30, 2019\n\f LYNCH, Circuit Judge. Stephen Knox's hand was badly\n\ninjured at his work at Cape Cod Copper (CCC) in October 2016 when\n\nhe operated a machine that was manufactured by defendant Schechtl\n\nMaschinenbau GmbH, a German company. The machine had been sold to\n\nCCC by defendant MetalForming, Inc., an American company located\n\nin Georgia and Schechtl's U.S. distributor.\n\n The question on appeal is whether there is personal\n\njurisdiction over Schechtl, named as a defendant by Knox and as a\n\ncross-claim defendant by MetalForming. The district court\n\ndismissed the claims against Schechtl, finding that Schechtl had\n\nnot purposefully availed itself of the privilege of doing business\n\nin Massachusetts. Knox v. MetalForming, Inc., 303 F. Supp. 3d\n\n179, 184 (D. Mass. 2018).\n\n We reverse.\n\n I.\n\nA. Background\n\n The district court did not permit jurisdictional\n\ndiscovery. Id. at 187. The following facts are undisputed.\n\n In October 2016, Stephen D. Knox, plaintiff here along\n\nwith his wife, Jean, was injured while using a Schechtl MAX 310,1\n\na motor-driven metal-bending machine. The injury occurred at CCC,\n\n\n\n 1 Although some materials refer to the machine as a\n\"MAX3100 FOLDER,\" the parties refer to it as a \"MAX 310,\" and we\nwill do the same.\n\fKnox's place of employment, located in Lakeville, Massachusetts.\n\nWhen Knox inadvertently hit the foot pedal of CCC's MAX 310, the\n\nmachine activated, crushing his left hand.\n\n Schechtl, the manufacturer of the MAX 310, is\n\nheadquartered in Edling, Germany and maintains no operations in\n\nthe United States. The company's marketing materials say that\n\nSchechtl manufactures the \"most popular architectural sheet metal\n\nfolders in the world.\"\n\n Schechtl sells its machines to United States customers\n\nthrough MetalForming, a separate and independently owned U.S.\n\ndistribution company. Schechtl's distribution agreement (\"the\n\nagreement\") with MetalForming gives MetalForming the exclusive\n\nright to distribute Schechtl's products in the \"Contract\n\nTerritory,\" which comprises Canada, the United States, and Mexico.\n\n The agreement outlines the procedure for selling\n\nSchechtl's machinery. The purchasing end user (\"the purchaser\")\n\nplaces an order with MetalForming, which in turn acquires the\n\nmachine from Schechtl. MetalForming then sends a purchase order,\n\nnaming the purchaser, to Schechtl in Germany. Under the agreement,\n\nMetalForming must include \"technical and other data\" in the\n\npurchase order, because that information is \"of importance for the\n\nordered product, the supply contract, and its performance.\"\n\n Schechtl then chooses whether to accept the purchase\n\norder. If it does accept, it issues a written order confirmation,\n\fwhich \"govern[s] the product to be delivered, its technical\n\nqualities, the delivery price, the place of delivery, the time of\n\ndelivery as well as all other relevant contractual provisions.\"\n\n Schechtl then manufactures the machine to the\n\npurchaser's specifications. The agreement provides that Schechtl\n\n\"reserves the right, in the exercise of its sole discretion, to\n\ndiscontinue the manufacture or distribution of any Product without\n\nincurring any obligation to [MetalForming].\"\n\n When the machine is ready, Schechtl delivers it to a\n\n\"freight forwarder or other transport agency\" in Germany, at which\n\npoint ownership passes to MetalForming. The record does not detail\n\nthe ordinary shipment process after that point, but, as we describe\n\nbelow, it does show how the MAX 310 that injured Knox came to CCC.\n\n Under the agreement, MetalForming is responsible for\n\ninstallation at the purchaser's site and for training the\n\npurchaser's personnel in the proper use of the machine. The\n\nagreement does, however, provide that it may \"become necessary\n\nthat installation work be conducted under the direction of a\"\n\nSchechtl technician. And there is somewhat different information\n\nas to training contained in the information manual, as noted below.\n\n The agreement also requires that MetalForming \"provide\n\nany and all warranty services for the\" Schechtl products. Schechtl\n\nprovides a one-year warranty \"to the end users for all of its\n\nmachines, machine parts, tools, spare parts, and accessories.\"\n\f MetalForming must also, under the agreement, \"pass along\n\nto customers information received from [Schechtl]\" regarding the\n\nproducts and their proper use. This information is packaged in\n\nwith each machine when it is delivered to the purchaser. The\n\nenclosed material includes a declaration that the machine had been\n\n\"developed, designed and manufactured in compliance with\"\n\napplicable European safety directives. It also includes\n\ninstruction manuals and safety instructions for each machine.\n\n The instruction manual includes an \"Instruction for\n\nInquiries and Spare Part Orders,\" which directs purchasers to\n\ncontact Schechtl (and not MetalForming) for inquiries and for\n\nadditional machine parts. A later troubleshooting section of that\n\nmanual also instructs that operators experiencing a problem\n\nshould, \"[i]f it is not possible to correct the malfunction with\n\nthe aid of the following tables, contact the Schechtl Maschinenbau\n\nGmbH Service department.\" It does not instruct the\n\noperator/purchaser to contact MetalForming. The manual also\n\noffers that \"[t]he operating company may receive extensive machine\n\ntraining by Schechtl Maschinenbau GmbH upon request . . . at\n\n[Schechtl's] facilities or at the operating company's facilities.\"\n\nThere is no evidence as to whether any Massachusetts purchaser\n\nmade such a request.\n\n The materials provided to the purchasers of Schechtl\n\nmachines contain Schechtl's direct contact information, including\n\fits phone and fax numbers and its mail and email addresses.\n\nSchechtl also operates a website that instructs purchasers of its\n\nmachines to contact Schechtl directly for frequently asked\n\nquestions, sales, parts, and other information relating to its\n\nmachines. See Schechtl, http://www.schechtl.biz/index_e.htm (last\n\nvisited Jan. 24, 2019).\n\n Schechtl has provided MetalForming with advertising\n\nmaterials to market Schechtl products in the United States.\n\nMetalForming has promoted Schechtl machines in national trade\n\npublications and at industry trade shows. There is no record\n\nevidence as to the Massachusetts recipients of those trade\n\npublications. And while the record shows that Schechtl\n\nrepresentatives attended several trade shows in the United States\n\nwith MetalForming, there is no evidence that any of those shows\n\nwere in Massachusetts.\n\n Between 2000 and September 2017, MetalForming sold 2,639\n\nSchechtl sheet metal machines throughout the United States, at a\n\nvalue of just over $97 million. Between July 2001 and September\n\n2017, MetalForming sold to purchasers in Massachusetts forty-five\n\nSchechtl machines and 234 Schechtl parts, at a value of nearly\n\n$1.5 million (about $1.3 million for the machines and $176,752 for\n\nthe parts). Schechtl's Massachusetts machine sales appear to\n\nconstitute 1.35% of its United States machine sales. The record\n\ndoes not reveal Schechtl's total parts sales in the U.S.\n\f Schechtl sold the MAX 310 which injured Knox to\n\nMetalForming in April 2001. MetalForming took delivery in Georgia.\n\nIn August, four months after the initial sale, MetalForming shipped\n\nthe machine to CCC, with CCC taking ownership of the machine in\n\nGeorgia. The respective purchase orders show that MetalForming\n\npurchased the machine from Schechtl for $25,830 and sold it to CCC\n\nfor $38,950. The purchase order from MetalForming to Schechtl\n\nidentified the purchaser as CCC but did not give CCC's location.\n\nThe purchase order from MetalForming to CCC shows that the machine\n\ncame with a one-year Schechtl warranty and that the price included\n\na \"Schechtl Installation Charge\" and a \"Schechtl Freight Charge\"\n\nto the purchaser, but no party explains what these last two terms\n\nmean or who receives the payment.\n\nB. Procedural History\n\n The Knoxes sued both Schechtl and MetalForming in\n\nMassachusetts state court. They alleged negligence, breach of\n\nwarranty, loss of consortium, and violation of the Massachusetts\n\nconsumer protection statute, Mass. Gen. Laws ch. 93A. MetalForming\n\nremoved the case to Massachusetts federal district court and filed\n\ncrossclaims against Schechtl for indemnification, contribution,\n\nand breach of contract. Schechtl moved to dismiss the claims\n\nagainst it for lack of personal jurisdiction. Both the Knoxes and\n\nMetalForming opposed Schechtl's motion.\n\f The district court, after finding that the terms of\n\nMassachusetts's long-arm statute were \"easily . . . satisfied,\"\n\nKnox, 303 F. Supp. 3d at 183, nonetheless granted Schechtl's motion\n\nto dismiss, id. at 188. The court reasoned that, even though\n\n\"Schechtl ha[d] derived . . . 'substantial revenue' from\n\nMetalForming's sales of Schechtl equipment to Massachusetts\n\ncustomers,\" id. at 186, Schechtl had not purposefully availed\n\nitself of the privilege of doing business in Massachusetts, id. at\n\n187. The court added that there was \"[n]o Massachusetts-specific\n\n'plus' factor,\" like \"'special state-related design, advertising,\n\nadvice, marketing,' etc.\" Id. at 186 (quoting J. McIntyre Mach.,\n\nLtd. v. Nicastro, 564 U.S. 873, 889 (2011) (Breyer, J.,\n\nconcurring)). The court did not mention either the instructions\n\nor the warranties that Schechtl provided to the purchasers in\n\nMassachusetts.\n\n This appeal followed.\n\n II.\n\n The district court held that MetalForming had not made\n\na prima facie showing of personal jurisdiction. See id. at 184.\n\nOn prima facie review, the plaintiffs' burden is to proffer\n\nevidence \"sufficient to support findings of all facts essential to\n\npersonal jurisdiction\" without relying on unsupported allegations.\n\nA Corp. v. All Am. Plumbing, Inc., 812 F.3d 54, 58 (1st Cir. 2016).\n\nWe construe these facts \"in the light most congenial to the\n\fplaintiff's jurisdictional claim.\" Mass. Sch. of Law at Andover,\n\nInc. v. Am. Bar Ass'n, 142 F.3d 26, 34 (1st Cir. 1998). \"Our\n\nreview is de novo.\" LP Sols. LLC v. Duchossois, 907 F.3d 95, 102\n\n(1st Cir. 2018).\n\n In a diversity jurisdiction case like this one, \"a\n\nplaintiff must satisfy both the forum state's long-arm statute and\n\nthe Due Process Clause of the Fourteenth Amendment.\" C.W. Downer\n\n& Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59, 65 (1st Cir.\n\n2014). Compliance with the terms of the Massachusetts long-arm\n\nstatute is not contested here. Schechtl proceeds directly to the\n\nfederal constitutional analysis; we will do so as well.\n\n For the exercise of personal jurisdiction to be\n\nconstitutional, a defendant must have \"certain minimum contacts\n\nwith [the forum state] such that the maintenance of the suit does\n\nnot offend 'traditional notions of fair play and substantial\n\njustice.'\" Int'l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945)\n\n(quoting Milliken v. Meyer, 311 U.S. 457, 463 (1940)). The\n\nconstitutional \"inquiry is highly 'fact-specific.'\" PREP Tours,\n\nInc. v. Am. Youth Soccer Org., No. 17-1223, 2019 WL 126221, at *4\n\n(1st Cir. Jan. 8, 2019) (quoting United Elec., Radio & Mach.\n\nWorkers of Am. v. 163 Pleasant St. Corp., 960 F.2d 1080, 1089 (1st\n\nCir. 1992)). Importantly, the \"test is 'not susceptible of\n\nmechanical application; rather, the facts of each case must be\n\fweighed.'\" Id. (quoting Kulko v. Superior Ct. of Cal., 436 U.S.\n\n84, 92 (1978)).\n\n The Knoxes and MetalForming have asserted specific\n\npersonal jurisdiction over Schechtl, so the constitutional\n\nanalysis here has three components: relatedness, purposeful\n\navailment, and reasonableness. Plixer Int'l, Inc. v. Scrutinizer\n\nGmbH, 905 F.3d 1, 7 (1st Cir. 2018). That is, the plaintiffs must\n\nshow that (1) their claims directly arise out of or relate to the\n\ndefendant's forum activities; (2) the defendant's forum contacts\n\nrepresent a purposeful availment of the privilege of conducting\n\nactivities in that forum, thus invoking the benefits and\n\nprotections of the forum's laws and rendering the defendant's\n\ninvoluntary presence in the forum's courts foreseeable; and\n\n(3) the exercise of jurisdiction is reasonable. Id. The Knoxes\n\nand MetalForming must meet all three requirements to establish\n\npersonal jurisdiction. Id. We hold that they have.\n\n The district court reached only the issue of purposeful\n\navailment. But at oral argument Schechtl's counsel conceded that\n\nthe other two requirements are met. We briefly explain below why\n\nwe agree and address the main issue of purposeful availment.\n\nA. Relatedness\n\n To show relatedness, the Knoxes and MetalForming must\n\ndemonstrate that their \"cause of action either arises directly out\n\nof, or is related to, the defendant's forum-based contacts.\"\n\fHarlow v. Children's Hosp., 432 F.3d 50, 61 (1st Cir. 2005) (citing\n\n163 Pleasant St., 960 F.2d at 1088-89). This \"flexible, relaxed\n\nstandard,\" N. Laminate Sales, Inc. v. Davis, 403 F.3d 14, 25 (1st\n\nCir. 2005) (quoting Pritzker v. Yari, 42 F.3d 53, 61 (1st Cir.\n\n1994)), requires only that the claim have a \"demonstrable nexus\"\n\nto the defendant's forum contacts, Mass. Sch. of Law, 142 F.3d at\n\n34. This requirement is easily met here.\n\nB. Purposeful Availment\n\n The case turns on the purposeful availment prong. To\n\nmeet this requirement, the Knoxes and MetalForming bear the burden\n\nof demonstrating that Schechtl has \"purposefully avail[ed] itself\n\nof the privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Hanson\n\nv. Denckla, 357 U.S. 235, 253 (1958).\n\n The purposeful availment requirement ensures that the\n\nexercise of jurisdiction is essentially voluntary and foreseeable,\n\nC.W. Downer, 771 F.3d at 66, and is not premised on a defendant's\n\n\"random, fortuitous, or attenuated contacts,\" Carreras v. PMG\n\nCollins, LLC, 660 F.3d 549, 555 (1st Cir. 2011) (quoting Burger\n\nKing Corp. v. Rudzewicz, 471 U.S. 462, 475 (1985)). \"[T]he Supreme\n\nCourt has explained that 'the foreseeability that is critical to\n\ndue process analysis . . . is that the defendant's conduct and\n\nconnection with the forum State are such that he should reasonably\n\nanticipate being haled into court there.'\" PREP Tours, 2019 WL\n\f126221, at *6 (quoting Burger King, 471 U.S. at 474). This\n\nrequirement applies equally to foreign defendants. Plixer, 905\n\nF.3d at 7.\n\n Each side asserts that the Supreme Court's decision in\n\nJ. McIntyre Machinery, Limited v. Nicastro supports its view. Like\n\nother circuits, we have held that the narrowest, and thus binding,\n\nopinion from the \"fragmented Court\" in that case was Justice\n\nBreyer's. Plixer, 905 F.3d at 10 (quoting Marks v. United States,\n\n430 U.S. 188, 193 (1977)); accord Williams v. Romarm, SA, 756 F.3d\n\n777, 784 (D.C. Cir. 2014) (finding Justice Breyer's concurring\n\nopinion controlling under Marks); Ainsworth v. Moffett Eng'g,\n\nLtd., 716 F.3d 174, 178 & n.14 (5th Cir. 2013) (same); AFTG-TG,\n\nLLC v. Nuvoton Tech. Corp., 689 F.3d 1358, 1363 (Fed. Cir. 2012)\n\n(same). In the end we do not think that this case, on the facts\n\nhere, fails the personal jurisdiction tests articulated by either\n\nJustice Breyer's concurring opinion or the plurality opinion in\n\nNicastro.\n\n The district court found that Schechtl had not\n\ndesignated Massachusetts \"for special attention\" and had not\n\n\"target[ed] buyers within\" Massachusetts. Knox, 303 F. Supp. 3d\n\nat 186. Using those tests, the district court held that Schechtl\n\nhad not purposefully availed itself of the privilege of conducting\n\fbusiness in the Commonwealth. Id.2 Those, as our Plixer decision\n\nlater made explicit, are not the exclusive tests to establish\n\npurposeful availment.\n\n In Plixer we concluded that \"Supreme Court precedent\n\ndoes not establish specific targeting of a forum as the only means\n\nof showing that the purposeful availment test has been met.\" 905\n\nF.3d at 9 (emphasis added). Depending on the facts, a defendant's\n\n\"'regular flow or regular course of sale' in the [forum]\" could\n\nmake the exercise of jurisdiction foreseeable to the defendant.\n\nId. at 10. And, again depending on the facts, jurisdiction could\n\nbe foreseeable based on \"something more\" than this, evidencing an\n\nintent to serve the forum. Id. (citing Asahi Metal Indus. Co.,\n\nLtd. v. Superior Court of Cal., 480 U.S. 102, 111-12 (1987)\n\n(opinion of O'Connor, J.)). Justice O'Connor's plurality opinion\n\nin Asahi, endorsed by the plurality opinion in Nicastro, see 564\n\nU.S. at 885 (plurality opinion), says that \"something more\" may\n\ninclude, \"for example, designing the product for the market in the\n\nforum State, advertising in the forum State, establishing channels\n\nfor providing regular advice to customers in the forum State, or\n\nmarketing the product through a distributor who has agreed to serve\n\n\n\n\n 2 To be clear, there is no argument that a producer like\nSchechtl is subject to jurisdiction solely because it knows that\nits products might be sold in Massachusetts. See Nicastro, 564\nU.S. at 891 (Breyer, J., concurring) (rejecting such a standard).\n\fas the sales agent in the forum State.\" Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.).\n\n Specific jurisdiction must rest on a defendant's\n\nvoluntary contact with the forum and not on \"the 'unilateral\n\nactivity of another party or a third person.'\" Burger King, 471\n\nU.S. at 475 (quoting Helicopteros Nacionales de Colombia, S.A. v.\n\nHall, 466 U.S. 408, 417 (1984)). The argument for jurisdiction\n\nhere does not rest on MetalForming's Massachusetts activities. It\n\nrests instead on the totality of Schechtl's activities,\n\nvoluntarily undertaken, that connect the German company to\n\nMassachusetts.\n\n These voluntary acts on Schechtl's part led to a \"regular\n\nflow or regular course of sales,\" and more than that, in the\n\nCommonwealth. Over sixteen years, Schechtl, through MetalForming,\n\nsold forty-five machines (an average of close to three machines in\n\neach of those sixteen years). It also provided 234 parts to\n\npurchasers in Massachusetts. Those parts and machines led to\n\nnearly $1.5 million of Massachusetts sales for Schechtl.\n\n We compare this case to Plixer, in which we upheld the\n\nexercise of jurisdiction over a defendant who, over three-and-a-\n\nhalf years, served 156 forum customers, generating about $200,000\n\nin business. See 905 F.3d at 4-5; see also id. at 11 (describing\n\npost-Nicastro rulings upholding the exercise of jurisdiction based\n\non \"a regular course of sales\"). And we compare Schechtl to the\n\fdefendant in Nicastro, who Justice Breyer described as having made\n\n\"a single isolated sale\" into the forum. 564 U.S. at 888 (Breyer,\n\nJ., concurring). Schechtl certainly does not fall into the\n\ncategory of manufacturer, \"small\" in \"shape[] and size[],\"\n\ndescribed by Justice Breyer in Nicastro. Id. at 892 (Breyer, J.,\n\nconcurring).\n\n Schechtl argues that we should discount its\n\nMassachusetts sales because those sales were part of a nationwide\n\nsales effort. But the question is not whether a defendant sells\n\nits product across the U.S.; it is instead whether a defendant's\n\nforum connection is such \"that the exercise of jurisdiction is\n\nessentially voluntary and foreseeable.\" Plixer, 905 F.3d at 7\n\n(citing C.W. Downer, 771 F.3d at 66); see Ainsworth, 716 F.3d at\n\n179 (upholding the exercise of jurisdiction based on substantial\n\nin-forum sales, even though the defendant's forum sales\n\nrepresented only 1.55% of its nationwide sales during the relevant\n\nperiod). And we note that the use of a nationwide distributor\n\ndoes not automatically preclude the exercise of jurisdiction. See\n\nAinsworth, 716 F.3d at 179 (upholding the exercise of jurisdiction\n\nover a manufacturer even though the manufacturer employed a\n\nnationwide distributor).\n\n To be clear, we do not hold that the mere volume of\n\nSchechtl's sales in Massachusetts over sixteen years standing\n\falone would suffice (a hypothetical situation we need not address).\n\nThere is more here.\n\n Schechtl individually approved and manufactured\n\naccording to purchaser-provided specifications each of the nearly\n\nfifty machines it sent to Massachusetts purchasers. See In re\n\nChinese-Manufactured Drywall Prods. Liab. Litig., 742 F.3d 576,\n\n589 (5th Cir. 2014) (upholding the exercise of personal\n\njurisdiction based in part on the defendant's fulfilling product\n\norders on a \"made-to-order basis\"); cf. Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.) (adding that \"designing the product for\n\nthe market in the forum State\" may be \"additional conduct\"\n\nnecessary to make the exercise of jurisdiction constitutional).\n\n Schechtl's relationship with purchasers in Massachusetts\n\ndid not end when Schechtl accepted the purchase order and\n\nmanufactured the machine. Schechtl required that MetalForming\n\ninclude, with each machine, materials that instructed that\n\npurchaser to contact Schechtl directly, whether to purchase\n\nreplacement parts or to obtain assistance with troubleshooting and\n\nfixing problems. From the fact that hundreds of Schechtl parts\n\nwere delivered to Massachusetts, the inference is entirely\n\nplausible that Massachusetts purchasers did use the channels\n\nSchechtl established both as to spare parts and as to\n\ntroubleshooting.\n\f Schechtl's channels to Massachusetts purchasers\n\nconstitute efforts to continue -- and perhaps to expand -- its\n\nrelationship with Massachusetts purchasers. Those deliberately\n\nopened channels, kept open over many years and presumably used,\n\nare relevant to the jurisdictional analysis. See Asahi, 480 U.S.\n\nat 112 (opinion of O'Connor, J.) (noting that \"establishing\n\nchannels for providing regular advice to customers in the forum\n\nState\" may be \"something more\" in support of jurisdiction). Those\n\nchannels established a direct link between Schechtl and its\n\npurchasers. Here that means that Schechtl voluntarily opened at\n\nleast forty-five such direct links with Massachusetts purchasers.\n\nSchechtl's long service of purchasers in Massachusetts through at\n\nleast its spare parts sales bolsters our conclusion that the\n\nexercise of jurisdiction here is foreseeable.3\n\n Purposeful availment analysis \"'will vary with the\n\nquality and the nature of the defendant's activity.'\" PREP Tours,\n\n2019 WL 126221, at *6 (quoting Burger King, 471 U.S. at 474-75).\n\nThis case involves a manufacturer which can direct where its\n\nproducts go, which sold dozens of expensive products into the forum\n\n\n 3 Schechtl argues that it did not know that CCC was located\nin Massachusetts. Even if that contention were correct, we would\nnot consider it dispositive given all the other facts here. We do\nnot comment on MetalForming's argument that Schechtl should have\nknown CCC's location.\n We also do not rest on, or even reach, the argument that\nSchechtl made no effort to exclude Massachusetts purchasers from\nits American market. Cf. Ainsworth, 716 F.3d at 179.\n\fover nearly two decades, and which initiated an ongoing\n\nrelationship with its in-forum purchasers. Nicastro, by contrast,\n\ninvolved a manufacturer which lacked any similar ability to control\n\nthe end location of its products, see 564 U.S. at 878 (plurality\n\nopinion) (noting that there was \"no allegation that the distributor\n\nwas under [the defendant's] control\"), and which had no other\n\nrelationship with the forum, see id. at 886. The defendant there\n\nknew only \"that its products are distributed through a nationwide\n\ndistribution system that might lead to those products being sold\n\nin any of the fifty states.\" Id. at 879 (internal quotation marks\n\nomitted). None of the opinions from Nicastro require that we\n\naccept Schechtl's arguments on appeal.\n\n Schechtl's only remaining argument is that MetalForming\n\ntakes title to the Schechtl products in Germany. First Circuit\n\nlaw has long found this argument irrelevant to the jurisdictional\n\nanalysis. See Benitez-Allende v. Alcan Aluminio do Brasil, S.A.,\n\n857 F.2d 26, 30 (1st Cir. 1988) (Breyer, J.) (\"The fact that title\n\nto the [products] passed in [a foreign country] is beside the\n\npoint, for '[i]f International Shoe stands for anything, however,\n\nit is that a truly interstate business may not shield itself from\n\nsuit by a careful but formalistic structuring of its business\n\ndealings.'\" (quoting Vencedor Mfg. Co., Inc. v. Gougler Indus.,\n\nInc., 557 F.2d 886, 891 (1st Cir. 1977))). The same is true for\n\nan international business.\n\fC. Reasonableness\n\n We explain briefly why we consider the exercise of\n\njurisdiction to be reasonable under the five \"gestalt\" factors:\n\n (1) the defendant's burden of appearing [in\n the forum], (2) the forum state's interest in\n adjudicating the dispute, (3) the plaintiff's\n interest in obtaining convenient and effective\n relief, (4) the judicial system's interest in\n obtaining the most effective resolution of the\n controversy, and (5) the common interests of\n all sovereigns in promoting substantive social\n policies.\n\n\nTicketmaster-N.Y., Inc. v. Alioto, 26 F.3d 201, 209 (1st Cir. 1994)\n\n(citing Burger King, 471 U.S. at 477). Schechtl in its briefs,\n\nbut not at oral argument, argues that Massachusetts litigation\n\nwould be burdensome because it is a German company with German\n\nemployees, and that cross-Atlantic travel and communications would\n\nimpose burdens on its employees. That there is some burden on\n\nSchechtl (which can be mitigated) is not enough on the facts here\n\nto make the exercise of jurisdiction unreasonable. See Plixer,\n\n905 F.3d at 13 (noting that \"'[w]hen minimum contacts have been\n\nestablished, often the interests of the plaintiff and the forum in\n\nthe exercise of jurisdiction will justify even the serious burdens\n\nplaced on the alien defendant'\" (quoting Asahi, 480 U.S. at 114\n\n(opinion of O'Connor, J.)); see also C.W. Downer, 771 F.3d at 70\n\n(noting that many of the case's logistical challenges \"can be\n\nresolved through the use of affidavits and video devices\").\n\f III.\n\n We conclude that the exercise of personal jurisdiction\n\nover Schechtl comports with due process. We reverse and remand\n\nfor further proceedings consistent with this opinion.\n[END_CASE]", "role": "user" } ]
4,586,550
Painters and Allied Trades v. Forest Pharmaceuticals, Inc.
2019-01-30
18-1146P
U.S. Court of Appeals for the First Circuit
{"judges": "Before Howard, Chief Judge, Torruella and Kayatta, Circuit Judges.", "parties": "", "opinions": [{"author": "KAYATTA, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\nNos. 18-1146, 18-1147\n\n IN RE: CELEXA AND LEXAPRO MARKETING AND\n SALES PRACTICES LITIGATION\n\n\nPAINTERS AND ALLIED TRADES DISTRICT COUNCIL 82 HEALTH CARE FUND;\n DELANA S. KIOSSOVSKI; RENEE RAMIREZ, on behalf of herself and\n all others similarly situated; MARLENE T. LOCONTE,\n\n Plaintiffs, Appellants,\n\n MARTHA PALUMBO, individually and on behalf of all other persons\nsimilarly situated; PETER PALUMBO, individually and on behalf of\n all other persons similarly situated; JAYNE EHRLICH,\n individually and on behalf of all other persons similarly\n situated; ANNA MURRET, individually and on behalf of all other\n persons similarly situated; UNIVERSAL CARE, INC.; ANGELA\n JAECKEL; MELVIN M. FULLMER, on behalf of himself and all others\n similarly situated; NEW MEXICO UFCW UNION'S AND EMPLOYER'S\n HEALTH AND WELFARE TRUST FUND, on behalf of itself and all\n others similarly situated; ALLIED SERVICES DIVISION WELFARE\n FUND, on behalf of itself and all others similarly situated;\n TARA JOHNDROW, individually and on behalf of all others\n similarly situated; BRIAN ANSON, individually and on behalf of\n all others similarly situated; SCOTT A. WILCOX, on behalf of\nhimself and all others similarly situated; MUNICIPAL REINSURANCE\nHEALTH INSURANCE FUND; RANDY MARCUS; BONNIE MARCUS; RUTH DUNHAM;\n TANYA SHIPPY; JILL POWELL,\n\n Plaintiffs,\n\n v.\n\n FOREST PHARMACEUTICALS, INC.; FOREST LABORATORIES, INC.; FOREST\nLABORATORIES, LLC, successor in interest to Forest Laboratories,\n Inc.,\n\n Defendants, Appellees,\n\n PFIZER, INC.; WARNER LAMBERT COMPANY,\n\f Defendants.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n R. Brent Wisner, with whom Michael L. Baum, Baum, Hedlund,\nAristei & Goldman, P.C., Christopher L. Coffin, and Pendley, Baudin\n& Coffin, LLP were on brief, for appellants.\n Andrew J. Ceresney, with whom Edwin G. Shallert, Kristin D.\nKiehn, J. Robert Abraham, Debevoise & Plimpton LLP, John G.\nO'Neill, and Sugarman, Rogers, Barshak & Cohen, P.C. were on brief,\nfor appellees.\n\n\n January 30, 2019\n\f KAYATTA, Circuit Judge. These consolidated appeals\n\narise out of two so-called \"off-label\" prescription-drug-marketing\n\ncases aggregated for pretrial proceedings in the District of\n\nMassachusetts by order of the multidistrict litigation panel.\n\nPlaintiffs claim that the defendants, Forest Pharmaceuticals, Inc.\n\nand Forest Laboratories, Inc. (collectively \"Forest\"), engaged in\n\nfraud to push their antidepressant drugs on unsuspecting minors\n\nfor whom the FDA had not approved the use of these medications.\n\nAs we will explain, we reverse the dismissal of the claims brought\n\nby two of the four plaintiffs, and we vacate the denial of\n\nplaintiffs' motion to compel the production of additional\n\ndocuments by Forest. We otherwise affirm the challenged district-\n\ncourt rulings, including the denial of class certification.\n\n I.\n\n We begin by summarizing the relevant statutory and\n\nregulatory framework and by reciting the facts relevant to the\n\nplaintiffs' summary-judgment appeal in the light most favorable to\n\nthe plaintiffs. See Boudreau v. Lussier, 901 F.3d 65, 71 (1st\n\nCir. 2018).\n\n A.\n\n The Federal Food, Drug, and Cosmetic Act (\"FDCA\")\n\nrequires drug manufacturers to obtain approval from the U.S. Food\n\nand Drug Administration (\"FDA\") before marketing a drug for a\n\nparticular medical use. 21 U.S.C. § 355(a); see also Mut. Pharm.\n\n - 3 -\n\fCo., Inc. v. Bartlett, 570 U.S. 472, 476 (2013). To secure that\n\napproval, the drug manufacturer must submit to the FDA either a\n\nnew-drug application (\"NDA\") or a supplemental new-drug\n\napplication (\"sNDA\"), and the manufacturer must demonstrate the\n\ndrug's efficacy for the indicated use in at least two double-\n\nblind, randomized-controlled trials (\"DBRCTs\"). See In re\n\nNeurontin Mktg. & Sales Practices Litig. (Kaiser), No. 04-cv-\n\n10739-PBS, 2011 WL 3852254, at *5 (D. Mass. Aug. 31, 2011), aff'd,\n\n712 F.3d 21 (1st. Cir. 2013); see generally 21 C.F.R. § 314.105.\n\nThe FDCA creates both civil and criminal penalties for drug\n\nmanufacturers that promote the use of approved drugs for unapproved\n\nuses (referred to here as \"off-label\" uses). See 21 U.S.C.\n\n§§ 331(d), 333(a), 355(a); Lawton ex rel. United States v. Takeda\n\nPharm. Co., 842 F.3d 125, 128 n.4 (1st Cir. 2016). The FDCA,\n\nhowever, does not prohibit doctors from prescribing drugs for off-\n\nlabel uses. Lawton ex rel. United States, 842 F.3d at 128 n.4.\n\n B.\n\n Forest manufactures and markets prescription drugs,\n\nincluding the antidepressant medications Celexa and Lexapro.\n\nCelexa and Lexapro are chemically similar selective serotonin\n\nreuptake inhibitors (\"SSRIs\"), a class of antidepressants that\n\naffect a patient's mood by blocking the reabsorption of the\n\nneurotransmitter serotonin in the brain, Eli Lilly & Co. v. Teva\n\nPharm. USA, Inc., No. 05-1044, 2005 WL 1635262, at *1 (Fed. Cir.\n\n - 4 -\n\fJuly 13, 2005). The FDA approved Celexa and Lexapro for the\n\ntreatment of major depressive disorder (\"MDD\") in adults (i.e.,\n\nindividuals aged eighteen or over) in 1998 and 2002, respectively.\n\nDrug manufacturers, including Forest, had difficulty demonstrating\n\nthat SSRIs were also effective in treating depression in children\n\nand adolescents. As of 2005, only Fluoxetine -- commercially known\n\nas Prozac -- had gained FDA approval for the treatment of pediatric\n\ndepression. In 2009, the FDA approved Lexapro for the treatment\n\nof depression in adolescents (i.e., individuals of ages twelve\n\nthrough seventeen). The FDA has never approved Celexa for any\n\npediatric use nor has it approved Lexapro as a treatment for\n\ndepression in children (i.e., individuals under the age of twelve).\n\n The record in this case nevertheless strongly suggests\n\nthat Forest engaged in a comprehensive off-label marketing scheme\n\nfrom 1998 through 2009 aimed at fraudulently inducing doctors to\n\nwrite pediatric prescriptions of Celexa and Lexapro when Forest\n\nhad insufficient reason to think that these drugs were effective\n\nfor the treatment of depression in children and adolescents.\n\nPlaintiffs have pointed to substantial evidence that Forest sought\n\nto achieve this illicit aim by: (1) promoting Celexa's efficacy\n\nfor the treatment of pediatric depression at medical conferences,\n\nat continuing-medical-education programs, and in press releases;\n\n(2) concealing negative clinical studies concerning Celexa's\n\nefficacy and safety; and (3) directly encouraging physicians to\n\n - 5 -\n\fprescribe Celexa and Lexapro for the treatment of pediatric\n\ndepression.\n\n For years, Forest nevertheless denied that it was\n\nengaged in the off-label promotion of these drugs. Forest\n\nLaboratories' Executive Vice President, Dr. Lawrence Olanoff,\n\ntestified before Congress in 2004 that \"because the FDA has not\n\napproved pediatric labeling for our products, Forest has always\n\nbeen scrupulous about not promoting the pediatric use of our\n\nantidepressant drugs, Celexa and Lexapro. That is the law, and we\n\nfollow it.\" Publication and Disclosure Issues in Antidepressant\n\nPediatric Clinical Trials: Hearing Before the Subcomm. on\n\nOversight & Investigations of the Comm. on Energy & Commerce, 108th\n\nCong. 82 (2004) (statement of Dr. Lawrence Olanoff).\n\n Even before Dr. Olanoff assured Congress of Forest's\n\nscrupulousness, a whistleblower had commenced a qui tam action,\n\nalleging that Forest had violated the False Claims Act (\"FCA\"), 31\n\nU.S.C. § 3729(a), by fraudulently marketing and promoting Celexa\n\nand Lexapro for the off-label treatment of depression in pediatric\n\npatients. Complaint, Gobble v. Forest Labs., Inc., No. 03-10395-\n\nNMG (D. Mass. Mar. 4, 2003), ECF No. 1. The United States later\n\nintervened in that suit, and, in February 2009, the district court\n\nunsealed the United States' complaint. Order Granting Motion to\n\nUnseal, United States ex rel. Gobble, No. 03-10395-NMG (D. Mass.\n\nFeb. 24, 2009), ECF No. 64. The evidence belying Dr. Olanoff's\n\n - 6 -\n\fassurances to Congress turned out to be quite substantial.\n\nUltimately, in September 2010, Forest paid a $39 million fine in\n\nconnection with pleading guilty to criminal violations of the FDCA\n\nfor its off-label promotion of Celexa between 1998 and 2002 and an\n\nadditional $149 million to the United States to settle civil claims\n\nthat Forest illegally promoted Celexa and Lexapro for pediatric\n\nuse in 2002 through 2005.\n\n C.\n\n Within the following four years, over a dozen consumers\n\nand entities who paid for prescription drugs filed the lawsuits\n\nthat led to this appeal. Initially, four plaintiffs joined in the\n\nnotice of appeal. Only two, Renee Ramirez and the Painters and\n\nAllied Trades District Council 82 Health Care Fund (\"Painters\")\n\nhave presented any argument on appeal. We refer to these two\n\ncollectively as \"plaintiffs.\"1 Ramirez purchased Celexa and\n\nLexapro for her young son from February 2003 through March 2010 on\n\nthe recommendation of her son's neurologist. Painters has\n\nreimbursed its pediatric insureds for off-label prescriptions of\n\nCelexa and Lexapro since early 1999. Plaintiffs together seek\n\n\n\n 1Marlene LoConte and Delena Kiossovski joined in the notice\nof appeal but subsequently filed no brief, and the single brief\nfiled by the other parties contains no argument at all for\nquestioning the grounds upon which the district court dismissed\nthe claims of LoConte and Kiossovski. We therefore deem their\nappeal of the judgments against them to be waived. See Vázquez-\nRivera v. Figueroa, 759 F.3d 44, 46-47 (1st Cir. 2014).\n\n - 7 -\n\frecovery under the Racketeer Influenced and Corrupt Organizations\n\nAct (\"RICO\"), 18 U.S.C. § 1962(c)–(d), the Minnesota Consumer\n\nFraud Act, Minn. Stat. § 325F.69, and the Minnesota Unfair Trade\n\nPractices Act, Minn. Stat. § 325D.13, and for unjust enrichment.\n\n In June 2016, the district court denied Painters' motion\n\nto certify two nationwide classes of similarly situated health-\n\ninsurance companies and health plans that had paid for or\n\nreimbursed off-label pediatric prescriptions of Celexa or Lexapro.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig. (Painters I),\n\n315 F.R.D. 116, 131 (D. Mass. 2016).2 In rejecting class\n\ncertification, the court reasoned that while Painters had\n\nsatisfied the Rule 23(a) numerosity, commonality, typicality, and\n\nadequacy requirements, Painters had failed to establish that\n\ncommon questions of fact or law predominated over individual issues\n\nas required by Rule 23(b)(3). Id. at 123–31.\n\n Subsequently, in March 2017, a dispute arose as a result\n\nof Forest's apparently belated production of two internal\n\nmemoranda in advance of a deposition conducted by agreement after\n\ndiscovery had otherwise closed. The two documents contained\n\n\n\n 2Painters' motion for class certification provided no time\nperiod for the proposed Celexa class. At oral argument, however,\nplaintiffs' counsel clarified that plaintiffs only seek to\nchallenge manufacturer-induced prescriptions for off-label uses\nmade prior to the FDA's approval of Lexapro for adolescent use in\nMarch 2009. Thus, we construe Painters' appeal in accordance with\nthis statement.\n\n - 8 -\n\fdetails regarding a study of Celexa's effectiveness. Forest\n\nrevealed that it had not sought any responsive documents from its\n\nClinical Supply Group in responding to Painters' discovery\n\nrequests. The district court nevertheless denied Painters' motion\n\nto compel Forest's supplemental production of documents from this\n\ngroup, concluding that any such production would be cumulative.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig.\n\n(Painters II), 288 F. Supp. 3d 483, 486–87 (D. Mass. 2018).\n\n In due course, after deeming discovery complete and\n\nruling on various interim motions, the district court entered\n\nsummary judgment for Forest on plaintiffs' RICO claims, holding\n\nthat neither Painters nor Ramirez could demonstrate injury. In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Painters III),\n\n289 F. Supp. 3d 247, 253–56 (D. Mass. 2018). The court then\n\nproceeded to dismiss plaintiffs’ state-based allegations as\n\nderiving from their noncognizable RICO claims. Id. at 258–59.\n\nThis appeal by Painters and Ramirez followed.\n\n II.\n\n Summary judgment is appropriate \"if the movant shows\n\nthat there is no genuine dispute as to any material fact and the\n\nmovant is entitled to judgment as a matter of law.\" Fed. R. Civ.\n\nP. 56(a). In granting summary judgment dismissing all of\n\nplaintiffs' claims, the district court concluded that plaintiffs\n\nhad no competent proof that either Celexa or Lexapro was\n\n - 9 -\n\fineffective for treating depression in children or adolescents.\n\nWe review this conclusion de novo. Martinez v. Petrenko, 792 F.3d\n\n173, 179 (1st Cir. 2015).\n\n A.\n\n Prevailing on a RICO claim requires proof of an economic\n\ninjury. See 18 U.S.C. § 1964(c) (\"Any person injured in his\n\nbusiness or property by reason of a violation of section 1962 of\n\nthis chapter may sue therefor.\"). Plaintiffs allege injury in the\n\nform of payments made for ineffective drugs.3 The district court\n\ntherefore turned its attention to determining whether plaintiffs\n\nhad enough evidence to allow a jury to find Celexa and/or Lexapro\n\nineffective for treating pediatric depression. See Painters III,\n\n289 F. Supp. 3d at 253–56. Four clinical trials and the FDA's\n\n2009 approval of Lexapro for adolescents informed the district\n\ncourt's decision.\n\n Starting in 1997, Lundbeck -- the developer of Celexa -\n\n- began conducting Study 94404, which focused on Celexa's efficacy\n\nin treating depression in adolescents. The study produced across-\n\nthe-board negative results. Forest then conducted Study MD-18 in\n\nan attempt to demonstrate Celexa's effectiveness in both children\n\n\n 3 In its opposition to Forest's motion for summary judgment,\nPainters argued that it need not demonstrate that Celexa and\nLexapro are ineffective in treating pediatric depression to\nestablish RICO injury. The district court rejected this argument\nin its order granting Forest's motion, and Painters has not\ndeveloped any challenge to that ruling on this appeal.\n\n - 10 -\n\fand adolescents. The efficacy results of MD-18 are difficult to\n\nassess because Forest bungled the study: Some participants\n\nrandomized into the active treatment group were dispensed\n\nnongeneric, pink tablets in one portion of the trial, potentially\n\nunblinding both the individuals who received these pills and the\n\nresearchers conducting the study. The MD-18 study only\n\ndemonstrated statistically positive results when these potentially\n\nunblinded participants were included. Finally, in 2002–2004 and\n\n2005-2007, Forest conducted two additional clinical trials. Study\n\nMD-15 examined Lexapro's efficacy in children and adolescents and\n\nachieved negative results. Study MD-32 set out to test Lexapro's\n\neffectiveness in treating only adolescents and achieved\n\nstatistically significant positive results.\n\n Based upon the results of MD-32 and the Celexa MD-18\n\nstudy, Forest submitted an sNDA to the FDA in 2008. In 2009, the\n\nFDA approved the application, allowing Forest to market Lexapro\n\nfor use in adolescents. Forest did not seek such approval for\n\nCelexa.\n\n Plaintiffs' evidence that Celexa and Lexapro were\n\nineffective for the pertinent indications consisted of the\n\nfollowing: The FDA has neither approved Celexa for treating\n\ndepression in children or adolescents nor has it approved Lexapro\n\nfor use in children; Study 94404 demonstrated only a detrimental\n\neffect of Celexa in treating depression in adolescents; Study MD-\n\n - 11 -\n\f18 was corrupted and showed no beneficial effect in children and\n\nadolescents unless the potentially unblinded participants are\n\nincluded in the results; and Study MD-15 produced uniformly\n\nnegative results in testing Lexapro's efficacy in children and\n\nadolescents. In addition, plaintiffs produced expert testimony\n\nopining that the positive results in MD-32 were not of clinical\n\nsignificance and that MD-18 should properly be considered a\n\nnegative trial. Plaintiffs also provided the results of a\n\n2016 meta-analysis study that found that neither Celexa nor\n\nLexapro had any more beneficial effect than a placebo in treating\n\npediatric depression.\n\n There is also evidence in the record before us, however,\n\nthat cuts the other way. In September 2002, the FDA accepted\n\nStudy MD-18 as a positive trial that would support a determination\n\nof Celexa's effectiveness for the treatment of MDD in adolescent\n\npatients. And in January 2003, the FDA also stated that MD-18\n\ncould be employed to support an application for FDA approval \"for\n\nboth Celexa and Lexapro, in pediatric patients with [MDD].\" The\n\nFDA relied in part on these findings in approving Lexapro for the\n\ntreatment of depression in adolescents in March 2009. Further,\n\nForest points out that neither Painters nor Prime Therapeutics\n\n(\"Prime\"), Painters' pharmacy-benefits manager, has taken any\n\neffort to limit or remove from its formulary pediatric\n\nprescriptions of Celexa and Lexapro.\n\n - 12 -\n\f This record raises two questions. First, do the FDA's\n\nvarious pronouncements or actions close the door on any effort to\n\nconvince a jury that either Celexa or Lexapro was ineffective?\n\nSecond, to the extent that the FDA's pronouncements and actions\n\nare not preclusive, is the evidence in this case nevertheless\n\ninsufficient to support a jury finding of ineffectiveness?\n\n 1.\n\n Forest claims that two of our recent decisions --\n\nD'Agostino v. ev3, Inc., 845 F.3d 1 (1st Cir. 2016), and In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Marcus), 779 F.3d\n\n34 (1st Cir. 2015) -- answer the first question in the affirmative\n\nby deeming FDA approval dispositive. Even were we to find it\n\nconvincing, this argument would not cover all the challenged uses\n\nat issue in this appeal. The FDA has never approved Celexa for\n\nany of the off-label uses for which Forest promoted it. Nor has\n\nit approved Lexapro for the treatment of MDD in children under the\n\nage of twelve. So Forest's reliance on actual FDA approval to\n\nforeclose a jury determination of inefficacy must be limited to\n\nForest's marketing of Lexapro for adolescent use and, perhaps as\n\nwell, to the question of how to construe MD-18.\n\n In any event, even as thus limited, we do not find\n\nForest's reliance on D'Agostino convincing. The claim in\n\nD'Agostino concerned the sale of medical devices after the FDA had\n\napproved the devices for the uses for which they were sold.\n\n - 13 -\n\fD'Agostino, 845 F.3d at 3, 7–9. In rejecting a challenge to those\n\npost-approval sales under the False Claims Act based on alleged\n\npre-approval fraud on the FDA, we reasoned that \"[t]o rule\n\notherwise would be to turn the FCA into a tool with which a jury\n\nof six people could retroactively eliminate the value of FDA\n\napproval and effectively require that a product largely be\n\nwithdrawn from the market even when the FDA itself sees no reason\n\nto do so.\" Id. at 8. Here, by contrast, plaintiffs challenge\n\nonly the promotion of Celexa and Lexapro for uses that were off-\n\nlabel (i.e., not FDA-approved) at the time Forest promoted and\n\nsold the drugs.4 When Forest is said to have made those marketing\n\nefforts, it could not have pleaded reliance on FDA approval. If\n\na jury were to hold Forest liable for such pre-approval marketing,\n\nit would simply be telling Forest that it should not have marketed\n\nthat which Congress under the FDCA does not want it to market:\n\ndrugs for unapproved uses. We therefore see no reason to accord\n\nto Forest the preclusive protection for pre-approval promotion\n\nthat FDA approval provided the medical-device manufacturer for\n\npost-approval conduct in D'Agostino.5\n\n\n 4 Though plaintiffs' complaints do not explicitly limit their\nRICO and state-law claims to the period prior to FDA's March 2009\napproval of Lexapro, plaintiffs' counsel indicated at oral\nargument that plaintiffs do not challenge Forest's post-approval\nmarketing of Celexa and Lexapro.\n 5 For similar reasons, Forest's reliance on Buckman Co. v.\nPlaintiffs' Legal Comm., 531 U.S. 341, 348 (2001), in which the\nSupreme Court rejected as preempted state fraud-on-the-FDA claims,\n - 14 -\n\f Nor does our opinion in Marcus aid Forest in this case.\n\nIn Marcus, we rejected a challenge to a drug label based on\n\ninformation that was \"plainly known to the FDA prior to approving\n\nthe label.\" 779 F.3d at 43. We made clear in doing so, however,\n\nthat we were merely applying the state-law preemption principles\n\nthe U.S. Supreme Court laid out in PLIVA, Inc. v. Mensing, 564\n\nU.S. 604 (2011), and Wyeth v. Levine, 555 U.S. 555 (2009). See\n\nMarcus, 779 F.3d at 40–43 (explaining that a drug manufacturer can\n\nonly be held liable under state law for inadequate warning in an\n\nFDA-approved label when the drug manufacturer can, \"of its own\n\nvolition, . . . strengthen its label in compliance with its state\n\ntort duty\" (quoting PLIVA, Inc., 564 U.S. at 624)). Marcus,\n\naccordingly, is inapposite.\n\n This is not to say that the FDA's 2009 approval of\n\nForest's sNDA for Lexapro is irrelevant to this case. Certainly\n\nthe approval and the FDA's reliance on MD-18 provide what many\n\njurors may view as strong evidence confirming that Lexapro, and\n\nperhaps Celexa as well, have always been efficacious in treating\n\npediatric depression. The common law has long recognized that\n\nagency approval of this type is relevant in tort suits. See\n\nRestatement (Third) of Torts: Prod. Liab. § 4 (Am. Law Inst. 1998)\n\n\nand its progeny is misplaced. Plaintiffs question the efficacy of\nCelexa and Lexapro only for off-label uses; their claims,\naccordingly, are not predicated on a fraud-on-the-FDA theory of\nliability.\n\n - 15 -\n\f(\"[C]ompliance with an applicable product safety statute . . . is\n\nproperly considered in [a product defect case].\"). But the common\n\nlaw also recognizes that such evidence is not always preclusive.\n\nId. (\"[S]uch compliance does not preclude as a matter of law a\n\nfinding of product defect.\"). And while there are strong reasons\n\nfor treating such evidence as preclusive when the challenged sales\n\nare made in reliance on agency approval, those same reasons cut\n\nthe other way when the sales are made without approval, and\n\ncertainly when made unlawfully, as we must assume they were here.\n\n 2.\n\n Having decided that the FDA's subsequent approval of\n\nLexapro does not preclude proving that pre-approval uses of these\n\ndrugs were ineffective, we turn to addressing whether plaintiffs\n\nmay proceed with a claim based on product ineffectiveness when the\n\nevidence of efficacy is conflicting. This is more or less the\n\nquestion we left unanswered in Kaiser. See Kaiser, 712 F.3d at 49\n\n(declining to address what evidentiary standard would be needed to\n\ndemonstrate efficacy \"if the results of DBRCTs were equivocal\" or\n\n\"if there were a different mix of DBRCT and non-DBRCT evidence\").6\n\n\n 6 To advance its preferred interpretation of the term\n\"equivocal\" in Kaiser, each party dedicates a significant portion\nof its brief to sparring over whether the DBRCT evidence in the\nNeurontin cases was, in fact, mixed. We need not address this\nquestion because, as we explain, Painters' RICO claim survives\nsummary judgment even though the evidence of inefficacy is mixed.\nWe note, however, that the DBRCTs in the Neurontin case were not\nuniformly negative as Forest would have us believe. Rather, the\n - 16 -\n\f Generally speaking, \"conflicting evidence\" is the\n\nhallmark of an issue that calls for factfinding, not summary\n\njudgment. See, e.g., Adria Int'l Grp. v. Ferre Dev., Inc., 241\n\nF.3d 103, 111 (1st Cir. 2001) (finding summary judgment\n\ninappropriate when evidence presented was \"contested and\n\ncontradictory\"); see also 10A Charles Alan Wright et al., Federal\n\nPractice and Procedure § 2712 (4th ed. 2018) (\"[S]ummary judgment\n\nis not a substitute for the trial of disputed fact issues.\"). We\n\nsee no reason to deviate from that general rule merely because the\n\nproduct marketed illegally is one that was later approved for\n\nlawful sales.7 In short, why should we forgo customary fact-\n\nfinding by the jury so as to reward unlawful conduct aimed at\n\ngetting children to consume unapproved drugs?\n\n Forest also argues that plaintiffs' evidence of\n\nineffectiveness falls short of proving injury because Painters has\n\nnot produced \"individualized\" proof that Celexa or Lexapro was\n\nineffective for any particular insured. By \"individualized\"\n\nproof, Forest appears to mean testimony from a patient (or from a\n\n\ndistrict court noted both positive and negative clinical studies\nin reviewing the parties' evidence of Neurontin's efficacy for the\nat-issue off-label conditions. See Kaiser, 2011 WL 3852254, at\n*34–46 (reviewing mixed DBRCT results).\n 7\n Nor is summary judgment for Forest warranted due to the fact\nthat Painters has not directed the removal of Celexa and Lexapro\nfor pediatric uses from its drug formulary. As we held in Kaiser,\nit is \"within the factfinder's province to weigh this evidence.\"\nKaiser, 712 F.3d at 41.\n\n - 17 -\n\fdoctor concerning that patient) that the patient experienced no\n\nbeneficial effects from the drug. While evidence of that type\n\ncould be probative, certainly it is not the only way to prove that\n\na drug is ineffective. Indeed, given that (1) an ineffective drug\n\nmay trigger a placebo effect in a given individual and (2) an\n\neffective drug may not benefit all users, individualized proof\n\nmight well be less probative than the type of expert, study-based\n\ntestimony that plaintiffs have offered. In any event, as we\n\nalready held, such individualized proof is certainly not required.\n\nSee In re Neurontin Mtkg. & Sales Practices Litig. (Harden), 712\n\nF.3d 60, 69 (1st Cir. 2013) (\"[W]e reject Pfizer's position that\n\nthese plaintiffs must prove the individual, subjective\n\nineffectiveness of each off-label prescription in order to\n\nestablish injury. . . . The Harden plaintiffs have proffered\n\nclinical trial evidence that Neurontin is ineffective . . ., which\n\nis certainly enough to raise a genuine issue of fact on the\n\neffectiveness issue.\" (citation omitted)); In re Neurontin Mtkg.\n\n& Sales Practices Litig. (Aetna), 712 F.3d 51, 59–60 (1st Cir.\n\n2013).\n\n In sum, we hold that the FDA's 2009 approval of Lexapro\n\ndoes not preclude a jury from concluding that the off-label uses\n\nof Celexa and Lexapro at issue in this case were ineffective in\n\ntreating pediatric depression. Moreover, plaintiffs have provided\n\ncompetent and sufficient evidence -- through DBRCTs, expert\n\n - 18 -\n\ftestimony, and peer-reviewed literature -- to raise a genuine issue\n\nof material fact as to the efficacy of these drugs for pediatric\n\nuse. Accordingly, the district court erred in granting summary\n\njudgment for Forest on plaintiffs' RICO and state-law claims on\n\nthis basis.\n\n B.\n\n In addition to demonstrating economic injury, a RICO\n\nplaintiff must prove that the defendant's racketeering conduct\n\ncaused her injury. 18 U.S.C. § 1964(c); Holmes v. Sec. Inv'r Prot.\n\nCorp., 503 U.S. 258, 268 (1992) (interpreting section 1964(c)'s\n\nlanguage to mean that a RICO plaintiff must show both but-for and\n\nproximate causation to establish standing). As we have already\n\nnoted, physicians can -- and do -- lawfully prescribe prescription\n\ndrugs for off-label uses, even though the manufacturer is barred\n\nby law from promoting such prescriptions. See Lawton ex rel.\n\nUnited States, 842 F.3d at 128 n.4. So for any given prescription\n\nin this case, one would reasonably ask whether Forest's efforts to\n\nprofit by illegally marketing drugs for pediatric use caused a\n\nparticular prescription to be made, or whether, instead, the doctor\n\nwrote a given prescription based on his or her own professional\n\nmedical judgment (perhaps reasoning that what works for an adult\n\npatient might also work for a younger patient).\n\n Forest therefore urges that, even if we disagree with\n\nthe district court on the issue of injury/efficacy, we should still\n\n - 19 -\n\faffirm the entry of summary judgment due to Painters' lack of proof\n\nof but-for causation. While the district court did not consider\n\nthe issue of causation in its summary-judgment ruling, it did\n\nearlier assay Painters' causation evidence in ruling on Painters'\n\nmotion for class certification. The district court labeled the\n\nproof so \"insubstantial\" and \"fundamentally flawed\" \"as to\n\npreclude class certification.\" Painters I, 315 F.R.D. at 126–28.\n\nForest would have us interpret these pronouncements as a finding\n\nthat the evidence was insufficient as a matter of law to prove\n\nbut-for causation.\n\n We disagree. In the first place, it is unclear why the\n\ndistrict court gauged the substantiality or merit of plaintiffs'\n\nproof in the context of a Rule 23 motion. The central issue in\n\nthat context is not whether the method of proof would or could\n\nprevail. Rather, it is whether the method of proof would apply in\n\ncommon to all class members. See, e.g., Tyson Foods, Inc. v.\n\nBouaphakeo, 136 S. Ct. 1036, 1047 (2016) (\"When . . . 'the concern\n\nabout the proposed class is not . . . some fatal dissimilarity\n\nbut, rather, a fatal similarity -- [an alleged] failure of proof\n\nas to an element of the plaintiffs' cause of action -- courts\n\nshould engage that question as a matter of summary judgment, not\n\nclass certification.'\" (alteration in original) (quoting Richard\n\nA. Nagareda, Class Certification in the Age of Aggregate Proof, 84\n\nN.Y.U. L. Rev. 97, 107 (2009))).\n\n - 20 -\n\f More substantively, Painters' evidence does not seem\n\nclearly insufficient. There is ample evidence that Forest spent\n\nmoney inducing doctors to prescribe its drugs to pediatric patients\n\nand that it would not have done so had the effort not been worth\n\nthe money. Two experts, Dr. Meredith Rosenthal and\n\nDr. Christopher Baum, also opined that Forest's spending on\n\npromotions in general correlated positively with sales. As the\n\ndistrict court pointed out, Painters' experts then assumed that\n\nthis same approximate correlation applied to off-label promotional\n\nspending and off-label sales. Painters I, 315 F.R.D. at 127. The\n\ndistrict court thought this assumption to be a \"fundamental flaw\"\n\nin the analysis. Id. Why, exactly, we are not sure. After all,\n\nwhy would Forest, which knew its markets better than anyone, have\n\nspent money on off-label marketing over the long term if it\n\ngenerated lower returns than would additional spending on less\n\nrisky, lawful marketing? Certainly there is room for reasonable\n\ndisagreement on the merits of Dr. Rosenthal and Dr. Baum's\n\nassumption.\n\n If the jury accepts this assumption as reasonable, and\n\nif it finds that the prescriptions that Painters paid for were\n\ntypical of those that the experts analyzed, jurors would then have\n\na fair path to finding that Forest's off-label marketing caused\n\nPainters to pay for ineffective drugs. The experts' interpretation\n\nof the data indicated that Forest's off-label promotions caused\n\n - 21 -\n\f76% and 54% of all pediatric prescriptions of Celexa and Lexapro,\n\nrespectively. Dr. Rosenthal estimated that if Painters paid for\n\nas few as five independent prescriptions, there would be a 98%\n\nchance that at least one was the result of off-label marketing.\n\nIn fact, Painters likely paid for the Celexa or Lexapro\n\nprescriptions of more than five different patients.8 So the odds\n\nthat Painters was not harmed if the drugs were, indeed, ineffective\n\nwas likely infinitesimal (assuming the prescriptions were\n\nindependent of one another).9\n\n\n\n\n 8In its summary judgment order, the district judge observed\nthat Painters reimbursed sixteen of its pediatric insureds for\nseventy-two off-label prescriptions of Celexa from 1999 through\n2004, and thirty-one of its pediatric insureds for 234 off-label\nprescriptions of Lexapro from 2002 through early 2015. Painters\nIII, 289 F. Supp. 3d at 251. It is not clear from the record how\nmany of these Lexapro prescriptions were written prior to March\n2009. Viewing this evidence in the light most favorable to\nPainters, Ellis v. Fidelity Mgmt. Tr. Co., 883 F.3d 1, 3, (1st\nCir. 2018), and without any counter-argument on this point by\nForest, we assume for purposes of this appeal only that well more\nthan five of the aforementioned Lexapro prescriptions were filled\nprior to the FDA's 2009 approval of Lexapro.\n 9The statistical proof in this instance is being used only\nto prove that a group of prescriptions likely includes at least\none that a certain activity caused, and it is then being utilized\nto estimate the percentage of such causally connected\nprescriptions in that group. Painters proposes no use of the\nstatistical data to prove that Forest's off-label marketing caused\nany particular prescription to be written. See In re Asacol\nAntitrust Litig. (Asacol), 907 F.3d 42, 54 (1st Cir. 2018) (finding\nit \"far from self-evident\" that expert testimony opining that\n\"ninety percent of class members were injured\" would be \"sufficient\nto prove that any given individual class member was injured\").\n\n - 22 -\n\f Nor is Painters' evidence limited to the thrust of its\n\nstatistics. Painters also has evidence that Forest sales\n\nrepresentatives called or visited at least two physicians who\n\nsubsequently ordered pediatric prescriptions of Celexa and Lexapro\n\nthat Painters reimbursed. In addition, Painters produced evidence\n\nsuggesting that Forest specifically targeted Painters' pharmacy-\n\nbenefits manager, Prime, and that Prime relied upon a misleading\n\nreport by Forest of Study MD-18 in managing Painters' formulary.\n\nAll together, this is surely enough to raise a triable issue of\n\nfact as to whether Forest's off-label marketing caused Painters to\n\npay for a prescription for which it would not have otherwise paid.\n\n This is not to say that Painters will ultimately prevail\n\non the issue of causation. The district court has not conducted\n\na Daubert analysis. And there may be other potential bones to\n\npick with the sufficiency of Painters' proof of causation. As the\n\nrecord now stands, though, we agree with Painters that we cannot\n\naffirm the summary judgment finding that its causation proof is\n\ninsufficient as a matter of law.\n\n As for Ramirez, Forest did not challenge her standing on\n\nthe basis of causation in its memorandum in support of its motion\n\nfor summary judgment. Accordingly, we express no opinion as to\n\nwhether Ramirez has raised a triable issue on RICO causation. See\n\nRosaura Bldg. Corp. v. Municipality of Mayagüez, 778 F.3d 55, 63\n\n\n\n - 23 -\n\f(1st Cir. 2015) (\"Time and time again we have held that arguments\n\nnot advanced before the district court are waived.\").\n\n As for proximate causation, it is of no moment that\n\npediatricians were the immediate target of Forest's fraudulent\n\nmarketing. Here, as in Kaiser, a jury could find that Painters\n\nand Ramirez were \"the primary and intended victims of [Forest's]\n\nscheme to defraud.\" Kaiser, 712 F.3d at 37 (quoting Bridge v.\n\nPhx. Bond & Indem. Co., 553 U.S. 639, 650 (2008)). Moreover,\n\nPainters' and Ramirez's alleged harm (i.e., reimbursing or\n\npurchasing more pediatric prescriptions than they otherwise would\n\nhave) was a \"foreseeable and natural consequence\" of Forest's\n\nscheme. Bridge, 553 U.S. at 658. Indeed, it was precisely the\n\npoint.\n\n Accordingly, for the foregoing reasons, we reverse the\n\ndistrict court's entry of summary judgment for Forest on Painters'\n\nRICO and state-law claims and on Ramirez's RICO and unjust-\n\nenrichment claims.\n\n III.\n\n Early on in this litigation the district court denied\n\nPainters' motion to certify this case as a class action under\n\nFederal Rule of Civil Procedure 23(b)(3). In so ruling, the\n\ndistrict court reasoned that a variety of important issues,\n\nincluding causation and injury, would pose individual questions\n\nthat would need to be answered for each class member. Painters I,\n\n - 24 -\n\f315 F.R.D. at 123–30. The presence of these individual questions,\n\nreasoned the district court, defeated Painters' effort to satisfy\n\nthe requirement of Rule 23(b)(3) that common issues must\n\npredominate. Id. Painters now appeals that ruling as it applies\n\nto classes consisting of third-party payors (\"TPP\") who paid for\n\nor reimbursed prescriptions of Celexa or Lexapro prior to early\n\n2009. It is not clear why those issues to which the district court\n\npointed would preclude certification of such a class. As we have\n\nalready explained, Painters' clinical and statistical evidence, if\n\nbelieved, could establish causation and injury at least for any\n\nTPP who paid for more than a handful of different patients'\n\nprescriptions. Nevertheless, as we will explain, it has become\n\napparent that the proper application of the statute of limitations,\n\nwhile preserving plaintiffs' individual claims, precludes\n\nPainters' attempt to maintain a class action.\n\n A.\n\n The parties agree that the applicable statutory\n\nlimitations period is four years. See Agency Holding Corp. v.\n\nMalley-Duff & Assocs., Inc., 483 U.S. 143, 156 (1987). That four-\n\nyear period began to run \"at the time [the] plaintiff knew or\n\nshould have known of his injury.\" Lares Grp., II v. Tobin, 221\n\nF.3d 41, 44 (1st Cir. 2000) (citing Rodriguez v. Banco Central,\n\n917 F.2d 664, 665 (1st Cir. 1990)). The injury here is the payment\n\nmade on account of off-label prescriptions that Forest induced.\n\n - 25 -\n\fSee Kaiser, 712 F.3d at 39 (\"[E]conomic injury occur[s] when\n\n[plaintiff] paid for fraudulently induced [drug] prescriptions.\").\n\nSo, the key question becomes: By what date can we say, as a matter\n\nof law, that Painters knew or should have known that Forest was\n\npromoting the off-label, ineffective use of Celexa or Lexapro?\n\n The district court found that date to be no later than\n\nMarch of 2009. In re Celexa & Lexapro Mktg. & Sales Practices\n\nLitig., 65 F. Supp. 3d 283, 289 (D. Mass. 2014). In February of\n\nthat year, the United States unsealed its complaint against Forest\n\nin United States ex rel. Gobble, which detailed in thirty-three\n\npages how \"Forest engaged in a fraudulent scheme to market and\n\npromote Celexa . . . and Lexapro . . . off-label to treat\n\ndepression and other psychiatric conditions in pediatric\n\npatients.\" Complaint at 2, United States ex rel. Gobble, No. 03-\n\n10395-NMG (D. Mass. Feb. 13, 2009), ECF No. 61 [hereinafter United\n\nStates' Complaint]. Within weeks, two private class-action\n\ncomplaints followed, one in New York and another in Missouri, each\n\nalso alleging a fraudulent scheme to market Celexa and Lexapro for\n\nineffective, off-label uses. See Class Action Complaint,\n\nUniversal Care, Inc. v. Forest Pharm., Inc., No. 09-cv-11518-NMG\n\n(D. Mass. Mar. 20, 2009), ECF No. 1; Class Action Complaint, N.M.\n\nUFCW Union's & Emp'rs' Health & Welfare Tr. Fund v. Forest Labs.,\n\nInc., No. 09-cv-11524-NMG (D. Mass. Mar. 12, 2009), ECF No. 1.\n\nPainters never argued before the district court that it was unaware\n\n - 26 -\n\fof the United States' complaint or the March 2009 lawsuits. Nor\n\ndoes it so argue on appeal. Rather, it argues that the lawsuits\n\ndid not provide enough notice that Forest had been promoting the\n\noff-label use of Celexa and Lexapro. Such notice, Painters says,\n\nwas not available until Forest's own public admission to that\n\neffect in November 2010, when it both pleaded guilty to criminal\n\nviolations of the FDCA and entered into a civil settlement\n\nagreement with the United States.\n\n Not surprisingly, Painters points to no case law holding\n\nthat a statutory limitations period does not start to run until\n\nthe potential defendant first delivers a gift-wrapped admission of\n\nits alleged wrongdoing. Were that the rule, very few limitations\n\nperiods would ever commence, much less conclude. Instead, as we\n\nhave explained in an analogous context, \"[w]e look first to whether\n\nsufficient facts were available to provoke a reasonable person in\n\nthe plaintiff's circumstances to inquire or investigate\n\nfurther. . . . Once a duty to inquire is established, the\n\nplaintiff is charged with the knowledge of what he or she would\n\nhave uncovered through a reasonably diligent investigation.\"\n\nMcIntyre v. United States, 367 F.3d 38, 52 (1st Cir. 2004); see\n\nalso Sanchez v. United States, 740 F.3d 47, 52 (1st Cir. 2014)\n\n(\"The discovery rule incorporates an objective standard. To delay\n\ncommencement of the running of the statute of limitations, 'the\n\nfactual basis for the cause of action must have been inherently\n\n - 27 -\n\funknowable, [that is, not capable of detection through the exercise\n\nof reasonable diligence] at the time of injury.'\" (alteration in\n\noriginal) (quoting Gonzalez v. United States, 284 F.3d 281, 288–\n\n89 (1st Cir. 2002))). The same fundamental principle applies to\n\nRICO suits. See Rotella v. Wood, 528 U.S. 549, 555 (2000)\n\n(\"Federal courts . . . generally apply a discovery accrual rule\n\nwhen a statute is silent on the issue, as civil RICO is here. . . .\n\n[D]iscovery of the injury . . . is what starts the clock.\"\n\n(citations omitted)); Koch v. Christie's Int'l PLC, 699 F.3d 141,\n\n150–51 (2d Cir. 2012) (noting that a RICO claim does not accrue\n\nuntil a plaintiff has \"actual or inquiry notice of the injury\"\n\n(quoting In re Merrill Lynch Ltd. P'ships Litig., 154 F.3d 56, 60\n\n(2d Cir. 1998))).\n\n We agree with the district court that the unsealing of\n\nthe United States' complaint and the subsequent lawsuits filed in\n\nMarch 2009 were more than sufficient to put a TPP like Painters on\n\nnotice that Forest had likely been inducing off-label\n\nprescriptions of Celexa and Lexapro. The United States' complaint\n\nchronicled how Forest suppressed a negative study on Celexa while\n\npromoting a positive study (which conveniently neglected to\n\nmention the earlier, negative study). United States' Complaint at\n\n3, 14. The complaint quoted internal Forest communications and\n\nrecounted the precise details of Forest's unlawful promotional\n\nactivities. Id. at 15–22. It quoted Forest's physician-call notes\n\n - 28 -\n\freporting on the efforts of Forest's sales representatives to\n\npromote the pediatric use of the drugs. E.g., id. at 20 (\"[F]ocus\n\non Lexapro efficacy at just 10 mg., great choice for\n\nchild/adolescents.\"). It also named Forest marketing executives,\n\ne.g., id. at 23, and outside physicians involved in the promotion\n\ncampaigns, e.g., id. at 21–22. It is inconceivable that any TPP\n\nlike Painters would not have found in the complaint a very strong\n\nprobability that Forest had systematically and fraudulently pushed\n\nits drugs on unsuspecting children.\n\n Nevertheless, we also agree with the district court that\n\nPainters survived Forest's statute-of-limitations defense because\n\nthe running of the limitations period was stayed for more than\n\neight months by the filing of the N.M. UFCW class action in March\n\n2009. See In re Celexa & Lexapro Mktg. & Sales Practices Litig.,\n\n65 F. Supp. 3d at 291. Painters was a member of the putative RICO\n\nclass action for which the N.M. UFCW complaint sought\n\ncertification. Under American Pipe & Construction Co. v. Utah,\n\n414 U.S. 538 (1974), the limitations period during which Painters\n\nmight sue on its own behalf was therefore tolled until the N.M.\n\nUFCW class action was dismissed in June 2010. Forest did not cross\n\nappeal the district court's application of American Pipe. Rather,\n\nForest argues only that the limitations period began running long\n\nbefore March of 2009 when plaintiffs first should have suspected\n\nthat Celexa and Lexapro were ineffective for pediatric use. We\n\n - 29 -\n\freject that argument because the injury here is paying for\n\nunlawfully induced off-label prescriptions, not merely physician-\n\ndirected, off-label prescriptions.\n\n B.\n\n Even though plaintiffs can sue, thanks to American Pipe,\n\nPainters cannot parlay that dispensation into the much-delayed\n\nfiling of a class action. See China Agritech, Inc. v. Resh, 138\n\nS. Ct. 1800 (2018). In American Pipe, the Supreme Court held that\n\nthe \"commencement of [a putative class action] tolls the running\n\nof the statute for all purported members of the class who make\n\ntimely motions to intervene after the court has found the suit\n\ninappropriate for class action status.\" 414 U.S. at 552-53. China\n\nAgritech clarified that this tolling rule has limits: While a\n\nputative class member may join an existing suit or file an\n\nindividual action upon denial of class certification, a putative\n\nclass member may not commence a class action anew beyond the time\n\nallowed by the untolled statute of limitations. 138 S. Ct. at\n\n1807 (\"The 'efficiency and economy of litigation' that support\n\ntolling of individual claims do not support maintenance of untimely\n\nsuccessive class actions; any additional class filings should be\n\nmade early on, soon after the commencement of the first action\n\nseeking class certification.\" (citation omitted) (quoting Am.\n\nPipe, 414 U.S. at 553)).\n\n\n\n - 30 -\n\f Painters argues that China Agritech is distinguishable\n\nfrom the case at hand because there was no substantive ruling on\n\nclass certification in N.M. UFCW; the first time any district court\n\naddressed class certification was in Painters' case. Painters'\n\nposition relies on an impermissibly narrow reading of the Court's\n\ndecision in China Agritech. Though the Supreme Court granted\n\ncertiorari in that case to answer the narrow question of whether\n\na putative class member may commence a class action beyond the\n\nlimitations period upon the district court's denial of a request\n\nfor class certification filed within the statute of limitations,\n\nid. at 1804, the Court proceeded to provide a broader answer: Its\n\nprecedents do not \"so much as hint[] that [American Pipe] tolling\n\nextends to otherwise time-barred class claims,\" id. at 1806. Thus,\n\nthe Court effectively ruled that the tolling effect of a motion to\n\ncertify a class applies only to individual claims, no matter how\n\nthe motion is ultimately resolved. To hold otherwise would be to\n\nallow a chain of withdrawn class-action suits to extend the\n\nlimitations period forever.\n\n For the foregoing reasons, the district court did not\n\nabuse its discretion in declining to certify Painters' proposed\n\nnationwide class of TPPs.\n\n IV.\n\n Finally, Painters also takes issue with the district\n\ncourt's denial of its motion to compel Forest's supplemental\n\n - 31 -\n\fproduction of documents related to the MD-18 Study. This court\n\nreviews a district court's discovery decision for abuse of\n\ndiscretion, intervening \"only upon a clear showing of manifest\n\ninjustice, that is, where the lower court's discovery order was\n\nplainly wrong and resulted in substantial prejudice to the\n\naggrieved party.\" Pina v. Children's Place, 740 F.3d 785, 791\n\n(1st Cir. 2014) (quoting Dennis v. Osram Sylvania, Inc., 549 F.3d\n\n851, 859 (1st Cir. 2008)).\n\n Here, it is undisputed that Forest did not perform an\n\nexhaustive search in response to Painters' requests for documents\n\nrelated to the MD-18 Study: Indeed, Forest acknowledges\n\n(employing the passive voice) that \"files within the custody of\n\nthe Clinical Supply Group were not searched.\" Forest also does\n\nnot deny that its own preliminary search within this group -- after\n\ndiscovery had closed -- produced two responsive memoranda\n\nregarding the packaging error in the MD-18 Study. The only excuse\n\nForest provides is that \"[p]laintiffs were fully apprised of the\n\nscope of document collection and were aware that files within the\n\ncustody of the Clinical Supply Group were not searched.\" Forest,\n\nhowever, points us to nothing in the record demonstrating that\n\nPainters acquiesced to Forest's limiting the scope of its document\n\ncollection in this way. These admissions notwithstanding, the\n\ndistrict court denied Painters' Rule 37 motion to compel the\n\nsupplementary production of documents related to the MD-18 Study.\n\n - 32 -\n\fIt reasoned that the Rule 26(e)(1) duty to supplement only applies\n\nwhen \"the supplemental material has not been otherwise made known\n\nto the requesting party\" and observed that Painters had already\n\nreceived \"substantial production of documents related to the\n\npackaging error\" such that any new production would be cumulative.\n\nPainters II, 288 F. Supp. 3d at 487.\n\n Rule 26(e)(1) requires that a party who has responded to\n\na request for production supplement its response in a timely manner\n\n\"if the party learns that in some material respect the . . .\n\nresponse is incomplete . . . and if the additional . . .\n\ninformation has not otherwise been made known to the other parties\n\nduring the discovery process.\" Fed. R. Civ. P. 26(e)(1). Whether\n\nor not \"information has not otherwise been made known\" -- and,\n\nthus, whether or not additional production would be cumulative --\n\nnecessarily hinges on the relevance that the additional production\n\nmight have for the requesting party's claims and the complexity of\n\nthe issue that the factfinder is tasked to resolve; clearly, a\n\nrelatively high degree of granularity in document production is to\n\nbe expected in technical matters of great significance to a party's\n\noverall claim.\n\n The district court viewed FDA approval as being\n\npreclusive as to the validity of Studies MD-18 and MD-32. See\n\nPainters III, 289 F. Supp. 3d at 255–56. It also viewed the\n\nvalidity of those two studies as fatal to plaintiffs' attempt to\n\n - 33 -\n\fprove ineffectiveness with the type of evidence used in Neurontin.\n\nSee id. Given those views, the district court understandably\n\ndecided that further evidence on the question of effectiveness was\n\ncumulative and of no material import. See Painters II, 288 F.\n\nSupp. 3d at 487. Because we have now explained why the FDA's\n\napproval of Lexapro for its use in adolescents is not as preclusive\n\nas the district court might have reasonably thought, and because\n\nPainters and Ramirez have a live claim on the merits, one might\n\nreasonably expect Forest to search for responsive files within the\n\n\"Clinical Supply Group.\" Accordingly, we vacate the district\n\ncourt's discovery ruling so that on remand it can consider whether\n\nfurther discovery is called for in view of our decision in this\n\nappeal.\n\n V. Conclusion\n\n For the foregoing reasons, we reverse the district\n\ncourt's entry of summary judgment for Forest on Painters' and\n\nRamirez's RICO and state-law claims and vacate the district court's\n\ndenial of Painters' Rule 37 motion to compel supplemental\n\ndiscovery. At the same time, we affirm the district court's denial\n\nof Painters' motion for class certification. We award no costs to\n\nany party.\n\n\n\n\n - 34 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363803/", "author_raw": "KAYATTA, Circuit Judge"}]}
HOWARD
TORRUELLA
KAYATTA
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586550/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Painters and Allied Trades v. Forest Pharmaceuticals, Inc.\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\nNos. 18-1146, 18-1147\n\n IN RE: CELEXA AND LEXAPRO MARKETING AND\n SALES PRACTICES LITIGATION\n\n\nPAINTERS AND ALLIED TRADES DISTRICT COUNCIL 82 HEALTH CARE FUND;\n DELANA S. KIOSSOVSKI; RENEE RAMIREZ, on behalf of herself and\n all others similarly situated; MARLENE T. LOCONTE,\n\n Plaintiffs, Appellants,\n\n MARTHA PALUMBO, individually and on behalf of all other persons\nsimilarly situated; PETER PALUMBO, individually and on behalf of\n all other persons similarly situated; JAYNE EHRLICH,\n individually and on behalf of all other persons similarly\n situated; ANNA MURRET, individually and on behalf of all other\n persons similarly situated; UNIVERSAL CARE, INC.; ANGELA\n JAECKEL; MELVIN M. FULLMER, on behalf of himself and all others\n similarly situated; NEW MEXICO UFCW UNION'S AND EMPLOYER'S\n HEALTH AND WELFARE TRUST FUND, on behalf of itself and all\n others similarly situated; ALLIED SERVICES DIVISION WELFARE\n FUND, on behalf of itself and all others similarly situated;\n TARA JOHNDROW, individually and on behalf of all others\n similarly situated; BRIAN ANSON, individually and on behalf of\n all others similarly situated; SCOTT A. WILCOX, on behalf of\nhimself and all others similarly situated; MUNICIPAL REINSURANCE\nHEALTH INSURANCE FUND; RANDY MARCUS; BONNIE MARCUS; RUTH DUNHAM;\n TANYA SHIPPY; JILL POWELL,\n\n Plaintiffs,\n\n v.\n\n FOREST PHARMACEUTICALS, INC.; FOREST LABORATORIES, INC.; FOREST\nLABORATORIES, LLC, successor in interest to Forest Laboratories,\n Inc.,\n\n Defendants, Appellees,\n\n PFIZER, INC.; WARNER LAMBERT COMPANY,\n\f Defendants.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. Nathaniel M. Gorton, U.S. District Judge]\n\n\n Before\n\n Howard, Chief Judge,\n Torruella and Kayatta, Circuit Judges.\n\n\n R. Brent Wisner, with whom Michael L. Baum, Baum, Hedlund,\nAristei & Goldman, P.C., Christopher L. Coffin, and Pendley, Baudin\n& Coffin, LLP were on brief, for appellants.\n Andrew J. Ceresney, with whom Edwin G. Shallert, Kristin D.\nKiehn, J. Robert Abraham, Debevoise & Plimpton LLP, John G.\nO'Neill, and Sugarman, Rogers, Barshak & Cohen, P.C. were on brief,\nfor appellees.\n\n\n January 30, 2019\n\f KAYATTA, Circuit Judge. These consolidated appeals\n\narise out of two so-called \"off-label\" prescription-drug-marketing\n\ncases aggregated for pretrial proceedings in the District of\n\nMassachusetts by order of the multidistrict litigation panel.\n\nPlaintiffs claim that the defendants, Forest Pharmaceuticals, Inc.\n\nand Forest Laboratories, Inc. (collectively \"Forest\"), engaged in\n\nfraud to push their antidepressant drugs on unsuspecting minors\n\nfor whom the FDA had not approved the use of these medications.\n\nAs we will explain, we reverse the dismissal of the claims brought\n\nby two of the four plaintiffs, and we vacate the denial of\n\nplaintiffs' motion to compel the production of additional\n\ndocuments by Forest. We otherwise affirm the challenged district-\n\ncourt rulings, including the denial of class certification.\n\n I.\n\n We begin by summarizing the relevant statutory and\n\nregulatory framework and by reciting the facts relevant to the\n\nplaintiffs' summary-judgment appeal in the light most favorable to\n\nthe plaintiffs. See Boudreau v. Lussier, 901 F.3d 65, 71 (1st\n\nCir. 2018).\n\n A.\n\n The Federal Food, Drug, and Cosmetic Act (\"FDCA\")\n\nrequires drug manufacturers to obtain approval from the U.S. Food\n\nand Drug Administration (\"FDA\") before marketing a drug for a\n\nparticular medical use. 21 U.S.C. § 355(a); see also Mut. Pharm.\n\n - 3 -\n\fCo., Inc. v. Bartlett, 570 U.S. 472, 476 (2013). To secure that\n\napproval, the drug manufacturer must submit to the FDA either a\n\nnew-drug application (\"NDA\") or a supplemental new-drug\n\napplication (\"sNDA\"), and the manufacturer must demonstrate the\n\ndrug's efficacy for the indicated use in at least two double-\n\nblind, randomized-controlled trials (\"DBRCTs\"). See In re\n\nNeurontin Mktg. & Sales Practices Litig. (Kaiser), No. 04-cv-\n\n10739-PBS, 2011 WL 3852254, at *5 (D. Mass. Aug. 31, 2011), aff'd,\n\n712 F.3d 21 (1st. Cir. 2013); see generally 21 C.F.R. § 314.105.\n\nThe FDCA creates both civil and criminal penalties for drug\n\nmanufacturers that promote the use of approved drugs for unapproved\n\nuses (referred to here as \"off-label\" uses). See 21 U.S.C.\n\n§§ 331(d), 333(a), 355(a); Lawton ex rel. United States v. Takeda\n\nPharm. Co., 842 F.3d 125, 128 n.4 (1st Cir. 2016). The FDCA,\n\nhowever, does not prohibit doctors from prescribing drugs for off-\n\nlabel uses. Lawton ex rel. United States, 842 F.3d at 128 n.4.\n\n B.\n\n Forest manufactures and markets prescription drugs,\n\nincluding the antidepressant medications Celexa and Lexapro.\n\nCelexa and Lexapro are chemically similar selective serotonin\n\nreuptake inhibitors (\"SSRIs\"), a class of antidepressants that\n\naffect a patient's mood by blocking the reabsorption of the\n\nneurotransmitter serotonin in the brain, Eli Lilly & Co. v. Teva\n\nPharm. USA, Inc., No. 05-1044, 2005 WL 1635262, at *1 (Fed. Cir.\n\n - 4 -\n\fJuly 13, 2005). The FDA approved Celexa and Lexapro for the\n\ntreatment of major depressive disorder (\"MDD\") in adults (i.e.,\n\nindividuals aged eighteen or over) in 1998 and 2002, respectively.\n\nDrug manufacturers, including Forest, had difficulty demonstrating\n\nthat SSRIs were also effective in treating depression in children\n\nand adolescents. As of 2005, only Fluoxetine -- commercially known\n\nas Prozac -- had gained FDA approval for the treatment of pediatric\n\ndepression. In 2009, the FDA approved Lexapro for the treatment\n\nof depression in adolescents (i.e., individuals of ages twelve\n\nthrough seventeen). The FDA has never approved Celexa for any\n\npediatric use nor has it approved Lexapro as a treatment for\n\ndepression in children (i.e., individuals under the age of twelve).\n\n The record in this case nevertheless strongly suggests\n\nthat Forest engaged in a comprehensive off-label marketing scheme\n\nfrom 1998 through 2009 aimed at fraudulently inducing doctors to\n\nwrite pediatric prescriptions of Celexa and Lexapro when Forest\n\nhad insufficient reason to think that these drugs were effective\n\nfor the treatment of depression in children and adolescents.\n\nPlaintiffs have pointed to substantial evidence that Forest sought\n\nto achieve this illicit aim by: (1) promoting Celexa's efficacy\n\nfor the treatment of pediatric depression at medical conferences,\n\nat continuing-medical-education programs, and in press releases;\n\n(2) concealing negative clinical studies concerning Celexa's\n\nefficacy and safety; and (3) directly encouraging physicians to\n\n - 5 -\n\fprescribe Celexa and Lexapro for the treatment of pediatric\n\ndepression.\n\n For years, Forest nevertheless denied that it was\n\nengaged in the off-label promotion of these drugs. Forest\n\nLaboratories' Executive Vice President, Dr. Lawrence Olanoff,\n\ntestified before Congress in 2004 that \"because the FDA has not\n\napproved pediatric labeling for our products, Forest has always\n\nbeen scrupulous about not promoting the pediatric use of our\n\nantidepressant drugs, Celexa and Lexapro. That is the law, and we\n\nfollow it.\" Publication and Disclosure Issues in Antidepressant\n\nPediatric Clinical Trials: Hearing Before the Subcomm. on\n\nOversight & Investigations of the Comm. on Energy & Commerce, 108th\n\nCong. 82 (2004) (statement of Dr. Lawrence Olanoff).\n\n Even before Dr. Olanoff assured Congress of Forest's\n\nscrupulousness, a whistleblower had commenced a qui tam action,\n\nalleging that Forest had violated the False Claims Act (\"FCA\"), 31\n\nU.S.C. § 3729(a), by fraudulently marketing and promoting Celexa\n\nand Lexapro for the off-label treatment of depression in pediatric\n\npatients. Complaint, Gobble v. Forest Labs., Inc., No. 03-10395-\n\nNMG (D. Mass. Mar. 4, 2003), ECF No. 1. The United States later\n\nintervened in that suit, and, in February 2009, the district court\n\nunsealed the United States' complaint. Order Granting Motion to\n\nUnseal, United States ex rel. Gobble, No. 03-10395-NMG (D. Mass.\n\nFeb. 24, 2009), ECF No. 64. The evidence belying Dr. Olanoff's\n\n - 6 -\n\fassurances to Congress turned out to be quite substantial.\n\nUltimately, in September 2010, Forest paid a $39 million fine in\n\nconnection with pleading guilty to criminal violations of the FDCA\n\nfor its off-label promotion of Celexa between 1998 and 2002 and an\n\nadditional $149 million to the United States to settle civil claims\n\nthat Forest illegally promoted Celexa and Lexapro for pediatric\n\nuse in 2002 through 2005.\n\n C.\n\n Within the following four years, over a dozen consumers\n\nand entities who paid for prescription drugs filed the lawsuits\n\nthat led to this appeal. Initially, four plaintiffs joined in the\n\nnotice of appeal. Only two, Renee Ramirez and the Painters and\n\nAllied Trades District Council 82 Health Care Fund (\"Painters\")\n\nhave presented any argument on appeal. We refer to these two\n\ncollectively as \"plaintiffs.\"1 Ramirez purchased Celexa and\n\nLexapro for her young son from February 2003 through March 2010 on\n\nthe recommendation of her son's neurologist. Painters has\n\nreimbursed its pediatric insureds for off-label prescriptions of\n\nCelexa and Lexapro since early 1999. Plaintiffs together seek\n\n\n\n 1Marlene LoConte and Delena Kiossovski joined in the notice\nof appeal but subsequently filed no brief, and the single brief\nfiled by the other parties contains no argument at all for\nquestioning the grounds upon which the district court dismissed\nthe claims of LoConte and Kiossovski. We therefore deem their\nappeal of the judgments against them to be waived. See Vázquez-\nRivera v. Figueroa, 759 F.3d 44, 46-47 (1st Cir. 2014).\n\n - 7 -\n\frecovery under the Racketeer Influenced and Corrupt Organizations\n\nAct (\"RICO\"), 18 U.S.C. § 1962(c)–(d), the Minnesota Consumer\n\nFraud Act, Minn. Stat. § 325F.69, and the Minnesota Unfair Trade\n\nPractices Act, Minn. Stat. § 325D.13, and for unjust enrichment.\n\n In June 2016, the district court denied Painters' motion\n\nto certify two nationwide classes of similarly situated health-\n\ninsurance companies and health plans that had paid for or\n\nreimbursed off-label pediatric prescriptions of Celexa or Lexapro.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig. (Painters I),\n\n315 F.R.D. 116, 131 (D. Mass. 2016).2 In rejecting class\n\ncertification, the court reasoned that while Painters had\n\nsatisfied the Rule 23(a) numerosity, commonality, typicality, and\n\nadequacy requirements, Painters had failed to establish that\n\ncommon questions of fact or law predominated over individual issues\n\nas required by Rule 23(b)(3). Id. at 123–31.\n\n Subsequently, in March 2017, a dispute arose as a result\n\nof Forest's apparently belated production of two internal\n\nmemoranda in advance of a deposition conducted by agreement after\n\ndiscovery had otherwise closed. The two documents contained\n\n\n\n 2Painters' motion for class certification provided no time\nperiod for the proposed Celexa class. At oral argument, however,\nplaintiffs' counsel clarified that plaintiffs only seek to\nchallenge manufacturer-induced prescriptions for off-label uses\nmade prior to the FDA's approval of Lexapro for adolescent use in\nMarch 2009. Thus, we construe Painters' appeal in accordance with\nthis statement.\n\n - 8 -\n\fdetails regarding a study of Celexa's effectiveness. Forest\n\nrevealed that it had not sought any responsive documents from its\n\nClinical Supply Group in responding to Painters' discovery\n\nrequests. The district court nevertheless denied Painters' motion\n\nto compel Forest's supplemental production of documents from this\n\ngroup, concluding that any such production would be cumulative.\n\nIn re Celexa & Lexapro Mktg. & Sales Practices Litig.\n\n(Painters II), 288 F. Supp. 3d 483, 486–87 (D. Mass. 2018).\n\n In due course, after deeming discovery complete and\n\nruling on various interim motions, the district court entered\n\nsummary judgment for Forest on plaintiffs' RICO claims, holding\n\nthat neither Painters nor Ramirez could demonstrate injury. In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Painters III),\n\n289 F. Supp. 3d 247, 253–56 (D. Mass. 2018). The court then\n\nproceeded to dismiss plaintiffs’ state-based allegations as\n\nderiving from their noncognizable RICO claims. Id. at 258–59.\n\nThis appeal by Painters and Ramirez followed.\n\n II.\n\n Summary judgment is appropriate \"if the movant shows\n\nthat there is no genuine dispute as to any material fact and the\n\nmovant is entitled to judgment as a matter of law.\" Fed. R. Civ.\n\nP. 56(a). In granting summary judgment dismissing all of\n\nplaintiffs' claims, the district court concluded that plaintiffs\n\nhad no competent proof that either Celexa or Lexapro was\n\n - 9 -\n\fineffective for treating depression in children or adolescents.\n\nWe review this conclusion de novo. Martinez v. Petrenko, 792 F.3d\n\n173, 179 (1st Cir. 2015).\n\n A.\n\n Prevailing on a RICO claim requires proof of an economic\n\ninjury. See 18 U.S.C. § 1964(c) (\"Any person injured in his\n\nbusiness or property by reason of a violation of section 1962 of\n\nthis chapter may sue therefor.\"). Plaintiffs allege injury in the\n\nform of payments made for ineffective drugs.3 The district court\n\ntherefore turned its attention to determining whether plaintiffs\n\nhad enough evidence to allow a jury to find Celexa and/or Lexapro\n\nineffective for treating pediatric depression. See Painters III,\n\n289 F. Supp. 3d at 253–56. Four clinical trials and the FDA's\n\n2009 approval of Lexapro for adolescents informed the district\n\ncourt's decision.\n\n Starting in 1997, Lundbeck -- the developer of Celexa -\n\n- began conducting Study 94404, which focused on Celexa's efficacy\n\nin treating depression in adolescents. The study produced across-\n\nthe-board negative results. Forest then conducted Study MD-18 in\n\nan attempt to demonstrate Celexa's effectiveness in both children\n\n\n 3 In its opposition to Forest's motion for summary judgment,\nPainters argued that it need not demonstrate that Celexa and\nLexapro are ineffective in treating pediatric depression to\nestablish RICO injury. The district court rejected this argument\nin its order granting Forest's motion, and Painters has not\ndeveloped any challenge to that ruling on this appeal.\n\n - 10 -\n\fand adolescents. The efficacy results of MD-18 are difficult to\n\nassess because Forest bungled the study: Some participants\n\nrandomized into the active treatment group were dispensed\n\nnongeneric, pink tablets in one portion of the trial, potentially\n\nunblinding both the individuals who received these pills and the\n\nresearchers conducting the study. The MD-18 study only\n\ndemonstrated statistically positive results when these potentially\n\nunblinded participants were included. Finally, in 2002–2004 and\n\n2005-2007, Forest conducted two additional clinical trials. Study\n\nMD-15 examined Lexapro's efficacy in children and adolescents and\n\nachieved negative results. Study MD-32 set out to test Lexapro's\n\neffectiveness in treating only adolescents and achieved\n\nstatistically significant positive results.\n\n Based upon the results of MD-32 and the Celexa MD-18\n\nstudy, Forest submitted an sNDA to the FDA in 2008. In 2009, the\n\nFDA approved the application, allowing Forest to market Lexapro\n\nfor use in adolescents. Forest did not seek such approval for\n\nCelexa.\n\n Plaintiffs' evidence that Celexa and Lexapro were\n\nineffective for the pertinent indications consisted of the\n\nfollowing: The FDA has neither approved Celexa for treating\n\ndepression in children or adolescents nor has it approved Lexapro\n\nfor use in children; Study 94404 demonstrated only a detrimental\n\neffect of Celexa in treating depression in adolescents; Study MD-\n\n - 11 -\n\f18 was corrupted and showed no beneficial effect in children and\n\nadolescents unless the potentially unblinded participants are\n\nincluded in the results; and Study MD-15 produced uniformly\n\nnegative results in testing Lexapro's efficacy in children and\n\nadolescents. In addition, plaintiffs produced expert testimony\n\nopining that the positive results in MD-32 were not of clinical\n\nsignificance and that MD-18 should properly be considered a\n\nnegative trial. Plaintiffs also provided the results of a\n\n2016 meta-analysis study that found that neither Celexa nor\n\nLexapro had any more beneficial effect than a placebo in treating\n\npediatric depression.\n\n There is also evidence in the record before us, however,\n\nthat cuts the other way. In September 2002, the FDA accepted\n\nStudy MD-18 as a positive trial that would support a determination\n\nof Celexa's effectiveness for the treatment of MDD in adolescent\n\npatients. And in January 2003, the FDA also stated that MD-18\n\ncould be employed to support an application for FDA approval \"for\n\nboth Celexa and Lexapro, in pediatric patients with [MDD].\" The\n\nFDA relied in part on these findings in approving Lexapro for the\n\ntreatment of depression in adolescents in March 2009. Further,\n\nForest points out that neither Painters nor Prime Therapeutics\n\n(\"Prime\"), Painters' pharmacy-benefits manager, has taken any\n\neffort to limit or remove from its formulary pediatric\n\nprescriptions of Celexa and Lexapro.\n\n - 12 -\n\f This record raises two questions. First, do the FDA's\n\nvarious pronouncements or actions close the door on any effort to\n\nconvince a jury that either Celexa or Lexapro was ineffective?\n\nSecond, to the extent that the FDA's pronouncements and actions\n\nare not preclusive, is the evidence in this case nevertheless\n\ninsufficient to support a jury finding of ineffectiveness?\n\n 1.\n\n Forest claims that two of our recent decisions --\n\nD'Agostino v. ev3, Inc., 845 F.3d 1 (1st Cir. 2016), and In re\n\nCelexa & Lexapro Mktg. & Sales Practices Litig. (Marcus), 779 F.3d\n\n34 (1st Cir. 2015) -- answer the first question in the affirmative\n\nby deeming FDA approval dispositive. Even were we to find it\n\nconvincing, this argument would not cover all the challenged uses\n\nat issue in this appeal. The FDA has never approved Celexa for\n\nany of the off-label uses for which Forest promoted it. Nor has\n\nit approved Lexapro for the treatment of MDD in children under the\n\nage of twelve. So Forest's reliance on actual FDA approval to\n\nforeclose a jury determination of inefficacy must be limited to\n\nForest's marketing of Lexapro for adolescent use and, perhaps as\n\nwell, to the question of how to construe MD-18.\n\n In any event, even as thus limited, we do not find\n\nForest's reliance on D'Agostino convincing. The claim in\n\nD'Agostino concerned the sale of medical devices after the FDA had\n\napproved the devices for the uses for which they were sold.\n\n - 13 -\n\fD'Agostino, 845 F.3d at 3, 7–9. In rejecting a challenge to those\n\npost-approval sales under the False Claims Act based on alleged\n\npre-approval fraud on the FDA, we reasoned that \"[t]o rule\n\notherwise would be to turn the FCA into a tool with which a jury\n\nof six people could retroactively eliminate the value of FDA\n\napproval and effectively require that a product largely be\n\nwithdrawn from the market even when the FDA itself sees no reason\n\nto do so.\" Id. at 8. Here, by contrast, plaintiffs challenge\n\nonly the promotion of Celexa and Lexapro for uses that were off-\n\nlabel (i.e., not FDA-approved) at the time Forest promoted and\n\nsold the drugs.4 When Forest is said to have made those marketing\n\nefforts, it could not have pleaded reliance on FDA approval. If\n\na jury were to hold Forest liable for such pre-approval marketing,\n\nit would simply be telling Forest that it should not have marketed\n\nthat which Congress under the FDCA does not want it to market:\n\ndrugs for unapproved uses. We therefore see no reason to accord\n\nto Forest the preclusive protection for pre-approval promotion\n\nthat FDA approval provided the medical-device manufacturer for\n\npost-approval conduct in D'Agostino.5\n\n\n 4 Though plaintiffs' complaints do not explicitly limit their\nRICO and state-law claims to the period prior to FDA's March 2009\napproval of Lexapro, plaintiffs' counsel indicated at oral\nargument that plaintiffs do not challenge Forest's post-approval\nmarketing of Celexa and Lexapro.\n 5 For similar reasons, Forest's reliance on Buckman Co. v.\nPlaintiffs' Legal Comm., 531 U.S. 341, 348 (2001), in which the\nSupreme Court rejected as preempted state fraud-on-the-FDA claims,\n - 14 -\n\f Nor does our opinion in Marcus aid Forest in this case.\n\nIn Marcus, we rejected a challenge to a drug label based on\n\ninformation that was \"plainly known to the FDA prior to approving\n\nthe label.\" 779 F.3d at 43. We made clear in doing so, however,\n\nthat we were merely applying the state-law preemption principles\n\nthe U.S. Supreme Court laid out in PLIVA, Inc. v. Mensing, 564\n\nU.S. 604 (2011), and Wyeth v. Levine, 555 U.S. 555 (2009). See\n\nMarcus, 779 F.3d at 40–43 (explaining that a drug manufacturer can\n\nonly be held liable under state law for inadequate warning in an\n\nFDA-approved label when the drug manufacturer can, \"of its own\n\nvolition, . . . strengthen its label in compliance with its state\n\ntort duty\" (quoting PLIVA, Inc., 564 U.S. at 624)). Marcus,\n\naccordingly, is inapposite.\n\n This is not to say that the FDA's 2009 approval of\n\nForest's sNDA for Lexapro is irrelevant to this case. Certainly\n\nthe approval and the FDA's reliance on MD-18 provide what many\n\njurors may view as strong evidence confirming that Lexapro, and\n\nperhaps Celexa as well, have always been efficacious in treating\n\npediatric depression. The common law has long recognized that\n\nagency approval of this type is relevant in tort suits. See\n\nRestatement (Third) of Torts: Prod. Liab. § 4 (Am. Law Inst. 1998)\n\n\nand its progeny is misplaced. Plaintiffs question the efficacy of\nCelexa and Lexapro only for off-label uses; their claims,\naccordingly, are not predicated on a fraud-on-the-FDA theory of\nliability.\n\n - 15 -\n\f(\"[C]ompliance with an applicable product safety statute . . . is\n\nproperly considered in [a product defect case].\"). But the common\n\nlaw also recognizes that such evidence is not always preclusive.\n\nId. (\"[S]uch compliance does not preclude as a matter of law a\n\nfinding of product defect.\"). And while there are strong reasons\n\nfor treating such evidence as preclusive when the challenged sales\n\nare made in reliance on agency approval, those same reasons cut\n\nthe other way when the sales are made without approval, and\n\ncertainly when made unlawfully, as we must assume they were here.\n\n 2.\n\n Having decided that the FDA's subsequent approval of\n\nLexapro does not preclude proving that pre-approval uses of these\n\ndrugs were ineffective, we turn to addressing whether plaintiffs\n\nmay proceed with a claim based on product ineffectiveness when the\n\nevidence of efficacy is conflicting. This is more or less the\n\nquestion we left unanswered in Kaiser. See Kaiser, 712 F.3d at 49\n\n(declining to address what evidentiary standard would be needed to\n\ndemonstrate efficacy \"if the results of DBRCTs were equivocal\" or\n\n\"if there were a different mix of DBRCT and non-DBRCT evidence\").6\n\n\n 6 To advance its preferred interpretation of the term\n\"equivocal\" in Kaiser, each party dedicates a significant portion\nof its brief to sparring over whether the DBRCT evidence in the\nNeurontin cases was, in fact, mixed. We need not address this\nquestion because, as we explain, Painters' RICO claim survives\nsummary judgment even though the evidence of inefficacy is mixed.\nWe note, however, that the DBRCTs in the Neurontin case were not\nuniformly negative as Forest would have us believe. Rather, the\n - 16 -\n\f Generally speaking, \"conflicting evidence\" is the\n\nhallmark of an issue that calls for factfinding, not summary\n\njudgment. See, e.g., Adria Int'l Grp. v. Ferre Dev., Inc., 241\n\nF.3d 103, 111 (1st Cir. 2001) (finding summary judgment\n\ninappropriate when evidence presented was \"contested and\n\ncontradictory\"); see also 10A Charles Alan Wright et al., Federal\n\nPractice and Procedure § 2712 (4th ed. 2018) (\"[S]ummary judgment\n\nis not a substitute for the trial of disputed fact issues.\"). We\n\nsee no reason to deviate from that general rule merely because the\n\nproduct marketed illegally is one that was later approved for\n\nlawful sales.7 In short, why should we forgo customary fact-\n\nfinding by the jury so as to reward unlawful conduct aimed at\n\ngetting children to consume unapproved drugs?\n\n Forest also argues that plaintiffs' evidence of\n\nineffectiveness falls short of proving injury because Painters has\n\nnot produced \"individualized\" proof that Celexa or Lexapro was\n\nineffective for any particular insured. By \"individualized\"\n\nproof, Forest appears to mean testimony from a patient (or from a\n\n\ndistrict court noted both positive and negative clinical studies\nin reviewing the parties' evidence of Neurontin's efficacy for the\nat-issue off-label conditions. See Kaiser, 2011 WL 3852254, at\n*34–46 (reviewing mixed DBRCT results).\n 7\n Nor is summary judgment for Forest warranted due to the fact\nthat Painters has not directed the removal of Celexa and Lexapro\nfor pediatric uses from its drug formulary. As we held in Kaiser,\nit is \"within the factfinder's province to weigh this evidence.\"\nKaiser, 712 F.3d at 41.\n\n - 17 -\n\fdoctor concerning that patient) that the patient experienced no\n\nbeneficial effects from the drug. While evidence of that type\n\ncould be probative, certainly it is not the only way to prove that\n\na drug is ineffective. Indeed, given that (1) an ineffective drug\n\nmay trigger a placebo effect in a given individual and (2) an\n\neffective drug may not benefit all users, individualized proof\n\nmight well be less probative than the type of expert, study-based\n\ntestimony that plaintiffs have offered. In any event, as we\n\nalready held, such individualized proof is certainly not required.\n\nSee In re Neurontin Mtkg. & Sales Practices Litig. (Harden), 712\n\nF.3d 60, 69 (1st Cir. 2013) (\"[W]e reject Pfizer's position that\n\nthese plaintiffs must prove the individual, subjective\n\nineffectiveness of each off-label prescription in order to\n\nestablish injury. . . . The Harden plaintiffs have proffered\n\nclinical trial evidence that Neurontin is ineffective . . ., which\n\nis certainly enough to raise a genuine issue of fact on the\n\neffectiveness issue.\" (citation omitted)); In re Neurontin Mtkg.\n\n& Sales Practices Litig. (Aetna), 712 F.3d 51, 59–60 (1st Cir.\n\n2013).\n\n In sum, we hold that the FDA's 2009 approval of Lexapro\n\ndoes not preclude a jury from concluding that the off-label uses\n\nof Celexa and Lexapro at issue in this case were ineffective in\n\ntreating pediatric depression. Moreover, plaintiffs have provided\n\ncompetent and sufficient evidence -- through DBRCTs, expert\n\n - 18 -\n\ftestimony, and peer-reviewed literature -- to raise a genuine issue\n\nof material fact as to the efficacy of these drugs for pediatric\n\nuse. Accordingly, the district court erred in granting summary\n\njudgment for Forest on plaintiffs' RICO and state-law claims on\n\nthis basis.\n\n B.\n\n In addition to demonstrating economic injury, a RICO\n\nplaintiff must prove that the defendant's racketeering conduct\n\ncaused her injury. 18 U.S.C. § 1964(c); Holmes v. Sec. Inv'r Prot.\n\nCorp., 503 U.S. 258, 268 (1992) (interpreting section 1964(c)'s\n\nlanguage to mean that a RICO plaintiff must show both but-for and\n\nproximate causation to establish standing). As we have already\n\nnoted, physicians can -- and do -- lawfully prescribe prescription\n\ndrugs for off-label uses, even though the manufacturer is barred\n\nby law from promoting such prescriptions. See Lawton ex rel.\n\nUnited States, 842 F.3d at 128 n.4. So for any given prescription\n\nin this case, one would reasonably ask whether Forest's efforts to\n\nprofit by illegally marketing drugs for pediatric use caused a\n\nparticular prescription to be made, or whether, instead, the doctor\n\nwrote a given prescription based on his or her own professional\n\nmedical judgment (perhaps reasoning that what works for an adult\n\npatient might also work for a younger patient).\n\n Forest therefore urges that, even if we disagree with\n\nthe district court on the issue of injury/efficacy, we should still\n\n - 19 -\n\faffirm the entry of summary judgment due to Painters' lack of proof\n\nof but-for causation. While the district court did not consider\n\nthe issue of causation in its summary-judgment ruling, it did\n\nearlier assay Painters' causation evidence in ruling on Painters'\n\nmotion for class certification. The district court labeled the\n\nproof so \"insubstantial\" and \"fundamentally flawed\" \"as to\n\npreclude class certification.\" Painters I, 315 F.R.D. at 126–28.\n\nForest would have us interpret these pronouncements as a finding\n\nthat the evidence was insufficient as a matter of law to prove\n\nbut-for causation.\n\n We disagree. In the first place, it is unclear why the\n\ndistrict court gauged the substantiality or merit of plaintiffs'\n\nproof in the context of a Rule 23 motion. The central issue in\n\nthat context is not whether the method of proof would or could\n\nprevail. Rather, it is whether the method of proof would apply in\n\ncommon to all class members. See, e.g., Tyson Foods, Inc. v.\n\nBouaphakeo, 136 S. Ct. 1036, 1047 (2016) (\"When . . . 'the concern\n\nabout the proposed class is not . . . some fatal dissimilarity\n\nbut, rather, a fatal similarity -- [an alleged] failure of proof\n\nas to an element of the plaintiffs' cause of action -- courts\n\nshould engage that question as a matter of summary judgment, not\n\nclass certification.'\" (alteration in original) (quoting Richard\n\nA. Nagareda, Class Certification in the Age of Aggregate Proof, 84\n\nN.Y.U. L. Rev. 97, 107 (2009))).\n\n - 20 -\n\f More substantively, Painters' evidence does not seem\n\nclearly insufficient. There is ample evidence that Forest spent\n\nmoney inducing doctors to prescribe its drugs to pediatric patients\n\nand that it would not have done so had the effort not been worth\n\nthe money. Two experts, Dr. Meredith Rosenthal and\n\nDr. Christopher Baum, also opined that Forest's spending on\n\npromotions in general correlated positively with sales. As the\n\ndistrict court pointed out, Painters' experts then assumed that\n\nthis same approximate correlation applied to off-label promotional\n\nspending and off-label sales. Painters I, 315 F.R.D. at 127. The\n\ndistrict court thought this assumption to be a \"fundamental flaw\"\n\nin the analysis. Id. Why, exactly, we are not sure. After all,\n\nwhy would Forest, which knew its markets better than anyone, have\n\nspent money on off-label marketing over the long term if it\n\ngenerated lower returns than would additional spending on less\n\nrisky, lawful marketing? Certainly there is room for reasonable\n\ndisagreement on the merits of Dr. Rosenthal and Dr. Baum's\n\nassumption.\n\n If the jury accepts this assumption as reasonable, and\n\nif it finds that the prescriptions that Painters paid for were\n\ntypical of those that the experts analyzed, jurors would then have\n\na fair path to finding that Forest's off-label marketing caused\n\nPainters to pay for ineffective drugs. The experts' interpretation\n\nof the data indicated that Forest's off-label promotions caused\n\n - 21 -\n\f76% and 54% of all pediatric prescriptions of Celexa and Lexapro,\n\nrespectively. Dr. Rosenthal estimated that if Painters paid for\n\nas few as five independent prescriptions, there would be a 98%\n\nchance that at least one was the result of off-label marketing.\n\nIn fact, Painters likely paid for the Celexa or Lexapro\n\nprescriptions of more than five different patients.8 So the odds\n\nthat Painters was not harmed if the drugs were, indeed, ineffective\n\nwas likely infinitesimal (assuming the prescriptions were\n\nindependent of one another).9\n\n\n\n\n 8In its summary judgment order, the district judge observed\nthat Painters reimbursed sixteen of its pediatric insureds for\nseventy-two off-label prescriptions of Celexa from 1999 through\n2004, and thirty-one of its pediatric insureds for 234 off-label\nprescriptions of Lexapro from 2002 through early 2015. Painters\nIII, 289 F. Supp. 3d at 251. It is not clear from the record how\nmany of these Lexapro prescriptions were written prior to March\n2009. Viewing this evidence in the light most favorable to\nPainters, Ellis v. Fidelity Mgmt. Tr. Co., 883 F.3d 1, 3, (1st\nCir. 2018), and without any counter-argument on this point by\nForest, we assume for purposes of this appeal only that well more\nthan five of the aforementioned Lexapro prescriptions were filled\nprior to the FDA's 2009 approval of Lexapro.\n 9The statistical proof in this instance is being used only\nto prove that a group of prescriptions likely includes at least\none that a certain activity caused, and it is then being utilized\nto estimate the percentage of such causally connected\nprescriptions in that group. Painters proposes no use of the\nstatistical data to prove that Forest's off-label marketing caused\nany particular prescription to be written. See In re Asacol\nAntitrust Litig. (Asacol), 907 F.3d 42, 54 (1st Cir. 2018) (finding\nit \"far from self-evident\" that expert testimony opining that\n\"ninety percent of class members were injured\" would be \"sufficient\nto prove that any given individual class member was injured\").\n\n - 22 -\n\f Nor is Painters' evidence limited to the thrust of its\n\nstatistics. Painters also has evidence that Forest sales\n\nrepresentatives called or visited at least two physicians who\n\nsubsequently ordered pediatric prescriptions of Celexa and Lexapro\n\nthat Painters reimbursed. In addition, Painters produced evidence\n\nsuggesting that Forest specifically targeted Painters' pharmacy-\n\nbenefits manager, Prime, and that Prime relied upon a misleading\n\nreport by Forest of Study MD-18 in managing Painters' formulary.\n\nAll together, this is surely enough to raise a triable issue of\n\nfact as to whether Forest's off-label marketing caused Painters to\n\npay for a prescription for which it would not have otherwise paid.\n\n This is not to say that Painters will ultimately prevail\n\non the issue of causation. The district court has not conducted\n\na Daubert analysis. And there may be other potential bones to\n\npick with the sufficiency of Painters' proof of causation. As the\n\nrecord now stands, though, we agree with Painters that we cannot\n\naffirm the summary judgment finding that its causation proof is\n\ninsufficient as a matter of law.\n\n As for Ramirez, Forest did not challenge her standing on\n\nthe basis of causation in its memorandum in support of its motion\n\nfor summary judgment. Accordingly, we express no opinion as to\n\nwhether Ramirez has raised a triable issue on RICO causation. See\n\nRosaura Bldg. Corp. v. Municipality of Mayagüez, 778 F.3d 55, 63\n\n\n\n - 23 -\n\f(1st Cir. 2015) (\"Time and time again we have held that arguments\n\nnot advanced before the district court are waived.\").\n\n As for proximate causation, it is of no moment that\n\npediatricians were the immediate target of Forest's fraudulent\n\nmarketing. Here, as in Kaiser, a jury could find that Painters\n\nand Ramirez were \"the primary and intended victims of [Forest's]\n\nscheme to defraud.\" Kaiser, 712 F.3d at 37 (quoting Bridge v.\n\nPhx. Bond & Indem. Co., 553 U.S. 639, 650 (2008)). Moreover,\n\nPainters' and Ramirez's alleged harm (i.e., reimbursing or\n\npurchasing more pediatric prescriptions than they otherwise would\n\nhave) was a \"foreseeable and natural consequence\" of Forest's\n\nscheme. Bridge, 553 U.S. at 658. Indeed, it was precisely the\n\npoint.\n\n Accordingly, for the foregoing reasons, we reverse the\n\ndistrict court's entry of summary judgment for Forest on Painters'\n\nRICO and state-law claims and on Ramirez's RICO and unjust-\n\nenrichment claims.\n\n III.\n\n Early on in this litigation the district court denied\n\nPainters' motion to certify this case as a class action under\n\nFederal Rule of Civil Procedure 23(b)(3). In so ruling, the\n\ndistrict court reasoned that a variety of important issues,\n\nincluding causation and injury, would pose individual questions\n\nthat would need to be answered for each class member. Painters I,\n\n - 24 -\n\f315 F.R.D. at 123–30. The presence of these individual questions,\n\nreasoned the district court, defeated Painters' effort to satisfy\n\nthe requirement of Rule 23(b)(3) that common issues must\n\npredominate. Id. Painters now appeals that ruling as it applies\n\nto classes consisting of third-party payors (\"TPP\") who paid for\n\nor reimbursed prescriptions of Celexa or Lexapro prior to early\n\n2009. It is not clear why those issues to which the district court\n\npointed would preclude certification of such a class. As we have\n\nalready explained, Painters' clinical and statistical evidence, if\n\nbelieved, could establish causation and injury at least for any\n\nTPP who paid for more than a handful of different patients'\n\nprescriptions. Nevertheless, as we will explain, it has become\n\napparent that the proper application of the statute of limitations,\n\nwhile preserving plaintiffs' individual claims, precludes\n\nPainters' attempt to maintain a class action.\n\n A.\n\n The parties agree that the applicable statutory\n\nlimitations period is four years. See Agency Holding Corp. v.\n\nMalley-Duff & Assocs., Inc., 483 U.S. 143, 156 (1987). That four-\n\nyear period began to run \"at the time [the] plaintiff knew or\n\nshould have known of his injury.\" Lares Grp., II v. Tobin, 221\n\nF.3d 41, 44 (1st Cir. 2000) (citing Rodriguez v. Banco Central,\n\n917 F.2d 664, 665 (1st Cir. 1990)). The injury here is the payment\n\nmade on account of off-label prescriptions that Forest induced.\n\n - 25 -\n\fSee Kaiser, 712 F.3d at 39 (\"[E]conomic injury occur[s] when\n\n[plaintiff] paid for fraudulently induced [drug] prescriptions.\").\n\nSo, the key question becomes: By what date can we say, as a matter\n\nof law, that Painters knew or should have known that Forest was\n\npromoting the off-label, ineffective use of Celexa or Lexapro?\n\n The district court found that date to be no later than\n\nMarch of 2009. In re Celexa & Lexapro Mktg. & Sales Practices\n\nLitig., 65 F. Supp. 3d 283, 289 (D. Mass. 2014). In February of\n\nthat year, the United States unsealed its complaint against Forest\n\nin United States ex rel. Gobble, which detailed in thirty-three\n\npages how \"Forest engaged in a fraudulent scheme to market and\n\npromote Celexa . . . and Lexapro . . . off-label to treat\n\ndepression and other psychiatric conditions in pediatric\n\npatients.\" Complaint at 2, United States ex rel. Gobble, No. 03-\n\n10395-NMG (D. Mass. Feb. 13, 2009), ECF No. 61 [hereinafter United\n\nStates' Complaint]. Within weeks, two private class-action\n\ncomplaints followed, one in New York and another in Missouri, each\n\nalso alleging a fraudulent scheme to market Celexa and Lexapro for\n\nineffective, off-label uses. See Class Action Complaint,\n\nUniversal Care, Inc. v. Forest Pharm., Inc., No. 09-cv-11518-NMG\n\n(D. Mass. Mar. 20, 2009), ECF No. 1; Class Action Complaint, N.M.\n\nUFCW Union's & Emp'rs' Health & Welfare Tr. Fund v. Forest Labs.,\n\nInc., No. 09-cv-11524-NMG (D. Mass. Mar. 12, 2009), ECF No. 1.\n\nPainters never argued before the district court that it was unaware\n\n - 26 -\n\fof the United States' complaint or the March 2009 lawsuits. Nor\n\ndoes it so argue on appeal. Rather, it argues that the lawsuits\n\ndid not provide enough notice that Forest had been promoting the\n\noff-label use of Celexa and Lexapro. Such notice, Painters says,\n\nwas not available until Forest's own public admission to that\n\neffect in November 2010, when it both pleaded guilty to criminal\n\nviolations of the FDCA and entered into a civil settlement\n\nagreement with the United States.\n\n Not surprisingly, Painters points to no case law holding\n\nthat a statutory limitations period does not start to run until\n\nthe potential defendant first delivers a gift-wrapped admission of\n\nits alleged wrongdoing. Were that the rule, very few limitations\n\nperiods would ever commence, much less conclude. Instead, as we\n\nhave explained in an analogous context, \"[w]e look first to whether\n\nsufficient facts were available to provoke a reasonable person in\n\nthe plaintiff's circumstances to inquire or investigate\n\nfurther. . . . Once a duty to inquire is established, the\n\nplaintiff is charged with the knowledge of what he or she would\n\nhave uncovered through a reasonably diligent investigation.\"\n\nMcIntyre v. United States, 367 F.3d 38, 52 (1st Cir. 2004); see\n\nalso Sanchez v. United States, 740 F.3d 47, 52 (1st Cir. 2014)\n\n(\"The discovery rule incorporates an objective standard. To delay\n\ncommencement of the running of the statute of limitations, 'the\n\nfactual basis for the cause of action must have been inherently\n\n - 27 -\n\funknowable, [that is, not capable of detection through the exercise\n\nof reasonable diligence] at the time of injury.'\" (alteration in\n\noriginal) (quoting Gonzalez v. United States, 284 F.3d 281, 288–\n\n89 (1st Cir. 2002))). The same fundamental principle applies to\n\nRICO suits. See Rotella v. Wood, 528 U.S. 549, 555 (2000)\n\n(\"Federal courts . . . generally apply a discovery accrual rule\n\nwhen a statute is silent on the issue, as civil RICO is here. . . .\n\n[D]iscovery of the injury . . . is what starts the clock.\"\n\n(citations omitted)); Koch v. Christie's Int'l PLC, 699 F.3d 141,\n\n150–51 (2d Cir. 2012) (noting that a RICO claim does not accrue\n\nuntil a plaintiff has \"actual or inquiry notice of the injury\"\n\n(quoting In re Merrill Lynch Ltd. P'ships Litig., 154 F.3d 56, 60\n\n(2d Cir. 1998))).\n\n We agree with the district court that the unsealing of\n\nthe United States' complaint and the subsequent lawsuits filed in\n\nMarch 2009 were more than sufficient to put a TPP like Painters on\n\nnotice that Forest had likely been inducing off-label\n\nprescriptions of Celexa and Lexapro. The United States' complaint\n\nchronicled how Forest suppressed a negative study on Celexa while\n\npromoting a positive study (which conveniently neglected to\n\nmention the earlier, negative study). United States' Complaint at\n\n3, 14. The complaint quoted internal Forest communications and\n\nrecounted the precise details of Forest's unlawful promotional\n\nactivities. Id. at 15–22. It quoted Forest's physician-call notes\n\n - 28 -\n\freporting on the efforts of Forest's sales representatives to\n\npromote the pediatric use of the drugs. E.g., id. at 20 (\"[F]ocus\n\non Lexapro efficacy at just 10 mg., great choice for\n\nchild/adolescents.\"). It also named Forest marketing executives,\n\ne.g., id. at 23, and outside physicians involved in the promotion\n\ncampaigns, e.g., id. at 21–22. It is inconceivable that any TPP\n\nlike Painters would not have found in the complaint a very strong\n\nprobability that Forest had systematically and fraudulently pushed\n\nits drugs on unsuspecting children.\n\n Nevertheless, we also agree with the district court that\n\nPainters survived Forest's statute-of-limitations defense because\n\nthe running of the limitations period was stayed for more than\n\neight months by the filing of the N.M. UFCW class action in March\n\n2009. See In re Celexa & Lexapro Mktg. & Sales Practices Litig.,\n\n65 F. Supp. 3d at 291. Painters was a member of the putative RICO\n\nclass action for which the N.M. UFCW complaint sought\n\ncertification. Under American Pipe & Construction Co. v. Utah,\n\n414 U.S. 538 (1974), the limitations period during which Painters\n\nmight sue on its own behalf was therefore tolled until the N.M.\n\nUFCW class action was dismissed in June 2010. Forest did not cross\n\nappeal the district court's application of American Pipe. Rather,\n\nForest argues only that the limitations period began running long\n\nbefore March of 2009 when plaintiffs first should have suspected\n\nthat Celexa and Lexapro were ineffective for pediatric use. We\n\n - 29 -\n\freject that argument because the injury here is paying for\n\nunlawfully induced off-label prescriptions, not merely physician-\n\ndirected, off-label prescriptions.\n\n B.\n\n Even though plaintiffs can sue, thanks to American Pipe,\n\nPainters cannot parlay that dispensation into the much-delayed\n\nfiling of a class action. See China Agritech, Inc. v. Resh, 138\n\nS. Ct. 1800 (2018). In American Pipe, the Supreme Court held that\n\nthe \"commencement of [a putative class action] tolls the running\n\nof the statute for all purported members of the class who make\n\ntimely motions to intervene after the court has found the suit\n\ninappropriate for class action status.\" 414 U.S. at 552-53. China\n\nAgritech clarified that this tolling rule has limits: While a\n\nputative class member may join an existing suit or file an\n\nindividual action upon denial of class certification, a putative\n\nclass member may not commence a class action anew beyond the time\n\nallowed by the untolled statute of limitations. 138 S. Ct. at\n\n1807 (\"The 'efficiency and economy of litigation' that support\n\ntolling of individual claims do not support maintenance of untimely\n\nsuccessive class actions; any additional class filings should be\n\nmade early on, soon after the commencement of the first action\n\nseeking class certification.\" (citation omitted) (quoting Am.\n\nPipe, 414 U.S. at 553)).\n\n\n\n - 30 -\n\f Painters argues that China Agritech is distinguishable\n\nfrom the case at hand because there was no substantive ruling on\n\nclass certification in N.M. UFCW; the first time any district court\n\naddressed class certification was in Painters' case. Painters'\n\nposition relies on an impermissibly narrow reading of the Court's\n\ndecision in China Agritech. Though the Supreme Court granted\n\ncertiorari in that case to answer the narrow question of whether\n\na putative class member may commence a class action beyond the\n\nlimitations period upon the district court's denial of a request\n\nfor class certification filed within the statute of limitations,\n\nid. at 1804, the Court proceeded to provide a broader answer: Its\n\nprecedents do not \"so much as hint[] that [American Pipe] tolling\n\nextends to otherwise time-barred class claims,\" id. at 1806. Thus,\n\nthe Court effectively ruled that the tolling effect of a motion to\n\ncertify a class applies only to individual claims, no matter how\n\nthe motion is ultimately resolved. To hold otherwise would be to\n\nallow a chain of withdrawn class-action suits to extend the\n\nlimitations period forever.\n\n For the foregoing reasons, the district court did not\n\nabuse its discretion in declining to certify Painters' proposed\n\nnationwide class of TPPs.\n\n IV.\n\n Finally, Painters also takes issue with the district\n\ncourt's denial of its motion to compel Forest's supplemental\n\n - 31 -\n\fproduction of documents related to the MD-18 Study. This court\n\nreviews a district court's discovery decision for abuse of\n\ndiscretion, intervening \"only upon a clear showing of manifest\n\ninjustice, that is, where the lower court's discovery order was\n\nplainly wrong and resulted in substantial prejudice to the\n\naggrieved party.\" Pina v. Children's Place, 740 F.3d 785, 791\n\n(1st Cir. 2014) (quoting Dennis v. Osram Sylvania, Inc., 549 F.3d\n\n851, 859 (1st Cir. 2008)).\n\n Here, it is undisputed that Forest did not perform an\n\nexhaustive search in response to Painters' requests for documents\n\nrelated to the MD-18 Study: Indeed, Forest acknowledges\n\n(employing the passive voice) that \"files within the custody of\n\nthe Clinical Supply Group were not searched.\" Forest also does\n\nnot deny that its own preliminary search within this group -- after\n\ndiscovery had closed -- produced two responsive memoranda\n\nregarding the packaging error in the MD-18 Study. The only excuse\n\nForest provides is that \"[p]laintiffs were fully apprised of the\n\nscope of document collection and were aware that files within the\n\ncustody of the Clinical Supply Group were not searched.\" Forest,\n\nhowever, points us to nothing in the record demonstrating that\n\nPainters acquiesced to Forest's limiting the scope of its document\n\ncollection in this way. These admissions notwithstanding, the\n\ndistrict court denied Painters' Rule 37 motion to compel the\n\nsupplementary production of documents related to the MD-18 Study.\n\n - 32 -\n\fIt reasoned that the Rule 26(e)(1) duty to supplement only applies\n\nwhen \"the supplemental material has not been otherwise made known\n\nto the requesting party\" and observed that Painters had already\n\nreceived \"substantial production of documents related to the\n\npackaging error\" such that any new production would be cumulative.\n\nPainters II, 288 F. Supp. 3d at 487.\n\n Rule 26(e)(1) requires that a party who has responded to\n\na request for production supplement its response in a timely manner\n\n\"if the party learns that in some material respect the . . .\n\nresponse is incomplete . . . and if the additional . . .\n\ninformation has not otherwise been made known to the other parties\n\nduring the discovery process.\" Fed. R. Civ. P. 26(e)(1). Whether\n\nor not \"information has not otherwise been made known\" -- and,\n\nthus, whether or not additional production would be cumulative --\n\nnecessarily hinges on the relevance that the additional production\n\nmight have for the requesting party's claims and the complexity of\n\nthe issue that the factfinder is tasked to resolve; clearly, a\n\nrelatively high degree of granularity in document production is to\n\nbe expected in technical matters of great significance to a party's\n\noverall claim.\n\n The district court viewed FDA approval as being\n\npreclusive as to the validity of Studies MD-18 and MD-32. See\n\nPainters III, 289 F. Supp. 3d at 255–56. It also viewed the\n\nvalidity of those two studies as fatal to plaintiffs' attempt to\n\n - 33 -\n\fprove ineffectiveness with the type of evidence used in Neurontin.\n\nSee id. Given those views, the district court understandably\n\ndecided that further evidence on the question of effectiveness was\n\ncumulative and of no material import. See Painters II, 288 F.\n\nSupp. 3d at 487. Because we have now explained why the FDA's\n\napproval of Lexapro for its use in adolescents is not as preclusive\n\nas the district court might have reasonably thought, and because\n\nPainters and Ramirez have a live claim on the merits, one might\n\nreasonably expect Forest to search for responsive files within the\n\n\"Clinical Supply Group.\" Accordingly, we vacate the district\n\ncourt's discovery ruling so that on remand it can consider whether\n\nfurther discovery is called for in view of our decision in this\n\nappeal.\n\n V. Conclusion\n\n For the foregoing reasons, we reverse the district\n\ncourt's entry of summary judgment for Forest on Painters' and\n\nRamirez's RICO and state-law claims and vacate the district court's\n\ndenial of Painters' Rule 37 motion to compel supplemental\n\ndiscovery. At the same time, we affirm the district court's denial\n\nof Painters' motion for class certification. We award no costs to\n\nany party.\n\n\n\n\n - 34 -\n[END_CASE]", "role": "user" } ]
4,586,551
MetalForming, Inc. v. Schechtl Maschinenbau Gmbh
2019-01-30
18-1550P
U.S. Court of Appeals for the First Circuit
{"judges": "Before Lynch, Stahl, and Barron, Circuit Judges.", "parties": "", "opinions": [{"author": "LYNCH, Circuit Judge", "type": "010combined", "text": "United States Court of Appeals\n For the First Circuit\n\n\nNos. 18-1550\n 18-1551\n\n STEPHEN D. KNOX; JEAN KNOX,\n\n Plaintiffs, Appellants,\n\n v.\n\n METALFORMING, INC.,\n\n Defendant, Appellant,\n\n SCHECHTL MASCHINENBAU GMBH,\n\n Defendant, Appellee.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. George A. O'Toole, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Benjamin R. Zimmermann, with whom Stacey L. Pietrowicz and\nSugarman and Sugarman, P.C. were on brief, for Stephen and Jean\nKnox.\n Javier F. Flores, with whom Eric V. Skelly, Thaddeus M.\nLenkiewicz, and Manning Gross & Massenburg LLP, were on brief, for\nMetalForming, Inc.\n Frederick W. Reif, with whom Marie E. Chafe, Cornell & Gollub,\nDebra Tama, and Wilson Elser Moskowitz Edelman & Dicker, LLP, were\non brief, for Schechtl Maschinenbau GmbH.\n\fJanuary 30, 2019\n\f LYNCH, Circuit Judge. Stephen Knox's hand was badly\n\ninjured at his work at Cape Cod Copper (CCC) in October 2016 when\n\nhe operated a machine that was manufactured by defendant Schechtl\n\nMaschinenbau GmbH, a German company. The machine had been sold to\n\nCCC by defendant MetalForming, Inc., an American company located\n\nin Georgia and Schechtl's U.S. distributor.\n\n The question on appeal is whether there is personal\n\njurisdiction over Schechtl, named as a defendant by Knox and as a\n\ncross-claim defendant by MetalForming. The district court\n\ndismissed the claims against Schechtl, finding that Schechtl had\n\nnot purposefully availed itself of the privilege of doing business\n\nin Massachusetts. Knox v. MetalForming, Inc., 303 F. Supp. 3d\n\n179, 184 (D. Mass. 2018).\n\n We reverse.\n\n I.\n\nA. Background\n\n The district court did not permit jurisdictional\n\ndiscovery. Id. at 187. The following facts are undisputed.\n\n In October 2016, Stephen D. Knox, plaintiff here along\n\nwith his wife, Jean, was injured while using a Schechtl MAX 310,1\n\na motor-driven metal-bending machine. The injury occurred at CCC,\n\n\n\n 1 Although some materials refer to the machine as a\n\"MAX3100 FOLDER,\" the parties refer to it as a \"MAX 310,\" and we\nwill do the same.\n\n - 3 -\n\fKnox's place of employment, located in Lakeville, Massachusetts.\n\nWhen Knox inadvertently hit the foot pedal of CCC's MAX 310, the\n\nmachine activated, crushing his left hand.\n\n Schechtl, the manufacturer of the MAX 310, is\n\nheadquartered in Edling, Germany and maintains no operations in\n\nthe United States. The company's marketing materials say that\n\nSchechtl manufactures the \"most popular architectural sheet metal\n\nfolders in the world.\"\n\n Schechtl sells its machines to United States customers\n\nthrough MetalForming, a separate and independently owned U.S.\n\ndistribution company. Schechtl's distribution agreement (\"the\n\nagreement\") with MetalForming gives MetalForming the exclusive\n\nright to distribute Schechtl's products in the \"Contract\n\nTerritory,\" which comprises Canada, the United States, and Mexico.\n\n The agreement outlines the procedure for selling\n\nSchechtl's machinery. The purchasing end user (\"the purchaser\")\n\nplaces an order with MetalForming, which in turn acquires the\n\nmachine from Schechtl. MetalForming then sends a purchase order,\n\nnaming the purchaser, to Schechtl in Germany. Under the agreement,\n\nMetalForming must include \"technical and other data\" in the\n\npurchase order, because that information is \"of importance for the\n\nordered product, the supply contract, and its performance.\"\n\n Schechtl then chooses whether to accept the purchase\n\norder. If it does accept, it issues a written order confirmation,\n\n - 4 -\n\fwhich \"govern[s] the product to be delivered, its technical\n\nqualities, the delivery price, the place of delivery, the time of\n\ndelivery as well as all other relevant contractual provisions.\"\n\n Schechtl then manufactures the machine to the\n\npurchaser's specifications. The agreement provides that Schechtl\n\n\"reserves the right, in the exercise of its sole discretion, to\n\ndiscontinue the manufacture or distribution of any Product without\n\nincurring any obligation to [MetalForming].\"\n\n When the machine is ready, Schechtl delivers it to a\n\n\"freight forwarder or other transport agency\" in Germany, at which\n\npoint ownership passes to MetalForming. The record does not detail\n\nthe ordinary shipment process after that point, but, as we describe\n\nbelow, it does show how the MAX 310 that injured Knox came to CCC.\n\n Under the agreement, MetalForming is responsible for\n\ninstallation at the purchaser's site and for training the\n\npurchaser's personnel in the proper use of the machine. The\n\nagreement does, however, provide that it may \"become necessary\n\nthat installation work be conducted under the direction of a\"\n\nSchechtl technician. And there is somewhat different information\n\nas to training contained in the information manual, as noted below.\n\n The agreement also requires that MetalForming \"provide\n\nany and all warranty services for the\" Schechtl products. Schechtl\n\nprovides a one-year warranty \"to the end users for all of its\n\nmachines, machine parts, tools, spare parts, and accessories.\"\n\n - 5 -\n\f MetalForming must also, under the agreement, \"pass along\n\nto customers information received from [Schechtl]\" regarding the\n\nproducts and their proper use. This information is packaged in\n\nwith each machine when it is delivered to the purchaser. The\n\nenclosed material includes a declaration that the machine had been\n\n\"developed, designed and manufactured in compliance with\"\n\napplicable European safety directives. It also includes\n\ninstruction manuals and safety instructions for each machine.\n\n The instruction manual includes an \"Instruction for\n\nInquiries and Spare Part Orders,\" which directs purchasers to\n\ncontact Schechtl (and not MetalForming) for inquiries and for\n\nadditional machine parts. A later troubleshooting section of that\n\nmanual also instructs that operators experiencing a problem\n\nshould, \"[i]f it is not possible to correct the malfunction with\n\nthe aid of the following tables, contact the Schechtl Maschinenbau\n\nGmbH Service department.\" It does not instruct the\n\noperator/purchaser to contact MetalForming. The manual also\n\noffers that \"[t]he operating company may receive extensive machine\n\ntraining by Schechtl Maschinenbau GmbH upon request . . . at\n\n[Schechtl's] facilities or at the operating company's facilities.\"\n\nThere is no evidence as to whether any Massachusetts purchaser\n\nmade such a request.\n\n The materials provided to the purchasers of Schechtl\n\nmachines contain Schechtl's direct contact information, including\n\n - 6 -\n\fits phone and fax numbers and its mail and email addresses.\n\nSchechtl also operates a website that instructs purchasers of its\n\nmachines to contact Schechtl directly for frequently asked\n\nquestions, sales, parts, and other information relating to its\n\nmachines. See Schechtl, http://www.schechtl.biz/index_e.htm (last\n\nvisited Jan. 24, 2019).\n\n Schechtl has provided MetalForming with advertising\n\nmaterials to market Schechtl products in the United States.\n\nMetalForming has promoted Schechtl machines in national trade\n\npublications and at industry trade shows. There is no record\n\nevidence as to the Massachusetts recipients of those trade\n\npublications. And while the record shows that Schechtl\n\nrepresentatives attended several trade shows in the United States\n\nwith MetalForming, there is no evidence that any of those shows\n\nwere in Massachusetts.\n\n Between 2000 and September 2017, MetalForming sold 2,639\n\nSchechtl sheet metal machines throughout the United States, at a\n\nvalue of just over $97 million. Between July 2001 and September\n\n2017, MetalForming sold to purchasers in Massachusetts forty-five\n\nSchechtl machines and 234 Schechtl parts, at a value of nearly\n\n$1.5 million (about $1.3 million for the machines and $176,752 for\n\nthe parts). Schechtl's Massachusetts machine sales appear to\n\nconstitute 1.35% of its United States machine sales. The record\n\ndoes not reveal Schechtl's total parts sales in the U.S.\n\n - 7 -\n\f Schechtl sold the MAX 310 which injured Knox to\n\nMetalForming in April 2001. MetalForming took delivery in Georgia.\n\nIn August, four months after the initial sale, MetalForming shipped\n\nthe machine to CCC, with CCC taking ownership of the machine in\n\nGeorgia. The respective purchase orders show that MetalForming\n\npurchased the machine from Schechtl for $25,830 and sold it to CCC\n\nfor $38,950. The purchase order from MetalForming to Schechtl\n\nidentified the purchaser as CCC but did not give CCC's location.\n\nThe purchase order from MetalForming to CCC shows that the machine\n\ncame with a one-year Schechtl warranty and that the price included\n\na \"Schechtl Installation Charge\" and a \"Schechtl Freight Charge\"\n\nto the purchaser, but no party explains what these last two terms\n\nmean or who receives the payment.\n\nB. Procedural History\n\n The Knoxes sued both Schechtl and MetalForming in\n\nMassachusetts state court. They alleged negligence, breach of\n\nwarranty, loss of consortium, and violation of the Massachusetts\n\nconsumer protection statute, Mass. Gen. Laws ch. 93A. MetalForming\n\nremoved the case to Massachusetts federal district court and filed\n\ncrossclaims against Schechtl for indemnification, contribution,\n\nand breach of contract. Schechtl moved to dismiss the claims\n\nagainst it for lack of personal jurisdiction. Both the Knoxes and\n\nMetalForming opposed Schechtl's motion.\n\n\n\n - 8 -\n\f The district court, after finding that the terms of\n\nMassachusetts's long-arm statute were \"easily . . . satisfied,\"\n\nKnox, 303 F. Supp. 3d at 183, nonetheless granted Schechtl's motion\n\nto dismiss, id. at 188. The court reasoned that, even though\n\n\"Schechtl ha[d] derived . . . 'substantial revenue' from\n\nMetalForming's sales of Schechtl equipment to Massachusetts\n\ncustomers,\" id. at 186, Schechtl had not purposefully availed\n\nitself of the privilege of doing business in Massachusetts, id. at\n\n187. The court added that there was \"[n]o Massachusetts-specific\n\n'plus' factor,\" like \"'special state-related design, advertising,\n\nadvice, marketing,' etc.\" Id. at 186 (quoting J. McIntyre Mach.,\n\nLtd. v. Nicastro, 564 U.S. 873, 889 (2011) (Breyer, J.,\n\nconcurring)). The court did not mention either the instructions\n\nor the warranties that Schechtl provided to the purchasers in\n\nMassachusetts.\n\n This appeal followed.\n\n II.\n\n The district court held that MetalForming had not made\n\na prima facie showing of personal jurisdiction. See id. at 184.\n\nOn prima facie review, the plaintiffs' burden is to proffer\n\nevidence \"sufficient to support findings of all facts essential to\n\npersonal jurisdiction\" without relying on unsupported allegations.\n\nA Corp. v. All Am. Plumbing, Inc., 812 F.3d 54, 58 (1st Cir. 2016).\n\nWe construe these facts \"in the light most congenial to the\n\n - 9 -\n\fplaintiff's jurisdictional claim.\" Mass. Sch. of Law at Andover,\n\nInc. v. Am. Bar Ass'n, 142 F.3d 26, 34 (1st Cir. 1998). \"Our\n\nreview is de novo.\" LP Sols. LLC v. Duchossois, 907 F.3d 95, 102\n\n(1st Cir. 2018).\n\n In a diversity jurisdiction case like this one, \"a\n\nplaintiff must satisfy both the forum state's long-arm statute and\n\nthe Due Process Clause of the Fourteenth Amendment.\" C.W. Downer\n\n& Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59, 65 (1st Cir.\n\n2014). Compliance with the terms of the Massachusetts long-arm\n\nstatute is not contested here. Schechtl proceeds directly to the\n\nfederal constitutional analysis; we will do so as well.\n\n For the exercise of personal jurisdiction to be\n\nconstitutional, a defendant must have \"certain minimum contacts\n\nwith [the forum state] such that the maintenance of the suit does\n\nnot offend 'traditional notions of fair play and substantial\n\njustice.'\" Int'l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945)\n\n(quoting Milliken v. Meyer, 311 U.S. 457, 463 (1940)). The\n\nconstitutional \"inquiry is highly 'fact-specific.'\" PREP Tours,\n\nInc. v. Am. Youth Soccer Org., No. 17-1223, 2019 WL 126221, at *4\n\n(1st Cir. Jan. 8, 2019) (quoting United Elec., Radio & Mach.\n\nWorkers of Am. v. 163 Pleasant St. Corp., 960 F.2d 1080, 1089 (1st\n\nCir. 1992)). Importantly, the \"test is 'not susceptible of\n\nmechanical application; rather, the facts of each case must be\n\n\n\n - 10 -\n\fweighed.'\" Id. (quoting Kulko v. Superior Ct. of Cal., 436 U.S.\n\n84, 92 (1978)).\n\n The Knoxes and MetalForming have asserted specific\n\npersonal jurisdiction over Schechtl, so the constitutional\n\nanalysis here has three components: relatedness, purposeful\n\navailment, and reasonableness. Plixer Int'l, Inc. v. Scrutinizer\n\nGmbH, 905 F.3d 1, 7 (1st Cir. 2018). That is, the plaintiffs must\n\nshow that (1) their claims directly arise out of or relate to the\n\ndefendant's forum activities; (2) the defendant's forum contacts\n\nrepresent a purposeful availment of the privilege of conducting\n\nactivities in that forum, thus invoking the benefits and\n\nprotections of the forum's laws and rendering the defendant's\n\ninvoluntary presence in the forum's courts foreseeable; and\n\n(3) the exercise of jurisdiction is reasonable. Id. The Knoxes\n\nand MetalForming must meet all three requirements to establish\n\npersonal jurisdiction. Id. We hold that they have.\n\n The district court reached only the issue of purposeful\n\navailment. But at oral argument Schechtl's counsel conceded that\n\nthe other two requirements are met. We briefly explain below why\n\nwe agree and address the main issue of purposeful availment.\n\nA. Relatedness\n\n To show relatedness, the Knoxes and MetalForming must\n\ndemonstrate that their \"cause of action either arises directly out\n\nof, or is related to, the defendant's forum-based contacts.\"\n\n - 11 -\n\fHarlow v. Children's Hosp., 432 F.3d 50, 61 (1st Cir. 2005) (citing\n\n163 Pleasant St., 960 F.2d at 1088-89). This \"flexible, relaxed\n\nstandard,\" N. Laminate Sales, Inc. v. Davis, 403 F.3d 14, 25 (1st\n\nCir. 2005) (quoting Pritzker v. Yari, 42 F.3d 53, 61 (1st Cir.\n\n1994)), requires only that the claim have a \"demonstrable nexus\"\n\nto the defendant's forum contacts, Mass. Sch. of Law, 142 F.3d at\n\n34. This requirement is easily met here.\n\nB. Purposeful Availment\n\n The case turns on the purposeful availment prong. To\n\nmeet this requirement, the Knoxes and MetalForming bear the burden\n\nof demonstrating that Schechtl has \"purposefully avail[ed] itself\n\nof the privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Hanson\n\nv. Denckla, 357 U.S. 235, 253 (1958).\n\n The purposeful availment requirement ensures that the\n\nexercise of jurisdiction is essentially voluntary and foreseeable,\n\nC.W. Downer, 771 F.3d at 66, and is not premised on a defendant's\n\n\"random, fortuitous, or attenuated contacts,\" Carreras v. PMG\n\nCollins, LLC, 660 F.3d 549, 555 (1st Cir. 2011) (quoting Burger\n\nKing Corp. v. Rudzewicz, 471 U.S. 462, 475 (1985)). \"[T]he Supreme\n\nCourt has explained that 'the foreseeability that is critical to\n\ndue process analysis . . . is that the defendant's conduct and\n\nconnection with the forum State are such that he should reasonably\n\nanticipate being haled into court there.'\" PREP Tours, 2019 WL\n\n - 12 -\n\f126221, at *6 (quoting Burger King, 471 U.S. at 474). This\n\nrequirement applies equally to foreign defendants. Plixer, 905\n\nF.3d at 7.\n\n Each side asserts that the Supreme Court's decision in\n\nJ. McIntyre Machinery, Limited v. Nicastro supports its view. Like\n\nother circuits, we have held that the narrowest, and thus binding,\n\nopinion from the \"fragmented Court\" in that case was Justice\n\nBreyer's. Plixer, 905 F.3d at 10 (quoting Marks v. United States,\n\n430 U.S. 188, 193 (1977)); accord Williams v. Romarm, SA, 756 F.3d\n\n777, 784 (D.C. Cir. 2014) (finding Justice Breyer's concurring\n\nopinion controlling under Marks); Ainsworth v. Moffett Eng'g,\n\nLtd., 716 F.3d 174, 178 & n.14 (5th Cir. 2013) (same); AFTG-TG,\n\nLLC v. Nuvoton Tech. Corp., 689 F.3d 1358, 1363 (Fed. Cir. 2012)\n\n(same). In the end we do not think that this case, on the facts\n\nhere, fails the personal jurisdiction tests articulated by either\n\nJustice Breyer's concurring opinion or the plurality opinion in\n\nNicastro.\n\n The district court found that Schechtl had not\n\ndesignated Massachusetts \"for special attention\" and had not\n\n\"target[ed] buyers within\" Massachusetts. Knox, 303 F. Supp. 3d\n\nat 186. Using those tests, the district court held that Schechtl\n\nhad not purposefully availed itself of the privilege of conducting\n\n\n\n\n - 13 -\n\fbusiness in the Commonwealth. Id.2 Those, as our Plixer decision\n\nlater made explicit, are not the exclusive tests to establish\n\npurposeful availment.\n\n In Plixer we concluded that \"Supreme Court precedent\n\ndoes not establish specific targeting of a forum as the only means\n\nof showing that the purposeful availment test has been met.\" 905\n\nF.3d at 9 (emphasis added). Depending on the facts, a defendant's\n\n\"'regular flow or regular course of sale' in the [forum]\" could\n\nmake the exercise of jurisdiction foreseeable to the defendant.\n\nId. at 10. And, again depending on the facts, jurisdiction could\n\nbe foreseeable based on \"something more\" than this, evidencing an\n\nintent to serve the forum. Id. (citing Asahi Metal Indus. Co.,\n\nLtd. v. Superior Court of Cal., 480 U.S. 102, 111-12 (1987)\n\n(opinion of O'Connor, J.)). Justice O'Connor's plurality opinion\n\nin Asahi, endorsed by the plurality opinion in Nicastro, see 564\n\nU.S. at 885 (plurality opinion), says that \"something more\" may\n\ninclude, \"for example, designing the product for the market in the\n\nforum State, advertising in the forum State, establishing channels\n\nfor providing regular advice to customers in the forum State, or\n\nmarketing the product through a distributor who has agreed to serve\n\n\n\n\n 2 To be clear, there is no argument that a producer like\nSchechtl is subject to jurisdiction solely because it knows that\nits products might be sold in Massachusetts. See Nicastro, 564\nU.S. at 891 (Breyer, J., concurring) (rejecting such a standard).\n - 14 -\n\fas the sales agent in the forum State.\" Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.).\n\n Specific jurisdiction must rest on a defendant's\n\nvoluntary contact with the forum and not on \"the 'unilateral\n\nactivity of another party or a third person.'\" Burger King, 471\n\nU.S. at 475 (quoting Helicopteros Nacionales de Colombia, S.A. v.\n\nHall, 466 U.S. 408, 417 (1984)). The argument for jurisdiction\n\nhere does not rest on MetalForming's Massachusetts activities. It\n\nrests instead on the totality of Schechtl's activities,\n\nvoluntarily undertaken, that connect the German company to\n\nMassachusetts.\n\n These voluntary acts on Schechtl's part led to a \"regular\n\nflow or regular course of sales,\" and more than that, in the\n\nCommonwealth. Over sixteen years, Schechtl, through MetalForming,\n\nsold forty-five machines (an average of close to three machines in\n\neach of those sixteen years). It also provided 234 parts to\n\npurchasers in Massachusetts. Those parts and machines led to\n\nnearly $1.5 million of Massachusetts sales for Schechtl.\n\n We compare this case to Plixer, in which we upheld the\n\nexercise of jurisdiction over a defendant who, over three-and-a-\n\nhalf years, served 156 forum customers, generating about $200,000\n\nin business. See 905 F.3d at 4-5; see also id. at 11 (describing\n\npost-Nicastro rulings upholding the exercise of jurisdiction based\n\non \"a regular course of sales\"). And we compare Schechtl to the\n\n - 15 -\n\fdefendant in Nicastro, who Justice Breyer described as having made\n\n\"a single isolated sale\" into the forum. 564 U.S. at 888 (Breyer,\n\nJ., concurring). Schechtl certainly does not fall into the\n\ncategory of manufacturer, \"small\" in \"shape[] and size[],\"\n\ndescribed by Justice Breyer in Nicastro. Id. at 892 (Breyer, J.,\n\nconcurring).\n\n Schechtl argues that we should discount its\n\nMassachusetts sales because those sales were part of a nationwide\n\nsales effort. But the question is not whether a defendant sells\n\nits product across the U.S.; it is instead whether a defendant's\n\nforum connection is such \"that the exercise of jurisdiction is\n\nessentially voluntary and foreseeable.\" Plixer, 905 F.3d at 7\n\n(citing C.W. Downer, 771 F.3d at 66); see Ainsworth, 716 F.3d at\n\n179 (upholding the exercise of jurisdiction based on substantial\n\nin-forum sales, even though the defendant's forum sales\n\nrepresented only 1.55% of its nationwide sales during the relevant\n\nperiod). And we note that the use of a nationwide distributor\n\ndoes not automatically preclude the exercise of jurisdiction. See\n\nAinsworth, 716 F.3d at 179 (upholding the exercise of jurisdiction\n\nover a manufacturer even though the manufacturer employed a\n\nnationwide distributor).\n\n To be clear, we do not hold that the mere volume of\n\nSchechtl's sales in Massachusetts over sixteen years standing\n\n\n\n - 16 -\n\falone would suffice (a hypothetical situation we need not address).\n\nThere is more here.\n\n Schechtl individually approved and manufactured\n\naccording to purchaser-provided specifications each of the nearly\n\nfifty machines it sent to Massachusetts purchasers. See In re\n\nChinese-Manufactured Drywall Prods. Liab. Litig., 742 F.3d 576,\n\n589 (5th Cir. 2014) (upholding the exercise of personal\n\njurisdiction based in part on the defendant's fulfilling product\n\norders on a \"made-to-order basis\"); cf. Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.) (adding that \"designing the product for\n\nthe market in the forum State\" may be \"additional conduct\"\n\nnecessary to make the exercise of jurisdiction constitutional).\n\n Schechtl's relationship with purchasers in Massachusetts\n\ndid not end when Schechtl accepted the purchase order and\n\nmanufactured the machine. Schechtl required that MetalForming\n\ninclude, with each machine, materials that instructed that\n\npurchaser to contact Schechtl directly, whether to purchase\n\nreplacement parts or to obtain assistance with troubleshooting and\n\nfixing problems. From the fact that hundreds of Schechtl parts\n\nwere delivered to Massachusetts, the inference is entirely\n\nplausible that Massachusetts purchasers did use the channels\n\nSchechtl established both as to spare parts and as to\n\ntroubleshooting.\n\n\n\n - 17 -\n\f Schechtl's channels to Massachusetts purchasers\n\nconstitute efforts to continue -- and perhaps to expand -- its\n\nrelationship with Massachusetts purchasers. Those deliberately\n\nopened channels, kept open over many years and presumably used,\n\nare relevant to the jurisdictional analysis. See Asahi, 480 U.S.\n\nat 112 (opinion of O'Connor, J.) (noting that \"establishing\n\nchannels for providing regular advice to customers in the forum\n\nState\" may be \"something more\" in support of jurisdiction). Those\n\nchannels established a direct link between Schechtl and its\n\npurchasers. Here that means that Schechtl voluntarily opened at\n\nleast forty-five such direct links with Massachusetts purchasers.\n\nSchechtl's long service of purchasers in Massachusetts through at\n\nleast its spare parts sales bolsters our conclusion that the\n\nexercise of jurisdiction here is foreseeable.3\n\n Purposeful availment analysis \"'will vary with the\n\nquality and the nature of the defendant's activity.'\" PREP Tours,\n\n2019 WL 126221, at *6 (quoting Burger King, 471 U.S. at 474-75).\n\nThis case involves a manufacturer which can direct where its\n\nproducts go, which sold dozens of expensive products into the forum\n\n\n 3 Schechtl argues that it did not know that CCC was located\nin Massachusetts. Even if that contention were correct, we would\nnot consider it dispositive given all the other facts here. We do\nnot comment on MetalForming's argument that Schechtl should have\nknown CCC's location.\n We also do not rest on, or even reach, the argument that\nSchechtl made no effort to exclude Massachusetts purchasers from\nits American market. Cf. Ainsworth, 716 F.3d at 179.\n - 18 -\n\fover nearly two decades, and which initiated an ongoing\n\nrelationship with its in-forum purchasers. Nicastro, by contrast,\n\ninvolved a manufacturer which lacked any similar ability to control\n\nthe end location of its products, see 564 U.S. at 878 (plurality\n\nopinion) (noting that there was \"no allegation that the distributor\n\nwas under [the defendant's] control\"), and which had no other\n\nrelationship with the forum, see id. at 886. The defendant there\n\nknew only \"that its products are distributed through a nationwide\n\ndistribution system that might lead to those products being sold\n\nin any of the fifty states.\" Id. at 879 (internal quotation marks\n\nomitted). None of the opinions from Nicastro require that we\n\naccept Schechtl's arguments on appeal.\n\n Schechtl's only remaining argument is that MetalForming\n\ntakes title to the Schechtl products in Germany. First Circuit\n\nlaw has long found this argument irrelevant to the jurisdictional\n\nanalysis. See Benitez-Allende v. Alcan Aluminio do Brasil, S.A.,\n\n857 F.2d 26, 30 (1st Cir. 1988) (Breyer, J.) (\"The fact that title\n\nto the [products] passed in [a foreign country] is beside the\n\npoint, for '[i]f International Shoe stands for anything, however,\n\nit is that a truly interstate business may not shield itself from\n\nsuit by a careful but formalistic structuring of its business\n\ndealings.'\" (quoting Vencedor Mfg. Co., Inc. v. Gougler Indus.,\n\nInc., 557 F.2d 886, 891 (1st Cir. 1977))). The same is true for\n\nan international business.\n\n - 19 -\n\fC. Reasonableness\n\n We explain briefly why we consider the exercise of\n\njurisdiction to be reasonable under the five \"gestalt\" factors:\n\n (1) the defendant's burden of appearing [in\n the forum], (2) the forum state's interest in\n adjudicating the dispute, (3) the plaintiff's\n interest in obtaining convenient and effective\n relief, (4) the judicial system's interest in\n obtaining the most effective resolution of the\n controversy, and (5) the common interests of\n all sovereigns in promoting substantive social\n policies.\n\n\nTicketmaster-N.Y., Inc. v. Alioto, 26 F.3d 201, 209 (1st Cir. 1994)\n\n(citing Burger King, 471 U.S. at 477). Schechtl in its briefs,\n\nbut not at oral argument, argues that Massachusetts litigation\n\nwould be burdensome because it is a German company with German\n\nemployees, and that cross-Atlantic travel and communications would\n\nimpose burdens on its employees. That there is some burden on\n\nSchechtl (which can be mitigated) is not enough on the facts here\n\nto make the exercise of jurisdiction unreasonable. See Plixer,\n\n905 F.3d at 13 (noting that \"'[w]hen minimum contacts have been\n\nestablished, often the interests of the plaintiff and the forum in\n\nthe exercise of jurisdiction will justify even the serious burdens\n\nplaced on the alien defendant'\" (quoting Asahi, 480 U.S. at 114\n\n(opinion of O'Connor, J.)); see also C.W. Downer, 771 F.3d at 70\n\n(noting that many of the case's logistical challenges \"can be\n\nresolved through the use of affidavits and video devices\").\n\n\n\n - 20 -\n\f III.\n\n We conclude that the exercise of personal jurisdiction\n\nover Schechtl comports with due process. We reverse and remand\n\nfor further proceedings consistent with this opinion.\n\n\n\n\n - 21 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363804/", "author_raw": "LYNCH, Circuit Judge"}]}
LYNCH
STAHL
BARRON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586551/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: MetalForming, Inc. v. Schechtl Maschinenbau Gmbh\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n For the First Circuit\n\n\nNos. 18-1550\n 18-1551\n\n STEPHEN D. KNOX; JEAN KNOX,\n\n Plaintiffs, Appellants,\n\n v.\n\n METALFORMING, INC.,\n\n Defendant, Appellant,\n\n SCHECHTL MASCHINENBAU GMBH,\n\n Defendant, Appellee.\n\n\n APPEALS FROM THE UNITED STATES DISTRICT COURT\n FOR THE DISTRICT OF MASSACHUSETTS\n\n [Hon. George A. O'Toole, Jr., U.S. District Judge]\n\n\n Before\n\n Lynch, Stahl, and Barron,\n Circuit Judges.\n\n\n Benjamin R. Zimmermann, with whom Stacey L. Pietrowicz and\nSugarman and Sugarman, P.C. were on brief, for Stephen and Jean\nKnox.\n Javier F. Flores, with whom Eric V. Skelly, Thaddeus M.\nLenkiewicz, and Manning Gross & Massenburg LLP, were on brief, for\nMetalForming, Inc.\n Frederick W. Reif, with whom Marie E. Chafe, Cornell & Gollub,\nDebra Tama, and Wilson Elser Moskowitz Edelman & Dicker, LLP, were\non brief, for Schechtl Maschinenbau GmbH.\n\fJanuary 30, 2019\n\f LYNCH, Circuit Judge. Stephen Knox's hand was badly\n\ninjured at his work at Cape Cod Copper (CCC) in October 2016 when\n\nhe operated a machine that was manufactured by defendant Schechtl\n\nMaschinenbau GmbH, a German company. The machine had been sold to\n\nCCC by defendant MetalForming, Inc., an American company located\n\nin Georgia and Schechtl's U.S. distributor.\n\n The question on appeal is whether there is personal\n\njurisdiction over Schechtl, named as a defendant by Knox and as a\n\ncross-claim defendant by MetalForming. The district court\n\ndismissed the claims against Schechtl, finding that Schechtl had\n\nnot purposefully availed itself of the privilege of doing business\n\nin Massachusetts. Knox v. MetalForming, Inc., 303 F. Supp. 3d\n\n179, 184 (D. Mass. 2018).\n\n We reverse.\n\n I.\n\nA. Background\n\n The district court did not permit jurisdictional\n\ndiscovery. Id. at 187. The following facts are undisputed.\n\n In October 2016, Stephen D. Knox, plaintiff here along\n\nwith his wife, Jean, was injured while using a Schechtl MAX 310,1\n\na motor-driven metal-bending machine. The injury occurred at CCC,\n\n\n\n 1 Although some materials refer to the machine as a\n\"MAX3100 FOLDER,\" the parties refer to it as a \"MAX 310,\" and we\nwill do the same.\n\n - 3 -\n\fKnox's place of employment, located in Lakeville, Massachusetts.\n\nWhen Knox inadvertently hit the foot pedal of CCC's MAX 310, the\n\nmachine activated, crushing his left hand.\n\n Schechtl, the manufacturer of the MAX 310, is\n\nheadquartered in Edling, Germany and maintains no operations in\n\nthe United States. The company's marketing materials say that\n\nSchechtl manufactures the \"most popular architectural sheet metal\n\nfolders in the world.\"\n\n Schechtl sells its machines to United States customers\n\nthrough MetalForming, a separate and independently owned U.S.\n\ndistribution company. Schechtl's distribution agreement (\"the\n\nagreement\") with MetalForming gives MetalForming the exclusive\n\nright to distribute Schechtl's products in the \"Contract\n\nTerritory,\" which comprises Canada, the United States, and Mexico.\n\n The agreement outlines the procedure for selling\n\nSchechtl's machinery. The purchasing end user (\"the purchaser\")\n\nplaces an order with MetalForming, which in turn acquires the\n\nmachine from Schechtl. MetalForming then sends a purchase order,\n\nnaming the purchaser, to Schechtl in Germany. Under the agreement,\n\nMetalForming must include \"technical and other data\" in the\n\npurchase order, because that information is \"of importance for the\n\nordered product, the supply contract, and its performance.\"\n\n Schechtl then chooses whether to accept the purchase\n\norder. If it does accept, it issues a written order confirmation,\n\n - 4 -\n\fwhich \"govern[s] the product to be delivered, its technical\n\nqualities, the delivery price, the place of delivery, the time of\n\ndelivery as well as all other relevant contractual provisions.\"\n\n Schechtl then manufactures the machine to the\n\npurchaser's specifications. The agreement provides that Schechtl\n\n\"reserves the right, in the exercise of its sole discretion, to\n\ndiscontinue the manufacture or distribution of any Product without\n\nincurring any obligation to [MetalForming].\"\n\n When the machine is ready, Schechtl delivers it to a\n\n\"freight forwarder or other transport agency\" in Germany, at which\n\npoint ownership passes to MetalForming. The record does not detail\n\nthe ordinary shipment process after that point, but, as we describe\n\nbelow, it does show how the MAX 310 that injured Knox came to CCC.\n\n Under the agreement, MetalForming is responsible for\n\ninstallation at the purchaser's site and for training the\n\npurchaser's personnel in the proper use of the machine. The\n\nagreement does, however, provide that it may \"become necessary\n\nthat installation work be conducted under the direction of a\"\n\nSchechtl technician. And there is somewhat different information\n\nas to training contained in the information manual, as noted below.\n\n The agreement also requires that MetalForming \"provide\n\nany and all warranty services for the\" Schechtl products. Schechtl\n\nprovides a one-year warranty \"to the end users for all of its\n\nmachines, machine parts, tools, spare parts, and accessories.\"\n\n - 5 -\n\f MetalForming must also, under the agreement, \"pass along\n\nto customers information received from [Schechtl]\" regarding the\n\nproducts and their proper use. This information is packaged in\n\nwith each machine when it is delivered to the purchaser. The\n\nenclosed material includes a declaration that the machine had been\n\n\"developed, designed and manufactured in compliance with\"\n\napplicable European safety directives. It also includes\n\ninstruction manuals and safety instructions for each machine.\n\n The instruction manual includes an \"Instruction for\n\nInquiries and Spare Part Orders,\" which directs purchasers to\n\ncontact Schechtl (and not MetalForming) for inquiries and for\n\nadditional machine parts. A later troubleshooting section of that\n\nmanual also instructs that operators experiencing a problem\n\nshould, \"[i]f it is not possible to correct the malfunction with\n\nthe aid of the following tables, contact the Schechtl Maschinenbau\n\nGmbH Service department.\" It does not instruct the\n\noperator/purchaser to contact MetalForming. The manual also\n\noffers that \"[t]he operating company may receive extensive machine\n\ntraining by Schechtl Maschinenbau GmbH upon request . . . at\n\n[Schechtl's] facilities or at the operating company's facilities.\"\n\nThere is no evidence as to whether any Massachusetts purchaser\n\nmade such a request.\n\n The materials provided to the purchasers of Schechtl\n\nmachines contain Schechtl's direct contact information, including\n\n - 6 -\n\fits phone and fax numbers and its mail and email addresses.\n\nSchechtl also operates a website that instructs purchasers of its\n\nmachines to contact Schechtl directly for frequently asked\n\nquestions, sales, parts, and other information relating to its\n\nmachines. See Schechtl, http://www.schechtl.biz/index_e.htm (last\n\nvisited Jan. 24, 2019).\n\n Schechtl has provided MetalForming with advertising\n\nmaterials to market Schechtl products in the United States.\n\nMetalForming has promoted Schechtl machines in national trade\n\npublications and at industry trade shows. There is no record\n\nevidence as to the Massachusetts recipients of those trade\n\npublications. And while the record shows that Schechtl\n\nrepresentatives attended several trade shows in the United States\n\nwith MetalForming, there is no evidence that any of those shows\n\nwere in Massachusetts.\n\n Between 2000 and September 2017, MetalForming sold 2,639\n\nSchechtl sheet metal machines throughout the United States, at a\n\nvalue of just over $97 million. Between July 2001 and September\n\n2017, MetalForming sold to purchasers in Massachusetts forty-five\n\nSchechtl machines and 234 Schechtl parts, at a value of nearly\n\n$1.5 million (about $1.3 million for the machines and $176,752 for\n\nthe parts). Schechtl's Massachusetts machine sales appear to\n\nconstitute 1.35% of its United States machine sales. The record\n\ndoes not reveal Schechtl's total parts sales in the U.S.\n\n - 7 -\n\f Schechtl sold the MAX 310 which injured Knox to\n\nMetalForming in April 2001. MetalForming took delivery in Georgia.\n\nIn August, four months after the initial sale, MetalForming shipped\n\nthe machine to CCC, with CCC taking ownership of the machine in\n\nGeorgia. The respective purchase orders show that MetalForming\n\npurchased the machine from Schechtl for $25,830 and sold it to CCC\n\nfor $38,950. The purchase order from MetalForming to Schechtl\n\nidentified the purchaser as CCC but did not give CCC's location.\n\nThe purchase order from MetalForming to CCC shows that the machine\n\ncame with a one-year Schechtl warranty and that the price included\n\na \"Schechtl Installation Charge\" and a \"Schechtl Freight Charge\"\n\nto the purchaser, but no party explains what these last two terms\n\nmean or who receives the payment.\n\nB. Procedural History\n\n The Knoxes sued both Schechtl and MetalForming in\n\nMassachusetts state court. They alleged negligence, breach of\n\nwarranty, loss of consortium, and violation of the Massachusetts\n\nconsumer protection statute, Mass. Gen. Laws ch. 93A. MetalForming\n\nremoved the case to Massachusetts federal district court and filed\n\ncrossclaims against Schechtl for indemnification, contribution,\n\nand breach of contract. Schechtl moved to dismiss the claims\n\nagainst it for lack of personal jurisdiction. Both the Knoxes and\n\nMetalForming opposed Schechtl's motion.\n\n\n\n - 8 -\n\f The district court, after finding that the terms of\n\nMassachusetts's long-arm statute were \"easily . . . satisfied,\"\n\nKnox, 303 F. Supp. 3d at 183, nonetheless granted Schechtl's motion\n\nto dismiss, id. at 188. The court reasoned that, even though\n\n\"Schechtl ha[d] derived . . . 'substantial revenue' from\n\nMetalForming's sales of Schechtl equipment to Massachusetts\n\ncustomers,\" id. at 186, Schechtl had not purposefully availed\n\nitself of the privilege of doing business in Massachusetts, id. at\n\n187. The court added that there was \"[n]o Massachusetts-specific\n\n'plus' factor,\" like \"'special state-related design, advertising,\n\nadvice, marketing,' etc.\" Id. at 186 (quoting J. McIntyre Mach.,\n\nLtd. v. Nicastro, 564 U.S. 873, 889 (2011) (Breyer, J.,\n\nconcurring)). The court did not mention either the instructions\n\nor the warranties that Schechtl provided to the purchasers in\n\nMassachusetts.\n\n This appeal followed.\n\n II.\n\n The district court held that MetalForming had not made\n\na prima facie showing of personal jurisdiction. See id. at 184.\n\nOn prima facie review, the plaintiffs' burden is to proffer\n\nevidence \"sufficient to support findings of all facts essential to\n\npersonal jurisdiction\" without relying on unsupported allegations.\n\nA Corp. v. All Am. Plumbing, Inc., 812 F.3d 54, 58 (1st Cir. 2016).\n\nWe construe these facts \"in the light most congenial to the\n\n - 9 -\n\fplaintiff's jurisdictional claim.\" Mass. Sch. of Law at Andover,\n\nInc. v. Am. Bar Ass'n, 142 F.3d 26, 34 (1st Cir. 1998). \"Our\n\nreview is de novo.\" LP Sols. LLC v. Duchossois, 907 F.3d 95, 102\n\n(1st Cir. 2018).\n\n In a diversity jurisdiction case like this one, \"a\n\nplaintiff must satisfy both the forum state's long-arm statute and\n\nthe Due Process Clause of the Fourteenth Amendment.\" C.W. Downer\n\n& Co. v. Bioriginal Food & Sci. Corp., 771 F.3d 59, 65 (1st Cir.\n\n2014). Compliance with the terms of the Massachusetts long-arm\n\nstatute is not contested here. Schechtl proceeds directly to the\n\nfederal constitutional analysis; we will do so as well.\n\n For the exercise of personal jurisdiction to be\n\nconstitutional, a defendant must have \"certain minimum contacts\n\nwith [the forum state] such that the maintenance of the suit does\n\nnot offend 'traditional notions of fair play and substantial\n\njustice.'\" Int'l Shoe Co. v. Washington, 326 U.S. 310, 316 (1945)\n\n(quoting Milliken v. Meyer, 311 U.S. 457, 463 (1940)). The\n\nconstitutional \"inquiry is highly 'fact-specific.'\" PREP Tours,\n\nInc. v. Am. Youth Soccer Org., No. 17-1223, 2019 WL 126221, at *4\n\n(1st Cir. Jan. 8, 2019) (quoting United Elec., Radio & Mach.\n\nWorkers of Am. v. 163 Pleasant St. Corp., 960 F.2d 1080, 1089 (1st\n\nCir. 1992)). Importantly, the \"test is 'not susceptible of\n\nmechanical application; rather, the facts of each case must be\n\n\n\n - 10 -\n\fweighed.'\" Id. (quoting Kulko v. Superior Ct. of Cal., 436 U.S.\n\n84, 92 (1978)).\n\n The Knoxes and MetalForming have asserted specific\n\npersonal jurisdiction over Schechtl, so the constitutional\n\nanalysis here has three components: relatedness, purposeful\n\navailment, and reasonableness. Plixer Int'l, Inc. v. Scrutinizer\n\nGmbH, 905 F.3d 1, 7 (1st Cir. 2018). That is, the plaintiffs must\n\nshow that (1) their claims directly arise out of or relate to the\n\ndefendant's forum activities; (2) the defendant's forum contacts\n\nrepresent a purposeful availment of the privilege of conducting\n\nactivities in that forum, thus invoking the benefits and\n\nprotections of the forum's laws and rendering the defendant's\n\ninvoluntary presence in the forum's courts foreseeable; and\n\n(3) the exercise of jurisdiction is reasonable. Id. The Knoxes\n\nand MetalForming must meet all three requirements to establish\n\npersonal jurisdiction. Id. We hold that they have.\n\n The district court reached only the issue of purposeful\n\navailment. But at oral argument Schechtl's counsel conceded that\n\nthe other two requirements are met. We briefly explain below why\n\nwe agree and address the main issue of purposeful availment.\n\nA. Relatedness\n\n To show relatedness, the Knoxes and MetalForming must\n\ndemonstrate that their \"cause of action either arises directly out\n\nof, or is related to, the defendant's forum-based contacts.\"\n\n - 11 -\n\fHarlow v. Children's Hosp., 432 F.3d 50, 61 (1st Cir. 2005) (citing\n\n163 Pleasant St., 960 F.2d at 1088-89). This \"flexible, relaxed\n\nstandard,\" N. Laminate Sales, Inc. v. Davis, 403 F.3d 14, 25 (1st\n\nCir. 2005) (quoting Pritzker v. Yari, 42 F.3d 53, 61 (1st Cir.\n\n1994)), requires only that the claim have a \"demonstrable nexus\"\n\nto the defendant's forum contacts, Mass. Sch. of Law, 142 F.3d at\n\n34. This requirement is easily met here.\n\nB. Purposeful Availment\n\n The case turns on the purposeful availment prong. To\n\nmeet this requirement, the Knoxes and MetalForming bear the burden\n\nof demonstrating that Schechtl has \"purposefully avail[ed] itself\n\nof the privilege of conducting activities within the forum State,\n\nthus invoking the benefits and protections of its laws.\" Hanson\n\nv. Denckla, 357 U.S. 235, 253 (1958).\n\n The purposeful availment requirement ensures that the\n\nexercise of jurisdiction is essentially voluntary and foreseeable,\n\nC.W. Downer, 771 F.3d at 66, and is not premised on a defendant's\n\n\"random, fortuitous, or attenuated contacts,\" Carreras v. PMG\n\nCollins, LLC, 660 F.3d 549, 555 (1st Cir. 2011) (quoting Burger\n\nKing Corp. v. Rudzewicz, 471 U.S. 462, 475 (1985)). \"[T]he Supreme\n\nCourt has explained that 'the foreseeability that is critical to\n\ndue process analysis . . . is that the defendant's conduct and\n\nconnection with the forum State are such that he should reasonably\n\nanticipate being haled into court there.'\" PREP Tours, 2019 WL\n\n - 12 -\n\f126221, at *6 (quoting Burger King, 471 U.S. at 474). This\n\nrequirement applies equally to foreign defendants. Plixer, 905\n\nF.3d at 7.\n\n Each side asserts that the Supreme Court's decision in\n\nJ. McIntyre Machinery, Limited v. Nicastro supports its view. Like\n\nother circuits, we have held that the narrowest, and thus binding,\n\nopinion from the \"fragmented Court\" in that case was Justice\n\nBreyer's. Plixer, 905 F.3d at 10 (quoting Marks v. United States,\n\n430 U.S. 188, 193 (1977)); accord Williams v. Romarm, SA, 756 F.3d\n\n777, 784 (D.C. Cir. 2014) (finding Justice Breyer's concurring\n\nopinion controlling under Marks); Ainsworth v. Moffett Eng'g,\n\nLtd., 716 F.3d 174, 178 & n.14 (5th Cir. 2013) (same); AFTG-TG,\n\nLLC v. Nuvoton Tech. Corp., 689 F.3d 1358, 1363 (Fed. Cir. 2012)\n\n(same). In the end we do not think that this case, on the facts\n\nhere, fails the personal jurisdiction tests articulated by either\n\nJustice Breyer's concurring opinion or the plurality opinion in\n\nNicastro.\n\n The district court found that Schechtl had not\n\ndesignated Massachusetts \"for special attention\" and had not\n\n\"target[ed] buyers within\" Massachusetts. Knox, 303 F. Supp. 3d\n\nat 186. Using those tests, the district court held that Schechtl\n\nhad not purposefully availed itself of the privilege of conducting\n\n\n\n\n - 13 -\n\fbusiness in the Commonwealth. Id.2 Those, as our Plixer decision\n\nlater made explicit, are not the exclusive tests to establish\n\npurposeful availment.\n\n In Plixer we concluded that \"Supreme Court precedent\n\ndoes not establish specific targeting of a forum as the only means\n\nof showing that the purposeful availment test has been met.\" 905\n\nF.3d at 9 (emphasis added). Depending on the facts, a defendant's\n\n\"'regular flow or regular course of sale' in the [forum]\" could\n\nmake the exercise of jurisdiction foreseeable to the defendant.\n\nId. at 10. And, again depending on the facts, jurisdiction could\n\nbe foreseeable based on \"something more\" than this, evidencing an\n\nintent to serve the forum. Id. (citing Asahi Metal Indus. Co.,\n\nLtd. v. Superior Court of Cal., 480 U.S. 102, 111-12 (1987)\n\n(opinion of O'Connor, J.)). Justice O'Connor's plurality opinion\n\nin Asahi, endorsed by the plurality opinion in Nicastro, see 564\n\nU.S. at 885 (plurality opinion), says that \"something more\" may\n\ninclude, \"for example, designing the product for the market in the\n\nforum State, advertising in the forum State, establishing channels\n\nfor providing regular advice to customers in the forum State, or\n\nmarketing the product through a distributor who has agreed to serve\n\n\n\n\n 2 To be clear, there is no argument that a producer like\nSchechtl is subject to jurisdiction solely because it knows that\nits products might be sold in Massachusetts. See Nicastro, 564\nU.S. at 891 (Breyer, J., concurring) (rejecting such a standard).\n - 14 -\n\fas the sales agent in the forum State.\" Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.).\n\n Specific jurisdiction must rest on a defendant's\n\nvoluntary contact with the forum and not on \"the 'unilateral\n\nactivity of another party or a third person.'\" Burger King, 471\n\nU.S. at 475 (quoting Helicopteros Nacionales de Colombia, S.A. v.\n\nHall, 466 U.S. 408, 417 (1984)). The argument for jurisdiction\n\nhere does not rest on MetalForming's Massachusetts activities. It\n\nrests instead on the totality of Schechtl's activities,\n\nvoluntarily undertaken, that connect the German company to\n\nMassachusetts.\n\n These voluntary acts on Schechtl's part led to a \"regular\n\nflow or regular course of sales,\" and more than that, in the\n\nCommonwealth. Over sixteen years, Schechtl, through MetalForming,\n\nsold forty-five machines (an average of close to three machines in\n\neach of those sixteen years). It also provided 234 parts to\n\npurchasers in Massachusetts. Those parts and machines led to\n\nnearly $1.5 million of Massachusetts sales for Schechtl.\n\n We compare this case to Plixer, in which we upheld the\n\nexercise of jurisdiction over a defendant who, over three-and-a-\n\nhalf years, served 156 forum customers, generating about $200,000\n\nin business. See 905 F.3d at 4-5; see also id. at 11 (describing\n\npost-Nicastro rulings upholding the exercise of jurisdiction based\n\non \"a regular course of sales\"). And we compare Schechtl to the\n\n - 15 -\n\fdefendant in Nicastro, who Justice Breyer described as having made\n\n\"a single isolated sale\" into the forum. 564 U.S. at 888 (Breyer,\n\nJ., concurring). Schechtl certainly does not fall into the\n\ncategory of manufacturer, \"small\" in \"shape[] and size[],\"\n\ndescribed by Justice Breyer in Nicastro. Id. at 892 (Breyer, J.,\n\nconcurring).\n\n Schechtl argues that we should discount its\n\nMassachusetts sales because those sales were part of a nationwide\n\nsales effort. But the question is not whether a defendant sells\n\nits product across the U.S.; it is instead whether a defendant's\n\nforum connection is such \"that the exercise of jurisdiction is\n\nessentially voluntary and foreseeable.\" Plixer, 905 F.3d at 7\n\n(citing C.W. Downer, 771 F.3d at 66); see Ainsworth, 716 F.3d at\n\n179 (upholding the exercise of jurisdiction based on substantial\n\nin-forum sales, even though the defendant's forum sales\n\nrepresented only 1.55% of its nationwide sales during the relevant\n\nperiod). And we note that the use of a nationwide distributor\n\ndoes not automatically preclude the exercise of jurisdiction. See\n\nAinsworth, 716 F.3d at 179 (upholding the exercise of jurisdiction\n\nover a manufacturer even though the manufacturer employed a\n\nnationwide distributor).\n\n To be clear, we do not hold that the mere volume of\n\nSchechtl's sales in Massachusetts over sixteen years standing\n\n\n\n - 16 -\n\falone would suffice (a hypothetical situation we need not address).\n\nThere is more here.\n\n Schechtl individually approved and manufactured\n\naccording to purchaser-provided specifications each of the nearly\n\nfifty machines it sent to Massachusetts purchasers. See In re\n\nChinese-Manufactured Drywall Prods. Liab. Litig., 742 F.3d 576,\n\n589 (5th Cir. 2014) (upholding the exercise of personal\n\njurisdiction based in part on the defendant's fulfilling product\n\norders on a \"made-to-order basis\"); cf. Asahi, 480 U.S. at 112\n\n(opinion of O'Connor, J.) (adding that \"designing the product for\n\nthe market in the forum State\" may be \"additional conduct\"\n\nnecessary to make the exercise of jurisdiction constitutional).\n\n Schechtl's relationship with purchasers in Massachusetts\n\ndid not end when Schechtl accepted the purchase order and\n\nmanufactured the machine. Schechtl required that MetalForming\n\ninclude, with each machine, materials that instructed that\n\npurchaser to contact Schechtl directly, whether to purchase\n\nreplacement parts or to obtain assistance with troubleshooting and\n\nfixing problems. From the fact that hundreds of Schechtl parts\n\nwere delivered to Massachusetts, the inference is entirely\n\nplausible that Massachusetts purchasers did use the channels\n\nSchechtl established both as to spare parts and as to\n\ntroubleshooting.\n\n\n\n - 17 -\n\f Schechtl's channels to Massachusetts purchasers\n\nconstitute efforts to continue -- and perhaps to expand -- its\n\nrelationship with Massachusetts purchasers. Those deliberately\n\nopened channels, kept open over many years and presumably used,\n\nare relevant to the jurisdictional analysis. See Asahi, 480 U.S.\n\nat 112 (opinion of O'Connor, J.) (noting that \"establishing\n\nchannels for providing regular advice to customers in the forum\n\nState\" may be \"something more\" in support of jurisdiction). Those\n\nchannels established a direct link between Schechtl and its\n\npurchasers. Here that means that Schechtl voluntarily opened at\n\nleast forty-five such direct links with Massachusetts purchasers.\n\nSchechtl's long service of purchasers in Massachusetts through at\n\nleast its spare parts sales bolsters our conclusion that the\n\nexercise of jurisdiction here is foreseeable.3\n\n Purposeful availment analysis \"'will vary with the\n\nquality and the nature of the defendant's activity.'\" PREP Tours,\n\n2019 WL 126221, at *6 (quoting Burger King, 471 U.S. at 474-75).\n\nThis case involves a manufacturer which can direct where its\n\nproducts go, which sold dozens of expensive products into the forum\n\n\n 3 Schechtl argues that it did not know that CCC was located\nin Massachusetts. Even if that contention were correct, we would\nnot consider it dispositive given all the other facts here. We do\nnot comment on MetalForming's argument that Schechtl should have\nknown CCC's location.\n We also do not rest on, or even reach, the argument that\nSchechtl made no effort to exclude Massachusetts purchasers from\nits American market. Cf. Ainsworth, 716 F.3d at 179.\n - 18 -\n\fover nearly two decades, and which initiated an ongoing\n\nrelationship with its in-forum purchasers. Nicastro, by contrast,\n\ninvolved a manufacturer which lacked any similar ability to control\n\nthe end location of its products, see 564 U.S. at 878 (plurality\n\nopinion) (noting that there was \"no allegation that the distributor\n\nwas under [the defendant's] control\"), and which had no other\n\nrelationship with the forum, see id. at 886. The defendant there\n\nknew only \"that its products are distributed through a nationwide\n\ndistribution system that might lead to those products being sold\n\nin any of the fifty states.\" Id. at 879 (internal quotation marks\n\nomitted). None of the opinions from Nicastro require that we\n\naccept Schechtl's arguments on appeal.\n\n Schechtl's only remaining argument is that MetalForming\n\ntakes title to the Schechtl products in Germany. First Circuit\n\nlaw has long found this argument irrelevant to the jurisdictional\n\nanalysis. See Benitez-Allende v. Alcan Aluminio do Brasil, S.A.,\n\n857 F.2d 26, 30 (1st Cir. 1988) (Breyer, J.) (\"The fact that title\n\nto the [products] passed in [a foreign country] is beside the\n\npoint, for '[i]f International Shoe stands for anything, however,\n\nit is that a truly interstate business may not shield itself from\n\nsuit by a careful but formalistic structuring of its business\n\ndealings.'\" (quoting Vencedor Mfg. Co., Inc. v. Gougler Indus.,\n\nInc., 557 F.2d 886, 891 (1st Cir. 1977))). The same is true for\n\nan international business.\n\n - 19 -\n\fC. Reasonableness\n\n We explain briefly why we consider the exercise of\n\njurisdiction to be reasonable under the five \"gestalt\" factors:\n\n (1) the defendant's burden of appearing [in\n the forum], (2) the forum state's interest in\n adjudicating the dispute, (3) the plaintiff's\n interest in obtaining convenient and effective\n relief, (4) the judicial system's interest in\n obtaining the most effective resolution of the\n controversy, and (5) the common interests of\n all sovereigns in promoting substantive social\n policies.\n\n\nTicketmaster-N.Y., Inc. v. Alioto, 26 F.3d 201, 209 (1st Cir. 1994)\n\n(citing Burger King, 471 U.S. at 477). Schechtl in its briefs,\n\nbut not at oral argument, argues that Massachusetts litigation\n\nwould be burdensome because it is a German company with German\n\nemployees, and that cross-Atlantic travel and communications would\n\nimpose burdens on its employees. That there is some burden on\n\nSchechtl (which can be mitigated) is not enough on the facts here\n\nto make the exercise of jurisdiction unreasonable. See Plixer,\n\n905 F.3d at 13 (noting that \"'[w]hen minimum contacts have been\n\nestablished, often the interests of the plaintiff and the forum in\n\nthe exercise of jurisdiction will justify even the serious burdens\n\nplaced on the alien defendant'\" (quoting Asahi, 480 U.S. at 114\n\n(opinion of O'Connor, J.)); see also C.W. Downer, 771 F.3d at 70\n\n(noting that many of the case's logistical challenges \"can be\n\nresolved through the use of affidavits and video devices\").\n\n\n\n - 20 -\n\f III.\n\n We conclude that the exercise of personal jurisdiction\n\nover Schechtl comports with due process. We reverse and remand\n\nfor further proceedings consistent with this opinion.\n\n\n\n\n - 21 -\n[END_CASE]", "role": "user" } ]
8,443,859
IN RE: the FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Oaktree Opportunities Fund IX, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Value Opportunities Fund, L.P. Ocher Rose, L.L.C. SV Credit, L.P., Movants, Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Movants, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Movants, Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Movants, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Interested Party v. Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P., Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc. UBS IRA Select Growth & Income Puerto Rico Fund, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Interested Party v. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Movants, Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico Official Committee of Unsecured Creditors, Movants
Altair Global Credit Opportunities Fund (A), LLC v. Fin. Oversight & Mgmt. Bd. for P.R. (In re Fin. Oversight & Mgmt. Bd. for P.R.)
2019-01-30
Nos. 18-1836; 18-1837; No. 18-1841; No. 18-1855; No. 18-1858; No. 18-1868
U.S. Court of Appeals for the First Circuit
{"judges": "Kayatta, Lynch, Stahl", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415286/", "author_raw": ""}]}
KAYATTA
LYNCH
STAHL
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443859/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: IN RE: the FINANCIAL OVERSIGHT AND MANAGEMENT BOARD FOR PUERTO RICO, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Oaktree Opportunities Fund IX, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Value Opportunities Fund, L.P. Ocher Rose, L.L.C. SV Credit, L.P., Movants, Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Movants, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Movants, Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Movants, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Interested Party v. Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P., Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc. UBS IRA Select Growth & Income Puerto Rico Fund, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Official Committee of Retired Employees of the Commonwealth of Puerto Rico, Interested Party v. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, In re: the Financial Oversight and Management Board for Puerto Rico, as Representative for the Commonwealth of Puerto Rico the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Highways and Transportation Authority the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Electric Power Authority (PREPA) the Financial Oversight and Management Board for Puerto Rico, as Representative for the Puerto Rico Sales Tax Financing Corporation, a/k/a Cofina the Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtors. Puerto Rico AAA Portfolio Bond Fund, Inc. Puerto Rico AAA Portfolio Bond Fund II, Inc. Puerto Rico AAA Portfolio Target Maturity Fund, Inc. Puerto Rico Fixed Income Fund, Inc. Puerto Rico Fixed Income Fund II, Inc. Puerto Rico Fixed Income Fund III, Inc. Puerto Rico Fixed Income Fund IV, Inc. Puerto Rico Fixed Income Fund V, Inc. Puerto Rico GNMA and U.S. Government Target Maturity Fund, Inc. Puerto Rico Investors Bond Fund I, Inc. Puerto Rico Investors Tax-Free Fund, Inc. Puerto Rico Investors Tax-Free Fund II, Inc. Puerto Rico Investors Tax-Free Fund III, Inc. Puerto Rico Investors Tax-Free Fund IV, Inc. Puerto Rico Investors Tax-Free Fund V, Inc. Puerto Rico Investors Tax-Free Fund VI, Inc. Puerto Rico Mortgage-Backed & U.S. Government Securities Fund, Inc. Tax-Free Puerto Rico Fund, Inc. Tax-Free Puerto Rico Fund II, Inc. Tax-Free Puerto Rico Target Maturity Fund, Inc., Movants, Altair Global Credit Opportunities Fund (A), LLC Andalusian Global Designated Activity Company Glendon Opportunities Fund, LP Mason Capital Master Fund LP Nokota Capital Master Fund, L.P. Oaktree Opportunities Fund IX (Parallel 2), L.P. Oaktree Opportunities Fund IX, L.P. Oaktree Value Opportunities Fund, L.P. Oaktree-Forrest Multi-Strategy, L.L.C. (Series B) Ocher Rose, L.L.C. SV Credit, L.P. UBS IRA Select Growth & Income Puerto Rico Fund, Movants v. The Financial Oversight and Management Board for Puerto Rico, as Representative for the Employees Retirement System of the Government of the Commonwealth of Puerto Rico, Debtor, American Federation of State County and Municipal Employees Official Committee of Retired Employees of the Commonwealth of Puerto Rico Official Committee of Unsecured Creditors, Movants\nCourt: U.S. Court of Appeals for the First Circuit\nDate decided: 2019-01-30\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,578,863
Shabazz v. United States
2019-01-04
17-167-cr
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: 25 26 KATZMANN, Chief Judge, LEVAL, Circuit Judge, and BERMAN, 27 District Judge.", "parties": "", "opinions": [{"author": "LEVAL, Circuit Judge:", "type": "010combined", "text": "17-167-cr\n Shabazz v. United States of America\n\n 1 UNITED STATES COURT OF APPEALS \n 2 FOR THE SECOND CIRCUIT \n 3  \n 4 August Term, 2017 \n 5  \n 6 (Argued: February 26, 2018     Decided: January 4, 2019 ) \n 7  \n 8 Docket No. 17‐167 \n 9  \n10  \n11 _____________________________________ \n12  \n13 AL‐MALIK FRUITKWAN SHABAZZ, fka Edward Levi Singer, \n14  \n15 Petitioner‐Appellee, \n16  \n17 v. \n18  \n19 UNITED STATES OF AMERICA, \n20  \n21 Respondent‐Appellant. \n22 _____________________________________ \n23  \n24 Before:   \n25  \n26 KATZMANN, Chief Judge, LEVAL, Circuit Judge, and BERMAN, \n27 District Judge.* \n28  \n29   The government appeals from the judgment of the United States \n30 District Court for Connecticut (Stefan R. Underhill, J.) granting petitioner Al‐\n31 Malik Fruitkwan Shabazz’s motion under 28 U.S.C. § 2255 to set aside his \n32 sentence imposed under the Armed Career Criminal Act of 1984 (“ACCA”), \n33 18 U.S.C. § 924(e), on the ground that his prior convictions for robbery under \n34 Con. Gen. Stat. § 53a‐133 did not qualify as ACCA predicates under ACCA’s \n35 Force Clause, mandating a sentence of at least fifteen years imprisonment. \n\n\n * Judge Richard M. Berman, United States District Court for the Southern \n District of New York, sitting by designation.  \n\f 1 Held, any offense that satisfies the essential elements of robbery under § 53a‐\n 2 133 involves use or threat of force capable of causing pain or injury and thus \n 3 qualifies as an ACCA predicate. REVERSED.  \n 4              \n 5 CHARLES F. WILLSON, Federal \n 6 Defender’s Office, Hartford, CT, for \n 7 Petitioner‐Appellee.  \n 8  \n 9 JOCELYN COURTNEY KAOUTZANIS (Marc \n10 H. Silverman, on the brief), on behalf of \n11 Deirdre M. Daly, United States \n12 Attorney, District of Connecticut, New \n13 Haven, CT, for Respondent‐Appellant. \n14  \n15 LEVAL, Circuit Judge: \n\n16 This is an appeal by the United States from a grant of habeas corpus \n\n17 under 28 U.S.C. § 2255 by the United States District Court for the District of \n\n18 Connecticut (Stefan R. Underhill, J.) in favor of petitioner Al‐Malik Fruitkwan \n\n19 Shabazz, requiring reduction of Shabazz’s sentence. The question presented \n\n20 by the appeal is whether the offense of robbery, as defined by Connecticut’s \n\n21 basic robbery statute, Conn. Gen. Stat. § 53a‐133, is a “violent felony” as that \n\n22 term is used in the Armed Career Criminal Act of 1984 (“ACCA”), 18 U.S.C. § \n\n23 924(e). That issue turns on whether robbery, as specified in § 53a‐133, has as \n\n24 an essential element the use or threatened use of force that is capable of \n\n25 causing pain or injury. See Johnson v. United States, 559 U.S. 133 (2010) (“2010 \n\n26 Johnson”). \n\n 2 \n\f 1 Shabazz was convicted in 2004 in the United States District Court for \n\n 2 Connecticut on one count of unlawful possession of a firearm by a convicted \n\n 3 felon, in violation of 18 U.S.C. § 922(g)(1). At the time, Shabazz had, among \n\n 4 other convictions, four prior Connecticut state‐court robbery convictions \n\n 5 under § 53a‐133. If at least three of those prior convictions were for violent \n\n 6 felonies as that term has been defined by the Supreme Court for purposes of \n\n 7 the ACCA statute, ACCA mandated a sentence of at least fifteen years \n\n 8 imprisonment. In sentencing Shabazz for the firearm violation, the district \n\n 9 court concluded that a mandatory fifteen‐year sentence was required by \n\n10 ACCA and sentenced Shabazz to 235 months imprisonment. 1  \n\n11 Since that time, decisions of the United States Supreme Court and our \n\n12 court have substantially altered the meaning of ACCA. Shabazz brought this \n\n13 petition for habeas corpus contending that ACCA, as currently understood, \n\n14 no longer applies to his robbery convictions because, he argues, one can be \n\n15 convicted of robbery in Connecticut for a theft that does not employ force \n\n16 capable of causing pain or injury. The district court, in a thoughtful, scholarly \n\n\n\n\n 1 The district court started with the mandatory minimum sentence as the \n baseline and determined, based on aggravating circumstances of Shabazz’s \n offense, that a sentence above that minimum was warranted. \n 3 \n\f 1 opinion, agreed with Shabazz and granted his petition. The court vacated his \n\n 2 prior sentence, sentenced him to 120 months imprisonment, and released him \n\n 3 from custody because he had completed service of the new sentence. The \n\n 4 cornerstone of the district court’s ruling was that robbery under § 53a‐133 \n\n 5 does not necessarily involve use of force that is capable of causing pain or \n\n 6 injury.  \n\n 7 The government brought this appeal, arguing that Connecticut’s core \n\n 8 robbery statute does require force (or threat of force) that is capable of causing \n\n 9 pain or injury. If the government is correct, Shabazz had at least three prior \n\n10 violent felonies, and therefore faced a mandatory sentence of at least fifteen \n\n11 years under ACCA. \n\n12 We respectfully disagree with the district court’s view that \n\n13 Connecticut’s robbery statute does not require at a minimum force that would \n\n14 satisfy the ACCA standard. We think that the threat of force capable of \n\n15 causing pain or injury is inherent in the crime of robbery. Accordingly, we \n\n16 VACATE the judgment.  \n\n\n\n\n 4 \n\f 1 BACKGROUND \n\n 2 In 2005, Shabazz was convicted of one count of unlawful possession of \n\n 3 a firearm by a convicted felon, in violation of 18 U.S.C. §§ 922(g)(1). See United \n\n 4 States v. Singer, No. 3:04‐cr‐210‐1 (SRU) (doc. 1, 71). In addition to other \n\n 5 convictions, Shabazz had four prior Connecticut convictions for various \n\n 6 degrees of robbery, each of which included a conviction under § 53a‐133. \n\n 7 Robbery in Connecticut is defined under a statutory scheme that \n\n 8 includes a basic robbery offense under § 53a‐133, and additional statutes that \n\n 9 define the aggravating factors, such that all robbery convictions must include \n\n10 a conviction under § 53a‐133, and any conviction for aggravated degrees of \n\n11 robbery, such as first degree robbery or second degree robbery, requires an \n\n12 additional conviction under the statute that defines the aggravating factors. \n\n13 The basic definition of robbery under § 53a‐133 is as follows:   \n\n14 A  person  commits  robbery  when,  in  the  course  of \n15 committing a larceny, he uses or threatens the immediate use of \n16 physical  force  upon  another  person  for  the  purpose  of:  (1) \n17 Preventing or overcoming resistance to the taking of the property \n18 or  to  the  retention  thereof  immediately  after  the  taking  or  (2) \n19 compelling  the  owner  of  such  property  or  another  person  to \n20 deliver up the property or to engage in other conduct which aids \n21 in the commission of the larceny.  \n\n\n\n\n 5 \n\f1   ACCA specifies that a person who violates 18 U.S.C. § 922(g)(1)’s \n\n2 prohibition of possession of a firearm by a convicted felon and has three \n\n3 previous convictions “for a violent felony” (or a serious drug offense) is \n\n4 subject to a mandatory minimum sentence of fifteen years. 18 U.S.C. § \n\n5 924(e)(1).2 The term “violent felony” is defined to include any crime \n\n\n\n\n 2 The full text of 18 U.S.C. 924(e) states: (e)(1) In the case of a person who \n violates section 922(g) of this title and has three previous convictions by any \n court referred to in section 922(g)(1) of this title for a violent felony or a \n serious drug offense, or both, committed on occasions different from one \n another, such person shall be fined under this title and imprisoned not less \n than fifteen years, and, notwithstanding any other provision of law, the court \n shall not suspend the sentence of, or grant a probationary sentence to, such \n person with respect to the conviction under section 922(g).  \n (2) As used in this subsection—  \n (A) the term “serious drug offense” means—  \n (i) an offense under the Controlled Substances Act (21 U.S.C. 801 \n et seq.), the Controlled Substances Import and Export Act (21 U.S.C. \n 951 et seq.), or chapter 705 of title 46, for which a maximum term of \n imprisonment of ten years or more is prescribed by law; or  \n (ii) an offense under State law, involving manufacturing, \n distributing, or possessing with intent to manufacture or distribute, a \n controlled substance (as defined in section 102 of the Controlled \n Substances Act (21 U.S.C. 802), for which a maximum term of \n imprisonment of ten years or more is prescribed by law;  \n (B) the term “violent felony” means any crime punishable by \n imprisonment for a term exceeding one year, or any act of juvenile \n delinquency involving the use or carrying of a firearm, knife, or \n destructive device that would be punishable by imprisonment for such \n term if committed by an adult, that—  \n\n 6 \n\f 1 punishable by imprisonment for a term exceeding one year that falls into any \n\n 2 of three categories that are defined in clauses (i) and (ii) of § 924(e)(1)(B). The \n\n 3 first of these, known as the Force Clause, set forth in subsection (i), is the \n\n 4 subject of this appeal. It specifies that the offense “(i) has as an element the \n\n 5 use, attempted use, or threatened use of physical force against the person of \n\n 6 another.” 18 U.S.C. § 924(e)(2)(B)(i). The second and third categories, the so‐\n\n 7 called Enumerated Felonies Clause and the Residual Clause, are set forth in \n\n 8 subsection (ii). The Enumerated Felonies Clause includes any offense that “is \n\n 9 burglary, arson, or extortion, [or] involves use of explosives.” 18 U.S.C. § \n\n10 924(e)(2)(B)(ii). The Residual Clause includes any offense that “otherwise \n\n11 involves conduct that presents a serious potential risk of physical injury to \n\n12 another.” Id. In order to determine whether a prior conviction comes within \n\n13 one of the aggravating categories, the Supreme Court ruled in Taylor v. United \n\n\n (i) has as an element the use, attempted use, or threatened use of \n physical force against the person of another; or  \n (ii) is burglary, arson, or extortion, involves use of explosives, or \n otherwise involves conduct that presents a serious potential risk of physical \n injury to another; and  \n (C) the term “conviction” includes a finding that a person has \n committed an act of juvenile delinquency involving a violent felony. \n (The language in italics has been found constitutionally invalid and may not \n be used for sentencing purposes. Johnson v. United States, 135 S.Ct. 2551 \n (2015).) \n 7 \n\f 1 States, 495 U.S. 575, 600 (1990), that the court must employ a “categorical \n\n 2 approach,” looking not at the facts of the defendant’s prior crimes but at the \n\n 3 statute under which he was convicted to determine whether the essential \n\n 4 elements of that statute bring the crime within the ACCA requirements.  \n\n 5 In sentencing Shabazz on his 2005 conviction for unlawful gun \n\n 6 possession, the court concluded on the basis of his prior Connecticut robbery \n\n 7 convictions that he was subject to ACCA’s fifteen‐year mandatory minimum \n\n 8 sentence. The court did not explain which of the clauses of the ACCA statute \n\n 9 justified its application to his case. Shabazz timely appealed his conviction \n\n10 without contesting the applicability of ACCA, and our court affirmed the \n\n11 judgment by summary order. United States v. Singer, 241 F. App’x 727, 729 (2d \n\n12 Cir. 2007).  \n\n13 Subsequent to his conviction, court decisions have altered the meaning \n\n14 of the ACCA statute. In 2010, the Supreme Court interpreted the phrase \n\n15 “physical force” in the Force Clause. See Johnson v. United States, 559 U.S. 133 \n\n16 (2010) (“2010 Johnson”). The Supreme Court reasoned that because the term \n\n17 “physical force” occurred “in the context of a statutory definition of ‘violent \n\n18 felony,’” the physical force invoked by the statute needed to be “violent \n\n\n\n 8 \n\f 1 force—that is, force capable of causing physical pain or injury to another \n\n 2 person.” Id. at 140 (emphasis in original). Therefore, in order for a previous \n\n 3 conviction to qualify as an ACCA predicate under the Force Clause, the \n\n 4 statutory definition of the crime must require force capable of causing \n\n 5 physical pain or injury to another person, or the threat of such force. Id. Then, \n\n 6 in 2015, in Johnson v. Unites States, 153 S. Ct. 2551 (2015) (“2015 Johnson”), the \n\n 7 Supreme Court struck down ACCA’s Residual Clause, finding it to be \n\n 8 unconstitutionally vague.  \n\n 9 After 2015 Johnson, Shabazz brought this petition, arguing that his \n\n10 sentence must be set aside because, to the extent the application of ACCA \n\n11 might have depended on the Residual Clause, that clause has since been \n\n12 invalidated, and to the extent it might have depended on the Force Clause, \n\n13 that would have been improper because the crime of robbery as defined by \n\n14 § 53a‐133 can be committed by use of force that is not sufficient to cause pain \n\n15 or injury. \n\n16 The issue before the district court was whether any three of Shabazz’s \n\n17 prior Connecticut robbery convictions were obtained under a statute that \n\n\n\n\n 9 \n\f 1 required as an essential element the use or threat of force capable of causing \n\n 2 pain or injury.  \n\n 3 On January 3, 2017, the district court issued a written ruling granting \n\n 4 Shabazz’s § 2255 motion and vacating his sentence. The court ruled that \n\n 5 simple robbery under § 53a‐133, without aggravating factors, does not qualify \n\n 6 as an ACCA predicate because the crime can be committed by use of levels of \n\n 7 force so slight that they are not capable of causing pain or injury. Thus, \n\n 8 notwithstanding that two of Shabazz’s convictions for first degree robbery \n\n 9 qualified as crimes of violence because the aggravating factor necessarily \n\n10 involved violent force, his other robbery convictions did not require violence. \n\n11 Having only two, and not three, prior violent felonies, Shabazz did not \n\n12 qualify for mandatory sentencing under ACCA.3 The government brought \n\n13 this appeal.    \n\n14 DISCUSSION \n\n\n\n\n 3 The district court, in adjudicating Shabazz’s petition under § 2255, \n concluded that, in passing Shabazz’s sentence in 2005, it had probably relied, \n at least in part, on the now‐unconstitutional Residual Clause to determine \n that ACCA’s mandatory sentencing provision applied. If the elements of \n § 53a‐133 require violent force, ACCA’s sentencing provision mandatorily \n applied to Shabazz under the Force Clause, so that even if the sentencing \n court had erroneously relied on the Residual Clause, the error was harmless.  \n 10 \n\f 1 The government contends that robbery under § 53a‐133 requires force \n\n 2 capable of causing pain or injury, so that, regardless of whether Shabazz was \n\n 3 convicted of aggravating factors, each of his Connecticut robbery convictions \n\n 4 qualifies as a violent felony within the meaning of ACCA’s Force Clause. \n\n 5 Employing the categorical approach mandated by Taylor, 495 U.S. at 600; see \n\n 6 also Mathis v. United States, 136 S. Ct. 2243, 2248‐49 (2016) (outlining the \n\n 7 categorical approach); Descamps v. United States, 570 U.S. 254, 257 (2013) \n\n 8 (same), courts identify “the minimum criminal conduct necessary for \n\n 9 conviction under a particular statute.” United States v. Acosta, 470 F.3d 132, 135 \n\n10 (2d Cir. 2006). “The reviewing court ‘cannot go behind the offense as it was \n\n11 charged to reach [its] own determination as to whether the underlying facts’ \n\n12 qualify the offense as,” in this case, a violent felony. Hill, 890 F.3d at 55 \n\n13 (quoting Ming Lam Sui v. INS, 250 F.3d 105, 117‐18 (2d Cir. 2001)).  \n\n14 Connecticut’s statute defines robbery essentially as it is understood in \n\n15 the common law and largely throughout the United States, as requiring the \n\n16 use or threat of force to take property from the person of another without the \n\n17 person’s consent. Robbery has consistently been treated as an aggravated \n\n18 form of larceny because the taking of property from the person of another \n\n\n\n 11 \n\f 1 against the victim’s will by force or threat of force is inevitably capable of \n\n 2 causing physical harm to the victim, regardless of whether the force actually \n\n 3 employed in the taking of the property is by itself sufficient to cause pain or \n\n 4 injury. Scholars of the criminal law underline the inherent potential for \n\n 5 physical harm to the victim as the explanation why robbery developed as, \n\n 6 and continues to be treated as, an aggravated felony, generally carrying \n\n 7 harsher punishments than other forms of larceny. See 3 W. LaFave, \n\n 8 Substantive Criminal Law § 20.3, p. 221 (3d ed. 2017) (“Robbery, a common‐\n\n 9 law felony, and today everywhere a statutory felony regardless of the amount \n\n10 taken, may be thought of as aggravated larceny—misappropriation of \n\n11 property under circumstances involving a danger to the person as well as a danger \n\n12 to property—and thus deserving of a greater punishment than that provided \n\n13 for larceny. Robbery consists of all six elements of larceny . . . plus two \n\n14 additional requirements: [(1)] that the property be taken from the person or \n\n15 presence of the other and [(2)] that the taking be accomplished by means of \n\n16 force or putting in fear.”) (emphasis added); see also id. at 222 n.4 (“Robbery \n\n17 may be considered a greater crime than the sum of the two lesser crimes of \n\n18 larceny and assault (or battery). As stated in Model Penal Code § 222.1, \n\n\n\n 12 \n\f 1 Comment at 98 (1980):  . . . [T]he robber may be distinguished from the \n\n 2 stealthy thief by the hardihood that enables him to carry out his purpose in \n\n 3 the presence of his victim and over his opposition—obstacles that might deter \n\n 4 ordinary sneak thieves and that justify the feeling of special danger evoked by \n\n 5 robbery.”) (emphasis added); E. Podgor, P. Henning, and N. Cohen, Mastering \n\n 6 Criminal Law, p. 215 (2d ed. 2015) (“Robbery, often punished by a lengthy \n\n 7 prison term, is an aggravated form of larceny. The offense entails a larceny \n\n 8 coupled with the use of force or a threat of violence to dispossess the victim of \n\n 9 the property. Robbery is deemed a very serious crime, a felony in every \n\n10 jurisdiction, because it presents the real danger of immediate serious physical harm \n\n11 to the victim. . . . Because the actual or potential bodily harm is the primary \n\n12 concern with robbery, it occurs irrespective of the value of the items taken.”) \n\n13 (emphasis added). \n\n14 Notwithstanding a robber’s actual use of minimal force (that would not \n\n15 in itself cause pain or injury) to take property from the person of another \n\n16 against the victim’s will, those face‐to‐face circumstances inherently carry an \n\n17 implicit threat of escalation, perhaps because of the victim’s predictable \n\n18 reaction, capable of resulting in physical harm. Therefore, even such minimal \n\n\n\n 13 \n\f 1 force, when employed in a taking of property from the person of another, \n\n 2 inherently implicates a realistic threat of causing pain or injury, so that the \n\n 3 crime qualifies as an ACCA predicate under 2010 Johnson.4 We therefore \n\n 4 conclude that the district court erred in its belief that, because the crime of \n\n 5 robbery could be committed through the actual use of minimal physical force, \n\n 6 it should not be deemed to fall within the category of a crime capable of \n\n 7 causing pain or injury.  \n\n 8 We conclude that the use or threat of even minimal force on another \n\n 9 person in aid of the theft of that person’s property, as required by § 53a‐133, is \n\n10 inherently capable of causing pain or injury, with the consequence that any \n\n11 violation of § 53a‐133 qualifies as an ACCA predicate. Shabazz had three or \n\n\n\n\n 4 We note that the Supreme Court, in a very recent decision, see United States \n v. Stitt, 139 S. Ct. 399 (2018), considered whether two state burglary statutes \n covering entry into vehicles designed or adapted for overnight \n accommodation categorically fit within the generic definition of “burglary” in \n the Enumerated Felonies Clause. In holding in the affirmative and \n distinguishing from earlier cases, Stitt relied in significant part on the \n “inherently dangerous” nature of such burglaries because they create a more \n significant likelihood of in‐person confrontation than burglaries of premises \n that are less likely to be occupied. See id. at 406‐07. Because, among other \n reasons, the statutes in question applied exclusively to a category of \n burglaries more likely to result in a violent confrontation, the Court held that \n they fit the enumerated felony of burglary. \n\n 14 \n\f 1 more such ACCA predicates. ACCA therefore mandated that he be sentenced \n\n 2 to no less than fifteen years imprisonment.  \n\n 3 Accordingly, we VACATE the district court’s judgment. The district \n\n 4 court’s judgment on Shabazz’s petition vacated his original sentence, \n\n 5 substituting the court’s new, lesser sentence. The effect of our ruling vacating \n\n 6 that judgment is to reinstate the original sentence.  \n\n 7 CONCLUSION \n\n 8   For the foregoing reasons, the district court’s judgment vacating \n\n 9 Shabazz’s sentence is VACATED, with the consequence that the original \n\n10 sentence is reinstated.  \n\n\n\n\n 15", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356116/", "author_raw": "LEVAL, Circuit Judge:"}]}
KATZMANN
LEVAL
BERMAN
1
{"KATZMANN": ", Chief", "LEVAL": ", Circuit", "BERMAN": ", District"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578863/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Shabazz v. United States\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-04\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17-167-cr\n Shabazz v. United States of America\n\n 1 UNITED STATES COURT OF APPEALS \n 2 FOR THE SECOND CIRCUIT \n 3  \n 4 August Term, 2017 \n 5  \n 6 (Argued: February 26, 2018     Decided: January 4, 2019 ) \n 7  \n 8 Docket No. 17‐167 \n 9  \n10  \n11 _____________________________________ \n12  \n13 AL‐MALIK FRUITKWAN SHABAZZ, fka Edward Levi Singer, \n14  \n15 Petitioner‐Appellee, \n16  \n17 v. \n18  \n19 UNITED STATES OF AMERICA, \n20  \n21 Respondent‐Appellant. \n22 _____________________________________ \n23  \n24 Before:   \n25  \n26 KATZMANN, Chief Judge, LEVAL, Circuit Judge, and BERMAN, \n27 District Judge.* \n28  \n29   The government appeals from the judgment of the United States \n30 District Court for Connecticut (Stefan R. Underhill, J.) granting petitioner Al‐\n31 Malik Fruitkwan Shabazz’s motion under 28 U.S.C. § 2255 to set aside his \n32 sentence imposed under the Armed Career Criminal Act of 1984 (“ACCA”), \n33 18 U.S.C. § 924(e), on the ground that his prior convictions for robbery under \n34 Con. Gen. Stat. § 53a‐133 did not qualify as ACCA predicates under ACCA’s \n35 Force Clause, mandating a sentence of at least fifteen years imprisonment. \n\n\n * Judge Richard M. Berman, United States District Court for the Southern \n District of New York, sitting by designation.  \n\f 1 Held, any offense that satisfies the essential elements of robbery under § 53a‐\n 2 133 involves use or threat of force capable of causing pain or injury and thus \n 3 qualifies as an ACCA predicate. REVERSED.  \n 4              \n 5 CHARLES F. WILLSON, Federal \n 6 Defender’s Office, Hartford, CT, for \n 7 Petitioner‐Appellee.  \n 8  \n 9 JOCELYN COURTNEY KAOUTZANIS (Marc \n10 H. Silverman, on the brief), on behalf of \n11 Deirdre M. Daly, United States \n12 Attorney, District of Connecticut, New \n13 Haven, CT, for Respondent‐Appellant. \n14  \n15 LEVAL, Circuit Judge: \n\n16 This is an appeal by the United States from a grant of habeas corpus \n\n17 under 28 U.S.C. § 2255 by the United States District Court for the District of \n\n18 Connecticut (Stefan R. Underhill, J.) in favor of petitioner Al‐Malik Fruitkwan \n\n19 Shabazz, requiring reduction of Shabazz’s sentence. The question presented \n\n20 by the appeal is whether the offense of robbery, as defined by Connecticut’s \n\n21 basic robbery statute, Conn. Gen. Stat. § 53a‐133, is a “violent felony” as that \n\n22 term is used in the Armed Career Criminal Act of 1984 (“ACCA”), 18 U.S.C. § \n\n23 924(e). That issue turns on whether robbery, as specified in § 53a‐133, has as \n\n24 an essential element the use or threatened use of force that is capable of \n\n25 causing pain or injury. See Johnson v. United States, 559 U.S. 133 (2010) (“2010 \n\n26 Johnson”). \n\n 2 \n\f 1 Shabazz was convicted in 2004 in the United States District Court for \n\n 2 Connecticut on one count of unlawful possession of a firearm by a convicted \n\n 3 felon, in violation of 18 U.S.C. § 922(g)(1). At the time, Shabazz had, among \n\n 4 other convictions, four prior Connecticut state‐court robbery convictions \n\n 5 under § 53a‐133. If at least three of those prior convictions were for violent \n\n 6 felonies as that term has been defined by the Supreme Court for purposes of \n\n 7 the ACCA statute, ACCA mandated a sentence of at least fifteen years \n\n 8 imprisonment. In sentencing Shabazz for the firearm violation, the district \n\n 9 court concluded that a mandatory fifteen‐year sentence was required by \n\n10 ACCA and sentenced Shabazz to 235 months imprisonment. 1  \n\n11 Since that time, decisions of the United States Supreme Court and our \n\n12 court have substantially altered the meaning of ACCA. Shabazz brought this \n\n13 petition for habeas corpus contending that ACCA, as currently understood, \n\n14 no longer applies to his robbery convictions because, he argues, one can be \n\n15 convicted of robbery in Connecticut for a theft that does not employ force \n\n16 capable of causing pain or injury. The district court, in a thoughtful, scholarly \n\n\n\n\n 1 The district court started with the mandatory minimum sentence as the \n baseline and determined, based on aggravating circumstances of Shabazz’s \n offense, that a sentence above that minimum was warranted. \n 3 \n\f 1 opinion, agreed with Shabazz and granted his petition. The court vacated his \n\n 2 prior sentence, sentenced him to 120 months imprisonment, and released him \n\n 3 from custody because he had completed service of the new sentence. The \n\n 4 cornerstone of the district court’s ruling was that robbery under § 53a‐133 \n\n 5 does not necessarily involve use of force that is capable of causing pain or \n\n 6 injury.  \n\n 7 The government brought this appeal, arguing that Connecticut’s core \n\n 8 robbery statute does require force (or threat of force) that is capable of causing \n\n 9 pain or injury. If the government is correct, Shabazz had at least three prior \n\n10 violent felonies, and therefore faced a mandatory sentence of at least fifteen \n\n11 years under ACCA. \n\n12 We respectfully disagree with the district court’s view that \n\n13 Connecticut’s robbery statute does not require at a minimum force that would \n\n14 satisfy the ACCA standard. We think that the threat of force capable of \n\n15 causing pain or injury is inherent in the crime of robbery. Accordingly, we \n\n16 VACATE the judgment.  \n\n\n\n\n 4 \n\f 1 BACKGROUND \n\n 2 In 2005, Shabazz was convicted of one count of unlawful possession of \n\n 3 a firearm by a convicted felon, in violation of 18 U.S.C. §§ 922(g)(1). See United \n\n 4 States v. Singer, No. 3:04‐cr‐210‐1 (SRU) (doc. 1, 71). In addition to other \n\n 5 convictions, Shabazz had four prior Connecticut convictions for various \n\n 6 degrees of robbery, each of which included a conviction under § 53a‐133. \n\n 7 Robbery in Connecticut is defined under a statutory scheme that \n\n 8 includes a basic robbery offense under § 53a‐133, and additional statutes that \n\n 9 define the aggravating factors, such that all robbery convictions must include \n\n10 a conviction under § 53a‐133, and any conviction for aggravated degrees of \n\n11 robbery, such as first degree robbery or second degree robbery, requires an \n\n12 additional conviction under the statute that defines the aggravating factors. \n\n13 The basic definition of robbery under § 53a‐133 is as follows:   \n\n14 A  person  commits  robbery  when,  in  the  course  of \n15 committing a larceny, he uses or threatens the immediate use of \n16 physical  force  upon  another  person  for  the  purpose  of:  (1) \n17 Preventing or overcoming resistance to the taking of the property \n18 or  to  the  retention  thereof  immediately  after  the  taking  or  (2) \n19 compelling  the  owner  of  such  property  or  another  person  to \n20 deliver up the property or to engage in other conduct which aids \n21 in the commission of the larceny.  \n\n\n\n\n 5 \n\f1   ACCA specifies that a person who violates 18 U.S.C. § 922(g)(1)’s \n\n2 prohibition of possession of a firearm by a convicted felon and has three \n\n3 previous convictions “for a violent felony” (or a serious drug offense) is \n\n4 subject to a mandatory minimum sentence of fifteen years. 18 U.S.C. § \n\n5 924(e)(1).2 The term “violent felony” is defined to include any crime \n\n\n\n\n 2 The full text of 18 U.S.C. 924(e) states: (e)(1) In the case of a person who \n violates section 922(g) of this title and has three previous convictions by any \n court referred to in section 922(g)(1) of this title for a violent felony or a \n serious drug offense, or both, committed on occasions different from one \n another, such person shall be fined under this title and imprisoned not less \n than fifteen years, and, notwithstanding any other provision of law, the court \n shall not suspend the sentence of, or grant a probationary sentence to, such \n person with respect to the conviction under section 922(g).  \n (2) As used in this subsection—  \n (A) the term “serious drug offense” means—  \n (i) an offense under the Controlled Substances Act (21 U.S.C. 801 \n et seq.), the Controlled Substances Import and Export Act (21 U.S.C. \n 951 et seq.), or chapter 705 of title 46, for which a maximum term of \n imprisonment of ten years or more is prescribed by law; or  \n (ii) an offense under State law, involving manufacturing, \n distributing, or possessing with intent to manufacture or distribute, a \n controlled substance (as defined in section 102 of the Controlled \n Substances Act (21 U.S.C. 802), for which a maximum term of \n imprisonment of ten years or more is prescribed by law;  \n (B) the term “violent felony” means any crime punishable by \n imprisonment for a term exceeding one year, or any act of juvenile \n delinquency involving the use or carrying of a firearm, knife, or \n destructive device that would be punishable by imprisonment for such \n term if committed by an adult, that—  \n\n 6 \n\f 1 punishable by imprisonment for a term exceeding one year that falls into any \n\n 2 of three categories that are defined in clauses (i) and (ii) of § 924(e)(1)(B). The \n\n 3 first of these, known as the Force Clause, set forth in subsection (i), is the \n\n 4 subject of this appeal. It specifies that the offense “(i) has as an element the \n\n 5 use, attempted use, or threatened use of physical force against the person of \n\n 6 another.” 18 U.S.C. § 924(e)(2)(B)(i). The second and third categories, the so‐\n\n 7 called Enumerated Felonies Clause and the Residual Clause, are set forth in \n\n 8 subsection (ii). The Enumerated Felonies Clause includes any offense that “is \n\n 9 burglary, arson, or extortion, [or] involves use of explosives.” 18 U.S.C. § \n\n10 924(e)(2)(B)(ii). The Residual Clause includes any offense that “otherwise \n\n11 involves conduct that presents a serious potential risk of physical injury to \n\n12 another.” Id. In order to determine whether a prior conviction comes within \n\n13 one of the aggravating categories, the Supreme Court ruled in Taylor v. United \n\n\n (i) has as an element the use, attempted use, or threatened use of \n physical force against the person of another; or  \n (ii) is burglary, arson, or extortion, involves use of explosives, or \n otherwise involves conduct that presents a serious potential risk of physical \n injury to another; and  \n (C) the term “conviction” includes a finding that a person has \n committed an act of juvenile delinquency involving a violent felony. \n (The language in italics has been found constitutionally invalid and may not \n be used for sentencing purposes. Johnson v. United States, 135 S.Ct. 2551 \n (2015).) \n 7 \n\f 1 States, 495 U.S. 575, 600 (1990), that the court must employ a “categorical \n\n 2 approach,” looking not at the facts of the defendant’s prior crimes but at the \n\n 3 statute under which he was convicted to determine whether the essential \n\n 4 elements of that statute bring the crime within the ACCA requirements.  \n\n 5 In sentencing Shabazz on his 2005 conviction for unlawful gun \n\n 6 possession, the court concluded on the basis of his prior Connecticut robbery \n\n 7 convictions that he was subject to ACCA’s fifteen‐year mandatory minimum \n\n 8 sentence. The court did not explain which of the clauses of the ACCA statute \n\n 9 justified its application to his case. Shabazz timely appealed his conviction \n\n10 without contesting the applicability of ACCA, and our court affirmed the \n\n11 judgment by summary order. United States v. Singer, 241 F. App’x 727, 729 (2d \n\n12 Cir. 2007).  \n\n13 Subsequent to his conviction, court decisions have altered the meaning \n\n14 of the ACCA statute. In 2010, the Supreme Court interpreted the phrase \n\n15 “physical force” in the Force Clause. See Johnson v. United States, 559 U.S. 133 \n\n16 (2010) (“2010 Johnson”). The Supreme Court reasoned that because the term \n\n17 “physical force” occurred “in the context of a statutory definition of ‘violent \n\n18 felony,’” the physical force invoked by the statute needed to be “violent \n\n\n\n 8 \n\f 1 force—that is, force capable of causing physical pain or injury to another \n\n 2 person.” Id. at 140 (emphasis in original). Therefore, in order for a previous \n\n 3 conviction to qualify as an ACCA predicate under the Force Clause, the \n\n 4 statutory definition of the crime must require force capable of causing \n\n 5 physical pain or injury to another person, or the threat of such force. Id. Then, \n\n 6 in 2015, in Johnson v. Unites States, 153 S. Ct. 2551 (2015) (“2015 Johnson”), the \n\n 7 Supreme Court struck down ACCA’s Residual Clause, finding it to be \n\n 8 unconstitutionally vague.  \n\n 9 After 2015 Johnson, Shabazz brought this petition, arguing that his \n\n10 sentence must be set aside because, to the extent the application of ACCA \n\n11 might have depended on the Residual Clause, that clause has since been \n\n12 invalidated, and to the extent it might have depended on the Force Clause, \n\n13 that would have been improper because the crime of robbery as defined by \n\n14 § 53a‐133 can be committed by use of force that is not sufficient to cause pain \n\n15 or injury. \n\n16 The issue before the district court was whether any three of Shabazz’s \n\n17 prior Connecticut robbery convictions were obtained under a statute that \n\n\n\n\n 9 \n\f 1 required as an essential element the use or threat of force capable of causing \n\n 2 pain or injury.  \n\n 3 On January 3, 2017, the district court issued a written ruling granting \n\n 4 Shabazz’s § 2255 motion and vacating his sentence. The court ruled that \n\n 5 simple robbery under § 53a‐133, without aggravating factors, does not qualify \n\n 6 as an ACCA predicate because the crime can be committed by use of levels of \n\n 7 force so slight that they are not capable of causing pain or injury. Thus, \n\n 8 notwithstanding that two of Shabazz’s convictions for first degree robbery \n\n 9 qualified as crimes of violence because the aggravating factor necessarily \n\n10 involved violent force, his other robbery convictions did not require violence. \n\n11 Having only two, and not three, prior violent felonies, Shabazz did not \n\n12 qualify for mandatory sentencing under ACCA.3 The government brought \n\n13 this appeal.    \n\n14 DISCUSSION \n\n\n\n\n 3 The district court, in adjudicating Shabazz’s petition under § 2255, \n concluded that, in passing Shabazz’s sentence in 2005, it had probably relied, \n at least in part, on the now‐unconstitutional Residual Clause to determine \n that ACCA’s mandatory sentencing provision applied. If the elements of \n § 53a‐133 require violent force, ACCA’s sentencing provision mandatorily \n applied to Shabazz under the Force Clause, so that even if the sentencing \n court had erroneously relied on the Residual Clause, the error was harmless.  \n 10 \n\f 1 The government contends that robbery under § 53a‐133 requires force \n\n 2 capable of causing pain or injury, so that, regardless of whether Shabazz was \n\n 3 convicted of aggravating factors, each of his Connecticut robbery convictions \n\n 4 qualifies as a violent felony within the meaning of ACCA’s Force Clause. \n\n 5 Employing the categorical approach mandated by Taylor, 495 U.S. at 600; see \n\n 6 also Mathis v. United States, 136 S. Ct. 2243, 2248‐49 (2016) (outlining the \n\n 7 categorical approach); Descamps v. United States, 570 U.S. 254, 257 (2013) \n\n 8 (same), courts identify “the minimum criminal conduct necessary for \n\n 9 conviction under a particular statute.” United States v. Acosta, 470 F.3d 132, 135 \n\n10 (2d Cir. 2006). “The reviewing court ‘cannot go behind the offense as it was \n\n11 charged to reach [its] own determination as to whether the underlying facts’ \n\n12 qualify the offense as,” in this case, a violent felony. Hill, 890 F.3d at 55 \n\n13 (quoting Ming Lam Sui v. INS, 250 F.3d 105, 117‐18 (2d Cir. 2001)).  \n\n14 Connecticut’s statute defines robbery essentially as it is understood in \n\n15 the common law and largely throughout the United States, as requiring the \n\n16 use or threat of force to take property from the person of another without the \n\n17 person’s consent. Robbery has consistently been treated as an aggravated \n\n18 form of larceny because the taking of property from the person of another \n\n\n\n 11 \n\f 1 against the victim’s will by force or threat of force is inevitably capable of \n\n 2 causing physical harm to the victim, regardless of whether the force actually \n\n 3 employed in the taking of the property is by itself sufficient to cause pain or \n\n 4 injury. Scholars of the criminal law underline the inherent potential for \n\n 5 physical harm to the victim as the explanation why robbery developed as, \n\n 6 and continues to be treated as, an aggravated felony, generally carrying \n\n 7 harsher punishments than other forms of larceny. See 3 W. LaFave, \n\n 8 Substantive Criminal Law § 20.3, p. 221 (3d ed. 2017) (“Robbery, a common‐\n\n 9 law felony, and today everywhere a statutory felony regardless of the amount \n\n10 taken, may be thought of as aggravated larceny—misappropriation of \n\n11 property under circumstances involving a danger to the person as well as a danger \n\n12 to property—and thus deserving of a greater punishment than that provided \n\n13 for larceny. Robbery consists of all six elements of larceny . . . plus two \n\n14 additional requirements: [(1)] that the property be taken from the person or \n\n15 presence of the other and [(2)] that the taking be accomplished by means of \n\n16 force or putting in fear.”) (emphasis added); see also id. at 222 n.4 (“Robbery \n\n17 may be considered a greater crime than the sum of the two lesser crimes of \n\n18 larceny and assault (or battery). As stated in Model Penal Code § 222.1, \n\n\n\n 12 \n\f 1 Comment at 98 (1980):  . . . [T]he robber may be distinguished from the \n\n 2 stealthy thief by the hardihood that enables him to carry out his purpose in \n\n 3 the presence of his victim and over his opposition—obstacles that might deter \n\n 4 ordinary sneak thieves and that justify the feeling of special danger evoked by \n\n 5 robbery.”) (emphasis added); E. Podgor, P. Henning, and N. Cohen, Mastering \n\n 6 Criminal Law, p. 215 (2d ed. 2015) (“Robbery, often punished by a lengthy \n\n 7 prison term, is an aggravated form of larceny. The offense entails a larceny \n\n 8 coupled with the use of force or a threat of violence to dispossess the victim of \n\n 9 the property. Robbery is deemed a very serious crime, a felony in every \n\n10 jurisdiction, because it presents the real danger of immediate serious physical harm \n\n11 to the victim. . . . Because the actual or potential bodily harm is the primary \n\n12 concern with robbery, it occurs irrespective of the value of the items taken.”) \n\n13 (emphasis added). \n\n14 Notwithstanding a robber’s actual use of minimal force (that would not \n\n15 in itself cause pain or injury) to take property from the person of another \n\n16 against the victim’s will, those face‐to‐face circumstances inherently carry an \n\n17 implicit threat of escalation, perhaps because of the victim’s predictable \n\n18 reaction, capable of resulting in physical harm. Therefore, even such minimal \n\n\n\n 13 \n\f 1 force, when employed in a taking of property from the person of another, \n\n 2 inherently implicates a realistic threat of causing pain or injury, so that the \n\n 3 crime qualifies as an ACCA predicate under 2010 Johnson.4 We therefore \n\n 4 conclude that the district court erred in its belief that, because the crime of \n\n 5 robbery could be committed through the actual use of minimal physical force, \n\n 6 it should not be deemed to fall within the category of a crime capable of \n\n 7 causing pain or injury.  \n\n 8 We conclude that the use or threat of even minimal force on another \n\n 9 person in aid of the theft of that person’s property, as required by § 53a‐133, is \n\n10 inherently capable of causing pain or injury, with the consequence that any \n\n11 violation of § 53a‐133 qualifies as an ACCA predicate. Shabazz had three or \n\n\n\n\n 4 We note that the Supreme Court, in a very recent decision, see United States \n v. Stitt, 139 S. Ct. 399 (2018), considered whether two state burglary statutes \n covering entry into vehicles designed or adapted for overnight \n accommodation categorically fit within the generic definition of “burglary” in \n the Enumerated Felonies Clause. In holding in the affirmative and \n distinguishing from earlier cases, Stitt relied in significant part on the \n “inherently dangerous” nature of such burglaries because they create a more \n significant likelihood of in‐person confrontation than burglaries of premises \n that are less likely to be occupied. See id. at 406‐07. Because, among other \n reasons, the statutes in question applied exclusively to a category of \n burglaries more likely to result in a violent confrontation, the Court held that \n they fit the enumerated felony of burglary. \n\n 14 \n\f 1 more such ACCA predicates. ACCA therefore mandated that he be sentenced \n\n 2 to no less than fifteen years imprisonment.  \n\n 3 Accordingly, we VACATE the district court’s judgment. The district \n\n 4 court’s judgment on Shabazz’s petition vacated his original sentence, \n\n 5 substituting the court’s new, lesser sentence. The effect of our ruling vacating \n\n 6 that judgment is to reinstate the original sentence.  \n\n 7 CONCLUSION \n\n 8   For the foregoing reasons, the district court’s judgment vacating \n\n 9 Shabazz’s sentence is VACATED, with the consequence that the original \n\n10 sentence is reinstated.  \n\n\n\n\n 15\n[END_CASE]", "role": "user" } ]
8,443,822
Al-Malik Fruitkwan SHABAZZ, fka Edward Levi Singer v. United States
Shabazz v. United States
2019-01-04
Docket No. 17-167; August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Berman, Katzmann, Leval", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415248/", "author_raw": ""}]}
BERMAN
KATZMANN
LEVAL
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443822/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Al-Malik Fruitkwan SHABAZZ, fka Edward Levi Singer v. United States\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-04\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,579,880
The PACA Trust Creditors v. Genecco Produce Inc.
2019-01-09
17-1949-(L)
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: SACK, RAGGI, AND CHIN, Circuit Judges.", "parties": "", "opinions": [{"author": "SACK, Circuit Judge:", "type": "010combined", "text": "17‐1949‐(L) \nThe PACA Trust Creditors v. Genecco Produce Inc. \n \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n August Term, 2018 \n (Submitted: September 5, 2018  Decided: January 9, 2019) \n Docket Nos. 17‐1949‐cv, 17‐2051‐cv \n\n  \n  \n THE PACA TRUST CREDITORS OF LENNY PERRYʹS PRODUCE, INC., \n Plaintiffs‐Appellees‐Cross‐Appellants, \n\n v. \n\n GENECCO PRODUCE INC., DAVID GENECCO, \n Defendants‐Appellants‐Cross‐Appellees.* \n  \n  \nBefore:  SACK, RAGGI, AND CHIN, Circuit Judges. \n\n The plaintiffs brought an adversary proceeding in the United States \n\nBankruptcy Court for the Western District of New York alleging that the \n\ndefendants wrongfully failed to pay the debtor Lenny Perryʹs Produce, Inc., for \n\nproduce held in trust for the plaintiffs, in violation of the Perishable Agricultural \n\nCommodities Act, 7 U.S.C. § 499.  The United States District Court for the \n\nWestern District of New York (William M. Skretny, Judge) adopted a bankruptcy \n\n                                                            \n * The Clerk of the Court is directed to amend the official caption to conform to the \nlisting of the parties above. \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\njudgeʹs report and recommendation (Michael J. Kaplan, Bankruptcy Judge) that \n\nsummary judgment be granted to the plaintiffs in the proceeding but that the \n\ndefendants receive a pro rata share of assets of the trust established under the \n\nAct.  We agree with the bankruptcy judge and district court.  Because assets \n\nsubject to the Act are held in a ʺfloatingʺ trust for the benefit of unpaid produce \n\nsuppliers and never become part of a bankruptcy estate, when a purchaser of \n\nproduce files for bankruptcy under Chapter 7, a creditor covered by the Actʹs \n\nprovisions is entitled to a pro rata share of trust assets, but not to a complete \n\noffset of mutual debts between it and the bankrupt.  Here, the defendants elected \n\nnot to file a proof of claim after the district court issued a claims process order \n\nunder the Act.  Nevertheless, they preserved their PACA claims by providing \n\nstatutorily required notice to the debtor in connection with each pre‐bankruptcy \n\nsale of fresh produce; filed a proof of claim with the bankruptcy court before the \n\ndistrict court had issued the claims process order; and reasonably, although \n\nmistakenly, thought that they could vindicate their rights as creditors using a \n\nbankruptcy offset.  Under those circumstances, we conclude that the district \n\n\n\n\n 2 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt did not err in awarding the defendants a pro rata share of the PACA trust \n\nassets.   \n\n The district courtʹs decision is therefore: \n\n AFFIRMED.     \n\n David L. Rasmussen, Mallory Kass Smith, \n Davidson Fink LLP, Rochester, New York, \n for Defendants‐Appellants‐Cross‐Appellees. \n Christopher M. Corrigan, Martyn & \n Associates, Cleveland, Ohio, for Plaintiffs‐\n Appellees‐Cross‐Appellants.  \nSACK, Circuit Judge: \n\n The plaintiffs and the defendants are creditors of debtor Lenny Perryʹs \n\nProduce, Inc. (ʺLPPʺ).  Between 2005 and 2008, defendant Genecco Produce, Inc., \n\n(ʺGPIʺ) and debtor LPP regularly sold produce to one another.  Because the \n\ngoods were perishable agricultural commodities, these transactions were \n\ngoverned by the federal Perishable Agricultural Commodities Act, 7 U.S.C. § 499 \n\n(ʺPACAʺ).   \n\n Instead of paying each other after each transaction, GPI and LPP \n\naccumulated mutual debts intended to offset one another.  By the end of 2008, \n\n\n\n\n 3 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthose debts totaled $204,774.88, owed by GPI to LPP, and $263,061.92, owed by \n\nLPP to GPI — a net balance of $58,287.04 in GPIʹs favor. \n\n On January 27, 2009, LPP filed for bankruptcy protection under Chapter 7 \n\nof the United States Bankruptcy Code in the United States Bankruptcy Court for \n\nthe Western District of New York.  The plaintiffs, also unpaid sellers of \n\nperishable agricultural commodities to LPP, brought an adversary proceeding \n\nagainst the defendants in the bankruptcy court.  They alleged that the $204,774.88 \n\nowed by GPI to LPP constituted assets of a trust that arose for their benefit under \n\nthe terms of PACA (ʺPACA Trustʺ).  In response, the defendants asserted that \n\nfederal bankruptcy law, 11 U.S.C. § 553(a), and New York State law, N.Y. Debt. & \n\nCred. L. § 151, entitled them to a complete offset of any amount otherwise due to \n\nthe PACA Trust by amounts that had been due to the defendants from LPP.  \n\n On June 7, 2017, the United States District Court for the Western District of \n\nNew York (William M. Skretny, Judge) entered a judgment adopting the \n\nbankruptcy judgeʹs report and recommendation (Michael J. Kaplan, Bankruptcy \n\nJudge) recommending that summary judgment be granted to the plaintiffs.  The \n\ndistrict court concluded that the defendants were not entitled to a full offset of \n\n\n\n\n 4 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ntheir mutual unpaid debts, but only to a pro rata share of the PACA Trust along \n\nwith other unpaid LPP produce suppliers. \n\n The defendants argue that the district court erred because New York State \n\nlaw and federal bankruptcy law entitle them to a complete offset of any amounts \n\nthey owed LPP or the PACA Trust; in the alternative, they claim that questions of \n\nfact regarding the transfer of accounts receivable into the PACA Trust render the \n\ndistrict court’s grant of summary judgment improper.  \n\n We disagree.  Because PACA assets are held in trust for the benefit of \n\nunpaid produce suppliers generally and never become part of a bankruptcy \n\nestate, and because such PACA creditors enjoy priority over non‐PACA \n\ncreditors, the defendantsʹ offset defense under section 553 of the U.S. Bankruptcy \n\nCode and New York State law is unavailing.  The district court therefore \n\ncorrectly found that the plaintiffsʹ claims against the defendants are not subject to \n\nthe statutory offset sought by the defendants.   \n\n Meanwhile, the plaintiffs assert that the district court erred in permitting \n\nthe defendants to recover even a pro rata share of the PACA Trust.  The plaintiffs \n\ndo not dispute that the defendants, like the plaintiffs, are PACA creditors.  \n\nRather, they contend that the defendants are barred from recovery because they \n\n\n\n 5 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ndid not file a proof of claim pursuant to the district courtʹs claims procedure \n\norder (ʺClaims Procedure Orderʺ), which established deadlines for the plaintiffsʹ \n\ncounsel to issue written notice to potential PACA claimants and for prospective \n\nclaimants to file proofs of claim.   \n\n We conclude otherwise.  The defendants preserved their PACA claims by \n\nproviding statutorily required notice to the debtor in each invoice at issue and \n\nfiled a proof of claim with the bankruptcy court before the district court had \n\nissued the PACA Claims Procedure Order.  Based at least, in part, on ambiguities \n\nin that Order, they reasonably, although mistakenly, thought that they could \n\nvindicate their rights as PACA creditors using a bankruptcy offset and elected \n\nnot to file a PACA proof of claim.  Under these circumstances, as the district \n\ncourt correctly concluded, PACAʹs statutory purpose is best realized if the \n\ndefendants are permitted to collect pro rata shares of the PACA assets.  The \n\ndistrict court did not err in allowing the defendants to recover their pro rata \n\nshare. \n\n The judgment of the district court is therefore affirmed. \n\n\n\n\n 6 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n BACKGROUND \n\n General Factual Background \n\n At all relevant times, GPI, and LPP before it filed for bankruptcy, were \n\nmerchants of perishable agricultural commodities operating out of the Niagara \n\nFrontier Food Terminal in Buffalo, New York.  Between September 2005 and \n\nOctober 2008, LPP and GPI regularly sold produce to one another for resale to \n\ntheir respective customers.  In connection with each transaction, the seller—LPP \n\nor GPI—issued an invoice to the other with a notice of intent to preserve its \n\nPACA rights.1 \n\n Usually, neither GPI nor LPP would pay the other for the produce they \n\nsold to one another.  Instead, they maintained open, off‐setting accounts.  \n\nAlthough GPI and LPP tried ʺto make sure . . . GPI was not sending Lenny \n\nPerryʹs more produce than Lenny Perryʹs was sending GPI,ʺ their efforts were \n\nnot entirely successful.  Report and Recommendation at 4, PACA Trust Creditors \n\n                                                            \n  The invoices contained the following language, which the Act, at section 499e(c)(4), \n 1\n\nidentifies as sufficient to provide notice of intent to preserve PACA benefits:  ʺThe \nperishable agricultural commodities listed on this invoice are sold subject to the \nstatutory trust authorized by section 5(c) of the Perishable Agricultural Commodities \nAct, 1930 (7 U.S.C. 499e(c)).  The seller of these commodities retains a trust claim over \nthese commodities, all inventories of food or other products derived from these \ncommodities, and any receivables or proceeds from the sale of these commodities until \nfull payment is received.ʺ  See LPP Invoices, Appʹx 134‐395.  \n \n 7 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nof Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., No. 09‐1269‐MJK (W.D.N.Y. \n\nFeb. 12, 2014), ECF No. 126.  By January 2009, LPP owed GPI $263,061.92, and \n\nGPI owed LPP $204,774.88, resulting in a net balance of $58,287.04 in GPIʹs favor.    \n\n The plaintiffs2 are also merchants dealing in perishable agricultural \n\ncommodities.  Like GPI, they sold fresh produce to LPP.  Those sales for which \n\nthe plaintiffs were never paid are governed by PACA.  When LPP filed for \n\nbankruptcy, it owed the plaintiffs an estimated $292,417.39.   \n\n Procedural History \n\n On January 27, 2009, LPP and its principal, Leonard R. Perry, filed \n\nʺVoluntary Petitionsʺ for protection under Chapter 7 of the Bankruptcy Code in \n\nthe United States Bankruptcy Court for the Western District of New York.  On \n\nFebruary 17, 2009, GPI filed a proof of claim for $263,061.92.  On March 9, 2009, \n\nthe plaintiffs brought an adversary proceeding against LPP and Perry in that \n\n\n\n\n                                                            \n  The plaintiffs are Burch Equipment LLC, Jackson’s Farming Co., Pismo Oceano \n 2\n\nVegetable Exchange, Wings Landing Farm, Brooks Tropicals LLC, John B. Ordille Inc., \nand Weis‐Buy Farms Inc. \n 8 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt alleging PACA violations and a breach of fiduciary duty owed to the \n\nPACA beneficiaries.   \n\n The plaintiffs filed a motion to establish a PACA claims procedure, which \n\nthe bankruptcy court granted on August 7, 2009.  Under the Claims Procedure \n\nOrder, LPP was required, on or before August 12, 2009, to provide the plaintiffsʹ \n\ncounsel with names and addresses of all potential PACA claimants not already \n\nlisted in the bankruptcy petition.  Also by order of the court, the plaintiffsʹ \n\ncounsel had until August 17, 2009, to issue written notice of the Claims \n\nProcedure Order to potential PACA claimants, and prospective PACA claimants \n\nhad until August 31, 2009, to file complaints in intervention and PACA proofs of \n\nclaim.  Although the plaintiffs timely served GPI with notice of the Claims \n\nProcedure Order, GPI elected not to file a PACA claim but to pursue its offset \n\nclaim instead. \n\n On November 4, 2009, the PACA Trust beneficiaries instituted an \n\nadversary proceeding against the defendants alleging that between September \n\n2005 and October 2008, LPP delivered to GPI fresh produce worth a total of \n\n$204,774.88, for which they were not compensated.  The beneficiaries further \n\nalleged that LPPʹs accounts receivable from those sales constituted PACA Trust \n\n\n\n 9 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nassets.  On December 30, 2009, the defendants filed an answer asserting that they \n\nwere ʺentitled to a setoff in the amount of $263,061.92,ʺ owed to them by LPP, \n\nʺwhich is in excess of the $204,774.88 claimed to be due and owing by [the \n\nplaintiffs].ʺ  Appʹx 94. \n\n Motion to Strike  \n\n\n On January 15, 2010, the plaintiffs filed a motion to strike the defendantsʹ \n\nstatutory‐offset defense.  They argued that the defendantsʹ offset rights, if any, \n\ncould only be asserted against LPP, not the PACA Trust or its beneficiaries.  On \n\nAugust 14, 2012, the bankruptcy court recommended that the district court deny \n\nthe plaintiffsʹ motion because it would be ʺunfair and inequitableʺ to strike the \n\noffset defense unless the defendants are ʺpermitted a late ʹopt‐inʹ to share as [] \n\nbeneficiar[ies] of the Trust.ʺ3  PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. \n\nGenecco Produce, Inc. (In re Lenny Perryʹs Produce), Bankr. No. 09‐10297 K, 2012 \n\nWL 7767580, at *4, 2012 Bankr. LEXIS 5440, at *14 (Bankr. W.D.N.Y. Aug. 14, \n\n2012).  On November 12, 2012, the district court adopted the bankruptcy courtʹs \n\n\n\n                                                            \n  Although the district court has jurisdiction over the adversary proceeding between \n 3\n\nthe plaintiffs and the defendants, it entered a Special Order of Reference to the \nbankruptcy court.  Pursuant to that Special Order, the bankruptcy court presided over \neach of the motions filed in this matter and issued reports and recommendations to the \ndistrict court.  \n 10 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nrecommendation.  John B. Ordille, Inc. v. Lenny Perryʹs Produce, Inc., No. 12‐MC‐\n\n54S, 2012 WL 5499652, 2012 U.S. Dist. LEXIS 161648 (W.D.N.Y. Nov. 12, 2012).    \n\n\n Motion for Summary Judgment \n\n\n On May 3, 2013, the plaintiffs moved for summary judgment, renewing \n\ntheir argument that GPI could only bring an offset claim against LPP, not against \n\nthe plaintiffs.  On February 12, 2014, the bankruptcy court recommended that the \n\ndistrict court grant the plaintiffsʹ motion.  Report and Recommendation, PACA \n\nTrust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., No. 09‐1269‐\n\nMJK (W.D.N.Y. Feb. 12, 2014), ECF No. 126.  It rejected the defendantsʹ argument \n\nthat a long‐term bartering arrangement had extinguished GPIʹs debts to LPP.  \n\nThe bankruptcy court noted that GPI had failed to produce any tax documents or \n\nother evidence to substantiate its claim of a bartering arrangement with LPP.  To \n\nthe contrary, it concluded, ʺthe parties were simply selling commodities to each \n\nother . . . , maintaining open, off‐setting accounts that remained so (meaning \n\nnever materially reconciled by off‐set) right up until the [d]ebtor went out of \n\nbusiness.ʺ  Id.  For that reason, it recommended that the district court enter \n\njudgment in favor of the plaintiffs in the amount that GPI owed to LPP, less GPIʹs \n\npro rata share of the PACA Trust.     \n\n\n 11 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n On September 4, 2014, the district court remanded the matter to the \n\nbankruptcy court for further proceedings.  PACA Trust Creditors of Lenny Perryʹs, \n\nInc. v. Genecco Produce, Inc., No. 14‐MC‐036S, 2014 WL 4385436, at *1, 2014 U.S. \n\nDist. LEXIS 123965, at *3 (W.D.N.Y. Sept. 4, 2014).  It explained that because \n\nʺbartering and setoff are different concepts,ʺ the absence of a bartering \n\nrelationship does not necessarily defeat an offset defense.  Id. at *3‐4; 2014 U.S. \n\nDist. LEXIS 123965, at *7.  The district court directed the bankruptcy court, on \n\nremand, to consider whether (i) GPI’s debt to LPP and LPPʹs debt to GPI \n\nconstitute ʺmutual debt[s]ʺ for purposes of section 553 of the Bankruptcy Code, \n\nand (ii) whether any funds due from GPI to LPP are PACA Trust assets not \n\nsubject to the defendantsʹ offset claim.  Id. at *2‐3; 2014 U.S. Dist. LEXIS 123965, at \n\n*7, 9‐10.   \n\n\n On February 23, 2015, the bankruptcy court issued a ʺClarified Report and \n\nRecommendation,ʺ which explained in greater detail—but did not materially \n\nalter—its February 12, 2014 recommendation.  PACA Trust Creditors of Lenny \n\nPerryʹs Produce, Inc. v. Genecco Produce, Inc. (In re Lenny Perryʹs Produce, Inc.), \n\nNo. 09‐10297 K, 2015 Bankr. LEXIS 2713 (Bankr. W.D.N.Y. Feb. 23, 2015).  On \n\nAugust 12, 2015, the district court again remanded the matter to the bankruptcy \n\n\n 12 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt, explaining that ʺclarification of the issues raised in the partiesʹ submissions \n\nas well as this Courtʹs prior order is warranted.ʺ  PACA Trust Creditors of Lenny \n\nPerryʹs Produce v. Genecco Produce, Inc., No. 15‐MC‐028S, 2015 WL 4761627, at *6, \n\n2015 U.S. Dist. LEXIS 105908, at *15 (W.D.N.Y. Aug. 12, 2015). \n\n\n The bankruptcy court issued what turned out to be its final report and \n\nrecommendation on December 28, 2015.  PACA Trust Creditors of Lenny Perryʹs \n\nProduce, Inc. v. Genecco Produce, Inc. (In re Lenny Perryʹs Produce, Inc.), No. 09‐\n\n10297 K, 2015 WL 9581383, 2015 Bankr. LEXIS 4371 (Bankr. W.D.N.Y. Dec. 28, \n\n2015).  The court concluded that ʺthe Trust’s rights are not now, and never were, \n\nsubject to the limitations that [LPP] suffered as to [GPI], or the defenses that \n\n[GPI] had against [LPP].ʺ  Id. at *2; 2015 Bankr. LEXIS 4371, at *4‐5.  In the \n\nbankruptcy courtʹs view, ʺevery item of perishable commodities [LPP] ever \n\nhandled was held by it in trust, as were any proceeds realized from those items,ʺ \n\nso that ʺeverything that [LPP] received from [GPI] or was entitled to receive from \n\n[GPI] on account of perishable commodities delivered to [GPI] was subject to the \n\nstatutory PACA Trust in favor of growers, cooperatives, etc.[,] which were owed \n\nmoney for those commodities.ʺ  Id.; 2015 Bankr. LEXIS 4371, at *5.  The PACA \n\n\n\n\n 13 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nTrust existed ʺfrom the moment that [LPP] bought or sold commodities subject to \n\nPACA.ʺ  Id.; 2015 Bankr. LEXIS 4371, at *5.   \n\n\n The bankruptcy court further decided that LPP and GPIʹs method of doing \n\nbusiness by maintaining mutual debts ʺwas not consistent with PACA,ʺ which \n\nrequires timely payments ʺso that all providers of perishable agricultural \n\ncommodities to [LPP] had a chance to receive cash payments from [GPI] for what \n\nthey provided.ʺ  Id. at *4; 2015 Bankr. LEXIS 4371, at *11‐12.  It concluded that \n\nʺequity requires treatment that PACA would seem to require,ʺ id.; 2015 Bankr. \n\nLEXIS 4371, at *12:  a judgment against GPI equal to ʺthe difference between what \n\n[GPI] owed [LPP] on the date of the Chapter 7 petition (and therefore owes to the \n\nPACA Trust) and the amount that [GPI] would receive as a PACA Trust \n\nbeneficiary,ʺ id. at *6; 2015 Bankr. LEXIS 4371, at *19 (emphasis in original).     \n\n\n On June 7, 2017, the district court adopted the bankruptcy courtʹs \n\nrecommendation in full.  PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. \n\nGenecco Produce Inc., No. 16‐MC‐4S, 2017 WL 2462035, 2017 U.S. Dist. LEXIS \n\n87488 (W.D.N.Y. June 7, 2017).  The district court rejected the defendantsʹ \n\nargument that they are entitled to a complete offset.  It observed that offsets only \n\napply to mutual debts, and the debts between GPI and LPP are ʺmutual only to \n\n\n 14 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthe extent [d]efendants are co‐beneficiaries to the PACA Trust.  And, to the \n\nextent that they are co‐beneficiaries, [p]laintiffs and [d]efendants owe one \n\nanother a fiduciary duty to take no more than their [pro rata] share of trust \n\nassets.ʺ  Id. at *2; 2017 U.S. Dist. LEXIS 87488, at *4.  The district court also \n\nrejected the plaintiffsʹ argument that the defendantsʹ failure to file a PACA claim \n\nprecludes them from recovering a pro rata share of the PACA Trust.  Instead, the \n\ndistrict court decided that allowing the defendants limited recovery as PACA \n\ncreditors ʺbest furthers the policies of PACA.ʺ  Id. at *1; 2017 U.S. Dist. LEXIS \n\n87488, at *4.  The district court concluded that although the defendants are not \n\nentitled to an offset under bankruptcy law, they may recover a pro rata share of \n\nthe PACA Trust.  Id.; 2017 U.S. Dist. LEXIS 87488, at *4‐5.   \n\n\n DISCUSSION \n\n There are two issues raised on appeal:  First, whether the district court \n\nerred in concluding that LPPʹs accounts receivable constitute PACA Trust assets \n\nand that the defendants are therefore not entitled to a statutory offset of their \n\ndebts to LPP against LPPʹs debts to them; and second, whether the district court \n\nerred in allowing the defendants to recover a pro rata share of the PACA Trust.  \n\nThe defendants argue that the Bankruptcy Code, 11 U.S. Code § 553, which \n\n\n 15 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ngoverns ʺSetoff,ʺ entitles them to a complete offset of any amount otherwise due \n\nto the PACA Trust.  The plaintiffs respond that the defendants may not recover \n\neven a pro rata share of the PACA Trust because they elected not to participate in \n\nthe PACA claims procedure in the bankruptcy court.  For the reasons discussed \n\nbelow, we affirm the district courtʹs judgment in its entirety. \n\n\n I. Standard of Review \n\n\n ʺWe review a grant of summary judgment de novo, examining the \n\nevidence in the light most favorable to, and drawing all inferences in favor of, the \n\nnon‐movant.ʺ  Blackman v. N.Y. City Transit Auth., 491 F.3d 95, 98 (2d Cir. 2007) \n\n(per curiam) (quoting Sheppard v. Beerman, 317 F.3d 351, 354 (2d Cir. 2003)).  \n\nSummary judgment is appropriate only if ʺthe movant shows that there is no \n\ngenuine dispute as to any material fact and the movant is entitled to judgment as \n\na matter of law.ʺ  Fed. R. Civ. P. 56(a).  A genuine dispute exists if ʺthe evidence \n\nis such that a reasonable jury could return a verdict for the nonmoving party.ʺ  \n\nFireman’s Fund Ins. Co. v. Great Am. Ins. Co. of N.Y., 822 F.3d 620, 631 n.12 (2d Cir. \n\n2016) (internal quotation marks omitted).  However, ʺa party may not rely on \n\nmere speculation or conjecture as to the true nature of the facts to overcome a \n\nmotion for summary judgment.ʺ  Fletcher v. Atex, Inc., 68 F.3d 1451, 1456 (2d Cir. \n\n\n 16 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n1995) (internal quotation marks omitted).  The party opposing summary \n\njudgment ʺmust do more than simply show that there is some metaphysical \n\ndoubt as to the material facts.ʺ  Matsushita Elec. Indus. Co. v. Zenith Radio Corp., \n\n475 U.S. 574, 586 (1986). \n\n\n When a district court interprets its own order, we apply an abuse‐of‐\n\ndiscretion standard.  Garcia v. Yonkers Sch. Dist., 561 F.3d 97, 103 (2d Cir. 2009); \n\nsee also United States v. Spallone, 399 F.3d 415, 423 (2d Cir. 2005) (ʺWhen an issuing \n\njudge interprets his own orders, we accord substantial deference to the \n\ndraftsman, and we will not reverse the judgeʹs construction of an ambiguity in \n\nhis own words except for abuse of discretion.ʺ). \n\n\n II. Statutory Offset  \n\n The defendants advance two arguments challenging the district courtʹs \n\nconclusion that they are not entitled to a complete offset of the debts covered by \n\nPACA from them to LLP against those from LLP to the defendants under New \n\nYork State law and federal bankruptcy law.  First, they argue that LPPʹs relevant \n\naccounts receivable were transferred to the PACA Trust, if at all, subject to the \n\ndefendantsʹ offset rights.  Second, they argue that factual disputes exist as to \n\n\n\n\n 17 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nwhether LPPʹs accounts receivable constituted PACA Trust assets.  We reject \n\nboth arguments. \n\n\n 1. Availability of Offset Defense Against the Plaintiffs’ PACA Claim \n\n The defendants claim that ʺ[n]o authority exists,ʺ Defendantsʹ Br. 14, that \n\nwould require the defendants to ʺpay [their] debts in full to the bankrupt[], while \n\nallowing the [defendants] to recover only a percentage of the debts owed to \n\n[them] by the bankrupt[, LPP],ʺ id. at 13 (internal quotation marks omitted).  Not \n\nso.  The statutory language of PACA and section 553 of the U.S. Bankruptcy \n\nCode, as well as this Courtʹs prior decisions, require precisely that.   \n\n\n The PACA trust provision, which Congress enacted in order ʺto make the \n\nsellersʹ interests in the commodities and sales proceeds superior to those of the \n\nbuyersʹ creditors,ʺ Am. Banana Co. v. Rep. Natʹl Bank of N.Y., 362 F.3d 33, 37 (2d \n\nCir. 2004), states in relevant part:  \n\n Perishable agricultural commodities received by a \n commission merchant, dealer, or broker in all \n transactions . . . and any receivables or proceeds from \n the sale of such commodities or products, shall be held \n by such commission merchant, dealer, or broker in trust \n for the benefit of all unpaid suppliers or sellers of such \n commodities or agents involved in the transaction, until \n full payment of the sums owing in connection with such \n transactions has been received by such unpaid \n suppliers, sellers, or agents.  \n 18 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n7 U.S.C. § 499e(c)(2).  Under regulations adopted by the U.S. Department of \n\nAgriculture (ʺDOAʺ), PACA assets ʺare to be preserved as a nonsegregated \n\nʹfloatingʹ trust.ʺ  7 C.F.R. § 46.46(b).  PACA and related DOA regulations provide \n\nproduce sellers with ʺa self‐help tool enabling them to protect themselves against \n\nthe abnormal risk of losses resulting from slow‐pay and no‐pay practices by \n\nbuyers or receivers of fruits and vegetables.ʺ  Coosemans Specialties, Inc. v. \n\nGargiulo, 485 F.3d 701, 705 (2d Cir. 2007) (citations omitted). \n\n\n We have explained that ʺ[o]rdinary principles of trust law apply to the \n\ntrusts created by [PACA] . . . so that the Produce Debtor holds the legal title to \n\nthe Produce and its derivatives or proceeds but the seller retains an equitable \n\ninterest in the trust property pending payment[.]ʺ  Tom Lange Co. v. Kornblum & \n\nCo. (In re Kornblum & Co.), 81 F.3d 280, 284 (2d Cir. 1996) (citations omitted).  \n\nBecause PACA creditors hold an equitable interest in the PACA trust pending \n\npayment, ʺthe Bankruptcy Code excludes PACA trust assets from the bankruptcy \n\nestate.ʺ  Id. (citing, inter alia, United States v. Whiting Pools, Inc., 462 U.S. 198, 205 \n\nn.10 (1983) (explaining that the Bankruptcy Code ʺplainly exclude[s from the \n\nbankruptcy estate] property of others held by the debtor in trust at the time of \n\nthe filing of the [bankruptcy] petitionʺ)).  Consequently, PACA ʺgives unpaid \n\n\n 19 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n[produce] suppliers . . . priority over secured lenders . . . to PACA trust assets.ʺ  \n\nAlbee Tomato, Inc. v. A.B. Shalom Produce Corp., 155 F.3d 612, 615 (2d Cir. 1998). \n\n\n The defendantsʹ reliance on bankruptcy law to defend against PACA \n\nclaims is misplaced.  To the extent the disputed assets represent PACA Trust \n\nassets, they are held outside the bankruptcy estate, and their disposition is, \n\ntherefore, governed by trust law rather than bankruptcy law.  See Kornblum, 81 \n\nF.3d at 284.  To permit a bankruptcy offset against PACA Trust assets would be \n\ninconsistent with Congressʹs intent in amending PACA in 1984 to ʺbroaden the \n\nprotections afforded to produce suppliersʺ who had previously ʺreceive[d] little \n\nprotection in any suit for recovery of damages where a buyer ha[d] failed to \n\nmake payment as required by the contract.ʺ  Id. at 283 (citation omitted).  Because \n\nPACA provides unpaid produce sellers with priority over other creditors and \n\nestablishes that the disposition of PACA assets is governed by trust law, see id. at \n\n284, we conclude that the district court did not err in deciding that the \n\ndefendants are not entitled to the offset they seek under New York and federal‐\n\nbankruptcy law.4 \n\n\n\n                                                            \n This conclusion is buttressed by the language in section 553 of the U.S. Bankruptcy \n4\n\nCode, which makes offsets available only for ʺmutualʺ debts.  11 U.S.C. § 553(a).  \n \n 20 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n 2. No Genuine Dispute of Material Fact \n\n The defendants next argue that material factual disputes exist as to \n\nwhether LPPʹs accounts receivable for the sale of produce to the defendants, \n\ntotaling $204,774.88, constitute PACA Trust assets.  The defendants suggest that \n\nbecause they sought an offset before the district court issued its Claims \n\nProcedure Order, LPPʹs receivables never became PACA Trust assets, or, if they \n\ndid, they were transferred subject to the defendantsʹ offset rights.   \n\n\n The defendantsʹ argument misses the mark.  We have explained that a \n\nPACA trust ʺis automatically established each time a broker or merchant \n\npurchases perishable commodities.ʺ  D.M Rothman & Co., Inc. v. Korea Commercial \n\nBank of N.Y., 411 F.3d 90, 96 (2d Cir. 2005); accord C&E Enters., Inc. v. Milton \n\n\n\n                                                            \nMutuality exists where debts ʺare due to and from the same persons in the same \ncapacity.ʺ  Westinghouse Credit Corp. v. D’Urso, 278 F.3d 138, 149 (2d Cir. 2002) (citations \nomitted).  The debts here are not mutual because the defendants and LPP appear in \ndifferent capacities:  The defendants assert their claim to $263,061.92 in their capacity as \ncreditors in LPP’s bankruptcy proceeding; LPP, by contrast, does not—and cannot—\nassert a claim for $204,774.88 in its capacity as a creditor, but instead pursues those \nfunds solely on behalf of unpaid suppliers.  See 7 U.S.C. § 499e(c)(2) (“Perishable \nagricultural commodities received by a . . . merchant, . . . and any receivables or \nproceeds from the sale of such commodities . . . , shall be held . . . in trust for the benefit \nof all unpaid suppliers . . . until full payment of the sums owing . . . has been received \nby such unpaid suppliers[.]”); cf. DʹUrso, 278 F.3d at 149 (ʺ[O]bligations lack mutuality \nwhere one party is a trust beneficiary asserting his or her rights against a trustee, and \nthe other is a creditor exercising his or her contractual rights[.]ʺ). \n\n 21 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nPoulos, Inc. (In re Milton Poulos, Inc.), 947 F.2d 1351, 1352 (9th Cir. 1991) (ʺThe \n\n[PACA] trust automatically arises in favor of a produce seller upon delivery of \n\nproduce[.]ʺ); Patterson Frozen Foods, Inc. v. Crown Foods Int’l, Inc., 307 F.3d 666, 669 \n\n(7th Cir. 2002) (ʺTh[e PACA] floating trust is automatically created when the \n\ndealer accepts the goods[.]ʺ).  Any factual dispute as to whether the defendants \n\nasserted their offset claim before the district court issued the Claims Procedure \n\nOrder is immaterial:  Even if the defendantsʹ offset claim predates the Claims \n\nProcedure Order, the PACA Trust arose immediately upon the sale of produce \n\nfrom the plaintiffs to LPP—long before the defendants asserted their offset \n\nclaim—such that the accounts receivable associated with those transactions \n\nwould not be subject to that defense. \n\n\n The defendants further argue that the plaintiffs have failed to establish that \n\nthe accounts receivable were PACA Trust assets.  This argument, too, fails.  It is \n\nthe defendants who bear the burden of demonstrating that disputed assets do not \n\nconstitute PACA trust assets.  Kornblum, 81 F.3d at 287.  They have not met that \n\nburden.  Nothing in the record suggests that LPP entered into a factoring \n\nagreement with GPI, that LPP and GPI engaged in a bartering relationship, or \n\nthat LPP and GPI paid down their mutual debts.  Instead, the record establishes \n\n\n 22 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthat LPP and GPIʹs debts to each other remained outstanding when GPI filed for \n\nbankruptcy.  \n\n\n The defendants thus have failed to identify any genuine dispute of \n\nmaterial fact as to whether LPPʹs accounts receivable constitute PACA Trust \n\nassets. \n\n\n III. Pro Rata Share   \n\n  Finally, we address the district courtʹs decision to award the defendants a \n\npro rata share of the PACA Trust, in light of the defendantsʹ loss on their set‐off \n\nclaim and failure to file a proof of claim after the district court issued the Claims \n\nProcedure Order.  The bankruptcy court recommended that the district court \n\nallow the defendants to recover a pro rata share, in part because the Claims \n\nProcedure Order did not specify which ʺreceivablesʺ were ʺtrust assetsʺ; it was \n\ntherefore ʺnot unreasonable for [GPI] to have relied upon its belief that ordinary \n\nsetoff rights as to ʹreceivablesʹ would apply.ʺ  In re Lenny Perryʹs Produce, 2012 \n\nWL 7767580, at *4, 2012 Bankr. LEXIS 5440, at *14‐15, adopted, John B. Ordille, Inc. \n\nv. Lenny Perryʹs Produce, Inc., No. 12‐MC‐54S, 2012 WL 5499652, 2012 U.S. Dist. \n\nLEXIS 161648 (W.D.N.Y. Nov. 12, 2012).   \n\n\n\n\n 23 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n The district court agreed:  It noted that the ʺ[d]efendants raised their \n\ndefense of offset even before the PACA Claims Procedure was established,ʺ and \n\nconcluded that they ʺhad a good faith basis for pursuing their claims through a \n\nbankruptcy offset rather than through the PACA claims process.ʺ  PACA Trust \n\nCreditors of Lenny Perryʹs Produce, Inc., 2017 WL 2462035, at *1, 2017 U.S. Dist. \n\nLEXIS 87488, at *4. \n\n\n The district court did not err in allowing the defendants to recover a pro \n\nrata share of the PACA Trust.  It is undisputed that the defendants complied \n\nwith all statutory requirements to preserve their PACA claims:  In each invoice \n\nthat GPI sent to LPP, it provided written notice of intent to preserve its PACA \n\nrights.  It is also undisputed that the defendants filed a proof of claim in \n\nbankruptcy court before the Claims Procedure Order was issued, for an offset in \n\nthe amount of $263,061.92.  Having filed an offset claim, the defendants \n\nreasonably thought that their debt to LPP was not a ʺreceivableʺ under the \n\nClaims Procedure Order and that they were not required to submit a PACA \n\nproof of claim.  The bankruptcy court and district court properly concluded that, \n\nin light of ambiguities in the Claims Procedure Order and the novelty of the legal \n\n\n\n\n 24 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nissues presented, the defendants had a good‐faith basis to pursue their claims \n\nthrough a bankruptcy offset in lieu of a PACA claim. \n\n\n Moreover, the statute states, in relevant part, that perishable goods and \n\nany receivables from their sale are held in trust ʺfor the benefit of all unpaid \n\nsuppliers or sellers of such commodities or agents involved in the transaction, \n\nuntil full payment of the sums owing in connection with such transactions has \n\nbeen received by such unpaid suppliers, sellers, or agents.ʺ  7 U.S.C. § 499e(c)(2) \n\n(emphasis added).  The defendants are unpaid suppliers of produce.  Denying \n\nthem a pro rata share of the PACA Trust, even though they preserved their \n\nPACA claims and filed a proof of claim in bankruptcy court, would be, we think, \n\ninconsistent with the statutory text and the district courtʹs interpretation of its \n\nown Claims Procedure Order.  We therefore conclude that the district court did \n\nnot err in permitting the defendants to recover a pro rata share of the PACA \n\nTrust. \n\n\n CONCLUSION \n We have considered the partiesʹ other arguments on appeal and conclude \n\nthat they are without merit.  For the foregoing reasons, we AFFIRM the \n\njudgment of the district court. \n\n\n\n 25", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357133/", "author_raw": "SACK, Circuit Judge:"}]}
SACK
RAGGI
CHIN
1
{"SACK": ", Circuit", "RAGGI": ", Circuit", "CHIN": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579880/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: The PACA Trust Creditors v. Genecco Produce Inc.\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17‐1949‐(L) \nThe PACA Trust Creditors v. Genecco Produce Inc. \n \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n August Term, 2018 \n (Submitted: September 5, 2018  Decided: January 9, 2019) \n Docket Nos. 17‐1949‐cv, 17‐2051‐cv \n\n  \n  \n THE PACA TRUST CREDITORS OF LENNY PERRYʹS PRODUCE, INC., \n Plaintiffs‐Appellees‐Cross‐Appellants, \n\n v. \n\n GENECCO PRODUCE INC., DAVID GENECCO, \n Defendants‐Appellants‐Cross‐Appellees.* \n  \n  \nBefore:  SACK, RAGGI, AND CHIN, Circuit Judges. \n\n The plaintiffs brought an adversary proceeding in the United States \n\nBankruptcy Court for the Western District of New York alleging that the \n\ndefendants wrongfully failed to pay the debtor Lenny Perryʹs Produce, Inc., for \n\nproduce held in trust for the plaintiffs, in violation of the Perishable Agricultural \n\nCommodities Act, 7 U.S.C. § 499.  The United States District Court for the \n\nWestern District of New York (William M. Skretny, Judge) adopted a bankruptcy \n\n                                                            \n * The Clerk of the Court is directed to amend the official caption to conform to the \nlisting of the parties above. \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\njudgeʹs report and recommendation (Michael J. Kaplan, Bankruptcy Judge) that \n\nsummary judgment be granted to the plaintiffs in the proceeding but that the \n\ndefendants receive a pro rata share of assets of the trust established under the \n\nAct.  We agree with the bankruptcy judge and district court.  Because assets \n\nsubject to the Act are held in a ʺfloatingʺ trust for the benefit of unpaid produce \n\nsuppliers and never become part of a bankruptcy estate, when a purchaser of \n\nproduce files for bankruptcy under Chapter 7, a creditor covered by the Actʹs \n\nprovisions is entitled to a pro rata share of trust assets, but not to a complete \n\noffset of mutual debts between it and the bankrupt.  Here, the defendants elected \n\nnot to file a proof of claim after the district court issued a claims process order \n\nunder the Act.  Nevertheless, they preserved their PACA claims by providing \n\nstatutorily required notice to the debtor in connection with each pre‐bankruptcy \n\nsale of fresh produce; filed a proof of claim with the bankruptcy court before the \n\ndistrict court had issued the claims process order; and reasonably, although \n\nmistakenly, thought that they could vindicate their rights as creditors using a \n\nbankruptcy offset.  Under those circumstances, we conclude that the district \n\n\n\n\n 2 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt did not err in awarding the defendants a pro rata share of the PACA trust \n\nassets.   \n\n The district courtʹs decision is therefore: \n\n AFFIRMED.     \n\n David L. Rasmussen, Mallory Kass Smith, \n Davidson Fink LLP, Rochester, New York, \n for Defendants‐Appellants‐Cross‐Appellees. \n Christopher M. Corrigan, Martyn & \n Associates, Cleveland, Ohio, for Plaintiffs‐\n Appellees‐Cross‐Appellants.  \nSACK, Circuit Judge: \n\n The plaintiffs and the defendants are creditors of debtor Lenny Perryʹs \n\nProduce, Inc. (ʺLPPʺ).  Between 2005 and 2008, defendant Genecco Produce, Inc., \n\n(ʺGPIʺ) and debtor LPP regularly sold produce to one another.  Because the \n\ngoods were perishable agricultural commodities, these transactions were \n\ngoverned by the federal Perishable Agricultural Commodities Act, 7 U.S.C. § 499 \n\n(ʺPACAʺ).   \n\n Instead of paying each other after each transaction, GPI and LPP \n\naccumulated mutual debts intended to offset one another.  By the end of 2008, \n\n\n\n\n 3 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthose debts totaled $204,774.88, owed by GPI to LPP, and $263,061.92, owed by \n\nLPP to GPI — a net balance of $58,287.04 in GPIʹs favor. \n\n On January 27, 2009, LPP filed for bankruptcy protection under Chapter 7 \n\nof the United States Bankruptcy Code in the United States Bankruptcy Court for \n\nthe Western District of New York.  The plaintiffs, also unpaid sellers of \n\nperishable agricultural commodities to LPP, brought an adversary proceeding \n\nagainst the defendants in the bankruptcy court.  They alleged that the $204,774.88 \n\nowed by GPI to LPP constituted assets of a trust that arose for their benefit under \n\nthe terms of PACA (ʺPACA Trustʺ).  In response, the defendants asserted that \n\nfederal bankruptcy law, 11 U.S.C. § 553(a), and New York State law, N.Y. Debt. & \n\nCred. L. § 151, entitled them to a complete offset of any amount otherwise due to \n\nthe PACA Trust by amounts that had been due to the defendants from LPP.  \n\n On June 7, 2017, the United States District Court for the Western District of \n\nNew York (William M. Skretny, Judge) entered a judgment adopting the \n\nbankruptcy judgeʹs report and recommendation (Michael J. Kaplan, Bankruptcy \n\nJudge) recommending that summary judgment be granted to the plaintiffs.  The \n\ndistrict court concluded that the defendants were not entitled to a full offset of \n\n\n\n\n 4 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ntheir mutual unpaid debts, but only to a pro rata share of the PACA Trust along \n\nwith other unpaid LPP produce suppliers. \n\n The defendants argue that the district court erred because New York State \n\nlaw and federal bankruptcy law entitle them to a complete offset of any amounts \n\nthey owed LPP or the PACA Trust; in the alternative, they claim that questions of \n\nfact regarding the transfer of accounts receivable into the PACA Trust render the \n\ndistrict court’s grant of summary judgment improper.  \n\n We disagree.  Because PACA assets are held in trust for the benefit of \n\nunpaid produce suppliers generally and never become part of a bankruptcy \n\nestate, and because such PACA creditors enjoy priority over non‐PACA \n\ncreditors, the defendantsʹ offset defense under section 553 of the U.S. Bankruptcy \n\nCode and New York State law is unavailing.  The district court therefore \n\ncorrectly found that the plaintiffsʹ claims against the defendants are not subject to \n\nthe statutory offset sought by the defendants.   \n\n Meanwhile, the plaintiffs assert that the district court erred in permitting \n\nthe defendants to recover even a pro rata share of the PACA Trust.  The plaintiffs \n\ndo not dispute that the defendants, like the plaintiffs, are PACA creditors.  \n\nRather, they contend that the defendants are barred from recovery because they \n\n\n\n 5 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ndid not file a proof of claim pursuant to the district courtʹs claims procedure \n\norder (ʺClaims Procedure Orderʺ), which established deadlines for the plaintiffsʹ \n\ncounsel to issue written notice to potential PACA claimants and for prospective \n\nclaimants to file proofs of claim.   \n\n We conclude otherwise.  The defendants preserved their PACA claims by \n\nproviding statutorily required notice to the debtor in each invoice at issue and \n\nfiled a proof of claim with the bankruptcy court before the district court had \n\nissued the PACA Claims Procedure Order.  Based at least, in part, on ambiguities \n\nin that Order, they reasonably, although mistakenly, thought that they could \n\nvindicate their rights as PACA creditors using a bankruptcy offset and elected \n\nnot to file a PACA proof of claim.  Under these circumstances, as the district \n\ncourt correctly concluded, PACAʹs statutory purpose is best realized if the \n\ndefendants are permitted to collect pro rata shares of the PACA assets.  The \n\ndistrict court did not err in allowing the defendants to recover their pro rata \n\nshare. \n\n The judgment of the district court is therefore affirmed. \n\n\n\n\n 6 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n BACKGROUND \n\n General Factual Background \n\n At all relevant times, GPI, and LPP before it filed for bankruptcy, were \n\nmerchants of perishable agricultural commodities operating out of the Niagara \n\nFrontier Food Terminal in Buffalo, New York.  Between September 2005 and \n\nOctober 2008, LPP and GPI regularly sold produce to one another for resale to \n\ntheir respective customers.  In connection with each transaction, the seller—LPP \n\nor GPI—issued an invoice to the other with a notice of intent to preserve its \n\nPACA rights.1 \n\n Usually, neither GPI nor LPP would pay the other for the produce they \n\nsold to one another.  Instead, they maintained open, off‐setting accounts.  \n\nAlthough GPI and LPP tried ʺto make sure . . . GPI was not sending Lenny \n\nPerryʹs more produce than Lenny Perryʹs was sending GPI,ʺ their efforts were \n\nnot entirely successful.  Report and Recommendation at 4, PACA Trust Creditors \n\n                                                            \n  The invoices contained the following language, which the Act, at section 499e(c)(4), \n 1\n\nidentifies as sufficient to provide notice of intent to preserve PACA benefits:  ʺThe \nperishable agricultural commodities listed on this invoice are sold subject to the \nstatutory trust authorized by section 5(c) of the Perishable Agricultural Commodities \nAct, 1930 (7 U.S.C. 499e(c)).  The seller of these commodities retains a trust claim over \nthese commodities, all inventories of food or other products derived from these \ncommodities, and any receivables or proceeds from the sale of these commodities until \nfull payment is received.ʺ  See LPP Invoices, Appʹx 134‐395.  \n \n 7 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nof Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., No. 09‐1269‐MJK (W.D.N.Y. \n\nFeb. 12, 2014), ECF No. 126.  By January 2009, LPP owed GPI $263,061.92, and \n\nGPI owed LPP $204,774.88, resulting in a net balance of $58,287.04 in GPIʹs favor.    \n\n The plaintiffs2 are also merchants dealing in perishable agricultural \n\ncommodities.  Like GPI, they sold fresh produce to LPP.  Those sales for which \n\nthe plaintiffs were never paid are governed by PACA.  When LPP filed for \n\nbankruptcy, it owed the plaintiffs an estimated $292,417.39.   \n\n Procedural History \n\n On January 27, 2009, LPP and its principal, Leonard R. Perry, filed \n\nʺVoluntary Petitionsʺ for protection under Chapter 7 of the Bankruptcy Code in \n\nthe United States Bankruptcy Court for the Western District of New York.  On \n\nFebruary 17, 2009, GPI filed a proof of claim for $263,061.92.  On March 9, 2009, \n\nthe plaintiffs brought an adversary proceeding against LPP and Perry in that \n\n\n\n\n                                                            \n  The plaintiffs are Burch Equipment LLC, Jackson’s Farming Co., Pismo Oceano \n 2\n\nVegetable Exchange, Wings Landing Farm, Brooks Tropicals LLC, John B. Ordille Inc., \nand Weis‐Buy Farms Inc. \n 8 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt alleging PACA violations and a breach of fiduciary duty owed to the \n\nPACA beneficiaries.   \n\n The plaintiffs filed a motion to establish a PACA claims procedure, which \n\nthe bankruptcy court granted on August 7, 2009.  Under the Claims Procedure \n\nOrder, LPP was required, on or before August 12, 2009, to provide the plaintiffsʹ \n\ncounsel with names and addresses of all potential PACA claimants not already \n\nlisted in the bankruptcy petition.  Also by order of the court, the plaintiffsʹ \n\ncounsel had until August 17, 2009, to issue written notice of the Claims \n\nProcedure Order to potential PACA claimants, and prospective PACA claimants \n\nhad until August 31, 2009, to file complaints in intervention and PACA proofs of \n\nclaim.  Although the plaintiffs timely served GPI with notice of the Claims \n\nProcedure Order, GPI elected not to file a PACA claim but to pursue its offset \n\nclaim instead. \n\n On November 4, 2009, the PACA Trust beneficiaries instituted an \n\nadversary proceeding against the defendants alleging that between September \n\n2005 and October 2008, LPP delivered to GPI fresh produce worth a total of \n\n$204,774.88, for which they were not compensated.  The beneficiaries further \n\nalleged that LPPʹs accounts receivable from those sales constituted PACA Trust \n\n\n\n 9 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nassets.  On December 30, 2009, the defendants filed an answer asserting that they \n\nwere ʺentitled to a setoff in the amount of $263,061.92,ʺ owed to them by LPP, \n\nʺwhich is in excess of the $204,774.88 claimed to be due and owing by [the \n\nplaintiffs].ʺ  Appʹx 94. \n\n Motion to Strike  \n\n\n On January 15, 2010, the plaintiffs filed a motion to strike the defendantsʹ \n\nstatutory‐offset defense.  They argued that the defendantsʹ offset rights, if any, \n\ncould only be asserted against LPP, not the PACA Trust or its beneficiaries.  On \n\nAugust 14, 2012, the bankruptcy court recommended that the district court deny \n\nthe plaintiffsʹ motion because it would be ʺunfair and inequitableʺ to strike the \n\noffset defense unless the defendants are ʺpermitted a late ʹopt‐inʹ to share as [] \n\nbeneficiar[ies] of the Trust.ʺ3  PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. \n\nGenecco Produce, Inc. (In re Lenny Perryʹs Produce), Bankr. No. 09‐10297 K, 2012 \n\nWL 7767580, at *4, 2012 Bankr. LEXIS 5440, at *14 (Bankr. W.D.N.Y. Aug. 14, \n\n2012).  On November 12, 2012, the district court adopted the bankruptcy courtʹs \n\n\n\n                                                            \n  Although the district court has jurisdiction over the adversary proceeding between \n 3\n\nthe plaintiffs and the defendants, it entered a Special Order of Reference to the \nbankruptcy court.  Pursuant to that Special Order, the bankruptcy court presided over \neach of the motions filed in this matter and issued reports and recommendations to the \ndistrict court.  \n 10 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nrecommendation.  John B. Ordille, Inc. v. Lenny Perryʹs Produce, Inc., No. 12‐MC‐\n\n54S, 2012 WL 5499652, 2012 U.S. Dist. LEXIS 161648 (W.D.N.Y. Nov. 12, 2012).    \n\n\n Motion for Summary Judgment \n\n\n On May 3, 2013, the plaintiffs moved for summary judgment, renewing \n\ntheir argument that GPI could only bring an offset claim against LPP, not against \n\nthe plaintiffs.  On February 12, 2014, the bankruptcy court recommended that the \n\ndistrict court grant the plaintiffsʹ motion.  Report and Recommendation, PACA \n\nTrust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., No. 09‐1269‐\n\nMJK (W.D.N.Y. Feb. 12, 2014), ECF No. 126.  It rejected the defendantsʹ argument \n\nthat a long‐term bartering arrangement had extinguished GPIʹs debts to LPP.  \n\nThe bankruptcy court noted that GPI had failed to produce any tax documents or \n\nother evidence to substantiate its claim of a bartering arrangement with LPP.  To \n\nthe contrary, it concluded, ʺthe parties were simply selling commodities to each \n\nother . . . , maintaining open, off‐setting accounts that remained so (meaning \n\nnever materially reconciled by off‐set) right up until the [d]ebtor went out of \n\nbusiness.ʺ  Id.  For that reason, it recommended that the district court enter \n\njudgment in favor of the plaintiffs in the amount that GPI owed to LPP, less GPIʹs \n\npro rata share of the PACA Trust.     \n\n\n 11 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n On September 4, 2014, the district court remanded the matter to the \n\nbankruptcy court for further proceedings.  PACA Trust Creditors of Lenny Perryʹs, \n\nInc. v. Genecco Produce, Inc., No. 14‐MC‐036S, 2014 WL 4385436, at *1, 2014 U.S. \n\nDist. LEXIS 123965, at *3 (W.D.N.Y. Sept. 4, 2014).  It explained that because \n\nʺbartering and setoff are different concepts,ʺ the absence of a bartering \n\nrelationship does not necessarily defeat an offset defense.  Id. at *3‐4; 2014 U.S. \n\nDist. LEXIS 123965, at *7.  The district court directed the bankruptcy court, on \n\nremand, to consider whether (i) GPI’s debt to LPP and LPPʹs debt to GPI \n\nconstitute ʺmutual debt[s]ʺ for purposes of section 553 of the Bankruptcy Code, \n\nand (ii) whether any funds due from GPI to LPP are PACA Trust assets not \n\nsubject to the defendantsʹ offset claim.  Id. at *2‐3; 2014 U.S. Dist. LEXIS 123965, at \n\n*7, 9‐10.   \n\n\n On February 23, 2015, the bankruptcy court issued a ʺClarified Report and \n\nRecommendation,ʺ which explained in greater detail—but did not materially \n\nalter—its February 12, 2014 recommendation.  PACA Trust Creditors of Lenny \n\nPerryʹs Produce, Inc. v. Genecco Produce, Inc. (In re Lenny Perryʹs Produce, Inc.), \n\nNo. 09‐10297 K, 2015 Bankr. LEXIS 2713 (Bankr. W.D.N.Y. Feb. 23, 2015).  On \n\nAugust 12, 2015, the district court again remanded the matter to the bankruptcy \n\n\n 12 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ncourt, explaining that ʺclarification of the issues raised in the partiesʹ submissions \n\nas well as this Courtʹs prior order is warranted.ʺ  PACA Trust Creditors of Lenny \n\nPerryʹs Produce v. Genecco Produce, Inc., No. 15‐MC‐028S, 2015 WL 4761627, at *6, \n\n2015 U.S. Dist. LEXIS 105908, at *15 (W.D.N.Y. Aug. 12, 2015). \n\n\n The bankruptcy court issued what turned out to be its final report and \n\nrecommendation on December 28, 2015.  PACA Trust Creditors of Lenny Perryʹs \n\nProduce, Inc. v. Genecco Produce, Inc. (In re Lenny Perryʹs Produce, Inc.), No. 09‐\n\n10297 K, 2015 WL 9581383, 2015 Bankr. LEXIS 4371 (Bankr. W.D.N.Y. Dec. 28, \n\n2015).  The court concluded that ʺthe Trust’s rights are not now, and never were, \n\nsubject to the limitations that [LPP] suffered as to [GPI], or the defenses that \n\n[GPI] had against [LPP].ʺ  Id. at *2; 2015 Bankr. LEXIS 4371, at *4‐5.  In the \n\nbankruptcy courtʹs view, ʺevery item of perishable commodities [LPP] ever \n\nhandled was held by it in trust, as were any proceeds realized from those items,ʺ \n\nso that ʺeverything that [LPP] received from [GPI] or was entitled to receive from \n\n[GPI] on account of perishable commodities delivered to [GPI] was subject to the \n\nstatutory PACA Trust in favor of growers, cooperatives, etc.[,] which were owed \n\nmoney for those commodities.ʺ  Id.; 2015 Bankr. LEXIS 4371, at *5.  The PACA \n\n\n\n\n 13 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nTrust existed ʺfrom the moment that [LPP] bought or sold commodities subject to \n\nPACA.ʺ  Id.; 2015 Bankr. LEXIS 4371, at *5.   \n\n\n The bankruptcy court further decided that LPP and GPIʹs method of doing \n\nbusiness by maintaining mutual debts ʺwas not consistent with PACA,ʺ which \n\nrequires timely payments ʺso that all providers of perishable agricultural \n\ncommodities to [LPP] had a chance to receive cash payments from [GPI] for what \n\nthey provided.ʺ  Id. at *4; 2015 Bankr. LEXIS 4371, at *11‐12.  It concluded that \n\nʺequity requires treatment that PACA would seem to require,ʺ id.; 2015 Bankr. \n\nLEXIS 4371, at *12:  a judgment against GPI equal to ʺthe difference between what \n\n[GPI] owed [LPP] on the date of the Chapter 7 petition (and therefore owes to the \n\nPACA Trust) and the amount that [GPI] would receive as a PACA Trust \n\nbeneficiary,ʺ id. at *6; 2015 Bankr. LEXIS 4371, at *19 (emphasis in original).     \n\n\n On June 7, 2017, the district court adopted the bankruptcy courtʹs \n\nrecommendation in full.  PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. \n\nGenecco Produce Inc., No. 16‐MC‐4S, 2017 WL 2462035, 2017 U.S. Dist. LEXIS \n\n87488 (W.D.N.Y. June 7, 2017).  The district court rejected the defendantsʹ \n\nargument that they are entitled to a complete offset.  It observed that offsets only \n\napply to mutual debts, and the debts between GPI and LPP are ʺmutual only to \n\n\n 14 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthe extent [d]efendants are co‐beneficiaries to the PACA Trust.  And, to the \n\nextent that they are co‐beneficiaries, [p]laintiffs and [d]efendants owe one \n\nanother a fiduciary duty to take no more than their [pro rata] share of trust \n\nassets.ʺ  Id. at *2; 2017 U.S. Dist. LEXIS 87488, at *4.  The district court also \n\nrejected the plaintiffsʹ argument that the defendantsʹ failure to file a PACA claim \n\nprecludes them from recovering a pro rata share of the PACA Trust.  Instead, the \n\ndistrict court decided that allowing the defendants limited recovery as PACA \n\ncreditors ʺbest furthers the policies of PACA.ʺ  Id. at *1; 2017 U.S. Dist. LEXIS \n\n87488, at *4.  The district court concluded that although the defendants are not \n\nentitled to an offset under bankruptcy law, they may recover a pro rata share of \n\nthe PACA Trust.  Id.; 2017 U.S. Dist. LEXIS 87488, at *4‐5.   \n\n\n DISCUSSION \n\n There are two issues raised on appeal:  First, whether the district court \n\nerred in concluding that LPPʹs accounts receivable constitute PACA Trust assets \n\nand that the defendants are therefore not entitled to a statutory offset of their \n\ndebts to LPP against LPPʹs debts to them; and second, whether the district court \n\nerred in allowing the defendants to recover a pro rata share of the PACA Trust.  \n\nThe defendants argue that the Bankruptcy Code, 11 U.S. Code § 553, which \n\n\n 15 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\ngoverns ʺSetoff,ʺ entitles them to a complete offset of any amount otherwise due \n\nto the PACA Trust.  The plaintiffs respond that the defendants may not recover \n\neven a pro rata share of the PACA Trust because they elected not to participate in \n\nthe PACA claims procedure in the bankruptcy court.  For the reasons discussed \n\nbelow, we affirm the district courtʹs judgment in its entirety. \n\n\n I. Standard of Review \n\n\n ʺWe review a grant of summary judgment de novo, examining the \n\nevidence in the light most favorable to, and drawing all inferences in favor of, the \n\nnon‐movant.ʺ  Blackman v. N.Y. City Transit Auth., 491 F.3d 95, 98 (2d Cir. 2007) \n\n(per curiam) (quoting Sheppard v. Beerman, 317 F.3d 351, 354 (2d Cir. 2003)).  \n\nSummary judgment is appropriate only if ʺthe movant shows that there is no \n\ngenuine dispute as to any material fact and the movant is entitled to judgment as \n\na matter of law.ʺ  Fed. R. Civ. P. 56(a).  A genuine dispute exists if ʺthe evidence \n\nis such that a reasonable jury could return a verdict for the nonmoving party.ʺ  \n\nFireman’s Fund Ins. Co. v. Great Am. Ins. Co. of N.Y., 822 F.3d 620, 631 n.12 (2d Cir. \n\n2016) (internal quotation marks omitted).  However, ʺa party may not rely on \n\nmere speculation or conjecture as to the true nature of the facts to overcome a \n\nmotion for summary judgment.ʺ  Fletcher v. Atex, Inc., 68 F.3d 1451, 1456 (2d Cir. \n\n\n 16 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n1995) (internal quotation marks omitted).  The party opposing summary \n\njudgment ʺmust do more than simply show that there is some metaphysical \n\ndoubt as to the material facts.ʺ  Matsushita Elec. Indus. Co. v. Zenith Radio Corp., \n\n475 U.S. 574, 586 (1986). \n\n\n When a district court interprets its own order, we apply an abuse‐of‐\n\ndiscretion standard.  Garcia v. Yonkers Sch. Dist., 561 F.3d 97, 103 (2d Cir. 2009); \n\nsee also United States v. Spallone, 399 F.3d 415, 423 (2d Cir. 2005) (ʺWhen an issuing \n\njudge interprets his own orders, we accord substantial deference to the \n\ndraftsman, and we will not reverse the judgeʹs construction of an ambiguity in \n\nhis own words except for abuse of discretion.ʺ). \n\n\n II. Statutory Offset  \n\n The defendants advance two arguments challenging the district courtʹs \n\nconclusion that they are not entitled to a complete offset of the debts covered by \n\nPACA from them to LLP against those from LLP to the defendants under New \n\nYork State law and federal bankruptcy law.  First, they argue that LPPʹs relevant \n\naccounts receivable were transferred to the PACA Trust, if at all, subject to the \n\ndefendantsʹ offset rights.  Second, they argue that factual disputes exist as to \n\n\n\n\n 17 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nwhether LPPʹs accounts receivable constituted PACA Trust assets.  We reject \n\nboth arguments. \n\n\n 1. Availability of Offset Defense Against the Plaintiffs’ PACA Claim \n\n The defendants claim that ʺ[n]o authority exists,ʺ Defendantsʹ Br. 14, that \n\nwould require the defendants to ʺpay [their] debts in full to the bankrupt[], while \n\nallowing the [defendants] to recover only a percentage of the debts owed to \n\n[them] by the bankrupt[, LPP],ʺ id. at 13 (internal quotation marks omitted).  Not \n\nso.  The statutory language of PACA and section 553 of the U.S. Bankruptcy \n\nCode, as well as this Courtʹs prior decisions, require precisely that.   \n\n\n The PACA trust provision, which Congress enacted in order ʺto make the \n\nsellersʹ interests in the commodities and sales proceeds superior to those of the \n\nbuyersʹ creditors,ʺ Am. Banana Co. v. Rep. Natʹl Bank of N.Y., 362 F.3d 33, 37 (2d \n\nCir. 2004), states in relevant part:  \n\n Perishable agricultural commodities received by a \n commission merchant, dealer, or broker in all \n transactions . . . and any receivables or proceeds from \n the sale of such commodities or products, shall be held \n by such commission merchant, dealer, or broker in trust \n for the benefit of all unpaid suppliers or sellers of such \n commodities or agents involved in the transaction, until \n full payment of the sums owing in connection with such \n transactions has been received by such unpaid \n suppliers, sellers, or agents.  \n 18 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n7 U.S.C. § 499e(c)(2).  Under regulations adopted by the U.S. Department of \n\nAgriculture (ʺDOAʺ), PACA assets ʺare to be preserved as a nonsegregated \n\nʹfloatingʹ trust.ʺ  7 C.F.R. § 46.46(b).  PACA and related DOA regulations provide \n\nproduce sellers with ʺa self‐help tool enabling them to protect themselves against \n\nthe abnormal risk of losses resulting from slow‐pay and no‐pay practices by \n\nbuyers or receivers of fruits and vegetables.ʺ  Coosemans Specialties, Inc. v. \n\nGargiulo, 485 F.3d 701, 705 (2d Cir. 2007) (citations omitted). \n\n\n We have explained that ʺ[o]rdinary principles of trust law apply to the \n\ntrusts created by [PACA] . . . so that the Produce Debtor holds the legal title to \n\nthe Produce and its derivatives or proceeds but the seller retains an equitable \n\ninterest in the trust property pending payment[.]ʺ  Tom Lange Co. v. Kornblum & \n\nCo. (In re Kornblum & Co.), 81 F.3d 280, 284 (2d Cir. 1996) (citations omitted).  \n\nBecause PACA creditors hold an equitable interest in the PACA trust pending \n\npayment, ʺthe Bankruptcy Code excludes PACA trust assets from the bankruptcy \n\nestate.ʺ  Id. (citing, inter alia, United States v. Whiting Pools, Inc., 462 U.S. 198, 205 \n\nn.10 (1983) (explaining that the Bankruptcy Code ʺplainly exclude[s from the \n\nbankruptcy estate] property of others held by the debtor in trust at the time of \n\nthe filing of the [bankruptcy] petitionʺ)).  Consequently, PACA ʺgives unpaid \n\n\n 19 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n[produce] suppliers . . . priority over secured lenders . . . to PACA trust assets.ʺ  \n\nAlbee Tomato, Inc. v. A.B. Shalom Produce Corp., 155 F.3d 612, 615 (2d Cir. 1998). \n\n\n The defendantsʹ reliance on bankruptcy law to defend against PACA \n\nclaims is misplaced.  To the extent the disputed assets represent PACA Trust \n\nassets, they are held outside the bankruptcy estate, and their disposition is, \n\ntherefore, governed by trust law rather than bankruptcy law.  See Kornblum, 81 \n\nF.3d at 284.  To permit a bankruptcy offset against PACA Trust assets would be \n\ninconsistent with Congressʹs intent in amending PACA in 1984 to ʺbroaden the \n\nprotections afforded to produce suppliersʺ who had previously ʺreceive[d] little \n\nprotection in any suit for recovery of damages where a buyer ha[d] failed to \n\nmake payment as required by the contract.ʺ  Id. at 283 (citation omitted).  Because \n\nPACA provides unpaid produce sellers with priority over other creditors and \n\nestablishes that the disposition of PACA assets is governed by trust law, see id. at \n\n284, we conclude that the district court did not err in deciding that the \n\ndefendants are not entitled to the offset they seek under New York and federal‐\n\nbankruptcy law.4 \n\n\n\n                                                            \n This conclusion is buttressed by the language in section 553 of the U.S. Bankruptcy \n4\n\nCode, which makes offsets available only for ʺmutualʺ debts.  11 U.S.C. § 553(a).  \n \n 20 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n 2. No Genuine Dispute of Material Fact \n\n The defendants next argue that material factual disputes exist as to \n\nwhether LPPʹs accounts receivable for the sale of produce to the defendants, \n\ntotaling $204,774.88, constitute PACA Trust assets.  The defendants suggest that \n\nbecause they sought an offset before the district court issued its Claims \n\nProcedure Order, LPPʹs receivables never became PACA Trust assets, or, if they \n\ndid, they were transferred subject to the defendantsʹ offset rights.   \n\n\n The defendantsʹ argument misses the mark.  We have explained that a \n\nPACA trust ʺis automatically established each time a broker or merchant \n\npurchases perishable commodities.ʺ  D.M Rothman & Co., Inc. v. Korea Commercial \n\nBank of N.Y., 411 F.3d 90, 96 (2d Cir. 2005); accord C&E Enters., Inc. v. Milton \n\n\n\n                                                            \nMutuality exists where debts ʺare due to and from the same persons in the same \ncapacity.ʺ  Westinghouse Credit Corp. v. D’Urso, 278 F.3d 138, 149 (2d Cir. 2002) (citations \nomitted).  The debts here are not mutual because the defendants and LPP appear in \ndifferent capacities:  The defendants assert their claim to $263,061.92 in their capacity as \ncreditors in LPP’s bankruptcy proceeding; LPP, by contrast, does not—and cannot—\nassert a claim for $204,774.88 in its capacity as a creditor, but instead pursues those \nfunds solely on behalf of unpaid suppliers.  See 7 U.S.C. § 499e(c)(2) (“Perishable \nagricultural commodities received by a . . . merchant, . . . and any receivables or \nproceeds from the sale of such commodities . . . , shall be held . . . in trust for the benefit \nof all unpaid suppliers . . . until full payment of the sums owing . . . has been received \nby such unpaid suppliers[.]”); cf. DʹUrso, 278 F.3d at 149 (ʺ[O]bligations lack mutuality \nwhere one party is a trust beneficiary asserting his or her rights against a trustee, and \nthe other is a creditor exercising his or her contractual rights[.]ʺ). \n\n 21 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nPoulos, Inc. (In re Milton Poulos, Inc.), 947 F.2d 1351, 1352 (9th Cir. 1991) (ʺThe \n\n[PACA] trust automatically arises in favor of a produce seller upon delivery of \n\nproduce[.]ʺ); Patterson Frozen Foods, Inc. v. Crown Foods Int’l, Inc., 307 F.3d 666, 669 \n\n(7th Cir. 2002) (ʺTh[e PACA] floating trust is automatically created when the \n\ndealer accepts the goods[.]ʺ).  Any factual dispute as to whether the defendants \n\nasserted their offset claim before the district court issued the Claims Procedure \n\nOrder is immaterial:  Even if the defendantsʹ offset claim predates the Claims \n\nProcedure Order, the PACA Trust arose immediately upon the sale of produce \n\nfrom the plaintiffs to LPP—long before the defendants asserted their offset \n\nclaim—such that the accounts receivable associated with those transactions \n\nwould not be subject to that defense. \n\n\n The defendants further argue that the plaintiffs have failed to establish that \n\nthe accounts receivable were PACA Trust assets.  This argument, too, fails.  It is \n\nthe defendants who bear the burden of demonstrating that disputed assets do not \n\nconstitute PACA trust assets.  Kornblum, 81 F.3d at 287.  They have not met that \n\nburden.  Nothing in the record suggests that LPP entered into a factoring \n\nagreement with GPI, that LPP and GPI engaged in a bartering relationship, or \n\nthat LPP and GPI paid down their mutual debts.  Instead, the record establishes \n\n\n 22 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nthat LPP and GPIʹs debts to each other remained outstanding when GPI filed for \n\nbankruptcy.  \n\n\n The defendants thus have failed to identify any genuine dispute of \n\nmaterial fact as to whether LPPʹs accounts receivable constitute PACA Trust \n\nassets. \n\n\n III. Pro Rata Share   \n\n  Finally, we address the district courtʹs decision to award the defendants a \n\npro rata share of the PACA Trust, in light of the defendantsʹ loss on their set‐off \n\nclaim and failure to file a proof of claim after the district court issued the Claims \n\nProcedure Order.  The bankruptcy court recommended that the district court \n\nallow the defendants to recover a pro rata share, in part because the Claims \n\nProcedure Order did not specify which ʺreceivablesʺ were ʺtrust assetsʺ; it was \n\ntherefore ʺnot unreasonable for [GPI] to have relied upon its belief that ordinary \n\nsetoff rights as to ʹreceivablesʹ would apply.ʺ  In re Lenny Perryʹs Produce, 2012 \n\nWL 7767580, at *4, 2012 Bankr. LEXIS 5440, at *14‐15, adopted, John B. Ordille, Inc. \n\nv. Lenny Perryʹs Produce, Inc., No. 12‐MC‐54S, 2012 WL 5499652, 2012 U.S. Dist. \n\nLEXIS 161648 (W.D.N.Y. Nov. 12, 2012).   \n\n\n\n\n 23 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\n The district court agreed:  It noted that the ʺ[d]efendants raised their \n\ndefense of offset even before the PACA Claims Procedure was established,ʺ and \n\nconcluded that they ʺhad a good faith basis for pursuing their claims through a \n\nbankruptcy offset rather than through the PACA claims process.ʺ  PACA Trust \n\nCreditors of Lenny Perryʹs Produce, Inc., 2017 WL 2462035, at *1, 2017 U.S. Dist. \n\nLEXIS 87488, at *4. \n\n\n The district court did not err in allowing the defendants to recover a pro \n\nrata share of the PACA Trust.  It is undisputed that the defendants complied \n\nwith all statutory requirements to preserve their PACA claims:  In each invoice \n\nthat GPI sent to LPP, it provided written notice of intent to preserve its PACA \n\nrights.  It is also undisputed that the defendants filed a proof of claim in \n\nbankruptcy court before the Claims Procedure Order was issued, for an offset in \n\nthe amount of $263,061.92.  Having filed an offset claim, the defendants \n\nreasonably thought that their debt to LPP was not a ʺreceivableʺ under the \n\nClaims Procedure Order and that they were not required to submit a PACA \n\nproof of claim.  The bankruptcy court and district court properly concluded that, \n\nin light of ambiguities in the Claims Procedure Order and the novelty of the legal \n\n\n\n\n 24 \n \n\f   17‐1949‐cv, 17‐2051‐cv \n The PACA Trust Creditors of Lenny Perryʹs Produce, Inc. v. Genecco Produce, Inc., David Genecco \n\nissues presented, the defendants had a good‐faith basis to pursue their claims \n\nthrough a bankruptcy offset in lieu of a PACA claim. \n\n\n Moreover, the statute states, in relevant part, that perishable goods and \n\nany receivables from their sale are held in trust ʺfor the benefit of all unpaid \n\nsuppliers or sellers of such commodities or agents involved in the transaction, \n\nuntil full payment of the sums owing in connection with such transactions has \n\nbeen received by such unpaid suppliers, sellers, or agents.ʺ  7 U.S.C. § 499e(c)(2) \n\n(emphasis added).  The defendants are unpaid suppliers of produce.  Denying \n\nthem a pro rata share of the PACA Trust, even though they preserved their \n\nPACA claims and filed a proof of claim in bankruptcy court, would be, we think, \n\ninconsistent with the statutory text and the district courtʹs interpretation of its \n\nown Claims Procedure Order.  We therefore conclude that the district court did \n\nnot err in permitting the defendants to recover a pro rata share of the PACA \n\nTrust. \n\n\n CONCLUSION \n We have considered the partiesʹ other arguments on appeal and conclude \n\nthat they are without merit.  For the foregoing reasons, we AFFIRM the \n\njudgment of the district court. \n\n\n\n 25\n[END_CASE]", "role": "user" } ]
4,579,881
Ogunkoya v. Drake
2019-01-09
17-3235
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: HALL, LYNCH, and CARNEY, Circuit Judges.", "parties": "", "opinions": [{"author": "PETER W. HALL, Circuit Judge:", "type": "010combined", "text": "17-3235\nOgunkoya v. Drake\n\n\n In the\n United States Court of Appeals\n For the Second Circuit\n\n August Term, 2018 \n  \n Argued: September 27, 2018 \n Decided: January 9, 2019 \n  \n Docket No. 17‐3235‐cv \n  \n  \n SEUN OGUNKOYA, \n  \n Plaintiff‐Appellee, \n   \n v. \n  \n MARK MONAGHAN, JAMES EGAN, COUNTY OF MONROE,  \n  \n Defendants‐Appellants, \n  \n SANDRA DOORLEY, ALBERT DRAKE III, INVESTIGATOR, DARIUSZ ZYSK, \nINVESTIGATOR, PETER SCHRAGE, TROOPER, MARK EIFERT, INVESTIGATOR, JOHN DOE, \n RICHARD ROE, \n  \n Defendants. \n  \n  \n\n\n\n  The Clerk of Court is respectfully requested to amend the official caption as set forth above.   \n 1 \n\f Appeal from the United States District Court \n for the Eastern District of New York \n No. 15‐CV‐06119, Matsumoto, Judge. \n  \n  \nBefore:  HALL, LYNCH, and CARNEY, Circuit Judges. \n\n \nThis  appeal  arises  out  of  Plaintiff‐Appellee  Seun  Ogunkoya’s  §  1983  lawsuit  alleging \nconstitutional violations during his warrantless arrest and subsequent prosecution.  He \nwas acquitted of all charges.  Two Monroe County Assistant District Attorneys appeal \nthe District Court’s denial of their Rule 12(b)(6) motion to dismiss on the ground that they \nhave absolute immunity for the violations alleged.  We hold that the Assistant District \nAttorneys have absolute immunity from suit and thus reverse the decision of the District \nCourt  with  respect  to  claims  against  these  prosecutors  in  their  individual  capacities.  \nMonroe  County  also  appeals  the  District  Court’s  denial  of  its  Rule  12(b)(6)  motion \narguing that municipal liability is not warranted because the county prosecutors were \nstate, not county, actors.  Because the elements of the claim against the county are not \ninextricably  intertwined  with  the  question  of  absolute  immunity,  we  are  without \nappellate jurisdiction to hear the county’s interlocutory appeal.  \n \n  REVERSED IN PART; DISMISSED IN PART; AND REMANDED. \n \n MATTHEW  D.  BROWN,  for  Michael  E.  Davis,  County \n Attorney, Monroe County, New York, for  Defendants‐\n Appellants. \n  \n DANIEL M. WHITE, Milbank, Tweed, Hadley & McCloy, \n LLP,  New  York,  NY  (Alexandra  Wang,  Max  Kelly, \n Milbank, Tweed, Hadley & McCloy, LLP, New York, \n New York, on the brief) for Plaintiff‐Appellee. \n  \n \nPETER W. HALL, Circuit Judge: \n\n This appeal principally concerns whether two Monroe County Assistant District \n\nAttorneys, James Egan and Mark Monaghan (“the ADAs”), are absolutely immune from \n\n\n\n 2 \n\fcivil  suit  for  interfering  in  the  timing  of  Plaintiff‐Appellee  Seun  Ogunkoya’s \n\narraignments in several town courts as the ADAs were preparing to present the charges \n\nto  a  grand  jury.  Ogunkoya  alleged  that the  ADAs, along  with  other  state  and county \n\ndefendants, violated his Fourth and Fourteenth Amendment rights by failing to timely \n\narraign him on four of six identity fraud and larceny charges.  Because the ADAs were \n\nperforming a traditional prosecutorial function when they determined that they would \n\ninitiate  Ogunkoya’s  prosecution  via  grand  jury  indictment  and  thus  delay  his \n\narraignment  on  separate  individual  charges,  we  reverse  the  District  Court’s  denial  of \n\nabsolute immunity.   \n\n Regarding Monroe County’s effort to appeal the denial of its motion to dismiss, \n\nbecause the claims against the county are not inextricably intertwined with the question \n\nof the ADAs’ immunity, we are without jurisdiction to consider the County’s appeal at \n\nthis time.   \n\n I. \n\n Absolute  immunity  protects  a  prosecutor  “not  only  from  liability  but  also  from \n\nsuit.”    Shmueli  v.  City  of  New  York,  424  F.3d  231,  236  (2d  Cir.  2005).    “Hence,  an \n\ninterlocutory  order  rejecting  the  defense  [of  absolute  immunity]  is  immediately \n\nappealable under the collateral order doctrine.”  Id.  \n\n “When a district court denies immunity on a Rule 12(b)(6) motion to dismiss, ‘we \n\nreview the district court’s denial de novo, accepting as true the material facts alleged in \n\n\n 3 \n\fthe  complaint  and  drawing  all  reasonable  inferences  in  plaintiffs’  favor.’”    Warney  v. \n\nMonroe Cty., 587 F.3d 113, 120 (2d Cir. 2009) (quoting Johnson v. Newburgh Enlarged Sch. \n\nDist., 239 F.3d 246, 250 (2d Cir. 2001)). \n\n II. \n\n  The  facts  as alleged in Ogunkoya’s  complaint are as  follows.  The  investigation \n\nleading  to  his  arrest  began  when  Home  Depot  reported  several  gift  card  purchases \n\nsuspected to be fraudulent to the New York State Police (“NYSP”).  The gift cards, totaling \n\n$28,000,  were  all  acquired  on  April  26,  2014,  at  Home  Depot  stores  in  three  Monroe \n\nCounty  towns—Greece,  Henrietta,  and  Irondequoit.    NYSP  Investigator  Mark  Eifert \n\nopened a criminal investigation and learned that Ogunkoya used his personal credit card \n\nfor small purchases in the Greece and Henrietta stores around the same time as the gift \n\ncards  were  purchased.    Eifert  also  reviewed  Home  Depot’s  surveillance  tapes.    Those \n\ntapes  show  someone  other  than  Ogunkoya  purchasing  the  gift  cards.    On  January  20, \n\n2015, Eifert prepared six felony complaints charging Ogunkoya with one count of identity \n\ntheft and one count of grand larceny in each of the three towns.  \n\n  A  month  later,  acting  on  Eifert’s  knowledge  and  belief,  but  without  an  arrest \n\nwarrant, the NYSP arrested Ogunkoya in his Brooklyn apartment.  Over the course of the \n\nday,  NYSP  officers  drove  Ogunkoya  to  Monroe  County,  where  he  was  brought  for \n\narraignment  before  the  Henrietta  Town  Court  around  10  P.M.    The  NYSP  filed  all  six \n\nfelony  complaints  with  the  Henrietta  court,  but  the  judge  refused  on  jurisdictional \n\n\n 4 \n\fgrounds to arraign Ogunkoya on the four complaints based on conduct alleged to have \n\noccurred in Greece and Irondequoit.  The judge instructed the NYSP to have Ogunkoya \n\narraigned on the remaining complaints during the next business day, Monday, February \n\n23, 2015.     \n\n  Ogunkoya was never arraigned in Greece or Irondequoit.  Instead, a bail hearing \n\nwas held that Monday in Monroe County Court.  At the hearing, Ogunkoya, who was \n\nplanning to sit for the bar exam in New York City the following day, asked to be arraigned \n\non the four remaining complaints “in time for a new bail application to be made on all \n\nthe charges.”  J. App. 11.  Considering Ogunkoya a “flight risk,” the ADAs argued for a \n\n$100,000  cash/$300,000  bond  bail  “based  on  the  combined  allegations  of  the  six  felony \n\ncomplaints.”    Id.    The  judge  set  Ogunkoya’s  bail  at  $100,000  cash/$300,000  bond.    As \n\nalleged by Ogunkoya, “[t]his amount of bail is unusually high considering the amount of \n\nthe alleged thefts [] and local custom.”  Id.   \n\n  Ogunkoya’s  family  then  sought  to  arrange  for  bail,  but  the  bail  bondsman \n\n“expressed  reluctance  at  posting  a  bond”  because  of  Ogunkoya’s  four  outstanding \n\ncriminal complaints on which he had not yet been arraigned.  J. App. 12.  Ogunkoya’s \n\ncounsel wrote to ADA Egan and again requested that Ogunkoya be arraigned on the four \n\noutstanding complaints so that he could secure bail.  Egan responded by email: \n\n There is no need to ever arraign him on the charges in the local court.  He \n was arrested on the Henrietta charges and received his prompt arraignment \n on them as required by the CPL.  The purpose of CPL 140.20 is to ensure a \n person who is arrested gets a prompt arraignment and doesn’t have to sit \n 5 \n\f in jail waiting for bail to be set.  The other charges are essentially “sealed” \n charges  since  he  has  never  been  arrested  or  arraigned  on  them.    In  any \n event, they were all referred to the grand jury and they will be presented \n together.    This  is  done  frequently  in  cases  involving  charges  in  multiple \n jurisdictions. \n  \nId. \n\n  Ogunkoya’s  counsel  continued  to  press  for  arraignment,  seeking  a  writ  on  the \n\nground that “Ogunkoya was prepared to post a $300,000 bond but that the bail bondsman \n\nrefused  to  post  the  bond  solely  because  of  the  unarraigned  charges.”    J.  App.  13.    On \n\nMarch 20th—28  days  after  his arrest—Ogunkoya was released after  a Monroe  County \n\nCourt judge signed his bond documents.  On or about May 15, 2015, a Monroe County \n\ngrand  jury  indicted  Ogunkoya  on  three  counts  of  identity  theft,  one  count  from  each \n\ntown.  At trial, the jury acquitted Ogunkoya on all charges.   \n\n  After  his  acquittal  Ogunkoya,  pro  se,  filed  a  §  1983  lawsuit  naming  the  NYSP \n\nofficers  involved  in  his  arrest,  Monroe  County  DA  Sandra  Doorley,1  Monroe  County \n\nADAs  Monaghan  and  Egan,  and  Monroe  County  itself.    Ogunkoya  amended  his \n\ncomplaint twice, with pro bono counsel filing the second amended complaint.  Both the \n\nNYSP and Monroe County defendants moved to dismiss under Fed. R. Civ. P. 12(b)(6) \n\n\n\n\n1 Monroe County District Attorney Sandra Doorley was incorrectly sued in her individual \ncapacity as Susan Doorley.  Although the briefs list Doorley as an appellant, the District Court \nadopted the magistrate judge’s recommendation that all claims against her be dismissed.  \nAccordingly, nothing remains pending against her at this time, and she has no stake in the \ninstant appeal. \n 6 \n\farguing that Ogungoya’s complaint failed to state a claim and that the prosecutors had \n\nabsolute immunity.  The fully briefed motions were referred to the magistrate judge.  \n\n  The  magistrate  judge’s  Report  and  Recommendation  (“R&R”)  construed  the \n\nsecond amended complaint to plead the following claims against all the individual NYSP \n\nand  Monroe  County  defendants:  false  arrest  and  false  imprisonment,  malicious \n\nprosecution, failure to arraign, and related claims for failure to intervene with respect to \n\neach of the preceding claims.  The R&R also construed Ogunkoya’s complaint to assert a \n\nMonell  municipal  liability  claim  against  Monroe  County,  alleging  an  unconstitutional \n\npractice or custom and failure to train its officers.  The magistrate judge recommended \n\nthat all claims against the NYSP defendants proceed except the claims alleging malicious \n\nprosecution,  failure  to  intervene  in  plaintiff’s  prosecution,  and  failure  to  intervene  in \n\nplaintiff’s arraignment on the part of the arresting officers in Brooklyn.  \n\n  With respect to the ADAs, the magistrate judge recommended that the false arrest, \n\nmalicious  prosecution,  and  related  failure  to  intervene  claims  be  dismissed.    The \n\nmagistrate judge recommended that the failure to arraign and related failure to intervene \n\nclaims proceed against the ADAs.  In so doing, the magistrate judge ruled that the ADAs \n\nwere  not  entitled  to  absolute  immunity  for  their  roles  in  the  events  underlying \n\nOgunkoya’s failure to arraign claims.   \n\n  In addition, the magistrate judge recommended that all claims against DA Doorley \n\nbe  dismissed  because  she  lacked  personal  involvement  or  had  absolute  immunity.    \n\n\n 7 \n\fFinally,  the  magistrate  judge  recommended  that  the  municipal  liability  claim  against \n\nMonroe County also proceed because Ogunkoya had plausibly pled a Monell violation \n\nrequiring the resolution of factual questions.   \n\n  The district judge adopted the R&R.  This appeal followed.   \n\n III. \n\n  Absolute immunity bars § 1983 suits against prosecutors for their role “in initiating \n\na prosecution and in presenting the State’s case.”  Imbler v. Pachtman, 424 U.S. 409, 431 \n\n(1976).  Instead of relying on strict categories of actions with respect to which absolute \n\nimmunity attaches, the relevant question is “whether there is pending or in preparation \n\na court proceeding in which the prosecutor acts as an advocate.”  Warney, 587 F.3d at 123.  \n\nUltimately, we ask “whether a reasonable prosecutor would view the acts challenged by \n\nthe complaint as reasonably within the functions of a prosecutor.”  Giraldo v. Kessler, 694 \n\nF.3d 161, 166 (2d Cir. 2012).  \n\n  The ADAs’ decision to prosecute Ogunkoya and proceed by grand jury indictment \n\nrather  than  proceed  on  separate  criminal  complaints  is  a  prosecutorial  exercise  of \n\ndiscretion  entitled  to  absolute  immunity.    See  Burns  v.  Reed,  500  U.S.  478,  486  (1991) \n\n(quoting Imbler, 424 U.S. at 430–31) (holding that “[p]rosecutors are absolutely immune \n\n. . . for their conduct in ‘initiating a prosecution’”).  What we must decide is whether the \n\nADAs  are  entitled  to  absolute  immunity  when  they  directed  the  NYSP  not  to  have \n\n\n\n\n 8 \n\fOgunkoya  arraigned  in  the  Greece  and  Irondequoit  town  courts  and  informed  those \n\ncourts that Ogunkoya would not be arraigned.  \n\n  In our view, the Supreme Court’s pronouncement in Imbler squarely addresses the \n\nconduct of the ADAs at issue here.  424 U.S. at 430–31.  The Court noted: \n\n We recognize that the duties of the prosecutor in his role as advocate for the \n State  involve  actions  preliminary  to  the  initiation  of  a  prosecution  and \n actions  apart  from  the  courtroom.    A  prosecuting  attorney  is  required \n constantly, in the course of his duty as such, to make decisions on a wide \n variety of sensitive issues.  These include questions of whether to present a \n case  to  a  grand  jury,  whether  to  file  an  information,  [and]  whether  and \n when to prosecute. . . . \n  \nId. at 431 n.33. \n\n  The District Court erred in denying the ADAs absolute immunity.  The District \n\nCourt  found  that  “’a  reasonable  prosecutor’  would  conclude  that  the  Greece  and \n\nIrondequoit arraignments were a police, not a prosecutorial, responsibility.”  J. App. 113.  \n\nWe disagree.  It is true that, in New York, the responsibility for presenting a detained \n\nperson before a court for evaluation of the legality of his or her detention is generally a \n\npolice responsibility.  See N.Y. Crim. Proc. Law § 140.20(1) (McKinney) (“Upon arresting \n\na person without a warrant, a police officer . . . must . . . without unnecessary delay bring \n\nthe  arrested  person  or  cause  him  to  be  brought  before  a  local  criminal  court  and  file \n\ntherewith  an  appropriate  accusatory  instrument  charging  him  with  the  offense  or \n\noffenses in question.”) (emphasis added).  When a police officer arrests a person without \n\na warrant, the officer is constitutionally obliged to present the arrestee before a judicial \n\n\n 9 \n\fofficer for a determination of probable cause.  See Gerstein v. Pugh, 420 U.S. 103, 113‐14 \n\n(1975).  That is necessarily an obligation imposed on the officer, who has custody of the \n\narrested person, to prevent an extended unauthorized detention.  However, whether a \n\nprosecutor is performing a police function or acting as an advocate on behalf of the state \n\nwith  regard  to  a  detained  individual  “depends  in  part  on  whether  one  looks  at  the \n\nprosecutors’  discrete  actions,  or  at  their  role  and  function  in  an  ongoing  proceeding.”  \n\nWarney,  587  F.3d  at  123.    We  take  the  second  approach,  determining  the  prosecutor’s \n\nimmunity “chiefly on whether there is pending or in preparation a court proceeding in \n\nwhich  the  prosecutor  acts  as  an  advocate.”    Id.    Viewed  in  the  context  of  Ogunkoya’s \n\npending indictment and prosecution on multiple charges, a reasonable prosecutor would \n\nconclude that the ADAs’ function in controlling Ogunkoya’s arraignments on multiple \n\ndifferent charges that would later be subsumed in a single charging document was part \n\nof a prosecutor’s role as the gatekeeper of “whether and when to prosecute.”  Imbler, 424 \n\nU.S. at 431 n.33. \n\n  The analysis this Court undertook in Warney is helpful to our analysis here.  In \n\nWarney,  we  recognized  that  prosecutors  who  are  alleged  to  have  not  timely  disclosed \n\nexculpatory DNA evidence obtained during habeas proceedings are entitled to absolute \n\nimmunity.  Id. at 115–21, 125.  We concluded that classifying the steps that the prosecutors \n\ntook—testing and delaying disclosure of DNA evidence, and identifying the real killer—\n\nwas impossible “with[out] reference to context.”  Id. at 123.  Inculpatory results would \n\n\n 10 \n\faid advocacy; exculpatory results could give rise to an administrative burden to effect \n\ndisclosure; results inculpating another would support initiation of a new investigation.  \n\nWe held that regardless of the test results, all the steps that the Warney prosecutors took \n\n“were integral to and subsumed in the advocacy functions being performed in connection \n\nwith Warney’s post‐conviction initiatives.”  Id.  \n\n  Our decision in Warney follows the Supreme Court’s instruction in Van de Kamp v. \n\nGoldstein,  555  U.S.  335,  344  (2009),  that  absolute  immunity  covers  administrative  acts \n\n“directly connected with the conduct of a trial.”  The Court explained: \n\n [U]nlike  with  other  claims  related  to  administrative  decisions,  an \n individual  prosecutor’s  error  in  the  plaintiff’s  specific  criminal  trial \n constitutes an essential element of the plaintiff’s claim.  The administrative \n obligations at issue here are thus unlike administrative duties concerning, \n for example, workplace hiring, payroll administration, the maintenance of \n physical facilities, and the like.  Moreover, the types of activities on which \n Goldstein’s  claims  focus  necessarily  require  legal  knowledge  and  the \n exercise of related discretion, e.g., in determining what information should \n be  included  in  the  training  or  the  supervision  or  the  information‐system \n management.  And in that sense also Goldstein’s claims are unlike claims \n of, say, unlawful discrimination in hiring employees.  Given these features \n of the case before us, we believe absolute immunity must follow. \n  \nId.  In Warney, “[j]ust as the administrative act in Goldstein was integral to an advocacy \n\nfunction,” the potentially administrative or investigative acts “were also integral to the \n\noverarching advocacy function.”  587 F.3d at 124. \n\n  Here,  the  ADAs’  direction  that  Ogunkoya  not  be  arraigned  in  Greece  and \n\nIrondequoit  cannot  be  understood  without  reference  to  their  decision  to  proceed  by \n\ngrand jury indictment on the three sets of charges together. Viewed as a set of discrete \n 11 \n\facts,  the  ADAs’  interference  in  Ogunkoya’s  arraignments  in  Greece  and  Irondequoit \n\nostensibly hampered a police administrative function—presentation of the defendant as \n\nthe last stage of the police’s investigation and arrest.  See, e.g., Simon v. City of New York, \n\n727 F.3d 167, 172 (2d Cir. 2013) (“Investigation, arrest, and detention have historically and \n\nby precedent been regarded as the work of police, not prosecutors.”).  But that is not the \n\nlens through which to examine the prosecutor’s actions.  Rather, we view what occurred \n\nas the ADAs directing the NYSP on how to proceed with respect to a court proceeding \n\npending or in preparation “in which the prosecutor [is acting] as an advocate.”  Warney, \n\n587 F.3d at 123.  \n\n  The decision to initiate prosecution, what charges to bring, and how to perfect and \n\nconsolidate those charges is a quintessential prosecutorial function.  See Imbler, 424 U.S. \n\nat 431; Ying Jing Gan v. City of New York, 996 F.2d 522, 530 (2d Cir. 1993) (“A prosecutor \n\n. . . has absolute immunity in connection with the decision whether or not to commence \n\na prosecution.”).  The ADAs were not only participating in Ogunkoya’s arraignment on \n\nthe Henrietta charges but preparing to prosecute him on what they were informed were \n\nmultiple charges in two other towns as well.  Exercising their “related discretion,” the \n\nADAs decided to initiate prosecution of Ogunkoya in the two other towns, and ultimately \n\nto  pursue  all  three  sets  of  charges,  by  grand  jury  indictment  rather  than  have  three \n\nseparate criminal actions proceed under the six felony complaints.  Goldstein, 555 U.S. at \n\n\n\n\n 12 \n\f344.  The ADAs directed that Ogunkoya’s arraignment in Greece and Henrietta not occur \n\nin order to control how the state’s criminal case would proceed.   \n\n  So,  while  the  District  Court  was  correct  that  in  New  York  state  arraignment  is \n\ngenerally a police function, its analysis failed to consider that a court proceeding was in \n\npreparation,  Warney,  587  F.3d  at  123,  and  that  the  ADAs’  participation  in  the  act  of \n\nscheduling arraignments on the multiple charges that were to be consolidated in a single \n\nindictment  was  “directly  connected  with  the  conduct  of  a  trial”  and  “require[d]  legal \n\nknowledge and the exercise of related discretion.”  Goldstein, 555 U.S. at 344.  As the ADA \n\nexplained in his email to Ogunkoya’s counsel, Ogunkoya had already been arraigned on \n\nthe Henrietta charges and was being detained on that basis.  Further arraignments on the \n\nGreece  and  Irondequoit  charges  were  not  necessary  for  him  to  continue  to  be  held \n\npursuant to the Henrietta arraignment and on terms set by the Henrietta court.2  As their \n\n\n\n\n2 Ogunkoya complains about ADA Egan’s argument to the Henrietta court that bail on the \nHenrietta charge should be set at a rate that reflected the pendency of the Greece and \nIrondequoit felony complaints, on which he had not been arraigned, in addition to the Henrietta \ncomplaints.  He further asserts that the bail bondsman did not want to post bail “because of the \npossibility that as soon as he was released [he] would be arrested on the four counts on which \nhe had not [been] arraigned.”  J. App. 13.  He cites documents not in the record assertedly \nshowing that he “was arrested on the Greece charges as well as the Henrietta charges.” On this \nbasis, he argues that the ADAs and the other New York state defendants violated his \nconstitutional rights by failing to “intervene and prevent his extended detention.”  J. App. 17.  \nAlthough the sequence of events is regrettable, these facts do not alter our analysis regarding \nthe prosecutors’ entitlement to absolute immunity in light of their exercise of prosecutorial \nfunctions in determining to arraign Ogunkoya only on the Henrietta charge, and to await a \ngrand jury’s indictment on the charges pertaining to events in all three towns. \n 13 \n\frole with respect to the arraignments was prosecutorial, the ADAs are thus entitled to \n\nabsolute immunity. \n\n    Nor does our decision in Simon, on which the District Court relied, mandate a \n\ndifferent result.  727 F.3d 167.  In Simon, we held that a prosecutor who used a material \n\nwitness warrant to detain a witness for questioning, instead of allowing officers to fulfill \n\nthe  warrant  by  bringing  the  witness  before  the  court,  was  not  entitled  to  absolute \n\nimmunity.  Id. at 169–70.  We reasoned that arrest and detention are historically police \n\nfunctions  and  that  New  York  law  explicitly  entrusts  the  execution  of  material  witness \n\nwarrants to police officers.  Id. at 172–73.   \n\n  Simon  was  not  detained  for  a  trial,  but  merely  held  in  the  course  of  a  criminal \n\ninvestigation, for which no judicial proceedings were scheduled.  Simon, 727 F.3d at 169, \n\n174.  The prosecutor’s acts were not “subsumed [with]in the advocacy function” related \n\nto a pending court proceeding in the nature of  a criminal prosecution.  Warney, 587 F.3d \n\nat 123.  We noted as much at the time.  Simon, 727 F.3d at 174 (explaining, “[t]hat Simon \n\nmight eventually have been called to testify in a judicial proceeding does not make her \n\ndetention a prosecutorial function”) (citing Buckley v. Fitzsimmons, 509 U.S. 259, 275–76 \n\n(1993)).    It  was  clear,  given  the  context  and  timing  of  the  Simon  prosecutor’s  acts  in \n\nquestion, that the prosecutor was involved in an investigation, not in advocacy related to \n\nthe initiation and prosecution of criminal charges.  Id.  Indeed, as we pointed out there, \n\nthe  prosecutor  in  Simon  was  “actively  avoiding  the  court‐ordered  material  witness \n\n\n 14 \n\fhearing”; his acts ensured that the plaintiff “had no way of contesting her detention.”  Id. \n\nat 173.  In this case, in contrast, it is immaterial that the ADAs may have interfered with \n\na police function because the overarching reason for their directing the arraignments in \n\ntown  courts  to  not  occur  was  not  related  to  Ogunkoya’s  warrantless  arrest,  but  rather \n\nconstituted an exercise of their prosecutorial discretion in preparing a case for indictment \n\nand deciding when, where, and how to prosecute.  The separation of the two functions is \n\nhighlighted further by the observation that once his bond documents for the Henrietta \n\ncharge alone were signed, he was released, despite his still not having been arraigned on \n\nthe  Greece  and  Irondequoit  charges.    For  these  reasons,  we  hold  that  the  ADAs  have \n\nabsolute immunity and the claims against them must be dismissed.  \n\n IV. \n\n  Monroe County appeals from the District Court’s denial of its motion to dismiss \n\nOgunkoya’s Monell municipal liability and failure‐to‐train claims.  Although the order \n\ndenying  absolute  immunity  is  “immediately  appealable  under  the  collateral  order \n\ndoctrine,”  Shmueli,  424  F.3d  at  236,  pendent  appellate  jurisdiction  is  only  appropriate \n\nwhere an issue is “inextricably intertwined” with the other issues on appeal giving rise \n\nto the appellate court’s jurisdiction or is necessary to ensure “meaningful review” of those \n\nissues.  Warney, 587 F.3d at 126 (internal quotation marks omitted).  Our decision here is \n\nguided, if not mandated, by the previous decision of this Court in Warney.  There we held:  \n\n Unlike the order denying immunity, the order denying Monroe County’s \n motion to dismiss is not immediately appealable pursuant to the collateral \n 15 \n\f order doctrine. . . . The elements of a Monell claim, and the extent to which \n prosecutors in New York are agents of the state (as opposed to a county) \n are  not  inextricably  intertwined  with  the  question  of  absolute  immunity.  \n We therefore decline to exercise pendent appellate jurisdiction over these \n issues at this time.   \n  \nId.;  cf.  Askins  v.  Doe  No.  1,  727  F.3d  248,  253  (2d  Cir.  2013)  (holding  that  an  arresting \n\nofficer’s liability is irrelevant to liability of municipality).  For these same reasons we hold \n\nthat the County’s appeal is premature and one over which we lack appellate jurisdiction. \n\n V. \n\n For  the  foregoing  reasons,  the  order  of  the  District  Court  insofar  as  it  denied \n\nabsolute  immunity  to  the  ADAs  is  reversed,  and  this  case  is  remanded  for  further \n\nproceedings  consistent  with  this  opinion.3    The  appeal  filed  by  Monroe  County  is \n\ndismissed. \n\n\n\n\n3 Ogunkoya’s lawsuit against the remaining defendants will proceed in the District Court.  We \nexpress no views as to the merits of those claims. \n 16", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357134/", "author_raw": "PETER W. HALL, Circuit Judge:"}]}
HALL
LYNCH
CARNEY
1
{"HALL": ", Circuit", "LYNCH": ", Circuit", "CARNEY": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579881/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Ogunkoya v. Drake\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17-3235\nOgunkoya v. Drake\n\n\n In the\n United States Court of Appeals\n For the Second Circuit\n\n August Term, 2018 \n  \n Argued: September 27, 2018 \n Decided: January 9, 2019 \n  \n Docket No. 17‐3235‐cv \n  \n  \n SEUN OGUNKOYA, \n  \n Plaintiff‐Appellee, \n   \n v. \n  \n MARK MONAGHAN, JAMES EGAN, COUNTY OF MONROE,  \n  \n Defendants‐Appellants, \n  \n SANDRA DOORLEY, ALBERT DRAKE III, INVESTIGATOR, DARIUSZ ZYSK, \nINVESTIGATOR, PETER SCHRAGE, TROOPER, MARK EIFERT, INVESTIGATOR, JOHN DOE, \n RICHARD ROE, \n  \n Defendants. \n  \n  \n\n\n\n  The Clerk of Court is respectfully requested to amend the official caption as set forth above.   \n 1 \n\f Appeal from the United States District Court \n for the Eastern District of New York \n No. 15‐CV‐06119, Matsumoto, Judge. \n  \n  \nBefore:  HALL, LYNCH, and CARNEY, Circuit Judges. \n\n \nThis  appeal  arises  out  of  Plaintiff‐Appellee  Seun  Ogunkoya’s  §  1983  lawsuit  alleging \nconstitutional violations during his warrantless arrest and subsequent prosecution.  He \nwas acquitted of all charges.  Two Monroe County Assistant District Attorneys appeal \nthe District Court’s denial of their Rule 12(b)(6) motion to dismiss on the ground that they \nhave absolute immunity for the violations alleged.  We hold that the Assistant District \nAttorneys have absolute immunity from suit and thus reverse the decision of the District \nCourt  with  respect  to  claims  against  these  prosecutors  in  their  individual  capacities.  \nMonroe  County  also  appeals  the  District  Court’s  denial  of  its  Rule  12(b)(6)  motion \narguing that municipal liability is not warranted because the county prosecutors were \nstate, not county, actors.  Because the elements of the claim against the county are not \ninextricably  intertwined  with  the  question  of  absolute  immunity,  we  are  without \nappellate jurisdiction to hear the county’s interlocutory appeal.  \n \n  REVERSED IN PART; DISMISSED IN PART; AND REMANDED. \n \n MATTHEW  D.  BROWN,  for  Michael  E.  Davis,  County \n Attorney, Monroe County, New York, for  Defendants‐\n Appellants. \n  \n DANIEL M. WHITE, Milbank, Tweed, Hadley & McCloy, \n LLP,  New  York,  NY  (Alexandra  Wang,  Max  Kelly, \n Milbank, Tweed, Hadley & McCloy, LLP, New York, \n New York, on the brief) for Plaintiff‐Appellee. \n  \n \nPETER W. HALL, Circuit Judge: \n\n This appeal principally concerns whether two Monroe County Assistant District \n\nAttorneys, James Egan and Mark Monaghan (“the ADAs”), are absolutely immune from \n\n\n\n 2 \n\fcivil  suit  for  interfering  in  the  timing  of  Plaintiff‐Appellee  Seun  Ogunkoya’s \n\narraignments in several town courts as the ADAs were preparing to present the charges \n\nto  a  grand  jury.  Ogunkoya  alleged  that the  ADAs, along  with  other  state  and county \n\ndefendants, violated his Fourth and Fourteenth Amendment rights by failing to timely \n\narraign him on four of six identity fraud and larceny charges.  Because the ADAs were \n\nperforming a traditional prosecutorial function when they determined that they would \n\ninitiate  Ogunkoya’s  prosecution  via  grand  jury  indictment  and  thus  delay  his \n\narraignment  on  separate  individual  charges,  we  reverse  the  District  Court’s  denial  of \n\nabsolute immunity.   \n\n Regarding Monroe County’s effort to appeal the denial of its motion to dismiss, \n\nbecause the claims against the county are not inextricably intertwined with the question \n\nof the ADAs’ immunity, we are without jurisdiction to consider the County’s appeal at \n\nthis time.   \n\n I. \n\n Absolute  immunity  protects  a  prosecutor  “not  only  from  liability  but  also  from \n\nsuit.”    Shmueli  v.  City  of  New  York,  424  F.3d  231,  236  (2d  Cir.  2005).    “Hence,  an \n\ninterlocutory  order  rejecting  the  defense  [of  absolute  immunity]  is  immediately \n\nappealable under the collateral order doctrine.”  Id.  \n\n “When a district court denies immunity on a Rule 12(b)(6) motion to dismiss, ‘we \n\nreview the district court’s denial de novo, accepting as true the material facts alleged in \n\n\n 3 \n\fthe  complaint  and  drawing  all  reasonable  inferences  in  plaintiffs’  favor.’”    Warney  v. \n\nMonroe Cty., 587 F.3d 113, 120 (2d Cir. 2009) (quoting Johnson v. Newburgh Enlarged Sch. \n\nDist., 239 F.3d 246, 250 (2d Cir. 2001)). \n\n II. \n\n  The  facts  as alleged in Ogunkoya’s  complaint are as  follows.  The  investigation \n\nleading  to  his  arrest  began  when  Home  Depot  reported  several  gift  card  purchases \n\nsuspected to be fraudulent to the New York State Police (“NYSP”).  The gift cards, totaling \n\n$28,000,  were  all  acquired  on  April  26,  2014,  at  Home  Depot  stores  in  three  Monroe \n\nCounty  towns—Greece,  Henrietta,  and  Irondequoit.    NYSP  Investigator  Mark  Eifert \n\nopened a criminal investigation and learned that Ogunkoya used his personal credit card \n\nfor small purchases in the Greece and Henrietta stores around the same time as the gift \n\ncards  were  purchased.    Eifert  also  reviewed  Home  Depot’s  surveillance  tapes.    Those \n\ntapes  show  someone  other  than  Ogunkoya  purchasing  the  gift  cards.    On  January  20, \n\n2015, Eifert prepared six felony complaints charging Ogunkoya with one count of identity \n\ntheft and one count of grand larceny in each of the three towns.  \n\n  A  month  later,  acting  on  Eifert’s  knowledge  and  belief,  but  without  an  arrest \n\nwarrant, the NYSP arrested Ogunkoya in his Brooklyn apartment.  Over the course of the \n\nday,  NYSP  officers  drove  Ogunkoya  to  Monroe  County,  where  he  was  brought  for \n\narraignment  before  the  Henrietta  Town  Court  around  10  P.M.    The  NYSP  filed  all  six \n\nfelony  complaints  with  the  Henrietta  court,  but  the  judge  refused  on  jurisdictional \n\n\n 4 \n\fgrounds to arraign Ogunkoya on the four complaints based on conduct alleged to have \n\noccurred in Greece and Irondequoit.  The judge instructed the NYSP to have Ogunkoya \n\narraigned on the remaining complaints during the next business day, Monday, February \n\n23, 2015.     \n\n  Ogunkoya was never arraigned in Greece or Irondequoit.  Instead, a bail hearing \n\nwas held that Monday in Monroe County Court.  At the hearing, Ogunkoya, who was \n\nplanning to sit for the bar exam in New York City the following day, asked to be arraigned \n\non the four remaining complaints “in time for a new bail application to be made on all \n\nthe charges.”  J. App. 11.  Considering Ogunkoya a “flight risk,” the ADAs argued for a \n\n$100,000  cash/$300,000  bond  bail  “based  on  the  combined  allegations  of  the  six  felony \n\ncomplaints.”    Id.    The  judge  set  Ogunkoya’s  bail  at  $100,000  cash/$300,000  bond.    As \n\nalleged by Ogunkoya, “[t]his amount of bail is unusually high considering the amount of \n\nthe alleged thefts [] and local custom.”  Id.   \n\n  Ogunkoya’s  family  then  sought  to  arrange  for  bail,  but  the  bail  bondsman \n\n“expressed  reluctance  at  posting  a  bond”  because  of  Ogunkoya’s  four  outstanding \n\ncriminal complaints on which he had not yet been arraigned.  J. App. 12.  Ogunkoya’s \n\ncounsel wrote to ADA Egan and again requested that Ogunkoya be arraigned on the four \n\noutstanding complaints so that he could secure bail.  Egan responded by email: \n\n There is no need to ever arraign him on the charges in the local court.  He \n was arrested on the Henrietta charges and received his prompt arraignment \n on them as required by the CPL.  The purpose of CPL 140.20 is to ensure a \n person who is arrested gets a prompt arraignment and doesn’t have to sit \n 5 \n\f in jail waiting for bail to be set.  The other charges are essentially “sealed” \n charges  since  he  has  never  been  arrested  or  arraigned  on  them.    In  any \n event, they were all referred to the grand jury and they will be presented \n together.    This  is  done  frequently  in  cases  involving  charges  in  multiple \n jurisdictions. \n  \nId. \n\n  Ogunkoya’s  counsel  continued  to  press  for  arraignment,  seeking  a  writ  on  the \n\nground that “Ogunkoya was prepared to post a $300,000 bond but that the bail bondsman \n\nrefused  to  post  the  bond  solely  because  of  the  unarraigned  charges.”    J.  App.  13.    On \n\nMarch 20th—28  days  after  his arrest—Ogunkoya was released after  a Monroe  County \n\nCourt judge signed his bond documents.  On or about May 15, 2015, a Monroe County \n\ngrand  jury  indicted  Ogunkoya  on  three  counts  of  identity  theft,  one  count  from  each \n\ntown.  At trial, the jury acquitted Ogunkoya on all charges.   \n\n  After  his  acquittal  Ogunkoya,  pro  se,  filed  a  §  1983  lawsuit  naming  the  NYSP \n\nofficers  involved  in  his  arrest,  Monroe  County  DA  Sandra  Doorley,1  Monroe  County \n\nADAs  Monaghan  and  Egan,  and  Monroe  County  itself.    Ogunkoya  amended  his \n\ncomplaint twice, with pro bono counsel filing the second amended complaint.  Both the \n\nNYSP and Monroe County defendants moved to dismiss under Fed. R. Civ. P. 12(b)(6) \n\n\n\n\n1 Monroe County District Attorney Sandra Doorley was incorrectly sued in her individual \ncapacity as Susan Doorley.  Although the briefs list Doorley as an appellant, the District Court \nadopted the magistrate judge’s recommendation that all claims against her be dismissed.  \nAccordingly, nothing remains pending against her at this time, and she has no stake in the \ninstant appeal. \n 6 \n\farguing that Ogungoya’s complaint failed to state a claim and that the prosecutors had \n\nabsolute immunity.  The fully briefed motions were referred to the magistrate judge.  \n\n  The  magistrate  judge’s  Report  and  Recommendation  (“R&R”)  construed  the \n\nsecond amended complaint to plead the following claims against all the individual NYSP \n\nand  Monroe  County  defendants:  false  arrest  and  false  imprisonment,  malicious \n\nprosecution, failure to arraign, and related claims for failure to intervene with respect to \n\neach of the preceding claims.  The R&R also construed Ogunkoya’s complaint to assert a \n\nMonell  municipal  liability  claim  against  Monroe  County,  alleging  an  unconstitutional \n\npractice or custom and failure to train its officers.  The magistrate judge recommended \n\nthat all claims against the NYSP defendants proceed except the claims alleging malicious \n\nprosecution,  failure  to  intervene  in  plaintiff’s  prosecution,  and  failure  to  intervene  in \n\nplaintiff’s arraignment on the part of the arresting officers in Brooklyn.  \n\n  With respect to the ADAs, the magistrate judge recommended that the false arrest, \n\nmalicious  prosecution,  and  related  failure  to  intervene  claims  be  dismissed.    The \n\nmagistrate judge recommended that the failure to arraign and related failure to intervene \n\nclaims proceed against the ADAs.  In so doing, the magistrate judge ruled that the ADAs \n\nwere  not  entitled  to  absolute  immunity  for  their  roles  in  the  events  underlying \n\nOgunkoya’s failure to arraign claims.   \n\n  In addition, the magistrate judge recommended that all claims against DA Doorley \n\nbe  dismissed  because  she  lacked  personal  involvement  or  had  absolute  immunity.    \n\n\n 7 \n\fFinally,  the  magistrate  judge  recommended  that  the  municipal  liability  claim  against \n\nMonroe County also proceed because Ogunkoya had plausibly pled a Monell violation \n\nrequiring the resolution of factual questions.   \n\n  The district judge adopted the R&R.  This appeal followed.   \n\n III. \n\n  Absolute immunity bars § 1983 suits against prosecutors for their role “in initiating \n\na prosecution and in presenting the State’s case.”  Imbler v. Pachtman, 424 U.S. 409, 431 \n\n(1976).  Instead of relying on strict categories of actions with respect to which absolute \n\nimmunity attaches, the relevant question is “whether there is pending or in preparation \n\na court proceeding in which the prosecutor acts as an advocate.”  Warney, 587 F.3d at 123.  \n\nUltimately, we ask “whether a reasonable prosecutor would view the acts challenged by \n\nthe complaint as reasonably within the functions of a prosecutor.”  Giraldo v. Kessler, 694 \n\nF.3d 161, 166 (2d Cir. 2012).  \n\n  The ADAs’ decision to prosecute Ogunkoya and proceed by grand jury indictment \n\nrather  than  proceed  on  separate  criminal  complaints  is  a  prosecutorial  exercise  of \n\ndiscretion  entitled  to  absolute  immunity.    See  Burns  v.  Reed,  500  U.S.  478,  486  (1991) \n\n(quoting Imbler, 424 U.S. at 430–31) (holding that “[p]rosecutors are absolutely immune \n\n. . . for their conduct in ‘initiating a prosecution’”).  What we must decide is whether the \n\nADAs  are  entitled  to  absolute  immunity  when  they  directed  the  NYSP  not  to  have \n\n\n\n\n 8 \n\fOgunkoya  arraigned  in  the  Greece  and  Irondequoit  town  courts  and  informed  those \n\ncourts that Ogunkoya would not be arraigned.  \n\n  In our view, the Supreme Court’s pronouncement in Imbler squarely addresses the \n\nconduct of the ADAs at issue here.  424 U.S. at 430–31.  The Court noted: \n\n We recognize that the duties of the prosecutor in his role as advocate for the \n State  involve  actions  preliminary  to  the  initiation  of  a  prosecution  and \n actions  apart  from  the  courtroom.    A  prosecuting  attorney  is  required \n constantly, in the course of his duty as such, to make decisions on a wide \n variety of sensitive issues.  These include questions of whether to present a \n case  to  a  grand  jury,  whether  to  file  an  information,  [and]  whether  and \n when to prosecute. . . . \n  \nId. at 431 n.33. \n\n  The District Court erred in denying the ADAs absolute immunity.  The District \n\nCourt  found  that  “’a  reasonable  prosecutor’  would  conclude  that  the  Greece  and \n\nIrondequoit arraignments were a police, not a prosecutorial, responsibility.”  J. App. 113.  \n\nWe disagree.  It is true that, in New York, the responsibility for presenting a detained \n\nperson before a court for evaluation of the legality of his or her detention is generally a \n\npolice responsibility.  See N.Y. Crim. Proc. Law § 140.20(1) (McKinney) (“Upon arresting \n\na person without a warrant, a police officer . . . must . . . without unnecessary delay bring \n\nthe  arrested  person  or  cause  him  to  be  brought  before  a  local  criminal  court  and  file \n\ntherewith  an  appropriate  accusatory  instrument  charging  him  with  the  offense  or \n\noffenses in question.”) (emphasis added).  When a police officer arrests a person without \n\na warrant, the officer is constitutionally obliged to present the arrestee before a judicial \n\n\n 9 \n\fofficer for a determination of probable cause.  See Gerstein v. Pugh, 420 U.S. 103, 113‐14 \n\n(1975).  That is necessarily an obligation imposed on the officer, who has custody of the \n\narrested person, to prevent an extended unauthorized detention.  However, whether a \n\nprosecutor is performing a police function or acting as an advocate on behalf of the state \n\nwith  regard  to  a  detained  individual  “depends  in  part  on  whether  one  looks  at  the \n\nprosecutors’  discrete  actions,  or  at  their  role  and  function  in  an  ongoing  proceeding.”  \n\nWarney,  587  F.3d  at  123.    We  take  the  second  approach,  determining  the  prosecutor’s \n\nimmunity “chiefly on whether there is pending or in preparation a court proceeding in \n\nwhich  the  prosecutor  acts  as  an  advocate.”    Id.    Viewed  in  the  context  of  Ogunkoya’s \n\npending indictment and prosecution on multiple charges, a reasonable prosecutor would \n\nconclude that the ADAs’ function in controlling Ogunkoya’s arraignments on multiple \n\ndifferent charges that would later be subsumed in a single charging document was part \n\nof a prosecutor’s role as the gatekeeper of “whether and when to prosecute.”  Imbler, 424 \n\nU.S. at 431 n.33. \n\n  The analysis this Court undertook in Warney is helpful to our analysis here.  In \n\nWarney,  we  recognized  that  prosecutors  who  are  alleged  to  have  not  timely  disclosed \n\nexculpatory DNA evidence obtained during habeas proceedings are entitled to absolute \n\nimmunity.  Id. at 115–21, 125.  We concluded that classifying the steps that the prosecutors \n\ntook—testing and delaying disclosure of DNA evidence, and identifying the real killer—\n\nwas impossible “with[out] reference to context.”  Id. at 123.  Inculpatory results would \n\n\n 10 \n\faid advocacy; exculpatory results could give rise to an administrative burden to effect \n\ndisclosure; results inculpating another would support initiation of a new investigation.  \n\nWe held that regardless of the test results, all the steps that the Warney prosecutors took \n\n“were integral to and subsumed in the advocacy functions being performed in connection \n\nwith Warney’s post‐conviction initiatives.”  Id.  \n\n  Our decision in Warney follows the Supreme Court’s instruction in Van de Kamp v. \n\nGoldstein,  555  U.S.  335,  344  (2009),  that  absolute  immunity  covers  administrative  acts \n\n“directly connected with the conduct of a trial.”  The Court explained: \n\n [U]nlike  with  other  claims  related  to  administrative  decisions,  an \n individual  prosecutor’s  error  in  the  plaintiff’s  specific  criminal  trial \n constitutes an essential element of the plaintiff’s claim.  The administrative \n obligations at issue here are thus unlike administrative duties concerning, \n for example, workplace hiring, payroll administration, the maintenance of \n physical facilities, and the like.  Moreover, the types of activities on which \n Goldstein’s  claims  focus  necessarily  require  legal  knowledge  and  the \n exercise of related discretion, e.g., in determining what information should \n be  included  in  the  training  or  the  supervision  or  the  information‐system \n management.  And in that sense also Goldstein’s claims are unlike claims \n of, say, unlawful discrimination in hiring employees.  Given these features \n of the case before us, we believe absolute immunity must follow. \n  \nId.  In Warney, “[j]ust as the administrative act in Goldstein was integral to an advocacy \n\nfunction,” the potentially administrative or investigative acts “were also integral to the \n\noverarching advocacy function.”  587 F.3d at 124. \n\n  Here,  the  ADAs’  direction  that  Ogunkoya  not  be  arraigned  in  Greece  and \n\nIrondequoit  cannot  be  understood  without  reference  to  their  decision  to  proceed  by \n\ngrand jury indictment on the three sets of charges together. Viewed as a set of discrete \n 11 \n\facts,  the  ADAs’  interference  in  Ogunkoya’s  arraignments  in  Greece  and  Irondequoit \n\nostensibly hampered a police administrative function—presentation of the defendant as \n\nthe last stage of the police’s investigation and arrest.  See, e.g., Simon v. City of New York, \n\n727 F.3d 167, 172 (2d Cir. 2013) (“Investigation, arrest, and detention have historically and \n\nby precedent been regarded as the work of police, not prosecutors.”).  But that is not the \n\nlens through which to examine the prosecutor’s actions.  Rather, we view what occurred \n\nas the ADAs directing the NYSP on how to proceed with respect to a court proceeding \n\npending or in preparation “in which the prosecutor [is acting] as an advocate.”  Warney, \n\n587 F.3d at 123.  \n\n  The decision to initiate prosecution, what charges to bring, and how to perfect and \n\nconsolidate those charges is a quintessential prosecutorial function.  See Imbler, 424 U.S. \n\nat 431; Ying Jing Gan v. City of New York, 996 F.2d 522, 530 (2d Cir. 1993) (“A prosecutor \n\n. . . has absolute immunity in connection with the decision whether or not to commence \n\na prosecution.”).  The ADAs were not only participating in Ogunkoya’s arraignment on \n\nthe Henrietta charges but preparing to prosecute him on what they were informed were \n\nmultiple charges in two other towns as well.  Exercising their “related discretion,” the \n\nADAs decided to initiate prosecution of Ogunkoya in the two other towns, and ultimately \n\nto  pursue  all  three  sets  of  charges,  by  grand  jury  indictment  rather  than  have  three \n\nseparate criminal actions proceed under the six felony complaints.  Goldstein, 555 U.S. at \n\n\n\n\n 12 \n\f344.  The ADAs directed that Ogunkoya’s arraignment in Greece and Henrietta not occur \n\nin order to control how the state’s criminal case would proceed.   \n\n  So,  while  the  District  Court  was  correct  that  in  New  York  state  arraignment  is \n\ngenerally a police function, its analysis failed to consider that a court proceeding was in \n\npreparation,  Warney,  587  F.3d  at  123,  and  that  the  ADAs’  participation  in  the  act  of \n\nscheduling arraignments on the multiple charges that were to be consolidated in a single \n\nindictment  was  “directly  connected  with  the  conduct  of  a  trial”  and  “require[d]  legal \n\nknowledge and the exercise of related discretion.”  Goldstein, 555 U.S. at 344.  As the ADA \n\nexplained in his email to Ogunkoya’s counsel, Ogunkoya had already been arraigned on \n\nthe Henrietta charges and was being detained on that basis.  Further arraignments on the \n\nGreece  and  Irondequoit  charges  were  not  necessary  for  him  to  continue  to  be  held \n\npursuant to the Henrietta arraignment and on terms set by the Henrietta court.2  As their \n\n\n\n\n2 Ogunkoya complains about ADA Egan’s argument to the Henrietta court that bail on the \nHenrietta charge should be set at a rate that reflected the pendency of the Greece and \nIrondequoit felony complaints, on which he had not been arraigned, in addition to the Henrietta \ncomplaints.  He further asserts that the bail bondsman did not want to post bail “because of the \npossibility that as soon as he was released [he] would be arrested on the four counts on which \nhe had not [been] arraigned.”  J. App. 13.  He cites documents not in the record assertedly \nshowing that he “was arrested on the Greece charges as well as the Henrietta charges.” On this \nbasis, he argues that the ADAs and the other New York state defendants violated his \nconstitutional rights by failing to “intervene and prevent his extended detention.”  J. App. 17.  \nAlthough the sequence of events is regrettable, these facts do not alter our analysis regarding \nthe prosecutors’ entitlement to absolute immunity in light of their exercise of prosecutorial \nfunctions in determining to arraign Ogunkoya only on the Henrietta charge, and to await a \ngrand jury’s indictment on the charges pertaining to events in all three towns. \n 13 \n\frole with respect to the arraignments was prosecutorial, the ADAs are thus entitled to \n\nabsolute immunity. \n\n    Nor does our decision in Simon, on which the District Court relied, mandate a \n\ndifferent result.  727 F.3d 167.  In Simon, we held that a prosecutor who used a material \n\nwitness warrant to detain a witness for questioning, instead of allowing officers to fulfill \n\nthe  warrant  by  bringing  the  witness  before  the  court,  was  not  entitled  to  absolute \n\nimmunity.  Id. at 169–70.  We reasoned that arrest and detention are historically police \n\nfunctions  and  that  New  York  law  explicitly  entrusts  the  execution  of  material  witness \n\nwarrants to police officers.  Id. at 172–73.   \n\n  Simon  was  not  detained  for  a  trial,  but  merely  held  in  the  course  of  a  criminal \n\ninvestigation, for which no judicial proceedings were scheduled.  Simon, 727 F.3d at 169, \n\n174.  The prosecutor’s acts were not “subsumed [with]in the advocacy function” related \n\nto a pending court proceeding in the nature of  a criminal prosecution.  Warney, 587 F.3d \n\nat 123.  We noted as much at the time.  Simon, 727 F.3d at 174 (explaining, “[t]hat Simon \n\nmight eventually have been called to testify in a judicial proceeding does not make her \n\ndetention a prosecutorial function”) (citing Buckley v. Fitzsimmons, 509 U.S. 259, 275–76 \n\n(1993)).    It  was  clear,  given  the  context  and  timing  of  the  Simon  prosecutor’s  acts  in \n\nquestion, that the prosecutor was involved in an investigation, not in advocacy related to \n\nthe initiation and prosecution of criminal charges.  Id.  Indeed, as we pointed out there, \n\nthe  prosecutor  in  Simon  was  “actively  avoiding  the  court‐ordered  material  witness \n\n\n 14 \n\fhearing”; his acts ensured that the plaintiff “had no way of contesting her detention.”  Id. \n\nat 173.  In this case, in contrast, it is immaterial that the ADAs may have interfered with \n\na police function because the overarching reason for their directing the arraignments in \n\ntown  courts  to  not  occur  was  not  related  to  Ogunkoya’s  warrantless  arrest,  but  rather \n\nconstituted an exercise of their prosecutorial discretion in preparing a case for indictment \n\nand deciding when, where, and how to prosecute.  The separation of the two functions is \n\nhighlighted further by the observation that once his bond documents for the Henrietta \n\ncharge alone were signed, he was released, despite his still not having been arraigned on \n\nthe  Greece  and  Irondequoit  charges.    For  these  reasons,  we  hold  that  the  ADAs  have \n\nabsolute immunity and the claims against them must be dismissed.  \n\n IV. \n\n  Monroe County appeals from the District Court’s denial of its motion to dismiss \n\nOgunkoya’s Monell municipal liability and failure‐to‐train claims.  Although the order \n\ndenying  absolute  immunity  is  “immediately  appealable  under  the  collateral  order \n\ndoctrine,”  Shmueli,  424  F.3d  at  236,  pendent  appellate  jurisdiction  is  only  appropriate \n\nwhere an issue is “inextricably intertwined” with the other issues on appeal giving rise \n\nto the appellate court’s jurisdiction or is necessary to ensure “meaningful review” of those \n\nissues.  Warney, 587 F.3d at 126 (internal quotation marks omitted).  Our decision here is \n\nguided, if not mandated, by the previous decision of this Court in Warney.  There we held:  \n\n Unlike the order denying immunity, the order denying Monroe County’s \n motion to dismiss is not immediately appealable pursuant to the collateral \n 15 \n\f order doctrine. . . . The elements of a Monell claim, and the extent to which \n prosecutors in New York are agents of the state (as opposed to a county) \n are  not  inextricably  intertwined  with  the  question  of  absolute  immunity.  \n We therefore decline to exercise pendent appellate jurisdiction over these \n issues at this time.   \n  \nId.;  cf.  Askins  v.  Doe  No.  1,  727  F.3d  248,  253  (2d  Cir.  2013)  (holding  that  an  arresting \n\nofficer’s liability is irrelevant to liability of municipality).  For these same reasons we hold \n\nthat the County’s appeal is premature and one over which we lack appellate jurisdiction. \n\n V. \n\n For  the  foregoing  reasons,  the  order  of  the  District  Court  insofar  as  it  denied \n\nabsolute  immunity  to  the  ADAs  is  reversed,  and  this  case  is  remanded  for  further \n\nproceedings  consistent  with  this  opinion.3    The  appeal  filed  by  Monroe  County  is \n\ndismissed. \n\n\n\n\n3 Ogunkoya’s lawsuit against the remaining defendants will proceed in the District Court.  We \nexpress no views as to the merits of those claims. \n 16\n[END_CASE]", "role": "user" } ]
8,443,838
Seun OGUNKOYA v. Mark MONAGHAN, James Egan, County of Monroe, Sandra Doorley, Albert Drake III, Investigator, Dariusz Zysk, Investigator, Peter Schrage, Trooper, Mark Eifert, Investigator, John Doe, Richard Roe
Ogunkoya v. Monaghan
2019-01-09
Docket No. 17-3235-cv; August Term, 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Carney, Hall, Lynch", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415264/", "author_raw": ""}]}
CARNEY
HALL
LYNCH
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443838/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Seun OGUNKOYA v. Mark MONAGHAN, James Egan, County of Monroe, Sandra Doorley, Albert Drake III, Investigator, Dariusz Zysk, Investigator, Peter Schrage, Trooper, Mark Eifert, Investigator, John Doe, Richard Roe\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
8,443,842
The PACA TRUST CREDITORS OF LENNY PERRY'S PRODUCE, INC., Plaintiffs-Appellees-Cross-Appellants v. GENECCO PRODUCE INC., David Genecco, Defendants-Appellants-Cross-Appellees.
Paca Trust Creditors of Lenny Perry's Produce, Inc. v. Genecco Produce Inc.
2019-01-09
Docket Nos. 17-1949-cv; 17-2051-cv; August Term, 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Chin, Raggi, Sack", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415268/", "author_raw": ""}]}
CHIN
RAGGI
SACK
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443842/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: The PACA TRUST CREDITORS OF LENNY PERRY'S PRODUCE, INC., Plaintiffs-Appellees-Cross-Appellants v. GENECCO PRODUCE INC., David Genecco, Defendants-Appellants-Cross-Appellees.\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,580,406
States Court of Appeals
2019-01-10
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges.", "parties": "", "opinions": [{"author": "ROBERT A. KATZMANN, Chief Judge", "type": "010combined", "text": "United States Court of Appeals\n for the Second Circuit\n _______________ \n\n AUGUST TERM, 2018 \n  \n (Argued: October 22, 2018               Decided: January 10, 2019) \n  \n Docket No. 17‐3355 \n  \n _______________ \n  \n UNITED STATES OF AMERICA, \n Appellee, \n  \n —v.— \n\n Tibor Klein, \n Defendant, \n  \n ROBERT SCHULMAN, \n Defendant‐Appellant. \n _______________ \n  \n Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges. \n\n _______________ \n  \n Defendant‐appellant Robert Schulman appeals from an October 4, 2017 \njudgment convicting him, following a jury trial, of one count of conspiracy to \ncommit securities fraud and one count of securities fraud. On appeal, Schulman \nargues that the district court erroneously denied his motion pursuant to Federal \nRule of Criminal Procedure 29 to vacate his convictions. According to Schulman, \n\n\n\n 1 \n \n\f \nhis convictions cannot stand because the government adduced insufficient \nevidence at trial of his criminal intent. Because the jury was not required to credit \nSchulman’s deposition testimony that he intended only to brag when he tipped \nhis friend and financial advisor about an upcoming merger, and the evidence \ntaken as a whole permitted the jury to find beyond a reasonable doubt that \nSchulman intended his communication to lead to trading in securities of the \ncompany in question, we disagree. Accordingly, we AFFIRM the judgment of \nthe district court. \n _______________ \n\n MARK D. HARRIS (John E. Roberts, on the brief), Proskauer Rose LLP,  \n New York, New York, for Defendant‐Appellant. \n  \n DAVID C. PITLUCK, Assistant United States Attorney (Jo Ann M. \n Navickas and Julia Nestor, Assistant United States Attorneys, \n on the brief), for Richard P. Donoghue, United States Attorney \n for the Eastern District of New York, Brooklyn, New York, for \n Appellee. \n\n         _______________ \n\nROBERT A. KATZMANN, Chief Judge:  \n\n This securities fraud case calls upon us to review whether there was \n\nsufficient evidence of criminal intent to sustain a judgment of conviction against \n\na tipper who did not directly trade on material, non‐public information but \n\nrather shared it with a tippee who did. Robert Schulman appeals from a \n\njudgment entered October 4, 2017 in the United States District Court for the \n\nEastern District of New York (Azrack, J.) convicting him, after a jury trial, of one \n\n\n 2 \n \n\f \ncount of conspiracy to commit securities fraud, in violation of 18 U.S.C. § 371, \n\nand one count of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff. The \n\njury found, in relevant part, that Schulman engaged in a conspiracy to trade in \n\nthe securities of a company called King Pharmaceuticals (“King”) using material, \n\nnon‐public information that he obtained through his representation of King \n\nwhile a partner at the law firm of Hunton & Williams (“Hunton”). Schulman’s \n\nsole contention on appeal is that the government adduced insufficient evidence \n\nat trial of his criminal intent. \n\n Schulman’s arguments focus on a comment Schulman says he made to his \n\nfriend and financial advisor Tibor Klein: “[I]t would be nice to be king for a day.” \n\nApp. 251. Schulman concedes that, in making this comment, he “disclosed non‐\n\npublic information to a friend who was also his financial advisor.” Appellant’s \n\nBr. at 4. But, according to Schulman, his comment was merely a “joke,” App. at \n\n251, or, as he argues now, “a boastful, imprudent” remark, Appellant’s Br. at 4. \n\nHe contends that no reasonable jury could conclude beyond a reasonable \n\ndoubt—in light of his testimony that he communicated nothing more about King \n\nor its ongoing merger talks, see App. at 252 (“I would have never told him . . . \n\n\n\n 3 \n \n\f \nthere’s a potential merger.”); id. (“[T]hat’s the extent of what I would have \n\ncommunicated to him.”)—that he disclosed this information “with the \n\nexpectation that [Klein would] trade on it,” United States v. Martoma, 894 F.3d 64, \n\n79 (2d Cir. 2017); see also Salman v. United States, 137 S. Ct. 420, 428 (2016). \n\n We disagree. The evidence here, taken as a whole, is sufficient to support \n\nthe jury’s verdict. The jury was entitled to discredit Schulman’s testimony in a \n\nprior deposition that he intended only to brag and that he told Klein nothing \n\nabout King’s ongoing merger talks. Extensive circumstantial evidence supports \n\nan inference that Schulman communicated more to Klein than that “it would be \n\nnice to be king for a day” and that Schulman expected Klein to use the non‐\n\npublic information he shared with him to trade in King securities. Accordingly, \n\nthe judgment of the district court is AFFIRMED.  \n\n  \n\n BACKGROUND \n\n  On August 4, 2016, a grand jury in the Eastern District of New York \n\ncharged Robert Schulman and Tibor Klein with securities fraud and conspiracy \n\nto commit securities fraud. On February 24, 2017, the district court granted \n\n\n\n 4 \n \n\f \nKlein’s motion to sever his trial from Schulman’s, and on March 6, 2017, \n\nSchulman’s trial commenced. At trial, the Government introduced, inter alia, the \n\ntestimony of a cooperating witness, Michael Shechtman; sworn statements \n\nSchulman made to the U.S. Securities and Exchange Commission (“SEC”) in a \n\ndeposition on August 27, 2012; and notes taken during Schulman’s meeting with \n\nthe U.S. Attorney’s Office (“USAO”) on May 19, 2015. Schulman called, among \n\nothers, his wife, Ronnie Schulman. Neither Robert Schulman nor Klein testified \n\nat trial. \n\n I. Trial Evidence \n\n The evidence at trial included the following. Schulman was a Washington \n\nD.C.‐based partner in Hunton’s patent group. Klein was the principal of Klein \n\nFinancial Services, a registered investment advisor based in Long Island, New \n\nYork. In or about 2000, Schulman and his wife, Ronnie Schulman, hired Klein. \n\nThe Schulmans gave Klein discretionary authority over their investment \n\naccounts, meaning that Klein could trade securities without first obtaining the \n\nSchulmans’ permission. For his efforts, the Schulmans paid Klein one percent of \n\n\n\n\n 5 \n \n\f \ntheir portfolio per year, an arrangement akin to those Klein had with other \n\nclients. \n\n  Approximately three times each year, Klein traveled to the Schulmans’ \n\nhome in McLean, Virginia to discuss the Schulmans’ finances. On these \n\noccasions, Klein arrived Friday afternoon, visited with Ronnie Schulman before \n\nRobert Schulman got home from work, and then had dinner with the Schulmans. \n\nAfter dinner, the Schulmans and Klein discussed the Schulmans’ investment \n\naccounts, including, albeit “very rarely,” individual stocks. App. at 805. Klein \n\nthen spent the night in the Schulmans’ guest room. \n\n The Schulmans and Klein had become friends. As Ronnie Schulman \n\nexplained, although her husband was “not close with Tibor in the personal way \n\nthat I was,” her husband and Klein went to baseball games, went out to dinner \n\nwhen Schulman travelled to New York for business, and would share a beer or \n\nglass of wine. Id. at 821. The Schulmans also introduced Klein to their friends, \n\nwho subsequently also invested with Klein. \n\n  The Schulmans were “generally pleased” with Klein’s services, although \n\nthey were concerned that Klein had been too “bearish” in the years following the \n\n\n\n 6 \n \n\f \n2008 financial crisis. Id. at 241. The jury also learned that, in April, May, and June \n\n2010, Klein made several purchases of Enzo Pharmaceuticals (“Enzo”) in \n\nSchulman’s IRA account. Enzo was Schulman’s client at the time, and Klein \n\nknew that. When Schulman was asked about these trades by the SEC in 2012, he \n\nsaid that he “remember[ed] being a little upset” at Klein when Klein told him \n\nabout these purchases, “because . . . the CEO [of Enzo] is a certifiable lunatic.” Id. \n\nat 245. He added: “I remember being a little upset, but I don’t remember what \n\nhappened with that. I think he sold it at some point after that.” Id. Several years \n\nlater, in 2015, when Schulman was asked about these trades by the USAO he said \n\nthat he believed “it was improper . . . to own shares in a client” and that he \n\n“reprimanded Klein not to [trade in securities of his clients] in the future.” Id. at \n\n242.  \n\n  Schulman’s convictions relate to his representation of King. In July 2010, \n\nSchulman was preparing for summary judgment and trial in a patent lawsuit \n\ninvolving King, when King’s in‐house counsel informed another Hunton partner \n\nthat King was looking to settle the case and that King was in merger discussions \n\nwith Pfizer. On August 4, 2010, that partner and another Hunton lawyer, David \n\n\n\n 7 \n \n\f \nKelly, met with Pfizer’s lawyers in New York as part of Pfizer’s due diligence. \n\nThereafter, Schulman learned of the potential merger from Kelly. Kelly told \n\nSchulman to keep the information confidential.  \n\n Less than ten days later, on Friday, August 13, Klein traveled to the \n\nSchulmans’ home in Virginia for one of their regular meetings. Klein arrived in \n\nthe afternoon, had dinner with the Schulmans, spent the night in their guest \n\nroom, and departed the next morning. Schulman, in his SEC deposition, \n\nadmitted to telling Klein about King. Specifically, Schulman said: \n\n [T]here was one evening when Mr. Klein was at my house where I did \n mention, and I kind of made a joke with him, “boy, it would be nice to be \n king for a day.” And I made some joke with him about that. And at that \n point I would have never told him anything about their meeting, there’s a \n potential merger, it would have been much more of the nature of “hey, \n wouldn’t it be great to be king for a day, ha, ha, ha,” kind of like telling \n him, like acting like I am a big shot and I know this thing. But that’s the \n extent of what I would have communicated to him. \n \nId. at 251‐52. Schulman provided a similar explanation to the USAO in his 2015 \n\ninterview. Id. at 240‐41.   \n\n Ronnie Schulman, the only person to testify at trial who was present that \n\nevening, said that she could not remember anything being said about King. In \n\n\n\n\n 8 \n \n\f \nparticular, Ronnie Schulman said that she did not hear her husband say, “I’d like \n\nto be king for a day,” but that, even if he had said it, she may not have picked up \n\non it as significant because it would have just been “silly talk.” Id. at 831‐32.  \n\n  On Sunday, August 15, Klein called Shechtman, his childhood best friend, \n\nand a financial advisor at Ameriprise Financial (“Ameriprise”), but could not \n\nreach him. The next day, Klein reached Shechtman and asked him what he \n\nwould do if he thought he had inside information. Shechtman asked Klein what \n\nhe was talking about. Klein said: “Pfizer’s buying King Pharmaceuticals.” Id. at \n\n335. Shechtman asked Klein if he had spoken to Frank Marzano, one of Klein’s \n\nformer colleagues, about King, and Klein told Shechtman that Marzano \n\n“wouldn’t touch this.” Id. at 337‐38. Shechtman did not ask Klein about the \n\nsource of his information because he “didn’t want to know the answers.” Id. at \n\n336. Klein did not mention any publicly available information that might justify \n\npurchasing King securities at the time he initially shared the material, non‐public \n\ninformation with Shechtman.  \n\n Shechtman then purchased $15,000 of King options, some expiring \n\nSeptember 18, 2010 and some expiring October 16, 2010. Shechtman also \n\n\n\n 9 \n \n\f \npurchased $45,000 of King stock for himself and his wife. Klein purchased 65,150 \n\nKing shares for $585,217 in various accounts including accounts belonging to \n\nhim, the Schulmans, and forty‐eight clients, including the Schulmans’ friends \n\nand Klein’s parents. Klein’s purchases for the Schulmans totaled $26,899, 7.35 \n\npercent of Robert Schulman’s IRA.  \n\n  On October 12, 2010, Pfizer announced its acquisition of King. Shechtman \n\nimmediately sold his King stock and options, for a profit of more than $110,000. \n\nKlein sold his King stock for a profit of approximately $8,000, and the King stock \n\nhe had purchased for his family and clients for a profit of $328,038. Schulman’s \n\nshare of these profits was around $15,500, an over 50 percent return in less than \n\ntwo months.  \n\n   A few weeks later, an Ameriprise compliance officer approached \n\nShechtman, telling him there was a serious problem. When Shechtman heard \n\nthis, he “went numb,” because he “immediately knew it was about the trades.” \n\nId. at 366. At first, Shechtman lied, saying that he had been looking at King for a \n\nwhile and had spoken with some fellow advisors about King who thought it was \n\na good investment. Later, Shechtman sent an email to Ameriprise compliance \n\n\n\n 10 \n \n\f \nofficers disclosing that he had spoken with Klein about King, in case \n\ninvestigators noticed his numerous phone calls with Klein. A week later, \n\nShechtman told Klein about the Ameriprise investigation. As Ameriprise had \n\nasked Shechtman for information backing up his story, such as research reports \n\nor notes, Klein sent an email to a “junk email” address shared by Shechtman and \n\nhis wife containing some research about King. Around this time, Klein also sold \n\nall of Schulman’s Enzo shares.  \n\n  Following an investigation, the SEC charged Shechtman and Shechtman \n\nadmitted liability. Shechtman also agreed to cooperate with the USAO and to \n\nplead guilty to conspiracy to commit securities fraud. The SEC then charged \n\nKlein in the fall of 2013, at which point the Schulmans fired Klein. Ronnie \n\ntestified that she and her husband had not fired Klein earlier, for example, after \n\nlearning that Klein had traded in King securities in their accounts or after Robert \n\nwas deposed by the SEC, because they “trusted” Klein and “believed there was \n\nan innocent explanation” for all that had happened. Id. at 839‐40. \n\n II. Post‐Trial Proceedings \n\n\n\n\n 11 \n \n\f \n Schulman moved for a judgment of acquittal after the government rested, \n\narguing, among other things, that the evidence did not establish that he intended \n\nfor Klein to trade in King securities. The district court denied Schulman’s motion. \n\nSchulman renewed his motion for a judgment of acquittal at the conclusion of the \n\nevidence, and the district court again denied the motion. Thereafter, the district \n\ncourt charged the jury, and, a little over a day later, the jury returned guilty \n\nverdicts on both counts. \n\n Schulman then moved for a judgment of acquittal pursuant to Federal \n\nRule of Criminal Procedure 29. Schulman argued, inter alia, that no reasonable \n\njury could have inferred that he told Klein more than the “king for a day” \n\ncomment and that no reasonable jury could have found that he had intended \n\nKlein to trade on it. The district court denied Schulman’s motion by reasoned \n\nopinion. Thereafter, the district court sentenced Schulman on both counts to \n\nthree years’ probation to run concurrently, a $50,000 fine, forfeiture in the \n\namount of $15,527, and 2,000 hours of community service. This appeal timely \n\nfollowed. \n\n\n\n\n 12 \n \n\f \n DISCUSSION \n\n We review de novo a district court’s order denying a Rule 29 motion \n\naddressing the sufficiency of the evidence. United States v. Khalil, 857 F.3d 137, \n\n139 (2d Cir. 2017). In challenging the jury’s verdict, a Rule 29 movant “bears a \n\nheavy burden.” Martoma, 894 F.3d at 72.1 A reviewing court must “credit[] every \n\ninference that could have been drawn in the government’s favor,” id., and \n\n“affirm the conviction so long as, from the inferences reasonably drawn, the jury \n\nmight fairly have concluded guilt beyond a reasonable doubt.” United States v. \n\nReifler, 446 F.3d 65, 94 (2d Cir. 2006).  \n\n Moreover, in considering Schulman’s sufficiency challenge, we do not \n\nevaluate the evidence piecemeal or in isolation. We view the evidence “in \n\nconjunction” and uphold Schulman’s conviction “if any rational trier of fact \n\ncould have found the essential elements of the crime beyond a reasonable \n\ndoubt.” Id. at 94‐95; see Jackson v. Virginia, 443 U.S. 307, 319 (1979). While \n\n“specious inferences are not indulged,” United States v. Lorenzo, 534 F.3d 153, 159 \n\n\n\n                                               \n\n  1 Unless otherwise indicated, in quoting cases, all internal quotation marks, \nalterations, footnotes, and citations are omitted. \n\n 13 \n\f \n(2d Cir. 2008), we “defer to the jury’s determination of the weight of the evidence \n\nand the credibility of the witnesses, and to the jury’s choice of the competing \n\ninferences that can be drawn from the evidence,” Reifler, 446 F.3d at 94. In a close \n\ncase, where “either of the two results, a reasonable doubt or no reasonable doubt, \n\nis fairly possible, [we] must let the jury decide the matter.” United States v. \n\nAutuori, 212 F.3d 105, 114 (2d Cir. 2000). \n\n In an insider trading case, the government must prove that the insider will \n\npersonally benefit from the disclosure to the tippee. See Martoma, 894 F.3d at 73. \n\nPersonal benefit can be established in a number of ways, including by illustrating \n\nthe nature of the relationship between the tipper and the tippee or the tipper’s \n\nreceipt of something of value. The critical question regards the tipper’s purpose: \n\ndid the tipper share the material non‐public information with the tippee \n\nintending that the tippee use the information to improperly trade in securities? \n\nSee id. at 79 (a tipper is liable under 15 U.S.C. § 78j(b) if the tipper discloses \n\nmaterial, non‐public information “with the expectation that the tippee will trade \n\non it”); see also United States v. Gansman, 657 F.3d 85, 92 (2d Cir. 2011) (“In \n\nprosecuting a putative ‘tipper’ under the misappropriation theory of insider \n\n\n\n 14 \n \n\f \ntrading, the government must prove as an element of the offense that the tipper \n\nconveyed material nonpublic information to his ‘tippee’ with the understanding \n\nthat it would be used for securities trading purposes.”).2 Schulman argues that \n\n“[t]he Government presented no evidence [at trial], either direct or \n\ncircumstantial, that [he] intended for Klein to trade on” his tip about King. \n\nAppellant’s Br. at 26. According to Schulman, the evidence merely “suggests that \n\n[he] made a misguided comment to a friend in an effort to show off that he knew \n\nsomething that the public did not.” Id. at 22. \n\n We disagree. This is a case where it is essential to view the various pieces \n\nof evidence together. Although Schulman told the SEC that he had \n\ncommunicated “nothing” more than that he wished he could be king for a day, \n\nApp. at 240—a comment that, by itself, is innocuous—the jury was entitled to \n\ndisbelieve that he communicated nothing more. The district court properly \n\n\n                                               \n\n   2 As relevant here, 15 U.S.C. § 78j(b) prohibits the use of “any manipulative or \n\n deceptive device or contrivance” to contravene an SEC rule, including Rule 10b‐5. See 17 \n C.F.R. § 240.10b‐5. Rule 10b‐5 bars “undisclosed trading on inside corporate information \n by individuals who are under a duty of trust and confidence that prohibits them from \n secretly using such information for their personal advantage.” Salman v. United States, \n 137 S. Ct. 420, 423 (2016). “These persons also may not tip inside information to others \n for trading.” Id. \n\n 15 \n\f \ninstructed the jury to draw “reasonable inferences,” id. at 1290, and “us[e] \n\ncommon sense,” id. at 1317. As a matter of common sense, Schulman had to have \n\ncommunicated additional information for Schulman to concede to the SEC that \n\nhis king‐for‐a‐day comment was in fact “a reference to King Pharmaceuticals,” id. \n\nat 241. An oral statement does not usually reflect capitalization. Nonetheless, \n\nKlein apparently recognized that by “king” Schulman meant “King.” Common \n\nsense also would lead a rational juror to conclude that Schulman had to have \n\ncommunicated additional information to Klein for Klein to have promptly called \n\nShechtman, cited “inside information” about King and Pfizer, id. at 335, and \n\nbegun buying King stock. Indeed, this precise issue was argued to the jury, see id. \n\nat 1231‐32, 1265, and was resolved by the jury against Schulman. \n\n Further, the trial record is replete with evidence supporting an inference \n\nthat Schulman told Klein information about King so that Klein would trade on it. \n\nFor example, a reasonable jury could infer that Schulman intended Klein to trade \n\nfrom the evidence that (1) Klein was Schulman’s money manager, with \n\ndiscretionary authority over Schulman’s accounts, and that Schulman told Klein \n\nabout King during a meeting to discuss his investment portfolio; (2) after \n\n\n\n 16 \n \n\f \nmeeting with Schulman, Klein immediately bought hundreds of thousands of \n\ndollars of King stock, including in Schulman’s account and in the accounts of \n\nSchulman’s friends; and (3) Klein, on behalf of Schulman, had previously \n\npurchased stock in one of Schulman’s clients, Enzo. \n\n We reject Schulman’s arguments that Klein’s role as his financial advisor, \n\nand Klein’s conversations with Shechtman and purchases of King stock \n\nfollowing the meeting with Schulman are irrelevant. A rational jury could infer \n\nfrom the fact that Klein managed Schulman’s money and worked as a \n\nprofessional stock trader that Schulman intended Klein to trade on a stock tip he \n\nshared with him. The fact that Klein and Schulman were also close friends does \n\nnot detract from the relevance of Klein’s profession; in fact, it supplies an \n\nadditional motive for Schulman’s tip. Similarly, a rational jury could infer from \n\nthe fact that Klein purchased hundreds of thousands of dollars in King securities \n\nimmediately after meeting with Schulman, including over twenty‐five thousand \n\ndollars of King stock in Schulman’s account, that Klein was acting in accordance \n\nwith Schulman’s intent. This is true even though there were “virtually no \n\ncommunications” between Schulman and Klein in the months following \n\n\n\n 17 \n \n\f \nSchulman’s disclosure. Appellant’s Br. at 29. The jury was not required to accept \n\nSchulman’s contrary interpretation of the facts—that Klein’s purchase of stock \n\nfor Schulman was reckless and unthinking—as there is ample evidence in the \n\nrecord that Klein behaved in a calculated manner in trading on the information \n\nabout King. \n\n  We also reject Schulman’s argument that Klein’s prior purchase of Enzo \n\nstock is irrelevant. A reasonable jury could infer from the fact that Klein had once \n\ntraded in the stock of Schulman’s clients that he might be expected to do so \n\nagain. And, as Schulman was aware of Klein’s trading in Enzo, the jury could \n\nfurther infer that when Schulman told Klein about King, he expected Klein to act \n\non the information. In making these inferences, a reasonable jury could consider \n\nSchulman’s varying explanations for his disapproval of Klein’s prior purchase of \n\nEnzo stock. Specifically, when Schulman was first interviewed by the SEC in \n\n2012, he testified, “I remember being a little upset at [Klein for buying Enzo \n\nstock,] because I think that the CEO [of Enzo] is a certifiable lunatic.” App. at 245. \n\nBut several years later, Schulman told the USAO that the reason he criticized \n\nKlein for buying Enzo stock was that it was improper to own shares of a client. \n\n\n\n 18 \n \n\f \nSee id. at 242. The jury could reasonably view Schulman’s second explanation as a \n\nconscious attempt to sanitize his first explanation, which had criticized only the \n\neconomic soundness of the investment, not its legality or propriety. \n\n  In addition, Schulman’s first, and perhaps more genuine explanation, \n\nprovides further context for the king‐for‐a‐day comment. For example, the jury \n\ncould reasonably infer from the Enzo evidence that, while Klein knew that \n\nSchulman had been upset at him for buying Enzo shares because the CEO was a \n\n“lunatic,” Klein understood that Schulman’s stating a wish to be “[K]ing for a \n\nday” meant that buying King shares was, in fact, given Schulman’s inside \n\ninformation, a good idea.  \n\n In this regard, it is also relevant that Schulman thought that Klein’s \n\ninvestments in 2009 and 2010 had been “too bearish,” id. at 241, since Schulman’s \n\ndesire to invest more aggressively, along with his view of Klein’s Enzo purchase \n\nas unwise, could be viewed as fueling a desire by Schulman to help Klein achieve \n\ngreater returns in Schulman’s portfolio. And while Schulman argues that $15,000 \n\nwas so insignificant a fraction of his overall net worth that it could not have been \n\nan incentive for him to tip Klein, that sizable net worth entitled the jury to \n\n\n\n 19 \n \n\f \ndisbelieve Schulman’s preferred explanation that he made his king‐for‐a‐day \n\ncomment simply to “show off.” Appellant’s Br. at 22.  \n\n Finally, Schulman contends that he is entitled to a judgment of acquittal \n\nbecause the evidence supporting the inference that he intended Klein to trade on \n\nhis tip about King is, at the very least, in equipoise with evidence supporting an \n\ninference that he intended merely to boast. But it is not. Schulman cites mainly \n\nthe absence of evidence of any follow‐up conversations with Klein. This absence \n\nof evidence at best supports an inference that Schulman did not intend for Klein \n\nto trade for Schulman’s benefit. It says little, if anything, about whether \n\nSchulman intended Klein to trade for Klein’s benefit, an independent basis upon \n\nwhich a rational jury could have found Schulman guilty.3 Moreover, we know of \n\nno requirement in insider trading law that the government adduce evidence of \n\nmultiple conversations between co‐conspirators, or that the government provide \n\ndirect testimonial evidence regarding a defendant’s intent. See Lorenzo, 534 F.3d \n\n\n\n                                               \n\n 3  The Government argued at trial that Martoma’s “personal benefit” requirement \n was satisfied both because Schulman intended to receive a financial benefit and because \n Schulman intended to make a “gift” to Klein. The district court instructed the jury on \n both theories. \n\n 20 \n\f \nat 159 (the government “is entitled to prove its case solely through circumstantial \n\nevidence”).  \n\n CONCLUSION \n\n After conducting an independent review of the record and considering the \n\nevidence as a whole, we conclude that a rational trier of fact could have found \n\nthat Schulman acted with the requisite intent beyond a reasonable doubt. We \n\nhave considered all of Schulman’s contentions on appeal and have found in them \n\nno basis for reversal. Accordingly, the judgment of the district court is \n\nAFFIRMED. \n\n\n\n\n 21", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357659/", "author_raw": "ROBERT A. KATZMANN, Chief Judge"}]}
KATZMANN
KEARSE
CHIN
1
{"KATZMANN": ", Chief", "KEARSE": ", Circuit", "CHIN": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580406/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: States Court of Appeals\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUnited States Court of Appeals\n for the Second Circuit\n _______________ \n\n AUGUST TERM, 2018 \n  \n (Argued: October 22, 2018               Decided: January 10, 2019) \n  \n Docket No. 17‐3355 \n  \n _______________ \n  \n UNITED STATES OF AMERICA, \n Appellee, \n  \n —v.— \n\n Tibor Klein, \n Defendant, \n  \n ROBERT SCHULMAN, \n Defendant‐Appellant. \n _______________ \n  \n Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges. \n\n _______________ \n  \n Defendant‐appellant Robert Schulman appeals from an October 4, 2017 \njudgment convicting him, following a jury trial, of one count of conspiracy to \ncommit securities fraud and one count of securities fraud. On appeal, Schulman \nargues that the district court erroneously denied his motion pursuant to Federal \nRule of Criminal Procedure 29 to vacate his convictions. According to Schulman, \n\n\n\n 1 \n \n\f \nhis convictions cannot stand because the government adduced insufficient \nevidence at trial of his criminal intent. Because the jury was not required to credit \nSchulman’s deposition testimony that he intended only to brag when he tipped \nhis friend and financial advisor about an upcoming merger, and the evidence \ntaken as a whole permitted the jury to find beyond a reasonable doubt that \nSchulman intended his communication to lead to trading in securities of the \ncompany in question, we disagree. Accordingly, we AFFIRM the judgment of \nthe district court. \n _______________ \n\n MARK D. HARRIS (John E. Roberts, on the brief), Proskauer Rose LLP,  \n New York, New York, for Defendant‐Appellant. \n  \n DAVID C. PITLUCK, Assistant United States Attorney (Jo Ann M. \n Navickas and Julia Nestor, Assistant United States Attorneys, \n on the brief), for Richard P. Donoghue, United States Attorney \n for the Eastern District of New York, Brooklyn, New York, for \n Appellee. \n\n         _______________ \n\nROBERT A. KATZMANN, Chief Judge:  \n\n This securities fraud case calls upon us to review whether there was \n\nsufficient evidence of criminal intent to sustain a judgment of conviction against \n\na tipper who did not directly trade on material, non‐public information but \n\nrather shared it with a tippee who did. Robert Schulman appeals from a \n\njudgment entered October 4, 2017 in the United States District Court for the \n\nEastern District of New York (Azrack, J.) convicting him, after a jury trial, of one \n\n\n 2 \n \n\f \ncount of conspiracy to commit securities fraud, in violation of 18 U.S.C. § 371, \n\nand one count of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff. The \n\njury found, in relevant part, that Schulman engaged in a conspiracy to trade in \n\nthe securities of a company called King Pharmaceuticals (“King”) using material, \n\nnon‐public information that he obtained through his representation of King \n\nwhile a partner at the law firm of Hunton & Williams (“Hunton”). Schulman’s \n\nsole contention on appeal is that the government adduced insufficient evidence \n\nat trial of his criminal intent. \n\n Schulman’s arguments focus on a comment Schulman says he made to his \n\nfriend and financial advisor Tibor Klein: “[I]t would be nice to be king for a day.” \n\nApp. 251. Schulman concedes that, in making this comment, he “disclosed non‐\n\npublic information to a friend who was also his financial advisor.” Appellant’s \n\nBr. at 4. But, according to Schulman, his comment was merely a “joke,” App. at \n\n251, or, as he argues now, “a boastful, imprudent” remark, Appellant’s Br. at 4. \n\nHe contends that no reasonable jury could conclude beyond a reasonable \n\ndoubt—in light of his testimony that he communicated nothing more about King \n\nor its ongoing merger talks, see App. at 252 (“I would have never told him . . . \n\n\n\n 3 \n \n\f \nthere’s a potential merger.”); id. (“[T]hat’s the extent of what I would have \n\ncommunicated to him.”)—that he disclosed this information “with the \n\nexpectation that [Klein would] trade on it,” United States v. Martoma, 894 F.3d 64, \n\n79 (2d Cir. 2017); see also Salman v. United States, 137 S. Ct. 420, 428 (2016). \n\n We disagree. The evidence here, taken as a whole, is sufficient to support \n\nthe jury’s verdict. The jury was entitled to discredit Schulman’s testimony in a \n\nprior deposition that he intended only to brag and that he told Klein nothing \n\nabout King’s ongoing merger talks. Extensive circumstantial evidence supports \n\nan inference that Schulman communicated more to Klein than that “it would be \n\nnice to be king for a day” and that Schulman expected Klein to use the non‐\n\npublic information he shared with him to trade in King securities. Accordingly, \n\nthe judgment of the district court is AFFIRMED.  \n\n  \n\n BACKGROUND \n\n  On August 4, 2016, a grand jury in the Eastern District of New York \n\ncharged Robert Schulman and Tibor Klein with securities fraud and conspiracy \n\nto commit securities fraud. On February 24, 2017, the district court granted \n\n\n\n 4 \n \n\f \nKlein’s motion to sever his trial from Schulman’s, and on March 6, 2017, \n\nSchulman’s trial commenced. At trial, the Government introduced, inter alia, the \n\ntestimony of a cooperating witness, Michael Shechtman; sworn statements \n\nSchulman made to the U.S. Securities and Exchange Commission (“SEC”) in a \n\ndeposition on August 27, 2012; and notes taken during Schulman’s meeting with \n\nthe U.S. Attorney’s Office (“USAO”) on May 19, 2015. Schulman called, among \n\nothers, his wife, Ronnie Schulman. Neither Robert Schulman nor Klein testified \n\nat trial. \n\n I. Trial Evidence \n\n The evidence at trial included the following. Schulman was a Washington \n\nD.C.‐based partner in Hunton’s patent group. Klein was the principal of Klein \n\nFinancial Services, a registered investment advisor based in Long Island, New \n\nYork. In or about 2000, Schulman and his wife, Ronnie Schulman, hired Klein. \n\nThe Schulmans gave Klein discretionary authority over their investment \n\naccounts, meaning that Klein could trade securities without first obtaining the \n\nSchulmans’ permission. For his efforts, the Schulmans paid Klein one percent of \n\n\n\n\n 5 \n \n\f \ntheir portfolio per year, an arrangement akin to those Klein had with other \n\nclients. \n\n  Approximately three times each year, Klein traveled to the Schulmans’ \n\nhome in McLean, Virginia to discuss the Schulmans’ finances. On these \n\noccasions, Klein arrived Friday afternoon, visited with Ronnie Schulman before \n\nRobert Schulman got home from work, and then had dinner with the Schulmans. \n\nAfter dinner, the Schulmans and Klein discussed the Schulmans’ investment \n\naccounts, including, albeit “very rarely,” individual stocks. App. at 805. Klein \n\nthen spent the night in the Schulmans’ guest room. \n\n The Schulmans and Klein had become friends. As Ronnie Schulman \n\nexplained, although her husband was “not close with Tibor in the personal way \n\nthat I was,” her husband and Klein went to baseball games, went out to dinner \n\nwhen Schulman travelled to New York for business, and would share a beer or \n\nglass of wine. Id. at 821. The Schulmans also introduced Klein to their friends, \n\nwho subsequently also invested with Klein. \n\n  The Schulmans were “generally pleased” with Klein’s services, although \n\nthey were concerned that Klein had been too “bearish” in the years following the \n\n\n\n 6 \n \n\f \n2008 financial crisis. Id. at 241. The jury also learned that, in April, May, and June \n\n2010, Klein made several purchases of Enzo Pharmaceuticals (“Enzo”) in \n\nSchulman’s IRA account. Enzo was Schulman’s client at the time, and Klein \n\nknew that. When Schulman was asked about these trades by the SEC in 2012, he \n\nsaid that he “remember[ed] being a little upset” at Klein when Klein told him \n\nabout these purchases, “because . . . the CEO [of Enzo] is a certifiable lunatic.” Id. \n\nat 245. He added: “I remember being a little upset, but I don’t remember what \n\nhappened with that. I think he sold it at some point after that.” Id. Several years \n\nlater, in 2015, when Schulman was asked about these trades by the USAO he said \n\nthat he believed “it was improper . . . to own shares in a client” and that he \n\n“reprimanded Klein not to [trade in securities of his clients] in the future.” Id. at \n\n242.  \n\n  Schulman’s convictions relate to his representation of King. In July 2010, \n\nSchulman was preparing for summary judgment and trial in a patent lawsuit \n\ninvolving King, when King’s in‐house counsel informed another Hunton partner \n\nthat King was looking to settle the case and that King was in merger discussions \n\nwith Pfizer. On August 4, 2010, that partner and another Hunton lawyer, David \n\n\n\n 7 \n \n\f \nKelly, met with Pfizer’s lawyers in New York as part of Pfizer’s due diligence. \n\nThereafter, Schulman learned of the potential merger from Kelly. Kelly told \n\nSchulman to keep the information confidential.  \n\n Less than ten days later, on Friday, August 13, Klein traveled to the \n\nSchulmans’ home in Virginia for one of their regular meetings. Klein arrived in \n\nthe afternoon, had dinner with the Schulmans, spent the night in their guest \n\nroom, and departed the next morning. Schulman, in his SEC deposition, \n\nadmitted to telling Klein about King. Specifically, Schulman said: \n\n [T]here was one evening when Mr. Klein was at my house where I did \n mention, and I kind of made a joke with him, “boy, it would be nice to be \n king for a day.” And I made some joke with him about that. And at that \n point I would have never told him anything about their meeting, there’s a \n potential merger, it would have been much more of the nature of “hey, \n wouldn’t it be great to be king for a day, ha, ha, ha,” kind of like telling \n him, like acting like I am a big shot and I know this thing. But that’s the \n extent of what I would have communicated to him. \n \nId. at 251‐52. Schulman provided a similar explanation to the USAO in his 2015 \n\ninterview. Id. at 240‐41.   \n\n Ronnie Schulman, the only person to testify at trial who was present that \n\nevening, said that she could not remember anything being said about King. In \n\n\n\n\n 8 \n \n\f \nparticular, Ronnie Schulman said that she did not hear her husband say, “I’d like \n\nto be king for a day,” but that, even if he had said it, she may not have picked up \n\non it as significant because it would have just been “silly talk.” Id. at 831‐32.  \n\n  On Sunday, August 15, Klein called Shechtman, his childhood best friend, \n\nand a financial advisor at Ameriprise Financial (“Ameriprise”), but could not \n\nreach him. The next day, Klein reached Shechtman and asked him what he \n\nwould do if he thought he had inside information. Shechtman asked Klein what \n\nhe was talking about. Klein said: “Pfizer’s buying King Pharmaceuticals.” Id. at \n\n335. Shechtman asked Klein if he had spoken to Frank Marzano, one of Klein’s \n\nformer colleagues, about King, and Klein told Shechtman that Marzano \n\n“wouldn’t touch this.” Id. at 337‐38. Shechtman did not ask Klein about the \n\nsource of his information because he “didn’t want to know the answers.” Id. at \n\n336. Klein did not mention any publicly available information that might justify \n\npurchasing King securities at the time he initially shared the material, non‐public \n\ninformation with Shechtman.  \n\n Shechtman then purchased $15,000 of King options, some expiring \n\nSeptember 18, 2010 and some expiring October 16, 2010. Shechtman also \n\n\n\n 9 \n \n\f \npurchased $45,000 of King stock for himself and his wife. Klein purchased 65,150 \n\nKing shares for $585,217 in various accounts including accounts belonging to \n\nhim, the Schulmans, and forty‐eight clients, including the Schulmans’ friends \n\nand Klein’s parents. Klein’s purchases for the Schulmans totaled $26,899, 7.35 \n\npercent of Robert Schulman’s IRA.  \n\n  On October 12, 2010, Pfizer announced its acquisition of King. Shechtman \n\nimmediately sold his King stock and options, for a profit of more than $110,000. \n\nKlein sold his King stock for a profit of approximately $8,000, and the King stock \n\nhe had purchased for his family and clients for a profit of $328,038. Schulman’s \n\nshare of these profits was around $15,500, an over 50 percent return in less than \n\ntwo months.  \n\n   A few weeks later, an Ameriprise compliance officer approached \n\nShechtman, telling him there was a serious problem. When Shechtman heard \n\nthis, he “went numb,” because he “immediately knew it was about the trades.” \n\nId. at 366. At first, Shechtman lied, saying that he had been looking at King for a \n\nwhile and had spoken with some fellow advisors about King who thought it was \n\na good investment. Later, Shechtman sent an email to Ameriprise compliance \n\n\n\n 10 \n \n\f \nofficers disclosing that he had spoken with Klein about King, in case \n\ninvestigators noticed his numerous phone calls with Klein. A week later, \n\nShechtman told Klein about the Ameriprise investigation. As Ameriprise had \n\nasked Shechtman for information backing up his story, such as research reports \n\nor notes, Klein sent an email to a “junk email” address shared by Shechtman and \n\nhis wife containing some research about King. Around this time, Klein also sold \n\nall of Schulman’s Enzo shares.  \n\n  Following an investigation, the SEC charged Shechtman and Shechtman \n\nadmitted liability. Shechtman also agreed to cooperate with the USAO and to \n\nplead guilty to conspiracy to commit securities fraud. The SEC then charged \n\nKlein in the fall of 2013, at which point the Schulmans fired Klein. Ronnie \n\ntestified that she and her husband had not fired Klein earlier, for example, after \n\nlearning that Klein had traded in King securities in their accounts or after Robert \n\nwas deposed by the SEC, because they “trusted” Klein and “believed there was \n\nan innocent explanation” for all that had happened. Id. at 839‐40. \n\n II. Post‐Trial Proceedings \n\n\n\n\n 11 \n \n\f \n Schulman moved for a judgment of acquittal after the government rested, \n\narguing, among other things, that the evidence did not establish that he intended \n\nfor Klein to trade in King securities. The district court denied Schulman’s motion. \n\nSchulman renewed his motion for a judgment of acquittal at the conclusion of the \n\nevidence, and the district court again denied the motion. Thereafter, the district \n\ncourt charged the jury, and, a little over a day later, the jury returned guilty \n\nverdicts on both counts. \n\n Schulman then moved for a judgment of acquittal pursuant to Federal \n\nRule of Criminal Procedure 29. Schulman argued, inter alia, that no reasonable \n\njury could have inferred that he told Klein more than the “king for a day” \n\ncomment and that no reasonable jury could have found that he had intended \n\nKlein to trade on it. The district court denied Schulman’s motion by reasoned \n\nopinion. Thereafter, the district court sentenced Schulman on both counts to \n\nthree years’ probation to run concurrently, a $50,000 fine, forfeiture in the \n\namount of $15,527, and 2,000 hours of community service. This appeal timely \n\nfollowed. \n\n\n\n\n 12 \n \n\f \n DISCUSSION \n\n We review de novo a district court’s order denying a Rule 29 motion \n\naddressing the sufficiency of the evidence. United States v. Khalil, 857 F.3d 137, \n\n139 (2d Cir. 2017). In challenging the jury’s verdict, a Rule 29 movant “bears a \n\nheavy burden.” Martoma, 894 F.3d at 72.1 A reviewing court must “credit[] every \n\ninference that could have been drawn in the government’s favor,” id., and \n\n“affirm the conviction so long as, from the inferences reasonably drawn, the jury \n\nmight fairly have concluded guilt beyond a reasonable doubt.” United States v. \n\nReifler, 446 F.3d 65, 94 (2d Cir. 2006).  \n\n Moreover, in considering Schulman’s sufficiency challenge, we do not \n\nevaluate the evidence piecemeal or in isolation. We view the evidence “in \n\nconjunction” and uphold Schulman’s conviction “if any rational trier of fact \n\ncould have found the essential elements of the crime beyond a reasonable \n\ndoubt.” Id. at 94‐95; see Jackson v. Virginia, 443 U.S. 307, 319 (1979). While \n\n“specious inferences are not indulged,” United States v. Lorenzo, 534 F.3d 153, 159 \n\n\n\n                                               \n\n  1 Unless otherwise indicated, in quoting cases, all internal quotation marks, \nalterations, footnotes, and citations are omitted. \n\n 13 \n\f \n(2d Cir. 2008), we “defer to the jury’s determination of the weight of the evidence \n\nand the credibility of the witnesses, and to the jury’s choice of the competing \n\ninferences that can be drawn from the evidence,” Reifler, 446 F.3d at 94. In a close \n\ncase, where “either of the two results, a reasonable doubt or no reasonable doubt, \n\nis fairly possible, [we] must let the jury decide the matter.” United States v. \n\nAutuori, 212 F.3d 105, 114 (2d Cir. 2000). \n\n In an insider trading case, the government must prove that the insider will \n\npersonally benefit from the disclosure to the tippee. See Martoma, 894 F.3d at 73. \n\nPersonal benefit can be established in a number of ways, including by illustrating \n\nthe nature of the relationship between the tipper and the tippee or the tipper’s \n\nreceipt of something of value. The critical question regards the tipper’s purpose: \n\ndid the tipper share the material non‐public information with the tippee \n\nintending that the tippee use the information to improperly trade in securities? \n\nSee id. at 79 (a tipper is liable under 15 U.S.C. § 78j(b) if the tipper discloses \n\nmaterial, non‐public information “with the expectation that the tippee will trade \n\non it”); see also United States v. Gansman, 657 F.3d 85, 92 (2d Cir. 2011) (“In \n\nprosecuting a putative ‘tipper’ under the misappropriation theory of insider \n\n\n\n 14 \n \n\f \ntrading, the government must prove as an element of the offense that the tipper \n\nconveyed material nonpublic information to his ‘tippee’ with the understanding \n\nthat it would be used for securities trading purposes.”).2 Schulman argues that \n\n“[t]he Government presented no evidence [at trial], either direct or \n\ncircumstantial, that [he] intended for Klein to trade on” his tip about King. \n\nAppellant’s Br. at 26. According to Schulman, the evidence merely “suggests that \n\n[he] made a misguided comment to a friend in an effort to show off that he knew \n\nsomething that the public did not.” Id. at 22. \n\n We disagree. This is a case where it is essential to view the various pieces \n\nof evidence together. Although Schulman told the SEC that he had \n\ncommunicated “nothing” more than that he wished he could be king for a day, \n\nApp. at 240—a comment that, by itself, is innocuous—the jury was entitled to \n\ndisbelieve that he communicated nothing more. The district court properly \n\n\n                                               \n\n   2 As relevant here, 15 U.S.C. § 78j(b) prohibits the use of “any manipulative or \n\n deceptive device or contrivance” to contravene an SEC rule, including Rule 10b‐5. See 17 \n C.F.R. § 240.10b‐5. Rule 10b‐5 bars “undisclosed trading on inside corporate information \n by individuals who are under a duty of trust and confidence that prohibits them from \n secretly using such information for their personal advantage.” Salman v. United States, \n 137 S. Ct. 420, 423 (2016). “These persons also may not tip inside information to others \n for trading.” Id. \n\n 15 \n\f \ninstructed the jury to draw “reasonable inferences,” id. at 1290, and “us[e] \n\ncommon sense,” id. at 1317. As a matter of common sense, Schulman had to have \n\ncommunicated additional information for Schulman to concede to the SEC that \n\nhis king‐for‐a‐day comment was in fact “a reference to King Pharmaceuticals,” id. \n\nat 241. An oral statement does not usually reflect capitalization. Nonetheless, \n\nKlein apparently recognized that by “king” Schulman meant “King.” Common \n\nsense also would lead a rational juror to conclude that Schulman had to have \n\ncommunicated additional information to Klein for Klein to have promptly called \n\nShechtman, cited “inside information” about King and Pfizer, id. at 335, and \n\nbegun buying King stock. Indeed, this precise issue was argued to the jury, see id. \n\nat 1231‐32, 1265, and was resolved by the jury against Schulman. \n\n Further, the trial record is replete with evidence supporting an inference \n\nthat Schulman told Klein information about King so that Klein would trade on it. \n\nFor example, a reasonable jury could infer that Schulman intended Klein to trade \n\nfrom the evidence that (1) Klein was Schulman’s money manager, with \n\ndiscretionary authority over Schulman’s accounts, and that Schulman told Klein \n\nabout King during a meeting to discuss his investment portfolio; (2) after \n\n\n\n 16 \n \n\f \nmeeting with Schulman, Klein immediately bought hundreds of thousands of \n\ndollars of King stock, including in Schulman’s account and in the accounts of \n\nSchulman’s friends; and (3) Klein, on behalf of Schulman, had previously \n\npurchased stock in one of Schulman’s clients, Enzo. \n\n We reject Schulman’s arguments that Klein’s role as his financial advisor, \n\nand Klein’s conversations with Shechtman and purchases of King stock \n\nfollowing the meeting with Schulman are irrelevant. A rational jury could infer \n\nfrom the fact that Klein managed Schulman’s money and worked as a \n\nprofessional stock trader that Schulman intended Klein to trade on a stock tip he \n\nshared with him. The fact that Klein and Schulman were also close friends does \n\nnot detract from the relevance of Klein’s profession; in fact, it supplies an \n\nadditional motive for Schulman’s tip. Similarly, a rational jury could infer from \n\nthe fact that Klein purchased hundreds of thousands of dollars in King securities \n\nimmediately after meeting with Schulman, including over twenty‐five thousand \n\ndollars of King stock in Schulman’s account, that Klein was acting in accordance \n\nwith Schulman’s intent. This is true even though there were “virtually no \n\ncommunications” between Schulman and Klein in the months following \n\n\n\n 17 \n \n\f \nSchulman’s disclosure. Appellant’s Br. at 29. The jury was not required to accept \n\nSchulman’s contrary interpretation of the facts—that Klein’s purchase of stock \n\nfor Schulman was reckless and unthinking—as there is ample evidence in the \n\nrecord that Klein behaved in a calculated manner in trading on the information \n\nabout King. \n\n  We also reject Schulman’s argument that Klein’s prior purchase of Enzo \n\nstock is irrelevant. A reasonable jury could infer from the fact that Klein had once \n\ntraded in the stock of Schulman’s clients that he might be expected to do so \n\nagain. And, as Schulman was aware of Klein’s trading in Enzo, the jury could \n\nfurther infer that when Schulman told Klein about King, he expected Klein to act \n\non the information. In making these inferences, a reasonable jury could consider \n\nSchulman’s varying explanations for his disapproval of Klein’s prior purchase of \n\nEnzo stock. Specifically, when Schulman was first interviewed by the SEC in \n\n2012, he testified, “I remember being a little upset at [Klein for buying Enzo \n\nstock,] because I think that the CEO [of Enzo] is a certifiable lunatic.” App. at 245. \n\nBut several years later, Schulman told the USAO that the reason he criticized \n\nKlein for buying Enzo stock was that it was improper to own shares of a client. \n\n\n\n 18 \n \n\f \nSee id. at 242. The jury could reasonably view Schulman’s second explanation as a \n\nconscious attempt to sanitize his first explanation, which had criticized only the \n\neconomic soundness of the investment, not its legality or propriety. \n\n  In addition, Schulman’s first, and perhaps more genuine explanation, \n\nprovides further context for the king‐for‐a‐day comment. For example, the jury \n\ncould reasonably infer from the Enzo evidence that, while Klein knew that \n\nSchulman had been upset at him for buying Enzo shares because the CEO was a \n\n“lunatic,” Klein understood that Schulman’s stating a wish to be “[K]ing for a \n\nday” meant that buying King shares was, in fact, given Schulman’s inside \n\ninformation, a good idea.  \n\n In this regard, it is also relevant that Schulman thought that Klein’s \n\ninvestments in 2009 and 2010 had been “too bearish,” id. at 241, since Schulman’s \n\ndesire to invest more aggressively, along with his view of Klein’s Enzo purchase \n\nas unwise, could be viewed as fueling a desire by Schulman to help Klein achieve \n\ngreater returns in Schulman’s portfolio. And while Schulman argues that $15,000 \n\nwas so insignificant a fraction of his overall net worth that it could not have been \n\nan incentive for him to tip Klein, that sizable net worth entitled the jury to \n\n\n\n 19 \n \n\f \ndisbelieve Schulman’s preferred explanation that he made his king‐for‐a‐day \n\ncomment simply to “show off.” Appellant’s Br. at 22.  \n\n Finally, Schulman contends that he is entitled to a judgment of acquittal \n\nbecause the evidence supporting the inference that he intended Klein to trade on \n\nhis tip about King is, at the very least, in equipoise with evidence supporting an \n\ninference that he intended merely to boast. But it is not. Schulman cites mainly \n\nthe absence of evidence of any follow‐up conversations with Klein. This absence \n\nof evidence at best supports an inference that Schulman did not intend for Klein \n\nto trade for Schulman’s benefit. It says little, if anything, about whether \n\nSchulman intended Klein to trade for Klein’s benefit, an independent basis upon \n\nwhich a rational jury could have found Schulman guilty.3 Moreover, we know of \n\nno requirement in insider trading law that the government adduce evidence of \n\nmultiple conversations between co‐conspirators, or that the government provide \n\ndirect testimonial evidence regarding a defendant’s intent. See Lorenzo, 534 F.3d \n\n\n\n                                               \n\n 3  The Government argued at trial that Martoma’s “personal benefit” requirement \n was satisfied both because Schulman intended to receive a financial benefit and because \n Schulman intended to make a “gift” to Klein. The district court instructed the jury on \n both theories. \n\n 20 \n\f \nat 159 (the government “is entitled to prove its case solely through circumstantial \n\nevidence”).  \n\n CONCLUSION \n\n After conducting an independent review of the record and considering the \n\nevidence as a whole, we conclude that a rational trier of fact could have found \n\nthat Schulman acted with the requisite intent beyond a reasonable doubt. We \n\nhave considered all of Schulman’s contentions on appeal and have found in them \n\nno basis for reversal. Accordingly, the judgment of the district court is \n\nAFFIRMED. \n\n\n\n\n 21\n[END_CASE]", "role": "user" } ]
4,580,407
Adam J. STARKE, Individually and on Behalf of All Others Similarly Situated, Plaintiff-Appellee, v. SQUARETRADE, INC., Defendant-Appellant
Starke v. SquareTrade, Inc.
2019-01-10
Docket 17-2474-cv; August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Lynch, Droney, Sessions", "parties": "", "opinions": [{"author": "GERARD E. LYNCH, Circuit Judge:", "type": "010combined", "text": "17-2474-cv\nStarke v. SquareTrade, Inc.\n\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE SECOND CIRCUIT\n\n\n\n August Term, 2017\n\n Argued: April 30, 2018 Decided: January 10, 2019\n\n Docket No. 17-2474-cv\n\n\n\n ADAM J. STARKE,\n Individually and On Behalf of All Others Similarly Situated,\n\n Plaintiff-Appellee,\n\n — v. —\n\n SQUARETRADE, INC.,\n\n Defendant-Appellant,\n\n\n\n\nB e f o r e:\n\n LYNCH and DRONEY, Circuit Judges, and SESSIONS, District Judge.*\n\n\n\n\n Appellant SquareTrade, Inc., appeals from the district court’s denial of its\nmotion to compel arbitration. SquareTrade argues that the governing terms of its\n\n\n*\n Judge William K. Sessions, III, of the United States District Court for the District\nof Vermont, sitting by designation.\n\fcontract with Appellee Adam J. Starke includes an arbitration clause. The district\ncourt concluded that the arbitration provision did not become part of the contract\nbecause Starke did not have reasonable notice of and manifest his assent to it.\nThe order of the district court is AFFIRMED.\n\n\n\n SOLOMON N. KLEIN (Bradley J. Nash, Schlam Stone & Dolan\n LLP, New York, NY; Mark Schlachet, Law Offices of Mark\n Schlachet, Cleveland, OH, on the brief) for Plaintiff-Appellee.\n\n DOUGLAS A. WINTHROP, Arnold & Porter Kaye Scholer LLP,\n San Francisco, CA (Michael D. Schissel, Arnold & Porter Kaye\n Scholer LLP, New York, NY; Elisabeth S. Theodore, Arnold &\n Porter Kaye Scholer LLP Washington, DC, on the brief) for\n Defendant-Appellant.\n\n\n\nGERARD E. LYNCH, Circuit Judge:\n\n Defendant-Appellant, SquareTrade, Inc., sells protection plans for\n\nconsumer products. Plaintiff-Appellee Adam J. Starke purchased one such\n\nprotection plan. Starke filed this putative class action, seeking to hold\n\nSquareTrade accountable for alleged violations of consumer protection laws.\n\nSquareTrade moved to compel arbitration, contending that its contract with\n\nStarke included an arbitration clause. Starke opposed the motion, arguing that\n\nthe purported arbitration clause had not become part of the contract because he\n\ndid not have reasonable notice of the clause and did not manifest assent to it. The\n\n\n\n 2\n\fUnited States District Court for the Eastern District of New York (Nicholas G.\n\nGaraufis, J.) denied SquareTrade’s motion, and SquareTrade appealed. For the\n\nreasons that follow, we AFFIRM.\n\n BACKGROUND1\n\n SquareTrade sells and administers service contracts called protection\n\nplans, which provide protections against defects and damage to a variety of\n\nconsumer products. Unlike warranties, which are provided by the product’s\n\nmanufacturer and are often included in the purchase price, SquareTrade\n\nprotection plans cover products made by other companies, and are sold for\n\nadditional consideration separate from the product price. SquareTrade markets\n\nand sells protection plans on its own website as well as through retailers\n\nincluding Costco, Target, Staples, Office Depot, and Amazon.\n\n As relevant here, Starke purchased the “SquareTrade 2-Year Electronics\n\nProtection Plan ($50-75)” (the “Protection Plan”) for $4.34 plus tax through\n\n\n\n1\n Courts deciding motions to compel apply a standard similar to the one\napplicable to a motion for summary judgment. Bensadoun v. Jobe-Riat, 316 F.3d\n171, 175 (2d Cir. 2003). On a motion for summary judgment, the court considers\nall relevant, admissible evidence submitted by the parties and contained in the\npleadings, depositions, answers to interrogatories, admissions and affidavits, and\ndraws all reasonable inferences in favor of the non-moving party. Nicosia v.\nAmazon.com, Inc., 834 F.3d 220, 229 (2d Cir. 2016).\n\n 3\n\fAmazon. Starke intended the Protection Plan to cover a CD player he had\n\npurchased from Staples for $61.83. Starke had previously purchased several\n\nSquareTrade protection plans through Amazon and one through Staples to cover\n\nother items.\n\n The Amazon webpage on which Starke purchased the Protection Plan\n\nlooked like this:\n\n\n\n\n 4\n\f5\n\f6\n\fApp’x at 113–14.2\n\n The portion of the purchase page copied above contains several sections of\n\ninformation about the Protection Plan. A block of text towards the top of the\n\npurchase page informed Starke that his “Service Contract [would] be delivered\n\nvia email and not mailed to [him]. It [would] come from SquareTrade Warranty\n\nServices . . . within 24 hours of purchase.” App’x at 113. Much further down in\n\nthe excerpted portion of the purchase page (which would likely require scrolling\n\non most computer screens), one encounters the heading: “Product information.”\n\nUnder that heading appears a small hyperlink labeled “Warranty [pdf].” The\n\n“Warranty” hyperlink provided access to a two-page document titled “Terms &\n\nConditions” stating: “Congratulations on purchasing this Protection Plan. Please\n\nread these terms and conditions carefully so that you fully understand your\n\ncoverage under this Protection Plan.” App’x at 40. The document contains terms\n\npurporting to govern the transaction, in addition to those terms appearing on the\n\nface of the Amazon purchase page. Notably, this document (the “Pre-Sale T&C”)\n\n\n\n\n2\n That is what the top half of the purchase page looked like. One who continued\nto scroll down the purchase page would come across additional customer\nquestions and answers, customer reviews, additional advertisements and\nbanners, and the Amazon.com footer. See App’x at 115–16.\n\n 7\n\fdid not contain an arbitration provision or a class action waiver.3 Starke did not\n\nclick on the “Warranty” hyperlink and therefore, did not review the Pre-Sale\n\nT&C. The Amazon purchase page did not contain a hyperlink to anything titled\n\n“Service Contract.”\n\n Slightly above the “Product information” was another heading,“Things to\n\nknow.” The first bullet point under this heading warns customers that\n\n“SquareTrade Protection Plans are only valid for new products purchased at\n\nAmazon within the last 30 days.” App’x at 114 (emphasis added). The fifth bullet\n\npoint under this heading informs customers that they “may cancel [their] plan\n\nanytime within the first 30 days for a full refund.” Id. Starke did not read that\n\npart of the purchase page and was not aware that the Protection Plan would not\n\ncover items that had not been purchased through Amazon.\n\n After his purchase, Starke received a confirmation email from Amazon\n\nwhich informed him that “[his] protection plan service agreement [would] be\n\n\n3\n SquareTrade represented to the district court that the Pre-Sale T&C document\nwas “an outdated version of SquareTrade’s Terms and Conditions.” App’x at 75.\nUpon realizing that the outdated version was posted on Amazon, as a result of\nthis lawsuit, SquareTrade contacted Amazon and requested that the updated\nversion—apparently containing an arbitration provision—be posted in its place.\nOn appeal, SquareTrade characterizes the Pre-Sale T&C as only a “sample” of\nSquareTrade’s terms and conditions. Appellant’s Br. at 5 n.1.\n\n 8\n\fsent via a separate e-mail by [the] seller.” App’x at 81. As the Amazon purchase\n\npage and confirmation email promised, Starke received an email from\n\nSquareTrade later that day. The email looked like this:\n\n\n\n\nApp’x at 83–84.\n\n\n\n 9\n\f The subject line of the email says “SquareTrade Protection Plan on\n\nAmazon.com - Contract is Enclosed.” The email contains several prompts and\n\ntext in various formats. As relevant to this case, the email contains a hyperlink in\n\nthe bottom left corner, labeled “Terms & Conditions,” that links to an eleven-\n\npage document titled “Protection Plan Terms & Conditions.” That document (the\n\n“Post-Sale T&C”) is a different document from the Pre-Sale T&C, and contains\n\nseveral provisions that were absent from the Pre-Sale T&C. One of the provisions\n\nappearing in the Post-Sale T&C but not the Pre-Sale T&C purports to bind the\n\nparties to arbitration of “[a]ny controversy or claim arising out of or relating to\n\nthis Protection Plan, or breach thereof . . . in accordance with the Commercial\n\nArbitration Rules of the American Arbitration Association.” App’x at 70. The\n\nPost-Sale T&C also contained a class action waiver and a California choice-of-law\n\nclause. Starke did not click on the “Terms & Conditions” hyperlink and did not\n\nreview the Post-Sale T&C. Nothing in the body of the email referred to\n\narbitration, and the email did not contain or refer to any attachments.4\n\n4\n According to Starke, following his prior purchases of SquareTrade protection\nplans on Amazon he had received, at most, confirmation emails that, at the very\nbottom, had links to Terms & Conditions, but that he never reviewed those\ndocuments. Starke’s explanation of the emails he received from SquareTrade on\nthese prior occasions is consistent with an affidavit submitted on behalf of\nSquareTrade indicating that SquareTrade’s purchase confirmation emails have\n\n 10\n\f After receiving the email, Starke followed the instructions directing him to\n\nsend SquareTrade a copy of the receipt for his electronics item. Starke alleges that\n\nthe receipt clearly stated that his CD player was purchased at Staples. Two days\n\nlater, SquareTrade confirmed that it had received a copy of his receipt.\n\n Some months later, Starke’s CD player required repair or replacement, and\n\nStarke made a claim for coverage under the Protection Plan. SquareTrade denied\n\nthe claim, notifying Starke that since the CD player had not been purchased\n\nthrough Amazon, it was not covered, and that his Protection Plan would be\n\ncancelled. SquareTrade offered Starke a refund for the full price of the Protection\n\nPlan.\n\n Shortly thereafter, Starke filed this putative class action against\n\nSquareTrade, alleging fraudulent and deceptive practices by SquareTrade in the\n\nselling and marketing of protection plans. The complaint seeks damages and\n\ninjunctive relief for violations of Sections 349 and 350 of New York’s General\n\nBusiness Law, and the Magnuson-Moss Warranty Act, 15 U.S.C. § 2301 et seq.,\n\n\n\nbeen delivered with substantially the same form and content since 2014. The one\ntime Starke purchased a SquareTrade protection plan through Staples, he\nreceived a confirmation email from SquareTrade with the terms and conditions\ngoverning the transaction in the body of the email. Those terms and conditions\ncontained neither an arbitration provision nor a class action waiver.\n\n 11\n\fand for unjust enrichment. Starke alleges that SquareTrade knowingly and\n\ndeceptively sells protection plans for items not purchased on Amazon and\n\ntherefore, not eligible for coverage, despite knowing that under the terms of the\n\nplan, which are not prominently disclosed, the products which its customers\n\nhave sought to protect are not eligible for coverage. According to the complaint,\n\nSquareTrade’s limiting of covered products to those purchased through Amazon\n\noperates as an intentionally deceptive scheme to take money from unsuspecting\n\ncustomers. If a SquareTrade customer never makes a claim under her plan,\n\nSquareTrade keeps her premium and retains the policy until expiration. But if the\n\ncustomer makes a claim that requires SquareTrade to honor the policy,\n\nSquareTrade informs the customer that her protection plan is void because the\n\nunderlying product was not purchased through Amazon.\n\n Starke also alleges that SquareTrade fails to disclose other material terms\n\nand restrictions prior to the sale, and hoodwinks customers by providing them\n\nwith pre-sale terms and conditions that differ from the more restrictive post-sale\n\nterms and conditions that are disclosed only after the purchase has been\n\ncompleted and only via a deliberately obscure hyperlink.\n\n In response, SquareTrade moved to stay the action and compel Starke to\n\n\n\n 12\n\farbitrate his claims individually, citing the arbitration clause and class action\n\nwaiver contained in the Post-Sale T&C. SquareTrade argued that Starke had\n\nreasonable notice of the Post-Sale T&C because the Amazon purchase page\n\nnotified him that he would receive his “Service Contract” via email, the email he\n\nreceived from SquareTrade contained a hyperlink to the Post-Sale T&C, and\n\nStarke manifested assent to the Post-Sale T&C by failing to return the Protection\n\nPlan within the 30-day window SquareTrade allowed. SquareTrade also argued\n\nthat Starke’s prior course of dealing with SquareTrade put him on notice of the\n\nPost-Sale T&C.\n\n The district court denied SquareTrade’s motion. The court applied New\n\nYork contract law to determine whether the parties had bound themselves to an\n\nenforceable arbitration agreement. First, the district court found that Starke did\n\nnot have actual knowledge of the arbitration provision in the Post-Sale T&C\n\nbecause he did not click on the “Terms & Conditions” hyperlink in the\n\nSquareTrade confirmation email and read the hyperlinked document. Then the\n\ncourt considered whether Starke (1) had reasonable notice of the Post-Sale T&C\n\nand (2) offered an objective manifestation of assent to the Post-Sale T&C.\n\n In determining whether Starke had reasonable notice of the Post-Sale T&C\n\n\n\n 13\n\fand manifested assent to such terms and conditions, the district court applied the\n\ntest adopted in Berkson v. Gogo LLC, 97 F. Supp. 3d 359, 402–03 (E.D.N.Y. 2015).5\n\nUnder that test, according to the district court, the court assesses four factors: (1)\n\nwhether Starke was aware that he was binding himself to more than an offer of\n\ngoods or services in exchange for money; (2) whether the design and content of\n\nthe SquareTrade confirmation email made the Post-Sale T&C readily and\n\nobviously available; (3) whether SquareTrade required any affirmative\n\nmanifestation of agreement to the Post-Sale T&C; and (4) whether SquareTrade\n\nclearly drew the consumer’s attention to the Post-Sale T&C in general or the\n\narbitration provision in particular.\n\n As to the first factor, the district court concluded that Starke had\n\nreasonable notice that some contractual terms would be forthcoming because he\n\nset out to purchase a service contract. But, the district court noted, Starke’s\n\nknowledge of the existence of some contractual terms did not necessarily mean\n\nthat he could reasonably be expected to discern and agree to all of the contractual\n\nterms to which SquareTrade intended to bind him.\n\n\n\n5\n The Berkson court applied the substantive contract law of New York, California,\nand Illinois, and determined that “these states[’] laws are substantively similar\nwith respect to . . . contract formation.” Berkson, 97 F. Supp. 3d at 388.\n\n 14\n\f The second, third, and fourth factors, according to the district court,\n\ncounseled against finding reasonable notice and manifestation of assent. The\n\ndistrict court found that the design and content of the SquareTrade confirmation\n\nemail did not make the Post-Sale T&C readily and obviously available, because it\n\ndid not draw any attention to the inconspicuously placed Terms & Conditions\n\nhyperlink in small font at the very bottom of the email. Rather, a reasonable\n\nperson in Starke’s position would have thought that the body of the email\n\nconstituted the contract itself. Given that the terms of the contract were obscured\n\nand minimized, the district court held that Starke could not have evidenced a\n\nclear manifestation of assent. Lastly, the district court noted that SquareTrade did\n\nnot draw Starke’s attention to the arbitration provision buried in the Post-Sale\n\nT&C. The district court, therefore, held that SquareTrade failed to establish an\n\nenforceable arbitration agreement with Starke, and denied its motion to compel\n\narbitration.6\n\n SquareTrade timely appealed the district court’s order pursuant to 9 U.S.C.\n\n§ 16(a)(1)(C), which permits an interlocutory appeal from the denial of a motion\n\n\n\n6\n Because the district court concluded that there was no enforceable agreement to\narbitrate, it declined to assess the scope of the arbitration provision or the validity\nof the class action waiver.\n\n 15\n\fto compel arbitration. On December 15, 2017, the district court stayed the\n\nunderlying action pending the outcome of this appeal.\n\n DISCUSSION\n\nI. Standard of Review\n\n We review the district court’s denial of a motion to compel arbitration de\n\nnovo where the denial is based on a legal conclusion about whether the parties\n\ncontractually bound themselves to arbitrate. See Meyer v. Uber Techs., Inc., 868\n\nF.3d 66, 72–73 (2d Cir. 2017). Since the district court’s conclusions regarding\n\nnotice and assent were based on undisputed facts, those conclusions are also\n\nsubject to de novo review. Id. at 73 (holding de novo review appropriate where the\n\nevidence “consists exclusively of screenshots from the Web site and order\n\nconfirmation email, and the authenticity of these screenshots is not subject to\n\nfactual dispute”).\n\n “Where the undisputed facts in the record require the matter of\n\narbitrability to be decided against one side or the other as a matter of law, we\n\nmay rule on the basis of that legal issue and avoid the need for further court\n\nproceedings.” Wachovia Bank, Nat’l Ass’n v. VCG Special Opportunities Master Fund,\n\nLtd., 661 F.3d 164, 172 (2d Cir. 2011) (internal quotation marks omitted).\n\n\n 16\n\fII. Governing Legal Principles\n\n The Federal Arbitration Act (“FAA”) provides that written agreements to\n\narbitrate are “valid, irrevocable, and enforceable, save upon such grounds as\n\nexist at law or in equity for the revocation of any contract.” 9 U.S.C. § 2. The FAA\n\n“is a congressional declaration of a liberal federal policy favoring arbitration\n\nagreements, notwithstanding any state substantive or procedural policies to the\n\ncontrary.” Moses H. Cone Mem’l Hosp. v. Mercury Constr. Corp., 460 U.S. 1, 24\n\n(1983). This policy is founded upon “a desire to preserve parties’ ability to agree\n\nto arbitrate, rather than litigate, [their] disputes.” Schnabel v. Trilegiant Corp., 697\n\nF.3d 110, 118 (2d Cir. 2012).\n\n But despite the strong federal policy favoring arbitration, arbitration\n\nremains a creature of contract. See Howsam v. Dean Witter Reynolds, Inc., 537 U.S.\n\n79, 83 (2002); AT&T Mobility LLC v. Concepcion, 563 U.S. 333, 339 (2011)\n\n(reiterating that it is a “fundamental principle” of the FAA that “arbitration is a\n\nmatter of contract”) (quoting Rent-A-Center, West, Inc. v. Jackson, 561 U.S. 63, 67\n\n(2010)). Thus, courts must still decide whether the parties to a contract have\n\nagreed to arbitrate disputes. Schnabel, 697 F.3d at 118 (“The threshold question\n\nfacing any court considering a motion to compel arbitration is . . . whether the\n\n\n 17\n\fparties have indeed agreed to arbitrate.”); Specht v. Netscape Commc’ns Corp., 306\n\nF.3d 17, 26 (2d Cir. 2002) (observing that it is “well-settled that a court may not\n\ncompel arbitration until it has resolved the question of the very existence of the\n\ncontract embodying the arbitration clause”) (internal quotation marks omitted).\n\nThat question is governed by state-law principles of contract formation. Here, the\n\nparties agree that New York contract law applies.\n\n It is a basic tenet of contract law that, in order to be binding, a contract\n\nrequires a “meeting of the minds” and “a manifestation of mutual assent.” See\n\nExpress Indus. & Terminal Corp. v. N.Y. Dep’t of Transp., 93 N.Y.2d 584, 589 (N.Y.\n\n1999). The manifestation of mutual assent must be sufficiently definite to assure\n\nthat the parties are truly in agreement with respect to all material terms. See\n\nJoseph Martin, Jr., Delicatessen, Inc. v. Schumacher, 52 N.Y.2d 105, 109 (N.Y. 1981);\n\nRegister.com, Inc. v. Verio, Inc., 356 F.3d 393, 427 (2d Cir. 2004) (“Mutual assent is\n\nessential to the formation of a contract and a party cannot be held to have\n\ncontracted if there was no assent or acceptance.”). These requirements assure that\n\nthe judiciary can enforce the parties’ mutually-agreed terms and conditions when\n\none party seeks to uphold them against the other. Express Indus., 93 N.Y.2d at 589.\n\nGenerally, courts look to the basic elements of the offer and the acceptance to\n\n\n 18\n\fdetermine whether there was an objective meeting of the minds sufficient to give\n\nrise to a binding and enforceable contract. Id.\n\n Where an offeree does not have actual notice of certain contract terms, he is\n\nnevertheless bound by such terms if he is on inquiry notice of them and assents to\n\nthem through conduct that a reasonable person would understand to constitute\n\nassent. See Schnabel, 697 F.3d at 120. In determining whether an offeree is on\n\ninquiry notice of contract terms, New York courts look to whether the term was\n\nobvious and whether it was called to the offeree’s attention. See 22 N.Y. Jur. 2d\n\nContracts § 29 (“[A] party should not be bound by clauses printed on the reverse\n\nside of a contract unless it is established that they were properly called to his or her\n\nattention and that he or she assented to them.”) (emphasis added). This often\n\nturns on whether the contract terms were presented to the offeree in a clear and\n\nconspicuous way. See, e.g., Gildor v. USPS, 179 F. App’x 756, 759–60 (2d Cir. 2006)\n\n(refusing to enforce contract provision incorporated on reverse side of postage\n\nlabel where the provision was “very small and difficult to read”); Arthur Philip\n\nExport Corp. v. Leathertone, Inc., 87 N.Y.S.2d 665, 667 (1st Dep’t 1949) (refusing to\n\nenforce contract terms that were inconspicuously placed in “small type and in\n\nparenthesis” on the back of a confirmation order).\n\n 19\n\f We apply these same contract law principles to online transactions. See\n\nRegister.com, 356 F.3d at 404 (“While new commerce on the Internet has exposed\n\ncourts to many new situations, it has not fundamentally changed the principles of\n\ncontract.”); Specht, 306 F.3d at 31 (“These principles apply equally to the\n\nemergent world of online product delivery, pop-up screens, hyperlinked pages,\n\nclickwrap licensing, scrollable documents, and urgent admonitions to\n\n“Download Now!”); Resorb Networks, Inc. v. YouNow.com, 30 N.Y.S.3d 506, 511\n\n(N.Y. Sup. Ct. 2016) (noting that when evaluating a transaction occurring online,\n\ncourts focus on “whether a reasonably prudent offeree would be on notice of the\n\nterm at issue” and whether the terms of the agreement were “reasonably\n\ncommunicated to the user,” because assent is mostly passive online).\n\n In the context of web-based contracts, we look to the design and content of\n\nthe relevant interface to determine if the contract terms were presented to the\n\nofferee in way that would put her on inquiry notice of such terms. See Nguyen v.\n\nBarnes & Noble Inc., 763 F.3d 1171, 1177 (9th Cir. 2014) (“Where the link to a\n\nwebsite’s terms of use is buried at the bottom of the page or tucked away in\n\nobscure corners of the website where users are unlikely to see it, courts have\n\nrefused to enforce the [] agreement.”); Specht, 306 F.3d at 23 (refusing to enforce\n\n\n 20\n\fterms of use that “would have become visible to plaintiffs only if they had\n\nscrolled to the next screen”).\n\n In Nicosia, 834 F.3d at 233–38, we examined an Amazon order page to\n\ndetermine if it put a consumer on constructive notice of Amazon’s “Conditions of\n\nUse,” which contained an arbitration clause.7 The Amazon order page looked like\n\nthis:\n\n\n\n\n7\n In Nicosia, we applied Washington law on the question of contract formation, id.\nat 231, but Washington law is the same as New York law with respect to the issue\nof contract formation, see id. at 232.\n\n 21\n\fId. at 241 (Addendum B).\n\n Amazon claimed that an arbitration provision contained in the “conditions\n\nof use” hyperlink (at the top of the page under the “Review your order” heading)\n\nwas part of the contract it formed with the customer who placed an order on this\n\n\n 22\n\fpage. Several features of the order page’s design and content were relevant to\n\nour analysis of whether the customer had inquiry notice of the terms at this\n\nhyperlink:\n\n • The message “By placing your order, you agree to\n Amazon.com’s . . . conditions of use” was not bold,\n capitalized, or conspicuous in light of the whole\n webpage. Id. at 237.\n\n • Numerous other links on the webpage, in several\n different colors, fonts, and locations, generally\n obscured the message. Id.\n\n • Multiple buttons and promotional advertisements on\n the order page drew attention away from the message.\n Id.\n\n • The presence of customers’ personal address, credit\n card information, shipping options, and purchase\n summary were distracting. Id.\n\n Given these features of the order page, we held that reasonable minds\n\ncould disagree regarding whether the customer was on inquiry notice of an\n\narbitration provision contained in Amazon’s Conditions of Use. Id. at 237. We\n\ntherefore left it up to the factfinder to determine whether, when the customer\n\nclicked the “Place your order” button, she had manifested assent to the\n\narbitration provision contained at the “conditions of use” hyperlink. Id. at 236–37.\n\n\n\n 23\n\f More recently, in Meyer, we had to determine whether a user signing up\n\nfor an Uber account was on inquiry notice of an arbitration provision contained\n\nin Uber’s “Terms of Service,” which were provided to the user via Uber’s\n\nsmartphone interface. 868 F.3d 66.8 The “Terms of Service” were hyperlinked to\n\nthe sign-up screen in an interface that looked like this:\n\n\n\n\n8\n The Meyer Court applied California law to the contract formation question, but\nnoted that “New York and California apply substantially similar rules for\ndetermining whether the parties have mutually assented to a contract term.” Id.\nat 74 (internal quotations omitted).\n\n 24\n\fId. at 82 (Addendum B).\n\n We concluded that this interface did provide reasonable notice of the\n\ncontract terms contained in the “TERMS OF SERVICE & PRIVACY POLICY”\n\nhyperlink because the hyperlink was clear and conspicuous. Id. at 77–78. In so\n\nconcluding, we noted the following things about the design of the screen and the\n\nlanguage used:\n\n • The payment screen was uncluttered with only fields\n for the user to enter his or her credit card details,\n buttons to register for a user account or to connect to\n the user’s pre-existing PayPal account or Google\n Wallet to the Uber account, and the warning that “By\n creating an Uber account, you agree to the TERMS OF\n SERVICE & PRIVACY POLICY.” Id. at 78.\n\n • The text, including the hyperlinks to the Terms and\n Conditions and Privacy Policy, appeared directly\n below, i.e., was “spatially coupled” with the\n registration button. Id.\n\n • The entire screen was visible at once, and thus the user\n did not need to scroll beyond what was immediately\n visible to find notice of the Terms of Service. Id.\n\n • The register button was “temporally coupled” with\n the hyperlink – i.e., the consumer was notified of the\n terms at the time of sale. Id.\n\n • The language “[b]y creating an Uber account, you\n agree” was a clear prompt directing the users to read\n\n 25\n\f the Terms and Conditions and signaling that their\n acceptance of the benefit of registration would be\n subject to contractual terms. Id. at 79.\n\n These factors led us to conclude that the user had been provided with\n\nobjectively reasonable notice of the terms contained at the “TERMS OF\n\nSERVICE” hyperlink. And, since a reasonable user would know that by clicking\n\nthe registration button he was agreeing to the terms and conditions accessible via\n\nthe hyperlink, regardless of whether he actually clicked the hyperlink, we\n\ncompelled arbitration. Id. at 79–80.\n\n The reasoning of Nicosia and Meyer provides the framework within which\n\nwe analyze the validity of assent to terms and conditions presented through a\n\nweb interface.\n\nIII. Reasonable Notice of the Arbitration Provision\n\n To determine whether Starke had reasonable notice of the arbitration\n\nprovision, we must analyze whether the Post-Sale T&C were provided to Starke\n\nin a clear and conspicuous way.9 See Meyer, 868 F.3d at 75. Several things about\n\nthe transaction and the email Starke received from SquareTrade following the\n\n\n\n9\n The district court found that Starke “did not have actual notice” of the\narbitration provision, and SquareTrade does not dispute that finding.\n\n 26\n\fAmazon confirmation email lead us to conclude that Starke did not have\n\nreasonable notice of the arbitration provision, which was contained only in the\n\nPost-Sale T&C.\n\n First, SquareTrade never directed Starke’s attention to the “Terms &\n\nConditions” hyperlink that contained the Post-Sale T&C. The first screen Starke\n\nencountered during the course of the transaction, the Amazon purchase page,\n\ndid not provide Starke with notice that terms governing the sale would be\n\nprovided via hyperlink. Instead, the Amazon purchase page notified Starke that\n\nhe would receive something called a “Service Contract” via email. Then, Starke\n\nreceived an email from Amazon, notifying him that he would receive a “service\n\nagreement” from SquareTrade. Starke subsequently received an email from\n\nSquareTrade indicating that his “Contract” was enclosed. None of these various\n\ncommunications put Starke on notice that his “Service Contract” would come in\n\nthe form of a hyperlink, rather than in the body of the email.\n\n Second, when Starke opened the email from SquareTrade he was\n\npresented with a chart titled “Your Protection Plan.” The chart described the\n\nparticular Protection Plan that Starke purchased, and identified the “Coverage\n\nAmount,” “Protection Plan Price,” “Coverage Type,” “Covered Product,”\n\n\n 27\n\f“Deductible,” “Quantity,” “Coverage Term,” “Coverage Start Date,” “Coverage\n\nEnd Date,” and “Waiting Period.” This information took up approximately half\n\nof the email.10 Nothing else in the email stands out as obviously being related to\n\nStarke’s Protection Plan, and none of the language in the cluttered email directed\n\nStarke’s attention to the hyperlink containing the Post-Sale T&C.\n\n Third, the SquareTrade email bears more resemblance to the Amazon\n\norder page in Nicosia, 834 F.3d at 237, than to the uncluttered screen in Meyer, 868\n\nF.3d at 78. The “Terms & Conditions” hyperlink is some of the smallest text in the\n\n\n10\n SquareTrade argues that Starke could not have believed that the “Your\nProtection Plan” chart was his “Contract” because the chart itself referenced\nmore detailed terms and conditions. Specifically, SquareTrade notes that the\n“Coverage Amount” is defined in the chart as “[u]p to the maximum coverage\nprice of the Protection Plan, or the purchase price of your item, whichever is\nlower,” and the “Coverage Type” is listed as “Standard.” Without more,\nSquareTrade says, those terms would be meaningless.\n But the language in the chart does not obviously point to additional details\nin another document. In fact, the terms that SquareTrade references are not even\nelucidated in the actual contract at the hyperlink. “Coverage Type” is defined in\nthe Terms & Conditions only as “the level of coverage You purchased, such as\nwhether Your Protection Plan includes Optional Coverage, such as Accidental\nDamage from Handling (ADH) coverage,” App’x at 103, but nowhere does it\ndescribe the contents of “Standard” coverage, App’x at 83. Nor is there mention\nof the “coverage price of this Protection Plan” in the contract, such that Starke\ncould compare it to the “purchase price of [his] item.” App’x at 103. And, even if\nStarke thought that those terms could be defined in greater detail elsewhere,\nthere was no reason for him to believe that such detail was available in the\nSquareTrade email, let alone the “Terms & Conditions” hyperlink.\n\n 28\n\femail and comes after several prompts unrelated to the enclosure of the contract,\n\nincluding a “Need help?” hyperlink, a button for Starke to log in to his\n\nSquareTrade account, a hyperlink for Starke to submit the receipt for his CD\n\nplayer, the chart with details of the plan, and a banner urging Starke to review\n\nthe Protection Plan on Amazon. Like the interface in Nicosia, and in sharp\n\ncontrast with the screen in Meyer, the interface here is cluttered with diverse text,\n\ndisplayed in multiple colors, sizes and fonts, and features various buttons and\n\npromotional advertisements that distract the reader from the relevant hyperlink.\n\nSee Specht, 306 F.3d at 31–32 (finding no inquiry notice of contract terms that were\n\nprovided via hyperlink at the very bottom of the Netscape webpage which\n\ndistracted viewer with praise for the product and a “Download” button).\n\n Moreover, unlike in Meyer, the SquareTrade email in no way signals to\n\nStarke that he should click on the link, and it does not advise him that he would\n\nbe deemed to agree to the contract terms in the document to be found by clicking\n\nthat link. Nor does the email instruct him that the hyperlink is where his\n\npromised service contract can be found. The “Terms & Conditions” hyperlink\n\nappears without any “language advising [Starke] to click on [it],” Starkey, 796\n\nF.3d at 197, or a “clear prompt directing [Starke] to read the Terms and\n\n\n 29\n\fConditions,” Meyer, 868 F.3d at 79. The hyperlink was buried at the bottom of the\n\nemail directly above the email footer. Far above the hyperlink, the second\n\nsentence of the email told Starke “You’re all set!” encouraging him to look no\n\nfurther. The placement of the “Terms & Conditions” hyperlink in the email\n\nmakes it hard to escape the inference that SquareTrade hoped the reader’s eye\n\nwould be drawn elsewhere.\n\n This case is also distinguishable from Meyer because here, the “Terms &\n\nConditions” hyperlink was neither spatially nor temporally coupled with the\n\ntransaction. The “Terms & Conditions” hyperlink was spatially decoupled from\n\nthe transaction because it was not provided near the portion of the Amazon\n\npurchase page actually requiring Starke’s attention (that is, the “Add to Cart”\n\nbutton), or indeed anywhere on the purchase page. To provide conspicuous\n\nnotice of the Post-Sale T&C, SquareTrade could have simply included a\n\nnoticeable hyperlink on the Amazon purchase page directing consumers to\n\nreview the terms and conditions. See, e.g., Nicosia, 834 F.3d at 237–38 (noting that\n\n“Amazon chose not to employ a clickwrap mechanism,” which is “certainly the\n\neasiest method of ensuring that terms are agreed to”); Starkey, 796 F.3d at 197 n.3\n\n(noting that it would have been “simpler to resolve” this question had a\n\n\n 30\n\fclickwrap mechanism been used). And, even if SquareTrade was committed to\n\nproviding the Post-Sale T&C via email, it could have done so in several more\n\nconspicuous ways, including by providing the Post-Sale T&C in the body of the\n\nemail, providing an attachment to the email with the Post-Sale T&C, or by\n\nproviding the “Terms & Conditions” hyperlink at the top of the email in a bigger\n\nfont notifying the customer that the hyperlink is where he will find his “Service\n\nContract,” and that by rejecting the Protection Plan within the specific period, he\n\nwould be deemed to have accepted those terms.11\n\n\n\n11\n SquareTrade’s argument that internet users know how hyperlinks work misses\nthe point. The issue here is not that the Post-Sale T&C were provided via\nhyperlink. The problem is that the hyperlink was obscured and SquareTrade did\nnothing to alert Starke to the fact that this hyperlink contained his “Service\nContract.” See Hines v. Overstock.com, Inc., 668 F. Supp. 2d 362, 367 (E.D.N.Y. 2009)\n(finding contract term contained in hyperlink unenforceable where hyperlink\nwas not prominently displayed on the website and there was nothing prompting\nthe user to click on hyperlink); In re Zappos.com, Inc., 893 F. Supp. 2d 1058, 1064\n(D. Nev. 2012) (finding plaintiff did not manifest assent to contract terms\ncontained in hyperlink where the hyperlink was “inconspicuous, buried in the\nmiddle to bottom of every . . . webpage among many other links, and the website\nnever direct[ed] a user to the Terms of Use”); cf. Meyer, 868 F.3d at 79 (“As long as\nthe hyperlinked text was itself reasonably conspicuous—and we conclude that it\nwas—a reasonably prudent smartphone user would have constructive notice of\nthe terms.”) (emphasis added); Starkey v. G Adventures, Inc., 796 F.3d 193, 197 (2d\nCir. 2015) (finding terms enforceable where the email containing the “TERMS\nAND CONDITIONS” hyperlink directed the plaintiff to read the hyperlinked\ndocument).\n\n 31\n\f The Post-Sale T&C were also temporally decoupled from the transaction.\n\nStarke purchased the Protection Plan from the Amazon website, but he had no\n\nway to review the Post-Sale T&C until he received the SquareTrade confirmation\n\nemail. In Meyer, 868 F.3d at 78–80, we placed significant weight on the fact that\n\nthe “Terms of Service” hyperlink was temporally coupled with the register\n\nbutton. For one, that meant that the user could not avoid noticing the hyperlink\n\nwhen she registered for an account. But importantly, that also allowed the\n\nplaintiff “to review the Terms of Service prior to registration, unlike web\n\nplatforms that provide notice of contract terms only after the user manifested his\n\nor her assent.” Id. at 80. (emphasis added).\n\n In defense of its pay-now-terms-later approach, SquareTrade notes that\n\nNew York Insurance Law, which creates the legal framework within which\n\nservice contracts may be sold in the state, permits sellers to provide customers\n\nwith the contract governing their transactions within a reasonable amount of\n\ntime after the purchase. See N.Y. Ins. Law § 7903(b)(1). The law requires that\n\nconsumers be provided at least twenty days after the service contract has been\n\nmailed to return the contract to the seller for a full refund. Id. at § 7903(e).\n\nSquareTrade points out that it provided Starke with thirty days within which to\n\n\n 32\n\freturn his contract. However, Section 7903 is a regulatory regime that imposes\n\ncertain disclosure responsibilities and other duties on sellers of service contracts,\n\nbut it does not appear to alter New York law as to the manifestation of assent in\n\ncontract formation. Nor has SquareTrade provided authority to support the\n\nproposition that it does.\n\n Under general principles of contract law, moreover, providing contract\n\nterms after a transaction has taken place may be an appropriate way to contract\n\nin certain situations. But we find little justification for it here, where it would\n\nhave been virtually costless for SquareTrade to provide the governing terms and\n\nconditions to Starke before he bought the Protection Plan. See Schnabel, 697 F.3d\n\nat 126–28 (noting that there was no policy rationale for a “terms later by email”\n\nconception of contract formation under the circumstances). Indeed, SquareTrade\n\ndid provide a hyperlink to the Pre-Sale T&C, which do not contain the terms that\n\nSquareTrade seeks to enforce, on the Amazon purchase page.12 But, had Starke\n\n\n\n12\n We do not mean to suggest that the “Warranty” hyperlink provided sufficient\nnotice of the Pre-Sale T&C, since that hyperlink was itself buried on the busy\nAmazon purchase page amidst various other hyperlinks, banner advertisements,\nand customer reviews, among other things. The point is merely that a consumer\nwho clicked on that link would have been misled about the terms governing the\ntransaction.\n\n 33\n\fclicked on the “Warranty” hyperlink on the Amazon purchase page, he would\n\nhave been taken to a document containing the Pre-Sale T&C, which set forth\n\nwhat would have appeared to be a complete recitation of the terms of the\n\ncontract between the purchaser and SquareTrade. A consumer reviewing the Pre-\n\nSale T&C would have reasonably believed that his contract did not contain an\n\narbitration provision.\n\n Of course, Starke, like any other offeree, had a duty to read the terms of the\n\ncontract presented to him, including contract terms provided post-sale. But cases\n\napplying the duty-to-read principle still require that the offeree be put on notice\n\nof the existence of additional contract terms before it can be said that he has\n\nassented to them. See Schnabel, 697 F.3d at 124; Specht, 306 F.3d at 30 (“An\n\nexception to [the duty to read] rule exists when the writing does not appear to be\n\na contract and the terms are not called to the attention of the recipient.”). Thus,\n\nthe duty to read does not morph into a duty to ferret out contract provisions\n\nwhen they are contained in inconspicuous hyperlinks. See Nguyen, 763 F.3d at\n\n1179 (“Given the breadth of the range of technological savvy of online\n\npurchasers, consumers cannot be expected to ferret out hyperlinks to terms and\n\nconditions to which they have no reason to suspect they will be bound.”). That is\n\n\n 34\n\fparticularly so where, as here, the consumer was presented with several\n\ndocuments including the Pre-Sale T&C, the body of the subsequent email, and\n\nthe Post-Sale T&C, none of them specifically identified as the “Service Contract”\n\ngoverning the purchase, and all containing different sets of terms.\n\nIV. Starke’s Prior Course of Dealing with SquareTrade\n\n Finally, SquareTrade points to the prior course of dealing between Starke\n\nand SquareTrade to demonstrate that Starke was on inquiry notice of terms and\n\nconditions that he would receive via email. SquareTrade relies on Register.com,\n\n356 F.3d 393, where this Court found that a prior course of dealing between the\n\nparties supported the conclusion that they had agreed to certain terms and\n\nconditions. In Register.com, the party challenging the applicability of the terms\n\nand conditions was a sophisticated corporate customer that had made “daily”\n\nuse of its counter-party’s services subject to the terms and conditions, and had\n\nbeen “fully aware” of the terms and conditions that the counter-party sought to\n\nenforce. Id. at 402. We compared the situation before us then to one in which a\n\nperson maintains a roadside fruit stand displaying bins of apples with a sign at\n\nthe exit of the fruit stand telling customers that the apples are 50 cents each. Id. at\n\n401. We said that a visitor who comes, takes an apple, bites into it, and does not\n\n 35\n\fsee the sign until he exits may well believe he has no obligation to pay for the\n\napple because he had no notice when he bit into it that 50 cents was expected in\n\nreturn. Id. However, if the visitor returns to the apple stand on a daily basis, each\n\nday taking an apple without paying for it, he cannot later use the same defense.\n\nId. Based on his prior transaction(s), he knows full well that the owner is offering\n\napples in exchange for 50 cents. Id.\n\n Unlike the apple stand visitor, who learns of the terms governing his\n\ncontract with the owner and feigns ignorance that the same terms will apply in\n\nfuture transactions, Starke was not put on notice of SquareTrade’s terms and\n\nconditions through his prior transactions. Although Starke had transacted with\n\nSquareTrade on six prior occasions, SquareTrade never gave Starke clear and\n\nconspicuous notice that the transaction would subject him to binding arbitration.\n\nEach time Starke purchased a SquareTrade protection plan through Amazon, he\n\nreceived a confirmation email from SquareTrade which looked just like the\n\nconfirmation email at issue here. The fact that Starke received emails with the\n\nsame inconspicuous hyperlink on more than one occasion does not lead us to\n\nconclude that Starke had either actual or inquiry notice of the Post-Sale T&C.\n\n\n\n\n 36\n\f On only one occasion (when Starke purchased a SquareTrade protection\n\nplan through Staples) did Starke receive an email from SquareTrade in which the\n\nterms and conditions were actually provided in the body of the email. In that\n\ninstance, however, the terms and conditions in the email did not contain an\n\narbitration provision, so that transaction could not have put Starke on notice of\n\nsuch term. Starke notes that when SquareTrade introduced an arbitration clause\n\ninto its terms and conditions, it pivoted to providing its terms and conditions via\n\na nondescript hyperlink. Thus, the prior course of dealing between Starke and\n\nSquareTrade by no means resembles the apple hypothetical in Register.com, and it\n\ndoes not convince us that Starke was on inquiry notice of the arbitration\n\nprovision contained in the Post-Sale T&C.\n\n We emphasize that we in no way hold that the terms of a contract may not\n\nbe provided by a hyperlinked document. So long as the purchaser’s attention is\n\nadequately directed to a conspicuous hyperlink that is clearly identified as\n\ncontaining contractual terms to which the customer manifests assent by\n\ncompleting the transaction or retaining the product or service, a hyperlink can be\n\nan effective device for specifying contract terms. Nor do we hold that the format\n\nused in Meyer is the only effective way to use hyperlinks (though we note that the\n\n\n 37\n\fclean, uncluttered, and conspicuous labeling of the location and binding nature\n\nof the terms in the hyperlinked document can be used as a model that this Court\n\nhas found effective). We hold merely that on the totality of the circumstances in\n\nthis case, Starke was not on sufficient notice of the terms of the Post-Sale T&C,\n\nincluding its arbitration clause, and therefore did not manifest assent to those\n\nterms.\n\n CONCLUSION\n\n For the reasons stated above, we AFFIRM the order of the district court,\n\ndenying SquareTrade’s motion to compel arbitration.\n\n\n\n\n 38", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357660/", "author_raw": "GERARD E. LYNCH, Circuit Judge:"}]}
LYNCH
DRONEY
SESSIONS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580407/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Adam J. STARKE, Individually and on Behalf of All Others Similarly Situated, Plaintiff-Appellee, v. SQUARETRADE, INC., Defendant-Appellant\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17-2474-cv\nStarke v. SquareTrade, Inc.\n\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE SECOND CIRCUIT\n\n\n\n August Term, 2017\n\n Argued: April 30, 2018 Decided: January 10, 2019\n\n Docket No. 17-2474-cv\n\n\n\n ADAM J. STARKE,\n Individually and On Behalf of All Others Similarly Situated,\n\n Plaintiff-Appellee,\n\n — v. —\n\n SQUARETRADE, INC.,\n\n Defendant-Appellant,\n\n\n\n\nB e f o r e:\n\n LYNCH and DRONEY, Circuit Judges, and SESSIONS, District Judge.*\n\n\n\n\n Appellant SquareTrade, Inc., appeals from the district court’s denial of its\nmotion to compel arbitration. SquareTrade argues that the governing terms of its\n\n\n*\n Judge William K. Sessions, III, of the United States District Court for the District\nof Vermont, sitting by designation.\n\fcontract with Appellee Adam J. Starke includes an arbitration clause. The district\ncourt concluded that the arbitration provision did not become part of the contract\nbecause Starke did not have reasonable notice of and manifest his assent to it.\nThe order of the district court is AFFIRMED.\n\n\n\n SOLOMON N. KLEIN (Bradley J. Nash, Schlam Stone & Dolan\n LLP, New York, NY; Mark Schlachet, Law Offices of Mark\n Schlachet, Cleveland, OH, on the brief) for Plaintiff-Appellee.\n\n DOUGLAS A. WINTHROP, Arnold & Porter Kaye Scholer LLP,\n San Francisco, CA (Michael D. Schissel, Arnold & Porter Kaye\n Scholer LLP, New York, NY; Elisabeth S. Theodore, Arnold &\n Porter Kaye Scholer LLP Washington, DC, on the brief) for\n Defendant-Appellant.\n\n\n\nGERARD E. LYNCH, Circuit Judge:\n\n Defendant-Appellant, SquareTrade, Inc., sells protection plans for\n\nconsumer products. Plaintiff-Appellee Adam J. Starke purchased one such\n\nprotection plan. Starke filed this putative class action, seeking to hold\n\nSquareTrade accountable for alleged violations of consumer protection laws.\n\nSquareTrade moved to compel arbitration, contending that its contract with\n\nStarke included an arbitration clause. Starke opposed the motion, arguing that\n\nthe purported arbitration clause had not become part of the contract because he\n\ndid not have reasonable notice of the clause and did not manifest assent to it. The\n\n\n\n 2\n\fUnited States District Court for the Eastern District of New York (Nicholas G.\n\nGaraufis, J.) denied SquareTrade’s motion, and SquareTrade appealed. For the\n\nreasons that follow, we AFFIRM.\n\n BACKGROUND1\n\n SquareTrade sells and administers service contracts called protection\n\nplans, which provide protections against defects and damage to a variety of\n\nconsumer products. Unlike warranties, which are provided by the product’s\n\nmanufacturer and are often included in the purchase price, SquareTrade\n\nprotection plans cover products made by other companies, and are sold for\n\nadditional consideration separate from the product price. SquareTrade markets\n\nand sells protection plans on its own website as well as through retailers\n\nincluding Costco, Target, Staples, Office Depot, and Amazon.\n\n As relevant here, Starke purchased the “SquareTrade 2-Year Electronics\n\nProtection Plan ($50-75)” (the “Protection Plan”) for $4.34 plus tax through\n\n\n\n1\n Courts deciding motions to compel apply a standard similar to the one\napplicable to a motion for summary judgment. Bensadoun v. Jobe-Riat, 316 F.3d\n171, 175 (2d Cir. 2003). On a motion for summary judgment, the court considers\nall relevant, admissible evidence submitted by the parties and contained in the\npleadings, depositions, answers to interrogatories, admissions and affidavits, and\ndraws all reasonable inferences in favor of the non-moving party. Nicosia v.\nAmazon.com, Inc., 834 F.3d 220, 229 (2d Cir. 2016).\n\n 3\n\fAmazon. Starke intended the Protection Plan to cover a CD player he had\n\npurchased from Staples for $61.83. Starke had previously purchased several\n\nSquareTrade protection plans through Amazon and one through Staples to cover\n\nother items.\n\n The Amazon webpage on which Starke purchased the Protection Plan\n\nlooked like this:\n\n\n\n\n 4\n\f5\n\f6\n\fApp’x at 113–14.2\n\n The portion of the purchase page copied above contains several sections of\n\ninformation about the Protection Plan. A block of text towards the top of the\n\npurchase page informed Starke that his “Service Contract [would] be delivered\n\nvia email and not mailed to [him]. It [would] come from SquareTrade Warranty\n\nServices . . . within 24 hours of purchase.” App’x at 113. Much further down in\n\nthe excerpted portion of the purchase page (which would likely require scrolling\n\non most computer screens), one encounters the heading: “Product information.”\n\nUnder that heading appears a small hyperlink labeled “Warranty [pdf].” The\n\n“Warranty” hyperlink provided access to a two-page document titled “Terms &\n\nConditions” stating: “Congratulations on purchasing this Protection Plan. Please\n\nread these terms and conditions carefully so that you fully understand your\n\ncoverage under this Protection Plan.” App’x at 40. The document contains terms\n\npurporting to govern the transaction, in addition to those terms appearing on the\n\nface of the Amazon purchase page. Notably, this document (the “Pre-Sale T&C”)\n\n\n\n\n2\n That is what the top half of the purchase page looked like. One who continued\nto scroll down the purchase page would come across additional customer\nquestions and answers, customer reviews, additional advertisements and\nbanners, and the Amazon.com footer. See App’x at 115–16.\n\n 7\n\fdid not contain an arbitration provision or a class action waiver.3 Starke did not\n\nclick on the “Warranty” hyperlink and therefore, did not review the Pre-Sale\n\nT&C. The Amazon purchase page did not contain a hyperlink to anything titled\n\n“Service Contract.”\n\n Slightly above the “Product information” was another heading,“Things to\n\nknow.” The first bullet point under this heading warns customers that\n\n“SquareTrade Protection Plans are only valid for new products purchased at\n\nAmazon within the last 30 days.” App’x at 114 (emphasis added). The fifth bullet\n\npoint under this heading informs customers that they “may cancel [their] plan\n\nanytime within the first 30 days for a full refund.” Id. Starke did not read that\n\npart of the purchase page and was not aware that the Protection Plan would not\n\ncover items that had not been purchased through Amazon.\n\n After his purchase, Starke received a confirmation email from Amazon\n\nwhich informed him that “[his] protection plan service agreement [would] be\n\n\n3\n SquareTrade represented to the district court that the Pre-Sale T&C document\nwas “an outdated version of SquareTrade’s Terms and Conditions.” App’x at 75.\nUpon realizing that the outdated version was posted on Amazon, as a result of\nthis lawsuit, SquareTrade contacted Amazon and requested that the updated\nversion—apparently containing an arbitration provision—be posted in its place.\nOn appeal, SquareTrade characterizes the Pre-Sale T&C as only a “sample” of\nSquareTrade’s terms and conditions. Appellant’s Br. at 5 n.1.\n\n 8\n\fsent via a separate e-mail by [the] seller.” App’x at 81. As the Amazon purchase\n\npage and confirmation email promised, Starke received an email from\n\nSquareTrade later that day. The email looked like this:\n\n\n\n\nApp’x at 83–84.\n\n\n\n 9\n\f The subject line of the email says “SquareTrade Protection Plan on\n\nAmazon.com - Contract is Enclosed.” The email contains several prompts and\n\ntext in various formats. As relevant to this case, the email contains a hyperlink in\n\nthe bottom left corner, labeled “Terms & Conditions,” that links to an eleven-\n\npage document titled “Protection Plan Terms & Conditions.” That document (the\n\n“Post-Sale T&C”) is a different document from the Pre-Sale T&C, and contains\n\nseveral provisions that were absent from the Pre-Sale T&C. One of the provisions\n\nappearing in the Post-Sale T&C but not the Pre-Sale T&C purports to bind the\n\nparties to arbitration of “[a]ny controversy or claim arising out of or relating to\n\nthis Protection Plan, or breach thereof . . . in accordance with the Commercial\n\nArbitration Rules of the American Arbitration Association.” App’x at 70. The\n\nPost-Sale T&C also contained a class action waiver and a California choice-of-law\n\nclause. Starke did not click on the “Terms & Conditions” hyperlink and did not\n\nreview the Post-Sale T&C. Nothing in the body of the email referred to\n\narbitration, and the email did not contain or refer to any attachments.4\n\n4\n According to Starke, following his prior purchases of SquareTrade protection\nplans on Amazon he had received, at most, confirmation emails that, at the very\nbottom, had links to Terms & Conditions, but that he never reviewed those\ndocuments. Starke’s explanation of the emails he received from SquareTrade on\nthese prior occasions is consistent with an affidavit submitted on behalf of\nSquareTrade indicating that SquareTrade’s purchase confirmation emails have\n\n 10\n\f After receiving the email, Starke followed the instructions directing him to\n\nsend SquareTrade a copy of the receipt for his electronics item. Starke alleges that\n\nthe receipt clearly stated that his CD player was purchased at Staples. Two days\n\nlater, SquareTrade confirmed that it had received a copy of his receipt.\n\n Some months later, Starke’s CD player required repair or replacement, and\n\nStarke made a claim for coverage under the Protection Plan. SquareTrade denied\n\nthe claim, notifying Starke that since the CD player had not been purchased\n\nthrough Amazon, it was not covered, and that his Protection Plan would be\n\ncancelled. SquareTrade offered Starke a refund for the full price of the Protection\n\nPlan.\n\n Shortly thereafter, Starke filed this putative class action against\n\nSquareTrade, alleging fraudulent and deceptive practices by SquareTrade in the\n\nselling and marketing of protection plans. The complaint seeks damages and\n\ninjunctive relief for violations of Sections 349 and 350 of New York’s General\n\nBusiness Law, and the Magnuson-Moss Warranty Act, 15 U.S.C. § 2301 et seq.,\n\n\n\nbeen delivered with substantially the same form and content since 2014. The one\ntime Starke purchased a SquareTrade protection plan through Staples, he\nreceived a confirmation email from SquareTrade with the terms and conditions\ngoverning the transaction in the body of the email. Those terms and conditions\ncontained neither an arbitration provision nor a class action waiver.\n\n 11\n\fand for unjust enrichment. Starke alleges that SquareTrade knowingly and\n\ndeceptively sells protection plans for items not purchased on Amazon and\n\ntherefore, not eligible for coverage, despite knowing that under the terms of the\n\nplan, which are not prominently disclosed, the products which its customers\n\nhave sought to protect are not eligible for coverage. According to the complaint,\n\nSquareTrade’s limiting of covered products to those purchased through Amazon\n\noperates as an intentionally deceptive scheme to take money from unsuspecting\n\ncustomers. If a SquareTrade customer never makes a claim under her plan,\n\nSquareTrade keeps her premium and retains the policy until expiration. But if the\n\ncustomer makes a claim that requires SquareTrade to honor the policy,\n\nSquareTrade informs the customer that her protection plan is void because the\n\nunderlying product was not purchased through Amazon.\n\n Starke also alleges that SquareTrade fails to disclose other material terms\n\nand restrictions prior to the sale, and hoodwinks customers by providing them\n\nwith pre-sale terms and conditions that differ from the more restrictive post-sale\n\nterms and conditions that are disclosed only after the purchase has been\n\ncompleted and only via a deliberately obscure hyperlink.\n\n In response, SquareTrade moved to stay the action and compel Starke to\n\n\n\n 12\n\farbitrate his claims individually, citing the arbitration clause and class action\n\nwaiver contained in the Post-Sale T&C. SquareTrade argued that Starke had\n\nreasonable notice of the Post-Sale T&C because the Amazon purchase page\n\nnotified him that he would receive his “Service Contract” via email, the email he\n\nreceived from SquareTrade contained a hyperlink to the Post-Sale T&C, and\n\nStarke manifested assent to the Post-Sale T&C by failing to return the Protection\n\nPlan within the 30-day window SquareTrade allowed. SquareTrade also argued\n\nthat Starke’s prior course of dealing with SquareTrade put him on notice of the\n\nPost-Sale T&C.\n\n The district court denied SquareTrade’s motion. The court applied New\n\nYork contract law to determine whether the parties had bound themselves to an\n\nenforceable arbitration agreement. First, the district court found that Starke did\n\nnot have actual knowledge of the arbitration provision in the Post-Sale T&C\n\nbecause he did not click on the “Terms & Conditions” hyperlink in the\n\nSquareTrade confirmation email and read the hyperlinked document. Then the\n\ncourt considered whether Starke (1) had reasonable notice of the Post-Sale T&C\n\nand (2) offered an objective manifestation of assent to the Post-Sale T&C.\n\n In determining whether Starke had reasonable notice of the Post-Sale T&C\n\n\n\n 13\n\fand manifested assent to such terms and conditions, the district court applied the\n\ntest adopted in Berkson v. Gogo LLC, 97 F. Supp. 3d 359, 402–03 (E.D.N.Y. 2015).5\n\nUnder that test, according to the district court, the court assesses four factors: (1)\n\nwhether Starke was aware that he was binding himself to more than an offer of\n\ngoods or services in exchange for money; (2) whether the design and content of\n\nthe SquareTrade confirmation email made the Post-Sale T&C readily and\n\nobviously available; (3) whether SquareTrade required any affirmative\n\nmanifestation of agreement to the Post-Sale T&C; and (4) whether SquareTrade\n\nclearly drew the consumer’s attention to the Post-Sale T&C in general or the\n\narbitration provision in particular.\n\n As to the first factor, the district court concluded that Starke had\n\nreasonable notice that some contractual terms would be forthcoming because he\n\nset out to purchase a service contract. But, the district court noted, Starke’s\n\nknowledge of the existence of some contractual terms did not necessarily mean\n\nthat he could reasonably be expected to discern and agree to all of the contractual\n\nterms to which SquareTrade intended to bind him.\n\n\n\n5\n The Berkson court applied the substantive contract law of New York, California,\nand Illinois, and determined that “these states[’] laws are substantively similar\nwith respect to . . . contract formation.” Berkson, 97 F. Supp. 3d at 388.\n\n 14\n\f The second, third, and fourth factors, according to the district court,\n\ncounseled against finding reasonable notice and manifestation of assent. The\n\ndistrict court found that the design and content of the SquareTrade confirmation\n\nemail did not make the Post-Sale T&C readily and obviously available, because it\n\ndid not draw any attention to the inconspicuously placed Terms & Conditions\n\nhyperlink in small font at the very bottom of the email. Rather, a reasonable\n\nperson in Starke’s position would have thought that the body of the email\n\nconstituted the contract itself. Given that the terms of the contract were obscured\n\nand minimized, the district court held that Starke could not have evidenced a\n\nclear manifestation of assent. Lastly, the district court noted that SquareTrade did\n\nnot draw Starke’s attention to the arbitration provision buried in the Post-Sale\n\nT&C. The district court, therefore, held that SquareTrade failed to establish an\n\nenforceable arbitration agreement with Starke, and denied its motion to compel\n\narbitration.6\n\n SquareTrade timely appealed the district court’s order pursuant to 9 U.S.C.\n\n§ 16(a)(1)(C), which permits an interlocutory appeal from the denial of a motion\n\n\n\n6\n Because the district court concluded that there was no enforceable agreement to\narbitrate, it declined to assess the scope of the arbitration provision or the validity\nof the class action waiver.\n\n 15\n\fto compel arbitration. On December 15, 2017, the district court stayed the\n\nunderlying action pending the outcome of this appeal.\n\n DISCUSSION\n\nI. Standard of Review\n\n We review the district court’s denial of a motion to compel arbitration de\n\nnovo where the denial is based on a legal conclusion about whether the parties\n\ncontractually bound themselves to arbitrate. See Meyer v. Uber Techs., Inc., 868\n\nF.3d 66, 72–73 (2d Cir. 2017). Since the district court’s conclusions regarding\n\nnotice and assent were based on undisputed facts, those conclusions are also\n\nsubject to de novo review. Id. at 73 (holding de novo review appropriate where the\n\nevidence “consists exclusively of screenshots from the Web site and order\n\nconfirmation email, and the authenticity of these screenshots is not subject to\n\nfactual dispute”).\n\n “Where the undisputed facts in the record require the matter of\n\narbitrability to be decided against one side or the other as a matter of law, we\n\nmay rule on the basis of that legal issue and avoid the need for further court\n\nproceedings.” Wachovia Bank, Nat’l Ass’n v. VCG Special Opportunities Master Fund,\n\nLtd., 661 F.3d 164, 172 (2d Cir. 2011) (internal quotation marks omitted).\n\n\n 16\n\fII. Governing Legal Principles\n\n The Federal Arbitration Act (“FAA”) provides that written agreements to\n\narbitrate are “valid, irrevocable, and enforceable, save upon such grounds as\n\nexist at law or in equity for the revocation of any contract.” 9 U.S.C. § 2. The FAA\n\n“is a congressional declaration of a liberal federal policy favoring arbitration\n\nagreements, notwithstanding any state substantive or procedural policies to the\n\ncontrary.” Moses H. Cone Mem’l Hosp. v. Mercury Constr. Corp., 460 U.S. 1, 24\n\n(1983). This policy is founded upon “a desire to preserve parties’ ability to agree\n\nto arbitrate, rather than litigate, [their] disputes.” Schnabel v. Trilegiant Corp., 697\n\nF.3d 110, 118 (2d Cir. 2012).\n\n But despite the strong federal policy favoring arbitration, arbitration\n\nremains a creature of contract. See Howsam v. Dean Witter Reynolds, Inc., 537 U.S.\n\n79, 83 (2002); AT&T Mobility LLC v. Concepcion, 563 U.S. 333, 339 (2011)\n\n(reiterating that it is a “fundamental principle” of the FAA that “arbitration is a\n\nmatter of contract”) (quoting Rent-A-Center, West, Inc. v. Jackson, 561 U.S. 63, 67\n\n(2010)). Thus, courts must still decide whether the parties to a contract have\n\nagreed to arbitrate disputes. Schnabel, 697 F.3d at 118 (“The threshold question\n\nfacing any court considering a motion to compel arbitration is . . . whether the\n\n\n 17\n\fparties have indeed agreed to arbitrate.”); Specht v. Netscape Commc’ns Corp., 306\n\nF.3d 17, 26 (2d Cir. 2002) (observing that it is “well-settled that a court may not\n\ncompel arbitration until it has resolved the question of the very existence of the\n\ncontract embodying the arbitration clause”) (internal quotation marks omitted).\n\nThat question is governed by state-law principles of contract formation. Here, the\n\nparties agree that New York contract law applies.\n\n It is a basic tenet of contract law that, in order to be binding, a contract\n\nrequires a “meeting of the minds” and “a manifestation of mutual assent.” See\n\nExpress Indus. & Terminal Corp. v. N.Y. Dep’t of Transp., 93 N.Y.2d 584, 589 (N.Y.\n\n1999). The manifestation of mutual assent must be sufficiently definite to assure\n\nthat the parties are truly in agreement with respect to all material terms. See\n\nJoseph Martin, Jr., Delicatessen, Inc. v. Schumacher, 52 N.Y.2d 105, 109 (N.Y. 1981);\n\nRegister.com, Inc. v. Verio, Inc., 356 F.3d 393, 427 (2d Cir. 2004) (“Mutual assent is\n\nessential to the formation of a contract and a party cannot be held to have\n\ncontracted if there was no assent or acceptance.”). These requirements assure that\n\nthe judiciary can enforce the parties’ mutually-agreed terms and conditions when\n\none party seeks to uphold them against the other. Express Indus., 93 N.Y.2d at 589.\n\nGenerally, courts look to the basic elements of the offer and the acceptance to\n\n\n 18\n\fdetermine whether there was an objective meeting of the minds sufficient to give\n\nrise to a binding and enforceable contract. Id.\n\n Where an offeree does not have actual notice of certain contract terms, he is\n\nnevertheless bound by such terms if he is on inquiry notice of them and assents to\n\nthem through conduct that a reasonable person would understand to constitute\n\nassent. See Schnabel, 697 F.3d at 120. In determining whether an offeree is on\n\ninquiry notice of contract terms, New York courts look to whether the term was\n\nobvious and whether it was called to the offeree’s attention. See 22 N.Y. Jur. 2d\n\nContracts § 29 (“[A] party should not be bound by clauses printed on the reverse\n\nside of a contract unless it is established that they were properly called to his or her\n\nattention and that he or she assented to them.”) (emphasis added). This often\n\nturns on whether the contract terms were presented to the offeree in a clear and\n\nconspicuous way. See, e.g., Gildor v. USPS, 179 F. App’x 756, 759–60 (2d Cir. 2006)\n\n(refusing to enforce contract provision incorporated on reverse side of postage\n\nlabel where the provision was “very small and difficult to read”); Arthur Philip\n\nExport Corp. v. Leathertone, Inc., 87 N.Y.S.2d 665, 667 (1st Dep’t 1949) (refusing to\n\nenforce contract terms that were inconspicuously placed in “small type and in\n\nparenthesis” on the back of a confirmation order).\n\n 19\n\f We apply these same contract law principles to online transactions. See\n\nRegister.com, 356 F.3d at 404 (“While new commerce on the Internet has exposed\n\ncourts to many new situations, it has not fundamentally changed the principles of\n\ncontract.”); Specht, 306 F.3d at 31 (“These principles apply equally to the\n\nemergent world of online product delivery, pop-up screens, hyperlinked pages,\n\nclickwrap licensing, scrollable documents, and urgent admonitions to\n\n“Download Now!”); Resorb Networks, Inc. v. YouNow.com, 30 N.Y.S.3d 506, 511\n\n(N.Y. Sup. Ct. 2016) (noting that when evaluating a transaction occurring online,\n\ncourts focus on “whether a reasonably prudent offeree would be on notice of the\n\nterm at issue” and whether the terms of the agreement were “reasonably\n\ncommunicated to the user,” because assent is mostly passive online).\n\n In the context of web-based contracts, we look to the design and content of\n\nthe relevant interface to determine if the contract terms were presented to the\n\nofferee in way that would put her on inquiry notice of such terms. See Nguyen v.\n\nBarnes & Noble Inc., 763 F.3d 1171, 1177 (9th Cir. 2014) (“Where the link to a\n\nwebsite’s terms of use is buried at the bottom of the page or tucked away in\n\nobscure corners of the website where users are unlikely to see it, courts have\n\nrefused to enforce the [] agreement.”); Specht, 306 F.3d at 23 (refusing to enforce\n\n\n 20\n\fterms of use that “would have become visible to plaintiffs only if they had\n\nscrolled to the next screen”).\n\n In Nicosia, 834 F.3d at 233–38, we examined an Amazon order page to\n\ndetermine if it put a consumer on constructive notice of Amazon’s “Conditions of\n\nUse,” which contained an arbitration clause.7 The Amazon order page looked like\n\nthis:\n\n\n\n\n7\n In Nicosia, we applied Washington law on the question of contract formation, id.\nat 231, but Washington law is the same as New York law with respect to the issue\nof contract formation, see id. at 232.\n\n 21\n\fId. at 241 (Addendum B).\n\n Amazon claimed that an arbitration provision contained in the “conditions\n\nof use” hyperlink (at the top of the page under the “Review your order” heading)\n\nwas part of the contract it formed with the customer who placed an order on this\n\n\n 22\n\fpage. Several features of the order page’s design and content were relevant to\n\nour analysis of whether the customer had inquiry notice of the terms at this\n\nhyperlink:\n\n • The message “By placing your order, you agree to\n Amazon.com’s . . . conditions of use” was not bold,\n capitalized, or conspicuous in light of the whole\n webpage. Id. at 237.\n\n • Numerous other links on the webpage, in several\n different colors, fonts, and locations, generally\n obscured the message. Id.\n\n • Multiple buttons and promotional advertisements on\n the order page drew attention away from the message.\n Id.\n\n • The presence of customers’ personal address, credit\n card information, shipping options, and purchase\n summary were distracting. Id.\n\n Given these features of the order page, we held that reasonable minds\n\ncould disagree regarding whether the customer was on inquiry notice of an\n\narbitration provision contained in Amazon’s Conditions of Use. Id. at 237. We\n\ntherefore left it up to the factfinder to determine whether, when the customer\n\nclicked the “Place your order” button, she had manifested assent to the\n\narbitration provision contained at the “conditions of use” hyperlink. Id. at 236–37.\n\n\n\n 23\n\f More recently, in Meyer, we had to determine whether a user signing up\n\nfor an Uber account was on inquiry notice of an arbitration provision contained\n\nin Uber’s “Terms of Service,” which were provided to the user via Uber’s\n\nsmartphone interface. 868 F.3d 66.8 The “Terms of Service” were hyperlinked to\n\nthe sign-up screen in an interface that looked like this:\n\n\n\n\n8\n The Meyer Court applied California law to the contract formation question, but\nnoted that “New York and California apply substantially similar rules for\ndetermining whether the parties have mutually assented to a contract term.” Id.\nat 74 (internal quotations omitted).\n\n 24\n\fId. at 82 (Addendum B).\n\n We concluded that this interface did provide reasonable notice of the\n\ncontract terms contained in the “TERMS OF SERVICE & PRIVACY POLICY”\n\nhyperlink because the hyperlink was clear and conspicuous. Id. at 77–78. In so\n\nconcluding, we noted the following things about the design of the screen and the\n\nlanguage used:\n\n • The payment screen was uncluttered with only fields\n for the user to enter his or her credit card details,\n buttons to register for a user account or to connect to\n the user’s pre-existing PayPal account or Google\n Wallet to the Uber account, and the warning that “By\n creating an Uber account, you agree to the TERMS OF\n SERVICE & PRIVACY POLICY.” Id. at 78.\n\n • The text, including the hyperlinks to the Terms and\n Conditions and Privacy Policy, appeared directly\n below, i.e., was “spatially coupled” with the\n registration button. Id.\n\n • The entire screen was visible at once, and thus the user\n did not need to scroll beyond what was immediately\n visible to find notice of the Terms of Service. Id.\n\n • The register button was “temporally coupled” with\n the hyperlink – i.e., the consumer was notified of the\n terms at the time of sale. Id.\n\n • The language “[b]y creating an Uber account, you\n agree” was a clear prompt directing the users to read\n\n 25\n\f the Terms and Conditions and signaling that their\n acceptance of the benefit of registration would be\n subject to contractual terms. Id. at 79.\n\n These factors led us to conclude that the user had been provided with\n\nobjectively reasonable notice of the terms contained at the “TERMS OF\n\nSERVICE” hyperlink. And, since a reasonable user would know that by clicking\n\nthe registration button he was agreeing to the terms and conditions accessible via\n\nthe hyperlink, regardless of whether he actually clicked the hyperlink, we\n\ncompelled arbitration. Id. at 79–80.\n\n The reasoning of Nicosia and Meyer provides the framework within which\n\nwe analyze the validity of assent to terms and conditions presented through a\n\nweb interface.\n\nIII. Reasonable Notice of the Arbitration Provision\n\n To determine whether Starke had reasonable notice of the arbitration\n\nprovision, we must analyze whether the Post-Sale T&C were provided to Starke\n\nin a clear and conspicuous way.9 See Meyer, 868 F.3d at 75. Several things about\n\nthe transaction and the email Starke received from SquareTrade following the\n\n\n\n9\n The district court found that Starke “did not have actual notice” of the\narbitration provision, and SquareTrade does not dispute that finding.\n\n 26\n\fAmazon confirmation email lead us to conclude that Starke did not have\n\nreasonable notice of the arbitration provision, which was contained only in the\n\nPost-Sale T&C.\n\n First, SquareTrade never directed Starke’s attention to the “Terms &\n\nConditions” hyperlink that contained the Post-Sale T&C. The first screen Starke\n\nencountered during the course of the transaction, the Amazon purchase page,\n\ndid not provide Starke with notice that terms governing the sale would be\n\nprovided via hyperlink. Instead, the Amazon purchase page notified Starke that\n\nhe would receive something called a “Service Contract” via email. Then, Starke\n\nreceived an email from Amazon, notifying him that he would receive a “service\n\nagreement” from SquareTrade. Starke subsequently received an email from\n\nSquareTrade indicating that his “Contract” was enclosed. None of these various\n\ncommunications put Starke on notice that his “Service Contract” would come in\n\nthe form of a hyperlink, rather than in the body of the email.\n\n Second, when Starke opened the email from SquareTrade he was\n\npresented with a chart titled “Your Protection Plan.” The chart described the\n\nparticular Protection Plan that Starke purchased, and identified the “Coverage\n\nAmount,” “Protection Plan Price,” “Coverage Type,” “Covered Product,”\n\n\n 27\n\f“Deductible,” “Quantity,” “Coverage Term,” “Coverage Start Date,” “Coverage\n\nEnd Date,” and “Waiting Period.” This information took up approximately half\n\nof the email.10 Nothing else in the email stands out as obviously being related to\n\nStarke’s Protection Plan, and none of the language in the cluttered email directed\n\nStarke’s attention to the hyperlink containing the Post-Sale T&C.\n\n Third, the SquareTrade email bears more resemblance to the Amazon\n\norder page in Nicosia, 834 F.3d at 237, than to the uncluttered screen in Meyer, 868\n\nF.3d at 78. The “Terms & Conditions” hyperlink is some of the smallest text in the\n\n\n10\n SquareTrade argues that Starke could not have believed that the “Your\nProtection Plan” chart was his “Contract” because the chart itself referenced\nmore detailed terms and conditions. Specifically, SquareTrade notes that the\n“Coverage Amount” is defined in the chart as “[u]p to the maximum coverage\nprice of the Protection Plan, or the purchase price of your item, whichever is\nlower,” and the “Coverage Type” is listed as “Standard.” Without more,\nSquareTrade says, those terms would be meaningless.\n But the language in the chart does not obviously point to additional details\nin another document. In fact, the terms that SquareTrade references are not even\nelucidated in the actual contract at the hyperlink. “Coverage Type” is defined in\nthe Terms & Conditions only as “the level of coverage You purchased, such as\nwhether Your Protection Plan includes Optional Coverage, such as Accidental\nDamage from Handling (ADH) coverage,” App’x at 103, but nowhere does it\ndescribe the contents of “Standard” coverage, App’x at 83. Nor is there mention\nof the “coverage price of this Protection Plan” in the contract, such that Starke\ncould compare it to the “purchase price of [his] item.” App’x at 103. And, even if\nStarke thought that those terms could be defined in greater detail elsewhere,\nthere was no reason for him to believe that such detail was available in the\nSquareTrade email, let alone the “Terms & Conditions” hyperlink.\n\n 28\n\femail and comes after several prompts unrelated to the enclosure of the contract,\n\nincluding a “Need help?” hyperlink, a button for Starke to log in to his\n\nSquareTrade account, a hyperlink for Starke to submit the receipt for his CD\n\nplayer, the chart with details of the plan, and a banner urging Starke to review\n\nthe Protection Plan on Amazon. Like the interface in Nicosia, and in sharp\n\ncontrast with the screen in Meyer, the interface here is cluttered with diverse text,\n\ndisplayed in multiple colors, sizes and fonts, and features various buttons and\n\npromotional advertisements that distract the reader from the relevant hyperlink.\n\nSee Specht, 306 F.3d at 31–32 (finding no inquiry notice of contract terms that were\n\nprovided via hyperlink at the very bottom of the Netscape webpage which\n\ndistracted viewer with praise for the product and a “Download” button).\n\n Moreover, unlike in Meyer, the SquareTrade email in no way signals to\n\nStarke that he should click on the link, and it does not advise him that he would\n\nbe deemed to agree to the contract terms in the document to be found by clicking\n\nthat link. Nor does the email instruct him that the hyperlink is where his\n\npromised service contract can be found. The “Terms & Conditions” hyperlink\n\nappears without any “language advising [Starke] to click on [it],” Starkey, 796\n\nF.3d at 197, or a “clear prompt directing [Starke] to read the Terms and\n\n\n 29\n\fConditions,” Meyer, 868 F.3d at 79. The hyperlink was buried at the bottom of the\n\nemail directly above the email footer. Far above the hyperlink, the second\n\nsentence of the email told Starke “You’re all set!” encouraging him to look no\n\nfurther. The placement of the “Terms & Conditions” hyperlink in the email\n\nmakes it hard to escape the inference that SquareTrade hoped the reader’s eye\n\nwould be drawn elsewhere.\n\n This case is also distinguishable from Meyer because here, the “Terms &\n\nConditions” hyperlink was neither spatially nor temporally coupled with the\n\ntransaction. The “Terms & Conditions” hyperlink was spatially decoupled from\n\nthe transaction because it was not provided near the portion of the Amazon\n\npurchase page actually requiring Starke’s attention (that is, the “Add to Cart”\n\nbutton), or indeed anywhere on the purchase page. To provide conspicuous\n\nnotice of the Post-Sale T&C, SquareTrade could have simply included a\n\nnoticeable hyperlink on the Amazon purchase page directing consumers to\n\nreview the terms and conditions. See, e.g., Nicosia, 834 F.3d at 237–38 (noting that\n\n“Amazon chose not to employ a clickwrap mechanism,” which is “certainly the\n\neasiest method of ensuring that terms are agreed to”); Starkey, 796 F.3d at 197 n.3\n\n(noting that it would have been “simpler to resolve” this question had a\n\n\n 30\n\fclickwrap mechanism been used). And, even if SquareTrade was committed to\n\nproviding the Post-Sale T&C via email, it could have done so in several more\n\nconspicuous ways, including by providing the Post-Sale T&C in the body of the\n\nemail, providing an attachment to the email with the Post-Sale T&C, or by\n\nproviding the “Terms & Conditions” hyperlink at the top of the email in a bigger\n\nfont notifying the customer that the hyperlink is where he will find his “Service\n\nContract,” and that by rejecting the Protection Plan within the specific period, he\n\nwould be deemed to have accepted those terms.11\n\n\n\n11\n SquareTrade’s argument that internet users know how hyperlinks work misses\nthe point. The issue here is not that the Post-Sale T&C were provided via\nhyperlink. The problem is that the hyperlink was obscured and SquareTrade did\nnothing to alert Starke to the fact that this hyperlink contained his “Service\nContract.” See Hines v. Overstock.com, Inc., 668 F. Supp. 2d 362, 367 (E.D.N.Y. 2009)\n(finding contract term contained in hyperlink unenforceable where hyperlink\nwas not prominently displayed on the website and there was nothing prompting\nthe user to click on hyperlink); In re Zappos.com, Inc., 893 F. Supp. 2d 1058, 1064\n(D. Nev. 2012) (finding plaintiff did not manifest assent to contract terms\ncontained in hyperlink where the hyperlink was “inconspicuous, buried in the\nmiddle to bottom of every . . . webpage among many other links, and the website\nnever direct[ed] a user to the Terms of Use”); cf. Meyer, 868 F.3d at 79 (“As long as\nthe hyperlinked text was itself reasonably conspicuous—and we conclude that it\nwas—a reasonably prudent smartphone user would have constructive notice of\nthe terms.”) (emphasis added); Starkey v. G Adventures, Inc., 796 F.3d 193, 197 (2d\nCir. 2015) (finding terms enforceable where the email containing the “TERMS\nAND CONDITIONS” hyperlink directed the plaintiff to read the hyperlinked\ndocument).\n\n 31\n\f The Post-Sale T&C were also temporally decoupled from the transaction.\n\nStarke purchased the Protection Plan from the Amazon website, but he had no\n\nway to review the Post-Sale T&C until he received the SquareTrade confirmation\n\nemail. In Meyer, 868 F.3d at 78–80, we placed significant weight on the fact that\n\nthe “Terms of Service” hyperlink was temporally coupled with the register\n\nbutton. For one, that meant that the user could not avoid noticing the hyperlink\n\nwhen she registered for an account. But importantly, that also allowed the\n\nplaintiff “to review the Terms of Service prior to registration, unlike web\n\nplatforms that provide notice of contract terms only after the user manifested his\n\nor her assent.” Id. at 80. (emphasis added).\n\n In defense of its pay-now-terms-later approach, SquareTrade notes that\n\nNew York Insurance Law, which creates the legal framework within which\n\nservice contracts may be sold in the state, permits sellers to provide customers\n\nwith the contract governing their transactions within a reasonable amount of\n\ntime after the purchase. See N.Y. Ins. Law § 7903(b)(1). The law requires that\n\nconsumers be provided at least twenty days after the service contract has been\n\nmailed to return the contract to the seller for a full refund. Id. at § 7903(e).\n\nSquareTrade points out that it provided Starke with thirty days within which to\n\n\n 32\n\freturn his contract. However, Section 7903 is a regulatory regime that imposes\n\ncertain disclosure responsibilities and other duties on sellers of service contracts,\n\nbut it does not appear to alter New York law as to the manifestation of assent in\n\ncontract formation. Nor has SquareTrade provided authority to support the\n\nproposition that it does.\n\n Under general principles of contract law, moreover, providing contract\n\nterms after a transaction has taken place may be an appropriate way to contract\n\nin certain situations. But we find little justification for it here, where it would\n\nhave been virtually costless for SquareTrade to provide the governing terms and\n\nconditions to Starke before he bought the Protection Plan. See Schnabel, 697 F.3d\n\nat 126–28 (noting that there was no policy rationale for a “terms later by email”\n\nconception of contract formation under the circumstances). Indeed, SquareTrade\n\ndid provide a hyperlink to the Pre-Sale T&C, which do not contain the terms that\n\nSquareTrade seeks to enforce, on the Amazon purchase page.12 But, had Starke\n\n\n\n12\n We do not mean to suggest that the “Warranty” hyperlink provided sufficient\nnotice of the Pre-Sale T&C, since that hyperlink was itself buried on the busy\nAmazon purchase page amidst various other hyperlinks, banner advertisements,\nand customer reviews, among other things. The point is merely that a consumer\nwho clicked on that link would have been misled about the terms governing the\ntransaction.\n\n 33\n\fclicked on the “Warranty” hyperlink on the Amazon purchase page, he would\n\nhave been taken to a document containing the Pre-Sale T&C, which set forth\n\nwhat would have appeared to be a complete recitation of the terms of the\n\ncontract between the purchaser and SquareTrade. A consumer reviewing the Pre-\n\nSale T&C would have reasonably believed that his contract did not contain an\n\narbitration provision.\n\n Of course, Starke, like any other offeree, had a duty to read the terms of the\n\ncontract presented to him, including contract terms provided post-sale. But cases\n\napplying the duty-to-read principle still require that the offeree be put on notice\n\nof the existence of additional contract terms before it can be said that he has\n\nassented to them. See Schnabel, 697 F.3d at 124; Specht, 306 F.3d at 30 (“An\n\nexception to [the duty to read] rule exists when the writing does not appear to be\n\na contract and the terms are not called to the attention of the recipient.”). Thus,\n\nthe duty to read does not morph into a duty to ferret out contract provisions\n\nwhen they are contained in inconspicuous hyperlinks. See Nguyen, 763 F.3d at\n\n1179 (“Given the breadth of the range of technological savvy of online\n\npurchasers, consumers cannot be expected to ferret out hyperlinks to terms and\n\nconditions to which they have no reason to suspect they will be bound.”). That is\n\n\n 34\n\fparticularly so where, as here, the consumer was presented with several\n\ndocuments including the Pre-Sale T&C, the body of the subsequent email, and\n\nthe Post-Sale T&C, none of them specifically identified as the “Service Contract”\n\ngoverning the purchase, and all containing different sets of terms.\n\nIV. Starke’s Prior Course of Dealing with SquareTrade\n\n Finally, SquareTrade points to the prior course of dealing between Starke\n\nand SquareTrade to demonstrate that Starke was on inquiry notice of terms and\n\nconditions that he would receive via email. SquareTrade relies on Register.com,\n\n356 F.3d 393, where this Court found that a prior course of dealing between the\n\nparties supported the conclusion that they had agreed to certain terms and\n\nconditions. In Register.com, the party challenging the applicability of the terms\n\nand conditions was a sophisticated corporate customer that had made “daily”\n\nuse of its counter-party’s services subject to the terms and conditions, and had\n\nbeen “fully aware” of the terms and conditions that the counter-party sought to\n\nenforce. Id. at 402. We compared the situation before us then to one in which a\n\nperson maintains a roadside fruit stand displaying bins of apples with a sign at\n\nthe exit of the fruit stand telling customers that the apples are 50 cents each. Id. at\n\n401. We said that a visitor who comes, takes an apple, bites into it, and does not\n\n 35\n\fsee the sign until he exits may well believe he has no obligation to pay for the\n\napple because he had no notice when he bit into it that 50 cents was expected in\n\nreturn. Id. However, if the visitor returns to the apple stand on a daily basis, each\n\nday taking an apple without paying for it, he cannot later use the same defense.\n\nId. Based on his prior transaction(s), he knows full well that the owner is offering\n\napples in exchange for 50 cents. Id.\n\n Unlike the apple stand visitor, who learns of the terms governing his\n\ncontract with the owner and feigns ignorance that the same terms will apply in\n\nfuture transactions, Starke was not put on notice of SquareTrade’s terms and\n\nconditions through his prior transactions. Although Starke had transacted with\n\nSquareTrade on six prior occasions, SquareTrade never gave Starke clear and\n\nconspicuous notice that the transaction would subject him to binding arbitration.\n\nEach time Starke purchased a SquareTrade protection plan through Amazon, he\n\nreceived a confirmation email from SquareTrade which looked just like the\n\nconfirmation email at issue here. The fact that Starke received emails with the\n\nsame inconspicuous hyperlink on more than one occasion does not lead us to\n\nconclude that Starke had either actual or inquiry notice of the Post-Sale T&C.\n\n\n\n\n 36\n\f On only one occasion (when Starke purchased a SquareTrade protection\n\nplan through Staples) did Starke receive an email from SquareTrade in which the\n\nterms and conditions were actually provided in the body of the email. In that\n\ninstance, however, the terms and conditions in the email did not contain an\n\narbitration provision, so that transaction could not have put Starke on notice of\n\nsuch term. Starke notes that when SquareTrade introduced an arbitration clause\n\ninto its terms and conditions, it pivoted to providing its terms and conditions via\n\na nondescript hyperlink. Thus, the prior course of dealing between Starke and\n\nSquareTrade by no means resembles the apple hypothetical in Register.com, and it\n\ndoes not convince us that Starke was on inquiry notice of the arbitration\n\nprovision contained in the Post-Sale T&C.\n\n We emphasize that we in no way hold that the terms of a contract may not\n\nbe provided by a hyperlinked document. So long as the purchaser’s attention is\n\nadequately directed to a conspicuous hyperlink that is clearly identified as\n\ncontaining contractual terms to which the customer manifests assent by\n\ncompleting the transaction or retaining the product or service, a hyperlink can be\n\nan effective device for specifying contract terms. Nor do we hold that the format\n\nused in Meyer is the only effective way to use hyperlinks (though we note that the\n\n\n 37\n\fclean, uncluttered, and conspicuous labeling of the location and binding nature\n\nof the terms in the hyperlinked document can be used as a model that this Court\n\nhas found effective). We hold merely that on the totality of the circumstances in\n\nthis case, Starke was not on sufficient notice of the terms of the Post-Sale T&C,\n\nincluding its arbitration clause, and therefore did not manifest assent to those\n\nterms.\n\n CONCLUSION\n\n For the reasons stated above, we AFFIRM the order of the district court,\n\ndenying SquareTrade’s motion to compel arbitration.\n\n\n\n\n 38\n[END_CASE]", "role": "user" } ]
4,580,533
United States v. Klein (Schulman)
2019-01-10
17-3355
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges.", "parties": "", "opinions": [{"author": "ROBERT A. KATZMANN, Chief Judge", "type": "010combined", "text": "17-3355\nUSA v. Klein (Schulman)\n\n\n\n United States Court of Appeals\n for the Second Circuit\n _______________ \n\n AUGUST TERM, 2018 \n\n (Argued: October 22, 2018               Decided: January 10, 2019) \n\n Docket No. 17‐3355 \n\n _______________ \n\n UNITED STATES OF AMERICA, \n Appellee, \n\n —v.— \n\n Tibor Klein, \n Defendant, \n\n ROBERT SCHULMAN, \n Defendant‐Appellant. \n _______________ \n\n Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges. \n\n _______________ \n\n Defendant‐appellant Robert Schulman appeals from an October 4, 2017 \n judgment convicting him, following a jury trial, of one count of conspiracy to \n commit securities fraud and one count of securities fraud. On appeal, Schulman \n argues that the district court erroneously denied his motion pursuant to Federal \n Rule of Criminal Procedure 29 to vacate his convictions. According to Schulman, \n\n\n\n 1 \n\f \nhis convictions cannot stand because the government adduced insufficient \nevidence at trial of his criminal intent. Because the jury was not required to credit \nSchulman’s deposition testimony that he intended only to brag when he tipped \nhis friend and financial advisor about an upcoming merger, and the evidence \ntaken as a whole permitted the jury to find beyond a reasonable doubt that \nSchulman intended his communication to lead to trading in securities of the \ncompany in question, we disagree. Accordingly, we AFFIRM the judgment of \nthe district court. \n _______________ \n\n MARK D. HARRIS (John E. Roberts, on the brief), Proskauer Rose LLP,  \n New York, New York, for Defendant‐Appellant. \n  \n DAVID C. PITLUCK, Assistant United States Attorney (Jo Ann M. \n Navickas and Julia Nestor, Assistant United States Attorneys, \n on the brief), for Richard P. Donoghue, United States Attorney \n for the Eastern District of New York, Brooklyn, New York, for \n Appellee. \n\n         _______________ \n\nROBERT A. KATZMANN, Chief Judge:  \n\n This securities fraud case calls upon us to review whether there was \n\nsufficient evidence of criminal intent to sustain a judgment of conviction against \n\na tipper who did not directly trade on material, non‐public information but \n\nrather shared it with a tippee who did. Robert Schulman appeals from a \n\njudgment entered October 4, 2017 in the United States District Court for the \n\nEastern District of New York (Azrack, J.) convicting him, after a jury trial, of one \n\n\n 2 \n \n\f \ncount of conspiracy to commit securities fraud, in violation of 18 U.S.C. § 371, \n\nand one count of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff. The \n\njury found, in relevant part, that Schulman engaged in a conspiracy to trade in \n\nthe securities of a company called King Pharmaceuticals (“King”) using material, \n\nnon‐public information that he obtained through his representation of King \n\nwhile a partner at the law firm of Hunton & Williams (“Hunton”). Schulman’s \n\nsole contention on appeal is that the government adduced insufficient evidence \n\nat trial of his criminal intent. \n\n Schulman’s arguments focus on a comment Schulman says he made to his \n\nfriend and financial advisor Tibor Klein: “[I]t would be nice to be king for a day.” \n\nApp. 251. Schulman concedes that, in making this comment, he “disclosed non‐\n\npublic information to a friend who was also his financial advisor.” Appellant’s \n\nBr. at 4. But, according to Schulman, his comment was merely a “joke,” App. at \n\n251, or, as he argues now, “a boastful, imprudent” remark, Appellant’s Br. at 4. \n\nHe contends that no reasonable jury could conclude beyond a reasonable \n\ndoubt—in light of his testimony that he communicated nothing more about King \n\nor its ongoing merger talks, see App. at 252 (“I would have never told him . . . \n\n\n\n 3 \n \n\f \nthere’s a potential merger.”); id. (“[T]hat’s the extent of what I would have \n\ncommunicated to him.”)—that he disclosed this information “with the \n\nexpectation that [Klein would] trade on it,” United States v. Martoma, 894 F.3d 64, \n\n79 (2d Cir. 2017); see also Salman v. United States, 137 S. Ct. 420, 428 (2016). \n\n We disagree. The evidence here, taken as a whole, is sufficient to support \n\nthe jury’s verdict. The jury was entitled to discredit Schulman’s testimony in a \n\nprior deposition that he intended only to brag and that he told Klein nothing \n\nabout King’s ongoing merger talks. Extensive circumstantial evidence supports \n\nan inference that Schulman communicated more to Klein than that “it would be \n\nnice to be king for a day” and that Schulman expected Klein to use the non‐\n\npublic information he shared with him to trade in King securities. Accordingly, \n\nthe judgment of the district court is AFFIRMED.  \n\n  \n\n BACKGROUND \n\n  On August 4, 2016, a grand jury in the Eastern District of New York \n\ncharged Robert Schulman and Tibor Klein with securities fraud and conspiracy \n\nto commit securities fraud. On February 24, 2017, the district court granted \n\n\n\n 4 \n \n\f \nKlein’s motion to sever his trial from Schulman’s, and on March 6, 2017, \n\nSchulman’s trial commenced. At trial, the Government introduced, inter alia, the \n\ntestimony of a cooperating witness, Michael Shechtman; sworn statements \n\nSchulman made to the U.S. Securities and Exchange Commission (“SEC”) in a \n\ndeposition on August 27, 2012; and notes taken during Schulman’s meeting with \n\nthe U.S. Attorney’s Office (“USAO”) on May 19, 2015. Schulman called, among \n\nothers, his wife, Ronnie Schulman. Neither Robert Schulman nor Klein testified \n\nat trial. \n\n I. Trial Evidence \n\n The evidence at trial included the following. Schulman was a Washington \n\nD.C.‐based partner in Hunton’s patent group. Klein was the principal of Klein \n\nFinancial Services, a registered investment advisor based in Long Island, New \n\nYork. In or about 2000, Schulman and his wife, Ronnie Schulman, hired Klein. \n\nThe Schulmans gave Klein discretionary authority over their investment \n\naccounts, meaning that Klein could trade securities without first obtaining the \n\nSchulmans’ permission. For his efforts, the Schulmans paid Klein one percent of \n\n\n\n\n 5 \n \n\f \ntheir portfolio per year, an arrangement akin to those Klein had with other \n\nclients. \n\n  Approximately three times each year, Klein traveled to the Schulmans’ \n\nhome in McLean, Virginia to discuss the Schulmans’ finances. On these \n\noccasions, Klein arrived Friday afternoon, visited with Ronnie Schulman before \n\nRobert Schulman got home from work, and then had dinner with the Schulmans. \n\nAfter dinner, the Schulmans and Klein discussed the Schulmans’ investment \n\naccounts, including, albeit “very rarely,” individual stocks. App. at 805. Klein \n\nthen spent the night in the Schulmans’ guest room. \n\n The Schulmans and Klein had become friends. As Ronnie Schulman \n\nexplained, although her husband was “not close with Tibor in the personal way \n\nthat I was,” her husband and Klein went to baseball games, went out to dinner \n\nwhen Schulman travelled to New York for business, and would share a beer or \n\nglass of wine. Id. at 821. The Schulmans also introduced Klein to their friends, \n\nwho subsequently also invested with Klein. \n\n  The Schulmans were “generally pleased” with Klein’s services, although \n\nthey were concerned that Klein had been too “bearish” in the years following the \n\n\n\n 6 \n \n\f \n2008 financial crisis. Id. at 241. The jury also learned that, in April, May, and June \n\n2010, Klein made several purchases of Enzo Pharmaceuticals (“Enzo”) in \n\nSchulman’s IRA account. Enzo was Schulman’s client at the time, and Klein \n\nknew that. When Schulman was asked about these trades by the SEC in 2012, he \n\nsaid that he “remember[ed] being a little upset” at Klein when Klein told him \n\nabout these purchases, “because . . . the CEO [of Enzo] is a certifiable lunatic.” Id. \n\nat 245. He added: “I remember being a little upset, but I don’t remember what \n\nhappened with that. I think he sold it at some point after that.” Id. Several years \n\nlater, in 2015, when Schulman was asked about these trades by the USAO he said \n\nthat he believed “it was improper . . . to own shares in a client” and that he \n\n“reprimanded Klein not to [trade in securities of his clients] in the future.” Id. at \n\n242.  \n\n  Schulman’s convictions relate to his representation of King. In July 2010, \n\nSchulman was preparing for summary judgment and trial in a patent lawsuit \n\ninvolving King, when King’s in‐house counsel informed another Hunton partner \n\nthat King was looking to settle the case and that King was in merger discussions \n\nwith Pfizer. On August 4, 2010, that partner and another Hunton lawyer, David \n\n\n\n 7 \n \n\f \nKelly, met with Pfizer’s lawyers in New York as part of Pfizer’s due diligence. \n\nThereafter, Schulman learned of the potential merger from Kelly. Kelly told \n\nSchulman to keep the information confidential.  \n\n Less than ten days later, on Friday, August 13, Klein traveled to the \n\nSchulmans’ home in Virginia for one of their regular meetings. Klein arrived in \n\nthe afternoon, had dinner with the Schulmans, spent the night in their guest \n\nroom, and departed the next morning. Schulman, in his SEC deposition, \n\nadmitted to telling Klein about King. Specifically, Schulman said: \n\n [T]here was one evening when Mr. Klein was at my house where I did \n mention, and I kind of made a joke with him, “boy, it would be nice to be \n king for a day.” And I made some joke with him about that. And at that \n point I would have never told him anything about their meeting, there’s a \n potential merger, it would have been much more of the nature of “hey, \n wouldn’t it be great to be king for a day, ha, ha, ha,” kind of like telling \n him, like acting like I am a big shot and I know this thing. But that’s the \n extent of what I would have communicated to him. \n \nId. at 251‐52. Schulman provided a similar explanation to the USAO in his 2015 \n\ninterview. Id. at 240‐41.   \n\n Ronnie Schulman, the only person to testify at trial who was present that \n\nevening, said that she could not remember anything being said about King. In \n\n\n\n\n 8 \n \n\f \nparticular, Ronnie Schulman said that she did not hear her husband say, “I’d like \n\nto be king for a day,” but that, even if he had said it, she may not have picked up \n\non it as significant because it would have just been “silly talk.” Id. at 831‐32.  \n\n  On Sunday, August 15, Klein called Shechtman, his childhood best friend, \n\nand a financial advisor at Ameriprise Financial (“Ameriprise”), but could not \n\nreach him. The next day, Klein reached Shechtman and asked him what he \n\nwould do if he thought he had inside information. Shechtman asked Klein what \n\nhe was talking about. Klein said: “Pfizer’s buying King Pharmaceuticals.” Id. at \n\n335. Shechtman asked Klein if he had spoken to Frank Marzano, one of Klein’s \n\nformer colleagues, about King, and Klein told Shechtman that Marzano \n\n“wouldn’t touch this.” Id. at 337‐38. Shechtman did not ask Klein about the \n\nsource of his information because he “didn’t want to know the answers.” Id. at \n\n336. Klein did not mention any publicly available information that might justify \n\npurchasing King securities at the time he initially shared the material, non‐public \n\ninformation with Shechtman.  \n\n Shechtman then purchased $15,000 of King options, some expiring \n\nSeptember 18, 2010 and some expiring October 16, 2010. Shechtman also \n\n\n\n 9 \n \n\f \npurchased $45,000 of King stock for himself and his wife. Klein purchased 65,150 \n\nKing shares for $585,217 in various accounts including accounts belonging to \n\nhim, the Schulmans, and forty‐eight clients, including the Schulmans’ friends \n\nand Klein’s parents. Klein’s purchases for the Schulmans totaled $26,899, 7.35 \n\npercent of Robert Schulman’s IRA.  \n\n  On October 12, 2010, Pfizer announced its acquisition of King. Shechtman \n\nimmediately sold his King stock and options, for a profit of more than $110,000. \n\nKlein sold his King stock for a profit of approximately $8,000, and the King stock \n\nhe had purchased for his family and clients for a profit of $328,038. Schulman’s \n\nshare of these profits was around $15,500, an over 50 percent return in less than \n\ntwo months.  \n\n   A few weeks later, an Ameriprise compliance officer approached \n\nShechtman, telling him there was a serious problem. When Shechtman heard \n\nthis, he “went numb,” because he “immediately knew it was about the trades.” \n\nId. at 366. At first, Shechtman lied, saying that he had been looking at King for a \n\nwhile and had spoken with some fellow advisors about King who thought it was \n\na good investment. Later, Shechtman sent an email to Ameriprise compliance \n\n\n\n 10 \n \n\f \nofficers disclosing that he had spoken with Klein about King, in case \n\ninvestigators noticed his numerous phone calls with Klein. A week later, \n\nShechtman told Klein about the Ameriprise investigation. As Ameriprise had \n\nasked Shechtman for information backing up his story, such as research reports \n\nor notes, Klein sent an email to a “junk email” address shared by Shechtman and \n\nhis wife containing some research about King. Around this time, Klein also sold \n\nall of Schulman’s Enzo shares.  \n\n  Following an investigation, the SEC charged Shechtman and Shechtman \n\nadmitted liability. Shechtman also agreed to cooperate with the USAO and to \n\nplead guilty to conspiracy to commit securities fraud. The SEC then charged \n\nKlein in the fall of 2013, at which point the Schulmans fired Klein. Ronnie \n\ntestified that she and her husband had not fired Klein earlier, for example, after \n\nlearning that Klein had traded in King securities in their accounts or after Robert \n\nwas deposed by the SEC, because they “trusted” Klein and “believed there was \n\nan innocent explanation” for all that had happened. Id. at 839‐40. \n\n II. Post‐Trial Proceedings \n\n\n\n\n 11 \n \n\f \n Schulman moved for a judgment of acquittal after the government rested, \n\narguing, among other things, that the evidence did not establish that he intended \n\nfor Klein to trade in King securities. The district court denied Schulman’s motion. \n\nSchulman renewed his motion for a judgment of acquittal at the conclusion of the \n\nevidence, and the district court again denied the motion. Thereafter, the district \n\ncourt charged the jury, and, a little over a day later, the jury returned guilty \n\nverdicts on both counts. \n\n Schulman then moved for a judgment of acquittal pursuant to Federal \n\nRule of Criminal Procedure 29. Schulman argued, inter alia, that no reasonable \n\njury could have inferred that he told Klein more than the “king for a day” \n\ncomment and that no reasonable jury could have found that he had intended \n\nKlein to trade on it. The district court denied Schulman’s motion by reasoned \n\nopinion. Thereafter, the district court sentenced Schulman on both counts to \n\nthree years’ probation to run concurrently, a $50,000 fine, forfeiture in the \n\namount of $15,527, and 2,000 hours of community service. This appeal timely \n\nfollowed. \n\n\n\n\n 12 \n \n\f \n DISCUSSION \n\n We review de novo a district court’s order denying a Rule 29 motion \n\naddressing the sufficiency of the evidence. United States v. Khalil, 857 F.3d 137, \n\n139 (2d Cir. 2017). In challenging the jury’s verdict, a Rule 29 movant “bears a \n\nheavy burden.” Martoma, 894 F.3d at 72.1 A reviewing court must “credit[] every \n\ninference that could have been drawn in the government’s favor,” id., and \n\n“affirm the conviction so long as, from the inferences reasonably drawn, the jury \n\nmight fairly have concluded guilt beyond a reasonable doubt.” United States v. \n\nReifler, 446 F.3d 65, 94 (2d Cir. 2006).  \n\n Moreover, in considering Schulman’s sufficiency challenge, we do not \n\nevaluate the evidence piecemeal or in isolation. We view the evidence “in \n\nconjunction” and uphold Schulman’s conviction “if any rational trier of fact \n\ncould have found the essential elements of the crime beyond a reasonable \n\ndoubt.” Id. at 94‐95; see Jackson v. Virginia, 443 U.S. 307, 319 (1979). While \n\n“specious inferences are not indulged,” United States v. Lorenzo, 534 F.3d 153, 159 \n\n\n\n                                               \n\n  1 Unless otherwise indicated, in quoting cases, all internal quotation marks, \nalterations, footnotes, and citations are omitted. \n\n 13 \n\f \n(2d Cir. 2008), we “defer to the jury’s determination of the weight of the evidence \n\nand the credibility of the witnesses, and to the jury’s choice of the competing \n\ninferences that can be drawn from the evidence,” Reifler, 446 F.3d at 94. In a close \n\ncase, where “either of the two results, a reasonable doubt or no reasonable doubt, \n\nis fairly possible, [we] must let the jury decide the matter.” United States v. \n\nAutuori, 212 F.3d 105, 114 (2d Cir. 2000). \n\n In an insider trading case, the government must prove that the insider will \n\npersonally benefit from the disclosure to the tippee. See Martoma, 894 F.3d at 73. \n\nPersonal benefit can be established in a number of ways, including by illustrating \n\nthe nature of the relationship between the tipper and the tippee or the tipper’s \n\nreceipt of something of value. The critical question regards the tipper’s purpose: \n\ndid the tipper share the material non‐public information with the tippee \n\nintending that the tippee use the information to improperly trade in securities? \n\nSee id. at 79 (a tipper is liable under 15 U.S.C. § 78j(b) if the tipper discloses \n\nmaterial, non‐public information “with the expectation that the tippee will trade \n\non it”); see also United States v. Gansman, 657 F.3d 85, 92 (2d Cir. 2011) (“In \n\nprosecuting a putative ‘tipper’ under the misappropriation theory of insider \n\n\n\n 14 \n \n\f \ntrading, the government must prove as an element of the offense that the tipper \n\nconveyed material nonpublic information to his ‘tippee’ with the understanding \n\nthat it would be used for securities trading purposes.”).2 Schulman argues that \n\n“[t]he Government presented no evidence [at trial], either direct or \n\ncircumstantial, that [he] intended for Klein to trade on” his tip about King. \n\nAppellant’s Br. at 26. According to Schulman, the evidence merely “suggests that \n\n[he] made a misguided comment to a friend in an effort to show off that he knew \n\nsomething that the public did not.” Id. at 22. \n\n We disagree. This is a case where it is essential to view the various pieces \n\nof evidence together. Although Schulman told the SEC that he had \n\ncommunicated “nothing” more than that he wished he could be king for a day, \n\nApp. at 240—a comment that, by itself, is innocuous—the jury was entitled to \n\ndisbelieve that he communicated nothing more. The district court properly \n\n\n                                               \n\n   2 As relevant here, 15 U.S.C. § 78j(b) prohibits the use of “any manipulative or \n\n deceptive device or contrivance” to contravene an SEC rule, including Rule 10b‐5. See 17 \n C.F.R. § 240.10b‐5. Rule 10b‐5 bars “undisclosed trading on inside corporate information \n by individuals who are under a duty of trust and confidence that prohibits them from \n secretly using such information for their personal advantage.” Salman v. United States, \n 137 S. Ct. 420, 423 (2016). “These persons also may not tip inside information to others \n for trading.” Id. \n\n 15 \n\f \ninstructed the jury to draw “reasonable inferences,” id. at 1290, and “us[e] \n\ncommon sense,” id. at 1317. As a matter of common sense, Schulman had to have \n\ncommunicated additional information for Schulman to concede to the SEC that \n\nhis king‐for‐a‐day comment was in fact “a reference to King Pharmaceuticals,” id. \n\nat 241. An oral statement does not usually reflect capitalization. Nonetheless, \n\nKlein apparently recognized that by “king” Schulman meant “King.” Common \n\nsense also would lead a rational juror to conclude that Schulman had to have \n\ncommunicated additional information to Klein for Klein to have promptly called \n\nShechtman, cited “inside information” about King and Pfizer, id. at 335, and \n\nbegun buying King stock. Indeed, this precise issue was argued to the jury, see id. \n\nat 1231‐32, 1265, and was resolved by the jury against Schulman. \n\n Further, the trial record is replete with evidence supporting an inference \n\nthat Schulman told Klein information about King so that Klein would trade on it. \n\nFor example, a reasonable jury could infer that Schulman intended Klein to trade \n\nfrom the evidence that (1) Klein was Schulman’s money manager, with \n\ndiscretionary authority over Schulman’s accounts, and that Schulman told Klein \n\nabout King during a meeting to discuss his investment portfolio; (2) after \n\n\n\n 16 \n \n\f \nmeeting with Schulman, Klein immediately bought hundreds of thousands of \n\ndollars of King stock, including in Schulman’s account and in the accounts of \n\nSchulman’s friends; and (3) Klein, on behalf of Schulman, had previously \n\npurchased stock in one of Schulman’s clients, Enzo. \n\n We reject Schulman’s arguments that Klein’s role as his financial advisor, \n\nand Klein’s conversations with Shechtman and purchases of King stock \n\nfollowing the meeting with Schulman are irrelevant. A rational jury could infer \n\nfrom the fact that Klein managed Schulman’s money and worked as a \n\nprofessional stock trader that Schulman intended Klein to trade on a stock tip he \n\nshared with him. The fact that Klein and Schulman were also close friends does \n\nnot detract from the relevance of Klein’s profession; in fact, it supplies an \n\nadditional motive for Schulman’s tip. Similarly, a rational jury could infer from \n\nthe fact that Klein purchased hundreds of thousands of dollars in King securities \n\nimmediately after meeting with Schulman, including over twenty‐five thousand \n\ndollars of King stock in Schulman’s account, that Klein was acting in accordance \n\nwith Schulman’s intent. This is true even though there were “virtually no \n\ncommunications” between Schulman and Klein in the months following \n\n\n\n 17 \n \n\f \nSchulman’s disclosure. Appellant’s Br. at 29. The jury was not required to accept \n\nSchulman’s contrary interpretation of the facts—that Klein’s purchase of stock \n\nfor Schulman was reckless and unthinking—as there is ample evidence in the \n\nrecord that Klein behaved in a calculated manner in trading on the information \n\nabout King. \n\n  We also reject Schulman’s argument that Klein’s prior purchase of Enzo \n\nstock is irrelevant. A reasonable jury could infer from the fact that Klein had once \n\ntraded in the stock of Schulman’s clients that he might be expected to do so \n\nagain. And, as Schulman was aware of Klein’s trading in Enzo, the jury could \n\nfurther infer that when Schulman told Klein about King, he expected Klein to act \n\non the information. In making these inferences, a reasonable jury could consider \n\nSchulman’s varying explanations for his disapproval of Klein’s prior purchase of \n\nEnzo stock. Specifically, when Schulman was first interviewed by the SEC in \n\n2012, he testified, “I remember being a little upset at [Klein for buying Enzo \n\nstock,] because I think that the CEO [of Enzo] is a certifiable lunatic.” App. at 245. \n\nBut several years later, Schulman told the USAO that the reason he criticized \n\nKlein for buying Enzo stock was that it was improper to own shares of a client. \n\n\n\n 18 \n \n\f \nSee id. at 242. The jury could reasonably view Schulman’s second explanation as a \n\nconscious attempt to sanitize his first explanation, which had criticized only the \n\neconomic soundness of the investment, not its legality or propriety. \n\n  In addition, Schulman’s first, and perhaps more genuine explanation, \n\nprovides further context for the king‐for‐a‐day comment. For example, the jury \n\ncould reasonably infer from the Enzo evidence that, while Klein knew that \n\nSchulman had been upset at him for buying Enzo shares because the CEO was a \n\n“lunatic,” Klein understood that Schulman’s stating a wish to be “[K]ing for a \n\nday” meant that buying King shares was, in fact, given Schulman’s inside \n\ninformation, a good idea.  \n\n In this regard, it is also relevant that Schulman thought that Klein’s \n\ninvestments in 2009 and 2010 had been “too bearish,” id. at 241, since Schulman’s \n\ndesire to invest more aggressively, along with his view of Klein’s Enzo purchase \n\nas unwise, could be viewed as fueling a desire by Schulman to help Klein achieve \n\ngreater returns in Schulman’s portfolio. And while Schulman argues that $15,000 \n\nwas so insignificant a fraction of his overall net worth that it could not have been \n\nan incentive for him to tip Klein, that sizable net worth entitled the jury to \n\n\n\n 19 \n \n\f \ndisbelieve Schulman’s preferred explanation that he made his king‐for‐a‐day \n\ncomment simply to “show off.” Appellant’s Br. at 22.  \n\n Finally, Schulman contends that he is entitled to a judgment of acquittal \n\nbecause the evidence supporting the inference that he intended Klein to trade on \n\nhis tip about King is, at the very least, in equipoise with evidence supporting an \n\ninference that he intended merely to boast. But it is not. Schulman cites mainly \n\nthe absence of evidence of any follow‐up conversations with Klein. This absence \n\nof evidence at best supports an inference that Schulman did not intend for Klein \n\nto trade for Schulman’s benefit. It says little, if anything, about whether \n\nSchulman intended Klein to trade for Klein’s benefit, an independent basis upon \n\nwhich a rational jury could have found Schulman guilty.3 Moreover, we know of \n\nno requirement in insider trading law that the government adduce evidence of \n\nmultiple conversations between co‐conspirators, or that the government provide \n\ndirect testimonial evidence regarding a defendant’s intent. See Lorenzo, 534 F.3d \n\n\n\n                                               \n\n 3  The Government argued at trial that Martoma’s “personal benefit” requirement \n was satisfied both because Schulman intended to receive a financial benefit and because \n Schulman intended to make a “gift” to Klein. The district court instructed the jury on \n both theories. \n\n 20 \n\f \nat 159 (the government “is entitled to prove its case solely through circumstantial \n\nevidence”).  \n\n CONCLUSION \n\n After conducting an independent review of the record and considering the \n\nevidence as a whole, we conclude that a rational trier of fact could have found \n\nthat Schulman acted with the requisite intent beyond a reasonable doubt. We \n\nhave considered all of Schulman’s contentions on appeal and have found in them \n\nno basis for reversal. Accordingly, the judgment of the district court is \n\nAFFIRMED. \n\n\n\n\n 21", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357786/", "author_raw": "ROBERT A. KATZMANN, Chief Judge"}]}
KATZMANN
KEARSE
CHIN
1
{"KATZMANN": ", Chief", "KEARSE": ", Circuit", "CHIN": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580533/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Klein (Schulman)\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17-3355\nUSA v. Klein (Schulman)\n\n\n\n United States Court of Appeals\n for the Second Circuit\n _______________ \n\n AUGUST TERM, 2018 \n\n (Argued: October 22, 2018               Decided: January 10, 2019) \n\n Docket No. 17‐3355 \n\n _______________ \n\n UNITED STATES OF AMERICA, \n Appellee, \n\n —v.— \n\n Tibor Klein, \n Defendant, \n\n ROBERT SCHULMAN, \n Defendant‐Appellant. \n _______________ \n\n Before: KATZMANN, Chief Judge, KEARSE and CHIN, Circuit Judges. \n\n _______________ \n\n Defendant‐appellant Robert Schulman appeals from an October 4, 2017 \n judgment convicting him, following a jury trial, of one count of conspiracy to \n commit securities fraud and one count of securities fraud. On appeal, Schulman \n argues that the district court erroneously denied his motion pursuant to Federal \n Rule of Criminal Procedure 29 to vacate his convictions. According to Schulman, \n\n\n\n 1 \n\f \nhis convictions cannot stand because the government adduced insufficient \nevidence at trial of his criminal intent. Because the jury was not required to credit \nSchulman’s deposition testimony that he intended only to brag when he tipped \nhis friend and financial advisor about an upcoming merger, and the evidence \ntaken as a whole permitted the jury to find beyond a reasonable doubt that \nSchulman intended his communication to lead to trading in securities of the \ncompany in question, we disagree. Accordingly, we AFFIRM the judgment of \nthe district court. \n _______________ \n\n MARK D. HARRIS (John E. Roberts, on the brief), Proskauer Rose LLP,  \n New York, New York, for Defendant‐Appellant. \n  \n DAVID C. PITLUCK, Assistant United States Attorney (Jo Ann M. \n Navickas and Julia Nestor, Assistant United States Attorneys, \n on the brief), for Richard P. Donoghue, United States Attorney \n for the Eastern District of New York, Brooklyn, New York, for \n Appellee. \n\n         _______________ \n\nROBERT A. KATZMANN, Chief Judge:  \n\n This securities fraud case calls upon us to review whether there was \n\nsufficient evidence of criminal intent to sustain a judgment of conviction against \n\na tipper who did not directly trade on material, non‐public information but \n\nrather shared it with a tippee who did. Robert Schulman appeals from a \n\njudgment entered October 4, 2017 in the United States District Court for the \n\nEastern District of New York (Azrack, J.) convicting him, after a jury trial, of one \n\n\n 2 \n \n\f \ncount of conspiracy to commit securities fraud, in violation of 18 U.S.C. § 371, \n\nand one count of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff. The \n\njury found, in relevant part, that Schulman engaged in a conspiracy to trade in \n\nthe securities of a company called King Pharmaceuticals (“King”) using material, \n\nnon‐public information that he obtained through his representation of King \n\nwhile a partner at the law firm of Hunton & Williams (“Hunton”). Schulman’s \n\nsole contention on appeal is that the government adduced insufficient evidence \n\nat trial of his criminal intent. \n\n Schulman’s arguments focus on a comment Schulman says he made to his \n\nfriend and financial advisor Tibor Klein: “[I]t would be nice to be king for a day.” \n\nApp. 251. Schulman concedes that, in making this comment, he “disclosed non‐\n\npublic information to a friend who was also his financial advisor.” Appellant’s \n\nBr. at 4. But, according to Schulman, his comment was merely a “joke,” App. at \n\n251, or, as he argues now, “a boastful, imprudent” remark, Appellant’s Br. at 4. \n\nHe contends that no reasonable jury could conclude beyond a reasonable \n\ndoubt—in light of his testimony that he communicated nothing more about King \n\nor its ongoing merger talks, see App. at 252 (“I would have never told him . . . \n\n\n\n 3 \n \n\f \nthere’s a potential merger.”); id. (“[T]hat’s the extent of what I would have \n\ncommunicated to him.”)—that he disclosed this information “with the \n\nexpectation that [Klein would] trade on it,” United States v. Martoma, 894 F.3d 64, \n\n79 (2d Cir. 2017); see also Salman v. United States, 137 S. Ct. 420, 428 (2016). \n\n We disagree. The evidence here, taken as a whole, is sufficient to support \n\nthe jury’s verdict. The jury was entitled to discredit Schulman’s testimony in a \n\nprior deposition that he intended only to brag and that he told Klein nothing \n\nabout King’s ongoing merger talks. Extensive circumstantial evidence supports \n\nan inference that Schulman communicated more to Klein than that “it would be \n\nnice to be king for a day” and that Schulman expected Klein to use the non‐\n\npublic information he shared with him to trade in King securities. Accordingly, \n\nthe judgment of the district court is AFFIRMED.  \n\n  \n\n BACKGROUND \n\n  On August 4, 2016, a grand jury in the Eastern District of New York \n\ncharged Robert Schulman and Tibor Klein with securities fraud and conspiracy \n\nto commit securities fraud. On February 24, 2017, the district court granted \n\n\n\n 4 \n \n\f \nKlein’s motion to sever his trial from Schulman’s, and on March 6, 2017, \n\nSchulman’s trial commenced. At trial, the Government introduced, inter alia, the \n\ntestimony of a cooperating witness, Michael Shechtman; sworn statements \n\nSchulman made to the U.S. Securities and Exchange Commission (“SEC”) in a \n\ndeposition on August 27, 2012; and notes taken during Schulman’s meeting with \n\nthe U.S. Attorney’s Office (“USAO”) on May 19, 2015. Schulman called, among \n\nothers, his wife, Ronnie Schulman. Neither Robert Schulman nor Klein testified \n\nat trial. \n\n I. Trial Evidence \n\n The evidence at trial included the following. Schulman was a Washington \n\nD.C.‐based partner in Hunton’s patent group. Klein was the principal of Klein \n\nFinancial Services, a registered investment advisor based in Long Island, New \n\nYork. In or about 2000, Schulman and his wife, Ronnie Schulman, hired Klein. \n\nThe Schulmans gave Klein discretionary authority over their investment \n\naccounts, meaning that Klein could trade securities without first obtaining the \n\nSchulmans’ permission. For his efforts, the Schulmans paid Klein one percent of \n\n\n\n\n 5 \n \n\f \ntheir portfolio per year, an arrangement akin to those Klein had with other \n\nclients. \n\n  Approximately three times each year, Klein traveled to the Schulmans’ \n\nhome in McLean, Virginia to discuss the Schulmans’ finances. On these \n\noccasions, Klein arrived Friday afternoon, visited with Ronnie Schulman before \n\nRobert Schulman got home from work, and then had dinner with the Schulmans. \n\nAfter dinner, the Schulmans and Klein discussed the Schulmans’ investment \n\naccounts, including, albeit “very rarely,” individual stocks. App. at 805. Klein \n\nthen spent the night in the Schulmans’ guest room. \n\n The Schulmans and Klein had become friends. As Ronnie Schulman \n\nexplained, although her husband was “not close with Tibor in the personal way \n\nthat I was,” her husband and Klein went to baseball games, went out to dinner \n\nwhen Schulman travelled to New York for business, and would share a beer or \n\nglass of wine. Id. at 821. The Schulmans also introduced Klein to their friends, \n\nwho subsequently also invested with Klein. \n\n  The Schulmans were “generally pleased” with Klein’s services, although \n\nthey were concerned that Klein had been too “bearish” in the years following the \n\n\n\n 6 \n \n\f \n2008 financial crisis. Id. at 241. The jury also learned that, in April, May, and June \n\n2010, Klein made several purchases of Enzo Pharmaceuticals (“Enzo”) in \n\nSchulman’s IRA account. Enzo was Schulman’s client at the time, and Klein \n\nknew that. When Schulman was asked about these trades by the SEC in 2012, he \n\nsaid that he “remember[ed] being a little upset” at Klein when Klein told him \n\nabout these purchases, “because . . . the CEO [of Enzo] is a certifiable lunatic.” Id. \n\nat 245. He added: “I remember being a little upset, but I don’t remember what \n\nhappened with that. I think he sold it at some point after that.” Id. Several years \n\nlater, in 2015, when Schulman was asked about these trades by the USAO he said \n\nthat he believed “it was improper . . . to own shares in a client” and that he \n\n“reprimanded Klein not to [trade in securities of his clients] in the future.” Id. at \n\n242.  \n\n  Schulman’s convictions relate to his representation of King. In July 2010, \n\nSchulman was preparing for summary judgment and trial in a patent lawsuit \n\ninvolving King, when King’s in‐house counsel informed another Hunton partner \n\nthat King was looking to settle the case and that King was in merger discussions \n\nwith Pfizer. On August 4, 2010, that partner and another Hunton lawyer, David \n\n\n\n 7 \n \n\f \nKelly, met with Pfizer’s lawyers in New York as part of Pfizer’s due diligence. \n\nThereafter, Schulman learned of the potential merger from Kelly. Kelly told \n\nSchulman to keep the information confidential.  \n\n Less than ten days later, on Friday, August 13, Klein traveled to the \n\nSchulmans’ home in Virginia for one of their regular meetings. Klein arrived in \n\nthe afternoon, had dinner with the Schulmans, spent the night in their guest \n\nroom, and departed the next morning. Schulman, in his SEC deposition, \n\nadmitted to telling Klein about King. Specifically, Schulman said: \n\n [T]here was one evening when Mr. Klein was at my house where I did \n mention, and I kind of made a joke with him, “boy, it would be nice to be \n king for a day.” And I made some joke with him about that. And at that \n point I would have never told him anything about their meeting, there’s a \n potential merger, it would have been much more of the nature of “hey, \n wouldn’t it be great to be king for a day, ha, ha, ha,” kind of like telling \n him, like acting like I am a big shot and I know this thing. But that’s the \n extent of what I would have communicated to him. \n \nId. at 251‐52. Schulman provided a similar explanation to the USAO in his 2015 \n\ninterview. Id. at 240‐41.   \n\n Ronnie Schulman, the only person to testify at trial who was present that \n\nevening, said that she could not remember anything being said about King. In \n\n\n\n\n 8 \n \n\f \nparticular, Ronnie Schulman said that she did not hear her husband say, “I’d like \n\nto be king for a day,” but that, even if he had said it, she may not have picked up \n\non it as significant because it would have just been “silly talk.” Id. at 831‐32.  \n\n  On Sunday, August 15, Klein called Shechtman, his childhood best friend, \n\nand a financial advisor at Ameriprise Financial (“Ameriprise”), but could not \n\nreach him. The next day, Klein reached Shechtman and asked him what he \n\nwould do if he thought he had inside information. Shechtman asked Klein what \n\nhe was talking about. Klein said: “Pfizer’s buying King Pharmaceuticals.” Id. at \n\n335. Shechtman asked Klein if he had spoken to Frank Marzano, one of Klein’s \n\nformer colleagues, about King, and Klein told Shechtman that Marzano \n\n“wouldn’t touch this.” Id. at 337‐38. Shechtman did not ask Klein about the \n\nsource of his information because he “didn’t want to know the answers.” Id. at \n\n336. Klein did not mention any publicly available information that might justify \n\npurchasing King securities at the time he initially shared the material, non‐public \n\ninformation with Shechtman.  \n\n Shechtman then purchased $15,000 of King options, some expiring \n\nSeptember 18, 2010 and some expiring October 16, 2010. Shechtman also \n\n\n\n 9 \n \n\f \npurchased $45,000 of King stock for himself and his wife. Klein purchased 65,150 \n\nKing shares for $585,217 in various accounts including accounts belonging to \n\nhim, the Schulmans, and forty‐eight clients, including the Schulmans’ friends \n\nand Klein’s parents. Klein’s purchases for the Schulmans totaled $26,899, 7.35 \n\npercent of Robert Schulman’s IRA.  \n\n  On October 12, 2010, Pfizer announced its acquisition of King. Shechtman \n\nimmediately sold his King stock and options, for a profit of more than $110,000. \n\nKlein sold his King stock for a profit of approximately $8,000, and the King stock \n\nhe had purchased for his family and clients for a profit of $328,038. Schulman’s \n\nshare of these profits was around $15,500, an over 50 percent return in less than \n\ntwo months.  \n\n   A few weeks later, an Ameriprise compliance officer approached \n\nShechtman, telling him there was a serious problem. When Shechtman heard \n\nthis, he “went numb,” because he “immediately knew it was about the trades.” \n\nId. at 366. At first, Shechtman lied, saying that he had been looking at King for a \n\nwhile and had spoken with some fellow advisors about King who thought it was \n\na good investment. Later, Shechtman sent an email to Ameriprise compliance \n\n\n\n 10 \n \n\f \nofficers disclosing that he had spoken with Klein about King, in case \n\ninvestigators noticed his numerous phone calls with Klein. A week later, \n\nShechtman told Klein about the Ameriprise investigation. As Ameriprise had \n\nasked Shechtman for information backing up his story, such as research reports \n\nor notes, Klein sent an email to a “junk email” address shared by Shechtman and \n\nhis wife containing some research about King. Around this time, Klein also sold \n\nall of Schulman’s Enzo shares.  \n\n  Following an investigation, the SEC charged Shechtman and Shechtman \n\nadmitted liability. Shechtman also agreed to cooperate with the USAO and to \n\nplead guilty to conspiracy to commit securities fraud. The SEC then charged \n\nKlein in the fall of 2013, at which point the Schulmans fired Klein. Ronnie \n\ntestified that she and her husband had not fired Klein earlier, for example, after \n\nlearning that Klein had traded in King securities in their accounts or after Robert \n\nwas deposed by the SEC, because they “trusted” Klein and “believed there was \n\nan innocent explanation” for all that had happened. Id. at 839‐40. \n\n II. Post‐Trial Proceedings \n\n\n\n\n 11 \n \n\f \n Schulman moved for a judgment of acquittal after the government rested, \n\narguing, among other things, that the evidence did not establish that he intended \n\nfor Klein to trade in King securities. The district court denied Schulman’s motion. \n\nSchulman renewed his motion for a judgment of acquittal at the conclusion of the \n\nevidence, and the district court again denied the motion. Thereafter, the district \n\ncourt charged the jury, and, a little over a day later, the jury returned guilty \n\nverdicts on both counts. \n\n Schulman then moved for a judgment of acquittal pursuant to Federal \n\nRule of Criminal Procedure 29. Schulman argued, inter alia, that no reasonable \n\njury could have inferred that he told Klein more than the “king for a day” \n\ncomment and that no reasonable jury could have found that he had intended \n\nKlein to trade on it. The district court denied Schulman’s motion by reasoned \n\nopinion. Thereafter, the district court sentenced Schulman on both counts to \n\nthree years’ probation to run concurrently, a $50,000 fine, forfeiture in the \n\namount of $15,527, and 2,000 hours of community service. This appeal timely \n\nfollowed. \n\n\n\n\n 12 \n \n\f \n DISCUSSION \n\n We review de novo a district court’s order denying a Rule 29 motion \n\naddressing the sufficiency of the evidence. United States v. Khalil, 857 F.3d 137, \n\n139 (2d Cir. 2017). In challenging the jury’s verdict, a Rule 29 movant “bears a \n\nheavy burden.” Martoma, 894 F.3d at 72.1 A reviewing court must “credit[] every \n\ninference that could have been drawn in the government’s favor,” id., and \n\n“affirm the conviction so long as, from the inferences reasonably drawn, the jury \n\nmight fairly have concluded guilt beyond a reasonable doubt.” United States v. \n\nReifler, 446 F.3d 65, 94 (2d Cir. 2006).  \n\n Moreover, in considering Schulman’s sufficiency challenge, we do not \n\nevaluate the evidence piecemeal or in isolation. We view the evidence “in \n\nconjunction” and uphold Schulman’s conviction “if any rational trier of fact \n\ncould have found the essential elements of the crime beyond a reasonable \n\ndoubt.” Id. at 94‐95; see Jackson v. Virginia, 443 U.S. 307, 319 (1979). While \n\n“specious inferences are not indulged,” United States v. Lorenzo, 534 F.3d 153, 159 \n\n\n\n                                               \n\n  1 Unless otherwise indicated, in quoting cases, all internal quotation marks, \nalterations, footnotes, and citations are omitted. \n\n 13 \n\f \n(2d Cir. 2008), we “defer to the jury’s determination of the weight of the evidence \n\nand the credibility of the witnesses, and to the jury’s choice of the competing \n\ninferences that can be drawn from the evidence,” Reifler, 446 F.3d at 94. In a close \n\ncase, where “either of the two results, a reasonable doubt or no reasonable doubt, \n\nis fairly possible, [we] must let the jury decide the matter.” United States v. \n\nAutuori, 212 F.3d 105, 114 (2d Cir. 2000). \n\n In an insider trading case, the government must prove that the insider will \n\npersonally benefit from the disclosure to the tippee. See Martoma, 894 F.3d at 73. \n\nPersonal benefit can be established in a number of ways, including by illustrating \n\nthe nature of the relationship between the tipper and the tippee or the tipper’s \n\nreceipt of something of value. The critical question regards the tipper’s purpose: \n\ndid the tipper share the material non‐public information with the tippee \n\nintending that the tippee use the information to improperly trade in securities? \n\nSee id. at 79 (a tipper is liable under 15 U.S.C. § 78j(b) if the tipper discloses \n\nmaterial, non‐public information “with the expectation that the tippee will trade \n\non it”); see also United States v. Gansman, 657 F.3d 85, 92 (2d Cir. 2011) (“In \n\nprosecuting a putative ‘tipper’ under the misappropriation theory of insider \n\n\n\n 14 \n \n\f \ntrading, the government must prove as an element of the offense that the tipper \n\nconveyed material nonpublic information to his ‘tippee’ with the understanding \n\nthat it would be used for securities trading purposes.”).2 Schulman argues that \n\n“[t]he Government presented no evidence [at trial], either direct or \n\ncircumstantial, that [he] intended for Klein to trade on” his tip about King. \n\nAppellant’s Br. at 26. According to Schulman, the evidence merely “suggests that \n\n[he] made a misguided comment to a friend in an effort to show off that he knew \n\nsomething that the public did not.” Id. at 22. \n\n We disagree. This is a case where it is essential to view the various pieces \n\nof evidence together. Although Schulman told the SEC that he had \n\ncommunicated “nothing” more than that he wished he could be king for a day, \n\nApp. at 240—a comment that, by itself, is innocuous—the jury was entitled to \n\ndisbelieve that he communicated nothing more. The district court properly \n\n\n                                               \n\n   2 As relevant here, 15 U.S.C. § 78j(b) prohibits the use of “any manipulative or \n\n deceptive device or contrivance” to contravene an SEC rule, including Rule 10b‐5. See 17 \n C.F.R. § 240.10b‐5. Rule 10b‐5 bars “undisclosed trading on inside corporate information \n by individuals who are under a duty of trust and confidence that prohibits them from \n secretly using such information for their personal advantage.” Salman v. United States, \n 137 S. Ct. 420, 423 (2016). “These persons also may not tip inside information to others \n for trading.” Id. \n\n 15 \n\f \ninstructed the jury to draw “reasonable inferences,” id. at 1290, and “us[e] \n\ncommon sense,” id. at 1317. As a matter of common sense, Schulman had to have \n\ncommunicated additional information for Schulman to concede to the SEC that \n\nhis king‐for‐a‐day comment was in fact “a reference to King Pharmaceuticals,” id. \n\nat 241. An oral statement does not usually reflect capitalization. Nonetheless, \n\nKlein apparently recognized that by “king” Schulman meant “King.” Common \n\nsense also would lead a rational juror to conclude that Schulman had to have \n\ncommunicated additional information to Klein for Klein to have promptly called \n\nShechtman, cited “inside information” about King and Pfizer, id. at 335, and \n\nbegun buying King stock. Indeed, this precise issue was argued to the jury, see id. \n\nat 1231‐32, 1265, and was resolved by the jury against Schulman. \n\n Further, the trial record is replete with evidence supporting an inference \n\nthat Schulman told Klein information about King so that Klein would trade on it. \n\nFor example, a reasonable jury could infer that Schulman intended Klein to trade \n\nfrom the evidence that (1) Klein was Schulman’s money manager, with \n\ndiscretionary authority over Schulman’s accounts, and that Schulman told Klein \n\nabout King during a meeting to discuss his investment portfolio; (2) after \n\n\n\n 16 \n \n\f \nmeeting with Schulman, Klein immediately bought hundreds of thousands of \n\ndollars of King stock, including in Schulman’s account and in the accounts of \n\nSchulman’s friends; and (3) Klein, on behalf of Schulman, had previously \n\npurchased stock in one of Schulman’s clients, Enzo. \n\n We reject Schulman’s arguments that Klein’s role as his financial advisor, \n\nand Klein’s conversations with Shechtman and purchases of King stock \n\nfollowing the meeting with Schulman are irrelevant. A rational jury could infer \n\nfrom the fact that Klein managed Schulman’s money and worked as a \n\nprofessional stock trader that Schulman intended Klein to trade on a stock tip he \n\nshared with him. The fact that Klein and Schulman were also close friends does \n\nnot detract from the relevance of Klein’s profession; in fact, it supplies an \n\nadditional motive for Schulman’s tip. Similarly, a rational jury could infer from \n\nthe fact that Klein purchased hundreds of thousands of dollars in King securities \n\nimmediately after meeting with Schulman, including over twenty‐five thousand \n\ndollars of King stock in Schulman’s account, that Klein was acting in accordance \n\nwith Schulman’s intent. This is true even though there were “virtually no \n\ncommunications” between Schulman and Klein in the months following \n\n\n\n 17 \n \n\f \nSchulman’s disclosure. Appellant’s Br. at 29. The jury was not required to accept \n\nSchulman’s contrary interpretation of the facts—that Klein’s purchase of stock \n\nfor Schulman was reckless and unthinking—as there is ample evidence in the \n\nrecord that Klein behaved in a calculated manner in trading on the information \n\nabout King. \n\n  We also reject Schulman’s argument that Klein’s prior purchase of Enzo \n\nstock is irrelevant. A reasonable jury could infer from the fact that Klein had once \n\ntraded in the stock of Schulman’s clients that he might be expected to do so \n\nagain. And, as Schulman was aware of Klein’s trading in Enzo, the jury could \n\nfurther infer that when Schulman told Klein about King, he expected Klein to act \n\non the information. In making these inferences, a reasonable jury could consider \n\nSchulman’s varying explanations for his disapproval of Klein’s prior purchase of \n\nEnzo stock. Specifically, when Schulman was first interviewed by the SEC in \n\n2012, he testified, “I remember being a little upset at [Klein for buying Enzo \n\nstock,] because I think that the CEO [of Enzo] is a certifiable lunatic.” App. at 245. \n\nBut several years later, Schulman told the USAO that the reason he criticized \n\nKlein for buying Enzo stock was that it was improper to own shares of a client. \n\n\n\n 18 \n \n\f \nSee id. at 242. The jury could reasonably view Schulman’s second explanation as a \n\nconscious attempt to sanitize his first explanation, which had criticized only the \n\neconomic soundness of the investment, not its legality or propriety. \n\n  In addition, Schulman’s first, and perhaps more genuine explanation, \n\nprovides further context for the king‐for‐a‐day comment. For example, the jury \n\ncould reasonably infer from the Enzo evidence that, while Klein knew that \n\nSchulman had been upset at him for buying Enzo shares because the CEO was a \n\n“lunatic,” Klein understood that Schulman’s stating a wish to be “[K]ing for a \n\nday” meant that buying King shares was, in fact, given Schulman’s inside \n\ninformation, a good idea.  \n\n In this regard, it is also relevant that Schulman thought that Klein’s \n\ninvestments in 2009 and 2010 had been “too bearish,” id. at 241, since Schulman’s \n\ndesire to invest more aggressively, along with his view of Klein’s Enzo purchase \n\nas unwise, could be viewed as fueling a desire by Schulman to help Klein achieve \n\ngreater returns in Schulman’s portfolio. And while Schulman argues that $15,000 \n\nwas so insignificant a fraction of his overall net worth that it could not have been \n\nan incentive for him to tip Klein, that sizable net worth entitled the jury to \n\n\n\n 19 \n \n\f \ndisbelieve Schulman’s preferred explanation that he made his king‐for‐a‐day \n\ncomment simply to “show off.” Appellant’s Br. at 22.  \n\n Finally, Schulman contends that he is entitled to a judgment of acquittal \n\nbecause the evidence supporting the inference that he intended Klein to trade on \n\nhis tip about King is, at the very least, in equipoise with evidence supporting an \n\ninference that he intended merely to boast. But it is not. Schulman cites mainly \n\nthe absence of evidence of any follow‐up conversations with Klein. This absence \n\nof evidence at best supports an inference that Schulman did not intend for Klein \n\nto trade for Schulman’s benefit. It says little, if anything, about whether \n\nSchulman intended Klein to trade for Klein’s benefit, an independent basis upon \n\nwhich a rational jury could have found Schulman guilty.3 Moreover, we know of \n\nno requirement in insider trading law that the government adduce evidence of \n\nmultiple conversations between co‐conspirators, or that the government provide \n\ndirect testimonial evidence regarding a defendant’s intent. See Lorenzo, 534 F.3d \n\n\n\n                                               \n\n 3  The Government argued at trial that Martoma’s “personal benefit” requirement \n was satisfied both because Schulman intended to receive a financial benefit and because \n Schulman intended to make a “gift” to Klein. The district court instructed the jury on \n both theories. \n\n 20 \n\f \nat 159 (the government “is entitled to prove its case solely through circumstantial \n\nevidence”).  \n\n CONCLUSION \n\n After conducting an independent review of the record and considering the \n\nevidence as a whole, we conclude that a rational trier of fact could have found \n\nthat Schulman acted with the requisite intent beyond a reasonable doubt. We \n\nhave considered all of Schulman’s contentions on appeal and have found in them \n\nno basis for reversal. Accordingly, the judgment of the district court is \n\nAFFIRMED. \n\n\n\n\n 21\n[END_CASE]", "role": "user" } ]
8,443,839
United States v. Tibor KLEIN, Robert Schulman
United States v. Klein
2019-01-10
Docket No. 17-3355; August Term, 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Chin, Katzmann, Kearse", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415265/", "author_raw": ""}]}
CHIN
KATZMANN
KEARSE
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443839/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Tibor KLEIN, Robert Schulman\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,580,816
United States v. Eaglin
2019-01-11
17-1224-cr
U.S. Court of Appeals for the Second Circuit
{"judges": "B e f o r e : CABRANES and CARNEY, Circuit Judges, and VILARDO, District Judge.", "parties": "", "opinions": [{"author": "SUSAN L. CARNEY, Circuit Judge:", "type": "010combined", "text": "17-1224-cr\nU.S. v. Eaglin\n\n\n\n17-1224-cr\nU.S. v. Eaglin\n\n\n\n In the\n United States Court of Appeals\n FOR THE SECOND CIRCUIT \n ______________  \n\n August Term, 2017 \n\n (Submitted:  March 7, 2018 Decided:  January 11, 2019) \n\n Docket No. 17‐1224‐cr \n ______________  \n\n UNITED STATES OF AMERICA, \n\n Appellee, \n\n –v.–\n\n JARRET EAGLIN, AKA JARRET L. EAGLIN, \n\n Defendant‐Appellant. \n ______________  \n\nB  e  f  o  r  e :\n\n CABRANES and CARNEY, Circuit Judges, and VILARDO, District Judge.* \n\n ______________  \n\nIn 2012, defendant‐appellant Jarret Eaglin was convicted of failing to register as a sex \noffender, in violation of 18 U.S.C. § 2250(a). In 2017, the United States District Court for \nthe Northern District of New York (D’Agostino, J.) found that Eaglin violated certain \nconditions of supervised release imposed as a consequence of the 2012 conviction. As \n\n\n*Judge Lawrence J. Vilardo, of the United States District Court for the Western District of New\nYork, sitting by designation. \n\f  \n\npunishment, it imposed a one‐year term of imprisonment to be followed by eleven \nyears of supervised release. In this appeal, Eaglin challenges two conditions of his 2017 \nsupervised release: a ban on accessing the Internet without prior specific permission of \nthe court and a total ban on viewing or possessing adult pornography. On abuse of \ndiscretion review, we conclude that the record as it stands does not support the \nimposition of these sweeping conditions. Eaglin was twice convicted over fifteen years \nago, when he was twenty‐one and twenty‐two years old, of having unlawful sexual \nrelationships with two thirteen‐year old girls, and since then has substantially, if \nimperfectly, complied with the terms of his extended periods of supervised release. His \ncrime of conviction now is failure to register as a sex offender. The District Court’s \nexplanation for its imposition of these conditions was wanting, but in light of the record \nbefore us we conclude that imposition of both the Internet ban and the pornography \nban was substantively unreasonable on this record as these conditions are not \nreasonably related to the relevant sentencing factors; further, they impose a greater \nrestriction than reasonably necessary to achieve the goals of sentencing in light of \nEaglin’s crime of conviction and his criminal history. Accordingly, the cause is \nREMANDED for resentencing consistent with this opinion. \n ______________ \n  \n Lisa A. Peebles, Federal Public Defender, Molly Corbett, \n James P. Egan, Assistant Federal Public Defenders, \n Office of the Federal Public Defender, Albany, New \n York, for Defendant‐Appellant.  \n  \n Richard D. Belliss, Paul D. Silver, Assistant United States \n Attorneys, for Grant C. Jaquith, Acting United States \n Attorney for the Northern District of New York, \n Albany, New York, for Appellee.  \n ______________ \n\nSUSAN L. CARNEY, Circuit Judge:   \n\n This case concerns the imposition of broad bans on Internet access and on \n\npossession of legal adult pornography as conditions of a multi‐year term of supervised \n\n\n  \n\n 2 \n  \n\f  \n\nrelease. We conclude that the record here does not support imposition of these \n\nsweeping prohibitions. To be sustained, a virtually categorical prohibition on a \n\ndefendant’s use of any device to access the Internet—a technology around which our \n\nsociety now unmistakably turns—must be carefully explained and robustly supported \n\nby a district court. As the Supreme Court recently reiterated, “cell phones and the \n\nservices they provide are ‘such a pervasive and insistent part of daily life’ that carrying \n\none is indispensable to participation in modern society.” Carpenter v. United States, 138 \n\nS. Ct. 2206, 2210 (2018) (quoting Riley v. California, 134 S. Ct. 2473, 2428 (2014)); see also \n\nPackingham v. North Carolina, 137 S. Ct. 1730 (2017). Although Internet access through \n\nsmart phones and other devices undeniably offers the potential for wrongdoing, to \n\nconsign an individual to a life virtually without access to the Internet is to exile that \n\nindividual from society. The record here inadequately supports the District Court’s \n\ndecision to take that drastic step. \n\n On abuse of discretion review, we conclude that both the virtual ban on Internet \n\naccess and the prohibition on viewing or possessing adult pornography are \n\nsubstantively unreasonable because, given the record before us, they are not reasonably \n\nrelated to the sentencing factors and impose a greater restriction than reasonably \n\nnecessary to achieve the goals of sentencing. The cause is REMANDED for \n\nresentencing consistent with this opinion. \n\n\n\n\n  \n\n 3 \n  \n\f  \n\n BACKGROUND2 \n\n Defendant‐Appellant Jarret Eaglin was convicted in 2003 and 2004 in New \n\nHampshire state court on four counts of felonious sexual assault. His convictions stem \n\nfrom his sexual relationships with two thirteen‐year‐old girls in that state when he was \n\ntwenty‐one and twenty‐two years old. Under New Hampshire law, “felonious sexual \n\nassault” is a statutory crime that is based on the age of the younger party alone, without \n\nregard to the age or mens rea of the perpetrator. N.H. Rev. Stat. § 632‐A:3 (2003) (to \n\n“[e]ngage[] in sexual penetration with a person . . . under 16 years of age” is a class B \n\nfelony); see Goodrow v. Perrin, 119 N.H. 483, 488 (1979) (no scienter requirement in § 632‐\n\nA:3). For the convictions related to the first victim, Eaglin received a sentence of twelve \n\nmonths’ incarceration and two years’ probation; for the conviction related to the second \n\nvictim, he received a deferred sentence and five years’ probation. The convictions \n\nrender Eaglin a “sex offender” under federal law, 34 U.S.C. § 20911, and obligate him to \n\ncomply with certain federal statutory registration requirements applicable to sex \n\noffenders, 18 U.S.C. § 2250.  \n\n In the fifteen years that have passed since his first convictions, Eaglin has \n\nstruggled to comply fully with the multiple conditions of his supervised release, which \n\nhave been renewed and revised on several occasions. He also has struggled to abide by \n\nthe requirements resulting from his sex offender status. In 2005, for example, he was \n\nremanded to custody for three breaches: failing to report a 2004 arrest following a \n\n                                                  \n\n2 The relevant facts are largely undisputed by the parties and are drawn from the documentary \nrecord including the 2012 Presentence Investigation Report (“PSR”) prepared with regard to \ndefendant Eaglin. We note in the text any significant differences in the parties’ accounts. \n  \n\n 4 \n  \n\f  \n\ndomestic dispute with his girlfriend,3 failing to complete a sex offender counseling \n\nprogram, and failing to obtain permission from his probation officer before changing \n\nhis place of residence. More recently, in September 2012, Eaglin pleaded guilty in the \n\nU.S. District Court for the District of New Hampshire to violating the federal \n\nregistration statute by failing to register as a sex offender when he moved from New \n\nHampshire to New York in August 2011. For that conviction, he was sentenced by \n\nJudge Joseph A. Diclerico, Jr., to twenty‐one months’ imprisonment and fifteen years of \n\nsupervised release.  \n\n In early 2014, the job of monitoring Eaglin’s compliance with the terms of his \n\nsupervised release for his 2012 conviction was transferred to the Northern District of \n\nNew York, so that Eaglin could legally return to Glen Falls, New York, and live near his \n\nimmediate family. His compliance challenges continued, however, in New York: in May \n\n2014, Eaglin was penalized with a two‐month home detention period for his failure to \n\nreport incidental contact with a minor and his chronic unemployment. As part of this \n\ndetention, Eaglin was instructed to stay away from his former residence, where the \n\nincidental contact occurred. In July 2014, he was again penalized—this time, with a two‐\n\nmonth period of curfew—after he failed to report that he had returned briefly without \n\npermission to his former residence (where his sister then resided) to get a ride to his sex \n\noffender treatment program after (as the Probation Office described it) “the bus he was \n\nsupposed to take to treatment broke down.” App. 14. And in 2015, a warrant issued for \n\nEaglin’s arrest after, over a period of months, he violated several conditions of release \n\n                                                  \n\n3 As a result of that dispute, Eaglin was convicted in New Hampshire state proceedings of \nresisting arrest and simple assault and sentenced to six months’ imprisonment.  \n  \n\n 5 \n  \n\f  \n\nby failing to participate in a sex offender treatment program, failing to notify his \n\nprobation officer of a change in employment, failing to register a new address with the \n\nstate sex offender registry, viewing and possessing adult pornography, and traveling \n\noutside the Northern District of New York to central Massachusetts without permission. \n\nFor those violations, Judge D’Agostino of the U.S. District Court for the Northern \n\nDistrict of New York sentenced Eaglin to sixteen months of incarceration, to be followed \n\nby thirteen years of supervised release. On the recommendation of the government and \n\nof the Probation Office, the District Court continued to impose conditions banning \n\naccess to sexually explicit materials and banning access to the Internet unless he \n\nparticipated in a monitoring program that would be run by Probation.  \n\n  Eaglin was released from prison and returned to supervised release status in \n\nAugust 2016. Once again, Eaglin struggled to comply with the terms of release. In April \n\n2017, Eaglin admitted to viewing and possessing sexually explicit images of adults, in \n\nviolation of the special conditions to which he was subject, and to using email accounts \n\nthat he had not registered with the New York state sex offender registry, as required by \n\nlaw. App. 69‐70; see N.Y. Correct. Law § 168‐f(4) (requiring that a sex offender provide \n\nthe state any “internet identifiers that such offender uses,” including email accounts). \n\nFor those violations, the District Court, now familiar with Eaglin from his repeated \n\nvisits on conditions violations of various sorts, sentenced him anew to twelve months of \n\nimprisonment and eleven years of supervised release.  \n\n In connection with those April 2017 proceedings, Eaglin’s counsel requested by \n\nletter that the District Court not reimpose two specific conditions of release to which \n\nEaglin earlier had been subject: the restrictions on his possession and use of Internet‐\n\n  \n\n 6 \n  \n\f  \n\ncapable devices, App. 51, and the condition that he “not view, possess, own, subscribe \n\nto or purchase any material, including pictures, videotapes, films, magazines, books, \n\ntelephone services, electronic media, computer programs, or computer service[s] that \n\ndepict sexually explicit conduct,” id. at 52. He argued that neither of these conditions \n\nwas reasonably related to Eaglin’s 2012 offense of conviction (his failure to register) and \n\nthat they imposed a “greater deprivation of liberty than reasonably necessary” to serve \n\nthe purposes of sentencing contrary to the principles underlying 18 U.S.C. § 3553 \n\n(“Imposition of sentence”). Id. at 54‐58.  \n\n For its part, the government took a diametrically opposed view, urging the court \n\nboth to reimpose the relevant conditions and to expand their scope: in particular, that \n\nthe Internet‐capable device restriction “be modified such that the defendant also be \n\nprohibited from accessing the Internet” entirely. App. 59. The government justified its \n\nrequest by pointing to a 2015 incident in which, without the permission of his probation \n\nofficer, Eaglin traveled out‐of‐state to Massachusetts to meet an adult woman whom he \n\nmet through an online dating website.4 This travel, it explained, was an example of \n\nEaglin’s continued efforts to “find sexual partners and to access pornography,” which it \n\nidentified as “risk factors.”5 App. 60. The government also cited Eaglin’s efforts to “hide \n\n[his] phone from Probation because he knew he would use the phone to try to find \n\n\n                                                  \n\n4 That woman later told police that Eaglin had raped her, but shortly thereafter recanted her \nstatement. All related charges against Eaglin were ultimately dismissed. \n\n5 In its 2017 presentencing letter, the government advised that it viewed Eaglin’s searches for \nsexual partners and for pornography not as “otherwise healthy sexual behavior,” but as \nactivities that “may lead to high‐risk behavior.” App. 60.  \n  \n\n 7 \n  \n\f  \n\nsexual partners and view pornography.” Id. The government presented these conditions \n\nto the district court as “necessary in this case to protect the public, to deter the \n\ndefendant from committing future violations, and to promote the rehabilitation of the \n\ndefendant.” Id. \n\n At sentencing, the District Court addressed the proposed pornography and \n\nInternet bans together, expressing the view that each was “very, very necessary” \n\nbecause Eaglin had used “an Internet‐capable device to look for sexual partners and to \n\nview pornography.” App. 73. The court continued,  \n\n I  think  that  it  is  very risky  for  you,  sir,  to be  using  Internet \n devices and I think that based upon your previous conviction, \n your underlying conviction, that it is very advisable that you \n stay off of the Internet, that you are prevented from using or \n viewing pornography. I’m aware it’s not child pornography \n at  this  point  that  is  being  viewed  but  these  appear  to  be \n significant risk factors to you in terms of your conduct.  \nId. at 73‐74. Remarking on the Probation Office’s report that Eaglin had attempted to \n\nhide his smartphone from his probation officer, the District Court commented without \n\nfurther explanation that “when you get Internet‐capable devices, when you view \n\npornography, I happen to believe that the community is at risk from you.” Id. at 74. As \n\nthe government had requested, the District Court then imposed conditions barring \n\nEaglin from “access[ing] the Internet from any computer or Internet‐capable device in \n\nany location unless authorized by the Court or as directed by the U.S. Probation Office \n\nupon approval of the Court,” id. at 77‐78, and banning him entirely from viewing or \n\n\n\n\n  \n\n 8 \n  \n\f  \n\npossessing material “that depict[s] sexually explicit conduct,” as more fully set forth in \n\nthe margin.6 Id. at 77. \n\n Eaglin timely appealed.  \n\n\n DISCUSSION \n\n We review the imposition of conditions of supervised release for abuse of \n\ndiscretion and any related legal rulings de novo. United States v. Johnson, 446 F.3d 272, \n\n277 (2d Cir. 2006). We review sentencing decisions for procedural and substantive \n\nreasonableness. See United States v. Cavera, 550 F.3d 180, 189 (2d Cir. 2008) (en banc). \n\n For a sentence to be procedurally reasonable, a District Court must “make an \n\nindividualized assessment when determining whether to impose a special condition of \n\nsupervised release, and . . . state on the record the reason for imposing it.” United States \n\nv. Betts, 886 F.3d 198, 202 (2d Cir. 2018). Any explanation provided by the District Court \n\nmust be adequately supported by the record. We reverse a sentence for substantive \n\nunreasonableness only “for those few cases that, although procedurally correct, would \n\nnonetheless damage the administration of justice because the sentence imposed was \n\nshockingly high, shockingly low, or otherwise unsupportable as a matter of law.” \n\nUnited States v. Mi Sun Cho, 713 F.3d 716, 723 (2d Cir. 2013) (per curiam) (quoting United \n\nStates v. Rigas, 583 F.3d 108, 123 (2d Cir. 2009)). We have held as a general matter that a \n\n                                                  \n\n6 The pornography condition provides that Eaglin “must not view, possess, own, subscribe to or \npurchase any material, including pictures, videotapes, films, magazines, books, telephone \nservices, electronic media, computer programs, or computer services that depict sexually \nexplicit conduct, as defined in 18 U.S.C. § 2256(2).” Id. It identifies no possible exceptions. See \nApp. 77‐78 (quoting District Judge’s oral pronouncement). \n  \n\n 9 \n  \n\f  \n\ndistrict court “may impose special conditions of supervised release that are \n\nreasonably related to certain statutory factors governing sentencing, ‘involve[] no \n\ngreater deprivation of liberty than is reasonably necessary’ to implement the statutory \n\npurposes of sentencing, and are consistent with pertinent Sentencing Commission \n\npolicy statements.” United States v. Myers, 426 F.3d 117, 123‐24 (2d Cir. 2005) (quoting 18 \n\nU.S.C. § 3583(d)); see also 18 U.S.C. § 3563; U.S.S.G. § 5D1.3(b). The “certain statutory \n\nfactors governing sentencing” to which we referred in Myers are set out in 18 U.S.C. \n\n§ 3553(a) and include, “the nature and circumstances of the offense and the history and \n\ncharacteristics of the defendant,” 18 U.S.C. § 3553(a)(1), as well as: \n\n the  need  for  the  sentence  imposed  (A)  to  reflect  the \n seriousness of the offense, to promote the respect for the law, \n and to provide just punishment for the offense; (B) to afford \n adequate  deterrence  to  criminal  conduct;  (C)  to  protect  the \n public  from  further  crimes  of  the  defendant;  and  (D)  to \n provide the defendant with needed educational or vocational \n training, medical care, or other correctional treatment in the \n most effective manner  \n\n18 U.S.C. § 3553(a)(2). Although we generally defer to the District Court’s discretionary \n\nassessment of the suitability of conditions of supervised release, we will “carefully \n\nscrutinize unusual and severe conditions.” United States v. Peterson, 248 F.3d 79, 82 (2d \n\nCir. 2001) (per curiam) (quoting United States v. Doe, 79 F.3d 1309, 1319‐20 (2d Cir. \n\n1996)). The conditions imposed here—prohibiting access to the Internet and to legal \n\nadult pornography—are such unusual and severe conditions; they merit our close \n\nexamination. Eaglin argues primarily that the eleven‐year virtually categorical bans on \n\nhis access to the Internet and to legal adult pornography are overly broad and \n\nunreasonably onerous. Both involve, he contends, a greater deprivation of liberty than \n  \n\n 10 \n  \n\f  \n\nis reasonably necessary to implement the statutory purposes we have just set forth. He \n\nargues further that the District Court did not justify either condition sufficiently, on the \n\nrecord, as reasonably related to any of the relevant sentencing factors.  \n\n Upon due consideration, we agree with Eaglin that the record as it now stands \n\nreveals an insufficient connection between each of these two conditions and the offense \n\nof conviction. The record also fails to reveal the District Court’s basis for identifying a \n\nconnection between the conditions and the likelihood of harm. The District Court’s \n\ngeneral reference to the conditions as being necessary to protect the community does \n\nnot suffice, even on the background of Eaglin’s repeated infractions of the better‐\n\nfounded terms of supervised release. We must conclude, therefore, that, on this record, \n\nthese conditions are substantively unreasonable because they are not reasonably related \n\nto the relevant sentencing factors and involve a greater deprivation of liberty than is \n\nreasonably necessary. The cause is remanded for further consideration and resentencing \n\nin accordance with this opinion. We set forth our reasons in greater detail below.  \n\n\nI. Internet ban \n\n Where a condition of supervised release implicates a constitutional right, we \n\nconduct a more searching review in light of the “heightened constitutional concerns” \n\npresented in such cases. Myers, 426 F.3d at 126. The government argues that Eaglin has \n\nno constitutional right to access the Internet. We reject that position as outdated and in \n\nconflict with recent Supreme Court precedent. The Supreme Court forcefully identified \n\nsuch a right in Packingham v. North Carolina, 137 S. Ct. 1730 (2017), and it suggested as \n\nmuch in Riley v. California, 134 S. Ct. 2473, 2428 (2014), as we adverted to above. \n\n\n  \n\n 11 \n  \n\f  \n\n  In Packingham, the Supreme Court struck down as unconstitutional a North \n\nCarolina criminal statute that made it a felony for sex offenders to access certain social \n\nmedia websites. 137 S. Ct. at 1738. The Court reasoned that, “to foreclose access to social \n\nmedia altogether is to prevent the user from engaging in the legitimate exercise of First \n\nAmendment rights.” Id. at 1737. By enforcing such a restriction, the Court elaborated, \n\n“North Carolina with one broad stroke bars access to what for many are the principal \n\nsources for knowing current events, checking ads for employment, speaking and \n\nlistening in the modern public square, and otherwise exploring the vast realms of \n\nhuman thought and knowledge.” Id. The Court stated that it had never “approved of a \n\nstatute as broad in its reach.” Id.  \n\n The restriction in Packingham created a permanent restriction in the form of a \n\ncriminal statute applicable to all registered sex offenders. See id. (noting the “troubling \n\nfact” that the offending statute imposed restrictions on persons who were no longer \n\nsubject to the supervision of the criminal justice system). The restriction that Eaglin \n\nchallenges here, in contrast, was imposed as a condition of supervised release that \n\napplies to Eaglin alone and for a limited albeit lengthy duration. Certain severe \n\nrestrictions may be unconstitutional when cast as a broadly‐applicable criminal \n\nprohibition, but permissible when imposed on an individual as a condition of \n\nsupervised release. See Farrell v. Burke, 449 F.3d 470, 497 (2d Cir. 2006) (“[T]he First \n\nAmendment rights of parolees are circumscribed.”). In our view, Packingham \n\nnevertheless establishes that, in modern society, citizens have a First Amendment right \n\nto access the Internet.  \n\n\n\n\n  \n\n 12 \n  \n\f  \n\n The substance of the Internet ban imposed on Eaglin is even broader in its terms, \n\nif not in its application, than that struck down in Packingham. Whereas the Packingham \n\nstatute banned access only to certain social networking sites where minors may be \n\npresent, such as Facebook and Twitter, the condition imposed on Eaglin prohibits his \n\naccess to all websites.7 It therefore implicates the same First Amendment concerns that \n\nwere at issue in Packingham: Eaglin has a First Amendment right to be able to email, \n\nblog, and discuss the issues of the day on the Internet while he is on supervised release. \n\nMoreover, one of the conditions of supervised release is that he remain employed: to \n\nsearch for a job in 2019, the Internet is nearly essential, as the Court in Packingham \n\nrecognized. 137 S. Ct. at 1737.  \n\n Even before Packingham was decided, we rejected total bans on Internet access in \n\nseveral cases challenging similar conditions of supervised release. For example, in \n\nPeterson, in 2001, we vacated a ban on Internet access as overly broad where the \n\ndefendant had been convicted of bank larceny but had been charged with violating \n\nconditions of supervised release by viewing adult pornography. 248 F.3d at 82. \n\nAlthough we acknowledged “a relationship” between Peterson’s Internet restriction \n\nand his conviction for incest predating his larceny conviction, we concluded \n\nnonetheless that “the condition [was] neither reasonably related to that conviction nor \n\nreasonably necessary to the sentencing objectives.” Id. at 83 (emphasis in original; \n\ninternal quotation marks omitted). Critically, the record in Peterson displayed “no \n\n\n                                                  \n\n7 Because the District Court adopted the condition on the government’s recommendation for a \ncomplete Internet ban and required specific permission from the court for any desired instances \nof internet access, we understand the condition effectively to operate as a total Internet ban.  \n  \n\n 13 \n  \n\f  \n\nindication that Peterson’s past incest offense had any connection to computers or to the \n\nInternet.” Id. We thus determined that the facts of Peterson’s case did not warrant “so \n\nbroad a prohibition” on his Internet usage. Id. \n\n Similarly, in United States v. Sofsky, in 2002, we held that a total Internet ban \n\ninflicted a greater deprivation of liberty than was reasonably necessary in the case of a \n\ndefendant who had illegally downloaded child pornography. 287 F.3d 122, 126 (2d Cir. \n\n2002). Like the Court in Packingham, we were concerned that such a ban “prevents use \n\nof e‐mail . . . [and] other common‐place computer uses such as doing any research, \n\ngetting a weather forecast, or reading a newspaper online”—activities that raise no \n\nobvious risk of criminal activity. Id. (internal quotation marks omitted).  \n\n Our sister circuits have similarly rejected absolute Internet bans even where the \n\ndefendant had used the computer for ill in his crime of conviction. See, e.g., United States \n\nv. LaCoste, 821 F.3d 1187, 1192 (9th Cir. 2016) (rejecting Internet ban where defendant \n\nconspired to commit securities fraud); United States v. Wiedower, 634 F.3d 490, 495 (8th \n\nCir. 2011) (rejecting Internet ban where defendant was convicted of possessing child \n\npornography); United States v. Perazza‐Mercado, 553 F.3d 65, 72‐74 (1st Cir. 2009) \n\n(rejecting Internet ban in the home where crime of conviction involved defendant \n\nknowingly engaging in sexual contact with a female under the age of twelve); United \n\nStates v. Freeman, 316 F.3d 386, 391‐92 (3d Cir. 2003) (rejecting Internet ban where \n\ndefendant was convicted of receiving and possessing child pornography); United States \n\nv. Holm, 326 F.3d 872, 877 (7th Cir. 2003) (rejecting Internet ban where defendant was \n\nconvicted of possessing child pornography). \n\n\n\n  \n\n 14 \n  \n\f  \n\n In light of our precedent, and as emphasized by Packingham’s recognition of a \n\nFirst Amendment right to access certain social networking websites, the imposition of a \n\ntotal Internet ban as a condition of supervised release inflicts a severe deprivation of \n\nliberty. In only highly unusual circumstances will a total Internet ban imposed as a \n\ncondition of supervised release be substantively reasonable and not amount to a \n\n“‘greater deprivation of liberty than is reasonably necessary’ to implement the statutory \n\npurposes of sentencing.” Myers, 426 F.3d at 123‐24 (quoting 18 U.S.C. § 3583(d)). On the \n\nrecord before us, the imposition of a total Internet ban for the eleven‐year period of \n\nEaglin’s supervised release is substantively unreasonable as it has not been shown to be \n\n“reasonably related” to the statutory factors governing sentencing nor to be reasonably \n\nnecessary to effectuate the sentencing objectives.  \n\n First, the record does not demonstrate that an Internet ban is reasonably related \n\nto “the nature and circumstances” of the crime of conviction or to Eaglin’s “history and \n\ncharacteristics.” 18 U.S.C. § 3553(a)(1). So far as we can see, the Internet has nothing to \n\ndo with Eaglin’s 2012 offense of failing to register as a sex offender. Nor has Eaglin been \n\ncharged with or convicted of a sex crime involving Internet use. This is not a case in \n\nwhich the crime of conviction or the violation of supervised release involved using the \n\nInternet to prey on children or otherwise endanger the public. Cf. Johnson, 446 F.3d at \n\n282‐83 (upholding ban where defendant previously used the Internet to convince \n\nchildren to meet him and have sex). Indeed, as the District Court noted, the record \n\ncontains no evidence that Eaglin accessed child pornography online (or at all). As we \n\nwarned in Peterson, recognizing that “a computer with Internet access offers the \n\npossibility of abusive use for illegitimate purposes” provides an insufficient justification \n\n\n  \n\n 15 \n  \n\f  \n\nfor an all‐out prohibition absent a close connection to the defendant’s past illegal \n\nconduct, or strong independent grounds for linking it to a real potential for future \n\nharm. 248 F.3d at 83 (emphasis added). Here, neither the nature and circumstances of \n\nEaglin’s failure to register nor his history and characteristics meaningfully support the \n\ndrastic step of imposing a complete Internet ban on Eaglin as means of protecting the \n\npublic or deterring recidivism.8  \n\n Moreover, imposing an Internet ban would arguably impair Eaglin’s ability to \n\nreceive “needed educational or vocational training, medical care, or other correctional \n\ntreatment in the most effective manner”—one of the goals of sentencing. 18 U.S.C. \n\n§ 3553(a)(2)(D). Today, as we observed above, access to the Internet is essential to \n\nreintegrating supervisees into everyday life, as it provides avenues for seeking \n\nemployment, banking, accessing government resources, reading about current events, \n\nand educating oneself. See, e.g., Carpenter, 138 S. Ct. at 2210 (carrying a cell or smart \n\nphone “is indispensable to participation in modern society”). Yet when imposing the \n\nsweeping Internet ban challenged here, the District Court did not address on the record \n\n                                                  \n\n8 Although the District Court did not address these concerns on the record, we observe and note \nour concern that the government’s sentencing memorandum adverted to “prior sexual assault \nconvictions involving both minor and adult victims, one of which involved the knife point rape \nof an adult female.” App. 60. Other than Eaglin’s 2003 and 2004 convictions for non‐violent \nfelonious sexual assault, the record on appeal reflects no convictions for sexual assault. The \nrecord does, however, reflect that Eaglin was acquitted by a jury in 2005 of charges that he had \nsexually assaulted a girlfriend at knifepoint. And in 2015, as mentioned above, Eaglin was \narrested for rape, and the charges were dismissed when the woman recanted her initial \nstatement and told police she had not been raped. To the extent that the government intended \nto invite the District Court to consider charges of which Eaglin was not convicted, we \nnonetheless question whether a total, outright Internet ban is sustainable in place of the \nconditions monitoring Internet use previously imposed.  \n  \n\n 16 \n  \n\f  \n\nthe likely adverse impact of isolating Eaglin from these important positive uses of the \n\nInternet or engage in any explicit balancing of these competing interests.  \n\n Finally, it is not clear from the record that an Internet ban was reasonably \n\nnecessary to effectuate any of the purposes of 18 U.S.C. § 3553(a)(2). Although the \n\nDistrict Court asserted that “the community is at risk from” Eaglin when he accesses the \n\nInternet, App. at 74, we are not persuaded that the Internet ban is reasonably necessary \n\nto “protect the public from [Eaglin’s] further crimes,” 18 U.S.C. § 3553(a)(2)(C). Both the \n\ngovernment and the District Court appear to have viewed a total Internet ban as a \n\nnecessary means of preventing Eaglin from viewing adult pornography (of which more \n\nwill be said below) and from identifying potential romantic or sexual partners.9 See \n\nAppellee’s Br. 24‐25; App. 73‐74. But the earlier Internet restriction placed on Eaglin, \n\nunder which his Internet use was monitored by the Probation Office, remained to all \n\noutward appearances a viable option. Such a restriction would adequately protect the \n\npublic from Eaglin’s potential misuse of the Internet while imposing a more reasonable \n\nburden on Eaglin’s First Amendment interest in accessing the Internet. See United States \n\nv. Browder, 866 F.3d 504, 512 (2d Cir. 2017) (holding that a condition of supervised \n\nrelease that imposed a “narrowly tailored” computer monitoring program on a \n\ndefendant convicted of child pornography possession was not an excessive deprivation \n\n\n                                                  \n\n9 To the extent that the District Court disapproved of Eaglin seeking out consensual adult sexual \npartners, the absence of a detailed explanation for its disapproval leaves us concerned. The \n“right to enter into and to maintain intimate personal relationships,” including sexual ones, is a \n“well‐established” liberty interest. United States v. Reeves, 591 F.3d 77, 82 (2d Cir. 2010). Unless \nthe record contains strong evidence of a reason for concern—and we saw none here—a court \nimposing conditions of supervised release must tread especially lightly in this area. \n  \n\n 17 \n  \n\f  \n\nof liberty). The record does not explain why such monitoring was insufficient, other \n\nthan by noting the Probation Office’s concern that, while under that restriction, Eaglin \n\nsuccessfully contacted an adult woman who agreed to an encounter with him. If \n\nEaglin’s potential contact with children is of concern, despite the record’s dearth of \n\nevidence suggesting that Eaglin is likely to seek out children on social media or prey on \n\nthem in reality, the District Court must make a record of the basis for such concerns and \n\ncraft restrictions that address them with particularity. As the Supreme Court noted in \n\nPackingham, such specific and narrowly tailored restrictions “must be the State’s first \n\nresort to ward off the serious harm that sexual crimes inflict.” 137 S. Ct at 1737.  \n\n In short, the Internet ban imposed on Eaglin severely encroached on his First \n\nAmendment rights by depriving him of the opportunity to engage with modern society. \n\nAnd it did so without any clear evidence in the record that the condition was warranted \n\nby Eaglin’s criminal history or characteristics, the need for deterrence or to protect the \n\npublic, or the court’s desire to provide necessary rehabilitative services to Eaglin. We \n\ntherefore conclude that the District Court exceeded the permissible bounds of its \n\ndiscretion in imposing this substantively unreasonable condition: the untailored \n\nInternet ban is not reasonably related to the relevant sentencing factors and involves a \n\ngreater deprivation of liberty than is reasonably necessary to serve the relevant \n\nsentencing objectives.  \n\n\nII. Pornography Ban \n\n Eaglin also challenges the condition of supervised release that prohibits him \n\nfrom viewing or possessing legal adult pornography. We tolerate such conditions only \n\nin limited circumstances: “Pornographic materials . . . receive full First \n  \n\n 18 \n  \n\f  \n\nAmendment protection when in the possession of ordinary adults, but may be \n\nregulated in the hands of parolees to a much greater extent.” Farrell, 449 F.3d at 497. To \n\nbe permissible, however, a condition prohibiting access to adult pornography must be \n\nreasonably related to the enumerated statutory factors and must impose no greater \n\ndeprivation of liberty than reasonably necessary. See United States v. Simmons, 343 F.3d \n\n72, 80 (2d Cir. 2003).  \n\n Applying these standards, we have routinely rejected bans on possession of \n\nadult pornography as a condition of supervised release where the district court failed \n\nadequately to connect the need for that condition to the defendant’s likelihood of \n\nrecidivism or to another sentencing factor. See, e.g., United States v. Brown, 653 F. App’x \n\n50, 52 (2d Cir. 2016) (summary order); United States v. Singer, 693 F. App’x 47, 48 (2d Cir. \n\n2017) (summary order). Such bans must be supported on the record by detailed factual \n\nfindings establishing that the proposed ban is reasonably related to the sentencing \n\nfactors set forth in 18 U.S.C. § 3553(a) and that it is reasonably necessary to accomplish \n\ntheir objectives. A general reference to “the public interest” ordinarily will not suffice. \n\n In this case, the District Court identified nothing in the record that adequately \n\njustifies imposing an adult pornography ban. This District Court said only that “when \n\nyou view pornography, I happen to believe that the community is at risk from you.” \n\nApp. 74. This general statement does not explain why possessing or viewing adult \n\npornography might in the court’s view prompt Eaglin to commit a new offense or cause \n\nhim to pose a risk to the public. Although the District Court repeatedly described \n\nEaglin’s viewing of pornography as “risky,” it never explained why such behavior \n\nrepresented a particular risk. See App. 73‐74. Upon review of the record, we have \n\n  \n\n 19 \n  \n\f  \n\nidentified no evidence that would support such a finding. Nor does the record \n\notherwise demonstrate that the condition was reasonably related to Eaglin’s criminal \n\nhistory or the other sentencing factors of factors set forth in 18 U.S.C. § 3553(a). \n\n In requesting the imposition of such a condition, the government cited our recent \n\nnonprecedential decision in United States v. Springer, 684 F. App’x 37 (2d Cir. 2017) \n\n(summary order), where we upheld an adult pornography ban as a condition of \n\nsupervised release. But there, the record was considerably more robust than here, and \n\nthe district court “made clear the reasons it incorporated the pornography restrictions \n\ninto Springer’s release conditions.” Id. at 40. In addition to Springer’s extensive record \n\nof violating release conditions, the court there considered Springer’s history of sex \n\noffenses involving both children and adults. (Springer had six such convictions, five of \n\nthem involving children and the sixth involving a teenager who was 19 years old). The \n\nDistrict Court also had before it an evaluation submitted by a mental health provider \n\nexplicitly “recommending that Springer be prohibited from accessing any pornographic \n\nmaterials.” Id.  \n\n Some comments made by the District Court here appear to reflect a worry that \n\nEaglin might one day view or possess child pornography. See, e.g., App. 73‐74 (“I’m \n\naware it’s not child pornography at this point that is being viewed but [Internet access \n\nand pornography] appear to be significant risk factors to you[.]”). But, if that was the \n\nreason for the ban, the court did little to explain on the record the source of that \n\nconsternation. The government has not directed us to record evidence suggesting that \n\nEaglin has a history of viewing child pornography or that he has expressed a desire to \n\ndo so such that the public needs to be protected from this potential future crime. The \n\n  \n\n 20 \n  \n\f  \n\nconnection to children that Eaglin’s criminal record evinces is found only in the \n\nstatutory convictions for his sexual relationships with two teenage girls fifteen years \n\nago when he was twenty‐one and twenty‐two years old. We do not minimize the \n\ngravity of those statutory crimes. But the record reflects no finding as to Eaglin’s mens \n\nrea with respect to those offenses, and neither involved child pornography. And the \n\nrecord of any sexual involvement by him with children in the past fifteen years is blank, \n\nso far as we can see. \n\n Before imposing a special condition such as this ban on adult pornography, a \n\ndistrict court must make factual findings supporting its view that the condition is \n\ndesigned to address a realistic danger and that the deprivation the condition creates is \n\nno greater than reasonably necessary to serve the sentencing factors. See Myers, 426 F.3d \n\nat 128. Here, the record does not suggest that Eaglin is likely to seek out child \n\npornography, so we are unable to count that risk as a legitimate basis for this condition.  \n\n And even if the District Court had found that Eaglin presented some risk of \n\nseeking to obtain and possess child pornography, it would still need to support its \n\nblanket ban on his accessing adult pornography by reference to the relevant statutory \n\nfactors. Here, the District Court erroneously treated the possession of adult \n\npornography as reprehensible in itself, rather than as an otherwise lawful action that \n\nviolated Eaglin’s conditions of supervised release. Imposing a wholesale ban on \n\naccessing adult pornography might be justified where the offense of conviction \n\ninvolved the creation of adult pornography with unconsenting victims, see, e.g., \n\nSimmons, 343 F.3d at 82, or where a mental health professional testified that viewing \n\npornography would be detrimental to the defendant’s rehabilitation, see, e.g., Springer, \n\n  \n\n 21 \n  \n\f  \n\n684 F. App’x at 40. In line with the decisions of many other courts, however, we \n\nconclude that a blanket ban on possessing or accessing adult pornography cannot be \n\nimposed unless such a ban on adult pornography is reasonably related to the sentencing \n\nfactors and reasonably necessary to accomplish the goals of sentencing.  \n\n Finally, the record provides inadequate support for the proposition that a \n\ndecade‐long deprivation of access to constitutionally permissible material is reasonably \n\nnecessary to protect the public or meet the other sentencing goals of 18 U.S.C. § 3553(a). \n\nIn finding an adult pornography ban to be more restrictive than necessary to achieve \n\nthe goals of sentencing where there is little indication that access to such material will \n\nimpede a defendant’s rehabilitation or put the community at risk, we have company. \n\nSee United States v. Taylor, 796 F.3d 788, 793 (7th Cir. 2015) (“It is true that both Taylor’s \n\ncrime and adult pornography have to do with sexual activity. But there is no evidence \n\nthat viewing or listening to adult pornography in any way led Taylor to commit the \n\ncrime here, or has led him to commit any other crime, nor is there any evidence in the \n\nrecord that viewing or listening to adult pornography would make the repeat of \n\nTaylor’s crime or similar crimes any more likely.”); United States v. Salazar, 743 F.3d 445, \n\n452 (5th Cir. 2014) (“It is hard to imagine how preventing Salazar from accessing \n\nsexually stimulating materials would prevent future criminal conduct when there is no \n\nindication in the record that Salazar has an unhealthy relationship with such materials \n\nor that such materials contributed to his underlying crimes or other violations.”); United \n\nStates v. Perazza‐Mercado, 553 F.3d 65, 76 (1st Cir. 2009) (“If the district court believed \n\nthat there was some relationship between the defendant’s possession and use of adult \n\npornography and the likelihood that he would engage in sexual misconduct involving \n\n\n  \n\n 22 \n  \n\f  \n\nyoung girls, the court should have explained the basis for that conclusion.”); United \n\nStates v. Voelker, 489 F.3d 139, 152‐53 (3d Cir. 2007) (“[N]othing on this record suggests \n\nthat sexually explicit material involving only adults contributed in any way to Voelker’s \n\noffense, nor is there any reason to believe that viewing such material would cause \n\nVoelker to reoffend”). \n\n In sum, on this record, we can discern no reasonable relation between Eaglin’s \n\nunderlying offense of failure to register, his criminal history (including his fifteen‐year \n\nold statutory rape crimes), his likelihood of recidivism, or need for rehabilitative \n\nservice, on the one hand, and the District Court’s wholesale restriction of his possession \n\nof legal adult pornography, on the other. Nor have we been directed to any record \n\nevidence suggesting Eaglin’s rehabilitation will be impaired by viewing such \n\npornography. We conclude, therefore, that the District Court’s imposition of this \n\ncondition was substantively unreasonable in that it was not reasonably related to the \n\nsentencing factors and not reasonably necessary to achieve a statutorily recognized \n\nsentencing objective. Accordingly, the condition must be struck. \n\n\n CONCLUSION \n\n We conclude that the special conditions of supervised release banning access to \n\nthe Internet and to adult pornography are substantively unreasonable in the \n\ncircumstances presented here because neither is reasonably related to the relevant \n\nsentencing factors and both involve a greater deprivation of liberty than is reasonably \n\nnecessary to implement the statutory purposes of sentencing. Accordingly, we \n\nREMAND the cause for resentencing consistent with this opinion.  \n\n\n  \n\n 23", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358069/", "author_raw": "SUSAN L. CARNEY, Circuit Judge:"}]}
CABRANES
CARNEY
VILARDO
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580816/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Eaglin\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-11\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17-1224-cr\nU.S. v. Eaglin\n\n\n\n17-1224-cr\nU.S. v. Eaglin\n\n\n\n In the\n United States Court of Appeals\n FOR THE SECOND CIRCUIT \n ______________  \n\n August Term, 2017 \n\n (Submitted:  March 7, 2018 Decided:  January 11, 2019) \n\n Docket No. 17‐1224‐cr \n ______________  \n\n UNITED STATES OF AMERICA, \n\n Appellee, \n\n –v.–\n\n JARRET EAGLIN, AKA JARRET L. EAGLIN, \n\n Defendant‐Appellant. \n ______________  \n\nB  e  f  o  r  e :\n\n CABRANES and CARNEY, Circuit Judges, and VILARDO, District Judge.* \n\n ______________  \n\nIn 2012, defendant‐appellant Jarret Eaglin was convicted of failing to register as a sex \noffender, in violation of 18 U.S.C. § 2250(a). In 2017, the United States District Court for \nthe Northern District of New York (D’Agostino, J.) found that Eaglin violated certain \nconditions of supervised release imposed as a consequence of the 2012 conviction. As \n\n\n*Judge Lawrence J. Vilardo, of the United States District Court for the Western District of New\nYork, sitting by designation. \n\f  \n\npunishment, it imposed a one‐year term of imprisonment to be followed by eleven \nyears of supervised release. In this appeal, Eaglin challenges two conditions of his 2017 \nsupervised release: a ban on accessing the Internet without prior specific permission of \nthe court and a total ban on viewing or possessing adult pornography. On abuse of \ndiscretion review, we conclude that the record as it stands does not support the \nimposition of these sweeping conditions. Eaglin was twice convicted over fifteen years \nago, when he was twenty‐one and twenty‐two years old, of having unlawful sexual \nrelationships with two thirteen‐year old girls, and since then has substantially, if \nimperfectly, complied with the terms of his extended periods of supervised release. His \ncrime of conviction now is failure to register as a sex offender. The District Court’s \nexplanation for its imposition of these conditions was wanting, but in light of the record \nbefore us we conclude that imposition of both the Internet ban and the pornography \nban was substantively unreasonable on this record as these conditions are not \nreasonably related to the relevant sentencing factors; further, they impose a greater \nrestriction than reasonably necessary to achieve the goals of sentencing in light of \nEaglin’s crime of conviction and his criminal history. Accordingly, the cause is \nREMANDED for resentencing consistent with this opinion. \n ______________ \n  \n Lisa A. Peebles, Federal Public Defender, Molly Corbett, \n James P. Egan, Assistant Federal Public Defenders, \n Office of the Federal Public Defender, Albany, New \n York, for Defendant‐Appellant.  \n  \n Richard D. Belliss, Paul D. Silver, Assistant United States \n Attorneys, for Grant C. Jaquith, Acting United States \n Attorney for the Northern District of New York, \n Albany, New York, for Appellee.  \n ______________ \n\nSUSAN L. CARNEY, Circuit Judge:   \n\n This case concerns the imposition of broad bans on Internet access and on \n\npossession of legal adult pornography as conditions of a multi‐year term of supervised \n\n\n  \n\n 2 \n  \n\f  \n\nrelease. We conclude that the record here does not support imposition of these \n\nsweeping prohibitions. To be sustained, a virtually categorical prohibition on a \n\ndefendant’s use of any device to access the Internet—a technology around which our \n\nsociety now unmistakably turns—must be carefully explained and robustly supported \n\nby a district court. As the Supreme Court recently reiterated, “cell phones and the \n\nservices they provide are ‘such a pervasive and insistent part of daily life’ that carrying \n\none is indispensable to participation in modern society.” Carpenter v. United States, 138 \n\nS. Ct. 2206, 2210 (2018) (quoting Riley v. California, 134 S. Ct. 2473, 2428 (2014)); see also \n\nPackingham v. North Carolina, 137 S. Ct. 1730 (2017). Although Internet access through \n\nsmart phones and other devices undeniably offers the potential for wrongdoing, to \n\nconsign an individual to a life virtually without access to the Internet is to exile that \n\nindividual from society. The record here inadequately supports the District Court’s \n\ndecision to take that drastic step. \n\n On abuse of discretion review, we conclude that both the virtual ban on Internet \n\naccess and the prohibition on viewing or possessing adult pornography are \n\nsubstantively unreasonable because, given the record before us, they are not reasonably \n\nrelated to the sentencing factors and impose a greater restriction than reasonably \n\nnecessary to achieve the goals of sentencing. The cause is REMANDED for \n\nresentencing consistent with this opinion. \n\n\n\n\n  \n\n 3 \n  \n\f  \n\n BACKGROUND2 \n\n Defendant‐Appellant Jarret Eaglin was convicted in 2003 and 2004 in New \n\nHampshire state court on four counts of felonious sexual assault. His convictions stem \n\nfrom his sexual relationships with two thirteen‐year‐old girls in that state when he was \n\ntwenty‐one and twenty‐two years old. Under New Hampshire law, “felonious sexual \n\nassault” is a statutory crime that is based on the age of the younger party alone, without \n\nregard to the age or mens rea of the perpetrator. N.H. Rev. Stat. § 632‐A:3 (2003) (to \n\n“[e]ngage[] in sexual penetration with a person . . . under 16 years of age” is a class B \n\nfelony); see Goodrow v. Perrin, 119 N.H. 483, 488 (1979) (no scienter requirement in § 632‐\n\nA:3). For the convictions related to the first victim, Eaglin received a sentence of twelve \n\nmonths’ incarceration and two years’ probation; for the conviction related to the second \n\nvictim, he received a deferred sentence and five years’ probation. The convictions \n\nrender Eaglin a “sex offender” under federal law, 34 U.S.C. § 20911, and obligate him to \n\ncomply with certain federal statutory registration requirements applicable to sex \n\noffenders, 18 U.S.C. § 2250.  \n\n In the fifteen years that have passed since his first convictions, Eaglin has \n\nstruggled to comply fully with the multiple conditions of his supervised release, which \n\nhave been renewed and revised on several occasions. He also has struggled to abide by \n\nthe requirements resulting from his sex offender status. In 2005, for example, he was \n\nremanded to custody for three breaches: failing to report a 2004 arrest following a \n\n                                                  \n\n2 The relevant facts are largely undisputed by the parties and are drawn from the documentary \nrecord including the 2012 Presentence Investigation Report (“PSR”) prepared with regard to \ndefendant Eaglin. We note in the text any significant differences in the parties’ accounts. \n  \n\n 4 \n  \n\f  \n\ndomestic dispute with his girlfriend,3 failing to complete a sex offender counseling \n\nprogram, and failing to obtain permission from his probation officer before changing \n\nhis place of residence. More recently, in September 2012, Eaglin pleaded guilty in the \n\nU.S. District Court for the District of New Hampshire to violating the federal \n\nregistration statute by failing to register as a sex offender when he moved from New \n\nHampshire to New York in August 2011. For that conviction, he was sentenced by \n\nJudge Joseph A. Diclerico, Jr., to twenty‐one months’ imprisonment and fifteen years of \n\nsupervised release.  \n\n In early 2014, the job of monitoring Eaglin’s compliance with the terms of his \n\nsupervised release for his 2012 conviction was transferred to the Northern District of \n\nNew York, so that Eaglin could legally return to Glen Falls, New York, and live near his \n\nimmediate family. His compliance challenges continued, however, in New York: in May \n\n2014, Eaglin was penalized with a two‐month home detention period for his failure to \n\nreport incidental contact with a minor and his chronic unemployment. As part of this \n\ndetention, Eaglin was instructed to stay away from his former residence, where the \n\nincidental contact occurred. In July 2014, he was again penalized—this time, with a two‐\n\nmonth period of curfew—after he failed to report that he had returned briefly without \n\npermission to his former residence (where his sister then resided) to get a ride to his sex \n\noffender treatment program after (as the Probation Office described it) “the bus he was \n\nsupposed to take to treatment broke down.” App. 14. And in 2015, a warrant issued for \n\nEaglin’s arrest after, over a period of months, he violated several conditions of release \n\n                                                  \n\n3 As a result of that dispute, Eaglin was convicted in New Hampshire state proceedings of \nresisting arrest and simple assault and sentenced to six months’ imprisonment.  \n  \n\n 5 \n  \n\f  \n\nby failing to participate in a sex offender treatment program, failing to notify his \n\nprobation officer of a change in employment, failing to register a new address with the \n\nstate sex offender registry, viewing and possessing adult pornography, and traveling \n\noutside the Northern District of New York to central Massachusetts without permission. \n\nFor those violations, Judge D’Agostino of the U.S. District Court for the Northern \n\nDistrict of New York sentenced Eaglin to sixteen months of incarceration, to be followed \n\nby thirteen years of supervised release. On the recommendation of the government and \n\nof the Probation Office, the District Court continued to impose conditions banning \n\naccess to sexually explicit materials and banning access to the Internet unless he \n\nparticipated in a monitoring program that would be run by Probation.  \n\n  Eaglin was released from prison and returned to supervised release status in \n\nAugust 2016. Once again, Eaglin struggled to comply with the terms of release. In April \n\n2017, Eaglin admitted to viewing and possessing sexually explicit images of adults, in \n\nviolation of the special conditions to which he was subject, and to using email accounts \n\nthat he had not registered with the New York state sex offender registry, as required by \n\nlaw. App. 69‐70; see N.Y. Correct. Law § 168‐f(4) (requiring that a sex offender provide \n\nthe state any “internet identifiers that such offender uses,” including email accounts). \n\nFor those violations, the District Court, now familiar with Eaglin from his repeated \n\nvisits on conditions violations of various sorts, sentenced him anew to twelve months of \n\nimprisonment and eleven years of supervised release.  \n\n In connection with those April 2017 proceedings, Eaglin’s counsel requested by \n\nletter that the District Court not reimpose two specific conditions of release to which \n\nEaglin earlier had been subject: the restrictions on his possession and use of Internet‐\n\n  \n\n 6 \n  \n\f  \n\ncapable devices, App. 51, and the condition that he “not view, possess, own, subscribe \n\nto or purchase any material, including pictures, videotapes, films, magazines, books, \n\ntelephone services, electronic media, computer programs, or computer service[s] that \n\ndepict sexually explicit conduct,” id. at 52. He argued that neither of these conditions \n\nwas reasonably related to Eaglin’s 2012 offense of conviction (his failure to register) and \n\nthat they imposed a “greater deprivation of liberty than reasonably necessary” to serve \n\nthe purposes of sentencing contrary to the principles underlying 18 U.S.C. § 3553 \n\n(“Imposition of sentence”). Id. at 54‐58.  \n\n For its part, the government took a diametrically opposed view, urging the court \n\nboth to reimpose the relevant conditions and to expand their scope: in particular, that \n\nthe Internet‐capable device restriction “be modified such that the defendant also be \n\nprohibited from accessing the Internet” entirely. App. 59. The government justified its \n\nrequest by pointing to a 2015 incident in which, without the permission of his probation \n\nofficer, Eaglin traveled out‐of‐state to Massachusetts to meet an adult woman whom he \n\nmet through an online dating website.4 This travel, it explained, was an example of \n\nEaglin’s continued efforts to “find sexual partners and to access pornography,” which it \n\nidentified as “risk factors.”5 App. 60. The government also cited Eaglin’s efforts to “hide \n\n[his] phone from Probation because he knew he would use the phone to try to find \n\n\n                                                  \n\n4 That woman later told police that Eaglin had raped her, but shortly thereafter recanted her \nstatement. All related charges against Eaglin were ultimately dismissed. \n\n5 In its 2017 presentencing letter, the government advised that it viewed Eaglin’s searches for \nsexual partners and for pornography not as “otherwise healthy sexual behavior,” but as \nactivities that “may lead to high‐risk behavior.” App. 60.  \n  \n\n 7 \n  \n\f  \n\nsexual partners and view pornography.” Id. The government presented these conditions \n\nto the district court as “necessary in this case to protect the public, to deter the \n\ndefendant from committing future violations, and to promote the rehabilitation of the \n\ndefendant.” Id. \n\n At sentencing, the District Court addressed the proposed pornography and \n\nInternet bans together, expressing the view that each was “very, very necessary” \n\nbecause Eaglin had used “an Internet‐capable device to look for sexual partners and to \n\nview pornography.” App. 73. The court continued,  \n\n I  think  that  it  is  very risky  for  you,  sir,  to be  using  Internet \n devices and I think that based upon your previous conviction, \n your underlying conviction, that it is very advisable that you \n stay off of the Internet, that you are prevented from using or \n viewing pornography. I’m aware it’s not child pornography \n at  this  point  that  is  being  viewed  but  these  appear  to  be \n significant risk factors to you in terms of your conduct.  \nId. at 73‐74. Remarking on the Probation Office’s report that Eaglin had attempted to \n\nhide his smartphone from his probation officer, the District Court commented without \n\nfurther explanation that “when you get Internet‐capable devices, when you view \n\npornography, I happen to believe that the community is at risk from you.” Id. at 74. As \n\nthe government had requested, the District Court then imposed conditions barring \n\nEaglin from “access[ing] the Internet from any computer or Internet‐capable device in \n\nany location unless authorized by the Court or as directed by the U.S. Probation Office \n\nupon approval of the Court,” id. at 77‐78, and banning him entirely from viewing or \n\n\n\n\n  \n\n 8 \n  \n\f  \n\npossessing material “that depict[s] sexually explicit conduct,” as more fully set forth in \n\nthe margin.6 Id. at 77. \n\n Eaglin timely appealed.  \n\n\n DISCUSSION \n\n We review the imposition of conditions of supervised release for abuse of \n\ndiscretion and any related legal rulings de novo. United States v. Johnson, 446 F.3d 272, \n\n277 (2d Cir. 2006). We review sentencing decisions for procedural and substantive \n\nreasonableness. See United States v. Cavera, 550 F.3d 180, 189 (2d Cir. 2008) (en banc). \n\n For a sentence to be procedurally reasonable, a District Court must “make an \n\nindividualized assessment when determining whether to impose a special condition of \n\nsupervised release, and . . . state on the record the reason for imposing it.” United States \n\nv. Betts, 886 F.3d 198, 202 (2d Cir. 2018). Any explanation provided by the District Court \n\nmust be adequately supported by the record. We reverse a sentence for substantive \n\nunreasonableness only “for those few cases that, although procedurally correct, would \n\nnonetheless damage the administration of justice because the sentence imposed was \n\nshockingly high, shockingly low, or otherwise unsupportable as a matter of law.” \n\nUnited States v. Mi Sun Cho, 713 F.3d 716, 723 (2d Cir. 2013) (per curiam) (quoting United \n\nStates v. Rigas, 583 F.3d 108, 123 (2d Cir. 2009)). We have held as a general matter that a \n\n                                                  \n\n6 The pornography condition provides that Eaglin “must not view, possess, own, subscribe to or \npurchase any material, including pictures, videotapes, films, magazines, books, telephone \nservices, electronic media, computer programs, or computer services that depict sexually \nexplicit conduct, as defined in 18 U.S.C. § 2256(2).” Id. It identifies no possible exceptions. See \nApp. 77‐78 (quoting District Judge’s oral pronouncement). \n  \n\n 9 \n  \n\f  \n\ndistrict court “may impose special conditions of supervised release that are \n\nreasonably related to certain statutory factors governing sentencing, ‘involve[] no \n\ngreater deprivation of liberty than is reasonably necessary’ to implement the statutory \n\npurposes of sentencing, and are consistent with pertinent Sentencing Commission \n\npolicy statements.” United States v. Myers, 426 F.3d 117, 123‐24 (2d Cir. 2005) (quoting 18 \n\nU.S.C. § 3583(d)); see also 18 U.S.C. § 3563; U.S.S.G. § 5D1.3(b). The “certain statutory \n\nfactors governing sentencing” to which we referred in Myers are set out in 18 U.S.C. \n\n§ 3553(a) and include, “the nature and circumstances of the offense and the history and \n\ncharacteristics of the defendant,” 18 U.S.C. § 3553(a)(1), as well as: \n\n the  need  for  the  sentence  imposed  (A)  to  reflect  the \n seriousness of the offense, to promote the respect for the law, \n and to provide just punishment for the offense; (B) to afford \n adequate  deterrence  to  criminal  conduct;  (C)  to  protect  the \n public  from  further  crimes  of  the  defendant;  and  (D)  to \n provide the defendant with needed educational or vocational \n training, medical care, or other correctional treatment in the \n most effective manner  \n\n18 U.S.C. § 3553(a)(2). Although we generally defer to the District Court’s discretionary \n\nassessment of the suitability of conditions of supervised release, we will “carefully \n\nscrutinize unusual and severe conditions.” United States v. Peterson, 248 F.3d 79, 82 (2d \n\nCir. 2001) (per curiam) (quoting United States v. Doe, 79 F.3d 1309, 1319‐20 (2d Cir. \n\n1996)). The conditions imposed here—prohibiting access to the Internet and to legal \n\nadult pornography—are such unusual and severe conditions; they merit our close \n\nexamination. Eaglin argues primarily that the eleven‐year virtually categorical bans on \n\nhis access to the Internet and to legal adult pornography are overly broad and \n\nunreasonably onerous. Both involve, he contends, a greater deprivation of liberty than \n  \n\n 10 \n  \n\f  \n\nis reasonably necessary to implement the statutory purposes we have just set forth. He \n\nargues further that the District Court did not justify either condition sufficiently, on the \n\nrecord, as reasonably related to any of the relevant sentencing factors.  \n\n Upon due consideration, we agree with Eaglin that the record as it now stands \n\nreveals an insufficient connection between each of these two conditions and the offense \n\nof conviction. The record also fails to reveal the District Court’s basis for identifying a \n\nconnection between the conditions and the likelihood of harm. The District Court’s \n\ngeneral reference to the conditions as being necessary to protect the community does \n\nnot suffice, even on the background of Eaglin’s repeated infractions of the better‐\n\nfounded terms of supervised release. We must conclude, therefore, that, on this record, \n\nthese conditions are substantively unreasonable because they are not reasonably related \n\nto the relevant sentencing factors and involve a greater deprivation of liberty than is \n\nreasonably necessary. The cause is remanded for further consideration and resentencing \n\nin accordance with this opinion. We set forth our reasons in greater detail below.  \n\n\nI. Internet ban \n\n Where a condition of supervised release implicates a constitutional right, we \n\nconduct a more searching review in light of the “heightened constitutional concerns” \n\npresented in such cases. Myers, 426 F.3d at 126. The government argues that Eaglin has \n\nno constitutional right to access the Internet. We reject that position as outdated and in \n\nconflict with recent Supreme Court precedent. The Supreme Court forcefully identified \n\nsuch a right in Packingham v. North Carolina, 137 S. Ct. 1730 (2017), and it suggested as \n\nmuch in Riley v. California, 134 S. Ct. 2473, 2428 (2014), as we adverted to above. \n\n\n  \n\n 11 \n  \n\f  \n\n  In Packingham, the Supreme Court struck down as unconstitutional a North \n\nCarolina criminal statute that made it a felony for sex offenders to access certain social \n\nmedia websites. 137 S. Ct. at 1738. The Court reasoned that, “to foreclose access to social \n\nmedia altogether is to prevent the user from engaging in the legitimate exercise of First \n\nAmendment rights.” Id. at 1737. By enforcing such a restriction, the Court elaborated, \n\n“North Carolina with one broad stroke bars access to what for many are the principal \n\nsources for knowing current events, checking ads for employment, speaking and \n\nlistening in the modern public square, and otherwise exploring the vast realms of \n\nhuman thought and knowledge.” Id. The Court stated that it had never “approved of a \n\nstatute as broad in its reach.” Id.  \n\n The restriction in Packingham created a permanent restriction in the form of a \n\ncriminal statute applicable to all registered sex offenders. See id. (noting the “troubling \n\nfact” that the offending statute imposed restrictions on persons who were no longer \n\nsubject to the supervision of the criminal justice system). The restriction that Eaglin \n\nchallenges here, in contrast, was imposed as a condition of supervised release that \n\napplies to Eaglin alone and for a limited albeit lengthy duration. Certain severe \n\nrestrictions may be unconstitutional when cast as a broadly‐applicable criminal \n\nprohibition, but permissible when imposed on an individual as a condition of \n\nsupervised release. See Farrell v. Burke, 449 F.3d 470, 497 (2d Cir. 2006) (“[T]he First \n\nAmendment rights of parolees are circumscribed.”). In our view, Packingham \n\nnevertheless establishes that, in modern society, citizens have a First Amendment right \n\nto access the Internet.  \n\n\n\n\n  \n\n 12 \n  \n\f  \n\n The substance of the Internet ban imposed on Eaglin is even broader in its terms, \n\nif not in its application, than that struck down in Packingham. Whereas the Packingham \n\nstatute banned access only to certain social networking sites where minors may be \n\npresent, such as Facebook and Twitter, the condition imposed on Eaglin prohibits his \n\naccess to all websites.7 It therefore implicates the same First Amendment concerns that \n\nwere at issue in Packingham: Eaglin has a First Amendment right to be able to email, \n\nblog, and discuss the issues of the day on the Internet while he is on supervised release. \n\nMoreover, one of the conditions of supervised release is that he remain employed: to \n\nsearch for a job in 2019, the Internet is nearly essential, as the Court in Packingham \n\nrecognized. 137 S. Ct. at 1737.  \n\n Even before Packingham was decided, we rejected total bans on Internet access in \n\nseveral cases challenging similar conditions of supervised release. For example, in \n\nPeterson, in 2001, we vacated a ban on Internet access as overly broad where the \n\ndefendant had been convicted of bank larceny but had been charged with violating \n\nconditions of supervised release by viewing adult pornography. 248 F.3d at 82. \n\nAlthough we acknowledged “a relationship” between Peterson’s Internet restriction \n\nand his conviction for incest predating his larceny conviction, we concluded \n\nnonetheless that “the condition [was] neither reasonably related to that conviction nor \n\nreasonably necessary to the sentencing objectives.” Id. at 83 (emphasis in original; \n\ninternal quotation marks omitted). Critically, the record in Peterson displayed “no \n\n\n                                                  \n\n7 Because the District Court adopted the condition on the government’s recommendation for a \ncomplete Internet ban and required specific permission from the court for any desired instances \nof internet access, we understand the condition effectively to operate as a total Internet ban.  \n  \n\n 13 \n  \n\f  \n\nindication that Peterson’s past incest offense had any connection to computers or to the \n\nInternet.” Id. We thus determined that the facts of Peterson’s case did not warrant “so \n\nbroad a prohibition” on his Internet usage. Id. \n\n Similarly, in United States v. Sofsky, in 2002, we held that a total Internet ban \n\ninflicted a greater deprivation of liberty than was reasonably necessary in the case of a \n\ndefendant who had illegally downloaded child pornography. 287 F.3d 122, 126 (2d Cir. \n\n2002). Like the Court in Packingham, we were concerned that such a ban “prevents use \n\nof e‐mail . . . [and] other common‐place computer uses such as doing any research, \n\ngetting a weather forecast, or reading a newspaper online”—activities that raise no \n\nobvious risk of criminal activity. Id. (internal quotation marks omitted).  \n\n Our sister circuits have similarly rejected absolute Internet bans even where the \n\ndefendant had used the computer for ill in his crime of conviction. See, e.g., United States \n\nv. LaCoste, 821 F.3d 1187, 1192 (9th Cir. 2016) (rejecting Internet ban where defendant \n\nconspired to commit securities fraud); United States v. Wiedower, 634 F.3d 490, 495 (8th \n\nCir. 2011) (rejecting Internet ban where defendant was convicted of possessing child \n\npornography); United States v. Perazza‐Mercado, 553 F.3d 65, 72‐74 (1st Cir. 2009) \n\n(rejecting Internet ban in the home where crime of conviction involved defendant \n\nknowingly engaging in sexual contact with a female under the age of twelve); United \n\nStates v. Freeman, 316 F.3d 386, 391‐92 (3d Cir. 2003) (rejecting Internet ban where \n\ndefendant was convicted of receiving and possessing child pornography); United States \n\nv. Holm, 326 F.3d 872, 877 (7th Cir. 2003) (rejecting Internet ban where defendant was \n\nconvicted of possessing child pornography). \n\n\n\n  \n\n 14 \n  \n\f  \n\n In light of our precedent, and as emphasized by Packingham’s recognition of a \n\nFirst Amendment right to access certain social networking websites, the imposition of a \n\ntotal Internet ban as a condition of supervised release inflicts a severe deprivation of \n\nliberty. In only highly unusual circumstances will a total Internet ban imposed as a \n\ncondition of supervised release be substantively reasonable and not amount to a \n\n“‘greater deprivation of liberty than is reasonably necessary’ to implement the statutory \n\npurposes of sentencing.” Myers, 426 F.3d at 123‐24 (quoting 18 U.S.C. § 3583(d)). On the \n\nrecord before us, the imposition of a total Internet ban for the eleven‐year period of \n\nEaglin’s supervised release is substantively unreasonable as it has not been shown to be \n\n“reasonably related” to the statutory factors governing sentencing nor to be reasonably \n\nnecessary to effectuate the sentencing objectives.  \n\n First, the record does not demonstrate that an Internet ban is reasonably related \n\nto “the nature and circumstances” of the crime of conviction or to Eaglin’s “history and \n\ncharacteristics.” 18 U.S.C. § 3553(a)(1). So far as we can see, the Internet has nothing to \n\ndo with Eaglin’s 2012 offense of failing to register as a sex offender. Nor has Eaglin been \n\ncharged with or convicted of a sex crime involving Internet use. This is not a case in \n\nwhich the crime of conviction or the violation of supervised release involved using the \n\nInternet to prey on children or otherwise endanger the public. Cf. Johnson, 446 F.3d at \n\n282‐83 (upholding ban where defendant previously used the Internet to convince \n\nchildren to meet him and have sex). Indeed, as the District Court noted, the record \n\ncontains no evidence that Eaglin accessed child pornography online (or at all). As we \n\nwarned in Peterson, recognizing that “a computer with Internet access offers the \n\npossibility of abusive use for illegitimate purposes” provides an insufficient justification \n\n\n  \n\n 15 \n  \n\f  \n\nfor an all‐out prohibition absent a close connection to the defendant’s past illegal \n\nconduct, or strong independent grounds for linking it to a real potential for future \n\nharm. 248 F.3d at 83 (emphasis added). Here, neither the nature and circumstances of \n\nEaglin’s failure to register nor his history and characteristics meaningfully support the \n\ndrastic step of imposing a complete Internet ban on Eaglin as means of protecting the \n\npublic or deterring recidivism.8  \n\n Moreover, imposing an Internet ban would arguably impair Eaglin’s ability to \n\nreceive “needed educational or vocational training, medical care, or other correctional \n\ntreatment in the most effective manner”—one of the goals of sentencing. 18 U.S.C. \n\n§ 3553(a)(2)(D). Today, as we observed above, access to the Internet is essential to \n\nreintegrating supervisees into everyday life, as it provides avenues for seeking \n\nemployment, banking, accessing government resources, reading about current events, \n\nand educating oneself. See, e.g., Carpenter, 138 S. Ct. at 2210 (carrying a cell or smart \n\nphone “is indispensable to participation in modern society”). Yet when imposing the \n\nsweeping Internet ban challenged here, the District Court did not address on the record \n\n                                                  \n\n8 Although the District Court did not address these concerns on the record, we observe and note \nour concern that the government’s sentencing memorandum adverted to “prior sexual assault \nconvictions involving both minor and adult victims, one of which involved the knife point rape \nof an adult female.” App. 60. Other than Eaglin’s 2003 and 2004 convictions for non‐violent \nfelonious sexual assault, the record on appeal reflects no convictions for sexual assault. The \nrecord does, however, reflect that Eaglin was acquitted by a jury in 2005 of charges that he had \nsexually assaulted a girlfriend at knifepoint. And in 2015, as mentioned above, Eaglin was \narrested for rape, and the charges were dismissed when the woman recanted her initial \nstatement and told police she had not been raped. To the extent that the government intended \nto invite the District Court to consider charges of which Eaglin was not convicted, we \nnonetheless question whether a total, outright Internet ban is sustainable in place of the \nconditions monitoring Internet use previously imposed.  \n  \n\n 16 \n  \n\f  \n\nthe likely adverse impact of isolating Eaglin from these important positive uses of the \n\nInternet or engage in any explicit balancing of these competing interests.  \n\n Finally, it is not clear from the record that an Internet ban was reasonably \n\nnecessary to effectuate any of the purposes of 18 U.S.C. § 3553(a)(2). Although the \n\nDistrict Court asserted that “the community is at risk from” Eaglin when he accesses the \n\nInternet, App. at 74, we are not persuaded that the Internet ban is reasonably necessary \n\nto “protect the public from [Eaglin’s] further crimes,” 18 U.S.C. § 3553(a)(2)(C). Both the \n\ngovernment and the District Court appear to have viewed a total Internet ban as a \n\nnecessary means of preventing Eaglin from viewing adult pornography (of which more \n\nwill be said below) and from identifying potential romantic or sexual partners.9 See \n\nAppellee’s Br. 24‐25; App. 73‐74. But the earlier Internet restriction placed on Eaglin, \n\nunder which his Internet use was monitored by the Probation Office, remained to all \n\noutward appearances a viable option. Such a restriction would adequately protect the \n\npublic from Eaglin’s potential misuse of the Internet while imposing a more reasonable \n\nburden on Eaglin’s First Amendment interest in accessing the Internet. See United States \n\nv. Browder, 866 F.3d 504, 512 (2d Cir. 2017) (holding that a condition of supervised \n\nrelease that imposed a “narrowly tailored” computer monitoring program on a \n\ndefendant convicted of child pornography possession was not an excessive deprivation \n\n\n                                                  \n\n9 To the extent that the District Court disapproved of Eaglin seeking out consensual adult sexual \npartners, the absence of a detailed explanation for its disapproval leaves us concerned. The \n“right to enter into and to maintain intimate personal relationships,” including sexual ones, is a \n“well‐established” liberty interest. United States v. Reeves, 591 F.3d 77, 82 (2d Cir. 2010). Unless \nthe record contains strong evidence of a reason for concern—and we saw none here—a court \nimposing conditions of supervised release must tread especially lightly in this area. \n  \n\n 17 \n  \n\f  \n\nof liberty). The record does not explain why such monitoring was insufficient, other \n\nthan by noting the Probation Office’s concern that, while under that restriction, Eaglin \n\nsuccessfully contacted an adult woman who agreed to an encounter with him. If \n\nEaglin’s potential contact with children is of concern, despite the record’s dearth of \n\nevidence suggesting that Eaglin is likely to seek out children on social media or prey on \n\nthem in reality, the District Court must make a record of the basis for such concerns and \n\ncraft restrictions that address them with particularity. As the Supreme Court noted in \n\nPackingham, such specific and narrowly tailored restrictions “must be the State’s first \n\nresort to ward off the serious harm that sexual crimes inflict.” 137 S. Ct at 1737.  \n\n In short, the Internet ban imposed on Eaglin severely encroached on his First \n\nAmendment rights by depriving him of the opportunity to engage with modern society. \n\nAnd it did so without any clear evidence in the record that the condition was warranted \n\nby Eaglin’s criminal history or characteristics, the need for deterrence or to protect the \n\npublic, or the court’s desire to provide necessary rehabilitative services to Eaglin. We \n\ntherefore conclude that the District Court exceeded the permissible bounds of its \n\ndiscretion in imposing this substantively unreasonable condition: the untailored \n\nInternet ban is not reasonably related to the relevant sentencing factors and involves a \n\ngreater deprivation of liberty than is reasonably necessary to serve the relevant \n\nsentencing objectives.  \n\n\nII. Pornography Ban \n\n Eaglin also challenges the condition of supervised release that prohibits him \n\nfrom viewing or possessing legal adult pornography. We tolerate such conditions only \n\nin limited circumstances: “Pornographic materials . . . receive full First \n  \n\n 18 \n  \n\f  \n\nAmendment protection when in the possession of ordinary adults, but may be \n\nregulated in the hands of parolees to a much greater extent.” Farrell, 449 F.3d at 497. To \n\nbe permissible, however, a condition prohibiting access to adult pornography must be \n\nreasonably related to the enumerated statutory factors and must impose no greater \n\ndeprivation of liberty than reasonably necessary. See United States v. Simmons, 343 F.3d \n\n72, 80 (2d Cir. 2003).  \n\n Applying these standards, we have routinely rejected bans on possession of \n\nadult pornography as a condition of supervised release where the district court failed \n\nadequately to connect the need for that condition to the defendant’s likelihood of \n\nrecidivism or to another sentencing factor. See, e.g., United States v. Brown, 653 F. App’x \n\n50, 52 (2d Cir. 2016) (summary order); United States v. Singer, 693 F. App’x 47, 48 (2d Cir. \n\n2017) (summary order). Such bans must be supported on the record by detailed factual \n\nfindings establishing that the proposed ban is reasonably related to the sentencing \n\nfactors set forth in 18 U.S.C. § 3553(a) and that it is reasonably necessary to accomplish \n\ntheir objectives. A general reference to “the public interest” ordinarily will not suffice. \n\n In this case, the District Court identified nothing in the record that adequately \n\njustifies imposing an adult pornography ban. This District Court said only that “when \n\nyou view pornography, I happen to believe that the community is at risk from you.” \n\nApp. 74. This general statement does not explain why possessing or viewing adult \n\npornography might in the court’s view prompt Eaglin to commit a new offense or cause \n\nhim to pose a risk to the public. Although the District Court repeatedly described \n\nEaglin’s viewing of pornography as “risky,” it never explained why such behavior \n\nrepresented a particular risk. See App. 73‐74. Upon review of the record, we have \n\n  \n\n 19 \n  \n\f  \n\nidentified no evidence that would support such a finding. Nor does the record \n\notherwise demonstrate that the condition was reasonably related to Eaglin’s criminal \n\nhistory or the other sentencing factors of factors set forth in 18 U.S.C. § 3553(a). \n\n In requesting the imposition of such a condition, the government cited our recent \n\nnonprecedential decision in United States v. Springer, 684 F. App’x 37 (2d Cir. 2017) \n\n(summary order), where we upheld an adult pornography ban as a condition of \n\nsupervised release. But there, the record was considerably more robust than here, and \n\nthe district court “made clear the reasons it incorporated the pornography restrictions \n\ninto Springer’s release conditions.” Id. at 40. In addition to Springer’s extensive record \n\nof violating release conditions, the court there considered Springer’s history of sex \n\noffenses involving both children and adults. (Springer had six such convictions, five of \n\nthem involving children and the sixth involving a teenager who was 19 years old). The \n\nDistrict Court also had before it an evaluation submitted by a mental health provider \n\nexplicitly “recommending that Springer be prohibited from accessing any pornographic \n\nmaterials.” Id.  \n\n Some comments made by the District Court here appear to reflect a worry that \n\nEaglin might one day view or possess child pornography. See, e.g., App. 73‐74 (“I’m \n\naware it’s not child pornography at this point that is being viewed but [Internet access \n\nand pornography] appear to be significant risk factors to you[.]”). But, if that was the \n\nreason for the ban, the court did little to explain on the record the source of that \n\nconsternation. The government has not directed us to record evidence suggesting that \n\nEaglin has a history of viewing child pornography or that he has expressed a desire to \n\ndo so such that the public needs to be protected from this potential future crime. The \n\n  \n\n 20 \n  \n\f  \n\nconnection to children that Eaglin’s criminal record evinces is found only in the \n\nstatutory convictions for his sexual relationships with two teenage girls fifteen years \n\nago when he was twenty‐one and twenty‐two years old. We do not minimize the \n\ngravity of those statutory crimes. But the record reflects no finding as to Eaglin’s mens \n\nrea with respect to those offenses, and neither involved child pornography. And the \n\nrecord of any sexual involvement by him with children in the past fifteen years is blank, \n\nso far as we can see. \n\n Before imposing a special condition such as this ban on adult pornography, a \n\ndistrict court must make factual findings supporting its view that the condition is \n\ndesigned to address a realistic danger and that the deprivation the condition creates is \n\nno greater than reasonably necessary to serve the sentencing factors. See Myers, 426 F.3d \n\nat 128. Here, the record does not suggest that Eaglin is likely to seek out child \n\npornography, so we are unable to count that risk as a legitimate basis for this condition.  \n\n And even if the District Court had found that Eaglin presented some risk of \n\nseeking to obtain and possess child pornography, it would still need to support its \n\nblanket ban on his accessing adult pornography by reference to the relevant statutory \n\nfactors. Here, the District Court erroneously treated the possession of adult \n\npornography as reprehensible in itself, rather than as an otherwise lawful action that \n\nviolated Eaglin’s conditions of supervised release. Imposing a wholesale ban on \n\naccessing adult pornography might be justified where the offense of conviction \n\ninvolved the creation of adult pornography with unconsenting victims, see, e.g., \n\nSimmons, 343 F.3d at 82, or where a mental health professional testified that viewing \n\npornography would be detrimental to the defendant’s rehabilitation, see, e.g., Springer, \n\n  \n\n 21 \n  \n\f  \n\n684 F. App’x at 40. In line with the decisions of many other courts, however, we \n\nconclude that a blanket ban on possessing or accessing adult pornography cannot be \n\nimposed unless such a ban on adult pornography is reasonably related to the sentencing \n\nfactors and reasonably necessary to accomplish the goals of sentencing.  \n\n Finally, the record provides inadequate support for the proposition that a \n\ndecade‐long deprivation of access to constitutionally permissible material is reasonably \n\nnecessary to protect the public or meet the other sentencing goals of 18 U.S.C. § 3553(a). \n\nIn finding an adult pornography ban to be more restrictive than necessary to achieve \n\nthe goals of sentencing where there is little indication that access to such material will \n\nimpede a defendant’s rehabilitation or put the community at risk, we have company. \n\nSee United States v. Taylor, 796 F.3d 788, 793 (7th Cir. 2015) (“It is true that both Taylor’s \n\ncrime and adult pornography have to do with sexual activity. But there is no evidence \n\nthat viewing or listening to adult pornography in any way led Taylor to commit the \n\ncrime here, or has led him to commit any other crime, nor is there any evidence in the \n\nrecord that viewing or listening to adult pornography would make the repeat of \n\nTaylor’s crime or similar crimes any more likely.”); United States v. Salazar, 743 F.3d 445, \n\n452 (5th Cir. 2014) (“It is hard to imagine how preventing Salazar from accessing \n\nsexually stimulating materials would prevent future criminal conduct when there is no \n\nindication in the record that Salazar has an unhealthy relationship with such materials \n\nor that such materials contributed to his underlying crimes or other violations.”); United \n\nStates v. Perazza‐Mercado, 553 F.3d 65, 76 (1st Cir. 2009) (“If the district court believed \n\nthat there was some relationship between the defendant’s possession and use of adult \n\npornography and the likelihood that he would engage in sexual misconduct involving \n\n\n  \n\n 22 \n  \n\f  \n\nyoung girls, the court should have explained the basis for that conclusion.”); United \n\nStates v. Voelker, 489 F.3d 139, 152‐53 (3d Cir. 2007) (“[N]othing on this record suggests \n\nthat sexually explicit material involving only adults contributed in any way to Voelker’s \n\noffense, nor is there any reason to believe that viewing such material would cause \n\nVoelker to reoffend”). \n\n In sum, on this record, we can discern no reasonable relation between Eaglin’s \n\nunderlying offense of failure to register, his criminal history (including his fifteen‐year \n\nold statutory rape crimes), his likelihood of recidivism, or need for rehabilitative \n\nservice, on the one hand, and the District Court’s wholesale restriction of his possession \n\nof legal adult pornography, on the other. Nor have we been directed to any record \n\nevidence suggesting Eaglin’s rehabilitation will be impaired by viewing such \n\npornography. We conclude, therefore, that the District Court’s imposition of this \n\ncondition was substantively unreasonable in that it was not reasonably related to the \n\nsentencing factors and not reasonably necessary to achieve a statutorily recognized \n\nsentencing objective. Accordingly, the condition must be struck. \n\n\n CONCLUSION \n\n We conclude that the special conditions of supervised release banning access to \n\nthe Internet and to adult pornography are substantively unreasonable in the \n\ncircumstances presented here because neither is reasonably related to the relevant \n\nsentencing factors and both involve a greater deprivation of liberty than is reasonably \n\nnecessary to implement the statutory purposes of sentencing. Accordingly, we \n\nREMAND the cause for resentencing consistent with this opinion.  \n\n\n  \n\n 23\n[END_CASE]", "role": "user" } ]
4,580,817
Gupta v. United States
2019-01-11
15-2707(L)
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: KEARSE, WESLEY, and DRONEY, Circuit Judges.", "parties": "", "opinions": [{"author": "the Southern District of New York, Jed S. Rakoff, Judge, denying Guptaʹs motion to", "type": "010combined", "text": "15‐2707(L) \n Gupta v USA \n \n \n 1 UNITED STATES COURT OF APPEALS \n \n 2 FOR THE SECOND CIRCUIT \n \n 3 ‐ ‐ ‐ ‐ ‐ ‐ \n \n 4 August Term, 2018 \n \n 5 (Argued:  November 16, 2016  Decided: January 11, 2019) \n \n 6 Docket Nos. 15‐2707(L), ‐2712(C) \n \n 7\n\n 8 RAJAT K. GUPTA, \n \n 9 Petitioner‐Appellant, \n \n 10 ‐ v. ‐ \n \n 11 UNITED STATES OF AMERICA, \n \n 12 Respondent‐Appellee. \n 13\n\n 14 Before: KEARSE, WESLEY, and DRONEY, Circuit Judges. \n \n 15 Petitioner Rajat K. Gupta, whose 2012 convictions of substantive  and \n \n 16 conspiracy crimes of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff, and \n \n 17 18 U.S.C. § 371, were upheld on appeal in 2014, see United States v. Gupta, 747 F.3d 111 \n\f 1 (2d Cir. 2014), appeals from a 2015 judgment of the United States District Court for \n \n 2 the Southern District of New York, Jed S. Rakoff, Judge, denying Guptaʹs motion to \n \n 3 vacate his convictions pursuant to 28 U.S.C. § 2255 on the ground that the trial courtʹs \n \n 4 instructions to the jury as to the ʺpersonal benefitʺ component of an insider trading \n \n 5 offense were legally invalid in light of this Courtʹs 2014 decision in United States v. \n \n 6 Newman, 773 F.3d 438 (2d Cir. 2014) (ʺNewmanʺ). The district court denied the motion, \n \n 7 concluding principally that Gupta, who had objected to those instructions at trial, \n \n 8 procedurally defaulted his present contention by not pursuing his objection on the \n \n 9 direct appeal from his conviction; that he made no showing that would excuse the \n \n 10 default; and that, in any event, the jury instructions were consistent with Newman, \n \n 11 even  as  interpreted by  Gupta.  See United States v. Gupta, 111 F.Supp.3d 557, 561 \n \n 12 (S.D.N.Y. 2015). On this appeal, Gupta concedes that he procedurally defaulted his \n \n 13 challenge to the trial courtʹs personal benefit instruction; but he contends that the \n \n 14 default should be excused on the grounds of cause and prejudice, or actual innocence, \n \n 15 or inapplicability of the normal default principles in light of the Supreme Courtʹs \n \n 16 decision  in  Montgomery  v.  Louisiana,  136  S.  Ct.  718  (2016).  We  conclude  that  his \n \n 17 contentions lack merit, and we affirm the denial of his motion for relief from the \n \n 18 judgment of conviction. \n\n\n  2\n\f 1 Affirmed. \n \n 2 GARY P. NAFTALIS, New York, New York (David S. \n 3 Frankel, Alan R. Friedman, Robin M. Wilcox,  Elliot \n 4 A.  Smith,  Kramer  Levin  Naftalis  &  Frankel,  New \n 5 York, New York, on the brief), for Petitioner‐Appellant. \n \n 6 DAMIAN WILLIAMS, Assistant United States Attorney, \n 7 New York, New York (Preet Bharara, United States \n 8 Attorney  for  the  Southern  District  of  New York, \n 9 Margaret Garnett, Assistant United States Attorney, \n 10 New York, New York, on the brief), for Respondent‐ \n 11 Appellee. \n \n 12 Per Curiam*: \n \n 13 Petitioner Rajat Gupta, who stands convicted of substantive and \n \n 14 conspiracy crimes of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff, and \n \n 15 18 U.S.C. § 371, see United States v. Gupta, 747  F.3d  111  (2d Cir. 2014) (ʺGupta Iʺ), \n \n 16 appeals from a judgment of the United States District Court for the Southern District \n \n 17 of  New  York,  Jed  S.  Rakoff,  Judge,  which  denied  Guptaʹs  motion  to  vacate  his \n \n 18 convictions pursuant to 28 U.S.C. § 2255 on the ground that the courtʹs instructions \n \n 19 to the jury as to the ʺpersonal benefitʺ component of an insider trading offense were \n \n 20 legally invalid in light of this Courtʹs subsequent decision in United States v. Newman, \n \n \n \n \n\n\n * This decision was originally entered as a summary order on January 7, 2019; the\n summary order is withdrawn.\n\n  3\n\f 1 773  F.3d  438  (2d  Cir. 2014)  (ʺNewmanʺ).  The district court denied the motion, \n \n 2 concluding principally that Gupta, who had objected to those instructions at trial, \n \n 3 procedurally defaulted his present contention by not pursuing his objection on  the \n \n 4 direct appeal from his conviction; that he made no showing that would excuse the \n \n 5 default; and that, in any event, the jury instructions were consistent with Newman, \n \n 6 even as  interpreted by  Gupta.  See United States v. Gupta, 111 F.Supp.3d 557, 561 \n \n 7 (S.D.N.Y. 2015) (ʺGupta IIʺ). \n \n 8 This Court granted Guptaʹs application for a certificate of appealability \n \n 9 on the issues of (1) whether his conviction should be vacated on the ground that the \n \n 10 jury was erroneously instructed, and (2) whether any procedural default of this claim \n \n 11 may be excused on the grounds of (a) cause and prejudice or (b) actual innocence. On \n \n 12 appeal, Gupta concedes that he procedurally defaulted his challenge to the trial \n \n 13 courtʹs personal benefit instruction; but he contends that the default should be \n \n 14 excused on the grounds of cause and prejudice, or actual innocence, or inapplicability \n \n 15 of the normal default principles in light of the Supreme Courtʹs decision in \n \n 16 Montgomery v. Louisiana, 136 S. Ct. 718 (2016).  For the reasons that follow, we see no \n \n 17 error  in  the  decision  of  the  district  court,  and  we  affirm  the  decision  in  Gupta  II \n \n 18 denying Guptaʹs motion for relief from the judgment of conviction. We assume the \n\n\n  4\n\f 1 partiesʹ familiarity with the underlying facts, procedural history, and  issues for \n \n 2 review. \n \n 3 Guptaʹs convictions of engaging in and conspiring to engage in an insider \n \n 4 trading  scheme  were  based  on  evidence  that  on  several  occasions  Gupta,  while \n \n 5 serving on boards of directors of various companies, disclosed material nonpublic \n \n 6 information about those companies to his friend and business associate Raj \n \n 7 Rajaratnam, founder of the Galleon Group (ʺGalleonʺ), a family of hedge funds that \n \n 8 invested billions of dollars for its principals and clients, see Gupta I, 747 F.3d at 116, \n \n 9 121.  In his direct appeal from the judgment of conviction, Gupta  principally \n \n 10 challenged the admission in evidence of certain wiretap evidence and challenged the \n \n 11 exclusion  of  certain  evidence  he  sought  to  introduce.  We  rejected  all  of  Guptaʹs \n \n 12 contentions and affirmed the judgment. See id. at 128‐40. Gupta did not challenge the \n \n 13 sufficiency of the evidence to convict him or any of the instructions to the jury. \n \n 14 After Guptaʹs appeal had been decided, this Court decided Newman, 773 \n \n 15 F.3d at 438, in which we reversed the insider trading convictions of two tippees. \n \n 16 In his present § 2255 motion, Gupta quotes the following parts of the trial \n \n 17 courtʹs instructions to the jury at his trial: \n\n\n\n\n  5\n\f 1 First,  [the  government  must  prove  that]  on  or  about  the  date \n 2 alleged, Mr. Gupta engaged in an insider trading scheme, in that, \n 3 in anticipation of receiving at least some modest benefit in return, he \n 4 provided to Mr. Rajaratnam the material non‐public information \n 5 specified in the count you are considering . . . . \n \n 6 . . . . \n \n 7 [A]s to the benefit that the defendant anticipated receiving, the \n 8 benefit does not need to be financial or to be tangible in nature.  It could \n 9 include, for example, maintaining a good relationship with a frequent \n 10 business partner, or obtaining future financial benefits. \n \n 11 (Gupta brief on appeal at 10 (all emphases and alterations in brief).) He contends that \n \n 12 [t]he  instruction  thus  began  by  emphasizing,  in  a  formulation \n 13 plainly invalid following Newman, that ʺthe benefit does not need \n 14 to be financial or to be tangible in nature.ʺ By way of example, the \n 15 district court continued, ʺmaintaining a good relationshipʺ  with \n 16 Rajaratnam  would  suffice.  The instruction thus permitted, \n 17 consistent with the governmentʹs theory, proof and arguments in \n 18 the case, a guilty verdict based on the relationship, alone, as  the \n 19 benefit. \n \n 20 (Id. at 10‐11 (emphasis in original).) Gupta contends that his convictions should be \n \n 21 vacated on the ground that Newman, ʺ[b]y contrast, . . . held that a personal  benefit \n \n 22 must take the form of an ʹexchangeʹ—a quid pro quo—in which the alleged tipper \n \n 23 receives an ʹobjective, consequential . . . gain of a pecuniary or similarly valuable \n \n 24 nature,ʹ or at least the opportunity for such gain.ʺ (Id. at 11 (quoting Newman, 773 \n \n 25 F.3d at 452)). We disagree. \n\n\n  6\n\f 1 ʺ[A] collateral challenge may not do service for an appeal.ʺ United States \n \n 2 v. Frady, 456 U.S. 152, 165 (1982). ʺWhere a defendant has procedurally defaulted a \n \n 3 claim by failing to raise it on direct review, the claim may be raised in habeas only if \n \n 4 the defendant can first demonstrate either ʹcauseʹ and actual ʹprejudice,ʹ Murray v. \n \n 5 Carrier, 477 U.S. 478, 485 (1986); Wainwright v. Sykes, 433 U.S. 72, 87 (1977), or that he \n \n 6 is ʹactually innocent,ʹ Murray, supra, at 496; Smith v. Murray, 477 U.S. 527, 537 (1986).ʺ \n \n 7 Bousley v. United States, 523 U.S. 614, 622 (1998).  In order to demonstrate cause, a \n \n 8 defendant  must  show  ʺsome  objective  factor  external  to  the  defense,ʺ  Murray  v. \n \n 9 Carrier, 477 U.S. 478, 488 (1986), such that the claim was ʺso novel that its legal basis \n \n 10 [was] not reasonably available to counsel,ʺ Reed v. Ross, 468 U.S. 1, 16 (1984). Novelty, \n \n 11 or futility, however, ʺcannot constitute cause if it  means  simply that a claim was \n \n 12 unacceptable to that particular court at that particular time.ʺ  Bousley, 523 U.S. at 623 \n \n 13 (internal quotation marks omitted).  ʺ[T]he question is not whether subsequent legal \n \n 14 developments have made counselʹs task easier, but whether at the time of the default \n \n 15 the claim was ʹavailableʹ at all.ʺ  United States v. Thorn, 659 F.3d 227, 233 (2d Cir. 2011) \n \n 16 (quoting Smith v. Murray, 477 U.S. 527, 537 (1986)).  ʺ[T]he mere fact that counsel \n \n 17 failed to recognize the factual or legal basis for a claim, or failed to raise the claim despite \n \n 18 recognizing it, does not constitute cause for a procedural default.ʺ Murray v. Carrier, \n\n  7\n\f 1 477 U.S. at 486 (emphasis added). \n \n 2 Further, in order to meet the cause‐and‐prejudice standard, the prejudice \n \n 3 that must be shown is ʺnot merely whether ʹthe instruction is undesirable, erroneous, \n \n 4 or even universally condemned,ʹʺ but rather ʺʹwhether the ailing instruction by itself \n \n 5 so infected the entire trial that the resulting conviction violates due process,ʹʺ  Frady, \n \n 6 456 U.S. at 169 (quoting Henderson v. Kibbe, 431 U.S. 145, 154 (1977)); see Frady, 456 U.S. \n \n 7 at 166 (ʺThe burden of demonstrating that an erroneous instruction was so prejudicial \n \n 8 that it will support a collateral attack on the constitutional validity of a state courtʹs \n \n 9 judgment is even greater than the showing required to establish plain error on direct \n \n 10 appeal.ʺ  (internal  quotation  marks  and  emphasis  omitted)).  And  in  order  to \n \n 11 demonstrate his actual innocence, a defendant must prove his ʺfactual innocence, not \n \n 12 mere legal insufficiency,ʺ and ʺdemonstrate that, ʹin light of all the evidence,ʹ ʹit is \n \n 13 more likely than not that no reasonable juror would have convicted him.ʹʺ  Bousley, \n \n 14 523 U.S. at 623 (quoting Schlup v. Delo, 513 U.S. 298, 327‐28 (1995)).  Gupta has made \n \n 15 none of the requisite showings. \n\n\n\n\n  8\n\f 1 No ʺCauseʺ \n \n 2 As to cause, we recently noted in Whitman v. United States, No. 15‐2686, \n \n 3 2018  WL  5828118  (2d  Cir.  Nov.  7,  2018)  (summary  order)  (ʺWhitmanʺ)—another \n \n 4 insider  trading  case  in  which  the  direct  appeal  was  decided  shortly  before  our \n \n 5 decision in Newman—that the defendant had objected at trial to the courtʹs personal \n \n 6 benefit instruction but did not pursue that objection on appeal. We noted that the \n \n 7 same objection had been pressed by defendants in other cases prior to our decision \n \n 8 in  Newman.  We  concluded  that  Whitman  did  not  show  cause  for  his  failure  to \n \n 9 challenge the personal benefit instructions on appeal: ʺIf other counsel were able to \n \n 10 raise the argument, including Whitmanʹs own former attorney, we cannot say the \n \n 11 same argument was unavailable to his appellate counsel.ʺ Whitman, 2018 WL 5828118 \n \n 12 at *2. \n \n 13 Although Whitman was decided by nonprecedential summary order, the \n \n 14 fact that we ʺ[d]eny[]  summary orders precedential effect  does not mean that   the \n \n 15 court considers itself free to rule differently in similar cases,ʺ Order dated  June 26, \n \n 16 2007, adopting 2d Cir. Local R. 32.1.1, and we see no basis for any different outcome \n \n 17 here. Defendants in other insider trading prosecutions were contending that juries \n \n 18 should be given narrower definitions of the personal benefit needed to find culpable \n\n\n  9\n\f 1 insider trading.  Gupta at his trial objected to the instructions he challenges now.  We \n \n 2 conclude that he presents no viable claim that the personal benefit challenge was \n \n 3 unavailable to his counsel on appeal. \n \n \n \n 4 No ʺPrejudiceʺ \n \n 5 Nor has Gupta shown prejudice—i.e., that the personal benefit \n \n 6 instructions he challenges were so flawed as to deny him due process.  First of all, we \n \n 7 assess the targeted portion of the district courtʹs instructions in context.  ʺAs [the \n \n 8 Supreme Court] ha[s] often emphasized:  ʹ[A] single instruction to a jury may not be \n \n 9 judged in artificial isolation, but must be viewed in the context of the overall charge.ʹʺ \n \n 10 Frady,  456  U.S.  at  169  (quoting  Cupp  v.  Naughten,  414  U.S.  141,  146‐47  (1973)). \n \n 11 Although Gupta argues that it was error for the trial judge to indicate that it would \n \n 12 suffice  to  establish  a  personal  benefit  if  Guptaʹs  purpose  had  been  simply \n \n 13 ʺʹmaintaining a good relationshipʹʺ (Gupta brief on appeal at 10 (quoting Tr. 3371)), \n \n 14 the courtʹs actual relationship language (included in Guptaʹs quote but omitted from \n \n 15 his argument) was ʺmaintaining a good relationship with a frequent business partnerʺ \n \n 16 (Tr. 3371 (emphasis added)). \n\n\n\n\n  10\n\f 1 Second, the trial courtʹs reference to a good relationship with a frequent \n \n 2 business partner was consistent with the Supreme Courtʹs discussion in Dirks v. SEC, \n \n 3 463 U.S. 646 (1983), as to what may properly be considered a tipperʹs anticipated \n \n 4 personal benefit sufficient to warrant his conviction of insider trading. In Dirks, \n \n 5 noting that ʺa purpose of the securities laws was to eliminate use of inside \n \n 6 information for personal advantage,ʺ id. at 662 (internal quotation marks omitted), the \n \n 7 Court stated that the test for whether that purpose has been contravened is ʺwhether \n \n 8 the insider receives a direct or indirect personal benefit from the disclosure, such as \n \n 9 a pecuniary gain or a reputational benefit that will translate into future earnings.ʺ  Id. \n \n 10 at 663.  The Court also stated that an inference of such a benefit may be warranted by \n \n 11 the circumstance of ʺa relationship between the insider and the recipient that suggests \n \n 12 a quid pro quo from the latter, or an intention to benefit the particular recipient.ʺ Id. \n \n 13 at 664.  Where the recipient of the tip is the tipperʹs ʺfrequentʺ ʺbusinessʺ partner, the \n \n 14 tipperʹs anticipation of a quid pro quo is easily inferable. \n \n 15 Third, the Dirks Courtʹs use of the above  disjunctives (i.e., ʺsuch as a \n \n 16 pecuniary gain or a reputational benefit that will translate into future earnings,ʺ id. \n \n 17 at 663, and ʺa quid pro quo from the [recipient] or an intention to benefit the particular \n \n 18 recipient,ʺ id.  at 664)—especially prefaced by ʺsuch asʺ—suggests varying sets of \n\n\n  11\n\f 1 circumstances each of which would warrant a finding of the tipperʹs illegal purpose. \n \n 2 Thus, while Gupta argues that the instruction at his trial was ʺinvalidʺ under Newman \n \n 3 for stating that ʺʹthe benefit does not need to be financial or to be tangibleʹʺ  (Gupta \n \n 4 brief on appeal at 10), that instruction was warranted by Dirks. Indeed, the lack  of \n \n 5 need for proof of the tipperʹs financial or tangible gain was highlighted as well by the \n \n 6 Dirks Courtʹs illustration that \n \n 7 [t]he  elements  of  fiduciary  duty  and  exploitation  of  nonpublic \n 8 information also exist when an insider makes a gift of confidential \n 9 information  to  a  trading  relative  or  friend.  The tip and trade \n 10 resemble trading by the insider himself followed by a gift of the \n 11 profits to the recipient. \n \n 12 463 U.S. at 664; see also United States v. Martoma, 894 F.3d 64, 75 (2d Cir. 2018)  (ʺThe \n \n 13 tipperʹs intention to benefit the tippee proves a breach of fiduciary duty because it \n \n 14 demonstrates that the tipper improperly used inside information for personal ends \n \n 15 and thus lacked a legitimate corporate purpose.ʺ). \n \n 16 Finally, the trial courtʹs instruction that the benefit to Gupta need not \n \n 17 have  been  financial  or  tangible,  although  contrary  to  the  formulation  given  in \n \n 18 Newman, could not have constituted prejudice to Gupta because it was correct. The \n \n 19 Newman formulation was expressly rejected by the Supreme Court in Salman v. United \n \n 20 States, 137 S. Ct. 420 (2016), as that Court noted that \n\n\n  12\n\f 1 [t]o the extent the Second Circuit held that the tipper must also \n 2 receive something of a ʺpecuniary or similarly valuable natureʺ in \n 3 exchange for a gift to family or friends, Newman, 773 F.3d, at 452, \n 4 . . . this requirement is inconsistent with Dirks. \n \n 5 137 S. Ct. at 428. Thus, in the wake of Salman, we have stated that ʺit is settled  law \n \n 6 that personal benefits may be indirect and intangible and need not be pecuniary at \n \n 7 all.ʺ United States v. Martoma, 894 F.3d at 75. \n \n 8 The fact that Newmanʹs requirement for proof of a tipperʹs pecuniary or \n \n 9 other  tangible  gain  has  been  rejected  by  the  Supreme  Court  disposes  of  Guptaʹs \n \n 10 contention—invoking Montgomery v. Louisiana, 136 S. Ct. 718, a case that involved \n \n 11 principles   of   retroactivity   and   that  did not address issues of cause and \n \n 12 prejudice—that Newman meant the trial courtʹs instruction that proof of pecuniary or \n \n 13 tangible benefit was not necessary caused him to be convicted of a crime for ʺconduct \n \n 14 that is not criminalʺ (Gupta brief on appeal at 22). \n \n \n \n 15 No Innocence \n \n 16 Lastly, as to the claim of actual innocence, Gupta has not ʺdemonstrate[d] \n \n 17 that, ʹin light of all the evidence,ʹ ʹit is more likely than not that no reasonable juror \n \n 18 would have convicted him,ʹʺ Bousley, 523 U.S. at 623 (quoting Schlup v. Delo, 513 U.S. \n\n\n\n  13\n\f 1 at 327‐28 (emphasis ours)), of insider trading.  As a matter of background, the record \n \n 2 as a whole, viewed in the light most favorable to the government, contained ample \n \n 3 evidence that Gupta and Rajaratnam were business associates. Gupta had invested \n \n 4 several million dollars in Galleon funds.  In 2005, Gupta and Rajaratnam invested in \n \n 5 another investment fund capitalized with $50 million; Gupta originally contributed \n \n 6 $5 million; he later doubled his investment with $5 million loaned to him by \n \n 7 Rajaratnam.  In  early  2008,  Gupta  was  made  chairman  of  Galleon  International, \n \n 8 which, as of April 2008, managed assets totaling some $1.1 billion and could earn \n \n 9 performance fees; Gupta was given a 15 percent ownership stake in that fund. Gupta \n \n 10 also regularly worked on Galleonʹs behalf in seeking potential investors; he had a \n \n 11 keycard allowing him access to Galleonʹs New York offices. See Gupta I, 747 F.3d at \n \n 12 116‐21. Gupta described Rajaratnam as a very close friend. Rajaratnamʹs address \n \n 13 book noted Gupta as a good friend; and Gupta was one of five persons whose call \n \n 14 Rajaratnamʹs secretary was authorized to put through if he called near the end of the \n \n 15 trading day. See id. at 121. \n \n 16 The jury was instructed that in order to convict Gupta on any given \n \n 17 count, it must find, inter alia, that ʺGupta anticipated that Mr. Rajaratnam or others \n \n 18 at Galleon would trade on the basis of th[e non‐public] informationʺ provided by \n\n\n  14\n\f 1 Gupta, that ʺthey then did so by buying or selling the shares specified in the count on \n \n 2 the basis of the inside information,ʺ and that ʺGupta, in return for providing this \n \n 3 information, anticipated receiving some personal benefit.ʺ (Tr. 3371.) There  was \n \n 4 ample evidence to permit the jury to find that Gupta intended Rajaratnam to trade on \n \n 5 the  basis  of  the  confidential  information  Gupta  passed  to  him  and  that  Gupta \n \n 6 personally benefitted in one of the ways envisioned in Dirks. \n \n 7 For example, on September 23, 2008, Gupta, a member of the board  of \n \n 8 directors  of  The  Goldman  Sachs  Group,  Inc.  (ʺGoldman  Sachsʺ  or  ʺGoldmanʺ), \n \n 9 participated in a Goldman board meeting via telephone and learned that Warren \n \n 10 Buffett was about to invest $5 billion in Goldman, which would be publicly \n \n 11 announced at 6 p.m. that day.  At 3:54 p.m.—one minute after the end of that board‐ \n \n 12 meeting telephone call—Gupta called Rajaratnam, telling Rajaratnamʹs secretary that \n \n 13 the  call was  urgent.  Gupta and Rajaratnam spoke briefly, and Rajaratnam then \n \n 14 immediately began having his people at Galleon buy Goldman shares.  Between 3:56 \n \n 15 p.m. and the 4:00 p.m. close of the market, they bought Goldman shares costing a \n \n 16 total of more than $33 million. The next morning, the price of the stock rose some \n \n 17 seven  percent.  See  Gupta  I,  747  F.3d at  117‐19.  The timing of Guptaʹs call to \n \n 18 Rajaratnam immediately after the end of his board call, and his statement at 3:54 p.m \n\n\n  15\n\f 1 that he needed to speak to Rajaratnam urgently, plainly allowed the inference  that \n \n 2 Gupta intended Rajaratnam to buy, and profit on, Goldman shares in advance of the \n \n 3 Buffett $5 billion announcement at 6 p.m. \n \n 4 Similarly, on October 23, 2008, Gupta learned in a Goldman Sachs board‐ \n \n 5 of‐directors  conference  call  that  Goldman  would  report  in  December  a  quarterly \n \n 6 financial loss.  The loss would be its first in its history as a public  company, and \n \n 7 market analysts were predicting another profitable quarter. One minute after the end \n \n 8 of that board  conference  call, Gupta   called  Rajaratnam.  The next morning, one \n \n 9 minute after the stock market opened, Rajaratnam began selling Goldman shares. In \n \n 10 little  over  an  hour,  Rajaratnam  sold  enough  shares  to  avoid  a  loss  of  more  than \n \n 11 $3.8  million.  Rajaratnam  also  advised  a  portfolio  manager  of  Galleon \n \n 12 International—which had in the past invested in Goldman stock, and in which Gupta \n \n 13 had a 15 percent ownership stake—that on the previous day Rajaratnam had received \n \n 14 confidential information from a Goldman board member, negative news that would \n \n 15 not be reported publicly until December. Rajaratnam said he himself would  make \n \n 16 short sales of Goldman stock. See Gupta I, 747 F.3d at 118‐21. On this evidence and \n \n 17 the record as a whole, the jury could rationally have found that Gupta anticipated \n \n 18 that Rajaratnam would engage in trading of Goldman shares that would benefit \n\n\n  16\n\f 1 Gupta financially. \n \n \n \n 2 Conclusion \n \n \n \n 3 We have considered all of Guptaʹs arguments on this appeal and have \n \n 4 found them to be without merit. The judgment of the district court is affirmed. \n\n\n\n\n  17", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358070/", "author_raw": "the Southern District of New York, Jed S. Rakoff, Judge, denying Guptaʹs motion to"}]}
KEARSE
WESLEY
DRONEY
1
{"KEARSE": ", Circuit", "WESLEY": ", Circuit", "DRONEY": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580817/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Gupta v. United States\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-11\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n15‐2707(L) \n Gupta v USA \n \n \n 1 UNITED STATES COURT OF APPEALS \n \n 2 FOR THE SECOND CIRCUIT \n \n 3 ‐ ‐ ‐ ‐ ‐ ‐ \n \n 4 August Term, 2018 \n \n 5 (Argued:  November 16, 2016  Decided: January 11, 2019) \n \n 6 Docket Nos. 15‐2707(L), ‐2712(C) \n \n 7\n\n 8 RAJAT K. GUPTA, \n \n 9 Petitioner‐Appellant, \n \n 10 ‐ v. ‐ \n \n 11 UNITED STATES OF AMERICA, \n \n 12 Respondent‐Appellee. \n 13\n\n 14 Before: KEARSE, WESLEY, and DRONEY, Circuit Judges. \n \n 15 Petitioner Rajat K. Gupta, whose 2012 convictions of substantive  and \n \n 16 conspiracy crimes of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff, and \n \n 17 18 U.S.C. § 371, were upheld on appeal in 2014, see United States v. Gupta, 747 F.3d 111 \n\f 1 (2d Cir. 2014), appeals from a 2015 judgment of the United States District Court for \n \n 2 the Southern District of New York, Jed S. Rakoff, Judge, denying Guptaʹs motion to \n \n 3 vacate his convictions pursuant to 28 U.S.C. § 2255 on the ground that the trial courtʹs \n \n 4 instructions to the jury as to the ʺpersonal benefitʺ component of an insider trading \n \n 5 offense were legally invalid in light of this Courtʹs 2014 decision in United States v. \n \n 6 Newman, 773 F.3d 438 (2d Cir. 2014) (ʺNewmanʺ). The district court denied the motion, \n \n 7 concluding principally that Gupta, who had objected to those instructions at trial, \n \n 8 procedurally defaulted his present contention by not pursuing his objection on the \n \n 9 direct appeal from his conviction; that he made no showing that would excuse the \n \n 10 default; and that, in any event, the jury instructions were consistent with Newman, \n \n 11 even  as  interpreted by  Gupta.  See United States v. Gupta, 111 F.Supp.3d 557, 561 \n \n 12 (S.D.N.Y. 2015). On this appeal, Gupta concedes that he procedurally defaulted his \n \n 13 challenge to the trial courtʹs personal benefit instruction; but he contends that the \n \n 14 default should be excused on the grounds of cause and prejudice, or actual innocence, \n \n 15 or inapplicability of the normal default principles in light of the Supreme Courtʹs \n \n 16 decision  in  Montgomery  v.  Louisiana,  136  S.  Ct.  718  (2016).  We  conclude  that  his \n \n 17 contentions lack merit, and we affirm the denial of his motion for relief from the \n \n 18 judgment of conviction. \n\n\n  2\n\f 1 Affirmed. \n \n 2 GARY P. NAFTALIS, New York, New York (David S. \n 3 Frankel, Alan R. Friedman, Robin M. Wilcox,  Elliot \n 4 A.  Smith,  Kramer  Levin  Naftalis  &  Frankel,  New \n 5 York, New York, on the brief), for Petitioner‐Appellant. \n \n 6 DAMIAN WILLIAMS, Assistant United States Attorney, \n 7 New York, New York (Preet Bharara, United States \n 8 Attorney  for  the  Southern  District  of  New York, \n 9 Margaret Garnett, Assistant United States Attorney, \n 10 New York, New York, on the brief), for Respondent‐ \n 11 Appellee. \n \n 12 Per Curiam*: \n \n 13 Petitioner Rajat Gupta, who stands convicted of substantive and \n \n 14 conspiracy crimes of securities fraud, in violation of 15 U.S.C. §§ 78j(b) and 78ff, and \n \n 15 18 U.S.C. § 371, see United States v. Gupta, 747  F.3d  111  (2d Cir. 2014) (ʺGupta Iʺ), \n \n 16 appeals from a judgment of the United States District Court for the Southern District \n \n 17 of  New  York,  Jed  S.  Rakoff,  Judge,  which  denied  Guptaʹs  motion  to  vacate  his \n \n 18 convictions pursuant to 28 U.S.C. § 2255 on the ground that the courtʹs instructions \n \n 19 to the jury as to the ʺpersonal benefitʺ component of an insider trading offense were \n \n 20 legally invalid in light of this Courtʹs subsequent decision in United States v. Newman, \n \n \n \n \n\n\n * This decision was originally entered as a summary order on January 7, 2019; the\n summary order is withdrawn.\n\n  3\n\f 1 773  F.3d  438  (2d  Cir. 2014)  (ʺNewmanʺ).  The district court denied the motion, \n \n 2 concluding principally that Gupta, who had objected to those instructions at trial, \n \n 3 procedurally defaulted his present contention by not pursuing his objection on  the \n \n 4 direct appeal from his conviction; that he made no showing that would excuse the \n \n 5 default; and that, in any event, the jury instructions were consistent with Newman, \n \n 6 even as  interpreted by  Gupta.  See United States v. Gupta, 111 F.Supp.3d 557, 561 \n \n 7 (S.D.N.Y. 2015) (ʺGupta IIʺ). \n \n 8 This Court granted Guptaʹs application for a certificate of appealability \n \n 9 on the issues of (1) whether his conviction should be vacated on the ground that the \n \n 10 jury was erroneously instructed, and (2) whether any procedural default of this claim \n \n 11 may be excused on the grounds of (a) cause and prejudice or (b) actual innocence. On \n \n 12 appeal, Gupta concedes that he procedurally defaulted his challenge to the trial \n \n 13 courtʹs personal benefit instruction; but he contends that the default should be \n \n 14 excused on the grounds of cause and prejudice, or actual innocence, or inapplicability \n \n 15 of the normal default principles in light of the Supreme Courtʹs decision in \n \n 16 Montgomery v. Louisiana, 136 S. Ct. 718 (2016).  For the reasons that follow, we see no \n \n 17 error  in  the  decision  of  the  district  court,  and  we  affirm  the  decision  in  Gupta  II \n \n 18 denying Guptaʹs motion for relief from the judgment of conviction. We assume the \n\n\n  4\n\f 1 partiesʹ familiarity with the underlying facts, procedural history, and  issues for \n \n 2 review. \n \n 3 Guptaʹs convictions of engaging in and conspiring to engage in an insider \n \n 4 trading  scheme  were  based  on  evidence  that  on  several  occasions  Gupta,  while \n \n 5 serving on boards of directors of various companies, disclosed material nonpublic \n \n 6 information about those companies to his friend and business associate Raj \n \n 7 Rajaratnam, founder of the Galleon Group (ʺGalleonʺ), a family of hedge funds that \n \n 8 invested billions of dollars for its principals and clients, see Gupta I, 747 F.3d at 116, \n \n 9 121.  In his direct appeal from the judgment of conviction, Gupta  principally \n \n 10 challenged the admission in evidence of certain wiretap evidence and challenged the \n \n 11 exclusion  of  certain  evidence  he  sought  to  introduce.  We  rejected  all  of  Guptaʹs \n \n 12 contentions and affirmed the judgment. See id. at 128‐40. Gupta did not challenge the \n \n 13 sufficiency of the evidence to convict him or any of the instructions to the jury. \n \n 14 After Guptaʹs appeal had been decided, this Court decided Newman, 773 \n \n 15 F.3d at 438, in which we reversed the insider trading convictions of two tippees. \n \n 16 In his present § 2255 motion, Gupta quotes the following parts of the trial \n \n 17 courtʹs instructions to the jury at his trial: \n\n\n\n\n  5\n\f 1 First,  [the  government  must  prove  that]  on  or  about  the  date \n 2 alleged, Mr. Gupta engaged in an insider trading scheme, in that, \n 3 in anticipation of receiving at least some modest benefit in return, he \n 4 provided to Mr. Rajaratnam the material non‐public information \n 5 specified in the count you are considering . . . . \n \n 6 . . . . \n \n 7 [A]s to the benefit that the defendant anticipated receiving, the \n 8 benefit does not need to be financial or to be tangible in nature.  It could \n 9 include, for example, maintaining a good relationship with a frequent \n 10 business partner, or obtaining future financial benefits. \n \n 11 (Gupta brief on appeal at 10 (all emphases and alterations in brief).) He contends that \n \n 12 [t]he  instruction  thus  began  by  emphasizing,  in  a  formulation \n 13 plainly invalid following Newman, that ʺthe benefit does not need \n 14 to be financial or to be tangible in nature.ʺ By way of example, the \n 15 district court continued, ʺmaintaining a good relationshipʺ  with \n 16 Rajaratnam  would  suffice.  The instruction thus permitted, \n 17 consistent with the governmentʹs theory, proof and arguments in \n 18 the case, a guilty verdict based on the relationship, alone, as  the \n 19 benefit. \n \n 20 (Id. at 10‐11 (emphasis in original).) Gupta contends that his convictions should be \n \n 21 vacated on the ground that Newman, ʺ[b]y contrast, . . . held that a personal  benefit \n \n 22 must take the form of an ʹexchangeʹ—a quid pro quo—in which the alleged tipper \n \n 23 receives an ʹobjective, consequential . . . gain of a pecuniary or similarly valuable \n \n 24 nature,ʹ or at least the opportunity for such gain.ʺ (Id. at 11 (quoting Newman, 773 \n \n 25 F.3d at 452)). We disagree. \n\n\n  6\n\f 1 ʺ[A] collateral challenge may not do service for an appeal.ʺ United States \n \n 2 v. Frady, 456 U.S. 152, 165 (1982). ʺWhere a defendant has procedurally defaulted a \n \n 3 claim by failing to raise it on direct review, the claim may be raised in habeas only if \n \n 4 the defendant can first demonstrate either ʹcauseʹ and actual ʹprejudice,ʹ Murray v. \n \n 5 Carrier, 477 U.S. 478, 485 (1986); Wainwright v. Sykes, 433 U.S. 72, 87 (1977), or that he \n \n 6 is ʹactually innocent,ʹ Murray, supra, at 496; Smith v. Murray, 477 U.S. 527, 537 (1986).ʺ \n \n 7 Bousley v. United States, 523 U.S. 614, 622 (1998).  In order to demonstrate cause, a \n \n 8 defendant  must  show  ʺsome  objective  factor  external  to  the  defense,ʺ  Murray  v. \n \n 9 Carrier, 477 U.S. 478, 488 (1986), such that the claim was ʺso novel that its legal basis \n \n 10 [was] not reasonably available to counsel,ʺ Reed v. Ross, 468 U.S. 1, 16 (1984). Novelty, \n \n 11 or futility, however, ʺcannot constitute cause if it  means  simply that a claim was \n \n 12 unacceptable to that particular court at that particular time.ʺ  Bousley, 523 U.S. at 623 \n \n 13 (internal quotation marks omitted).  ʺ[T]he question is not whether subsequent legal \n \n 14 developments have made counselʹs task easier, but whether at the time of the default \n \n 15 the claim was ʹavailableʹ at all.ʺ  United States v. Thorn, 659 F.3d 227, 233 (2d Cir. 2011) \n \n 16 (quoting Smith v. Murray, 477 U.S. 527, 537 (1986)).  ʺ[T]he mere fact that counsel \n \n 17 failed to recognize the factual or legal basis for a claim, or failed to raise the claim despite \n \n 18 recognizing it, does not constitute cause for a procedural default.ʺ Murray v. Carrier, \n\n  7\n\f 1 477 U.S. at 486 (emphasis added). \n \n 2 Further, in order to meet the cause‐and‐prejudice standard, the prejudice \n \n 3 that must be shown is ʺnot merely whether ʹthe instruction is undesirable, erroneous, \n \n 4 or even universally condemned,ʹʺ but rather ʺʹwhether the ailing instruction by itself \n \n 5 so infected the entire trial that the resulting conviction violates due process,ʹʺ  Frady, \n \n 6 456 U.S. at 169 (quoting Henderson v. Kibbe, 431 U.S. 145, 154 (1977)); see Frady, 456 U.S. \n \n 7 at 166 (ʺThe burden of demonstrating that an erroneous instruction was so prejudicial \n \n 8 that it will support a collateral attack on the constitutional validity of a state courtʹs \n \n 9 judgment is even greater than the showing required to establish plain error on direct \n \n 10 appeal.ʺ  (internal  quotation  marks  and  emphasis  omitted)).  And  in  order  to \n \n 11 demonstrate his actual innocence, a defendant must prove his ʺfactual innocence, not \n \n 12 mere legal insufficiency,ʺ and ʺdemonstrate that, ʹin light of all the evidence,ʹ ʹit is \n \n 13 more likely than not that no reasonable juror would have convicted him.ʹʺ  Bousley, \n \n 14 523 U.S. at 623 (quoting Schlup v. Delo, 513 U.S. 298, 327‐28 (1995)).  Gupta has made \n \n 15 none of the requisite showings. \n\n\n\n\n  8\n\f 1 No ʺCauseʺ \n \n 2 As to cause, we recently noted in Whitman v. United States, No. 15‐2686, \n \n 3 2018  WL  5828118  (2d  Cir.  Nov.  7,  2018)  (summary  order)  (ʺWhitmanʺ)—another \n \n 4 insider  trading  case  in  which  the  direct  appeal  was  decided  shortly  before  our \n \n 5 decision in Newman—that the defendant had objected at trial to the courtʹs personal \n \n 6 benefit instruction but did not pursue that objection on appeal. We noted that the \n \n 7 same objection had been pressed by defendants in other cases prior to our decision \n \n 8 in  Newman.  We  concluded  that  Whitman  did  not  show  cause  for  his  failure  to \n \n 9 challenge the personal benefit instructions on appeal: ʺIf other counsel were able to \n \n 10 raise the argument, including Whitmanʹs own former attorney, we cannot say the \n \n 11 same argument was unavailable to his appellate counsel.ʺ Whitman, 2018 WL 5828118 \n \n 12 at *2. \n \n 13 Although Whitman was decided by nonprecedential summary order, the \n \n 14 fact that we ʺ[d]eny[]  summary orders precedential effect  does not mean that   the \n \n 15 court considers itself free to rule differently in similar cases,ʺ Order dated  June 26, \n \n 16 2007, adopting 2d Cir. Local R. 32.1.1, and we see no basis for any different outcome \n \n 17 here. Defendants in other insider trading prosecutions were contending that juries \n \n 18 should be given narrower definitions of the personal benefit needed to find culpable \n\n\n  9\n\f 1 insider trading.  Gupta at his trial objected to the instructions he challenges now.  We \n \n 2 conclude that he presents no viable claim that the personal benefit challenge was \n \n 3 unavailable to his counsel on appeal. \n \n \n \n 4 No ʺPrejudiceʺ \n \n 5 Nor has Gupta shown prejudice—i.e., that the personal benefit \n \n 6 instructions he challenges were so flawed as to deny him due process.  First of all, we \n \n 7 assess the targeted portion of the district courtʹs instructions in context.  ʺAs [the \n \n 8 Supreme Court] ha[s] often emphasized:  ʹ[A] single instruction to a jury may not be \n \n 9 judged in artificial isolation, but must be viewed in the context of the overall charge.ʹʺ \n \n 10 Frady,  456  U.S.  at  169  (quoting  Cupp  v.  Naughten,  414  U.S.  141,  146‐47  (1973)). \n \n 11 Although Gupta argues that it was error for the trial judge to indicate that it would \n \n 12 suffice  to  establish  a  personal  benefit  if  Guptaʹs  purpose  had  been  simply \n \n 13 ʺʹmaintaining a good relationshipʹʺ (Gupta brief on appeal at 10 (quoting Tr. 3371)), \n \n 14 the courtʹs actual relationship language (included in Guptaʹs quote but omitted from \n \n 15 his argument) was ʺmaintaining a good relationship with a frequent business partnerʺ \n \n 16 (Tr. 3371 (emphasis added)). \n\n\n\n\n  10\n\f 1 Second, the trial courtʹs reference to a good relationship with a frequent \n \n 2 business partner was consistent with the Supreme Courtʹs discussion in Dirks v. SEC, \n \n 3 463 U.S. 646 (1983), as to what may properly be considered a tipperʹs anticipated \n \n 4 personal benefit sufficient to warrant his conviction of insider trading. In Dirks, \n \n 5 noting that ʺa purpose of the securities laws was to eliminate use of inside \n \n 6 information for personal advantage,ʺ id. at 662 (internal quotation marks omitted), the \n \n 7 Court stated that the test for whether that purpose has been contravened is ʺwhether \n \n 8 the insider receives a direct or indirect personal benefit from the disclosure, such as \n \n 9 a pecuniary gain or a reputational benefit that will translate into future earnings.ʺ  Id. \n \n 10 at 663.  The Court also stated that an inference of such a benefit may be warranted by \n \n 11 the circumstance of ʺa relationship between the insider and the recipient that suggests \n \n 12 a quid pro quo from the latter, or an intention to benefit the particular recipient.ʺ Id. \n \n 13 at 664.  Where the recipient of the tip is the tipperʹs ʺfrequentʺ ʺbusinessʺ partner, the \n \n 14 tipperʹs anticipation of a quid pro quo is easily inferable. \n \n 15 Third, the Dirks Courtʹs use of the above  disjunctives (i.e., ʺsuch as a \n \n 16 pecuniary gain or a reputational benefit that will translate into future earnings,ʺ id. \n \n 17 at 663, and ʺa quid pro quo from the [recipient] or an intention to benefit the particular \n \n 18 recipient,ʺ id.  at 664)—especially prefaced by ʺsuch asʺ—suggests varying sets of \n\n\n  11\n\f 1 circumstances each of which would warrant a finding of the tipperʹs illegal purpose. \n \n 2 Thus, while Gupta argues that the instruction at his trial was ʺinvalidʺ under Newman \n \n 3 for stating that ʺʹthe benefit does not need to be financial or to be tangibleʹʺ  (Gupta \n \n 4 brief on appeal at 10), that instruction was warranted by Dirks. Indeed, the lack  of \n \n 5 need for proof of the tipperʹs financial or tangible gain was highlighted as well by the \n \n 6 Dirks Courtʹs illustration that \n \n 7 [t]he  elements  of  fiduciary  duty  and  exploitation  of  nonpublic \n 8 information also exist when an insider makes a gift of confidential \n 9 information  to  a  trading  relative  or  friend.  The tip and trade \n 10 resemble trading by the insider himself followed by a gift of the \n 11 profits to the recipient. \n \n 12 463 U.S. at 664; see also United States v. Martoma, 894 F.3d 64, 75 (2d Cir. 2018)  (ʺThe \n \n 13 tipperʹs intention to benefit the tippee proves a breach of fiduciary duty because it \n \n 14 demonstrates that the tipper improperly used inside information for personal ends \n \n 15 and thus lacked a legitimate corporate purpose.ʺ). \n \n 16 Finally, the trial courtʹs instruction that the benefit to Gupta need not \n \n 17 have  been  financial  or  tangible,  although  contrary  to  the  formulation  given  in \n \n 18 Newman, could not have constituted prejudice to Gupta because it was correct. The \n \n 19 Newman formulation was expressly rejected by the Supreme Court in Salman v. United \n \n 20 States, 137 S. Ct. 420 (2016), as that Court noted that \n\n\n  12\n\f 1 [t]o the extent the Second Circuit held that the tipper must also \n 2 receive something of a ʺpecuniary or similarly valuable natureʺ in \n 3 exchange for a gift to family or friends, Newman, 773 F.3d, at 452, \n 4 . . . this requirement is inconsistent with Dirks. \n \n 5 137 S. Ct. at 428. Thus, in the wake of Salman, we have stated that ʺit is settled  law \n \n 6 that personal benefits may be indirect and intangible and need not be pecuniary at \n \n 7 all.ʺ United States v. Martoma, 894 F.3d at 75. \n \n 8 The fact that Newmanʹs requirement for proof of a tipperʹs pecuniary or \n \n 9 other  tangible  gain  has  been  rejected  by  the  Supreme  Court  disposes  of  Guptaʹs \n \n 10 contention—invoking Montgomery v. Louisiana, 136 S. Ct. 718, a case that involved \n \n 11 principles   of   retroactivity   and   that  did not address issues of cause and \n \n 12 prejudice—that Newman meant the trial courtʹs instruction that proof of pecuniary or \n \n 13 tangible benefit was not necessary caused him to be convicted of a crime for ʺconduct \n \n 14 that is not criminalʺ (Gupta brief on appeal at 22). \n \n \n \n 15 No Innocence \n \n 16 Lastly, as to the claim of actual innocence, Gupta has not ʺdemonstrate[d] \n \n 17 that, ʹin light of all the evidence,ʹ ʹit is more likely than not that no reasonable juror \n \n 18 would have convicted him,ʹʺ Bousley, 523 U.S. at 623 (quoting Schlup v. Delo, 513 U.S. \n\n\n\n  13\n\f 1 at 327‐28 (emphasis ours)), of insider trading.  As a matter of background, the record \n \n 2 as a whole, viewed in the light most favorable to the government, contained ample \n \n 3 evidence that Gupta and Rajaratnam were business associates. Gupta had invested \n \n 4 several million dollars in Galleon funds.  In 2005, Gupta and Rajaratnam invested in \n \n 5 another investment fund capitalized with $50 million; Gupta originally contributed \n \n 6 $5 million; he later doubled his investment with $5 million loaned to him by \n \n 7 Rajaratnam.  In  early  2008,  Gupta  was  made  chairman  of  Galleon  International, \n \n 8 which, as of April 2008, managed assets totaling some $1.1 billion and could earn \n \n 9 performance fees; Gupta was given a 15 percent ownership stake in that fund. Gupta \n \n 10 also regularly worked on Galleonʹs behalf in seeking potential investors; he had a \n \n 11 keycard allowing him access to Galleonʹs New York offices. See Gupta I, 747 F.3d at \n \n 12 116‐21. Gupta described Rajaratnam as a very close friend. Rajaratnamʹs address \n \n 13 book noted Gupta as a good friend; and Gupta was one of five persons whose call \n \n 14 Rajaratnamʹs secretary was authorized to put through if he called near the end of the \n \n 15 trading day. See id. at 121. \n \n 16 The jury was instructed that in order to convict Gupta on any given \n \n 17 count, it must find, inter alia, that ʺGupta anticipated that Mr. Rajaratnam or others \n \n 18 at Galleon would trade on the basis of th[e non‐public] informationʺ provided by \n\n\n  14\n\f 1 Gupta, that ʺthey then did so by buying or selling the shares specified in the count on \n \n 2 the basis of the inside information,ʺ and that ʺGupta, in return for providing this \n \n 3 information, anticipated receiving some personal benefit.ʺ (Tr. 3371.) There  was \n \n 4 ample evidence to permit the jury to find that Gupta intended Rajaratnam to trade on \n \n 5 the  basis  of  the  confidential  information  Gupta  passed  to  him  and  that  Gupta \n \n 6 personally benefitted in one of the ways envisioned in Dirks. \n \n 7 For example, on September 23, 2008, Gupta, a member of the board  of \n \n 8 directors  of  The  Goldman  Sachs  Group,  Inc.  (ʺGoldman  Sachsʺ  or  ʺGoldmanʺ), \n \n 9 participated in a Goldman board meeting via telephone and learned that Warren \n \n 10 Buffett was about to invest $5 billion in Goldman, which would be publicly \n \n 11 announced at 6 p.m. that day.  At 3:54 p.m.—one minute after the end of that board‐ \n \n 12 meeting telephone call—Gupta called Rajaratnam, telling Rajaratnamʹs secretary that \n \n 13 the  call was  urgent.  Gupta and Rajaratnam spoke briefly, and Rajaratnam then \n \n 14 immediately began having his people at Galleon buy Goldman shares.  Between 3:56 \n \n 15 p.m. and the 4:00 p.m. close of the market, they bought Goldman shares costing a \n \n 16 total of more than $33 million. The next morning, the price of the stock rose some \n \n 17 seven  percent.  See  Gupta  I,  747  F.3d at  117‐19.  The timing of Guptaʹs call to \n \n 18 Rajaratnam immediately after the end of his board call, and his statement at 3:54 p.m \n\n\n  15\n\f 1 that he needed to speak to Rajaratnam urgently, plainly allowed the inference  that \n \n 2 Gupta intended Rajaratnam to buy, and profit on, Goldman shares in advance of the \n \n 3 Buffett $5 billion announcement at 6 p.m. \n \n 4 Similarly, on October 23, 2008, Gupta learned in a Goldman Sachs board‐ \n \n 5 of‐directors  conference  call  that  Goldman  would  report  in  December  a  quarterly \n \n 6 financial loss.  The loss would be its first in its history as a public  company, and \n \n 7 market analysts were predicting another profitable quarter. One minute after the end \n \n 8 of that board  conference  call, Gupta   called  Rajaratnam.  The next morning, one \n \n 9 minute after the stock market opened, Rajaratnam began selling Goldman shares. In \n \n 10 little  over  an  hour,  Rajaratnam  sold  enough  shares  to  avoid  a  loss  of  more  than \n \n 11 $3.8  million.  Rajaratnam  also  advised  a  portfolio  manager  of  Galleon \n \n 12 International—which had in the past invested in Goldman stock, and in which Gupta \n \n 13 had a 15 percent ownership stake—that on the previous day Rajaratnam had received \n \n 14 confidential information from a Goldman board member, negative news that would \n \n 15 not be reported publicly until December. Rajaratnam said he himself would  make \n \n 16 short sales of Goldman stock. See Gupta I, 747 F.3d at 118‐21. On this evidence and \n \n 17 the record as a whole, the jury could rationally have found that Gupta anticipated \n \n 18 that Rajaratnam would engage in trading of Goldman shares that would benefit \n\n\n  16\n\f 1 Gupta financially. \n \n \n \n 2 Conclusion \n \n \n \n 3 We have considered all of Guptaʹs arguments on this appeal and have \n \n 4 found them to be without merit. The judgment of the district court is affirmed. \n\n\n\n\n  17\n[END_CASE]", "role": "user" } ]
4,580,818
Federal Trade Commission v. Federal Check Processing, Inc.
2019-01-11
16-3811-(L)
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: CABRANES, SACK, AND PARKER, Circuit Judges.", "parties": "", "opinions": [{"author": "SACK, Circuit Judge:", "type": "010combined", "text": "16‐3811‐(L) \nFederal Trade Commission v. Federal Check Processing, Inc. \n \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n August Term, 2018 \n (Argued: October 3, 2018   Decided: January 11, 2019) \n Docket No. 16‐3811‐cv, 16‐3805‐cv \n\n  \n  \n FEDERAL TRADE COMMISSION, \n Plaintiff‐Appellee, \n\n v. \n\n WILLIAM MOSES, individually and as an officer of one or more of the Corporate \n Defendants, FEDERAL CHECK PROCESSING INC., a New York corporation, MARK \n BRIANDI, individually and as an officer of one or more of the Corporate \n Defendants. \n Defendants‐Appellants, \n FEDERAL RECOVERIES, LLC, et al., \n Defendants. \n  \nBefore:  CABRANES, SACK, AND PARKER, Circuit Judges. \n\n The Federal Trade Commission brought this action in the United States \n\nDistrict Court for the Western District of New York alleging that the defendantsʹ \n\ndebt collection practices had violated several provisions of the Federal Trade \n\nCommission Act and the Federal Fair Debt Collection Practices Act.  The court \n\n(William M. Skretny, Judge) adopted a report and recommendation of Magistrate \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nJudge Michael J. Roemer recommending that summary judgment be granted in \n\nfavor of the FTC.   \n\n The defendant‐appellant William Moses submitted no brief prior to the \n\ndeadline for submission set by this Court.  We therefore dismiss his appeal \n\npursuant to Local Rule 31.2(d).  The defendant‐appellant Mark Briandi asserts \n\nthat there are genuine issues of material fact as to whether he had knowledge of \n\nthe businessesʹ practices at the heart of this action.  He also contends that the \n\ndisgorgement order against him is grossly excessive.  The evidence before the \n\ncourt on summary judgment established as a matter of law that Briandi had \n\ncontrol over the companiesʹ affairs, was aware of their illegal practices, and, \n\ntherefore, was liable for them.  We conclude that the disgorgement assessed \n\njointly and severally against all defendants, including Briandi and Moses, was in \n\nan appropriate amount because it was a reasonable approximation of the total \n\namounts received by the defendant companies from consumers as a result of \n\ntheir unlawful acts.  The judgment of the district court is therefore: \n\n AFFIRMED.     \n\n HERBERT L. GREENMAN, Lipsitz Green \n Scime Cambria, LLP, Buffalo, NY, for \n Defendant‐Appellant Mark Briandi. \n\n\n 2 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n MICHELE ARINGTON (David C. Shonka, Joel \n Marcus, Katherine M. Worthman, Colin A. \n Hector, on the brief), Federal Trade \n Commission, Washington, D.C., for \n Plaintiff‐Appellee.  \nSACK, Circuit Judge: \n\n The Federal Trade Commission (the ʺFTCʺ or the ʺgovernmentʺ) brought \n\nthis action against thirteen corporate entities (the ʺCorporate Defendantsʺ) and \n\ndefendants‐appellants Mark Briandi (ʺBriandiʺ) and William Moses (ʺMosesʺ) \n\nalleging that the defendants’ combined debt collection violated the Federal Trade \n\nCommission Act (ʺFTCAʺ), 15 U.S.C. § 45(a), and the Fair Debt Collection \n\nPractices Act (ʺFDCPAʺ), 15 U.S.C. § 1692 et seq.  The United States District Court \n\nfor the Western District of New York (William M. Skretny, Judge) adopted the \n\nreport and recommendation of Magistrate Judge Michael J. Roemer, \n\nrecommending the grant of summary judgment to the FTC on the grounds that \n\nthe evidence before the court had established as a matter of law that the \n\nCorporate Defendants violated the FTCA and FDCPA, and that Briandi and \n\nMoses were personally liable for the amount of money that the defendants had \n\nreceived because of the violations. \n\n\n\n\n 3 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Briandi and Moses appealed.  Moses did not file a brief, and, there being \n\nno valid excuse proffered therefor, we dismiss his appeal pursuant to our Local \n\nRule 31.2(d).1  \n\n Briandi does not contest the district court’s conclusion that the Corporate \n\nDefendants violated the FTCA and FDCPA.  He argues instead that the court \n\nerred by concluding that he is personally liable for the violations.  He also \n\ncontends that the district court erred by setting the measure of equitable \n\nmonetary relief as the total proceeds of the debt collection enterprise.  For the \n\nreasons set forth below, we agree with the district court on both issues, and, \n\ntherefore, affirm its judgment.   \n\n BACKGROUND \n\n General Factual Background2 \n\n In 2009, Briandi and Moses founded, and thereafter co‐owned and co‐\n\ndirected, the first of the Corporate Defendants, Federal Recoveries, LLC.  Over \n\n\n\n                                                            \n  Local Rule 31.2(d) provides:  ʺFailure to File.  The court may dismiss an appeal or \n 1\n\ntake other appropriate action for failure to timely file a brief or to meet a deadline under \nthis rule.ʺ \n 2 The following statement of facts is taken primarily from the FTCʹs ʺStatement of \n\nMaterial Facts as to Which There is no Genuine Issue to be Tried,ʺ which is largely \nundisputed, and, where relevant, evidence Briandi proffered in attempting to establish \nthe existence of a genuine dispute of material fact.   \n 4 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nthe next few years, Briandi or Moses incorporated twelve other Corporate \n\nDefendants, which were part of a single debt collection enterprise.  The \n\nCorporate Defendantsʹ business consisted largely of collecting payday loan \n\ndebts,3 which they bought from consumer‐debt creditors and compiled into debt \n\nportfolios.  These portfolios contained debtorsʹ names, addresses, and general \n\ninformation about the debts allegedly owed. \n\n\n At the Corporate Defendantsʹ behest, nearly all of their approximately \n\ntwenty‐five employee‐debt collectors would routinely contact debtors by \n\ntelephone and falsely identify themselves as ʺprocessors,ʺ ʺofficers,ʺ or \n\nʺinvestigatorsʺ from a ʺfraud unitʺ or ʺfraud division,ʺ then accuse debtors of \n\ncheck fraud or a related crime and threaten them with criminal prosecution if \n\nthey did not pay their debts.  On some occasions, collectors called friends, family \n\nmembers, employers, or co‐workers of debtors, telling them that the debtors \n\nowed a debt, had committed a crime in failing to pay it, and faced possible legal \n\n\n                                                            \n   ʺWhile there is no set definition of a payday loan, it is usually a short‐term, high cost \n 3\n\nloan, generally for $500 or less, that is typically due on [the borrowerʹs] next payday.ʺ  \nU.S. Consumer Financial Protection Bureau, ʺWhat is a payday loan?,ʺ available at \nhttps://www.consumerfinance.gov/ask‐cfpb/what‐is‐a‐payday‐loan‐en‐1567/ (last \nvisited December 16, 2018); see also Fed. Trade Commʹn v. Fed. Check Processing, Inc., \nNo. 14‐CV‐122‐WMS‐MJR, 2016 WL 5956073, at *2 n.5, 2016 U.S. Dist. LEXIS \n50589, at *7‐8 n.5 (W.D.N.Y. Apr. 13, 2016) (similar). \n 5 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nrepercussions.  When debtors or other interested parties sought further \n\ninformation about the debt, collectors typically refused to provide it. \n\n\n After receiving a litany of consumer complaints about these activities, the \n\nOffice of the New York State Attorney General began investigating the Corporate \n\nDefendantsʹ businesses.  On February 3, 2013, in an attempt to terminate the \n\ninvestigation, Briandi and Moses executed, on behalf of themselves and the \n\nrelevant Corporate Defendants, a written ʺAssurance of Discontinuanceʺ (the \n\nʺAODʺ) with the State Attorney General.  While not admitting fault, Briandi and \n\nMoses conceded in the AOD that the Corporate Defendants were subject to \n\nspecified federal and state laws, including the FDCPA.  Additionally, they \n\nagreed to dissolve some of the Corporate Defendants.  And they stated that they \n\nwould advise the New York State Attorney Generalʹs Office if any of the \n\nCorporate Defendants changed their principal place of business; if the individual \n\ndefendants incorporated a new corporation or business entity; or if any of the \n\nCorporate Defendants did business under a new name.  On May 8, 2013, Briandi \n\nand Moses also executed an affidavit in which they represented that they had \n\nimplemented procedures — including the hiring of a ʺcompliance officerʺ — to \n\nensure that the Corporate Defendants met the requirements of the FDCPA. \n\n\n 6 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Shortly after the AOD became effective, though, and without informing \n\nthe Attorney Generalʹs Office, Briandi and Moses incorporated new Corporate \n\nDefendants, some in other states.  And the Corporate Defendants continued to \n\nengage in the forsworn practices. \n\n\n Briandiʹs Corporate Responsibilities  \n\n\n Briandi was a co‐founder, co‐owner, co‐director, and general manager of \n\nall but perhaps one of the Corporate Defendants.  He maintained a personal \n\noffice within the Corporate Defendantsʹ East Amherst, New York, office and a \n\ndesk in the ʺcollection callʺ area from which dunning calls were made by the \n\ncompaniesʹ employees.  Briandi had signature authority with respect to the \n\ncompaniesʹ bank accounts, and in the more than four years between February 10, \n\n2010, and February 26, 2014, received approximately $1.3 million in \n\ncompensation from the Corporate Defendants. \n\n\n Briandiʹs principal responsibilities for the companies included signing \n\ntheir checks; managing the banking side of their businesses; handling personnel \n\nmatters, such as hiring and firing employees; maintaining the companiesʹ phone \n\nsystems and websites; receiving consumer payments; and — along with Moses, \n\nwho was in charge of collections — operating the entity, bearing the mellifluous \n\n 7 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nname ʺFlowing Streams,ʺ which purchased consumer debts.  Prior to 2013, \n\nBriandi would himself also occasionally make collection calls on behalf of the \n\nCorporate Defendants. \n\n\n After the instant litigation began, Briandi asserted in a deposition taken by \n\nFTC counsel on April 15, 2015, that, beginning in March of 2013, he had a \n\ndiminished involvement with the Corporate Defendants.  He testified that this \n\nresulted from his decision to become a pastor, which led to his spending much of \n\nhis work days praying in his office and taking online bible classes.  Although \n\nBriandi acknowledged that he continued to review corporate bank accounts from \n\ntime to time, speak to managers, and occasionally take ʺhostileʺ consumer calls, \n\nBriandi Dep., April 15, 2015, at 65‐66, 72; he denied having continued to visit his \n\ndesk on the collection floor more than ʺonceʺ or ʺtwiceʺ a day, id. at 134, 137, 143.   \n\n\n Procedural History  \n\n On February 24, 2014, the FTC filed a complaint against Briandi, Moses, \n\nand the Corporate Defendants in the United States District Court for the Western \n\nDistrict of New York.  It alleged two violations of Section 5(a) of the FTCA, 15 \n\nU.S.C. § 45(a) (ʺUnfair or Deceptive Acts or Practicesʺ), and four violations of the \n\nFDCPA, 15 U.S.C § 1692 (ʺDebt Collection Practicesʺ).  The FTC accused the \n\n 8 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndefendants of violating the statutes, despite having executed the AOD, by \n\noperating companies in which collectors continued to mask their identities, \n\nfalsely accuse consumers of various crimes, and refuse to reveal to debtors the \n\ncircumstances and nature of alleged debts.  The FTC also sought and received \n\nfrom the district court an ex parte temporary restraining order prohibiting the \n\ndefendants from using false representations or deceptive means to continue \n\ncollecting debts, freezing all of the defendantsʹ assets, and appointing a receiver \n\nto oversee the Corporate Defendants.  \n\n\n On June 17, 2014, Briandi and Moses asked the district court for one year in \n\nwhich to conduct discovery.  A magistrate judge granted their request but noted \n\nthat ʺno extensions of this order will be entertained.ʺ  Dkt. No. 67. \n\n\n Meanwhile, the FTC subpoenaed and received copies of a variety of scripts \n\nused by the Corporate Defendantsʹ employees to make demand telephone calls, \n\nrecordings of telephone calls between various collectors and consumers, and \n\nmany consumer complaints and declarations detailing and challenging the \n\ncompaniesʹ practices.  The FTC also submitted interrogatories to the defendants \n\nand took oral depositions of Briandi and Moses.  For their parts, though, Briandi, \n\nMoses, and the Corporate Defendants engaged in no discovery.  And Briandi \n\n 9 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nfailed to answer interrogatories propounded by the FTC until after the discovery \n\ndeadline had passed, and then only as part of his attempt to oppose the FTCʹs \n\nmotion for summary judgment. \n\n\n The FTC moved for summary judgment on August 27, 2015.  The motion \n\nincluded a request for $10,852,396 in monetary relief, for which, the FTC \n\nasserted, all of the defendants, include Briandi and Moses, should be jointly and \n\nseverally liable.  That figure was based on ʺthe gross total of consumer funds \n\ndeposited by merchant processorsʺ found ʺin the [d]efendantsʹ settlement \n\naccounts.ʺ  Second Suppl. Decl. of FTC Investigator Michael B. Goldstein ¶ 26 \n\n(July 24, 2015). \n\n\n Briandi did not dispute the allegations that the Corporate Defendants \n\nengaged in wrongdoing.  He denied, however, that he could be held individually \n\nliable for the Corporate Defendantsʹ actions.  He based that argument largely on \n\nhis contention that he did not control the Corporate Defendants, did not \n\nparticipate in their activities, and lacked any knowledge of their alleged \n\nwrongdoing.  Briandi also asserted that the governmentʹs requested relief vastly \n\nexceeded the Corporate Defendantsʹ unlawful gains. \n\n\n The District Courtʹs Decision \n\n 10 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n On April 13, 2016, Michael J. Roemer, the magistrate judge to whom the \n\nmatter had by then been referred by the district court ʺfor all pre‐trial matters, \n\nincluding preparation of a report and recommendation on dispositive motions,ʺ \n\nissued a report and recommendation concluding that the FTCʹs motion for \n\nsummary judgment should be granted.  FTC v. Fed. Check Processing, Inc., No. 14‐\n\nCV‐122‐WMS‐MJR, 2016 WL 5956073, at *1, 2016 U.S. Dist. LEXIS 50589, at *2 \n\n(W.D.N.Y. Apr. 13, 2016), adopted, No. 14‐CV‐122S, 2016 WL 5940485, 2016 U.S. \n\nDist. LEXIS 141998 (W.D.N.Y. Oct. 13, 2016).  First, the magistrate judge \n\nconcluded that the FTC had proved that Briandi both had ʺthe authority to \n\ncontrol the [C]orporate [D]efendants and knew of their wrongdoing.ʺ  Id. at *14, \n\n2016 U.S. Dist. LEXIS 50589 at *41‐42.  According to the magistrate judge, even if \n\nBriandi somehow lacked detailed knowledge of the Corporate Defendantsʹ illicit \n\ncollection practices, he could not plead ignorance after expressly agreeing to the \n\n2013 AOD.  Id. at *13, 2016 U.S. Dist. LEXIS 50589 at *40.  The existence of the \n\nAOD executed by Briandi established that he had notice of the Corporate \n\nDefendantsʹ illicit collection activities and was required to ensure that they \n\nfollowed the FTCA and the FDCPA.  Id., 2016 U.S. Dist. LEXIS 50589 at *40. \n\n\n\n\n 11 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Second, the magistrate judge concluded that the FTCʹs disgorgement \n\nrequest ʺreasonably approximate[d] the [C]orporate [D]efendantsʹ unjust gains.ʺ  \n\nId. at *16, 2016 U.S. Dist. LEXIS 50589 at *48.  As the magistrate judge observed, \n\nthis amount was based on bank account data compiled by the FTC showing that \n\nʺbetween May 2010 and March 2014 the [C]orporate [D]efendants collected \n\n$10,852,396 from consumers.ʺ  Id., 2016 U.S. Dist. LEXIS 50589 at *48.  The FTC \n\nhad also demonstrated that ʺthe defendantsʹ misrepresentations were widely \n\ndisseminated,ʺ and that their operation was ʺpermeated with fraud.ʺ  Id., 2016 \n\nU.S. Dist. LEXIS 50589 at *48.   Finally, the magistrate judge noted that the \n\ndefendant had failed to produce any evidence that would serve to dispute the \n\nrecommended penalty.  Id., 2016 U.S. Dist. LEXIS 50589 at *48. \n\n\n On October 12, 2016, the district court adopted Magistrate Judge Roemerʹs \n\nreport and recommendation in its entirety and entered judgment in the \n\ngovernmentʹs favor.  Fed. Trade Commʹn v. Fed. Check Processing, Inc., No. 14‐CV‐\n\n122S, 2016 WL 5940485, at *1, 2016 U.S. Dist. LEXIS 141998, at *4 (W.D.N.Y. Oct. \n\n13, 2016). \n\n\n\n\n 12 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n DISCUSSION \n\n Briandi makes three principal arguments on appeal.  First, he contends \n\nthat he should have been given time to conduct discovery.  Second, he argues, \n\nbased on the information contained in his deposition, that there were material \n\nfacts at issue as to whether he could be held individually liable for the actions of \n\nthe Corporate Defendants.  He contends that these factual issues rendered \n\nsummary judgment for the FTC improper.  Finally, he asserts that the \n\ndisgorgement amount adopted by the district court was grossly excessive.  For \n\nthe reasons that follow, we disagree with each of these contentions. \n\n\n I. Standard of Review \n\n\n A district courtʹs decision on a partyʹs request for ʺmore time to conduct \n\ndiscovery . . . is subject to reversal only if [the district court] abused its \n\ndiscretion.ʺ  Paddington Partners v. Bouchard, 34 F.3d 1132, 1137 (2d Cir. 1994).   \n\n\n We review the ʺdistrict courtʹs decision to grant summary judgment de \n\nnovo, resolving all ambiguities and drawing all permissible factual inferences in \n\nfavor of the party against whom summary judgment is sought.ʺ  Burg v. Gosselin, \n\n591 F.3d 95, 97 (2d Cir. 2010) (internal quotation mark omitted).  Summary \n\njudgment is appropriate only when ʺthe movant shows that there is no genuine \n\n 13 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndispute as to any material fact and the movant is entitled to judgment as a matter \n\nof law.ʺ  Fed. R. Civ. P. 56(a).  However, ʺa party may not rely on mere \n\nspeculation or conjecture as to the true nature of the facts to overcome a motion \n\nfor summary judgment.ʺ  Fletcher v. Atex, Inc., 68 F.3d 1451, 1456 (2d Cir. 1995) \n\n(internal quotation marks omitted).  ʺ[C]onclusory allegations or denialsʺ \n\ntherefore ʺare not evidence and cannot by themselves create a genuine issue of \n\nmaterial fact where none would otherwise exist.ʺ  Id. (internal quotation marks \n\nomitted).   \n\n\n II. Additional Discovery \n\n Briandi contends that the district court wrongly denied an extension to the \n\none‐year discovery period already provided.  But Briandi has waived this \n\nargument.  Federal Rule of Civil Procedure 56(d) provides that a party opposing \n\nsummary judgment based on incomplete discovery must file an affidavit \n\nexplaining why such discovery is necessary.  See id. (ʺIf a nonmovant shows by \n\naffidavit or declaration that, for specified reasons, it cannot present facts essential \n\nto justify its opposition, the court may . . . allow time to obtain affidavits or \n\ndeclarations or to take discovery.ʺ)  Briandi submitted no such affidavit to the \n\nmagistrate judge or the district court; nor does he contend otherwise. \n\n\n 14 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Also, it was Briandi and Moses who asked for the approximately one‐year \n\ndiscovery period, and then chose, for unstated reasons, not to conduct any \n\ndiscovery at all during that period.  Briandi now asserts that he did not \n\nunderstand the ʺcircumstances of [his] position.ʺ  Briandi Br. 22.  However, he \n\nidentifies no standard upon which to judge whether or not that is the case. Nor \n\ndoes he explain how the ʺcircumstances of his positionʺ were unclear or \n\nconfusing, or provide any authority for the proposition that, if they were, he was \n\ntherefore entitled to an extension on the lengthy period the court provided for \n\ndiscovery. \n\n\n III. Briandiʹs Personal Liability \n\n Briandi argues that the district court erred in granting summary judgment \n\nagainst him because genuine disputes of material fact exist regarding his control \n\nof the debt collection agencies, and therefore his personal liability for their \n\nactions.  We disagree.  In light of the undisputed evidence regarding the \n\nCorporate Defendants’ operations and Briandi’s relationship with them, we \n\nconclude that he had both sufficient authority over the Corporate Defendants, \n\nand knowledge of their practices, to be held individually liable for their \n\nmisconduct as a matter of law. \n\n\n 15 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n A.  Standard for Individual Liability Under the FTCA and FDCPA \n\n\n Section 5(a)(1) of the FTCA, 15 U.S.C. § 45(a)(1), prohibits ʺ[u]nfair or \n\ndeceptive acts or practices in or affecting commerce.ʺ  The FTC must show three \n\nelements to prove a deceptive act or practice in violation of § 5(a)(1): ʺ[1] a \n\nrepresentation, omission, or practice, that [2] is likely to mislead consumers \n\nacting reasonably under the circumstances, and [3], the representation, omission, \n\nor practice is material.ʺ FTC v. Verity Intʹl, Ltd., 443 F.3d 48, 63 (2d Cir. 2006) \n\n(brackets in the original; internal quotation marks omitted).  ʺThe deception need \n\nnot be made with intent to deceive; it is enough that the representations or \n\npractices were likely to mislead consumers acting reasonably.ʺ  Id.  \n\n\n An individual may be held liable under the FTCA for a corporation’s \n\ndeceptive acts or practices ʺif, with knowledge of the deceptive nature of the \n\nscheme, he either ʹparticipate[s] directly in the practices or acts or ha[s] authority \n\nto control them.ʹʺ  FTC v. LeadClick Media, LLC, 838 F.3d 158, 169 (2d Cir. 2016) \n\n(quoting FTC v. Amy Travel Serv., Inc., 875 F.2d 564, 573 (7th Cir. 1989)).4   To \n\nprevail on the issue, the FTC must therefore establish that \n\n\n                                                            \n  The First, Fourth, Seventh, Ninth, Tenth, and Eleventh Circuits have also adopted \n 4\n\nthis standard.  See FTC v. Direct Mktg. Concepts, Inc., 624 F.3d 1, 12 (1st Cir. 2010); FTC v. \nRoss, 743 F.3d 886, 892 (4th Cir. 2014); FTC v. Amy Travel Serv., Inc., 875 F.2d 564, 573‐74 \n 16 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n the corporate practices were misrepresentations or \n omissions of a kind usually relied on by reasonably \n prudent persons and that consumer injury resulted.  \n Once corporate liability is established, the FTC must \n show that the individual defendants participated \n directly in the practices or acts or had authority to \n control them.  Authority to control the company can be \n evidenced by active involvement in business affairs and \n the making of corporate policy, including assuming the \n duties of a corporate officer.   \n\nAmy Travel, 875 F.2d at 573 (citations omitted).  ʺThe FTC is [also] required to \n\nestablish the defendants had or should have had knowledge or awareness of the \n\nmisrepresentations.ʺ  Id. at 574 (citation omitted). \n\n The FTC need not establish in this context that the defendant had actual \n\nand explicit knowledge of the particular deception at issue.  We agree with our \n\nsister circuits that ʺknowledge ʹmay be established by showing that the \n\nindividual [defendant] had actual knowledge of the deceptive conduct, [or] was \n\nrecklessly indifferent to its deceptiveness, or had an awareness of a high \n\nprobability of deceptiveness and intentionally avoided learning of the truth.ʹʺ  \n\nFTC v. Primary Grp., Inc., 713 F. Appʹx 805, 807 (11th Cir. 2017) (per curiam) \n\n(quoting FTC v. Ross, 743 F.3d 886, 892 (4th Cir. 2014)); accord FTC v. World Media \n\n                                                            \n(7th Cir. 1989);  FTC v. Grant Connect, LLC, 763 F.3d 1094, 1101 (9th Cir. 2014); FTC v. \nFreecom Commcʹns, Inc., 401 F.3d 1192, 1204, 1207 (10th Cir. 2005); FTC v. IAB Mktg. \nAssocs., LP, 746 F.3d 1228, 1233 (11th Cir. 2014). \n 17 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nBrokers, 415 F.3d 758, 764 (7th Cir. 2005).5  And we agree with the Eleventh \n\nCircuit that ʺthis standard correctly describes the breadth of individual liability \n\nunder the FTC[A].ʺ  Primary Grp., 713 F. App’x at 807.  Imposing a more rigid \n\nknowledge requirement ʺwould be inconsistent with the policies behind the \n\nFTCA and place too great a burden on the FTC.ʺ  Amy Travel, 875 F.2d at 574. \n\n Finally on this score, we conclude that the same standard applies when the \n\nFTC brings an action to enforce the FDCPA.  ʺ[V]iolations of the FDCPA are \n\ndeemed to be unfair or deceptive acts or practices under the [FTCA].ʺ  Jerman v. \n\nCarlisle, McNellie, Rini, Kramer & Ulrich LPA, 559 U.S. 573, 577, (2010); see also 15 \n\nU.S.C. § 1692l(a) (ʺ[A] violation of [the FDCPA] shall be deemed an unfair or \n\ndeceptive act or practice in violation ofʺ the FTCA and is subject to enforcement \n\nʺin the same manner as if the violation had been a violation of a[n] [FTC] trade \n\nregulation rule.ʺ)  The FTC, then, is enforcing the FDCPA pursuant to its \n\nauthority under the FTCA.  And because the FTC can enforce compliance with \n\nthe FDCPA only by employing the FTCA, and ʺin the same manner as a \n\nviolationʺ of the FTCA, 15 U.S.C. § 1692l(a), it follows, we conclude, that the \n\nFTCA individual liability standard applies. \n\n                                                            \n  Under Eleventh Circuit Local Rule 36‐2, “[u]npublished opinions are not considered \n 5\n\nbinding precedent, but they may be cited as persuasive authority,” as we do here. \n 18 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n B.  Briandiʹs Authority to Control the Corporate Defendants \n\n\n Briandi was a founder of all but perhaps one of the Corporate Defendants, \n\nheld a 50 percent ownership stake in them, had signatory authority over their \n\nbank accounts, and served as their co‐director and general manager.  In these \n\nvarious roles, Briandi had the authority to control the Corporate Defendants’ \n\ndeceptive actions.  For example, in his deposition, Briandi admitted to having the \n\npower to hire and reprimand employees including those responsible for the \n\nCorporate Defendantsʹ violations of the FTCA and FDCPA. \n\n\n Briandi retained this authority after signing the AOD.  From March 2013 \n\nuntil the time of the FTCʹs complaint, he remained a co‐owner, co‐director, and \n\ngeneral manager of the Corporate Defendants, fielded hostile calls from \n\nconsumers, continued to review the Corporate Defendantsʹ financial activities, \n\nand, once or twice a day, would visit the collection floor, where he would speak \n\nto other managers about the corporationsʹ business. \n\n\n Briandi’s deposition testimony that he contends was to the contrary was \n\ndirected to the question of whether he exercised authority to control the Corporate \n\nDefendantsʹ conduct, not whether he possessed authority to control it, which is the \n\ndispositive issue.  Viewed in light of all the evidence properly before the district \n\n 19 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ncourt on the motion for summary judgment, then, Briandiʹs denial of \n\ninvolvement in, rather than the authority to control the actions of, the Corporate \n\nDefendants did not create a dispute of material fact requiring the district court to \n\ndeny the motion. \n\n\n C.  Briandiʹs Knowledge of the Corporate Defendantsʹ Activities \n\n\n The defendants were ordered to disgorge $10,852,396, an amount equal to \n\nall profits ʺresulting from [d]efendantsʹ unlawful acts or practices,ʺ Fed. Check \n\nProcessing, Inc., 2016 WL 5940485, at *4, 2016 U.S. Dist. LEXIS 50589, at *40 \n\n(adopting magistrate judgeʹs April 13 ,2016 report and recommendation).  This \n\namount was calculated by the magistrate judge based on the Corporate \n\nDefendantsʹ bank account data between May 2010 and March 2014.  The FTC \n\ntherefore was required to establish that Briandi had knowledge of the Corporate \n\nDefendantsʹ wrongdoing during that entire period — both prior to and after his \n\nexecution of the 2013 AOD — to hold him individually liable for the unlawful \n\nreceipts of the Corporate Defendants during the same period.   We conclude that \n\nthe FTC did so. \n\n\n We agree with the magistrate judgeʹs report and recommendation that \n\nafter the AOD was executed by Briandi in 2013, Briandi was at least aware ʺof a \n\n 20 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nhigh probability of fraud and intentionally avoided learning the truth.ʺ  Fed. \n\nCheck Processing, Inc., 2016 WL 5956073, at *13, 2016 U.S. Dist. LEXIS 50589, at *36.  \n\nThe AOD explicitly accused the Corporate Defendants of violating the FTC and \n\nFDCPA.   \n\n\n After executing the document, Briandi nonetheless continued to oversee \n\nthe Corporate Defendantsʹ collection activities.  As the magistrate judge pointed \n\nout, the FTC found ʺnumerous consumer complaints in Briandiʹs personal office.ʺ  \n\nId; 2016 U.S. Dist. LEXIS 50589, at *40.  Briandi was thus aware of consumer \n\ncomplaints against the Corporate Defendants made to the New York Attorney \n\nGeneral, the Better Business Bureau, and the FTC, complaints that numbered \n\nwell into the hundreds. \n\n\n To be sure, Briandi testified, as noted above, that beginning in March 2013, \n\nhe neglected his managerial duties in favor of prayer and other spiritual pursuits.  \n\nBut he alleged that he began to neglect these managerial duties only after \n\npersonally executing the AOD, in which he agreed to take measures to address \n\nthe Corporate Defendantsʹ deceptive conduct; and he did so after executing an \n\naffidavit in which he represented that he had implemented procedures — \n\nincluding the hiring of a ʺcompliance officerʺ — to ensure that the Corporate \n\n 21 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nDefendants met the requirements of the FDCPA.  Therefore, when, according to \n\nBriandi, he retreated into spiritual pursuits at the expense of his managerial \n\nduties, he was not only on notice that the Corporate Defendants had been \n\nviolating the FDCPA; he had taken on a personal duty to correct the Corporate \n\nDefendantsʹ misbehavior.  Briandiʹs withdrawal under these circumstances is at \n\nleast evidence of reckless indifference to the Corporate Defendantsʹ deceptive \n\nconduct after the 2013 AOD.  See Primary Grp., 713 F. Appʹx at 807. \n\n\n We also agree with the district court that Briandi had knowledge of the \n\nCorporate Defendantsʹ unlawful conduct prior to the 2013 AOD.  Fed. Check \n\nProcessing, Inc., 2016 WL 5940485, at *1, 2016 U.S. Dist. LEXIS 141998 at *6 (ʺAt all \n\ntimes material to the Complaint . . . Defendant Mark Briandi . . . had actual or \n\nconstructive knowledge of the violative acts and practicesʺ (emphasis added)).  \n\nʺ[T]he degree of participation in business affairsʺ is a relevant factor in \n\ndetermining whether Briandi had knowledge of the Corporate Defendantsʹ \n\nwrongful actions.  Amy Travel, 875 F.2d at 574.  Here, that factor is dispositive.  \n\nBriandi served as the Corporate Defendantsʹ co‐director and general manager.  In \n\nperforming that role, Briandi was intimately involved with the unlawful \n\nactivities at issue: the collection calls.  The evidence before the magistrate judge \n\n\n 22 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nand district court established that Briandi maintained a personal desk in the call \n\ncenter itself, which, he conceded, he visited at least daily.  Adrian Fronczak, a \n\nformer employee of the Corporate Defendants, testified in a deposition that \n\nBriandi sat at the desk ʺprobably half the day.ʺ  Fronczak Dep. 44.  Fronczak also \n\ntestified that Briandi and Moses would take over calls if asked to do so by one of \n\nthe debt collectors.   Id. at 44‐45.  \n\n\n Far from demonstrating that the testimony was false, Briandi essentially \n\ncorroborated it in his own deposition.  There he admitted that he would take \n\nover from employees calls with hostile debtors, but said that he did so less \n\nfrequently after he signed the AOD and became more engaged in his religious \n\npractices.  According to his testimony, then, he was even more involved with the \n\ndebt collection calls prior to the 2013 AOD.  Indeed, Briandi made some of the \n\nmore offensive collection calls himself; they were mentioned in nine consumer \n\ncomplaints filed before the AOD was executed.  The magistrate judge and district \n\ncourt thus had ample evidence upon which to conclude that Brandi had \n\nknowledge of the Corporate Defendantsʹ violations both before and after he \n\nexecuted the AOD. \n\n\n\n\n 23 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n IV. FTC Disgorgement \n\n Finally, Briandi argues that the FTCʹs request that he be ordered to \n\ndisgorge $10,852,396, which was adopted by the magistrate judge and confirmed \n\nby the district court, was grossly excessive.  Briandi asserts that the FTCʹs \n\ncalculation was predicated on ʺapproximately 45 calls where it claimed that \n\nfraudulent claims were made,ʺ which is ʺa far cry from the courtʹs finding that \n\nthe entire operation was ʹpermeated with fraud.ʹʺ  Briandi Br. 30‐31 (quoting Fed. \n\nCheck Processing, Inc., 2016 WL 5956073, at *12, 2016 U.S. Dist. LEXIS 50589, at \n\n*48).  Therefore, Briandi contends, ʺthere was no basis to find that [he] should be \n\n[held] responsible for the entire amount of all the debt collected over [the] \n\napproximately four year period.ʺ  Briandi Br. 34.   \n\n\n Section 13(b) of the FTCA provides that ʺin proper cases the [FTC] may \n\nseek, and after proper proof, the court may issue, a permanent injunction.ʺ  15 \n\nU.S.C. § 53(b).  Although we have acknowledged that ʺthe provisionʹs express \n\ntext refers only to injunctive relief,ʺ we have also held that the ʺunqualified grant \n\nof statutory authority to issue an injunction under [S]ection 13(b) carries with it \n\nthe full range of equitable remedies, including the power to grant consumer \n\n\n\n\n 24 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nredress and compel disgorgement of profits.ʺ  FTC v. Bronson Partners, LLC, 654 \n\nF.3d 359, 365 (2d Cir. 2011) (internal quotation marks omitted).   \n\n\n We have adopted a ʺtwo‐step burden‐shifting framework for calculating \n\nequitable monetary relief.  That framework requires a court to look first to the \n\nFTC to ʹshow that its calculations reasonably approximated the amount of the \n\ndefendant[sʹ] unjust gainsʹ and then shift the burden ʹto the defendants to show \n\nthat those figures were inaccurate.ʹʺ  Id. at 364 (quoting Verity Intʹl, 443 F.3d at \n\n67).  \n\n\n To obtain equitable monetary relief, the FTC must also demonstrate that \n\nconsumers relied on the misrepresentations at issue.  Because ʺrequir[ing] proof \n\nof each individual consumerʹs reliance on a defendantʹs misrepresentations \n\nwould be an onerous task with the potential to frustrate the purpose of the FTCʹs \n\nstatutory mandate,ʺ we concluded in FTC v. BlueHippo Funding, LLC, 762 F.3d \n\n238, 244 (2d Cir. 2014), that ʺthe FTC is entitled to a presumption of consumer \n\nreliance upon showing that (1) the defendant made material misrepresentations \n\nor omissions that were of a kind usually relied upon by reasonable prudent \n\npersons; (2) the misrepresentations or omissions were widely disseminated; and \n\n\n\n\n 25 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n(3) consumers actually purchased the defendantsʹ products.ʺ  Id.  (alteration in \n\noriginal; internal quotation marks omitted). \n\n\n Here, in support of its motion for summary judgment, the FTC submitted \n\nmore than five hundred consumer complaints regarding the defendantsʹ debt \n\ncollection practices, aggressive collection telephone scripts located in fifteen of \n\nthe twenty‐six Corporate Defendantsʹ collection cubicles, and audio recordings of \n\ntwenty‐one of the twenty‐five employee debt‐collectors falsely telling consumers \n\nthat the employees were law enforcement personnel or ʺprocessors.ʺ  There is \n\nthus ample proof that the misrepresentations at issue were widely disseminated.   \n\n\n Briandi argues that those consumer complaints are inadmissible at the \n\nsummary judgment stage.  But he explicitly waived that challenge in the district \n\ncourt.  As the magistrate judge correctly noted: \n\n\n The  defendants  do  not  argue  that  the  FTCʹs  evidence  (e.g., \n telephone calls, scripts, consumer complaints) is inadmissible, \n and their failure to do so may be construed as a waiver of any \n such argument.  DeCintio v. Westchester Cnty. Med. Ctr., 821 F.2d \n 111, 114 (2d Cir. 1987).  \n\nFed. Check Processing, Inc., 2016 WL 5956073, at *2 n.6, 2016 U.S. Dist. LEXIS \n\n50589, at *8‐9 n.6.   \n\n\n\n\n 26 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Moreover, the case that Briandi relies on for the proposition that it is \n\ninappropriate to admit consumer complaints in support of a motion for \n\nsummary judgment, FTC v. Washington Data Resources, No. 8:09‐cv‐2309, 2011 WL \n\n2669661, 2011 U.S. Dist. LEXIS 72886 (M.D. Fla. July 7, 2011), was a district court \n\ndecision without precedential effect that rejected the use of consumer complaints \n\nas a substitute for trial testimony, rather than in summary judgment proceedings.   \n\n\n Finally, even excluding consideration of these complaints, it is clear from \n\nthe voluminous audio recordings and collection scripts submitted to the \n\nmagistrate judge by the FTC that the magistrate judge did not err in concluding – \n\nnor did the district court in adopting the conclusion – that the defendantsʹ \n\noperation was ʺpermeated with fraud.ʺ  Fed. Check Processing, Inc., 2016 WL \n\n5956073 at *12, 2016 U.S. Dist. LEXIS 50589, at *37. \n\n\n The FTC has thus shown that it was entitled to a presumption of reliance. \n\nAnd when the FTC establishes such a presumption, it can ʺuse[] the defendantsʹ \n\ngross receipts as a baseline for calculating damagesʺ at the first step of the \n\nburden‐shifting framework.  BlueHippo Funding, LLC, 762 F.3d at 245.  That is \n\nexactly what the FTC did here.  If the defendant wanted to attempt to refute the \n\nFTCʹs calculation, he had the burden to do so before the magistrate judge or the \n\n 27 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndistrict court.  See Verity Intʹl, 443 F.3d at 67 (noting that burden‐shifting \n\nframework requires ʺthe FTC to first show that its calculations reasonably \n\napproximated the amount of the defendantʹs unjust gains, after which the burden \n\nshifts to the defendants to show that those figures were inaccurateʺ (internal \n\nquotation marks omitted)).  The defendant chose not to submit any proof that the \n\ndebt corporations earned ʺall or some of their revenue through lawful means.ʺ  \n\nFed. Check Processing, Inc., 2016 WL 5956073, at *16, 2016 U.S. Dist. LEXIS 50589, \n\nat *48; see also id., 2016 U.S. Dist. LEXIS 50589, at *49 (ʺHad [the defendants \n\nchallenged the accuracy of the FTCʹs figures] a hearing may have been required \n\nto determine the amount of disgorgement.ʺ)  Accordingly, we conclude that it \n\nwas appropriate for the district court to award the disgorgement in the amount \n\nsought by the FTC. \n\n\n CONCLUSION \n We have considered the appellantsʹ remaining arguments on appeal and \n\nconclude that they are without merit.  For the foregoing reasons, we DISMISS \n\nMosesʹs appeal, and AFFIRM the remainder of the judgment of the district court. \n\n\n\n\n 28", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358071/", "author_raw": "SACK, Circuit Judge:"}]}
CABRANES
SACK
PARKER
1
{"CABRANES": ", Circuit", "SACK": ", Circuit", "PARKER": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580818/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Federal Trade Commission v. Federal Check Processing, Inc.\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-11\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n16‐3811‐(L) \nFederal Trade Commission v. Federal Check Processing, Inc. \n \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n August Term, 2018 \n (Argued: October 3, 2018   Decided: January 11, 2019) \n Docket No. 16‐3811‐cv, 16‐3805‐cv \n\n  \n  \n FEDERAL TRADE COMMISSION, \n Plaintiff‐Appellee, \n\n v. \n\n WILLIAM MOSES, individually and as an officer of one or more of the Corporate \n Defendants, FEDERAL CHECK PROCESSING INC., a New York corporation, MARK \n BRIANDI, individually and as an officer of one or more of the Corporate \n Defendants. \n Defendants‐Appellants, \n FEDERAL RECOVERIES, LLC, et al., \n Defendants. \n  \nBefore:  CABRANES, SACK, AND PARKER, Circuit Judges. \n\n The Federal Trade Commission brought this action in the United States \n\nDistrict Court for the Western District of New York alleging that the defendantsʹ \n\ndebt collection practices had violated several provisions of the Federal Trade \n\nCommission Act and the Federal Fair Debt Collection Practices Act.  The court \n\n(William M. Skretny, Judge) adopted a report and recommendation of Magistrate \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nJudge Michael J. Roemer recommending that summary judgment be granted in \n\nfavor of the FTC.   \n\n The defendant‐appellant William Moses submitted no brief prior to the \n\ndeadline for submission set by this Court.  We therefore dismiss his appeal \n\npursuant to Local Rule 31.2(d).  The defendant‐appellant Mark Briandi asserts \n\nthat there are genuine issues of material fact as to whether he had knowledge of \n\nthe businessesʹ practices at the heart of this action.  He also contends that the \n\ndisgorgement order against him is grossly excessive.  The evidence before the \n\ncourt on summary judgment established as a matter of law that Briandi had \n\ncontrol over the companiesʹ affairs, was aware of their illegal practices, and, \n\ntherefore, was liable for them.  We conclude that the disgorgement assessed \n\njointly and severally against all defendants, including Briandi and Moses, was in \n\nan appropriate amount because it was a reasonable approximation of the total \n\namounts received by the defendant companies from consumers as a result of \n\ntheir unlawful acts.  The judgment of the district court is therefore: \n\n AFFIRMED.     \n\n HERBERT L. GREENMAN, Lipsitz Green \n Scime Cambria, LLP, Buffalo, NY, for \n Defendant‐Appellant Mark Briandi. \n\n\n 2 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n MICHELE ARINGTON (David C. Shonka, Joel \n Marcus, Katherine M. Worthman, Colin A. \n Hector, on the brief), Federal Trade \n Commission, Washington, D.C., for \n Plaintiff‐Appellee.  \nSACK, Circuit Judge: \n\n The Federal Trade Commission (the ʺFTCʺ or the ʺgovernmentʺ) brought \n\nthis action against thirteen corporate entities (the ʺCorporate Defendantsʺ) and \n\ndefendants‐appellants Mark Briandi (ʺBriandiʺ) and William Moses (ʺMosesʺ) \n\nalleging that the defendants’ combined debt collection violated the Federal Trade \n\nCommission Act (ʺFTCAʺ), 15 U.S.C. § 45(a), and the Fair Debt Collection \n\nPractices Act (ʺFDCPAʺ), 15 U.S.C. § 1692 et seq.  The United States District Court \n\nfor the Western District of New York (William M. Skretny, Judge) adopted the \n\nreport and recommendation of Magistrate Judge Michael J. Roemer, \n\nrecommending the grant of summary judgment to the FTC on the grounds that \n\nthe evidence before the court had established as a matter of law that the \n\nCorporate Defendants violated the FTCA and FDCPA, and that Briandi and \n\nMoses were personally liable for the amount of money that the defendants had \n\nreceived because of the violations. \n\n\n\n\n 3 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Briandi and Moses appealed.  Moses did not file a brief, and, there being \n\nno valid excuse proffered therefor, we dismiss his appeal pursuant to our Local \n\nRule 31.2(d).1  \n\n Briandi does not contest the district court’s conclusion that the Corporate \n\nDefendants violated the FTCA and FDCPA.  He argues instead that the court \n\nerred by concluding that he is personally liable for the violations.  He also \n\ncontends that the district court erred by setting the measure of equitable \n\nmonetary relief as the total proceeds of the debt collection enterprise.  For the \n\nreasons set forth below, we agree with the district court on both issues, and, \n\ntherefore, affirm its judgment.   \n\n BACKGROUND \n\n General Factual Background2 \n\n In 2009, Briandi and Moses founded, and thereafter co‐owned and co‐\n\ndirected, the first of the Corporate Defendants, Federal Recoveries, LLC.  Over \n\n\n\n                                                            \n  Local Rule 31.2(d) provides:  ʺFailure to File.  The court may dismiss an appeal or \n 1\n\ntake other appropriate action for failure to timely file a brief or to meet a deadline under \nthis rule.ʺ \n 2 The following statement of facts is taken primarily from the FTCʹs ʺStatement of \n\nMaterial Facts as to Which There is no Genuine Issue to be Tried,ʺ which is largely \nundisputed, and, where relevant, evidence Briandi proffered in attempting to establish \nthe existence of a genuine dispute of material fact.   \n 4 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nthe next few years, Briandi or Moses incorporated twelve other Corporate \n\nDefendants, which were part of a single debt collection enterprise.  The \n\nCorporate Defendantsʹ business consisted largely of collecting payday loan \n\ndebts,3 which they bought from consumer‐debt creditors and compiled into debt \n\nportfolios.  These portfolios contained debtorsʹ names, addresses, and general \n\ninformation about the debts allegedly owed. \n\n\n At the Corporate Defendantsʹ behest, nearly all of their approximately \n\ntwenty‐five employee‐debt collectors would routinely contact debtors by \n\ntelephone and falsely identify themselves as ʺprocessors,ʺ ʺofficers,ʺ or \n\nʺinvestigatorsʺ from a ʺfraud unitʺ or ʺfraud division,ʺ then accuse debtors of \n\ncheck fraud or a related crime and threaten them with criminal prosecution if \n\nthey did not pay their debts.  On some occasions, collectors called friends, family \n\nmembers, employers, or co‐workers of debtors, telling them that the debtors \n\nowed a debt, had committed a crime in failing to pay it, and faced possible legal \n\n\n                                                            \n   ʺWhile there is no set definition of a payday loan, it is usually a short‐term, high cost \n 3\n\nloan, generally for $500 or less, that is typically due on [the borrowerʹs] next payday.ʺ  \nU.S. Consumer Financial Protection Bureau, ʺWhat is a payday loan?,ʺ available at \nhttps://www.consumerfinance.gov/ask‐cfpb/what‐is‐a‐payday‐loan‐en‐1567/ (last \nvisited December 16, 2018); see also Fed. Trade Commʹn v. Fed. Check Processing, Inc., \nNo. 14‐CV‐122‐WMS‐MJR, 2016 WL 5956073, at *2 n.5, 2016 U.S. Dist. LEXIS \n50589, at *7‐8 n.5 (W.D.N.Y. Apr. 13, 2016) (similar). \n 5 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nrepercussions.  When debtors or other interested parties sought further \n\ninformation about the debt, collectors typically refused to provide it. \n\n\n After receiving a litany of consumer complaints about these activities, the \n\nOffice of the New York State Attorney General began investigating the Corporate \n\nDefendantsʹ businesses.  On February 3, 2013, in an attempt to terminate the \n\ninvestigation, Briandi and Moses executed, on behalf of themselves and the \n\nrelevant Corporate Defendants, a written ʺAssurance of Discontinuanceʺ (the \n\nʺAODʺ) with the State Attorney General.  While not admitting fault, Briandi and \n\nMoses conceded in the AOD that the Corporate Defendants were subject to \n\nspecified federal and state laws, including the FDCPA.  Additionally, they \n\nagreed to dissolve some of the Corporate Defendants.  And they stated that they \n\nwould advise the New York State Attorney Generalʹs Office if any of the \n\nCorporate Defendants changed their principal place of business; if the individual \n\ndefendants incorporated a new corporation or business entity; or if any of the \n\nCorporate Defendants did business under a new name.  On May 8, 2013, Briandi \n\nand Moses also executed an affidavit in which they represented that they had \n\nimplemented procedures — including the hiring of a ʺcompliance officerʺ — to \n\nensure that the Corporate Defendants met the requirements of the FDCPA. \n\n\n 6 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Shortly after the AOD became effective, though, and without informing \n\nthe Attorney Generalʹs Office, Briandi and Moses incorporated new Corporate \n\nDefendants, some in other states.  And the Corporate Defendants continued to \n\nengage in the forsworn practices. \n\n\n Briandiʹs Corporate Responsibilities  \n\n\n Briandi was a co‐founder, co‐owner, co‐director, and general manager of \n\nall but perhaps one of the Corporate Defendants.  He maintained a personal \n\noffice within the Corporate Defendantsʹ East Amherst, New York, office and a \n\ndesk in the ʺcollection callʺ area from which dunning calls were made by the \n\ncompaniesʹ employees.  Briandi had signature authority with respect to the \n\ncompaniesʹ bank accounts, and in the more than four years between February 10, \n\n2010, and February 26, 2014, received approximately $1.3 million in \n\ncompensation from the Corporate Defendants. \n\n\n Briandiʹs principal responsibilities for the companies included signing \n\ntheir checks; managing the banking side of their businesses; handling personnel \n\nmatters, such as hiring and firing employees; maintaining the companiesʹ phone \n\nsystems and websites; receiving consumer payments; and — along with Moses, \n\nwho was in charge of collections — operating the entity, bearing the mellifluous \n\n 7 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nname ʺFlowing Streams,ʺ which purchased consumer debts.  Prior to 2013, \n\nBriandi would himself also occasionally make collection calls on behalf of the \n\nCorporate Defendants. \n\n\n After the instant litigation began, Briandi asserted in a deposition taken by \n\nFTC counsel on April 15, 2015, that, beginning in March of 2013, he had a \n\ndiminished involvement with the Corporate Defendants.  He testified that this \n\nresulted from his decision to become a pastor, which led to his spending much of \n\nhis work days praying in his office and taking online bible classes.  Although \n\nBriandi acknowledged that he continued to review corporate bank accounts from \n\ntime to time, speak to managers, and occasionally take ʺhostileʺ consumer calls, \n\nBriandi Dep., April 15, 2015, at 65‐66, 72; he denied having continued to visit his \n\ndesk on the collection floor more than ʺonceʺ or ʺtwiceʺ a day, id. at 134, 137, 143.   \n\n\n Procedural History  \n\n On February 24, 2014, the FTC filed a complaint against Briandi, Moses, \n\nand the Corporate Defendants in the United States District Court for the Western \n\nDistrict of New York.  It alleged two violations of Section 5(a) of the FTCA, 15 \n\nU.S.C. § 45(a) (ʺUnfair or Deceptive Acts or Practicesʺ), and four violations of the \n\nFDCPA, 15 U.S.C § 1692 (ʺDebt Collection Practicesʺ).  The FTC accused the \n\n 8 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndefendants of violating the statutes, despite having executed the AOD, by \n\noperating companies in which collectors continued to mask their identities, \n\nfalsely accuse consumers of various crimes, and refuse to reveal to debtors the \n\ncircumstances and nature of alleged debts.  The FTC also sought and received \n\nfrom the district court an ex parte temporary restraining order prohibiting the \n\ndefendants from using false representations or deceptive means to continue \n\ncollecting debts, freezing all of the defendantsʹ assets, and appointing a receiver \n\nto oversee the Corporate Defendants.  \n\n\n On June 17, 2014, Briandi and Moses asked the district court for one year in \n\nwhich to conduct discovery.  A magistrate judge granted their request but noted \n\nthat ʺno extensions of this order will be entertained.ʺ  Dkt. No. 67. \n\n\n Meanwhile, the FTC subpoenaed and received copies of a variety of scripts \n\nused by the Corporate Defendantsʹ employees to make demand telephone calls, \n\nrecordings of telephone calls between various collectors and consumers, and \n\nmany consumer complaints and declarations detailing and challenging the \n\ncompaniesʹ practices.  The FTC also submitted interrogatories to the defendants \n\nand took oral depositions of Briandi and Moses.  For their parts, though, Briandi, \n\nMoses, and the Corporate Defendants engaged in no discovery.  And Briandi \n\n 9 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nfailed to answer interrogatories propounded by the FTC until after the discovery \n\ndeadline had passed, and then only as part of his attempt to oppose the FTCʹs \n\nmotion for summary judgment. \n\n\n The FTC moved for summary judgment on August 27, 2015.  The motion \n\nincluded a request for $10,852,396 in monetary relief, for which, the FTC \n\nasserted, all of the defendants, include Briandi and Moses, should be jointly and \n\nseverally liable.  That figure was based on ʺthe gross total of consumer funds \n\ndeposited by merchant processorsʺ found ʺin the [d]efendantsʹ settlement \n\naccounts.ʺ  Second Suppl. Decl. of FTC Investigator Michael B. Goldstein ¶ 26 \n\n(July 24, 2015). \n\n\n Briandi did not dispute the allegations that the Corporate Defendants \n\nengaged in wrongdoing.  He denied, however, that he could be held individually \n\nliable for the Corporate Defendantsʹ actions.  He based that argument largely on \n\nhis contention that he did not control the Corporate Defendants, did not \n\nparticipate in their activities, and lacked any knowledge of their alleged \n\nwrongdoing.  Briandi also asserted that the governmentʹs requested relief vastly \n\nexceeded the Corporate Defendantsʹ unlawful gains. \n\n\n The District Courtʹs Decision \n\n 10 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n On April 13, 2016, Michael J. Roemer, the magistrate judge to whom the \n\nmatter had by then been referred by the district court ʺfor all pre‐trial matters, \n\nincluding preparation of a report and recommendation on dispositive motions,ʺ \n\nissued a report and recommendation concluding that the FTCʹs motion for \n\nsummary judgment should be granted.  FTC v. Fed. Check Processing, Inc., No. 14‐\n\nCV‐122‐WMS‐MJR, 2016 WL 5956073, at *1, 2016 U.S. Dist. LEXIS 50589, at *2 \n\n(W.D.N.Y. Apr. 13, 2016), adopted, No. 14‐CV‐122S, 2016 WL 5940485, 2016 U.S. \n\nDist. LEXIS 141998 (W.D.N.Y. Oct. 13, 2016).  First, the magistrate judge \n\nconcluded that the FTC had proved that Briandi both had ʺthe authority to \n\ncontrol the [C]orporate [D]efendants and knew of their wrongdoing.ʺ  Id. at *14, \n\n2016 U.S. Dist. LEXIS 50589 at *41‐42.  According to the magistrate judge, even if \n\nBriandi somehow lacked detailed knowledge of the Corporate Defendantsʹ illicit \n\ncollection practices, he could not plead ignorance after expressly agreeing to the \n\n2013 AOD.  Id. at *13, 2016 U.S. Dist. LEXIS 50589 at *40.  The existence of the \n\nAOD executed by Briandi established that he had notice of the Corporate \n\nDefendantsʹ illicit collection activities and was required to ensure that they \n\nfollowed the FTCA and the FDCPA.  Id., 2016 U.S. Dist. LEXIS 50589 at *40. \n\n\n\n\n 11 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Second, the magistrate judge concluded that the FTCʹs disgorgement \n\nrequest ʺreasonably approximate[d] the [C]orporate [D]efendantsʹ unjust gains.ʺ  \n\nId. at *16, 2016 U.S. Dist. LEXIS 50589 at *48.  As the magistrate judge observed, \n\nthis amount was based on bank account data compiled by the FTC showing that \n\nʺbetween May 2010 and March 2014 the [C]orporate [D]efendants collected \n\n$10,852,396 from consumers.ʺ  Id., 2016 U.S. Dist. LEXIS 50589 at *48.  The FTC \n\nhad also demonstrated that ʺthe defendantsʹ misrepresentations were widely \n\ndisseminated,ʺ and that their operation was ʺpermeated with fraud.ʺ  Id., 2016 \n\nU.S. Dist. LEXIS 50589 at *48.   Finally, the magistrate judge noted that the \n\ndefendant had failed to produce any evidence that would serve to dispute the \n\nrecommended penalty.  Id., 2016 U.S. Dist. LEXIS 50589 at *48. \n\n\n On October 12, 2016, the district court adopted Magistrate Judge Roemerʹs \n\nreport and recommendation in its entirety and entered judgment in the \n\ngovernmentʹs favor.  Fed. Trade Commʹn v. Fed. Check Processing, Inc., No. 14‐CV‐\n\n122S, 2016 WL 5940485, at *1, 2016 U.S. Dist. LEXIS 141998, at *4 (W.D.N.Y. Oct. \n\n13, 2016). \n\n\n\n\n 12 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n DISCUSSION \n\n Briandi makes three principal arguments on appeal.  First, he contends \n\nthat he should have been given time to conduct discovery.  Second, he argues, \n\nbased on the information contained in his deposition, that there were material \n\nfacts at issue as to whether he could be held individually liable for the actions of \n\nthe Corporate Defendants.  He contends that these factual issues rendered \n\nsummary judgment for the FTC improper.  Finally, he asserts that the \n\ndisgorgement amount adopted by the district court was grossly excessive.  For \n\nthe reasons that follow, we disagree with each of these contentions. \n\n\n I. Standard of Review \n\n\n A district courtʹs decision on a partyʹs request for ʺmore time to conduct \n\ndiscovery . . . is subject to reversal only if [the district court] abused its \n\ndiscretion.ʺ  Paddington Partners v. Bouchard, 34 F.3d 1132, 1137 (2d Cir. 1994).   \n\n\n We review the ʺdistrict courtʹs decision to grant summary judgment de \n\nnovo, resolving all ambiguities and drawing all permissible factual inferences in \n\nfavor of the party against whom summary judgment is sought.ʺ  Burg v. Gosselin, \n\n591 F.3d 95, 97 (2d Cir. 2010) (internal quotation mark omitted).  Summary \n\njudgment is appropriate only when ʺthe movant shows that there is no genuine \n\n 13 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndispute as to any material fact and the movant is entitled to judgment as a matter \n\nof law.ʺ  Fed. R. Civ. P. 56(a).  However, ʺa party may not rely on mere \n\nspeculation or conjecture as to the true nature of the facts to overcome a motion \n\nfor summary judgment.ʺ  Fletcher v. Atex, Inc., 68 F.3d 1451, 1456 (2d Cir. 1995) \n\n(internal quotation marks omitted).  ʺ[C]onclusory allegations or denialsʺ \n\ntherefore ʺare not evidence and cannot by themselves create a genuine issue of \n\nmaterial fact where none would otherwise exist.ʺ  Id. (internal quotation marks \n\nomitted).   \n\n\n II. Additional Discovery \n\n Briandi contends that the district court wrongly denied an extension to the \n\none‐year discovery period already provided.  But Briandi has waived this \n\nargument.  Federal Rule of Civil Procedure 56(d) provides that a party opposing \n\nsummary judgment based on incomplete discovery must file an affidavit \n\nexplaining why such discovery is necessary.  See id. (ʺIf a nonmovant shows by \n\naffidavit or declaration that, for specified reasons, it cannot present facts essential \n\nto justify its opposition, the court may . . . allow time to obtain affidavits or \n\ndeclarations or to take discovery.ʺ)  Briandi submitted no such affidavit to the \n\nmagistrate judge or the district court; nor does he contend otherwise. \n\n\n 14 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Also, it was Briandi and Moses who asked for the approximately one‐year \n\ndiscovery period, and then chose, for unstated reasons, not to conduct any \n\ndiscovery at all during that period.  Briandi now asserts that he did not \n\nunderstand the ʺcircumstances of [his] position.ʺ  Briandi Br. 22.  However, he \n\nidentifies no standard upon which to judge whether or not that is the case. Nor \n\ndoes he explain how the ʺcircumstances of his positionʺ were unclear or \n\nconfusing, or provide any authority for the proposition that, if they were, he was \n\ntherefore entitled to an extension on the lengthy period the court provided for \n\ndiscovery. \n\n\n III. Briandiʹs Personal Liability \n\n Briandi argues that the district court erred in granting summary judgment \n\nagainst him because genuine disputes of material fact exist regarding his control \n\nof the debt collection agencies, and therefore his personal liability for their \n\nactions.  We disagree.  In light of the undisputed evidence regarding the \n\nCorporate Defendants’ operations and Briandi’s relationship with them, we \n\nconclude that he had both sufficient authority over the Corporate Defendants, \n\nand knowledge of their practices, to be held individually liable for their \n\nmisconduct as a matter of law. \n\n\n 15 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n A.  Standard for Individual Liability Under the FTCA and FDCPA \n\n\n Section 5(a)(1) of the FTCA, 15 U.S.C. § 45(a)(1), prohibits ʺ[u]nfair or \n\ndeceptive acts or practices in or affecting commerce.ʺ  The FTC must show three \n\nelements to prove a deceptive act or practice in violation of § 5(a)(1): ʺ[1] a \n\nrepresentation, omission, or practice, that [2] is likely to mislead consumers \n\nacting reasonably under the circumstances, and [3], the representation, omission, \n\nor practice is material.ʺ FTC v. Verity Intʹl, Ltd., 443 F.3d 48, 63 (2d Cir. 2006) \n\n(brackets in the original; internal quotation marks omitted).  ʺThe deception need \n\nnot be made with intent to deceive; it is enough that the representations or \n\npractices were likely to mislead consumers acting reasonably.ʺ  Id.  \n\n\n An individual may be held liable under the FTCA for a corporation’s \n\ndeceptive acts or practices ʺif, with knowledge of the deceptive nature of the \n\nscheme, he either ʹparticipate[s] directly in the practices or acts or ha[s] authority \n\nto control them.ʹʺ  FTC v. LeadClick Media, LLC, 838 F.3d 158, 169 (2d Cir. 2016) \n\n(quoting FTC v. Amy Travel Serv., Inc., 875 F.2d 564, 573 (7th Cir. 1989)).4   To \n\nprevail on the issue, the FTC must therefore establish that \n\n\n                                                            \n  The First, Fourth, Seventh, Ninth, Tenth, and Eleventh Circuits have also adopted \n 4\n\nthis standard.  See FTC v. Direct Mktg. Concepts, Inc., 624 F.3d 1, 12 (1st Cir. 2010); FTC v. \nRoss, 743 F.3d 886, 892 (4th Cir. 2014); FTC v. Amy Travel Serv., Inc., 875 F.2d 564, 573‐74 \n 16 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n the corporate practices were misrepresentations or \n omissions of a kind usually relied on by reasonably \n prudent persons and that consumer injury resulted.  \n Once corporate liability is established, the FTC must \n show that the individual defendants participated \n directly in the practices or acts or had authority to \n control them.  Authority to control the company can be \n evidenced by active involvement in business affairs and \n the making of corporate policy, including assuming the \n duties of a corporate officer.   \n\nAmy Travel, 875 F.2d at 573 (citations omitted).  ʺThe FTC is [also] required to \n\nestablish the defendants had or should have had knowledge or awareness of the \n\nmisrepresentations.ʺ  Id. at 574 (citation omitted). \n\n The FTC need not establish in this context that the defendant had actual \n\nand explicit knowledge of the particular deception at issue.  We agree with our \n\nsister circuits that ʺknowledge ʹmay be established by showing that the \n\nindividual [defendant] had actual knowledge of the deceptive conduct, [or] was \n\nrecklessly indifferent to its deceptiveness, or had an awareness of a high \n\nprobability of deceptiveness and intentionally avoided learning of the truth.ʹʺ  \n\nFTC v. Primary Grp., Inc., 713 F. Appʹx 805, 807 (11th Cir. 2017) (per curiam) \n\n(quoting FTC v. Ross, 743 F.3d 886, 892 (4th Cir. 2014)); accord FTC v. World Media \n\n                                                            \n(7th Cir. 1989);  FTC v. Grant Connect, LLC, 763 F.3d 1094, 1101 (9th Cir. 2014); FTC v. \nFreecom Commcʹns, Inc., 401 F.3d 1192, 1204, 1207 (10th Cir. 2005); FTC v. IAB Mktg. \nAssocs., LP, 746 F.3d 1228, 1233 (11th Cir. 2014). \n 17 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nBrokers, 415 F.3d 758, 764 (7th Cir. 2005).5  And we agree with the Eleventh \n\nCircuit that ʺthis standard correctly describes the breadth of individual liability \n\nunder the FTC[A].ʺ  Primary Grp., 713 F. App’x at 807.  Imposing a more rigid \n\nknowledge requirement ʺwould be inconsistent with the policies behind the \n\nFTCA and place too great a burden on the FTC.ʺ  Amy Travel, 875 F.2d at 574. \n\n Finally on this score, we conclude that the same standard applies when the \n\nFTC brings an action to enforce the FDCPA.  ʺ[V]iolations of the FDCPA are \n\ndeemed to be unfair or deceptive acts or practices under the [FTCA].ʺ  Jerman v. \n\nCarlisle, McNellie, Rini, Kramer & Ulrich LPA, 559 U.S. 573, 577, (2010); see also 15 \n\nU.S.C. § 1692l(a) (ʺ[A] violation of [the FDCPA] shall be deemed an unfair or \n\ndeceptive act or practice in violation ofʺ the FTCA and is subject to enforcement \n\nʺin the same manner as if the violation had been a violation of a[n] [FTC] trade \n\nregulation rule.ʺ)  The FTC, then, is enforcing the FDCPA pursuant to its \n\nauthority under the FTCA.  And because the FTC can enforce compliance with \n\nthe FDCPA only by employing the FTCA, and ʺin the same manner as a \n\nviolationʺ of the FTCA, 15 U.S.C. § 1692l(a), it follows, we conclude, that the \n\nFTCA individual liability standard applies. \n\n                                                            \n  Under Eleventh Circuit Local Rule 36‐2, “[u]npublished opinions are not considered \n 5\n\nbinding precedent, but they may be cited as persuasive authority,” as we do here. \n 18 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n B.  Briandiʹs Authority to Control the Corporate Defendants \n\n\n Briandi was a founder of all but perhaps one of the Corporate Defendants, \n\nheld a 50 percent ownership stake in them, had signatory authority over their \n\nbank accounts, and served as their co‐director and general manager.  In these \n\nvarious roles, Briandi had the authority to control the Corporate Defendants’ \n\ndeceptive actions.  For example, in his deposition, Briandi admitted to having the \n\npower to hire and reprimand employees including those responsible for the \n\nCorporate Defendantsʹ violations of the FTCA and FDCPA. \n\n\n Briandi retained this authority after signing the AOD.  From March 2013 \n\nuntil the time of the FTCʹs complaint, he remained a co‐owner, co‐director, and \n\ngeneral manager of the Corporate Defendants, fielded hostile calls from \n\nconsumers, continued to review the Corporate Defendantsʹ financial activities, \n\nand, once or twice a day, would visit the collection floor, where he would speak \n\nto other managers about the corporationsʹ business. \n\n\n Briandi’s deposition testimony that he contends was to the contrary was \n\ndirected to the question of whether he exercised authority to control the Corporate \n\nDefendantsʹ conduct, not whether he possessed authority to control it, which is the \n\ndispositive issue.  Viewed in light of all the evidence properly before the district \n\n 19 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ncourt on the motion for summary judgment, then, Briandiʹs denial of \n\ninvolvement in, rather than the authority to control the actions of, the Corporate \n\nDefendants did not create a dispute of material fact requiring the district court to \n\ndeny the motion. \n\n\n C.  Briandiʹs Knowledge of the Corporate Defendantsʹ Activities \n\n\n The defendants were ordered to disgorge $10,852,396, an amount equal to \n\nall profits ʺresulting from [d]efendantsʹ unlawful acts or practices,ʺ Fed. Check \n\nProcessing, Inc., 2016 WL 5940485, at *4, 2016 U.S. Dist. LEXIS 50589, at *40 \n\n(adopting magistrate judgeʹs April 13 ,2016 report and recommendation).  This \n\namount was calculated by the magistrate judge based on the Corporate \n\nDefendantsʹ bank account data between May 2010 and March 2014.  The FTC \n\ntherefore was required to establish that Briandi had knowledge of the Corporate \n\nDefendantsʹ wrongdoing during that entire period — both prior to and after his \n\nexecution of the 2013 AOD — to hold him individually liable for the unlawful \n\nreceipts of the Corporate Defendants during the same period.   We conclude that \n\nthe FTC did so. \n\n\n We agree with the magistrate judgeʹs report and recommendation that \n\nafter the AOD was executed by Briandi in 2013, Briandi was at least aware ʺof a \n\n 20 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nhigh probability of fraud and intentionally avoided learning the truth.ʺ  Fed. \n\nCheck Processing, Inc., 2016 WL 5956073, at *13, 2016 U.S. Dist. LEXIS 50589, at *36.  \n\nThe AOD explicitly accused the Corporate Defendants of violating the FTC and \n\nFDCPA.   \n\n\n After executing the document, Briandi nonetheless continued to oversee \n\nthe Corporate Defendantsʹ collection activities.  As the magistrate judge pointed \n\nout, the FTC found ʺnumerous consumer complaints in Briandiʹs personal office.ʺ  \n\nId; 2016 U.S. Dist. LEXIS 50589, at *40.  Briandi was thus aware of consumer \n\ncomplaints against the Corporate Defendants made to the New York Attorney \n\nGeneral, the Better Business Bureau, and the FTC, complaints that numbered \n\nwell into the hundreds. \n\n\n To be sure, Briandi testified, as noted above, that beginning in March 2013, \n\nhe neglected his managerial duties in favor of prayer and other spiritual pursuits.  \n\nBut he alleged that he began to neglect these managerial duties only after \n\npersonally executing the AOD, in which he agreed to take measures to address \n\nthe Corporate Defendantsʹ deceptive conduct; and he did so after executing an \n\naffidavit in which he represented that he had implemented procedures — \n\nincluding the hiring of a ʺcompliance officerʺ — to ensure that the Corporate \n\n 21 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nDefendants met the requirements of the FDCPA.  Therefore, when, according to \n\nBriandi, he retreated into spiritual pursuits at the expense of his managerial \n\nduties, he was not only on notice that the Corporate Defendants had been \n\nviolating the FDCPA; he had taken on a personal duty to correct the Corporate \n\nDefendantsʹ misbehavior.  Briandiʹs withdrawal under these circumstances is at \n\nleast evidence of reckless indifference to the Corporate Defendantsʹ deceptive \n\nconduct after the 2013 AOD.  See Primary Grp., 713 F. Appʹx at 807. \n\n\n We also agree with the district court that Briandi had knowledge of the \n\nCorporate Defendantsʹ unlawful conduct prior to the 2013 AOD.  Fed. Check \n\nProcessing, Inc., 2016 WL 5940485, at *1, 2016 U.S. Dist. LEXIS 141998 at *6 (ʺAt all \n\ntimes material to the Complaint . . . Defendant Mark Briandi . . . had actual or \n\nconstructive knowledge of the violative acts and practicesʺ (emphasis added)).  \n\nʺ[T]he degree of participation in business affairsʺ is a relevant factor in \n\ndetermining whether Briandi had knowledge of the Corporate Defendantsʹ \n\nwrongful actions.  Amy Travel, 875 F.2d at 574.  Here, that factor is dispositive.  \n\nBriandi served as the Corporate Defendantsʹ co‐director and general manager.  In \n\nperforming that role, Briandi was intimately involved with the unlawful \n\nactivities at issue: the collection calls.  The evidence before the magistrate judge \n\n\n 22 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nand district court established that Briandi maintained a personal desk in the call \n\ncenter itself, which, he conceded, he visited at least daily.  Adrian Fronczak, a \n\nformer employee of the Corporate Defendants, testified in a deposition that \n\nBriandi sat at the desk ʺprobably half the day.ʺ  Fronczak Dep. 44.  Fronczak also \n\ntestified that Briandi and Moses would take over calls if asked to do so by one of \n\nthe debt collectors.   Id. at 44‐45.  \n\n\n Far from demonstrating that the testimony was false, Briandi essentially \n\ncorroborated it in his own deposition.  There he admitted that he would take \n\nover from employees calls with hostile debtors, but said that he did so less \n\nfrequently after he signed the AOD and became more engaged in his religious \n\npractices.  According to his testimony, then, he was even more involved with the \n\ndebt collection calls prior to the 2013 AOD.  Indeed, Briandi made some of the \n\nmore offensive collection calls himself; they were mentioned in nine consumer \n\ncomplaints filed before the AOD was executed.  The magistrate judge and district \n\ncourt thus had ample evidence upon which to conclude that Brandi had \n\nknowledge of the Corporate Defendantsʹ violations both before and after he \n\nexecuted the AOD. \n\n\n\n\n 23 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n IV. FTC Disgorgement \n\n Finally, Briandi argues that the FTCʹs request that he be ordered to \n\ndisgorge $10,852,396, which was adopted by the magistrate judge and confirmed \n\nby the district court, was grossly excessive.  Briandi asserts that the FTCʹs \n\ncalculation was predicated on ʺapproximately 45 calls where it claimed that \n\nfraudulent claims were made,ʺ which is ʺa far cry from the courtʹs finding that \n\nthe entire operation was ʹpermeated with fraud.ʹʺ  Briandi Br. 30‐31 (quoting Fed. \n\nCheck Processing, Inc., 2016 WL 5956073, at *12, 2016 U.S. Dist. LEXIS 50589, at \n\n*48).  Therefore, Briandi contends, ʺthere was no basis to find that [he] should be \n\n[held] responsible for the entire amount of all the debt collected over [the] \n\napproximately four year period.ʺ  Briandi Br. 34.   \n\n\n Section 13(b) of the FTCA provides that ʺin proper cases the [FTC] may \n\nseek, and after proper proof, the court may issue, a permanent injunction.ʺ  15 \n\nU.S.C. § 53(b).  Although we have acknowledged that ʺthe provisionʹs express \n\ntext refers only to injunctive relief,ʺ we have also held that the ʺunqualified grant \n\nof statutory authority to issue an injunction under [S]ection 13(b) carries with it \n\nthe full range of equitable remedies, including the power to grant consumer \n\n\n\n\n 24 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \nredress and compel disgorgement of profits.ʺ  FTC v. Bronson Partners, LLC, 654 \n\nF.3d 359, 365 (2d Cir. 2011) (internal quotation marks omitted).   \n\n\n We have adopted a ʺtwo‐step burden‐shifting framework for calculating \n\nequitable monetary relief.  That framework requires a court to look first to the \n\nFTC to ʹshow that its calculations reasonably approximated the amount of the \n\ndefendant[sʹ] unjust gainsʹ and then shift the burden ʹto the defendants to show \n\nthat those figures were inaccurate.ʹʺ  Id. at 364 (quoting Verity Intʹl, 443 F.3d at \n\n67).  \n\n\n To obtain equitable monetary relief, the FTC must also demonstrate that \n\nconsumers relied on the misrepresentations at issue.  Because ʺrequir[ing] proof \n\nof each individual consumerʹs reliance on a defendantʹs misrepresentations \n\nwould be an onerous task with the potential to frustrate the purpose of the FTCʹs \n\nstatutory mandate,ʺ we concluded in FTC v. BlueHippo Funding, LLC, 762 F.3d \n\n238, 244 (2d Cir. 2014), that ʺthe FTC is entitled to a presumption of consumer \n\nreliance upon showing that (1) the defendant made material misrepresentations \n\nor omissions that were of a kind usually relied upon by reasonable prudent \n\npersons; (2) the misrepresentations or omissions were widely disseminated; and \n\n\n\n\n 25 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n(3) consumers actually purchased the defendantsʹ products.ʺ  Id.  (alteration in \n\noriginal; internal quotation marks omitted). \n\n\n Here, in support of its motion for summary judgment, the FTC submitted \n\nmore than five hundred consumer complaints regarding the defendantsʹ debt \n\ncollection practices, aggressive collection telephone scripts located in fifteen of \n\nthe twenty‐six Corporate Defendantsʹ collection cubicles, and audio recordings of \n\ntwenty‐one of the twenty‐five employee debt‐collectors falsely telling consumers \n\nthat the employees were law enforcement personnel or ʺprocessors.ʺ  There is \n\nthus ample proof that the misrepresentations at issue were widely disseminated.   \n\n\n Briandi argues that those consumer complaints are inadmissible at the \n\nsummary judgment stage.  But he explicitly waived that challenge in the district \n\ncourt.  As the magistrate judge correctly noted: \n\n\n The  defendants  do  not  argue  that  the  FTCʹs  evidence  (e.g., \n telephone calls, scripts, consumer complaints) is inadmissible, \n and their failure to do so may be construed as a waiver of any \n such argument.  DeCintio v. Westchester Cnty. Med. Ctr., 821 F.2d \n 111, 114 (2d Cir. 1987).  \n\nFed. Check Processing, Inc., 2016 WL 5956073, at *2 n.6, 2016 U.S. Dist. LEXIS \n\n50589, at *8‐9 n.6.   \n\n\n\n\n 26 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \n Moreover, the case that Briandi relies on for the proposition that it is \n\ninappropriate to admit consumer complaints in support of a motion for \n\nsummary judgment, FTC v. Washington Data Resources, No. 8:09‐cv‐2309, 2011 WL \n\n2669661, 2011 U.S. Dist. LEXIS 72886 (M.D. Fla. July 7, 2011), was a district court \n\ndecision without precedential effect that rejected the use of consumer complaints \n\nas a substitute for trial testimony, rather than in summary judgment proceedings.   \n\n\n Finally, even excluding consideration of these complaints, it is clear from \n\nthe voluminous audio recordings and collection scripts submitted to the \n\nmagistrate judge by the FTC that the magistrate judge did not err in concluding – \n\nnor did the district court in adopting the conclusion – that the defendantsʹ \n\noperation was ʺpermeated with fraud.ʺ  Fed. Check Processing, Inc., 2016 WL \n\n5956073 at *12, 2016 U.S. Dist. LEXIS 50589, at *37. \n\n\n The FTC has thus shown that it was entitled to a presumption of reliance. \n\nAnd when the FTC establishes such a presumption, it can ʺuse[] the defendantsʹ \n\ngross receipts as a baseline for calculating damagesʺ at the first step of the \n\nburden‐shifting framework.  BlueHippo Funding, LLC, 762 F.3d at 245.  That is \n\nexactly what the FTC did here.  If the defendant wanted to attempt to refute the \n\nFTCʹs calculation, he had the burden to do so before the magistrate judge or the \n\n 27 \n \n\f 16‐3811‐cv, 16‐3805‐cv \n Federal Trade Commission v. Federal Check Processing, Inc, et al. \n    \ndistrict court.  See Verity Intʹl, 443 F.3d at 67 (noting that burden‐shifting \n\nframework requires ʺthe FTC to first show that its calculations reasonably \n\napproximated the amount of the defendantʹs unjust gains, after which the burden \n\nshifts to the defendants to show that those figures were inaccurateʺ (internal \n\nquotation marks omitted)).  The defendant chose not to submit any proof that the \n\ndebt corporations earned ʺall or some of their revenue through lawful means.ʺ  \n\nFed. Check Processing, Inc., 2016 WL 5956073, at *16, 2016 U.S. Dist. LEXIS 50589, \n\nat *48; see also id., 2016 U.S. Dist. LEXIS 50589, at *49 (ʺHad [the defendants \n\nchallenged the accuracy of the FTCʹs figures] a hearing may have been required \n\nto determine the amount of disgorgement.ʺ)  Accordingly, we conclude that it \n\nwas appropriate for the district court to award the disgorgement in the amount \n\nsought by the FTC. \n\n\n CONCLUSION \n We have considered the appellantsʹ remaining arguments on appeal and \n\nconclude that they are without merit.  For the foregoing reasons, we DISMISS \n\nMosesʹs appeal, and AFFIRM the remainder of the judgment of the district court. \n\n\n\n\n 28\n[END_CASE]", "role": "user" } ]
8,443,840
United States v. Jarret EAGLIN, aka Jarret L. Eaglin
United States v. Eaglin
2019-01-11
Docket No. 17-1224-cr; August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Cabranes, Carney, Vilardo", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415266/", "author_raw": ""}]}
CABRANES
CARNEY
VILARDO
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443840/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Jarret EAGLIN, aka Jarret L. Eaglin\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-11\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
8,443,843
FEDERAL TRADE COMMISSION v. William MOSES, Individually and as an Officer of One or More of the Corporate Federal Check Processing Inc., a New York Corporation, Mark Briandi, Individually and as an Officer of One or More of the Corporate Federal Recoveries, LLC
Fed. Trade Comm'n v. Moses
2019-01-11
Docket No. 16-3811-cv; 16-3805-cv; August Term, 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Cabranes, Parker, Sack", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415269/", "author_raw": ""}]}
CABRANES
PARKER
SACK
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443843/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: FEDERAL TRADE COMMISSION v. William MOSES, Individually and as an Officer of One or More of the Corporate Federal Check Processing Inc., a New York Corporation, Mark Briandi, Individually and as an Officer of One or More of the Corporate Federal Recoveries, LLC\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-11\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,581,195
Frommert v. Conkright
2019-01-14
17-114-cv(L)
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: 28 29 KEARSE, CABRANES, and LOHIER, Circuit Judges.", "parties": "", "opinions": [{"author": "LOHIER, Circuit Judge:", "type": "010combined", "text": "17‐114‐cv(L) \n Frommert v. Conkright \n 1  UNITED STATES COURT OF APPEALS \n 2  FOR THE SECOND CIRCUIT \n 3   \n 4  August Term, 2017 \n 5   \n 6  (Argued: April 18, 2018  Decided: January 14, 2019 ) \n 7   \n 8  Docket Nos. 17‐114‐cv(L), 17‐738‐cv(CON) \n 9   \n10  _____________________________________ \n11   \n12  PAUL J. FROMMERT, DONALD S. FOOTE, THOMAS I. BARNES, RONALD \n13  J. CAMPBELL, FRANK D. COMMESSO, WILLIAM F. COONS, JAMES D. \n14  GAGNIER, BRIAN L. GAITA, WILLIAM J. LADUE, GERALD A. \n15  LEONARDO, JR., FRANK MAWDESLEY, HAROLD S. MITCHELL, \n16  WALTER J. PETROFF, RICHARD C. SPRING, PATRICIA M. JOHNSON, F. \n17  PATRICIA M. TOBIN, NANCY A. REVELLA, ANATOLI G. PUSCHKIN, \n18  WILLIAM R. PLUMMER, MICHAEL J. MCCOY, ALAN H. CLAIR, LARRY J. \n19  GALLAGHER, NAPOLEON B. BARBOSA, ALEXANDRA SPEARMAN \n20  HARRICK, JANIS A. EDELMAN, PATRICIA H. JOHNSTON, KENNETH P. \n21  PARNETT, JOYCE D. CATHCART, FLOYD SWAIM, JULIE A. MCMILLIAN, \n22  DENNIS E. BAINES, RUBY JEAN MURPHY, MATTHEW D. ALFIERI, \n23  IRSHAD QURESHI, RICHARD C. CRATER, GAIL J. LEVY, JOHN A. \n24  WILLIAMS, CRYSTAL THORTON, CHARLES R. DRANNBAUER, \n25  WILLIAM M. BURRITT, JANICE ROSS HEILER, JOSEPH MCNEIL, \n26  THOMAS F. MCGEE, VINCENT G. JOHNSON, F. COLT HITCHCOCK, \n27  RONNIE TABAK, MARTHA LEE TAYLOR, KATHY FAY THOMPSON, \n28  MARY BETH ALLEN, CRAIG SPENCER, LINDA S. BOURQUE, THOMAS \n29  MICHAEL VASTA, FRANK C. DARLING, CLARK C. DINGMAN, CAROL \n30  E. GANNON, JOSEPH E. WRIGHT, DAVID M. ROHAN, DAVID B. \n31  RUDDOCK, CHARLES HOBBS, CHARLES ZABINSKI, CHARLES J. \n32  MADDALOZZO, JOYCE M. PRUETT, WILLIAM A. CRAVEN, MAUREEN \n33  A. LOUGHLIN JONES, KENNETH W. PIETROWSKI, BONNIE COHEN, \n34  LAWRENCE R. HOLLAND, GAIL A. NASMAN, STEVEN D. BARLEY, \n35  DONNA S. LIPARI, ANDREW C. MATTELIANO, MICHAEL HORROCKS, \n36  CANDICE J. WHITE, KATHLEEN E. HUNTER, JOHN L. CRISAFULLI, \n\f 1  DEBORAH J. DAVIS, BRENDA H. MCCONNELL, KATHLEEN A. BOWEN, \n 2  ROBERT P. CARANDDO, TERENCE J. KURTZ, WILLIAM J. CHESLOCK, \n 3  THOMAS E. DALTON, LYNN BARNSDALE, BRUCE D. CRAIG, GARY P. \n 4  HARDIN, CLAUDETTE M. LONG, DALE PLATTETER, MARY ANN \n 5  SERGEANT, MOLLY WHITE KEHOE, DAVID K. YOUNG, LESLIE ANN \n 6  WUNSCH, RICHARD J. GLIKIN, EUGENE H. UPDYKE, MICHAEL R. \n 7  BENSON, ALVIN M. ADAMS, RONNIE KOLNIAK, JAMES J. FARRELL, \n 8  ROBERT L. BRACKHAHN, BENJAMIN C. ROTH, CARMEN J. SOFIA, \n 9  KATHLEEN W. LEVEA, FREDERICK SCACCHITTI, PAUL DEFINA, JAMES \n10  G. WALLS, \n11   \n12  Plaintiffs‐Appellants, \n13   \n14  v. \n15   \n16  SALLY L. CONKRIGHT, XEROX CORPORATION PENSION PLAN \n17  ADMINISTRATOR, PATRICIA M. NAZEMENTZ, XEROX CORPORATION \n18  PENSION PLAN ADMINISTRATOR, XEROX CORPORATION, LAWRENCE \n19  M. BECKER, XEROX CORPORATION PLAN ADMINISTRATOR, XEROX \n20  CORPORATION RETIREMENT INCOME GUARANTEE PLAN, \n21  LAWRENCE BECKER, XEROX CORPORATION PLAN ADMINISTRATORS, \n22   \n23  Defendants‐Appellees.  \n24   \n25  _____________________________________ \n26   \n27  Before:   \n28   \n29      KEARSE, CABRANES, and LOHIER, Circuit Judges. \n30   \n31    The plaintiffs, a group of current and former employees of Xerox \n32  Corporation, appeal the decisions of the United States District Court for the \n33  Western District of New York (Larimer, J.) ordering the defendants, Xerox \n34  and various parties tied to its retirement plan, to recalculate the plaintiffs’ \n35  retirement benefits as a matter of equitable reformation and to pay \n\n\n 2 \n  \n  \n\f 1  prejudgment interest at the federal prime rate.  The plaintiffs argue that both \n 2  awards are inadequate.  We AFFIRM. \n 3               \n 4  ELIZABETH R. BRANNEN (Peter K. Stris, \n 5  Brendan S. Maher, on the brief), Stris & \n 6  Maher LLP, Los Angeles, CA; Shaun P. \n 7  Martin, University of San Diego School \n 8  of Law, San Diego, CA, for Plaintiffs‐\n 9  Appellants. \n10   \n11  MARGARET A. CLEMENS (Pamela S.C. \n12  Reynolds, on the brief), Littler \n13  Mendelson, P.C., Fairport, NY, for \n14  Defendants‐Appellees. \n15   \n16  LOHIER, Circuit Judge: \n17   \n18    The principal issue in this appeal is whether the United States District \n\n19  Court for the Western District of New York (Larimer, J.) awarded an adequate \n\n20  equitable remedy for violations under the Employee Retirement Income \n\n21  Security Act of 1974 (“ERISA”), 29 U.S.C. § 1101 et seq., related to Xerox \n\n22  Corporation’s pension plan (the “Plan”).  The plaintiffs‐appellants \n\n23  (“Plaintiffs”) “are Xerox employees who left the company in the 1980’s, \n\n24  received lump‐sum distributions of retirement benefits they had earned up to \n\n25  that point, and were later rehired.”  Conkright v. Frommert, 559 U.S. 506, 510 \n\n26  (2010).  “The dispute giving rise to this case concerns how to account for [the \n\n27  Plaintiffs’] past distributions when calculating their current benefits—that is, \n 3 \n  \n  \n\f 1  how to avoid paying [the Plaintiffs] the same benefits twice.”  Id.  The \n\n 2  defendants‐appellees are Xerox, the Plan, and individually named retirement \n\n 3  plan administrators (individually and collectively, the “Plan Administrator”).  \n\n 4  In our most recent decision in this case we determined that the Plan \n\n 5  Administrator’s method of calculating the Plaintiffs’ current benefits violated \n\n 6  ERISA’s notice requirements and therefore could not be applied to the \n\n 7  Plaintiffs’ benefits.  Frommert v. Conkright, 738 F.3d 522, 531–34 (2d Cir. \n\n 8  2013) (“Frommert III”).  We remanded to the District Court to fashion, in its \n\n 9  discretion, an equitable remedy providing appropriate retirement benefits to \n\n10  the Plaintiffs (we refer to these benefits as “New Benefits”).  Id. at 534.   \n\n11    Selecting the equitable remedy of reformation, the District Court held \n\n12  that New Benefits should be calculated as if the Plaintiffs were newly hired on \n\n13  their return to Xerox.  Frommert v. Becker, 153 F. Supp. 3d 599, 605–07, 615–\n\n14  17 (W.D.N.Y. 2016) (“January 2016 Decision”).  In a separate decision and \n\n15  order, the District Court also determined that the Plaintiffs are entitled to \n\n16  prejudgment interest at the federal prime rate.  Frommert v. Becker, 216 F. \n\n17  Supp. 3d 309, 316 (W.D.N.Y. 2016) (“November 2016 Decision”).   \n\n18  We affirm.   \n\n 4 \n  \n  \n\f 1  BACKGROUND \n\n 2    We assume familiarity with our three prior decisions in this long‐\n\n 3  running case, as well as the Supreme Court’s decision in Conkright.  See \n\n 4  Conkright, 559 U.S. 506; Frommert III, 738 F.3d 522; Frommert v. Conkright, \n\n 5  535 F.3d 111 (2d Cir. 2008) (“Frommert II”); Frommert v. Conkright, 433 F.3d \n\n 6  254 (2d Cir. 2006) (“Frommert I”); see also Testa v. Becker, 910 F.3d 677, 679–\n\n 7  81 (2d Cir. 2018) (describing litigation history).  We refer to the facts, history, \n\n 8  and record of these and other prior proceedings only as necessary to explain \n\n 9  our decision to affirm. \n\n10    Throughout this litigation, the Plaintiffs have claimed that the Plan \n\n11  Administrator improperly calculated New Benefits under the Plan in \n\n12  violation of ERISA.  See, e.g., Frommert v. Conkright, 328 F. Supp. 2d 420, 423 \n\n13  (W.D.N.Y. 2004).  The District Court initially granted summary judgment in \n\n14  favor of the Plan Administrator.  Id. at 424, 439.  We vacated, concluding that \n\n15  the Plan Administrator’s method of accounting for distributions of prior \n\n16  benefits, and its resulting calculation of New Benefits, violated the Plaintiffs’ \n\n17  rights under ERISA.  Frommert I, 433 F.3d at 256–57.   \n\n\n\n\n 5 \n  \n  \n\f 1  In a subsequent decision, we reviewed the District Court’s method of \n\n 2  calculating New Benefits as a matter of plan interpretation and concluded \n\n 3  that the method was proper under the Plan.  Frommert II, 535 F.3d at 117–18.  \n\n 4  We further held that the District Court could refuse to defer to the Plan \n\n 5  Administrator’s interpretation of the Plan.  Id. at 119.  The Supreme Court \n\n 6  reversed the latter ruling, holding, as relevant here, that we had “erred in \n\n 7  holding that the District Court could refuse to defer to the Plan \n\n 8  Administrator’s interpretation of the Plan . . . simply because [we] had found \n\n 9  a previous related interpretation by the [Plan] Administrator to be invalid.”  \n\n10  Conkright, 559 U.S. at 522.  On remand, the District Court held that the Plan \n\n11  Administrator’s proposed method of calculating New Benefits by offsetting \n\n12  the lump sum distributions made to the Plaintiffs when they initially left \n\n13  Xerox reflected a reasonable interpretation of the Plan.  Frommert v. \n\n14  Conkright, 825 F. Supp. 2d 433, 438–43 (W.D.N.Y. 2011).  It also concluded \n\n15  that the Plan adequately notified participants of the offset.  See id. at 444–47.   \n\n16  In our most recent decision, we disagreed with the District Court.  \n\n17  Frommert III, 738 F.3d at 531–34.  We held that the Plan Administrator’s \n\n18  proposed offset approach was based on an unreasonable interpretation of the \n\n 6 \n  \n  \n\f 1  Plan and that the Plan and its related documents, as interpreted and applied \n\n 2  by the Plan Administrator, violated ERISA’s notice provisions.  Id. at 529–34.  \n\n 3  We therefore instructed the District Court to first determine on remand \n\n 4  whether there existed an “appropriate” equitable remedy available to resolve \n\n 5  the Plaintiffs’ claims without resorting to plan interpretation.  Id. at 534.  “If \n\n 6  the district court holds that the Plan’s notice violations justify the imposition \n\n 7  of an equitable remedy,” we explained, “such a remedy will provide the relief \n\n 8  that [the] Plaintiffs seek.”  Id.  We also instructed that “if [the District Court] \n\n 9  finds that no equitable remedy is available, it should separately consider [the] \n\n10  Plaintiff’s unreasonable‐interpretation claim,” id. (emphasis added), meaning \n\n11  that if the court could devise an appropriate equitable remedy, it could forgo \n\n12  interpreting the Plan. \n\n13  Following Frommert III, the District Court decided to reform the Plan \n\n14  as an appropriate equitable remedy under the circumstances.  January 2016 \n\n15  Decision, 153 F. Supp. 3d at 615.  It then set about exploring methods of \n\n16  calculating New Benefits that were consistent with reforming the Plan.  \n\n17  Although the District Court surveyed several possible remedies, many of \n\n18  which had been endorsed at varying times by one or both parties, we focus on \n\n 7 \n  \n  \n\f 1  three of these approaches, starting with the so‐called “new hire” remedy that \n\n 2  the District Court ultimately selected. \n\n 3  The District Court’s new hire remedy is “to recalculate [the P]laintiffs’ \n\n 4  benefits, treating [the P]laintiffs upon their re‐employment with Xerox as if \n\n 5  they had been newly hired, with no offset whatsoever.”  Id. at 605.  In other \n\n 6  words, the remedy treats the Plaintiffs’ return to Xerox as the start of a period \n\n 7  of new employment, without any reduction of the Plaintiffs’ retirement \n\n 8  benefits to account for any prior benefit distributions or any credit for earlier \n\n 9  years of service with Xerox.  See id. at 606. \n\n10  In selecting the new hire remedy, the District Court considered and \n\n11  rejected the “Layaou” and “actual annuity” approaches as ways to calculate \n\n12  benefits.1  Id. at 611–15.  Each of these remedies would have entailed, in effect, \n\n13  subtracting the unadjusted value of the Plaintiffs’ original retirement benefits \n\n14  from their New Benefits.  See Joint App’x at 66–69 (explaining actual annuity \n\n15  method), 69–70 (explaining Layaou method).  We previously affirmed the \n\n16  District Court’s adoption of the Layaou approach in Frommert II.  But that \n\n\n                                                  \n 1 The Layaou method is so‐named because it was first applied in an earlier, related \n\n action.  See Layaou v. Xerox Corp., 330 F. Supp. 2d 297, 304 (W.D.N.Y. 2004); see \n also Layaou v. Xerox Corp., 238 F.3d 205 (2d Cir. 2001). \n 8 \n  \n  \n\f1  approach came under heavy criticism from the Supreme Court in Conkright, \n\n2  which decried it variously as “an interpretation of the Plan that does not \n\n3  account for the time value of money,” “actuarial . . . heresy,” and “highly \n\n4  unforeseeable.”2  559 U.S. at 519.   \n\n5  After outlining the deficiencies (which we do not recount in detail here) \n\n6  of each of the alternative approaches, and over the Plaintiffs’ objections, the \n\n7  District Court adopted the new hire remedy to award the Plaintiffs New \n\n8  Benefits.  See January 2016 Decision, 153 F. Supp. 3d at 605, 610–12.  The \n\n9  District Court cited four principal reasons for doing so.   \n\n\n\n                                                  \n 2 At different times, the District Court also considered two other approaches: the \n\n “phantom account” method and the “actuarial equivalent” method, both of which \n subtract or offset the expected value of the prior lump sum distributions from the \n Plaintiffs’ New Benefits.  See, e.g., Frommert I, 433 F.3d at 260 (explaining phantom \n account method); Testa, 910 F.3d at 680 (same); Frommert III, 738 F.3d at 528 & n.8, \n 530 (explaining actuarial equivalent method).  Although in Testa we suggested, in \n dicta, that the phantom account method may be applied to similarly situated \n employees who were not plaintiffs in this action, see 910 F.3d at 684–85, there is no \n question that the resolution of the challenge here is squarely governed by Frommert \n I, which held that the phantom account method may not be applied to the Plaintiffs \n in this action, 433 F.3d at 263.  And in Frommert III, we held, as noted above, that a \n lack of notice prevented the District Court from applying any expected value \n method to the Plaintiffs.  738 F.3d at 534; see also January 2016 Decision, 153 F. \n Supp. 3d at 605–06.  The District Court also rejected a third method, the “no‐offset” \n method, under which the Plaintiffs would accrue benefits for all their years of \n service without any reduction to account for the prior distributions.  January 2016 \n Decision, 153 F. Supp. 3d at 613–14.   \n 9 \n  \n  \n\f 1  First, at different stages of the litigation the Plaintiffs had agreed that \n\n 2  the new hire remedy was appropriate.  Id. at 610 (“Both sides have at times \n\n 3  expressed some amenability to a new‐hire remedy.”); Transcript of \n\n 4  Proceedings dated October 23, 2014, statement of Plaintiffs’ counsel, Dist. Ct. \n\n 5  Dkt. No. 280, at 4 (“[W]e are entitled to and we do still request . . . partial \n\n 6  summary judgment that entitles the [P]laintiffs to be paid . . . at least as well \n\n 7  as new hires.”); Plaintiffs’ Motion to Reenter Judgment, dated October 8, 2010, \n\n 8  Dist. Ct. Dkt. No. 205, at 21 (Plaintiffs requesting that “at a minimum, [the \n\n 9  District Court] . . . enter a judgment that orders [the Plan Administrator] to \n\n10  pay rehired employees no less than the pension that identically‐situated new \n\n11  employees would receive”).  In view of these prior statements, the Plaintiffs’ \n\n12  claim that the new hire remedy is inequitable appears somewhat \n\n13  disingenuous.   \n\n14  Second, the remedy properly accounts for the time value of money and \n\n15  thus avoids the Supreme Court’s main criticism of the Layaou approach.  \n\n16  January 2016 Decision, 153 F. Supp. 3d at 612; see Conkright, 559 U.S. at 519.   \n\n17  Third, in Frommert III we stated that, at a minimum, rehired employees \n\n18  should not end up with lower benefits than similarly situated, newly hired \n\n 10 \n  \n  \n\f 1  employees.  January 2016 Decision, 153 F. Supp. 3d at 605–06; Frommert III, \n\n 2  738 F.3d at 530–31.   \n\n 3  And fourth, the new hire remedy, as the District Court found, “strikes a \n\n 4  balance” between penalizing the Plaintiffs by subtracting the value of their \n\n 5  prior distributions without proper notice and overpaying the Plaintiffs by \n\n 6  allowing double benefits for the same period of service.  January 2016 \n\n 7  Decision, 153 F. Supp. 3d at 615. \n\n 8    Having selected the new hire remedy to calculate the Plaintiffs’ New \n\n 9  Benefits, the District Court by later decision and order proceeded to pick a \n\n10  rate of prejudgment interest to apply to the award.  November 2016 Decision, \n\n11  216 F. Supp. 3d at 311–12, 316.  The Plaintiffs asked the District Court to \n\n12  impose the New York statutory rate of nine percent, while the Plan \n\n13  Administrator urged the selection of the federal post‐judgment interest rate, \n\n14  see 28 U.S.C. § 1961, which, “[a]s of October 14, 2016, . . . stood at 0.66%,” \n\n15  November 2016 Decision, 216 F. Supp. 3d at 315.  Rejecting the Plaintiffs’ \n\n16  proposed rate as too high and the Plan Administrator’s as too low, the District \n\n17  Court chose the federal prime rate of 3.5 percent.  Id. at 315–16.   \n\n18    The Plaintiffs timely appealed both decisions.   \n\n 11 \n  \n  \n\f 1  DISCUSSION \n\n 2  On appeal, the Plaintiffs argue that both the new hire remedy and the \n\n 3  awarded prejudgment interest (at the federal prime rate) are inadequate.  We \n\n 4  consider each argument in turn.   \n\n\n 5  1. New Hire Remedy \n\n 6  We first address whether the District Court abused its discretion when \n\n 7  it selected the new hire approach as an equitable remedy to redress the Plan \n\n 8  Administrator’s notice violations.  See Chao v. Merino, 452 F.3d 174, 185 (2d \n\n 9  Cir. 2006) (“We review the district courtʹs fashioning of equitable remedies \n\n10  under ERISA for abuse of discretion.”).3   \n\n11  As an initial matter, we note that the Plaintiffs do not challenge the \n\n12  District Court’s finding that contract reformation was an appropriate \n\n13  equitable remedy in this case.  Instead, the Plaintiffs argue that, having \n\n\n\n                                                  \n 3 As we have recognized, “[t]he word ‘abuse’ in the ‘abuse of discretion’ standard is \n\n an unfortunate—and inaccurate—term of art” because “abuses of discretion” rarely, \n if ever, involve anything “as heinous as abuse.”  In re City of New York, 607 F.3d \n 923, 943 n.21 (2d Cir. 2010); see also In re Sims, 534 F.3d 117, 132 (2d Cir. 2008) (“A \n district court has abused its discretion if it based its ruling on an erroneous view of \n the law or on a clearly erroneous assessment of the evidence or rendered a decision \n that cannot be located within the range of permissible decisions.” (quotation marks \n omitted)). \n 12 \n  \n  \n\f 1  decided to reform the Plan, the District Court should have chosen a \n\n 2  calculation of New Benefits that was more favorable to them than the new \n\n 3  hire approach.  We are not persuaded.  \n\n 4  Each of the considered equitable approaches for calculating the \n\n 5  Plaintiffs’ benefits has proven to be imperfect.  Indeed, our decision in \n\n 6  Frommert III foreclosed the possibility of applying any of the expected value \n\n 7  methods.  See 738 F.3d at 534.  Meanwhile, although Conkright did not \n\n 8  address equitable remedies, its criticism of the unadjusted value methods as \n\n 9  failing to account for the time value of money is reason enough to disqualify \n\n10  those methods.4  See 559 U.S. at 519.  Nor, as the District Court found, does \n\n11  the no‐offset method, which results in a clear windfall to the Plaintiffs, fare \n\n12  any better as a suitable remedy.  See January 2016 Decision, 153 F. Supp. 3d at \n\n13  613–14.   \n\n\n\n\n                                                  \n 4 The Plaintiffs attempt to distinguish the actual annuity method from the Layaou \n\n method by claiming that the former, an annuity, accounts for the time value of \n money.  But the actual annuity method derives from the unadjusted value of what \n the Plaintiffs could have received as original retirement benefits.  Indeed, as the \n Plaintiffs’ own expert admitted, the actual annuity method and the Layaou method \n produce very similar New Benefits calculations.  See Joint App’x at 330–31; see also \n Joint App’x at 70.   \n 13 \n  \n  \n\f 1  The new hire approach has its own flaws, insofar as it fails to fully \n\n 2  count all years of service at Xerox, with an offset for the prior distributions \n\n 3  made to the Plaintiffs when they first left Xerox, as the parties originally \n\n 4  expected.  See Frommert v. Conkright, 472 F. Supp. 2d 452, 455, 458 \n\n 5  (W.D.N.Y. 2007) (“2007 Decision”).  Nevertheless, the District Court did not \n\n 6  abuse its discretion in selecting the new hire approach as an adequate \n\n 7  equitable remedy.  Among its significant advantages over other potential \n\n 8  remedies, the new hire approach accounts for the time value of money, see \n\n 9  Conkright, 559 U.S. at 519, but avoids the problems associated with the \n\n10  expected value methods described above and in Frommert III, 738 F.3d at 534.  \n\n11  The approach has two more advantages to distinguish it in the context of this \n\n12  litigation.  First, as we explained in Frommert III, the Plaintiffs are entitled to \n\n13  at least the new hire remedy.  Id. at 530–31.  Second, we agree with the \n\n14  District Court that the new hire approach better balances the dueling interests \n\n15  of the Plan Administrator and the Plaintiffs.  See January 2016 Decision, 153 F. \n\n16  Supp. 3d at 610, 612, 614–15. \n\n\n17  In urging a contrary conclusion, the Plaintiffs argue that the District \n\n18  Court improperly refused to consider two alternative theories of equitable \n\n 14 \n  \n  \n\f 1  remedy, surcharge and estoppel.  They claim that one or both theories might \n\n 2  have justified a higher benefits award.  But having determined that the \n\n 3  District Court did not abuse its discretion when it reformed the Plan to grant \n\n 4  the new hire remedy as adequate equitable relief, “we need not address \n\n 5  whether relief would alternatively have been proper pursuant to different \n\n 6  equitable remedies such as surcharge or estoppel.”  Amara v. CIGNA Corp., \n\n 7  775 F.3d 510, 532 (2d Cir. 2014).  And the District Court, far from ignoring \n\n 8  surcharge or estoppel, explicitly described them as “unnecessary.”  January \n\n 9  2016 Decision, 153 F. Supp. 3d at 613. \n\n\n10  The Plaintiffs also argue that the District Court was affirmatively \n\n11  required to interpret the Plan.  They claim that this in turn might have yielded \n\n12  a higher benefits award.  But this argument runs headlong into Frommert III.  \n\n13  There we stated, to the contrary, that the District Court did not need to \n\n14  engage in plan interpretation if it determined that an appropriate equitable \n\n15  remedy existed.  738 F.3d at 534; see DiLaura v. Power Auth., 982 F.2d 73, 76 \n\n16  (2d Cir. 1992) (observing that under the “law of the case” doctrine, “when a \n\n17  court decides upon a rule of law, that decision should continue to govern the \n\n18  same issues in subsequent stages in the same case” (quotation marks \n\n 15 \n  \n  \n\f 1  omitted)).  District courts generally may avoid interpreting a pension plan \n\n 2  and instead fashion equitable remedies for ERISA violations where the plan is \n\n 3  “significantly incomplete” and misleads its employees.  See CIGNA Corp. v. \n\n 4  Amara, 563 U.S. 421, 428, 438–43 (2011).  Under those circumstances, a district \n\n 5  court may, for example, “properly reform[ ] [a pension] plan to reflect the \n\n 6  representations that the defendants made to the plaintiffs.”  Osberg v. Foot \n\n 7  Locker, Inc., 862 F.3d 198, 215 (2d Cir. 2017) (quotation marks omitted).   \n\n\n 8  The Plaintiffs themselves appear to have acknowledged this point.  \n\n 9  They informed the District Court that “[o]nce [the P]laintiffs are granted the \n\n10  equitable relief to which they are entitled for the undisputed notice violations, \n\n11  [the District Court] need not attempt to resolve the plan interpretation issue.”  \n\n12  Memorandum of Points and Authorities In Support of Plaintiffs’ Motion for \n\n13  Entry of Judgment on Notice Issue, dated October 20, 2014, Dist. Ct. Dkt. No. \n\n14  267‐1, at 2.  In this case, the District Court found that there was no reasonable \n\n15  plan interpretation as to which notice had been provided by Xerox.  See \n\n16  January 2016 Decision, 153 F. Supp. 3d at 604–05; 2007 Decision, 472 F. Supp. \n\n17  2d at 457 (noting that “virtually nothing is set forth in either the Plan or the \n\n18  [summary plan description]” to explain how to account for prior \n\n 16 \n  \n  \n\f 1  distributions).  The District Court was therefore entitled to reform the Plan \n\n 2  and employ the new hire approach as an equitable remedy in compliance \n\n 3  with our mandate in Frommert III.  See 738 F.3d at 534.  \n\n\n 4  The District Court’s selection of the new hire remedy falls within the \n\n 5  “range of permissible decisions available under an abuse of discretion \n\n 6  standard.”  Osberg, 862 F.3d at 215 (quotation marks omitted).  For these \n\n 7  reasons, we affirm the District Court’s decision to use the new hire approach \n\n 8  as an equitable remedy to redress the Plan Administrator’s notice violations. \n\n\n 9  2. Prejudgment Interest \n\n10  We next address the District Court’s award of prejudgment interest at \n\n11  the federal prime rate.  As an initial matter, the District Court enjoyed broad \n\n12  discretion to decide whether to award prejudgment interest in this case.  See \n\n13  S.E.C. v. First Jersey Sec., Inc., 101 F.3d 1450, 1476 (2d Cir. 1996).  In exercising \n\n14  such discretion, the District Court had to consider “(i) the need to fully \n\n15  compensate the wronged party for actual damages suffered, (ii) . . . fairness \n\n16  and the relative equities of the award, (iii) the remedial purpose of the statute \n\n17  involved, and/or (iv) such other general principles as are deemed relevant by \n\n18  the court.”  Jones v. UNUM Life Ins. Co. of Am., 223 F.3d 130, 139 (2d Cir. \n 17 \n  \n  \n\f 1  2000) (quotation marks omitted).  Those same factors also inform a district \n\n 2  court’s choice of a particular interest rate,  id., which “must not result in over‐\n\n 3  compensation of the plaintiff,”  Wickham Contracting Co. v. Local Union No. \n\n 4  3, IBEW, 955 F.2d 831, 834 (2d Cir. 1992).  “We have allowed discretionary \n\n 5  awards of prejudgment interest . . . when the awards were fair, equitable and \n\n 6  necessary to compensate the wronged party fully.”  Id. at 835. \n\n 7  In its November 2016 Decision, the District Court concluded that the \n\n 8  Plaintiffs were entitled to prejudgment interest at the federal prime rate.  The \n\n 9  court specifically found that the prime rate of 3.5 percent “strikes an \n\n10  appropriate balance” and “fairly compensate[s]” the Plaintiffs.5  November \n\n11  2016 Decision, 216 F. Supp. 3d at 316.  The court also carefully explained why \n\n12  it rejected the New York statutory rate of nine percent (proposed by the \n\n13  Plaintiffs) as too high and the federal post‐judgment interest rate of 0.66 \n\n14  percent (proposed by the Plan Administrator) as too low.  Id. at 315.  We \n\n15  affirm the District Court’s decision to use the prime rate for three reasons.  \n\n\n\n                                                  \n 5 This decision was clarified in another decision entered on May 4, 2017.  Frommert \n\n v. Conkright, 2017 WL 3867795, at *1 (W.D.N.Y. May 4, 2017).  That decision \n addressed primarily the mechanics of implementing the District Court’s \n prejudgment interest award—mechanics that are not at issue in this appeal. \n 18 \n  \n  \n\f1  First, it had broad discretion to grant prejudgment interest and to select a rate.  \n\n2  Second, it carefully considered all the relevant factors in determining whether \n\n3  prejudgment interest was warranted, and, if so, what the rate should be.  And \n\n4  finally, it thoroughly explained its reasoning for using the federal prime rate. \n\n\n5  CONCLUSION \n\n6  We have considered the Plaintiffs’ remaining arguments and conclude \n\n7  that they are without merit.  For the foregoing reasons, we AFFIRM.  \n\n\n\n\n 19", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358448/", "author_raw": "LOHIER, Circuit Judge:"}]}
KEARSE
CABRANES
LOHIER
1
{"KEARSE": ", Circuit", "CABRANES": ", Circuit", "LOHIER": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4581195/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Frommert v. Conkright\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-14\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17‐114‐cv(L) \n Frommert v. Conkright \n 1  UNITED STATES COURT OF APPEALS \n 2  FOR THE SECOND CIRCUIT \n 3   \n 4  August Term, 2017 \n 5   \n 6  (Argued: April 18, 2018  Decided: January 14, 2019 ) \n 7   \n 8  Docket Nos. 17‐114‐cv(L), 17‐738‐cv(CON) \n 9   \n10  _____________________________________ \n11   \n12  PAUL J. FROMMERT, DONALD S. FOOTE, THOMAS I. BARNES, RONALD \n13  J. CAMPBELL, FRANK D. COMMESSO, WILLIAM F. COONS, JAMES D. \n14  GAGNIER, BRIAN L. GAITA, WILLIAM J. LADUE, GERALD A. \n15  LEONARDO, JR., FRANK MAWDESLEY, HAROLD S. MITCHELL, \n16  WALTER J. PETROFF, RICHARD C. SPRING, PATRICIA M. JOHNSON, F. \n17  PATRICIA M. TOBIN, NANCY A. REVELLA, ANATOLI G. PUSCHKIN, \n18  WILLIAM R. PLUMMER, MICHAEL J. MCCOY, ALAN H. CLAIR, LARRY J. \n19  GALLAGHER, NAPOLEON B. BARBOSA, ALEXANDRA SPEARMAN \n20  HARRICK, JANIS A. EDELMAN, PATRICIA H. JOHNSTON, KENNETH P. \n21  PARNETT, JOYCE D. CATHCART, FLOYD SWAIM, JULIE A. MCMILLIAN, \n22  DENNIS E. BAINES, RUBY JEAN MURPHY, MATTHEW D. ALFIERI, \n23  IRSHAD QURESHI, RICHARD C. CRATER, GAIL J. LEVY, JOHN A. \n24  WILLIAMS, CRYSTAL THORTON, CHARLES R. DRANNBAUER, \n25  WILLIAM M. BURRITT, JANICE ROSS HEILER, JOSEPH MCNEIL, \n26  THOMAS F. MCGEE, VINCENT G. JOHNSON, F. COLT HITCHCOCK, \n27  RONNIE TABAK, MARTHA LEE TAYLOR, KATHY FAY THOMPSON, \n28  MARY BETH ALLEN, CRAIG SPENCER, LINDA S. BOURQUE, THOMAS \n29  MICHAEL VASTA, FRANK C. DARLING, CLARK C. DINGMAN, CAROL \n30  E. GANNON, JOSEPH E. WRIGHT, DAVID M. ROHAN, DAVID B. \n31  RUDDOCK, CHARLES HOBBS, CHARLES ZABINSKI, CHARLES J. \n32  MADDALOZZO, JOYCE M. PRUETT, WILLIAM A. CRAVEN, MAUREEN \n33  A. LOUGHLIN JONES, KENNETH W. PIETROWSKI, BONNIE COHEN, \n34  LAWRENCE R. HOLLAND, GAIL A. NASMAN, STEVEN D. BARLEY, \n35  DONNA S. LIPARI, ANDREW C. MATTELIANO, MICHAEL HORROCKS, \n36  CANDICE J. WHITE, KATHLEEN E. HUNTER, JOHN L. CRISAFULLI, \n\f 1  DEBORAH J. DAVIS, BRENDA H. MCCONNELL, KATHLEEN A. BOWEN, \n 2  ROBERT P. CARANDDO, TERENCE J. KURTZ, WILLIAM J. CHESLOCK, \n 3  THOMAS E. DALTON, LYNN BARNSDALE, BRUCE D. CRAIG, GARY P. \n 4  HARDIN, CLAUDETTE M. LONG, DALE PLATTETER, MARY ANN \n 5  SERGEANT, MOLLY WHITE KEHOE, DAVID K. YOUNG, LESLIE ANN \n 6  WUNSCH, RICHARD J. GLIKIN, EUGENE H. UPDYKE, MICHAEL R. \n 7  BENSON, ALVIN M. ADAMS, RONNIE KOLNIAK, JAMES J. FARRELL, \n 8  ROBERT L. BRACKHAHN, BENJAMIN C. ROTH, CARMEN J. SOFIA, \n 9  KATHLEEN W. LEVEA, FREDERICK SCACCHITTI, PAUL DEFINA, JAMES \n10  G. WALLS, \n11   \n12  Plaintiffs‐Appellants, \n13   \n14  v. \n15   \n16  SALLY L. CONKRIGHT, XEROX CORPORATION PENSION PLAN \n17  ADMINISTRATOR, PATRICIA M. NAZEMENTZ, XEROX CORPORATION \n18  PENSION PLAN ADMINISTRATOR, XEROX CORPORATION, LAWRENCE \n19  M. BECKER, XEROX CORPORATION PLAN ADMINISTRATOR, XEROX \n20  CORPORATION RETIREMENT INCOME GUARANTEE PLAN, \n21  LAWRENCE BECKER, XEROX CORPORATION PLAN ADMINISTRATORS, \n22   \n23  Defendants‐Appellees.  \n24   \n25  _____________________________________ \n26   \n27  Before:   \n28   \n29      KEARSE, CABRANES, and LOHIER, Circuit Judges. \n30   \n31    The plaintiffs, a group of current and former employees of Xerox \n32  Corporation, appeal the decisions of the United States District Court for the \n33  Western District of New York (Larimer, J.) ordering the defendants, Xerox \n34  and various parties tied to its retirement plan, to recalculate the plaintiffs’ \n35  retirement benefits as a matter of equitable reformation and to pay \n\n\n 2 \n  \n  \n\f 1  prejudgment interest at the federal prime rate.  The plaintiffs argue that both \n 2  awards are inadequate.  We AFFIRM. \n 3               \n 4  ELIZABETH R. BRANNEN (Peter K. Stris, \n 5  Brendan S. Maher, on the brief), Stris & \n 6  Maher LLP, Los Angeles, CA; Shaun P. \n 7  Martin, University of San Diego School \n 8  of Law, San Diego, CA, for Plaintiffs‐\n 9  Appellants. \n10   \n11  MARGARET A. CLEMENS (Pamela S.C. \n12  Reynolds, on the brief), Littler \n13  Mendelson, P.C., Fairport, NY, for \n14  Defendants‐Appellees. \n15   \n16  LOHIER, Circuit Judge: \n17   \n18    The principal issue in this appeal is whether the United States District \n\n19  Court for the Western District of New York (Larimer, J.) awarded an adequate \n\n20  equitable remedy for violations under the Employee Retirement Income \n\n21  Security Act of 1974 (“ERISA”), 29 U.S.C. § 1101 et seq., related to Xerox \n\n22  Corporation’s pension plan (the “Plan”).  The plaintiffs‐appellants \n\n23  (“Plaintiffs”) “are Xerox employees who left the company in the 1980’s, \n\n24  received lump‐sum distributions of retirement benefits they had earned up to \n\n25  that point, and were later rehired.”  Conkright v. Frommert, 559 U.S. 506, 510 \n\n26  (2010).  “The dispute giving rise to this case concerns how to account for [the \n\n27  Plaintiffs’] past distributions when calculating their current benefits—that is, \n 3 \n  \n  \n\f 1  how to avoid paying [the Plaintiffs] the same benefits twice.”  Id.  The \n\n 2  defendants‐appellees are Xerox, the Plan, and individually named retirement \n\n 3  plan administrators (individually and collectively, the “Plan Administrator”).  \n\n 4  In our most recent decision in this case we determined that the Plan \n\n 5  Administrator’s method of calculating the Plaintiffs’ current benefits violated \n\n 6  ERISA’s notice requirements and therefore could not be applied to the \n\n 7  Plaintiffs’ benefits.  Frommert v. Conkright, 738 F.3d 522, 531–34 (2d Cir. \n\n 8  2013) (“Frommert III”).  We remanded to the District Court to fashion, in its \n\n 9  discretion, an equitable remedy providing appropriate retirement benefits to \n\n10  the Plaintiffs (we refer to these benefits as “New Benefits”).  Id. at 534.   \n\n11    Selecting the equitable remedy of reformation, the District Court held \n\n12  that New Benefits should be calculated as if the Plaintiffs were newly hired on \n\n13  their return to Xerox.  Frommert v. Becker, 153 F. Supp. 3d 599, 605–07, 615–\n\n14  17 (W.D.N.Y. 2016) (“January 2016 Decision”).  In a separate decision and \n\n15  order, the District Court also determined that the Plaintiffs are entitled to \n\n16  prejudgment interest at the federal prime rate.  Frommert v. Becker, 216 F. \n\n17  Supp. 3d 309, 316 (W.D.N.Y. 2016) (“November 2016 Decision”).   \n\n18  We affirm.   \n\n 4 \n  \n  \n\f 1  BACKGROUND \n\n 2    We assume familiarity with our three prior decisions in this long‐\n\n 3  running case, as well as the Supreme Court’s decision in Conkright.  See \n\n 4  Conkright, 559 U.S. 506; Frommert III, 738 F.3d 522; Frommert v. Conkright, \n\n 5  535 F.3d 111 (2d Cir. 2008) (“Frommert II”); Frommert v. Conkright, 433 F.3d \n\n 6  254 (2d Cir. 2006) (“Frommert I”); see also Testa v. Becker, 910 F.3d 677, 679–\n\n 7  81 (2d Cir. 2018) (describing litigation history).  We refer to the facts, history, \n\n 8  and record of these and other prior proceedings only as necessary to explain \n\n 9  our decision to affirm. \n\n10    Throughout this litigation, the Plaintiffs have claimed that the Plan \n\n11  Administrator improperly calculated New Benefits under the Plan in \n\n12  violation of ERISA.  See, e.g., Frommert v. Conkright, 328 F. Supp. 2d 420, 423 \n\n13  (W.D.N.Y. 2004).  The District Court initially granted summary judgment in \n\n14  favor of the Plan Administrator.  Id. at 424, 439.  We vacated, concluding that \n\n15  the Plan Administrator’s method of accounting for distributions of prior \n\n16  benefits, and its resulting calculation of New Benefits, violated the Plaintiffs’ \n\n17  rights under ERISA.  Frommert I, 433 F.3d at 256–57.   \n\n\n\n\n 5 \n  \n  \n\f 1  In a subsequent decision, we reviewed the District Court’s method of \n\n 2  calculating New Benefits as a matter of plan interpretation and concluded \n\n 3  that the method was proper under the Plan.  Frommert II, 535 F.3d at 117–18.  \n\n 4  We further held that the District Court could refuse to defer to the Plan \n\n 5  Administrator’s interpretation of the Plan.  Id. at 119.  The Supreme Court \n\n 6  reversed the latter ruling, holding, as relevant here, that we had “erred in \n\n 7  holding that the District Court could refuse to defer to the Plan \n\n 8  Administrator’s interpretation of the Plan . . . simply because [we] had found \n\n 9  a previous related interpretation by the [Plan] Administrator to be invalid.”  \n\n10  Conkright, 559 U.S. at 522.  On remand, the District Court held that the Plan \n\n11  Administrator’s proposed method of calculating New Benefits by offsetting \n\n12  the lump sum distributions made to the Plaintiffs when they initially left \n\n13  Xerox reflected a reasonable interpretation of the Plan.  Frommert v. \n\n14  Conkright, 825 F. Supp. 2d 433, 438–43 (W.D.N.Y. 2011).  It also concluded \n\n15  that the Plan adequately notified participants of the offset.  See id. at 444–47.   \n\n16  In our most recent decision, we disagreed with the District Court.  \n\n17  Frommert III, 738 F.3d at 531–34.  We held that the Plan Administrator’s \n\n18  proposed offset approach was based on an unreasonable interpretation of the \n\n 6 \n  \n  \n\f 1  Plan and that the Plan and its related documents, as interpreted and applied \n\n 2  by the Plan Administrator, violated ERISA’s notice provisions.  Id. at 529–34.  \n\n 3  We therefore instructed the District Court to first determine on remand \n\n 4  whether there existed an “appropriate” equitable remedy available to resolve \n\n 5  the Plaintiffs’ claims without resorting to plan interpretation.  Id. at 534.  “If \n\n 6  the district court holds that the Plan’s notice violations justify the imposition \n\n 7  of an equitable remedy,” we explained, “such a remedy will provide the relief \n\n 8  that [the] Plaintiffs seek.”  Id.  We also instructed that “if [the District Court] \n\n 9  finds that no equitable remedy is available, it should separately consider [the] \n\n10  Plaintiff’s unreasonable‐interpretation claim,” id. (emphasis added), meaning \n\n11  that if the court could devise an appropriate equitable remedy, it could forgo \n\n12  interpreting the Plan. \n\n13  Following Frommert III, the District Court decided to reform the Plan \n\n14  as an appropriate equitable remedy under the circumstances.  January 2016 \n\n15  Decision, 153 F. Supp. 3d at 615.  It then set about exploring methods of \n\n16  calculating New Benefits that were consistent with reforming the Plan.  \n\n17  Although the District Court surveyed several possible remedies, many of \n\n18  which had been endorsed at varying times by one or both parties, we focus on \n\n 7 \n  \n  \n\f 1  three of these approaches, starting with the so‐called “new hire” remedy that \n\n 2  the District Court ultimately selected. \n\n 3  The District Court’s new hire remedy is “to recalculate [the P]laintiffs’ \n\n 4  benefits, treating [the P]laintiffs upon their re‐employment with Xerox as if \n\n 5  they had been newly hired, with no offset whatsoever.”  Id. at 605.  In other \n\n 6  words, the remedy treats the Plaintiffs’ return to Xerox as the start of a period \n\n 7  of new employment, without any reduction of the Plaintiffs’ retirement \n\n 8  benefits to account for any prior benefit distributions or any credit for earlier \n\n 9  years of service with Xerox.  See id. at 606. \n\n10  In selecting the new hire remedy, the District Court considered and \n\n11  rejected the “Layaou” and “actual annuity” approaches as ways to calculate \n\n12  benefits.1  Id. at 611–15.  Each of these remedies would have entailed, in effect, \n\n13  subtracting the unadjusted value of the Plaintiffs’ original retirement benefits \n\n14  from their New Benefits.  See Joint App’x at 66–69 (explaining actual annuity \n\n15  method), 69–70 (explaining Layaou method).  We previously affirmed the \n\n16  District Court’s adoption of the Layaou approach in Frommert II.  But that \n\n\n                                                  \n 1 The Layaou method is so‐named because it was first applied in an earlier, related \n\n action.  See Layaou v. Xerox Corp., 330 F. Supp. 2d 297, 304 (W.D.N.Y. 2004); see \n also Layaou v. Xerox Corp., 238 F.3d 205 (2d Cir. 2001). \n 8 \n  \n  \n\f1  approach came under heavy criticism from the Supreme Court in Conkright, \n\n2  which decried it variously as “an interpretation of the Plan that does not \n\n3  account for the time value of money,” “actuarial . . . heresy,” and “highly \n\n4  unforeseeable.”2  559 U.S. at 519.   \n\n5  After outlining the deficiencies (which we do not recount in detail here) \n\n6  of each of the alternative approaches, and over the Plaintiffs’ objections, the \n\n7  District Court adopted the new hire remedy to award the Plaintiffs New \n\n8  Benefits.  See January 2016 Decision, 153 F. Supp. 3d at 605, 610–12.  The \n\n9  District Court cited four principal reasons for doing so.   \n\n\n\n                                                  \n 2 At different times, the District Court also considered two other approaches: the \n\n “phantom account” method and the “actuarial equivalent” method, both of which \n subtract or offset the expected value of the prior lump sum distributions from the \n Plaintiffs’ New Benefits.  See, e.g., Frommert I, 433 F.3d at 260 (explaining phantom \n account method); Testa, 910 F.3d at 680 (same); Frommert III, 738 F.3d at 528 & n.8, \n 530 (explaining actuarial equivalent method).  Although in Testa we suggested, in \n dicta, that the phantom account method may be applied to similarly situated \n employees who were not plaintiffs in this action, see 910 F.3d at 684–85, there is no \n question that the resolution of the challenge here is squarely governed by Frommert \n I, which held that the phantom account method may not be applied to the Plaintiffs \n in this action, 433 F.3d at 263.  And in Frommert III, we held, as noted above, that a \n lack of notice prevented the District Court from applying any expected value \n method to the Plaintiffs.  738 F.3d at 534; see also January 2016 Decision, 153 F. \n Supp. 3d at 605–06.  The District Court also rejected a third method, the “no‐offset” \n method, under which the Plaintiffs would accrue benefits for all their years of \n service without any reduction to account for the prior distributions.  January 2016 \n Decision, 153 F. Supp. 3d at 613–14.   \n 9 \n  \n  \n\f 1  First, at different stages of the litigation the Plaintiffs had agreed that \n\n 2  the new hire remedy was appropriate.  Id. at 610 (“Both sides have at times \n\n 3  expressed some amenability to a new‐hire remedy.”); Transcript of \n\n 4  Proceedings dated October 23, 2014, statement of Plaintiffs’ counsel, Dist. Ct. \n\n 5  Dkt. No. 280, at 4 (“[W]e are entitled to and we do still request . . . partial \n\n 6  summary judgment that entitles the [P]laintiffs to be paid . . . at least as well \n\n 7  as new hires.”); Plaintiffs’ Motion to Reenter Judgment, dated October 8, 2010, \n\n 8  Dist. Ct. Dkt. No. 205, at 21 (Plaintiffs requesting that “at a minimum, [the \n\n 9  District Court] . . . enter a judgment that orders [the Plan Administrator] to \n\n10  pay rehired employees no less than the pension that identically‐situated new \n\n11  employees would receive”).  In view of these prior statements, the Plaintiffs’ \n\n12  claim that the new hire remedy is inequitable appears somewhat \n\n13  disingenuous.   \n\n14  Second, the remedy properly accounts for the time value of money and \n\n15  thus avoids the Supreme Court’s main criticism of the Layaou approach.  \n\n16  January 2016 Decision, 153 F. Supp. 3d at 612; see Conkright, 559 U.S. at 519.   \n\n17  Third, in Frommert III we stated that, at a minimum, rehired employees \n\n18  should not end up with lower benefits than similarly situated, newly hired \n\n 10 \n  \n  \n\f 1  employees.  January 2016 Decision, 153 F. Supp. 3d at 605–06; Frommert III, \n\n 2  738 F.3d at 530–31.   \n\n 3  And fourth, the new hire remedy, as the District Court found, “strikes a \n\n 4  balance” between penalizing the Plaintiffs by subtracting the value of their \n\n 5  prior distributions without proper notice and overpaying the Plaintiffs by \n\n 6  allowing double benefits for the same period of service.  January 2016 \n\n 7  Decision, 153 F. Supp. 3d at 615. \n\n 8    Having selected the new hire remedy to calculate the Plaintiffs’ New \n\n 9  Benefits, the District Court by later decision and order proceeded to pick a \n\n10  rate of prejudgment interest to apply to the award.  November 2016 Decision, \n\n11  216 F. Supp. 3d at 311–12, 316.  The Plaintiffs asked the District Court to \n\n12  impose the New York statutory rate of nine percent, while the Plan \n\n13  Administrator urged the selection of the federal post‐judgment interest rate, \n\n14  see 28 U.S.C. § 1961, which, “[a]s of October 14, 2016, . . . stood at 0.66%,” \n\n15  November 2016 Decision, 216 F. Supp. 3d at 315.  Rejecting the Plaintiffs’ \n\n16  proposed rate as too high and the Plan Administrator’s as too low, the District \n\n17  Court chose the federal prime rate of 3.5 percent.  Id. at 315–16.   \n\n18    The Plaintiffs timely appealed both decisions.   \n\n 11 \n  \n  \n\f 1  DISCUSSION \n\n 2  On appeal, the Plaintiffs argue that both the new hire remedy and the \n\n 3  awarded prejudgment interest (at the federal prime rate) are inadequate.  We \n\n 4  consider each argument in turn.   \n\n\n 5  1. New Hire Remedy \n\n 6  We first address whether the District Court abused its discretion when \n\n 7  it selected the new hire approach as an equitable remedy to redress the Plan \n\n 8  Administrator’s notice violations.  See Chao v. Merino, 452 F.3d 174, 185 (2d \n\n 9  Cir. 2006) (“We review the district courtʹs fashioning of equitable remedies \n\n10  under ERISA for abuse of discretion.”).3   \n\n11  As an initial matter, we note that the Plaintiffs do not challenge the \n\n12  District Court’s finding that contract reformation was an appropriate \n\n13  equitable remedy in this case.  Instead, the Plaintiffs argue that, having \n\n\n\n                                                  \n 3 As we have recognized, “[t]he word ‘abuse’ in the ‘abuse of discretion’ standard is \n\n an unfortunate—and inaccurate—term of art” because “abuses of discretion” rarely, \n if ever, involve anything “as heinous as abuse.”  In re City of New York, 607 F.3d \n 923, 943 n.21 (2d Cir. 2010); see also In re Sims, 534 F.3d 117, 132 (2d Cir. 2008) (“A \n district court has abused its discretion if it based its ruling on an erroneous view of \n the law or on a clearly erroneous assessment of the evidence or rendered a decision \n that cannot be located within the range of permissible decisions.” (quotation marks \n omitted)). \n 12 \n  \n  \n\f 1  decided to reform the Plan, the District Court should have chosen a \n\n 2  calculation of New Benefits that was more favorable to them than the new \n\n 3  hire approach.  We are not persuaded.  \n\n 4  Each of the considered equitable approaches for calculating the \n\n 5  Plaintiffs’ benefits has proven to be imperfect.  Indeed, our decision in \n\n 6  Frommert III foreclosed the possibility of applying any of the expected value \n\n 7  methods.  See 738 F.3d at 534.  Meanwhile, although Conkright did not \n\n 8  address equitable remedies, its criticism of the unadjusted value methods as \n\n 9  failing to account for the time value of money is reason enough to disqualify \n\n10  those methods.4  See 559 U.S. at 519.  Nor, as the District Court found, does \n\n11  the no‐offset method, which results in a clear windfall to the Plaintiffs, fare \n\n12  any better as a suitable remedy.  See January 2016 Decision, 153 F. Supp. 3d at \n\n13  613–14.   \n\n\n\n\n                                                  \n 4 The Plaintiffs attempt to distinguish the actual annuity method from the Layaou \n\n method by claiming that the former, an annuity, accounts for the time value of \n money.  But the actual annuity method derives from the unadjusted value of what \n the Plaintiffs could have received as original retirement benefits.  Indeed, as the \n Plaintiffs’ own expert admitted, the actual annuity method and the Layaou method \n produce very similar New Benefits calculations.  See Joint App’x at 330–31; see also \n Joint App’x at 70.   \n 13 \n  \n  \n\f 1  The new hire approach has its own flaws, insofar as it fails to fully \n\n 2  count all years of service at Xerox, with an offset for the prior distributions \n\n 3  made to the Plaintiffs when they first left Xerox, as the parties originally \n\n 4  expected.  See Frommert v. Conkright, 472 F. Supp. 2d 452, 455, 458 \n\n 5  (W.D.N.Y. 2007) (“2007 Decision”).  Nevertheless, the District Court did not \n\n 6  abuse its discretion in selecting the new hire approach as an adequate \n\n 7  equitable remedy.  Among its significant advantages over other potential \n\n 8  remedies, the new hire approach accounts for the time value of money, see \n\n 9  Conkright, 559 U.S. at 519, but avoids the problems associated with the \n\n10  expected value methods described above and in Frommert III, 738 F.3d at 534.  \n\n11  The approach has two more advantages to distinguish it in the context of this \n\n12  litigation.  First, as we explained in Frommert III, the Plaintiffs are entitled to \n\n13  at least the new hire remedy.  Id. at 530–31.  Second, we agree with the \n\n14  District Court that the new hire approach better balances the dueling interests \n\n15  of the Plan Administrator and the Plaintiffs.  See January 2016 Decision, 153 F. \n\n16  Supp. 3d at 610, 612, 614–15. \n\n\n17  In urging a contrary conclusion, the Plaintiffs argue that the District \n\n18  Court improperly refused to consider two alternative theories of equitable \n\n 14 \n  \n  \n\f 1  remedy, surcharge and estoppel.  They claim that one or both theories might \n\n 2  have justified a higher benefits award.  But having determined that the \n\n 3  District Court did not abuse its discretion when it reformed the Plan to grant \n\n 4  the new hire remedy as adequate equitable relief, “we need not address \n\n 5  whether relief would alternatively have been proper pursuant to different \n\n 6  equitable remedies such as surcharge or estoppel.”  Amara v. CIGNA Corp., \n\n 7  775 F.3d 510, 532 (2d Cir. 2014).  And the District Court, far from ignoring \n\n 8  surcharge or estoppel, explicitly described them as “unnecessary.”  January \n\n 9  2016 Decision, 153 F. Supp. 3d at 613. \n\n\n10  The Plaintiffs also argue that the District Court was affirmatively \n\n11  required to interpret the Plan.  They claim that this in turn might have yielded \n\n12  a higher benefits award.  But this argument runs headlong into Frommert III.  \n\n13  There we stated, to the contrary, that the District Court did not need to \n\n14  engage in plan interpretation if it determined that an appropriate equitable \n\n15  remedy existed.  738 F.3d at 534; see DiLaura v. Power Auth., 982 F.2d 73, 76 \n\n16  (2d Cir. 1992) (observing that under the “law of the case” doctrine, “when a \n\n17  court decides upon a rule of law, that decision should continue to govern the \n\n18  same issues in subsequent stages in the same case” (quotation marks \n\n 15 \n  \n  \n\f 1  omitted)).  District courts generally may avoid interpreting a pension plan \n\n 2  and instead fashion equitable remedies for ERISA violations where the plan is \n\n 3  “significantly incomplete” and misleads its employees.  See CIGNA Corp. v. \n\n 4  Amara, 563 U.S. 421, 428, 438–43 (2011).  Under those circumstances, a district \n\n 5  court may, for example, “properly reform[ ] [a pension] plan to reflect the \n\n 6  representations that the defendants made to the plaintiffs.”  Osberg v. Foot \n\n 7  Locker, Inc., 862 F.3d 198, 215 (2d Cir. 2017) (quotation marks omitted).   \n\n\n 8  The Plaintiffs themselves appear to have acknowledged this point.  \n\n 9  They informed the District Court that “[o]nce [the P]laintiffs are granted the \n\n10  equitable relief to which they are entitled for the undisputed notice violations, \n\n11  [the District Court] need not attempt to resolve the plan interpretation issue.”  \n\n12  Memorandum of Points and Authorities In Support of Plaintiffs’ Motion for \n\n13  Entry of Judgment on Notice Issue, dated October 20, 2014, Dist. Ct. Dkt. No. \n\n14  267‐1, at 2.  In this case, the District Court found that there was no reasonable \n\n15  plan interpretation as to which notice had been provided by Xerox.  See \n\n16  January 2016 Decision, 153 F. Supp. 3d at 604–05; 2007 Decision, 472 F. Supp. \n\n17  2d at 457 (noting that “virtually nothing is set forth in either the Plan or the \n\n18  [summary plan description]” to explain how to account for prior \n\n 16 \n  \n  \n\f 1  distributions).  The District Court was therefore entitled to reform the Plan \n\n 2  and employ the new hire approach as an equitable remedy in compliance \n\n 3  with our mandate in Frommert III.  See 738 F.3d at 534.  \n\n\n 4  The District Court’s selection of the new hire remedy falls within the \n\n 5  “range of permissible decisions available under an abuse of discretion \n\n 6  standard.”  Osberg, 862 F.3d at 215 (quotation marks omitted).  For these \n\n 7  reasons, we affirm the District Court’s decision to use the new hire approach \n\n 8  as an equitable remedy to redress the Plan Administrator’s notice violations. \n\n\n 9  2. Prejudgment Interest \n\n10  We next address the District Court’s award of prejudgment interest at \n\n11  the federal prime rate.  As an initial matter, the District Court enjoyed broad \n\n12  discretion to decide whether to award prejudgment interest in this case.  See \n\n13  S.E.C. v. First Jersey Sec., Inc., 101 F.3d 1450, 1476 (2d Cir. 1996).  In exercising \n\n14  such discretion, the District Court had to consider “(i) the need to fully \n\n15  compensate the wronged party for actual damages suffered, (ii) . . . fairness \n\n16  and the relative equities of the award, (iii) the remedial purpose of the statute \n\n17  involved, and/or (iv) such other general principles as are deemed relevant by \n\n18  the court.”  Jones v. UNUM Life Ins. Co. of Am., 223 F.3d 130, 139 (2d Cir. \n 17 \n  \n  \n\f 1  2000) (quotation marks omitted).  Those same factors also inform a district \n\n 2  court’s choice of a particular interest rate,  id., which “must not result in over‐\n\n 3  compensation of the plaintiff,”  Wickham Contracting Co. v. Local Union No. \n\n 4  3, IBEW, 955 F.2d 831, 834 (2d Cir. 1992).  “We have allowed discretionary \n\n 5  awards of prejudgment interest . . . when the awards were fair, equitable and \n\n 6  necessary to compensate the wronged party fully.”  Id. at 835. \n\n 7  In its November 2016 Decision, the District Court concluded that the \n\n 8  Plaintiffs were entitled to prejudgment interest at the federal prime rate.  The \n\n 9  court specifically found that the prime rate of 3.5 percent “strikes an \n\n10  appropriate balance” and “fairly compensate[s]” the Plaintiffs.5  November \n\n11  2016 Decision, 216 F. Supp. 3d at 316.  The court also carefully explained why \n\n12  it rejected the New York statutory rate of nine percent (proposed by the \n\n13  Plaintiffs) as too high and the federal post‐judgment interest rate of 0.66 \n\n14  percent (proposed by the Plan Administrator) as too low.  Id. at 315.  We \n\n15  affirm the District Court’s decision to use the prime rate for three reasons.  \n\n\n\n                                                  \n 5 This decision was clarified in another decision entered on May 4, 2017.  Frommert \n\n v. Conkright, 2017 WL 3867795, at *1 (W.D.N.Y. May 4, 2017).  That decision \n addressed primarily the mechanics of implementing the District Court’s \n prejudgment interest award—mechanics that are not at issue in this appeal. \n 18 \n  \n  \n\f1  First, it had broad discretion to grant prejudgment interest and to select a rate.  \n\n2  Second, it carefully considered all the relevant factors in determining whether \n\n3  prejudgment interest was warranted, and, if so, what the rate should be.  And \n\n4  finally, it thoroughly explained its reasoning for using the federal prime rate. \n\n\n5  CONCLUSION \n\n6  We have considered the Plaintiffs’ remaining arguments and conclude \n\n7  that they are without merit.  For the foregoing reasons, we AFFIRM.  \n\n\n\n\n 19\n[END_CASE]", "role": "user" } ]
8,443,841
Paul J. FROMMERT, Donald S. Foote, Thomas I. Barnes, Ronald J. Campbell, Frank D. Commesso, William F. Coons, James D. Gagnier, Brian L. Gaita, William J. Ladue, Gerald A. Leonardo, Jr., Frank Mawdesley, Harold S. Mitchell, Walter J. Petroff, Richard C. Spring, Patricia M. Johnson, F. Patricia M. Tobin, Nancy A. Revella, Anatoli G. Puschkin, William R. Plummer, Michael J. McCoy, Alan H. Clair, Larry J. Gallagher, Napoleon B. Barbosa, Alexandra Spearman Harrick, Janis A. Edelman, Patricia H. Johnston, Kenneth P. Parnett, Joyce D. Cathcart, Floyd Swaim, Julie A. McMillian, Dennis E. Baines, Ruby Jean Murphy, Matthew D. Alfieri, Irshad Qureshi, Richard C. Crater, Gail J. Levy, John A. Williams, Crystal Thorton, Charles R. Drannbauer, William M. Burritt, Janice Ross Heiler, Joseph McNeil, Thomas F. McGee, Vincent G. Johnson, F. Colt Hitchcock, Ronnie Tabak, Martha Lee Taylor, Kathy Fay Thompson, Mary Beth Allen, Craig Spencer, Linda S. Bourque, Thomas Michael Vasta, Frank C. Darling, Clark C. Dingman, Carol E. Gannon, Joseph E. Wright, David M. Rohan, David B. Ruddock, Charles Hobbs, Charles Zabinski, Charles J. Maddalozzo, Joyce M. Pruett, William A. Craven, Maureen A. Loughlin Jones, Kenneth W. Pietrowski, Bonnie Cohen, Lawrence R. Holland, Gail A. Nasman, Steven D. Barley, Donna S. Lipari, Andrew C. Matteliano, Michael Horrocks, Candice J. White, Kathleen E. Hunter, John L. Crisafulli, Deborah J. Davis, Brenda H. McConnell, Kathleen A. Bowen, Robert P. Caranddo, Terence J. Kurtz, William J. Cheslock, Thomas E. Dalton, Lynn Barnsdale, Bruce D. Craig, Gary P. Hardin, Claudette M. Long, Dale Platteter, Mary Ann Sergeant, Molly White Kehoe, David K. Young, Leslie Ann Wunsch, Richard J. Glikin, Eugene H. Updyke, Michael R. Benson, Alvin M. Adams, Ronnie Kolniak, James J. Farrell, Robert L. Brackhahn, Benjamin C. Roth, Carmen J. Sofia, Kathleen W. Levea, Frederick Scacchitti, Paul Defina, James G. Walls v. Sally L. CONKRIGHT, Xerox Corporation Pension Plan Administrator, Patricia M. Nazementz, Xerox Corporation Pension Plan Administrator, Xerox Corporation, Lawrence M. Becker, Xerox Corporation Plan Administrator, Xerox Corporation Retirement Income Guarantee Plan, Lawrence Becker, Xerox Corporation Plan Administrators
Frommert v. Conkright
2019-01-14
Docket Nos. 17-114-cv(L); 17-738-cv(CON); August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Cabranes, Kearse, Lohier", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415267/", "author_raw": ""}]}
CABRANES
KEARSE
LOHIER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443841/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Paul J. FROMMERT, Donald S. Foote, Thomas I. Barnes, Ronald J. Campbell, Frank D. Commesso, William F. Coons, James D. Gagnier, Brian L. Gaita, William J. Ladue, Gerald A. Leonardo, Jr., Frank Mawdesley, Harold S. Mitchell, Walter J. Petroff, Richard C. Spring, Patricia M. Johnson, F. Patricia M. Tobin, Nancy A. Revella, Anatoli G. Puschkin, William R. Plummer, Michael J. McCoy, Alan H. Clair, Larry J. Gallagher, Napoleon B. Barbosa, Alexandra Spearman Harrick, Janis A. Edelman, Patricia H. Johnston, Kenneth P. Parnett, Joyce D. Cathcart, Floyd Swaim, Julie A. McMillian, Dennis E. Baines, Ruby Jean Murphy, Matthew D. Alfieri, Irshad Qureshi, Richard C. Crater, Gail J. Levy, John A. Williams, Crystal Thorton, Charles R. Drannbauer, William M. Burritt, Janice Ross Heiler, Joseph McNeil, Thomas F. McGee, Vincent G. Johnson, F. Colt Hitchcock, Ronnie Tabak, Martha Lee Taylor, Kathy Fay Thompson, Mary Beth Allen, Craig Spencer, Linda S. Bourque, Thomas Michael Vasta, Frank C. Darling, Clark C. Dingman, Carol E. Gannon, Joseph E. Wright, David M. Rohan, David B. Ruddock, Charles Hobbs, Charles Zabinski, Charles J. Maddalozzo, Joyce M. Pruett, William A. Craven, Maureen A. Loughlin Jones, Kenneth W. Pietrowski, Bonnie Cohen, Lawrence R. Holland, Gail A. Nasman, Steven D. Barley, Donna S. Lipari, Andrew C. Matteliano, Michael Horrocks, Candice J. White, Kathleen E. Hunter, John L. Crisafulli, Deborah J. Davis, Brenda H. McConnell, Kathleen A. Bowen, Robert P. Caranddo, Terence J. Kurtz, William J. Cheslock, Thomas E. Dalton, Lynn Barnsdale, Bruce D. Craig, Gary P. Hardin, Claudette M. Long, Dale Platteter, Mary Ann Sergeant, Molly White Kehoe, David K. Young, Leslie Ann Wunsch, Richard J. Glikin, Eugene H. Updyke, Michael R. Benson, Alvin M. Adams, Ronnie Kolniak, James J. Farrell, Robert L. Brackhahn, Benjamin C. Roth, Carmen J. Sofia, Kathleen W. Levea, Frederick Scacchitti, Paul Defina, James G. Walls v. Sally L. CONKRIGHT, Xerox Corporation Pension Plan Administrator, Patricia M. Nazementz, Xerox Corporation Pension Plan Administrator, Xerox Corporation, Lawrence M. Becker, Xerox Corporation Plan Administrator, Xerox Corporation Retirement Income Guarantee Plan, Lawrence Becker, Xerox Corporation Plan Administrators\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-14\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
8,443,923
Dr. Robert D. HAAR, M.D. v. NATIONWIDE MUTUAL FIRE INSURANCE COMPANY, John And Jane Doe Corps., 1-10, John and Jane Doe 1-10
Haar v. Nationwide Mut. Fire Ins. Co.
2019-01-15
Docket No. 18-128; August Term, 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Hall, Katzmann, Lynch", "parties": "", "opinions": [{"author": "PER CURIAM", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415354/", "author_raw": "PER CURIAM"}]}
HALL
KATZMANN
LYNCH
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443923/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Dr. Robert D. HAAR, M.D. v. NATIONWIDE MUTUAL FIRE INSURANCE COMPANY, John And Jane Doe Corps., 1-10, John and Jane Doe 1-10\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-15\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,583,695
Lockwood v. Commissioner
2019-01-23
17-2591-cv
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: CABRANES and POOLER, Circuit Judges, and OETKEN, District Judge.", "parties": "", "opinions": [{"type": "010combined", "text": "17‐2591‐cv    \nLockwood v. Commissioner \n\n\n\n\n In the \n\n\n United States Court of Appeals\n for the Second Circuit\n      \n \n \n AUGUST TERM 2018 \n  \n No. 17‐2591‐cv \n  \n STEPHEN LOCKWOOD, \n Plaintiff‐Appellant, \n \n v. \n \n COMMISSIONER OF SOCIAL SECURITY ADMINISTRATION, \n Defendant‐Appellee. \n      \n  \n On Appeal from the United States District Court \n for the Northern District of New York \n      \n \n SUBMITTED: AUGUST 15, 2018 \n DECIDED: JANUARY 23, 2019 \n      \n \n\fBefore: CABRANES and POOLER, Circuit Judges, and OETKEN, District \nJudge.*  \n\n      \n\n Plaintiff‐Appellant  Stephen  Lockwood  appeals  from  a \njudgment of the United States District Court for the Northern District \nof New York (Christian F. Hummel, Magistrate Judge), upholding the \ndecision  of  Defendant‐Appellee  Commissioner  of  Social  Security  to \ndeny  his  application  for  disability  insurance  benefits.    We  conclude \nthat  the  Commissioner’s  decision  was  not  supported  by  substantial \nevidence because it relied on testimony from a vocational expert that \nappeared to be in conflict with the authoritative guidance set out in the \nDepartment  of  Labor’s  Dictionary  of  Occupational  Titles.    Because  the \nCommissioner was not entitled to rely on this testimony without first \nidentifying and inquiring into the apparent conflict, the District Court \nerred in declining to set aside the Commissioner’s benefits decision. \n\n Accordingly, we REVERSE the District Court’s judgment and \nREMAND for further proceedings. \n\n      \n\n          Patrick G. Radel, Getnick Livingston \n Atkinson & Priore, LLP, Utica, NY, for \n Plaintiff‐Appellant. \n\n\n *  Judge J. Paul Oetken, of the United States District Court for the Southern \nDistrict of New York, sitting by designation. \n\n\n\n\n 2 \n\f Andreea L. Lechleitner, Special Assistant \n United States Attorney, (Stephen P. Conte, \n Regional Chief Counsel – Region II, on the \n brief), Office of the General Counsel, United \n States Social Security Administration, New \n York, NY, for Grant C. Jaquith, United States \n Attorney for the Northern District of New \n York, Syracuse, NY, for Defendant‐Appellee. \n\n      \n\nJ. PAUL OETKEN, District Judge: \n\n Plaintiff‐Appellant Stephen Lockwood appeals from a June 21, \n2017  judgment  of  the  United  States  District  Court  for  the  Northern \nDistrict  of  New  York  (Christian  F.  Hummel,  Magistrate  Judge), \nupholding  the  decision  of  Defendant‐Appellee  Commissioner  of \nSocial Security (“Commissioner”) to deny Lockwood’s application for \ndisability  insurance  benefits.    On  appeal,  Lockwood  argues  among \nother things that the District Court should have set aside the benefits \ndenial  as  unsupported  by  substantial  evidence  because  the  denial \nrelied  on  expert  testimony  that  contained  an  unexamined  apparent \nconflict  with  an  authoritative  Department  of  Labor  publication,  the \nDictionary  of  Occupational  Titles.    We  agree  with  Lockwood  on  this \npoint  and  therefore  REVERSE  the  District  Court’s  judgment  and \nREMAND for further proceedings.   \n\n\n\n\n 3 \n\f I. BACKGROUND \n\n A. Factual Background \n\n On November 11, 2011, Lockwood was injured in an automobile \naccident  while  working  as  a  landscaper.    In  the  following  months, \nLockwood  experienced  abnormal  sensation  in  his  hands  and  severe \npain in his neck and was, according to Drs. Srinivasan Mani and Mark \nSmith, disabled from performing his regular job as a consequence.  In \nterms  of  diagnosis,  the  doctors  believed  that  the  unusual  feeling  in \nLockwood’s hands might be a result of carpal tunnel syndrome and \nthat  the  neck  pain  might  be  attributable  to  herniated  disks  in \nLockwood’s cervical spine. \n\n To  address  the  neck  pain,  Dr.  Smith  advised  Lockwood  to \nundergo  disk‐repair  surgery.    Dr.  Richard  Tallarico,  an  orthopedic", "author": "J. PAUL OETKEN, District Judge:"}, {"type": "concurrence", "author": "surgeon", "text": "surgeon,  concurred  in  this  advice,  and  he  performed  the \nrecommended surgery on November 7, 2012.   \n\n Following the surgery, Lockwood consulted several times with \nNurse  Practitioner  Catherine  Tomaiuoli.    In  an  early  consultation, \nNurse Tomaiuoli observed that Lockwood’s neck pain persisted and \nthat he had a reduced range of motion in his left shoulder, as well as \ndifficulty  with  certain  arm  movements.    She  recommended  that \nLockwood  receive  a  magnetic  resonance  imaging  (“MRI”)  scan  and \nthat he restrict the amount of weight he lifted.   \n\n In June 2013, Lockwood received the recommended MRI.  Based \non  the  results,  Nurse  Tomaiuoli  referred  Lockwood  to  Dr.  John \n\n\n\n\n 4 \n\fCannizzaro, an orthopedic surgeon, who examined Lockwood and on \nJuly 16, 2013, concluded that his shoulder was 30% disabled.  During \na  subsequent  consultation,  Dr.  Tallarico,  the  surgeon  who  had \noperated on Lockwood’s neck, deemed Lockwood to be 75% impaired \nas a result of his continuing neck and shoulder pain and his limited \nrange of motion.  Dr. Tallarico considered Lockwood’s disability to be \npermanent.   \n\n Meanwhile,  Lockwood  was  following  up  on  his  doctors’ \nsuggestion that he suffered from carpal tunnel syndrome.  On May 22, \n2013, he received carpal tunnel release surgery on his right wrist from \nDr.  Kevin  Setter.    During  a  follow‐up  examination  with  Nurse \nPractitioner Carmelita Woods, however, Lockwood reported that he \nwas  continuing  to  experience  tenderness  and  abnormal  sensation  in \nhis hands.  After examining Lockwood, Nurse Woods concluded that \nLockwood had 50% and 25% impairments in his right and left hands, \nrespectively,  and  that  carpal  tunnel  release  surgery  on  the  left  hand \nwould  be  appropriate.    Dr.  Setter  performed  that  surgery  on  July  1, \n2013.   \n\n B. Administrative Proceedings \n\n On  July  26,  2013,  Lockwood  submitted  an  application  to  the \nCommissioner pursuant to the Social Security Act, 42 U.S.C. § 301 et \nseq.,  seeking  disability  insurance  benefits  as  of  the  date  of  his \nautomobile  accident.    At  the  Commissioner’s  request,  Lockwood \nreceived  an  examination  from  orthopedist  Dr.  Tanya  Perkins‐\nMwantuali.    The  doctor  found  that  Lockwood  had  “moderate \n\n\n\n\n 5 \n\flimitation  with  lifting,  pushing,  pulling,  reaching  forward  and \nreaching above the level of the shoulder, and carrying with the use of \nthe left arm.”  Admin. Record (“R.”) 330.1  She also determined that \nLockwood had mild to moderate limitations with respect to activities \nthat require a full range of neck motion.  Following this assessment, \nthe Commissioner denied Lockwood’s benefits application.  \n\n Lockwood  then  requested  a  hearing  before  an  Administrative \nLaw  Judge  (“ALJ”).    At  the  resultant  June  2,  2014  hearing,  the  ALJ \nheard testimony from Lockwood and from Dian Heller, a vocational \nexpert.  Heller offered her opinion that a person of Lockwood’s age, \neducation, and experience could perform the physical tasks associated \nwith  three  specific  jobs  that  collectively  number  around  154,000 \nnationally, as long as he retained the ability to perform light work that \ndid not require any overhead reaching. \n\n On October 27, 2014, the ALJ issued a written opinion denying \nbenefits.  Although the ALJ found that Lockwood suffered from severe \nimpairments,  she  concluded  that  he  was  nonetheless  capable  of \nperforming certain physical activities that, among other things, did not \ninvolve  any  “overhead  reaching.”    R.  19–20.    Relying  on  Heller’s \ntestimony  regarding  the  three  jobs  that  people  with  comparable \nlimitations are capable of performing, and finding that these jobs exist \nin significant number in the national economy, the ALJ concluded that \nLockwood was not entitled to benefits.  \n\n\n  The Administrative Record is available at Docket Number 8 of the District \n 1\n\nCourt docket.  Lockwood v. Commissioner, No. 6:16‐CV‐0648 (N.D.N.Y.). \n\n\n\n\n 6 \n\f Lockwood  sought  review  from  the  Social  Security  Appeals \nCouncil.  The Appeals Council granted review and, in a May 3, 2016 \ndecision, adopted the ALJ’s opinion as its own in all relevant respects.  \nWith that decision, the Commissioner’s denial of Lockwood’s benefits \napplication became final. \n\n C. Federal Court Proceedings \n\n Dissatisfied by the result of the agency proceedings, Lockwood \nturned to federal court.  On June 7, 2016, Lockwood filed a complaint \nin  the  United  States  District  Court  for  the  Northern  District  of  New \nYork,  seeking  review  of  the  benefits  denial.    See  42  U.S.C.  § 405(g) \n(authorizing  judicial  review  of  the  Commissioner’s  final  decisions).  \nFollowing  submission  of  the  administrative  record,  both  Lockwood \nand the Commissioner moved for judgment on the pleadings. \n\n In support of his motion, Lockwood advanced two arguments \nthat  are  relevant  here.    First,  he  argued  that  the  Commissioner  had \nrelied  on  Heller’s  testimony  without  first  probing  into  an  apparent \nconflict  between  that  testimony  and  an  authoritative  Department  of \nLabor  publication,  the  Dictionary  of  Occupational  Titles  (the \n“Dictionary”).2  Specifically, he pointed out that Heller had identified \nthree jobs capable of being performed by a person who cannot reach \noverhead,  but  that  the  Dictionary’s  descriptions  of  these  jobs  state \nwithout  qualification  that  each  requires  “reaching.”    Second,  he \n\n 2  This opinion’s references to the Dictionary also include where relevant the \nDictionary’s  companion  publication,  the  Selected  Characteristics  of  Occupations \nDefined in the Revised Dictionary of Occupational Titles.  \n\n\n\n\n 7 \n\fargued that the Commissioner, in assessing his physical capabilities, \nfailed  to  address  Nurse  Woods’s  observation  that  he  had  respective \nimpairments of 50% and 25% in his right and left hands. \n\n The District Court rejected both of Lockwood’s arguments.  As \nfor the first argument, the District Court held that even if there had \nbeen  a  conflict  between  Heller’s  testimony  and  the  Dictionary,  the \nconflict was “reconciled because [Heller’s] testimony indicate[d] that \nshe  based  her  opinion  on  her  own  experience  observing  the \nperformance of the identified jobs.”  Lockwood v. Comm’r of Soc. Sec., \nNo.  6:16‐CV‐0648,  2017  WL  2656194,  at  *5  (N.D.N.Y.  June  20,  2017).  \nTherefore,  it  was  “possible  to  reasonably  infer”  that  Heller’s \nexperience was her basis for testifying “that [Lockwood] would be able \nto perform [the jobs in question] despite a limitation for avoidance of \noverhead reaching,” notwithstanding any contrary indications in the \nDictionary.  Id. \n\n As  for  Lockwood’s  second  argument,  the  District  Court  held \nthat the omission of Nurse Woods’s opinion had been harmless.  See \nid. at *6–8.  In the District Court’s view, Nurse Woods’s opinion was \n“ambiguous as to what precisely [Lockwood] is limited to doing with \nhis hands” and so did not undermine the Commissioner’s conclusion \nthat Lockwood could perform the jobs Heller had identified.  Id. at *7.   \n\n Having  so  reasoned,  the  District  Court  granted  the \nCommissioner’s  motion  for  judgment  on  the  pleadings  and  denied \nLockwood’s.  This appeal followed. \n\n\n\n\n 8 \n\f II. DISCUSSION \n\n On  appeal,  Lockwood  renews  his  arguments  that  the  benefits \ndenial  must  be  set  aside  because  the  Commissioner  (1)  failed  to \nexamine  an  apparent  conflict  between  Heller’s  testimony  and  the \nDictionary and (2) failed to address Nurse Woods’s opinion regarding \nLockwood’s hand impairments.  We agree with Lockwood on the first \npoint and therefore reverse the District Court’s judgment and remand \nfor further proceedings.  In light of that holding, we need not address \nLockwood’s second argument. \n\n A. Standard of Review \n\n We  may  reverse  the  District  Court’s  decision  to  uphold  the \nCommissioner’s denial of benefits only if our “plenary review of the \nadministrative  record”  reveals  that  “the  [Commissioner’s]  factual \nfindings  are  not  supported  by  ‘substantial  evidence’”  or  that  “the \n[benefits] decision is based on legal error.”  Shaw v. Chater, 221 F.3d \n126, 131 (2d Cir. 2000) (quoting 42 U.S.C. § 405(g)). \n\n B. Analysis \n\n Our analysis begins and ends with Lockwood’s argument that \nthe Commissioner’s finding that he is capable of performing the three \njobs  identified  by  Heller  was  not  based  on  substantial  evidence.    In \nLockwood’s view, the evidence upon which the Commissioner relied \nin  determining  what  physical  demands  those  jobs  entail—Heller’s \ntestimony—cannot constitute substantial evidence because it contains \nan  apparent,  unresolved  conflict  with  the  Dictionary.    We  agree  and \n\n\n\n\n 9 \n\ftherefore  conclude  that  the  District  Court  erred  in  declining  to  set \naside the Commissioner’s benefits denial. \n\n Under  the  Social  Security  Act,  a  claimant  is  ineligible  for \ndisability insurance benefits unless, among other things, he suffers an \nimpairment “of such severity that he . . . cannot, considering his age, \neducation, and work experience, engage in any . . . kind of substantial \ngainful  work  which  exists  in  the  national  economy.”    42  U.S.C. \n§ 423(d)(2)(A);  see  also  id.  § 423(a)(1)(E).    Accordingly,  even  where  a \nclaimant  is  impaired  to  the  point  that  he  can  no  longer  perform  his \nprevious  work,  the  Commissioner  may  properly  deny  benefits  if, \nconsidering  the  claimant’s  “residual  functional  capacity”—i.e.,  his \nphysical  capabilities  notwithstanding  his  impairment,  20  C.F.R. \n§ 404.1545—“and  [his]  age,  education,  and  work  experience,”  the \nclaimant  “can  make  an  adjustment  to  other  work,”  id. \n§ 404.1520(a)(4)(v).  If benefits are denied on this basis, however, the \nCommissioner bears the burden of “show[ing] that there is work in the \nnational economy that the claimant can do.”  Poupore v. Astrue, 566 F.3d \n303, 306 (2d Cir. 2009) (per curiam). \n\n A  2000  Social  Security  Administration  Policy  Interpretation \nRuling  (the  “Ruling”)  governs  the  Commissioner’s  assessment  of \nwhether  any  particular  job  can  accommodate  a  given  claimant’s \nphysical  limitations.    Under  the  Ruling,  the  Commissioner  “rel[ies] \nprimarily  on  the  [Dictionary]  . . .  for  information  about  the  [job’s] \nrequirements”  but  “may  also  use  [vocational  experts]  . . .  to  resolve \ncomplex vocational issues.”  SSR 00‐4p, 2000 WL 1898704, at *2 (Dec. \n4,  2000).    If  the  Commissioner  does  consider  the  testimony  of  such \n\n\n\n\n 10 \n\fexperts,  however,  she  must  be  alert  to  the  possibility  of  “apparent \nunresolved conflict[s]” between the testimony and the Dictionary.  Id.  \nIn light of this possibility, the Ruling tasks the Commissioner with “an \naffirmative responsibility to ask about any possible conflict,” id. at *4, \nand to “elicit a reasonable explanation for [any such] conflict before \nrelying on the [vocational expert’s testimony],” id. at *2. \n\n  Lockwood now argues, as he did in the District Court, that the \nCommissioner  in  this  case  neglected  the  Ruling’s  requirements.    In \ndenying  Lockwood’s  benefits  application,  the  Commissioner \nconcluded that Lockwood was “not disabled” within the meaning of \nthe  Social  Security  Act  because  “there  [were]  jobs  that  exist[ed]  in \nsignificant numbers in the national economy that [he could] perform.”  \nR.  6–7.    The  Commissioner  reasoned  that  even  though  Lockwood \nsuffered  an  impairment  that  required  him  to  “avoid  all  overhead \nreaching tasks,” Heller’s testimony had established that at least three \nspecific jobs existing collectively in significant number in the national \neconomy would accommodate this limitation.  R. 6.  But, as Lockwood \npoints  out,  the  Dictionary  establishes  that  each  of  these  three  jobs \nrequires  occasional  or  frequent  “reaching.”    See  Dictionary  of \nOccupational Titles 295.357‐018, 1991 WL 672589; id. 205.367‐014, 1991 \nWL  671715;  id.  729.684‐054,  1991  WL  679729.    And  because  a  1985 \nSocial  Security  Program  Policy  Statement  defines  “reaching”  as \n“extending the hands and arms in any direction,” SSR 85‐15, 1985 WL \n56857,  at  *7  (Jan.  1,  1985)  (emphasis  added),  Lockwood  goes  on,  the \nDictionary raises a potential inconsistency with Heller’s testimony that \na  claimant  with  a  restriction  on  overhead  reaching  is  capable  of \n\n\n\n\n 11 \n\fperforming  the  three  jobs  at  issue.    In  his  view,  then,  the  Ruling \nrequired  the  Commissioner  to  probe  this  apparent  conflict  before \nrelying on Heller’s testimony. \n\n We agree.  As the Fourth Circuit has persuasively explained, the \nRuling mandates that whenever the Commissioner intends to “rely[] \non  [a]  vocational  expert’s  testimony,”  she  must  identify  and  inquire \ninto all those areas “where the expert’s testimony seems to . . . conflict \nwith the Dictionary.”  Pearson v. Colvin, 810 F.3d 204, 209 (4th Cir. 2015) \n(emphasis  added).    In  other  words,  the  Ruling  requires  the \nCommissioner  to  “obtain  a  reasonable  explanation”  for  any \n“apparent”—even if non‐obvious—conflict between the Dictionary and \na vocational expert’s testimony.3  SSR 00‐4p, 2000 WL 1898704, at *2 \n(emphasis  added).    In  both  the  1985  Policy  Statement  and  common \nusage, “reaching” includes overhead reaching.  Cf. Selian v. Astrue, 708 \nF.3d 409, 422 (2d Cir. 2013) (per curiam) (suggesting that the inability \nto reach above one’s head may be inconsistent with a job that requires \nreaching).    Testimony  that  a  claimant  with  overhead  reaching \nlimitations is capable of performing a job that the Dictionary describes \nas requiring “reaching,” then, creates at least an apparent conflict that \ntriggers the Commissioner’s duty to elicit an explanation that would \njustify crediting the testimony.  See, e.g., Prochaska v. Barnhart, 454 F.3d \n731, 736 (7th Cir. 2006) (describing such testimony as raising “exactly \n\n\n 3  To the extent that other courts have understood the Ruling’s reference to \nan “apparent conflict” to refer to a conflict that is “obvious,” see, e.g., Gutierrez v. \nColvin, 844 F.3d 804, 808–09 (9th Cir. 2016), we respectfully disagree for the reasons \nthe Fourth Circuit has cogently articulated, see Pearson, 810 F.3d at 209–10. \n\n\n\n\n 12 \n\fthe sort of inconsistency the [Commissioner] should . . . resolve[]”); see \nalso Pearson, 810 F.3d at 210–11 (similar); Kemp ex rel. Kemp v. Colvin, \n743 F.3d 630, 632–33 (8th Cir. 2014) (similar). \n\n The Commissioner’s arguments to the contrary do not persuade \nus.    First,  she  suggests  that  there  is  no  conflict  between  the  expert \ntestimony  and  the  Dictionary  because  describing  a  job  as  requiring \n“reaching”  does  not  necessarily  establish  that  it  requires  overhead \nreaching.  See Gutierrez v. Colvin, 844 F.3d 804, 808–09 (9th Cir. 2016); \nsee also Segovia v. Astrue, 226 F. App’x 801, 804 (10th Cir. 2007) (“[E]ven \na  job  requiring  frequent  reaching  does  not  necessarily  require  more \nthan occasional overhead reaching.” (emphasis in original)).  But while \n“this Court could guess” what the three jobs Heller identified “require \nin reality, it [was] the [Commissioner’s] duty to elicit an explanation \nfrom  [Heller]  as  to  whether  th[ose]  occupations  actually  require  . . . \noverhead  reaching.”    Spears  v.  Colvin,  No.  15‐CV‐6236,  2016  WL \n4973890, at *5 (W.D.N.Y. Sept. 19, 2016).  The importance of teasing out \nsuch details is precisely why the Commissioner bears an “affirmative \nresponsibility” to ask about “any possible conflict between [vocational \nexpert] evidence and information provided in the [Dictionary].”  SSR \n00‐4p,  2000  WL  1898704,  at  *4  (emphasis  added).    Absent  such  an \ninquiry, the Commissioner lacks a substantial basis for concluding that \nno such conflicts in fact exist.  See Washington v. Comm’r of Soc. Sec., 906 \nF.3d 1353, 1366 (11th Cir. 2018) (“We take the word ‘apparent’ [as used \nin the Ruling] to mean ‘seeming real or true, but not necessarily so.’” \n(quoting Pearson, 810 F.3d at 209)). \n\n\n\n\n 13 \n\f Second,  the  Commissioner  contends  that  the  Dictionary’s \nnarrative  descriptions  of  the  three  jobs  at  issue  contain  no  express \nreference to overhead reaching.  Thus, the Commissioner invites us to \ndisregard  the  apparent  conflict  between  Heller’s  testimony  and  the \nphysical  requirements  enumerated  in  the  Dictionary’s  occupational \ndescriptions.  See Burgess v. Colvin, No. 13‐CV‐6177, 2014 WL 1875360, \nat *13 (W.D.N.Y. May 9, 2014) (consulting the narrative descriptions of \ncertain  jobs  requiring  “reaching”  to  conclude  that  the  jobs  are \nconsistent  with  an  overhead‐reaching  limitation).    This  argument, \nthough,  fails  for  essentially  the  reasons  given  above.    While  the \nDictionary’s  narrative  descriptions certainly  make it  conceivable that \nthe three jobs Heller identified do not require overhead reaching, the \nCommissioner bore the burden of showing that Lockwood is actually \ncapable of performing those jobs.  See Poupore, 566 F.3d at 306.  If the \nCommissioner  wished  to  rely  on  Heller’s  expert  testimony  to  carry \nthat burden, the Ruling makes clear that she was obliged to identify \nand  resolve  the  apparent  conflict  between  that  testimony  and  the \nDictionary,  even  if  there  is  a  chance  that,  upon  inquiry,  no  actual \nconflict would have emerged.4 \n\n\n\n 4 For the same reason, we decline to follow the District Court in “infer[ring]” \nthat Heller’s personal observations of the jobs about which she testified led her to \nconclude  that  those  jobs  do  not  entail  overhead  reaching.    Lockwood,  2017  WL \n2656194,  at  *5.    While  Heller’s  observations  may  well  explain  the  apparent \ndiscrepancy between her testimony and the Dictionary, the fact remains that it is the \nCommissioner’s responsibility to “obtain a reasonable explanation” for any such \ndiscrepancies, and not this Court’s obligation to concoct one post hoc.  SSR 00‐4p, \n2000 WL 1898704, at *1. \n\n\n\n\n 14 \n\f Third and finally, the Commissioner argues that even if—as we \nhave  now  concluded—the  apparent  conflict  between  Heller’s \ntestimony and the Dictionary triggered her duty to probe further, the \nALJ adequately carried out that duty.  After Heller had identified three \njobs  that,  in  her  view,  a  person  with  Lockwood’s  limitations  could \nperform, the ALJ asked whether this opinion “was consistent with [the \nDictionary].”    R.  41.    Heller  replied,  in  relevant  part,  “It  is.”    Id.  \nAccording to the Commissioner, this exchange operated to resolve any \napparent conflict. \n\n  We disagree.  As the Eleventh Circuit has recently explained, \nthe Commissioner’s duty “to identify and resolve apparent conflicts \nbetween [the Dictionary] and [vocational expert] testimony . . . is not \nfulfilled simply by taking the [vocational expert] at his word that his \ntestimony comports with the [Dictionary] when the record reveals an \napparent conflict.”  Washington, 906 F.3d at 1362.  Rather, the Ruling \nplaces  the  onus  on  the  Commissioner,  acting  through  her  ALJs,  to \naffirmatively “[i]dentify” any conflicts.  SSR 00‐4p, 2000 WL 1898704, \nat  *1.    Allowing  the  Commissioner  to  fulfill  this  obligation  through \n“catch‐all question[s]” like the one the ALJ posed during Lockwood’s \nhearing would essentially shunt the Commissioner’s “duty to identify, \nexplain and resolve” apparent conflicts onto the testifying expert.  Patti \nv.  Colvin,  No.  13‐CV‐1123,  2015  WL  114046,  at  *6  (W.D.N.Y.  Jan.  8, \n2015).  Particularly in light of “[t]he inquisitorial nature of disability \nhearings”—in which claimants often appear pro se—we agree with the \nEleventh  Circuit  that  the  Ruling  must  be  read  to  “impose[]  an \nindependent,  affirmative  obligation  on  the  part  of  the  ALJ  to \n\n\n\n\n 15 \n\fundertake  a  meaningful  investigatory  effort  to  uncover  apparent \nconflicts, beyond merely asking the [vocational expert] if there is one.”  \nWashington, 906 F.3d at 1364. \n\n In  the  end,  the  Commissioner  failed  to  reconcile  Heller’s \ntestimony  that  a  person  with  an  overhead  reaching  limitation  can \nperform  the  three  jobs  at  issue  here  with  the  Dictionary’s  indication \nthat all three jobs require “reaching.”  Heller’s testimony cannot, then, \nrepresent  substantial  evidence  capable  of  demonstrating  that \nLockwood can successfully perform work in the national economy.  It \nmay well be that the apparent conflict between Heller’s testimony and \nthe  Dictionary  is  susceptible  to  easy  resolution—if,  for  example,  the \nreaching  involved  in  the  three  jobs  at  issue  consists  exclusively  of \nlateral or downward reaching.  But it is not our role to speculate as to \nhow  or  whether  that  conflict  might  have  been  resolved  had  the \nCommissioner  carried  out  her  responsibility  to  probe  such  matters.  \nInstead, we must reverse and remand for further proceedings so that \nthe Commissioner may have the opportunity to conduct the requisite \ninquiry in the first instance. \n\n In  light  of  this  result,  the  Court  has  no  occasion  to  reach \nLockwood’s argument that the Commissioner failed to address Nurse \nWoods’s opinion regarding Lockwood’s hand impairments.  Neither \nthe ALJ nor the Appeals Council explicitly addressed Nurse Woods’s \nopinion  when  denying  Lockwood’s  benefits  application.    See  R.  4–7, \n17–24.    The  Commissioner  maintains  that  this  omission  is  of  no \nmoment:    She  argues  that  the  record  makes  clear  that  the  nurse’s \nopinion was in fact considered, if not explicitly remarked upon, and \n\n\n\n\n 16 \n\fthat any failure to consider the opinion would have been harmless in \nany event.  Lockwood disagrees on both points.  Because Lockwood’s \ncase  must  return  to  the  agency  either  way  for  the  reasons  already \ngiven,  the  Commissioner  will  have  the  opportunity  on  remand  to \nobviate  this  dispute  altogether  by  giving  express  consideration  to \nNurse Woods’s opinion and by making clear what, if any, weight it \nmerits. \n\n III. CONCLUSION \n\n  To  summarize,  we  hold  that  the  District  Court  erred  in \ndetermining that substantial evidence supported the Commissioner’s \ndenial of Lockwood’s disability insurance benefits application.  This is \nbecause  the  Commissioner’s  denial  was  based  on  evidence  that \ncontained  an  apparent  conflict  with  the  Dictionary’s  authoritative \nguidance, and yet the Commissioner failed to take any steps to explore \nor resolve that conflict.  In light of this holding, we decline to address \nLockwood’s argument that reversal is independently warranted as a \nconsequence  of  the  Commissioner’s  failure  to  expressly  consider \nNurse Woods’s medical opinion. \n\n For  the  foregoing  reasons,  we  REVERSE  the  District  Court’s \njudgment and REMAND for further proceedings.  \n\n\n\n\n 17"}]}
CABRANES
POOLER
OETKEN
1
{"CABRANES": ", Circuit", "POOLER": ", Circuit", "OETKEN": ", District"}
2
0
0
1
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583695/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Lockwood v. Commissioner\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-23\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\n17‐2591‐cv    \nLockwood v. Commissioner \n\n\n\n\n In the \n\n\n United States Court of Appeals\n for the Second Circuit\n      \n \n \n AUGUST TERM 2018 \n  \n No. 17‐2591‐cv \n  \n STEPHEN LOCKWOOD, \n Plaintiff‐Appellant, \n \n v. \n \n COMMISSIONER OF SOCIAL SECURITY ADMINISTRATION, \n Defendant‐Appellee. \n      \n  \n On Appeal from the United States District Court \n for the Northern District of New York \n      \n \n SUBMITTED: AUGUST 15, 2018 \n DECIDED: JANUARY 23, 2019 \n      \n \n\fBefore: CABRANES and POOLER, Circuit Judges, and OETKEN, District \nJudge.*  \n\n      \n\n Plaintiff‐Appellant  Stephen  Lockwood  appeals  from  a \njudgment of the United States District Court for the Northern District \nof New York (Christian F. Hummel, Magistrate Judge), upholding the \ndecision  of  Defendant‐Appellee  Commissioner  of  Social  Security  to \ndeny  his  application  for  disability  insurance  benefits.    We  conclude \nthat  the  Commissioner’s  decision  was  not  supported  by  substantial \nevidence because it relied on testimony from a vocational expert that \nappeared to be in conflict with the authoritative guidance set out in the \nDepartment  of  Labor’s  Dictionary  of  Occupational  Titles.    Because  the \nCommissioner was not entitled to rely on this testimony without first \nidentifying and inquiring into the apparent conflict, the District Court \nerred in declining to set aside the Commissioner’s benefits decision. \n\n Accordingly, we REVERSE the District Court’s judgment and \nREMAND for further proceedings. \n\n      \n\n          Patrick G. Radel, Getnick Livingston \n Atkinson & Priore, LLP, Utica, NY, for \n Plaintiff‐Appellant. \n\n\n *  Judge J. Paul Oetken, of the United States District Court for the Southern \nDistrict of New York, sitting by designation. \n\n\n\n\n 2 \n\f Andreea L. Lechleitner, Special Assistant \n United States Attorney, (Stephen P. Conte, \n Regional Chief Counsel – Region II, on the \n brief), Office of the General Counsel, United \n States Social Security Administration, New \n York, NY, for Grant C. Jaquith, United States \n Attorney for the Northern District of New \n York, Syracuse, NY, for Defendant‐Appellee. \n\n      \n\nJ. PAUL OETKEN, District Judge: \n\n Plaintiff‐Appellant Stephen Lockwood appeals from a June 21, \n2017  judgment  of  the  United  States  District  Court  for  the  Northern \nDistrict  of  New  York  (Christian  F.  Hummel,  Magistrate  Judge), \nupholding  the  decision  of  Defendant‐Appellee  Commissioner  of \nSocial Security (“Commissioner”) to deny Lockwood’s application for \ndisability  insurance  benefits.    On  appeal,  Lockwood  argues  among \nother things that the District Court should have set aside the benefits \ndenial  as  unsupported  by  substantial  evidence  because  the  denial \nrelied  on  expert  testimony  that  contained  an  unexamined  apparent \nconflict  with  an  authoritative  Department  of  Labor  publication,  the \nDictionary  of  Occupational  Titles.    We  agree  with  Lockwood  on  this \npoint  and  therefore  REVERSE  the  District  Court’s  judgment  and \nREMAND for further proceedings.   \n\n\n\n\n 3 \n\f I. BACKGROUND \n\n A. Factual Background \n\n On November 11, 2011, Lockwood was injured in an automobile \naccident  while  working  as  a  landscaper.    In  the  following  months, \nLockwood  experienced  abnormal  sensation  in  his  hands  and  severe \npain in his neck and was, according to Drs. Srinivasan Mani and Mark \nSmith, disabled from performing his regular job as a consequence.  In \nterms  of  diagnosis,  the  doctors  believed  that  the  unusual  feeling  in \nLockwood’s hands might be a result of carpal tunnel syndrome and \nthat  the  neck  pain  might  be  attributable  to  herniated  disks  in \nLockwood’s cervical spine. \n\n To  address  the  neck  pain,  Dr.  Smith  advised  Lockwood  to \nundergo  disk‐repair  surgery.    Dr.  Richard  Tallarico,  an  orthopedic\n[END_CASE]", "role": "user" } ]
8,443,853
Stephen LOCKWOOD v. COMMISSIONER OF SOCIAL SECURITY ADMINISTRATION
Lockwood v. Comm'r of Soc. Sec. Admin.
2019-01-23
No. 17-2591-cv; August Term 2018
U.S. Court of Appeals for the Second Circuit
{"judges": "Cabranes, Oetken, Pooler", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415280/", "author_raw": ""}]}
CABRANES
OETKEN
POOLER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443853/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Stephen LOCKWOOD v. COMMISSIONER OF SOCIAL SECURITY ADMINISTRATION\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-23\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,584,699
United States v. Donald Ray Boles
2019-01-25
17-1138-cr
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: WESLEY, CHIN, AND CARNEY, Circuit Judges.", "parties": "", "opinions": [{"author": "CHIN, Circuit Judge:", "type": "010combined", "text": "17‐1138‐cr \nUnited States v. Donald Ray Boles \n  \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n\n August Term 2017 \n\n (Argued: April 16, 2018                  Decided: January 25, 2019) \n  \n Docket No. 17‐1138‐cr \n\n            \n\n UNITED STATES OF AMERICA, \n                Appellee, \n \n ‐ against ‐ \n\n DONALD RAY BOLES,  \n Defendant‐Appellant. \n\n            \n\n ON APPEAL FROM THE UNITED STATES DISTRICT COURT \n FOR THE DISTRICT OF VERMONT \n  \nBefore: \n WESLEY, CHIN, AND CARNEY, Circuit Judges. \n  \n    Appeal from a judgment of the United States District Court for the \n\nDistrict of Vermont (Sessions, J.) convicting defendant‐appellant, following a jury \n\ntrial, of one count of possessing child pornography and sentencing him \n\nprincipally to 120 monthsʹ imprisonment followed by ten yearsʹ supervised \n\f  \n\n\nrelease.  On appeal, defendant‐appellant raises three principal challenges:  (1) the \n\ndistrict court erred in denying his motion to suppress evidence of child \n\npornography seized at his home pursuant to a search warrant; (2) the \n\ngovernment failed at trial to prove that computers seized at his home had been \n\ntransported in interstate or foreign commerce or had been used to produce child \n\npornography; and (3) the district court erred in sentencing him to a mandatory \n\nminimum term of imprisonment and in imposing two special conditions of \n\nsupervised release.   \n\n    AFFIRMED IN PART, VACATED IN PART, AND REMANDED. \n            \n\n BARBARA A. MASTERSON, Assistant United States \n Attorney (Gregory L. Waples, Assistant United \n States Attorney, on the brief), for Christina E. \n Nolan, United States Attorney for the District of \n Vermont, Burlington, Vermont, for Appellee. \n  \n STEVEN L. BARTH, Assistant Federal Public Defender \n (Barclay T. Johnson, Assistant Federal Public \n Defender, on the brief), for Michael L. Desautels, \n Federal Public Defender for the District of \n Vermont, Burlington, Vermont, for Defendant‐\n Appellant. \n            \n\n \n\n \n\n -2-\n\f  \n\n\nCHIN, Circuit Judge: \n\n    In this case, defendant‐appellant Donald Ray Boles was convicted in \n\nthe United States District Court for the District of Vermont, following a jury trial, \n\nof possession of child pornography in violation of 18 U.S.C. § 2252(a)(4)(B).  On \n\nApril 17, 2017, the district court sentenced him principally to 120 monthsʹ \n\nincarceration and a ten‐year term of supervised release.  On appeal, he contends \n\nthat the district court erred in denying his motion to suppress evidence obtained \n\nin a search of his home pursuant to a warrant.  He raises other issues relating to \n\nhis trial and sentence.  We affirm the conviction and sentence, except that we \n\nvacate the ʺriskʺ condition of his supervised release and remand in that respect \n\nonly. \n\n BACKGROUND  \n\nA.  The Facts1 \n\n In 2001, in an earlier case, Boles pleaded guilty to possession of child \n\npornography, also in the U.S. District Court for the District of Vermont.  The \n\ncourt (Sessions, J.) sentenced him to 15 months in prison and two yearsʹ  \n\n\n\n\n1\n    The facts herein are drawn from the affidavit that supported the warrant for Bolesʹs arrest, J. App. \n40‐66. \n\n -3-\n\f  \n\n\nsupervised release.  Boles served his prison term and completed his supervised \n\nrelease on August 8, 2004.   \n\n In January 2010, the Innocent Images Operations Unit (the ʺIIOUʺ) of \n\nthe Federal Bureau of Investigation (the ʺFBIʺ) investigated the distribution of \n\nchild pornography via an online message board called ʺGirls.Forumcircle.com.ʺ  \n\nThe IIOU investigation revealed that the message board was password‐\n\nprotected, had around 65 members, and was utilized to trade both illegal child \n\npornography and legal ʺchild eroticaʺ (images of children that are not sexually \n\nexplicit but that may be ʺsexually arousing to a given individual,ʺ see United \n\nStates v. Martin, 426 F.3d 68, 79 (2d. Cir. 2005)).  The investigation further \n\nrevealed that a user named ʺdrb05ʺ was a member of Girls.Forumcircle.com and \n\nwas linked to the email address ʺ[email protected].ʺ   \n\n Between August and November 2009, the administrator of \n\nGirls.Forumcircle.com posted messages that usersʹ accounts would be deleted if \n\nthey did not post photos or videos on the forum by November 30.  On November \n\n30, 2009, user drb05 posted 13 images of child erotica (not child pornography) \n\ndepicting a young girl in sexually suggestive poses.  User drb05 also posted two \n\ncomments on the message board indicating a sexual interest in young girls:  one \n\n\n\n -4-\n\f  \n\n\nin response to other usersʹ posts of child erotica on November 29 and one \n\naccompanying drb05ʹs post of child erotica on November 30.   \n\n    On July 19, 2010, the IIOU served a subpoena on Microsoft.  The \n\nresponsive materials revealed that ʺ[email protected]ʺ was associated with a \n\nʺDon Bʺ in ʺVermont, 05301.ʺ  The materials also revealed a log of IP addresses \n\nfor recent logins for [email protected].  On August 4, 2010, the IIOU \n\nsubpoenaed internet service provider FairPoint Communications (ʺFairPointʺ) \n\nrequesting information about subscribers associated with the IP addresses \n\nobtained from Microsoft, but FairPoint responded that it could not link IP \n\naddresses to specific subscribers.   \n\n    During its investigation, the IIOU also operated an FBI undercover \n\nwebsite that advertised access to free child pornography.  The ʺhome pageʺ of the \n\nwebsite made clear that its purpose was to share child pornography.  The home \n\npage also contained a login field that required a unique password to access the \n\nrest of the website.  Users obtained unique passwords by responding to a \n\npersonal email advertisement sent undercover by the FBI.  Once a user entered \n\nthe unique password, the user was taken to the ʺlanding page,ʺ which listed and \n\ndescribed free child pornography videos available to view or download.  When a \n\n\n\n -5-\n\f  \n\n\nuser clicked on the ʺdownloadʺ button for any of these videos, the website \n\nrecorded the userʹs IP address, video sample number, and the number of \n\ndownloads attempted, but no child pornography was actually made available.  \n\nThe landing page also included a link to a ʺpaid area,ʺ where users could \n\nostensibly pay to view a live stream of child pornography from Eastern Europe.   \n\n    On September 2, 2010, the FBI sent such an email to \n\[email protected].  On September 6, 2010, a user from IP address \n\n72.92.136.14 accessed the home page of the undercover website and entered the \n\nunique password sent to [email protected].  After arriving at the landing \n\npage, however, this user did not attempt to view or download any of the \n\nadvertised child pornography videos or access the ʺpaid areaʺ of the undercover \n\nwebsite.  At some point after sending the first email, an agent sent a new email to \n\[email protected], but the user did not respond.  Using this information, the \n\nIIOU again served a subpoena upon FairPoint requesting the information of any \n\nsubscribers associated with the IP address 72.92.136.14, but FairPoint again \n\nstated that it could not link subscribers to IP addresses.   \n\n    Nearly one year later, on July 21, 2011, FBI Special Agent Jeffrey \n\nAlford sent an email to FBI Special Agent Christopher Hughes regarding an \n\n\n\n -6-\n\f  \n\n\napplication for a warrant to search Bolesʹs residence, as Boles was the suspected \n\nowner of [email protected].  In this email, Alford asked whether there had \n\nbeen recent efforts to reach out to Boles regarding the undercover website, \n\nacknowledging that ʺI might otherwise now have a ʹstalenessʹ issue.ʺ  J. App. 67.  \n\nHughes responded that he had sent a new email but ʺ[Boles] did not respond to \n\nthe new request ‐‐ there may be a staleness issue with this at this point but itʹs \n\nworth seeing if the AUSA will go for it.ʺ  J. App. 69.  On August 19, 2011, the \n\nagents confirmed from a subpoena served upon eBay that drb0505@hotmail was \n\noperated by Boles, and the subpoena also revealed Bolesʹs home address.   \n\n    On August 25, 2011, the agents applied for a warrant to search and \n\nseize computer evidence from Bolesʹs residence.  The district court (Sessions, J.) \n\nissued the warrant the same day, finding that probable cause supported the \n\nrequest.  The agents executed the warrant on September 6, 2011.  More than 100 \n\nimages of child pornography were discovered on Bolesʹs computer and hard \n\ndrives.   \n\nB.  Proceedings Below \n\n On July 15, 2014, Boles was charged with possession of child \n\npornography in violation of 18 U.S.C. § 2252(a)(4)(B).  He was ultimately tried on \n\n\n\n -7-\n\f  \n\n\na second superseding indictment (the ʺIndictmentʺ) that charged three counts:  \n\none count of possessing child pornography and two counts of access with intent \n\nto view child pornography, all in violation of 18 U.S.C. § 2252(a)(4)(B).   \n\n On December 22, 2014, Boles moved to suppress the seized evidence \n\non the basis that the warrant was not supported by probable cause and the \n\ninformation in the affidavit was stale when the warrant was issued.  The district \n\ncourt denied Bolesʹs motion in a written decision filed April 2, 2015.2   \n\n Trial commenced on May 31, 2016.  The district court received into \n\nevidence, over Bolesʹs objection, two computers (with hard drives inside) and a \n\nseparate hard drive seized at Bolesʹs residence pursuant to the warrant.  Labels \n\naffixed to the computers and hard drives identified the manufacturer and \n\nshowed the place of origin as being outside the United States (China and \n\nThailand).  Boles argued that the labels were hearsay.  The district court \n\noverruled the objection and admitted the computer evidence.  The district court \n\nalso permitted an FBI agent to testify, again over defense counselʹs objection, that \n\nthe types of computer hardware in question (Hitachi, Compaq, and Hewlett \n\nPackard) were manufactured outside the United States.  On June 3, 2016, the jury \n\n\n2\n    In its opinion, the district court noted that it was ʺin the somewhat unusual position of \nreviewing a warrant that it issued in the first place.ʺ  J. App. 97.   \n -8-\n\f  \n\n\nconvicted Boles on the possession count but acquitted him on the two access \n\ncharges.   \n\n Prior to sentencing, Boles objected to several conditions of \n\nsupervised release proposed in his PSR, including two at issue on this appeal:  \n\n(1) the ʺriskʺ condition, which requires Boles to notify any person or organization \n\nof any risk he posed if his probation officer determined Boles was a risk; and (2) \n\nthe ʺpolygraphʺ condition, which requires Boles to submit to a polygraph exam \n\nas directed by the probation officer as part of his sex offender treatment program.  \n\nAt sentencing on April 17, 2017, the district court overruled Bolesʹs objections to \n\nthe conditions.  The district court sentenced Boles to 120 monthsʹ imprisonment  \n\n‐‐ the mandatory minimum ‐‐ and ten yearsʹ supervised release, imposing the \n\ndisputed conditions.   \n\n This appeal followed. \n\n DISCUSSION \n\n    On appeal, Boles raises three principal challenges:  (1) the district \n\ncourt erred in denying his motion to suppress because the search warrant issued \n\nwithout probable cause; (2) the government failed at trial to sufficiently prove \n\nthe interstate or foreign commerce element of the crime of conviction; and (3) the \n\n\n\n -9-\n\f  \n\n\ndistrict court erred in sentencing him to a mandatory minimum term of \n\nimprisonment and in imposing the two disputed conditions of supervised \n\nrelease.  We discuss each challenge in turn.  \n\nI.  The Motion to Suppress \n\n Boles argues that the warrant to search his residence was not \n\nsupported by probable cause because the affidavit submitted in support of the \n\nrequest for the warrant alleged nothing more than legal activity and was based \n\non stale information.  The government contends, however, that the district court \n\ndid not err in finding probable cause because the record established that Boles \n\nwas a collector of child pornography who likely was hoarding such images.  \n\nMoreover, the government argues that, even assuming the warrant issued \n\nwithout probable cause, the district court did not err in denying the motion \n\nbased on the good faith exception to the exclusionary rule.   \n\n We do not decide whether probable cause existed to support the \n\nissuance of the warrant, for we agree that in the circumstances here, even \n\nassuming the warrant was not supported by probable cause, the good faith \n\nexception applies.   \n\n  \n\n\n\n - 10 -\n\f  \n\n\n  A.  Applicable Law  \n\n    The Fourth Amendment prohibits ʺunreasonable searches and \n\nseizuresʺ and provides that ʺno Warrants shall issue, but upon probable cause, \n\nsupported by Oath or affirmation.ʺ  U.S. Const. amend. IV.   \n\n In determining whether probable cause exists to support the \n\nissuance of a warrant, a judge must ʺmake a practical, common‐sense decision \n\nwhether, given all the circumstances set forth in the affidavit before him, . . . \n\nthere is a fair probability that contraband or evidence of a crime will be found in \n\na particular place.ʺ  United States v. Falso, 544 F.3d 110, 117 (2d Cir. 2008) (quoting \n\nIllinois v. Gates, 462 U.S. 213, 238 (1983)) (alteration in original).  ʺOn appeal from \n\na district courtʹs ruling on a motion to suppress, we review the courtʹs factual \n\nfindings for clear error.  We review the courtʹs legal determinations, including \n\nthe existence of probable cause and the good faith of officers relying on a search \n\nwarrant, de novo.ʺ  United States v. Raymonda, 780 F.3d 105, 113 (2d Cir. 2015) \n\n(citation omitted).  We accord ʺʹsubstantial deference to the finding of an issuing \n\njudicial officer that probable cause exists,ʹ limiting our inquiry to whether the \n\nofficer ʹhad a substantial basisʹ for his determination.ʺ  Id. (quoting United States \n\nv. Wagner, 989 F.2d 69, 72 (2d Cir. 1993)).   \n\n\n\n - 11 -\n\f  \n\n\n Even where a warrant was issued without probable cause in \n\nviolation of the Fourth Amendment, suppression of the evidence is not \n\nautomatic; rather, because the remedy exacts a heavy toll on the justice system, \n\nthe exclusionary rule will apply only to deter ʺdeliberate, reckless, or grossly \n\nnegligent conductʺ by law enforcement.  Herring v. United States, 555 U.S. 135, 144 \n\n(2009).  Accordingly, ʺ[w]hen an officer genuinely believes that he has obtained a \n\nvalid warrant . . . and executes that warrant in good faith, there is no conscious \n\nviolation of the Fourth Amendment, ʹand thus nothing to deter.ʹʺ  Raymonda, 780 \n\nF.3d at 118 (quoting United States v. Leon, 468 U.S. 897, 921 (1984)); see also Falso, \n\n544 F.3d at 125 (explaining that evidence obtained by officers ʺin objectively \n\nreasonable relianceʺ on a subsequently invalidated warrant is not generally \n\nsubject to exclusion). \n\n For an officer to be able to claim the benefits of the good faith \n\nexception, however, his reliance on a warrant must be objectively reasonable.  See \n\nLeon, 468 U.S. at 922.  Thus,  \n\n the good faith exception cannot shield [] an   \n    officer who relies on a duly issued warrant in at  \n    least four circumstances:  (1) where the issuing  \n    magistrate has been knowingly misled; (2) where  \n    the issuing magistrate wholly abandoned his or  \n    her judicial role; (3) where the application is so  \n\n\n - 12 -\n\f  \n\n\n    lacking in indicia of probable cause as to render  \n    reliance upon it unreasonable; and (4) where the  \n    warrant is so facially deficient that reliance upon  \n    it is unreasonable. \n\nRaymonda, 780 F.3d at 118 (quoting United States v. Clark, 638 F.3d 89, 100 (2d Cir. \n\n2011); see also Leon, 468 U.S. at 923 (suppression is an appropriate remedy if the \n\nmagistrate issuing the warrant was ʺmisled by information in an affidavit that \n\nthe affiant knew was false or would have known was false except for his reckless \n\ndisregard of the truthʺ).  ʺWhen the police exhibit ʹdeliberate,ʹ ʹreckless,ʹ or \n\nʹgrossly negligentʹ disregard for Fourth Amendment rights, the deterrent value of \n\nexclusion is strong and tends to outweigh the resulting costsʺ of suppression.  \n\nDavis v. United States, 564 U.S. 229, 238 (2011) (internal quotation marks omitted). \n\n  B.  Application \n\n The existence of probable cause in this case presents a close \n\nquestion.  We need not decide the issue, however, because we conclude that, \n\neven assuming probable cause was lacking, the good faith exception applies.  \n\nThe government argues that even if the warrant to search Bolesʹs residence was \n\nnot supported by probable cause, the FBI agents were justified in relying on the \n\ndistrict courtʹs determination that the warrant was valid.  We agree. \n\n\n\n\n - 13 -\n\f  \n\n\n In Raymonda, we directly addressed the exclusionary rule in the \n\ncontext of an affidavit containing potentially stale and misleading information.  \n\nIn that case, the affidavit supporting the warrant application alleged only that, on \n\none occasion nine months earlier, a user with an IP address associated with \n\nRaymondaʹs home opened between one and three pages of a website housing \n\nthumbnail links to images of child pornography but did not click on any \n\nthumbnails to view full‐sized files.  780 F.3d at 117.  The affidavit was written as \n\nto suggest that the suspect intentionally accessed 76 pornographic images, and, \n\nsignificantly, it omitted the fact that the images were open for just seventeen \n\nseconds, a time span consistent with a user having ʺsimply closedʺ the site \n\nimmediately after clicking on it, rather than intentionally saving or viewing all of \n\nthe images that his browser had accessed.  Id. at 111‐12. \n\n Absent any further indicia that Raymonda was a collector of child \n\npornography, we concluded that the single incident of access, which was ʺat least \n\nequally consistent with an innocent user inadvertently stumbling upon a child \n\npornography website,ʺ did not create a fair probability that child pornography \n\nwould be found on Raymondaʹs computer months later.  Id. at 117.  We therefore \n\nagreed with the district court that the warrant lacked probable cause.  We \n\n\n\n - 14 -\n\f  \n\n\nreversed, however, the district courtʹs grant of Raymondaʹs motion to suppress \n\nthe evidence, holding that the agents who had executed the search were entitled \n\nto rely in good faith on the duly issued warrant for two reasons:  (1) the \n\nmagistrate judge had reached an independent determination of probable cause \n\nthat, while ultimately incorrect, was not contrary to established law or so facially \n\ndeficient that reliance upon it would be unreasonable, and (2) we disagreed with \n\nthe district court that an agent had acted in such a ʺgrossly negligentʺ manner \n\nwith respect to the warrant application as to justify exclusion of the evidence.   \n\nSee id. at 121.   \n\n In concluding that the agent had not been grossly negligent, first, we \n\ndisagreed with the district court that the agent was effectively on notice about a \n\nstaleness issue with the nine‐month old evidence because he had previously \n\nworked on a case in which one‐year‐old evidence was found to be stale.  Id. at \n\n119.  We explained that the agentʹs knowledge that an earlier case found nearly \n\nyear‐old evidence too stale to create probable cause could not have given him \n\nsufficient notice that his affidavit in Raymonda would be found equally deficient.  \n\nSee id. (ʺ[A prior holding by a district court cannot establish a binding principle \n\nof law sufficient to undermine an agentʹs good faith reliance on a later warrant.ʺ). \n\n\n\n - 15 -\n\f  \n\n\n Second, we rejected the argument that there were key omissions and \n\nexaggerations in the affidavit that had materially misled the magistrate judge \n\nissuing the warrant.  Although we acknowledged that the agent ʺmay have \n\nexaggerated the significance ofʺ certain facts and potentially ʺmischaracteriz[ed]ʺ \n\nthe evidence, we nevertheless determined that, absent a finding that the agent \n\nintended to deceive the magistrate judge with these statements, the ʺoversightsʺ \n\nfell ʺshort of deliberate deception or gross negligence.ʺ  Id. at 120.  We therefore \n\nheld that agents were entitled to rely in good faith on the warrant.  See id. at 121.  \n\n As in Raymonda, the agents in this case were entitled to rely in good \n\nfaith on the duly issued warrant.  First, the district court made an independent \n\ndetermination that the warrant was supported by probable cause, which it based \n\nprimarily on:  (1) Bolesʹs membership in Girls.Forumcircle.com and his postings \n\nof child erotica; (2) Bolesʹs visit to the FBI Undercover website using the unique \n\ncode that was emailed to him; and (3) Bolesʹs prior conviction for possession of \n\nchild pornography.  Even assuming that these facts did not add up to probable \n\ncause, the existence of probable cause in this case is an exceedingly close \n\nquestion.  Accordingly, the courtʹs finding of probable cause was not facially \n\n\n\n\n - 16 -\n\f  \n\n\ninsufficient such that any reliance upon the warrant would be unreasonable.  Id. \n\nat 121. \n\n Second, as in Raymonda, the representations in the affidavit here \n\nwere not intentionally false, reckless, or grossly negligent such as to otherwise \n\npreclude the good faith exception.  Boles attempts to distinguish this case from \n\nRaymonda on the ground that here the agents were specifically aware that ʺthere \n\nmay be a staleness issue with [the evidence]ʺ prior to applying for the warrant.  \n\nWe are not persuaded, however, that the agents acted in reckless disregard of \n\nBolesʹs Fourth Amendment rights merely because they knew of a possible \n\nstaleness issue before applying for the warrant.  As the district court noted, the \n\nexchange does indicate ʺsome degree of uncertainty on the part of the agentsʺ as \n\nto whether the evidence would be considered stale.  Sp. App. 15.  But there was \n\nnothing inappropriate in their leaving the issue to the prosecutor and court to \n\nresolve.  As this Court has repeatedly recognized, there is ʺno bright‐line rule for \n\nstaleness,ʺ Walcyzk v. Rio, 496 F.3d 139, 162 (2d Cir. 2007), which depends ʺon the \n\nbasis of the facts of each case,ʺ United States v. Martino, 664 F.2d 860, 867 (2d Cir. \n\n\n\n\n - 17 -\n\f  \n\n\n1981); accord Raymonda, 780 F.3d at 114.  While some of the information here \n\narguably was stale, other facts weighed against a finding of staleness. 3   \n\n Even assuming the information was stale, the agents disclosed the \n\ninformation to a neutral and detached judge, who was made aware of the \n\nʺstaleness issueʺ and the relevant facts and circumstances, but nevertheless \n\nissued the warrant.  The agents cannot be said to have acted in bad faith by \n\nasking a judge to decide the question of staleness.  See Leon, 468 U.S. at 922 \n\n(evidence seized ʺin objectively reasonable reliance onʺ warrant issued by \n\ndetached and neutral judge is admissible, even where reviewing court later \n\ndetermines warrant was invalid).  \n\n\n\n\n3\n   For example, (1) Boles had previously been convicted of possession of child \npornography in June 2000, see Raymonda, 780 F.3d at 114 (evidence that ʺpersons \npossessed child pornography in the past supports a reasonable inference that they \nretain those images ‐‐ or have obtained new ones ‐‐ in the presentʺ); (2) Boles apparently \nhad joined Girls.Forumcircle.com, a website used for posting and trading illegal child \npornography and legal erotica, see Martin, 426 F.3d at 73 (upholding warrant to search \ndefendantʹs computer where he had recently joined an Internet group devoted to \ndistributing child pornography, even absent evidence that he had actually accessed any \nillicit images through that site); and (3) Boles had entered a unique code enabling him to \naccess the FBI undercover page, which advertised its purpose as the distribution of \nchild pornography, see United States v. Vosburg, 602 F.3d 512, 517 (3d Cir. 2010) (no \nstaleness where suspect had to enter decoded URL and could not access images of child \npornography ʺwith a simple click of the mouseʺ).   \n \n - 18 -\n\f  \n\n\n Finally, we note that the affidavit in this case disclosed that Boles \n\nhad not attempted to download child pornography from the FBI undercover \n\nwebsite and that he had not responded to the FBIʹs second email solicitation.  \n\nHence, the agents disclosed these facts to the district court, and the district court \n\nnoted these facts in nonetheless denying the motion.  While the agents here \n\narguably should have provided more information, including, for example, \n\ndetails relating to the Girls.Forumcircle.com website, any omissions and \n\nexaggerations were not as egregious as those in Raymonda, where we held that \n\nthe good faith exception applied even though there were at least arguable \n\nomissions and exaggerations in the agentʹs affidavit.  See 780 F.3d at 122 (Chin, J., \n\ndissenting).  We are hard‐pressed to conclude that the agents acted in a \n\ndeliberate or reckless or grossly negligent manner here. \n\n We therefore agree with the district court that, despite the agentsʹ \n\nuncertainty as to whether the evidence was stale, ʺ[o]nce the Court ruled on the \n\nlegal sufficiency of the facts alleged in the affidavit, the officers were justified inʺ \n\nsubsequently relying on that determination and executing the warrant.  See Sp. \n\nApp. 16; see also Herring, 555 U.S. at 144.  We conclude that the district court did \n\nnot err in denying Bolesʹs motion to suppress the computer evidence. \n\n\n\n - 19 -\n\f  \n\n\nII.  The Interstate or Foreign Commerce Requirement \n\n Boles makes three arguments with respect to the interstate or foreign \n\ncommerce element of the crime of conviction:  (a) the government constructively \n\namended the Indictment in its proof at trial; (b) the government failed to present \n\nsufficient evidence that the images on his computer were ʺproducedʺ using \n\nmaterials transported by a means of interstate or foreign commerce; and (c) the \n\ndistrict court erred in admitting evidence that the computers and hard drives \n\nwere manufactured outside the United States.   \n\n  A.  Constructive Amendment \n\n Boles argues that the government constructively amended the \n\nIndictment charging him with one count of possession of child pornography \n\nunder 18 U.S.C. § 2252(a)(4)(B).4  The Indictment alleged that Boles  \n\n\n\n\n4    The statute provides in relevant part: \n \n Any person who . . . knowingly possesses, or knowingly accesses with \n intent to view, 1 or more books, magazines, periodicals, films, video \n tapes, or other matter which contain any visual depiction that has been \n mailed, or has been shipped or transported using any means or facility of \n interstate or foreign commerce or in or affecting interstate or foreign \n commerce, or which was produced using materials which have been \n mailed or so shipped or transported, by any means including by \n computer, if ‐‐ (i) the producing of such visual depiction involves the use \n of a minor engaging in sexually explicit conduct; and (ii) such visual \n depiction is of such conduct; . . . [commits a crime]. \n  \n 18 U.S.C. § 2252(a)(4)(B). \n\n - 20 -\n\f  \n\n\n possessed at least one matter which contained a \n visual depiction that was produced using \n materials which had been mailed and shipped \n and transported using any means and facility of \n interstate and foreign commerce, including by \n computer, the production of such visual depiction \n involved the use of a minor engaging in sexually \n explicit conduct, and such visual depiction was of \n such conduct. \n\n J. App. 15 (emphasis added).  Boles argues that, as written, the Indictment \n\nrequired the government ʺto prove that the computer hardware was mailed, \n\nshipped, or transported ʹusingʹ a ʹmeans and facility of interstate or foreign \n\ncommerce.ʹʺ  Def.‐Appellantʹs Reply Br. 15 (emphasis in original).  The district \n\ncourt charged the jury, however, that it had to find only ʺthat the visual depiction \n\nwas produced using materials that had been transported in or affecting interstate \n\nor foreign commerce.ʺ  J. App. 271.  Boles contends that the government failed to \n\nprove the actual means by which the hardware had traveled.    \n\n    1.  Applicable Law \n\n We review a constructive amendment challenge de novo.  See United \n\nStates v. Agrawal, 726 F.3d 235, 259 (2d Cir. 2013).  To prevail on a constructive \n\namendment claim, a defendant must establish that ʺthe terms of the indictment \n\nare in effect altered by the presentation of evidence and jury instructions which \n\nso modify essential elements of the offense charged that there is a substantial \n\n - 21 -\n\f  \n\n\nlikelihood that the defendant may have been convicted of an offense other than \n\nthat charged in the indictment.ʺ  United States v. DʹAmelio, 683 F.3d 412, 416 (2d \n\nCir. 2012) (internal quotation marks omitted) (emphasis in original); see also \n\nUnited States v. Spoor, 904 F.3d 141, 152 (2d Cir. 2018).   \n\n Where a defendant fails to raise a claim in the district court, we must \n\nalso review for plain error to assess the impact of any alleged error on the \n\ndefendantʹs rights.  United States v. Taylor, 816 F.3d 12, 18 (2d Cir. 2016).  To \n\nestablish plain error, a defendant must demonstrate ʺ(1) error, (2) that is plain, \n\nand (3) that affect[s] substantial rights.  If all three conditions are met, an \n\nappellate court may then exercise its discretion to notice a forfeited error, but \n\nonly if (4) the error seriously affect[s] the fairness, integrity, or public reputation \n\nof judicial proceedings.ʺ  Id. (brackets in original) (quoting Johnson v. United \n\nStates, 520 U.S. 461, 467 (1997)). \n\n    2.  Application \n\n Boles argues that, under the Indictment as written, the government \n\nwas required to present evidence of the actual means or facility by which the \n\ncomputer hardware traveled interstate.  We conclude that the district court did \n\nnot plainly err in charging the jury that it only had to find that the hardware had \n\n\n\n - 22 -\n\f  \n\n\nbeen transported in or affected interstate commerce.  Boles did not raise this \n\nissue below, and, as did the government, proceeded on the basis that the \n\ngovernment was required only to prove that the computer hardware traveled in \n\ninterstate commerce, not the actual means by which it had traveled.  \n\n Furthermore, in discussions with the district court about the jury \n\ncharge, defense counsel specifically requested that the jurors not see the actual \n\nIndictment because he did not want them ʺfocusedʺ on it.  Boles was therefore \n\nadequately informed about the arguments the government intended to make \n\nabout the jurisdictional element and the types of evidence it would produce to \n\nsupport its theory.  Thus, there was no error, much less error that was ʺplain.ʺ  \n\n Moreover, for purposes of plain error review, we do not view as \n\nsignificant the difference between proving (a) the ʺmeans or facilityʺ of interstate \n\ntravel (that is, how the equipment was physically transported) and (b) the fact \n\nthat the equipment was shipped or transported in interstate or foreign \n\ncommerce.  See 18 U.S.C. § 2252(a)(4)(B) (referring to any matter containing ʺany \n\nvisual depiction that has been . . . shipped or transported using any means or \n\nfacility of interstate or foreign commerceʺ or ʺproduced using materials which \n\nhave been mailed or so shipped or transported, by any meansʺ).    \n\n\n\n - 23 -\n\f  \n\n\n Finally, we have held that there is sufficient evidence to support \n\nconviction for possession of child pornography where a defendant possessed \n\nimages of child pornography on computer equipment manufactured outside this \n\ncountry.  See United States v. Ramos, 685 F.3d 120, 132‐33 (2d Cir. 2012) (applying \n\ninterstate commerce element of § 2252A(a)(5)(B)); accord United States v. \n\nGrzybowicz, 747 F.3d 1296, 1306‐07 (11th Cir. 2014); United States v. Anderson, 280 \n\nF.3d 1121, 1125 (7th Cir. 2002).  Accordingly, we are not persuaded that the error \n\nʺaffect[ed] the fairness, integrity, or public reputation of judicial proceedings.ʺ  \n\nJohnson, 520 U.S. at 467 (internal quotation marks omitted).  \n\n  B.  The Evidence of ʺProductionʺ \n\n Boles further argues that the government failed to prove that the \n\nhardware was used to ʺproduceʺ the child pornography because the government \n\ndid not present evidence that the seized hardware was used to create the child \n\npornography in the first instance (i.e., that Boles had manufactured the child \n\npornography using the hardware rather than merely storing copies of the images \n\non the hardware).    \n\n This Court has not specifically addressed the question of whether \n\nmerely transferring or copying child pornography using materials that have \n\n\n\n - 24 -\n\f  \n\n\ntraveled interstate means that the child pornography has been ʺproducedʺ using \n\nthose materials as required under 18 U.S.C. § 2552(a)(4)(B).  See Ramos, 685 F.3d \n\nat 133 n.10 (explaining that the court would not reach the question of whether \n\nʺthe mere copying or downloading of an image is ʹproductionʹ for purposes of \n\nthe federal child pornography statutesʺ).5  \n\n    Almost every circuit to address this issue, however, has held that the \n\nword ʺproducedʺ encompasses mere copying or downloading of child \n\npornography.  See United States v. Burdulis, 753 F.3d 255, 262 (1st Cir. 2014) \n\n(images are ʺproducedʺ for the purposes of § 2254(a)(4)(B) when they are copied \n\nor downloaded onto a digital medium); United States v. Dickson, 632 F.3d 186, \n\n189‐90 (5th Cir. 2011) (same); United States v. Angle, 234 F.3d 326, 341 (7th Cir. \n\n2000) (same); United States v. Lacy, 119 F.3d 742, 750 (9th Cir. 1997) (same).  But see \n\nUnited States v. Wilson, 182 F.3d 737, 742‐43 (10th Cir. 1999) (holding that the \n\n\n5   Although the government argues that we decided this issue in United States v. Pattee, 820 \nF.3d 496 (2d Cir. 2016), there we interpreted ʺproductionʺ in the context of 18 U.S.C. § 2251, \nrather than the statute at issue here, 18 U.S.C. § 2252(a)(4)(B).  Moreover, we noted that  \n\n [i]t does not follow from this conclusion, however, that merely \n transferring or copying a pornographic image that was produced \n by someone else is tantamount to ʺproducingʺ child pornography, \n such that simple possession, which typically involves making a \n copy of a file to a hard disk or other medium, would qualify as \n production. \n\nId. at 511 n.8. \n - 25 -\n\f  \n\n\ngovernment produced insufficient evidence to support the interstate commerce \n\nelement of § 2252(a)(4)(B) because there was no evidence that the digital \n\nmediums were used to produce the graphic files even though the files could be \n\nstored on the mediums). \n\n    Those circuits that have interpreted ʺproducedʺ to include copying \n\nor transferring rely on 18 U.S.C. § 2256(3), which defines the word ʺproducingʺ in \n\nthe child pornography and child exploitation statutes to mean ʺproducing, \n\ndirecting, manufacturing, issuing, publishing, or advertising.ʺ  18 U.S.C. \n\n§ 2256(3); see also Angle, 234 F.3d at 341.  The plain meaning of the word \n\nʺproducedʺ would include producing or making a copy.  Moreover, we agree \n\nthat to interpret ʺproducedʺ to exclude pulling up images on a computer monitor \n\nis ʺfar too restrictive as it essentially renders meaningless the statutory definition \n\nof ʹproducingʹ [in § 2256(3)] . . . and focuses entirely on the circumstances \n\nsurrounding the original or actual production of the visual depiction.ʺ  Angle, 234 \n\nF.3d at 241.  To read the statute this way would require the government to \n\npresent evidence about the original materials used to create the child \n\npornography in every case a defendant is charged under the ʺproduced using \n\nmaterialsʺ language.  Boles fails to point to, and we are unable to find, any \n\n\n\n - 26 -\n\f  \n\n\nevidence that Congress intended these subsections to be applied so narrowly.  \n\nIndeed, the nature of the industry is that these images are copied over and over \n\nagain as collectors share them, and it would be difficult in many cases to prove \n\nthe circumstances of the original ʺproduction.ʺ  \n\n    Therefore, we agree that the government was not required to prove \n\nthat the hardware was used to create the pornography in the first instance and \n\nthat it was sufficient for the government to prove that the hardware was used to \n\nmake, store, or display copies of the pornographic images.   \n\n  C.  The Evidence the Computer Equipment \n    Was Manufactured Outside the United States \n \n    Boles argues that the district court erred by (1) admitting \n\ninscriptions on the back of seized pieces of computer hardware because the \n\nlabels were inadmissible hearsay; and (2) allowing Agent Alfin to testify as an \n\nexpert about where the relevant companies manufacture hardware.   \n\n    A district court has ʺbroad discretionʺ over the admission of \n\nevidence.  United States v. Nektalov, 461 F.3d 309, 318 (2d Cir. 2006).  Accordingly, \n\nʺ[t]his [C]ourt reviews evidentiary rulings for abuse of discretion.ʺ  United States \n\nv. Cummings, 858 F.3d 763, 771 (2d Cir. 2017).  ʺA district court has abused its \n\ndiscretion if it based its ruling on an erroneous view of the law or on a clearly \n\n - 27 -\n\f  \n\n\nerroneous assessment of the evidence or rendered a decision that cannot be \n\nlocated within the range of permissible decisions.ʺ  United States v. Natal, 849 F.3d \n\n530, 534 (2d Cir. 2017) (per curiam) (internal quotation marks omitted).  \n\n     1.  The Hardware Inscriptions   \n\n We have not directly addressed whether manufacturersʹ inscriptions \n\nor labels identifying a productʹs country of origin are inadmissible hearsay.  We \n\nconclude that the district court did not abuse its discretion in allowing evidence \n\nof the inscriptions here.   \n\n As a threshold matter, there is some doubt as to whether the \n\ninscriptions are hearsay at all, as the government, relying principally on gun \n\ncases, argues that under the ʺmechanical traceʺ theory, markings on products \n\ndesignating country of origin are not ʺstatementsʺ subject to the hearsay rule.  See \n\nFed. R. Civ. P. 801(a), (c); United States v. Bowling, 32 F.3d 326, 328 (8th Cir. 1994) \n\n(holding that manufacturerʹs name stamped on firearm was not ʺa statement of \n\nfactʺ subject to hearsay rule); United States v. Thody, 978 F.2d 625, 630‐31 (10th Cir. \n\n1992) (ʺ[T]he manufacturerʹs imprint in the gun is not hearsay.  It is technically \n\nnot an assertion by a declarant as contemplated by the [hearsay rule].ʺ); United \n\nStates v. Alvarez, 972 F.2d 1000, 1004 (9th Cir. 1992) (ʺAn inscription placed on a \n\n\n\n - 28 -\n\f  \n\n\nfirearm by the manufacturer is similarly a mechanical trace and not a statement \n\nfor purposes of Federal Rule of Evidence 801(c).ʺ), overruled on other grounds by \n\nKawashima v. Mukasey, 530 F.3d 1111, 1116 (9th Cir. 2008).  We need not decide \n\nthe issue because, even assuming the inscriptions here are hearsay, we conclude \n\nthat they are nonetheless admissible.   \n\n Inscriptions indicating foreign origin are regulated, see 19 U.S.C. \n\n§ 1304, and federal law prohibits misleading designations of origin, see 15 U.S.C. \n\n§ 1405.  Additionally, under Federal Rule of Evidence 902(7), trade inscriptions \n\nare self‐authenticating, that is, they ʺrequire no extrinsic evidence of authenticity \n\nin order to be admitted.ʺ  Fed. R. Evid. 902.  While Boles is correct that self‐\n\nauthentication alone does not qualify as an exception to the hearsay rule, it does \n\nrender the inscriptions particularly trustworthy.  As the First Circuit has noted, \n\nʺ[a]n authentic inscription, of the kind made regularly by manufacturers in \n\naccordance with federal law, bears significant similarity to other forms of \n\nevidence admissible under the enumerated hearsay exceptions.ʺ  Burdulis, 753 \n\nF.3d at 263‐64 (citing Fed. R. Evid. 803(6) (records of regularly conducted \n\nactivity), 803(9) (certain information reported to a public office in accordance \n\nwith a legal duty), and 807 (residual exception)); accord United States v. Koch, 625 \n\n\n\n - 29 -\n\f  \n\n\nF.3d 470, 480 (8th Cir. 2010) (rejecting claim that ʺmanufacturerʹs inscription on a \n\nproduct is inadmissible hearsayʺ).  Any of these exceptions would suffice here, \n\nand we hold that the district court did not abuse its discretion in overruling the \n\nhearsay objection.   \n\n    2.  The Agentʹs Testimony as an Expert \n\n    Boles also argues that the district court erred by permitting FBI \n\nSpecial Agent Alfin to testify about the origin of the computer hardware.  Rule \n\n702 permits testimony in the form of an opinion only if ʺthe expertʹs scientific, \n\ntechnical, or other specialized knowledge will help the trier of fact to understand \n\nthe evidence or to determine a fact in issue.ʺ  Fed. R. Evid. 702(a).  Boles \n\nadditionally argues that the defense had been given no prior notice in the \n\ngovernmentʹs Rule 16 expert disclosure that Alfin would testify about the \n\nmanufacturing origin of the hardware.   \n\n    A district court has ʺbroad discretionʺ in deciding whether to admit \n\nexpert testimony, and the exercise of that discretion will not be disturbed unless \n\nit is ʺmanifestly erroneous.ʺ  United States v. Locasio, 6 F.3d 924, 936 (2d Cir. 1993); \n\naccord United States v. Dukagjini, 326 F.3d 45, 52 (2d Cir. 2003).  We discern no \n\nmanifest error here, where the district court permitted an FBI agent with \n\n\n\n - 30 -\n\f  \n\n\nspecialized training and experience in computers, computer forensics, and \n\nforensic imaging to testify that he knew the computer hardware in question was \n\nmanufactured outside Vermont and outside the United States.   \n\n While there is a dispute as to whether the government provided \n\nsufficient notice of the agentʹs testimony as an expert as required by Fed. R. \n\nCrim. P. 16(a), even assuming the testimony was not properly noticed, the \n\ndistrict court had the discretion to admit the evidence nonetheless as long as the \n\nviolation did not cause Boles ʺsubstantial prejudice.ʺ  United States v. Thai, 29 F.3d \n\n785, 804 (2d Cir. 1994).  Here, Boles has not identified any prejudice from the \n\npurported lack of advance notice, and the record is clear in any event that Boles \n\nand his counsel knew that the government intended to introduce evidence to \n\nprove the interstate or foreign commerce nexus.  Finally, as we have held that the \n\nmanufacturersʹ inscriptions were admissible, any error with respect to the \n\nadmission of the agentʹs testimony in this respect was harmless. \n\nIII.  The Sentence \n\n    Boles raises two challenges to his sentence: (a) the imposition of the \n\nmandatory minimum term of imprisonment; and (b) the imposition of the two \n\ndisputed special conditions of supervised release. \n\n\n\n - 31 -\n\f  \n\n\n A. The Mandatory Minimum \n\n First, Boles argues that the district courtʹs application of the ten‐year \n\nmandatory minimum penalty, under 18 U.S.C. § 2252(b)(2), violated the Sixth \n\nAmendment because Bolesʹs prior conviction was not found by the jury beyond a \n\nreasonable doubt.  His argument, however, is expressly foreclosed by this \n\nCourtʹs decision in United States v. Arline, 835 F.3d 277 (2d Cir. 2016) (per curiam), \n\nwhere we acknowledged that ʺ[t]he fact of a prior conviction may be decided by \n\na judge and need not be determined by a jury.ʺ  Id. at 280 (citation omitted).  \n\nAccordingly, the district court properly recognized that the mandatory minimum \n\nof ten years applied to Boles. \n\n  B.   The Conditions of Supervised Release \n\n    Second, Boles raises challenges to two conditions of his supervised \n\nrelease.  He challenges Standard Condition 17, the ʺriskʺ condition, which \n\nprovides: \n\n   If the probation officer determines that you pose a risk \n to another person (including an organization), the \n probation officer may require you to notify the person \n about the risk and you must comply with that \n instruction.  The probation officer may contact the \n person and confirm that you have notified the person \n about the risk. \n  \nPSR ¶ 95, Cond. 27.   \n\n - 32 -\n\f  \n\n\n Boles specifically argues that the risk condition is ʺfar too vague to \n\nbe related to any goal of supervisionʺ because the court did not define ʺrisk,ʺ and \n\nthe condition leaves ʺtoo much discretion[] to the supervising officer.ʺ  Def.‐\n\nAppellantʹs Br. 14‐15. \n\n Boles also challenges the ʺpolygraphʺ condition of supervised \n\nrelease, which provides that Boles: \n\n shall participate in an approved program of sex \n offender evaluation and treatment, which may \n include polygraph examinations, as directed by \n the probation officer.  Any refusal to submit to \n such assessment or tests as scheduled is a \n violation of the conditions of supervision. \n  \nPSR ¶ 96, Cond. (a). \n\n    Boles contends that the condition violates the Fifth Amendment, \n\nbecause if he answers questions, he may incriminate himself, and on the other \n\nhand, if he invokes his Fifth Amendment right to remain silent, he violates the \n\ncondition, and will be subject to having his supervised release revoked.   \n\n    1.  Applicable Law \n\n We generally review the imposition of conditions of supervised \n\nrelease for abuse of discretion.  See United States v. Reeves, 591 F.3d 77, 80 (2d Cir. \n\n2010).  ʺWhen a challenge to a condition of supervised release presents an issue \n\n - 33 -\n\f  \n\n\nof law,ʺ however, ʺwe review the imposition of that condition de novo, bearing in \n\nmind that any error of law necessarily constitutes an abuse of discretion.ʺ  United \n\nStates v. McLaurin, 731 F.3d 258, 261 (2d Cir. 2013) (internal quotation marks \n\nomitted).  \n\n A district court may  \n\n impose special conditions of supervised release to \n the extent that they are reasonably related to (i) \n the nature and circumstances of the offense and \n the history and characteristics of the defendant, \n and (ii) the purposes of sentencing, including the \n need to afford adequate deterrence, to protect the \n public from further crimes of the defendant, and \n to provide the defendant with needed training or \n treatment. \n\nUnited States v. Johnson, 446 F.3d 272, 277 (2d Cir. 2006) (quoting United States v. \n\nGermosen, 139 F.3d 120, 131 (2d Cir. 1998)); see also 18 U.S.C. § 3583(d).  ʺWhile \n\ndistrict courts have broad discretion to tailor conditions of supervised release, \n\nthat discretion is not unfettered,ʺ and we will ʺcarefully scrutinize conditions that \n\nmay be excessively harsh or inexplicably punitive.ʺ  United States v. Jenkins, 854 \n\nF.3d 181, 188 (2d Cir. 2017) (internal citations omitted). \n\n    2.  Application \n\n As to the first challenged condition, we agree with Boles that the \n\nʺriskʺ condition is vague and affords too much discretion to the probation officer.  \n\n - 34 -\n\f  \n\n\nIn United States v. Peterson, we vacated a district courtʹs imposition of two similar \n\nstandard conditions of supervised release, in part, because they, too, gave the \n\nprobation officer too much discretion.  248 F.3d 79, 86 (2d Cir. 2001) (per curiam).  \n\nThe defendant in Peterson was convicted of bank larceny, but the court noted that \n\nthe supervised release conditions were ʺbased in part on a prior, unrelated New \n\nYork state‐sex‐offense conviction [for incest].ʺ  Id. at 81. \n\n In Peterson, we held that the conditions were impermissible to the \n\nextent that they required Peterson to notify employers about his state conviction, \n\nbecause occupational restrictions must be related to the offense of conviction at \n\nissue.  Id. at 85‐86.  We further held, to the extent that the conditions required \n\nPeterson to notify employers about his federal conviction, ʺthe [district] court \n\nmust determine, rather than leaving to the discretion of the probation officer, \n\nwhether such notification is required . . . [and] may not simply leave the issues of \n\nemployer notification to the probation officerʹs unfettered discretion.ʺ  Id. at 86.  \n\nWe therefore remanded the case for clarification of the nature and scope of \n\nemployer notification of the offense of conviction.  Id.   \n\n Because the condition at issue here extends to warning employers of \n\nrisk and gives the probation office unfettered discretion with respect to the \n\n\n\n - 35 -\n\f  \n\n\nnotification requirement, we agree with Boles that the condition is largely \n\nindistinguishable from the one we struck down in Peterson.  Accordingly, we \n\nvacate the risk condition and remand to the district court to clarify the scope of \n\nthe ʺriskʺ condition. \n\n We are not persuaded, however, as to Bolesʹs challenge to the \n\npolygraph condition of supervised released.  In Johnson, 446 F.3d at 272, we \n\nupheld a polygraph condition against a Fifth Amendment challenge, similar to \n\nthe one at issue here.  We held that requiring a defendant to take a polygraph test \n\nas a condition of his supervised release does not violate the Fifth Amendment \n\nbecause the defendant retains the right to later challenge any resulting self‐\n\nincrimination in court.  Id. at 280; see also Asherman v. Meachum, 957 F.2d 978, 982‐\n\n83 (2d Cir. 1992) (en banc) (explaining that revocation may be based on a refusal \n\nto answer questions, so long as the administrator does nothing to impair later \n\ninvocation of the Fifth Amendment privilege).   \n\n Furthermore, in upholding the condition in Johnson, we recognized \n\nthe strong deterrent value of polygraph conditions, explaining that such \n\nconditions ʺfurther sentencing objectives such as rehabilitation and deterrence, \n\nwith reasonably small incremental deprivations of liberty.ʺ  Johnson, 446 F.3d at \n\n\n\n - 36 -\n\f  \n\n\n278.  When the district court imposed the polygraph condition at issue here, it \n\nspecifically noted that the condition is ʺa tremendous deterrent and satisfies a \n\nvery legitimate purpose in probationary supervision.ʺ  J. App. 396.  Accordingly, \n\nwe conclude that the district court did not abuse its discretion in ordering \n\npolygraph examinations as part of Bolesʹs sex offender treatment following his \n\nmost recent conviction.    \n\n CONCLUSION \n\n    For the reasons set forth above, we AFFIRM the judgment in all \n\nrespects except that we VACATE the ʺriskʺ condition of supervised release and \n\nREMAND to the district court for clarification as set forth above. \n\n \n\n\n\n\n - 37 -", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361952/", "author_raw": "CHIN, Circuit Judge:"}]}
WESLEY
CHIN
CARNEY
1
{"WESLEY": ", Circuit", "CHIN": ", Circuit", "CARNEY": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584699/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Donald Ray Boles\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17‐1138‐cr \nUnited States v. Donald Ray Boles \n  \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n\n August Term 2017 \n\n (Argued: April 16, 2018                  Decided: January 25, 2019) \n  \n Docket No. 17‐1138‐cr \n\n            \n\n UNITED STATES OF AMERICA, \n                Appellee, \n \n ‐ against ‐ \n\n DONALD RAY BOLES,  \n Defendant‐Appellant. \n\n            \n\n ON APPEAL FROM THE UNITED STATES DISTRICT COURT \n FOR THE DISTRICT OF VERMONT \n  \nBefore: \n WESLEY, CHIN, AND CARNEY, Circuit Judges. \n  \n    Appeal from a judgment of the United States District Court for the \n\nDistrict of Vermont (Sessions, J.) convicting defendant‐appellant, following a jury \n\ntrial, of one count of possessing child pornography and sentencing him \n\nprincipally to 120 monthsʹ imprisonment followed by ten yearsʹ supervised \n\f  \n\n\nrelease.  On appeal, defendant‐appellant raises three principal challenges:  (1) the \n\ndistrict court erred in denying his motion to suppress evidence of child \n\npornography seized at his home pursuant to a search warrant; (2) the \n\ngovernment failed at trial to prove that computers seized at his home had been \n\ntransported in interstate or foreign commerce or had been used to produce child \n\npornography; and (3) the district court erred in sentencing him to a mandatory \n\nminimum term of imprisonment and in imposing two special conditions of \n\nsupervised release.   \n\n    AFFIRMED IN PART, VACATED IN PART, AND REMANDED. \n            \n\n BARBARA A. MASTERSON, Assistant United States \n Attorney (Gregory L. Waples, Assistant United \n States Attorney, on the brief), for Christina E. \n Nolan, United States Attorney for the District of \n Vermont, Burlington, Vermont, for Appellee. \n  \n STEVEN L. BARTH, Assistant Federal Public Defender \n (Barclay T. Johnson, Assistant Federal Public \n Defender, on the brief), for Michael L. Desautels, \n Federal Public Defender for the District of \n Vermont, Burlington, Vermont, for Defendant‐\n Appellant. \n            \n\n \n\n \n\n -2-\n\f  \n\n\nCHIN, Circuit Judge: \n\n    In this case, defendant‐appellant Donald Ray Boles was convicted in \n\nthe United States District Court for the District of Vermont, following a jury trial, \n\nof possession of child pornography in violation of 18 U.S.C. § 2252(a)(4)(B).  On \n\nApril 17, 2017, the district court sentenced him principally to 120 monthsʹ \n\nincarceration and a ten‐year term of supervised release.  On appeal, he contends \n\nthat the district court erred in denying his motion to suppress evidence obtained \n\nin a search of his home pursuant to a warrant.  He raises other issues relating to \n\nhis trial and sentence.  We affirm the conviction and sentence, except that we \n\nvacate the ʺriskʺ condition of his supervised release and remand in that respect \n\nonly. \n\n BACKGROUND  \n\nA.  The Facts1 \n\n In 2001, in an earlier case, Boles pleaded guilty to possession of child \n\npornography, also in the U.S. District Court for the District of Vermont.  The \n\ncourt (Sessions, J.) sentenced him to 15 months in prison and two yearsʹ  \n\n\n\n\n1\n    The facts herein are drawn from the affidavit that supported the warrant for Bolesʹs arrest, J. App. \n40‐66. \n\n -3-\n\f  \n\n\nsupervised release.  Boles served his prison term and completed his supervised \n\nrelease on August 8, 2004.   \n\n In January 2010, the Innocent Images Operations Unit (the ʺIIOUʺ) of \n\nthe Federal Bureau of Investigation (the ʺFBIʺ) investigated the distribution of \n\nchild pornography via an online message board called ʺGirls.Forumcircle.com.ʺ  \n\nThe IIOU investigation revealed that the message board was password‐\n\nprotected, had around 65 members, and was utilized to trade both illegal child \n\npornography and legal ʺchild eroticaʺ (images of children that are not sexually \n\nexplicit but that may be ʺsexually arousing to a given individual,ʺ see United \n\nStates v. Martin, 426 F.3d 68, 79 (2d. Cir. 2005)).  The investigation further \n\nrevealed that a user named ʺdrb05ʺ was a member of Girls.Forumcircle.com and \n\nwas linked to the email address ʺ[email protected].ʺ   \n\n Between August and November 2009, the administrator of \n\nGirls.Forumcircle.com posted messages that usersʹ accounts would be deleted if \n\nthey did not post photos or videos on the forum by November 30.  On November \n\n30, 2009, user drb05 posted 13 images of child erotica (not child pornography) \n\ndepicting a young girl in sexually suggestive poses.  User drb05 also posted two \n\ncomments on the message board indicating a sexual interest in young girls:  one \n\n\n\n -4-\n\f  \n\n\nin response to other usersʹ posts of child erotica on November 29 and one \n\naccompanying drb05ʹs post of child erotica on November 30.   \n\n    On July 19, 2010, the IIOU served a subpoena on Microsoft.  The \n\nresponsive materials revealed that ʺ[email protected]ʺ was associated with a \n\nʺDon Bʺ in ʺVermont, 05301.ʺ  The materials also revealed a log of IP addresses \n\nfor recent logins for [email protected].  On August 4, 2010, the IIOU \n\nsubpoenaed internet service provider FairPoint Communications (ʺFairPointʺ) \n\nrequesting information about subscribers associated with the IP addresses \n\nobtained from Microsoft, but FairPoint responded that it could not link IP \n\naddresses to specific subscribers.   \n\n    During its investigation, the IIOU also operated an FBI undercover \n\nwebsite that advertised access to free child pornography.  The ʺhome pageʺ of the \n\nwebsite made clear that its purpose was to share child pornography.  The home \n\npage also contained a login field that required a unique password to access the \n\nrest of the website.  Users obtained unique passwords by responding to a \n\npersonal email advertisement sent undercover by the FBI.  Once a user entered \n\nthe unique password, the user was taken to the ʺlanding page,ʺ which listed and \n\ndescribed free child pornography videos available to view or download.  When a \n\n\n\n -5-\n\f  \n\n\nuser clicked on the ʺdownloadʺ button for any of these videos, the website \n\nrecorded the userʹs IP address, video sample number, and the number of \n\ndownloads attempted, but no child pornography was actually made available.  \n\nThe landing page also included a link to a ʺpaid area,ʺ where users could \n\nostensibly pay to view a live stream of child pornography from Eastern Europe.   \n\n    On September 2, 2010, the FBI sent such an email to \n\[email protected].  On September 6, 2010, a user from IP address \n\n72.92.136.14 accessed the home page of the undercover website and entered the \n\nunique password sent to [email protected].  After arriving at the landing \n\npage, however, this user did not attempt to view or download any of the \n\nadvertised child pornography videos or access the ʺpaid areaʺ of the undercover \n\nwebsite.  At some point after sending the first email, an agent sent a new email to \n\[email protected], but the user did not respond.  Using this information, the \n\nIIOU again served a subpoena upon FairPoint requesting the information of any \n\nsubscribers associated with the IP address 72.92.136.14, but FairPoint again \n\nstated that it could not link subscribers to IP addresses.   \n\n    Nearly one year later, on July 21, 2011, FBI Special Agent Jeffrey \n\nAlford sent an email to FBI Special Agent Christopher Hughes regarding an \n\n\n\n -6-\n\f  \n\n\napplication for a warrant to search Bolesʹs residence, as Boles was the suspected \n\nowner of [email protected].  In this email, Alford asked whether there had \n\nbeen recent efforts to reach out to Boles regarding the undercover website, \n\nacknowledging that ʺI might otherwise now have a ʹstalenessʹ issue.ʺ  J. App. 67.  \n\nHughes responded that he had sent a new email but ʺ[Boles] did not respond to \n\nthe new request ‐‐ there may be a staleness issue with this at this point but itʹs \n\nworth seeing if the AUSA will go for it.ʺ  J. App. 69.  On August 19, 2011, the \n\nagents confirmed from a subpoena served upon eBay that drb0505@hotmail was \n\noperated by Boles, and the subpoena also revealed Bolesʹs home address.   \n\n    On August 25, 2011, the agents applied for a warrant to search and \n\nseize computer evidence from Bolesʹs residence.  The district court (Sessions, J.) \n\nissued the warrant the same day, finding that probable cause supported the \n\nrequest.  The agents executed the warrant on September 6, 2011.  More than 100 \n\nimages of child pornography were discovered on Bolesʹs computer and hard \n\ndrives.   \n\nB.  Proceedings Below \n\n On July 15, 2014, Boles was charged with possession of child \n\npornography in violation of 18 U.S.C. § 2252(a)(4)(B).  He was ultimately tried on \n\n\n\n -7-\n\f  \n\n\na second superseding indictment (the ʺIndictmentʺ) that charged three counts:  \n\none count of possessing child pornography and two counts of access with intent \n\nto view child pornography, all in violation of 18 U.S.C. § 2252(a)(4)(B).   \n\n On December 22, 2014, Boles moved to suppress the seized evidence \n\non the basis that the warrant was not supported by probable cause and the \n\ninformation in the affidavit was stale when the warrant was issued.  The district \n\ncourt denied Bolesʹs motion in a written decision filed April 2, 2015.2   \n\n Trial commenced on May 31, 2016.  The district court received into \n\nevidence, over Bolesʹs objection, two computers (with hard drives inside) and a \n\nseparate hard drive seized at Bolesʹs residence pursuant to the warrant.  Labels \n\naffixed to the computers and hard drives identified the manufacturer and \n\nshowed the place of origin as being outside the United States (China and \n\nThailand).  Boles argued that the labels were hearsay.  The district court \n\noverruled the objection and admitted the computer evidence.  The district court \n\nalso permitted an FBI agent to testify, again over defense counselʹs objection, that \n\nthe types of computer hardware in question (Hitachi, Compaq, and Hewlett \n\nPackard) were manufactured outside the United States.  On June 3, 2016, the jury \n\n\n2\n    In its opinion, the district court noted that it was ʺin the somewhat unusual position of \nreviewing a warrant that it issued in the first place.ʺ  J. App. 97.   \n -8-\n\f  \n\n\nconvicted Boles on the possession count but acquitted him on the two access \n\ncharges.   \n\n Prior to sentencing, Boles objected to several conditions of \n\nsupervised release proposed in his PSR, including two at issue on this appeal:  \n\n(1) the ʺriskʺ condition, which requires Boles to notify any person or organization \n\nof any risk he posed if his probation officer determined Boles was a risk; and (2) \n\nthe ʺpolygraphʺ condition, which requires Boles to submit to a polygraph exam \n\nas directed by the probation officer as part of his sex offender treatment program.  \n\nAt sentencing on April 17, 2017, the district court overruled Bolesʹs objections to \n\nthe conditions.  The district court sentenced Boles to 120 monthsʹ imprisonment  \n\n‐‐ the mandatory minimum ‐‐ and ten yearsʹ supervised release, imposing the \n\ndisputed conditions.   \n\n This appeal followed. \n\n DISCUSSION \n\n    On appeal, Boles raises three principal challenges:  (1) the district \n\ncourt erred in denying his motion to suppress because the search warrant issued \n\nwithout probable cause; (2) the government failed at trial to sufficiently prove \n\nthe interstate or foreign commerce element of the crime of conviction; and (3) the \n\n\n\n -9-\n\f  \n\n\ndistrict court erred in sentencing him to a mandatory minimum term of \n\nimprisonment and in imposing the two disputed conditions of supervised \n\nrelease.  We discuss each challenge in turn.  \n\nI.  The Motion to Suppress \n\n Boles argues that the warrant to search his residence was not \n\nsupported by probable cause because the affidavit submitted in support of the \n\nrequest for the warrant alleged nothing more than legal activity and was based \n\non stale information.  The government contends, however, that the district court \n\ndid not err in finding probable cause because the record established that Boles \n\nwas a collector of child pornography who likely was hoarding such images.  \n\nMoreover, the government argues that, even assuming the warrant issued \n\nwithout probable cause, the district court did not err in denying the motion \n\nbased on the good faith exception to the exclusionary rule.   \n\n We do not decide whether probable cause existed to support the \n\nissuance of the warrant, for we agree that in the circumstances here, even \n\nassuming the warrant was not supported by probable cause, the good faith \n\nexception applies.   \n\n  \n\n\n\n - 10 -\n\f  \n\n\n  A.  Applicable Law  \n\n    The Fourth Amendment prohibits ʺunreasonable searches and \n\nseizuresʺ and provides that ʺno Warrants shall issue, but upon probable cause, \n\nsupported by Oath or affirmation.ʺ  U.S. Const. amend. IV.   \n\n In determining whether probable cause exists to support the \n\nissuance of a warrant, a judge must ʺmake a practical, common‐sense decision \n\nwhether, given all the circumstances set forth in the affidavit before him, . . . \n\nthere is a fair probability that contraband or evidence of a crime will be found in \n\na particular place.ʺ  United States v. Falso, 544 F.3d 110, 117 (2d Cir. 2008) (quoting \n\nIllinois v. Gates, 462 U.S. 213, 238 (1983)) (alteration in original).  ʺOn appeal from \n\na district courtʹs ruling on a motion to suppress, we review the courtʹs factual \n\nfindings for clear error.  We review the courtʹs legal determinations, including \n\nthe existence of probable cause and the good faith of officers relying on a search \n\nwarrant, de novo.ʺ  United States v. Raymonda, 780 F.3d 105, 113 (2d Cir. 2015) \n\n(citation omitted).  We accord ʺʹsubstantial deference to the finding of an issuing \n\njudicial officer that probable cause exists,ʹ limiting our inquiry to whether the \n\nofficer ʹhad a substantial basisʹ for his determination.ʺ  Id. (quoting United States \n\nv. Wagner, 989 F.2d 69, 72 (2d Cir. 1993)).   \n\n\n\n - 11 -\n\f  \n\n\n Even where a warrant was issued without probable cause in \n\nviolation of the Fourth Amendment, suppression of the evidence is not \n\nautomatic; rather, because the remedy exacts a heavy toll on the justice system, \n\nthe exclusionary rule will apply only to deter ʺdeliberate, reckless, or grossly \n\nnegligent conductʺ by law enforcement.  Herring v. United States, 555 U.S. 135, 144 \n\n(2009).  Accordingly, ʺ[w]hen an officer genuinely believes that he has obtained a \n\nvalid warrant . . . and executes that warrant in good faith, there is no conscious \n\nviolation of the Fourth Amendment, ʹand thus nothing to deter.ʹʺ  Raymonda, 780 \n\nF.3d at 118 (quoting United States v. Leon, 468 U.S. 897, 921 (1984)); see also Falso, \n\n544 F.3d at 125 (explaining that evidence obtained by officers ʺin objectively \n\nreasonable relianceʺ on a subsequently invalidated warrant is not generally \n\nsubject to exclusion). \n\n For an officer to be able to claim the benefits of the good faith \n\nexception, however, his reliance on a warrant must be objectively reasonable.  See \n\nLeon, 468 U.S. at 922.  Thus,  \n\n the good faith exception cannot shield [] an   \n    officer who relies on a duly issued warrant in at  \n    least four circumstances:  (1) where the issuing  \n    magistrate has been knowingly misled; (2) where  \n    the issuing magistrate wholly abandoned his or  \n    her judicial role; (3) where the application is so  \n\n\n - 12 -\n\f  \n\n\n    lacking in indicia of probable cause as to render  \n    reliance upon it unreasonable; and (4) where the  \n    warrant is so facially deficient that reliance upon  \n    it is unreasonable. \n\nRaymonda, 780 F.3d at 118 (quoting United States v. Clark, 638 F.3d 89, 100 (2d Cir. \n\n2011); see also Leon, 468 U.S. at 923 (suppression is an appropriate remedy if the \n\nmagistrate issuing the warrant was ʺmisled by information in an affidavit that \n\nthe affiant knew was false or would have known was false except for his reckless \n\ndisregard of the truthʺ).  ʺWhen the police exhibit ʹdeliberate,ʹ ʹreckless,ʹ or \n\nʹgrossly negligentʹ disregard for Fourth Amendment rights, the deterrent value of \n\nexclusion is strong and tends to outweigh the resulting costsʺ of suppression.  \n\nDavis v. United States, 564 U.S. 229, 238 (2011) (internal quotation marks omitted). \n\n  B.  Application \n\n The existence of probable cause in this case presents a close \n\nquestion.  We need not decide the issue, however, because we conclude that, \n\neven assuming probable cause was lacking, the good faith exception applies.  \n\nThe government argues that even if the warrant to search Bolesʹs residence was \n\nnot supported by probable cause, the FBI agents were justified in relying on the \n\ndistrict courtʹs determination that the warrant was valid.  We agree. \n\n\n\n\n - 13 -\n\f  \n\n\n In Raymonda, we directly addressed the exclusionary rule in the \n\ncontext of an affidavit containing potentially stale and misleading information.  \n\nIn that case, the affidavit supporting the warrant application alleged only that, on \n\none occasion nine months earlier, a user with an IP address associated with \n\nRaymondaʹs home opened between one and three pages of a website housing \n\nthumbnail links to images of child pornography but did not click on any \n\nthumbnails to view full‐sized files.  780 F.3d at 117.  The affidavit was written as \n\nto suggest that the suspect intentionally accessed 76 pornographic images, and, \n\nsignificantly, it omitted the fact that the images were open for just seventeen \n\nseconds, a time span consistent with a user having ʺsimply closedʺ the site \n\nimmediately after clicking on it, rather than intentionally saving or viewing all of \n\nthe images that his browser had accessed.  Id. at 111‐12. \n\n Absent any further indicia that Raymonda was a collector of child \n\npornography, we concluded that the single incident of access, which was ʺat least \n\nequally consistent with an innocent user inadvertently stumbling upon a child \n\npornography website,ʺ did not create a fair probability that child pornography \n\nwould be found on Raymondaʹs computer months later.  Id. at 117.  We therefore \n\nagreed with the district court that the warrant lacked probable cause.  We \n\n\n\n - 14 -\n\f  \n\n\nreversed, however, the district courtʹs grant of Raymondaʹs motion to suppress \n\nthe evidence, holding that the agents who had executed the search were entitled \n\nto rely in good faith on the duly issued warrant for two reasons:  (1) the \n\nmagistrate judge had reached an independent determination of probable cause \n\nthat, while ultimately incorrect, was not contrary to established law or so facially \n\ndeficient that reliance upon it would be unreasonable, and (2) we disagreed with \n\nthe district court that an agent had acted in such a ʺgrossly negligentʺ manner \n\nwith respect to the warrant application as to justify exclusion of the evidence.   \n\nSee id. at 121.   \n\n In concluding that the agent had not been grossly negligent, first, we \n\ndisagreed with the district court that the agent was effectively on notice about a \n\nstaleness issue with the nine‐month old evidence because he had previously \n\nworked on a case in which one‐year‐old evidence was found to be stale.  Id. at \n\n119.  We explained that the agentʹs knowledge that an earlier case found nearly \n\nyear‐old evidence too stale to create probable cause could not have given him \n\nsufficient notice that his affidavit in Raymonda would be found equally deficient.  \n\nSee id. (ʺ[A prior holding by a district court cannot establish a binding principle \n\nof law sufficient to undermine an agentʹs good faith reliance on a later warrant.ʺ). \n\n\n\n - 15 -\n\f  \n\n\n Second, we rejected the argument that there were key omissions and \n\nexaggerations in the affidavit that had materially misled the magistrate judge \n\nissuing the warrant.  Although we acknowledged that the agent ʺmay have \n\nexaggerated the significance ofʺ certain facts and potentially ʺmischaracteriz[ed]ʺ \n\nthe evidence, we nevertheless determined that, absent a finding that the agent \n\nintended to deceive the magistrate judge with these statements, the ʺoversightsʺ \n\nfell ʺshort of deliberate deception or gross negligence.ʺ  Id. at 120.  We therefore \n\nheld that agents were entitled to rely in good faith on the warrant.  See id. at 121.  \n\n As in Raymonda, the agents in this case were entitled to rely in good \n\nfaith on the duly issued warrant.  First, the district court made an independent \n\ndetermination that the warrant was supported by probable cause, which it based \n\nprimarily on:  (1) Bolesʹs membership in Girls.Forumcircle.com and his postings \n\nof child erotica; (2) Bolesʹs visit to the FBI Undercover website using the unique \n\ncode that was emailed to him; and (3) Bolesʹs prior conviction for possession of \n\nchild pornography.  Even assuming that these facts did not add up to probable \n\ncause, the existence of probable cause in this case is an exceedingly close \n\nquestion.  Accordingly, the courtʹs finding of probable cause was not facially \n\n\n\n\n - 16 -\n\f  \n\n\ninsufficient such that any reliance upon the warrant would be unreasonable.  Id. \n\nat 121. \n\n Second, as in Raymonda, the representations in the affidavit here \n\nwere not intentionally false, reckless, or grossly negligent such as to otherwise \n\npreclude the good faith exception.  Boles attempts to distinguish this case from \n\nRaymonda on the ground that here the agents were specifically aware that ʺthere \n\nmay be a staleness issue with [the evidence]ʺ prior to applying for the warrant.  \n\nWe are not persuaded, however, that the agents acted in reckless disregard of \n\nBolesʹs Fourth Amendment rights merely because they knew of a possible \n\nstaleness issue before applying for the warrant.  As the district court noted, the \n\nexchange does indicate ʺsome degree of uncertainty on the part of the agentsʺ as \n\nto whether the evidence would be considered stale.  Sp. App. 15.  But there was \n\nnothing inappropriate in their leaving the issue to the prosecutor and court to \n\nresolve.  As this Court has repeatedly recognized, there is ʺno bright‐line rule for \n\nstaleness,ʺ Walcyzk v. Rio, 496 F.3d 139, 162 (2d Cir. 2007), which depends ʺon the \n\nbasis of the facts of each case,ʺ United States v. Martino, 664 F.2d 860, 867 (2d Cir. \n\n\n\n\n - 17 -\n\f  \n\n\n1981); accord Raymonda, 780 F.3d at 114.  While some of the information here \n\narguably was stale, other facts weighed against a finding of staleness. 3   \n\n Even assuming the information was stale, the agents disclosed the \n\ninformation to a neutral and detached judge, who was made aware of the \n\nʺstaleness issueʺ and the relevant facts and circumstances, but nevertheless \n\nissued the warrant.  The agents cannot be said to have acted in bad faith by \n\nasking a judge to decide the question of staleness.  See Leon, 468 U.S. at 922 \n\n(evidence seized ʺin objectively reasonable reliance onʺ warrant issued by \n\ndetached and neutral judge is admissible, even where reviewing court later \n\ndetermines warrant was invalid).  \n\n\n\n\n3\n   For example, (1) Boles had previously been convicted of possession of child \npornography in June 2000, see Raymonda, 780 F.3d at 114 (evidence that ʺpersons \npossessed child pornography in the past supports a reasonable inference that they \nretain those images ‐‐ or have obtained new ones ‐‐ in the presentʺ); (2) Boles apparently \nhad joined Girls.Forumcircle.com, a website used for posting and trading illegal child \npornography and legal erotica, see Martin, 426 F.3d at 73 (upholding warrant to search \ndefendantʹs computer where he had recently joined an Internet group devoted to \ndistributing child pornography, even absent evidence that he had actually accessed any \nillicit images through that site); and (3) Boles had entered a unique code enabling him to \naccess the FBI undercover page, which advertised its purpose as the distribution of \nchild pornography, see United States v. Vosburg, 602 F.3d 512, 517 (3d Cir. 2010) (no \nstaleness where suspect had to enter decoded URL and could not access images of child \npornography ʺwith a simple click of the mouseʺ).   \n \n - 18 -\n\f  \n\n\n Finally, we note that the affidavit in this case disclosed that Boles \n\nhad not attempted to download child pornography from the FBI undercover \n\nwebsite and that he had not responded to the FBIʹs second email solicitation.  \n\nHence, the agents disclosed these facts to the district court, and the district court \n\nnoted these facts in nonetheless denying the motion.  While the agents here \n\narguably should have provided more information, including, for example, \n\ndetails relating to the Girls.Forumcircle.com website, any omissions and \n\nexaggerations were not as egregious as those in Raymonda, where we held that \n\nthe good faith exception applied even though there were at least arguable \n\nomissions and exaggerations in the agentʹs affidavit.  See 780 F.3d at 122 (Chin, J., \n\ndissenting).  We are hard‐pressed to conclude that the agents acted in a \n\ndeliberate or reckless or grossly negligent manner here. \n\n We therefore agree with the district court that, despite the agentsʹ \n\nuncertainty as to whether the evidence was stale, ʺ[o]nce the Court ruled on the \n\nlegal sufficiency of the facts alleged in the affidavit, the officers were justified inʺ \n\nsubsequently relying on that determination and executing the warrant.  See Sp. \n\nApp. 16; see also Herring, 555 U.S. at 144.  We conclude that the district court did \n\nnot err in denying Bolesʹs motion to suppress the computer evidence. \n\n\n\n - 19 -\n\f  \n\n\nII.  The Interstate or Foreign Commerce Requirement \n\n Boles makes three arguments with respect to the interstate or foreign \n\ncommerce element of the crime of conviction:  (a) the government constructively \n\namended the Indictment in its proof at trial; (b) the government failed to present \n\nsufficient evidence that the images on his computer were ʺproducedʺ using \n\nmaterials transported by a means of interstate or foreign commerce; and (c) the \n\ndistrict court erred in admitting evidence that the computers and hard drives \n\nwere manufactured outside the United States.   \n\n  A.  Constructive Amendment \n\n Boles argues that the government constructively amended the \n\nIndictment charging him with one count of possession of child pornography \n\nunder 18 U.S.C. § 2252(a)(4)(B).4  The Indictment alleged that Boles  \n\n\n\n\n4    The statute provides in relevant part: \n \n Any person who . . . knowingly possesses, or knowingly accesses with \n intent to view, 1 or more books, magazines, periodicals, films, video \n tapes, or other matter which contain any visual depiction that has been \n mailed, or has been shipped or transported using any means or facility of \n interstate or foreign commerce or in or affecting interstate or foreign \n commerce, or which was produced using materials which have been \n mailed or so shipped or transported, by any means including by \n computer, if ‐‐ (i) the producing of such visual depiction involves the use \n of a minor engaging in sexually explicit conduct; and (ii) such visual \n depiction is of such conduct; . . . [commits a crime]. \n  \n 18 U.S.C. § 2252(a)(4)(B). \n\n - 20 -\n\f  \n\n\n possessed at least one matter which contained a \n visual depiction that was produced using \n materials which had been mailed and shipped \n and transported using any means and facility of \n interstate and foreign commerce, including by \n computer, the production of such visual depiction \n involved the use of a minor engaging in sexually \n explicit conduct, and such visual depiction was of \n such conduct. \n\n J. App. 15 (emphasis added).  Boles argues that, as written, the Indictment \n\nrequired the government ʺto prove that the computer hardware was mailed, \n\nshipped, or transported ʹusingʹ a ʹmeans and facility of interstate or foreign \n\ncommerce.ʹʺ  Def.‐Appellantʹs Reply Br. 15 (emphasis in original).  The district \n\ncourt charged the jury, however, that it had to find only ʺthat the visual depiction \n\nwas produced using materials that had been transported in or affecting interstate \n\nor foreign commerce.ʺ  J. App. 271.  Boles contends that the government failed to \n\nprove the actual means by which the hardware had traveled.    \n\n    1.  Applicable Law \n\n We review a constructive amendment challenge de novo.  See United \n\nStates v. Agrawal, 726 F.3d 235, 259 (2d Cir. 2013).  To prevail on a constructive \n\namendment claim, a defendant must establish that ʺthe terms of the indictment \n\nare in effect altered by the presentation of evidence and jury instructions which \n\nso modify essential elements of the offense charged that there is a substantial \n\n - 21 -\n\f  \n\n\nlikelihood that the defendant may have been convicted of an offense other than \n\nthat charged in the indictment.ʺ  United States v. DʹAmelio, 683 F.3d 412, 416 (2d \n\nCir. 2012) (internal quotation marks omitted) (emphasis in original); see also \n\nUnited States v. Spoor, 904 F.3d 141, 152 (2d Cir. 2018).   \n\n Where a defendant fails to raise a claim in the district court, we must \n\nalso review for plain error to assess the impact of any alleged error on the \n\ndefendantʹs rights.  United States v. Taylor, 816 F.3d 12, 18 (2d Cir. 2016).  To \n\nestablish plain error, a defendant must demonstrate ʺ(1) error, (2) that is plain, \n\nand (3) that affect[s] substantial rights.  If all three conditions are met, an \n\nappellate court may then exercise its discretion to notice a forfeited error, but \n\nonly if (4) the error seriously affect[s] the fairness, integrity, or public reputation \n\nof judicial proceedings.ʺ  Id. (brackets in original) (quoting Johnson v. United \n\nStates, 520 U.S. 461, 467 (1997)). \n\n    2.  Application \n\n Boles argues that, under the Indictment as written, the government \n\nwas required to present evidence of the actual means or facility by which the \n\ncomputer hardware traveled interstate.  We conclude that the district court did \n\nnot plainly err in charging the jury that it only had to find that the hardware had \n\n\n\n - 22 -\n\f  \n\n\nbeen transported in or affected interstate commerce.  Boles did not raise this \n\nissue below, and, as did the government, proceeded on the basis that the \n\ngovernment was required only to prove that the computer hardware traveled in \n\ninterstate commerce, not the actual means by which it had traveled.  \n\n Furthermore, in discussions with the district court about the jury \n\ncharge, defense counsel specifically requested that the jurors not see the actual \n\nIndictment because he did not want them ʺfocusedʺ on it.  Boles was therefore \n\nadequately informed about the arguments the government intended to make \n\nabout the jurisdictional element and the types of evidence it would produce to \n\nsupport its theory.  Thus, there was no error, much less error that was ʺplain.ʺ  \n\n Moreover, for purposes of plain error review, we do not view as \n\nsignificant the difference between proving (a) the ʺmeans or facilityʺ of interstate \n\ntravel (that is, how the equipment was physically transported) and (b) the fact \n\nthat the equipment was shipped or transported in interstate or foreign \n\ncommerce.  See 18 U.S.C. § 2252(a)(4)(B) (referring to any matter containing ʺany \n\nvisual depiction that has been . . . shipped or transported using any means or \n\nfacility of interstate or foreign commerceʺ or ʺproduced using materials which \n\nhave been mailed or so shipped or transported, by any meansʺ).    \n\n\n\n - 23 -\n\f  \n\n\n Finally, we have held that there is sufficient evidence to support \n\nconviction for possession of child pornography where a defendant possessed \n\nimages of child pornography on computer equipment manufactured outside this \n\ncountry.  See United States v. Ramos, 685 F.3d 120, 132‐33 (2d Cir. 2012) (applying \n\ninterstate commerce element of § 2252A(a)(5)(B)); accord United States v. \n\nGrzybowicz, 747 F.3d 1296, 1306‐07 (11th Cir. 2014); United States v. Anderson, 280 \n\nF.3d 1121, 1125 (7th Cir. 2002).  Accordingly, we are not persuaded that the error \n\nʺaffect[ed] the fairness, integrity, or public reputation of judicial proceedings.ʺ  \n\nJohnson, 520 U.S. at 467 (internal quotation marks omitted).  \n\n  B.  The Evidence of ʺProductionʺ \n\n Boles further argues that the government failed to prove that the \n\nhardware was used to ʺproduceʺ the child pornography because the government \n\ndid not present evidence that the seized hardware was used to create the child \n\npornography in the first instance (i.e., that Boles had manufactured the child \n\npornography using the hardware rather than merely storing copies of the images \n\non the hardware).    \n\n This Court has not specifically addressed the question of whether \n\nmerely transferring or copying child pornography using materials that have \n\n\n\n - 24 -\n\f  \n\n\ntraveled interstate means that the child pornography has been ʺproducedʺ using \n\nthose materials as required under 18 U.S.C. § 2552(a)(4)(B).  See Ramos, 685 F.3d \n\nat 133 n.10 (explaining that the court would not reach the question of whether \n\nʺthe mere copying or downloading of an image is ʹproductionʹ for purposes of \n\nthe federal child pornography statutesʺ).5  \n\n    Almost every circuit to address this issue, however, has held that the \n\nword ʺproducedʺ encompasses mere copying or downloading of child \n\npornography.  See United States v. Burdulis, 753 F.3d 255, 262 (1st Cir. 2014) \n\n(images are ʺproducedʺ for the purposes of § 2254(a)(4)(B) when they are copied \n\nor downloaded onto a digital medium); United States v. Dickson, 632 F.3d 186, \n\n189‐90 (5th Cir. 2011) (same); United States v. Angle, 234 F.3d 326, 341 (7th Cir. \n\n2000) (same); United States v. Lacy, 119 F.3d 742, 750 (9th Cir. 1997) (same).  But see \n\nUnited States v. Wilson, 182 F.3d 737, 742‐43 (10th Cir. 1999) (holding that the \n\n\n5   Although the government argues that we decided this issue in United States v. Pattee, 820 \nF.3d 496 (2d Cir. 2016), there we interpreted ʺproductionʺ in the context of 18 U.S.C. § 2251, \nrather than the statute at issue here, 18 U.S.C. § 2252(a)(4)(B).  Moreover, we noted that  \n\n [i]t does not follow from this conclusion, however, that merely \n transferring or copying a pornographic image that was produced \n by someone else is tantamount to ʺproducingʺ child pornography, \n such that simple possession, which typically involves making a \n copy of a file to a hard disk or other medium, would qualify as \n production. \n\nId. at 511 n.8. \n - 25 -\n\f  \n\n\ngovernment produced insufficient evidence to support the interstate commerce \n\nelement of § 2252(a)(4)(B) because there was no evidence that the digital \n\nmediums were used to produce the graphic files even though the files could be \n\nstored on the mediums). \n\n    Those circuits that have interpreted ʺproducedʺ to include copying \n\nor transferring rely on 18 U.S.C. § 2256(3), which defines the word ʺproducingʺ in \n\nthe child pornography and child exploitation statutes to mean ʺproducing, \n\ndirecting, manufacturing, issuing, publishing, or advertising.ʺ  18 U.S.C. \n\n§ 2256(3); see also Angle, 234 F.3d at 341.  The plain meaning of the word \n\nʺproducedʺ would include producing or making a copy.  Moreover, we agree \n\nthat to interpret ʺproducedʺ to exclude pulling up images on a computer monitor \n\nis ʺfar too restrictive as it essentially renders meaningless the statutory definition \n\nof ʹproducingʹ [in § 2256(3)] . . . and focuses entirely on the circumstances \n\nsurrounding the original or actual production of the visual depiction.ʺ  Angle, 234 \n\nF.3d at 241.  To read the statute this way would require the government to \n\npresent evidence about the original materials used to create the child \n\npornography in every case a defendant is charged under the ʺproduced using \n\nmaterialsʺ language.  Boles fails to point to, and we are unable to find, any \n\n\n\n - 26 -\n\f  \n\n\nevidence that Congress intended these subsections to be applied so narrowly.  \n\nIndeed, the nature of the industry is that these images are copied over and over \n\nagain as collectors share them, and it would be difficult in many cases to prove \n\nthe circumstances of the original ʺproduction.ʺ  \n\n    Therefore, we agree that the government was not required to prove \n\nthat the hardware was used to create the pornography in the first instance and \n\nthat it was sufficient for the government to prove that the hardware was used to \n\nmake, store, or display copies of the pornographic images.   \n\n  C.  The Evidence the Computer Equipment \n    Was Manufactured Outside the United States \n \n    Boles argues that the district court erred by (1) admitting \n\ninscriptions on the back of seized pieces of computer hardware because the \n\nlabels were inadmissible hearsay; and (2) allowing Agent Alfin to testify as an \n\nexpert about where the relevant companies manufacture hardware.   \n\n    A district court has ʺbroad discretionʺ over the admission of \n\nevidence.  United States v. Nektalov, 461 F.3d 309, 318 (2d Cir. 2006).  Accordingly, \n\nʺ[t]his [C]ourt reviews evidentiary rulings for abuse of discretion.ʺ  United States \n\nv. Cummings, 858 F.3d 763, 771 (2d Cir. 2017).  ʺA district court has abused its \n\ndiscretion if it based its ruling on an erroneous view of the law or on a clearly \n\n - 27 -\n\f  \n\n\nerroneous assessment of the evidence or rendered a decision that cannot be \n\nlocated within the range of permissible decisions.ʺ  United States v. Natal, 849 F.3d \n\n530, 534 (2d Cir. 2017) (per curiam) (internal quotation marks omitted).  \n\n     1.  The Hardware Inscriptions   \n\n We have not directly addressed whether manufacturersʹ inscriptions \n\nor labels identifying a productʹs country of origin are inadmissible hearsay.  We \n\nconclude that the district court did not abuse its discretion in allowing evidence \n\nof the inscriptions here.   \n\n As a threshold matter, there is some doubt as to whether the \n\ninscriptions are hearsay at all, as the government, relying principally on gun \n\ncases, argues that under the ʺmechanical traceʺ theory, markings on products \n\ndesignating country of origin are not ʺstatementsʺ subject to the hearsay rule.  See \n\nFed. R. Civ. P. 801(a), (c); United States v. Bowling, 32 F.3d 326, 328 (8th Cir. 1994) \n\n(holding that manufacturerʹs name stamped on firearm was not ʺa statement of \n\nfactʺ subject to hearsay rule); United States v. Thody, 978 F.2d 625, 630‐31 (10th Cir. \n\n1992) (ʺ[T]he manufacturerʹs imprint in the gun is not hearsay.  It is technically \n\nnot an assertion by a declarant as contemplated by the [hearsay rule].ʺ); United \n\nStates v. Alvarez, 972 F.2d 1000, 1004 (9th Cir. 1992) (ʺAn inscription placed on a \n\n\n\n - 28 -\n\f  \n\n\nfirearm by the manufacturer is similarly a mechanical trace and not a statement \n\nfor purposes of Federal Rule of Evidence 801(c).ʺ), overruled on other grounds by \n\nKawashima v. Mukasey, 530 F.3d 1111, 1116 (9th Cir. 2008).  We need not decide \n\nthe issue because, even assuming the inscriptions here are hearsay, we conclude \n\nthat they are nonetheless admissible.   \n\n Inscriptions indicating foreign origin are regulated, see 19 U.S.C. \n\n§ 1304, and federal law prohibits misleading designations of origin, see 15 U.S.C. \n\n§ 1405.  Additionally, under Federal Rule of Evidence 902(7), trade inscriptions \n\nare self‐authenticating, that is, they ʺrequire no extrinsic evidence of authenticity \n\nin order to be admitted.ʺ  Fed. R. Evid. 902.  While Boles is correct that self‐\n\nauthentication alone does not qualify as an exception to the hearsay rule, it does \n\nrender the inscriptions particularly trustworthy.  As the First Circuit has noted, \n\nʺ[a]n authentic inscription, of the kind made regularly by manufacturers in \n\naccordance with federal law, bears significant similarity to other forms of \n\nevidence admissible under the enumerated hearsay exceptions.ʺ  Burdulis, 753 \n\nF.3d at 263‐64 (citing Fed. R. Evid. 803(6) (records of regularly conducted \n\nactivity), 803(9) (certain information reported to a public office in accordance \n\nwith a legal duty), and 807 (residual exception)); accord United States v. Koch, 625 \n\n\n\n - 29 -\n\f  \n\n\nF.3d 470, 480 (8th Cir. 2010) (rejecting claim that ʺmanufacturerʹs inscription on a \n\nproduct is inadmissible hearsayʺ).  Any of these exceptions would suffice here, \n\nand we hold that the district court did not abuse its discretion in overruling the \n\nhearsay objection.   \n\n    2.  The Agentʹs Testimony as an Expert \n\n    Boles also argues that the district court erred by permitting FBI \n\nSpecial Agent Alfin to testify about the origin of the computer hardware.  Rule \n\n702 permits testimony in the form of an opinion only if ʺthe expertʹs scientific, \n\ntechnical, or other specialized knowledge will help the trier of fact to understand \n\nthe evidence or to determine a fact in issue.ʺ  Fed. R. Evid. 702(a).  Boles \n\nadditionally argues that the defense had been given no prior notice in the \n\ngovernmentʹs Rule 16 expert disclosure that Alfin would testify about the \n\nmanufacturing origin of the hardware.   \n\n    A district court has ʺbroad discretionʺ in deciding whether to admit \n\nexpert testimony, and the exercise of that discretion will not be disturbed unless \n\nit is ʺmanifestly erroneous.ʺ  United States v. Locasio, 6 F.3d 924, 936 (2d Cir. 1993); \n\naccord United States v. Dukagjini, 326 F.3d 45, 52 (2d Cir. 2003).  We discern no \n\nmanifest error here, where the district court permitted an FBI agent with \n\n\n\n - 30 -\n\f  \n\n\nspecialized training and experience in computers, computer forensics, and \n\nforensic imaging to testify that he knew the computer hardware in question was \n\nmanufactured outside Vermont and outside the United States.   \n\n While there is a dispute as to whether the government provided \n\nsufficient notice of the agentʹs testimony as an expert as required by Fed. R. \n\nCrim. P. 16(a), even assuming the testimony was not properly noticed, the \n\ndistrict court had the discretion to admit the evidence nonetheless as long as the \n\nviolation did not cause Boles ʺsubstantial prejudice.ʺ  United States v. Thai, 29 F.3d \n\n785, 804 (2d Cir. 1994).  Here, Boles has not identified any prejudice from the \n\npurported lack of advance notice, and the record is clear in any event that Boles \n\nand his counsel knew that the government intended to introduce evidence to \n\nprove the interstate or foreign commerce nexus.  Finally, as we have held that the \n\nmanufacturersʹ inscriptions were admissible, any error with respect to the \n\nadmission of the agentʹs testimony in this respect was harmless. \n\nIII.  The Sentence \n\n    Boles raises two challenges to his sentence: (a) the imposition of the \n\nmandatory minimum term of imprisonment; and (b) the imposition of the two \n\ndisputed special conditions of supervised release. \n\n\n\n - 31 -\n\f  \n\n\n A. The Mandatory Minimum \n\n First, Boles argues that the district courtʹs application of the ten‐year \n\nmandatory minimum penalty, under 18 U.S.C. § 2252(b)(2), violated the Sixth \n\nAmendment because Bolesʹs prior conviction was not found by the jury beyond a \n\nreasonable doubt.  His argument, however, is expressly foreclosed by this \n\nCourtʹs decision in United States v. Arline, 835 F.3d 277 (2d Cir. 2016) (per curiam), \n\nwhere we acknowledged that ʺ[t]he fact of a prior conviction may be decided by \n\na judge and need not be determined by a jury.ʺ  Id. at 280 (citation omitted).  \n\nAccordingly, the district court properly recognized that the mandatory minimum \n\nof ten years applied to Boles. \n\n  B.   The Conditions of Supervised Release \n\n    Second, Boles raises challenges to two conditions of his supervised \n\nrelease.  He challenges Standard Condition 17, the ʺriskʺ condition, which \n\nprovides: \n\n   If the probation officer determines that you pose a risk \n to another person (including an organization), the \n probation officer may require you to notify the person \n about the risk and you must comply with that \n instruction.  The probation officer may contact the \n person and confirm that you have notified the person \n about the risk. \n  \nPSR ¶ 95, Cond. 27.   \n\n - 32 -\n\f  \n\n\n Boles specifically argues that the risk condition is ʺfar too vague to \n\nbe related to any goal of supervisionʺ because the court did not define ʺrisk,ʺ and \n\nthe condition leaves ʺtoo much discretion[] to the supervising officer.ʺ  Def.‐\n\nAppellantʹs Br. 14‐15. \n\n Boles also challenges the ʺpolygraphʺ condition of supervised \n\nrelease, which provides that Boles: \n\n shall participate in an approved program of sex \n offender evaluation and treatment, which may \n include polygraph examinations, as directed by \n the probation officer.  Any refusal to submit to \n such assessment or tests as scheduled is a \n violation of the conditions of supervision. \n  \nPSR ¶ 96, Cond. (a). \n\n    Boles contends that the condition violates the Fifth Amendment, \n\nbecause if he answers questions, he may incriminate himself, and on the other \n\nhand, if he invokes his Fifth Amendment right to remain silent, he violates the \n\ncondition, and will be subject to having his supervised release revoked.   \n\n    1.  Applicable Law \n\n We generally review the imposition of conditions of supervised \n\nrelease for abuse of discretion.  See United States v. Reeves, 591 F.3d 77, 80 (2d Cir. \n\n2010).  ʺWhen a challenge to a condition of supervised release presents an issue \n\n - 33 -\n\f  \n\n\nof law,ʺ however, ʺwe review the imposition of that condition de novo, bearing in \n\nmind that any error of law necessarily constitutes an abuse of discretion.ʺ  United \n\nStates v. McLaurin, 731 F.3d 258, 261 (2d Cir. 2013) (internal quotation marks \n\nomitted).  \n\n A district court may  \n\n impose special conditions of supervised release to \n the extent that they are reasonably related to (i) \n the nature and circumstances of the offense and \n the history and characteristics of the defendant, \n and (ii) the purposes of sentencing, including the \n need to afford adequate deterrence, to protect the \n public from further crimes of the defendant, and \n to provide the defendant with needed training or \n treatment. \n\nUnited States v. Johnson, 446 F.3d 272, 277 (2d Cir. 2006) (quoting United States v. \n\nGermosen, 139 F.3d 120, 131 (2d Cir. 1998)); see also 18 U.S.C. § 3583(d).  ʺWhile \n\ndistrict courts have broad discretion to tailor conditions of supervised release, \n\nthat discretion is not unfettered,ʺ and we will ʺcarefully scrutinize conditions that \n\nmay be excessively harsh or inexplicably punitive.ʺ  United States v. Jenkins, 854 \n\nF.3d 181, 188 (2d Cir. 2017) (internal citations omitted). \n\n    2.  Application \n\n As to the first challenged condition, we agree with Boles that the \n\nʺriskʺ condition is vague and affords too much discretion to the probation officer.  \n\n - 34 -\n\f  \n\n\nIn United States v. Peterson, we vacated a district courtʹs imposition of two similar \n\nstandard conditions of supervised release, in part, because they, too, gave the \n\nprobation officer too much discretion.  248 F.3d 79, 86 (2d Cir. 2001) (per curiam).  \n\nThe defendant in Peterson was convicted of bank larceny, but the court noted that \n\nthe supervised release conditions were ʺbased in part on a prior, unrelated New \n\nYork state‐sex‐offense conviction [for incest].ʺ  Id. at 81. \n\n In Peterson, we held that the conditions were impermissible to the \n\nextent that they required Peterson to notify employers about his state conviction, \n\nbecause occupational restrictions must be related to the offense of conviction at \n\nissue.  Id. at 85‐86.  We further held, to the extent that the conditions required \n\nPeterson to notify employers about his federal conviction, ʺthe [district] court \n\nmust determine, rather than leaving to the discretion of the probation officer, \n\nwhether such notification is required . . . [and] may not simply leave the issues of \n\nemployer notification to the probation officerʹs unfettered discretion.ʺ  Id. at 86.  \n\nWe therefore remanded the case for clarification of the nature and scope of \n\nemployer notification of the offense of conviction.  Id.   \n\n Because the condition at issue here extends to warning employers of \n\nrisk and gives the probation office unfettered discretion with respect to the \n\n\n\n - 35 -\n\f  \n\n\nnotification requirement, we agree with Boles that the condition is largely \n\nindistinguishable from the one we struck down in Peterson.  Accordingly, we \n\nvacate the risk condition and remand to the district court to clarify the scope of \n\nthe ʺriskʺ condition. \n\n We are not persuaded, however, as to Bolesʹs challenge to the \n\npolygraph condition of supervised released.  In Johnson, 446 F.3d at 272, we \n\nupheld a polygraph condition against a Fifth Amendment challenge, similar to \n\nthe one at issue here.  We held that requiring a defendant to take a polygraph test \n\nas a condition of his supervised release does not violate the Fifth Amendment \n\nbecause the defendant retains the right to later challenge any resulting self‐\n\nincrimination in court.  Id. at 280; see also Asherman v. Meachum, 957 F.2d 978, 982‐\n\n83 (2d Cir. 1992) (en banc) (explaining that revocation may be based on a refusal \n\nto answer questions, so long as the administrator does nothing to impair later \n\ninvocation of the Fifth Amendment privilege).   \n\n Furthermore, in upholding the condition in Johnson, we recognized \n\nthe strong deterrent value of polygraph conditions, explaining that such \n\nconditions ʺfurther sentencing objectives such as rehabilitation and deterrence, \n\nwith reasonably small incremental deprivations of liberty.ʺ  Johnson, 446 F.3d at \n\n\n\n - 36 -\n\f  \n\n\n278.  When the district court imposed the polygraph condition at issue here, it \n\nspecifically noted that the condition is ʺa tremendous deterrent and satisfies a \n\nvery legitimate purpose in probationary supervision.ʺ  J. App. 396.  Accordingly, \n\nwe conclude that the district court did not abuse its discretion in ordering \n\npolygraph examinations as part of Bolesʹs sex offender treatment following his \n\nmost recent conviction.    \n\n CONCLUSION \n\n    For the reasons set forth above, we AFFIRM the judgment in all \n\nrespects except that we VACATE the ʺriskʺ condition of supervised release and \n\nREMAND to the district court for clarification as set forth above. \n\n \n\n\n\n\n - 37 -\n[END_CASE]", "role": "user" } ]
8,443,854
United States v. Donald Ray BOLES
United States v. Boles
2019-01-25
Docket No. 17-1138-cr; August Term 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Carney, Chin, Wesley", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415281/", "author_raw": ""}]}
CARNEY
CHIN
WESLEY
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443854/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Donald Ray BOLES\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,585,383
Bellamy v. City of New York
2019-01-29
17-1859
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: WALKER AND JACOBS, Circuit Judges, SHEA, District Judge.", "parties": "", "opinions": [{"author": "", "type": "010combined", "text": "17‐1859 \n Bellamy v. City of New York \n\n 1 In the\n 2 United States Court of Appeals\n 3 For the Second Circuit\n 4 ________ \n 5  \n 6 AUGUST TERM, 2017 \n 7  \n 8 ARGUED: APRIL 26, 2018  \n 9 DECIDED: JANUARY 29, 2019 \n10  \n11 No. 17‐1859‐cv \n12  \n13 KAREEM BELLAMY, \n14 Plaintiff‐Appellant, \n15  \n16 v. \n17  \n18 CITY OF NEW YORK, JOHN J. GILLEN, AND MICHAEL F. SOLOMENO,  \n19 Defendants‐Appellees, \n20  \n21 John Doe 1, John Doe 2, Supervising Officers at the NYPD 101st \n22 Precinct, Vincent NMI Pepe, and Robert Schruhl, \n23 Defendants. \n24 ________ \n25  \n26 Appeal from the United States District Court \n27 for the Eastern District of New York. \n28 No. 12‐cv‐01025 – Ann M. Donnelly, Judge. \n29 ________ \n30  \n31 Before: WALKER AND JACOBS, Circuit Judges, SHEA, District Judge. \n32 ________ \n\n \n   Judge  Michael  P.  Shea,  of  the  United  States  District  Court  for  the \n District of Connecticut, sitting by designation. \n\n 2  No. 17‐1859\n\n 1 Kareem Bellamy filed this action in the Eastern District of New \n\n 2 York under New York state law and 42 U.S.C. § 1983 following the \n\n 3 vacatur of his state convictions for murder in the second degree under \n\n 4 N.Y. Penal Law § 125.25(2) and criminal possession of a weapon in \n\n 5 the  fourth  degree  under  N.Y.  Penal  Law  §  265.01(2),  for  which  he \n\n 6 served more than 14 years of a 25 years‐to‐life sentence.  Bellamy sued \n\n 7 investigating  Detectives  Michael  Solomeno  and  John  Gillen  of  the \n\n 8 New York Police Department (and certain John Does) as well as the \n\n 9 City  of  New  York  (at  times,  the  “City”),  alleging  that  each  are \n\n10 responsible  for  constitutional  infirmities  that  infected  Bellamy’s \n\n11 criminal  trial,  caused  his  wrongful  conviction,  and  resulted  in \n\n12 damages.  The  district  court  granted  the  Defendants’  motion  for \n\n13 summary judgment. \n\n14 As  relevant  on  appeal,  Bellamy  alleged  that  Detectives \n\n15 Solomeno  and  Gillen  fabricated  inculpatory  evidence  and  failed  to \n\n16 disclose  material  exculpatory  or  impeaching  evidence  depriving \n\n17 Bellamy of his rights to due process and a fair trial.  Bellamy alleged \n\n18 that the City is responsible, pursuant to Monell v. Department of Social \n\n19 Services  of  City  of  New  York,  436  U.S.  658  (1978),  for  violations  of \n\n20 Bellamy’s due process rights caused by certain policies of the office of \n\n21 the  Queens  County  District  Attorney  (“QCDA”),  the  office  that \n\n22 prosecuted Bellamy.  Principally, Bellamy alleged that (i) the QCDA’s \n\n23 office failed to disclose to the defense substantial benefits received by \n\n 3  No. 17‐1859\n\n 1 a key state witness due to an office policy of purposefully shielding \n\n 2 from prosecutors (and thereby the defense) the full scope of relocation \n\n 3 benefits  given  to  witnesses  in  its  witness  protection  program;  and \n\n 4 (ii) his  prosecutor  made  prejudicial  improper  remarks  during  his \n\n 5 summation,  which  was  ultimately  a  result  of  the  QCDA’s  office’s \n\n 6 customary indifference to its prosecutors’ summation misconduct.   \n\n 7 The district court (Donnelly, J.) granted Defendants’ motion for \n\n 8 summary  judgment  and  dismissed  each  of  Bellamy’s  claims.    As \n\n 9 relevant here, the district court rejected the claims against Detectives \n\n10 Solomeno and Gillen on the ground that Bellamy raised no material \n\n11 issue  of  fact  as  to  whether  either  detective  fabricated  or  withheld \n\n12 material evidence.  The district court rejected the claims against the \n\n13 City, concluding that the City could not as a matter of law be liable \n\n14 under Monell for the alleged policies of the QCDA’s office, and that, \n\n15 in any event, Bellamy did not raise a material issue of fact as to either \n\n16 of the constitutional violations underlying his Monell claims. \n\n17 The questions for our determination are whether Bellamy has \n\n18 produced sufficient evidence to raise material issues of fact that must \n\n19 be tried to a jury and whether the district court erred in dismissing \n\n20 the Monell claims as a matter of law.  If not, summary judgment was \n\n21 proper; if so, then summary judgment should not have been granted. \n\n22  \n\n 4  No. 17‐1859\n\n 1 We conclude that Bellamy has raised material issues of fact as \n\n 2 to  certain,  but  not  all,  of  his  claims  that  Detectives  Solomeno  and \n\n 3 Gillen fabricated and withheld material evidence, and we therefore \n\n 4 VACATE  in  part  and  AFFIRM  in  part  the  dismissal  of  Bellamy’s \n\n 5 claims against them.  We further conclude that the City of New York \n\n 6 may be held liable for the consequences of the alleged policies of the \n\n 7 QCDA’s office under the Monell doctrine, and that Bellamy has raised \n\n 8 material issues of fact as to the underlying constitutional violations: \n\n 9 the non‐disclosure of financial benefits received by one of the state’s \n\n10 principal  witnesses  and  the  impropriety  of  his  prosecutor’s \n\n11 summation.  Consequently, we VACATE the dismissal of Bellamy’s \n\n12 claims against the City.   \n\n13 We REMAND the cause for further proceedings consistent with \n\n14 this opinion. \n\n15 Judge Jacobs dissents in a separate opinion.  \n\n16 ________ \n17  \n18 JOEL  B.  RUDIN,  Law  Office  of  Joel  B.  Rudin,  P.C., \n19 New York, NY, for Plaintiff‐Appellant. \n20  \n21 MEGAN  E.K.  MONTCALM  (Richard Dearing, on the \n22 brief), for Zachary W. Carter, Corporation Counsel \n23 of  the  City  of  New  York,  New  York,  NY,  for \n24 Defendants‐Appellees. \n25  \n26 Richard D. Willstatter, Vice Chair, Amicus Curiae \n27 Committee of the National Association of Criminal \n\n 5  No. 17‐1859\n\n 1 Defense  Lawyers,  Chair,  Amicus  Curiae \n 2 Committee  of  the  New  York  State  Association  of \n 3 Criminal  Defense  Lawyers,  White  Plains,  NY; \n 4 Adele  Bernhard,  Innocence  Network,  New  York, \n 5 NY;  Barry  Scheck,  Innocence  Project,  New  York, \n 6 NY; Ross E. Firsenbaum, Wilmer Cutler Pickering \n 7 Hale  and  Door  LLP,  New  York  NY,  for  Amici \n 8 Curiae  National  Association  of  Criminal  Defense \n 9 Lawyers,  New  York  State  Association  of  Criminal \n10 Defense  Lawyers,  Innocence  Network,  and  Innocence \n11 Project. \n12 ________ \n13  \n14 JOHN M. WALKER, JR., Circuit Judge: \n\n15  Kareem Bellamy filed this action in the Eastern District of New \n\n16 York under New York state law and 42 U.S.C. § 1983 following the \n\n17 vacatur of his state convictions for murder in the second degree under \n\n18 N.Y. Penal Law § 125.25(2) and criminal possession of a weapon in \n\n19 the  fourth  degree  under  N.Y.  Penal  Law  §  265.01(2),  for  which  he \n\n20 served  more  than  14  years  of  a  25  years‐to‐life  sentence.      Bellamy \n\n21 sued investigating Detectives Michael Solomeno and John Gillen of \n\n22 the New York Police Department (and certain John Does) as well as \n\n23 the  City  of  New  York  (at  times,  the  “City”),  alleging  that  each  are \n\n24 responsible  for  constitutional  infirmities  that  infected  Bellamy’s \n\n25 criminal  trial,  caused  his  wrongful  conviction,  and  resulted  in \n\n26 damages.  The  district  court  granted  the  Defendants’  motion  for \n\n27 summary judgment. \n\n 6  No. 17‐1859\n\n 1 As  relevant  on  appeal,  Bellamy  alleged  that  Detectives \n\n 2 Solomeno  and  Gillen  fabricated  inculpatory  evidence  and  failed  to \n\n 3 disclose  material  exculpatory  or  impeaching  evidence  depriving \n\n 4 Bellamy of his rights to due process and a fair trial.  Bellamy alleged \n\n 5 that the City is responsible, pursuant to Monell v. Department of Social \n\n 6 Services  of  City  of  New  York,  436  U.S.  658  (1978),  for  violations  of \n\n 7 Bellamy’s due process rights caused by certain policies of the office of \n\n 8 the  Queens  County  District  Attorney  (“QCDA”),  the  office  that \n\n 9 prosecuted Bellamy.  Principally, Bellamy alleged that (i) the QCDA’s \n\n10 office failed to disclose to the defense substantial benefits received by \n\n11 a key state witness due to an office policy of purposefully shielding \n\n12 from prosecutors (and thereby the defense) the full scope of relocation \n\n13 benefits  given  to  witnesses  in  its  witness  protection  program;  and \n\n14 (ii) his  prosecutor  made  prejudicial  improper  remarks  during  his \n\n15 summation,  which  was  ultimately  a  result  of  the  QCDA’s  office’s \n\n16 customary indifference to its prosecutors’ summation misconduct.   \n\n17 The district court (Donnelly, J.) granted Defendants‐Appellees’ \n\n18 motion  for  summary  judgment  and  dismissed  each  of  Bellamy’s \n\n19 claims.  As relevant here, the district court rejected the claims against \n\n20 Detectives Solomeno and Gillen on the ground that Bellamy raised no \n\n21 material  issue  of  fact  as  to  whether  either  detective  fabricated  or \n\n22 withheld  material  evidence.    The  district  court  rejected  the  claims \n\n23 against the City, concluding that the City could not as a matter of law \n\n 7  No. 17‐1859\n\n 1 be liable under Monell for the alleged policies of the QCDA’s office, \n\n 2 and that, in any event, Bellamy did not raise a material issue of fact as \n\n 3 to either of the constitutional violations underlying his Monell claims. \n\n 4 The questions for our determination are whether Bellamy has \n\n 5 produced sufficient evidence to raise material issues of fact that must \n\n 6 be tried to a jury and whether the district court erred in dismissing \n\n 7 the Monell claims as a matter of law.  If not, summary judgment was \n\n 8 proper; if so, then summary judgment should not have been granted. \n\n 9 We conclude that Bellamy has raised material issues of fact as \n\n10 to  certain,  but  not  all,  of  his  claims  that  Detectives  Solomeno  and \n\n11 Gillen fabricated and withheld material evidence, and we therefore \n\n12 VACATE  in  part  and  AFFIRM  in  part  the  dismissal  of  Bellamy’s \n\n13 claims against them.  We further conclude that the City of New York \n\n14 may be held liable for the consequences of the alleged policies of the \n\n15 QCDA’s office under the Monell doctrine, and that Bellamy has raised \n\n16 material issues of fact as to the underlying constitutional violations: \n\n17 the non‐disclosure of financial benefits received by one of the state’s \n\n18 principal  witnesses  and  the  impropriety  of  his  prosecutor’s \n\n19 summation.  Consequently, we VACATE the dismissal of Bellamy’s \n\n20 claims against the City.   \n\n21 We REMAND the cause for further proceedings consistent with \n\n22 this opinion. \n\n 8  No. 17‐1859\n\n 1 BACKGROUND \n\n 2   This appeal requires us to address the complex and protracted \n\n 3 facts surrounding the events pertaining to the 1994 killing of James \n\n 4 Abbott.    While  Plaintiff‐Appellant  Kareem  Bellamy  was  ultimately \n\n 5 convicted in New York state court for Abbott’s murder, the uncertain \n\n 6 circumstances  of  the  killing,  and  the  investigation  and  trial  that \n\n 7 followed, sparked a lengthy, circuitous, and at times dramatic legal \n\n 8 fight  that  continued  into  post‐conviction  proceedings.    That  battle \n\n 9 began  with  what  the  record  shows  to  have  been  a  hard‐fought \n\n10 criminal trial with no certain outcome in sight.  Ultimately, Bellamy \n\n11 was acquitted on the charge of intentional murder but convicted of \n\n12 depraved indifference murder and unlawful possession of a weapon.  \n\n13 After  Bellamy  exhausted  his  direct  appeal  opportunities  without \n\n14 success,  the  post‐conviction  litigation  proceeded  in  two  general \n\n15 stages.  First, after a prolonged and complicated state post‐conviction \n\n16 process,  the  state  court  vacated  Bellamy’s  convictions  in  light  of \n\n17 newly  discovered  evidence  that  another  individual  might  have \n\n18 committed the Abbott murder.  Second, following the state’s decision \n\n19 not  to  re‐try  him  and  his  release  from  prison,  Bellamy  sought  civil \n\n20 relief in federal court alleging that his criminal trial was infected with \n\n21 constitutional error.  The instant lawsuit concerns only the latter fight, \n\n22 which pertains not to how or why Bellamy was released but whether \n\n23 constitutional error led to his conviction in the first place. \n\n 9  No. 17‐1859\n\n 1   In assessing the constitutional propriety of Bellamy’s criminal \n\n 2 trial,  we  are  aided  by  (i)  an  extensive  summary  judgment  record, \n\n 3 which  includes  documents  related  to  the  investigation  and \n\n 4 prosecution  of  Bellamy;  (ii)  the  record  of  Bellamy’s  criminal  trial; \n\n 5 (iii) the  record  of  Bellamy’s  state  post‐conviction  proceedings;  and \n\n 6 (iv) extensive  deposition  testimony  taken  in  this  action.1    Although \n\n 7 much is in contention in this case, what follows are the undisputed \n\n 8 facts  from  this  complicated  record  and  other  relevant  facts  that  we \n\n 9 identify as remaining in dispute. \n\n10 I. James Abbott’s Murder and the Resulting Investigation \n\n11 Shortly  before  10:00  a.m.,  on  Saturday,  April  9,  1994,  an \n\n12 assailant fatally stabbed James Abbott near a phone booth during an \n\n13 altercation after Abbott left a C‐Town Supermarket in Far Rockaway, \n\n14 Queens.   Detectives Michael Solomeno and John Gillen of the NYPD’s \n\n15 101st Precinct were assigned to investigate.  In canvassing the area, \n\n16 Detective Gillen, with other officers, entered the C‐Town store with a \n\n17 photo of Abbott to see if anyone had witnessed anything.  Detective \n\n\n\n   Throughout  this  opinion,  we  cite  to  the  transcripts  of  Bellamy’s \n 1\n\n criminal trial (“Trial Tr.”), the first and second hearings held on Bellamy’s \n New York state post‐conviction motion filed pursuant to N.Y. Crim. Proc. \n Law  §  440.10  (“First  440  Tr.”  and  “Second  440  Tr.,”  respectively),  and \n deposition testimony taken in this case (“[] Dep. Tr.”).  We direct the reader \n to the district court docket to review the full versions of these transcripts.  \n See No. 12‐cv‐1025 (E.D.N.Y.), Dkt. Nos. 188–99, 204–13 [hereinafter, “Dkt. \n No. []”]. \n\n 10  No. 17‐1859\n\n 1 Gillen spoke with Jay Judel, a C‐Town deli clerk, who reported that \n\n 2 Abbott, a regular customer, had been in the store alone that morning.   \n\n 3 Another officer interviewed Andrew Carter, a wheelchair‐bound man \n\n 4 living adjacent to the C‐Town who said that he saw the attack while \n\n 5 waiting at a bus stop down the street from the phone booth where the \n\n 6 altercation took place.  Carter told the officer that he saw three males \n\n 7 he did not recognize leave the C‐Town, and that when one stopped to \n\n 8 use the payphone, the other two “started punching and kicking” him, \n\n 9 and that “one of the males then produced a knife and started stabbing \n\n10 the  victim  numerous  times  about  the  body  and  head.”    App’x  234.  \n\n11 Carter told the officer that the two men fled on foot. \n\n12 The  following  week,  on  April  15,  1994,  Detective  Gillen \n\n13 received a phone call from a woman who identified herself as Anna \n\n14 Simmons.    Simmons  reported  that  she  had  overheard  two \n\n15 individuals,  Levon  (“Ish”)  Martin  and  Rodney  (“Turk”)  Harris, \n\n16 discussing the Abbott murder.  Simmons said that she heard Ish and \n\n17 Turk bragging that they had killed Abbott following Abbott’s refusal \n\n18 to  join  their  gang,  the  Regulators.    The  following  day,  Detectives \n\n19 Solomeno  and  Gillen  re‐interviewed  Carter,  who  was  unable  to \n\n20 identify Ish and Turk from a photo array.  In the days that followed, \n\n21 Detectives  Solomeno  and  Gillen  tried  to  track  down  Simmons,  but \n\n22 never found her. \n\n 11  No. 17‐1859\n\n 1 On April 22, 1994, Linda Sanchez, a C‐Town cashier who was \n\n 2 working at the store on the morning of Abbott’s murder, called the \n\n 3 101st Precinct.2  Detectives Solomeno and Gillen then interviewed her \n\n 4 at her home.  Sanchez told the detectives that on the morning of the \n\n 5 murder,  Abbott,  whom  she  recognized,  entered  the  store,  collected \n\n 6 certain goods and got in a cashier’s line, and that two other men then \n\n 7 came into the store and ultimately got in line behind Abbott.  After \n\n 8 making his purchases, Abbott remained in the store to speak with the \n\n 9 store’s manager, “JJ,” while the two men behind Abbott in line had \n\n10 left the store and started walking through the parking lot “toward the \n\n11 chicken  store.”   App’x  237.    Sanchez  noted that  before  they  left  the \n\n12 parking  lot,  the  two  men  stopped  and  looked  back  at  the  C‐Town \n\n13 store.    Sanchez  herself  then  walked  to  the  parking  lot  to  collect \n\n14 shopping  carts  whereupon  she  saw  Abbott  walk  out  of  the  store \n\n15 through  the  parking  lot  and  also  in  the  direction  of  the  “[c]hicken \n\n16 store.”  App’x 237–238.  The detectives showed Sanchez a photo array \n\n17 that  included  Ish  and  Turk—the  two  men  identified  in  the  Anna \n\n\n\n  Sanchez’s telling of why she called the police on April 22, 1994 has not \n 2\n\n been  entirely  clear.    On  direct  examination  she  testified  (and  Defendants \n agree) that she called the police because Bellamy threatened her. Trial Tr. \n 706–08.  Sanchez, however, did not then mention those threats in her phone \n call  to  the  precinct  or  in  the  interview  that  followed,  and  on  cross‐\n examination,  she  at  times  suggested  that  her  call  was  prompted  by  an \n article  about  the  Abbott  murder  in  The  Wave  newspaper,  which  listed \n Detective Solomeno’s contact information.  See Trial Tr. 741–51. \n\n 12  No. 17‐1859\n\n 1 Simmons phone call—but she did not recognize them as the two men \n\n 2 she had seen in the store in line behind Abbott. \n\n 3 Three weeks later, on May 13, 1994, Sanchez again called the \n\n 4 precinct  to  report  that  a  man,  who  was  drinking  a  40‐ounce  beer \n\n 5 across the street from the C‐Town, was one of the two men that she \n\n 6 had previously reported were in the cashier’s line behind Abbott on \n\n 7 the morning of Abbott’s murder.  Shortly thereafter, Detective Gillen \n\n 8 arrived  on  the  scene  with  other  detectives,  and  they  saw  Bellamy \n\n 9 drinking  a  40‐ounce  beer  in  the  location  Sanchez  described.    The \n\n10 detectives detained Bellamy in a squad car and told him that he was \n\n11 being taken to the station to be fined in relation to his public drinking. \n\n12 As  we  will  discuss  later,  Detective  Gillen  said  at  trial  that  Bellamy \n\n13 made  spontaneous  and  unprompted  comments  in  the  police  car \n\n14 regarding a murder, but Bellamy denies that this occurred. \n\n15 At the police station, Detective Gillen showed Bellamy a photo \n\n16 of Abbott’s body and told him that there were witnesses identifying \n\n17 him as the assailant.  Bellamy denied any involvement in the murder \n\n18 and told Detective Gillen that he was with a friend named Terrill Lee \n\n19 on  the  day  of  the  murder.    Bellamy  was  placed  in  a  holding  cell \n\n20 overnight.   \n\n21 The following day, May 14, 1994, Detective Gillen orchestrated \n\n22 a  six‐person  lineup  at  the  precinct,  to  be  viewed  by  Sanchez  and \n\n23 Carter,  the  sole  eyewitnesses  known  to  the  detectives  at  that  time. \n\n 13  No. 17‐1859\n\n 1 Bellamy  was  in  position  one.    Sanchez  identified  the  individual  in \n\n 2 position one as one of the two men she saw leave the C‐Town prior to \n\n 3 Abbott on the day of Abbott’s killing.  As to be discussed, the parties \n\n 4 dispute certain aspects of what occurred during Carter’s viewing of \n\n 5 the lineup.  All agree, however, that Carter initially recognized one of \n\n 6 Abbott’s  assailants  in  either  position  one  or  two  but  that  he \n\n 7 subsequently  told  Detective  Gillen  in  a  separate  room  that  he  was \n\n 8 “99% sure” that the person he recognized was in position one, which \n\n 9 in fact was Bellamy.  App’x 295, 2415. \n\n10 Hours  later,  in  the  early  morning  of  May  15,  1994,  Detective \n\n11 Gillen  and  Assistant  District Attorney  (ADA) Stephen  Antignani  of \n\n12 the QCDA’s office took a sworn statement from Terrill Lee, the man \n\n13 Bellamy  claimed  he  was  with  on  the  day  of  Abbott’s  murder.    Lee \n\n14 stated  that  although  he  was  friends  with  Bellamy,  he  was  not  with \n\n15 him  at  all  on  April  9,  1994.    Thereupon,  that  same  day,  Detective \n\n16 Gillen filled out a criminal complaint charging Bellamy with Abbott’s \n\n17 murder. \n\n18 II. Criminal Proceedings Against Kareem Bellamy \n\n19 The grand jury indicted Bellamy on two counts of murder in \n\n20 the  second  degree  under  N.Y.  Penal  Law  §  125.25(1)  (intentional \n\n21 murder)  and  §  125.25(2)  (depraved  indifference  murder),  and  one \n\n22 count of criminal possession of a weapon in the fourth degree under \n\n23 N.Y. Penal Law § 265.01(2).  After unsuccessful suppression motions \n\n 14  No. 17‐1859\n\n 1 by  the  defense,  the  case  proceeded  to  trial  in  November  1995  with \n\n 2 ADA David Guy of the QCDA’s office as the prosecutor. \n\n 3 As  relevant  to  this  appeal,  the  state  called  the  following \n\n 4 witnesses:  (i) Detective  Gillen;  (ii)  Linda  Sanchez;  (iii)  Detective \n\n 5 Solomeno;  (iv)  Carter;  (v)  Deborah  Abbot,  the  victim’s  sister;  and \n\n 6 (vi) Veronica  Walker,  an eyewitness who  surfaced  for the  first time \n\n 7 during  the  trial.  We  summarize  the  relevant  portions  of  each  state \n\n 8 witness’s trial testimony and the summations.3 \n\n 9 Detective  Gillen.    Detective  Gillen’s  testimony  described  his \n\n10 investigation  of  the  Abbott  murder.    He  testified  about  his  initial \n\n11 discussion with Carter on the day of the murder, the Anna Simmons \n\n12 phone call the following week, and his role in the lineups.  Detective \n\n13 Gillen  also  testified  about  the  circumstances  of  picking  up  Bellamy \n\n14 following  Sanchez’s  call  to  the  precinct.    Detective  Gillen  testified \n\n15 with reference to an unsigned handwritten note that he wrote, that he \n\n16 said  was  his  contemporaneous  memorialization  of  Bellamy’s \n\n17 utterance in the squad car on the way to the police station: “This must \n\n18 be  a  case  of  mistaken  identity—someone  probably  accused  me  of \n\n19 murdering  someone.”    Trial  Tr.  494–95;  see  App’x  290.    Detective \n\n\n\n  Bellamy’s lone witness was Bellamy’s stepfather, with whom Bellamy \n 3\n\n lived on the day of the murder.  Bellamy’s stepfather testified that Bellamy \n did not leave the house on the day of the murder until 10:15–10:20 a.m.  Trial \n Tr. 1027–29. \n\n 15  No. 17‐1859\n\n 1 Gillen  then  testified  that  after  arriving  at  the  station  he  added  the \n\n 2 following notation on the same piece of paper: “Statement made by \n\n 3 [Bellamy]  while  being  asked  his  pedigree—spontaneous  & \n\n 4 unsolicited.”    Trial  Tr.  534–40;  App’x  1707.4    On  cross‐examination, \n\n 5 Detective  Gillen  acknowledged  that  he  did  not  incorporate  any  of \n\n 6 Bellamy’s statements in a “DD‐5,” known as a “complaint follow up” \n\n 7 form,  despite  having  prepared  eight  DD‐5s  throughout  the \n\n 8 investigation of the Abbott murder.  Trial Tr. 527–28, 532–34. \n\n 9 Linda Sanchez.5  ADA Guy began his questioning of Sanchez \n\n10 by  soliciting  her  biographical  information  and  then  asking  if  she \n\n11 “receive[d] any money from the office of the [QCDA] prior to coming \n\n12 into court today?”  Trial Tr. 633.  Sanchez acknowledged that she had \n\n13 received  $50  from  the  QCDA’s  office  and  anticipated  receiving \n\n14 another $50 from the office.  She testified that the money was for “food \n\n15 for the babies, Pampers,” and amounted to “$25 a day.”  Trial Tr. 634.  \n\n\n\n   Detective  Gillen  did  not  testify  at  trial  as  to  another  purported \n 4\n\n statement from Bellamy that he recorded on the same piece of paper:  “Why \n would  someone  accuse  me  of  something  I  didn’t  do?”    App’x  1707.  \n Nevertheless, the document in its entirety was entered into evidence at trial.  \n See Trial Tr. 538.  Detective Gillen acknowledged in a pre‐trial hearing that \n he recorded the first “murder” statement right away in the squad car and \n wrote the second “accuse” statement on the same piece of paper when he \n returned to the precinct.  App’x 2413. \n  It appears that the prosecution viewed Sanchez as a reluctant witness, \n 5\n\n in that she showed up to testify only after the prosecution served her with \n a material witness order on the first day of trial.  App’x 2044.  ADA Guy \n did not refer to Sanchez in his opening statement.   \n\n 16  No. 17‐1859\n\n 1 She further testified that she “came [to court] with the detective,” and \n\n 2 that  she  was  staying  overnight  at  a  “different  location”  than  her \n\n 3 residence,  and  that  “[t]he  detective”  “put  [her]  into  that  differen[t] \n\n 4 location.”  Trial Tr. 634–35. \n\n 5 Sanchez  then  testified  as  to  what  she  saw  on  the  morning  of \n\n 6 April  9,  1994.    She  identified  Bellamy  as  being  in  the  C‐Town  that \n\n 7 morning, wearing a green jacket and braids in his hair, with “a lot of \n\n 8 braids sticking up,” and that he and another taller person went to the \n\n 9 same line as Abbott.  Trial Tr. 639–41, 774.  Sanchez had seen Bellamy \n\n10 in the C‐Town many times before and noticed him that day because \n\n11 “[h]e was buying beer on a Sunday—on a Saturday that day.”  Trial \n\n12 Tr. 642.  Bellamy was in the store for about fifteen minutes and walked \n\n13 out before Abbott.  Sanchez noticed Bellamy turn to the right after he \n\n14 left the store, rather than to the left, the direction in which he usually \n\n15 departed from the store.  Sanchez then walked to the parking lot to \n\n16 retrieve shopping carts when she noticed Abbott catch up to Bellamy \n\n17 and the taller person and pass by them.  Sanchez testified that when \n\n18 NYPD  officers  came  to  the  C‐Town  later  that  morning,  she  did  not \n\n19 speak to them.   \n\n20 Finally,  Sanchez  testified  that Bellamy  threatened  her  on  two \n\n21 separate occasions after the Abbott murder.  A week after the murder, \n\n22 Bellamy entered the C‐Town and said to her: “You know, you know, \n\n23 you  fucking  bitch.  .  .  .  You’re  next.”    Trial  Tr.  706.    Then,  Sanchez \n\n 17  No. 17‐1859\n\n 1 testified  that  the  following  occurred  on  the  street  on  May  13,  1994 \n\n 2 before  she  called  the  police:  “He  was  pointing  at  me.    You  know \n\n 3 yelling, at like, yelling something at me.  Just pointing and pointing \n\n 4 at my direction.”  Trial Tr. 710.  Sanchez testified that she never told \n\n 5 the police about these threats, and that she had not told anyone about \n\n 6 them until one week before Bellamy’s trial (in November 1995).6 \n\n 7 Detective Solomeno.  Detective Solomeno testified that he was \n\n 8 initially  the  assigned  detective  on  the  investigation  of  the  Abbott \n\n 9 murder, and that he played a role in the Ish and Turk photo arrays \n\n10 shown to Sanchez and Carter and that he conducted the April 22, 1994 \n\n11 interview of Sanchez.  Detective Solomeno also testified that, in the \n\n12 days prior to his trial testimony, he had spoken to Deborah Abbott, \n\n13 the victim’s sister, who had given him the contact information for a \n\n14 woman named Veronica Walker.  Detective Solomeno testified that \n\n15 he spoke with Walker shortly before trial on December 1, 1995 and \n\n16 that he prepared a DD‐5 in connection with that interview.  \n\n17 Andrew  Carter.    Carter  testified  as  to  what  he  saw  on  the \n\n18 morning of the murder and what happened at the Bellamy lineup.  On \n\n19 April 9, 1994, as he was waiting for the bus, he saw three people walk \n\n20 out of the C‐Town store, one by himself and the other two together.  \n\n\n\n  However, Sanchez later testified that she mentioned the threats to an \n 6\n\n ADA immediately prior to testifying in front of the grand jury.  Trial Tr. \n 758–59. \n\n 18  No. 17‐1859\n\n 1 The  three  men  came  “right  past”  him,  and  then  Carter  looked  in \n\n 2 another direction.  Trial Tr. 868.  When Carter turned back towards \n\n 3 the direction of the three men, “the other two guys were beating the \n\n 4 hell out of [Abbott].”  Trial Tr. 869.  Carter then testified that one of \n\n 5 the two men pulled out a “brass knuckle knife” and stabbed Abbott.  \n\n 6 Trial Tr. 872.  Carter pointed to Bellamy from the witness stand and \n\n 7 testified that the individual who stabbed Abbott was “the gentlemen \n\n 8 right  there.”    Trial  Tr.  870–71.    Carter  had  never  seen  any  of  the \n\n 9 individuals before, but he got a good look at their faces.  Trial Tr. 872–\n\n10 73.  Carter had “[n]o doubt” that Bellamy was the person he saw stab \n\n11 Abbott that morning.  Trial Tr. 872. \n\n12 Carter  then  testified  at  length  about  viewing  the  lineup  in \n\n13 which Bellamy was in position one.  He testified that he initially told \n\n14 the detective that “it was either one or two, because they got their hair \n\n15 different.”    Trial  Tr.  880.    Specifically,  Carter  testified  that  the \n\n16 individual he saw stab Abbott did not have braids in his hair, but that \n\n17 the person in position one at the lineup did have braids.  Carter then \n\n18 had  a  conversation  in  another  room  with  an  ADA  and  a  detective \n\n19 where Carter “said [it was] two.”  Trial Tr. 883.  Carter testified several \n\n20 times at trial that the individual he saw stab Abbott was in position \n\n21 number  two  in  the  lineup.    Trial  Tr.  895–96,  903–04.    Nevertheless, \n\n22 Carter  testified  that  he  told  the  detectives  at  the  time  that  it  was \n\n23 “either one or two,” but also that he was 99% sure the assailant was \n\n 19  No. 17‐1859\n\n 1 in position number one.  Trial Tr.  882, 896, 903.  ADA Guy tried to \n\n 2 sum  up  (but  not  resolve)  the  confusion  on  redirect,  asking  Carter: \n\n 3 “You told us today it was number two, but you told the detective it \n\n 4 was number one that day?”  Trial Tr. 904.  Carter responded, “Yes.”  \n\n 5 Trial Tr. 904. \n\n 6 Deborah Abbott.  Deborah Abbott, the victim’s sister, testified \n\n 7 about a conversation she had with Veronica Walker in July of 1995, \n\n 8 fifteen months after the killing of her brother but four months prior \n\n 9 to  the  trial.    Following  that  conversation,  she  called  the  police  and \n\n10 spoke  with  prosecutor  ADA  Guy.    The  next  time  Deborah  Abbott \n\n11 spoke to ADA Guy was one week before the trial, where she for the \n\n12 first time gave identifying information for Walker.   \n\n13 Veronica Walker.  Walker testified as to what she saw on the \n\n14 morning of April 9, 1994.  Walker stopped into the C‐Town prior to a \n\n15 10:00 a.m. hair appointment, and briefly spoke with Abbott who she \n\n16 recognized from her neighborhood.  She left the store after about 5–6 \n\n17 minutes, got in her car, and began to drive away.  She stopped at the \n\n18 adjacent  intersection  and  saw  through  her  car’s  passenger  side \n\n19 window that Abbott was fighting with a lone man near a phone booth \n\n20 directly  to  her  right.    Walker  then  made  a  righthand  turn  when  a \n\n21 skinny 5’6” man with braided hair “came from across the left‐hand \n\n22 side of the street from the back of [her] car, running across the street,” \n\n23 and  joined  in  the  fight  between  Abbott  and  the  unidentified  man.  \n\n 20  No. 17‐1859\n\n 1 Trial  Tr.  1001–03.    Walker,  who  knew  Bellamy  personally,  testified \n\n 2 that she did not recognize the man who ran behind her car to join the \n\n 3 fight,  had  never  seen  him  before,  and  did  not  see  him  in  the \n\n 4 courtroom.   \n\n 5 In an apparent attempt to impeach Walker’s non‐identification \n\n 6 of Bellamy, ADA Guy then asked Walker about her interview with \n\n 7 Detectives Solomeno and Gillen the previous week: \n\n 8 Q:  Well,  didn’t  you  tell  Detective  Solomeno \n 9 and  Detective  Gillen  that  you  recognized \n10 that person [who you saw run by the car] as \n11 Kareem [Bellamy]? \n12 A:    No. \n13 Q:  What—Well,  did  you  tell  Detective \n14 Solomeno  that  the  person  looked  like \n15 Kareem? \n16 A:    I said it could have been him.  It could have. \n\n17 Trial Tr. 1005.  The defense asked Walker almost no questions. \n18 Defense Summation.7  In summation, the defense argued that \n\n19 the state had not shown that Bellamy committed the Abbott murder \n\n20 beyond  a reasonable  doubt.    It  argued  that  the  case  was  a “rush  to \n\n21 judgment,” and that “the district attorney was anxious to close this \n\n22 case and so they closed it.”  Trial Tr. 1099.  The defense principally \n\n23 attacked the three eyewitnesses.  It argued that Sanchez’s story lacked \n\n\n\n  Under New York law, the defense delivers its summation first and has \n 7\n\n no right of rebuttal.  See N.Y. Crim. Proc. Law § 260.30. \n\n 21  No. 17‐1859\n\n 1 common sense and that she had a motive to lie given her receipt of \n\n 2 $25 per day by the QCDA’s office.  The defense focused on Carter’s \n\n 3 trial testimony to the effect that the assailant was in position two at \n\n 4 the  lineup,  not  position  one,  and  downplayed  Carter’s  in‐court \n\n 5 identification by arguing that Carter simply pointed to the only “black \n\n 6 man” at the defense counsel’s table.  Trial Tr. 1099.  Counsel reminded \n\n 7 the jury that Walker did not identify Bellamy as the person she saw \n\n 8 run by her car, and rather acknowledged only that it could have been \n\n 9 him.    The  defense  also  focused  on  the  differing  accounts  from  the \n\n10 witnesses as to whether the assailant did or did not have braided hair.  \n\n11 Trial  Tr.  1093;  compare  Trial  Tr.  774  &  1003  (Sanchez  and  Walker’s \n\n12 testimony  that  the  assailant  had  braids)  with  Trial  Tr.  896  (Carter’s \n\n13 testimony that the assailant did not have braids).8   The defense then \n\n14 argued  that  Bellamy  never  made  the  spontaneous  “murder” \n\n15 statement  in  the  squad  car,  and  that  even  if  he  did,  it  was  not \n\n16 inculpatory.  Finally, the defense counsel reminded the jury that the \n\n17 state had never attempted to establish any motive for the killing. \n\n18 State’s Summation.  ADA Guy delivered a lengthy summation, \n\n19 acknowledging, at the outset, that the evidence in the case was messy \n\n20 and was not presented in a “tidy little package” for the jury.  Trial Tr. \n\n\n  The trial testimony Carter gave as to Bellamy’s hair contradicted his \n 8\n\n testimony at the grand jury, where he testified that on the day of the lineup \n the assailant “had his hair cut,” but that on the day of the Abbott murder \n he had “[k]inky, short braids.”  App’x 334. \n\n 22  No. 17‐1859\n\n 1 1113.  But, he argued, the jury’s “task becomes relatively easy” when \n\n 2 it applies common sense and focuses principally on the testimony of \n\n 3 the three eyewitnesses.  Trial Tr. 1115.   \n\n 4 ADA Guy acknowledged that Sanchez “may not be the most \n\n 5 articulate  person,”  and  that  she  “got  a  little  confused  from  time  to \n\n 6 time”  and  “didn’t  testify  all  that  well,”  in  that  she  made  certain \n\n 7 mistakes and contradictions, but that her story was credible, she had \n\n 8 no reason to lie, and there was no “evidence that she is a liar.”  Trial \n\n 9 Tr.  1121,  1138–40,  1144.    ADA  Guy  also  acknowledged  certain \n\n10 contradictions in Carter’s testimony and argued that Carter “made a \n\n11 mistake” when he said that the assailant was in position two at the \n\n12 lineup.  Trial Tr. 1134–36.  But, ADA Guy argued, “[y]ou don’t have \n\n13 to  take  my  word.    Common  sense  will  tell  you  it’s  the  defendant, \n\n14 number  one,  who  is  on  trial,  not  some  filler  in  a  lineup.”    Trial  Tr. \n\n15 1137.    ADA  Guy  also  acknowledged  Walker’s  non‐identification  of \n\n16 Bellamy in court but argued that the jury should instead focus on the \n\n17 physical description that she provided of the individual she saw on \n\n18 the  morning  of  the  Abbott  murder,  which  is  consistent  both  with \n\n19 Bellamy’s actual description and the other eyewitnesses’ description \n\n20 of the assailant.   \n\n21 ADA Guy then addressed the defense’s remaining contentions.  \n\n22 He answered the defense’s contention that the state offered no motive \n\n23 for Bellamy’s alleged killing of Abbott by arguing that there was no \n\n 23  No. 17‐1859\n\n 1 proof, either way, of motive in this case, “submit[ting that] there is no \n\n 2 proof that he had no motive.”  Trial Tr. 1133 (emphasis added).  ADA \n\n 3 Guy also reminded the jury of Detective Gillen’s testimony regarding \n\n 4 Bellamy’s “premature denial” in the squad car, arguing that it was in \n\n 5 character with Bellamy’s inability to “keep his mouth shut,” a mouth \n\n 6 that  ADA  Guy  argued  was  “huge”  and  “cavernous,”  as  well  as \n\n 7 Bellamy’s status as a “liar.”  Trial Tr. 1145–48.  \n\n 8 ADA Guy concluded by again imploring the jurors to use their \n\n 9 common sense.  As reflected in the trial transcript, ADA Guy told the \n\n10 jury:  “I  know  who  committed  the  murder.    You  know  it  was  an \n\n11 intentional murder and you know there is no rational explanation for \n\n12 why so many people are pointing their fingers at [Bellamy].”  Trial Tr. \n\n13 1149.9    ADA  Guy  concluded  in  substance:    “When  the  defendant \n\n14 asked  why  would  someone  be  accusing  me  of  murder,  by  your \n\n15 verdict you can answer his question.  Because you are the murderer.  \n\n16 It’s because the evidence shows that you are the murderer, and that \n\n17 you are not going to get away with it, not this time.”  Trial Tr. 1150.  \n\n18 *  *  * \n\n19 After  three  days  of  deliberations,  during  which  the  jury \n\n20 submitted eighteen notes to the judge, sought lengthy readbacks of \n\n\n   As  to  be  discussed,  the  Defendants  contend  that  the  trial  transcript \n 9\n\n contains a transcription error, and that ADA Guy stated, “You know who \n committed the murder.” \n\n 24  No. 17‐1859\n\n 1 testimony,  and  was  given  an  Allen  charge,10  the  jury  acquitted \n\n 2 Bellamy  of  intentional  murder  but  convicted  him  of  depraved \n\n 3 indifference  murder  and  a  weapons  charge.    The  court  sentenced \n\n 4 Bellamy  to  25‐years‐to‐life.    Bellamy  appealed  the  convictions, \n\n 5 arguing  (i) insufficiency  of  the  evidence;  (ii)  that  Detective  Gillen \n\n 6 provided false testimony; and (iii) that Bellamy’s statements to Gillen \n\n 7 and the lineup identifications should have been suppressed.  The state \n\n 8 appellate court affirmed, 247 A.D.2d 399, and leave to appeal to the \n\n 9 Court of Appeals was denied, 91 N.Y.2d 970.  Bellamy’s federal habeas \n\n10 corpus petition, which depended entirely on his assertion that Gillen \n\n11 falsely testified as to Bellamy’s statements in the squad car following \n\n12 his pickup, was denied and not appealed.   \n\n13 III. Bellamy’s State Post‐Conviction Proceedings \n\n14 In  2007,  more  than  a  decade  after  his  conviction,  Bellamy \n\n15 moved  to  vacate  the  judgment  against  him  pursuant  to  N.Y.  Crim. \n\n16 Proc.  Law  §  440.10(f),  (g)  and  (h).    See  People  v.  Bellamy,  2008  WL \n\n17 3271995, at *2–3 (Sup. Ct. Queens Cnty. June 27, 2008).  The central \n\n\n\n   “The  term  ‘Allen  charge’  is  a  generic  term  used  for  a  type  of \n 10\n\n supplemental instruction that is given to a deadlocked jury, first approved \n by  the  Supreme  Court  in  Allen  v.  United  States,  164  U.S.  492  (1896).    ‘A \n traditional  Allen  charge  reminds  the  jurors  about  the  importance  of \n obtaining  a  verdict  and  encourages  jurors  to  listen  ‘to  each  other’s \n arguments’ while also emphasizing that ‘the verdict must be the verdict of \n each individual juror, and not a mere acquiescence in the conclusion of his \n fellows.’ Id. at 501.”  Smalls v. Batista, 191 F.3d 272, 275 n.1 (2d Cir. 1999).  \n\n 25  No. 17‐1859\n\n 1 basis for the sought‐after relief was § 440.10(g), which under certain \n\n 2 circumstances  allows  for  the  vacatur  of  a  guilty  verdict  upon  the \n\n 3 discovery of new evidence.  The principal new evidence relied on by \n\n 4 Bellamy  was  that:  (i)  another  individual,  Ish,  had  confessed  to  the \n\n 5 Abbott murder to a police informant named Michael Green, and that \n\n 6 Green had Ish on tape discussing the crime; and (ii) Carter recanted \n\n 7 his  trial  testimony  that  identified  Bellamy  as  the  assailant  and  was \n\n 8 now  asserting  that  he  falsely  inculpated  Bellamy  at  trial  under \n\n 9 pressure by Detective Gillen. \n\n10 The  state  post‐conviction  court  conducted  a  lengthy  hearing, \n\n11 which included taking the testimony of several of the trial witnesses, \n\n12 including  Carter,11  Walker,  Sanchez,  and  Detectives  Solomeno  and \n\n13 Gillen, as well as the testimony of Green and ADA Antignani.  As will \n\n14 be  discussed,  some  of  the  testimony  at  this  hearing  added  further \n\n15 color  to  the  events  surrounding  Abbott’s  murder,  while  other \n\n16 testimony conflicted with that given at trial.  Following the hearing, \n\n17 the court granted Bellamy’s motion and vacated his conviction based \n\n18 solely  on  the  newly  discovered  evidence  proffered  by  Green  that \n\n\n\n\n   On  June  11,  2008,  following  his  testimony  at  the  initial  hearing  on \n 11\n\n Bellamy’s § 440 motion (but prior to the second such hearing), Carter passed \n away.   \n\n 26  No. 17‐1859\n\n 1 inculpated Ish in Abbott’s murder.12  See id. at *11–12 (finding Carter’s \n\n 2 recantation not credible). \n\n 3 After  filing  an  appeal  of  that  judgment,  however,  the  state \n\n 4 moved  for  reargument  before  the  hearing  court,  arguing  that  the \n\n 5 evidence  from  Green  that  the  court  relied  on  to  vacate  Bellamy’s \n\n 6 conviction  was  perjurious  and  fraudulent.    The  state  submitted  an \n\n 7 affidavit  from  Green  in  which  he  now  admitted  that  the  tape  he \n\n 8 offered  at  the  §  440  hearing  purportedly  capturing  a  conversation \n\n 9 between Green and Ish was in fact a recording between Green and an \n\n10 acquaintance  pretending  to  be  Ish.    See  People  v.  Bellamy,  2010  WL \n\n11 143462, at *1 (Sup. Ct. Queens Cnty. Jan. 14, 2010).  The hearing court \n\n12 reopened  the  proceeding  and  again  took  significant  witness \n\n13 testimony, including that of Green, who testified consistent with his \n\n14 affidavit  that  he  created  the  false  tape,  that  he  lied  at  the  earlier \n\n15 hearing,  and  that  Ish  never  told  him  that  he  was  involved  in  the \n\n16 Abbott murder.   \n\n17 Despite  finding  that  Green  had  falsely  testified  about  a \n\n18 fabricated  tape,  the  court  adhered  to  its  earlier  ruling  ordering  the \n\n19 vacatur of Bellamy’s judgment of conviction.  The court found parts \n\n20 of  Green’s  testimony  inculpating  Ish  at  the  initial  hearing  credible \n\n21 despite  the  fake  tape  and  Green’s  subsequent  recantation.    Bellamy, \n\n\n  The motion court referred to Green in this initial ruling on Bellamy’s \n 12\n\n § 440 motion as “John Doe/CI.”  See Bellamy, 2008 WL 3271995, at *8–9. \n\n 27  No. 17‐1859\n\n 1 2010  WL 143462,  at  *6.    The  Second  Department  affirmed,  agreeing \n\n 2 that  a  “reasonable  jury  could  find  .  .  .  that  [Green’s]  original \n\n 3 unsolicited implication of [Ish] was truthful, regardless of [Green’s] \n\n 4 later recantation of those statements.”  84 A.D.3d 1260, 1262 (2d Dep’t \n\n 5 2011).  Leave to appeal to the Court of Appeals was denied, 17 N.Y.3d \n\n 6 813, Bellamy was released from prison, and the state dismissed the \n\n 7 indictment.13 \n\n 8 IV. The Instant Civil Action \n\n 9   In March 2012, Bellamy filed the instant action in the Eastern \n\n10 District  of  New  York  against  the  City  of  New  York,  Detectives \n\n11 Solomeno and Gillen, and two John Doe defendants. 14  At the core of \n\n\n\n  In a series of rulings after Bellamy’s conviction, the New York Court \n 13\n\n of  Appeals  significantly  limited  the  reach  of  New  York’s  criminal \n prohibition against depraved indifference murder, the only murder charge \n on  which  Bellamy  was  convicted.    See  People  v.  Payne,  3  N.Y.3d  266,  270 \n (N.Y.  2004).    In  short,  the  Court  of  Appeals  concluded  that  where  an  act \n evinces  an  intent  to  kill,  that  act  cannot  support  a  depraved  indifference \n charge, which is not a lesser included offense of intentional murder.  Id.  The \n state  therefore  conceded  that  it  could  not  “in  good  faith,  proceed  with  a \n subsequent  prosecution  [of  Bellamy]  for  depraved  indifference  murder \n because we are legally prohibited from doing so. . . . [We] have no other \n choice but to move to dismiss this indictment against this defendant . . . not \n because he has been exonerated or because we believe him to be actually \n innocent  but because a continued prosecution  is not  legally  sustainable.”  \n App’x 698. \n  On October 31, 2014, Bellamy filed an amended complaint replacing \n 14\n\n the  two  John  Does  with  named  defendants,  Dkt.  No.  82,  but  Bellamy \n withdrew that pleading and the parties stipulated that the original March \n 2012 complaint would be the operative complaint, Dkt. No. 110. \n\n 28  No. 17‐1859\n\n 1 Bellamy’s complaint were allegations that the Defendants engaged in \n\n 2 material misconduct during the investigation and trial that deprived \n\n 3 him  of  his  rights  to  due  process  under  the  Fourteenth  Amendment \n\n 4 and to a fair trial under the Sixth Amendment.  In short, Bellamy’s \n\n 5 claims at issue here fall into three general categories:  (i) claims that \n\n 6 Detectives  Solomeno  and  Gillen  fabricated  material  evidence; \n\n 7 (ii) claims  that  Detectives  Solomeno  and  Gillen  withheld  material \n\n 8 evidence; and (iii) Monell claims against the City of New York based \n\n 9 upon allegations that, pursuant to a policy, the QCDA withheld the \n\n10 full scope of relocation benefits it provided to Sanchez and that, due \n\n11 to a systemic failure to train or discipline, ADA Guy’s summation was \n\n12 improper.15  Specifically, as relevant on appeal, Bellamy’s complaint \n\n13 alleges that: \n\n\n  After the district court’s denial of the Defendants’ motion to dismiss, \n 15\n\n and Bellamy’s withdrawal of his claims against the John Doe defendants, \n Dkt. 24, 110, one of his Monell claims, see Dkt. 112, 158 at 21 n.5, and a claim \n for negligent infliction of emotional distress, Dkt. 24, the following claims \n remained at issue:  \n (i) Section  1983  claims  against  Detectives  Solomeno  and  Gillen \n alleging  a  denial  of  due  process,  the  right  to  a  fair  trial,  and \n conscience shocking government action.  \n (ii) Section  1983  and  state  law  claims  against  Detectives  Solomeno \n and Gillen alleging malicious prosecution.  \n (iii) Section 1983 Monell claims against the City of New York. \n (iv) State  law  intentional  infliction  of  emotional  distress  claims \n against Detectives Solomeno and Gillen. \n (v) A state law respondeat superior claim against the City of New York.   \n\n 29  No. 17‐1859\n\n 1 (i) Detective  Gillen  fabricated  evidence  that  Bellamy \n 2 referenced a murder in the squad car that escorted him to \n 3 the police station on May 13, 1994 and falsely testified as to \n 4 such at Bellamy’s criminal trial; \n 5 (ii) Detective Solomeno fabricated evidence in the form of the \n 6 contents of a DD‐5 that reported that during her December \n 7 1,  2005  interview  Walker  identified  Bellamy  as  the \n 8 individual she saw on the morning of the Abbott murder; \n 9 (iii) Detective  Gillen  improperly  pressured  Carter  to  identify \n10 Bellamy  in  the  lineup  conducted  on  May  14,  1994,  even \n11 though Carter was unsure if Bellamy was the person he saw \n12 stab Abbott; \n13 (iv) Detective  Gillen  and/or  Solomeno  failed  to  disclose \n14 statements  Sanchez  made  during  the  investigation \n15 indicating that the morning she saw Bellamy was a Sunday, \n16 rather than a Saturday, the day on which Abbott was killed; \n17 (v) Detective  Gillen  failed  to  disclose  Sanchez’s  statement \n18 during  the  investigation  that  the  person  she  saw  with \n19 Bellamy on the morning of the Abbott murder was Terrill \n20 Lee; \n21 (vi) Detective  Gillen  failed  to  disclose  Sanchez’s  statements  to \n22 police officers on April 9, 1994, the day of Abbott’s murder, \n23 that she “didn’t see anything” and “didn’t know anything”; \n24 (vii) Detectives Solomeno and Gillen failed to disclose Walker’s \n25 statements  during  her  December  1,  2005  interview  that \n26 Bellamy was not the person she saw on the morning of the \n27 Abbott murder and that Walker refused to sign the DD‐5 to \n28 the effect that she had seen Bellamy; \n29 (viii) the  prosecution  failed  to  disclose  to  the  defense  the  full \n30 relocation  benefits  received  by  Sanchez  as  part  of  her \n31 participation  in  the  QCDA’s  witness  protection  program; \n32 and \n33 (ix) ADA Guy committed prejudicial summation misconduct. \n\n 30  No. 17‐1859\n\n 1 The  district  court  stayed  discovery  on  the  core  of  Bellamy’s \n\n 2 Monell claims (viii and ix above) but allowed discovery to proceed in \n\n 3 full on the claims against Detectives Solomeno and Gillen.  See Dkt. \n\n 4 No. 52. The parties took substantial deposition testimony, including \n\n 5 from  the  following  witnesses:  (i)  Bellamy;  (ii)  Detective  Gillen;  (iii) \n\n 6 Detective Solomeno; (iv) ADA Antignani; (v) ADA Guy; (vi) Michael \n\n 7 Mansfield, the Director of the QCDA’s witness protection program; \n\n 8 (vii) Daniel Cox, the administrator of the QCDA’s witness protection \n\n 9 program responsible for Sanchez’s participation; (viii) Sanchez; and \n\n10 (ix)  Walker.    We  refer  to  the  deposition  testimony  in  detail  in  our \n\n11 forthcoming  analysis  of  Bellamy’s  claims,  but  simply  preview  here \n\n12 that  the  deposition  testimony,  like  the  testimony  at  the  §  440 \n\n13 proceeding, provides further, albeit at times conflicting, accounts of \n\n14 the  circumstances  surrounding  Abbott’s  murder  and  the  resulting \n\n15 investigation. \n\n16   At  the  close  of  discovery  on  the  claims  against  Detectives \n\n17 Solomeno  and  Gillen,  both  parties  cross‐moved  for  summary \n\n18 judgment.  In an 80‐page ruling, the district court granted summary \n\n19 judgment  to  Defendants  dismissing  Bellamy’s  claims  against \n\n20 Detectives Solomeno and Gillen and dismissing the Monell claims on \n\n21 the pleadings.  Bellamy v. City of New York, 2017 WL 2189528 (E.D.N.Y. \n\n22 May 17, 2017).  First, the district court dismissed Bellamy’s malicious \n\n23 prosecution claims against the detectives on the ground that Bellamy \n\n 31  No. 17‐1859\n\n 1 failed to raise a triable issue of fact as to whether he was prosecuted \n\n 2 without probable cause.16  Id. at *29–34.  Second, it dismissed the core \n\n 3 of  Bellamy’s  due  process  and  fair  trial  claims  against  Detectives \n\n 4 Solomeno  and  Gillen  upon  concluding  that  Bellamy  raised  no \n\n 5 material  issue  of  fact  as  to  whether  either  detective  fabricated  or \n\n 6 withheld  material  evidence.    Id.  at  *34–36.    Third,  it  dismissed \n\n 7 Bellamy’s  “shocks  the  conscience”  due  process  claims  against  the \n\n 8 detectives as duplicative of Bellamy’s malicious prosecution claims.  \n\n 9 Id.  at  *36.    Fourth,  it  dismissed  Bellamy’s  intentional  infliction  of \n\n10 emotional  distress  claims  against  the  detectives  on  the  ground  that \n\n11 Bellamy raised no triable issue as to whether the detectives conduct \n\n12 was “extreme and outrageous,” and that, regardless, the claims were \n\n13 also duplicative of Bellamy’s malicious prosecution claim.  Id. at *37.  \n\n14 Finally, the district court dismissed Bellamy’s Monell claims against \n\n15 the City on the pleadings for two reasons: (i) in light of Van de Kamp \n\n16 v.  Goldstein,  555  U.S.  335  (2009),  the  City  of  New  York  cannot  as  a \n\n17 matter of law be liable for the alleged policies of the QCDA’s office; \n\n18 and  (ii)  regardless,  Bellamy  did  not  sufficiently  establish  the \n\n19 underlying constitutional due process violations he alleged:  the non‐\n\n\n\n\n  Later in its opinion, the district court also concluded that Detectives \n 16\n\n Solomeno  and  Gillen  would  have  been  protected  by  qualified  immunity \n from Bellamy’s malicious prosecution claims regardless.  Id. at *37. \n\n 32  No. 17‐1859\n\n 1 disclosure  of  Sanchez’s  relocation  benefits  and  ADA  Guy’s \n\n 2 summation misconduct.17  Id. at *37–41. \n\n 3   Bellamy’s  appeal  challenges  only  the  dismissal  of  his  due \n\n 4 process and fair trial claims against Detectives Solomeno and Gillen \n\n 5 and  his  Monell  claims  against  the  City  of  New  York.    His  baseline \n\n 6 position is that (i) as to the claims against Detectives Solomeno and \n\n 7 Gillen,  the  evidence  as  a  whole  (from  the  trial,  the  post‐conviction \n\n 8 hearing,  and  the  depositions  in  the  instant  civil  case),  presents \n\n 9 disputed issues of material fact that necessitate a trial, and (ii) with \n\n10 respect to the Monell claims, the district court committed legal error \n\n11 and  that  material  fact  issues  remain  as  to  the  underlying  conduct \n\n12 alleged. \n\n13 DISCUSSION \n\n14 We review de novo both a grant of a summary judgment and the \n\n15 grant  of  judgment  on  the  pleadings.    Bank  of  New  York  v.  First \n\n16 Millennium, Inc., 607 F.3d 905, 914, 922 (2d Cir. 2010). \n\n17 Summary judgment may be granted only “if the movant shows \n\n18 that there is no genuine dispute as to any material fact and that the \n\n\n\n\n  It does not appear that the Defendants moved for summary judgment \n 17\n\n on Bellamy’s Count XII against the City of New York for respondeat superior, \n and  the  district  court  did  not  address  the  claim.    Regardless,  Bellamy’s \n respondeat  superior  claim  depended  on  his  establishing  his  state  law  tort \n claims, see Dkt. 1 ¶¶ 472–73, which the district court dismissed.  Bellamy \n does not appeal the dismissal of those claims, so this issue is not relevant. \n\n 33  No. 17‐1859\n\n 1 movant is entitled to judgment as a matter of law.”  Fed. R. Civ. P. \n\n 2 56(a).  We may affirm the grant of summary judgment only when, in \n\n 3 “resolv[ing]  all  ambiguities  and  draw[ing]  all  permissible  factual \n\n 4 inferences in favor of the [non‐moving] party. . . the record taken as a \n\n 5 whole could not lead a rational trier of fact to find for the non‐moving \n\n 6 party.”  Estate of Gustafson v. Target Corp., 819 F.3d 673, 675 (2d Cir. \n\n 7 2016) (internal quotation marks omitted).  Thus, in the present context \n\n 8 and of significance here, where the summary judgment non‐movant \n\n 9 is a former criminal defendant bringing § 1983 claims related to his \n\n10 underlying criminal trial, the summary judgment standard, generally \n\n11 speaking, is the converse of the standard applicable direct appeal of a \n\n12 criminal  defendant’s  conviction,  which  requires  us  to  “view  the \n\n13 evidence in a light that is most favorable to the government, and with \n\n14 all reasonable inferences resolved in favor of the government.” United \n\n15 States  v.  Anderson,  747  F.3d  51,  60  (2d  Cir.  2014)  (internal  quotation \n\n16 marks omitted). \n\n17 A court may grant judgment on the pleadings only when, after \n\n18 “accept[ing]  all  factual  allegations  in  the  complaint  as  true  and \n\n19 draw[ing] all reasonable inferences in favor of the [plaintiff] . . . the \n\n20 complaint  [does  not]  contain  sufficient  factual  matter  .  .  .  to  state  a \n\n21 claim to relief that is plausible on its face.”  Bank of New York, 607 F.3d \n\n22 at 922. \n\n 34  No. 17‐1859\n\n 1 These  principles  lead  us  to  conclude,  contrary  to  the  district \n\n 2 court, that Bellamy has succeeded in raising material issues of fact as \n\n 3 to a number of the claims subject to this appeal.  This requires us to \n\n 4 vacate in large part the dismissal of Bellamy’s due process and fair \n\n 5 trial claims against Detectives Solomeno and Gillen and to vacate in \n\n 6 full the dismissal of Bellamy’s Monell claims.18 \n\n 7 I. Claims Against Detectives Solomeno and Gillen \n\n 8 As  we  have  previously  discussed,  Bellamy’s  claims  against \n\n 9 Detectives  Solomeno  and  Gillen  fall  into  two  general  categories: \n\n10 (i) claims  that  the  detectives  fabricated  material  evidence;  and \n\n11 (ii) claims that the detectives withheld material evidence. \n\n12 a. Evidence Fabrication Claims \n\n13 “When  a  police  officer  creates  false  information  likely  to \n\n14 influence  a  jury’s  decision  and  forwards  that  information  to \n\n15 prosecutors,  he  violates  the  accused’s  constitutional  right  to  a  fair \n\n16 trial.”  Ricciuti v. N.Y.C. Transit Auth., 124 F.3d 123, 130 (2d Cir. 1997). \n\n17 Bellamy  contends  that  Detective  Gillen  and/or  Solomeno  fabricated \n\n18 three pieces of material evidence: (i) Bellamy’s “murder” statement in \n\n19 the  squad  car;  (ii) Walker’s  statement  implicating  Bellamy  as \n\n20 recorded in a DD‐5 drafted by Detective Solomeno; and (iii) Carter’s \n\n\n  The dissent posits views of the evidence that, if accepted by a trial jury, \n 18\n\n would  likely  result  in  a  defendants’  verdict.  But  it  does  so  by  drawing \n inferences against the plaintiffs and thus does not gainsay the existence of \n disputed issues of material fact that require a trial determination.  \n\n 35  No. 17‐1859\n\n 1 lineup identification of Bellamy.  We conclude that Bellamy has raised \n\n 2 material issues of fact precluding summary judgment as to the first \n\n 3 two contentions, but not the third. \n\n 4 i. Bellamy’s “Murder” Statement in the Squad Car \n\n 5 The prosecution relied at trial on Detective Gillen’s testimony \n\n 6 regarding  an  undated  and  unsigned  note  that  Detective  Gillen \n\n 7 contended that he wrote while in the squad car shortly after he picked \n\n 8 up Bellamy.  The note purportedly captured the following utterance \n\n 9 from Bellamy: “This must be a case of mistaken identity—someone \n\n10 probably accused me of murdering someone.”  App’x 290.  The note \n\n11 also supposedly transcribed the following squad car statement from \n\n12 Bellamy,  which  Detective  Gillen  only  added  to  the  note  after \n\n13 returning  to  the  precinct:    “Why  would  someone  accuse  me  of \n\n14 something  I  didn’t  do?”    App’x  290,  2413.    Sometime  thereafter, \n\n15 Detective  Gillen  again  added  to  the  note  the  following:  “Statement \n\n16 made  by  def  while  being  asked  his  pedigree—spontaneous  & \n\n17 unsolicited.”    App’x  1707.    The  prosecution  relied  heavily  on  this \n\n18 evidence at trial.  Detective Gillen, the state’s first witness, testified at \n\n19 length regarding Bellamy’s purported murder statement in the squad \n\n20 car, which Gillen allegedly memorialized in a handwritten note in his \n\n21 police  spiral  notebook.  Trial  Tr.  494–96,  529.  ADA  Guy  relied  on \n\n22 Bellamy’s purported murder statement in summation, Trial Tr. 1124.  \n\n23 The prosecution’s reliance on this statement is unsurprising because, \n\n 36  No. 17‐1859\n\n 1 if  Bellamy  made  it,  it  is  highly  inculpatory.    No  one  mentioned \n\n 2 Abbott’s  murder  to  Bellamy  when  he  was  picked  up,  and  from \n\n 3 Bellamy’s  perspective,  all  indications  were  that  the  detectives  were \n\n 4 detaining Bellamy solely for consuming alcohol in public.  \n\n 5 Bellamy  has  consistently  denied  making  the  “murder” \n\n 6 statement, including in his deposition in this case, and asserts as part \n\n 7 of  his  fair  trial  claim  that  it  was  wholly  fabricated  by  Detective \n\n 8 Gillen.19    In  a  brief  analysis,  the  district  court  rejected  the  claim, \n\n 9 relying on Jeffreys v. City of New York, 426 F.3d 549 (2d Cir. 2005), for \n\n10 the  proposition  that  self‐serving  deposition  testimony  that  is \n\n11 “unsubstantiated by any other direct evidence” cannot raise an issue \n\n12 of material fact.  2017 WL 2189528, at *31. \n\n13 We  conclude,  contrary  to  the  district  court,  that  Bellamy  has \n\n14 raised a material issue of fact as to whether Detective Gillen fabricated \n\n15 the note purportedly memorializing Bellamy’s “murder” statement in \n\n16 the  squad  car.    Contrary  to  the  district  court’s  analysis,  a  §  1983 \n\n17 plaintiff’s testimony alone may be independently sufficient to raise a \n\n18 genuine issue of material fact.  See, e.g., Rentas v. Ruffin, 816 F.3d 214, \n\n19 221  (2d  Cir.  2016).  Jeffreys  is  inapposite  because  the  self‐serving \n\n\n\n   Bellamy  affirmatively  denies  making  the  “murder”  statement  but \n 19\n\n takes  a  softer  stance  as  to  the  “accuse”  statement,  stating  he  cannot \n remember making it but that if he did it was “probably . . . after they . . . put \n the [photo of the] bloody guy on the table and told me that two people said \n they seen me kill somebody.”  Bellamy Dep. Tr. 145–47. \n\n 37  No. 17‐1859\n\n 1 testimony in that case was “contradictory and incomplete,” and “so \n\n 2 replete  with  inconsistencies  and  improbabilities  that  no  reasonable \n\n 3 juror would undertake the suspension of disbelief necessary to credit \n\n 4 the  allegations.”    426  F.3d  at  555.    Here,  Bellamy’s  testimony  was \n\n 5 consistent and uncomplicated:  he never made the statement.  Neither \n\n 6 is his testimony wholly improbable:  why would Bellamy offer such \n\n 7 an admission when he was told only that he was being picked up on \n\n 8 a public drinking charge? \n\n 9 Further  distinguishing  this  case  from  Jeffreys  is  that  there  is \n\n10 evidence  in  the  record,  independent  from  Bellamy’s  unequivocal \n\n11 denial, tending to support an inference of fabrication.  The DD‐5 that \n\n12 Detective  Gillen  drafted  that  summarized  the  circumstances  of \n\n13 Bellamy’s  pickup  makes  no  mention  of  the  “murder”  statement, \n\n14 despite the fact that the DD‐5 both identified that Bellamy was being \n\n15 investigated for homicide and that Detective Gillen was specifically \n\n16 investigating the Abbott murder when he went to pick up Bellamy.  \n\n17 See App’x 1738; see also Trial Tr. 491.  At trial, Detective Gillen will no \n\n18 doubt be asked to explain this omission from the DD‐5.  In so doing, \n\n19 he may repeat the explanation he offered at a pre‐trial hearing that \n\n20 the omission was “basically an oversight.”  App’x 2411.  The jury will \n\n21 be free, however, to weigh that assertion against evidence that NYPD \n\n22 detectives  commonly  understand  that  DD‐5s  are  to  be  used  at  trial \n\n23 and  that  it  is  protocol  for  a  suspect’s  statements  to  be  incorporated \n\n 38  No. 17‐1859\n\n 1 into  a  DD‐5,  especially  statements  as  significant  as  those  that \n\n 2 Detective Gillen attributes to Bellamy.  See Solomeno Dep. Tr. 27–28; \n\n 3 Guy Dep. Tr. 79, 126–27; see also Trial Tr. 532–33 (Gillen testimony that \n\n 4 he prepared eight DD‐5s related to the Abbott murder investigation \n\n 5 alone).   \n\n 6 The  jury  will  also  be  free  to  weigh  other  evidence  tending to \n\n 7 undermine  Detective  Gillen’s  testimony  that  Bellamy  made  the \n\n 8 “murder” statement in the police car, such as the fact that Detective \n\n 9 Gillen did not identify this statement during his grand jury testimony, \n\n10 see  App’x  336–38,  and  the  fact  that  the  record  shows  that  Detective \n\n11 Gillen,  who  was  in  the  backseat  with  Bellamy,  said  that  Bellamy \n\n12 “yell[ed]”  the  “murder”  statement  but  neither  of  the  two  other \n\n13 officers who were in the car was asked to—or did—corroborate his \n\n14 story. Both of those detectives testified at trial and neither mentioned \n\n15 the “murder” statement.  Gillen Dep. Tr. 53; Trial Tr. 495.  In sum, the \n\n16 jury  would  be  entitled  to  consider  the  lack  of  corroboration  of \n\n17 Detective Gillen’s testimony.20  \n\n\n\n\n  Defendants assert support for the accuracy of Gillen’s transcription of \n 20\n\n the “murder” statement in the form of ADA Antignani’s notice served to \n Bellamy pursuant to N.Y. Crim. Proc. Law § 710.30 two days after Bellamy \n was picked up, which notifies Bellamy of the state’s intent to rely on the \n “murder” statement at trial.  App’x 1610.  Even if this fact could support an \n inference that the Gillen transcription was accurate, it just as easily supports \n the inference that ADA Antignani simply relied on Gillen’s fabricated note. \n\n 39  No. 17‐1859\n\n 1 We conclude that, taken as a whole, the evidence compiled at \n\n 2 summary judgment, viewed in the light most favorable to Bellamy, \n\n 3 cannot  rule  out  the  inference  that  Detective  Gillen  fabricated  the \n\n 4 “murder” statement.  Bellamy has therefore raised a material issue of \n\n 5 fact precluding summary judgment on this fair trial claim. \n\n 6 ii. DD‐5 Documenting Walker Interview \n\n 7 On  December  1,  2005,  while  Bellamy’s  criminal  trial  was \n\n 8 ongoing,  Detectives  Solomeno  and  Gillen  for  the  first  time \n\n 9 interviewed Veronica Walker, who, as discussed, testified at trial that \n\n10 she  had  been  at  the  scene  in  her  car  when  Abbott  was  killed.  \n\n11 Following that interview, Detective Solomeno drafted a DD‐5 that, he \n\n12 testified, memorialized Walker’s statements and forwarded the DD‐5 \n\n13 to ADA Guy.  Bellamy contends that Detective Solomeno fabricated \n\n14 the statements inculpating Bellamy attributed to Walker in that DD‐\n\n15 5, and that the state materially relied on the fabricated DD‐5 at trial.  \n\n16 We conclude that the summary judgment record, again taken in the \n\n17 light most favorable to non‐movant Bellamy, raises a material issue of \n\n18 fact as to whether Detective Solomeno in fact fabricated the evidence \n\n19 contained in the DD‐5.  \n\n20 At her deposition, Walker testified in detail about her mid‐trial \n\n21 interview with Detectives Solomeno and Gillen.  Walker testified that \n\n22 the  detectives  told  her  they  received  her  contact  information  from \n\n23 Deborah Abbott, the victim’s sister, and that Deborah had reported to \n\n 40  No. 17‐1859\n\n 1 them that she had a conversation with Walker in which Walker said \n\n 2 she witnessed Bellamy kill Abbott.  Walker testified that she told the \n\n 3 detectives that the story was not true, but the detectives continued to \n\n 4 insist  to  her  that  she  witnessed  Bellamy  murder  Abbott.    Detective \n\n 5 Solomeno  then  showed  Walker  two  photos  of  Bellamy,  whom  she \n\n 6 told the detectives she recognized and had seen over 300 times in her \n\n 7 life.  Walker testified that she repeatedly told the detectives, however, \n\n 8 that it was not Bellamy that she saw on the day of the Abbott murder.  \n\n 9 She  testified  that,  despite  those  statements,  Detective  Solomeno \n\n10 drafted the following handwritten statement directly to the contrary \n\n11 and asked Walker to sign it: \n\n12 Miss Walker stated that she drove past the two males \n13 fighting and that when . . . she looked back and then \n14 saw another male black she knew as Kareem Bellamy \n15 also  fighting  with  James  [Abbott]  and  that  Kareem \n16 and the other male black were kicking and punching \n17 James. \n\n18 App’x 2128–29.  Walker swore that she refused to sign the statement \n\n19 because, in her view and consistent with her repeated statements to \n\n20 the detectives, it was not true.  As she explained in her deposition:   \n\n21 I read the whole thing and that is not what it stated \n22 that I said.  It stated that I witnessed Kareem, that I \n23 seen  Kareem  and  that  is  what  I  was  saying  to  them \n24 and that’s the reason why I didn’t sign it because I did \n25 not see him. \n\n 41  No. 17‐1859\n\n 1 Walker Dep. Tr. 40.  Walker repeatedly characterized the statement as \n\n 2 “lies,”  Walker  Dep.  Tr.  127–31,  the  same  position  she  took  years \n\n 3 earlier when testifying at Bellamy’s § 440 proceeding.  First 440 Tr. 97 \n\n 4 (“Absolutely not. Never told them that.”). \n\n 5   While Detectives Solomeno and Gillen both insist the statement \n\n 6 was true, they concede that Walker refused to sign the statement that \n\n 7 Detective Solomeno drafted during their December 1, 2005 interview.  \n\n 8 Solomeno  Dep.  Tr.  42–43;  Gillen  Dep.  Tr.  191.    Detective  Solomeno \n\n 9 acknowledges that he nevertheless put the “almost word for word” \n\n10 statement in a DD‐5, but failed to disclose in the DD‐5 that Walker \n\n11 refused to sign it (as he concedes he “should have” done), and that he \n\n12 gave the DD‐5 to ADA Guy, again without revealing to the prosecutor \n\n13 that Walker refused to sign the statement.  Solomeno Dep. Tr. 143–45.  \n\n14 ADA  Guy  testified  that  he  was  unaware  of  any  of  this  and \n\n15 characterized the allegations of the concealment of the refusal to sign \n\n16 as “very troubling,” and, if true, “reprehensible.” Guy Dep. Tr. 117. \n\n17   Significantly,  the  Defendants  do  not  dispute  that  the  above \n\n18 evidence  at  the  least  raises  an  issue  of  fact  as  to  whether  Detective \n\n19 Solomeno fabricated the Walker statement and forwarded it to ADA \n\n20 Guy.    See  Br.  of  Appellees  44–46.    Their  sole  argument  in  favor  of \n\n21 dismissal of this evidence fabrication claim is that the allegedly false \n\n22 DD‐5 was immaterial in that it did not impact Bellamy’s criminal trial \n\n23 because it was not introduced into evidence and, at trial, Walker did \n\n 42  No. 17‐1859\n\n 1 not identify Bellamy.  For support, they rely on DuFort v. City of New \n\n 2 York,  874  F.3d  338  (2d  Cir.  2017),  where  we  concluded  that  ʺ[m]ere \n\n 3 attempts  to  withhold  or  falsify  evidence  cannot  form  the  basis  of  a \n\n 4 § 1983  claim  for  violation  of  the  right  to  due  process  when  those \n\n 5 attempts have no impact on the conduct of a criminal trial.”  Id. at 355.  \n\n 6 We find DuFort readily distinguishable. \n\n 7   DuFort  involved  a  “paradigmatic  example  of  an  improperly \n\n 8 suggestive  lineup,”  in  which  detectives  allowed  a  criminal  suspect, \n\n 9 DuFort, to wear a red sweatshirt during a lineup despite knowing that \n\n10 the sole eyewitness, Park, had told them that, although she could not \n\n11 identify his face, one of the assailants was wearing a red sweatshirt \n\n12 during the commission of the crime.  Id. at 348.  Park then selected \n\n13 DuFort out of the lineup but did so based solely on her knowledge \n\n14 that  the  assailant  was  wearing  a  red  sweatshirt.    During  the \n\n15 subsequent criminal trial of DuFort, Park could not identify DuFort \n\n16 and  testified  that  she  only  selected  DuFort  at  the  lineup  due  to  his \n\n17 distinctive clothing.  Id.   \n\n18 DuFort  was  acquitted  and  sued  the  detectives  claiming  that \n\n19 their manipulation of the lineup violated his right to a fair trial.  We \n\n20 rejected the claim, noting that evidence fabrication claims rest on “the \n\n21 right to have one’s case tried based on an accurate evidentiary record \n\n22 that has not been manipulated by the prosecution.”  Id. at 355.  We \n\n23 concluded  that  there  was  no  such  defect  in  DuFort’s  trial  record  in \n\n 43  No. 17‐1859\n\n 1 light  of  Park’s  unequivocal  and  unchallenged testimony  to  the  jury \n\n 2 that she only identified DuFort because of his clothing: “the evidence \n\n 3 that  DuFort  claims  was  withheld  or  misrepresented  was  in  fact \n\n 4 disclosed  in  a  straightforward  manner  at  the  trial:  the  prosecution \n\n 5 elicited testimony from [the witness] that she recognized DuFort not \n\n 6 by his face, but by his clothing.”  Id.  Consequently, in DuFort, the jury \n\n 7 was  presented  with  the  full  universe  of  information,  despite  any \n\n 8 earlier police misconduct.  Indeed, we noted that it was “undisputed \n\n 9 that [the] attempt [to distort the trial record] failed.”  Id. \n\n10 DuFort is far afield from the instant case because it is not clear \n\n11 (and  certainly  not  undisputed)  that  Detective  Solomeno’s  allegedly \n\n12 false  DD‐5  report  had  “no  impact  on  the  conduct  of  [Bellamy’s] \n\n13 criminal trial.”  DuFort, 874 F.3d at 355. (emphasis added).  Although \n\n14 Walker did not identify Bellamy as the assailant at trial, there was an \n\n15 unacceptable risk, due only to the allegedly fabricated DD‐5, that the \n\n16 jury  was  left  with  the  potentially  incorrect  impression  that  she  had \n\n17 done so previously.  During Solomeno’s testimony, ADA Guy elicited \n\n18 the  fact  that  Solomemo  had  prepared  a  DD‐5  to  memorialize  the \n\n19 interview  with  Walker.  Trial  Tr.  802.  While  ADA  Guy  did  not \n\n20 introduce the DD‐5 into evidence, he then asked Walker during her \n\n21 testimony, “didn’t you tell Detective Solomeno and Detective Gillen \n\n22 that you recognized that person as Kareem?”  Trial Tr. 1005.  Despite \n\n23 Walker’s response of “No,” the jury could have viewed ADA Guy’s \n\n 44  No. 17‐1859\n\n 1 question itself as suggesting that Walker did in fact tell the detectives \n\n 2 that it was Bellamy she saw and that ADA Guy had a good faith basis \n\n 3 for asking the question.  And ADA Guy would have had no basis to \n\n 4 ask that question if Detective Solomeno had not provided him with \n\n 5 the  allegedly  fabricated  DD‐5.    We  have  previously  noted  that,  in \n\n 6 contexts  such  as  these,  “defense  counsel’s  unanswered  questions \n\n 7 about prior inconsistent statements [may] likely alert[] the jury to the \n\n 8 issue of the reliability of [the] testimony,” and, even where “the jury \n\n 9 was  told  that  the  lawyer’s  questions  are  not  evidence  .  .  .  the  sting \n\n10 survives such instructions.”  See Washington v. Schriver, 255 F.3d 45, 61 \n\n11 (2d  Cir.  2001)  (internal  quotation  marks  omitted).21    Significantly, \n\n12 ADA Guy then closed the loop in summation when he argued to the \n\n13 jury  that  it  should  take  stock  of  what  Walker  said  in  her  interview \n\n14 with Detectives Solomeno and Gillen.  Trial Tr. 1122–23; see also Trial \n\n15 Tr. 1144.22 \n\n16   Further  evidence  supports  the  material  impact  of  the  Walker \n\n17 DD‐5 on Bellamy’s conviction.  After the trial, ADA Guy stated that \n\n\n\n  To analogize to DuFort, it would be as if DuFort’s prosecutor asked \n 21\n\n Park:  “Isn’t it true that you told the detectives that you recognized DuFort \n wholly apart from his clothing?”  But DuFort’s prosecutor asked no such \n thing. \n   An  illustration  of  the  potential  for  confusion  caused  by  Walker’s \n 22\n\n testimony  is  that,  in  resolving  Bellamy’s  petition  for  habeas  corpus,  the \n federal  district  court  incorrectly  stated  that  at  trial  “[t]hree  witnesses \n identified petitioner as present at [t]he scene of the murder.”  App’x 613. \n\n 45  No. 17‐1859\n\n 1 the DD‐5 was “most helpful” to the prosecution.  App’x 1752.  As he \n\n 2 wrote in a post‐trial “commendation letter” to NYPD Commissioner \n\n 3 William Bratton praising Detectives Solomeno and Gillen’s conduct \n\n 4 specifically with respect to the Walker DD‐5: \n\n 5 [Detectives Solomeno and Gillen] also helped locate a \n 6 previously  unknown  (second)  eye‐witness  to  the \n 7 murder and interviewed her in the midst of my trial, \n 8 and helped secure her appearance, too.  She proved to \n 9 be fairly uncooperative, but because your detectives had \n10 prepared a detailed DD‐5 of their conversation with her, she \n11 had less “wiggle” room, and in the end what she had told \n12 the detectives proved most helpful. \n\n13 App’x 1752 (emphasis added).  It is therefore plain that ADA Guy, for \n\n14 his  part,  thought  that  the  DD‐5  provided  to  him  by  Detective \n\n15 Solomeno was material to Bellamy’s conviction.  See also Guy Dep. Tr. \n\n16 208 (testifying that he only sent commendation letters “from time to \n\n17 time in a case that I thought merited a little pat on the back . . .  Not \n\n18 many, more than just two or three”).  Finally, it bears noting that the \n\n19 jurors apparently attached significance to Walker’s testimony because \n\n20 that testimony prompted their only request for a second readback of \n\n21 particular testimony during deliberations.  See Trial Tr. 1209, 1224–26.  \n\n22 Under these circumstances, we find that there is “an overwhelming \n\n23 probability  that  the  jury  [was]  unable  to  follow  the  court’s \n\n24 instructions”  that  the  lawyers’  questions  are  not  evidence,  and  “a \n\n25 strong likelihood that the effect of the evidence [was] devastating to \n\n 46  No. 17‐1859\n\n 1 the defendant.” Greer v. Miller, 483 U.S. 756, 766 n.8 (1987) (citation \n\n 2 omitted).  \n\n 3   Of course, it is entirely possible that Walker implicated Bellamy \n\n 4 to  the  detectives  and  that  her  later  denials  were  false,  and  that \n\n 5 Detective  Solomeno  simply  prepared  a  truthful  DD‐5  that  Walker \n\n 6 refused to sign.  But this is a quintessentially disputed fact issue, as \n\n 7 neither side contests, and it is a material one, as the record shows.  We \n\n 8 therefore conclude that, notwithstanding DuFort, Bellamy has raised \n\n 9 a material issue of fact as to the truth or fabrication of the contents of \n\n10 the  DD‐5  purportedly  memorializing  Detectives  Solomeno  and \n\n11 Gillen’s December 1, 2005 interview with Walker. \n\n12 iii. Carter’s Lineup Identification \n\n13 Bellamy  contends  that  Detective  Gillen  pressured  Carter  to \n\n14 identify  Bellamy  in  the  lineup  that  took  place  on  May  14,  1994.  \n\n15 Specifically,  Bellamy  contends  that  Carter  initially  was  indecisive \n\n16 about whether the assailant was in position one or two, but that Carter \n\n17 was  then  taken  to  another  room  with  Detective  Gillen  where \n\n18 Detective Gillen proceeded to put pressure on Carter to identify the \n\n19 individual in position one, which Carter ultimately did.  \n\n20 The  sole  direct  evidence  supporting  this  claim  appears  to  be \n\n21 Carter’s testimony at Bellamy’s § 440 proceeding, in which Carter, in \n\n22 recanting  his  trial  testimony,  testified  that  Detective  Gillen  pointed \n\n23 out  Bellamy  at  the  lineup  and  pressured  Carter  to  identify  him.  \n\n 47  No. 17‐1859\n\n 1 Subsequent  to  that  testimony,  however,  Carter  died,  and  Bellamy \n\n 2 concedes that Carter’s testimony at the § 440 proceeding will not be \n\n 3 admissible at trial.  Br. of Appellant at 24 n.10.  And, it is axiomatic \n\n 4 that, when reviewing a summary judgment determination, we may \n\n 5 only consider admissible evidence.  See Ehrens v. Lutheran Church, 385 \n\n 6 F.3d 232, 235 (2d Cir. 2004) (per curiam). Bellamy therefore relies only \n\n 7 on a claimed inference in his attempt to raise a genuine issue of fact \n\n 8 as  to  whether  Detective  Gillen  pressured  Carter  at  the  lineup.  \n\n 9 Bellamy  focuses  on  two  aspects  of  Detective  Gillen’s  testimony:  (i) \n\n10 that Detective Gillen told Bellamy to pat down his braids prior to the \n\n11 lineup; and (ii) that Carter then told Detective Gillen that the basis of \n\n12 his confusion as to whether the assailant was in position one or two \n\n13 was the braided hair of the individual in position one.  Consequently, \n\n14 Bellamy contends that it is “likely [that Gillen] suggested to Carter the \n\n15 braids explanation for why he had failed to recognize Number 1.”  Br. \n\n16 of  Appellant  at  41.    This  contention  is  pure  speculation  and  is \n\n17 therefore insufficient to raise a triable issue of fact.  See Harlan Assocs. \n\n18 v. Inc. Village of Mineola, 273 F.3d 494, 502 (2d Cir. 2001).  We affirm \n\n19 the district court’s dismissal of this claim of misconduct. \n\n20 b. Evidence Withholding Claims \n\n21 When  police  officers  withhold  exculpatory  or  impeaching \n\n22 evidence from prosecutors, they may be held liable under § 1983 for \n\n23 violating the disclosure requirements of Brady v. Maryland, 373 U.S. \n\n 48  No. 17‐1859\n\n 1 83 (1963).23  See Bermudez v. City of New York, 790 F.3d 368, 376 n.4 (2d \n\n 2 Cir. 2015) (citing Walker v. City of New York, 974 F.2d 293, 299 (2d Cir. \n\n 3 1992)).    To  prevail  on  such  a  claim,  a  plaintiff  must  show  the \n\n 4 materiality  of  the  nondisclosed  evidence,  a  showing  that  “does  not \n\n 5 depend  on  factual  innocence,  but  rather  what  would  have  been \n\n 6 proven absent the violation . . . [with] reference to the likely effect that \n\n 7 the suppression of [the] particular evidence had on the outcome of the \n\n 8 trial.”  Poventud v. City of New York, 750 F.3d 121, 134 (2d Cir. 2014) (en \n\n 9 banc)  (internal  quotation  marks  and  emphasis  omitted).    Stated \n\n10 differently,  to  show  prejudice  the  claimant  “must  demonstrate  a \n\n11 reasonable  probability  that,  had  the  evidence  been  disclosed,  the \n\n12 result of the proceeding would have been different.”  United States v. \n\n13 Ulbricht,  858  F.3d  71,  112  (2d  Cir.  2017)  (internal  quotation  marks \n\n14 omitted).  For example, a § 1983 plaintiff proceeding on a Brady theory \n\n\n  We have suggested, though without so concluding, that a civil Brady \n 23\n\n claim  requires  a  showing  that  the  non‐disclosure  was  intentional.    See \n Fappiano v. City of New York, 640 F. App’x 115, 118 (2d Cir. 2017 (summary \n order);  see  also  Darnell  v.  Pineiro,  849  F.3d  17,  36  (2d  Cir.  2017).    Even \n assuming  such  an  intent  requirement,  we  have  no  need  to  specifically \n address, at this stage, the detectives’ intent as to each of the alleged Brady \n violations  here.    This  is  because  of  the  evidence  in  the  record,  already \n discussed,  that  raises  material  issues  of  fact  as  to  whether  Detective \n Solomeno  and  Gillen’s  conducting  of  the  Abbott  investigation  was \n improper.    See  Manganiello  v.  City  of  New  York,  612  F.3d  149,  164  (2d  Cir. \n 2010) (permitting an inference of a detective’s malice because, “in light of \n the other evidence as to [the detective’s] conduct of the investigation, [the \n jury  would  be  entitled]  to  view  [the  detective’s]  misrepresentation  as \n indicative of [his] state of mind all along”). \n\n 49  No. 17‐1859\n\n 1 can  succeed  on  his  claim  if,  had  the  withheld  information  been \n\n 2 disclosed  prior  to  trial,  “he  would  have  been  acquitted  based  on \n\n 3 reasonable doubt or convicted on a lesser charge.”  Poventud, 750 F.3d \n\n 4 at 134–35. \n\n 5 Bellamy contends that Detectives Solomeno and Gillen violated \n\n 6 Brady  by  failing  to  disclose  to  prosecutors  four  categories  of \n\n 7 exculpatory or impeaching statements made by Sanchez and Walker \n\n 8 during the course of the investigation of the Abbott murder: first, that \n\n 9 in the weeks following the murder, Sanchez told Detective Gillen that \n\n10 she saw Bellamy in the C‐Town trying to buy beer on a day in which \n\n11 C‐Town did not (and legally could not) sell beer before noon, which \n\n12 could  only  have  been  a  Sunday  (rather  than  a  Saturday,  the  day \n\n13 Abbott  was  killed);  second,  that  Sanchez  identified  Terrill  Lee  to \n\n14 Detective  Gillen  as  the  person  that  she  saw  with  Bellamy  in  the  C‐\n\n15 Town on the morning of Abbott’s murder; third, that on the day of \n\n16 Abbott’s  murder  Sanchez  told  Detective  Gillen  that  she  “didn’t  see \n\n17 anything”  and  “didn’t  know  anything”;  and  fourth,  Detectives \n\n18 Solomeno  and  Gillen  failed  to  disclose  Walker’s  claimed  non‐\n\n19 identification of Bellamy at her December 1, 1995 interview as well as \n\n20 her  refusal  to  sign  the  DD‐5  attesting  that  she  had  so  identified \n\n21 Bellamy.  We address each in turn. \n\n 50  No. 17‐1859\n\n 1 i. Sanchez’s Sunday/Beer Statement \n\n 2 Bellamy contends that Detectives Solomeno and Gillen failed to \n\n 3 disclose to the prosecution statements Sanchez made to them during \n\n 4 the  investigation  of  the  Abbott  murder  that  the  day  in  which  she \n\n 5 reported  seeing  Bellamy  in  the  C‐Town  with  Abbott  was  a  Sunday \n\n 6 and  a  day  in  which  the  C‐Town  could  not  have  lawfully  sold  beer \n\n 7 prior to noon (which could only have been a Sunday).  See N.Y. Alco. \n\n 8 Bev. Cont. Law § 105‐a (1971) (amended 2006).  It is undisputed that \n\n 9 Abbott  was  killed  on  Saturday,  April  9,  1994.    Although  Sanchez’s \n\n10 several rounds of testimony in this legal saga have been consistently \n\n11 inconsistent, Sanchez more than once testified that she told detectives \n\n 51  No. 17‐1859\n\n1 that  she  saw  Bellamy  on  a  Sunday.24    During  Bellamy’s  §  440 \n\n2 proceeding, she repeatedly testified that Bellamy was trying to buy \n\n3 beer on a Sunday when he could not, and agreed that she “first told \n\n4 police that [she] saw Kareem Bellamy on a Sunday.”  First 440 Tr. 458–\n\n\n\n  Sanchez’s testimony as to which day she remembered seeing Bellamy \n 24\n\n has been, at best, confused.  At the grand jury, she testified that Bellamy \n bought beer on the day in question.  App’x 320–23.  And at trial, she was \n asked “[w]hat first caused you to notice the defendant inside that C‐Town \n that morning,” to which she responded, “[h]e was buying beer.”  Trial Tr. \n 641.  But, ADA Guy followed up with, “[d]id anything direct your attention \n to  the  defendant  that  morning,”  to  which  Sanchez  responded,  “[h]e  was \n buying beer on a Sunday—on a Saturday that day.”  Trial Tr. 642.  This self‐\n correction is curious, however, because it begs the question why it would \n have  been  notable  for  Sanchez  to  notice  that  Bellamy  was  specifically \n buying  beer  on  a  Saturday.    Sanchez  sowed  further  confusion  during  the \n § 440 proceeding, where she unequivocally testified that, on the day of the \n murder, Bellamy “was trying to buy beer on a day he couldn’t buy beer,” \n clarified that that day was a Sunday, and recalled that the C‐Town manager \n even told Bellamy that “you can’t buy beer.”  First 440 Tr. 453–60, 490–91.  \n Her  story  got  more  confusing  at  her  deposition  in  this  case,  when  she \n continued  to  adamantly  assert  that  she  saw  Bellamy  on  “a  day  that  you \n couldn’t buy beer,” but also that she was certain that the day was a Saturday \n (a day in which you could buy beer).  Sanchez Dep. Tr. 24–27.  Sanchez then \n testified,  for  the  first  time,  that  she  specifically  remembers  it  being  a \n Saturday because  she “freshen[ed] up [her]  memory and  speaking to the \n members of [her] family it was a Saturday because [a family member named \n Julio]  was  outside  mechanicking  on  the  block.”    Sanchez  Dep.  Tr.  26–27.  \n She even testified that “I told [my family] it was Sunday [and] they said no \n Linda,  it  wasn’t  Sunday  it  was  Saturday  .  .  .  the  guy  Julio  was  outside \n mechanicking and he remember clearly it was Saturday.”  Sanchez Dep. Tr. \n 139–40.  Despite accepting her family’s correction that it was a Saturday, \n Sanchez nevertheless vividly remembered that Bellamy was trying to buy \n beer on a day that C‐Town could not sell beer.  Indeed, she remembered \n that Bellamy was upset because he could not buy beer, “I just know he had \n a look on his face, just body language.”  Sanchez Dep. Tr. 37. \n\n 52  No. 17‐1859\n\n 1 59.    She  reaffirmed  this  testimony  in  her  deposition  in  this  case, \n\n 2 testifying that “[a]t some point” she told Detective Gillen that Bellamy \n\n 3 was trying to buy beer on the same morning of the murder and that \n\n 4 the manager told Bellamy that he could not do so.  Sanchez Dep. Tr. \n\n 5 37.    Although  both  detectives  deny  any  recollection  of  these \n\n 6 statements by Sanchez, First 440 Tr. 912–13; Gillen Dep. Tr. 162–65; \n\n 7 Solomeno  Dep.  Tr.  116–17,  Sanchez’s  testimony  both  at  the  §  440 \n\n 8 proceeding and her deposition create a triable question of fact as to \n\n 9 whether the statements were made to either of the detectives (and not \n\n10 disclosed to the prosecution). \n\n11 The question then becomes one of materiality.  We believe that \n\n12 disclosure of the above statements would have significantly increased \n\n13 the defense’s chances of sowing a reasonable doubt in the jury’s mind \n\n14 about  Bellamy’s  guilt.    As  identified  in  detail,  see  infra  note  24, \n\n15 Sanchez,  a  key  state  witness,  has  consistently  held  the  inconsistent \n\n16 positions that she is certain that the morning she saw Bellamy in the \n\n17 C‐Town was a day in which the C‐Town could not lawfully sell beer, \n\n18 but also that the morning was a Saturday.  Had defense counsel been \n\n19 able to impeach Sanchez with that obvious inconsistency in front of \n\n20 the jury it would have been of great value to the defense, given how \n\n21 relatively thin the overall evidence was against Bellamy.   \n\n22 Indeed,  both  ADAs  Guy  and  Antignani,  as  well  as  Detective \n\n23 Solomeno,  conceded  in  their  depositions  the  materiality  of  any \n\n 53  No. 17‐1859\n\n 1 statements by Sanchez that she saw Bellamy on a day in which the C‐\n\n 2 Town could not lawfully sell beer.  ADA Guy testified that, if he had \n\n 3 known about them, he would have likely turned over such statements \n\n 4 precisely “so that the defense attorney could explore her confusion as \n\n 5 to  the  date.”    Guy  Dep.  Tr.  127.    He  continued:  “if  [Sanchez] \n\n 6 remembered that it was a Sunday because you’re not allowed to sell \n\n 7 beer on a Sunday before noon, that might give more credence to it,” \n\n 8 and  “[i]f  she  had  said  that  to  Detective  Gillen  .  .  .  [he]  presumably \n\n 9 would  have  written  that  in  the  DD‐5.”    Guy  Dep.  Tr.  126–27.  \n\n10 Detective  Solomeno  also  agreed,  evidenced  by  his  deposition \n\n11 testimony  that  if  he  had  heard  Sanchez  make  these  statements  he \n\n12 would  have  recorded  them.    Solomeno  Dep.  Tr.  117.    As  did  ADA \n\n13 Antignani,  who  testified  at  his  deposition  that  “if  in  fact,  Linda \n\n14 Sanchez said that to John Gillen, then I think John Gillen should have \n\n15 said it.”  Antignani Dep. Tr. 86–87.   \n\n16 We  therefore  conclude  that  there  is  sufficient  evidence  from \n\n17 which a jury could reasonably determine that the nondisclosure of the \n\n18 Sanchez Sunday/beer statements, if they were made to the detectives \n\n19 (another  jury  question),  were  actionable  Brady  violations.    Bellamy \n\n20 has therefore raised a triable issue of fact as to this allegation. \n\n21 ii. Sanchez’s Identification of Terrill Lee \n\n22 Bellamy contends that Detective Gillen failed to disclose that, \n\n23 during  the  investigation,  Sanchez  identified  Terrill  Lee  as  the \n\n 54  No. 17‐1859\n\n 1 individual  with  Bellamy  in  the  C‐Town  on  the  day  of  Abbott’s \n\n 2 murder.    The  contention  centers  on  Sanchez’s  testimony  during \n\n 3 Bellamy’s § 440 proceeding in which she testified that, following the \n\n 4 lineup,  a  detective  showed  her  a  Polaroid  photo  of  Lee,  whom  she \n\n 5 then identified to the detective as the person she saw with Bellamy in \n\n 6 the C‐Town on the morning of Abbott’s murder.25  First 440 Tr. 468; \n\n 7 see also Gillen Dep. Tr. 170 (discussing that Lee had a Polaroid taken \n\n 8 at the precinct). \n\n 9 The parties dispute whether Detective Gillen showed Sanchez \n\n10 a photo of Lee (and thus whether Sanchez identified Lee to Detective \n\n11 Gillen).   Although Sanchez  so  testified  at  the § 440  proceeding,  she \n\n12 subsequently did not recall being shown Lee’s photo when testifying \n\n13 at  her  deposition  in  this  case.    Sanchez  Dep.  Tr.  45–46.    However, \n\n14 despite her lack of recollection then (seven years later, and more than \n\n15 twenty years from the alleged incident), she also testified that she had \n\n16 no reason to think she did not tell the truth when she so testified at \n\n\n  Defendants contend that the evidence cannot establish that Detective \n 25\n\n Gillen  was  the  “detective”  that  Sanchez  referenced  when  she  was \n purportedly shown the Lee photo.  Br. of Appellees at 53 (relying on the \n fact that Sanchez’s testimony only uses the pronoun “they”).  The argument \n is meritless.  Sanchez made clear that it was “one” of the “detective[s]” who \n showed her the photo “after the lineup.”  First 440 Tr. 468.  And the record \n makes plain that Detective Gillen was the only detective at the lineup and \n that he oversaw the lineup.  See Trial Tr. 502–09; App’x 293; First 440 Tr. \n 1109.    At  the  very  least,  we  would  be  required  at  this  stage  to  infer  that \n Sanchez’s testimony referenced Detective Gillen.  Ultimately, however, the \n question is for the jury to decide. \n\n 55  No. 17‐1859\n\n 1 the  §  440  proceeding.    Sanchez  Dep.  Tr.  45–46.    While  Detective \n\n 2 Solomeno and ADAs Antignani and Guy each testified that someone \n\n 3 should  have  shown  Lee’s  photo  to  Sanchez,  Solomeno  Dep.  Tr.  169; \n\n 4 Antignani Dep. Tr. 122–23; Guy Dep. Tr. 76–77, Detective Gillen and \n\n 5 ADAs  Antignani  and  Guy  each  testified  that  they  did  not  show \n\n 6 Sanchez a photo of Lee and that they do not know if anyone else did.  \n\n 7 First 440 Tr. 865, 877 (Gillen); First 440 Tr. 1111, 1151–52, 1164, 1165 \n\n 8 (ADA Antignani); First 440 Tr. 1178, 1210–11 (ADA Guy); Gillen Dep. \n\n 9 Tr. 170.    \n\n10 Although a close question, we conclude that Bellamy has raised \n\n11 a genuine disputed issue of fact as to whether Sanchez told Detective \n\n12 Gillen  that  Lee  was  the  individual  with  Bellamy  (and  therefore \n\n13 whether Detective Gillen failed to disclose such).  See Del. & Hudson \n\n14 Ry. Co. v. Consolidated Rail Corp., 902 F.2d 174, 177–78 (2d Cir. 1990) \n\n15 (summary judgment non‐movant need only demonstrate “that there \n\n16 is  some  evidence  which  would  create  a  genuine  issue,”  meaning \n\n17 “more  than  a  scintilla  of  evidence”  and  “more  than  some \n\n18 metaphysical doubt as to the material facts” (internal quotation marks \n\n19 omitted)). \n\n20 The district court came to no conclusion as to the state of the \n\n21 factual record on this allegation, and rather concluded that “even if \n\n22 Sanchez had identified [Lee] as the plaintiff’s companion, it is difficult \n\n 56  No. 17‐1859\n\n 1 to  see  how  that  would  have  been  helpful  to  [Bellamy].”    2017  WL \n\n 2 2189528, at *36.  We disagree.   \n\n 3 Because  the  record  makes  plain  that  the  detectives  had  no \n\n 4 suspicions  that  Lee  was  involved  in  the  Abbott  murder,  see  Gillen \n\n 5 Dep. Tr. 170–71; see also Antignani Dep. Tr. 146–47; Guy Dep. Tr. 69–\n\n 6 72, any identification of Lee by Sanchez as being in the C‐Town with \n\n 7 Bellamy  would  seriously  undermine  the  reliability  of  Sanchez’s \n\n 8 placement of Bellamy in the store on the morning of Abbott’s murder.  \n\n 9 If  Lee  was  not  with  Bellamy  on  the  morning  in  question—as  the \n\n10 detectives seemingly concluded—and if Bellamy was with Lee at the \n\n11 time Sanchez had in mind during her trial testimony, Sanchez must \n\n12 have  been  confused  about  which  morning  she  saw  Bellamy,  a  not \n\n13 unlikely possibility, as previously discussed in depth, see infra note 24, \n\n14 and  as  one  particular  exchange  highlights.26    And  Sanchez’s \n\n15 identification  of  Lee  to  Detective  Gillen  would  be  material  even  if \n\n16 Sanchez was wrong about her identification of Lee because it would \n\n17 call into question Sanchez’s general recollection of the morning of the \n\n\n  “Q: [Y]ou had seen two people that Sunday?  A: Yes.  Q: Correct. When \n 26\n\n you  say  the  other  guy  are  you  referring  to  the  other  guy  you  saw  that \n Sunday?  A: The other guy that was with Kareem . . . .  Q: Where you shown \n a photograph of this other guy?  A: Yes.  Q: Okay. And what did—what \n kind of photograph was it?  A: It’s a Polaroid . . . .  Q: So they told you that \n the person in the photograph was Terrell Lee?  A: Yes.  Q: Well, just—I just \n want to be clear.  And you told them that the person in that Polaroid photo \n who they told you was Terrell Lee was the person you saw together with \n Kareem; is that correct?  A: Yes.” 440 Tr. 464–68.  \n\n 57  No. 17‐1859\n\n 1 Abbott murder, including her identification of Bellamy.  Either way, \n\n 2 had the defense known that Sanchez had at one point contended that \n\n 3 Lee was the person with Bellamy on the morning of the murder, the \n\n 4 defense  would  have  had  an  important  additional  tool  of  cross‐\n\n 5 examination. \n\n 6 Consequently, viewing the evidence in Bellamy’s favor as we \n\n 7 must at this stage, we think that Bellamy has raised a genuine issue of \n\n 8 material  fact  as  to  whether  Detective  Gillen,  in  violation  of  Brady, \n\n 9 failed to disclose Sanchez’s identification of Lee.  \n\n10 iii. Sanchez’s  Didn’t  Know/See  Anything \n11 Statements \n\n12 Bellamy  contends  that  Detective  Gillen  failed  to  disclose \n\n13 statements Sanchez made on the morning of the Abbott murder that \n\n14 she  “didn’t  know  anything”  and  “didn’t  see  anything.”    Bellamy \n\n15 grounds  this  contention  on  Sanchez’s  testimony  at  Bellamy’s  §  440 \n\n16 proceeding, where Sanchez testified that on the morning of Abbott’s \n\n17 murder, certain detectives (including Detective Gillen) “came in the \n\n18 [C‐Town] supermarket.  I didn’t speak to them they just came in and \n\n19 they said do you know anything.  I said no . . . I said no, I didn’t know \n\n20 anything.”  First 440 Tr. 453; see also First 440 Tr. 459 (Sanchez agreeing \n\n21 with the statement that “the police came in on the day of the murder \n\n22 and  [she]  said  [she]  didn’t  see  anything”).    These  de  minimis \n\n23 statements,  even  if  they  were  made  (recall  that,  at  trial,  Sanchez \n\n 58  No. 17‐1859\n\n 1 denied  speaking  with  officers  the  morning  of  the  murder),  are \n\n 2 manifestly  immaterial  principally  because  nothing  in  the  record \n\n 3 shows that Sanchez had any reason to think that anything was afoot \n\n 4 when  Detective  Gillen  first  entered  the  C‐Town  that  morning.  \n\n 5 Indeed,  Sanchez  testified  at  trial  that  she  did  not  learn  of  Abbott’s \n\n 6 murder  until  a  week  later.    Trial  Tr.  745;  see  also  Trial  652–53.27  \n\n 7 Consequently,  at  that  time,  from  her  perspective,  Sanchez  did  not \n\n 8 “know”  or  “see”  anything  out  of  the  ordinary.    Disclosure  of  these \n\n 9 statements  would  therefore  not  have  served  to  materially  impeach \n\n10 Sanchez or exculpate Bellamy.  We affirm the district court’s dismissal \n\n11 of this Brady contention. \n\n12 iv. Walker’s December 1, 2005 Statements \n\n13 Apart from Bellamy’s claim that Detective Solomeno fabricated \n\n14 the contents of the DD‐5 purportedly memorializing the December 1, \n\n15 2005 interview of Veronica Walker, see infra at pp. 39–46, Bellamy also \n\n16 brings  a  Brady  claim  challenging  Detectives  Solomeno  and  Gillen’s \n\n\n\n   Bellamy  contends  that  Sanchez  “admitted  she  learned  of  Abbott’s \n 27\n\n murder  ‘when  the  cops  came  inside  the  C‐Town  to  ask  questions’  about \n Abbott.”  Br. of Appellants 44.  But, Sanchez’s testimony makes clear that \n she only learned about any incident of note from JJ, the C‐Town deli clerk, \n who told her about the subject of the officers’ visit only after “the cops were \n already  gone.”    First  440  Tr.  493.    Consequently,  although  Sanchez’s \n testimony has been inconsistent as to whether she first learned of the Abbott \n murder  on the  day of April  9, 1994 or in  the  week  thereafter,  there  is no \n evidence that she knew of the incident prior to interacting with detectives \n on the morning of April 9.  \n\n 59  No. 17‐1859\n\n 1 failure to disclose the statements he claims that Walker actually did \n\n 2 make  during  that  interview.    See  App’x  62  ¶¶  183–200;  App’x  93  ¶ \n\n 3 379.    Most  principally,  Bellamy  challenges  the  detectives’  failure  to \n\n 4 disclose what Walker testified were her unequivocal statements that \n\n 5 Bellamy  was  not  the  person  she  saw  on  the  morning  of  Abbott’s \n\n 6 murder, as well as Walker’s refusal to sign Detective Solomeno’s DD‐\n\n 7 5 because the contents, in her view, were not true.  \n\n 8 The Defendants did not seek summary judgment on this claim, \n\n 9 see App’x 734–38, and therefore it was error for the district court to \n\n10 have  dismissed  it  without  providing  Bellamy  “notice  and  a \n\n11 reasonable time to respond.”  Fed. R. Civ. P. 56 (f)(2).  This is sufficient \n\n12 by itself to vacate the district court’s dismissal of this claim.   \n\n13 We would arrive at the same outcome even if the Defendants \n\n14 had sought summary judgment on this claim.  For similar reasons that \n\n15 we concluded that Bellamy has raised a triable issue of fact as to his \n\n16 evidence  fabrication  claim  premised  on  the  DD‐5  following  the \n\n17 Walker interview, we conclude that Bellamy has raised a triable issue \n\n18 as  to  the  related  Brady  claim.    Walker’s  testimony  raises  a  genuine \n\n19 disputed issue as to whether Walker affirmatively told the detectives \n\n20 that  the  individual  she  saw  was  not  Bellamy,  and  both  detectives \n\n21 admit that Walker refused to sign the DD‐5 and that they did not tell \n\n22 ADA  Guy  that  she  had  so  refused.    If  her  denial  existed  from  the \n\n23 outset (which we hold to be a jury question), then its disclosure would \n\n 60  No. 17‐1859\n\n 1 have  weakened  ADA  Guy’s  examination  while  permitting  the \n\n 2 criminal defense team to refresh Walker’s recollection as to whether \n\n 3 earlier she firmly denied seeing Bellamy, a fact that did not come out \n\n 4 at trial.  Thus, this claim even if it had been challenged at summary \n\n 5 judgment, should not have been dismissed. \n\n 6 II. Monell Claims Against the City of New York  \n\n 7 We now turn to whether the district court properly dismissed \n\n 8 Bellamy’s  §  1983  claims  against  the  City  of  New  York.    Although \n\n 9 § 1983 subjects only “person[s]” to liability, 42 U.S.C. § 1983, Monell \n\n10 established that “a municipality [such as the City of New York] is a \n\n11 person within the meaning of Section 1983,” Vives v. City of New York, \n\n12 524 F.3d 346, 350 (2d Cir. 2008).  To establish liability under Monell, a \n\n13 plaintiff must show that he suffered the denial of a constitutional right \n\n14 that was caused by an official municipal policy or custom.  See Wray \n\n15 v. City of New York, 490 F.3d 189, 195 (2d Cir. 2007).   \n\n16 As  relevant  here,  Bellamy  proffers  two  theories  of  Monell \n\n17 liability:  (i)  the  prosecution  failed  to  disclose  the  full  relocation \n\n18 benefits Sanchez received from the QCDA’s office, a Brady violation \n\n19 that was caused by a deliberate information barrier imposed by the \n\n20 QCDA  that  purposefully  kept  prosecutors  unaware  of  the  full \n\n21 benefits  received  by  witnesses  in  its  witness  protection  program \n\n22 (“WPP”); and (ii) ADA Guy’s improper summation was a due process \n\n23 violation  caused  by  the  QCDA  office’s  failure  to  discipline \n\n 61  No. 17‐1859\n\n1 summation  misconduct.28    The  City  challenges  Bellamy’s  Monell \n\n2 claims  on  two  general  grounds:  (i)  the  City  is  not  responsible  as  a \n\n3 matter of law under Monell for the alleged policies of the QCDA; and \n\n4 (ii) regardless, Bellamy did not sufficiently establish underlying due \n\n5 process  violations  to  withstand  summary  judgment.29    We  disagree \n\n6 with  both  contentions  and  vacate  the  district  court’s  dismissal  of \n\n7 Bellamy’s Monell claims. \n\n\n\n\n  Bellamy also pled a claim that the QCDA’s office failed to discipline \n 28\n\n Brady  violations,  specifically  as  to  its  prosecutors’  failure  to  diligently \n search  out  the  benefits  received  by  its  witnesses.    Defendants  did  not \n specifically move for summary judgment on this claim and the district court \n did not address it, which means that its dismissal was improper.  See Fed. \n R. Civ. P. 56(f)(2).  Bellamy affirmed on appeal his intention to proceed on \n this  claim,  yet  Defendants  did  not  address  it  in  their  brief.    See  Br.  of \n Appellant 48 n.15; Reply Br. of Appellant 11 n.5.  We decline to address this \n claim in the first instance. \n  Whether the QCDA in fact had the challenged policies is not at issue \n 29\n\n before us.  Following the denial of the Defendants’ motion to dismiss, the \n district  court  bifurcated  discovery  on  Bellamy’s  non‐Monell  and  Monell \n claims  by  allowing  the  completion  of  non‐Monell  discovery  but  limiting \n Monell  discovery  to  “the  question  whether  any  of  the  plaintiff’s  federal \n constitutional rights were violated by the actions of the district attorney’s \n office.”    Dkt.  No.  52.    Although  the  parties  subsequently  stipulated  to \n proceed  to  full  discovery  on  Bellamy’s  Monell  claims,  Dkt.  No.  112, \n including  as  to  the  existence  of  the  alleged  policies,  the  district  court \n subsequently  re‐imposed  the  discovery  stay  before  Bellamy  took  any \n Monell depositions pending resolution of the parties’ summary judgment \n motions.    See  Dkt.  No.  152.    Consequently,  Bellamy  has  yet  to  have  full \n discovery as to the existence of the alleged policies, and the City makes no \n argument regarding the existence of the policies on appeal.  \n\n 62  No. 17‐1859\n\n 1 a. The City of New York’s Liability Under Monell for the \n 2 Alleged Policies of the QCDA’s Office \n\n 3 The City argues that it cannot be held liable as a matter of law \n\n 4 for  any  constitutional  harms  inflicted  by  the  alleged  policies  of  the \n\n 5 QCDA’s office that give rise to Bellamy’s Monell claims because those \n\n 6 were not policies for which the City is responsible.  The district court \n\n 7 agreed, but we do not. \n\n 8 Monell  liability  attaches  only  where  an  infringement  of \n\n 9 constitutional  rights  is  caused  by  a  local  government  policy.    See \n\n10 Outlaw v. Hartford, 884 F.3d 351, 372–73 (2d Cir. 2018).  In searching \n\n11 for the proper local government that is subject to liability on a given \n\n12 Monell claim we look for “those official or governmental bodies who \n\n13 speak  with  final  policymaking  authority  . . .  concerning  the  action \n\n14 alleged to have caused the particular . . . violation at issue.”  Jett v. \n\n15 Dallas Ind. Sch. Dist., 491 U.S. 701, 737 (1989).  The issue for us is thus \n\n16 whether the City of New York is the “final policymaking authority” \n\n17 in  relation  to  the  alleged  QCDA  policies  at  issue  here:    the  WPP \n\n18 information  barrier  and  the  failure  to  discipline  summation \n\n19 misconduct.    The  City  argues,  as  the  district  court  concluded,  that \n\n20 pursuant  to  Van  de  Kamp  v.  Goldstein,  555  U.S.  335  (2009),  the \n\n21 challenged conduct of the QCDA’s office is necessarily a function of \n\n22 state  policies,  and  therefore  the  City  may  not  be  subject  to  Monell \n\n23 liability as a matter of law.  We think this argument overextends Van \n\n 63  No. 17‐1859\n\n 1 de  Kamp,  a  case  assessing  the  distinct  doctrine  of  prosecutorial \n\n 2 immunity, and that our controlling precedent plainly establishes that \n\n 3 the  City  may  be  held  liable  under  Monell  for  the  alleged  QCDA \n\n 4 policies at issue. \n\n 5 On  numerous  occasions  we  have  been  called  upon  to  assess \n\n 6 how  plaintiffs  may  pursue  claims  under  Monell  that  allege  that \n\n 7 policies  of  prosecutors’  offices  led  to  infringements  of  their \n\n 8 constitutional  rights.    To  adequately  explain  why  we  conclude  that \n\n 9 the City is a proper defendant with respect to Bellamy’s Monell claims \n\n10 here, a brief review of these cases will be helpful.     \n\n11 In  Baez  v.  Hennessy,  853  F.2d  73  (2d  Cir.  1988),  Baez  sued  an \n\n12 Onondaga County prosecutor, and the county under Monell, after the \n\n13 prosecutor improperly indicted Baez based on an erroneous reading \n\n14 of  a  grand  jury  vote  sheet.    We  affirmed  dismissal  of  both  claims, \n\n15 concluding  that  the  prosecutor  was  protected  by  absolute \n\n16 prosecutorial immunity and, relevant here, that the county was not a \n\n17 proper  party  for  a  Monell  claim.    As  to  the  latter  conclusion,  we \n\n18 reasoned  that  “[w]hen  prosecuting  a  criminal  matter,  a  district \n\n19 attorney  in  New  York  State,  acting  in  a  quasi‐judicial  capacity, \n\n20 represents the State and not the county.”  Id. at 77.  And because the \n\n21 prosecutor was representing the state, the county could not be held \n\n22 legally  responsible  for  injuries  that  the  prosecutor  had  caused.  \n\n23 Although  we  have  never  questioned  the  conclusion  in  Baez  that  a \n\n 64  No. 17‐1859\n\n 1 prosecutor  is  a  state  rather  than  a  local  representative  “[w]hen \n\n 2 prosecuting  a  criminal  matter,”  id.,  our  subsequent  cases  have \n\n 3 narrowed Baez in significant and relevant ways. \n\n 4 We began to cabin Baez in Gentile v. County of Suffolk, 926 F.2d \n\n 5 142 (2d Cir. 1991), where we affirmed a judgment concluding that the \n\n 6 County of Suffolk, rather than the state, was the responsible party for \n\n 7 purposes of Monell in relation to allegations that the county’s district \n\n 8 attorney’s  office  had  a  policy  of  ignoring  police  misconduct.    We \n\n 9 rejected the argument that, under Baez, the district attorney’s office’s \n\n10 conduct was a function of state rather than county policies because, \n\n11 unlike  in  Baez,  “the  County’s  liability  is  based  not  upon  a  specific \n\n12 decision of the District Attorney to prosecute but upon the County’s \n\n13 long  history  of  negligent  disciplinary  practices  regarding  law \n\n14 enforcement personnel.”  Id. at 152 n.5.  \n\n15 We  then  reaffirmed  and  further  developed  the  narrowing  of \n\n16 Baez  in  Walker  v.  City  of  New  York,  974  F.2d  293  (2d  Cir.  1992), \n\n17 specifically noting that Gentile “confined Baez to challenges to specific \n\n18 decisions of the District Attorney to prosecute.”  Id. at 301 (internal \n\n19 quotation  marks  omitted).    Moreover,  Walker  also  made  plain  that \n\n20 when  a  Monell  claim  challenges  policies  of  the  City  of  New  York’s \n\n21 “constituent  counties,”  the  City  is  a  proper  defendant.    Id.; see  also \n\n22 Ramos v. City of New York, 285 A.D.2d 284, 303 (1st Dep’t 2001).  Walker \n\n23 reversed the dismissal of Monell claims against the City of New York \n\n 65  No. 17‐1859\n\n 1 that alleged that the Kings County District Attorney’s office failed to \n\n 2 adequately  train  its  prosecutors  to  turn  over  exculpatory  evidence \n\n 3 and not to suborn perjury.  We concluded that in such an instance, \n\n 4 notwithstanding  Baez,  “the  district  attorney  is  a  municipal \n\n 5 policymaker,”  because  in  making  decisions  other  than  whether  to \n\n 6 prosecute  the  “district  attorney  acts  as  the  manager  of  the  district \n\n 7 attorney’s office,” which, we concluded, is a municipal function.  974 \n\n 8 F.3d at 301.  In Ying Jing Gan v. City of New York, 996 F.2d 522 (2d Cir. \n\n 9 1993), we reaffirmed Walker and clarified that a county prosecutor’s \n\n10 actions are a function of state policies, rather than city policies, only \n\n11 where plaintiff’s “claims center[] . . . on decisions whether or not, and \n\n12 on what charges, to prosecute,” and not where those claims focus “on \n\n13 the administration of the district attorney’s office.”  Id. at 536; see also \n\n14 Pinaud v. County of Suffolk, 52 F.3d 1139, 1153 n.14 (2d Cir. 1995). \n\n15 Subsequent  to  these  cases,  the  Supreme  Court  decided \n\n16 McMillian v. Monroe County, Alabama, 520 U.S. 781 (1997), a case that \n\n17 addressed  Monell  liability  outside  of  the  context  of  a  prosecutor’s \n\n18 office,  but  that  clarified  the  scope  of  analysis  for  Monell  claims \n\n19 generally.  The Court held that Monroe County, Alabama was not the \n\n20 relevant  policymaker  for  purposes  of  a  Monell  claim  that  asserted \n\n21 unconstitutional conduct of a Monroe County sheriff.   How the Court \n\n22 arrived at that conclusion is significant: it examined Alabama law in \n\n23 detail and concluded that the state was the relevant final policymaker \n\n 66  No. 17‐1859\n\n 1 because it had sufficient authority over the sheriff’s specific functions \n\n 2 at issue.  Id. at 786.  The Court relied heavily on the Alabama state \n\n 3 constitution,  for  example,  which  evinced  “‘the  framers’  intent  to \n\n 4 ensure that sheriffs be considered executive officers of the state.’”  Id. \n\n 5 at 789 (quoting Parker v. Amerson, 519 So.2d 442, 444 (Ala. 1987)).  The \n\n 6 relevant  lesson  from  McMillian  is  plain:    because  “the  States  have \n\n 7 wide  authority  to  set  up  their  state  and  local  governments  as  they \n\n 8 wish,” a search for the “final policymaking authority” under Monell \n\n 9 “is dependent on an analysis of state law.”  Id. at 786, 795. \n\n10 In Myers v. County of Orange, 157 F.3d 66 (2d Cir. 1998), in light \n\n11 of  McMillian’s  directive  to  delve  into  state  law  to  ascertain  a  final \n\n12 policymaker  for  purposes  of  Monell  liability,  we  revisited  our  cases \n\n13 discussed above that broadly applied Monell to prosecutors’ offices.  \n\n14 There,  we  addressed  Monell  claims  brought  against  the  New  York \n\n15 County  of  Orange  that  alleged  that  the  county’s  district  attorney’s \n\n16 office  had  an  unconstitutional  policy  of  refusing  to  entertain  cross‐\n\n17 complaints  by  complaining  witnesses.    Id.  at  69.    After  reviewing  a \n\n18 wealth of New York statutory and case law (which our earlier cases \n\n19 had  not  done),  we  reaffirmed  our  earlier  conclusions  that  “[u]nder \n\n20 New  York  law,  DAs  and  ADAs  are  generally  presumed  to  be  local \n\n21 county officers, not state officers,” and reiterated once again that Baez \n\n22 was a “narrow exception . . . [for] when a prosecutor makes individual \n\n23 determinations about whether to prosecute.”  Id. at 76–77. \n\n 67  No. 17‐1859\n\n 1 Because  we  have  never  doubted  the  rule  stemming  from  the \n\n 2 line of cases extending from Gentile and Walker to Myers, we have been \n\n 3 consistent in holding that the actions of county prosecutors in New \n\n 4 York  are  generally  controlled  by  municipal  policymakers  for \n\n 5 purposes  of  Monell,  with  a  narrow  exception  emanating  from  Baez \n\n 6 being  the  decision  of  whether,  and  on  what  charges,  to  prosecute.  \n\n 7 Thus, in this case, the rule from these cases requires the conclusion \n\n 8 that  the  conduct  Bellamy  challenges  is  a  result  of  municipal  rather \n\n 9 than  state  policymaking.    The  City  does  not  dispute  this  reasoning \n\n10 based  on  our  precedents,  informed  along  the  way  by  the  Court’s \n\n11 decision in McMillian.  The City’s sole contention is that our Walker \n\n12 line of cases was implicitly abrogated by the Supreme Court’s 2009 \n\n13 decision in Van de Kamp, “requir[ing] a different boundary between \n\n14 prosecutorial  and  administrative  functions  than  the  one  [we  have] \n\n15 previously set forth.”  Br. of Appellees at 67.  We disagree.  \n\n16 In  Van  de  Kamp,  plaintiff  Goldstein  obtained  a  vacatur  of  his \n\n17 state  murder  conviction  by  a  grant  of  federal  habeas  corpus  on  the \n\n18 ground that the prosecution failed to disclose to the defense that they \n\n19 had  offered  a  reduced  sentence  to  a  witness  that  provided  critical \n\n20 inculpatory testimony.  555 U.S. at 339.  As relevant here, Goldstein \n\n21 then filed a civil § 1983 claim against his prosecutors’ supervisors (as \n\n22 individuals),  arguing  that  they  failed  to  train  or  supervise  their \n\n23 prosecutors to prevent violations of the duty to disclose impeachment \n\n 68  No. 17‐1859\n\n 1 material.  Id. at 340.  The defendants moved to dismiss on the basis of \n\n 2 absolute  prosecutorial  immunity,  an  argument  the  district  court \n\n 3 rejected  on  the  ground  that  prosecutors  are  entitled  to  absolute \n\n 4 immunity  only  for  “prosecutorial”  functions,  not  “administrative” \n\n 5 ones, and that the failure‐to‐train allegations fell in the latter category.  \n\n 6 Id.  The Court of Appeals affirmed, 481 F.3d 1170 (9th Cir. 2007), but \n\n 7 the  Supreme  Court  reversed.    It  disagreed  with  the  lower  courts’ \n\n 8 conclusions  that  a  prosecutor  is  not  entitled  to  immunity  simply \n\n 9 because  her  challenged  conduct  can  be  labeled  “administrative.”  \n\n10 Rather,  the  inquiry  is  whether  the  prosecutor’s  conduct \n\n11 (administrative  or  otherwise)  was  “directly  connected  with  the \n\n12 conduct of a trial.”  555 U.S. at 344.  If so, the Court concluded, the \n\n13 conduct falls within the traditional immunity offered to prosecutors \n\n14 under long‐standing notions of federal common law. \n\n15 Although Van de Kamp said nothing about Monell or municipal \n\n16 liability, the City argues that Van de Kamp affects how Monell claims \n\n17 can proceed against prosecutors’ offices specifically.  Its argument is \n\n18 as follows.  In the Walker line of cases, we concluded that inherently \n\n19 prosecutorial  functions  (i.e.,  decisions  whether  to  prosecute)  are \n\n20 controlled by state policies for purposes of Monell, and other functions \n\n21 of the prosecutor are controlled by municipal policies.  For example, in \n\n22 Baez, the act of indicting based on a misread grand jury verdict form \n\n23 was  inherently  prosecutorial  and  therefore  a  state  function,  but,  in \n\n 69  No. 17‐1859\n\n 1 Walker, the failure to train on Brady obligations related to the district \n\n 2 attorney’s management of the office, and we therefore concluded that \n\n 3 was  a  municipal  function.    Consequently,  the  argument  goes,  our \n\n 4 Monell cases have drawn separate circles around “prosecutorial” and \n\n 5 “managerial” functions, with the former circle being state‐controlled \n\n 6 functions and the latter municipally‐controlled ones.  The argument \n\n 7 then goes that although our cases have narrowed the “prosecutorial” \n\n 8 circle  such  that  it  includes  only  the  prosecutor’s  decision  to  bring \n\n 9 charges, Van de Kamp expanded the circle of prosecutorial functions \n\n10 to  include  a  failure  to  train  on  Brady  obligations  (which,  the  City \n\n11 argues,  is  akin  to  Bellamy’s  arguments  here).    Thus,  the  argument \n\n12 concludes, because Bellamy’s claims pertain to conduct that now falls \n\n13 within  the  “prosecutorial”  circle,  and  New  York  concludes \n\n14 “prosecutorial”  conduct  is  a  state  function,  the  conduct  supporting \n\n15 Bellamy’s  Monell  claims  must  be  a  state  rather  than  a  municipal \n\n16 function.  We are unpersuaded. \n\n17 The  key  flaw  in  the  City’s  argument  is  its  unsupported \n\n18 assumption  that  the  circle  demarcating  what  is  a  “prosecutorial” \n\n19 function  for  purposes  of  prosecutorial  immunity  is  necessarily  the \n\n20 same  as  the  circle  New  York  has  chosen  to  demarcate  state  versus \n\n21 local  prosecutorial  functions.    But,  the  legal  question  of  when \n\n22 immunity  should  attach  is  an  entirely  separate  inquiry  from  which \n\n23 state entity is a final policymaker for Monell.  This was the reasoning \n\n 70  No. 17‐1859\n\n 1 adopted in Goldstein v. City of Long Beach, 715 F.3d 750 (9th Cir. 2013), \n\n 2 the lower court decision that followed the Supreme Court’s remand \n\n 3 in Van de Kamp.  Although the Court had rejected plaintiff’s individual \n\n 4 claims,  the  Ninth  Circuit  was  left  to  evaluate  plaintiff’s  remaining \n\n 5 Monell claims.  The defendants argued on remand, as the City does \n\n 6 here, that “Van de Kamp determines the outcome” of the Monell claims.  \n\n 7 Id.  at  760.    The  Ninth  Circuit  rejected  the  argument  because  “the \n\n 8 inquiries of prosecutorial immunity and state or local policymaking . \n\n 9 . . are separate.”  Id.  We agree.  In contrast to the immunity inquiry, \n\n10 Monell addresses not whether certain functions can open individuals to \n\n11 liability,  but  simply  which  governmental  entity  (the  state  or  the \n\n12 municipality)  is  responsible  for  a  given  function.    And  as  we  have \n\n13 discussed,  the  Supreme  Court  has  left  no  doubt  that  state  law,  not \n\n14 federal  law,  is  responsible  for  demarcating  that  division  of \n\n15 responsibility.  The McMillian court was worried about imposing “a \n\n16 uniform,  national  characterization”  of  state  actors,  concerned  that \n\n17 “such a blunderbuss approach would ignore a crucial axiom of our \n\n18 government: the States have wide authority to set up their state and \n\n19 local governments as they wish.”  520 U.S. at 795.  Consequently, the \n\n20 responsible entity for purposes of Monell liability must be ascertained \n\n21 by looking at how the relevant state elects to allocate responsibilities \n\n22 between itself and its subdivisions.  Id. \n\n 71  No. 17‐1859\n\n 1 The City’s contention, if adopted, would turn McMillian on its \n\n 2 head: it would require courts assessing Monell claims that challenge \n\n 3 the conduct of prosecutors to consider the way in which the federal \n\n 4 system  chooses  to  immunize  prosecutors  in  determining  which \n\n 5 functions  are  state  functions  and  which  are  local  ones.    Stated \n\n 6 differently,  under  the  City’s  formulation,  we  would  no  longer  be \n\n 7 looking to the intricacies of state law to decide a Monell claim against \n\n 8 a prosecutor’s office, as we did in Myers (at the express direction of \n\n 9 McMillian),  but  would  instead  look  to  Van  de  Kamp,  a  decision \n\n10 exclusively assessing federal common law and federal policy.30   \n\n11 Such a course would adversely affect state reliance interests as \n\n12 well:  New  York  appellate  courts  have  expressly  affirmed  our \n\n13 conclusions as to the content of New York law in Walker and Myers.  \n\n14 See Ramos, 285 A.D.2d at 303 (concluding as “firmly grounded in New \n\n15 York law,” the conclusion from Gentile, Walker, and Myers that “where \n\n16 prosecutors,  pursuant  to  policy  or  custom,  conceal  exculpatory \n\n17 evidence and commit other wrongs in order to secure a conviction, \n\n18 liability  rests  with  the  county  (or  for  New  York  City’s  constituent \n\n\n\n\n  The focus on federal common law was center stage in Van de Kamp.  \n 30\n\n See 555 U.S. at 340–41 (looking to Judge Learned Hand’s policy statements \n from “[o]ver a half century ago”); see also id. (relying on Imbler v. Pachtman, \n 424  U.S.  409  (1976),  the  Court’s  “first  opportunity  to  address  the  s  1983 \n liability of a state prosecuting officer,” which then relied on federal cases \n dating back to the mid‐19th‐century, id. at 420–22 & n.18)). \n\n 72  No. 17‐1859\n\n 1 counties,  the  City)”);  Johnson  v.  Kings  Cnty.  Dist.  Atty’s  Office,  308 \n\n 2 A.D.2d 278, 295–96 (2d Dep’t 2003) (same).   \n\n 3 Thus we conclude, consistent with our precedent, that the City \n\n 4 is the proper policymaking authority for purposes of Bellamy’s Monell \n\n 5 claims. \n\n 6 b. The Alleged Constitutional Violations of the QCDA’s \n 7 Office \n\n 8 Bellamy  proffers  two  underlying  constitutional  violations  for \n\n 9 which he claims the City is responsible: (i) the non‐disclosure to the \n\n10 prosecution (and therefore to the defense) of the full benefits Sanchez \n\n11 was promised as part of her participation in the QCDA’s WPP; and \n\n12 (ii) summation misconduct by ADA Guy.  We conclude that Bellamy \n\n13 has presented sufficient evidence of both violations to withstand the \n\n14 motion for summary judgment. \n\n15 i. Benefits Promised to Sanchez \n\n16 Bellamy  contends  that  Sanchez  was  promised  significantly \n\n17 more financial support from the QCDA than the $100 and undefined \n\n18 relocation benefits to which she testified at trial.  See Trial Tr. 633–35.  \n\n19 The district court, despite appearing to acknowledge that the record \n\n20 established that Sanchez was promised substantially more than that \n\n21 to  which  she  testified,  rejected  the  claim  because  the  promised \n\n22 “benefits did not arise until after the plaintiff’s trial, and did not affect \n\n23 the trial itself.”  2017 WL 2189528, at *40.  This was error. \n\n 73  No. 17‐1859\n\n 1 The record unmistakably raises a question of fact as to whether \n\n 2 Sanchez  was  promised,  prior  to  her  testifying,  substantially  more \n\n 3 than  she  ultimately  disclosed  during  her  testimony.    Specifically, \n\n 4 there  is  evidence  in  the  record  that  Sanchez  was  promised,  before \n\n 5 trial,  that  the  QCDA’s  office  would  relocate  her,  and,  in  doing  so, \n\n 6 would  pay  for  her  first  month’s  rent,  last  month’s  rent,  security \n\n 7 deposit, and a broker fee, totaling $2,800.  See Sanchez Dep. Tr. 79–97, \n\n 8 147–148; Dkt. No. 193‐1 at 291 (Sanchez testimony at the initial § 440 \n\n 9 proceeding).    Daniel  Cox,  the  WPP  administrator  who  worked \n\n10 directly  with  Sanchez,  testified  at  his  deposition  that  his  office \n\n11 generally  referred  to  this  as  “Seed  Money,”  and  that  he  would  tell \n\n12 program  participants  “early  when  you’re  starting  to  have \n\n13 conversations” that they would be receiving it.  Cox Dep. Tr. 43.  Cox \n\n14 clarified that he would tell participants about the seed money “at [the] \n\n15 first meeting,” which, as to Sanchez, would have been on November \n\n16 28, 1995, prior to her testifying.  Cox Dep. Tr. 100–01; but see Mansfield \n\n17 Dep.  Tr.  75–76  (“of  course”  we  would  make  no  specific  promises \n\n18 during the orientation).  In any event, Corporation counsel conceded \n\n19 at oral argument before us that a reasonable jury could conclude on \n\n20 this evidence that Cox promised Sanchez the seed money prior to her \n\n21 testifying.    Oral  Arg.  Rec.  at  36:04.    And,  ADA  Guy  testified  at  his \n\n22 deposition  that  he  was  never  aware  of  the  promised  seed  money, \n\n 74  No. 17‐1859\n\n 1 either at the time of trial or even at the time of his deposition in this \n\n 2 case.  Guy Dep. Tr. 138–39. \n\n 3 As corporation counsel’s concession makes plain, the City does \n\n 4 not seriously dispute any of the above and argues only that Bellamy \n\n 5 was not prejudiced by the lack of disclosure because the benefits that \n\n 6 were disclosed at trial provided a sufficient basis for defense counsel \n\n 7 to attack Sanchez’s credibility.  We disagree.  The potential for witness \n\n 8 bias is of course greater when the amount to be received is $2,800 as \n\n 9 opposed  to  $100  (4  x  $25/day),  particularly  for  a  witness  of  limited \n\n10 financial  means  like  Sanchez,  see  App’x  1622.    Further,  the  actual \n\n11 benefit promised was substantially larger than that to which Sanchez \n\n12 testified,  which  would  have  allowed  for  a  heightened  attack  on \n\n13 Sanchez’s truthfulness.  Moreover, ADA Guy both conceded that the \n\n14 promise of $2,800 of seed money was Brady material and explained \n\n15 why  the  information  was  particularly  probative  in  this  case:  “[The] \n\n16 dollar  amount  and  total  benefit  amount  is  at  odds  with  [Sanchez’s \n\n17 trial]  testimony.    So  it  might  affect  her  credibility  and  [if  I  were \n\n18 defense counsel] I might be able to make some use of that in asking \n\n19 the jury to disregard her or to at least challenge her credibility.”  Guy \n\n20 Dep.  Tr.  138–41.    Finally,  the  problem  was  exacerbated  when  ADA \n\n21 Guy, in his summation, noted the absence of evidence supporting the \n\n22 defense’s contention that Sanchez had a motive to lie out of bias.  See \n\n23 Trial Tr. 1139 (“Why would she come in and lie about the defendant?  \n\n 75  No. 17‐1859\n\n 1 Is there any evidence that she had any motivation to come in and lie \n\n 2 about the defendant?”); Trial Tr. 1144 (“There is no evidence she is a \n\n 3 liar.”). \n\n 4 We therefore conclude that Bellamy raised a material issue of \n\n 5 fact as to whether his Brady rights were violated by the QCDA’s non‐\n\n 6 disclosure of the full scope of benefits promised to Sanchez prior to \n\n 7 her testimony.  And, in light of our conclusion that the City of New \n\n 8 York may be held liable for this conduct, we vacate the district court’s \n\n 9 dismissal of this Monell claim.  \n\n10 ii. ADA Guy’s Summation \n\n11 Bellamy  contends  that  ADA  Guy  made  numerous  improper \n\n12 remarks  during  his  summation  sufficient  to  render  Bellamy’s \n\n13 subsequent  conviction  a  denial  of  due  process.    The  district  court \n\n14 disagreed, largely on its conclusion that ADA Guy’s “comments were \n\n15 garden variety summation comments.”  2017 WL 2189528, at *41.  We \n\n16 disagree and conclude that the impact of the summation on the trial \n\n17 presents a jury question. \n\n18 In United States v. Certified Environmental Services, Inc., 753 F.3d \n\n19 72 (2d Cir. 2014), we discussed the relevant standard: \n\n20 When reviewing claims of prosecutorial misconduct \n21 based on inappropriate remarks in the Government’s \n22 .  .  .  summation[],  we  will  reverse  if  the  misconduct \n23 caused substantial prejudice by so infecting the trial \n24 with unfairness as to make the resulting conviction a \n25 denial  of  due  process.    In  assessing  whether \n\n 76  No. 17‐1859\n\n 1 prosecutorial  misconduct  caused  ‘substantial \n 2 prejudice,’  this  Court  has  adopted  a  three‐part  test, \n 3 which  considers  the  severity  of  the  misconduct,  the \n 4 measures  adopted  to  cure  the  misconduct,  and  the \n 5 certainty of conviction absent the misconduct. \n\n 6 Id. at 95 (internal quotation marks and citations omitted).  \n\n 7 Bellamy contended at summary judgment that ADA Guy made \n\n 8 fourteen  improper  summation  remarks.    App’x  1969–72.    Bellamy \n\n 9 contends these remarks were sufficiently improper to entitle him to \n\n10 relief under § 1983, even though his counsel did not object to them \n\n11 during  trial  (or  afterwards).    While  we  are  not  persuaded  that  the \n\n12 majority of the remarks identified by Bellamy were either improper \n\n13 or could have affected the trial, we believe that certain remarks were \n\n14 sufficiently  problematic  to  require  that  they  be  assessed  by  a  jury \n\n15 (despite the absence of a contemporaneous objection by trial counsel).  \n\n16 The  most problematic  is  Bellamy’s  contention  that  ADA Guy \n\n17 told the jury near the end of his summation: “I know who committed \n\n18 the murder.”  Trial Tr. 1149.  This statement was clearly improper and \n\n19 severely prejudicial if it was made.  “It is unprofessional conduct for \n\n20 the prosecutor to express his or her personal belief or opinion as to \n\n21 the . . . evidence or guilt of the defendant.” United States v. Modica, 663 \n\n22 F.2d 1173, 1178 (2d Cir. 1981) (per curiam) (quoting ABA Standards for \n\n23 Criminal  Justice,  Standard  3‐5.8(b));  see  also  U.S.  v.  Burse,  531  F.2d \n\n24 1151,  1154–55  (2d  Cir.  1976)  (a  prosecutor  may  not  give  “the \n\n 77  No. 17‐1859\n\n 1 impression that the government ha[s] within its possession evidence \n\n 2 of [the defendant’s] guilt which had not been given the jury”); United \n\n 3 States v. Rivera, 22 F.3d 430, 437–38 (2d Cir. 1994) (“use of the personal \n\n 4 pronoun  ‘I’  .  .  .  tends  to  [improperly]  make  an  issue  of  [the \n\n 5 prosecution’s]  own  credibility”  (internal  quotation  marks  and \n\n 6 alterations  omitted)).    We  have  concluded  that  the  “policies \n\n 7 underlying this proscription go to the heart of a fair trial.”  Modica, \n\n 8 663 F.2d at 1178.   In short, it is the height of summation misconduct \n\n 9 for  a  prosecutor  to  argue  to  the  jury  his  personal  opinion  as  to  a \n\n10 defendant’s guilt. \n\n11 Defendants do not dispute that had the statement been made it \n\n12 would  have  been  serious  misconduct;  rather,  they  point  to  ADA \n\n13 Guy’s  deposition  testimony  denying  that  he  made  the  remark  and \n\n14 contending  that  there  was  simply  a  transcription  error  in  the  trial \n\n15 record.  Guy Dep. Tr. 154–55, 232 (stating that he said “[you] know \n\n16 who  committed  the  murder”).    But,  on  a  motion  for  summary \n\n17 judgment, we must draw all inferences in favor of the non‐movant, \n\n18 which  requires  us  to  accept  the  inference  that  the  trial  transcript \n\n19 accurately depicts what occurred at trial. \n\n20 Regardless,  that  remark,  if  it  occurred,  does  not  stand  alone.  \n\n21 Also improper was ADA Guy’s comment, again made near the end \n\n22 of his summation, that “you [Bellamy] are not going to get away with \n\n23 it, not this time.” Trial Tr. 1150 (emphasis added).  Viewed in Bellamy’s \n\n 78  No. 17‐1859\n\n 1 favor,  this  statement  permitted  the  inference  that  Bellamy  had \n\n 2 committed  other  uncharged crimes at  other  times  (murder,  no  less, \n\n 3 the crime for which Bellamy was on trial) and that the government \n\n 4 had  evidence  of  those  crimes  to  which  the  jury  was  not  privy.    See \n\n 5 United States v. Farmer, 583 F.3d 131, 146 (2d Cir. 2009) (improper to \n\n 6 make  remarks  “suggestive  of  a  [defendant’s]  criminal  disposition” \n\n 7 where  that  remark  has  no  otherwise  “legitimate  relationship  to  the \n\n 8 crimes charged,” especially where the remark hints at “a propensity \n\n 9 to commit particularly heinous crimes,” such as murder, “including \n\n10 the  very  offenses  charged  in  the  indictment”  (internal  quotation \n\n11 marks  omitted));  Burse,  531  F.2d  at  1155;  see  also  Manning  v.  Artuz, \n\n12 1996  WL  294359,  at  *3,  *5  (E.D.N.Y.  May  29,  1996)  (prosecutor’s \n\n13 summation statement that “the gun recovered by the police was the \n\n14 ‘tool  of  [Petitioner’s]  trade’  .  .  .  overstepped  the  bounds  of  proper \n\n15 summation”).  \n\n16 ADA Guy’s summation contained other improper remarks.  In \n\n17 arguing  to  the  jury  that  the  evidence  showed  that  Carter  identified \n\n18 Bellamy at the lineup, ADA Guy told the jury that they “don’t have \n\n19 to take my word” on the subject, Trial Tr. 1137 (emphasis added), but, \n\n20 as discussed, a prosecutor may not inform the jury either way what \n\n21 his “word” is.  See Modica, 663 F.2d at 1178–79.  Also crossing the line \n\n22 was ADA Guy’s rhetorical question to the jury, in a case where the \n\n23 government  put  in  no  evidence  of  motive:  “Where  is  there  proof \n\n 79  No. 17‐1859\n\n 1 defendant  had  no  motive  to  kill  somebody?”    Trial  Tr.  1133.    Of \n\n 2 course,  Bellamy  was  under  no  obligation  to  prove  the  absence  of  a \n\n 3 motive and it is difficult to see how a defendant could possibly do so.  \n\n 4 At another point, ADA Guy remarked that Bellamy “is a liar,” Trial \n\n 5 Tr.  1148,  a  comment  we  have  found  deserving  of  admonishment, \n\n 6 especially  where,  as  here,  “such  characterization  is  applied  to  a \n\n 7 [criminal]  defendant  .  .  .  [where]  the  risk  of  prejudice  is  greater.”  \n\n 8 United States v. Leeds, 457 F.2d 857, 860–61 (2d Cir. 1972).   \n\n 9 The  trial  court  took  no  “curative  measures”  to  obviate  the \n\n10 harms from these improper comments, see United States v. Espinal, 981 \n\n11 F.2d  664,  666–67  (2d  Cir.  1992),  but  the  reason  for  that  is  clear: \n\n12 Bellamy’s  defense  counsel  did  not  object  to  them  nor  subsequently \n\n13 seek a curative instruction.31  A defense counsel’s failure to object to \n\n14 an improper summation remark undercuts the probative value of the \n\n15 subsequent lack of a curative measure.  See United States v. Melendez, \n\n16 57  F.3d  238,  242  (2d  Cir.  1995)  (generally,  “the  failure  to  request \n\n17 specific  instructions  before  the  jury  retires  will  limit  the  defense’s \n\n18 ability to complain about the relative lack of curative measures for the \n\n19 first  time  on  appeal”);  but  see  id.  (a  “failure  to  request  specific \n\n\n\n\n  Defense counsel objected three times during ADA Guy’s summation, \n 31\n\n but not with respect to any of the comments we identify above.  See Trial \n Tr. 1127, 1129, 1143. \n\n 80  No. 17‐1859\n\n 1 instructions may be overlooked where the prosecutor’s misconduct is \n\n 2 so prejudicial that no instruction could mitigate its effects”).32  \n\n 3 But,  “[c]urative  measures  constitute  only  one  part  of  the \n\n 4 analysis.”    Espinal,  981  F.2d  at  667.    As  identified  above,  the  third \n\n 5 component of our due process test requires, notwithstanding the lack \n\n 6 of an objection from defense counsel, that we still ask how confident \n\n 7 we are that the criminal defendant would have been convicted absent \n\n 8 the summation misconduct.  We must as a consequence take stock of \n\n 9 the  realities  of  the  trial  in  which  the  summation  misconduct  due \n\n10 process violations are said to occur.  For example, in Farmer, we found \n\n11 that  the  prosecutor’s  “flagrant  abuse”  through  his  summation \n\n12 remarks,  not  objected  to  by  defense  counsel,  was  insufficient  to \n\n13 warrant  reversal  of  one  of  the  defendant’s  convictions  because  the \n\n14 defendant’s  guilt  on  that  charge  “was  supported  by  such \n\n15 overwhelming  evidence  that  conviction  was  a  certainty,”  but  the \n\n16 improper  summation  remarks  did  warrant  reversal  of  defendant’s \n\n17 conviction on a different charge for which the evidence “was far less \n\n18 conclusive.”  583 F.3d at 147–48.  As we concluded, “the determinative \n\n19 factor [was] the weight of the evidence.”  Id. at 147. \n\n\n\n\n  We also note that Bellamy did not raise this summation misconduct \n 32\n\n issue on direct appeal or as part of his habeas corpus petition.  But, there is \n no general exhaustion requirement under § 1983.  See Roach v. Morse, 440 \n F.3d 53, 56 (2d Cir. 2006). \n\n 81  No. 17‐1859\n\n 1 If the trial evidence here had clearly pointed to Bellamy’s guilt, \n\n 2 we  would  have  no  hesitation  in  rejecting  his  improper  summation \n\n 3 claim on this record.   See Espinal, 981 F.2d at 666–67; Farmer, 583 F.3d \n\n 4 at  147–48.    The  bar  for  concluding  that  unobjected  to  summation \n\n 5 remarks  amount  to  a  due  process  violation  is  appropriately  high.  \n\n 6 And  we  also  acknowledge  that  as  an  appellate  court  we  should  be \n\n 7 wary of “cherry‐picking” improper yet isolated remarks from a cold \n\n 8 record made during a lengthy summation, especially where defense \n\n 9 counsel,  who  witnessed  the  statements  live  in  court,  offered  no \n\n10 contemporaneous objection.  But here, it is difficult to conclude other \n\n11 than  that  Bellamy’s  criminal  trial  existed  at  the  cusp  of  reasonable \n\n12 doubt.  Thus we conclude that a civil jury evaluating Bellamy’s due \n\n13 process  claim  could  reasonably  find  that  ADA  Guy’s  improper \n\n14 remarks pushed this case over the line.   \n\n15 Heading  into  summations,  the  QCDA’s  office  had  major \n\n16 misgivings about the quality of its case.  See generally People v. Bellamy, \n\n17 84 A.D.3d 1260, 1262 (2d Dep’t 2011) (stating that there was “less than \n\n18 overwhelming  evidence  against  [Bellamy]”);  see  also  App’x  2088 \n\n19 (documenting  the  jury’s  prolonged  and  difficult  deliberations).  \n\n20 Discovery revealed that ADA Guy himself, after the close of evidence, \n\n21 thought  the  case  had  “sort  of  crumbled  in  [his]  hand,”  and  that  he \n\n22 “needed  something  else.”    App’x  1715.    ADA  Guy  met  with  other \n\n23 prosecutors, including his bureau chief, prior to giving his summation \n\n 82  No. 17‐1859\n\n 1 because they all “sensed there was a problem going on.”  Guy Dep. \n\n 2 Tr. 44–45, 192–93.  And ADA Guy admitted during his deposition that \n\n 3 although earlier he thought he had a strong case against Bellamy, by \n\n 4 the time the evidence had closed “it was closer to being a weak case \n\n 5 for the prosecution.”  Guy Dep. Tr. 46.  In his deposition, ADA Guy \n\n 6 acknowledged  that  “[t]here  was  also  enough  weakness  that  a  jury \n\n 7 could’ve said, no, we have a reasonable doubt.”  Guy Dep. Tr. 193.  \n\n 8 Indeed,  “[t]he  general  consensus,”  ADA  Guy  acknowledged,  “was \n\n 9 that [he] needed a very strong summation in order to sort of salvage \n\n10 this case. . . .  I thought I was in trouble.”  App’x 1718.   \n\n11 ADA Guy then delivered his “very strong summation,” App’x \n\n12 1718, but one that was supported by what our cases have consistently \n\n13 described  as  improper  remarks  that  tend  to  sway  the  jury  in \n\n14 constitutionally impermissible ways.  The principal statements with \n\n15 which  we  take  issue  were  given  at  the  very  end  of  ADA  Guy’s \n\n16 summation, which, in New York, follows the defense summation and \n\n17 is not subject to rebuttal.  Thus, if the transcript is to be believed, the \n\n18 nearly final words the jury heard before entering deliberations were \n\n19 ADA Guy’s statement that he, as the prosecutor, knew that Bellamy \n\n20 killed Abbott and that Bellamy was not going to get away with it, “not \n\n21 this  time.”    Viewed  in  this  context,  and  considering  the  other \n\n22 inappropriate  comments  we  have  identified,  we  conclude  that \n\n23 Bellamy has raised a triable issue of fact as to whether ADA Guy’s \n\n 83  No. 17‐1859\n\n1 summation “so infect[ed] [Bellamy’s] trial with unfairness as to make \n\n2 [his]  resulting  conviction  a  denial  of  due  process.”    Certified  Env. \n\n3 Servs., Inc., 753 F.3d at 95. \n\n4 CONCLUSION \n\n5 For the foregoing reasons, we VACATE in part and AFFIRM in \n\n6 part  the  judgment  of  the  district  court  and  REMAND  for  further \n\n7 proceedings consistent with this opinion.33 \n\n\n\n\n   Bellamy  requests  that  we  assign  this  case  on  remand  to  a  different \n 33\n\n district judge.  The request is denied.", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362636/", "author_raw": ""}, {"author": "JACOBS, Circuit Judge, dissenting", "type": "dissent", "text": "JACOBS, Circuit Judge, dissenting in part: \n I respectfully dissent insofar as the majority opinion vacates the grant of \nsummary judgment on qualified immunity for Detectives Solomeno and Gillen, \nand vacates the grant of summary judgment dismissing the Monell claims \nagainst the City of New York.  The facts of the matter are set forth meticulously \nin the majority opinion.   \n  \n I \n The majority opinion vacates the dismissal of two claims alleging \nfabrication of evidence. \n Bellamy’s “Murder” Statement.  Bellamy, who had been identified as the \nmurderer, was picked up ostensibly for drinking an alcoholic beverage in public.  \nDet. Gillen testified that, when he made the arrest, Bellamy blurted out: “This \nmust be a case of mistaken identity; someone probably accused me of murdering \nsomeone.  Why would someone accuse me of something I didn’t do?”  App’x \n290.  Bellamy denies making the statement.  On that self‐serving denial alone, the \nmajority opinion allows Bellamy’s claim of manufactured evidence to withstand \nsummary judgment.  However, it cannot be that a viable claim of fabricated \nevidence can be premised on nothing more than a defendant’s denial of a \nstatement attributed to him by the police. \n The district court’s grant of summary judgment relied in part on Jeffreys v. \nCity of New York, 426 F.3d 549, 551, 555 (2d Cir. 2005), which deemed \ninsufficient an allegation of police misconduct that is unsubstantiated and \ninconsistent.  The majority opinion distinguishes Jeffreys on the ground that \nBellamy’s explanation is “consistent and uncomplicated.”  Op. at 37.  However, \nas in Jeffreys, Bellamy’s claim is unsubstantiated and inconsistent.   \n There is less here by way of substantiation than there was in Jeffreys, in \nwhich the claim of excessive force was supported by affidavits from multiple \nfamily members, and by inferences drawn from medical records and police \nreports.  Bellamy relies on his bald assertion.  However, “[t]he non‐moving party \nmay not rely on mere conclusory allegations nor speculation, but instead must \noffer some hard evidence showing that its version of the events is not wholly \nfanciful.”  D’Amico v. City of New York, 132 F.3d 145, 149 (2d Cir. 1998). \n\n\n 1 \n\n Moreover, Bellamy’s account of his interactions with the police is \ninconsistent in critical respects.  He first denied that Det. Gillen read him \nMiranda warnings, App’x 2392, before admitting that his statements followed a \nreading of his rights, App’x 1355‐56; and he denied telling Det. Gillen that he \nwent to the C‐Town the morning of the murder, App’x 2396, before admitting \nthat too, App’x 1357.  The majority opinion, which does not take account of these \ncontradictions, deems Bellamy’s denial “uncomplicated.”  Op. at 37.  But it is \nneither complicated nor surprising that one would regret and deny an \ninculpatory remark. \n The majority argues that there is evidence “tending to support an inference \nof fabrication” because the statement did not appear in the Form DD‐5 prepared \nby Det. Gillen.  Op. at 37.  But a “lack of corroboration,” Op. at 39, does not \namount to evidence in support.  The majority opinion notes that no other police \nwitness supported Det. Gillenʹs testimony.  Then again, Bellamy did not ask \nwhen he had the chance.   \n Det. Gillen’s statement is corroborated by the notes he made in the police \ncar while taking Bellamy to the police station, and on arrival there.  App’x 290, \n2143.  Det. Gillen informed prosecutors about the “murder” statement the day it \nwas made, Trial Tr. 539‐40; and prosecutors disclosed it to Bellamy’s counsel in \ntwo notices within two weeks, see App’x 1610.  And Det. Gillen testified \nconsistently about the statement at the suppression hearing and at the trial, \nwhere he faced cross‐examination on that issue. \n Walker Interview Form DD‐5.  The majority opinion entertains the claim \nthat the Form DD‐5 memorializing Veronica Walker’s interview was fabricated.  \nHowever, Bellamy’s claim fails as a matter of law because the DD‐5 had no \nimpact on the evidentiary record before the jury.  DuFort v. City of New York, \n874 F.3d 338, 355 (2d Cir. 2017). \n It had no impact on the evidentiary record because it did not come into \nevidence.  “The manufacture of false evidence in and of itself, . . . does not impair \nanyone’s liberty, and therefore does not impair anyone’s constitutional right.”  \nZharey v. Coffey, 221 F.3d 342, 358 (2d Cir. 2000) (internal quotation marks \nomitted).  “Mere attempts to withhold or falsify evidence cannot form the basis \nfor a § 1983 claim for a violation of the right to due process when those attempts \nhave no impact on the conduct of a criminal trial.”  DuFort, 874 F.3d at 355. \n\n\n\n 2 \n\n As the majority opinion concedes, an attempt to distort the evidentiary \nrecord is irrelevant if the “jury is presented with the full universe of information, \ndespite any earlier police misconduct”; but the majority opinion nevertheless \nconceives an exception for evidence that was somehow “materially relied upon” \neven if it was never in evidence.  Op. at 43.  The DD‐5, which recounts Walker’s \nidentification of Bellamy, was not offered in evidence evidently because she \nrefused to sign it.  The prosecution nevertheless asked Walker whether she \nidentified Bellamy to the police.  But the prosecution’s (ill‐considered) question \nelicited a devastating reply: “No. . . . I said that it could have been him. It could \nhave.”  Trial Tr. 1005.  Any impression conveyed by asking the question was thus \nimmediately undone “in a straightforward manner.”  See DuFort, 874 F.3d at 355.  \nFurthermore, the court instructed the jury that counsel’s questions were not \nevidence.  See, e.g., Trial Tr. 432, 827, 1140.  Therefore, “[a]ny attempt to distort \nthe evidentiary record was fully mitigated” by Walker’s testimony.  See DuFort, \n874 F.3d at 355. \n For ballast, the majority opinion relies on a police merit award that the \nprosecutor presented to the detectives, praising their initiative in preparing a \ndetailed report of Walker’s interview.  Op. at 45.  But the citation does not say \nthat the substance of Walker’s identification was conveyed to the jury‐‐and it \nwouldnʹt matter if it did.  It goes without saying that the award was not offered \nin evidence.  The use of a police merit award in the majority opinion plows new \nground that is better left unturned. \n \n II \n The majority opinion vacates the district court’s grant of summary \njudgment dismissing three claims alleging Brady violations. \n Sanchez’s Beer Statement.  Sanchez testified that she saw Bellamy follow \nthe victim out of C‐Town on the Saturday that the murder was committed.  A \ndecade later, she recalled that Bellamy was prevented from buying beer.  Since \nbeer can be sold all day on Saturdays but cannot be sold (until noon) on Sundays, \nBellamy draws the inference that the witness was testifying about some day \nother than the day of the crime.  Bellamy’s Brady claim is that the beer issue is \nthus exculpatory, that Sanchez conveyed that information to Det. Gillen, and that \nGillen withheld that information from the prosecutor. \n\n\n 3 \n\n However, none of this matters for Brady purposes unless Sanchez told Det. \nGillen that Bellamy was unable to buy beer, and told him so at a point in time \nwhen he could have conveyed it to the prosecution before trial.  It was no until \ndiscovery in this case that Sanchez briefly acceded to a suggestion by Bellamy’s \ncounsel that she told the detective “at some point.”  App’x 1499.  That assent was \nelicited after experienced counsel used all his efforts to outwit a witness who \nbags groceries.  And even so, he failed: the vague and unhelpful concession came \nafter and was followed by repeated denials.1  App’x 1495‐1500.  Bellamy offers no \nevidence that the Det. Gillen had evidence in 1994 or 1995 that Sanchez saw \nBellamy follow the victim on a Sunday.  \n The majority posits that the trial outcome would have been different \n“[h]ad defense counsel been able to impeach Sanchez with” the inconsistency \nthat (i) she saw Bellamy in C‐Town on a day on which he could not buy beer, \nand (ii) that day was a Saturday.  Op. at 52.  But to the extent Sanchez was \nconfused on this point, her confusion was evident at trial, and available for \nexploitation by the defense.  She testified that she noticed Bellamy because “[h]e \nwas buying beer on a Sunday‐‐on a Saturday that day.”  Trial Tr. 642.  Moreover, \nthe prosecution told the jury that Sanchez gave contradictory testimony, Trial Tr. \n1138.  If (as the majority opinion has it) Sanchez’s imperfect memory “would \nhave been of great value to the defense,” Op. at 52, it is odd that defense counsel \ndid not ask her a single question about the blue laws in Queens. \n In any event, the issue is not difficult.  Sanchez saw Bellamy buying beer in \nC‐Town almost everyday.  Trial Tr. 642, 676.  No one should be surprised if a \nconvenience store prevents somebody from buying more beer‐‐on any day of the \nweek.  And Bellamy was not abstemious: he was drinking a 40‐ounce container \nof beer when he was arrested two weeks later.   \n Sanchez’s Identification of Lee.  Following Sanchez’s identification of \nBellamy, the police showed her a picture of Terrill Lee, whom she said was \naccompanying Bellamy on the day of the murder.  Bellamy conceded that he was \n                                                            \n1 “Q. And you told [Det. Gillen] [Bellamy] was trying to buy beer on a day he couldn’t \nbuy beer?  A. I can’t remember that part. . . . Q. So you may not remember exactly when \nbut at some point you told them about [sic] he was trying to buy beer and he couldn’t \nbuy beer?  A. Correct, yes. . . . Q. Which day, you don’t remember which day?  A. I can’t \nremember if I said that.  I can’t remember if I said that what day was the 22nd or‐‐I \ncan’t.”  Appx 1495‐1500. \n\n 4 \n\nwith Lee, but only later in the day.  But Lee’s wife told the police that Lee was \nwith her that day and not with Bellamy at all.  The detectives inferred that if Lee \nwas not there, Sanchez must have seen the two of them together on some other \nday, so the police did not investigate the matter further. \n Bellamy’s Brady claim is that the police failed to tell the prosecution that \nthey dropped Lee from their investigation.  The majority opinion characterizes \nthis Brady claim as “close,” which is generous.  As the district court explained, it \nis hard to see how this evidence would have helped Bellamy: a decision by the \npolice not to investigate whether Lee was there does not constitute evidence that \nhe wasn’t, let alone that Bellamy was elsewhere as well.  Anyway, Lee’s presence \nwas not an issue at the trial.  By then, Bellamy had changed his alibi: he was with \nhis father.   \n More fundamentally, there was no suppression of the evidence bearing \nupon this claim, and therefore there could not have been a Brady violation.  \n“Evidence is not ‘suppressed’ [for Brady purposes] if the defendant either knew \nor should have known of the essential facts permitting him to take advantage of \nany exculpatory evidence.”  United States v. LeRoy, 687 F.2d 610, 618 (2d Cir. \n1982) (internal citations omitted).  “The government is not required to make a \nwitness’ statement known to a defendant who is on notice of the essential facts \nwhich would enable him to call the witness and thus take advantage of any \nexculpatory testimony that [s]he might furnish.”  United States v. Stewart, 513 \nF.2d 957, 960 (2d Cir. 1975).   \n The defense was on notice of all the facts.  Bellamy knew, well in advance \nof trial, that Sanchez was a witness to the events that took place in C‐Town the \nmorning of the murder.  He knew that she claimed to have seen him with \nanother male.  And he knew (according to his own statements) that he had been \nwith Lee that day.  Accordingly, Bellamy was “on notice of the essential facts” \nthat enabled him to ask Sanchez whether she had seen him with Lee. \n The majority opinion suggests that the exculpatory value of the decision \nnot to investigate about Lee would have been to impeach Sanchez.  But if the \nidentification was to be used only to show Sanchez was unreliable, this method \nwould have been complicated and unconvincing‐‐and it would only have \nemphasized that Bellamy switched alibis.  \n\n\n\n\n 5 \n\n The Walker Form DD‐5.  Veronica Walker refused to sign the DD‐5 \nprepared after her interview, and made statements that Bellamy was not the \nperson she saw at the time of the crime.  Bellamy alleges that the police failed to \ntell that to the prosecution.  While this information (if true) should have been \nconveyed, this claim has been forfeited.  See Patterson v. Balsamico, 440 F.3d 104, \n112 (2d Cir. 2006) (deeming a forfeited civil claim “abandoned” and declining to \nconsider it).  It was pleaded as a Brady claim in the complaint; the defendants \nmoved to dismiss as immaterial all Brady claims premised on Walker’s \ntestimony, App’x 737; Bellamy’s response did not mention this claim; the district \ncourt did not mention it either; and there was no motion to reconsider.  Bellamy \ncannot now press the point on appeal. \n  \n III \n The majority opinion vacates the district court’s grant of summary \njudgment dismissing two Monell claims against the City of New York. \n Benefits Promised to Sanchez.  The defense argued to the jury that \nSanchez’s testimony should be discounted as induced by bribes, because Sanchez \nwas receiving $25 a week from the government, along with certain other benefits.  \nThe majority opinion points out, however, that the defense was not told the total \ndollar figure.  Op. at 74.  This is presented as a Monell claim because it was or is \nthe practice not to tell the prosecutor the full scope of such assistance.  This claim \nfails for several reasons. \n The prosecution disclosed all the evidence required; and Bellamy was on \nnotice of facts permitting him to elicit any additional evidence from the witness.  \nSee LeRoy, 687 F.2d at 618.  The prosecution disclosed to the defense that that she \nhad been placed in witness protection; that she had been given $25 per day ever \nsince; that she would continue to receive subsidies (for an unspecified time); that \nshe had been temporarily relocated by the government; and that the government \nwas proceeding with permanent relocation.  And since it was further disclosed \nthat she was unmarried, unemployed, and supporting herself (and her little \ntwins) on public assistance, the inference was clear that the government was \npaying for all this.  The majority cites no case suggesting that additional \ndisclosures were required. \n\n\n\n\n 6 \n\n Moreover, the jury knew that Sanchez was receiving benefits, and that she \nwas being permanently relocated.  On that basis, the cash total ($2,800) was not \nmaterial to the defense.  See United States v. Brown, 582 F.2d 197, 200‐01 (2d Cir. \n1978) (no prejudice where non‐disclosure had no effect on the defense’s theory of \nthe case). \n In any event, it would have done the defense no good to bring out the full \namount and thereby risk that the prosecution would refute an imputation of \nbribery by explaining that Sanchez was being supported because she was in the \nwitness protection program.  Any juror would infer from that that Bellamy was \ndangerous.  The evidence that Bellamy claims would be exculpatory would \ntherefore have operated as a boomerang.  If defense counsel had used the \ninformation the Bellamy claims he needed, Bellamy might have ended up with a \nvalid claim of ineffective counsel. \n The State’s Summation.  I agree with the majority opinion that (contrary to \nthe district court’s ruling) the City can be held responsible for the failure by a \ndistrict attorney to train staff to avoid improprieties in summation.  However, \nsince discovery was stayed as to the existence and sufficiency of the City’s \ntraining, the only question now is whether the improper summation resulted in \n“substantial prejudice.”  United States v. Certified Envtl. Servs., Inc., 753 F.3d 72, \n95 (2d Cir. 2014).  That turns on: (i) the severity of the misconduct; (ii) the value \nof any curative instruction; and (iii) the weight of the evidence.  Id.  I will take \nthem one by one. \n (i) Bellamy identifies remarks that are, as the majority opinion recognizes, \ntroubling.  Op. at 76‐78. But (ii) as the majority opinion observes, “Bellamy’s \ndefense counsel did not object to them nor subsequently seek a curative \ninstruction.”  Op. at 79.  Nor did Bellamy raise this summation misconduct on \ndirect appeal or as part of his habeas corpus petition.  It is therefore implausible \nthat the absence of a curative instruction was consequential.  Op. at 80; see \nUnited States v. Melendez, 57 F.3d 238, 242 (2d Cir. 1995).  So the majority \nopinion concludes, and I agree, that the “the determinative factor” is the weight \nof the evidence.  Op. at 81. \n (iii) Bellamy undertakes “a heavy burden” of establishing misconduct “so \nsevere and significant as to result in the denial” of due process.  United States v. \nLocascio, 6 F.3d 924, 945 (2d Cir. 1993).  “[W]here the jury’s verdict finds \nsubstantial support in the evidence, counsel’s improper statements will \n\n 7 \n\nfrequently be de minimis in the context of the entire trial.”  Marcic v. Reinauer \nTransp. Cos., 397 F.3d 120, 124 (2d Cir. 2005). \n The majority opinion asserts that Bellamy’s trial “existed at the cusp of \nreasonable doubt.”  Op. at 81.  However, the evidence easily supported \nconviction.  Bellamy admitted that he had known the victim for years and had \nbeen in the C‐Town the morning of the murder.  Sanchez (who recognized \nBellamy as a regular customer) testified that she saw him follow the victim out of \nthe C‐Town the morning of the murder.  That testimony placed Bellamy and the \nvictim together at the very time and place that another witness (Carter) watched \nfrom a few feet away as Bellamy stabbed the victim.  And Sanchez testified that \nBellamy later returned to the C‐Town to threaten her into silence.  \n Bellamy’s conviction was not attributable to improper remarks on \nsummation. \n\n\n\n\n 8", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362636/", "author_raw": "JACOBS, Circuit Judge, dissenting"}]}
WALKER
JACOBS
SHEA
1
{"WALKER": ", Circuit", "JACOBS": ", Circuit", "SHEA": ", District"}
2
0
1
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4585383/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Bellamy v. City of New York\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-29\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17‐1859 \n Bellamy v. City of New York \n\n 1 In the\n 2 United States Court of Appeals\n 3 For the Second Circuit\n 4 ________ \n 5  \n 6 AUGUST TERM, 2017 \n 7  \n 8 ARGUED: APRIL 26, 2018  \n 9 DECIDED: JANUARY 29, 2019 \n10  \n11 No. 17‐1859‐cv \n12  \n13 KAREEM BELLAMY, \n14 Plaintiff‐Appellant, \n15  \n16 v. \n17  \n18 CITY OF NEW YORK, JOHN J. GILLEN, AND MICHAEL F. SOLOMENO,  \n19 Defendants‐Appellees, \n20  \n21 John Doe 1, John Doe 2, Supervising Officers at the NYPD 101st \n22 Precinct, Vincent NMI Pepe, and Robert Schruhl, \n23 Defendants. \n24 ________ \n25  \n26 Appeal from the United States District Court \n27 for the Eastern District of New York. \n28 No. 12‐cv‐01025 – Ann M. Donnelly, Judge. \n29 ________ \n30  \n31 Before: WALKER AND JACOBS, Circuit Judges, SHEA, District Judge. \n32 ________ \n\n \n   Judge  Michael  P.  Shea,  of  the  United  States  District  Court  for  the \n District of Connecticut, sitting by designation. \n\n 2  No. 17‐1859\n\n 1 Kareem Bellamy filed this action in the Eastern District of New \n\n 2 York under New York state law and 42 U.S.C. § 1983 following the \n\n 3 vacatur of his state convictions for murder in the second degree under \n\n 4 N.Y. Penal Law § 125.25(2) and criminal possession of a weapon in \n\n 5 the  fourth  degree  under  N.Y.  Penal  Law  §  265.01(2),  for  which  he \n\n 6 served more than 14 years of a 25 years‐to‐life sentence.  Bellamy sued \n\n 7 investigating  Detectives  Michael  Solomeno  and  John  Gillen  of  the \n\n 8 New York Police Department (and certain John Does) as well as the \n\n 9 City  of  New  York  (at  times,  the  “City”),  alleging  that  each  are \n\n10 responsible  for  constitutional  infirmities  that  infected  Bellamy’s \n\n11 criminal  trial,  caused  his  wrongful  conviction,  and  resulted  in \n\n12 damages.  The  district  court  granted  the  Defendants’  motion  for \n\n13 summary judgment. \n\n14 As  relevant  on  appeal,  Bellamy  alleged  that  Detectives \n\n15 Solomeno  and  Gillen  fabricated  inculpatory  evidence  and  failed  to \n\n16 disclose  material  exculpatory  or  impeaching  evidence  depriving \n\n17 Bellamy of his rights to due process and a fair trial.  Bellamy alleged \n\n18 that the City is responsible, pursuant to Monell v. Department of Social \n\n19 Services  of  City  of  New  York,  436  U.S.  658  (1978),  for  violations  of \n\n20 Bellamy’s due process rights caused by certain policies of the office of \n\n21 the  Queens  County  District  Attorney  (“QCDA”),  the  office  that \n\n22 prosecuted Bellamy.  Principally, Bellamy alleged that (i) the QCDA’s \n\n23 office failed to disclose to the defense substantial benefits received by \n\n 3  No. 17‐1859\n\n 1 a key state witness due to an office policy of purposefully shielding \n\n 2 from prosecutors (and thereby the defense) the full scope of relocation \n\n 3 benefits  given  to  witnesses  in  its  witness  protection  program;  and \n\n 4 (ii) his  prosecutor  made  prejudicial  improper  remarks  during  his \n\n 5 summation,  which  was  ultimately  a  result  of  the  QCDA’s  office’s \n\n 6 customary indifference to its prosecutors’ summation misconduct.   \n\n 7 The district court (Donnelly, J.) granted Defendants’ motion for \n\n 8 summary  judgment  and  dismissed  each  of  Bellamy’s  claims.    As \n\n 9 relevant here, the district court rejected the claims against Detectives \n\n10 Solomeno and Gillen on the ground that Bellamy raised no material \n\n11 issue  of  fact  as  to  whether  either  detective  fabricated  or  withheld \n\n12 material evidence.  The district court rejected the claims against the \n\n13 City, concluding that the City could not as a matter of law be liable \n\n14 under Monell for the alleged policies of the QCDA’s office, and that, \n\n15 in any event, Bellamy did not raise a material issue of fact as to either \n\n16 of the constitutional violations underlying his Monell claims. \n\n17 The questions for our determination are whether Bellamy has \n\n18 produced sufficient evidence to raise material issues of fact that must \n\n19 be tried to a jury and whether the district court erred in dismissing \n\n20 the Monell claims as a matter of law.  If not, summary judgment was \n\n21 proper; if so, then summary judgment should not have been granted. \n\n22  \n\n 4  No. 17‐1859\n\n 1 We conclude that Bellamy has raised material issues of fact as \n\n 2 to  certain,  but  not  all,  of  his  claims  that  Detectives  Solomeno  and \n\n 3 Gillen fabricated and withheld material evidence, and we therefore \n\n 4 VACATE  in  part  and  AFFIRM  in  part  the  dismissal  of  Bellamy’s \n\n 5 claims against them.  We further conclude that the City of New York \n\n 6 may be held liable for the consequences of the alleged policies of the \n\n 7 QCDA’s office under the Monell doctrine, and that Bellamy has raised \n\n 8 material issues of fact as to the underlying constitutional violations: \n\n 9 the non‐disclosure of financial benefits received by one of the state’s \n\n10 principal  witnesses  and  the  impropriety  of  his  prosecutor’s \n\n11 summation.  Consequently, we VACATE the dismissal of Bellamy’s \n\n12 claims against the City.   \n\n13 We REMAND the cause for further proceedings consistent with \n\n14 this opinion. \n\n15 Judge Jacobs dissents in a separate opinion.  \n\n16 ________ \n17  \n18 JOEL  B.  RUDIN,  Law  Office  of  Joel  B.  Rudin,  P.C., \n19 New York, NY, for Plaintiff‐Appellant. \n20  \n21 MEGAN  E.K.  MONTCALM  (Richard Dearing, on the \n22 brief), for Zachary W. Carter, Corporation Counsel \n23 of  the  City  of  New  York,  New  York,  NY,  for \n24 Defendants‐Appellees. \n25  \n26 Richard D. Willstatter, Vice Chair, Amicus Curiae \n27 Committee of the National Association of Criminal \n\n 5  No. 17‐1859\n\n 1 Defense  Lawyers,  Chair,  Amicus  Curiae \n 2 Committee  of  the  New  York  State  Association  of \n 3 Criminal  Defense  Lawyers,  White  Plains,  NY; \n 4 Adele  Bernhard,  Innocence  Network,  New  York, \n 5 NY;  Barry  Scheck,  Innocence  Project,  New  York, \n 6 NY; Ross E. Firsenbaum, Wilmer Cutler Pickering \n 7 Hale  and  Door  LLP,  New  York  NY,  for  Amici \n 8 Curiae  National  Association  of  Criminal  Defense \n 9 Lawyers,  New  York  State  Association  of  Criminal \n10 Defense  Lawyers,  Innocence  Network,  and  Innocence \n11 Project. \n12 ________ \n13  \n14 JOHN M. WALKER, JR., Circuit Judge: \n\n15  Kareem Bellamy filed this action in the Eastern District of New \n\n16 York under New York state law and 42 U.S.C. § 1983 following the \n\n17 vacatur of his state convictions for murder in the second degree under \n\n18 N.Y. Penal Law § 125.25(2) and criminal possession of a weapon in \n\n19 the  fourth  degree  under  N.Y.  Penal  Law  §  265.01(2),  for  which  he \n\n20 served  more  than  14  years  of  a  25  years‐to‐life  sentence.      Bellamy \n\n21 sued investigating Detectives Michael Solomeno and John Gillen of \n\n22 the New York Police Department (and certain John Does) as well as \n\n23 the  City  of  New  York  (at  times,  the  “City”),  alleging  that  each  are \n\n24 responsible  for  constitutional  infirmities  that  infected  Bellamy’s \n\n25 criminal  trial,  caused  his  wrongful  conviction,  and  resulted  in \n\n26 damages.  The  district  court  granted  the  Defendants’  motion  for \n\n27 summary judgment. \n\n 6  No. 17‐1859\n\n 1 As  relevant  on  appeal,  Bellamy  alleged  that  Detectives \n\n 2 Solomeno  and  Gillen  fabricated  inculpatory  evidence  and  failed  to \n\n 3 disclose  material  exculpatory  or  impeaching  evidence  depriving \n\n 4 Bellamy of his rights to due process and a fair trial.  Bellamy alleged \n\n 5 that the City is responsible, pursuant to Monell v. Department of Social \n\n 6 Services  of  City  of  New  York,  436  U.S.  658  (1978),  for  violations  of \n\n 7 Bellamy’s due process rights caused by certain policies of the office of \n\n 8 the  Queens  County  District  Attorney  (“QCDA”),  the  office  that \n\n 9 prosecuted Bellamy.  Principally, Bellamy alleged that (i) the QCDA’s \n\n10 office failed to disclose to the defense substantial benefits received by \n\n11 a key state witness due to an office policy of purposefully shielding \n\n12 from prosecutors (and thereby the defense) the full scope of relocation \n\n13 benefits  given  to  witnesses  in  its  witness  protection  program;  and \n\n14 (ii) his  prosecutor  made  prejudicial  improper  remarks  during  his \n\n15 summation,  which  was  ultimately  a  result  of  the  QCDA’s  office’s \n\n16 customary indifference to its prosecutors’ summation misconduct.   \n\n17 The district court (Donnelly, J.) granted Defendants‐Appellees’ \n\n18 motion  for  summary  judgment  and  dismissed  each  of  Bellamy’s \n\n19 claims.  As relevant here, the district court rejected the claims against \n\n20 Detectives Solomeno and Gillen on the ground that Bellamy raised no \n\n21 material  issue  of  fact  as  to  whether  either  detective  fabricated  or \n\n22 withheld  material  evidence.    The  district  court  rejected  the  claims \n\n23 against the City, concluding that the City could not as a matter of law \n\n 7  No. 17‐1859\n\n 1 be liable under Monell for the alleged policies of the QCDA’s office, \n\n 2 and that, in any event, Bellamy did not raise a material issue of fact as \n\n 3 to either of the constitutional violations underlying his Monell claims. \n\n 4 The questions for our determination are whether Bellamy has \n\n 5 produced sufficient evidence to raise material issues of fact that must \n\n 6 be tried to a jury and whether the district court erred in dismissing \n\n 7 the Monell claims as a matter of law.  If not, summary judgment was \n\n 8 proper; if so, then summary judgment should not have been granted. \n\n 9 We conclude that Bellamy has raised material issues of fact as \n\n10 to  certain,  but  not  all,  of  his  claims  that  Detectives  Solomeno  and \n\n11 Gillen fabricated and withheld material evidence, and we therefore \n\n12 VACATE  in  part  and  AFFIRM  in  part  the  dismissal  of  Bellamy’s \n\n13 claims against them.  We further conclude that the City of New York \n\n14 may be held liable for the consequences of the alleged policies of the \n\n15 QCDA’s office under the Monell doctrine, and that Bellamy has raised \n\n16 material issues of fact as to the underlying constitutional violations: \n\n17 the non‐disclosure of financial benefits received by one of the state’s \n\n18 principal  witnesses  and  the  impropriety  of  his  prosecutor’s \n\n19 summation.  Consequently, we VACATE the dismissal of Bellamy’s \n\n20 claims against the City.   \n\n21 We REMAND the cause for further proceedings consistent with \n\n22 this opinion. \n\n 8  No. 17‐1859\n\n 1 BACKGROUND \n\n 2   This appeal requires us to address the complex and protracted \n\n 3 facts surrounding the events pertaining to the 1994 killing of James \n\n 4 Abbott.    While  Plaintiff‐Appellant  Kareem  Bellamy  was  ultimately \n\n 5 convicted in New York state court for Abbott’s murder, the uncertain \n\n 6 circumstances  of  the  killing,  and  the  investigation  and  trial  that \n\n 7 followed, sparked a lengthy, circuitous, and at times dramatic legal \n\n 8 fight  that  continued  into  post‐conviction  proceedings.    That  battle \n\n 9 began  with  what  the  record  shows  to  have  been  a  hard‐fought \n\n10 criminal trial with no certain outcome in sight.  Ultimately, Bellamy \n\n11 was acquitted on the charge of intentional murder but convicted of \n\n12 depraved indifference murder and unlawful possession of a weapon.  \n\n13 After  Bellamy  exhausted  his  direct  appeal  opportunities  without \n\n14 success,  the  post‐conviction  litigation  proceeded  in  two  general \n\n15 stages.  First, after a prolonged and complicated state post‐conviction \n\n16 process,  the  state  court  vacated  Bellamy’s  convictions  in  light  of \n\n17 newly  discovered  evidence  that  another  individual  might  have \n\n18 committed the Abbott murder.  Second, following the state’s decision \n\n19 not  to  re‐try  him  and  his  release  from  prison,  Bellamy  sought  civil \n\n20 relief in federal court alleging that his criminal trial was infected with \n\n21 constitutional error.  The instant lawsuit concerns only the latter fight, \n\n22 which pertains not to how or why Bellamy was released but whether \n\n23 constitutional error led to his conviction in the first place. \n\n 9  No. 17‐1859\n\n 1   In assessing the constitutional propriety of Bellamy’s criminal \n\n 2 trial,  we  are  aided  by  (i)  an  extensive  summary  judgment  record, \n\n 3 which  includes  documents  related  to  the  investigation  and \n\n 4 prosecution  of  Bellamy;  (ii)  the  record  of  Bellamy’s  criminal  trial; \n\n 5 (iii) the  record  of  Bellamy’s  state  post‐conviction  proceedings;  and \n\n 6 (iv) extensive  deposition  testimony  taken  in  this  action.1    Although \n\n 7 much is in contention in this case, what follows are the undisputed \n\n 8 facts  from  this  complicated  record  and  other  relevant  facts  that  we \n\n 9 identify as remaining in dispute. \n\n10 I. James Abbott’s Murder and the Resulting Investigation \n\n11 Shortly  before  10:00  a.m.,  on  Saturday,  April  9,  1994,  an \n\n12 assailant fatally stabbed James Abbott near a phone booth during an \n\n13 altercation after Abbott left a C‐Town Supermarket in Far Rockaway, \n\n14 Queens.   Detectives Michael Solomeno and John Gillen of the NYPD’s \n\n15 101st Precinct were assigned to investigate.  In canvassing the area, \n\n16 Detective Gillen, with other officers, entered the C‐Town store with a \n\n17 photo of Abbott to see if anyone had witnessed anything.  Detective \n\n\n\n   Throughout  this  opinion,  we  cite  to  the  transcripts  of  Bellamy’s \n 1\n\n criminal trial (“Trial Tr.”), the first and second hearings held on Bellamy’s \n New York state post‐conviction motion filed pursuant to N.Y. Crim. Proc. \n Law  §  440.10  (“First  440  Tr.”  and  “Second  440  Tr.,”  respectively),  and \n deposition testimony taken in this case (“[] Dep. Tr.”).  We direct the reader \n to the district court docket to review the full versions of these transcripts.  \n See No. 12‐cv‐1025 (E.D.N.Y.), Dkt. Nos. 188–99, 204–13 [hereinafter, “Dkt. \n No. []”]. \n\n 10  No. 17‐1859\n\n 1 Gillen spoke with Jay Judel, a C‐Town deli clerk, who reported that \n\n 2 Abbott, a regular customer, had been in the store alone that morning.   \n\n 3 Another officer interviewed Andrew Carter, a wheelchair‐bound man \n\n 4 living adjacent to the C‐Town who said that he saw the attack while \n\n 5 waiting at a bus stop down the street from the phone booth where the \n\n 6 altercation took place.  Carter told the officer that he saw three males \n\n 7 he did not recognize leave the C‐Town, and that when one stopped to \n\n 8 use the payphone, the other two “started punching and kicking” him, \n\n 9 and that “one of the males then produced a knife and started stabbing \n\n10 the  victim  numerous  times  about  the  body  and  head.”    App’x  234.  \n\n11 Carter told the officer that the two men fled on foot. \n\n12 The  following  week,  on  April  15,  1994,  Detective  Gillen \n\n13 received a phone call from a woman who identified herself as Anna \n\n14 Simmons.    Simmons  reported  that  she  had  overheard  two \n\n15 individuals,  Levon  (“Ish”)  Martin  and  Rodney  (“Turk”)  Harris, \n\n16 discussing the Abbott murder.  Simmons said that she heard Ish and \n\n17 Turk bragging that they had killed Abbott following Abbott’s refusal \n\n18 to  join  their  gang,  the  Regulators.    The  following  day,  Detectives \n\n19 Solomeno  and  Gillen  re‐interviewed  Carter,  who  was  unable  to \n\n20 identify Ish and Turk from a photo array.  In the days that followed, \n\n21 Detectives  Solomeno  and  Gillen  tried  to  track  down  Simmons,  but \n\n22 never found her. \n\n 11  No. 17‐1859\n\n 1 On April 22, 1994, Linda Sanchez, a C‐Town cashier who was \n\n 2 working at the store on the morning of Abbott’s murder, called the \n\n 3 101st Precinct.2  Detectives Solomeno and Gillen then interviewed her \n\n 4 at her home.  Sanchez told the detectives that on the morning of the \n\n 5 murder,  Abbott,  whom  she  recognized,  entered  the  store,  collected \n\n 6 certain goods and got in a cashier’s line, and that two other men then \n\n 7 came into the store and ultimately got in line behind Abbott.  After \n\n 8 making his purchases, Abbott remained in the store to speak with the \n\n 9 store’s manager, “JJ,” while the two men behind Abbott in line had \n\n10 left the store and started walking through the parking lot “toward the \n\n11 chicken  store.”   App’x  237.    Sanchez  noted that  before  they  left  the \n\n12 parking  lot,  the  two  men  stopped  and  looked  back  at  the  C‐Town \n\n13 store.    Sanchez  herself  then  walked  to  the  parking  lot  to  collect \n\n14 shopping  carts  whereupon  she  saw  Abbott  walk  out  of  the  store \n\n15 through  the  parking  lot  and  also  in  the  direction  of  the  “[c]hicken \n\n16 store.”  App’x 237–238.  The detectives showed Sanchez a photo array \n\n17 that  included  Ish  and  Turk—the  two  men  identified  in  the  Anna \n\n\n\n  Sanchez’s telling of why she called the police on April 22, 1994 has not \n 2\n\n been  entirely  clear.    On  direct  examination  she  testified  (and  Defendants \n agree) that she called the police because Bellamy threatened her. Trial Tr. \n 706–08.  Sanchez, however, did not then mention those threats in her phone \n call  to  the  precinct  or  in  the  interview  that  followed,  and  on  cross‐\n examination,  she  at  times  suggested  that  her  call  was  prompted  by  an \n article  about  the  Abbott  murder  in  The  Wave  newspaper,  which  listed \n Detective Solomeno’s contact information.  See Trial Tr. 741–51. \n\n 12  No. 17‐1859\n\n 1 Simmons phone call—but she did not recognize them as the two men \n\n 2 she had seen in the store in line behind Abbott. \n\n 3 Three weeks later, on May 13, 1994, Sanchez again called the \n\n 4 precinct  to  report  that  a  man,  who  was  drinking  a  40‐ounce  beer \n\n 5 across the street from the C‐Town, was one of the two men that she \n\n 6 had previously reported were in the cashier’s line behind Abbott on \n\n 7 the morning of Abbott’s murder.  Shortly thereafter, Detective Gillen \n\n 8 arrived  on  the  scene  with  other  detectives,  and  they  saw  Bellamy \n\n 9 drinking  a  40‐ounce  beer  in  the  location  Sanchez  described.    The \n\n10 detectives detained Bellamy in a squad car and told him that he was \n\n11 being taken to the station to be fined in relation to his public drinking. \n\n12 As  we  will  discuss  later,  Detective  Gillen  said  at  trial  that  Bellamy \n\n13 made  spontaneous  and  unprompted  comments  in  the  police  car \n\n14 regarding a murder, but Bellamy denies that this occurred. \n\n15 At the police station, Detective Gillen showed Bellamy a photo \n\n16 of Abbott’s body and told him that there were witnesses identifying \n\n17 him as the assailant.  Bellamy denied any involvement in the murder \n\n18 and told Detective Gillen that he was with a friend named Terrill Lee \n\n19 on  the  day  of  the  murder.    Bellamy  was  placed  in  a  holding  cell \n\n20 overnight.   \n\n21 The following day, May 14, 1994, Detective Gillen orchestrated \n\n22 a  six‐person  lineup  at  the  precinct,  to  be  viewed  by  Sanchez  and \n\n23 Carter,  the  sole  eyewitnesses  known  to  the  detectives  at  that  time. \n\n 13  No. 17‐1859\n\n 1 Bellamy  was  in  position  one.    Sanchez  identified  the  individual  in \n\n 2 position one as one of the two men she saw leave the C‐Town prior to \n\n 3 Abbott on the day of Abbott’s killing.  As to be discussed, the parties \n\n 4 dispute certain aspects of what occurred during Carter’s viewing of \n\n 5 the lineup.  All agree, however, that Carter initially recognized one of \n\n 6 Abbott’s  assailants  in  either  position  one  or  two  but  that  he \n\n 7 subsequently  told  Detective  Gillen  in  a  separate  room  that  he  was \n\n 8 “99% sure” that the person he recognized was in position one, which \n\n 9 in fact was Bellamy.  App’x 295, 2415. \n\n10 Hours  later,  in  the  early  morning  of  May  15,  1994,  Detective \n\n11 Gillen  and  Assistant  District Attorney  (ADA) Stephen  Antignani  of \n\n12 the QCDA’s office took a sworn statement from Terrill Lee, the man \n\n13 Bellamy  claimed  he  was  with  on  the  day  of  Abbott’s  murder.    Lee \n\n14 stated  that  although  he  was  friends  with  Bellamy,  he  was  not  with \n\n15 him  at  all  on  April  9,  1994.    Thereupon,  that  same  day,  Detective \n\n16 Gillen filled out a criminal complaint charging Bellamy with Abbott’s \n\n17 murder. \n\n18 II. Criminal Proceedings Against Kareem Bellamy \n\n19 The grand jury indicted Bellamy on two counts of murder in \n\n20 the  second  degree  under  N.Y.  Penal  Law  §  125.25(1)  (intentional \n\n21 murder)  and  §  125.25(2)  (depraved  indifference  murder),  and  one \n\n22 count of criminal possession of a weapon in the fourth degree under \n\n23 N.Y. Penal Law § 265.01(2).  After unsuccessful suppression motions \n\n 14  No. 17‐1859\n\n 1 by  the  defense,  the  case  proceeded  to  trial  in  November  1995  with \n\n 2 ADA David Guy of the QCDA’s office as the prosecutor. \n\n 3 As  relevant  to  this  appeal,  the  state  called  the  following \n\n 4 witnesses:  (i) Detective  Gillen;  (ii)  Linda  Sanchez;  (iii)  Detective \n\n 5 Solomeno;  (iv)  Carter;  (v)  Deborah  Abbot,  the  victim’s  sister;  and \n\n 6 (vi) Veronica  Walker,  an eyewitness who  surfaced  for the  first time \n\n 7 during  the  trial.  We  summarize  the  relevant  portions  of  each  state \n\n 8 witness’s trial testimony and the summations.3 \n\n 9 Detective  Gillen.    Detective  Gillen’s  testimony  described  his \n\n10 investigation  of  the  Abbott  murder.    He  testified  about  his  initial \n\n11 discussion with Carter on the day of the murder, the Anna Simmons \n\n12 phone call the following week, and his role in the lineups.  Detective \n\n13 Gillen  also  testified  about  the  circumstances  of  picking  up  Bellamy \n\n14 following  Sanchez’s  call  to  the  precinct.    Detective  Gillen  testified \n\n15 with reference to an unsigned handwritten note that he wrote, that he \n\n16 said  was  his  contemporaneous  memorialization  of  Bellamy’s \n\n17 utterance in the squad car on the way to the police station: “This must \n\n18 be  a  case  of  mistaken  identity—someone  probably  accused  me  of \n\n19 murdering  someone.”    Trial  Tr.  494–95;  see  App’x  290.    Detective \n\n\n\n  Bellamy’s lone witness was Bellamy’s stepfather, with whom Bellamy \n 3\n\n lived on the day of the murder.  Bellamy’s stepfather testified that Bellamy \n did not leave the house on the day of the murder until 10:15–10:20 a.m.  Trial \n Tr. 1027–29. \n\n 15  No. 17‐1859\n\n 1 Gillen  then  testified  that  after  arriving  at  the  station  he  added  the \n\n 2 following notation on the same piece of paper: “Statement made by \n\n 3 [Bellamy]  while  being  asked  his  pedigree—spontaneous  & \n\n 4 unsolicited.”    Trial  Tr.  534–40;  App’x  1707.4    On  cross‐examination, \n\n 5 Detective  Gillen  acknowledged  that  he  did  not  incorporate  any  of \n\n 6 Bellamy’s statements in a “DD‐5,” known as a “complaint follow up” \n\n 7 form,  despite  having  prepared  eight  DD‐5s  throughout  the \n\n 8 investigation of the Abbott murder.  Trial Tr. 527–28, 532–34. \n\n 9 Linda Sanchez.5  ADA Guy began his questioning of Sanchez \n\n10 by  soliciting  her  biographical  information  and  then  asking  if  she \n\n11 “receive[d] any money from the office of the [QCDA] prior to coming \n\n12 into court today?”  Trial Tr. 633.  Sanchez acknowledged that she had \n\n13 received  $50  from  the  QCDA’s  office  and  anticipated  receiving \n\n14 another $50 from the office.  She testified that the money was for “food \n\n15 for the babies, Pampers,” and amounted to “$25 a day.”  Trial Tr. 634.  \n\n\n\n   Detective  Gillen  did  not  testify  at  trial  as  to  another  purported \n 4\n\n statement from Bellamy that he recorded on the same piece of paper:  “Why \n would  someone  accuse  me  of  something  I  didn’t  do?”    App’x  1707.  \n Nevertheless, the document in its entirety was entered into evidence at trial.  \n See Trial Tr. 538.  Detective Gillen acknowledged in a pre‐trial hearing that \n he recorded the first “murder” statement right away in the squad car and \n wrote the second “accuse” statement on the same piece of paper when he \n returned to the precinct.  App’x 2413. \n  It appears that the prosecution viewed Sanchez as a reluctant witness, \n 5\n\n in that she showed up to testify only after the prosecution served her with \n a material witness order on the first day of trial.  App’x 2044.  ADA Guy \n did not refer to Sanchez in his opening statement.   \n\n 16  No. 17‐1859\n\n 1 She further testified that she “came [to court] with the detective,” and \n\n 2 that  she  was  staying  overnight  at  a  “different  location”  than  her \n\n 3 residence,  and  that  “[t]he  detective”  “put  [her]  into  that  differen[t] \n\n 4 location.”  Trial Tr. 634–35. \n\n 5 Sanchez  then  testified  as  to  what  she  saw  on  the  morning  of \n\n 6 April  9,  1994.    She  identified  Bellamy  as  being  in  the  C‐Town  that \n\n 7 morning, wearing a green jacket and braids in his hair, with “a lot of \n\n 8 braids sticking up,” and that he and another taller person went to the \n\n 9 same line as Abbott.  Trial Tr. 639–41, 774.  Sanchez had seen Bellamy \n\n10 in the C‐Town many times before and noticed him that day because \n\n11 “[h]e was buying beer on a Sunday—on a Saturday that day.”  Trial \n\n12 Tr. 642.  Bellamy was in the store for about fifteen minutes and walked \n\n13 out before Abbott.  Sanchez noticed Bellamy turn to the right after he \n\n14 left the store, rather than to the left, the direction in which he usually \n\n15 departed from the store.  Sanchez then walked to the parking lot to \n\n16 retrieve shopping carts when she noticed Abbott catch up to Bellamy \n\n17 and the taller person and pass by them.  Sanchez testified that when \n\n18 NYPD  officers  came  to  the  C‐Town  later  that  morning,  she  did  not \n\n19 speak to them.   \n\n20 Finally,  Sanchez  testified  that Bellamy  threatened  her  on  two \n\n21 separate occasions after the Abbott murder.  A week after the murder, \n\n22 Bellamy entered the C‐Town and said to her: “You know, you know, \n\n23 you  fucking  bitch.  .  .  .  You’re  next.”    Trial  Tr.  706.    Then,  Sanchez \n\n 17  No. 17‐1859\n\n 1 testified  that  the  following  occurred  on  the  street  on  May  13,  1994 \n\n 2 before  she  called  the  police:  “He  was  pointing  at  me.    You  know \n\n 3 yelling, at like, yelling something at me.  Just pointing and pointing \n\n 4 at my direction.”  Trial Tr. 710.  Sanchez testified that she never told \n\n 5 the police about these threats, and that she had not told anyone about \n\n 6 them until one week before Bellamy’s trial (in November 1995).6 \n\n 7 Detective Solomeno.  Detective Solomeno testified that he was \n\n 8 initially  the  assigned  detective  on  the  investigation  of  the  Abbott \n\n 9 murder, and that he played a role in the Ish and Turk photo arrays \n\n10 shown to Sanchez and Carter and that he conducted the April 22, 1994 \n\n11 interview of Sanchez.  Detective Solomeno also testified that, in the \n\n12 days prior to his trial testimony, he had spoken to Deborah Abbott, \n\n13 the victim’s sister, who had given him the contact information for a \n\n14 woman named Veronica Walker.  Detective Solomeno testified that \n\n15 he spoke with Walker shortly before trial on December 1, 1995 and \n\n16 that he prepared a DD‐5 in connection with that interview.  \n\n17 Andrew  Carter.    Carter  testified  as  to  what  he  saw  on  the \n\n18 morning of the murder and what happened at the Bellamy lineup.  On \n\n19 April 9, 1994, as he was waiting for the bus, he saw three people walk \n\n20 out of the C‐Town store, one by himself and the other two together.  \n\n\n\n  However, Sanchez later testified that she mentioned the threats to an \n 6\n\n ADA immediately prior to testifying in front of the grand jury.  Trial Tr. \n 758–59. \n\n 18  No. 17‐1859\n\n 1 The  three  men  came  “right  past”  him,  and  then  Carter  looked  in \n\n 2 another direction.  Trial Tr. 868.  When Carter turned back towards \n\n 3 the direction of the three men, “the other two guys were beating the \n\n 4 hell out of [Abbott].”  Trial Tr. 869.  Carter then testified that one of \n\n 5 the two men pulled out a “brass knuckle knife” and stabbed Abbott.  \n\n 6 Trial Tr. 872.  Carter pointed to Bellamy from the witness stand and \n\n 7 testified that the individual who stabbed Abbott was “the gentlemen \n\n 8 right  there.”    Trial  Tr.  870–71.    Carter  had  never  seen  any  of  the \n\n 9 individuals before, but he got a good look at their faces.  Trial Tr. 872–\n\n10 73.  Carter had “[n]o doubt” that Bellamy was the person he saw stab \n\n11 Abbott that morning.  Trial Tr. 872. \n\n12 Carter  then  testified  at  length  about  viewing  the  lineup  in \n\n13 which Bellamy was in position one.  He testified that he initially told \n\n14 the detective that “it was either one or two, because they got their hair \n\n15 different.”    Trial  Tr.  880.    Specifically,  Carter  testified  that  the \n\n16 individual he saw stab Abbott did not have braids in his hair, but that \n\n17 the person in position one at the lineup did have braids.  Carter then \n\n18 had  a  conversation  in  another  room  with  an  ADA  and  a  detective \n\n19 where Carter “said [it was] two.”  Trial Tr. 883.  Carter testified several \n\n20 times at trial that the individual he saw stab Abbott was in position \n\n21 number  two  in  the  lineup.    Trial  Tr.  895–96,  903–04.    Nevertheless, \n\n22 Carter  testified  that  he  told  the  detectives  at  the  time  that  it  was \n\n23 “either one or two,” but also that he was 99% sure the assailant was \n\n 19  No. 17‐1859\n\n 1 in position number one.  Trial Tr.  882, 896, 903.  ADA Guy tried to \n\n 2 sum  up  (but  not  resolve)  the  confusion  on  redirect,  asking  Carter: \n\n 3 “You told us today it was number two, but you told the detective it \n\n 4 was number one that day?”  Trial Tr. 904.  Carter responded, “Yes.”  \n\n 5 Trial Tr. 904. \n\n 6 Deborah Abbott.  Deborah Abbott, the victim’s sister, testified \n\n 7 about a conversation she had with Veronica Walker in July of 1995, \n\n 8 fifteen months after the killing of her brother but four months prior \n\n 9 to  the  trial.    Following  that  conversation,  she  called  the  police  and \n\n10 spoke  with  prosecutor  ADA  Guy.    The  next  time  Deborah  Abbott \n\n11 spoke to ADA Guy was one week before the trial, where she for the \n\n12 first time gave identifying information for Walker.   \n\n13 Veronica Walker.  Walker testified as to what she saw on the \n\n14 morning of April 9, 1994.  Walker stopped into the C‐Town prior to a \n\n15 10:00 a.m. hair appointment, and briefly spoke with Abbott who she \n\n16 recognized from her neighborhood.  She left the store after about 5–6 \n\n17 minutes, got in her car, and began to drive away.  She stopped at the \n\n18 adjacent  intersection  and  saw  through  her  car’s  passenger  side \n\n19 window that Abbott was fighting with a lone man near a phone booth \n\n20 directly  to  her  right.    Walker  then  made  a  righthand  turn  when  a \n\n21 skinny 5’6” man with braided hair “came from across the left‐hand \n\n22 side of the street from the back of [her] car, running across the street,” \n\n23 and  joined  in  the  fight  between  Abbott  and  the  unidentified  man.  \n\n 20  No. 17‐1859\n\n 1 Trial  Tr.  1001–03.    Walker,  who  knew  Bellamy  personally,  testified \n\n 2 that she did not recognize the man who ran behind her car to join the \n\n 3 fight,  had  never  seen  him  before,  and  did  not  see  him  in  the \n\n 4 courtroom.   \n\n 5 In an apparent attempt to impeach Walker’s non‐identification \n\n 6 of Bellamy, ADA Guy then asked Walker about her interview with \n\n 7 Detectives Solomeno and Gillen the previous week: \n\n 8 Q:  Well,  didn’t  you  tell  Detective  Solomeno \n 9 and  Detective  Gillen  that  you  recognized \n10 that person [who you saw run by the car] as \n11 Kareem [Bellamy]? \n12 A:    No. \n13 Q:  What—Well,  did  you  tell  Detective \n14 Solomeno  that  the  person  looked  like \n15 Kareem? \n16 A:    I said it could have been him.  It could have. \n\n17 Trial Tr. 1005.  The defense asked Walker almost no questions. \n18 Defense Summation.7  In summation, the defense argued that \n\n19 the state had not shown that Bellamy committed the Abbott murder \n\n20 beyond  a reasonable  doubt.    It  argued  that  the  case  was  a “rush  to \n\n21 judgment,” and that “the district attorney was anxious to close this \n\n22 case and so they closed it.”  Trial Tr. 1099.  The defense principally \n\n23 attacked the three eyewitnesses.  It argued that Sanchez’s story lacked \n\n\n\n  Under New York law, the defense delivers its summation first and has \n 7\n\n no right of rebuttal.  See N.Y. Crim. Proc. Law § 260.30. \n\n 21  No. 17‐1859\n\n 1 common sense and that she had a motive to lie given her receipt of \n\n 2 $25 per day by the QCDA’s office.  The defense focused on Carter’s \n\n 3 trial testimony to the effect that the assailant was in position two at \n\n 4 the  lineup,  not  position  one,  and  downplayed  Carter’s  in‐court \n\n 5 identification by arguing that Carter simply pointed to the only “black \n\n 6 man” at the defense counsel’s table.  Trial Tr. 1099.  Counsel reminded \n\n 7 the jury that Walker did not identify Bellamy as the person she saw \n\n 8 run by her car, and rather acknowledged only that it could have been \n\n 9 him.    The  defense  also  focused  on  the  differing  accounts  from  the \n\n10 witnesses as to whether the assailant did or did not have braided hair.  \n\n11 Trial  Tr.  1093;  compare  Trial  Tr.  774  &  1003  (Sanchez  and  Walker’s \n\n12 testimony  that  the  assailant  had  braids)  with  Trial  Tr.  896  (Carter’s \n\n13 testimony that the assailant did not have braids).8   The defense then \n\n14 argued  that  Bellamy  never  made  the  spontaneous  “murder” \n\n15 statement  in  the  squad  car,  and  that  even  if  he  did,  it  was  not \n\n16 inculpatory.  Finally, the defense counsel reminded the jury that the \n\n17 state had never attempted to establish any motive for the killing. \n\n18 State’s Summation.  ADA Guy delivered a lengthy summation, \n\n19 acknowledging, at the outset, that the evidence in the case was messy \n\n20 and was not presented in a “tidy little package” for the jury.  Trial Tr. \n\n\n  The trial testimony Carter gave as to Bellamy’s hair contradicted his \n 8\n\n testimony at the grand jury, where he testified that on the day of the lineup \n the assailant “had his hair cut,” but that on the day of the Abbott murder \n he had “[k]inky, short braids.”  App’x 334. \n\n 22  No. 17‐1859\n\n 1 1113.  But, he argued, the jury’s “task becomes relatively easy” when \n\n 2 it applies common sense and focuses principally on the testimony of \n\n 3 the three eyewitnesses.  Trial Tr. 1115.   \n\n 4 ADA Guy acknowledged that Sanchez “may not be the most \n\n 5 articulate  person,”  and  that  she  “got  a  little  confused  from  time  to \n\n 6 time”  and  “didn’t  testify  all  that  well,”  in  that  she  made  certain \n\n 7 mistakes and contradictions, but that her story was credible, she had \n\n 8 no reason to lie, and there was no “evidence that she is a liar.”  Trial \n\n 9 Tr.  1121,  1138–40,  1144.    ADA  Guy  also  acknowledged  certain \n\n10 contradictions in Carter’s testimony and argued that Carter “made a \n\n11 mistake” when he said that the assailant was in position two at the \n\n12 lineup.  Trial Tr. 1134–36.  But, ADA Guy argued, “[y]ou don’t have \n\n13 to  take  my  word.    Common  sense  will  tell  you  it’s  the  defendant, \n\n14 number  one,  who  is  on  trial,  not  some  filler  in  a  lineup.”    Trial  Tr. \n\n15 1137.    ADA  Guy  also  acknowledged  Walker’s  non‐identification  of \n\n16 Bellamy in court but argued that the jury should instead focus on the \n\n17 physical description that she provided of the individual she saw on \n\n18 the  morning  of  the  Abbott  murder,  which  is  consistent  both  with \n\n19 Bellamy’s actual description and the other eyewitnesses’ description \n\n20 of the assailant.   \n\n21 ADA Guy then addressed the defense’s remaining contentions.  \n\n22 He answered the defense’s contention that the state offered no motive \n\n23 for Bellamy’s alleged killing of Abbott by arguing that there was no \n\n 23  No. 17‐1859\n\n 1 proof, either way, of motive in this case, “submit[ting that] there is no \n\n 2 proof that he had no motive.”  Trial Tr. 1133 (emphasis added).  ADA \n\n 3 Guy also reminded the jury of Detective Gillen’s testimony regarding \n\n 4 Bellamy’s “premature denial” in the squad car, arguing that it was in \n\n 5 character with Bellamy’s inability to “keep his mouth shut,” a mouth \n\n 6 that  ADA  Guy  argued  was  “huge”  and  “cavernous,”  as  well  as \n\n 7 Bellamy’s status as a “liar.”  Trial Tr. 1145–48.  \n\n 8 ADA Guy concluded by again imploring the jurors to use their \n\n 9 common sense.  As reflected in the trial transcript, ADA Guy told the \n\n10 jury:  “I  know  who  committed  the  murder.    You  know  it  was  an \n\n11 intentional murder and you know there is no rational explanation for \n\n12 why so many people are pointing their fingers at [Bellamy].”  Trial Tr. \n\n13 1149.9    ADA  Guy  concluded  in  substance:    “When  the  defendant \n\n14 asked  why  would  someone  be  accusing  me  of  murder,  by  your \n\n15 verdict you can answer his question.  Because you are the murderer.  \n\n16 It’s because the evidence shows that you are the murderer, and that \n\n17 you are not going to get away with it, not this time.”  Trial Tr. 1150.  \n\n18 *  *  * \n\n19 After  three  days  of  deliberations,  during  which  the  jury \n\n20 submitted eighteen notes to the judge, sought lengthy readbacks of \n\n\n   As  to  be  discussed,  the  Defendants  contend  that  the  trial  transcript \n 9\n\n contains a transcription error, and that ADA Guy stated, “You know who \n committed the murder.” \n\n 24  No. 17‐1859\n\n 1 testimony,  and  was  given  an  Allen  charge,10  the  jury  acquitted \n\n 2 Bellamy  of  intentional  murder  but  convicted  him  of  depraved \n\n 3 indifference  murder  and  a  weapons  charge.    The  court  sentenced \n\n 4 Bellamy  to  25‐years‐to‐life.    Bellamy  appealed  the  convictions, \n\n 5 arguing  (i) insufficiency  of  the  evidence;  (ii)  that  Detective  Gillen \n\n 6 provided false testimony; and (iii) that Bellamy’s statements to Gillen \n\n 7 and the lineup identifications should have been suppressed.  The state \n\n 8 appellate court affirmed, 247 A.D.2d 399, and leave to appeal to the \n\n 9 Court of Appeals was denied, 91 N.Y.2d 970.  Bellamy’s federal habeas \n\n10 corpus petition, which depended entirely on his assertion that Gillen \n\n11 falsely testified as to Bellamy’s statements in the squad car following \n\n12 his pickup, was denied and not appealed.   \n\n13 III. Bellamy’s State Post‐Conviction Proceedings \n\n14 In  2007,  more  than  a  decade  after  his  conviction,  Bellamy \n\n15 moved  to  vacate  the  judgment  against  him  pursuant  to  N.Y.  Crim. \n\n16 Proc.  Law  §  440.10(f),  (g)  and  (h).    See  People  v.  Bellamy,  2008  WL \n\n17 3271995, at *2–3 (Sup. Ct. Queens Cnty. June 27, 2008).  The central \n\n\n\n   “The  term  ‘Allen  charge’  is  a  generic  term  used  for  a  type  of \n 10\n\n supplemental instruction that is given to a deadlocked jury, first approved \n by  the  Supreme  Court  in  Allen  v.  United  States,  164  U.S.  492  (1896).    ‘A \n traditional  Allen  charge  reminds  the  jurors  about  the  importance  of \n obtaining  a  verdict  and  encourages  jurors  to  listen  ‘to  each  other’s \n arguments’ while also emphasizing that ‘the verdict must be the verdict of \n each individual juror, and not a mere acquiescence in the conclusion of his \n fellows.’ Id. at 501.”  Smalls v. Batista, 191 F.3d 272, 275 n.1 (2d Cir. 1999).  \n\n 25  No. 17‐1859\n\n 1 basis for the sought‐after relief was § 440.10(g), which under certain \n\n 2 circumstances  allows  for  the  vacatur  of  a  guilty  verdict  upon  the \n\n 3 discovery of new evidence.  The principal new evidence relied on by \n\n 4 Bellamy  was  that:  (i)  another  individual,  Ish,  had  confessed  to  the \n\n 5 Abbott murder to a police informant named Michael Green, and that \n\n 6 Green had Ish on tape discussing the crime; and (ii) Carter recanted \n\n 7 his  trial  testimony  that  identified  Bellamy  as  the  assailant  and  was \n\n 8 now  asserting  that  he  falsely  inculpated  Bellamy  at  trial  under \n\n 9 pressure by Detective Gillen. \n\n10 The  state  post‐conviction  court  conducted  a  lengthy  hearing, \n\n11 which included taking the testimony of several of the trial witnesses, \n\n12 including  Carter,11  Walker,  Sanchez,  and  Detectives  Solomeno  and \n\n13 Gillen, as well as the testimony of Green and ADA Antignani.  As will \n\n14 be  discussed,  some  of  the  testimony  at  this  hearing  added  further \n\n15 color  to  the  events  surrounding  Abbott’s  murder,  while  other \n\n16 testimony conflicted with that given at trial.  Following the hearing, \n\n17 the court granted Bellamy’s motion and vacated his conviction based \n\n18 solely  on  the  newly  discovered  evidence  proffered  by  Green  that \n\n\n\n\n   On  June  11,  2008,  following  his  testimony  at  the  initial  hearing  on \n 11\n\n Bellamy’s § 440 motion (but prior to the second such hearing), Carter passed \n away.   \n\n 26  No. 17‐1859\n\n 1 inculpated Ish in Abbott’s murder.12  See id. at *11–12 (finding Carter’s \n\n 2 recantation not credible). \n\n 3 After  filing  an  appeal  of  that  judgment,  however,  the  state \n\n 4 moved  for  reargument  before  the  hearing  court,  arguing  that  the \n\n 5 evidence  from  Green  that  the  court  relied  on  to  vacate  Bellamy’s \n\n 6 conviction  was  perjurious  and  fraudulent.    The  state  submitted  an \n\n 7 affidavit  from  Green  in  which  he  now  admitted  that  the  tape  he \n\n 8 offered  at  the  §  440  hearing  purportedly  capturing  a  conversation \n\n 9 between Green and Ish was in fact a recording between Green and an \n\n10 acquaintance  pretending  to  be  Ish.    See  People  v.  Bellamy,  2010  WL \n\n11 143462, at *1 (Sup. Ct. Queens Cnty. Jan. 14, 2010).  The hearing court \n\n12 reopened  the  proceeding  and  again  took  significant  witness \n\n13 testimony, including that of Green, who testified consistent with his \n\n14 affidavit  that  he  created  the  false  tape,  that  he  lied  at  the  earlier \n\n15 hearing,  and  that  Ish  never  told  him  that  he  was  involved  in  the \n\n16 Abbott murder.   \n\n17 Despite  finding  that  Green  had  falsely  testified  about  a \n\n18 fabricated  tape,  the  court  adhered  to  its  earlier  ruling  ordering  the \n\n19 vacatur of Bellamy’s judgment of conviction.  The court found parts \n\n20 of  Green’s  testimony  inculpating  Ish  at  the  initial  hearing  credible \n\n21 despite  the  fake  tape  and  Green’s  subsequent  recantation.    Bellamy, \n\n\n  The motion court referred to Green in this initial ruling on Bellamy’s \n 12\n\n § 440 motion as “John Doe/CI.”  See Bellamy, 2008 WL 3271995, at *8–9. \n\n 27  No. 17‐1859\n\n 1 2010  WL 143462,  at  *6.    The  Second  Department  affirmed,  agreeing \n\n 2 that  a  “reasonable  jury  could  find  .  .  .  that  [Green’s]  original \n\n 3 unsolicited implication of [Ish] was truthful, regardless of [Green’s] \n\n 4 later recantation of those statements.”  84 A.D.3d 1260, 1262 (2d Dep’t \n\n 5 2011).  Leave to appeal to the Court of Appeals was denied, 17 N.Y.3d \n\n 6 813, Bellamy was released from prison, and the state dismissed the \n\n 7 indictment.13 \n\n 8 IV. The Instant Civil Action \n\n 9   In March 2012, Bellamy filed the instant action in the Eastern \n\n10 District  of  New  York  against  the  City  of  New  York,  Detectives \n\n11 Solomeno and Gillen, and two John Doe defendants. 14  At the core of \n\n\n\n  In a series of rulings after Bellamy’s conviction, the New York Court \n 13\n\n of  Appeals  significantly  limited  the  reach  of  New  York’s  criminal \n prohibition against depraved indifference murder, the only murder charge \n on  which  Bellamy  was  convicted.    See  People  v.  Payne,  3  N.Y.3d  266,  270 \n (N.Y.  2004).    In  short,  the  Court  of  Appeals  concluded  that  where  an  act \n evinces  an  intent  to  kill,  that  act  cannot  support  a  depraved  indifference \n charge, which is not a lesser included offense of intentional murder.  Id.  The \n state  therefore  conceded  that  it  could  not  “in  good  faith,  proceed  with  a \n subsequent  prosecution  [of  Bellamy]  for  depraved  indifference  murder \n because we are legally prohibited from doing so. . . . [We] have no other \n choice but to move to dismiss this indictment against this defendant . . . not \n because he has been exonerated or because we believe him to be actually \n innocent  but because a continued prosecution  is not  legally  sustainable.”  \n App’x 698. \n  On October 31, 2014, Bellamy filed an amended complaint replacing \n 14\n\n the  two  John  Does  with  named  defendants,  Dkt.  No.  82,  but  Bellamy \n withdrew that pleading and the parties stipulated that the original March \n 2012 complaint would be the operative complaint, Dkt. No. 110. \n\n 28  No. 17‐1859\n\n 1 Bellamy’s complaint were allegations that the Defendants engaged in \n\n 2 material misconduct during the investigation and trial that deprived \n\n 3 him  of  his  rights  to  due  process  under  the  Fourteenth  Amendment \n\n 4 and to a fair trial under the Sixth Amendment.  In short, Bellamy’s \n\n 5 claims at issue here fall into three general categories:  (i) claims that \n\n 6 Detectives  Solomeno  and  Gillen  fabricated  material  evidence; \n\n 7 (ii) claims  that  Detectives  Solomeno  and  Gillen  withheld  material \n\n 8 evidence; and (iii) Monell claims against the City of New York based \n\n 9 upon allegations that, pursuant to a policy, the QCDA withheld the \n\n10 full scope of relocation benefits it provided to Sanchez and that, due \n\n11 to a systemic failure to train or discipline, ADA Guy’s summation was \n\n12 improper.15  Specifically, as relevant on appeal, Bellamy’s complaint \n\n13 alleges that: \n\n\n  After the district court’s denial of the Defendants’ motion to dismiss, \n 15\n\n and Bellamy’s withdrawal of his claims against the John Doe defendants, \n Dkt. 24, 110, one of his Monell claims, see Dkt. 112, 158 at 21 n.5, and a claim \n for negligent infliction of emotional distress, Dkt. 24, the following claims \n remained at issue:  \n (i) Section  1983  claims  against  Detectives  Solomeno  and  Gillen \n alleging  a  denial  of  due  process,  the  right  to  a  fair  trial,  and \n conscience shocking government action.  \n (ii) Section  1983  and  state  law  claims  against  Detectives  Solomeno \n and Gillen alleging malicious prosecution.  \n (iii) Section 1983 Monell claims against the City of New York. \n (iv) State  law  intentional  infliction  of  emotional  distress  claims \n against Detectives Solomeno and Gillen. \n (v) A state law respondeat superior claim against the City of New York.   \n\n 29  No. 17‐1859\n\n 1 (i) Detective  Gillen  fabricated  evidence  that  Bellamy \n 2 referenced a murder in the squad car that escorted him to \n 3 the police station on May 13, 1994 and falsely testified as to \n 4 such at Bellamy’s criminal trial; \n 5 (ii) Detective Solomeno fabricated evidence in the form of the \n 6 contents of a DD‐5 that reported that during her December \n 7 1,  2005  interview  Walker  identified  Bellamy  as  the \n 8 individual she saw on the morning of the Abbott murder; \n 9 (iii) Detective  Gillen  improperly  pressured  Carter  to  identify \n10 Bellamy  in  the  lineup  conducted  on  May  14,  1994,  even \n11 though Carter was unsure if Bellamy was the person he saw \n12 stab Abbott; \n13 (iv) Detective  Gillen  and/or  Solomeno  failed  to  disclose \n14 statements  Sanchez  made  during  the  investigation \n15 indicating that the morning she saw Bellamy was a Sunday, \n16 rather than a Saturday, the day on which Abbott was killed; \n17 (v) Detective  Gillen  failed  to  disclose  Sanchez’s  statement \n18 during  the  investigation  that  the  person  she  saw  with \n19 Bellamy on the morning of the Abbott murder was Terrill \n20 Lee; \n21 (vi) Detective  Gillen  failed  to  disclose  Sanchez’s  statements  to \n22 police officers on April 9, 1994, the day of Abbott’s murder, \n23 that she “didn’t see anything” and “didn’t know anything”; \n24 (vii) Detectives Solomeno and Gillen failed to disclose Walker’s \n25 statements  during  her  December  1,  2005  interview  that \n26 Bellamy was not the person she saw on the morning of the \n27 Abbott murder and that Walker refused to sign the DD‐5 to \n28 the effect that she had seen Bellamy; \n29 (viii) the  prosecution  failed  to  disclose  to  the  defense  the  full \n30 relocation  benefits  received  by  Sanchez  as  part  of  her \n31 participation  in  the  QCDA’s  witness  protection  program; \n32 and \n33 (ix) ADA Guy committed prejudicial summation misconduct. \n\n 30  No. 17‐1859\n\n 1 The  district  court  stayed  discovery  on  the  core  of  Bellamy’s \n\n 2 Monell claims (viii and ix above) but allowed discovery to proceed in \n\n 3 full on the claims against Detectives Solomeno and Gillen.  See Dkt. \n\n 4 No. 52. The parties took substantial deposition testimony, including \n\n 5 from  the  following  witnesses:  (i)  Bellamy;  (ii)  Detective  Gillen;  (iii) \n\n 6 Detective Solomeno; (iv) ADA Antignani; (v) ADA Guy; (vi) Michael \n\n 7 Mansfield, the Director of the QCDA’s witness protection program; \n\n 8 (vii) Daniel Cox, the administrator of the QCDA’s witness protection \n\n 9 program responsible for Sanchez’s participation; (viii) Sanchez; and \n\n10 (ix)  Walker.    We  refer  to  the  deposition  testimony  in  detail  in  our \n\n11 forthcoming  analysis  of  Bellamy’s  claims,  but  simply  preview  here \n\n12 that  the  deposition  testimony,  like  the  testimony  at  the  §  440 \n\n13 proceeding, provides further, albeit at times conflicting, accounts of \n\n14 the  circumstances  surrounding  Abbott’s  murder  and  the  resulting \n\n15 investigation. \n\n16   At  the  close  of  discovery  on  the  claims  against  Detectives \n\n17 Solomeno  and  Gillen,  both  parties  cross‐moved  for  summary \n\n18 judgment.  In an 80‐page ruling, the district court granted summary \n\n19 judgment  to  Defendants  dismissing  Bellamy’s  claims  against \n\n20 Detectives Solomeno and Gillen and dismissing the Monell claims on \n\n21 the pleadings.  Bellamy v. City of New York, 2017 WL 2189528 (E.D.N.Y. \n\n22 May 17, 2017).  First, the district court dismissed Bellamy’s malicious \n\n23 prosecution claims against the detectives on the ground that Bellamy \n\n 31  No. 17‐1859\n\n 1 failed to raise a triable issue of fact as to whether he was prosecuted \n\n 2 without probable cause.16  Id. at *29–34.  Second, it dismissed the core \n\n 3 of  Bellamy’s  due  process  and  fair  trial  claims  against  Detectives \n\n 4 Solomeno  and  Gillen  upon  concluding  that  Bellamy  raised  no \n\n 5 material  issue  of  fact  as  to  whether  either  detective  fabricated  or \n\n 6 withheld  material  evidence.    Id.  at  *34–36.    Third,  it  dismissed \n\n 7 Bellamy’s  “shocks  the  conscience”  due  process  claims  against  the \n\n 8 detectives as duplicative of Bellamy’s malicious prosecution claims.  \n\n 9 Id.  at  *36.    Fourth,  it  dismissed  Bellamy’s  intentional  infliction  of \n\n10 emotional  distress  claims  against  the  detectives  on  the  ground  that \n\n11 Bellamy raised no triable issue as to whether the detectives conduct \n\n12 was “extreme and outrageous,” and that, regardless, the claims were \n\n13 also duplicative of Bellamy’s malicious prosecution claim.  Id. at *37.  \n\n14 Finally, the district court dismissed Bellamy’s Monell claims against \n\n15 the City on the pleadings for two reasons: (i) in light of Van de Kamp \n\n16 v.  Goldstein,  555  U.S.  335  (2009),  the  City  of  New  York  cannot  as  a \n\n17 matter of law be liable for the alleged policies of the QCDA’s office; \n\n18 and  (ii)  regardless,  Bellamy  did  not  sufficiently  establish  the \n\n19 underlying constitutional due process violations he alleged:  the non‐\n\n\n\n\n  Later in its opinion, the district court also concluded that Detectives \n 16\n\n Solomeno  and  Gillen  would  have  been  protected  by  qualified  immunity \n from Bellamy’s malicious prosecution claims regardless.  Id. at *37. \n\n 32  No. 17‐1859\n\n 1 disclosure  of  Sanchez’s  relocation  benefits  and  ADA  Guy’s \n\n 2 summation misconduct.17  Id. at *37–41. \n\n 3   Bellamy’s  appeal  challenges  only  the  dismissal  of  his  due \n\n 4 process and fair trial claims against Detectives Solomeno and Gillen \n\n 5 and  his  Monell  claims  against  the  City  of  New  York.    His  baseline \n\n 6 position is that (i) as to the claims against Detectives Solomeno and \n\n 7 Gillen,  the  evidence  as  a  whole  (from  the  trial,  the  post‐conviction \n\n 8 hearing,  and  the  depositions  in  the  instant  civil  case),  presents \n\n 9 disputed issues of material fact that necessitate a trial, and (ii) with \n\n10 respect to the Monell claims, the district court committed legal error \n\n11 and  that  material  fact  issues  remain  as  to  the  underlying  conduct \n\n12 alleged. \n\n13 DISCUSSION \n\n14 We review de novo both a grant of a summary judgment and the \n\n15 grant  of  judgment  on  the  pleadings.    Bank  of  New  York  v.  First \n\n16 Millennium, Inc., 607 F.3d 905, 914, 922 (2d Cir. 2010). \n\n17 Summary judgment may be granted only “if the movant shows \n\n18 that there is no genuine dispute as to any material fact and that the \n\n\n\n\n  It does not appear that the Defendants moved for summary judgment \n 17\n\n on Bellamy’s Count XII against the City of New York for respondeat superior, \n and  the  district  court  did  not  address  the  claim.    Regardless,  Bellamy’s \n respondeat  superior  claim  depended  on  his  establishing  his  state  law  tort \n claims, see Dkt. 1 ¶¶ 472–73, which the district court dismissed.  Bellamy \n does not appeal the dismissal of those claims, so this issue is not relevant. \n\n 33  No. 17‐1859\n\n 1 movant is entitled to judgment as a matter of law.”  Fed. R. Civ. P. \n\n 2 56(a).  We may affirm the grant of summary judgment only when, in \n\n 3 “resolv[ing]  all  ambiguities  and  draw[ing]  all  permissible  factual \n\n 4 inferences in favor of the [non‐moving] party. . . the record taken as a \n\n 5 whole could not lead a rational trier of fact to find for the non‐moving \n\n 6 party.”  Estate of Gustafson v. Target Corp., 819 F.3d 673, 675 (2d Cir. \n\n 7 2016) (internal quotation marks omitted).  Thus, in the present context \n\n 8 and of significance here, where the summary judgment non‐movant \n\n 9 is a former criminal defendant bringing § 1983 claims related to his \n\n10 underlying criminal trial, the summary judgment standard, generally \n\n11 speaking, is the converse of the standard applicable direct appeal of a \n\n12 criminal  defendant’s  conviction,  which  requires  us  to  “view  the \n\n13 evidence in a light that is most favorable to the government, and with \n\n14 all reasonable inferences resolved in favor of the government.” United \n\n15 States  v.  Anderson,  747  F.3d  51,  60  (2d  Cir.  2014)  (internal  quotation \n\n16 marks omitted). \n\n17 A court may grant judgment on the pleadings only when, after \n\n18 “accept[ing]  all  factual  allegations  in  the  complaint  as  true  and \n\n19 draw[ing] all reasonable inferences in favor of the [plaintiff] . . . the \n\n20 complaint  [does  not]  contain  sufficient  factual  matter  .  .  .  to  state  a \n\n21 claim to relief that is plausible on its face.”  Bank of New York, 607 F.3d \n\n22 at 922. \n\n 34  No. 17‐1859\n\n 1 These  principles  lead  us  to  conclude,  contrary  to  the  district \n\n 2 court, that Bellamy has succeeded in raising material issues of fact as \n\n 3 to a number of the claims subject to this appeal.  This requires us to \n\n 4 vacate in large part the dismissal of Bellamy’s due process and fair \n\n 5 trial claims against Detectives Solomeno and Gillen and to vacate in \n\n 6 full the dismissal of Bellamy’s Monell claims.18 \n\n 7 I. Claims Against Detectives Solomeno and Gillen \n\n 8 As  we  have  previously  discussed,  Bellamy’s  claims  against \n\n 9 Detectives  Solomeno  and  Gillen  fall  into  two  general  categories: \n\n10 (i) claims  that  the  detectives  fabricated  material  evidence;  and \n\n11 (ii) claims that the detectives withheld material evidence. \n\n12 a. Evidence Fabrication Claims \n\n13 “When  a  police  officer  creates  false  information  likely  to \n\n14 influence  a  jury’s  decision  and  forwards  that  information  to \n\n15 prosecutors,  he  violates  the  accused’s  constitutional  right  to  a  fair \n\n16 trial.”  Ricciuti v. N.Y.C. Transit Auth., 124 F.3d 123, 130 (2d Cir. 1997). \n\n17 Bellamy  contends  that  Detective  Gillen  and/or  Solomeno  fabricated \n\n18 three pieces of material evidence: (i) Bellamy’s “murder” statement in \n\n19 the  squad  car;  (ii) Walker’s  statement  implicating  Bellamy  as \n\n20 recorded in a DD‐5 drafted by Detective Solomeno; and (iii) Carter’s \n\n\n  The dissent posits views of the evidence that, if accepted by a trial jury, \n 18\n\n would  likely  result  in  a  defendants’  verdict.  But  it  does  so  by  drawing \n inferences against the plaintiffs and thus does not gainsay the existence of \n disputed issues of material fact that require a trial determination.  \n\n 35  No. 17‐1859\n\n 1 lineup identification of Bellamy.  We conclude that Bellamy has raised \n\n 2 material issues of fact precluding summary judgment as to the first \n\n 3 two contentions, but not the third. \n\n 4 i. Bellamy’s “Murder” Statement in the Squad Car \n\n 5 The prosecution relied at trial on Detective Gillen’s testimony \n\n 6 regarding  an  undated  and  unsigned  note  that  Detective  Gillen \n\n 7 contended that he wrote while in the squad car shortly after he picked \n\n 8 up Bellamy.  The note purportedly captured the following utterance \n\n 9 from Bellamy: “This must be a case of mistaken identity—someone \n\n10 probably accused me of murdering someone.”  App’x 290.  The note \n\n11 also supposedly transcribed the following squad car statement from \n\n12 Bellamy,  which  Detective  Gillen  only  added  to  the  note  after \n\n13 returning  to  the  precinct:    “Why  would  someone  accuse  me  of \n\n14 something  I  didn’t  do?”    App’x  290,  2413.    Sometime  thereafter, \n\n15 Detective  Gillen  again  added  to  the  note  the  following:  “Statement \n\n16 made  by  def  while  being  asked  his  pedigree—spontaneous  & \n\n17 unsolicited.”    App’x  1707.    The  prosecution  relied  heavily  on  this \n\n18 evidence at trial.  Detective Gillen, the state’s first witness, testified at \n\n19 length regarding Bellamy’s purported murder statement in the squad \n\n20 car, which Gillen allegedly memorialized in a handwritten note in his \n\n21 police  spiral  notebook.  Trial  Tr.  494–96,  529.  ADA  Guy  relied  on \n\n22 Bellamy’s purported murder statement in summation, Trial Tr. 1124.  \n\n23 The prosecution’s reliance on this statement is unsurprising because, \n\n 36  No. 17‐1859\n\n 1 if  Bellamy  made  it,  it  is  highly  inculpatory.    No  one  mentioned \n\n 2 Abbott’s  murder  to  Bellamy  when  he  was  picked  up,  and  from \n\n 3 Bellamy’s  perspective,  all  indications  were  that  the  detectives  were \n\n 4 detaining Bellamy solely for consuming alcohol in public.  \n\n 5 Bellamy  has  consistently  denied  making  the  “murder” \n\n 6 statement, including in his deposition in this case, and asserts as part \n\n 7 of  his  fair  trial  claim  that  it  was  wholly  fabricated  by  Detective \n\n 8 Gillen.19    In  a  brief  analysis,  the  district  court  rejected  the  claim, \n\n 9 relying on Jeffreys v. City of New York, 426 F.3d 549 (2d Cir. 2005), for \n\n10 the  proposition  that  self‐serving  deposition  testimony  that  is \n\n11 “unsubstantiated by any other direct evidence” cannot raise an issue \n\n12 of material fact.  2017 WL 2189528, at *31. \n\n13 We  conclude,  contrary  to  the  district  court,  that  Bellamy  has \n\n14 raised a material issue of fact as to whether Detective Gillen fabricated \n\n15 the note purportedly memorializing Bellamy’s “murder” statement in \n\n16 the  squad  car.    Contrary  to  the  district  court’s  analysis,  a  §  1983 \n\n17 plaintiff’s testimony alone may be independently sufficient to raise a \n\n18 genuine issue of material fact.  See, e.g., Rentas v. Ruffin, 816 F.3d 214, \n\n19 221  (2d  Cir.  2016).  Jeffreys  is  inapposite  because  the  self‐serving \n\n\n\n   Bellamy  affirmatively  denies  making  the  “murder”  statement  but \n 19\n\n takes  a  softer  stance  as  to  the  “accuse”  statement,  stating  he  cannot \n remember making it but that if he did it was “probably . . . after they . . . put \n the [photo of the] bloody guy on the table and told me that two people said \n they seen me kill somebody.”  Bellamy Dep. Tr. 145–47. \n\n 37  No. 17‐1859\n\n 1 testimony in that case was “contradictory and incomplete,” and “so \n\n 2 replete  with  inconsistencies  and  improbabilities  that  no  reasonable \n\n 3 juror would undertake the suspension of disbelief necessary to credit \n\n 4 the  allegations.”    426  F.3d  at  555.    Here,  Bellamy’s  testimony  was \n\n 5 consistent and uncomplicated:  he never made the statement.  Neither \n\n 6 is his testimony wholly improbable:  why would Bellamy offer such \n\n 7 an admission when he was told only that he was being picked up on \n\n 8 a public drinking charge? \n\n 9 Further  distinguishing  this  case  from  Jeffreys  is  that  there  is \n\n10 evidence  in  the  record,  independent  from  Bellamy’s  unequivocal \n\n11 denial, tending to support an inference of fabrication.  The DD‐5 that \n\n12 Detective  Gillen  drafted  that  summarized  the  circumstances  of \n\n13 Bellamy’s  pickup  makes  no  mention  of  the  “murder”  statement, \n\n14 despite the fact that the DD‐5 both identified that Bellamy was being \n\n15 investigated for homicide and that Detective Gillen was specifically \n\n16 investigating the Abbott murder when he went to pick up Bellamy.  \n\n17 See App’x 1738; see also Trial Tr. 491.  At trial, Detective Gillen will no \n\n18 doubt be asked to explain this omission from the DD‐5.  In so doing, \n\n19 he may repeat the explanation he offered at a pre‐trial hearing that \n\n20 the omission was “basically an oversight.”  App’x 2411.  The jury will \n\n21 be free, however, to weigh that assertion against evidence that NYPD \n\n22 detectives  commonly  understand  that  DD‐5s  are  to  be  used  at  trial \n\n23 and  that  it  is  protocol  for  a  suspect’s  statements  to  be  incorporated \n\n 38  No. 17‐1859\n\n 1 into  a  DD‐5,  especially  statements  as  significant  as  those  that \n\n 2 Detective Gillen attributes to Bellamy.  See Solomeno Dep. Tr. 27–28; \n\n 3 Guy Dep. Tr. 79, 126–27; see also Trial Tr. 532–33 (Gillen testimony that \n\n 4 he prepared eight DD‐5s related to the Abbott murder investigation \n\n 5 alone).   \n\n 6 The  jury  will  also  be  free  to  weigh  other  evidence  tending to \n\n 7 undermine  Detective  Gillen’s  testimony  that  Bellamy  made  the \n\n 8 “murder” statement in the police car, such as the fact that Detective \n\n 9 Gillen did not identify this statement during his grand jury testimony, \n\n10 see  App’x  336–38,  and  the  fact  that  the  record  shows  that  Detective \n\n11 Gillen,  who  was  in  the  backseat  with  Bellamy,  said  that  Bellamy \n\n12 “yell[ed]”  the  “murder”  statement  but  neither  of  the  two  other \n\n13 officers who were in the car was asked to—or did—corroborate his \n\n14 story. Both of those detectives testified at trial and neither mentioned \n\n15 the “murder” statement.  Gillen Dep. Tr. 53; Trial Tr. 495.  In sum, the \n\n16 jury  would  be  entitled  to  consider  the  lack  of  corroboration  of \n\n17 Detective Gillen’s testimony.20  \n\n\n\n\n  Defendants assert support for the accuracy of Gillen’s transcription of \n 20\n\n the “murder” statement in the form of ADA Antignani’s notice served to \n Bellamy pursuant to N.Y. Crim. Proc. Law § 710.30 two days after Bellamy \n was picked up, which notifies Bellamy of the state’s intent to rely on the \n “murder” statement at trial.  App’x 1610.  Even if this fact could support an \n inference that the Gillen transcription was accurate, it just as easily supports \n the inference that ADA Antignani simply relied on Gillen’s fabricated note. \n\n 39  No. 17‐1859\n\n 1 We conclude that, taken as a whole, the evidence compiled at \n\n 2 summary judgment, viewed in the light most favorable to Bellamy, \n\n 3 cannot  rule  out  the  inference  that  Detective  Gillen  fabricated  the \n\n 4 “murder” statement.  Bellamy has therefore raised a material issue of \n\n 5 fact precluding summary judgment on this fair trial claim. \n\n 6 ii. DD‐5 Documenting Walker Interview \n\n 7 On  December  1,  2005,  while  Bellamy’s  criminal  trial  was \n\n 8 ongoing,  Detectives  Solomeno  and  Gillen  for  the  first  time \n\n 9 interviewed Veronica Walker, who, as discussed, testified at trial that \n\n10 she  had  been  at  the  scene  in  her  car  when  Abbott  was  killed.  \n\n11 Following that interview, Detective Solomeno drafted a DD‐5 that, he \n\n12 testified, memorialized Walker’s statements and forwarded the DD‐5 \n\n13 to ADA Guy.  Bellamy contends that Detective Solomeno fabricated \n\n14 the statements inculpating Bellamy attributed to Walker in that DD‐\n\n15 5, and that the state materially relied on the fabricated DD‐5 at trial.  \n\n16 We conclude that the summary judgment record, again taken in the \n\n17 light most favorable to non‐movant Bellamy, raises a material issue of \n\n18 fact as to whether Detective Solomeno in fact fabricated the evidence \n\n19 contained in the DD‐5.  \n\n20 At her deposition, Walker testified in detail about her mid‐trial \n\n21 interview with Detectives Solomeno and Gillen.  Walker testified that \n\n22 the  detectives  told  her  they  received  her  contact  information  from \n\n23 Deborah Abbott, the victim’s sister, and that Deborah had reported to \n\n 40  No. 17‐1859\n\n 1 them that she had a conversation with Walker in which Walker said \n\n 2 she witnessed Bellamy kill Abbott.  Walker testified that she told the \n\n 3 detectives that the story was not true, but the detectives continued to \n\n 4 insist  to  her  that  she  witnessed  Bellamy  murder  Abbott.    Detective \n\n 5 Solomeno  then  showed  Walker  two  photos  of  Bellamy,  whom  she \n\n 6 told the detectives she recognized and had seen over 300 times in her \n\n 7 life.  Walker testified that she repeatedly told the detectives, however, \n\n 8 that it was not Bellamy that she saw on the day of the Abbott murder.  \n\n 9 She  testified  that,  despite  those  statements,  Detective  Solomeno \n\n10 drafted the following handwritten statement directly to the contrary \n\n11 and asked Walker to sign it: \n\n12 Miss Walker stated that she drove past the two males \n13 fighting and that when . . . she looked back and then \n14 saw another male black she knew as Kareem Bellamy \n15 also  fighting  with  James  [Abbott]  and  that  Kareem \n16 and the other male black were kicking and punching \n17 James. \n\n18 App’x 2128–29.  Walker swore that she refused to sign the statement \n\n19 because, in her view and consistent with her repeated statements to \n\n20 the detectives, it was not true.  As she explained in her deposition:   \n\n21 I read the whole thing and that is not what it stated \n22 that I said.  It stated that I witnessed Kareem, that I \n23 seen  Kareem  and  that  is  what  I  was  saying  to  them \n24 and that’s the reason why I didn’t sign it because I did \n25 not see him. \n\n 41  No. 17‐1859\n\n 1 Walker Dep. Tr. 40.  Walker repeatedly characterized the statement as \n\n 2 “lies,”  Walker  Dep.  Tr.  127–31,  the  same  position  she  took  years \n\n 3 earlier when testifying at Bellamy’s § 440 proceeding.  First 440 Tr. 97 \n\n 4 (“Absolutely not. Never told them that.”). \n\n 5   While Detectives Solomeno and Gillen both insist the statement \n\n 6 was true, they concede that Walker refused to sign the statement that \n\n 7 Detective Solomeno drafted during their December 1, 2005 interview.  \n\n 8 Solomeno  Dep.  Tr.  42–43;  Gillen  Dep.  Tr.  191.    Detective  Solomeno \n\n 9 acknowledges that he nevertheless put the “almost word for word” \n\n10 statement in a DD‐5, but failed to disclose in the DD‐5 that Walker \n\n11 refused to sign it (as he concedes he “should have” done), and that he \n\n12 gave the DD‐5 to ADA Guy, again without revealing to the prosecutor \n\n13 that Walker refused to sign the statement.  Solomeno Dep. Tr. 143–45.  \n\n14 ADA  Guy  testified  that  he  was  unaware  of  any  of  this  and \n\n15 characterized the allegations of the concealment of the refusal to sign \n\n16 as “very troubling,” and, if true, “reprehensible.” Guy Dep. Tr. 117. \n\n17   Significantly,  the  Defendants  do  not  dispute  that  the  above \n\n18 evidence  at  the  least  raises  an  issue  of  fact  as  to  whether  Detective \n\n19 Solomeno fabricated the Walker statement and forwarded it to ADA \n\n20 Guy.    See  Br.  of  Appellees  44–46.    Their  sole  argument  in  favor  of \n\n21 dismissal of this evidence fabrication claim is that the allegedly false \n\n22 DD‐5 was immaterial in that it did not impact Bellamy’s criminal trial \n\n23 because it was not introduced into evidence and, at trial, Walker did \n\n 42  No. 17‐1859\n\n 1 not identify Bellamy.  For support, they rely on DuFort v. City of New \n\n 2 York,  874  F.3d  338  (2d  Cir.  2017),  where  we  concluded  that  ʺ[m]ere \n\n 3 attempts  to  withhold  or  falsify  evidence  cannot  form  the  basis  of  a \n\n 4 § 1983  claim  for  violation  of  the  right  to  due  process  when  those \n\n 5 attempts have no impact on the conduct of a criminal trial.”  Id. at 355.  \n\n 6 We find DuFort readily distinguishable. \n\n 7   DuFort  involved  a  “paradigmatic  example  of  an  improperly \n\n 8 suggestive  lineup,”  in  which  detectives  allowed  a  criminal  suspect, \n\n 9 DuFort, to wear a red sweatshirt during a lineup despite knowing that \n\n10 the sole eyewitness, Park, had told them that, although she could not \n\n11 identify his face, one of the assailants was wearing a red sweatshirt \n\n12 during the commission of the crime.  Id. at 348.  Park then selected \n\n13 DuFort out of the lineup but did so based solely on her knowledge \n\n14 that  the  assailant  was  wearing  a  red  sweatshirt.    During  the \n\n15 subsequent criminal trial of DuFort, Park could not identify DuFort \n\n16 and  testified  that  she  only  selected  DuFort  at  the  lineup  due  to  his \n\n17 distinctive clothing.  Id.   \n\n18 DuFort  was  acquitted  and  sued  the  detectives  claiming  that \n\n19 their manipulation of the lineup violated his right to a fair trial.  We \n\n20 rejected the claim, noting that evidence fabrication claims rest on “the \n\n21 right to have one’s case tried based on an accurate evidentiary record \n\n22 that has not been manipulated by the prosecution.”  Id. at 355.  We \n\n23 concluded  that  there  was  no  such  defect  in  DuFort’s  trial  record  in \n\n 43  No. 17‐1859\n\n 1 light  of  Park’s  unequivocal  and  unchallenged testimony  to  the  jury \n\n 2 that she only identified DuFort because of his clothing: “the evidence \n\n 3 that  DuFort  claims  was  withheld  or  misrepresented  was  in  fact \n\n 4 disclosed  in  a  straightforward  manner  at  the  trial:  the  prosecution \n\n 5 elicited testimony from [the witness] that she recognized DuFort not \n\n 6 by his face, but by his clothing.”  Id.  Consequently, in DuFort, the jury \n\n 7 was  presented  with  the  full  universe  of  information,  despite  any \n\n 8 earlier police misconduct.  Indeed, we noted that it was “undisputed \n\n 9 that [the] attempt [to distort the trial record] failed.”  Id. \n\n10 DuFort is far afield from the instant case because it is not clear \n\n11 (and  certainly  not  undisputed)  that  Detective  Solomeno’s  allegedly \n\n12 false  DD‐5  report  had  “no  impact  on  the  conduct  of  [Bellamy’s] \n\n13 criminal trial.”  DuFort, 874 F.3d at 355. (emphasis added).  Although \n\n14 Walker did not identify Bellamy as the assailant at trial, there was an \n\n15 unacceptable risk, due only to the allegedly fabricated DD‐5, that the \n\n16 jury  was  left  with  the  potentially  incorrect  impression  that  she  had \n\n17 done so previously.  During Solomeno’s testimony, ADA Guy elicited \n\n18 the  fact  that  Solomemo  had  prepared  a  DD‐5  to  memorialize  the \n\n19 interview  with  Walker.  Trial  Tr.  802.  While  ADA  Guy  did  not \n\n20 introduce the DD‐5 into evidence, he then asked Walker during her \n\n21 testimony, “didn’t you tell Detective Solomeno and Detective Gillen \n\n22 that you recognized that person as Kareem?”  Trial Tr. 1005.  Despite \n\n23 Walker’s response of “No,” the jury could have viewed ADA Guy’s \n\n 44  No. 17‐1859\n\n 1 question itself as suggesting that Walker did in fact tell the detectives \n\n 2 that it was Bellamy she saw and that ADA Guy had a good faith basis \n\n 3 for asking the question.  And ADA Guy would have had no basis to \n\n 4 ask that question if Detective Solomeno had not provided him with \n\n 5 the  allegedly  fabricated  DD‐5.    We  have  previously  noted  that,  in \n\n 6 contexts  such  as  these,  “defense  counsel’s  unanswered  questions \n\n 7 about prior inconsistent statements [may] likely alert[] the jury to the \n\n 8 issue of the reliability of [the] testimony,” and, even where “the jury \n\n 9 was  told  that  the  lawyer’s  questions  are  not  evidence  .  .  .  the  sting \n\n10 survives such instructions.”  See Washington v. Schriver, 255 F.3d 45, 61 \n\n11 (2d  Cir.  2001)  (internal  quotation  marks  omitted).21    Significantly, \n\n12 ADA Guy then closed the loop in summation when he argued to the \n\n13 jury  that  it  should  take  stock  of  what  Walker  said  in  her  interview \n\n14 with Detectives Solomeno and Gillen.  Trial Tr. 1122–23; see also Trial \n\n15 Tr. 1144.22 \n\n16   Further  evidence  supports  the  material  impact  of  the  Walker \n\n17 DD‐5 on Bellamy’s conviction.  After the trial, ADA Guy stated that \n\n\n\n  To analogize to DuFort, it would be as if DuFort’s prosecutor asked \n 21\n\n Park:  “Isn’t it true that you told the detectives that you recognized DuFort \n wholly apart from his clothing?”  But DuFort’s prosecutor asked no such \n thing. \n   An  illustration  of  the  potential  for  confusion  caused  by  Walker’s \n 22\n\n testimony  is  that,  in  resolving  Bellamy’s  petition  for  habeas  corpus,  the \n federal  district  court  incorrectly  stated  that  at  trial  “[t]hree  witnesses \n identified petitioner as present at [t]he scene of the murder.”  App’x 613. \n\n 45  No. 17‐1859\n\n 1 the DD‐5 was “most helpful” to the prosecution.  App’x 1752.  As he \n\n 2 wrote in a post‐trial “commendation letter” to NYPD Commissioner \n\n 3 William Bratton praising Detectives Solomeno and Gillen’s conduct \n\n 4 specifically with respect to the Walker DD‐5: \n\n 5 [Detectives Solomeno and Gillen] also helped locate a \n 6 previously  unknown  (second)  eye‐witness  to  the \n 7 murder and interviewed her in the midst of my trial, \n 8 and helped secure her appearance, too.  She proved to \n 9 be fairly uncooperative, but because your detectives had \n10 prepared a detailed DD‐5 of their conversation with her, she \n11 had less “wiggle” room, and in the end what she had told \n12 the detectives proved most helpful. \n\n13 App’x 1752 (emphasis added).  It is therefore plain that ADA Guy, for \n\n14 his  part,  thought  that  the  DD‐5  provided  to  him  by  Detective \n\n15 Solomeno was material to Bellamy’s conviction.  See also Guy Dep. Tr. \n\n16 208 (testifying that he only sent commendation letters “from time to \n\n17 time in a case that I thought merited a little pat on the back . . .  Not \n\n18 many, more than just two or three”).  Finally, it bears noting that the \n\n19 jurors apparently attached significance to Walker’s testimony because \n\n20 that testimony prompted their only request for a second readback of \n\n21 particular testimony during deliberations.  See Trial Tr. 1209, 1224–26.  \n\n22 Under these circumstances, we find that there is “an overwhelming \n\n23 probability  that  the  jury  [was]  unable  to  follow  the  court’s \n\n24 instructions”  that  the  lawyers’  questions  are  not  evidence,  and  “a \n\n25 strong likelihood that the effect of the evidence [was] devastating to \n\n 46  No. 17‐1859\n\n 1 the defendant.” Greer v. Miller, 483 U.S. 756, 766 n.8 (1987) (citation \n\n 2 omitted).  \n\n 3   Of course, it is entirely possible that Walker implicated Bellamy \n\n 4 to  the  detectives  and  that  her  later  denials  were  false,  and  that \n\n 5 Detective  Solomeno  simply  prepared  a  truthful  DD‐5  that  Walker \n\n 6 refused to sign.  But this is a quintessentially disputed fact issue, as \n\n 7 neither side contests, and it is a material one, as the record shows.  We \n\n 8 therefore conclude that, notwithstanding DuFort, Bellamy has raised \n\n 9 a material issue of fact as to the truth or fabrication of the contents of \n\n10 the  DD‐5  purportedly  memorializing  Detectives  Solomeno  and \n\n11 Gillen’s December 1, 2005 interview with Walker. \n\n12 iii. Carter’s Lineup Identification \n\n13 Bellamy  contends  that  Detective  Gillen  pressured  Carter  to \n\n14 identify  Bellamy  in  the  lineup  that  took  place  on  May  14,  1994.  \n\n15 Specifically,  Bellamy  contends  that  Carter  initially  was  indecisive \n\n16 about whether the assailant was in position one or two, but that Carter \n\n17 was  then  taken  to  another  room  with  Detective  Gillen  where \n\n18 Detective Gillen proceeded to put pressure on Carter to identify the \n\n19 individual in position one, which Carter ultimately did.  \n\n20 The  sole  direct  evidence  supporting  this  claim  appears  to  be \n\n21 Carter’s testimony at Bellamy’s § 440 proceeding, in which Carter, in \n\n22 recanting  his  trial  testimony,  testified  that  Detective  Gillen  pointed \n\n23 out  Bellamy  at  the  lineup  and  pressured  Carter  to  identify  him.  \n\n 47  No. 17‐1859\n\n 1 Subsequent  to  that  testimony,  however,  Carter  died,  and  Bellamy \n\n 2 concedes that Carter’s testimony at the § 440 proceeding will not be \n\n 3 admissible at trial.  Br. of Appellant at 24 n.10.  And, it is axiomatic \n\n 4 that, when reviewing a summary judgment determination, we may \n\n 5 only consider admissible evidence.  See Ehrens v. Lutheran Church, 385 \n\n 6 F.3d 232, 235 (2d Cir. 2004) (per curiam). Bellamy therefore relies only \n\n 7 on a claimed inference in his attempt to raise a genuine issue of fact \n\n 8 as  to  whether  Detective  Gillen  pressured  Carter  at  the  lineup.  \n\n 9 Bellamy  focuses  on  two  aspects  of  Detective  Gillen’s  testimony:  (i) \n\n10 that Detective Gillen told Bellamy to pat down his braids prior to the \n\n11 lineup; and (ii) that Carter then told Detective Gillen that the basis of \n\n12 his confusion as to whether the assailant was in position one or two \n\n13 was the braided hair of the individual in position one.  Consequently, \n\n14 Bellamy contends that it is “likely [that Gillen] suggested to Carter the \n\n15 braids explanation for why he had failed to recognize Number 1.”  Br. \n\n16 of  Appellant  at  41.    This  contention  is  pure  speculation  and  is \n\n17 therefore insufficient to raise a triable issue of fact.  See Harlan Assocs. \n\n18 v. Inc. Village of Mineola, 273 F.3d 494, 502 (2d Cir. 2001).  We affirm \n\n19 the district court’s dismissal of this claim of misconduct. \n\n20 b. Evidence Withholding Claims \n\n21 When  police  officers  withhold  exculpatory  or  impeaching \n\n22 evidence from prosecutors, they may be held liable under § 1983 for \n\n23 violating the disclosure requirements of Brady v. Maryland, 373 U.S. \n\n 48  No. 17‐1859\n\n 1 83 (1963).23  See Bermudez v. City of New York, 790 F.3d 368, 376 n.4 (2d \n\n 2 Cir. 2015) (citing Walker v. City of New York, 974 F.2d 293, 299 (2d Cir. \n\n 3 1992)).    To  prevail  on  such  a  claim,  a  plaintiff  must  show  the \n\n 4 materiality  of  the  nondisclosed  evidence,  a  showing  that  “does  not \n\n 5 depend  on  factual  innocence,  but  rather  what  would  have  been \n\n 6 proven absent the violation . . . [with] reference to the likely effect that \n\n 7 the suppression of [the] particular evidence had on the outcome of the \n\n 8 trial.”  Poventud v. City of New York, 750 F.3d 121, 134 (2d Cir. 2014) (en \n\n 9 banc)  (internal  quotation  marks  and  emphasis  omitted).    Stated \n\n10 differently,  to  show  prejudice  the  claimant  “must  demonstrate  a \n\n11 reasonable  probability  that,  had  the  evidence  been  disclosed,  the \n\n12 result of the proceeding would have been different.”  United States v. \n\n13 Ulbricht,  858  F.3d  71,  112  (2d  Cir.  2017)  (internal  quotation  marks \n\n14 omitted).  For example, a § 1983 plaintiff proceeding on a Brady theory \n\n\n  We have suggested, though without so concluding, that a civil Brady \n 23\n\n claim  requires  a  showing  that  the  non‐disclosure  was  intentional.    See \n Fappiano v. City of New York, 640 F. App’x 115, 118 (2d Cir. 2017 (summary \n order);  see  also  Darnell  v.  Pineiro,  849  F.3d  17,  36  (2d  Cir.  2017).    Even \n assuming  such  an  intent  requirement,  we  have  no  need  to  specifically \n address, at this stage, the detectives’ intent as to each of the alleged Brady \n violations  here.    This  is  because  of  the  evidence  in  the  record,  already \n discussed,  that  raises  material  issues  of  fact  as  to  whether  Detective \n Solomeno  and  Gillen’s  conducting  of  the  Abbott  investigation  was \n improper.    See  Manganiello  v.  City  of  New  York,  612  F.3d  149,  164  (2d  Cir. \n 2010) (permitting an inference of a detective’s malice because, “in light of \n the other evidence as to [the detective’s] conduct of the investigation, [the \n jury  would  be  entitled]  to  view  [the  detective’s]  misrepresentation  as \n indicative of [his] state of mind all along”). \n\n 49  No. 17‐1859\n\n 1 can  succeed  on  his  claim  if,  had  the  withheld  information  been \n\n 2 disclosed  prior  to  trial,  “he  would  have  been  acquitted  based  on \n\n 3 reasonable doubt or convicted on a lesser charge.”  Poventud, 750 F.3d \n\n 4 at 134–35. \n\n 5 Bellamy contends that Detectives Solomeno and Gillen violated \n\n 6 Brady  by  failing  to  disclose  to  prosecutors  four  categories  of \n\n 7 exculpatory or impeaching statements made by Sanchez and Walker \n\n 8 during the course of the investigation of the Abbott murder: first, that \n\n 9 in the weeks following the murder, Sanchez told Detective Gillen that \n\n10 she saw Bellamy in the C‐Town trying to buy beer on a day in which \n\n11 C‐Town did not (and legally could not) sell beer before noon, which \n\n12 could  only  have  been  a  Sunday  (rather  than  a  Saturday,  the  day \n\n13 Abbott  was  killed);  second,  that  Sanchez  identified  Terrill  Lee  to \n\n14 Detective  Gillen  as  the  person  that  she  saw  with  Bellamy  in  the  C‐\n\n15 Town on the morning of Abbott’s murder; third, that on the day of \n\n16 Abbott’s  murder  Sanchez  told  Detective  Gillen  that  she  “didn’t  see \n\n17 anything”  and  “didn’t  know  anything”;  and  fourth,  Detectives \n\n18 Solomeno  and  Gillen  failed  to  disclose  Walker’s  claimed  non‐\n\n19 identification of Bellamy at her December 1, 1995 interview as well as \n\n20 her  refusal  to  sign  the  DD‐5  attesting  that  she  had  so  identified \n\n21 Bellamy.  We address each in turn. \n\n 50  No. 17‐1859\n\n 1 i. Sanchez’s Sunday/Beer Statement \n\n 2 Bellamy contends that Detectives Solomeno and Gillen failed to \n\n 3 disclose to the prosecution statements Sanchez made to them during \n\n 4 the  investigation  of  the  Abbott  murder  that  the  day  in  which  she \n\n 5 reported  seeing  Bellamy  in  the  C‐Town  with  Abbott  was  a  Sunday \n\n 6 and  a  day  in  which  the  C‐Town  could  not  have  lawfully  sold  beer \n\n 7 prior to noon (which could only have been a Sunday).  See N.Y. Alco. \n\n 8 Bev. Cont. Law § 105‐a (1971) (amended 2006).  It is undisputed that \n\n 9 Abbott  was  killed  on  Saturday,  April  9,  1994.    Although  Sanchez’s \n\n10 several rounds of testimony in this legal saga have been consistently \n\n11 inconsistent, Sanchez more than once testified that she told detectives \n\n 51  No. 17‐1859\n\n1 that  she  saw  Bellamy  on  a  Sunday.24    During  Bellamy’s  §  440 \n\n2 proceeding, she repeatedly testified that Bellamy was trying to buy \n\n3 beer on a Sunday when he could not, and agreed that she “first told \n\n4 police that [she] saw Kareem Bellamy on a Sunday.”  First 440 Tr. 458–\n\n\n\n  Sanchez’s testimony as to which day she remembered seeing Bellamy \n 24\n\n has been, at best, confused.  At the grand jury, she testified that Bellamy \n bought beer on the day in question.  App’x 320–23.  And at trial, she was \n asked “[w]hat first caused you to notice the defendant inside that C‐Town \n that morning,” to which she responded, “[h]e was buying beer.”  Trial Tr. \n 641.  But, ADA Guy followed up with, “[d]id anything direct your attention \n to  the  defendant  that  morning,”  to  which  Sanchez  responded,  “[h]e  was \n buying beer on a Sunday—on a Saturday that day.”  Trial Tr. 642.  This self‐\n correction is curious, however, because it begs the question why it would \n have  been  notable  for  Sanchez  to  notice  that  Bellamy  was  specifically \n buying  beer  on  a  Saturday.    Sanchez  sowed  further  confusion  during  the \n § 440 proceeding, where she unequivocally testified that, on the day of the \n murder, Bellamy “was trying to buy beer on a day he couldn’t buy beer,” \n clarified that that day was a Sunday, and recalled that the C‐Town manager \n even told Bellamy that “you can’t buy beer.”  First 440 Tr. 453–60, 490–91.  \n Her  story  got  more  confusing  at  her  deposition  in  this  case,  when  she \n continued  to  adamantly  assert  that  she  saw  Bellamy  on  “a  day  that  you \n couldn’t buy beer,” but also that she was certain that the day was a Saturday \n (a day in which you could buy beer).  Sanchez Dep. Tr. 24–27.  Sanchez then \n testified,  for  the  first  time,  that  she  specifically  remembers  it  being  a \n Saturday because  she “freshen[ed] up [her]  memory and  speaking to the \n members of [her] family it was a Saturday because [a family member named \n Julio]  was  outside  mechanicking  on  the  block.”    Sanchez  Dep.  Tr.  26–27.  \n She even testified that “I told [my family] it was Sunday [and] they said no \n Linda,  it  wasn’t  Sunday  it  was  Saturday  .  .  .  the  guy  Julio  was  outside \n mechanicking and he remember clearly it was Saturday.”  Sanchez Dep. Tr. \n 139–40.  Despite accepting her family’s correction that it was a Saturday, \n Sanchez nevertheless vividly remembered that Bellamy was trying to buy \n beer on a day that C‐Town could not sell beer.  Indeed, she remembered \n that Bellamy was upset because he could not buy beer, “I just know he had \n a look on his face, just body language.”  Sanchez Dep. Tr. 37. \n\n 52  No. 17‐1859\n\n 1 59.    She  reaffirmed  this  testimony  in  her  deposition  in  this  case, \n\n 2 testifying that “[a]t some point” she told Detective Gillen that Bellamy \n\n 3 was trying to buy beer on the same morning of the murder and that \n\n 4 the manager told Bellamy that he could not do so.  Sanchez Dep. Tr. \n\n 5 37.    Although  both  detectives  deny  any  recollection  of  these \n\n 6 statements by Sanchez, First 440 Tr. 912–13; Gillen Dep. Tr. 162–65; \n\n 7 Solomeno  Dep.  Tr.  116–17,  Sanchez’s  testimony  both  at  the  §  440 \n\n 8 proceeding and her deposition create a triable question of fact as to \n\n 9 whether the statements were made to either of the detectives (and not \n\n10 disclosed to the prosecution). \n\n11 The question then becomes one of materiality.  We believe that \n\n12 disclosure of the above statements would have significantly increased \n\n13 the defense’s chances of sowing a reasonable doubt in the jury’s mind \n\n14 about  Bellamy’s  guilt.    As  identified  in  detail,  see  infra  note  24, \n\n15 Sanchez,  a  key  state  witness,  has  consistently  held  the  inconsistent \n\n16 positions that she is certain that the morning she saw Bellamy in the \n\n17 C‐Town was a day in which the C‐Town could not lawfully sell beer, \n\n18 but also that the morning was a Saturday.  Had defense counsel been \n\n19 able to impeach Sanchez with that obvious inconsistency in front of \n\n20 the jury it would have been of great value to the defense, given how \n\n21 relatively thin the overall evidence was against Bellamy.   \n\n22 Indeed,  both  ADAs  Guy  and  Antignani,  as  well  as  Detective \n\n23 Solomeno,  conceded  in  their  depositions  the  materiality  of  any \n\n 53  No. 17‐1859\n\n 1 statements by Sanchez that she saw Bellamy on a day in which the C‐\n\n 2 Town could not lawfully sell beer.  ADA Guy testified that, if he had \n\n 3 known about them, he would have likely turned over such statements \n\n 4 precisely “so that the defense attorney could explore her confusion as \n\n 5 to  the  date.”    Guy  Dep.  Tr.  127.    He  continued:  “if  [Sanchez] \n\n 6 remembered that it was a Sunday because you’re not allowed to sell \n\n 7 beer on a Sunday before noon, that might give more credence to it,” \n\n 8 and  “[i]f  she  had  said  that  to  Detective  Gillen  .  .  .  [he]  presumably \n\n 9 would  have  written  that  in  the  DD‐5.”    Guy  Dep.  Tr.  126–27.  \n\n10 Detective  Solomeno  also  agreed,  evidenced  by  his  deposition \n\n11 testimony  that  if  he  had  heard  Sanchez  make  these  statements  he \n\n12 would  have  recorded  them.    Solomeno  Dep.  Tr.  117.    As  did  ADA \n\n13 Antignani,  who  testified  at  his  deposition  that  “if  in  fact,  Linda \n\n14 Sanchez said that to John Gillen, then I think John Gillen should have \n\n15 said it.”  Antignani Dep. Tr. 86–87.   \n\n16 We  therefore  conclude  that  there  is  sufficient  evidence  from \n\n17 which a jury could reasonably determine that the nondisclosure of the \n\n18 Sanchez Sunday/beer statements, if they were made to the detectives \n\n19 (another  jury  question),  were  actionable  Brady  violations.    Bellamy \n\n20 has therefore raised a triable issue of fact as to this allegation. \n\n21 ii. Sanchez’s Identification of Terrill Lee \n\n22 Bellamy contends that Detective Gillen failed to disclose that, \n\n23 during  the  investigation,  Sanchez  identified  Terrill  Lee  as  the \n\n 54  No. 17‐1859\n\n 1 individual  with  Bellamy  in  the  C‐Town  on  the  day  of  Abbott’s \n\n 2 murder.    The  contention  centers  on  Sanchez’s  testimony  during \n\n 3 Bellamy’s § 440 proceeding in which she testified that, following the \n\n 4 lineup,  a  detective  showed  her  a  Polaroid  photo  of  Lee,  whom  she \n\n 5 then identified to the detective as the person she saw with Bellamy in \n\n 6 the C‐Town on the morning of Abbott’s murder.25  First 440 Tr. 468; \n\n 7 see also Gillen Dep. Tr. 170 (discussing that Lee had a Polaroid taken \n\n 8 at the precinct). \n\n 9 The parties dispute whether Detective Gillen showed Sanchez \n\n10 a photo of Lee (and thus whether Sanchez identified Lee to Detective \n\n11 Gillen).   Although Sanchez  so  testified  at  the § 440  proceeding,  she \n\n12 subsequently did not recall being shown Lee’s photo when testifying \n\n13 at  her  deposition  in  this  case.    Sanchez  Dep.  Tr.  45–46.    However, \n\n14 despite her lack of recollection then (seven years later, and more than \n\n15 twenty years from the alleged incident), she also testified that she had \n\n16 no reason to think she did not tell the truth when she so testified at \n\n\n  Defendants contend that the evidence cannot establish that Detective \n 25\n\n Gillen  was  the  “detective”  that  Sanchez  referenced  when  she  was \n purportedly shown the Lee photo.  Br. of Appellees at 53 (relying on the \n fact that Sanchez’s testimony only uses the pronoun “they”).  The argument \n is meritless.  Sanchez made clear that it was “one” of the “detective[s]” who \n showed her the photo “after the lineup.”  First 440 Tr. 468.  And the record \n makes plain that Detective Gillen was the only detective at the lineup and \n that he oversaw the lineup.  See Trial Tr. 502–09; App’x 293; First 440 Tr. \n 1109.    At  the  very  least,  we  would  be  required  at  this  stage  to  infer  that \n Sanchez’s testimony referenced Detective Gillen.  Ultimately, however, the \n question is for the jury to decide. \n\n 55  No. 17‐1859\n\n 1 the  §  440  proceeding.    Sanchez  Dep.  Tr.  45–46.    While  Detective \n\n 2 Solomeno and ADAs Antignani and Guy each testified that someone \n\n 3 should  have  shown  Lee’s  photo  to  Sanchez,  Solomeno  Dep.  Tr.  169; \n\n 4 Antignani Dep. Tr. 122–23; Guy Dep. Tr. 76–77, Detective Gillen and \n\n 5 ADAs  Antignani  and  Guy  each  testified  that  they  did  not  show \n\n 6 Sanchez a photo of Lee and that they do not know if anyone else did.  \n\n 7 First 440 Tr. 865, 877 (Gillen); First 440 Tr. 1111, 1151–52, 1164, 1165 \n\n 8 (ADA Antignani); First 440 Tr. 1178, 1210–11 (ADA Guy); Gillen Dep. \n\n 9 Tr. 170.    \n\n10 Although a close question, we conclude that Bellamy has raised \n\n11 a genuine disputed issue of fact as to whether Sanchez told Detective \n\n12 Gillen  that  Lee  was  the  individual  with  Bellamy  (and  therefore \n\n13 whether Detective Gillen failed to disclose such).  See Del. & Hudson \n\n14 Ry. Co. v. Consolidated Rail Corp., 902 F.2d 174, 177–78 (2d Cir. 1990) \n\n15 (summary judgment non‐movant need only demonstrate “that there \n\n16 is  some  evidence  which  would  create  a  genuine  issue,”  meaning \n\n17 “more  than  a  scintilla  of  evidence”  and  “more  than  some \n\n18 metaphysical doubt as to the material facts” (internal quotation marks \n\n19 omitted)). \n\n20 The district court came to no conclusion as to the state of the \n\n21 factual record on this allegation, and rather concluded that “even if \n\n22 Sanchez had identified [Lee] as the plaintiff’s companion, it is difficult \n\n 56  No. 17‐1859\n\n 1 to  see  how  that  would  have  been  helpful  to  [Bellamy].”    2017  WL \n\n 2 2189528, at *36.  We disagree.   \n\n 3 Because  the  record  makes  plain  that  the  detectives  had  no \n\n 4 suspicions  that  Lee  was  involved  in  the  Abbott  murder,  see  Gillen \n\n 5 Dep. Tr. 170–71; see also Antignani Dep. Tr. 146–47; Guy Dep. Tr. 69–\n\n 6 72, any identification of Lee by Sanchez as being in the C‐Town with \n\n 7 Bellamy  would  seriously  undermine  the  reliability  of  Sanchez’s \n\n 8 placement of Bellamy in the store on the morning of Abbott’s murder.  \n\n 9 If  Lee  was  not  with  Bellamy  on  the  morning  in  question—as  the \n\n10 detectives seemingly concluded—and if Bellamy was with Lee at the \n\n11 time Sanchez had in mind during her trial testimony, Sanchez must \n\n12 have  been  confused  about  which  morning  she  saw  Bellamy,  a  not \n\n13 unlikely possibility, as previously discussed in depth, see infra note 24, \n\n14 and  as  one  particular  exchange  highlights.26    And  Sanchez’s \n\n15 identification  of  Lee  to  Detective  Gillen  would  be  material  even  if \n\n16 Sanchez was wrong about her identification of Lee because it would \n\n17 call into question Sanchez’s general recollection of the morning of the \n\n\n  “Q: [Y]ou had seen two people that Sunday?  A: Yes.  Q: Correct. When \n 26\n\n you  say  the  other  guy  are  you  referring  to  the  other  guy  you  saw  that \n Sunday?  A: The other guy that was with Kareem . . . .  Q: Where you shown \n a photograph of this other guy?  A: Yes.  Q: Okay. And what did—what \n kind of photograph was it?  A: It’s a Polaroid . . . .  Q: So they told you that \n the person in the photograph was Terrell Lee?  A: Yes.  Q: Well, just—I just \n want to be clear.  And you told them that the person in that Polaroid photo \n who they told you was Terrell Lee was the person you saw together with \n Kareem; is that correct?  A: Yes.” 440 Tr. 464–68.  \n\n 57  No. 17‐1859\n\n 1 Abbott murder, including her identification of Bellamy.  Either way, \n\n 2 had the defense known that Sanchez had at one point contended that \n\n 3 Lee was the person with Bellamy on the morning of the murder, the \n\n 4 defense  would  have  had  an  important  additional  tool  of  cross‐\n\n 5 examination. \n\n 6 Consequently, viewing the evidence in Bellamy’s favor as we \n\n 7 must at this stage, we think that Bellamy has raised a genuine issue of \n\n 8 material  fact  as  to  whether  Detective  Gillen,  in  violation  of  Brady, \n\n 9 failed to disclose Sanchez’s identification of Lee.  \n\n10 iii. Sanchez’s  Didn’t  Know/See  Anything \n11 Statements \n\n12 Bellamy  contends  that  Detective  Gillen  failed  to  disclose \n\n13 statements Sanchez made on the morning of the Abbott murder that \n\n14 she  “didn’t  know  anything”  and  “didn’t  see  anything.”    Bellamy \n\n15 grounds  this  contention  on  Sanchez’s  testimony  at  Bellamy’s  §  440 \n\n16 proceeding, where Sanchez testified that on the morning of Abbott’s \n\n17 murder, certain detectives (including Detective Gillen) “came in the \n\n18 [C‐Town] supermarket.  I didn’t speak to them they just came in and \n\n19 they said do you know anything.  I said no . . . I said no, I didn’t know \n\n20 anything.”  First 440 Tr. 453; see also First 440 Tr. 459 (Sanchez agreeing \n\n21 with the statement that “the police came in on the day of the murder \n\n22 and  [she]  said  [she]  didn’t  see  anything”).    These  de  minimis \n\n23 statements,  even  if  they  were  made  (recall  that,  at  trial,  Sanchez \n\n 58  No. 17‐1859\n\n 1 denied  speaking  with  officers  the  morning  of  the  murder),  are \n\n 2 manifestly  immaterial  principally  because  nothing  in  the  record \n\n 3 shows that Sanchez had any reason to think that anything was afoot \n\n 4 when  Detective  Gillen  first  entered  the  C‐Town  that  morning.  \n\n 5 Indeed,  Sanchez  testified  at  trial  that  she  did  not  learn  of  Abbott’s \n\n 6 murder  until  a  week  later.    Trial  Tr.  745;  see  also  Trial  652–53.27  \n\n 7 Consequently,  at  that  time,  from  her  perspective,  Sanchez  did  not \n\n 8 “know”  or  “see”  anything  out  of  the  ordinary.    Disclosure  of  these \n\n 9 statements  would  therefore  not  have  served  to  materially  impeach \n\n10 Sanchez or exculpate Bellamy.  We affirm the district court’s dismissal \n\n11 of this Brady contention. \n\n12 iv. Walker’s December 1, 2005 Statements \n\n13 Apart from Bellamy’s claim that Detective Solomeno fabricated \n\n14 the contents of the DD‐5 purportedly memorializing the December 1, \n\n15 2005 interview of Veronica Walker, see infra at pp. 39–46, Bellamy also \n\n16 brings  a  Brady  claim  challenging  Detectives  Solomeno  and  Gillen’s \n\n\n\n   Bellamy  contends  that  Sanchez  “admitted  she  learned  of  Abbott’s \n 27\n\n murder  ‘when  the  cops  came  inside  the  C‐Town  to  ask  questions’  about \n Abbott.”  Br. of Appellants 44.  But, Sanchez’s testimony makes clear that \n she only learned about any incident of note from JJ, the C‐Town deli clerk, \n who told her about the subject of the officers’ visit only after “the cops were \n already  gone.”    First  440  Tr.  493.    Consequently,  although  Sanchez’s \n testimony has been inconsistent as to whether she first learned of the Abbott \n murder  on the  day of April  9, 1994 or in  the  week  thereafter,  there  is no \n evidence that she knew of the incident prior to interacting with detectives \n on the morning of April 9.  \n\n 59  No. 17‐1859\n\n 1 failure to disclose the statements he claims that Walker actually did \n\n 2 make  during  that  interview.    See  App’x  62  ¶¶  183–200;  App’x  93  ¶ \n\n 3 379.    Most  principally,  Bellamy  challenges  the  detectives’  failure  to \n\n 4 disclose what Walker testified were her unequivocal statements that \n\n 5 Bellamy  was  not  the  person  she  saw  on  the  morning  of  Abbott’s \n\n 6 murder, as well as Walker’s refusal to sign Detective Solomeno’s DD‐\n\n 7 5 because the contents, in her view, were not true.  \n\n 8 The Defendants did not seek summary judgment on this claim, \n\n 9 see App’x 734–38, and therefore it was error for the district court to \n\n10 have  dismissed  it  without  providing  Bellamy  “notice  and  a \n\n11 reasonable time to respond.”  Fed. R. Civ. P. 56 (f)(2).  This is sufficient \n\n12 by itself to vacate the district court’s dismissal of this claim.   \n\n13 We would arrive at the same outcome even if the Defendants \n\n14 had sought summary judgment on this claim.  For similar reasons that \n\n15 we concluded that Bellamy has raised a triable issue of fact as to his \n\n16 evidence  fabrication  claim  premised  on  the  DD‐5  following  the \n\n17 Walker interview, we conclude that Bellamy has raised a triable issue \n\n18 as  to  the  related  Brady  claim.    Walker’s  testimony  raises  a  genuine \n\n19 disputed issue as to whether Walker affirmatively told the detectives \n\n20 that  the  individual  she  saw  was  not  Bellamy,  and  both  detectives \n\n21 admit that Walker refused to sign the DD‐5 and that they did not tell \n\n22 ADA  Guy  that  she  had  so  refused.    If  her  denial  existed  from  the \n\n23 outset (which we hold to be a jury question), then its disclosure would \n\n 60  No. 17‐1859\n\n 1 have  weakened  ADA  Guy’s  examination  while  permitting  the \n\n 2 criminal defense team to refresh Walker’s recollection as to whether \n\n 3 earlier she firmly denied seeing Bellamy, a fact that did not come out \n\n 4 at trial.  Thus, this claim even if it had been challenged at summary \n\n 5 judgment, should not have been dismissed. \n\n 6 II. Monell Claims Against the City of New York  \n\n 7 We now turn to whether the district court properly dismissed \n\n 8 Bellamy’s  §  1983  claims  against  the  City  of  New  York.    Although \n\n 9 § 1983 subjects only “person[s]” to liability, 42 U.S.C. § 1983, Monell \n\n10 established that “a municipality [such as the City of New York] is a \n\n11 person within the meaning of Section 1983,” Vives v. City of New York, \n\n12 524 F.3d 346, 350 (2d Cir. 2008).  To establish liability under Monell, a \n\n13 plaintiff must show that he suffered the denial of a constitutional right \n\n14 that was caused by an official municipal policy or custom.  See Wray \n\n15 v. City of New York, 490 F.3d 189, 195 (2d Cir. 2007).   \n\n16 As  relevant  here,  Bellamy  proffers  two  theories  of  Monell \n\n17 liability:  (i)  the  prosecution  failed  to  disclose  the  full  relocation \n\n18 benefits Sanchez received from the QCDA’s office, a Brady violation \n\n19 that was caused by a deliberate information barrier imposed by the \n\n20 QCDA  that  purposefully  kept  prosecutors  unaware  of  the  full \n\n21 benefits  received  by  witnesses  in  its  witness  protection  program \n\n22 (“WPP”); and (ii) ADA Guy’s improper summation was a due process \n\n23 violation  caused  by  the  QCDA  office’s  failure  to  discipline \n\n 61  No. 17‐1859\n\n1 summation  misconduct.28    The  City  challenges  Bellamy’s  Monell \n\n2 claims  on  two  general  grounds:  (i)  the  City  is  not  responsible  as  a \n\n3 matter of law under Monell for the alleged policies of the QCDA; and \n\n4 (ii) regardless, Bellamy did not sufficiently establish underlying due \n\n5 process  violations  to  withstand  summary  judgment.29    We  disagree \n\n6 with  both  contentions  and  vacate  the  district  court’s  dismissal  of \n\n7 Bellamy’s Monell claims. \n\n\n\n\n  Bellamy also pled a claim that the QCDA’s office failed to discipline \n 28\n\n Brady  violations,  specifically  as  to  its  prosecutors’  failure  to  diligently \n search  out  the  benefits  received  by  its  witnesses.    Defendants  did  not \n specifically move for summary judgment on this claim and the district court \n did not address it, which means that its dismissal was improper.  See Fed. \n R. Civ. P. 56(f)(2).  Bellamy affirmed on appeal his intention to proceed on \n this  claim,  yet  Defendants  did  not  address  it  in  their  brief.    See  Br.  of \n Appellant 48 n.15; Reply Br. of Appellant 11 n.5.  We decline to address this \n claim in the first instance. \n  Whether the QCDA in fact had the challenged policies is not at issue \n 29\n\n before us.  Following the denial of the Defendants’ motion to dismiss, the \n district  court  bifurcated  discovery  on  Bellamy’s  non‐Monell  and  Monell \n claims  by  allowing  the  completion  of  non‐Monell  discovery  but  limiting \n Monell  discovery  to  “the  question  whether  any  of  the  plaintiff’s  federal \n constitutional rights were violated by the actions of the district attorney’s \n office.”    Dkt.  No.  52.    Although  the  parties  subsequently  stipulated  to \n proceed  to  full  discovery  on  Bellamy’s  Monell  claims,  Dkt.  No.  112, \n including  as  to  the  existence  of  the  alleged  policies,  the  district  court \n subsequently  re‐imposed  the  discovery  stay  before  Bellamy  took  any \n Monell depositions pending resolution of the parties’ summary judgment \n motions.    See  Dkt.  No.  152.    Consequently,  Bellamy  has  yet  to  have  full \n discovery as to the existence of the alleged policies, and the City makes no \n argument regarding the existence of the policies on appeal.  \n\n 62  No. 17‐1859\n\n 1 a. The City of New York’s Liability Under Monell for the \n 2 Alleged Policies of the QCDA’s Office \n\n 3 The City argues that it cannot be held liable as a matter of law \n\n 4 for  any  constitutional  harms  inflicted  by  the  alleged  policies  of  the \n\n 5 QCDA’s office that give rise to Bellamy’s Monell claims because those \n\n 6 were not policies for which the City is responsible.  The district court \n\n 7 agreed, but we do not. \n\n 8 Monell  liability  attaches  only  where  an  infringement  of \n\n 9 constitutional  rights  is  caused  by  a  local  government  policy.    See \n\n10 Outlaw v. Hartford, 884 F.3d 351, 372–73 (2d Cir. 2018).  In searching \n\n11 for the proper local government that is subject to liability on a given \n\n12 Monell claim we look for “those official or governmental bodies who \n\n13 speak  with  final  policymaking  authority  . . .  concerning  the  action \n\n14 alleged to have caused the particular . . . violation at issue.”  Jett v. \n\n15 Dallas Ind. Sch. Dist., 491 U.S. 701, 737 (1989).  The issue for us is thus \n\n16 whether the City of New York is the “final policymaking authority” \n\n17 in  relation  to  the  alleged  QCDA  policies  at  issue  here:    the  WPP \n\n18 information  barrier  and  the  failure  to  discipline  summation \n\n19 misconduct.    The  City  argues,  as  the  district  court  concluded,  that \n\n20 pursuant  to  Van  de  Kamp  v.  Goldstein,  555  U.S.  335  (2009),  the \n\n21 challenged conduct of the QCDA’s office is necessarily a function of \n\n22 state  policies,  and  therefore  the  City  may  not  be  subject  to  Monell \n\n23 liability as a matter of law.  We think this argument overextends Van \n\n 63  No. 17‐1859\n\n 1 de  Kamp,  a  case  assessing  the  distinct  doctrine  of  prosecutorial \n\n 2 immunity, and that our controlling precedent plainly establishes that \n\n 3 the  City  may  be  held  liable  under  Monell  for  the  alleged  QCDA \n\n 4 policies at issue. \n\n 5 On  numerous  occasions  we  have  been  called  upon  to  assess \n\n 6 how  plaintiffs  may  pursue  claims  under  Monell  that  allege  that \n\n 7 policies  of  prosecutors’  offices  led  to  infringements  of  their \n\n 8 constitutional  rights.    To  adequately  explain  why  we  conclude  that \n\n 9 the City is a proper defendant with respect to Bellamy’s Monell claims \n\n10 here, a brief review of these cases will be helpful.     \n\n11 In  Baez  v.  Hennessy,  853  F.2d  73  (2d  Cir.  1988),  Baez  sued  an \n\n12 Onondaga County prosecutor, and the county under Monell, after the \n\n13 prosecutor improperly indicted Baez based on an erroneous reading \n\n14 of  a  grand  jury  vote  sheet.    We  affirmed  dismissal  of  both  claims, \n\n15 concluding  that  the  prosecutor  was  protected  by  absolute \n\n16 prosecutorial immunity and, relevant here, that the county was not a \n\n17 proper  party  for  a  Monell  claim.    As  to  the  latter  conclusion,  we \n\n18 reasoned  that  “[w]hen  prosecuting  a  criminal  matter,  a  district \n\n19 attorney  in  New  York  State,  acting  in  a  quasi‐judicial  capacity, \n\n20 represents the State and not the county.”  Id. at 77.  And because the \n\n21 prosecutor was representing the state, the county could not be held \n\n22 legally  responsible  for  injuries  that  the  prosecutor  had  caused.  \n\n23 Although  we  have  never  questioned  the  conclusion  in  Baez  that  a \n\n 64  No. 17‐1859\n\n 1 prosecutor  is  a  state  rather  than  a  local  representative  “[w]hen \n\n 2 prosecuting  a  criminal  matter,”  id.,  our  subsequent  cases  have \n\n 3 narrowed Baez in significant and relevant ways. \n\n 4 We began to cabin Baez in Gentile v. County of Suffolk, 926 F.2d \n\n 5 142 (2d Cir. 1991), where we affirmed a judgment concluding that the \n\n 6 County of Suffolk, rather than the state, was the responsible party for \n\n 7 purposes of Monell in relation to allegations that the county’s district \n\n 8 attorney’s  office  had  a  policy  of  ignoring  police  misconduct.    We \n\n 9 rejected the argument that, under Baez, the district attorney’s office’s \n\n10 conduct was a function of state rather than county policies because, \n\n11 unlike  in  Baez,  “the  County’s  liability  is  based  not  upon  a  specific \n\n12 decision of the District Attorney to prosecute but upon the County’s \n\n13 long  history  of  negligent  disciplinary  practices  regarding  law \n\n14 enforcement personnel.”  Id. at 152 n.5.  \n\n15 We  then  reaffirmed  and  further  developed  the  narrowing  of \n\n16 Baez  in  Walker  v.  City  of  New  York,  974  F.2d  293  (2d  Cir.  1992), \n\n17 specifically noting that Gentile “confined Baez to challenges to specific \n\n18 decisions of the District Attorney to prosecute.”  Id. at 301 (internal \n\n19 quotation  marks  omitted).    Moreover,  Walker  also  made  plain  that \n\n20 when  a  Monell  claim  challenges  policies  of  the  City  of  New  York’s \n\n21 “constituent  counties,”  the  City  is  a  proper  defendant.    Id.; see  also \n\n22 Ramos v. City of New York, 285 A.D.2d 284, 303 (1st Dep’t 2001).  Walker \n\n23 reversed the dismissal of Monell claims against the City of New York \n\n 65  No. 17‐1859\n\n 1 that alleged that the Kings County District Attorney’s office failed to \n\n 2 adequately  train  its  prosecutors  to  turn  over  exculpatory  evidence \n\n 3 and not to suborn perjury.  We concluded that in such an instance, \n\n 4 notwithstanding  Baez,  “the  district  attorney  is  a  municipal \n\n 5 policymaker,”  because  in  making  decisions  other  than  whether  to \n\n 6 prosecute  the  “district  attorney  acts  as  the  manager  of  the  district \n\n 7 attorney’s office,” which, we concluded, is a municipal function.  974 \n\n 8 F.3d at 301.  In Ying Jing Gan v. City of New York, 996 F.2d 522 (2d Cir. \n\n 9 1993), we reaffirmed Walker and clarified that a county prosecutor’s \n\n10 actions are a function of state policies, rather than city policies, only \n\n11 where plaintiff’s “claims center[] . . . on decisions whether or not, and \n\n12 on what charges, to prosecute,” and not where those claims focus “on \n\n13 the administration of the district attorney’s office.”  Id. at 536; see also \n\n14 Pinaud v. County of Suffolk, 52 F.3d 1139, 1153 n.14 (2d Cir. 1995). \n\n15 Subsequent  to  these  cases,  the  Supreme  Court  decided \n\n16 McMillian v. Monroe County, Alabama, 520 U.S. 781 (1997), a case that \n\n17 addressed  Monell  liability  outside  of  the  context  of  a  prosecutor’s \n\n18 office,  but  that  clarified  the  scope  of  analysis  for  Monell  claims \n\n19 generally.  The Court held that Monroe County, Alabama was not the \n\n20 relevant  policymaker  for  purposes  of  a  Monell  claim  that  asserted \n\n21 unconstitutional conduct of a Monroe County sheriff.   How the Court \n\n22 arrived at that conclusion is significant: it examined Alabama law in \n\n23 detail and concluded that the state was the relevant final policymaker \n\n 66  No. 17‐1859\n\n 1 because it had sufficient authority over the sheriff’s specific functions \n\n 2 at issue.  Id. at 786.  The Court relied heavily on the Alabama state \n\n 3 constitution,  for  example,  which  evinced  “‘the  framers’  intent  to \n\n 4 ensure that sheriffs be considered executive officers of the state.’”  Id. \n\n 5 at 789 (quoting Parker v. Amerson, 519 So.2d 442, 444 (Ala. 1987)).  The \n\n 6 relevant  lesson  from  McMillian  is  plain:    because  “the  States  have \n\n 7 wide  authority  to  set  up  their  state  and  local  governments  as  they \n\n 8 wish,” a search for the “final policymaking authority” under Monell \n\n 9 “is dependent on an analysis of state law.”  Id. at 786, 795. \n\n10 In Myers v. County of Orange, 157 F.3d 66 (2d Cir. 1998), in light \n\n11 of  McMillian’s  directive  to  delve  into  state  law  to  ascertain  a  final \n\n12 policymaker  for  purposes  of  Monell  liability,  we  revisited  our  cases \n\n13 discussed above that broadly applied Monell to prosecutors’ offices.  \n\n14 There,  we  addressed  Monell  claims  brought  against  the  New  York \n\n15 County  of  Orange  that  alleged  that  the  county’s  district  attorney’s \n\n16 office  had  an  unconstitutional  policy  of  refusing  to  entertain  cross‐\n\n17 complaints  by  complaining  witnesses.    Id.  at  69.    After  reviewing  a \n\n18 wealth of New York statutory and case law (which our earlier cases \n\n19 had  not  done),  we  reaffirmed  our  earlier  conclusions  that  “[u]nder \n\n20 New  York  law,  DAs  and  ADAs  are  generally  presumed  to  be  local \n\n21 county officers, not state officers,” and reiterated once again that Baez \n\n22 was a “narrow exception . . . [for] when a prosecutor makes individual \n\n23 determinations about whether to prosecute.”  Id. at 76–77. \n\n 67  No. 17‐1859\n\n 1 Because  we  have  never  doubted  the  rule  stemming  from  the \n\n 2 line of cases extending from Gentile and Walker to Myers, we have been \n\n 3 consistent in holding that the actions of county prosecutors in New \n\n 4 York  are  generally  controlled  by  municipal  policymakers  for \n\n 5 purposes  of  Monell,  with  a  narrow  exception  emanating  from  Baez \n\n 6 being  the  decision  of  whether,  and  on  what  charges,  to  prosecute.  \n\n 7 Thus, in this case, the rule from these cases requires the conclusion \n\n 8 that  the  conduct  Bellamy  challenges  is  a  result  of  municipal  rather \n\n 9 than  state  policymaking.    The  City  does  not  dispute  this  reasoning \n\n10 based  on  our  precedents,  informed  along  the  way  by  the  Court’s \n\n11 decision in McMillian.  The City’s sole contention is that our Walker \n\n12 line of cases was implicitly abrogated by the Supreme Court’s 2009 \n\n13 decision in Van de Kamp, “requir[ing] a different boundary between \n\n14 prosecutorial  and  administrative  functions  than  the  one  [we  have] \n\n15 previously set forth.”  Br. of Appellees at 67.  We disagree.  \n\n16 In  Van  de  Kamp,  plaintiff  Goldstein  obtained  a  vacatur  of  his \n\n17 state  murder  conviction  by  a  grant  of  federal  habeas  corpus  on  the \n\n18 ground that the prosecution failed to disclose to the defense that they \n\n19 had  offered  a  reduced  sentence  to  a  witness  that  provided  critical \n\n20 inculpatory testimony.  555 U.S. at 339.  As relevant here, Goldstein \n\n21 then filed a civil § 1983 claim against his prosecutors’ supervisors (as \n\n22 individuals),  arguing  that  they  failed  to  train  or  supervise  their \n\n23 prosecutors to prevent violations of the duty to disclose impeachment \n\n 68  No. 17‐1859\n\n 1 material.  Id. at 340.  The defendants moved to dismiss on the basis of \n\n 2 absolute  prosecutorial  immunity,  an  argument  the  district  court \n\n 3 rejected  on  the  ground  that  prosecutors  are  entitled  to  absolute \n\n 4 immunity  only  for  “prosecutorial”  functions,  not  “administrative” \n\n 5 ones, and that the failure‐to‐train allegations fell in the latter category.  \n\n 6 Id.  The Court of Appeals affirmed, 481 F.3d 1170 (9th Cir. 2007), but \n\n 7 the  Supreme  Court  reversed.    It  disagreed  with  the  lower  courts’ \n\n 8 conclusions  that  a  prosecutor  is  not  entitled  to  immunity  simply \n\n 9 because  her  challenged  conduct  can  be  labeled  “administrative.”  \n\n10 Rather,  the  inquiry  is  whether  the  prosecutor’s  conduct \n\n11 (administrative  or  otherwise)  was  “directly  connected  with  the \n\n12 conduct of a trial.”  555 U.S. at 344.  If so, the Court concluded, the \n\n13 conduct falls within the traditional immunity offered to prosecutors \n\n14 under long‐standing notions of federal common law. \n\n15 Although Van de Kamp said nothing about Monell or municipal \n\n16 liability, the City argues that Van de Kamp affects how Monell claims \n\n17 can proceed against prosecutors’ offices specifically.  Its argument is \n\n18 as follows.  In the Walker line of cases, we concluded that inherently \n\n19 prosecutorial  functions  (i.e.,  decisions  whether  to  prosecute)  are \n\n20 controlled by state policies for purposes of Monell, and other functions \n\n21 of the prosecutor are controlled by municipal policies.  For example, in \n\n22 Baez, the act of indicting based on a misread grand jury verdict form \n\n23 was  inherently  prosecutorial  and  therefore  a  state  function,  but,  in \n\n 69  No. 17‐1859\n\n 1 Walker, the failure to train on Brady obligations related to the district \n\n 2 attorney’s management of the office, and we therefore concluded that \n\n 3 was  a  municipal  function.    Consequently,  the  argument  goes,  our \n\n 4 Monell cases have drawn separate circles around “prosecutorial” and \n\n 5 “managerial” functions, with the former circle being state‐controlled \n\n 6 functions and the latter municipally‐controlled ones.  The argument \n\n 7 then goes that although our cases have narrowed the “prosecutorial” \n\n 8 circle  such  that  it  includes  only  the  prosecutor’s  decision  to  bring \n\n 9 charges, Van de Kamp expanded the circle of prosecutorial functions \n\n10 to  include  a  failure  to  train  on  Brady  obligations  (which,  the  City \n\n11 argues,  is  akin  to  Bellamy’s  arguments  here).    Thus,  the  argument \n\n12 concludes, because Bellamy’s claims pertain to conduct that now falls \n\n13 within  the  “prosecutorial”  circle,  and  New  York  concludes \n\n14 “prosecutorial”  conduct  is  a  state  function,  the  conduct  supporting \n\n15 Bellamy’s  Monell  claims  must  be  a  state  rather  than  a  municipal \n\n16 function.  We are unpersuaded. \n\n17 The  key  flaw  in  the  City’s  argument  is  its  unsupported \n\n18 assumption  that  the  circle  demarcating  what  is  a  “prosecutorial” \n\n19 function  for  purposes  of  prosecutorial  immunity  is  necessarily  the \n\n20 same  as  the  circle  New  York  has  chosen  to  demarcate  state  versus \n\n21 local  prosecutorial  functions.    But,  the  legal  question  of  when \n\n22 immunity  should  attach  is  an  entirely  separate  inquiry  from  which \n\n23 state entity is a final policymaker for Monell.  This was the reasoning \n\n 70  No. 17‐1859\n\n 1 adopted in Goldstein v. City of Long Beach, 715 F.3d 750 (9th Cir. 2013), \n\n 2 the lower court decision that followed the Supreme Court’s remand \n\n 3 in Van de Kamp.  Although the Court had rejected plaintiff’s individual \n\n 4 claims,  the  Ninth  Circuit  was  left  to  evaluate  plaintiff’s  remaining \n\n 5 Monell claims.  The defendants argued on remand, as the City does \n\n 6 here, that “Van de Kamp determines the outcome” of the Monell claims.  \n\n 7 Id.  at  760.    The  Ninth  Circuit  rejected  the  argument  because  “the \n\n 8 inquiries of prosecutorial immunity and state or local policymaking . \n\n 9 . . are separate.”  Id.  We agree.  In contrast to the immunity inquiry, \n\n10 Monell addresses not whether certain functions can open individuals to \n\n11 liability,  but  simply  which  governmental  entity  (the  state  or  the \n\n12 municipality)  is  responsible  for  a  given  function.    And  as  we  have \n\n13 discussed,  the  Supreme  Court  has  left  no  doubt  that  state  law,  not \n\n14 federal  law,  is  responsible  for  demarcating  that  division  of \n\n15 responsibility.  The McMillian court was worried about imposing “a \n\n16 uniform,  national  characterization”  of  state  actors,  concerned  that \n\n17 “such a blunderbuss approach would ignore a crucial axiom of our \n\n18 government: the States have wide authority to set up their state and \n\n19 local governments as they wish.”  520 U.S. at 795.  Consequently, the \n\n20 responsible entity for purposes of Monell liability must be ascertained \n\n21 by looking at how the relevant state elects to allocate responsibilities \n\n22 between itself and its subdivisions.  Id. \n\n 71  No. 17‐1859\n\n 1 The City’s contention, if adopted, would turn McMillian on its \n\n 2 head: it would require courts assessing Monell claims that challenge \n\n 3 the conduct of prosecutors to consider the way in which the federal \n\n 4 system  chooses  to  immunize  prosecutors  in  determining  which \n\n 5 functions  are  state  functions  and  which  are  local  ones.    Stated \n\n 6 differently,  under  the  City’s  formulation,  we  would  no  longer  be \n\n 7 looking to the intricacies of state law to decide a Monell claim against \n\n 8 a prosecutor’s office, as we did in Myers (at the express direction of \n\n 9 McMillian),  but  would  instead  look  to  Van  de  Kamp,  a  decision \n\n10 exclusively assessing federal common law and federal policy.30   \n\n11 Such a course would adversely affect state reliance interests as \n\n12 well:  New  York  appellate  courts  have  expressly  affirmed  our \n\n13 conclusions as to the content of New York law in Walker and Myers.  \n\n14 See Ramos, 285 A.D.2d at 303 (concluding as “firmly grounded in New \n\n15 York law,” the conclusion from Gentile, Walker, and Myers that “where \n\n16 prosecutors,  pursuant  to  policy  or  custom,  conceal  exculpatory \n\n17 evidence and commit other wrongs in order to secure a conviction, \n\n18 liability  rests  with  the  county  (or  for  New  York  City’s  constituent \n\n\n\n\n  The focus on federal common law was center stage in Van de Kamp.  \n 30\n\n See 555 U.S. at 340–41 (looking to Judge Learned Hand’s policy statements \n from “[o]ver a half century ago”); see also id. (relying on Imbler v. Pachtman, \n 424  U.S.  409  (1976),  the  Court’s  “first  opportunity  to  address  the  s  1983 \n liability of a state prosecuting officer,” which then relied on federal cases \n dating back to the mid‐19th‐century, id. at 420–22 & n.18)). \n\n 72  No. 17‐1859\n\n 1 counties,  the  City)”);  Johnson  v.  Kings  Cnty.  Dist.  Atty’s  Office,  308 \n\n 2 A.D.2d 278, 295–96 (2d Dep’t 2003) (same).   \n\n 3 Thus we conclude, consistent with our precedent, that the City \n\n 4 is the proper policymaking authority for purposes of Bellamy’s Monell \n\n 5 claims. \n\n 6 b. The Alleged Constitutional Violations of the QCDA’s \n 7 Office \n\n 8 Bellamy  proffers  two  underlying  constitutional  violations  for \n\n 9 which he claims the City is responsible: (i) the non‐disclosure to the \n\n10 prosecution (and therefore to the defense) of the full benefits Sanchez \n\n11 was promised as part of her participation in the QCDA’s WPP; and \n\n12 (ii) summation misconduct by ADA Guy.  We conclude that Bellamy \n\n13 has presented sufficient evidence of both violations to withstand the \n\n14 motion for summary judgment. \n\n15 i. Benefits Promised to Sanchez \n\n16 Bellamy  contends  that  Sanchez  was  promised  significantly \n\n17 more financial support from the QCDA than the $100 and undefined \n\n18 relocation benefits to which she testified at trial.  See Trial Tr. 633–35.  \n\n19 The district court, despite appearing to acknowledge that the record \n\n20 established that Sanchez was promised substantially more than that \n\n21 to  which  she  testified,  rejected  the  claim  because  the  promised \n\n22 “benefits did not arise until after the plaintiff’s trial, and did not affect \n\n23 the trial itself.”  2017 WL 2189528, at *40.  This was error. \n\n 73  No. 17‐1859\n\n 1 The record unmistakably raises a question of fact as to whether \n\n 2 Sanchez  was  promised,  prior  to  her  testifying,  substantially  more \n\n 3 than  she  ultimately  disclosed  during  her  testimony.    Specifically, \n\n 4 there  is  evidence  in  the  record  that  Sanchez  was  promised,  before \n\n 5 trial,  that  the  QCDA’s  office  would  relocate  her,  and,  in  doing  so, \n\n 6 would  pay  for  her  first  month’s  rent,  last  month’s  rent,  security \n\n 7 deposit, and a broker fee, totaling $2,800.  See Sanchez Dep. Tr. 79–97, \n\n 8 147–148; Dkt. No. 193‐1 at 291 (Sanchez testimony at the initial § 440 \n\n 9 proceeding).    Daniel  Cox,  the  WPP  administrator  who  worked \n\n10 directly  with  Sanchez,  testified  at  his  deposition  that  his  office \n\n11 generally  referred  to  this  as  “Seed  Money,”  and  that  he  would  tell \n\n12 program  participants  “early  when  you’re  starting  to  have \n\n13 conversations” that they would be receiving it.  Cox Dep. Tr. 43.  Cox \n\n14 clarified that he would tell participants about the seed money “at [the] \n\n15 first meeting,” which, as to Sanchez, would have been on November \n\n16 28, 1995, prior to her testifying.  Cox Dep. Tr. 100–01; but see Mansfield \n\n17 Dep.  Tr.  75–76  (“of  course”  we  would  make  no  specific  promises \n\n18 during the orientation).  In any event, Corporation counsel conceded \n\n19 at oral argument before us that a reasonable jury could conclude on \n\n20 this evidence that Cox promised Sanchez the seed money prior to her \n\n21 testifying.    Oral  Arg.  Rec.  at  36:04.    And,  ADA  Guy  testified  at  his \n\n22 deposition  that  he  was  never  aware  of  the  promised  seed  money, \n\n 74  No. 17‐1859\n\n 1 either at the time of trial or even at the time of his deposition in this \n\n 2 case.  Guy Dep. Tr. 138–39. \n\n 3 As corporation counsel’s concession makes plain, the City does \n\n 4 not seriously dispute any of the above and argues only that Bellamy \n\n 5 was not prejudiced by the lack of disclosure because the benefits that \n\n 6 were disclosed at trial provided a sufficient basis for defense counsel \n\n 7 to attack Sanchez’s credibility.  We disagree.  The potential for witness \n\n 8 bias is of course greater when the amount to be received is $2,800 as \n\n 9 opposed  to  $100  (4  x  $25/day),  particularly  for  a  witness  of  limited \n\n10 financial  means  like  Sanchez,  see  App’x  1622.    Further,  the  actual \n\n11 benefit promised was substantially larger than that to which Sanchez \n\n12 testified,  which  would  have  allowed  for  a  heightened  attack  on \n\n13 Sanchez’s truthfulness.  Moreover, ADA Guy both conceded that the \n\n14 promise of $2,800 of seed money was Brady material and explained \n\n15 why  the  information  was  particularly  probative  in  this  case:  “[The] \n\n16 dollar  amount  and  total  benefit  amount  is  at  odds  with  [Sanchez’s \n\n17 trial]  testimony.    So  it  might  affect  her  credibility  and  [if  I  were \n\n18 defense counsel] I might be able to make some use of that in asking \n\n19 the jury to disregard her or to at least challenge her credibility.”  Guy \n\n20 Dep.  Tr.  138–41.    Finally,  the  problem  was  exacerbated  when  ADA \n\n21 Guy, in his summation, noted the absence of evidence supporting the \n\n22 defense’s contention that Sanchez had a motive to lie out of bias.  See \n\n23 Trial Tr. 1139 (“Why would she come in and lie about the defendant?  \n\n 75  No. 17‐1859\n\n 1 Is there any evidence that she had any motivation to come in and lie \n\n 2 about the defendant?”); Trial Tr. 1144 (“There is no evidence she is a \n\n 3 liar.”). \n\n 4 We therefore conclude that Bellamy raised a material issue of \n\n 5 fact as to whether his Brady rights were violated by the QCDA’s non‐\n\n 6 disclosure of the full scope of benefits promised to Sanchez prior to \n\n 7 her testimony.  And, in light of our conclusion that the City of New \n\n 8 York may be held liable for this conduct, we vacate the district court’s \n\n 9 dismissal of this Monell claim.  \n\n10 ii. ADA Guy’s Summation \n\n11 Bellamy  contends  that  ADA  Guy  made  numerous  improper \n\n12 remarks  during  his  summation  sufficient  to  render  Bellamy’s \n\n13 subsequent  conviction  a  denial  of  due  process.    The  district  court \n\n14 disagreed, largely on its conclusion that ADA Guy’s “comments were \n\n15 garden variety summation comments.”  2017 WL 2189528, at *41.  We \n\n16 disagree and conclude that the impact of the summation on the trial \n\n17 presents a jury question. \n\n18 In United States v. Certified Environmental Services, Inc., 753 F.3d \n\n19 72 (2d Cir. 2014), we discussed the relevant standard: \n\n20 When reviewing claims of prosecutorial misconduct \n21 based on inappropriate remarks in the Government’s \n22 .  .  .  summation[],  we  will  reverse  if  the  misconduct \n23 caused substantial prejudice by so infecting the trial \n24 with unfairness as to make the resulting conviction a \n25 denial  of  due  process.    In  assessing  whether \n\n 76  No. 17‐1859\n\n 1 prosecutorial  misconduct  caused  ‘substantial \n 2 prejudice,’  this  Court  has  adopted  a  three‐part  test, \n 3 which  considers  the  severity  of  the  misconduct,  the \n 4 measures  adopted  to  cure  the  misconduct,  and  the \n 5 certainty of conviction absent the misconduct. \n\n 6 Id. at 95 (internal quotation marks and citations omitted).  \n\n 7 Bellamy contended at summary judgment that ADA Guy made \n\n 8 fourteen  improper  summation  remarks.    App’x  1969–72.    Bellamy \n\n 9 contends these remarks were sufficiently improper to entitle him to \n\n10 relief under § 1983, even though his counsel did not object to them \n\n11 during  trial  (or  afterwards).    While  we  are  not  persuaded  that  the \n\n12 majority of the remarks identified by Bellamy were either improper \n\n13 or could have affected the trial, we believe that certain remarks were \n\n14 sufficiently  problematic  to  require  that  they  be  assessed  by  a  jury \n\n15 (despite the absence of a contemporaneous objection by trial counsel).  \n\n16 The  most problematic  is  Bellamy’s  contention  that  ADA Guy \n\n17 told the jury near the end of his summation: “I know who committed \n\n18 the murder.”  Trial Tr. 1149.  This statement was clearly improper and \n\n19 severely prejudicial if it was made.  “It is unprofessional conduct for \n\n20 the prosecutor to express his or her personal belief or opinion as to \n\n21 the . . . evidence or guilt of the defendant.” United States v. Modica, 663 \n\n22 F.2d 1173, 1178 (2d Cir. 1981) (per curiam) (quoting ABA Standards for \n\n23 Criminal  Justice,  Standard  3‐5.8(b));  see  also  U.S.  v.  Burse,  531  F.2d \n\n24 1151,  1154–55  (2d  Cir.  1976)  (a  prosecutor  may  not  give  “the \n\n 77  No. 17‐1859\n\n 1 impression that the government ha[s] within its possession evidence \n\n 2 of [the defendant’s] guilt which had not been given the jury”); United \n\n 3 States v. Rivera, 22 F.3d 430, 437–38 (2d Cir. 1994) (“use of the personal \n\n 4 pronoun  ‘I’  .  .  .  tends  to  [improperly]  make  an  issue  of  [the \n\n 5 prosecution’s]  own  credibility”  (internal  quotation  marks  and \n\n 6 alterations  omitted)).    We  have  concluded  that  the  “policies \n\n 7 underlying this proscription go to the heart of a fair trial.”  Modica, \n\n 8 663 F.2d at 1178.   In short, it is the height of summation misconduct \n\n 9 for  a  prosecutor  to  argue  to  the  jury  his  personal  opinion  as  to  a \n\n10 defendant’s guilt. \n\n11 Defendants do not dispute that had the statement been made it \n\n12 would  have  been  serious  misconduct;  rather,  they  point  to  ADA \n\n13 Guy’s  deposition  testimony  denying  that  he  made  the  remark  and \n\n14 contending  that  there  was  simply  a  transcription  error  in  the  trial \n\n15 record.  Guy Dep. Tr. 154–55, 232 (stating that he said “[you] know \n\n16 who  committed  the  murder”).    But,  on  a  motion  for  summary \n\n17 judgment, we must draw all inferences in favor of the non‐movant, \n\n18 which  requires  us  to  accept  the  inference  that  the  trial  transcript \n\n19 accurately depicts what occurred at trial. \n\n20 Regardless,  that  remark,  if  it  occurred,  does  not  stand  alone.  \n\n21 Also improper was ADA Guy’s comment, again made near the end \n\n22 of his summation, that “you [Bellamy] are not going to get away with \n\n23 it, not this time.” Trial Tr. 1150 (emphasis added).  Viewed in Bellamy’s \n\n 78  No. 17‐1859\n\n 1 favor,  this  statement  permitted  the  inference  that  Bellamy  had \n\n 2 committed  other  uncharged crimes at  other  times  (murder,  no  less, \n\n 3 the crime for which Bellamy was on trial) and that the government \n\n 4 had  evidence  of  those  crimes  to  which  the  jury  was  not  privy.    See \n\n 5 United States v. Farmer, 583 F.3d 131, 146 (2d Cir. 2009) (improper to \n\n 6 make  remarks  “suggestive  of  a  [defendant’s]  criminal  disposition” \n\n 7 where  that  remark  has  no  otherwise  “legitimate  relationship  to  the \n\n 8 crimes charged,” especially where the remark hints at “a propensity \n\n 9 to commit particularly heinous crimes,” such as murder, “including \n\n10 the  very  offenses  charged  in  the  indictment”  (internal  quotation \n\n11 marks  omitted));  Burse,  531  F.2d  at  1155;  see  also  Manning  v.  Artuz, \n\n12 1996  WL  294359,  at  *3,  *5  (E.D.N.Y.  May  29,  1996)  (prosecutor’s \n\n13 summation statement that “the gun recovered by the police was the \n\n14 ‘tool  of  [Petitioner’s]  trade’  .  .  .  overstepped  the  bounds  of  proper \n\n15 summation”).  \n\n16 ADA Guy’s summation contained other improper remarks.  In \n\n17 arguing  to  the  jury  that  the  evidence  showed  that  Carter  identified \n\n18 Bellamy at the lineup, ADA Guy told the jury that they “don’t have \n\n19 to take my word” on the subject, Trial Tr. 1137 (emphasis added), but, \n\n20 as discussed, a prosecutor may not inform the jury either way what \n\n21 his “word” is.  See Modica, 663 F.2d at 1178–79.  Also crossing the line \n\n22 was ADA Guy’s rhetorical question to the jury, in a case where the \n\n23 government  put  in  no  evidence  of  motive:  “Where  is  there  proof \n\n 79  No. 17‐1859\n\n 1 defendant  had  no  motive  to  kill  somebody?”    Trial  Tr.  1133.    Of \n\n 2 course,  Bellamy  was  under  no  obligation  to  prove  the  absence  of  a \n\n 3 motive and it is difficult to see how a defendant could possibly do so.  \n\n 4 At another point, ADA Guy remarked that Bellamy “is a liar,” Trial \n\n 5 Tr.  1148,  a  comment  we  have  found  deserving  of  admonishment, \n\n 6 especially  where,  as  here,  “such  characterization  is  applied  to  a \n\n 7 [criminal]  defendant  .  .  .  [where]  the  risk  of  prejudice  is  greater.”  \n\n 8 United States v. Leeds, 457 F.2d 857, 860–61 (2d Cir. 1972).   \n\n 9 The  trial  court  took  no  “curative  measures”  to  obviate  the \n\n10 harms from these improper comments, see United States v. Espinal, 981 \n\n11 F.2d  664,  666–67  (2d  Cir.  1992),  but  the  reason  for  that  is  clear: \n\n12 Bellamy’s  defense  counsel  did  not  object  to  them  nor  subsequently \n\n13 seek a curative instruction.31  A defense counsel’s failure to object to \n\n14 an improper summation remark undercuts the probative value of the \n\n15 subsequent lack of a curative measure.  See United States v. Melendez, \n\n16 57  F.3d  238,  242  (2d  Cir.  1995)  (generally,  “the  failure  to  request \n\n17 specific  instructions  before  the  jury  retires  will  limit  the  defense’s \n\n18 ability to complain about the relative lack of curative measures for the \n\n19 first  time  on  appeal”);  but  see  id.  (a  “failure  to  request  specific \n\n\n\n\n  Defense counsel objected three times during ADA Guy’s summation, \n 31\n\n but not with respect to any of the comments we identify above.  See Trial \n Tr. 1127, 1129, 1143. \n\n 80  No. 17‐1859\n\n 1 instructions may be overlooked where the prosecutor’s misconduct is \n\n 2 so prejudicial that no instruction could mitigate its effects”).32  \n\n 3 But,  “[c]urative  measures  constitute  only  one  part  of  the \n\n 4 analysis.”    Espinal,  981  F.2d  at  667.    As  identified  above,  the  third \n\n 5 component of our due process test requires, notwithstanding the lack \n\n 6 of an objection from defense counsel, that we still ask how confident \n\n 7 we are that the criminal defendant would have been convicted absent \n\n 8 the summation misconduct.  We must as a consequence take stock of \n\n 9 the  realities  of  the  trial  in  which  the  summation  misconduct  due \n\n10 process violations are said to occur.  For example, in Farmer, we found \n\n11 that  the  prosecutor’s  “flagrant  abuse”  through  his  summation \n\n12 remarks,  not  objected  to  by  defense  counsel,  was  insufficient  to \n\n13 warrant  reversal  of  one  of  the  defendant’s  convictions  because  the \n\n14 defendant’s  guilt  on  that  charge  “was  supported  by  such \n\n15 overwhelming  evidence  that  conviction  was  a  certainty,”  but  the \n\n16 improper  summation  remarks  did  warrant  reversal  of  defendant’s \n\n17 conviction on a different charge for which the evidence “was far less \n\n18 conclusive.”  583 F.3d at 147–48.  As we concluded, “the determinative \n\n19 factor [was] the weight of the evidence.”  Id. at 147. \n\n\n\n\n  We also note that Bellamy did not raise this summation misconduct \n 32\n\n issue on direct appeal or as part of his habeas corpus petition.  But, there is \n no general exhaustion requirement under § 1983.  See Roach v. Morse, 440 \n F.3d 53, 56 (2d Cir. 2006). \n\n 81  No. 17‐1859\n\n 1 If the trial evidence here had clearly pointed to Bellamy’s guilt, \n\n 2 we  would  have  no  hesitation  in  rejecting  his  improper  summation \n\n 3 claim on this record.   See Espinal, 981 F.2d at 666–67; Farmer, 583 F.3d \n\n 4 at  147–48.    The  bar  for  concluding  that  unobjected  to  summation \n\n 5 remarks  amount  to  a  due  process  violation  is  appropriately  high.  \n\n 6 And  we  also  acknowledge  that  as  an  appellate  court  we  should  be \n\n 7 wary of “cherry‐picking” improper yet isolated remarks from a cold \n\n 8 record made during a lengthy summation, especially where defense \n\n 9 counsel,  who  witnessed  the  statements  live  in  court,  offered  no \n\n10 contemporaneous objection.  But here, it is difficult to conclude other \n\n11 than  that  Bellamy’s  criminal  trial  existed  at  the  cusp  of  reasonable \n\n12 doubt.  Thus we conclude that a civil jury evaluating Bellamy’s due \n\n13 process  claim  could  reasonably  find  that  ADA  Guy’s  improper \n\n14 remarks pushed this case over the line.   \n\n15 Heading  into  summations,  the  QCDA’s  office  had  major \n\n16 misgivings about the quality of its case.  See generally People v. Bellamy, \n\n17 84 A.D.3d 1260, 1262 (2d Dep’t 2011) (stating that there was “less than \n\n18 overwhelming  evidence  against  [Bellamy]”);  see  also  App’x  2088 \n\n19 (documenting  the  jury’s  prolonged  and  difficult  deliberations).  \n\n20 Discovery revealed that ADA Guy himself, after the close of evidence, \n\n21 thought  the  case  had  “sort  of  crumbled  in  [his]  hand,”  and  that  he \n\n22 “needed  something  else.”    App’x  1715.    ADA  Guy  met  with  other \n\n23 prosecutors, including his bureau chief, prior to giving his summation \n\n 82  No. 17‐1859\n\n 1 because they all “sensed there was a problem going on.”  Guy Dep. \n\n 2 Tr. 44–45, 192–93.  And ADA Guy admitted during his deposition that \n\n 3 although earlier he thought he had a strong case against Bellamy, by \n\n 4 the time the evidence had closed “it was closer to being a weak case \n\n 5 for the prosecution.”  Guy Dep. Tr. 46.  In his deposition, ADA Guy \n\n 6 acknowledged  that  “[t]here  was  also  enough  weakness  that  a  jury \n\n 7 could’ve said, no, we have a reasonable doubt.”  Guy Dep. Tr. 193.  \n\n 8 Indeed,  “[t]he  general  consensus,”  ADA  Guy  acknowledged,  “was \n\n 9 that [he] needed a very strong summation in order to sort of salvage \n\n10 this case. . . .  I thought I was in trouble.”  App’x 1718.   \n\n11 ADA Guy then delivered his “very strong summation,” App’x \n\n12 1718, but one that was supported by what our cases have consistently \n\n13 described  as  improper  remarks  that  tend  to  sway  the  jury  in \n\n14 constitutionally impermissible ways.  The principal statements with \n\n15 which  we  take  issue  were  given  at  the  very  end  of  ADA  Guy’s \n\n16 summation, which, in New York, follows the defense summation and \n\n17 is not subject to rebuttal.  Thus, if the transcript is to be believed, the \n\n18 nearly final words the jury heard before entering deliberations were \n\n19 ADA Guy’s statement that he, as the prosecutor, knew that Bellamy \n\n20 killed Abbott and that Bellamy was not going to get away with it, “not \n\n21 this  time.”    Viewed  in  this  context,  and  considering  the  other \n\n22 inappropriate  comments  we  have  identified,  we  conclude  that \n\n23 Bellamy has raised a triable issue of fact as to whether ADA Guy’s \n\n 83  No. 17‐1859\n\n1 summation “so infect[ed] [Bellamy’s] trial with unfairness as to make \n\n2 [his]  resulting  conviction  a  denial  of  due  process.”    Certified  Env. \n\n3 Servs., Inc., 753 F.3d at 95. \n\n4 CONCLUSION \n\n5 For the foregoing reasons, we VACATE in part and AFFIRM in \n\n6 part  the  judgment  of  the  district  court  and  REMAND  for  further \n\n7 proceedings consistent with this opinion.33 \n\n\n\n\n   Bellamy  requests  that  we  assign  this  case  on  remand  to  a  different \n 33\n\n district judge.  The request is denied.\n[END_CASE]", "role": "user" } ]
8,443,860
Kareem BELLAMY v. CITY OF NEW YORK, John J. Gillen, and Michael F. Solomeno, John Doe 1, John Doe 2, Supervising Officers at the NYPD 101st Precinct, Vincent NMI Pepe, and Robert Schruhl
Bellamy v. City of N.Y.
2019-01-29
No. 17-1859-cv; August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Jacobs, Shea, Walker", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415287/", "author_raw": ""}]}
JACOBS
SHEA
WALKER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443860/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Kareem BELLAMY v. CITY OF NEW YORK, John J. Gillen, and Michael F. Solomeno, John Doe 1, John Doe 2, Supervising Officers at the NYPD 101st Precinct, Vincent NMI Pepe, and Robert Schruhl\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-29\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,586,201
United States v. Thrower
2019-01-31
17-445-pr
U.S. Court of Appeals for the Second Circuit
{"judges": "Before: WESLEY and CHIN, Circuit Judges, and COTE, District Judge.", "parties": "", "opinions": [{"author": "Judge Denise Cote, of the United States District Court for the Southern District of New", "type": "010combined", "text": "17‐445‐pr \nUnited States v. Thrower \n  \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n ______________                          \n  \n August Term, 2017 \n  \n (Submitted: April 19, 2018          Decided: January 31, 2019) \n  \n Docket No. 17‐445‐pr \n ____________                          \n  \n UNITED STATES OF AMERICA, \n  \n Petitioner‐Appellee, \n  \n –v.–  \n  \n WILLIAM THROWER, \n  \n Respondent‐Appellant. *\n \n ______________ \n \n \n ON APPEAL FROM THE UNITED STATES DISTRICT COURT FOR THE \n EASTERN DISTRICT OF NEW YORK \n  \nBefore:  \n WESLEY and CHIN, Circuit Judges, and COTE, District Judge.† \n\n\n*  The Clerk of the Court is directed to amend the caption as set forth above. \n Judge Denise Cote, of the United States District Court for the Southern District of New \n†\n\nYork, sitting by designation. \n\f  The  Government  appeals  from  a  judgment  of  the  United  States  District \nCourt  for  the  Eastern  District  of  New  York  (Ross,  J.)  reducing  the  defendant’s \nsentence from 180 months to 120 months and ordering his immediate release on \ntime  served.  The  Government argues that  the  district  court  erred  in  concluding \nthat the defendant’s prior convictions for the New York offenses of robbery in the \nthird degree and attempted robbery in the third degree do not qualify as predicate \n“violent felonies” under the Armed Career Criminal Act, 18 U.S.C. § 924(e)(1). \n We  agree  with  the  Government.  Accordingly,  we  REVERSE  the  district \ncourt’s grant of Thrower’s § 2255 petition, VACATE the amended judgment, and \nREMAND for the district court to reinstate Thrower’s original sentence. \n ______________ \n  \n Amy Busa, Alexander Mindlin, Assistant United States \n Attorneys, for Richard P. Donoghue, United States \n Attorney for the Eastern District of New York, for \n Appellant. \n \n Jane Simkin Smith, Millbrook, NY, for Defendant‐\n Appellee. \n                           \n ______________ \n  \nPER CURIAM: \n\n The Government appeals from a February 13, 2017 judgment of the United \n\nStates  District  Court  for  the  Eastern  District  of  New  York  (Ross,  J.)  reducing \n\ndefendant  William  Thrower’s  sentence  from  180  months  to  120  months  and \n\nordering  Thrower’s  immediate  release  on  time  served.  The  Government  argues \n\nthat the district court erred in concluding that Thrower’s prior convictions for the \n\nNew York offenses of robbery in the third degree and attempted robbery in the \n\n\n 2 \n\fthird degree do not qualify as predicate “violent felonies” under the Armed Career \n\nCriminal Act (“ACCA”), 18 U.S.C. § 924(e)(1), an enhancement that mandates a \n\nminimum sentence of 180 months. \n\n We  agree  with  the  Government.  Accordingly,  we  REVERSE  the  district \n\ncourt’s grant of Thrower’s § 2255 petition, VACATE the amended judgment, and \n\nREMAND for the district court to reinstate Thrower’s original sentence. \n\n\n BACKGROUND \n\n  In  2005,  William  Thrower  was  convicted  of  possessing  a  firearm  while \n\npreviously having been convicted of a “violent felony,” in violation of 18 U.S.C. \n\n§ 922(g)(1). A conviction under § 922(g)(1) carries a mandatory‐minimum sentence \n\nof 120 months. During sentencing in 2008, the district court additionally found that \n\nThrower  qualified  as  an  “armed  career  criminal”  under  ACCA,  18  U.S.C. \n\n§ 924(e)(1),  which  mandates  a  minimum  sentence  of  180  months  for  anyone \n\nconvicted of § 922(g)(1) who also has three prior “violent felony” convictions. The \n\ndistrict court noted that Thrower’s criminal history included the following felony \n\noffenses: (1) a 1981 conviction for first‐degree robbery, N.Y. Penal Law § 160.15; \n\n(2) a 1981 conviction for third‐degree burglary, N.Y. Penal Law § 140.20; (3) a 1993 \n\nconviction for fourth‐degree larceny, N.Y. Penal Law § 155.30; (4) a 1994 conviction \n\n 3 \n\ffor attempted third‐degree robbery, N.Y. Penal Law §§ 160.05 and 110.00; and (5) \n\na  2000  conviction  for  third‐degree  robbery,  N.Y.  Penal  Law  §  160.05.  Without \n\nspecifying  which  of  Thrower’s  prior  convictions  constituted  the  three  predicate \n\n“violent  felonies”  or  which  ACCA  clause(s)—the  force  clause,  the  enumerated‐\n\noffenses  clause,  or  the  residual  clause—it  relied  upon  in  determining  that  the \n\nconvictions  so  qualified,  the  district  court  found  Thrower  subject  to  the  ACCA \n\nenhancement and consequently sentenced him to 180 months’ incarceration. \n\n The Supreme Court subsequently struck down ACCA’s residual clause as \n\nunconstitutionally  vague,  Johnson  v.  United  States,  135  S.  Ct.  2551,  2557  (2015) \n\n(“Johnson II”); see also Welch v. United States, 136 S. Ct. 1257, 1265 (2016) (holding \n\nthat  Johnson  II  applies  retroactively),  calling  into  question  Thrower’s  sentence. \n\nConsequently, Thrower challenged the ACCA enhancement in a 28 U.S.C. § 2255 \n\npetition for a writ of habeas corpus, which the district court granted.1 The district \n\ncourt agreed with Thrower that neither New York robbery in the third degree nor \n\nNew York attempted robbery in the third degree qualifies as a “violent felony” \n\n\n1 In adjudicating Thrower’s petition under § 2255, the district court concluded that when \nsentencing Thrower in 2008, it had relied, at least in part, on the now‐unconstitutional \nresidual  clause  to  determine  that  ACCA’s  mandatory  sentencing  provision  applied.  It \ntherefore analyzed anew whether at least three of Thrower’s prior convictions qualified \nunder the two remaining ACCA clauses. Because they did not, the district court found \nthat the prior error was prejudicial. \n 4 \n\funder  ACCA’s  force  clause.2  Because  the  Government  no  longer  claimed  that \n\nfourth‐degree larceny qualified without the residual clause, only two of Thrower’s \n\nprior convictions remained as potential ACCA predicates—a number insufficient \n\nto subject him to the ACCA enhancement. Seeing, therefore, no need to determine \n\nwhether  first‐degree  robbery  or  third‐degree  burglary  qualifies  as  a  “violent \n\nfelony,” the district court ordered Thrower immediately released on time served. \n\n The Government timely appealed, arguing that because robbery in the first \n\nand  third  degrees  and  attempted  robbery  in  the  third  degree  qualify  as  ACCA \n\npredicates, the district court erred in granting Thrower’s § 2255 petition. \n\n\n DISCUSSION \n\n   We review de novo whether the offenses of New York robbery in the first and \n\nthird degrees and attempted robbery in the third degree qualify as ACCA “violent \n\nfelonies.” See United States v. Brown, 629 F.3d 290, 293 (2d Cir. 2011) (per curiam). \n\nThey do. \n\n \n\n \n\n\n\n2 The Government did not contend that either offense satisfies the requirements of the \nenumerated‐offenses clause. \n 5 \n\f  1.  Armed Career Criminal Act  \n\n  ACCA  mandates  a  minimum  180‐month  term  of  imprisonment  for  any \n\nperson convicted of possessing a firearm in violation of 18 U.S.C. § 922(g)(1) who \n\nalso has three prior “violent felony” convictions. Id. § 924(e)(1). Under the force \n\nclause, a “violent felony” is “any crime punishable by imprisonment for a term \n\nexceeding  one  year,  .  .  .  that  .  .  .  has  as  an  element  the  use,  attempted  use,  or \n\nthreatened use of physical force against the person of another.” Id. § 924(e)(2)(B)(i). \n\nAs the Supreme Court has explained, “‘physical force’ means violent force—that \n\nis, force capable of causing physical pain or injury to another person.” Johnson v. \n\nUnited States, 559 U.S. 133, 140 (2010) (“Johnson I”) (emphasis in original); see also \n\nStokeling v. United States, 139 S. Ct. 544, 554 (2019) (explaining that “Johnson [I] . . . \n\ndoes not require any particular degree of likelihood or probability that the force \n\nused will cause physical pain or injury; only potentiality”). \n\n Courts  apply  a  “categorical  approach”  to  determine  whether  a  prior \n\nconviction qualifies as a “violent felony.” See, e.g., United States v. Hill, 890 F.3d 51, \n\n55–56  (2d  Cir.  2018).  Under  the  categorical  approach,  “courts  identify  ‘the \n\nminimum criminal conduct necessary for conviction under a particular statute.’”  \n\n \n\n\n 6 \n\fId.  at  55  (quoting  United  States  v.  Acosta,  470  F.3d  132,  135  (2d  Cir.  2006)  (per \n\ncuriam)).  In  so  doing,  they  “look  only  to  the  statutory  definitions—i.e.,  the \n\nelements—of the offense, and not to the particular underlying facts.” Id. (quoting \n\nDescamps v. United States, 570 U.S. 254, 261 (2013) (alterations omitted)). If the state‐\n\nlaw  offense  categorically  requires  the  elements  listed  in  § 924(e)(2)(B)(i),  it  may \n\nserve as a predicate “violent felony.” \n\n  2.  New York Robbery in the First and Third Degrees \n\n  Thrower argues that the New York offense of robbery in the third degree \n\ndoes not qualify as a “violent felony” because the requisite force for the offense \n\n“can  be  something  less  than  ‘force  capable  of  causing  physical  pain  or  injury.’” \n\nAppellee Br. 17 (quoting Johnson I, 599 U.S. at 140). We disagree. \n\n The New York offense of robbery in the third degree occurs when a person \n\n“forcibly steals property.” N.Y. Penal Law § 160.05. Forcible stealing—common to \n\nevery degree of robbery in New York State3—is defined as: \n\n when,  in  the  course  of  committing  a  larceny,  [a  person]  uses  or \n threatens  the  immediate  use  of  physical  force  upon  another  person \n for  the  purpose  of:  1.  Preventing  or  overcoming  resistance  to  the \n taking  of  the  property  or  to  the  retention  thereof  immediately  after \n the taking; or 2. Compelling the owner of such property or another \n\n\n3 See N.Y. Penal Law § 160.05; id. § 160.10; id. § 160.15; see also People v. Miller, 87 N.Y.2d \n211, 214 (1995) (“The essence of the [New York] crime of robbery is forcible stealing.”). \n 7 \n\f person to deliver up the property or to engage in other conduct which \n aids in the commission of the larceny. \n \nId. § 160.00.  \n\n By  its  plain  language,  the  New  York  robbery  statute  matches  the  ACCA \n\ndefinition of a “violent felony.” Predicate offenses under ACCA include those that \n\nhave as an element “the use . . . or threatened use of physical force.” 18 U.S.C. § \n\n924(e)(2)(B)(i). New York requires the “use[] or threaten[ed] . . . immediate use of \n\nphysical  force.”  Additionally,  the  New  York  robbery  statute,  like  ACCA’s  force \n\nclause,  is  modeled  on  the  common  law  definition  of  robbery.  As  the  Supreme \n\nCourt  recently  explained  in  Stokeling,  “the  term  ‘physical  force’  in  ACCA \n\nencompasses  the  degree  of  force  necessary  to  commit  common‐law  robbery,” \n\ndefined  as  “the  amount  of  force  necessary  to  overcome  a  victim’s  resistance.” \n\nStokeling, 139 S. Ct. at 555. Like the Florida robbery statute at issue in Stokeling, the \n\nNew York robbery statute uses the term “physical force.” The New York Court of \n\nAppeals has explained that “if a statute uses a word which has a definite and well‐\n\nknown meaning at common law, it will be construed with the aid of common‐law \n\ndefinitions, unless it clearly appears that it was not so intended.” People v. King, 61 \n\nN.Y.2d  550,  554–55  (1984).  Far  from  evincing  a  clear  intent  to  stray  from  the \n\ncommon law understanding of robbery, the robbery statute explicitly incorporates \n\n 8 \n\fthe  common  law  definition  by  explaining  that  “physical  force”  means  enough \n\nforce to “[p]revent[] or overcom[e] resistance to the taking . . . or . . . [to c]ompel[] \n\nthe owner . . . to deliver up the property.” N.Y. Penal Law § 160.00; see also People \n\nv. Jurgins, 26 N.Y.3d 607, 614 (2015). \n\n None of the cases to which Thrower cites convince us that New York courts \n\ninterpret the force required for New York robbery as less than that required under \n\nACCA. In People v. Lee, 197 A.D.2d 378 (1st Dep’t 1993), a New York intermediate \n\ncourt of appeals found the force element of § 160.05 satisfied where the defendant \n\n“bumped  his  unidentified  victim,  took  money,  and  fled  while  another  forcibly \n\nblocked  the  victim’s  pursuit,”  because  the  act  of  blocking  was  a  form  of \n\novercoming the victim’s resistance, id. at 378 (citing People v. Patton, 184 A.D.2d \n\n483,  483  (1st  Dep’t  1992)  (“[A]ct[ing]  as  a  blocker  [is  a  form  of]  overcoming  the \n\nvictim’s  resistance  to  the  robbery  within  the  meaning  of  Penal  Law  §  160.00(1).” \n\n(emphasis added))).4 Similarly, in People v. Safon, 166 A.D.2d 892 (4th Dep’t 1990), \n\n\n\n4 See also United States v. Pereira‐Gomez, 903 F.3d 155, 166 (2d Cir. 2018) (explaining that a \n“’human wall’ [is] no mere obstacle to the victim’s pursuit of the robber; it constitute[s] a \nthreat that pursuit would lead to a violent confrontation” and therefore holding that New \nYork attempted robbery in the second degree qualifies as a “crime of violence” under the \nidentically worded force clause of application note 1(B)(iii) to Section 2L1.2 of the 2014 \nSentencing Guidelines); see also U.S.S.G. § 2L1.2 cmt. 1(B)(iii) (2014) (defining a “crime of \nviolence” as having “as an element the use, attempted use, or threatened use of physical \nforce against the person of another”). \n 9 \n\fa  New  York  intermediate  appellate  court  affirmed  a  third‐degree  robbery \n\nconviction where the evidence showed that the defendant and the victim “tugged \n\nat each other until defendant’s hand slipped out of the glove holding the money” \n\nbecause this “was sufficient to prove that defendant used physical force for the \n\npurpose  of  overcoming  the  victimʹs  resistance  to  the  taking,”  id.  at  893  (emphasis \n\nadded). \n\n We  therefore  conclude  that  the  New  York  offense  of  robbery  in  the  third \n\ndegree, which like every degree of robbery in New York requires the common law \n\nelement  of  “forcible  stealing,”  is  a  “violent  felony”  under  ACCA.  By  extension, \n\nNew York robbery in the first degree is also a “violent felony” under ACCA.5 \n\n 3.  New York Attempted Robbery in the Third Degree \n\n Thrower next argues that the New York offense of attempted robbery in the \n\nthird  degree  does  not  qualify  as  a  “violent  felony”  because  a  person  may  be \n\nconvicted of  attempted  robbery  by merely  attempting  to  threaten  to  use  physical \n\n\n\n5 Thrower argues that his conviction for first‐degree robbery does not qualify as an ACCA \npredicate because he received a Certificate of Relief from Civil Disabilities from the State \nof New York that restored his civil rights. Although Thrower is correct that a conviction \nwith respect to which civil rights have been restored cannot serve as an ACCA predicate, \nthis  exception  applies  only  where  the  Certificate  does  not  prohibit  the  possession  of \nfirearms. See 18 U.S.C. § 921(a)(20). Thrower has not shown that his Certificate lacks such \na prohibition. See United States v. Bullock, 550 F.3d 247, 250 (2d Cir. 2008). \n 10 \n\fforce, falling short of the requirement of attempting to use physical force. We again \n\ndisagree. \n\n As  above,  the  New  York  attempted  robbery  statute,  by  its  own  terms, \n\nmatches  the  ACCA  definition  of  a  “violent  felony.”  Predicate  offenses  under \n\nACCA include those that have as an element the “attempted use . . . of physical \n\nforce.”  18  U.S.C.  §  924(e)(2)(B)(i).  Under  federal  law,  “[a]  person  is  guilty  of  an \n\nattempt to commit a crime if he or she (1) had the intent to commit the crime, and \n\n(2) engaged in conduct amounting to a ‘substantial step’ towards the commission \n\nof the crime.” United States v. Martinez, 775 F.2d 31, 35 (2d Cir. 1985).  \n\n New  York  requires  that,  “with  intent  to  commit  a  crime  .  .  .  [a  person] \n\nengage[]  in  conduct  which  tends  to  effect  the  commission  of  such  crime.”  N.Y. \n\nPenal Law § 110.00. The New York Court of Appeals has clarified that an attempt \n\nrequires that the action taken by an accused be “so near to its accomplishment that \n\nin all reasonable probability the crime itself would have been committed but for \n\ntimely  interference.”  People  v.  Rizzo,  246  N.Y.  334,  337  (1927);  see  also  People  v. \n\nDenson, 26 N.Y.3d 179, 189 (2015) (“[F]or a defendant to be guilty of an attempted \n\ncrime, the defendant must have engaged in conduct that came dangerously near \n\ncommission  of  the  completed  crime.”  (quotation  marks  and  citation  omitted)). \n\n\n 11 \n\fWhere a statute requires that a person be so “dangerously near” forcibly stealing \n\nproperty  “that  in  all  reasonable  probability”  she  would  have  completed  the \n\nrobbery but for interference, the statute categorically requires that a person take a \n\n“substantial step” toward the use of physical force. See People v. Acosta, 80 N.Y.2d \n\n665,  670  (1993)  (explaining  that  New  York’s  attempt  statute  is  “more  stringent” \n\nthan the “‘substantial step’ test . . . adopted by [the Second Circuit]”); United States \n\nv.  Farhane,  634  F.3d  127,  146  (2d  Cir.  2011)  (noting  that  the  federal  “substantial \n\nstep” test “ushered in a broader view of attempt” than that employed at common \n\nlaw). \n\n Nothing from New York’s courts leads us to conclude otherwise. Though \n\nThrower posits that a defendant might be convicted of attempted robbery in New \n\nYork for an attempt to threaten to use physical force—as distinct from an attempt \n\nto use physical force or a threat to use physical force—he fails to “at least point to \n\nhis own case or other cases in which the state courts in fact did apply the statute \n\nin the . . . manner for which he argues.”6 See Gonzales v. Duenas–Alvarez, 549 U.S. \n\n\n\n\n6 Even if Thrower could cite to such an example, we would not come out differently on \nthis  issue.  An  attempt  to  threaten  to  use  force  by,  for  example,  attempting  to  use  a \nthreatening note, itself constitutes a “threatened use of physical force.” \n 12 \n\f183,  193  (2007).  As  such,  we  are  left  with  the  text  of  the  New  York  attempted \n\nrobbery statute, which plainly matches ACCA’s definition of a “violent felony.”  \n\n We therefore conclude that the New York offense of attempted robbery in \n\nthe third degree is a “violent felony” under ACCA. \n\n\n CONCLUSION \n\n  Robbery in the first and third degrees and attempted robbery in the third \n\ndegree,  in  violation  of  N.Y.  Penal  Law  §§  110.00,  160.05,  160.15,  are  “violent \n\nfelonies” under the force clause of ACCA. Because Thrower therefore has three \n\nqualifying “violent felony” convictions under ACCA, the district court erred by \n\nnot  sentencing  him  to  the  applicable  180‐month  mandatory  minimum  term  of \n\nincarceration. \n\n We  REVERSE  the  district  court’s  grant  of  Thrower’s  §  2255  petition, \n\nVACATE the amended judgment, and REMAND for the district court to reinstate \n\nThrower’s original sentence. \n\n\n\n\n 13", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4363454/", "author_raw": "Judge Denise Cote, of the United States District Court for the Southern District of New"}]}
WESLEY
CHIN
COTE
1
{"WESLEY": ", Circuit", "CHIN": ", Circuit", "COTE": ", District"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4586201/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Thrower\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-31\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n17‐445‐pr \nUnited States v. Thrower \n  \n UNITED STATES COURT OF APPEALS \n FOR THE SECOND CIRCUIT \n ______________                          \n  \n August Term, 2017 \n  \n (Submitted: April 19, 2018          Decided: January 31, 2019) \n  \n Docket No. 17‐445‐pr \n ____________                          \n  \n UNITED STATES OF AMERICA, \n  \n Petitioner‐Appellee, \n  \n –v.–  \n  \n WILLIAM THROWER, \n  \n Respondent‐Appellant. *\n \n ______________ \n \n \n ON APPEAL FROM THE UNITED STATES DISTRICT COURT FOR THE \n EASTERN DISTRICT OF NEW YORK \n  \nBefore:  \n WESLEY and CHIN, Circuit Judges, and COTE, District Judge.† \n\n\n*  The Clerk of the Court is directed to amend the caption as set forth above. \n Judge Denise Cote, of the United States District Court for the Southern District of New \n†\n\nYork, sitting by designation. \n\f  The  Government  appeals  from  a  judgment  of  the  United  States  District \nCourt  for  the  Eastern  District  of  New  York  (Ross,  J.)  reducing  the  defendant’s \nsentence from 180 months to 120 months and ordering his immediate release on \ntime  served.  The  Government argues that  the  district  court  erred  in  concluding \nthat the defendant’s prior convictions for the New York offenses of robbery in the \nthird degree and attempted robbery in the third degree do not qualify as predicate \n“violent felonies” under the Armed Career Criminal Act, 18 U.S.C. § 924(e)(1). \n We  agree  with  the  Government.  Accordingly,  we  REVERSE  the  district \ncourt’s grant of Thrower’s § 2255 petition, VACATE the amended judgment, and \nREMAND for the district court to reinstate Thrower’s original sentence. \n ______________ \n  \n Amy Busa, Alexander Mindlin, Assistant United States \n Attorneys, for Richard P. Donoghue, United States \n Attorney for the Eastern District of New York, for \n Appellant. \n \n Jane Simkin Smith, Millbrook, NY, for Defendant‐\n Appellee. \n                           \n ______________ \n  \nPER CURIAM: \n\n The Government appeals from a February 13, 2017 judgment of the United \n\nStates  District  Court  for  the  Eastern  District  of  New  York  (Ross,  J.)  reducing \n\ndefendant  William  Thrower’s  sentence  from  180  months  to  120  months  and \n\nordering  Thrower’s  immediate  release  on  time  served.  The  Government  argues \n\nthat the district court erred in concluding that Thrower’s prior convictions for the \n\nNew York offenses of robbery in the third degree and attempted robbery in the \n\n\n 2 \n\fthird degree do not qualify as predicate “violent felonies” under the Armed Career \n\nCriminal Act (“ACCA”), 18 U.S.C. § 924(e)(1), an enhancement that mandates a \n\nminimum sentence of 180 months. \n\n We  agree  with  the  Government.  Accordingly,  we  REVERSE  the  district \n\ncourt’s grant of Thrower’s § 2255 petition, VACATE the amended judgment, and \n\nREMAND for the district court to reinstate Thrower’s original sentence. \n\n\n BACKGROUND \n\n  In  2005,  William  Thrower  was  convicted  of  possessing  a  firearm  while \n\npreviously having been convicted of a “violent felony,” in violation of 18 U.S.C. \n\n§ 922(g)(1). A conviction under § 922(g)(1) carries a mandatory‐minimum sentence \n\nof 120 months. During sentencing in 2008, the district court additionally found that \n\nThrower  qualified  as  an  “armed  career  criminal”  under  ACCA,  18  U.S.C. \n\n§ 924(e)(1),  which  mandates  a  minimum  sentence  of  180  months  for  anyone \n\nconvicted of § 922(g)(1) who also has three prior “violent felony” convictions. The \n\ndistrict court noted that Thrower’s criminal history included the following felony \n\noffenses: (1) a 1981 conviction for first‐degree robbery, N.Y. Penal Law § 160.15; \n\n(2) a 1981 conviction for third‐degree burglary, N.Y. Penal Law § 140.20; (3) a 1993 \n\nconviction for fourth‐degree larceny, N.Y. Penal Law § 155.30; (4) a 1994 conviction \n\n 3 \n\ffor attempted third‐degree robbery, N.Y. Penal Law §§ 160.05 and 110.00; and (5) \n\na  2000  conviction  for  third‐degree  robbery,  N.Y.  Penal  Law  §  160.05.  Without \n\nspecifying  which  of  Thrower’s  prior  convictions  constituted  the  three  predicate \n\n“violent  felonies”  or  which  ACCA  clause(s)—the  force  clause,  the  enumerated‐\n\noffenses  clause,  or  the  residual  clause—it  relied  upon  in  determining  that  the \n\nconvictions  so  qualified,  the  district  court  found  Thrower  subject  to  the  ACCA \n\nenhancement and consequently sentenced him to 180 months’ incarceration. \n\n The Supreme Court subsequently struck down ACCA’s residual clause as \n\nunconstitutionally  vague,  Johnson  v.  United  States,  135  S.  Ct.  2551,  2557  (2015) \n\n(“Johnson II”); see also Welch v. United States, 136 S. Ct. 1257, 1265 (2016) (holding \n\nthat  Johnson  II  applies  retroactively),  calling  into  question  Thrower’s  sentence. \n\nConsequently, Thrower challenged the ACCA enhancement in a 28 U.S.C. § 2255 \n\npetition for a writ of habeas corpus, which the district court granted.1 The district \n\ncourt agreed with Thrower that neither New York robbery in the third degree nor \n\nNew York attempted robbery in the third degree qualifies as a “violent felony” \n\n\n1 In adjudicating Thrower’s petition under § 2255, the district court concluded that when \nsentencing Thrower in 2008, it had relied, at least in part, on the now‐unconstitutional \nresidual  clause  to  determine  that  ACCA’s  mandatory  sentencing  provision  applied.  It \ntherefore analyzed anew whether at least three of Thrower’s prior convictions qualified \nunder the two remaining ACCA clauses. Because they did not, the district court found \nthat the prior error was prejudicial. \n 4 \n\funder  ACCA’s  force  clause.2  Because  the  Government  no  longer  claimed  that \n\nfourth‐degree larceny qualified without the residual clause, only two of Thrower’s \n\nprior convictions remained as potential ACCA predicates—a number insufficient \n\nto subject him to the ACCA enhancement. Seeing, therefore, no need to determine \n\nwhether  first‐degree  robbery  or  third‐degree  burglary  qualifies  as  a  “violent \n\nfelony,” the district court ordered Thrower immediately released on time served. \n\n The Government timely appealed, arguing that because robbery in the first \n\nand  third  degrees  and  attempted  robbery  in  the  third  degree  qualify  as  ACCA \n\npredicates, the district court erred in granting Thrower’s § 2255 petition. \n\n\n DISCUSSION \n\n   We review de novo whether the offenses of New York robbery in the first and \n\nthird degrees and attempted robbery in the third degree qualify as ACCA “violent \n\nfelonies.” See United States v. Brown, 629 F.3d 290, 293 (2d Cir. 2011) (per curiam). \n\nThey do. \n\n \n\n \n\n\n\n2 The Government did not contend that either offense satisfies the requirements of the \nenumerated‐offenses clause. \n 5 \n\f  1.  Armed Career Criminal Act  \n\n  ACCA  mandates  a  minimum  180‐month  term  of  imprisonment  for  any \n\nperson convicted of possessing a firearm in violation of 18 U.S.C. § 922(g)(1) who \n\nalso has three prior “violent felony” convictions. Id. § 924(e)(1). Under the force \n\nclause, a “violent felony” is “any crime punishable by imprisonment for a term \n\nexceeding  one  year,  .  .  .  that  .  .  .  has  as  an  element  the  use,  attempted  use,  or \n\nthreatened use of physical force against the person of another.” Id. § 924(e)(2)(B)(i). \n\nAs the Supreme Court has explained, “‘physical force’ means violent force—that \n\nis, force capable of causing physical pain or injury to another person.” Johnson v. \n\nUnited States, 559 U.S. 133, 140 (2010) (“Johnson I”) (emphasis in original); see also \n\nStokeling v. United States, 139 S. Ct. 544, 554 (2019) (explaining that “Johnson [I] . . . \n\ndoes not require any particular degree of likelihood or probability that the force \n\nused will cause physical pain or injury; only potentiality”). \n\n Courts  apply  a  “categorical  approach”  to  determine  whether  a  prior \n\nconviction qualifies as a “violent felony.” See, e.g., United States v. Hill, 890 F.3d 51, \n\n55–56  (2d  Cir.  2018).  Under  the  categorical  approach,  “courts  identify  ‘the \n\nminimum criminal conduct necessary for conviction under a particular statute.’”  \n\n \n\n\n 6 \n\fId.  at  55  (quoting  United  States  v.  Acosta,  470  F.3d  132,  135  (2d  Cir.  2006)  (per \n\ncuriam)).  In  so  doing,  they  “look  only  to  the  statutory  definitions—i.e.,  the \n\nelements—of the offense, and not to the particular underlying facts.” Id. (quoting \n\nDescamps v. United States, 570 U.S. 254, 261 (2013) (alterations omitted)). If the state‐\n\nlaw  offense  categorically  requires  the  elements  listed  in  § 924(e)(2)(B)(i),  it  may \n\nserve as a predicate “violent felony.” \n\n  2.  New York Robbery in the First and Third Degrees \n\n  Thrower argues that the New York offense of robbery in the third degree \n\ndoes not qualify as a “violent felony” because the requisite force for the offense \n\n“can  be  something  less  than  ‘force  capable  of  causing  physical  pain  or  injury.’” \n\nAppellee Br. 17 (quoting Johnson I, 599 U.S. at 140). We disagree. \n\n The New York offense of robbery in the third degree occurs when a person \n\n“forcibly steals property.” N.Y. Penal Law § 160.05. Forcible stealing—common to \n\nevery degree of robbery in New York State3—is defined as: \n\n when,  in  the  course  of  committing  a  larceny,  [a  person]  uses  or \n threatens  the  immediate  use  of  physical  force  upon  another  person \n for  the  purpose  of:  1.  Preventing  or  overcoming  resistance  to  the \n taking  of  the  property  or  to  the  retention  thereof  immediately  after \n the taking; or 2. Compelling the owner of such property or another \n\n\n3 See N.Y. Penal Law § 160.05; id. § 160.10; id. § 160.15; see also People v. Miller, 87 N.Y.2d \n211, 214 (1995) (“The essence of the [New York] crime of robbery is forcible stealing.”). \n 7 \n\f person to deliver up the property or to engage in other conduct which \n aids in the commission of the larceny. \n \nId. § 160.00.  \n\n By  its  plain  language,  the  New  York  robbery  statute  matches  the  ACCA \n\ndefinition of a “violent felony.” Predicate offenses under ACCA include those that \n\nhave as an element “the use . . . or threatened use of physical force.” 18 U.S.C. § \n\n924(e)(2)(B)(i). New York requires the “use[] or threaten[ed] . . . immediate use of \n\nphysical  force.”  Additionally,  the  New  York  robbery  statute,  like  ACCA’s  force \n\nclause,  is  modeled  on  the  common  law  definition  of  robbery.  As  the  Supreme \n\nCourt  recently  explained  in  Stokeling,  “the  term  ‘physical  force’  in  ACCA \n\nencompasses  the  degree  of  force  necessary  to  commit  common‐law  robbery,” \n\ndefined  as  “the  amount  of  force  necessary  to  overcome  a  victim’s  resistance.” \n\nStokeling, 139 S. Ct. at 555. Like the Florida robbery statute at issue in Stokeling, the \n\nNew York robbery statute uses the term “physical force.” The New York Court of \n\nAppeals has explained that “if a statute uses a word which has a definite and well‐\n\nknown meaning at common law, it will be construed with the aid of common‐law \n\ndefinitions, unless it clearly appears that it was not so intended.” People v. King, 61 \n\nN.Y.2d  550,  554–55  (1984).  Far  from  evincing  a  clear  intent  to  stray  from  the \n\ncommon law understanding of robbery, the robbery statute explicitly incorporates \n\n 8 \n\fthe  common  law  definition  by  explaining  that  “physical  force”  means  enough \n\nforce to “[p]revent[] or overcom[e] resistance to the taking . . . or . . . [to c]ompel[] \n\nthe owner . . . to deliver up the property.” N.Y. Penal Law § 160.00; see also People \n\nv. Jurgins, 26 N.Y.3d 607, 614 (2015). \n\n None of the cases to which Thrower cites convince us that New York courts \n\ninterpret the force required for New York robbery as less than that required under \n\nACCA. In People v. Lee, 197 A.D.2d 378 (1st Dep’t 1993), a New York intermediate \n\ncourt of appeals found the force element of § 160.05 satisfied where the defendant \n\n“bumped  his  unidentified  victim,  took  money,  and  fled  while  another  forcibly \n\nblocked  the  victim’s  pursuit,”  because  the  act  of  blocking  was  a  form  of \n\novercoming the victim’s resistance, id. at 378 (citing People v. Patton, 184 A.D.2d \n\n483,  483  (1st  Dep’t  1992)  (“[A]ct[ing]  as  a  blocker  [is  a  form  of]  overcoming  the \n\nvictim’s  resistance  to  the  robbery  within  the  meaning  of  Penal  Law  §  160.00(1).” \n\n(emphasis added))).4 Similarly, in People v. Safon, 166 A.D.2d 892 (4th Dep’t 1990), \n\n\n\n4 See also United States v. Pereira‐Gomez, 903 F.3d 155, 166 (2d Cir. 2018) (explaining that a \n“’human wall’ [is] no mere obstacle to the victim’s pursuit of the robber; it constitute[s] a \nthreat that pursuit would lead to a violent confrontation” and therefore holding that New \nYork attempted robbery in the second degree qualifies as a “crime of violence” under the \nidentically worded force clause of application note 1(B)(iii) to Section 2L1.2 of the 2014 \nSentencing Guidelines); see also U.S.S.G. § 2L1.2 cmt. 1(B)(iii) (2014) (defining a “crime of \nviolence” as having “as an element the use, attempted use, or threatened use of physical \nforce against the person of another”). \n 9 \n\fa  New  York  intermediate  appellate  court  affirmed  a  third‐degree  robbery \n\nconviction where the evidence showed that the defendant and the victim “tugged \n\nat each other until defendant’s hand slipped out of the glove holding the money” \n\nbecause this “was sufficient to prove that defendant used physical force for the \n\npurpose  of  overcoming  the  victimʹs  resistance  to  the  taking,”  id.  at  893  (emphasis \n\nadded). \n\n We  therefore  conclude  that  the  New  York  offense  of  robbery  in  the  third \n\ndegree, which like every degree of robbery in New York requires the common law \n\nelement  of  “forcible  stealing,”  is  a  “violent  felony”  under  ACCA.  By  extension, \n\nNew York robbery in the first degree is also a “violent felony” under ACCA.5 \n\n 3.  New York Attempted Robbery in the Third Degree \n\n Thrower next argues that the New York offense of attempted robbery in the \n\nthird  degree  does  not  qualify  as  a  “violent  felony”  because  a  person  may  be \n\nconvicted of  attempted  robbery  by merely  attempting  to  threaten  to  use  physical \n\n\n\n5 Thrower argues that his conviction for first‐degree robbery does not qualify as an ACCA \npredicate because he received a Certificate of Relief from Civil Disabilities from the State \nof New York that restored his civil rights. Although Thrower is correct that a conviction \nwith respect to which civil rights have been restored cannot serve as an ACCA predicate, \nthis  exception  applies  only  where  the  Certificate  does  not  prohibit  the  possession  of \nfirearms. See 18 U.S.C. § 921(a)(20). Thrower has not shown that his Certificate lacks such \na prohibition. See United States v. Bullock, 550 F.3d 247, 250 (2d Cir. 2008). \n 10 \n\fforce, falling short of the requirement of attempting to use physical force. We again \n\ndisagree. \n\n As  above,  the  New  York  attempted  robbery  statute,  by  its  own  terms, \n\nmatches  the  ACCA  definition  of  a  “violent  felony.”  Predicate  offenses  under \n\nACCA include those that have as an element the “attempted use . . . of physical \n\nforce.”  18  U.S.C.  §  924(e)(2)(B)(i).  Under  federal  law,  “[a]  person  is  guilty  of  an \n\nattempt to commit a crime if he or she (1) had the intent to commit the crime, and \n\n(2) engaged in conduct amounting to a ‘substantial step’ towards the commission \n\nof the crime.” United States v. Martinez, 775 F.2d 31, 35 (2d Cir. 1985).  \n\n New  York  requires  that,  “with  intent  to  commit  a  crime  .  .  .  [a  person] \n\nengage[]  in  conduct  which  tends  to  effect  the  commission  of  such  crime.”  N.Y. \n\nPenal Law § 110.00. The New York Court of Appeals has clarified that an attempt \n\nrequires that the action taken by an accused be “so near to its accomplishment that \n\nin all reasonable probability the crime itself would have been committed but for \n\ntimely  interference.”  People  v.  Rizzo,  246  N.Y.  334,  337  (1927);  see  also  People  v. \n\nDenson, 26 N.Y.3d 179, 189 (2015) (“[F]or a defendant to be guilty of an attempted \n\ncrime, the defendant must have engaged in conduct that came dangerously near \n\ncommission  of  the  completed  crime.”  (quotation  marks  and  citation  omitted)). \n\n\n 11 \n\fWhere a statute requires that a person be so “dangerously near” forcibly stealing \n\nproperty  “that  in  all  reasonable  probability”  she  would  have  completed  the \n\nrobbery but for interference, the statute categorically requires that a person take a \n\n“substantial step” toward the use of physical force. See People v. Acosta, 80 N.Y.2d \n\n665,  670  (1993)  (explaining  that  New  York’s  attempt  statute  is  “more  stringent” \n\nthan the “‘substantial step’ test . . . adopted by [the Second Circuit]”); United States \n\nv.  Farhane,  634  F.3d  127,  146  (2d  Cir.  2011)  (noting  that  the  federal  “substantial \n\nstep” test “ushered in a broader view of attempt” than that employed at common \n\nlaw). \n\n Nothing from New York’s courts leads us to conclude otherwise. Though \n\nThrower posits that a defendant might be convicted of attempted robbery in New \n\nYork for an attempt to threaten to use physical force—as distinct from an attempt \n\nto use physical force or a threat to use physical force—he fails to “at least point to \n\nhis own case or other cases in which the state courts in fact did apply the statute \n\nin the . . . manner for which he argues.”6 See Gonzales v. Duenas–Alvarez, 549 U.S. \n\n\n\n\n6 Even if Thrower could cite to such an example, we would not come out differently on \nthis  issue.  An  attempt  to  threaten  to  use  force  by,  for  example,  attempting  to  use  a \nthreatening note, itself constitutes a “threatened use of physical force.” \n 12 \n\f183,  193  (2007).  As  such,  we  are  left  with  the  text  of  the  New  York  attempted \n\nrobbery statute, which plainly matches ACCA’s definition of a “violent felony.”  \n\n We therefore conclude that the New York offense of attempted robbery in \n\nthe third degree is a “violent felony” under ACCA. \n\n\n CONCLUSION \n\n  Robbery in the first and third degrees and attempted robbery in the third \n\ndegree,  in  violation  of  N.Y.  Penal  Law  §§  110.00,  160.05,  160.15,  are  “violent \n\nfelonies” under the force clause of ACCA. Because Thrower therefore has three \n\nqualifying “violent felony” convictions under ACCA, the district court erred by \n\nnot  sentencing  him  to  the  applicable  180‐month  mandatory  minimum  term  of \n\nincarceration. \n\n We  REVERSE  the  district  court’s  grant  of  Thrower’s  §  2255  petition, \n\nVACATE the amended judgment, and REMAND for the district court to reinstate \n\nThrower’s original sentence. \n\n\n\n\n 13\n[END_CASE]", "role": "user" } ]
8,443,861
United States v. William THROWER
United States v. Thrower
2019-01-31
Docket No. 17-445-pr; August Term, 2017
U.S. Court of Appeals for the Second Circuit
{"judges": "Chin, Cote, Wesley", "parties": "", "opinions": [{"author": "PER CURIAM", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415288/", "author_raw": "PER CURIAM"}]}
CHIN
COTE
WESLEY
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443861/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. William THROWER\nCourt: U.S. Court of Appeals for the Second Circuit\nDate decided: 2019-01-31\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,578,607
Kevin Culley v. Cumberland Valley School Dist
2019-01-03
17-3800
U.S. Court of Appeals for the Third Circuit
{"judges": "Before: AMBRO, SCIRICA, and RENDELL, Circuit Judges (Opinion", "parties": "", "opinions": [{"author": "AMBRO, Circuit Judge", "type": "010combined", "text": "NOT PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 17-3800\n ________________\n\n KEVIN CULLEY, and; DENISE CULLEY, on behalf of; J.C.\n\n v.\n\n CUMBERLAND VALLEY SCHOOL DISTRICT,\n\n Appellant\n ________________\n\n Appeal from the United States District Court\n for the Middle District of Pennsylvania\n (D.C. Civil Action No. 1-15-cv-00857)\n District Judge: Honorable John E. Jones, III\n ________________\n\n Argued November 6, 2018\n\n Before: AMBRO, SCIRICA, and RENDELL, Circuit Judges\n\n (Opinion filed: December 20, 2018)\n\n\nMark W. Cheramie Walz [Argued]\nSweet, Stevens, Katz & Williams LLP\n331 East Butler Avenue\nP.O. Box 5069\nNew Britain, PA 18901\n Counsel for Appellant\n\nJudith A. Gran [Argued]\nReisman Carolla & Gran LLP\n19 Chestnut Street\nHaddonfield, NJ 08033\n\fPhillip A. Drumheiser\nP.O. Box 890\nCarlisle, PA 17013\n Counsel for Appellees\n\n ________________\n\n OPINION*\n ________________\n\nAMBRO, Circuit Judge\n\n J.C., son of plaintiffs Kevin and Denise Culley, was diagnosed with Crohn’s\n\ndisease at age six. It is a painful, even debilitating, disease that affects the digestive tract\n\nand can cause abdominal pain, diarrhea, fatigue, weight loss, and malnutrition. It can\n\neven be life-threatening. See Mayo Clinic, Crohn’s Disease (Mar. 8, 2018), available at\n\nhttps://www.mayoclinic.org/diseases-conditions/crohns-disease/symptoms-causes/syc-\n\n20353304. After a disciplinary dispute with J.C.’s school, part of the Cumberland Valley\n\nSchool District system, that resulted in his expulsion, J.C.’s parents filed suit claiming\n\nthat Cumberland had violated J.C.’s rights under the Individuals with Disabilities\n\nEducation Act (IDEA), 20 U.S.C. § 1400 et seq., and under Section 504 of the\n\nRehabilitation Act. 29 U.S.C. § 701 et seq. The District Court agreed, and we now\n\naffirm.\n\n Born in 1998, J.C. was diagnosed with Crohn’s disease in 2004. Cumberland was\n\ninformed of the diagnosis in 2007. App. at 53. J.C.’s performance in school was\n\ngenerally strong through his sixth grade year, in 2009–2010, and he did not have\n\n\n\n*\n This disposition is not an opinion of the full Court and pursuant to I.O.P. 5.7 does not\nconstitute binding precedent.\n 2\n\fsignificant behavioral or social difficulties through that time. Id. at 130–131. But from\n\nseventh grade onward, both J.C.’s academic performance and his disciplinary record took\n\nsignificant turns for the worse. From seventh through tenth grade, when the incident\n\ngiving rise to this lawsuit occurred and he was expelled, J.C. maintained a grade point\n\naverage just above a failing mark of 70, had numerous disciplinary incidents, and was\n\nincreasingly absent from school. Id. at 128, 131, 169–170. By tenth grade J.C. was\n\nabsent 43 times, or over 30% of the time.\n\n In April 2013, while in ninth grade, J.C. was admitted to Hershey Medical Center\n\nfor surgery. Shortly thereafter in May, the school received a letter from his physician\n\nstating that J.C. should be allowed to cease activities during his physical education\n\nclasses if he experienced pain. Id. at 170. In July 2013 the school received another letter\n\nfrom J.C.’s doctor stating that he should be allowed to leave class to use the bathroom on\n\na liberal basis. Id. It appears Cumberland agreed to these accommodations.\n\n On January 17, 2014, J.C. had a disciplinary incident where he, apparently along\n\nwith several friends, attempted to leave the school grounds during the day. The other\n\nstudents fled, while J.C. was apprehended and had disciplinary proceedings brought\n\nagainst him, with an eye toward expulsion. After J.C.’s doctor wrote a letter to the school\n\non January 27, 2014, giving a fuller account of J.C.’s diagnosis and the accommodations\n\nhe required, his parents filed a due process complaint under the IDEA on January 29.\n\nCumberland adopted a Section 504 Service Plan for J.C. in March 2014, which provided\n\nfor a number of accommodations, including an “any time pass” to go to the nurse or the\n\nbathroom, extra time to complete assignments, and the provision of class notes in case of\n\n 3\n\ffrequent absences. Id. at 92–94. After receiving a letter from J.C.’s doctor stating that he\n\nshould receive homebound instruction for half of each school day, Cumberland tried to\n\nimplement this accommodation as well, but things did not go well. J.C. was rarely\n\npresent when the instructor arrived at his house, and even when present was not\n\nmotivated or cooperative. Id. at 107–116.\n\n The school board voted to expel J.C. on April 7, 2014, with the expulsion taking\n\neffect on May 8, 2014. At the same time, Cumberland released its Evaluation Report\n\nfrom its psychologist’s evaluation of J.C. Id. at 123. The report concluded that he did\n\nnot have a “qualifying disability” and thus was not eligible for special education under\n\nthe IDEA. Id. at 152. It also stated that there was insufficient evidence that J.C.’s\n\nCrohn’s disease was responsible for his difficulties in school, and that his condition\n\ncalled for Section 504 accommodations, not IDEA specialized instruction. J.C.’s parents\n\nthen requested an independent educational evaluation (IEE), which reached the opposite\n\nconclusion. Id. at 162–192. Noting the pervasive effect of Crohn’s on J.C.’s life, the IEE\n\nfound that he was eligible for special education under the IDEA and gave numerous\n\n“recommendations for specially designed instruction” to help tailor J.C.’s education to\n\nhis benefit. Id. at 189–191. It also found that J.C. had ADHD and specific learning\n\ndisabilities as to math and listening comprehension. Id. at 189. After J.C. moved to a\n\nneighboring school district, East Pennsboro, for the 2014–'15 school year, that district\n\nadopted an individualized education program (IEP) for J.C. to provide special education\n\nunder the IDEA. Id. at 249–279.\n\n\n\n 4\n\f Meanwhile, the Hearing Officer on J.C.’s due process complaint held a hearing\n\nand issued his decision in February 2015. He found that J.C. was not eligible for special\n\neducation under the IDEA because, even though Crohn’s disease was a qualifying\n\ndisability, it did not require specialized instruction. Id. at 48. The Hearing Officer\n\nendorsed Cumberland’s Evaluation Report and largely dismissed the findings from the\n\nIEE. He noted that while J.C.’s frequent absences doubtless caused much of his\n\nacademic decline, it was not clear that most or all of these absences were caused by\n\nCrohn’s. Id. The Hearing Officer also concluded that, while J.C. was unambiguously\n\ncovered by Section 504, Cumberland had met all of its obligations under that statute by\n\nproviding every accommodation requested by his family. Id. at 50–51.\n\n J.C.’s parents then timely filed a civil action on his behalf in the Middle District of\n\nPennsylvania challenging the Hearing Officer’s decision. See Culley et al. v.\n\nCumberland Valley School District, No. 1:15-cv-00857-JEJ (M.D. Pa. 2015). Ruling on\n\nthe parties’ cross-motions for judgment on the record, the District Court reversed the\n\nHearing Officer, finding that J.C. was eligible under the IDEA, that Cumberland had\n\nviolated its “Child Find” duty to identify students with disabilities, and that it violated\n\nSection 504 by failing to evaluate J.C. prior to March 2014. Op. at 26 (App. at 28).\n\nCumberland now appeals, arguing that the District Court erred by (1) reversing the\n\nHearing Officer’s determination that Cumberland’s Evaluation Report was appropriate,\n\n(2) finding that J.C. was eligible for special education under the IDEA, and (3) finding\n\nthat Cumberland breached its “Child Find” duty.\n\n\n\n 5\n\f The District Court had original jurisdiction under 28 U.S.C. § 1331 and 20 U.S.C.\n\n§ 1415(i)(2). We have appellate jurisdiction under 28 U.S.C. § 1291. We review afresh\n\nthe District Court’s conclusions of law, including whether it applied the correct legal\n\nstandards under the IDEA, and we review its findings of fact for clear error. Ridley\n\nSchool District v. M.R., 680 F.3d 260, 268 (3d Cir. 2012). As to the merits, we review\n\nthe state administrative decision under the so-called “modified de novo” standard, under\n\nwhich the hearing officer’s findings of fact are given “due weight” and treated as “prima\n\nfacie correct,” which means that, if the Court disagrees with those findings, it must\n\nexplain the basis for its disagreement. Id. This is not substantively different from de\n\nnovo review, though courts are cautioned not to substitute their view of sound educational\n\npolicy for that of local school authorities. Id.\n\n Cumberland’s first argument on appeal, concerning the “appropriateness” of the\n\nEvaluation Report, seems to involve a category error on its part. Neither the District\n\nCourt’s decision nor the Hearing Officer used the word “appropriate” in connection with\n\nthe Evaluation Report. Nor do the statutory and regulatory provisions governing IDEA\n\nevaluations. See 20 U.S.C. § 1414(b), 34 C.F.R. § 300.304. The cases Cumberland cites\n\nconcern whether an IEP adopted under the IDEA is appropriate. See, e.g., Board of\n\nEducation of Hendrick Hudson Central School District, Westchester Co. v. Rowley, 458\n\nU.S. 176 (1982). The deference commended by Rowley and the other cases Cumberland\n\ncites, therefore, goes not to the threshold question of eligibility under the IDEA but how\n\nbest to tailor the education of children to their unique needs once they are found eligible.\n\n\n\n 6\n\fThat is of no relevance to this case, where Cumberland found J.C. ineligible for IDEA\n\nspecial education.\n\n The question of the weight to be given to the Evaluation Report, and to the IEE, is\n\nundoubtedly key to the main issue in this case, namely whether J.C. is in fact qualified\n\nfor special education under the IDEA. Cumberland does identify one problem in the\n\nDistrict Court’s analysis: it misquoted the Report as stating that there was “insufficient\n\nevidence to determine eligibility based on the category of Other Health Impairment,”\n\nwhen in fact the Report said that there was “insufficient information that [J.C.] has\n\nlimited alertness due to a medical condition.” Compare Op. at 11 (App. at 13), App. at\n\n152. Hence the Report was not incomplete.\n\n The rest of Cumberland’s arguments misread the record. The District Court did\n\nnot neglect the second prong of IDEA eligibility—that a student need not only have an\n\neligible disability but must also require specially designed instruction due to that\n\ndisability. Rather, its opinion explicitly referred to the correct set of criteria. Op. at 9.\n\nAnd while the Court did not discuss in detail J.C.’s need for specially designed\n\ninstruction, it did give reasons why the Hearing Officer was wrong to discount the IEE,\n\nwhich contained detailed instructions for ways J.C.’s instruction should be modified to\n\nsuit his needs. If credited, then, the IEE provides ample support for finding that J.C. was\n\nIDEA eligible. And we agree that the IEE paints a fuller and more accurate picture of\n\nJ.C.’s conditions than the Evaluation Report.\n\n The Hearing Officer’s principal ground for discounting the independent report was\n\nits finding of a specific learning disability as to mathematics, but the District Court was\n\n 7\n\fcorrect that J.C.’s performance in math was anything but strong. In ninth grade, for\n\ninstance, J.C. failed the first three periods of his basic algebra course, only passing the\n\nentire course (with a D grade) due to a strong final period. App. at 69. Arguably this\n\npattern—strong performance for many years followed by a sharp decline—indicates a\n\n“discrepancy between intellectual ability and academic achievement.” See 22 Pa. Code\n\n§ 14.125. Cumberland cites no evidence for its claim that a specific learning disability\n\ncould not manifest progressively over time, aside from a conclusory citation to the\n\ndefinition of specific learning disabilities as “a disorder in one or more of the basic\n\npsychological processes involved” in various tasks. There is nothing illogical about the\n\nidea that a learning disability might only impair a student’s ability to do the tasks\n\ninvolved in higher and more complex forms of mathematics.\n\n Even aside from this specific dispute, the Hearing Officer was wrong to\n\ncharacterize the independent report as “conclusory;” it is plainly more detailed in its\n\nanalysis than the school’s own Evaluation Report, showing J.C.’s life and the misery his\n\ndisease inflicts on him in far richer context. Compare App. at 151–152, 188–189.\n\nPerhaps if the Hearing Officer’s factual conclusions were entitled to increased deference,\n\nsuch as clear error review, the District Court’s reversal as to the weight of the\n\nindependent evaluation would be more of a problem. But the “modified de novo”\n\nstandard does not actually restrict the Court’s power to reach its own conclusions as to\n\neligibility based on the preponderance of the evidence. This merely requires it to explain\n\nits disagreements with the Hearing Officer, which it did.\n\n\n\n 8\n\f Cumberland also misstates that the school’s Report concluded that J.C. was not\n\nIDEA eligible because of the second criterion, the need for specially designed instruction.\n\nIn fact the Report checked the box indicating that J.C. does not have a qualifying\n\ndisability at all. App. at 152. The Hearing Officer concluded to the contrary that Crohn’s\n\ndisease was a qualifying disability, and Cumberland does not argue otherwise. Nor is\n\nCumberland correct in stating that the East Pennsboro IEP is “actually just an\n\naccommodations plan, but contained on an IEP form instead of on a Section 504 form.”\n\nAppellant’s Br. at 18. Although the IEP does include many of the same accommodations\n\nas the Cumberland Section 504 plan, and states that J.C. must participate in the general\n\neducation curriculum for all classes, it also concludes that he requires itinerant\n\nlearning/emotional support and “specially designed instructional strategies within his\n\nmainstream courses of study.” App. at 262. And while Cumberland argues that there had\n\nnot been sufficient time to see whether the newly enacted Section 504 plan and its\n\naccommodation of homebound instruction would be sufficient to address J.C.’s needs, it\n\nwas already apparent that homebound instruction was, to put it mildly, not going well.\n\n Ultimately the basis for Cumberland’s conviction that J.C. does not require\n\nspecially designed instruction is not the Evaluation Report but rather a disbelief that “a\n\ndisease of the digestive system required adapting the content, methodology, or delivery of\n\nthe academic curriculum.” Appellant’s Br. at 17. But the independent evaluation\n\nexplains the connection well: J.C.’s life has been pervasively shaped in all facets by his\n\ndisease, and his numerous behavioral, emotional, social, and academic problems are, to\n\nsome degree, related to it. App. at 188. It may even, as the Evaluation Report itself\n\n 9\n\fsuggested, App. at 124, contribute to his ADHD—something neither the Report nor the\n\nHearing Officer considered in their analysis of J.C.’s IDEA eligibility. In seeing Crohn’s\n\nas something requiring only a Section 504 accommodation, not IDEA special education,\n\nCumberland and the Hearing Officer both treated the disease as something discrete and\n\nisolated rather than the defining condition of J.C.’s life. The District Court did not err in\n\nfinding to the contrary.\n\n Finally, Cumberland claims the District Court erred in finding that the school\n\nbreached its so-called “Child Find” duty. This refers to a school’s obligation, under\n\nrelevant federal law, to identify students with disabilities who require accommodations or\n\nspecial education services proactively rather than waiting around for a child’s parents to\n\nconfront them with evidence of this need. Both the IDEA and Section 504 impose such a\n\nduty, see 20 U.S.C. § 1412(a)(3); 34 C.F.R. § 104.32. And there appears to be some\n\nconfusion in this case about which “Child Find” duty is actually at issue. The Hearing\n\nOfficer’s decision made no finding as to Child Find under the IDEA because he\n\nconcluded that J.C. was not IDEA-eligible, and then ruled that Cumberland had not\n\nviolated Section 504 by failing to provide accommodations earlier. This analysis did not\n\ndiscuss the 504 Child Find obligation, and reasoned principally that the school had no\n\nnotice that J.C. required accommodations prior to receiving the physician’s notes in 2014.\n\nThe District Court, meanwhile, found a violation of the Child Find duty under the IDEA;\n\nit also found that Cumberland should have provided Section 504 services well before\n\nwhen it started providing those services, but did not discuss the 504 claims in terms of a\n\n\n\n 10\n\fChild Find duty. On appeal, however, both parties’ briefs discuss the Child Find issue as\n\nthough it were a Section 504 question.\n\n Because both the IDEA Child Find and the Section 504 claims involve what\n\nCumberland knew or should have known at what point in time, we will analyze them\n\ntogether. Cumberland knew of J.C.’s diagnosis as early as 2007. This seems sufficient to\n\ntrigger its Section 504 obligations to ensure that J.C. received whatever accommodations\n\nhe might require for his Crohn’s disease, as no one disputes that Crohn’s is sufficient to\n\ntrigger Section 504 coverage. Although it appears Cumberland was willing to make ad\n\nhoc accommodations to J.C.’s needs due to Crohn’s, see App. at 22, this was entirely\n\nreactive. It would be bad enough had J.C.’s performance in school been exemplary. But\n\nfrom seventh grade on he experienced severe academic decline and numerous\n\ndisciplinary issues. The District Court is correct that Cumberland at least should have\n\ninvestigated the question of whether J.C.’s numerous issues stemmed from his\n\ndebilitating, life-threatening disease in a way that would be helped by accommodations.\n\nIt did not do so. The same applies under the IDEA, given that J.C. is IDEA-eligible and\n\nthat among the warning signs was his declining academic performance.\n\n Cumberland contends that the Hearing Officer correctly rejected the Section 504\n\nclaim because J.C. and his parents failed to prove that the “warning signs” they cite were\n\ncaused by Crohn’s. Appellant’s Br. at 26–27. There are two problems here. First, the\n\ndiscussion they cite in the Hearing Officer’s decision was not about Section 504 or the\n\nChild Find obligation at all; instead it concerned whether J.C.’s Crohn’s disease qualified\n\nhim for special education under the IDEA. In that context the Hearing Officer held that\n\n 11\n\fJ.C. had not sufficiently proven that his absences from school were caused by Crohn’s,\n\nsuch that he had not proven his disease adversely affected his education.\n\n Second, Cumberland’s argument is illogical and inconsistent with the basic\n\nconcept of a Child Find obligation. The School knew that J.C. had Crohn’s, and it\n\nobserved the warning signs. There cannot have been a burden on J.C. or his parents to\n\ncome forward, at that time, with evidence the disease was the cause of his problems; that\n\nwould be placing the burden on J.C. and his family for identifying him as a student with a\n\ndisability, precisely what the Child Find duty forbids. If there was no burden at that time,\n\nif the school was obliged to investigate J.C.’s needs under the IDEA and Section 504\n\neven before he had proven that his poor conduct and performance were a result of his\n\ndisease, there can be no requirement for that proof now during litigation. That obligation\n\nwas in play even were his disease not behind his declining performance in school. The\n\nDistrict Court did not err, therefore, in concluding that Cumberland violated its Child\n\nFind obligations under the IDEA and that it violated its obligations under Section 504 by\n\nfailing to adopt a service plan for J.C. until March 2014.\n\n * * * * *\n\n Thus we affirm.\n\n\n\n\n 12", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355860/", "author_raw": "AMBRO, Circuit Judge"}]}
AMBRO
SCIRICA
RENDELL
1
{"AMBRO": ", Circuit", "SCIRICA": ", Circuit", "RENDELL": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578607/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Kevin Culley v. Cumberland Valley School Dist\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-03\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nNOT PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 17-3800\n ________________\n\n KEVIN CULLEY, and; DENISE CULLEY, on behalf of; J.C.\n\n v.\n\n CUMBERLAND VALLEY SCHOOL DISTRICT,\n\n Appellant\n ________________\n\n Appeal from the United States District Court\n for the Middle District of Pennsylvania\n (D.C. Civil Action No. 1-15-cv-00857)\n District Judge: Honorable John E. Jones, III\n ________________\n\n Argued November 6, 2018\n\n Before: AMBRO, SCIRICA, and RENDELL, Circuit Judges\n\n (Opinion filed: December 20, 2018)\n\n\nMark W. Cheramie Walz [Argued]\nSweet, Stevens, Katz & Williams LLP\n331 East Butler Avenue\nP.O. Box 5069\nNew Britain, PA 18901\n Counsel for Appellant\n\nJudith A. Gran [Argued]\nReisman Carolla & Gran LLP\n19 Chestnut Street\nHaddonfield, NJ 08033\n\fPhillip A. Drumheiser\nP.O. Box 890\nCarlisle, PA 17013\n Counsel for Appellees\n\n ________________\n\n OPINION*\n ________________\n\nAMBRO, Circuit Judge\n\n J.C., son of plaintiffs Kevin and Denise Culley, was diagnosed with Crohn’s\n\ndisease at age six. It is a painful, even debilitating, disease that affects the digestive tract\n\nand can cause abdominal pain, diarrhea, fatigue, weight loss, and malnutrition. It can\n\neven be life-threatening. See Mayo Clinic, Crohn’s Disease (Mar. 8, 2018), available at\n\nhttps://www.mayoclinic.org/diseases-conditions/crohns-disease/symptoms-causes/syc-\n\n20353304. After a disciplinary dispute with J.C.’s school, part of the Cumberland Valley\n\nSchool District system, that resulted in his expulsion, J.C.’s parents filed suit claiming\n\nthat Cumberland had violated J.C.’s rights under the Individuals with Disabilities\n\nEducation Act (IDEA), 20 U.S.C. § 1400 et seq., and under Section 504 of the\n\nRehabilitation Act. 29 U.S.C. § 701 et seq. The District Court agreed, and we now\n\naffirm.\n\n Born in 1998, J.C. was diagnosed with Crohn’s disease in 2004. Cumberland was\n\ninformed of the diagnosis in 2007. App. at 53. J.C.’s performance in school was\n\ngenerally strong through his sixth grade year, in 2009–2010, and he did not have\n\n\n\n*\n This disposition is not an opinion of the full Court and pursuant to I.O.P. 5.7 does not\nconstitute binding precedent.\n 2\n\fsignificant behavioral or social difficulties through that time. Id. at 130–131. But from\n\nseventh grade onward, both J.C.’s academic performance and his disciplinary record took\n\nsignificant turns for the worse. From seventh through tenth grade, when the incident\n\ngiving rise to this lawsuit occurred and he was expelled, J.C. maintained a grade point\n\naverage just above a failing mark of 70, had numerous disciplinary incidents, and was\n\nincreasingly absent from school. Id. at 128, 131, 169–170. By tenth grade J.C. was\n\nabsent 43 times, or over 30% of the time.\n\n In April 2013, while in ninth grade, J.C. was admitted to Hershey Medical Center\n\nfor surgery. Shortly thereafter in May, the school received a letter from his physician\n\nstating that J.C. should be allowed to cease activities during his physical education\n\nclasses if he experienced pain. Id. at 170. In July 2013 the school received another letter\n\nfrom J.C.’s doctor stating that he should be allowed to leave class to use the bathroom on\n\na liberal basis. Id. It appears Cumberland agreed to these accommodations.\n\n On January 17, 2014, J.C. had a disciplinary incident where he, apparently along\n\nwith several friends, attempted to leave the school grounds during the day. The other\n\nstudents fled, while J.C. was apprehended and had disciplinary proceedings brought\n\nagainst him, with an eye toward expulsion. After J.C.’s doctor wrote a letter to the school\n\non January 27, 2014, giving a fuller account of J.C.’s diagnosis and the accommodations\n\nhe required, his parents filed a due process complaint under the IDEA on January 29.\n\nCumberland adopted a Section 504 Service Plan for J.C. in March 2014, which provided\n\nfor a number of accommodations, including an “any time pass” to go to the nurse or the\n\nbathroom, extra time to complete assignments, and the provision of class notes in case of\n\n 3\n\ffrequent absences. Id. at 92–94. After receiving a letter from J.C.’s doctor stating that he\n\nshould receive homebound instruction for half of each school day, Cumberland tried to\n\nimplement this accommodation as well, but things did not go well. J.C. was rarely\n\npresent when the instructor arrived at his house, and even when present was not\n\nmotivated or cooperative. Id. at 107–116.\n\n The school board voted to expel J.C. on April 7, 2014, with the expulsion taking\n\neffect on May 8, 2014. At the same time, Cumberland released its Evaluation Report\n\nfrom its psychologist’s evaluation of J.C. Id. at 123. The report concluded that he did\n\nnot have a “qualifying disability” and thus was not eligible for special education under\n\nthe IDEA. Id. at 152. It also stated that there was insufficient evidence that J.C.’s\n\nCrohn’s disease was responsible for his difficulties in school, and that his condition\n\ncalled for Section 504 accommodations, not IDEA specialized instruction. J.C.’s parents\n\nthen requested an independent educational evaluation (IEE), which reached the opposite\n\nconclusion. Id. at 162–192. Noting the pervasive effect of Crohn’s on J.C.’s life, the IEE\n\nfound that he was eligible for special education under the IDEA and gave numerous\n\n“recommendations for specially designed instruction” to help tailor J.C.’s education to\n\nhis benefit. Id. at 189–191. It also found that J.C. had ADHD and specific learning\n\ndisabilities as to math and listening comprehension. Id. at 189. After J.C. moved to a\n\nneighboring school district, East Pennsboro, for the 2014–'15 school year, that district\n\nadopted an individualized education program (IEP) for J.C. to provide special education\n\nunder the IDEA. Id. at 249–279.\n\n\n\n 4\n\f Meanwhile, the Hearing Officer on J.C.’s due process complaint held a hearing\n\nand issued his decision in February 2015. He found that J.C. was not eligible for special\n\neducation under the IDEA because, even though Crohn’s disease was a qualifying\n\ndisability, it did not require specialized instruction. Id. at 48. The Hearing Officer\n\nendorsed Cumberland’s Evaluation Report and largely dismissed the findings from the\n\nIEE. He noted that while J.C.’s frequent absences doubtless caused much of his\n\nacademic decline, it was not clear that most or all of these absences were caused by\n\nCrohn’s. Id. The Hearing Officer also concluded that, while J.C. was unambiguously\n\ncovered by Section 504, Cumberland had met all of its obligations under that statute by\n\nproviding every accommodation requested by his family. Id. at 50–51.\n\n J.C.’s parents then timely filed a civil action on his behalf in the Middle District of\n\nPennsylvania challenging the Hearing Officer’s decision. See Culley et al. v.\n\nCumberland Valley School District, No. 1:15-cv-00857-JEJ (M.D. Pa. 2015). Ruling on\n\nthe parties’ cross-motions for judgment on the record, the District Court reversed the\n\nHearing Officer, finding that J.C. was eligible under the IDEA, that Cumberland had\n\nviolated its “Child Find” duty to identify students with disabilities, and that it violated\n\nSection 504 by failing to evaluate J.C. prior to March 2014. Op. at 26 (App. at 28).\n\nCumberland now appeals, arguing that the District Court erred by (1) reversing the\n\nHearing Officer’s determination that Cumberland’s Evaluation Report was appropriate,\n\n(2) finding that J.C. was eligible for special education under the IDEA, and (3) finding\n\nthat Cumberland breached its “Child Find” duty.\n\n\n\n 5\n\f The District Court had original jurisdiction under 28 U.S.C. § 1331 and 20 U.S.C.\n\n§ 1415(i)(2). We have appellate jurisdiction under 28 U.S.C. § 1291. We review afresh\n\nthe District Court’s conclusions of law, including whether it applied the correct legal\n\nstandards under the IDEA, and we review its findings of fact for clear error. Ridley\n\nSchool District v. M.R., 680 F.3d 260, 268 (3d Cir. 2012). As to the merits, we review\n\nthe state administrative decision under the so-called “modified de novo” standard, under\n\nwhich the hearing officer’s findings of fact are given “due weight” and treated as “prima\n\nfacie correct,” which means that, if the Court disagrees with those findings, it must\n\nexplain the basis for its disagreement. Id. This is not substantively different from de\n\nnovo review, though courts are cautioned not to substitute their view of sound educational\n\npolicy for that of local school authorities. Id.\n\n Cumberland’s first argument on appeal, concerning the “appropriateness” of the\n\nEvaluation Report, seems to involve a category error on its part. Neither the District\n\nCourt’s decision nor the Hearing Officer used the word “appropriate” in connection with\n\nthe Evaluation Report. Nor do the statutory and regulatory provisions governing IDEA\n\nevaluations. See 20 U.S.C. § 1414(b), 34 C.F.R. § 300.304. The cases Cumberland cites\n\nconcern whether an IEP adopted under the IDEA is appropriate. See, e.g., Board of\n\nEducation of Hendrick Hudson Central School District, Westchester Co. v. Rowley, 458\n\nU.S. 176 (1982). The deference commended by Rowley and the other cases Cumberland\n\ncites, therefore, goes not to the threshold question of eligibility under the IDEA but how\n\nbest to tailor the education of children to their unique needs once they are found eligible.\n\n\n\n 6\n\fThat is of no relevance to this case, where Cumberland found J.C. ineligible for IDEA\n\nspecial education.\n\n The question of the weight to be given to the Evaluation Report, and to the IEE, is\n\nundoubtedly key to the main issue in this case, namely whether J.C. is in fact qualified\n\nfor special education under the IDEA. Cumberland does identify one problem in the\n\nDistrict Court’s analysis: it misquoted the Report as stating that there was “insufficient\n\nevidence to determine eligibility based on the category of Other Health Impairment,”\n\nwhen in fact the Report said that there was “insufficient information that [J.C.] has\n\nlimited alertness due to a medical condition.” Compare Op. at 11 (App. at 13), App. at\n\n152. Hence the Report was not incomplete.\n\n The rest of Cumberland’s arguments misread the record. The District Court did\n\nnot neglect the second prong of IDEA eligibility—that a student need not only have an\n\neligible disability but must also require specially designed instruction due to that\n\ndisability. Rather, its opinion explicitly referred to the correct set of criteria. Op. at 9.\n\nAnd while the Court did not discuss in detail J.C.’s need for specially designed\n\ninstruction, it did give reasons why the Hearing Officer was wrong to discount the IEE,\n\nwhich contained detailed instructions for ways J.C.’s instruction should be modified to\n\nsuit his needs. If credited, then, the IEE provides ample support for finding that J.C. was\n\nIDEA eligible. And we agree that the IEE paints a fuller and more accurate picture of\n\nJ.C.’s conditions than the Evaluation Report.\n\n The Hearing Officer’s principal ground for discounting the independent report was\n\nits finding of a specific learning disability as to mathematics, but the District Court was\n\n 7\n\fcorrect that J.C.’s performance in math was anything but strong. In ninth grade, for\n\ninstance, J.C. failed the first three periods of his basic algebra course, only passing the\n\nentire course (with a D grade) due to a strong final period. App. at 69. Arguably this\n\npattern—strong performance for many years followed by a sharp decline—indicates a\n\n“discrepancy between intellectual ability and academic achievement.” See 22 Pa. Code\n\n§ 14.125. Cumberland cites no evidence for its claim that a specific learning disability\n\ncould not manifest progressively over time, aside from a conclusory citation to the\n\ndefinition of specific learning disabilities as “a disorder in one or more of the basic\n\npsychological processes involved” in various tasks. There is nothing illogical about the\n\nidea that a learning disability might only impair a student’s ability to do the tasks\n\ninvolved in higher and more complex forms of mathematics.\n\n Even aside from this specific dispute, the Hearing Officer was wrong to\n\ncharacterize the independent report as “conclusory;” it is plainly more detailed in its\n\nanalysis than the school’s own Evaluation Report, showing J.C.’s life and the misery his\n\ndisease inflicts on him in far richer context. Compare App. at 151–152, 188–189.\n\nPerhaps if the Hearing Officer’s factual conclusions were entitled to increased deference,\n\nsuch as clear error review, the District Court’s reversal as to the weight of the\n\nindependent evaluation would be more of a problem. But the “modified de novo”\n\nstandard does not actually restrict the Court’s power to reach its own conclusions as to\n\neligibility based on the preponderance of the evidence. This merely requires it to explain\n\nits disagreements with the Hearing Officer, which it did.\n\n\n\n 8\n\f Cumberland also misstates that the school’s Report concluded that J.C. was not\n\nIDEA eligible because of the second criterion, the need for specially designed instruction.\n\nIn fact the Report checked the box indicating that J.C. does not have a qualifying\n\ndisability at all. App. at 152. The Hearing Officer concluded to the contrary that Crohn’s\n\ndisease was a qualifying disability, and Cumberland does not argue otherwise. Nor is\n\nCumberland correct in stating that the East Pennsboro IEP is “actually just an\n\naccommodations plan, but contained on an IEP form instead of on a Section 504 form.”\n\nAppellant’s Br. at 18. Although the IEP does include many of the same accommodations\n\nas the Cumberland Section 504 plan, and states that J.C. must participate in the general\n\neducation curriculum for all classes, it also concludes that he requires itinerant\n\nlearning/emotional support and “specially designed instructional strategies within his\n\nmainstream courses of study.” App. at 262. And while Cumberland argues that there had\n\nnot been sufficient time to see whether the newly enacted Section 504 plan and its\n\naccommodation of homebound instruction would be sufficient to address J.C.’s needs, it\n\nwas already apparent that homebound instruction was, to put it mildly, not going well.\n\n Ultimately the basis for Cumberland’s conviction that J.C. does not require\n\nspecially designed instruction is not the Evaluation Report but rather a disbelief that “a\n\ndisease of the digestive system required adapting the content, methodology, or delivery of\n\nthe academic curriculum.” Appellant’s Br. at 17. But the independent evaluation\n\nexplains the connection well: J.C.’s life has been pervasively shaped in all facets by his\n\ndisease, and his numerous behavioral, emotional, social, and academic problems are, to\n\nsome degree, related to it. App. at 188. It may even, as the Evaluation Report itself\n\n 9\n\fsuggested, App. at 124, contribute to his ADHD—something neither the Report nor the\n\nHearing Officer considered in their analysis of J.C.’s IDEA eligibility. In seeing Crohn’s\n\nas something requiring only a Section 504 accommodation, not IDEA special education,\n\nCumberland and the Hearing Officer both treated the disease as something discrete and\n\nisolated rather than the defining condition of J.C.’s life. The District Court did not err in\n\nfinding to the contrary.\n\n Finally, Cumberland claims the District Court erred in finding that the school\n\nbreached its so-called “Child Find” duty. This refers to a school’s obligation, under\n\nrelevant federal law, to identify students with disabilities who require accommodations or\n\nspecial education services proactively rather than waiting around for a child’s parents to\n\nconfront them with evidence of this need. Both the IDEA and Section 504 impose such a\n\nduty, see 20 U.S.C. § 1412(a)(3); 34 C.F.R. § 104.32. And there appears to be some\n\nconfusion in this case about which “Child Find” duty is actually at issue. The Hearing\n\nOfficer’s decision made no finding as to Child Find under the IDEA because he\n\nconcluded that J.C. was not IDEA-eligible, and then ruled that Cumberland had not\n\nviolated Section 504 by failing to provide accommodations earlier. This analysis did not\n\ndiscuss the 504 Child Find obligation, and reasoned principally that the school had no\n\nnotice that J.C. required accommodations prior to receiving the physician’s notes in 2014.\n\nThe District Court, meanwhile, found a violation of the Child Find duty under the IDEA;\n\nit also found that Cumberland should have provided Section 504 services well before\n\nwhen it started providing those services, but did not discuss the 504 claims in terms of a\n\n\n\n 10\n\fChild Find duty. On appeal, however, both parties’ briefs discuss the Child Find issue as\n\nthough it were a Section 504 question.\n\n Because both the IDEA Child Find and the Section 504 claims involve what\n\nCumberland knew or should have known at what point in time, we will analyze them\n\ntogether. Cumberland knew of J.C.’s diagnosis as early as 2007. This seems sufficient to\n\ntrigger its Section 504 obligations to ensure that J.C. received whatever accommodations\n\nhe might require for his Crohn’s disease, as no one disputes that Crohn’s is sufficient to\n\ntrigger Section 504 coverage. Although it appears Cumberland was willing to make ad\n\nhoc accommodations to J.C.’s needs due to Crohn’s, see App. at 22, this was entirely\n\nreactive. It would be bad enough had J.C.’s performance in school been exemplary. But\n\nfrom seventh grade on he experienced severe academic decline and numerous\n\ndisciplinary issues. The District Court is correct that Cumberland at least should have\n\ninvestigated the question of whether J.C.’s numerous issues stemmed from his\n\ndebilitating, life-threatening disease in a way that would be helped by accommodations.\n\nIt did not do so. The same applies under the IDEA, given that J.C. is IDEA-eligible and\n\nthat among the warning signs was his declining academic performance.\n\n Cumberland contends that the Hearing Officer correctly rejected the Section 504\n\nclaim because J.C. and his parents failed to prove that the “warning signs” they cite were\n\ncaused by Crohn’s. Appellant’s Br. at 26–27. There are two problems here. First, the\n\ndiscussion they cite in the Hearing Officer’s decision was not about Section 504 or the\n\nChild Find obligation at all; instead it concerned whether J.C.’s Crohn’s disease qualified\n\nhim for special education under the IDEA. In that context the Hearing Officer held that\n\n 11\n\fJ.C. had not sufficiently proven that his absences from school were caused by Crohn’s,\n\nsuch that he had not proven his disease adversely affected his education.\n\n Second, Cumberland’s argument is illogical and inconsistent with the basic\n\nconcept of a Child Find obligation. The School knew that J.C. had Crohn’s, and it\n\nobserved the warning signs. There cannot have been a burden on J.C. or his parents to\n\ncome forward, at that time, with evidence the disease was the cause of his problems; that\n\nwould be placing the burden on J.C. and his family for identifying him as a student with a\n\ndisability, precisely what the Child Find duty forbids. If there was no burden at that time,\n\nif the school was obliged to investigate J.C.’s needs under the IDEA and Section 504\n\neven before he had proven that his poor conduct and performance were a result of his\n\ndisease, there can be no requirement for that proof now during litigation. That obligation\n\nwas in play even were his disease not behind his declining performance in school. The\n\nDistrict Court did not err, therefore, in concluding that Cumberland violated its Child\n\nFind obligations under the IDEA and that it violated its obligations under Section 504 by\n\nfailing to adopt a service plan for J.C. until March 2014.\n\n * * * * *\n\n Thus we affirm.\n\n\n\n\n 12\n[END_CASE]", "role": "user" } ]
4,578,608
John F. SIMPSON, T/A Warrior Ridge Trading; T/A LCT Pro Shop v. ATTORNEY GENERAL UNITED STATES OF AMERICA; Director, Bureau of Alcohol, Tobacco, Firearms & Explosives; Director of Industry Operations, Bureau of Alcohol, Tobacco, Firearms & Explosives; United States of America John F. Simpson, Appellant
John Simpson v. Attorney General United States
2019-01-03
17-3718
U.S. Court of Appeals for the Third Circuit
{"judges": "Chagares, Jordan, Vanaskie", "parties": "", "opinions": [{"author": "VANASKIE, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-3718\n _____________\n\nJOHN F. SIMPSON, t/a Warrior Ridge Trading; t/a LCT Pro Shop\n\n v.\n\n ATTORNEY GENERAL UNITED STATES OF AMERICA;\nDIRECTOR, BUREAU OF ALCOHOL, TOBACCO, FIREARMS\n & EXPLOSIVES; DIRECTOR OF INDUSTRY OPERATIONS,\n BUREAU OF ALCOHOL, TOBACCO, FIREARMS &\n EXPLOSIVES; UNITED STATES OF AMERICA\n\n John F. Simpson,\n Appellant\n\n _____________\n\n On Appeal from the United States District Court\n for the Middle District of Pennsylvania\n District Judge: Honorable John E. Jones, III\n (D.C. Civil No. 1-15-mc-00297)\n ______________\n\n Argued October 30, 2018\n ______________\n\f Before: CHAGARES, JORDAN, and VANASKIE, Circuit\n Judges\n\n (Opinion Filed: January 3, 2019)\n\nAdam J. Kraut\nJoshua Prince [ARGUED]\nPrince Law Offices\n646 Lenape Road\nBechtelsville, PA 19505\n Counsel for Appellant\n\nDavid J. Freed\nUnited States Attorney\nCarlo D. Marchioli [ARGUED]\nKate L. Mershimer\nOffice of United States Attorney\n228 Walnut Street, P.O. Box 11754\n220 Federal Building and Courthouse\nHarrisburg, PA 17108\n\nJeffrey A. Cohen\nATF Associate Chief Counsel\nJohn Kevin White\nATF Division Counsel\n601 Walnut Street, Suite 1000E\nPhiladelphia, PA 19106\n Counsel for Appellees\n\n\n\n The Honorable Judge Vanaskie transmitted the opinion to the\nClerk for filing prior to retiring from the bench on January 1, 2019.\nDue to the intervening holiday, the opinion has been entered on the\ndocket by the Clerk this day.\n\n\n\n\n 2\n\f ________________\n\n OPINION\n ________________\n\nVANASKIE, Circuit Judge.\n\n Appellant John Simpson appeals the District Court’s\norder granting summary judgment for Appellees and affirming\nthe Bureau of Alcohol, Tobacco, Firearms & Explosives’\n(“ATF”) revocation of his federal firearms licenses (“FFLs”).\nAfter an annual compliance investigation, the ATF determined\nthat Simpson had committed over 400 willful violations of the\nGun Control Act of 1968, 18 U.S.C. § 921 et seq. (“GCA”),\nand therefore revoked his FFLs pursuant to 18 U.S.C. § 923(e)\nand 27 C.F.R. § 478.73. After an administrative hearing, the\nATF affirmed its revocation decision and Simpson filed a\npetition for judicial review under 18 U.S.C. § 923(f)(3). The\nDistrict Court, adopting a Magistrate Judge’s report and\nrecommendation, granted summary judgment in favor of the\nATF. For the following reasons, we will affirm.\n\n Simpson’s appeal presents us with the question of what\nstandard to apply to determine whether a violation of the GCA\nwas willful, an issue we have not yet addressed in a\nprecedential opinion. In a non-precedential opinion, we found\npersuasive the willfulness standard used by seven other\ncircuits: knowledge of a legal obligation and purposeful\ndisregard or plain indifference to it. Taylor v. Hughes, 548 F.\nApp’x 822, 824 (3d Cir. 2013) (citing Borchardt Rifle Corp. v.\nCook, 684 F.3d 1037, 1042 n.9 (10th Cir. 2012) (listing cases)).\nAgreeing with the unanimous view of all the Courts of Appeals\nto have addressed this issue, we now hold in this precedential\n\n\n\n\n 3\n\fopinion that this willfulness standard applies to violations of\nthe GCA. Because it is clear that Simpson knew of and was\nplainly indifferent to his obligations by committing hundreds\nof GCA violations, we will affirm the District Court’s ruling.\n\n I.\n\n Simpson applied for a dealer’s FFL in 2010, which\nprompted an ATF interview. During the interview, ATF\nrepresentatives discussed Simpson’s legal responsibilities and\nobligations as a firearms dealer, covering topics such as\nacquisition and disposition (“A&D”) recordkeeping, sales to\nlaw enforcement, out-of-state gun sales, prohibited sales,\nconsignment of firearms, and personal firearms. At the end of\nthe meeting, Simpson signed an Acknowledgement of Federal\nFirearms Regulations, certifying that he understood his\nresponsibility to learn and follow all laws and regulations\ngoverning his FFL. Simpson subsequently received an FFL\nand opened a firearms store, Warrior Ridge Trading\n\n In 2011, Simpson attended a seminar for FFL holders,\nwhere ATF officials discussed federal firearms regulations and\nshowed sample Firearms Transaction Records. In 2012, after\nconsulting with the ATF about his desire to assemble AR-15\nrifles, Simpson applied for an additional FFL to manufacture\nfirearms. ATF officials met with him and discussed the legal\nresponsibilities associated with a manufacturer’s license,\nincluding the duty to mark all manufactured firearms and to\nkeep a separate manufacturing A&D book. Simpson again\nsigned an acknowledgement form certifying that he understood\nhis legal obligations under his additional FFL.\n\n In February 2014, Simpson applied to relocate his FFLs\nbecause he planned to move his firearms store to another\n\n\n\n\n 4\n\flocation. An ATF Industry Operations Inspector (“IOI”) met\nwith him and discussed his application. Simpson once again\nsigned a form acknowledging that he understood his\nresponsibilities and obligations under the GCA.\n\n In April 2014, ATF conducted a compliance inspection\nof Simpson’s FFLs pursuant to 18 U.S.C. § 923(g)(1)(C). ]\nAccording to IOI Susan Whitman, this inspection “was the\nworst [she] ever conducted,” and, based upon her report, the\nATF decided to revoke Simpson’s FFLs. (App. I 7). Simpson\nrequested a review of the revocation decision pursuant to 18\nU.S.C. § 923(f)(2) and 27 C.F.R. § 478.74. After a hearing,\nATF Director of Industry Operations (“DIO”) Juan Orellana\nfound that Simpson had committed over 400 willful violations\nof the GCA. As summarized by the Magistrate Judge, these\nviolations include:\n\n [S]elling or delivering multiple\n firearms without having completed\n Firearm Transaction Records,\n ATF Forms 4473, and without\n Simpson making the required\n entries in his [A&D] Book;\n transferring firearms without\n conducting background checks;\n dealing firearms at the Alexandria\n Sportsman’s Club and in West\n Virginia without obtaining a\n license to do so; selling or\n delivering firearms, firearm\n frames, or firearm receivers in\n seven instances to individuals who\n did not live in Pennsylvania;\n incorrectly identifying in multiple\n\n\n\n\n 5\n\f instances the firearms that had\n been transferred; failing to identify\n and mark 14 firearms that he\n manufactured, and failing to make\n the required records for those\n manufactured firearms; failing to\n record the disposition of five\n firearms to other licensees; failing\n to record the record of disposition\n of 30 firearms to non-licensees;\n failing on over 70 occasions to\n record required information in his\n A&D Book; failing in\n approximately 200 instances to\n record information on ATF Forms\n 4473; failing to appropriately sign\n and date ATF Form 4473 in dozens\n of cases to indicate that he did not\n have reasonable cause to believe\n that a transferee was disqualified\n from receiving a firearm; and\n failing to submit an Annual\n Firearms Manufacturing and\n Exportation Report (ATF Form\n 5300.11) in 2012 and 2013.\n\n(App. I 7-8; see also App. II 137-98). As such, the ATF issued\nfinal revocation notices to Simpson.\n\n Simpson then filed a petition for judicial review and\nmoved for an emergency stay of the revocation of his FFLs.\nThe District Court denied his motion, finding that Simpson was\nunlikely to “succe[ed] on the merits, given the numerosity and\ntypes of violations,” and because the court was not “persuaded\n\n\n\n\n 6\n\fby [Simpson’s] contention that he was inadequately trained by\n[the ATF].” (App. 9). The case was then referred to a\nMagistrate Judge for pretrial management. Upon completion\nof discovery, the parties filed cross-motions for summary\njudgment.\n\n Addressing the cross-motions in a Report and\nRecommendation, the Magistrate Judge concluded that the\nATF was authorized to revoke Simpson’s FFLs because he had\nwillfully committed over 400 violations of the GCA. (App. I\n33-34). The District Court adopted the report and\nrecommendation in its entirety, and thus granted summary\njudgment for the ATF and affirmed its revocation of Simpson’s\nFFLs. Simpson’s timely appeal followed.\n\n\n\n II.\n\n The District Court had jurisdiction to review the ATF’s\nrevocation decision under 18 U.S.C. § 923(f), 5 U.S.C. § 702,\nand 28 U.S.C. § 1331. We have appellate jurisdiction pursuant\nto 28 U.S.C. § 1291. We exercise de novo review over the\nDistrict Court’s grant of summary judgment. See, e.g., Kelly\nv. Borough of Carlisle, 622 F.3d 248, 253 (3d Cir. 2010). A\ngrant of summary judgment is warranted “if the movant shows\nthat there is no genuine dispute as to any material fact and the\nmovant is entitled to judgment as a matter of law.” Fed. R.\nCiv. P. 56(a). Further, an administrative record “enjoys a\npresumption of veracity” at summary judgment. Am. Arms\nInt’l v. Herbert, 563 F.3d 78, 86 n.12 (4th Cir. 2009) (citation\nomitted).\n\n\n\n\n 7\n\f III.\n\n Under the GCA, the ATF may revoke an FFL if the\nlicense holder willfully violated any provision of the GCA or\nany rule or regulation prescribed under the GCA. 18 U.S.C.\n§ 923(e); see also 27 C.F.R. § 478.73. “A single willful\nviolation [of the GCA] authorizes the ATF to revoke the\nviolator’s FFL, regardless of how severe . . . .” Fairmont Cash\nMgmt., L.L.C. v. James, 858 F.3d 356, 362 (5th Cir. 2017).\nThus, in the GCA context, our review of the District Court’s\ngrant of summary judgment requires us to determine whether\nthere was no genuine dispute as to any material fact\nestablishing even one willful violation of the GCA. See Am.\nArms, 563 F.3d at 86 (noting that “a single uncontested\nviolation suffices to uphold” summary judgment for the ATF\n(citing Armalite, Inc. v. Lambert, 544 F.3d 644, 649 (6th Cir.\n2008))).\n\n Eight other Courts of Appeals have held that a violation\nof the GCA is willful where the licensee knew of his legal\nobligation and purposefully disregarded or was plainly\nindifferent to the requirements. See Borchardt Rifle, 684 F.3d\nat 1042; Fairmont Cash Mgmt., 858 F.3d at 362; Armalite, 544\nF.3d at 647; RSM, Inc. v. Herbert, 466 F.3d 316, 317 (4th Cir.\n2006); Article II Gun Shop, Inc. v. Gonzales, 441 F.3d 492, 497\n(7th Cir. 2006); Willingham Sports, Inc. v. ATF, 415 F.3d 1274,\n1277 (11th Cir. 2005); Perri v. ATF, 637 F.2d 1332, 1336 (9th\nCir. 1981); Lewin v. Blumenthal, 590 F.2d 268, 269 (8th Cir.\n1979). We find this definition of willfulness to be appropriate.\nIndeed, this standard mirrors the willfulness standard we have\napplied in the parallel context of ATF revocations of fireworks\nand explosives licenses for violations of federal explosives\nlaws. See Vineland Fireworks Co. v. ATF, 544 F.3d 509, 517–\n19 (upholding the ATF’s interpretation of willful because it\n\n\n\n\n 8\n\fwas reasonable).1 In Vineland, we upheld that willfulness\n“do[es] not require a bad purpose,” or an intent to disobey the\nlaw, but rather willfulness can be established by a mere\n“violation of the regulations with knowledge of their\nrequirements.” Id. Moreover, both parties in this case agree\nwith this willfulness standard. Accordingly, we now join our\nsister circuits in holding that a violation of the GCA is willful\nwhere the licensee: (1) knew of his legal obligation under the\nGCA, and (2) either purposefully disregarded or was plainly\nindifferent to GCA requirements.\n\n Here, Simpson has been charged with willfully\nviolating the GCA over 400 times. He contends that he did not\nfully understand his obligations and that any violations he\ncommitted were not willful, but due to mistake or ignorance.\nWe disagree, as the record indicates that Simpson was well\napprised of his duties under the GCA but continually violated\nGCA recordkeeping, manufacturing, and sales requirements.\n\n\n\n 1\n In Vineland, we deferred to the ATF’s interpretation\nof willfulness under federal explosives law because we found\nit reasonable. See Vineland, 544 F.3d at 518 n.17. Our review\nof explosives licensing decisions is governed only by 5 U.S.C.\n§ 706, so we apply Chevron deference to reasonable agency\ndecisions. See 18 U.S.C. § 843(e)(2); see also Chevron,\nU.S.A., Inc. v. Nat. Res. Def. Council, Inc., 467 U.S. 837\n(1984). In contrast, the GCA explicitly tasks courts with\nconducting de novo review of ATF licensing denials or\nrevocations. See 18 U.S.C. § 923(f)(3). As such, we review\ndistrict court decisions regarding ATF firearms licensing de\nnovo. See, e.g., Willingham Sports, 415 F.3d at 1275-76.\n\n\n\n\n 9\n\f A.\n\n The record shows that Simpson was informed of his\nobligations as an FFL licensee. For example, Simpson met\nwith ATF officials three times about his FFLs and, at the\nconclusion of each meeting, he signed a form acknowledging\nthat he discussed various regulatory topics with the ATF. In\naddition, Simpson attended an ATF seminar for FFL holders\nwhere he learned more about his obligations under the GCA.\n\n The record also demonstrates that Simpson often\ncomplied with GCA requirements. On numerous occasions,\nSimpson lawfully sold firearms and fully completed the A&D\nrecordkeeping required under the GCA. Also, he applied to\nrelocate his FFL, demonstrating that he knew that he was only\nallowed to sell firearms from his approved FFL location. His\nfull compliance with GCA requirements in some instances\nbelies his assertion that he did not understand those\nrequirements.\n\n Further, some of Simpson’s actions illustrate that he\nunderstood the GCA regulatory scheme quite well. For\nexample, he sometimes transferred firearms from his FFL\ninventory to his personal collection, thereby taking advantage\nof a statutory loophole that allowed him to later sell the\nfirearms at gun shows without conducting background checks.\nSuch action is inconsistent with that of a person who does not\nunderstand the GCA regulatory scheme. Accordingly, we find\nthat no reasonable fact-finder could disagree that Simpson\nknew and understood his GCA obligations as an FFL licensee.\n\n\n\n\n 10\n\f B.\n\n In this case, the ATF has alleged that Simpson was\nplainly indifferent to the GCA’s requirements. We must\ntherefore determine what constitutes plain indifference under\nthe willfulness standard we have adopted.\n\n Plain indifference is demonstrated by “a lack of concern\nfor [GCA] regulations. . . .” Am. Arms Int’l, 563 F.3d at 87. A\nlack of concern may be shown by circumstantial evidence—\nsuch as repeated violations or a large quantity of violations.\nSee, e.g., Borchardt Rifle, 684 F.3d at 1043–44; Am. Arms\nInt’l, 563 F.3d at 87; On Target Sporting Goods, Inc. v. Att’y\nGen., 472 F.3d 572, 575 (8th Cir. 2007); RSM, Inc., 466 F.3d\nat 322; Willingham Sports, 415 F.3d at 1277.\n\n The ATF charged Simpson with willfully violating a\nlong list of separate provisions of the GCA under his\nmanufacturer’s FFL, including, inter alia:\n\n (a) selling firearms without completing Form 4473s;\n (b) selling or delivering firearms without recording the\n disposition in his A&D book;\n (c) transferring firearms without conducting\n background checks;\n (d) dealing firearms outside of his FFL premises;\n (e) selling or delivering firearms to non-Pennsylvania\n residents;\n (f) transferring firearms and misidentifying\n corresponding A&D entries;\n (g) failing to identify and mark manufactured firearms;\n (h) failing to record the manufacture of firearms in his\n A&D book;\n\n\n\n\n 11\n\f (i) failing to record dispositions of firearms to FFL\n holders and non-licensees;\n (j) failing to complete all fields of Form 4473s; and\n (k) failing to sign and date Form 4473s.\n\n(See App. I 8). Additionally, the ATF charged Simpson with\nwillfully violating another series of provisions of the GCA\nunder his dealer’s FFL. These include, inter alia:\n\n (a) selling firearms without completing Form 4473s;\n (b) selling or delivering firearms without recording the\n disposition in his A&D book;\n (c) transferring firearms without conducting\n background checks;\n (d) selling firearms in West Virginia;\n (e) selling or delivering firearms to non-Pennsylvania\n residents\n (f) purchasing firearms without recording the purchases\n in his A&D book;\n (g) failing to complete all fields of Form 4473s; and\n (h) failing to sign and date Form 4473s.\n\nId.\n\n Simpson contends that all of these violations either were\nmere mistakes or were due to his “fundamental\nmisunderstanding as to the importance” of GCA recordkeeping\nrequirements. (Appellant’s Br. 35). However, in view of the\nfact that Simpson received training on his obligations and\nexplicitly acknowledged that he understood his GCA\nobligations, the sheer number and continuing nature of the\nviolations clearly demonstrate Simpson’s plain indifference to\nthe GCA’s requirements.\n\n\n\n\n 12\n\f While there is no dispute that Simpson violated the\nGCA on numerous occasions, there is also evidence of other\nfirearms transactions in which Simpson fully complied with\nGCA requirements by completing, signing, and dating Form\n4473s, recording the dispositions in his A&D book, and\nconducting background checks. This inconsistent conduct\nsuggests both that Simpson knew of his obligations and was\nindifferent to complying with them. Moreover, there is\nevidence of blatant GCA violations. For example, Simpson\nroutinely transferred receivers to out-of-state residents—in\nclear violation of the GCA—but falsely recorded the transfers\nas rifle sales in his A&D book, making these transactions\nappear lawful. Such behavior is indicative of Simpson’s lack\nof concern for his GCA obligations as an FFL holder.\n\n In sum, the record sufficiently shows that Simpson had\nknowledge of his FFL obligations, yet acted plainly\nindifferently to them, thus willfully violating the GCA.\nAccordingly, we find that the ATF was authorized to revoke\nSimpson’s FFLs.\n\n\n\n IV.\n\n For the foregoing reasons we will affirm the District\nCourt’s grant of summary judgment in favor of the ATF,\naffirming its revocation of Simpson’s FFLs.\n\n\n\n\n 13", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355861/", "author_raw": "VANASKIE, Circuit Judge."}]}
CHAGARES
JORDAN
VANASKIE
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578608/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: John F. SIMPSON, T/A Warrior Ridge Trading; T/A LCT Pro Shop v. ATTORNEY GENERAL UNITED STATES OF AMERICA; Director, Bureau of Alcohol, Tobacco, Firearms & Explosives; Director of Industry Operations, Bureau of Alcohol, Tobacco, Firearms & Explosives; United States of America John F. Simpson, Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-03\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-3718\n _____________\n\nJOHN F. SIMPSON, t/a Warrior Ridge Trading; t/a LCT Pro Shop\n\n v.\n\n ATTORNEY GENERAL UNITED STATES OF AMERICA;\nDIRECTOR, BUREAU OF ALCOHOL, TOBACCO, FIREARMS\n & EXPLOSIVES; DIRECTOR OF INDUSTRY OPERATIONS,\n BUREAU OF ALCOHOL, TOBACCO, FIREARMS &\n EXPLOSIVES; UNITED STATES OF AMERICA\n\n John F. Simpson,\n Appellant\n\n _____________\n\n On Appeal from the United States District Court\n for the Middle District of Pennsylvania\n District Judge: Honorable John E. Jones, III\n (D.C. Civil No. 1-15-mc-00297)\n ______________\n\n Argued October 30, 2018\n ______________\n\f Before: CHAGARES, JORDAN, and VANASKIE, Circuit\n Judges\n\n (Opinion Filed: January 3, 2019)\n\nAdam J. Kraut\nJoshua Prince [ARGUED]\nPrince Law Offices\n646 Lenape Road\nBechtelsville, PA 19505\n Counsel for Appellant\n\nDavid J. Freed\nUnited States Attorney\nCarlo D. Marchioli [ARGUED]\nKate L. Mershimer\nOffice of United States Attorney\n228 Walnut Street, P.O. Box 11754\n220 Federal Building and Courthouse\nHarrisburg, PA 17108\n\nJeffrey A. Cohen\nATF Associate Chief Counsel\nJohn Kevin White\nATF Division Counsel\n601 Walnut Street, Suite 1000E\nPhiladelphia, PA 19106\n Counsel for Appellees\n\n\n\n The Honorable Judge Vanaskie transmitted the opinion to the\nClerk for filing prior to retiring from the bench on January 1, 2019.\nDue to the intervening holiday, the opinion has been entered on the\ndocket by the Clerk this day.\n\n\n\n\n 2\n\f ________________\n\n OPINION\n ________________\n\nVANASKIE, Circuit Judge.\n\n Appellant John Simpson appeals the District Court’s\norder granting summary judgment for Appellees and affirming\nthe Bureau of Alcohol, Tobacco, Firearms & Explosives’\n(“ATF”) revocation of his federal firearms licenses (“FFLs”).\nAfter an annual compliance investigation, the ATF determined\nthat Simpson had committed over 400 willful violations of the\nGun Control Act of 1968, 18 U.S.C. § 921 et seq. (“GCA”),\nand therefore revoked his FFLs pursuant to 18 U.S.C. § 923(e)\nand 27 C.F.R. § 478.73. After an administrative hearing, the\nATF affirmed its revocation decision and Simpson filed a\npetition for judicial review under 18 U.S.C. § 923(f)(3). The\nDistrict Court, adopting a Magistrate Judge’s report and\nrecommendation, granted summary judgment in favor of the\nATF. For the following reasons, we will affirm.\n\n Simpson’s appeal presents us with the question of what\nstandard to apply to determine whether a violation of the GCA\nwas willful, an issue we have not yet addressed in a\nprecedential opinion. In a non-precedential opinion, we found\npersuasive the willfulness standard used by seven other\ncircuits: knowledge of a legal obligation and purposeful\ndisregard or plain indifference to it. Taylor v. Hughes, 548 F.\nApp’x 822, 824 (3d Cir. 2013) (citing Borchardt Rifle Corp. v.\nCook, 684 F.3d 1037, 1042 n.9 (10th Cir. 2012) (listing cases)).\nAgreeing with the unanimous view of all the Courts of Appeals\nto have addressed this issue, we now hold in this precedential\n\n\n\n\n 3\n\fopinion that this willfulness standard applies to violations of\nthe GCA. Because it is clear that Simpson knew of and was\nplainly indifferent to his obligations by committing hundreds\nof GCA violations, we will affirm the District Court’s ruling.\n\n I.\n\n Simpson applied for a dealer’s FFL in 2010, which\nprompted an ATF interview. During the interview, ATF\nrepresentatives discussed Simpson’s legal responsibilities and\nobligations as a firearms dealer, covering topics such as\nacquisition and disposition (“A&D”) recordkeeping, sales to\nlaw enforcement, out-of-state gun sales, prohibited sales,\nconsignment of firearms, and personal firearms. At the end of\nthe meeting, Simpson signed an Acknowledgement of Federal\nFirearms Regulations, certifying that he understood his\nresponsibility to learn and follow all laws and regulations\ngoverning his FFL. Simpson subsequently received an FFL\nand opened a firearms store, Warrior Ridge Trading\n\n In 2011, Simpson attended a seminar for FFL holders,\nwhere ATF officials discussed federal firearms regulations and\nshowed sample Firearms Transaction Records. In 2012, after\nconsulting with the ATF about his desire to assemble AR-15\nrifles, Simpson applied for an additional FFL to manufacture\nfirearms. ATF officials met with him and discussed the legal\nresponsibilities associated with a manufacturer’s license,\nincluding the duty to mark all manufactured firearms and to\nkeep a separate manufacturing A&D book. Simpson again\nsigned an acknowledgement form certifying that he understood\nhis legal obligations under his additional FFL.\n\n In February 2014, Simpson applied to relocate his FFLs\nbecause he planned to move his firearms store to another\n\n\n\n\n 4\n\flocation. An ATF Industry Operations Inspector (“IOI”) met\nwith him and discussed his application. Simpson once again\nsigned a form acknowledging that he understood his\nresponsibilities and obligations under the GCA.\n\n In April 2014, ATF conducted a compliance inspection\nof Simpson’s FFLs pursuant to 18 U.S.C. § 923(g)(1)(C). ]\nAccording to IOI Susan Whitman, this inspection “was the\nworst [she] ever conducted,” and, based upon her report, the\nATF decided to revoke Simpson’s FFLs. (App. I 7). Simpson\nrequested a review of the revocation decision pursuant to 18\nU.S.C. § 923(f)(2) and 27 C.F.R. § 478.74. After a hearing,\nATF Director of Industry Operations (“DIO”) Juan Orellana\nfound that Simpson had committed over 400 willful violations\nof the GCA. As summarized by the Magistrate Judge, these\nviolations include:\n\n [S]elling or delivering multiple\n firearms without having completed\n Firearm Transaction Records,\n ATF Forms 4473, and without\n Simpson making the required\n entries in his [A&D] Book;\n transferring firearms without\n conducting background checks;\n dealing firearms at the Alexandria\n Sportsman’s Club and in West\n Virginia without obtaining a\n license to do so; selling or\n delivering firearms, firearm\n frames, or firearm receivers in\n seven instances to individuals who\n did not live in Pennsylvania;\n incorrectly identifying in multiple\n\n\n\n\n 5\n\f instances the firearms that had\n been transferred; failing to identify\n and mark 14 firearms that he\n manufactured, and failing to make\n the required records for those\n manufactured firearms; failing to\n record the disposition of five\n firearms to other licensees; failing\n to record the record of disposition\n of 30 firearms to non-licensees;\n failing on over 70 occasions to\n record required information in his\n A&D Book; failing in\n approximately 200 instances to\n record information on ATF Forms\n 4473; failing to appropriately sign\n and date ATF Form 4473 in dozens\n of cases to indicate that he did not\n have reasonable cause to believe\n that a transferee was disqualified\n from receiving a firearm; and\n failing to submit an Annual\n Firearms Manufacturing and\n Exportation Report (ATF Form\n 5300.11) in 2012 and 2013.\n\n(App. I 7-8; see also App. II 137-98). As such, the ATF issued\nfinal revocation notices to Simpson.\n\n Simpson then filed a petition for judicial review and\nmoved for an emergency stay of the revocation of his FFLs.\nThe District Court denied his motion, finding that Simpson was\nunlikely to “succe[ed] on the merits, given the numerosity and\ntypes of violations,” and because the court was not “persuaded\n\n\n\n\n 6\n\fby [Simpson’s] contention that he was inadequately trained by\n[the ATF].” (App. 9). The case was then referred to a\nMagistrate Judge for pretrial management. Upon completion\nof discovery, the parties filed cross-motions for summary\njudgment.\n\n Addressing the cross-motions in a Report and\nRecommendation, the Magistrate Judge concluded that the\nATF was authorized to revoke Simpson’s FFLs because he had\nwillfully committed over 400 violations of the GCA. (App. I\n33-34). The District Court adopted the report and\nrecommendation in its entirety, and thus granted summary\njudgment for the ATF and affirmed its revocation of Simpson’s\nFFLs. Simpson’s timely appeal followed.\n\n\n\n II.\n\n The District Court had jurisdiction to review the ATF’s\nrevocation decision under 18 U.S.C. § 923(f), 5 U.S.C. § 702,\nand 28 U.S.C. § 1331. We have appellate jurisdiction pursuant\nto 28 U.S.C. § 1291. We exercise de novo review over the\nDistrict Court’s grant of summary judgment. See, e.g., Kelly\nv. Borough of Carlisle, 622 F.3d 248, 253 (3d Cir. 2010). A\ngrant of summary judgment is warranted “if the movant shows\nthat there is no genuine dispute as to any material fact and the\nmovant is entitled to judgment as a matter of law.” Fed. R.\nCiv. P. 56(a). Further, an administrative record “enjoys a\npresumption of veracity” at summary judgment. Am. Arms\nInt’l v. Herbert, 563 F.3d 78, 86 n.12 (4th Cir. 2009) (citation\nomitted).\n\n\n\n\n 7\n\f III.\n\n Under the GCA, the ATF may revoke an FFL if the\nlicense holder willfully violated any provision of the GCA or\nany rule or regulation prescribed under the GCA. 18 U.S.C.\n§ 923(e); see also 27 C.F.R. § 478.73. “A single willful\nviolation [of the GCA] authorizes the ATF to revoke the\nviolator’s FFL, regardless of how severe . . . .” Fairmont Cash\nMgmt., L.L.C. v. James, 858 F.3d 356, 362 (5th Cir. 2017).\nThus, in the GCA context, our review of the District Court’s\ngrant of summary judgment requires us to determine whether\nthere was no genuine dispute as to any material fact\nestablishing even one willful violation of the GCA. See Am.\nArms, 563 F.3d at 86 (noting that “a single uncontested\nviolation suffices to uphold” summary judgment for the ATF\n(citing Armalite, Inc. v. Lambert, 544 F.3d 644, 649 (6th Cir.\n2008))).\n\n Eight other Courts of Appeals have held that a violation\nof the GCA is willful where the licensee knew of his legal\nobligation and purposefully disregarded or was plainly\nindifferent to the requirements. See Borchardt Rifle, 684 F.3d\nat 1042; Fairmont Cash Mgmt., 858 F.3d at 362; Armalite, 544\nF.3d at 647; RSM, Inc. v. Herbert, 466 F.3d 316, 317 (4th Cir.\n2006); Article II Gun Shop, Inc. v. Gonzales, 441 F.3d 492, 497\n(7th Cir. 2006); Willingham Sports, Inc. v. ATF, 415 F.3d 1274,\n1277 (11th Cir. 2005); Perri v. ATF, 637 F.2d 1332, 1336 (9th\nCir. 1981); Lewin v. Blumenthal, 590 F.2d 268, 269 (8th Cir.\n1979). We find this definition of willfulness to be appropriate.\nIndeed, this standard mirrors the willfulness standard we have\napplied in the parallel context of ATF revocations of fireworks\nand explosives licenses for violations of federal explosives\nlaws. See Vineland Fireworks Co. v. ATF, 544 F.3d 509, 517–\n19 (upholding the ATF’s interpretation of willful because it\n\n\n\n\n 8\n\fwas reasonable).1 In Vineland, we upheld that willfulness\n“do[es] not require a bad purpose,” or an intent to disobey the\nlaw, but rather willfulness can be established by a mere\n“violation of the regulations with knowledge of their\nrequirements.” Id. Moreover, both parties in this case agree\nwith this willfulness standard. Accordingly, we now join our\nsister circuits in holding that a violation of the GCA is willful\nwhere the licensee: (1) knew of his legal obligation under the\nGCA, and (2) either purposefully disregarded or was plainly\nindifferent to GCA requirements.\n\n Here, Simpson has been charged with willfully\nviolating the GCA over 400 times. He contends that he did not\nfully understand his obligations and that any violations he\ncommitted were not willful, but due to mistake or ignorance.\nWe disagree, as the record indicates that Simpson was well\napprised of his duties under the GCA but continually violated\nGCA recordkeeping, manufacturing, and sales requirements.\n\n\n\n 1\n In Vineland, we deferred to the ATF’s interpretation\nof willfulness under federal explosives law because we found\nit reasonable. See Vineland, 544 F.3d at 518 n.17. Our review\nof explosives licensing decisions is governed only by 5 U.S.C.\n§ 706, so we apply Chevron deference to reasonable agency\ndecisions. See 18 U.S.C. § 843(e)(2); see also Chevron,\nU.S.A., Inc. v. Nat. Res. Def. Council, Inc., 467 U.S. 837\n(1984). In contrast, the GCA explicitly tasks courts with\nconducting de novo review of ATF licensing denials or\nrevocations. See 18 U.S.C. § 923(f)(3). As such, we review\ndistrict court decisions regarding ATF firearms licensing de\nnovo. See, e.g., Willingham Sports, 415 F.3d at 1275-76.\n\n\n\n\n 9\n\f A.\n\n The record shows that Simpson was informed of his\nobligations as an FFL licensee. For example, Simpson met\nwith ATF officials three times about his FFLs and, at the\nconclusion of each meeting, he signed a form acknowledging\nthat he discussed various regulatory topics with the ATF. In\naddition, Simpson attended an ATF seminar for FFL holders\nwhere he learned more about his obligations under the GCA.\n\n The record also demonstrates that Simpson often\ncomplied with GCA requirements. On numerous occasions,\nSimpson lawfully sold firearms and fully completed the A&D\nrecordkeeping required under the GCA. Also, he applied to\nrelocate his FFL, demonstrating that he knew that he was only\nallowed to sell firearms from his approved FFL location. His\nfull compliance with GCA requirements in some instances\nbelies his assertion that he did not understand those\nrequirements.\n\n Further, some of Simpson’s actions illustrate that he\nunderstood the GCA regulatory scheme quite well. For\nexample, he sometimes transferred firearms from his FFL\ninventory to his personal collection, thereby taking advantage\nof a statutory loophole that allowed him to later sell the\nfirearms at gun shows without conducting background checks.\nSuch action is inconsistent with that of a person who does not\nunderstand the GCA regulatory scheme. Accordingly, we find\nthat no reasonable fact-finder could disagree that Simpson\nknew and understood his GCA obligations as an FFL licensee.\n\n\n\n\n 10\n\f B.\n\n In this case, the ATF has alleged that Simpson was\nplainly indifferent to the GCA’s requirements. We must\ntherefore determine what constitutes plain indifference under\nthe willfulness standard we have adopted.\n\n Plain indifference is demonstrated by “a lack of concern\nfor [GCA] regulations. . . .” Am. Arms Int’l, 563 F.3d at 87. A\nlack of concern may be shown by circumstantial evidence—\nsuch as repeated violations or a large quantity of violations.\nSee, e.g., Borchardt Rifle, 684 F.3d at 1043–44; Am. Arms\nInt’l, 563 F.3d at 87; On Target Sporting Goods, Inc. v. Att’y\nGen., 472 F.3d 572, 575 (8th Cir. 2007); RSM, Inc., 466 F.3d\nat 322; Willingham Sports, 415 F.3d at 1277.\n\n The ATF charged Simpson with willfully violating a\nlong list of separate provisions of the GCA under his\nmanufacturer’s FFL, including, inter alia:\n\n (a) selling firearms without completing Form 4473s;\n (b) selling or delivering firearms without recording the\n disposition in his A&D book;\n (c) transferring firearms without conducting\n background checks;\n (d) dealing firearms outside of his FFL premises;\n (e) selling or delivering firearms to non-Pennsylvania\n residents;\n (f) transferring firearms and misidentifying\n corresponding A&D entries;\n (g) failing to identify and mark manufactured firearms;\n (h) failing to record the manufacture of firearms in his\n A&D book;\n\n\n\n\n 11\n\f (i) failing to record dispositions of firearms to FFL\n holders and non-licensees;\n (j) failing to complete all fields of Form 4473s; and\n (k) failing to sign and date Form 4473s.\n\n(See App. I 8). Additionally, the ATF charged Simpson with\nwillfully violating another series of provisions of the GCA\nunder his dealer’s FFL. These include, inter alia:\n\n (a) selling firearms without completing Form 4473s;\n (b) selling or delivering firearms without recording the\n disposition in his A&D book;\n (c) transferring firearms without conducting\n background checks;\n (d) selling firearms in West Virginia;\n (e) selling or delivering firearms to non-Pennsylvania\n residents\n (f) purchasing firearms without recording the purchases\n in his A&D book;\n (g) failing to complete all fields of Form 4473s; and\n (h) failing to sign and date Form 4473s.\n\nId.\n\n Simpson contends that all of these violations either were\nmere mistakes or were due to his “fundamental\nmisunderstanding as to the importance” of GCA recordkeeping\nrequirements. (Appellant’s Br. 35). However, in view of the\nfact that Simpson received training on his obligations and\nexplicitly acknowledged that he understood his GCA\nobligations, the sheer number and continuing nature of the\nviolations clearly demonstrate Simpson’s plain indifference to\nthe GCA’s requirements.\n\n\n\n\n 12\n\f While there is no dispute that Simpson violated the\nGCA on numerous occasions, there is also evidence of other\nfirearms transactions in which Simpson fully complied with\nGCA requirements by completing, signing, and dating Form\n4473s, recording the dispositions in his A&D book, and\nconducting background checks. This inconsistent conduct\nsuggests both that Simpson knew of his obligations and was\nindifferent to complying with them. Moreover, there is\nevidence of blatant GCA violations. For example, Simpson\nroutinely transferred receivers to out-of-state residents—in\nclear violation of the GCA—but falsely recorded the transfers\nas rifle sales in his A&D book, making these transactions\nappear lawful. Such behavior is indicative of Simpson’s lack\nof concern for his GCA obligations as an FFL holder.\n\n In sum, the record sufficiently shows that Simpson had\nknowledge of his FFL obligations, yet acted plainly\nindifferently to them, thus willfully violating the GCA.\nAccordingly, we find that the ATF was authorized to revoke\nSimpson’s FFLs.\n\n\n\n IV.\n\n For the foregoing reasons we will affirm the District\nCourt’s grant of summary judgment in favor of the ATF,\naffirming its revocation of Simpson’s FFLs.\n\n\n\n\n 13\n[END_CASE]", "role": "user" } ]
4,578,609
CHIAO FANG KU, AKA Chiao Fang Ronan, AKA Anna Ronan, Petitioner v. ATTORNEY GENERAL UNITED STATES OF AMERICA, Respondent
Chiao Ku v. Attorney General United States
2019-01-03
17-3001
U.S. Court of Appeals for the Third Circuit
{"judges": "Jordan, Vanaskie, Nygaard", "parties": "", "opinions": [{"author": "VANASKIE, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-3001\n _____________\n\n CHIAO FANG KU,\n AKA Chiao Fang Ronan, AKA Anna Ronan,\n Petitioner\n v.\n\nATTORNEY GENERAL UNITED STATES OF AMERICA,\n Respondent\n _____________\n\n On Petition for Review of an Order of the\n Board of Immigration Appeals\n (Agency No. A077-160-352)\n Immigration Judge: Walter A. Durling\n ______________\n\n Argued September 12, 2018\n ______________\n\n Before: JORDAN, VANASKIE, and NYGAARD, Circuit\n Judges\n\n\n The Honorable Judge Vanaskie transmitted the opinion to the Clerk for\nfiling prior to retiring from the bench on January 1, 2019. Due to the\nintervening holiday, the opinion has been entered on the docket by the\nClerk this day.\n\f (Opinion Filed: January 3, 2019)\n\n\nThomas M. Griffin [Argued]\nSurin & Griffin\n718 Arch Street\nSuite 701N\nPhiladelphia, PA 19106\n Counsel for Petitioner\n\nChad A. Readler, Acting Assistant Attorney General\nNancy E. Friedman, Senior Litigation Counsel\nJustin R. Markel, Senior Litigation Counsel\nGregory A. Pennington, Jr. [Argued]\nUnited States Department of Justice\nOffice of Immigration Litigation\nCivil Division\nP.O. Box 878\nBen Franklin Station\nWashington, DC 20044\n Counsel for Respondent\n\n ________________\n\n OPINION\n ________________\n\n\nVANASKIE, Circuit Judge.\n\n Seeking to remain in this country, Chiao Fang Ku\npetitions for review of a final order of removal issued by the\nBoard of Immigration Appeals (“BIA” or “Board”). The\nBoard determined that Ku had committed an aggravated felony\n\n\n\n\n 2\n\funder 8 U.S.C. § 1101(a)(43)(M)(i) because her prior\nconviction for wire fraud constituted an offense involving\nfraud or deceit in which the loss to the victims exceeded\n$10,000. The Board also found that Ku’s wire fraud conviction\nconstituted a “crime involving moral turpitude” under 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I) such that, without a waiver, she is\nineligible for an adjustment of status. Although the\nImmigration Judge (“IJ”) granted Ku a waiver of\ninadmissibility under 8 U.S.C. § 1182(h)(1)(B) based on the\nextreme hardship that her deportation would cause her U.S.\nCitizen children, the Board reversed that decision. Ku\nchallenges each of the Board’s decisions.\n\n In Nijhawan v. Holder, 557 U.S. 29 (2009), the Court\nheld that determination of whether a fraud offense involved\nloss to the victims of $10,000 or more requires a circumstance-\nspecific approach, allowing the immigration court to review\nboth the charging document and sentencing-related materials\nto determine the loss amount attributable to the offense. On\nthe facts of this case, we find that the undisputed loss to the\nvictims of well over $10,000 was sufficiently tethered to Ku’s\nwire fraud conviction such that the conviction qualifies as an\naggravated felony. Furthermore, we find no error in the\nBoard’s determination that wire fraud constitutes a crime of\nmoral turpitude. Lastly, regarding the waiver of admissibility,\nwe do not have jurisdiction to review the discretionary denial\nof a waiver under § 212(h) of the INA. Accordingly, we will\ndeny in part and dismiss in part Ku’s petition for review.\n\n I.\n\n Ku is a native and citizen of Taiwan. She was admitted\nto the United States in 1997 and gained status as a lawful\npermanent resident in 2002. In 2014, Ku was charged with a\n\n\n\n\n 3\n\fsingle count of wire fraud, in violation of 18 U.S.C. § 1343.\nKu waived her right to an indictment and was charged by\ninformation only. The Information alleged that Ku was tasked\nwith managing the finances of her in-laws, E.R. and M.R, and\nthat she was provided access to her in-laws’ bank accounts in\nconnection with this role. The Information further alleged that,\nbetween May 2008 and July 2013, Ku defrauded her in-laws\nby using her access to their accounts to take money from them\nfor her personal use. In particular, it alleged that Ku: (1)\ntransferred funds from her in-laws’ accounts to her own\naccounts; (2) withdrew funds from her in-laws’ accounts as\ncash; (3) made payments from her in-laws’ accounts to pay off\nher personal credit cards; (4) wrote and cashed checks payable\nto herself by forging her mother-in-law’s signature; and (5)\nfraudulently applied for and obtained credit cards in her\nmother-in-law’s name and used them for her own purposes.\nThe Information alleged that, in total, Ku stole more than\n$950,000 from her in-laws.\n\n These allegations were incorporated by reference into\nthe sole count of the Information, which alleged that, on or\nabout November 7, 2011, Ku,\n\n having devised and intending to devise a\n scheme and artifice to defraud and to obtain\n money and property by means of materially\n false and fraudulent pretenses,\n representations, and promises, did cause\n writings, signs, signals, pictures, and sounds\n to be transmitted by means of wire\n communications in interstate commerce for\n the purpose of executing such scheme and\n artifice, to wit: executing an online payment\n from M.R.’s Sovereign Bank account, ending\n\n\n\n\n 4\n\f in 8497, to the defendant’s Chase credit card\n account, ending in 6567, in the amount of\n $2,290.53.\n\n(App. 590). The Information further contained forfeiture\nallegations, which directed that, upon conviction of the sole\ncount of the Information, Ku “forfeit to the United States . . .\nany property, real or personal, that constitutes, or is derived\nfrom, proceeds traceable to the commission of the offense,\nincluding but not limited to at least $950,000 in United States\ncurrency.” (App. 591).\n\n Ku pleaded guilty, pursuant to a plea agreement,1 to the\nsingle count of the Information. In her sentencing\nmemorandum, Ku, through counsel, acknowledged that she\nwas “now subject to automatic deportation as a result of her\nconviction in this case.” (App. 740). Ku was ultimately\nsentenced to a term of 18 months’ imprisonment, followed by\none year of supervised release. The judgment includes a total\nloss determination of $954,515.71 and orders restitution in that\namount. (App. 582).\n\n After Ku completed her sentence, she was served with\na Notice to Appear and placed in removal proceedings. The\nNotice to Appear charged Ku with being removable under\n§ 237(a)(2)(A)(iii) of the Immigration and Nationality Act\n(“INA” or the “Act”), 8 U.S.C. § 1227(a)(2)(A)(iii), as an\nindividual convicted of an aggravated felony as defined in 8\nU.S.C. § 1101(a)(43)(M)(i). The Immigration Judge\nconcluded that Ku was removable as charged because the\n\n\n 1\n The plea agreement is not part of the administrative\nrecord before us, nor was it in the record before the IJ or BIA.\n\n\n\n\n 5\n\frecord of conviction substantiated a finding that the wire fraud\ninvolved a loss of more than $10,000.\n\n In order to avoid deportation, Ku sought to re-adjust her\nstatus based on her U.S. Citizen husband.2 The Immigration\nJudge granted Ku’s application for a waiver of inadmissibility\nunder § 212(h)(1)(B) of the Act, 8 U.S.C. § 1182(h)(1)(B),\nbased on the extreme hardship that her deportation would cause\nher U.S. Citizen children, and granted Ku’s adjustment of\nstatus pursuant to § 245(a) of the INA, 8 U.S.C. § 1255(a).\n\n On appeal, the Board affirmed that the Government\ndemonstrated by clear and convincing evidence that Ku was\nremovable as an aggravated felon as defined at\n§ 1101(a)(43)(M)(i) in that her offense involved fraud or deceit\nin which the loss to the victims exceeded $10,000. In doing so,\nthe Board noted that the Information alleged that Ku stole more\nthan $950,000 in funds belonging to her in-laws, and that this\nallegation was incorporated by reference into the count to\nwhich Ku pleaded guilty. It also observed that the Information\nalso contained a forfeiture allegation stating that, upon\nconviction, Ku would forfeit over $950,000 in currency.\nFinally, the Board considered relevant that the Judgment of\nConviction found a total loss of over $950,000 and ordered\nrestitution in that amount.\n\n The Board further concluded that Ku’s conviction was\nfor a crime involving moral turpitude, making her inadmissible\nunder § 212(a)(2)(A)(i)(I) of the INA, 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I), such that she required a § 212(h) waiver\n\n 2\n Ku's present husband is not the man to whom she was\npreviously married and whose parents are the elderly in-laws\nshe defrauded.\n\n\n\n\n 6\n\fin order to adjust her status. See 8 U.S.C. § 1255(a) (providing\nfor adjustment of status of certain aliens to that of an alien\nlawfully admitted for permanent residence); see also 8 U.S.C.\n§ 1182(h)(1)(B) (providing for waiver of inadmissibility at the\ndiscretion of the Attorney General). Although it acknowledged\nthe hardship posed to her family, the Board ultimately found\nthat, given the severity of her crime, Ku did not merit a\n§ 212(h) waiver. It accordingly vacated the decision of the IJ\nand denied Ku’s applications for a § 212(h) waiver and for\nadjustment of status. Ku timely filed a petition for review.\n\n II.\n\n Although we have jurisdiction to review final orders of\nremoval under 8 U.S.C. § 1252(a),3 “no court shall have\n\n 3\n We have taken a broad view of what constitutes a\n“final order of removal” under § 1252. Higgs v. Att’y Gen.,\n655 F.3d 333, 337–38 (3d Cir. 2011). “[A]n order is final for\njurisdictional purposes when a removability determination has\nbeen made that is no longer appealable to the BIA, regardless\n[of] whether a formal order of removal has been entered.” Id.\n(quoting Yusupov v. Att’y Gen., 518 F.3d 185, 195 (3d Cir.\n2008)); see also Shehu v. Att’y Gen., 482 F.3d 652, 656 (3d\nCir. 2007) (“[D]enial of a . . . petition for asylum, withholding\nof removal, and relief under the [Convention Against Torture]\nconstitutes ‘a final order of removal’ within the meaning of\n[§ 1252], [because] the alien is entitled to no further process\nbefore deportation.”). Here, although the Board did not\nexplicitly order Ku removed to Taiwan, it found her removable\nand denied her application for adjustment of status, her only\npetition for relief. (App. 5). Furthermore, the Board sustained\nDHS’s appeal, which requested that Ku be ordered removed to\nTaiwan. Accordingly, for the purposes of this appeal, we\n\n\n\n\n 7\n\fjurisdiction to review any final order of removal against an\nalien who is removable by reason of having committed [an\naggravated felony].” 8 U.S.C. § 1252(a)(2)(C). “We do,\nhowever, have jurisdiction to examine ‘constitutional claims or\nquestions of law.’” Fan Wang v. Att’y Gen., 898 F.3d 341, 343\n(3d Cir. 2018) (quoting Catwell v. Att’y Gen., 623 F.3d 199,\n205 (3d Cir. 2010); 8 U.S.C. § 1252(a)(2)(D)). Therefore, we\nhave authority to take up the issue, applying plenary review, of\nwhether Ku’s conviction qualifies as an aggravated felony\nbecause it is “a purely legal question, and one that governs our\nown jurisdiction.” Id. (quoting Valansi v. Ashcroft, 278 F.3d\n203, 207 (3d Cir. 2002)). We also review de novo the legal\nquestion of what elements of a federal criminal statute\nimplicate moral turpitude, while affording Chevron deference\nto the Board’s definition of “moral turpitude.” Knapik v.\nAshcroft, 384 F.3d 84, 88 (3d Cir. 2004).\n\n III.\n\n On appeal, Ku challenges all three aspects of the BIA’s\norder. First, she contends that the BIA incorrectly determined\nthat her wire-fraud conviction involved a loss of more than\n$10,000 by relying on evidence that was not sufficiently\ntethered to the sole count of conviction.4 Second, Ku argues\n\n\nconsider the Board’s order to be a final order of removal. The\nGovernment’s motion to remand this case to the Board for\nissuance of an order directing that Ku be removed to Taiwan\nand to allow the IJ to make additional findings on removability\nwill be denied as moot.\n 4\n We note that Ku does not challenge—and did not\nchallenge before the IJ or the Board—that her wire fraud\n\n\n\n\n 8\n\fthat the Board erred in finding that her wire-fraud conviction\nwas for a crime involving moral turpitude because the statute\nof conviction does not require a showing of intent. Third, Ku\nasserts that the BIA applied the incorrect legal standard in\nreversing the IJ’s grant of a discretionary waiver of\ninadmissibility. We reject all three of Ku’s challenges and\ntherefore deny the petition for review.\n\n A.\n\n Section 237(a)(2)(A)(iii) of the INA, as amended,\nprovides that “[a]ny alien who is convicted of an aggravated\nfelony at any time after admission is deportable.” 8 U.S.C.\n§ 1227(a)(2)(A)(iii). The Act defines “aggravated felony,” in\nrelevant part, as an offense that “involves fraud or deceit in\nwhich the loss to the victim or victims exceeds $10,000.” 8\nU.S.C. § 1101(a)(43)(M)(i).\n\n In Nijhawan v. Holder, the Supreme Court addressed\nthe issue of whether the $10,000 threshold of the aggravated\nfelony statute “refers to an element of a fraud statute or to the\nfactual circumstances surrounding commission of the crime on\na specific occasion.” 557 U.S. at 33. The Court adopted the\nlatter interpretation, characterizing the review as examining\n“the specific way in which an offender committed the crime on\na specific occasion.” Id. at 34. The Court distinguished the\n“circumstance-specific approach” to be used in determining\nwhether a crime “involves fraud or deceit in which the loss to\nthe victim or victims exceeds $10,000” from the “categorical\napproach” used in determining whether a crime is a “violent\nfelony” under the Armed Career Criminal Act (“ACCA”), 18\n\nconviction “involves fraud or deceit” under 8 U.S.C.\n§ 1101(a)(43)(M).\n\n\n\n\n 9\n\fU.S.C. § 924(e). Id. at 34–40. It also rejected the use of the\nso-called “modified categorical approach” employed in some\ncontexts, which would limit an IJ’s consideration to charging\ndocuments, jury instructions, special jury findings, or some\nequivalent judge-made findings and—in the case of a guilty\nplea—to the written plea documents or plea colloquy. Id. at\n41. While the Supreme Court acknowledged that “the statute\nforesees the use of fundamentally fair procedures,” it rejected\nthe argument that fairness requires such evidentiary\nlimitations. Id. Accordingly, it found “nothing unfair” about\nthe IJ’s reliance upon the defendant’s stipulation and the\ndistrict court’s restitution order to determine that the crime at\nissue was an “aggravated felony” under § 1101(a)(43)(M)(i).\nId. at 42–43.\n\n Since Nijhawan, we have consistently applied the\ncircumstance-specific approach to determine the amount of\nloss in “aggravated felony” cases. See, e.g., Kaplun v. Att’y\nGen., 602 F.3d 260, 265–66 (3d Cir. 2010); Doe v. Att’y Gen.,\n659 F.3d 266, 274–76 (3d Cir. 2011). Most recently, we\naddressed the issue in Fan Wang, in which we reviewed “not\nonly those documents that may be considered in a modified\ncategorical approach (the indictment, plea agreement, and\njudgment),” but also others, including “the presentence\ninvestigation report and any sentencing-related material.” 898\nF.3d at 348–49 (citations and internal quotation marks\nomitted). Relying on Nijhawan, we reasoned that\nconsideration of such materials “is appropriate so long as the\npetitioner has been given a ‘fair opportunity’ to challenge the\nGovernment’s claim.” Id. at 349 (quoting Nijhawan, 557 U.S.\nat 41). Accordingly, we determined that the Board did not go\nbeyond the bounds of proper review by examining the record—\nincluding the sole count of the superseding information, the\n\n\n\n\n 10\n\fplea colloquy, the presentence investigation report, the “total\nloss” specified in the judgment, and the restitution order—to\ndetermine whether the petitioner’s prior conviction was an\n“aggravated felony.” Id. at 349–50. In determining the proper\namount of loss in that case, we were persuaded by the\nGovernment’s argument that the loss amount listed in the\njudgment and restitution order was “undeniably tethered” to\nthe conduct for which the petitioner was convicted. Id. at 351.\n\n We consider the loss to the victims in this case—as\nevidenced by the Information, Judgment, and Restitution\nOrder—to be sufficiently tethered to the count of conviction\nsuch that Ku’s conviction was an aggravated felony.\nParagraphs 1 through 10 of the Information allege that Ku stole\nmore than $950,000 in funds belonging to her in-laws, and\nthese paragraphs were incorporated by reference into the count\nto which Ku pleaded guilty. Furthermore, the forfeiture\nallegation contained in the Information states that, upon\nconviction, Ku would forfeit the “proceeds traceable to the\ncommission of the offense, including but not limited to at least\n$950,000 in United States currency.” (App. 591). Finally, the\nJudgment of Conviction indicates a loss of $954,515.71 and\norders restitution in that amount. Each of these documents is\nreviewable under the circumstance-specific approach laid out\nby the Supreme Court in Nijhawan. Together, they provide\nclear and convincing evidence that Ku’s offense involved a\nloss of over $10,000. Nonetheless, we briefly addresses Ku’s\narguments to the contrary, all of which lack merit.\n\n 1.\n\n First, Ku contends that the circumstance-specific\napproach described in Nijhawan does not apply in her case\nbecause the single count of the Information made clear that it\n\n\n\n\n 11\n\fwas for the specified amount of $2,290.53. She urges us to\nread Nijhawan to have kept intact the modified categorical\napproach for cases in which the charging document contains a\nclear indication of the loss amount. Under the modified\ncategorical approach, she contends, the Board was correct in\nreviewing the Information but, because the count of conviction\ncontains a loss amount of $2,290.53, the Board should have\nstopped there.\n\n Contrary to Ku’s assertion, Nijhawan does not stand for\nthe proposition that, when the count of conviction contains a\nloss amount, immigration officials must look no further. The\nSupreme Court explicitly rejected the use of the modified\ncategorical approach in determining whether a prior conviction\nis an aggravated felony under § 1101(a)(43)(M)(i). Nijhawan,\n557 U.S. at 41–42; see also Kaplun, 602 F.3d at 265–66\n(interpreting Nijhawan). Rather, it determined that the\ncircumstance-specific approach is required because the\naggravated felony statute “refers to the particular\ncircumstances in which an offender committed a (more broadly\ndefined) fraud or deceit crime on a particular occasion,” and\nnot to an element of the offense. Nijhawan, 557 U.S. at 32.\nNoting that the Government in immigration proceedings is\nheld only to a “clear and convincing” burden of proof, and not\n“beyond a reasonable doubt,” the Supreme Court found\n“nothing unfair about [an IJ] rel[ying] upon earlier sentencing-\nrelated material”—in that case a sentencing stipulation and\nrestitution order. Id. at 42–43. It also noted that “the sole\npurpose of the aggravated felony inquiry is to ascertain the\nnature of a prior conviction; it is not an invitation to relitigate\nthe conviction itself.” Id. (internal quotation marks omitted).\n\n Nothing in Nijhawan suggests that the circumstance-\nspecific approach applies in some cases but not others, or that\n\n\n\n\n 12\n\fthe documents reviewable under that approach vary from case\nto case. Furthermore, we have consistently interpreted\nNijhawan as allowing an IJ, in determining the loss amount, to\nlook beyond the charging document to sentencing-related\nmaterials. See Kaplun, 602 F.3d at 265–66; Fan Wang, 898\nF.3d at 348–49. Ku has not persuaded us that our reading is\nincorrect.\n\n 2.\n\n Second, Ku contends that, because her conviction was\nfor “a single act of a $2,290.53 on-line transfer,” the losses she\ncaused through other acts and transactions are not sufficiently\n“tethered” to the count of conviction for purposes of the\naggravated felony statute. (Petitioner’s Br. at 27). In doing so,\nKu asks us to read the Information as charging her in Count\nOne with a “scheme and artifice to defraud” her in-laws of\n$2,290.53, and not as charging her with one instance of wire\nfraud that was part of a broader “scheme and artifice to\ndefraud” her in-laws of over $950,000. However, such an\ninterpretation is inconsistent with the language of the\nInformation. In Count One, the Government “re-alleges and\nincorporates by reference” the first eight paragraphs, which\nallege that, over five years, Ku defrauded her in-laws of more\nthan $950,000 by transferring funds from their accounts to her\nown accounts, withdrawing funds as cash, making payments to\ncredit card companies for charges she incurred, and writing and\ncashing checks payable to herself. (App. 588–90). The explicit\nincorporation of those paragraphs into the count to which Ku\npleaded guilty supports an interpretation of the count itself as\ndescribing Ku’s “scheme and artifice to defraud” her in-laws\nof more than $950,000.\n\n\n\n\n 13\n\f We are similarly unpersuaded by Ku’s contention that,\nbecause Paragraphs 1 through 8 of the Information describe\nconduct that does not necessarily amount to wire fraud, such\nconduct cannot count toward the total loss resulting from her\nconviction. It is incontrovertible that the “scheme and artifice\nto defraud” charged in Count One of the Information\nencompassed the whole course of Ku’s unlawful conduct,\nincluding the one incident in which Ku committed wire fraud\nin the amount of $2,390.53, and which resulted in a total loss\nof over $950,000. In short, because Ku pleaded guilty to\ncommitting wire fraud as part of a scheme to defraud her in-\nlaws of more than $950,000, the total loss amount is, to use our\nlanguage from Fan Wang, “undeniably tethered” to her wire\nfraud conviction.\n\n 3.\n\n Finally, Ku contends that the single-count Information\nto which she pleaded guilty is part of the “justice package”\nworked out between her and the Government and urges the\nCourt to defer to that agreement. (Petitioner’s Br. at 35). In\ndoing so, Ku relies on our opinion in Alaka v. Attorney\nGeneral, 456 F.3d 88 (3d Cir. 2006). However, the facts of\nthis case make it distinguishable from Alaka.\n\n In Alaka—which we decided prior to Nijhawan5—we\nheld that the IJ erred by considering the amount of intended\n\n\n 5\n Because Alaka was decided prior to the Supreme\nCourt’s decision in Nijhawan, its application of the modified\ncategorical approach to the aggravated-felony analysis does\nnot affect our decision. However, to the extent that Alaka\nstands for the proposition that an IJ may not consider dismissed\n\n\n\n\n 14\n\floss for all of the charges against the petitioner rather than the\nsingle count for which she was convicted. Alaka, 456 F.3d at\n106. The petitioner had been indicted on three counts for\nconduct involving fraudulent checks, but was convicted of only\none count, for which the actual loss was $4,716.68. Id. at 92.\nThe sentencing court nonetheless held that the petitioner’s\nconduct was part of a “common scheme or plan,” and therefore\nfound the total intended loss to be nearly $50,000. Id. It\nordered her to pay $4,716.68 in restitution. Id. In subsequent\nimmigration proceedings, the IJ concluded that the petitioner\nhad been convicted of an aggravated felony on the ground that\nthe intended loss was more than $10,000. Id. at 105, n.27. On\nappeal, we determined that, while the IJ properly considered\nthe factual findings of the sentencing report in determining\nwhether the offense was an aggravated felony, the loss amount\ntied to the dismissed charges was not properly considered as\npart of the aggravated-felony analysis. Id. at 106–08. In doing\nso, we noted that “the plain and unambiguous language of the\nstatute . . . predicates removal on a convicted offense resulting\nin losses greater than $10,000,” thereby foreclosing inclusion\nof losses stemming from unconvicted offenses. Id. 106–07\n(citations omitted). Furthermore, we considered that, because\nit is “the plea agreement that establishes the offense for which\nthe defendant will be convicted, it is to that agreement, and not\nthe indictment or the sentence, that we look in determining the\nintended loss.” Id. at 107. The petitioner “unmistakably pled\nguilty to one count, and the plea agreement plainly documented\nthat loss at less than $10,000.” Id. at 108 (citations and\nalterations omitted). Because the plea agreement “spell[ed] it\nout for us in black and white,” we concluded that the plea\n\n\ncharges when calculating the loss attributable to the conviction,\nit remains good law.\n\n\n\n\n 15\n\fagreement alone established the loss amount, and “not . . . the\nloss charged in the indictment, tabulated for restitution\npurposes, or calculated for sentencing.” Id. (citations omitted).\n\n Here, in stark contrast to the petitioner in Alaka, the\nrecord before us contains no plea agreement, and certainly not\none which explicitly spells out the loss amount to which Ku\npleaded guilty. Instead, Ku urges us to find that, based on the\nfact that the Government could have charged her with a much\nlonger list of crimes but did not, the loss amount as indicated\nin Count One was part of an explicit bargain between her and\nthe Government. However, this argument is based on pure\nconjecture. Absent a clear and unmistakable indication of loss\nin a written plea agreement, we are left with only the\nInformation, Judgment, and Restitution Order to determine the\nloss attributable to Ku’s conviction. As explained above, these\ndocuments, taken together, provide clear and convincing\nevidence that the loss amount attributable to Ku’s wire fraud\nconviction exceeded $10,000, and Ku has provided no plea\nagreement or any other document to the contrary.6\n\n 6\n The sentencing court in Alaka calculated the total loss\namount based on the “common scheme or plan,” which, it\nconsidered, included both the count of conviction and the\ndismissed counts, and we considered the IJ’s reliance on that\ncalculation to be in error in light of the plea agreement. 456\nF.3d at 106. But this does not help Ku. As explained above,\nthe wire fraud count to which Ku pleaded guilty was based in\npart on her “scheme and artifice to defraud” her in-laws of over\n$950,000. (App. 590). Unlike the sentencing court in Alaka,\nthe sentencing court in this case did not base its loss calculation\non any acts that were not explicitly incorporated into the count\nof conviction.\n\n\n\n\n 16\n\f Ku’s argument that this Court should respect the\n“justice package” between her and the Government also\ntouches on the Supreme Court’s landmark holdings in Padilla\nv. Kentucky, 559 U.S. 356 (2010), and Descamps v. United\nStates, 570 U.S. 254 (2013), both of which, she argues, counsel\ntoward respecting agreements between criminal defendants\nand the Government with respect to the collateral\nconsequences of a conviction. But this line of argument merely\nhighlights another critical shortcoming of Ku’s case. To the\nextent Ku argues that the Information was designed\nspecifically to avoid immigration consequences, there is no\nevidence in the record to support such a finding. Indeed, Ku’s\nattorney indicated in her sentencing memorandum that Ku “is\nnow subject to automatic deportation as a result of her\nconviction in this case.” (App. 740). This statement, while not\nconclusive, certainly undermines any assertion that the “justice\npackage” referred to by Ku was designed to avoid an\naggravated felony conviction. Indeed, absent any other\nevidence in the record to the contrary, the sentencing\nmemorandum supports a finding that, at the time of her guilty\nplea, Ku understood that she was pleading guilty to an\naggravated felony.\n\n B.\n\n Having concluded that the Board did not err in finding\nthat Ku was convicted of an aggravated felony, we turn to the\nquestion of whether Ku’s conviction constituted a “crime\ninvolving moral turpitude” under the INA. Ku argues that wire\nfraud is not a “crime involving moral turpitude” under 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I) because it does not include as an element\nthe specific intent to defraud. This is incorrect.\n\n\n\n\n 17\n\f The statute provides that a person is guilty of wire fraud\nif, “having devised or intending to devise any scheme or\nartifice to defraud,” that person “transmits or causes to be\ntransmitted by means of wire, radio, or television\ncommunication in interstate or foreign commerce, any\nwritings, signs, signals, pictures, or sounds for the purpose of\nexecuting such scheme or artifice.” 18 U.S.C. § 1343. Courts\nhave long treated fraud crimes as “involving moral turpitude.”\nJordan v. De George, 341 U.S. 223, 232 (1951) (“[T]he\ndecided cases make it plain that crimes in which fraud was an\ningredient have always been regarded as involving moral\nturpitude.”); Singh v. Att’y Gen., 807 F.3d 547, 550 (3d Cir.\n2015) (“Crimes . . . involving allegations of dishonesty or fraud\nfall well within the recognized definition of ‘crimes involving\nmoral turpitude.’”). Furthermore, we have also consistently\nread the wire fraud statute as containing the element of specific\nintent. See, e.g., United States v. Andrews, 681 F.3d 509, 518\n(3d Cir. 2012) (“To prove wire fraud, the Government must\nestablish (1) the defendant’s knowing and willful participation\nin a scheme or artifice to defraud, (2) with the specific intent to\ndefraud, and (3) the use of . . . interstate wire communications\nin furtherance of the scheme.”) (internal quotation marks\nomitted) (emphasis added).\n\n Seeking to persuade us to revisit these tenets, Ku asks\nus to read the statutory terms “having devised” and “intending\nto devise” as disjunctive means of committing wire fraud, the\nlatter containing the mens rea of intent, and the former\neschewing any mens rea at all. But the language of the statute\ndoes not lend itself to such an interpretation. The specific\nintent requirement is contained in the latter part of the statute—\n“for the purpose of executing [a] scheme or artifice [to\ndefraud]”—and must be proved regardless of whether the\n\n\n\n\n 18\n\fperson made the transmission after “having devised” or while\n“intending to devise” the scheme to defraud. 18 U.S.C. § 1343.\nPlainly read, the language Ku seizes on, “having devised or\nintending to devise,” refers not to the requisite mens rea but to\nthe temporal relationship between the formation of the fraud\nscheme and the transmission itself. Either way, the person\nmust have made the transmission for the purpose of executing\nthe fraud scheme in order to be convicted.\n\n Ku’s statutory interpretation argument holds no weight.\nAccordingly, we see no need to revisit the long-held tenet that\nfraud crimes—including wire fraud—are crimes involving\nmoral turpitude under the INA.\n\n C.\n\n Finally, Ku asks us to find that the Board committed\nerror in its reversal of the IJ’s finding that she was eligible for\na discretionary waiver of inadmissibility based on the hardship\nher deportation would cause her U.S. citizen children.\nHowever, we lack jurisdiction over the Board’s decision on\nthis point.\n\n The INA provides that an alien is inadmissible to the\nUnited States if she has been convicted of a crime involving\nmoral turpitude. 8 U.S.C. § 1182(a)(2)(A)(i)(I). The Act also\nprovides, however, that the Attorney General may waive\ninadmissibility to allow an applicant to obtain adjustment of\nstatus under § 1182(h), “if the alien is a spouse, parent, or child\nof a United States citizen . . . and can show that denial of\nadmission would cause extreme hardship to the citizen . . . .”\nDe Leon–Reynoso v. Ashcroft, 293 F.3d 633, 637 (3d Cir.\n2002). The authority to waive one or more grounds of\ninadmissibility is vested solely in the Attorney General and “no\n\n\n\n\n 19\n\fcourt shall have jurisdiction to review” a decision to deny such\na request. 8 U.S.C. § 1252(a)(2)(B)(i).\n\n We may, however, review “constitutional claims or\nquestions of law raised upon a petition for review . . . .” Id. at\n§ 1252(a)(2)(D). Our jurisdiction in that respect is “narrowly\ncircumscribed” in that it is limited to “colorable claims or\nquestions of law.” Cospito v. Att’y Gen., 539 F.3d 166, 170 (3d\nCir. 2008) (per curiam) (quotation marks and citation omitted).\nWhile “[t]he question of our jurisdiction over a colorable legal\nclaim does not turn on whether that claim is ultimately\nmeritorious . . . , a party may not dress up a claim with legal\nclothing to invoke this Court's jurisdiction.” Pareja v. Att’y\nGen., 615 F.3d 180, 187 (3d Cir. 2010) (citations omitted).\n\n Ku argues that we have jurisdiction to consider her\npetition for review on the waiver issue because it presents a\nquestion of law, namely whether the Board applied the proper\nlegal standard in making the discretionary determination. But\nKu’s argument boils down to her contention that the Board\nfailed to consider certain equities relevant to the hardship\ndetermination. As we have consistently held, “arguments such\nas that an Immigration Judge or the BIA incorrectly weighed\nevidence, failed to consider evidence or improperly weighed\nequitable factors are not questions of law under\n§ 1252(a)(2)(D).” Jarbough v. Att’y Gen., 483 F.3d 184, 189\n(3d Cir. 2007). Because the substance of Ku’s petition for\nreview amounts to contesting the weight the Board should have\ngiven to the positive equities of her case, we do not have\njurisdiction over it and will dismiss in part that aspect of the\npetition.\n\n IV.\n\n\n\n\n 20\n\f For the foregoing reasons, we will deny in part and\ndismiss in part Ku's petition for review, and we will deny as\nmoot the Government's motion to remand.\n\n\n\n\n 21", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355862/", "author_raw": "VANASKIE, Circuit Judge."}]}
JORDAN
VANASKIE
NYGAARD
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578609/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: CHIAO FANG KU, AKA Chiao Fang Ronan, AKA Anna Ronan, Petitioner v. ATTORNEY GENERAL UNITED STATES OF AMERICA, Respondent\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-03\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-3001\n _____________\n\n CHIAO FANG KU,\n AKA Chiao Fang Ronan, AKA Anna Ronan,\n Petitioner\n v.\n\nATTORNEY GENERAL UNITED STATES OF AMERICA,\n Respondent\n _____________\n\n On Petition for Review of an Order of the\n Board of Immigration Appeals\n (Agency No. A077-160-352)\n Immigration Judge: Walter A. Durling\n ______________\n\n Argued September 12, 2018\n ______________\n\n Before: JORDAN, VANASKIE, and NYGAARD, Circuit\n Judges\n\n\n The Honorable Judge Vanaskie transmitted the opinion to the Clerk for\nfiling prior to retiring from the bench on January 1, 2019. Due to the\nintervening holiday, the opinion has been entered on the docket by the\nClerk this day.\n\f (Opinion Filed: January 3, 2019)\n\n\nThomas M. Griffin [Argued]\nSurin & Griffin\n718 Arch Street\nSuite 701N\nPhiladelphia, PA 19106\n Counsel for Petitioner\n\nChad A. Readler, Acting Assistant Attorney General\nNancy E. Friedman, Senior Litigation Counsel\nJustin R. Markel, Senior Litigation Counsel\nGregory A. Pennington, Jr. [Argued]\nUnited States Department of Justice\nOffice of Immigration Litigation\nCivil Division\nP.O. Box 878\nBen Franklin Station\nWashington, DC 20044\n Counsel for Respondent\n\n ________________\n\n OPINION\n ________________\n\n\nVANASKIE, Circuit Judge.\n\n Seeking to remain in this country, Chiao Fang Ku\npetitions for review of a final order of removal issued by the\nBoard of Immigration Appeals (“BIA” or “Board”). The\nBoard determined that Ku had committed an aggravated felony\n\n\n\n\n 2\n\funder 8 U.S.C. § 1101(a)(43)(M)(i) because her prior\nconviction for wire fraud constituted an offense involving\nfraud or deceit in which the loss to the victims exceeded\n$10,000. The Board also found that Ku’s wire fraud conviction\nconstituted a “crime involving moral turpitude” under 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I) such that, without a waiver, she is\nineligible for an adjustment of status. Although the\nImmigration Judge (“IJ”) granted Ku a waiver of\ninadmissibility under 8 U.S.C. § 1182(h)(1)(B) based on the\nextreme hardship that her deportation would cause her U.S.\nCitizen children, the Board reversed that decision. Ku\nchallenges each of the Board’s decisions.\n\n In Nijhawan v. Holder, 557 U.S. 29 (2009), the Court\nheld that determination of whether a fraud offense involved\nloss to the victims of $10,000 or more requires a circumstance-\nspecific approach, allowing the immigration court to review\nboth the charging document and sentencing-related materials\nto determine the loss amount attributable to the offense. On\nthe facts of this case, we find that the undisputed loss to the\nvictims of well over $10,000 was sufficiently tethered to Ku’s\nwire fraud conviction such that the conviction qualifies as an\naggravated felony. Furthermore, we find no error in the\nBoard’s determination that wire fraud constitutes a crime of\nmoral turpitude. Lastly, regarding the waiver of admissibility,\nwe do not have jurisdiction to review the discretionary denial\nof a waiver under § 212(h) of the INA. Accordingly, we will\ndeny in part and dismiss in part Ku’s petition for review.\n\n I.\n\n Ku is a native and citizen of Taiwan. She was admitted\nto the United States in 1997 and gained status as a lawful\npermanent resident in 2002. In 2014, Ku was charged with a\n\n\n\n\n 3\n\fsingle count of wire fraud, in violation of 18 U.S.C. § 1343.\nKu waived her right to an indictment and was charged by\ninformation only. The Information alleged that Ku was tasked\nwith managing the finances of her in-laws, E.R. and M.R, and\nthat she was provided access to her in-laws’ bank accounts in\nconnection with this role. The Information further alleged that,\nbetween May 2008 and July 2013, Ku defrauded her in-laws\nby using her access to their accounts to take money from them\nfor her personal use. In particular, it alleged that Ku: (1)\ntransferred funds from her in-laws’ accounts to her own\naccounts; (2) withdrew funds from her in-laws’ accounts as\ncash; (3) made payments from her in-laws’ accounts to pay off\nher personal credit cards; (4) wrote and cashed checks payable\nto herself by forging her mother-in-law’s signature; and (5)\nfraudulently applied for and obtained credit cards in her\nmother-in-law’s name and used them for her own purposes.\nThe Information alleged that, in total, Ku stole more than\n$950,000 from her in-laws.\n\n These allegations were incorporated by reference into\nthe sole count of the Information, which alleged that, on or\nabout November 7, 2011, Ku,\n\n having devised and intending to devise a\n scheme and artifice to defraud and to obtain\n money and property by means of materially\n false and fraudulent pretenses,\n representations, and promises, did cause\n writings, signs, signals, pictures, and sounds\n to be transmitted by means of wire\n communications in interstate commerce for\n the purpose of executing such scheme and\n artifice, to wit: executing an online payment\n from M.R.’s Sovereign Bank account, ending\n\n\n\n\n 4\n\f in 8497, to the defendant’s Chase credit card\n account, ending in 6567, in the amount of\n $2,290.53.\n\n(App. 590). The Information further contained forfeiture\nallegations, which directed that, upon conviction of the sole\ncount of the Information, Ku “forfeit to the United States . . .\nany property, real or personal, that constitutes, or is derived\nfrom, proceeds traceable to the commission of the offense,\nincluding but not limited to at least $950,000 in United States\ncurrency.” (App. 591).\n\n Ku pleaded guilty, pursuant to a plea agreement,1 to the\nsingle count of the Information. In her sentencing\nmemorandum, Ku, through counsel, acknowledged that she\nwas “now subject to automatic deportation as a result of her\nconviction in this case.” (App. 740). Ku was ultimately\nsentenced to a term of 18 months’ imprisonment, followed by\none year of supervised release. The judgment includes a total\nloss determination of $954,515.71 and orders restitution in that\namount. (App. 582).\n\n After Ku completed her sentence, she was served with\na Notice to Appear and placed in removal proceedings. The\nNotice to Appear charged Ku with being removable under\n§ 237(a)(2)(A)(iii) of the Immigration and Nationality Act\n(“INA” or the “Act”), 8 U.S.C. § 1227(a)(2)(A)(iii), as an\nindividual convicted of an aggravated felony as defined in 8\nU.S.C. § 1101(a)(43)(M)(i). The Immigration Judge\nconcluded that Ku was removable as charged because the\n\n\n 1\n The plea agreement is not part of the administrative\nrecord before us, nor was it in the record before the IJ or BIA.\n\n\n\n\n 5\n\frecord of conviction substantiated a finding that the wire fraud\ninvolved a loss of more than $10,000.\n\n In order to avoid deportation, Ku sought to re-adjust her\nstatus based on her U.S. Citizen husband.2 The Immigration\nJudge granted Ku’s application for a waiver of inadmissibility\nunder § 212(h)(1)(B) of the Act, 8 U.S.C. § 1182(h)(1)(B),\nbased on the extreme hardship that her deportation would cause\nher U.S. Citizen children, and granted Ku’s adjustment of\nstatus pursuant to § 245(a) of the INA, 8 U.S.C. § 1255(a).\n\n On appeal, the Board affirmed that the Government\ndemonstrated by clear and convincing evidence that Ku was\nremovable as an aggravated felon as defined at\n§ 1101(a)(43)(M)(i) in that her offense involved fraud or deceit\nin which the loss to the victims exceeded $10,000. In doing so,\nthe Board noted that the Information alleged that Ku stole more\nthan $950,000 in funds belonging to her in-laws, and that this\nallegation was incorporated by reference into the count to\nwhich Ku pleaded guilty. It also observed that the Information\nalso contained a forfeiture allegation stating that, upon\nconviction, Ku would forfeit over $950,000 in currency.\nFinally, the Board considered relevant that the Judgment of\nConviction found a total loss of over $950,000 and ordered\nrestitution in that amount.\n\n The Board further concluded that Ku’s conviction was\nfor a crime involving moral turpitude, making her inadmissible\nunder § 212(a)(2)(A)(i)(I) of the INA, 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I), such that she required a § 212(h) waiver\n\n 2\n Ku's present husband is not the man to whom she was\npreviously married and whose parents are the elderly in-laws\nshe defrauded.\n\n\n\n\n 6\n\fin order to adjust her status. See 8 U.S.C. § 1255(a) (providing\nfor adjustment of status of certain aliens to that of an alien\nlawfully admitted for permanent residence); see also 8 U.S.C.\n§ 1182(h)(1)(B) (providing for waiver of inadmissibility at the\ndiscretion of the Attorney General). Although it acknowledged\nthe hardship posed to her family, the Board ultimately found\nthat, given the severity of her crime, Ku did not merit a\n§ 212(h) waiver. It accordingly vacated the decision of the IJ\nand denied Ku’s applications for a § 212(h) waiver and for\nadjustment of status. Ku timely filed a petition for review.\n\n II.\n\n Although we have jurisdiction to review final orders of\nremoval under 8 U.S.C. § 1252(a),3 “no court shall have\n\n 3\n We have taken a broad view of what constitutes a\n“final order of removal” under § 1252. Higgs v. Att’y Gen.,\n655 F.3d 333, 337–38 (3d Cir. 2011). “[A]n order is final for\njurisdictional purposes when a removability determination has\nbeen made that is no longer appealable to the BIA, regardless\n[of] whether a formal order of removal has been entered.” Id.\n(quoting Yusupov v. Att’y Gen., 518 F.3d 185, 195 (3d Cir.\n2008)); see also Shehu v. Att’y Gen., 482 F.3d 652, 656 (3d\nCir. 2007) (“[D]enial of a . . . petition for asylum, withholding\nof removal, and relief under the [Convention Against Torture]\nconstitutes ‘a final order of removal’ within the meaning of\n[§ 1252], [because] the alien is entitled to no further process\nbefore deportation.”). Here, although the Board did not\nexplicitly order Ku removed to Taiwan, it found her removable\nand denied her application for adjustment of status, her only\npetition for relief. (App. 5). Furthermore, the Board sustained\nDHS’s appeal, which requested that Ku be ordered removed to\nTaiwan. Accordingly, for the purposes of this appeal, we\n\n\n\n\n 7\n\fjurisdiction to review any final order of removal against an\nalien who is removable by reason of having committed [an\naggravated felony].” 8 U.S.C. § 1252(a)(2)(C). “We do,\nhowever, have jurisdiction to examine ‘constitutional claims or\nquestions of law.’” Fan Wang v. Att’y Gen., 898 F.3d 341, 343\n(3d Cir. 2018) (quoting Catwell v. Att’y Gen., 623 F.3d 199,\n205 (3d Cir. 2010); 8 U.S.C. § 1252(a)(2)(D)). Therefore, we\nhave authority to take up the issue, applying plenary review, of\nwhether Ku’s conviction qualifies as an aggravated felony\nbecause it is “a purely legal question, and one that governs our\nown jurisdiction.” Id. (quoting Valansi v. Ashcroft, 278 F.3d\n203, 207 (3d Cir. 2002)). We also review de novo the legal\nquestion of what elements of a federal criminal statute\nimplicate moral turpitude, while affording Chevron deference\nto the Board’s definition of “moral turpitude.” Knapik v.\nAshcroft, 384 F.3d 84, 88 (3d Cir. 2004).\n\n III.\n\n On appeal, Ku challenges all three aspects of the BIA’s\norder. First, she contends that the BIA incorrectly determined\nthat her wire-fraud conviction involved a loss of more than\n$10,000 by relying on evidence that was not sufficiently\ntethered to the sole count of conviction.4 Second, Ku argues\n\n\nconsider the Board’s order to be a final order of removal. The\nGovernment’s motion to remand this case to the Board for\nissuance of an order directing that Ku be removed to Taiwan\nand to allow the IJ to make additional findings on removability\nwill be denied as moot.\n 4\n We note that Ku does not challenge—and did not\nchallenge before the IJ or the Board—that her wire fraud\n\n\n\n\n 8\n\fthat the Board erred in finding that her wire-fraud conviction\nwas for a crime involving moral turpitude because the statute\nof conviction does not require a showing of intent. Third, Ku\nasserts that the BIA applied the incorrect legal standard in\nreversing the IJ’s grant of a discretionary waiver of\ninadmissibility. We reject all three of Ku’s challenges and\ntherefore deny the petition for review.\n\n A.\n\n Section 237(a)(2)(A)(iii) of the INA, as amended,\nprovides that “[a]ny alien who is convicted of an aggravated\nfelony at any time after admission is deportable.” 8 U.S.C.\n§ 1227(a)(2)(A)(iii). The Act defines “aggravated felony,” in\nrelevant part, as an offense that “involves fraud or deceit in\nwhich the loss to the victim or victims exceeds $10,000.” 8\nU.S.C. § 1101(a)(43)(M)(i).\n\n In Nijhawan v. Holder, the Supreme Court addressed\nthe issue of whether the $10,000 threshold of the aggravated\nfelony statute “refers to an element of a fraud statute or to the\nfactual circumstances surrounding commission of the crime on\na specific occasion.” 557 U.S. at 33. The Court adopted the\nlatter interpretation, characterizing the review as examining\n“the specific way in which an offender committed the crime on\na specific occasion.” Id. at 34. The Court distinguished the\n“circumstance-specific approach” to be used in determining\nwhether a crime “involves fraud or deceit in which the loss to\nthe victim or victims exceeds $10,000” from the “categorical\napproach” used in determining whether a crime is a “violent\nfelony” under the Armed Career Criminal Act (“ACCA”), 18\n\nconviction “involves fraud or deceit” under 8 U.S.C.\n§ 1101(a)(43)(M).\n\n\n\n\n 9\n\fU.S.C. § 924(e). Id. at 34–40. It also rejected the use of the\nso-called “modified categorical approach” employed in some\ncontexts, which would limit an IJ’s consideration to charging\ndocuments, jury instructions, special jury findings, or some\nequivalent judge-made findings and—in the case of a guilty\nplea—to the written plea documents or plea colloquy. Id. at\n41. While the Supreme Court acknowledged that “the statute\nforesees the use of fundamentally fair procedures,” it rejected\nthe argument that fairness requires such evidentiary\nlimitations. Id. Accordingly, it found “nothing unfair” about\nthe IJ’s reliance upon the defendant’s stipulation and the\ndistrict court’s restitution order to determine that the crime at\nissue was an “aggravated felony” under § 1101(a)(43)(M)(i).\nId. at 42–43.\n\n Since Nijhawan, we have consistently applied the\ncircumstance-specific approach to determine the amount of\nloss in “aggravated felony” cases. See, e.g., Kaplun v. Att’y\nGen., 602 F.3d 260, 265–66 (3d Cir. 2010); Doe v. Att’y Gen.,\n659 F.3d 266, 274–76 (3d Cir. 2011). Most recently, we\naddressed the issue in Fan Wang, in which we reviewed “not\nonly those documents that may be considered in a modified\ncategorical approach (the indictment, plea agreement, and\njudgment),” but also others, including “the presentence\ninvestigation report and any sentencing-related material.” 898\nF.3d at 348–49 (citations and internal quotation marks\nomitted). Relying on Nijhawan, we reasoned that\nconsideration of such materials “is appropriate so long as the\npetitioner has been given a ‘fair opportunity’ to challenge the\nGovernment’s claim.” Id. at 349 (quoting Nijhawan, 557 U.S.\nat 41). Accordingly, we determined that the Board did not go\nbeyond the bounds of proper review by examining the record—\nincluding the sole count of the superseding information, the\n\n\n\n\n 10\n\fplea colloquy, the presentence investigation report, the “total\nloss” specified in the judgment, and the restitution order—to\ndetermine whether the petitioner’s prior conviction was an\n“aggravated felony.” Id. at 349–50. In determining the proper\namount of loss in that case, we were persuaded by the\nGovernment’s argument that the loss amount listed in the\njudgment and restitution order was “undeniably tethered” to\nthe conduct for which the petitioner was convicted. Id. at 351.\n\n We consider the loss to the victims in this case—as\nevidenced by the Information, Judgment, and Restitution\nOrder—to be sufficiently tethered to the count of conviction\nsuch that Ku’s conviction was an aggravated felony.\nParagraphs 1 through 10 of the Information allege that Ku stole\nmore than $950,000 in funds belonging to her in-laws, and\nthese paragraphs were incorporated by reference into the count\nto which Ku pleaded guilty. Furthermore, the forfeiture\nallegation contained in the Information states that, upon\nconviction, Ku would forfeit the “proceeds traceable to the\ncommission of the offense, including but not limited to at least\n$950,000 in United States currency.” (App. 591). Finally, the\nJudgment of Conviction indicates a loss of $954,515.71 and\norders restitution in that amount. Each of these documents is\nreviewable under the circumstance-specific approach laid out\nby the Supreme Court in Nijhawan. Together, they provide\nclear and convincing evidence that Ku’s offense involved a\nloss of over $10,000. Nonetheless, we briefly addresses Ku’s\narguments to the contrary, all of which lack merit.\n\n 1.\n\n First, Ku contends that the circumstance-specific\napproach described in Nijhawan does not apply in her case\nbecause the single count of the Information made clear that it\n\n\n\n\n 11\n\fwas for the specified amount of $2,290.53. She urges us to\nread Nijhawan to have kept intact the modified categorical\napproach for cases in which the charging document contains a\nclear indication of the loss amount. Under the modified\ncategorical approach, she contends, the Board was correct in\nreviewing the Information but, because the count of conviction\ncontains a loss amount of $2,290.53, the Board should have\nstopped there.\n\n Contrary to Ku’s assertion, Nijhawan does not stand for\nthe proposition that, when the count of conviction contains a\nloss amount, immigration officials must look no further. The\nSupreme Court explicitly rejected the use of the modified\ncategorical approach in determining whether a prior conviction\nis an aggravated felony under § 1101(a)(43)(M)(i). Nijhawan,\n557 U.S. at 41–42; see also Kaplun, 602 F.3d at 265–66\n(interpreting Nijhawan). Rather, it determined that the\ncircumstance-specific approach is required because the\naggravated felony statute “refers to the particular\ncircumstances in which an offender committed a (more broadly\ndefined) fraud or deceit crime on a particular occasion,” and\nnot to an element of the offense. Nijhawan, 557 U.S. at 32.\nNoting that the Government in immigration proceedings is\nheld only to a “clear and convincing” burden of proof, and not\n“beyond a reasonable doubt,” the Supreme Court found\n“nothing unfair about [an IJ] rel[ying] upon earlier sentencing-\nrelated material”—in that case a sentencing stipulation and\nrestitution order. Id. at 42–43. It also noted that “the sole\npurpose of the aggravated felony inquiry is to ascertain the\nnature of a prior conviction; it is not an invitation to relitigate\nthe conviction itself.” Id. (internal quotation marks omitted).\n\n Nothing in Nijhawan suggests that the circumstance-\nspecific approach applies in some cases but not others, or that\n\n\n\n\n 12\n\fthe documents reviewable under that approach vary from case\nto case. Furthermore, we have consistently interpreted\nNijhawan as allowing an IJ, in determining the loss amount, to\nlook beyond the charging document to sentencing-related\nmaterials. See Kaplun, 602 F.3d at 265–66; Fan Wang, 898\nF.3d at 348–49. Ku has not persuaded us that our reading is\nincorrect.\n\n 2.\n\n Second, Ku contends that, because her conviction was\nfor “a single act of a $2,290.53 on-line transfer,” the losses she\ncaused through other acts and transactions are not sufficiently\n“tethered” to the count of conviction for purposes of the\naggravated felony statute. (Petitioner’s Br. at 27). In doing so,\nKu asks us to read the Information as charging her in Count\nOne with a “scheme and artifice to defraud” her in-laws of\n$2,290.53, and not as charging her with one instance of wire\nfraud that was part of a broader “scheme and artifice to\ndefraud” her in-laws of over $950,000. However, such an\ninterpretation is inconsistent with the language of the\nInformation. In Count One, the Government “re-alleges and\nincorporates by reference” the first eight paragraphs, which\nallege that, over five years, Ku defrauded her in-laws of more\nthan $950,000 by transferring funds from their accounts to her\nown accounts, withdrawing funds as cash, making payments to\ncredit card companies for charges she incurred, and writing and\ncashing checks payable to herself. (App. 588–90). The explicit\nincorporation of those paragraphs into the count to which Ku\npleaded guilty supports an interpretation of the count itself as\ndescribing Ku’s “scheme and artifice to defraud” her in-laws\nof more than $950,000.\n\n\n\n\n 13\n\f We are similarly unpersuaded by Ku’s contention that,\nbecause Paragraphs 1 through 8 of the Information describe\nconduct that does not necessarily amount to wire fraud, such\nconduct cannot count toward the total loss resulting from her\nconviction. It is incontrovertible that the “scheme and artifice\nto defraud” charged in Count One of the Information\nencompassed the whole course of Ku’s unlawful conduct,\nincluding the one incident in which Ku committed wire fraud\nin the amount of $2,390.53, and which resulted in a total loss\nof over $950,000. In short, because Ku pleaded guilty to\ncommitting wire fraud as part of a scheme to defraud her in-\nlaws of more than $950,000, the total loss amount is, to use our\nlanguage from Fan Wang, “undeniably tethered” to her wire\nfraud conviction.\n\n 3.\n\n Finally, Ku contends that the single-count Information\nto which she pleaded guilty is part of the “justice package”\nworked out between her and the Government and urges the\nCourt to defer to that agreement. (Petitioner’s Br. at 35). In\ndoing so, Ku relies on our opinion in Alaka v. Attorney\nGeneral, 456 F.3d 88 (3d Cir. 2006). However, the facts of\nthis case make it distinguishable from Alaka.\n\n In Alaka—which we decided prior to Nijhawan5—we\nheld that the IJ erred by considering the amount of intended\n\n\n 5\n Because Alaka was decided prior to the Supreme\nCourt’s decision in Nijhawan, its application of the modified\ncategorical approach to the aggravated-felony analysis does\nnot affect our decision. However, to the extent that Alaka\nstands for the proposition that an IJ may not consider dismissed\n\n\n\n\n 14\n\floss for all of the charges against the petitioner rather than the\nsingle count for which she was convicted. Alaka, 456 F.3d at\n106. The petitioner had been indicted on three counts for\nconduct involving fraudulent checks, but was convicted of only\none count, for which the actual loss was $4,716.68. Id. at 92.\nThe sentencing court nonetheless held that the petitioner’s\nconduct was part of a “common scheme or plan,” and therefore\nfound the total intended loss to be nearly $50,000. Id. It\nordered her to pay $4,716.68 in restitution. Id. In subsequent\nimmigration proceedings, the IJ concluded that the petitioner\nhad been convicted of an aggravated felony on the ground that\nthe intended loss was more than $10,000. Id. at 105, n.27. On\nappeal, we determined that, while the IJ properly considered\nthe factual findings of the sentencing report in determining\nwhether the offense was an aggravated felony, the loss amount\ntied to the dismissed charges was not properly considered as\npart of the aggravated-felony analysis. Id. at 106–08. In doing\nso, we noted that “the plain and unambiguous language of the\nstatute . . . predicates removal on a convicted offense resulting\nin losses greater than $10,000,” thereby foreclosing inclusion\nof losses stemming from unconvicted offenses. Id. 106–07\n(citations omitted). Furthermore, we considered that, because\nit is “the plea agreement that establishes the offense for which\nthe defendant will be convicted, it is to that agreement, and not\nthe indictment or the sentence, that we look in determining the\nintended loss.” Id. at 107. The petitioner “unmistakably pled\nguilty to one count, and the plea agreement plainly documented\nthat loss at less than $10,000.” Id. at 108 (citations and\nalterations omitted). Because the plea agreement “spell[ed] it\nout for us in black and white,” we concluded that the plea\n\n\ncharges when calculating the loss attributable to the conviction,\nit remains good law.\n\n\n\n\n 15\n\fagreement alone established the loss amount, and “not . . . the\nloss charged in the indictment, tabulated for restitution\npurposes, or calculated for sentencing.” Id. (citations omitted).\n\n Here, in stark contrast to the petitioner in Alaka, the\nrecord before us contains no plea agreement, and certainly not\none which explicitly spells out the loss amount to which Ku\npleaded guilty. Instead, Ku urges us to find that, based on the\nfact that the Government could have charged her with a much\nlonger list of crimes but did not, the loss amount as indicated\nin Count One was part of an explicit bargain between her and\nthe Government. However, this argument is based on pure\nconjecture. Absent a clear and unmistakable indication of loss\nin a written plea agreement, we are left with only the\nInformation, Judgment, and Restitution Order to determine the\nloss attributable to Ku’s conviction. As explained above, these\ndocuments, taken together, provide clear and convincing\nevidence that the loss amount attributable to Ku’s wire fraud\nconviction exceeded $10,000, and Ku has provided no plea\nagreement or any other document to the contrary.6\n\n 6\n The sentencing court in Alaka calculated the total loss\namount based on the “common scheme or plan,” which, it\nconsidered, included both the count of conviction and the\ndismissed counts, and we considered the IJ’s reliance on that\ncalculation to be in error in light of the plea agreement. 456\nF.3d at 106. But this does not help Ku. As explained above,\nthe wire fraud count to which Ku pleaded guilty was based in\npart on her “scheme and artifice to defraud” her in-laws of over\n$950,000. (App. 590). Unlike the sentencing court in Alaka,\nthe sentencing court in this case did not base its loss calculation\non any acts that were not explicitly incorporated into the count\nof conviction.\n\n\n\n\n 16\n\f Ku’s argument that this Court should respect the\n“justice package” between her and the Government also\ntouches on the Supreme Court’s landmark holdings in Padilla\nv. Kentucky, 559 U.S. 356 (2010), and Descamps v. United\nStates, 570 U.S. 254 (2013), both of which, she argues, counsel\ntoward respecting agreements between criminal defendants\nand the Government with respect to the collateral\nconsequences of a conviction. But this line of argument merely\nhighlights another critical shortcoming of Ku’s case. To the\nextent Ku argues that the Information was designed\nspecifically to avoid immigration consequences, there is no\nevidence in the record to support such a finding. Indeed, Ku’s\nattorney indicated in her sentencing memorandum that Ku “is\nnow subject to automatic deportation as a result of her\nconviction in this case.” (App. 740). This statement, while not\nconclusive, certainly undermines any assertion that the “justice\npackage” referred to by Ku was designed to avoid an\naggravated felony conviction. Indeed, absent any other\nevidence in the record to the contrary, the sentencing\nmemorandum supports a finding that, at the time of her guilty\nplea, Ku understood that she was pleading guilty to an\naggravated felony.\n\n B.\n\n Having concluded that the Board did not err in finding\nthat Ku was convicted of an aggravated felony, we turn to the\nquestion of whether Ku’s conviction constituted a “crime\ninvolving moral turpitude” under the INA. Ku argues that wire\nfraud is not a “crime involving moral turpitude” under 8 U.S.C.\n§ 1182(a)(2)(A)(i)(I) because it does not include as an element\nthe specific intent to defraud. This is incorrect.\n\n\n\n\n 17\n\f The statute provides that a person is guilty of wire fraud\nif, “having devised or intending to devise any scheme or\nartifice to defraud,” that person “transmits or causes to be\ntransmitted by means of wire, radio, or television\ncommunication in interstate or foreign commerce, any\nwritings, signs, signals, pictures, or sounds for the purpose of\nexecuting such scheme or artifice.” 18 U.S.C. § 1343. Courts\nhave long treated fraud crimes as “involving moral turpitude.”\nJordan v. De George, 341 U.S. 223, 232 (1951) (“[T]he\ndecided cases make it plain that crimes in which fraud was an\ningredient have always been regarded as involving moral\nturpitude.”); Singh v. Att’y Gen., 807 F.3d 547, 550 (3d Cir.\n2015) (“Crimes . . . involving allegations of dishonesty or fraud\nfall well within the recognized definition of ‘crimes involving\nmoral turpitude.’”). Furthermore, we have also consistently\nread the wire fraud statute as containing the element of specific\nintent. See, e.g., United States v. Andrews, 681 F.3d 509, 518\n(3d Cir. 2012) (“To prove wire fraud, the Government must\nestablish (1) the defendant’s knowing and willful participation\nin a scheme or artifice to defraud, (2) with the specific intent to\ndefraud, and (3) the use of . . . interstate wire communications\nin furtherance of the scheme.”) (internal quotation marks\nomitted) (emphasis added).\n\n Seeking to persuade us to revisit these tenets, Ku asks\nus to read the statutory terms “having devised” and “intending\nto devise” as disjunctive means of committing wire fraud, the\nlatter containing the mens rea of intent, and the former\neschewing any mens rea at all. But the language of the statute\ndoes not lend itself to such an interpretation. The specific\nintent requirement is contained in the latter part of the statute—\n“for the purpose of executing [a] scheme or artifice [to\ndefraud]”—and must be proved regardless of whether the\n\n\n\n\n 18\n\fperson made the transmission after “having devised” or while\n“intending to devise” the scheme to defraud. 18 U.S.C. § 1343.\nPlainly read, the language Ku seizes on, “having devised or\nintending to devise,” refers not to the requisite mens rea but to\nthe temporal relationship between the formation of the fraud\nscheme and the transmission itself. Either way, the person\nmust have made the transmission for the purpose of executing\nthe fraud scheme in order to be convicted.\n\n Ku’s statutory interpretation argument holds no weight.\nAccordingly, we see no need to revisit the long-held tenet that\nfraud crimes—including wire fraud—are crimes involving\nmoral turpitude under the INA.\n\n C.\n\n Finally, Ku asks us to find that the Board committed\nerror in its reversal of the IJ’s finding that she was eligible for\na discretionary waiver of inadmissibility based on the hardship\nher deportation would cause her U.S. citizen children.\nHowever, we lack jurisdiction over the Board’s decision on\nthis point.\n\n The INA provides that an alien is inadmissible to the\nUnited States if she has been convicted of a crime involving\nmoral turpitude. 8 U.S.C. § 1182(a)(2)(A)(i)(I). The Act also\nprovides, however, that the Attorney General may waive\ninadmissibility to allow an applicant to obtain adjustment of\nstatus under § 1182(h), “if the alien is a spouse, parent, or child\nof a United States citizen . . . and can show that denial of\nadmission would cause extreme hardship to the citizen . . . .”\nDe Leon–Reynoso v. Ashcroft, 293 F.3d 633, 637 (3d Cir.\n2002). The authority to waive one or more grounds of\ninadmissibility is vested solely in the Attorney General and “no\n\n\n\n\n 19\n\fcourt shall have jurisdiction to review” a decision to deny such\na request. 8 U.S.C. § 1252(a)(2)(B)(i).\n\n We may, however, review “constitutional claims or\nquestions of law raised upon a petition for review . . . .” Id. at\n§ 1252(a)(2)(D). Our jurisdiction in that respect is “narrowly\ncircumscribed” in that it is limited to “colorable claims or\nquestions of law.” Cospito v. Att’y Gen., 539 F.3d 166, 170 (3d\nCir. 2008) (per curiam) (quotation marks and citation omitted).\nWhile “[t]he question of our jurisdiction over a colorable legal\nclaim does not turn on whether that claim is ultimately\nmeritorious . . . , a party may not dress up a claim with legal\nclothing to invoke this Court's jurisdiction.” Pareja v. Att’y\nGen., 615 F.3d 180, 187 (3d Cir. 2010) (citations omitted).\n\n Ku argues that we have jurisdiction to consider her\npetition for review on the waiver issue because it presents a\nquestion of law, namely whether the Board applied the proper\nlegal standard in making the discretionary determination. But\nKu’s argument boils down to her contention that the Board\nfailed to consider certain equities relevant to the hardship\ndetermination. As we have consistently held, “arguments such\nas that an Immigration Judge or the BIA incorrectly weighed\nevidence, failed to consider evidence or improperly weighed\nequitable factors are not questions of law under\n§ 1252(a)(2)(D).” Jarbough v. Att’y Gen., 483 F.3d 184, 189\n(3d Cir. 2007). Because the substance of Ku’s petition for\nreview amounts to contesting the weight the Board should have\ngiven to the positive equities of her case, we do not have\njurisdiction over it and will dismiss in part that aspect of the\npetition.\n\n IV.\n\n\n\n\n 20\n\f For the foregoing reasons, we will deny in part and\ndismiss in part Ku's petition for review, and we will deny as\nmoot the Government's motion to remand.\n\n\n\n\n 21\n[END_CASE]", "role": "user" } ]
4,580,566
T MOBILE NORTHEAST LLC, Appellant v. CITY OF WILMINGTON, DELAWARE ; City of Wilmington Zoning Board of Adjustment
T Mobile Northeast LLC v. City of Wilmington
2019-01-10
18-1831
U.S. Court of Appeals for the Third Circuit
{"judges": "Jordan, Nygaard, Vanaskie", "parties": "", "opinions": [{"author": "JORDAN, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 18-1831\n _____________\n\n T MOBILE NORTHEAST LLC,\n Appellant\n\n v.\n\n CITY OF WILMINGTON, DELAWARE;\nCITY OF WILMINGTON ZONING BOARD OF ADJUSTMENT\n _____________\n\n On Appeal from the United States District Court\n for the District of Delaware\n (D.C. No. 1-16-cv-01108)\n District Judge: Hon. Eduardo C. Robreno\n _______________\n\n Argued\n September 12, 2018\n\nBefore: JORDAN, NYGAARD, and VANASKIE, * Circuit Judge\n (Filed: January 10, 2019)\n\n\n *\n The Honorable Thomas I. Vanaskie retired from the\nCourt on January 1, 2019 after the argument and conference\nin this case, but before the filing of the opinion. This opinion\nis filed by a quorum of the panel pursuant to 28 U.S.C.\n§ 46(d) and Third Circuit I.O.P. Chapter 12.\n\f _______________\n\nThomas S. Thompson [ARGUED]\nDavis Wright Tremaine\n1919 Pennsylvania Avenue, NW\nSte. 800\nWashington, DC 20006\n\nCounsel for Appellant\n\nJoseph Van Eaton [ARGUED]\nBest Best & Krieger\n2000 Pennsylvania Avenue\nSte. 5300\nWashington, DC 20006\n\nCounsel for Appellees\n _______________\n\n OPINION OF THE COURT\n _______________\n\n\nJORDAN, Circuit Judge.\n\n No one likes bad cell phone reception or slow\nstreaming data on their smartphone, but that does not mean\nanyone wants a cellular antenna in their neighborhood, which\nis why there are zoning battles like the one central to this\ncase.\n\n T Mobile Northeast LLC (“T Mobile”), a wireless\ntelecommunications service provider, applied to the Zoning\nBoard of Adjustment (“ZBA”) of the City of Wilmington,\nDelaware for permission to erect an antenna in the City. The\n\n\n\n\n 2\n\fZBA said no. So, relying on a provision of federal law that\nallows a disappointed wireless service provider like T Mobile\nto seek review in a district court “within 30 days after” a\nzoning authority’s “final action,” 47 U.S.C.\n§ 332(c)(7)(B)(v), T Mobile filed suit. After the case had\nproceeded for over a year, however, the District Court\nconcluded that it lacked jurisdiction. The Court reasoned that\nbecause T Mobile filed its complaint before the ZBA released\na written decision confirming an earlier oral rejection of the\nzoning application, the claim was not ripe. And, since\nT Mobile did not supplement its complaint to include the\nZBA’s written decision within 30 days of its issuance, the\nCourt also concluded that relation back could not remedy the\nripeness defect. The District Court thus granted the City’s\nmotion for summary judgment.\n\n T Mobile now appeals. It argues that its complaint\nwas not premature or, in the alternative, that its supplemental\npleading cured any ripeness problem. We agree that the grant\nof summary judgment was improper and, for the reasons that\nfollow, will remand the case for further proceedings\nconsistent with this opinion.\n\nI. BACKGROUND\n\n A. Statutory Framework\n\n This dispute is governed by the Telecommunications\nAct of 1996 (“TCA”), which amended the Federal\nCommunications Act of 1934 and includes provisions on\nmobile phone services. Pub. L. No. 104-104, §§ 1, 704, 110\nStat. 56, 56, 151 (1996); 47 U.S.C. § 332. Passed to\n“encourage the rapid deployment of new telecommunications\n\n\n\n\n 3\n\ftechnologies,” Preamble, 110 Stat. at 56, the TCA provides\nfor expedited review in federal court of a denial of permission\nto build a cell phone antenna, id. § 704, 110 Stat. at 151-52.\nSuch review is a “benefit Congress expressly intended to\nconfer on wireless providers[.]” Nextel W. Corp. v. Unity\nTwp., 282 F.3d 257, 264 (3d Cir. 2002). At the same time,\nthe TCA also serves to preserve local zoning authority. 47\nU.S.C. § 332(c)(7).\n\n At issue here are three key sections of the statute.\nFirst, the TCA mandates that “[a] State or local government\nor instrumentality thereof shall act on any request for\nauthorization to place, construct, or modify personal wireless\nservice facilities within a reasonable period of time after the\nrequest is duly filed[.]” Id. § 332(c)(7)(B)(ii). The Federal\nCommunications Commission (“FCC”) has interpreted\n“reasonable period of time” in that statutory provision to\nmean that zoning authorities have a “shot clock” 1 and must\nact within 90 days of an application to attach an antenna to an\nexisting structure or 150 days of an application where a new\nsupport structure is to be built. Petition for Declaratory\n\n 1\n “Shot clock” is a term borrowed from basketball. In\nthat game, it signifies a time limit to make a shot attempt,\nbeginning once a team has possession of the basketball. See,\ne.g., Nat’s Basketball Ass’n, NBA Rulebook Rule No. 7: Shot\nClock (2018-2019), http://official.nba.com/rule-no-7-24-\nsecond-clock/. If the team has not made a shot attempt, i.e.,\nacted, within the prescribed time limit, it forfeits possession\nof the ball. Id. Here, the permitting authority has exclusive\njurisdiction over an application until it fails to act within a\n“reasonable period of time.” 47 U.S.C. §§ 332(c)(7)(A),\n332(c)(7)(B)(ii).\n\n\n\n\n 4\n\fRuling to Clarify Provisions of Section 332(c)(7)(B), 24 FCC\nRcd. 13994, 14008, 14012 (2009). Second, in what we will\ncall the “review provision” of the statute, the TCA grants\n“[a]ny person adversely affected by any final action or failure\nto act by a State or local government or any instrumentality\nthereof” a right to have that locality’s decision reviewed by\n“commenc[ing] an action” “within 30 days” in district court.\n47 U.S.C. § 332(c)(7)(B)(v). Third, in the statute’s “denial\nprovision,” the TCA states that “[a]ny decision by a State or\nlocal government or instrumentality thereof to deny a request\nto place, construct, or modify personal wireless service\nfacilities shall be in writing and supported by substantial\nevidence contained in a written record.” Id.\n§ 332(c)(7)(B)(iii). Notably, the terms “act,” “final action,”\nand “decision … to deny” are not defined in the TCA.\nFurthermore, the statute does not make clear whether “final\naction” should be read to encompass all decisions to deny,\nincluding oral ones, nor does it address whether there is a\ndifference between an “act” for purposes of the shot clock\nand a “final action” for purposes of judicial review.\n\n B. Factual Background\n\n T Mobile is a telecommunications service provider. It\nsays that it needs to erect a cellular antenna to fill “a\nsignificant gap” in coverage for its customers in Wilmington,\nDelaware, (Opening Br. at 3) presumably where there has\nbeen an increase in phone calls and data usage. T Mobile\nwants to put its antenna on top of a senior living high-rise in\nthe City, but, because a special exception to local zoning laws\nis needed, it first had to go to the ZBA. It filed an initial\napplication and then, on August 25, 2016, a final amended\napplication, seeking the exception.\n\n\n\n\n 5\n\f The ZBA held a hearing on October 26, 2016, to\nconsider T Mobile’s request, some two months after the final\namended application was submitted. During the hearing,\nT Mobile presented evidence of the need for the antenna and\ndiscussed proposals to address aesthetic concerns. The ZBA\nalso received objections from members of the local\ncommunity, some of whom were outspoken in worrying\nabout the effects of radio frequency emissions. At the end of\nthe hearing, the ZBA denied T Mobile’s application in a\nunanimous oral decision.\n\n The Board gave several reasons for the denial. One\nboard member said the ZBA should not encourage the use of\na senior living community rooftop as the base for an antenna\nbecause of the potential adverse effect on the properties in the\nneighborhood. Another board member said there was not\nenough proof of a need for additional coverage to support the\napplication. The Chairman said there was not enough\nevidence that T Mobile needed the antenna and that it did not\nappear to satisfy the zoning code in terms of placement and\nheight restrictions.\n\n The ZBA’s oral decision to deny the application was\nnot put in writing on October 26 or anytime soon thereafter.\nAccording to T Mobile, that fits a “pattern and practice of\n[the ZBA] not issuing a written decision of land use denials\nunless or until the City is sued.” (Opening Br. at 7.) Only\nafter T Mobile had filed its initial complaint in the District\nCourt, and after the City filed its answer, did the ZBA issue\nits written decision and explanation of its reasoning for\ndenying the application.\n\n\n\n\n 6\n\f T Mobile asserts that the denial of its application\nviolates the TCA. Under the statute, such a denial is invalid\nif it has the “effect of prohibiting the provision of personal\nwireless services[,]” 47 U.S.C. § 332(c)(7)(B)(i)(II), or is “on\nthe basis of the environmental effects of radio frequency\nemissions[,]” id. at § 332(c)(7)(B)(iv). T Mobile claims that\nWilmington’s denial was improper on both of those grounds. 2\nBut those assertions go to the merits and are not actually\nbefore us on this appeal. At issue now is whether T Mobile’s\nclaim can be heard at all.\n\n C. Procedural History\n\n Evidently with its eye on the 30-day deadline in the\nTCA’s review provision, T Mobile filed a lawsuit in the\nUnited States District Court for the District of Delaware\nwithin 30 days of the ZBA’s oral decision, challenging that\ndenial. 3 In addition to its claims on the merits, T Mobile’s\ninitial complaint alleged that the City violated procedures\nmandated in the TCA, specifically those in the denial\nprovision, by failing to provide a written decision\n\n 2\n T Mobile also raised a Delaware state law claim.\nThat claim is not at issue here and does not impact\nT Mobile’s claims under federal law.\n 3\n For reasons discussed herein, the 30-day filing\ndeadline was not triggered by the oral decision. See infra pp.\n12-20. If it were, however, T Mobile’s complaint would have\nbeen timely. The oral decision was delivered at the\nOctober 26, 2016 hearing. Suit was filed on November 28,\n2016, but because the thirtieth day from October 26 fell on a\nweekend, the November 28 filing was within the 30-day\nwindow. Fed. R. Civ. P. 6(a)(1).\n\n\n\n\n 7\n\fcontemporaneous with its oral decision and by not supporting\nthe denial with substantial evidence.\n\n The parties entered into a stipulation asking the\nDistrict Court for an expedited case schedule, as provided for\nin the review provision of the TCA. 47 U.S.C.\n§ 332(c)(7)(B)(v). That request was granted. Wilmington\nthen answered the complaint, asserting a number of\naffirmative defenses, including that the complaint was not\nripe because the ZBA had not yet issued a final written\ndecision. Nevertheless, the City did not, at that time, file a\nmotion to dismiss for failure to state a claim or for lack of\njurisdiction. Two days after the City filed its answer, the\nZBA issued a written decision on T Mobile’s application.\nThe parties pressed forward with the suit and prepared a\ndiscovery plan, which specifically mentioned the written\ndecision. T Mobile filed a motion for summary judgment,\nwhich the City met with a cross-motion for summary\njudgment. The City’s motion was styled in the alternative as\na motion to dismiss the complaint as unripe because it was\nfiled prematurely, i.e., before the written decision had been\nissued.\n\n Not until December 21, 2017, nearly a year after the\nZBA issued its written denial, did T Mobile file a motion\nseeking leave to amend or supplement the initial complaint to\nnote the issuance of that written decision. 4 The District Court\n\n 4\n When “[a] claim or defense set out in a pleading [is]\naffected by events that occur after the pleading is filed ….\nRule 15(d) allows a court,” to permit a supplemental\npleading. 3 James Wm. Moore et al., Moore’s Federal\nPractice ¶ 15.30 (3d ed. 2018). Supplemental pleadings\n\n\n\n\n 8\n\fgranted the motion to supplement. Wilmington then\nresponded by moving to dismiss the supplemental complaint\nas untimely because it failed to cure the defect.\n\n Ultimately, the District Court granted Wilmington’s\ncross-motion for summary judgment for want of jurisdiction,\nwithout ruling on the City’s motion to dismiss. The Court\nfirst concluded that the initial complaint was irreparably\nunripe because both the TCA and Delaware law require the\nZBA to issue a written decision before the agency’s action\ncould be considered final, and T Mobile had thus filed its\ninitial complaint too soon. Second, the Court said that the\nsupplemental complaint could not fix the ripeness problem\nbecause it was filed past the 30-day window for seeking\nreview of the ZBA’s final action. Because the Court reached\n\n\n\nunder Rule 15(d) differ from amended pleadings made under\nRule 15(a). First, amended pleadings “relate to matters that\noccurred prior to the filing of the original pleading and\nentirely replace the earlier pleading; [supplemental pleadings]\ndeal with events subsequent to the pleading to be altered and\nrepresent additions to or continuations of the earlier\npleadings.” 6A Charles Alan Wright et al., Federal Practice\n& Procedure § 1504 (3d ed. 2018). Second “certain\namendments may be made as a matter of course within stated\ntime periods, whereas all supplemental pleadings require\nleave of court under Rule 15(d).” Id. “Parties and courts\noccasionally confuse supplemental pleadings with amended\npleadings and mislabeling is common.” Id. Here, T Mobile’s\ncomplaint was filed as an amended complaint but it is\nproperly categorized as a supplemental complaint, and we\nwill refer to it as such herein.\n\n\n\n\n 9\n\fthat determination, it found it unnecessary to conclude\nwhether T Mobile’s supplemental complaint was entitled to\nthe benefit of the relation-back doctrine under Rule 15(c).\n\n This appeal followed.\nII. DISCUSSION 5\n\n T Mobile challenges the District Court’s grant of\nsummary judgment in favor of Wilmington, contending that\nthere is jurisdiction to hear its case. It advances two\nalternative grounds for reversal: that its complaint was ripe\nbecause the ZBA’s oral decision qualifies as a “final action”\nunder the review provision of the TCA, and, in the\nalternative, that the supplemental complaint relates back to\nand cures any ripeness problem with its initial complaint.\nThose arguments in turn raise three questions for determining\nwhether the District Court’s jurisdictional ruling was proper.\nFirst, whether the oral decision of the ZBA was a final action.\nSecond, whether the timing requirement in the TCA’s review\nprovision is jurisdictional. And third, whether an untimely\n\n 5\n The District Court had jurisdiction to consider its\njurisdiction under 28 U.S.C. §§ 1331 and 1367(a), but\ndetermined the complaint contained incurable jurisdictional\ndefects and declined to reach the merits. We have jurisdiction\npursuant to 28 U.S.C. § 1291. We review all the issues\npresented in this case de novo, as they involve only legal\nissues, i.e., interpretation of a federal statute and of a Federal\nRule of Civil Procedure. Giles v. Campbell, 698 F.3d 153,\n155 (3d Cir. 2012); Viera v. Life Ins. Co. of N. Am., 642 F.3d\n407, 413 (3d Cir. 2011); DIRECTV Inc. v. Seijas, 508 F.3d\n123, 125 (3d Cir. 2007).\n\n\n\n\n 10\n\fsupplemental complaint can relate back and cure an unripe\ninitial complaint. Although we disagree with T Mobile that\nan oral decision of the ZBA qualifies as a “final action,” we\nagree that jurisdiction was proper in the District Court\nbecause the timing requirement in the TCA’s review\nprovision is non-jurisdictional, and T Mobile’s supplemental\ncomplaint therefore relates back and cures the ripeness\nproblem with the initial complaint. The District Court should\nthus have reached the merits of the dispute.\n\n A. The Oral Decision Was Not a Final Action of\n the ZBA.\n\n The ripeness of T Mobile’s initial complaint depends\nupon whether the ZBA’s oral decision was a “final action”\nwithin the meaning of the TCA. Consideration of that issue\nuncovers another: whether the TCA requires a locality to\nrender its decision in writing for that decision to qualify as a\nfinal action. The District Court held that, under both federal\nand Delaware law, only a written decision can serve as a final\naction of the ZBA. Because traditional hallmarks of agency\naction and the statutory text and structure of the TCA favor\nthat approach, we agree that only a written decision can serve\nas a locality’s final action when denying an application.\n\n In Delaware Riverkeeper Network v. Secretary\nPennsylvania Department of Environmental Protection,\n(Riverkeeper III), we determined that, when reviewing\nfinality under the Natural Gas Act, “[a]lthough the\ndecisionmaking process we are reviewing is defined by [state]\nlaw, we nevertheless apply a federal finality standard to\ndetermine whether Congress has made the results of that\nprocess reviewable[.]” 903 F.3d 65, 72 (3d Cir. 2018). The\n\n\n\n\n 11\n\fsame reasoning holds true here, since, for the TCA just as for\nthe Natural Gas Act, “the finality requirement itself, along\nwith the presumption that Congress intended us to apply it,\nare creatures of federal, not state, law.” Id. at 71.\n\n Under federal law, not all agency determinations are\nfinal actions. Bacon v. Sullivan, 969 F.2d 1517, 1519 (3d Cir.\n1992). Final agency actions bear certain “traditional\nhallmarks” that demonstrate “[t]here is nothing left for the\nagency to do[,]” Del. Riverkeeper Network v. Sec’y of Pa.\nDep’t of Envtl. Prot., (Riverkeeper II), 870 F.3d 171, 178 (3d\nCir. 2017). We noted those hallmarks on an earlier occasion\nwhen we said that, “[f]inal agency action must mark the\nconsummation of the agency’s decisionmaking process, must\nnot be of a merely tentative or interlocutory nature, and must\nbe one by which rights or obligations have been determined,\nor from which legal consequences will flow.” Riverkeeper\nIII, 903 F.3d at 72, 75 (citation and internal quotation marks\nomitted).\n\n To decide what the TCA requires for finality, we\nbegin, of course, with the text. See, e.g., Ross v. Blake, 136 S.\nCt. 1850, 1856 (2016) (“Statutory interpretation … begins\nwith the text[.]”) Here, the statutory text makes it clear that,\nif a denial is not in writing, there is something left for the\nagency to do. The denial provision of the TCA states that\n“[a]ny decision … to deny … shall be in writing and\nsupported by substantial evidence contained in a written\nrecord.” 47 U.S.C. § 332(c)(7)(B)(iii). We see no reason\nwhy the same should not be true for actions besides denial, 6\n\n 6\n For instance, it is not apparent why community\nmembers aggrieved by a decision to grant some permit to a\n\n\n\n\n 12\n\fbut we need not decide that today. It is enough to say that, in\nthose zoning decisions governed by the TCA, a locality’s oral\ndeclaration of a denial is “of a merely tentative or\ninterlocutory nature.” Riverkeeper III, 903 F.3d at 72\n(citation omitted) (speaking in reference to the Natural Gas\nAct); cf. Athens Cellular, Inc. v. Oconee Cty., 886 F.3d 1094,\n1104-05, 1107 (11th Cir. 2018) (noting that a zoning board\ncould have approved the minutes, revised them, or rejected\nthem, and thus until the board approved the minutes its\ndecision was not final).\n\n Moreover, an oral decision is not an action from which\nlegal consequences flow. Federal law governs finality, but\nDelaware’s procedures still matter, and the Delaware\nSuperior Court has concluded that a written document must\nbe filed for a ZBA action to be final. McDonald’s Corp. v.\nZoning Bd. of Adjustment for the City of Wilmington, No.\nCIV. A. 01A-05-011CG, 2002 WL 88944, at *1 (Del. Super.\nCt. Jan. 10, 2002). The court reasoned that Section 328 of\nTitle 22 of the Delaware Code, the section that governs\nappeals from ZBA proceedings, requires a written document\nto be filed because the statute “provides that [s]uch petition\nshall be presented to the Court within 30 days after the filing\nof the decision in the office of the board.” Id. (internal\nquotation marks omitted). That reasoning is persuasive and\n\n\n\n\nwireless provider, assuming those members have standing to\nsue, would not be equally entitled to a zoning authority’s\nwritten decision before the time limit in the TCA’s review\nprovision is triggered.\n\n\n\n\n 13\n\fshows that, under Delaware law, the ZBA’s oral decision is\nwithout legal consequences. 7\n\n There are distinct policy advantages to forestalling\njudicial scrutiny until a written denial is issued. Requiring a\nwritten decision focuses review on a particular, documented\nstatement of reasons. See USCOC of Greater Mo. v. City of\nFerguson, 583 F.3d 1035, 1042 (8th Cir. 2009) (“Because the\nwritten decision is the central object of our scrutiny under the\nTCA, the process of judicial review is best served by delaying\nthe ripening of a TCA claim until the local authority has\nissued its written decision.”). It also prevents ambiguity with\nrespect to when a claim can be brought. As the District Court\nhere stated, to hold otherwise “would promote a pernicious\nambiguity as to when that short period of time begins to run.”\n(App. at 7.) And it promotes uniformity of federal procedures\nby clarifying when, across all jurisdictions, an action becomes\nfinal.\n\n 7\n T Mobile cites to a different opinion, Schmalhofer v.\nBoard of Adjustment of Newark, to advance a contrary\nposition. No. C.A. 99A-05-010-WTQ, 2000 WL 703510\n(Del. Super. Ct. May 9, 2000). Schmalhofer states in a\nfootnote that “a written decision is not required or expressly\ncontemplated by this section.” Id. at *3 n.3. But T Mobile is\nstretching the Schmalhofer court’s language too far. In that\ncase, the City of Newark had issued a verbatim transcript of\nthe hearing, so there was a writing. Id. at *3; see infra note\n11. There is no indication of any written decision in this case,\nprior to December 22, 2016, when the City issued the written\ndenial bearing the date of December 21, 2016.\n\n\n\n\n 14\n\f The Supreme Court’s decision in T-Mobile South, LLC\nv. City of Roswell, Georgia, also adds support to the\nconclusion that only a written denial can constitute final\naction, triggering a party’s right to review. 135 S. Ct. 808\n(2015). In that case, the Court held that the “substantial\nevidence” supporting a locality’s decision to deny must be\nreleased contemporaneously with the written decision to\ndeny. 8 Id. at 811-12. In doing so, the Court tied together a\nlocal zoning authority’s final action, which triggers judicial\nreview, and its decision to deny, which must be in writing.\nIndeed, the Supreme Court said in no uncertain terms that,\n“[t]he relevant ‘final action’ [in that case, was] the issuance of\nthe written notice of denial[.]” Id. at 817 n.4. The Court\nlinked the locality’s decision to deny to the 30-day time limit\nto file a complaint after a final action has been taken. Id. at\n817 (“Only once the denial is issued would the 30-day\ncommencement-of-suit clock begin.”); id. at 813 (“[N]ow 29\ndays after the City denied petitioner’s application—petitioner\nfiled suit in Federal District Court.”).\n\n The Court went on to discuss timing, saying, “the\nlocality must provide or make available its written reasons at\nessentially the same time as it communicates its denial[,]”\n“[b]ecause an entity may not be able to make a considered\n\n 8\n The Court was interpreting the denial provision,\nwhich, as we noted earlier, states that, “[a]ny decision by a\nState or local government or instrumentality thereof to deny a\nrequest to place, construct, or modify personal wireless\nservice facilities shall be in writing and supported by\nsubstantial evidence contained in a written record.” 47\nU.S.C. § 332(c)(7)(B)(iii), City of Roswell, 135 S. Ct. at 811.\n\n\n\n\n 15\n\fdecision whether to seek judicial review without knowing the\nreasons for the denial of its application, and because a court\ncannot review the denial without knowing the locality’s\nreasons[.]” Id. at 816. The majority opinion was critical of\nthe dissent for attempting to “fashion a world in which a\nlocality can wait until a lawsuit is commenced and a court\norders it to state its reasons[,] … [leaving the challenging\nentity to] risk being sandbagged by the written reasons that\nthe locality subsequently provides in litigation after the\nchallenging entity has shown its cards.” Id. at 816 n.3. That\ncritique is premised on the written decision being the final\naction that starts the 30-day time limit for commencing suit. 9\n\n The Supreme Court anticipated that localities might\nneed to delay issuing a written denial if they are not ready to\nrelease their substantial reasons. See id. at 817 (noting that\n\n 9\n T Mobile asserts that Wilmington has a “pattern and\npractice of not issuing a written decision of land use denials\nunless or until the City is sued.” (Opening Br. at 7.) But if\nonly a written denial is a final action, the shot clock requires\nthe City to issue that written decision within a given time\nperiod. 24 FCC Rcd. 13994, 14012 (2009). T Mobile also\nasserts that when a locality has a pattern and practice of not\nreleasing written decisions, that practice delays the overall\nprocess, since a cellular service provider would be required to\ninitiate two causes of action: one to compel a written decision\nand another to challenge that written decision. That,\nhowever, is precisely what Congress envisioned by providing\nseparate remedies for a failure to “act” within a reasonable\ntime period and for an improper denial. 47 U.S.C.\n§ 332(c)(7)(B)(iii).\n\n\n\n\n 16\n\f“[i]f a locality is not in a position to provide its reasons\npromptly, the locality can delay the issuance of its denial\nwithin this 90– or 150–day window, and instead release it\nalong with its reasons once those reasons are ready to be\nprovided.”). That further counsels against treating an oral\ndetermination as a final action since, if an oral determination\nis deemed a final action, localities will be unable to take\nadvantage of the permissible delay afforded by the shot clock\nfor publishing their reasoning.\n\n Two of our sister courts of appeals agree that only a\nwritten decision can constitute final action. The Eighth\nCircuit in USCOC of Greater Missouri v. City of Ferguson\nstated that “[t]he plain language of the TCA indicates that\n‘final action’ does not occur until issuance of a written\ndecision.” 583 F.3d at 1041. The Eleventh Circuit in\nPreferred Sites LLC v. Troup County likewise held a\ncomplaint to be timely when it was filed within 30 days of a\nwritten decision, even though it was filed more than 30 days\nafter an oral decision. 10 296 F.3d 1210, 1217-18 (11th Cir.\n\n 10\n T Mobile attempts to distinguish Preferred Sites by\nstating that, unlike here, the case did “not address a city that\ndoes not issue a written decision close in time to when it\nmakes the decision to deny.” (Opening Br. at 37.) But that\nargument is irrelevant to whether the statutory text requires a\nwriting for an agency decision to be final. T Mobile also cites\nto Preferred Sites to argue that it should not matter if there is\na writing requirement since the oral denial could be seen as\nakin to a court announcing a decision. It explains that “when\nan appeal is filed after the court announces a decision, but\nbefore the entry of the judgment, it is treated as being filed on\nthe date of entry.” (Opening Br. at 28-29 (citing Preferred\n\n\n\n\n 17\n\f2002) (concluding that, “[b]ased on the plain language of the\nstatute,” that “a ‘final action’ occurs when the state or local\nauthority issues its written decision. The statute expressly\nmandates a … decision … committed to writing. Until the\nstate or local authority issues its written notification, its task\nunder the statute is not complete.”). No circuit has held\notherwise.\n\n Persuasive authority thus indicates that any action, and\ncertainly a denial, must be in writing to be final. But, there is\nanother possible interpretation of the statutory text. The\nwords “shall be in writing” could be read not as a condition of\nfinality, but instead as a simple directive to state and local\ngovernments to place their final action in writing. “The TCA\nprovides no express answer to … when a local government’s\npermitting decision becomes a ‘final action,’ which starts the\nthirty-day clock.” Athens Cellular, 886 F.3d at 1102-03. The\nstatute only states that denials must be in writing. 47 U.S.C.\n§ 332(c)(7)(b)(iii). Decisions to grant are not limited in the\nsame way. Id. And, Congress used the words “decision to\ndeny” in one statutory subsection and “final action” in\nanother, which could evince an intent to give those terms\ndifferent meanings. As the Supreme Court has “recognized\n… Congress’s use of certain language in one part of the\nstatute and different language in another can indicate that\ndifferent meanings were intended.” Sebelius v. Auburn Reg’l\nMed. Ctr., 568 U.S. 145, 156 (2013) (citation and quotation\n\n\n\nSites, 296 F.3d at 1217 n.7).) That analogy did appear in\nPreferred Sites, but it was only contained in a footnote. No\nother court has followed that line of reasoning, and we\ndecline to follow it here.\n\n\n\n\n 18\n\fmarks omitted). Thus, it could be argued, if Congress wanted\nto mandate a writing for zoning denials to constitute final\naction, it could have been more explicit, providing, for\ninstance, that a “decision must be in writing to qualify as a\nfinal action.”\n\n But, of course, one can almost always fault legislative\ndrafting, like other kinds of writing, after the fact. That\nsomething might have been said even more clearly does not\nmean it is not clear enough. So, “[r]ather than expecting (let\nalone demanding) perfection in drafting,” we can “construe[]\nstatutes to have a particular meaning even as we\nacknowledge[] that Congress could have expressed itself\nmore clearly.” Torres v. Lynch, 136 S. Ct. 1619, 1633\n(2016).\n\n The text and structure of the statute, Delaware\nprocedures, Supreme Court reasoning, our sister circuits’\ndecisions, and policy arguments all support the conclusion\nthat a writing is in fact a requirement for a denial to be final. 11\nIn light of that conclusion, the ZBA’s oral determination on\n\n 11\n What constitutes a “writing” has some flexibility,\nthough. See, e.g., Omnipoint Holdings, Inc. v. City of\nSouthfield, 355 F.3d 601, 605-07 (6th Cir. 2004) (approving\nminutes by written resolution was a final action that bound\nthe parties). In City of Roswell, for example, the Supreme\nCourt indicated that minutes of an oral meeting could be\nsufficient. 135 S. Ct. at 816. Here, however, there is no\nevidence that the ZBA’s oral determination was noted in the\nminutes of the October 26th meeting and issued by the City as\nits formal decision.\n\n\n\n\n 19\n\fOctober 26, 2016, was not a final action ripe for judicial\nreview. Therefore, as that oral determination was not reduced\nto writing until December 22, 2016, preceding the filing of\nT Mobile’s initial complaint, that complaint’s cause of action\nwas not ripe.\n\n\n\n\n 20\n\f B. No Separate Time Limit Exists Following an\n Oral Determination.\n\n As an alternative to its argument that the ZBA’s oral\ndecision was a final action, T Mobile asks us to consider\nwhether a “local government must issue the ‘writing’ close in\ntime to the ‘decision … to deny’ to establish a ‘final action’\nthat will be subject to expedited review.” 12 (Opening Br. at\n41.) Essentially, T Mobile is asserting that the “shot clock”\ngoverning the time to act, which allows a wireless carrier to\nsue for a locality’s failure to act, is insufficient, and that a\nnew requirement, albeit not in the statute, should be imposed\non localities. Under T Mobile’s proposed rule, an oral\ndecision would have to be reduced to writing within a\nspecified time period. That argument assumes that an oral\ndetermination can serve to satisfy the requirement to “act” on\na request within the limits of the shot clock, and that, without\na separate judicially created time limit, there would be no\ndeadline for the locality to release its written decision to deny,\ndespite City of Rowell’s contemporaneous writing\nrequirement. Because we conclude that a denial must be in\nwriting to be a final action, the issuance of that writing is the\ngovernment “act” ruled by the shot clock. 13 Aside from the\n\n 12\n Wilmington argues that T Mobile has waived that\nissue, but we need not address that argument because we\nconclude that no such requirement exists.\n 13\n Again, the Supreme Court held in City of Roswell\nthat a locality’s decision to deny must be accompanied by\nsubstantial reasons. 135 S. Ct. at 811-12. Otherwise, if a\nlocality were able to withhold its reasoning for its decision,\nthose aggrieved by the locality’s actions would “be left to\n\n\n\n\n 21\n\ftime limits associated with the “shot clock,” there is no other\ndeadline governing the issuance of a written decision\nfollowing an oral determination. 47 U.S.C. § 332(c)(7)(b).\nAny time limit we fabricated would be inappropriate.\n\n T Mobile argues that, without a requirement for\nlocalities to issue a written decision within a set amount of\ntime following an oral determination, wireless carriers are left\n“to wait until the FCC ‘shot clock’ expires – which could be\n90 or 150 days depending on the type of installation involved\n– and then [to] file an action alleging that the City has failed\nto act in a reasonable time[.]” (Opening Br. at 45.) It also\ncontends that a “failure to act” lawsuit is insufficient because\nthe remedy for a successful suit is simply an order telling the\nCity to issue a written decision. In T Mobile’s view, forcing\nwireless providers to sue both to compel a written decision\nonce the shot clock is violated and again to contest the written\ndecision serves only to “create yet further delay.” (Opening\nBr. at 46.)\n\n\n\n\nguess at what the locality’s written reasons will be, write a\ncomplaint that contains those hypotheses, and risk being\nsandbagged by the written reasons that the locality\nsubsequently provides in litigation after the challenging entity\nhas shown its cards.” Id. at 816 n.3. If an applicant cannot\nfile suit, however, because the locality’s “final action” has not\nyet occurred, those concerns vanish. The ZBA’s decision\nhere, when reduced to writing, was both its decision to deny\nand its final action.\n\n\n\n\n 22\n\f Those concerns are overstated and, in any case,\nirrelevant. The shot clock begins to run once a wireless\nprovider files its application, so it is already ticking before\nany oral decision is made. If the locality fails to meet that\ndeadline by not issuing a written decision before the shot\nclock expires, the wireless provider can bring a claim for a\n“failure to act.” 14 24 FCC Rcd. 13994, 14012 (2009). T\nMobile asserts that requiring a separate failure-to-act suit, in\naddition to a suit on the merits, undercuts the statutory\npurpose of expedited judicial review, particularly in cases\nwhere the locality has a “pattern and practice of not issuing a\nwritten decision of land use denials unless or until [it] is\nsued.” (Opening Br. at 7.) But the statute’s own remedies\ncannot possibly undercut its purpose. A separate failure-to-\nact claim is the very remedy Congress chose for shot clock\nviolations. 24 FCC Rcd. 14013 at ¶ 4 (2009). Whether or not\nT Mobile likes that policy choice, it is the one Congress\nmade, and we are not free to change it.\n\n C. The Timing Requirement Is Not\n Jurisdictional.\n\n Because we hold that a writing is required for a denial\nto constitute a final action, T Mobile’s initial complaint was\nnot ripe for review when filed. And, T Mobile’s\nsupplemental complaint was filed more than 30 days after the\nZBA issued its written decision and was therefore untimely\nunder the TCA’s review provision. 47 U.S.C.\n§ 332(c)(7)(B)(v). Thus, the District Court only had\njurisdiction if T Mobile’s supplemental complaint cured the\n\n 14\n It is not clear which time limit would have applied in\nthis case and whether it would have been violated.\n\n\n\n\n 23\n\fripeness flaw in its initial complaint by relating back to the\noriginal filing date. If the 30-day time limit in the TCA’s\nreview provision is nonjurisdictional, we can safely say that\nrelation back is possible and allows a supplemental complaint\nto cure a defective premature filing. 15 At the outset, then, we\nmust determine whether that 30-day time limit is\njurisdictional, being mindful both of the Supreme Court’s\ncounsel to exercise caution before holding timing\nrequirements to be jurisdictional and of its guidance regarding\nwhat constitutes a jurisdictional limit. 16 Sebelius, 568 U.S. at\n149, 153-54. Caution is indeed warranted because statutes of\nlimitations and other filing deadlines “ordinarily are not\njurisdictional.” Id. at 154; see also United States v. Kwai Fun\nWong, 135 S. Ct. 1625, 1632 (2015) (“[M]ost time bars are\nnonjurisdictional.”).\n\n\n 15\n We do not reach the issue of whether an unripe\ncomplaint can be cured by a supplemental or amended\npleading over which the Court lacked jurisdiction.\n 16\n The City claims that our decision in Nextel Partners\nInc. v. Kingston Township, 286 F.3d 687 (3d Cir. 2002) is\neffectively determinative. Not so. In Kingston Township,\nthen-Judge Alito noted that the District Court had held the\ntiming requirement in the TCA’s review provision was\njurisdictional. Id. at 695. But we did not address whether\nthat determination was correct, nor did we rely on it. Instead,\nwe concluded that there could be no “failure to act” towards\nan application that was not submitted. Id. at 692. Since our\ndecision in that case, the Supreme Court has clarified the\nprocess for determining if a time limit is jurisdictional.\nSebelius, 568 U.S. at 149.\n\n\n\n\n 24\n\f “[T]o ward off profligate use of the term ‘jurisdiction,’\n[the Supreme Court has] adopted a readily administrable\nbright line for determining whether to classify a statutory\nlimitation as jurisdictional.” Sebelius, 568 U.S. at 153 (citing\nArbaugh v. Y & H Corp., 546 U.S. 500, 516 (2006))\n(quotation marks omitted). We are to ask “whether Congress\nhas clearly state[d] that the rule is jurisdictional; absent such a\nclear statement, we … should treat the restriction as\nnonjurisdictional in character.” Id. (alteration in original)\n(citation and quotation marks omitted); see also Musacchio v.\nUnited States, 136 S. Ct. 709, 716 (2016) (Thus, “[w]e treat a\ntime bar as jurisdictional only if Congress has ‘clearly stated’\nthat it is.”). In deciding whether Congress has made such a\nclear statement, “we evaluate the ‘text, context, and relevant\nhistorical treatment.’” United States v. Kalb, 891 F.3d 455,\n460 (2018) (quoting Reed Elsevier, 559 U.S. 154, 166\n(2010)).\n\n Referencing that last test, Wilmington asserts that\n“[s]ection 332’s statutory grant of jurisdiction to district\ncourts, the text of the statute, the placement of the filing\nwindow in that same section, and the well-established\ntreatment of the filing window as jurisdictional, [all\ndemonstrate] that the filing window is jurisdictional.”\n(Answering Br. at 15.) We disagree. The differences\nbetween the review provision’s timing requirement and the\ntiming requirement we held to be jurisdictional in Kalb, and\nthe similarities between the review provision’s timing\nrequirements and those at issue in Sebelius and Musacchio,\nwhich the Supreme Court held to be nonjurisdictional,\nactually support treating the timing requirement in the TCA’s\nreview provision as nonjurisdictional.\n\n\n\n\n 25\n\f First, although Wilmington says that the text of the\nstatute indicates Congress’s desire to make the 30-day timing\nrequirement jurisdictional, the text does not use the term\n“jurisdictional” or any variation of it to describe the timing\nrequirement. 47 U.S.C. § 332(c)(7)(B)(v). To the contrary,\nthe statute uses permissive rather than mandatory language.\nUnlike the timing requirement we held to be jurisdictional in\nKalb, which mandated that an action would be barred if not\nfiled in time, the TCA’s review provision states that an action\n“may” be filed within 30-days. Compare Kalb, 891 F.3d at\n460 with 47 U.S.C. § 332(c)(7)(B)(v). The language is much\ncloser to that which the Supreme Court decided was\nnonjurisdictional in Sebelius. The statute at issue in that case,\nlike the review provision here, uses a permissive phrase –\n“may obtain a hearing” – before it states the timing\nrequirement. 17 Compare Sebelius, 568 U.S. at 154, with 47\nU.S.C. § 332(c)(7)(B)(v) (“may … commence an action”).\nSimilar to the timing requirement the Supreme Court held to\nbe nonjurisdictional in Musacchio, the review provision does\nnot confer jurisdiction, instead it allows an action to be\n\n 17\n T Mobile also points to Henderson v. Shinseki,\nwhich held a timing requirement to be nonjurisdictional even\nthough it used the mandatory “shall” before stating the timing\nrequirement. 562 U.S. 428, 441-42 (2011). But the decision\nin Shinseki, where the pertinent timing requirement could\nhave barred a veteran’s appeal, was partly based on “the\ncanon that provisions for benefits to members of the Armed\nServices are to be construed in the beneficiaries’ favor,” and\nso it is of less utility in deciding this dispute. Id. at 441\n(quotation marks and citations omitted).\n\n\n\n\n 26\n\fcommenced “in any court of competent jurisdiction.” See\nMusacchio, 136 S. Ct. at 717 (“[The provision] does not\nexpressly refer to subject-matter jurisdiction or speak in\njurisdictional terms.”). The text of the statute therefore favors\na holding that the timing requirement is nonjurisdictional.\n\n Wilmington next contends that the context of the\ntiming requirement favors the view that the requirement is\njurisdictional, because the Supreme Court has stated that it is\n“inextricably linked to … the language that creates the right\nof action[.]” (Answering Br. at 13-14 (citing City of Rancho\nPalos Verdes v. Abrams, 544 U.S. 113, 125 (2005)).) Thus,\nsays the City, the “filing window created by [the review\nprovision] is jurisdictional [because] it is integral to the\nexpress purpose of the section, to this Court’s jurisdiction,\nand to the parties’ rights and obligations[.]” (Answering Br.\nat 8.)\n\n True enough, the review provision’s timing\nrequirement does appear in the same subsection as the\nstatutory text granting jurisdiction. 47 U.S.C.\n§ 332(c)(7)(B)(v). And, as we stated in Kalb, the Supreme\nCourt’s decisions in Bowles v. Russell, 551 U.S. 205, 210\n(2007), and Reed Elsevier, Inc. v. Muchnick, 559 U.S. at 166,\nboth found the source of the timing requirement to be\nimportant in determining whether that requirement was\njurisdictional. 891 F.3d at 462. In Kalb, moreover, we made\nthe same point the City now does, stating that a timing\nrequirement was jurisdictional because “the thirty-day appeal\nperiod here is embedded in the same statutory section that\ngrants jurisdiction to the court of appeals.” Id.\n\n\n\n\n 27\n\f But the location of the timing requirement within the\nstatutory structure, without more, does not clearly reveal\nCongressional intent. As noted by the Supreme Court in\nSebelius, a timing requirement should not be classified as\njurisdictional solely based on its placement in a jurisdictional\nprovision. Sebelius, 568 U.S. at 155 (“A requirement we\nwould otherwise classify as nonjurisdictional … does not\nbecome jurisdictional simply because it is placed in a section\nof a statute that also contains jurisdictional provisions.”\n(citing Gonzalez v. Thaler, 565 U.S. 134, 146-47 (2012))). In\nMusacchio too, the Supreme Court held that a timing\nrequirement was nonjurisdictional despite its presence in the\njurisdiction-granting section of the statute at issue. 136 S. Ct.\nat 717. The Court emphasized that the statute did not directly\nspeak of the timing requirement as jurisdictional, despite its\nmandatory language. Id. That reasoning applies with at least\nequal force here, so the context of the review provision’s\ntiming requirement does not make the requirement\njurisdictional.\n\n Finally, Wilmington asserts that the timing\nrequirement is jurisdictional because of the historical\ntreatment of similar provisions. The City asserts that the\nphrase “within 30 days after” creates a “window,” during\nwhich a complaint must be filed, and not a “deadline.”\n(Answering Br. at 11-12 (citing W. Union Tel. Co. v. FCC,\n773 F.2d 375, 377 (D.C. Cir. 1985)) (noting that “within 60\ndays after” creates a 60-day filing window while “no later\nthan 60 days after” creates a filing deadline).) But that\nargument misses the point because it goes to whether the rule\nbars suit between certain dates or only after a certain date, not\nto whether the timing requirement is jurisdictional. See, e.g.,\nUnion Tel. Co., 773 F.2d at 377-78 (discussing whether the\n\n\n\n\n 28\n\ffiling window is a jurisdictional bar for suits filed before the\nwindow opens). And just because a complaint may be unripe\nbefore a particular date does not mean that a deadline by\nwhich suit must be filed is jurisdictional. As we stated in\nKalb, the Supreme Court’s decisions in Bowles and Reed\nElsevier both looked to “the Court’s prior treatment of\n[similar timing requirements.]” Kalb, 891 F.3d at 460. In\nSebelius, the timing requirement, as here, used the phrase\n“within” and thus, under Wilmington’s logic, it would have\nbeen a jurisdictional limit. Sebelius, 568 U.S. at 154. But the\nSupreme Court held otherwise, id., and that is of high\nimportance.\n\n Because the text and context of this statute, and\nhistorical treatment of timing requirements in similar statutes,\ndo not reveal a clear intent from Congress to make the review\nprovision’s timing requirement jurisdictional, we conclude\nthat it is not. 18\n\n D. Rule 15 Allows a Supplemental Complaint\n Filed After a Claims Processing Deadline To\n Relate Back and Cure an Unripe Initial\n Complaint.\n\n We next consider whether an untimely supplemental\ncomplaint can, by relating back, cure an initial complaint that\nwas unripe. We believe it can, and because T Mobile’s\n\n 18\n That conclusion is further supported by the\nthoughtful concurrence in Athens Cellular, concluding after\nSebelius that the timing requirement “imposed by Congress in\nthe TCA … is not a jurisdictional bar.” Athens Cellular, 886\nF.3d at 1113 (Kaplan, J. concurring).\n\n\n\n\n 29\n\fmotion to supplement its complaint was properly granted, that\nsupplemental complaint relates back and is ripe. The District\nCourt therefore had jurisdiction and should not have granted\nWilmington’s motion for summary judgment.\n\n At the outset, we note that the parties do not dispute,\nand we agree, that the District Court was within its discretion\nto grant T Mobile’s motion to supplement its complaint.\nPursuant to Federal Rule of Civil Procedure 15(d), “[o]n\nmotion and reasonable notice, the [district] court may, on just\nterms, permit a [moving] party to serve a supplemental\npleading setting out any … event that happened after the date\nof the pleading to be supplemented.” Fed. R. Civ. P. 15(d);\nsee also 3 James Wm. Moore et al., Moore’s Federal Practice\n¶ 15.30 (3d ed. 2018) (“Supplemental pleadings … are\nlimited to subsequent events related to the claim or defense\npresented in the original pleading.”). Here, the District Court\nrightly granted T Mobile’s motion to supplement. That\ndecision was just, since Wilmington had long since had notice\nof the event – the filing of the written denial – that occurred\nafter the initial pleading. After all, the City issued that denial,\nand the denial was featured in the parties’ discovery plan.\nThe issuance of it was also plainly related to T Mobile’s\ninitial complaint.\n\n That the initial complaint was premature is not a bar\nsince, under Rule 15(d), “[t]he court may permit\nsupplementation even though the original pleading is\ndefective in stating a claim for relief or defense.” Fed. R.\nCiv. P. 15(d). As the Advisory Committee Notes make clear,\n“Rule 15(d) is intended to give the [district] court broad\ndiscretion in allowing a supplemental pleading.” Fed. R. Civ.\nP. 15(d) advisory committee’s note to 1963 amendment. It is\n\n\n\n\n 30\n\ffurthermore “within the discretion of the court to allow a\nsupplemental pleading to be filed at any stage of the case[.]”\nMoore et al., supra, ¶ 15.30. The District Court here was thus\nwell within its discretion in granting T Mobile’s motion to\nsupplement the complaint.\n\n Rule 15 does not indicate whether or under what\ncircumstances a supplemental pleading can relate back to the\ndate of the original pleading to avoid the effect of a time\nlimit. 6A Charles Alan Wright et al., Federal Practice &\nProcedure § 1508 (3d ed. 2018). Subsection (c) of the Rule,\nwhich provides for the relation back of amended pleadings,\ndoes not specifically refer to supplemental pleadings. Fed. R.\nCiv. P. 15(c). Nor does Rule 15(d) make any mention of\nrelation back. Fed. R. Civ. P. 15(d). But case law and\nsecondary sources have long instructed that once a\nsupplemental complaint is granted, it is treated like an\namended complaint for purposes of relation back. 19 Thus,\neven though Rule 15(d) is in a separate statutory provision\nfrom Rule 15(c), a supplemental complaint can relate back.\nWright et al., supra, § 1508; see also F.D.I.C. v. Knostman,\n966 F.2d 1133, 1138 (7th Cir. 1992) (“The distinction\nbetween an amended pleading and a supplemental pleading is\n\n 19\n Courts have generally held that a supplemental\ncomplaint is eligible for relation back, but rely on different\nrationales to do so. See Wright et al., supra, § 1508 (“[S]ome\ncourts have held that for purposes of applying the relation-\nback doctrine a supplemental pleading may be treated as an\namended pleading under Rule 15(c); other courts have\napplied the relation-back principle directly to supplemental\npleadings even though Rule 15(d) does not mention it.”)\n(internal citations omitted).\n\n\n\n\n 31\n\foften disregarded for purposes of relation back under Rule\n15(c).”); Russell v. New Amsterdam Cas. Co., 303 F.2d 674,\n680-81 (8th Cir. 1962) (finding supplemental pleading related\nback despite plaintiff suing in the wrong capacity and not\nachieving appropriate status for diversity jurisdiction until\nafter the limitations period had expired). That stands to\nreason, since, if a “defendant had notice of the subject matter\nof the dispute and was not prejudiced in preparing a defense\n…[,] the policy against stale claims becomes subsidiary to the\npolicy expressed throughout the rules in favor of allowing a\nparty to set forth all the grievances against another party in\none action and resolving them on their merits.” Wright et al.,\nsupra, § 1508.\n\n So a pleading filed according to Rule 15(d) can relate\nback, assuming it meets “the basic test for relation back\nprescribed by Rule 15(c).” Id.; see also Moore et al., supra,\n¶ 15.30 (“A supplemental pleading may relate back to the\ndate of the original complaint if the requirements under Rule\n15(c) for relation back are satisfied”); Davis v. Piper Aircraft\nCorp., 615 F.2d 606, 609 n.3 (4th Cir. 1980) (supplemental\npleading relates back if Rule 15(c)’s test is met). In fact, as\nthe District Court observed, if a supplemental complaint\nmeets the requirements for relation back then “[r]elation back\nis mandatory,” and not subject to additional equitable\nconsiderations. 20 (App. at 6 (citing Arthur v. Maersk, Inc.,\n434 F.3d 196, 202-03 (3d Cir. 2006)).)\n\n 20\n We note, however, that “[a] party opposing the\nintroduction of a supplemental pleading might wish to raise\nthe statute-of-limitations defense when the additional\npleading (1) alleges new matter that brings the earlier\npleading up to date; (2) cures a defect in the original pleading;\n\n\n\n\n 32\n\f Looking then to Rule 15(c), a complaint “relates back\nto the date of the original pleading when … [it] asserts a\nclaim or defense that arose out of the conduct, transaction, or\noccurrence set out -- or attempted to be set out -- in the\noriginal pleading[.]” Fed. R. Civ. P. 15(c)(1)(B). The\nDistrict Court here concluded that there was no need to\ndetermine whether T Mobile’s supplemental complaint\nrelated back, because, even if it did, “it fail[ed] to cure the\ndeficiencies of the initial complaint[.]” (App. at 8.) But\ngiven our view that the supplemental complaint could indeed\ncure the ripeness problem with the initial complaint, we must\ncontend with the relation-back question.\n\n To determine if relation back is proper, the only issue\nis whether there is a “common core of operative facts in the\ntwo pleadings.” Bensel v. Allied Pilots Ass’n, 387 F.3d 298,\n310 (3d Cir. 2004.) Here, that test is met. Both complaints\nrely on the same core facts. The written denial was a\ncertification and restatement of the earlier oral denial.\n\n Thus, the only question remaining is whether a\ncomplaint that relates back can cure an untimely initial\ncomplaint, and the answer is yes. The clear preference\nembodied in Rule 15 is for merits-based decision making. Cf.\nMoore et al., supra, ¶ 15.30 (“The same principles that\nsupport the liberal amendment of pleadings also apply to\nsupplemental pleadings.”). As the Supreme Court has stated,\nthe purpose of Rule 15 is “to balance the interests of the\n\n\nor (3) states a new claim that arose after the filing of the\ncomplaint.” Wright et al., supra, § 1508.\n\n\n\n\n 33\n\fdefendant protected by the statute of limitations with the\npreference expressed in the Federal Rules of Civil Procedure\nin general, and Rule 15 in particular, for resolving disputes on\ntheir merits.” Krupski v. Costa Crociere S.p.A., 560 U.S. 538,\n550 (2010). The requirements of Rule 15 itself protect\ndefendants from an unfair relation back. 21 Under that Rule,\ncourts “look[s] to whether the opposing party has had fair\nnotice of the general fact situation and legal theory upon\nwhich the amending party proceeds.” Bensel, 387 F.3d at\n310. In this instance, Wilmington had sufficient notice since\nthe supplemented complaint simply alleged the issuance of\nthe ZBA’s written denial. And, of course, Wilmington had\nnotice of everything in the supplemental complaint. It not\nonly knew of the written denial and the reasons given, it\ngenerated them.\n\n Relation back has been allowed to address\njurisdictional problems. We said in Berkshire Fashions, Inc.\nv. M.V. Hakusan II that relation back may be used to cure\ndefects in jurisdictional allegations. 954 F.2d 874, 878 (3rd\nCir. 1992). In that case, the District Court had dismissed the\nplaintiff’s claim based on admiralty jurisdiction and denied\nthe plaintiff’s motion to amend its complaint to allege\ndiversity jurisdiction. Id. at 877. We concluded that both\ndecisions were in error, holding that an amended complaint\nrelates back and can cure insufficient pleading of subject\nmatter jurisdiction. Id. at 878. Recently, our Circuit allowed\n\n 21\n This is not a pass for endless delay in\nsupplementing a complaint. Indeed, we have endeavored to\nemphasize that whether to allow supplemental pleading\ndepends on equitable considerations of fairness and notice\nthat district courts must take into account.\n\n\n\n\n 34\n\fa plaintiff to cure a diversity defect when the case had been\nlitigated for years. See GBForefront, L.P., v. Forefront\nMgmt. Grp., LLC, 888 F.3d 29, 32 (3d Cir. 2018)\n(“instruct[ing] the [d]istrict [c]ourt to give leave to further\namend the complaint … to cure defective jurisdictional\nallegations”).\n\n Other circuits have held the same. See Woods v. Ind.\nUniv.-Purdue Univ. at Indianapolis, 996 F.2d 880, 884 (7th\nCir. 1993) (“Consistent with its history and purpose, Rule\n15(c) has uniformly been applied to relate back [filings] that\ncure defective statements of jurisdiction ….”); Boyce v.\nAnderson, 405 F.2d 605, 607 (9th Cir. 1968) (allowing\namendment alleging that no previous appeal had been taken\nto the United States Court of Customs and Patent Appeals to\ncure jurisdictional defect in complaint after statute of\nlimitations had expired). That conclusion is also consistent\nwith 28 U.S.C. § 1653, which allows “[d]efective allegations\nof jurisdiction [to] be amended, upon terms, in the trial or\nappellate courts.” Id.\n\n Courts have similarly permitted cure of actual defects\nin the court’s jurisdiction, going beyond just jurisdictional\nallegations. For instance, although not in a case involving a\nlater complaint, the Supreme Court has said that a court can\ndrop a dispensable non-diverse party to cure a defect in\ndiversity jurisdiction. Newman-Green, Inc. v. Alfonzo-\nLarrain, 490 U.S. 826, 837-38 (1989); see also E.R. Squibb &\nSons, Inc. v. Lloyd’s & Cos., 241 F.3d 154, 163 (2d Cir.\n2001) (stating that, “where it is appropriate to relate back an\namendment to a pleading under Rule 15, jurisdiction is\nassessed as if the amendment had taken place at the time the\ncomplaint was first filed[,]” and thus replacing a non-diverse\n\n\n\n\n 35\n\fplaintiff with a diverse plaintiff cured any jurisdiction\nproblem); Rowe v. United States Fid. & Guar. Co., 421 F.2d\n937, 939, 944 (4th Cir. 1970) (concluding that a defective\ncomplaint could be cured by a later complaint that pled an\nassignment occurring after the original complaint was filed).\n\n Nonetheless, “[a]mendments that go beyond the mere\ncorrection or factual modification of the original pleading and\nsignificantly alter the claim or defense alleged in that\npleading are treated more cautiously by the courts in applying\nthe relation-back doctrine.” Wright et al., supra, § 1497. The\nSecond Circuit, for instance, only sometimes allows\njurisdictional defects to be cured “when the underlying facts,\nif properly pled, would have supported jurisdiction at the time\nthe action commenced.” Correspondent Servs. Corp. v. First\nEquities Corp. of Fla., 338 F.3d 119, 125 (2d Cir. 2003); see\nalso, e.g., Barton v. Ellis, No. 75-1188, 1977 WL 15469, at\n*1 (D.S.C. Apr. 26, 1977) (denying using relation back to\ncure the original complaint since they were defects “not [in\nthe] allegations of existing underlying jurisdictional facts but\nrather [in] the prerequisite jurisdictional facts themselves”).\nWilmington argues such hesitance is appropriate here because\nallowing relation back to cure the jurisdictional problem with\nT Mobile’s initial complaint “would allow two wrongs under\nSection 332 [(filing early and filing late)] to make a right.”\n(Answering Br. at 2.)\n\n We again disagree with the City. It is quite true that\nT Mobile has made procedural matters more difficult than\nthey should be in this case. But denying relation-back to cure\nthe defect in this instance would not comport with Rule 15’s\naim to encourage resolution of disputes on the merits\nwhenever possible. The ripeness requirement exists so that\n\n\n\n\n 36\n\fcourts avoid issuing essentially advisory opinions. See\nRichard H. Fallon, Jr. et al., Hart and Wechsler’s the Federal\nCourts and the Federal System 224 (5th ed. 2003) (noting that\nthe ripeness doctrine allows courts to avoid a “dispute … too\n‘ill-defined’ to be appropriate for judicial resolution until\nfurther developments … more sharply framed the issues for\ndecision.”). That concern ceased to exist here once the\nsupplemental pleading was in place. At that point, the dispute\nhad matured and become capable of judicial review,\ndemonstrating that, “actions taken after the filing of the initial\ncomplaint can be used to establish subject matter\njurisdiction.” Prasco, LLC v. Medicis Pharm. Corp., 537\nF.3d 1329, 1337 (Fed. Cir. 2008).\n\n If a supplemental complaint cannot cure an unripe\ncomplaint, an endless feedback loop would be created\nwhereby the ripeness problem could never be overcome, even\nthough, as here, the dispute later became obviously ripe. Our\nsister circuits have recognized that problem and concluded\nthat a supplemental complaint is the solution. 22 In Wilson v.\nWestinghouse Electric Corp., the Eighth Circuit determined\nthat prohibiting an amended (or supplemental) complaint\nfrom alleging facts that occurred after the date the initial\n\n 22\n In our Circuit, a thoughtful district court decision\nhad long ago reached that conclusion. It held that an\nuntimely supplement adding facts occurring after the initial\nfiling that showed exhaustion of administrative remedies\ncould relate back to the initial premature complaint and allow\nmaintenance of the lawsuit. Bates v. W. Elec., 420 F. Supp.\n521, 526-27 (E.D. Pa. 1976).\n\n\n\n\n 37\n\fcomplaint was filed would turn a premature complaint into an\n“irretrievable mistake that bars jurisdiction” and would be\n“precisely the kind of procedural mousetrap that the Federal\nRules were designed to dismantle.” 838 F.2d 286, 289 (8th\nCir. 1988). The court held that, “[e]ven when the District\nCourt lacks jurisdiction over a claim at the time of its original\nfiling, a supplemental complaint may cure the defect by\nalleging the subsequent fact which eliminates the\njurisdictional bar.” Id. at 290 (citing Mathews, 426 U.S. at\n75). While Wilson addressed a circumstance in which the\nsupplemental complaint was timely filed, the proposition still\napplies in a case like ours because, if a party was limited to\nrefiling within an applicable time limit, there would be little\nneed to make provision for supplementation of a complaint,\nas a new complaint could be filed. 23\n\n 23\n We note that sparing the cost of refiling and\nproviding convenience to the Court would remain legitimate\nreasons for allowing supplemental complaints. But the\npurpose of Rule 15(d) is broader. See Wright et al., supra, §\n1504 (“The purpose of subdivision (d) is to promote as\ncomplete an adjudication of the dispute between the parties as\nis possible. … A supplemental pleading may be employed\nfor a variety of purposes.”). Wilmington contends that\nWilson is inapposite since it involved a timely supplemental\ncomplaint. Thus, concern about a perpetual loop outcome\nwas not proper because the plaintiff could have simply refiled\nhis complaint. But we agree that “a plaintiff need not\ncommence a new action when after-occurring events\ndemonstrate that it has a right to relief even if the original\ncomplaint was insufficient. A plaintiff may also be allowed\nto supplement the complaint even if jurisdiction … would not\nhave been proper if the claim had been asserted in an\n\n\n\n\n 38\n\f The Ninth Circuit, in Security Insurance Co. of New\nHaven v. United States ex rel. Haydis, also relied on that logic\nto find that relation back could cure an unripe complaint filed\nbefore a statutory filing window opened. 338 F.2d 444, 448-\n49 (9th Cir. 1964). In a fact scenario with striking similarities\nto the present appeal, the plaintiff had filed its claim before a\nstatutory waiting period was over and then did not file an\namended complaint until after the statute of limitations period\nhad run. Id. at 445-46. The appeals court held that the\ndistrict court was “not required to apply the doctrine of\nrelation back so literally as to carry it to a time [before it was\nripe] so as to prevent the maintenance of the action in the first\nplace.” Id. at 449.\n\n The Supreme Court has favorably cited Security\nInsurance’s ruling. In Mathews, the plaintiff had not satisfied\na precondition of filing a complaint by first filing an\napplication with a particular agency. 426 U.S. at 72, 75. The\nCourt noted that a supplemental complaint, alleging that the\napplication had since been filed, would have cured the\njurisdictional defect. Id. at 75. In saying so, the Court relied\n\n\n\nindependent action.” Moore et al., supra, ¶ 15.30 (3d ed.\n2018) (citation omitted). If supplemental complaints could\nnot cure ripeness, “then all supplemental pleadings of this\nnature would be defeated for lack of jurisdiction – [the]\n‘procedural mousetrap’ would render all supplemental\npleadings void.” George v. IRS, No. C05-00955 MJJ, 2006\nWL 3499230, at *3 (N.D. Cal. Dec. 4, 2006) (citation\nomitted).\n\n\n\n\n 39\n\fon Security Insurance. Id. at 75 n.8 (citing Security\nInsurance, 338 F.2d at 447-49). 24\n\n Yet Wilmington asserts that ripeness can never be\ncured by a later complaint. It advances four cases for that\nproposition, but none are helpful. First, the City cites\nDelaware Riverkeeper Network v. Secretary Pennsylvania\nDepartment of Environmental Protection, (Riverkeeper I),\n833 F.3d 360 (3d Cir. 2016), in which we concluded that,\n“even though the underlying claim became ripe for review\nduring the pendency of the case, the ripening of the claim did\nnot cure deficient pleadings.” (App. at 8.) In that case,\nhowever, no attempt to file a later complaint alleging ripeness\nwas made. Riverkeeper I, 833 F.3d at 369-70.\n\n Likewise, in another two of the four cases that\nWilmington cites, there was no effort made to amend or\nsupplement the complaint. See TeleSTAR, Inc. v. FCC, 888\nF.2d 132, 134 (D.C. Cir. 1989) (concluding non-final agency\naction at the time of filing of petition may only be reviewed\nupon the filing of another petition); W. Union Tel. Co., 773\nF.2d at 377-78 (concluding that the court lacked jurisdiction\nover challenges filed before the action became final).\nTherefore, neither case determined whether relation back of a\nlater-filed complaint could cure a ripeness problem in the\ninitial complaint.\n\n 24\n Wilmington contends that Mathews is inapposite\nsince the statute of limitations was waived. That argument\nhas no traction since, if it were a jurisdictional bar, it could\nnot be waived.\n\n\n\n\n 40\n\f The City fares no better relying on Council Tree\nCommunications v. FCC, in which we stated that “[a] petition\nto review a non-final agency order is incurably premature.”\n503 F.3d 284, 291 (3d Cir. 2007). At no point in that case\nwas the complaint ripe, and the petitioner still had a petition\nfor reconsideration pending before the relevant agency on the\ndate the case was decided. Id. at 287. Furthermore, Council\nTree explicitly acknowledged that a supplemental complaint\ncan cure an unripe complaint when there is jurisdiction over\nthat supplemental pleading. See id. at 291 (“[W]e note that\n‘nothing prevented [the petitioners] from supplementing their\npremature petition with a later protective petition.’” (second\nalteration in original) (quoting Horsehead Res. Dev. Co. v.\nE.P.A., 130 F.3d 1090, 1095 (D.C. Cir. 1997))).\n\n Wilmington also makes three policy arguments in\nsupport of its position that an untimely supplemental\ncomplaint should not be able to cure an unripe complaint.\nFirst, it contends that allowing suits to be filed before an\naction is ripe would “extend[] federal court jurisdiction over\nlocal government actions before those actions are final[.]”\n(Answering Br. at 9.) Second, such filings would waste\njudicial resources and, in this case, cost taxpayers money, by\nforcing courts to deal with a higher volume of unripe\ncomplaints. Third, the purpose of § 332 is to preserve local\nzoning authority, which would be undermined by allowing\nplaintiffs to file suit early and thereby places undue pressure\non zoning commissions.\n\n Those contentions, however, are unpersuasive. First, a\ncourt would remain without jurisdiction if the claim had not\nripened by the time of the supplemental complaint. Second, it\n\n\n\n\n 41\n\fseems that Wilmington overstates the impact that a decision\nallowing an unripe complaint to be cured would have, since\nour holding today makes it clear that an action is not final\nuntil a written decision has been issued. Clarifying when a\ndetermination is ripe for review should end any incentive for\naggrieved parties to file early to ensure they have not filed too\nlate.\n\n Perhaps more importantly, however, courts can police\nany potential abuse on a case-by-case basis using Rule 15(d)\nand the Rule 15(c) test for relation back. It is understood that\n“relation back of a supplemental pleading should not result in\nproviding unfair procedural advantages to a plaintiff[,] so …\nrelation back may not be for all purposes.” Wright et al.,\nsupra, § 1508. But here no unfair advantage has resulted, and\ndefendants in general will be adequately protected by a\ndistrict court’s Rule 15(d) analysis, which will determine if a\nsupplemental complaint should be allowed at all. For\ninstance, if a locality’s action is not yet a final action at the\ntime a Rule 15(d) motion is filed, the motion can easily be\ndenied. See Beezley v. Fremont Indem. Co., 804 F.2d 530,\n530 (9th Cir. 1986) (supplemental pleading denied when it\nstill failed to cure defective original pleading).\n\n When all is said and done here, we conclude that, to\neffectuate the liberal purpose of Rule 15 and to avoid the\nendless feedback loop that the City’s legal argument would\ncreate, Rule 15 allows an untimely supplemental complaint to\nrelate back and cure an unripe initial complaint.\n\n\n\n\n 42\n\fIII. CONCLUSION\n\n For the foregoing reasons, we will reverse the District\nCourt’s grant of the City’s motion for summary judgment,\nvacate the District Court’s denial of T Mobile’s motion for\nsummary judgment, and remand to the District Court for\nfurther proceedings consistent with this opinion.25\n\n\n\n\n 25\n We will vacate the District Court’s denial of\nT Mobile’s motion for summary judgment because it was\nsolely based on a finding that T Mobile’s suit was not timely\nbrought.\n\n\n\n\n 43", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357819/", "author_raw": "JORDAN, Circuit Judge."}]}
JORDAN
NYGAARD
VANASKIE
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580566/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: T MOBILE NORTHEAST LLC, Appellant v. CITY OF WILMINGTON, DELAWARE ; City of Wilmington Zoning Board of Adjustment\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-10\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 18-1831\n _____________\n\n T MOBILE NORTHEAST LLC,\n Appellant\n\n v.\n\n CITY OF WILMINGTON, DELAWARE;\nCITY OF WILMINGTON ZONING BOARD OF ADJUSTMENT\n _____________\n\n On Appeal from the United States District Court\n for the District of Delaware\n (D.C. No. 1-16-cv-01108)\n District Judge: Hon. Eduardo C. Robreno\n _______________\n\n Argued\n September 12, 2018\n\nBefore: JORDAN, NYGAARD, and VANASKIE, * Circuit Judge\n (Filed: January 10, 2019)\n\n\n *\n The Honorable Thomas I. Vanaskie retired from the\nCourt on January 1, 2019 after the argument and conference\nin this case, but before the filing of the opinion. This opinion\nis filed by a quorum of the panel pursuant to 28 U.S.C.\n§ 46(d) and Third Circuit I.O.P. Chapter 12.\n\f _______________\n\nThomas S. Thompson [ARGUED]\nDavis Wright Tremaine\n1919 Pennsylvania Avenue, NW\nSte. 800\nWashington, DC 20006\n\nCounsel for Appellant\n\nJoseph Van Eaton [ARGUED]\nBest Best & Krieger\n2000 Pennsylvania Avenue\nSte. 5300\nWashington, DC 20006\n\nCounsel for Appellees\n _______________\n\n OPINION OF THE COURT\n _______________\n\n\nJORDAN, Circuit Judge.\n\n No one likes bad cell phone reception or slow\nstreaming data on their smartphone, but that does not mean\nanyone wants a cellular antenna in their neighborhood, which\nis why there are zoning battles like the one central to this\ncase.\n\n T Mobile Northeast LLC (“T Mobile”), a wireless\ntelecommunications service provider, applied to the Zoning\nBoard of Adjustment (“ZBA”) of the City of Wilmington,\nDelaware for permission to erect an antenna in the City. The\n\n\n\n\n 2\n\fZBA said no. So, relying on a provision of federal law that\nallows a disappointed wireless service provider like T Mobile\nto seek review in a district court “within 30 days after” a\nzoning authority’s “final action,” 47 U.S.C.\n§ 332(c)(7)(B)(v), T Mobile filed suit. After the case had\nproceeded for over a year, however, the District Court\nconcluded that it lacked jurisdiction. The Court reasoned that\nbecause T Mobile filed its complaint before the ZBA released\na written decision confirming an earlier oral rejection of the\nzoning application, the claim was not ripe. And, since\nT Mobile did not supplement its complaint to include the\nZBA’s written decision within 30 days of its issuance, the\nCourt also concluded that relation back could not remedy the\nripeness defect. The District Court thus granted the City’s\nmotion for summary judgment.\n\n T Mobile now appeals. It argues that its complaint\nwas not premature or, in the alternative, that its supplemental\npleading cured any ripeness problem. We agree that the grant\nof summary judgment was improper and, for the reasons that\nfollow, will remand the case for further proceedings\nconsistent with this opinion.\n\nI. BACKGROUND\n\n A. Statutory Framework\n\n This dispute is governed by the Telecommunications\nAct of 1996 (“TCA”), which amended the Federal\nCommunications Act of 1934 and includes provisions on\nmobile phone services. Pub. L. No. 104-104, §§ 1, 704, 110\nStat. 56, 56, 151 (1996); 47 U.S.C. § 332. Passed to\n“encourage the rapid deployment of new telecommunications\n\n\n\n\n 3\n\ftechnologies,” Preamble, 110 Stat. at 56, the TCA provides\nfor expedited review in federal court of a denial of permission\nto build a cell phone antenna, id. § 704, 110 Stat. at 151-52.\nSuch review is a “benefit Congress expressly intended to\nconfer on wireless providers[.]” Nextel W. Corp. v. Unity\nTwp., 282 F.3d 257, 264 (3d Cir. 2002). At the same time,\nthe TCA also serves to preserve local zoning authority. 47\nU.S.C. § 332(c)(7).\n\n At issue here are three key sections of the statute.\nFirst, the TCA mandates that “[a] State or local government\nor instrumentality thereof shall act on any request for\nauthorization to place, construct, or modify personal wireless\nservice facilities within a reasonable period of time after the\nrequest is duly filed[.]” Id. § 332(c)(7)(B)(ii). The Federal\nCommunications Commission (“FCC”) has interpreted\n“reasonable period of time” in that statutory provision to\nmean that zoning authorities have a “shot clock” 1 and must\nact within 90 days of an application to attach an antenna to an\nexisting structure or 150 days of an application where a new\nsupport structure is to be built. Petition for Declaratory\n\n 1\n “Shot clock” is a term borrowed from basketball. In\nthat game, it signifies a time limit to make a shot attempt,\nbeginning once a team has possession of the basketball. See,\ne.g., Nat’s Basketball Ass’n, NBA Rulebook Rule No. 7: Shot\nClock (2018-2019), http://official.nba.com/rule-no-7-24-\nsecond-clock/. If the team has not made a shot attempt, i.e.,\nacted, within the prescribed time limit, it forfeits possession\nof the ball. Id. Here, the permitting authority has exclusive\njurisdiction over an application until it fails to act within a\n“reasonable period of time.” 47 U.S.C. §§ 332(c)(7)(A),\n332(c)(7)(B)(ii).\n\n\n\n\n 4\n\fRuling to Clarify Provisions of Section 332(c)(7)(B), 24 FCC\nRcd. 13994, 14008, 14012 (2009). Second, in what we will\ncall the “review provision” of the statute, the TCA grants\n“[a]ny person adversely affected by any final action or failure\nto act by a State or local government or any instrumentality\nthereof” a right to have that locality’s decision reviewed by\n“commenc[ing] an action” “within 30 days” in district court.\n47 U.S.C. § 332(c)(7)(B)(v). Third, in the statute’s “denial\nprovision,” the TCA states that “[a]ny decision by a State or\nlocal government or instrumentality thereof to deny a request\nto place, construct, or modify personal wireless service\nfacilities shall be in writing and supported by substantial\nevidence contained in a written record.” Id.\n§ 332(c)(7)(B)(iii). Notably, the terms “act,” “final action,”\nand “decision … to deny” are not defined in the TCA.\nFurthermore, the statute does not make clear whether “final\naction” should be read to encompass all decisions to deny,\nincluding oral ones, nor does it address whether there is a\ndifference between an “act” for purposes of the shot clock\nand a “final action” for purposes of judicial review.\n\n B. Factual Background\n\n T Mobile is a telecommunications service provider. It\nsays that it needs to erect a cellular antenna to fill “a\nsignificant gap” in coverage for its customers in Wilmington,\nDelaware, (Opening Br. at 3) presumably where there has\nbeen an increase in phone calls and data usage. T Mobile\nwants to put its antenna on top of a senior living high-rise in\nthe City, but, because a special exception to local zoning laws\nis needed, it first had to go to the ZBA. It filed an initial\napplication and then, on August 25, 2016, a final amended\napplication, seeking the exception.\n\n\n\n\n 5\n\f The ZBA held a hearing on October 26, 2016, to\nconsider T Mobile’s request, some two months after the final\namended application was submitted. During the hearing,\nT Mobile presented evidence of the need for the antenna and\ndiscussed proposals to address aesthetic concerns. The ZBA\nalso received objections from members of the local\ncommunity, some of whom were outspoken in worrying\nabout the effects of radio frequency emissions. At the end of\nthe hearing, the ZBA denied T Mobile’s application in a\nunanimous oral decision.\n\n The Board gave several reasons for the denial. One\nboard member said the ZBA should not encourage the use of\na senior living community rooftop as the base for an antenna\nbecause of the potential adverse effect on the properties in the\nneighborhood. Another board member said there was not\nenough proof of a need for additional coverage to support the\napplication. The Chairman said there was not enough\nevidence that T Mobile needed the antenna and that it did not\nappear to satisfy the zoning code in terms of placement and\nheight restrictions.\n\n The ZBA’s oral decision to deny the application was\nnot put in writing on October 26 or anytime soon thereafter.\nAccording to T Mobile, that fits a “pattern and practice of\n[the ZBA] not issuing a written decision of land use denials\nunless or until the City is sued.” (Opening Br. at 7.) Only\nafter T Mobile had filed its initial complaint in the District\nCourt, and after the City filed its answer, did the ZBA issue\nits written decision and explanation of its reasoning for\ndenying the application.\n\n\n\n\n 6\n\f T Mobile asserts that the denial of its application\nviolates the TCA. Under the statute, such a denial is invalid\nif it has the “effect of prohibiting the provision of personal\nwireless services[,]” 47 U.S.C. § 332(c)(7)(B)(i)(II), or is “on\nthe basis of the environmental effects of radio frequency\nemissions[,]” id. at § 332(c)(7)(B)(iv). T Mobile claims that\nWilmington’s denial was improper on both of those grounds. 2\nBut those assertions go to the merits and are not actually\nbefore us on this appeal. At issue now is whether T Mobile’s\nclaim can be heard at all.\n\n C. Procedural History\n\n Evidently with its eye on the 30-day deadline in the\nTCA’s review provision, T Mobile filed a lawsuit in the\nUnited States District Court for the District of Delaware\nwithin 30 days of the ZBA’s oral decision, challenging that\ndenial. 3 In addition to its claims on the merits, T Mobile’s\ninitial complaint alleged that the City violated procedures\nmandated in the TCA, specifically those in the denial\nprovision, by failing to provide a written decision\n\n 2\n T Mobile also raised a Delaware state law claim.\nThat claim is not at issue here and does not impact\nT Mobile’s claims under federal law.\n 3\n For reasons discussed herein, the 30-day filing\ndeadline was not triggered by the oral decision. See infra pp.\n12-20. If it were, however, T Mobile’s complaint would have\nbeen timely. The oral decision was delivered at the\nOctober 26, 2016 hearing. Suit was filed on November 28,\n2016, but because the thirtieth day from October 26 fell on a\nweekend, the November 28 filing was within the 30-day\nwindow. Fed. R. Civ. P. 6(a)(1).\n\n\n\n\n 7\n\fcontemporaneous with its oral decision and by not supporting\nthe denial with substantial evidence.\n\n The parties entered into a stipulation asking the\nDistrict Court for an expedited case schedule, as provided for\nin the review provision of the TCA. 47 U.S.C.\n§ 332(c)(7)(B)(v). That request was granted. Wilmington\nthen answered the complaint, asserting a number of\naffirmative defenses, including that the complaint was not\nripe because the ZBA had not yet issued a final written\ndecision. Nevertheless, the City did not, at that time, file a\nmotion to dismiss for failure to state a claim or for lack of\njurisdiction. Two days after the City filed its answer, the\nZBA issued a written decision on T Mobile’s application.\nThe parties pressed forward with the suit and prepared a\ndiscovery plan, which specifically mentioned the written\ndecision. T Mobile filed a motion for summary judgment,\nwhich the City met with a cross-motion for summary\njudgment. The City’s motion was styled in the alternative as\na motion to dismiss the complaint as unripe because it was\nfiled prematurely, i.e., before the written decision had been\nissued.\n\n Not until December 21, 2017, nearly a year after the\nZBA issued its written denial, did T Mobile file a motion\nseeking leave to amend or supplement the initial complaint to\nnote the issuance of that written decision. 4 The District Court\n\n 4\n When “[a] claim or defense set out in a pleading [is]\naffected by events that occur after the pleading is filed ….\nRule 15(d) allows a court,” to permit a supplemental\npleading. 3 James Wm. Moore et al., Moore’s Federal\nPractice ¶ 15.30 (3d ed. 2018). Supplemental pleadings\n\n\n\n\n 8\n\fgranted the motion to supplement. Wilmington then\nresponded by moving to dismiss the supplemental complaint\nas untimely because it failed to cure the defect.\n\n Ultimately, the District Court granted Wilmington’s\ncross-motion for summary judgment for want of jurisdiction,\nwithout ruling on the City’s motion to dismiss. The Court\nfirst concluded that the initial complaint was irreparably\nunripe because both the TCA and Delaware law require the\nZBA to issue a written decision before the agency’s action\ncould be considered final, and T Mobile had thus filed its\ninitial complaint too soon. Second, the Court said that the\nsupplemental complaint could not fix the ripeness problem\nbecause it was filed past the 30-day window for seeking\nreview of the ZBA’s final action. Because the Court reached\n\n\n\nunder Rule 15(d) differ from amended pleadings made under\nRule 15(a). First, amended pleadings “relate to matters that\noccurred prior to the filing of the original pleading and\nentirely replace the earlier pleading; [supplemental pleadings]\ndeal with events subsequent to the pleading to be altered and\nrepresent additions to or continuations of the earlier\npleadings.” 6A Charles Alan Wright et al., Federal Practice\n& Procedure § 1504 (3d ed. 2018). Second “certain\namendments may be made as a matter of course within stated\ntime periods, whereas all supplemental pleadings require\nleave of court under Rule 15(d).” Id. “Parties and courts\noccasionally confuse supplemental pleadings with amended\npleadings and mislabeling is common.” Id. Here, T Mobile’s\ncomplaint was filed as an amended complaint but it is\nproperly categorized as a supplemental complaint, and we\nwill refer to it as such herein.\n\n\n\n\n 9\n\fthat determination, it found it unnecessary to conclude\nwhether T Mobile’s supplemental complaint was entitled to\nthe benefit of the relation-back doctrine under Rule 15(c).\n\n This appeal followed.\nII. DISCUSSION 5\n\n T Mobile challenges the District Court’s grant of\nsummary judgment in favor of Wilmington, contending that\nthere is jurisdiction to hear its case. It advances two\nalternative grounds for reversal: that its complaint was ripe\nbecause the ZBA’s oral decision qualifies as a “final action”\nunder the review provision of the TCA, and, in the\nalternative, that the supplemental complaint relates back to\nand cures any ripeness problem with its initial complaint.\nThose arguments in turn raise three questions for determining\nwhether the District Court’s jurisdictional ruling was proper.\nFirst, whether the oral decision of the ZBA was a final action.\nSecond, whether the timing requirement in the TCA’s review\nprovision is jurisdictional. And third, whether an untimely\n\n 5\n The District Court had jurisdiction to consider its\njurisdiction under 28 U.S.C. §§ 1331 and 1367(a), but\ndetermined the complaint contained incurable jurisdictional\ndefects and declined to reach the merits. We have jurisdiction\npursuant to 28 U.S.C. § 1291. We review all the issues\npresented in this case de novo, as they involve only legal\nissues, i.e., interpretation of a federal statute and of a Federal\nRule of Civil Procedure. Giles v. Campbell, 698 F.3d 153,\n155 (3d Cir. 2012); Viera v. Life Ins. Co. of N. Am., 642 F.3d\n407, 413 (3d Cir. 2011); DIRECTV Inc. v. Seijas, 508 F.3d\n123, 125 (3d Cir. 2007).\n\n\n\n\n 10\n\fsupplemental complaint can relate back and cure an unripe\ninitial complaint. Although we disagree with T Mobile that\nan oral decision of the ZBA qualifies as a “final action,” we\nagree that jurisdiction was proper in the District Court\nbecause the timing requirement in the TCA’s review\nprovision is non-jurisdictional, and T Mobile’s supplemental\ncomplaint therefore relates back and cures the ripeness\nproblem with the initial complaint. The District Court should\nthus have reached the merits of the dispute.\n\n A. The Oral Decision Was Not a Final Action of\n the ZBA.\n\n The ripeness of T Mobile’s initial complaint depends\nupon whether the ZBA’s oral decision was a “final action”\nwithin the meaning of the TCA. Consideration of that issue\nuncovers another: whether the TCA requires a locality to\nrender its decision in writing for that decision to qualify as a\nfinal action. The District Court held that, under both federal\nand Delaware law, only a written decision can serve as a final\naction of the ZBA. Because traditional hallmarks of agency\naction and the statutory text and structure of the TCA favor\nthat approach, we agree that only a written decision can serve\nas a locality’s final action when denying an application.\n\n In Delaware Riverkeeper Network v. Secretary\nPennsylvania Department of Environmental Protection,\n(Riverkeeper III), we determined that, when reviewing\nfinality under the Natural Gas Act, “[a]lthough the\ndecisionmaking process we are reviewing is defined by [state]\nlaw, we nevertheless apply a federal finality standard to\ndetermine whether Congress has made the results of that\nprocess reviewable[.]” 903 F.3d 65, 72 (3d Cir. 2018). The\n\n\n\n\n 11\n\fsame reasoning holds true here, since, for the TCA just as for\nthe Natural Gas Act, “the finality requirement itself, along\nwith the presumption that Congress intended us to apply it,\nare creatures of federal, not state, law.” Id. at 71.\n\n Under federal law, not all agency determinations are\nfinal actions. Bacon v. Sullivan, 969 F.2d 1517, 1519 (3d Cir.\n1992). Final agency actions bear certain “traditional\nhallmarks” that demonstrate “[t]here is nothing left for the\nagency to do[,]” Del. Riverkeeper Network v. Sec’y of Pa.\nDep’t of Envtl. Prot., (Riverkeeper II), 870 F.3d 171, 178 (3d\nCir. 2017). We noted those hallmarks on an earlier occasion\nwhen we said that, “[f]inal agency action must mark the\nconsummation of the agency’s decisionmaking process, must\nnot be of a merely tentative or interlocutory nature, and must\nbe one by which rights or obligations have been determined,\nor from which legal consequences will flow.” Riverkeeper\nIII, 903 F.3d at 72, 75 (citation and internal quotation marks\nomitted).\n\n To decide what the TCA requires for finality, we\nbegin, of course, with the text. See, e.g., Ross v. Blake, 136 S.\nCt. 1850, 1856 (2016) (“Statutory interpretation … begins\nwith the text[.]”) Here, the statutory text makes it clear that,\nif a denial is not in writing, there is something left for the\nagency to do. The denial provision of the TCA states that\n“[a]ny decision … to deny … shall be in writing and\nsupported by substantial evidence contained in a written\nrecord.” 47 U.S.C. § 332(c)(7)(B)(iii). We see no reason\nwhy the same should not be true for actions besides denial, 6\n\n 6\n For instance, it is not apparent why community\nmembers aggrieved by a decision to grant some permit to a\n\n\n\n\n 12\n\fbut we need not decide that today. It is enough to say that, in\nthose zoning decisions governed by the TCA, a locality’s oral\ndeclaration of a denial is “of a merely tentative or\ninterlocutory nature.” Riverkeeper III, 903 F.3d at 72\n(citation omitted) (speaking in reference to the Natural Gas\nAct); cf. Athens Cellular, Inc. v. Oconee Cty., 886 F.3d 1094,\n1104-05, 1107 (11th Cir. 2018) (noting that a zoning board\ncould have approved the minutes, revised them, or rejected\nthem, and thus until the board approved the minutes its\ndecision was not final).\n\n Moreover, an oral decision is not an action from which\nlegal consequences flow. Federal law governs finality, but\nDelaware’s procedures still matter, and the Delaware\nSuperior Court has concluded that a written document must\nbe filed for a ZBA action to be final. McDonald’s Corp. v.\nZoning Bd. of Adjustment for the City of Wilmington, No.\nCIV. A. 01A-05-011CG, 2002 WL 88944, at *1 (Del. Super.\nCt. Jan. 10, 2002). The court reasoned that Section 328 of\nTitle 22 of the Delaware Code, the section that governs\nappeals from ZBA proceedings, requires a written document\nto be filed because the statute “provides that [s]uch petition\nshall be presented to the Court within 30 days after the filing\nof the decision in the office of the board.” Id. (internal\nquotation marks omitted). That reasoning is persuasive and\n\n\n\n\nwireless provider, assuming those members have standing to\nsue, would not be equally entitled to a zoning authority’s\nwritten decision before the time limit in the TCA’s review\nprovision is triggered.\n\n\n\n\n 13\n\fshows that, under Delaware law, the ZBA’s oral decision is\nwithout legal consequences. 7\n\n There are distinct policy advantages to forestalling\njudicial scrutiny until a written denial is issued. Requiring a\nwritten decision focuses review on a particular, documented\nstatement of reasons. See USCOC of Greater Mo. v. City of\nFerguson, 583 F.3d 1035, 1042 (8th Cir. 2009) (“Because the\nwritten decision is the central object of our scrutiny under the\nTCA, the process of judicial review is best served by delaying\nthe ripening of a TCA claim until the local authority has\nissued its written decision.”). It also prevents ambiguity with\nrespect to when a claim can be brought. As the District Court\nhere stated, to hold otherwise “would promote a pernicious\nambiguity as to when that short period of time begins to run.”\n(App. at 7.) And it promotes uniformity of federal procedures\nby clarifying when, across all jurisdictions, an action becomes\nfinal.\n\n 7\n T Mobile cites to a different opinion, Schmalhofer v.\nBoard of Adjustment of Newark, to advance a contrary\nposition. No. C.A. 99A-05-010-WTQ, 2000 WL 703510\n(Del. Super. Ct. May 9, 2000). Schmalhofer states in a\nfootnote that “a written decision is not required or expressly\ncontemplated by this section.” Id. at *3 n.3. But T Mobile is\nstretching the Schmalhofer court’s language too far. In that\ncase, the City of Newark had issued a verbatim transcript of\nthe hearing, so there was a writing. Id. at *3; see infra note\n11. There is no indication of any written decision in this case,\nprior to December 22, 2016, when the City issued the written\ndenial bearing the date of December 21, 2016.\n\n\n\n\n 14\n\f The Supreme Court’s decision in T-Mobile South, LLC\nv. City of Roswell, Georgia, also adds support to the\nconclusion that only a written denial can constitute final\naction, triggering a party’s right to review. 135 S. Ct. 808\n(2015). In that case, the Court held that the “substantial\nevidence” supporting a locality’s decision to deny must be\nreleased contemporaneously with the written decision to\ndeny. 8 Id. at 811-12. In doing so, the Court tied together a\nlocal zoning authority’s final action, which triggers judicial\nreview, and its decision to deny, which must be in writing.\nIndeed, the Supreme Court said in no uncertain terms that,\n“[t]he relevant ‘final action’ [in that case, was] the issuance of\nthe written notice of denial[.]” Id. at 817 n.4. The Court\nlinked the locality’s decision to deny to the 30-day time limit\nto file a complaint after a final action has been taken. Id. at\n817 (“Only once the denial is issued would the 30-day\ncommencement-of-suit clock begin.”); id. at 813 (“[N]ow 29\ndays after the City denied petitioner’s application—petitioner\nfiled suit in Federal District Court.”).\n\n The Court went on to discuss timing, saying, “the\nlocality must provide or make available its written reasons at\nessentially the same time as it communicates its denial[,]”\n“[b]ecause an entity may not be able to make a considered\n\n 8\n The Court was interpreting the denial provision,\nwhich, as we noted earlier, states that, “[a]ny decision by a\nState or local government or instrumentality thereof to deny a\nrequest to place, construct, or modify personal wireless\nservice facilities shall be in writing and supported by\nsubstantial evidence contained in a written record.” 47\nU.S.C. § 332(c)(7)(B)(iii), City of Roswell, 135 S. Ct. at 811.\n\n\n\n\n 15\n\fdecision whether to seek judicial review without knowing the\nreasons for the denial of its application, and because a court\ncannot review the denial without knowing the locality’s\nreasons[.]” Id. at 816. The majority opinion was critical of\nthe dissent for attempting to “fashion a world in which a\nlocality can wait until a lawsuit is commenced and a court\norders it to state its reasons[,] … [leaving the challenging\nentity to] risk being sandbagged by the written reasons that\nthe locality subsequently provides in litigation after the\nchallenging entity has shown its cards.” Id. at 816 n.3. That\ncritique is premised on the written decision being the final\naction that starts the 30-day time limit for commencing suit. 9\n\n The Supreme Court anticipated that localities might\nneed to delay issuing a written denial if they are not ready to\nrelease their substantial reasons. See id. at 817 (noting that\n\n 9\n T Mobile asserts that Wilmington has a “pattern and\npractice of not issuing a written decision of land use denials\nunless or until the City is sued.” (Opening Br. at 7.) But if\nonly a written denial is a final action, the shot clock requires\nthe City to issue that written decision within a given time\nperiod. 24 FCC Rcd. 13994, 14012 (2009). T Mobile also\nasserts that when a locality has a pattern and practice of not\nreleasing written decisions, that practice delays the overall\nprocess, since a cellular service provider would be required to\ninitiate two causes of action: one to compel a written decision\nand another to challenge that written decision. That,\nhowever, is precisely what Congress envisioned by providing\nseparate remedies for a failure to “act” within a reasonable\ntime period and for an improper denial. 47 U.S.C.\n§ 332(c)(7)(B)(iii).\n\n\n\n\n 16\n\f“[i]f a locality is not in a position to provide its reasons\npromptly, the locality can delay the issuance of its denial\nwithin this 90– or 150–day window, and instead release it\nalong with its reasons once those reasons are ready to be\nprovided.”). That further counsels against treating an oral\ndetermination as a final action since, if an oral determination\nis deemed a final action, localities will be unable to take\nadvantage of the permissible delay afforded by the shot clock\nfor publishing their reasoning.\n\n Two of our sister courts of appeals agree that only a\nwritten decision can constitute final action. The Eighth\nCircuit in USCOC of Greater Missouri v. City of Ferguson\nstated that “[t]he plain language of the TCA indicates that\n‘final action’ does not occur until issuance of a written\ndecision.” 583 F.3d at 1041. The Eleventh Circuit in\nPreferred Sites LLC v. Troup County likewise held a\ncomplaint to be timely when it was filed within 30 days of a\nwritten decision, even though it was filed more than 30 days\nafter an oral decision. 10 296 F.3d 1210, 1217-18 (11th Cir.\n\n 10\n T Mobile attempts to distinguish Preferred Sites by\nstating that, unlike here, the case did “not address a city that\ndoes not issue a written decision close in time to when it\nmakes the decision to deny.” (Opening Br. at 37.) But that\nargument is irrelevant to whether the statutory text requires a\nwriting for an agency decision to be final. T Mobile also cites\nto Preferred Sites to argue that it should not matter if there is\na writing requirement since the oral denial could be seen as\nakin to a court announcing a decision. It explains that “when\nan appeal is filed after the court announces a decision, but\nbefore the entry of the judgment, it is treated as being filed on\nthe date of entry.” (Opening Br. at 28-29 (citing Preferred\n\n\n\n\n 17\n\f2002) (concluding that, “[b]ased on the plain language of the\nstatute,” that “a ‘final action’ occurs when the state or local\nauthority issues its written decision. The statute expressly\nmandates a … decision … committed to writing. Until the\nstate or local authority issues its written notification, its task\nunder the statute is not complete.”). No circuit has held\notherwise.\n\n Persuasive authority thus indicates that any action, and\ncertainly a denial, must be in writing to be final. But, there is\nanother possible interpretation of the statutory text. The\nwords “shall be in writing” could be read not as a condition of\nfinality, but instead as a simple directive to state and local\ngovernments to place their final action in writing. “The TCA\nprovides no express answer to … when a local government’s\npermitting decision becomes a ‘final action,’ which starts the\nthirty-day clock.” Athens Cellular, 886 F.3d at 1102-03. The\nstatute only states that denials must be in writing. 47 U.S.C.\n§ 332(c)(7)(b)(iii). Decisions to grant are not limited in the\nsame way. Id. And, Congress used the words “decision to\ndeny” in one statutory subsection and “final action” in\nanother, which could evince an intent to give those terms\ndifferent meanings. As the Supreme Court has “recognized\n… Congress’s use of certain language in one part of the\nstatute and different language in another can indicate that\ndifferent meanings were intended.” Sebelius v. Auburn Reg’l\nMed. Ctr., 568 U.S. 145, 156 (2013) (citation and quotation\n\n\n\nSites, 296 F.3d at 1217 n.7).) That analogy did appear in\nPreferred Sites, but it was only contained in a footnote. No\nother court has followed that line of reasoning, and we\ndecline to follow it here.\n\n\n\n\n 18\n\fmarks omitted). Thus, it could be argued, if Congress wanted\nto mandate a writing for zoning denials to constitute final\naction, it could have been more explicit, providing, for\ninstance, that a “decision must be in writing to qualify as a\nfinal action.”\n\n But, of course, one can almost always fault legislative\ndrafting, like other kinds of writing, after the fact. That\nsomething might have been said even more clearly does not\nmean it is not clear enough. So, “[r]ather than expecting (let\nalone demanding) perfection in drafting,” we can “construe[]\nstatutes to have a particular meaning even as we\nacknowledge[] that Congress could have expressed itself\nmore clearly.” Torres v. Lynch, 136 S. Ct. 1619, 1633\n(2016).\n\n The text and structure of the statute, Delaware\nprocedures, Supreme Court reasoning, our sister circuits’\ndecisions, and policy arguments all support the conclusion\nthat a writing is in fact a requirement for a denial to be final. 11\nIn light of that conclusion, the ZBA’s oral determination on\n\n 11\n What constitutes a “writing” has some flexibility,\nthough. See, e.g., Omnipoint Holdings, Inc. v. City of\nSouthfield, 355 F.3d 601, 605-07 (6th Cir. 2004) (approving\nminutes by written resolution was a final action that bound\nthe parties). In City of Roswell, for example, the Supreme\nCourt indicated that minutes of an oral meeting could be\nsufficient. 135 S. Ct. at 816. Here, however, there is no\nevidence that the ZBA’s oral determination was noted in the\nminutes of the October 26th meeting and issued by the City as\nits formal decision.\n\n\n\n\n 19\n\fOctober 26, 2016, was not a final action ripe for judicial\nreview. Therefore, as that oral determination was not reduced\nto writing until December 22, 2016, preceding the filing of\nT Mobile’s initial complaint, that complaint’s cause of action\nwas not ripe.\n\n\n\n\n 20\n\f B. No Separate Time Limit Exists Following an\n Oral Determination.\n\n As an alternative to its argument that the ZBA’s oral\ndecision was a final action, T Mobile asks us to consider\nwhether a “local government must issue the ‘writing’ close in\ntime to the ‘decision … to deny’ to establish a ‘final action’\nthat will be subject to expedited review.” 12 (Opening Br. at\n41.) Essentially, T Mobile is asserting that the “shot clock”\ngoverning the time to act, which allows a wireless carrier to\nsue for a locality’s failure to act, is insufficient, and that a\nnew requirement, albeit not in the statute, should be imposed\non localities. Under T Mobile’s proposed rule, an oral\ndecision would have to be reduced to writing within a\nspecified time period. That argument assumes that an oral\ndetermination can serve to satisfy the requirement to “act” on\na request within the limits of the shot clock, and that, without\na separate judicially created time limit, there would be no\ndeadline for the locality to release its written decision to deny,\ndespite City of Rowell’s contemporaneous writing\nrequirement. Because we conclude that a denial must be in\nwriting to be a final action, the issuance of that writing is the\ngovernment “act” ruled by the shot clock. 13 Aside from the\n\n 12\n Wilmington argues that T Mobile has waived that\nissue, but we need not address that argument because we\nconclude that no such requirement exists.\n 13\n Again, the Supreme Court held in City of Roswell\nthat a locality’s decision to deny must be accompanied by\nsubstantial reasons. 135 S. Ct. at 811-12. Otherwise, if a\nlocality were able to withhold its reasoning for its decision,\nthose aggrieved by the locality’s actions would “be left to\n\n\n\n\n 21\n\ftime limits associated with the “shot clock,” there is no other\ndeadline governing the issuance of a written decision\nfollowing an oral determination. 47 U.S.C. § 332(c)(7)(b).\nAny time limit we fabricated would be inappropriate.\n\n T Mobile argues that, without a requirement for\nlocalities to issue a written decision within a set amount of\ntime following an oral determination, wireless carriers are left\n“to wait until the FCC ‘shot clock’ expires – which could be\n90 or 150 days depending on the type of installation involved\n– and then [to] file an action alleging that the City has failed\nto act in a reasonable time[.]” (Opening Br. at 45.) It also\ncontends that a “failure to act” lawsuit is insufficient because\nthe remedy for a successful suit is simply an order telling the\nCity to issue a written decision. In T Mobile’s view, forcing\nwireless providers to sue both to compel a written decision\nonce the shot clock is violated and again to contest the written\ndecision serves only to “create yet further delay.” (Opening\nBr. at 46.)\n\n\n\n\nguess at what the locality’s written reasons will be, write a\ncomplaint that contains those hypotheses, and risk being\nsandbagged by the written reasons that the locality\nsubsequently provides in litigation after the challenging entity\nhas shown its cards.” Id. at 816 n.3. If an applicant cannot\nfile suit, however, because the locality’s “final action” has not\nyet occurred, those concerns vanish. The ZBA’s decision\nhere, when reduced to writing, was both its decision to deny\nand its final action.\n\n\n\n\n 22\n\f Those concerns are overstated and, in any case,\nirrelevant. The shot clock begins to run once a wireless\nprovider files its application, so it is already ticking before\nany oral decision is made. If the locality fails to meet that\ndeadline by not issuing a written decision before the shot\nclock expires, the wireless provider can bring a claim for a\n“failure to act.” 14 24 FCC Rcd. 13994, 14012 (2009). T\nMobile asserts that requiring a separate failure-to-act suit, in\naddition to a suit on the merits, undercuts the statutory\npurpose of expedited judicial review, particularly in cases\nwhere the locality has a “pattern and practice of not issuing a\nwritten decision of land use denials unless or until [it] is\nsued.” (Opening Br. at 7.) But the statute’s own remedies\ncannot possibly undercut its purpose. A separate failure-to-\nact claim is the very remedy Congress chose for shot clock\nviolations. 24 FCC Rcd. 14013 at ¶ 4 (2009). Whether or not\nT Mobile likes that policy choice, it is the one Congress\nmade, and we are not free to change it.\n\n C. The Timing Requirement Is Not\n Jurisdictional.\n\n Because we hold that a writing is required for a denial\nto constitute a final action, T Mobile’s initial complaint was\nnot ripe for review when filed. And, T Mobile’s\nsupplemental complaint was filed more than 30 days after the\nZBA issued its written decision and was therefore untimely\nunder the TCA’s review provision. 47 U.S.C.\n§ 332(c)(7)(B)(v). Thus, the District Court only had\njurisdiction if T Mobile’s supplemental complaint cured the\n\n 14\n It is not clear which time limit would have applied in\nthis case and whether it would have been violated.\n\n\n\n\n 23\n\fripeness flaw in its initial complaint by relating back to the\noriginal filing date. If the 30-day time limit in the TCA’s\nreview provision is nonjurisdictional, we can safely say that\nrelation back is possible and allows a supplemental complaint\nto cure a defective premature filing. 15 At the outset, then, we\nmust determine whether that 30-day time limit is\njurisdictional, being mindful both of the Supreme Court’s\ncounsel to exercise caution before holding timing\nrequirements to be jurisdictional and of its guidance regarding\nwhat constitutes a jurisdictional limit. 16 Sebelius, 568 U.S. at\n149, 153-54. Caution is indeed warranted because statutes of\nlimitations and other filing deadlines “ordinarily are not\njurisdictional.” Id. at 154; see also United States v. Kwai Fun\nWong, 135 S. Ct. 1625, 1632 (2015) (“[M]ost time bars are\nnonjurisdictional.”).\n\n\n 15\n We do not reach the issue of whether an unripe\ncomplaint can be cured by a supplemental or amended\npleading over which the Court lacked jurisdiction.\n 16\n The City claims that our decision in Nextel Partners\nInc. v. Kingston Township, 286 F.3d 687 (3d Cir. 2002) is\neffectively determinative. Not so. In Kingston Township,\nthen-Judge Alito noted that the District Court had held the\ntiming requirement in the TCA’s review provision was\njurisdictional. Id. at 695. But we did not address whether\nthat determination was correct, nor did we rely on it. Instead,\nwe concluded that there could be no “failure to act” towards\nan application that was not submitted. Id. at 692. Since our\ndecision in that case, the Supreme Court has clarified the\nprocess for determining if a time limit is jurisdictional.\nSebelius, 568 U.S. at 149.\n\n\n\n\n 24\n\f “[T]o ward off profligate use of the term ‘jurisdiction,’\n[the Supreme Court has] adopted a readily administrable\nbright line for determining whether to classify a statutory\nlimitation as jurisdictional.” Sebelius, 568 U.S. at 153 (citing\nArbaugh v. Y & H Corp., 546 U.S. 500, 516 (2006))\n(quotation marks omitted). We are to ask “whether Congress\nhas clearly state[d] that the rule is jurisdictional; absent such a\nclear statement, we … should treat the restriction as\nnonjurisdictional in character.” Id. (alteration in original)\n(citation and quotation marks omitted); see also Musacchio v.\nUnited States, 136 S. Ct. 709, 716 (2016) (Thus, “[w]e treat a\ntime bar as jurisdictional only if Congress has ‘clearly stated’\nthat it is.”). In deciding whether Congress has made such a\nclear statement, “we evaluate the ‘text, context, and relevant\nhistorical treatment.’” United States v. Kalb, 891 F.3d 455,\n460 (2018) (quoting Reed Elsevier, 559 U.S. 154, 166\n(2010)).\n\n Referencing that last test, Wilmington asserts that\n“[s]ection 332’s statutory grant of jurisdiction to district\ncourts, the text of the statute, the placement of the filing\nwindow in that same section, and the well-established\ntreatment of the filing window as jurisdictional, [all\ndemonstrate] that the filing window is jurisdictional.”\n(Answering Br. at 15.) We disagree. The differences\nbetween the review provision’s timing requirement and the\ntiming requirement we held to be jurisdictional in Kalb, and\nthe similarities between the review provision’s timing\nrequirements and those at issue in Sebelius and Musacchio,\nwhich the Supreme Court held to be nonjurisdictional,\nactually support treating the timing requirement in the TCA’s\nreview provision as nonjurisdictional.\n\n\n\n\n 25\n\f First, although Wilmington says that the text of the\nstatute indicates Congress’s desire to make the 30-day timing\nrequirement jurisdictional, the text does not use the term\n“jurisdictional” or any variation of it to describe the timing\nrequirement. 47 U.S.C. § 332(c)(7)(B)(v). To the contrary,\nthe statute uses permissive rather than mandatory language.\nUnlike the timing requirement we held to be jurisdictional in\nKalb, which mandated that an action would be barred if not\nfiled in time, the TCA’s review provision states that an action\n“may” be filed within 30-days. Compare Kalb, 891 F.3d at\n460 with 47 U.S.C. § 332(c)(7)(B)(v). The language is much\ncloser to that which the Supreme Court decided was\nnonjurisdictional in Sebelius. The statute at issue in that case,\nlike the review provision here, uses a permissive phrase –\n“may obtain a hearing” – before it states the timing\nrequirement. 17 Compare Sebelius, 568 U.S. at 154, with 47\nU.S.C. § 332(c)(7)(B)(v) (“may … commence an action”).\nSimilar to the timing requirement the Supreme Court held to\nbe nonjurisdictional in Musacchio, the review provision does\nnot confer jurisdiction, instead it allows an action to be\n\n 17\n T Mobile also points to Henderson v. Shinseki,\nwhich held a timing requirement to be nonjurisdictional even\nthough it used the mandatory “shall” before stating the timing\nrequirement. 562 U.S. 428, 441-42 (2011). But the decision\nin Shinseki, where the pertinent timing requirement could\nhave barred a veteran’s appeal, was partly based on “the\ncanon that provisions for benefits to members of the Armed\nServices are to be construed in the beneficiaries’ favor,” and\nso it is of less utility in deciding this dispute. Id. at 441\n(quotation marks and citations omitted).\n\n\n\n\n 26\n\fcommenced “in any court of competent jurisdiction.” See\nMusacchio, 136 S. Ct. at 717 (“[The provision] does not\nexpressly refer to subject-matter jurisdiction or speak in\njurisdictional terms.”). The text of the statute therefore favors\na holding that the timing requirement is nonjurisdictional.\n\n Wilmington next contends that the context of the\ntiming requirement favors the view that the requirement is\njurisdictional, because the Supreme Court has stated that it is\n“inextricably linked to … the language that creates the right\nof action[.]” (Answering Br. at 13-14 (citing City of Rancho\nPalos Verdes v. Abrams, 544 U.S. 113, 125 (2005)).) Thus,\nsays the City, the “filing window created by [the review\nprovision] is jurisdictional [because] it is integral to the\nexpress purpose of the section, to this Court’s jurisdiction,\nand to the parties’ rights and obligations[.]” (Answering Br.\nat 8.)\n\n True enough, the review provision’s timing\nrequirement does appear in the same subsection as the\nstatutory text granting jurisdiction. 47 U.S.C.\n§ 332(c)(7)(B)(v). And, as we stated in Kalb, the Supreme\nCourt’s decisions in Bowles v. Russell, 551 U.S. 205, 210\n(2007), and Reed Elsevier, Inc. v. Muchnick, 559 U.S. at 166,\nboth found the source of the timing requirement to be\nimportant in determining whether that requirement was\njurisdictional. 891 F.3d at 462. In Kalb, moreover, we made\nthe same point the City now does, stating that a timing\nrequirement was jurisdictional because “the thirty-day appeal\nperiod here is embedded in the same statutory section that\ngrants jurisdiction to the court of appeals.” Id.\n\n\n\n\n 27\n\f But the location of the timing requirement within the\nstatutory structure, without more, does not clearly reveal\nCongressional intent. As noted by the Supreme Court in\nSebelius, a timing requirement should not be classified as\njurisdictional solely based on its placement in a jurisdictional\nprovision. Sebelius, 568 U.S. at 155 (“A requirement we\nwould otherwise classify as nonjurisdictional … does not\nbecome jurisdictional simply because it is placed in a section\nof a statute that also contains jurisdictional provisions.”\n(citing Gonzalez v. Thaler, 565 U.S. 134, 146-47 (2012))). In\nMusacchio too, the Supreme Court held that a timing\nrequirement was nonjurisdictional despite its presence in the\njurisdiction-granting section of the statute at issue. 136 S. Ct.\nat 717. The Court emphasized that the statute did not directly\nspeak of the timing requirement as jurisdictional, despite its\nmandatory language. Id. That reasoning applies with at least\nequal force here, so the context of the review provision’s\ntiming requirement does not make the requirement\njurisdictional.\n\n Finally, Wilmington asserts that the timing\nrequirement is jurisdictional because of the historical\ntreatment of similar provisions. The City asserts that the\nphrase “within 30 days after” creates a “window,” during\nwhich a complaint must be filed, and not a “deadline.”\n(Answering Br. at 11-12 (citing W. Union Tel. Co. v. FCC,\n773 F.2d 375, 377 (D.C. Cir. 1985)) (noting that “within 60\ndays after” creates a 60-day filing window while “no later\nthan 60 days after” creates a filing deadline).) But that\nargument misses the point because it goes to whether the rule\nbars suit between certain dates or only after a certain date, not\nto whether the timing requirement is jurisdictional. See, e.g.,\nUnion Tel. Co., 773 F.2d at 377-78 (discussing whether the\n\n\n\n\n 28\n\ffiling window is a jurisdictional bar for suits filed before the\nwindow opens). And just because a complaint may be unripe\nbefore a particular date does not mean that a deadline by\nwhich suit must be filed is jurisdictional. As we stated in\nKalb, the Supreme Court’s decisions in Bowles and Reed\nElsevier both looked to “the Court’s prior treatment of\n[similar timing requirements.]” Kalb, 891 F.3d at 460. In\nSebelius, the timing requirement, as here, used the phrase\n“within” and thus, under Wilmington’s logic, it would have\nbeen a jurisdictional limit. Sebelius, 568 U.S. at 154. But the\nSupreme Court held otherwise, id., and that is of high\nimportance.\n\n Because the text and context of this statute, and\nhistorical treatment of timing requirements in similar statutes,\ndo not reveal a clear intent from Congress to make the review\nprovision’s timing requirement jurisdictional, we conclude\nthat it is not. 18\n\n D. Rule 15 Allows a Supplemental Complaint\n Filed After a Claims Processing Deadline To\n Relate Back and Cure an Unripe Initial\n Complaint.\n\n We next consider whether an untimely supplemental\ncomplaint can, by relating back, cure an initial complaint that\nwas unripe. We believe it can, and because T Mobile’s\n\n 18\n That conclusion is further supported by the\nthoughtful concurrence in Athens Cellular, concluding after\nSebelius that the timing requirement “imposed by Congress in\nthe TCA … is not a jurisdictional bar.” Athens Cellular, 886\nF.3d at 1113 (Kaplan, J. concurring).\n\n\n\n\n 29\n\fmotion to supplement its complaint was properly granted, that\nsupplemental complaint relates back and is ripe. The District\nCourt therefore had jurisdiction and should not have granted\nWilmington’s motion for summary judgment.\n\n At the outset, we note that the parties do not dispute,\nand we agree, that the District Court was within its discretion\nto grant T Mobile’s motion to supplement its complaint.\nPursuant to Federal Rule of Civil Procedure 15(d), “[o]n\nmotion and reasonable notice, the [district] court may, on just\nterms, permit a [moving] party to serve a supplemental\npleading setting out any … event that happened after the date\nof the pleading to be supplemented.” Fed. R. Civ. P. 15(d);\nsee also 3 James Wm. Moore et al., Moore’s Federal Practice\n¶ 15.30 (3d ed. 2018) (“Supplemental pleadings … are\nlimited to subsequent events related to the claim or defense\npresented in the original pleading.”). Here, the District Court\nrightly granted T Mobile’s motion to supplement. That\ndecision was just, since Wilmington had long since had notice\nof the event – the filing of the written denial – that occurred\nafter the initial pleading. After all, the City issued that denial,\nand the denial was featured in the parties’ discovery plan.\nThe issuance of it was also plainly related to T Mobile’s\ninitial complaint.\n\n That the initial complaint was premature is not a bar\nsince, under Rule 15(d), “[t]he court may permit\nsupplementation even though the original pleading is\ndefective in stating a claim for relief or defense.” Fed. R.\nCiv. P. 15(d). As the Advisory Committee Notes make clear,\n“Rule 15(d) is intended to give the [district] court broad\ndiscretion in allowing a supplemental pleading.” Fed. R. Civ.\nP. 15(d) advisory committee’s note to 1963 amendment. It is\n\n\n\n\n 30\n\ffurthermore “within the discretion of the court to allow a\nsupplemental pleading to be filed at any stage of the case[.]”\nMoore et al., supra, ¶ 15.30. The District Court here was thus\nwell within its discretion in granting T Mobile’s motion to\nsupplement the complaint.\n\n Rule 15 does not indicate whether or under what\ncircumstances a supplemental pleading can relate back to the\ndate of the original pleading to avoid the effect of a time\nlimit. 6A Charles Alan Wright et al., Federal Practice &\nProcedure § 1508 (3d ed. 2018). Subsection (c) of the Rule,\nwhich provides for the relation back of amended pleadings,\ndoes not specifically refer to supplemental pleadings. Fed. R.\nCiv. P. 15(c). Nor does Rule 15(d) make any mention of\nrelation back. Fed. R. Civ. P. 15(d). But case law and\nsecondary sources have long instructed that once a\nsupplemental complaint is granted, it is treated like an\namended complaint for purposes of relation back. 19 Thus,\neven though Rule 15(d) is in a separate statutory provision\nfrom Rule 15(c), a supplemental complaint can relate back.\nWright et al., supra, § 1508; see also F.D.I.C. v. Knostman,\n966 F.2d 1133, 1138 (7th Cir. 1992) (“The distinction\nbetween an amended pleading and a supplemental pleading is\n\n 19\n Courts have generally held that a supplemental\ncomplaint is eligible for relation back, but rely on different\nrationales to do so. See Wright et al., supra, § 1508 (“[S]ome\ncourts have held that for purposes of applying the relation-\nback doctrine a supplemental pleading may be treated as an\namended pleading under Rule 15(c); other courts have\napplied the relation-back principle directly to supplemental\npleadings even though Rule 15(d) does not mention it.”)\n(internal citations omitted).\n\n\n\n\n 31\n\foften disregarded for purposes of relation back under Rule\n15(c).”); Russell v. New Amsterdam Cas. Co., 303 F.2d 674,\n680-81 (8th Cir. 1962) (finding supplemental pleading related\nback despite plaintiff suing in the wrong capacity and not\nachieving appropriate status for diversity jurisdiction until\nafter the limitations period had expired). That stands to\nreason, since, if a “defendant had notice of the subject matter\nof the dispute and was not prejudiced in preparing a defense\n…[,] the policy against stale claims becomes subsidiary to the\npolicy expressed throughout the rules in favor of allowing a\nparty to set forth all the grievances against another party in\none action and resolving them on their merits.” Wright et al.,\nsupra, § 1508.\n\n So a pleading filed according to Rule 15(d) can relate\nback, assuming it meets “the basic test for relation back\nprescribed by Rule 15(c).” Id.; see also Moore et al., supra,\n¶ 15.30 (“A supplemental pleading may relate back to the\ndate of the original complaint if the requirements under Rule\n15(c) for relation back are satisfied”); Davis v. Piper Aircraft\nCorp., 615 F.2d 606, 609 n.3 (4th Cir. 1980) (supplemental\npleading relates back if Rule 15(c)’s test is met). In fact, as\nthe District Court observed, if a supplemental complaint\nmeets the requirements for relation back then “[r]elation back\nis mandatory,” and not subject to additional equitable\nconsiderations. 20 (App. at 6 (citing Arthur v. Maersk, Inc.,\n434 F.3d 196, 202-03 (3d Cir. 2006)).)\n\n 20\n We note, however, that “[a] party opposing the\nintroduction of a supplemental pleading might wish to raise\nthe statute-of-limitations defense when the additional\npleading (1) alleges new matter that brings the earlier\npleading up to date; (2) cures a defect in the original pleading;\n\n\n\n\n 32\n\f Looking then to Rule 15(c), a complaint “relates back\nto the date of the original pleading when … [it] asserts a\nclaim or defense that arose out of the conduct, transaction, or\noccurrence set out -- or attempted to be set out -- in the\noriginal pleading[.]” Fed. R. Civ. P. 15(c)(1)(B). The\nDistrict Court here concluded that there was no need to\ndetermine whether T Mobile’s supplemental complaint\nrelated back, because, even if it did, “it fail[ed] to cure the\ndeficiencies of the initial complaint[.]” (App. at 8.) But\ngiven our view that the supplemental complaint could indeed\ncure the ripeness problem with the initial complaint, we must\ncontend with the relation-back question.\n\n To determine if relation back is proper, the only issue\nis whether there is a “common core of operative facts in the\ntwo pleadings.” Bensel v. Allied Pilots Ass’n, 387 F.3d 298,\n310 (3d Cir. 2004.) Here, that test is met. Both complaints\nrely on the same core facts. The written denial was a\ncertification and restatement of the earlier oral denial.\n\n Thus, the only question remaining is whether a\ncomplaint that relates back can cure an untimely initial\ncomplaint, and the answer is yes. The clear preference\nembodied in Rule 15 is for merits-based decision making. Cf.\nMoore et al., supra, ¶ 15.30 (“The same principles that\nsupport the liberal amendment of pleadings also apply to\nsupplemental pleadings.”). As the Supreme Court has stated,\nthe purpose of Rule 15 is “to balance the interests of the\n\n\nor (3) states a new claim that arose after the filing of the\ncomplaint.” Wright et al., supra, § 1508.\n\n\n\n\n 33\n\fdefendant protected by the statute of limitations with the\npreference expressed in the Federal Rules of Civil Procedure\nin general, and Rule 15 in particular, for resolving disputes on\ntheir merits.” Krupski v. Costa Crociere S.p.A., 560 U.S. 538,\n550 (2010). The requirements of Rule 15 itself protect\ndefendants from an unfair relation back. 21 Under that Rule,\ncourts “look[s] to whether the opposing party has had fair\nnotice of the general fact situation and legal theory upon\nwhich the amending party proceeds.” Bensel, 387 F.3d at\n310. In this instance, Wilmington had sufficient notice since\nthe supplemented complaint simply alleged the issuance of\nthe ZBA’s written denial. And, of course, Wilmington had\nnotice of everything in the supplemental complaint. It not\nonly knew of the written denial and the reasons given, it\ngenerated them.\n\n Relation back has been allowed to address\njurisdictional problems. We said in Berkshire Fashions, Inc.\nv. M.V. Hakusan II that relation back may be used to cure\ndefects in jurisdictional allegations. 954 F.2d 874, 878 (3rd\nCir. 1992). In that case, the District Court had dismissed the\nplaintiff’s claim based on admiralty jurisdiction and denied\nthe plaintiff’s motion to amend its complaint to allege\ndiversity jurisdiction. Id. at 877. We concluded that both\ndecisions were in error, holding that an amended complaint\nrelates back and can cure insufficient pleading of subject\nmatter jurisdiction. Id. at 878. Recently, our Circuit allowed\n\n 21\n This is not a pass for endless delay in\nsupplementing a complaint. Indeed, we have endeavored to\nemphasize that whether to allow supplemental pleading\ndepends on equitable considerations of fairness and notice\nthat district courts must take into account.\n\n\n\n\n 34\n\fa plaintiff to cure a diversity defect when the case had been\nlitigated for years. See GBForefront, L.P., v. Forefront\nMgmt. Grp., LLC, 888 F.3d 29, 32 (3d Cir. 2018)\n(“instruct[ing] the [d]istrict [c]ourt to give leave to further\namend the complaint … to cure defective jurisdictional\nallegations”).\n\n Other circuits have held the same. See Woods v. Ind.\nUniv.-Purdue Univ. at Indianapolis, 996 F.2d 880, 884 (7th\nCir. 1993) (“Consistent with its history and purpose, Rule\n15(c) has uniformly been applied to relate back [filings] that\ncure defective statements of jurisdiction ….”); Boyce v.\nAnderson, 405 F.2d 605, 607 (9th Cir. 1968) (allowing\namendment alleging that no previous appeal had been taken\nto the United States Court of Customs and Patent Appeals to\ncure jurisdictional defect in complaint after statute of\nlimitations had expired). That conclusion is also consistent\nwith 28 U.S.C. § 1653, which allows “[d]efective allegations\nof jurisdiction [to] be amended, upon terms, in the trial or\nappellate courts.” Id.\n\n Courts have similarly permitted cure of actual defects\nin the court’s jurisdiction, going beyond just jurisdictional\nallegations. For instance, although not in a case involving a\nlater complaint, the Supreme Court has said that a court can\ndrop a dispensable non-diverse party to cure a defect in\ndiversity jurisdiction. Newman-Green, Inc. v. Alfonzo-\nLarrain, 490 U.S. 826, 837-38 (1989); see also E.R. Squibb &\nSons, Inc. v. Lloyd’s & Cos., 241 F.3d 154, 163 (2d Cir.\n2001) (stating that, “where it is appropriate to relate back an\namendment to a pleading under Rule 15, jurisdiction is\nassessed as if the amendment had taken place at the time the\ncomplaint was first filed[,]” and thus replacing a non-diverse\n\n\n\n\n 35\n\fplaintiff with a diverse plaintiff cured any jurisdiction\nproblem); Rowe v. United States Fid. & Guar. Co., 421 F.2d\n937, 939, 944 (4th Cir. 1970) (concluding that a defective\ncomplaint could be cured by a later complaint that pled an\nassignment occurring after the original complaint was filed).\n\n Nonetheless, “[a]mendments that go beyond the mere\ncorrection or factual modification of the original pleading and\nsignificantly alter the claim or defense alleged in that\npleading are treated more cautiously by the courts in applying\nthe relation-back doctrine.” Wright et al., supra, § 1497. The\nSecond Circuit, for instance, only sometimes allows\njurisdictional defects to be cured “when the underlying facts,\nif properly pled, would have supported jurisdiction at the time\nthe action commenced.” Correspondent Servs. Corp. v. First\nEquities Corp. of Fla., 338 F.3d 119, 125 (2d Cir. 2003); see\nalso, e.g., Barton v. Ellis, No. 75-1188, 1977 WL 15469, at\n*1 (D.S.C. Apr. 26, 1977) (denying using relation back to\ncure the original complaint since they were defects “not [in\nthe] allegations of existing underlying jurisdictional facts but\nrather [in] the prerequisite jurisdictional facts themselves”).\nWilmington argues such hesitance is appropriate here because\nallowing relation back to cure the jurisdictional problem with\nT Mobile’s initial complaint “would allow two wrongs under\nSection 332 [(filing early and filing late)] to make a right.”\n(Answering Br. at 2.)\n\n We again disagree with the City. It is quite true that\nT Mobile has made procedural matters more difficult than\nthey should be in this case. But denying relation-back to cure\nthe defect in this instance would not comport with Rule 15’s\naim to encourage resolution of disputes on the merits\nwhenever possible. The ripeness requirement exists so that\n\n\n\n\n 36\n\fcourts avoid issuing essentially advisory opinions. See\nRichard H. Fallon, Jr. et al., Hart and Wechsler’s the Federal\nCourts and the Federal System 224 (5th ed. 2003) (noting that\nthe ripeness doctrine allows courts to avoid a “dispute … too\n‘ill-defined’ to be appropriate for judicial resolution until\nfurther developments … more sharply framed the issues for\ndecision.”). That concern ceased to exist here once the\nsupplemental pleading was in place. At that point, the dispute\nhad matured and become capable of judicial review,\ndemonstrating that, “actions taken after the filing of the initial\ncomplaint can be used to establish subject matter\njurisdiction.” Prasco, LLC v. Medicis Pharm. Corp., 537\nF.3d 1329, 1337 (Fed. Cir. 2008).\n\n If a supplemental complaint cannot cure an unripe\ncomplaint, an endless feedback loop would be created\nwhereby the ripeness problem could never be overcome, even\nthough, as here, the dispute later became obviously ripe. Our\nsister circuits have recognized that problem and concluded\nthat a supplemental complaint is the solution. 22 In Wilson v.\nWestinghouse Electric Corp., the Eighth Circuit determined\nthat prohibiting an amended (or supplemental) complaint\nfrom alleging facts that occurred after the date the initial\n\n 22\n In our Circuit, a thoughtful district court decision\nhad long ago reached that conclusion. It held that an\nuntimely supplement adding facts occurring after the initial\nfiling that showed exhaustion of administrative remedies\ncould relate back to the initial premature complaint and allow\nmaintenance of the lawsuit. Bates v. W. Elec., 420 F. Supp.\n521, 526-27 (E.D. Pa. 1976).\n\n\n\n\n 37\n\fcomplaint was filed would turn a premature complaint into an\n“irretrievable mistake that bars jurisdiction” and would be\n“precisely the kind of procedural mousetrap that the Federal\nRules were designed to dismantle.” 838 F.2d 286, 289 (8th\nCir. 1988). The court held that, “[e]ven when the District\nCourt lacks jurisdiction over a claim at the time of its original\nfiling, a supplemental complaint may cure the defect by\nalleging the subsequent fact which eliminates the\njurisdictional bar.” Id. at 290 (citing Mathews, 426 U.S. at\n75). While Wilson addressed a circumstance in which the\nsupplemental complaint was timely filed, the proposition still\napplies in a case like ours because, if a party was limited to\nrefiling within an applicable time limit, there would be little\nneed to make provision for supplementation of a complaint,\nas a new complaint could be filed. 23\n\n 23\n We note that sparing the cost of refiling and\nproviding convenience to the Court would remain legitimate\nreasons for allowing supplemental complaints. But the\npurpose of Rule 15(d) is broader. See Wright et al., supra, §\n1504 (“The purpose of subdivision (d) is to promote as\ncomplete an adjudication of the dispute between the parties as\nis possible. … A supplemental pleading may be employed\nfor a variety of purposes.”). Wilmington contends that\nWilson is inapposite since it involved a timely supplemental\ncomplaint. Thus, concern about a perpetual loop outcome\nwas not proper because the plaintiff could have simply refiled\nhis complaint. But we agree that “a plaintiff need not\ncommence a new action when after-occurring events\ndemonstrate that it has a right to relief even if the original\ncomplaint was insufficient. A plaintiff may also be allowed\nto supplement the complaint even if jurisdiction … would not\nhave been proper if the claim had been asserted in an\n\n\n\n\n 38\n\f The Ninth Circuit, in Security Insurance Co. of New\nHaven v. United States ex rel. Haydis, also relied on that logic\nto find that relation back could cure an unripe complaint filed\nbefore a statutory filing window opened. 338 F.2d 444, 448-\n49 (9th Cir. 1964). In a fact scenario with striking similarities\nto the present appeal, the plaintiff had filed its claim before a\nstatutory waiting period was over and then did not file an\namended complaint until after the statute of limitations period\nhad run. Id. at 445-46. The appeals court held that the\ndistrict court was “not required to apply the doctrine of\nrelation back so literally as to carry it to a time [before it was\nripe] so as to prevent the maintenance of the action in the first\nplace.” Id. at 449.\n\n The Supreme Court has favorably cited Security\nInsurance’s ruling. In Mathews, the plaintiff had not satisfied\na precondition of filing a complaint by first filing an\napplication with a particular agency. 426 U.S. at 72, 75. The\nCourt noted that a supplemental complaint, alleging that the\napplication had since been filed, would have cured the\njurisdictional defect. Id. at 75. In saying so, the Court relied\n\n\n\nindependent action.” Moore et al., supra, ¶ 15.30 (3d ed.\n2018) (citation omitted). If supplemental complaints could\nnot cure ripeness, “then all supplemental pleadings of this\nnature would be defeated for lack of jurisdiction – [the]\n‘procedural mousetrap’ would render all supplemental\npleadings void.” George v. IRS, No. C05-00955 MJJ, 2006\nWL 3499230, at *3 (N.D. Cal. Dec. 4, 2006) (citation\nomitted).\n\n\n\n\n 39\n\fon Security Insurance. Id. at 75 n.8 (citing Security\nInsurance, 338 F.2d at 447-49). 24\n\n Yet Wilmington asserts that ripeness can never be\ncured by a later complaint. It advances four cases for that\nproposition, but none are helpful. First, the City cites\nDelaware Riverkeeper Network v. Secretary Pennsylvania\nDepartment of Environmental Protection, (Riverkeeper I),\n833 F.3d 360 (3d Cir. 2016), in which we concluded that,\n“even though the underlying claim became ripe for review\nduring the pendency of the case, the ripening of the claim did\nnot cure deficient pleadings.” (App. at 8.) In that case,\nhowever, no attempt to file a later complaint alleging ripeness\nwas made. Riverkeeper I, 833 F.3d at 369-70.\n\n Likewise, in another two of the four cases that\nWilmington cites, there was no effort made to amend or\nsupplement the complaint. See TeleSTAR, Inc. v. FCC, 888\nF.2d 132, 134 (D.C. Cir. 1989) (concluding non-final agency\naction at the time of filing of petition may only be reviewed\nupon the filing of another petition); W. Union Tel. Co., 773\nF.2d at 377-78 (concluding that the court lacked jurisdiction\nover challenges filed before the action became final).\nTherefore, neither case determined whether relation back of a\nlater-filed complaint could cure a ripeness problem in the\ninitial complaint.\n\n 24\n Wilmington contends that Mathews is inapposite\nsince the statute of limitations was waived. That argument\nhas no traction since, if it were a jurisdictional bar, it could\nnot be waived.\n\n\n\n\n 40\n\f The City fares no better relying on Council Tree\nCommunications v. FCC, in which we stated that “[a] petition\nto review a non-final agency order is incurably premature.”\n503 F.3d 284, 291 (3d Cir. 2007). At no point in that case\nwas the complaint ripe, and the petitioner still had a petition\nfor reconsideration pending before the relevant agency on the\ndate the case was decided. Id. at 287. Furthermore, Council\nTree explicitly acknowledged that a supplemental complaint\ncan cure an unripe complaint when there is jurisdiction over\nthat supplemental pleading. See id. at 291 (“[W]e note that\n‘nothing prevented [the petitioners] from supplementing their\npremature petition with a later protective petition.’” (second\nalteration in original) (quoting Horsehead Res. Dev. Co. v.\nE.P.A., 130 F.3d 1090, 1095 (D.C. Cir. 1997))).\n\n Wilmington also makes three policy arguments in\nsupport of its position that an untimely supplemental\ncomplaint should not be able to cure an unripe complaint.\nFirst, it contends that allowing suits to be filed before an\naction is ripe would “extend[] federal court jurisdiction over\nlocal government actions before those actions are final[.]”\n(Answering Br. at 9.) Second, such filings would waste\njudicial resources and, in this case, cost taxpayers money, by\nforcing courts to deal with a higher volume of unripe\ncomplaints. Third, the purpose of § 332 is to preserve local\nzoning authority, which would be undermined by allowing\nplaintiffs to file suit early and thereby places undue pressure\non zoning commissions.\n\n Those contentions, however, are unpersuasive. First, a\ncourt would remain without jurisdiction if the claim had not\nripened by the time of the supplemental complaint. Second, it\n\n\n\n\n 41\n\fseems that Wilmington overstates the impact that a decision\nallowing an unripe complaint to be cured would have, since\nour holding today makes it clear that an action is not final\nuntil a written decision has been issued. Clarifying when a\ndetermination is ripe for review should end any incentive for\naggrieved parties to file early to ensure they have not filed too\nlate.\n\n Perhaps more importantly, however, courts can police\nany potential abuse on a case-by-case basis using Rule 15(d)\nand the Rule 15(c) test for relation back. It is understood that\n“relation back of a supplemental pleading should not result in\nproviding unfair procedural advantages to a plaintiff[,] so …\nrelation back may not be for all purposes.” Wright et al.,\nsupra, § 1508. But here no unfair advantage has resulted, and\ndefendants in general will be adequately protected by a\ndistrict court’s Rule 15(d) analysis, which will determine if a\nsupplemental complaint should be allowed at all. For\ninstance, if a locality’s action is not yet a final action at the\ntime a Rule 15(d) motion is filed, the motion can easily be\ndenied. See Beezley v. Fremont Indem. Co., 804 F.2d 530,\n530 (9th Cir. 1986) (supplemental pleading denied when it\nstill failed to cure defective original pleading).\n\n When all is said and done here, we conclude that, to\neffectuate the liberal purpose of Rule 15 and to avoid the\nendless feedback loop that the City’s legal argument would\ncreate, Rule 15 allows an untimely supplemental complaint to\nrelate back and cure an unripe initial complaint.\n\n\n\n\n 42\n\fIII. CONCLUSION\n\n For the foregoing reasons, we will reverse the District\nCourt’s grant of the City’s motion for summary judgment,\nvacate the District Court’s denial of T Mobile’s motion for\nsummary judgment, and remand to the District Court for\nfurther proceedings consistent with this opinion.25\n\n\n\n\n 25\n We will vacate the District Court’s denial of\nT Mobile’s motion for summary judgment because it was\nsolely based on a finding that T Mobile’s suit was not timely\nbrought.\n\n\n\n\n 43\n[END_CASE]", "role": "user" } ]
4,582,001
UNITED STATES of America, Appellant in 17-1346 v. Chaka FATTAH, Sr., Appellant in 16-4397 Karen Nicholas, Appellant in 16-4410 Robert Brand, Appellant in 16-4411 Herbert Vederman, Appellant in 16-4427
United States v. Herbert Vederman
2019-01-16
16-4397; 16-4410; 16-4411; 16-4427; 17-1346
U.S. Court of Appeals for the Third Circuit
{"judges": "Smith, Greenaway, Krause", "parties": "", "opinions": [{"author": "SMITH, Chief Judge", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n Nos. 16-4397, 16-4410, 16-4411,\n 16-4427, 17-1346\n _____________\n\n UNITED STATES OF AMERICA\n Appellant in 17-1346\n\n v.\n\n CHAKA FATTAH, SR.,\n Appellant in 16-4397\n\n KAREN NICHOLAS,\n Appellant in 16-4410\n\n ROBERT BRAND,\n Appellant in 16-4411\n\n HERBERT VEDERMAN,\n Appellant in 16-4427\n _____________\n\nOn Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n District Court Nos. 2-15-cr-00346-001,\n\f 2-15-cr-00346-002, 2-15-cr-00346-003,\n 2-15-cr-00346-004\n District Judge: The Honorable Harvey Bartle III\n\n Argued January 18, 2018\n\nBefore: SMITH, Chief Judge, GREENAWAY, JR., and\n KRAUSE, Circuit Judges\n\n (Filed: January 16, 2019)\n\nAndrea G. Foulkes\nEric L. Gibson\nPaul L. Gray\nRobert A. Zauzmer\nOffice of United States Attorney\n615 Chestnut Street\nSuite 1250\nPhiladelphia, PA 19106\n\nJonathan Ian Kravis [ARGUED]\nUnited States Department of Justice\nCriminal Division, Public Integrity Section\n1400 New York Avenue, N.W.\nWashington, DC 20005\n Counsel for the United States\n\nMark M. Lee\nBruce P. Merenstein [ARGUED]\nSamuel W. Silver\n 2\n\fSchnader Harrison Segal & Lewis\n1600 Market Street\nSuite 3600\nPhiladelphia, PA 19103\n Counsel for Appellant Fattah\n\nAnn C. Flannery [ARGUED]\nSuite 2700\n1835 Market Street\nPhiladelphia, PA 19103\n\nLisa A. Mathewson\nSuite 810\n123 South Broad Street\nPhiladelphia, PA 19109\n Counsel for Appellant Nicholas\n\nAlan Silber\nPashman Stein Walder Hayden\n21 Main Street\nSuite 200\nHackensack, NJ 07601\n Counsel for National Association of Criminal\n Defense Lawyers, Amicus Appellant Nicholas\n\nMira E. Baylson\nBarry Gross [ARGUED]\nMeredith C. Slawe\nDrinker Biddle & Reath\nOne Logan Square\n 3\n\fSuite 2000\nPhiladelphia, PA 19103\n Counsel for Appellant Brand\n\nHenry W. Asbill\nBuckley Sandler\n1250 24th Street, N.W.\nSuite 700\nWashington, DC 20037\n\nGlen D. Nager [ARGUED]\nJacob M. Roth\nJulia W. M. F. Sheketoff\nJones Day\n51 Louisiana Avenue, N.W.\nWashington, DC 20001\n Counsel for Appellant Vederman\n\n ________________\n\n OPINION\n ________________\n\n\nSMITH, Chief Judge.\n\n\n\n\n 4\n\f Table of Contents\nI. Introduction ................................................................... 8\nII. Background .................................................................. 9\n A. The Fattah for Mayor Scheme ................................. 9\n 1. The Lord Loan and Its Repayment ..................... 10\n 2. The College Tuition Component of the FFM\n Scheme ................................................................ 27\n 3. The NOAA Grant and the Phantom Conference 28\n B. The Blue Guardians Scheme.................................. 31\n C. The Fattah–Vederman Bribery Scheme................. 33\n D. The Indictment and Trial ....................................... 39\nIII. Juror Misconduct and Dismissal of Juror 12 ........... 58\n A. Investigation of Alleged Juror Misconduct ........... 58\n B. Dismissal of Juror 12 ............................................. 64\nIV. The District Court’s Instructions Under McDonnell 70\n A. The McDonnell Framework................................... 71\n B. The Kirk Meeting ................................................... 76\n C. Fattah’s Efforts to Secure Vederman an\n Ambassadorship.......................................................... 79\n D. The Zionts Hiring .................................................. 82\n E. Vederman’s Sufficiency Challenge to Counts 16–18\n and 22–23.................................................................... 89\n F. Blue Guardians ....................................................... 91\n\n 5\n\fV. Sufficiency of the Evidence for the RICO Conspiracy\nConviction ...................................................................... 95\nVI. Variance from the Indictment and Sufficiency of the\nEvidence for Count 2.................................................... 110\nVII. The District Court’s Instruction to the Jury on the\nMeaning of Intent ......................................................... 120\nVIII. Sending the Indictment to the Jury ...................... 126\nIX. The District Court’s Evidentiary Rulings .............. 129\n A. The District Court’s Application of Rule 404(b) 129\n B. Evidentiary Rulings Regarding Nicholas’s\n Defense ..................................................................... 134\n 1. The EAA Board Minutes .................................. 134\n 2. Jones’ Memory Regarding Other Contracts ..... 136\n 3. Exclusion of NOAA Evidence.......................... 137\n C. The Cooperating Witness’s Mental Health\n Records ..................................................................... 138\n 1. The District Court’s Denial of Access to the\n Mental Health Records ..................................... 140\n 2. The District Court’s Grant of the Motion in\n Limine ............................................................... 142\nX. The Government’s Cross-Appeal ............................ 147\n A. CUMA is a Mortgage Lending Business............. 148\n B. Sufficiency of the Evidence ................................. 155\nXI. Prejudicial Spillover ............................................... 158\n A. Fattah’s Claim of Prejudicial Spillover ............... 159\n 6\n\f B. Vederman’s Assertion of Prejudicial Spillover ... 160\nXII. Conclusion ............................................................ 164\n\n\n\n\n 7\n\f I. Introduction\n Chaka Fattah, Sr., a powerful and prominent fixture\nin Philadelphia politics, financially overextended himself\nin both his personal life and his professional career during\nan ultimately unsuccessful run for mayor. Fattah received\na substantial illicit loan to his mayoral campaign and used\nhis political influence and personal connections to engage\nfriends, employees, and others in an elaborate series of\nschemes aimed at preserving his political status by hiding\nthe source of the illicit loan and its repayment. In so doing,\nFattah and his allies engaged in shady and, at times, illegal\nbehavior, including the misuse of federal grant money and\nfederal appropriations, the siphoning of money from\nnonprofit organizations to pay campaign debts, and the\nmisappropriation of campaign funds to pay personal\nobligations.\n Based upon their actions, Fattah and four of his\nassociates—Herbert Vederman, Robert Brand, Bonnie\nBowser, and Karen Nicholas—were charged with\nnumerous criminal acts in a twenty-nine count indictment.\nAfter a jury trial, each was convicted on multiple counts.\nAll but Bowser appealed. As we explain below, the\nDistrict Court’s judgment will be affirmed in part and\nreversed in part.\n\n\n\n\n 8\n\f II. Background1\n During the 1980s and ’90s, Fattah served in both\nhouses of the Pennsylvania General Assembly, first as a\nmember of the House of Representatives and later as a\nSenator. In 1995, Fattah was elected to the United States\nHouse of Representatives for Pennsylvania’s Second\nCongressional District. In 2006, Fattah launched an\nunsuccessful run for Mayor of Philadelphia, setting in\nmotion the events that would lead to his criminal\nconviction and resignation from Congress ten years later.\n\n A. The Fattah for Mayor Scheme\n Fattah declared his candidacy for mayor in\nNovember of 2006. Thomas Lindenfeld, a political\nconsultant on Fattah’s exploratory committee, believed\nthat “[a]t the beginning of the campaign, [Fattah] was a\nconsiderable . . . candidate and somebody who had a very\nlikely chance of success.” JA1618. But Fattah’s campaign\nsoon began to experience difficulties, particularly with\nfundraising. Philadelphia had adopted its first-ever\ncampaign contribution limits, which limited contributions\nto $2,500 from individuals and $10,000 from political\naction committees and certain types of business\norganizations. Fattah’s fundraising difficulties led him to\n\n\n\n1\n The facts are drawn from the trial record unless otherwise\nnoted.\n 9\n\fseek a substantial loan, far in excess of the new\ncontribution limits.\n\n 1. The Lord Loan and Its Repayment\n While serving in Congress, Fattah became\nacquainted with Albert Lord, II. The two first met around\n1998, when Lord was a member of the Board of Directors\nof Sallie Mae.\n As the May 15, 2007 primary date for the\nPhiladelphia mayoral race approached, Fattah met Lord to\nask for assistance, telling Lord that the Fattah for Mayor\n(FFM) campaign was running low on funds. Fattah asked\nLord to meet with Thomas Lindenfeld, a political\nconsultant in Washington, D.C., and part-owner of LSG\nStrategies, Inc. (Strategies), a company that was working\nwith the FFM campaign and that specialized in direct voter\ncontact initiatives. Lindenfeld had been part of the\nexploratory group that initially considered Fattah’s\nviability as a candidate for mayor. Lindenfeld had known\nFattah since 1999, when Fattah endorsed Philadelphia\nMayor John Street. Through Fattah, Lindenfeld had also\ngotten to know several of Fattah’s associates, including\nHerbert Vederman, Robert Brand, and Bonnie Bowser.\nHerbert Vederman, a businessman and former state\nofficial, was the finance director for the FFM campaign.\nRobert Brand owned Solutions for Progress (Solutions), a\n“Philadelphia-based public policy technology company,\nwhose mission [was] to deliver technology that directly\nassists low and middle income families [in obtaining]\n 10\n\fpublic benefits.” JA6551. Bowser was Fattah’s Chief of\nStaff and campaign treasurer, and served in his district\noffice in Philadelphia.\n Lord’s assistant contacted Lindenfeld to arrange a\nmeeting, and Lindenfeld informed Fattah that he would be\nmeeting with Lord. Lindenfeld, along with his partner,\nMichael Matthews, met with Lord and discussed Fattah’s\nneed for funds to mount an intensive media campaign.\nAfter that meeting, Lindenfeld reported to Fattah that Lord\nwanted to help, but that they had not discussed a specific\ndollar amount. Approximately a week later, Fattah\ninstructed Lindenfeld to meet with Lord a second time.\nLord “wanted to know if he could give a substantial\namount of money, a million dollars” to Fattah’s campaign.\nJA1630. That prompted Lindenfeld to reply that the\namount “would be beyond the campaign finance limits.”\nId.\n\n Lord proposed a solution: he offered to instead give\na million dollars to Strategies in the form of a loan. To that\nend, Lindenfeld had a promissory note drafted which\nspecified that Lord was lending Strategies $1 million, and\nthat Strategies promised to repay the $1 million at 9.25%\ninterest, with repayment to commence January 31, 2008.\nLindenfeld later acknowledged that the promissory note\nwould make it appear as though Lord’s $1 million was not\na contribution directly to the Congressman, although he\nknew that it was actually a loan to the FFM campaign.\nIndeed, Lindenfeld confirmed with Fattah that neither\n\n 11\n\fLindenfeld nor Strategies would be responsible for\nrepayment. With that understanding, Lindenfeld executed\nboth the note and a security agreement purporting to\nencumber Strategies’ accounts receivable and all its assets.\n\n On May 1, shortly before the primary election, Lord\nwired $1 million to Lindenfeld. Lindenfeld held the money\nin Strategies’ operating account until Fattah told him how\nit was to be spent. Some of the money was eventually used\nfor print materials mailed directly to voters. And, at\nFattah’s direction, Lindenfeld wired a substantial sum to\nSydney Lei and Associates (SLA), a company owned by\nGregory Naylor which specialized in “get out the vote”\nefforts.\n Naylor had known Fattah for more than 30 years.2\nDuring the campaign, Naylor worked as the field director\nand was in charge of getting out the vote on election day.\n\n2\n Naylor first worked with Fattah when he was in the state\nlegislature. When Fattah was elected to Congress, Naylor\nworked in his Philadelphia office. Naylor met Nicholas\nwhen she joined Fattah’s staff at some point in the 1990s.\nAfter concluding her employment with Fattah’s office,\nNicholas worked with the Educational Advancement\nAlliance (EAA), an education nonprofit entity founded by\nFattah. This entity helped to recruit underrepresented\nstudents for scholarship and college opportunities. Around\n2009, Naylor left Fattah’s office to work exclusively with\nSLA. Naylor also knew Brand.\n 12\n\fOn the final day of the campaign, Naylor worked with\nVederman, who allowed Naylor to use his credit card to\nrent vans that would transport Fattah voters to the polls.\n As the primary date neared, Fattah and Naylor knew\nthe campaign was running out of money. The campaign\nwas unable to finance “media buys,” and Naylor needed\nmoney for field operations to cover Philadelphia’s more\nthan one thousand polling places. In early May,\nLindenfeld called Naylor to say that Lindenfeld “would be\nsending some money [Naylor’s] way.” JA3057. Within\ndays, SLA received a six-figure sum for Naylor to use in\nthe campaign and on election day. Naylor used the money\nto pay some outstanding bills, including salaries for FFM\nemployees, and allocated $200,000 to field operations for\nelection day.\n\n Fattah lost the mayoral primary on May 15, 2007.\nAfterward, Lindenfeld spoke with Fattah, Naylor and\nBowser about accounting for the FFM campaign money\nfrom Lord that had been spent. They decided that the\namounts should not appear in the FFM campaign finance\nreports, and Fattah instructed Naylor to have his firm,\nSLA, create an invoice. Naylor did so, creating an invoice\ndated June 1, 2007 from SLA to FFM, seeking payment of\n$193,580.19. Naylor later acknowledged that the FFM\ncampaign did not actually owe money to SLA, and that the\nfalse invoice was created to “hide the transaction that took\nplace earlier” and “make it look like [SLA] was owed\nmoney.” JA3075–76. Although FFM did not owe SLA\n\n 13\n\fanything for the election day expenses, the FFM campaign\nfinance reports from 2009 through 2013 listed a $20,000\nin-kind contribution from SLA for each year, thereby\nlowering FFM’s alleged outstanding debt to SLA.\n\n Of the total $1 million Lord loan, $400,000 had not\nbeen spent. Lindenfeld returned that sum to Lord on June\n3, 2007. He included a cover letter which stated: “As it\nturns out the business opportunities we had contemplated\ndo not seem to be as fruitful as previously expected.”\nJA1254. Lindenfeld later admitted that there were no such\n“business opportunities” and that the letter was simply an\neffort to conceal the loan.\n In late 2007, faced with financial pressures, Lord\nasked his son, Albert Lord, III, to collect the outstanding\n$600,000 balance on the loan to Strategies. Lord III\ncontacted Lindenfeld about repayment and expressed a\nwillingness to forgive the interest owed if the principal\nwas paid. Lindenfeld immediately called Fattah and\ninformed him that repayment could not be put off any\nlonger. Fattah told Lindenfeld more than once that “[h]e\nwould take care of it,” JA1652, but Fattah did not act.\nNeeding someone who might have Fattah’s ear,\nLindenfeld reached out to Naylor and Bowser. Naylor\ntalked to Fattah on several occasions and told him that\nLindenfeld was under considerable pressure to repay the\nloan. Fattah told Naylor more than once that he was\n“working on it.” JA3082–83.\n\n\n 14\n\f During his political career, Fattah had focused on\neducation, especially for the underprivileged. Indeed,\nFattah founded two nonprofit organizations: College\nOpportunity Resources for Education (CORE), and the\nEducational Advancement Alliance (EAA).\n\n EAA held the annual Fattah Conference on Higher\nEducation (the “annual conference”) to acquaint high\nschool students with higher education options. JA3079.\nSallie Mae regularly sponsored the conference. According\nto Raymond Jones, EAA’s chairman of the board from\n2004 through 2007, EAA offered a variety of programs to\nprovide “marginalized students with educational\nopportunities so they could continue and go to college.”\nJA1360. EAA was funded with federal grant money which\ncould only be spent for the purposes described in the\nparticular grant. Karen Nicholas served as EAA’s\nexecutive director, handling the organization’s day-to-day\nadministrative responsibilities. Nicholas had previously\nbeen a staffer for Fattah when he was a member of\nPennsylvania’s House of Representatives.\n CORE was an organization that awarded\nscholarships to graduating high school students in\nPhiladelphia who had gained admission to a state\nuniversity or the Community College of Philadelphia.\nCORE received funding from a variety of sources,\nincluding Sallie Mae. Because CORE also received\nfederal funds, and because EAA had experience working\nwith federal grants, EAA received and handled the federal\n\n 15\n\ffunds awarded to CORE. In short, EAA functioned as a\nfiduciary for CORE. When money became a problem for\nthe FFM campaign, Fattah’s involvement with EAA and\nCORE soon became less about helping underprivileged\nstudents, and more about providing an avenue for\ndisguising efforts to repay the illicit campaign funds from\nLord.\n\n On January 7, 2008, Robert Brand contacted Fattah\nby telephone. Shortly thereafter, Lindenfeld received an\nunexpected call from Brand proposing an arrangement for\nBrand’s company, Solutions, to work with Strategies.\nSolutions had developed a software tool called “The\nBenefit Bank,” which was designed to “assist low and\nmoderate income families to have enhanced access to\nbenefits and taxes.” JA1993. During the telephone call,\nBrand referred to The Benefit Bank and suggested a\ncontract under which Strategies would be paid $600,000\nupfront. JA1666. Shortly thereafter, on January 9, 2008,\nBrand followed up on his call to Lindenfeld with an email\nabout “develop[ing] a working relationship where you\ncould help us to grow The Benefit Bank and our process\nof civic engagement. While I know this is not your core\nbusiness I would like to try to convince you to take us on\nas a client.” JA6427. Lindenfeld responded that he was\ninterested. To Lindenfeld, “this was the way that\nCongressman Fattah was going to repay the debt to Al\nLord.” JA1654. When Lindenfeld called Fattah and told\nhim of the contact from Brand, Fattah simply replied that\nLindenfeld “should just proceed.” JA1666–67.\n 16\n\f A few days later, Brand emailed Nicholas at EAA a\nproposal from Solutions concerning The Benefit Bank,\nwhich sought EAA’s support in developing an education\nedition of The Benefit Bank and a $900,000 upfront\npayment.\n\n As the January 31 date for repayment of the balance\nof the $1 million Lord loan approached, a flurry of activity\ntook place. On January 24, both Raymond Jones, chair of\nthe EAA Board, and Nicholas signed a check from EAA\nmade out to Solutions in the amount of $500,000.\nAlthough no contract existed between EAA and Solutions,\nthe memo line of the check indicated that it was for a\ncontract, and Nicholas entered it into EAA’s ledger.3\n\n That same day, Ivy Butts, an employee of\nStrategies, emailed Lindenfeld the instructions Brand\nwould need to wire the $600,000 balance on the Lord loan.\n\n3\n Raymond Jones, who was EAA’s Chairman of the Board\nfrom 2004 through 2007, recalled at trial that the Board\nhad a limit on the amount that Nicholas could spend\nwithout board approval. JA1358, 1369. Nicholas was\nauthorized to sign contracts on behalf of EAA for no more\nthan $100,000. JA1369–71. Jones did not recall the\ncontract between EAA and Solutions, nor did the EAA\nboard minutes for December 2007, February 2008, or May\n2008 refer to the EAA–Solutions contract or to the\nsubstantial upfront payment of half a million dollars upon\nexecution of the agreement. JA6358–63; 6567.\n 17\n\fWithin minutes, Lindenfeld forwarded that email to Brand\nat Solutions. Brand then made two telephone calls to\nFattah. By late afternoon, Brand emailed Nicholas,\ninforming her that he had “met with all the people I need\nto meet with and have a pretty clear schedule of what\nworks best for us. I am also seeing what line of credit we\nhave to stretch out the payments until you get your line of\ncredit in place.” JA6558. Brand asked if they could talk\nand “finalize this effort.” JA6558. On January 25 and 26,\nthere were a number of calls between Fattah, Brand, and\nNicholas.\n\n On Sunday January 27, at 5:46 pm, Brand\ntelephoned Fattah. At 10:59 pm, Brand emailed Nicholas\na revised contract between EAA and Solutions for the\nengagement of services. Brand indicated he would send\nsomeone to pick up the check at about 1:00 pm the\nfollowing day. The revised contract called for the same\n$900,000 payment from EAA to Solutions, yet specified\nthat $500,000 was to be paid on signing, with $100,000\ndue three weeks later, and another $100,000 to be paid six\nweeks out. No due date for the $200,000 balance was\nspecified. The terms of the contract called for EAA to\nassist Solutions with further developing The Benefit Bank.\nIn addition, under the contract, EAA would receive certain\n\n\n\n\n 18\n\ffunds from the Commonwealth of Pennsylvania for a\nprogram relating to FAFSA applications. 4\n\n The same evening, Brand sent Lindenfeld a contract\nentitled “Cooperative Development Agreement to Provide\nServices to Solutions for Progress, Inc. for Growth of The\nBenefit Bank.” JA6569. The agreement proposed a\nworking partnership in which Strategies would work with\nSolutions to identify and secure a Benefit Bank affiliate in\nthe District of Columbia and two other states, and to\nfacilitate introductions to key officials in other states\nwhere The Benefit Bank might expand. The terms of the\nagreement provided that Solutions would pay $600,000 to\nStrategies by January 31, 2008, which would “enable\n[Strategies’] team to assess opportunities and develop\ndetailed work plans for each area.” JA6572. Brand copied\nSolutions’ Chief Financial Officer, Michael Golden.\nLindenfeld responded to Brand’s email within a minute,\nasking if Brand had received the wiring instructions.\nBrand immediately confirmed that he had.\n\n Concerned that Solutions did not have $600,000 to\npay Strategies, Golden talked to Brand, who informed him\nthat Solutions would be receiving a check for $500,000\nfrom EAA. Early the next morning, Nicholas responded to\nBrand’s email from the night before. She advised Brand\nthat he could pick up the check, “but as I stated I am not\n\n4\n FAFSA is an acronym for Free Application for Federal\nStudent Aid.\n 19\n\fin a position to sign a contract committing funds that I am\nnot sure that I will have.” Gov’t Supp. App. (GSA) 1. That\nsame day, a $540,000 transfer was made from the\nconference account, which EAA handled, into EAA’s\nchecking account. The conference account was maintained\nto handle expenses for Fattah’s annual higher education\nconference. Prior to this transfer, EAA had only\n$23,170.95 in its account. EAA then tendered a $500,000\ncheck to Solutions, which promptly deposited the check\nbefore the close of that day’s business. EAA never\nreplenished the $540,000 withdrawal from the conference\naccount.\n Brand received the executed contract between\nSolutions and Strategies on January 28. Even though the\ncontract called for Strategies to perform services in\nexchange for the $600,000 payment, Lindenfeld neither\nexpected to do any work for the $600,000, nor did he in\nfact do any work.\n\n In sum, by January 28, Solutions had received\n$500,000 from EAA, but it still had to come up with\n$100,000 to provide Strategies with the entire amount\nneeded to repay the Lord loan. Golden obtained the needed\nfunds the following day by drawing $150,000 on a line of\ncredit held by Brand’s wife. Brand and Fattah spoke four\nmore times on the telephone on January 29. Trial evidence\nlater showed that, during the month of January 2008,\nneither the FFM campaign bank account nor Fattah’s\n\n\n 20\n\fpersonal account had a sufficient balance to fund a\n$600,000 payment.\n On the morning of January 30, frustrated by the\ndelay, Lindenfeld sent Brand an email with a subject line\n“You are killing me.” JA6430. Lindenfeld stated that he\nhad “made a commitment based on yours to me. Please\ndon’t drag this out. I have a lot on the line.” Id. Brand\nresponded late in the afternoon, stating: “just met with\nMichael. He does the transfer at 8 AM tomorrow. It should\nbe in your account ($600K) early tomorrow morning.” Id.\nLindenfeld replied: “The earlier the better.” Id. The\nfollowing morning, Golden wired $600,000 from\nSolutions’ Pennsylvania bank account into Strategies’\nWashington D.C. bank account. JA2745, 2874. Strategies\nin turn, wired the same amount from its Washington D.C.\nbank account to Lord’s bank account in Virginia. JA2874,\n6549. Around noon, Brand telephoned Lindenfeld.\n\n In the days following the exhaustive efforts to meet\nthe January 31 loan repayment deadline, four more\ntelephone calls took place between Brand and Fattah.5\nNaylor learned at some point that the loan had been paid\noff. When Naylor asked Fattah about details of the\nrepayment, Fattah simply replied “[t]hat it went through\nEAA to Solutions and it was done.” JA3088.\n\n5\n By contrast, between October to December 2007, Brand\nand Fattah spoke by telephone only “once or twice [a]\nmonth.” JA2734.\n 21\n\f Meanwhile, at some point in January, EAA received\nnotice that the Department of Justice Office of the\nInspector General (DOJ) intended to audit its books.6 DOJ\nauditors told EAA to provide, at the “entrance\nconference,” documentation containing budgetary and\naccounting information. EAA failed to produce any\naccounting information.\n Although Lindenfeld was no longer making\ndemands of Brand, Brand was still owed the remaining\n$100,000 that Solutions had paid to satisfy the Lord loan.\nOn March 23, 2008, Brand sent Nicholas an email\noutlining his efforts to contact her over the previous two\nweeks about documentation on the CORE work, how to\nproceed with the paperwork for the Commonwealth of\nPennsylvania, and “how we can get our proposed contract\nsigned and the outstanding payments made.” JA2749.\nNicholas responded that evening, writing:\n\n I can appreciate your urgency however I do\n have EAA work that I continue to do,\n including the [usual] facilitation of programs,\n our financial audit, the start-up of two new\n programs[,] and of course the DOJ audit. I am\n still trying to obtain a line of credit without a\n completed 2007 audit and things are getting a\n\n\n\n6\n One of the terms and conditions of a federal grant is that\nthe recipient “be readily prepared for an audit.” JA2314.\n 22\n\f little uncomfortable now as I try to keep us\n afloat.\nJA6576. Nicholas told Brand that the DOJ auditors were\nmaking demands and would soon be on site. She noted that\n“[t]hey are still very uncomfortable with your contract\namongst other things and depending on their findings\nsome of the funding received may have to be returned.” Id.\nNicholas said that she had submitted the paperwork to the\nstate, and she told Brand that “in the future . . . as a result\nof the DOJ audit I will not be in a position to do another\ncontract such as this.” Id.\n Shortly after Nicholas’s reply to Brand, Nicholas\nforwarded the Brand–Nicholas email chain to Fattah. The\nbody of the email stated, in its entirety: “I really don’t\nappreciate the tone of Bob’s email. I can appreciate that he\nhas some things going on however I am doing my best to\nassist him. Some other things are a priority. He needs to\nback off.” GSA2. Later that night, Bowser sent Fattah an\nemail with a subject line that read “Karen N” and a\ntelephone number. JA2752.\n\n As the audit continued, the auditors found other\ndeficiencies. During April of 2008, DOJ issued a notice of\nirregularity to EAA, which resulted in the audit being\nreferred to DOJ’s Investigations Division for a more\ncomprehensive review.\n\n On April 24, 2008, Brand emailed Nicholas asking\nfor a time to update her on The Benefit Bank. In early May,\n 23\n\fBrand sent another email to Nicholas attaching a revised\nEAA–Solutions contract proposal, which decreased the\ninitial upfront cost from $900,000 to $700,000.\n Although Solutions and EAA had still not signed a\ncontract, EAA paid Solutions another $100,000 in May.\nThat money was obtained via a loan to EAA from CORE.\nThomas Butler, who had worked for Fattah both when\nFattah was in Congress and when he was in the General\nAssembly, was CORE’s executive director. Butler had\nbeen contacted in mid-May by Jackie Barnett, a member\nof CORE’s Board who had also worked with\nCongressman Fattah. Barnett informed Butler that\nNicholas had requested a loan from CORE to EAA, and\nthat Fattah, as Chairman of CORE’s Board, had approved\nit. Butler and Barnett withdrew funds from two CORE\nbank accounts and obtained a cashier’s check, dated May\n19, in the amount of $225,000 and made payable to EAA.\nThe withdrawals were from accounts used for Sallie Mae\nfunds and other scholarship money.\n After EAA received the $225,000 check, EAA\ntendered a $100,000 check to Solutions. The check bore\nthe notation “Commonwealth of Pennsylvania.” EAA\nrepaid CORE the following month. Because EAA lacked\nsufficient funds of its own to cover this payment, EAA\ndrew on grant money that it had received from NASA.\n\n Brand and Lindenfeld continued to communicate\nconcerning The Benefit Bank. In July of 2008, a meeting\nwas held at Solutions with Brand, Lindenfeld, Golden, and\n 24\n\fother Solutions employees to discuss “an enormous\namount of work” that Brand wanted Strategies to do.\nJA1670. Lindenfeld said in response “we’d be glad to do\nthat, but . . . we would have to be paid.” Id. At that point,\nsomeone in the meeting stated that Strategies “had already\nbeen paid” $600,000. Id. Lindenfeld replied: “well, that\nwas for Congressman Fattah, . . . that’s not for us. So if\nyou want us to do work, we have to get paid for it\nseparately.” Id. Brand became upset with Lindenfeld over\nhis comment about being paid because his colleagues at\nSolutions were not aware of the reason for the $600,000\npayment.\n Meanwhile, EAA was attempting to meet the\ndemands of the DOJ auditors, who were focused on the\nrelationship between EAA and CORE. DOJ served a\nsubpoena upon Solutions to produce “[a]ny and all\ndocuments including, but not limited to, contract\ndocuments, invoices, correspondence, timesheets,\ndeliverables and proof of payment related to any services\nprovided to or payments received” from CORE or EAA.\nJA2350.\n\n Special Agent Dieffenbach, from the DOJ,\ninterviewed Nicholas on July 14, 2008. During that\ninterview, Nicholas discussed the relationship between\nEAA and CORE, how invoices were paid, and how\nconsultants were handled. Nicholas also answered\nquestions about EAA’s relationship with Solutions,\nincluding the payment of invoices. She did not inform\n\n 25\n\fAgent Dieffenbach of the $500,000 payment in January or\nthe subsequent $100,000 payment in May. Nor did the\ninterview address the EAA–Solutions contract that\npurportedly required those payments, because the contract\nhad yet to be produced.\n\n Solutions failed to comply with the subpoena,\nprompting an email from Agent Dieffenbach on August 26\nasking for an update concerning Solutions’ reply to the\nDOJ subpoena. Solutions then produced an undated\nversion of the EAA–Solutions contract that required the\n$600,000 upfront payment. Neither Brand nor Nicholas\nprovided the auditors with the January and May checks\nfrom EAA to Solutions.\n Efforts to conceal the repayment of the Lord loan\nand to promote the political and financial interests of\nFattah continued. The FFM campaign reports indicated in-\nkind contributions of debt forgiveness by SLA even\nthough there had been no actual debt. In September of\n2009, with EAA’s ledgers still under scrutiny, Nicholas\naltered the description of the entry for the $100,000 check\nto Solutions from “professional fees consulting” to\n“CORE Philly.” JA2546. Other FFM campaign debt was\nreduced further after Vederman negotiated with creditors.\n\n EAA never fully recovered from its payment of the\n$600,000 balance on the Lord loan and the audits that took\nplace in 2008. It began laying off employees in 2011, and\nby June of 2012, only four employees remained. JA3659.\nEAA ceased operations at some point in 2012. JA1530.\n 26\n\f 2. The College Tuition Component of the FFM\n Scheme\n Although the FFM campaign was close to insolvent,\nit nevertheless made tuition payments for Fattah’s son,\nChaka Fattah Jr., also known as Chip. Chip attended\nDrexel University, but had yet to complete his coursework\nbecause he had failed to pay an outstanding tuition\nbalance. As the FFM campaign got underway in 2007,\nFattah wanted Chip to re-enroll in classes at Drexel and\nget a degree. Fattah asked Naylor to help financially, and\nhe did so by writing checks from SLA to Drexel toward\nChip’s outstanding tuition. By October of 2007, Chip was\npermitted to re-enroll in classes.\n Although Naylor never directly addressed the issue\nwith Fattah, he agreed to assist with Chip’s outstanding\ntuition with the expectation that SLA would be repaid. The\nfirst check to Drexel in the amount of $5,000 was sent in\nAugust of 2007, with $400 payments in the months that\nfollowed until August of 2008. At some point, Chip\ninformed Naylor that the payee was no longer Drexel, but\nSallie Mae. Naylor then began sending monthly checks\nfrom SLA to Sallie Mae. Those payments, in the amount\nof $525.52, began in March of 2009 and continued until\nApril of 2011, after which Fattah told Naylor he no longer\nneeded to make them. SLA’s payments to Drexel and\nSallie Mae totaled $23,063.52.\n\n Naylor’s expectation of repayment was eventually\nrealized. Beginning in January of 2008 and continuing\n 27\n\funtil November 2010, Bowser sporadically sent SLA\nreimbursement checks from the FFM campaign with a\nnotation that payment was for “election day operation\nexpenses.” JA3136. The FFM funds had been transferred\nfrom the Fattah for Congress campaign. These\nreimbursement checks totaled $25,400. In an effort to\nconceal the source of the payments to Drexel and Sallie\nMae, and to make it appear that the younger Fattah had\nperformed services for SLA, Naylor created false tax\nforms for Chip. Chip, however, had never performed\nservices for SLA.\n\n 3. The NOAA Grant and the Phantom Conference\n In mid-December 2011, when EAA was\nexperiencing serious financial difficulties, Nicholas\nsubmitted an email request to the educational partnership\nprogram of the National Oceanic & Atmospheric\nAdministration (NOAA) for a grant “designed to provide\ntraining opportunities and funding to students at minority\nserving institutions” interested in science, technology,\nengineering, and math fields related to NOAA’s mission.\nJA3354–55. The request sought $409,000 to fund EAA’s\nannual conference scheduled for February 17–19, 2012.\nJacqueline Rousseau, a supervisory program manager at\nNOAA, participated in a conference call with Nicholas\nshortly thereafter and advised Nicholas that the agency\ncould not afford the $409,000 request but would consider\na smaller grant. Rousseau advised Nicholas that EAA\n\n\n 28\n\fwould need to submit an application if it wished to be\nconsidered for a grant.\n Before submitting a grant application, Nicholas\nemailed Rousseau about sponsoring the conference. On\nJanuary 11, 2012, Rousseau informed Nicholas that the\n“NOAA Office of Education, Scholarship Programs has\nagreed to participate and provide sponsorship funds of\n$50K to support the referenced conference.” JA6453.\nRousseau also informed Nicholas that Chantell Haskins,\nwho also worked with the student scholarship program,\nwould be the point of contact for NOAA.\n In February 2012, EAA held its annual conference\nat the Sheraton Hotel in downtown Philadelphia. The\nconference had been held at the same location each year\nsince 2008.\n\n Nicholas contacted Haskins at some point in early\n2012, inquiring about the $50,000 grant. On May 8, 2012,\nHaskins sent Nicholas an e-mail which included\ninformation about submitting proposals to fund a\nconference for students. EAA then submitted a grant\napplication, which Haskins reviewed. She advised\nNicholas on June 28, 2012 that the grant could not be used\nto provide meals, and that the date of the conference would\nhave to be pushed back, with the new date included in a\nmodified application. When Nicholas asked if expenses\nfrom a previous conference could be paid from the new\ngrant, Haskins informed her that this was not allowed.\n\n 29\n\f In early July 2012, Nicholas sent a modified grant\nproposal to Haskins. It eliminated the budget item for food\nand changed the date of the 2012 conference to October\n19–21, 2012 at the same Sheraton Hotel in Philadelphia\nwhere EAA’s annual conference had taken place earlier in\nthe year. NOAA approved a $50,000 grant for the October\n2012 conference—a conference that would never be held.\n\n Unaware that no October 2012 conference had\ntaken place, NOAA allowed Nicholas access to the\n$50,000 grant in March of 2013. She then transferred the\nentire amount from NOAA to EAA’s bank account a few\ndays later. Naylor had performed services for EAA for\nwhich he was still owed $116,590. JA3119. In discussions\nwith Naylor, Nicholas had informed him that the\nlikelihood of EAA’s being able to pay him was “[n]ot very\ngood.” JA3120. Yet several days after EAA had received\nthe $50,000 from NOAA, Nicholas sent Naylor a check\nfor $20,000. JA3120, 4283.\n\n On April 3, 2013, Nicholas submitted a final report\nto NOAA concerning EAA’s use of the grant. Notably,\npage 4 of the report stated the conference had been held in\nFebruary 2012, while page 17 stated that the conference\nhad been held from October 19 to 21, 2012. NOAA issued\na notice asking for clarification and for a list of students\nwho had been supported at the conference. Nicholas failed\nto file either a clarifying report regarding the date of the\nconference or a timely report regarding the disbursement\nof the grant. Finally, in November of 2013, Nicholas\n\n 30\n\fsubmitted the final Federal Financial Report in which she\ncertified, falsely, that the $50,000 had been used for a\nproject during the period from August 1, 2012 to\nDecember 30, 2012.\n\n B. The Blue Guardians Scheme\n In addition to functioning as the conduit for Lord’s\n$1 million loan to Fattah’s campaign, Lindenfeld’s\ncompany, Strategies, also performed services for the\ncampaign. The work resulted in indebtedness from FFM\nto Strategies of approximately $95,000. Fattah made\nseveral small payments, but failed to pay the full amount\ndue. Although Lindenfeld spoke to Fattah, Naylor and\nBowser about the debt, no payments were forthcoming.\nDuring a meeting in Fattah’s D.C. office, Fattah told\nLindenfeld “that [repayment] really wasn’t going to be\npossible because the campaign had been over for a long\ntime” and the funds were not available. JA1693. Fattah\nthen asked Lindenfeld if he could write off the debt on his\nFFM campaign finance reports. Id. Lindenfeld told Fattah\nthat as long as he was paid, it was not his business how\nFattah disclosed it on the campaign finance reports.\nJA1694.\n In lieu of repayment, Fattah suggested that\nStrategies could claim to be interested in setting up an\nentity to address environmental issues and ocean pollution\nalong the coastline and in the Caribbean. Fattah explained\nthat creating such an entity would make it possible to\nobtain an appropriation from the government. Hearing\n 31\n\fthis, Lindenfeld knew he was not going to be paid by the\nFFM campaign, and was amenable to receiving money\nfrom an appropriation instead. At a later meeting,\nLindenfeld told Fattah that the name of the entity would\nbe “Blue Guardians.” Lindenfeld consulted with an\nattorney about creating Blue Guardians as an entity to\nreceive the federal grant. He emailed Fattah, asking\nquestions about how to complete an application to the\nHouse Appropriations Committee. Fattah provided\nsuggestions, and an application was eventually completed.\nIt indicated that Blue Guardians would be “in operation for\na minimum of ten years,” and, in accordance with Fattah’s\nguidance, requested $15 million in federal funds. JA1711–\n13.\n Lindenfeld submitted the application to Fattah’s\noffice in April of 2009. Afterward, a Fattah staffer\ncontacted Lindenfeld to suggest that he change his\nWashington, D.C., address to Philadelphia because that\nwas the location of Fattah’s district. Fattah later suggested\nto Lindenfeld that Brand might allow the use of his\nPhiladelphia office address, a plan to which Brand agreed.\n\n In February 2010, Lindenfeld submitted a second\napplication to the Appropriations Committee. In March,\nFattah submitted a project request using his congressional\nletterhead and seeking $3,000,000 for the “Blue\nGuardians, Coastal Environmental Education Outreach\nProgram.” JA6432. Within a month, Blue Guardians had\nboth articles of incorporation and a bank account. Around\n\n 32\n\fthat time, a news reporter contacted Lindenfeld to discuss\nthe new Blue Guardians entity. The inquiry made\nLindenfeld uncomfortable, and he ultimately decided to\nabandon the Blue Guardians project. He continued to seek\npayment from Fattah, to no avail.\n\n Nonetheless, having obtained Lindenfeld’s\nacquiescence to writing off the campaign’s debt to\nStrategies, Fattah started falsifying FFM’s campaign\nreports. Beginning in 2009 and extending through 2013,\nthe FFM campaign reports executed by Fattah and Bowser\nstated that Strategies made in-kind contributions of\n$20,000, until the debt appeared to have been paid in full.\n\n C. The Fattah–Vederman Bribery Scheme\n Vederman and Fattah were personal friends.\nVederman was a successful businessman who had also\nserved in prominent roles in the administrations of Ed\nRendell when he was Mayor of Philadelphia and Governor\nof Pennsylvania. In November of 2008, Vederman was a\nsenior consultant in the government and public affairs\npractice group of a Philadelphia law firm. His assistance\nto the FFM campaign included paying for rented vans used\nin the get-out-the-vote effort.\n\n After Fattah’s electoral defeat, the campaign still\nowed more than $84,000 to a different law firm for\nservices performed for the campaign. Vederman\napproached that firm in the summer of 2008 asking if it\nwould forgive FFM’s debt. Negotiations resulted in a\n 33\n\fcommitment from FFM to pay the firm $30,000 by the end\nof 2008 in exchange for forgiveness of $20,000, all of\nwhich would appear on the FFM campaign finance report.\nVederman’s efforts also led to payment by Fattah of an\nadditional $10,000 in 2009 to the law firm, in exchange\nfor additional forgiveness of $20,000 of debt. It was not\nlong after Vederman’s successful efforts to lower Fattah’s\ncampaign debt, that Fattah wrote a letter to U.S. Senator\nRobert P. Casey recommending Vederman for an\nambassadorship.\n\n At some point in 2010, Vederman again intervened\non behalf of the FFM campaign. FFM remained in debt to\nan advertising and public relations firm owned by Robert\nDilella. By late 2011, Vederman and Dilella had worked\nout a settlement to resolve the outstanding debt. Pursuant\nto that settlement, Dilella received partial payment from\nthe FFM campaign: $25,000 in satisfaction of a $55,000\ndebt. Dilella testified at trial that he would not have agreed\nto retire a portion of the debt had he known the FFM\ncampaign was paying college tuition for Fattah’s son.\n Vederman helped Fattah financially in other ways.\nBefore the 2006 FFM campaign, Fattah and his wife,\nRenee Chenault-Fattah, sponsored a young woman named\nSimone Muller to live with them as an au pair exchange\nvisitor. Muller was from South Africa, and her J-1 visa\nallowed her to serve as a nanny and to study in the United\nStates. Muller later applied for and received a second visa,\nan F-1 student visa that indicated she had been accepted as\n\n 34\n\fan international student at the Community College of\nPhiladelphia. The application indicated that Muller would\nagain be residing with the Fattahs. Notwithstanding this\nliving arrangement, Fattah identified Vederman as the\nperson who would be paying for Muller’s trip to the\nUnited States.\n By the beginning of 2010, Muller wished to transfer\nto Philadelphia University. This required her to submit\nverification that funds were available to pay for her study.\nAlthough the Fattahs were Muller’s sponsors, Fattah\nexplained to the University’s Dean of Enrollment Services\nthat he was submitting a letter of secondary support from\nVederman. JA3754, 3763–65, 6504. Without Vederman’s\nJanuary 2010 letter of support, the University would not\nhave admitted Muller. In addition to this pledge of support,\nVederman paid $3,000 of Muller’s tuition. Shortly\nthereafter, Fattah resumed his efforts to secure an\nambassadorship for Vederman.\n\n In February of 2010, Fattah staffer Maisha Leek\ncontacted Katherine Kochman, a scheduler for White\nHouse Chief of Staff Rahm Emanuel. Leek requested a\ntelephone conference with Emanuel, Rendell, and Fattah\nto discuss Vederman’s “serving his country in an\ninternational capacity.” JA2893. In a follow-up email on\nMarch 26, Leek sent documents to Kristin Sheehy, a\nsecretary to White House Deputy Chief of Staff James\nMessina. The documents included Fattah’s 2008 letter to\nSenator Casey and Vederman’s biography. After\n\n 35\n\fparticipating in a telephone conference about Vederman\nwith Fattah and Rendell, Messina sent Vederman’s\nbiography to the White House personnel office for\nconsideration.\n\n As the April 2010 tax deadline approached, Fattah\nstill owed the City of Philadelphia earned income tax in\nthe amount of $2,381. Just days before the filing deadline,\nVederman gave a check to Chip Fattah for $3,500. The\nyounger Fattah quickly deposited $2,310 into his father’s\nbank account. Fattah paid his tax bill on April 15. Without\nChip’s deposit into his father’s bank account, the older\nFattah would not have had sufficient funds to pay his tax\nbill.\n On October 30, 2010, Vederman gave Chip another\ncheck, this one for $2,800. That same day, Fattah hand-\ndelivered a letter to President Obama recommending\nVederman for an ambassadorship. A few weeks later,\nFattah’s staffer, Leek, sent the letter that Fattah had given\nto President Obama to Messina’s office. That letter\npointed out that both Rendell and Fattah had sent letters\non behalf of Vederman, and that he was an\n“unquestionably exceptional candidate for an\nambassadorship.” JA6291–92.\n\n Fattah’s efforts to secure Vederman an\nambassadorship were unsuccessful. Fattah then shifted\ngears and sought to secure Vederman a position on a\nfederal trade committee. Fattah approached Ron Kirk, who\nserved as U.S. Trade Representative, and asked him to\n 36\n\fspeak with a constituent. In May of 2011, Leek followed\nup on that discussion by emailing Kirk and asking him to\nmeet with Vederman. Kirk met with Vederman on June 5,\n2011 and explained to him the role of the trade advisory\ncommittees. Although the two men “had a very nice\nconversation,” JA 3566, it soon became “pretty apparent\nto [Kirk and his staff] that [serving on a trade advisory\ncommittee was] not what Mr. Vederman was interested\nin.” JA3567. As Kirk put it, “it was obvious that\n[Vederman] was looking for something perhaps more\nrobust in his mind or . . . higher profile than one of our\nadvisory committees.” Id. Given Vederman’s lukewarm\ninterest, no appointment to an advisory committee was\nforthcoming.\n In late December 2011, the Fattahs applied for a\nmortgage so they could purchase a second home in the\nPoconos. Shortly after applying for the mortgage, Fattah\nemailed Vederman, offering to sell him his wife’s 1989\nPorsche for $18,000. Vederman accepted the offer. The\nnext day, Vederman wired $18,000 to Fattah’s Wright\nPatman Federal Credit Union account.\n\n The Credit Union Mortgage Association (CUMA)\nacted as the loan processing organization for the home\nmortgage. Because CUMA is required to verify the source\nof any large deposits, CUMA’s mortgage loan processor,\nVictoria Souza, contacted Fattah on January 17, 2012, to\nconfirm the source of the $18,000. Fattah informed Souza\nthat the $18,000 represented the proceeds of the Porsche\n\n 37\n\fsale. Souza requested documentation, including a signed\nbill of sale and title.\n That same day, Bowser emailed Vederman a blank\nbill of sale for the Porsche. After Vederman signed the bill\nof sale, Fattah forwarded it to Souza. The bill of sale was\ndated January 16, 2012, which was the day before Souza\nhad requested the documentation. It bore the signatures of\nRenee Chenault-Fattah and Herbert Vederman, with\nBonnie Bowser as a witness.\n\n Fattah also provided Souza with a copy of the\nPorsche’s title. It was dated the same day it was sent to\nSouza, and bore signatures of Chenault-Fattah as the seller\nand Vederman as buyer, along with a notary’s stamp.\nNeither Vederman nor Chenault-Fattah actually appeared\nbefore the notary.\n\n Vederman never took possession of the Porsche.\nRenee Chenault-Fattah continued to have the Porsche\nserviced and insured long after the purported sale had\ntaken place. Moreover, the Porsche remained registered in\nChenault-Fattah’s name, and was never registered to\nHerbert Vederman. When FBI agents searched the\nFattahs’ home in 2014, the Porsche was discovered in the\nFattahs’ garage.\n\n On January 24, 2012, the Fattahs wired $25,000 to\nthe attorney handling the escrow account for the purchase\nof the vacation home. Without the $18,000 transfer from\n\n 38\n\fVederman, the Fattahs would not have had sufficient funds\nin their bank accounts to close on the home.\n Around the same time that the Fattahs were\npurchasing the house in the Poconos, Fattah’s Philadelphia\noffice hired Vederman’s longtime girlfriend, Alexandra\nZionts. Zionts had long worked for a federal magistrate\njudge in Florida. Near the end of 2011, the magistrate\njudge retired, leaving Zionts ten months shy of obtaining\nthe necessary service required to receive retirement\nbenefits. If Zionts could find another job in the federal\ngovernment, her benefits and pension would not be\nadversely affected. Vederman assisted Zionts in her job\nsearch, which included calling Fattah. Fattah hired her, a\nmove that put his congressional office overbudget. Zionts\nworked in Fattah’s office for only about two months,\nleaving to work for a congressman from Florida.\n\n Tia Watson, who performed constituent services for\nFattah and worked on the same floor as Zionts in Fattah’s\ndistrict office, testified she had no idea what work Zionts\nperformed. Although Zionts contacted Temple University\nabout archiving Fattah’s papers from his career in both the\nstate and federal government, an employee from Temple\nUniversity observed that Zionts’ work contributed nothing\nof value to the papers project.\n\n D. The Indictment and Trial\n Fattah’s schemes eventually unraveled. On July 29,\n2015, a federal grand jury in the Eastern District of\n 39\n\fPennsylvania returned a twenty-nine count indictment\nalleging that Fattah and his associates had engaged in a\nvariety of criminal acts. Fattah, Vederman, Nicholas,\nBrand, and Bowser were charged with unlawfully\nconspiring to violate the Racketeer Influenced and Corrupt\nOrganizations Act (RICO), 18 U.S.C. § 1962(d). In\naddition to the RICO charge, the indictment alleged that\nFattah and certain co-defendants had unlawfully conspired\nto commit wire fraud, 18 U.S.C. §§ 1343, 1349; honest\nservices fraud, 18 U.S.C. §§ 1343, 1346, 1349; mail fraud,\n18 U.S.C. §§ 1341, 1349; money laundering, 18 U.S.C.\n§ 1956; and to defraud the United States, 18 U.S.C. § 371.\nSeveral defendants were also charged with making false\nstatements to banks, 18 U.S.C. § 1014; falsifying records,\n18 U.S.C. § 1519; laundering money, 18 U.S.C. § 1957;\nand engaging in mail, wire, and bank fraud, 18 U.S.C.\n§§ 1341, 1343, and 1344.\n\n The RICO charge alleged that the defendants and\nother co-conspirators constituted an enterprise aimed at\nsupporting and promoting Fattah’s political and financial\ninterests. The efforts to conceal the $1 million Lord loan\nand its repayment are at the heart of the RICO conspiracy\nand the Fattah for Mayor scheme. The indictment further\nalleged that the RICO enterprise involved: (1) the scheme\nto satisfy an outstanding campaign debt by creating the\nfake “Blue Guardians” nonprofit; and (2) the bribery\nscheme to obtain payments and things of value from\nVederman in exchange for Fattah’s efforts to secure\nVederman an appointment as a United States Ambassador.\n 40\n\f A jury trial, before the Honorable Harvey Bartle III\nof the Eastern District of Pennsylvania, began on May 16,\n2016, and lasted about a month. 7 Judge Bartle charged the\njury on Wednesday, June 15, 2016, and deliberations\nbegan late that afternoon. The following day, after\ndeliberating for only four hours, the jury sent a note to the\njudge. Written by the foreperson, the note read:\n Juror Number 12 refuses to vote by the letter\n of the law. He will not, after proof, still\n change his vote. His answer will not change.\n He has the 11 of us a total wreck knowing that\n we are not getting anywhere in the hour of\n deliberation yesterday and the three hours\n today. We have zero verdicts at this time all\n due to Juror Number 12. He will not listen or\n reason with anybody. He is killing every\n other juror’s experience. We showed him all\n the proof. He doesn’t care. Juror Number 12\n has an agenda or ax to grind w/govt.\nJA5916.\n\n Shortly after receiving the foreperson’s note, the\nCourt received a second communication—a note signed\n\n\n\n 7\n The District Court dismissed one charge prior to\ntrial: an individual money laundering count against\nNicholas.\n 41\n\fby nine jurors, including the foreperson. The second note\nread:\n We feel that [Juror 12] is argumentative,\n incapable of making decision. He constantly\n scream [sic] at all of us.\nId.\n Judge Bartle met with counsel in his chambers and\nadvised them of his intention to voir dire both the\nforeperson and Juror 12 in an effort to determine whether\nthe juror was deliberating as required by his oath. The\nJudge also indicated that he would “stay away from the\nmerits of the case,” and that whether he would voir dire\nmore jurors “remain[ed] to be seen.” JA5917.\n Counsel for the defendants objected to the Court’s\nproposed inquiry. As a group, they indicated that while the\nnote could be read as suggesting “a flat refusal to\ndeliberate,” they were of the opinion that it sounded “more\nin the manner of a disagreement over the evidence.”\nJA5918. Nicholas’s counsel specifically argued that\nquestioning the jurors so quickly after the start of\ndeliberations would send a message that differences of\nopinion among a block of jurors could be resolved by\ncomplaining to the Court. Defense counsel acknowledged\nthat the case law gave Judge Bartle wide discretion on how\nto proceed, but suggested that a “less intrusive” course of\naction was preferred. JA5918–19. They collectively urged\n\n 42\n\fthe Court to do nothing more than remind the jurors of\ntheir duty to deliberate.\n The Government agreed with Judge Bartle’s\nproposed voir dire. In the prosecution’s view, the Court\nhad already given proper instructions to the jury on their\nduty to deliberate. The Government further argued that if\nJuror 12 had exhibited bias, as suggested in the notes, he\nwould have lied during the voir dire process and his\nrefusal to deliberate would be “further evidence of that and\nhis unsuitability as a juror.” JA5921.\n\n With all counsel present, and over defense counsel’s\nobjections, Judge Bartle ultimately questioned five jurors\nin chambers. He questioned Juror 2 (the foreperson), Juror\n12 (the subject of the complaints), Juror 3, Juror 6, and\nJuror 1.\n\n Judge Bartle began each voir dire by informing the\njuror that he would ask a series of questions, but would not\ninquire into the merits of the case or how any juror was\nvoting. Each juror was placed under oath, and Judge Bartle\nasked, among other questions, whether screaming was\noccurring; whether the jurors were discussing the\nevidence; whether Juror 12 was placing his hands on other\njurors; and whether Juror 12 was unwilling to follow his\ninstructions.\n The foreperson acknowledged that he had written\nthe initial note during lunch earlier that day. He stated that\nJuror 12 was not willing to follow the law, but instead\n 43\n\f“want[ed] to add his own piece of the law . . . which has\nnothing to do with it.” JA5927–28. The foreperson further\ntestified that Juror 12 “was standing up screaming” and\nthat “[i]t was everybody pretty much against [Juror 12].”\nJA5929. He testified that Juror 12 “has his own agenda,”\nand that Juror 12 put his hand on another juror. JA5930.\nThe foreperson also stated that the jury had discussed only\na single count since the day before, and that they were still\ndiscussing it. When the District Court responded that the\njurors should understand that they could take as much time\nas they needed, the foreperson responded: “I understand\nthat. . . . [W]e all understand it. But we feel that he’s just—\nhe’s got another agenda.” JA5934.\n Judge Bartle advised counsel that he considered this\n“a very serious situation” and that he would proceed to\nvoir dire Juror 12. JA5937. Fattah’s counsel renewed his\nobjection to questioning Juror 12, which the Court\noverruled. Brand’s counsel argued that because the Court\nhad decided to voir dire Juror 12, it should also voir dire\nan additional juror. The Court agreed to do so.\n When the Court questioned Juror 12, he admitted to\nhaving “yelled back” at others, but only when they raised\ntheir voices to him. JA5939. Juror 12 contended that he, in\nfact, was “the only one” deliberating. Id. When an initial\nvote was taken the previous afternoon, his vote “was\ndifferent than everybody else’s.” Id. Juror 12 explained to\nthe other jurors why his vote was different, bringing up\nspecific evidence. In response, the other jurors said “that\n\n 44\n\fdoesn’t mean anything” and “pointed to the indictment.”\nJA5940. Juror 12 told the other jurors that the indictment\nis not evidence. Id. In response, the others “threatened to\nhave [him] thrown off.” Id.\n\n Juror 12 testified that a similar sequence of events\nhad taken place that morning. After a brief period of\ndeliberations, another vote was taken, and with the same\nresult as the previous afternoon. A discussion ensued, and\nthe other jurors again “point[ed] to the indictment.” Id.\nJuror 12 told them to “read the charge,” “[t]he indictment\nis not evidence.” Id. They read the charge, and Juror 12\nagain attempted to explain his view, but the other jurors\npaid little attention. Accordingly, Juror 12 told the others\nthat if they did not want him there, he “[didn’t] want to be\n[there]”—he would be “[o]kay with it” if they wanted him\ntaken off the jury. JA5941.\n Upon hearing this testimony, Judge Bartle again\nasked about the tone of deliberations. Juror 12 repeated\nthat he raised his voice only in response to others who did\nso—he did “not want to yell at anybody.” JA5942. Judge\nBartle then asked whether he had touched other jurors.\nJuror 12 replied that he had not hurt anyone. When asked\nif he had put his hand on anybody’s shoulder, Juror 12\nanswered: “I couldn’t remember to be honest with you.”\nJA5946.\n\n Following Juror 12’s voir dire, the Court summoned\nJuror 3 to chambers. Juror 3 testified that, after discussion\nof a particular count, there was one juror at odds with the\n 45\n\fothers. According to Juror 3, “the rest of the jurors\npounced on the gentleman with the . . . dissenting\nopinion.” JA5948. Juror 3 testified that Juror 12 “got very\ndefensive and just a little bit [] impatient” and that “the\nother jurors were very impatient with him.” Id. Juror 3 did\nnot recall witnessing Juror 12 putting his hand on any\nother jurors.\n\n The Government requested that the Court voir dire\nanother juror. Defense counsel objected, claiming that the\nquestioning “threaten[ed] . . . the entire deliberative\nprocess.” JA5949–50. Judge Bartle reminded counsel that\nhe had the authority to question each juror, and called for\nvoir dire of Juror 6.\n Juror 6 testified that the jury had been discussing the\ncase and reviewing the evidence, but that Juror 12 “wants\nto be seen” and was “being obstinate.” JA5951–52.\nAccording to Juror 6, Juror 12 “may not agree” with the\nconclusion of other jurors but “doesn’t give valid reasons\nas to why he may disagree with the charge.” JA5952. Juror\n6 also revealed that Juror 12 was the first to raise his voice,\nand that he may have touched her and another juror. When\nasked to clarify what she meant by Juror 12 disagreeing\nwith “the charge,” Juror 6 testified that Juror 12 was\n“reading maybe too deeply into it and putting his own\nemotions into it instead of just looking at what it says [and]\nwhat the facts are.” JA5952, 5955. According to Juror 6,\nJuror 12 “just continues to read past that into his own mind\nof what he feels it should be.” JA5955. Juror 6 testified\n\n 46\n\fthat Juror 12’s “justification for some of his responses [did\nnot] seem to relate to what the matter [was] before\n[them].” JA5957.\n Judge Bartle chose to hear from yet another juror.\nJuror 1 was called and informed the Court and counsel that\nthe jury “really [hadn’t] been able to even start the\ndeliberation process” in light of the disruptive behavior of\n“one particular individual.” JA5958–59. The particular\nindividual, according to Juror 1, was “very opinionated”\nand “[came] into the process with his view already\nestablished, refusing to even listen to any of the evidence\n. . . [being] very forceful . . . standing up, yelling, pointing\nhis finger.” JA5959. When asked if this individual was\nwilling to follow the Court’s instructions, Juror 1 testified\nthat he “pours [sic] over the documents very well” but that\nhe was adding other factors to answer the question on the\nverdict form, such as “what did this person feel.” JA5961.\nWhen Judge Bartle advised that intent was an appropriate\nconsideration, Juror 1 agreed but said that Juror 12 was\n“trying to investigate . . . going way beyond the scope” of\nthe evidence before them. JA5961–62. Juror 12, he said,\n“has an opinion and that opinion is established.” JA5962.\nHe stated that Juror 12 was “not willing to listen to any\nsort of reason or any sort of what everyone else is saying”\nbut instead, was “trying to force everyone else to get to his\npoint of view.” Id. “[I]f he feels like he’s not getting there,\nhe gets louder and louder and points and puts his hand on\nyour shoulder . . . .” Id.\n\n 47\n\f After questioning the five jurors (Jurors 1, 2, 3, 6,\nand 12), Judge Bartle heard argument from counsel. The\nattorney for the Government pointed out that the Court\nwould have to make a credibility determination because\nJuror 12 stated that he did not recall touching anyone. In\nthe Government’s view, Juror 12 was disrupting the\nprocess and should be removed. Defense counsel\ndisagreed. They argued that Juror 12 was conscientious\nand was engaging with the evidence. They pointed out that\ndespite the testimony that Juror 12 was reading too deeply\ninto the instructions or introducing new factors for the jury\nto consider, Juror 6 had testified that the jurors “talked it\nthrough” and resolved the concern. JA5965. Defense\ncounsel argued that the jury was discussing intent, an issue\nthat was at the heart of the case. Defense counsel perceived\nno breakdown in deliberations and argued that dismissal\nwould be premature. They suggested, instead, that the\nCourt provide a supplemental instruction.\n\n Judge Bartle decided to adjourn for the afternoon.\nBut before he left the courtroom, defense counsel brought\ntwo matters to his attention. First, in light of testimony\nduring the voir dire, they asked that the jury be\nreinstructed that the verdict form and indictment were not\nevidence. Second, they apprised the Judge of the standard\nfor juror dismissal set forth in United States v. Kemp, 500\nF.3d 257 (3d Cir. 2007). Defense counsel stated that under\nKemp, a request to discharge a juror must be denied if there\nis a possibility that the request stems from the juror’s view\nof the evidence. Judge Bartle expressed hesitation on\n 48\n\freinstructing the jury, but agreed that Kemp would control\nhis determination as to whether dismissal was appropriate.\n With the following morning came a new revelation.\nWith counsel in chambers, the Judge informed them that\n“additional significant evidence” had come to light since\nthe previous day’s recess. JA5980. He placed his\ncourtroom deputy under oath, and she proceeded to testify\nto an exchange that had occurred the previous day as she\nwas escorting Juror 12 back to the jury room after he had\nbeen voir dired. According to the deputy, Juror 12 stopped\nher in the hallway, placed his hand on her shoulder, and\nlooked her “straight in the eye.” JA5981. He then said:\n“I’m going to hang this jury.” Id. The deputy then related\nthat before any further conversation could take place\nbetween Juror 12 and the deputy, Judge Bartle summoned\nJuror 12 back to his chambers. Later that day, however,\nJuror 12 and the courtroom deputy had another exchange.\nShe testified that after all five jurors had been questioned,\nJuror 12 emerged from the jury room and told her “I really\nneed to talk to you.” JA5982. She informed Judge Bartle\nand counsel that Juror 12 “said more about how they’re\ntreating him and what he’s saying to them.” Id. He flatly\nstated that “it’s going to be 11 to 1 no matter what.” Id.\n\n There were no follow-up questions for the deputy.\nInstead, defense counsel suggested that what Juror 12 may\nhave meant was that he was willing to hang the jury\nbecause of a lack of evidence. They requested that Juror\n12 be asked about his comments to the deputy.\n\n 49\n\f After once again summoning Juror 12 to his\nchambers, the Judge advised him that “[s]ome questions\nhave arisen” about what he may have done after being voir\ndired the previous day. JA5985. Juror 12 acknowledged\nhaving conversations with the courtroom deputy. When\nasked “what happened” and “[w]hat occurred,” Juror 12\nresponded: “Basically, I said that there was a lot of name\ncalling going on.” JA5985. He said comments had been\nmade by other jurors about his service in the military. He\nspecifically referred to other jurors’ suggesting that he had\npossibly “hit [his] head . . . hard a few times” while\nserving in a parachute regiment. JA5986. He testified he\nhad conveyed these comments to the deputy and that he\nfound them offensive. When asked if he said anything else\nto the deputy, Juror 12 responded: “I may have. I really\ncan’t recall.” JA5987. And when Judge Bartle followed up\nby asking if he could recall anything else that he said to\nthe deputy, Juror 12 simply replied: “No. To me, that was\nthe most important thing.” Id. Juror 12 was then excused\nfrom chambers.\n Defense counsel next requested that the juror be\nasked directly whether he told the courtroom deputy that\nhe was going to “hang this jury.” JA5988. Juror 12 was\nrecalled to chambers, and the following back and forth\ntook place:\n\n The Court: You may be seated. And, of\n course, [Juror 12], you know you’re under\n oath here from yesterday?\n\n 50\n\f Juror 12: Yes, sir.\n The Court: . . . Did you say to [the courtroom\n deputy] that you’re going to hang this jury?\n Juror 12: I said I would.\n The Court: You did?\n Juror 12: I did. I said—I told her—I said, we\n don’t agree; I’m not just going to say guilty\n because everybody wants me to, and if that\n hangs this jury, so be it.\n ....\n Juror 12: I did say that, sir.\n The Court: You didn’t remember that before?\n Juror 12: I’m more concerned about people\n spitting on my military record.\n The Court: Did you say that you’d hang the\n jury no matter what?\n Juror 12: If they do—if we cannot come to—\n The Court: No. The question is what you said\n to her. Did you say to her you would hang the\n jury no matter what?\n Juror 12: I can’t really remember that. I did\n say that if we didn’t—a person—no matter\n what, I can’t recall that exactly.\n The Court: All right. Thank you very much.\n You can wait just out there in the anteroom.\nJA5989–90.\n\n Defense counsel continued to oppose Juror 12’s\ndismissal. They argued that the juror’s concern was about\n\n 51\n\fthe evidence, and that his comments to the courtroom\ndeputy reflected a conviction that “he’s not going to agree\njust because others want him to agree.” JA5991. They also\nargued that nothing should be made of Juror 12’s failure\nto mention the comments when initially questioned by the\nCourt, and that a supplemental instruction was all that was\nwarranted given the early stage of the deliberations.\n\n The Government strongly disagreed. The Assistant\nUnited States Attorney argued that Juror 12 “should\nabsolutely be removed” because “his demeanor ha[d]\ndemonstrated a hostility . . . both to the other jurors and to\nthe court.” JA5993. The Government also suggested that\nJuror 12’s comments that he would hang the jury meant\nthat he was not participating in the deliberations and was\nignoring the evidence and the law.\n\n Ruling from the bench, Judge Bartle announced:\n I find [the deputy clerk] to be credible. I find\n [Juror 12], not to be credible. I find that [Juror\n 12] did tell [the deputy clerk] that he was\n going to hang this jury no matter what.\n There have been only approximately\n four hours of deliberation. There’s no way in\n the world he could have reviewed and\n considered all of the evidence in the case and\n my instructions on the law.\n I instructed the jury to deliberate,\n meaning to discuss the evidence; obviously,\n to hold onto your honestly held beliefs, but at\n 52\n\f least you have to be willing to discuss the\n evidence and participate in the discussion\n with other jurors.\n Juror number 12 has delayed,\n disrupted, impeded, and obstructed the\n deliberative process and had the intent to do\n so. I base that having observed him, based on\n his words and his demeanor before me.\n He wants only to have his own voice\n heard. He has preconceived notions about the\n case. He has violated his oath as a juror.\n And I do not believe that any further\n instructions or admonitions would do any\n good. I think he’s intent on, as he said,\n hanging this jury no matter what the law is,\n no matter what the evidence is.\n Therefore, he will be excused, and I\n will replace him with the next alternate . . . .\n\nJA5994–95.\n In response, defense counsel moved for a mistrial,\nwhich the judge promptly denied. He then informed the\nreconstituted jury that deliberations would need to start\nover, and reinstructed them on certain points of law,\nincluding that the verdict slip does not constitute evidence.\n\n Judge Bartle elaborated upon his decision to remove\nJuror 12 in two post-trial memorandum opinions. In the\nfirst, ruling on a media request for the sealed transcripts,\nhe explained:\n 53\n\f Here, there is no doubt that Juror 12\n intentionally refused to deliberate when he\n declared so early in the process that he would\n hang the jury no matter what. This finding\n was predicated on the admission of Juror 12\n as reported by the court’s deputy clerk. The\n facts became clear to the court after hearing\n the credible testimony of the deputy clerk and\n the less credible testimony of Juror 12. The\n demeanor of Juror 12 before the court\n confirmed the court’s findings.\n\nGSA23–24. The second opinion addressed motions for\nbail pending appeal from Nicholas and Brand. GSA25.\nThere, Judge Bartle explained:\n\n The law is well-settled that the court has\n discretion to act as it did under these\n circumstances. See United States v. Kemp,\n 500 F.3d 257, 304 (3d Cir. 2007). The court,\n after taking testimony, specifically found that\n the juror, following only a few hours of\n deliberation, stated to the court’s courtroom\n deputy clerk that he would hang this jury no\n matter what. He could not possibly have\n reviewed all of the law and evidence of this\n five-week trial at the time he made his\n remark. The court examined the deputy clerk\n and the juror under oath in the presence of\n counsel for all parties. The undersigned\n\n 54\n\f found the deputy clerk to be credible and the\n juror not to be credible. Based on the juror’s\n demeanor, it was clear he would not change\n his attitude and that his intent had been and\n would continue to be to refuse to deliberate\n in good faith concerning the law and the\n evidence.\n\nGSA32.\n After deliberating for approximately 15 hours, the\njury returned with its verdicts on June 21, 2016, finding\nthe defendants guilty on most counts. Fattah, Vederman,\nand Brand were convicted on all counts. The jury acquitted\nBowser on sixteen counts, but found her guilty of the\nbribery conspiracy and the associated charges of bank\nfraud, making false statements to a financial institution,\nfalsifying records, and money laundering (Counts 16, 19,\n20, 21 and 22). The jury also acquitted Nicholas of wire\nfraud (Count 24). See Nicholas Supp. App. (NSA) 36.\n The following week, on June 27, the Supreme Court\nissued its opinion in McDonnell v. United States, 136 S.\nCt. 2355 (2016). McDonnell provided new limitations on\nthe definition of “official acts” as used in the honest\nservices fraud and bribery statutes under which Fattah and\nVederman had been convicted. Id. at 2369–72. Fattah and\nVederman both moved to set aside their convictions. The\nDistrict Court “acknowledge[d] that under McDonnell our\ninstructions to the jury on the meaning of official act\nturned out to be incomplete and thus erroneous.” JA103.\n 55\n\fBut the Court held that “the incomplete and thus erroneous\njury instruction on the meaning of official acts did not\ninfluence the verdict on the bribery counts” and upheld the\nverdict on Counts 16–18 and 22–23. JA107, 121.\n\n Fattah, Vederman, and Bowser had more success\nwith their other post-verdict motions. The District Court,\nin a thoughtful opinion, granted relief under Federal Rule\nof Criminal Procedure 29, acquitting Vederman of the\nRICO conspiracy (Count 1) and Fattah, Vederman, and\nBowser of bank fraud, making false statements to a\nfinancial institution, and falsifying records (Counts 19, 20,\nand 21). JA37–139.\n This appeal followed. 8 The defendants raise a\nvariety of challenges to their convictions. All defendants\nbut Bowser challenge the District Court’s decision to\ndismiss Juror 12. Fattah and Vederman argue that the\nDistrict Court erred in upholding the jury’s verdict on the\nbribery and honest services fraud counts in light of the\nSupreme Court’s decision in McDonnell. Fattah, Brand\nand Nicholas challenge the sufficiency of the evidence\nunderlying the RICO conviction. Several of the defendants\ncontend the District Court erred in its instruction on intent\nand by sending the indictment out to the jury. There are\n\n\n\n8\n Fattah, Brand, Vederman, and Nicholas each filed a\ntimely notice of appeal, but Bowser did not challenge her\nconvictions.\n 56\n\falso several evidentiary challenges.9 The Government\ncross-appeals from the District Court’s judgment\nacquitting Fattah and Vederman on Counts 19 and 20,\narguing that the District Court erred in interpreting the\ndefinition of a “mortgage lending business” under 18\nU.S.C. § 27. We address these arguments in turn.\n\n We hold that the District Court erred in upholding\nthe jury verdict in light of McDonnell, and we will\ntherefore reverse and remand for retrial on Counts 16, 17,\n18, 22, and 23. We also hold that the District Court erred\n\n9\n Pursuant to Rule 28(i), “Fattah joins in the arguments of\nHerbert Vederman, Robert Brand, and Karen Nicholas to\nthe extent their arguments on appeal apply to Mr. Fattah.”\nFattah Br. 19 n.69. Federal Rule of Appellate Procedure\n28(i) provides that a defendant, “[i]n a case involving\nmore than one appellant . . . may adopt by reference a part\nof another’s brief.” Here, Fattah’s decision to join fails to\nspecify which of the many issues of his codefendants he\nbelieves worthy of our consideration. Rather, it appears\nthat he presumes we will scour the record and make that\ndetermination for him. This type of blanket request fails to\nsatisfy Rule 28(a)(5)’s directive requiring that the\n“appellant’s brief must contain . . . a statement of the\nissues presented for review.” Fed. R. App. P. 28(a)(5). We\nconclude that expecting the appellate court to identify the\nissues to be adopted simply results in the abandonment and\nwaiver of the unspecified issues. See Kost v. Kozakiewicz,\n1 F.3d 176, 182 (3d Cir. 1993).\n 57\n\fin acquitting Fattah and Vederman on Counts 19 and 20.\nBecause the jury’s verdict was supported by the evidence,\nwe will reinstate the convictions as to those counts. In all\nother respects, we will affirm the judgment of the District\nCourt.\n\n III. Juror Misconduct and Dismissal of Juror 12 10\n Defendant Fattah challenges the District Court’s\ndecision to conduct an in camera inquiry into alleged juror\nmisconduct and the ultimate dismissal of Juror 12. 11 We\nreject both challenges. The record reveals credible\nallegations of juror misconduct and a sufficient basis to\nsupport the finding that Juror 12 violated his oath.\n\n A. Investigation of Alleged Juror Misconduct\n We first consider whether the District Court erred in\nits handling of the two notes from jurors. A trial court’s\nresponse to allegations of juror misconduct is reviewed\nunder an abuse of discretion standard. United States v.\nBoone, 458 F.3d 321, 326 (3d Cir. 2006) (citing United\nStates v. Resko, 3 F.3d 684, 690 (3d Cir. 1993)). We\nconclude that the District Court did not abuse its discretion\n\n\n10\n The District Court had jurisdiction under 18 U.S.C.\n§ 3231. We have jurisdiction under 28 U.S.C. § 1291 and\n18 U.S.C. § 3742(a).\n11\n Vederman, Nicholas, and Brand adopt Fattah’s claim of\nreversible error concerning the dismissal of Juror 12.\n 58\n\fin addressing the issues raised in the jurors’ notes to the\nCourt.\n Trial courts are afforded discretion in responding to\nallegations of juror misconduct. This is so because “the\ntrial court is in a superior position to observe the ‘mood at\ntrial and the predilections of the jury.’ ” Resko, 3 F.3d at\n690 (quoting United States v. Chiantese, 582 F.2d 974,\n980 (5th Cir. 1978)). But this discretion is not unlimited.\nOnce the jury retires to deliberate, the confidentiality of its\ndeliberations must be closely guarded. An accused is\nconstitutionally entitled to be tried before a jury of his\npeers. As ordinary citizens, jurors are “expected to speak,\ndebate, argue, and make decisions the way ordinary people\ndo in their daily lives.” Pena-Rodriguez v. Colorado, 137\nS. Ct. 855, 874 (2017) (Alito, J., dissenting). To protect\nagainst intrusion into a defendant’s right to be judged only\nby fellow citizens, “the door to the jury room [is] locked.”\nId. at 875.\n In Boone, this Court considered the threshold for\nintervention by a trial judge who is presented with\nallegations of juror misconduct during the course of\ndeliberations. 458 F.3d at 327. We recognized that “[i]t is\nbeyond question that the secrecy of deliberations is critical\nto the success of the jury system.” Id. at 329. But that\nsecrecy abuts a competing interest—the jury’s proper\nexecution of its duties. That is, “a juror who refuses to\ndeliberate or who commits jury nullification violates the\nsworn jury oath and prevents the jury from fulfilling its\n\n 59\n\fconstitutional role.” Id. Recognizing these competing\ninterests, we declined in Boone to adopt a sweeping\nlimitation on a trial court’s ability to investigate\nallegations of misconduct during jury deliberations. See id.\nConsistent with the standard applied at other stages of\ncriminal proceedings, Boone teaches that “where\nsubstantial evidence of jury misconduct—including\ncredible allegations of jury nullification or of a refusal to\ndeliberate—arises during deliberations, a district court\nmay, within its sound discretion, investigate the\nallegations through juror questioning or other appropriate\nmeans.” Id.\n Fattah argues that the District Court had no basis to\nquestion any of the jurors. Fattah Br. 20. We disagree. In\nBoone, notes from the jury presented substantial credible\nevidence of misconduct. 458 F.3d at 330. Here, the initial\nnote from the foreperson alleged that Juror 12 “refuse[d]\nto vote by the letter of the law,” would “not listen or reason\nwith anybody,” and that he had “an agenda or ax to grind”\nwith the Government. JA5916. The note contained\nallegations of both a refusal to deliberate and a suggestion\nof nullification. A refusal to deliberate is a violation of a\njuror’s oath. Boone, 458 F.3d at 329 (citing United States\nv. Baker, 262 F.3d 124, 130 (2d Cir. 2001) (“It is well-\nsettled that jurors have a duty to deliberate.”)). Moreover,\nnullification—a juror’s refusal to follow the law—is a\nviolation of the juror’s sworn oath to render a verdict\naccording to the law and evidence. See United States v.\nThomas, 116 F.3d 606, 614–18 (2d Cir. 1997) (discussing\n 60\n\fboth “benevolent” and “shameful” examples of juror\nnullification, but “categorically reject[ing] the idea that, in\na society committed to the rule of law, jury nullification is\ndesirable or that courts may permit it to occur when it is\nwithin their authority to prevent”). The second jury note,\nsigned by nine jurors, supported the claim of misconduct\nby asserting that Juror 12 was “incapable of making\ndecision[s]” and was “constantly scream[ing]” at the other\njurors. JA5916–17. We conclude that the District Court\ndid not abuse its discretion in deciding to initially question\nJuror 2, and subsequently, Jurors 12, 3, 6 and 1.\n\n Fattah also challenges the scope of the District\nCourt’s questioning. He argues that the rights to an\nimpartial jury and to a unanimous verdict “would be\nrendered toothless if trial courts had free rein to question\njurors during deliberations.” Fattah Br. 36. Indeed, we\nacknowledged the legitimacy of such a concern in Boone.\nDespite adopting a modest “credible allegations” standard\nfor investigating misconduct, we “ke[pt] in mind the\nimportance of maintaining deliberative secrecy.” Boone,\n458 F.3d at 329. Fattah asserts that the trial court’s\nquestions to the five jurors were “intrusive and pointed”\nand “nothing like the questioning . . . approved in Boone.”\nFattah Br. 38. But Fattah does not elaborate on how, in his\nview, the questions posed by Judge Bartle specifically\nintruded into deliberative secrecy.\n\n To be sure, Judge Bartle’s questioning of each juror\nwas more extemporaneous than the juror questioning in\n\n 61\n\fBoone. There, the district court asked a single juror four\n“concise and carefully-worded” questions. 458 F.3d at\n330. Judge Bartle’s voir dire of each of the five jurors took\non a more conversational tone. We take no issue with that\napproach. The substance of the judge’s questions was\nlimited and mirrored that of questions we deemed\nappropriate in Kemp. There, the court conducted three\nrounds of questioning. In the first round, each juror was\nasked:\n (1) “Are you personally experiencing any\n problems with how the deliberations are\n proceeding without telling us anything about\n the votes as to guilt or innocence? If yes,\n describe the problem.” (2) “Are all the jurors\n discussing the evidence or lack of evidence?”\n (3) “Are all the jurors following the court’s\n instructions on the law?”\n\nKemp, 500 F.3d at 273. In the second and third rounds,\neach juror was asked:\n (1) “Is there any juror or jurors who are\n refusing to deliberate?” (2) “Is there any juror\n who is refusing to discuss the evidence or\n lack of evidence?” (3) “Is there any juror who\n is refusing to follow the Court’s\n instructions?”\nId. at 274. Here, Judge Bartle began his voir dire of each\njuror by stating that he did not wish for the juror to discuss\n 62\n\fthe merits of the case or to reveal the content of the\ndeliberations that had taken place. He asked the jurors\nwhether screaming was occurring, whether the jurors were\ndiscussing the evidence, whether Juror 12 was placing his\nhands on other jurors, and whether Juror 12 was unwilling\nto follow his instructions.\n Fattah points to no specific question posed or topic\ndiscussed that was inappropriate, and we see little to no\nsubstantive difference between the questions here and\nthose asked by the trial judge in Kemp. As in Kemp, “the\nDistrict Court took care to limit its questions to appropriate\nmatters that did not touch on the merits of the jury’s\ndeliberation, and expressly informed each juror on\nmultiple occasions that he or she should not reveal the\nsubstance of the deliberations.” Id. at 302 (citing United\nStates v. Edwards, 303 F.3d 606, 634 n.16 (5th Cir. 2002)).\n Fattah also argues that once the remarks of Juror 2\nand Juror 12 revealed no further evidence of misconduct,\nthe court had no basis to question other jurors. Fattah\nReply 19. Yet, our cases make clear that a trial court may,\nin its discretion, examine each juror. Kemp, 500 F.3d at\n302 (“We have recognized that there are times in which\nindividual questioning is the optimal way in which to root\nout misconduct.”). Indeed, “the District Court must utilize\nprocedures that will ‘provide a reasonable assurance for\nthe discovery of prejudice.’ ” Id. (quoting Martin v.\n\n\n\n 63\n\fWarden, Huntingdon State Corr. Inst., 653 F.2d 799, 807\n(3d Cir. 1981)). 12\n\n Judge Bartle, a very able and experienced district\njudge, was in the best position to determine what type of\ninquiry was warranted under the circumstances. We\nconclude that his questioning of the five jurors was not an\nabuse of discretion. See id. at 302.\n\n B. Dismissal of Juror 12\n Fattah, joined by Vederman, Brand, and Nicholas,\nstrongly contends that the District Court committed\nreversible error by dismissing Juror 12. “We review the\ndismissal of a juror for cause for abuse of discretion.”\n\n12\n Our cases do not suggest that a trial judge confronted\nwith allegations that a jury’s deliberations are being\nobstructed by one of its members should always resort to\ninterviewing jurors. Reinstructing the jury on its duty to\ndeliberate will often be the better course at the first sign of\ntrouble. Mere disagreement among jurors—even spirited\ndisagreement—is no ground for intervention.\nFurthermore, intrusive or leading questions about the\ndeliberative process may work against the twin goals of\nprotecting that process and ensuring that jurors remain\nfaithful to their oaths. We share the Eleventh Circuit’s\npreference of “err[ing] on the side of too little inquiry as\nopposed to too much.” United States v. Oscar, 877 F.3d\n1270, 1287 (11th Cir. 2017) (quoting United States v.\nAugustin, 661 F.3d 1105, 1133 (11th Cir. 2011)).\n 64\n\fKemp, 500 F.3d at 303. That deferential standard compels\nus to affirm.\n Rule 23(b) of the Federal Rules of Criminal\nProcedure permits a trial court to excuse a deliberating\njuror for good cause. See id. (citing Fed. R. Crim. P.\n23(b)). Good cause exists where a juror refuses to apply\nthe law, refuses to follow the court’s instructions, refuses\nto deliberate with his or her fellow jurors, or demonstrates\nbias. See Kemp, 500 F.3d at 305–06; United States v.\nOscar, 877 F.3d 1270, 1287 (11th Cir. 2017); Thomas, 116\nF.3d at 617. Good cause does not exist when there is\nreasonable but sustained disagreement about how a juror\nviews the evidence. The courts of appeals are emphatic\nthat trial courts “may not dismiss a juror during\ndeliberations if the request for discharge stems from\ndoubts the juror harbors about the sufficiency of the\ngovernment’s evidence.” Kemp, 500 F.3d at 303 (quoting\nUnited States v. Brown, 823 F.2d 591, 596 (D.C. Cir.\n1987)); see also Oscar, 877 F.3d at 1287 (same); United\nStates v. Symington, 195 F.3d 1080, 1087 (9th Cir. 1999);\nThomas, 116 F.3d at 622.\n\n To reinforce a defendant’s right to a unanimous\njury, we have adopted a high standard for juror dismissal.\nKemp, 500 F.3d at 304 & n.26. “[D]istrict courts may\ndischarge a juror for bias, failure to deliberate, failure to\nfollow the district court’s instructions, or jury nullification\nwhen there is no reasonable possibility that the allegations\nof misconduct stem from the juror’s view of the evidence.”\n\n 65\n\fId. at 304 (emphasis added). This “no reasonable\npossibility” standard is “by no means lax.” Id. Rather, “[i]t\ncorresponds with the burden for establishing guilt in a\ncriminal trial.” Id.\n\n We first applied this standard in Kemp, but have not\nhad occasion to do so since. There, the evidence\nsupporting the district court’s removal decision was\n“overwhelming.” 500 F.3d at 304. Ten jurors separately\nand consistently reported that a juror was improperly\nbiased, and did so only after three rounds of questioning\nand careful and correct instructions from the district court\nas to the distinction between appropriate skepticism and\nimpermissible bias. Id. at 304–05; see id. at 275–76\n(district court’s instruction). The testimony also showed\nthat the juror in question refused to deliberate or to discuss\nthe evidence with her fellow jurors. Id. at 305.\n Whether the evidence of misconduct in this case is\nas strong as that in Kemp is beside the point. After only\nfour hours of deliberations, Juror 12 stated unequivocally\nto the courtroom deputy that he was “going to hang” the\njury, and that it would be “11 to 1 no matter what.”\nJA5981–82 (emphasis added). These statements, coupled\nwith the District Court’s finding that Juror 12 lacked\ncredibility, provided a sufficient basis for Juror 12’s\ndismissal.\n\n As grounds for excusing Juror 12, the District Court\nfound that he refused to deliberate in good faith, “delayed,\ndisrupted, impeded, and obstructed the deliberative\n 66\n\fprocess and had the intent to do so,” JA5995, and that he\nwas “intent on . . . hanging this jury no matter what the law\nis, no matter what the evidence is.” Id. The District Court\ndetermined from this that Juror 12 had violated his oath as\na juror and that no further instructions or admonitions\ncould rehabilitate the juror. Id. The District Court based\nthese findings on personal observation, including Juror\n12’s words and demeanor, and making the specific finding\nthat Juror 12 was not credible. That finding is amply\nsupported by the record.\n\n In United States v. Abbell, 271 F.3d 1286, 1303 (9th\nCir. 2001), the Ninth Circuit recognized that “the\ndemeanor of the pertinent juror is important to juror\nmisconduct determinations” because the “juror’s\nmotivations and intentions are at issue.” That court\nemphasized, as we do, that a district judge is best situated\nto assess the demeanor of a juror. Id. Here, Juror 12 stated\nhe could not recall putting his hand on another juror’s\nshoulder, while his fellow jurors’ testimony was consistent\non this point. Juror 12 also failed, at first, to recall his\ntroubling statements to the courtroom deputy despite\nhaving made those statements only the previous afternoon.\nWhen questioned a second time and asked directly about\nthe statements, he admitted to saying that he would hang\nthe jury but claimed he could not “really remember”\nsaying “no matter what” the day before. JA5989–90. Juror\n12’s spotty recollection of the previous day’s events\nfurther supports the District Court’s finding that he was\nnot credible.\n 67\n\f Fattah argues that the credibility determination was\nnot, by itself, a sufficient reason to dismiss the juror\nbecause the record demonstrates more than a reasonable\npossibility that the complaints about his conduct stemmed\nfrom Juror 12’s own view of the Government’s case.\nFattah Reply Br. 11; Fattah Br. 25, 28. Fattah claims that\nthe District Court abused its discretion by dismissing Juror\n12 “on the basis of, in effect, six words the juror\npurportedly said to the court’s deputy after he was verbally\nattacked by other jurors.” Fattah Br. 24. According to\nFattah, the questioning of the other jurors “confirmed that\nthere were no legitimate grounds for removing juror 12.”\nId. at 26. We conclude otherwise.\n “A district court’s finding on the question whether\na juror has impermissibly refused to participate in the\ndeliberation process is a finding of fact to which\nappropriate deference is due.” Baker, 262 F.3d at 130.\nWhile district courts must apply a high standard for juror\ndismissal, their underlying findings are afforded\nconsiderable deference on appeal. Kemp, 500 F.3d at 304\n(citing Abbell, 271 F.3d at 1302–03). We will reverse only\nif the decision to dismiss a juror was “without factual\nsupport, or for a legally irrelevant reason.” Abbell, 271\nF.3d at 1302 (citation omitted).\n Here, the District Court had a legitimate reason for\nremoving Juror 12. Refusal to deliberate constitutes good\ncause for dismissal. Although the judge did not expressly\narticulate the Kemp standard when he announced that he\n\n 68\n\fwould dismiss Juror 12, he did acknowledge the “no\nreasonable possibility” standard in his discussion with\ncounsel. The unmistakable import of the District Court’s\nstatement from the bench is that there was no reasonable\npossibility that Juror 12’s intransigence was based on his\nview of the evidence. See Oscar, 877 F.3d at 1288 n.16.\n Fattah contends that there is no record support for\nthe finding that Juror 12 said “he was going to hang this\njury no matter what.” Fattah Br. 29. To be sure, the\ncourtroom deputy’s testimony is not that Juror 12 used the\nwords “hang this jury” and “no matter what” in the same\nsentence. She testified that Juror 12 first stated “I am going\nto hang this jury,” then later stated “it is going to be 11 to\n1 no matter what.” JA5981–82. This is a distinction\nwithout a difference. Likewise, Fattah challenges the\nDistrict Court’s finding that Juror 12 was determined to\nhang the jury “no matter what the law is” and “no matter\nwhat the evidence is.” Fattah Br. 29. Although there is no\nevidence that Juror 12 uttered the phrases “no matter what\nthe law is” or “no matter what the evidence is,” the District\nCourt was describing the import of Juror 12’s statements.\nThis was not error.\n Fattah expresses the concern that “[i]f jurors are\nasked the right questions or interrogated long enough, it\nwould not be difficult for a trial court to elicit testimony\nfrom [a] majority [of] jurors that can be held up as\nevidence of a dissenting juror’s bias or refusal to\ndeliberate.” Fattah Br. 22. He also worries that a group of\n\n 69\n\fjurors might have an incentive to rid themselves of a juror\nwho holds a different view. Id. These are valid concerns—\nbut no basis existed for such concerns in this case. Juror\n12’s own words provided most of the support for his\neventual dismissal. Furthermore, his statements were\nmade early in the deliberations, in a complex case, before\nany juror could reasonably be expected to have reached\nfinal verdicts on the twenty-nine counts before the jury.\n\n The able District Judge did not err in finding that\nJuror 12 refused to deliberate and therefore violated his\noath.\n\n IV. The District Court’s Instructions Under\n McDonnell\n On appeal, Fattah and Vederman renew their\nchallenge to the jury instructions given on Counts 3, 16,\n17, 18, 22, and 23, concerning the meaning of the term\n“official act” as used in the bribery statute (pursuant to\nwhich both were convicted) and the honest services fraud\nstatute (pursuant to which Fattah alone was convicted).\n\n In light of the Supreme Court’s opinion in\nMcDonnell v. United States, 136 S. Ct. 2355 (2016),\nreleased the week after the jury verdict, the District Court\nconceded that its instructions were incomplete and\nerroneous, at least as to Counts 16–18. Nevertheless, the\nDistrict Court held that the erroneous jury instructions had\nnot influenced the verdict on the bribery counts, and\ndeclined to set aside Fattah and Vederman’s convictions.\n 70\n\fAs to Counts 16–18 and 22–23, we disagree, and will\nreverse the District Court’s judgment. The District Court’s\njudgment with respect to Count 3, which did not involve\nVederman, will be affirmed. JA78–79.\n\n A. The McDonnell Framework\n In McDonnell, the Supreme Court interpreted the\nterm “official act” as defined in 18 U.S.C. § 201(a)(3). 136\nS. Ct. at 2368. The statute defines an “official act” as “any\ndecision or action on any question, matter, cause, suit,\nproceeding or controversy, which may at any time be\npending, or which may by law be brought before any\npublic official, in such official’s official capacity, or in\nsuch official’s place of trust or profit.” 18 U.S.C.\n§ 201(a)(3). The McDonnell Court distilled this definition\ninto two requirements:\n First, the Government must identify a\n “question, matter, cause, suit, proceeding or\n controversy” that “may at any time be\n pending” or “may by law be brought” before\n a public official. Second, the Government\n must prove that the public official made a\n decision or took an action “on” that question,\n matter, cause, suit, proceeding, or\n controversy, or agreed to do so.\n\n136 S. Ct. at 2368. Applying this two-step test to Governor\nRobert McDonnell’s convictions, the Supreme Court\nconcluded that “the jury was not correctly instructed on\n 71\n\fthe meaning of ‘official act,’ ” and as a result, “may have\nconvicted Governor McDonnell for conduct that is not\nunlawful.” Id. at 2375. Given that uncertainty, the Court\n“[could not] conclude that the errors in the jury\ninstructions were ‘harmless beyond a reasonable doubt.’ ”\nId. (quoting Neder v. United States, 527 U.S. 1, 16 (1999)).\nThe Supreme Court, therefore, vacated Governor\nMcDonnell’s convictions. Id.\n\n McDonnell lays out a clear path for the Government\nto follow in proving that an accused has performed an\n“official act.” First, the Government must “identify a\n‘question, matter, cause, suit, proceeding or controversy’\nthat ‘may at any time be pending’ or ‘may by law be\nbrought’ before a public official.” 136 S. Ct. at 2368\n(quoting 18 U.S.C. § 201(a)(3)). This first step is divided\ninto two sub-components. In Step 1(A), the Government\nmust “identify a ‘question, matter, cause, suit, proceeding\nor controversy.’ ” Id. Step 1(B) then clarifies that the\nidentified “question, matter, cause, suit, proceeding or\ncontroversy” be one that “ ‘may at any time be pending’ or\n‘may by law be brought’ before a public official.” Id.\n\n Under Step 1(A), a “question, matter, cause, suit,\nproceeding or controversy” must be “a formal exercise of\ngovernmental power that is similar in nature to a lawsuit\nbefore a court, a determination before an agency, or a\nhearing before a committee.” Id. at 2372. Importantly, “a\ntypical meeting, telephone call, or event arranged by a\n\n\n 72\n\fpublic official” does not qualify as such a formal exercise\nof governmental power. Id. at 2368.\n Step 1(B) then requires us to ask whether the\nqualifying “question, matter, cause, suit, proceeding or\ncontroversy” was one that “ ‘may at any time be pending’\nor ‘may by law be brought’ before a public official.” Id.\nAs the McDonnell Court clarified, “ ‘[p]ending’ and ‘may\nby law be brought’ suggest something that is relatively\ncircumscribed—the kind of thing that can be put on an\nagenda, tracked for progress, and then checked off as\ncomplete.” Id. at 2369; accord United States v. Repak, 852\nF.3d 230, 252 (3d Cir. 2017) (quoting McDonnell, 136 S.\nCt. at 2369). By contrast, matters described at a high level\nof generality—for example, “[e]conomic development,”\n“justice,” and “national security”—are not sufficiently\n“focused and concrete.” McDonnell, 136 S. Ct. at 2369.\n\n In McDonnell, the Court concluded that at least\nthree questions or matters identified by the Fourth Circuit\nwere sufficiently focused:\n (1) whether researchers at any of Virginia’s\n state universities would initiate a study of [a\n drug]; (2) whether the state-created Tobacco\n Indemnification and Community\n Revitalization Commission would allocate\n grant money for the study of [a chemical\n compound]; and (3) whether the health\n insurance plan for state employees in\n\n 73\n\f Virginia would include [a specific drug] as a\n covered drug.\nId. at 2370 (internal quotations omitted) (quoting United\nStates v. McDonnell, 792 F.3d 478, 515–16 (4th Cir.\n2015)). We provided guidance in the form of a fourth\nexample in Repak, when we held that a redevelopment\nauthority’s awarding of contracts was “a concrete\ndetermination made by the [redevelopment authority’s]\nBoard of Directors.” 852 F.3d at 253.\n\n Step 2 requires the Government to prove that the\npublic official made a “decision” or took “an action” on\nthe identified “question, matter, cause, suit, proceeding or\ncontroversy.” McDonnell, 136 S. Ct. at 2368. The\nMcDonnell Court explained:\n Setting up a meeting, hosting an event, or\n calling an official (or agreeing to do so)\n merely to talk about a research study or to\n gather additional information . . . does not\n qualify as a decision or action on the pending\n question of whether to initiate the study.\n Simply expressing support for the research\n study at a meeting, event, or call—or sending\n a subordinate to such a meeting, event, or\n call—similarly does not qualify as a decision\n or action on the study, as long as the public\n official does not intend to exert pressure on\n another official or provide advice, knowing\n\n 74\n\f or intending such advice to form the basis for\n an “official act.”\nId. at 2371. The Court further clarified:\n\n If an official sets up a meeting, hosts an\n event, or makes a phone call on a question or\n matter that is or could be pending before\n another official, that could serve as evidence\n of an agreement to take an official act. A jury\n could conclude, for example, that the official\n was attempting to pressure or advise another\n official on a pending matter. And if the\n official agreed to exert that pressure or give\n that advice in exchange for a thing of value,\n that would be illegal.\nId.\n Here, Fattah was charged with engaging in three\ncategories of official acts, which we analyze in accordance\nwith the McDonnell framework. In Counts 16–18 and 22–\n23, Fattah is alleged to have set up a meeting between\nVederman and the U.S. Trade Representative, attempted\nto secure Vederman an ambassadorship, and hired\nVederman’s girlfriend, all in return for a course of conduct\nwherein Vederman provided things of value to Fattah.\n\n In this case, as in McDonnell, the jury instructions\nwere erroneous. We conclude that the first category of the\ncharged acts—setting up a meeting between Vederman\n 75\n\fand the U.S. Trade Representative—is not unlawful, and\nthat the second category—attempting to secure Vederman\nan ambassadorship—requires reconsideration by a\nproperly instructed jury. The third charged act—hiring\nVederman’s girlfriend—is clearly an official act. But\nbecause we cannot isolate the jury’s consideration of the\nhiring from the first two categories of charged acts, we\nmust reverse and remand the judgment of the District\nCourt.\n\n B. The Kirk Meeting\n We turn first to Fattah’s scheduling of a meeting\nbetween Vederman and the U.S. Trade Representative,\nRon Kirk. Under McDonnell, “setting up a meeting . . .\ndoes not, standing alone, qualify as an ‘official act.’ ” 136\nS. Ct. at 2368. Fattah’s setting up the meeting between\nVederman and Kirk was therefore not an official act, a\nconcession implicit in the Government’s opening brief.\nSee Gov’t Br. 32 (failing to mention the Kirk meeting as\none of the “two categories” of allegedly “official acts”).\nBut the jury was not properly instructed on this point.\nWithout the benefit of the principles laid down in\nMcDonnell, the jury was free to conclude that arranging\nthe Kirk meeting was an official act—and it may have\ndone so. The District Court’s erroneous jury instructions,\ntherefore, cannot survive harmless error review.\n\n In a footnote in its brief to this Court, the\nGovernment argues that evidence about the Kirk meeting\nwas offered only “because it established the strength of\n 76\n\fVederman’s desire to be an ambassador” and not because\nthe Government was attempting to establish the meeting\nas an independent official act. Id. at79–80 n.6. But the\nrecord undercuts the Government’s post hoc justification.\n\n The indictment, provided to the jury in redacted\nform for use in its deliberations, lists Fattah’s setting up\nthe Kirk meeting as an official act under the heading\n“FATTAH’s Official Acts for VEDERMAN.” JA494.\nUnder this heading are three distinct subheadings:\n(1) “The Pursuit of an Ambassadorship,” (2) “The Pursuit\nof Another Executive Branch Position,” and (3) “Hiring\nthe Lobbyist’s Girlfriend to the Congressional Staff.”\nJA494–95. The second subheading, “The Pursuit of\nAnother Executive Branch Position,” describes the\narrangement of the Kirk meeting. Quite clearly, then, this\nthree-part structure demonstrates that setting up the Kirk\nmeeting was one of three distinct categories of official acts\nalleged by the Government.\n\n Although there is some support for the\nGovernment’s argument that evidence of the Kirk meeting\nwas presented at trial only to establish the extent of\nVederman’s interest in becoming an ambassador, JA827,\n852–53 (mentioning the Kirk meeting in close proximity\nto references to Fattah’s attempts to secure Vederman an\nambassadorship), it is undermined by language in the\nredacted indictment itself, and by the way in which the\nGovernment presented its case at trial as a “pattern” of\nconnected acts.\n\n 77\n\f The redacted indictment, for example, refers to the\nKirk meeting as “The Pursuit of Another Executive\nBranch Position.” JA495 (emphasis added). The use of the\nword “Another” strongly suggests that evidence about the\nKirk meeting was not merely evidence of Fattah’s attempt\nto secure Vederman an ambassadorship, but was also\nevidence of a separate and distinct attempt to secure\nVederman a position on a federal trade-related\ncommission. The redacted indictment also notes that “[i]n\nor around May 2011, with little progress made on securing\nan ambassadorship for VEDERMAN, FATTAH turned\ntowards obtaining for VEDERMAN an appointment in the\nExecutive Branch to a federal trade commission.” Id.\n(emphasis added). The words “turned towards,” taken\nliterally, clearly convey that arranging the Kirk meeting\nwas presented as distinct from Fattah’s efforts to secure\nVederman an ambassadorship.\n\n The District Court denied Fattah and Vederman a\nnew trial on Counts 17 and 18, referring to evidence of the\nKirk meeting as “de minimis” and noting that “Kirk’s\ntestimony during this lengthy trial lasted a mere sixteen\nminutes.” JA97 n.14. In the District Court’s view,\nevidence of the Kirk meeting “played no role in the\noutcome” of the case. Id. Considering the record in light\nof McDonnell, we are not so sure.\n\n Although it is possible that evidence of the Kirk\nmeeting played a minor role at trial when compared to the\nother acts on which the Government presented evidence,\n\n 78\n\fthe redacted indictment suggests that the Kirk meeting was\na significant part of the Government’s case. The\nindictment dedicates five paragraphs to describing the\nKirk meeting, but just three paragraphs to describing the\nhiring of Vederman’s girlfriend—a hiring that, as we\nexplain below, is clearly an official act. JA495–96. While\nneither the number of minutes used at trial nor the number\nof paragraphs contained in an indictment is a dispositive\nunit of measurement for determining the significance of\nevidence, we conclude that the District Court’s erroneous\njury instructions pertaining to the Kirk meeting were not\nharmless.\n We conclude, in accordance with McDonnell, that\nFattah’s arranging a meeting between Vederman and the\nU.S. Trade Representative was not itself an official act.\nBecause the jury may have convicted Fattah for conduct\nthat is not unlawful, we cannot conclude that the error in\nthe jury instruction was harmless beyond a reasonable\ndoubt, and we must vacate and remand the convictions of\nFattah and Vederman as to Counts 16, 17, 18, 22 and 23.\n\n C. Fattah’s Efforts to Secure Vederman an\n Ambassadorship\n The nature of Fattah’s efforts to secure Vederman\nan ambassadorship is less clear, and presents a closer\nquestion than the Kirk meeting. We ultimately conclude\nthat the question warrants remand so that it may be\nanswered by a properly instructed jury. On remand, the\njury must decide whether Fattah’s conduct constituted a\n 79\n\f“decision” or “action” under Step 2 of the McDonnell\nanalysis.\n At the outset, it is clear to us that, under Steps 1(A)\nand 1(B), a formal appointment of Vederman as an\nambassador would qualify as a “matter” that “may at any\ntime be pending” before a public official. The formal\nappointment of a particular person (Vederman), to a\nspecific position (an ambassadorship), constitutes a matter\nthat is sufficiently focused and concrete. The formal\nappointment of an ambassador is a matter that is “pending”\nbefore the President—the constitutional actor charged\nwith nominating ambassadors—as well Senators, who are\ncharged with confirming the President’s ambassadorial\nnominations. U.S. Const. art. II § 2 (“[H]e shall nominate,\nand by and with the Advice and Consent of the Senate,\nshall appoint Ambassadors . . . .”). It is beyond cavil that\nthe formal appointment of an ambassador satisfies both\nsub-components of McDonnell’s Step 1.\n Turning to Step 2, we consider whether Fattah’s\nefforts to secure Vederman an ambassadorship qualify as\nmaking a “decision” or taking “an action” on the identified\n“matter” of appointment. McDonnell, 136 S. Ct. at 2368.\nAlthough those efforts—three emails, two letters, and one\nphone call—do not themselves qualify as a “question,\nmatter, cause, suit, proceeding, or controversy” under\nMcDonnell’s Step 1, they may nonetheless qualify as the\nmaking of a “decision” or taking “an action” on the\nidentified matter of appointment. Id.\n\n 80\n\f McDonnell’s Step 2 requires us to determine\nwhether Fattah’s efforts qualify as permissible attempts to\n“express[] support,” or impermissible attempts “to\npressure or advise another official on a pending matter.”\nId. at 2371. At trial, the jury was not instructed that they\nhad to place Fattah’s efforts on one side or the other of this\ndivide. The jury might even have thought they were\npermitted to find Fattah’s efforts—three emails, two\nletters, and one phone call—to themselves be official acts,\nrather than a “decision” or “action” on the properly\nidentified matter of appointment. Such a determination\nwould have been contrary to the dictates of McDonnell.\n Faced with such uncertainty, we cannot assume the\njury verdict was proper. Although the jury might not have\nconcluded that Fattah’s efforts were themselves official\nacts, and although the jury might not have concluded that\nthose efforts crossed the line into impermissible attempts\n“to pressure or advise,” we are unable to conclude that the\njury necessarily did so. Nor can we, on the cold record\nbefore us, determine whether Fattah’s efforts to secure\nVederman an ambassadorship crossed the line.\nDetermining, for example, just how forceful a strongly\nworded letter of recommendation must be before it\nbecomes impermissible “pressure or advice” is a fact-\nintensive inquiry that falls within the domain of a properly\ninstructed jury. Should the Government elect to retry these\ncounts after remand, the finder of fact will need to decide\nwhether Fattah’s efforts constituted permissible attempts\nto “express[] support,” or impermissible attempts “to\n 81\n\fpressure or advise another official on a pending matter.”\nId.\n\n D. The Zionts Hiring\n The third group of acts charged in the Fattah–\nVederman scheme involves Fattah’s decision to hire\nVederman’s girlfriend, Alexandra Zionts, as a\ncongressional staffer. We conclude that the hiring was an\nofficial act. A brief analysis of McDonnell’s two steps\nsuffices to show why this is so.\n Here, under McDonnell’s Step 1(A), the relevant\n“matter” is the decision to hire Zionts. Step 1(B) of the\nanalysis is satisfied because the hiring decision was\n“pending” before Fattah himself. And that hiring was\n“focused and concrete,” “within the specific duties of an\nofficial’s position—the function conferred by the\nauthority of his office.” Id. at 2369. Finally, McDonnell’s\nStep 2 requires that the “Government . . . prove that the\npublic official made a decision or took an action ‘on’ [the\nidentified] question, matter, cause, suit, proceeding, or\ncontroversy, or agreed to do so.” Id. at 2368. Fattah’s\ndecision to hire Zionts clearly satisfies that requirement.\nWe therefore conclude that the hiring of Zionts was an\nofficial act under McDonnell.\n\n Vederman concedes that the Zionts hiring was an\nofficial act. Oral Argument Transcript at 5–6. Fattah, for\nhis part, maintains that “hiring someone for a routine, part-\ntime, short-term position falls well outside [the] definition\n 82\n\f[of ‘official act’] and is nothing like a lawsuit, agency\ndetermination, or committee hearing, even if each shares\nthe happenstance that federal funds will be used.” Fattah\nReply Br. 25.\n\n Fattah’s argument lacks traction. Official acts need\nnot be momentous decisions—or even notable ones.\nJudges, for example, make “routine” evidentiary rulings\nevery day, and yet it is beyond question that those rulings\nare official acts. In the realm of official acts, it is of no\nmoment that Zionts provided only “part-time, short term”\nlabor. When a public official hires an employee to work in\nhis government office, he has engaged in an official act.\n * * *\n If we could conclude that the Zionts hiring was the\nonly category of actions that the jury relied on when it\nfound that Fattah performed an official act under Counts\n16–18 and 22–23, remand would not be necessary. But, as\nwe have explained, we cannot rule out that the jury\nerroneously convicted Fattah and Vederman based on\nother actions that were not official acts under\nMcDonnell.13\n\n\n13\n More specifically, the incomplete, and therefore\nerroneous, instructions could have led the jury to commit\nat least one of three mistakes. First, the jury could have\nimproperly convicted Vederman and Fattah based on the\nKirk meeting alone, or misunderstood the Kirk meeting to\n 83\n\f The Government argues that because the Zionts\nhiring was an official act, the effect of the erroneous jury\ninstructions could be no more than harmless. The jury’s\nverdict, the Government contends, permits us to deduce\nthat the jury necessarily concluded the Zionts hiring was\nan official act, and that this conclusion alone supported\nFattah’s and Vederman’s convictions as to Counts 16–18\nand 22–23—regardless of whether the jury erroneously\nfound any unofficial acts to be official acts. We disagree.\n Fattah and Vederman objected to the definition of\n“official act” at trial. We thus apply the harmless error\nstandard of review. McDonnell, 136 S. Ct. at 2375. The\nGovernment argues that because the jury convicted Fattah\nand Vederman of illegally laundering the proceeds of a\n“scheme to commit bribery” under Count 23, the jury\nfound that the scheme must have encompassed only the\nZionts hiring. JA531.That would mean that the jury did not\nconclude that the “scheme to commit bribery” included\n\nbe a necessary component of an impermissible “pattern”\nof official acts. Second, the jury might have concluded that\nFattah’s efforts to secure Vederman an ambassadorship\nwere themselves official acts. Third, the jury might have\nconcluded that Fattah’s efforts to secure Vederman an\nambassadorship were merely attempts to “express[]\nsupport,” rather than to “exert pressure . . . or provide\nadvice,” but nonetheless erroneously concluded that those\nexpressions of support were official acts. McDonnell, 136\nS. Ct. at 2371.\n 84\n\fany acts that McDonnell now makes clear were unofficial.\nYet the redacted indictment, jury instructions, and the fact\nthat the Government presented its case under a “pattern”\ntheory at trial compel us to reject the Government’s\nargument.\n\n The very first sentence under Count 23 of the\nredacted indictment incorporates all three categories of\n“Overt Acts” contained within paragraphs “58 through 95\nof Count One.” 14 All three of these categories fall under a\ngeneral heading within the redacted indictment titled “The\nBribery and Fraud Scheme [redacted].” JA494. The jury\nhad before it instructions for Count 23 which referred to\n“the alleged bribery scheme involving an $18,000\npayment,” JA448 (emphasis added), and the redacted\nindictment which referred to “a scheme to commit\nbribery,” JA531 (emphasis added). The parallel language\ncould well lead a rational jury to conclude that the relevant\n“scheme” included all three categories of acts listed under\nthe general heading: “The Bribery and Fraud Scheme\n[redacted].” JA494 (emphasis added).\n\n\n\n14\n JA531. Paragraphs 58 through 95 of Count 1 refer to the\nthree categories of allegedly official acts discussed above:\n(1) “The Pursuit of an Ambassadorship,” (2) “The Pursuit\nof Another Executive Branch Position,” and (3) the\n“Hiring of the Lobbyist’s Girlfriend to the Congressional\nStaff.” JA494–95.\n 85\n\f Like the redacted indictment and jury instructions,\nthe Government’s trial arguments referred to patterns and\na course of conduct, and stressed that the jury need not\nconnect specific payments to particular official acts. In its\nclosing argument to the jury, the Government stated that\nthe alleged “scheme took place over a period of several\nyears. Over and over again you’re going to see the same\npattern.” JA5383 (emphasis added). Then, in its rebuttal\nargument, the Government went out of its way to\nexplicitly distinguish its “pattern” theory from an\nalternative theory that would have directly connected\nindividual payments to individual acts. As the prosecutor\nargued to the jury:\n Ms. Recker appears to argue that each thing\n of value must coincide with some specific\n official act, but that is not the law and that is\n not what Judge Bartle is going to instruct you.\n Instead what he will tell you is that the\n government is not required to prove that\n Vederman intended to influence Fattah to\n perform a set number of official acts in return\n for things of value so long as the evidence\n shows a course of conduct of giving things of\n value, things of value to Fattah in exchange\n for a pattern of official acts favorable to\n Vederman. In other words a stream of\n benefits. These for those, not this for that.\n\n\n\n 86\n\fJA5715–16 (emphases added). In closing to the jury, the\nGovernment made several other references to this\n“pattern” theory, 15 and the District Court referred to this\n“pattern” theory in its instructions to the jury. As Judge\nBartle instructed:\n\n [I]t is not necessary for the government to\n prove that a defendant intended to induce a\n public official to perform a number of official\n acts in return for things of value.\n So as long as the evidence shows a\n course of conduct of giving things of value to\n a public official in exchange for a pattern of\n official acts favorable to the giver.\n\nJA5833–34 (emphasis added). On appeal, the Government\nchanges course, asking us to assume that the jury ignored\nthese repeated references to a “pattern of official acts” and\n\n15\n See, e.g., JA5389 (“And the exchange of an official act\nfor a thing of value is called a bribe. There’s the pattern.\nFattah needs money, Vederman gets an official act.”); JA\n5393 (“That’s why you see the pattern over and over again.\nFattah needs money, Vederman gets an official act.”);\nJA5400 (“The same pattern we saw over and over again.\nFattah needs money, Vederman gets an official act.”);\nJA5409 (“[Y]ou know that these were bribes because of\nthe pattern you saw over and over and over again. Fattah\nneeds money, Vederman gets an official act, that makes\nthese things a bribe.”).\n 87\n\finstead considered the Zionts hiring and Vederman’s\n$18,000 payment to Fattah as an isolated quid pro quo.\nThis is an invitation to speculate, and we decline to do so.16\nThe jury began its deliberations accompanied by a copy of\nthe redacted indictment which alleged a pattern of official\nacts, consisting of any combination of three categories of\nacts: pursuing an ambassadorship, arranging the Kirk\nmeeting, and hiring Zionts. In light of the erroneous\ninstructions, and because only one category clearly\n\n16\n Providing some support to the Government’s ultimately\nunconvincing argument that the jury considered the Zionts\nhiring and $18,000 payment in isolation, we note that the\nredacted indictment does mention those two events side-\nby-side in paragraph 78 of the indictment’s Part V. JA497\n(“On January 13, 2012, VEDERMAN wired $18,000 to\nFATTAH, and six days later, on January 19, 2012,\nBOWSER emailed VEDERMAN’s girlfriend, A.Z.,\nwelcoming her as a new employee to FATTAH’s\nCongressional Staff.”). But although paragraph 78\nmentions the $18,000 wire transfer and the Zionts hiring\nin the same breath, paragraph 78 does not instruct the jury\nto connect these two events apart from the rest of the\nevidence presented at trial. In light of the other instructions\nand arguments indicating that the jury should not consider\nthe Zionts hiring in isolation, but instead should consider\nthe hiring as one part of a three-part scheme, paragraph 78\nis not sufficient to avoid a reversal and remand on the\nconvictions of Fattah and Vederman as to Counts 16–18\nand 22–23.\n 88\n\fqualifies as an “official act,” the jury’s deliberations were\nfraught with the potential for McDonnell error. We will\nvacate the convictions of Fattah and Vederman as to\nCounts 16, 17, 18, 22, and 23, and remand to the District\nCourt.\n\nE. Vederman’s Sufficiency Challenge to Counts 16–18\n and 22–23\n Vederman argues that there is insufficient evidence\nto support a conviction, even if a jury were properly\ninstructed under McDonnell. Specifically, Vederman\nargues that there is insufficient evidence to convict him\nand Fattah, after remand, on Counts 16–18 and 22–23\nbecause “[a]t least seven of the eight alleged ‘official acts’\nwere, as a matter of law, not official at all.” Vederman Br.\n35. As to the single act that Vederman implicitly concedes\nto be an official act—the Zionts hiring—Vederman argues\nthat “[t]he only thing that even arguably associates” the\nZionts hiring with Vederman was its timing in relation to\nVederman’s sham purchase of the Fattahs’ Porsche. Id.\nAccording to Vederman, “the undisputed chronology\nprecludes any inference that Vederman conferred this\nbenefit on his friend as an illegal bribe.” Id. (emphasis\nomitted). Vederman is wrong. Sufficient evidence was\nproduced at trial to have allowed a properly-instructed jury\nto convict Fattah and Vederman of Counts 16–18 and 22–\n23.\n To begin with, even if the Zionts hiring had been the\nsole official act to survive this Court’s interpretation of\n 89\n\fMcDonnell, there would still be sufficient evidence to\nconvict Fattah and Vederman. Zionts did not receive\nwritten notice of her official hiring until six days after the\nsham Porsche purchase. Moreover, the jury would not be\nrestricted to considering the chronology of the sham\npurchase alone. It would be free to consider Vederman’s\nentire course of conduct. Under the general heading\n“VEDERMAN’S Payments and Things of Value to\nFATTAH,” the redacted indictment not only refers to the\n$18,000 wire transaction from Vederman to Fattah as part\nof the sham Porsche purchase, but also to Vederman’s\n$3,000 payment for the college tuition of Simone Muller,\nFattah’s live-in au pair, as well as thousands of dollars in\npayments made by Vederman for Chip Fattah’s college\ntuition. JA496–97.\n And the Zionts hiring is not the only act to survive\nour application of McDonnell. As we explained, a jury\ncould find that Fattah’s efforts to secure Vederman an\nambassadorship—three emails, two letters, and a phone\ncall—were an impermissible attempt to “pressure or\nadvise” President Obama, Senator Casey, or both men.17\n\n17\n Although Fattah’s efforts to secure Vederman an\nambassadorship present a jury question that is not for us to\nanswer on appeal, we note that not one of these efforts\nalone could qualify as an official act itself. See McDonnell,\n136 S. Ct. at 2372 (“Setting up a meeting, talking to\nanother official, or organizing an event (or agreeing to do\nso)—without more—does not fit that definition of ‘official\n 90\n\fThis means that a properly instructed jury on remand,\npresented with evidence of Fattah’s efforts to secure an\nambassadorship for Vederman and evidence of the Zionts\nhiring, could find more than a single official act.\n\n F. Blue Guardians\n In addition to the charges arising from his dealings\nwith Vederman, Fattah was charged in Count 3 with\n\n\nact.’ ”). The relevant question for a jury to consider on\nremand, then, is whether these actions constituted “a\n‘decision or action’ on a different question or matter”—to\nwit, the formal appointment of an ambassador. Id. at 2369\n(emphasis omitted).\n Even though the emails, letters, and phone call are\nnot, individually, official acts, it will be for a jury to decide\nif Fattah’s efforts to secure an ambassadorship for\nVederman crossed the line from permissible “support” to\nimpermissible “pressure or advice.” While we express\ndoubt that some of Fattah’s efforts concerning the\nambassadorship are, when considered in isolation, enough\nto cross that line, a properly instructed jury considering all\nof the facts in context might nonetheless conclude that\nother efforts—such as a hand-delivered letter to the\nPresident of the United States—indeed crossed that line.\nFurther, a jury might find that in the aggregate, three\nemails, two letters, and a phone call crossed the line and\ntherefore constituted a “decision or action” on the\nidentified matter of appointment.\n 91\n\fparticipating in a scheme with Lindenfeld to funnel money\nto a fraudulent nonprofit organization. In connection with\nthis scheme, Fattah was convicted of conspiring to commit\nhonest services fraud.\n\n Fattah owed Lindenfeld nearly $100,000 for work\nperformed on Fattah’s 2007 mayoral campaign. In lieu of\nrepayment, Fattah suggested that Lindenfeld create an\nentity, later named Blue Guardians, to which Fattah would\ndirect $15,000,000 in public funds by using his position as\na member of the House Committee on Appropriations.\nNothing in McDonnell requires us to upset Fattah’s\nconviction on Count 3.\n Step 1(A) of our McDonnell analysis requires the\nGovernment to “identify a ‘question, matter, cause, suit,\nproceeding or controversy.’ ” 136 S. Ct. at 2368. Here, the\n“matter” is the appropriation of millions of dollars in\npublic funds. See Repak, 852 F.3d at 253–54 (holding the\nawarding of redevelopment funds to be an official act). In\nparticular, it was Fattah’s promise to perform this official\nact that was unlawful. As McDonnell makes clear:\n\n [A] public official is not required to actually\n make a decision or take an action on a\n “question, matter, cause, suit, proceeding or\n controversy”; it is enough that the official\n agree to do so. The agreement need not be\n explicit, and the public official need not\n specify the means that he will use to perform\n his end of the bargain.\n 92\n\f136 S. Ct. at 2370–71 (internal citations omitted). That\nFattah took steps to actually carry out his promise (e.g., by\ndrafting and sending a formal appropriations request on\nofficial congressional letterhead) is evidence of his illegal\npromise. See id. at 2371.\n\n Step 1(B) requires the Government to establish that\nthe “ ‘question, matter, cause, suit, proceeding or\ncontroversy’ . . . ‘may at any time be pending’ or ‘may by\nlaw be brought’ before a public official.” McDonnell, 136\nS. Ct. at 2368. Appropriating public funds was not only a\nmatter that was pending before Fattah as a member of the\nAppropriations Committee, it was also a matter that was\npending before the Chairman and Ranking Member of an\nAppropriations Subcommittee to whom Fattah ultimately\nsent a formal written request. See id. at 2369 (“[T]he\nmatter may be pending either before the public official\nwho is performing the official act, or before another public\nofficial.”). Appropriating millions of dollars in response to\nthe Blue Guardians request is “focused and concrete,” and\n“the kind of thing that can be put on an agenda, tracked for\nprogress, and then checked off as complete.” Id.\n\n Given Fattah’s membership on the Appropriations\nCommittee, this was “something within the specific duties\nof an official’s position—the function conferred by the\nauthority of his office.” Id. Even if we were to assume,\nagainst all reason, that an appropriation is not “something\nwithin the specific duties” of either Fattah or the Chairman\nor Ranking Member of an Appropriations Subcommittee,\n\n 93\n\fFattah’s formal request for an appropriation was\nsomething that Fattah had the authority to do. Like the\nExecutive Director in Repak, who lacked authority himself\nto award redevelopment funds but could request such\nfunds from the Board, Fattah used his position as a\nCongressman to formally request appropriations for the\nBlue Guardians. 852 F.3d at 254 (“Repak had the power\nto, and indeed did, make recommendations to the\n[redevelopment authority.\n Step 2 of McDonnell requires the Government to\n“prove that the public official made a decision or took an\naction ‘on’ that question, matter, cause, suit, proceeding,\nor controversy, or agreed to do so.” 136 S. Ct. at 2368\n(emphasis added). Here, Fattah agreed to request an\nappropriation for a bogus purpose. Unlike Fattah’s letters,\nemails, and phone call seeking an ambassadorship for\nVederman, there is no potential for the jury to have made\na mistake when it found Fattah’s Blue Guardians promise\nunlawful.\n Fattah argues that the Government presented “[n]o\nevidence . . . that would have allowed [the jury] to\nconclude that [he] made a decision or took an action, or\ncould have done so, on the question whether Blue\nGuardians would receive a $15 million federal grant.”\nFattah Br. 46. This argument misses the point. It was\nFattah’s agreement to engage in the official act of formally\nrequesting the appropriation that was illegal. See\nMcDonnell, 136 S. Ct. at 2371.\n\n 94\n\f Lindenfeld’s trial testimony provided sufficient\nevidence of Fattah’s illegal agreement. JA1694–96, 1954.\nFattah’s letter provided additional evidence from which\nthe jury could have concluded that Fattah illegally agreed\nto perform an official act. 18 In short, the agreement itself\nwas illegal, and the Government provided sufficient\nevidence for the jury to conclude that the illegal agreement\ntook place.\n\n The Government’s evidence in support of the Blue\nGuardians scheme meets the requirements of McDonnell,\nand the Count 3 verdict will stand.\n\n V. Sufficiency of the Evidence for the RICO\n Conspiracy Conviction\n The jury found Fattah, Vederman, Brand, and\nNicholas guilty of the RICO conspiracy charged in Count\n1 of the indictment, but acquitted Bowser. Vederman filed\na post-verdict motion, and the District Court overturned\nhis RICO conspiracy conviction.\n\n\n\n18\n Despite Fattah’s protestation to the contrary, there is\nevidence that Fattah took steps to carry out his official act.\nJA6432–33 (Letter from Congressman Fattah to House\nAppropriations Subcommittee members “request[ing]\nfunding and support for the following projects and\nprograms of critical importance,” including $3,000,000\nfor “Blue Guardians”).\n 95\n\f On appeal, Fattah, Brand, and Nicholas challenge\nthe sufficiency of the evidence supporting their RICO\nconspiracy convictions. We “review[] the sufficiency of\nthe evidence in the light most favorable to the government\nand must credit all available inferences in favor of the\ngovernment.” United States v. Riddick, 156 F.3d 505, 509\n(3d Cir. 1998). If a rational juror could have found the\nelements of the crime beyond a reasonable doubt, we must\nsustain the verdict. United States v. Cartwright, 359 F.3d\n281, 286 (3d Cir. 2004), abrogated on other grounds by\nUnited States v. Caraballo-Rodriguez, 726 F.3d 418 (3d\nCir. 2013) (en banc).\n The indictment charged a RICO conspiracy in\nviolation of 18 U.S.C. § 1962(d), which makes it\n“unlawful for any person to conspire to violate” § 1962(c).\nSection 1962(c) provides:\n It shall be unlawful for any person . . .\n associated with any enterprise engaged in, or\n the activities of which affect, interstate . . .\n commerce, to conduct or participate, directly\n or indirectly, in the conduct of such\n enterprise’s affairs through a pattern of\n racketeering activity . . . .\n\n18 U.S.C. § 1962(c).\n\n In Salinas v. United States, 522 U.S. 52 (1997), the\ndefendant was convicted of a § 1962(d) RICO conspiracy,\nbut a jury acquitted him of the substantive RICO offense\n 96\n\funder § 1962(c). Id. at 55. The Supreme Court rejected\nSalinas’s contention that his conviction had to be set aside\nbecause he had neither committed nor agreed to commit\nthe two predicate acts required for the § 1962(c) offense.\nId. at 66. The Court declared that liability for a RICO\nconspiracy under § 1962(d), “unlike the general\nconspiracy provision applicable to federal crimes,” does\nnot require proof of an overt act. Id. at 63. A conspiracy\nmay be found, the Court explained, “even if a conspirator\ndoes not agree to commit or facilitate each and every part\nof the substantive offense. The partners in the criminal\nplan must agree to pursue the same criminal objective and\nmay divide up the work, yet each is responsible for the acts\nof each other.” Id. at 63–64 (citations omitted). This means\nthat, if a plan “calls for some conspirators to perpetrate the\ncrime and others to provide support, the supporters are as\nguilty as the perpetrators.” Id. at 64. Thus, opting into and\nparticipating in a conspiracy may result in criminal\nliability for the acts of one’s co-conspirators. Smith v.\nBerg, 247 F.3d 532, 537 (3d Cir. 2001).\n Accordingly, liability for a RICO conspiracy may\nbe found where the conspirator intended to “further an\nendeavor which, if completed, would satisfy all of the\nelements of a substantive criminal offense, but it suffices\nthat he adopt the goal of furthering or facilitating the\ncriminal endeavor.” Salinas, 522 U.S. at 65. Because the\nsubstantive criminal offense here was conducting a\n§ 1962(c) enterprise, the government had to prove:\n\n 97\n\f (1) that two or more persons agreed to\n conduct or to participate, directly or\n indirectly, in the conduct of an enterprise’s\n affairs through a pattern of racketeering\n activity; (2) that the defendant was a party to\n or member of that agreement; and (3) that the\n defendant joined the agreement or conspiracy\n knowing of its objective to conduct or\n participate, directly or indirectly, in the\n conduct of an enterprise’s affairs through a\n pattern of racketeering activity.\n\nUnited States v. John-Baptiste, 747 F.3d 186, 207 (3d Cir.\n2014).\n In United States v. Turkette, 452 U.S. 576 (1981),\nthe Supreme Court instructed that an enterprise is a “group\nof persons associated together for a common purpose of\nengaging in a course of conduct.” Id. at 583. The\ngovernment can prove an enterprise “by evidence of an\nongoing organization, formal or informal, and by evidence\nthat the various associates function as a continuing unit.”\nId. In Boyle v. United States, 556 U.S. 938 (2009), the\nSupreme Court established that an “association-in-fact\nenterprise must have at least three structural features: a\npurpose, relationships among those associated with the\nenterprise, and longevity sufficient to permit these\nassociates to pursue the enterprise’s purpose.” Id. at 946.\nThe structure necessary for a § 1962(c) enterprise is not\ncomplex. Boyle explained that an enterprise\n\n 98\n\f need not have a hierarchical structure or a\n “chain of command”; decisions may be made\n on an ad hoc basis and by any number of\n methods—by majority vote, consensus, a\n show of strength, etc. Members of the group\n need not have fixed roles; different members\n may perform different roles at different\n times. The group need not have a name,\n regular meetings, dues, [or] established rules\n and regulations . . . .While the group must\n function as a continuing unit and remain in\n existence long enough to pursue a course of\n conduct, nothing in RICO exempts an\n enterprise whose associates engage in spurts\n of activity punctuated by periods of\n quiescence.\n\nId. at 948.\n\n Another element of a substantive § 1962(c) RICO\nenterprise is that the enterprise must conduct its affairs\nthrough a pattern of racketeering activity. Section 1961\ndefines racketeering activity to include various criminal\noffenses, including wire fraud, 18 U.S.C. § 1344, and\nobstruction of justice, 18 U.S.C. § 1511. See 18 U.S.C.\n§ 1961(1). A pattern of such activity “requires at least two\nacts of racketeering activity.” Id. § 1961(5). The\nracketeering predicates may establish a pattern if they\n“related and . . . amounted to, or threatened the likelihood\n\n\n 99\n\fof, continued criminal activity.” H.J. Inc. v. Nw. Bell Tel.\nCo., 492 U.S. 229, 237 (1989).\n Here, the District Court denied the post-trial\nsufficiency arguments raised by Fattah, Brand, and\nNicholas. It reasoned:\n For a RICO conspiracy to exist, the\n conspirators must agree to participate in an\n enterprise with a unity of purpose as well as\n relationships among those involved. The\n evidence demonstrates that an agreement\n among Fattah, Brand, Nicholas, Lindenfeld,\n and Naylor existed for the overall purpose of\n maintaining and enhancing Fattah as a\n political figure and of preventing his standing\n from being weakened by the failure to be able\n to pay or write down his campaign debts.\n These five persons agreed to work together as\n a continuing unit, albeit with different roles.\n The Government established that\n Fattah, Brand, and Nicholas conspired along\n with Naylor and Lindenfeld to conceal and\n repay the 2007 illegal $1,000,000 loan to the\n Fattah for Mayor campaign.\n\nJA128–29. The District Court further determined that\n [w]hile each member may not have been\n involved in every aspect of the enterprise, its\n activities were sufficiently structured and\n 100\n\f coordinated to achieve the purpose of\n maintaining and enhancing Fattah’s political\n standing and of preventing him from being\n weakened politically because of his\n campaign debts.\n A RICO conspiracy also requires an\n agreement to participate in an enterprise with\n longevity sufficient to pursue its purpose.\n This was established. In May 2007 the illegal\n loan was obtained and continued through its\n repayment in January 2008 and into at least\n 2014 when the last campaign report reducing\n a fake campaign debt to Naylor’s consulting\n firm was filed by Fattah.\nJA131.\n\n The defendants argue that the evidence is\ninsufficient to show either an enterprise for purposes of\n§ 1962(c) or an agreement as required for a § 1962(d)\nconspiracy. We disagree, and conclude that the District\nCourt’s analysis is on the mark.\n\n We begin by considering whether there was an\nagreement. The evidence showed that Fattah knew each\nmember involved in the scheme to conceal the unlawful\ncampaign loan. When Lindenfeld learned of the $1 million\nloan, he informed Fattah that it exceeded campaign\nfinance limits. In short, the transaction was unlawful, and\nthe two knew it. The transaction nonetheless went\nforward, disguised as a loan, with Lindenfeld executing\n 101\n\fthe promissory note as Strategies’ officer and obligating\nStrategies to repay Lord $1 million. The concealment\nefforts continued as Lindenfeld funneled a substantial\nportion of the loan proceeds to Naylor for get-out-the-vote\nefforts. After the losing campaign, Lindenfeld spoke with\nFattah and Naylor about accounting for the funds that had\nbeen spent. They decided not to include the amounts in the\nFFM campaign reports. Fattah instructed Naylor to\nprepare a fictitious invoice, and Naylor complied. The\nFFM campaign reports filed from 2008 to 2014 disclosed\nnothing about the unlawful $1 million loan. Instead, they\nfalsely showed that Naylor’s consulting firm made yearly\nin-kind contributions of $20,000 in debt forgiveness, when\nin reality there was no debt to forgive.\n As Lindenfeld fretted over repaying the $600,000\nbalance of the Lord loan, Naylor assured him that Fattah\nhad promised to take care of the repayment. And the\nevidence supports an inference that Fattah recruited both\nNicholas and Brand in doing so. As EAA’s director,\nNicholas could fund the repayment. Brand, through his\ncompany, Solutions, acted as the middleman: he received\nthe payment from EAA pursuant to a fictitious contract,\nand then forwarded the balance due to Strategies pursuant\nto yet another fictitious contract. Nicholas and Brand\ncontinued in the spring and summer of 2008 to hide the\nfictitious agreement and the $600,000 payment to\nLindenfeld to satisfy the Lord loan.\n\n\n\n 102\n\f In short, this evidence shows that Fattah,\nLindenfeld, Naylor, Brand, and Nicholas all agreed to\nparticipate in Fattah’s plan to conceal the unlawful\ncampaign loan to maintain his political stature. Nicholas\nand Brand claim that they had no knowledge of the false\ncampaign reporting aspect of the plan. But as Salinas\ninstructs, conspirators need not “agree to commit or\nfacilitate each and every part of the” conspiracy. 522 U.S.\nat 63. Rather, they “must agree to pursue the same criminal\nobjective and may divide up the work, yet each [be]\nresponsible for the acts of each other.” Id. at 63–64. Thus,\na conspirator may agree to “facilitate only some of the acts\nleading to the substantive offense” yet still be criminally\nliable. Id. at 65.\n The evidence showed that a substantial amount of\nmoney was needed to repay Lord, and that the source of\nthe repayment was EAA, a non-profit organization whose\nfunds could be spent only for purposes consistent with the\nterms of the grants it received. It also showed that Nicholas\nwas presented with a sham contract to legitimize the\nEAA–Solutions transaction. We conclude that the\nevidence is sufficient to support an inference that Nicholas\nknew at the start that the plan was unlawful. Yet she still\nagreed to provide the requisite funds and to play a role in\nconcealing the illegal campaign loan so that Fattah could\nmaintain his political stature.\n\n As to Brand, even if he did not know that false\ncampaign reports were being filed, the evidence is\n\n 103\n\fsufficient to show he played a key role in the enterprise.\nFrom the outset, Brand worked to disguise the repayment\nof the Lord loan as the consideration in a sham contract\nbetween EAA and Solutions. He then arranged for the\ntransfer of funds to Strategies in satisfaction of a\ncontractual term in another purported business agreement\nbetween Solutions and Strategies. The evidence reveals\nthat Brand was the point man in the effort to meet the\nJanuary 31, 2008 deadline to repay the Lord loan, and it\namply shows that Brand also agreed to participate in the\nplan to hide the illegal campaign loan and its repayment to\nbenefit Fattah politically.\n Fattah, Brand, and Nicholas attack their RICO\nconspiracy convictions on another front. They argue that\nthose verdicts should be set aside because the evidence\nfails to show that the various schemes alleged in the\nindictment as part of the RICO conspiracy are connected.\nThe RICO count, they assert, charges a hub-and-spoke\nconspiracy that is unconnected by a rim. In their view,\nFattah is the hub, and the spokes consist of a series of\nindependent schemes: the Vederman bribery scheme, the\npayment of the outstanding tuition debt of Fattah’s son\nChip, the Blue Guardians plan, and the repayment of the\nillegal Lord loan to maintain Fattah’s political stature.\nThey argue that, without a unifying rim, their actions\ncannot constitute an enterprise. Again, we disagree.\n\n In In re Insurance Brokerage Antitrust Litigation,\n618 F.3d 300 (3d Cir. 2010), we concluded, in analyzing\n\n 104\n\fone of plaintiffs’ RICO claims, that the alleged hub-and-\nspoke enterprise—comprised of broker hubs and insurer\nspokes—could not withstand a motion to dismiss because\nit did not have a unifying rim. Id. at 374. We explained\nthat the allegations did “not plausibly imply concerted\naction—as opposed to merely parallel conduct—by the\ninsurers, and therefore cannot provide a ‘rim’ enclosing\nthe ‘spokes’ of these alleged ‘hub-and-spoke’\nenterprises.” Id. Thus, the allegations did not “adequately\nplead an association-in-fact enterprise” because the hub-\nand-spoke conspiracy failed to “function as a unit.” Id.\n\n That is not the case here. The evidence showed that\nFattah, Brand, and Nicholas agreed to conceal the illegal\nLord loan. Each acted for the common purpose of\nfurthering Fattah’s political interests. In short, they\nengaged in concerted activity and functioned as a unit. The\njury convicted Fattah, Brand, and Nicholas of the RICO\nconspiracy based on the racketeering activity of wire fraud\nand obstruction of justice to conceal the unlawful\ntransaction. Because the evidence shows that Fattah,\nLindenfeld, Naylor, Brand, and Nicholas agreed to protect\nFattah’s political status by acting to maintain the secrecy\nof the unlawful Lord loan, the alleged lack of a unifying\n“rim” is not fatal to this RICO enterprise. What matters in\nanalyzing the structure of this enterprise is that it\nfunctioned as a unit. Boyle, 556 U.S. at 945; In re Ins.\nBrokerage Antitrust Litig., 618 F.3d at 374. That “basic\nrequirement” was met. Id.\n\n 105\n\f We turn next to the contention that the evidence\nfails to establish other components of an enterprise. We\nconclude that much of the evidence supporting the\nexistence of an agreement also shows that there was an\nassociation-in-fact enterprise.\n\n Boyle made clear that an association-in-fact\nenterprise must have “a purpose, relationships among\nthose associated with the enterprise, and longevity\nsufficient to permit these associates to pursue the\nenterprise’s purpose.” 556 U.S. at 946. The purpose, as we\nhave repeatedly observed, was to maintain and preserve\nFattah’s political stature by concealing the illegal loan and\nits repayment. Though informal, there were relationships\namong those associated with the enterprise. Fattah was at\nthe center of this association and he directed its activity.\nHe knew each of the association’s members, and the\nmembers knew each other (except, perhaps, for Nicholas,\nwho may not have known Lindenfeld).19\n\n\n19\n Nicholas’s lack of familiarity with Lindenfeld does not\nundermine her membership in this association-in-fact\nenterprise. We have previously explained that “[i]t is well-\nestablished that one conspirator need not know the\nidentities of all his co-conspirators, nor be aware of all the\ndetails of the conspiracy in order to be found to have\nagreed to participate in it.” United States v. Riccobene, 709\nF.2d 214, 225 (3d Cir. 1983), abrogated on other grounds\nby Griffin v. United States, 502 U.S. 46 (1991).\n 106\n\f The Government also adduced sufficient proof of\nthe longevity component required for an enterprise. The\nscheme began in mid-2007, when Lord made the\ncampaign loan, directing the proceeds of the loan to\nStrategies. From the outset, Fattah, Lindenfeld, and Naylor\nall knew they needed to conceal this illegal transaction.\nThey began by fabricating an explanation for the source of\nthe funds they spent on election day. SLA created a fake\ninvoice for the campaign, showing a fictitious debt that\nNaylor could later forgive by fictitious in-kind\ncontributions existing only on Fattah’s campaign finance\nreports.\n The effort to disguise the Lord loan was not limited\nto filing false campaign reports. Nicholas and Brand, who\njoined the conspiracy a few months later than the other\nmembers, understood that they too had to make the\nfraudulent $600,000 payment by EAA to Solutions appear\nlegitimate. Nicholas and Brand tried to disguise the sham\ncontract as an ordinary transaction (even though it called\nfor a six-figure upfront payment simply to support\nSolutions’ various projects), and they succeeded in\nkeeping it out of the DOJ auditors’ view until August\n2008. The ruse continued as Solutions funneled the\n$600,000 payment to Strategies under the guise of another\nsham contract (which also required an upfront six-figure\npayment). The scheme then continued as Fattah submitted\nfalse FFM campaign reports from 2008 through 2014.\n\n\n\n 107\n\f Finally, we consider whether the enterprise\nconducted its affairs through a pattern of racketeering\nactivity, as required for a § 1962(c) enterprise. Wire fraud\nand obstruction of justice may constitute “racketeering\nactivity” under § 1961(1). As the Supreme Court\ninstructed in H.J. Inc., the “multiple predicates within a\nsingle scheme” must be related and “amount[] to, or\nthreaten[] the likelihood of, continued criminal activity.”\n492 U.S. at 237. Here, the amount of the illegal loan to be\nconcealed was substantial. The enterprise needed to write\noff the fictitious debt to Naylor’s consulting firm, and it\nwas urgent that both the EAA–Solutions contract and the\nSolutions–Strategies contract be legitimized. We conclude\nthe evidence was sufficient to establish that this enterprise\nconducted its affairs through a pattern of racketeering\nactivity and that the predicate acts of wire fraud and\nobstruction of justice were related. The racketeering\nactivity furthered the goals of maintaining the secrecy of\nthis $1 million illicit campaign loan and of preserving\nFattah’s political stature.\n Nicholas contends that the evidence fails to\nestablish a pattern of racketeering activity because the\nactions to which she agreed did not “extend[] over a\nsubstantial period of time” as H.J. Inc. requires. 492 U.S.\nat 242. That case indeed instructs that the continuity\nrequirement of a pattern is a “temporal concept,” and that\n“[p]redicate acts extending over a few weeks or months”\ndo not satisfy the continuity concept. Id. But the Supreme\nCourt explained that continuity may also be established by\n 108\n\fshowing that there is a “threat of continued racketeering\nactivity.” Id. Here, the course of fraudulent conduct\nundertaken to secure and to conceal the $1 million Lord\nloan consisted of the creation of sham debts, fictitious\ncontracts, and false accounting entries over the course of\nabout a year. But because Fattah needed to appear able to\nretire his campaign debt, the enterprise needed to continue\nfiling false campaign reports for several years, allowing\nthe annual $20,000 in-kind debt forgiveness contributions\nto appear to satisfy Naylor’s fake $193,000 invoice. That\nevidence was sufficient to establish the requisite threat of\ncontinued criminal activity. See H.J. Inc., 492 U.S. at 242–\n43.\n We conclude that the Government met its burden in\nproving that Fattah, Brand, and Nicholas 20 engaged in a\nRICO conspiracy in violation of § 1962(d).\n\n\n20\n Nicholas also asserts, in passing, that that her conviction\nunder § 1962(d) should be set aside because that statutory\nprovision is unconstitutionally vague as applied to her.\nAccording to Nicholas, a person of ordinary intelligence\nwould not know that her actions constituted an agreement\nto participate in a RICO enterprise. See United States v.\nPungitore, 910 F.2d 1084, 1104–05 (3d Cir. 1990). To the\ncontrary, a person of ordinary intelligence, who had been\nemployed by a prominent politician and then became the\nCEO of a nonprofit organization which that politician had\nfounded (and, to some extent, continued to direct), would\n 109\n\f VI. Variance from the Indictment and Sufficiency of\n the Evidence for Count 2\n Brand and Nicholas challenge their convictions for\nconspiracy to commit wire fraud by arguing that the\nGovernment’s evidence at trial impermissibly varied from\nthe indictment. Nicholas also challenges the sufficiency of\nthe evidence to support her conviction for conspiracy to\ncommit wire fraud. We address these contentions\ntogether. 21\n\n Count 2 of the indictment alleged a single\nconspiracy. JA277–79. Brand and Nicholas assert that the\nGovernment’s evidence at trial did not support the\nexistence of a single conspiracy but instead showed two\nindependent conspiracies, only one of which involved the\ntwo of them. According to Brand and Nicholas, the only\nconspiracy with which they were involved ended more\nthan five years before the Government charged them. That\nwould mean that all their conduct falls outside the five-\nyear limitations period for wire fraud conspiracy under 18\nU.S.C. § 3282.\n\n\nrealize that agreeing to participate with others in hiding an\nunlawful campaign loan of $1 million could constitute an\nunlawful RICO conspiracy.\n21\n In her briefing, Nicholas discusses variance in far less\ndetail than Brand, so we refer primarily to Brand’s\narguments. See Nicholas Br. 54–56. Her variance\narguments fail for the same reasons that Brand’s fail.\n 110\n\f “A conviction must be vacated when (1) there is a\nvariance between the indictment and the proof presented\nat trial and (2) the variance prejudices a substantial right\nof the defendant.” Kemp, 500 F.3d at 287 (quoting United\nStates v. Kelly, 892 F.2d 255, 258 (3d Cir. 1989)). We see\nno variance, and will affirm the District Court.\n A variance exists “if the indictment charges a single\nconspiracy while the evidence presented at trial proves\nonly the existence of multiple conspiracies.” Id. “We must\ndetermine ‘whether there was sufficient evidence from\nwhich the jury could have concluded that the government\nproved the single conspiracy alleged in the indictment.’ ”\nId. (quoting Kelly, 892 F.2d at 258). Viewing the record in\nthe light most favorable to the Government, we consider\nthree factors: (1) “whether there was a common goal\namong the conspirators”; (2) “whether the agreement\ncontemplated bringing to pass a continuous result that will\nnot continue without the continuous cooperation of the\nconspirators”; and (3) “the extent to which the participants\noverlap in the various dealings.” Id. (quoting Kelly, 892\nF.2d at 259).\n\n Brand argues that the Government failed to\nestablish a common goal among the conspirators. To\ndetermine whether the conspirators shared a common\ngoal, “we look to the underlying purpose of the alleged\ncriminal activity” in a fairly broad sense. United States v.\nRigas, 605 F.3d 194, 214 (3d Cir. 2010) (en banc). In\nRigas, we described the common goal of the defendants as\n\n 111\n\f“enriching [themselves] through the plunder of [their\ncorporate employer],” id., and we have similarly\narticulated the common goal in fairly general terms\nelsewhere. See United States v. Greenidge, 495 F.3d 85,\n93 (3d Cir. 2007) (“There was certainly evidence of a\ncommon goal among these co-conspirators: to make\nmoney by depositing stolen and altered corporate checks\ninto business accounts.”); Kelly, 892 F.2d at 259 (“[T]he\ncommon goal of all the participants was simply to make\nmoney selling ‘speed.’ ”). Importantly, a common goal\nmay exist even when “conspirators individually or in\ngroups perform different tasks in pursuing the common\ngoal,” and a single conspiracy may “attract[] different\nmembers at different times” or “involve[] different sub-\ngroups committing acts in furtherance of the overall plan.”\nUnited States v. Boyd, 595 F.2d 120, 123 (3d Cir. 1978).\n\n Here, the indictment described the purpose of the\nunified conspiracy in Count 2 at length:\n\n It was a purpose of the conspiracy to obtain\n an illegal campaign loan and to fraudulently\n repay that loan with hundreds of thousands of\n dollars of misappropriated charitable funds\n from Sallie Mae and federal grant funds from\n NASA which were intended for educational\n purposes.\n\n . . . . It was further a purpose of the\n conspiracy to present FATTAH to the public\n as a perennially viable candidate for public\n 112\n\f office who honored his obligations to his\n creditors and was able to retire his publicly\n reported campaign debts.\n . . . . It was further a purpose of the\n conspiracy to promote FATTAH’s political\n and financial goals through deception by\n concealing and protecting the conspirators’\n activities from detection and prosecution by\n law enforcement officials and the federal\n judiciary, as well as from exposure by the\n news media, through means that included\n obstruction of justice and the falsification of\n documents, including Campaign Finance\n Reports, false invoices, contracts, and other\n documents and records.\n\nJA277–78, ¶¶ 3–5.\n Brand characterizes the evidence at trial as\nestablishing two distinct conspiracies. The first he labels\nthe “diversion of funds scheme,” covering the\nmisappropriation of funds by Nicholas, Brand,\nLindenfeld, and Fattah to repay the Lord loan. Brand Br.\n34. Brand calls the second conspiracy the “CFR scheme,”\nin which Fattah and Naylor filed the false campaign\nfinance reports showing Naylor gradually forgiving a non-\nexistent debt. Id.\n Brand argues that the only goal of the CFR scheme\nwas to cover up how the funds from the illegal campaign\n 113\n\floan were spent, a goal he distinguishes from that of the\ndiversion of funds scheme, which he characterizes as a\nplan to cover up the repayment of the loan with stolen\nfunds. He also argues that the evidence does not establish\nhe was involved in, or even aware of, the false campaign\nfinance reports filed by Fattah. In Brand’s view, that\nnecessarily means the evidence showed two separate\nconspiracies.\n\n In considering these arguments, we begin by noting\nthat one conspiracy can involve multiple subsidiary\nschemes. Rigas, 605 F.3d at 214. It is true that the false\ncampaign finance reports, in the narrowest sense, had the\nspecific purpose of covering up how the illegal loan funds\nwere used during the election. But the false campaign\nfinance reports were also filed in furtherance of a broader\ngoal shared by the conspirators involved in repayment of\nthe Lord loan. They sought to promote Fattah’s political\nand financial goals by preserving his image as a viable\ncandidate and making him appear able to repay or\notherwise service his campaign debts without resorting to\nillegal means in doing so. The two subsidiary schemes\nworked in concert in furtherance of this overarching goal,\nand both were directed at covering up how the loan was\ntruly repaid. The “diversion of funds scheme” hid the\nillegal (but real) loan repayment through the use of fake\ncontracts; the “CFR scheme” showed the seemingly legal\n(but fake) loan forgiveness installments through the\ncreation of fake invoices and campaign finance reports.\nThe existence of two concealment schemes acting in\n 114\n\fconcert does not undermine the unity of the conspiracy of\nwhich they were both a part. We have no difficulty\nconcluding that the false campaign finance reports and the\nconcealed use of stolen funds to repay the Lord loan\noperated together in furtherance of a common goal.\n\n As for Brand’s argument that he was unaware of the\nfalse campaign finance reports and therefore could not be\na part of any conspiracy involving them, it is well-settled\nthat “each member of the charged conspiracy is liable for\nthe substantive crimes his coconspirators commit in\nfurtherance of the conspiracy even if he neither\nparticipates in his co-conspirators’ crimes nor has any\nknowledge of them.” United States v. Bailey, 840 F.3d 99,\n112 (3d Cir. 2016) (citing Pinkerton v. United States, 328\nU.S. 640 (1946)). The exceptions to that rule allow a\ndefendant to escape liability for a co-conspirator’s crime\nif: (1) “the substantive offense committed by one of the\nconspirators was not in fact done in furtherance of the\nconspiracy,” (2) “the substantive offense committed by\none of the conspirators ‘did not fall within the scope of the\nunlawful project,’ ” or (3) “the substantive offense\ncommitted by one of the conspirators ‘could not be\nreasonably foreseen as a necessary or natural consequence\nof the unlawful agreement.’ ” Id. (quoting Pinkerton, 328\nU.S. at 647–48). There was, as we have concluded, a unity\nof purpose between the co-conspirators to further Fattah’s\npolitical and financial goals by secretly obtaining and\nrepaying an illegal campaign loan with stolen funds. The\nfiling of false campaign reports does not fit within any of\n 115\n\fthe recognized exceptions to co-conspirator liability, as it\nwas in furtherance of the conspiracy’s shared goal, within\nthe scope of the agreement to conceal the loan, and\nforeseeable to Brand and Nicholas.\n\n Neither Brand nor Nicholas briefed the other two\nfactors we consider when determining whether the\nevidence impermissibly varied from the evidence,\n“whether the agreement contemplated bringing to pass a\ncontinuous result that will not continue without the\ncontinuous cooperation of the conspirators,” and “the\nextent to which the participants overlap in the various\ndealings.” Kemp, 500 F.3d at 287 (quoting Kelly, 892 F.2d\nat 258). The unified goal of promoting Fattah’s political\ncareer and maintaining secrecy surrounding the illegal\nloan and the misappropriated funds used to repay it\nrequired the continuous cooperation of the conspirators.\nIndeed, the efforts of several of them overlapped in every\naspect of the scheme. And Lindenfeld and Fattah were, at\na minimum, involved in some way in nearly every aspect\nof the origination of the loan, the false campaign finance\nreports, and the use of misappropriated funds to repay the\nloan. For his part, Naylor was involved in the use of the\nfunds, the false campaign finance reports, and to a lesser\nextent, the repayment of the loan.\n Brand (as part of his variance argument) and\nNicholas (as part of her sufficiency argument) argue that\nthe Government did not prove they agreed to conceal their\nactions, and thus the false campaign reports would not be\n\n 116\n\fsufficient to extend the duration of the conspiracy so that\nit fell within the statute of limitations. Acts of\nconcealment, such as the false campaign reports, are not\nautomatically “in furtherance” of a conspiracy. We must\ndetermine whether there was “an express original\nagreement among the conspirators to continue to act in\nconcert in order to cover up, for their own self-protection,\ntraces of the crime after its commission,” as opposed to “a\nconspiracy to conceal . . . being implied from elements\nwhich will be present in virtually every conspiracy case,\nthat is, secrecy plus overt acts of concealment.”\nGrunewald v. United States, 353 U.S. 391, 404 (1957). If\nthe indictment “specifically alleges a continuing\nconspiracy” to conceal the crime after the completion of\nthe wire fraud, and such a conspiracy can be proven, the\nstatute of limitations does not begin to run until the last\novert act of concealment. United States v. Moses, 148 F.3d\n277, 282 (3d Cir. 1998).\n\n Here, the evidence shows that the conspirators\nexpressly agreed to conceal the loan and its repayment. As\nan initial matter, Brand’s only role in the conspiracy was\nto cover up the use of stolen funds by (1) serving as an\nintermediary between Nicholas and Lindenfeld; and\n(2) agreeing to create false documentation (the contracts)\nwith both EAA and Strategies for the sole purpose of\ndisguising the payments and covering up the wire fraud\nconspiracy. Nicholas could simply have paid Lindenfeld\nherself (or paid Lord) if she and Brand had not agreed to\nconceal the crime from the start. Additionally, and as\n 117\n\fBrand acknowledges, the false campaign finance reports\nbegan before the loan was repaid, proving that\nconcealment of the crime was contemplated and begun as\na direct purpose of the conspiracy before Brand and\nNicholas became involved in the repayment. Nicholas too\nagreed to conceal the repayment, as she implicitly\nacknowledged in her emails with Brand and Fattah. GSA2.\nFinally, when Lindenfeld briefly strayed from the\nconspiracy’s commitment to secrecy by mentioning the\nrepayment in front of others who did not know of the\nscheme, Brand became “angry,” “took [Lindenfeld] out in\nthe hallway,” and chastised him, saying that “[Lindenfeld]\ncouldn’t say that sort of []thing” in front of other people.\nJA1670–71. We conclude that the evidence is consistent\nwith the allegations in the indictment, which charge a\nsingle conspiracy consisting of an original agreement to\nconceal the illegal loan and its subsequent illegal\nrepayment to further Fattah’s political career.\n\n Nicholas makes several arguments in passing. She\nsuggests that the District Court upheld the conviction after\ntrial “on a theory not submitted to the jury.” Nicholas Br.\n51. This argument is, essentially, that the indictment and\nthe District Court’s post-trial ruling described the\nconspiracy one way, but that the jury charge described the\nconspiracy differently. Nicholas argues that the jury was\npresented with the theory that the sole purpose of the false\ncampaign reports under Count 2 was to “conceal[] the\nalleged scheme to defraud,” JA5849, rather than to support\n\n 118\n\fFattah’s political career, as the District Court described the\npurpose after trial, see JA74.\n Nicholas ignores that part of the jury charge which\ninstructed that Count 2 required a finding “[t]hat two or\nmore persons agreed to commit wire fraud as charged in\nthe indictment.” JA5845 (emphasis added). The jury had\naccess to the indictment, and as Nicholas points out,\nNicholas Br. 45–46, the indictment outlines the offense in\nthe same way the District Court later described it in its\npost-trial ruling. The District Court consistently described\nthe count, and we see no reversible error.\n Nicholas also argues that the conspiracy charged in\nCount 2 has an objective—“to ‘present Fattah’ as\n‘perennially viable’ ”—and that such an objective is not\nillegal. Nicholas Br. 53. But, of course, the jury was not\ninstructed that it was illegal to be a Fattah supporter, or\neven to work on his campaign. The jury was charged\nspecifically on the crime of wire fraud.\n\n We conclude that there was no impermissible\nvariance between the indictment and the Government’s\nevidence at trial, and that there was sufficient evidence to\nsupport the convictions. We will affirm the convictions of\nBrand and Nicholas for conspiracy to commit wire fraud\nunder Count 2.\n\n\n\n\n 119\n\f VII. The District Court’s Instruction to the Jury on\n the Meaning of Intent\n Nicholas contends that the District Court\nimproperly instructed the jury by using the disjunctive\nrather than the conjunctive at one point in its definition of\nintent. When providing its final charge to the jury, the\nDistrict Court explained:\n Certain of the offenses charged in the\n indictment require that the government prove\n that the charged defendant acted intentionally\n or with intent. This means that the\n government must prove either that (1), it was\n the defendant’s conscious desire or purpose\n to act in a certain way or to cause a certain\n result; or (2), the defendant knew that he or\n she was acting in that way or it would be\n practically certain to cause that result.\n\nJA5787 (emphasis added). According to Nicholas, an\naccurate definition of intent required that the final “or” be\nan “and.” Nicholas argues that this was an error so\ngrievous as to “effectively eliminate[] the intent element\nfrom each offense of conviction.” 22 Nicholas Br. 26.\n\n\n22\n The Comment to Third Circuit Model Criminal Jury\nInstruction 5.03 makes clear that the definition of intent\nencapsulates both “specific intent” (acting “purposely” or\nwith “conscious object”) and “general intent” (acting\n 120\n\f Our review of whether a jury instruction stated the\nproper legal standard is plenary. United States v. Petersen,\n622 F.3d 196, 207 n.7 (3d Cir. 2010). At trial, Nicholas\nfailed to object to this portion of the jury charge.\nAccordingly, our review must be for plain error. See\nUnited States v. Flores-Mejia, 759 F.3d 253, 258 (3d Cir.\n2014) (en banc).\n\n To prevail on plain error review, Nicholas must\nestablish that there was an error, that it was plain (i.e., clear\nunder current law), and that it affected her substantial\nrights (i.e., whether there is a reasonable likelihood that\nthe jury applied the challenged instruction in an\nimpermissible manner). United States v. Olano, 507 U.S.\n\n“knowingly” or “with awareness”). Although Nicholas\ndescribes the alleged error as “essentially eliminating” the\nelement of intent, we think Nicholas’s argument is better\nunderstood as a claim that the instruction given could have\npermitted a jury to conclude that she acted with only\ngeneral intent (that she was aware of what she was doing),\nwhen her crimes require specific intent (that she had an\nillegal purpose). As her brief states, “[p]lainly she\n‘knowingly’ wrote checks from EAA to [Solutions] and\nmade record entries about them; the question was whether\nshe intended to defraud EAA and NASA, or to obstruct\njustice, by doing so.” Nicholas Br. 24. We cannot agree\nwith her characterization that the instruction resulted in the\n“effective omission” of the intent element from the jury\ninstructions.\n 121\n\f725, 733–34 (1993); United States v. Dobson, 419 F.3d\n231, 239–40 (3d Cir. 2005). If these requirements are met,\nwe may then exercise our discretion to address the error,\nbut only if we conclude that the error seriously affected the\nfairness, integrity, or public reputation of the judicial\nproceeding. United States v. Andrews, 681 F.3d 509, 517\n(3d Cir. 2012) (quoting Johnson v. United States, 520 U.S.\n461, 467 (1997)). A failure to instruct the jury on a\nnecessary element of an offense ordinarily constitutes\nplain error, unless the instructions as a whole otherwise\nmake clear to the jury all the necessary elements of the\noffense. United States v. Stimler, 864 F.3d 253, 270 (3d\nCir. 2017).\n Nicholas acknowledges, as she must, that the\ninstruction given was a verbatim recitation of Instruction\n5.03 of the Third Circuit’s Model Criminal Jury\nInstructions. She nonetheless contends that our Model\nInstruction is erroneous. Even if we were to accept\nNicholas’s contention that the instruction is incorrect, a\nproposition we consider as highly doubtful, see Petersen,\n622 F.3d at 208 (“We have a hard time concluding that the\nuse of our own model jury instruction can constitute error\n. . . .”), we conclude that, considering the instructions as a\nwhole, the District Court clearly and specifically\ninstructed the jury on the intent element as it applied to\neach of Nicholas’s charged crimes.\n\n The disputed intent instruction was given at the\nbeginning of the final charge, explaining the general\n\n 122\n\fmeaning of the intent applicable to “[c]ertain of the\noffenses charged.”23 JA5787. The District Court went on\nto instruct the jury in specific detail on the elements of\neach of the crimes of which Nicholas was accused,\n\n\n\n\n23\n The introductory definition did not end with the\nlanguage Nicholas cites. The District Court elaborated that\nacting in good faith is a complete defense to the charges:\n\n The offenses charged in the indictment\n require proof that the charged defendants\n acted with criminal intent. If you find that a\n defendant acted in good faith that would be a\n complete defense to such a charge, because\n good faith on the part of the defendant would\n be inconsistent with his or her acting\n knowingly, willfully, corruptly, or with intent\n to defraud or intent to impede, obstruct, or\n wrongfully influence.\n\nJA5788–89 (emphasis added). This instruction\nundermines Nicholas’s claim that the jury could have\nreasonably concluded that she “ ‘knowingly’ wrote\nchecks” but did not “intend[] to defraud . . . or to obstruct\njustice[] by doing so,” Nicholas Br. 24, as this instruction\nleaves little room for doubt that good faith is at odds with\n“criminal intent.”\n\n 123\n\fexplaining also the intent element of each. 24 See JA5791\n(describing the third element of the RICO conspiracy\ncharge as: “the particular defendant and at least one other\nalleged conspirator shared a unity of purpose and the intent\nto achieve the objective of conducting or participating in\nthe conduct of an enterprise’s affairs through a pattern of\nracketeering activity”); JA5823 (regarding wire fraud,\ninstructing that the government must prove “[t]hat the\ndefendant under consideration acted with the intent to\ndefraud”); JA5838–39 (regarding obstruction of justice,\ninstructing that the defendant must have acted “with the\nintent to impair the record, document, or object’s integrity\nor availability for use in an official proceeding,” and must\nhave acted corruptly “with the purpose of wrongfully\nimpeding the due administration of justice”); JA5860\n(explaining that falsification of records requires that “the\ndefendant under consideration acted with the intent to\nimpede, obstruct or influence the investigation or proper\nadministration of a matter”). These instructions are\nconsistent with both our Model Jury Instructions and our\ncase law concerning the elements of these crimes. See\nThird Circuit Model Criminal Jury Instruction 6.18.1962D\n(RICO), 6.18.1343 (wire fraud), 6.18.1512A2 (obstruction\nof justice); United States v. Sussman, 709 F.3d 155, 168\n(3d Cir. 2013) (obstruction of justice); United States v.\n\n24\n Nicholas did not object to the knowledge and intent\ninstructions when the District Court discussed each of the\nindividual charges, and does not identify a disagreement\nwith any specific instruction on any particular charge.\n 124\n\fMoyer, 674 F.3d 192, 208–09 (3d Cir. 2012) (falsification\nof records); United States v. Pelullo (Pelullo I), 964 F.2d\n193, 216 (3d Cir. 1992) (wire fraud).\n The District Court also provided a separate\ndefinition of the knowledge element of each charge,\nillustrating the difference between knowledge and intent.\nSee JA5793 (explaining that the evidence must show that\na RICO defendant “knowingly agreed to facilitate or\nfurther a course of conduct, which if completed would\ninclude a pattern of racketeering activity”); JA5823 (wire\nfraud means that the defendant “knowingly devised a\nscheme to defraud a victim . . . by materially false or\nfraudulent pretenses”); JA5860 (falsification of records\nhas as an element “[t]hat the defendant under\nconsideration knowingly concealed, covered up, falsified\nor made false entries in a document or record”). These\ninstructions made clear that knowledge and intent are\nseparate considerations, undermining Nicholas’s\ncontention that the jury was led to believe that “knowledge\nis sufficient to prove intent.” Nicholas Br. 24.\n The District Court provided each member of the\njury with more than 100 pages of instructions before\ndeliberations began. Viewing those instructions as a\nwhole, we are satisfied that the jury was apprised of the\ncorrect meaning of intent as an element of the crimes with\nwhich Nicholas was charged, as well as the distinction\nbetween knowledge and intent. We perceive no error,\n\n\n 125\n\fmuch less error that is plain, in the District Court’s\ninstructions to the jury. 25\n\n VIII. Sending the Indictment to the Jury\n At trial, Vederman, Nicholas, and Brand objected to\nthe District Court’s decision to give the jury a redacted\ncopy of the indictment to use during its deliberations. Only\nNicholas and Brand raise this issue on appeal. In\nNicholas’s view, sending the indictment to the jury\nunfairly prejudiced her because it contained unsupported\nallegations that she had obstructed federal agencies and\nreferred to a nonexistent certification requirement for\nSallie Mae funds. Brand argues that he was prejudiced by\nthe indictment’s references to “schemes” and “fake”\ncontracts, and because it mentioned Brand’s spouse and\nthat she was a former member of Fattah’s congressional\nstaff. Nicholas and Brand together assert that the\nindictment included legal theories on which the jury was\nnot instructed. They contend that the indictment’s\nnarrative of the Government’s case set out a roadmap that\nomitted any averments relating to the defense theory and\nallowed the Government to yet again present its case. To\nbuttress that argument, Nicholas and Brand cite the\ntestimony of Juror 12, who described the jury’s initial\n\n\n\n25\n Accordingly, we need not consider the merits of\nNicholas’s argument that Model Criminal Jury Instruction\n5.03 is erroneous.\n 126\n\fdeliberations and alleged that the jurors viewed the\nindictment as evidence.\n In United States v. Todaro, 448 F.2d 64, 66 (3d Cir.\n1971), we held that the decision to allow “jurors to have a\ncopy of the indictment with them during their\ndeliberations . . . is a matter within the discretion of the\nDistrict Judge, subject to a limiting instruction that the\nindictment does not constitute evidence, but is an\naccusation only.” Subsequently, in United States v.\nPungitore, 910 F.2d 1084, 1142 n.83 (3d Cir. 1990), we\nacknowledged that the District Court has the power to\nredact the indictment if doing so would be appropriate to\navoid prejudice to the defendant. See also United States v.\nRoy, 473 F.3d 1232, 1237 n.2 (D.C. Cir. 2007) (noting that\ncourt may redact an indictment before submitting it to the\njury).\n\n While both Nicholas and Brand objected in general\nterms to the District Court’s decision to provide the\nindictment to the jury, they have not directed us to any\nspecific request to redact the information they now claim\nis prejudicial. And the District Court provided a limiting\ninstruction on four occasions during its charge, repeatedly\nemphasizing that the indictment was not evidence.\nJA5765, 5767, 5782, 5880. The Court instructed the jury\non its duty to base its verdict “solely upon the evidence in\nthe case.” JA5764. Just before the jury retired to\ndeliberate, the Court reiterated that the purpose of the\n\n\n 127\n\findictment is to set forth the charges, and that it is “merely\nan accusation.” JA5909.\n “[J]uries are presumed to follow their instructions\n. . . .” Richardson v. Marsh, 481 U.S. 200, 211 (1987). In\nour view, Juror 12’s assertion that the indictment was\nbeing considered evidence does not, standing alone,\nestablish that his fellow jurors actually did so. We reject\nthe notion that the jury, after hearing weeks of testimony\nand having viewed substantial documentary evidence,\nwent on to ignore the Court’s limiting instruction\nconcerning the indictment. 26 Accordingly, we conclude\n\n\n26\n We acknowledge that our case law provides minimal\nguidance to district courts concerning the practice of\nsending an indictment to the jury for their use during\ndeliberations. We are also aware that some courts have\ndisapproved the practice of sending the indictment out\nwith the jury. See United States v. Esso, 684 F.3d 347, 352\nn.5 (2d Cir. 2012); Roy, 473 F.3d at 1237 n.2. We\nemphasize that this practice is committed to the sound\ndiscretion of the district judge. Todaro, 448 F.2d at 66. In\nour view, such an exercise of a judge’s discretion should\nbe informed by considering the nature of the case, the\nnumber of defendants, the length of the indictment, the\nextent of the factual recitation supporting the criminal\ncharges, and most importantly, whether the indictment\n(especially if lengthy and fact-laden) will be useful to the\njury, in light of the judge’s own carefully tailored jury\n 128\n\fthat the District Court did not abuse its discretion in\nsending the indictment out to the jury.\n\n IX. The District Court’s Evidentiary Rulings\n Vederman, Nicholas, and Brand each challenge\nevidentiary rulings by the District Court. We conclude that\nnone of these contentions warrants setting aside their\nconvictions.\n\n A. The District Court’s Application of Rule 404(b)\n Vederman argues that the District Court misapplied\nFederal Rule of Evidence 404(b) when it excluded\nevidence of Vederman’s prior gift-giving. 27 This Court\nreviews a district court’s application of Rule 404(b) for\nabuse of discretion. United States v. Daraio, 445 F.3d 253,\n\ninstruction, as supplemented by a verdict slip. See Esso,\n684 F.3d at 352 n.5.\n27\n Although Rule 404(b) determinations are usually in\nresponse to attempts to introduce “bad” acts evidence,\nVederman’s attempt to introduce “good” acts of gift-\ngiving is properly analyzed under the same rule. Ansell v.\nGreen Acres Contracting Co., 347 F.3d 515, 520 (3d Cir.\n2003) (“The evidence admitted in this case differs from\ngarden variety Rule 404(b) matter because it is evidence,\nnot of a prior bad act in a criminal case, but of a subsequent\ngood act in a civil case. Nonetheless, this evidence is\nencompassed by the plain text of Rule 404(b) which\naddresses ‘other . . . acts,’ not just prior bad acts.”).\n 129\n\f259 (3d Cir. 2006); Ansell v. Green Acres Contracting Co.,\n347 F.3d 515, 519 (3d Cir. 2003). A trial court commits\n“[a]n abuse of discretion . . . when [the] district court’s\ndecision rests upon a clearly erroneous finding of fact, an\nerrant conclusion of law or an improper application of law\nto fact.” Pardini v. Allegheny Intermediate Unit, 524 F.3d\n419, 422 (3d Cir. 2008) (quoting P.N. v. Clementon Bd. of\nEduc., 442 F.3d 848, 852 (3d Cir. 2006)).\n\n Federal Rule of Evidence 404(b) provides in part:\n (b) Crimes, Wrongs, or Other Acts.\n\n (1) Prohibited Uses. Evidence of a\n crime, wrong, or other act is not\n admissible to prove a person’s\n character in order to show that on a\n particular occasion the person\n acted in accordance with the\n character.\n\n (2) Permitted Uses; Notice in a\n Criminal Case. This evidence may\n be admissible for another purpose,\n such as proving motive,\n opportunity, intent, preparation,\n plan, knowledge, identity, absence\n of mistake, or lack of accident.\nFed. R. Evid. 404(b)(1)–(2).\n\n 130\n\f At trial, Vederman sought to present a witness from\nAmerican University who would have testified that\n“Vederman agreed, on more than fifty instances, to\nfinancially assist students [at American] who needed help\nwith tuition, book money, or travel funds to visit their\nfamilies.” Vederman Br. 42 (emphasis omitted).\nAccording to Vederman, the testimony was relevant to\nrefuting the Government’s argument that he agreed to\nguarantee the tuition expenses of Fattah’s au pair as a way\nof bribing the congressman. In excluding this evidence\nunder Rule 404(b), the District Court stated at sidebar:\n\n I sustain the government’s objection to\n calling a representative of American\n University to testify on behalf of Herbert\n Vederman.\n\n In my view the testimony runs afoul of\n Rule 404(b)(1) of the Federal Rules of\n Evidence. I find it to be propensity evidence.\n He or she would be testifying about Mr.\n Vederman’s financial generosity with respect\n to students of American University.\n The issue here is payment of partial\n tuition of a student at the Philadelphia\n University. I see no connection between the\n generosity at American University and the\n situation with Philadelphia University.\n\n\n 131\n\fJA4459–60. Vederman argues that because the proposed\nevidence related to Vederman’s intent, and not solely his\npropensity to perform good acts, we should conclude that\nthe District Court abused its discretion. We see no error in\nthe District Court’s ruling.\n\n Vederman challenges as arbitrary the District\nCourt’s “assertion that support for American University\nstudents is too remote from support for Philadelphia\nUniversity students” such that it constitutes inadmissible\nevidence. Vederman Reply Br. 23. This distinction was far\nfrom arbitrary. Vederman may well have financially\nsupported American University students because of\nconnections he had to that school or to the D.C.\ncommunity at large—connections Vederman did not have\nto Philadelphia University. And the excluded testimony\nappears to have described support for students Vederman\ndid not previously know. By supporting Fattah’s au pair,\nVederman was helping an employee of a man whom he\nknew quite well. JA889 (“[Fattah and Vederman] spent a\nlot of time together traveling back and forth to\nWashington, in the case of a death in the family attending\ncertain ceremonies that were important, and above all\nspending time with each other and their families\ntogether.”). Vederman’s decision to help Fattah’s au pair,\nwho wished to attend Philadelphia University, seems more\nlike a departure from, rather than a continuation of, his\npattern of support for American University students.\n\n\n\n 132\n\f As the party seeking admission of evidence under\nRule 404(b), Vederman bore “the burden of demonstrating\nits applicability” and “identifying a proper purpose.”\nUnited States v. Caldwell, 760 F.3d 267, 276 (3d Cir.\n2014). By failing to explain sufficiently why the factual\ndistinctions discussed above were not material, Vederman\nfailed to meet his burden. In particular, although\nVederman argues that he offered evidence of his prior gift-\ngiving to prove intent—“a proper non-propensity\npurpose”—he failed to show why the proposed testimony\nwas “relevant to that identified purpose.” Id. at 277. 28 As\nwe noted in Ansell v. Green Acres Contracting, an\nemployment discrimination case on which Vederman\nheavily relies, “[t]here is. . . no bright line rule for\ndetermining when evidence is too remote to be relevant.”\n347 F.3d at 525. As such, a district court’s determination\nunder Rule 404(b) “will not be disturbed on appeal unless\nit amounts to an abuse of discretion.” Id. The District\n\n\n\n28\n Under Rule 404(b), “prior act evidence is inadmissible\nunless the evidence is (1) offered for a proper non-\npropensity purpose that is at issue in the case; (2) relevant\nto that identified purpose; (3) sufficiently probative under\nRule 403 such that its probative value is not outweighed\nby any inherent danger of unfair prejudice; and\n(4) accompanied by a limiting instruction, if requested.”\nUnited States v. Caldwell, 760 F.3d 267, 277–78 (3d Cir.\n2014).\n 133\n\fCourt did not abuse its discretion in excluding evidence of\nVederman’s support for students at American University.\n\nB. Evidentiary Rulings Regarding Nicholas’s Defense\n Nicholas argues that the District Court rendered\nthree erroneous evidentiary rulings that prejudiced her\ndefense. We do not find any of her arguments convincing.\n\n 1. The EAA Board Minutes\n In support of its theory that Nicholas defrauded\nEAA, the Government introduced minutes from EAA’s\nBoard. Minutes from 2005 revealed that the Board limited\nNicholas’s signing authority to $100,000. Minutes from\nDecember 2007, February 2008, and May 2008 failed to\nreference either the EAA–Solutions contract or the checks,\ndrawn from EAA’s account for $500,000 and $100,000,\nthat were purportedly paid pursuant to the contract.\nNicholas contends that the Board minutes were\nerroneously admitted because they constituted improper\nhearsay which failed to satisfy either the exception for\nbusiness records under Federal Rule of Evidence 803(6)\nor the absence of records exception under Federal Rule of\nEvidence 803(7). “We review the District Court’s\nevidentiary ruling[s] for abuse of discretion, but also\n‘exercise plenary review . . . to the extent [the rulings] are\nbased on a legal interpretation of the Federal Rules of\nEvidence.’ ” Repak, 852 F.3d at 240 (citations omitted)\n(second alteration in original).\n\n 134\n\f Applying those standards here,29 we conclude there\nwas sufficient basis to admit exhibit EAA-48 under\nFederal Rule of Evidence 803(6) as a business record.\nAlthough allowing the prosecution to inquire over\nNicholas’s earlier objection based on Federal Rule of\nEvidence 803(7) to the absence of any mention of the\n$500,000 check in the 2008 Board Minutes was error, it\nwas not reversible error. Other evidence in the record\noverwhelmingly showed that Nicholas made the $500,000\nand $100,000 payments to Solutions with the requisite\nfraudulent intent. That evidence included the 2005 policy\nlimiting Nicholas’s authority to approve expenditures to\n$100,000, the accountant’s testimony about the\ndisbursement policy requiring the completion of a check\nrequest form for the issuance of a check, and Jones’\ntestimony that he never saw a request for the $500,000\ncheck. That evidence, coupled with Nicholas’s tendering\nof the upfront half-million dollar payment before the terms\nof the purported agreement had been finalized or executed,\nher failure to mention the $600,000 in payments to\nSolutions during her interview with FBI Agent\n\n29\n We note that the argument section of Nicholas’s brief on\nthis issue specifically cited to the page in the record where\nexhibit EAA-48 was admitted without objection by any\ndefense counsel. See Appellant’s Br. at 57 (citing JA4381-\n82). Nonetheless, there was an earlier objection to the\nadmission of exhibit EAA-48 that was preserved and that\nwas referenced in a string citation elsewhere in Nicholas’s\nbrief.\n 135\n\fDieffenbach, and her alteration of EAA’s general ledger\nto conceal the $100,000 payment, makes it “highly\nprobable” that the jury would have reached the same\nresult. See United States v. Friedman, 658 F.3d 342, 352\n(3d Cir. 2011).\n\n Nicholas also asserts that the Board minutes were\nunfairly prejudicial. We disagree. Any possible prejudice\nwas minimized by the fact that the Board minutes make no\nreference to either the EAA–Solutions contract or to any\nfinancial matters whatsoever. Indeed, given these lacunae\nin the Government’s proof, a reasonable factfinder might\nwell have concluded that the Board’s intention to limit\nNicholas’s signing authority had not been implemented\nand that Nicholas had not concealed the contract from the\nBoard.\n\n 2. Jones’ Memory Regarding Other Contracts\n Nicholas next asserts that the District Court erred\nduring her cross-examination of Board Chairman Jones by\nsustaining the prosecution’s objection to her inquiry into\nwhether he remembered other contracts in excess of\n$100,000 being brought to the Board. See JA1386–87. The\nbasis of the prosecution’s objection seemed to be that\nNicholas’s line of inquiry was beyond the scope of the\ndirect testimony. JA1387 (“I showed checks concerning\nwhat’s going on, not other programs.”); see Fed. R. Evid.\n611(b). The District Court sustained the objection,\ndeclaring that “it has absolutely nothing to do with this\ncase.” JA1387. Nicholas contends that if Jones did not\n 136\n\frecall whether other large contracts had been presented to\nthe Board, his inability to recall the EAA–Solutions\ncontract would have been “unremarkable rather than\nevidence of fraud or concealment.” Nicholas Br. 61.\n\n We acknowledge that whether Jones remembered\nother large contracts requiring Board approval had some\nrelevance under Rule 401. Yet any error by the District\nCourt in prohibiting Nicholas’s counsel from pursuing this\nline of inquiry is harmless. Jones admitted that he did not\nknow if the Board ever implemented the policy requiring\nits approval of contracts exceeding $100,000. He also\nconceded that the EAA Board focused less on the financial\nside of EAA than on its programs. JA1383–85. Nicholas\ncould not have been prejudiced by the District Court’s\nruling.\n\n 3. Exclusion of NOAA Evidence\n Nicholas defended against the criminal charges\narising out of the non-existent October 2012 conference\nby asserting that she acted in “good faith in spending the\nNOAA funds on EAA expenses,” Nicholas Br. 64, that the\ndifference in the dates in the paperwork was not material,\nand that NOAA had received the benefits of the\nsponsorship because its logo was displayed on the signage\nused at the February conference. Nicholas succeeded in\npresenting testimony and introducing photographs that\nshowed NOAA’s logo on the February 2012 annual\nconference bags, padfolios, and name tags. The Court\nexcluded a photograph of a NOAA intern at the February\n 137\n\f2012 conference, other photographs of the February\nconference signage, and some checks that pertained to the\nFebruary conference. Nicholas claims that her inability to\nintroduce those exhibits frustrated her ability to present\nher good faith defense. We are not persuaded.\n\n The photographs were excluded as cumulative, the\nsort of ruling to which we afford trial judges very broad\ndiscretion. See Fed. R. Evid. 403; United States v.\nDalfonso, 707 F.2d 757, 762 (3d Cir. 1983). It was not\nerror to exclude the student intern’s photograph. The\nconference brochure included photographs from previous\nconferences, and the witness from NOAA was unable to\ntestify to the year the student served as an intern. Finally,\nthe checks tendered for the travel expenses incurred for the\nFebruary conference were excluded as irrelevant to\nwhether Nicholas had a good faith belief that NOAA\nsponsored the October conference.\n\nC. The Cooperating Witness’s Mental Health Records\n During discovery, Brand learned that a cooperating\nwitness was diagnosed with bipolar II disorder and was\ntaking medication to treat that condition. Brand\nsubpoenaed mental health records kept by the witness’s\ncurrent and former psychiatrists in hopes of using those\nrecords to attack the witness’s memory, truthfulness, and\ncredibility. The witness and the Government both filed\nmotions to quash the subpoena, arguing that the witness’s\nmental health records were protected by the\npsychotherapist–patient privilege recognized by the\n 138\n\fSupreme Court in Jaffee v. Redmond, 518 U.S. 1 (1996).\nThe Government also filed a motion in limine seeking to\nrestrict the scope of cross-examination to prevent Brand\nfrom questioning the witness about his mental health.\n\n Alongside his motion to quash, the witness\nvoluntarily produced for the Court his mental health\nrecords. The Court concluded that the psychotherapist–\npatient privilege would ordinarily apply to the mental\nhealth records, but that the privilege was not absolute,\nespecially when invoked in response to a criminal\ndefendant’s efforts to obtain through discovery evidence\nthat is favorable to his case. Following the procedure set\nforth in Pennsylvania v. Ritchie, 480 U.S. 39 (1987), the\nDistrict Court conducted an in camera review of the\nmental health records to determine if they contained\nmaterial evidence—that is, evidence that would “give[]\nrise to a reasonable probability that it [would] affect the\noutcome of the case.” JA149. The District Court found\n“nothing in the mental health records of the [witness] . . .\nmaterial for this criminal action,” noting that “[t]he\nrecords reveal nothing that calls into question [the\nwitness’s] memory, perception, competence, or veracity.”\nJA150. Accordingly, the Court entered an order granting\nthe motions to quash the subpoena.\n The District Court also granted the Government’s\nmotion in limine and restricted the scope of cross-\nexamination, ruling that “no reference may be made to [the\nwitness’s] bipolar disorder or the medications he takes to\n\n 139\n\fmanage it.” JA142, 156. The Court reasoned that bipolar\ndisorder varied in its effects from person to person, and\nconcluded that Brand had not shown that the effects of the\ndisorder had any bearing on the witness’s credibility. The\nDistrict Court ruled that cross-examination would not\nserve any valid impeachment purpose.\n Brand claims that the District Court’s order ran\nafoul of the Due Process Clause of the Fifth Amendment\nand the Confrontation Clause of the Sixth Amendment.\nWe review a district court’s rulings to quash a subpoena\nand to limit the scope of cross-examination for abuse of\ndiscretion. United States v. Tykarsky, 446 F.3d 458, 475\n(3d Cir. 2006); NLRB v. Frazier, 966 F.2d 812, 815 (3d\nCir. 1992). Here, the District Court did not abuse that\ndiscretion.\n\n1. The District Court’s Denial of Access to the Mental\n Health Records\n In claiming that the District Court’s decision to\nreview the mental health records in camera before ruling\non their admissibility violated his rights under both the\nFifth and Sixth Amendments, Brand specifically argues\nthat his right to confront the witness was impeded because\nhe was denied access to records he could have used to\nimpeach the witness. This very argument was considered\nand rejected by a plurality of the Supreme Court in Ritchie,\nwhich noted that “the effect [of the argument] would be to\ntransform the Confrontation Clause into a constitutionally\ncompelled rule of pretrial discovery. . . . [T]he right to\n 140\n\fconfrontation is a trial right, designed to prevent improper\nrestrictions on the types of questions that defense counsel\nmay ask during cross-examination.” 480 U.S. at 52. We\nfollow the Ritchie plurality, and conclude that the\nConfrontation Clause did not require the District Court to\ngrant Brand access to the witness’s mental health records.\n Brand next challenges the District Court’s decision\nto quash the subpoena as a violation of the Fifth\nAmendment’s Due Process Clause. He concedes that\nRitchie’s Due Process holding allowed the District Court\nto review the mental health records in camera without\ndisclosing them to him. See id. at 59–60 (“A defendant’s\nright to discover exculpatory evidence does not include the\nunsupervised authority to search through [the\nGovernment’s] files. . . . We find that [the defendant’s]\ninterest . . . in ensuring a fair trial can be protected fully by\nrequiring that the [privileged] files be submitted only to\nthe trial court for in camera review.”). Brand instead\nargues that the District Court abused its discretion by\nfocusing on “irrelevant facts and spurious symptoms. . . .\nsuch as ‘hallucinations,’ ” and by “refus[ing] to consider\nevidence of cognitive impairment and memory issues.”\nBrand Br. 30. The record reveals, however, that the\nDistrict Court reviewed the mental health records and\ndetermined that they “reveal[ed] nothing that calls into\nquestion [the witness’s] memory, perception, competence,\nor veracity.” JA150. This hardly amounts to a refusal to\nconsider evidence of cognitive impairment or memory\nissues.\n 141\n\f Brand also challenges the legal standard applied by\nthe District Court, arguing that the court “focused solely\non whether disclosure would ‘change the outcome’ of\nBrand’s trial,” Brand Br. 29 (quoting JA148), rather than\nconsidering “whether the ultimate verdict is one ‘worthy\nof confidence.’ ” Id. (quoting United States v. Robinson,\n583 F.3d 1265, 1270 (10th Cir. 2009)). Brand\nmisleadingly quotes from the District Court’s opinion. The\nDistrict Court considered, in accordance with Ritchie,\n“whether there is a reasonable probability that disclosure\nwould change the outcome” of Brand’s trial, JA148\n(emphasis added), not whether disclosure would\nnecessarily change the outcome. As articulated in Ritchie,\na “ ‘reasonable probability’ is a probability sufficient to\nundermine confidence in the outcome.” 480 U.S. at 57\n(quoting United States v. Bagley, 473 U.S. 667, 682 (1985)\n(Blackmun, J.)). The District Court applied the correct\nstandard.\n\n2. The District Court’s Grant of the Motion in Limine\n In granting the Government’s motion in limine, the\nDistrict Court ruled that Brand could not “reference . . .\n[the witness’s] bipolar disorder or the medications he takes\nto manage it.” JA156. Yet that ruling placed no restriction\non Brand’s ability to cross-examine the witness with\nrespect to “his memory, competence, or truthfulness.” Id.\nBrand argues, nevertheless, that his Sixth Amendment\nright “to be confronted with the witnesses against him”\nwas violated. U.S. Const. amend. VI.\n\n 142\n\f The Confrontation Clause protects a defendant’s\nright to cross-examine a witness with respect to any\ntestimonial statements made by that witness. United States\nv. Berrios, 676 F.3d 118, 125–26 (3d Cir. 2012) (citing\nCrawford v. Washington, 541 U.S. 36, 51 (2004), and\nDavis v. Washington, 547 U.S. 813, 823–24 (2006)). But\nthe scope of cross-examination is not unlimited, and “[a]\ndistrict court retains ‘wide latitude insofar as the\nConfrontation Clause is concerned to impose reasonable\nlimits on such cross-examination based on concerns about\n. . . harassment, prejudice, confusion of the issues, the\nwitness’ safety, or interrogation that is repetitive or only\nmarginally relevant.’ ” John-Baptiste, 747 F.3d at 211\n(quoting United States v. Mussare, 405 F.3d 161, 169 (3d\nCir. 2005)). We review limitations on cross-examination\nfor abuse of discretion, and reverse “only when the\nrestriction ‘is so severe as to constitute a denial of the\ndefendant’s right to confront witnesses against him and . . .\nis prejudicial to [his] substantial rights.’ ” Id. (alternation\nin original) (quoting United States v. Conley, 92 F.3d 157,\n169 (3d Cir. 1996)).\n In United States v. Chandler, 326 F.3d 210, 219 (3d\nCir. 2003), we analyzed whether a district court’s decision\nto limit cross-examination with respect to a witness’s\nmotivation for testifying violated the Confrontation\nClause. See also Mussare, 405 F.3d at 169; John-Baptiste,\n747 F.3d at 211–12. Consistent with Delaware v. Van\nArsdall, 475 U.S. 673 (1986), we first concluded that “the\nexposure of a witness’ motivation in testifying is a proper\n 143\n\fand important function of the constitutionally protected\nright of cross-examination.” Chandler, 326 F.3d at 219–\n20 (quoting Van Arsdall, 475 U.S. at 678–79). We also\nnoted that the Confrontation Clause does not prevent a trial\njudge from imposing reasonable limits on cross-\nexamination. Id. In reviewing a district judge’s imposition\nof such limitations, we apply a two-part analysis. As we\nhave since described, “we inquire into: ‘(1) whether the\nlimitation significantly limited the defendant’s right to\ninquire into a witness’s motivation for testifying; and\n(2) whether the constraints imposed fell within the\nreasonable limits that a district court has the authority to\nimpose.’ ” John-Baptiste, 747 F.3d at 211–12 (quoting\nMussare, 405 F.3d at 169).\n The same analytical framework is appropriate when\ndetermining whether a restriction on the cross-\nexamination of a witness with respect to his memory and\nperception violates the Confrontation Clause. See Davis v.\nAlaska, 415 U.S. 308, 316 (1974); Greene v. McElroy, 360\nU.S. 474, 496 (1959); United States v. Segal, 534 F.2d\n578, 582 (3d Cir. 1976). Memory and perception, like\nmotivation for testifying, are central issues affecting the\ncredibility of any witness, and unreasonable limitations on\nthe right to cross-examine on those subjects cannot be\ncountenanced. We therefore ask, paraphrasing Chandler:\n(1) whether the District Court’s decision to put the\nwitness’s diagnosis and medications off limits\nsignificantly impaired Brand’s right to inquire into the\nwitness’s memory and perception; and (2) whether the\n 144\n\fruling fell within the reasonable limits that the District\nCourt has the authority to impose.\n We conclude that the District Court did not err. As\nan initial matter, the District Court permitted Brand to\ncross-examine the witness about his memory and\nperception, and limited cross-examination only with\nrespect to the witness’s bipolar disorder and the\nmedications he was taking to treat that condition. Brand\nwas free to question the witness about his memory and\nperception, and indeed did so. The restriction on asking\nthe witness about his bipolar disorder was not a significant\nlimitation of Brand’s right to inquire into the witness’s\nmemory or perception. Moreover, as the District Court\npointed out, Brand failed to show how inquiry into the\nwitness’s bipolar disorder would be useful for\nimpeachment purposes. See JA154.\n\n Given that failure, the District Court’s limits on\ncross-examination were reasonable. The Court concluded,\nafter reviewing the evidence submitted by Brand and the\nwitness’s mental health records, that any mention of the\nwitness’s bipolar disorder would “only be designed to\nconfuse the jury or to stigmatize him unfairly because of a\n‘mental problem’ without any countervailing probative\nvalue.” JA155. The District Court did not abuse its\ndiscretion in limiting Brand’s cross-examination on a topic\nthat would be far more prejudicial than probative. See\nTykarsky, 446 F.3d at 476–77 (“[T]he District Court acted\n\n\n 145\n\fwell within its discretion to restrict irrelevant and\nconfusing testimony.”).\n All of this is not to suggest that a witness’s mental\nhealth is always off limits. The appropriate course in any\ngiven case must be determined from the facts and\ncircumstances surrounding that case and the witness’s\nparticular condition. See United States v. George, 532 F.3d\n933, 937 (D.C. Cir. 2008) (“The days are long past when\nany mental illness was presumed to undermine a witness’s\ncompetence to testify. . . . [M]ental illness [is] potentially\nrelevant in a broad[] range of circumstances . . . . [But]\nsome indication is needed that a particular witness’s\nmedical history throws some doubt on the witness’s\ncompetence or credibility.”). Here, Brand failed to show,\nthrough mental health records or otherwise, any\nparticularized reason to doubt the credibility of the witness\nfor medical reasons.\n\n Brand states that the witness provided “the only\nevidence offered” on the intent element of his conspiracy\nconviction and that he should therefore be entitled to\nunrestricted cross-examination. Brand Br. 12 n.3. Yet no\nmatter the importance of a witness to any party, a district\ncourt may always place reasonable limits on cross-\nexamination to avoid “harassment, prejudice, confusion of\nthe issues, the witness’ safety, or interrogation that is\nrepetitive or only marginally relevant.” John-Baptiste, 747\nF.3d at 211 (citation omitted).\n\n\n 146\n\f We conclude that the District Court did not abuse\nits discretion in restricting the scope of Brand’s cross-\nexamination of the cooperating witness.\n\n X. The Government’s Cross-Appeal\n The jury convicted Fattah, Vederman, and Bowser\nof bank fraud, 18 U.S.C. § 134430 (Count 19) and making\nfalse statements to a financial institution, 18 U.S.C.\n§ 1014 31 (Count 20). In response to post-trial motions, the\nDistrict Court granted a judgment of acquittal on both\ncounts under Fed. R. Crim. P. 29, concluding that the\n\n30\n “Whoever knowingly executes, or attempts to execute,\na scheme or artifice . . . to defraud a financial institution\n. . . shall be fined not more than $1,000,000 or imprisoned\nnot more than 30 years, or both.” The definition of\n“financial institution” for purposes of § 1344 is set forth at\n18 U.S.C. § 20, and includes “a credit union with accounts\ninsured by the National Credit Union Share Insurance\nFund” and “a mortgage lending business (as defined in\nsection 27 of this Title).” 18 U.S.C. §§ 20(2), (10).\n31\n “Whoever knowingly makes any false statement or\nreport, or willfully overvalues any land, property or\nsecurity, for the purpose of influencing in any way the\naction of . . . a Federal credit union . . . any institution the\naccounts of which are insured by . . . the National Credit\nUnion Administration Board . . . or a mortgage lending\nbusiness . . . shall be fined not more than $1,000,000 or\nimprisoned not more than 30 years, or both.”\n 147\n\fevidence was insufficient to establish that the Credit\nUnion Mortgage Association (CUMA), the entity to whom\nFattah, Vederman, and Bowser made the false statements,\nis a “financial institution,” or, more specifically, a\n“mortgage lending business” as defined in 18 U.S.C. § 27.\nThe Government claims that, viewing the evidence in the\nlight most favorable to it, the District Court erred and that\nCUMA is, indeed, a “mortgage lending business.” We\nagree. Because the evidence is sufficient to support the\njury’s verdict, we will remand so Fattah and Vederman\nmay be resentenced on these charges.32\n\n A. CUMA is a Mortgage Lending Business\n In reviewing the District Court’s post-verdict\njudgment of acquittal under Rule 29 of the Federal Rules\nof Civil Procedure, we consider whether the evidence,\nwhen viewed in a light most favorable to the government,\nsupports the jury’s verdict. United States v. Dixon, 658\nF.2d 181, 188 (3d Cir. 1981). Our standard of review is the\nsame as that applied by the District Court, and we must\nuphold the jury’s verdict unless no reasonable juror could\naccept the evidence as sufficient to support the defendant’s\nguilt beyond a reasonable doubt. United States v.\nColeman, 811 F.2d 804, 807 (3d Cir. 1987).\n\n32\n Because the Government did not file an appeal as to\nBowser, the cross-appeal is limited to Fattah and\nVederman. The judgment of acquittal as to Bowser is\ntherefore unaffected by our ruling today.\n 148\n\f Initially, the grand jury’s indictment alleged that\nCUMA is a financial institution because it is federally\ninsured. JA302–03. At trial, however, the jury was\ninstructed that CUMA could qualify as a financial\ninstitution either because it is federally insured or because\nit is a “mortgage lending business.” See JA111, 401–02. A\n“mortgage lending business” is “an organization which\nfinances or refinances any debt secured by an interest in\nreal estate, including private mortgage companies and any\nsubsidiaries of such organizations, and whose activities\naffect interstate or foreign commerce.” 18 U.S.C. § 27.\n\n At trial, CUMA’s president and CEO, Eddie Scott\nToler, testified that CUMA is not federally insured.\nJA4235. The Government therefore attempted to prove\nthat CUMA is a “mortgage lending business” by\npresenting evidence that CUMA funds mortgages and then\nsells them in a secondary market.\n\n Toler also testified that CUMA is a “credit union\nservice organization”—a for-profit company owned by 48\ncredit unions, which serves small credit unions that do not\nhave the infrastructure or in-house expertise to handle\nmortgage loans themselves. JA4235. According to Toler,\n“[CUMA] exclusively provide[s] First Trust Residential\nMortgage loaning [sic] services, all the way from the\norigination of the mortgage loan through processing,\nunderwriting, closing and access to the secondary market\nwhere—and we’re selling the mortgage loan on the\nsecondary market.” JA4236–37. In jurisdictions in which\n\n 149\n\fCUMA is licensed, 33 CUMA holds the mortgage for a\nlimited period, generally from two to thirty days, and then\nsells the mortgage either to a partner credit union or on the\nsecondary market. JA4240.\n\n The District Court concluded that CUMA is not a\n“mortgage lending business” because “[t]he record is\ndevoid of any evidence that CUMA finances or refinances\nany debt.” JA113. Concluding that CUMA “simply is a\nloan processor for various credit unions which do the\nfinancing or refinancing,” id., the District Court ruled that\nCUMA’s “activity does not constitute the financing or\nrefinancing of any debt. CUMA is not the mortgagee. It is\nmerely selling the debt instrument to a third party.” JA114.\n We cannot agree with the District Court’s view of\nthe evidence. Toler testified that in “Maryland, D.C., and\nVirginia . . . all of the loans are closed in the name of\nCUMA.” JA4238–39. As Toler described it, CUMA\nborrows on a line of credit to fund the loan, and when the\nloan is sold, CUMA pays off its line of credit. JA4239–40.\nSo contrary to the District Court’s assessment, the\nevidence, viewed in a light most favorable to the\nGovernment, shows that CUMA is indeed the\nmortgagee—at least during the time from closing until the\nloan is sold to a partner credit union or on the secondary\nmarket. The fact that CUMA funds the closing and then\n\n33\n CUMA is licensed in Maryland, Washington, D.C., and\nVirginia. JA4238.\n 150\n\fholds the mortgage, even for a brief time, is sufficient to\nsupport a conclusion that CUMA is “an organization\nwhich finances or refinances any debt secured by an\ninterest in real estate.” 18 U.S.C. § 27.\n\n Fattah and Vederman attempt to refute the argument\nthat CUMA engages in financing mortgages by focusing\non Toler’s testimony that CUMA “doesn’t actually have\nany money to fund these mortgage loans.” JA4239; see\nFattah Reply Br. 38, Vederman Reply Br. 36. But Toler\ntestified that CUMA employs a credit line to borrow the\nfunds necessary to close on mortgages. See JA4239. That\nCUMA incurs debt to finance mortgages hardly\nundermines a conclusion that CUMA finances mortgages.\nIndeed, it is the very nature of modern banking that\nfinancial institutions do not hold cash reserves equal to the\nfull amount of their liabilities. See, e.g., Timothy C.\nHarker, Bailment Ailment: An Analysis of the Legal Status\nof Ordinary Demand Deposits in the Shadow of the\nFinancial Crisis of 2008, 19 Fordham J. Corp. & Fin. L.\n543, 561 (2014) (“[F]ractional reserve banking . . . is the\nde facto standard for all modern banks.”).\n\n Vederman also argues that, even if CUMA acts as a\nmortgage lending business in some transactions, it was not\nacting as a mortgage lending business in this transaction.\nVederman points to Toler’s testimony that, in a state in\nwhich CUMA is not licensed, the mortgage is closed in the\nname of a credit union. In such cases, the credit union, and\nnot CUMA, owns the mortgage for the short period before\n\n 151\n\fthe loan is sold on the secondary market. JA4241. CUMA\nis not licensed in the Commonwealth of Pennsylvania. See\nid. Thus, according to Vederman, CUMA was acting in its\ncapacity as a mortgage servicing company for Fattah’s\nvacation home purchase and did not—and could not—\nfinance Fattah’s mortgage. That would mean that CUMA\ncould not have been a victim of a crime against a financial\ninstitution in this instance: “When an entity is not\nfunctioning as a mortgage lender, the ‘pertinent federal\ninterest’ behind the statutes is not implicated.” Vederman\nReply Br. 38 (citation omitted).\n\n The Government responds that neither of the\nstatutes of conviction requires that the fraud or false\nstatement occur in connection with the same transaction\nthat places the entity within the definition of “financial\ninstitution.” Gov’t Fourth Step Br. 4. We agree with the\nGovernment.\n\n Both § 1344 and § 1014 protect entities that fall\nwithin the definition of “financial institution” and are\notherwise quite broad in their application. See Loughrin v.\nUnited States, 134 S. Ct. 2384, 2389 (2014) (interpreting\n§ 1344 as not requiring specific intent to defraud a bank);\nUnited States v. Boren, 278 F.3d 911, 914 (9th Cir. 2002)\n(“[Section 1014’s] reach is not limited to false statements\nmade with regard to loans, but extends to any application,\ncommitment or other specified transaction.”). Neither\nstatute is expressly limited in the manner that Vederman\nsuggests. Williams v. United States, 458 U.S. 279, 284\n\n 152\n\f(1982) (“To obtain a conviction under § 1014, the\nGovernment must establish two propositions: it must\ndemonstrate (1) that the defendant made a ‘false statement\nor report,’ . . . and (2) that he did so ‘for the purpose of\ninfluencing in any way the action of [a described financial\ninstitution] upon any application, advance, . . .\ncommitment, or loan.’ ”); United States v. Leahy, 445 F.3d\n634, 646 (3d Cir. 2006) (“The purpose of the bank fraud\nstatute is to protect the ‘financial integrity of [banking]\ninstitutions.’ ”) (citing S. Rep. No. 98-225, at 377 (1983),\nas reprinted in 1984 U.S.C.C.A.N. 3517), abrogated on\nother grounds by Loughrin, 134 S. Ct. at 2389.\n In support of his position, Vederman relies on\nUnited States v. Devoll, 39 F.3d 575 (5th Cir. 1994), in\nwhich the Fifth Circuit concluded that § 1014 (false\nstatements to a financial institution) is not intended to\ncapture fraud unrelated to an entity’s lending activities,\nand therefore held that it “applies only to actions involving\nlending transactions.” Id. at 580. The Fifth Circuit stated:\n [W]e are not persuaded that the statute\n imposes liability whenever a defendant’s\n false statement was intended to interfere with\n any activity of a financial institution; such a\n broad interpretation of section 1014\n presumably would encompass fraud or false\n representations having nothing to do with\n financial transactions, such as fraud in an\n employment contract or, for example, in a\n\n 153\n\f contract to provide goods or services for\n custodial care, premises repair, or renovation.\nId.\n\n Yet a majority of circuits, including our own, have\ndeclined to follow Devoll’s suggestion that § 1014 is\nrestricted to lending transactions. As the Ninth Circuit has\nheld, “we join at least six of our sister circuits—the First,\nThird, Fourth, Sixth, Seventh, and Tenth—in holding that\n18 U.S.C. § 1014 is not limited to lending transactions,\nand reject the minority rule to the contrary.” Boren, 278\nF.3d at 915. And even if we were to adopt Devoll’s narrow\nconstruction of § 1014 to lending transactions, that would\nnot resolve the more specific question of whether the\ndefrauded entity must be defined as a “mortgage lending\nbusiness” by virtue of the specific transaction in which the\nfalse statements arose.\n Recently, the Eighth Circuit addressed precisely\nthis issue. In United States v. Springer, 866 F.3d 949 (8th\nCir. 2017), that Court considered the defendant’s appeal\nfrom the district court’s denial of a Rule 29 motion on\ngrounds that GMAC, the entity defrauded, was not a\n“financial institution.” The Court upheld the district\ncourt’s determination that the evidence was sufficient to\nestablish that GMAC is in the mortgage lending business\nbecause there was testimony that “it had made hundreds or\nthousands of loans secured by mortgages in 2010 and 2011\nin states all across the country,” which established that its\nactivities affect interstate commerce. Id. at 953. It was not\n 154\n\fdeterminative that GMAC did not own the specific loan at\nissue in the case: “we discern no requirement in the\ndefinition of ‘mortgage lending business’ that the business\nown the particular loan in question; it need only finance or\nrefinance any debt secured by an interest in real estate, or,\nin other words, be in the interstate mortgage lending\nbusiness in general.” Id.\n\n In our view, the Eighth Circuit’s analysis is correct.\nWe therefore adopt that Court’s reasoning in Springer and\nconclude that it is of no moment that CUMA did not\nfinance the mortgage at issue in Fattah’s case. CUMA is a\n“mortgage lending business,” and that alone suffices to\nsupport the convictions under §§ 1014 and 1344.\n\n B. Sufficiency of the Evidence\n Finally, Vederman argues that, even if CUMA is a\nfinancial institution, the judgment of acquittal should\nstand because the Government did not put forth any\nevidence that he made a false representation to CUMA.34\nSpecifically, Vederman argues that the title to the Porsche\nwas actually changed to his name, making it a “true sale”\nas a matter of law, without regard to whether Fattah’s wife\n\n34\n Although Vederman presented this argument in his Rule\n29 motion, the District Court did not need to reach it in the\ncontext of Counts 19 and 20 because the Court granted the\nmotion on the ground that CUMA is not a financial\ninstitution. The District Court rejected the argument as to\nCounts 16, 17, and 18. See JA100–02.\n 155\n\fcontinued to retain possession. See United States v.\nCastro, 704 F.3d 125, 139 (3d Cir. 2013) (holding in\nanother context that “the government must be able to show\nthat [the defendant] made a statement to government\nagents that was untrue, and the government cannot satisfy\nthat burden by showing that the defendant intended to\ndeceive, if in fact he told the literal truth”); see also 75 Pa.\nCons. Stat. § 102 (defining “owner” as “[a] person, other\nthan a lienholder, having the property right in or title to a\nvehicle”).\n\n The Government responds that, regardless of\nwhether it is legally possible for one person to hold a title\nwhile a different person possesses the vehicle, the jury was\npermitted to consider all the circumstances in deciding\nwhether the Porsche sale was a sham. We agree.\n\n First, as the District Court observed, it was unclear\nas to whether the title had been properly executed under\nPennsylvania law. For instance, Fattah’s wife never\nappeared before a notary. 35 JA101. In addition, title 75,\nsection 1111(a) of the Pennsylvania Consolidated Statutes\nrequires that, “[i]n the event of the sale or transfer of the\nownership of a vehicle within this Commonwealth, the\nowner shall . . . deliver the certificate to the transferee at\n\n35\n Vederman argues that it is of no significance that the\nparties did not appear before a notary as the statute\nrequires, but he offers cases only from states other than\nPennsylvania to support this proposition.\n 156\n\fthe time of the delivery of the vehicle.” And, the transferee\nmust, within twenty days of the assignment of the vehicle,\napply for a new title. See 75 Pa. Cons. Stat. § 1111(b).\nNeither of these requirements was fulfilled. Finally,\nVederman never registered the Porsche in his name with\nthe Department of Motor Vehicles. See id.; JA4254.\n Second, and more importantly, even if the title had\nbeen properly transferred to Vederman, the title provisions\nof the Pennsylvania Motor Vehicle Code “were [not]\ndesigned to establish conclusively the ownership of an\nautomobile.” Weigelt v. Factors Credit Corp., 101 A.2d\n404, 404 (Pa. Super. Ct. 1953). Indeed, “[t]he purpose of\na certificate of title is not to conclusively establish\nownership in a motor vehicle, but rather to establish the\nperson entitled to possession.” Speck Cadillac-Olds, Inc.\nv. Goodman, 95 A.2d 191, 193 (Pa. 1953). Thus, a title\nprovides evidence of ownership; it is not dispositive of the\nissue. Wasilko v. Home Mut. Cas. Co., 232 A.2d 60, 61\n(Pa. Super. Ct. 1967).\n Vederman’s argument that the title in his name\nconstitutes conclusive evidence of ownership rests upon\nan erroneous conclusion that the jury was prohibited from\nconsidering all the circumstances of the transfer. As the\nDistrict Court observed, though, Pennsylvania’s\nCommonwealth Court has held that “[w]hether a\ntransferor has transferred ownership of a motor vehicle to\na transferee is a factual determination to be made by the\ncourt below.” Dep’t. of Transp. v. Walker, 584 A.2d 1080,\n\n 157\n\f1082 (Pa. Commw. Ct. 1990). Thus, the signed certificate\nof title was appropriately treated as one piece of evidence\nfor the jury to consider in assessing the validity of the\nvehicle transfer. Considered in the light most favorable to\nthe Government, the totality of the evidence is sufficient\nto support the jury’s conclusion that the Porsche sale was\na sham.\n\n XI. Prejudicial Spillover\n Finally, Fattah, Vederman, Nicholas, and Brand\neach contend that their convictions on various counts\nresulted from prejudicial spillover. We are not persuaded.\n We exercise plenary review over a district court’s\ndenial of a claim of prejudicial spillover, United States v.\nLee, 612 F.3d 170, 178–79 (3d Cir. 2010), and we apply a\ntwo-step test when reviewing such a claim. United States\nv. Wright, 665 F.3d 560, 575 (3d Cir. 2002). First, a court\nmust consider “whether the jury heard evidence that would\nhave been inadmissible at a trial limited to the remaining\nvalid count[s].” Id. (quoting United States v. Cross, 308\nF.3d 308, 317 (3d Cir. 2002)). The second step requires\nthat we “ask whether that evidence (the ‘spillover\nevidence’) was prejudicial.” Id. We consider four factors:\n“whether (1) the charges are intertwined with each other;\n(2) the evidence for the remaining counts is sufficiently\ndistinct to support the verdict on these counts; (3) the\nelimination of the invalid count [will] significantly\nchange[] the strategy of the trial; and (4) the prosecution\nused language of the sort to arouse a jury.” Id. (quoting\n 158\n\fUnited States v. Murphy, 323 F.3d 102, 118 (3d Cir.\n2003)); see also United States v. Pelullo (Pellulo II), 14\nF.3d 881, 898–99 (3d. Cir. 1994). These four factors are\nconsidered in a light “somewhat favorable to the\ndefendant.” Wright, 665 F.3d at 575 (quoting Murphy, 323\nF.3d at 122); see also Gov’t Br. 198 (same).\n\n A. Fattah’s Claim of Prejudicial Spillover\n Fattah argues that he suffered prejudicial spillover\non the remaining counts of conviction in light of (1)\nevidence pertinent to the alleged Vederman bribery\nschemes that is now arguably inadmissible under\nMcDonnell; and (2) “the government’s flawed RICO\nconspiracy theory.” Fattah Br. 50, 64. Fattah’s argument\nis undercut substantially because of our determination that\nMcDonnell requires a new trial for Counts 16, 17, 22, and\n23 and our decision to affirm the RICO conspiracy\nconviction. The only possible spillover left to consider is\nthe evidence pertaining to Fattah’s arranging a meeting\nbetween Vederman and the U.S. Trade Representative,\nRon Kirk, which in light of McDonnell is now arguably\ninadmissible.36\n\n The evidence of the Kirk meeting admitted during\nthis five-week trial was limited. Although this evidence\n\n36\n Nothing in this opinion is intended to foreclose the\npossibility that evidence of the Kirk meeting may be\nadmissible on retrial for some purpose other than as proof\nof an official act.\n 159\n\fwas part of the Government’s proof as to both the RICO\nand the bribery related charges, there is more than\nsufficient—and distinct —evidence to support Fattah’s\nconviction on all the other counts. In our view, eliminating\nany evidence of the Kirk meeting would not have altered\nthe strategy of the trial, nor should it significantly change\nthe strategy for any new trial that may be held. Because\nFattah has not pointed us to any argument by the\nprosecution relating to this meeting that could have\ninflamed the jury, we conclude that Fattah’s prejudicial\nspillover claim fails. Like the District Court, we presume\nthat the jury followed the Court’s instructions to consider\nand weigh separately the evidence on each count as to each\ndefendant and not to be swayed by evidence pertaining to\nother defendants. 37\n\n B. Vederman’s Assertion of Prejudicial Spillover\n Because the District Court acquitted Vederman of\nthe RICO charge, Vederman argues that he was “severely\nprejudiced by the presentation to the jury of a legally\nflawed racketeering conspiracy charge,” and as a\nconsequence his bribery and money laundering\n\n37\n We likewise reject Brand’s prejudicial spillover\narguments. See Brand Br. 6 (“Brand adopts the significant\nissue advanced by his co-appellant pursuant to Fed. R.\nApp. P. 28(i) that improper jury instructions and the\nresulting spillover of related improperly admitted\nevidence and argument unfairly prejudiced Brand.”).\n 160\n\fconvictions should be overturned. Vederman Br. 46. In\nresponse to the Government’s appeal of the District\nCourt’s Rule 29 acquittal on Counts 19–20 involving\nCUMA, Vederman asserts that these two counts also were\naffected by spillover evidence because the Government’s\ntheory tied the bribery charges to the actions taken to\ndefraud CUMA. In that we are vacating Vederman’s\nconvictions of Counts 16–18 and 22–23 based on\nMcDonnell and remanding for further proceedings, we\nneed address only Vederman’s argument of prejudicial\nspillover as it relates to the charges involving CUMA in\nCounts 19–20, charges that we will reinstate.\n The District Court’s acquittal of Vederman on the\nRICO count establishes that step one of the Wright\nspillover test has been met. “[T]he jury heard evidence that\nwould have been inadmissible at a trial limited” to the\nbribery and CUMA-related counts. Wright, 665 F.3d at\n575 (quoting Cross, 308 F.3d at 317).\n\n Wright’s second step requires “ask[ing] whether\nthat evidence (the ‘spillover evidence’) was prejudicial.”\nId. Vederman submits that the RICO, bribery, and CUMA-\nrelated charges were intertwined “in that the acts relating\nto the alleged bribery scheme were also charged as\n‘predicates’ under RICO.” Vederman Br. 49. We disagree.\n\n To be sure, the RICO, bribery, and CUMA Counts\nare related to one another. But in this instance, mere\nrelatedness is not enough to demonstrate the foundation\nnecessary for spillover. This is so because the bribery\n 161\n\fcharges were a predicate to the RICO charge. In other\nwords, the jury had to determine if Vederman was guilty\nof bribery, and the jury then used that “predicate” to\nconsider whether he was also guilty of the RICO\nconspiracy. Thus, the necessarily tiered structure of the\nquestions presented to the jury refute Vederman’s\nargument that the counts were intertwined.\n\n That the bribery charges were predicates for the\nRICO conspiracy further demonstrates that the “evidence\nfor the different counts was sufficiently distinct to support\nthe verdict on other separate counts.” Pelullo II, 14 F.3d at\n898. Regardless of the evidence pertaining solely to the\nRICO conviction, the evidence supporting both the bribery\ncharges and the charges involving CUMA in Counts 19–\n20 would have remained the same.\n\n The next factor we address is “whether the\nelimination of the count on which the defendant was\ninvalidly convicted would have significantly changed the\n[defendant’s] strategy of the trial.” Id. As Vederman\nargues, “the RICO charge interfered with Vederman’s\ncentral defense to the bribery charge—that his gestures\ntoward Fattah ‘were motivated purely by friendship.’ ”\nVederman Reply Br. 28 (citing Gov’t Br. 200). In other\nwords, the “RICO count made it dangerous to unduly\nemphasize [Vederman’s] close friendship” with Fattah. Id.\nFrom Vederman’s perspective, “a bribery-only trial would\nhave reduced this danger and allowed a freer presentation\nof the defense.” Id.\n\n 162\n\f It is quite likely that Vederman’s claim of friendship\nwould have been less risky as a litigation strategy if he had\nnot been facing a RICO charge. But Vederman\nnevertheless chose to take that risk and fully presented his\nfriendship argument to the jury. Moreover, while\nVederman’s reliance on friendship might have helped him\ndefend against the bribery charges, that friendship would\nnot have altered the evidence pertaining to Counts 19–20\ninvolving CUMA. Whether done for friendship or some\nother reason, submitting fraudulent information to a\nfinancial institution is unlawful.\n\n Finally, we “examine the charges, the language that\nthe government used, and the evidence introduced during\nthe trial to see whether they are ‘of the sort to arouse a\njury.’ ” Pelullo II, 14 F.3d at 899 (quoting United States v.\nIvic, 700 F.2d 51, 65 (2d Cir. 1983)). Vederman points out\nthat Fattah was presented as “a backslapping, corrupt party\nboss,” with “predictable spillover to his friend and\nassociate, Vederman.” Vederman Br. 50 (quoting United\nStates v. Murphy, 323 F.3d 102, 118 (3d Cir. 2003)). But\nthis description was of Fattah, not Vederman. Vederman\ncites other examples of prejudicial, pejorative language in\nthe Government’s closing arguments. At one point, the\nGovernment referred to “conspirators engaged in what can\nonly be described as a white collar crime spree from\nPhiladelphia all the way to Washington, D.C.” and\npromised “to untangle the webs of lies and deception that\nthese conspirators spun.” Vederman Br. 51 (quoting\nJA5295, 5297). Whatever rhetorical flair these words\n 163\n\fcontained, they did not obscure the evidence which\nindependently supported the convictions for bank fraud at\nCount 19 and for making false statements to CUMA at\nCount 20. Accordingly, because we presume that the jury\nfollowed the District Court’s instruction to consider and to\nweigh separately the evidence on each count and as to each\ndefendant, and because the evidence supporting the\nCUMA-related charges in Counts 19–20 is sufficiently\ndistinct from the RICO conspiracy, we conclude that\nVederman’s spillover argument is unavailing.38\n\n XII. Conclusion\n We will vacate the convictions of Chaka Fattah, Sr.\nand Herbert Vederman as to Counts 16, 17, 18, 22, and 23.\n\n38\n Nicholas adopted “pertinent portions” of the prejudicial\nspillover arguments advanced by Vederman and Fattah.\nNicholas Br. 65. Her spillover claim has no more merit\nthan theirs. Nicholas’s involvement in the RICO\nconspiracy was distinct from the bribery charges, which\ndid not unfairly influence the other counts. As to\nNicholas’s assertion that the NOAA charges did not\nbelong in the indictment and should have been tried\nseparately, we fail to see how this relates to a claim of\nprejudicial spillover. To the extent it challenges the\nDistrict Court’s denial of Nicholas’s motion for a\nseverance, Nicholas has failed to provide legal support for\nsuch a contention. See Fed. R. App. P. 28(a)(8)(A); United\nStates v. Irizarry, 341 F.3d 273, 305 (3d Cir. 2003).\n 164\n\fFattah and Vederman may be retried on these counts\nbefore a properly instructed jury. We will also reverse the\nDistrict Court’s judgment of acquittal on Counts 19 and\n20. The convictions of Chaka Fattah, Sr. and Herbert\nVederman will be reinstated, and the case will be\nremanded for sentencing on those counts. In all other\nrespects, the judgments of the District Court will be\naffirmed.\n\n\n\n\n 165", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359254/", "author_raw": "SMITH, Chief Judge"}]}
SMITH
GREENAWAY
KRAUSE
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582001/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellant in 17-1346 v. Chaka FATTAH, Sr., Appellant in 16-4397 Karen Nicholas, Appellant in 16-4410 Robert Brand, Appellant in 16-4411 Herbert Vederman, Appellant in 16-4427\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n Nos. 16-4397, 16-4410, 16-4411,\n 16-4427, 17-1346\n _____________\n\n UNITED STATES OF AMERICA\n Appellant in 17-1346\n\n v.\n\n CHAKA FATTAH, SR.,\n Appellant in 16-4397\n\n KAREN NICHOLAS,\n Appellant in 16-4410\n\n ROBERT BRAND,\n Appellant in 16-4411\n\n HERBERT VEDERMAN,\n Appellant in 16-4427\n _____________\n\nOn Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n District Court Nos. 2-15-cr-00346-001,\n\f 2-15-cr-00346-002, 2-15-cr-00346-003,\n 2-15-cr-00346-004\n District Judge: The Honorable Harvey Bartle III\n\n Argued January 18, 2018\n\nBefore: SMITH, Chief Judge, GREENAWAY, JR., and\n KRAUSE, Circuit Judges\n\n (Filed: January 16, 2019)\n\nAndrea G. Foulkes\nEric L. Gibson\nPaul L. Gray\nRobert A. Zauzmer\nOffice of United States Attorney\n615 Chestnut Street\nSuite 1250\nPhiladelphia, PA 19106\n\nJonathan Ian Kravis [ARGUED]\nUnited States Department of Justice\nCriminal Division, Public Integrity Section\n1400 New York Avenue, N.W.\nWashington, DC 20005\n Counsel for the United States\n\nMark M. Lee\nBruce P. Merenstein [ARGUED]\nSamuel W. Silver\n 2\n\fSchnader Harrison Segal & Lewis\n1600 Market Street\nSuite 3600\nPhiladelphia, PA 19103\n Counsel for Appellant Fattah\n\nAnn C. Flannery [ARGUED]\nSuite 2700\n1835 Market Street\nPhiladelphia, PA 19103\n\nLisa A. Mathewson\nSuite 810\n123 South Broad Street\nPhiladelphia, PA 19109\n Counsel for Appellant Nicholas\n\nAlan Silber\nPashman Stein Walder Hayden\n21 Main Street\nSuite 200\nHackensack, NJ 07601\n Counsel for National Association of Criminal\n Defense Lawyers, Amicus Appellant Nicholas\n\nMira E. Baylson\nBarry Gross [ARGUED]\nMeredith C. Slawe\nDrinker Biddle & Reath\nOne Logan Square\n 3\n\fSuite 2000\nPhiladelphia, PA 19103\n Counsel for Appellant Brand\n\nHenry W. Asbill\nBuckley Sandler\n1250 24th Street, N.W.\nSuite 700\nWashington, DC 20037\n\nGlen D. Nager [ARGUED]\nJacob M. Roth\nJulia W. M. F. Sheketoff\nJones Day\n51 Louisiana Avenue, N.W.\nWashington, DC 20001\n Counsel for Appellant Vederman\n\n ________________\n\n OPINION\n ________________\n\n\nSMITH, Chief Judge.\n\n\n\n\n 4\n\f Table of Contents\nI. Introduction ................................................................... 8\nII. Background .................................................................. 9\n A. The Fattah for Mayor Scheme ................................. 9\n 1. The Lord Loan and Its Repayment ..................... 10\n 2. The College Tuition Component of the FFM\n Scheme ................................................................ 27\n 3. The NOAA Grant and the Phantom Conference 28\n B. The Blue Guardians Scheme.................................. 31\n C. The Fattah–Vederman Bribery Scheme................. 33\n D. The Indictment and Trial ....................................... 39\nIII. Juror Misconduct and Dismissal of Juror 12 ........... 58\n A. Investigation of Alleged Juror Misconduct ........... 58\n B. Dismissal of Juror 12 ............................................. 64\nIV. The District Court’s Instructions Under McDonnell 70\n A. The McDonnell Framework................................... 71\n B. The Kirk Meeting ................................................... 76\n C. Fattah’s Efforts to Secure Vederman an\n Ambassadorship.......................................................... 79\n D. The Zionts Hiring .................................................. 82\n E. Vederman’s Sufficiency Challenge to Counts 16–18\n and 22–23.................................................................... 89\n F. Blue Guardians ....................................................... 91\n\n 5\n\fV. Sufficiency of the Evidence for the RICO Conspiracy\nConviction ...................................................................... 95\nVI. Variance from the Indictment and Sufficiency of the\nEvidence for Count 2.................................................... 110\nVII. The District Court’s Instruction to the Jury on the\nMeaning of Intent ......................................................... 120\nVIII. Sending the Indictment to the Jury ...................... 126\nIX. The District Court’s Evidentiary Rulings .............. 129\n A. The District Court’s Application of Rule 404(b) 129\n B. Evidentiary Rulings Regarding Nicholas’s\n Defense ..................................................................... 134\n 1. The EAA Board Minutes .................................. 134\n 2. Jones’ Memory Regarding Other Contracts ..... 136\n 3. Exclusion of NOAA Evidence.......................... 137\n C. The Cooperating Witness’s Mental Health\n Records ..................................................................... 138\n 1. The District Court’s Denial of Access to the\n Mental Health Records ..................................... 140\n 2. The District Court’s Grant of the Motion in\n Limine ............................................................... 142\nX. The Government’s Cross-Appeal ............................ 147\n A. CUMA is a Mortgage Lending Business............. 148\n B. Sufficiency of the Evidence ................................. 155\nXI. Prejudicial Spillover ............................................... 158\n A. Fattah’s Claim of Prejudicial Spillover ............... 159\n 6\n\f B. Vederman’s Assertion of Prejudicial Spillover ... 160\nXII. Conclusion ............................................................ 164\n\n\n\n\n 7\n\f I. Introduction\n Chaka Fattah, Sr., a powerful and prominent fixture\nin Philadelphia politics, financially overextended himself\nin both his personal life and his professional career during\nan ultimately unsuccessful run for mayor. Fattah received\na substantial illicit loan to his mayoral campaign and used\nhis political influence and personal connections to engage\nfriends, employees, and others in an elaborate series of\nschemes aimed at preserving his political status by hiding\nthe source of the illicit loan and its repayment. In so doing,\nFattah and his allies engaged in shady and, at times, illegal\nbehavior, including the misuse of federal grant money and\nfederal appropriations, the siphoning of money from\nnonprofit organizations to pay campaign debts, and the\nmisappropriation of campaign funds to pay personal\nobligations.\n Based upon their actions, Fattah and four of his\nassociates—Herbert Vederman, Robert Brand, Bonnie\nBowser, and Karen Nicholas—were charged with\nnumerous criminal acts in a twenty-nine count indictment.\nAfter a jury trial, each was convicted on multiple counts.\nAll but Bowser appealed. As we explain below, the\nDistrict Court’s judgment will be affirmed in part and\nreversed in part.\n\n\n\n\n 8\n\f II. Background1\n During the 1980s and ’90s, Fattah served in both\nhouses of the Pennsylvania General Assembly, first as a\nmember of the House of Representatives and later as a\nSenator. In 1995, Fattah was elected to the United States\nHouse of Representatives for Pennsylvania’s Second\nCongressional District. In 2006, Fattah launched an\nunsuccessful run for Mayor of Philadelphia, setting in\nmotion the events that would lead to his criminal\nconviction and resignation from Congress ten years later.\n\n A. The Fattah for Mayor Scheme\n Fattah declared his candidacy for mayor in\nNovember of 2006. Thomas Lindenfeld, a political\nconsultant on Fattah’s exploratory committee, believed\nthat “[a]t the beginning of the campaign, [Fattah] was a\nconsiderable . . . candidate and somebody who had a very\nlikely chance of success.” JA1618. But Fattah’s campaign\nsoon began to experience difficulties, particularly with\nfundraising. Philadelphia had adopted its first-ever\ncampaign contribution limits, which limited contributions\nto $2,500 from individuals and $10,000 from political\naction committees and certain types of business\norganizations. Fattah’s fundraising difficulties led him to\n\n\n\n1\n The facts are drawn from the trial record unless otherwise\nnoted.\n 9\n\fseek a substantial loan, far in excess of the new\ncontribution limits.\n\n 1. The Lord Loan and Its Repayment\n While serving in Congress, Fattah became\nacquainted with Albert Lord, II. The two first met around\n1998, when Lord was a member of the Board of Directors\nof Sallie Mae.\n As the May 15, 2007 primary date for the\nPhiladelphia mayoral race approached, Fattah met Lord to\nask for assistance, telling Lord that the Fattah for Mayor\n(FFM) campaign was running low on funds. Fattah asked\nLord to meet with Thomas Lindenfeld, a political\nconsultant in Washington, D.C., and part-owner of LSG\nStrategies, Inc. (Strategies), a company that was working\nwith the FFM campaign and that specialized in direct voter\ncontact initiatives. Lindenfeld had been part of the\nexploratory group that initially considered Fattah’s\nviability as a candidate for mayor. Lindenfeld had known\nFattah since 1999, when Fattah endorsed Philadelphia\nMayor John Street. Through Fattah, Lindenfeld had also\ngotten to know several of Fattah’s associates, including\nHerbert Vederman, Robert Brand, and Bonnie Bowser.\nHerbert Vederman, a businessman and former state\nofficial, was the finance director for the FFM campaign.\nRobert Brand owned Solutions for Progress (Solutions), a\n“Philadelphia-based public policy technology company,\nwhose mission [was] to deliver technology that directly\nassists low and middle income families [in obtaining]\n 10\n\fpublic benefits.” JA6551. Bowser was Fattah’s Chief of\nStaff and campaign treasurer, and served in his district\noffice in Philadelphia.\n Lord’s assistant contacted Lindenfeld to arrange a\nmeeting, and Lindenfeld informed Fattah that he would be\nmeeting with Lord. Lindenfeld, along with his partner,\nMichael Matthews, met with Lord and discussed Fattah’s\nneed for funds to mount an intensive media campaign.\nAfter that meeting, Lindenfeld reported to Fattah that Lord\nwanted to help, but that they had not discussed a specific\ndollar amount. Approximately a week later, Fattah\ninstructed Lindenfeld to meet with Lord a second time.\nLord “wanted to know if he could give a substantial\namount of money, a million dollars” to Fattah’s campaign.\nJA1630. That prompted Lindenfeld to reply that the\namount “would be beyond the campaign finance limits.”\nId.\n\n Lord proposed a solution: he offered to instead give\na million dollars to Strategies in the form of a loan. To that\nend, Lindenfeld had a promissory note drafted which\nspecified that Lord was lending Strategies $1 million, and\nthat Strategies promised to repay the $1 million at 9.25%\ninterest, with repayment to commence January 31, 2008.\nLindenfeld later acknowledged that the promissory note\nwould make it appear as though Lord’s $1 million was not\na contribution directly to the Congressman, although he\nknew that it was actually a loan to the FFM campaign.\nIndeed, Lindenfeld confirmed with Fattah that neither\n\n 11\n\fLindenfeld nor Strategies would be responsible for\nrepayment. With that understanding, Lindenfeld executed\nboth the note and a security agreement purporting to\nencumber Strategies’ accounts receivable and all its assets.\n\n On May 1, shortly before the primary election, Lord\nwired $1 million to Lindenfeld. Lindenfeld held the money\nin Strategies’ operating account until Fattah told him how\nit was to be spent. Some of the money was eventually used\nfor print materials mailed directly to voters. And, at\nFattah’s direction, Lindenfeld wired a substantial sum to\nSydney Lei and Associates (SLA), a company owned by\nGregory Naylor which specialized in “get out the vote”\nefforts.\n Naylor had known Fattah for more than 30 years.2\nDuring the campaign, Naylor worked as the field director\nand was in charge of getting out the vote on election day.\n\n2\n Naylor first worked with Fattah when he was in the state\nlegislature. When Fattah was elected to Congress, Naylor\nworked in his Philadelphia office. Naylor met Nicholas\nwhen she joined Fattah’s staff at some point in the 1990s.\nAfter concluding her employment with Fattah’s office,\nNicholas worked with the Educational Advancement\nAlliance (EAA), an education nonprofit entity founded by\nFattah. This entity helped to recruit underrepresented\nstudents for scholarship and college opportunities. Around\n2009, Naylor left Fattah’s office to work exclusively with\nSLA. Naylor also knew Brand.\n 12\n\fOn the final day of the campaign, Naylor worked with\nVederman, who allowed Naylor to use his credit card to\nrent vans that would transport Fattah voters to the polls.\n As the primary date neared, Fattah and Naylor knew\nthe campaign was running out of money. The campaign\nwas unable to finance “media buys,” and Naylor needed\nmoney for field operations to cover Philadelphia’s more\nthan one thousand polling places. In early May,\nLindenfeld called Naylor to say that Lindenfeld “would be\nsending some money [Naylor’s] way.” JA3057. Within\ndays, SLA received a six-figure sum for Naylor to use in\nthe campaign and on election day. Naylor used the money\nto pay some outstanding bills, including salaries for FFM\nemployees, and allocated $200,000 to field operations for\nelection day.\n\n Fattah lost the mayoral primary on May 15, 2007.\nAfterward, Lindenfeld spoke with Fattah, Naylor and\nBowser about accounting for the FFM campaign money\nfrom Lord that had been spent. They decided that the\namounts should not appear in the FFM campaign finance\nreports, and Fattah instructed Naylor to have his firm,\nSLA, create an invoice. Naylor did so, creating an invoice\ndated June 1, 2007 from SLA to FFM, seeking payment of\n$193,580.19. Naylor later acknowledged that the FFM\ncampaign did not actually owe money to SLA, and that the\nfalse invoice was created to “hide the transaction that took\nplace earlier” and “make it look like [SLA] was owed\nmoney.” JA3075–76. Although FFM did not owe SLA\n\n 13\n\fanything for the election day expenses, the FFM campaign\nfinance reports from 2009 through 2013 listed a $20,000\nin-kind contribution from SLA for each year, thereby\nlowering FFM’s alleged outstanding debt to SLA.\n\n Of the total $1 million Lord loan, $400,000 had not\nbeen spent. Lindenfeld returned that sum to Lord on June\n3, 2007. He included a cover letter which stated: “As it\nturns out the business opportunities we had contemplated\ndo not seem to be as fruitful as previously expected.”\nJA1254. Lindenfeld later admitted that there were no such\n“business opportunities” and that the letter was simply an\neffort to conceal the loan.\n In late 2007, faced with financial pressures, Lord\nasked his son, Albert Lord, III, to collect the outstanding\n$600,000 balance on the loan to Strategies. Lord III\ncontacted Lindenfeld about repayment and expressed a\nwillingness to forgive the interest owed if the principal\nwas paid. Lindenfeld immediately called Fattah and\ninformed him that repayment could not be put off any\nlonger. Fattah told Lindenfeld more than once that “[h]e\nwould take care of it,” JA1652, but Fattah did not act.\nNeeding someone who might have Fattah’s ear,\nLindenfeld reached out to Naylor and Bowser. Naylor\ntalked to Fattah on several occasions and told him that\nLindenfeld was under considerable pressure to repay the\nloan. Fattah told Naylor more than once that he was\n“working on it.” JA3082–83.\n\n\n 14\n\f During his political career, Fattah had focused on\neducation, especially for the underprivileged. Indeed,\nFattah founded two nonprofit organizations: College\nOpportunity Resources for Education (CORE), and the\nEducational Advancement Alliance (EAA).\n\n EAA held the annual Fattah Conference on Higher\nEducation (the “annual conference”) to acquaint high\nschool students with higher education options. JA3079.\nSallie Mae regularly sponsored the conference. According\nto Raymond Jones, EAA’s chairman of the board from\n2004 through 2007, EAA offered a variety of programs to\nprovide “marginalized students with educational\nopportunities so they could continue and go to college.”\nJA1360. EAA was funded with federal grant money which\ncould only be spent for the purposes described in the\nparticular grant. Karen Nicholas served as EAA’s\nexecutive director, handling the organization’s day-to-day\nadministrative responsibilities. Nicholas had previously\nbeen a staffer for Fattah when he was a member of\nPennsylvania’s House of Representatives.\n CORE was an organization that awarded\nscholarships to graduating high school students in\nPhiladelphia who had gained admission to a state\nuniversity or the Community College of Philadelphia.\nCORE received funding from a variety of sources,\nincluding Sallie Mae. Because CORE also received\nfederal funds, and because EAA had experience working\nwith federal grants, EAA received and handled the federal\n\n 15\n\ffunds awarded to CORE. In short, EAA functioned as a\nfiduciary for CORE. When money became a problem for\nthe FFM campaign, Fattah’s involvement with EAA and\nCORE soon became less about helping underprivileged\nstudents, and more about providing an avenue for\ndisguising efforts to repay the illicit campaign funds from\nLord.\n\n On January 7, 2008, Robert Brand contacted Fattah\nby telephone. Shortly thereafter, Lindenfeld received an\nunexpected call from Brand proposing an arrangement for\nBrand’s company, Solutions, to work with Strategies.\nSolutions had developed a software tool called “The\nBenefit Bank,” which was designed to “assist low and\nmoderate income families to have enhanced access to\nbenefits and taxes.” JA1993. During the telephone call,\nBrand referred to The Benefit Bank and suggested a\ncontract under which Strategies would be paid $600,000\nupfront. JA1666. Shortly thereafter, on January 9, 2008,\nBrand followed up on his call to Lindenfeld with an email\nabout “develop[ing] a working relationship where you\ncould help us to grow The Benefit Bank and our process\nof civic engagement. While I know this is not your core\nbusiness I would like to try to convince you to take us on\nas a client.” JA6427. Lindenfeld responded that he was\ninterested. To Lindenfeld, “this was the way that\nCongressman Fattah was going to repay the debt to Al\nLord.” JA1654. When Lindenfeld called Fattah and told\nhim of the contact from Brand, Fattah simply replied that\nLindenfeld “should just proceed.” JA1666–67.\n 16\n\f A few days later, Brand emailed Nicholas at EAA a\nproposal from Solutions concerning The Benefit Bank,\nwhich sought EAA’s support in developing an education\nedition of The Benefit Bank and a $900,000 upfront\npayment.\n\n As the January 31 date for repayment of the balance\nof the $1 million Lord loan approached, a flurry of activity\ntook place. On January 24, both Raymond Jones, chair of\nthe EAA Board, and Nicholas signed a check from EAA\nmade out to Solutions in the amount of $500,000.\nAlthough no contract existed between EAA and Solutions,\nthe memo line of the check indicated that it was for a\ncontract, and Nicholas entered it into EAA’s ledger.3\n\n That same day, Ivy Butts, an employee of\nStrategies, emailed Lindenfeld the instructions Brand\nwould need to wire the $600,000 balance on the Lord loan.\n\n3\n Raymond Jones, who was EAA’s Chairman of the Board\nfrom 2004 through 2007, recalled at trial that the Board\nhad a limit on the amount that Nicholas could spend\nwithout board approval. JA1358, 1369. Nicholas was\nauthorized to sign contracts on behalf of EAA for no more\nthan $100,000. JA1369–71. Jones did not recall the\ncontract between EAA and Solutions, nor did the EAA\nboard minutes for December 2007, February 2008, or May\n2008 refer to the EAA–Solutions contract or to the\nsubstantial upfront payment of half a million dollars upon\nexecution of the agreement. JA6358–63; 6567.\n 17\n\fWithin minutes, Lindenfeld forwarded that email to Brand\nat Solutions. Brand then made two telephone calls to\nFattah. By late afternoon, Brand emailed Nicholas,\ninforming her that he had “met with all the people I need\nto meet with and have a pretty clear schedule of what\nworks best for us. I am also seeing what line of credit we\nhave to stretch out the payments until you get your line of\ncredit in place.” JA6558. Brand asked if they could talk\nand “finalize this effort.” JA6558. On January 25 and 26,\nthere were a number of calls between Fattah, Brand, and\nNicholas.\n\n On Sunday January 27, at 5:46 pm, Brand\ntelephoned Fattah. At 10:59 pm, Brand emailed Nicholas\na revised contract between EAA and Solutions for the\nengagement of services. Brand indicated he would send\nsomeone to pick up the check at about 1:00 pm the\nfollowing day. The revised contract called for the same\n$900,000 payment from EAA to Solutions, yet specified\nthat $500,000 was to be paid on signing, with $100,000\ndue three weeks later, and another $100,000 to be paid six\nweeks out. No due date for the $200,000 balance was\nspecified. The terms of the contract called for EAA to\nassist Solutions with further developing The Benefit Bank.\nIn addition, under the contract, EAA would receive certain\n\n\n\n\n 18\n\ffunds from the Commonwealth of Pennsylvania for a\nprogram relating to FAFSA applications. 4\n\n The same evening, Brand sent Lindenfeld a contract\nentitled “Cooperative Development Agreement to Provide\nServices to Solutions for Progress, Inc. for Growth of The\nBenefit Bank.” JA6569. The agreement proposed a\nworking partnership in which Strategies would work with\nSolutions to identify and secure a Benefit Bank affiliate in\nthe District of Columbia and two other states, and to\nfacilitate introductions to key officials in other states\nwhere The Benefit Bank might expand. The terms of the\nagreement provided that Solutions would pay $600,000 to\nStrategies by January 31, 2008, which would “enable\n[Strategies’] team to assess opportunities and develop\ndetailed work plans for each area.” JA6572. Brand copied\nSolutions’ Chief Financial Officer, Michael Golden.\nLindenfeld responded to Brand’s email within a minute,\nasking if Brand had received the wiring instructions.\nBrand immediately confirmed that he had.\n\n Concerned that Solutions did not have $600,000 to\npay Strategies, Golden talked to Brand, who informed him\nthat Solutions would be receiving a check for $500,000\nfrom EAA. Early the next morning, Nicholas responded to\nBrand’s email from the night before. She advised Brand\nthat he could pick up the check, “but as I stated I am not\n\n4\n FAFSA is an acronym for Free Application for Federal\nStudent Aid.\n 19\n\fin a position to sign a contract committing funds that I am\nnot sure that I will have.” Gov’t Supp. App. (GSA) 1. That\nsame day, a $540,000 transfer was made from the\nconference account, which EAA handled, into EAA’s\nchecking account. The conference account was maintained\nto handle expenses for Fattah’s annual higher education\nconference. Prior to this transfer, EAA had only\n$23,170.95 in its account. EAA then tendered a $500,000\ncheck to Solutions, which promptly deposited the check\nbefore the close of that day’s business. EAA never\nreplenished the $540,000 withdrawal from the conference\naccount.\n Brand received the executed contract between\nSolutions and Strategies on January 28. Even though the\ncontract called for Strategies to perform services in\nexchange for the $600,000 payment, Lindenfeld neither\nexpected to do any work for the $600,000, nor did he in\nfact do any work.\n\n In sum, by January 28, Solutions had received\n$500,000 from EAA, but it still had to come up with\n$100,000 to provide Strategies with the entire amount\nneeded to repay the Lord loan. Golden obtained the needed\nfunds the following day by drawing $150,000 on a line of\ncredit held by Brand’s wife. Brand and Fattah spoke four\nmore times on the telephone on January 29. Trial evidence\nlater showed that, during the month of January 2008,\nneither the FFM campaign bank account nor Fattah’s\n\n\n 20\n\fpersonal account had a sufficient balance to fund a\n$600,000 payment.\n On the morning of January 30, frustrated by the\ndelay, Lindenfeld sent Brand an email with a subject line\n“You are killing me.” JA6430. Lindenfeld stated that he\nhad “made a commitment based on yours to me. Please\ndon’t drag this out. I have a lot on the line.” Id. Brand\nresponded late in the afternoon, stating: “just met with\nMichael. He does the transfer at 8 AM tomorrow. It should\nbe in your account ($600K) early tomorrow morning.” Id.\nLindenfeld replied: “The earlier the better.” Id. The\nfollowing morning, Golden wired $600,000 from\nSolutions’ Pennsylvania bank account into Strategies’\nWashington D.C. bank account. JA2745, 2874. Strategies\nin turn, wired the same amount from its Washington D.C.\nbank account to Lord’s bank account in Virginia. JA2874,\n6549. Around noon, Brand telephoned Lindenfeld.\n\n In the days following the exhaustive efforts to meet\nthe January 31 loan repayment deadline, four more\ntelephone calls took place between Brand and Fattah.5\nNaylor learned at some point that the loan had been paid\noff. When Naylor asked Fattah about details of the\nrepayment, Fattah simply replied “[t]hat it went through\nEAA to Solutions and it was done.” JA3088.\n\n5\n By contrast, between October to December 2007, Brand\nand Fattah spoke by telephone only “once or twice [a]\nmonth.” JA2734.\n 21\n\f Meanwhile, at some point in January, EAA received\nnotice that the Department of Justice Office of the\nInspector General (DOJ) intended to audit its books.6 DOJ\nauditors told EAA to provide, at the “entrance\nconference,” documentation containing budgetary and\naccounting information. EAA failed to produce any\naccounting information.\n Although Lindenfeld was no longer making\ndemands of Brand, Brand was still owed the remaining\n$100,000 that Solutions had paid to satisfy the Lord loan.\nOn March 23, 2008, Brand sent Nicholas an email\noutlining his efforts to contact her over the previous two\nweeks about documentation on the CORE work, how to\nproceed with the paperwork for the Commonwealth of\nPennsylvania, and “how we can get our proposed contract\nsigned and the outstanding payments made.” JA2749.\nNicholas responded that evening, writing:\n\n I can appreciate your urgency however I do\n have EAA work that I continue to do,\n including the [usual] facilitation of programs,\n our financial audit, the start-up of two new\n programs[,] and of course the DOJ audit. I am\n still trying to obtain a line of credit without a\n completed 2007 audit and things are getting a\n\n\n\n6\n One of the terms and conditions of a federal grant is that\nthe recipient “be readily prepared for an audit.” JA2314.\n 22\n\f little uncomfortable now as I try to keep us\n afloat.\nJA6576. Nicholas told Brand that the DOJ auditors were\nmaking demands and would soon be on site. She noted that\n“[t]hey are still very uncomfortable with your contract\namongst other things and depending on their findings\nsome of the funding received may have to be returned.” Id.\nNicholas said that she had submitted the paperwork to the\nstate, and she told Brand that “in the future . . . as a result\nof the DOJ audit I will not be in a position to do another\ncontract such as this.” Id.\n Shortly after Nicholas’s reply to Brand, Nicholas\nforwarded the Brand–Nicholas email chain to Fattah. The\nbody of the email stated, in its entirety: “I really don’t\nappreciate the tone of Bob’s email. I can appreciate that he\nhas some things going on however I am doing my best to\nassist him. Some other things are a priority. He needs to\nback off.” GSA2. Later that night, Bowser sent Fattah an\nemail with a subject line that read “Karen N” and a\ntelephone number. JA2752.\n\n As the audit continued, the auditors found other\ndeficiencies. During April of 2008, DOJ issued a notice of\nirregularity to EAA, which resulted in the audit being\nreferred to DOJ’s Investigations Division for a more\ncomprehensive review.\n\n On April 24, 2008, Brand emailed Nicholas asking\nfor a time to update her on The Benefit Bank. In early May,\n 23\n\fBrand sent another email to Nicholas attaching a revised\nEAA–Solutions contract proposal, which decreased the\ninitial upfront cost from $900,000 to $700,000.\n Although Solutions and EAA had still not signed a\ncontract, EAA paid Solutions another $100,000 in May.\nThat money was obtained via a loan to EAA from CORE.\nThomas Butler, who had worked for Fattah both when\nFattah was in Congress and when he was in the General\nAssembly, was CORE’s executive director. Butler had\nbeen contacted in mid-May by Jackie Barnett, a member\nof CORE’s Board who had also worked with\nCongressman Fattah. Barnett informed Butler that\nNicholas had requested a loan from CORE to EAA, and\nthat Fattah, as Chairman of CORE’s Board, had approved\nit. Butler and Barnett withdrew funds from two CORE\nbank accounts and obtained a cashier’s check, dated May\n19, in the amount of $225,000 and made payable to EAA.\nThe withdrawals were from accounts used for Sallie Mae\nfunds and other scholarship money.\n After EAA received the $225,000 check, EAA\ntendered a $100,000 check to Solutions. The check bore\nthe notation “Commonwealth of Pennsylvania.” EAA\nrepaid CORE the following month. Because EAA lacked\nsufficient funds of its own to cover this payment, EAA\ndrew on grant money that it had received from NASA.\n\n Brand and Lindenfeld continued to communicate\nconcerning The Benefit Bank. In July of 2008, a meeting\nwas held at Solutions with Brand, Lindenfeld, Golden, and\n 24\n\fother Solutions employees to discuss “an enormous\namount of work” that Brand wanted Strategies to do.\nJA1670. Lindenfeld said in response “we’d be glad to do\nthat, but . . . we would have to be paid.” Id. At that point,\nsomeone in the meeting stated that Strategies “had already\nbeen paid” $600,000. Id. Lindenfeld replied: “well, that\nwas for Congressman Fattah, . . . that’s not for us. So if\nyou want us to do work, we have to get paid for it\nseparately.” Id. Brand became upset with Lindenfeld over\nhis comment about being paid because his colleagues at\nSolutions were not aware of the reason for the $600,000\npayment.\n Meanwhile, EAA was attempting to meet the\ndemands of the DOJ auditors, who were focused on the\nrelationship between EAA and CORE. DOJ served a\nsubpoena upon Solutions to produce “[a]ny and all\ndocuments including, but not limited to, contract\ndocuments, invoices, correspondence, timesheets,\ndeliverables and proof of payment related to any services\nprovided to or payments received” from CORE or EAA.\nJA2350.\n\n Special Agent Dieffenbach, from the DOJ,\ninterviewed Nicholas on July 14, 2008. During that\ninterview, Nicholas discussed the relationship between\nEAA and CORE, how invoices were paid, and how\nconsultants were handled. Nicholas also answered\nquestions about EAA’s relationship with Solutions,\nincluding the payment of invoices. She did not inform\n\n 25\n\fAgent Dieffenbach of the $500,000 payment in January or\nthe subsequent $100,000 payment in May. Nor did the\ninterview address the EAA–Solutions contract that\npurportedly required those payments, because the contract\nhad yet to be produced.\n\n Solutions failed to comply with the subpoena,\nprompting an email from Agent Dieffenbach on August 26\nasking for an update concerning Solutions’ reply to the\nDOJ subpoena. Solutions then produced an undated\nversion of the EAA–Solutions contract that required the\n$600,000 upfront payment. Neither Brand nor Nicholas\nprovided the auditors with the January and May checks\nfrom EAA to Solutions.\n Efforts to conceal the repayment of the Lord loan\nand to promote the political and financial interests of\nFattah continued. The FFM campaign reports indicated in-\nkind contributions of debt forgiveness by SLA even\nthough there had been no actual debt. In September of\n2009, with EAA’s ledgers still under scrutiny, Nicholas\naltered the description of the entry for the $100,000 check\nto Solutions from “professional fees consulting” to\n“CORE Philly.” JA2546. Other FFM campaign debt was\nreduced further after Vederman negotiated with creditors.\n\n EAA never fully recovered from its payment of the\n$600,000 balance on the Lord loan and the audits that took\nplace in 2008. It began laying off employees in 2011, and\nby June of 2012, only four employees remained. JA3659.\nEAA ceased operations at some point in 2012. JA1530.\n 26\n\f 2. The College Tuition Component of the FFM\n Scheme\n Although the FFM campaign was close to insolvent,\nit nevertheless made tuition payments for Fattah’s son,\nChaka Fattah Jr., also known as Chip. Chip attended\nDrexel University, but had yet to complete his coursework\nbecause he had failed to pay an outstanding tuition\nbalance. As the FFM campaign got underway in 2007,\nFattah wanted Chip to re-enroll in classes at Drexel and\nget a degree. Fattah asked Naylor to help financially, and\nhe did so by writing checks from SLA to Drexel toward\nChip’s outstanding tuition. By October of 2007, Chip was\npermitted to re-enroll in classes.\n Although Naylor never directly addressed the issue\nwith Fattah, he agreed to assist with Chip’s outstanding\ntuition with the expectation that SLA would be repaid. The\nfirst check to Drexel in the amount of $5,000 was sent in\nAugust of 2007, with $400 payments in the months that\nfollowed until August of 2008. At some point, Chip\ninformed Naylor that the payee was no longer Drexel, but\nSallie Mae. Naylor then began sending monthly checks\nfrom SLA to Sallie Mae. Those payments, in the amount\nof $525.52, began in March of 2009 and continued until\nApril of 2011, after which Fattah told Naylor he no longer\nneeded to make them. SLA’s payments to Drexel and\nSallie Mae totaled $23,063.52.\n\n Naylor’s expectation of repayment was eventually\nrealized. Beginning in January of 2008 and continuing\n 27\n\funtil November 2010, Bowser sporadically sent SLA\nreimbursement checks from the FFM campaign with a\nnotation that payment was for “election day operation\nexpenses.” JA3136. The FFM funds had been transferred\nfrom the Fattah for Congress campaign. These\nreimbursement checks totaled $25,400. In an effort to\nconceal the source of the payments to Drexel and Sallie\nMae, and to make it appear that the younger Fattah had\nperformed services for SLA, Naylor created false tax\nforms for Chip. Chip, however, had never performed\nservices for SLA.\n\n 3. The NOAA Grant and the Phantom Conference\n In mid-December 2011, when EAA was\nexperiencing serious financial difficulties, Nicholas\nsubmitted an email request to the educational partnership\nprogram of the National Oceanic & Atmospheric\nAdministration (NOAA) for a grant “designed to provide\ntraining opportunities and funding to students at minority\nserving institutions” interested in science, technology,\nengineering, and math fields related to NOAA’s mission.\nJA3354–55. The request sought $409,000 to fund EAA’s\nannual conference scheduled for February 17–19, 2012.\nJacqueline Rousseau, a supervisory program manager at\nNOAA, participated in a conference call with Nicholas\nshortly thereafter and advised Nicholas that the agency\ncould not afford the $409,000 request but would consider\na smaller grant. Rousseau advised Nicholas that EAA\n\n\n 28\n\fwould need to submit an application if it wished to be\nconsidered for a grant.\n Before submitting a grant application, Nicholas\nemailed Rousseau about sponsoring the conference. On\nJanuary 11, 2012, Rousseau informed Nicholas that the\n“NOAA Office of Education, Scholarship Programs has\nagreed to participate and provide sponsorship funds of\n$50K to support the referenced conference.” JA6453.\nRousseau also informed Nicholas that Chantell Haskins,\nwho also worked with the student scholarship program,\nwould be the point of contact for NOAA.\n In February 2012, EAA held its annual conference\nat the Sheraton Hotel in downtown Philadelphia. The\nconference had been held at the same location each year\nsince 2008.\n\n Nicholas contacted Haskins at some point in early\n2012, inquiring about the $50,000 grant. On May 8, 2012,\nHaskins sent Nicholas an e-mail which included\ninformation about submitting proposals to fund a\nconference for students. EAA then submitted a grant\napplication, which Haskins reviewed. She advised\nNicholas on June 28, 2012 that the grant could not be used\nto provide meals, and that the date of the conference would\nhave to be pushed back, with the new date included in a\nmodified application. When Nicholas asked if expenses\nfrom a previous conference could be paid from the new\ngrant, Haskins informed her that this was not allowed.\n\n 29\n\f In early July 2012, Nicholas sent a modified grant\nproposal to Haskins. It eliminated the budget item for food\nand changed the date of the 2012 conference to October\n19–21, 2012 at the same Sheraton Hotel in Philadelphia\nwhere EAA’s annual conference had taken place earlier in\nthe year. NOAA approved a $50,000 grant for the October\n2012 conference—a conference that would never be held.\n\n Unaware that no October 2012 conference had\ntaken place, NOAA allowed Nicholas access to the\n$50,000 grant in March of 2013. She then transferred the\nentire amount from NOAA to EAA’s bank account a few\ndays later. Naylor had performed services for EAA for\nwhich he was still owed $116,590. JA3119. In discussions\nwith Naylor, Nicholas had informed him that the\nlikelihood of EAA’s being able to pay him was “[n]ot very\ngood.” JA3120. Yet several days after EAA had received\nthe $50,000 from NOAA, Nicholas sent Naylor a check\nfor $20,000. JA3120, 4283.\n\n On April 3, 2013, Nicholas submitted a final report\nto NOAA concerning EAA’s use of the grant. Notably,\npage 4 of the report stated the conference had been held in\nFebruary 2012, while page 17 stated that the conference\nhad been held from October 19 to 21, 2012. NOAA issued\na notice asking for clarification and for a list of students\nwho had been supported at the conference. Nicholas failed\nto file either a clarifying report regarding the date of the\nconference or a timely report regarding the disbursement\nof the grant. Finally, in November of 2013, Nicholas\n\n 30\n\fsubmitted the final Federal Financial Report in which she\ncertified, falsely, that the $50,000 had been used for a\nproject during the period from August 1, 2012 to\nDecember 30, 2012.\n\n B. The Blue Guardians Scheme\n In addition to functioning as the conduit for Lord’s\n$1 million loan to Fattah’s campaign, Lindenfeld’s\ncompany, Strategies, also performed services for the\ncampaign. The work resulted in indebtedness from FFM\nto Strategies of approximately $95,000. Fattah made\nseveral small payments, but failed to pay the full amount\ndue. Although Lindenfeld spoke to Fattah, Naylor and\nBowser about the debt, no payments were forthcoming.\nDuring a meeting in Fattah’s D.C. office, Fattah told\nLindenfeld “that [repayment] really wasn’t going to be\npossible because the campaign had been over for a long\ntime” and the funds were not available. JA1693. Fattah\nthen asked Lindenfeld if he could write off the debt on his\nFFM campaign finance reports. Id. Lindenfeld told Fattah\nthat as long as he was paid, it was not his business how\nFattah disclosed it on the campaign finance reports.\nJA1694.\n In lieu of repayment, Fattah suggested that\nStrategies could claim to be interested in setting up an\nentity to address environmental issues and ocean pollution\nalong the coastline and in the Caribbean. Fattah explained\nthat creating such an entity would make it possible to\nobtain an appropriation from the government. Hearing\n 31\n\fthis, Lindenfeld knew he was not going to be paid by the\nFFM campaign, and was amenable to receiving money\nfrom an appropriation instead. At a later meeting,\nLindenfeld told Fattah that the name of the entity would\nbe “Blue Guardians.” Lindenfeld consulted with an\nattorney about creating Blue Guardians as an entity to\nreceive the federal grant. He emailed Fattah, asking\nquestions about how to complete an application to the\nHouse Appropriations Committee. Fattah provided\nsuggestions, and an application was eventually completed.\nIt indicated that Blue Guardians would be “in operation for\na minimum of ten years,” and, in accordance with Fattah’s\nguidance, requested $15 million in federal funds. JA1711–\n13.\n Lindenfeld submitted the application to Fattah’s\noffice in April of 2009. Afterward, a Fattah staffer\ncontacted Lindenfeld to suggest that he change his\nWashington, D.C., address to Philadelphia because that\nwas the location of Fattah’s district. Fattah later suggested\nto Lindenfeld that Brand might allow the use of his\nPhiladelphia office address, a plan to which Brand agreed.\n\n In February 2010, Lindenfeld submitted a second\napplication to the Appropriations Committee. In March,\nFattah submitted a project request using his congressional\nletterhead and seeking $3,000,000 for the “Blue\nGuardians, Coastal Environmental Education Outreach\nProgram.” JA6432. Within a month, Blue Guardians had\nboth articles of incorporation and a bank account. Around\n\n 32\n\fthat time, a news reporter contacted Lindenfeld to discuss\nthe new Blue Guardians entity. The inquiry made\nLindenfeld uncomfortable, and he ultimately decided to\nabandon the Blue Guardians project. He continued to seek\npayment from Fattah, to no avail.\n\n Nonetheless, having obtained Lindenfeld’s\nacquiescence to writing off the campaign’s debt to\nStrategies, Fattah started falsifying FFM’s campaign\nreports. Beginning in 2009 and extending through 2013,\nthe FFM campaign reports executed by Fattah and Bowser\nstated that Strategies made in-kind contributions of\n$20,000, until the debt appeared to have been paid in full.\n\n C. The Fattah–Vederman Bribery Scheme\n Vederman and Fattah were personal friends.\nVederman was a successful businessman who had also\nserved in prominent roles in the administrations of Ed\nRendell when he was Mayor of Philadelphia and Governor\nof Pennsylvania. In November of 2008, Vederman was a\nsenior consultant in the government and public affairs\npractice group of a Philadelphia law firm. His assistance\nto the FFM campaign included paying for rented vans used\nin the get-out-the-vote effort.\n\n After Fattah’s electoral defeat, the campaign still\nowed more than $84,000 to a different law firm for\nservices performed for the campaign. Vederman\napproached that firm in the summer of 2008 asking if it\nwould forgive FFM’s debt. Negotiations resulted in a\n 33\n\fcommitment from FFM to pay the firm $30,000 by the end\nof 2008 in exchange for forgiveness of $20,000, all of\nwhich would appear on the FFM campaign finance report.\nVederman’s efforts also led to payment by Fattah of an\nadditional $10,000 in 2009 to the law firm, in exchange\nfor additional forgiveness of $20,000 of debt. It was not\nlong after Vederman’s successful efforts to lower Fattah’s\ncampaign debt, that Fattah wrote a letter to U.S. Senator\nRobert P. Casey recommending Vederman for an\nambassadorship.\n\n At some point in 2010, Vederman again intervened\non behalf of the FFM campaign. FFM remained in debt to\nan advertising and public relations firm owned by Robert\nDilella. By late 2011, Vederman and Dilella had worked\nout a settlement to resolve the outstanding debt. Pursuant\nto that settlement, Dilella received partial payment from\nthe FFM campaign: $25,000 in satisfaction of a $55,000\ndebt. Dilella testified at trial that he would not have agreed\nto retire a portion of the debt had he known the FFM\ncampaign was paying college tuition for Fattah’s son.\n Vederman helped Fattah financially in other ways.\nBefore the 2006 FFM campaign, Fattah and his wife,\nRenee Chenault-Fattah, sponsored a young woman named\nSimone Muller to live with them as an au pair exchange\nvisitor. Muller was from South Africa, and her J-1 visa\nallowed her to serve as a nanny and to study in the United\nStates. Muller later applied for and received a second visa,\nan F-1 student visa that indicated she had been accepted as\n\n 34\n\fan international student at the Community College of\nPhiladelphia. The application indicated that Muller would\nagain be residing with the Fattahs. Notwithstanding this\nliving arrangement, Fattah identified Vederman as the\nperson who would be paying for Muller’s trip to the\nUnited States.\n By the beginning of 2010, Muller wished to transfer\nto Philadelphia University. This required her to submit\nverification that funds were available to pay for her study.\nAlthough the Fattahs were Muller’s sponsors, Fattah\nexplained to the University’s Dean of Enrollment Services\nthat he was submitting a letter of secondary support from\nVederman. JA3754, 3763–65, 6504. Without Vederman’s\nJanuary 2010 letter of support, the University would not\nhave admitted Muller. In addition to this pledge of support,\nVederman paid $3,000 of Muller’s tuition. Shortly\nthereafter, Fattah resumed his efforts to secure an\nambassadorship for Vederman.\n\n In February of 2010, Fattah staffer Maisha Leek\ncontacted Katherine Kochman, a scheduler for White\nHouse Chief of Staff Rahm Emanuel. Leek requested a\ntelephone conference with Emanuel, Rendell, and Fattah\nto discuss Vederman’s “serving his country in an\ninternational capacity.” JA2893. In a follow-up email on\nMarch 26, Leek sent documents to Kristin Sheehy, a\nsecretary to White House Deputy Chief of Staff James\nMessina. The documents included Fattah’s 2008 letter to\nSenator Casey and Vederman’s biography. After\n\n 35\n\fparticipating in a telephone conference about Vederman\nwith Fattah and Rendell, Messina sent Vederman’s\nbiography to the White House personnel office for\nconsideration.\n\n As the April 2010 tax deadline approached, Fattah\nstill owed the City of Philadelphia earned income tax in\nthe amount of $2,381. Just days before the filing deadline,\nVederman gave a check to Chip Fattah for $3,500. The\nyounger Fattah quickly deposited $2,310 into his father’s\nbank account. Fattah paid his tax bill on April 15. Without\nChip’s deposit into his father’s bank account, the older\nFattah would not have had sufficient funds to pay his tax\nbill.\n On October 30, 2010, Vederman gave Chip another\ncheck, this one for $2,800. That same day, Fattah hand-\ndelivered a letter to President Obama recommending\nVederman for an ambassadorship. A few weeks later,\nFattah’s staffer, Leek, sent the letter that Fattah had given\nto President Obama to Messina’s office. That letter\npointed out that both Rendell and Fattah had sent letters\non behalf of Vederman, and that he was an\n“unquestionably exceptional candidate for an\nambassadorship.” JA6291–92.\n\n Fattah’s efforts to secure Vederman an\nambassadorship were unsuccessful. Fattah then shifted\ngears and sought to secure Vederman a position on a\nfederal trade committee. Fattah approached Ron Kirk, who\nserved as U.S. Trade Representative, and asked him to\n 36\n\fspeak with a constituent. In May of 2011, Leek followed\nup on that discussion by emailing Kirk and asking him to\nmeet with Vederman. Kirk met with Vederman on June 5,\n2011 and explained to him the role of the trade advisory\ncommittees. Although the two men “had a very nice\nconversation,” JA 3566, it soon became “pretty apparent\nto [Kirk and his staff] that [serving on a trade advisory\ncommittee was] not what Mr. Vederman was interested\nin.” JA3567. As Kirk put it, “it was obvious that\n[Vederman] was looking for something perhaps more\nrobust in his mind or . . . higher profile than one of our\nadvisory committees.” Id. Given Vederman’s lukewarm\ninterest, no appointment to an advisory committee was\nforthcoming.\n In late December 2011, the Fattahs applied for a\nmortgage so they could purchase a second home in the\nPoconos. Shortly after applying for the mortgage, Fattah\nemailed Vederman, offering to sell him his wife’s 1989\nPorsche for $18,000. Vederman accepted the offer. The\nnext day, Vederman wired $18,000 to Fattah’s Wright\nPatman Federal Credit Union account.\n\n The Credit Union Mortgage Association (CUMA)\nacted as the loan processing organization for the home\nmortgage. Because CUMA is required to verify the source\nof any large deposits, CUMA’s mortgage loan processor,\nVictoria Souza, contacted Fattah on January 17, 2012, to\nconfirm the source of the $18,000. Fattah informed Souza\nthat the $18,000 represented the proceeds of the Porsche\n\n 37\n\fsale. Souza requested documentation, including a signed\nbill of sale and title.\n That same day, Bowser emailed Vederman a blank\nbill of sale for the Porsche. After Vederman signed the bill\nof sale, Fattah forwarded it to Souza. The bill of sale was\ndated January 16, 2012, which was the day before Souza\nhad requested the documentation. It bore the signatures of\nRenee Chenault-Fattah and Herbert Vederman, with\nBonnie Bowser as a witness.\n\n Fattah also provided Souza with a copy of the\nPorsche’s title. It was dated the same day it was sent to\nSouza, and bore signatures of Chenault-Fattah as the seller\nand Vederman as buyer, along with a notary’s stamp.\nNeither Vederman nor Chenault-Fattah actually appeared\nbefore the notary.\n\n Vederman never took possession of the Porsche.\nRenee Chenault-Fattah continued to have the Porsche\nserviced and insured long after the purported sale had\ntaken place. Moreover, the Porsche remained registered in\nChenault-Fattah’s name, and was never registered to\nHerbert Vederman. When FBI agents searched the\nFattahs’ home in 2014, the Porsche was discovered in the\nFattahs’ garage.\n\n On January 24, 2012, the Fattahs wired $25,000 to\nthe attorney handling the escrow account for the purchase\nof the vacation home. Without the $18,000 transfer from\n\n 38\n\fVederman, the Fattahs would not have had sufficient funds\nin their bank accounts to close on the home.\n Around the same time that the Fattahs were\npurchasing the house in the Poconos, Fattah’s Philadelphia\noffice hired Vederman’s longtime girlfriend, Alexandra\nZionts. Zionts had long worked for a federal magistrate\njudge in Florida. Near the end of 2011, the magistrate\njudge retired, leaving Zionts ten months shy of obtaining\nthe necessary service required to receive retirement\nbenefits. If Zionts could find another job in the federal\ngovernment, her benefits and pension would not be\nadversely affected. Vederman assisted Zionts in her job\nsearch, which included calling Fattah. Fattah hired her, a\nmove that put his congressional office overbudget. Zionts\nworked in Fattah’s office for only about two months,\nleaving to work for a congressman from Florida.\n\n Tia Watson, who performed constituent services for\nFattah and worked on the same floor as Zionts in Fattah’s\ndistrict office, testified she had no idea what work Zionts\nperformed. Although Zionts contacted Temple University\nabout archiving Fattah’s papers from his career in both the\nstate and federal government, an employee from Temple\nUniversity observed that Zionts’ work contributed nothing\nof value to the papers project.\n\n D. The Indictment and Trial\n Fattah’s schemes eventually unraveled. On July 29,\n2015, a federal grand jury in the Eastern District of\n 39\n\fPennsylvania returned a twenty-nine count indictment\nalleging that Fattah and his associates had engaged in a\nvariety of criminal acts. Fattah, Vederman, Nicholas,\nBrand, and Bowser were charged with unlawfully\nconspiring to violate the Racketeer Influenced and Corrupt\nOrganizations Act (RICO), 18 U.S.C. § 1962(d). In\naddition to the RICO charge, the indictment alleged that\nFattah and certain co-defendants had unlawfully conspired\nto commit wire fraud, 18 U.S.C. §§ 1343, 1349; honest\nservices fraud, 18 U.S.C. §§ 1343, 1346, 1349; mail fraud,\n18 U.S.C. §§ 1341, 1349; money laundering, 18 U.S.C.\n§ 1956; and to defraud the United States, 18 U.S.C. § 371.\nSeveral defendants were also charged with making false\nstatements to banks, 18 U.S.C. § 1014; falsifying records,\n18 U.S.C. § 1519; laundering money, 18 U.S.C. § 1957;\nand engaging in mail, wire, and bank fraud, 18 U.S.C.\n§§ 1341, 1343, and 1344.\n\n The RICO charge alleged that the defendants and\nother co-conspirators constituted an enterprise aimed at\nsupporting and promoting Fattah’s political and financial\ninterests. The efforts to conceal the $1 million Lord loan\nand its repayment are at the heart of the RICO conspiracy\nand the Fattah for Mayor scheme. The indictment further\nalleged that the RICO enterprise involved: (1) the scheme\nto satisfy an outstanding campaign debt by creating the\nfake “Blue Guardians” nonprofit; and (2) the bribery\nscheme to obtain payments and things of value from\nVederman in exchange for Fattah’s efforts to secure\nVederman an appointment as a United States Ambassador.\n 40\n\f A jury trial, before the Honorable Harvey Bartle III\nof the Eastern District of Pennsylvania, began on May 16,\n2016, and lasted about a month. 7 Judge Bartle charged the\njury on Wednesday, June 15, 2016, and deliberations\nbegan late that afternoon. The following day, after\ndeliberating for only four hours, the jury sent a note to the\njudge. Written by the foreperson, the note read:\n Juror Number 12 refuses to vote by the letter\n of the law. He will not, after proof, still\n change his vote. His answer will not change.\n He has the 11 of us a total wreck knowing that\n we are not getting anywhere in the hour of\n deliberation yesterday and the three hours\n today. We have zero verdicts at this time all\n due to Juror Number 12. He will not listen or\n reason with anybody. He is killing every\n other juror’s experience. We showed him all\n the proof. He doesn’t care. Juror Number 12\n has an agenda or ax to grind w/govt.\nJA5916.\n\n Shortly after receiving the foreperson’s note, the\nCourt received a second communication—a note signed\n\n\n\n 7\n The District Court dismissed one charge prior to\ntrial: an individual money laundering count against\nNicholas.\n 41\n\fby nine jurors, including the foreperson. The second note\nread:\n We feel that [Juror 12] is argumentative,\n incapable of making decision. He constantly\n scream [sic] at all of us.\nId.\n Judge Bartle met with counsel in his chambers and\nadvised them of his intention to voir dire both the\nforeperson and Juror 12 in an effort to determine whether\nthe juror was deliberating as required by his oath. The\nJudge also indicated that he would “stay away from the\nmerits of the case,” and that whether he would voir dire\nmore jurors “remain[ed] to be seen.” JA5917.\n Counsel for the defendants objected to the Court’s\nproposed inquiry. As a group, they indicated that while the\nnote could be read as suggesting “a flat refusal to\ndeliberate,” they were of the opinion that it sounded “more\nin the manner of a disagreement over the evidence.”\nJA5918. Nicholas’s counsel specifically argued that\nquestioning the jurors so quickly after the start of\ndeliberations would send a message that differences of\nopinion among a block of jurors could be resolved by\ncomplaining to the Court. Defense counsel acknowledged\nthat the case law gave Judge Bartle wide discretion on how\nto proceed, but suggested that a “less intrusive” course of\naction was preferred. JA5918–19. They collectively urged\n\n 42\n\fthe Court to do nothing more than remind the jurors of\ntheir duty to deliberate.\n The Government agreed with Judge Bartle’s\nproposed voir dire. In the prosecution’s view, the Court\nhad already given proper instructions to the jury on their\nduty to deliberate. The Government further argued that if\nJuror 12 had exhibited bias, as suggested in the notes, he\nwould have lied during the voir dire process and his\nrefusal to deliberate would be “further evidence of that and\nhis unsuitability as a juror.” JA5921.\n\n With all counsel present, and over defense counsel’s\nobjections, Judge Bartle ultimately questioned five jurors\nin chambers. He questioned Juror 2 (the foreperson), Juror\n12 (the subject of the complaints), Juror 3, Juror 6, and\nJuror 1.\n\n Judge Bartle began each voir dire by informing the\njuror that he would ask a series of questions, but would not\ninquire into the merits of the case or how any juror was\nvoting. Each juror was placed under oath, and Judge Bartle\nasked, among other questions, whether screaming was\noccurring; whether the jurors were discussing the\nevidence; whether Juror 12 was placing his hands on other\njurors; and whether Juror 12 was unwilling to follow his\ninstructions.\n The foreperson acknowledged that he had written\nthe initial note during lunch earlier that day. He stated that\nJuror 12 was not willing to follow the law, but instead\n 43\n\f“want[ed] to add his own piece of the law . . . which has\nnothing to do with it.” JA5927–28. The foreperson further\ntestified that Juror 12 “was standing up screaming” and\nthat “[i]t was everybody pretty much against [Juror 12].”\nJA5929. He testified that Juror 12 “has his own agenda,”\nand that Juror 12 put his hand on another juror. JA5930.\nThe foreperson also stated that the jury had discussed only\na single count since the day before, and that they were still\ndiscussing it. When the District Court responded that the\njurors should understand that they could take as much time\nas they needed, the foreperson responded: “I understand\nthat. . . . [W]e all understand it. But we feel that he’s just—\nhe’s got another agenda.” JA5934.\n Judge Bartle advised counsel that he considered this\n“a very serious situation” and that he would proceed to\nvoir dire Juror 12. JA5937. Fattah’s counsel renewed his\nobjection to questioning Juror 12, which the Court\noverruled. Brand’s counsel argued that because the Court\nhad decided to voir dire Juror 12, it should also voir dire\nan additional juror. The Court agreed to do so.\n When the Court questioned Juror 12, he admitted to\nhaving “yelled back” at others, but only when they raised\ntheir voices to him. JA5939. Juror 12 contended that he, in\nfact, was “the only one” deliberating. Id. When an initial\nvote was taken the previous afternoon, his vote “was\ndifferent than everybody else’s.” Id. Juror 12 explained to\nthe other jurors why his vote was different, bringing up\nspecific evidence. In response, the other jurors said “that\n\n 44\n\fdoesn’t mean anything” and “pointed to the indictment.”\nJA5940. Juror 12 told the other jurors that the indictment\nis not evidence. Id. In response, the others “threatened to\nhave [him] thrown off.” Id.\n\n Juror 12 testified that a similar sequence of events\nhad taken place that morning. After a brief period of\ndeliberations, another vote was taken, and with the same\nresult as the previous afternoon. A discussion ensued, and\nthe other jurors again “point[ed] to the indictment.” Id.\nJuror 12 told them to “read the charge,” “[t]he indictment\nis not evidence.” Id. They read the charge, and Juror 12\nagain attempted to explain his view, but the other jurors\npaid little attention. Accordingly, Juror 12 told the others\nthat if they did not want him there, he “[didn’t] want to be\n[there]”—he would be “[o]kay with it” if they wanted him\ntaken off the jury. JA5941.\n Upon hearing this testimony, Judge Bartle again\nasked about the tone of deliberations. Juror 12 repeated\nthat he raised his voice only in response to others who did\nso—he did “not want to yell at anybody.” JA5942. Judge\nBartle then asked whether he had touched other jurors.\nJuror 12 replied that he had not hurt anyone. When asked\nif he had put his hand on anybody’s shoulder, Juror 12\nanswered: “I couldn’t remember to be honest with you.”\nJA5946.\n\n Following Juror 12’s voir dire, the Court summoned\nJuror 3 to chambers. Juror 3 testified that, after discussion\nof a particular count, there was one juror at odds with the\n 45\n\fothers. According to Juror 3, “the rest of the jurors\npounced on the gentleman with the . . . dissenting\nopinion.” JA5948. Juror 3 testified that Juror 12 “got very\ndefensive and just a little bit [] impatient” and that “the\nother jurors were very impatient with him.” Id. Juror 3 did\nnot recall witnessing Juror 12 putting his hand on any\nother jurors.\n\n The Government requested that the Court voir dire\nanother juror. Defense counsel objected, claiming that the\nquestioning “threaten[ed] . . . the entire deliberative\nprocess.” JA5949–50. Judge Bartle reminded counsel that\nhe had the authority to question each juror, and called for\nvoir dire of Juror 6.\n Juror 6 testified that the jury had been discussing the\ncase and reviewing the evidence, but that Juror 12 “wants\nto be seen” and was “being obstinate.” JA5951–52.\nAccording to Juror 6, Juror 12 “may not agree” with the\nconclusion of other jurors but “doesn’t give valid reasons\nas to why he may disagree with the charge.” JA5952. Juror\n6 also revealed that Juror 12 was the first to raise his voice,\nand that he may have touched her and another juror. When\nasked to clarify what she meant by Juror 12 disagreeing\nwith “the charge,” Juror 6 testified that Juror 12 was\n“reading maybe too deeply into it and putting his own\nemotions into it instead of just looking at what it says [and]\nwhat the facts are.” JA5952, 5955. According to Juror 6,\nJuror 12 “just continues to read past that into his own mind\nof what he feels it should be.” JA5955. Juror 6 testified\n\n 46\n\fthat Juror 12’s “justification for some of his responses [did\nnot] seem to relate to what the matter [was] before\n[them].” JA5957.\n Judge Bartle chose to hear from yet another juror.\nJuror 1 was called and informed the Court and counsel that\nthe jury “really [hadn’t] been able to even start the\ndeliberation process” in light of the disruptive behavior of\n“one particular individual.” JA5958–59. The particular\nindividual, according to Juror 1, was “very opinionated”\nand “[came] into the process with his view already\nestablished, refusing to even listen to any of the evidence\n. . . [being] very forceful . . . standing up, yelling, pointing\nhis finger.” JA5959. When asked if this individual was\nwilling to follow the Court’s instructions, Juror 1 testified\nthat he “pours [sic] over the documents very well” but that\nhe was adding other factors to answer the question on the\nverdict form, such as “what did this person feel.” JA5961.\nWhen Judge Bartle advised that intent was an appropriate\nconsideration, Juror 1 agreed but said that Juror 12 was\n“trying to investigate . . . going way beyond the scope” of\nthe evidence before them. JA5961–62. Juror 12, he said,\n“has an opinion and that opinion is established.” JA5962.\nHe stated that Juror 12 was “not willing to listen to any\nsort of reason or any sort of what everyone else is saying”\nbut instead, was “trying to force everyone else to get to his\npoint of view.” Id. “[I]f he feels like he’s not getting there,\nhe gets louder and louder and points and puts his hand on\nyour shoulder . . . .” Id.\n\n 47\n\f After questioning the five jurors (Jurors 1, 2, 3, 6,\nand 12), Judge Bartle heard argument from counsel. The\nattorney for the Government pointed out that the Court\nwould have to make a credibility determination because\nJuror 12 stated that he did not recall touching anyone. In\nthe Government’s view, Juror 12 was disrupting the\nprocess and should be removed. Defense counsel\ndisagreed. They argued that Juror 12 was conscientious\nand was engaging with the evidence. They pointed out that\ndespite the testimony that Juror 12 was reading too deeply\ninto the instructions or introducing new factors for the jury\nto consider, Juror 6 had testified that the jurors “talked it\nthrough” and resolved the concern. JA5965. Defense\ncounsel argued that the jury was discussing intent, an issue\nthat was at the heart of the case. Defense counsel perceived\nno breakdown in deliberations and argued that dismissal\nwould be premature. They suggested, instead, that the\nCourt provide a supplemental instruction.\n\n Judge Bartle decided to adjourn for the afternoon.\nBut before he left the courtroom, defense counsel brought\ntwo matters to his attention. First, in light of testimony\nduring the voir dire, they asked that the jury be\nreinstructed that the verdict form and indictment were not\nevidence. Second, they apprised the Judge of the standard\nfor juror dismissal set forth in United States v. Kemp, 500\nF.3d 257 (3d Cir. 2007). Defense counsel stated that under\nKemp, a request to discharge a juror must be denied if there\nis a possibility that the request stems from the juror’s view\nof the evidence. Judge Bartle expressed hesitation on\n 48\n\freinstructing the jury, but agreed that Kemp would control\nhis determination as to whether dismissal was appropriate.\n With the following morning came a new revelation.\nWith counsel in chambers, the Judge informed them that\n“additional significant evidence” had come to light since\nthe previous day’s recess. JA5980. He placed his\ncourtroom deputy under oath, and she proceeded to testify\nto an exchange that had occurred the previous day as she\nwas escorting Juror 12 back to the jury room after he had\nbeen voir dired. According to the deputy, Juror 12 stopped\nher in the hallway, placed his hand on her shoulder, and\nlooked her “straight in the eye.” JA5981. He then said:\n“I’m going to hang this jury.” Id. The deputy then related\nthat before any further conversation could take place\nbetween Juror 12 and the deputy, Judge Bartle summoned\nJuror 12 back to his chambers. Later that day, however,\nJuror 12 and the courtroom deputy had another exchange.\nShe testified that after all five jurors had been questioned,\nJuror 12 emerged from the jury room and told her “I really\nneed to talk to you.” JA5982. She informed Judge Bartle\nand counsel that Juror 12 “said more about how they’re\ntreating him and what he’s saying to them.” Id. He flatly\nstated that “it’s going to be 11 to 1 no matter what.” Id.\n\n There were no follow-up questions for the deputy.\nInstead, defense counsel suggested that what Juror 12 may\nhave meant was that he was willing to hang the jury\nbecause of a lack of evidence. They requested that Juror\n12 be asked about his comments to the deputy.\n\n 49\n\f After once again summoning Juror 12 to his\nchambers, the Judge advised him that “[s]ome questions\nhave arisen” about what he may have done after being voir\ndired the previous day. JA5985. Juror 12 acknowledged\nhaving conversations with the courtroom deputy. When\nasked “what happened” and “[w]hat occurred,” Juror 12\nresponded: “Basically, I said that there was a lot of name\ncalling going on.” JA5985. He said comments had been\nmade by other jurors about his service in the military. He\nspecifically referred to other jurors’ suggesting that he had\npossibly “hit [his] head . . . hard a few times” while\nserving in a parachute regiment. JA5986. He testified he\nhad conveyed these comments to the deputy and that he\nfound them offensive. When asked if he said anything else\nto the deputy, Juror 12 responded: “I may have. I really\ncan’t recall.” JA5987. And when Judge Bartle followed up\nby asking if he could recall anything else that he said to\nthe deputy, Juror 12 simply replied: “No. To me, that was\nthe most important thing.” Id. Juror 12 was then excused\nfrom chambers.\n Defense counsel next requested that the juror be\nasked directly whether he told the courtroom deputy that\nhe was going to “hang this jury.” JA5988. Juror 12 was\nrecalled to chambers, and the following back and forth\ntook place:\n\n The Court: You may be seated. And, of\n course, [Juror 12], you know you’re under\n oath here from yesterday?\n\n 50\n\f Juror 12: Yes, sir.\n The Court: . . . Did you say to [the courtroom\n deputy] that you’re going to hang this jury?\n Juror 12: I said I would.\n The Court: You did?\n Juror 12: I did. I said—I told her—I said, we\n don’t agree; I’m not just going to say guilty\n because everybody wants me to, and if that\n hangs this jury, so be it.\n ....\n Juror 12: I did say that, sir.\n The Court: You didn’t remember that before?\n Juror 12: I’m more concerned about people\n spitting on my military record.\n The Court: Did you say that you’d hang the\n jury no matter what?\n Juror 12: If they do—if we cannot come to—\n The Court: No. The question is what you said\n to her. Did you say to her you would hang the\n jury no matter what?\n Juror 12: I can’t really remember that. I did\n say that if we didn’t—a person—no matter\n what, I can’t recall that exactly.\n The Court: All right. Thank you very much.\n You can wait just out there in the anteroom.\nJA5989–90.\n\n Defense counsel continued to oppose Juror 12’s\ndismissal. They argued that the juror’s concern was about\n\n 51\n\fthe evidence, and that his comments to the courtroom\ndeputy reflected a conviction that “he’s not going to agree\njust because others want him to agree.” JA5991. They also\nargued that nothing should be made of Juror 12’s failure\nto mention the comments when initially questioned by the\nCourt, and that a supplemental instruction was all that was\nwarranted given the early stage of the deliberations.\n\n The Government strongly disagreed. The Assistant\nUnited States Attorney argued that Juror 12 “should\nabsolutely be removed” because “his demeanor ha[d]\ndemonstrated a hostility . . . both to the other jurors and to\nthe court.” JA5993. The Government also suggested that\nJuror 12’s comments that he would hang the jury meant\nthat he was not participating in the deliberations and was\nignoring the evidence and the law.\n\n Ruling from the bench, Judge Bartle announced:\n I find [the deputy clerk] to be credible. I find\n [Juror 12], not to be credible. I find that [Juror\n 12] did tell [the deputy clerk] that he was\n going to hang this jury no matter what.\n There have been only approximately\n four hours of deliberation. There’s no way in\n the world he could have reviewed and\n considered all of the evidence in the case and\n my instructions on the law.\n I instructed the jury to deliberate,\n meaning to discuss the evidence; obviously,\n to hold onto your honestly held beliefs, but at\n 52\n\f least you have to be willing to discuss the\n evidence and participate in the discussion\n with other jurors.\n Juror number 12 has delayed,\n disrupted, impeded, and obstructed the\n deliberative process and had the intent to do\n so. I base that having observed him, based on\n his words and his demeanor before me.\n He wants only to have his own voice\n heard. He has preconceived notions about the\n case. He has violated his oath as a juror.\n And I do not believe that any further\n instructions or admonitions would do any\n good. I think he’s intent on, as he said,\n hanging this jury no matter what the law is,\n no matter what the evidence is.\n Therefore, he will be excused, and I\n will replace him with the next alternate . . . .\n\nJA5994–95.\n In response, defense counsel moved for a mistrial,\nwhich the judge promptly denied. He then informed the\nreconstituted jury that deliberations would need to start\nover, and reinstructed them on certain points of law,\nincluding that the verdict slip does not constitute evidence.\n\n Judge Bartle elaborated upon his decision to remove\nJuror 12 in two post-trial memorandum opinions. In the\nfirst, ruling on a media request for the sealed transcripts,\nhe explained:\n 53\n\f Here, there is no doubt that Juror 12\n intentionally refused to deliberate when he\n declared so early in the process that he would\n hang the jury no matter what. This finding\n was predicated on the admission of Juror 12\n as reported by the court’s deputy clerk. The\n facts became clear to the court after hearing\n the credible testimony of the deputy clerk and\n the less credible testimony of Juror 12. The\n demeanor of Juror 12 before the court\n confirmed the court’s findings.\n\nGSA23–24. The second opinion addressed motions for\nbail pending appeal from Nicholas and Brand. GSA25.\nThere, Judge Bartle explained:\n\n The law is well-settled that the court has\n discretion to act as it did under these\n circumstances. See United States v. Kemp,\n 500 F.3d 257, 304 (3d Cir. 2007). The court,\n after taking testimony, specifically found that\n the juror, following only a few hours of\n deliberation, stated to the court’s courtroom\n deputy clerk that he would hang this jury no\n matter what. He could not possibly have\n reviewed all of the law and evidence of this\n five-week trial at the time he made his\n remark. The court examined the deputy clerk\n and the juror under oath in the presence of\n counsel for all parties. The undersigned\n\n 54\n\f found the deputy clerk to be credible and the\n juror not to be credible. Based on the juror’s\n demeanor, it was clear he would not change\n his attitude and that his intent had been and\n would continue to be to refuse to deliberate\n in good faith concerning the law and the\n evidence.\n\nGSA32.\n After deliberating for approximately 15 hours, the\njury returned with its verdicts on June 21, 2016, finding\nthe defendants guilty on most counts. Fattah, Vederman,\nand Brand were convicted on all counts. The jury acquitted\nBowser on sixteen counts, but found her guilty of the\nbribery conspiracy and the associated charges of bank\nfraud, making false statements to a financial institution,\nfalsifying records, and money laundering (Counts 16, 19,\n20, 21 and 22). The jury also acquitted Nicholas of wire\nfraud (Count 24). See Nicholas Supp. App. (NSA) 36.\n The following week, on June 27, the Supreme Court\nissued its opinion in McDonnell v. United States, 136 S.\nCt. 2355 (2016). McDonnell provided new limitations on\nthe definition of “official acts” as used in the honest\nservices fraud and bribery statutes under which Fattah and\nVederman had been convicted. Id. at 2369–72. Fattah and\nVederman both moved to set aside their convictions. The\nDistrict Court “acknowledge[d] that under McDonnell our\ninstructions to the jury on the meaning of official act\nturned out to be incomplete and thus erroneous.” JA103.\n 55\n\fBut the Court held that “the incomplete and thus erroneous\njury instruction on the meaning of official acts did not\ninfluence the verdict on the bribery counts” and upheld the\nverdict on Counts 16–18 and 22–23. JA107, 121.\n\n Fattah, Vederman, and Bowser had more success\nwith their other post-verdict motions. The District Court,\nin a thoughtful opinion, granted relief under Federal Rule\nof Criminal Procedure 29, acquitting Vederman of the\nRICO conspiracy (Count 1) and Fattah, Vederman, and\nBowser of bank fraud, making false statements to a\nfinancial institution, and falsifying records (Counts 19, 20,\nand 21). JA37–139.\n This appeal followed. 8 The defendants raise a\nvariety of challenges to their convictions. All defendants\nbut Bowser challenge the District Court’s decision to\ndismiss Juror 12. Fattah and Vederman argue that the\nDistrict Court erred in upholding the jury’s verdict on the\nbribery and honest services fraud counts in light of the\nSupreme Court’s decision in McDonnell. Fattah, Brand\nand Nicholas challenge the sufficiency of the evidence\nunderlying the RICO conviction. Several of the defendants\ncontend the District Court erred in its instruction on intent\nand by sending the indictment out to the jury. There are\n\n\n\n8\n Fattah, Brand, Vederman, and Nicholas each filed a\ntimely notice of appeal, but Bowser did not challenge her\nconvictions.\n 56\n\falso several evidentiary challenges.9 The Government\ncross-appeals from the District Court’s judgment\nacquitting Fattah and Vederman on Counts 19 and 20,\narguing that the District Court erred in interpreting the\ndefinition of a “mortgage lending business” under 18\nU.S.C. § 27. We address these arguments in turn.\n\n We hold that the District Court erred in upholding\nthe jury verdict in light of McDonnell, and we will\ntherefore reverse and remand for retrial on Counts 16, 17,\n18, 22, and 23. We also hold that the District Court erred\n\n9\n Pursuant to Rule 28(i), “Fattah joins in the arguments of\nHerbert Vederman, Robert Brand, and Karen Nicholas to\nthe extent their arguments on appeal apply to Mr. Fattah.”\nFattah Br. 19 n.69. Federal Rule of Appellate Procedure\n28(i) provides that a defendant, “[i]n a case involving\nmore than one appellant . . . may adopt by reference a part\nof another’s brief.” Here, Fattah’s decision to join fails to\nspecify which of the many issues of his codefendants he\nbelieves worthy of our consideration. Rather, it appears\nthat he presumes we will scour the record and make that\ndetermination for him. This type of blanket request fails to\nsatisfy Rule 28(a)(5)’s directive requiring that the\n“appellant’s brief must contain . . . a statement of the\nissues presented for review.” Fed. R. App. P. 28(a)(5). We\nconclude that expecting the appellate court to identify the\nissues to be adopted simply results in the abandonment and\nwaiver of the unspecified issues. See Kost v. Kozakiewicz,\n1 F.3d 176, 182 (3d Cir. 1993).\n 57\n\fin acquitting Fattah and Vederman on Counts 19 and 20.\nBecause the jury’s verdict was supported by the evidence,\nwe will reinstate the convictions as to those counts. In all\nother respects, we will affirm the judgment of the District\nCourt.\n\n III. Juror Misconduct and Dismissal of Juror 12 10\n Defendant Fattah challenges the District Court’s\ndecision to conduct an in camera inquiry into alleged juror\nmisconduct and the ultimate dismissal of Juror 12. 11 We\nreject both challenges. The record reveals credible\nallegations of juror misconduct and a sufficient basis to\nsupport the finding that Juror 12 violated his oath.\n\n A. Investigation of Alleged Juror Misconduct\n We first consider whether the District Court erred in\nits handling of the two notes from jurors. A trial court’s\nresponse to allegations of juror misconduct is reviewed\nunder an abuse of discretion standard. United States v.\nBoone, 458 F.3d 321, 326 (3d Cir. 2006) (citing United\nStates v. Resko, 3 F.3d 684, 690 (3d Cir. 1993)). We\nconclude that the District Court did not abuse its discretion\n\n\n10\n The District Court had jurisdiction under 18 U.S.C.\n§ 3231. We have jurisdiction under 28 U.S.C. § 1291 and\n18 U.S.C. § 3742(a).\n11\n Vederman, Nicholas, and Brand adopt Fattah’s claim of\nreversible error concerning the dismissal of Juror 12.\n 58\n\fin addressing the issues raised in the jurors’ notes to the\nCourt.\n Trial courts are afforded discretion in responding to\nallegations of juror misconduct. This is so because “the\ntrial court is in a superior position to observe the ‘mood at\ntrial and the predilections of the jury.’ ” Resko, 3 F.3d at\n690 (quoting United States v. Chiantese, 582 F.2d 974,\n980 (5th Cir. 1978)). But this discretion is not unlimited.\nOnce the jury retires to deliberate, the confidentiality of its\ndeliberations must be closely guarded. An accused is\nconstitutionally entitled to be tried before a jury of his\npeers. As ordinary citizens, jurors are “expected to speak,\ndebate, argue, and make decisions the way ordinary people\ndo in their daily lives.” Pena-Rodriguez v. Colorado, 137\nS. Ct. 855, 874 (2017) (Alito, J., dissenting). To protect\nagainst intrusion into a defendant’s right to be judged only\nby fellow citizens, “the door to the jury room [is] locked.”\nId. at 875.\n In Boone, this Court considered the threshold for\nintervention by a trial judge who is presented with\nallegations of juror misconduct during the course of\ndeliberations. 458 F.3d at 327. We recognized that “[i]t is\nbeyond question that the secrecy of deliberations is critical\nto the success of the jury system.” Id. at 329. But that\nsecrecy abuts a competing interest—the jury’s proper\nexecution of its duties. That is, “a juror who refuses to\ndeliberate or who commits jury nullification violates the\nsworn jury oath and prevents the jury from fulfilling its\n\n 59\n\fconstitutional role.” Id. Recognizing these competing\ninterests, we declined in Boone to adopt a sweeping\nlimitation on a trial court’s ability to investigate\nallegations of misconduct during jury deliberations. See id.\nConsistent with the standard applied at other stages of\ncriminal proceedings, Boone teaches that “where\nsubstantial evidence of jury misconduct—including\ncredible allegations of jury nullification or of a refusal to\ndeliberate—arises during deliberations, a district court\nmay, within its sound discretion, investigate the\nallegations through juror questioning or other appropriate\nmeans.” Id.\n Fattah argues that the District Court had no basis to\nquestion any of the jurors. Fattah Br. 20. We disagree. In\nBoone, notes from the jury presented substantial credible\nevidence of misconduct. 458 F.3d at 330. Here, the initial\nnote from the foreperson alleged that Juror 12 “refuse[d]\nto vote by the letter of the law,” would “not listen or reason\nwith anybody,” and that he had “an agenda or ax to grind”\nwith the Government. JA5916. The note contained\nallegations of both a refusal to deliberate and a suggestion\nof nullification. A refusal to deliberate is a violation of a\njuror’s oath. Boone, 458 F.3d at 329 (citing United States\nv. Baker, 262 F.3d 124, 130 (2d Cir. 2001) (“It is well-\nsettled that jurors have a duty to deliberate.”)). Moreover,\nnullification—a juror’s refusal to follow the law—is a\nviolation of the juror’s sworn oath to render a verdict\naccording to the law and evidence. See United States v.\nThomas, 116 F.3d 606, 614–18 (2d Cir. 1997) (discussing\n 60\n\fboth “benevolent” and “shameful” examples of juror\nnullification, but “categorically reject[ing] the idea that, in\na society committed to the rule of law, jury nullification is\ndesirable or that courts may permit it to occur when it is\nwithin their authority to prevent”). The second jury note,\nsigned by nine jurors, supported the claim of misconduct\nby asserting that Juror 12 was “incapable of making\ndecision[s]” and was “constantly scream[ing]” at the other\njurors. JA5916–17. We conclude that the District Court\ndid not abuse its discretion in deciding to initially question\nJuror 2, and subsequently, Jurors 12, 3, 6 and 1.\n\n Fattah also challenges the scope of the District\nCourt’s questioning. He argues that the rights to an\nimpartial jury and to a unanimous verdict “would be\nrendered toothless if trial courts had free rein to question\njurors during deliberations.” Fattah Br. 36. Indeed, we\nacknowledged the legitimacy of such a concern in Boone.\nDespite adopting a modest “credible allegations” standard\nfor investigating misconduct, we “ke[pt] in mind the\nimportance of maintaining deliberative secrecy.” Boone,\n458 F.3d at 329. Fattah asserts that the trial court’s\nquestions to the five jurors were “intrusive and pointed”\nand “nothing like the questioning . . . approved in Boone.”\nFattah Br. 38. But Fattah does not elaborate on how, in his\nview, the questions posed by Judge Bartle specifically\nintruded into deliberative secrecy.\n\n To be sure, Judge Bartle’s questioning of each juror\nwas more extemporaneous than the juror questioning in\n\n 61\n\fBoone. There, the district court asked a single juror four\n“concise and carefully-worded” questions. 458 F.3d at\n330. Judge Bartle’s voir dire of each of the five jurors took\non a more conversational tone. We take no issue with that\napproach. The substance of the judge’s questions was\nlimited and mirrored that of questions we deemed\nappropriate in Kemp. There, the court conducted three\nrounds of questioning. In the first round, each juror was\nasked:\n (1) “Are you personally experiencing any\n problems with how the deliberations are\n proceeding without telling us anything about\n the votes as to guilt or innocence? If yes,\n describe the problem.” (2) “Are all the jurors\n discussing the evidence or lack of evidence?”\n (3) “Are all the jurors following the court’s\n instructions on the law?”\n\nKemp, 500 F.3d at 273. In the second and third rounds,\neach juror was asked:\n (1) “Is there any juror or jurors who are\n refusing to deliberate?” (2) “Is there any juror\n who is refusing to discuss the evidence or\n lack of evidence?” (3) “Is there any juror who\n is refusing to follow the Court’s\n instructions?”\nId. at 274. Here, Judge Bartle began his voir dire of each\njuror by stating that he did not wish for the juror to discuss\n 62\n\fthe merits of the case or to reveal the content of the\ndeliberations that had taken place. He asked the jurors\nwhether screaming was occurring, whether the jurors were\ndiscussing the evidence, whether Juror 12 was placing his\nhands on other jurors, and whether Juror 12 was unwilling\nto follow his instructions.\n Fattah points to no specific question posed or topic\ndiscussed that was inappropriate, and we see little to no\nsubstantive difference between the questions here and\nthose asked by the trial judge in Kemp. As in Kemp, “the\nDistrict Court took care to limit its questions to appropriate\nmatters that did not touch on the merits of the jury’s\ndeliberation, and expressly informed each juror on\nmultiple occasions that he or she should not reveal the\nsubstance of the deliberations.” Id. at 302 (citing United\nStates v. Edwards, 303 F.3d 606, 634 n.16 (5th Cir. 2002)).\n Fattah also argues that once the remarks of Juror 2\nand Juror 12 revealed no further evidence of misconduct,\nthe court had no basis to question other jurors. Fattah\nReply 19. Yet, our cases make clear that a trial court may,\nin its discretion, examine each juror. Kemp, 500 F.3d at\n302 (“We have recognized that there are times in which\nindividual questioning is the optimal way in which to root\nout misconduct.”). Indeed, “the District Court must utilize\nprocedures that will ‘provide a reasonable assurance for\nthe discovery of prejudice.’ ” Id. (quoting Martin v.\n\n\n\n 63\n\fWarden, Huntingdon State Corr. Inst., 653 F.2d 799, 807\n(3d Cir. 1981)). 12\n\n Judge Bartle, a very able and experienced district\njudge, was in the best position to determine what type of\ninquiry was warranted under the circumstances. We\nconclude that his questioning of the five jurors was not an\nabuse of discretion. See id. at 302.\n\n B. Dismissal of Juror 12\n Fattah, joined by Vederman, Brand, and Nicholas,\nstrongly contends that the District Court committed\nreversible error by dismissing Juror 12. “We review the\ndismissal of a juror for cause for abuse of discretion.”\n\n12\n Our cases do not suggest that a trial judge confronted\nwith allegations that a jury’s deliberations are being\nobstructed by one of its members should always resort to\ninterviewing jurors. Reinstructing the jury on its duty to\ndeliberate will often be the better course at the first sign of\ntrouble. Mere disagreement among jurors—even spirited\ndisagreement—is no ground for intervention.\nFurthermore, intrusive or leading questions about the\ndeliberative process may work against the twin goals of\nprotecting that process and ensuring that jurors remain\nfaithful to their oaths. We share the Eleventh Circuit’s\npreference of “err[ing] on the side of too little inquiry as\nopposed to too much.” United States v. Oscar, 877 F.3d\n1270, 1287 (11th Cir. 2017) (quoting United States v.\nAugustin, 661 F.3d 1105, 1133 (11th Cir. 2011)).\n 64\n\fKemp, 500 F.3d at 303. That deferential standard compels\nus to affirm.\n Rule 23(b) of the Federal Rules of Criminal\nProcedure permits a trial court to excuse a deliberating\njuror for good cause. See id. (citing Fed. R. Crim. P.\n23(b)). Good cause exists where a juror refuses to apply\nthe law, refuses to follow the court’s instructions, refuses\nto deliberate with his or her fellow jurors, or demonstrates\nbias. See Kemp, 500 F.3d at 305–06; United States v.\nOscar, 877 F.3d 1270, 1287 (11th Cir. 2017); Thomas, 116\nF.3d at 617. Good cause does not exist when there is\nreasonable but sustained disagreement about how a juror\nviews the evidence. The courts of appeals are emphatic\nthat trial courts “may not dismiss a juror during\ndeliberations if the request for discharge stems from\ndoubts the juror harbors about the sufficiency of the\ngovernment’s evidence.” Kemp, 500 F.3d at 303 (quoting\nUnited States v. Brown, 823 F.2d 591, 596 (D.C. Cir.\n1987)); see also Oscar, 877 F.3d at 1287 (same); United\nStates v. Symington, 195 F.3d 1080, 1087 (9th Cir. 1999);\nThomas, 116 F.3d at 622.\n\n To reinforce a defendant’s right to a unanimous\njury, we have adopted a high standard for juror dismissal.\nKemp, 500 F.3d at 304 & n.26. “[D]istrict courts may\ndischarge a juror for bias, failure to deliberate, failure to\nfollow the district court’s instructions, or jury nullification\nwhen there is no reasonable possibility that the allegations\nof misconduct stem from the juror’s view of the evidence.”\n\n 65\n\fId. at 304 (emphasis added). This “no reasonable\npossibility” standard is “by no means lax.” Id. Rather, “[i]t\ncorresponds with the burden for establishing guilt in a\ncriminal trial.” Id.\n\n We first applied this standard in Kemp, but have not\nhad occasion to do so since. There, the evidence\nsupporting the district court’s removal decision was\n“overwhelming.” 500 F.3d at 304. Ten jurors separately\nand consistently reported that a juror was improperly\nbiased, and did so only after three rounds of questioning\nand careful and correct instructions from the district court\nas to the distinction between appropriate skepticism and\nimpermissible bias. Id. at 304–05; see id. at 275–76\n(district court’s instruction). The testimony also showed\nthat the juror in question refused to deliberate or to discuss\nthe evidence with her fellow jurors. Id. at 305.\n Whether the evidence of misconduct in this case is\nas strong as that in Kemp is beside the point. After only\nfour hours of deliberations, Juror 12 stated unequivocally\nto the courtroom deputy that he was “going to hang” the\njury, and that it would be “11 to 1 no matter what.”\nJA5981–82 (emphasis added). These statements, coupled\nwith the District Court’s finding that Juror 12 lacked\ncredibility, provided a sufficient basis for Juror 12’s\ndismissal.\n\n As grounds for excusing Juror 12, the District Court\nfound that he refused to deliberate in good faith, “delayed,\ndisrupted, impeded, and obstructed the deliberative\n 66\n\fprocess and had the intent to do so,” JA5995, and that he\nwas “intent on . . . hanging this jury no matter what the law\nis, no matter what the evidence is.” Id. The District Court\ndetermined from this that Juror 12 had violated his oath as\na juror and that no further instructions or admonitions\ncould rehabilitate the juror. Id. The District Court based\nthese findings on personal observation, including Juror\n12’s words and demeanor, and making the specific finding\nthat Juror 12 was not credible. That finding is amply\nsupported by the record.\n\n In United States v. Abbell, 271 F.3d 1286, 1303 (9th\nCir. 2001), the Ninth Circuit recognized that “the\ndemeanor of the pertinent juror is important to juror\nmisconduct determinations” because the “juror’s\nmotivations and intentions are at issue.” That court\nemphasized, as we do, that a district judge is best situated\nto assess the demeanor of a juror. Id. Here, Juror 12 stated\nhe could not recall putting his hand on another juror’s\nshoulder, while his fellow jurors’ testimony was consistent\non this point. Juror 12 also failed, at first, to recall his\ntroubling statements to the courtroom deputy despite\nhaving made those statements only the previous afternoon.\nWhen questioned a second time and asked directly about\nthe statements, he admitted to saying that he would hang\nthe jury but claimed he could not “really remember”\nsaying “no matter what” the day before. JA5989–90. Juror\n12’s spotty recollection of the previous day’s events\nfurther supports the District Court’s finding that he was\nnot credible.\n 67\n\f Fattah argues that the credibility determination was\nnot, by itself, a sufficient reason to dismiss the juror\nbecause the record demonstrates more than a reasonable\npossibility that the complaints about his conduct stemmed\nfrom Juror 12’s own view of the Government’s case.\nFattah Reply Br. 11; Fattah Br. 25, 28. Fattah claims that\nthe District Court abused its discretion by dismissing Juror\n12 “on the basis of, in effect, six words the juror\npurportedly said to the court’s deputy after he was verbally\nattacked by other jurors.” Fattah Br. 24. According to\nFattah, the questioning of the other jurors “confirmed that\nthere were no legitimate grounds for removing juror 12.”\nId. at 26. We conclude otherwise.\n “A district court’s finding on the question whether\na juror has impermissibly refused to participate in the\ndeliberation process is a finding of fact to which\nappropriate deference is due.” Baker, 262 F.3d at 130.\nWhile district courts must apply a high standard for juror\ndismissal, their underlying findings are afforded\nconsiderable deference on appeal. Kemp, 500 F.3d at 304\n(citing Abbell, 271 F.3d at 1302–03). We will reverse only\nif the decision to dismiss a juror was “without factual\nsupport, or for a legally irrelevant reason.” Abbell, 271\nF.3d at 1302 (citation omitted).\n Here, the District Court had a legitimate reason for\nremoving Juror 12. Refusal to deliberate constitutes good\ncause for dismissal. Although the judge did not expressly\narticulate the Kemp standard when he announced that he\n\n 68\n\fwould dismiss Juror 12, he did acknowledge the “no\nreasonable possibility” standard in his discussion with\ncounsel. The unmistakable import of the District Court’s\nstatement from the bench is that there was no reasonable\npossibility that Juror 12’s intransigence was based on his\nview of the evidence. See Oscar, 877 F.3d at 1288 n.16.\n Fattah contends that there is no record support for\nthe finding that Juror 12 said “he was going to hang this\njury no matter what.” Fattah Br. 29. To be sure, the\ncourtroom deputy’s testimony is not that Juror 12 used the\nwords “hang this jury” and “no matter what” in the same\nsentence. She testified that Juror 12 first stated “I am going\nto hang this jury,” then later stated “it is going to be 11 to\n1 no matter what.” JA5981–82. This is a distinction\nwithout a difference. Likewise, Fattah challenges the\nDistrict Court’s finding that Juror 12 was determined to\nhang the jury “no matter what the law is” and “no matter\nwhat the evidence is.” Fattah Br. 29. Although there is no\nevidence that Juror 12 uttered the phrases “no matter what\nthe law is” or “no matter what the evidence is,” the District\nCourt was describing the import of Juror 12’s statements.\nThis was not error.\n Fattah expresses the concern that “[i]f jurors are\nasked the right questions or interrogated long enough, it\nwould not be difficult for a trial court to elicit testimony\nfrom [a] majority [of] jurors that can be held up as\nevidence of a dissenting juror’s bias or refusal to\ndeliberate.” Fattah Br. 22. He also worries that a group of\n\n 69\n\fjurors might have an incentive to rid themselves of a juror\nwho holds a different view. Id. These are valid concerns—\nbut no basis existed for such concerns in this case. Juror\n12’s own words provided most of the support for his\neventual dismissal. Furthermore, his statements were\nmade early in the deliberations, in a complex case, before\nany juror could reasonably be expected to have reached\nfinal verdicts on the twenty-nine counts before the jury.\n\n The able District Judge did not err in finding that\nJuror 12 refused to deliberate and therefore violated his\noath.\n\n IV. The District Court’s Instructions Under\n McDonnell\n On appeal, Fattah and Vederman renew their\nchallenge to the jury instructions given on Counts 3, 16,\n17, 18, 22, and 23, concerning the meaning of the term\n“official act” as used in the bribery statute (pursuant to\nwhich both were convicted) and the honest services fraud\nstatute (pursuant to which Fattah alone was convicted).\n\n In light of the Supreme Court’s opinion in\nMcDonnell v. United States, 136 S. Ct. 2355 (2016),\nreleased the week after the jury verdict, the District Court\nconceded that its instructions were incomplete and\nerroneous, at least as to Counts 16–18. Nevertheless, the\nDistrict Court held that the erroneous jury instructions had\nnot influenced the verdict on the bribery counts, and\ndeclined to set aside Fattah and Vederman’s convictions.\n 70\n\fAs to Counts 16–18 and 22–23, we disagree, and will\nreverse the District Court’s judgment. The District Court’s\njudgment with respect to Count 3, which did not involve\nVederman, will be affirmed. JA78–79.\n\n A. The McDonnell Framework\n In McDonnell, the Supreme Court interpreted the\nterm “official act” as defined in 18 U.S.C. § 201(a)(3). 136\nS. Ct. at 2368. The statute defines an “official act” as “any\ndecision or action on any question, matter, cause, suit,\nproceeding or controversy, which may at any time be\npending, or which may by law be brought before any\npublic official, in such official’s official capacity, or in\nsuch official’s place of trust or profit.” 18 U.S.C.\n§ 201(a)(3). The McDonnell Court distilled this definition\ninto two requirements:\n First, the Government must identify a\n “question, matter, cause, suit, proceeding or\n controversy” that “may at any time be\n pending” or “may by law be brought” before\n a public official. Second, the Government\n must prove that the public official made a\n decision or took an action “on” that question,\n matter, cause, suit, proceeding, or\n controversy, or agreed to do so.\n\n136 S. Ct. at 2368. Applying this two-step test to Governor\nRobert McDonnell’s convictions, the Supreme Court\nconcluded that “the jury was not correctly instructed on\n 71\n\fthe meaning of ‘official act,’ ” and as a result, “may have\nconvicted Governor McDonnell for conduct that is not\nunlawful.” Id. at 2375. Given that uncertainty, the Court\n“[could not] conclude that the errors in the jury\ninstructions were ‘harmless beyond a reasonable doubt.’ ”\nId. (quoting Neder v. United States, 527 U.S. 1, 16 (1999)).\nThe Supreme Court, therefore, vacated Governor\nMcDonnell’s convictions. Id.\n\n McDonnell lays out a clear path for the Government\nto follow in proving that an accused has performed an\n“official act.” First, the Government must “identify a\n‘question, matter, cause, suit, proceeding or controversy’\nthat ‘may at any time be pending’ or ‘may by law be\nbrought’ before a public official.” 136 S. Ct. at 2368\n(quoting 18 U.S.C. § 201(a)(3)). This first step is divided\ninto two sub-components. In Step 1(A), the Government\nmust “identify a ‘question, matter, cause, suit, proceeding\nor controversy.’ ” Id. Step 1(B) then clarifies that the\nidentified “question, matter, cause, suit, proceeding or\ncontroversy” be one that “ ‘may at any time be pending’ or\n‘may by law be brought’ before a public official.” Id.\n\n Under Step 1(A), a “question, matter, cause, suit,\nproceeding or controversy” must be “a formal exercise of\ngovernmental power that is similar in nature to a lawsuit\nbefore a court, a determination before an agency, or a\nhearing before a committee.” Id. at 2372. Importantly, “a\ntypical meeting, telephone call, or event arranged by a\n\n\n 72\n\fpublic official” does not qualify as such a formal exercise\nof governmental power. Id. at 2368.\n Step 1(B) then requires us to ask whether the\nqualifying “question, matter, cause, suit, proceeding or\ncontroversy” was one that “ ‘may at any time be pending’\nor ‘may by law be brought’ before a public official.” Id.\nAs the McDonnell Court clarified, “ ‘[p]ending’ and ‘may\nby law be brought’ suggest something that is relatively\ncircumscribed—the kind of thing that can be put on an\nagenda, tracked for progress, and then checked off as\ncomplete.” Id. at 2369; accord United States v. Repak, 852\nF.3d 230, 252 (3d Cir. 2017) (quoting McDonnell, 136 S.\nCt. at 2369). By contrast, matters described at a high level\nof generality—for example, “[e]conomic development,”\n“justice,” and “national security”—are not sufficiently\n“focused and concrete.” McDonnell, 136 S. Ct. at 2369.\n\n In McDonnell, the Court concluded that at least\nthree questions or matters identified by the Fourth Circuit\nwere sufficiently focused:\n (1) whether researchers at any of Virginia’s\n state universities would initiate a study of [a\n drug]; (2) whether the state-created Tobacco\n Indemnification and Community\n Revitalization Commission would allocate\n grant money for the study of [a chemical\n compound]; and (3) whether the health\n insurance plan for state employees in\n\n 73\n\f Virginia would include [a specific drug] as a\n covered drug.\nId. at 2370 (internal quotations omitted) (quoting United\nStates v. McDonnell, 792 F.3d 478, 515–16 (4th Cir.\n2015)). We provided guidance in the form of a fourth\nexample in Repak, when we held that a redevelopment\nauthority’s awarding of contracts was “a concrete\ndetermination made by the [redevelopment authority’s]\nBoard of Directors.” 852 F.3d at 253.\n\n Step 2 requires the Government to prove that the\npublic official made a “decision” or took “an action” on\nthe identified “question, matter, cause, suit, proceeding or\ncontroversy.” McDonnell, 136 S. Ct. at 2368. The\nMcDonnell Court explained:\n Setting up a meeting, hosting an event, or\n calling an official (or agreeing to do so)\n merely to talk about a research study or to\n gather additional information . . . does not\n qualify as a decision or action on the pending\n question of whether to initiate the study.\n Simply expressing support for the research\n study at a meeting, event, or call—or sending\n a subordinate to such a meeting, event, or\n call—similarly does not qualify as a decision\n or action on the study, as long as the public\n official does not intend to exert pressure on\n another official or provide advice, knowing\n\n 74\n\f or intending such advice to form the basis for\n an “official act.”\nId. at 2371. The Court further clarified:\n\n If an official sets up a meeting, hosts an\n event, or makes a phone call on a question or\n matter that is or could be pending before\n another official, that could serve as evidence\n of an agreement to take an official act. A jury\n could conclude, for example, that the official\n was attempting to pressure or advise another\n official on a pending matter. And if the\n official agreed to exert that pressure or give\n that advice in exchange for a thing of value,\n that would be illegal.\nId.\n Here, Fattah was charged with engaging in three\ncategories of official acts, which we analyze in accordance\nwith the McDonnell framework. In Counts 16–18 and 22–\n23, Fattah is alleged to have set up a meeting between\nVederman and the U.S. Trade Representative, attempted\nto secure Vederman an ambassadorship, and hired\nVederman’s girlfriend, all in return for a course of conduct\nwherein Vederman provided things of value to Fattah.\n\n In this case, as in McDonnell, the jury instructions\nwere erroneous. We conclude that the first category of the\ncharged acts—setting up a meeting between Vederman\n 75\n\fand the U.S. Trade Representative—is not unlawful, and\nthat the second category—attempting to secure Vederman\nan ambassadorship—requires reconsideration by a\nproperly instructed jury. The third charged act—hiring\nVederman’s girlfriend—is clearly an official act. But\nbecause we cannot isolate the jury’s consideration of the\nhiring from the first two categories of charged acts, we\nmust reverse and remand the judgment of the District\nCourt.\n\n B. The Kirk Meeting\n We turn first to Fattah’s scheduling of a meeting\nbetween Vederman and the U.S. Trade Representative,\nRon Kirk. Under McDonnell, “setting up a meeting . . .\ndoes not, standing alone, qualify as an ‘official act.’ ” 136\nS. Ct. at 2368. Fattah’s setting up the meeting between\nVederman and Kirk was therefore not an official act, a\nconcession implicit in the Government’s opening brief.\nSee Gov’t Br. 32 (failing to mention the Kirk meeting as\none of the “two categories” of allegedly “official acts”).\nBut the jury was not properly instructed on this point.\nWithout the benefit of the principles laid down in\nMcDonnell, the jury was free to conclude that arranging\nthe Kirk meeting was an official act—and it may have\ndone so. The District Court’s erroneous jury instructions,\ntherefore, cannot survive harmless error review.\n\n In a footnote in its brief to this Court, the\nGovernment argues that evidence about the Kirk meeting\nwas offered only “because it established the strength of\n 76\n\fVederman’s desire to be an ambassador” and not because\nthe Government was attempting to establish the meeting\nas an independent official act. Id. at79–80 n.6. But the\nrecord undercuts the Government’s post hoc justification.\n\n The indictment, provided to the jury in redacted\nform for use in its deliberations, lists Fattah’s setting up\nthe Kirk meeting as an official act under the heading\n“FATTAH’s Official Acts for VEDERMAN.” JA494.\nUnder this heading are three distinct subheadings:\n(1) “The Pursuit of an Ambassadorship,” (2) “The Pursuit\nof Another Executive Branch Position,” and (3) “Hiring\nthe Lobbyist’s Girlfriend to the Congressional Staff.”\nJA494–95. The second subheading, “The Pursuit of\nAnother Executive Branch Position,” describes the\narrangement of the Kirk meeting. Quite clearly, then, this\nthree-part structure demonstrates that setting up the Kirk\nmeeting was one of three distinct categories of official acts\nalleged by the Government.\n\n Although there is some support for the\nGovernment’s argument that evidence of the Kirk meeting\nwas presented at trial only to establish the extent of\nVederman’s interest in becoming an ambassador, JA827,\n852–53 (mentioning the Kirk meeting in close proximity\nto references to Fattah’s attempts to secure Vederman an\nambassadorship), it is undermined by language in the\nredacted indictment itself, and by the way in which the\nGovernment presented its case at trial as a “pattern” of\nconnected acts.\n\n 77\n\f The redacted indictment, for example, refers to the\nKirk meeting as “The Pursuit of Another Executive\nBranch Position.” JA495 (emphasis added). The use of the\nword “Another” strongly suggests that evidence about the\nKirk meeting was not merely evidence of Fattah’s attempt\nto secure Vederman an ambassadorship, but was also\nevidence of a separate and distinct attempt to secure\nVederman a position on a federal trade-related\ncommission. The redacted indictment also notes that “[i]n\nor around May 2011, with little progress made on securing\nan ambassadorship for VEDERMAN, FATTAH turned\ntowards obtaining for VEDERMAN an appointment in the\nExecutive Branch to a federal trade commission.” Id.\n(emphasis added). The words “turned towards,” taken\nliterally, clearly convey that arranging the Kirk meeting\nwas presented as distinct from Fattah’s efforts to secure\nVederman an ambassadorship.\n\n The District Court denied Fattah and Vederman a\nnew trial on Counts 17 and 18, referring to evidence of the\nKirk meeting as “de minimis” and noting that “Kirk’s\ntestimony during this lengthy trial lasted a mere sixteen\nminutes.” JA97 n.14. In the District Court’s view,\nevidence of the Kirk meeting “played no role in the\noutcome” of the case. Id. Considering the record in light\nof McDonnell, we are not so sure.\n\n Although it is possible that evidence of the Kirk\nmeeting played a minor role at trial when compared to the\nother acts on which the Government presented evidence,\n\n 78\n\fthe redacted indictment suggests that the Kirk meeting was\na significant part of the Government’s case. The\nindictment dedicates five paragraphs to describing the\nKirk meeting, but just three paragraphs to describing the\nhiring of Vederman’s girlfriend—a hiring that, as we\nexplain below, is clearly an official act. JA495–96. While\nneither the number of minutes used at trial nor the number\nof paragraphs contained in an indictment is a dispositive\nunit of measurement for determining the significance of\nevidence, we conclude that the District Court’s erroneous\njury instructions pertaining to the Kirk meeting were not\nharmless.\n We conclude, in accordance with McDonnell, that\nFattah’s arranging a meeting between Vederman and the\nU.S. Trade Representative was not itself an official act.\nBecause the jury may have convicted Fattah for conduct\nthat is not unlawful, we cannot conclude that the error in\nthe jury instruction was harmless beyond a reasonable\ndoubt, and we must vacate and remand the convictions of\nFattah and Vederman as to Counts 16, 17, 18, 22 and 23.\n\n C. Fattah’s Efforts to Secure Vederman an\n Ambassadorship\n The nature of Fattah’s efforts to secure Vederman\nan ambassadorship is less clear, and presents a closer\nquestion than the Kirk meeting. We ultimately conclude\nthat the question warrants remand so that it may be\nanswered by a properly instructed jury. On remand, the\njury must decide whether Fattah’s conduct constituted a\n 79\n\f“decision” or “action” under Step 2 of the McDonnell\nanalysis.\n At the outset, it is clear to us that, under Steps 1(A)\nand 1(B), a formal appointment of Vederman as an\nambassador would qualify as a “matter” that “may at any\ntime be pending” before a public official. The formal\nappointment of a particular person (Vederman), to a\nspecific position (an ambassadorship), constitutes a matter\nthat is sufficiently focused and concrete. The formal\nappointment of an ambassador is a matter that is “pending”\nbefore the President—the constitutional actor charged\nwith nominating ambassadors—as well Senators, who are\ncharged with confirming the President’s ambassadorial\nnominations. U.S. Const. art. II § 2 (“[H]e shall nominate,\nand by and with the Advice and Consent of the Senate,\nshall appoint Ambassadors . . . .”). It is beyond cavil that\nthe formal appointment of an ambassador satisfies both\nsub-components of McDonnell’s Step 1.\n Turning to Step 2, we consider whether Fattah’s\nefforts to secure Vederman an ambassadorship qualify as\nmaking a “decision” or taking “an action” on the identified\n“matter” of appointment. McDonnell, 136 S. Ct. at 2368.\nAlthough those efforts—three emails, two letters, and one\nphone call—do not themselves qualify as a “question,\nmatter, cause, suit, proceeding, or controversy” under\nMcDonnell’s Step 1, they may nonetheless qualify as the\nmaking of a “decision” or taking “an action” on the\nidentified matter of appointment. Id.\n\n 80\n\f McDonnell’s Step 2 requires us to determine\nwhether Fattah’s efforts qualify as permissible attempts to\n“express[] support,” or impermissible attempts “to\npressure or advise another official on a pending matter.”\nId. at 2371. At trial, the jury was not instructed that they\nhad to place Fattah’s efforts on one side or the other of this\ndivide. The jury might even have thought they were\npermitted to find Fattah’s efforts—three emails, two\nletters, and one phone call—to themselves be official acts,\nrather than a “decision” or “action” on the properly\nidentified matter of appointment. Such a determination\nwould have been contrary to the dictates of McDonnell.\n Faced with such uncertainty, we cannot assume the\njury verdict was proper. Although the jury might not have\nconcluded that Fattah’s efforts were themselves official\nacts, and although the jury might not have concluded that\nthose efforts crossed the line into impermissible attempts\n“to pressure or advise,” we are unable to conclude that the\njury necessarily did so. Nor can we, on the cold record\nbefore us, determine whether Fattah’s efforts to secure\nVederman an ambassadorship crossed the line.\nDetermining, for example, just how forceful a strongly\nworded letter of recommendation must be before it\nbecomes impermissible “pressure or advice” is a fact-\nintensive inquiry that falls within the domain of a properly\ninstructed jury. Should the Government elect to retry these\ncounts after remand, the finder of fact will need to decide\nwhether Fattah’s efforts constituted permissible attempts\nto “express[] support,” or impermissible attempts “to\n 81\n\fpressure or advise another official on a pending matter.”\nId.\n\n D. The Zionts Hiring\n The third group of acts charged in the Fattah–\nVederman scheme involves Fattah’s decision to hire\nVederman’s girlfriend, Alexandra Zionts, as a\ncongressional staffer. We conclude that the hiring was an\nofficial act. A brief analysis of McDonnell’s two steps\nsuffices to show why this is so.\n Here, under McDonnell’s Step 1(A), the relevant\n“matter” is the decision to hire Zionts. Step 1(B) of the\nanalysis is satisfied because the hiring decision was\n“pending” before Fattah himself. And that hiring was\n“focused and concrete,” “within the specific duties of an\nofficial’s position—the function conferred by the\nauthority of his office.” Id. at 2369. Finally, McDonnell’s\nStep 2 requires that the “Government . . . prove that the\npublic official made a decision or took an action ‘on’ [the\nidentified] question, matter, cause, suit, proceeding, or\ncontroversy, or agreed to do so.” Id. at 2368. Fattah’s\ndecision to hire Zionts clearly satisfies that requirement.\nWe therefore conclude that the hiring of Zionts was an\nofficial act under McDonnell.\n\n Vederman concedes that the Zionts hiring was an\nofficial act. Oral Argument Transcript at 5–6. Fattah, for\nhis part, maintains that “hiring someone for a routine, part-\ntime, short-term position falls well outside [the] definition\n 82\n\f[of ‘official act’] and is nothing like a lawsuit, agency\ndetermination, or committee hearing, even if each shares\nthe happenstance that federal funds will be used.” Fattah\nReply Br. 25.\n\n Fattah’s argument lacks traction. Official acts need\nnot be momentous decisions—or even notable ones.\nJudges, for example, make “routine” evidentiary rulings\nevery day, and yet it is beyond question that those rulings\nare official acts. In the realm of official acts, it is of no\nmoment that Zionts provided only “part-time, short term”\nlabor. When a public official hires an employee to work in\nhis government office, he has engaged in an official act.\n * * *\n If we could conclude that the Zionts hiring was the\nonly category of actions that the jury relied on when it\nfound that Fattah performed an official act under Counts\n16–18 and 22–23, remand would not be necessary. But, as\nwe have explained, we cannot rule out that the jury\nerroneously convicted Fattah and Vederman based on\nother actions that were not official acts under\nMcDonnell.13\n\n\n13\n More specifically, the incomplete, and therefore\nerroneous, instructions could have led the jury to commit\nat least one of three mistakes. First, the jury could have\nimproperly convicted Vederman and Fattah based on the\nKirk meeting alone, or misunderstood the Kirk meeting to\n 83\n\f The Government argues that because the Zionts\nhiring was an official act, the effect of the erroneous jury\ninstructions could be no more than harmless. The jury’s\nverdict, the Government contends, permits us to deduce\nthat the jury necessarily concluded the Zionts hiring was\nan official act, and that this conclusion alone supported\nFattah’s and Vederman’s convictions as to Counts 16–18\nand 22–23—regardless of whether the jury erroneously\nfound any unofficial acts to be official acts. We disagree.\n Fattah and Vederman objected to the definition of\n“official act” at trial. We thus apply the harmless error\nstandard of review. McDonnell, 136 S. Ct. at 2375. The\nGovernment argues that because the jury convicted Fattah\nand Vederman of illegally laundering the proceeds of a\n“scheme to commit bribery” under Count 23, the jury\nfound that the scheme must have encompassed only the\nZionts hiring. JA531.That would mean that the jury did not\nconclude that the “scheme to commit bribery” included\n\nbe a necessary component of an impermissible “pattern”\nof official acts. Second, the jury might have concluded that\nFattah’s efforts to secure Vederman an ambassadorship\nwere themselves official acts. Third, the jury might have\nconcluded that Fattah’s efforts to secure Vederman an\nambassadorship were merely attempts to “express[]\nsupport,” rather than to “exert pressure . . . or provide\nadvice,” but nonetheless erroneously concluded that those\nexpressions of support were official acts. McDonnell, 136\nS. Ct. at 2371.\n 84\n\fany acts that McDonnell now makes clear were unofficial.\nYet the redacted indictment, jury instructions, and the fact\nthat the Government presented its case under a “pattern”\ntheory at trial compel us to reject the Government’s\nargument.\n\n The very first sentence under Count 23 of the\nredacted indictment incorporates all three categories of\n“Overt Acts” contained within paragraphs “58 through 95\nof Count One.” 14 All three of these categories fall under a\ngeneral heading within the redacted indictment titled “The\nBribery and Fraud Scheme [redacted].” JA494. The jury\nhad before it instructions for Count 23 which referred to\n“the alleged bribery scheme involving an $18,000\npayment,” JA448 (emphasis added), and the redacted\nindictment which referred to “a scheme to commit\nbribery,” JA531 (emphasis added). The parallel language\ncould well lead a rational jury to conclude that the relevant\n“scheme” included all three categories of acts listed under\nthe general heading: “The Bribery and Fraud Scheme\n[redacted].” JA494 (emphasis added).\n\n\n\n14\n JA531. Paragraphs 58 through 95 of Count 1 refer to the\nthree categories of allegedly official acts discussed above:\n(1) “The Pursuit of an Ambassadorship,” (2) “The Pursuit\nof Another Executive Branch Position,” and (3) the\n“Hiring of the Lobbyist’s Girlfriend to the Congressional\nStaff.” JA494–95.\n 85\n\f Like the redacted indictment and jury instructions,\nthe Government’s trial arguments referred to patterns and\na course of conduct, and stressed that the jury need not\nconnect specific payments to particular official acts. In its\nclosing argument to the jury, the Government stated that\nthe alleged “scheme took place over a period of several\nyears. Over and over again you’re going to see the same\npattern.” JA5383 (emphasis added). Then, in its rebuttal\nargument, the Government went out of its way to\nexplicitly distinguish its “pattern” theory from an\nalternative theory that would have directly connected\nindividual payments to individual acts. As the prosecutor\nargued to the jury:\n Ms. Recker appears to argue that each thing\n of value must coincide with some specific\n official act, but that is not the law and that is\n not what Judge Bartle is going to instruct you.\n Instead what he will tell you is that the\n government is not required to prove that\n Vederman intended to influence Fattah to\n perform a set number of official acts in return\n for things of value so long as the evidence\n shows a course of conduct of giving things of\n value, things of value to Fattah in exchange\n for a pattern of official acts favorable to\n Vederman. In other words a stream of\n benefits. These for those, not this for that.\n\n\n\n 86\n\fJA5715–16 (emphases added). In closing to the jury, the\nGovernment made several other references to this\n“pattern” theory, 15 and the District Court referred to this\n“pattern” theory in its instructions to the jury. As Judge\nBartle instructed:\n\n [I]t is not necessary for the government to\n prove that a defendant intended to induce a\n public official to perform a number of official\n acts in return for things of value.\n So as long as the evidence shows a\n course of conduct of giving things of value to\n a public official in exchange for a pattern of\n official acts favorable to the giver.\n\nJA5833–34 (emphasis added). On appeal, the Government\nchanges course, asking us to assume that the jury ignored\nthese repeated references to a “pattern of official acts” and\n\n15\n See, e.g., JA5389 (“And the exchange of an official act\nfor a thing of value is called a bribe. There’s the pattern.\nFattah needs money, Vederman gets an official act.”); JA\n5393 (“That’s why you see the pattern over and over again.\nFattah needs money, Vederman gets an official act.”);\nJA5400 (“The same pattern we saw over and over again.\nFattah needs money, Vederman gets an official act.”);\nJA5409 (“[Y]ou know that these were bribes because of\nthe pattern you saw over and over and over again. Fattah\nneeds money, Vederman gets an official act, that makes\nthese things a bribe.”).\n 87\n\finstead considered the Zionts hiring and Vederman’s\n$18,000 payment to Fattah as an isolated quid pro quo.\nThis is an invitation to speculate, and we decline to do so.16\nThe jury began its deliberations accompanied by a copy of\nthe redacted indictment which alleged a pattern of official\nacts, consisting of any combination of three categories of\nacts: pursuing an ambassadorship, arranging the Kirk\nmeeting, and hiring Zionts. In light of the erroneous\ninstructions, and because only one category clearly\n\n16\n Providing some support to the Government’s ultimately\nunconvincing argument that the jury considered the Zionts\nhiring and $18,000 payment in isolation, we note that the\nredacted indictment does mention those two events side-\nby-side in paragraph 78 of the indictment’s Part V. JA497\n(“On January 13, 2012, VEDERMAN wired $18,000 to\nFATTAH, and six days later, on January 19, 2012,\nBOWSER emailed VEDERMAN’s girlfriend, A.Z.,\nwelcoming her as a new employee to FATTAH’s\nCongressional Staff.”). But although paragraph 78\nmentions the $18,000 wire transfer and the Zionts hiring\nin the same breath, paragraph 78 does not instruct the jury\nto connect these two events apart from the rest of the\nevidence presented at trial. In light of the other instructions\nand arguments indicating that the jury should not consider\nthe Zionts hiring in isolation, but instead should consider\nthe hiring as one part of a three-part scheme, paragraph 78\nis not sufficient to avoid a reversal and remand on the\nconvictions of Fattah and Vederman as to Counts 16–18\nand 22–23.\n 88\n\fqualifies as an “official act,” the jury’s deliberations were\nfraught with the potential for McDonnell error. We will\nvacate the convictions of Fattah and Vederman as to\nCounts 16, 17, 18, 22, and 23, and remand to the District\nCourt.\n\nE. Vederman’s Sufficiency Challenge to Counts 16–18\n and 22–23\n Vederman argues that there is insufficient evidence\nto support a conviction, even if a jury were properly\ninstructed under McDonnell. Specifically, Vederman\nargues that there is insufficient evidence to convict him\nand Fattah, after remand, on Counts 16–18 and 22–23\nbecause “[a]t least seven of the eight alleged ‘official acts’\nwere, as a matter of law, not official at all.” Vederman Br.\n35. As to the single act that Vederman implicitly concedes\nto be an official act—the Zionts hiring—Vederman argues\nthat “[t]he only thing that even arguably associates” the\nZionts hiring with Vederman was its timing in relation to\nVederman’s sham purchase of the Fattahs’ Porsche. Id.\nAccording to Vederman, “the undisputed chronology\nprecludes any inference that Vederman conferred this\nbenefit on his friend as an illegal bribe.” Id. (emphasis\nomitted). Vederman is wrong. Sufficient evidence was\nproduced at trial to have allowed a properly-instructed jury\nto convict Fattah and Vederman of Counts 16–18 and 22–\n23.\n To begin with, even if the Zionts hiring had been the\nsole official act to survive this Court’s interpretation of\n 89\n\fMcDonnell, there would still be sufficient evidence to\nconvict Fattah and Vederman. Zionts did not receive\nwritten notice of her official hiring until six days after the\nsham Porsche purchase. Moreover, the jury would not be\nrestricted to considering the chronology of the sham\npurchase alone. It would be free to consider Vederman’s\nentire course of conduct. Under the general heading\n“VEDERMAN’S Payments and Things of Value to\nFATTAH,” the redacted indictment not only refers to the\n$18,000 wire transaction from Vederman to Fattah as part\nof the sham Porsche purchase, but also to Vederman’s\n$3,000 payment for the college tuition of Simone Muller,\nFattah’s live-in au pair, as well as thousands of dollars in\npayments made by Vederman for Chip Fattah’s college\ntuition. JA496–97.\n And the Zionts hiring is not the only act to survive\nour application of McDonnell. As we explained, a jury\ncould find that Fattah’s efforts to secure Vederman an\nambassadorship—three emails, two letters, and a phone\ncall—were an impermissible attempt to “pressure or\nadvise” President Obama, Senator Casey, or both men.17\n\n17\n Although Fattah’s efforts to secure Vederman an\nambassadorship present a jury question that is not for us to\nanswer on appeal, we note that not one of these efforts\nalone could qualify as an official act itself. See McDonnell,\n136 S. Ct. at 2372 (“Setting up a meeting, talking to\nanother official, or organizing an event (or agreeing to do\nso)—without more—does not fit that definition of ‘official\n 90\n\fThis means that a properly instructed jury on remand,\npresented with evidence of Fattah’s efforts to secure an\nambassadorship for Vederman and evidence of the Zionts\nhiring, could find more than a single official act.\n\n F. Blue Guardians\n In addition to the charges arising from his dealings\nwith Vederman, Fattah was charged in Count 3 with\n\n\nact.’ ”). The relevant question for a jury to consider on\nremand, then, is whether these actions constituted “a\n‘decision or action’ on a different question or matter”—to\nwit, the formal appointment of an ambassador. Id. at 2369\n(emphasis omitted).\n Even though the emails, letters, and phone call are\nnot, individually, official acts, it will be for a jury to decide\nif Fattah’s efforts to secure an ambassadorship for\nVederman crossed the line from permissible “support” to\nimpermissible “pressure or advice.” While we express\ndoubt that some of Fattah’s efforts concerning the\nambassadorship are, when considered in isolation, enough\nto cross that line, a properly instructed jury considering all\nof the facts in context might nonetheless conclude that\nother efforts—such as a hand-delivered letter to the\nPresident of the United States—indeed crossed that line.\nFurther, a jury might find that in the aggregate, three\nemails, two letters, and a phone call crossed the line and\ntherefore constituted a “decision or action” on the\nidentified matter of appointment.\n 91\n\fparticipating in a scheme with Lindenfeld to funnel money\nto a fraudulent nonprofit organization. In connection with\nthis scheme, Fattah was convicted of conspiring to commit\nhonest services fraud.\n\n Fattah owed Lindenfeld nearly $100,000 for work\nperformed on Fattah’s 2007 mayoral campaign. In lieu of\nrepayment, Fattah suggested that Lindenfeld create an\nentity, later named Blue Guardians, to which Fattah would\ndirect $15,000,000 in public funds by using his position as\na member of the House Committee on Appropriations.\nNothing in McDonnell requires us to upset Fattah’s\nconviction on Count 3.\n Step 1(A) of our McDonnell analysis requires the\nGovernment to “identify a ‘question, matter, cause, suit,\nproceeding or controversy.’ ” 136 S. Ct. at 2368. Here, the\n“matter” is the appropriation of millions of dollars in\npublic funds. See Repak, 852 F.3d at 253–54 (holding the\nawarding of redevelopment funds to be an official act). In\nparticular, it was Fattah’s promise to perform this official\nact that was unlawful. As McDonnell makes clear:\n\n [A] public official is not required to actually\n make a decision or take an action on a\n “question, matter, cause, suit, proceeding or\n controversy”; it is enough that the official\n agree to do so. The agreement need not be\n explicit, and the public official need not\n specify the means that he will use to perform\n his end of the bargain.\n 92\n\f136 S. Ct. at 2370–71 (internal citations omitted). That\nFattah took steps to actually carry out his promise (e.g., by\ndrafting and sending a formal appropriations request on\nofficial congressional letterhead) is evidence of his illegal\npromise. See id. at 2371.\n\n Step 1(B) requires the Government to establish that\nthe “ ‘question, matter, cause, suit, proceeding or\ncontroversy’ . . . ‘may at any time be pending’ or ‘may by\nlaw be brought’ before a public official.” McDonnell, 136\nS. Ct. at 2368. Appropriating public funds was not only a\nmatter that was pending before Fattah as a member of the\nAppropriations Committee, it was also a matter that was\npending before the Chairman and Ranking Member of an\nAppropriations Subcommittee to whom Fattah ultimately\nsent a formal written request. See id. at 2369 (“[T]he\nmatter may be pending either before the public official\nwho is performing the official act, or before another public\nofficial.”). Appropriating millions of dollars in response to\nthe Blue Guardians request is “focused and concrete,” and\n“the kind of thing that can be put on an agenda, tracked for\nprogress, and then checked off as complete.” Id.\n\n Given Fattah’s membership on the Appropriations\nCommittee, this was “something within the specific duties\nof an official’s position—the function conferred by the\nauthority of his office.” Id. Even if we were to assume,\nagainst all reason, that an appropriation is not “something\nwithin the specific duties” of either Fattah or the Chairman\nor Ranking Member of an Appropriations Subcommittee,\n\n 93\n\fFattah’s formal request for an appropriation was\nsomething that Fattah had the authority to do. Like the\nExecutive Director in Repak, who lacked authority himself\nto award redevelopment funds but could request such\nfunds from the Board, Fattah used his position as a\nCongressman to formally request appropriations for the\nBlue Guardians. 852 F.3d at 254 (“Repak had the power\nto, and indeed did, make recommendations to the\n[redevelopment authority.\n Step 2 of McDonnell requires the Government to\n“prove that the public official made a decision or took an\naction ‘on’ that question, matter, cause, suit, proceeding,\nor controversy, or agreed to do so.” 136 S. Ct. at 2368\n(emphasis added). Here, Fattah agreed to request an\nappropriation for a bogus purpose. Unlike Fattah’s letters,\nemails, and phone call seeking an ambassadorship for\nVederman, there is no potential for the jury to have made\na mistake when it found Fattah’s Blue Guardians promise\nunlawful.\n Fattah argues that the Government presented “[n]o\nevidence . . . that would have allowed [the jury] to\nconclude that [he] made a decision or took an action, or\ncould have done so, on the question whether Blue\nGuardians would receive a $15 million federal grant.”\nFattah Br. 46. This argument misses the point. It was\nFattah’s agreement to engage in the official act of formally\nrequesting the appropriation that was illegal. See\nMcDonnell, 136 S. Ct. at 2371.\n\n 94\n\f Lindenfeld’s trial testimony provided sufficient\nevidence of Fattah’s illegal agreement. JA1694–96, 1954.\nFattah’s letter provided additional evidence from which\nthe jury could have concluded that Fattah illegally agreed\nto perform an official act. 18 In short, the agreement itself\nwas illegal, and the Government provided sufficient\nevidence for the jury to conclude that the illegal agreement\ntook place.\n\n The Government’s evidence in support of the Blue\nGuardians scheme meets the requirements of McDonnell,\nand the Count 3 verdict will stand.\n\n V. Sufficiency of the Evidence for the RICO\n Conspiracy Conviction\n The jury found Fattah, Vederman, Brand, and\nNicholas guilty of the RICO conspiracy charged in Count\n1 of the indictment, but acquitted Bowser. Vederman filed\na post-verdict motion, and the District Court overturned\nhis RICO conspiracy conviction.\n\n\n\n18\n Despite Fattah’s protestation to the contrary, there is\nevidence that Fattah took steps to carry out his official act.\nJA6432–33 (Letter from Congressman Fattah to House\nAppropriations Subcommittee members “request[ing]\nfunding and support for the following projects and\nprograms of critical importance,” including $3,000,000\nfor “Blue Guardians”).\n 95\n\f On appeal, Fattah, Brand, and Nicholas challenge\nthe sufficiency of the evidence supporting their RICO\nconspiracy convictions. We “review[] the sufficiency of\nthe evidence in the light most favorable to the government\nand must credit all available inferences in favor of the\ngovernment.” United States v. Riddick, 156 F.3d 505, 509\n(3d Cir. 1998). If a rational juror could have found the\nelements of the crime beyond a reasonable doubt, we must\nsustain the verdict. United States v. Cartwright, 359 F.3d\n281, 286 (3d Cir. 2004), abrogated on other grounds by\nUnited States v. Caraballo-Rodriguez, 726 F.3d 418 (3d\nCir. 2013) (en banc).\n The indictment charged a RICO conspiracy in\nviolation of 18 U.S.C. § 1962(d), which makes it\n“unlawful for any person to conspire to violate” § 1962(c).\nSection 1962(c) provides:\n It shall be unlawful for any person . . .\n associated with any enterprise engaged in, or\n the activities of which affect, interstate . . .\n commerce, to conduct or participate, directly\n or indirectly, in the conduct of such\n enterprise’s affairs through a pattern of\n racketeering activity . . . .\n\n18 U.S.C. § 1962(c).\n\n In Salinas v. United States, 522 U.S. 52 (1997), the\ndefendant was convicted of a § 1962(d) RICO conspiracy,\nbut a jury acquitted him of the substantive RICO offense\n 96\n\funder § 1962(c). Id. at 55. The Supreme Court rejected\nSalinas’s contention that his conviction had to be set aside\nbecause he had neither committed nor agreed to commit\nthe two predicate acts required for the § 1962(c) offense.\nId. at 66. The Court declared that liability for a RICO\nconspiracy under § 1962(d), “unlike the general\nconspiracy provision applicable to federal crimes,” does\nnot require proof of an overt act. Id. at 63. A conspiracy\nmay be found, the Court explained, “even if a conspirator\ndoes not agree to commit or facilitate each and every part\nof the substantive offense. The partners in the criminal\nplan must agree to pursue the same criminal objective and\nmay divide up the work, yet each is responsible for the acts\nof each other.” Id. at 63–64 (citations omitted). This means\nthat, if a plan “calls for some conspirators to perpetrate the\ncrime and others to provide support, the supporters are as\nguilty as the perpetrators.” Id. at 64. Thus, opting into and\nparticipating in a conspiracy may result in criminal\nliability for the acts of one’s co-conspirators. Smith v.\nBerg, 247 F.3d 532, 537 (3d Cir. 2001).\n Accordingly, liability for a RICO conspiracy may\nbe found where the conspirator intended to “further an\nendeavor which, if completed, would satisfy all of the\nelements of a substantive criminal offense, but it suffices\nthat he adopt the goal of furthering or facilitating the\ncriminal endeavor.” Salinas, 522 U.S. at 65. Because the\nsubstantive criminal offense here was conducting a\n§ 1962(c) enterprise, the government had to prove:\n\n 97\n\f (1) that two or more persons agreed to\n conduct or to participate, directly or\n indirectly, in the conduct of an enterprise’s\n affairs through a pattern of racketeering\n activity; (2) that the defendant was a party to\n or member of that agreement; and (3) that the\n defendant joined the agreement or conspiracy\n knowing of its objective to conduct or\n participate, directly or indirectly, in the\n conduct of an enterprise’s affairs through a\n pattern of racketeering activity.\n\nUnited States v. John-Baptiste, 747 F.3d 186, 207 (3d Cir.\n2014).\n In United States v. Turkette, 452 U.S. 576 (1981),\nthe Supreme Court instructed that an enterprise is a “group\nof persons associated together for a common purpose of\nengaging in a course of conduct.” Id. at 583. The\ngovernment can prove an enterprise “by evidence of an\nongoing organization, formal or informal, and by evidence\nthat the various associates function as a continuing unit.”\nId. In Boyle v. United States, 556 U.S. 938 (2009), the\nSupreme Court established that an “association-in-fact\nenterprise must have at least three structural features: a\npurpose, relationships among those associated with the\nenterprise, and longevity sufficient to permit these\nassociates to pursue the enterprise’s purpose.” Id. at 946.\nThe structure necessary for a § 1962(c) enterprise is not\ncomplex. Boyle explained that an enterprise\n\n 98\n\f need not have a hierarchical structure or a\n “chain of command”; decisions may be made\n on an ad hoc basis and by any number of\n methods—by majority vote, consensus, a\n show of strength, etc. Members of the group\n need not have fixed roles; different members\n may perform different roles at different\n times. The group need not have a name,\n regular meetings, dues, [or] established rules\n and regulations . . . .While the group must\n function as a continuing unit and remain in\n existence long enough to pursue a course of\n conduct, nothing in RICO exempts an\n enterprise whose associates engage in spurts\n of activity punctuated by periods of\n quiescence.\n\nId. at 948.\n\n Another element of a substantive § 1962(c) RICO\nenterprise is that the enterprise must conduct its affairs\nthrough a pattern of racketeering activity. Section 1961\ndefines racketeering activity to include various criminal\noffenses, including wire fraud, 18 U.S.C. § 1344, and\nobstruction of justice, 18 U.S.C. § 1511. See 18 U.S.C.\n§ 1961(1). A pattern of such activity “requires at least two\nacts of racketeering activity.” Id. § 1961(5). The\nracketeering predicates may establish a pattern if they\n“related and . . . amounted to, or threatened the likelihood\n\n\n 99\n\fof, continued criminal activity.” H.J. Inc. v. Nw. Bell Tel.\nCo., 492 U.S. 229, 237 (1989).\n Here, the District Court denied the post-trial\nsufficiency arguments raised by Fattah, Brand, and\nNicholas. It reasoned:\n For a RICO conspiracy to exist, the\n conspirators must agree to participate in an\n enterprise with a unity of purpose as well as\n relationships among those involved. The\n evidence demonstrates that an agreement\n among Fattah, Brand, Nicholas, Lindenfeld,\n and Naylor existed for the overall purpose of\n maintaining and enhancing Fattah as a\n political figure and of preventing his standing\n from being weakened by the failure to be able\n to pay or write down his campaign debts.\n These five persons agreed to work together as\n a continuing unit, albeit with different roles.\n The Government established that\n Fattah, Brand, and Nicholas conspired along\n with Naylor and Lindenfeld to conceal and\n repay the 2007 illegal $1,000,000 loan to the\n Fattah for Mayor campaign.\n\nJA128–29. The District Court further determined that\n [w]hile each member may not have been\n involved in every aspect of the enterprise, its\n activities were sufficiently structured and\n 100\n\f coordinated to achieve the purpose of\n maintaining and enhancing Fattah’s political\n standing and of preventing him from being\n weakened politically because of his\n campaign debts.\n A RICO conspiracy also requires an\n agreement to participate in an enterprise with\n longevity sufficient to pursue its purpose.\n This was established. In May 2007 the illegal\n loan was obtained and continued through its\n repayment in January 2008 and into at least\n 2014 when the last campaign report reducing\n a fake campaign debt to Naylor’s consulting\n firm was filed by Fattah.\nJA131.\n\n The defendants argue that the evidence is\ninsufficient to show either an enterprise for purposes of\n§ 1962(c) or an agreement as required for a § 1962(d)\nconspiracy. We disagree, and conclude that the District\nCourt’s analysis is on the mark.\n\n We begin by considering whether there was an\nagreement. The evidence showed that Fattah knew each\nmember involved in the scheme to conceal the unlawful\ncampaign loan. When Lindenfeld learned of the $1 million\nloan, he informed Fattah that it exceeded campaign\nfinance limits. In short, the transaction was unlawful, and\nthe two knew it. The transaction nonetheless went\nforward, disguised as a loan, with Lindenfeld executing\n 101\n\fthe promissory note as Strategies’ officer and obligating\nStrategies to repay Lord $1 million. The concealment\nefforts continued as Lindenfeld funneled a substantial\nportion of the loan proceeds to Naylor for get-out-the-vote\nefforts. After the losing campaign, Lindenfeld spoke with\nFattah and Naylor about accounting for the funds that had\nbeen spent. They decided not to include the amounts in the\nFFM campaign reports. Fattah instructed Naylor to\nprepare a fictitious invoice, and Naylor complied. The\nFFM campaign reports filed from 2008 to 2014 disclosed\nnothing about the unlawful $1 million loan. Instead, they\nfalsely showed that Naylor’s consulting firm made yearly\nin-kind contributions of $20,000 in debt forgiveness, when\nin reality there was no debt to forgive.\n As Lindenfeld fretted over repaying the $600,000\nbalance of the Lord loan, Naylor assured him that Fattah\nhad promised to take care of the repayment. And the\nevidence supports an inference that Fattah recruited both\nNicholas and Brand in doing so. As EAA’s director,\nNicholas could fund the repayment. Brand, through his\ncompany, Solutions, acted as the middleman: he received\nthe payment from EAA pursuant to a fictitious contract,\nand then forwarded the balance due to Strategies pursuant\nto yet another fictitious contract. Nicholas and Brand\ncontinued in the spring and summer of 2008 to hide the\nfictitious agreement and the $600,000 payment to\nLindenfeld to satisfy the Lord loan.\n\n\n\n 102\n\f In short, this evidence shows that Fattah,\nLindenfeld, Naylor, Brand, and Nicholas all agreed to\nparticipate in Fattah’s plan to conceal the unlawful\ncampaign loan to maintain his political stature. Nicholas\nand Brand claim that they had no knowledge of the false\ncampaign reporting aspect of the plan. But as Salinas\ninstructs, conspirators need not “agree to commit or\nfacilitate each and every part of the” conspiracy. 522 U.S.\nat 63. Rather, they “must agree to pursue the same criminal\nobjective and may divide up the work, yet each [be]\nresponsible for the acts of each other.” Id. at 63–64. Thus,\na conspirator may agree to “facilitate only some of the acts\nleading to the substantive offense” yet still be criminally\nliable. Id. at 65.\n The evidence showed that a substantial amount of\nmoney was needed to repay Lord, and that the source of\nthe repayment was EAA, a non-profit organization whose\nfunds could be spent only for purposes consistent with the\nterms of the grants it received. It also showed that Nicholas\nwas presented with a sham contract to legitimize the\nEAA–Solutions transaction. We conclude that the\nevidence is sufficient to support an inference that Nicholas\nknew at the start that the plan was unlawful. Yet she still\nagreed to provide the requisite funds and to play a role in\nconcealing the illegal campaign loan so that Fattah could\nmaintain his political stature.\n\n As to Brand, even if he did not know that false\ncampaign reports were being filed, the evidence is\n\n 103\n\fsufficient to show he played a key role in the enterprise.\nFrom the outset, Brand worked to disguise the repayment\nof the Lord loan as the consideration in a sham contract\nbetween EAA and Solutions. He then arranged for the\ntransfer of funds to Strategies in satisfaction of a\ncontractual term in another purported business agreement\nbetween Solutions and Strategies. The evidence reveals\nthat Brand was the point man in the effort to meet the\nJanuary 31, 2008 deadline to repay the Lord loan, and it\namply shows that Brand also agreed to participate in the\nplan to hide the illegal campaign loan and its repayment to\nbenefit Fattah politically.\n Fattah, Brand, and Nicholas attack their RICO\nconspiracy convictions on another front. They argue that\nthose verdicts should be set aside because the evidence\nfails to show that the various schemes alleged in the\nindictment as part of the RICO conspiracy are connected.\nThe RICO count, they assert, charges a hub-and-spoke\nconspiracy that is unconnected by a rim. In their view,\nFattah is the hub, and the spokes consist of a series of\nindependent schemes: the Vederman bribery scheme, the\npayment of the outstanding tuition debt of Fattah’s son\nChip, the Blue Guardians plan, and the repayment of the\nillegal Lord loan to maintain Fattah’s political stature.\nThey argue that, without a unifying rim, their actions\ncannot constitute an enterprise. Again, we disagree.\n\n In In re Insurance Brokerage Antitrust Litigation,\n618 F.3d 300 (3d Cir. 2010), we concluded, in analyzing\n\n 104\n\fone of plaintiffs’ RICO claims, that the alleged hub-and-\nspoke enterprise—comprised of broker hubs and insurer\nspokes—could not withstand a motion to dismiss because\nit did not have a unifying rim. Id. at 374. We explained\nthat the allegations did “not plausibly imply concerted\naction—as opposed to merely parallel conduct—by the\ninsurers, and therefore cannot provide a ‘rim’ enclosing\nthe ‘spokes’ of these alleged ‘hub-and-spoke’\nenterprises.” Id. Thus, the allegations did not “adequately\nplead an association-in-fact enterprise” because the hub-\nand-spoke conspiracy failed to “function as a unit.” Id.\n\n That is not the case here. The evidence showed that\nFattah, Brand, and Nicholas agreed to conceal the illegal\nLord loan. Each acted for the common purpose of\nfurthering Fattah’s political interests. In short, they\nengaged in concerted activity and functioned as a unit. The\njury convicted Fattah, Brand, and Nicholas of the RICO\nconspiracy based on the racketeering activity of wire fraud\nand obstruction of justice to conceal the unlawful\ntransaction. Because the evidence shows that Fattah,\nLindenfeld, Naylor, Brand, and Nicholas agreed to protect\nFattah’s political status by acting to maintain the secrecy\nof the unlawful Lord loan, the alleged lack of a unifying\n“rim” is not fatal to this RICO enterprise. What matters in\nanalyzing the structure of this enterprise is that it\nfunctioned as a unit. Boyle, 556 U.S. at 945; In re Ins.\nBrokerage Antitrust Litig., 618 F.3d at 374. That “basic\nrequirement” was met. Id.\n\n 105\n\f We turn next to the contention that the evidence\nfails to establish other components of an enterprise. We\nconclude that much of the evidence supporting the\nexistence of an agreement also shows that there was an\nassociation-in-fact enterprise.\n\n Boyle made clear that an association-in-fact\nenterprise must have “a purpose, relationships among\nthose associated with the enterprise, and longevity\nsufficient to permit these associates to pursue the\nenterprise’s purpose.” 556 U.S. at 946. The purpose, as we\nhave repeatedly observed, was to maintain and preserve\nFattah’s political stature by concealing the illegal loan and\nits repayment. Though informal, there were relationships\namong those associated with the enterprise. Fattah was at\nthe center of this association and he directed its activity.\nHe knew each of the association’s members, and the\nmembers knew each other (except, perhaps, for Nicholas,\nwho may not have known Lindenfeld).19\n\n\n19\n Nicholas’s lack of familiarity with Lindenfeld does not\nundermine her membership in this association-in-fact\nenterprise. We have previously explained that “[i]t is well-\nestablished that one conspirator need not know the\nidentities of all his co-conspirators, nor be aware of all the\ndetails of the conspiracy in order to be found to have\nagreed to participate in it.” United States v. Riccobene, 709\nF.2d 214, 225 (3d Cir. 1983), abrogated on other grounds\nby Griffin v. United States, 502 U.S. 46 (1991).\n 106\n\f The Government also adduced sufficient proof of\nthe longevity component required for an enterprise. The\nscheme began in mid-2007, when Lord made the\ncampaign loan, directing the proceeds of the loan to\nStrategies. From the outset, Fattah, Lindenfeld, and Naylor\nall knew they needed to conceal this illegal transaction.\nThey began by fabricating an explanation for the source of\nthe funds they spent on election day. SLA created a fake\ninvoice for the campaign, showing a fictitious debt that\nNaylor could later forgive by fictitious in-kind\ncontributions existing only on Fattah’s campaign finance\nreports.\n The effort to disguise the Lord loan was not limited\nto filing false campaign reports. Nicholas and Brand, who\njoined the conspiracy a few months later than the other\nmembers, understood that they too had to make the\nfraudulent $600,000 payment by EAA to Solutions appear\nlegitimate. Nicholas and Brand tried to disguise the sham\ncontract as an ordinary transaction (even though it called\nfor a six-figure upfront payment simply to support\nSolutions’ various projects), and they succeeded in\nkeeping it out of the DOJ auditors’ view until August\n2008. The ruse continued as Solutions funneled the\n$600,000 payment to Strategies under the guise of another\nsham contract (which also required an upfront six-figure\npayment). The scheme then continued as Fattah submitted\nfalse FFM campaign reports from 2008 through 2014.\n\n\n\n 107\n\f Finally, we consider whether the enterprise\nconducted its affairs through a pattern of racketeering\nactivity, as required for a § 1962(c) enterprise. Wire fraud\nand obstruction of justice may constitute “racketeering\nactivity” under § 1961(1). As the Supreme Court\ninstructed in H.J. Inc., the “multiple predicates within a\nsingle scheme” must be related and “amount[] to, or\nthreaten[] the likelihood of, continued criminal activity.”\n492 U.S. at 237. Here, the amount of the illegal loan to be\nconcealed was substantial. The enterprise needed to write\noff the fictitious debt to Naylor’s consulting firm, and it\nwas urgent that both the EAA–Solutions contract and the\nSolutions–Strategies contract be legitimized. We conclude\nthe evidence was sufficient to establish that this enterprise\nconducted its affairs through a pattern of racketeering\nactivity and that the predicate acts of wire fraud and\nobstruction of justice were related. The racketeering\nactivity furthered the goals of maintaining the secrecy of\nthis $1 million illicit campaign loan and of preserving\nFattah’s political stature.\n Nicholas contends that the evidence fails to\nestablish a pattern of racketeering activity because the\nactions to which she agreed did not “extend[] over a\nsubstantial period of time” as H.J. Inc. requires. 492 U.S.\nat 242. That case indeed instructs that the continuity\nrequirement of a pattern is a “temporal concept,” and that\n“[p]redicate acts extending over a few weeks or months”\ndo not satisfy the continuity concept. Id. But the Supreme\nCourt explained that continuity may also be established by\n 108\n\fshowing that there is a “threat of continued racketeering\nactivity.” Id. Here, the course of fraudulent conduct\nundertaken to secure and to conceal the $1 million Lord\nloan consisted of the creation of sham debts, fictitious\ncontracts, and false accounting entries over the course of\nabout a year. But because Fattah needed to appear able to\nretire his campaign debt, the enterprise needed to continue\nfiling false campaign reports for several years, allowing\nthe annual $20,000 in-kind debt forgiveness contributions\nto appear to satisfy Naylor’s fake $193,000 invoice. That\nevidence was sufficient to establish the requisite threat of\ncontinued criminal activity. See H.J. Inc., 492 U.S. at 242–\n43.\n We conclude that the Government met its burden in\nproving that Fattah, Brand, and Nicholas 20 engaged in a\nRICO conspiracy in violation of § 1962(d).\n\n\n20\n Nicholas also asserts, in passing, that that her conviction\nunder § 1962(d) should be set aside because that statutory\nprovision is unconstitutionally vague as applied to her.\nAccording to Nicholas, a person of ordinary intelligence\nwould not know that her actions constituted an agreement\nto participate in a RICO enterprise. See United States v.\nPungitore, 910 F.2d 1084, 1104–05 (3d Cir. 1990). To the\ncontrary, a person of ordinary intelligence, who had been\nemployed by a prominent politician and then became the\nCEO of a nonprofit organization which that politician had\nfounded (and, to some extent, continued to direct), would\n 109\n\f VI. Variance from the Indictment and Sufficiency of\n the Evidence for Count 2\n Brand and Nicholas challenge their convictions for\nconspiracy to commit wire fraud by arguing that the\nGovernment’s evidence at trial impermissibly varied from\nthe indictment. Nicholas also challenges the sufficiency of\nthe evidence to support her conviction for conspiracy to\ncommit wire fraud. We address these contentions\ntogether. 21\n\n Count 2 of the indictment alleged a single\nconspiracy. JA277–79. Brand and Nicholas assert that the\nGovernment’s evidence at trial did not support the\nexistence of a single conspiracy but instead showed two\nindependent conspiracies, only one of which involved the\ntwo of them. According to Brand and Nicholas, the only\nconspiracy with which they were involved ended more\nthan five years before the Government charged them. That\nwould mean that all their conduct falls outside the five-\nyear limitations period for wire fraud conspiracy under 18\nU.S.C. § 3282.\n\n\nrealize that agreeing to participate with others in hiding an\nunlawful campaign loan of $1 million could constitute an\nunlawful RICO conspiracy.\n21\n In her briefing, Nicholas discusses variance in far less\ndetail than Brand, so we refer primarily to Brand’s\narguments. See Nicholas Br. 54–56. Her variance\narguments fail for the same reasons that Brand’s fail.\n 110\n\f “A conviction must be vacated when (1) there is a\nvariance between the indictment and the proof presented\nat trial and (2) the variance prejudices a substantial right\nof the defendant.” Kemp, 500 F.3d at 287 (quoting United\nStates v. Kelly, 892 F.2d 255, 258 (3d Cir. 1989)). We see\nno variance, and will affirm the District Court.\n A variance exists “if the indictment charges a single\nconspiracy while the evidence presented at trial proves\nonly the existence of multiple conspiracies.” Id. “We must\ndetermine ‘whether there was sufficient evidence from\nwhich the jury could have concluded that the government\nproved the single conspiracy alleged in the indictment.’ ”\nId. (quoting Kelly, 892 F.2d at 258). Viewing the record in\nthe light most favorable to the Government, we consider\nthree factors: (1) “whether there was a common goal\namong the conspirators”; (2) “whether the agreement\ncontemplated bringing to pass a continuous result that will\nnot continue without the continuous cooperation of the\nconspirators”; and (3) “the extent to which the participants\noverlap in the various dealings.” Id. (quoting Kelly, 892\nF.2d at 259).\n\n Brand argues that the Government failed to\nestablish a common goal among the conspirators. To\ndetermine whether the conspirators shared a common\ngoal, “we look to the underlying purpose of the alleged\ncriminal activity” in a fairly broad sense. United States v.\nRigas, 605 F.3d 194, 214 (3d Cir. 2010) (en banc). In\nRigas, we described the common goal of the defendants as\n\n 111\n\f“enriching [themselves] through the plunder of [their\ncorporate employer],” id., and we have similarly\narticulated the common goal in fairly general terms\nelsewhere. See United States v. Greenidge, 495 F.3d 85,\n93 (3d Cir. 2007) (“There was certainly evidence of a\ncommon goal among these co-conspirators: to make\nmoney by depositing stolen and altered corporate checks\ninto business accounts.”); Kelly, 892 F.2d at 259 (“[T]he\ncommon goal of all the participants was simply to make\nmoney selling ‘speed.’ ”). Importantly, a common goal\nmay exist even when “conspirators individually or in\ngroups perform different tasks in pursuing the common\ngoal,” and a single conspiracy may “attract[] different\nmembers at different times” or “involve[] different sub-\ngroups committing acts in furtherance of the overall plan.”\nUnited States v. Boyd, 595 F.2d 120, 123 (3d Cir. 1978).\n\n Here, the indictment described the purpose of the\nunified conspiracy in Count 2 at length:\n\n It was a purpose of the conspiracy to obtain\n an illegal campaign loan and to fraudulently\n repay that loan with hundreds of thousands of\n dollars of misappropriated charitable funds\n from Sallie Mae and federal grant funds from\n NASA which were intended for educational\n purposes.\n\n . . . . It was further a purpose of the\n conspiracy to present FATTAH to the public\n as a perennially viable candidate for public\n 112\n\f office who honored his obligations to his\n creditors and was able to retire his publicly\n reported campaign debts.\n . . . . It was further a purpose of the\n conspiracy to promote FATTAH’s political\n and financial goals through deception by\n concealing and protecting the conspirators’\n activities from detection and prosecution by\n law enforcement officials and the federal\n judiciary, as well as from exposure by the\n news media, through means that included\n obstruction of justice and the falsification of\n documents, including Campaign Finance\n Reports, false invoices, contracts, and other\n documents and records.\n\nJA277–78, ¶¶ 3–5.\n Brand characterizes the evidence at trial as\nestablishing two distinct conspiracies. The first he labels\nthe “diversion of funds scheme,” covering the\nmisappropriation of funds by Nicholas, Brand,\nLindenfeld, and Fattah to repay the Lord loan. Brand Br.\n34. Brand calls the second conspiracy the “CFR scheme,”\nin which Fattah and Naylor filed the false campaign\nfinance reports showing Naylor gradually forgiving a non-\nexistent debt. Id.\n Brand argues that the only goal of the CFR scheme\nwas to cover up how the funds from the illegal campaign\n 113\n\floan were spent, a goal he distinguishes from that of the\ndiversion of funds scheme, which he characterizes as a\nplan to cover up the repayment of the loan with stolen\nfunds. He also argues that the evidence does not establish\nhe was involved in, or even aware of, the false campaign\nfinance reports filed by Fattah. In Brand’s view, that\nnecessarily means the evidence showed two separate\nconspiracies.\n\n In considering these arguments, we begin by noting\nthat one conspiracy can involve multiple subsidiary\nschemes. Rigas, 605 F.3d at 214. It is true that the false\ncampaign finance reports, in the narrowest sense, had the\nspecific purpose of covering up how the illegal loan funds\nwere used during the election. But the false campaign\nfinance reports were also filed in furtherance of a broader\ngoal shared by the conspirators involved in repayment of\nthe Lord loan. They sought to promote Fattah’s political\nand financial goals by preserving his image as a viable\ncandidate and making him appear able to repay or\notherwise service his campaign debts without resorting to\nillegal means in doing so. The two subsidiary schemes\nworked in concert in furtherance of this overarching goal,\nand both were directed at covering up how the loan was\ntruly repaid. The “diversion of funds scheme” hid the\nillegal (but real) loan repayment through the use of fake\ncontracts; the “CFR scheme” showed the seemingly legal\n(but fake) loan forgiveness installments through the\ncreation of fake invoices and campaign finance reports.\nThe existence of two concealment schemes acting in\n 114\n\fconcert does not undermine the unity of the conspiracy of\nwhich they were both a part. We have no difficulty\nconcluding that the false campaign finance reports and the\nconcealed use of stolen funds to repay the Lord loan\noperated together in furtherance of a common goal.\n\n As for Brand’s argument that he was unaware of the\nfalse campaign finance reports and therefore could not be\na part of any conspiracy involving them, it is well-settled\nthat “each member of the charged conspiracy is liable for\nthe substantive crimes his coconspirators commit in\nfurtherance of the conspiracy even if he neither\nparticipates in his co-conspirators’ crimes nor has any\nknowledge of them.” United States v. Bailey, 840 F.3d 99,\n112 (3d Cir. 2016) (citing Pinkerton v. United States, 328\nU.S. 640 (1946)). The exceptions to that rule allow a\ndefendant to escape liability for a co-conspirator’s crime\nif: (1) “the substantive offense committed by one of the\nconspirators was not in fact done in furtherance of the\nconspiracy,” (2) “the substantive offense committed by\none of the conspirators ‘did not fall within the scope of the\nunlawful project,’ ” or (3) “the substantive offense\ncommitted by one of the conspirators ‘could not be\nreasonably foreseen as a necessary or natural consequence\nof the unlawful agreement.’ ” Id. (quoting Pinkerton, 328\nU.S. at 647–48). There was, as we have concluded, a unity\nof purpose between the co-conspirators to further Fattah’s\npolitical and financial goals by secretly obtaining and\nrepaying an illegal campaign loan with stolen funds. The\nfiling of false campaign reports does not fit within any of\n 115\n\fthe recognized exceptions to co-conspirator liability, as it\nwas in furtherance of the conspiracy’s shared goal, within\nthe scope of the agreement to conceal the loan, and\nforeseeable to Brand and Nicholas.\n\n Neither Brand nor Nicholas briefed the other two\nfactors we consider when determining whether the\nevidence impermissibly varied from the evidence,\n“whether the agreement contemplated bringing to pass a\ncontinuous result that will not continue without the\ncontinuous cooperation of the conspirators,” and “the\nextent to which the participants overlap in the various\ndealings.” Kemp, 500 F.3d at 287 (quoting Kelly, 892 F.2d\nat 258). The unified goal of promoting Fattah’s political\ncareer and maintaining secrecy surrounding the illegal\nloan and the misappropriated funds used to repay it\nrequired the continuous cooperation of the conspirators.\nIndeed, the efforts of several of them overlapped in every\naspect of the scheme. And Lindenfeld and Fattah were, at\na minimum, involved in some way in nearly every aspect\nof the origination of the loan, the false campaign finance\nreports, and the use of misappropriated funds to repay the\nloan. For his part, Naylor was involved in the use of the\nfunds, the false campaign finance reports, and to a lesser\nextent, the repayment of the loan.\n Brand (as part of his variance argument) and\nNicholas (as part of her sufficiency argument) argue that\nthe Government did not prove they agreed to conceal their\nactions, and thus the false campaign reports would not be\n\n 116\n\fsufficient to extend the duration of the conspiracy so that\nit fell within the statute of limitations. Acts of\nconcealment, such as the false campaign reports, are not\nautomatically “in furtherance” of a conspiracy. We must\ndetermine whether there was “an express original\nagreement among the conspirators to continue to act in\nconcert in order to cover up, for their own self-protection,\ntraces of the crime after its commission,” as opposed to “a\nconspiracy to conceal . . . being implied from elements\nwhich will be present in virtually every conspiracy case,\nthat is, secrecy plus overt acts of concealment.”\nGrunewald v. United States, 353 U.S. 391, 404 (1957). If\nthe indictment “specifically alleges a continuing\nconspiracy” to conceal the crime after the completion of\nthe wire fraud, and such a conspiracy can be proven, the\nstatute of limitations does not begin to run until the last\novert act of concealment. United States v. Moses, 148 F.3d\n277, 282 (3d Cir. 1998).\n\n Here, the evidence shows that the conspirators\nexpressly agreed to conceal the loan and its repayment. As\nan initial matter, Brand’s only role in the conspiracy was\nto cover up the use of stolen funds by (1) serving as an\nintermediary between Nicholas and Lindenfeld; and\n(2) agreeing to create false documentation (the contracts)\nwith both EAA and Strategies for the sole purpose of\ndisguising the payments and covering up the wire fraud\nconspiracy. Nicholas could simply have paid Lindenfeld\nherself (or paid Lord) if she and Brand had not agreed to\nconceal the crime from the start. Additionally, and as\n 117\n\fBrand acknowledges, the false campaign finance reports\nbegan before the loan was repaid, proving that\nconcealment of the crime was contemplated and begun as\na direct purpose of the conspiracy before Brand and\nNicholas became involved in the repayment. Nicholas too\nagreed to conceal the repayment, as she implicitly\nacknowledged in her emails with Brand and Fattah. GSA2.\nFinally, when Lindenfeld briefly strayed from the\nconspiracy’s commitment to secrecy by mentioning the\nrepayment in front of others who did not know of the\nscheme, Brand became “angry,” “took [Lindenfeld] out in\nthe hallway,” and chastised him, saying that “[Lindenfeld]\ncouldn’t say that sort of []thing” in front of other people.\nJA1670–71. We conclude that the evidence is consistent\nwith the allegations in the indictment, which charge a\nsingle conspiracy consisting of an original agreement to\nconceal the illegal loan and its subsequent illegal\nrepayment to further Fattah’s political career.\n\n Nicholas makes several arguments in passing. She\nsuggests that the District Court upheld the conviction after\ntrial “on a theory not submitted to the jury.” Nicholas Br.\n51. This argument is, essentially, that the indictment and\nthe District Court’s post-trial ruling described the\nconspiracy one way, but that the jury charge described the\nconspiracy differently. Nicholas argues that the jury was\npresented with the theory that the sole purpose of the false\ncampaign reports under Count 2 was to “conceal[] the\nalleged scheme to defraud,” JA5849, rather than to support\n\n 118\n\fFattah’s political career, as the District Court described the\npurpose after trial, see JA74.\n Nicholas ignores that part of the jury charge which\ninstructed that Count 2 required a finding “[t]hat two or\nmore persons agreed to commit wire fraud as charged in\nthe indictment.” JA5845 (emphasis added). The jury had\naccess to the indictment, and as Nicholas points out,\nNicholas Br. 45–46, the indictment outlines the offense in\nthe same way the District Court later described it in its\npost-trial ruling. The District Court consistently described\nthe count, and we see no reversible error.\n Nicholas also argues that the conspiracy charged in\nCount 2 has an objective—“to ‘present Fattah’ as\n‘perennially viable’ ”—and that such an objective is not\nillegal. Nicholas Br. 53. But, of course, the jury was not\ninstructed that it was illegal to be a Fattah supporter, or\neven to work on his campaign. The jury was charged\nspecifically on the crime of wire fraud.\n\n We conclude that there was no impermissible\nvariance between the indictment and the Government’s\nevidence at trial, and that there was sufficient evidence to\nsupport the convictions. We will affirm the convictions of\nBrand and Nicholas for conspiracy to commit wire fraud\nunder Count 2.\n\n\n\n\n 119\n\f VII. The District Court’s Instruction to the Jury on\n the Meaning of Intent\n Nicholas contends that the District Court\nimproperly instructed the jury by using the disjunctive\nrather than the conjunctive at one point in its definition of\nintent. When providing its final charge to the jury, the\nDistrict Court explained:\n Certain of the offenses charged in the\n indictment require that the government prove\n that the charged defendant acted intentionally\n or with intent. This means that the\n government must prove either that (1), it was\n the defendant’s conscious desire or purpose\n to act in a certain way or to cause a certain\n result; or (2), the defendant knew that he or\n she was acting in that way or it would be\n practically certain to cause that result.\n\nJA5787 (emphasis added). According to Nicholas, an\naccurate definition of intent required that the final “or” be\nan “and.” Nicholas argues that this was an error so\ngrievous as to “effectively eliminate[] the intent element\nfrom each offense of conviction.” 22 Nicholas Br. 26.\n\n\n22\n The Comment to Third Circuit Model Criminal Jury\nInstruction 5.03 makes clear that the definition of intent\nencapsulates both “specific intent” (acting “purposely” or\nwith “conscious object”) and “general intent” (acting\n 120\n\f Our review of whether a jury instruction stated the\nproper legal standard is plenary. United States v. Petersen,\n622 F.3d 196, 207 n.7 (3d Cir. 2010). At trial, Nicholas\nfailed to object to this portion of the jury charge.\nAccordingly, our review must be for plain error. See\nUnited States v. Flores-Mejia, 759 F.3d 253, 258 (3d Cir.\n2014) (en banc).\n\n To prevail on plain error review, Nicholas must\nestablish that there was an error, that it was plain (i.e., clear\nunder current law), and that it affected her substantial\nrights (i.e., whether there is a reasonable likelihood that\nthe jury applied the challenged instruction in an\nimpermissible manner). United States v. Olano, 507 U.S.\n\n“knowingly” or “with awareness”). Although Nicholas\ndescribes the alleged error as “essentially eliminating” the\nelement of intent, we think Nicholas’s argument is better\nunderstood as a claim that the instruction given could have\npermitted a jury to conclude that she acted with only\ngeneral intent (that she was aware of what she was doing),\nwhen her crimes require specific intent (that she had an\nillegal purpose). As her brief states, “[p]lainly she\n‘knowingly’ wrote checks from EAA to [Solutions] and\nmade record entries about them; the question was whether\nshe intended to defraud EAA and NASA, or to obstruct\njustice, by doing so.” Nicholas Br. 24. We cannot agree\nwith her characterization that the instruction resulted in the\n“effective omission” of the intent element from the jury\ninstructions.\n 121\n\f725, 733–34 (1993); United States v. Dobson, 419 F.3d\n231, 239–40 (3d Cir. 2005). If these requirements are met,\nwe may then exercise our discretion to address the error,\nbut only if we conclude that the error seriously affected the\nfairness, integrity, or public reputation of the judicial\nproceeding. United States v. Andrews, 681 F.3d 509, 517\n(3d Cir. 2012) (quoting Johnson v. United States, 520 U.S.\n461, 467 (1997)). A failure to instruct the jury on a\nnecessary element of an offense ordinarily constitutes\nplain error, unless the instructions as a whole otherwise\nmake clear to the jury all the necessary elements of the\noffense. United States v. Stimler, 864 F.3d 253, 270 (3d\nCir. 2017).\n Nicholas acknowledges, as she must, that the\ninstruction given was a verbatim recitation of Instruction\n5.03 of the Third Circuit’s Model Criminal Jury\nInstructions. She nonetheless contends that our Model\nInstruction is erroneous. Even if we were to accept\nNicholas’s contention that the instruction is incorrect, a\nproposition we consider as highly doubtful, see Petersen,\n622 F.3d at 208 (“We have a hard time concluding that the\nuse of our own model jury instruction can constitute error\n. . . .”), we conclude that, considering the instructions as a\nwhole, the District Court clearly and specifically\ninstructed the jury on the intent element as it applied to\neach of Nicholas’s charged crimes.\n\n The disputed intent instruction was given at the\nbeginning of the final charge, explaining the general\n\n 122\n\fmeaning of the intent applicable to “[c]ertain of the\noffenses charged.”23 JA5787. The District Court went on\nto instruct the jury in specific detail on the elements of\neach of the crimes of which Nicholas was accused,\n\n\n\n\n23\n The introductory definition did not end with the\nlanguage Nicholas cites. The District Court elaborated that\nacting in good faith is a complete defense to the charges:\n\n The offenses charged in the indictment\n require proof that the charged defendants\n acted with criminal intent. If you find that a\n defendant acted in good faith that would be a\n complete defense to such a charge, because\n good faith on the part of the defendant would\n be inconsistent with his or her acting\n knowingly, willfully, corruptly, or with intent\n to defraud or intent to impede, obstruct, or\n wrongfully influence.\n\nJA5788–89 (emphasis added). This instruction\nundermines Nicholas’s claim that the jury could have\nreasonably concluded that she “ ‘knowingly’ wrote\nchecks” but did not “intend[] to defraud . . . or to obstruct\njustice[] by doing so,” Nicholas Br. 24, as this instruction\nleaves little room for doubt that good faith is at odds with\n“criminal intent.”\n\n 123\n\fexplaining also the intent element of each. 24 See JA5791\n(describing the third element of the RICO conspiracy\ncharge as: “the particular defendant and at least one other\nalleged conspirator shared a unity of purpose and the intent\nto achieve the objective of conducting or participating in\nthe conduct of an enterprise’s affairs through a pattern of\nracketeering activity”); JA5823 (regarding wire fraud,\ninstructing that the government must prove “[t]hat the\ndefendant under consideration acted with the intent to\ndefraud”); JA5838–39 (regarding obstruction of justice,\ninstructing that the defendant must have acted “with the\nintent to impair the record, document, or object’s integrity\nor availability for use in an official proceeding,” and must\nhave acted corruptly “with the purpose of wrongfully\nimpeding the due administration of justice”); JA5860\n(explaining that falsification of records requires that “the\ndefendant under consideration acted with the intent to\nimpede, obstruct or influence the investigation or proper\nadministration of a matter”). These instructions are\nconsistent with both our Model Jury Instructions and our\ncase law concerning the elements of these crimes. See\nThird Circuit Model Criminal Jury Instruction 6.18.1962D\n(RICO), 6.18.1343 (wire fraud), 6.18.1512A2 (obstruction\nof justice); United States v. Sussman, 709 F.3d 155, 168\n(3d Cir. 2013) (obstruction of justice); United States v.\n\n24\n Nicholas did not object to the knowledge and intent\ninstructions when the District Court discussed each of the\nindividual charges, and does not identify a disagreement\nwith any specific instruction on any particular charge.\n 124\n\fMoyer, 674 F.3d 192, 208–09 (3d Cir. 2012) (falsification\nof records); United States v. Pelullo (Pelullo I), 964 F.2d\n193, 216 (3d Cir. 1992) (wire fraud).\n The District Court also provided a separate\ndefinition of the knowledge element of each charge,\nillustrating the difference between knowledge and intent.\nSee JA5793 (explaining that the evidence must show that\na RICO defendant “knowingly agreed to facilitate or\nfurther a course of conduct, which if completed would\ninclude a pattern of racketeering activity”); JA5823 (wire\nfraud means that the defendant “knowingly devised a\nscheme to defraud a victim . . . by materially false or\nfraudulent pretenses”); JA5860 (falsification of records\nhas as an element “[t]hat the defendant under\nconsideration knowingly concealed, covered up, falsified\nor made false entries in a document or record”). These\ninstructions made clear that knowledge and intent are\nseparate considerations, undermining Nicholas’s\ncontention that the jury was led to believe that “knowledge\nis sufficient to prove intent.” Nicholas Br. 24.\n The District Court provided each member of the\njury with more than 100 pages of instructions before\ndeliberations began. Viewing those instructions as a\nwhole, we are satisfied that the jury was apprised of the\ncorrect meaning of intent as an element of the crimes with\nwhich Nicholas was charged, as well as the distinction\nbetween knowledge and intent. We perceive no error,\n\n\n 125\n\fmuch less error that is plain, in the District Court’s\ninstructions to the jury. 25\n\n VIII. Sending the Indictment to the Jury\n At trial, Vederman, Nicholas, and Brand objected to\nthe District Court’s decision to give the jury a redacted\ncopy of the indictment to use during its deliberations. Only\nNicholas and Brand raise this issue on appeal. In\nNicholas’s view, sending the indictment to the jury\nunfairly prejudiced her because it contained unsupported\nallegations that she had obstructed federal agencies and\nreferred to a nonexistent certification requirement for\nSallie Mae funds. Brand argues that he was prejudiced by\nthe indictment’s references to “schemes” and “fake”\ncontracts, and because it mentioned Brand’s spouse and\nthat she was a former member of Fattah’s congressional\nstaff. Nicholas and Brand together assert that the\nindictment included legal theories on which the jury was\nnot instructed. They contend that the indictment’s\nnarrative of the Government’s case set out a roadmap that\nomitted any averments relating to the defense theory and\nallowed the Government to yet again present its case. To\nbuttress that argument, Nicholas and Brand cite the\ntestimony of Juror 12, who described the jury’s initial\n\n\n\n25\n Accordingly, we need not consider the merits of\nNicholas’s argument that Model Criminal Jury Instruction\n5.03 is erroneous.\n 126\n\fdeliberations and alleged that the jurors viewed the\nindictment as evidence.\n In United States v. Todaro, 448 F.2d 64, 66 (3d Cir.\n1971), we held that the decision to allow “jurors to have a\ncopy of the indictment with them during their\ndeliberations . . . is a matter within the discretion of the\nDistrict Judge, subject to a limiting instruction that the\nindictment does not constitute evidence, but is an\naccusation only.” Subsequently, in United States v.\nPungitore, 910 F.2d 1084, 1142 n.83 (3d Cir. 1990), we\nacknowledged that the District Court has the power to\nredact the indictment if doing so would be appropriate to\navoid prejudice to the defendant. See also United States v.\nRoy, 473 F.3d 1232, 1237 n.2 (D.C. Cir. 2007) (noting that\ncourt may redact an indictment before submitting it to the\njury).\n\n While both Nicholas and Brand objected in general\nterms to the District Court’s decision to provide the\nindictment to the jury, they have not directed us to any\nspecific request to redact the information they now claim\nis prejudicial. And the District Court provided a limiting\ninstruction on four occasions during its charge, repeatedly\nemphasizing that the indictment was not evidence.\nJA5765, 5767, 5782, 5880. The Court instructed the jury\non its duty to base its verdict “solely upon the evidence in\nthe case.” JA5764. Just before the jury retired to\ndeliberate, the Court reiterated that the purpose of the\n\n\n 127\n\findictment is to set forth the charges, and that it is “merely\nan accusation.” JA5909.\n “[J]uries are presumed to follow their instructions\n. . . .” Richardson v. Marsh, 481 U.S. 200, 211 (1987). In\nour view, Juror 12’s assertion that the indictment was\nbeing considered evidence does not, standing alone,\nestablish that his fellow jurors actually did so. We reject\nthe notion that the jury, after hearing weeks of testimony\nand having viewed substantial documentary evidence,\nwent on to ignore the Court’s limiting instruction\nconcerning the indictment. 26 Accordingly, we conclude\n\n\n26\n We acknowledge that our case law provides minimal\nguidance to district courts concerning the practice of\nsending an indictment to the jury for their use during\ndeliberations. We are also aware that some courts have\ndisapproved the practice of sending the indictment out\nwith the jury. See United States v. Esso, 684 F.3d 347, 352\nn.5 (2d Cir. 2012); Roy, 473 F.3d at 1237 n.2. We\nemphasize that this practice is committed to the sound\ndiscretion of the district judge. Todaro, 448 F.2d at 66. In\nour view, such an exercise of a judge’s discretion should\nbe informed by considering the nature of the case, the\nnumber of defendants, the length of the indictment, the\nextent of the factual recitation supporting the criminal\ncharges, and most importantly, whether the indictment\n(especially if lengthy and fact-laden) will be useful to the\njury, in light of the judge’s own carefully tailored jury\n 128\n\fthat the District Court did not abuse its discretion in\nsending the indictment out to the jury.\n\n IX. The District Court’s Evidentiary Rulings\n Vederman, Nicholas, and Brand each challenge\nevidentiary rulings by the District Court. We conclude that\nnone of these contentions warrants setting aside their\nconvictions.\n\n A. The District Court’s Application of Rule 404(b)\n Vederman argues that the District Court misapplied\nFederal Rule of Evidence 404(b) when it excluded\nevidence of Vederman’s prior gift-giving. 27 This Court\nreviews a district court’s application of Rule 404(b) for\nabuse of discretion. United States v. Daraio, 445 F.3d 253,\n\ninstruction, as supplemented by a verdict slip. See Esso,\n684 F.3d at 352 n.5.\n27\n Although Rule 404(b) determinations are usually in\nresponse to attempts to introduce “bad” acts evidence,\nVederman’s attempt to introduce “good” acts of gift-\ngiving is properly analyzed under the same rule. Ansell v.\nGreen Acres Contracting Co., 347 F.3d 515, 520 (3d Cir.\n2003) (“The evidence admitted in this case differs from\ngarden variety Rule 404(b) matter because it is evidence,\nnot of a prior bad act in a criminal case, but of a subsequent\ngood act in a civil case. Nonetheless, this evidence is\nencompassed by the plain text of Rule 404(b) which\naddresses ‘other . . . acts,’ not just prior bad acts.”).\n 129\n\f259 (3d Cir. 2006); Ansell v. Green Acres Contracting Co.,\n347 F.3d 515, 519 (3d Cir. 2003). A trial court commits\n“[a]n abuse of discretion . . . when [the] district court’s\ndecision rests upon a clearly erroneous finding of fact, an\nerrant conclusion of law or an improper application of law\nto fact.” Pardini v. Allegheny Intermediate Unit, 524 F.3d\n419, 422 (3d Cir. 2008) (quoting P.N. v. Clementon Bd. of\nEduc., 442 F.3d 848, 852 (3d Cir. 2006)).\n\n Federal Rule of Evidence 404(b) provides in part:\n (b) Crimes, Wrongs, or Other Acts.\n\n (1) Prohibited Uses. Evidence of a\n crime, wrong, or other act is not\n admissible to prove a person’s\n character in order to show that on a\n particular occasion the person\n acted in accordance with the\n character.\n\n (2) Permitted Uses; Notice in a\n Criminal Case. This evidence may\n be admissible for another purpose,\n such as proving motive,\n opportunity, intent, preparation,\n plan, knowledge, identity, absence\n of mistake, or lack of accident.\nFed. R. Evid. 404(b)(1)–(2).\n\n 130\n\f At trial, Vederman sought to present a witness from\nAmerican University who would have testified that\n“Vederman agreed, on more than fifty instances, to\nfinancially assist students [at American] who needed help\nwith tuition, book money, or travel funds to visit their\nfamilies.” Vederman Br. 42 (emphasis omitted).\nAccording to Vederman, the testimony was relevant to\nrefuting the Government’s argument that he agreed to\nguarantee the tuition expenses of Fattah’s au pair as a way\nof bribing the congressman. In excluding this evidence\nunder Rule 404(b), the District Court stated at sidebar:\n\n I sustain the government’s objection to\n calling a representative of American\n University to testify on behalf of Herbert\n Vederman.\n\n In my view the testimony runs afoul of\n Rule 404(b)(1) of the Federal Rules of\n Evidence. I find it to be propensity evidence.\n He or she would be testifying about Mr.\n Vederman’s financial generosity with respect\n to students of American University.\n The issue here is payment of partial\n tuition of a student at the Philadelphia\n University. I see no connection between the\n generosity at American University and the\n situation with Philadelphia University.\n\n\n 131\n\fJA4459–60. Vederman argues that because the proposed\nevidence related to Vederman’s intent, and not solely his\npropensity to perform good acts, we should conclude that\nthe District Court abused its discretion. We see no error in\nthe District Court’s ruling.\n\n Vederman challenges as arbitrary the District\nCourt’s “assertion that support for American University\nstudents is too remote from support for Philadelphia\nUniversity students” such that it constitutes inadmissible\nevidence. Vederman Reply Br. 23. This distinction was far\nfrom arbitrary. Vederman may well have financially\nsupported American University students because of\nconnections he had to that school or to the D.C.\ncommunity at large—connections Vederman did not have\nto Philadelphia University. And the excluded testimony\nappears to have described support for students Vederman\ndid not previously know. By supporting Fattah’s au pair,\nVederman was helping an employee of a man whom he\nknew quite well. JA889 (“[Fattah and Vederman] spent a\nlot of time together traveling back and forth to\nWashington, in the case of a death in the family attending\ncertain ceremonies that were important, and above all\nspending time with each other and their families\ntogether.”). Vederman’s decision to help Fattah’s au pair,\nwho wished to attend Philadelphia University, seems more\nlike a departure from, rather than a continuation of, his\npattern of support for American University students.\n\n\n\n 132\n\f As the party seeking admission of evidence under\nRule 404(b), Vederman bore “the burden of demonstrating\nits applicability” and “identifying a proper purpose.”\nUnited States v. Caldwell, 760 F.3d 267, 276 (3d Cir.\n2014). By failing to explain sufficiently why the factual\ndistinctions discussed above were not material, Vederman\nfailed to meet his burden. In particular, although\nVederman argues that he offered evidence of his prior gift-\ngiving to prove intent—“a proper non-propensity\npurpose”—he failed to show why the proposed testimony\nwas “relevant to that identified purpose.” Id. at 277. 28 As\nwe noted in Ansell v. Green Acres Contracting, an\nemployment discrimination case on which Vederman\nheavily relies, “[t]here is. . . no bright line rule for\ndetermining when evidence is too remote to be relevant.”\n347 F.3d at 525. As such, a district court’s determination\nunder Rule 404(b) “will not be disturbed on appeal unless\nit amounts to an abuse of discretion.” Id. The District\n\n\n\n28\n Under Rule 404(b), “prior act evidence is inadmissible\nunless the evidence is (1) offered for a proper non-\npropensity purpose that is at issue in the case; (2) relevant\nto that identified purpose; (3) sufficiently probative under\nRule 403 such that its probative value is not outweighed\nby any inherent danger of unfair prejudice; and\n(4) accompanied by a limiting instruction, if requested.”\nUnited States v. Caldwell, 760 F.3d 267, 277–78 (3d Cir.\n2014).\n 133\n\fCourt did not abuse its discretion in excluding evidence of\nVederman’s support for students at American University.\n\nB. Evidentiary Rulings Regarding Nicholas’s Defense\n Nicholas argues that the District Court rendered\nthree erroneous evidentiary rulings that prejudiced her\ndefense. We do not find any of her arguments convincing.\n\n 1. The EAA Board Minutes\n In support of its theory that Nicholas defrauded\nEAA, the Government introduced minutes from EAA’s\nBoard. Minutes from 2005 revealed that the Board limited\nNicholas’s signing authority to $100,000. Minutes from\nDecember 2007, February 2008, and May 2008 failed to\nreference either the EAA–Solutions contract or the checks,\ndrawn from EAA’s account for $500,000 and $100,000,\nthat were purportedly paid pursuant to the contract.\nNicholas contends that the Board minutes were\nerroneously admitted because they constituted improper\nhearsay which failed to satisfy either the exception for\nbusiness records under Federal Rule of Evidence 803(6)\nor the absence of records exception under Federal Rule of\nEvidence 803(7). “We review the District Court’s\nevidentiary ruling[s] for abuse of discretion, but also\n‘exercise plenary review . . . to the extent [the rulings] are\nbased on a legal interpretation of the Federal Rules of\nEvidence.’ ” Repak, 852 F.3d at 240 (citations omitted)\n(second alteration in original).\n\n 134\n\f Applying those standards here,29 we conclude there\nwas sufficient basis to admit exhibit EAA-48 under\nFederal Rule of Evidence 803(6) as a business record.\nAlthough allowing the prosecution to inquire over\nNicholas’s earlier objection based on Federal Rule of\nEvidence 803(7) to the absence of any mention of the\n$500,000 check in the 2008 Board Minutes was error, it\nwas not reversible error. Other evidence in the record\noverwhelmingly showed that Nicholas made the $500,000\nand $100,000 payments to Solutions with the requisite\nfraudulent intent. That evidence included the 2005 policy\nlimiting Nicholas’s authority to approve expenditures to\n$100,000, the accountant’s testimony about the\ndisbursement policy requiring the completion of a check\nrequest form for the issuance of a check, and Jones’\ntestimony that he never saw a request for the $500,000\ncheck. That evidence, coupled with Nicholas’s tendering\nof the upfront half-million dollar payment before the terms\nof the purported agreement had been finalized or executed,\nher failure to mention the $600,000 in payments to\nSolutions during her interview with FBI Agent\n\n29\n We note that the argument section of Nicholas’s brief on\nthis issue specifically cited to the page in the record where\nexhibit EAA-48 was admitted without objection by any\ndefense counsel. See Appellant’s Br. at 57 (citing JA4381-\n82). Nonetheless, there was an earlier objection to the\nadmission of exhibit EAA-48 that was preserved and that\nwas referenced in a string citation elsewhere in Nicholas’s\nbrief.\n 135\n\fDieffenbach, and her alteration of EAA’s general ledger\nto conceal the $100,000 payment, makes it “highly\nprobable” that the jury would have reached the same\nresult. See United States v. Friedman, 658 F.3d 342, 352\n(3d Cir. 2011).\n\n Nicholas also asserts that the Board minutes were\nunfairly prejudicial. We disagree. Any possible prejudice\nwas minimized by the fact that the Board minutes make no\nreference to either the EAA–Solutions contract or to any\nfinancial matters whatsoever. Indeed, given these lacunae\nin the Government’s proof, a reasonable factfinder might\nwell have concluded that the Board’s intention to limit\nNicholas’s signing authority had not been implemented\nand that Nicholas had not concealed the contract from the\nBoard.\n\n 2. Jones’ Memory Regarding Other Contracts\n Nicholas next asserts that the District Court erred\nduring her cross-examination of Board Chairman Jones by\nsustaining the prosecution’s objection to her inquiry into\nwhether he remembered other contracts in excess of\n$100,000 being brought to the Board. See JA1386–87. The\nbasis of the prosecution’s objection seemed to be that\nNicholas’s line of inquiry was beyond the scope of the\ndirect testimony. JA1387 (“I showed checks concerning\nwhat’s going on, not other programs.”); see Fed. R. Evid.\n611(b). The District Court sustained the objection,\ndeclaring that “it has absolutely nothing to do with this\ncase.” JA1387. Nicholas contends that if Jones did not\n 136\n\frecall whether other large contracts had been presented to\nthe Board, his inability to recall the EAA–Solutions\ncontract would have been “unremarkable rather than\nevidence of fraud or concealment.” Nicholas Br. 61.\n\n We acknowledge that whether Jones remembered\nother large contracts requiring Board approval had some\nrelevance under Rule 401. Yet any error by the District\nCourt in prohibiting Nicholas’s counsel from pursuing this\nline of inquiry is harmless. Jones admitted that he did not\nknow if the Board ever implemented the policy requiring\nits approval of contracts exceeding $100,000. He also\nconceded that the EAA Board focused less on the financial\nside of EAA than on its programs. JA1383–85. Nicholas\ncould not have been prejudiced by the District Court’s\nruling.\n\n 3. Exclusion of NOAA Evidence\n Nicholas defended against the criminal charges\narising out of the non-existent October 2012 conference\nby asserting that she acted in “good faith in spending the\nNOAA funds on EAA expenses,” Nicholas Br. 64, that the\ndifference in the dates in the paperwork was not material,\nand that NOAA had received the benefits of the\nsponsorship because its logo was displayed on the signage\nused at the February conference. Nicholas succeeded in\npresenting testimony and introducing photographs that\nshowed NOAA’s logo on the February 2012 annual\nconference bags, padfolios, and name tags. The Court\nexcluded a photograph of a NOAA intern at the February\n 137\n\f2012 conference, other photographs of the February\nconference signage, and some checks that pertained to the\nFebruary conference. Nicholas claims that her inability to\nintroduce those exhibits frustrated her ability to present\nher good faith defense. We are not persuaded.\n\n The photographs were excluded as cumulative, the\nsort of ruling to which we afford trial judges very broad\ndiscretion. See Fed. R. Evid. 403; United States v.\nDalfonso, 707 F.2d 757, 762 (3d Cir. 1983). It was not\nerror to exclude the student intern’s photograph. The\nconference brochure included photographs from previous\nconferences, and the witness from NOAA was unable to\ntestify to the year the student served as an intern. Finally,\nthe checks tendered for the travel expenses incurred for the\nFebruary conference were excluded as irrelevant to\nwhether Nicholas had a good faith belief that NOAA\nsponsored the October conference.\n\nC. The Cooperating Witness’s Mental Health Records\n During discovery, Brand learned that a cooperating\nwitness was diagnosed with bipolar II disorder and was\ntaking medication to treat that condition. Brand\nsubpoenaed mental health records kept by the witness’s\ncurrent and former psychiatrists in hopes of using those\nrecords to attack the witness’s memory, truthfulness, and\ncredibility. The witness and the Government both filed\nmotions to quash the subpoena, arguing that the witness’s\nmental health records were protected by the\npsychotherapist–patient privilege recognized by the\n 138\n\fSupreme Court in Jaffee v. Redmond, 518 U.S. 1 (1996).\nThe Government also filed a motion in limine seeking to\nrestrict the scope of cross-examination to prevent Brand\nfrom questioning the witness about his mental health.\n\n Alongside his motion to quash, the witness\nvoluntarily produced for the Court his mental health\nrecords. The Court concluded that the psychotherapist–\npatient privilege would ordinarily apply to the mental\nhealth records, but that the privilege was not absolute,\nespecially when invoked in response to a criminal\ndefendant’s efforts to obtain through discovery evidence\nthat is favorable to his case. Following the procedure set\nforth in Pennsylvania v. Ritchie, 480 U.S. 39 (1987), the\nDistrict Court conducted an in camera review of the\nmental health records to determine if they contained\nmaterial evidence—that is, evidence that would “give[]\nrise to a reasonable probability that it [would] affect the\noutcome of the case.” JA149. The District Court found\n“nothing in the mental health records of the [witness] . . .\nmaterial for this criminal action,” noting that “[t]he\nrecords reveal nothing that calls into question [the\nwitness’s] memory, perception, competence, or veracity.”\nJA150. Accordingly, the Court entered an order granting\nthe motions to quash the subpoena.\n The District Court also granted the Government’s\nmotion in limine and restricted the scope of cross-\nexamination, ruling that “no reference may be made to [the\nwitness’s] bipolar disorder or the medications he takes to\n\n 139\n\fmanage it.” JA142, 156. The Court reasoned that bipolar\ndisorder varied in its effects from person to person, and\nconcluded that Brand had not shown that the effects of the\ndisorder had any bearing on the witness’s credibility. The\nDistrict Court ruled that cross-examination would not\nserve any valid impeachment purpose.\n Brand claims that the District Court’s order ran\nafoul of the Due Process Clause of the Fifth Amendment\nand the Confrontation Clause of the Sixth Amendment.\nWe review a district court’s rulings to quash a subpoena\nand to limit the scope of cross-examination for abuse of\ndiscretion. United States v. Tykarsky, 446 F.3d 458, 475\n(3d Cir. 2006); NLRB v. Frazier, 966 F.2d 812, 815 (3d\nCir. 1992). Here, the District Court did not abuse that\ndiscretion.\n\n1. The District Court’s Denial of Access to the Mental\n Health Records\n In claiming that the District Court’s decision to\nreview the mental health records in camera before ruling\non their admissibility violated his rights under both the\nFifth and Sixth Amendments, Brand specifically argues\nthat his right to confront the witness was impeded because\nhe was denied access to records he could have used to\nimpeach the witness. This very argument was considered\nand rejected by a plurality of the Supreme Court in Ritchie,\nwhich noted that “the effect [of the argument] would be to\ntransform the Confrontation Clause into a constitutionally\ncompelled rule of pretrial discovery. . . . [T]he right to\n 140\n\fconfrontation is a trial right, designed to prevent improper\nrestrictions on the types of questions that defense counsel\nmay ask during cross-examination.” 480 U.S. at 52. We\nfollow the Ritchie plurality, and conclude that the\nConfrontation Clause did not require the District Court to\ngrant Brand access to the witness’s mental health records.\n Brand next challenges the District Court’s decision\nto quash the subpoena as a violation of the Fifth\nAmendment’s Due Process Clause. He concedes that\nRitchie’s Due Process holding allowed the District Court\nto review the mental health records in camera without\ndisclosing them to him. See id. at 59–60 (“A defendant’s\nright to discover exculpatory evidence does not include the\nunsupervised authority to search through [the\nGovernment’s] files. . . . We find that [the defendant’s]\ninterest . . . in ensuring a fair trial can be protected fully by\nrequiring that the [privileged] files be submitted only to\nthe trial court for in camera review.”). Brand instead\nargues that the District Court abused its discretion by\nfocusing on “irrelevant facts and spurious symptoms. . . .\nsuch as ‘hallucinations,’ ” and by “refus[ing] to consider\nevidence of cognitive impairment and memory issues.”\nBrand Br. 30. The record reveals, however, that the\nDistrict Court reviewed the mental health records and\ndetermined that they “reveal[ed] nothing that calls into\nquestion [the witness’s] memory, perception, competence,\nor veracity.” JA150. This hardly amounts to a refusal to\nconsider evidence of cognitive impairment or memory\nissues.\n 141\n\f Brand also challenges the legal standard applied by\nthe District Court, arguing that the court “focused solely\non whether disclosure would ‘change the outcome’ of\nBrand’s trial,” Brand Br. 29 (quoting JA148), rather than\nconsidering “whether the ultimate verdict is one ‘worthy\nof confidence.’ ” Id. (quoting United States v. Robinson,\n583 F.3d 1265, 1270 (10th Cir. 2009)). Brand\nmisleadingly quotes from the District Court’s opinion. The\nDistrict Court considered, in accordance with Ritchie,\n“whether there is a reasonable probability that disclosure\nwould change the outcome” of Brand’s trial, JA148\n(emphasis added), not whether disclosure would\nnecessarily change the outcome. As articulated in Ritchie,\na “ ‘reasonable probability’ is a probability sufficient to\nundermine confidence in the outcome.” 480 U.S. at 57\n(quoting United States v. Bagley, 473 U.S. 667, 682 (1985)\n(Blackmun, J.)). The District Court applied the correct\nstandard.\n\n2. The District Court’s Grant of the Motion in Limine\n In granting the Government’s motion in limine, the\nDistrict Court ruled that Brand could not “reference . . .\n[the witness’s] bipolar disorder or the medications he takes\nto manage it.” JA156. Yet that ruling placed no restriction\non Brand’s ability to cross-examine the witness with\nrespect to “his memory, competence, or truthfulness.” Id.\nBrand argues, nevertheless, that his Sixth Amendment\nright “to be confronted with the witnesses against him”\nwas violated. U.S. Const. amend. VI.\n\n 142\n\f The Confrontation Clause protects a defendant’s\nright to cross-examine a witness with respect to any\ntestimonial statements made by that witness. United States\nv. Berrios, 676 F.3d 118, 125–26 (3d Cir. 2012) (citing\nCrawford v. Washington, 541 U.S. 36, 51 (2004), and\nDavis v. Washington, 547 U.S. 813, 823–24 (2006)). But\nthe scope of cross-examination is not unlimited, and “[a]\ndistrict court retains ‘wide latitude insofar as the\nConfrontation Clause is concerned to impose reasonable\nlimits on such cross-examination based on concerns about\n. . . harassment, prejudice, confusion of the issues, the\nwitness’ safety, or interrogation that is repetitive or only\nmarginally relevant.’ ” John-Baptiste, 747 F.3d at 211\n(quoting United States v. Mussare, 405 F.3d 161, 169 (3d\nCir. 2005)). We review limitations on cross-examination\nfor abuse of discretion, and reverse “only when the\nrestriction ‘is so severe as to constitute a denial of the\ndefendant’s right to confront witnesses against him and . . .\nis prejudicial to [his] substantial rights.’ ” Id. (alternation\nin original) (quoting United States v. Conley, 92 F.3d 157,\n169 (3d Cir. 1996)).\n In United States v. Chandler, 326 F.3d 210, 219 (3d\nCir. 2003), we analyzed whether a district court’s decision\nto limit cross-examination with respect to a witness’s\nmotivation for testifying violated the Confrontation\nClause. See also Mussare, 405 F.3d at 169; John-Baptiste,\n747 F.3d at 211–12. Consistent with Delaware v. Van\nArsdall, 475 U.S. 673 (1986), we first concluded that “the\nexposure of a witness’ motivation in testifying is a proper\n 143\n\fand important function of the constitutionally protected\nright of cross-examination.” Chandler, 326 F.3d at 219–\n20 (quoting Van Arsdall, 475 U.S. at 678–79). We also\nnoted that the Confrontation Clause does not prevent a trial\njudge from imposing reasonable limits on cross-\nexamination. Id. In reviewing a district judge’s imposition\nof such limitations, we apply a two-part analysis. As we\nhave since described, “we inquire into: ‘(1) whether the\nlimitation significantly limited the defendant’s right to\ninquire into a witness’s motivation for testifying; and\n(2) whether the constraints imposed fell within the\nreasonable limits that a district court has the authority to\nimpose.’ ” John-Baptiste, 747 F.3d at 211–12 (quoting\nMussare, 405 F.3d at 169).\n The same analytical framework is appropriate when\ndetermining whether a restriction on the cross-\nexamination of a witness with respect to his memory and\nperception violates the Confrontation Clause. See Davis v.\nAlaska, 415 U.S. 308, 316 (1974); Greene v. McElroy, 360\nU.S. 474, 496 (1959); United States v. Segal, 534 F.2d\n578, 582 (3d Cir. 1976). Memory and perception, like\nmotivation for testifying, are central issues affecting the\ncredibility of any witness, and unreasonable limitations on\nthe right to cross-examine on those subjects cannot be\ncountenanced. We therefore ask, paraphrasing Chandler:\n(1) whether the District Court’s decision to put the\nwitness’s diagnosis and medications off limits\nsignificantly impaired Brand’s right to inquire into the\nwitness’s memory and perception; and (2) whether the\n 144\n\fruling fell within the reasonable limits that the District\nCourt has the authority to impose.\n We conclude that the District Court did not err. As\nan initial matter, the District Court permitted Brand to\ncross-examine the witness about his memory and\nperception, and limited cross-examination only with\nrespect to the witness’s bipolar disorder and the\nmedications he was taking to treat that condition. Brand\nwas free to question the witness about his memory and\nperception, and indeed did so. The restriction on asking\nthe witness about his bipolar disorder was not a significant\nlimitation of Brand’s right to inquire into the witness’s\nmemory or perception. Moreover, as the District Court\npointed out, Brand failed to show how inquiry into the\nwitness’s bipolar disorder would be useful for\nimpeachment purposes. See JA154.\n\n Given that failure, the District Court’s limits on\ncross-examination were reasonable. The Court concluded,\nafter reviewing the evidence submitted by Brand and the\nwitness’s mental health records, that any mention of the\nwitness’s bipolar disorder would “only be designed to\nconfuse the jury or to stigmatize him unfairly because of a\n‘mental problem’ without any countervailing probative\nvalue.” JA155. The District Court did not abuse its\ndiscretion in limiting Brand’s cross-examination on a topic\nthat would be far more prejudicial than probative. See\nTykarsky, 446 F.3d at 476–77 (“[T]he District Court acted\n\n\n 145\n\fwell within its discretion to restrict irrelevant and\nconfusing testimony.”).\n All of this is not to suggest that a witness’s mental\nhealth is always off limits. The appropriate course in any\ngiven case must be determined from the facts and\ncircumstances surrounding that case and the witness’s\nparticular condition. See United States v. George, 532 F.3d\n933, 937 (D.C. Cir. 2008) (“The days are long past when\nany mental illness was presumed to undermine a witness’s\ncompetence to testify. . . . [M]ental illness [is] potentially\nrelevant in a broad[] range of circumstances . . . . [But]\nsome indication is needed that a particular witness’s\nmedical history throws some doubt on the witness’s\ncompetence or credibility.”). Here, Brand failed to show,\nthrough mental health records or otherwise, any\nparticularized reason to doubt the credibility of the witness\nfor medical reasons.\n\n Brand states that the witness provided “the only\nevidence offered” on the intent element of his conspiracy\nconviction and that he should therefore be entitled to\nunrestricted cross-examination. Brand Br. 12 n.3. Yet no\nmatter the importance of a witness to any party, a district\ncourt may always place reasonable limits on cross-\nexamination to avoid “harassment, prejudice, confusion of\nthe issues, the witness’ safety, or interrogation that is\nrepetitive or only marginally relevant.” John-Baptiste, 747\nF.3d at 211 (citation omitted).\n\n\n 146\n\f We conclude that the District Court did not abuse\nits discretion in restricting the scope of Brand’s cross-\nexamination of the cooperating witness.\n\n X. The Government’s Cross-Appeal\n The jury convicted Fattah, Vederman, and Bowser\nof bank fraud, 18 U.S.C. § 134430 (Count 19) and making\nfalse statements to a financial institution, 18 U.S.C.\n§ 1014 31 (Count 20). In response to post-trial motions, the\nDistrict Court granted a judgment of acquittal on both\ncounts under Fed. R. Crim. P. 29, concluding that the\n\n30\n “Whoever knowingly executes, or attempts to execute,\na scheme or artifice . . . to defraud a financial institution\n. . . shall be fined not more than $1,000,000 or imprisoned\nnot more than 30 years, or both.” The definition of\n“financial institution” for purposes of § 1344 is set forth at\n18 U.S.C. § 20, and includes “a credit union with accounts\ninsured by the National Credit Union Share Insurance\nFund” and “a mortgage lending business (as defined in\nsection 27 of this Title).” 18 U.S.C. §§ 20(2), (10).\n31\n “Whoever knowingly makes any false statement or\nreport, or willfully overvalues any land, property or\nsecurity, for the purpose of influencing in any way the\naction of . . . a Federal credit union . . . any institution the\naccounts of which are insured by . . . the National Credit\nUnion Administration Board . . . or a mortgage lending\nbusiness . . . shall be fined not more than $1,000,000 or\nimprisoned not more than 30 years, or both.”\n 147\n\fevidence was insufficient to establish that the Credit\nUnion Mortgage Association (CUMA), the entity to whom\nFattah, Vederman, and Bowser made the false statements,\nis a “financial institution,” or, more specifically, a\n“mortgage lending business” as defined in 18 U.S.C. § 27.\nThe Government claims that, viewing the evidence in the\nlight most favorable to it, the District Court erred and that\nCUMA is, indeed, a “mortgage lending business.” We\nagree. Because the evidence is sufficient to support the\njury’s verdict, we will remand so Fattah and Vederman\nmay be resentenced on these charges.32\n\n A. CUMA is a Mortgage Lending Business\n In reviewing the District Court’s post-verdict\njudgment of acquittal under Rule 29 of the Federal Rules\nof Civil Procedure, we consider whether the evidence,\nwhen viewed in a light most favorable to the government,\nsupports the jury’s verdict. United States v. Dixon, 658\nF.2d 181, 188 (3d Cir. 1981). Our standard of review is the\nsame as that applied by the District Court, and we must\nuphold the jury’s verdict unless no reasonable juror could\naccept the evidence as sufficient to support the defendant’s\nguilt beyond a reasonable doubt. United States v.\nColeman, 811 F.2d 804, 807 (3d Cir. 1987).\n\n32\n Because the Government did not file an appeal as to\nBowser, the cross-appeal is limited to Fattah and\nVederman. The judgment of acquittal as to Bowser is\ntherefore unaffected by our ruling today.\n 148\n\f Initially, the grand jury’s indictment alleged that\nCUMA is a financial institution because it is federally\ninsured. JA302–03. At trial, however, the jury was\ninstructed that CUMA could qualify as a financial\ninstitution either because it is federally insured or because\nit is a “mortgage lending business.” See JA111, 401–02. A\n“mortgage lending business” is “an organization which\nfinances or refinances any debt secured by an interest in\nreal estate, including private mortgage companies and any\nsubsidiaries of such organizations, and whose activities\naffect interstate or foreign commerce.” 18 U.S.C. § 27.\n\n At trial, CUMA’s president and CEO, Eddie Scott\nToler, testified that CUMA is not federally insured.\nJA4235. The Government therefore attempted to prove\nthat CUMA is a “mortgage lending business” by\npresenting evidence that CUMA funds mortgages and then\nsells them in a secondary market.\n\n Toler also testified that CUMA is a “credit union\nservice organization”—a for-profit company owned by 48\ncredit unions, which serves small credit unions that do not\nhave the infrastructure or in-house expertise to handle\nmortgage loans themselves. JA4235. According to Toler,\n“[CUMA] exclusively provide[s] First Trust Residential\nMortgage loaning [sic] services, all the way from the\norigination of the mortgage loan through processing,\nunderwriting, closing and access to the secondary market\nwhere—and we’re selling the mortgage loan on the\nsecondary market.” JA4236–37. In jurisdictions in which\n\n 149\n\fCUMA is licensed, 33 CUMA holds the mortgage for a\nlimited period, generally from two to thirty days, and then\nsells the mortgage either to a partner credit union or on the\nsecondary market. JA4240.\n\n The District Court concluded that CUMA is not a\n“mortgage lending business” because “[t]he record is\ndevoid of any evidence that CUMA finances or refinances\nany debt.” JA113. Concluding that CUMA “simply is a\nloan processor for various credit unions which do the\nfinancing or refinancing,” id., the District Court ruled that\nCUMA’s “activity does not constitute the financing or\nrefinancing of any debt. CUMA is not the mortgagee. It is\nmerely selling the debt instrument to a third party.” JA114.\n We cannot agree with the District Court’s view of\nthe evidence. Toler testified that in “Maryland, D.C., and\nVirginia . . . all of the loans are closed in the name of\nCUMA.” JA4238–39. As Toler described it, CUMA\nborrows on a line of credit to fund the loan, and when the\nloan is sold, CUMA pays off its line of credit. JA4239–40.\nSo contrary to the District Court’s assessment, the\nevidence, viewed in a light most favorable to the\nGovernment, shows that CUMA is indeed the\nmortgagee—at least during the time from closing until the\nloan is sold to a partner credit union or on the secondary\nmarket. The fact that CUMA funds the closing and then\n\n33\n CUMA is licensed in Maryland, Washington, D.C., and\nVirginia. JA4238.\n 150\n\fholds the mortgage, even for a brief time, is sufficient to\nsupport a conclusion that CUMA is “an organization\nwhich finances or refinances any debt secured by an\ninterest in real estate.” 18 U.S.C. § 27.\n\n Fattah and Vederman attempt to refute the argument\nthat CUMA engages in financing mortgages by focusing\non Toler’s testimony that CUMA “doesn’t actually have\nany money to fund these mortgage loans.” JA4239; see\nFattah Reply Br. 38, Vederman Reply Br. 36. But Toler\ntestified that CUMA employs a credit line to borrow the\nfunds necessary to close on mortgages. See JA4239. That\nCUMA incurs debt to finance mortgages hardly\nundermines a conclusion that CUMA finances mortgages.\nIndeed, it is the very nature of modern banking that\nfinancial institutions do not hold cash reserves equal to the\nfull amount of their liabilities. See, e.g., Timothy C.\nHarker, Bailment Ailment: An Analysis of the Legal Status\nof Ordinary Demand Deposits in the Shadow of the\nFinancial Crisis of 2008, 19 Fordham J. Corp. & Fin. L.\n543, 561 (2014) (“[F]ractional reserve banking . . . is the\nde facto standard for all modern banks.”).\n\n Vederman also argues that, even if CUMA acts as a\nmortgage lending business in some transactions, it was not\nacting as a mortgage lending business in this transaction.\nVederman points to Toler’s testimony that, in a state in\nwhich CUMA is not licensed, the mortgage is closed in the\nname of a credit union. In such cases, the credit union, and\nnot CUMA, owns the mortgage for the short period before\n\n 151\n\fthe loan is sold on the secondary market. JA4241. CUMA\nis not licensed in the Commonwealth of Pennsylvania. See\nid. Thus, according to Vederman, CUMA was acting in its\ncapacity as a mortgage servicing company for Fattah’s\nvacation home purchase and did not—and could not—\nfinance Fattah’s mortgage. That would mean that CUMA\ncould not have been a victim of a crime against a financial\ninstitution in this instance: “When an entity is not\nfunctioning as a mortgage lender, the ‘pertinent federal\ninterest’ behind the statutes is not implicated.” Vederman\nReply Br. 38 (citation omitted).\n\n The Government responds that neither of the\nstatutes of conviction requires that the fraud or false\nstatement occur in connection with the same transaction\nthat places the entity within the definition of “financial\ninstitution.” Gov’t Fourth Step Br. 4. We agree with the\nGovernment.\n\n Both § 1344 and § 1014 protect entities that fall\nwithin the definition of “financial institution” and are\notherwise quite broad in their application. See Loughrin v.\nUnited States, 134 S. Ct. 2384, 2389 (2014) (interpreting\n§ 1344 as not requiring specific intent to defraud a bank);\nUnited States v. Boren, 278 F.3d 911, 914 (9th Cir. 2002)\n(“[Section 1014’s] reach is not limited to false statements\nmade with regard to loans, but extends to any application,\ncommitment or other specified transaction.”). Neither\nstatute is expressly limited in the manner that Vederman\nsuggests. Williams v. United States, 458 U.S. 279, 284\n\n 152\n\f(1982) (“To obtain a conviction under § 1014, the\nGovernment must establish two propositions: it must\ndemonstrate (1) that the defendant made a ‘false statement\nor report,’ . . . and (2) that he did so ‘for the purpose of\ninfluencing in any way the action of [a described financial\ninstitution] upon any application, advance, . . .\ncommitment, or loan.’ ”); United States v. Leahy, 445 F.3d\n634, 646 (3d Cir. 2006) (“The purpose of the bank fraud\nstatute is to protect the ‘financial integrity of [banking]\ninstitutions.’ ”) (citing S. Rep. No. 98-225, at 377 (1983),\nas reprinted in 1984 U.S.C.C.A.N. 3517), abrogated on\nother grounds by Loughrin, 134 S. Ct. at 2389.\n In support of his position, Vederman relies on\nUnited States v. Devoll, 39 F.3d 575 (5th Cir. 1994), in\nwhich the Fifth Circuit concluded that § 1014 (false\nstatements to a financial institution) is not intended to\ncapture fraud unrelated to an entity’s lending activities,\nand therefore held that it “applies only to actions involving\nlending transactions.” Id. at 580. The Fifth Circuit stated:\n [W]e are not persuaded that the statute\n imposes liability whenever a defendant’s\n false statement was intended to interfere with\n any activity of a financial institution; such a\n broad interpretation of section 1014\n presumably would encompass fraud or false\n representations having nothing to do with\n financial transactions, such as fraud in an\n employment contract or, for example, in a\n\n 153\n\f contract to provide goods or services for\n custodial care, premises repair, or renovation.\nId.\n\n Yet a majority of circuits, including our own, have\ndeclined to follow Devoll’s suggestion that § 1014 is\nrestricted to lending transactions. As the Ninth Circuit has\nheld, “we join at least six of our sister circuits—the First,\nThird, Fourth, Sixth, Seventh, and Tenth—in holding that\n18 U.S.C. § 1014 is not limited to lending transactions,\nand reject the minority rule to the contrary.” Boren, 278\nF.3d at 915. And even if we were to adopt Devoll’s narrow\nconstruction of § 1014 to lending transactions, that would\nnot resolve the more specific question of whether the\ndefrauded entity must be defined as a “mortgage lending\nbusiness” by virtue of the specific transaction in which the\nfalse statements arose.\n Recently, the Eighth Circuit addressed precisely\nthis issue. In United States v. Springer, 866 F.3d 949 (8th\nCir. 2017), that Court considered the defendant’s appeal\nfrom the district court’s denial of a Rule 29 motion on\ngrounds that GMAC, the entity defrauded, was not a\n“financial institution.” The Court upheld the district\ncourt’s determination that the evidence was sufficient to\nestablish that GMAC is in the mortgage lending business\nbecause there was testimony that “it had made hundreds or\nthousands of loans secured by mortgages in 2010 and 2011\nin states all across the country,” which established that its\nactivities affect interstate commerce. Id. at 953. It was not\n 154\n\fdeterminative that GMAC did not own the specific loan at\nissue in the case: “we discern no requirement in the\ndefinition of ‘mortgage lending business’ that the business\nown the particular loan in question; it need only finance or\nrefinance any debt secured by an interest in real estate, or,\nin other words, be in the interstate mortgage lending\nbusiness in general.” Id.\n\n In our view, the Eighth Circuit’s analysis is correct.\nWe therefore adopt that Court’s reasoning in Springer and\nconclude that it is of no moment that CUMA did not\nfinance the mortgage at issue in Fattah’s case. CUMA is a\n“mortgage lending business,” and that alone suffices to\nsupport the convictions under §§ 1014 and 1344.\n\n B. Sufficiency of the Evidence\n Finally, Vederman argues that, even if CUMA is a\nfinancial institution, the judgment of acquittal should\nstand because the Government did not put forth any\nevidence that he made a false representation to CUMA.34\nSpecifically, Vederman argues that the title to the Porsche\nwas actually changed to his name, making it a “true sale”\nas a matter of law, without regard to whether Fattah’s wife\n\n34\n Although Vederman presented this argument in his Rule\n29 motion, the District Court did not need to reach it in the\ncontext of Counts 19 and 20 because the Court granted the\nmotion on the ground that CUMA is not a financial\ninstitution. The District Court rejected the argument as to\nCounts 16, 17, and 18. See JA100–02.\n 155\n\fcontinued to retain possession. See United States v.\nCastro, 704 F.3d 125, 139 (3d Cir. 2013) (holding in\nanother context that “the government must be able to show\nthat [the defendant] made a statement to government\nagents that was untrue, and the government cannot satisfy\nthat burden by showing that the defendant intended to\ndeceive, if in fact he told the literal truth”); see also 75 Pa.\nCons. Stat. § 102 (defining “owner” as “[a] person, other\nthan a lienholder, having the property right in or title to a\nvehicle”).\n\n The Government responds that, regardless of\nwhether it is legally possible for one person to hold a title\nwhile a different person possesses the vehicle, the jury was\npermitted to consider all the circumstances in deciding\nwhether the Porsche sale was a sham. We agree.\n\n First, as the District Court observed, it was unclear\nas to whether the title had been properly executed under\nPennsylvania law. For instance, Fattah’s wife never\nappeared before a notary. 35 JA101. In addition, title 75,\nsection 1111(a) of the Pennsylvania Consolidated Statutes\nrequires that, “[i]n the event of the sale or transfer of the\nownership of a vehicle within this Commonwealth, the\nowner shall . . . deliver the certificate to the transferee at\n\n35\n Vederman argues that it is of no significance that the\nparties did not appear before a notary as the statute\nrequires, but he offers cases only from states other than\nPennsylvania to support this proposition.\n 156\n\fthe time of the delivery of the vehicle.” And, the transferee\nmust, within twenty days of the assignment of the vehicle,\napply for a new title. See 75 Pa. Cons. Stat. § 1111(b).\nNeither of these requirements was fulfilled. Finally,\nVederman never registered the Porsche in his name with\nthe Department of Motor Vehicles. See id.; JA4254.\n Second, and more importantly, even if the title had\nbeen properly transferred to Vederman, the title provisions\nof the Pennsylvania Motor Vehicle Code “were [not]\ndesigned to establish conclusively the ownership of an\nautomobile.” Weigelt v. Factors Credit Corp., 101 A.2d\n404, 404 (Pa. Super. Ct. 1953). Indeed, “[t]he purpose of\na certificate of title is not to conclusively establish\nownership in a motor vehicle, but rather to establish the\nperson entitled to possession.” Speck Cadillac-Olds, Inc.\nv. Goodman, 95 A.2d 191, 193 (Pa. 1953). Thus, a title\nprovides evidence of ownership; it is not dispositive of the\nissue. Wasilko v. Home Mut. Cas. Co., 232 A.2d 60, 61\n(Pa. Super. Ct. 1967).\n Vederman’s argument that the title in his name\nconstitutes conclusive evidence of ownership rests upon\nan erroneous conclusion that the jury was prohibited from\nconsidering all the circumstances of the transfer. As the\nDistrict Court observed, though, Pennsylvania’s\nCommonwealth Court has held that “[w]hether a\ntransferor has transferred ownership of a motor vehicle to\na transferee is a factual determination to be made by the\ncourt below.” Dep’t. of Transp. v. Walker, 584 A.2d 1080,\n\n 157\n\f1082 (Pa. Commw. Ct. 1990). Thus, the signed certificate\nof title was appropriately treated as one piece of evidence\nfor the jury to consider in assessing the validity of the\nvehicle transfer. Considered in the light most favorable to\nthe Government, the totality of the evidence is sufficient\nto support the jury’s conclusion that the Porsche sale was\na sham.\n\n XI. Prejudicial Spillover\n Finally, Fattah, Vederman, Nicholas, and Brand\neach contend that their convictions on various counts\nresulted from prejudicial spillover. We are not persuaded.\n We exercise plenary review over a district court’s\ndenial of a claim of prejudicial spillover, United States v.\nLee, 612 F.3d 170, 178–79 (3d Cir. 2010), and we apply a\ntwo-step test when reviewing such a claim. United States\nv. Wright, 665 F.3d 560, 575 (3d Cir. 2002). First, a court\nmust consider “whether the jury heard evidence that would\nhave been inadmissible at a trial limited to the remaining\nvalid count[s].” Id. (quoting United States v. Cross, 308\nF.3d 308, 317 (3d Cir. 2002)). The second step requires\nthat we “ask whether that evidence (the ‘spillover\nevidence’) was prejudicial.” Id. We consider four factors:\n“whether (1) the charges are intertwined with each other;\n(2) the evidence for the remaining counts is sufficiently\ndistinct to support the verdict on these counts; (3) the\nelimination of the invalid count [will] significantly\nchange[] the strategy of the trial; and (4) the prosecution\nused language of the sort to arouse a jury.” Id. (quoting\n 158\n\fUnited States v. Murphy, 323 F.3d 102, 118 (3d Cir.\n2003)); see also United States v. Pelullo (Pellulo II), 14\nF.3d 881, 898–99 (3d. Cir. 1994). These four factors are\nconsidered in a light “somewhat favorable to the\ndefendant.” Wright, 665 F.3d at 575 (quoting Murphy, 323\nF.3d at 122); see also Gov’t Br. 198 (same).\n\n A. Fattah’s Claim of Prejudicial Spillover\n Fattah argues that he suffered prejudicial spillover\non the remaining counts of conviction in light of (1)\nevidence pertinent to the alleged Vederman bribery\nschemes that is now arguably inadmissible under\nMcDonnell; and (2) “the government’s flawed RICO\nconspiracy theory.” Fattah Br. 50, 64. Fattah’s argument\nis undercut substantially because of our determination that\nMcDonnell requires a new trial for Counts 16, 17, 22, and\n23 and our decision to affirm the RICO conspiracy\nconviction. The only possible spillover left to consider is\nthe evidence pertaining to Fattah’s arranging a meeting\nbetween Vederman and the U.S. Trade Representative,\nRon Kirk, which in light of McDonnell is now arguably\ninadmissible.36\n\n The evidence of the Kirk meeting admitted during\nthis five-week trial was limited. Although this evidence\n\n36\n Nothing in this opinion is intended to foreclose the\npossibility that evidence of the Kirk meeting may be\nadmissible on retrial for some purpose other than as proof\nof an official act.\n 159\n\fwas part of the Government’s proof as to both the RICO\nand the bribery related charges, there is more than\nsufficient—and distinct —evidence to support Fattah’s\nconviction on all the other counts. In our view, eliminating\nany evidence of the Kirk meeting would not have altered\nthe strategy of the trial, nor should it significantly change\nthe strategy for any new trial that may be held. Because\nFattah has not pointed us to any argument by the\nprosecution relating to this meeting that could have\ninflamed the jury, we conclude that Fattah’s prejudicial\nspillover claim fails. Like the District Court, we presume\nthat the jury followed the Court’s instructions to consider\nand weigh separately the evidence on each count as to each\ndefendant and not to be swayed by evidence pertaining to\nother defendants. 37\n\n B. Vederman’s Assertion of Prejudicial Spillover\n Because the District Court acquitted Vederman of\nthe RICO charge, Vederman argues that he was “severely\nprejudiced by the presentation to the jury of a legally\nflawed racketeering conspiracy charge,” and as a\nconsequence his bribery and money laundering\n\n37\n We likewise reject Brand’s prejudicial spillover\narguments. See Brand Br. 6 (“Brand adopts the significant\nissue advanced by his co-appellant pursuant to Fed. R.\nApp. P. 28(i) that improper jury instructions and the\nresulting spillover of related improperly admitted\nevidence and argument unfairly prejudiced Brand.”).\n 160\n\fconvictions should be overturned. Vederman Br. 46. In\nresponse to the Government’s appeal of the District\nCourt’s Rule 29 acquittal on Counts 19–20 involving\nCUMA, Vederman asserts that these two counts also were\naffected by spillover evidence because the Government’s\ntheory tied the bribery charges to the actions taken to\ndefraud CUMA. In that we are vacating Vederman’s\nconvictions of Counts 16–18 and 22–23 based on\nMcDonnell and remanding for further proceedings, we\nneed address only Vederman’s argument of prejudicial\nspillover as it relates to the charges involving CUMA in\nCounts 19–20, charges that we will reinstate.\n The District Court’s acquittal of Vederman on the\nRICO count establishes that step one of the Wright\nspillover test has been met. “[T]he jury heard evidence that\nwould have been inadmissible at a trial limited” to the\nbribery and CUMA-related counts. Wright, 665 F.3d at\n575 (quoting Cross, 308 F.3d at 317).\n\n Wright’s second step requires “ask[ing] whether\nthat evidence (the ‘spillover evidence’) was prejudicial.”\nId. Vederman submits that the RICO, bribery, and CUMA-\nrelated charges were intertwined “in that the acts relating\nto the alleged bribery scheme were also charged as\n‘predicates’ under RICO.” Vederman Br. 49. We disagree.\n\n To be sure, the RICO, bribery, and CUMA Counts\nare related to one another. But in this instance, mere\nrelatedness is not enough to demonstrate the foundation\nnecessary for spillover. This is so because the bribery\n 161\n\fcharges were a predicate to the RICO charge. In other\nwords, the jury had to determine if Vederman was guilty\nof bribery, and the jury then used that “predicate” to\nconsider whether he was also guilty of the RICO\nconspiracy. Thus, the necessarily tiered structure of the\nquestions presented to the jury refute Vederman’s\nargument that the counts were intertwined.\n\n That the bribery charges were predicates for the\nRICO conspiracy further demonstrates that the “evidence\nfor the different counts was sufficiently distinct to support\nthe verdict on other separate counts.” Pelullo II, 14 F.3d at\n898. Regardless of the evidence pertaining solely to the\nRICO conviction, the evidence supporting both the bribery\ncharges and the charges involving CUMA in Counts 19–\n20 would have remained the same.\n\n The next factor we address is “whether the\nelimination of the count on which the defendant was\ninvalidly convicted would have significantly changed the\n[defendant’s] strategy of the trial.” Id. As Vederman\nargues, “the RICO charge interfered with Vederman’s\ncentral defense to the bribery charge—that his gestures\ntoward Fattah ‘were motivated purely by friendship.’ ”\nVederman Reply Br. 28 (citing Gov’t Br. 200). In other\nwords, the “RICO count made it dangerous to unduly\nemphasize [Vederman’s] close friendship” with Fattah. Id.\nFrom Vederman’s perspective, “a bribery-only trial would\nhave reduced this danger and allowed a freer presentation\nof the defense.” Id.\n\n 162\n\f It is quite likely that Vederman’s claim of friendship\nwould have been less risky as a litigation strategy if he had\nnot been facing a RICO charge. But Vederman\nnevertheless chose to take that risk and fully presented his\nfriendship argument to the jury. Moreover, while\nVederman’s reliance on friendship might have helped him\ndefend against the bribery charges, that friendship would\nnot have altered the evidence pertaining to Counts 19–20\ninvolving CUMA. Whether done for friendship or some\nother reason, submitting fraudulent information to a\nfinancial institution is unlawful.\n\n Finally, we “examine the charges, the language that\nthe government used, and the evidence introduced during\nthe trial to see whether they are ‘of the sort to arouse a\njury.’ ” Pelullo II, 14 F.3d at 899 (quoting United States v.\nIvic, 700 F.2d 51, 65 (2d Cir. 1983)). Vederman points out\nthat Fattah was presented as “a backslapping, corrupt party\nboss,” with “predictable spillover to his friend and\nassociate, Vederman.” Vederman Br. 50 (quoting United\nStates v. Murphy, 323 F.3d 102, 118 (3d Cir. 2003)). But\nthis description was of Fattah, not Vederman. Vederman\ncites other examples of prejudicial, pejorative language in\nthe Government’s closing arguments. At one point, the\nGovernment referred to “conspirators engaged in what can\nonly be described as a white collar crime spree from\nPhiladelphia all the way to Washington, D.C.” and\npromised “to untangle the webs of lies and deception that\nthese conspirators spun.” Vederman Br. 51 (quoting\nJA5295, 5297). Whatever rhetorical flair these words\n 163\n\fcontained, they did not obscure the evidence which\nindependently supported the convictions for bank fraud at\nCount 19 and for making false statements to CUMA at\nCount 20. Accordingly, because we presume that the jury\nfollowed the District Court’s instruction to consider and to\nweigh separately the evidence on each count and as to each\ndefendant, and because the evidence supporting the\nCUMA-related charges in Counts 19–20 is sufficiently\ndistinct from the RICO conspiracy, we conclude that\nVederman’s spillover argument is unavailing.38\n\n XII. Conclusion\n We will vacate the convictions of Chaka Fattah, Sr.\nand Herbert Vederman as to Counts 16, 17, 18, 22, and 23.\n\n38\n Nicholas adopted “pertinent portions” of the prejudicial\nspillover arguments advanced by Vederman and Fattah.\nNicholas Br. 65. Her spillover claim has no more merit\nthan theirs. Nicholas’s involvement in the RICO\nconspiracy was distinct from the bribery charges, which\ndid not unfairly influence the other counts. As to\nNicholas’s assertion that the NOAA charges did not\nbelong in the indictment and should have been tried\nseparately, we fail to see how this relates to a claim of\nprejudicial spillover. To the extent it challenges the\nDistrict Court’s denial of Nicholas’s motion for a\nseverance, Nicholas has failed to provide legal support for\nsuch a contention. See Fed. R. App. P. 28(a)(8)(A); United\nStates v. Irizarry, 341 F.3d 273, 305 (3d Cir. 2003).\n 164\n\fFattah and Vederman may be retried on these counts\nbefore a properly instructed jury. We will also reverse the\nDistrict Court’s judgment of acquittal on Counts 19 and\n20. The convictions of Chaka Fattah, Sr. and Herbert\nVederman will be reinstated, and the case will be\nremanded for sentencing on those counts. In all other\nrespects, the judgments of the District Court will be\naffirmed.\n\n\n\n\n 165\n[END_CASE]", "role": "user" } ]
8,443,856
United States v. Karen NICHOLAS
United States v. Nicholas
2019-01-16
No. 16-4410
U.S. Court of Appeals for the Third Circuit
{"judges": "Smith", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415283/", "author_raw": ""}]}
SMITH
SMITH
0
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443856/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Karen NICHOLAS\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,582,573
UNITED STATES of America, Appellant v. Raymont WRIGHT
United States v. Raymont Wright
2019-01-17
17-1972
U.S. Court of Appeals for the Third Circuit
{"judges": "Shwartz, Nygaard", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887874/", "author_raw": ""}, {"author": "", "type": "040dissent", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887875/", "author_raw": ""}, {"type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014. 1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13", "author": "SHWARTZ, Circuit Judge."}, {"type": "dissent", "author": "Our", "text": "Our dissenting colleague says that our approach\ndeprives the court from taking action “when warranted to\nprotect the institutional integrity of the judiciary.” Dissent at\n3. We disagree. This approach recognizes a court’s role in our\ntripartite system of government and ensures that a court\nintercedes when proceeding would violate the Constitution.\nFurthermore, our approach does not preclude a court from\nending a case where the evidence is insufficient or the conduct\nof the prosecution is improper.\n\n\n\n\n 22\n\nNo. 17-1972, United States of America v. Raymont Wright"}, {"author": "NYGAARD, Circuit Judge, dissenting", "type": "dissent", "text": "NYGAARD, Circuit Judge, dissenting\n\n This appeal presents us with two issues: First, does a\ndistrict court possess the inherent power to dismiss an\nindictment after serial hung juries, and second, did the\nDistrict Court here abuse its discretion by dismissing this\nindictment after two of them. I answer yes to the first and no\nto the second. Because I view this to be a matter of\nsubstantial importance, I must respectfully dissent. 1\n\n As the majority notes, twice now, the Government has\ntried Raymont Wright for a violation of federal law: being a\nfelon in possession of a firearm. 2 Twice now, the\nGovernment has done so on the basis of essentially the same\nevidence at trials presided over by the same District Court.\nAnd twice now, two different juries could not reach a verdict.\nThus, when the Government announced its intention to put\nWright on trial for the third time, the District Court was\nskeptical. It asked for briefing on whether it possessed the\ninherent power to prohibit the Government from taking a\n\n1\n Whether the District Court had the inherent power to\ndismiss the indictment is a legal question. We employ a\nplenary standard of review to that issue. See United States v.\nSchiff, 602 F.3d 152, 161 (3d Cir. 2010) (citing United States\nv. Scott, 223 F.3d 208, 210 (3d Cir. 2000)). Whether the\nDistrict Court appropriately exercised this power is reviewed\nfor an abuse of discretion. Link v. Wabash R.R. Co., 370 U.S.\n626, 633 (1962).\n2\n See 18 U.S.C. § 922(g).\n\nthird turn, and if it did, whether the court should use that\npower. 3 After hearing from both sides, the District Court\nconcluded that its inherent power applied to this\ncircumstance. It then exercised its discretion to dismiss the\nindictment.\n\n Neither the Government nor the majority disputes that\ndistrict courts have the inherent authority to dismiss\nindictments under at least some circumstances. Citing to\nUnited States v. Hasting, 4 however, the majority cabins that\nauthority to those instances in which there is evidence of\nprosecutorial misconduct. In my view, in so doing, the\nmajority conflates and confuses the various powers of the\ncourt. And it also hobbles the court’s discretion to probe the\nimpact on the fair administration of justice of those\nprosecutorial decisions that sit outside the definition of bad\nconduct but still pose—or threaten to pose—real institutional\nharm.\n\n The executive office inheres prosecutors with the\npower to bring a case to trial. The judicial office, on the other\nhand, inheres the court with the power to end a case. 5 Both\n\n3\n The District Court ordered the parties to “file cross briefs\nstating their position regarding whether the Court, through an\nexercise of its inherent authority, should prohibit or permit a\nsecond re-trial in this case.” United States v. Wright, No. 14-\ncr-292, 2017 WL 1179006, at *1 (W.D. Pa. 2017).\n4\n 461 U.S. 499, 505 (1983).\n5\n See Young v. U.S. ex rel. Vuitton et Fils S.A., 481 U.S. 787,\n816 (1987)(Scalia, J. concurring)(“The judicial power is the\npower to decide, in accordance with law, who should prevail\nin a case or controversy. See Art. III, § 2. . . . [S]ince the\n\n\n\n\n 2\n\noffices share a responsibility to safeguard the overall integrity\nof the judicial process. But when a prosecutor decides to\nproceed with another trial in the aftermath of multiple\nmistrials, who but the court is empowered to question the\nimpact of the prosecutor’s discretion on the fair\nadministration of justice, particularly when the court has\nconcerns that the proceedings—and the institution—will be\ntainted by the abuse of jury shopping? It could be argued that\ntwo mistrials may not in some instances be enough to inflict\nserious institutional damage. But, the majority’s combined\nreliance on Dietz v. Bouldin 6 and Fed. R. Crim. P. 31(b)(3) to\nallow the prosecutor to bring an unlimited number of retrials,\nso long as she or he does not stray into the realm of “illegal\nconduct,” provides the prosecutor with an unchecked power.\nThis poses a threat to the integrity of the judiciary and\ncontradicts the inherent responsibility and authority vested in\nthe judiciary by the framers of the Constitution. Thus, it is\nthe majority’s decision—and not the District Court’s exercise\nof its inherent authority—that violates the separation of\npower principles on which the majority relies. We must\naffirm that our trial court judges have the discretion,\noriginating in the court’s inherent power, to take proper\naction when warranted to protect the institutional integrity of\nthe judiciary.\n\n Here, the District Court mindfully struck the balance\nthat is necessary anytime the power of the court and the\n\n\nprosecution of law violators is part of the implementation of\nthe laws, it is—at least to the extent that it is publicly\nexercised—executive power, vested by the Constitution in the\nPresident.”) (footnote omitted)).\n6\n 136 S. Ct. 1885, 1892 (2016).\n\n\n\n\n 3\n\npower of the prosecutor intersect. Drawing from factors set\nout in State v. Abbati, 7 the District Court identified and\ninvestigated a circumstance that it identified as harmful to the\ninstitution and to the defendant: jury shopping. It also took\nnote of the impact of serial retrials on the defendant. It then\nproperly dismissed the indictment. Its use of the court’s\ninherent discretion did not violate the separation of powers\ndoctrine. To the contrary, it gave definition and substance to\nit.\n\n I.\n\n Some review is appropriate to illuminate how and\npossibly why I believe the majority confuses the court’s\nvarious powers.\n\n A.\n\n Federal courts operate within a constitutional system\nthat enumerates the powers of each branch of government, as\nset forth in the founding document. Article I restrains\ncongressional power to those “legislative Powers granted\nherein.” 8 By comparison, Article II vests the President with\n“the executive Power” without further description, limitation,\nor restriction. 9 Analogous to Article II, Article III conveys\nwithout restriction or limitation the “judicial Power” to\nfederal courts. 10 Accordingly, the Supreme Court has—since\nat least 1812—recognized that “[c]ertain implied powers must\n\n7\n 493 A.2d 513, 521-22 (N.J. 1985).\n8\n U.S. Const. art. I, § 1.\n9\n U.S. Const. art. II, § 1.\n10\n U.S. Const. art. III, § 1.\n\n\n\n\n 4\n\nnecessarily result to our Courts of justice from the nature of\ntheir institution.” 11 “The moment the courts of the United\nStates were called into existence and invested with\njurisdiction over any subject, they became possessed of”\ninherent authority. 12\n\n Moreover, two bedrock purposes of the Constitution—\nchecking the actions of the states and ensuring that Congress\nand the Executive do not overstep their boundaries—require a\nfederal judiciary that exercises its own independent judicial\npower. That is, it would be impossible for federal courts to\ndischarge these vital duties if they lacked some inherent\npower beyond the reach of the Executive or the legislature. I\nthink of it this way: the elaborate measures set out in the\nConstitution to protect the independence of the judiciary (life\ntenure, removal from office only through impeachment, no\ndecrease in salary during a judge’s tenure, for example)\nwould be meaningless if there were not some inherent,\nunimpeachable power vested solely in the federal courts.\n\n In Eash v. Riggins Trucking Inc., 13 we defined inherent\npower as vesting in federal courts upon their creation and as\nnot deriving from any statute. In this sense, the “judicial\npower” given to the federal courts by Article III of the\nConstitution is the “power to decide, in accordance with law,\nwho should prevail in a case or controversy.” 14 No matter the\ndescription, this power is intrinsic to the judicial office and\n\n11\n United States v. Hudson, 11 U.S. (7 Cranch) 32, 34 (1812).\n12\n Ex parte Robinson, 86 U.S. 505, 510 (1873) (speaking of\nthe inherent contempt power).\n13\n 757 F.2d 557, 561 (3d Cir. 1985) (en banc).\n14\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n\n\n\n\n 5\n\ncannot be inhibited by any rule or act of Congress. As we\nhave recognized, the boundaries of this power are often\n“nebulous” and “shadowy,” 15 and “it is not always possible to\ncategorize inherent power.” 16 Yet, we have an outline.\n\n In Eash, we identified three main classes or categories\nof inherent power: 1) inherent powers based in Article III,\nthat is, the power of a lower federal court to decide a case\nover which it has jurisdiction; 2) those powers “necessary to\nthe exercise of all others,” 17 and 3) powers that include those\nreasonably useful to achieve justice, which are “necessary\nonly in the practical sense of being useful.” 18 Focusing on the\nfirst category, the inherent power to decide a case is “so\nfundamental to the essence of a court as a constitutional\ntribunal that to divest the court of absolute command within\nthis sphere is really to render practically meaningless the\nterms ‘court’ and ‘judicial power.’” 19 In other words, powers\n\n15\n Eash, 757 F.2d at 561 (citation omitted).\n16\n Id. at 562.\n17\n Id. (quoting Roadway Express, Inc., v. Piper, 447 U.S. 752,\n764 (1980)).\n18\n Id. at 563; see also Am. Civil Liberties Union v. Holder,\n673 F.3d 245, 255-56 (4th Cir. 2011) (applying Eash factors);\nIn re Stone, 986 F.2d 898, 901-02 (5th Cir. 1993) (per\ncuriam) (adopting Eash factors). In Chambers v. NASCO\nInc., the Supreme Court was urged to adopt our approach to\ninherent powers. But the Court held that it “ha[d] never so\nclassified the inherent powers and . . . ha[d] no need to do so\nnow.” 501 U.S. 32, 47 n.12 (1991).\n19\n Eash, 757 F.2d at 562. The third aspect of a court’s\ninherent power is its authority to employ persons or\ninstruments not connected with the court, such as experts and\n\n\n\n\n 6\n\nin this category make a court a court; they are encoded into\nthe judiciary’s DNA. Courts have referred to this power as a\ncourt’s “irreducible inherent authority” 20 and “the core\nArticle III power.” 21 It is nothing less than our ability to\ndecide a case over which we have jurisdiction, without\ninterference by Congress or the Executive. 22\n\n Drawing from this, when I refer to a district court’s\ninherent power, I mean a ‘“[c]ertain implied power[] [that]\nmust necessarily result to our Courts of justice from the\nnature of their institution,’ [a] power[] ‘which cannot be\ndispensed with in a Court, because they are necessary to the\nexercise of all others.’” 23 It is “grounded in the separation of\npowers concept,” since to deny it and yet maintain an\nindependent judiciary “is a self-contradiction.” 24\n\n However, that is not to say that the court operates\nsolely outside the realm of legislatively granted judicial\n\n\nauditors, to assist in its decision-making function. This facet\nof inherent power is not in play here.\n20\n Id.\n21\n Am. Civil Liberties Union v. Holder, 673 F.3d at 256.\n22\n United States v. Klein, 80 U.S. (13 Wall.) 128, 147 (1871),\nEash, 757 F.2d at 562 (noting that courts may exercise this\ntype of inherent power despite legislation to the contrary); see\nalso Michaelson v. United States ex rel. Chicago, St. P., M. &\nO. Ry. Co., 266 U.S. 42, 64 (1924) (acknowledging that the\nConstitution vests courts with some powers unalterable by\nlegislation).\n23\n Chambers, 501 U.S. at 43 (quoting Hudson, 11 U.S. (7\nCranch) at 34.).\n24\n Eash, 757 F.2d at 562.\n\n\n\n\n 7\n\npowers. 25 In fact, the categorization scheme in Eash was\nintended largely as a means of explaining the relationship\nbetween inherent judicial powers and legislatively granted\njudicial powers. 26 It is here that I believe the majority’s\nanalysis strays.\n\n B.\n\n The majority, the briefs, and the discussion at oral\nargument reveal what has become a commonplace but\nimprecise conflation of the terms “inherent power” and\n“supervisory power.” 27 The Government, while referencing\nthe District Court’s “inherent power,” also referred to the\ncourt’s “supervisory power,” and its “inherent supervisory\njudicial authority.” 28 The Appellee covers the entire panoply,\nciting the District Court’s “supervisory authority,” its\n\n\n25\n See Hudson, 11 U.S. (7 Cranch) at 33.\n26\n See In re Tutu Wells Contamination Litig., 120 F.3d 368,\n384 n.14 (3d Cir. 1997), overruled on other grounds by\nCunningham v. Hamilton County, Ohio, 527 U.S. 198 (1999).\n27\n In Eash, we noted that “[t]he conceptual and definitional\nproblems regarding inherent power . . . have bedeviled\ncommentators for years,” 757 F.2d at 561, and that “those\ncases that have employed inherent power appear to use that\ngeneric term to describe several distinguishable court\npowers,” id. at 562. We also noted that “this lack of\nspecificity [has been compounded by courts] rel[ying] . . . on\nprecedents involving one form of power to support the court’s\nuse of another.” Id.\n28\n E.g., Appellant’s Br. at 13, 16; Appellant’s Reply Br. at 2,\n14.\n\n\n\n\n 8\n\n“supervisory power,” and its “inherent power.” 29 At times,\nwe too have been guilty of adding to the confusion. 30 The\nerroneous interchangeability of these terms clouds an\nimportant distinction that is crucial to this appeal: the\ndifference between inherent judicial powers and legislatively\ngranted judicial powers. 31 As noted supra, inherent “judicial\npower” is given to the federal courts by Article III of the\nConstitution. 32 Through this grant, federal courts receive the\n“power to decide, in accordance with law, who should prevail\nin a case or controversy.” 33 The merging of the terms\n“inherent” and “supervisory” likely has its genesis in the fact\nthat some inherent powers are supervisory in function, such\nas a federal court’s inherent power “to supervise the\nadministration of criminal justice.” 34\n\n29\n E.g., Appellee’s Br. at 22, 26.\n30\n See, e.g., United States v. Accetturo, 783 F.2d 382, 396 (3d\nCir. 1986) (Sloviter, J., dissenting) (speaking of our “inherent\nsupervisory power”); see also United States v. Watkins, 339\nF.3d 167, 180 (3d Cir. 2003) (Nygaard, J., concurring)\n(referring to both a court’s supervisory power and inherent\npower to dismiss a case under Fed. R. Crim. P. 48(b)).\n31\n In re Tutu Wells Litig., 120 F.3d at 384 n. 14.\n32\n See U.S. Const. art. III, § 1.\n33\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n34\n United States v. Payner, 447 U.S. 727, 735 n.7 (1980)\n(quotation marks omitted); see also Sara Sun Beale,\nReconsidering Supervisory Power in Criminal Cases;\nConstitutional and Statutory Limits of the Federal Courts, 84\nColum. L. Rev. 1433, 1433-34, 1465, 1470 (1984)\n(identification of Article III “judicial power,” not\ncongressional acts, as the source of the Supreme Court’s\nsupervisory authority).\n\n\n\n\n 9\n\n However, unlike inherent powers, a court’s\nsupervisory authority may come from, and can be limited by,\nacts of Congress or a court’s own rules. 35 Supervisory power\noften speaks to the power “to mandate ‘procedures deemed\ndesirable from the viewpoint of sound judicial practice.’” 36 A\ncourt’s use of supervisory power can usually be classified in\none of three ways. First, supervisory power can refer to an\nappellate court’s supervision of a district court, through the\nimposition of procedures in addition to those already imposed\nby federal statute or constitutional provision. 37 We have, for\nexample, relied on our supervisory power over district courts\nto review the application of local rules of practice and\nprocedure. 38 We have also used our supervisory power to\n\n\n\n\n35\n See, e.g., McNabb v. United States, 318 U.S. 332, 340-41\n(1943); Hasting, 461 U.S. at 505.\n36\n United States v. Moreno, 809 F.3d 766, 780 (3d Cir. 2016)\n(quoting Thomas v. Arn, 474 U.S. 140, 146-47 (1985)).\n37\n See, e.g., Castro v. United States, 540 U.S. 375, 384 (2003)\n(instructing district courts to notify pro se litigants about\nconsequences of re-characterizing motions as ones seeking\nrelief under 28 U.S.C. § 2255); Thiel v. S. Pac. Co., 328 U.S.\n217, 225 (1946) (announcing a new rule for the composition\nof federal juries); Dunbar v. Triangle Lumber & Supply Co.,\n816 F.2d 126, 129 (3d Cir. 1987) (prescribing procedures for\nmotions to dismiss based on the conduct of a litigant’s\ncounsel); United States v. Bazzano, 570 F.2d 1120, 1137-38\n(3d Cir. 1977) (requiring district courts to state reasons for a\ncriminal sentence).\n38\n See United States v. Wecht, 484 F.3d 194, 204-05 (3d Cir.\n2007).\n\n\n\n\n 10\n\nprohibit certain jury instructions in the district courts 39 and to\nreview attorney-client fee arrangements. 40 Second, Courts—\nboth trial and appellate—also refer to their “supervisory\npower” when meaning their power to supervise pending\nlitigation. 41 They can, for example, seal and unseal records, 42\nreassign a case to a different judge on remand, 43 or disqualify\nan attorney on ethical grounds. 44 Lastly, the power of a\nfederal court to supervise law enforcement officials can also\nbe what a court intends when it speaks of its “supervisory\n\n\n\n\n39\n See United States v. E. Med. Billing Inc., 230 F.3d 600,\n607-12 (3d Cir. 2000).\n40\n See Ryan v. Butera, Beausang, Cohen & Brennan, 193 F.3d\n210, 214 (3d Cir. 1999).\n41\n See, e.g., Carlisle v. United States, 517 U.S. 416, 425-26\n(1996) (acknowledging “supervisory power” of district courts\nover litigation before them).\n42\n See, e.g., Hagestad v. Tragesser, 49 F.3d 1430, 1434 (9th\nCir. 1995).\n43\n See Gov’t of the Virgin Islands v. Walker, 261 F.3d 370,\n376 (3d Cir. 2001) (noting that, “[a]lthough it is the standard\npractice in the district courts and in this circuit that a case on\nremand is assigned to the judge who originally heard it, we\ncan, in the exercise of our supervisory power, reassign this\ncase to a different judge upon remand.”) (quotation marks\nomitted).\n44\n In re Grand Jury Investigation, 447 F. Supp. 2d 453, 456-\n57 (E.D. Pa. 2006) (collecting cases); see also United States\nv. Moreno, 809 F.3d at 780 (summarizing supervisory\nauthority).\n\n\n\n\n 11\n\npower.” 45 These powers broadly ensure that pending cases\nare managed uniformly and efficiently.\n\n I concede that the boundary between supervisory\nauthority that is inherent to the court and that which is granted\nby the legislature can, at times, be difficult to identify.\nHowever, these difficulties are irrelevant to this case because\nI conclude that the District Court here acted pursuant to its\ninherent power and not to any authority conferred by any\nstatute or rule. The District Court’s action was not\nundertaken in supervision of pending litigation—two trials\nwere already concluded and a potential third trial had not yet\nbegun. Nor was it exercised according to a rule of procedure\nor practice newly announced by an appellate tribunal.\nMoreover, its action was not a response to any prosecutorial\nmisconduct or request from Wright to dismiss the indictment.\nThere is simply no basis to conclude that the inherent power\nthat the District Court exercised in this case derived from any\nlegislative grant.\n\n To the contrary, the specific power under review here\nis the power to dismiss an indictment after two mistrials\nbecause of deadlocked juries in each instance. This power\nfalls within Eash’s first category of power because it is an\ninherent power to resolve a case. A court, by its nature, must\nbe able to dismiss with prejudice actions brought before it,\njust as it must have the power to decide cases and enter\n\n45\n See, e.g., United States v. Thompson, 772 F.3d 752, 763 (3d\nCir. 2014). For a comprehensive discussion of the origins\nand uses of supervisory power, see Amy Coney Barrett, The\nSupervisory Power of the Supreme Court, 106 Colum. L. Rev.\n324, 330 (2006).\n\n\n\n\n 12\n\njudgments. 46 Such exercises of power are fundamental to the\nessence of a court. Were they not, the judicial system simply\ncould not function. 47\n\n The inherent power to dismiss is “of ancient origin,\nhaving its roots in judgments of nonsuit and non prosequitur\nentered at common law,” and so is a power that is part of the\nvery nature of the judicial institution. 48 It is incidental and\nnecessary to the fair and efficient operation of the courts. 49\nIndeed, “the power to dismiss exists in many situations. For\nexample, a district court has the inherent power to dismiss sua\nsponte for lack of jurisdiction, or under the doctrine of forum\nnon conveniens.” 50 Because the power to resolve a case by\ndismissing an indictment (in a criminal action) or a complaint\n(in a civil action) is fundamental to the essence of a court of\njustice, it cannot be interfered with. Indeed, as two\ncommentators have explained, “McNabb, other Supreme\n\n46\n We have also noted that our power to remand is a subset of\nthe inherent power to dismiss a case. See Bradgate Assocs.,\nInc. v. Fellows, Read & Assocs., Inc., 999 F.2d. 745, 750 n.4\n(3d Cir. 1993).\n47\n See, e.g., Fitzgerald v. First E. Seventh St. Tenants Corp.,\n221 F.3d 362, 363-364 (2d Cir. 2000) (holding a district court\nhas the inherent power to dismiss a case, sua sponte, if it\ndetermines that the action is frivolous or the court lacks\njurisdiction over the matter).\n48\n Link, 370 U.S. at 630.\n49\n See, e.g., Bowers v. Nat’l Collegiate Athletic Ass’n, 564 F.\nSupp. 2d 322, 333 (D.N.J. 2008) (citing Derzack v. County of\nAllegheny, 173 F.R.D. 400, 411 (W.D. Pa. 1996), aff’d\nwithout op., 118 F.3d 1575 (3d Cir. 1997)).\n50\n In re Prevot, 59 F.3d 556, 565-66 (6th Cir. 1995).\n\n\n\n\n 13\n\nCourt cases, and an analysis of several lower court opinions\naddressing this precise issue should sufficiently dispel any\nnotion that the federal courts lack the power to bar repeated\nattempts to obtain a conviction” following serial mistrials.51\nThus, the District Court’s action here was well within the\nboundaries of its inherent power.\n\n Therefore, the majority’s conclusion that “inherent\nauthority,” “supervisory power,” and “supervisory authority”\nall refer to the same thing (while understandable given the\nrampant muddled references that persist) ultimately misses\nthe point. The power at issue here is the inherent power of\nthe court to decide a case: a power that is limited by the\nboundaries of reason and discretion and is subject to appellate\nreview for abuse. It is not subject to the power of Congress\nor the Executive.\n\n II.\n\n There is no dispute that district courts have the\ninherent power to dismiss indictments in at least some\ncircumstance. The majority nevertheless concludes that the\nDistrict Court lacked the power to do so in this case. The\nmajority reaches that conclusion for three principal reasons,\nbut none withstands scrutiny.\n\n A.\n\n51\n Michael A. Berch & Rebecca White Berch, The Power of\nthe Judiciary to Dismiss Criminal Charges After Several\nHung Juries: A Proposed Rule to Control Judicial Discretion,\n30 Loy. L.A. L. Rev. 535, 543 & nn. 42-43 (1997) (collecting\ncases).\n\n\n\n\n 14\n\n First, the majority agrees with the Government’s\nargument that the District Court’s dismissal violated the\nSeparation of Powers Doctrine. I agree that the District\nCourt’s dismissal implicates the separation of powers. But its\nactions were in furtherance—not in violation—of the\ndoctrine. The separation of powers doctrine refers to the\nbalance among the branches of Government which prevents\none branch from disrupting the constitutional functions of\nanother. 52\n\n Here, the majority concludes that, in dismissing the\nindictment after two hung juries, the District Court\nencroached on the independence of the Executive because it\nprohibited the prosecution from exercising its constitutional\nduty to enforce the laws of the United States. Certainly, the\nUnited States Attorney, as a member of the Executive Branch,\nhas such a responsibility. 53 And, just as certainly, the\ndecision to prosecute “is soundly within the discretion of the\nprosecutor, not the courts.” 54 The Government’s authority\nnot to prosecute a case is clear as well. 55 But we see no sign\nthat the District Court did anything to prevent the\nGovernment from fulfilling its duty. To the contrary, the\nGovernment was twice given a full and fair opportunity to\n\n52\n See, e.g., Clinton v. Jones, 520 U.S. 681, 699-700 (1997);\nMorrison v. Olson, 487 U.S. 654, 696 (1988); Nixon v. Adm’r\nof Gen. Servs., 433 U.S. 425, 442-43 (1977); Baraka v.\nMcGreevey, 481 F.3d 187, 201 (3d Cir. 2007).\n53\n See, e.g., In re Grand Jury, 286 F.3d 153, 163 (3d Cir.\n2002).\n54\n United States v. Talley, 164 F.3d 989, 997 (6th Cir. 1999).\n55\n See, e.g., United States v. Quinn, 728 F.3d 243, 255-56 (3d\nCir. 2013).\n\n\n\n\n 15\n\npresent its case and makes no claim that the District Court\never prevented it from doing so. Having had those\nopportunities, the Government had no absolute right as a\nmatter of separation of powers or otherwise to try again. As\ntwo commentators have explained, a district court’s use of its\ninherent power to dismiss an indictment after serial mistrials\ndoes not raise “significant separation of powers concerns”\nbecause the nature of that inherent power means that federal\ncourts “need not automatically defer to a prosecutor’s\ndecision to retry a defendant” in this situation. 56\n\n The majority nevertheless concludes that prosecutors\nhave the unimpeded right to try persons for violating federal\nlaw based on an indictment as many times as they wish and\nthat the separation of powers doctrine prohibits a federal court\nfrom interfering. This position is untenable because it is not a\ntrue reflection of the separation of powers. It is axiomatic\nthat no one branch of government is completely divorced\nfrom the other two. In reality, “our constitutional system\nimposes on the Branches a degree of overlapping\nresponsibility, a duty of interdependence as well as\nindependence.” 57 This overlap becomes problematic, of\ncourse, when it results in an encroachment (when an action of\none branch might undermine the independence of another\nbranch) or an aggrandizement (where one branch seeks\n“powers more appropriately diffused among separate\nBranches”). 58\n\n\n56\n Berch & Berch, supra note 51, at 544.\n57\n Mistretta v. United States, 488 U.S. 361, 381 (1989).\n58\n Id. at 381; see also In re Tribune Media Co., 799 F.3d 272,\n285 (3d Cir. 2015) (Ambro, J., concurring).\n\n\n\n\n 16\n\n But recognizing a district court’s right to prohibit a\nretrial following serial mistrials does not implicate these\nconcerns. To the contrary, and putting the shoe on the other\nfoot, the Government’s position that nothing limits its\nopportunity to try and retry a defendant as many times as it\nchooses violates the judicial branch’s constitutional mandate\nto exercise its judicial power. Just as the filing of an\nindictment is an exercise of executive power, the dismissal of\none is an exercise of judicial power. The unlimited serial\nprosecutions that the Government advocates for, and that the\nmajority permits, would limit a court’s authority to dismiss an\nindictment to only those instances in which the prosecutor\nsteps outside the bounds of professional conduct. But our\nindependence as an institution of government must include an\nability to adjudicate, and thus dismiss with prejudice,\nindividual cases when a district court, in its discretion, has\nconcerns about the impact of serial retrials on the institution\nand the defendant. We view the prosecution of a defendant\nafter deadlocked juries as a tipping point in balancing the\nseparation of powers. As the repeated prosecutions increase,\nso too does the judiciary’s power to limit them. As we stated\nin Eash, and as we said supra, a court’s exercise of its\ninherent power to dismiss an indictment after retrials does not\nviolate the separation of powers but is grounded in it. 59\n\n B.\n\n Second, and relatedly, the majority concludes that the\nDistrict Court’s dismissal was in violation of Fed. R. Crim. P.\n31(b)(3), which the majority claims confers on prosecutors\nthe unlimited discretion to retry defendants following serial\n\n59\n See Eash, 757 F.2d at 562.\n\n\n\n\n 17\n\nmistrials. Rule 31 does nothing of the kind. Rule 31 provides\nin relevant part that “if a jury cannot agree on a verdict on one\nor more counts, the court may declare a mistrial on those\ncounts. The government may retry any defendant on any\ncounts on which the jury could not agree.” 60 The Supreme\nCourt adopted this rule in its original form in 1944 as a\n“restatement of existing law.” 61 The Supreme Court itself\nappears never to have cited Rule 31(b)(3), and neither the few\nCourts of Appeals to have done so 62 nor its Advisory\nCommittee Notes have discussed its history or purpose in any\ndetail. Arguably, the rule’s reference to the prosecutor’s\ngeneral ability to retry a defendant following a mistrial may\nbe nothing more than a recognition of the longstanding\nprinciple that retrials following mistrials are not prohibited by\nthe Double Jeopardy Clause, 63 which is not at issue here.\n\n In any event, this rule does not by its terms prohibit\ndistrict courts from dismissing indictments following serial\nmistrials. District courts have the inherent power to do so as\nexplained above. A district court’s exercise of that power\ncould be contrary to Rule 31(b)(3) only if the rule contained\nan “express grant of or limitation on” that power. 64 It does\nnot. The rule does not mandate a retrial after a mistrial. Nor\n\n60\n Fed. R. Crim. P. 31(b)(3).\n61\n Id. advisory committee’s note to 1944 adoption.\n62\n See United States v. Melendez, 775 F.3d 50, 57 (1st Cir.\n2014); United States v. Warren, 593 F.3d 540, 546 (7th Cir.\n2010); United States v. Fort, 472 F.3d 1106, 1111 n.3 (9th\nCir. 2007); United States v. Gotti, 451 F.3d 133, 137 (2d Cir.\n2006).\n63\n See United States v. Perez, 22 U.S. 579, 580 (1824).\n64\n Dietz, 136 S. Ct. at 1892.\n\n\n\n\n 18\n\ndoes it contain any other limitation on the district court’s\npower to prohibit one. In fact, the rule does not even mention\nthat issue. 65 Thus, as the Supreme Court has noted in\naddressing other rules of court, “[i]t would require a much\nclearer expression of purpose than [this rule] provides for us\nto assume that it was intended to abrogate” the district courts’\ninherent power. 66 Put simply, when there have been multiple\nmistrials and the prosecutor seeks to try the case again, Rule\n31(b)(3) does not purport to reduce the role of the district\ncourts to that of a rubber stamp.\n\n C.\n\n Finally, the majority claims that a district court can\nexercise its inherent power to dismiss an indictment only if\nthere is evidence of willful bad faith or prosecutorial\nmisconduct on the part of the government and resultant\nprejudice to the defendant. It cites to numerous decisions that\nit says supports this position. 67 But none of these cases deals\n\n65\n The majority claims that Rule 31(b)(3)’s silence on this\nissue supports the proposition that district courts lack the\nauthority to dismiss an indictment following serial mistrials.\nBut because district courts have the inherent power to do so\nas explained above, the question is not whether Rule 31(b)(3)\npermits district courts to dismiss an indictment in that\ncircumstance. The question instead is whether Rule 31(b)(3)\nprohibits them from doing so. It does not.\n66\n Link, 370 U.S. at 631-32.\n67\n See Bank of Nova Scotia v. United States, 487 U.S. 250,\n254-56, 263 (1988); United States v. Chapman, 524 F.3d\n1073, 1087 (9th Cir. 2008); United States v. Goodson, 204\nF.3d 508, 514 (4th Cir. 2000); United States v. Derrick, 163\n\n\n\n\n 19\n\nwith the particular circumstance we face here: the decision to\nretry a defendant after serial mistrials. 68 In fact, many are\ndismissals due to prosecutorial misconduct. The majority’s\nreliance on such decisions is misplaced because it ignores the\nfact that the dismissal in this case was not punitive in nature;\nit was not a sanction for misconduct. 69 As two commentators\nhave explained, “[a]lthough the inherent power principle has\nusually involved cases of misconduct by the parties or a\nvindication of statutory principles, the doctrine is not so\nlimited.” 70 To the contrary, courts may use their inherent\nauthority to dismiss indictments whenever necessary to\nvindicate “principles of fairness to the defendant and the\ninterests of the public in the effective administration of\njustice.” 71\n\n That is just what the District Court did here. The\nGovernment asked the District Court to dismiss without\nprejudice “[e]ven if this court were inclined to dismiss the\ncase.” 72 Yet the Government proffered no additional\n\n\nF.3d 799, 808 (4th Cir. 1998); United States v. Tucker, 8 F.3d\n673, 674 (9th Cir. 1993) (en banc); United States v. Van\nEngel, 15 F.3d 623, 631-32 (7th Cir. 1993); United States v.\nSantana, 6 F.3d 1, 11 (1st Cir. 1993); United States v. Isgro,\n974 F.2d 1091, 1094 (9th Cir. 1992).\n68\n Derrick does deal with a dismissal of the indictment after\nan initial grant of a retrial, but the circumstance differs from\nthis case because the mistrials were not due to deadlocked\nverdicts. See 163 F.3d at 803\n69\n Cf., e.g., Isgro, 974 F.2d at 1097.\n70\n Berch & Berch, supra note 51, at 548.\n71\n Id.\n72\n Wright, 2017 WL 1179006, at *7.\n\n\n\n\n 20\n\nevidence it would present if Wright was re-indicted. It asked\nto try the same case again before a third jury, merely hoping\nfor a different result. The District Court’s dismissal of the\nindictment with prejudice was based on the merits, or lack\nthereof, of the Government’s request, no more and no less.\n\n Moreover, the dismissal was not, as the majority\ncontends, a general declaration of unfairness simply because\nthe government failed to obtain a conviction. 73 Nor was it\nmerely an attempt to shield the defendant from the anxiety of\na retrial. 74 Reference to Miller and Shepherd misconstrues\nnot only the circumstance of this case, but also the gravity of\nthe District Court’s concern. As I discuss next, the District\nCourt weighed many factors, mindful of the importance of\neach, before making its decision. From all of this—even\ntaking into account the separation of powers and Rule\n31(b)(3)—it is evident to me that the District Court correctly\nconcluded it had the inherent authority to act upon the\nprosecutor’s decision to retry this case in the wake of two\nmistrials. 75\n\n73\n See United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\n74\n See United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975); see also Arizona v. Washington, 434 U.S. 497, 503-04\n(1978).\n75\n Although we conclude that the District Court appropriately\nexercised its inherent power as a court of law to dismiss an\nindictment, thus placing its actions within Eash’s first\ncategory, the District Court appeared at one point to tether its\ndismissal to its “inherent authority to effectuate . . . the\nspeedy and orderly administration of justice and to ensure\nfundamental fairness.” Wright, 2017 WL 1179006, at *2.\nThese actions are typically associated with the second\n\n\n\n\n 21\n\n III.\n\n Before moving to the actual merits of the District\nCourt’s decision, a word of caution is in order. Just because a\ncourt has inherent power to dismiss an indictment after a\nretrial does not mean it should always be exercised. 76 My\ndissenting opinion today should not be interpreted as an\nendorsement of unchecked and ungrounded judicial power.\nNor should it be interpreted as permitting district courts in\nthis Circuit to dismiss indictments without a significant basis\nfor doing so. Moreover, nothing in this opinion should be\nread as limiting reprosecution to two trials. Cases no doubt\nexist where a third or fourth trial on the same indictment may\nbe appropriate where the evidence so indicates. It is simply\nmy conclusion that, in some cases, and in the proper exercise\nof its discretion, a district court has the inherent power to\nprohibit continued re-prosecution by dismissing an\nindictment.\n\n IV.\n\n This is such a case. The District Court here rightly\nproceeded with the Government’s request for another trial\nwith deliberate caution. Recognizing the lack of guidance\n\n\nclassification of Eash’s powers. See Eash, 757 F.2d at 562-\n563. Nonetheless, it invoked the inherent power of the court\nand dismissed the case and it is on this basis that I conclude\nthe District Court did not reach the boundaries of its power.\n76\n See Lopez v. United States 373 U.S. 427, 440 (1963); see\nalso Chambers, 501 U.S. at 44 (“Because of their very\npotency and discretion, inherent powers must be exercised\nwith restraint and discretion.”).\n\n\n\n\n 22\n\nfrom this Court, the District Court turned to a decision of the\nSupreme Court of New Jersey. In State v. Abbati, 77 that court\nlisted several factors a trial court should consider before\ndismissing an indictment after several hung juries. These\nfactors are valid inquiries and include\n\n • the number of previous mistrials and the\n outcome of the juries’ deliberations, as far as\n can be determined;\n • the character or nature of the previous trials,\n considering their length, complexity of issues,\n and similarities in evidence;\n • the probability that any subsequent trial will be\n much different from the previous ones;\n • the relative strength of the party’s case, as\n determined by the trial court;\n • the conduct of counsel during the previous\n trials. 78\n\nIn considering these factors, a district court must also accord\nappropriate weight to the Government’s decision to continue\nprosecution, giving deliberate consideration to the reasons for\nthat choice. 79\n\n Other considerations might include the seriousness of\nthe crimes charged, the public’s interest in the effective\nresolution of criminal charges, and the criminal defendant’s\ncircumstances, including the impact that continued\nprosecution might have on him or her and the potential for\n\n77\n 493 A.2d 513.\n78\n Id. at 521-22.\n79\n See id.\n\n\n\n\n 23\n\nunfairness or unnecessary hardship. 80 The factors just\noutlined are not an exhaustive list and district courts could\nconsider other things that are reasonably useful in answering\nwhether further prosecutions after deadlocked juries should\nbe permitted. Moreover, all of these elements of inquiry\nenable the court to assess the impact that a serial retrial has on\nthe integrity of the judiciary as an institution.\n\n These avenues of inquiry make sense to me. Take\ndifferences in evidence, for example. If the evidence would\nbe different at a retrial, then there seems little chance that\ncontinued prosecution should be curtailed. If, on the other\nhand, there would be no substantial difference in evidence,\nconcern about re-prosecution is appropriate. So too the\nnumber of deadlocked juries is an important consideration.\nContinued prosecution after two, three, or even four\ndeadlocked juries could unbalance the scale. By inquiring\ninto the seriousness of the charges, a district court could\ncompare the crime being prosecuted to other cases when a\ncourt dismissed an indictment after deadlocked juries. In\nother words, a district court must make sufficient findings and\nestablish a sufficient record supporting its decision, thus\nenabling a court of appeals to accurately assess whether the\ndistrict court abused its discretion or not. That is what the\nDistrict Court did here.\n\n I see no abuse of discretion in the District Court’s\nexercise of its inherent powers. The District Court’s ruling\nwas not arbitrary and instead was based on a thorough,\ncareful, and balanced consideration of the above factors. The\nDistrict Court first acknowledged the weight of its actions\n\n80\n See id.\n\n\n\n\n 24\n\nwithin our constitutional scheme. It then found that the\nevidence suggested that the deadlock was not the result of a\nlone holdout. As to the character of the preceding trials, the\nDistrict Court noted the Government’s position that this was a\n“simple” case. It also stated that both previous trials were\n“virtual duplicates” and that counsel on both sides was the\nsame for both prosecutions. The District Court further\nobserved the lack of any allegation of jury nullification or\nbias. Instead, it found that “there is every indication that the\ntwo juries engaged in deliberations in good faith, and, despite\ntheir best efforts, were unable to reach a verdict.”\n\n The District Court also considered the strength of the\nparties’ respective cases and determined that its opinion on\nthis factor was irrelevant, given that two separate juries had\nconcluded that the Government failed to meet its burden of\nproof. It commended the professionalism and hence the\neffectiveness of counsel on all sides, which it weighted as\nfavoring disallowing any further prosecution. The District\nCourt specifically considered the seriousness of the crime\ncharged, and it noted that other courts had dismissed\nindictments when the charges were far graver. 81 Lastly, the\nDistrict Court thoroughly balanced the Government’s\nauthority to prosecute against the effect of continued\nprosecution on Wright. Recognizing that Wright has been on\nbond since July of 2014, and on home detention for nearly\ntwo years, the District Court concluded that this inquiry\ntipped in his favor.\n\n81\n Wright, 2017 WL 1179006, at *6 (citing United States v.\nIngram, 412 F. Supp. 384, 385 (D.D.C. 1976); State v.\nMoriwake, 647 P.2d 705, 708 (Haw. 1982); Abbati, 493 A.2d\nat 517; and State v. Witt, 572 S.W.2d 913, 914 (Tenn. 1978)).\n\n\n\n\n 25\n\n V.\n\n In conclusion, I see no abuse of discretion in the\nDistrict Court’s careful and thorough balancing of relevant\nfactors, a balancing which led it to invoke its inherent power\nand to dismiss the Government’s indictment of Wright. For\nall of these reasons, I respectfully dissent from my esteemed\ncolleagues in the majority. I would affirm.\n\n\n\n\n 26", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359826/", "author_raw": "NYGAARD, Circuit Judge, dissenting"}]}
SHWARTZ
NYGAARD
SHWARTZ
1
{}
5
0
3
0
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4582573/
Published
1
1
0
0
1
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Appellant v. Raymont WRIGHT\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-17\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014. 1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13\n[END_CASE]", "role": "user" } ]
4,582,984
United States v. Raymont Wright
2019-01-18
17-1972
U.S. Court of Appeals for the Third Circuit
{"judges": "Before: MCKEE, SHWARTZ, and NYGAARD, Circuit Judges.", "parties": "", "opinions": [{"type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014.1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13", "author": "SHWARTZ, Circuit Judge."}, {"type": "dissent", "author": "Our", "text": "Our dissenting colleague says that our approach\ndeprives the court from taking action “when warranted to\nprotect the institutional integrity of the judiciary.” Dissent at\n3. We disagree. This approach recognizes a court’s role in our\ntripartite system of government and ensures that a court\nintercedes when proceeding would violate the Constitution.\nFurthermore, our approach does not preclude a court from\nending a case where the evidence is insufficient or the conduct\nof the prosecution is improper.\n\n\n\n\n 22\n\nNo. 17-1972, United States of America v. Raymont Wright"}, {"author": "NYGAARD, Circuit Judge, dissenting", "type": "dissent", "text": "NYGAARD, Circuit Judge, dissenting\n\n This appeal presents us with two issues: First, does a\ndistrict court possess the inherent power to dismiss an\nindictment after serial hung juries, and second, did the\nDistrict Court here abuse its discretion by dismissing this\nindictment after two of them. I answer yes to the first and no\nto the second. Because I view this to be a matter of\nsubstantial importance, I must respectfully dissent. 1\n\n As the majority notes, twice now, the Government has\ntried Raymont Wright for a violation of federal law: being a\nfelon in possession of a firearm. 2 Twice now, the\nGovernment has done so on the basis of essentially the same\nevidence at trials presided over by the same District Court.\nAnd twice now, two different juries could not reach a verdict.\nThus, when the Government announced its intention to put\nWright on trial for the third time, the District Court was\nskeptical. It asked for briefing on whether it possessed the\ninherent power to prohibit the Government from taking a\n\n1\n Whether the District Court had the inherent power to\ndismiss the indictment is a legal question. We employ a\nplenary standard of review to that issue. See United States v.\nSchiff, 602 F.3d 152, 161 (3d Cir. 2010) (citing United States\nv. Scott, 223 F.3d 208, 210 (3d Cir. 2000)). Whether the\nDistrict Court appropriately exercised this power is reviewed\nfor an abuse of discretion. Link v. Wabash R.R. Co., 370 U.S.\n626, 633 (1962).\n2\n See 18 U.S.C. § 922(g).\n\nthird turn, and if it did, whether the court should use that\npower. 3 After hearing from both sides, the District Court\nconcluded that its inherent power applied to this\ncircumstance. It then exercised its discretion to dismiss the\nindictment.\n\n Neither the Government nor the majority disputes that\ndistrict courts have the inherent authority to dismiss\nindictments under at least some circumstances. Citing to\nUnited States v. Hasting, 4 however, the majority cabins that\nauthority to those instances in which there is evidence of\nprosecutorial misconduct. In my view, in so doing, the\nmajority conflates and confuses the various powers of the\ncourt. And it also hobbles the court’s discretion to probe the\nimpact on the fair administration of justice of those\nprosecutorial decisions that sit outside the definition of bad\nconduct but still pose—or threaten to pose—real institutional\nharm.\n\n The executive office inheres prosecutors with the\npower to bring a case to trial. The judicial office, on the other\nhand, inheres the court with the power to end a case. 5 Both\n\n3\n The District Court ordered the parties to “file cross briefs\nstating their position regarding whether the Court, through an\nexercise of its inherent authority, should prohibit or permit a\nsecond re-trial in this case.” United States v. Wright, No. 14-\ncr-292, 2017 WL 1179006, at *1 (W.D. Pa. 2017).\n4\n 461 U.S. 499, 505 (1983).\n5\n See Young v. U.S. ex rel. Vuitton et Fils S.A., 481 U.S. 787,\n816 (1987)(Scalia, J. concurring)(“The judicial power is the\npower to decide, in accordance with law, who should prevail\nin a case or controversy. See Art. III, § 2. . . . [S]ince the\n\n\n\n\n 2\n\noffices share a responsibility to safeguard the overall integrity\nof the judicial process. But when a prosecutor decides to\nproceed with another trial in the aftermath of multiple\nmistrials, who but the court is empowered to question the\nimpact of the prosecutor’s discretion on the fair\nadministration of justice, particularly when the court has\nconcerns that the proceedings—and the institution—will be\ntainted by the abuse of jury shopping? It could be argued that\ntwo mistrials may not in some instances be enough to inflict\nserious institutional damage. But, the majority’s combined\nreliance on Dietz v. Bouldin 6 and Fed. R. Crim. P. 31(b)(3) to\nallow the prosecutor to bring an unlimited number of retrials,\nso long as she or he does not stray into the realm of “illegal\nconduct,” provides the prosecutor with an unchecked power.\nThis poses a threat to the integrity of the judiciary and\ncontradicts the inherent responsibility and authority vested in\nthe judiciary by the framers of the Constitution. Thus, it is\nthe majority’s decision—and not the District Court’s exercise\nof its inherent authority—that violates the separation of\npower principles on which the majority relies. We must\naffirm that our trial court judges have the discretion,\noriginating in the court’s inherent power, to take proper\naction when warranted to protect the institutional integrity of\nthe judiciary.\n\n Here, the District Court mindfully struck the balance\nthat is necessary anytime the power of the court and the\n\n\nprosecution of law violators is part of the implementation of\nthe laws, it is—at least to the extent that it is publicly\nexercised—executive power, vested by the Constitution in the\nPresident.”) (footnote omitted)).\n6\n 136 S. Ct. 1885, 1892 (2016).\n\n\n\n\n 3\n\npower of the prosecutor intersect. Drawing from factors set\nout in State v. Abbati, 7 the District Court identified and\ninvestigated a circumstance that it identified as harmful to the\ninstitution and to the defendant: jury shopping. It also took\nnote of the impact of serial retrials on the defendant. It then\nproperly dismissed the indictment. Its use of the court’s\ninherent discretion did not violate the separation of powers\ndoctrine. To the contrary, it gave definition and substance to\nit.\n\n I.\n\n Some review is appropriate to illuminate how and\npossibly why I believe the majority confuses the court’s\nvarious powers.\n\n A.\n\n Federal courts operate within a constitutional system\nthat enumerates the powers of each branch of government, as\nset forth in the founding document. Article I restrains\ncongressional power to those “legislative Powers granted\nherein.” 8 By comparison, Article II vests the President with\n“the executive Power” without further description, limitation,\nor restriction. 9 Analogous to Article II, Article III conveys\nwithout restriction or limitation the “judicial Power” to\nfederal courts. 10 Accordingly, the Supreme Court has—since\nat least 1812—recognized that “[c]ertain implied powers must\n\n7\n 493 A.2d 513, 521-22 (N.J. 1985).\n8\n U.S. Const. art. I, § 1.\n9\n U.S. Const. art. II, § 1.\n10\n U.S. Const. art. III, § 1.\n\n\n\n\n 4\n\nnecessarily result to our Courts of justice from the nature of\ntheir institution.” 11 “The moment the courts of the United\nStates were called into existence and invested with\njurisdiction over any subject, they became possessed of”\ninherent authority. 12\n\n Moreover, two bedrock purposes of the Constitution—\nchecking the actions of the states and ensuring that Congress\nand the Executive do not overstep their boundaries—require a\nfederal judiciary that exercises its own independent judicial\npower. That is, it would be impossible for federal courts to\ndischarge these vital duties if they lacked some inherent\npower beyond the reach of the Executive or the legislature. I\nthink of it this way: the elaborate measures set out in the\nConstitution to protect the independence of the judiciary (life\ntenure, removal from office only through impeachment, no\ndecrease in salary during a judge’s tenure, for example)\nwould be meaningless if there were not some inherent,\nunimpeachable power vested solely in the federal courts.\n\n In Eash v. Riggins Trucking Inc., 13 we defined inherent\npower as vesting in federal courts upon their creation and as\nnot deriving from any statute. In this sense, the “judicial\npower” given to the federal courts by Article III of the\nConstitution is the “power to decide, in accordance with law,\nwho should prevail in a case or controversy.” 14 No matter the\ndescription, this power is intrinsic to the judicial office and\n\n11\n United States v. Hudson, 11 U.S. (7 Cranch) 32, 34 (1812).\n12\n Ex parte Robinson, 86 U.S. 505, 510 (1873) (speaking of\nthe inherent contempt power).\n13\n 757 F.2d 557, 561 (3d Cir. 1985) (en banc).\n14\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n\n\n\n\n 5\n\ncannot be inhibited by any rule or act of Congress. As we\nhave recognized, the boundaries of this power are often\n“nebulous” and “shadowy,” 15 and “it is not always possible to\ncategorize inherent power.” 16 Yet, we have an outline.\n\n In Eash, we identified three main classes or categories\nof inherent power: 1) inherent powers based in Article III,\nthat is, the power of a lower federal court to decide a case\nover which it has jurisdiction; 2) those powers “necessary to\nthe exercise of all others,” 17 and 3) powers that include those\nreasonably useful to achieve justice, which are “necessary\nonly in the practical sense of being useful.” 18 Focusing on the\nfirst category, the inherent power to decide a case is “so\nfundamental to the essence of a court as a constitutional\ntribunal that to divest the court of absolute command within\nthis sphere is really to render practically meaningless the\nterms ‘court’ and ‘judicial power.’” 19 In other words, powers\n\n15\n Eash, 757 F.2d at 561 (citation omitted).\n16\n Id. at 562.\n17\n Id. (quoting Roadway Express, Inc., v. Piper, 447 U.S. 752,\n764 (1980)).\n18\n Id. at 563; see also Am. Civil Liberties Union v. Holder,\n673 F.3d 245, 255-56 (4th Cir. 2011) (applying Eash factors);\nIn re Stone, 986 F.2d 898, 901-02 (5th Cir. 1993) (per\ncuriam) (adopting Eash factors). In Chambers v. NASCO\nInc., the Supreme Court was urged to adopt our approach to\ninherent powers. But the Court held that it “ha[d] never so\nclassified the inherent powers and . . . ha[d] no need to do so\nnow.” 501 U.S. 32, 47 n.12 (1991).\n19\n Eash, 757 F.2d at 562. The third aspect of a court’s\ninherent power is its authority to employ persons or\ninstruments not connected with the court, such as experts and\n\n\n\n\n 6\n\nin this category make a court a court; they are encoded into\nthe judiciary’s DNA. Courts have referred to this power as a\ncourt’s “irreducible inherent authority” 20 and “the core\nArticle III power.” 21 It is nothing less than our ability to\ndecide a case over which we have jurisdiction, without\ninterference by Congress or the Executive. 22\n\n Drawing from this, when I refer to a district court’s\ninherent power, I mean a ‘“[c]ertain implied power[] [that]\nmust necessarily result to our Courts of justice from the\nnature of their institution,’ [a] power[] ‘which cannot be\ndispensed with in a Court, because they are necessary to the\nexercise of all others.’” 23 It is “grounded in the separation of\npowers concept,” since to deny it and yet maintain an\nindependent judiciary “is a self-contradiction.” 24\n\n However, that is not to say that the court operates\nsolely outside the realm of legislatively granted judicial\n\n\nauditors, to assist in its decision-making function. This facet\nof inherent power is not in play here.\n20\n Id.\n21\n Am. Civil Liberties Union v. Holder, 673 F.3d at 256.\n22\n United States v. Klein, 80 U.S. (13 Wall.) 128, 147 (1871),\nEash, 757 F.2d at 562 (noting that courts may exercise this\ntype of inherent power despite legislation to the contrary); see\nalso Michaelson v. United States ex rel. Chicago, St. P., M. &\nO. Ry. Co., 266 U.S. 42, 64 (1924) (acknowledging that the\nConstitution vests courts with some powers unalterable by\nlegislation).\n23\n Chambers, 501 U.S. at 43 (quoting Hudson, 11 U.S. (7\nCranch) at 34.).\n24\n Eash, 757 F.2d at 562.\n\n\n\n\n 7\n\npowers. 25 In fact, the categorization scheme in Eash was\nintended largely as a means of explaining the relationship\nbetween inherent judicial powers and legislatively granted\njudicial powers. 26 It is here that I believe the majority’s\nanalysis strays.\n\n B.\n\n The majority, the briefs, and the discussion at oral\nargument reveal what has become a commonplace but\nimprecise conflation of the terms “inherent power” and\n“supervisory power.” 27 The Government, while referencing\nthe District Court’s “inherent power,” also referred to the\ncourt’s “supervisory power,” and its “inherent supervisory\njudicial authority.” 28 The Appellee covers the entire panoply,\nciting the District Court’s “supervisory authority,” its\n\n\n25\n See Hudson, 11 U.S. (7 Cranch) at 33.\n26\n See In re Tutu Wells Contamination Litig., 120 F.3d 368,\n384 n.14 (3d Cir. 1997), overruled on other grounds by\nCunningham v. Hamilton County, Ohio, 527 U.S. 198 (1999).\n27\n In Eash, we noted that “[t]he conceptual and definitional\nproblems regarding inherent power . . . have bedeviled\ncommentators for years,” 757 F.2d at 561, and that “those\ncases that have employed inherent power appear to use that\ngeneric term to describe several distinguishable court\npowers,” id. at 562. We also noted that “this lack of\nspecificity [has been compounded by courts] rel[ying] . . . on\nprecedents involving one form of power to support the court’s\nuse of another.” Id.\n28\n E.g., Appellant’s Br. at 13, 16; Appellant’s Reply Br. at 2,\n14.\n\n\n\n\n 8\n\n“supervisory power,” and its “inherent power.” 29 At times,\nwe too have been guilty of adding to the confusion. 30 The\nerroneous interchangeability of these terms clouds an\nimportant distinction that is crucial to this appeal: the\ndifference between inherent judicial powers and legislatively\ngranted judicial powers. 31 As noted supra, inherent “judicial\npower” is given to the federal courts by Article III of the\nConstitution. 32 Through this grant, federal courts receive the\n“power to decide, in accordance with law, who should prevail\nin a case or controversy.” 33 The merging of the terms\n“inherent” and “supervisory” likely has its genesis in the fact\nthat some inherent powers are supervisory in function, such\nas a federal court’s inherent power “to supervise the\nadministration of criminal justice.” 34\n\n29\n E.g., Appellee’s Br. at 22, 26.\n30\n See, e.g., United States v. Accetturo, 783 F.2d 382, 396 (3d\nCir. 1986) (Sloviter, J., dissenting) (speaking of our “inherent\nsupervisory power”); see also United States v. Watkins, 339\nF.3d 167, 180 (3d Cir. 2003) (Nygaard, J., concurring)\n(referring to both a court’s supervisory power and inherent\npower to dismiss a case under Fed. R. Crim. P. 48(b)).\n31\n In re Tutu Wells Litig., 120 F.3d at 384 n. 14.\n32\n See U.S. Const. art. III, § 1.\n33\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n34\n United States v. Payner, 447 U.S. 727, 735 n.7 (1980)\n(quotation marks omitted); see also Sara Sun Beale,\nReconsidering Supervisory Power in Criminal Cases;\nConstitutional and Statutory Limits of the Federal Courts, 84\nColum. L. Rev. 1433, 1433-34, 1465, 1470 (1984)\n(identification of Article III “judicial power,” not\ncongressional acts, as the source of the Supreme Court’s\nsupervisory authority).\n\n\n\n\n 9\n\n However, unlike inherent powers, a court’s\nsupervisory authority may come from, and can be limited by,\nacts of Congress or a court’s own rules. 35 Supervisory power\noften speaks to the power “to mandate ‘procedures deemed\ndesirable from the viewpoint of sound judicial practice.’” 36 A\ncourt’s use of supervisory power can usually be classified in\none of three ways. First, supervisory power can refer to an\nappellate court’s supervision of a district court, through the\nimposition of procedures in addition to those already imposed\nby federal statute or constitutional provision. 37 We have, for\nexample, relied on our supervisory power over district courts\nto review the application of local rules of practice and\nprocedure. 38 We have also used our supervisory power to\n\n\n\n\n35\n See, e.g., McNabb v. United States, 318 U.S. 332, 340-41\n(1943); Hasting, 461 U.S. at 505.\n36\n United States v. Moreno, 809 F.3d 766, 780 (3d Cir. 2016)\n(quoting Thomas v. Arn, 474 U.S. 140, 146-47 (1985)).\n37\n See, e.g., Castro v. United States, 540 U.S. 375, 384 (2003)\n(instructing district courts to notify pro se litigants about\nconsequences of re-characterizing motions as ones seeking\nrelief under 28 U.S.C. § 2255); Thiel v. S. Pac. Co., 328 U.S.\n217, 225 (1946) (announcing a new rule for the composition\nof federal juries); Dunbar v. Triangle Lumber & Supply Co.,\n816 F.2d 126, 129 (3d Cir. 1987) (prescribing procedures for\nmotions to dismiss based on the conduct of a litigant’s\ncounsel); United States v. Bazzano, 570 F.2d 1120, 1137-38\n(3d Cir. 1977) (requiring district courts to state reasons for a\ncriminal sentence).\n38\n See United States v. Wecht, 484 F.3d 194, 204-05 (3d Cir.\n2007).\n\n\n\n\n 10\n\nprohibit certain jury instructions in the district courts 39 and to\nreview attorney-client fee arrangements. 40 Second, Courts—\nboth trial and appellate—also refer to their “supervisory\npower” when meaning their power to supervise pending\nlitigation. 41 They can, for example, seal and unseal records, 42\nreassign a case to a different judge on remand, 43 or disqualify\nan attorney on ethical grounds. 44 Lastly, the power of a\nfederal court to supervise law enforcement officials can also\nbe what a court intends when it speaks of its “supervisory\n\n\n\n\n39\n See United States v. E. Med. Billing Inc., 230 F.3d 600,\n607-12 (3d Cir. 2000).\n40\n See Ryan v. Butera, Beausang, Cohen & Brennan, 193 F.3d\n210, 214 (3d Cir. 1999).\n41\n See, e.g., Carlisle v. United States, 517 U.S. 416, 425-26\n(1996) (acknowledging “supervisory power” of district courts\nover litigation before them).\n42\n See, e.g., Hagestad v. Tragesser, 49 F.3d 1430, 1434 (9th\nCir. 1995).\n43\n See Gov’t of the Virgin Islands v. Walker, 261 F.3d 370,\n376 (3d Cir. 2001) (noting that, “[a]lthough it is the standard\npractice in the district courts and in this circuit that a case on\nremand is assigned to the judge who originally heard it, we\ncan, in the exercise of our supervisory power, reassign this\ncase to a different judge upon remand.”) (quotation marks\nomitted).\n44\n In re Grand Jury Investigation, 447 F. Supp. 2d 453, 456-\n57 (E.D. Pa. 2006) (collecting cases); see also United States\nv. Moreno, 809 F.3d at 780 (summarizing supervisory\nauthority).\n\n\n\n\n 11\n\npower.” 45 These powers broadly ensure that pending cases\nare managed uniformly and efficiently.\n\n I concede that the boundary between supervisory\nauthority that is inherent to the court and that which is granted\nby the legislature can, at times, be difficult to identify.\nHowever, these difficulties are irrelevant to this case because\nI conclude that the District Court here acted pursuant to its\ninherent power and not to any authority conferred by any\nstatute or rule. The District Court’s action was not\nundertaken in supervision of pending litigation—two trials\nwere already concluded and a potential third trial had not yet\nbegun. Nor was it exercised according to a rule of procedure\nor practice newly announced by an appellate tribunal.\nMoreover, its action was not a response to any prosecutorial\nmisconduct or request from Wright to dismiss the indictment.\nThere is simply no basis to conclude that the inherent power\nthat the District Court exercised in this case derived from any\nlegislative grant.\n\n To the contrary, the specific power under review here\nis the power to dismiss an indictment after two mistrials\nbecause of deadlocked juries in each instance. This power\nfalls within Eash’s first category of power because it is an\ninherent power to resolve a case. A court, by its nature, must\nbe able to dismiss with prejudice actions brought before it,\njust as it must have the power to decide cases and enter\n\n45\n See, e.g., United States v. Thompson, 772 F.3d 752, 763 (3d\nCir. 2014). For a comprehensive discussion of the origins\nand uses of supervisory power, see Amy Coney Barrett, The\nSupervisory Power of the Supreme Court, 106 Colum. L. Rev.\n324, 330 (2006).\n\n\n\n\n 12\n\njudgments. 46 Such exercises of power are fundamental to the\nessence of a court. Were they not, the judicial system simply\ncould not function. 47\n\n The inherent power to dismiss is “of ancient origin,\nhaving its roots in judgments of nonsuit and non prosequitur\nentered at common law,” and so is a power that is part of the\nvery nature of the judicial institution. 48 It is incidental and\nnecessary to the fair and efficient operation of the courts. 49\nIndeed, “the power to dismiss exists in many situations. For\nexample, a district court has the inherent power to dismiss sua\nsponte for lack of jurisdiction, or under the doctrine of forum\nnon conveniens.” 50 Because the power to resolve a case by\ndismissing an indictment (in a criminal action) or a complaint\n(in a civil action) is fundamental to the essence of a court of\njustice, it cannot be interfered with. Indeed, as two\ncommentators have explained, “McNabb, other Supreme\n\n46\n We have also noted that our power to remand is a subset of\nthe inherent power to dismiss a case. See Bradgate Assocs.,\nInc. v. Fellows, Read & Assocs., Inc., 999 F.2d. 745, 750 n.4\n(3d Cir. 1993).\n47\n See, e.g., Fitzgerald v. First E. Seventh St. Tenants Corp.,\n221 F.3d 362, 363-364 (2d Cir. 2000) (holding a district court\nhas the inherent power to dismiss a case, sua sponte, if it\ndetermines that the action is frivolous or the court lacks\njurisdiction over the matter).\n48\n Link, 370 U.S. at 630.\n49\n See, e.g., Bowers v. Nat’l Collegiate Athletic Ass’n, 564 F.\nSupp. 2d 322, 333 (D.N.J. 2008) (citing Derzack v. County of\nAllegheny, 173 F.R.D. 400, 411 (W.D. Pa. 1996), aff’d\nwithout op., 118 F.3d 1575 (3d Cir. 1997)).\n50\n In re Prevot, 59 F.3d 556, 565-66 (6th Cir. 1995).\n\n\n\n\n 13\n\nCourt cases, and an analysis of several lower court opinions\naddressing this precise issue should sufficiently dispel any\nnotion that the federal courts lack the power to bar repeated\nattempts to obtain a conviction” following serial mistrials.51\nThus, the District Court’s action here was well within the\nboundaries of its inherent power.\n\n Therefore, the majority’s conclusion that “inherent\nauthority,” “supervisory power,” and “supervisory authority”\nall refer to the same thing (while understandable given the\nrampant muddled references that persist) ultimately misses\nthe point. The power at issue here is the inherent power of\nthe court to decide a case: a power that is limited by the\nboundaries of reason and discretion and is subject to appellate\nreview for abuse. It is not subject to the power of Congress\nor the Executive.\n\n II.\n\n There is no dispute that district courts have the\ninherent power to dismiss indictments in at least some\ncircumstance. The majority nevertheless concludes that the\nDistrict Court lacked the power to do so in this case. The\nmajority reaches that conclusion for three principal reasons,\nbut none withstands scrutiny.\n\n A.\n\n51\n Michael A. Berch & Rebecca White Berch, The Power of\nthe Judiciary to Dismiss Criminal Charges After Several\nHung Juries: A Proposed Rule to Control Judicial Discretion,\n30 Loy. L.A. L. Rev. 535, 543 & nn. 42-43 (1997) (collecting\ncases).\n\n\n\n\n 14\n\n First, the majority agrees with the Government’s\nargument that the District Court’s dismissal violated the\nSeparation of Powers Doctrine. I agree that the District\nCourt’s dismissal implicates the separation of powers. But its\nactions were in furtherance—not in violation—of the\ndoctrine. The separation of powers doctrine refers to the\nbalance among the branches of Government which prevents\none branch from disrupting the constitutional functions of\nanother. 52\n\n Here, the majority concludes that, in dismissing the\nindictment after two hung juries, the District Court\nencroached on the independence of the Executive because it\nprohibited the prosecution from exercising its constitutional\nduty to enforce the laws of the United States. Certainly, the\nUnited States Attorney, as a member of the Executive Branch,\nhas such a responsibility. 53 And, just as certainly, the\ndecision to prosecute “is soundly within the discretion of the\nprosecutor, not the courts.” 54 The Government’s authority\nnot to prosecute a case is clear as well. 55 But we see no sign\nthat the District Court did anything to prevent the\nGovernment from fulfilling its duty. To the contrary, the\nGovernment was twice given a full and fair opportunity to\n\n52\n See, e.g., Clinton v. Jones, 520 U.S. 681, 699-700 (1997);\nMorrison v. Olson, 487 U.S. 654, 696 (1988); Nixon v. Adm’r\nof Gen. Servs., 433 U.S. 425, 442-43 (1977); Baraka v.\nMcGreevey, 481 F.3d 187, 201 (3d Cir. 2007).\n53\n See, e.g., In re Grand Jury, 286 F.3d 153, 163 (3d Cir.\n2002).\n54\n United States v. Talley, 164 F.3d 989, 997 (6th Cir. 1999).\n55\n See, e.g., United States v. Quinn, 728 F.3d 243, 255-56 (3d\nCir. 2013).\n\n\n\n\n 15\n\npresent its case and makes no claim that the District Court\never prevented it from doing so. Having had those\nopportunities, the Government had no absolute right as a\nmatter of separation of powers or otherwise to try again. As\ntwo commentators have explained, a district court’s use of its\ninherent power to dismiss an indictment after serial mistrials\ndoes not raise “significant separation of powers concerns”\nbecause the nature of that inherent power means that federal\ncourts “need not automatically defer to a prosecutor’s\ndecision to retry a defendant” in this situation. 56\n\n The majority nevertheless concludes that prosecutors\nhave the unimpeded right to try persons for violating federal\nlaw based on an indictment as many times as they wish and\nthat the separation of powers doctrine prohibits a federal court\nfrom interfering. This position is untenable because it is not a\ntrue reflection of the separation of powers. It is axiomatic\nthat no one branch of government is completely divorced\nfrom the other two. In reality, “our constitutional system\nimposes on the Branches a degree of overlapping\nresponsibility, a duty of interdependence as well as\nindependence.” 57 This overlap becomes problematic, of\ncourse, when it results in an encroachment (when an action of\none branch might undermine the independence of another\nbranch) or an aggrandizement (where one branch seeks\n“powers more appropriately diffused among separate\nBranches”). 58\n\n\n56\n Berch & Berch, supra note 51, at 544.\n57\n Mistretta v. United States, 488 U.S. 361, 381 (1989).\n58\n Id. at 381; see also In re Tribune Media Co., 799 F.3d 272,\n285 (3d Cir. 2015) (Ambro, J., concurring).\n\n\n\n\n 16\n\n But recognizing a district court’s right to prohibit a\nretrial following serial mistrials does not implicate these\nconcerns. To the contrary, and putting the shoe on the other\nfoot, the Government’s position that nothing limits its\nopportunity to try and retry a defendant as many times as it\nchooses violates the judicial branch’s constitutional mandate\nto exercise its judicial power. Just as the filing of an\nindictment is an exercise of executive power, the dismissal of\none is an exercise of judicial power. The unlimited serial\nprosecutions that the Government advocates for, and that the\nmajority permits, would limit a court’s authority to dismiss an\nindictment to only those instances in which the prosecutor\nsteps outside the bounds of professional conduct. But our\nindependence as an institution of government must include an\nability to adjudicate, and thus dismiss with prejudice,\nindividual cases when a district court, in its discretion, has\nconcerns about the impact of serial retrials on the institution\nand the defendant. We view the prosecution of a defendant\nafter deadlocked juries as a tipping point in balancing the\nseparation of powers. As the repeated prosecutions increase,\nso too does the judiciary’s power to limit them. As we stated\nin Eash, and as we said supra, a court’s exercise of its\ninherent power to dismiss an indictment after retrials does not\nviolate the separation of powers but is grounded in it. 59\n\n B.\n\n Second, and relatedly, the majority concludes that the\nDistrict Court’s dismissal was in violation of Fed. R. Crim. P.\n31(b)(3), which the majority claims confers on prosecutors\nthe unlimited discretion to retry defendants following serial\n\n59\n See Eash, 757 F.2d at 562.\n\n\n\n\n 17\n\nmistrials. Rule 31 does nothing of the kind. Rule 31 provides\nin relevant part that “if a jury cannot agree on a verdict on one\nor more counts, the court may declare a mistrial on those\ncounts. The government may retry any defendant on any\ncounts on which the jury could not agree.” 60 The Supreme\nCourt adopted this rule in its original form in 1944 as a\n“restatement of existing law.” 61 The Supreme Court itself\nappears never to have cited Rule 31(b)(3), and neither the few\nCourts of Appeals to have done so 62 nor its Advisory\nCommittee Notes have discussed its history or purpose in any\ndetail. Arguably, the rule’s reference to the prosecutor’s\ngeneral ability to retry a defendant following a mistrial may\nbe nothing more than a recognition of the longstanding\nprinciple that retrials following mistrials are not prohibited by\nthe Double Jeopardy Clause, 63 which is not at issue here.\n\n In any event, this rule does not by its terms prohibit\ndistrict courts from dismissing indictments following serial\nmistrials. District courts have the inherent power to do so as\nexplained above. A district court’s exercise of that power\ncould be contrary to Rule 31(b)(3) only if the rule contained\nan “express grant of or limitation on” that power. 64 It does\nnot. The rule does not mandate a retrial after a mistrial. Nor\n\n60\n Fed. R. Crim. P. 31(b)(3).\n61\n Id. advisory committee’s note to 1944 adoption.\n62\n See United States v. Melendez, 775 F.3d 50, 57 (1st Cir.\n2014); United States v. Warren, 593 F.3d 540, 546 (7th Cir.\n2010); United States v. Fort, 472 F.3d 1106, 1111 n.3 (9th\nCir. 2007); United States v. Gotti, 451 F.3d 133, 137 (2d Cir.\n2006).\n63\n See United States v. Perez, 22 U.S. 579, 580 (1824).\n64\n Dietz, 136 S. Ct. at 1892.\n\n\n\n\n 18\n\ndoes it contain any other limitation on the district court’s\npower to prohibit one. In fact, the rule does not even mention\nthat issue. 65 Thus, as the Supreme Court has noted in\naddressing other rules of court, “[i]t would require a much\nclearer expression of purpose than [this rule] provides for us\nto assume that it was intended to abrogate” the district courts’\ninherent power. 66 Put simply, when there have been multiple\nmistrials and the prosecutor seeks to try the case again, Rule\n31(b)(3) does not purport to reduce the role of the district\ncourts to that of a rubber stamp.\n\n C.\n\n Finally, the majority claims that a district court can\nexercise its inherent power to dismiss an indictment only if\nthere is evidence of willful bad faith or prosecutorial\nmisconduct on the part of the government and resultant\nprejudice to the defendant. It cites to numerous decisions that\nit says supports this position. 67 But none of these cases deals\n\n65\n The majority claims that Rule 31(b)(3)’s silence on this\nissue supports the proposition that district courts lack the\nauthority to dismiss an indictment following serial mistrials.\nBut because district courts have the inherent power to do so\nas explained above, the question is not whether Rule 31(b)(3)\npermits district courts to dismiss an indictment in that\ncircumstance. The question instead is whether Rule 31(b)(3)\nprohibits them from doing so. It does not.\n66\n Link, 370 U.S. at 631-32.\n67\n See Bank of Nova Scotia v. United States, 487 U.S. 250,\n254-56, 263 (1988); United States v. Chapman, 524 F.3d\n1073, 1087 (9th Cir. 2008); United States v. Goodson, 204\nF.3d 508, 514 (4th Cir. 2000); United States v. Derrick, 163\n\n\n\n\n 19\n\nwith the particular circumstance we face here: the decision to\nretry a defendant after serial mistrials. 68 In fact, many are\ndismissals due to prosecutorial misconduct. The majority’s\nreliance on such decisions is misplaced because it ignores the\nfact that the dismissal in this case was not punitive in nature;\nit was not a sanction for misconduct. 69 As two commentators\nhave explained, “[a]lthough the inherent power principle has\nusually involved cases of misconduct by the parties or a\nvindication of statutory principles, the doctrine is not so\nlimited.” 70 To the contrary, courts may use their inherent\nauthority to dismiss indictments whenever necessary to\nvindicate “principles of fairness to the defendant and the\ninterests of the public in the effective administration of\njustice.” 71\n\n That is just what the District Court did here. The\nGovernment asked the District Court to dismiss without\nprejudice “[e]ven if this court were inclined to dismiss the\ncase.” 72 Yet the Government proffered no additional\n\n\nF.3d 799, 808 (4th Cir. 1998); United States v. Tucker, 8 F.3d\n673, 674 (9th Cir. 1993) (en banc); United States v. Van\nEngel, 15 F.3d 623, 631-32 (7th Cir. 1993); United States v.\nSantana, 6 F.3d 1, 11 (1st Cir. 1993); United States v. Isgro,\n974 F.2d 1091, 1094 (9th Cir. 1992).\n68\n Derrick does deal with a dismissal of the indictment after\nan initial grant of a retrial, but the circumstance differs from\nthis case because the mistrials were not due to deadlocked\nverdicts. See 163 F.3d at 803\n69\n Cf., e.g., Isgro, 974 F.2d at 1097.\n70\n Berch & Berch, supra note 51, at 548.\n71\n Id.\n72\n Wright, 2017 WL 1179006, at *7.\n\n\n\n\n 20\n\nevidence it would present if Wright was re-indicted. It asked\nto try the same case again before a third jury, merely hoping\nfor a different result. The District Court’s dismissal of the\nindictment with prejudice was based on the merits, or lack\nthereof, of the Government’s request, no more and no less.\n\n Moreover, the dismissal was not, as the majority\ncontends, a general declaration of unfairness simply because\nthe government failed to obtain a conviction. 73 Nor was it\nmerely an attempt to shield the defendant from the anxiety of\na retrial. 74 Reference to Miller and Shepherd misconstrues\nnot only the circumstance of this case, but also the gravity of\nthe District Court’s concern. As I discuss next, the District\nCourt weighed many factors, mindful of the importance of\neach, before making its decision. From all of this—even\ntaking into account the separation of powers and Rule\n31(b)(3)—it is evident to me that the District Court correctly\nconcluded it had the inherent authority to act upon the\nprosecutor’s decision to retry this case in the wake of two\nmistrials. 75\n\n73\n See United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\n74\n See United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975); see also Arizona v. Washington, 434 U.S. 497, 503-04\n(1978).\n75\n Although we conclude that the District Court appropriately\nexercised its inherent power as a court of law to dismiss an\nindictment, thus placing its actions within Eash’s first\ncategory, the District Court appeared at one point to tether its\ndismissal to its “inherent authority to effectuate . . . the\nspeedy and orderly administration of justice and to ensure\nfundamental fairness.” Wright, 2017 WL 1179006, at *2.\nThese actions are typically associated with the second\n\n\n\n\n 21\n\n III.\n\n Before moving to the actual merits of the District\nCourt’s decision, a word of caution is in order. Just because a\ncourt has inherent power to dismiss an indictment after a\nretrial does not mean it should always be exercised. 76 My\ndissenting opinion today should not be interpreted as an\nendorsement of unchecked and ungrounded judicial power.\nNor should it be interpreted as permitting district courts in\nthis Circuit to dismiss indictments without a significant basis\nfor doing so. Moreover, nothing in this opinion should be\nread as limiting reprosecution to two trials. Cases no doubt\nexist where a third or fourth trial on the same indictment may\nbe appropriate where the evidence so indicates. It is simply\nmy conclusion that, in some cases, and in the proper exercise\nof its discretion, a district court has the inherent power to\nprohibit continued re-prosecution by dismissing an\nindictment.\n\n IV.\n\n This is such a case. The District Court here rightly\nproceeded with the Government’s request for another trial\nwith deliberate caution. Recognizing the lack of guidance\n\n\nclassification of Eash’s powers. See Eash, 757 F.2d at 562-\n563. Nonetheless, it invoked the inherent power of the court\nand dismissed the case and it is on this basis that I conclude\nthe District Court did not reach the boundaries of its power.\n76\n See Lopez v. United States 373 U.S. 427, 440 (1963); see\nalso Chambers, 501 U.S. at 44 (“Because of their very\npotency and discretion, inherent powers must be exercised\nwith restraint and discretion.”).\n\n\n\n\n 22\n\nfrom this Court, the District Court turned to a decision of the\nSupreme Court of New Jersey. In State v. Abbati, 77 that court\nlisted several factors a trial court should consider before\ndismissing an indictment after several hung juries. These\nfactors are valid inquiries and include\n\n • the number of previous mistrials and the\n outcome of the juries’ deliberations, as far as\n can be determined;\n • the character or nature of the previous trials,\n considering their length, complexity of issues,\n and similarities in evidence;\n • the probability that any subsequent trial will be\n much different from the previous ones;\n • the relative strength of the party’s case, as\n determined by the trial court;\n • the conduct of counsel during the previous\n trials. 78\n\nIn considering these factors, a district court must also accord\nappropriate weight to the Government’s decision to continue\nprosecution, giving deliberate consideration to the reasons for\nthat choice. 79\n\n Other considerations might include the seriousness of\nthe crimes charged, the public’s interest in the effective\nresolution of criminal charges, and the criminal defendant’s\ncircumstances, including the impact that continued\nprosecution might have on him or her and the potential for\n\n77\n 493 A.2d 513.\n78\n Id. at 521-22.\n79\n See id.\n\n\n\n\n 23\n\nunfairness or unnecessary hardship. 80 The factors just\noutlined are not an exhaustive list and district courts could\nconsider other things that are reasonably useful in answering\nwhether further prosecutions after deadlocked juries should\nbe permitted. Moreover, all of these elements of inquiry\nenable the court to assess the impact that a serial retrial has on\nthe integrity of the judiciary as an institution.\n\n These avenues of inquiry make sense to me. Take\ndifferences in evidence, for example. If the evidence would\nbe different at a retrial, then there seems little chance that\ncontinued prosecution should be curtailed. If, on the other\nhand, there would be no substantial difference in evidence,\nconcern about re-prosecution is appropriate. So too the\nnumber of deadlocked juries is an important consideration.\nContinued prosecution after two, three, or even four\ndeadlocked juries could unbalance the scale. By inquiring\ninto the seriousness of the charges, a district court could\ncompare the crime being prosecuted to other cases when a\ncourt dismissed an indictment after deadlocked juries. In\nother words, a district court must make sufficient findings and\nestablish a sufficient record supporting its decision, thus\nenabling a court of appeals to accurately assess whether the\ndistrict court abused its discretion or not. That is what the\nDistrict Court did here.\n\n I see no abuse of discretion in the District Court’s\nexercise of its inherent powers. The District Court’s ruling\nwas not arbitrary and instead was based on a thorough,\ncareful, and balanced consideration of the above factors. The\nDistrict Court first acknowledged the weight of its actions\n\n80\n See id.\n\n\n\n\n 24\n\nwithin our constitutional scheme. It then found that the\nevidence suggested that the deadlock was not the result of a\nlone holdout. As to the character of the preceding trials, the\nDistrict Court noted the Government’s position that this was a\n“simple” case. It also stated that both previous trials were\n“virtual duplicates” and that counsel on both sides was the\nsame for both prosecutions. The District Court further\nobserved the lack of any allegation of jury nullification or\nbias. Instead, it found that “there is every indication that the\ntwo juries engaged in deliberations in good faith, and, despite\ntheir best efforts, were unable to reach a verdict.”\n\n The District Court also considered the strength of the\nparties’ respective cases and determined that its opinion on\nthis factor was irrelevant, given that two separate juries had\nconcluded that the Government failed to meet its burden of\nproof. It commended the professionalism and hence the\neffectiveness of counsel on all sides, which it weighted as\nfavoring disallowing any further prosecution. The District\nCourt specifically considered the seriousness of the crime\ncharged, and it noted that other courts had dismissed\nindictments when the charges were far graver. 81 Lastly, the\nDistrict Court thoroughly balanced the Government’s\nauthority to prosecute against the effect of continued\nprosecution on Wright. Recognizing that Wright has been on\nbond since July of 2014, and on home detention for nearly\ntwo years, the District Court concluded that this inquiry\ntipped in his favor.\n\n81\n Wright, 2017 WL 1179006, at *6 (citing United States v.\nIngram, 412 F. Supp. 384, 385 (D.D.C. 1976); State v.\nMoriwake, 647 P.2d 705, 708 (Haw. 1982); Abbati, 493 A.2d\nat 517; and State v. Witt, 572 S.W.2d 913, 914 (Tenn. 1978)).\n\n\n\n\n 25\n\n V.\n\n In conclusion, I see no abuse of discretion in the\nDistrict Court’s careful and thorough balancing of relevant\nfactors, a balancing which led it to invoke its inherent power\nand to dismiss the Government’s indictment of Wright. For\nall of these reasons, I respectfully dissent from my esteemed\ncolleagues in the majority. I would affirm.\n\n\n\n\n 26", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360237/", "author_raw": "NYGAARD, Circuit Judge, dissenting"}, {"author": "McKEE, Circuit Judge, concurring", "type": "concurrence", "text": "McKEE, Circuit Judge, concurring in the judgment.\n\n As I shall explain, I am sympathetic to what the District\nCourt was trying to do in this case and I think I understand why\nthe court acted as it did. Moreover, I agree with Judge Nygaard\ninsofar as he posits in dissent that a District Court can step in\nat some point and bar a retrial without infringing on the\nseparation of powers. Nevertheless, despite my belief that the\nseparation of powers doctrine is not necessarily violated by a\ntrial court barring a retrial after successive mistrials, and\ndespite my belief that the District Court was trying to act in a\nmanner that would assure a measure of justice for Wright, I\nconcur in the judgment reversing the District Court. I simply\ndo not believe that the current state of the law supports the\nDistrict Court’s action in the absence of prosecutorial\nmisconduct, bad faith, or more than two unsuccessful trials.\nSince the record is clear that the District Court found neither\nprosecutorial misconduct nor bad faith, I concur in the\njudgment reversing the court’s order but feel compelled to\nwrite separately to explain why.\n I.\n At the outset, it is important to note that I do not believe\nthat a trial court lacks the power to, at some point, call a halt to\nsuccessive prosecutions following deadlocked juries, and I do\nnot read Judge Shwartz’s opinion as standing for that principle.\nThe Government even conceded at oral argument that there\ncould come a point where successive prosecutions become so\nonerous and burdensome that additional trials rise to the level\nof a Due Process violation which a trial court is clearly\nempowered to prevent. Moreover, in Barkus v. Illinois, 1 the\nSupreme Court noted that there “may” come a point where\nmultiple prosecutions become so harassing that they violate the\nDue Process Clause. 2\n\n Here the evidence in both trials consisted solely of\npolice testimony. According to the officers’ testimony, some\nresidents of the community witnessed crucial parts of Wright’s\nencounter with the police, but they did not testify. Similarly,\nWright did not testify on his own behalf, nor did the defense\nput on a case. His theory was that he had no way of knowing\n\n1\n 359 U.S. 121 (1959).\n2\n Id. at 127.\n 1\n\nthat the men in plain clothes and unmarked cars who began\npursuing him were police; he panicked, sped away, and\ncrashed; and police subsequently planted the gun at the scene.\nWright also asserted that the officers chose not to test the gun\nfor DNA or fingerprints because they knew the results would\ncontradict their story. In an effort to counter Wright’s\nargument from the first trial that police decided not to test the\ngun for fingerprints and DNA in order to hide their\nmalfeasance, the Government called experts at the second trial\n“who testified about the difficulty of retrieving DNA and\nfingerprint evidence from firearms.” 3\n\n Nevertheless, the Government’s case depended entirely\non the testimony of police officers who had worked together\nfor many years and/or knew one another. Over the span of ten\nmonths, the District Court twice listened to the police\ntestimony during the trials. That testimony was at times\ncontradictory and at other times strained credulity.\n\n At the first trial, Detective Fallert, who first noticed\nWright speeding, testified that Wright was travelling at 90\nmph, but he did not note that in his police paperwork nor did\nhe note it at the pretrial hearing. His contemporaneously\nprepared investigative report also did not claim that Wright\nwas initially speeding. Detective Henson, who took over the\nchase, testified that he saw Wright holding a handgun, but\nconceded that he had no way of knowing whether Wright knew\nhe was a police officer when the pursuit began. Lastly,\nDetective Baker testified similarly to Henson, yet guessed that\nWright had been going at a speed of 60 mph and accelerated.\nThis is a very substantial discrepancy, especially for seasoned\npolice officers who can be expected to have some expertise and\nexperience in estimating the speed of an automobile.\n\n In the second trial, the Government called the same\nwitnesses, with the exception of Detective Fallert. Notably,\nthis time Detective Henson testified he actually did not see\nWright speeding. Two different juries found themselves\ndeadlocked—unable to convict or acquit.\n II.\n The majority opinion suggests that the District Court’s\n\n3\n Appellant Br. at 11.\n 2\n\ndecision to dismiss the indictment with prejudice\nimpermissibly infringed upon the jury’s role. Judge Shwartz\nstates: “[t]he District Court nonetheless applied its own\npredictions about what another jury may do when presented\nwith the same evidence,” and concluded that was “an improper\nexercise of a court’s supervisory power.” 4 However, it is\ndifficult to know whether the District Court ruled as it did\nbased upon a belief that a third jury presented with the same\nevidence would be unable to reach a verdict or whether it\nsimply shared the doubts that some of the jurors obviously had\nabout the veracity of police officers’ testimony.\n\n In any event, either scenario poses exactly the same\nissue about a court overstepping its bounds and infringing on\nthe role of a jury as well as prosecutorial discretion. As I stated\nat the beginning, to the extent that a trial judge can intervene\nand dismiss an indictment, I am skeptical that this record\nsupports such an assertion of judicial authority. Nevertheless,\nthere is more support for the judge’s actions here than our\nreversal suggests.\n\n It is not a novel proposition that a trial judge must\n“ensure that any and all . . . evidence is not only relevant, but\nalso reliable.” 5 “The trial judge’s role is to preside over the\ntrial; passively if possible but aggressively when indicated.” 6\nThus, the law allows for trial courts to channel the jury’s\njudgment in certain circumstances. Here, the court’s decision\nwould prevent another jury from hearing the same evidence\nthat has failed to convict Wright on two prior occasions.\n\n There are situations in which judges must act as\n“gatekeepers” and ensure the reliability of evidence before a\njury is able to consider it. Accordingly, in an admittedly very\ndifferent context, the Supreme Court has described trial judges\nas gatekeepers of evidence. 7 “[A] gatekeeping role for the\n\n4\n Maj. Op. 13–14.\n5\n Kannankeril v. Terminix Int’l, Inc., 128 F.3d 802, 806 (3d\nCir. 1997) (citing Daubert v. Merrill Dow Pharms., 509 U.S.\n579, 589 (1993)).\n6\n Holdnrook v. Lykes Bros. Steamship Co., 80 F.3d 777, 788\n(3d Cir. 1996).\n7\n Daubert, 509 U.S. at 597.\n 3\n\njudge, no matter how flexible, inevitably on occasion will\nprevent the jury from learning of authentic insights and\ninnovations.” 8\n\n Despite the importance of the jury system, and the faith\nwe place in juries, the law has thus traditionally recognized the\ndanger that jurors may not be able to restrict their deliberations\nto admissible evidence and that they may return a verdict based\non factors other than the evidence presented at trial. For\nexample, Federal Rule of Evidence 403 allows courts to\nprevent jurors from learning of certain testimony (even\nuncontradicted testimony) if the court concludes that the\ntestimony could cause a jury to reach a verdict based more on\nemotion or prejudice than on evidence. 9\n\n The best known example of how courts are empowered\nto limit what a jury can consider may well be the body of law\nthat has developed in the wake of the Supreme Court’s decision\nin Daubert. In Daubert, the Court stated: “the trial judge must\nensure that any and all scientific testimony or evidence\nadmitted is not only relevant, but reliable.” 10 We certainly\ncould, but do not, allow the jury to determine whether the\nscientific evidence is reliable in the first instance based upon\ntestimony at trial. Instead, that preliminary factual\ndetermination rests solely with the trial court if the reliability\nis challenged.\n\n The difficulty with relying on this body of law here is,\nof course, the fact that the trial court’s dismissal of Wright’s\nindictment was not limited to an intrusion into the jury-box.\nMore fundamentally, and more importantly, it also trespassed\non the separation of powers, and concomitantly, on the\nprosecutorial discretion that is endemic in that concept.\n\n Despite Judge Nygaard’s thoughtful attempt to address\nthat issue and the jury’s obvious concerns regarding the\n\n8\n Id.\n9\n See, e.g., United States v. Bailey, 840 F.3d 99, 117, 121–23,\n(3d Cir. 2016) (finding that the probative value of video\nevidence of murder committed by coconspirators was\nsubstantially outweighed by risk of unfair prejudice).\n10\n Daubert, 509 U.S. at 589.\n 4\n\ntestimony of police officers in this case, I am not convinced\nthat the United States Supreme Court would agree that the\ninherent powers of a trial court are broad enough to justify what\nhappened here.\n\n The Government clearly has the inherent authority to\ndecide not to retry Wright given all of the circumstances in this\ncase, including the seemingly improbable account of what\nhappened, 11 the conflicting nature of the police testimony and\nthe jurors’ apparent trouble with it, the fact that there is no\nadditional evidence to offer at a third trial, and Wright’s\napparent steps toward rehabilitation since the offense which\ndisqualified him from lawfully owning a firearm, as well as any\nother factors that the Government might appropriately\nconsider. 12 However, I can find no authority that convinces me\nthat the United States Supreme Court would agree that a trial\ncourt’s inherent authority allows it to dismiss an indictment\nwith prejudice on this record.\n\n III.\n\n\n\n11\n According to the officers’ accounts, they watched (in the\nopen and without cover) as Wright fumbled in the back of a\ncar with tinted windows and came out holding a gun. They\nthen continued to stand and watch from approximately 25\nyards away—without cover and without taking any actions to\nprotect themselves—as he attempted to rack the slide which\nwould have placed a bullet in the chamber.\n12\n Appellee argues without contradiction that:\n\n [f]ollowing early involvement with the criminal\n justice system, Mr. Wright began to turn his life\n around, returning to school and earning his\n Associates degree in Computer Management-\n Networking Engineering Technology[,] . . . a\n Bachelor of Science degree in Information\n Technology and Management . . . graduating\n cum laude[,] . . . and . . . a Master of Science\n degree.\n\nAppellee Br. at 52.\n 5\n\n As I noted at the outset, the Government agrees that\nsuccessive prosecutions can rise to the level of a Due Process\nviolation, which a court clearly could remedy by dismissing an\nindictment. However, the Government strenuously argues\nWright’s prosecution has not yet reached that point. The\nGovernment’s position inherently argues that the court’s action\nhere is also not justified by any concept of fundamental\nfairness. In Ake v. Oklahoma, 13 the Supreme Court observed\nthat the right to Due Process includes the “guarantee of\nfundamental fairness.” 14 As has been discussed by Judge\nShwartz, the District Court here relied on the decision of the\nNew Jersey Supreme Court in State v. Abbati. 15 There, the\nNew Jersey Supreme Court affirmed a trial court’s dismissal of\nan indictment with prejudice after two juries deadlocked,\nresulting in mistrials. 16 That situation is on “all fours” with the\ncircumstances here and the District Court relied heavily on that\ndecision to justify its action and fashion a rule that would\nproperly allow a trial court to dismiss an indictment with\nprejudice under certain circumstances. 17\n\n However, the New Jersey Supreme Court based its\ndecision on the inherent authority of state courts under the New\nJersey Constitution. 18 It did not purport to rest its decision on\nthe U.S. Constitution and, with very limited exception, it cited\nto state judicial decisions—not federal ones—in discussing\nwhen consecutive hung juries justified dismissing an\nindictment with prejudice. 19 The holding of the Court is\n\n13\n 470 U.S. 68 (1985).\n14\n Id. at 76.\n15\n 493 A.2d 513 (N.J. 1985).\n16\n Id. at 522.\n17\n See United States v. Wright, Crim A No. 14-292, 2017 WL\n1179006, at *3, *4 (W.D. Pa. Mar. 30, 2017).\n18\n Abbati, 493 A.3d at 517–18.\n19\n Abbati cited to Ake, for the general proposition that the\n“requirement of fundamental fairness [is] grounded in [the]\nfourteenth amendment’s due process guarantee.” 493 A.2d at\n518. However, with the exception of a single District Court\ncase, the Court cited numerous state court cases for the\nproposition that a trial court had the inherent authority to\ndismiss an indictment with prejudice after two juries\ndeadlocked. Id. at 519–20. It concluded by finding “[t]hese\n 6\n\nsummarized in its statement that the “judicial responsibility for\nthe proper administration of criminal justice also gives rise to\nthe inherent power to dismiss an indictment in appropriate\ncircumstances.” 20\n\n The Abbati standard has not been discussed by this\nCourt (aside from in the instant case), let alone adopted by it.\nAlthough some of the factors used by the New Jersey Supreme\nCourt are analogous to considerations federal courts have made\nin similar federal cases, such as United States v. Ingram 21 and\nUnited States v. Rossoff, 22 Abbati has no real corollary in\nfederal case law. 23\n\nexamples of the courts’ exercise of their power to administer\nthe criminal justice system assist in answering the further\nargument of the State that recognition of an inherent judicial\npower to dismiss an indictment with prejudice would overstep\nthe separation of powers.” Id. at 520. Abbati dismissed that\nargument based upon its belief that “[t]he separation of\npowers is not an end in itself, but a general principle intended\nto ensure that the system of checks and balances remains\nvital.” Id. at 521 (citing State v. Leonardis, 375 A.2d 607, 612\n(N.J. 1977)).\n20\n Id. at 520.\n21\n 412 F. Supp. 384 (D.D.C. 1976). The District Court of the\nDistrict of Columbia dismissed an indictment after two trials\nin which twenty-one of twenty-four jurors voted to acquit.\nThe court found no prosecutorial misconduct. Id. at 386. It\ninstead considered the issue a “matter of fair play,”\nemphasizing that “[t]he Government has no new proof; it\nsimply wants another chance” and “simply wishes to keep\npressing so long as juries disagree in the hope that a\nconviction eventually will result.” Id. at 385.\n22\n 806 F. Supp. 200 (C.D. Ill. 1992).\n23\n For example, the first prong of Abbati’s analysis concerns\nthe number of mistrials and the outcome of the juries’\ndeliberations. 493 A.2d at 521. Both Rossoff and Ingram took\nthis into account in dismissing indictments. See Rossoff, 806\nF. Supp. at 203 (naming, as “additional compelling\ncircumstances: 1) the majority of jurors in both cases found\nDr. Rossoff Not Guilty; 2) if not for the allegedly biased juror\nin the second trial, Dr. Rossoff would have been acquitted on\nall counts; 3) the two trials have taken over one solid month\n 7\n\n Accordingly, as I noted at the outset, I am sympathetic\nto the District Court’s efforts given the totality of the\ncircumstances here. However, until Congress or the United\nStates Supreme Court determines otherwise, I agree that we\nhave no alternative but to enter judgment reversing the District\nCourt. I therefore concur in the judgment reversing the District\nCourt’s order.\n\n\n\n\nof the Court’s time”); Ingram, 412 F. Supp. at 385 (“The\nproof was legally sufficient to support a conviction in each\ninstance but the juries simply did not credit the witnesses,\nvoting 10–2 and 11–1 for acquittal.”).\n The Abbati standard is also based on the likelihood of\nany substantial difference in a subsequent trial, which the\nIngram decision also considered. See Ingram, 412 F. Supp. at\n385 (“If another trial takes place there is every reason to\nbelieve the jury will again be divided or will acquit.”).\n Finally, Rossoff and Ingram both made determinations\nsimilar to Abbati’s seventh prong, the status of the individual\nand the impact of a retrial upon the defendant in terms of\nuntoward hardship and unfairness. 483 A.2d at 422; see\nIngram, 412 F. Supp. at 385–86 (“Here is a man in jail now\nmore than seven months primarily because of an offense\nwhich the Government is unable to convince a jury he\ncommitted. . . . To permit a retrial, after 21 of 24 jurors have\nalready refused to convict, is to ignore the reasonable doubt\nstandard.”); Rossoff, 806 F. Supp. at 203 (“Dr. Rossoff is 71\nyears of age and in poor health. He has had heart surgery,\nsuffers from severe anemia and at the time of the second trial\nwas on experimental treatment. He has been under great\nphysical and emotional strain as the result of these repeated\ntrials and was even hospitalized immediately following the\nsecond trial.”).\n\n 8", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360237/", "author_raw": "McKEE, Circuit Judge, concurring"}]}
MCKEE
SHWARTZ
NYGAARD
1
{"MCKEE": ", Circuit", "SHWARTZ": ", Circuit", "NYGAARD": ", Circuit"}
4
0
2
1
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582984/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Raymont Wright\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014.1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13\n[END_CASE]", "role": "user" } ]
4,582,985
Carlyle BRYAN ; Julie Beberman; Charles Francis, Appellants v. UNITED STATES of America; Unknown Officers of the Department of Homeland Security; Bureau of Customs & Border Protection; Customs and Border Protection Officers John Mazur; Jamie Demarais; Obed Torres; William Santiago ; Orlando Baez; Timothy Ogg; Andres Vazquez ; Joel Osorio; Juan Gracia; Gregory Defelice
Carlyle Bryan v. United States
2019-01-18
17-1519
U.S. Court of Appeals for the Third Circuit
{"judges": "Krause, Roth, Fisher", "parties": "", "opinions": [{"author": "ROTH, Circuit Judge", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 17-1519\n ________________\n\n CARLYLE BRYAN; JULIE BEBERMAN;\n CHARLES FRANCIS,\n\n Appellants\n\n v.\n\nUNITED STATES OF AMERICA; UNKNOWN OFFICERS OF THE DEPARTMENT\nOF HOMELAND SECURITY; BUREAU OF CUSTOMS & BORDER PROTECTION;\n CUSTOMS AND BORDER PROTECTION OFFICERS JOHN MAZUR;\n JAMIE DEMARAIS; OBED TORRES; WILLIAM SANTIAGO;\n ORLANDO BAEZ; TIMOTHY OGG; ANDRES VAZQUEZ;\n JOEL OSORIO; JUAN GRACIA; GREGORY DEFELICE\n ________________\n\n Appeal from the District Court of the Virgin Islands\n (Division of St. Croix)\n (D.C. Civil Action No. 1-10-cv-00066)\n District Judge: Honorable Wilma A. Lewis\n ________________\n\n Argued on May 22, 2018\n\n Before: KRAUSE, ROTH and FISHER, Circuit Judges\n\n (Opinion filed: January 18, 2019)\n\n\nDavid M. Nissman, (Argued)\nMcChain Nissman Law Group\n53A Company Street\nChristiansted, VI 00820\n\n Counsel for Appellants\n\fSamantha L. Chaifetz (Argued)\nJoycelyn Hewett\nChad A. Readler\nMark B. Stern\nUnited States Department of Justice\nAppellate Section\nRoom 7248\n950 Pennsylvania Avenue, N.W.\nWashington, DC 20530\n\nJeffrey E. Sandberg\nUnited States Department of Justice\nCivil Division\nRoom 7214\n950 Pennsylvania Avenue, N.W.\nWashington, DC 20530\n\n Counsel for Appellee\n\n\n ________________\n\n OPINION\n ________________\n\nROTH, Circuit Judge\n\n In 2008, Carlyle Bryan, Julie Beberman, and Charles Francis (the travelers),\nresidents of St. Croix in the U.S. Virgin Islands, embarked on a Caribbean cruise aboard\nthe Adventure of the Seas. Their trip took them to a number of foreign ports before they\nreturned to the United States. During their trip, U.S. Customs and Border Protection\n(CBP) officers searched their cabins on suspicion of drug-smuggling activity. Those\nsearches yielded no contraband and prompted the three travelers to assert Bivens claims1\nagainst the officers for allegedly violating their Fourth Amendment rights. They also\nasserted tort claims against the United States government under the Federal Tort Claims\nAct (FTCA or the Act). The District Court of the Virgin Islands granted summary\njudgment in favor of the officers and the government.\n\n\n\n1 Bivens provides for private rights of action against federal officials for certain\nconstitutional violations. Bivens v. Six Unknown Named Agents of Federal Bureau of\nNarcotics, 403 U.S. 388 (1971).\n 2\n\f Because we conclude that the officers are entitled to qualified immunity and the\nUnited States government is shielded from liability under the FTCA’s discretionary\nfunction exception, we will affirm.\n\n I.\n\n The Cruise\n\n The cruise lasted from August 31 to September 7, 2008. Beberman had booked\ntwo cabins for the three travelers: one for Bryan and herself, and a second for Francis.\nThe cruise began in the United States. They sailed from San Juan, Puerto Rico, stopped\nat several foreign ports, including Antigua, Barbados, St. Lucia, and St. Maarten,\nproceeded to St. Thomas in the U.S. Virgin Islands, and returned to San Juan.\n\n The travelers had to pass through a CBP checkpoint in San Juan before boarding\nthe ship. Bryan and Beberman went through without incident. Francis’s trip through the\ncheckpoint was not so smooth. When a CBP officer asked Francis what his occupation\nwas, he hesitated and then said “oil change.” (Francis worked with automobiles and\nchanged motor oil.) CBP officers then inspected Francis’s bag. There was a very full\ncanister of shaving powder in the bag. When a CBP officer opened the canister, the\npowder dispersed through the room and coated the officer. Bryan laughed. They contend\nnow that the inspection of their cabins was in retaliation for Bryan’s laughing at the CBP\nofficer. The officers found nothing unlawful in Francis’s bags. CBP Officer Baez made\na notation in the Treasury Enforcement Communications System (TECS) database that\nFrancis had appeared “disoriented and nervous” and that it took him some time to state\nhis employment, but that the examination of his bag did not uncover anything.2\n\n The Creation of “Lookout” Entries by Officer Timothy Ogg (September 5, 2008)\n\n CBP Officer Timothy Ogg, stationed in San Juan, was routinely assigned the task\nof reviewing passenger manifests for the Adventure of the Seas to identify passengers\nworthy of further scrutiny. Around September 1, he compared the names on the\npassenger manifest against the names on reports logged onto TECS. Both Bryan’s and\nFrancis’s names yielded matches; both had TECS entries related to drug smuggling.\n\n Officer Ogg found two entries on Bryan. The first, dated May 17, 2000, was\nauthored by Immigration & Customs Enforcement (ICE) Agent Hillary Hodge. Referring\nto Bryan, the entry read: “Subject is associate[d] with suspected drug smugglers within\nthe US Virgin Islands. Subject is also suspected of smuggling narcotics within the Virgin\nIslands. If encountered, conduct 100% exam . . ..”3 Officer Ogg later testified that he\n\n2 JA 8.\n3 JA 9.\n 3\n\fhad previously worked with Agent Hodge and credited his entry in part because he\nregarded Hodge as an excellent worker. The second TECS entry, from 2004, referred to\nthe prior entry, characterized Bryan as a “suspect in USVI drug smuggling,” and\nencouraged agents to “document [his] co-travelers, employment and reason for travel.”4\n\n As for Francis, Officer Ogg uncovered two TECS reports from 2006 identifying\nFrancis as the “Subject of [a Drug Enforcement Administration] indictment.” The first\nreport was authored while the Drug Enforcement Administration investigation was going\non and characterized Francis as a “subject of current interest”; the second was authored\nafter the investigation had ended and referred to him as a “Previous Suspect.”5 Both\nreports urged personnel to alert special agents if they encountered Francis.\n\n According to Officer Ogg’s subsequent deposition testimony, another factor\naroused his suspicion: CBP officers had previously made narcotics seizures on the\nAdventure of the Seas on the same route. A number of islands along the route were\nknown to be sources of narcotics smuggled into the United States. Officer Ogg\ncharacterized them as high-risk islands.\n\n On September 5, primarily on the strength of the TECS records concerning Bryan\nand Francis, Officer Ogg created “lookout” entries for Bryan and Francis in the TECS\ndatabase. A “lookout” is a TECS entry that alerts CBP officers to specific passengers and\nrecommends certain investigative steps when they are encountered. In the case of Bryan\nand Francis, the “lookout entries” noted their connection to “drug smuggling” and\nrecommended, in the standard TECS shorthand (i.e., “100% exam”), that their cabins be\ninspected before their return to San Juan on September 7. 6\n\n Officer Ogg also entered a separate “lookout” for Beberman. Except for the co-\ntravelers listed, the “lookout” entry for Beberman mirrored Bryan’s. At his deposition,\nOfficer Ogg gave two reasons for the Beberman “lookout.” First, she was traveling with\ntwo individuals about whom there were independent TECS entries predicated on drug-\nsmuggling concerns. Second, as a practical matter, Officer Ogg stated that he had to\nenter a lookout for Beberman to ensure that Bryan and Francis did not use her to evade\n\n\n\n\n4 JA 9-10.\n5 JA 10.\n6 Id.\n\n\n 4\n\fdetection and inspection by having her submit a single customs declaration form for the\nthree of them, but in her name only.7\n\n The St. Thomas Cabin Searches (September 6, 2008)\n\n On the morning of September 6, 2008, after the travelers had returned to United\nStates waters and had docked in St. Thomas, CBP Officers DeFelice, Demarais, Mazur,\nSantiago, and Torres (collectively, the St. Thomas Officers) inspected Bryan and\nBeberman’s cabin, along with Francis’s.\n\n The cabin searches each lasted between five and ten minutes.8 The St. Thomas\nofficers knocked on the cabin doors before opening them. The occupants were asked to\nget dressed without using the bathroom, and in at least partial view of the officers. They\nwere then asked to leave their cabins and stand against a wall in the hallway. They\nwaited in the hallway for between two and five minutes, while officers with a drug-\nsniffing dog inspected their cabins. Neither cabin search yielded any contraband; the St.\nThomas Officers created TECS entries to that effect.9\n\n II.\n\n As a result of the searches, Beberman, Bryan, and Francis filed suit in the District\nCourt for the Virgin Islands, asserting Fourth Amendment Bivens claims against Officer\nOgg, who had recommended, but not participated in, the cabin searches and against the\nSt. Thomas officers, who had executed the cabin searches. The travelers also asserted\ntort claims against the United States under the FTCA for invasion of privacy, false\nimprisonment, and intentional infliction of emotional distress.\n\n\n7 Ogg testified at his deposition that passengers traveling together were allowed to submit\na single customs declaration form without identifying every passenger. Because\nsecondary inspections were triggered by the names included on declaration forms, Bryan\nand Francis could have attempted to evade detection by having Beberman submit a form\nin her name only. Officer Ogg explained that he had entered three separate “lookouts” to\nguard against that possibility.\n8 The cabin inspections differed in two respects: The occupants found themselves in\n\ndifferent states of undress (i.e., Francis was naked, while Bryan and Beberman were\npartially clothed) and the occupants were observed to different extents while they dressed\n(i.e., Bryan and Beberman dressed with their cabin door ajar and the officers outside,\nwhile Francis dressed in full view of the officers).\n9 On September 7, when the ship reached San Juan, a different set of CBP officers began\n\nto inspect the travelers’ cabins but cut short the searches when they learned of the St.\nThomas searches. The San Juan searches are not implicated in this appeal. The travelers\nvoluntarily dismissed their Bivens claims against the San Juan officers.\n 5\n\f At the close of discovery, the officers and the United States moved for summary\njudgment. The District Court granted their motion on all claims.\n\n As for the officers, the District Court reasoned that neither Officer Ogg’s entry of\n“lookouts” nor the St. Thomas cabin searches violated the travelers’ Fourth Amendment\nrights. Further, it held that the officers were entitled to qualified immunity because their\nconduct did not violate clearly established Fourth Amendment rights.\n\n As for the United States, the District Court held that the FTCA claims were barred\nby the Act’s discretionary function exception.\n\n We review the District Court’s grant of summary judgment de novo, applying the\nsame decisional principle.10 The District Court exercised subject matter jurisdiction\nunder 28 U.S.C. §§ 1331 and 1346(b). We have appellate jurisdiction under 28 U.S.C. §\n1291.\n\n III.\n\n The Fourth Amendment protects the public “against unreasonable searches and\nseizures.”11 Whether a search is reasonable turns on “all of the circumstances\nsurrounding the search,” including where the search took place. 12\n\n The search here took place at the border. The border serves a unique gate-keeping\nfunction. Our controlling Fourth Amendment precedent is attuned to that reality. The\nSupreme Court has stressed the border’s role in protecting our territorial sovereignty,\nalong with the need to curb the inflow of drugs at the border. 13 For those reasons, we\nextend the government special latitude at the border and strike “the Fourth Amendment\nbalance between the interests of the Government and the privacy right of the individual”\nin the government’s favor.14\n\n10 Summary judgment should be granted when, “after drawing all reasonable inferences\nfrom the underlying facts in the light most favorable to the nonmoving party, the court\nconcludes that there is no genuine issue of material fact to be resolved at trial and the\nmoving party is entitled to judgment as a matter of law.” Petruzzi’s IGA Supermarkets,\nInc. v. Darling-Delaware Co., 998 F.2d 1224, 1230 (3d Cir. 1993).\n11 U.S. Const. amend. IV.\n12 United States v. Montoya de Hernandez, 473 U.S. 531, 537 (1985).\n13 See Montoya, 473 U.S. at 538 (highlighting a “longstanding concern for the protection\n\nof the integrity of the border. This concern is, if anything, heightened by the veritable\nnational crisis in law enforcement caused by smuggling of illicit narcotics . . ..”) (citation\nomitted); see also Bradley v. United States, 299 F.3d 197, 201-02 (3d Cir. 2002).\n14 Montoya, 473 U.S. at 539-40; see also United States v. Hyde, 37 F.3d 116, 119-20 (3d\n\nCir. 1994).\n 6\n\f In view of the government’s interests, we “have long held that routine searches at\nour nation’s borders are presumed to be reasonable under the Fourth Amendment.” 15\nIndeed, “[r]outine searches of the persons and effects of entrants are not subject to any\nrequirement of reasonable suspicion, probable cause, or warrant . . ..”16 In contrast,\n“nonroutine searches . . . require reasonable suspicion.”17 This approach to border\nsearches applies with equal force at “the functional equivalent” of the border,18 such as a\nship’s first port of call in the United States. 19 Under this standard, the search here was a\nborder search.\n\n On September 4, 2008, a day before Officer Ogg entered “lookouts” for the\ntravelers and two days before the cabin searches, we ruled for the first time on the\nconstitutional propriety of border searches in the same context presented in this appeal —\nin remarkable coincidence, searches of cabins aboard the Adventure of the Seas. 20 In\nUnited States v. Whitted, we acknowledged “the surprising dearth of authority” on\nwhether a search of a cruise ship cabin at the border is a routine search requiring no\nsuspicion, or a non-routine search requiring “reasonable suspicion” (i.e., a “particularized\nand objective basis” to suspect criminal activity).21 We held for the first time that\nbecause of a passenger’s “high expectation of privacy” and the “level of intrusiveness,” a\nsearch of a cruise ship cabin at the border is non-routine and requires reasonable\nsuspicion.22 We also held that unsubstantiated information from TECS can establish\nreasonable suspicion.23\n\n IV.\n\n In considering whether a government official is entitled to qualified immunity, a\ncourt can determine whether a constitutional right was violated or in the alternative,\nwhether that right was clearly established.24 Following that precedent, we will not opine\nas to whether there were underlying Fourth Amendment violations involved in the search\nhere. We will instead determine whether the Whitted standard, that a search of a cabin on\na cruise ship required reasonable suspicion, was clearly established when Officer Ogg\nincluded in his entry of “lookouts” in the TECS System that 100 % examination of the\n\n15 Bradley, 299 F.3d at 201 (citations omitted).\n16 Montoya, 473 U.S. at 538 (footnote omitted).\n17 Bradley, 299 F.3d at 204 n.8 (citation omitted).\n18 Almeida-Sanchez v. United States, 413 U.S. 266, 272-73 (1973).\n19 United States v. Smith, 273 F.3d 629, 633 n.8 (5th Cir. 2001) (citation omitted).\n20 United States v. Whitted, 541 F.3d 480 (3d Cir. 2008).\n21 Whitted, 541 F.3d at 486, 489.\n22 Id. at 489.\n23 Id. at 490.\n24 Pearson v. Callahan, 555 U.S. 223, 236 (2009).\n\n\n 7\n\fthree travelers, i.e., examination of their cabins, was recommended and the next day\nwhen the St. Thomas officers searched the travelers’ cabins.\n\n The doctrine of qualified immunity shields government officials from Bivens\nclaims and money damages, unless a plaintiff can establish that the official violated a\nstatutory or constitutional right, and that the right was “clearly established at the time of\nthe challenged conduct.”25 To be clearly established, a right’s contours must be\n“sufficiently definite that any reasonable official in the defendant’s shoes would have\nunderstood that he was violating it” and that “existing precedent . . . placed the statutory\nor constitutional question confronted by the official beyond debate.” 26\n\n Further, as the Supreme Court recently reiterated, “clearly established law should\nnot be defined at a high level of generality” but must instead “be particularized to the\nfacts of the case.”27 The doctrine is designed to “give[] government officials breathing\nroom to make reasonable but mistaken judgments by protect[ing] all but the plainly\nincompetent or those who knowingly violate the law.”28\n\n Supreme Court discussion of searches has emphasized the threats posed at borders\nand the government’s compelling interests in searches there. 29 Because the government’s\ninterest in preventing the entry of unwarranted persons and effects is at its zenith at the\nborder,30 Congress “has granted the Executive plenary authority to conduct routine\nsearches and seizures at the border, without probable cause or a warrant . . ..”31 Until\nSeptember 4, 2008, there had been no ruling in the Third Circuit as to what constituted a\n“routine search.” As for Officer Ogg, he was located in San Juan, Puerto Rico, in the\nFirst Circuit. There had not been any such ruling in the First Circuit, and the First Circuit\ncourts would not be bound by Whitted, a Third Circuit case.\n\n When such a ruling is made, a ruling which affects the procedures used in border\nsearches, it is beyond belief that within two days the government could determine what\nwas “reasonable suspicion” and what new policy was required to conform to the ruling,\nmuch less communicate that new policy to the CBP officers. We can only conclude that\nas of September 5, 2008, it was not clearly established in either the Third Circuit or the\nFirst Circuit that a search of a cruise ship cabin at the border had to be supported by\n\n25 Ashcroft v. al-Kidd, 563 U.S. 731, 735 (2011) (citing Harlow v. Fitzgerald, 457 U.S.\n800, 818 (1982)).\n26 Plumhoff v. Rickard, 134 S. Ct. 2012, 2023 (2014) (quoting Ashcroft, 563 U.S. at 741).\n27 White v. Pauly, 137 S. Ct. 548, 552 (2017) (per curiam) (citation omitted); see also\n\nL.R. v. Sch. Dist. of Phila., 836 F.3d 235, 248 (3d Cir. 2016).\n28 City & Cty. of S.F. v. Sheehan, 135 S. Ct. 1765, 1774 (2015) (citation omitted).\n29 See, e.g., Montoya, 473 U.S. at 539-40.\n30 United States v. Flores-Montano, 541 U.S. 149, 152-53 (2004).\n31 Id. at 153.\n\n\n 8\n\freasonable suspicion. Accordingly, under the circumstances that Officer Ogg confronted,\nhe did not violate clearly established law by entering lookouts for the three passengers the\nday after we issued our decision in Whitted. He is entitled to qualified immunity.\n\n We conclude that the same situation applies to the St. Thomas officers. On\nSeptember 6, the Whitted standard was no more clearly established than it had been the\nday before. Moreover, if the St. Thomas officers had been aware of Whitted, they would\nhave known that Whitted held that unsubstantiated information from TECS can establish\nreasonable suspicion.32\n\n For these reasons, we conclude that the Whitted standard was not clearly\nestablished in the Third Circuit, or the First Circuit, on September 5 or 6. Within one or\ntwo days, neither Officer Ogg nor the St. Thomas officers could reasonably be expected\nto have learned of this development in our Fourth Amendment jurisprudence. At that\ntime, it would not have been beyond debate that, absent reasonable suspicion, the Fourth\nAmendment prohibited the search of the travelers’ cabins. For purposes of qualified\nimmunity, a legal principle does not become “clearly established” the day we announce a\ndecision, or even one or two days later.\n\n This holding is informed by the overarching aim of the qualified immunity\ndoctrine to insulate from civil liability “all but the plainly incompetent or those who\nknowingly violate the law,”33 and the need to ensure that the relevant legal principle is\nframed with particularity34 and settled “beyond debate.”35 We are, however, deciding\nonly this case. For that reason, we decline to draw a bright line demarcating when a legal\nprinciple becomes “clearly established.” We leave that exercise for another day.\n\n Finally, the tort claims against the United States also fail because of the FTCA’s\ndiscretionary function exception. The FTCA provides a limited waiver of sovereign\nimmunity in certain tort actions against the United States for money damages.36 That\nwaiver does not extend to various types of government conduct enumerated in 28 U.S.C.\n\n\n\n\n32 541 F.3d at 490.\n33 White, 137 S. Ct. at 552.\n34 Id.\n35 Plumhoff, 134 S. Ct. at 2023.\n36 28 U.S.C. § 1346(b)(1).\n\n\n 9\n\f§ 2680, including “the exercise or performance or the failure to exercise or perform a\ndiscretionary function or duty . . . whether or not the discretion involved be abused.”37\n\n The travelers do not dispute that Officer Ogg’s entry of “lookouts” and the\nsearches that followed were discretionary acts under the “discretionary function”\nexception.38 Rather, they argue that the United States is not shielded from liability\nbecause the officers in this case, though exercising their discretion, violated “clearly\nestablished . . . constitutional rights of which a reasonable person would have known.” 39\n\n Because, for the reasons set out above, the CBP officers did not violate clearly\nestablished constitutional rights, the FTCA claims also fail.\n\n V.\n\n For the reasons stated above, we will affirm the judgment of the District Court.\n\n\n\n\n37 28 U.S.C. § 2680(a). Discretionary acts and omissions “involv[e] an element of\njudgment or choice.” Conduct is non-discretionary only if a “federal statute, regulation,\nor policy specifically prescribes a course of action for an employee to follow” and the\ngovernment “employee has no rightful option but to adhere to the directive.” United\nStates v. Gaubert, 499 U.S. 315, 322 (1991) (quoting Berkovitz ex rel. Berkovitz v. United\nStates, 486 U.S. 531, 536 (1988)).\n38 Br. at 63-64.\n39 Harlow, 457 U.S. at 818.\n\n\n 10", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360238/", "author_raw": "ROTH, Circuit Judge"}]}
KRAUSE
ROTH
FISHER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582985/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Carlyle BRYAN ; Julie Beberman; Charles Francis, Appellants v. UNITED STATES of America; Unknown Officers of the Department of Homeland Security; Bureau of Customs & Border Protection; Customs and Border Protection Officers John Mazur; Jamie Demarais; Obed Torres; William Santiago ; Orlando Baez; Timothy Ogg; Andres Vazquez ; Joel Osorio; Juan Gracia; Gregory Defelice\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 17-1519\n ________________\n\n CARLYLE BRYAN; JULIE BEBERMAN;\n CHARLES FRANCIS,\n\n Appellants\n\n v.\n\nUNITED STATES OF AMERICA; UNKNOWN OFFICERS OF THE DEPARTMENT\nOF HOMELAND SECURITY; BUREAU OF CUSTOMS & BORDER PROTECTION;\n CUSTOMS AND BORDER PROTECTION OFFICERS JOHN MAZUR;\n JAMIE DEMARAIS; OBED TORRES; WILLIAM SANTIAGO;\n ORLANDO BAEZ; TIMOTHY OGG; ANDRES VAZQUEZ;\n JOEL OSORIO; JUAN GRACIA; GREGORY DEFELICE\n ________________\n\n Appeal from the District Court of the Virgin Islands\n (Division of St. Croix)\n (D.C. Civil Action No. 1-10-cv-00066)\n District Judge: Honorable Wilma A. Lewis\n ________________\n\n Argued on May 22, 2018\n\n Before: KRAUSE, ROTH and FISHER, Circuit Judges\n\n (Opinion filed: January 18, 2019)\n\n\nDavid M. Nissman, (Argued)\nMcChain Nissman Law Group\n53A Company Street\nChristiansted, VI 00820\n\n Counsel for Appellants\n\fSamantha L. Chaifetz (Argued)\nJoycelyn Hewett\nChad A. Readler\nMark B. Stern\nUnited States Department of Justice\nAppellate Section\nRoom 7248\n950 Pennsylvania Avenue, N.W.\nWashington, DC 20530\n\nJeffrey E. Sandberg\nUnited States Department of Justice\nCivil Division\nRoom 7214\n950 Pennsylvania Avenue, N.W.\nWashington, DC 20530\n\n Counsel for Appellee\n\n\n ________________\n\n OPINION\n ________________\n\nROTH, Circuit Judge\n\n In 2008, Carlyle Bryan, Julie Beberman, and Charles Francis (the travelers),\nresidents of St. Croix in the U.S. Virgin Islands, embarked on a Caribbean cruise aboard\nthe Adventure of the Seas. Their trip took them to a number of foreign ports before they\nreturned to the United States. During their trip, U.S. Customs and Border Protection\n(CBP) officers searched their cabins on suspicion of drug-smuggling activity. Those\nsearches yielded no contraband and prompted the three travelers to assert Bivens claims1\nagainst the officers for allegedly violating their Fourth Amendment rights. They also\nasserted tort claims against the United States government under the Federal Tort Claims\nAct (FTCA or the Act). The District Court of the Virgin Islands granted summary\njudgment in favor of the officers and the government.\n\n\n\n1 Bivens provides for private rights of action against federal officials for certain\nconstitutional violations. Bivens v. Six Unknown Named Agents of Federal Bureau of\nNarcotics, 403 U.S. 388 (1971).\n 2\n\f Because we conclude that the officers are entitled to qualified immunity and the\nUnited States government is shielded from liability under the FTCA’s discretionary\nfunction exception, we will affirm.\n\n I.\n\n The Cruise\n\n The cruise lasted from August 31 to September 7, 2008. Beberman had booked\ntwo cabins for the three travelers: one for Bryan and herself, and a second for Francis.\nThe cruise began in the United States. They sailed from San Juan, Puerto Rico, stopped\nat several foreign ports, including Antigua, Barbados, St. Lucia, and St. Maarten,\nproceeded to St. Thomas in the U.S. Virgin Islands, and returned to San Juan.\n\n The travelers had to pass through a CBP checkpoint in San Juan before boarding\nthe ship. Bryan and Beberman went through without incident. Francis’s trip through the\ncheckpoint was not so smooth. When a CBP officer asked Francis what his occupation\nwas, he hesitated and then said “oil change.” (Francis worked with automobiles and\nchanged motor oil.) CBP officers then inspected Francis’s bag. There was a very full\ncanister of shaving powder in the bag. When a CBP officer opened the canister, the\npowder dispersed through the room and coated the officer. Bryan laughed. They contend\nnow that the inspection of their cabins was in retaliation for Bryan’s laughing at the CBP\nofficer. The officers found nothing unlawful in Francis’s bags. CBP Officer Baez made\na notation in the Treasury Enforcement Communications System (TECS) database that\nFrancis had appeared “disoriented and nervous” and that it took him some time to state\nhis employment, but that the examination of his bag did not uncover anything.2\n\n The Creation of “Lookout” Entries by Officer Timothy Ogg (September 5, 2008)\n\n CBP Officer Timothy Ogg, stationed in San Juan, was routinely assigned the task\nof reviewing passenger manifests for the Adventure of the Seas to identify passengers\nworthy of further scrutiny. Around September 1, he compared the names on the\npassenger manifest against the names on reports logged onto TECS. Both Bryan’s and\nFrancis’s names yielded matches; both had TECS entries related to drug smuggling.\n\n Officer Ogg found two entries on Bryan. The first, dated May 17, 2000, was\nauthored by Immigration & Customs Enforcement (ICE) Agent Hillary Hodge. Referring\nto Bryan, the entry read: “Subject is associate[d] with suspected drug smugglers within\nthe US Virgin Islands. Subject is also suspected of smuggling narcotics within the Virgin\nIslands. If encountered, conduct 100% exam . . ..”3 Officer Ogg later testified that he\n\n2 JA 8.\n3 JA 9.\n 3\n\fhad previously worked with Agent Hodge and credited his entry in part because he\nregarded Hodge as an excellent worker. The second TECS entry, from 2004, referred to\nthe prior entry, characterized Bryan as a “suspect in USVI drug smuggling,” and\nencouraged agents to “document [his] co-travelers, employment and reason for travel.”4\n\n As for Francis, Officer Ogg uncovered two TECS reports from 2006 identifying\nFrancis as the “Subject of [a Drug Enforcement Administration] indictment.” The first\nreport was authored while the Drug Enforcement Administration investigation was going\non and characterized Francis as a “subject of current interest”; the second was authored\nafter the investigation had ended and referred to him as a “Previous Suspect.”5 Both\nreports urged personnel to alert special agents if they encountered Francis.\n\n According to Officer Ogg’s subsequent deposition testimony, another factor\naroused his suspicion: CBP officers had previously made narcotics seizures on the\nAdventure of the Seas on the same route. A number of islands along the route were\nknown to be sources of narcotics smuggled into the United States. Officer Ogg\ncharacterized them as high-risk islands.\n\n On September 5, primarily on the strength of the TECS records concerning Bryan\nand Francis, Officer Ogg created “lookout” entries for Bryan and Francis in the TECS\ndatabase. A “lookout” is a TECS entry that alerts CBP officers to specific passengers and\nrecommends certain investigative steps when they are encountered. In the case of Bryan\nand Francis, the “lookout entries” noted their connection to “drug smuggling” and\nrecommended, in the standard TECS shorthand (i.e., “100% exam”), that their cabins be\ninspected before their return to San Juan on September 7. 6\n\n Officer Ogg also entered a separate “lookout” for Beberman. Except for the co-\ntravelers listed, the “lookout” entry for Beberman mirrored Bryan’s. At his deposition,\nOfficer Ogg gave two reasons for the Beberman “lookout.” First, she was traveling with\ntwo individuals about whom there were independent TECS entries predicated on drug-\nsmuggling concerns. Second, as a practical matter, Officer Ogg stated that he had to\nenter a lookout for Beberman to ensure that Bryan and Francis did not use her to evade\n\n\n\n\n4 JA 9-10.\n5 JA 10.\n6 Id.\n\n\n 4\n\fdetection and inspection by having her submit a single customs declaration form for the\nthree of them, but in her name only.7\n\n The St. Thomas Cabin Searches (September 6, 2008)\n\n On the morning of September 6, 2008, after the travelers had returned to United\nStates waters and had docked in St. Thomas, CBP Officers DeFelice, Demarais, Mazur,\nSantiago, and Torres (collectively, the St. Thomas Officers) inspected Bryan and\nBeberman’s cabin, along with Francis’s.\n\n The cabin searches each lasted between five and ten minutes.8 The St. Thomas\nofficers knocked on the cabin doors before opening them. The occupants were asked to\nget dressed without using the bathroom, and in at least partial view of the officers. They\nwere then asked to leave their cabins and stand against a wall in the hallway. They\nwaited in the hallway for between two and five minutes, while officers with a drug-\nsniffing dog inspected their cabins. Neither cabin search yielded any contraband; the St.\nThomas Officers created TECS entries to that effect.9\n\n II.\n\n As a result of the searches, Beberman, Bryan, and Francis filed suit in the District\nCourt for the Virgin Islands, asserting Fourth Amendment Bivens claims against Officer\nOgg, who had recommended, but not participated in, the cabin searches and against the\nSt. Thomas officers, who had executed the cabin searches. The travelers also asserted\ntort claims against the United States under the FTCA for invasion of privacy, false\nimprisonment, and intentional infliction of emotional distress.\n\n\n7 Ogg testified at his deposition that passengers traveling together were allowed to submit\na single customs declaration form without identifying every passenger. Because\nsecondary inspections were triggered by the names included on declaration forms, Bryan\nand Francis could have attempted to evade detection by having Beberman submit a form\nin her name only. Officer Ogg explained that he had entered three separate “lookouts” to\nguard against that possibility.\n8 The cabin inspections differed in two respects: The occupants found themselves in\n\ndifferent states of undress (i.e., Francis was naked, while Bryan and Beberman were\npartially clothed) and the occupants were observed to different extents while they dressed\n(i.e., Bryan and Beberman dressed with their cabin door ajar and the officers outside,\nwhile Francis dressed in full view of the officers).\n9 On September 7, when the ship reached San Juan, a different set of CBP officers began\n\nto inspect the travelers’ cabins but cut short the searches when they learned of the St.\nThomas searches. The San Juan searches are not implicated in this appeal. The travelers\nvoluntarily dismissed their Bivens claims against the San Juan officers.\n 5\n\f At the close of discovery, the officers and the United States moved for summary\njudgment. The District Court granted their motion on all claims.\n\n As for the officers, the District Court reasoned that neither Officer Ogg’s entry of\n“lookouts” nor the St. Thomas cabin searches violated the travelers’ Fourth Amendment\nrights. Further, it held that the officers were entitled to qualified immunity because their\nconduct did not violate clearly established Fourth Amendment rights.\n\n As for the United States, the District Court held that the FTCA claims were barred\nby the Act’s discretionary function exception.\n\n We review the District Court’s grant of summary judgment de novo, applying the\nsame decisional principle.10 The District Court exercised subject matter jurisdiction\nunder 28 U.S.C. §§ 1331 and 1346(b). We have appellate jurisdiction under 28 U.S.C. §\n1291.\n\n III.\n\n The Fourth Amendment protects the public “against unreasonable searches and\nseizures.”11 Whether a search is reasonable turns on “all of the circumstances\nsurrounding the search,” including where the search took place. 12\n\n The search here took place at the border. The border serves a unique gate-keeping\nfunction. Our controlling Fourth Amendment precedent is attuned to that reality. The\nSupreme Court has stressed the border’s role in protecting our territorial sovereignty,\nalong with the need to curb the inflow of drugs at the border. 13 For those reasons, we\nextend the government special latitude at the border and strike “the Fourth Amendment\nbalance between the interests of the Government and the privacy right of the individual”\nin the government’s favor.14\n\n10 Summary judgment should be granted when, “after drawing all reasonable inferences\nfrom the underlying facts in the light most favorable to the nonmoving party, the court\nconcludes that there is no genuine issue of material fact to be resolved at trial and the\nmoving party is entitled to judgment as a matter of law.” Petruzzi’s IGA Supermarkets,\nInc. v. Darling-Delaware Co., 998 F.2d 1224, 1230 (3d Cir. 1993).\n11 U.S. Const. amend. IV.\n12 United States v. Montoya de Hernandez, 473 U.S. 531, 537 (1985).\n13 See Montoya, 473 U.S. at 538 (highlighting a “longstanding concern for the protection\n\nof the integrity of the border. This concern is, if anything, heightened by the veritable\nnational crisis in law enforcement caused by smuggling of illicit narcotics . . ..”) (citation\nomitted); see also Bradley v. United States, 299 F.3d 197, 201-02 (3d Cir. 2002).\n14 Montoya, 473 U.S. at 539-40; see also United States v. Hyde, 37 F.3d 116, 119-20 (3d\n\nCir. 1994).\n 6\n\f In view of the government’s interests, we “have long held that routine searches at\nour nation’s borders are presumed to be reasonable under the Fourth Amendment.” 15\nIndeed, “[r]outine searches of the persons and effects of entrants are not subject to any\nrequirement of reasonable suspicion, probable cause, or warrant . . ..”16 In contrast,\n“nonroutine searches . . . require reasonable suspicion.”17 This approach to border\nsearches applies with equal force at “the functional equivalent” of the border,18 such as a\nship’s first port of call in the United States. 19 Under this standard, the search here was a\nborder search.\n\n On September 4, 2008, a day before Officer Ogg entered “lookouts” for the\ntravelers and two days before the cabin searches, we ruled for the first time on the\nconstitutional propriety of border searches in the same context presented in this appeal —\nin remarkable coincidence, searches of cabins aboard the Adventure of the Seas. 20 In\nUnited States v. Whitted, we acknowledged “the surprising dearth of authority” on\nwhether a search of a cruise ship cabin at the border is a routine search requiring no\nsuspicion, or a non-routine search requiring “reasonable suspicion” (i.e., a “particularized\nand objective basis” to suspect criminal activity).21 We held for the first time that\nbecause of a passenger’s “high expectation of privacy” and the “level of intrusiveness,” a\nsearch of a cruise ship cabin at the border is non-routine and requires reasonable\nsuspicion.22 We also held that unsubstantiated information from TECS can establish\nreasonable suspicion.23\n\n IV.\n\n In considering whether a government official is entitled to qualified immunity, a\ncourt can determine whether a constitutional right was violated or in the alternative,\nwhether that right was clearly established.24 Following that precedent, we will not opine\nas to whether there were underlying Fourth Amendment violations involved in the search\nhere. We will instead determine whether the Whitted standard, that a search of a cabin on\na cruise ship required reasonable suspicion, was clearly established when Officer Ogg\nincluded in his entry of “lookouts” in the TECS System that 100 % examination of the\n\n15 Bradley, 299 F.3d at 201 (citations omitted).\n16 Montoya, 473 U.S. at 538 (footnote omitted).\n17 Bradley, 299 F.3d at 204 n.8 (citation omitted).\n18 Almeida-Sanchez v. United States, 413 U.S. 266, 272-73 (1973).\n19 United States v. Smith, 273 F.3d 629, 633 n.8 (5th Cir. 2001) (citation omitted).\n20 United States v. Whitted, 541 F.3d 480 (3d Cir. 2008).\n21 Whitted, 541 F.3d at 486, 489.\n22 Id. at 489.\n23 Id. at 490.\n24 Pearson v. Callahan, 555 U.S. 223, 236 (2009).\n\n\n 7\n\fthree travelers, i.e., examination of their cabins, was recommended and the next day\nwhen the St. Thomas officers searched the travelers’ cabins.\n\n The doctrine of qualified immunity shields government officials from Bivens\nclaims and money damages, unless a plaintiff can establish that the official violated a\nstatutory or constitutional right, and that the right was “clearly established at the time of\nthe challenged conduct.”25 To be clearly established, a right’s contours must be\n“sufficiently definite that any reasonable official in the defendant’s shoes would have\nunderstood that he was violating it” and that “existing precedent . . . placed the statutory\nor constitutional question confronted by the official beyond debate.” 26\n\n Further, as the Supreme Court recently reiterated, “clearly established law should\nnot be defined at a high level of generality” but must instead “be particularized to the\nfacts of the case.”27 The doctrine is designed to “give[] government officials breathing\nroom to make reasonable but mistaken judgments by protect[ing] all but the plainly\nincompetent or those who knowingly violate the law.”28\n\n Supreme Court discussion of searches has emphasized the threats posed at borders\nand the government’s compelling interests in searches there. 29 Because the government’s\ninterest in preventing the entry of unwarranted persons and effects is at its zenith at the\nborder,30 Congress “has granted the Executive plenary authority to conduct routine\nsearches and seizures at the border, without probable cause or a warrant . . ..”31 Until\nSeptember 4, 2008, there had been no ruling in the Third Circuit as to what constituted a\n“routine search.” As for Officer Ogg, he was located in San Juan, Puerto Rico, in the\nFirst Circuit. There had not been any such ruling in the First Circuit, and the First Circuit\ncourts would not be bound by Whitted, a Third Circuit case.\n\n When such a ruling is made, a ruling which affects the procedures used in border\nsearches, it is beyond belief that within two days the government could determine what\nwas “reasonable suspicion” and what new policy was required to conform to the ruling,\nmuch less communicate that new policy to the CBP officers. We can only conclude that\nas of September 5, 2008, it was not clearly established in either the Third Circuit or the\nFirst Circuit that a search of a cruise ship cabin at the border had to be supported by\n\n25 Ashcroft v. al-Kidd, 563 U.S. 731, 735 (2011) (citing Harlow v. Fitzgerald, 457 U.S.\n800, 818 (1982)).\n26 Plumhoff v. Rickard, 134 S. Ct. 2012, 2023 (2014) (quoting Ashcroft, 563 U.S. at 741).\n27 White v. Pauly, 137 S. Ct. 548, 552 (2017) (per curiam) (citation omitted); see also\n\nL.R. v. Sch. Dist. of Phila., 836 F.3d 235, 248 (3d Cir. 2016).\n28 City & Cty. of S.F. v. Sheehan, 135 S. Ct. 1765, 1774 (2015) (citation omitted).\n29 See, e.g., Montoya, 473 U.S. at 539-40.\n30 United States v. Flores-Montano, 541 U.S. 149, 152-53 (2004).\n31 Id. at 153.\n\n\n 8\n\freasonable suspicion. Accordingly, under the circumstances that Officer Ogg confronted,\nhe did not violate clearly established law by entering lookouts for the three passengers the\nday after we issued our decision in Whitted. He is entitled to qualified immunity.\n\n We conclude that the same situation applies to the St. Thomas officers. On\nSeptember 6, the Whitted standard was no more clearly established than it had been the\nday before. Moreover, if the St. Thomas officers had been aware of Whitted, they would\nhave known that Whitted held that unsubstantiated information from TECS can establish\nreasonable suspicion.32\n\n For these reasons, we conclude that the Whitted standard was not clearly\nestablished in the Third Circuit, or the First Circuit, on September 5 or 6. Within one or\ntwo days, neither Officer Ogg nor the St. Thomas officers could reasonably be expected\nto have learned of this development in our Fourth Amendment jurisprudence. At that\ntime, it would not have been beyond debate that, absent reasonable suspicion, the Fourth\nAmendment prohibited the search of the travelers’ cabins. For purposes of qualified\nimmunity, a legal principle does not become “clearly established” the day we announce a\ndecision, or even one or two days later.\n\n This holding is informed by the overarching aim of the qualified immunity\ndoctrine to insulate from civil liability “all but the plainly incompetent or those who\nknowingly violate the law,”33 and the need to ensure that the relevant legal principle is\nframed with particularity34 and settled “beyond debate.”35 We are, however, deciding\nonly this case. For that reason, we decline to draw a bright line demarcating when a legal\nprinciple becomes “clearly established.” We leave that exercise for another day.\n\n Finally, the tort claims against the United States also fail because of the FTCA’s\ndiscretionary function exception. The FTCA provides a limited waiver of sovereign\nimmunity in certain tort actions against the United States for money damages.36 That\nwaiver does not extend to various types of government conduct enumerated in 28 U.S.C.\n\n\n\n\n32 541 F.3d at 490.\n33 White, 137 S. Ct. at 552.\n34 Id.\n35 Plumhoff, 134 S. Ct. at 2023.\n36 28 U.S.C. § 1346(b)(1).\n\n\n 9\n\f§ 2680, including “the exercise or performance or the failure to exercise or perform a\ndiscretionary function or duty . . . whether or not the discretion involved be abused.”37\n\n The travelers do not dispute that Officer Ogg’s entry of “lookouts” and the\nsearches that followed were discretionary acts under the “discretionary function”\nexception.38 Rather, they argue that the United States is not shielded from liability\nbecause the officers in this case, though exercising their discretion, violated “clearly\nestablished . . . constitutional rights of which a reasonable person would have known.” 39\n\n Because, for the reasons set out above, the CBP officers did not violate clearly\nestablished constitutional rights, the FTCA claims also fail.\n\n V.\n\n For the reasons stated above, we will affirm the judgment of the District Court.\n\n\n\n\n37 28 U.S.C. § 2680(a). Discretionary acts and omissions “involv[e] an element of\njudgment or choice.” Conduct is non-discretionary only if a “federal statute, regulation,\nor policy specifically prescribes a course of action for an employee to follow” and the\ngovernment “employee has no rightful option but to adhere to the directive.” United\nStates v. Gaubert, 499 U.S. 315, 322 (1991) (quoting Berkovitz ex rel. Berkovitz v. United\nStates, 486 U.S. 531, 536 (1988)).\n38 Br. at 63-64.\n39 Harlow, 457 U.S. at 818.\n\n\n 10\n[END_CASE]", "role": "user" } ]
4,583,040
UNITED STATES of America v. William HIRD, Appellant at No. 14-4754 United States of America v. Thomasine Tynes, Appellant at No. 14-4804 United States of America v. Robert Mulgrew, Appellant at No. 14-4812 United States of America v. Michael Lowry, Appellant at No. 15-1344 United States of America v. Willie Singletary, Appellant at No. 15-1739 United States of America v. Henry P. Alfano, AKA Ed, AKA Eddie, Henry P. Alfano, Appellant at No. 15-3765
United States v. William Hird
2019-01-18
14-4754; 14-4804; 14-4812; 15-1344; 15-1739; 15-3765
U.S. Court of Appeals for the Third Circuit
{"judges": "Greenaway, Nygaard, Fisher", "parties": "", "opinions": [{"author": "NYGAARD, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n\n __________\n\nNos. 14-4754, 14-4804, 14-4812, 15-1344, 15-1739, 15-3765\n __________\n\n UNITED STATES OF AMERICA\n v.\n WILLIAM HIRD,\n Appellant at No. 14-4754\n __________\n\n UNITED STATES OF AMERICA\n v.\n THOMASINE TYNES,\n Appellant at No. 14-4804\n __________\n\n UNITED STATES OF AMERICA\n v.\n ROBERT MULGREW,\n Appellant at No. 14-4812\n __________\n\n UNITED STATES OF AMERICA\n v.\n MICHAEL LOWRY,\n Appellant at No. 15-1344\n\f __________\n\n UNITED STATES OF AMERICA\n v.\n WILLIE SINGLETARY,\n Appellant at No. 15-1739\n ___________\n\n UNITED STATES OF AMERICA\n v.\n HENRY P. ALFANO,\n aka Ed, aka Eddie,\n\n Henry P. Alfano,\n Appellant at No. 15-3765\n __________\n\n On Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n\n (District Court Criminal Nos. 2-13-cr-00039-007,\n2-13-cr-00039-005, 2-13-cr-00039-003, 2-13-cr-00039-002,\n 2-13-cr-00039-004, 2-13-cr-00039-008)\n District Judge: Honorable Robert F. Kelly\n District Judge: Honorable Lawrence F. Stengel\n\n Argued October 23, 2017\n\n BEFORE: GREENAWAY, JR., NYGAARD,\n and FISHER, Circuit Judges\n\n\n (Opinion Filed: January 18, 2019)\n\n\n\n\n 2\n\fAngela Halim\nHalim Drossner\n1528 Walnut Street, Suite 1501\nPhiladelphia, PA 19102\n\nGregory J. Pagano\n1315 Walnut Street, 12th Floor\nPhiladelphia, PA 19107\n Counsel for Appellant in No. 14-4754\n\nLisa A. Mathewson [Argued]\n123 South Broad Street, Suite 810\nPhiladelphia, PA 19109\n Counsel for Appellant No. 14-4804\n\nPeter Goldberger [Argued]\nPamela A. Wilk\n50 Rittenhouse Place\nArdmore, PA 19003\n Counsel for Appellant in No. 14-4812\n\nMichael J. Engle [Argued]\nStradley Ronon Stevens & Young\n2005 Market Street, Suite 2600\nPhiladelphia, PA 19103\n\nMeredith A. Lowry\n1528 Walnut Street, Suite 1501\nPhiladelphia, PA 19102\n Counsel for Appellant in No. 15-1344\n\n\n\n\n 3\n\fWilliam J. Brennan\n1600 Locust Street\nPhiladelphia, PA 19103\n Counsel for Appellant in No. 15-1739\n\nMark E. Cedrone [Argued]\nCedrone & Mancano\n123 South Broad Street, Suite 810\nPhiladelphia, PA 19109\n Counsel for Appellant in No. 15-3765\n\n\nLouis D. Lappen\nDenise S. Wolf\nAnthony J. Wzorek\nRobert A. Zauzmer [Argued]\nOffice of United States Attorney\n615 Chestnut Street, Suite 1250\nPhiladelphia, PA 19106\n Counsel for Appellee\n\n\n\n\n __________\n\n OPINION OF THE COURT\n __________\n\nNYGAARD, Circuit Judge.\n\n I.\n\n\n\n\n 4\n\f In the run-up to a joint trial on a 77-count indictment\nthat charged Appellants with operating a ticket-fixing scheme\nin the Philadelphia Traffic Court, the District Court denied a\nmotion, under Federal Rule of Criminal Procedure\n12(b)(3)(B)(v), to dismiss charges of conspiracy (18 U.S.C. §\n1349), mail fraud (18 U.S.C. § 1341), and wire fraud (18\nU.S.C. § 1343). Appellants Henry Alfano (private citizen)\nand William Hird (Traffic Court administrator) subsequently\npleaded guilty to all counts against them. But now they\nappeal the District Court’s decision on this motion,\nquestioning whether the indictment properly alleged offenses\nof mail fraud and wire fraud. 1\n\n Appellants Michael Lowry, Robert Mulgrew, and\nThomasine Tynes (Traffic Court judges) proceeded to a joint\ntrial and were acquitted on the fraud and conspiracy counts,\nbut they were convicted of perjury for statements they made\nbefore the Grand Jury. Lowry, Mulgrew, and Tynes dispute\nthe sufficiency of the evidence on which they were convicted\nby arguing that the prosecutor’s questions were vague, and\nthat their answers were literally true. Lowry and Mulgrew\ncontend alternatively that the jury was prejudiced by evidence\npresented at trial on the fraud and conspiracy counts.\nMulgrew also complains that the District Court erred by\nruling that certain evidence was inadmissible.\n\n At the same trial, the jury convicted Willie Singletary\n(Traffic Court judge) of making false statements during the\ninvestigation. He claims the District Court made errors when\n\n\n1\n Alfano and Hird preserved their right to appeal. See infra\nsubsection I.C.\n\n\n\n\n 5\n\fit sentenced him. 2 The Government concurs with\nSingletary’s challenge to his sentence.\n\n We have consolidated these appeals for efficiency and\nhave grouped the arguments—to the extent that it is\npossible—by common issues. We agree with Singletary and\nthe Government that he should be resentenced. We will\nreverse the judgment and remand his cause to the District\nCourt for this purpose. We are not persuaded by the rest of\nAppellants’ arguments and will affirm their judgments of\nconviction. 3\n\n II.\n\n Appellants Alfano 4 and Hird 5\n\n\n\n2\n Singletary also attempted to join additional arguments raised\nby other appellants, but for reasons we explain later, see infra\nnote 33, we focus only on his challenge to his sentence.\n3\n The District Court had jurisdiction pursuant to 18 U.S.C. §\n3231. We have jurisdiction to review these claims under 28\nU.S.C.§ 1291 and 18 U.S.C. § 3742(a).\n4\n Appellant Alfano pleaded guilty to Conspiracy (Count 1),\nWire Fraud (Counts 2, 3, 4, 5, 6, 7) and Mail Fraud (Counts\n51, 52, 53, 54, 55, 56).\n5\n Appellant Hird pleaded guilty to Conspiracy (Count 1),\nWire Fraud (Counts 3, 4, 5, 6, 16, 17, 18, 19, 20, 22, 23) and\nMail Fraud (Counts 58, 59, 60).\n\n\n\n\n 6\n\f A.\n\n We begin with a brief look at the indictment’s\ndescription of the Traffic Court and its operations to\ncontextualize the arguments made by Alfano and Hird. The\nPhiladelphia Traffic Court was part of the First Judicial\nDistrict of Pennsylvania. App. 186 (Indictment ¶ 2). 6 It\nadjudicated violations of the Pennsylvania Motor Vehicle\nCode occurring in the City of Philadelphia, no matter whether\nthe Philadelphia Police or the Pennsylvania State Police\nissued the tickets. App. 187 (Indictment ¶5). When a person\nwas cited for a violation he or she was required—within ten\ndays—to enter a plea of guilty or not guilty. If the person\nfailed to plead, the Traffic Court issued a notice that his or her\nlicense was being suspended. App. 189 (Indictment ¶ 12). A\nperson who pleaded not guilty proceeded to a hearing with a\nTraffic Court judge presiding. App. 187 (Indictment ¶ 6).\n\n A guilty plea, or a determination of guilt by a Traffic\nCourt judge after a hearing, resulted in a judgment ordering\npayment of statutory fines and court costs. App. 188\n(Indictment ¶ 8). 7 The Traffic Court was responsible for\ncollecting these fines (sending them to the City and\n\n\n6\n Philadelphia Traffic Court was abolished and its jurisdiction\nwas transferred to the Municipal Court in 2013 by an Act of\nthe Pennsylvania General Assembly. 42 Pa.Con.Stat.\n§1121(a)(2) (2013). The court is now known as the Traffic\nDivision of the Municipal Court.\n7\n Although other penalties are prescribed by the Pennsylvania\nMotor Vehicle Code (App. 188), this appeal is limited to the\nmonetary fines and costs. App. 355.\n\n\n\n\n 7\n\fCommonwealth) and costs (which it distributed to several\npre-designated funds). App. 188-89 (Indictment ¶ 9).\nFinally, it reported the disposition of each adjudication to the\nPennsylvania Department of Transportation (PennDOT).\nApp. 189 (Indictment ¶ 11).\n\n B.\n\n The indictment charged that, at the behest of Alfano\n(App. 193 (Indictment ¶ 25)) and others, the Traffic Court\nadministrator and judges operated an “extra-judicial system,\nnot sanctioned by the Pennsylvania court system” that\nignored court procedure and gave preferential treatment\n(“consideration”) to select individuals with connections to the\ncourt who had been cited for motor vehicle violations. App.\n196 (Indictment ¶ 31). The special treatment included:\n\n (1) dismissing tickets outright; (2)\n finding the ticketholder not guilty\n after a “show” hearing; (3)\n adjudicating the ticket in a\n manner to reduce fines and avoid\n assignment of points to a driver’s\n record; and (4) obtaining\n continuances of trial dates to\n “judge-shop,” that is find a Traffic\n Court judge who would accede to\n a request for preferential\n treatment.\n\nApp. 195-196 (Indictment ¶ 30). All of this was “not\navailable to the rest of the citizenry.” App. 196 (Indictment ¶\n32). It also alleged that Appellants cooperated with each\n\n\n\n\n 8\n\fother to fulfill requests they and their staffs received. App.\n194-95 (Indictment ¶ 27). Finally, it charged that “[i]n\nacceding to requests for ‘consideration,’ defendants were\ndepriving the City of Philadelphia and the Commonwealth of\nPennsylvania of money which would have been properly due\nas fines and costs.” App. 197 (Indictment ¶ 38). 8\n After extending consideration to favored individuals,\nTraffic Court judges would report the final adjudication to\n“various authorities, including PennDOT, as if there had been\na fair and open review of the circumstances.” App. 197\n(Indictment ¶ 34). Appellant Hird provided a printout to\nAppellant Alfano showing citations that had been “dismissed\nor otherwise disposed of.” App. 198-99 (Indictment ¶ 42).\nSuch “receipts” were not routinely issued in cases.\n\n C.\n\n Hird and Alfano pleaded guilty to all the charges\nagainst them in the indictment. But, in their plea agreement\nthey reserved the right to appeal “whether the Indictment\n\n\n8\n An example of the many allegations involving Alfano and\nHird is: A.S. requested assistance from Appellant Alfano and\nAppellant Hird on Citation Number P1J0PK568L4 on or\naround February 17, 2010. The citation charged A.S. with\ndriving a tractor-trailer from which snow and ice fell, striking\nvehicles on Interstate 95. The violation carried a $300 fine\nand costs of $142. Appellant Hird promised that he would\n“stop all action” on the citation and instructed A.S. to ignore\nthe ticket. Although A.S. did not appear at the hearing, the\nTraffic Court judge (who is not an appellant here) ruled A.S.\nnot guilty. App. 210-12 (Indictment ¶¶ 25-34).\n\n\n\n\n 9\n\fsufficiently alleged that the defendants engaged in a scheme\nto defraud the Commonwealth of Pennsylvania and the City\nof Philadelphia of money in costs and fees.” App. 355 (Plea\nAgreement ¶ 9(b)(4)). So they now appeal the District\nCourt’s order denying the motion to dismiss, asserting that\nthe indictment failed to allege violations of mail fraud and\nwire fraud.\n\n “To be sufficient, an indictment must allege that the\ndefendant performed acts which, if proven, constitute a\nviolation of the law that he is charged with violating.” United\nStates v. Small, 793 F.3d 350, 352 (3d Cir. 2015). We\nassume in our review that the allegations in the indictment are\ntrue. United States v. Hedaithy, 392 F.3d 580, 583 (3d Cir.\n2004). “The question of whether the . . . indictments alleged\nfacts that are within the ambit of the mail fraud statute is a\nquestion of statutory interpretation subject to plenary review.”\nId. at 590 n.10.\n\n To indict on mail or wire fraud, the Government must\nallege that defendants “devised or intend[ed] to devise any\nscheme or artifice to defraud, or for obtaining money or\nproperty by means of false or fraudulent pretenses,\nrepresentations, or promises” and used mail or wire to effect\nthe scheme. 18 U.S.C. §§ 1341, 1343. Alfano and Hird claim\nthe Government failed to allege that the scheme to commit\nwire and mail fraud had an objective of “obtaining money or\nproperty.” 9\n\n9\n In the context of mail fraud (§ 1341) and wire fraud (§1343)\nthe term “money” has the same meaning. The same is true\nfor the term “property.” Carpenter v. United States, 484 U.S.\n19, 25 n. 6 (1987).\n\n\n\n\n 10\n\f The District Court ruled that the indictment\nsufficiently alleged that the scheme “involved defrauding the\nCommonwealth and the City of money.” App. 20. It noted,\namong others, allegations that:\n\n The conspirators used the\n Philadelphia Traffic Court\n (“Traffic Court”) to give\n preferential treatment to certain\n ticketholders, most commonly by\n “fixing” tickets for those with\n whom they were politically and\n socially connected. By doing so,\n the conspirators defrauded the\n Commonwealth of Pennsylvania\n and the City of Philadelphia of\n funds to which the\n Commonwealth and the City were\n entitled.\n\nId. at 18; see also id. at 185 (Indictment ¶ 1). Similarly, it\nreferred to the following.\n\n In acceding to requests for\n “consideration,” defendants were\n depriving the City of Philadelphia\n and the Commonwealth of\n Pennsylvania of money which\n would have been properly due as\n fines and costs.\n\n\n\n\n 11\n\fId. at 9; see also id. at 197 (quoting Indictment ¶ 38).\nHighlighting the references to “funds” and “money,” and that\nthe monetary amounts of the fines are specifically pleaded,\nthe District Court cited to a case from the Court of Appeals\nfor the Eighth Circuit which concluded succinctly that\n“[m]oney is money.” United States v. Sullivan, No. 2:13-cr-\n00039, 2013 WL 3305217, at *7 (E.D. Pa. July 1, 2013)\n(quoting United States v. Granberry, 908 F.2d 278, 280 (8th\nCir. 1990)). The District Court was satisfied that the\nindictment alleged enough.\n\n “Money, of course, is a form of property.” Reiter v.\nSonotone Corp., 442 U.S. 330, 338 (1979). But Alfano and\nHird argue that the mere mention of money in an indictment\nis not enough. They point to a string of Supreme Court and\nCourt of Appeals decisions analyzing Section 1341 and\nSection 1343 which reinforce the point that crimes of mail\nfraud and wire fraud are “limited in scope to the protection of\nproperty rights.” McNally v. United States, 483 U.S. 350, 360\n(1987). 10 The Supreme Court said that “[a]ny benefit which\nthe government derives from the [mail fraud] statute must be\nlimited to the Government’s interests as a property holder.”\nId. at 359 n.8 (emphasis added). Appellants are convinced\nthat money in the form of traffic fines and costs cannot be\nregarded as the Government’s “property” for purposes of mail\nor wire fraud, and they identify two decisions as particularly\nsupportive of their position: Cleveland v. United States, 531\n\n10\n The District Court cited to a number of cases that came\nafter McNally: Carpenter v. United States, 484 U.S. 19\n(1987); Cleveland v. United States, 531 U.S. 12 (2000);\nPasquantino v. United States, 544 U.S. 349 (2005).\n\n\n\n\n 12\n\fU.S. 12 (2000); and United States v. Henry¸ 29 F.3d 112 (3d\nCir. 1994).\n\n The Court in Cleveland examined the mail fraud\nconvictions of individuals who received a state video poker\nlicense by submitting a license application that withheld\nimportant information. Cleveland, 531 U.S. 12. 11 The Court\nnoted that the video poker licenses were part of a state\nprogram that was “purely regulatory.” Id. at 22 (citation\nomitted). 12 It ruled that licenses are a “paradigmatic\nexercise[] of the States’ traditional police powers.” Id. at 23.\nThe Court went on to say that the state’s regulatory powers\ninvolving “intangible rights of allocation, exclusion, and\ncontrol” (which are embodied in a license) are not interests\nthat traditionally have been recognized as property. Id.\nTherefore, even though appellants may have obtained the\nlicense through deception, this was not mail fraud because the\nlicense—at least while still in the hands of the state—was not\n\n\n\n11\n The licenses were part of a regulatory scheme that had as\nits purpose to increase public confidence in the honesty of\ngaming activities that are free of criminal involvement.\nCleveland, 531 U.S. at 20–21 (quoting La. Rev. Stat. Ann. §\n27:306(A)(1) (2000) (repealed 2012)).\n12\n The Court rebuffed the Government’s attempts to analogize\nlicenses to other forms of property like patents and franchise\nrights. As for likening licenses to franchise rights, the Court\nobserved that the Government did not enter the video poker\nbusiness, but rather decided to “permit, regulate, and tax\nprivate operators of the games.” Id. at 24.\n\n\n\n\n 13\n\fproperty. Id. at 26-27. It was a purely administrative tool\nused to achieve regulatory objectives. Id. at 21.\n\n The state responded to the Court’s concerns by\nagreeing that the licenses served a regulatory purpose, but it\ndirected attention to the revenue it received from fees\ncollected for license applications and renewals, as well as\ndevice fees. Id. at 21-22. It argued that this revenue is a\nproperty interest. Id. The Court was not convinced:\n\n Tellingly, as to the character of\n Louisiana’s stake in its video\n poker licenses, the Government\n nowhere alleges that Cleveland\n defrauded the State of any money\n to which the State was entitled by\n law. Indeed, there is no dispute\n that TSG paid the State of\n Louisiana its proper share of\n revenue, which totaled more than\n $1.2 million, between 1993 and\n 1995. If Cleveland defrauded the\n State of “property,” the nature of\n that property cannot be economic.\n\nId. at 22 (emphasis added). It concluded that “[e]ven when\ntied to an expected stream of revenue, the State’s right of\ncontrol does not create a property interest any more than a\nlaw licensing liquor sales in a State that levies a sales tax on\n\n\n\n\n 14\n\fliquor.” Id. at 23. 13 The money collected from application\nand processing fees was an integral part of the state\nregulatory program and it did not create any property interest.\nSee id.\n\n The purpose of the Pennsylvania Motor Vehicle Code\nis to “promote the safety of persons and property within the\nstate.” Mauer v. Boardman, 7 A.2d 466, 472 (Pa. 1939).\nMoreover, issuing traffic tickets is a crucial element in the\nenforcement of the Motor Vehicle Code: it is a quintessential\nexercise of state police power. Alfano and Hird conclude,\nmuch like Cleveland, that no property interest could arise\nfrom revenue generated from the state’s exercise of its police\npower in the form of a traffic-ticket fine. They see nothing\nbut a regulatory program here. But this ignores crucial\naspects of the case before us that make it different.\n\n Simply stated, fees charged to obtain a license cannot\nbe equated with fines and costs that result from a traffic\nticket. The license fee was imposed, adjusted, and collected\nsolely by the state’s exercise of its regulatory authority. In\ncontrast, here the state’s police power is exercised when a\ncitation is issued, but this ticket merely establishes the\nsummary violation with which the person is charged. Once a\nperson has been charged, it is judicial power (not the state’s\npolice power) that is exercised to determine whether the\n\n\n\n\n13\n Cleveland also held that Government-issued licenses have\nno intrinsic economic worth before they are given to\napplicants. Id. at 23.\n\n\n\n\n 15\n\fperson is guilty and, if guilty, to impose the fine and costs. 14\nThese fines and costs, although specified by the Motor\nVehicle Code, cannot be cabined as a product of the state’s\nregulatory authority. They are part and parcel of the\njudgment of the court. With this in mind, it is significant that\nthe indictment does not focus on how the citations were\nissued (which would implicate police power), but rather\nalleges that the judicial process was rigged to produce only\njudgments that imposed lower fines—or most often—no fines\nand costs at all. 15\n\n But this raises a further question: can a criminal\njudgment held by the government ever be “property?” The\nCourt in Cleveland offered a critique in its analysis of a\n\n14\n The Traffic Court was not an administrative tribunal.\nRather, it was part of the First Judicial District of\nPennsylvania. App. 186 (Indictment ¶ 2). See also supra\nnote 6 and accompanying text.\n15\n On this point, it is noteworthy that the Supreme Court also\nsaid the following: “We resist . . . [any invitation] to approve\na sweeping expansion of federal criminal jurisdiction in the\nabsence of a clear statement by Congress. . . . ‘[U]nless\nCongress conveys its purpose clearly, it will not be deemed to\nhave significantly changed the federal-state balance’ in the\nprosecution of crimes.” Cleveland, 531 U.S. at 24-25\n(quoting Jones v. United States, 529 U.S. 848, 858 (2000)).\nAs we discuss later, the legal tradition of understanding\njudgments as property is long-established. Consequently, the\nconcern about expanding the reach of federal fraud statutes to\nnew classes of property that was present in the deliberation of\nstate licenses in Cleveland is not at issue here.\n\n\n\n\n 16\n\fdifferent issue (whether licenses were analogous to patents)\nthat is apropos to answering this question.\n\n [W]hile a patent holder may sell\n her patent, see 35 U.S.C. § 261 . .\n . “patents shall have the attributes\n of personal property” . . . the State\n may not sell its licensing\n authority. Instead of a patent\n holder’s interest in an unlicensed\n patent, the better analogy is to the\n Federal Government’s interest in\n an unissued patent. That interest,\n like the State’s interest in\n licensing video poker operations,\n surely implicates the\n Government’s role as sovereign,\n not as property holder.\n\nCleveland, 531 U.S. at 23–24. Fines imposed by judges are\ncriminal penalties that “implicate[] the Government’s role as\nsovereign.” Id. at 24. Judgments ordering traffic fines and\ncosts cannot be sold and, in the logic of Cleveland, would\nseem then to have no intrinsic economic value. Indeed, the\npenal (non-economic) nature of the fine is undeniable because\nthe failure to pay a fine can result in the imposition of\nsentences of greater consequence, including imprisonment.\nSee Pa. R. Crim. P. 706 cmt. But Cleveland is not the last\nword. As we will discuss below, a Supreme Court opinion\nissued five years later, Pasquantino v. United States, 544 U.S.\n349 (2005), forecloses the defendants’ argument.\n\n\n\n\n 17\n\f Finally, we note a dissimilarity between this case and\nCleveland, highlighted by the District Court, on the\nsignificance of the monetary interest that the Government\nassociates with the fraud. The Cleveland Court regarded the\nlicensing fees as integral to the regulatory effort and collateral\nto the matter at hand. The indictment there centered on the\nscheme to obtain liceneses, and did not even raise the\nlicensing fees. See Cleveland, 531 U.S. at 22. Indeed, those\ncharged with the fraud paid all the appropriate fees; there was\nno evidence that the government suffered any economic\ndetriment. Id.\n\n In contrast, the indictment here explicitly states that\nthe scheme deprived the City and the Commonwealth of\nmoney, and it describes the object of the scheme as obviating\njudgments of guilt that imposed the fines and costs. Unlike\nCleveland, the fines and costs play a central role in the\nscheme as alleged.\n\n Alfano and Hird next focus on our decision in Henry\nto argue that the Government cannot claim to have a property\nright because the Government never had a legal claim to the\nfines and costs at any point in the scheme. In Henry, we\nexamined convictions for wire fraud arising from a\ncompetitive bidding process among banks to receive deposits\nof a public agency’s bridge tolls. Henry v. United States, 29\nF.3d 112 (3d Cir. 1994). Appellants—public employees—\nwere convicted of mail fraud for giving one bank confidential\ninformation about bids from other banks. Id. at 113. We\nidentified several problems, 16 but Alfano and Hird highlight\n\n16\n The Supreme Court had already made clear that “a\ngovernment official’s breach of his or her obligations to the\n\n\n\n\n 18\n\four observation in Henry that the object of the mail and wire\nfraud must be something to which the victim could claim a\nright of entitlement. Id. at 115 (“a grant of a right of\nexclusion”) (citing Carpenter, 484 U.S. at 26-27)). 17 Indeed,\nwe noted that a bank’s property right to the tolls would attach\nonly after the funds were deposited. Id. at 114. So the banks\nthat lost the bidding process never had a basis to claim any\nlegally recognized entitlement to the toll deposits. 18 Id. at\n115. A fraud claim cannot rest on the bidders being cheated\nout of an opportunity to receive the deposits. For these\nreasons, we concluded that the indictment did not allege a\nscheme to obtain fraudulently someone’s “property.” Id. at\n116.\n\n Here, the Government alleged that the defendants\n“were depriving . . . Philadelphia and . . . Pennsylvania of\nmoney which would have been properly due as fines and\ncosts” by making it possible for certain well-connected\nindividuals to avoid a judgment of guilt that imposed an\nobligation to pay appropriate statutory fines. App. 197\n\n\npublic or an employee’s breach of his or her obligations to an\nemployer” did not fall within the scope of Section 1343.\nHenry, 29 F.3d at 114 (citing Carpenter, 484 U.S. at 25).\n17\n To assess whether a particular claim is a legal entitlement,\n“we look to whether the law traditionally has recognized and\nenforced [the entitlement] as a property right.” Henry, 29\nF.3d at 115.\n18\n They were, no doubt, robbed of a fair process, but we could\nnot identify any legal tradition that recognized this\ndeprivation as a property right. Id. at 115.\n\n\n\n\n 19\n\f(Indictment ¶ 38). But Appellants stress that, like the\ndeposits in Henry, the indictment here alleged an entitlement\nthat does not yet exist because a person must be adjudicated\n(or plead) guilty before they must pay any fines or costs.\nNone of the cases directly associated with Alfano and Hird\nresulted in a guilty judgment. As a result, they argue, the\nGovernment cannot claim here that it was cheated of an\nentitlement, because they were only fines and costs that the\npeople might have owed if they had been found guilty.\n\n The District Court said it well. Accepting this\nargument “would permit the alleged conspirators” to take\nadvantage of their “unique position” in this case “to enter into\na scheme to commit fraud and then hide behind the argument\nthat the success of their fraud precludes prosecution under the\n‘money or property interest’ requirement of the mail and wire\nfraud statutes.” Sullivan, 2013 WL 3305217, at *7.\nAppellants cannot rest on the very object of their scheme (to\nwork on behalf of favored individuals to obviate judgments of\nguilt and the imposition of fines and costs) as the basis to\nclaim that there is no fraud. Indeed, the not-guilty judgments\nthat Alfano and Hird worked to obtain through the\nextrajudicial system were alleged in the indictment as\nevidence of the scheme itself.\n\n Even if some of the cases in the extra-judicial system\nwould have been judged not guilty in a real adjudication it is\n(as the District Court correctly noted) the intent of the\nscheme, not the successful execution of it, that is the basis for\ncriminal liability. See Neder v. United States, 527 U.S. 1, 25\n(1999) (In the criminal context, the court focuses on the\nobjective of the scheme rather than its actual outcome; what\noperatives intended to do, not whether they were successful in\n\n\n\n\n 20\n\fdoing it.); United States v. Rowe, 56 F.2d 747, 749 (2d Cir.)\n(“Civilly of course the [mail fraud statute]would fail without\nproof of damage, but that has no application to criminal\nliability.”), cert. denied 286 U.S. 554 (1932). The indictment\ngenerally alleges not just that Appellants operated a system\nthat operated outside the bounds of Traffic Court procedures,\nbut that it did so for the purpose of obviating judgments of\nguilt imposing fines and costs in those selected cases. See,\ne.g., supra note 8. Moreover, we note that in one case not\ndirectly involving either Alfano or Hird, the indictment\nalleged that fines and costs were not just obviated, but were\nactually erased by an alleged co-conspirator traffic court\njudge who ignored the conviction, backdated a continuance,\nand “adjudicated” the person not-guilty. App. 228-29\n(Indictment ¶¶ 108-113). This episode serves to highlight\nthat the entire scheme was centered on keeping (or taking)\njudgments out of the hands of the Government to prevent the\nimposition of fines and costs. As a result, Appellants’\nreliance on our justice system’s presumption of innocence as\na basis to argue against the existence of a governmental\nproperty interest is a red herring that is properly disregarded\nhere.\n\n Accordingly, we conclude that the indictment’s\nallegation that the scheme had an objective of depriving\n“Philadelphia and . . . Pennsylvania of money which would\nhave been properly due as fines and costs” is not undermined\nby the lack of guilty verdicts. App. 197 (Indictment ¶38\n(emphasis added)).\n\n Alfano and Hird next highlight that, in Henry, our\nproperty interest analysis centered on “whether the law\ntraditionally has recognized and enforced [the entitlement in\n\n\n\n\n 21\n\fquestion] as a property right.” 29 F.3d at 115. Appellants\nassert that traffic fines and costs typically have not been\nconsidered economic property and are unsupported by any\nlegal tradition sufficient to ground charges of wire and mail\nfraud. As we have already noted we disagree with any\nconclusion that the fines and costs at issue have no intrinsic\neconomic value. But we turn to another decision of the\nSupreme Court that came after Cleveland to address squarely\nwhether jurisprudence supports our conclusion.\n\n In 2005 the Supreme Court reviewed convictions\narising from a scheme to smuggle large quantities of liquor\nfrom the United States into Canada, evading Canadian taxes.\nSee Pasquantino v. United States, 544 U.S. 349, 353 (2005).\nThe Court noted that the right to be paid has been routinely\nrecognized as property, id. at 355–56, 19 observing that there is\nan equivalence between “money in hand and money legally\ndue,” id. at 356. Affirming the conviction, the Court said:\n“Had petitioners complied with this legal obligation, they\nwould have paid money to Canada. Petitioners’ tax evasion\ndeprived Canada of that money, inflicting an economic injury\nno less than had they embezzled funds from the Canadian\ntreasury.” Id. It concluded that: “[t]he object of petitioners’\nscheme was to deprive Canada of money legally due, and\ntheir scheme thereby had as its object the deprivation of\nCanada’s ‘property.’” Id. Under Pasquantino, then, traffic\ntickets (or more precisely, judgments arising from them) are\nconsidered an “entitlement to collect money from individuals,\n\n\n19\n The Court cited 3 W. Blackstone, Commentaries on the\nLaws of England 153–155 (1768), which classified the right\nto sue on a debt as personal property.\n\n\n\n\n 22\n\fthe possession of which is ‘something of value.’” 544 U.S. at\n355 (quoting McNally, 483 U.S. at 358). 20 We conclude that\na scheme to obviate judgments imposing fines, effectively\npreventing the government from holding and collecting on\nsuch judgments imposes an economic injury that is the\nequivalent of unlawfully taking money from fines paid out of\nthe Government’s accounts. See id. at 358.\n\n Alfano and Hird focus, finally, on the role that a\njudge’s discretion plays in the adjudication of a case,\nasserting that the uncertainty this creates about outcomes in\nany given case undermines any argument that a judgment in a\nTraffic Court case can be claimed as an entitlement to\nproperty. To the extent that this merely rephrases the issue of\nguilt or innocence on particular charges, we have already\n\n20\n We also note that Pennsylvania law permits the government\nto remedy the nonpayment of fines and costs as an unpaid\ndebt through civil process, enabling the government to\nbecome a judgment creditor. Pa. R. Crim. P. 706 cmt.\n(“Nothing in this rule [concerning criminal fines] is intended\nto abridge any rights the Commonwealth may have in a civil\nproceeding to collect a fine or costs.”). Because of this, a\nseparate legal tradition is implicated that recognizes the\njudgment itself as property. See, e.g., Armada (Singapore)\nPTE Ltd. v. Amcol International Corp., 885 F.3d 1090, 1094\n(7th Cir. 2018). This long, stable legal tradition of\nrecognizing civil judgments for money as property supports\nthe conclusion that the fines arising from judgments in traffic\ncourt cannot be regarded merely as implicating the act of a\nsovereign imposing a criminal penalty. They can be collected\nby civil process as a debt and are, thus, a property interest.\n\n\n\n\n 23\n\faddressed it above. To the degree that it refers to a judge’s\ndiscretion in sentencing, as the District Court noted, there is\nno such discretion here. 21 The Motor Vehicle Code imposes\nfines and costs for each violation, eliminating any judicial\ndiscretion in this regard.\n\n D.\n\n All of this leads us to conclude that the District Court\ndid not err by denying the motion to dismiss. We conclude\nthat, as alleged, this scheme had the objective of preventing\nthe City of Philadelphia and the Commonwealth of\nPennsylvania from possessing a lawful entitlement to collect\nmoney in the form of fines and costs—a property interest—\nfrom individuals who Alfano and Hird assisted. We will thus\naffirm the convictions of Appellants Alfano and Hird.\n\n III.\n\n Appellants Tynes, Lowry, and Mulgrew\n\n A.\n\n\n\n\n21\n We question, in general, the relevance of an entity’s\nauthority to relinquish a just entitlement or to forbear an\nobligation that an entitlement imposes upon another, as a\nbasis to call into doubt the legitimacy of, or the very existence\nof the entitlement. But see United States v. Mariani, 90 F.\nSupp. 2d 574, 583 (M.D. Pa. 2000) (Discretionary civil fines\nand penalties “may be too speculative to constitute a valid\nproperty interest.”) (internal citation omitted).\n\n\n\n\n 24\n\f In 2011, the United States Attorney presented to the\nGrand Jury evidence arising from the Federal Bureau of\nInvestigation’s inquiry into the Traffic Court. Appellants\nLowry, Mulgrew, and Tynes testified and the Government\nbrought perjury charges against them for statements they\nmade to the Grand Jury. After Hird and Alfano pleaded\nguilty, the rest of the Appellants went to trial. The jury\nacquitted Lowry, Mulgrew, and Tynes of all counts against\nthem on wire fraud, mail fraud, and conspiracy. But it found\nthem guilty of perjury. Tynes, Lowry, and Mulgrew\nchallenge their convictions by raising similar legal arguments\nabout the sufficiency of the evidence.\n As with all challenges to the sufficiency of the\nevidence, we use a highly deferential standard of review. See\nUnited States v. Caraballo-Rodriguez, 726 F.3d 418, 430 (3d\nCir. 2013) (en banc). We examine the record in a light most\nfavorable to the prosecution, and will not disturb the verdict if\n“any rational trier of fact could have found the essential\nelements of the crime beyond a reasonable doubt.” United\nStates v. McGee, 763 F.3d 304, 316 (3d Cir. 2014) (emphasis\nin original) (quoting Jackson v. Virginia, 443 U.S. 307, 319\n(1979)). Tynes, Lowry, and Mulgrew argue that the\nquestions asked of them at trial were fatally vague and/or that\ntheir answers were truthful. As a result, they contend that\nthese questions and answers are an inadequate basis for a\nperjury conviction.\n\n A conviction for perjury before a grand jury requires\nthe Government to prove that the defendant took an oath\nbefore the grand jury and then knowingly made a “false\nmaterial declaration.” 18 U.S.C. § 1623. But we recognized\n(in the context of a sentencing enhancement for perjury) that\nsometimes “confusion, mistake, or faulty memory” results in\n\n\n\n\n 25\n\finaccuracies that cannot be categorized as a “willful attempt\nto obstruct justice” under perjury statutes. United States v.\nMiller, 527 F.3d 54, 75 (3d Cir. 2008) (quoting U.S.\nSentencing Guidelines Manual § 3C1.1 cmt. n.2 (U.S.\nSentencing Comm’n 2003). So we do understand that\n“[p]recise questioning is imperative as a predicate for the\noffense of perjury.” Bronston v. United States, 409 U.S. 352,\n362 (1973).\n\n Precision, however, is assessed in context. An\nexaminer’s line of questioning should, at a minimum,\nestablish the factual basis grounding an accusation that an\nanswer to a particular question is false. Miller, 527 F.3d at\n78. So a perjury conviction is supported by the record “when\nthe defendant’s testimony ‘can reasonably be inferred to be\nknowingly untruthful and intentionally misleading, even\nthough the specific question to which the response is given\nmay itself be imprecise.’” United States v. Serafini, 167 F.3d\n812, 823 (3d Cir. 1999) (quoting United States v. DeZarn,\n157 F.3d 1042, 1043 (6th Cir. 1998)).\n\n Challenges to the clarity of a question are typically left\nto the jury, which has the responsibility of determining\nwhether the defendant understood the question to be\nconfusing or subject to many interpretations. United States v.\nSlawik, 548 F.2d 75, 86 (3d Cir. 1977). Moreover, consistent\nwith our standard of review, we will not disturb a jury’s\ndetermination that a response under oath constitutes perjury\nunless “it is ‘entirely unreasonable to expect that the\ndefendant understood the question posed to him.’” Serafini,\n167 F.3d at 820 (quoting United States v. Ryan, 828 F.2d\n1010, 1015 (3d Cir. 1987), abrogated on other grounds by\n\n\n\n\n 26\n\fUnited States v. Wells, 519 U.S. 482 (1997)). 22 On appeal,\nwe review every aspect of the record pertinent to both the\nquestion and answer to reach a conclusion about whether, in\ncontext, the witness understood the question well enough to\ngive an answer that he or she knew to be false. See Miller,\n527 F.3d at 78. Our review, however, is focused on glaring\ninstances of vagueness or double-speak by the examiner at the\ntime of questioning (rather than artful post-hoc interpretations\nof the questions) that—by the lights of any reasonable fact-\nfinder—would mislead or confuse a witness into making a\nresponse that later becomes the basis of a perjury conviction.\nQuestions that breach this threshold are “fundamentally\nambiguous” and cannot legitimately ground a perjury\nconviction. Id. at 77. 23\n\n\n22\n The Court of Appeals for the Second Circuit underscored\nthe high bar this establishes for appellants by noting that a\nfundamentally ambiguous question is “not a phrase with a\nmeaning about which men of ordinary intellect could agree,\nnor one which could be used with mutual understanding by a\nquestioner and answerer unless it were defined at the time it\nwere sought and offered as testimony.” United States v.\nLighte, 782 F.2d 367, 375 (2d Cir. 1986) (quoting United\nStates v. Lattimore, 127 F. Supp. 405, 410 (D. D.C.), aff’d,\n232 F.2d. 334 (D.C. Cir. 1955)).\n23\n The rule of fundamental ambiguity is intended to\n“preclude convictions that are grounded on little more than\nsurmise or conjecture, and . . . prevent witnesses . . . from\nunfairly bearing the risks associated with the inadequacies of\ntheir examiners.” Ryan, 828 F.2d at 1015.\n\n\n\n\n 27\n\f That is the law applicable to the claims raised by\nTynes, Lowry and Mulgrew. But, because our review is fact-\ndependent, and because each raises some unique issues, we\nwill address each of their claims individually. 24\n B.\n\n\n\n\n24\n Adopting the arguments made by Alfano and Hird,\nAppellants Lowry, Mulgrew and Tynes assert that the\nGovernment improperly charged them with conspiracy, wire\nfraud, and mail fraud. Therefore, they assert, their joint trial\non these counts of the indictment prejudiced the jury’s\ndeliberation on the charges of perjury. They claim such\nevidence would have been excluded under Federal Rule of\nEvidence. 403. They also contend that, without a charge of\nconspiracy, the joinder of their cases would have been\nimpermissible under Federal Rule of Criminal Evidence 8(b)\nor, at the very least, severance of their cases would have been\nwarranted under Federal Rule of Criminal Procedure 14(a).\nCertainly, where there is evidence of prejudice resulting from\n“spillover” evidence from counts that should have been\ndismissed, reversal is warranted. See United States v. Wright,\n665 F.3d 560, 575-577 (3d Cir. 2012). But we have\nconcluded that the District Court did not err by denying the\nmotion, under Federal Rule of Civil Procedure 12(b)(3), to\ndismiss the conspiracy, wire fraud and mail fraud counts of\nthe indictment. Thus, Appellants’ spillover argument has\nbeen nullified. Likewise, Appellants have no basis to claim\nthat the Court unfairly prejudiced them by not granting\nseparate trials.\n\n\n\n\n 28\n\f Appellant Tynes 25\n\n Appellant Tynes claims her convictions for perjury at\nCount 71 and Count 72 lack sufficient evidence because she\nwas responding to questions that were fundamentally\nambiguous. The perjury charged at Count 71 arises from the\nfollowing exchange.\n\n Q. In all the years\n you’ve been [at Traffic\n Court] have you\n ever been asked to give\n\n\n25\n Tynes filed a separate motion to dismiss. App. 291-99.\nThe record also contains Tynes’ proposed order to join\nSullivan’s motion to dismiss. App. 290. However, Tynes’\nmotion contains no such request. Moreover, the\nGovernment’s response to the motions notes that Lowry and\nMulgrew moved to join (without argument), and makes no\nmention of Tynes. The District Court’s ruling on Tynes’\nmotion to dismiss relates only to the arguments she made\nseparately in her brief. As a result, we cannot consider\nTynes’ arguments on appeal that relate to those raised in\nSullivan’s motion. Moreover, since she failed to raise any of\nthe arguments she made in her separate motion to dismiss,\nthese arguments are waived. With that said, we will affirm\nthe District Court’s ruling on the Motion raised by Sullivan\nand joined by the five Appellants. Therefore, we need not\naddress Tynes’ assertion that the District Court’s mishandled\nher joinder motion because it does not prejudice the outcome\nof her appeal.\n\n\n\n\n 29\n\f favorable treatment on\n a case to anybody?\n\n A. No, not favorable\n treatment. People basically\n know me. The lawyers\n know me. The court\n officers know me. I have\n been called a nononsense\n person because I’m just not\n that way. I take my\n position seriously, and the\n cards fall where they may.\n\nApp. 255, 5720. 26 Tynes contends that the Government\npursued a novel theory here (applying federal fraud statutes to\nallegations of ticket fixing) and used the vague term\n“favorable treatment” to gloss over its uncertainty about what,\nultimately, would constitute an illegal act. She points out that\nthe term had not been used before in reference to this case\nand that the Government offered no explanation or definition\nof the term to alert Tynes to the intent of the question.\n\n Also, from Tynes’ perspective, every litigant\nappearing before a court seeks an outcome that is favorable,\nthus making “favorable treatment” a term that essentially\nreferred to “how litigation works.” She claims that its use\namounted to a fishing expedition designed to capture unfairly\n\n26\n We cite to the testimony quoted in the indictment and the\nGrand Jury that was used at trial. We note that there are some\ntypographical inconsistencies between these sources and in\nthose instances we have quoted the Grand Jury testimony.\n\n\n\n\n 30\n\fthe entirety of her conduct in the courtroom. She warns that\nthis is precisely the type of “open-ended construction” in\nquestioning that we found unacceptable in Serafini. 167 F.3d\nat 822.\n\n Tynes makes a related argument against her perjury\nconviction for Count 72. That conviction is based on this\nexchange.\n Q. You’ve never taken\n action on a request?\n\n A. No.\n\nApp. 257, 5722. She maintains that the word “request” was\npresented to the jury as a follow-on to the question grounding\nCount 71, requiring a person to link the term “favorable\ntreatment” and the word “request” to make sense of it. She\nargues that the Government took advantage of the ambiguity\nof “favorable treatment,” forcing the jury to speculate that\nTynes interpreted “request” as “favorable treatment.” This\nreliance on “sequential referents” is, from her perspective,\nexactly what we criticized in Serafini. 167 F.3d at 821. But\nshe misconstrues our holding.\n\n In Serafini, the surrounding questions focused on a\ndifferent topic. This bolstered appellant’s argument in that\ncase that the question on which the perjury conviction rested\nwas fundamentally ambiguous. Id. The appellant said the\nmultiplicity of topics in surrounding questions caused the jury\nto speculate improperly on how he understood the question at\nissue. We said: “The meaning of individual questions and\nanswers is not determined by ‘lifting a statement . . . out of its\nimmediate context,’ when it is that very context which fixes\n\n\n\n\n 31\n\fthe meaning of the question.” Serafini, 167 F.3d at 821\n(quoting United States v. Tonelli, 577 F.3d 194, 198 (3d Cir.\n1978)). In the case of Serafini, the context made the\nconfusing nature of the question apparent. The various topics\nin surrounding questions created sufficient ambiguity to\nundermine the conviction. Id.\n\n Here, however, even though the terms used by the\nexaminer changed, we conclude that the line of questioning—\nincluding both questions that ground Count 71 and 72—have\nan obvious, consistent focus.\n\n Q. In all the years\n you’ve been [at Traffic\n Court] have you\n ever been asked to give\n favorable treatment on\n a case to anybody?\n\n A. No, not favorable\n treatment. People basically\n know me. The lawyers\n know me. The court\n officers know me. I have\n been called a nononsense\n person because I’m just not\n that way. I take my\n position seriously and the\n cards fall where they\n may. Most of the time . . .\n the people in my Court\n plea bargain. They know\n that most of the time,\n\n\n\n\n 32\n\fninety percent of the time,\nsay 90 percent, I go with\nthe police officer’s\nrecommendation. . . .\n\nQ. So, in all those years\nno one has ever asked you\nto find somebody not\nguilty--\n\nA. No.\n\nQ. --or to find a lesser\nviolation; find a lesser fine;\nanything along those lines?\n\nA. No. I will say to\npeople go to court, go to\ntrial and see what\nhappens. . . .\n\nQ. Ward leaders,\npoliticians has anyone\ncalled you and said I\nhave Johnny Jones coming\nup next week and I\nwould appreciate it if -- if\nyou would look\nfavorably on him when he\ncomes through? Has\nanything like that ever\nhappened?\n\n\n\n\n 33\n\f A. Throughout the\n years ward leaders and\n people have called all the\n time and asked me\n questions. The only thing I\n will say to them is they\n need to go to court. If you\n think it’s a problem, they\n need to hire a lawyer, or\n make sure you bring all\n your evidence to court. If\n it’s something like\n inspection, make sure you\n bring your -- papers and\n things like that. That’s\n what I would tell them to\n do. I give advice that\n way. I don’t know if that’s\n wrong or not, but I do.\n\n Q. You’ve never taken\n action on a request?\n\n A. No.\n\nApp. 528-29, 530; 5720-22. This broader context would give\nany reasonable fact-finder more than enough basis to\nconclude that the witness knew the point of reference for both\nthe term “favorable treatment” and “request” was ticket\nfixing. In fact, Tynes is asking us to do precisely the thing we\ncriticized in Serafini, to lift a phrase or statement out of its\ncontext. Serafini, 167 F.3d at 821. Tynes has not persuaded\nus that the question harbors any fatal ambiguity.\n\n\n\n\n 34\n\f Tynes next contends that her responses to questions\ngrounding Count 71 and Count 72 cannot support convictions\nfor perjury because they were literally true. Of course,\nperjury arises only from making knowingly false material\ndeclarations. 18 U.S.C. § 1623. Therefore, a witness who\nanswers an ambiguous question with a non-responsive answer\nthat the witness believes is true—even if the answer is\nmisleading—does not commit perjury. See Bronston, 409\nU.S. at 361-62; see also United States v. Reilly, 33 F.3d 1396,\n1416 (3d Cir. 1994).\n Tynes argues that, because she regarded the question\nabout favorable treatment as vague, she interpreted it as\nasking whether she accepted any bribes in exchange for a\njudgment of not guilty or a reduced punishment. Her\nresponse of “no” (grounding Count 71) is literally true—she\nsays—because there is no evidence that she accepted any\nbribes in return for giving preferential outcomes in the\nadjudication of some individuals who were cited for breaking\nthe law. Under this theory, the same argument can also\nnegate the charges at Count 72 since she says she did not\naccept any “requests” (bribes) in exchange for preferential\ntreatment.\n\n Although the jury is permitted reasonable inferences\ndrawn from the record about the witness’ understanding of\nthe truth or falsity of the answer, it is not (as we noted above)\npermitted to reach conclusions based merely on speculation\nor conjecture. See Bronston, 409 U.S. at 359. Tynes’\nassertion of literal truth is undermined because the trial record\nsupports no reasonable inference that the Government was\nasking her about matters outside of the alleged bribes, nor\n\n\n\n\n 35\n\fdoes it provide any reason why Tynes would interpret the\nquestion in this way.\n\n Finally, Tynes contends that the evidence was not\nsufficient to support her conviction. However, the jury heard\nTynes’ personal assistant, Medaglia “Dolly” Warren, testify\nthat she received from personal assistants of other judges\nthree to four cards per week requesting consideration. Each\ncard had the name of a person who was appearing before\nTynes on that day. She passed these to Tynes’ court officer,\nwho was present during the proceedings. App. 4593-95.\nTynes also instructed Warren to give similar cards to the staff\nof other judges. App. 4598. Warren knew to act discreetly\nwhen she was transferring the cards. App. 4599. The jury\nalso heard testimony from those who actually received\nconsideration from Tynes. For example, Timothy Blong was\ncited for reckless driving and driving without a license. He\nadmitted in testimony that he did not have a license when he\nwas cited. App. 3150. He also testified that he requested\nconsideration through a Traffic Court employee (Danielle\nCzerniakowski, who worked as a personal assistant to a\nTraffic Court judge) with whom he was acquainted. When he\nappeared in court, he was simply told that his case was\ndismissed. He did not have to say anything, App. 3159-60.\nBlong testified he was told his case was dismissed because\nthe police officer did not appear (App. 3160-61), but the\ngovernment produced evidence that an officer was present.\nApp. 3193-96. The Government also showed that Tynes was\nthe presiding judge in Blong’s case. App. 3193. Richard\nCarrigan—who admitted in testimony that he drove through a\nred light—described a similar experience in which, after\nrequesting favorable treatment through Judge Lowry’s\npersonal assistant, Kevin O’Donnell, his case was dismissed\n\n\n\n\n 36\n\fby Judge Tynes without ever having to say a word. App.\n3178-82.\n\n Tynes does not challenge any of this in her appeal.\nInstead she focuses on the weight of other evidence and\nperceived gaps in testimony. We conclude that all of this\nprovides more than a sufficient basis to support a reasonable\njury’s conclusion that Tynes did “give favorable treatment on\na case,” and did “take[] action on a request.” App. 528-30.\n\n For all of these reasons, we will affirm the judgment of\nconviction on perjury as to Appellant Tynes.\n C.\n\n Appellant Lowry 27\n\n Like Tynes, Appellant Lowry advances arguments of\nfundamental ambiguity and literal truth. His perjury\nconviction centered on one question and answer.\n\n\n Q. So if I understand\n your testimony, you’re\n saying you don’t give out\n special favors; is that right?\n\n A. No, I treat\n everybody in that\n courtroom the same.\n\n\n27\n Lowry was charged with perjury in Count 69 of the\nindictment.\n\n\n\n\n 37\n\fApp. 489. Lowry attacks the Government’s use of the term\n“special favors” as one with many potential meanings.\nHowever, as we noted above in our reference to Serafini, we\nreject arguments that lift individual questions or answers—or\nindividual phrases embedded in either—from the context of\nsurrounding questions that help fix their meaning. Serafini,\n167 F.3d at 821. The larger context for the question asked of\nLowry is as follows.\n\n Q. So if I understand\n your testimony, you’re\n saying you don’t give out\n special favors; is that right?\n\n A. Well, I know it\n appears that way; and it’s\n hard for me to prove to\n you . . .\n\n Q. I’m just asking,\n your testimony is you don’t\n give out special favors, is\n that right?\n\n A. No, I treat\n everybody in that\n courtroom the same.\n\n Q. You treat everybody\n fairly?\n\n A. I’m a lenient judge.\n I will admit to that.\n\n\n\n\n 38\n\f Q. You treat everybody\n fairly?\n\n A. Yes, I do.\n\n Q. And these notices\n that you get from your\n personal or from other\n people, they don’t affect\n you in any way; is that\n right?\n\n A. Virtually no effect\n at all.\n\n\nApp. 489-90.\n\n Lowry’s assertion that the phrase “special favors” is\nsubject to many interpretations is unconvincing. We note two\nthings. First, the line of questioning reasonably supports a\nconclusion that this inquiry referenced conduct associated\nwith allegations of ticket fixing. Second, Lowry answered as\nif his understanding of the question was consistent with this\ninterpretation. He said that he was aware it may “appear” that\nhe gave special favors. He also defended himself by saying\nthat such requests did not affect his conduct in the courtroom\nat all. If—as he says—he understood “special favors” to\nmean fair treatment, his answer makes no sense.\n\n Lowry next claims that, since the question was\nstructured to elicit a negative response, his answer cannot be\n\n\n\n\n 39\n\fused as the basis of a perjury charge. Relatedly, he contends\nthat the question was merely a summation of an answer that\nhe gave just before this question. In essence he argues that\nthis was a leading question. We have concluded, in the\ncontext of a trial, that the propriety of leading questions in\ndirect examinations is a matter left to the sound discretion of\nthe trial judge. See United States v. Montgomery, 126 F.2d\n151, 153 (3d Cir. 1942). We extend the same deference here\nto the District Court’s decision to admit this portion of the\nGrand Jury transcript. We do not regard the question as\nfundamentally unfair or unclear, or something outside the\nnorm of questions typically employed on direct examination.\nFor these reasons, we conclude that the District Court did not\nabuse its discretion here.\n\n Alternatively, Lowry argues that—if the term is\nunderstood to reference fixing tickets—there is no evidence\nto contradict his response that requests for special favors did\nnot impact any of his adjudications. We do not agree. The\nrecord contains the following testimony.\n\n Kevin O’Donnell, who was Lowry’s personal\nassistant, testified about Lowry’s involvement with requesting\nand giving consideration. He said that Lowry made four to\nfive requests each month for consideration and that\nO’Donnell transmitted them to the personal assistants of other\nTraffic Court judges. App. 1854. Likewise, he said other\njudges transmitted requests for consideration to Lowry\nthrough their personal assistants. App. 1812-13. Appellant\nHird and various politicians also made requests of Lowry for\nconsideration. App. 1827-28, 1832-33. O’Donnell said he\nwould give the requests to Lowry on the day scheduled for\nhearing on the citation. App. 1818-19. The requests were for\n\n\n\n\n 40\n\fpreferential treatment in the adjudication of particular\ncitations: typically the requests were for “removing points”\nand obtaining a “not guilty” judgment. App. 1819.\nO’Donnell said he sometimes had to signal Lowry in the\ncourtroom to remind him that a particular case was supposed\nto receive consideration. App. 1822-23. He testified from\nhis own observation that Lowry typically honored requests\nfor consideration. App. 1829. He also declared if Lowry\nclaimed he never gave consideration or asked it of others, this\nwould not be truthful. App. 1813. The same assistant\ntestified that if Lowry testified that he ignored requests for\nconsideration, or that he never honored requests for\nconsideration, that testimony would not be true. App. 1855.\nThe Government also asked: “If [Lowry] claimed that . . .\nconsideration requests had no impact when he disposed of\ncases, would that be true?” The assistant responded,\n“probably not.” Id.\n\n Another witness, Walt Smaczylo, employed as a court\nofficer in the Traffic Court, provided an example of how\n“consideration” worked in the courtroom.\n\n When someone comes in,\n for example, for a reckless\n driving ticket and that\n judge normally comes\n down pretty hard and finds\n that defendant guilty and\n then the same type cases\n come in and you see a\n defendant walk out either\n not guilty or a significantly\n reduced charge.\n\n\n\n\n 41\n\fApp. 1912. The Government asked Smaczylo if he saw\nLowry preside over such instances, and he answered: “That’s\ncorrect, yes.” Id. Smaczylo testified that requests for\nconsideration were written on small note cards or “sticky”\nnotes and that he saw Lowry in possession of these cards and\nnotes. App. 1914. He also provided a generalized example\nof consideration, based on his observation and understanding,\nin which a reckless driving citation would be reduced to\ncareless driving. In such instances, he indicated that a $300\nto $400 fine would be cut in half. He said: “So, that money\nwas not collected, obviously, by the state. If that ticket was\nfixed then I saw it as stealing.” App. 1919. Smaczylo was\nasked: “[I]f Judge Lowry testified at the [G]rand [J]ury he\ndidn’t give consideration would that be a truth or would that\nbe a lie?” He responded: “That would not be the truth.”\nApp. 1921.\n\n All of this testimony provides more than a sufficient\nbasis to support a reasonable jury’s conclusion that Lowry\nwas not truthful when he responded to the Government’s\nquestion about special favors. 28\n\n28\n Lowry points to the cross-examination of both witnesses in\nwhich they seem to equivocate on some of their observations\nand responses to the Government. For instance O’Donnell\nstated his view that giving consideration was no different\nfrom the leniency that Lowry extended to every other person\nwho pleaded not guilty and appeared at the hearing.\nHowever, we do not weigh the credibility of evidence in the\nrecord. We only judge whether there is sufficient evidence in\nthe record to support a reasonable fact-finder’s determination\nthat the record supported conviction of Lowry on a charge of\n\n\n\n\n 42\n\f Finally, Lowry argues that the Government’s question\nsought a dispositive response from him on the charges of\nconspiracy and fraud. He says an affirmative answer to\nwhether he gave “special favors” to certain individuals would\nhave been enough to convict him of conspiracy and fraud.\nThus, he maintains that his acquittal on charges of mail fraud,\nwire fraud, and conspiracy is res judicata as to the perjury\ncharges that are based on his answer. He said he did not\ncommit fraud and the jury agreed with him. Therefore, he\nsays, he did not perjure himself. However, even if we\naccepted Lowry’s characterization of the question, we reject\nthis argument.\n\n First, a jury’s determination that Lowry’s ticket-fixing\nconduct did not constitute wire fraud, mail fraud, and\nconspiracy does not preclude its determination that he lied\nabout this conduct before the Grand Jury. Moreover, as the\nSupreme Court has articulated, a verdict on one count that\nseems to be at odds with another “shows that either in the\nacquittal or the conviction the jury did not speak their real\nconclusions, but that does not show that they were not\nconvinced of the defendant’s guilt.” United States v. Powell,\n469 U.S. 57, 63 (1984) (quoting Dunn v. United States, 284\nU.S. 390, 393 (1932)). It is impossible to know in such cases\nwhether the verdicts were an exercise of lenity by the jury or\noutright error.\n\n Nonetheless, as the Powell Court noted, any\nassessment of the jury’s rationale for its verdicts “would be\n\n\nperjury. See United States v. Richardson, 658 F.3d 333, 337\n(3d Cir. 2011).\n\n\n\n\n 43\n\fbased either on pure speculation or would require inquiries\ninto the jury’s deliberations that courts generally will not\nundertake.” Id. at 58. So, even if Lowry was correct that the\nacquittal is relevant to his response to the question grounding\nhis perjury conviction, we are not convinced that his perjury\nconviction is unfounded. Given the substantial body of\nevidence presented to the jury, nothing here demands that we\nabandon the deference we traditionally give to the collective\njudgment of the jury. For all these reasons, we will affirm the\njury’s verdict as to Lowry.\n\n D.\n\n Appellant Mulgrew 29\n\n Mulgrew does not argue that the question asked at the\nGrand Jury was ambiguous, he simply maintains that his\nstatement was truthful. 30 The questions and answers\ngrounding his perjury conviction are as follows.\n\n Q. How about your\n personal, has your personal\n received any calls like that\n from other judges, other\n ward leaders that she’s\n conveyed to you, saying\n\n29\n Mulgrew was charged with perjury in Count 70 of the\nindictment.\n30\n Mulgrew’s claims are reviewed for plain error because he\ndid not make the same argument before the District Court.\nUnited States v. Syme, 276 F.3d 131, 148 (3d Cir. 2002).\n\n\n\n\n 44\n\f so-and-so has called about\n this case?\n\n A. If she did, she didn’t\n convey them to me.\n\n\nApp. 432-33 (emphasis added). Shortly after this, the\nfollowing exchange occurred:\n\n Q. Let me make sure as\n well that if I got your\n testimony correct [sic].\n You’re saying that if other\n people, whether they be\n political leaders, friends\n and family, anybody is\n approaching your personal\n and asking her specifically\n to look out for a case, see\n what she can do in a case,\n give preferential treatment,\n however you want to\n phrase it, that she is not\n relaying any of that\n information on to you; is\n that correct?\n\n A. No, she isn’t.\n\nApp. 438. As to the first exchange, Mulgrew claims that the\nGovernment’s use of the word “call” referred exclusively to\ntelephone calls. This mattered to him, he says, because others\n\n\n\n\n 45\n\fhad testified that personal assistants of other Traffic Court\njudges would give index cards to his personal assistant in his\nchambers or robing room containing names of some\nindividuals whose tickets were listed for hearing. Mulgrew\nclaims that there is no evidence that he ever received any\nphone calls asking that he act extrajudicially to give well-\nconnected individuals preferential treatment. The implication\nis that, had the Government asked him about receiving index\ncards with such requests, his answer would have been\ncompletely different.\n As with Tynes and Lowry, our review of claims of\nliteral truth drives us to examine the context of the question.\n\n Q. How about other\n judges, have other judges\n ever approached you or\n called to you or get a\n message to you either\n themselves or through their\n personals saying that\n someone is going to be on\n your list next week or next\n Monday and can you could\n some special way towards\n the case?\n\n A. No, they haven’t.\n\n Q. Never?\n\n A. No.\n\n\n\n\n 46\n\fQ. How about your\npersonal, has your personal\nreceived any calls like that\nfrom other judges, other\nward leaders that she’s\nconveyed to you saying so\nand so has called about this\ncase?\n\nA. If she did, she didn’t\nconvey them to me.\n\nQ. And your personal\nis who?\n\nA. Gloria McNasby.\n\nQ. Have you ever seen\non traffic court files --You\nactually get a file when\nsomeone’s case is called?\n\nA. Right.\n\nQ. So the case is called\nand you get a file presented\nto you; is that right?\n\nA. uh-huh.\n\nQ. Have you ever seen\nany index cards or\nnotations on the file\n\n\n\n\n 47\n\f indicating that a person has\n called or taken some\n special interest in this\n case?\n\n A. Nope.\n\nApp. 432-33 (emphasis added). The transcript makes it\nobvious that Mulgrew’s singular reliance on the reference to a\n“call” ignores the thrust of the Government’s line of\nquestions. The questions focus on the substance of the\ncommunications between Mulgrew’s personal assistant and\nhimself, rather than the mode of those communications.\n\n Mulgrew also claims that he responded truthfully to\nthe second question.\n\n Q. Let me make sure as\n well that if I got your\n testimony correct [sic].\n You’re saying that if other\n people whether they be\n political leaders, friends\n and family, anybody is\n approaching your personal\n and asking her specifically\n to look out for a case, see\n what she can do in a case,\n give preferential treatment,\n however you want to\n phrase it, that she is not\n relaying any of that\n\n\n\n\n 48\n\f information on to you; is\n that correct?\n\n A. No, she isn’t.\n\n Q. Wouldn’t you want\n to know it?\n\n A. No, I don’t want to\n know. Then I never have to\n worry about what I do in\n the courtroom.\n\nApp. 437-38 (emphasis added). Apparently focusing on the\nwords “see what she can do,” he says that he answered\ntruthfully by responding that his personal assistant did not tell\nhim that people were approaching her and asking her to give\nthem preferential treatment. But, as with the first question,\nMulgrew cherry-picks a small part of the question out of\ncontext, distorting it. The full text and follow up question\nshow that the thrust of the inquiry was whether Mulgrew’s\npersonal assistant was informing him of the names of those\nrequesting preferential treatment from him. And Mulgrew’s\nresponse to the follow-up question —saying that he did not\nwant to know so that he did not have to worry about what he\ndid in the courtroom—is consistent with one who understood\nthis. App. 438.\n\n We conclude that, ultimately, the evidence is sufficient\nfor a reasonable jury to conclude Mulgrew understood that\nboth of these questions were focused on whether his personal\nassistant informed him of requests for him to give preferential\ntreatment, and that he answered in the negative to both.\n\n\n\n\n 49\n\f Mulgrew alternatively asserts that the District Court\nerred by refusing to admit additional testimony from the\nGrand Jury that he claims is relevant to his perjury\nconviction. 31 After the Government introduced Mulgrew’s\nGrand Jury testimony, Mulgrew sought the admission of other\nportions of his testimony. But the District Court sustained the\nGovernment’s hearsay objection. The portion of the\ntranscript supporting the perjury conviction is as follows:\n\n Q. [W]hether you have\n ever been asked to provide,\n what I’ll call, favorable\n treatment for people in\n traffic court or however\n you define that, whether it\n would be special handling,\n keep an eye out for a\n ticket, do me a favor.\n Have you ever been asked\n to provide any type of\n treatment like that for\n people in traffic court?\n\n A. People have asked\n me for consideration, but I\n give consideration to\n everybody that comes in\n my courtroom[,] so it\n\n31\n We review the District Court’s ruling on the admissibility\nof evidence for abuse of discretion. United States v. Green,\n617 F.3d 233, 239 (3d Cir. 2010).\n\n\n\n\n 50\n\f doesn’t make a difference\n to me.\n\n\nApp. 422-23. The basis for the Government’s hearsay\nobjection to this portion of the testimony was that it raised an\nout-of-court statement not offered by a party opponent.\n\n Mulgrew first contends that the District Court erred by\nruling that this was hearsay because it was not offered for the\ntruth of the matter asserted. He says that the testimony was\ninstead offered to show his state of mind later in his\ntestimony. See United States v. Hoffecker, 530 F.3d 137,\n191-92 (3d Cir. 2008). However, we conclude that it was not\nan abuse of discretion for the District Court to sustain the\nGovernment’s hearsay objection. It was reasonable for the\nDistrict Court to conclude here that his response relied on\nout-of-court statements offered to assert his innocence since\nhis response conveys a declaration that he treated no person\ndifferent from another.\n\n Mulgrew also argues that this portion of the transcript\nis admissible under Federal Rule of Evidence 106: “[i]f a\nparty introduces all or part of a writing or recorded statement,\nan adverse party may require the introduction, at that time, of\nany other part—or any other writing or recorded statement—\nthat in fairness ought to be considered at the same time.”\nMulgrew maintains that this question and answer provides\ncontext showing that he did not commit perjury. He also\nmaintains that the “doctrine of completeness” applies here:\nfairness demanded the admission of the statements. See\n\n\n\n\n 51\n\fUnited States v. Soures, 736 F.2d 87, 91 (3d Cir. 1984). 32 We\nare not convinced.\n\n The excerpt at issue occurs many pages before the\ntestimony regarded as perjurious. It is unrelated in the overall\nsequence of questions and to the answers grounding his\nconviction. Moreover, as the intervening pages suggest, it\nwas separated by the passage of time during questioning. We\nalso fail to see how Mulgrew’s equivocation over the term\n“consideration” gives helpful context to his later denial of\nreceiving requests for consideration. For these reasons, we\nconclude the District Court did not abuse its discretion by\nsustaining the Government’s hearsay objection.\n\n IV.\n\n Appellant Singletary 33\n\n\n32\n “Under this doctrine of completeness, a second writing may\nbe required to be read if it is necessary to (1) explain the\nadmitted portion, (2) place the admitted portion in context, (3)\navoid misleading the trier of fact, or (4) insure a fair and\nimpartial understanding.” Soures, 736 F.2d at 91.\n33\n Appellant Singletary was charged with making false\nstatements in Counts 73 and 74 of the indictment. He states\nin his brief that he ‘joins all arguments on behalf of co-\nappellants pursuant to Federal Rules of Appellate Procedure\n28(i).” Singletary Br. 19. To the extent that he joins the\nargument of prejudice resulting from the trial on the fraud and\nconspiracy charges, we already have determined that the\nindictment was proper and no prejudice resulted from\n\n\n\n\n 52\n\f During the investigation of the Traffic Court by the\nFederal Bureau of Investigation, Appellant Singletary was\namong those interviewed. The jury acquitted Singletary of all\ncounts of wire fraud, mail fraud, and conspiracy. It found\nhim guilty of false statements made to the Federal Bureau of\nInvestigation. At sentencing, over Singletary’s objection, the\nDistrict Court sentenced Singletary using the Guideline on\nobstruction.\n\n The Government agrees that the single count on which\nhe was convicted does not contain all of the elements of\nobstruction. U.S.S.G. § 2J1.2. For this reason, the\nGovernment agrees with Singletary that he is entitled to a\nremand for resentencing. Accordingly, we will vacate the\njudgment of sentence as to Singletary and remand to the\nDistrict Court for resentencing.\n\n V.\n\n For all of these reasons, we will vacate the judgment of\nsentence of the District Court with regard to Appellant\nSingletary and remand for resentencing. We will affirm the\njudgments of the District Court as to Appellants Alfano, Hird,\nLowry, Mulgrew and Tynes.\n\n\n\nbringing these charges to trial. As for the challenges to\nperjury in Counts 72 and 74, we note that Singletary was\ncharged with a different crime: false statements in a federal\ninvestigation pursuant to 18 U.S.C. § 1001. In addition, the\nchallenges to all of such charges are inherently fact-intensive.\nAs he did not provide a factual basis for such a challenge, we\nregard the issue to be waived.\n\n\n\n\n 53", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360293/", "author_raw": "NYGAARD, Circuit Judge."}]}
GREENAWAY
NYGAARD
FISHER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583040/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America v. William HIRD, Appellant at No. 14-4754 United States of America v. Thomasine Tynes, Appellant at No. 14-4804 United States of America v. Robert Mulgrew, Appellant at No. 14-4812 United States of America v. Michael Lowry, Appellant at No. 15-1344 United States of America v. Willie Singletary, Appellant at No. 15-1739 United States of America v. Henry P. Alfano, AKA Ed, AKA Eddie, Henry P. Alfano, Appellant at No. 15-3765\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n\n __________\n\nNos. 14-4754, 14-4804, 14-4812, 15-1344, 15-1739, 15-3765\n __________\n\n UNITED STATES OF AMERICA\n v.\n WILLIAM HIRD,\n Appellant at No. 14-4754\n __________\n\n UNITED STATES OF AMERICA\n v.\n THOMASINE TYNES,\n Appellant at No. 14-4804\n __________\n\n UNITED STATES OF AMERICA\n v.\n ROBERT MULGREW,\n Appellant at No. 14-4812\n __________\n\n UNITED STATES OF AMERICA\n v.\n MICHAEL LOWRY,\n Appellant at No. 15-1344\n\f __________\n\n UNITED STATES OF AMERICA\n v.\n WILLIE SINGLETARY,\n Appellant at No. 15-1739\n ___________\n\n UNITED STATES OF AMERICA\n v.\n HENRY P. ALFANO,\n aka Ed, aka Eddie,\n\n Henry P. Alfano,\n Appellant at No. 15-3765\n __________\n\n On Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n\n (District Court Criminal Nos. 2-13-cr-00039-007,\n2-13-cr-00039-005, 2-13-cr-00039-003, 2-13-cr-00039-002,\n 2-13-cr-00039-004, 2-13-cr-00039-008)\n District Judge: Honorable Robert F. Kelly\n District Judge: Honorable Lawrence F. Stengel\n\n Argued October 23, 2017\n\n BEFORE: GREENAWAY, JR., NYGAARD,\n and FISHER, Circuit Judges\n\n\n (Opinion Filed: January 18, 2019)\n\n\n\n\n 2\n\fAngela Halim\nHalim Drossner\n1528 Walnut Street, Suite 1501\nPhiladelphia, PA 19102\n\nGregory J. Pagano\n1315 Walnut Street, 12th Floor\nPhiladelphia, PA 19107\n Counsel for Appellant in No. 14-4754\n\nLisa A. Mathewson [Argued]\n123 South Broad Street, Suite 810\nPhiladelphia, PA 19109\n Counsel for Appellant No. 14-4804\n\nPeter Goldberger [Argued]\nPamela A. Wilk\n50 Rittenhouse Place\nArdmore, PA 19003\n Counsel for Appellant in No. 14-4812\n\nMichael J. Engle [Argued]\nStradley Ronon Stevens & Young\n2005 Market Street, Suite 2600\nPhiladelphia, PA 19103\n\nMeredith A. Lowry\n1528 Walnut Street, Suite 1501\nPhiladelphia, PA 19102\n Counsel for Appellant in No. 15-1344\n\n\n\n\n 3\n\fWilliam J. Brennan\n1600 Locust Street\nPhiladelphia, PA 19103\n Counsel for Appellant in No. 15-1739\n\nMark E. Cedrone [Argued]\nCedrone & Mancano\n123 South Broad Street, Suite 810\nPhiladelphia, PA 19109\n Counsel for Appellant in No. 15-3765\n\n\nLouis D. Lappen\nDenise S. Wolf\nAnthony J. Wzorek\nRobert A. Zauzmer [Argued]\nOffice of United States Attorney\n615 Chestnut Street, Suite 1250\nPhiladelphia, PA 19106\n Counsel for Appellee\n\n\n\n\n __________\n\n OPINION OF THE COURT\n __________\n\nNYGAARD, Circuit Judge.\n\n I.\n\n\n\n\n 4\n\f In the run-up to a joint trial on a 77-count indictment\nthat charged Appellants with operating a ticket-fixing scheme\nin the Philadelphia Traffic Court, the District Court denied a\nmotion, under Federal Rule of Criminal Procedure\n12(b)(3)(B)(v), to dismiss charges of conspiracy (18 U.S.C. §\n1349), mail fraud (18 U.S.C. § 1341), and wire fraud (18\nU.S.C. § 1343). Appellants Henry Alfano (private citizen)\nand William Hird (Traffic Court administrator) subsequently\npleaded guilty to all counts against them. But now they\nappeal the District Court’s decision on this motion,\nquestioning whether the indictment properly alleged offenses\nof mail fraud and wire fraud. 1\n\n Appellants Michael Lowry, Robert Mulgrew, and\nThomasine Tynes (Traffic Court judges) proceeded to a joint\ntrial and were acquitted on the fraud and conspiracy counts,\nbut they were convicted of perjury for statements they made\nbefore the Grand Jury. Lowry, Mulgrew, and Tynes dispute\nthe sufficiency of the evidence on which they were convicted\nby arguing that the prosecutor’s questions were vague, and\nthat their answers were literally true. Lowry and Mulgrew\ncontend alternatively that the jury was prejudiced by evidence\npresented at trial on the fraud and conspiracy counts.\nMulgrew also complains that the District Court erred by\nruling that certain evidence was inadmissible.\n\n At the same trial, the jury convicted Willie Singletary\n(Traffic Court judge) of making false statements during the\ninvestigation. He claims the District Court made errors when\n\n\n1\n Alfano and Hird preserved their right to appeal. See infra\nsubsection I.C.\n\n\n\n\n 5\n\fit sentenced him. 2 The Government concurs with\nSingletary’s challenge to his sentence.\n\n We have consolidated these appeals for efficiency and\nhave grouped the arguments—to the extent that it is\npossible—by common issues. We agree with Singletary and\nthe Government that he should be resentenced. We will\nreverse the judgment and remand his cause to the District\nCourt for this purpose. We are not persuaded by the rest of\nAppellants’ arguments and will affirm their judgments of\nconviction. 3\n\n II.\n\n Appellants Alfano 4 and Hird 5\n\n\n\n2\n Singletary also attempted to join additional arguments raised\nby other appellants, but for reasons we explain later, see infra\nnote 33, we focus only on his challenge to his sentence.\n3\n The District Court had jurisdiction pursuant to 18 U.S.C. §\n3231. We have jurisdiction to review these claims under 28\nU.S.C.§ 1291 and 18 U.S.C. § 3742(a).\n4\n Appellant Alfano pleaded guilty to Conspiracy (Count 1),\nWire Fraud (Counts 2, 3, 4, 5, 6, 7) and Mail Fraud (Counts\n51, 52, 53, 54, 55, 56).\n5\n Appellant Hird pleaded guilty to Conspiracy (Count 1),\nWire Fraud (Counts 3, 4, 5, 6, 16, 17, 18, 19, 20, 22, 23) and\nMail Fraud (Counts 58, 59, 60).\n\n\n\n\n 6\n\f A.\n\n We begin with a brief look at the indictment’s\ndescription of the Traffic Court and its operations to\ncontextualize the arguments made by Alfano and Hird. The\nPhiladelphia Traffic Court was part of the First Judicial\nDistrict of Pennsylvania. App. 186 (Indictment ¶ 2). 6 It\nadjudicated violations of the Pennsylvania Motor Vehicle\nCode occurring in the City of Philadelphia, no matter whether\nthe Philadelphia Police or the Pennsylvania State Police\nissued the tickets. App. 187 (Indictment ¶5). When a person\nwas cited for a violation he or she was required—within ten\ndays—to enter a plea of guilty or not guilty. If the person\nfailed to plead, the Traffic Court issued a notice that his or her\nlicense was being suspended. App. 189 (Indictment ¶ 12). A\nperson who pleaded not guilty proceeded to a hearing with a\nTraffic Court judge presiding. App. 187 (Indictment ¶ 6).\n\n A guilty plea, or a determination of guilt by a Traffic\nCourt judge after a hearing, resulted in a judgment ordering\npayment of statutory fines and court costs. App. 188\n(Indictment ¶ 8). 7 The Traffic Court was responsible for\ncollecting these fines (sending them to the City and\n\n\n6\n Philadelphia Traffic Court was abolished and its jurisdiction\nwas transferred to the Municipal Court in 2013 by an Act of\nthe Pennsylvania General Assembly. 42 Pa.Con.Stat.\n§1121(a)(2) (2013). The court is now known as the Traffic\nDivision of the Municipal Court.\n7\n Although other penalties are prescribed by the Pennsylvania\nMotor Vehicle Code (App. 188), this appeal is limited to the\nmonetary fines and costs. App. 355.\n\n\n\n\n 7\n\fCommonwealth) and costs (which it distributed to several\npre-designated funds). App. 188-89 (Indictment ¶ 9).\nFinally, it reported the disposition of each adjudication to the\nPennsylvania Department of Transportation (PennDOT).\nApp. 189 (Indictment ¶ 11).\n\n B.\n\n The indictment charged that, at the behest of Alfano\n(App. 193 (Indictment ¶ 25)) and others, the Traffic Court\nadministrator and judges operated an “extra-judicial system,\nnot sanctioned by the Pennsylvania court system” that\nignored court procedure and gave preferential treatment\n(“consideration”) to select individuals with connections to the\ncourt who had been cited for motor vehicle violations. App.\n196 (Indictment ¶ 31). The special treatment included:\n\n (1) dismissing tickets outright; (2)\n finding the ticketholder not guilty\n after a “show” hearing; (3)\n adjudicating the ticket in a\n manner to reduce fines and avoid\n assignment of points to a driver’s\n record; and (4) obtaining\n continuances of trial dates to\n “judge-shop,” that is find a Traffic\n Court judge who would accede to\n a request for preferential\n treatment.\n\nApp. 195-196 (Indictment ¶ 30). All of this was “not\navailable to the rest of the citizenry.” App. 196 (Indictment ¶\n32). It also alleged that Appellants cooperated with each\n\n\n\n\n 8\n\fother to fulfill requests they and their staffs received. App.\n194-95 (Indictment ¶ 27). Finally, it charged that “[i]n\nacceding to requests for ‘consideration,’ defendants were\ndepriving the City of Philadelphia and the Commonwealth of\nPennsylvania of money which would have been properly due\nas fines and costs.” App. 197 (Indictment ¶ 38). 8\n After extending consideration to favored individuals,\nTraffic Court judges would report the final adjudication to\n“various authorities, including PennDOT, as if there had been\na fair and open review of the circumstances.” App. 197\n(Indictment ¶ 34). Appellant Hird provided a printout to\nAppellant Alfano showing citations that had been “dismissed\nor otherwise disposed of.” App. 198-99 (Indictment ¶ 42).\nSuch “receipts” were not routinely issued in cases.\n\n C.\n\n Hird and Alfano pleaded guilty to all the charges\nagainst them in the indictment. But, in their plea agreement\nthey reserved the right to appeal “whether the Indictment\n\n\n8\n An example of the many allegations involving Alfano and\nHird is: A.S. requested assistance from Appellant Alfano and\nAppellant Hird on Citation Number P1J0PK568L4 on or\naround February 17, 2010. The citation charged A.S. with\ndriving a tractor-trailer from which snow and ice fell, striking\nvehicles on Interstate 95. The violation carried a $300 fine\nand costs of $142. Appellant Hird promised that he would\n“stop all action” on the citation and instructed A.S. to ignore\nthe ticket. Although A.S. did not appear at the hearing, the\nTraffic Court judge (who is not an appellant here) ruled A.S.\nnot guilty. App. 210-12 (Indictment ¶¶ 25-34).\n\n\n\n\n 9\n\fsufficiently alleged that the defendants engaged in a scheme\nto defraud the Commonwealth of Pennsylvania and the City\nof Philadelphia of money in costs and fees.” App. 355 (Plea\nAgreement ¶ 9(b)(4)). So they now appeal the District\nCourt’s order denying the motion to dismiss, asserting that\nthe indictment failed to allege violations of mail fraud and\nwire fraud.\n\n “To be sufficient, an indictment must allege that the\ndefendant performed acts which, if proven, constitute a\nviolation of the law that he is charged with violating.” United\nStates v. Small, 793 F.3d 350, 352 (3d Cir. 2015). We\nassume in our review that the allegations in the indictment are\ntrue. United States v. Hedaithy, 392 F.3d 580, 583 (3d Cir.\n2004). “The question of whether the . . . indictments alleged\nfacts that are within the ambit of the mail fraud statute is a\nquestion of statutory interpretation subject to plenary review.”\nId. at 590 n.10.\n\n To indict on mail or wire fraud, the Government must\nallege that defendants “devised or intend[ed] to devise any\nscheme or artifice to defraud, or for obtaining money or\nproperty by means of false or fraudulent pretenses,\nrepresentations, or promises” and used mail or wire to effect\nthe scheme. 18 U.S.C. §§ 1341, 1343. Alfano and Hird claim\nthe Government failed to allege that the scheme to commit\nwire and mail fraud had an objective of “obtaining money or\nproperty.” 9\n\n9\n In the context of mail fraud (§ 1341) and wire fraud (§1343)\nthe term “money” has the same meaning. The same is true\nfor the term “property.” Carpenter v. United States, 484 U.S.\n19, 25 n. 6 (1987).\n\n\n\n\n 10\n\f The District Court ruled that the indictment\nsufficiently alleged that the scheme “involved defrauding the\nCommonwealth and the City of money.” App. 20. It noted,\namong others, allegations that:\n\n The conspirators used the\n Philadelphia Traffic Court\n (“Traffic Court”) to give\n preferential treatment to certain\n ticketholders, most commonly by\n “fixing” tickets for those with\n whom they were politically and\n socially connected. By doing so,\n the conspirators defrauded the\n Commonwealth of Pennsylvania\n and the City of Philadelphia of\n funds to which the\n Commonwealth and the City were\n entitled.\n\nId. at 18; see also id. at 185 (Indictment ¶ 1). Similarly, it\nreferred to the following.\n\n In acceding to requests for\n “consideration,” defendants were\n depriving the City of Philadelphia\n and the Commonwealth of\n Pennsylvania of money which\n would have been properly due as\n fines and costs.\n\n\n\n\n 11\n\fId. at 9; see also id. at 197 (quoting Indictment ¶ 38).\nHighlighting the references to “funds” and “money,” and that\nthe monetary amounts of the fines are specifically pleaded,\nthe District Court cited to a case from the Court of Appeals\nfor the Eighth Circuit which concluded succinctly that\n“[m]oney is money.” United States v. Sullivan, No. 2:13-cr-\n00039, 2013 WL 3305217, at *7 (E.D. Pa. July 1, 2013)\n(quoting United States v. Granberry, 908 F.2d 278, 280 (8th\nCir. 1990)). The District Court was satisfied that the\nindictment alleged enough.\n\n “Money, of course, is a form of property.” Reiter v.\nSonotone Corp., 442 U.S. 330, 338 (1979). But Alfano and\nHird argue that the mere mention of money in an indictment\nis not enough. They point to a string of Supreme Court and\nCourt of Appeals decisions analyzing Section 1341 and\nSection 1343 which reinforce the point that crimes of mail\nfraud and wire fraud are “limited in scope to the protection of\nproperty rights.” McNally v. United States, 483 U.S. 350, 360\n(1987). 10 The Supreme Court said that “[a]ny benefit which\nthe government derives from the [mail fraud] statute must be\nlimited to the Government’s interests as a property holder.”\nId. at 359 n.8 (emphasis added). Appellants are convinced\nthat money in the form of traffic fines and costs cannot be\nregarded as the Government’s “property” for purposes of mail\nor wire fraud, and they identify two decisions as particularly\nsupportive of their position: Cleveland v. United States, 531\n\n10\n The District Court cited to a number of cases that came\nafter McNally: Carpenter v. United States, 484 U.S. 19\n(1987); Cleveland v. United States, 531 U.S. 12 (2000);\nPasquantino v. United States, 544 U.S. 349 (2005).\n\n\n\n\n 12\n\fU.S. 12 (2000); and United States v. Henry¸ 29 F.3d 112 (3d\nCir. 1994).\n\n The Court in Cleveland examined the mail fraud\nconvictions of individuals who received a state video poker\nlicense by submitting a license application that withheld\nimportant information. Cleveland, 531 U.S. 12. 11 The Court\nnoted that the video poker licenses were part of a state\nprogram that was “purely regulatory.” Id. at 22 (citation\nomitted). 12 It ruled that licenses are a “paradigmatic\nexercise[] of the States’ traditional police powers.” Id. at 23.\nThe Court went on to say that the state’s regulatory powers\ninvolving “intangible rights of allocation, exclusion, and\ncontrol” (which are embodied in a license) are not interests\nthat traditionally have been recognized as property. Id.\nTherefore, even though appellants may have obtained the\nlicense through deception, this was not mail fraud because the\nlicense—at least while still in the hands of the state—was not\n\n\n\n11\n The licenses were part of a regulatory scheme that had as\nits purpose to increase public confidence in the honesty of\ngaming activities that are free of criminal involvement.\nCleveland, 531 U.S. at 20–21 (quoting La. Rev. Stat. Ann. §\n27:306(A)(1) (2000) (repealed 2012)).\n12\n The Court rebuffed the Government’s attempts to analogize\nlicenses to other forms of property like patents and franchise\nrights. As for likening licenses to franchise rights, the Court\nobserved that the Government did not enter the video poker\nbusiness, but rather decided to “permit, regulate, and tax\nprivate operators of the games.” Id. at 24.\n\n\n\n\n 13\n\fproperty. Id. at 26-27. It was a purely administrative tool\nused to achieve regulatory objectives. Id. at 21.\n\n The state responded to the Court’s concerns by\nagreeing that the licenses served a regulatory purpose, but it\ndirected attention to the revenue it received from fees\ncollected for license applications and renewals, as well as\ndevice fees. Id. at 21-22. It argued that this revenue is a\nproperty interest. Id. The Court was not convinced:\n\n Tellingly, as to the character of\n Louisiana’s stake in its video\n poker licenses, the Government\n nowhere alleges that Cleveland\n defrauded the State of any money\n to which the State was entitled by\n law. Indeed, there is no dispute\n that TSG paid the State of\n Louisiana its proper share of\n revenue, which totaled more than\n $1.2 million, between 1993 and\n 1995. If Cleveland defrauded the\n State of “property,” the nature of\n that property cannot be economic.\n\nId. at 22 (emphasis added). It concluded that “[e]ven when\ntied to an expected stream of revenue, the State’s right of\ncontrol does not create a property interest any more than a\nlaw licensing liquor sales in a State that levies a sales tax on\n\n\n\n\n 14\n\fliquor.” Id. at 23. 13 The money collected from application\nand processing fees was an integral part of the state\nregulatory program and it did not create any property interest.\nSee id.\n\n The purpose of the Pennsylvania Motor Vehicle Code\nis to “promote the safety of persons and property within the\nstate.” Mauer v. Boardman, 7 A.2d 466, 472 (Pa. 1939).\nMoreover, issuing traffic tickets is a crucial element in the\nenforcement of the Motor Vehicle Code: it is a quintessential\nexercise of state police power. Alfano and Hird conclude,\nmuch like Cleveland, that no property interest could arise\nfrom revenue generated from the state’s exercise of its police\npower in the form of a traffic-ticket fine. They see nothing\nbut a regulatory program here. But this ignores crucial\naspects of the case before us that make it different.\n\n Simply stated, fees charged to obtain a license cannot\nbe equated with fines and costs that result from a traffic\nticket. The license fee was imposed, adjusted, and collected\nsolely by the state’s exercise of its regulatory authority. In\ncontrast, here the state’s police power is exercised when a\ncitation is issued, but this ticket merely establishes the\nsummary violation with which the person is charged. Once a\nperson has been charged, it is judicial power (not the state’s\npolice power) that is exercised to determine whether the\n\n\n\n\n13\n Cleveland also held that Government-issued licenses have\nno intrinsic economic worth before they are given to\napplicants. Id. at 23.\n\n\n\n\n 15\n\fperson is guilty and, if guilty, to impose the fine and costs. 14\nThese fines and costs, although specified by the Motor\nVehicle Code, cannot be cabined as a product of the state’s\nregulatory authority. They are part and parcel of the\njudgment of the court. With this in mind, it is significant that\nthe indictment does not focus on how the citations were\nissued (which would implicate police power), but rather\nalleges that the judicial process was rigged to produce only\njudgments that imposed lower fines—or most often—no fines\nand costs at all. 15\n\n But this raises a further question: can a criminal\njudgment held by the government ever be “property?” The\nCourt in Cleveland offered a critique in its analysis of a\n\n14\n The Traffic Court was not an administrative tribunal.\nRather, it was part of the First Judicial District of\nPennsylvania. App. 186 (Indictment ¶ 2). See also supra\nnote 6 and accompanying text.\n15\n On this point, it is noteworthy that the Supreme Court also\nsaid the following: “We resist . . . [any invitation] to approve\na sweeping expansion of federal criminal jurisdiction in the\nabsence of a clear statement by Congress. . . . ‘[U]nless\nCongress conveys its purpose clearly, it will not be deemed to\nhave significantly changed the federal-state balance’ in the\nprosecution of crimes.” Cleveland, 531 U.S. at 24-25\n(quoting Jones v. United States, 529 U.S. 848, 858 (2000)).\nAs we discuss later, the legal tradition of understanding\njudgments as property is long-established. Consequently, the\nconcern about expanding the reach of federal fraud statutes to\nnew classes of property that was present in the deliberation of\nstate licenses in Cleveland is not at issue here.\n\n\n\n\n 16\n\fdifferent issue (whether licenses were analogous to patents)\nthat is apropos to answering this question.\n\n [W]hile a patent holder may sell\n her patent, see 35 U.S.C. § 261 . .\n . “patents shall have the attributes\n of personal property” . . . the State\n may not sell its licensing\n authority. Instead of a patent\n holder’s interest in an unlicensed\n patent, the better analogy is to the\n Federal Government’s interest in\n an unissued patent. That interest,\n like the State’s interest in\n licensing video poker operations,\n surely implicates the\n Government’s role as sovereign,\n not as property holder.\n\nCleveland, 531 U.S. at 23–24. Fines imposed by judges are\ncriminal penalties that “implicate[] the Government’s role as\nsovereign.” Id. at 24. Judgments ordering traffic fines and\ncosts cannot be sold and, in the logic of Cleveland, would\nseem then to have no intrinsic economic value. Indeed, the\npenal (non-economic) nature of the fine is undeniable because\nthe failure to pay a fine can result in the imposition of\nsentences of greater consequence, including imprisonment.\nSee Pa. R. Crim. P. 706 cmt. But Cleveland is not the last\nword. As we will discuss below, a Supreme Court opinion\nissued five years later, Pasquantino v. United States, 544 U.S.\n349 (2005), forecloses the defendants’ argument.\n\n\n\n\n 17\n\f Finally, we note a dissimilarity between this case and\nCleveland, highlighted by the District Court, on the\nsignificance of the monetary interest that the Government\nassociates with the fraud. The Cleveland Court regarded the\nlicensing fees as integral to the regulatory effort and collateral\nto the matter at hand. The indictment there centered on the\nscheme to obtain liceneses, and did not even raise the\nlicensing fees. See Cleveland, 531 U.S. at 22. Indeed, those\ncharged with the fraud paid all the appropriate fees; there was\nno evidence that the government suffered any economic\ndetriment. Id.\n\n In contrast, the indictment here explicitly states that\nthe scheme deprived the City and the Commonwealth of\nmoney, and it describes the object of the scheme as obviating\njudgments of guilt that imposed the fines and costs. Unlike\nCleveland, the fines and costs play a central role in the\nscheme as alleged.\n\n Alfano and Hird next focus on our decision in Henry\nto argue that the Government cannot claim to have a property\nright because the Government never had a legal claim to the\nfines and costs at any point in the scheme. In Henry, we\nexamined convictions for wire fraud arising from a\ncompetitive bidding process among banks to receive deposits\nof a public agency’s bridge tolls. Henry v. United States, 29\nF.3d 112 (3d Cir. 1994). Appellants—public employees—\nwere convicted of mail fraud for giving one bank confidential\ninformation about bids from other banks. Id. at 113. We\nidentified several problems, 16 but Alfano and Hird highlight\n\n16\n The Supreme Court had already made clear that “a\ngovernment official’s breach of his or her obligations to the\n\n\n\n\n 18\n\four observation in Henry that the object of the mail and wire\nfraud must be something to which the victim could claim a\nright of entitlement. Id. at 115 (“a grant of a right of\nexclusion”) (citing Carpenter, 484 U.S. at 26-27)). 17 Indeed,\nwe noted that a bank’s property right to the tolls would attach\nonly after the funds were deposited. Id. at 114. So the banks\nthat lost the bidding process never had a basis to claim any\nlegally recognized entitlement to the toll deposits. 18 Id. at\n115. A fraud claim cannot rest on the bidders being cheated\nout of an opportunity to receive the deposits. For these\nreasons, we concluded that the indictment did not allege a\nscheme to obtain fraudulently someone’s “property.” Id. at\n116.\n\n Here, the Government alleged that the defendants\n“were depriving . . . Philadelphia and . . . Pennsylvania of\nmoney which would have been properly due as fines and\ncosts” by making it possible for certain well-connected\nindividuals to avoid a judgment of guilt that imposed an\nobligation to pay appropriate statutory fines. App. 197\n\n\npublic or an employee’s breach of his or her obligations to an\nemployer” did not fall within the scope of Section 1343.\nHenry, 29 F.3d at 114 (citing Carpenter, 484 U.S. at 25).\n17\n To assess whether a particular claim is a legal entitlement,\n“we look to whether the law traditionally has recognized and\nenforced [the entitlement] as a property right.” Henry, 29\nF.3d at 115.\n18\n They were, no doubt, robbed of a fair process, but we could\nnot identify any legal tradition that recognized this\ndeprivation as a property right. Id. at 115.\n\n\n\n\n 19\n\f(Indictment ¶ 38). But Appellants stress that, like the\ndeposits in Henry, the indictment here alleged an entitlement\nthat does not yet exist because a person must be adjudicated\n(or plead) guilty before they must pay any fines or costs.\nNone of the cases directly associated with Alfano and Hird\nresulted in a guilty judgment. As a result, they argue, the\nGovernment cannot claim here that it was cheated of an\nentitlement, because they were only fines and costs that the\npeople might have owed if they had been found guilty.\n\n The District Court said it well. Accepting this\nargument “would permit the alleged conspirators” to take\nadvantage of their “unique position” in this case “to enter into\na scheme to commit fraud and then hide behind the argument\nthat the success of their fraud precludes prosecution under the\n‘money or property interest’ requirement of the mail and wire\nfraud statutes.” Sullivan, 2013 WL 3305217, at *7.\nAppellants cannot rest on the very object of their scheme (to\nwork on behalf of favored individuals to obviate judgments of\nguilt and the imposition of fines and costs) as the basis to\nclaim that there is no fraud. Indeed, the not-guilty judgments\nthat Alfano and Hird worked to obtain through the\nextrajudicial system were alleged in the indictment as\nevidence of the scheme itself.\n\n Even if some of the cases in the extra-judicial system\nwould have been judged not guilty in a real adjudication it is\n(as the District Court correctly noted) the intent of the\nscheme, not the successful execution of it, that is the basis for\ncriminal liability. See Neder v. United States, 527 U.S. 1, 25\n(1999) (In the criminal context, the court focuses on the\nobjective of the scheme rather than its actual outcome; what\noperatives intended to do, not whether they were successful in\n\n\n\n\n 20\n\fdoing it.); United States v. Rowe, 56 F.2d 747, 749 (2d Cir.)\n(“Civilly of course the [mail fraud statute]would fail without\nproof of damage, but that has no application to criminal\nliability.”), cert. denied 286 U.S. 554 (1932). The indictment\ngenerally alleges not just that Appellants operated a system\nthat operated outside the bounds of Traffic Court procedures,\nbut that it did so for the purpose of obviating judgments of\nguilt imposing fines and costs in those selected cases. See,\ne.g., supra note 8. Moreover, we note that in one case not\ndirectly involving either Alfano or Hird, the indictment\nalleged that fines and costs were not just obviated, but were\nactually erased by an alleged co-conspirator traffic court\njudge who ignored the conviction, backdated a continuance,\nand “adjudicated” the person not-guilty. App. 228-29\n(Indictment ¶¶ 108-113). This episode serves to highlight\nthat the entire scheme was centered on keeping (or taking)\njudgments out of the hands of the Government to prevent the\nimposition of fines and costs. As a result, Appellants’\nreliance on our justice system’s presumption of innocence as\na basis to argue against the existence of a governmental\nproperty interest is a red herring that is properly disregarded\nhere.\n\n Accordingly, we conclude that the indictment’s\nallegation that the scheme had an objective of depriving\n“Philadelphia and . . . Pennsylvania of money which would\nhave been properly due as fines and costs” is not undermined\nby the lack of guilty verdicts. App. 197 (Indictment ¶38\n(emphasis added)).\n\n Alfano and Hird next highlight that, in Henry, our\nproperty interest analysis centered on “whether the law\ntraditionally has recognized and enforced [the entitlement in\n\n\n\n\n 21\n\fquestion] as a property right.” 29 F.3d at 115. Appellants\nassert that traffic fines and costs typically have not been\nconsidered economic property and are unsupported by any\nlegal tradition sufficient to ground charges of wire and mail\nfraud. As we have already noted we disagree with any\nconclusion that the fines and costs at issue have no intrinsic\neconomic value. But we turn to another decision of the\nSupreme Court that came after Cleveland to address squarely\nwhether jurisprudence supports our conclusion.\n\n In 2005 the Supreme Court reviewed convictions\narising from a scheme to smuggle large quantities of liquor\nfrom the United States into Canada, evading Canadian taxes.\nSee Pasquantino v. United States, 544 U.S. 349, 353 (2005).\nThe Court noted that the right to be paid has been routinely\nrecognized as property, id. at 355–56, 19 observing that there is\nan equivalence between “money in hand and money legally\ndue,” id. at 356. Affirming the conviction, the Court said:\n“Had petitioners complied with this legal obligation, they\nwould have paid money to Canada. Petitioners’ tax evasion\ndeprived Canada of that money, inflicting an economic injury\nno less than had they embezzled funds from the Canadian\ntreasury.” Id. It concluded that: “[t]he object of petitioners’\nscheme was to deprive Canada of money legally due, and\ntheir scheme thereby had as its object the deprivation of\nCanada’s ‘property.’” Id. Under Pasquantino, then, traffic\ntickets (or more precisely, judgments arising from them) are\nconsidered an “entitlement to collect money from individuals,\n\n\n19\n The Court cited 3 W. Blackstone, Commentaries on the\nLaws of England 153–155 (1768), which classified the right\nto sue on a debt as personal property.\n\n\n\n\n 22\n\fthe possession of which is ‘something of value.’” 544 U.S. at\n355 (quoting McNally, 483 U.S. at 358). 20 We conclude that\na scheme to obviate judgments imposing fines, effectively\npreventing the government from holding and collecting on\nsuch judgments imposes an economic injury that is the\nequivalent of unlawfully taking money from fines paid out of\nthe Government’s accounts. See id. at 358.\n\n Alfano and Hird focus, finally, on the role that a\njudge’s discretion plays in the adjudication of a case,\nasserting that the uncertainty this creates about outcomes in\nany given case undermines any argument that a judgment in a\nTraffic Court case can be claimed as an entitlement to\nproperty. To the extent that this merely rephrases the issue of\nguilt or innocence on particular charges, we have already\n\n20\n We also note that Pennsylvania law permits the government\nto remedy the nonpayment of fines and costs as an unpaid\ndebt through civil process, enabling the government to\nbecome a judgment creditor. Pa. R. Crim. P. 706 cmt.\n(“Nothing in this rule [concerning criminal fines] is intended\nto abridge any rights the Commonwealth may have in a civil\nproceeding to collect a fine or costs.”). Because of this, a\nseparate legal tradition is implicated that recognizes the\njudgment itself as property. See, e.g., Armada (Singapore)\nPTE Ltd. v. Amcol International Corp., 885 F.3d 1090, 1094\n(7th Cir. 2018). This long, stable legal tradition of\nrecognizing civil judgments for money as property supports\nthe conclusion that the fines arising from judgments in traffic\ncourt cannot be regarded merely as implicating the act of a\nsovereign imposing a criminal penalty. They can be collected\nby civil process as a debt and are, thus, a property interest.\n\n\n\n\n 23\n\faddressed it above. To the degree that it refers to a judge’s\ndiscretion in sentencing, as the District Court noted, there is\nno such discretion here. 21 The Motor Vehicle Code imposes\nfines and costs for each violation, eliminating any judicial\ndiscretion in this regard.\n\n D.\n\n All of this leads us to conclude that the District Court\ndid not err by denying the motion to dismiss. We conclude\nthat, as alleged, this scheme had the objective of preventing\nthe City of Philadelphia and the Commonwealth of\nPennsylvania from possessing a lawful entitlement to collect\nmoney in the form of fines and costs—a property interest—\nfrom individuals who Alfano and Hird assisted. We will thus\naffirm the convictions of Appellants Alfano and Hird.\n\n III.\n\n Appellants Tynes, Lowry, and Mulgrew\n\n A.\n\n\n\n\n21\n We question, in general, the relevance of an entity’s\nauthority to relinquish a just entitlement or to forbear an\nobligation that an entitlement imposes upon another, as a\nbasis to call into doubt the legitimacy of, or the very existence\nof the entitlement. But see United States v. Mariani, 90 F.\nSupp. 2d 574, 583 (M.D. Pa. 2000) (Discretionary civil fines\nand penalties “may be too speculative to constitute a valid\nproperty interest.”) (internal citation omitted).\n\n\n\n\n 24\n\f In 2011, the United States Attorney presented to the\nGrand Jury evidence arising from the Federal Bureau of\nInvestigation’s inquiry into the Traffic Court. Appellants\nLowry, Mulgrew, and Tynes testified and the Government\nbrought perjury charges against them for statements they\nmade to the Grand Jury. After Hird and Alfano pleaded\nguilty, the rest of the Appellants went to trial. The jury\nacquitted Lowry, Mulgrew, and Tynes of all counts against\nthem on wire fraud, mail fraud, and conspiracy. But it found\nthem guilty of perjury. Tynes, Lowry, and Mulgrew\nchallenge their convictions by raising similar legal arguments\nabout the sufficiency of the evidence.\n As with all challenges to the sufficiency of the\nevidence, we use a highly deferential standard of review. See\nUnited States v. Caraballo-Rodriguez, 726 F.3d 418, 430 (3d\nCir. 2013) (en banc). We examine the record in a light most\nfavorable to the prosecution, and will not disturb the verdict if\n“any rational trier of fact could have found the essential\nelements of the crime beyond a reasonable doubt.” United\nStates v. McGee, 763 F.3d 304, 316 (3d Cir. 2014) (emphasis\nin original) (quoting Jackson v. Virginia, 443 U.S. 307, 319\n(1979)). Tynes, Lowry, and Mulgrew argue that the\nquestions asked of them at trial were fatally vague and/or that\ntheir answers were truthful. As a result, they contend that\nthese questions and answers are an inadequate basis for a\nperjury conviction.\n\n A conviction for perjury before a grand jury requires\nthe Government to prove that the defendant took an oath\nbefore the grand jury and then knowingly made a “false\nmaterial declaration.” 18 U.S.C. § 1623. But we recognized\n(in the context of a sentencing enhancement for perjury) that\nsometimes “confusion, mistake, or faulty memory” results in\n\n\n\n\n 25\n\finaccuracies that cannot be categorized as a “willful attempt\nto obstruct justice” under perjury statutes. United States v.\nMiller, 527 F.3d 54, 75 (3d Cir. 2008) (quoting U.S.\nSentencing Guidelines Manual § 3C1.1 cmt. n.2 (U.S.\nSentencing Comm’n 2003). So we do understand that\n“[p]recise questioning is imperative as a predicate for the\noffense of perjury.” Bronston v. United States, 409 U.S. 352,\n362 (1973).\n\n Precision, however, is assessed in context. An\nexaminer’s line of questioning should, at a minimum,\nestablish the factual basis grounding an accusation that an\nanswer to a particular question is false. Miller, 527 F.3d at\n78. So a perjury conviction is supported by the record “when\nthe defendant’s testimony ‘can reasonably be inferred to be\nknowingly untruthful and intentionally misleading, even\nthough the specific question to which the response is given\nmay itself be imprecise.’” United States v. Serafini, 167 F.3d\n812, 823 (3d Cir. 1999) (quoting United States v. DeZarn,\n157 F.3d 1042, 1043 (6th Cir. 1998)).\n\n Challenges to the clarity of a question are typically left\nto the jury, which has the responsibility of determining\nwhether the defendant understood the question to be\nconfusing or subject to many interpretations. United States v.\nSlawik, 548 F.2d 75, 86 (3d Cir. 1977). Moreover, consistent\nwith our standard of review, we will not disturb a jury’s\ndetermination that a response under oath constitutes perjury\nunless “it is ‘entirely unreasonable to expect that the\ndefendant understood the question posed to him.’” Serafini,\n167 F.3d at 820 (quoting United States v. Ryan, 828 F.2d\n1010, 1015 (3d Cir. 1987), abrogated on other grounds by\n\n\n\n\n 26\n\fUnited States v. Wells, 519 U.S. 482 (1997)). 22 On appeal,\nwe review every aspect of the record pertinent to both the\nquestion and answer to reach a conclusion about whether, in\ncontext, the witness understood the question well enough to\ngive an answer that he or she knew to be false. See Miller,\n527 F.3d at 78. Our review, however, is focused on glaring\ninstances of vagueness or double-speak by the examiner at the\ntime of questioning (rather than artful post-hoc interpretations\nof the questions) that—by the lights of any reasonable fact-\nfinder—would mislead or confuse a witness into making a\nresponse that later becomes the basis of a perjury conviction.\nQuestions that breach this threshold are “fundamentally\nambiguous” and cannot legitimately ground a perjury\nconviction. Id. at 77. 23\n\n\n22\n The Court of Appeals for the Second Circuit underscored\nthe high bar this establishes for appellants by noting that a\nfundamentally ambiguous question is “not a phrase with a\nmeaning about which men of ordinary intellect could agree,\nnor one which could be used with mutual understanding by a\nquestioner and answerer unless it were defined at the time it\nwere sought and offered as testimony.” United States v.\nLighte, 782 F.2d 367, 375 (2d Cir. 1986) (quoting United\nStates v. Lattimore, 127 F. Supp. 405, 410 (D. D.C.), aff’d,\n232 F.2d. 334 (D.C. Cir. 1955)).\n23\n The rule of fundamental ambiguity is intended to\n“preclude convictions that are grounded on little more than\nsurmise or conjecture, and . . . prevent witnesses . . . from\nunfairly bearing the risks associated with the inadequacies of\ntheir examiners.” Ryan, 828 F.2d at 1015.\n\n\n\n\n 27\n\f That is the law applicable to the claims raised by\nTynes, Lowry and Mulgrew. But, because our review is fact-\ndependent, and because each raises some unique issues, we\nwill address each of their claims individually. 24\n B.\n\n\n\n\n24\n Adopting the arguments made by Alfano and Hird,\nAppellants Lowry, Mulgrew and Tynes assert that the\nGovernment improperly charged them with conspiracy, wire\nfraud, and mail fraud. Therefore, they assert, their joint trial\non these counts of the indictment prejudiced the jury’s\ndeliberation on the charges of perjury. They claim such\nevidence would have been excluded under Federal Rule of\nEvidence. 403. They also contend that, without a charge of\nconspiracy, the joinder of their cases would have been\nimpermissible under Federal Rule of Criminal Evidence 8(b)\nor, at the very least, severance of their cases would have been\nwarranted under Federal Rule of Criminal Procedure 14(a).\nCertainly, where there is evidence of prejudice resulting from\n“spillover” evidence from counts that should have been\ndismissed, reversal is warranted. See United States v. Wright,\n665 F.3d 560, 575-577 (3d Cir. 2012). But we have\nconcluded that the District Court did not err by denying the\nmotion, under Federal Rule of Civil Procedure 12(b)(3), to\ndismiss the conspiracy, wire fraud and mail fraud counts of\nthe indictment. Thus, Appellants’ spillover argument has\nbeen nullified. Likewise, Appellants have no basis to claim\nthat the Court unfairly prejudiced them by not granting\nseparate trials.\n\n\n\n\n 28\n\f Appellant Tynes 25\n\n Appellant Tynes claims her convictions for perjury at\nCount 71 and Count 72 lack sufficient evidence because she\nwas responding to questions that were fundamentally\nambiguous. The perjury charged at Count 71 arises from the\nfollowing exchange.\n\n Q. In all the years\n you’ve been [at Traffic\n Court] have you\n ever been asked to give\n\n\n25\n Tynes filed a separate motion to dismiss. App. 291-99.\nThe record also contains Tynes’ proposed order to join\nSullivan’s motion to dismiss. App. 290. However, Tynes’\nmotion contains no such request. Moreover, the\nGovernment’s response to the motions notes that Lowry and\nMulgrew moved to join (without argument), and makes no\nmention of Tynes. The District Court’s ruling on Tynes’\nmotion to dismiss relates only to the arguments she made\nseparately in her brief. As a result, we cannot consider\nTynes’ arguments on appeal that relate to those raised in\nSullivan’s motion. Moreover, since she failed to raise any of\nthe arguments she made in her separate motion to dismiss,\nthese arguments are waived. With that said, we will affirm\nthe District Court’s ruling on the Motion raised by Sullivan\nand joined by the five Appellants. Therefore, we need not\naddress Tynes’ assertion that the District Court’s mishandled\nher joinder motion because it does not prejudice the outcome\nof her appeal.\n\n\n\n\n 29\n\f favorable treatment on\n a case to anybody?\n\n A. No, not favorable\n treatment. People basically\n know me. The lawyers\n know me. The court\n officers know me. I have\n been called a nononsense\n person because I’m just not\n that way. I take my\n position seriously, and the\n cards fall where they may.\n\nApp. 255, 5720. 26 Tynes contends that the Government\npursued a novel theory here (applying federal fraud statutes to\nallegations of ticket fixing) and used the vague term\n“favorable treatment” to gloss over its uncertainty about what,\nultimately, would constitute an illegal act. She points out that\nthe term had not been used before in reference to this case\nand that the Government offered no explanation or definition\nof the term to alert Tynes to the intent of the question.\n\n Also, from Tynes’ perspective, every litigant\nappearing before a court seeks an outcome that is favorable,\nthus making “favorable treatment” a term that essentially\nreferred to “how litigation works.” She claims that its use\namounted to a fishing expedition designed to capture unfairly\n\n26\n We cite to the testimony quoted in the indictment and the\nGrand Jury that was used at trial. We note that there are some\ntypographical inconsistencies between these sources and in\nthose instances we have quoted the Grand Jury testimony.\n\n\n\n\n 30\n\fthe entirety of her conduct in the courtroom. She warns that\nthis is precisely the type of “open-ended construction” in\nquestioning that we found unacceptable in Serafini. 167 F.3d\nat 822.\n\n Tynes makes a related argument against her perjury\nconviction for Count 72. That conviction is based on this\nexchange.\n Q. You’ve never taken\n action on a request?\n\n A. No.\n\nApp. 257, 5722. She maintains that the word “request” was\npresented to the jury as a follow-on to the question grounding\nCount 71, requiring a person to link the term “favorable\ntreatment” and the word “request” to make sense of it. She\nargues that the Government took advantage of the ambiguity\nof “favorable treatment,” forcing the jury to speculate that\nTynes interpreted “request” as “favorable treatment.” This\nreliance on “sequential referents” is, from her perspective,\nexactly what we criticized in Serafini. 167 F.3d at 821. But\nshe misconstrues our holding.\n\n In Serafini, the surrounding questions focused on a\ndifferent topic. This bolstered appellant’s argument in that\ncase that the question on which the perjury conviction rested\nwas fundamentally ambiguous. Id. The appellant said the\nmultiplicity of topics in surrounding questions caused the jury\nto speculate improperly on how he understood the question at\nissue. We said: “The meaning of individual questions and\nanswers is not determined by ‘lifting a statement . . . out of its\nimmediate context,’ when it is that very context which fixes\n\n\n\n\n 31\n\fthe meaning of the question.” Serafini, 167 F.3d at 821\n(quoting United States v. Tonelli, 577 F.3d 194, 198 (3d Cir.\n1978)). In the case of Serafini, the context made the\nconfusing nature of the question apparent. The various topics\nin surrounding questions created sufficient ambiguity to\nundermine the conviction. Id.\n\n Here, however, even though the terms used by the\nexaminer changed, we conclude that the line of questioning—\nincluding both questions that ground Count 71 and 72—have\nan obvious, consistent focus.\n\n Q. In all the years\n you’ve been [at Traffic\n Court] have you\n ever been asked to give\n favorable treatment on\n a case to anybody?\n\n A. No, not favorable\n treatment. People basically\n know me. The lawyers\n know me. The court\n officers know me. I have\n been called a nononsense\n person because I’m just not\n that way. I take my\n position seriously and the\n cards fall where they\n may. Most of the time . . .\n the people in my Court\n plea bargain. They know\n that most of the time,\n\n\n\n\n 32\n\fninety percent of the time,\nsay 90 percent, I go with\nthe police officer’s\nrecommendation. . . .\n\nQ. So, in all those years\nno one has ever asked you\nto find somebody not\nguilty--\n\nA. No.\n\nQ. --or to find a lesser\nviolation; find a lesser fine;\nanything along those lines?\n\nA. No. I will say to\npeople go to court, go to\ntrial and see what\nhappens. . . .\n\nQ. Ward leaders,\npoliticians has anyone\ncalled you and said I\nhave Johnny Jones coming\nup next week and I\nwould appreciate it if -- if\nyou would look\nfavorably on him when he\ncomes through? Has\nanything like that ever\nhappened?\n\n\n\n\n 33\n\f A. Throughout the\n years ward leaders and\n people have called all the\n time and asked me\n questions. The only thing I\n will say to them is they\n need to go to court. If you\n think it’s a problem, they\n need to hire a lawyer, or\n make sure you bring all\n your evidence to court. If\n it’s something like\n inspection, make sure you\n bring your -- papers and\n things like that. That’s\n what I would tell them to\n do. I give advice that\n way. I don’t know if that’s\n wrong or not, but I do.\n\n Q. You’ve never taken\n action on a request?\n\n A. No.\n\nApp. 528-29, 530; 5720-22. This broader context would give\nany reasonable fact-finder more than enough basis to\nconclude that the witness knew the point of reference for both\nthe term “favorable treatment” and “request” was ticket\nfixing. In fact, Tynes is asking us to do precisely the thing we\ncriticized in Serafini, to lift a phrase or statement out of its\ncontext. Serafini, 167 F.3d at 821. Tynes has not persuaded\nus that the question harbors any fatal ambiguity.\n\n\n\n\n 34\n\f Tynes next contends that her responses to questions\ngrounding Count 71 and Count 72 cannot support convictions\nfor perjury because they were literally true. Of course,\nperjury arises only from making knowingly false material\ndeclarations. 18 U.S.C. § 1623. Therefore, a witness who\nanswers an ambiguous question with a non-responsive answer\nthat the witness believes is true—even if the answer is\nmisleading—does not commit perjury. See Bronston, 409\nU.S. at 361-62; see also United States v. Reilly, 33 F.3d 1396,\n1416 (3d Cir. 1994).\n Tynes argues that, because she regarded the question\nabout favorable treatment as vague, she interpreted it as\nasking whether she accepted any bribes in exchange for a\njudgment of not guilty or a reduced punishment. Her\nresponse of “no” (grounding Count 71) is literally true—she\nsays—because there is no evidence that she accepted any\nbribes in return for giving preferential outcomes in the\nadjudication of some individuals who were cited for breaking\nthe law. Under this theory, the same argument can also\nnegate the charges at Count 72 since she says she did not\naccept any “requests” (bribes) in exchange for preferential\ntreatment.\n\n Although the jury is permitted reasonable inferences\ndrawn from the record about the witness’ understanding of\nthe truth or falsity of the answer, it is not (as we noted above)\npermitted to reach conclusions based merely on speculation\nor conjecture. See Bronston, 409 U.S. at 359. Tynes’\nassertion of literal truth is undermined because the trial record\nsupports no reasonable inference that the Government was\nasking her about matters outside of the alleged bribes, nor\n\n\n\n\n 35\n\fdoes it provide any reason why Tynes would interpret the\nquestion in this way.\n\n Finally, Tynes contends that the evidence was not\nsufficient to support her conviction. However, the jury heard\nTynes’ personal assistant, Medaglia “Dolly” Warren, testify\nthat she received from personal assistants of other judges\nthree to four cards per week requesting consideration. Each\ncard had the name of a person who was appearing before\nTynes on that day. She passed these to Tynes’ court officer,\nwho was present during the proceedings. App. 4593-95.\nTynes also instructed Warren to give similar cards to the staff\nof other judges. App. 4598. Warren knew to act discreetly\nwhen she was transferring the cards. App. 4599. The jury\nalso heard testimony from those who actually received\nconsideration from Tynes. For example, Timothy Blong was\ncited for reckless driving and driving without a license. He\nadmitted in testimony that he did not have a license when he\nwas cited. App. 3150. He also testified that he requested\nconsideration through a Traffic Court employee (Danielle\nCzerniakowski, who worked as a personal assistant to a\nTraffic Court judge) with whom he was acquainted. When he\nappeared in court, he was simply told that his case was\ndismissed. He did not have to say anything, App. 3159-60.\nBlong testified he was told his case was dismissed because\nthe police officer did not appear (App. 3160-61), but the\ngovernment produced evidence that an officer was present.\nApp. 3193-96. The Government also showed that Tynes was\nthe presiding judge in Blong’s case. App. 3193. Richard\nCarrigan—who admitted in testimony that he drove through a\nred light—described a similar experience in which, after\nrequesting favorable treatment through Judge Lowry’s\npersonal assistant, Kevin O’Donnell, his case was dismissed\n\n\n\n\n 36\n\fby Judge Tynes without ever having to say a word. App.\n3178-82.\n\n Tynes does not challenge any of this in her appeal.\nInstead she focuses on the weight of other evidence and\nperceived gaps in testimony. We conclude that all of this\nprovides more than a sufficient basis to support a reasonable\njury’s conclusion that Tynes did “give favorable treatment on\na case,” and did “take[] action on a request.” App. 528-30.\n\n For all of these reasons, we will affirm the judgment of\nconviction on perjury as to Appellant Tynes.\n C.\n\n Appellant Lowry 27\n\n Like Tynes, Appellant Lowry advances arguments of\nfundamental ambiguity and literal truth. His perjury\nconviction centered on one question and answer.\n\n\n Q. So if I understand\n your testimony, you’re\n saying you don’t give out\n special favors; is that right?\n\n A. No, I treat\n everybody in that\n courtroom the same.\n\n\n27\n Lowry was charged with perjury in Count 69 of the\nindictment.\n\n\n\n\n 37\n\fApp. 489. Lowry attacks the Government’s use of the term\n“special favors” as one with many potential meanings.\nHowever, as we noted above in our reference to Serafini, we\nreject arguments that lift individual questions or answers—or\nindividual phrases embedded in either—from the context of\nsurrounding questions that help fix their meaning. Serafini,\n167 F.3d at 821. The larger context for the question asked of\nLowry is as follows.\n\n Q. So if I understand\n your testimony, you’re\n saying you don’t give out\n special favors; is that right?\n\n A. Well, I know it\n appears that way; and it’s\n hard for me to prove to\n you . . .\n\n Q. I’m just asking,\n your testimony is you don’t\n give out special favors, is\n that right?\n\n A. No, I treat\n everybody in that\n courtroom the same.\n\n Q. You treat everybody\n fairly?\n\n A. I’m a lenient judge.\n I will admit to that.\n\n\n\n\n 38\n\f Q. You treat everybody\n fairly?\n\n A. Yes, I do.\n\n Q. And these notices\n that you get from your\n personal or from other\n people, they don’t affect\n you in any way; is that\n right?\n\n A. Virtually no effect\n at all.\n\n\nApp. 489-90.\n\n Lowry’s assertion that the phrase “special favors” is\nsubject to many interpretations is unconvincing. We note two\nthings. First, the line of questioning reasonably supports a\nconclusion that this inquiry referenced conduct associated\nwith allegations of ticket fixing. Second, Lowry answered as\nif his understanding of the question was consistent with this\ninterpretation. He said that he was aware it may “appear” that\nhe gave special favors. He also defended himself by saying\nthat such requests did not affect his conduct in the courtroom\nat all. If—as he says—he understood “special favors” to\nmean fair treatment, his answer makes no sense.\n\n Lowry next claims that, since the question was\nstructured to elicit a negative response, his answer cannot be\n\n\n\n\n 39\n\fused as the basis of a perjury charge. Relatedly, he contends\nthat the question was merely a summation of an answer that\nhe gave just before this question. In essence he argues that\nthis was a leading question. We have concluded, in the\ncontext of a trial, that the propriety of leading questions in\ndirect examinations is a matter left to the sound discretion of\nthe trial judge. See United States v. Montgomery, 126 F.2d\n151, 153 (3d Cir. 1942). We extend the same deference here\nto the District Court’s decision to admit this portion of the\nGrand Jury transcript. We do not regard the question as\nfundamentally unfair or unclear, or something outside the\nnorm of questions typically employed on direct examination.\nFor these reasons, we conclude that the District Court did not\nabuse its discretion here.\n\n Alternatively, Lowry argues that—if the term is\nunderstood to reference fixing tickets—there is no evidence\nto contradict his response that requests for special favors did\nnot impact any of his adjudications. We do not agree. The\nrecord contains the following testimony.\n\n Kevin O’Donnell, who was Lowry’s personal\nassistant, testified about Lowry’s involvement with requesting\nand giving consideration. He said that Lowry made four to\nfive requests each month for consideration and that\nO’Donnell transmitted them to the personal assistants of other\nTraffic Court judges. App. 1854. Likewise, he said other\njudges transmitted requests for consideration to Lowry\nthrough their personal assistants. App. 1812-13. Appellant\nHird and various politicians also made requests of Lowry for\nconsideration. App. 1827-28, 1832-33. O’Donnell said he\nwould give the requests to Lowry on the day scheduled for\nhearing on the citation. App. 1818-19. The requests were for\n\n\n\n\n 40\n\fpreferential treatment in the adjudication of particular\ncitations: typically the requests were for “removing points”\nand obtaining a “not guilty” judgment. App. 1819.\nO’Donnell said he sometimes had to signal Lowry in the\ncourtroom to remind him that a particular case was supposed\nto receive consideration. App. 1822-23. He testified from\nhis own observation that Lowry typically honored requests\nfor consideration. App. 1829. He also declared if Lowry\nclaimed he never gave consideration or asked it of others, this\nwould not be truthful. App. 1813. The same assistant\ntestified that if Lowry testified that he ignored requests for\nconsideration, or that he never honored requests for\nconsideration, that testimony would not be true. App. 1855.\nThe Government also asked: “If [Lowry] claimed that . . .\nconsideration requests had no impact when he disposed of\ncases, would that be true?” The assistant responded,\n“probably not.” Id.\n\n Another witness, Walt Smaczylo, employed as a court\nofficer in the Traffic Court, provided an example of how\n“consideration” worked in the courtroom.\n\n When someone comes in,\n for example, for a reckless\n driving ticket and that\n judge normally comes\n down pretty hard and finds\n that defendant guilty and\n then the same type cases\n come in and you see a\n defendant walk out either\n not guilty or a significantly\n reduced charge.\n\n\n\n\n 41\n\fApp. 1912. The Government asked Smaczylo if he saw\nLowry preside over such instances, and he answered: “That’s\ncorrect, yes.” Id. Smaczylo testified that requests for\nconsideration were written on small note cards or “sticky”\nnotes and that he saw Lowry in possession of these cards and\nnotes. App. 1914. He also provided a generalized example\nof consideration, based on his observation and understanding,\nin which a reckless driving citation would be reduced to\ncareless driving. In such instances, he indicated that a $300\nto $400 fine would be cut in half. He said: “So, that money\nwas not collected, obviously, by the state. If that ticket was\nfixed then I saw it as stealing.” App. 1919. Smaczylo was\nasked: “[I]f Judge Lowry testified at the [G]rand [J]ury he\ndidn’t give consideration would that be a truth or would that\nbe a lie?” He responded: “That would not be the truth.”\nApp. 1921.\n\n All of this testimony provides more than a sufficient\nbasis to support a reasonable jury’s conclusion that Lowry\nwas not truthful when he responded to the Government’s\nquestion about special favors. 28\n\n28\n Lowry points to the cross-examination of both witnesses in\nwhich they seem to equivocate on some of their observations\nand responses to the Government. For instance O’Donnell\nstated his view that giving consideration was no different\nfrom the leniency that Lowry extended to every other person\nwho pleaded not guilty and appeared at the hearing.\nHowever, we do not weigh the credibility of evidence in the\nrecord. We only judge whether there is sufficient evidence in\nthe record to support a reasonable fact-finder’s determination\nthat the record supported conviction of Lowry on a charge of\n\n\n\n\n 42\n\f Finally, Lowry argues that the Government’s question\nsought a dispositive response from him on the charges of\nconspiracy and fraud. He says an affirmative answer to\nwhether he gave “special favors” to certain individuals would\nhave been enough to convict him of conspiracy and fraud.\nThus, he maintains that his acquittal on charges of mail fraud,\nwire fraud, and conspiracy is res judicata as to the perjury\ncharges that are based on his answer. He said he did not\ncommit fraud and the jury agreed with him. Therefore, he\nsays, he did not perjure himself. However, even if we\naccepted Lowry’s characterization of the question, we reject\nthis argument.\n\n First, a jury’s determination that Lowry’s ticket-fixing\nconduct did not constitute wire fraud, mail fraud, and\nconspiracy does not preclude its determination that he lied\nabout this conduct before the Grand Jury. Moreover, as the\nSupreme Court has articulated, a verdict on one count that\nseems to be at odds with another “shows that either in the\nacquittal or the conviction the jury did not speak their real\nconclusions, but that does not show that they were not\nconvinced of the defendant’s guilt.” United States v. Powell,\n469 U.S. 57, 63 (1984) (quoting Dunn v. United States, 284\nU.S. 390, 393 (1932)). It is impossible to know in such cases\nwhether the verdicts were an exercise of lenity by the jury or\noutright error.\n\n Nonetheless, as the Powell Court noted, any\nassessment of the jury’s rationale for its verdicts “would be\n\n\nperjury. See United States v. Richardson, 658 F.3d 333, 337\n(3d Cir. 2011).\n\n\n\n\n 43\n\fbased either on pure speculation or would require inquiries\ninto the jury’s deliberations that courts generally will not\nundertake.” Id. at 58. So, even if Lowry was correct that the\nacquittal is relevant to his response to the question grounding\nhis perjury conviction, we are not convinced that his perjury\nconviction is unfounded. Given the substantial body of\nevidence presented to the jury, nothing here demands that we\nabandon the deference we traditionally give to the collective\njudgment of the jury. For all these reasons, we will affirm the\njury’s verdict as to Lowry.\n\n D.\n\n Appellant Mulgrew 29\n\n Mulgrew does not argue that the question asked at the\nGrand Jury was ambiguous, he simply maintains that his\nstatement was truthful. 30 The questions and answers\ngrounding his perjury conviction are as follows.\n\n Q. How about your\n personal, has your personal\n received any calls like that\n from other judges, other\n ward leaders that she’s\n conveyed to you, saying\n\n29\n Mulgrew was charged with perjury in Count 70 of the\nindictment.\n30\n Mulgrew’s claims are reviewed for plain error because he\ndid not make the same argument before the District Court.\nUnited States v. Syme, 276 F.3d 131, 148 (3d Cir. 2002).\n\n\n\n\n 44\n\f so-and-so has called about\n this case?\n\n A. If she did, she didn’t\n convey them to me.\n\n\nApp. 432-33 (emphasis added). Shortly after this, the\nfollowing exchange occurred:\n\n Q. Let me make sure as\n well that if I got your\n testimony correct [sic].\n You’re saying that if other\n people, whether they be\n political leaders, friends\n and family, anybody is\n approaching your personal\n and asking her specifically\n to look out for a case, see\n what she can do in a case,\n give preferential treatment,\n however you want to\n phrase it, that she is not\n relaying any of that\n information on to you; is\n that correct?\n\n A. No, she isn’t.\n\nApp. 438. As to the first exchange, Mulgrew claims that the\nGovernment’s use of the word “call” referred exclusively to\ntelephone calls. This mattered to him, he says, because others\n\n\n\n\n 45\n\fhad testified that personal assistants of other Traffic Court\njudges would give index cards to his personal assistant in his\nchambers or robing room containing names of some\nindividuals whose tickets were listed for hearing. Mulgrew\nclaims that there is no evidence that he ever received any\nphone calls asking that he act extrajudicially to give well-\nconnected individuals preferential treatment. The implication\nis that, had the Government asked him about receiving index\ncards with such requests, his answer would have been\ncompletely different.\n As with Tynes and Lowry, our review of claims of\nliteral truth drives us to examine the context of the question.\n\n Q. How about other\n judges, have other judges\n ever approached you or\n called to you or get a\n message to you either\n themselves or through their\n personals saying that\n someone is going to be on\n your list next week or next\n Monday and can you could\n some special way towards\n the case?\n\n A. No, they haven’t.\n\n Q. Never?\n\n A. No.\n\n\n\n\n 46\n\fQ. How about your\npersonal, has your personal\nreceived any calls like that\nfrom other judges, other\nward leaders that she’s\nconveyed to you saying so\nand so has called about this\ncase?\n\nA. If she did, she didn’t\nconvey them to me.\n\nQ. And your personal\nis who?\n\nA. Gloria McNasby.\n\nQ. Have you ever seen\non traffic court files --You\nactually get a file when\nsomeone’s case is called?\n\nA. Right.\n\nQ. So the case is called\nand you get a file presented\nto you; is that right?\n\nA. uh-huh.\n\nQ. Have you ever seen\nany index cards or\nnotations on the file\n\n\n\n\n 47\n\f indicating that a person has\n called or taken some\n special interest in this\n case?\n\n A. Nope.\n\nApp. 432-33 (emphasis added). The transcript makes it\nobvious that Mulgrew’s singular reliance on the reference to a\n“call” ignores the thrust of the Government’s line of\nquestions. The questions focus on the substance of the\ncommunications between Mulgrew’s personal assistant and\nhimself, rather than the mode of those communications.\n\n Mulgrew also claims that he responded truthfully to\nthe second question.\n\n Q. Let me make sure as\n well that if I got your\n testimony correct [sic].\n You’re saying that if other\n people whether they be\n political leaders, friends\n and family, anybody is\n approaching your personal\n and asking her specifically\n to look out for a case, see\n what she can do in a case,\n give preferential treatment,\n however you want to\n phrase it, that she is not\n relaying any of that\n\n\n\n\n 48\n\f information on to you; is\n that correct?\n\n A. No, she isn’t.\n\n Q. Wouldn’t you want\n to know it?\n\n A. No, I don’t want to\n know. Then I never have to\n worry about what I do in\n the courtroom.\n\nApp. 437-38 (emphasis added). Apparently focusing on the\nwords “see what she can do,” he says that he answered\ntruthfully by responding that his personal assistant did not tell\nhim that people were approaching her and asking her to give\nthem preferential treatment. But, as with the first question,\nMulgrew cherry-picks a small part of the question out of\ncontext, distorting it. The full text and follow up question\nshow that the thrust of the inquiry was whether Mulgrew’s\npersonal assistant was informing him of the names of those\nrequesting preferential treatment from him. And Mulgrew’s\nresponse to the follow-up question —saying that he did not\nwant to know so that he did not have to worry about what he\ndid in the courtroom—is consistent with one who understood\nthis. App. 438.\n\n We conclude that, ultimately, the evidence is sufficient\nfor a reasonable jury to conclude Mulgrew understood that\nboth of these questions were focused on whether his personal\nassistant informed him of requests for him to give preferential\ntreatment, and that he answered in the negative to both.\n\n\n\n\n 49\n\f Mulgrew alternatively asserts that the District Court\nerred by refusing to admit additional testimony from the\nGrand Jury that he claims is relevant to his perjury\nconviction. 31 After the Government introduced Mulgrew’s\nGrand Jury testimony, Mulgrew sought the admission of other\nportions of his testimony. But the District Court sustained the\nGovernment’s hearsay objection. The portion of the\ntranscript supporting the perjury conviction is as follows:\n\n Q. [W]hether you have\n ever been asked to provide,\n what I’ll call, favorable\n treatment for people in\n traffic court or however\n you define that, whether it\n would be special handling,\n keep an eye out for a\n ticket, do me a favor.\n Have you ever been asked\n to provide any type of\n treatment like that for\n people in traffic court?\n\n A. People have asked\n me for consideration, but I\n give consideration to\n everybody that comes in\n my courtroom[,] so it\n\n31\n We review the District Court’s ruling on the admissibility\nof evidence for abuse of discretion. United States v. Green,\n617 F.3d 233, 239 (3d Cir. 2010).\n\n\n\n\n 50\n\f doesn’t make a difference\n to me.\n\n\nApp. 422-23. The basis for the Government’s hearsay\nobjection to this portion of the testimony was that it raised an\nout-of-court statement not offered by a party opponent.\n\n Mulgrew first contends that the District Court erred by\nruling that this was hearsay because it was not offered for the\ntruth of the matter asserted. He says that the testimony was\ninstead offered to show his state of mind later in his\ntestimony. See United States v. Hoffecker, 530 F.3d 137,\n191-92 (3d Cir. 2008). However, we conclude that it was not\nan abuse of discretion for the District Court to sustain the\nGovernment’s hearsay objection. It was reasonable for the\nDistrict Court to conclude here that his response relied on\nout-of-court statements offered to assert his innocence since\nhis response conveys a declaration that he treated no person\ndifferent from another.\n\n Mulgrew also argues that this portion of the transcript\nis admissible under Federal Rule of Evidence 106: “[i]f a\nparty introduces all or part of a writing or recorded statement,\nan adverse party may require the introduction, at that time, of\nany other part—or any other writing or recorded statement—\nthat in fairness ought to be considered at the same time.”\nMulgrew maintains that this question and answer provides\ncontext showing that he did not commit perjury. He also\nmaintains that the “doctrine of completeness” applies here:\nfairness demanded the admission of the statements. See\n\n\n\n\n 51\n\fUnited States v. Soures, 736 F.2d 87, 91 (3d Cir. 1984). 32 We\nare not convinced.\n\n The excerpt at issue occurs many pages before the\ntestimony regarded as perjurious. It is unrelated in the overall\nsequence of questions and to the answers grounding his\nconviction. Moreover, as the intervening pages suggest, it\nwas separated by the passage of time during questioning. We\nalso fail to see how Mulgrew’s equivocation over the term\n“consideration” gives helpful context to his later denial of\nreceiving requests for consideration. For these reasons, we\nconclude the District Court did not abuse its discretion by\nsustaining the Government’s hearsay objection.\n\n IV.\n\n Appellant Singletary 33\n\n\n32\n “Under this doctrine of completeness, a second writing may\nbe required to be read if it is necessary to (1) explain the\nadmitted portion, (2) place the admitted portion in context, (3)\navoid misleading the trier of fact, or (4) insure a fair and\nimpartial understanding.” Soures, 736 F.2d at 91.\n33\n Appellant Singletary was charged with making false\nstatements in Counts 73 and 74 of the indictment. He states\nin his brief that he ‘joins all arguments on behalf of co-\nappellants pursuant to Federal Rules of Appellate Procedure\n28(i).” Singletary Br. 19. To the extent that he joins the\nargument of prejudice resulting from the trial on the fraud and\nconspiracy charges, we already have determined that the\nindictment was proper and no prejudice resulted from\n\n\n\n\n 52\n\f During the investigation of the Traffic Court by the\nFederal Bureau of Investigation, Appellant Singletary was\namong those interviewed. The jury acquitted Singletary of all\ncounts of wire fraud, mail fraud, and conspiracy. It found\nhim guilty of false statements made to the Federal Bureau of\nInvestigation. At sentencing, over Singletary’s objection, the\nDistrict Court sentenced Singletary using the Guideline on\nobstruction.\n\n The Government agrees that the single count on which\nhe was convicted does not contain all of the elements of\nobstruction. U.S.S.G. § 2J1.2. For this reason, the\nGovernment agrees with Singletary that he is entitled to a\nremand for resentencing. Accordingly, we will vacate the\njudgment of sentence as to Singletary and remand to the\nDistrict Court for resentencing.\n\n V.\n\n For all of these reasons, we will vacate the judgment of\nsentence of the District Court with regard to Appellant\nSingletary and remand for resentencing. We will affirm the\njudgments of the District Court as to Appellants Alfano, Hird,\nLowry, Mulgrew and Tynes.\n\n\n\nbringing these charges to trial. As for the challenges to\nperjury in Counts 72 and 74, we note that Singletary was\ncharged with a different crime: false statements in a federal\ninvestigation pursuant to 18 U.S.C. § 1001. In addition, the\nchallenges to all of such charges are inherently fact-intensive.\nAs he did not provide a factual basis for such a challenge, we\nregard the issue to be waived.\n\n\n\n\n 53\n[END_CASE]", "role": "user" } ]
4,583,111
UNITED STATES of America v. Thomasine TYNES, Appellant
United States v. Thomasine Tynes
2019-01-18
14-4804
U.S. Court of Appeals for the Third Circuit
{"judges": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN, HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE, RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges The petition for rehearing en banc", "parties": "", "opinions": [{"author": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN", "type": "010combined", "text": "UNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n\n\n No. 14-4804\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n THOMASINE TYNES,\n Appellant\n\n\n (E. D. Pa. Criminal No. 2-13-cr-00039-005)\n\n\n\n\n SUR PETITION FOR REHEARING\n\n\n\n\n Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN,\n HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE,\n RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges\n\n\n The petition for rehearing en banc filed by appellant Thomasine Tynes in\n\nthe above-entitled case having been submitted to the judges who participated in the\n\ndecision of this Court and to all the other available circuit judges of the circuit in regular\n\nactive service, and no judge who concurred in the decision having asked for rehearing,\n\n\n\n*\n Pursuant to Third Circuit I.O.P. 9.5.3, Judge Richard L. Nygaard’s and Judge D.\nMichael Fisher’s votes are limited to panel rehearing.\n\fand a majority of the circuit judges of the circuit in regular service not having voted for\n\nrehearing, the petition for rehearing en banc is DENIED.\n\n The petition for rehearing by the panel is GRANTED IN PART, solely as to the\n\nclaim that there was insufficient evidence to support Tynes’ conviction.\n\n After consideration of Appellant’s argument, the panel has agreed to amend the\n\nopinion, which will be filed simultaneously with this order in all of the consolidated\n\ncases. Each of the judgments entered August 21, 2018, shall remain in full force and\n\neffect.\n\n BY THE COURT,\n\n\n s/ Richard L. Nygaard\n Circuit Judge\n\nDated: January 18, 2019\nPDB/CLW/cc: All Counsel of Record", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360364/", "author_raw": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN"}]}
SMITH
MCKEE
AMBRO
2
CHAGARES; JORDAN; HARDIMAN; GREENAWAY JR; SHWARTZ; KRAUSE; RESTREPO; BIBAS; PORTER; NYGAARD; FISHER
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583111/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America v. Thomasine TYNES, Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n\n\n No. 14-4804\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n THOMASINE TYNES,\n Appellant\n\n\n (E. D. Pa. Criminal No. 2-13-cr-00039-005)\n\n\n\n\n SUR PETITION FOR REHEARING\n\n\n\n\n Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN,\n HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE,\n RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges\n\n\n The petition for rehearing en banc filed by appellant Thomasine Tynes in\n\nthe above-entitled case having been submitted to the judges who participated in the\n\ndecision of this Court and to all the other available circuit judges of the circuit in regular\n\nactive service, and no judge who concurred in the decision having asked for rehearing,\n\n\n\n*\n Pursuant to Third Circuit I.O.P. 9.5.3, Judge Richard L. Nygaard’s and Judge D.\nMichael Fisher’s votes are limited to panel rehearing.\n\fand a majority of the circuit judges of the circuit in regular service not having voted for\n\nrehearing, the petition for rehearing en banc is DENIED.\n\n The petition for rehearing by the panel is GRANTED IN PART, solely as to the\n\nclaim that there was insufficient evidence to support Tynes’ conviction.\n\n After consideration of Appellant’s argument, the panel has agreed to amend the\n\nopinion, which will be filed simultaneously with this order in all of the consolidated\n\ncases. Each of the judgments entered August 21, 2018, shall remain in full force and\n\neffect.\n\n BY THE COURT,\n\n\n s/ Richard L. Nygaard\n Circuit Judge\n\nDated: January 18, 2019\nPDB/CLW/cc: All Counsel of Record\n[END_CASE]", "role": "user" } ]
4,583,112
UNITED STATES of America v. Robert MULGREW, Appellant
United States v. Robert Mulgrew
2019-01-18
14-4812
U.S. Court of Appeals for the Third Circuit
{"judges": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN, HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE, RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges The petition for rehearing en banc", "parties": "", "opinions": [{"author": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN", "type": "010combined", "text": "UNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n\n\n No. 14-4812\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n ROBERT MULGREW,\n Appellant\n\n\n (E. D. Pa. Criminal No. 2-13-cr-00039-003)\n\n\n\n\n SUR PETITION FOR REHEARING\n\n\n\n\n Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN,\n HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE,\n RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges\n\n\n The petition for rehearing en banc filed by appellant Robert Mulgrew in the\n\nabove-entitled case having been submitted to the judges who participated in the decision\n\nof this Court and to all the other available circuit judges of the circuit in regular active\n\nservice, and no judge who concurred in the decision having asked for rehearing, and a\n\n\n\n*\n Pursuant to Third Circuit I.O.P. 9.5.3, Judge Richard L. Nygaard’s and Judge D.\nMichael Fisher’s votes are limited to panel rehearing.\n\fmajority of the circuit judges of the circuit in regular service not having voted for\n\nrehearing, the petition for rehearing en banc is DENIED.\n\n The petition for rehearing by the panel is GRANTED IN PART, solely as to\n\nAppellant’s claim that he is entitled to a consideration of the sufficiency of the evidence\n\nof perjury based upon an accurate understanding of his argument relating to his response\n\nto a particular question.\n\n Q. Let me make sure as well that if I got your\n testimony correct [sic]. You’re saying that if\n other people whether they be political leaders,\n friends and family, anybody is approaching\n your personal and asking her specifically to\n look out for a case, see what she can do in a\n case, give preferential treatment, however you\n want to phrase it, that she is not relaying any of\n that information on to you; is that correct?\n\n A. No, she isn’t.\n\n\nApp. 437-38. After consideration of Appellant’s argument, the panel has agreed to\n\namend the opinion, which will be filed simultaneously with this order in all of the\n\nconsolidated cases. Each of the judgments entered August 21, 2018, shall remain in full\n\nforce and effect.\n\n\n BY THE COURT,\n\n s/ Richard L. Nygaard\n Circuit Judge\n\nDated: January 18, 2019\nPDB/CLW/cc: All Counsel of Record", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360365/", "author_raw": "Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN"}]}
SMITH
MCKEE
AMBRO
2
CHAGARES; JORDAN; HARDIMAN; GREENAWAY JR; SHWARTZ; KRAUSE; RESTREPO; BIBAS; PORTER; NYGAARD; FISHER
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583112/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America v. Robert MULGREW, Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n\n\n No. 14-4812\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n ROBERT MULGREW,\n Appellant\n\n\n (E. D. Pa. Criminal No. 2-13-cr-00039-003)\n\n\n\n\n SUR PETITION FOR REHEARING\n\n\n\n\n Present: SMITH, Chief Judge, McKEE, AMBRO, CHAGARES, JORDAN,\n HARDIMAN, GREENAWAY, JR., SHWARTZ, KRAUSE,\n RESTREPO, BIBAS, PORTER, NYGAARD, and FISHER * Circuit Judges\n\n\n The petition for rehearing en banc filed by appellant Robert Mulgrew in the\n\nabove-entitled case having been submitted to the judges who participated in the decision\n\nof this Court and to all the other available circuit judges of the circuit in regular active\n\nservice, and no judge who concurred in the decision having asked for rehearing, and a\n\n\n\n*\n Pursuant to Third Circuit I.O.P. 9.5.3, Judge Richard L. Nygaard’s and Judge D.\nMichael Fisher’s votes are limited to panel rehearing.\n\fmajority of the circuit judges of the circuit in regular service not having voted for\n\nrehearing, the petition for rehearing en banc is DENIED.\n\n The petition for rehearing by the panel is GRANTED IN PART, solely as to\n\nAppellant’s claim that he is entitled to a consideration of the sufficiency of the evidence\n\nof perjury based upon an accurate understanding of his argument relating to his response\n\nto a particular question.\n\n Q. Let me make sure as well that if I got your\n testimony correct [sic]. You’re saying that if\n other people whether they be political leaders,\n friends and family, anybody is approaching\n your personal and asking her specifically to\n look out for a case, see what she can do in a\n case, give preferential treatment, however you\n want to phrase it, that she is not relaying any of\n that information on to you; is that correct?\n\n A. No, she isn’t.\n\n\nApp. 437-38. After consideration of Appellant’s argument, the panel has agreed to\n\namend the opinion, which will be filed simultaneously with this order in all of the\n\nconsolidated cases. Each of the judgments entered August 21, 2018, shall remain in full\n\nforce and effect.\n\n\n BY THE COURT,\n\n s/ Richard L. Nygaard\n Circuit Judge\n\nDated: January 18, 2019\nPDB/CLW/cc: All Counsel of Record\n[END_CASE]", "role": "user" } ]
4,583,113
United States v. Raymont Wright
2019-01-18
17-1972
U.S. Court of Appeals for the Third Circuit
{"judges": "Before: MCKEE, SHWARTZ, and NYGAARD, Circuit Judges.", "parties": "", "opinions": [{"type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014.1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13", "author": "SHWARTZ, Circuit Judge."}, {"type": "dissent", "author": "Our", "text": "Our dissenting colleague says that our approach\ndeprives the court from taking action “when warranted to\nprotect the institutional integrity of the judiciary.” Dissent at\n3. We disagree. This approach recognizes a court’s role in our\ntripartite system of government and ensures that a court\nintercedes when proceeding would violate the Constitution.\nFurthermore, our approach does not preclude a court from\nending a case where the evidence is insufficient or the conduct\nof the prosecution is improper.\n\n\n\n\n 22"}, {"author": "McKEE, Circuit Judge, concurring", "type": "concurrence", "text": "McKEE, Circuit Judge, concurring in the judgment.\n\n As I shall explain, I am sympathetic to what the District\nCourt was trying to do in this case and I think I understand why\nthe court acted as it did. Moreover, I agree with Judge Nygaard\ninsofar as he posits in dissent that a District Court can step in\nat some point and bar a retrial without infringing on the\nseparation of powers. Nevertheless, despite my belief that the\nseparation of powers doctrine is not necessarily violated by a\ntrial court barring a retrial after successive mistrials, and\ndespite my belief that the District Court was trying to act in a\nmanner that would assure a measure of justice for Wright, I\nconcur in the judgment reversing the District Court. I simply\ndo not believe that the current state of the law supports the\nDistrict Court’s action in the absence of prosecutorial\nmisconduct, bad faith, or more than two unsuccessful trials.\nSince the record is clear that the District Court found neither\nprosecutorial misconduct nor bad faith, I concur in the\njudgment reversing the court’s order but feel compelled to\nwrite separately to explain why.\n I.\n At the outset, it is important to note that I do not believe\nthat a trial court lacks the power to, at some point, call a halt to\nsuccessive prosecutions following deadlocked juries, and I do\nnot read Judge Shwartz’s opinion as standing for that principle.\nThe Government even conceded at oral argument that there\ncould come a point where successive prosecutions become so\nonerous and burdensome that additional trials rise to the level\nof a Due Process violation which a trial court is clearly\nempowered to prevent. Moreover, in Barkus v. Illinois, 1 the\nSupreme Court noted that there “may” come a point where\nmultiple prosecutions become so harassing that they violate the\nDue Process Clause. 2\n\n Here the evidence in both trials consisted solely of\npolice testimony. According to the officers’ testimony, some\nresidents of the community witnessed crucial parts of Wright’s\nencounter with the police, but they did not testify. Similarly,\nWright did not testify on his own behalf, nor did the defense\nput on a case. His theory was that he had no way of knowing\n\n1\n 359 U.S. 121 (1959).\n2\n Id. at 127.\n 1\n\nthat the men in plain clothes and unmarked cars who began\npursuing him were police; he panicked, sped away, and\ncrashed; and police subsequently planted the gun at the scene.\nWright also asserted that the officers chose not to test the gun\nfor DNA or fingerprints because they knew the results would\ncontradict their story. In an effort to counter Wright’s\nargument from the first trial that police decided not to test the\ngun for fingerprints and DNA in order to hide their\nmalfeasance, the Government called experts at the second trial\n“who testified about the difficulty of retrieving DNA and\nfingerprint evidence from firearms.” 3\n\n Nevertheless, the Government’s case depended entirely\non the testimony of police officers who had worked together\nfor many years and/or knew one another. Over the span of ten\nmonths, the District Court twice listened to the police\ntestimony during the trials. That testimony was at times\ncontradictory and at other times strained credulity.\n\n At the first trial, Detective Fallert, who first noticed\nWright speeding, testified that Wright was travelling at 90\nmph, but he did not note that in his police paperwork nor did\nhe note it at the pretrial hearing. His contemporaneously\nprepared investigative report also did not claim that Wright\nwas initially speeding. Detective Henson, who took over the\nchase, testified that he saw Wright holding a handgun, but\nconceded that he had no way of knowing whether Wright knew\nhe was a police officer when the pursuit began. Lastly,\nDetective Baker testified similarly to Henson, yet guessed that\nWright had been going at a speed of 60 mph and accelerated.\nThis is a very substantial discrepancy, especially for seasoned\npolice officers who can be expected to have some expertise and\nexperience in estimating the speed of an automobile.\n\n In the second trial, the Government called the same\nwitnesses, with the exception of Detective Fallert. Notably,\nthis time Detective Henson testified he actually did not see\nWright speeding. Two different juries found themselves\ndeadlocked—unable to convict or acquit.\n II.\n The majority opinion suggests that the District Court’s\n\n3\n Appellant Br. at 11.\n 2\n\ndecision to dismiss the indictment with prejudice\nimpermissibly infringed upon the jury’s role. Judge Shwartz\nstates: “[t]he District Court nonetheless applied its own\npredictions about what another jury may do when presented\nwith the same evidence,” and concluded that was “an improper\nexercise of a court’s supervisory power.” 4 However, it is\ndifficult to know whether the District Court ruled as it did\nbased upon a belief that a third jury presented with the same\nevidence would be unable to reach a verdict or whether it\nsimply shared the doubts that some of the jurors obviously had\nabout the veracity of police officers’ testimony.\n\n In any event, either scenario poses exactly the same\nissue about a court overstepping its bounds and infringing on\nthe role of a jury as well as prosecutorial discretion. As I stated\nat the beginning, to the extent that a trial judge can intervene\nand dismiss an indictment, I am skeptical that this record\nsupports such an assertion of judicial authority. Nevertheless,\nthere is more support for the judge’s actions here than our\nreversal suggests.\n\n It is not a novel proposition that a trial judge must\n“ensure that any and all . . . evidence is not only relevant, but\nalso reliable.” 5 “The trial judge’s role is to preside over the\ntrial; passively if possible but aggressively when indicated.” 6\nThus, the law allows for trial courts to channel the jury’s\njudgment in certain circumstances. Here, the court’s decision\nwould prevent another jury from hearing the same evidence\nthat has failed to convict Wright on two prior occasions.\n\n There are situations in which judges must act as\n“gatekeepers” and ensure the reliability of evidence before a\njury is able to consider it. Accordingly, in an admittedly very\ndifferent context, the Supreme Court has described trial judges\nas gatekeepers of evidence. 7 “[A] gatekeeping role for the\n\n4\n Maj. Op. 13–14.\n5\n Kannankeril v. Terminix Int’l, Inc., 128 F.3d 802, 806 (3d\nCir. 1997) (citing Daubert v. Merrill Dow Pharms., 509 U.S.\n579, 589 (1993)).\n6\n Holdnrook v. Lykes Bros. Steamship Co., 80 F.3d 777, 788\n(3d Cir. 1996).\n7\n Daubert, 509 U.S. at 597.\n 3\n\njudge, no matter how flexible, inevitably on occasion will\nprevent the jury from learning of authentic insights and\ninnovations.” 8\n\n Despite the importance of the jury system, and the faith\nwe place in juries, the law has thus traditionally recognized the\ndanger that jurors may not be able to restrict their deliberations\nto admissible evidence and that they may return a verdict based\non factors other than the evidence presented at trial. For\nexample, Federal Rule of Evidence 403 allows courts to\nprevent jurors from learning of certain testimony (even\nuncontradicted testimony) if the court concludes that the\ntestimony could cause a jury to reach a verdict based more on\nemotion or prejudice than on evidence. 9\n\n The best known example of how courts are empowered\nto limit what a jury can consider may well be the body of law\nthat has developed in the wake of the Supreme Court’s decision\nin Daubert. In Daubert, the Court stated: “the trial judge must\nensure that any and all scientific testimony or evidence\nadmitted is not only relevant, but reliable.” 10 We certainly\ncould, but do not, allow the jury to determine whether the\nscientific evidence is reliable in the first instance based upon\ntestimony at trial. Instead, that preliminary factual\ndetermination rests solely with the trial court if the reliability\nis challenged.\n\n The difficulty with relying on this body of law here is,\nof course, the fact that the trial court’s dismissal of Wright’s\nindictment was not limited to an intrusion into the jury-box.\nMore fundamentally, and more importantly, it also trespassed\non the separation of powers, and concomitantly, on the\nprosecutorial discretion that is endemic in that concept.\n\n Despite Judge Nygaard’s thoughtful attempt to address\nthat issue and the jury’s obvious concerns regarding the\n\n8\n Id.\n9\n See, e.g., United States v. Bailey, 840 F.3d 99, 117, 121–23,\n(3d Cir. 2016) (finding that the probative value of video\nevidence of murder committed by coconspirators was\nsubstantially outweighed by risk of unfair prejudice).\n10\n Daubert, 509 U.S. at 589.\n 4\n\ntestimony of police officers in this case, I am not convinced\nthat the United States Supreme Court would agree that the\ninherent powers of a trial court are broad enough to justify what\nhappened here.\n\n The Government clearly has the inherent authority to\ndecide not to retry Wright given all of the circumstances in this\ncase, including the seemingly improbable account of what\nhappened, 11 the conflicting nature of the police testimony and\nthe jurors’ apparent trouble with it, the fact that there is no\nadditional evidence to offer at a third trial, and Wright’s\napparent steps toward rehabilitation since the offense which\ndisqualified him from lawfully owning a firearm, as well as any\nother factors that the Government might appropriately\nconsider. 12 However, I can find no authority that convinces me\nthat the United States Supreme Court would agree that a trial\ncourt’s inherent authority allows it to dismiss an indictment\nwith prejudice on this record.\n\n III.\n\n\n\n11\n According to the officers’ accounts, they watched (in the\nopen and without cover) as Wright fumbled in the back of a\ncar with tinted windows and came out holding a gun. They\nthen continued to stand and watch from approximately 25\nyards away—without cover and without taking any actions to\nprotect themselves—as he attempted to rack the slide which\nwould have placed a bullet in the chamber.\n12\n Appellee argues without contradiction that:\n\n [f]ollowing early involvement with the criminal\n justice system, Mr. Wright began to turn his life\n around, returning to school and earning his\n Associates degree in Computer Management-\n Networking Engineering Technology[,] . . . a\n Bachelor of Science degree in Information\n Technology and Management . . . graduating\n cum laude[,] . . . and . . . a Master of Science\n degree.\n\nAppellee Br. at 52.\n 5\n\n As I noted at the outset, the Government agrees that\nsuccessive prosecutions can rise to the level of a Due Process\nviolation, which a court clearly could remedy by dismissing an\nindictment. However, the Government strenuously argues\nWright’s prosecution has not yet reached that point. The\nGovernment’s position inherently argues that the court’s action\nhere is also not justified by any concept of fundamental\nfairness. In Ake v. Oklahoma, 13 the Supreme Court observed\nthat the right to Due Process includes the “guarantee of\nfundamental fairness.” 14 As has been discussed by Judge\nShwartz, the District Court here relied on the decision of the\nNew Jersey Supreme Court in State v. Abbati. 15 There, the\nNew Jersey Supreme Court affirmed a trial court’s dismissal of\nan indictment with prejudice after two juries deadlocked,\nresulting in mistrials. 16 That situation is on “all fours” with the\ncircumstances here and the District Court relied heavily on that\ndecision to justify its action and fashion a rule that would\nproperly allow a trial court to dismiss an indictment with\nprejudice under certain circumstances. 17\n\n However, the New Jersey Supreme Court based its\ndecision on the inherent authority of state courts under the New\nJersey Constitution. 18 It did not purport to rest its decision on\nthe U.S. Constitution and, with very limited exception, it cited\nto state judicial decisions—not federal ones—in discussing\nwhen consecutive hung juries justified dismissing an\nindictment with prejudice. 19 The holding of the Court is\n\n13\n 470 U.S. 68 (1985).\n14\n Id. at 76.\n15\n 493 A.2d 513 (N.J. 1985).\n16\n Id. at 522.\n17\n See United States v. Wright, Crim A No. 14-292, 2017 WL\n1179006, at *3, *4 (W.D. Pa. Mar. 30, 2017).\n18\n Abbati, 493 A.3d at 517–18.\n19\n Abbati cited to Ake, for the general proposition that the\n“requirement of fundamental fairness [is] grounded in [the]\nfourteenth amendment’s due process guarantee.” 493 A.2d at\n518. However, with the exception of a single District Court\ncase, the Court cited numerous state court cases for the\nproposition that a trial court had the inherent authority to\ndismiss an indictment with prejudice after two juries\ndeadlocked. Id. at 519–20. It concluded by finding “[t]hese\n 6\n\nsummarized in its statement that the “judicial responsibility for\nthe proper administration of criminal justice also gives rise to\nthe inherent power to dismiss an indictment in appropriate\ncircumstances.” 20\n\n The Abbati standard has not been discussed by this\nCourt (aside from in the instant case), let alone adopted by it.\nAlthough some of the factors used by the New Jersey Supreme\nCourt are analogous to considerations federal courts have made\nin similar federal cases, such as United States v. Ingram 21 and\nUnited States v. Rossoff, 22 Abbati has no real corollary in\nfederal case law. 23\n\nexamples of the courts’ exercise of their power to administer\nthe criminal justice system assist in answering the further\nargument of the State that recognition of an inherent judicial\npower to dismiss an indictment with prejudice would overstep\nthe separation of powers.” Id. at 520. Abbati dismissed that\nargument based upon its belief that “[t]he separation of\npowers is not an end in itself, but a general principle intended\nto ensure that the system of checks and balances remains\nvital.” Id. at 521 (citing State v. Leonardis, 375 A.2d 607, 612\n(N.J. 1977)).\n20\n Id. at 520.\n21\n 412 F. Supp. 384 (D.D.C. 1976). The District Court of the\nDistrict of Columbia dismissed an indictment after two trials\nin which twenty-one of twenty-four jurors voted to acquit.\nThe court found no prosecutorial misconduct. Id. at 386. It\ninstead considered the issue a “matter of fair play,”\nemphasizing that “[t]he Government has no new proof; it\nsimply wants another chance” and “simply wishes to keep\npressing so long as juries disagree in the hope that a\nconviction eventually will result.” Id. at 385.\n22\n 806 F. Supp. 200 (C.D. Ill. 1992).\n23\n For example, the first prong of Abbati’s analysis concerns\nthe number of mistrials and the outcome of the juries’\ndeliberations. 493 A.2d at 521. Both Rossoff and Ingram took\nthis into account in dismissing indictments. See Rossoff, 806\nF. Supp. at 203 (naming, as “additional compelling\ncircumstances: 1) the majority of jurors in both cases found\nDr. Rossoff Not Guilty; 2) if not for the allegedly biased juror\nin the second trial, Dr. Rossoff would have been acquitted on\nall counts; 3) the two trials have taken over one solid month\n 7\n\n Accordingly, as I noted at the outset, I am sympathetic\nto the District Court’s efforts given the totality of the\ncircumstances here. However, until Congress or the United\nStates Supreme Court determines otherwise, I agree that we\nhave no alternative but to enter judgment reversing the District\nCourt. I therefore concur in the judgment reversing the District\nCourt’s order.\n\n\n\n\nof the Court’s time”); Ingram, 412 F. Supp. at 385 (“The\nproof was legally sufficient to support a conviction in each\ninstance but the juries simply did not credit the witnesses,\nvoting 10–2 and 11–1 for acquittal.”).\n The Abbati standard is also based on the likelihood of\nany substantial difference in a subsequent trial, which the\nIngram decision also considered. See Ingram, 412 F. Supp. at\n385 (“If another trial takes place there is every reason to\nbelieve the jury will again be divided or will acquit.”).\n Finally, Rossoff and Ingram both made determinations\nsimilar to Abbati’s seventh prong, the status of the individual\nand the impact of a retrial upon the defendant in terms of\nuntoward hardship and unfairness. 483 A.2d at 422; see\nIngram, 412 F. Supp. at 385–86 (“Here is a man in jail now\nmore than seven months primarily because of an offense\nwhich the Government is unable to convince a jury he\ncommitted. . . . To permit a retrial, after 21 of 24 jurors have\nalready refused to convict, is to ignore the reasonable doubt\nstandard.”); Rossoff, 806 F. Supp. at 203 (“Dr. Rossoff is 71\nyears of age and in poor health. He has had heart surgery,\nsuffers from severe anemia and at the time of the second trial\nwas on experimental treatment. He has been under great\nphysical and emotional strain as the result of these repeated\ntrials and was even hospitalized immediately following the\nsecond trial.”).\n\n 8", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360366/", "author_raw": "McKEE, Circuit Judge, concurring"}, {"author": "NYGAARD, Circuit Judge, dissenting", "type": "dissent", "text": "NYGAARD, Circuit Judge, dissenting\n\n This appeal presents us with two issues: First, does a\ndistrict court possess the inherent power to dismiss an\nindictment after serial hung juries, and second, did the\nDistrict Court here abuse its discretion by dismissing this\nindictment after two of them. I answer yes to the first and no\nto the second. Because I view this to be a matter of\nsubstantial importance, I must respectfully dissent.1\n\n As the majority notes, twice now, the Government has\ntried Raymont Wright for a violation of federal law: being a\nfelon in possession of a firearm.2 Twice now, the\nGovernment has done so on the basis of essentially the same\nevidence at trials presided over by the same District Court.\nAnd twice now, two different juries could not reach a verdict.\nThus, when the Government announced its intention to put\nWright on trial for the third time, the District Court was\nskeptical. It asked for briefing on whether it possessed the\ninherent power to prohibit the Government from taking a\nthird turn, and if it did, whether the court should use that\n\n\n\n\n1\n Whether the District Court had the inherent power to\ndismiss the indictment is a legal question. We employ a\nplenary standard of review to that issue. See United States v.\nSchiff, 602 F.3d 152, 161 (3d Cir. 2010) (citing United States\nv. Scott, 223 F.3d 208, 210 (3d Cir. 2000)). Whether the\nDistrict Court appropriately exercised this power is reviewed\nfor an abuse of discretion. Link v. Wabash R.R. Co., 370 U.S.\n626, 633 (1962).\n2\n See 18 U.S.C. § 922(g).\n\n\n\n\n 1\n\npower.3 After hearing from both sides, the District Court\nconcluded that its inherent power applied to this\ncircumstance. It then exercised its discretion to dismiss the\nindictment.\n\n Neither the Government nor the majority disputes that\ndistrict courts have the inherent authority to dismiss\nindictments under at least some circumstances. Citing to\nUnited States v. Hasting,4 however, the majority cabins that\nauthority to those instances in which there is evidence of\nprosecutorial misconduct. In my view, in so doing, the\nmajority conflates and confuses the various powers of the\ncourt. And it also hobbles the court’s discretion to probe the\nimpact on the fair administration of justice of those\nprosecutorial decisions that sit outside the definition of bad\nconduct but still pose—or threaten to pose—real institutional\nharm.\n\n The executive office inheres prosecutors with the\npower to bring a case to trial. The judicial office, on the other\nhand, inheres the court with the power to end a case.5 Both\n\n3\n The District Court ordered the parties to “file cross briefs\nstating their position regarding whether the Court, through an\nexercise of its inherent authority, should prohibit or permit a\nsecond re-trial in this case.” United States v. Wright, No. 14-\ncr-292, 2017 WL 1179006, at *1 (W.D. Pa. 2017).\n4\n 461 U.S. 499, 505 (1983).\n5\n See Young v. U.S. ex rel. Vuitton et Fils S.A., 481 U.S. 787,\n816 (1987)(Scalia, J. concurring)(“The judicial power is the\npower to decide, in accordance with law, who should prevail\nin a case or controversy. See Art. III, § 2. . . . [S]ince the\nprosecution of law violators is part of the implementation of\n\n\n\n\n 2\n\noffices share a responsibility to safeguard the overall integrity\nof the judicial process. But when a prosecutor decides to\nproceed with another trial in the aftermath of multiple\nmistrials, who but the court is empowered to question the\nimpact of the prosecutor’s discretion on the fair\nadministration of justice, particularly when the court has\nconcerns that the proceedings—and the institution—will be\ntainted by the abuse of jury shopping? It could be argued that\ntwo mistrials may not in some instances be enough to inflict\nserious institutional damage. But, the majority’s combined\nreliance on Dietz v. Bouldin6 and Fed. R. Crim. P. 31(b)(3) to\nallow the prosecutor to bring an unlimited number of retrials,\nso long as she or he does not stray into the realm of “illegal\nconduct,” provides the prosecutor with an unchecked power.\nThis poses a threat to the integrity of the judiciary and\ncontradicts the inherent responsibility and authority vested in\nthe judiciary by the framers of the Constitution. Thus, it is\nthe majority’s decision—and not the District Court’s exercise\nof its inherent authority—that violates the separation of\npower principles on which the majority relies. We must\naffirm that our trial court judges have the discretion,\noriginating in the court’s inherent power, to take proper\naction when warranted to protect the institutional integrity of\nthe judiciary.\n\n Here, the District Court mindfully struck the balance\nthat is necessary anytime the power of the court and the\npower of the prosecutor intersect. Drawing from factors set\n\n\nthe laws, it is—at least to the extent that it is publicly\nexercised—executive power, vested by the Constitution in the\nPresident.”) (footnote omitted)).\n6\n 136 S. Ct. 1885, 1892 (2016).\n\n\n\n\n 3\n\nout in State v. Abbati,7 the District Court identified and\ninvestigated a circumstance that it identified as harmful to the\ninstitution and to the defendant: jury shopping. It also took\nnote of the impact of serial retrials on the defendant. It then\nproperly dismissed the indictment. Its use of the court’s\ninherent discretion did not violate the separation of powers\ndoctrine. To the contrary, it gave definition and substance to\nit.\n\n I.\n\n Some review is appropriate to illuminate how and\npossibly why I believe the majority confuses the court’s\nvarious powers.\n\n A.\n\n Federal courts operate within a constitutional system\nthat enumerates the powers of each branch of government, as\nset forth in the founding document. Article I restrains\ncongressional power to those “legislative Powers granted\nherein.”8 By comparison, Article II vests the President with\n“the executive Power” without further description, limitation,\nor restriction.9 Analogous to Article II, Article III conveys\nwithout restriction or limitation the “judicial Power” to\nfederal courts.10 Accordingly, the Supreme Court has—since\nat least 1812—recognized that “[c]ertain implied powers must\nnecessarily result to our Courts of justice from the nature of\n\n7\n 493 A.2d 513, 521-22 (N.J. 1985).\n8\n U.S. Const. art. I, § 1.\n9\n U.S. Const. art. II, § 1.\n10\n U.S. Const. art. III, § 1.\n\n\n\n\n 4\n\ntheir institution.”11 “The moment the courts of the United\nStates were called into existence and invested with\njurisdiction over any subject, they became possessed of”\ninherent authority.12\n\n Moreover, two bedrock purposes of the Constitution—\nchecking the actions of the states and ensuring that Congress\nand the Executive do not overstep their boundaries—require a\nfederal judiciary that exercises its own independent judicial\npower. That is, it would be impossible for federal courts to\ndischarge these vital duties if they lacked some inherent\npower beyond the reach of the Executive or the legislature. I\nthink of it this way: the elaborate measures set out in the\nConstitution to protect the independence of the judiciary (life\ntenure, removal from office only through impeachment, no\ndecrease in salary during a judge’s tenure, for example)\nwould be meaningless if there were not some inherent,\nunimpeachable power vested solely in the federal courts.\n\n In Eash v. Riggins Trucking Inc.,13 we defined inherent\npower as vesting in federal courts upon their creation and as\nnot deriving from any statute. In this sense, the “judicial\npower” given to the federal courts by Article III of the\nConstitution is the “power to decide, in accordance with law,\nwho should prevail in a case or controversy.”14 No matter the\ndescription, this power is intrinsic to the judicial office and\ncannot be inhibited by any rule or act of Congress. As we\n\n11\n United States v. Hudson, 11 U.S. (7 Cranch) 32, 34 (1812).\n12\n Ex parte Robinson, 86 U.S. 505, 510 (1873) (speaking of\nthe inherent contempt power).\n13\n 757 F.2d 557, 561 (3d Cir. 1985) (en banc).\n14\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n\n\n\n\n 5\n\nhave recognized, the boundaries of this power are often\n“nebulous” and “shadowy,”15 and “it is not always possible to\ncategorize inherent power.”16 Yet, we have an outline.\n\n In Eash, we identified three main classes or categories\nof inherent power: 1) inherent powers based in Article III,\nthat is, the power of a lower federal court to decide a case\nover which it has jurisdiction; 2) those powers “necessary to\nthe exercise of all others,”17 and 3) powers that include those\nreasonably useful to achieve justice, which are “necessary\nonly in the practical sense of being useful.”18 Focusing on the\nfirst category, the inherent power to decide a case is “so\nfundamental to the essence of a court as a constitutional\ntribunal that to divest the court of absolute command within\nthis sphere is really to render practically meaningless the\nterms ‘court’ and ‘judicial power.’”19 In other words, powers\n\n\n15\n Eash, 757 F.2d at 561 (citation omitted).\n16\n Id. at 562.\n17\n Id. (quoting Roadway Express, Inc., v. Piper, 447 U.S. 752,\n764 (1980)).\n18\n Id. at 563; see also Am. Civil Liberties Union v. Holder,\n673 F.3d 245, 255-56 (4th Cir. 2011) (applying Eash factors);\nIn re Stone, 986 F.2d 898, 901-02 (5th Cir. 1993) (per\ncuriam) (adopting Eash factors). In Chambers v. NASCO\nInc., the Supreme Court was urged to adopt our approach to\ninherent powers. But the Court held that it “ha[d] never so\nclassified the inherent powers and . . . ha[d] no need to do so\nnow.” 501 U.S. 32, 47 n.12 (1991).\n19\n Eash, 757 F.2d at 562. The third aspect of a court’s\ninherent power is its authority to employ persons or\ninstruments not connected with the court, such as experts and\n\n\n\n\n 6\n\nin this category make a court a court; they are encoded into\nthe judiciary’s DNA. Courts have referred to this power as a\ncourt’s “irreducible inherent authority”20 and “the core Article\nIII power.”21 It is nothing less than our ability to decide a\ncase over which we have jurisdiction, without interference by\nCongress or the Executive.22\n\n Drawing from this, when I refer to a district court’s\ninherent power, I mean a ‘“[c]ertain implied power[] [that]\nmust necessarily result to our Courts of justice from the\nnature of their institution,’ [a] power[] ‘which cannot be\ndispensed with in a Court, because they are necessary to the\nexercise of all others.’”23 It is “grounded in the separation of\npowers concept,” since to deny it and yet maintain an\nindependent judiciary “is a self-contradiction.”24\n\n However, that is not to say that the court operates\nsolely outside the realm of legislatively granted judicial\n\n\nauditors, to assist in its decision-making function. This facet\nof inherent power is not in play here.\n20\n Id.\n21\n Am. Civil Liberties Union v. Holder, 673 F.3d at 256.\n22\n United States v. Klein, 80 U.S. (13 Wall.) 128, 147 (1871),\nEash, 757 F.2d at 562 (noting that courts may exercise this\ntype of inherent power despite legislation to the contrary); see\nalso Michaelson v. United States ex rel. Chicago, St. P., M. &\nO. Ry. Co., 266 U.S. 42, 64 (1924) (acknowledging that the\nConstitution vests courts with some powers unalterable by\nlegislation).\n23\n Chambers, 501 U.S. at 43 (quoting Hudson, 11 U.S. (7\nCranch) at 34.).\n24\n Eash, 757 F.2d at 562.\n\n\n\n\n 7\n\npowers.25 In fact, the categorization scheme in Eash was\nintended largely as a means of explaining the relationship\nbetween inherent judicial powers and legislatively granted\njudicial powers.26 It is here that I believe the majority’s\nanalysis strays.\n\n B.\n\n The majority, the briefs, and the discussion at oral\nargument reveal what has become a commonplace but\nimprecise conflation of the terms “inherent power” and\n“supervisory power.”27 The Government, while referencing\nthe District Court’s “inherent power,” also referred to the\ncourt’s “supervisory power,” and its “inherent supervisory\njudicial authority.”28 The Appellee covers the entire panoply,\nciting the District Court’s “supervisory authority,” its\n\n\n25\n See Hudson, 11 U.S. (7 Cranch) at 33.\n26\n See In re Tutu Wells Contamination Litig., 120 F.3d 368,\n384 n.14 (3d Cir. 1997), overruled on other grounds by\nCunningham v. Hamilton County, Ohio, 527 U.S. 198 (1999).\n27\n In Eash, we noted that “[t]he conceptual and definitional\nproblems regarding inherent power . . . have bedeviled\ncommentators for years,” 757 F.2d at 561, and that “those\ncases that have employed inherent power appear to use that\ngeneric term to describe several distinguishable court\npowers,” id. at 562. We also noted that “this lack of\nspecificity [has been compounded by courts] rel[ying] . . . on\nprecedents involving one form of power to support the court’s\nuse of another.” Id.\n28\n E.g., Appellant’s Br. at 13, 16; Appellant’s Reply Br. at 2,\n14.\n\n\n\n\n 8\n\n“supervisory power,” and its “inherent power.”29 At times,\nwe too have been guilty of adding to the confusion.30 The\nerroneous interchangeability of these terms clouds an\nimportant distinction that is crucial to this appeal: the\ndifference between inherent judicial powers and legislatively\ngranted judicial powers.31 As noted supra, inherent “judicial\npower” is given to the federal courts by Article III of the\nConstitution.32 Through this grant, federal courts receive the\n“power to decide, in accordance with law, who should prevail\nin a case or controversy.”33 The merging of the terms\n“inherent” and “supervisory” likely has its genesis in the fact\nthat some inherent powers are supervisory in function, such\nas a federal court’s inherent power “to supervise the\nadministration of criminal justice.”34\n\n29\n E.g., Appellee’s Br. at 22, 26.\n30\n See, e.g., United States v. Accetturo, 783 F.2d 382, 396 (3d\nCir. 1986) (Sloviter, J., dissenting) (speaking of our “inherent\nsupervisory power”); see also United States v. Watkins, 339\nF.3d 167, 180 (3d Cir. 2003) (Nygaard, J., concurring)\n(referring to both a court’s supervisory power and inherent\npower to dismiss a case under Fed. R. Crim. P. 48(b)).\n31\n In re Tutu Wells Litig., 120 F.3d at 384 n. 14.\n32\n See U.S. Const. art. III, § 1.\n33\n Young, 481 U.S. at 816 (Scalia, J., concurring).\n34\n United States v. Payner, 447 U.S. 727, 735 n.7 (1980)\n(quotation marks omitted); see also Sara Sun Beale,\nReconsidering Supervisory Power in Criminal Cases;\nConstitutional and Statutory Limits of the Federal Courts, 84\nColum. L. Rev. 1433, 1433-34, 1465, 1470 (1984)\n(identification of Article III “judicial power,” not\ncongressional acts, as the source of the Supreme Court’s\nsupervisory authority).\n\n\n\n\n 9\n\n However, unlike inherent powers, a court’s\nsupervisory authority may come from, and can be limited by,\nacts of Congress or a court’s own rules.35 Supervisory power\noften speaks to the power “to mandate ‘procedures deemed\ndesirable from the viewpoint of sound judicial practice.’”36 A\ncourt’s use of supervisory power can usually be classified in\none of three ways. First, supervisory power can refer to an\nappellate court’s supervision of a district court, through the\nimposition of procedures in addition to those already imposed\nby federal statute or constitutional provision.37 We have, for\nexample, relied on our supervisory power over district courts\nto review the application of local rules of practice and\nprocedure.38 We have also used our supervisory power to\n\n\n\n\n35\n See, e.g., McNabb v. United States, 318 U.S. 332, 340-41\n(1943); Hasting, 461 U.S. at 505.\n36\n United States v. Moreno, 809 F.3d 766, 780 (3d Cir. 2016)\n(quoting Thomas v. Arn, 474 U.S. 140, 146-47 (1985)).\n37\n See, e.g., Castro v. United States, 540 U.S. 375, 384 (2003)\n(instructing district courts to notify pro se litigants about\nconsequences of re-characterizing motions as ones seeking\nrelief under 28 U.S.C. § 2255); Thiel v. S. Pac. Co., 328 U.S.\n217, 225 (1946) (announcing a new rule for the composition\nof federal juries); Dunbar v. Triangle Lumber & Supply Co.,\n816 F.2d 126, 129 (3d Cir. 1987) (prescribing procedures for\nmotions to dismiss based on the conduct of a litigant’s\ncounsel); United States v. Bazzano, 570 F.2d 1120, 1137-38\n(3d Cir. 1977) (requiring district courts to state reasons for a\ncriminal sentence).\n38\n See United States v. Wecht, 484 F.3d 194, 204-05 (3d Cir.\n2007).\n\n\n\n\n 10\n\nprohibit certain jury instructions in the district courts39 and to\nreview attorney-client fee arrangements.40 Second, Courts—\nboth trial and appellate—also refer to their “supervisory\npower” when meaning their power to supervise pending\nlitigation.41 They can, for example, seal and unseal records,42\nreassign a case to a different judge on remand,43 or disqualify\nan attorney on ethical grounds.44 Lastly, the power of a\nfederal court to supervise law enforcement officials can also\nbe what a court intends when it speaks of its “supervisory\n\n\n\n\n39\n See United States v. E. Med. Billing Inc., 230 F.3d 600,\n607-12 (3d Cir. 2000).\n40\n See Ryan v. Butera, Beausang, Cohen & Brennan, 193 F.3d\n210, 214 (3d Cir. 1999).\n41\n See, e.g., Carlisle v. United States, 517 U.S. 416, 425-26\n(1996) (acknowledging “supervisory power” of district courts\nover litigation before them).\n42\n See, e.g., Hagestad v. Tragesser, 49 F.3d 1430, 1434 (9th\nCir. 1995).\n43\n See Gov’t of the Virgin Islands v. Walker, 261 F.3d 370,\n376 (3d Cir. 2001) (noting that, “[a]lthough it is the standard\npractice in the district courts and in this circuit that a case on\nremand is assigned to the judge who originally heard it, we\ncan, in the exercise of our supervisory power, reassign this\ncase to a different judge upon remand.”) (quotation marks\nomitted).\n44\n In re Grand Jury Investigation, 447 F. Supp. 2d 453, 456-\n57 (E.D. Pa. 2006) (collecting cases); see also United States\nv. Moreno, 809 F.3d at 780 (summarizing supervisory\nauthority).\n\n\n\n\n 11\n\npower.”45 These powers broadly ensure that pending cases\nare managed uniformly and efficiently.\n\n I concede that the boundary between supervisory\nauthority that is inherent to the court and that which is granted\nby the legislature can, at times, be difficult to identify.\nHowever, these difficulties are irrelevant to this case because\nI conclude that the District Court here acted pursuant to its\ninherent power and not to any authority conferred by any\nstatute or rule. The District Court’s action was not\nundertaken in supervision of pending litigation—two trials\nwere already concluded and a potential third trial had not yet\nbegun. Nor was it exercised according to a rule of procedure\nor practice newly announced by an appellate tribunal.\nMoreover, its action was not a response to any prosecutorial\nmisconduct or request from Wright to dismiss the indictment.\nThere is simply no basis to conclude that the inherent power\nthat the District Court exercised in this case derived from any\nlegislative grant.\n\n To the contrary, the specific power under review here\nis the power to dismiss an indictment after two mistrials\nbecause of deadlocked juries in each instance. This power\nfalls within Eash’s first category of power because it is an\ninherent power to resolve a case. A court, by its nature, must\nbe able to dismiss with prejudice actions brought before it,\njust as it must have the power to decide cases and enter\n\n45\n See, e.g., United States v. Thompson, 772 F.3d 752, 763 (3d\nCir. 2014). For a comprehensive discussion of the origins\nand uses of supervisory power, see Amy Coney Barrett, The\nSupervisory Power of the Supreme Court, 106 Colum. L. Rev.\n324, 330 (2006).\n\n\n\n\n 12\n\njudgments.46 Such exercises of power are fundamental to the\nessence of a court. Were they not, the judicial system simply\ncould not function.47\n\n The inherent power to dismiss is “of ancient origin,\nhaving its roots in judgments of nonsuit and non prosequitur\nentered at common law,” and so is a power that is part of the\nvery nature of the judicial institution.48 It is incidental and\nnecessary to the fair and efficient operation of the courts.49\nIndeed, “the power to dismiss exists in many situations. For\nexample, a district court has the inherent power to dismiss sua\nsponte for lack of jurisdiction, or under the doctrine of forum\nnon conveniens.”50 Because the power to resolve a case by\ndismissing an indictment (in a criminal action) or a complaint\n(in a civil action) is fundamental to the essence of a court of\njustice, it cannot be interfered with. Indeed, as two\ncommentators have explained, “McNabb, other Supreme\n\n46\n We have also noted that our power to remand is a subset of\nthe inherent power to dismiss a case. See Bradgate Assocs.,\nInc. v. Fellows, Read & Assocs., Inc., 999 F.2d. 745, 750 n.4\n(3d Cir. 1993).\n47\n See, e.g., Fitzgerald v. First E. Seventh St. Tenants Corp.,\n221 F.3d 362, 363-364 (2d Cir. 2000) (holding a district court\nhas the inherent power to dismiss a case, sua sponte, if it\ndetermines that the action is frivolous or the court lacks\njurisdiction over the matter).\n48\n Link, 370 U.S. at 630.\n49\n See, e.g., Bowers v. Nat’l Collegiate Athletic Ass’n, 564 F.\nSupp. 2d 322, 333 (D.N.J. 2008) (citing Derzack v. County of\nAllegheny, 173 F.R.D. 400, 411 (W.D. Pa. 1996), aff’d\nwithout op., 118 F.3d 1575 (3d Cir. 1997)).\n50\n In re Prevot, 59 F.3d 556, 565-66 (6th Cir. 1995).\n\n\n\n\n 13\n\nCourt cases, and an analysis of several lower court opinions\naddressing this precise issue should sufficiently dispel any\nnotion that the federal courts lack the power to bar repeated\nattempts to obtain a conviction” following serial mistrials.51\nThus, the District Court’s action here was well within the\nboundaries of its inherent power.\n\n Therefore, the majority’s conclusion that “inherent\nauthority,” “supervisory power,” and “supervisory authority”\nall refer to the same thing (while understandable given the\nrampant muddled references that persist) ultimately misses\nthe point. The power at issue here is the inherent power of\nthe court to decide a case: a power that is limited by the\nboundaries of reason and discretion and is subject to appellate\nreview for abuse. It is not subject to the power of Congress\nor the Executive.\n\n II.\n\n There is no dispute that district courts have the\ninherent power to dismiss indictments in at least some\ncircumstance. The majority nevertheless concludes that the\nDistrict Court lacked the power to do so in this case. The\nmajority reaches that conclusion for three principal reasons,\nbut none withstands scrutiny.\n\n A.\n\n51\n Michael A. Berch & Rebecca White Berch, The Power of\nthe Judiciary to Dismiss Criminal Charges After Several\nHung Juries: A Proposed Rule to Control Judicial Discretion,\n30 Loy. L.A. L. Rev. 535, 543 & nn. 42-43 (1997) (collecting\ncases).\n\n\n\n\n 14\n\n First, the majority agrees with the Government’s\nargument that the District Court’s dismissal violated the\nSeparation of Powers Doctrine. I agree that the District\nCourt’s dismissal implicates the separation of powers. But its\nactions were in furtherance—not in violation—of the\ndoctrine. The separation of powers doctrine refers to the\nbalance among the branches of Government which prevents\none branch from disrupting the constitutional functions of\nanother.52\n\n Here, the majority concludes that, in dismissing the\nindictment after two hung juries, the District Court\nencroached on the independence of the Executive because it\nprohibited the prosecution from exercising its constitutional\nduty to enforce the laws of the United States. Certainly, the\nUnited States Attorney, as a member of the Executive Branch,\nhas such a responsibility.53 And, just as certainly, the\ndecision to prosecute “is soundly within the discretion of the\nprosecutor, not the courts.”54 The Government’s authority\nnot to prosecute a case is clear as well.55 But we see no sign\nthat the District Court did anything to prevent the\nGovernment from fulfilling its duty. To the contrary, the\nGovernment was twice given a full and fair opportunity to\n\n52\n See, e.g., Clinton v. Jones, 520 U.S. 681, 699-700 (1997);\nMorrison v. Olson, 487 U.S. 654, 696 (1988); Nixon v. Adm’r\nof Gen. Servs., 433 U.S. 425, 442-43 (1977); Baraka v.\nMcGreevey, 481 F.3d 187, 201 (3d Cir. 2007).\n53\n See, e.g., In re Grand Jury, 286 F.3d 153, 163 (3d Cir.\n2002).\n54\n United States v. Talley, 164 F.3d 989, 997 (6th Cir. 1999).\n55\n See, e.g., United States v. Quinn, 728 F.3d 243, 255-56 (3d\nCir. 2013).\n\n\n\n\n 15\n\npresent its case and makes no claim that the District Court\never prevented it from doing so. Having had those\nopportunities, the Government had no absolute right as a\nmatter of separation of powers or otherwise to try again. As\ntwo commentators have explained, a district court’s use of its\ninherent power to dismiss an indictment after serial mistrials\ndoes not raise “significant separation of powers concerns”\nbecause the nature of that inherent power means that federal\ncourts “need not automatically defer to a prosecutor’s\ndecision to retry a defendant” in this situation.56\n\n The majority nevertheless concludes that prosecutors\nhave the unimpeded right to try persons for violating federal\nlaw based on an indictment as many times as they wish and\nthat the separation of powers doctrine prohibits a federal court\nfrom interfering. This position is untenable because it is not a\ntrue reflection of the separation of powers. It is axiomatic\nthat no one branch of government is completely divorced\nfrom the other two. In reality, “our constitutional system\nimposes on the Branches a degree of overlapping\nresponsibility, a duty of interdependence as well as\nindependence.”57 This overlap becomes problematic, of\ncourse, when it results in an encroachment (when an action of\none branch might undermine the independence of another\nbranch) or an aggrandizement (where one branch seeks\n“powers more appropriately diffused among separate\nBranches”).58\n\n\n56\n Berch & Berch, supra note 51, at 544.\n57\n Mistretta v. United States, 488 U.S. 361, 381 (1989).\n58\n Id. at 381; see also In re Tribune Media Co., 799 F.3d 272,\n285 (3d Cir. 2015) (Ambro, J., concurring).\n\n\n\n\n 16\n\n But recognizing a district court’s right to prohibit a\nretrial following serial mistrials does not implicate these\nconcerns. To the contrary, and putting the shoe on the other\nfoot, the Government’s position that nothing limits its\nopportunity to try and retry a defendant as many times as it\nchooses violates the judicial branch’s constitutional mandate\nto exercise its judicial power. Just as the filing of an\nindictment is an exercise of executive power, the dismissal of\none is an exercise of judicial power. The unlimited serial\nprosecutions that the Government advocates for, and that the\nmajority permits, would limit a court’s authority to dismiss an\nindictment to only those instances in which the prosecutor\nsteps outside the bounds of professional conduct. But our\nindependence as an institution of government must include an\nability to adjudicate, and thus dismiss with prejudice,\nindividual cases when a district court, in its discretion, has\nconcerns about the impact of serial retrials on the institution\nand the defendant. We view the prosecution of a defendant\nafter deadlocked juries as a tipping point in balancing the\nseparation of powers. As the repeated prosecutions increase,\nso too does the judiciary’s power to limit them. As we stated\nin Eash, and as we said supra, a court’s exercise of its\ninherent power to dismiss an indictment after retrials does not\nviolate the separation of powers but is grounded in it.59\n\n B.\n\n Second, and relatedly, the majority concludes that the\nDistrict Court’s dismissal was in violation of Fed. R. Crim. P.\n31(b)(3), which the majority claims confers on prosecutors\nthe unlimited discretion to retry defendants following serial\n\n59\n See Eash, 757 F.2d at 562.\n\n\n\n\n 17\n\nmistrials. Rule 31 does nothing of the kind. Rule 31 provides\nin relevant part that “if a jury cannot agree on a verdict on one\nor more counts, the court may declare a mistrial on those\ncounts. The government may retry any defendant on any\ncounts on which the jury could not agree.”60 The Supreme\nCourt adopted this rule in its original form in 1944 as a\n“restatement of existing law.”61 The Supreme Court itself\nappears never to have cited Rule 31(b)(3), and neither the few\nCourts of Appeals to have done so62 nor its Advisory\nCommittee Notes have discussed its history or purpose in any\ndetail. Arguably, the rule’s reference to the prosecutor’s\ngeneral ability to retry a defendant following a mistrial may\nbe nothing more than a recognition of the longstanding\nprinciple that retrials following mistrials are not prohibited by\nthe Double Jeopardy Clause,63 which is not at issue here.\n\n In any event, this rule does not by its terms prohibit\ndistrict courts from dismissing indictments following serial\nmistrials. District courts have the inherent power to do so as\nexplained above. A district court’s exercise of that power\ncould be contrary to Rule 31(b)(3) only if the rule contained\nan “express grant of or limitation on” that power.64 It does\nnot. The rule does not mandate a retrial after a mistrial. Nor\n\n60\n Fed. R. Crim. P. 31(b)(3).\n61\n Id. advisory committee’s note to 1944 adoption.\n62\n See United States v. Melendez, 775 F.3d 50, 57 (1st Cir.\n2014); United States v. Warren, 593 F.3d 540, 546 (7th Cir.\n2010); United States v. Fort, 472 F.3d 1106, 1111 n.3 (9th\nCir. 2007); United States v. Gotti, 451 F.3d 133, 137 (2d Cir.\n2006).\n63\n See United States v. Perez, 22 U.S. 579, 580 (1824).\n64\n Dietz, 136 S. Ct. at 1892.\n\n\n\n\n 18\n\ndoes it contain any other limitation on the district court’s\npower to prohibit one. In fact, the rule does not even mention\nthat issue.65 Thus, as the Supreme Court has noted in\naddressing other rules of court, “[i]t would require a much\nclearer expression of purpose than [this rule] provides for us\nto assume that it was intended to abrogate” the district courts’\ninherent power.66 Put simply, when there have been multiple\nmistrials and the prosecutor seeks to try the case again, Rule\n31(b)(3) does not purport to reduce the role of the district\ncourts to that of a rubber stamp.\n\n C.\n\n Finally, the majority claims that a district court can\nexercise its inherent power to dismiss an indictment only if\nthere is evidence of willful bad faith or prosecutorial\nmisconduct on the part of the government and resultant\nprejudice to the defendant. It cites to numerous decisions that\nit says supports this position.67 But none of these cases deals\n\n65\n The majority claims that Rule 31(b)(3)’s silence on this\nissue supports the proposition that district courts lack the\nauthority to dismiss an indictment following serial mistrials.\nBut because district courts have the inherent power to do so\nas explained above, the question is not whether Rule 31(b)(3)\npermits district courts to dismiss an indictment in that\ncircumstance. The question instead is whether Rule 31(b)(3)\nprohibits them from doing so. It does not.\n66\n Link, 370 U.S. at 631-32.\n67\n See Bank of Nova Scotia v. United States, 487 U.S. 250,\n254-56, 263 (1988); United States v. Chapman, 524 F.3d\n1073, 1087 (9th Cir. 2008); United States v. Goodson, 204\nF.3d 508, 514 (4th Cir. 2000); United States v. Derrick, 163\n\n\n\n\n 19\n\nwith the particular circumstance we face here: the decision to\nretry a defendant after serial mistrials.68 In fact, many are\ndismissals due to prosecutorial misconduct. The majority’s\nreliance on such decisions is misplaced because it ignores the\nfact that the dismissal in this case was not punitive in nature;\nit was not a sanction for misconduct.69 As two commentators\nhave explained, “[a]lthough the inherent power principle has\nusually involved cases of misconduct by the parties or a\nvindication of statutory principles, the doctrine is not so\nlimited.”70 To the contrary, courts may use their inherent\nauthority to dismiss indictments whenever necessary to\nvindicate “principles of fairness to the defendant and the\ninterests of the public in the effective administration of\njustice.”71\n\n That is just what the District Court did here. The\nGovernment asked the District Court to dismiss without\nprejudice “[e]ven if this court were inclined to dismiss the\ncase.”72 Yet the Government proffered no additional\n\n\nF.3d 799, 808 (4th Cir. 1998); United States v. Tucker, 8 F.3d\n673, 674 (9th Cir. 1993) (en banc); United States v. Van\nEngel, 15 F.3d 623, 631-32 (7th Cir. 1993); United States v.\nSantana, 6 F.3d 1, 11 (1st Cir. 1993); United States v. Isgro,\n974 F.2d 1091, 1094 (9th Cir. 1992).\n68\n Derrick does deal with a dismissal of the indictment after\nan initial grant of a retrial, but the circumstance differs from\nthis case because the mistrials were not due to deadlocked\nverdicts. See 163 F.3d at 803\n69\n Cf., e.g., Isgro, 974 F.2d at 1097.\n70\n Berch & Berch, supra note 51, at 548.\n71\n Id.\n72\n Wright, 2017 WL 1179006, at *7.\n\n\n\n\n 20\n\nevidence it would present if Wright was re-indicted. It asked\nto try the same case again before a third jury, merely hoping\nfor a different result. The District Court’s dismissal of the\nindictment with prejudice was based on the merits, or lack\nthereof, of the Government’s request, no more and no less.\n\n Moreover, the dismissal was not, as the majority\ncontends, a general declaration of unfairness simply because\nthe government failed to obtain a conviction.73 Nor was it\nmerely an attempt to shield the defendant from the anxiety of\na retrial.74 Reference to Miller and Shepherd misconstrues\nnot only the circumstance of this case, but also the gravity of\nthe District Court’s concern. As I discuss next, the District\nCourt weighed many factors, mindful of the importance of\neach, before making its decision. From all of this—even\ntaking into account the separation of powers and Rule\n31(b)(3)—it is evident to me that the District Court correctly\nconcluded it had the inherent authority to act upon the\nprosecutor’s decision to retry this case in the wake of two\nmistrials.75\n\n73\n See United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\n74\n See United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975); see also Arizona v. Washington, 434 U.S. 497, 503-04\n(1978).\n75\n Although we conclude that the District Court appropriately\nexercised its inherent power as a court of law to dismiss an\nindictment, thus placing its actions within Eash’s first\ncategory, the District Court appeared at one point to tether its\ndismissal to its “inherent authority to effectuate . . . the\nspeedy and orderly administration of justice and to ensure\nfundamental fairness.” Wright, 2017 WL 1179006, at *2.\nThese actions are typically associated with the second\n\n\n\n\n 21\n\n III.\n\n Before moving to the actual merits of the District\nCourt’s decision, a word of caution is in order. Just because a\ncourt has inherent power to dismiss an indictment after a\nretrial does not mean it should always be exercised.76 My\ndissenting opinion today should not be interpreted as an\nendorsement of unchecked and ungrounded judicial power.\nNor should it be interpreted as permitting district courts in\nthis Circuit to dismiss indictments without a significant basis\nfor doing so. Moreover, nothing in this opinion should be\nread as limiting reprosecution to two trials. Cases no doubt\nexist where a third or fourth trial on the same indictment may\nbe appropriate where the evidence so indicates. It is simply\nmy conclusion that, in some cases, and in the proper exercise\nof its discretion, a district court has the inherent power to\nprohibit continued re-prosecution by dismissing an\nindictment.\n\n IV.\n\n This is such a case. The District Court here rightly\nproceeded with the Government’s request for another trial\nwith deliberate caution. Recognizing the lack of guidance\n\n\nclassification of Eash’s powers. See Eash, 757 F.2d at 562-\n563. Nonetheless, it invoked the inherent power of the court\nand dismissed the case and it is on this basis that I conclude\nthe District Court did not reach the boundaries of its power.\n76\n See Lopez v. United States 373 U.S. 427, 440 (1963); see\nalso Chambers, 501 U.S. at 44 (“Because of their very\npotency and discretion, inherent powers must be exercised\nwith restraint and discretion.”).\n\n\n\n\n 22\n\nfrom this Court, the District Court turned to a decision of the\nSupreme Court of New Jersey. In State v. Abbati,77 that court\nlisted several factors a trial court should consider before\ndismissing an indictment after several hung juries. These\nfactors are valid inquiries and include\n\n  the number of previous mistrials and the\n outcome of the juries’ deliberations, as far as\n can be determined;\n  the character or nature of the previous trials,\n considering their length, complexity of issues,\n and similarities in evidence;\n  the probability that any subsequent trial will be\n much different from the previous ones;\n  the relative strength of the party’s case, as\n determined by the trial court;\n  the conduct of counsel during the previous\n trials.78\n\nIn considering these factors, a district court must also accord\nappropriate weight to the Government’s decision to continue\nprosecution, giving deliberate consideration to the reasons for\nthat choice.79\n\n Other considerations might include the seriousness of\nthe crimes charged, the public’s interest in the effective\nresolution of criminal charges, and the criminal defendant’s\ncircumstances, including the impact that continued\nprosecution might have on him or her and the potential for\n\n77\n 493 A.2d 513.\n78\n Id. at 521-22.\n79\n See id.\n\n\n\n\n 23\n\nunfairness or unnecessary hardship.80 The factors just\noutlined are not an exhaustive list and district courts could\nconsider other things that are reasonably useful in answering\nwhether further prosecutions after deadlocked juries should\nbe permitted. Moreover, all of these elements of inquiry\nenable the court to assess the impact that a serial retrial has on\nthe integrity of the judiciary as an institution.\n\n These avenues of inquiry make sense to me. Take\ndifferences in evidence, for example. If the evidence would\nbe different at a retrial, then there seems little chance that\ncontinued prosecution should be curtailed. If, on the other\nhand, there would be no substantial difference in evidence,\nconcern about re-prosecution is appropriate. So too the\nnumber of deadlocked juries is an important consideration.\nContinued prosecution after two, three, or even four\ndeadlocked juries could unbalance the scale. By inquiring\ninto the seriousness of the charges, a district court could\ncompare the crime being prosecuted to other cases when a\ncourt dismissed an indictment after deadlocked juries. In\nother words, a district court must make sufficient findings and\nestablish a sufficient record supporting its decision, thus\nenabling a court of appeals to accurately assess whether the\ndistrict court abused its discretion or not. That is what the\nDistrict Court did here.\n\n I see no abuse of discretion in the District Court’s\nexercise of its inherent powers. The District Court’s ruling\nwas not arbitrary and instead was based on a thorough,\ncareful, and balanced consideration of the above factors. The\nDistrict Court first acknowledged the weight of its actions\n\n80\n See id.\n\n\n\n\n 24\n\nwithin our constitutional scheme. It then found that the\nevidence suggested that the deadlock was not the result of a\nlone holdout. As to the character of the preceding trials, the\nDistrict Court noted the Government’s position that this was a\n“simple” case. It also stated that both previous trials were\n“virtual duplicates” and that counsel on both sides was the\nsame for both prosecutions. The District Court further\nobserved the lack of any allegation of jury nullification or\nbias. Instead, it found that “there is every indication that the\ntwo juries engaged in deliberations in good faith, and, despite\ntheir best efforts, were unable to reach a verdict.”\n\n The District Court also considered the strength of the\nparties’ respective cases and determined that its opinion on\nthis factor was irrelevant, given that two separate juries had\nconcluded that the Government failed to meet its burden of\nproof. It commended the professionalism and hence the\neffectiveness of counsel on all sides, which it weighted as\nfavoring disallowing any further prosecution. The District\nCourt specifically considered the seriousness of the crime\ncharged, and it noted that other courts had dismissed\nindictments when the charges were far graver.81 Lastly, the\nDistrict Court thoroughly balanced the Government’s\nauthority to prosecute against the effect of continued\nprosecution on Wright. Recognizing that Wright has been on\nbond since July of 2014, and on home detention for nearly\ntwo years, the District Court concluded that this inquiry\ntipped in his favor.\n\n81\n Wright, 2017 WL 1179006, at *6 (citing United States v.\nIngram, 412 F. Supp. 384, 385 (D.D.C. 1976); State v.\nMoriwake, 647 P.2d 705, 708 (Haw. 1982); Abbati, 493 A.2d\nat 517; and State v. Witt, 572 S.W.2d 913, 914 (Tenn. 1978)).\n\n\n\n\n 25\n\n V.\n\n In conclusion, I see no abuse of discretion in the\nDistrict Court’s careful and thorough balancing of relevant\nfactors, a balancing which led it to invoke its inherent power\nand to dismiss the Government’s indictment of Wright. For\nall of these reasons, I respectfully dissent from my esteemed\ncolleagues in the majority. I would affirm.\n\n\n\n\n 26", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360366/", "author_raw": "NYGAARD, Circuit Judge, dissenting"}]}
MCKEE
SHWARTZ
NYGAARD
1
{"MCKEE": ", Circuit", "SHWARTZ": ", Circuit", "NYGAARD": ", Circuit"}
4
0
2
1
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583113/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: United States v. Raymont Wright\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-18\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-1972\n _____________\n\n UNITED STATES OF AMERICA,\n\n Appellant\n\n v.\n\n RAYMONT WRIGHT\n\n ______________\n\n ON APPEAL FROM THE\n UNITED STATES DISTRICT COURT\nFOR THE WESTERN DISTRICT OF PENNSYLVANIA\n (D.C. No. 2-14-cr-00292-001)\n District Judge: Hon. Cathy Bissoon\n ______________\n\n Argued May 24, 2018\n ______________\n\nBefore: MCKEE, SHWARTZ, and NYGAARD, Circuit\n Judges.\n\n (Opinion Filed: January 17, 2019)\n\n ______________\n\n OPINION OF THE COURT\n ________________\n\nDonovan J. Cocas, Esq. [ARGUED]\nJane M. Datttilo, Esq.\nLaura S. Irwin, Esq.\nOffice of the United States Attorney\n700 Grant Street\nSuite 4000\nPittsburgh, PA 15219\n\n Attorney for Appellant\n\nRenee Pietropaolo, Esq. [ARGUED]\nLisa B. Freeland, Esq.\nAkin Adepoju, Esq.\nOffice of the Federal Public Defender\n1001 Liberty Avenue\n1500 Liberty Center\nPittsburgh, PA 15222\n\n Attorneys for Appellee Raymont Wright\n\nLawrence S. Lustberg, Esq. [ARGUED]\nGibbons, P.C.\nOne Gateway Center\nNewark, NJ 07102\n\n Attorney for Amicus Appellee National Association of\n Criminal Defense Lawyers\n\n\n\n\n 2\n\nSHWARTZ, Circuit Judge.\n\n The District Court barred a retrial of and dismissed the\nindictment against Defendant Raymont Wright with prejudice\nafter two juries failed to reach a verdict. The Court did so\nrelying on its inherent authority, but without finding that any\nmisconduct had occurred or that Wright would suffer any\nprejudice beyond the general anxiety and inconvenience of\nfacing a retrial. Under such circumstances, the Court lacked\nthe inherent authority to bar the retrial and dismiss the\nindictment. Therefore, we will reverse the order dismissing the\nindictment and remand for further proceedings.\n\n I\n\n In December 2014, Wright was charged with being a\nfelon in possession of a firearm, in violation of 18 U.S.C.\n§ 922(g)(1). He pleaded not guilty and proceeded to trial in\nMay 2016. The jury was unable to reach a verdict. A second\ntrial was held in March 2017, and that jury was also unable to\nreach a verdict.\n\n During both trials, the jury heard evidence from police\nofficers about Wright’s actions on July 24, 2014.1 That\nevening, five Pittsburgh Police detectives were patrolling in\ntwo unmarked cars. Detectives Kennedy, Henson, and Baker\nwere in the lead car, and Detectives Fallert and Goob were in\nthe second car. Around 8:30 p.m. (when it was still daylight),\nFallert and Goob saw a man, later identified as Wright, driving\n\n 1\n The following facts are drawn largely from the\nevidence presented at the first trial.\n\n\n\n\n 3\n\na car in the opposite direction well above the 25-mile-per-hour\nspeed limit. The detectives turned around to follow Wright,\nand Wright sped up and turned onto a loop-shaped road. The\ndetectives pursued Wright, who fled at a high speed and ran at\nleast four stop signs. The lead car lost sight of Wright shortly\nthereafter and discontinued pursuit.\n\n Officers in the lead car then noticed skid marks\nsuggesting that a car had intended but failed to make a left turn\nat the end of a street. Officers thereafter came upon Wright’s\ncar in a parking lot below. The car had gone through a fence,\nover a hillside, and into the lot. The car hit two unoccupied\nparked cars, its tires blew out, and its windows were down.\n\n Detectives Baker and Henson exited the vehicle at the\ntop of the hill and remained where Wright’s car broke through\nthe fence, and Detective Kennedy drove his car down to the\nparking lot’s entrance. Baker and Henson testified that they\nsaw Wright search around the rear passenger seat of the car,\nback out of the vehicle with a black semi-automatic handgun\nin his right hand, and try to “rack the slide,” which can insert\nor remove a round from the chamber. App. 118-19. They had\ntheir weapons drawn and told Wright to drop the gun. At first,\nWright merely stepped back, but he eventually tossed the gun\nto the side, backed away, and lied on the ground. Pittsburgh\npolice officer Elliott and his partner, who heard of the crash on\nthe radio, were the first to reach Wright, and saw him lying on\nthe ground with a handgun next to him. Henson stated that\nwhen he made it down to the parking lot, he heard Wright say\nto him, “Hey, big guy. You won this time or you won this\nround, something of that nature. He [Wright] said: You feel\nme? You won this time,” which Henson understood to mean\nthat he had just avoided a shootout or that he caught Wright\n\n\n\n\n 4\n\nafter the pursuit. App. 125. Henson subsequently took custody\nof the gun and noticed the slide lever was bent, and when he\nstraightened it, saw the gun was loaded with eight rounds, and\none in the chamber. 2\n\n At the close of the Government’s case, Wright moved\nfor a directed verdict, arguing that no reasonable juror could\nfind beyond a reasonable doubt that Wright possessed the\nfirearm. The District Court denied the motion because “the\nevidence does thus far demonstrate that a reasonable juror\ncould most certainly find the Defendant guilty of the charge in\nthis case.” App. 171. Wright did not present a case.\n\n The jury deliberated for approximately five hours and\nthen reported to the Court that it was deadlocked. After polling\nthe jurors to confirm they were deadlocked and further\ndeliberations would not bring them closer to a unanimous\nverdict, the District Court declared a mistrial.\n\n At Wright’s March 2017 retrial, the Government\npresented substantially the same evidence. The Government\nalso called Detective Kennedy and Lieutenant Palermo, who\nwere at the scene after Wright was arrested, as well as experts\nwho testified regarding the collection of DNA and fingerprint\nevidence from firearms to respond to Wright’s argument at the\nfirst trial that investigators chose not to test the gun for forensic\nevidence in an effort to cover up that they had planted the gun\nat the scene.\n\n\n 2\n The parties stipulated Wright had been convicted of a\nqualifying felony, and an ATF Special Agent testified about\nthe gun’s interstate nexus.\n\n\n\n\n 5\n\n At the close of the Government’s case, Wright again\nmoved for a judgment of acquittal, which the Court denied\nbecause “there is sufficient evidence in the record to establish\nbeyond a reasonable doubt that Mr. Wright possessed the\nfirearm in the case,” App. 650. Wright did not put on a case.\n\n The second jury deliberated for approximately three\nhours and then reported that it was hopelessly deadlocked. The\nCourt polled the jury to confirm the deadlock and then\ndismissed the jury. 3\n\n After the Government notified the Court that it intended\nto retry the case, the Court required the parties to brief\n“whether the Court, through an exercise of its inherent\nauthority, should prohibit or permit a second re-trial in this\ncase.” App. 26. After considering the parties’ arguments, the\nDistrict Court dismissed the indictment with prejudice, holding\nthat it “ha[d] the inherent authority, under some circumstances,\nto dismiss an indictment following multiple mistrials.” United\nStates v. Wright, Crim. A. No. 14-292, 2017 WL 1179006, at\n*4 (W.D. Pa. Mar. 30, 2017). It reasoned that: (1) principles\nunderlying the Double Jeopardy Clause also applied to a\ndefendant facing a retrial after multiple mistrials, id. at *1-2;\n(2) other courts had dismissed indictments in similar\n\n 3\n Wright asserted that in the first trial, jurors voted 8-4\nfor acquittal, and in the second trial, the jury was evenly split.\nThe Government asserted that in the first trial, jurors voted 7-\n5 for acquittal, and in the second trial, voted 8-4 for conviction.\nSee United States v. Wright, Crim. A. No. 14-292, 2017 WL\n1179006, at *5 (W.D. Pa. Mar. 30, 2017). While Wright does\nnot explain how he obtained these numbers, the Government\nsaid it obtained them by speaking with the jurors.\n\n\n\n\n 6\n\ncircumstances, id. at *2-3 (citing United States v. Rossoff, 806\nF. Supp. 200, 202-03 (C.D. Ill. 1992); United States v. Ingram,\n412 F. Supp. 384, 385 (D.D.C. 1976); Sivels v. State, 741\nN.E.2d 1197, 1201 (Ind. 2001); State v. Abbati, 493 A.2d 513,\n517 (N.J. 1985); State v. Moriwake, 647 P.2d 705, 712-13\n(Haw. 1982); State v. Witt, 572 S.W.2d 913, 917 (Tenn.\n1978)); (3) while Federal Rule of Criminal Procedure 31(b)(3)\nexpressly allows the Government to retry a case after a mistrial,\nnothing in the rule “limits a court’s inherent supervisory\nauthority to dismiss an indictment in the interests of\nfundamental fairness,” id. at *4; and (4) if the Court were to\nadopt the Government’s position that there are no limit to the\nnumber of times the Government can retry a defendant, it\nwould be tantamount to a “type of jury shopping” that a court\nshould not permit, id. at *4. The District Court also considered\nthe factors set forth in Abbati, 493 A.2d at 521-22, and\nconcluded that most factors supported dismissal. 4\n\n 4\n The Abbati factors are\n\n (1) the number of prior mistrials and the\n outcome of the juries’ deliberations, so far as is\n known; (2) the character of prior trials in terms\n of length, complexity, and similarity of evidence\n presented; (3) the likelihood of any substantial\n difference in a subsequent trial, if allowed;\n (4) the trial court’s own evaluation of the relative\n strength of each party’s case; and (5) the\n professional conduct and diligence of respective\n counsel, particularly of the prosecuting attorney.\n The court must also give due weight to the\n prosecutor’s decision to reprosecute, assessing\n the reasons for that decision, such as the gravity\n\n\n\n\n 7\n\n The Government appeals.\n\n II 5\n\n We review the District Court’s order dismissing the\nindictment based on the Court’s inherent power for abuse of\ndiscretion. 6 See United States v. Chapman, 524 F.3d 1073,\n\n of the criminal charges and the public’s concern\n in the effective and definitive conclusion of\n criminal prosecutions. Conversely, the court\n should accord careful consideration to the status\n of the individual defendant and the impact of a\n retrial upon the defendant in terms of untoward\n hardship and unfairness.\n\nWright, 2017 WL 1179006, at *4 (quoting Abbati, 493 A.2d\nat 521-22). For the reasons set forth herein, we would not\nadopt Abbati, but even if we were to consider the Abbati\nfactors, we would conclude that they do not support dismissal\nin this case.\n 5\n The District Court had jurisdiction pursuant to 18\nU.S.C. § 3231. We have jurisdiction pursuant to 18 U.S.C.\n§ 3731.\n 6\n The phrases “inherent power,” “inherent authority,”\n“supervisory power,” and “supervisory authority” are all used\nto describe the basis for a court action seeking to maintain the\nintegrity of the proceedings that is not directly tethered to a\nspecific rule, statute, or constitutional provision. See, e.g.,\nCarlisle v. United States, 517 U.S. 416, 426 (1996) (inherent\npower); United States v. Williams, 504 U.S. 36, 46 (1992)\n(supervisory power); Chambers v. NASCO, Inc., 501 U.S. 32,\n43 (1991) (inherent power); Bank of Nova Scotia v. United\n\n\n\n\n 8\n\n1084-88, 1090 (9th Cir. 2008) (reviewing dismissal of\nindictment for abuse of discretion); cf. Chambers v. NASCO,\nInc., 501 U.S. 32, 55 (1991) (reviewing a court’s imposition of\nsanctions under its inherent power for abuse of discretion);\nGov’t of the Virgin Islands v. Fahie, 419 F.3d 249, 258 (3d Cir.\n2005) (“A trial court’s remedy for a discovery violation under\nits supervisory powers is reviewed for abuse of discretion.”).\nA district court abuses its discretion when it makes an errant\nconclusion of law, an improper application of law to fact, or a\nclearly erroneous finding of fact. McDowell v. Phila. Hous.\nAuth., 423 F.3d 233, 238 (3d Cir. 2005).\n\n A\n\n Federal Rule of Criminal Procedure 31 allows the\nGovernment to retry a case if the court declares a mistrial after\na jury announces it is unable to reach a verdict. Specifically,\nRule 31(b)(3) provides: “[i]f the jury cannot agree on a verdict\non one or more counts, the court may declare a mistrial on\nthose counts. The government may retry any defendant on any\ncount on which the jury could not agree.” Fed. R. Crim. P.\n31(b)(3). The word “may” means that the Government has the\n\n\nStates, 487 U.S. 250, 254-56, 263 (1988) (supervisory\nauthority); United States v. Hasting, 461 U.S. 499, 505 (1983)\n(supervisory power); United States v. Payner, 447 U.S. 727,\n733-36 (1980) (supervisory power); United States v. Nobles,\n422 U.S. 225, 231 (1975) (inherent power).\n Even if we accepted the distinctions our dissenting\ncolleague has drawn between inherent judicial powers,\nlegislatively granted judicial powers, and supervisory powers,\neach category must operate within the constitutional\nframework, including the separation of powers.\n\n\n\n\n 9\n\ndiscretion to retry a case, and nothing in the rule or its\ncommentary provides or even suggests a limit on the number\nof retrials it may conduct. See United States v. Wqas Khan,\nNo. 2:10-CR-0175 KJM, 2014 WL 1330681, at *2 (E.D. Cal.\nApr. 1, 2014) (“Nothing suggests that multiple mistrials take a\ncase out of the Rule’s operation.”), appeal dismissed, No. 14-\n10218 (9th Cir. July 9, 2014). 7 Moreover, there is nothing in\n\n 7\n While Rule 31 does not limit the Government’s\nauthority to retry a case, a handful of district courts have\ndismissed indictments following a second hung jury, but those\ndecisions are not persuasive. In Ingram, the district court\ndismissed the indictment sua sponte (without any initial\nobjection by the Government) after two mistrials—in which\njurors had voted 10-2 and 11-1 for acquittal, the defendant was\njailed during the pendency of the trials, and “[t]he Government\nha[d] no new proof; it simply want[ed] another chance.” 412\nF. Supp. at 385. The court concluded that to permit a retrial\nwould be “to ignore the reasonable doubt standard,” and so\n“[t]he Court’s intervention [was] required in the interest of\njustice.” Id. at 386 (citing United States v. De Diego, 511 F.2d\n818, 824 n.8 (D.C. Cir. 1975); De Diego, 511 F.2d at 833 n.6\n(McGowan, J., dissenting)). The Ingram court, however, relied\nin part on the dissent in De Diego. Cases since Ingram have\napplied the De Diego majority’s view concerning a court’s\nlimited authority to dismiss an indictment. See, e.g., United\nStates v. Hall, 559 F.2d 1160, 1164-65 (9th Cir. 1977) (citing\nDe Diego and reversing the district court’s dismissal of the\nindictment where the district court found it would be\n“unconscionable” to retry to the defendant); United States v.\nHudson, 545 F.2d 724, 724-26 (10th Cir. 1976) (discussing De\nDiego and its dissent and holding a district court does not have\nauthority to sua sponte dismiss an indictment based on the\n\n\n\n\n 10\n\ndefendant’s poor health); United States v. Mussehl, 453 F.\nSupp. 1235, 1236 (D.N.D. 1978) (denying defendants’ motion\nto dismiss the indictment based on alleged errors at trial, and\nciting De Diego for the proposition that “[t]he duty [to\nadminister justice] encompasses the concept of review of the\nquestion whether the United States Attorney, in making his\ndecision to prosecute, complied with the law, but does not\nallow the Court to question a United States Attorney’s\njudgment decision to prosecute, when lawfully made”).\n The District Court also relied on Rossoff, where the\ncourt denied the Government’s motion to dismiss the\nindictment under Federal Rule of Criminal Procedure 48(a),\nbut still dismissed the indictment with prejudice. 806 F. Supp.\nat 202-03 (citing Ingram, 412 F. Supp. at 385-86). There had\nbeen two trials, and the Government sought to dismiss the\nindictment and refile the charges in a different judicial district.\nId. The court determined it had authority to dismiss an\nindictment with prejudice if a retrial was “against the concept\nof fundamental fairness,” id. at 202 (citing Ingram, 412 F.\nSupp. 384), and did so because, among other reasons, the\ndefendant was in poor health, was under significant strain, and\na majority of jurors at both trials found him not guilty, id. at\n203. Rossoff, however, is distinguishable from Wright’s case\nbecause in Rossoff, the Government sought to dismiss the\nindictment so that it could refile charges in a different judicial\ndistrict, which caused the court to question the Government’s\ngood faith. In Wright’s case, the District Court made no\nfinding that the Government’s desire to retry Wright was for\nan improper purpose.\n In addition, and significantly, neither Ingram nor\nRossoff addressed the doctrine of separation of powers.\nRather, each essentially relied on a general concept of fairness\n\n\n\n\n 11\n\nthe text that empowers a court to prohibit the Government from\nretrying a case. 8\n B\n\n Apparently aware that Rule 31 did not provide it with a\nbasis to preclude a retrial in these circumstances, the District\nCourt concluded that it had the inherent authority to forbid the\nretrial and dismiss the indictment. The District Court erred.\n\n The exercise of inherent authority must satisfy two\nrequirements: (1) it “must be a reasonable response to the\n\n\nto the defendant in deciding to dismiss an indictment. See\nRossoff, 806 F. Supp. at 202; Ingram, 412 F. Supp. at 385-86.\nIn this Circuit, however, “[t]he judiciary may not impose its\npersonal and private notions of ‘fairness’ on law enforcement\nofficials, but does have a limited authority to affect\nprosecutorial actions when those actions are taken in violation\nof the Constitution.” United States v. Santtini, 963 F.2d 585,\n596 (3d Cir. 1992) (citations omitted).\n 8\n Rule 31 differs from other Federal Rules of Criminal\nProcedure because it makes no mention of the court’s\nauthority. For instance, Rule 48(b) states that a court has\nauthority to dismiss an indictment “if unnecessary delay occurs\nin: (1) presenting a charge to the grand jury; (2) filing an\ninformation against a defendant; or (3) bringing a defendant to\ntrial.” Fed. R. Crim. P. 48(b). There are other Rule-based\ngrounds on which a district court could also dismiss an\nindictment, but each would be triggered by a motion, such as a\nmotion to dismiss for failure to comply with Rule 16’s\ndiscovery obligations if justice so requires, Fed. R. Crim. P.\n16(d)(2)(D), or a motion asserting a defect in the indictment,\nFed. R. Crim. P. 12(b)(3)(B).\n\n\n\n\n 12\n\nproblems and needs confronting the court’s fair administration\nof justice,” and (2) it “cannot be contrary to any express grant\nof or limitation on the district court’s power contained in a rule\nor statute.” Dietz v. Bouldin, 136 S. Ct. 1885, 1892 (2016)\n(citations and internal quotation marks omitted). We will\nexamine each of these requirements in turn.\n\n 1\n\n As to the first Dietz requirement, “[g]uided by\nconsiderations of justice, and in the exercise of supervisory\npowers, federal courts may, within limits, formulate procedural\nrules not specifically required by the Constitution or the\nCongress.” United States v. Hasting, 461 U.S. 499, 505 (1983)\n(internal quotation marks and citation omitted). Such rules\nmust be imposed (1) “to implement a remedy for violation of\nrecognized rights,” (2) “to preserve judicial integrity by\nensuring that a conviction rests on appropriate considerations\nvalidly before the jury,” and (3) “as a remedy designed to deter\nillegal conduct.” Id. (citations omitted). Thus, a court may\nexercise its inherent authority only when it is necessary to\naddress improper conduct and ensure respect for the\nproceedings.\n\n Under these principles, a court may dismiss an\nindictment based upon its inherent authority only if the\nGovernment engaged in misconduct, the defendant was\nprejudiced, and no less severe remedy was available to address\nthe prejudice. See Bank of Nova Scotia v. United States, 487\nU.S. 250, 254-56, 263 (1988); Chapman, 524 F.3d at 1087\n(stating that “[a] court may dismiss an indictment under its\nsupervisory powers only when the defendant suffers\nsubstantial prejudice and where no lesser remedial action is\n\n\n\n\n 13\n\navailable” (citations and internal quotation marks omitted));\nUnited States v. Goodson, 204 F.3d 508, 514 (4th Cir. 2000)\n(observing that “a district court may not, in the management of\nits docket, exercise its discretion to dismiss an indictment with\nprejudice, either under Rule 48(b) or under its supervisory\npower, unless the violation caused prejudice to the defendant\nor posed a substantial threat thereof” (emphasis omitted));\nUnited States v. Derrick, 163 F.3d 799, 808 (4th Cir. 1998)\n(holding that an indictment may not be dismissed for\nprosecutorial misconduct absent a showing that the misconduct\nprejudiced the defendants, and stating that “virtually every\nother circuit to consider the issue post-Hasting and Nova Scotia\nhas also held that an indictment may not be dismissed based on\nprosecutorial misconduct, absent a showing of prejudice to the\ndefendant”); United States v. Van Engel, 15 F.3d 623, 631-32\n(7th Cir. 1993) (“A federal judge is not authorized to punish\nthe misconduct of a prosecutor by letting the defendant walk,\nunless the misconduct not only violated the defendant’s rights\nbut also prejudiced his defense . . . .”); United States v. Tucker,\n8 F.3d 673, 674 (9th Cir. 1993) (“[A] federal court may not\nexercise its supervisory authority to reverse a conviction or\ndismiss an indictment absent prejudice to the defendant.”);\nUnited States v. Santana, 6 F.3d 1, 11 (1st Cir. 1993) (“[T]aken\ntogether, [United States v. ]Payner, [447 U.S. 727, 735 (1980),]\nHasting, and Bank of Nova Scotia form a trilogy admonishing\nfederal courts to refrain from using the supervisory power to\nconform executive conduct to judicially preferred norms by\ndismissing charges, absent cognizable prejudice to a particular\ndefendant.”); United States v. Isgro, 974 F.2d 1091, 1094 (9th\nCir. 1992) (“Before it may invoke this [supervisory] power [to\ndismiss an indictment], a court must first find that the\ndefendant is actually prejudiced . . . .”), amended by 43 F.3d\n1480 (9th Cir. 1994).\n\n\n\n\n 14\n\n In this case, there has been no misconduct. Indeed, the\nDistrict Court noted that the Government performed diligently\nand professionally in both trials, Wright, 2017 WL 1179006,\nat *4, and found that the evidence was sufficient to prove\nbeyond a reasonable doubt that Wright possessed the gun. The\nDistrict Court nonetheless applied its own predictions about\nwhat another jury may do when presented with the same\nevidence, emphasized the need for finality, and opined that the\neffect of prosecution on the defendant precluded a proper\nprosecution from proceeding. See id. at *5-6. Invoking its own\nnotions about the unfairness of requiring a defendant to face a\nretrial where the Government did not obtain a majority of the\njurors’ votes is an improper exercise of a court’s supervisory\npower. United States v. Miller, 4 F.3d 792, 795 (9th Cir. 1993).\nMoreover, there is no prejudice to a defendant simply because\nhe faces the anxiety and the normal stress of undergoing a trial.\nSee United States v. Shepherd, 511 F.2d 119, 123 (5th Cir.\n1975) (“[A]nxiety is present to some degree in virtually every\ncase. Something more than the normal anxiety that\naccompanies a trial is necessary to show a degree of\nprejudice.”); United States v. Clyburn, Crim. No. 89-0154\n(JHG), 1991 WL 45749, at *2 (D.D.C. Mar. 22, 1991) (“The\nonly real harm alleged is the general unfairness to these\ndefendants in having to go forward yet again with a lengthy\ntrial, in their being ‘ground down’ by the several months’ drain\non their mental, emotional, and financial resources. A lack of\nsuch fairness, however, does not alone violate due process.”).\nRather, prejudice sufficient for the District Court to intervene\nin a proper prosecution based upon its inherent authority occurs\nonly where the Government engages in actions that place a\ndefendant at a disadvantage in addressing the charges. That\nsort of prejudice is absent in this case.\n\n\n\n\n 15\n\n Unless there is some constitutional basis, such as a due\nprocess violation, it makes sense to limit a court’s authority to\nbar retrial to instances of prosecutorial misconduct and\nprejudice. First, it ensures that a judge’s personal preferences\nabout a case do not influence whether the case proceeds. See\nUnited States v. Santtini, 963 F.2d 585, 596 (3d Cir. 1992)\n(“The judiciary may not impose its personal and private\nnotions of ‘fairness’ on law enforcement officials, but does\nhave a limited authority to affect prosecutorial actions when\nthose actions are taken in violation of the Constitution.”).\nSecond, as more fully discussed below, it guarantees that a\ncourt limits the Executive’s decision to prosecute only where\nthere is a constitutionally sound reason to do so. 9 This brings\nus to the second Dietz requirement.\n\n\n 9\n For these reasons, we find unpersuasive our dissenting\ncolleague’s reliance on Eash v. Riggins Trucking Inc., 757\nF.2d 557, 562 (3d Cir. 1985) (en banc), and particularly its\nobservation that a court has the inherent power to resolve a\ncase, as authority for allowing a court dismiss an indictment\nafter successive hung juries. As a general matter, there is no\ndoubt that a court has the authority to dismiss a case, but it may\nnot simply end a case because it decides that it should not be\ntried again. Rather, as Bank of Nova Scotia, Chapman, and\ntheir progeny make clear, the court must point to evidentiary\ndeficiency, prejudicial misconduct, or a constitutional basis,\nsuch as double jeopardy or due process, to justify precluding a\nprosecution. If a court believed that the evidence was deficient,\nthe prosecutor engaged in prejudicial misconduct, or a retrial\nwould violate the constitution, then it has a basis to preclude a\nretrial. Requiring such reasons for barring a retrial ensures that\n\n\n\n\n 16\n\n 2\n\n The second Dietz requirement reminds a court that the\nexercise of its powers must be in accordance with the\nConstitution, statutes, and rules. 136 S. Ct. at 1892. Beginning\nwith the Constitution, a court must be mindful of its role in our\ntripartite form of government and the doctrine of separation of\npowers. Separation-of-powers principles limit a court’s\ninherent authority. “Regardless of whether the supervisory\npower stems from the federal courts’ inherent power to check\nintrusions by other branches of government or whether it is a\nform of specialized federal common law, the separation-of-\npowers principle imposes significant limits on it,” and\n“[p]roper regard for judicial integrity does not justify a\n‘chancellor’s foot veto’ over activities of coequal branches of\ngovernment.” United States v. Gatto, 763 F.2d 1040, 1046 (9th\nCir. 1985) (internal quotation marks omitted) (quoting United\nStates v. Russell, 411 U.S. 423, 435 (1973)).\n\n In the criminal context, the Executive Branch has\n“broad discretion as to whom to prosecute,” and this discretion\n“rests largely on the recognition that the decision to prosecute\nis particularly ill-suited to judicial review.” Wayte v. United\nStates, 470 U.S. 598, 607-08 (1985) (citation and internal\nquotation marks omitted). A court is not equipped to evaluate\n\n [s]uch factors as . . . the prosecution’s general\n deterrence value, the Government’s enforcement\n priorities, and the case’s relationship to the\n\n\nthe ruling is not based on a court’s own personal sense of\nwhether a case is worthy of prosecution.\n\n\n\n\n 17\n\n Government’s overall enforcement plan . . . .\n Judicial supervision in this area, moreover,\n entails systemic costs of particular concern.\n Examining the basis of a prosecution delays the\n criminal proceeding, threatens to chill law\n enforcement by subjecting the prosecutor’s\n motives and decisionmaking to outside inquiry,\n and may undermine prosecutorial effectiveness\n by revealing the Government’s enforcement\n policy. All of these are substantial concerns that\n make the courts properly hesitant to examine the\n decision whether to prosecute.\n\nId.; see also In re Richards, 213 F.3d 773, 786 (3d Cir. 2000)\n(echoing similar sentiments with respect to Rule 48(a)\ndismissals). Thus, absent constitutional concerns, the decision\nto try or retry a case is at the discretion of the prosecutor.\nUnited States v. HSBC Bank USA, N.A., 863 F.3d 125, 129,\n137-38 (2d Cir. 2017) (stating that the court’s “role is not to act\nas superprosecutors, second-guessing the legitimate exercise of\ncore elements of prosecutorial discretion, but rather as neutral\narbiters of the law” (citation and internal quotation marks\nomitted)); United States v. Raineri, 42 F.3d 36, 43 (1st Cir.\n1994) (“[T]he choice to forego permanently a prosecution is\nordinarily made by the executive branch.”); Tucker, 8 F.3d at\n676 (“In maintaining order in our own house, we should not\nneedlessly trample on the interest of the prosecutor and of the\npublic in securing proper, lasting convictions.”); Isgro, 974\nF.2d at 1097 (stating that the doctrine of separation of powers\n“mandates judicial respect for the independence of the\nprosecutor,” and “[d]ismissal of an indictment with prejudice\n\n\n\n\n 18\n\nis the most severe sanction possible”). 10 Accordingly,\nseparation-of-powers principles preclude a court from\nterminating a prosecution absent misconduct and prejudice to\nthe defendant. See Bank of Nova Scotia, 487 U.S. at 254-56,\n263; Goodson, 204 F.3d at 514; Tucker, 8 F.3d at 674; Isgro,\n974 F.2d at 1094.\n\n In short, a court’s power to preclude a prosecution is\nlimited by the separation of powers and, specifically, the\nExecutive’s law-enforcement and prosecutorial prerogative.\nSee Wayte, 470 U.S. at 607-08; HSBC, 863 F.3d at 137; In re\nRichards, 213 F.3d at 786; Raineri, 42 F.3d at 43; Tucker, 8\nF.3d at 676; Isgro, 974 F.2d at 1095-97; Santtini, 963 F.2d at\n596; Gatto, 763 F.2d at 1046. Exercising inherent authority\nhere to dismiss an indictment in the absence of misconduct and\nprejudice and based only on the fact that two juries could not\nreach a verdict intrudes on the Executive’s domain and thereby\nviolates the separation of powers. See, e.g., HSBC, 863 F.3d\nat 138; Isgro, 974 F.2d 1091.\n\n 10\n Several state courts have also refused to recognize\nany inherent authority to dismiss an indictment to prevent a\nretrial. See People v. Sierb, 581 N.W.2d 219, 225 (Mich.\n1998); State v. Johnson, 821 S.W.2d 609, 613 (Tex. Crim.\nApp. 1991) (en banc); State v. Sherrod, 383 So.2d 752, 753\n(Fla. Dist. Ct. App. 1980). Other states, however, have\nrecognized a court’s authority to dismiss an indictment sua\nsponte. See State v. Sauve, 666 A.2d 1164, 1167-68, 1167 n.1\n(Vt. 1995); Abbati, 493 A.2d at 521; Moriwake, 647 P.2d at\n712; Witt, 572 S.W.2d at 917. These latter cases are\nunpersuasive because they give too little weight to the\nseparation of powers, a crucial constitutional principle in the\nfederal system.\n\n\n\n\n 19\n\n Finally, there is no statute or procedural rule that\npermits a court to bar a retrial in the absence of misconduct and\nprejudice. First, a court may not dismiss an indictment as a\nmethod to manage its own affairs. 11 See Hasting, 461 U.S. at\n505. Second, a court’s inherent power does not “include the\npower to develop rules that circumvent or conflict with the\nFederal Rules of Criminal Procedure.” Carlisle v. United\nStates, 517 U.S. 416, 426 (1996). Barring a retrial through the\nexercise of inherent authority circumvents the absence of\npower of the district court to dismiss an indictment in Rule\n31(b). As stated above, courts have inherent authority to\ndismiss indictments, including, for instance, for prosecutorial\nmisconduct if the defendant was prejudiced, Bank of Nova\nScotia, 487 U.S. at 254-56, 263, but neither the Supreme Court\nnor our Court has extended a court’s inherent authority to allow\n\n 11\n In Chambers, for example, the Supreme Court\nrecognized a court’s authority to impose silence, respect, and\ndecorum based on its authority to manage its own affairs. 501\nU.S. at 43. This authority has been exercised by controlling\nadmission to the bar and disciplining its members; punishing\nfor contempt, which penalizes disruption to proceedings and\ndisobedience to court orders; disallowing fraud on the courts;\nensuring the proceedings move forward; and curtailing\nlitigation abuses. Id. at 43-45; see also Link v. Wabash R.R.\nCo., 370 U.S. 626, 629-31 (1962) (noting a court can dismiss a\ncivil case for failure to prosecute to prevent delays and court\ncongestion as part of a court’s inherent power to manage its\nown affairs). Chambers and Link address how a court may\nmanage its own proceedings, but they do not address how the\ncourt must also account for issues of separation of powers in\nthe context of a criminal case.\n\n\n\n\n 20\n\nthe sua sponte dismissal of an indictment solely to preclude\nmultiple mistrials following hung juries, see Chambers, 501\nU.S. at 47; HSBC, 863 F.3d at 136. 12\n\n 12\n Most cases concerning a court’s inherent authority\nhave arisen in the civil context. See Dietz, 136 S. Ct. at 1893\n(noting a court’s inherent powers to rescind a jury discharge\norder and recall a jury); Chambers, 501 U.S. at 44, 55-58\n(recognizing a court’s authority to vacate a judgment upon\nproof that a fraud was perpetrated on the court, and, in\nparticular, to assess as a sanction the entire amount of the\nopposing party’s attorney’s fees); Link, 370 U.S. at 629-31\n(authority to dismiss a civil case sua sponte for failure to\nprosecute); Gulf Oil Corp. v. Gilbert, 330 U.S. 501, 507-08\n(1947) (dismissing an action based on the doctrine of forum\nnon conveniens). See generally Dietz, 136 S. Ct. at 1892-93\n(citing cases involving the scope of a district court’s inherent\npower); Eash, 757 F.2d at 561-64 (same).\n There are other circumstances in which district courts\nlack the inherent authority to act, and most of those situations\narise in the criminal context. See, e.g., Carlisle, 517 U.S. at\n433 (holding that a court does not have authority to grant a\npost-verdict motion for judgment of acquittal, filed one day\noutside the time limit under Rule 29(e)); Williams, 504 U.S. at\n45-50, 55 (holding that a district court does not have inherent\nauthority to dismiss an indictment because the Government\nfailed to disclose to the grand jury substantial exculpatory\nevidence; “[b]ecause the grand jury is an institution separate\nfrom the courts, over whose functioning the courts do not\npreside, we think it clear that, as a general matter at least, no\nsuch ‘supervisory’ judicial authority exists”); HSBC, 863 F.3d\nat 129, 135-37 (holding that the district court violated\nseparation-of-powers principles by sua sponte invoking its\n\n\n\n\n 21\n\n Thus, the District Court abused its discretion in barring\na retrial and dismissing the indictment. 13\n\n III\n\n For the foregoing reasons, we will reverse and remand\nfor further proceedings.\n\n\n\n\nsupervisory power to oversee the government’s entry into and\nimplementation of a deferred prosecution agreement).\n 13\n[END_CASE]", "role": "user" } ]
4,583,425
UNITED STATES of America v. Jay GOLDSTEIN A/K/A Yaakov Jay Goldstein, Appellant
United States v. Jay Goldstein
2019-01-22
15-4094
U.S. Court of Appeals for the Third Circuit
{"judges": "Chagares, Restrepo, Roth", "parties": "", "opinions": [{"author": "", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 15-4094\n ________________\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n JAY GOLDSTEIN a/k/a Yaakov\n\n JAY GOLDSTEIN,\n\nAppellant\n ________________\n\n On Appeal from the United States District Court\n for the District of New Jersey\n (D. C. No. 3-14-cr-00287-003)\n District Judge: Honorable Freda L. Wolfson\n ________________\n\n Argued on January 25, 2017\n Panel Rehearing Granted on August 30, 2018\n\n Before: CHAGARES, RESTREPO and ROTH, Circuit\n Judges\n\f (Opinion filed: January 22, 2019)\n\n\nAidan P. O’Connor [Argued]\nPashman Stein Walder Hayden\n21 Main Street\nCourt Plaza South, Suite 200\nHackensack, NJ 07601\n Counsel for Appellant\n\nMark E. Coyne\nOffice of United States Attorney\n970 Broad Street, Room 700\nNewark, NJ 07102\n\nNorman Gross [Argued]\nGlenn J. Moramarco [Argued]\nOffice of United States Attorney\nCamden Federal Building & Courthouse\n401 Market Street\nCamden, NJ 08101\n Counsel for Appellee\n\n\n ________________\n\n OPINION\n ________________\n\n\nROTH, Circuit Judge\n\n\n\n\n 2\n\f I.\n\n We granted Appellant Jay Goldstein’s petition for\nrehearing to address the effect of the Supreme Court’s recent\ndecision in Carpenter v. United States1 on our prior panel\ndecision, United States v. Stimler.2 In Stimler, we held that\nthe District Court properly denied Goldstein’s motion to\nsuppress his cell site location information (CSLI) because\nGoldstein had no reasonable expectation of privacy in his\nCSLI, and, therefore, the government did not need probable\ncause to collect this data.3 Carpenter sets forth a new rule\nthat defendants do in fact have a privacy interest in their\nCSLI, and the government must generally obtain a search\nwarrant supported by probable cause to obtain this\ninformation.4 However, we still affirm the District Court’s\ndecision under the good faith exception to the exclusionary\nrule because the government had an objectively reasonable\ngood faith belief that its conduct was legal when it acquired\nGoldstein’s CSLI.\n\n II.\n\n We recited a comprehensive factual background in our\nprevious decision.5 The facts relevant to this decision follow.\n\n1\n 138 S. Ct. 2206 (2018).\n2\n 864 F.3d 253 (3d Cir. 2017).\n3\n Id. at 263. Carpenter does not affect our other holdings in\nStimler. Those remain as written and are not addressed in or\nchanged by this decision.\n4\n Carpenter, 138 S. Ct. at 2217, 2222.\n5\n Stimler, 864 F.3d at 259-61.\n\n\n\n\n 3\n\fGoldstein was arrested for his involvement in a kidnapping\nscheme. Hoping to find evidence placing Goldstein at the\nscene of the kidnapping, the prosecutors obtained a court\norder under the Stored Communications Act (SCA)—\nspecifically 18 U.S.C. § 2703(d)—compelling Goldstein’s\ncell phone carrier to turn over 57 days’ worth of his CSLI.\nCSLI is a type of metadata that is generated every time a\nuser’s cell phone connects to the nearest antenna. The user’s\ncell phone service provider retains a time-stamped record\nidentifying the particular antenna to which the phone\nconnected. Because most people constantly carry and\nfrequently use their cell phones, CSLI can provide a detailed\nlog of an individual’s movements over a period of time.\n\n The legal question in this case centers on whether\nSection 2703(d), the statutory provision under which the\ngovernment obtained Goldstein’s CSLI, complies with the\nFourth Amendment. The Fourth Amendment protects against\nunreasonable searches. In order for the acquisition of CSLI to\nbe a “search” under the Fourth Amendment, an individual\nmust have a reasonable expectation of privacy in his CSLI.6\nIn order for a search to be “reasonable,” it generally must be\nconducted pursuant to a search warrant supported by probable\ncause, unless an exception to the warrant requirement\napplies.7 Consequently, if there is no reasonable expectation\nof privacy as to CSLI, then its acquisition does not require a\nsearch warrant; if there is, then a warrant is generally\nrequired. Section 2703(d) does not require a showing of\n\n6\n See United States v. Knotts, 460 U.S. 276, 281 (1983)\n(explaining what constitutes a reasonable expectation of\nprivacy).\n7\n See Riley v. California, 134 S. Ct. 2473, 2482 (2014).\n\n\n\n\n 4\n\fprobable cause to obtain CSLI. Rather, it calls for a more\nlenient standard, requiring “specific and articulable facts\nshowing that there are reasonable grounds to believe” that the\nCSLI is relevant and material.8\n\n Before trial, Goldstein moved to suppress the CSLI,\narguing that this provision violates the Fourth Amendment\nbecause it authorizes disclosure of CSLI without a warrant\nsupported by probable cause. The District Court rejected this\nargument and denied the motion. Through the testimony of\nan FBI agent, the government introduced the CSLI at trial,\nwhich placed him in the vicinity of the kidnapping site.\nGoldstein was convicted and sentenced to 96 months in\nprison.\n\n In our previous decision, we affirmed the District\nCourt’s denial of Goldstein’s motion to suppress, holding that\nSection 2703(d) complied with the Fourth Amendment\nbecause cell phone users have no reasonable expectation of\nprivacy in their CSLI.9 We relied on our decision in In re\nApplication of the United States for an Order Directing a\nProvider of Electronic Communication Service to Disclose\nRecords to the Government (In re Application),10 which also\nfound no reasonable expectation of privacy in CSLI,11 and we\n\n\n\n\n8\n 18 U.S.C. § 2703(d).\n9\n Stimler, 864 F.3d at 263.\n10\n 620 F.3d 304 (3d Cir. 2010).\n11\n Id. at 312-13 (holding that CSLI is obtainable without “the\ntraditional probable cause determination” because\nindividuals’ privacy interests do not extend to CSLI).\n\n\n\n\n 5\n\freasoned that there were no intervening changes in law\nundermining In re Application.12\n\n Goldstein petitioned for rehearing, and we held the\npetition curia advisari vult pending the Supreme Court’s\ndecision in Carpenter, which was set to address essentially\nthe same question we answered in Stimler: whether obtaining\nCSLI without a warrant supported by probable cause under\nSection 2703(d) violates the Fourth Amendment’s protection\nagainst unreasonable searches. The Supreme Court decided\nCarpenter, and we granted Goldstein’s petition for panel\nrehearing.13 Carpenter came to the opposite conclusion that\nwe came to in In re Application and Stimler and held that “an\nindividual maintains a legitimate expectation of privacy in the\nrecord of his physical movements as captured though CSLI”\nand that the government’s collection of CSLI requires a\nshowing of probable cause under the Fourth Amendment.14\nConsequently, Section 2703(d) may not be used to access\nCSLI because it requires less than probable cause.\n\n Applying Carpenter to Goldstein’s case, we find that\nthe government did violate Goldstein’s Fourth Amendment\nrights when it acquired his CSLI under Section 2703(d) of the\nSCA. However, we will still affirm the District Court’s\nadmission of Goldstein’s CSLI because the government was\nacting under an objectively reasonable good faith belief that\n\n\n12\n Stimler, 864 F.3d at 264-67.\n13\n Appellants Stimler and Epstein also petitioned for\nrehearing, but we denied those petitions because the\ngovernment did not collect their CSLI.\n14\n Carpenter, 138 S. Ct. at 2217, 2222.\n\n\n\n\n 6\n\fobtaining CSLI under Section 2703(d) was constitutional at\nthe time.\n\n\n 15\n III.\n\n It is clear that under Carpenter, acquiring Goldstein’s\nCSLI was an unconstitutional search under the Fourth\nAmendment because the government did not obtain a warrant\nsupported by probable cause.16 However, evidence obtained\nin violation of a defendant’s Fourth Amendment rights is not\nautomatically suppressed. Evidence will be suppressed under\nthe exclusionary rule when suppression would further the\nexclusionary rule’s primary objective: to deter Fourth\nAmendment violations.17 One instance where suppressing\nevidence will not encourage deterrence is where the\ngovernment acted “upon an objectively reasonable good faith\nbelief in the legality of [its] conduct” when conducting a\n\n\n15\n The District Court had jurisdiction under 18 U.S.C. § 3231.\nWe have jurisdiction pursuant to 28 U.S.C. § 1291. “In\nreviewing a motion to suppress, ‘we review a district court’s\nfactual findings for clear error, and we exercise de novo\nreview over its application of the law to those factual\nfindings.’” United States v. Katzin, 769 F.3d 163, 169 n.4 (3d\nCir. 2014) (en banc) (quoting United States v. Pavulak, 700\nF.3d 651, 660 (3d Cir. 2012)).\n16\n A warrantless search is still reasonable under the Fourth\nAmendment if an exception to the warrant requirement\napplies, but the parties do not argue, and we do not find, that\nany exception applies here. Carpenter, 138 S. Ct. at 2222-23.\n17\n Katzin, 769 F.3d at 170-71.\n\n\n\n\n 7\n\fsearch.18 Indeed, “applying the exclusionary rule would not\n‘yield appreciable deterrence’” when government actors have\na reasonable belief that their conduct conforms with the law.19\nThis is known as the good faith exception, and where it\napplies, the illegally-obtained evidence will not be suppressed\nunder the exclusionary rule.\n\n The Supreme Court has applied this exception across a\nnumber of cases where suppressing evidence would not have\nany deterrent value—three of which are relevant here. In\nIllinois v. Krull,20 the Court held that the good faith exception\napplies when a search is executed pursuant to a statute that\nwas valid at the time of the search but later declared\nunconstitutional.21 Except in instances where a statute is\nobviously unconstitutional, suppressing evidence obtained by\na law enforcement officer “acting in objectively reasonable\nreliance on a statute would have . . . little deterrent effect on\nthe [government’s] actions.”22 Under Davis v. United\nStates,23 this exception also applies when a search is\nconducted based upon reasonable reliance on then-binding\nappellate precedent because exclusion in this context would\nnot deter improper government conduct.24 And under United\n\n\n18\n Id. at 182.\n19\n United States v. Vasquez-Algarin, 821 F.3d 467, 482-83 (3d\nCir. 2016) (quoting Davis v. United States, 564 U.S. 229, 237\n(2011)).\n20\n 480 U.S. 340 (1987).\n21\n Id. at 349-50.\n22\n Id.\n23\n 564 U.S. 229 (2011).\n24\n Id. at 241.\n\n\n\n\n 8\n\fStates v. Leon,25 the exclusionary rule will not apply when\nlaw enforcement conducts a search pursuant to a judicial\norder later found invalid.26\n\n The good faith exception applies to the government’s\nsearch in this case because the government acted upon an\nobjectively reasonable, good faith belief that obtaining\nGoldstein’s CSLI under Section 2703(d) was legal. At the\ntime the search was executed, it was authorized under Section\n2703(d). The government complied with all requirements of\nSection 2703(d) and obtained a valid judicial order to collect\nGoldstein’s CSLI. Moreover, the government had no reason\nto question the constitutionality of obtaining CSLI through\nSection 2703(d) because that question had been answered by\nthis Court in In re Application—which was binding appellate\nprecedent.27 Thus, because the government relied on a\nproperly-obtained valid judicial order, a then-valid statute,\nand then-binding appellate authority, it had an objectively\nreasonable, good faith belief that its conduct was legal.\nIndeed, the conduct was legal at the time. Excluding\nevidence obtained through methods that complied with the\nlaw at the time of the search cannot serve any deterrent\npurpose. Under Krull, Davis, and Leon, the good faith\nexception applies, and the District Court’s denial of the\nmotion to suppress is affirmed. Our holding puts us in good\ncompany, as many of our sister circuits have also found that\n\n25\n 468 U.S. 897 (1984).\n26\n Id. at 922.\n27\n In re Application, 620 F.3d at 313 (“[W]e hold that CSLI\nfrom cell phone calls is obtainable under a § 2703(d) order\nand that such an order does not require the traditional\nprobable cause determination.”).\n\n\n\n\n 9\n\fthe good faith exception applies when the government\nobtained CLSI data without a warrant prior to Carpenter.28\n Goldstein contends that the good faith exception does\nnot apply because the government’s reliance on Section\n2703(d) was unreasonable for two reasons, both of which fail.\nFirst, he argues that, at the time of the search, the Eleventh\nCircuit had held that collecting CSLI without a warrant\nsupported by probable cause violated the Fourth\n\n28\n See, e.g., United States v. Joyner, 899 F.3d 1199, 1204-05\n(11th Cir. 2018) (“Here, the Government complied with the\nrequirements of the SCA in obtaining the orders to compel\ncell site records, and when they did so in June 2015, that\nwarrantless procedure was, under this Court’s precedent,\nwithin the bounds of the Fourth Amendment.”);\nUnited States v. Chavez, 894 F.3d 593, 608 (4th Cir. 2018)\n(Carpenter does not affect cases where investigators acted\npursuant to court orders and the SCA); United States v.\nCurtis, 901 F.3d 846, 849 (7th Cir. 2018) (“We conclude,\ntherefore, that even though it is now established that the\nFourth Amendment requires a warrant for the type of cell-\nphone data present here, exclusion of that information was\nnot required because it was collected in good faith.”); United\nStates v. Chambers, No. 16-163-CR, 2018 WL 4523607, at\n*3 (2d Cir. Sept. 21, 2018) (“Thus, we conclude that even\nafter Jones, but before Carpenter, it was objectively\nreasonable for authorities to think that if they complied with\nthe SCA, no warrant based on probable cause was\nconstitutionally required to obtain cell-site information from a\nthird party.”). Judge Restrepo’s concurrence in Stimler also\nconcluded that the good faith exception applied here in light\nof In re Application. See Stimler, 864 F.3d at 279-80\n(Restrepo, J., concurring).\n\n\n\n\n 10\n\fAmendment.29 But, under Davis, only binding appellate\nprecedent is relevant to the good faith exception, and In re\nApplication was binding in this Circuit at the time. Second,\nhe contends the government could not have reasonably relied\non In re Application because it had been undermined by two\nsubsequent Supreme Court cases—United States v. Jones30\nand Riley v. California.31 As discussed in Stimler, neither\ncase undercuts In re Application because neither addresses\nthe long-term collection of metadata from cell phones.32\nJones addressed long-term collection of GPS location data\nfrom a car—not a cell phone.33 Riley involved the contents of\na cell phone, not the metadata transmitted from a cell phone\nto a third party.34 Indeed, Carpenter itself recognizes that the\ncollection of CSLI does “not fit neatly under existing\n\n\n29\n See Appellant’s Supplemental Letter at 3-4. The case that\nGoldstein refers to was reversed on rehearing and upheld the\nconstitutionality of CSLI obtained on less than probable\ncause. See United States v. Davis, 785 F.3d 498, 513 (11th\nCir. 2015).\n30\n 565 U.S. 400 (2012) (holding that placing a GPS tracker on\na defendant’s car for 28 days without a warrant violated the\nFourth Amendment).\n31\n 134 S. Ct. 2473 (2014) (holding that a warrantless search of\nthe contents of a cell phone violated Fourth Amendment).\n32\n Stimler, 864 F.3d at 264-67.\n33\n Jones, 565 U.S. at 412-13. Carpenter explains that cars\ncannot be analogized to cell phones in this context because\ncell phones can provide law enforcement with more\ninformation than a car about an individual’s movements.\nCarpenter, 138 S. Ct. at 2218.\n34\n Riley, 134 S. Ct. at 2494-95.\n\n\n\n\n 11\n\fprecedents.”35 The government could not have predicted the\noutcome of Carpenter and the overruling of In re Application\nfrom two Supreme Court cases that the Supreme Court itself\nsaid are not directly applicable.\n\n Goldstein also argues that the good faith exception\napplies only to police officers and other investigators, not the\ngovernment attorneys who obtained the Section 2703(d) order\nhere. Goldstein cites nothing in support of his proposed\nlimitation on the good faith exception, and we see no reason\nto limit its applicability in this case. The relevant inquiry\nhere is not who the state actor is, but rather, whether the state\nactor had a reasonable, good faith belief that his actions were\nlegal. The prosecutors relied on a then-valid statute whose\nconstitutionality had been confirmed by this Circuit. The\ngood faith exception applies.\n\n IV.\n\n For the foregoing reasons, we affirm the District Court’s\ndenial of Goldstein’s motion to suppress.\n\n\n\n\n35\n Carpenter, 138 S. Ct. at 2214-16.\n\n\n\n\n 12", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360678/", "author_raw": ""}]}
CHAGARES
RESTREPO
ROTH
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583425/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America v. Jay GOLDSTEIN A/K/A Yaakov Jay Goldstein, Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-22\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n\n No. 15-4094\n ________________\n\n\n UNITED STATES OF AMERICA\n\n v.\n\n JAY GOLDSTEIN a/k/a Yaakov\n\n JAY GOLDSTEIN,\n\nAppellant\n ________________\n\n On Appeal from the United States District Court\n for the District of New Jersey\n (D. C. No. 3-14-cr-00287-003)\n District Judge: Honorable Freda L. Wolfson\n ________________\n\n Argued on January 25, 2017\n Panel Rehearing Granted on August 30, 2018\n\n Before: CHAGARES, RESTREPO and ROTH, Circuit\n Judges\n\f (Opinion filed: January 22, 2019)\n\n\nAidan P. O’Connor [Argued]\nPashman Stein Walder Hayden\n21 Main Street\nCourt Plaza South, Suite 200\nHackensack, NJ 07601\n Counsel for Appellant\n\nMark E. Coyne\nOffice of United States Attorney\n970 Broad Street, Room 700\nNewark, NJ 07102\n\nNorman Gross [Argued]\nGlenn J. Moramarco [Argued]\nOffice of United States Attorney\nCamden Federal Building & Courthouse\n401 Market Street\nCamden, NJ 08101\n Counsel for Appellee\n\n\n ________________\n\n OPINION\n ________________\n\n\nROTH, Circuit Judge\n\n\n\n\n 2\n\f I.\n\n We granted Appellant Jay Goldstein’s petition for\nrehearing to address the effect of the Supreme Court’s recent\ndecision in Carpenter v. United States1 on our prior panel\ndecision, United States v. Stimler.2 In Stimler, we held that\nthe District Court properly denied Goldstein’s motion to\nsuppress his cell site location information (CSLI) because\nGoldstein had no reasonable expectation of privacy in his\nCSLI, and, therefore, the government did not need probable\ncause to collect this data.3 Carpenter sets forth a new rule\nthat defendants do in fact have a privacy interest in their\nCSLI, and the government must generally obtain a search\nwarrant supported by probable cause to obtain this\ninformation.4 However, we still affirm the District Court’s\ndecision under the good faith exception to the exclusionary\nrule because the government had an objectively reasonable\ngood faith belief that its conduct was legal when it acquired\nGoldstein’s CSLI.\n\n II.\n\n We recited a comprehensive factual background in our\nprevious decision.5 The facts relevant to this decision follow.\n\n1\n 138 S. Ct. 2206 (2018).\n2\n 864 F.3d 253 (3d Cir. 2017).\n3\n Id. at 263. Carpenter does not affect our other holdings in\nStimler. Those remain as written and are not addressed in or\nchanged by this decision.\n4\n Carpenter, 138 S. Ct. at 2217, 2222.\n5\n Stimler, 864 F.3d at 259-61.\n\n\n\n\n 3\n\fGoldstein was arrested for his involvement in a kidnapping\nscheme. Hoping to find evidence placing Goldstein at the\nscene of the kidnapping, the prosecutors obtained a court\norder under the Stored Communications Act (SCA)—\nspecifically 18 U.S.C. § 2703(d)—compelling Goldstein’s\ncell phone carrier to turn over 57 days’ worth of his CSLI.\nCSLI is a type of metadata that is generated every time a\nuser’s cell phone connects to the nearest antenna. The user’s\ncell phone service provider retains a time-stamped record\nidentifying the particular antenna to which the phone\nconnected. Because most people constantly carry and\nfrequently use their cell phones, CSLI can provide a detailed\nlog of an individual’s movements over a period of time.\n\n The legal question in this case centers on whether\nSection 2703(d), the statutory provision under which the\ngovernment obtained Goldstein’s CSLI, complies with the\nFourth Amendment. The Fourth Amendment protects against\nunreasonable searches. In order for the acquisition of CSLI to\nbe a “search” under the Fourth Amendment, an individual\nmust have a reasonable expectation of privacy in his CSLI.6\nIn order for a search to be “reasonable,” it generally must be\nconducted pursuant to a search warrant supported by probable\ncause, unless an exception to the warrant requirement\napplies.7 Consequently, if there is no reasonable expectation\nof privacy as to CSLI, then its acquisition does not require a\nsearch warrant; if there is, then a warrant is generally\nrequired. Section 2703(d) does not require a showing of\n\n6\n See United States v. Knotts, 460 U.S. 276, 281 (1983)\n(explaining what constitutes a reasonable expectation of\nprivacy).\n7\n See Riley v. California, 134 S. Ct. 2473, 2482 (2014).\n\n\n\n\n 4\n\fprobable cause to obtain CSLI. Rather, it calls for a more\nlenient standard, requiring “specific and articulable facts\nshowing that there are reasonable grounds to believe” that the\nCSLI is relevant and material.8\n\n Before trial, Goldstein moved to suppress the CSLI,\narguing that this provision violates the Fourth Amendment\nbecause it authorizes disclosure of CSLI without a warrant\nsupported by probable cause. The District Court rejected this\nargument and denied the motion. Through the testimony of\nan FBI agent, the government introduced the CSLI at trial,\nwhich placed him in the vicinity of the kidnapping site.\nGoldstein was convicted and sentenced to 96 months in\nprison.\n\n In our previous decision, we affirmed the District\nCourt’s denial of Goldstein’s motion to suppress, holding that\nSection 2703(d) complied with the Fourth Amendment\nbecause cell phone users have no reasonable expectation of\nprivacy in their CSLI.9 We relied on our decision in In re\nApplication of the United States for an Order Directing a\nProvider of Electronic Communication Service to Disclose\nRecords to the Government (In re Application),10 which also\nfound no reasonable expectation of privacy in CSLI,11 and we\n\n\n\n\n8\n 18 U.S.C. § 2703(d).\n9\n Stimler, 864 F.3d at 263.\n10\n 620 F.3d 304 (3d Cir. 2010).\n11\n Id. at 312-13 (holding that CSLI is obtainable without “the\ntraditional probable cause determination” because\nindividuals’ privacy interests do not extend to CSLI).\n\n\n\n\n 5\n\freasoned that there were no intervening changes in law\nundermining In re Application.12\n\n Goldstein petitioned for rehearing, and we held the\npetition curia advisari vult pending the Supreme Court’s\ndecision in Carpenter, which was set to address essentially\nthe same question we answered in Stimler: whether obtaining\nCSLI without a warrant supported by probable cause under\nSection 2703(d) violates the Fourth Amendment’s protection\nagainst unreasonable searches. The Supreme Court decided\nCarpenter, and we granted Goldstein’s petition for panel\nrehearing.13 Carpenter came to the opposite conclusion that\nwe came to in In re Application and Stimler and held that “an\nindividual maintains a legitimate expectation of privacy in the\nrecord of his physical movements as captured though CSLI”\nand that the government’s collection of CSLI requires a\nshowing of probable cause under the Fourth Amendment.14\nConsequently, Section 2703(d) may not be used to access\nCSLI because it requires less than probable cause.\n\n Applying Carpenter to Goldstein’s case, we find that\nthe government did violate Goldstein’s Fourth Amendment\nrights when it acquired his CSLI under Section 2703(d) of the\nSCA. However, we will still affirm the District Court’s\nadmission of Goldstein’s CSLI because the government was\nacting under an objectively reasonable good faith belief that\n\n\n12\n Stimler, 864 F.3d at 264-67.\n13\n Appellants Stimler and Epstein also petitioned for\nrehearing, but we denied those petitions because the\ngovernment did not collect their CSLI.\n14\n Carpenter, 138 S. Ct. at 2217, 2222.\n\n\n\n\n 6\n\fobtaining CSLI under Section 2703(d) was constitutional at\nthe time.\n\n\n 15\n III.\n\n It is clear that under Carpenter, acquiring Goldstein’s\nCSLI was an unconstitutional search under the Fourth\nAmendment because the government did not obtain a warrant\nsupported by probable cause.16 However, evidence obtained\nin violation of a defendant’s Fourth Amendment rights is not\nautomatically suppressed. Evidence will be suppressed under\nthe exclusionary rule when suppression would further the\nexclusionary rule’s primary objective: to deter Fourth\nAmendment violations.17 One instance where suppressing\nevidence will not encourage deterrence is where the\ngovernment acted “upon an objectively reasonable good faith\nbelief in the legality of [its] conduct” when conducting a\n\n\n15\n The District Court had jurisdiction under 18 U.S.C. § 3231.\nWe have jurisdiction pursuant to 28 U.S.C. § 1291. “In\nreviewing a motion to suppress, ‘we review a district court’s\nfactual findings for clear error, and we exercise de novo\nreview over its application of the law to those factual\nfindings.’” United States v. Katzin, 769 F.3d 163, 169 n.4 (3d\nCir. 2014) (en banc) (quoting United States v. Pavulak, 700\nF.3d 651, 660 (3d Cir. 2012)).\n16\n A warrantless search is still reasonable under the Fourth\nAmendment if an exception to the warrant requirement\napplies, but the parties do not argue, and we do not find, that\nany exception applies here. Carpenter, 138 S. Ct. at 2222-23.\n17\n Katzin, 769 F.3d at 170-71.\n\n\n\n\n 7\n\fsearch.18 Indeed, “applying the exclusionary rule would not\n‘yield appreciable deterrence’” when government actors have\na reasonable belief that their conduct conforms with the law.19\nThis is known as the good faith exception, and where it\napplies, the illegally-obtained evidence will not be suppressed\nunder the exclusionary rule.\n\n The Supreme Court has applied this exception across a\nnumber of cases where suppressing evidence would not have\nany deterrent value—three of which are relevant here. In\nIllinois v. Krull,20 the Court held that the good faith exception\napplies when a search is executed pursuant to a statute that\nwas valid at the time of the search but later declared\nunconstitutional.21 Except in instances where a statute is\nobviously unconstitutional, suppressing evidence obtained by\na law enforcement officer “acting in objectively reasonable\nreliance on a statute would have . . . little deterrent effect on\nthe [government’s] actions.”22 Under Davis v. United\nStates,23 this exception also applies when a search is\nconducted based upon reasonable reliance on then-binding\nappellate precedent because exclusion in this context would\nnot deter improper government conduct.24 And under United\n\n\n18\n Id. at 182.\n19\n United States v. Vasquez-Algarin, 821 F.3d 467, 482-83 (3d\nCir. 2016) (quoting Davis v. United States, 564 U.S. 229, 237\n(2011)).\n20\n 480 U.S. 340 (1987).\n21\n Id. at 349-50.\n22\n Id.\n23\n 564 U.S. 229 (2011).\n24\n Id. at 241.\n\n\n\n\n 8\n\fStates v. Leon,25 the exclusionary rule will not apply when\nlaw enforcement conducts a search pursuant to a judicial\norder later found invalid.26\n\n The good faith exception applies to the government’s\nsearch in this case because the government acted upon an\nobjectively reasonable, good faith belief that obtaining\nGoldstein’s CSLI under Section 2703(d) was legal. At the\ntime the search was executed, it was authorized under Section\n2703(d). The government complied with all requirements of\nSection 2703(d) and obtained a valid judicial order to collect\nGoldstein’s CSLI. Moreover, the government had no reason\nto question the constitutionality of obtaining CSLI through\nSection 2703(d) because that question had been answered by\nthis Court in In re Application—which was binding appellate\nprecedent.27 Thus, because the government relied on a\nproperly-obtained valid judicial order, a then-valid statute,\nand then-binding appellate authority, it had an objectively\nreasonable, good faith belief that its conduct was legal.\nIndeed, the conduct was legal at the time. Excluding\nevidence obtained through methods that complied with the\nlaw at the time of the search cannot serve any deterrent\npurpose. Under Krull, Davis, and Leon, the good faith\nexception applies, and the District Court’s denial of the\nmotion to suppress is affirmed. Our holding puts us in good\ncompany, as many of our sister circuits have also found that\n\n25\n 468 U.S. 897 (1984).\n26\n Id. at 922.\n27\n In re Application, 620 F.3d at 313 (“[W]e hold that CSLI\nfrom cell phone calls is obtainable under a § 2703(d) order\nand that such an order does not require the traditional\nprobable cause determination.”).\n\n\n\n\n 9\n\fthe good faith exception applies when the government\nobtained CLSI data without a warrant prior to Carpenter.28\n Goldstein contends that the good faith exception does\nnot apply because the government’s reliance on Section\n2703(d) was unreasonable for two reasons, both of which fail.\nFirst, he argues that, at the time of the search, the Eleventh\nCircuit had held that collecting CSLI without a warrant\nsupported by probable cause violated the Fourth\n\n28\n See, e.g., United States v. Joyner, 899 F.3d 1199, 1204-05\n(11th Cir. 2018) (“Here, the Government complied with the\nrequirements of the SCA in obtaining the orders to compel\ncell site records, and when they did so in June 2015, that\nwarrantless procedure was, under this Court’s precedent,\nwithin the bounds of the Fourth Amendment.”);\nUnited States v. Chavez, 894 F.3d 593, 608 (4th Cir. 2018)\n(Carpenter does not affect cases where investigators acted\npursuant to court orders and the SCA); United States v.\nCurtis, 901 F.3d 846, 849 (7th Cir. 2018) (“We conclude,\ntherefore, that even though it is now established that the\nFourth Amendment requires a warrant for the type of cell-\nphone data present here, exclusion of that information was\nnot required because it was collected in good faith.”); United\nStates v. Chambers, No. 16-163-CR, 2018 WL 4523607, at\n*3 (2d Cir. Sept. 21, 2018) (“Thus, we conclude that even\nafter Jones, but before Carpenter, it was objectively\nreasonable for authorities to think that if they complied with\nthe SCA, no warrant based on probable cause was\nconstitutionally required to obtain cell-site information from a\nthird party.”). Judge Restrepo’s concurrence in Stimler also\nconcluded that the good faith exception applied here in light\nof In re Application. See Stimler, 864 F.3d at 279-80\n(Restrepo, J., concurring).\n\n\n\n\n 10\n\fAmendment.29 But, under Davis, only binding appellate\nprecedent is relevant to the good faith exception, and In re\nApplication was binding in this Circuit at the time. Second,\nhe contends the government could not have reasonably relied\non In re Application because it had been undermined by two\nsubsequent Supreme Court cases—United States v. Jones30\nand Riley v. California.31 As discussed in Stimler, neither\ncase undercuts In re Application because neither addresses\nthe long-term collection of metadata from cell phones.32\nJones addressed long-term collection of GPS location data\nfrom a car—not a cell phone.33 Riley involved the contents of\na cell phone, not the metadata transmitted from a cell phone\nto a third party.34 Indeed, Carpenter itself recognizes that the\ncollection of CSLI does “not fit neatly under existing\n\n\n29\n See Appellant’s Supplemental Letter at 3-4. The case that\nGoldstein refers to was reversed on rehearing and upheld the\nconstitutionality of CSLI obtained on less than probable\ncause. See United States v. Davis, 785 F.3d 498, 513 (11th\nCir. 2015).\n30\n 565 U.S. 400 (2012) (holding that placing a GPS tracker on\na defendant’s car for 28 days without a warrant violated the\nFourth Amendment).\n31\n 134 S. Ct. 2473 (2014) (holding that a warrantless search of\nthe contents of a cell phone violated Fourth Amendment).\n32\n Stimler, 864 F.3d at 264-67.\n33\n Jones, 565 U.S. at 412-13. Carpenter explains that cars\ncannot be analogized to cell phones in this context because\ncell phones can provide law enforcement with more\ninformation than a car about an individual’s movements.\nCarpenter, 138 S. Ct. at 2218.\n34\n Riley, 134 S. Ct. at 2494-95.\n\n\n\n\n 11\n\fprecedents.”35 The government could not have predicted the\noutcome of Carpenter and the overruling of In re Application\nfrom two Supreme Court cases that the Supreme Court itself\nsaid are not directly applicable.\n\n Goldstein also argues that the good faith exception\napplies only to police officers and other investigators, not the\ngovernment attorneys who obtained the Section 2703(d) order\nhere. Goldstein cites nothing in support of his proposed\nlimitation on the good faith exception, and we see no reason\nto limit its applicability in this case. The relevant inquiry\nhere is not who the state actor is, but rather, whether the state\nactor had a reasonable, good faith belief that his actions were\nlegal. The prosecutors relied on a then-valid statute whose\nconstitutionality had been confirmed by this Circuit. The\ngood faith exception applies.\n\n IV.\n\n For the foregoing reasons, we affirm the District Court’s\ndenial of Goldstein’s motion to suppress.\n\n\n\n\n35\n Carpenter, 138 S. Ct. at 2214-16.\n\n\n\n\n 12\n[END_CASE]", "role": "user" } ]
4,583,426
G.S. v. Rose Tree Media School Distric
2019-01-22
17-2886
U.S. Court of Appeals for the Third Circuit
{"judges": "Present: AMBRO and JORDAN, Circuit Judges Motion by Amici to Convert a Not Precedential Opinion to Precedential.", "parties": "", "opinions": [{"author": "s/Thomas L. Ambro, Circuit Judge", "type": "010combined", "text": "UNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n No. 17-2886\n\n G.S., a minor, by his parents, J.S. and E.S.\n\n v.\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n (E.D. Pa. No. 2-16-cv-04782)\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n\n v.\n\n E.S. and J.S., Parents and Natural Guardians of G.S., a Minor\n (E.D. Pa. No. 2-16-cv-04849)\n\n Rose Tree Media School District,\n Appellant\n\nPresent: AMBRO and JORDAN, Circuit Judges\n\n Motion by Amici to Convert a Not Precedential Opinion to Precedential.\n\n Respectfully,\n Clerk/nmr\n_______________________________O R D E R ____________________________\nThe foregoing Motion by Amici to convert a Not Precedential Opinion to a Precedential\nOpinion is granted.\n\n By the Court,\n\n s/Thomas L. Ambro, Circuit Judge\n\nDated: January 22, 2019\n\n\n\n\n The Honorable Thomas I. Vanaskie, who authored the Court’s opinion in this matter,\nretired from the Court on January 1, 2019 and did not participate in the consideration of\nthe motion.", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360679/", "author_raw": "s/Thomas L. Ambro, Circuit Judge"}]}
AMBRO
JORDAN
0
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583426/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: G.S. v. Rose Tree Media School Distric\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-22\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n No. 17-2886\n\n G.S., a minor, by his parents, J.S. and E.S.\n\n v.\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n (E.D. Pa. No. 2-16-cv-04782)\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n\n v.\n\n E.S. and J.S., Parents and Natural Guardians of G.S., a Minor\n (E.D. Pa. No. 2-16-cv-04849)\n\n Rose Tree Media School District,\n Appellant\n\nPresent: AMBRO and JORDAN, Circuit Judges\n\n Motion by Amici to Convert a Not Precedential Opinion to Precedential.\n\n Respectfully,\n Clerk/nmr\n_______________________________O R D E R ____________________________\nThe foregoing Motion by Amici to convert a Not Precedential Opinion to a Precedential\nOpinion is granted.\n\n By the Court,\n\n s/Thomas L. Ambro, Circuit Judge\n\nDated: January 22, 2019\n\n\n\n\n The Honorable Thomas I. Vanaskie, who authored the Court’s opinion in this matter,\nretired from the Court on January 1, 2019 and did not participate in the consideration of\nthe motion.\n[END_CASE]", "role": "user" } ]
4,583,427
G.S. v. Rose Tree Media School Distric
2019-01-22
17-2886
U.S. Court of Appeals for the Third Circuit
{"judges": "Before: AMBRO, JORDAN, and VANASKIE,* Circuit Judges (Opinion", "parties": "", "opinions": [{"author": "Vanaskie. Judge Vanaskie retired from the Court on January", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-2886\n _____________\n\n G.S., a minor, by his parents, J.S. and E.S.\n\n v.\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n (E.D. Pa. No. 2-16-cv-04782)\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n\n v.\n\nE.S. and J.S., Parents and Natural Guardians of G.S., a Minor\n (E.D. Pa. No. 2-16-cv-04849)\n\n Rose Tree Media School District,\n Appellant\n _____________\n On Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n (D.C. Civil Nos. 2-16-cv-04782 & 2-16-cv-04849)\n District Judge: Honorable Eduardo C. Robreno\n ______________\n\n Argued June 4, 2018\n\f ______________\n\n Before: AMBRO, JORDAN,\n and VANASKIE,* Circuit Judges\n\n (Opinion Filed: November 6, 2018)\n\nGabrielle C. Goham, Esq.\nKatherine H. Meehan, Esq. [Argued]\nRaffaele Puppio\n19 West Third Street\nMedia, PA 19063\n Counsel for Appellant\n\nMichael D. Raffaele, Esq. [Argued]\nKershenbaum and Raffaele\n1230 County Line Road\nBryn Mawr, PA 19010\n Counsel for Appellees\n\n\n\n\n*\n On November 6, 2018, the panel issued a not precedential\nopinion in this matter authored by the Honorable Thomas I.\nVanaskie. Judge Vanaskie retired from the Court on January\n1, 2019. After Judge Vanaskie's retirement, amici curiae filed\na motion to issue the opinion as a precedential opinion which\nwas considered by the remaining members of the merits\npanel. Today, the Court has issued the opinion as a\nprecedential per curiam opinion. See 3rd Cir. I.O.P. 12.1 (d).\n\n\n\n\n 2\n\fShannon L.C. Ammon, Esq.\nJeffrey A. Sturgeon, Esq.\nMorgan Lewis & Bockius\n1701 Market Street\nPhiladelphia, PA 19103\n\nMaura McInerney\nEducation Law Center\n1315 Walnut Street, Suite 400\nPhiladelphia, PA 19107\n Counsel for Amicus Appellees\n\n\n ______________\n\n OPINION OF THE COURT\n ______________\n\nPER CURIAM\n\n Appellant Rose Tree Media School District (“Rose\nTree”) appeals the District Court’s grant of summary judgment\nconcluding that Rose Tree was obligated to enroll Appellee\nG.S. under Subtitle VII-B of the McKinney-Vento Homeless\nAssistance Act (“McKinney-Vento” or the “Act”), 42 U.S.C.\n§ 11434a(2) and § 11432(g)(3)(A)(i). We agree with the\nDistrict Court that G.S. satisfies the Act’s definition of youth\nhomelessness because he has been living in his maternal\ngrandmother’s home, along with his parents, ever since his\nparents lost their home in November 2014. Accordingly, we\nwill affirm.\n\n I.\n\n\n\n\n 3\n\f In 2010, G.S., along with his parents, his two sisters,\nand his paternal grandparents, moved into a rental home within\nRose Tree. At the time, G.S. and his sister, S.S., attended\nschools within Rose Tree. In November 2014, G.S.’s parents\nwere unable to make payments and lost the home. As a result,\nG.S. moved in with Ba.S., his maternal grandmother. The\ngrandmother’s single-family, 1500-square-foot row house was\nlocated outside of Rose Tree.\n\n With the addition of G.S., a total of ten people—five\nadults and five children—resided in the grandmother’s home.\nInitially, G.S. slept in the living room with his parents and two\nsisters. At times, G.S. moved his cot to the kitchen or basement\nto obtain some privacy. The parties agree that, to date, G.S.’s\nliving conditions remain unchanged.\n\n Rose Tree immediately learned of the change in G.S.’s\nliving conditions. At that time, Rose Tree deemed G.S. and\nS.S. homeless and thus continued to enroll them in a manner\nconsistent with its obligations under McKinney-Vento,\n42 U.S.C. § 11432(g)(3)(A)(i).\n\n In January 2015—less than two months after G.S.\nmoved in with his maternal grandmother—he was involved in\na disciplinary incident at school. Rose Tree suspended G.S. for\nthree days, extended the suspension to ten days, and threatened\nhim with expulsion. G.S.’s parents challenged Rose Tree’s\nactions. The parties resolved the matter pursuant to a written\nSettlement Agreement. Rose Tree, for its part, agreed to pay\nfor G.S. to attend a school outside of its jurisdiction for the\n2015–16 school year. In exchange, G.S.’s parents agreed to\nwaive all claims through August 31, 2016. The Settlement\nAgreement also included a provision purporting to waive\nG.S.’s right to claim homelessness after the 2015–16 academic\nyear.\n\n\n\n\n 4\n\f Pursuant to the Agreement, G.S. attended a school\noutside Rose Tree for the 2015–16 school year. Following the\nconclusion of that academic year, in July 2016, G.S.’s parents\nnotified Rose Tree of the family’s intent to re-enroll G.S. in\none of its schools for the 2016–17 academic year. Rose Tree\nrefused to enroll G.S., reasoning that his parents had waived\nhis right to claim homelessness and thereby enroll under\nMcKinney-Vento.\n\n G.S.’s parents initiated state grievance proceedings.\nAfter conducting an inquiry, the Pennsylvania Department of\nEducation issued a determination letter, stating:\n\n the outcome of our investigation is\n that [G.S.] . . . ha[s] the right under\n the federal McKinney-Vento\n Homelessness Act to continue\n being educated in the Rose Tree\n Media School District since it is\n [his] school district of origin and\n [he] is temporarily residing in a\n doubled up living situation that is\n not fixed, regular nor adequate.\n\n(App. 365.) G.S.’s parents again attempted to enroll G.S. in\nRose Tree, but the School District again refused.\n Throughout the pendency of this matter, Rose Tree\ncontinued to enroll G.S.’s sister, S.S, in one of its schools. The\nparties do not dispute that S.S.’s living conditions are identical\nto those of G.S.\n\n G.S. and his parents filed suit in federal court, Case No.\n16-4782, against Rose Tree, seeking enrollment. Rose Tree\nfiled a separate lawsuit in federal court, Case No. 16-4849,\nagainst G.S.’s parents, seeking a declaration that it was not\n\n\n\n\n 5\n\fobligated to enroll G.S. The District Court consolidated the\ntwo cases in February 2017. Both parties moved for summary\njudgment. The District Court resolved both motions in a single\norder, finding in favor of G.S. Rose Tree timely appealed. On\nappeal, the Education Law Center, the Homeless Children’s\nEducation Fund, the National Law Center of Homelessness and\nPoverty, and the People’s Emergency Center appear as amici\nin support of G.S.\n\n II.\n\n The District Court had jurisdiction under 28 U.S.C.\n§ 1331. We have appellate jurisdiction under 28 U.S.C.\n§ 1291. We exercise plenary review over a district court’s\ngrant of summary judgment. Blunt v. Lower Merion Sch. Dist.,\n767 F.3d 247, 265 (3d Cir. 2014).\n\n III.\n\n Rose Tree argues that the grant of summary judgment\nin favor of Appellees was erroneous because: (1) G.S.’s\nparents waived his McKinney-Vento rights for the 2016–17\nacademic year in the Settlement Agreement; (2) G.S. is no\nlonger “homeless” within the meaning of the Act; and (3)\nenrollment in Rose Tree is not in G.S.’s “best interest.”\n\n\n\n\n 6\n\f A.\n As a threshold matter, we must determine whether\nG.S.’s parents waived his McKinney-Vento rights in the\nSettlement Agreement. The parties agree that Pennsylvania\nlaw governs our interpretation of the Agreement. Under\nPennsylvania law, “[t]he fundamental rule in contract\ninterpretation is to ascertain the intent of the contracting\nparties.” Ins. Adjustment Bureau, Inc. v. Allstate Ins. Co., 905\nA.2d 462, 468 (Pa. 2006) (internal citation omitted). “In cases\nof a written contract, the intent of the parties is the writing itself\n. . . When the terms of a contract are clear and unambiguous,\nthe intent of the parties is to be ascertained from the document\nitself.” Id. (internal citations omitted).\n\n In relevant part, the Settlement Agreement includes a\nprovision purporting to waive G.S.’s McKinney-Vento rights\nfor the 2016–17 academic year. This provision states:\n\n Parents agree that they will make\n no claim of homeless status after\n the 2015-16 school year and that\n the District will have no further\n obligations to Student after the\n 2015-16 school year.\n\n(App. 140.) The District Court concluded that the waiver was\nunenforceable for lack of consideration. We agree.\n\n Under Pennsylvania law, consideration is an essential\nelement of a valid contract. See Taylor v. Stanley Co. of Am.,\n158 A. 157, 158 (Pa. 1932); see also Johnston the Florist, Inc.\nv. TEDCO Constr. Corp., 657 A.2d 511, 516 (Pa. Super. Ct.\n1995). In addition to the waiver provision excerpted above, the\nSettlement Agreement includes a provision titled “Adequate\nConsideration.” This provision states:\n\n\n\n\n 7\n\f Adequate Consideration. The Parents\n specifically acknowledge and agree that the\n District’s agreement to make the above\n payments is intended to and does provide the\n Parents with sufficient consideration for a\n settlement and compromise of any and all\n outstanding education and discrimination claims\n that they may now have or have had, whether\n known or unknown, from the beginning of time\n through August 31, 2016. The Parents also\n expressly acknowledge and confirm that: (1) the\n only consideration for their signing of this\n Agreement consists of the terms and provisions\n stated herein; and (2) no other promise or\n agreement of any kind, save those set forth in this\n Agreement, has been made by any person or\n entity whatsoever to cause them to sign the\n document.\n\n(App. 141) (emphasis in original).\n\n Rose Tree argues, in conclusory fashion, that the family\nreceived “adequate” and “substantial consideration for all of\nthe promises made . . . .” (Appellant’s Br. 6.) G.S. and his\nparents counter that the “Adequate Consideration” provision of\nthe Agreement expressly limits consideration to claims arising\nbefore August 31, 2016, and thus any waiver of claims\nconcerning the 2016–17 academic year lacks consideration.\n(Appellees’ Br. 11–12, 15–16.) As the District Court\nconcluded, the clear and unambiguous language of this\nprovision states that consideration was only provided for\nclaims through August 31, 2016, which pre-dates claims\narising out of the 2016–17 academic year. Accordingly, we\nagree that any purported waiver of claims arising after August\n31, 2016 lacks consideration and is unenforceable.\n\n\n\n\n 8\n\f B.\n Next, Rose Tree contends it need not enroll G.S.\nbecause he is no longer “homeless” within the meaning of the\nAct. Subtitle VII-B of the Act, “Education for Homeless\nChildren and Youths” (“EHCY”), addresses the educational\nbarriers faced by homeless children. EHCY preserves the right\nof equal access to a “free, appropriate public education”\nindependent of a child’s housing status. 42 U.S.C. § 11431(1).\nSpecifically, under this subtitle, local education agencies are\nrequired to continue a homeless child’s education in his or her\n“school of origin” for the “duration” of his or her homelessness\nif doing so is in the child’s “best interest.” Id.\n§ 11432(g)(3)(A)(i). Notably, there is no statutory limit on the\nduration of homelessness.\n\n Whether a child is eligible under EHCY is determined\nby the Act’s definition of youth homelessness, 42 U.S.C.\n§ 11434a(2). In relevant part, this definition provides:\n\n The term “homeless children and youths”—\n\n (A) means individuals who lack a\n fixed, regular, and adequate\n nighttime residence (within the\n meaning of section 11302(a)(1) of\n this title); and\n (B) includes—\n\n (i) children and youths who\n are sharing the housing of\n other persons due to loss of\n housing, economic\n hardship, or a similar\n reason; . . .\n\n\n\n\n 9\n\fId. § 11434a(2). Children who satisfy § 11434a(2)(B)(i) are\noften described as living “doubled up.” See U.S. Dep’t of\nEduc., Education for Homeless Children and Youths Program\nNon-Regulatory Guidance, 5 (2016),\nhttps://www2.ed.gov/policy/elsec/leg/essa/160240ehcyguidan\nce072716.pdf.\n\n There is no dispute that G.S. satisfied § 11434a(2) when\nhe first moved in with his maternal grandmother. Rather, the\nquestion is whether G.S. continues to satisfy this definition\nalmost four years later. Rose Tree argues that G.S. no longer\nlacks a fixed, regular, and adequate nighttime residence due to\nthe fact that his doubled-up living arrangement has persisted\nfor several years. We are not convinced.\n\n First, Rose Tree’s interpretation is inconsistent with the\nplain meaning of the statute. There is no dispute that G.S.\ncontinues to satisfy § 11434a(2)(B)(i), which is listed as a\nspecific example of youth homelessness. Second, the Act does\nnot impose a limit on the duration of homelessness. This\nundermines Rose Tree’s argument that a doubled-up\narrangement can transform into a fixed, adequate, and regular\nnighttime residence if it persists long enough. Third, Rose\nTree fails to cite any authority other than general provisions of\nthe Act and the dictionary for its interpretation. This is\nunsurprising—to date, no court has adopted Rose Tree’s\ninterpretation. Fourth, several circumstances particular to this\ncase persuade us that G.S. is eligible for coverage. Rose Tree\ninitially treated G.S. as homeless, and the parties agree his\nliving arrangements have not changed. It is also compelling\nthat Rose Tree has continued to enroll G.S.’s similarly situated\nsister, S.S., throughout the duration of this matter.1 And\n 1\n Although S.S. is enrolled, the record is unclear as to\nwhether Rose Tree still considers her to be homeless within the\nmeaning of the McKinney-Vento Act. (App. 292–93.) At oral\n\n\n\n\n 10\n\ffinally, the Pennsylvania Department of Education determined\nthat G.S. remains homeless. Although we are not bound by the\nAgency’s determination, we think it is well-reasoned and,\ntherefore, instructive. To remove G.S. from the protections of\nthe Act under these circumstances strikes us as nothing short\nof arbitrary. Accordingly, we agree that G.S. continues to\nqualify as homeless for purposes of enrollment in a Rose Tree\nschool.\n\n C.\n\n Finally, assuming G.S. qualifies as homeless, Rose Tree\nargues it need not enroll G.S. because enrollment is not in his\nbest interest. It raises this argument for the first time on appeal\nand thus we need not consider it. See Caisson Corp. v.\nIngersoll-Rand Co., 622 F.2d 672, 680 (3d Cir. 1980).\nNonetheless, we take a moment to reject this argument on its\nmerits.\n\n A school district is required to enroll a homeless student\nso long as doing so accords with the child’s “best interest.” 42\nU.S.C. § 11432(g)(3)(A). It is presumed that the best interest\nof the student is to remain in his or her school of origin unless\ndoing so is contrary to the request of the parent or youth. Id.\n§ 11432(g)(3)(B). School of origin “means [either] the school\nthat a child or youth attended when permanently housed or the\nschool in which the child or youth was last enrolled, including\na preschool.” Id. § 11432(g)(3)(I)(i).\n\n Here, all of the statutory considerations align to suggest\nenrollment in Rose Tree is in G.S.’s best interest. Rose Tree\nhosts the school where G.S. was enrolled when he became\n\nargument, the School District took the position that while S.S.\nwas homeless at the start of the 2016–17 academic year, she\nmay not be homeless currently.\n\n\n\n\n 11\n\fhomeless; the school where G.S. was last enrolled; the school\nwhere his sister attends; and the school where he and his\nparents seek enrollment. Under these circumstances, we\nconclude that continued enrollment in Rose Tree is in G.S.’s\nbest interest.\n IV.\n\n For these reasons, we will affirm the order of the\nDistrict Court dated July 31, 2017.\n\n\n\n\n 12", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4360680/", "author_raw": "Vanaskie. Judge Vanaskie retired from the Court on January"}]}
AMBRO
JORDAN
VANASKIE
1
{"AMBRO": ", Circuit", "JORDAN": ", Circuit", "VANASKIE": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583427/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: G.S. v. Rose Tree Media School Distric\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-22\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 17-2886\n _____________\n\n G.S., a minor, by his parents, J.S. and E.S.\n\n v.\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n (E.D. Pa. No. 2-16-cv-04782)\n\n ROSE TREE MEDIA SCHOOL DISTRICT\n\n v.\n\nE.S. and J.S., Parents and Natural Guardians of G.S., a Minor\n (E.D. Pa. No. 2-16-cv-04849)\n\n Rose Tree Media School District,\n Appellant\n _____________\n On Appeal from the United States District Court\n for the Eastern District of Pennsylvania\n (D.C. Civil Nos. 2-16-cv-04782 & 2-16-cv-04849)\n District Judge: Honorable Eduardo C. Robreno\n ______________\n\n Argued June 4, 2018\n\f ______________\n\n Before: AMBRO, JORDAN,\n and VANASKIE,* Circuit Judges\n\n (Opinion Filed: November 6, 2018)\n\nGabrielle C. Goham, Esq.\nKatherine H. Meehan, Esq. [Argued]\nRaffaele Puppio\n19 West Third Street\nMedia, PA 19063\n Counsel for Appellant\n\nMichael D. Raffaele, Esq. [Argued]\nKershenbaum and Raffaele\n1230 County Line Road\nBryn Mawr, PA 19010\n Counsel for Appellees\n\n\n\n\n*\n On November 6, 2018, the panel issued a not precedential\nopinion in this matter authored by the Honorable Thomas I.\nVanaskie. Judge Vanaskie retired from the Court on January\n1, 2019. After Judge Vanaskie's retirement, amici curiae filed\na motion to issue the opinion as a precedential opinion which\nwas considered by the remaining members of the merits\npanel. Today, the Court has issued the opinion as a\nprecedential per curiam opinion. See 3rd Cir. I.O.P. 12.1 (d).\n\n\n\n\n 2\n\fShannon L.C. Ammon, Esq.\nJeffrey A. Sturgeon, Esq.\nMorgan Lewis & Bockius\n1701 Market Street\nPhiladelphia, PA 19103\n\nMaura McInerney\nEducation Law Center\n1315 Walnut Street, Suite 400\nPhiladelphia, PA 19107\n Counsel for Amicus Appellees\n\n\n ______________\n\n OPINION OF THE COURT\n ______________\n\nPER CURIAM\n\n Appellant Rose Tree Media School District (“Rose\nTree”) appeals the District Court’s grant of summary judgment\nconcluding that Rose Tree was obligated to enroll Appellee\nG.S. under Subtitle VII-B of the McKinney-Vento Homeless\nAssistance Act (“McKinney-Vento” or the “Act”), 42 U.S.C.\n§ 11434a(2) and § 11432(g)(3)(A)(i). We agree with the\nDistrict Court that G.S. satisfies the Act’s definition of youth\nhomelessness because he has been living in his maternal\ngrandmother’s home, along with his parents, ever since his\nparents lost their home in November 2014. Accordingly, we\nwill affirm.\n\n I.\n\n\n\n\n 3\n\f In 2010, G.S., along with his parents, his two sisters,\nand his paternal grandparents, moved into a rental home within\nRose Tree. At the time, G.S. and his sister, S.S., attended\nschools within Rose Tree. In November 2014, G.S.’s parents\nwere unable to make payments and lost the home. As a result,\nG.S. moved in with Ba.S., his maternal grandmother. The\ngrandmother’s single-family, 1500-square-foot row house was\nlocated outside of Rose Tree.\n\n With the addition of G.S., a total of ten people—five\nadults and five children—resided in the grandmother’s home.\nInitially, G.S. slept in the living room with his parents and two\nsisters. At times, G.S. moved his cot to the kitchen or basement\nto obtain some privacy. The parties agree that, to date, G.S.’s\nliving conditions remain unchanged.\n\n Rose Tree immediately learned of the change in G.S.’s\nliving conditions. At that time, Rose Tree deemed G.S. and\nS.S. homeless and thus continued to enroll them in a manner\nconsistent with its obligations under McKinney-Vento,\n42 U.S.C. § 11432(g)(3)(A)(i).\n\n In January 2015—less than two months after G.S.\nmoved in with his maternal grandmother—he was involved in\na disciplinary incident at school. Rose Tree suspended G.S. for\nthree days, extended the suspension to ten days, and threatened\nhim with expulsion. G.S.’s parents challenged Rose Tree’s\nactions. The parties resolved the matter pursuant to a written\nSettlement Agreement. Rose Tree, for its part, agreed to pay\nfor G.S. to attend a school outside of its jurisdiction for the\n2015–16 school year. In exchange, G.S.’s parents agreed to\nwaive all claims through August 31, 2016. The Settlement\nAgreement also included a provision purporting to waive\nG.S.’s right to claim homelessness after the 2015–16 academic\nyear.\n\n\n\n\n 4\n\f Pursuant to the Agreement, G.S. attended a school\noutside Rose Tree for the 2015–16 school year. Following the\nconclusion of that academic year, in July 2016, G.S.’s parents\nnotified Rose Tree of the family’s intent to re-enroll G.S. in\none of its schools for the 2016–17 academic year. Rose Tree\nrefused to enroll G.S., reasoning that his parents had waived\nhis right to claim homelessness and thereby enroll under\nMcKinney-Vento.\n\n G.S.’s parents initiated state grievance proceedings.\nAfter conducting an inquiry, the Pennsylvania Department of\nEducation issued a determination letter, stating:\n\n the outcome of our investigation is\n that [G.S.] . . . ha[s] the right under\n the federal McKinney-Vento\n Homelessness Act to continue\n being educated in the Rose Tree\n Media School District since it is\n [his] school district of origin and\n [he] is temporarily residing in a\n doubled up living situation that is\n not fixed, regular nor adequate.\n\n(App. 365.) G.S.’s parents again attempted to enroll G.S. in\nRose Tree, but the School District again refused.\n Throughout the pendency of this matter, Rose Tree\ncontinued to enroll G.S.’s sister, S.S, in one of its schools. The\nparties do not dispute that S.S.’s living conditions are identical\nto those of G.S.\n\n G.S. and his parents filed suit in federal court, Case No.\n16-4782, against Rose Tree, seeking enrollment. Rose Tree\nfiled a separate lawsuit in federal court, Case No. 16-4849,\nagainst G.S.’s parents, seeking a declaration that it was not\n\n\n\n\n 5\n\fobligated to enroll G.S. The District Court consolidated the\ntwo cases in February 2017. Both parties moved for summary\njudgment. The District Court resolved both motions in a single\norder, finding in favor of G.S. Rose Tree timely appealed. On\nappeal, the Education Law Center, the Homeless Children’s\nEducation Fund, the National Law Center of Homelessness and\nPoverty, and the People’s Emergency Center appear as amici\nin support of G.S.\n\n II.\n\n The District Court had jurisdiction under 28 U.S.C.\n§ 1331. We have appellate jurisdiction under 28 U.S.C.\n§ 1291. We exercise plenary review over a district court’s\ngrant of summary judgment. Blunt v. Lower Merion Sch. Dist.,\n767 F.3d 247, 265 (3d Cir. 2014).\n\n III.\n\n Rose Tree argues that the grant of summary judgment\nin favor of Appellees was erroneous because: (1) G.S.’s\nparents waived his McKinney-Vento rights for the 2016–17\nacademic year in the Settlement Agreement; (2) G.S. is no\nlonger “homeless” within the meaning of the Act; and (3)\nenrollment in Rose Tree is not in G.S.’s “best interest.”\n\n\n\n\n 6\n\f A.\n As a threshold matter, we must determine whether\nG.S.’s parents waived his McKinney-Vento rights in the\nSettlement Agreement. The parties agree that Pennsylvania\nlaw governs our interpretation of the Agreement. Under\nPennsylvania law, “[t]he fundamental rule in contract\ninterpretation is to ascertain the intent of the contracting\nparties.” Ins. Adjustment Bureau, Inc. v. Allstate Ins. Co., 905\nA.2d 462, 468 (Pa. 2006) (internal citation omitted). “In cases\nof a written contract, the intent of the parties is the writing itself\n. . . When the terms of a contract are clear and unambiguous,\nthe intent of the parties is to be ascertained from the document\nitself.” Id. (internal citations omitted).\n\n In relevant part, the Settlement Agreement includes a\nprovision purporting to waive G.S.’s McKinney-Vento rights\nfor the 2016–17 academic year. This provision states:\n\n Parents agree that they will make\n no claim of homeless status after\n the 2015-16 school year and that\n the District will have no further\n obligations to Student after the\n 2015-16 school year.\n\n(App. 140.) The District Court concluded that the waiver was\nunenforceable for lack of consideration. We agree.\n\n Under Pennsylvania law, consideration is an essential\nelement of a valid contract. See Taylor v. Stanley Co. of Am.,\n158 A. 157, 158 (Pa. 1932); see also Johnston the Florist, Inc.\nv. TEDCO Constr. Corp., 657 A.2d 511, 516 (Pa. Super. Ct.\n1995). In addition to the waiver provision excerpted above, the\nSettlement Agreement includes a provision titled “Adequate\nConsideration.” This provision states:\n\n\n\n\n 7\n\f Adequate Consideration. The Parents\n specifically acknowledge and agree that the\n District’s agreement to make the above\n payments is intended to and does provide the\n Parents with sufficient consideration for a\n settlement and compromise of any and all\n outstanding education and discrimination claims\n that they may now have or have had, whether\n known or unknown, from the beginning of time\n through August 31, 2016. The Parents also\n expressly acknowledge and confirm that: (1) the\n only consideration for their signing of this\n Agreement consists of the terms and provisions\n stated herein; and (2) no other promise or\n agreement of any kind, save those set forth in this\n Agreement, has been made by any person or\n entity whatsoever to cause them to sign the\n document.\n\n(App. 141) (emphasis in original).\n\n Rose Tree argues, in conclusory fashion, that the family\nreceived “adequate” and “substantial consideration for all of\nthe promises made . . . .” (Appellant’s Br. 6.) G.S. and his\nparents counter that the “Adequate Consideration” provision of\nthe Agreement expressly limits consideration to claims arising\nbefore August 31, 2016, and thus any waiver of claims\nconcerning the 2016–17 academic year lacks consideration.\n(Appellees’ Br. 11–12, 15–16.) As the District Court\nconcluded, the clear and unambiguous language of this\nprovision states that consideration was only provided for\nclaims through August 31, 2016, which pre-dates claims\narising out of the 2016–17 academic year. Accordingly, we\nagree that any purported waiver of claims arising after August\n31, 2016 lacks consideration and is unenforceable.\n\n\n\n\n 8\n\f B.\n Next, Rose Tree contends it need not enroll G.S.\nbecause he is no longer “homeless” within the meaning of the\nAct. Subtitle VII-B of the Act, “Education for Homeless\nChildren and Youths” (“EHCY”), addresses the educational\nbarriers faced by homeless children. EHCY preserves the right\nof equal access to a “free, appropriate public education”\nindependent of a child’s housing status. 42 U.S.C. § 11431(1).\nSpecifically, under this subtitle, local education agencies are\nrequired to continue a homeless child’s education in his or her\n“school of origin” for the “duration” of his or her homelessness\nif doing so is in the child’s “best interest.” Id.\n§ 11432(g)(3)(A)(i). Notably, there is no statutory limit on the\nduration of homelessness.\n\n Whether a child is eligible under EHCY is determined\nby the Act’s definition of youth homelessness, 42 U.S.C.\n§ 11434a(2). In relevant part, this definition provides:\n\n The term “homeless children and youths”—\n\n (A) means individuals who lack a\n fixed, regular, and adequate\n nighttime residence (within the\n meaning of section 11302(a)(1) of\n this title); and\n (B) includes—\n\n (i) children and youths who\n are sharing the housing of\n other persons due to loss of\n housing, economic\n hardship, or a similar\n reason; . . .\n\n\n\n\n 9\n\fId. § 11434a(2). Children who satisfy § 11434a(2)(B)(i) are\noften described as living “doubled up.” See U.S. Dep’t of\nEduc., Education for Homeless Children and Youths Program\nNon-Regulatory Guidance, 5 (2016),\nhttps://www2.ed.gov/policy/elsec/leg/essa/160240ehcyguidan\nce072716.pdf.\n\n There is no dispute that G.S. satisfied § 11434a(2) when\nhe first moved in with his maternal grandmother. Rather, the\nquestion is whether G.S. continues to satisfy this definition\nalmost four years later. Rose Tree argues that G.S. no longer\nlacks a fixed, regular, and adequate nighttime residence due to\nthe fact that his doubled-up living arrangement has persisted\nfor several years. We are not convinced.\n\n First, Rose Tree’s interpretation is inconsistent with the\nplain meaning of the statute. There is no dispute that G.S.\ncontinues to satisfy § 11434a(2)(B)(i), which is listed as a\nspecific example of youth homelessness. Second, the Act does\nnot impose a limit on the duration of homelessness. This\nundermines Rose Tree’s argument that a doubled-up\narrangement can transform into a fixed, adequate, and regular\nnighttime residence if it persists long enough. Third, Rose\nTree fails to cite any authority other than general provisions of\nthe Act and the dictionary for its interpretation. This is\nunsurprising—to date, no court has adopted Rose Tree’s\ninterpretation. Fourth, several circumstances particular to this\ncase persuade us that G.S. is eligible for coverage. Rose Tree\ninitially treated G.S. as homeless, and the parties agree his\nliving arrangements have not changed. It is also compelling\nthat Rose Tree has continued to enroll G.S.’s similarly situated\nsister, S.S., throughout the duration of this matter.1 And\n 1\n Although S.S. is enrolled, the record is unclear as to\nwhether Rose Tree still considers her to be homeless within the\nmeaning of the McKinney-Vento Act. (App. 292–93.) At oral\n\n\n\n\n 10\n\ffinally, the Pennsylvania Department of Education determined\nthat G.S. remains homeless. Although we are not bound by the\nAgency’s determination, we think it is well-reasoned and,\ntherefore, instructive. To remove G.S. from the protections of\nthe Act under these circumstances strikes us as nothing short\nof arbitrary. Accordingly, we agree that G.S. continues to\nqualify as homeless for purposes of enrollment in a Rose Tree\nschool.\n\n C.\n\n Finally, assuming G.S. qualifies as homeless, Rose Tree\nargues it need not enroll G.S. because enrollment is not in his\nbest interest. It raises this argument for the first time on appeal\nand thus we need not consider it. See Caisson Corp. v.\nIngersoll-Rand Co., 622 F.2d 672, 680 (3d Cir. 1980).\nNonetheless, we take a moment to reject this argument on its\nmerits.\n\n A school district is required to enroll a homeless student\nso long as doing so accords with the child’s “best interest.” 42\nU.S.C. § 11432(g)(3)(A). It is presumed that the best interest\nof the student is to remain in his or her school of origin unless\ndoing so is contrary to the request of the parent or youth. Id.\n§ 11432(g)(3)(B). School of origin “means [either] the school\nthat a child or youth attended when permanently housed or the\nschool in which the child or youth was last enrolled, including\na preschool.” Id. § 11432(g)(3)(I)(i).\n\n Here, all of the statutory considerations align to suggest\nenrollment in Rose Tree is in G.S.’s best interest. Rose Tree\nhosts the school where G.S. was enrolled when he became\n\nargument, the School District took the position that while S.S.\nwas homeless at the start of the 2016–17 academic year, she\nmay not be homeless currently.\n\n\n\n\n 11\n\fhomeless; the school where G.S. was last enrolled; the school\nwhere his sister attends; and the school where he and his\nparents seek enrollment. Under these circumstances, we\nconclude that continued enrollment in Rose Tree is in G.S.’s\nbest interest.\n IV.\n\n For these reasons, we will affirm the order of the\nDistrict Court dated July 31, 2017.\n\n\n\n\n 12\n[END_CASE]", "role": "user" } ]
4,583,849
FEDERAL TRADE COMMISSION; Commonwealth of Pennsylvania v. PENN STATE HERSHEY MEDICAL CENTER; Pinnacle Health System Commonwealth of Pennsylvania, Appellant
Fed. Trade Comm'n v. Penn State Hershey Med. Ctr.
2019-01-23
17-2270
U.S. Court of Appeals for the Third Circuit
{"judges": "Shwartz, Nygaard, Rendell", "parties": "", "opinions": [{"author": "NYGAARD, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n\n __________\n\n No. 17-2270\n __________\n\n FEDERAL TRADE COMMISSION;\n COMMONWEALTH OF PENNSYLVANIA\n\n v.\n\n PENN STATE HERSHEY MEDICAL CENTER;\n PINNACLE HEALTH SYSTEM\n\n Commonwealth of Pennsylvania,\n\n Appellant\n __________\n\n On Appeal from the United States District Court\n for the Middle District of Pennsylvania\n (District Court Civil No. 1-15-cv-02362)\n District Judge: Honorable John E. Jones III\n\n Argued July 10, 2018\n\nBEFORE: SHWARTZ, NYGAARD, and RENDELL,\n Circuit Judges.\n\f (Filed: January 23, 2019)\n\n\nWesley G. Carson, Esq.\nPeggy Bayer Femenella, Esq.\nJames W. Frost, Esq.\nLynda Lao, Esq.\nFederal Trade Commission\n600 Pennsylvania Avenue, N.W.\nWashington, DC 20580\n\nWilliam H. Efron, Esq.\nRyan F. Harsch, Esq.\nJared P. Nagley, Esq.\nJonathan W. Platt, Esq.\nGerald A. Stein, Esq.\nGeralyn J. Trujillo, Esq.\nNancy Turnblacer, Esq.\nTheodore Zang, Esq.\nFederal Trade Commission\nOne Bowling Green\nSuite 318\nNew York, NY 10004\n\n Counsel for Plaintiff Federal Trade Commission\n\nHoward G. Hopkirk, Esq. [Argued]\nTracy W. Wertz, Esq.\nOffice of Attorney General of Pennsylvania\nStrawberry Square\nHarrisburg, PA 17120\n\n\n\n\n 2\n\fKemal A. Mericli, Esq.\nOffice of Attorney General of Pennsylvania\n1251 Waterfront Place\nPittsburgh, PA 15222\n\n Counsel for Appellant Commonwealth of Pennsylvania\n\n\nWilliam D. Coglianese, Esq. [Argued]\nChristopher N. Thatch, Esq.\nAdrian Wager-Zito, Esq.\nJones Day\n51 Louisiana Avenue, N.W.\nWashington, DC 20001\n\n Counsel for Appellees Penn State Hershey Medical\n and Pinnacle Health System\n\nLuminita Nodit, Esq.\nOffice of Attorney General of Washington\n800 Fifth Avenue\nSuite 2000\nSeattle, WA 98104\n\n Counsel for Amicus Appellants\n\n __________\n\n OPINION OF THE COURT\n __________\n\nNYGAARD, Circuit Judge.\n\n\n\n\n 3\n\f I.\n\n In March 2015, the Boards of Penn State Hershey\nMedical Center and PinnacleHealth System (“Hershey” and\n“Pinnacle,” respectively) formally approved a plan to merge.\nThey had announced the proposal a year earlier, so the\nCommonwealth of Pennsylvania and the Federal Trade\nCommission (“FTC”) were already investigating the impact\nof the proposed merger when the Boards approved it. This\njoint probe resulted in the FTC filing an administrative\ncomplaint alleging that the merger violated Section 7 of the\nClayton Act. 1 The FTC scheduled an administrative hearing\non the merits for May 2016. At the same time, the\nCommonwealth and the FTC jointly sued Hershey and\nPinnacle under Section 16 of the Clayton Act, 2 and Section\n13(b) of the Federal Trade Commission Act (“FTC Act”), 3 to\n“prevent and restrain Hershey and Pinnacle from violating\nSection 7 of the Clayton Act . . . pending the Commission’s\nadministrative proceeding.” 4 They sought a preliminary\ninjunction and a temporary restraining order.\n\n The District Court denied relief. 5 But, on September\n27, 2016, we reversed the District Court’s order and directed\nit to preliminarily enjoin the merger “pending the outcome of\n\n1\n 15 U.S.C. § 18.\n2\n 15 U.S.C. § 26.\n3\n 15 U.S.C. § 53(b).\n4\n Amended Complaint at 7 ¶ 14, FTC v. Penn State Hershey\nMed. Ctr., 185 F. Supp. 3d 552 (M.D. Pa. 2016) (No. 1:15-\ncv-2362) (“Hershey I”).\n5\n Hershey I, 185 F. Supp. 3d at 564.\n\n\n\n\n 4\n\fthe FTC’s administrative adjudication.” 6 Within three weeks,\nHershey and Pinnacle terminated their Agreement,\nreferencing our remand ordering the temporary injunction as\nthe impetus. The District Court ultimately issued the\ninjunction on October 20, 2016.\n\n The Commonwealth then moved for attorneys’ fees\nand costs, asserting that it “substantially prevailed” under\nSection 16 of the Clayton Act, but the District Court denied\nthe motion. 7 In doing so, the District Court rejected\nHershey’s and Pinnacle’s argument that the Commonwealth\ncould not seek attorneys’ fees and costs under Section 16 of\nthe Clayton Act because, in ordering the injunction, we\napplied Section 13(b) of the FTC Act instead. The District\nCourt denied the fee request, however, because the\nCommonwealth had not “substantially prevailed” under\nSection 16 of the Clayton Act. The Commonwealth timely\nappealed. We will affirm, because we credit Hershey’s and\nPinnacle’s argument that we ordered the injunction based on\nSection 13(b) of the FTC Act, not Section 16 of the Clayton\nAct.\n\n II.\n\n\n\n\n6\n FTC v. Penn State Hershey Med. Ctr., 838 F.3d 327, 354\n(3d Cir. 2016) (“Hershey II”).\n7\n FTC v. Penn State Hershey Med. Ctr., No. 1:15-cv-2362,\n2017 WL 1954398, at *9 (M.D. Pa. May 11, 2017) (“Hershey\nIII”).\n\n\n\n\n 5\n\f Ordinarily, we review the District Court’s denial of\nattorneys’ fees for abuse of discretion. 8 As explained below,\nhowever, our decision turns on the legal question as to which\nstatute applies. Our review of that legal question is plenary. 9\n\n III.\n\n The American Rule, grounded in longstanding\ncommon law tradition, requires parties to pay their own legal\ncosts “win or lose, unless a statute or contract provides\notherwise.” 10 One such statute is Section 16 of the Clayton\nAct. That section provides in relevant part:\n\n Any person, firm, corporation, or\n association shall be entitled to sue\n for and have injunctive relief, in\n any court of the United States\n having jurisdiction over the\n parties, against threatened loss or\n damage by a violation of the\n antitrust laws . . . . In any action\n under this section in which the\n plaintiff substantially prevails, the\n court shall award the cost of suit,\n including a reasonable attorney’s\n fee, to such plaintiff. 11\n\n8\n Raab v. City of Ocean City, 833 F.3d 286, 292 (3d Cir.\n2016).\n9\n See id.\n10\n Baker Botts L.L.P. v. ASARCO LLC, 135 S. Ct. 2158, 2164\n(2015).\n11\n 15 U.S.C. § 26.\n\n\n\n\n 6\n\f The District Court concluded that the Commonwealth\ndid not “substantially prevail” under this section for two\nreasons. First, the District Court ruled that the termination of\nthe merger did not render the Commonwealth a prevailing\nparty because the injunction itself did not terminate the\nmerger and, even though the injunction motivated Hershey\nand Pinnacle to do so on their own, the Supreme Court has\nrejected the “catalyst theory” of prevailing-party status. 12\nSecond, the District Court determined that, because our ruling\nwas based on the holding that the Commonwealth and FTC\nwere merely likely to succeed on the merits, our ruling was\nnot a grant of relief “on the merits” as required for prevailing-\nparty status by Singer Management Consultants, Inc. v.\nMilgram. 13\n\n The Commonwealth contests both conclusions. But\nHershey and Pinnacle argue that we need not address them\nbecause Section 16 of the Clayton Act and its attorneys’ fees\nprovision do not apply at all. Hershey and Pinnacle contend\nthat the preliminary injunction on which the Commonwealth\nrelies for its claim of attorneys’ fees was not entered “in an\naction under this section” as required for application of\nSection 16 of the Clayton Act. Instead, they argue, the\ninjunction was issued under the authority of Section 13(b) of\nthe FTC Act, which does not provide for attorneys’ fees. 14\nThus, they argue, the Commonwealth does not have any legal\nground to claim entitlement to attorneys’ fees on the basis of\n\n12\n See Buckhannon Bd. & Care Home, Inc. v. W. Va. Dep’t of\nHealth & Human Res., 532 U.S. 598, 605, 610 (2001).\n13\n 650 F.3d 223, 228-29 (3d Cir. 2011) (en banc).\n14\n 15 U.S.C. § 53(b).\n\n\n\n\n 7\n\fthe injunction (or the merger termination that it prompted) in\nthis case.\n\n We ultimately agree with Hershey and Pinnacle. We\nwill therefore assume without deciding that the\nCommonwealth is a prevailing party, leaving for another day\nthe questions of whether the Supreme Court’s rejection of the\ncatalyst theory controls claims for fees under Section 16 of\nthe Clayton Act and whether a preliminary injunction entered\npursuant to that section can constitute relief “on the merits.”\nOur sole focus here is to examine the Commonwealth’s claim\nthat it has a statutory basis to be awarded its fees.\n\n\n IV.\n\n We conclude that it does not. The Commonwealth\nclaims attorneys’ fees under Section 16 of the Clayton Act.\nThe District Court noted that, in ordering the injunction, our\nCourt “solely applied the standard outlined by Section 13(b)\nof the FTC Act.” 15 And, as noted above, Section 13(b) of the\nFTC Act makes no provision for attorneys’ fees. The District\nCourt nevertheless determined that the Commonwealth was\npotentially entitled to fees under Section 16 of the Clayton\nAct because the Commonwealth referenced that section when\nit joined with the FTC to seek a preliminary injunction\nagainst Hershey and Pinnacle, 16 and policy and Supreme\nCourt precedent supported the allowance of fees.\n\n\n\n\n15\n Hershey III, 2017 WL 1954398, at *2.\n16\n Id. at *3.\n\n\n\n\n 8\n\f The District Court’s initial conclusion that we ordered\nthe injunction under Section 13(b) of the FTC Act and not\nSection 16 of the Clayton act was correct, and its inquiry\nshould have ended there. The strongest indication that the\ninjunction rested solely on Section 13(b) of the FTC Act was\nthe standard that we used in ordering that injunction. When\nconsidering requests for injunctive relief under Section 16 of\nthe Clayton Act, courts generally apply the traditional four-\npart preliminary injunction standard that includes a\nconsideration of: (1) the likelihood of success on the merits;\n(2) the threat of irreparable harm in the absence of an\ninjunction; (3) the possibility of substantial harm to other\ninterested parties; and (4) the public interest. 17 In ordering\nthe injunction in Hershey II, we referenced the “traditional\nequity standard for injunctive relief,” 18 but we did not use it.\nInstead, we determined that the standard governing\ninjunctions under Section 13(b) of the FTC Act is different,\nand we went on to apply that different standard. 19\n\n In particular, and drawing directly from the statute, we\nsaid that the question of preliminary injunctive relief under\nSection 13(b) of the FTC Act is resolved by “weighing the\nequities and considering the Commission’s likelihood of\nultimate success” to determine whether “such action would be\nin the public interest.” 20 In doing so, we emphasized that the\n\n17\n See Holland v. Rosen, 895 F.3d 272, 285-86 (3d Cir. 2018)\ncert. denied 139 S. Ct. 440 (2018); see also Julian O. von\nKalinowski, Antitrust Laws and Trade Regulations §\n172.02[3][b] & n.60 (2d ed. 2018) (collecting cases).\n18\n Hershey II, 838 F.3d at 337.\n19\n Id.\n20\n Id. (quoting 15 U.S.C. § 53(b)).\n\n\n\n\n 9\n\fpublic interest standard in the second prong of this analysis\ndiffers from “the traditional equity standard for injunctive\nrelief.” 21 This assessment aligns with the judgment of other\nCourts of Appeals, which have concluded that the Section\n13(b) standard is not only different from, but easier to satisfy\nthan the traditional standard for injunctive relief that courts\napply to claims under Section 16 of the Clayton Act. 22\n\n In sum, in ordering the injunction on which the\nCommonwealth relies, we expressly applied Section 13(b) of\nthe FTC Act and its lower evidentiary bar instead of Section\n16 of the Clayton Act. Thus, to the extent that the\nCommonwealth can be said to have “prevailed,” it did so\nunder Section 13(b) of the FTC Act and not Section 16 of the\nClayton Act. For similar reasons, the only court of which we\nare aware to have addressed the issue has concluded that an\ninjunction issued under Section 13(b) of the FTC Act does\nnot trigger potential entitlement to attorneys’ fees under\n\n\n\n\n21\n Id.\n22\n See, e.g., FTC v. H.J. Heinz Co., 246 F.3d 708, 714 (D.C.\nCir. 2001) (explaining that Congress, in drafting Section\n13(b), “intended th[e Section 13(b)] standard to depart from .\n. . the then-traditional equity standard” so that the FTC “was\nnot held to the high thresholds applicable where private\nparties seek interim restraining orders”) (quotation marks\nomitted); FTC v. Affordable Media, LLC, 179 F.3d 1228,\n1233 (9th Cir. 1999) (recognizing that Section 13(b) “places a\nlighter burden on the Commission than that imposed on\nprivate litigants by the traditional equity standard”)(quotation\nmarks omitted).\n\n\n\n\n 10\n\fSection 16 of the Clayton Act. 23 We agree with that\nconclusion.\n\n The District Court relied on a number of factors in\nconcluding otherwise, but none is persuasive. The District\nCourt first pointed to the legislative history of the Clayton\nAct to justify its relevance here. It noted that “Congress\nintended that an individual plaintiff should not bear ‘the very\nhigh price of obtaining judicial enforcement of . . . the\nantitrust laws.’” 24 However, we have examined the extensive\nhistory of this Act and find nothing that clearly shows\nCongress’s intent to empower us to extend the fee-shifting\nprovision of the Clayton Act to cover an action for injunctive\nrelief under another statute. 25 As a result, we are not\npersuaded that the legislative history of the Clayton Act\nsupports the District Court’s conclusion.\n\n The District Court also cited Supreme Court precedent,\nMaher v. Gagne, 26 for the proposition that the fee-shifting\nprovisions of one statute can apply to pendent claims brought\nunder other statutes. Maher, however, does not support\n\n23\n See FTC v. Staples, Inc., 239 F. Supp. 3d 1, 4-5 (D.D.C.\n2017).\n24\n Hershey III, 2017 WL 1954398, at *3 (quoting H.R. Rep.\nNo. 94-499, part 1, at 19-20 (1976)).\n25\n See H.R. Rep. No. 94-499, pt. 1, at 18-20 (1976); see also\nBuckhannon Bd., 532 U.S. at 608 (holding that, “in view of\nthe ‘American Rule’ that attorney’s fees will not be awarded\nabsent explicit statutory authority, . . . [ambiguous] legislative\nhistory is clearly insufficient to alter the accepted meaning of\nthe statutory term”) (quotation marks omitted).\n26\n 448 U.S. 122 (1980).\n\n\n\n\n 11\n\fapplication of the Clayton Act’s fee-shifting provision in this\ncase. In Maher, the plaintiff brought claims under 42 U.S.C.\n§ 1983, alleging that Connecticut’s Aid to Families with\nDependent Children program violated Section 402(a)(7) of\nthe Social Security Act, 27 as well as the Equal Protection and\nDue Process Clauses of the Fourteenth Amendment. 28 After\nthe District Court approved a settlement between the parties,\nthe plaintiff sought attorneys’ fees under 42 U.S.C. § 1988,\nwhich authorizes fees for parties who prevail under Section\n1983 (among other statutes). Responding to objections that\nthe Eleventh Amendment prevented a federal court from\nordering fees against a state for statutory, non-civil rights\nclaims like the plaintiff’s claim under the Social Security Act,\nthe Supreme Court held that Section 1988 allows for “the\naward of fees in a case in which the plaintiff prevails on a\nwholly statutory, non-civil-rights claim pendent to a\nsubstantial constitutional claim or in one in which both a\nstatutory and a substantial constitutional claim are settled\nfavorably to the plaintiff without adjudication.” 29 The Court\nwent on to say: “The legislative history makes it clear that\nCongress intended fees to be awarded where a pendent\nconstitutional claim is involved, even if the statutory claim on\nwhich the plaintiff prevailed is one for which fees cannot be\nawarded under the Act.” 30\n\n Stretching the logic of Maher, the Commonwealth\nargues that it is entitled to attorneys’ fees because its claim\nunder Section 16 of the Clayton Act was pendent to the\n\n27\n 42 U.S.C. § 602(a)(7).\n28\n Maher, 448 U.S. at 125.\n29\n Id. at 132.\n30\n Id. at 132 n.15.\n\n\n\n\n 12\n\fFTC’s claim under Section 13(b) of the FTC Act. But the\nissue in Maher was fundamentally different. The issue in\nMaher was whether the plaintiff’s including the Social\nSecurity Act violation in its Section 1983 complaint\ndisqualified it from receiving fees authorized by Section\n1988. The theory was that the fees were only to vindicate\nviolations of the Fourteenth Amendment. But the Supreme\nCourt held that the plaintiff could recover attorneys’ fees\nunder Section 1988 because she had alleged violations of her\nFourteenth Amendment Due Process and Equal Protection\nrights. As for the fact that she had also alleged a purely\nstatutory violation (of the Social Security Act), the Supreme\nCourt held that this did not preclude an award of attorneys’\nfees under Section 1988 because this was pendant to the\nconstitutional claims. 31\n\n But—as we noted earlier—Section 16 of the Clayton\nAct specifies that a party must substantially prevail “[i]n any\naction under this section.” 32 This language limits the\napplication of Chapter 13’s fee-shifting provision to parties\nwho obtain relief under that section. 33 As we noted above,\nrequests for relief under that section are assessed on a\n\n31\n Id. at 132.\n32\n 15 U.S.C. § 26 (emphasis added).\n33\n See John T. ex rel. Paul T. v. Del. Cty. Intermediate Unit,\n318 F.3d 545, 560 (3d Cir. 2003) (“When the [Individuals\nwith Disabilities Education Act] fee-shifting provision\nauthorizes attorneys[’] fees ‘in any action or proceeding\nbrought under this section,’ it not only limits the universe to\nwhich it applies but also clarifies the type of proceeding on\nwhich a party must ‘prevail.’”) (first emphasis added)\n(quoting 20 U.S.C. § 1415(i)(3)).\n\n\n\n\n 13\n\fdifferent and more lenient standard than are requests for relief\nunder Section 16 of the Clayton Act, and we clearly decided\nthat the injunction should issue based on the standard of\nSection 13(b), not Section 16. Such differences were not\nevident in Maher. As also noted above, the legislative history\ndoes not justify extending the Clayton Act’s fee-shifting\nprovisions to other statutory schemes. For all of these\nreasons, we are not persuaded that Maher gives us any basis\nto extend the fee-shifting provisions of the Clayton Act to a\nclaim raised and adjudicated under the FTC Act. 34\n\n34\n The Commonwealth maintains that it did raise its claim\nunder the Clayton Act and that we acknowledged this in\nHershey II. It is true that we referenced both the Clayton Act\nand the FTC Act as a basis for the suit brought jointly by the\nCommonwealth and the FTC. In particular, we noted that the\nCommonwealth and the FTC “filed suit . . . under” both\nSection 16 of the Clayton Act and Section 13(b) of the FTC\nAct, Hershey II, 838 F.3d at 333, and we also stated that\n“[t]he District Court had jurisdiction” under both Section 16\nof the Clayton Act and Section 13(b) of the FTC Act, id. at\n335. But the Commonwealth does not have standing to\npursue a claim under the FTC Act, and these statements\nmerely declare that the Clayton Act gave them standing in\nthis case. The issue of standing aside, the facts remain that\nthe Commonwealth and the FTC litigated their request for an\ninjunction under Section 13(b) of the FTC Act and that we\nordered the injunction under that section and the more lenient\nstandard that applies thereto. As one court explained in\nrejecting the Commonwealth’s claim for attorneys’ fees in a\nsimilar case, the Commonwealth “cannot have it both ways”\nby “rid[ing] the FTC’s claim to a successful preliminary\ninjunction under the more permissive Section 13(b) standard\n\n\n\n\n 14\n\f Finally, the District Court raised concerns that failing\nto allow the Commonwealth to seek attorneys’ fees in this\nsituation would be contrary to the interests of judicial\neconomy. Forcing the Commonwealth to pursue a separate\ncase to bring a claim under Section 16, the District Court said,\ncould result in “duplicative litigation, separate filings, and\nrepetitive arguments” because this would be the only avenue\nfor claiming attorneys’ fees. 35 We are not persuaded that\nsuch concerns outweigh the plain language of the statutes.\n\n V.\n\n In sum, we conclude that the authority for this\ninjunction arose from Section 13(b) of the FTC Act, which—\nunlike Section 16 of the Clayton Act—does not provide for\nattorneys’ fees. Hence, for all of the foregoing reasons, the\nCommonwealth has no legal basis to claim attorneys’ fees in\nthis case and we will affirm the order of the District Court on\nthat ground.\n\n\n\n\nand then cit[ing] that favorable ruling as the sole justification\nfor fee-shifting under the more rigorous Clayton Act\nstandard.” Staples, 239 F. Supp. 3d at 5.\n35\n Hershey III, 2017 WL 1954398, at *3.\n\n\n\n\n 15", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361102/", "author_raw": "NYGAARD, Circuit Judge."}]}
SHWARTZ
NYGAARD
RENDELL
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583849/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: FEDERAL TRADE COMMISSION; Commonwealth of Pennsylvania v. PENN STATE HERSHEY MEDICAL CENTER; Pinnacle Health System Commonwealth of Pennsylvania, Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-23\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n\n __________\n\n No. 17-2270\n __________\n\n FEDERAL TRADE COMMISSION;\n COMMONWEALTH OF PENNSYLVANIA\n\n v.\n\n PENN STATE HERSHEY MEDICAL CENTER;\n PINNACLE HEALTH SYSTEM\n\n Commonwealth of Pennsylvania,\n\n Appellant\n __________\n\n On Appeal from the United States District Court\n for the Middle District of Pennsylvania\n (District Court Civil No. 1-15-cv-02362)\n District Judge: Honorable John E. Jones III\n\n Argued July 10, 2018\n\nBEFORE: SHWARTZ, NYGAARD, and RENDELL,\n Circuit Judges.\n\f (Filed: January 23, 2019)\n\n\nWesley G. Carson, Esq.\nPeggy Bayer Femenella, Esq.\nJames W. Frost, Esq.\nLynda Lao, Esq.\nFederal Trade Commission\n600 Pennsylvania Avenue, N.W.\nWashington, DC 20580\n\nWilliam H. Efron, Esq.\nRyan F. Harsch, Esq.\nJared P. Nagley, Esq.\nJonathan W. Platt, Esq.\nGerald A. Stein, Esq.\nGeralyn J. Trujillo, Esq.\nNancy Turnblacer, Esq.\nTheodore Zang, Esq.\nFederal Trade Commission\nOne Bowling Green\nSuite 318\nNew York, NY 10004\n\n Counsel for Plaintiff Federal Trade Commission\n\nHoward G. Hopkirk, Esq. [Argued]\nTracy W. Wertz, Esq.\nOffice of Attorney General of Pennsylvania\nStrawberry Square\nHarrisburg, PA 17120\n\n\n\n\n 2\n\fKemal A. Mericli, Esq.\nOffice of Attorney General of Pennsylvania\n1251 Waterfront Place\nPittsburgh, PA 15222\n\n Counsel for Appellant Commonwealth of Pennsylvania\n\n\nWilliam D. Coglianese, Esq. [Argued]\nChristopher N. Thatch, Esq.\nAdrian Wager-Zito, Esq.\nJones Day\n51 Louisiana Avenue, N.W.\nWashington, DC 20001\n\n Counsel for Appellees Penn State Hershey Medical\n and Pinnacle Health System\n\nLuminita Nodit, Esq.\nOffice of Attorney General of Washington\n800 Fifth Avenue\nSuite 2000\nSeattle, WA 98104\n\n Counsel for Amicus Appellants\n\n __________\n\n OPINION OF THE COURT\n __________\n\nNYGAARD, Circuit Judge.\n\n\n\n\n 3\n\f I.\n\n In March 2015, the Boards of Penn State Hershey\nMedical Center and PinnacleHealth System (“Hershey” and\n“Pinnacle,” respectively) formally approved a plan to merge.\nThey had announced the proposal a year earlier, so the\nCommonwealth of Pennsylvania and the Federal Trade\nCommission (“FTC”) were already investigating the impact\nof the proposed merger when the Boards approved it. This\njoint probe resulted in the FTC filing an administrative\ncomplaint alleging that the merger violated Section 7 of the\nClayton Act. 1 The FTC scheduled an administrative hearing\non the merits for May 2016. At the same time, the\nCommonwealth and the FTC jointly sued Hershey and\nPinnacle under Section 16 of the Clayton Act, 2 and Section\n13(b) of the Federal Trade Commission Act (“FTC Act”), 3 to\n“prevent and restrain Hershey and Pinnacle from violating\nSection 7 of the Clayton Act . . . pending the Commission’s\nadministrative proceeding.” 4 They sought a preliminary\ninjunction and a temporary restraining order.\n\n The District Court denied relief. 5 But, on September\n27, 2016, we reversed the District Court’s order and directed\nit to preliminarily enjoin the merger “pending the outcome of\n\n1\n 15 U.S.C. § 18.\n2\n 15 U.S.C. § 26.\n3\n 15 U.S.C. § 53(b).\n4\n Amended Complaint at 7 ¶ 14, FTC v. Penn State Hershey\nMed. Ctr., 185 F. Supp. 3d 552 (M.D. Pa. 2016) (No. 1:15-\ncv-2362) (“Hershey I”).\n5\n Hershey I, 185 F. Supp. 3d at 564.\n\n\n\n\n 4\n\fthe FTC’s administrative adjudication.” 6 Within three weeks,\nHershey and Pinnacle terminated their Agreement,\nreferencing our remand ordering the temporary injunction as\nthe impetus. The District Court ultimately issued the\ninjunction on October 20, 2016.\n\n The Commonwealth then moved for attorneys’ fees\nand costs, asserting that it “substantially prevailed” under\nSection 16 of the Clayton Act, but the District Court denied\nthe motion. 7 In doing so, the District Court rejected\nHershey’s and Pinnacle’s argument that the Commonwealth\ncould not seek attorneys’ fees and costs under Section 16 of\nthe Clayton Act because, in ordering the injunction, we\napplied Section 13(b) of the FTC Act instead. The District\nCourt denied the fee request, however, because the\nCommonwealth had not “substantially prevailed” under\nSection 16 of the Clayton Act. The Commonwealth timely\nappealed. We will affirm, because we credit Hershey’s and\nPinnacle’s argument that we ordered the injunction based on\nSection 13(b) of the FTC Act, not Section 16 of the Clayton\nAct.\n\n II.\n\n\n\n\n6\n FTC v. Penn State Hershey Med. Ctr., 838 F.3d 327, 354\n(3d Cir. 2016) (“Hershey II”).\n7\n FTC v. Penn State Hershey Med. Ctr., No. 1:15-cv-2362,\n2017 WL 1954398, at *9 (M.D. Pa. May 11, 2017) (“Hershey\nIII”).\n\n\n\n\n 5\n\f Ordinarily, we review the District Court’s denial of\nattorneys’ fees for abuse of discretion. 8 As explained below,\nhowever, our decision turns on the legal question as to which\nstatute applies. Our review of that legal question is plenary. 9\n\n III.\n\n The American Rule, grounded in longstanding\ncommon law tradition, requires parties to pay their own legal\ncosts “win or lose, unless a statute or contract provides\notherwise.” 10 One such statute is Section 16 of the Clayton\nAct. That section provides in relevant part:\n\n Any person, firm, corporation, or\n association shall be entitled to sue\n for and have injunctive relief, in\n any court of the United States\n having jurisdiction over the\n parties, against threatened loss or\n damage by a violation of the\n antitrust laws . . . . In any action\n under this section in which the\n plaintiff substantially prevails, the\n court shall award the cost of suit,\n including a reasonable attorney’s\n fee, to such plaintiff. 11\n\n8\n Raab v. City of Ocean City, 833 F.3d 286, 292 (3d Cir.\n2016).\n9\n See id.\n10\n Baker Botts L.L.P. v. ASARCO LLC, 135 S. Ct. 2158, 2164\n(2015).\n11\n 15 U.S.C. § 26.\n\n\n\n\n 6\n\f The District Court concluded that the Commonwealth\ndid not “substantially prevail” under this section for two\nreasons. First, the District Court ruled that the termination of\nthe merger did not render the Commonwealth a prevailing\nparty because the injunction itself did not terminate the\nmerger and, even though the injunction motivated Hershey\nand Pinnacle to do so on their own, the Supreme Court has\nrejected the “catalyst theory” of prevailing-party status. 12\nSecond, the District Court determined that, because our ruling\nwas based on the holding that the Commonwealth and FTC\nwere merely likely to succeed on the merits, our ruling was\nnot a grant of relief “on the merits” as required for prevailing-\nparty status by Singer Management Consultants, Inc. v.\nMilgram. 13\n\n The Commonwealth contests both conclusions. But\nHershey and Pinnacle argue that we need not address them\nbecause Section 16 of the Clayton Act and its attorneys’ fees\nprovision do not apply at all. Hershey and Pinnacle contend\nthat the preliminary injunction on which the Commonwealth\nrelies for its claim of attorneys’ fees was not entered “in an\naction under this section” as required for application of\nSection 16 of the Clayton Act. Instead, they argue, the\ninjunction was issued under the authority of Section 13(b) of\nthe FTC Act, which does not provide for attorneys’ fees. 14\nThus, they argue, the Commonwealth does not have any legal\nground to claim entitlement to attorneys’ fees on the basis of\n\n12\n See Buckhannon Bd. & Care Home, Inc. v. W. Va. Dep’t of\nHealth & Human Res., 532 U.S. 598, 605, 610 (2001).\n13\n 650 F.3d 223, 228-29 (3d Cir. 2011) (en banc).\n14\n 15 U.S.C. § 53(b).\n\n\n\n\n 7\n\fthe injunction (or the merger termination that it prompted) in\nthis case.\n\n We ultimately agree with Hershey and Pinnacle. We\nwill therefore assume without deciding that the\nCommonwealth is a prevailing party, leaving for another day\nthe questions of whether the Supreme Court’s rejection of the\ncatalyst theory controls claims for fees under Section 16 of\nthe Clayton Act and whether a preliminary injunction entered\npursuant to that section can constitute relief “on the merits.”\nOur sole focus here is to examine the Commonwealth’s claim\nthat it has a statutory basis to be awarded its fees.\n\n\n IV.\n\n We conclude that it does not. The Commonwealth\nclaims attorneys’ fees under Section 16 of the Clayton Act.\nThe District Court noted that, in ordering the injunction, our\nCourt “solely applied the standard outlined by Section 13(b)\nof the FTC Act.” 15 And, as noted above, Section 13(b) of the\nFTC Act makes no provision for attorneys’ fees. The District\nCourt nevertheless determined that the Commonwealth was\npotentially entitled to fees under Section 16 of the Clayton\nAct because the Commonwealth referenced that section when\nit joined with the FTC to seek a preliminary injunction\nagainst Hershey and Pinnacle, 16 and policy and Supreme\nCourt precedent supported the allowance of fees.\n\n\n\n\n15\n Hershey III, 2017 WL 1954398, at *2.\n16\n Id. at *3.\n\n\n\n\n 8\n\f The District Court’s initial conclusion that we ordered\nthe injunction under Section 13(b) of the FTC Act and not\nSection 16 of the Clayton act was correct, and its inquiry\nshould have ended there. The strongest indication that the\ninjunction rested solely on Section 13(b) of the FTC Act was\nthe standard that we used in ordering that injunction. When\nconsidering requests for injunctive relief under Section 16 of\nthe Clayton Act, courts generally apply the traditional four-\npart preliminary injunction standard that includes a\nconsideration of: (1) the likelihood of success on the merits;\n(2) the threat of irreparable harm in the absence of an\ninjunction; (3) the possibility of substantial harm to other\ninterested parties; and (4) the public interest. 17 In ordering\nthe injunction in Hershey II, we referenced the “traditional\nequity standard for injunctive relief,” 18 but we did not use it.\nInstead, we determined that the standard governing\ninjunctions under Section 13(b) of the FTC Act is different,\nand we went on to apply that different standard. 19\n\n In particular, and drawing directly from the statute, we\nsaid that the question of preliminary injunctive relief under\nSection 13(b) of the FTC Act is resolved by “weighing the\nequities and considering the Commission’s likelihood of\nultimate success” to determine whether “such action would be\nin the public interest.” 20 In doing so, we emphasized that the\n\n17\n See Holland v. Rosen, 895 F.3d 272, 285-86 (3d Cir. 2018)\ncert. denied 139 S. Ct. 440 (2018); see also Julian O. von\nKalinowski, Antitrust Laws and Trade Regulations §\n172.02[3][b] & n.60 (2d ed. 2018) (collecting cases).\n18\n Hershey II, 838 F.3d at 337.\n19\n Id.\n20\n Id. (quoting 15 U.S.C. § 53(b)).\n\n\n\n\n 9\n\fpublic interest standard in the second prong of this analysis\ndiffers from “the traditional equity standard for injunctive\nrelief.” 21 This assessment aligns with the judgment of other\nCourts of Appeals, which have concluded that the Section\n13(b) standard is not only different from, but easier to satisfy\nthan the traditional standard for injunctive relief that courts\napply to claims under Section 16 of the Clayton Act. 22\n\n In sum, in ordering the injunction on which the\nCommonwealth relies, we expressly applied Section 13(b) of\nthe FTC Act and its lower evidentiary bar instead of Section\n16 of the Clayton Act. Thus, to the extent that the\nCommonwealth can be said to have “prevailed,” it did so\nunder Section 13(b) of the FTC Act and not Section 16 of the\nClayton Act. For similar reasons, the only court of which we\nare aware to have addressed the issue has concluded that an\ninjunction issued under Section 13(b) of the FTC Act does\nnot trigger potential entitlement to attorneys’ fees under\n\n\n\n\n21\n Id.\n22\n See, e.g., FTC v. H.J. Heinz Co., 246 F.3d 708, 714 (D.C.\nCir. 2001) (explaining that Congress, in drafting Section\n13(b), “intended th[e Section 13(b)] standard to depart from .\n. . the then-traditional equity standard” so that the FTC “was\nnot held to the high thresholds applicable where private\nparties seek interim restraining orders”) (quotation marks\nomitted); FTC v. Affordable Media, LLC, 179 F.3d 1228,\n1233 (9th Cir. 1999) (recognizing that Section 13(b) “places a\nlighter burden on the Commission than that imposed on\nprivate litigants by the traditional equity standard”)(quotation\nmarks omitted).\n\n\n\n\n 10\n\fSection 16 of the Clayton Act. 23 We agree with that\nconclusion.\n\n The District Court relied on a number of factors in\nconcluding otherwise, but none is persuasive. The District\nCourt first pointed to the legislative history of the Clayton\nAct to justify its relevance here. It noted that “Congress\nintended that an individual plaintiff should not bear ‘the very\nhigh price of obtaining judicial enforcement of . . . the\nantitrust laws.’” 24 However, we have examined the extensive\nhistory of this Act and find nothing that clearly shows\nCongress’s intent to empower us to extend the fee-shifting\nprovision of the Clayton Act to cover an action for injunctive\nrelief under another statute. 25 As a result, we are not\npersuaded that the legislative history of the Clayton Act\nsupports the District Court’s conclusion.\n\n The District Court also cited Supreme Court precedent,\nMaher v. Gagne, 26 for the proposition that the fee-shifting\nprovisions of one statute can apply to pendent claims brought\nunder other statutes. Maher, however, does not support\n\n23\n See FTC v. Staples, Inc., 239 F. Supp. 3d 1, 4-5 (D.D.C.\n2017).\n24\n Hershey III, 2017 WL 1954398, at *3 (quoting H.R. Rep.\nNo. 94-499, part 1, at 19-20 (1976)).\n25\n See H.R. Rep. No. 94-499, pt. 1, at 18-20 (1976); see also\nBuckhannon Bd., 532 U.S. at 608 (holding that, “in view of\nthe ‘American Rule’ that attorney’s fees will not be awarded\nabsent explicit statutory authority, . . . [ambiguous] legislative\nhistory is clearly insufficient to alter the accepted meaning of\nthe statutory term”) (quotation marks omitted).\n26\n 448 U.S. 122 (1980).\n\n\n\n\n 11\n\fapplication of the Clayton Act’s fee-shifting provision in this\ncase. In Maher, the plaintiff brought claims under 42 U.S.C.\n§ 1983, alleging that Connecticut’s Aid to Families with\nDependent Children program violated Section 402(a)(7) of\nthe Social Security Act, 27 as well as the Equal Protection and\nDue Process Clauses of the Fourteenth Amendment. 28 After\nthe District Court approved a settlement between the parties,\nthe plaintiff sought attorneys’ fees under 42 U.S.C. § 1988,\nwhich authorizes fees for parties who prevail under Section\n1983 (among other statutes). Responding to objections that\nthe Eleventh Amendment prevented a federal court from\nordering fees against a state for statutory, non-civil rights\nclaims like the plaintiff’s claim under the Social Security Act,\nthe Supreme Court held that Section 1988 allows for “the\naward of fees in a case in which the plaintiff prevails on a\nwholly statutory, non-civil-rights claim pendent to a\nsubstantial constitutional claim or in one in which both a\nstatutory and a substantial constitutional claim are settled\nfavorably to the plaintiff without adjudication.” 29 The Court\nwent on to say: “The legislative history makes it clear that\nCongress intended fees to be awarded where a pendent\nconstitutional claim is involved, even if the statutory claim on\nwhich the plaintiff prevailed is one for which fees cannot be\nawarded under the Act.” 30\n\n Stretching the logic of Maher, the Commonwealth\nargues that it is entitled to attorneys’ fees because its claim\nunder Section 16 of the Clayton Act was pendent to the\n\n27\n 42 U.S.C. § 602(a)(7).\n28\n Maher, 448 U.S. at 125.\n29\n Id. at 132.\n30\n Id. at 132 n.15.\n\n\n\n\n 12\n\fFTC’s claim under Section 13(b) of the FTC Act. But the\nissue in Maher was fundamentally different. The issue in\nMaher was whether the plaintiff’s including the Social\nSecurity Act violation in its Section 1983 complaint\ndisqualified it from receiving fees authorized by Section\n1988. The theory was that the fees were only to vindicate\nviolations of the Fourteenth Amendment. But the Supreme\nCourt held that the plaintiff could recover attorneys’ fees\nunder Section 1988 because she had alleged violations of her\nFourteenth Amendment Due Process and Equal Protection\nrights. As for the fact that she had also alleged a purely\nstatutory violation (of the Social Security Act), the Supreme\nCourt held that this did not preclude an award of attorneys’\nfees under Section 1988 because this was pendant to the\nconstitutional claims. 31\n\n But—as we noted earlier—Section 16 of the Clayton\nAct specifies that a party must substantially prevail “[i]n any\naction under this section.” 32 This language limits the\napplication of Chapter 13’s fee-shifting provision to parties\nwho obtain relief under that section. 33 As we noted above,\nrequests for relief under that section are assessed on a\n\n31\n Id. at 132.\n32\n 15 U.S.C. § 26 (emphasis added).\n33\n See John T. ex rel. Paul T. v. Del. Cty. Intermediate Unit,\n318 F.3d 545, 560 (3d Cir. 2003) (“When the [Individuals\nwith Disabilities Education Act] fee-shifting provision\nauthorizes attorneys[’] fees ‘in any action or proceeding\nbrought under this section,’ it not only limits the universe to\nwhich it applies but also clarifies the type of proceeding on\nwhich a party must ‘prevail.’”) (first emphasis added)\n(quoting 20 U.S.C. § 1415(i)(3)).\n\n\n\n\n 13\n\fdifferent and more lenient standard than are requests for relief\nunder Section 16 of the Clayton Act, and we clearly decided\nthat the injunction should issue based on the standard of\nSection 13(b), not Section 16. Such differences were not\nevident in Maher. As also noted above, the legislative history\ndoes not justify extending the Clayton Act’s fee-shifting\nprovisions to other statutory schemes. For all of these\nreasons, we are not persuaded that Maher gives us any basis\nto extend the fee-shifting provisions of the Clayton Act to a\nclaim raised and adjudicated under the FTC Act. 34\n\n34\n The Commonwealth maintains that it did raise its claim\nunder the Clayton Act and that we acknowledged this in\nHershey II. It is true that we referenced both the Clayton Act\nand the FTC Act as a basis for the suit brought jointly by the\nCommonwealth and the FTC. In particular, we noted that the\nCommonwealth and the FTC “filed suit . . . under” both\nSection 16 of the Clayton Act and Section 13(b) of the FTC\nAct, Hershey II, 838 F.3d at 333, and we also stated that\n“[t]he District Court had jurisdiction” under both Section 16\nof the Clayton Act and Section 13(b) of the FTC Act, id. at\n335. But the Commonwealth does not have standing to\npursue a claim under the FTC Act, and these statements\nmerely declare that the Clayton Act gave them standing in\nthis case. The issue of standing aside, the facts remain that\nthe Commonwealth and the FTC litigated their request for an\ninjunction under Section 13(b) of the FTC Act and that we\nordered the injunction under that section and the more lenient\nstandard that applies thereto. As one court explained in\nrejecting the Commonwealth’s claim for attorneys’ fees in a\nsimilar case, the Commonwealth “cannot have it both ways”\nby “rid[ing] the FTC’s claim to a successful preliminary\ninjunction under the more permissive Section 13(b) standard\n\n\n\n\n 14\n\f Finally, the District Court raised concerns that failing\nto allow the Commonwealth to seek attorneys’ fees in this\nsituation would be contrary to the interests of judicial\neconomy. Forcing the Commonwealth to pursue a separate\ncase to bring a claim under Section 16, the District Court said,\ncould result in “duplicative litigation, separate filings, and\nrepetitive arguments” because this would be the only avenue\nfor claiming attorneys’ fees. 35 We are not persuaded that\nsuch concerns outweigh the plain language of the statutes.\n\n V.\n\n In sum, we conclude that the authority for this\ninjunction arose from Section 13(b) of the FTC Act, which—\nunlike Section 16 of the Clayton Act—does not provide for\nattorneys’ fees. Hence, for all of the foregoing reasons, the\nCommonwealth has no legal basis to claim attorneys’ fees in\nthis case and we will affirm the order of the District Court on\nthat ground.\n\n\n\n\nand then cit[ing] that favorable ruling as the sole justification\nfor fee-shifting under the more rigorous Clayton Act\nstandard.” Staples, 239 F. Supp. 3d at 5.\n35\n Hershey III, 2017 WL 1954398, at *3.\n\n\n\n\n 15\n[END_CASE]", "role": "user" } ]
4,583,850
Dieuland JEAN LOUIS, Petitioner v. ATTORNEY GENERAL UNITED STATES of America, Respondent
Dieuland Jean Louis v. Attorney General United States
2019-01-23
18-2082
U.S. Court of Appeals for the Third Circuit
{"judges": "Greenaway, Shwartz, Bibas", "parties": "", "opinions": [{"author": "BIBAS, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _______________\n\n No. 18-2082\n _______________\n\n DIEULAND JEAN LOUIS,\n Petitioner\n\n v.\n\nATTORNEY GENERAL UNITED STATES OF AMERICA,\n Respondent\n _______________\n\n On Petition for Review of a Decision of the\n United States Department of Justice\n Board of Immigration Appeals\n (Agency No. A206-596-150)\n Immigration Judge: Honorable Ramin Rastegar\n _______________\n\n Submitted Under Third Circuit L.A.R. 34.1(a)\n on November 14, 2018\n\n Before: GREENAWAY, JR., SHWARTZ, and BIBAS,\n Circuit Judges.\n\n (Filed: January 23, 2019)\n\f Raymond S. Vivino\n Vivino & Vivino\n 401 Hamburg Turnpike\n Suite 201\n Wayne, NJ 07474\n Counsel for Petitioner\n\n Tim Ramnitz\n Jennifer A. Singer\n John D. Williams\n United States Department of Justice\n Office of Immigration Litigation\n Room 10006\n P.O. Box 878\n Ben Franklin Station\n Washington, DC 20044\n Counsel for Respondent\n _______________\n\n OPINION OF THE COURT\n _______________\n\nBIBAS, Circuit Judge.\n A non-lawyer “immigration expert” advised Dieuland Jean\nLouis that he could miss his asylum hearing without conse-\nquence. I App. A6-7. So he did. But the “immigration expert”\nwas wrong—and an immigration judge relied on Jean Louis’s\nabsence to order his removal in absentia. Id.\n Jean Louis now contends that we should reopen that order\nbecause the non-lawyer’s advice qualifies as an exceptional\n\n\n\n\n 2\n\fcircumstance. But that is not the law. Exceptional circum-\nstances must be grave and beyond the applicant’s control. And\nholding the hearing without Jean Louis did not violate due pro-\ncess because he had the opportunity to attend. He chose not to.\nSo we will deny his petition for review.\n I. BACKGROUND\n Jean Louis, a native and citizen of Haiti, entered the United\nStates illegally. He later applied for asylum. While that appli-\ncation was pending, he married a U.S. citizen and sought citi-\nzenship on that basis.\n Jean Louis received a notice, dated August 2016, explain-\ning that he had to appear for an asylum hearing in June 2017.\nThe notice made clear that the immigration judge could hold\nthe hearing and remove Jean Louis if he did not attend.\n But Jean Louis, who does not speak English, wanted ad-\nvice. So he went to Gustave Thermitus. Thermitus is associated\nwith Caracol Financial. He is not a lawyer and does not belong\nto a legal organization. Still, Jean Louis thought Thermitus was\na lawyer.\n But Thermitus did not hold himself out as a lawyer. And\nJean Louis does not claim that Thermitus intentionally misled\nhim. According to Jean Louis, Thermitus held himself out as\n“an immigration expert that performed other work as well.” II\nApp. A6.\n Jean Louis asked Thermitus about his notice. Thermitus\ntold him he did not have to go to the hearing because he had\nanother path to citizenship: marriage. That advice was wrong.\n\n\n\n\n 3\n\f So Jean Louis did not attend his asylum hearing. The hear-\ning was held without him. Because he had conceded that he\nhad entered the country illegally, the judge found him remov-\nable and ordered him removed.\n Jean Louis then reached out to Thermitus. Thermitus said\nhe worked with a lawyer who could file a motion for Jean\nLouis. This was little comfort to Jean Louis, who until that mo-\nment had thought that Thermitus himself was a lawyer.\n So Jean Louis hired a real lawyer and moved to reopen his\nasylum case. The immigration judge denied the motion. The\nBoard of Immigration Appeals affirmed because no “excep-\ntional circumstances” had prevented Jean Louis from attending\nhis hearing. AR 3-4.\n The Board had jurisdiction under 8 C.F.R. § 1003.1(b)(3).\nWe have jurisdiction under 8 U.S.C. § 1252(a)(5). We review\nthe Board’s decision not to reopen an in absentia removal order\nfor abuse of discretion. Ramos-Olivieri v. Att’y Gen., 624 F.3d\n622, 625 (3d Cir. 2010). We review questions of law, including\nwhether an alien’s due process rights were violated, de novo.\nContreras v. Att’y Gen., 665 F.3d 578, 583 (3d Cir. 2012).\n II. A NON-LAWYER’S BAD ADVICE IS NOT AN EXCEP-\n TIONAL CIRCUMSTANCE\n\n The Board need reopen Jean Louis’s removal order only if\n“exceptional circumstances” prevented him from attending the\nhearing. 8 U.S.C. § 1229a(b)(5)(C) (also listing two other\ngrounds for rescinding a removal order, neither of which ap-\nplies here). He has not made that showing.\n\n\n\n\n 4\n\f To warrant reopening an in absentia removal order, excep-\ntional circumstances must be “beyond the control of the alien.”\n8 U.S.C. § 1229a(e)(1). The statute lists several examples: “bat-\ntery or extreme cruelty to the alien or any child or parent of the\nalien, serious illness of the alien, or serious illness or death of\nthe spouse, child, or parent of the alien.” Id. And it makes clear\nthat other circumstances do not count if they are “less compel-\nling” than these examples. Id. In short, exceptional circum-\nstances must not only be extreme, but also beyond the alien’s\ncontrol.\n Jean Louis’s situation does not meet this high bar. He fol-\nlowed bad advice from someone he trusted. It was his choice—\nand his alone—to seek out and follow that advice. So his cir-\ncumstances were not beyond his control. And his situation is a\nfar cry from the death, serious illness, or abuse outlined in the\nstatute. People make mistakes every day. But generally, mis-\ntakes do not rise to the extreme level of extreme cruelty, seri-\nous illness, or death. See id.\n Our precedent supports this result. We have held that fraud\ncommitted by lawyers and paralegals can qualify as an excep-\ntional circumstance. Borges v. Gonzales, 402 F.3d 398, 408 (3d\nCir. 2005). While some circuits have found that ineffective as-\nsistance of counsel qualifies too, we have neither adopted nor\nrejected that position. Id. But we have noted that the fraud al-\nleged in Borges was more extreme than a typical ineffective-\nassistance claim. Id.\n Jean Louis’s case differs from Borges in two important\nways. First, Thermitus is neither a lawyer nor a legal assistant.\nSo accepting Jean Louis’s argument would extend Borges far\n\n\n\n\n 5\n\fbeyond legal representation. Second, Jean Louis has not shown\nthat Thermitus defrauded him. Thermitus never pretended to\nbe a lawyer or offered to represent Jean Louis in court. But in\nBorges, fraud was “the crucial issue.” Id. Borges carefully lim-\nited its holding to fraud committed by lawyers and legal organ-\nizations. We will not extend Borges’s limited holding beyond\nthat boundary.\n III. IN ABSENTIA REMOVAL ORDERS DO NOT CATEGORI-\n CALLY VIOLATE DUE PROCESS\n\n Next, Jean Louis argues that his in absentia removal order\nviolates his due process rights. Due process indeed guarantees\naliens a hearing and an opportunity to be heard and present ev-\nidence. Abdulrahman v. Ashcroft, 330 F.3d 587, 596 (3d Cir.\n2003). But the immigration judge did not violate these rights\nby holding the hearing without Jean Louis. Jean Louis had an\nopportunity to attend his hearing, but chose not to.\n Jean Louis’s argument would have troubling consequences:\nIf we held that in absentia hearings violated due process, we\nwould effectively invalidate 8 U.S.C. § 1229a(b)(5)(A), which\nspecifically permits in absentia hearings. And we would per-\nversely let aliens avoid removal by not attending their hearings.\nSo in absentia removal orders do not categorically violate due\nprocess.\n Jean Louis relies on one of our precedents to make his due\nprocess argument, but this precedent is distinguishable. In\nCabrera-Perez v. Gonzales, an alien arrived for her hearing fif-\nteen to twenty minutes late. 456 F.3d 109, 117 (3d Cir. 2006).\nWe held that due process forbids treating slight lateness as a\n\n\n\n\n 6\n\ffailure to appear if, when the alien arrives, the judge “is either\nstill on the bench or recently retired.” Id. at 116. But coming\nlate is very different from not showing up at all. Id. at 117. Jean\nLouis did not show up at all, so Cabrera-Perez is inapt. His\nremoval order satisfied due process.\n *****\n We recognize that this result may seem harsh. Jean Louis\nrelied on someone whom he thought was an expert. But this\nsituation, while regrettable, is not exceptional. So we will deny\nhis petition.\n\n\n\n\n 7", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361103/", "author_raw": "BIBAS, Circuit Judge."}]}
GREENAWAY
SHWARTZ
BIBAS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583850/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Dieuland JEAN LOUIS, Petitioner v. ATTORNEY GENERAL UNITED STATES of America, Respondent\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-23\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _______________\n\n No. 18-2082\n _______________\n\n DIEULAND JEAN LOUIS,\n Petitioner\n\n v.\n\nATTORNEY GENERAL UNITED STATES OF AMERICA,\n Respondent\n _______________\n\n On Petition for Review of a Decision of the\n United States Department of Justice\n Board of Immigration Appeals\n (Agency No. A206-596-150)\n Immigration Judge: Honorable Ramin Rastegar\n _______________\n\n Submitted Under Third Circuit L.A.R. 34.1(a)\n on November 14, 2018\n\n Before: GREENAWAY, JR., SHWARTZ, and BIBAS,\n Circuit Judges.\n\n (Filed: January 23, 2019)\n\f Raymond S. Vivino\n Vivino & Vivino\n 401 Hamburg Turnpike\n Suite 201\n Wayne, NJ 07474\n Counsel for Petitioner\n\n Tim Ramnitz\n Jennifer A. Singer\n John D. Williams\n United States Department of Justice\n Office of Immigration Litigation\n Room 10006\n P.O. Box 878\n Ben Franklin Station\n Washington, DC 20044\n Counsel for Respondent\n _______________\n\n OPINION OF THE COURT\n _______________\n\nBIBAS, Circuit Judge.\n A non-lawyer “immigration expert” advised Dieuland Jean\nLouis that he could miss his asylum hearing without conse-\nquence. I App. A6-7. So he did. But the “immigration expert”\nwas wrong—and an immigration judge relied on Jean Louis’s\nabsence to order his removal in absentia. Id.\n Jean Louis now contends that we should reopen that order\nbecause the non-lawyer’s advice qualifies as an exceptional\n\n\n\n\n 2\n\fcircumstance. But that is not the law. Exceptional circum-\nstances must be grave and beyond the applicant’s control. And\nholding the hearing without Jean Louis did not violate due pro-\ncess because he had the opportunity to attend. He chose not to.\nSo we will deny his petition for review.\n I. BACKGROUND\n Jean Louis, a native and citizen of Haiti, entered the United\nStates illegally. He later applied for asylum. While that appli-\ncation was pending, he married a U.S. citizen and sought citi-\nzenship on that basis.\n Jean Louis received a notice, dated August 2016, explain-\ning that he had to appear for an asylum hearing in June 2017.\nThe notice made clear that the immigration judge could hold\nthe hearing and remove Jean Louis if he did not attend.\n But Jean Louis, who does not speak English, wanted ad-\nvice. So he went to Gustave Thermitus. Thermitus is associated\nwith Caracol Financial. He is not a lawyer and does not belong\nto a legal organization. Still, Jean Louis thought Thermitus was\na lawyer.\n But Thermitus did not hold himself out as a lawyer. And\nJean Louis does not claim that Thermitus intentionally misled\nhim. According to Jean Louis, Thermitus held himself out as\n“an immigration expert that performed other work as well.” II\nApp. A6.\n Jean Louis asked Thermitus about his notice. Thermitus\ntold him he did not have to go to the hearing because he had\nanother path to citizenship: marriage. That advice was wrong.\n\n\n\n\n 3\n\f So Jean Louis did not attend his asylum hearing. The hear-\ning was held without him. Because he had conceded that he\nhad entered the country illegally, the judge found him remov-\nable and ordered him removed.\n Jean Louis then reached out to Thermitus. Thermitus said\nhe worked with a lawyer who could file a motion for Jean\nLouis. This was little comfort to Jean Louis, who until that mo-\nment had thought that Thermitus himself was a lawyer.\n So Jean Louis hired a real lawyer and moved to reopen his\nasylum case. The immigration judge denied the motion. The\nBoard of Immigration Appeals affirmed because no “excep-\ntional circumstances” had prevented Jean Louis from attending\nhis hearing. AR 3-4.\n The Board had jurisdiction under 8 C.F.R. § 1003.1(b)(3).\nWe have jurisdiction under 8 U.S.C. § 1252(a)(5). We review\nthe Board’s decision not to reopen an in absentia removal order\nfor abuse of discretion. Ramos-Olivieri v. Att’y Gen., 624 F.3d\n622, 625 (3d Cir. 2010). We review questions of law, including\nwhether an alien’s due process rights were violated, de novo.\nContreras v. Att’y Gen., 665 F.3d 578, 583 (3d Cir. 2012).\n II. A NON-LAWYER’S BAD ADVICE IS NOT AN EXCEP-\n TIONAL CIRCUMSTANCE\n\n The Board need reopen Jean Louis’s removal order only if\n“exceptional circumstances” prevented him from attending the\nhearing. 8 U.S.C. § 1229a(b)(5)(C) (also listing two other\ngrounds for rescinding a removal order, neither of which ap-\nplies here). He has not made that showing.\n\n\n\n\n 4\n\f To warrant reopening an in absentia removal order, excep-\ntional circumstances must be “beyond the control of the alien.”\n8 U.S.C. § 1229a(e)(1). The statute lists several examples: “bat-\ntery or extreme cruelty to the alien or any child or parent of the\nalien, serious illness of the alien, or serious illness or death of\nthe spouse, child, or parent of the alien.” Id. And it makes clear\nthat other circumstances do not count if they are “less compel-\nling” than these examples. Id. In short, exceptional circum-\nstances must not only be extreme, but also beyond the alien’s\ncontrol.\n Jean Louis’s situation does not meet this high bar. He fol-\nlowed bad advice from someone he trusted. It was his choice—\nand his alone—to seek out and follow that advice. So his cir-\ncumstances were not beyond his control. And his situation is a\nfar cry from the death, serious illness, or abuse outlined in the\nstatute. People make mistakes every day. But generally, mis-\ntakes do not rise to the extreme level of extreme cruelty, seri-\nous illness, or death. See id.\n Our precedent supports this result. We have held that fraud\ncommitted by lawyers and paralegals can qualify as an excep-\ntional circumstance. Borges v. Gonzales, 402 F.3d 398, 408 (3d\nCir. 2005). While some circuits have found that ineffective as-\nsistance of counsel qualifies too, we have neither adopted nor\nrejected that position. Id. But we have noted that the fraud al-\nleged in Borges was more extreme than a typical ineffective-\nassistance claim. Id.\n Jean Louis’s case differs from Borges in two important\nways. First, Thermitus is neither a lawyer nor a legal assistant.\nSo accepting Jean Louis’s argument would extend Borges far\n\n\n\n\n 5\n\fbeyond legal representation. Second, Jean Louis has not shown\nthat Thermitus defrauded him. Thermitus never pretended to\nbe a lawyer or offered to represent Jean Louis in court. But in\nBorges, fraud was “the crucial issue.” Id. Borges carefully lim-\nited its holding to fraud committed by lawyers and legal organ-\nizations. We will not extend Borges’s limited holding beyond\nthat boundary.\n III. IN ABSENTIA REMOVAL ORDERS DO NOT CATEGORI-\n CALLY VIOLATE DUE PROCESS\n\n Next, Jean Louis argues that his in absentia removal order\nviolates his due process rights. Due process indeed guarantees\naliens a hearing and an opportunity to be heard and present ev-\nidence. Abdulrahman v. Ashcroft, 330 F.3d 587, 596 (3d Cir.\n2003). But the immigration judge did not violate these rights\nby holding the hearing without Jean Louis. Jean Louis had an\nopportunity to attend his hearing, but chose not to.\n Jean Louis’s argument would have troubling consequences:\nIf we held that in absentia hearings violated due process, we\nwould effectively invalidate 8 U.S.C. § 1229a(b)(5)(A), which\nspecifically permits in absentia hearings. And we would per-\nversely let aliens avoid removal by not attending their hearings.\nSo in absentia removal orders do not categorically violate due\nprocess.\n Jean Louis relies on one of our precedents to make his due\nprocess argument, but this precedent is distinguishable. In\nCabrera-Perez v. Gonzales, an alien arrived for her hearing fif-\nteen to twenty minutes late. 456 F.3d 109, 117 (3d Cir. 2006).\nWe held that due process forbids treating slight lateness as a\n\n\n\n\n 6\n\ffailure to appear if, when the alien arrives, the judge “is either\nstill on the bench or recently retired.” Id. at 116. But coming\nlate is very different from not showing up at all. Id. at 117. Jean\nLouis did not show up at all, so Cabrera-Perez is inapt. His\nremoval order satisfied due process.\n *****\n We recognize that this result may seem harsh. Jean Louis\nrelied on someone whom he thought was an expert. But this\nsituation, while regrettable, is not exceptional. So we will deny\nhis petition.\n\n\n\n\n 7\n[END_CASE]", "role": "user" } ]
4,584,869
Frank Andrew v. Todd Buskirk
2019-01-25
17-3011
U.S. Court of Appeals for the Third Circuit
{"judges": "Before: GREENAWAY, JR., RESTREPO, and BIBAS, Circuit Judges The petition for rehearing", "parties": "", "opinions": [{"author": "", "type": "010combined", "text": "UNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n ___________\n\n No. 17-3011\n ___________\n\n FRANK E. ANDREW,\n Appellant\n\n v.\n\n TODD BUSKIRK; FRANK LONGENBACH; ROBIN STANLEY\n _________________________________________\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE EASTERN DISTRICT OF PENNSYLVANIA\n (E.D. Pa. No. 5-16-cv-03851)\n ________________\n\n SUR PETITION FOR PANEL REHEARING\n ______________\n\n\nBefore: GREENAWAY, JR., RESTREPO, and BIBAS, Circuit Judges\n\n\n The petition for rehearing filed by Appellant in the above-entitled case having\n\nbeen submitted to the judges who participated in the decision of this Court, it is hereby\n\nORDERED that the petition for rehearing by the panel is GRANTED. Pursuant to 3d\n\nCir. I.O.P. 8.3.1, the panel’s previous non-precedential opinion and judgment filed\n\nNovember 19, 2018 are hereby VACATED. The panel will issue an opinion and\n\naccompanying judgment at a later date.\n\n By the Court,\n\n s/ L. Felipe Restrepo\n Circuit Judge\nDated: January 25, 2019\nJK/cc: All Counsel of Record", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362122/", "author_raw": ""}]}
GREENAWAY JR
RESTREPO
BIBAS
1
{"GREENAWAY JR": ", Circuit", "RESTREPO": ", Circuit", "BIBAS": ", Circuit"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584869/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Frank Andrew v. Todd Buskirk\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nUNITED STATES COURT OF APPEALS FOR THE THIRD CIRCUIT\n\n ___________\n\n No. 17-3011\n ___________\n\n FRANK E. ANDREW,\n Appellant\n\n v.\n\n TODD BUSKIRK; FRANK LONGENBACH; ROBIN STANLEY\n _________________________________________\n\n APPEAL FROM THE UNITED STATES DISTRICT COURT\n FOR THE EASTERN DISTRICT OF PENNSYLVANIA\n (E.D. Pa. No. 5-16-cv-03851)\n ________________\n\n SUR PETITION FOR PANEL REHEARING\n ______________\n\n\nBefore: GREENAWAY, JR., RESTREPO, and BIBAS, Circuit Judges\n\n\n The petition for rehearing filed by Appellant in the above-entitled case having\n\nbeen submitted to the judges who participated in the decision of this Court, it is hereby\n\nORDERED that the petition for rehearing by the panel is GRANTED. Pursuant to 3d\n\nCir. I.O.P. 8.3.1, the panel’s previous non-precedential opinion and judgment filed\n\nNovember 19, 2018 are hereby VACATED. The panel will issue an opinion and\n\naccompanying judgment at a later date.\n\n By the Court,\n\n s/ L. Felipe Restrepo\n Circuit Judge\nDated: January 25, 2019\nJK/cc: All Counsel of Record\n[END_CASE]", "role": "user" } ]
8,443,855
Frank E. ANDREW v. Todd BUSKIRK Frank Longenbach Robin Stanley
Andrew v. Buskirk
2019-01-25
No. 17-3011
U.S. Court of Appeals for the Third Circuit
{"judges": "", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/8415282/"}]}
0
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/8443855/
Published
0
1
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Frank E. ANDREW v. Todd BUSKIRK Frank Longenbach Robin Stanley\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\n\n[END_CASE]", "role": "user" } ]
4,585,443
Ever BEDOYA; Diego Gonzales; Manuel Decastro, on Behalf of Themselves and All Others Similarly Situated v. AMERICAN EAGLE EXPRESS INC., D/B/A AEX Group v. KV Service, LLC; M&J Express, LLC; A&D Delivery Express, LLC American Eagle Express, Inc., Appellant
Ever Bedoya v. American Eagle Express Inc
2019-01-29
18-1641
U.S. Court of Appeals for the Third Circuit
{"judges": "Greenaway, Shwartz, Bibas", "parties": "", "opinions": [{"author": "SHWARTZ, Circuit Judge.", "type": "010combined", "text": "PRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 18-1641\n _____________\n\n EVER BEDOYA; DIEGO GONZALES; MANUEL\n DECASTRO,\n on behalf of themselves and all others similarly situated\n\n v.\n\nAMERICAN EAGLE EXPRESS INC, d/b/a AEX GROUP\n\n v.\n\n KV SERVICE, LLC; M&J EXPRESS, LLC; A&D\n DELIVERY EXPRESS, LLC\n\n American Eagle Express, Inc.,\n Appellant\n ______________\n\n Appeal from the United States District Court\n for the District of New Jersey\n (D.C. No. 2-14-cv-02811)\n District Judge: Hon. Esther Salas\n ______________\n\f Argued November 14, 2018\n ______________\n\n Before: GREENAWAY, JR., SHWARTZ, and BIBAS,\n Circuit Judges.\n\n (Opinion Filed: January 29, 2019)\n\nHarold L. Lichten [ARGUED]\nLichten & Liss-Riordan\n729 Boylston Street\nSuite 2000\nBoston, MA 02116\n\nR. Andrew Santillo\nPeter D. Winebrake\nWinebrake & Santillo\n715 Twinning Road\nSuite 211, Twinning Office Center\nDresher, PA 19025\n\n Counsel for Plaintiff-Appellees\n\nJoseph C. DeBlasio [ARGUED]\nJackson Lewis\n220 Headquarters Plaza\nEast Tower, 7th Floor\nMorristown, NJ 07960\n\n Counsel for Defendant-Appellant\n\nAdina H. Rosenbaum\nPublic Citizen Litigation Group\n\n\n\n\n 2\n\f1600 20th Street, NW.\nWashington, DC 20009\n\n Counsel for Amicus Public Citizen Inc.\n\n\nChristopher W. Weber [ARGUED]\nEmily M. Bisnauth\nOffice of Attorney General of New Jersey\nDepartment of Law & Public Safety\nRichard J. Hughes Justice Complex\n25 Market Street\nP.O. Box 112\nTrenton, NJ 08625\n\n Counsel for Amicus New Jersey Department of Labor\n and Workforce Development\n\n\n ___________\n\n OPINION\n ___________\n\n\nSHWARTZ, Circuit Judge.\n\n Plaintiff delivery drivers Ever Bedoya, Diego Gonzalez,\nand Manuel Decastro (collectively, “the Drivers”) filed a\nputative class action against Defendant American Eagle\nExpress, Inc., (“AEX”), alleging that AEX misclassified them\nas independent contractors when they are actually employees\nunder the New Jersey Wage and Hour Law (“NJWHL”), N.J.\n\n\n\n\n 3\n\fStat. Ann. §§ 34:11-56a to -56a3, and the New Jersey Wage\nPayment Law (“NJWPL”), N.J. Stat. Ann. §§ 34:11-4.1 to -\n4:14. AEX moved for judgment on the pleadings pursuant to\nFed. R. Civ. P. 12(c), arguing that the Drivers’ claims are\npreempted by the Federal Aviation Authorization\nAdministration Act of 1994 (“FAAAA”), 49 U.S.C. §§ 14501-\n06. The District Court denied AEX’s motion and certified the\norder for interlocutory appeal. Because the FAAAA does not\npreempt the New Jersey law for determining employment\nstatus for the purposes of NJWHL and NJWPL, we will affirm\nthe order and remand for further proceedings.\n\n I\n\n AEX is a logistics company that provides delivery\nservices to various medical organizations. The Drivers are\nNew Jersey residents who make deliveries for AEX. The\nDrivers filed this putative class action against AEX seeking,\namong other things, a judgment declaring that they are\nemployees of AEX, rather than independent contractors, which\nentitles them to compensation under the NJWHL and NJWPL.1\nAEX moved for judgment on the pleadings, arguing that the\nFAAAA preempts the Drivers’ claims.\n\n The District Court denied AEX’s motion, Bedoya v.\nAm. Eagle Express, Civ. No. 14-2811, 2017 WL 4330351, at\n*1 (D.N.J. Sept. 29, 2017), reasoning that “[t]here is no clear\nindication” that Congress intended for the FAAAA to preempt\nstate wage laws, Dkt. 109 at 6, 10, and that the connection\nbetween regulation of AEX’s workforce and the “prices,\n\n 1\n The District Court has jurisdiction pursuant to 28\nU.S.C. § 1332(d).\n\n\n\n\n 4\n\froutes, and services” provided to its consumers is too\nattenuated to justify preempting claims under the NJWHL and\nNJWPL, id. at 8-9. We now consider AEX’s interlocutory\nappeal of the order denying the motion pursuant to 28 U.S.C.\n§ 1292(b). Bedoya, 2017 WL 4330351, at *1-4.\n\n II2\n\n A\n\n The question before us is whether the FAAAA preempts\nNew Jersey’s test for determining employment classification\nfor purposes of the NJWHL and NJWPL. Under this test,\nworkers performing services for a given company in exchange\nfor pay are deemed employees unless the company can\ndemonstrate each of the following:\n\n A. Such individual has been and will continue to\n be free from control or direction over the\n\n 2\n We review an order granting or denying a motion for\njudgment on the pleadings de novo. Zimmerman v. Corbett,\n873 F.3d 414, 417 (3d Cir. 2017) (citing Allah v. Al-Hafeez,\n226 F.3d 247, 249 (3d Cir. 2007)). Judgment will not be\ngranted unless the movant “clearly establishes there are no\nmaterial issues of fact, and he is entitled to judgment as a\nmatter of law.” Sikirica v. Nationwide Ins. Co., 416 F.3d 214,\n220 (3d Cir. 2005) (citation omitted). In considering a motion\nfor judgment on the pleadings, we must accept as true all facts\npresented in the complaint and answer and draw all reasonable\ninferences in favor of the non-moving party—here, the\nDrivers. Id. at 417-18. While AEX implores us to look beyond\nthe pleadings, we may not.\n\n\n\n\n 5\n\f performance of such service, both under his\n contract of service and in fact; and\n\n B. Such service is either outside the usual course\n of the business for which such service is\n performed, or that such service is performed\n outside of all the places of business of the\n enterprise for which such service is\n performed; and\n\n C. Such individual is customarily engaged in an\n independently established trade, occupation,\n profession, or business.\n\nN.J. Stat. Ann. §§ 43:21-19(i)(6)(A)-(C) (“New Jersey ABC\nclassification test”). Where a company successfully\ndemonstrates all three elements with respect to a worker, that\nworker qualifies as an independent contractor under the\nNJWHL and NJWPL. Hargrove v. Sleepy’s, LLC, 106 A.3d\n449, 458 (N.J. 2015). The company, in turn, is exempt from\nrequirements under those statutes with respect to the worker.\nId. For individuals classified as employees, however, the\nemploying company is subject to each statute’s obligations,\nincluding minimum and overtime wage requirements, N.J.\nStat. Ann. § 34:11-56a4, conditions regarding the time and\nmode of pay, N.J. Stat. Ann. § 34:11-4.2, 4.2a, and restrictions\non pay deductions, N.J. Stat. Ann. § 34:11-4.4. AEX contends\nthat the New Jersey ABC classification test is preempted by the\nFAAAA.\n\n\n\n\n 6\n\f B\n\n The preemption doctrine stems from the Supremacy\nClause, which provides that “the Laws of the United States . . .\nshall be the supreme Law of the Land . . . any Thing in the\nConstitution or Laws of any State to the Contrary\nnotwithstanding.” U.S. Const. art. VI, cl. 2. Thus, “Congress\n. . . has the power to preempt state law.” In re Vehicle Carrier\nServs. Antitrust Litig., 846 F.3d 71, 83 (3d Cir. 2017) (citing\nArizona v. United States, 567 U.S. 387 (2012)), cert denied sub\nnom., Alban v. Nippon Yusen Kabushiki Kaisha, 138 S. Ct.\n114 (2017). There are three categories of preemption: field\npreemption, conflict preemption, and express preemption.\nHolk v. Snapple Beverage Corp., 575 F.3d 329, 334 (3d Cir.\n2009) (citing Hillsborough County, Fla. v. Automated Med.\nLabs., Inc., 471 U.S. 707, 713 (1985)).\n\n Because preemption is an affirmative defense, we\nexamine the specific preemption defense asserted. In re\nVehicle, 846 F.3d at 84 (citing Oneok, Inc. v. Learjet, Inc., 135\nS. Ct. 1591 (2015)). AEX argues that New Jersey’s ABC\nclassification test is subject to express preemption under 49\nU.S.C. § 14501(c)(1). “Express preemption requires a[n]\nanalysis of whether ‘[s]tate action may be foreclosed by\nexpress language in a congressional enactment.’” Lupian v.\nJoseph Cory Holdings, LLC, 905 F.3d 127, 131 (3d Cir. 2018)\n(alteration in original) (quoting Lorillard Tobacco Co. v.\nReilly, 533 U.S. 525, 541 (2001)).\n\n In evaluating AEX’s argument, we first decide whether\nthe presumption against preemption applies. City of Columbus\nv. Ours Garage & Wrecker Serv., Inc., 536 U.S. 424, 438\n(2002) (applying the presumption against preemption in the\n\n\n\n\n 7\n\fFAAAA context). Under this presumption, “the historic police\npowers of the States” are “not to be superseded by [a] [f]ederal\n[a]ct unless that was the clear and manifest purpose of\nCongress.” Sikkelee v. Precision Airmotive Corp., 822 F.3d\n680, 687 (3d Cir. 2016) (quoting Wyeth v. Levine, 555 U.S.\n555, 565 (2009)). Thus, we “presume claims based on laws\nembodying state police powers are not preempted.” In re\nVehicle, 846 F.3d at 84; see also Farina v. Nokia Inc., 625 F.3d\n97, 116 (3d Cir. 2010).\n\n Many employment regulations, such as the wage laws\nat issue here, seek to ensure workers receive fair pay. Because\nthey protect workers, they are within New Jersey’s police\npower, and the presumption against preemption by federal law\napplies. See, e.g., Lupian, 905 F.3d at 131 (stating wage laws\nthat protect workers represent an exercise of “police power”);\nsee also Fort Halifax Packing Co. v. Coyne, 482 U.S. 1, 21\n(1987) (applying the presumption against preemption to a state\nlabor law regarding severance pay “since the establishment of\nlabor standards falls within the traditional police power of the\nState”).\n\n The presumption is rebutted where Congress had a\n“clear and manifest purpose” to preempt state laws. Sikkelee,\n822 F.3d at 687 (citation omitted); see also Cipollone v. Liggett\nGrp., Inc., 505 U.S. 504, 516 (1992) (directing courts to\nexamine congressional intent, the “ultimate touchstone” in\ndiscerning the preemptive scope of a statute (internal quotation\nmarks and citation omitted)). To determine Congress’\npurpose, we look to the plain language of the statute and, if\nnecessary, to the statutory framework as a whole. Medtronic,\nInc. v. Lohr, 518 U.S. 470, 486 (1996) (citation omitted).\nThus, we next examine Congress’ purpose in enacting the\n\n\n\n\n 8\n\fFAAAA and the Airline Deregulation Act of 1978 (“ADA”),\n49 U.S.C. §§ 40101-130, an earlier statute with a similar\npreemption provision.\n\n C\n\n In 1978, following a long period of heightened\nregulation, Congress enacted the ADA, which sought to\nderegulate the air-travel industry to “maxim[ize] reliance on\ncompetitive market forces.” Morales v. Trans World Airlines,\nInc., 504 U.S. 374, 378 (1992) (quoting 49 U.S.C. App. §\n1302(a)(4)). To ensure that this objective would not be\nfrustrated by state regulation, Congress included a preemption\nprovision providing that “no State . . . shall enact or enforce\nany law . . . relating to rates, routes, or services of any air\ncarrier.” Id. at 420 (Stevens, J., dissenting) (quoting 49 U.S.C.\nApp. § 1305(a)).\n\n Congress enacted similar laws focused on deregulating\ninterstate trucking, culminating with the passage of the\nFAAAA in 1994. Lupian, 905 F.3d at 132-33. Via the\nFAAAA, Congress sought to “level the playing field” between\nair carriers and motor carriers so that both could benefit from\nfederal deregulation. H.R. Conf. Rep. No. 103-677, at 88\n(1994); see also Californians for Safe & Competitive Dump\nTruck Transp. v. Mendonca, 152 F.3d 1184, 1187-88 (9th Cir.\n1998) (detailing FAAAA legislative history). The FAAAA\ncontains a preemption provision modeled after the ADA’s,\nproviding, with limited exceptions, that:\n\n a State . . . may not enact or enforce a law,\n regulation, or other provision having the force\n and effect of law related to a price, route, or\n\n\n\n\n 9\n\f service of any motor carrier . . . with respect to\n the transportation of property.\n\n49 U.S.C. § 14501(c)(1). Because of the parallels between the\nADA and FAAAA, ADA cases are instructive regarding the\nscope of FAAAA preemption. See Rowe v. N.H. Motor\nTransp. Ass’n, 552 U.S. 364, 370 (2008) (analyzing FAAAA\npreemption using ADA cases as guidance). As with the ADA,\nthe FAAAA preemption provision’s central objective is to\navoid frustrating the statute’s deregulatory purpose by\npreventing states from imposing “a patchwork of state service-\ndetermining laws.” Dan’s City Used Cars, Inc. v. Pelkey, 569\nU.S. 251, 264 (2013) (quoting Rowe, 552 U.S. at 373). The\nFAAAA, however, has a qualifier that is absent from the ADA:\nthe preempted state law must relate to prices, routes, or services\n“with respect to the transportation of property.” 49 U.S.C.\n§ 14501(c)(1). The Supreme Court has recognized that this\nlanguage “massively limits the scope of preemption ordered by\nthe FAAAA.” Dan’s City, 569 U.S. at 261 (internal citation\nand quotation marks omitted).\n\n Further insight into the limits of FAAAA preemption\ncomes from the subjects Congress considered when enacting\nthat statute. “Congress identified ten jurisdictions (nine states\nand the District of Columbia . . . ) that did not regulate intrastate\nprices, routes, and services.” Cal. Trucking Ass’n v. Su, 903\nF.3d 953, 967 (9th Cir. 2018) (citing Mendonca, 152 F.3d at\n1187). By implication, Congress determined that the laws then\nin existence in those jurisdictions did not contravene its\nderegulatory goals and thus were not preempted. Id.\n\n The Supreme Court has also articulated several\nprinciples that inform us about the breadth of FAAAA\n\n\n\n\n 10\n\fpreemption. First, the “related to” language from the FAAAA\npreemption clause gives it a broad scope, encompassing any\nstate actions that have “a connection with, or [make] reference\nto . . . rates, routes, or services” of a motor carrier. Nw., Inc.\nv. Ginsberg, 572 U.S. 273, 280-81 (2014) (internal quotation\nmarks and citation omitted) (interpreting the ADA). While this\nlanguage covers any state law that has a connection with or\nrefers to “price[s], route[s], [or] service[s,]” id. at 280, “the\nbreadth of the words ‘related to’ does not mean the sky is the\nlimit,” Dan’s City, 569 U.S. at 260. Drawing from case law\nexamining similar wording in the preemption provision of the\nEmployee Retirement Income Security Act of 1974, 29 U.S.C.\n§ 1144(a), see, e.g., Morales, 504 U.S. at 383-84, the Supreme\nCourt has observed that reading the phrase “related to” with\n“uncritical literalism” would render preemption an endless\nexercise, Dan’s City, 569 U.S. at 260-61 (citation omitted),\nbecause “everything [is] relat[ed] to everything else in some\nmanner[,]” Schwann v. FedEx Ground Package Sys., Inc., 813\nF.3d 429, 436 (1st Cir. 2016) (citing N.Y. State Conference of\nBlue Cross & Blue Shield Plans v. Travelers Ins. Co., 514 U.S.\n645, 655 (1955)).\n\n Second, FAAAA preemption reaches laws that affect\nprices, routes, or services even if the effect “is only indirect.”\nRowe, 552 U.S. at 370 (quoting Morales, 504 U.S. at 386).\nHowever, where a law’s impact on carrier prices, routes, or\nservices is so indirect that the law affects them “in only a\ntenuous, remote, or peripheral . . . manner,” the law is not\npreempted. Dan’s City, 569 U.S. at 261 (quoting Rowe, 552\nU.S. at 371); Morales, 504 U.S. at 390 (quoting Shaw v. Delta\nAir Lines, Inc., 463 U.S. 85, 100 n.21 (1983)).\n\n\n\n\n 11\n\f Finally, preemption occurs where a state law has “a\n‘significant impact’ on carrier rates, routes, or services.”3\nRowe, 552 U.S. at 375 (emphasis omitted) (quoting Morales,\n504 U.S. at 390).\n\n Mindful of these principles, we next review the case law\nfor guidance concerning whether a law has a direct or indirect\neffect and whether it has a significant or insignificant effect.\nFrom our review, we identify factors courts examine and set\nforth those factors that may shed light on a law’s directness and\nthose that may reflect the significance of the law’s effect on the\nregulated entities at issue.\n\n D\n\n Neither the Supreme Court nor our Court has recited\nprecise standards for evaluating directness or significance, but\ncases addressing the issue provide some guidance. For\nexample, the Supreme Court has held that consumer protection\nand fraud laws used to regulate frequent-flyer programs could\ndirectly and significantly affect prices and services and are thus\npreempted. See Am. Airlines, Inc. v. Wolens, 513 U.S. 219,\n223 (1995); Morales, 504 U.S. at 388-89. Similarly, the Court\ndetermined that a Maine law requiring a specific procedure to\nverify the recipient of tobacco deliveries was preempted by the\nFAAAA because it dictated a service that tobacco motor\ncarriers were required to provide for property they transported.\nRowe, 552 U.S. at 372. In addition, we recently observed that\n\n 3\n The Supreme Court also noted that “it makes no\ndifference whether a state law is ‘consistent’ or ‘inconsistent’\nwith federal regulation.” Rowe, 552 U.S. at 370 (quoting\nMorales, 504 U.S. at 386-87).\n\n\n\n\n 12\n\fthe FAAAA’s “preemption clause undoubtedly applies, for\nexample, to state laws directly restricting types of goods that\ncan be carried by trucks, tariffs, and barriers to entry.” Lupian,\n905 F.3d at 135; H.R. Conf. Rep. No. 103-677, at 86 (1994).\n\n On the other hand, the FAAAA itself, the Supreme\nCourt, and the courts of appeals have identified laws that are\ntoo “tenuous, remote, or peripheral” from carrier prices, routes,\nand services to trigger preemption. See, e.g., Rowe, 552 U.S.\nat 371; Dilts v. Penske Logistics, LLC, 769 F.3d 637, 646 (9th\nCir. 2014). The FAAAA explicitly exempts from preemption\nlaws governing motor vehicle safety, local route controls based\non vehicle size and weight, and driver insurance requirements.4\n49 U.S.C. § 14501(c)(2)(A). The Supreme Court has stated\nthat the FAAAA does not preempt laws prohibiting\nprostitution, gambling, and “obscene depictions,” Morales,\n504 U.S. at 390, or those addressing zoning, Dan’s City, 569\nU.S. at 264. We have observed that “garden variety\nemployment claim[s]” evade ADA and FAAAA preemption\nbecause they are “too remote and too attenuated” from carrier\nprices, services, or routes. Lupian, 905 F.3d at 134 (quoting\nGary v. Air Grp., Inc., 397 F.3d 183, 189 (3d Cir. 2005)). As\nrelevant to this case, we recently held that wage claims under\nthe Illinois Wage Payment and Collection Act (“IWPCA”),\n820 Ill. Comp. Stat. 115/1-115/15, are not preempted under the\nFAAAA because they are “too far removed from the statute’s\n\n 4\n The House of Representatives Conference Report\nspecifies that the list provided in 49 U.S.C. § 14501(c)(2) and\n(3) is “not intended to be all inclusive, but merely to specify\nsome of the matters which are not ‘prices, rates or services’ and\nwhich are therefore not preempted.” H.R. Conf. Rep. No. 103-\n677, at 83.\n\n\n\n\n 13\n\fpurpose to warrant preemption.” Lupian, 905 F.3d at 136.\nMany of our sister circuits have similarly held that the FAAAA\nand ADA do not preempt state employment laws. See, e.g.,\nAllied Concrete & Supply Co. v. Baker, 904 F.3d 1053, 1068\n(9th Cir. 2018) (holding California prevailing wage law for\nworkers on public projects not preempted); Su, 903 F.3d at 957\n(holding California common law test for employee versus\nindependent contractor status not preempted); Costello v.\nBeavEx, Inc., 810 F.3d 1045, 1048 (7th Cir. 2016) (holding\nIllinois wage law not preempted), cert. denied, 137 S. Ct. 2289\n(2017); Amerijet Int’l, Inc. v. Miami-Dade County, Fla., 627\nF. App’x 744, 751 (11th Cir. 2015) (holding Miami-Dade\nCounty living wage ordinance as applied to air carriers not\npreempted); Dilts, 769 F.3d at 647 (holding California meal\nand rest-break laws not preempted); Mendonca, 152 F.3d at\n1189 (holding California wage law not preempted).\n\n From the language of the FAAAA preemption provision\nand these cases, we can distill several factors courts should\nconsider when deciding whether a particular state law is\nFAAAA-preempted. First, courts should examine whether the\nstate law at issue applies to all businesses or whether it focuses\non motor carriers. Laws that are directed at “members of the\ngeneral public” and that are not targeted at motor carriers are\nusually viewed as not having a direct effect on motor carriers.\nRowe, 552 U.S. at 375.\n\n Even targeted laws, however, are not necessarily\npreempted. We know from the FAAAA itself that state laws\nthat may target motor carrier safety and insurance, or restrict\nlocal routes based on vehicle size and weight, are not\npreempted. 49 U.S.C. § 14501(c)(2). Conversely, laws of\ngeneral applicability may nonetheless be preempted where\n\n\n\n\n 14\n\fthey have a significant impact on the services a carrier\nprovides. See, e.g., DiFiore v. Am. Airlines Inc., 646 F.3d 81,\n88-89 (1st Cir. 2011) (holding generally applicable state tip\nlaw as applied to airlines preempted under the ADA because it\n“directly regulate[d] how an airline service is performed and\nhow its price is displayed to customers”). Thus, whether a law\nis applicable to every business or targets carriers is a helpful\nbut nondispositive factor for determining whether a law has a\ndirect effect on motor carriers’ prices, routes, or services.\nMorales, 504 U.S. at 386.\n\n Second, courts should consider whether the law\naddresses the carrier-employee relationship as opposed to the\ncarrier-customer relationship. “[G]enerally applicable state\nlaws that affect the carrier’s relationship with its customers\n[differ from] those that affect the carrier’s relationship with its\nworkforce.” Costello, 810 F.3d at 1054; see also Su, 903 F.3d\nat 961-63 (noting same dichotomy); DiFiore, 646 F.3d at 88\n(preempting a Massachusetts law prohibiting employer from\ncollecting fee advertised as “service charge” because the law\nregulates how a company performs services for its customers\nand “not merely how the airline behaves as an employer or\nproprietor”).\n\n The Court of Appeals for the Seventh Circuit provides\na useful analysis explaining why laws governing an employer’s\nrelationship with its employees have too remote an impact to\nbe preempted. S.C. Johnson & Son, Inc. v. Transp. Corp. of\nAm., Inc., 697 F.3d 544, 558 (7th Cir. 2012) (citing Mendonca,\n152 F.3d at 1189). The court examines whether the challenged\nstate law regulates matters needed to operate the business,\nwhich it calls resource inputs, as opposed to laws governing\nthe goods or services the business puts out, which it calls\n\n\n\n\n 15\n\fproduct outputs. Id. The product outputs of the motor carrier\nindustry are the services it provides—transportation of\nproperty from origin to destination. Id. The FAAAA’s focus\non prices, routes, and services shows that the statute is\nconcerned with the industry’s production outputs, and seeks to\nprotect them from state regulation.\n\n Resource inputs, on the other hand, are the resources\nnecessary for a business to create product outputs, including\n“labor, capital, and technology,” which may be regulated by\nvarious laws. Id. “For example, labor inputs are affected by a\nnetwork of labor laws, including minimum wage laws, worker-\nsafety laws, anti-discrimination laws, and pension regulations.\nCapital is regulated by banking laws, securities rules, and tax\nlaws, among others. Technology is heavily influenced by\nintellectual property laws.” Id. Although laws that regulate\ninputs may impact costs and may in turn affect prices charged\nand services provided to customers, “no one thinks that the\nADA or the FAAAA preempts these [regulations] and the\nmany comparable state laws[.]” Id. That is because,\nnotwithstanding the state laws’ indirect effects, they “operate\none or more steps away from the moment at which the firm\noffers its customer[s] a service for a particular price” and\ntherefore have too “remote” an effect on prices, routes, and\nservices to be the intended target of preemption. Id. (internal\ncitations omitted); see also Su, 903 F.3d at 966 (stating that\ncourts should examine “where in the chain of a motor carrier’s\nbusiness [the state law] is acting to compel a certain result (e.g.,\nconsumer or work force), and what result it is compelling (e.g.,\ncertain wage, non-discrimination, a specific system of\ndelivery, a specific person to perform the delivery)”); Costello,\n810 F.3d at 1055 (embracing S.C. Johnson, 697 F.3d at 558).\nIn short, laws regulating labor inputs, such as wage laws, have\n\n\n\n\n 16\n\ftoo remote an effect on the price the company charges, the\nroutes it uses, and service outputs it provides and are less likely\nto be preempted by the FAAAA.\n\n Third, courts should consider whether the law binds the\ncarrier to provide a particular price, route, or service. As\ndiscussed above, the Supreme Court held that Maine’s\nidentification requirements for tobacco deliveries required a\nmotor carrier transporting tobacco to provide a particular\nservice. Rowe, 552 U.S. at 372. Similarly, the Court of\nAppeals for the First Circuit determined that Massachusetts’\nABC test for classifying employees in effect bound the carrier\nto provide its services using employees rather than independent\ncontractors. Schwann, 813 F.3d at 437. Under Massachusetts’\nindependent contractor statute, only workers who perform a\nservice that is outside the employer’s usual course of business\nmay be classified as independent contractors. Id. (quoting\nMass. Gen. Laws ch. 149, § 148B(a)(2)). Thus, application of\nMassachusetts’ test “in substance, bar[red] [the carrier at issue]\nfrom using any individuals as full-fledged independent\ncontractors.” Id. In other words, the Massachusetts test\nessentially foreclosed the independent contractor classification\nof any of the carrier’s workers performing delivery services\nbecause such services were within the carrier’s usual course of\nbusiness. Id. As a result, the Massachusetts statute bound the\ncarrier to provide its services using employees and not\nindependent contractors.\n\n The same was not true with laws that do not dictate a\nprice, route, or service. For example, the Court of Appeals for\nthe Ninth Circuit analyzed whether the FAAAA preempted a\nCalifornia law that requires employers to provide meal and rest\nbreaks, reviewing, among other factors, whether the law bound\n\n\n\n\n 17\n\fthe carrier to specific prices, routes, or services. Dilts, 769 F.3d\nat 649-50. The court held that the FAAAA did not preempt\nCalifornia’s meal and rest-break laws. Id. The court relied\npartially on the fact that the California laws did not “set prices,\nmandate or prohibit certain routes, or tell motor carriers what\nservices they may or may not provide, either directly or\nindirectly.” Id. at 647. Put simply, the law at issue did “not\n‘bind’ motor carriers to specific prices, routes, or services.”5\nId. (citation omitted).\n\n Finally, courts examining a preemption challenge to a\nstate law should be mindful of Congress’ goal of avoiding a\n“patchwork” of differing state “service-determining laws,”\nwhich could undermine its “major legislative effort to leave\n[decisions regarding the provision of services] to the\ncompetitive marketplace.” Rowe, 552 U.S. at 373 (citing H.R.\nConf. Rep. No. 103-677, at 87 (1994)). This goal does not\nconstitute a categorical imperative to free motor carriers of all\nstate regulation. Rather, the plain language of the FAAAA,\nand its preemption of only laws “relat[ing] to” carrier “price[s],\nroute[s], or service[s],” 49 U.S.C. § 14501(c)(1), demonstrates\nthat Congress was concerned only with a limited set of state\n\n 5\n AEX characterizes Dilts as impermissibly relying on\nthis “binds to” test to conclude that the FAAAA did not\npreempt California’s meal and rest break laws, arguing that\nsuch a test construes the scope of FAAAA preemption too\nnarrowly. While relying solely on such a “binds to” test may\nnarrow FAAAA preemption to an unacceptable degree, Dilts\nmerely recognized that the “binds to” test provides one of\nseveral possible avenues to demonstrate that a state law has a\nsignificant effect on carrier prices, routes, or services. Dilts,\n769 F.3d at 649.\n\n\n\n\n 18\n\flaws. Dilts, 769 F.3d at 646-47. Thus, “[t]he fact that laws\nmay differ from state to state is not, on its own, cause for\nFAAAA preemption.” Id. at 647. Laws that are “more or less\nnationally uniform,” Chambers v. RDI Logistics, Inc., 65\nN.E.3d 1, 11-12 (Mass. 2016), are less likely to pose the kind\nof state law interference FAAAA preemption seeks to avoid.\n\n In sum, to assess the directness of a law’s effect on\nprices, routes, or services, courts should examine whether the\nlaw: (1) mentions a carrier’s prices, routes, or services;\n(2) specifically targets carriers as opposed to all businesses;\nand (3) addresses the carrier-customer relationship rather than\nnon-customer-carrier relationships (e.g., carrier-employee). If\na law has a direct impact on carriers’ prices, routes, or services\nwith respect to the transportation of property, then it is\npreempted unless it falls within one of the statutory exceptions.\nThough we can draw no firm line between laws whose effects\non rates, routes, or services are indirect and laws whose effects\nare “tenuous, remote, or peripheral,” these factors, and perhaps\nother considerations, will guide courts in the inquiry.\n\n To assess whether a law has a significant effect on a\ncarrier’s prices, routes, or services, courts should consider\nwhether: (1) the law binds a carrier to provide or not provide a\nparticular price, route, or service; (2) the carrier has various\navenues to comply with the law; (3) the law creates a\npatchwork of regulation that erects barriers to entry, imposes\ntariffs, or restricts the goods a carrier is permitted to transport;\nand (4) the law existed in one of the jurisdictions Congress\ndetermined lacked laws that regulate intrastate prices, routes,\nor services and thus, by implication, is a law Congress found\nnot to interfere with the FAAAA’s deregulatory goal. Other\nfactors may also lead a court to decide that a state law has a\n\n\n\n\n 19\n\fsignificant effect where the law undermines Congress’ goal of\nhaving competitive market forces dictate prices, routes, or\nservices of motor carriers.6\n\n E\n\n We have examined each of these considerations and\nconclude that New Jersey’s ABC classification test is not\npreempted as it has neither a direct, nor an indirect, nor a\nsignificant effect on carrier prices, routes, or services.\n\n 6\n Before the Supreme Court’s rulings in Rowe and\nDan’s City, our Court once framed the inquiry—albeit in the\ncontext of whether a defamation claim was preempted under\nthe ADA (a question we answered in the negative, holding that\nthe defamation claim was not preempted)—as whether the law\nor claim in question would “frustrate[] deregulation by\ninterfering with competition through public utility-style\nregulation.” Taj Mahal Travel, Inc. v. Delta Airlines, Inc., 164\nF.3d 186, 194 (3d Cir. 1998) (citation omitted). Elaborating\non regulation in a “public utility sense” in the context of airline\nservices, our Court said that regulations of “the frequency and\nscheduling of transportation” and “the selection of markets”\nare public-utility styled regulations (which would thus be\npreempted under the ADA), whereas “provision of in-flight\nbeverages, personal assistance to passengers, the handling of\nluggage, and similar amenities” are not services in a “public\nutility sense,” and thus could be regulated, for instance through\nstate implementation of a duty to exercise reasonable care, the\nviolation of which could give rise to ordinary tort claims. Id.\nat 193 (quoting Charas v. Trans World Airlines, Inc., 160 F.3d\n1259, 1261, 1265-66 (9th Cir. 1998) (en banc)).\n\n\n\n\n 20\n\f Any effect New Jersey’s ABC classification test has on\nprices, routes, or services is tenuous. The test does not mention\ncarrier prices, routes, or services, nor does it single out carriers.\nIndeed, the test applies to all businesses as part of the\n“backdrop” they “face in conducting their affairs.” Lupian,\n905 F.3d at 136; see also Dilts, 769 F.3d at 646 (describing a\nstate employment law as a “background regulation[]”). The\ntest also does not regulate carrier-customer interactions or\nother product outputs. Rather, it only concerns employer-\nworker relationships. Laws governing how an employer pays\nits workers do not “directly regulate[] how [a carrier’s] service\nis performed[;]” they merely dictate how a carrier “behaves as\nan employer[.]” DiFiore, 646 F.3d at 88. As a result, the test\nis “steps removed” from regulating customer-carrier\ninteractions through prices, routes, or services. Costello, 810\nF.3d 1054 (quoting Dilts, 769 F.3d at 646).\n\n The New Jersey ABC classification test does not have a\nsignificant effect on prices, routes, or services either. The test\ndoes not bind AEX to a particular method of providing services\nand thus it is unlike the preempted Massachusetts law at issue\nin Schwann, 813 F.3d 429. The Massachusetts statute does not\ninclude New Jersey’s alternative method for reaching\nindependent contractor status—that is, by demonstrating that\nthe worker provides services outside of the putative employer’s\n“places of business.” N.J. Stat. Ann. § 43:21-19(i)(6)(B).\nThus, if the other prongs of the New Jersey classification test\nare met, the test allows an employer to classify a worker as an\nindependent contractor if it shows that the worker either\nprovides a service that is “outside the [employer’s] usual\ncourse of business . . . or [performs such service] outside of all\n\n\n\n\n 21\n\fthe places of business of [the employer].” Id.7 No part of the\nNew Jersey test categorically prevents carriers from using\nindependent contractors. As a result, the state law at issue here\ndoes not mandate a particular course of action—e.g., requiring\ncarriers to use employees rather than independent\ncontractors—and it offers carriers various options to comply\nwith New Jersey employment law.8\n\n 7\n AEX focuses its argument on the B prong of the New\nJersey test, but also asserts that the A and C prongs of the test\nare preempted. AEX cites no case holding that prong A or C\nis preempted under either the FAAAA or the ADA. This is not\nsurprising given the legion of cases holding that the A and C\nprongs are not FAAAA-preempted. See, e.g., Vargas v. Spirit\nDelivery & Distrib. Servs., Inc., 245 F. Supp. 3d 268, 281-84\n(D. Mass. 2017); DaSilva v. Border Transfer of Mass., Inc.,\n227 F. Supp. 3d 154, 159-60 (D. Mass. 2017); Portillo v. Nat’l\nFreight, Inc., Civ. No. 15-7908, 2016 WL 5402215, at *5-6\n(D.N.J. Sept. 26, 2016); Chambers v. RDI Logistics, Inc., 65\nN.E.3d 1, 11-12 (Mass. 2016). AEX also provides no reason\nwhy these prongs are preempted and in fact does not\nindividually analyze them. Thus, AEX has failed to carry its\nburden to demonstrate that the affirmative defense of FAAAA\npreemption applies to these prongs.\n 8\n AEX makes much of the fact that the Costello and\nLupian courts observed that certain aspects of the IWPCA\nclassification provision could be contracted around (i.e.,\nemployees could enter into contracts with carriers to allow\ncertain paycheck deductions), Lupian, 905 F.3d at 135 n.12,\nwhereas neither the New Jersey test nor the Massachusetts test\nallows the same contractual avoidance. Contrary to AEX’s\nargument, this does not make the current case more analogous\n\n\n\n\n 22\n\f AEX argues that applying the New Jersey law may\nrequire it to shift its model away from using independent\ncontractors, which will increase its costs, and in turn, its prices.\nSpecifically, AEX asserts that if it can no longer use\nindependent contractors to perform its delivery services, then\nit will be forced to recruit employees, bring on a human\nresources department to manage them, acquire and maintain a\nfleet of vehicles and pay expense reimbursements, provide\nfringe benefits, plan and dictate delivery routes and timing, and\npay overtime wages and employment taxes. Our Court and our\nsister circuits have rejected similar lists of conclusory impacts.\nLupian, 905 F.3d at 135-36; Costello, 810 F.3d at 1056;\nMendonca, 152 F.3d at 1189. Though AEX correctly states\nthat it need not proffer empirical evidence to support its\nassertions of significant impact at the pleading stage, see, e.g.,\nCostello, 810 F.3d at 1055 (citing Rowe, 552 U.S. at 373-74),\n\n\nto Schwann than to Costello and Lupian. Though Costello and\nLupian correctly took the IWPCA contractual loophole into\naccount, neither court relied on it. See Lupian, 905 F.3d at 136\nn.12 (observing that the Costello court “noted” the contractual\nallowance in the IWPCA); Costello, 810 F.3d at 1057 (noting\nin a single sentence that the IWPCA’s prohibition on\ndeductions from wages can be contracted around, ultimately\nholding that the IWPCA is not “related to a price, route, or\nservice of any motor carrier”). Moreover, while a contractual\ncircumvention option may provide another route for\ncompliance, weighing against FAAAA preemption, it is not the\nonly way a state statute can afford carriers some flexibility.\nHere, the New Jersey ABC classification test gives carriers\noptions; it does not need to provide a contractual workaround\nto avoid preemption.\n\n\n\n\n 23\n\fit does not provide even a logical connection between the\napplication of New Jersey’s ABC classification test and the list\nof new costs it would purportedly incur.9\n\n AEX’s argument that it may be subject to other legal\nrequirements arising from reclassification, citing only the\nAffordable Care Act,10 is equally unavailing. In the words of\nthe Costello court, “[c]onspicuously absent from [the\ncompany’s] parade of horrors is any citation of authority\nshowing that it would be required to comply with [other]\nfederal and state laws.” Id. at 1056. Instead, AEX “rel[ies] on\nconclusory allegations that compliance with the [NJWHL and\nNJWPL] will require [AEX] to switch its entire business model\n. . . [but w]e see no basis for concluding that [New Jersey law]\nwould require that change given that the federal employment\nlaws and other state labor laws [may] have different tests” for\ndetermining whether someone is an employee under a specific\nstatute. Id. (citations omitted).\n\n Furthermore, while “[w]e have no doubt that the\ndisruption of a labor model—especially after services have\nbeen performed—could have negative financial and other\nconsequences for an employer,” Lupian, 905 F.3d at 136, this\nimpact on the employer does not equate to a significant impact\non Congress’ goal of deregulation. Congress sought to ensure\n\n 9\n For instance, we cannot see, nor has AEX explained,\nhow reclassification of employees would necessarily require\nAEX to acquire a new fleet of vehicles or create a human\nresources department.\n 10\n Patient Protection and Affordable Care Act of 2010,\nPub. L. No. 111-148, 124 Stat. 119 (2010).\n\n\n\n\n 24\n\fmarket forces determined prices, routes, and services. Nothing\nin that goal, however, meant to exempt workers from receiving\nproper wages, even if the wage laws had an incidental impact\non carrier prices, routes, or services.11\n\n Finally, the fact that New Jersey’s ABC classification\ntest differs from the federal test used in the Fair Labor\nStandards Act of 1938, 29 U.S.C. §§ 201-19, will not result in\na “‘patchwork’ of unique state legislation, which [AEX\ncontends] regulates differently from state to state how motor\ncarriers are required to perform their delivery services.” Reply\nBr. at 14. Most notably, New Jersey’s test is similar to that\nused in many other states. See, e.g., RDI Logistics, 65 N.E.3d\nat 11-12 (holding that prongs A and C of the Massachusetts\ntest, which are identical to those in the New Jersey test, were\nnot FAAAA-preempted because they did not present a\n“patchwork problem” as they were “more or less nationally\nuniform,” unlike the Massachusetts B prong, which was\npreempted in Schwann because it was anomalous (quoting\nSchwann, 813 F.3d at 440)).\n\n\n\n\n 11\n Indeed, Congress evinced its intent for the FAAAA\nnot to preempt general state wage laws when it included New\nJersey—where, at the time the FAAAA was enacted, the\nNJWHL and NJWPL were already in effect, N.J. Stat. Ann. §§\n34:11-56a7 & 34:11-4.1 (indicating initial enactment in 1966\nand 1965, respectively)—in its list of jurisdictions with laws\nthat did not run afoul of the FAAAA. H.R. Conf. Rep. No.\n103-677, at 86 (1994); see also Mendonca, 152 F.3d at 1187-\n88 & n.3.\n\n\n\n\n 25\n\f Thus, AEX has not shown that New Jersey’s ABC\nclassification test has a “significant impact” on Congress’\nderegulatory efforts with respect to motor carrier businesses,\nnor are the NJWHL and NJWPL—typical state wage and hour\nlaws—the kinds of preexisting state regulations with which\nCongress was concerned when it passed the FAAAA.12 See\nLupian, 905 F.3d at 135-36; Schwann, 813 F.3d at 438;\nCostello, 810 F.3d at 1050-51; Amerijet, 627 F. App’x at 751;\nDilts, 769 F.3d at 647-48; Gary, 397 F.3d at 189-90;\nMendonca, 152 F.3d at 1187-89. Notably, eight of the ten\njurisdictions that Congress identified as not regulating\nintrastate prices, routes, and services “had laws for\ndifferentiating between an employee and an independent\ncontractor,” Su, 903 F.3d at 967, and at least three codified\nABC tests similar to that of New Jersey, see Alaska Stat. §\n23.20.525(a)(10) (1992); Del. Code Ann. tit. 19, § 3302(9)(k)\n(1992); Vt. Stat. Ann. tit. 21, § 1301(6)(B) (1992). Therefore,\nAEX’s patchwork argument fails.\n\n Accordingly, any effect the New Jersey ABC\nclassification test has on prices, routes, or services with respect\nto the transportation of property is tenuous and insignificant.\nSee Lupian, 905 F.3d at 136. As a result, the test is not\npreempted.\n\n\n\n\n 12\n As the Schwann court observed, while Congress\nsought “to avoid ‘a patchwork of state service-determining\nlaws,’” we can assume that “Congress intended to leave\nuntouched” “pre-existing and customary manifestation[s] of\nthe state’s police power.” 813 F.3d at 438 (quoting Rowe, 552\nU.S. at 373).\n\n\n\n\n 26\n\f III\n\n For the foregoing reasons, we will affirm the District\nCourt’s order denying AEX’s motion for judgment on the\npleadings and remand for further proceedings.\n\n\n\n\n 27", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362696/", "author_raw": "SHWARTZ, Circuit Judge."}]}
GREENAWAY
SHWARTZ
BIBAS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4585443/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Ever BEDOYA; Diego Gonzales; Manuel Decastro, on Behalf of Themselves and All Others Similarly Situated v. AMERICAN EAGLE EXPRESS INC., D/B/A AEX Group v. KV Service, LLC; M&J Express, LLC; A&D Delivery Express, LLC American Eagle Express, Inc., Appellant\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-29\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n _____________\n\n No. 18-1641\n _____________\n\n EVER BEDOYA; DIEGO GONZALES; MANUEL\n DECASTRO,\n on behalf of themselves and all others similarly situated\n\n v.\n\nAMERICAN EAGLE EXPRESS INC, d/b/a AEX GROUP\n\n v.\n\n KV SERVICE, LLC; M&J EXPRESS, LLC; A&D\n DELIVERY EXPRESS, LLC\n\n American Eagle Express, Inc.,\n Appellant\n ______________\n\n Appeal from the United States District Court\n for the District of New Jersey\n (D.C. No. 2-14-cv-02811)\n District Judge: Hon. Esther Salas\n ______________\n\f Argued November 14, 2018\n ______________\n\n Before: GREENAWAY, JR., SHWARTZ, and BIBAS,\n Circuit Judges.\n\n (Opinion Filed: January 29, 2019)\n\nHarold L. Lichten [ARGUED]\nLichten & Liss-Riordan\n729 Boylston Street\nSuite 2000\nBoston, MA 02116\n\nR. Andrew Santillo\nPeter D. Winebrake\nWinebrake & Santillo\n715 Twinning Road\nSuite 211, Twinning Office Center\nDresher, PA 19025\n\n Counsel for Plaintiff-Appellees\n\nJoseph C. DeBlasio [ARGUED]\nJackson Lewis\n220 Headquarters Plaza\nEast Tower, 7th Floor\nMorristown, NJ 07960\n\n Counsel for Defendant-Appellant\n\nAdina H. Rosenbaum\nPublic Citizen Litigation Group\n\n\n\n\n 2\n\f1600 20th Street, NW.\nWashington, DC 20009\n\n Counsel for Amicus Public Citizen Inc.\n\n\nChristopher W. Weber [ARGUED]\nEmily M. Bisnauth\nOffice of Attorney General of New Jersey\nDepartment of Law & Public Safety\nRichard J. Hughes Justice Complex\n25 Market Street\nP.O. Box 112\nTrenton, NJ 08625\n\n Counsel for Amicus New Jersey Department of Labor\n and Workforce Development\n\n\n ___________\n\n OPINION\n ___________\n\n\nSHWARTZ, Circuit Judge.\n\n Plaintiff delivery drivers Ever Bedoya, Diego Gonzalez,\nand Manuel Decastro (collectively, “the Drivers”) filed a\nputative class action against Defendant American Eagle\nExpress, Inc., (“AEX”), alleging that AEX misclassified them\nas independent contractors when they are actually employees\nunder the New Jersey Wage and Hour Law (“NJWHL”), N.J.\n\n\n\n\n 3\n\fStat. Ann. §§ 34:11-56a to -56a3, and the New Jersey Wage\nPayment Law (“NJWPL”), N.J. Stat. Ann. §§ 34:11-4.1 to -\n4:14. AEX moved for judgment on the pleadings pursuant to\nFed. R. Civ. P. 12(c), arguing that the Drivers’ claims are\npreempted by the Federal Aviation Authorization\nAdministration Act of 1994 (“FAAAA”), 49 U.S.C. §§ 14501-\n06. The District Court denied AEX’s motion and certified the\norder for interlocutory appeal. Because the FAAAA does not\npreempt the New Jersey law for determining employment\nstatus for the purposes of NJWHL and NJWPL, we will affirm\nthe order and remand for further proceedings.\n\n I\n\n AEX is a logistics company that provides delivery\nservices to various medical organizations. The Drivers are\nNew Jersey residents who make deliveries for AEX. The\nDrivers filed this putative class action against AEX seeking,\namong other things, a judgment declaring that they are\nemployees of AEX, rather than independent contractors, which\nentitles them to compensation under the NJWHL and NJWPL.1\nAEX moved for judgment on the pleadings, arguing that the\nFAAAA preempts the Drivers’ claims.\n\n The District Court denied AEX’s motion, Bedoya v.\nAm. Eagle Express, Civ. No. 14-2811, 2017 WL 4330351, at\n*1 (D.N.J. Sept. 29, 2017), reasoning that “[t]here is no clear\nindication” that Congress intended for the FAAAA to preempt\nstate wage laws, Dkt. 109 at 6, 10, and that the connection\nbetween regulation of AEX’s workforce and the “prices,\n\n 1\n The District Court has jurisdiction pursuant to 28\nU.S.C. § 1332(d).\n\n\n\n\n 4\n\froutes, and services” provided to its consumers is too\nattenuated to justify preempting claims under the NJWHL and\nNJWPL, id. at 8-9. We now consider AEX’s interlocutory\nappeal of the order denying the motion pursuant to 28 U.S.C.\n§ 1292(b). Bedoya, 2017 WL 4330351, at *1-4.\n\n II2\n\n A\n\n The question before us is whether the FAAAA preempts\nNew Jersey’s test for determining employment classification\nfor purposes of the NJWHL and NJWPL. Under this test,\nworkers performing services for a given company in exchange\nfor pay are deemed employees unless the company can\ndemonstrate each of the following:\n\n A. Such individual has been and will continue to\n be free from control or direction over the\n\n 2\n We review an order granting or denying a motion for\njudgment on the pleadings de novo. Zimmerman v. Corbett,\n873 F.3d 414, 417 (3d Cir. 2017) (citing Allah v. Al-Hafeez,\n226 F.3d 247, 249 (3d Cir. 2007)). Judgment will not be\ngranted unless the movant “clearly establishes there are no\nmaterial issues of fact, and he is entitled to judgment as a\nmatter of law.” Sikirica v. Nationwide Ins. Co., 416 F.3d 214,\n220 (3d Cir. 2005) (citation omitted). In considering a motion\nfor judgment on the pleadings, we must accept as true all facts\npresented in the complaint and answer and draw all reasonable\ninferences in favor of the non-moving party—here, the\nDrivers. Id. at 417-18. While AEX implores us to look beyond\nthe pleadings, we may not.\n\n\n\n\n 5\n\f performance of such service, both under his\n contract of service and in fact; and\n\n B. Such service is either outside the usual course\n of the business for which such service is\n performed, or that such service is performed\n outside of all the places of business of the\n enterprise for which such service is\n performed; and\n\n C. Such individual is customarily engaged in an\n independently established trade, occupation,\n profession, or business.\n\nN.J. Stat. Ann. §§ 43:21-19(i)(6)(A)-(C) (“New Jersey ABC\nclassification test”). Where a company successfully\ndemonstrates all three elements with respect to a worker, that\nworker qualifies as an independent contractor under the\nNJWHL and NJWPL. Hargrove v. Sleepy’s, LLC, 106 A.3d\n449, 458 (N.J. 2015). The company, in turn, is exempt from\nrequirements under those statutes with respect to the worker.\nId. For individuals classified as employees, however, the\nemploying company is subject to each statute’s obligations,\nincluding minimum and overtime wage requirements, N.J.\nStat. Ann. § 34:11-56a4, conditions regarding the time and\nmode of pay, N.J. Stat. Ann. § 34:11-4.2, 4.2a, and restrictions\non pay deductions, N.J. Stat. Ann. § 34:11-4.4. AEX contends\nthat the New Jersey ABC classification test is preempted by the\nFAAAA.\n\n\n\n\n 6\n\f B\n\n The preemption doctrine stems from the Supremacy\nClause, which provides that “the Laws of the United States . . .\nshall be the supreme Law of the Land . . . any Thing in the\nConstitution or Laws of any State to the Contrary\nnotwithstanding.” U.S. Const. art. VI, cl. 2. Thus, “Congress\n. . . has the power to preempt state law.” In re Vehicle Carrier\nServs. Antitrust Litig., 846 F.3d 71, 83 (3d Cir. 2017) (citing\nArizona v. United States, 567 U.S. 387 (2012)), cert denied sub\nnom., Alban v. Nippon Yusen Kabushiki Kaisha, 138 S. Ct.\n114 (2017). There are three categories of preemption: field\npreemption, conflict preemption, and express preemption.\nHolk v. Snapple Beverage Corp., 575 F.3d 329, 334 (3d Cir.\n2009) (citing Hillsborough County, Fla. v. Automated Med.\nLabs., Inc., 471 U.S. 707, 713 (1985)).\n\n Because preemption is an affirmative defense, we\nexamine the specific preemption defense asserted. In re\nVehicle, 846 F.3d at 84 (citing Oneok, Inc. v. Learjet, Inc., 135\nS. Ct. 1591 (2015)). AEX argues that New Jersey’s ABC\nclassification test is subject to express preemption under 49\nU.S.C. § 14501(c)(1). “Express preemption requires a[n]\nanalysis of whether ‘[s]tate action may be foreclosed by\nexpress language in a congressional enactment.’” Lupian v.\nJoseph Cory Holdings, LLC, 905 F.3d 127, 131 (3d Cir. 2018)\n(alteration in original) (quoting Lorillard Tobacco Co. v.\nReilly, 533 U.S. 525, 541 (2001)).\n\n In evaluating AEX’s argument, we first decide whether\nthe presumption against preemption applies. City of Columbus\nv. Ours Garage & Wrecker Serv., Inc., 536 U.S. 424, 438\n(2002) (applying the presumption against preemption in the\n\n\n\n\n 7\n\fFAAAA context). Under this presumption, “the historic police\npowers of the States” are “not to be superseded by [a] [f]ederal\n[a]ct unless that was the clear and manifest purpose of\nCongress.” Sikkelee v. Precision Airmotive Corp., 822 F.3d\n680, 687 (3d Cir. 2016) (quoting Wyeth v. Levine, 555 U.S.\n555, 565 (2009)). Thus, we “presume claims based on laws\nembodying state police powers are not preempted.” In re\nVehicle, 846 F.3d at 84; see also Farina v. Nokia Inc., 625 F.3d\n97, 116 (3d Cir. 2010).\n\n Many employment regulations, such as the wage laws\nat issue here, seek to ensure workers receive fair pay. Because\nthey protect workers, they are within New Jersey’s police\npower, and the presumption against preemption by federal law\napplies. See, e.g., Lupian, 905 F.3d at 131 (stating wage laws\nthat protect workers represent an exercise of “police power”);\nsee also Fort Halifax Packing Co. v. Coyne, 482 U.S. 1, 21\n(1987) (applying the presumption against preemption to a state\nlabor law regarding severance pay “since the establishment of\nlabor standards falls within the traditional police power of the\nState”).\n\n The presumption is rebutted where Congress had a\n“clear and manifest purpose” to preempt state laws. Sikkelee,\n822 F.3d at 687 (citation omitted); see also Cipollone v. Liggett\nGrp., Inc., 505 U.S. 504, 516 (1992) (directing courts to\nexamine congressional intent, the “ultimate touchstone” in\ndiscerning the preemptive scope of a statute (internal quotation\nmarks and citation omitted)). To determine Congress’\npurpose, we look to the plain language of the statute and, if\nnecessary, to the statutory framework as a whole. Medtronic,\nInc. v. Lohr, 518 U.S. 470, 486 (1996) (citation omitted).\nThus, we next examine Congress’ purpose in enacting the\n\n\n\n\n 8\n\fFAAAA and the Airline Deregulation Act of 1978 (“ADA”),\n49 U.S.C. §§ 40101-130, an earlier statute with a similar\npreemption provision.\n\n C\n\n In 1978, following a long period of heightened\nregulation, Congress enacted the ADA, which sought to\nderegulate the air-travel industry to “maxim[ize] reliance on\ncompetitive market forces.” Morales v. Trans World Airlines,\nInc., 504 U.S. 374, 378 (1992) (quoting 49 U.S.C. App. §\n1302(a)(4)). To ensure that this objective would not be\nfrustrated by state regulation, Congress included a preemption\nprovision providing that “no State . . . shall enact or enforce\nany law . . . relating to rates, routes, or services of any air\ncarrier.” Id. at 420 (Stevens, J., dissenting) (quoting 49 U.S.C.\nApp. § 1305(a)).\n\n Congress enacted similar laws focused on deregulating\ninterstate trucking, culminating with the passage of the\nFAAAA in 1994. Lupian, 905 F.3d at 132-33. Via the\nFAAAA, Congress sought to “level the playing field” between\nair carriers and motor carriers so that both could benefit from\nfederal deregulation. H.R. Conf. Rep. No. 103-677, at 88\n(1994); see also Californians for Safe & Competitive Dump\nTruck Transp. v. Mendonca, 152 F.3d 1184, 1187-88 (9th Cir.\n1998) (detailing FAAAA legislative history). The FAAAA\ncontains a preemption provision modeled after the ADA’s,\nproviding, with limited exceptions, that:\n\n a State . . . may not enact or enforce a law,\n regulation, or other provision having the force\n and effect of law related to a price, route, or\n\n\n\n\n 9\n\f service of any motor carrier . . . with respect to\n the transportation of property.\n\n49 U.S.C. § 14501(c)(1). Because of the parallels between the\nADA and FAAAA, ADA cases are instructive regarding the\nscope of FAAAA preemption. See Rowe v. N.H. Motor\nTransp. Ass’n, 552 U.S. 364, 370 (2008) (analyzing FAAAA\npreemption using ADA cases as guidance). As with the ADA,\nthe FAAAA preemption provision’s central objective is to\navoid frustrating the statute’s deregulatory purpose by\npreventing states from imposing “a patchwork of state service-\ndetermining laws.” Dan’s City Used Cars, Inc. v. Pelkey, 569\nU.S. 251, 264 (2013) (quoting Rowe, 552 U.S. at 373). The\nFAAAA, however, has a qualifier that is absent from the ADA:\nthe preempted state law must relate to prices, routes, or services\n“with respect to the transportation of property.” 49 U.S.C.\n§ 14501(c)(1). The Supreme Court has recognized that this\nlanguage “massively limits the scope of preemption ordered by\nthe FAAAA.” Dan’s City, 569 U.S. at 261 (internal citation\nand quotation marks omitted).\n\n Further insight into the limits of FAAAA preemption\ncomes from the subjects Congress considered when enacting\nthat statute. “Congress identified ten jurisdictions (nine states\nand the District of Columbia . . . ) that did not regulate intrastate\nprices, routes, and services.” Cal. Trucking Ass’n v. Su, 903\nF.3d 953, 967 (9th Cir. 2018) (citing Mendonca, 152 F.3d at\n1187). By implication, Congress determined that the laws then\nin existence in those jurisdictions did not contravene its\nderegulatory goals and thus were not preempted. Id.\n\n The Supreme Court has also articulated several\nprinciples that inform us about the breadth of FAAAA\n\n\n\n\n 10\n\fpreemption. First, the “related to” language from the FAAAA\npreemption clause gives it a broad scope, encompassing any\nstate actions that have “a connection with, or [make] reference\nto . . . rates, routes, or services” of a motor carrier. Nw., Inc.\nv. Ginsberg, 572 U.S. 273, 280-81 (2014) (internal quotation\nmarks and citation omitted) (interpreting the ADA). While this\nlanguage covers any state law that has a connection with or\nrefers to “price[s], route[s], [or] service[s,]” id. at 280, “the\nbreadth of the words ‘related to’ does not mean the sky is the\nlimit,” Dan’s City, 569 U.S. at 260. Drawing from case law\nexamining similar wording in the preemption provision of the\nEmployee Retirement Income Security Act of 1974, 29 U.S.C.\n§ 1144(a), see, e.g., Morales, 504 U.S. at 383-84, the Supreme\nCourt has observed that reading the phrase “related to” with\n“uncritical literalism” would render preemption an endless\nexercise, Dan’s City, 569 U.S. at 260-61 (citation omitted),\nbecause “everything [is] relat[ed] to everything else in some\nmanner[,]” Schwann v. FedEx Ground Package Sys., Inc., 813\nF.3d 429, 436 (1st Cir. 2016) (citing N.Y. State Conference of\nBlue Cross & Blue Shield Plans v. Travelers Ins. Co., 514 U.S.\n645, 655 (1955)).\n\n Second, FAAAA preemption reaches laws that affect\nprices, routes, or services even if the effect “is only indirect.”\nRowe, 552 U.S. at 370 (quoting Morales, 504 U.S. at 386).\nHowever, where a law’s impact on carrier prices, routes, or\nservices is so indirect that the law affects them “in only a\ntenuous, remote, or peripheral . . . manner,” the law is not\npreempted. Dan’s City, 569 U.S. at 261 (quoting Rowe, 552\nU.S. at 371); Morales, 504 U.S. at 390 (quoting Shaw v. Delta\nAir Lines, Inc., 463 U.S. 85, 100 n.21 (1983)).\n\n\n\n\n 11\n\f Finally, preemption occurs where a state law has “a\n‘significant impact’ on carrier rates, routes, or services.”3\nRowe, 552 U.S. at 375 (emphasis omitted) (quoting Morales,\n504 U.S. at 390).\n\n Mindful of these principles, we next review the case law\nfor guidance concerning whether a law has a direct or indirect\neffect and whether it has a significant or insignificant effect.\nFrom our review, we identify factors courts examine and set\nforth those factors that may shed light on a law’s directness and\nthose that may reflect the significance of the law’s effect on the\nregulated entities at issue.\n\n D\n\n Neither the Supreme Court nor our Court has recited\nprecise standards for evaluating directness or significance, but\ncases addressing the issue provide some guidance. For\nexample, the Supreme Court has held that consumer protection\nand fraud laws used to regulate frequent-flyer programs could\ndirectly and significantly affect prices and services and are thus\npreempted. See Am. Airlines, Inc. v. Wolens, 513 U.S. 219,\n223 (1995); Morales, 504 U.S. at 388-89. Similarly, the Court\ndetermined that a Maine law requiring a specific procedure to\nverify the recipient of tobacco deliveries was preempted by the\nFAAAA because it dictated a service that tobacco motor\ncarriers were required to provide for property they transported.\nRowe, 552 U.S. at 372. In addition, we recently observed that\n\n 3\n The Supreme Court also noted that “it makes no\ndifference whether a state law is ‘consistent’ or ‘inconsistent’\nwith federal regulation.” Rowe, 552 U.S. at 370 (quoting\nMorales, 504 U.S. at 386-87).\n\n\n\n\n 12\n\fthe FAAAA’s “preemption clause undoubtedly applies, for\nexample, to state laws directly restricting types of goods that\ncan be carried by trucks, tariffs, and barriers to entry.” Lupian,\n905 F.3d at 135; H.R. Conf. Rep. No. 103-677, at 86 (1994).\n\n On the other hand, the FAAAA itself, the Supreme\nCourt, and the courts of appeals have identified laws that are\ntoo “tenuous, remote, or peripheral” from carrier prices, routes,\nand services to trigger preemption. See, e.g., Rowe, 552 U.S.\nat 371; Dilts v. Penske Logistics, LLC, 769 F.3d 637, 646 (9th\nCir. 2014). The FAAAA explicitly exempts from preemption\nlaws governing motor vehicle safety, local route controls based\non vehicle size and weight, and driver insurance requirements.4\n49 U.S.C. § 14501(c)(2)(A). The Supreme Court has stated\nthat the FAAAA does not preempt laws prohibiting\nprostitution, gambling, and “obscene depictions,” Morales,\n504 U.S. at 390, or those addressing zoning, Dan’s City, 569\nU.S. at 264. We have observed that “garden variety\nemployment claim[s]” evade ADA and FAAAA preemption\nbecause they are “too remote and too attenuated” from carrier\nprices, services, or routes. Lupian, 905 F.3d at 134 (quoting\nGary v. Air Grp., Inc., 397 F.3d 183, 189 (3d Cir. 2005)). As\nrelevant to this case, we recently held that wage claims under\nthe Illinois Wage Payment and Collection Act (“IWPCA”),\n820 Ill. Comp. Stat. 115/1-115/15, are not preempted under the\nFAAAA because they are “too far removed from the statute’s\n\n 4\n The House of Representatives Conference Report\nspecifies that the list provided in 49 U.S.C. § 14501(c)(2) and\n(3) is “not intended to be all inclusive, but merely to specify\nsome of the matters which are not ‘prices, rates or services’ and\nwhich are therefore not preempted.” H.R. Conf. Rep. No. 103-\n677, at 83.\n\n\n\n\n 13\n\fpurpose to warrant preemption.” Lupian, 905 F.3d at 136.\nMany of our sister circuits have similarly held that the FAAAA\nand ADA do not preempt state employment laws. See, e.g.,\nAllied Concrete & Supply Co. v. Baker, 904 F.3d 1053, 1068\n(9th Cir. 2018) (holding California prevailing wage law for\nworkers on public projects not preempted); Su, 903 F.3d at 957\n(holding California common law test for employee versus\nindependent contractor status not preempted); Costello v.\nBeavEx, Inc., 810 F.3d 1045, 1048 (7th Cir. 2016) (holding\nIllinois wage law not preempted), cert. denied, 137 S. Ct. 2289\n(2017); Amerijet Int’l, Inc. v. Miami-Dade County, Fla., 627\nF. App’x 744, 751 (11th Cir. 2015) (holding Miami-Dade\nCounty living wage ordinance as applied to air carriers not\npreempted); Dilts, 769 F.3d at 647 (holding California meal\nand rest-break laws not preempted); Mendonca, 152 F.3d at\n1189 (holding California wage law not preempted).\n\n From the language of the FAAAA preemption provision\nand these cases, we can distill several factors courts should\nconsider when deciding whether a particular state law is\nFAAAA-preempted. First, courts should examine whether the\nstate law at issue applies to all businesses or whether it focuses\non motor carriers. Laws that are directed at “members of the\ngeneral public” and that are not targeted at motor carriers are\nusually viewed as not having a direct effect on motor carriers.\nRowe, 552 U.S. at 375.\n\n Even targeted laws, however, are not necessarily\npreempted. We know from the FAAAA itself that state laws\nthat may target motor carrier safety and insurance, or restrict\nlocal routes based on vehicle size and weight, are not\npreempted. 49 U.S.C. § 14501(c)(2). Conversely, laws of\ngeneral applicability may nonetheless be preempted where\n\n\n\n\n 14\n\fthey have a significant impact on the services a carrier\nprovides. See, e.g., DiFiore v. Am. Airlines Inc., 646 F.3d 81,\n88-89 (1st Cir. 2011) (holding generally applicable state tip\nlaw as applied to airlines preempted under the ADA because it\n“directly regulate[d] how an airline service is performed and\nhow its price is displayed to customers”). Thus, whether a law\nis applicable to every business or targets carriers is a helpful\nbut nondispositive factor for determining whether a law has a\ndirect effect on motor carriers’ prices, routes, or services.\nMorales, 504 U.S. at 386.\n\n Second, courts should consider whether the law\naddresses the carrier-employee relationship as opposed to the\ncarrier-customer relationship. “[G]enerally applicable state\nlaws that affect the carrier’s relationship with its customers\n[differ from] those that affect the carrier’s relationship with its\nworkforce.” Costello, 810 F.3d at 1054; see also Su, 903 F.3d\nat 961-63 (noting same dichotomy); DiFiore, 646 F.3d at 88\n(preempting a Massachusetts law prohibiting employer from\ncollecting fee advertised as “service charge” because the law\nregulates how a company performs services for its customers\nand “not merely how the airline behaves as an employer or\nproprietor”).\n\n The Court of Appeals for the Seventh Circuit provides\na useful analysis explaining why laws governing an employer’s\nrelationship with its employees have too remote an impact to\nbe preempted. S.C. Johnson & Son, Inc. v. Transp. Corp. of\nAm., Inc., 697 F.3d 544, 558 (7th Cir. 2012) (citing Mendonca,\n152 F.3d at 1189). The court examines whether the challenged\nstate law regulates matters needed to operate the business,\nwhich it calls resource inputs, as opposed to laws governing\nthe goods or services the business puts out, which it calls\n\n\n\n\n 15\n\fproduct outputs. Id. The product outputs of the motor carrier\nindustry are the services it provides—transportation of\nproperty from origin to destination. Id. The FAAAA’s focus\non prices, routes, and services shows that the statute is\nconcerned with the industry’s production outputs, and seeks to\nprotect them from state regulation.\n\n Resource inputs, on the other hand, are the resources\nnecessary for a business to create product outputs, including\n“labor, capital, and technology,” which may be regulated by\nvarious laws. Id. “For example, labor inputs are affected by a\nnetwork of labor laws, including minimum wage laws, worker-\nsafety laws, anti-discrimination laws, and pension regulations.\nCapital is regulated by banking laws, securities rules, and tax\nlaws, among others. Technology is heavily influenced by\nintellectual property laws.” Id. Although laws that regulate\ninputs may impact costs and may in turn affect prices charged\nand services provided to customers, “no one thinks that the\nADA or the FAAAA preempts these [regulations] and the\nmany comparable state laws[.]” Id. That is because,\nnotwithstanding the state laws’ indirect effects, they “operate\none or more steps away from the moment at which the firm\noffers its customer[s] a service for a particular price” and\ntherefore have too “remote” an effect on prices, routes, and\nservices to be the intended target of preemption. Id. (internal\ncitations omitted); see also Su, 903 F.3d at 966 (stating that\ncourts should examine “where in the chain of a motor carrier’s\nbusiness [the state law] is acting to compel a certain result (e.g.,\nconsumer or work force), and what result it is compelling (e.g.,\ncertain wage, non-discrimination, a specific system of\ndelivery, a specific person to perform the delivery)”); Costello,\n810 F.3d at 1055 (embracing S.C. Johnson, 697 F.3d at 558).\nIn short, laws regulating labor inputs, such as wage laws, have\n\n\n\n\n 16\n\ftoo remote an effect on the price the company charges, the\nroutes it uses, and service outputs it provides and are less likely\nto be preempted by the FAAAA.\n\n Third, courts should consider whether the law binds the\ncarrier to provide a particular price, route, or service. As\ndiscussed above, the Supreme Court held that Maine’s\nidentification requirements for tobacco deliveries required a\nmotor carrier transporting tobacco to provide a particular\nservice. Rowe, 552 U.S. at 372. Similarly, the Court of\nAppeals for the First Circuit determined that Massachusetts’\nABC test for classifying employees in effect bound the carrier\nto provide its services using employees rather than independent\ncontractors. Schwann, 813 F.3d at 437. Under Massachusetts’\nindependent contractor statute, only workers who perform a\nservice that is outside the employer’s usual course of business\nmay be classified as independent contractors. Id. (quoting\nMass. Gen. Laws ch. 149, § 148B(a)(2)). Thus, application of\nMassachusetts’ test “in substance, bar[red] [the carrier at issue]\nfrom using any individuals as full-fledged independent\ncontractors.” Id. In other words, the Massachusetts test\nessentially foreclosed the independent contractor classification\nof any of the carrier’s workers performing delivery services\nbecause such services were within the carrier’s usual course of\nbusiness. Id. As a result, the Massachusetts statute bound the\ncarrier to provide its services using employees and not\nindependent contractors.\n\n The same was not true with laws that do not dictate a\nprice, route, or service. For example, the Court of Appeals for\nthe Ninth Circuit analyzed whether the FAAAA preempted a\nCalifornia law that requires employers to provide meal and rest\nbreaks, reviewing, among other factors, whether the law bound\n\n\n\n\n 17\n\fthe carrier to specific prices, routes, or services. Dilts, 769 F.3d\nat 649-50. The court held that the FAAAA did not preempt\nCalifornia’s meal and rest-break laws. Id. The court relied\npartially on the fact that the California laws did not “set prices,\nmandate or prohibit certain routes, or tell motor carriers what\nservices they may or may not provide, either directly or\nindirectly.” Id. at 647. Put simply, the law at issue did “not\n‘bind’ motor carriers to specific prices, routes, or services.”5\nId. (citation omitted).\n\n Finally, courts examining a preemption challenge to a\nstate law should be mindful of Congress’ goal of avoiding a\n“patchwork” of differing state “service-determining laws,”\nwhich could undermine its “major legislative effort to leave\n[decisions regarding the provision of services] to the\ncompetitive marketplace.” Rowe, 552 U.S. at 373 (citing H.R.\nConf. Rep. No. 103-677, at 87 (1994)). This goal does not\nconstitute a categorical imperative to free motor carriers of all\nstate regulation. Rather, the plain language of the FAAAA,\nand its preemption of only laws “relat[ing] to” carrier “price[s],\nroute[s], or service[s],” 49 U.S.C. § 14501(c)(1), demonstrates\nthat Congress was concerned only with a limited set of state\n\n 5\n AEX characterizes Dilts as impermissibly relying on\nthis “binds to” test to conclude that the FAAAA did not\npreempt California’s meal and rest break laws, arguing that\nsuch a test construes the scope of FAAAA preemption too\nnarrowly. While relying solely on such a “binds to” test may\nnarrow FAAAA preemption to an unacceptable degree, Dilts\nmerely recognized that the “binds to” test provides one of\nseveral possible avenues to demonstrate that a state law has a\nsignificant effect on carrier prices, routes, or services. Dilts,\n769 F.3d at 649.\n\n\n\n\n 18\n\flaws. Dilts, 769 F.3d at 646-47. Thus, “[t]he fact that laws\nmay differ from state to state is not, on its own, cause for\nFAAAA preemption.” Id. at 647. Laws that are “more or less\nnationally uniform,” Chambers v. RDI Logistics, Inc., 65\nN.E.3d 1, 11-12 (Mass. 2016), are less likely to pose the kind\nof state law interference FAAAA preemption seeks to avoid.\n\n In sum, to assess the directness of a law’s effect on\nprices, routes, or services, courts should examine whether the\nlaw: (1) mentions a carrier’s prices, routes, or services;\n(2) specifically targets carriers as opposed to all businesses;\nand (3) addresses the carrier-customer relationship rather than\nnon-customer-carrier relationships (e.g., carrier-employee). If\na law has a direct impact on carriers’ prices, routes, or services\nwith respect to the transportation of property, then it is\npreempted unless it falls within one of the statutory exceptions.\nThough we can draw no firm line between laws whose effects\non rates, routes, or services are indirect and laws whose effects\nare “tenuous, remote, or peripheral,” these factors, and perhaps\nother considerations, will guide courts in the inquiry.\n\n To assess whether a law has a significant effect on a\ncarrier’s prices, routes, or services, courts should consider\nwhether: (1) the law binds a carrier to provide or not provide a\nparticular price, route, or service; (2) the carrier has various\navenues to comply with the law; (3) the law creates a\npatchwork of regulation that erects barriers to entry, imposes\ntariffs, or restricts the goods a carrier is permitted to transport;\nand (4) the law existed in one of the jurisdictions Congress\ndetermined lacked laws that regulate intrastate prices, routes,\nor services and thus, by implication, is a law Congress found\nnot to interfere with the FAAAA’s deregulatory goal. Other\nfactors may also lead a court to decide that a state law has a\n\n\n\n\n 19\n\fsignificant effect where the law undermines Congress’ goal of\nhaving competitive market forces dictate prices, routes, or\nservices of motor carriers.6\n\n E\n\n We have examined each of these considerations and\nconclude that New Jersey’s ABC classification test is not\npreempted as it has neither a direct, nor an indirect, nor a\nsignificant effect on carrier prices, routes, or services.\n\n 6\n Before the Supreme Court’s rulings in Rowe and\nDan’s City, our Court once framed the inquiry—albeit in the\ncontext of whether a defamation claim was preempted under\nthe ADA (a question we answered in the negative, holding that\nthe defamation claim was not preempted)—as whether the law\nor claim in question would “frustrate[] deregulation by\ninterfering with competition through public utility-style\nregulation.” Taj Mahal Travel, Inc. v. Delta Airlines, Inc., 164\nF.3d 186, 194 (3d Cir. 1998) (citation omitted). Elaborating\non regulation in a “public utility sense” in the context of airline\nservices, our Court said that regulations of “the frequency and\nscheduling of transportation” and “the selection of markets”\nare public-utility styled regulations (which would thus be\npreempted under the ADA), whereas “provision of in-flight\nbeverages, personal assistance to passengers, the handling of\nluggage, and similar amenities” are not services in a “public\nutility sense,” and thus could be regulated, for instance through\nstate implementation of a duty to exercise reasonable care, the\nviolation of which could give rise to ordinary tort claims. Id.\nat 193 (quoting Charas v. Trans World Airlines, Inc., 160 F.3d\n1259, 1261, 1265-66 (9th Cir. 1998) (en banc)).\n\n\n\n\n 20\n\f Any effect New Jersey’s ABC classification test has on\nprices, routes, or services is tenuous. The test does not mention\ncarrier prices, routes, or services, nor does it single out carriers.\nIndeed, the test applies to all businesses as part of the\n“backdrop” they “face in conducting their affairs.” Lupian,\n905 F.3d at 136; see also Dilts, 769 F.3d at 646 (describing a\nstate employment law as a “background regulation[]”). The\ntest also does not regulate carrier-customer interactions or\nother product outputs. Rather, it only concerns employer-\nworker relationships. Laws governing how an employer pays\nits workers do not “directly regulate[] how [a carrier’s] service\nis performed[;]” they merely dictate how a carrier “behaves as\nan employer[.]” DiFiore, 646 F.3d at 88. As a result, the test\nis “steps removed” from regulating customer-carrier\ninteractions through prices, routes, or services. Costello, 810\nF.3d 1054 (quoting Dilts, 769 F.3d at 646).\n\n The New Jersey ABC classification test does not have a\nsignificant effect on prices, routes, or services either. The test\ndoes not bind AEX to a particular method of providing services\nand thus it is unlike the preempted Massachusetts law at issue\nin Schwann, 813 F.3d 429. The Massachusetts statute does not\ninclude New Jersey’s alternative method for reaching\nindependent contractor status—that is, by demonstrating that\nthe worker provides services outside of the putative employer’s\n“places of business.” N.J. Stat. Ann. § 43:21-19(i)(6)(B).\nThus, if the other prongs of the New Jersey classification test\nare met, the test allows an employer to classify a worker as an\nindependent contractor if it shows that the worker either\nprovides a service that is “outside the [employer’s] usual\ncourse of business . . . or [performs such service] outside of all\n\n\n\n\n 21\n\fthe places of business of [the employer].” Id.7 No part of the\nNew Jersey test categorically prevents carriers from using\nindependent contractors. As a result, the state law at issue here\ndoes not mandate a particular course of action—e.g., requiring\ncarriers to use employees rather than independent\ncontractors—and it offers carriers various options to comply\nwith New Jersey employment law.8\n\n 7\n AEX focuses its argument on the B prong of the New\nJersey test, but also asserts that the A and C prongs of the test\nare preempted. AEX cites no case holding that prong A or C\nis preempted under either the FAAAA or the ADA. This is not\nsurprising given the legion of cases holding that the A and C\nprongs are not FAAAA-preempted. See, e.g., Vargas v. Spirit\nDelivery & Distrib. Servs., Inc., 245 F. Supp. 3d 268, 281-84\n(D. Mass. 2017); DaSilva v. Border Transfer of Mass., Inc.,\n227 F. Supp. 3d 154, 159-60 (D. Mass. 2017); Portillo v. Nat’l\nFreight, Inc., Civ. No. 15-7908, 2016 WL 5402215, at *5-6\n(D.N.J. Sept. 26, 2016); Chambers v. RDI Logistics, Inc., 65\nN.E.3d 1, 11-12 (Mass. 2016). AEX also provides no reason\nwhy these prongs are preempted and in fact does not\nindividually analyze them. Thus, AEX has failed to carry its\nburden to demonstrate that the affirmative defense of FAAAA\npreemption applies to these prongs.\n 8\n AEX makes much of the fact that the Costello and\nLupian courts observed that certain aspects of the IWPCA\nclassification provision could be contracted around (i.e.,\nemployees could enter into contracts with carriers to allow\ncertain paycheck deductions), Lupian, 905 F.3d at 135 n.12,\nwhereas neither the New Jersey test nor the Massachusetts test\nallows the same contractual avoidance. Contrary to AEX’s\nargument, this does not make the current case more analogous\n\n\n\n\n 22\n\f AEX argues that applying the New Jersey law may\nrequire it to shift its model away from using independent\ncontractors, which will increase its costs, and in turn, its prices.\nSpecifically, AEX asserts that if it can no longer use\nindependent contractors to perform its delivery services, then\nit will be forced to recruit employees, bring on a human\nresources department to manage them, acquire and maintain a\nfleet of vehicles and pay expense reimbursements, provide\nfringe benefits, plan and dictate delivery routes and timing, and\npay overtime wages and employment taxes. Our Court and our\nsister circuits have rejected similar lists of conclusory impacts.\nLupian, 905 F.3d at 135-36; Costello, 810 F.3d at 1056;\nMendonca, 152 F.3d at 1189. Though AEX correctly states\nthat it need not proffer empirical evidence to support its\nassertions of significant impact at the pleading stage, see, e.g.,\nCostello, 810 F.3d at 1055 (citing Rowe, 552 U.S. at 373-74),\n\n\nto Schwann than to Costello and Lupian. Though Costello and\nLupian correctly took the IWPCA contractual loophole into\naccount, neither court relied on it. See Lupian, 905 F.3d at 136\nn.12 (observing that the Costello court “noted” the contractual\nallowance in the IWPCA); Costello, 810 F.3d at 1057 (noting\nin a single sentence that the IWPCA’s prohibition on\ndeductions from wages can be contracted around, ultimately\nholding that the IWPCA is not “related to a price, route, or\nservice of any motor carrier”). Moreover, while a contractual\ncircumvention option may provide another route for\ncompliance, weighing against FAAAA preemption, it is not the\nonly way a state statute can afford carriers some flexibility.\nHere, the New Jersey ABC classification test gives carriers\noptions; it does not need to provide a contractual workaround\nto avoid preemption.\n\n\n\n\n 23\n\fit does not provide even a logical connection between the\napplication of New Jersey’s ABC classification test and the list\nof new costs it would purportedly incur.9\n\n AEX’s argument that it may be subject to other legal\nrequirements arising from reclassification, citing only the\nAffordable Care Act,10 is equally unavailing. In the words of\nthe Costello court, “[c]onspicuously absent from [the\ncompany’s] parade of horrors is any citation of authority\nshowing that it would be required to comply with [other]\nfederal and state laws.” Id. at 1056. Instead, AEX “rel[ies] on\nconclusory allegations that compliance with the [NJWHL and\nNJWPL] will require [AEX] to switch its entire business model\n. . . [but w]e see no basis for concluding that [New Jersey law]\nwould require that change given that the federal employment\nlaws and other state labor laws [may] have different tests” for\ndetermining whether someone is an employee under a specific\nstatute. Id. (citations omitted).\n\n Furthermore, while “[w]e have no doubt that the\ndisruption of a labor model—especially after services have\nbeen performed—could have negative financial and other\nconsequences for an employer,” Lupian, 905 F.3d at 136, this\nimpact on the employer does not equate to a significant impact\non Congress’ goal of deregulation. Congress sought to ensure\n\n 9\n For instance, we cannot see, nor has AEX explained,\nhow reclassification of employees would necessarily require\nAEX to acquire a new fleet of vehicles or create a human\nresources department.\n 10\n Patient Protection and Affordable Care Act of 2010,\nPub. L. No. 111-148, 124 Stat. 119 (2010).\n\n\n\n\n 24\n\fmarket forces determined prices, routes, and services. Nothing\nin that goal, however, meant to exempt workers from receiving\nproper wages, even if the wage laws had an incidental impact\non carrier prices, routes, or services.11\n\n Finally, the fact that New Jersey’s ABC classification\ntest differs from the federal test used in the Fair Labor\nStandards Act of 1938, 29 U.S.C. §§ 201-19, will not result in\na “‘patchwork’ of unique state legislation, which [AEX\ncontends] regulates differently from state to state how motor\ncarriers are required to perform their delivery services.” Reply\nBr. at 14. Most notably, New Jersey’s test is similar to that\nused in many other states. See, e.g., RDI Logistics, 65 N.E.3d\nat 11-12 (holding that prongs A and C of the Massachusetts\ntest, which are identical to those in the New Jersey test, were\nnot FAAAA-preempted because they did not present a\n“patchwork problem” as they were “more or less nationally\nuniform,” unlike the Massachusetts B prong, which was\npreempted in Schwann because it was anomalous (quoting\nSchwann, 813 F.3d at 440)).\n\n\n\n\n 11\n Indeed, Congress evinced its intent for the FAAAA\nnot to preempt general state wage laws when it included New\nJersey—where, at the time the FAAAA was enacted, the\nNJWHL and NJWPL were already in effect, N.J. Stat. Ann. §§\n34:11-56a7 & 34:11-4.1 (indicating initial enactment in 1966\nand 1965, respectively)—in its list of jurisdictions with laws\nthat did not run afoul of the FAAAA. H.R. Conf. Rep. No.\n103-677, at 86 (1994); see also Mendonca, 152 F.3d at 1187-\n88 & n.3.\n\n\n\n\n 25\n\f Thus, AEX has not shown that New Jersey’s ABC\nclassification test has a “significant impact” on Congress’\nderegulatory efforts with respect to motor carrier businesses,\nnor are the NJWHL and NJWPL—typical state wage and hour\nlaws—the kinds of preexisting state regulations with which\nCongress was concerned when it passed the FAAAA.12 See\nLupian, 905 F.3d at 135-36; Schwann, 813 F.3d at 438;\nCostello, 810 F.3d at 1050-51; Amerijet, 627 F. App’x at 751;\nDilts, 769 F.3d at 647-48; Gary, 397 F.3d at 189-90;\nMendonca, 152 F.3d at 1187-89. Notably, eight of the ten\njurisdictions that Congress identified as not regulating\nintrastate prices, routes, and services “had laws for\ndifferentiating between an employee and an independent\ncontractor,” Su, 903 F.3d at 967, and at least three codified\nABC tests similar to that of New Jersey, see Alaska Stat. §\n23.20.525(a)(10) (1992); Del. Code Ann. tit. 19, § 3302(9)(k)\n(1992); Vt. Stat. Ann. tit. 21, § 1301(6)(B) (1992). Therefore,\nAEX’s patchwork argument fails.\n\n Accordingly, any effect the New Jersey ABC\nclassification test has on prices, routes, or services with respect\nto the transportation of property is tenuous and insignificant.\nSee Lupian, 905 F.3d at 136. As a result, the test is not\npreempted.\n\n\n\n\n 12\n As the Schwann court observed, while Congress\nsought “to avoid ‘a patchwork of state service-determining\nlaws,’” we can assume that “Congress intended to leave\nuntouched” “pre-existing and customary manifestation[s] of\nthe state’s police power.” 813 F.3d at 438 (quoting Rowe, 552\nU.S. at 373).\n\n\n\n\n 26\n\f III\n\n For the foregoing reasons, we will affirm the District\nCourt’s order denying AEX’s motion for judgment on the\npleadings and remand for further proceedings.\n\n\n\n\n 27\n[END_CASE]", "role": "user" } ]
4,585,444
*The ESTATE OF Adriano ROMAN, Jr., Appellant v. CITY OF NEWARK; City of Newark Police Department; Anthony Campos, Chief of Police; Rodger C. Mendes; Albano Ferreira ; Onofre H. Cabezas; Joseph Cueto; FNU Ressureicao; FNU Golpe; Joyce Hill, Individually and in Their Capacity as Police Officers; John Does 1-20, as Fictitious Names for Presently Unknown Agents Member Commissioners and Chiefs *(Amended Pursuant to Clerk's Order Dated 1/25/2018)
Estate of Adriano Roman, Jr. v. City of Newark
2019-01-29
17-2302
U.S. Court of Appeals for the Third Circuit
{"judges": "Jordan, Hardiman", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887936/", "author_raw": ""}, {"author": "", "type": "030concurrence", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887937/", "author_raw": ""}, {"author": "", "type": "035concurrenceinpart", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887938/", "author_raw": ""}, {"author": "AMBRO, Circuit Judge", "type": "010combined", "text": "PRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n No. 17-2302\n ________________\n\n *THE ESTATE OF ADRIANO ROMAN, JR.,\n Appellant\n\n v.\n\n CITY OF NEWARK;\n CITY OF NEWARK POLICE DEPARTMENT;\n ANTHONY CAMPOS, Chief of Police;\n RODGER C. MENDES;\n ALBANO FERREIRA; ONOFRE H. CABEZAS;\n JOSEPH CUETO;\n FNU RESSUREICAO; FNU GOLPE; JOYCE HILL,\n Individually and in their capacity as police officers;\nJOHN DOES 1-20, as fictitious names for presently unknown\n agents member commissioners and chiefs\n\n *(Amended pursuant to Clerk’s Order dated 1/25/18)\n ________________\n Appeal from the United States District Court\n for the District of New Jersey\n (D.C. Civil Action No. 2-16-cv-01110)\n District Judge: Honorable Susan D. Wigenton\n ________________\n\n Argued June 12, 2018\n\n Before: AMBRO, JORDAN, and\n HARDIMAN, Circuit Judges\n\n (Opinion filed: January 29, 2019)\n\nJustin D. Santagata (Argued)\nKaufman Semeraro & Leibman\nTwo Executive Drive, Suite 530\nFort Lee, NJ 07024\n\n Counsel for Appellant\n\nKenyatta K. Stewart, Acting Corporation Counsel\nWilson D. Antoine (Argued)\nCity of Newark–Department of Law\n920 Broad Street, Room 316\nNewark, NJ 07102\n\n Counsel for Appellees\n\n ________________\n OPINION OF THE COURT\n ________________\n\nAMBRO, Circuit Judge\n\n Newark police officers forcibly entered and searched\nthe apartment of Adriano Roman’s girlfriend. App. at 386,\n391, 459, 486. They arrested Roman, who was present in the\napartment, after they found drugs in a common area that was\nshared by multiple tenants. Id. at 399, 479. Though he was\nimprisoned for over six months and indicted for various drug\n\n\n\n\n 2\n\noffenses, the New Jersey Superior Court found the search to\nbe unlawful and the charges were dropped.\n\n Roman now brings claims against the City of Newark\n(which includes its Police Department) and various police\nofficers under 42 U.S.C. § 1983 (which gives a federal\nremedy against state officials who, acting under color of state\nlaw, deprive “any citizen of the United States . . . of any\nrights, privileges, or immunities secured by the [U.S.]\nConstitution and laws”) and New Jersey tort law. He alleges\nthe City had a pattern or practice of constitutional violations\nand failed to train, supervise, and discipline its officers. He\nalso pleads an unlawful search claim against the officers and\ncontends they are liable for false imprisonment and malicious\nprosecution. The District Court dismissed all of the claims\nbecause they were inadequately pled. It also held the City did\nnot have an ongoing practice of unconstitutional searches and\narrests.\n While most of Roman’s claims do not withstand\ndismissal, his § 1983 claims against the City do. He has\nadequately alleged that its Police Department had a custom of\nwarrantless searches and false arrests. He also sufficiently\npled that the Department failed to train, supervise, and\ndiscipline its officers, specifically with respect to “the\nrequirements of [the] Fourth Amendment and related law.”\nApp. at 160. Because Roman has stated a plausible claim\nagainst the City, we vacate and remand the District Court’s\nholding on municipal liability. We affirm in all other\nrespects.\n\n\n\n\n 3\n\nI. Background1\n On May 2, 2014, Roman and his girlfriend Tiffany\nReyes were watching a movie in her apartment’s bedroom.\nApp. at 386, 389, 395. Unbeknownst to them, four Newark\npolice officers had set up surveillance outside of her building\nbecause of complaints about narcotics activity. Id. at 338.\nThe officers heard an argument between a man and a woman,\nid. at 340-42, and decided to enter Reyes’ apartment without\na warrant, id. at 491.\n After they stepped inside the building, they discovered\nthat the front door of the apartment was locked. They also\n\n 1\n As noted below, we must, while reviewing a ruling\non a motion to dismiss, view the facts in the light most\nfavorable to the plaintiff. Accordingly, without judging the\nfacts, we recount them as set out in the amended complaint\nand the transcript of the suppression hearing referred to\nbelow. Although Roman did not attach the transcript to the\namended complaint, the Defendants included it in their\nmotion to dismiss and told the District Court it was “capable\nof judicial notice” and “integral to the [c]omplaint.” App. at\n130. Thus we consider it at this stage.\n\n In any event, both the amended complaint and\ntranscript note that the officers forcibly entered the apartment,\nassaulted Roman, and falsely charged him with possession of\na controlled substance. See Am. Compl. ¶¶ 17, 22, 28. Any\nminor differences in the two documents do not affect our\nanalysis of his municipal liability claim. See infra Section\nIII.A (explaining that the events leading up to Roman’s\nsearch and arrest are not relevant to the merits of his\nmunicipal liability claim).\n\n\n\n\n 4\n\nnoticed Melissa Isaksem, Reyes’ friend, walking inside the\nbuilding. Id. at 417-20. They stopped and questioned her.\nId. at 417, 419. When she told them she was visiting Reyes,\nid. at 419, they ordered her to knock on the apartment door\nfor them and threatened to arrest her if she did not comply, id.\nat 419-20. Isaksem led them to the apartment and stood\ndirectly in front of the peephole. Id. at 421. The police stood\nto her left, presumably out of the peephole’s range. Id. An\nofficer knocked on her behalf. Id. Reyes asked who was at\nthe door, and Isaksem announced her presence. Id.\n Reyes opened the door, expecting to see only Isaksem.\nId. at 386, 400, 501. Instead, several officers rushed inside.\nId. at 387, 400, 501. They handcuffed Roman, Reyes, and\nIsaksem, then demanded Roman “call someone to bring drugs\nto the [apartment].” Am. Compl. ¶ 30 (internal quotation\nmarks omitted). If he did, they assured him they would\n“‘make a deal’ and ‘let him go.’” Id. Roman refused the\nofficers’ demands, id. ¶ 33, and the police searched the\napartment. Eventually they found drugs in a common-area\nspace that was shared by multiple tenants and located in the\nback of the apartment. App. at 399, 479. After seizing the\ncontraband, they yelled, “[W]e got you, motherfucker[;] . . .\nyou’re fucked now.” Id. at 427. Officer Rodger Mendes\nwalked back to Roman, “flipped him . . . on[]to his stomach\n. . . , put his knee in his neck[,] and . . . said he was going to\nget raped [in prison].” Id. at 428. Another officer informed\nRoman’s father, who lived next door and observed parts of\nthe search, that his son “would go away for a long time.” Id.\nat 454.\n Roman was arrested and imprisoned on the same night.\nThe officers filed a criminal complaint against him for\npossession of, as well as intent to distribute, heroin and\ncocaine. A New Jersey grand jury returned a six-count\nindictment against him for the same offenses.\n\n\n\n\n 5\n\n In response, Roman moved to suppress the evidence\nseized from the apartment. He argued the search was invalid\nunder the Fourth Amendment because the contraband was not\nin plain view and thus a warrant was needed. The New Jersey\nSuperior Court agreed. It concluded the plain-view exception\ndid not apply and suppressed the contraband.\n The State of New Jersey did not appeal the ruling and\ninstead moved to dismiss the case. The Superior Court\ngranted its motion in December 2014 and issued a final\njudgment of dismissal. Roman was released from prison\nduring the same month.\n Approximately a year later, Roman brought § 1983\nand state-law tort claims against the City of Newark and\nvarious police officers (for simplicity, the City and the\nofficers are jointly referred to as the “Defendants”). Among\nother things, he alleged the City had a custom or policy of\nunconstitutional searches, inadequate training, and poor\nsupervision and discipline.2 He also claimed the officers\nunlawfully searched his apartment and were liable for the\ntorts of unlawful imprisonment and malicious prosecution.3\n\n\n 2\n Roman’s amended complaint also included\nallegations of discrimination of national origin in violation of\n42 U.S.C. § 1983, civil conspiracy in violation of 42 U.S.C.\n§ 1985, conspiracy to commit an unlawful search in violation\nof the New Jersey Constitution and 42 U.S.C. § 1985, and\nconspiracy to commit unlawful imprisonment in violation of\n42 U.S.C. § 1985. We do not address these claims, as Roman\ndoes not press them on appeal.\n 3\n We construe Roman’s claim for unlawful\nimprisonment as a claim for false imprisonment. Although\n\n\n\n\n 6\n\n The Defendants responded with a motion to dismiss.\nThe District Court sided with them, dismissing the complaint\nin its entirety. It first addressed Roman’s claim against the\nCity and concluded the complaint “fail[ed] to plead . . . a\ncustom or policy” of unlawful searches and a failure to train\nor supervise officers. Roman v. City of Newark, Civil Action\nNo. 16-1110-SDW-LDW, 2017 WL 436251, at *4 (D.N.J.\nJan. 30, 2017). Although the complaint alleged “a pattern or\npractice of constitutional violations in areas including stop[]\nand arrest practices, use of force, and theft by officers,” the\nCourt did not consider that sufficient to state a claim. Id.\n(internal quotation marks omitted) (quoting Compl. ¶ 59).\nInstead, it viewed those practices as predating Roman’s arrest\nand observed that “the imposition of a [f]ederal [m]onitor\nindicate[d] [the City’s] attempts to change any wrongful\npolicies or practices.” Id.\n The Court also held the unlawful search claim was\ninadequately pled, as Roman did not “explain which\n[Defendant(s)] committed the allegedly wrongful acts” during\nthe search and arrest. Id. Turning to the false imprisonment\nand malicious prosecution claims, it construed them as state-\nlaw claims and noted that plaintiffs must comply with the\n\nNew Jersey lacks a cause of action for “unlawful\nimprisonment,” it has codified the elements of a false\nimprisonment claim. See N.J. Stat. Ann. § 2C:13-3; Mallery\nv. Erie R. Co., 92 A. 371, 371 (N.J. 1914) (“This appeal\nbrings up a judgment recovered by the respondent in an\naction for false imprisonment. The declaration described\nthe unlawful imprisonment. . . .”); see also 8 American Law\nof Torts § 27:1 (“False imprisonment, sometimes called\ncriminal restraint or unlawful imprisonment, is committed\nwhen a defendant so restrains another person as to interfere\nsubstantially with his liberty.”).\n\n\n\n\n 7\n\nNew Jersey Tort Claims Act before bringing them against\npublic entities. See N.J. Stat. Ann. § 59:8-1 et seq. Because\nthe “[c]omplaint nowhere allege[d]” Roman complied with\nthe Act’s procedures, the Court dismissed those claims as\nwell. Roman, 2017 WL 436251, at *6.\n\n The Court’s dismissal was without prejudice, and it\ngranted Roman leave to amend. He did so by omitting his\ntort claims and retaining his other allegations in almost\nidentical form. The Court dismissed his amended complaint\nand reaffirmed its ruling on reconsideration. This appeal\nfollowed.4\nII. Jurisdiction and Standard of Review\n The District Court had federal-question and\nsupplemental jurisdiction per 28 U.S.C. §§ 1331 and 1367(a),\nrespectively, and we have jurisdiction over its final orders\nunder 28 U.S.C. § 1291.\n We review de novo its dismissal of a complaint under\nFederal Rule of Civil Procedure 12(b)(6). See Phillips v.\nCounty of Allegheny, 515 F.3d 224, 230 (3d Cir. 2008).\nWhen conducting our review, “we accept all factual\nallegations as true [and] construe the complaint in the light\nmost favorable to the plaintiff.” Warren Gen. Hosp. v.\nAmgen Inc., 643 F.3d 77, 84 (3d Cir. 2011) (internal\nquotation marks omitted). However, “we are not compelled\nto accept unsupported conclusions and unwarranted\ninferences . . . or a legal conclusion couched as a factual\nallegation[.]” Baraka v. McGreevey, 481 F.3d 187, 195 (3d\n\n\n 4\n Roman passed away while this appeal was pending,\nand his estate brings the claims on his behalf. We do not\ndistinguish between Roman and his estate in this opinion.\n\n\n\n\n 8\n\nCir. 2007) (internal quotation marks omitted) (internal\ncitation omitted).\n\nIII. Discussion\n A. Roman sufficiently pled a municipal liability\n claim against Newark.\n\n As noted, Roman alleges the City is liable under\n§ 1983 because it “engaged in a pattern or practice of\nconstitutional violations,” “failed to properly train and/or\nsupervise” its police force, and “failed to properly and\nadequately control and discipline” its police officers.5 Am.\nCompl. ¶¶ 68, 73-74. Before discussing the merits of his\nclaims, Roman directs our attention to the types of documents\nwe may consider on a motion to dismiss. He contends we\nmay review three sources that were provided to the District\nCourt: an article published in the Newark Star Ledger (the\n“Star Ledger article”), a press release issued by the U.S.\nAttorney’s Office (the “press release”), and a consent decree\nbetween the United States and the City of Newark (the\n“consent decree”). The Star Ledger article and press release\nwere referenced in the amended complaint, see id. ¶¶ 68-69\n(including hyperlinks to both), but the consent decree was\nattached to the Defendants’ motion to dismiss, see App. at\n129. Roman also asks us to look at one other document: the\nDepartment of Justice’s Report on the investigation of the\nNewark Police Department (the “DOJ Report”). Although he\n\n 5\n Roman brings his municipal liability claims under\n§ 1983 and the New Jersey Civil Rights Act, N.J. Stat. Ann.\n§ 10:6-1 et seq. Because the latter “is interpreted analogously\nto . . . § 1983,” we consider his New Jersey Civil Rights Act\nclaims along with his § 1983 claim. Coles v. Carlini, 162 F.\nSupp. 3d 380, 404 (D.N.J. 2015).\n\n\n\n\n 9\n\nacknowledges the DOJ Report was never provided to the\nDistrict Court, he now claims it is integral to the pleadings.\n\n Though the Defendants dispute that we may consider\nthe DOJ Report, they add that we also cannot consider the\nconsent decree because “no relevant provisions of [it] . . .\nwere ever cited . . . to the District Court” and it is\ninadmissible settlement material. Defendants’ Br. at 42.\nThey assert as well, without any citation to the record, that\nRoman may not rely on the decree because he asked the\nDistrict Court to confine its analysis to the pleadings.\n We disagree with the Defendants’ view of the consent\ndecree. Although we examine the “complaint, exhibits\nattached to the complaint, [and] matters of public record,”\nMayer v. Belichick, 605 F.3d 223, 230 (3d Cir. 2010), we can\nalso consider documents “that a defendant attaches as an\nexhibit to a motion to dismiss,” Pension Benefits Guar. Corp.\nv. White Consol. Indus., Inc., 998 F.2d 1192, 1196 (3d Cir.\n1993), if they are “undisputedly authentic” and “the\n[plaintiff’s] claims are based [on them],” Mayer, 605 F.3d at\n230. That holding extends to settlement material because\nplaintiffs “need not provide admissible proof at th[e] [motion-\nto-dismiss] stage.” In re OSG Sec. Litig., 12 F. Supp. 3d 619,\n622 (S.D.N.Y. 2014); see also In re MyFord Touch Consumer\nLitig., 46 F. Supp. 3d 936, 961 n.5 (N.D. Cal. 2014) (same).\nMoreover, the Supreme Court has been clear about the scope\nof our review, stating we “must consider the complaint in its\nentirety, as well as other sources [we] ordinarily examine\nwhen ruling on . . . motions to dismiss, in particular,\ndocuments incorporated into the complaint by reference, and\nmatters of which a court may take judicial notice.” Tellabs,\nInc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 322 (2007)\n(emphasis added).\n\n\n\n\n 10\n\n Here, although the consent decree was not attached to\nRoman’s amended complaint, we are free to review its\ncontents for three reasons.6 First, the Defendants attached the\ndecree to their motion to dismiss and affirmed that it is\n“capable of judicial notice” as an indisputably authentic\ngovernment document. App. at 129. Second, contrary to the\ndissent’s assertion, the Defendants themselves argued (and\ncorrectly) before the District Court that Roman’s claims were\nbased on the consent decree. Compare Dissenting Op. at 5\n(“What is crucial is whether Roman’s complaint was ‘based’\non the consent decree.”), with App. at 129 (filing from\nDefendants characterizing the consent decree as “integral to\nthe Complaint”). Third, the amended complaint cited, and the\nDistrict Court discussed, the DOJ investigation and federal\nmonitor that eventually led to the consent decree. See\nRoman, 2017 WL 436251, at *4; see also Am. Compl. ¶¶ 68-\n71. Thus it was especially important for the Court to have\nconsidered the decree as well, given that it provides essential\ncontext to Roman’s claims. That it did not was an abuse of\ndiscretion.\n\n That said, we may not consider the DOJ Report at this\nstage because it was not provided to the District Court in the\nfirst instance by any party. Nor is it apparent that the Court\nconsidered it sua sponte. See United States ex rel. Wilkins v.\n\n 6\n Though the Defendants and our dissenting colleague\ndo not challenge the Star Ledger article or the press release,\nwe note that we consider them because they are referenced in\nthe amended complaint. See Tellabs, 551 U.S. at 322. As\nJudge Jordan explains in his concurrence, however, Roman\ndoes not need either document or the suppression hearing\ntranscript to state a municipal liability claim; the consent\ndecree gives his allegations enough plausibility to survive\ndismissal.\n\n\n\n\n 11\n\nUnited Health Grp., Inc., 659 F.3d 295, 302 (3d Cir. 2011)\n(“Though we do not doubt the authenticity of\nthese documents, nevertheless we will not consider them\nbecause the parties did not present them to the District Court\nand we do not find any indication in the record that the Court\nconsidered them on its own initiative.”). Hence it cannot\ncarry any weight in our analysis.\n Turning to the amended complaint, Roman claims the\nCity is liable for his unlawful search because it “failed to train\nits officers in the use of search and seizure techniques,\nprobable cause, and/or methods to properly obtain a search\nwarrant.” Am. Compl. ¶ 95. He alleges the Newark Police\nDepartment “engaged in a pattern or practice of constitutional\nviolations” and asserts the Department of Justice appointed a\nfederal monitor to oversee the reforms to which the City\nconsented. Id. ¶ 68. His allegations also touch on the City’s\nfailure to “control and discipline” its police force, id. ¶ 74,\nand failure to “investigate . . . instances of . . . police\nmisconduct,” id. ¶ 81. He characterizes the City’s practices in\nthese areas as “tantamount to a[n] [unconstitutional] custom\nand/or policy,” id. ¶ 82, thus indicating its “deliberate\nindifference to [its citizens’ constitutional] rights,” id. ¶ 83.\n The Defendants respond that Roman has failed to\nallege a municipal liability claim, as no part of the Star\nLedger article, press release, or consent decree references the\ntypes of constitutional violations pled in the amended\ncomplaint. They also contend the City had no notice “of any\npattern of constitutional violations with respect to forced\nentry and searches of homes.” Defendants’ Br. at 50.\n To plead a municipal liability claim, a plaintiff must\nallege that “a [local] government’s policy or custom . . .\ninflict[ed] the injury” in question. Monell v. Dep’t of Soc.\nServs., 436 U.S. 658, 694 (1978). “Policy is made when a\n\n\n\n\n 12\n\ndecisionmaker possess[ing] final authority to establish\nmunicipal policy with respect to the action issues an official\nproclamation, policy, or edict.” Andrews v. City of\nPhiladelphia, 895 F.2d 1469, 1480 (3d Cir. 1990) (alteration\nin original) (internal quotation marks omitted). “Custom, on\nthe other hand, can be proven by showing that a given course\nof conduct, although not specifically endorsed or authorized\nby law, is so well-settled and permanent as virtually to\nconstitute law.” Bielevicz v. Dubinon, 915 F.2d 845, 850 (3d\nCir. 1990) (Becker, J.); see also Brown v. Muhlenberg Twp.,\n269 F.3d 205, 215 (3d Cir. 2001) (“A custom . . . must have\nthe force of law by virtue of the persistent practices of state\n[or municipal] officials.” (internal quotation marks omitted)).\n Although a policy or custom is necessary to plead a\nmunicipal claim, it is not sufficient to survive a motion to\ndismiss. A plaintiff must also allege that the policy or custom\nwas the “proximate cause” of his injuries. See Kneipp v.\nTedder, 95 F.3d 1199, 1213 (3d Cir. 1996). He may do so by\ndemonstrating an “affirmative link” between the policy or\ncustom and the particular constitutional violation he alleges.\nBielevicz, 915 F.2d at 850 (internal quotation marks omitted).\nThis is done for a custom if Roman demonstrates that Newark\nhad knowledge of “similar unlawful conduct in the past, . . .\nfailed to take precautions against future violations, and that\n[its] failure, at least in part, led to [his] injury.” Id. at 851.\nDespite these requirements, Roman does not need to identify\na responsible decisionmaker in his pleadings. See id. at 850.\nNor is he required to prove that the custom had the City’s\nformal approval. See Anela v. City of Wildwood, 790 F.2d\n1063, 1067 (3d Cir. 1986).\n The pleading requirements are different for failure-to-\ntrain claims because a plaintiff need not allege an\nunconstitutional policy. See Reitz v. County of Bucks, 125\nF.3d 139, 145 (3d Cir. 1997) (“[I]n the absence of an\n\n\n\n\n 13\n\nunconstitutional policy, a municipality’s failure to properly\ntrain its employees and officers can create an actionable\nviolation . . . under § 1983.”). Instead, he must demonstrate\nthat a city’s failure to train its employees “reflects a deliberate\nor conscious choice.” Brown, 269 F.3d at 215 (internal\nquotation marks omitted). For claims involving police\nofficers, the Supreme Court has held that the failure to train\n“serve[s] as [a] basis for § 1983 liability only where [it] . . .\namounts to deliberate indifference to the rights of persons\nwith whom the police come into contact.” City of Canton v.\nHarris, 489 U.S. 378, 388 (1989) (footnote omitted). A\nplaintiff sufficiently pleads deliberate indifference by\nshowing that “(1) municipal policymakers know that\nemployees will confront a particular situation[,] (2) the\nsituation involves a difficult choice or a history of employees\nmishandling[,] and (3) the wrong choice by an employee will\nfrequently cause deprivation of constitutional rights.” Doe v.\nLuzerne County, 660 F.3d 169, 180 (3d Cir. 2011) (internal\nquotation marks omitted) (quoting Carter v. City of\nPhiladelphia, 181 F.3d 339, 357 (3d Cir. 1999)).\n\n In view of this case law, Roman has not pled a\nmunicipal policy, as his amended complaint fails to refer to\n“an official proclamation, policy, or [an] edict.” Andrews,\n895 F.2d at 1480. However, he has sufficiently alleged a\ncustom of warrantless or nonconsensual searches. He has\nalso adequately pled that the City failed to train, supervise,\nand discipline its police officers.7\n\n\n 7\n We consider allegations of failure to train, supervise,\nand discipline together because they fall under the same\nspecies of municipal liability. See Rosalie Berger Levinson,\nWho Will Supervise the Supervisors? Establishing Liability\nfor Failure to Train, Supervise, or Discipline in a Post-\n\n\n\n\n 14\n\n We start with Roman’s allegations on municipal\ncustom. He asserts the City had “a pattern or practice of\nconstitutional violations in areas including . . . arrest\npractices.” App. at 137. He further contends it had notice of\nthis practice, as it received “complaints against officers\naccused of . . . conducting improper searches and false\narrests.” Id. at 134. The amended complaint, along with the\npress release and Star Ledger article, note that Newark was\nunder the supervision of a federal monitor after Roman’s\narrest. Am. Compl. ¶ 68; App. at 133, 137. According to the\npress release, the monitor would oversee reforms in several\nareas, including searches, arrests, and the intake and\ninvestigation of misconduct complaints. App. at 137.\n The consent decree echoes these points. It covers the\nsame type of conduct Roman alleges, as it “prohibit[s]\nofficers from relying on information known to be materially\nfalse or incorrect to justify a warrantless search . . . [or to]\neffect[] an arrest.” Id. at 158; see also id. at 163 (mandating\nofficers to collect data on consent, the type of search, and “a\nbrief description of the facts creating probable cause”). The\ndecree also requires the Police Department to investigate\npolice misconduct, see generally id. at 184-92, with special\nemphasis on allegations of criminal misconduct, false arrest,\nplanting evidence, and unlawful searches, see id. at 150, 186.\n While the consent decree was not in place during\nRoman’s search and arrest, we may fairly infer that the\nproblems that led to it were occurring during the time of his\nallegations and for some time before that. See id. at 133-34\n(noting the investigation that resulted in the consent decree\nand federal supervision began in May 2011 and ended in July\n2014). With this mind, the decree fortifies Roman’s\n\nIqbal/Connick World, 47 Harv. C.R.-C.L. L. Rev. 273, 280\n(2012).\n\n\n\n\n 15\n\nallegations of unlawful custom because it acknowledges “a\npattern or practice of conduct by the Newark Police\n[Department] that deprives individuals of rights, privileges,\nand immunities secured by the Constitution.” Id. at 144.\nWhen viewed in conjunction with the Star Ledger article, it\nreferences the types of constitutional violations mentioned in\nthe amended complaint: warrantless searches, id. at 134, and\nfalse arrests, id. at 158. These violations were widespread\nand causally linked to Roman’s alleged injury, as the Police\nDepartment was aware of them but “rare[ly] . . . acted” on\ncitizen complaints. Id. at 134 (discussing complaints of\n“improper searches and false arrests”); see also Beck v. City\nof Pittsburgh, 89 F.3d 966, 974 (3d Cir. 1996) (noting the\npolice department’s failure to act on complaints\n“perpetuate[d] the City’s custom of acquiescing in the\nexcessive use of force by its police officers”). In light of\nthese allegations, “it is logical to assume that [the City’s]\ncontinued official tolerance of repeated misconduct\nfacilitate[d] similar unlawful actions in the future,” including\nthe search and arrest of Roman. Bielevicz, 915 F.2d at 851. It\nfollows that he has adequately pled a municipal custom and\nproximate causation under § 1983.\n We reach the same conclusion with respect to\nRoman’s failure-to-train, failure-to-supervise, and failure-to-\ndiscipline claims. To start, the Star Ledger article includes a\nstatement on police training from James Stewart, Jr., the head\nof Newark’s police union. He conceded the “last training [he]\nreceived” was in 1995, when he first joined the Newark\nPolice Department. App. at 134 (internal quotation marks\nomitted). Moreover, Stewart is not some unreliable, rogue\nofficer—he is the head of the police union. Nor is his\nexperience isolated: the consent decree indicates Newark\npolice officers in general were not trained on “the\nrequirements of [the] Fourth Amendment and related law.”\nId. at 160 (discussing various Fourth Amendment doctrines\n\n\n\n\n 16\n\nthat should be included in police training, including “the\ndifference[] . . . between voluntary consent and mere\nacquiescence to police authority”). The consent decree also\ntouches on supervisory review of unlawful searches and\narrests, requiring desk lieutenants and unit commanders to\nreview “searches that appear to be without legal justification”\nand “arrests that are unsupported by probable cause.” Id. at\n161. Finally, it provides disciplinary measures for police\nofficers who engage in “unlawful . . . searches” and “false\narrests.” Id. at 192. At the pleadings stage, a fair inference is\nthat the consent decree was necessary because of Department-\nwide failures, not because one officer was last trained in\n1995.\n This is enough to prove municipal liability because the\nCity “[knew] to a moral certainty” that its officers would need\nto conduct searches. Harris, 489 U.S. at 390 n.10. Yet in at\nleast one instance it failed to provide training since 1995, see\nApp. at 134, and per the decree its training did not cover the\nbasics of the Fourth Amendment, see id. at 158-61. The City\nalso did not discipline officers for “sustained allegations of\nmisconduct,” including “prior violations” and other\n“aggravating factors.” Id. at 192-93. In view of these\ndeficiencies, one could reasonably infer that the City’s\ninaction “reflected [its] ‘deliberate indifference’” to Roman’s\nFourth Amendment rights. Bd. of Cty. Comm’rs v. Brown,\n520 U.S. 397, 409 (1997); cf. Harris, 489 U.S. at 390 n.10\n(“[C]ity policymakers know to a moral certainty that their\npolice officers will be required to arrest fleeing felons. . . .\nThus, the need to train officers in the constitutional\nlimitations on the use of deadly force . . . can be said to be ‘so\nobvious’ . . . that failure to do so could properly be\ncharacterized as ‘deliberate indifference’ to constitutional\nrights.” (internal citation omitted)). One could also infer that\nthe City’s failure to establish an adequate training program\ncontributed to the specific constitutional violations alleged in\n\n\n\n\n 17\n\nthe amended complaint. See Brown, 520 U.S. at 409-10\n(“The likelihood that the situation will recur and the\npredictability that an officer lacking specific tools to handle\nthat situation will violate citizens’ rights . . . may also support\nan inference of causation.”); cf. A.M. ex rel. J.M.K. v. Luzerne\nCty. Juvenile Detention Ctr., 372 F.3d 572, 582 (3d Cir.\n2004) (reversing the District Court’s grant of summary\njudgment in favor of a municipality because of “unrebutted\ntestimony” that its juvenile detention center “did not have an\nadequate training program”).\n We conclude that the allegations regarding Newark’s\nfailure to train, supervise, and discipline are strong enough to\nsurvive a motion to dismiss. See Am. Compl. ¶¶ 63-98.\nAmong them are: a failure to train officers on obtaining a\nsearch warrant, id. ¶ 67, and on “issuing truthful investigative\nreports,” id. ¶ 77; a failure to supervise and manage officers,\nid. ¶¶ 67-68; and a failure to discipline officers, id. ¶ 74, first\nby “refus[ing]” to create a well-run Internal Affairs\nDepartment, id. ¶ 81, and second by “inadequately\ninvestigating, if investigating at all, citizens’ complaints\nregarding illegal search and seizure, id. ¶ 84. The result was a\n“complete lack of accountability” and of “record keeping,” id.\n¶ 92, leading to a culture in which officers “knew there would\nbe no professional consequences for their action[s],” id. ¶ 94.\nAs the amended complaint alleges, it should come as no\nsurprise that these conditions led to a federal investigation.\nSee id. ¶ 89.\n The dissent’s attempt to distinguish the consent decree\nis unpersuasive. First, it misperceives the decree as\nconcerning only police interactions with “pedestrians or the\noccupants of vehicles,” not home searches. Dissenting Op. at\n7 (“The consent decree says nothing about arrests and\nsearches without consent that occur at residences . . .”). In\nfact, one concern of the decree was false arrests, see App. at\n\n\n\n\n 18\n\n158, which can occur both at home and on the street. And the\ndecree does concern home searches: it sets parameters\nofficers must follow before searching “a home based upon\nconsent.” Id. Although Reyes by no means consented to the\nsearch here, she willingly opened her apartment door only\nbecause the police had used her friend Isaksem as a Trojan\nhorse to gain entry.\n Second, the dissent believes that the consent decree\ncannot help Roman’s case because Roman was Hispanic. See\nDissenting Op. at 7 (“[T]he decree addressed police practices\nthat disparately impacted the black community. But that\nracial disparity did not apply to Roman, who was Hispanic.”).\nTo the contrary, the consent decree includes an entire section\nentitled “Bias-Free Policing,” see App. at 165-67, that never\nrestricts itself to bias against the black community. Instead, it\nprovides that police officers must “operate without bias based\non any demographic category,” id. at 166 (emphasis added),\nand specifically forbids officers from discriminating based on\n“proxies for demographic category” such as “language\nability,” id. at 167. Plainly, the consent decree was meant to\nprotect all Newark residents, including Hispanic residents.\n Further, we find it difficult to square the dissent’s\nreasoning with the record evidence discussing the City’s\ntroubling practices around the time of Roman’s search and\narrest. See, e.g., id. at 134 (stating only one complaint out of\n261 filed was sustained by department investigators); id. at\n158 (prohibiting officers from relying on materially false\ninformation to justify a warrantless search); id. at 160\n(requiring police officers to be trained on “the requirements\nof [the] Fourth Amendment and related law”); id. at 161\n(mandating supervisory review of “searches that appear to be\nwithout legal justification” and “arrests that are unsupported\nby probable cause”).\n\n\n\n\n 19\n\n Unable to distinguish the consent decree outright, the\ndissent offers two narrow readings of the decree. First, it\nmaintains that the decree can speak only to the Police\nDepartment’s obligations going forward rather than shed any\nlight whatsoever on the “status quo” within the Department\nbefore federal intervention. See Dissenting Op. at 10 (stating\nthat the decree does not provide “any detail as to the status\nquo it addressed”). The dissent concedes that the DOJ\nprobably did not enter into the consent decree because it was\nimpressed with Newark’s policing practices and wanted to\nencourage the City to keep up the good work. Id. At this\nstage, we must draw not only such obvious inferences, but\nalso all reasonable ones, in favor of Roman. Thus we agree\nwith the dissent on the “clear” difference between “agreeing\nto train more” (the consent decree on its face) and “agreeing\nthat prior training was constitutionally inadequate” (the way\nin which the decree supports Roman’s claims). Id. We\nsimply believe that a reasonable inference bridges the gap in\nthis case. Indeed, no inference is needed because Roman\nmade the link explicit in the amended complaint. See Am.\nCompl. ¶ 89 (stating that the Police Department’s “deliberate\nindifference to citizens’ rights is what led to the imposition of\na [f]ederal [m]onitor program . . . .”).\n\n Second, the dissent believes that the consent decree’s\ntraining requirements, from which we can reasonably infer\ninadequate training before the decree, simply amount to\n“additional training” in, for instance, the requirements of the\nFourth Amendment. Dissenting Op. at 10. To the contrary,\nthe consent decree was meant to take the Newark Police\nDepartment back to basics: Do not lie on a warrant\napplication or to justify a warrantless search, App. at 158;\ninvestigate police activities that appear to have lacked legal\njustification, id. at 161; and at all times follow the\nrequirements of the Fourth Amendment, id. at 160.\n\n\n\n\n 20\n\n The theme of the dissent appears to be that we are\nrefashioning the amended complaint. It claims we are\nvacating the District Court’s decision based on facts and\narguments that were not presented to it. But as discussed\nabove, we are engaged in de novo review of the adequacy of\nthe amended complaint in light of documents that were before\nthe District Court and that informed its allegations. See supra\npp. 8-10. Additionally, and to repeat, the specific events\nleading up to Roman’s search and arrest are not relevant to\nthe merits of his municipal liability claim. Thus we are not\nvacating the Court’s decision for excluding these facts from\nits analysis.\n Rather, our focus is directed to Newark’s practice at\nthe time of Roman’s search and arrest. The Court had notice\nof them, as it acknowledged that Roman alleged “a ‘pattern or\npractice of constitutional violations in areas including stop[]\nand arrest practices, use of force, and theft by officers.’”\nRoman, 2017 WL 436251, at *4 (quoting Compl. ¶ 59).\nNonetheless it dismissed the complaint and amended\ncomplaint because it viewed the City as attempting to change\nits practices. Even if the record can be read that way—and\nwe doubt that8—the District Court’s rationale has the wrong\n\n\n 8\n The record does not support the Court’s inferences,\nas it tells us the DOJ’s investigation was not completed until\nJuly 2014, see App. at 137; the Government did not solicit\napplications for a federal monitor until February 2015, see id.;\nand the consent decree was not final until May 2016, see id.\nat 215. By contrast, Roman was arrested in May 2014 and\nimprisoned until December of that year. As such, it is\nplausible that Newark’s practices were ongoing when police\nofficers searched and arrested him. It is also reasonable to\ninfer that the City’s corrective measures postdated the arrest.\n\n\n\n\n 21\n\nfocus. The question is not whether some evidence can be\nviewed as supporting the City. It is whether, viewing the\npleadings and properly associated documents in the light most\nfavorable to Roman, there are claims plausible enough to\nwithstand a motion to dismiss. We think there is one—the\nmunicipal liability claim. And the Court did not have to look\nbeyond the amended complaint and supporting documents to\nglean these facts.\n\n In sum, Roman’s municipal liability claim survives\ndismissal based on the record that was before the District\nCourt. Because the Court reached the opposite conclusion,\nwe part with its holding. Thus we vacate and remand this\nportion of its decision.\n B. The District Court correctly dismissed the\n false imprisonment and malicious\n prosecution claims because they were not\n pled under § 1983.\n\n Roman alleges the Defendants are also liable for false\nimprisonment and malicious prosecution. As noted, the\nDistrict Court construed these claims as state-law claims. It\ndismissed them because Roman did not comply with the New\nJersey Tort Claims Act’s procedural requirements for\nbringing claims against public entities and public employees.\nSee N.J. Stat. Ann. § 59:8-1 et seq.\n On appeal, Roman contends the Court erred in\ndismissing his claims because they were pled under § 1983.\nThe Defendants counter that both claims were presented as\n\n\n\nHence we do not consider the City’s corrective measures to\nbe enough to defeat Roman’s allegations.\n\n\n\n\n 22\n\nstate-law tort claims. They also point out that Roman omitted\nthem from his amended complaint.9\n\n As a preliminary matter, the Defendants correctly\nobserve that false imprisonment and malicious prosecution\nare not in the amended complaint. Hence we must first\ndecide if Roman has waived his right to challenge their\ndismissal on appeal. If we conclude that waiver does not\napply, we then determine if the District Court correctly\nconstrued them as state-law tort claims.\n We have not applied a strict rule in favor of waiver in\nthis context. Instead, we have allowed “plaintiffs to appeal\ndismissals despite amended pleadings that omit the dismissed\nclaim[,] provided repleading the particular cause of action\nwould have been futile.” United States ex rel. Atkinson v. Pa.\nShipbuilding Co., 473 F.3d 506, 516 (3d Cir. 2007) (emphasis\nin original) (footnote omitted). “Repleading is futile when\nthe dismissal was ‘on the merits.’ A dismissal is on the\nmerits when it is with prejudice or based on some legal\nbarrier other than want of specificity or particularity.” Id. If\na court is uncertain, “doubt[] should be resolved against the\nparty asserting waiver.” Id. at 517 (emphasis in original).\n\n 9\n At oral argument, Roman’s counsel stated the false\nimprisonment claim was repled in Count 13 of the amended\ncomplaint even though that count alleges “conspiracy to\ncommit unlawful imprisonment . . . [in violation of] 42\nU.S.C. § 1985.” App. at 278 (emphasis added); see Audio\nRecording of Oral Argument held June 12, 2018 at 11:39 to\n12:06 (http://www2.ca3.uscourts.gov/oralargument/audio/17-\n2302TheEstateofAdrianoRomanJrvCityofNewarketal.mp3).\nWe do not consider this contention, as it was raised for the\nfirst time at oral argument and thus is waived. See In re\nGrand Jury, 635 F.3d 101, 105 n.4 (3d Cir. 2011).\n\n\n\n\n 23\n\n Here the District Court analyzed both claims on legal\ngrounds. It observed that they were based on the New Jersey\nTort Claims Act, which allows individuals to bring tort claims\nagainst public entities and employees after complying with\ncertain procedural and notice requirements, see Tripo v.\nRobert Wood Johnson Med. Ctr., 845 F. Supp. 2d 621, 626-\n27 (D.N.J. 2012) (summarizing the Act’s procedures for suing\na public entity or employee). It concluded Roman did not\nfollow these requirements and thus dismissed the claims.\n Although the Court was guided by procedural\nconcerns, its dismissal was on the merits. The Tort Claims\nAct bars claims against public entities and employees if a\nplaintiff waits more than two years to file a “notice of claim.”\nSee N.J. Stat. Ann. § 59:8-8(b). The two-year mark is\nmeasured from the day the claim accrues (i.e., the day on\nwhich the public entity or employee allegedly harmed the\nplaintiff). In our case, because Roman’s claims accrued in\nMay 2014, he had until May 2016 to file a notice of claim.\nAs the Court noted, however, he did not file any type of\nnotice during the two-year period. See Roman, 2017 WL\n436251, at *6 (observing that, as of January 31, 2017, the date\non which the Court dismissed the complaint, Roman had not\nfiled a notice). Thus Roman’s procedural error morphed into\na dismissal on the merits, see N.J. Stat. Ann. § 59:8-8(b)\n(“The claimant shall be forever barred from recovering\nagainst a public entity or public employee if . . . [t]wo years\nhave elapsed since the accrual of the claim.”), and he may\nappeal the District Court’s decision on his false imprisonment\nand malicious prosecution claims, see Atkinson, 473 F.3d at\n516-17.\n In light of this conclusion, we must focus on the\npleadings and decide if Roman’s claims are based on § 1983.\nIf we look to the complaint, it suggests both false\nimprisonment and malicious prosecution are state-law tort\n\n\n\n\n 24\n\nclaims. It never identifies them as § 1983 or federal claims.\nRather, it presents them generically, following a series of\nother state-law tort claims. See, e.g., App. at 44 (“intentional\ninfliction of emotional distress”); id. at 46 (“negligent\ninfliction of emotional distress”); id. at 47 (“assault and\nbattery”); id. at 49 (“unlawful imprisonment”); id. at 51\n(“malicious prosecution”). This indicates to us that Roman\npled both claims as state-law claims, not federal claims.\nWhile the unlawful (i.e., false) imprisonment claim does note\nthat the Defendants “restrict[ed] [Roman’s] constitutionally\nguaranteed rights of liberty and freedom of movement,” it is\nsilent as to whether it refers to the United States or New\nJersey Constitution. Compl. ¶ 114. This is too facile to\nimply the former when but a few identifying words would do.\nThe default is New Jersey law, which defines false\nimprisonment as “an[y] unlawful restraint that interferes with\na victim’s liberty” and requires “[n]o further wrongful\npurpose” for a prima facie showing. State v. Savage, 799\nA.2d 477, 494 (N.J. 2009).\n Accordingly, the District Court correctly construed the\nfalse imprisonment and malicious prosecution claims as state-\nlaw tort claims, and we affirm this portion of its holding.10\n C. The doctrines of res judicata, collateral\n estoppel, and judicial estoppel do not require\n us to dismiss Roman’s § 1983 claims.\n Finally, the Defendants invoke the doctrines of res\njudicata, collateral estoppel, and judicial estoppel. According\n\n\n 10\n We also affirm the dismissal of Roman’s unlawful-\nsearch claims because they were not adequately pled. We do\nnot opine on whether a plaintiff may allege joint and several\nliability in connection with an unlawful-search claim.\n\n\n\n\n 25\n\nto them, each doctrine compels us to dismiss Roman’s § 1983\nclaims.\n\n We start with res judicata. The Defendants contend it\nbars Roman’s claims because “the criminal matter and the\nsuppression hearing were based on the exact same facts” as\nthose alleged in Roman’s pleadings. Defendants’ Br. at 64.\nIn their view, criminal proceedings are enough to preclude a\ncivil suit seeking damages under § 1983.\n\n We disagree. “A party seeking to invoke res judicata\nmust establish three elements: (1) a final judgment on the\nmerits in a prior suit involving (2) the same parties or their\nprivies and (3) a subsequent suit based on the same cause of\naction.” Duhaney v. Att’y Gen., 621 F.3d 340, 347 (3d Cir.\n2010) (internal quotation marks omitted). Roman’s suit is not\nbased on the same cause of action as the criminal complaint\nand suppression hearing. Nor are his current claims of the\ntype “that could have been brought” in the earlier criminal\nproceeding. Id. (internal quotation marks omitted); see also\nHelvering v. Mitchell, 303 U.S. 391, 397 (1938) (“The\ndifference in degree of the burden of proof in criminal and\ncivil cases precludes application of the doctrine of res\njudicata.”). New Jersey initiated the criminal case. Roman\nwas not at liberty to assert any claims except for defenses\nagainst the prosecution’s case-in-chief. See Leather v. Eyck,\n180 F.3d 420, 425 (2d Cir. 1999) (“[B]ecause the nature of\nthe prior state[-]court proceeding was such that [the\nAppellant] could not have sought damages for his alleged\nconstitutional injuries (while defending himself on [a\ncriminal] charge . . . ), res judicata does not bar his federal §\n1983 suit for damages.”). Moreover, he was not free to raise\nhis § 1983 claims in the same criminal case; indeed, he could\nnot bring them until the criminal proceeding concluded. See\nHeck v. Humphrey, 512 U.S. 477, 486 (1994) (“[T]he . . .\nprinciple that civil tort actions are not appropriate vehicles for\n\n\n\n\n 26\n\nchallenging the validity of outstanding criminal judgments\napplies to § 1983 damages actions that necessarily require the\nplaintiff to prove the unlawfulness of his conviction or\nconfinement. . . .”). Accordingly, res judicata does not bar\nRoman’s claims.\n\n Moving on to collateral estoppel, the Defendants argue\nit (1) absolves Officer Mendes of liability because the\nSuperior Court made a factual finding that Roman possessed\nthe contraband that was seized from the apartment, (2)\nabsolves Sergeant Joyce Hill because nothing in the Superior\nCourt’s transcript indicates she was present for the search and\narrest, and (3) absolves the other named defendants because\nthe Superior Court’s transcript suggests they only handled the\ncontraband. According to the Defendants, the Superior Court\ndecided all of these issues in their favor during the\nsuppression hearing. See Bd. of Trs. of Trucking Emps. of N.\nJersey Welfare Fund, Inc. v. Centra, 983 F.2d 495, 505 (3d\nCir. 1992) (stating a party is collaterally estopped from\nlitigating a specific issue if, among other things, “[an]\nidentical issue was decided in a prior adjudication”). Again\nwe disagree. Contrary to the Defendants’ assertions, the\nSuperior Court never decided any of these issues during the\nsuppression hearing. While it did find that Roman had a\npossessory interest in the apartment, that is not enough for us\nto conclude that he had actual or constructive possession over\nthe contraband. Collateral estoppel is not appropriate in this\ncontext.\n Last, the Defendants assert that judicial estoppel\nprecludes Roman’s claims because he admitted that (1) drugs\nwere found in the apartment, (2) he had a possessory interest\nin the apartment, (3) Officer Mendes was the only officer who\ninitiated the prosecution, and (4) the remaining officers only\nhandled the contraband and had no other roles. They insist\nthese concessions “are sufficient to establish that [Roman’s]\n\n\n\n\n 27\n\narrest and prosecution arise out of his possession of\nincriminating evidence[.]” Defendants’ Br. at 65. As noted,\n“[j]udicial estoppel, sometimes called the ‘doctrine against\nthe assertion of inconsistent positions,’ is a judge-made\ndoctrine that . . . prevent[s] a litigant from asserting a position\ninconsistent with one that []he has previously asserted . . . in a\nprevious proceeding.” Ryan Operations G.P., 81 F.3d at 358.\nThis doctrine is not in play here, as Roman never stipulated\nthat Officer Mendes was the only officer to bring the\nprosecution or that the remaining officers only handled the\ncontraband. While the Court found that Roman had a\npossessory interest in the apartment, that interest (we repeat)\nis not enough to establish that he possessed the contraband.\nAccordingly, judicial estoppel does not require us to dismiss\nRoman’s claims.\n * * * * *\n Roman has sufficiently alleged a municipal liability\nclaim against the City of Newark under § 1983. He cites\nvarious examples of inadequate police training, poor police\ndiscipline, and unheeded citizen complaints. He tells us\ncertain police officers did not receive training for over 20\nyears, and their training did not cover the basic requirements\nof the Fourth Amendment. In his pleadings, he states the\nNewark Police Department did not discipline officers who\nengaged in police misconduct, Am. Compl. ¶¶ 84-86,\nincluding unlawful searches and false arrests, App. at 134.\nHe also notes the public filed formal complaints about\nimproper searches and false arrests that were disregarded\nalmost wholesale. Id. These alleged practices were ongoing\nwhen Roman’s search and arrest occurred, and the City had\nnotice of them at that time. While the proof developed to\nsupport these allegations may or may not be persuasive to a\nfinder of fact, they are enough to survive dismissal at this\nstage. Based on this conclusion, we part with the District\n\n\n\n\n 28\n\nCourt’s holding that Roman failed to state a § 1983 claim\nagainst the City. Though we affirm otherwise, we vacate and\nremand its decision on municipal liability.\n\n\n\n\n 29", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362697/", "author_raw": "AMBRO, Circuit Judge"}, {"author": "JORDAN, Circuit Judge, concurring", "type": "concurrence", "text": "JORDAN, Circuit Judge, concurring.\n\n I join the majority opinion and write separately only to\nnote that, even if we were to ignore the suppression hearing\ntranscript and the press release and the Star Ledger article,\nthere is still a sound basis to conclude that Roman has stated\nplausible claims for municipal liability. Our panel is united in\nunderstanding that we can properly consider the consent decree\nbecause it was provided to the District Court and was\nreferenced and relied upon in Roman’s amended complaint.\nThose two sources – the consent decree and the amended\ncomplaint – are sufficient to overcome the motion to dismiss\nthe claims against the City of Newark.\n\n The consent decree supports the allegations in the\namended complaint in a number of respects. For example, it\nexpressly prohibits Newark Police officers “from relying on\ninformation known to be materially false or incorrect to justify\na warrantless search or to seek a search warrant[.]” (App. at\n158). A fair inference from that prohibition is that it was\nneeded precisely because the police were often relying on false\ninformation to justify warrantless searches. That inference\nbolsters Roman’s allegation that “[n]o drugs were found in\n[his] possession” and yet the police “arrested [him] and falsely\ncharged him with possession of a controlled dangerous\nsubstance[.]” (App. at 263 ¶¶ 28-29).\n\n In another instance, the consent decree suggests that\nthere has been a lack of training and supervision in the Newark\nPolice Department. To remedy that deficiency, the consent\ndecree requires the Department to “provide all officers with at\nleast 16 hours of training on stops, searches, arrests, ... [and]\n\n\n\n\n 1\n\ntraining ... in ... Fourth Amendment issues” as well as\nmandating “desk lieutenant[s] or unit commander[s] [to]\nreview each arrest report by officers under their command[.]”\n(App. at 159-61). The inference that there was inadequate\ntraining supports Roman’s allegation that the Department’s\nofficers, “through their actions, inactions, course of conduct,\npoor or non-existent training and deficient supervision[,]\ncaused ... [the] illegal deprivation of [his] liberty[.]” (App. at\n265 ¶ 48).\n\n As a final example, the consent decree says that the\nDepartment must “conduct integrity audits and compliance\nreviews to identify and investigate all officers who have\nengaged in misconduct including unlawful ... searches[] and\nseizures[.]” (App. at 192). The need for such audits and\nreviews lends plausibility to Roman’s allegation that the “City\nhad a custom and practice of inadequately investigating ...\ncitizens’ complaints regarding illegal search and seizure[.]”\n(App. at 272 ¶ 84).\n\n Thus, looking only at the amended complaint together\nwith the consent decree, and giving Roman the benefit of all\nfavorable inferences, as we must at this stage, there is a\nsufficient basis to say that Roman has stated plausible claims\nfor municipal liability under 42 U.S.C. § 1983. Dismissal of\nthose claims was therefore an error.\n\n\n\n\n 2", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362697/", "author_raw": "JORDAN, Circuit Judge, concurring"}, {"author": "HARDIMAN, Circuit Judge, concurring", "type": "concurrence", "text": "HARDIMAN, Circuit Judge, concurring in part and dissenting\nin part.\n\n The District Court dismissed Roman’s case after giving\nhim two opportunities to state a claim upon which relief may\nbe granted and after reconsidering its order of dismissal. Based\non the record presented to it, the District Court’s decision was\ncorrect and should be affirmed as to all but one of Roman’s\nclaims (the municipal liability claim for failure to train,\nsupervise, or discipline).\n\n The Majority vacates part of the District Court’s\njudgment by reciting facts found nowhere in Roman’s\namended complaint and by adding facts of its own creation that\nwere neither pleaded nor argued to the District Court with\nsufficient specificity. The Majority’s deviation from standard\ncivil practice and procedure compels this partial dissent.\n\n I\n\n This dissent results principally from a disagreement\nwith my colleagues about which facts were properly before the\nDistrict Court. First, the Majority proffers a narrative that\nRoman never gave the District Court and which has no\nrelevance to the claims it revives. This Court need not (and\nshould not) recite these “facts” and “background” as true.\nSecond, Roman did not sufficiently plead a municipal liability\nclaim based on Newark’s alleged pattern or practice of Fourth\nAmendment violations. If the facts as pleaded (or subject to\njudicial notice) were as the Majority recites them, I would\nagree that Roman stated a claim for relief. But since the actual\nfacts before the District Court were quite different from those\nenunciated by the Majority, the District Court did not err by\ndismissing this claim.\n\n\n\n\n 1\n\n Despite these disagreements with my colleagues, I\nagree with them that Roman’s amended complaint sufficiently\nstated a municipal liability claim for failure to train, supervise,\nor discipline. Yet I cannot agree with their reasoning in toto\nbecause we should not extrapolate—and the District Court did\nnot err by declining to extrapolate—from extraneous\ndocuments (like the consent decree Roman never provided nor\ncited to the District Court) to reach that conclusion. This single\nclaim should be resuscitated, but only based on the face of the\namended complaint.\n\n A\n\n The Majority purports to recount the facts of this case\n“as set out in the amended complaint and the transcript of the\n[state court] suppression hearing.” Maj. Op. 4 n.1. Yet precious\nfew of those facts were actually pleaded, primarily because the\nstate court transcript was not proffered to the District Court by\nRoman. Moreover, the Majority’s narrative of Roman’s\nalleged mistreatment has effectively no bearing on the\nmunicipal liability claims it revives.\n\n The lion’s share of the troubling facts recited by the\nMajority were taken from sources other than Roman’s\namended complaint. Those sources—including the state-court\nproceedings and subsequent briefs—paint a picture the District\nCourt never observed while considering the motion to dismiss.\nIn truth, the amended complaint says nothing about how the\ninvestigation began, or the surveillance of Roman’s apartment,\nor the initial interaction between police and Melissa Isaksem,\nor the officers’ use of Isaksem as a decoy to gain entry into the\napartment, or the fact that drugs were seized from a common\narea, or the expletives and threats that specific officers yelled\nat both Roman and his father, or Officer Mendes’s use of\n\n\n\n\n 2\n\nphysical force. Unlike those graphic and specific facts the\nMajority extracts, the amended complaint is replete with\nconclusory and generalized assertions. See App. 261–63.\n\n Here are some examples of the Majority’s approach:\nInstead of averring that Officer Mendes flipped Roman on his\nstomach and put a knee in Roman’s neck, Maj. Op. 5, the\namended complaint merely states that “[t]he Defendant\nOfficers and Defendant John Does 1–20 (fictitious names)\nillegally assaulted the Plaintiff, throwing him against a wall\nand handcuffing him,” App. 262. And rather than recounting a\ndetailed plan to initiate an illegal search that included using an\nunwitting friend as a decoy, Maj. Op. 5, the amended\ncomplaint states only that “‘Defendant Officers’ . . . and\nDefendant John Does 1–20 (fictitious names), after having the\nopportunity to observe that the Plaintiff was a person of Latino\ndescent, initiated an illegal search and seizure of the Plaintiff’s\nresidence,” App. 261.\n\n Now on appeal, for the first time Roman cites facts\nestablishing how the police gained entry into the apartment, the\nthreatening words they spoke, and the actions of Officer\nMendes. Roman Br. 10–12. We should not endorse this\nunpleaded narrative, nor suggest the District Court erred by\nfailing to manufacture it in the first place.\n\n B\n\n The Majority concludes that Roman’s amended\ncomplaint (supplemented by the consent decree, a news article,\nand a press release) contains enough facts to make plausible\nhis claims that his injuries were proximately caused by\nNewark’s: (1) pattern or practice of constitutional violations in\nthe area of arrest practices; and (2) failure to adequately train,\n\n\n\n\n 3\n\nsupervise, or discipline its officers. Maj. Op. 15–16. The first\nconclusion is unwarranted. And while the second conclusion is\ncorrect, the Majority still errs in its reliance on a document\nRoman never cited and inferential leaps that Roman’s\npleadings themselves do not admit.\n\n 1\n\n On its face, the amended complaint contains very few\nfacts related to Roman’s arrest or Newark’s alleged pattern or\npractice of rights violations, and what it does contain amount\nonly to conclusory statements. See Ashcroft v. Iqbal, 556 U.S.\n662, 678 (2009) (noting that a court’s duty to “accept as true\nall of the allegations contained in a complaint is inapplicable\nto legal conclusions,” and that “[t]hreadbare recitals of the\nelements of a cause of action, supported by mere conclusory\nstatements, do not suffice”). When we excise from the\nMajority’s narrative all facts that were neither pleaded nor\npresented to the District Court and the complaints’ legal\nconclusions, it becomes clear that the District Court did not err\nby twice deeming Roman’s complaint deficient regarding a\npattern or practice of rights violations.\n\n This Court should not fault the trial judge for failing to\ntake cognizance of facts or arguments never presented to her,\nespecially here, where Roman chose not to include in his\namended pleading facts that could have been gleaned from\nDefendants’ first motion to dismiss and the consent decree\nattached to it. See Snyder v. Pascack Valley Hosp., 303 F.3d\n271, 276 (3d Cir. 2002) (noting that “[a]n amended complaint\nsupercedes the original version in providing the blueprint for\nthe future course of a lawsuit”).\n\n\n\n\n 4\n\n The Majority primarily (and incorrectly) relies on that\nconsent decree to buttress Roman’s pattern-or-practice claim.\nAlthough the District Court could take notice of the consent\ndecree’s existence, it’s quite another matter to hold it\naccountable for not accepting as true everything its contents\ncould possibly imply—especially when Roman neither\npleaded nor relied upon the decree’s contents.\n\n What is crucial is whether Roman’s complaint was\n“based” on the consent decree.1 In re Burlington Coat Factory\nSec. Litig., 114 F.3d 1410, 1426 (3d Cir. 1997). Only to the\nextent the Majority refashions Roman’s pattern-or-practice\nclaim such that it is now based on implausible inferences from\nthe consent decree is it “based on” the consent decree. For\nRoman did not explicitly reference, quote, or rely on the\ndocument in his amended complaint—even after the City\nprovided it. The amended complaint merely references the\ndecree’s announcement by the Department of Justice months\nafter his arrest.2 See App. 270 ¶ 68. The District Court, though\nit must draw all reasonable inferences in Roman’s favor, had\nno obligation to abstract facts or inferences or claims Roman\n\n\n 1\n His appellate briefs’ references to the document are\nnot determinative, no matter how many times they cite the\ndecree.\n 2\n This timing further complicates the Majority’s reliance\non the consent decree. The decree’s announcement months\nafter Roman’s arrest requires yet another “infer[ence] that the\nproblems that led to it were occurring during the time of his\nallegations and for some time before that.” Maj. Op. 15. It also\nrequires an inference that all of the City’s “corrective measures\npostdated the arrest.” Id. at 21 n.8.\n\n\n\n\n 5\n\nchose not to plead.3 Instead, he was the master of his own\ncomplaint. See Judon v. Travelers Prop. Cas. Co. of Am., 773\nF.3d 495, 505 (3d Cir. 2014).\n\n And even if we accept as true all the consent decree\ncontains, Roman’s arrest was not plausibly part of the pattern\nor practice of rights violations the decree addressed, except\nperhaps at the highest level of generality.4 For starters, the\ndecree addressed police stops and arrests of pedestrians or the\noccupants of vehicles. See App. 79 (detailing the pattern or\npractice investigated by the DOJ that led to the consent\n\n 3\n The document’s undisputed authenticity as a\ngovernment document says nothing about the reasonableness\nof the inferences the Majority abstracts from the consent\ndecree. Nor does it speak to the contents’ relevance to Roman’s\ncase. Such authenticity merely provides one reason for\njudicially noticing the decree’s existence and eliminates one\npotential reason for not relying on it. It does not follow that it\nis “especially important” for district courts to rely on and\nextrapolate from such documents. Maj. Op. 11.\n 4\n The consent decree itself admits no specific pattern or\npractice of rights violations. Although it followed a DOJ report\nthat “revealed a pattern or practice of constitutional violations\nin areas including stop and arrest practices, use of force, and\ntheft by officers,” that report was never provided to the District\nCourt. App. 137; see Maj. Op. 11–12. Instead, the consent\ndecree only outlines measures Newark agreed to take—not any\npattern or practice of rights violations, let alone one that\nplausibly caused Roman’s injuries. In fact, that report actually\ndemonstrates that even the pattern or practice that led to the\nconsent decree could not plausibly have caused Roman’s\ninjuries.\n\n\n\n\n 6\n\ndecree’s adoption). The consent decree says nothing about\narrests or searches without consent that occur at residences,\nwhich is what Roman complains of in this case.\n\n Another problem that distinguishes Roman’s complaint\nfrom the problems that led to the consent decree is the fact that\nthe decree addressed police practices that disparately impacted\nthe black community. See App. 93–98 (detailing same).5 But\nthat racial disparity did not apply to Roman, who was Hispanic.\nSee App. 261 ¶ 16. While the consent decree may have been\n“meant to protect all Newark residents,” Maj. Op. 19, the point\nremains that the pattern or practice giving rise to it was not one\nthat plausibly caused Roman’s injuries.\n\n Finally, the consent decree addressed erroneous\nnarcotics arrest reports where “individuals often were\npurportedly seated in cars holding clear plastic baggies in front\nof them or on their laps and officers could ‘immediately’ see\nthe contraband, even though the report indicated that the\nsubject’s back was to an officer, or that the officer had not yet\napproached the car.” App. 92 (detailing the pattern or practice\ninvestigated by the DOJ that led to the consent decree’s\nadoption). Wholly unrelated to those erroneous reports, Roman\nalleges that officers exhaustively searched the apartment\n\n 5\n In his motion for reconsideration, Roman claimed his\nmunicipal liability argument was based on “the City’s\nwidespread and systemic misuse of police powers to treat\nmembers of a protected racial class different from those of\nwhite citizens.” ECF 43-3 at 8. Unlike the pattern or practice\nof Fourth Amendment violations the Majority now remands,\nhe argued “racial profiling, racial discrimination, or other\nwidespread discrimination of minorities” gave rise to his\nmunicipal liability cause of action. Id.\n\n\n\n\n 7\n\nwithout a warrant, and he is silent as to where and when the\nofficers found the drugs. See App. 30–31, 262–63.\n\n In sum, Roman’s arrest was too dissimilar from the\npattern or practice addressed by the consent decree to plausibly\nallege proximate causation for his injuries. While clear that the\nDOJ did not enter into the consent decree “because it was\nimpressed with Newark’s policing practices,” Maj. Op. 20, it\nwas not the District Court’s duty to imagine all possible\ninferences from the document. It was Roman’s duty to plead\nthem. See Judon, 773 F.3d at 505. For the Majority to conclude\notherwise, it must derive that pattern or practice from sources\nnot before the District Court and define it at the highest level\nof generality: Fourth Amendment violations writ large. In other\nwords, my colleagues conclude that because Newark police\nallegedly engaged in a pattern or practice of Fourth\nAmendment violations of type x, it follows that they plausibly\ncommitted this violation of type y—all based on a document\nthey cannot claim the District Court must have considered. The\nDistrict Court did not err in failing to perform the Majority’s\ninferential leaps to reach that conclusion based on a document\nit need not have considered in the first place. It properly\ndismissed this claim rather than indulge such speculation. See\nIqbal, 556 U.S. at 679–80.\n\n With or without these sources, the amended complaint’s\nbare legal conclusions need not be accepted as true. Id. at 678.\nSo Roman failed to state a pattern-or-practice claim on which\nrelief could be granted.\n\n\n\n\n 8\n\n 2\n\n Roman’s failure-to-train, failure-to-supervise, and\nfailure-to-discipline claim was sufficiently pleaded. But the\nMajority’s method for arriving at this conclusion suffers from\nsimilar deficiencies to its pattern-or-practice reasoning. The\nMajority’s reliance on the consent decree is again misplaced\nfor the reasons discussed above.6 And even if such reliance\nwere appropriate, the consent decree does not make Roman’s\nclaim plausible.\n\n Roman’s arrest was not plausibly caused by the failures\nto train, supervise, or discipline Newark officers the Majority\ncites in the consent decree because no such failures appear in\nthe document. The Majority claims “the consent decree\nindicates Newark police officers were not trained on ‘the\nrequirements of [the] Fourth Amendment and related law.’”\nMaj. Op. 16. And “per the decree” the City’s “training did not\ncover the basics of the Fourth Amendment.” Id. at 17. It does\nno such thing. Rather, it indicates that Newark agreed to\n\n 6\n The Majority’s reliance on the news article and press\nrelease hyperlinked in Roman’s complaints is likewise\ninappropriate. The news article’s identification of one\nofficer—who may or may not have been involved in Roman’s\narrest—who told a reporter he “think[s]” he did not receive\ntraining for 20 years is not enough to subject the City to\nliability for failure to adequately train its entire police force.\nApp. 134 (emphasis added). This demonstrates no custom; nor\ndoes it plausibly demonstrate the police academy training all\nofficers receive was constitutionally inadequate without more\nfollow-up. Nor does the article address supervision or\ndiscipline. Similarly, the press release addresses none of the\nthree.\n\n\n\n\n 9\n\nimplement additional training on “the requirements of [the]\nFourth Amendment and related law” without any detail as to\nthe status quo it addressed. App. 160. While it’s safe to say that\nthe DOJ did not endorse that status quo, the difference between\nagreeing to train more and agreeing that prior training was\nconstitutionally inadequate regarding the Fourth Amendment\nwrit large should be clear. And, as discussed above, the consent\ndecree arose from a host of policing practices unlike those\nRoman alleged (except at the highest level of generality).\nNewark could not plausibly have agreed to the extraordinary\nliability that would come from admitting that its police training\nviolated the Fourth Amendment in every instance, or in every\ninstance possibly connected to Roman’s arrest. Indeed, the\ndecree says no such thing about any instance.\n\n The consent decree is even thinner as it relates to\nsupervisory and disciplinary issues. From the City’s agreement\nto adhere to certain review processes and disciplinary measures\nregarding unlawful searches and false arrests, the Majority\nperceives a “deliberate indifference to Roman’s Fourth\nAmendment rights.” Maj. Op. 17 (internal quotations and\ncitation omitted). That does not follow. The decree does not\ndescribe or admit any processes or measures already in place\nor any existing pattern of unlawful searches or false arrests.\n\n Instead, Roman’s amended complaint directly alleged\ntraining, supervision, and discipline problems with adequate\nspecificity to survive a motion to dismiss. See, e.g., App. 270–\n72 ¶¶ 68, 70, 71, 78, 80, 82; see also Doe v. Luzerne Cty., 660\nF.3d 169, 179–80 (3d Cir. 2011) (quoting Carter v. City of\nPhila., 181 F.3d 339, 357 (3d Cir.1999)) (detailing standard at\nsummary judgment for failure-to-train claim). The Majority’s\nimproper reliance on the consent decree and inferential leaps\n\n\n\n\n 10\n\nfrom that and other sources outside the amended complaint are,\nin my view, erroneous and unnecessary.\n\n * * *\n\n As we have noted many times before, we are a court of\nreview, not a court of first view. See, e.g., In Re: J & S Props.,\nLLC, 872 F.3d 138, 148 (3d Cir. 2017). Our review is based on\nthe record as presented by counsel in our adversary system. We\nshould not fault the District Court for failing to manufacture\nfacts and craft arguments that Roman neglected to plead. By\nconjuring its own facts repackaged as if pleaded in the\namended complaint, the Majority imposes a new duty upon\ndistrict judges within the Third Circuit. It does so without\nciting precedent for the proposition that a district court must\nconsider facts and arguments never pleaded or argued by the\nplaintiff. I cannot subscribe to this new rule.\n\n This appeal implicates a fundamental legal principle:\nthe plaintiff is the master of his complaint. Because of that\ntime-honored principle, Roman’s failure to state a policy-or-\npractice claim upon which relief may be granted requires the\nharsh sanction of dismissal. After his initial complaint was\nfound inadequate, Roman failed to file an amended complaint\nthat cured the deficiencies identified by the District Court.\nEven assuming Roman might have had a legitimate claim, it\nwould have been improper for the District Court to try to make\nRoman’s case for him. And it’s especially inappropriate for us\nto overrule the decision of a district judge because of a failure\nto apprehend facts and arguments never presented to her. I\nrespectfully dissent.\n\n\n\n\n 11", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362697/", "author_raw": "HARDIMAN, Circuit Judge, concurring"}]}
JORDAN
HARDIMAN
JORDAN
1
{}
6
0
0
4
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4585444/
Published
1
1
1
1
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: *The ESTATE OF Adriano ROMAN, Jr., Appellant v. CITY OF NEWARK; City of Newark Police Department; Anthony Campos, Chief of Police; Rodger C. Mendes; Albano Ferreira ; Onofre H. Cabezas; Joseph Cueto; FNU Ressureicao; FNU Golpe; Joyce Hill, Individually and in Their Capacity as Police Officers; John Does 1-20, as Fictitious Names for Presently Unknown Agents Member Commissioners and Chiefs *(Amended Pursuant to Clerk's Order Dated 1/25/2018)\nCourt: U.S. Court of Appeals for the Third Circuit\nDate decided: 2019-01-29\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPRECEDENTIAL\n\n UNITED STATES COURT OF APPEALS\n FOR THE THIRD CIRCUIT\n ________________\n No. 17-2302\n ________________\n\n *THE ESTATE OF ADRIANO ROMAN, JR.,\n Appellant\n\n v.\n\n CITY OF NEWARK;\n CITY OF NEWARK POLICE DEPARTMENT;\n ANTHONY CAMPOS, Chief of Police;\n RODGER C. MENDES;\n ALBANO FERREIRA; ONOFRE H. CABEZAS;\n JOSEPH CUETO;\n FNU RESSUREICAO; FNU GOLPE; JOYCE HILL,\n Individually and in their capacity as police officers;\nJOHN DOES 1-20, as fictitious names for presently unknown\n agents member commissioners and chiefs\n\n *(Amended pursuant to Clerk’s Order dated 1/25/18)\n ________________\n Appeal from the United States District Court\n for the District of New Jersey\n (D.C. Civil Action No. 2-16-cv-01110)\n District Judge: Honorable Susan D. Wigenton\n ________________\n\n Argued June 12, 2018\n\n Before: AMBRO, JORDAN, and\n HARDIMAN, Circuit Judges\n\n (Opinion filed: January 29, 2019)\n\nJustin D. Santagata (Argued)\nKaufman Semeraro & Leibman\nTwo Executive Drive, Suite 530\nFort Lee, NJ 07024\n\n Counsel for Appellant\n\nKenyatta K. Stewart, Acting Corporation Counsel\nWilson D. Antoine (Argued)\nCity of Newark–Department of Law\n920 Broad Street, Room 316\nNewark, NJ 07102\n\n Counsel for Appellees\n\n ________________\n OPINION OF THE COURT\n ________________\n\nAMBRO, Circuit Judge\n\n Newark police officers forcibly entered and searched\nthe apartment of Adriano Roman’s girlfriend. App. at 386,\n391, 459, 486. They arrested Roman, who was present in the\napartment, after they found drugs in a common area that was\nshared by multiple tenants. Id. at 399, 479. Though he was\nimprisoned for over six months and indicted for various drug\n\n\n\n\n 2\n\noffenses, the New Jersey Superior Court found the search to\nbe unlawful and the charges were dropped.\n\n Roman now brings claims against the City of Newark\n(which includes its Police Department) and various police\nofficers under 42 U.S.C. § 1983 (which gives a federal\nremedy against state officials who, acting under color of state\nlaw, deprive “any citizen of the United States . . . of any\nrights, privileges, or immunities secured by the [U.S.]\nConstitution and laws”) and New Jersey tort law. He alleges\nthe City had a pattern or practice of constitutional violations\nand failed to train, supervise, and discipline its officers. He\nalso pleads an unlawful search claim against the officers and\ncontends they are liable for false imprisonment and malicious\nprosecution. The District Court dismissed all of the claims\nbecause they were inadequately pled. It also held the City did\nnot have an ongoing practice of unconstitutional searches and\narrests.\n While most of Roman’s claims do not withstand\ndismissal, his § 1983 claims against the City do. He has\nadequately alleged that its Police Department had a custom of\nwarrantless searches and false arrests. He also sufficiently\npled that the Department failed to train, supervise, and\ndiscipline its officers, specifically with respect to “the\nrequirements of [the] Fourth Amendment and related law.”\nApp. at 160. Because Roman has stated a plausible claim\nagainst the City, we vacate and remand the District Court’s\nholding on municipal liability. We affirm in all other\nrespects.\n\n\n\n\n 3\n\nI. Background1\n On May 2, 2014, Roman and his girlfriend Tiffany\nReyes were watching a movie in her apartment’s bedroom.\nApp. at 386, 389, 395. Unbeknownst to them, four Newark\npolice officers had set up surveillance outside of her building\nbecause of complaints about narcotics activity. Id. at 338.\nThe officers heard an argument between a man and a woman,\nid. at 340-42, and decided to enter Reyes’ apartment without\na warrant, id. at 491.\n After they stepped inside the building, they discovered\nthat the front door of the apartment was locked. They also\n\n 1\n As noted below, we must, while reviewing a ruling\non a motion to dismiss, view the facts in the light most\nfavorable to the plaintiff. Accordingly, without judging the\nfacts, we recount them as set out in the amended complaint\nand the transcript of the suppression hearing referred to\nbelow. Although Roman did not attach the transcript to the\namended complaint, the Defendants included it in their\nmotion to dismiss and told the District Court it was “capable\nof judicial notice” and “integral to the [c]omplaint.” App. at\n130. Thus we consider it at this stage.\n\n In any event, both the amended complaint and\ntranscript note that the officers forcibly entered the apartment,\nassaulted Roman, and falsely charged him with possession of\na controlled substance. See Am. Compl. ¶¶ 17, 22, 28. Any\nminor differences in the two documents do not affect our\nanalysis of his municipal liability claim. See infra Section\nIII.A (explaining that the events leading up to Roman’s\nsearch and arrest are not relevant to the merits of his\nmunicipal liability claim).\n\n\n\n\n 4\n\nnoticed Melissa Isaksem, Reyes’ friend, walking inside the\nbuilding. Id. at 417-20. They stopped and questioned her.\nId. at 417, 419. When she told them she was visiting Reyes,\nid. at 419, they ordered her to knock on the apartment door\nfor them and threatened to arrest her if she did not comply, id.\nat 419-20. Isaksem led them to the apartment and stood\ndirectly in front of the peephole. Id. at 421. The police stood\nto her left, presumably out of the peephole’s range. Id. An\nofficer knocked on her behalf. Id. Reyes asked who was at\nthe door, and Isaksem announced her presence. Id.\n Reyes opened the door, expecting to see only Isaksem.\nId. at 386, 400, 501. Instead, several officers rushed inside.\nId. at 387, 400, 501. They handcuffed Roman, Reyes, and\nIsaksem, then demanded Roman “call someone to bring drugs\nto the [apartment].” Am. Compl. ¶ 30 (internal quotation\nmarks omitted). If he did, they assured him they would\n“‘make a deal’ and ‘let him go.’” Id. Roman refused the\nofficers’ demands, id. ¶ 33, and the police searched the\napartment. Eventually they found drugs in a common-area\nspace that was shared by multiple tenants and located in the\nback of the apartment. App. at 399, 479. After seizing the\ncontraband, they yelled, “[W]e got you, motherfucker[;] . . .\nyou’re fucked now.” Id. at 427. Officer Rodger Mendes\nwalked back to Roman, “flipped him . . . on[]to his stomach\n. . . , put his knee in his neck[,] and . . . said he was going to\nget raped [in prison].” Id. at 428. Another officer informed\nRoman’s father, who lived next door and observed parts of\nthe search, that his son “would go away for a long time.” Id.\nat 454.\n Roman was arrested and imprisoned on the same night.\nThe officers filed a criminal complaint against him for\npossession of, as well as intent to distribute, heroin and\ncocaine. A New Jersey grand jury returned a six-count\nindictment against him for the same offenses.\n\n\n\n\n 5\n\n In response, Roman moved to suppress the evidence\nseized from the apartment. He argued the search was invalid\nunder the Fourth Amendment because the contraband was not\nin plain view and thus a warrant was needed. The New Jersey\nSuperior Court agreed. It concluded the plain-view exception\ndid not apply and suppressed the contraband.\n The State of New Jersey did not appeal the ruling and\ninstead moved to dismiss the case. The Superior Court\ngranted its motion in December 2014 and issued a final\njudgment of dismissal. Roman was released from prison\nduring the same month.\n Approximately a year later, Roman brought § 1983\nand state-law tort claims against the City of Newark and\nvarious police officers (for simplicity, the City and the\nofficers are jointly referred to as the “Defendants”). Among\nother things, he alleged the City had a custom or policy of\nunconstitutional searches, inadequate training, and poor\nsupervision and discipline.2 He also claimed the officers\nunlawfully searched his apartment and were liable for the\ntorts of unlawful imprisonment and malicious prosecution.3\n\n\n 2\n Roman’s amended complaint also included\nallegations of discrimination of national origin in violation of\n42 U.S.C. § 1983, civil conspiracy in violation of 42 U.S.C.\n§ 1985, conspiracy to commit an unlawful search in violation\nof the New Jersey Constitution and 42 U.S.C. § 1985, and\nconspiracy to commit unlawful imprisonment in violation of\n42 U.S.C. § 1985. We do not address these claims, as Roman\ndoes not press them on appeal.\n 3\n We construe Roman’s claim for unlawful\nimprisonment as a claim for false imprisonment. Although\n\n\n\n\n 6\n\n The Defendants responded with a motion to dismiss.\nThe District Court sided with them, dismissing the complaint\nin its entirety. It first addressed Roman’s claim against the\nCity and concluded the complaint “fail[ed] to plead . . . a\ncustom or policy” of unlawful searches and a failure to train\nor supervise officers. Roman v. City of Newark, Civil Action\nNo. 16-1110-SDW-LDW, 2017 WL 436251, at *4 (D.N.J.\nJan. 30, 2017). Although the complaint alleged “a pattern or\npractice of constitutional violations in areas including stop[]\nand arrest practices, use of force, and theft by officers,” the\nCourt did not consider that sufficient to state a claim. Id.\n(internal quotation marks omitted) (quoting Compl. ¶ 59).\nInstead, it viewed those practices as predating Roman’s arrest\nand observed that “the imposition of a [f]ederal [m]onitor\nindicate[d] [the City’s] attempts to change any wrongful\npolicies or practices.” Id.\n The Court also held the unlawful search claim was\ninadequately pled, as Roman did not “explain which\n[Defendant(s)] committed the allegedly wrongful acts” during\nthe search and arrest. Id. Turning to the false imprisonment\nand malicious prosecution claims, it construed them as state-\nlaw claims and noted that plaintiffs must comply with the\n\nNew Jersey lacks a cause of action for “unlawful\nimprisonment,” it has codified the elements of a false\nimprisonment claim. See N.J. Stat. Ann. § 2C:13-3; Mallery\nv. Erie R. Co., 92 A. 371, 371 (N.J. 1914) (“This appeal\nbrings up a judgment recovered by the respondent in an\naction for false imprisonment. The declaration described\nthe unlawful imprisonment. . . .”); see also 8 American Law\nof Torts § 27:1 (“False imprisonment, sometimes called\ncriminal restraint or unlawful imprisonment, is committed\nwhen a defendant so restrains another person as to interfere\nsubstantially with his liberty.”).\n\n\n\n\n 7\n\nNew Jersey Tort Claims Act before bringing them against\npublic entities. See N.J. Stat. Ann. § 59:8-1 et seq. Because\nthe “[c]omplaint nowhere allege[d]” Roman complied with\nthe Act’s procedures, the Court dismissed those claims as\nwell. Roman, 2017 WL 436251, at *6.\n\n The Court’s dismissal was without prejudice, and it\ngranted Roman leave to amend. He did so by omitting his\ntort claims and retaining his other allegations in almost\nidentical form. The Court dismissed his amended complaint\nand reaffirmed its ruling on reconsideration. This appeal\nfollowed.4\nII. Jurisdiction and Standard of Review\n The District Court had federal-question and\nsupplemental jurisdiction per 28 U.S.C. §§ 1331 and 1367(a),\nrespectively, and we have jurisdiction over its final orders\nunder 28 U.S.C. § 1291.\n We review de novo its dismissal of a complaint under\nFederal Rule of Civil Procedure 12(b)(6). See Phillips v.\nCounty of Allegheny, 515 F.3d 224, 230 (3d Cir. 2008).\nWhen conducting our review, “we accept all factual\nallegations as true [and] construe the complaint in the light\nmost favorable to the plaintiff.” Warren Gen. Hosp. v.\nAmgen Inc., 643 F.3d 77, 84 (3d Cir. 2011) (internal\nquotation marks omitted). However, “we are not compelled\nto accept unsupported conclusions and unwarranted\ninferences . . . or a legal conclusion couched as a factual\nallegation[.]” Baraka v. McGreevey, 481 F.3d 187, 195 (3d\n\n\n 4\n Roman passed away while this appeal was pending,\nand his estate brings the claims on his behalf. We do not\ndistinguish between Roman and his estate in this opinion.\n\n\n\n\n 8\n\nCir. 2007) (internal quotation marks omitted) (internal\ncitation omitted).\n\nIII. Discussion\n A. Roman sufficiently pled a municipal liability\n claim against Newark.\n\n As noted, Roman alleges the City is liable under\n§ 1983 because it “engaged in a pattern or practice of\nconstitutional violations,” “failed to properly train and/or\nsupervise” its police force, and “failed to properly and\nadequately control and discipline” its police officers.5 Am.\nCompl. ¶¶ 68, 73-74. Before discussing the merits of his\nclaims, Roman directs our attention to the types of documents\nwe may consider on a motion to dismiss. He contends we\nmay review three sources that were provided to the District\nCourt: an article published in the Newark Star Ledger (the\n“Star Ledger article”), a press release issued by the U.S.\nAttorney’s Office (the “press release”), and a consent decree\nbetween the United States and the City of Newark (the\n“consent decree”). The Star Ledger article and press release\nwere referenced in the amended complaint, see id. ¶¶ 68-69\n(including hyperlinks to both), but the consent decree was\nattached to the Defendants’ motion to dismiss, see App. at\n129. Roman also asks us to look at one other document: the\nDepartment of Justice’s Report on the investigation of the\nNewark Police Department (the “DOJ Report”). Although he\n\n 5\n Roman brings his municipal liability claims under\n§ 1983 and the New Jersey Civil Rights Act, N.J. Stat. Ann.\n§ 10:6-1 et seq. Because the latter “is interpreted analogously\nto . . . § 1983,” we consider his New Jersey Civil Rights Act\nclaims along with his § 1983 claim. Coles v. Carlini, 162 F.\nSupp. 3d 380, 404 (D.N.J. 2015).\n\n\n\n\n 9\n\nacknowledges the DOJ Report was never provided to the\nDistrict Court, he now claims it is integral to the pleadings.\n\n Though the Defendants dispute that we may consider\nthe DOJ Report, they add that we also cannot consider the\nconsent decree because “no relevant provisions of [it] . . .\nwere ever cited . . . to the District Court” and it is\ninadmissible settlement material. Defendants’ Br. at 42.\nThey assert as well, without any citation to the record, that\nRoman may not rely on the decree because he asked the\nDistrict Court to confine its analysis to the pleadings.\n We disagree with the Defendants’ view of the consent\ndecree. Although we examine the “complaint, exhibits\nattached to the complaint, [and] matters of public record,”\nMayer v. Belichick, 605 F.3d 223, 230 (3d Cir. 2010), we can\nalso consider documents “that a defendant attaches as an\nexhibit to a motion to dismiss,” Pension Benefits Guar. Corp.\nv. White Consol. Indus., Inc., 998 F.2d 1192, 1196 (3d Cir.\n1993), if they are “undisputedly authentic” and “the\n[plaintiff’s] claims are based [on them],” Mayer, 605 F.3d at\n230. That holding extends to settlement material because\nplaintiffs “need not provide admissible proof at th[e] [motion-\nto-dismiss] stage.” In re OSG Sec. Litig., 12 F. Supp. 3d 619,\n622 (S.D.N.Y. 2014); see also In re MyFord Touch Consumer\nLitig., 46 F. Supp. 3d 936, 961 n.5 (N.D. Cal. 2014) (same).\nMoreover, the Supreme Court has been clear about the scope\nof our review, stating we “must consider the complaint in its\nentirety, as well as other sources [we] ordinarily examine\nwhen ruling on . . . motions to dismiss, in particular,\ndocuments incorporated into the complaint by reference, and\nmatters of which a court may take judicial notice.” Tellabs,\nInc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 322 (2007)\n(emphasis added).\n\n\n\n\n 10\n\n Here, although the consent decree was not attached to\nRoman’s amended complaint, we are free to review its\ncontents for three reasons.6 First, the Defendants attached the\ndecree to their motion to dismiss and affirmed that it is\n“capable of judicial notice” as an indisputably authentic\ngovernment document. App. at 129. Second, contrary to the\ndissent’s assertion, the Defendants themselves argued (and\ncorrectly) before the District Court that Roman’s claims were\nbased on the consent decree. Compare Dissenting Op. at 5\n(“What is crucial is whether Roman’s complaint was ‘based’\non the consent decree.”), with App. at 129 (filing from\nDefendants characterizing the consent decree as “integral to\nthe Complaint”). Third, the amended complaint cited, and the\nDistrict Court discussed, the DOJ investigation and federal\nmonitor that eventually led to the consent decree. See\nRoman, 2017 WL 436251, at *4; see also Am. Compl. ¶¶ 68-\n71. Thus it was especially important for the Court to have\nconsidered the decree as well, given that it provides essential\ncontext to Roman’s claims. That it did not was an abuse of\ndiscretion.\n\n That said, we may not consider the DOJ Report at this\nstage because it was not provided to the District Court in the\nfirst instance by any party. Nor is it apparent that the Court\nconsidered it sua sponte. See United States ex rel. Wilkins v.\n\n 6\n Though the Defendants and our dissenting colleague\ndo not challenge the Star Ledger article or the press release,\nwe note that we consider them because they are referenced in\nthe amended complaint. See Tellabs, 551 U.S. at 322. As\nJudge Jordan explains in his concurrence, however, Roman\ndoes not need either document or the suppression hearing\ntranscript to state a municipal liability claim; the consent\ndecree gives his allegations enough plausibility to survive\ndismissal.\n\n\n\n\n 11\n\nUnited Health Grp., Inc., 659 F.3d 295, 302 (3d Cir. 2011)\n(“Though we do not doubt the authenticity of\nthese documents, nevertheless we will not consider them\nbecause the parties did not present them to the District Court\nand we do not find any indication in the record that the Court\nconsidered them on its own initiative.”). Hence it cannot\ncarry any weight in our analysis.\n Turning to the amended complaint, Roman claims the\nCity is liable for his unlawful search because it “failed to train\nits officers in the use of search and seizure techniques,\nprobable cause, and/or methods to properly obtain a search\nwarrant.” Am. Compl. ¶ 95. He alleges the Newark Police\nDepartment “engaged in a pattern or practice of constitutional\nviolations” and asserts the Department of Justice appointed a\nfederal monitor to oversee the reforms to which the City\nconsented. Id. ¶ 68. His allegations also touch on the City’s\nfailure to “control and discipline” its police force, id. ¶ 74,\nand failure to “investigate . . . instances of . . . police\nmisconduct,” id. ¶ 81. He characterizes the City’s practices in\nthese areas as “tantamount to a[n] [unconstitutional] custom\nand/or policy,” id. ¶ 82, thus indicating its “deliberate\nindifference to [its citizens’ constitutional] rights,” id. ¶ 83.\n The Defendants respond that Roman has failed to\nallege a municipal liability claim, as no part of the Star\nLedger article, press release, or consent decree references the\ntypes of constitutional violations pled in the amended\ncomplaint. They also contend the City had no notice “of any\npattern of constitutional violations with respect to forced\nentry and searches of homes.” Defendants’ Br. at 50.\n To plead a municipal liability claim, a plaintiff must\nallege that “a [local] government’s policy or custom . . .\ninflict[ed] the injury” in question. Monell v. Dep’t of Soc.\nServs., 436 U.S. 658, 694 (1978). “Policy is made when a\n\n\n\n\n 12\n\ndecisionmaker possess[ing] final authority to establish\nmunicipal policy with respect to the action issues an official\nproclamation, policy, or edict.” Andrews v. City of\nPhiladelphia, 895 F.2d 1469, 1480 (3d Cir. 1990) (alteration\nin original) (internal quotation marks omitted). “Custom, on\nthe other hand, can be proven by showing that a given course\nof conduct, although not specifically endorsed or authorized\nby law, is so well-settled and permanent as virtually to\nconstitute law.” Bielevicz v. Dubinon, 915 F.2d 845, 850 (3d\nCir. 1990) (Becker, J.); see also Brown v. Muhlenberg Twp.,\n269 F.3d 205, 215 (3d Cir. 2001) (“A custom . . . must have\nthe force of law by virtue of the persistent practices of state\n[or municipal] officials.” (internal quotation marks omitted)).\n Although a policy or custom is necessary to plead a\nmunicipal claim, it is not sufficient to survive a motion to\ndismiss. A plaintiff must also allege that the policy or custom\nwas the “proximate cause” of his injuries. See Kneipp v.\nTedder, 95 F.3d 1199, 1213 (3d Cir. 1996). He may do so by\ndemonstrating an “affirmative link” between the policy or\ncustom and the particular constitutional violation he alleges.\nBielevicz, 915 F.2d at 850 (internal quotation marks omitted).\nThis is done for a custom if Roman demonstrates that Newark\nhad knowledge of “similar unlawful conduct in the past, . . .\nfailed to take precautions against future violations, and that\n[its] failure, at least in part, led to [his] injury.” Id. at 851.\nDespite these requirements, Roman does not need to identify\na responsible decisionmaker in his pleadings. See id. at 850.\nNor is he required to prove that the custom had the City’s\nformal approval. See Anela v. City of Wildwood, 790 F.2d\n1063, 1067 (3d Cir. 1986).\n The pleading requirements are different for failure-to-\ntrain claims because a plaintiff need not allege an\nunconstitutional policy. See Reitz v. County of Bucks, 125\nF.3d 139, 145 (3d Cir. 1997) (“[I]n the absence of an\n\n\n\n\n 13\n\nunconstitutional policy, a municipality’s failure to properly\ntrain its employees and officers can create an actionable\nviolation . . . under § 1983.”). Instead, he must demonstrate\nthat a city’s failure to train its employees “reflects a deliberate\nor conscious choice.” Brown, 269 F.3d at 215 (internal\nquotation marks omitted). For claims involving police\nofficers, the Supreme Court has held that the failure to train\n“serve[s] as [a] basis for § 1983 liability only where [it] . . .\namounts to deliberate indifference to the rights of persons\nwith whom the police come into contact.” City of Canton v.\nHarris, 489 U.S. 378, 388 (1989) (footnote omitted). A\nplaintiff sufficiently pleads deliberate indifference by\nshowing that “(1) municipal policymakers know that\nemployees will confront a particular situation[,] (2) the\nsituation involves a difficult choice or a history of employees\nmishandling[,] and (3) the wrong choice by an employee will\nfrequently cause deprivation of constitutional rights.” Doe v.\nLuzerne County, 660 F.3d 169, 180 (3d Cir. 2011) (internal\nquotation marks omitted) (quoting Carter v. City of\nPhiladelphia, 181 F.3d 339, 357 (3d Cir. 1999)).\n\n In view of this case law, Roman has not pled a\nmunicipal policy, as his amended complaint fails to refer to\n“an official proclamation, policy, or [an] edict.” Andrews,\n895 F.2d at 1480. However, he has sufficiently alleged a\ncustom of warrantless or nonconsensual searches. He has\nalso adequately pled that the City failed to train, supervise,\nand discipline its police officers.7\n\n\n 7\n We consider allegations of failure to train, supervise,\nand discipline together because they fall under the same\nspecies of municipal liability. See Rosalie Berger Levinson,\nWho Will Supervise the Supervisors? Establishing Liability\nfor Failure to Train, Supervise, or Discipline in a Post-\n\n\n\n\n 14\n\n We start with Roman’s allegations on municipal\ncustom. He asserts the City had “a pattern or practice of\nconstitutional violations in areas including . . . arrest\npractices.” App. at 137. He further contends it had notice of\nthis practice, as it received “complaints against officers\naccused of . . . conducting improper searches and false\narrests.” Id. at 134. The amended complaint, along with the\npress release and Star Ledger article, note that Newark was\nunder the supervision of a federal monitor after Roman’s\narrest. Am. Compl. ¶ 68; App. at 133, 137. According to the\npress release, the monitor would oversee reforms in several\nareas, including searches, arrests, and the intake and\ninvestigation of misconduct complaints. App. at 137.\n The consent decree echoes these points. It covers the\nsame type of conduct Roman alleges, as it “prohibit[s]\nofficers from relying on information known to be materially\nfalse or incorrect to justify a warrantless search . . . [or to]\neffect[] an arrest.” Id. at 158; see also id. at 163 (mandating\nofficers to collect data on consent, the type of search, and “a\nbrief description of the facts creating probable cause”). The\ndecree also requires the Police Department to investigate\npolice misconduct, see generally id. at 184-92, with special\nemphasis on allegations of criminal misconduct, false arrest,\nplanting evidence, and unlawful searches, see id. at 150, 186.\n While the consent decree was not in place during\nRoman’s search and arrest, we may fairly infer that the\nproblems that led to it were occurring during the time of his\nallegations and for some time before that. See id. at 133-34\n(noting the investigation that resulted in the consent decree\nand federal supervision began in May 2011 and ended in July\n2014). With this mind, the decree fortifies Roman’s\n\nIqbal/Connick World, 47 Harv. C.R.-C.L. L. Rev. 273, 280\n(2012).\n\n\n\n\n 15\n\nallegations of unlawful custom because it acknowledges “a\npattern or practice of conduct by the Newark Police\n[Department] that deprives individuals of rights, privileges,\nand immunities secured by the Constitution.” Id. at 144.\nWhen viewed in conjunction with the Star Ledger article, it\nreferences the types of constitutional violations mentioned in\nthe amended complaint: warrantless searches, id. at 134, and\nfalse arrests, id. at 158. These violations were widespread\nand causally linked to Roman’s alleged injury, as the Police\nDepartment was aware of them but “rare[ly] . . . acted” on\ncitizen complaints. Id. at 134 (discussing complaints of\n“improper searches and false arrests”); see also Beck v. City\nof Pittsburgh, 89 F.3d 966, 974 (3d Cir. 1996) (noting the\npolice department’s failure to act on complaints\n“perpetuate[d] the City’s custom of acquiescing in the\nexcessive use of force by its police officers”). In light of\nthese allegations, “it is logical to assume that [the City’s]\ncontinued official tolerance of repeated misconduct\nfacilitate[d] similar unlawful actions in the future,” including\nthe search and arrest of Roman. Bielevicz, 915 F.2d at 851. It\nfollows that he has adequately pled a municipal custom and\nproximate causation under § 1983.\n We reach the same conclusion with respect to\nRoman’s failure-to-train, failure-to-supervise, and failure-to-\ndiscipline claims. To start, the Star Ledger article includes a\nstatement on police training from James Stewart, Jr., the head\nof Newark’s police union. He conceded the “last training [he]\nreceived” was in 1995, when he first joined the Newark\nPolice Department. App. at 134 (internal quotation marks\nomitted). Moreover, Stewart is not some unreliable, rogue\nofficer—he is the head of the police union. Nor is his\nexperience isolated: the consent decree indicates Newark\npolice officers in general were not trained on “the\nrequirements of [the] Fourth Amendment and related law.”\nId. at 160 (discussing various Fourth Amendment doctrines\n\n\n\n\n 16\n\nthat should be included in police training, including “the\ndifference[] . . . between voluntary consent and mere\nacquiescence to police authority”). The consent decree also\ntouches on supervisory review of unlawful searches and\narrests, requiring desk lieutenants and unit commanders to\nreview “searches that appear to be without legal justification”\nand “arrests that are unsupported by probable cause.” Id. at\n161. Finally, it provides disciplinary measures for police\nofficers who engage in “unlawful . . . searches” and “false\narrests.” Id. at 192. At the pleadings stage, a fair inference is\nthat the consent decree was necessary because of Department-\nwide failures, not because one officer was last trained in\n1995.\n This is enough to prove municipal liability because the\nCity “[knew] to a moral certainty” that its officers would need\nto conduct searches. Harris, 489 U.S. at 390 n.10. Yet in at\nleast one instance it failed to provide training since 1995, see\nApp. at 134, and per the decree its training did not cover the\nbasics of the Fourth Amendment, see id. at 158-61. The City\nalso did not discipline officers for “sustained allegations of\nmisconduct,” including “prior violations” and other\n“aggravating factors.” Id. at 192-93. In view of these\ndeficiencies, one could reasonably infer that the City’s\ninaction “reflected [its] ‘deliberate indifference’” to Roman’s\nFourth Amendment rights. Bd. of Cty. Comm’rs v. Brown,\n520 U.S. 397, 409 (1997); cf. Harris, 489 U.S. at 390 n.10\n(“[C]ity policymakers know to a moral certainty that their\npolice officers will be required to arrest fleeing felons. . . .\nThus, the need to train officers in the constitutional\nlimitations on the use of deadly force . . . can be said to be ‘so\nobvious’ . . . that failure to do so could properly be\ncharacterized as ‘deliberate indifference’ to constitutional\nrights.” (internal citation omitted)). One could also infer that\nthe City’s failure to establish an adequate training program\ncontributed to the specific constitutional violations alleged in\n\n\n\n\n 17\n\nthe amended complaint. See Brown, 520 U.S. at 409-10\n(“The likelihood that the situation will recur and the\npredictability that an officer lacking specific tools to handle\nthat situation will violate citizens’ rights . . . may also support\nan inference of causation.”); cf. A.M. ex rel. J.M.K. v. Luzerne\nCty. Juvenile Detention Ctr., 372 F.3d 572, 582 (3d Cir.\n2004) (reversing the District Court’s grant of summary\njudgment in favor of a municipality because of “unrebutted\ntestimony” that its juvenile detention center “did not have an\nadequate training program”).\n We conclude that the allegations regarding Newark’s\nfailure to train, supervise, and discipline are strong enough to\nsurvive a motion to dismiss. See Am. Compl. ¶¶ 63-98.\nAmong them are: a failure to train officers on obtaining a\nsearch warrant, id. ¶ 67, and on “issuing truthful investigative\nreports,” id. ¶ 77; a failure to supervise and manage officers,\nid. ¶¶ 67-68; and a failure to discipline officers, id. ¶ 74, first\nby “refus[ing]” to create a well-run Internal Affairs\nDepartment, id. ¶ 81, and second by “inadequately\ninvestigating, if investigating at all, citizens’ complaints\nregarding illegal search and seizure, id. ¶ 84. The result was a\n“complete lack of accountability” and of “record keeping,” id.\n¶ 92, leading to a culture in which officers “knew there would\nbe no professional consequences for their action[s],” id. ¶ 94.\nAs the amended complaint alleges, it should come as no\nsurprise that these conditions led to a federal investigation.\nSee id. ¶ 89.\n The dissent’s attempt to distinguish the consent decree\nis unpersuasive. First, it misperceives the decree as\nconcerning only police interactions with “pedestrians or the\noccupants of vehicles,” not home searches. Dissenting Op. at\n7 (“The consent decree says nothing about arrests and\nsearches without consent that occur at residences . . .”). In\nfact, one concern of the decree was false arrests, see App. at\n\n\n\n\n 18\n\n158, which can occur both at home and on the street. And the\ndecree does concern home searches: it sets parameters\nofficers must follow before searching “a home based upon\nconsent.” Id. Although Reyes by no means consented to the\nsearch here, she willingly opened her apartment door only\nbecause the police had used her friend Isaksem as a Trojan\nhorse to gain entry.\n Second, the dissent believes that the consent decree\ncannot help Roman’s case because Roman was Hispanic. See\nDissenting Op. at 7 (“[T]he decree addressed police practices\nthat disparately impacted the black community. But that\nracial disparity did not apply to Roman, who was Hispanic.”).\nTo the contrary, the consent decree includes an entire section\nentitled “Bias-Free Policing,” see App. at 165-67, that never\nrestricts itself to bias against the black community. Instead, it\nprovides that police officers must “operate without bias based\non any demographic category,” id. at 166 (emphasis added),\nand specifically forbids officers from discriminating based on\n“proxies for demographic category” such as “language\nability,” id. at 167. Plainly, the consent decree was meant to\nprotect all Newark residents, including Hispanic residents.\n Further, we find it difficult to square the dissent’s\nreasoning with the record evidence discussing the City’s\ntroubling practices around the time of Roman’s search and\narrest. See, e.g., id. at 134 (stating only one complaint out of\n261 filed was sustained by department investigators); id. at\n158 (prohibiting officers from relying on materially false\ninformation to justify a warrantless search); id. at 160\n(requiring police officers to be trained on “the requirements\nof [the] Fourth Amendment and related law”); id. at 161\n(mandating supervisory review of “searches that appear to be\nwithout legal justification” and “arrests that are unsupported\nby probable cause”).\n\n\n\n\n 19\n\n Unable to distinguish the consent decree outright, the\ndissent offers two narrow readings of the decree. First, it\nmaintains that the decree can speak only to the Police\nDepartment’s obligations going forward rather than shed any\nlight whatsoever on the “status quo” within the Department\nbefore federal intervention. See Dissenting Op. at 10 (stating\nthat the decree does not provide “any detail as to the status\nquo it addressed”). The dissent concedes that the DOJ\nprobably did not enter into the consent decree because it was\nimpressed with Newark’s policing practices and wanted to\nencourage the City to keep up the good work. Id. At this\nstage, we must draw not only such obvious inferences, but\nalso all reasonable ones, in favor of Roman. Thus we agree\nwith the dissent on the “clear” difference between “agreeing\nto train more” (the consent decree on its face) and “agreeing\nthat prior training was constitutionally inadequate” (the way\nin which the decree supports Roman’s claims). Id. We\nsimply believe that a reasonable inference bridges the gap in\nthis case. Indeed, no inference is needed because Roman\nmade the link explicit in the amended complaint. See Am.\nCompl. ¶ 89 (stating that the Police Department’s “deliberate\nindifference to citizens’ rights is what led to the imposition of\na [f]ederal [m]onitor program . . . .”).\n\n Second, the dissent believes that the consent decree’s\ntraining requirements, from which we can reasonably infer\ninadequate training before the decree, simply amount to\n“additional training” in, for instance, the requirements of the\nFourth Amendment. Dissenting Op. at 10. To the contrary,\nthe consent decree was meant to take the Newark Police\nDepartment back to basics: Do not lie on a warrant\napplication or to justify a warrantless search, App. at 158;\ninvestigate police activities that appear to have lacked legal\njustification, id. at 161; and at all times follow the\nrequirements of the Fourth Amendment, id. at 160.\n\n\n\n\n 20\n\n The theme of the dissent appears to be that we are\nrefashioning the amended complaint. It claims we are\nvacating the District Court’s decision based on facts and\narguments that were not presented to it. But as discussed\nabove, we are engaged in de novo review of the adequacy of\nthe amended complaint in light of documents that were before\nthe District Court and that informed its allegations. See supra\npp. 8-10. Additionally, and to repeat, the specific events\nleading up to Roman’s search and arrest are not relevant to\nthe merits of his municipal liability claim. Thus we are not\nvacating the Court’s decision for excluding these facts from\nits analysis.\n Rather, our focus is directed to Newark’s practice at\nthe time of Roman’s search and arrest. The Court had notice\nof them, as it acknowledged that Roman alleged “a ‘pattern or\npractice of constitutional violations in areas including stop[]\nand arrest practices, use of force, and theft by officers.’”\nRoman, 2017 WL 436251, at *4 (quoting Compl. ¶ 59).\nNonetheless it dismissed the complaint and amended\ncomplaint because it viewed the City as attempting to change\nits practices. Even if the record can be read that way—and\nwe doubt that8—the District Court’s rationale has the wrong\n\n\n 8\n The record does not support the Court’s inferences,\nas it tells us the DOJ’s investigation was not completed until\nJuly 2014, see App. at 137; the Government did not solicit\napplications for a federal monitor until February 2015, see id.;\nand the consent decree was not final until May 2016, see id.\nat 215. By contrast, Roman was arrested in May 2014 and\nimprisoned until December of that year. As such, it is\nplausible that Newark’s practices were ongoing when police\nofficers searched and arrested him. It is also reasonable to\ninfer that the City’s corrective measures postdated the arrest.\n\n\n\n\n 21\n\nfocus. The question is not whether some evidence can be\nviewed as supporting the City. It is whether, viewing the\npleadings and properly associated documents in the light most\nfavorable to Roman, there are claims plausible enough to\nwithstand a motion to dismiss. We think there is one—the\nmunicipal liability claim. And the Court did not have to look\nbeyond the amended complaint and supporting documents to\nglean these facts.\n\n In sum, Roman’s municipal liability claim survives\ndismissal based on the record that was before the District\nCourt. Because the Court reached the opposite conclusion,\nwe part with its holding. Thus we vacate and remand this\nportion of its decision.\n B. The District Court correctly dismissed the\n false imprisonment and malicious\n prosecution claims because they were not\n pled under § 1983.\n\n Roman alleges the Defendants are also liable for false\nimprisonment and malicious prosecution. As noted, the\nDistrict Court construed these claims as state-law claims. It\ndismissed them because Roman did not comply with the New\nJersey Tort Claims Act’s procedural requirements for\nbringing claims against public entities and public employees.\nSee N.J. Stat. Ann. § 59:8-1 et seq.\n On appeal, Roman contends the Court erred in\ndismissing his claims because they were pled under § 1983.\nThe Defendants counter that both claims were presented as\n\n\n\nHence we do not consider the City’s corrective measures to\nbe enough to defeat Roman’s allegations.\n\n\n\n\n 22\n\nstate-law tort claims. They also point out that Roman omitted\nthem from his amended complaint.9\n\n As a preliminary matter, the Defendants correctly\nobserve that false imprisonment and malicious prosecution\nare not in the amended complaint. Hence we must first\ndecide if Roman has waived his right to challenge their\ndismissal on appeal. If we conclude that waiver does not\napply, we then determine if the District Court correctly\nconstrued them as state-law tort claims.\n We have not applied a strict rule in favor of waiver in\nthis context. Instead, we have allowed “plaintiffs to appeal\ndismissals despite amended pleadings that omit the dismissed\nclaim[,] provided repleading the particular cause of action\nwould have been futile.” United States ex rel. Atkinson v. Pa.\nShipbuilding Co., 473 F.3d 506, 516 (3d Cir. 2007) (emphasis\nin original) (footnote omitted). “Repleading is futile when\nthe dismissal was ‘on the merits.’ A dismissal is on the\nmerits when it is with prejudice or based on some legal\nbarrier other than want of specificity or particularity.” Id. If\na court is uncertain, “doubt[] should be resolved against the\nparty asserting waiver.” Id. at 517 (emphasis in original).\n\n 9\n At oral argument, Roman’s counsel stated the false\nimprisonment claim was repled in Count 13 of the amended\ncomplaint even though that count alleges “conspiracy to\ncommit unlawful imprisonment . . . [in violation of] 42\nU.S.C. § 1985.” App. at 278 (emphasis added); see Audio\nRecording of Oral Argument held June 12, 2018 at 11:39 to\n12:06 (http://www2.ca3.uscourts.gov/oralargument/audio/17-\n2302TheEstateofAdrianoRomanJrvCityofNewarketal.mp3).\nWe do not consider this contention, as it was raised for the\nfirst time at oral argument and thus is waived. See In re\nGrand Jury, 635 F.3d 101, 105 n.4 (3d Cir. 2011).\n\n\n\n\n 23\n\n Here the District Court analyzed both claims on legal\ngrounds. It observed that they were based on the New Jersey\nTort Claims Act, which allows individuals to bring tort claims\nagainst public entities and employees after complying with\ncertain procedural and notice requirements, see Tripo v.\nRobert Wood Johnson Med. Ctr., 845 F. Supp. 2d 621, 626-\n27 (D.N.J. 2012) (summarizing the Act’s procedures for suing\na public entity or employee). It concluded Roman did not\nfollow these requirements and thus dismissed the claims.\n Although the Court was guided by procedural\nconcerns, its dismissal was on the merits. The Tort Claims\nAct bars claims against public entities and employees if a\nplaintiff waits more than two years to file a “notice of claim.”\nSee N.J. Stat. Ann. § 59:8-8(b). The two-year mark is\nmeasured from the day the claim accrues (i.e., the day on\nwhich the public entity or employee allegedly harmed the\nplaintiff). In our case, because Roman’s claims accrued in\nMay 2014, he had until May 2016 to file a notice of claim.\nAs the Court noted, however, he did not file any type of\nnotice during the two-year period. See Roman, 2017 WL\n436251, at *6 (observing that, as of January 31, 2017, the date\non which the Court dismissed the complaint, Roman had not\nfiled a notice). Thus Roman’s procedural error morphed into\na dismissal on the merits, see N.J. Stat. Ann. § 59:8-8(b)\n(“The claimant shall be forever barred from recovering\nagainst a public entity or public employee if . . . [t]wo years\nhave elapsed since the accrual of the claim.”), and he may\nappeal the District Court’s decision on his false imprisonment\nand malicious prosecution claims, see Atkinson, 473 F.3d at\n516-17.\n In light of this conclusion, we must focus on the\npleadings and decide if Roman’s claims are based on § 1983.\nIf we look to the complaint, it suggests both false\nimprisonment and malicious prosecution are state-law tort\n\n\n\n\n 24\n\nclaims. It never identifies them as § 1983 or federal claims.\nRather, it presents them generically, following a series of\nother state-law tort claims. See, e.g., App. at 44 (“intentional\ninfliction of emotional distress”); id. at 46 (“negligent\ninfliction of emotional distress”); id. at 47 (“assault and\nbattery”); id. at 49 (“unlawful imprisonment”); id. at 51\n(“malicious prosecution”). This indicates to us that Roman\npled both claims as state-law claims, not federal claims.\nWhile the unlawful (i.e., false) imprisonment claim does note\nthat the Defendants “restrict[ed] [Roman’s] constitutionally\nguaranteed rights of liberty and freedom of movement,” it is\nsilent as to whether it refers to the United States or New\nJersey Constitution. Compl. ¶ 114. This is too facile to\nimply the former when but a few identifying words would do.\nThe default is New Jersey law, which defines false\nimprisonment as “an[y] unlawful restraint that interferes with\na victim’s liberty” and requires “[n]o further wrongful\npurpose” for a prima facie showing. State v. Savage, 799\nA.2d 477, 494 (N.J. 2009).\n Accordingly, the District Court correctly construed the\nfalse imprisonment and malicious prosecution claims as state-\nlaw tort claims, and we affirm this portion of its holding.10\n C. The doctrines of res judicata, collateral\n estoppel, and judicial estoppel do not require\n us to dismiss Roman’s § 1983 claims.\n Finally, the Defendants invoke the doctrines of res\njudicata, collateral estoppel, and judicial estoppel. According\n\n\n 10\n We also affirm the dismissal of Roman’s unlawful-\nsearch claims because they were not adequately pled. We do\nnot opine on whether a plaintiff may allege joint and several\nliability in connection with an unlawful-search claim.\n\n\n\n\n 25\n\nto them, each doctrine compels us to dismiss Roman’s § 1983\nclaims.\n\n We start with res judicata. The Defendants contend it\nbars Roman’s claims because “the criminal matter and the\nsuppression hearing were based on the exact same facts” as\nthose alleged in Roman’s pleadings. Defendants’ Br. at 64.\nIn their view, criminal proceedings are enough to preclude a\ncivil suit seeking damages under § 1983.\n\n We disagree. “A party seeking to invoke res judicata\nmust establish three elements: (1) a final judgment on the\nmerits in a prior suit involving (2) the same parties or their\nprivies and (3) a subsequent suit based on the same cause of\naction.” Duhaney v. Att’y Gen., 621 F.3d 340, 347 (3d Cir.\n2010) (internal quotation marks omitted). Roman’s suit is not\nbased on the same cause of action as the criminal complaint\nand suppression hearing. Nor are his current claims of the\ntype “that could have been brought” in the earlier criminal\nproceeding. Id. (internal quotation marks omitted); see also\nHelvering v. Mitchell, 303 U.S. 391, 397 (1938) (“The\ndifference in degree of the burden of proof in criminal and\ncivil cases precludes application of the doctrine of res\njudicata.”). New Jersey initiated the criminal case. Roman\nwas not at liberty to assert any claims except for defenses\nagainst the prosecution’s case-in-chief. See Leather v. Eyck,\n180 F.3d 420, 425 (2d Cir. 1999) (“[B]ecause the nature of\nthe prior state[-]court proceeding was such that [the\nAppellant] could not have sought damages for his alleged\nconstitutional injuries (while defending himself on [a\ncriminal] charge . . . ), res judicata does not bar his federal §\n1983 suit for damages.”). Moreover, he was not free to raise\nhis § 1983 claims in the same criminal case; indeed, he could\nnot bring them until the criminal proceeding concluded. See\nHeck v. Humphrey, 512 U.S. 477, 486 (1994) (“[T]he . . .\nprinciple that civil tort actions are not appropriate vehicles for\n\n\n\n\n 26\n\nchallenging the validity of outstanding criminal judgments\napplies to § 1983 damages actions that necessarily require the\nplaintiff to prove the unlawfulness of his conviction or\nconfinement. . . .”). Accordingly, res judicata does not bar\nRoman’s claims.\n\n Moving on to collateral estoppel, the Defendants argue\nit (1) absolves Officer Mendes of liability because the\nSuperior Court made a factual finding that Roman possessed\nthe contraband that was seized from the apartment, (2)\nabsolves Sergeant Joyce Hill because nothing in the Superior\nCourt’s transcript indicates she was present for the search and\narrest, and (3) absolves the other named defendants because\nthe Superior Court’s transcript suggests they only handled the\ncontraband. According to the Defendants, the Superior Court\ndecided all of these issues in their favor during the\nsuppression hearing. See Bd. of Trs. of Trucking Emps. of N.\nJersey Welfare Fund, Inc. v. Centra, 983 F.2d 495, 505 (3d\nCir. 1992) (stating a party is collaterally estopped from\nlitigating a specific issue if, among other things, “[an]\nidentical issue was decided in a prior adjudication”). Again\nwe disagree. Contrary to the Defendants’ assertions, the\nSuperior Court never decided any of these issues during the\nsuppression hearing. While it did find that Roman had a\npossessory interest in the apartment, that is not enough for us\nto conclude that he had actual or constructive possession over\nthe contraband. Collateral estoppel is not appropriate in this\ncontext.\n Last, the Defendants assert that judicial estoppel\nprecludes Roman’s claims because he admitted that (1) drugs\nwere found in the apartment, (2) he had a possessory interest\nin the apartment, (3) Officer Mendes was the only officer who\ninitiated the prosecution, and (4) the remaining officers only\nhandled the contraband and had no other roles. They insist\nthese concessions “are sufficient to establish that [Roman’s]\n\n\n\n\n 27\n\narrest and prosecution arise out of his possession of\nincriminating evidence[.]” Defendants’ Br. at 65. As noted,\n“[j]udicial estoppel, sometimes called the ‘doctrine against\nthe assertion of inconsistent positions,’ is a judge-made\ndoctrine that . . . prevent[s] a litigant from asserting a position\ninconsistent with one that []he has previously asserted . . . in a\nprevious proceeding.” Ryan Operations G.P., 81 F.3d at 358.\nThis doctrine is not in play here, as Roman never stipulated\nthat Officer Mendes was the only officer to bring the\nprosecution or that the remaining officers only handled the\ncontraband. While the Court found that Roman had a\npossessory interest in the apartment, that interest (we repeat)\nis not enough to establish that he possessed the contraband.\nAccordingly, judicial estoppel does not require us to dismiss\nRoman’s claims.\n * * * * *\n Roman has sufficiently alleged a municipal liability\nclaim against the City of Newark under § 1983. He cites\nvarious examples of inadequate police training, poor police\ndiscipline, and unheeded citizen complaints. He tells us\ncertain police officers did not receive training for over 20\nyears, and their training did not cover the basic requirements\nof the Fourth Amendment. In his pleadings, he states the\nNewark Police Department did not discipline officers who\nengaged in police misconduct, Am. Compl. ¶¶ 84-86,\nincluding unlawful searches and false arrests, App. at 134.\nHe also notes the public filed formal complaints about\nimproper searches and false arrests that were disregarded\nalmost wholesale. Id. These alleged practices were ongoing\nwhen Roman’s search and arrest occurred, and the City had\nnotice of them at that time. While the proof developed to\nsupport these allegations may or may not be persuasive to a\nfinder of fact, they are enough to survive dismissal at this\nstage. Based on this conclusion, we part with the District\n\n\n\n\n 28\n\nCourt’s holding that Roman failed to state a § 1983 claim\nagainst the City. Though we affirm otherwise, we vacate and\nremand its decision on municipal liability.\n\n\n\n\n 29\n[END_CASE]", "role": "user" } ]
4,578,632
Clarence GRIFFIN, Plaintiff - Appellant, v. DEPARTMENT OF LABOR FEDERAL CREDIT UNION, A/K/A DOLFCU, Defendant - Appellee, National Association of Federally-Insured Credit Unions; Credit Union National Association, Amici Supporting Appellee.
Griffin v. Dep't of Labor Fed. Credit Union
2019-01-03
18-1312
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Wilkinson, King, Quattlebaum", "parties": "", "opinions": [{"author": "WILKINSON, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1312\n\n\nCLARENCE GRIFFIN,\n\n Plaintiff – Appellant,\n\n v.\n\nDEPARTMENT OF LABOR FEDERAL CREDIT UNION, a/k/a DOLFCU,\n\n Defendant – Appellee,\n\n------------------------------\n\nNATIONAL ASSOCIATION OF FEDERALLY-INSURED CREDIT UNIONS;\nCREDIT UNION NATIONAL ASSOCIATION,\n\n Amici Supporting Appellee.\n\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. T.S. Ellis, III, Senior District Judge. (1:17-cv-01419-TSE-IDD)\n\n\nArgued: October 30, 2018 Decided: January 3, 2019\n\n\nBefore WILKINSON, KING, and QUATTLEBAUM, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355885/", "author_raw": "WILKINSON, Circuit Judge:"}, {"author": "Quattlebaum joined. Judge King wrote an opinion concurring", "type": "concurrence", "text": "Quattlebaum joined. Judge King wrote an opinion concurring in the judgment.\n\nARGUED: Thomas Eugene Strelka, STRELKA LAW OFFICE, Roanoke, Virginia, for\nAppellant. John Michael Bredehoft, KAUFMAN & CANOLES, PC, Norfolk, Virginia,\nfor Appellee. ON BRIEF: L. Leigh Strelka, Norvell W. West IV, STRELKA LAW\nOFFICE, Roanoke, Virginia; Scott J. Ferrell, Victoria C. Knowles, PACIFIC TRIAL\nATTORNEYS, P.C., Newport Beach, California, for Appellant. Edward Lee Isler, Mark\nE. Papadopoulos, ISLER DARE, P.C., Vienna, Virginia, for Amicus National\nAssociation of Federally-Insured Credit Unions. Jonathan C. Sandler, Los Angeles,\nCalifornia, Christine A. Samsel, Denver, Colorado, Michael H. Pryor, BROWNSTEIN\nHYATT FARBER SCHRECK, LLP, Washington, D.C., for Amicus Credit Union\nNational Association.\n\n\n\n\n 2\n\nWILKINSON, Circuit Judge:\n\n Appellant here has asserted that he has standing to challenge various aspects of the\n\nDepartment of Labor Federal Credit Union’s website under the Americans with\n\nDisabilities Act. 42 U.S.C. § 12101 et seq. The district court granted the Credit Union’s\n\nFederal Rule of Civil Procedure 12(b)(1) motion to dismiss. Because we agree that\n\nappellant lacks constitutional standing, we now affirm the judgment.\n\n I.\n\n The Department of Labor Federal Credit Union, the appellee, is a federal credit\n\nunion that, under the Federal Credit Union Act of 1934, accepts as members only those\n\nwho share the “common bond” of being current and former employees of the Department\n\nof Labor and their immediate families and households. 12 U.S.C. § 1759(b). Only\n\nmembers can take advantage of the Credit Union’s products or services; only members\n\nmay open an account or take out a loan or enjoy in any way the benefits of the Credit\n\nUnion. The Credit Union maintains a website that describes its services and products.\n\n Clarence Griffin, the appellant, is a blind resident of Virginia. Because of his\n\nvisual impairment, Griffin uses a screen reader to access the Internet. As he explains in\n\nhis complaint, screen readers help the blind access the Internet by reading aloud the text\n\nthat appears on a website. Website operators often take special care to ensure their sites\n\nare legible to screen readers. Many visually impaired people like Griffin also rely more\n\nheavily on keyboards than mouses to navigate the Internet. Because of this, it is\n\nrecommended that website operators avoid “redundant links,” which can be tedious and\n\ntime-consuming for keyboard users to navigate.\n\n 3\n\n Griffin is not eligible for membership in the Credit Union. He does not work for\n\nthe Department of Labor and never has in the past. No one in his immediate family has\n\never worked for the Department of Labor, nor has any member of his household. He\n\nmakes no allegation in his complaint that he is legally permitted to make use of the Credit\n\nUnion’s benefits. *\n\n According to his complaint, Griffin tried to access the Credit Union’s website in\n\nOctober of 2017. He alleges his attempt was stymied in three ways. First, there were\n\nlinked images that lacked “alternative text.” As a consequence, Griffin’s screen reader\n\ncould not describe those images to him and he could not navigate to the linked content.\n\nSecond, there were “redundant links.” This meant Griffin had to take additional,\n\nunnecessary steps to make full use of the site. And third, “form labels” were missing.\n\nGriffin could not tell when the website wanted him to input information that is often\n\nnecessary to access the site further.\n\n Griffin sued, arguing that the Credit Union’s failure to make reasonable\n\nmodifications to its policies and practices that would make its site accessible to the\n\ndisabled violated the Americans with Disabilities Act, 42 U.S.C. §12101 et seq. The\n\ncomplaint sought injunctive relief as well as costs and attorney’s fees. The Credit Union\n\n\n\n *\n Questions surfaced at oral argument regarding Griffin’s eligibility to make use of\nthe Credit Union’s ATMs. This argument appears nowhere in the briefing, perhaps\nbecause it is tangential or an afterthought to the central inquiry. Plaintiff does mention\nATMs in his complaint, stating that they are “available to Defendant’s members,” J.A.\n15, which, as noted, Griffin plainly is not.\n\n\n 4\n\nmoved to dismiss for lack of standing, pursuant to Federal Rule of Civil Procedure\n\n12(b)(1), which the district court granted. Griffin now appeals this dismissal.\n\n II.\n\n Griffin puts his case in broad terms, claiming that the rights generally of people\n\nwith disabilities to sue for Internet-based harms under the ADA are at stake. But that\n\nquestion is not before us. This case concerns the application of standing doctrine in an\n\nelectronic age and it is important that we move narrowly in exploring this new territory.\n\nAccordingly, we address only whether this plaintiff who is barred by law from making\n\nuse of defendant’s services may sue under the ADA for an allegedly deficient website.\n\nThe answer to this narrow question here is no.\n\n Article III limits the judicial power of the United States to “Cases” and\n\n“Controversies.” Embedded in this limitation is a “set of requirements that together make\n\nup the ‘irreducible constitutional minimum of standing.’” Lexmark Intern., Inc. v. Static\n\nControl Components, Inc., 572 U.S. 118, 125 (2014) (quoting Lujan v. Defenders of\n\nWildlife, 504 U.S. 555, 560 (1992)). Where these requirements are not met, this court\n\nwould “exceed [its] authority” if it adjudicated the merits of a dispute. Spokeo, Inc. v.\n\nRobins, 136 S. Ct. 1540, 1547 (2016).\n\n An injury in fact is an indispensable aspect of constitutional standing; no “Case”\n\nor “Controvers[y]” exists without injury. It is “[f]irst and foremost” of the three\n\nrequirements of constitutional standing. Spokeo, 136 S. Ct. at 1547 (quoting Steel Co. v.\n\nCitizens for Better Environment, 523 U.S. 83, 103 (1998)) (describing the other two\n\nrequirements as causation and redressability). A wrong suffered by a party is only an\n\n 5\n\ninjury in fact if it is sufficiently “concrete and particularized.” Id. at 1545 (quoting\n\nFriends of the Earth, Inc. v. Laidlaw Environmental Services (TOC), Inc., 528 U.S. 167\n\n180-81 (2000)) (emphasis in original). These are separate criteria which must both be\n\nsatisfied. Id. And when a party seeks injunctive relief, as Griffin does, there is the\n\nadditional requirement of a “real or immediate threat” that the party will suffer an injury\n\nin the future. City of Los Angeles v. Lyons, 461 U.S. 95, 111 (1983).\n\n Thus, in order to prevail, Griffin must allege an injury that is concrete,\n\nparticularized, and immediately threatening. It is important that we do not take a cramped\n\nview of standing in civil rights cases, lest we impair the remedial purpose Congress had\n\nin mind when enacting civil rights statutes. But even under this broad view Griffin’s\n\ncomplaint fails to satisfy each of the Supreme Court’s requirements. We address them in\n\nturn.\n\n A.\n\n Griffin’s alleged injury is not concrete. An injury is “concrete” when it is “real and\n\nnot abstract.” Spokeo, 136 S. Ct. at 1548. But an injury may be concrete without being\n\n“tangible.” Id. at 1549. In deciding what intangible injuries are concrete, we consult the\n\n“judgment of Congress” because “Congress is well positioned to identify intangible\n\nharms that meet minimum Article III requirements.” Id. See also Moore v. Blibaum &\n\nAssociates, P.A., 693 Fed. Appx. 205, 206 (4th Cir. 2017) (“In particular, the injury-in-\n\nfact requirement is not limited simply to financial or economic losses.”). Dignitary harms\n\nor “stigmatic injur[ies],” while not tangible, may be sufficiently concrete to constitute\n\n\n\n 6\n\ninjury in fact, Allen v. Wright, 468 U.S. 737, 754-55 (1984), and therefore may\n\nconstitutionally be protected by statute.\n\n Griffin has alleged just such a dignitary harm. It is true that his complaint does not\n\ninclude the phrases “dignitary harm” or “stigmatic injury.” But such a ritual incantation is\n\nunnecessary; dignitary harms are readily inferred by allegations of unequal treatment. See\n\nAllen, 468 U.S. 752-53. And Congress, in enacting the ADA, intended in part to protect\n\npeople with disabilities against stigmatic injury. Tennessee v. Lane, 541 U.S. 509, 536\n\n(2004) (Ginsburg, J., concurring); Shaver v. Independent Stave Co., 350 F.3d 716, 724\n\n(8th Cir. 2003).\n\n But not all dignitary harms are sufficiently concrete to serve as injuries in fact. As\n\nJustice O’Connor explained in Allen v. Wright, geographic separation between the\n\nchallenged conduct and the stigmatic injury can reduce the “personal” impact of the\n\ninjury and render it too “abstract.” Allen, 468 U.S. at 756-57. “A black person in\n\nHawaii,” for example, cannot challenge “a racially discriminatory school in Maine.” Id.\n\nat 757. Otherwise, the federal courts would “transform” into a “vehicle for the\n\nvindication of value interests of concerned bystanders.” Id. at 756 (quoting United States\n\nv. SCRAP, 412 U.S. 669, 687 (1973)).\n\n The legal barriers between Griffin and the Credit Union render his injury\n\n“abstract” just as the geographic barriers did in Allen. Allen’s hypothetical Hawaiian\n\nlitigant could not sue the Maine school because geography made it impossible for the\n\nplaintiff to interact directly with the school and be “personally subject” to its\n\ndiscrimination. Allen 468 U.S. at 757 n.22. Here, a neutral proposition of federal law\n\n 7\n\nmakes it impossible for Griffin to interact directly with the Credit Union. The Federal\n\nCredit Union Act of 1934 expressly forbids the provision of any products or services to\n\nhim. 12 U.S.C. § 1759. It is therefore impossible—absent a violation of federal law—for\n\nGriffin to be “personally subject” to the dignitary harms allegedly occasioned by the\n\nCredit Union’s website.\n\n Griffin’s assertion of informational harm fares no better than his assertion of\n\ndignitary harm, for the same reason. Inability to obtain information is sufficiently\n\nconcrete to constitute injury in fact only when the information has some relevance to the\n\nlitigant. In Federal Election Commission v. Akins, the Supreme Court explained that\n\nplaintiffs who sought information that would “help them . . . evaluate candidates for\n\npublic office” suffered a concrete injury when they failed to receive it. 524 U.S. 11, 21\n\n(1998). The information was relevant to the plaintiffs’ fulfillment of their civic\n\nresponsibility. See also Dreher v. Experian Information Solutions, Inc., 856 F.3d 337,\n\n345 (4th Cir. 2017). Here, on the other hand, the information Griffin failed to obtain\n\nlacks a comparable relevance to him. Griffin sought information on the Credit Union’s\n\n“services, privileges, advantages, and accommodations and amenities,” as well as the\n\nphysical locations where those services are provided. J.A. 13. But this information lacks\n\nthe requisite relevance to Griffin; a federal law closes the door of the Credit Union to\n\nGriffin whether or not he obtains the information he seeks. 12 U.S.C. § 1759.\n\n B.\n\n Griffin’s injury is also not particularized. For an injury to be particularized, it must\n\naffect the plaintiff in a way that is “individual.” Lujan v. Defenders of Wildlife, 504 U.S.\n\n 8\n\n555, 560 n.1 (1992); Daniels v. Arcade, L.P., 477 Fed. Appx. 125, 129 (4th Cir. 2012).\n\nThere must be some connection between the plaintiff and the defendant that\n\n“[]differentiate[s]” the plaintiff so that his injury is not “common to all members of the\n\npublic.” United States v. Richardson, 418 U.S. 166, 177 (1974) (quoting Ex parte Levitt,\n\n302 U.S. 633, 634 (1937)). Thus, as the Supreme Court explained in Lujan v. Defenders\n\nof Wildlife, just “anyone who goes to see Asian elephants in the Bronx Zoo” cannot sue a\n\ndefendant whose actions have harmed that species in a particular part of the world. 504\n\nU.S. at 566. His injury is not particularized. But, a person who, as a vocation, studies\n\nAsian elephants in the part of the world in question “plausib[ly]” has enough of a\n\nconnection to convert the general harm to the species into a particular harm to the\n\nplaintiff. Id.\n\n Griffin has not pointed to any connection between the defendant and himself that\n\ntransforms the general harms he alleges into particularized ones. Again, the law of credit\n\nunions is dispositive on this point. The Federal Credit Union Act of 1934 positively\n\nforbids Griffin from taking advantage of any of the Credit Union’s products or services\n\nbecause he does not share the “common bond” of those who may become its members.\n\n12 U.S.C.§ 1759(b). That law severs any connection between the Credit Union and\n\nGriffin that could plausibly serve to particularize his alleged injury.\n\n The cases Griffin points to do not counsel the opposite conclusion. In Menkowitz\n\nv. Pottstown Memorial Medical Center, the plaintiff was a doctor with “staff privileges”\n\nat the defendant hospital. 154 F.3d 113, 115 (3d Cir. 1998). Those staff privileges\n\nsupplied the requisite connection between plaintiff and defendant that converted an\n\n 9\n\notherwise general harm into a particular one. Likewise, visits to a physical location may\n\nsupply a particularizing connection, as they differentiate the plaintiff from the general\n\npublic who are barred by distance from ever making such a visit. Griffin’s reference to\n\nthose cases in which a visit was actually made or plausibly contemplated is therefore\n\ninapt. Br. for the Appellant at 25-32 (citing Houston v. Marod Supermarkets, Inc., 733\n\nF.3d 1323, 1326 (11th Cir. 2013); Molski v. M.J. Cable, 481 F.3d 724, 727 (9th Cir.\n\n2007); Civil Rights Education and Enforcement Center. v. Hospitality Props. Trust, 867\n\nF.3d 1093, 1096 (9th Cir. 2017).\n\n C.\n\n Griffin has not suffered a concrete and particular injury in the past. There is also\n\nnot an immediate threat that Griffin will suffer an injury in fact in the future. A plaintiff\n\nhas standing to sue for injunctive relief when there is “real or immediate threat” that the\n\nparty will suffer an injury in the future. City of Los Angeles v. Lyons, 461 U.S. 95, 111\n\n(1983). Such an injury must be “imminent.” Clapper v. Amnesty Intern. USA, 568 U.S.\n\n398, 409 (2013). “[I]mminence is concededly a somewhat elastic concept,” but it “cannot\n\nbe stretched beyond its purpose.” Id. (quoting Lujan, 504 U.S. at 565, n. 2). In short, an\n\ninjury should be “certainly impending” to serve as the basis for standing in a suit for\n\ninjunctive relief. Whitmore v. Arkansas, 495 U.S. 149, 158 (1990).\n\n This court’s opinion in Nanni v. Aberdeen Marketplace is both insightful and\n\ninstructive on this point as it pertains to injuries under ADA. 878 F.3d 447 (4th Cir.\n\n2017). There we explained that a plaintiff who experienced a past injury from a visit to a\n\nphysical location need only show a plausible intent to return to that location in order to\n\n 10\n\nhave standing to sue for injunctive relief. Id. at 455. Nanni, the plaintiff, visited the\n\ndefendant Marketplace and allegedly discovered that the Marketplace’s various ADA\n\nviolations impeded his use of a wheelchair. Id. We held that this was a sufficiently\n\nconcrete and particular past injury. Id. at 456. We further held that Nanni’s intent to\n\nreturn to the Marketplace was plausible because he passed the store several times a year\n\non visits to Baltimore and Washington from his home in Delaware. Id. And so, despite\n\nthe distance between the Marketplace and Nanni’s home, we held that he had standing to\n\nsue. See also Houston v. Marod Supermarkets, Inc., 733 F.3d 1323, 1329 (11th Cir. 2013)\n\n(relying on the “totality of facts” to determine the plausibility of an asserted intent to\n\nreturn to an ADA-noncompliant location).\n\n Griffin’s complaint does not satisfy the requirements of Nanni. The first\n\nrequirement, a past injury that is concrete and particular, is not met for reasons explained\n\nabove. And the second requirement is unmet because, unlike the plaintiff in Nanni,\n\nGriffin has not demonstrated that his intent to return to the Credit Union’s website is\n\nplausible. Indeed, there are reasons to think it is objectively implausible: why would an\n\nindividual with no hope of ever making use of the Credit Union’s services want to visit a\n\nwebsite describing those services? In short, Nanni could take advantage of the store’s\n\nwares and accommodations. Griffin, by contrast, is ineligible for perfectly neutral reasons\n\nto utilize the Credit Union’s services.\n\n Griffin points to his status as an ADA tester. It is true that tester status does not\n\ndestroy standing. Nanni, 878 F.3d at 457. But by the same token it cannot create standing\n\nin the absence of an otherwise plausible assertion that a return to the website would allow\n\n 11\n\nGriffin to avail himself of its services. Even in Houston v. Marod Supermarkets, a case\n\nrelied on heavily by Griffin, tester status, while a factor in favor of the plaintiff, was\n\ninsufficient to show a threat of future injury without more. 733 F.3d 1323, 1334 (11th\n\nCir. 2013). The Eleventh Circuit explained that the tester-plaintiff’s assertion that he\n\nwould return to the ADA-noncompliant supermarket was plausible only because, even\n\nthough it was not the closest market to his home, the plaintiff passed the store “regularly”\n\non his trips to Miami-Dade County. Id. at 1336. If, however the plaintiff “live[d]\n\nhundreds of miles away from the store with no particular reason to return” the facts “may\n\ndemand a different conclusion.” Id. Those are the facts here. Griffin may not live\n\nhundreds of miles away from the Credit Union, but the legal barriers between the two\n\nparties serve the same role as geographic ones. And those same legal barriers mean that\n\nGriffin has “no particular reason”—other than his role as a tester, which alone is\n\ninsufficient—to ever return.\n\n III.\n\n Our decision is not born of any lack of sympathy for people with visual\n\nimpairments. Those who do not suffer from impairments of this nature must be alert and\n\nsensitive to the formidable challenges such impairments impose on the navigation of\n\neveryday life. We must be sensitive as well to the wealth of talent that, before the passage\n\nof the ADA, was locked behind society’s unthinking exclusion of people with disabilities.\n\nWe thus recognize and respect the Americans with Disabilities Act’s transformative goal\n\nof “the elimination or reduction of physical and social structures that impede people with\n\nsome present, past, or perceived impairments from contributing, according to their\n\n 12\n\ntalents, to our Nation’s social, economic, and civic life.” Tennessee v. Lane, 541 U.S.\n\n509, 536 (2004) (Ginsburg, J., concurring).\n\n But to ignore the requirement of an injury in fact in this case would be to\n\ntransform constitutional standing into a null item. Spokeo requires a concrete and\n\nparticularized harm to find Article III standing, something greater than “a bare procedural\n\nviolation, divorced from any concrete harm.” 136 S. Ct. 1540, 1549 (2016). We are not at\n\nliberty to assail the basic principles of Spokeo here. Standing doctrine will doubtless pose\n\ncomplicated questions as it is applied to Internet-based harms in the future, but the case\n\nbefore us today is straightforward and narrow. Griffin is not a member of the Credit\n\nUnion, he is not eligible to become a member of the Credit Union, he has no plans to\n\nbecome eligible to be a member of the Credit Union, and no action we take could\n\npossibly make him eligible to become a member of the Credit Union. Under these\n\nspecific circumstances there can be no injury in fact. We have no occasion to consider\n\nhere, for example, a case brought by a similarly disabled individual who was eligible for\n\ncredit union membership in the defendant.\n\n This narrow holding stands in stark contrast to the broad position Griffin would\n\nhave us adopt. His argument admits of no limiting principle. If adopted, it would allow\n\nany aggrieved person to challenge any allegedly deficient website belonging to anyone in\n\nthe country. It would require us to open the courthouse doors to abstract and hypothetical\n\ncontroversies, in brazen violation of Supreme Court precedent.\n\n Five different district judges in Virginia alone have reached the same conclusion\n\nthat we reach here. See Carroll v. Roanoke Valley Community Federal Credit Union,\n\n 13\n\n2018 WL 2921106 (W.D. Va. June 11, 2018); Carroll v. 1st Advantage Federal Credit\n\nUnion, 2018 WL 2933411 (E.D. Va. April 9, 2018); Carroll v. Washington Gas Light\n\nFederal Credit Union, 2018 WL 2933412 (E.D. Va. April 4, 2018); Carroll v. ABNB\n\nFederal Credit Union, 2018 WL 1180317 (E.D. Va. March 5, 2018); Carroll v.\n\nNorthwest Federal Credit Union, 2018 WL 2933407 (E.D. Va. Jan. 26, 2018), adhered to\n\non reconsideration, 2018 WL 2933408 (E.D. Va. April 16, 2018). The Constitution\n\ncontemplates a crucial albeit limited role for the federal judiciary. Our trial court\n\ncolleagues’ fidelity to this vision betrays no lack of feeling, only the presence of a\n\nprofound respect for law.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 14", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355885/", "author_raw": "Quattlebaum joined. Judge King wrote an opinion concurring"}, {"author": "KING, Circuit Judge, concurring", "type": "concurrence", "text": "KING, Circuit Judge, concurring in the judgment:\n\n I write separately and concur in the determination of my fine colleagues to affirm\n\nthe district court. I agree with my friends that either a dignitary harm, or a harm in the\n\nform of the denial of access to information, can confer Article III standing under the\n\nAmericans with Disabilities Act of 1990, 42 U.S.C. § 12101 et seq. See Allen v. Wright,\n\n468 U.S. 737, 754-55 (1984) (recognizing that dignitary harm or stigmatic injury can\n\nconfer standing), abrogated on other grounds by Lexmark Int’l, Inc. v. Static Control\n\nComponents, Inc., 572 U.S. 118 (2014); Havens Realty Corp. v. Coleman, 455 U.S. 363,\n\n373-74 (1982) (concluding that “tester” had standing to pursue claim when deprived of\n\nstatutorily-required information). I disagree, however, that we need to assess and\n\ndelineate the boundaries of those principles.\n\n In my view, we should resolve this appeal by concluding only that the Complaint\n\nfails to sufficiently allege Griffin’s intent or plan to return to the Credit Union’s website,\n\nand that Griffin is therefore not entitled to the sole form of relief being sought, that is,\n\ninjunctive relief. See Nanni v. Aberdeen Marketplace, Inc., 878 F.3d 447, 455 (4th Cir.\n\n2017) (explaining that, to possess standing to seek injunctive relief, plaintiff must\n\nplausibly allege future injury). At bottom, the Complaint offers no plausible suggestion\n\nas to why Griffin would ever again visit the Credit Union’s website and suffer a future\n\ninjury. As I see it, that is all we need to say in order to decide his appeal.\n\n\n\n\n 15", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4355885/", "author_raw": "KING, Circuit Judge, concurring"}]}
WILKINSON
KING
QUATTLEBAUM
1
{}
3
0
0
2
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578632/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Clarence GRIFFIN, Plaintiff - Appellant, v. DEPARTMENT OF LABOR FEDERAL CREDIT UNION, A/K/A DOLFCU, Defendant - Appellee, National Association of Federally-Insured Credit Unions; Credit Union National Association, Amici Supporting Appellee.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-03\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1312\n\n\nCLARENCE GRIFFIN,\n\n Plaintiff – Appellant,\n\n v.\n\nDEPARTMENT OF LABOR FEDERAL CREDIT UNION, a/k/a DOLFCU,\n\n Defendant – Appellee,\n\n------------------------------\n\nNATIONAL ASSOCIATION OF FEDERALLY-INSURED CREDIT UNIONS;\nCREDIT UNION NATIONAL ASSOCIATION,\n\n Amici Supporting Appellee.\n\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. T.S. Ellis, III, Senior District Judge. (1:17-cv-01419-TSE-IDD)\n\n\nArgued: October 30, 2018 Decided: January 3, 2019\n\n\nBefore WILKINSON, KING, and QUATTLEBAUM, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge\n[END_CASE]", "role": "user" } ]
4,578,972
UNITED STATES of America, Plaintiff - Appellee, v. Thomas Anthony HAMMOND, Defendant - Appellant.
United States v. Thomas Hammond
2019-01-04
17-4702
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Agee, Keenan, Richardson", "parties": "", "opinions": [{"author": "BARBARA MILANO KEENAN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4702\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nTHOMAS ANTHONY HAMMOND,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the Western District of North Carolina,\nat Charlotte. Robert J. Conrad, Jr., District Judge. (3:17-cr-00044-RJC-DSC-1)\n\n\nArgued: November 1, 2018 Decided: January 4, 2019\n\n\nBefore AGEE, KEENAN, and RICHARDSON, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Keenan wrote the opinion, in which Judge Agee\nand Judge Richardson joined.\n\n\nARGUED: Ann Loraine Hester, FEDERAL DEFENDERS OF WESTERN NORTH\nCAROLINA, INC., Charlotte, North Carolina, for Appellant. Anthony Joseph Enright,\nOFFICE OF THE UNITED STATES ATTORNEY, Charlotte, North Carolina, for\nAppellee. ON BRIEF: Anthony Martinez, Federal Public Defender, FEDERAL\nDEFENDERS OF WESTERN NORTH CAROLINA, INC., Charlotte, North Carolina,\nfor Appellant. R. Andrew Murray, United States Attorney, OFFICE OF THE UNITED\nSTATES ATTORNEY, Charlotte, North Carolina, for Appellee.\n\fBARBARA MILANO KEENAN, Circuit Judge:\n\n In this appeal, we consider whether the offense of New York first-degree robbery,\n\nin violation of New York Penal Law § 160.15, qualifies as a “crime of violence” for\n\npurposes of the United States Sentencing Guidelines § 4B1.1 “career offender”\n\nenhancement. Thomas Anthony Hammond contends that the district court erred in\n\nsentencing him as a career offender, in part based on his prior conviction for that offense.\n\nAmong other things, Hammond argues that the crime of first-degree robbery under New\n\nYork law does not qualify as a crime of violence under the Guidelines’ “force clause.”\n\nWe disagree and, upon our review, conclude that New York statutory robbery,\n\nirrespective of the degree of the offense, is a crime of violence, because it necessarily\n\ninvolves the “use, attempted use, or threatened use of physical force against the person of\n\nanother.” U.S.S.G. § 4B1.2(a)(1). Accordingly, we affirm the district court’s judgment.\n\n\n\n I.\n\n In 2017, Hammond pleaded guilty to one count of attempted bank robbery and one\n\ncount of bank robbery, both in violation of 18 U.S.C. § 2113(a). Before sentencing, the\n\nprobation officer prepared a presentence report, which included a summary of\n\nHammond’s criminal history. The criminal history showed that Hammond previously\n\nhad been convicted of North Carolina common law robbery, and of New York first-\n\ndegree robbery, in violation of New York Penal Law § 160.15.\n\n Based on these convictions, the probation officer recommended that the district\n\ncourt impose the career offender sentencing enhancement under Guidelines § 4B1.1(a).\n\n 2\n\fApplying this enhancement, the probation officer calculated a Guidelines range of\n\nbetween 151 and 188 months’ imprisonment. Hammond contends that without the career\n\noffender enhancement, his advisory sentencing range would have been between 84 and\n\n105 months’ imprisonment.\n\n Hammond objected to his classification as a career offender, arguing that his\n\nconviction for New York first-degree robbery did not qualify as a crime of violence under\n\nthe Guidelines. 1 The district court rejected Hammond’s argument and imposed a\n\nsentence of 168 months’ imprisonment, followed by three years of supervised release.\n\nHammond now appeals.\n\n\n\n II.\n\n Hammond advances the same argument on appeal that he raised in the district\n\ncourt. Thus, we consider whether the offense of New York first-degree robbery, in\n\nviolation of New York Penal Law § 160.15, qualifies as a crime of violence within the\n\nmeaning of Guidelines § 4B1.1. This question presents an issue of law, which we review\n\nde novo. United States v. Jenkins, 631 F.3d 680, 682 (4th Cir. 2011).\n\n A.\n\n Before addressing Hammond’s arguments, we begin with an overview of the\n\nGuidelines’ career offender enhancement. Under Guidelines § 4B1.1, a defendant\n\n 1\n Because we have concluded that North Carolina common law robbery “qualifies\nas ‘robbery,’ as that term is used in U.S.S.G. § 4B1.2(a)(2),” Hammond concedes that his\nconviction for North Carolina common law robbery qualifies as a predicate offense under\nthe Guidelines. See United States v. Gattis, 877 F.3d 150, 160 (4th Cir. 2017).\n\n 3\n\fqualifies as a career offender if he has “at least two prior felony convictions for either a\n\ncrime of violence or a controlled substance offense.” U.S.S.G. § 4B1.1(a)(3). A “crime\n\nof violence” is defined as any state or federal offense punishable by imprisonment for a\n\nterm exceeding one year, that\n\n (1) has as an element the use, attempted use, or threatened use of physical\n force against the person of another [the force clause], or\n\n (2) is murder, voluntary manslaughter, kidnapping, aggravated assault, a\n forcible sex offense, robbery, arson, extortion or the use or unlawful\n possession of a firearm . . . or explosive material [the enumerated\n offense clause].\n\nId. § 4B1.2(a).\n\n We focus our analysis on the force clause of subparagraph (1) set forth above,\n\nbecause that clause provides the most direct route to answering the question before us.\n\nTo determine whether a conviction for a state offense is a crime of violence under the\n\nforce clause, we apply the “categorical approach.” United States v. Gardner, 823 F.3d\n\n793, 802 (4th Cir. 2016). Under that approach, the state crime necessarily must have as\n\nan element the “use, attempted use, or threatened use of physical force against the person\n\nof another” to qualify as a crime of violence under the force clause. U.S.S.G. §\n\n4B1.2(a)(1). The Supreme Court has interpreted the term “physical force” as “violent\n\nforce—that is, force capable of causing physical pain or injury to another person.”\n\nJohnson v. United States, 559 U.S. 133, 140 (2010). If the elements of the state offense\n\ncan be satisfied by “de minimis physical contact,” the offense does not qualify\n\ncategorically as a crime of violence. See United States v. Burns-Johnson, 864 F.3d 313,\n\n316 (4th Cir. 2017).\n\n 4\n\f In making this assessment, we review the elements of the offense and “the\n\nminimum conduct necessary for a violation” as defined by state law. See Gardner, 823\n\nF.3d at 803 (citation omitted). To determine the “minimum conduct” required for the\n\nstate offense, this Court must ensure that there is “a realistic probability, not a theoretical\n\npossibility, that a state would actually punish that conduct.” United States v. Doctor, 842\n\nF.3d 306, 308 (4th Cir. 2016) (internal quotation marks and citation omitted). With this\n\nframework in mind, we turn to consider Hammond’s arguments.\n\n B.\n\n Hammond raises two arguments in support of his contention that New York first-\n\ndegree robbery does not constitute a crime of violence. He contends (1) that New York\n\nrobbery, regardless of degree, does not include as an element the use of violent physical\n\nforce as defined by the Supreme Court, and (2) that New York first-degree robbery in\n\nparticular can be committed without the use of any force. We address each argument in\n\nturn.\n\n 1.\n\n Hammond first argues that New York robbery does not qualify categorically as a\n\ncrime of violence, because the offense does not require the use of violent physical force\n\n“capable of causing physical pain or injury to another person.” Johnson, 559 U.S. at 140.\n\nHe contends that New York courts have interpreted New York’s robbery statutes to\n\nrequire only de minimis force, such as “mere snatching.” We disagree with Hammond’s\n\nargument.\n\n\n\n 5\n\f At the outset, we note that this Court, in an unpublished decision, recently\n\nconcluded that New York second- and third-degree robbery constitute violent felonies\n\nunder the identically-worded force clause of the Armed Career Criminal Act (ACCA), 18\n\nU.S.C. § 924(e). United States v. Bowles, 733 F. App’x 699, 702 (4th Cir. 2018).\n\nBecause unpublished decisions may constitute persuasive, but not binding, authority, we\n\nindependently examine the New York statutes. See Collins v. Pond Creek Mining Co.,\n\n468 F.3d 213, 219 (4th Cir. 2006).\n\n New York has divided its robbery offense into three distinct statutes (the New\n\nYork robbery statutes), each involving an increasing degree of culpable conduct. N.Y.\n\nPenal Law §§ 160.00-160.15; see People v. Miller, 661 N.E.2d 1358, 1360-61 (N.Y.\n\n1995). All the New York robbery statutes, however, require the same element of force,\n\nnamely, “forcible stealing.” See N.Y. Penal Law § 160.00. Stated differently, the “core\n\ncrime” of New York robbery, irrespective of degree, is defined as “forcibly steal[ing]\n\nproperty.” Id.; Miller, 661 N.E.2d at 1360 (“The essence of the [New York] crime of\n\nrobbery is forcible stealing.”). Accordingly, if “forcible stealing” requires the use of\n\n“force capable of causing physical pain or injury,” Johnson, 559 U.S. at 140, the New\n\nYork robbery statutes all qualify as predicate offenses under the Guidelines’ force clause.\n\n A person “forcibly steals property” under New York law when\n\n in the course of committing a larceny, he uses or threatens the immediate\n use of physical force upon another person for the purpose of:\n\n 1. Preventing or overcoming resistance to the taking of the property or\n to the retention thereof immediately after the taking; or\n\n\n\n 6\n\f 2. Compelling the owner of such property or another person to deliver\n up the property or to engage in other conduct which aids in the commission\n of the larceny.\n\nN.Y. Penal Law § 160.00 (emphasis added). Although “physical force” in this context is\n\nnot defined, New York law gives common-law terms their common-law meanings, unless\n\ncontext suggests otherwise. People v. King, 463 N.E.2d 601, 603 (N.Y. 1984). “Physical\n\nforce” as used to define robbery under the common law has “long been understood to\n\nrequire violent force or intimidation of violent force.” Perez v. United States, 885 F.3d\n\n984, 988-89 (6th Cir. 2018) (citations omitted). Thus, the plain language of the New\n\nYork robbery statutes suggests that the use or threat of violent physical force is required\n\nfor all degrees of the offense. See United States v. Pereira-Gomez, 903 F.3d 155, 165 (2d\n\nCir. 2018) (“By its plain language . . . New York’s robbery statute includes as an element\n\nthe use of violent force.”).\n\n This interpretation is supported by New York case law applying the New York\n\nrobbery statutes. New York courts have interpreted “forcible stealing” to require\n\n“significantly more [force] than mere unwanted physical contact.” People v. Curet, 683\n\nN.Y.S.2d 602, 603 (N.Y. App. Div. 1998); see People v. Chatman, 833 N.Y.S.2d 794,\n\n795 (N.Y. App. Div. 2007) (affirming second-degree robbery conviction when the\n\ndefendant pushed the victim aside and entered her vehicle, later breaking the victim’s\n\nhold by driving away); People v. Dixon, 648 N.Y.S.2d 1009, 1010 (N.Y. App. Div. 1996)\n\n(concluding that evidence that a victim “experienced pain in her neck and suffered a\n\nscratch” as a result of the defendant pulling the victim’s necklaces was sufficient to\n\nsupport the defendant’s conviction for third-degree robbery). Indeed, New York courts\n\n 7\n\fconsistently have reversed robbery convictions when the taking at issue was committed\n\nwithout the use or threat of significant physical force. See, e.g., People v. Dobbs, 805\n\nN.Y.S.2d 734, 735-36 (N.Y. App. Div. 2005) (affirming reduction in charge from third-\n\ndegree robbery to petit larceny because there was “no indication” that the victim was\n\nthreatened or injured by the defendant); People v. Middleton, 623 N.Y.S.2d 298, 299\n\n(N.Y. App. Div. 1995) (reversing a third-degree robbery conviction when the victim was\n\nnot “intimidated, knocked down, struck, or injured”). Thus, we do not discern any\n\nmaterial difference between the amount of force required under the New York robbery\n\nstatutes and the violent physical force necessary to satisfy the Guidelines’ force clause.\n\nSee Johnson, 559 U.S. at 142 (recognizing that violent force requires more than “a mere\n\nunwanted touching”).\n\n Contrary to Hammond’s contention, the great weight of New York authority\n\nestablishes that the act of merely “snatching” property from a victim does not amount to\n\n“forcibly steal[ing] property” from a person. See, e.g., People v. Chessman, 429\n\nN.Y.S.2d 224, 227-29 (N.Y. App. Div. 1980) (holding that a purse snatching when the\n\nvictim “did not feel anything on her body” did not constitute third-degree robbery under\n\nNew York law); People v. Davis, 418 N.Y.S.2d 127, 128 (N.Y. App. Div. 1979)\n\n(concluding that a purse snatching did not amount to third-degree robbery in the absence\n\nof evidence that the victim “was injured or was in danger of injury”). Indeed, the New\n\nYork Court of Appeals recently stated that “a taking ‘by sudden or stealthy seizure or\n\nsnatching,’” such as “pickpocketing” or “jostling” a victim, is insufficient to support a\n\nconviction for New York second-degree robbery. People v. Jurgins, 46 N.E.3d 1048,\n\n 8\n\f1052-53 (N.Y. 2015). Based on the foregoing, we conclude that all the New York\n\nrobbery statutes have as an element the use or threatened use of violent physical force\n\nsufficient to satisfy the force clause of Guidelines § 4B2.1(a)(1). 2\n\n Notably, none of the decisions on which Hammond relies suggests a different\n\nresult. Hammond first cites to a decision in which a defendant and a victim had “tugged\n\nat each other” until the defendant was able to pull his hand away. People v. Safon, 560\n\nN.Y.S.2d 552, 552 (N.Y. App. Div. 1990). The court in Safon concluded that the\n\ninteraction between the defendant and the victim was sufficient to uphold a conviction for\n\nNew York third-degree robbery. Id.\n\n We recognize that an offense that requires only a “slight degree of force” does not\n\nqualify as a crime of violence under the Guidelines’ force clause. See United States v.\n\nWinston, 850 F.3d 677, 685 (4th Cir. 2017) (internal quotation marks and citation\n\nomitted). Nonetheless, the Supreme Court has emphasized that, to constitute a crime of\n\nviolence, a state offense need only require force that is “capable of causing physical pain\n\nor injury,” such as a “slap in the face.” Johnson, 559 U.S. at 140, 143 (emphasis added).\n\nIf a slap constitutes enough physical force to satisfy Johnson, we cannot say that a pull,\n\n\n 2\n We note that our conclusion is consistent with the majority of courts of appeals\nto consider whether the New York robbery statutes require, as an element, the use or\nthreatened use of violent physical force. See United States v. Pereira-Gomez, 903 F.3d\n155, 166 (2d Cir. 2018) (concluding that New York second-degree robbery qualifies as a\ncrime of violence under Section 2L1.2 of the Guidelines); United States v. Williams, 899\nF.3d 659, 663-65 (8th Cir. 2018) (same); Perez, 855 F.3d at 989 (holding that New York\nsecond-degree robbery qualifies as a violent felony for purposes of the ACCA). But see\nUnited States v. Steed, 879 F.3d 440, 448-50 (1st Cir. 2018) (concluding that New York\nsecond-degree robbery is not a crime of violence under Guidelines § 4B2.1(a)).\n\n 9\n\fpowerful enough to break a person’s grip, would not be “capable of causing physical\n\npain.” 3 Id. at 140.\n\n Hammond next cites to a New York state case in which the defendant and three\n\nothers “formed a human wall that blocked the victim’s path as the victim attempted to\n\npursue” the defendant, who had “picked” the victim’s “pocket,” People v. Bennett, 631\n\nN.Y.S.2d 834, 834 (N.Y. App. Div. 1995), and to another case in which the defendant\n\nphysically “block[ed] the victim’s passage,” People v. Patton, 585 N.Y.S.2d 431, 431\n\n(N.Y. App. Div. 1992). Hammond contends that because there was no actual force\n\nemployed against the victims in those cases, yet the defendants were convicted of New\n\nYork second-degree robbery, the decisions in Bennett and Patton demonstrate that\n\n“forcible stealing” can be committed without any use or threatened use of force.\n\n Hammond, however, minimizes the defendants’ conduct in those cases. In Patton,\n\nthe defendant not only blocked the victim’s path, but “persistently shoved [the victim]\n\nback” multiple times. Id. The codefendant in that case also stole the victim’s gold chain\n\nby “yank[ing]” it from the victim’s neck, “scratching the victim and tearing his shirt.” Id.\n\n\n 3\n We disagree with Hammond’s argument that this Court’s decisions in Winston,\n850 F.3d 677, and Gardner, 823 F.3d 793, require a different result here. In Winston and\nGardner, we considered whether Virginia’s and North Carolina’s respective common law\nrobbery crimes constituted “violent felonies” under the ACCA. See Winston, 850 F.3d at\n685; Gardner, 823 F.3d at 803-04. Based on each states’ interpretation of its own\nrobbery offense, we concluded that each respective crime could be committed without the\nforce required by the Supreme Court. See Winston, 850 F.3d at 685; Gardner, 823 F.3d\nat 803-04. We conduct the same analysis in the present case, applying the same legal\nstandards. That we reach a different conclusion based on New York courts’\ninterpretation of the New York robbery statutes does not create a tension among our\ncases.\n\n 10\n\fTaken as a whole, the conduct at issue in Patton plainly involved the use or threatened\n\nuse of violent physical force.\n\n With respect to Bennett, Hammond correctly observes that the defendant in that\n\ncase did not use actual force against the victim. Nonetheless, Hammond fails to\n\nrecognize that the defendant’s action with others of forming the “human wall” involved\n\nthe “threatened use of physical force.” See Bennett, 631 N.Y.S.2d at 834. Stated\n\ndifferently, the actions of the defendant and his accomplices involved a threat of violent\n\nforce that dissuaded the victim from attempting to break through the human wall or\n\notherwise to pursue the defendant. Accord Pereira-Gomez, 903 F.3d at 166; Perez, 885\n\nF.3d at 989-90. Because the Guidelines’ force clause includes the “threatened use of\n\nphysical force,” U.S.S.G. § 4B2.1(a)(1), the cases on which Hammond relies involve a\n\ndegree of threatened force sufficient to come within the scope of the Guidelines’ career\n\noffender enhancement.\n\n 2.\n\n In a related argument, Hammond contends that, regardless of New York’s\n\nstatutory definition of robbery, New York first-degree robbery is not a crime of violence\n\nbecause that statute can be violated by merely possessing, without displaying, a deadly\n\nweapon. See N.Y. Penal Law § 160.15(2) (“A person is guilty of robbery in the first\n\ndegree when he forcibly steals property and when . . . [he] is armed with a deadly\n\nweapon.”). However, Hammond misconstrues New York’s first-degree robbery statute.\n\n As we have explained, the New York robbery statutes all require that the\n\nprosecution prove the same element of “forcible stealing.” See People v. Gordon, 16\n\n 11\n\fN.E.3d 1178, 1183-84 (N.Y. 2014). A person is guilty of New York first-degree robbery\n\nwhen he “forcibly steals property,” as defined in New York Penal Law § 160.00, and his\n\nconduct satisfies one of four additional aggravating circumstances, such as being armed\n\nwith a deadly weapon. 4 See N.Y. Penal Law § 160.15. Thus, anyone convicted of New\n\nYork first-degree robbery necessarily has been convicted of “us[ing] or threaten[ing] the\n\nimmediate use of physical force upon another person.” Id. § 160.00; see Miller, 661\n\nN.E.2d at 1360-62.\n\n The aggravating factors necessary to commit New York first-degree robbery do\n\nnot eliminate the “core” physical force element of New York robbery, but merely elevate\n\nthe crime based on additional culpable conduct. See Miller, 661 N.E.2d at 1360-61; see\n\nalso Perez, 885 F.3d at 988. Accordingly, because all the New York robbery statutes\n\nrequire the same element of violent physical force or threatened violent force, New York\n\nfirst-degree robbery qualifies as a crime of violence under Guidelines § 4B1.2(a)(1). 5\n\n\n\n\n 4\n The other aggravating circumstances are when the defendant: (1) “[c]auses\nserious physical injury to any person who is not a participant in the crime;” (2) “[u]ses or\nthreatens the immediate use of a dangerous instrument;” or (3) displays certain types of\noperable firearms. N.Y. Penal Law § 160.15.\n 5\n For the same reason, we reject Hammond’s contention that we must apply the\nmodified categorical approach to New York’s first-degree robbery statute. The modified\ncategorical approach is not required when each of the crimes into which a statute may be\ndivided constitutes a crime of violence. See United States v. Cabrera-Umanzor, 728 F.3d\n347, 352 (4th Cir. 2013) (citing Descamps v. United States, 570 U.S. 254, 264 (2013)).\nBecause we conclude that all subsections of New York first-degree robbery qualify as\ncrimes of violence, we need not apply the modified categorical approach.\n\n 12\n\f III.\n\n For these reasons, we hold that Hammond’s conviction for New York first-degree\n\nrobbery qualifies as a crime of violence under the force clause of Guidelines §\n\n4B1.2(a)(1). 6 We therefore affirm the district court’s judgment.\n\n AFFIRMED\n\n\n\n\n 6\n Based on our holding, we need not address Hammond’s alternative argument\nconcerning whether New York first-degree robbery qualifies as a crime of violence under\nthe “enumerated offense” clause of Guidelines § 4B1.2(a)(2).\n\n\n 13", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356225/", "author_raw": "BARBARA MILANO KEENAN, Circuit Judge:"}]}
AGEE
KEENAN
RICHARDSON
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4578972/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff - Appellee, v. Thomas Anthony HAMMOND, Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-04\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4702\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nTHOMAS ANTHONY HAMMOND,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the Western District of North Carolina,\nat Charlotte. Robert J. Conrad, Jr., District Judge. (3:17-cr-00044-RJC-DSC-1)\n\n\nArgued: November 1, 2018 Decided: January 4, 2019\n\n\nBefore AGEE, KEENAN, and RICHARDSON, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Keenan wrote the opinion, in which Judge Agee\nand Judge Richardson joined.\n\n\nARGUED: Ann Loraine Hester, FEDERAL DEFENDERS OF WESTERN NORTH\nCAROLINA, INC., Charlotte, North Carolina, for Appellant. Anthony Joseph Enright,\nOFFICE OF THE UNITED STATES ATTORNEY, Charlotte, North Carolina, for\nAppellee. ON BRIEF: Anthony Martinez, Federal Public Defender, FEDERAL\nDEFENDERS OF WESTERN NORTH CAROLINA, INC., Charlotte, North Carolina,\nfor Appellant. R. Andrew Murray, United States Attorney, OFFICE OF THE UNITED\nSTATES ATTORNEY, Charlotte, North Carolina, for Appellee.\n\fBARBARA MILANO KEENAN, Circuit Judge:\n\n In this appeal, we consider whether the offense of New York first-degree robbery,\n\nin violation of New York Penal Law § 160.15, qualifies as a “crime of violence” for\n\npurposes of the United States Sentencing Guidelines § 4B1.1 “career offender”\n\nenhancement. Thomas Anthony Hammond contends that the district court erred in\n\nsentencing him as a career offender, in part based on his prior conviction for that offense.\n\nAmong other things, Hammond argues that the crime of first-degree robbery under New\n\nYork law does not qualify as a crime of violence under the Guidelines’ “force clause.”\n\nWe disagree and, upon our review, conclude that New York statutory robbery,\n\nirrespective of the degree of the offense, is a crime of violence, because it necessarily\n\ninvolves the “use, attempted use, or threatened use of physical force against the person of\n\nanother.” U.S.S.G. § 4B1.2(a)(1). Accordingly, we affirm the district court’s judgment.\n\n\n\n I.\n\n In 2017, Hammond pleaded guilty to one count of attempted bank robbery and one\n\ncount of bank robbery, both in violation of 18 U.S.C. § 2113(a). Before sentencing, the\n\nprobation officer prepared a presentence report, which included a summary of\n\nHammond’s criminal history. The criminal history showed that Hammond previously\n\nhad been convicted of North Carolina common law robbery, and of New York first-\n\ndegree robbery, in violation of New York Penal Law § 160.15.\n\n Based on these convictions, the probation officer recommended that the district\n\ncourt impose the career offender sentencing enhancement under Guidelines § 4B1.1(a).\n\n 2\n\fApplying this enhancement, the probation officer calculated a Guidelines range of\n\nbetween 151 and 188 months’ imprisonment. Hammond contends that without the career\n\noffender enhancement, his advisory sentencing range would have been between 84 and\n\n105 months’ imprisonment.\n\n Hammond objected to his classification as a career offender, arguing that his\n\nconviction for New York first-degree robbery did not qualify as a crime of violence under\n\nthe Guidelines. 1 The district court rejected Hammond’s argument and imposed a\n\nsentence of 168 months’ imprisonment, followed by three years of supervised release.\n\nHammond now appeals.\n\n\n\n II.\n\n Hammond advances the same argument on appeal that he raised in the district\n\ncourt. Thus, we consider whether the offense of New York first-degree robbery, in\n\nviolation of New York Penal Law § 160.15, qualifies as a crime of violence within the\n\nmeaning of Guidelines § 4B1.1. This question presents an issue of law, which we review\n\nde novo. United States v. Jenkins, 631 F.3d 680, 682 (4th Cir. 2011).\n\n A.\n\n Before addressing Hammond’s arguments, we begin with an overview of the\n\nGuidelines’ career offender enhancement. Under Guidelines § 4B1.1, a defendant\n\n 1\n Because we have concluded that North Carolina common law robbery “qualifies\nas ‘robbery,’ as that term is used in U.S.S.G. § 4B1.2(a)(2),” Hammond concedes that his\nconviction for North Carolina common law robbery qualifies as a predicate offense under\nthe Guidelines. See United States v. Gattis, 877 F.3d 150, 160 (4th Cir. 2017).\n\n 3\n\fqualifies as a career offender if he has “at least two prior felony convictions for either a\n\ncrime of violence or a controlled substance offense.” U.S.S.G. § 4B1.1(a)(3). A “crime\n\nof violence” is defined as any state or federal offense punishable by imprisonment for a\n\nterm exceeding one year, that\n\n (1) has as an element the use, attempted use, or threatened use of physical\n force against the person of another [the force clause], or\n\n (2) is murder, voluntary manslaughter, kidnapping, aggravated assault, a\n forcible sex offense, robbery, arson, extortion or the use or unlawful\n possession of a firearm . . . or explosive material [the enumerated\n offense clause].\n\nId. § 4B1.2(a).\n\n We focus our analysis on the force clause of subparagraph (1) set forth above,\n\nbecause that clause provides the most direct route to answering the question before us.\n\nTo determine whether a conviction for a state offense is a crime of violence under the\n\nforce clause, we apply the “categorical approach.” United States v. Gardner, 823 F.3d\n\n793, 802 (4th Cir. 2016). Under that approach, the state crime necessarily must have as\n\nan element the “use, attempted use, or threatened use of physical force against the person\n\nof another” to qualify as a crime of violence under the force clause. U.S.S.G. §\n\n4B1.2(a)(1). The Supreme Court has interpreted the term “physical force” as “violent\n\nforce—that is, force capable of causing physical pain or injury to another person.”\n\nJohnson v. United States, 559 U.S. 133, 140 (2010). If the elements of the state offense\n\ncan be satisfied by “de minimis physical contact,” the offense does not qualify\n\ncategorically as a crime of violence. See United States v. Burns-Johnson, 864 F.3d 313,\n\n316 (4th Cir. 2017).\n\n 4\n\f In making this assessment, we review the elements of the offense and “the\n\nminimum conduct necessary for a violation” as defined by state law. See Gardner, 823\n\nF.3d at 803 (citation omitted). To determine the “minimum conduct” required for the\n\nstate offense, this Court must ensure that there is “a realistic probability, not a theoretical\n\npossibility, that a state would actually punish that conduct.” United States v. Doctor, 842\n\nF.3d 306, 308 (4th Cir. 2016) (internal quotation marks and citation omitted). With this\n\nframework in mind, we turn to consider Hammond’s arguments.\n\n B.\n\n Hammond raises two arguments in support of his contention that New York first-\n\ndegree robbery does not constitute a crime of violence. He contends (1) that New York\n\nrobbery, regardless of degree, does not include as an element the use of violent physical\n\nforce as defined by the Supreme Court, and (2) that New York first-degree robbery in\n\nparticular can be committed without the use of any force. We address each argument in\n\nturn.\n\n 1.\n\n Hammond first argues that New York robbery does not qualify categorically as a\n\ncrime of violence, because the offense does not require the use of violent physical force\n\n“capable of causing physical pain or injury to another person.” Johnson, 559 U.S. at 140.\n\nHe contends that New York courts have interpreted New York’s robbery statutes to\n\nrequire only de minimis force, such as “mere snatching.” We disagree with Hammond’s\n\nargument.\n\n\n\n 5\n\f At the outset, we note that this Court, in an unpublished decision, recently\n\nconcluded that New York second- and third-degree robbery constitute violent felonies\n\nunder the identically-worded force clause of the Armed Career Criminal Act (ACCA), 18\n\nU.S.C. § 924(e). United States v. Bowles, 733 F. App’x 699, 702 (4th Cir. 2018).\n\nBecause unpublished decisions may constitute persuasive, but not binding, authority, we\n\nindependently examine the New York statutes. See Collins v. Pond Creek Mining Co.,\n\n468 F.3d 213, 219 (4th Cir. 2006).\n\n New York has divided its robbery offense into three distinct statutes (the New\n\nYork robbery statutes), each involving an increasing degree of culpable conduct. N.Y.\n\nPenal Law §§ 160.00-160.15; see People v. Miller, 661 N.E.2d 1358, 1360-61 (N.Y.\n\n1995). All the New York robbery statutes, however, require the same element of force,\n\nnamely, “forcible stealing.” See N.Y. Penal Law § 160.00. Stated differently, the “core\n\ncrime” of New York robbery, irrespective of degree, is defined as “forcibly steal[ing]\n\nproperty.” Id.; Miller, 661 N.E.2d at 1360 (“The essence of the [New York] crime of\n\nrobbery is forcible stealing.”). Accordingly, if “forcible stealing” requires the use of\n\n“force capable of causing physical pain or injury,” Johnson, 559 U.S. at 140, the New\n\nYork robbery statutes all qualify as predicate offenses under the Guidelines’ force clause.\n\n A person “forcibly steals property” under New York law when\n\n in the course of committing a larceny, he uses or threatens the immediate\n use of physical force upon another person for the purpose of:\n\n 1. Preventing or overcoming resistance to the taking of the property or\n to the retention thereof immediately after the taking; or\n\n\n\n 6\n\f 2. Compelling the owner of such property or another person to deliver\n up the property or to engage in other conduct which aids in the commission\n of the larceny.\n\nN.Y. Penal Law § 160.00 (emphasis added). Although “physical force” in this context is\n\nnot defined, New York law gives common-law terms their common-law meanings, unless\n\ncontext suggests otherwise. People v. King, 463 N.E.2d 601, 603 (N.Y. 1984). “Physical\n\nforce” as used to define robbery under the common law has “long been understood to\n\nrequire violent force or intimidation of violent force.” Perez v. United States, 885 F.3d\n\n984, 988-89 (6th Cir. 2018) (citations omitted). Thus, the plain language of the New\n\nYork robbery statutes suggests that the use or threat of violent physical force is required\n\nfor all degrees of the offense. See United States v. Pereira-Gomez, 903 F.3d 155, 165 (2d\n\nCir. 2018) (“By its plain language . . . New York’s robbery statute includes as an element\n\nthe use of violent force.”).\n\n This interpretation is supported by New York case law applying the New York\n\nrobbery statutes. New York courts have interpreted “forcible stealing” to require\n\n“significantly more [force] than mere unwanted physical contact.” People v. Curet, 683\n\nN.Y.S.2d 602, 603 (N.Y. App. Div. 1998); see People v. Chatman, 833 N.Y.S.2d 794,\n\n795 (N.Y. App. Div. 2007) (affirming second-degree robbery conviction when the\n\ndefendant pushed the victim aside and entered her vehicle, later breaking the victim’s\n\nhold by driving away); People v. Dixon, 648 N.Y.S.2d 1009, 1010 (N.Y. App. Div. 1996)\n\n(concluding that evidence that a victim “experienced pain in her neck and suffered a\n\nscratch” as a result of the defendant pulling the victim’s necklaces was sufficient to\n\nsupport the defendant’s conviction for third-degree robbery). Indeed, New York courts\n\n 7\n\fconsistently have reversed robbery convictions when the taking at issue was committed\n\nwithout the use or threat of significant physical force. See, e.g., People v. Dobbs, 805\n\nN.Y.S.2d 734, 735-36 (N.Y. App. Div. 2005) (affirming reduction in charge from third-\n\ndegree robbery to petit larceny because there was “no indication” that the victim was\n\nthreatened or injured by the defendant); People v. Middleton, 623 N.Y.S.2d 298, 299\n\n(N.Y. App. Div. 1995) (reversing a third-degree robbery conviction when the victim was\n\nnot “intimidated, knocked down, struck, or injured”). Thus, we do not discern any\n\nmaterial difference between the amount of force required under the New York robbery\n\nstatutes and the violent physical force necessary to satisfy the Guidelines’ force clause.\n\nSee Johnson, 559 U.S. at 142 (recognizing that violent force requires more than “a mere\n\nunwanted touching”).\n\n Contrary to Hammond’s contention, the great weight of New York authority\n\nestablishes that the act of merely “snatching” property from a victim does not amount to\n\n“forcibly steal[ing] property” from a person. See, e.g., People v. Chessman, 429\n\nN.Y.S.2d 224, 227-29 (N.Y. App. Div. 1980) (holding that a purse snatching when the\n\nvictim “did not feel anything on her body” did not constitute third-degree robbery under\n\nNew York law); People v. Davis, 418 N.Y.S.2d 127, 128 (N.Y. App. Div. 1979)\n\n(concluding that a purse snatching did not amount to third-degree robbery in the absence\n\nof evidence that the victim “was injured or was in danger of injury”). Indeed, the New\n\nYork Court of Appeals recently stated that “a taking ‘by sudden or stealthy seizure or\n\nsnatching,’” such as “pickpocketing” or “jostling” a victim, is insufficient to support a\n\nconviction for New York second-degree robbery. People v. Jurgins, 46 N.E.3d 1048,\n\n 8\n\f1052-53 (N.Y. 2015). Based on the foregoing, we conclude that all the New York\n\nrobbery statutes have as an element the use or threatened use of violent physical force\n\nsufficient to satisfy the force clause of Guidelines § 4B2.1(a)(1). 2\n\n Notably, none of the decisions on which Hammond relies suggests a different\n\nresult. Hammond first cites to a decision in which a defendant and a victim had “tugged\n\nat each other” until the defendant was able to pull his hand away. People v. Safon, 560\n\nN.Y.S.2d 552, 552 (N.Y. App. Div. 1990). The court in Safon concluded that the\n\ninteraction between the defendant and the victim was sufficient to uphold a conviction for\n\nNew York third-degree robbery. Id.\n\n We recognize that an offense that requires only a “slight degree of force” does not\n\nqualify as a crime of violence under the Guidelines’ force clause. See United States v.\n\nWinston, 850 F.3d 677, 685 (4th Cir. 2017) (internal quotation marks and citation\n\nomitted). Nonetheless, the Supreme Court has emphasized that, to constitute a crime of\n\nviolence, a state offense need only require force that is “capable of causing physical pain\n\nor injury,” such as a “slap in the face.” Johnson, 559 U.S. at 140, 143 (emphasis added).\n\nIf a slap constitutes enough physical force to satisfy Johnson, we cannot say that a pull,\n\n\n 2\n We note that our conclusion is consistent with the majority of courts of appeals\nto consider whether the New York robbery statutes require, as an element, the use or\nthreatened use of violent physical force. See United States v. Pereira-Gomez, 903 F.3d\n155, 166 (2d Cir. 2018) (concluding that New York second-degree robbery qualifies as a\ncrime of violence under Section 2L1.2 of the Guidelines); United States v. Williams, 899\nF.3d 659, 663-65 (8th Cir. 2018) (same); Perez, 855 F.3d at 989 (holding that New York\nsecond-degree robbery qualifies as a violent felony for purposes of the ACCA). But see\nUnited States v. Steed, 879 F.3d 440, 448-50 (1st Cir. 2018) (concluding that New York\nsecond-degree robbery is not a crime of violence under Guidelines § 4B2.1(a)).\n\n 9\n\fpowerful enough to break a person’s grip, would not be “capable of causing physical\n\npain.” 3 Id. at 140.\n\n Hammond next cites to a New York state case in which the defendant and three\n\nothers “formed a human wall that blocked the victim’s path as the victim attempted to\n\npursue” the defendant, who had “picked” the victim’s “pocket,” People v. Bennett, 631\n\nN.Y.S.2d 834, 834 (N.Y. App. Div. 1995), and to another case in which the defendant\n\nphysically “block[ed] the victim’s passage,” People v. Patton, 585 N.Y.S.2d 431, 431\n\n(N.Y. App. Div. 1992). Hammond contends that because there was no actual force\n\nemployed against the victims in those cases, yet the defendants were convicted of New\n\nYork second-degree robbery, the decisions in Bennett and Patton demonstrate that\n\n“forcible stealing” can be committed without any use or threatened use of force.\n\n Hammond, however, minimizes the defendants’ conduct in those cases. In Patton,\n\nthe defendant not only blocked the victim’s path, but “persistently shoved [the victim]\n\nback” multiple times. Id. The codefendant in that case also stole the victim’s gold chain\n\nby “yank[ing]” it from the victim’s neck, “scratching the victim and tearing his shirt.” Id.\n\n\n 3\n We disagree with Hammond’s argument that this Court’s decisions in Winston,\n850 F.3d 677, and Gardner, 823 F.3d 793, require a different result here. In Winston and\nGardner, we considered whether Virginia’s and North Carolina’s respective common law\nrobbery crimes constituted “violent felonies” under the ACCA. See Winston, 850 F.3d at\n685; Gardner, 823 F.3d at 803-04. Based on each states’ interpretation of its own\nrobbery offense, we concluded that each respective crime could be committed without the\nforce required by the Supreme Court. See Winston, 850 F.3d at 685; Gardner, 823 F.3d\nat 803-04. We conduct the same analysis in the present case, applying the same legal\nstandards. That we reach a different conclusion based on New York courts’\ninterpretation of the New York robbery statutes does not create a tension among our\ncases.\n\n 10\n\fTaken as a whole, the conduct at issue in Patton plainly involved the use or threatened\n\nuse of violent physical force.\n\n With respect to Bennett, Hammond correctly observes that the defendant in that\n\ncase did not use actual force against the victim. Nonetheless, Hammond fails to\n\nrecognize that the defendant’s action with others of forming the “human wall” involved\n\nthe “threatened use of physical force.” See Bennett, 631 N.Y.S.2d at 834. Stated\n\ndifferently, the actions of the defendant and his accomplices involved a threat of violent\n\nforce that dissuaded the victim from attempting to break through the human wall or\n\notherwise to pursue the defendant. Accord Pereira-Gomez, 903 F.3d at 166; Perez, 885\n\nF.3d at 989-90. Because the Guidelines’ force clause includes the “threatened use of\n\nphysical force,” U.S.S.G. § 4B2.1(a)(1), the cases on which Hammond relies involve a\n\ndegree of threatened force sufficient to come within the scope of the Guidelines’ career\n\noffender enhancement.\n\n 2.\n\n In a related argument, Hammond contends that, regardless of New York’s\n\nstatutory definition of robbery, New York first-degree robbery is not a crime of violence\n\nbecause that statute can be violated by merely possessing, without displaying, a deadly\n\nweapon. See N.Y. Penal Law § 160.15(2) (“A person is guilty of robbery in the first\n\ndegree when he forcibly steals property and when . . . [he] is armed with a deadly\n\nweapon.”). However, Hammond misconstrues New York’s first-degree robbery statute.\n\n As we have explained, the New York robbery statutes all require that the\n\nprosecution prove the same element of “forcible stealing.” See People v. Gordon, 16\n\n 11\n\fN.E.3d 1178, 1183-84 (N.Y. 2014). A person is guilty of New York first-degree robbery\n\nwhen he “forcibly steals property,” as defined in New York Penal Law § 160.00, and his\n\nconduct satisfies one of four additional aggravating circumstances, such as being armed\n\nwith a deadly weapon. 4 See N.Y. Penal Law § 160.15. Thus, anyone convicted of New\n\nYork first-degree robbery necessarily has been convicted of “us[ing] or threaten[ing] the\n\nimmediate use of physical force upon another person.” Id. § 160.00; see Miller, 661\n\nN.E.2d at 1360-62.\n\n The aggravating factors necessary to commit New York first-degree robbery do\n\nnot eliminate the “core” physical force element of New York robbery, but merely elevate\n\nthe crime based on additional culpable conduct. See Miller, 661 N.E.2d at 1360-61; see\n\nalso Perez, 885 F.3d at 988. Accordingly, because all the New York robbery statutes\n\nrequire the same element of violent physical force or threatened violent force, New York\n\nfirst-degree robbery qualifies as a crime of violence under Guidelines § 4B1.2(a)(1). 5\n\n\n\n\n 4\n The other aggravating circumstances are when the defendant: (1) “[c]auses\nserious physical injury to any person who is not a participant in the crime;” (2) “[u]ses or\nthreatens the immediate use of a dangerous instrument;” or (3) displays certain types of\noperable firearms. N.Y. Penal Law § 160.15.\n 5\n For the same reason, we reject Hammond’s contention that we must apply the\nmodified categorical approach to New York’s first-degree robbery statute. The modified\ncategorical approach is not required when each of the crimes into which a statute may be\ndivided constitutes a crime of violence. See United States v. Cabrera-Umanzor, 728 F.3d\n347, 352 (4th Cir. 2013) (citing Descamps v. United States, 570 U.S. 254, 264 (2013)).\nBecause we conclude that all subsections of New York first-degree robbery qualify as\ncrimes of violence, we need not apply the modified categorical approach.\n\n 12\n\f III.\n\n For these reasons, we hold that Hammond’s conviction for New York first-degree\n\nrobbery qualifies as a crime of violence under the force clause of Guidelines §\n\n4B1.2(a)(1). 6 We therefore affirm the district court’s judgment.\n\n AFFIRMED\n\n\n\n\n 6\n Based on our holding, we need not address Hammond’s alternative argument\nconcerning whether New York first-degree robbery qualifies as a crime of violence under\nthe “enumerated offense” clause of Guidelines § 4B1.2(a)(2).\n\n\n 13\n[END_CASE]", "role": "user" } ]
4,579,294
UNITED STATES of America, Plaintiff - Appellee, v. Gary Giovon LYNN, Defendant - Appellant.
United States v. Gary Giovon Lynn
2019-01-07
17-4232
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Motz, Floyd, Jones, Western, Virginia", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887832/", "author_raw": ""}, {"author": "", "type": "035concurrenceinpart", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887833/", "author_raw": ""}, {"type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4232\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nGARY GIOVON LYNN,\n\n Defendant - Appellant.\n\n\n\nAppeal from the United States District Court for the Middle District of North Carolina, at\nGreensboro. William L. Osteen, Jr., District Judge. (1:16-cr-00287-WO-1)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n\n\nBefore MOTZ and FLOYD, Circuit Judges, and James P. JONES, United States District\nJudge for the Western District of Virginia, sitting by designation.\n\n\nAffirmed by published opinion. Judge Jones wrote the majority opinion, in which Judge\nMotz joined. Judge Floyd wrote a separate opinion, in which he concurred in part and\ndissented in part.\n\n\nARGUED: John Arthur Duberstein, OFFICE OF THE FEDERAL PUBLIC\nDEFENDER, Greensboro, North Carolina, for Appellant. Kimberly Furr Davis, OFFICE\nOF THE UNITED STATES ATTORNEY, Winston-Salem, North Carolina, for\nAppellee. ON BRIEF: Louis C. Allen, Federal Public Defender, OFFICE OF THE\nFEDERAL PUBLIC DEFENDER, Greensboro, North Carolina, for Appellant. Matthew\nG.T. Martin, United States Attorney, OFFICE OF THE UNITED STATES ATTORNEY,\n\nGreensboro, North Carolina, for Appellee.\n\n\n\n\n 2\n\nJONES, District Judge:\n\n Gary Giovon Lynn pled guilty to being a felon in possession of a firearm, in\n\nviolation of 18 U.S.C. §§ 922(g)(l), 924(a)(2). The district court sentenced Lynn to 120\n\nmonths’ imprisonment. On appeal, counsel filed a brief pursuant to Anders v. California,\n\n386 U.S. 738 (1967), questioning whether the district court erred in applying a cross-\n\nreference to the attempted murder Sentencing Guideline. U.S. Sentencing Guidelines\n\nManual (USSG) §§ 2A2.1, 2K2.1(c)(l)(A), 2X1.l(a) (2016). We directed supplemental\n\nbriefing on the additional issue of whether in light of USSG § 5G3.1(c), the district court\n\nerred in failing to impose its sentence to run concurrently with an anticipated term of\n\nstate imprisonment. We now affirm the district court’s judgment.\n\n I.\n\n On January 4, 2016, Officer A.D. Gardner of the Winston-Salem Police\n\nDepartment stopped a speeding vehicle occupied by Lynn along with two other\n\nindividuals. While standing near the vehicle, Officer Gardner smelled marijuana, and he\n\nrequested additional officers for assistance. When the other officers arrived, Officer\n\nGardner asked each of the occupants to exit the vehicle. After Officer Gardner frisked\n\nLynn, Gardner instructed him to stand by a guardrail with the driver of the vehicle. As\n\nOfficer Nicholas Powell was frisking another passenger, Lynn jumped into the driver’s\n\nside of the vehicle and Officer Powell followed, landing on top of him. The two\n\nstruggled over control of the vehicle, with Lynn putting the vehicle into drive, and\n\nOfficer Powell pulling the emergency brake. The vehicle rolled away, and Officer\n\nGardner pursued it. He heard a gunshot, and when he reached the vehicle, he saw Officer\n\n 3\n\nPowell lying on top of Lynn and holding Lynn’s left hand, in which Lynn had a pistol\n\npointed at Officer Powell. Officer Powell had suffered gunshot wounds to his arms and\n\nchest. Lynn had also suffered a gunshot wound, although Officer Powell had not fired\n\nhis weapon during the struggle.\n\n Lynn was arrested and charged in state court with attempted first-degree murder,\n\npossession of a firearm by a felon, and fleeing or eluding arrest with a motor vehicle.\n\nWhile Lynn was detained in state custody, he was indicted on a federal charge of being a\n\nfelon in possession of a firearm, stemming from the same conduct as the state charges.\n\nLynn was obtained by the district court on a writ of habeas corpus ad prosequendum\n\nwhile his state charges were pending, and he eventually pleaded guilty to the federal\n\nfirearms charge.\n\n At Lynn’s federal sentencing hearing on February 28, 2017, he and Officer Powell\n\nboth testified about what had occurred in the vehicle. Officer Powell stated that after he\n\nhad been able to bring the vehicle to a stop, Lynn dove between the front seats, and as\n\nOfficer Powell had turned to face Lynn, he felt gun shots hit him. On the other hand,\n\nLynn testified that he and Officer Powell had struggled over possession of the firearm,\n\nand it went off accidentally during the struggle. The district court found that Officer\n\nPowell’s testimony was credible while Lynn’s was not, and it determined that a sentence\n\nof 120 months’ imprisonment —the statutory maximum—was appropriate.\n\n The court also heard argument as to whether this sentence should run concurrently\n\nwith or consecutive to Lynn’s future anticipated state sentence. Because Lynn was in\n\nprimary state custody, that state sentence would be served in its entirety before he entered\n\n 4\n\nthe federal prison system. The district court stated that it would be “terribly difficult” for\n\nit to calculate what portion, if any, of Lynn’s sentence should run concurrently with his\n\nanticipated state sentence in light of the variety of state charges he faced, along with the\n\ndispute as to the facts surrounding the shooting. J.A. 153. The court explained:\n\n [L]et’s say that a state court jury finds beyond a reasonable doubt . . . that\n there was a struggle and this constitutes some kind of aggravated assault.\n I’m not sure I would want this sentence to be imposed to run concurrently\n based on the facts that I found.\n\n On the other hand, if there’s an attempted second degree murder\n conviction and some 288-month sentence is imposed, then I think, in\n fairness, the circumstances might merit some overlapping consideration,\n but I just don’t know at this point.\n\nJ.A. 154. The court also suggested that, in light of its uncertainty regarding the extent to\n\nwhich its sentence should run concurrently with the anticipated state sentence, the state\n\ncourt could take the federal sentence into account in fashioning its sentence, and Lynn\n\ncould also request the Bureau of Prisons (BOP) to designate the state prison as his place\n\nof confinement, thus effectively running his federal sentence concurrently with the state\n\nsentence. Ultimately, the court stated:\n\n I am not able to make a determination as to how much of this sentence\n should be imposed to run concurrently with the state court prosecution that\n is now pending. . . . Therefore, at this time I will decline to make a finding\n with respect to running any part of this sentence concurrently to any\n sentence imposed in the state court.\n\nJ.A. 159.\n\n Thereafter, on May 4, 2017, Lynn pleaded guilty in North Carolina Superior Court\n\nto assault with a deadly weapon with intent to kill, inflicting serious bodily injury,\n\n\n\n 5\n\npossession of a firearm by a felon, and fleeing or eluding arrest with a motor vehicle.\n\nThe state court imposed a total sentence of 104 to 137 months’ imprisonment.\n\n II.\n\n A.\n\n Before resolving the issue that was the subject of supplemental briefing and oral\n\nargument, we can easily dispose of the question raised in the Anders brief.\n\n We review a defendant’s sentence “under a deferential abuse-of-discretion\n\nstandard.” Gall v. United States, 552 U.S. 38, 41 (2007). Under the Gall standard, a\n\nsentence is reviewed for both procedural and substantive reasonableness. Id. at 51. In\n\ndetermining procedural reasonableness, we consider, among other things, whether the\n\ncourt properly determined the Sentencing Guidelines range, considered the 18 U.S.C. §\n\n3553(a) factors, and sufficiently explained the selected sentence. Id. at 49–51.\n\n We review the factual findings underlying a district court’s application of a\n\nGuidelines cross-reference for clear error and the court’s legal conclusions de novo.\n\nUnited States v. Ashford, 718 F.3d 377, 380, 383–84 (4th Cir. 2013). “In the event of a\n\nconviction for illegal possession of a firearm, USSG § 2K2.1(c) authorizes a district court\n\nto substitute the offense level for any criminal offense that the defendant committed or\n\nattempted to commit in connection with the possession of the firearm.” Id. at 381. Here,\n\nthe district court found that Lynn committed attempted murder with the firearm at issue.\n\nSentencing Guideline § 2A2.l(a) provides for a base offense level of 33 if the attempted\n\nmurder would have constituted first-degree murder; otherwise, the offense level is 27.\n\n“[S]econd-degree murder simply requires proof of malice aforethought, which may be\n\n 6\n\nestablished by evidence of conduct which is reckless and wanton and a gross deviation\n\nfrom a reasonable standard of care, of such a nature that a jury is warranted in inferring\n\nthat defendant was aware of a serious risk of death or serious bodily harm.” Ashford, 718\n\nF.3d at 384 (internal quotation marks, citation, and alterations omitted).\n\n We conclude that the district court did not err in finding that the murder cross-\n\nreference applied. The district court based its ruling on finding that the victim’s\n\ntestimony was credible and that Lynn’s testimony was not.\n\n [W]hen a trial judge’s finding is based on his decision to credit the\n testimony of one of two or more witnesses, each of whom has told a\n coherent and facially plausible story that is not contradicted by extrinsic\n evidence, that finding, if not internally inconsistent, can virtually never be\n clear error.\n\nUnited States v. Hall, 664 F.3d 456, 462 (4th Cir. 2012) (internal quotation marks and\n\ncitation omitted). Moreover, ballistic evidence indicated that multiple shots were fired\n\nfrom Lynn’s firearm and that more would have been fired had it not malfunctioned. The\n\ndistrict court’s decision not to credit Lynn’s testimony is likewise supported by the\n\nrecord—the firing of multiple shots is arguably inconsistent with Lynn’s explanation that\n\nthe shooting was an accident.\n\n B.\n\n Relying on Setser v. United States, 566 U.S. 231 (2012), Lynn contends that the\n\ndistrict court erred in declining to run its sentence concurrently, in whole or in part, with\n\nthe yet-to-be-imposed state sentence. In light of the now-imposed state sentence, he\n\nseeks a remand for reconsideration of that issue by the district court.\n\n\n\n 7\n\n In Setser, noting that sentencing judges “have discretion to select whether the\n\nsentences they impose will run concurrently or consecutively with respect to other\n\nsentences that they impose, or that have been imposed in other proceedings,” id. at 236,\n\nthe Court held that 18 U.S.C. § 3584(a) allows judges to impose a federal sentence\n\nconcurrently or consecutively to an anticipated, but unimposed, state sentence, id. at 236–\n\n39.\n\n The relevant Sentencing Guideline, added after Setser by USSG amendment 787,\n\neffective November 1, 2014, provides that if “a state term of imprisonment is anticipated\n\nto result from another offense that is relevant conduct to the instant offense of\n\nconviction . . . , the sentence for the instant offense shall be imposed to run concurrently\n\nto the anticipated term of imprisonment.” USSG § 5G1.3(c). There is no question but\n\nthat Lynn’s state charges were relevant conduct to his federal conviction. However,\n\nbecause the Guidelines are advisory, a district court is not obligated to impose a\n\nconcurrent sentence pursuant to USSG § 5G1.3. United States v. Nania, 724 F.3d 824,\n\n830 (7th Cir. 2013). Rather, the district court is required to consider the 18 U.S.C. §\n\n3553(a) factors in determining whether to run sentences consecutively or concurrently.\n\n18 U.S.C. § 3584(b).\n\n Here the district court provided a thorough explanation of the sentence. The court\n\nfound that Lynn’s offense conduct was extremely serious. The court then explained that\n\nit would not order its sentence to run concurrently with the anticipated state sentence in\n\nlight of this seriousness, remarking that a lengthy term of imprisonment was necessary in\n\nthis case. The court recognized its discretion to order the sentence to run concurrently,\n\n 8\n\nbut simply declined to exercise its discretion after considering the required factors. Thus,\n\nwe discern no abuse of discretion in the district court’s decision. See United States v.\n\nHall, 825 F.3d 373, 375–76 (8th Cir. 2016) (upholding decision not to run sentence\n\nconcurrent to anticipated state sentence based on district court’s consideration of the §\n\n3553(a) factors and its explanation that the possibility of a relatively short state sentence\n\nthat would result in an inappropriate period of imprisonment).\n\n Lynn argues that by declining to order the sentence to run concurrently, the district\n\ncourt treaded on the separation-of-powers issue outlined in Setser. See 566 U.S. at 242–\n\n43. In holding that 18 U.S.C. § 3584(a) allows a district court to impose a federal\n\nsentence concurrently or consecutively to an anticipated state sentence, the Court in\n\nSetser rejected the parties’ argument that when a future state sentence is anticipated, the\n\nBOP should decide after the federal sentence has been imposed whether it runs\n\nconcurrently with or consecutive to the state sentence, based upon its authority granted\n\nunder 18 U.S.C. § 3621(b). 1 The Court rejected this argument in part out of concern that\n\nit would leave sentencing in the hands of “the same Department of Justice that conducts\n\nthe prosecution.” Setser, 566 U.S. at 242. Instead, the Court determined that in the first\n\ninstance, the district court, rather than the BOP, should decide whether a federal sentence\n\nruns concurrently with or consecutive to an anticipated state sentence. Id. at 242–43.\n\nHowever, recognizing an exception to this determination, the Court stated that “a district\n\n 1\n That statute provides that the BOP “may designate any available penal or\ncorrectional facility . . ., whether maintained by the Federal Government or otherwise . . .,\nthat the Bureau determines to be appropriate and suitable.” 18 U.S.C. § 3621(b).\n\n\n 9\n\ncourt should exercise the power to impose anticipatory consecutive (or concurrent)\n\nsentences intelligently. In some situations, a district court may have inadequate\n\ninformation and may forbear, but in other situations, that will not be the case.” Id. at 242\n\nn.6.\n\n Lynn’s argument requires us to consider the boundaries of this exception—in what\n\nsituations does a district court’s lack of information permit it to decline to order its\n\nsentence to run concurrently with an anticipated state sentence? To be sure, these\n\nsituations will be limited. When a state sentence is anticipated, the district court will\n\nnormally lack definite information about that sentence, and if this alone were sufficient to\n\npermit the district court to forbear, the exception would swallow the rule. Thus, in most\n\ncases, the district court should decide whether its sentence will run concurrently with or\n\nconsecutive to an anticipated state sentence involving relevant conduct. But as pointed\n\nout by the Sentencing Commission with regard to USSG § 5G1.3, “[d]etermining\n\nwhether, and how, to use this discretion will depend on the adequacy of the information\n\navailable.” USSG Amend. 776 (Nov. 1, 2013).\n\n It is clear that Lynn’s case was not routine. First, the conduct at issue was\n\nextremely serious. As the district court stated, “this is . . . one of the most, if not the\n\nmost, serious forms of a 922(g)(1) offense. The only thing more serious is a shooting in\n\nwhich an individual is actually killed.” J.A. 158. Further, the variety of state charges\n\nagainst Lynn, along with his dispute as to the facts surrounding the shooting—in\n\nparticular, his testimony that the shooting was accidental—made it possible for his\n\nanticipated state sentence to range from relatively short to over double his federal\n\n 10\n\nsentence. The district court considered this possibility and the effect it would have on\n\nany concurrent sentence it might order, ultimately determining that the uncertainty it\n\ncreated prevented the court from accomplishing its proper sentencing objectives.\n\n Of course, we know by now the sentence imposed on Lynn by the state court. But\n\nit was not unreasonable at the time of imposing sentence for the district court to have\n\njustified doubts as to the scope of that state sentence. As noted by the Court in Setser, the\n\nfact that the later state sentence may be unexpected, “does not establish that the District\n\nCourt abused its discretion by imposing an unreasonable sentence.” 566 U.S. at 244. The\n\ndistrict court attempted to exercise its power to impose a concurrent or consecutive\n\nsentence intelligently, but, for the reasons discussed above, it lacked adequate\n\ninformation to do so. Accordingly, the district court did not err in declining to run its\n\nsentence concurrently with the anticipated state sentence. 2\n\n\n 2\n Shortly before oral argument, the government submitted additional authority\npursuant to Federal Rule of Appellate Procedure 28(j) and Local Rule 28(e), arguing that\nwhen Lynn agreed that his state court sentence “shall run consecutively to any other\nsentence the defendant is now subject to,” Lynn waived the issues he raises on appeal,\nand any error by the district court must be disregarded. We disagree.\n\n Lynn’s agreement regarding his state court sentence has no effect on his federal\nsentence. As previously noted, Lynn was in primary state custody when he was\nsentenced on the federal charge, and as a result, he will serve his state sentence in its\nentirety before he serves his federal sentence. “In our American system of dual\nsovereignty, each sovereign—whether the Federal Government or a State—is responsible\nfor the administration of its own criminal justice system.” Setser, 566 U.S. at 241\n(internal quotation marks, citation, and alterations omitted). “If a prisoner like [Lynn]\nstarts in state custody, serves his state sentence, and then moves to federal custody, it will\nalways be the Federal Government . . . that decides whether he will receive credit for the\ntime served in state custody.” Id. Thus, Lynn’s state court sentence cannot run\nconsecutively to his federal sentence, and the state court cannot dictate that his federal\n(Continued)\n 11", "author": "JONES, District Judge:"}, {"type": "dissent", "author": "Our", "text": "Our dissenting colleague parts company with us based upon the contention that the\n\ndistrict court violated its procedural duty by failing to expressly accept or reject the\n\nadvisory language of § 5G1.3(c). But the court satisfied its procedural duty when it\n\nconsidered the Guideline and fully explained its rationale for declining to exercise its\n\ndiscretion. For the reasons given above, we find that the district court’s explanation\n\ngiven in this case was sufficient, and as authorized by Setser.\n\n\n\n AFFIRMED\n\n\n\n\nsentence will run consecutively to his state sentence. Accordingly, Lynn could not—and\nhas not—waived his argument regarding his federal sentence.\n\n 12"}, {"author": "FLOYD, Circuit Judge, concurring", "type": "concurrence", "text": "FLOYD, Circuit Judge, concurring in part and dissenting in part:\n\n I join with all parts of the majority opinion save one: I disagree with my\n\ncolleagues’ conclusion that the district court had the discretion to make no decision at all\n\non whether Lynn’s federal sentence would run concurrently with his anticipated state\n\nsentence. I would hold that because U.S.S.G. § 5G1.3 was a “pertinent Sentencing\n\nCommission policy statement,” United States v. Olmeda, 894 F.3d 89, 93 (2d Cir. 2018)\n\n(quoting United States v. Cavera, 550 F.3d 180, 188–89 (2d Cir. 2008) (en banc)), the\n\ndistrict court was required to decide whether to adopt § 5G1.3’s recommendation that\n\nLynn’s sentences run concurrently. That is, the district court had the discretion either to\n\nfollow or depart from the Sentencing Commission’s recommendation on concurrency.\n\nBut the district court did not have the discretion to make no decision on concurrency at\n\nall. Therefore, I respectfully dissent as to Part II.B of the majority opinion.\n\n\n\n I.\n\n Lynn’s federal sentencing hearing took place before his pending state charges\n\nwere resolved. During the sentencing, the government raised U.S.S.G. § 5G3.1(c) and its\n\nrecommendation that Lynn’s federal sentence run concurrently with his anticipated state\n\nsentence. Both government and defense counsel argued that § 5G3.1(c) applied and that\n\nat least a portion of Lynn’s federal sentence should run concurrently with his anticipated\n\nstate sentence.\n\n In response, the district court stated that it was “terribly difficult” to calculate how\n\nmuch of Lynn’s federal sentence should run concurrently with a yet-to-be-determined\n\n\n 13\n\nstate sentence. J.A. 153. The length of Lynn’s future state sentence could vary widely,\n\nfrom a relatively short sentence for aggravated assault to a far longer sentence for\n\nattempted murder. Should Lynn receive a short sentence, the court was “not sure” that it\n\nwanted any of the federal sentence to be served concurrently with the state sentence. J.A.\n\n154. If, however, Lynn received a long state sentence, the court believed that “in\n\nfairness, the circumstances might merit some overlapping” of the sentences. Id.\n\n The district court then opined that it need not decide the § 5G3.1(c) question\n\nbecause “ultimately, the Bureau of Prisons has the authority to come back in and handle\n\n[this situation] through one of those retroactive designations.” J.A. 153. When defense\n\ncounsel expressed confusion regarding what the court meant by retroactive designations,\n\nthe court replied: “When an individual does finally arrive at the Bureau of Prisons,”\n\nmeaning after the defendant has served his state sentence and is transferred to federal\n\ncustody to serve his federal sentence for related conduct, “there is an administrative\n\nprocess where [offenders] can apply and ask for that overlap – the overlapping sentences\n\nto be taken into consideration and the Bureau of Prisons backdate the start of the federal\n\nsentence to some date during the state sentence that’s been served.” J.A. 156. When\n\nsuch a request is made, the district court continued, “I usually get a letter that asks for my\n\nposition on that, and if it is truly a circumstance where there was overlapping conduct\n\nthat enhanced both sentences, I usually tell that to the Bureau of Prisons, but I don’t know\n\nwhat they do with that once I’ve made my comment.” Id.\n\n Ultimately, the district court declined to decide whether to apply § 5G3.1(c)’s\n\nrecommendation that Lynn’s sentences be served concurrently, stating:\n\n\n 14\n\n I am not able to make a determination as to how much of this sentence\n should be imposed to run concurrently with the state court prosecution that\n is now pending. Certainly, to the extent Mr. Lynn was ultimately either\n found guilty or pled guilty to an attempted second-degree murder [in state\n court], there would be significant overlap between these two sentences that\n are imposed in this case, but, ultimately . . . should Mr. Lynn ultimately be\n convicted of a [weapons possession] offense or some other offense, I would\n not be inclined to run any of this sentence concurrent to the sentence that\n may be imposed in state court. Therefore, at this time I will decline to\n make a finding with respect to running any part of this sentence\n concurrently to any sentence imposed in the state court.\n\nJ.A. 159 (emphasis added). I thus disagree with my colleagues in the majority to the\n\nextent that they understand the district court’s ruling as a decision to not adopt\n\n§ 5G3.1(c)’s concurrency recommendation. Rather, we are faced here with a case in\n\nwhich the district court refrained from making any decision at all on a pertinent\n\nSentencing Guideline.\n\n\n\n II.\n\n The Bureau of Prisons’ (BOP) role in making concurrency determinations serves\n\nas important background here. The BOP is empowered by statute to decide where federal\n\ninmates serve their sentences. 18 U.S.C. § 3621(b) (2012). When making that\n\ndetermination, the BOP may “designate any available penal or correctional facility that\n\nmeets minimum standards . . . whether maintained by the Federal Government or\n\notherwise.” Id. Thus, “when a federal defendant is already serving a state sentence, BOP\n\nhas the practical power to ‘make the federal sentence run concurrently by designating the\n\nstate prison as a place of federal confinement, so that the clock would start to tick on the\n\nfederal sentence.’” Fegans v. United States, 506 F.3d 1101, 1103 (8th Cir. 2007)\n\n\n 15\n\n(quoting Romandine v. United States, 206 F.3d 731, 738 (7th Cir. 2000)). Congress’s\n\ngrant of power to the BOP to select a place of confinement for federal prisoners has\n\ntherefore become a de facto power to determine whether a federal sentence will be served\n\nconcurrently with a state sentence.\n\n When a district court has made the concurrency determination already, the BOP\n\nenforces the court’s order. See BOP Program Statement 5160.05 ¶ 7 (“When a federal\n\njudge orders or recommends a federal sentence run concurrently with a state sentence\n\nalready imposed, the Bureau implements such order or recommendation . . . .”); Fegans,\n\n506 F.3d at 1105. When, however, a federal judge fails to make a concurrency\n\ndetermination, the BOP refers to 18 U.S.C. § 3584(a), which states:\n\n If multiple terms of imprisonment are imposed on a defendant at the same\n time, or if a term of imprisonment is imposed on a defendant who is already\n subject to an undischarged term of imprisonment, the terms may run\n concurrently or consecutively . . . . Multiple terms of imprisonment\n imposed at the same time run concurrently unless the court orders or the\n statute mandates that the terms are to run consecutively. Multiple terms of\n imprisonment imposed at different times run consecutively unless the court\n orders that the terms are to run concurrently.\n\nSee Mangum v. Hallembaek, 824 F.3d 98, 101–02 (4th Cir. 2016) (explaining the BOP’s\n\nreliance on 18 U.S.C. § 3584). Hence, when a district court is silent as to whether a\n\nsentence should be served concurrently with or consecutively to another sentence, the\n\nBOP uses § 3584(a) to fill in the gaps.\n\n The plain text of § 3584(a), however, contains its own gap: It says nothing about\n\nwhether a district court may order a federal sentence to be served concurrently with a yet-\n\n\n\n\n 16\n\nto-be-imposed state sentence. 1 After § 3584(a) was enacted, some circuits interpreted\n\nthat gap to mean that district courts could not order a federal sentence to be served\n\nconcurrently with a yet-to-be-imposed state sentence. See Abdul-Malik v. Hawk-Sawyer,\n\n403 F.3d 72, 75–76 (2d Cir. 2005) (collecting cases); Fegans, 506 F.3d at 1104 (noting\n\nexistence of circuit split). In those circuits, a pragmatic problem arose: once the state\n\nsentence was imposed, who could decide whether the federal sentence would run\n\nconcurrently or consecutively? The Third Circuit was the first to address that question\n\nand held that the BOP should fill this void by reviewing applications from prisoners who\n\nhad been transferred to federal custody after serving a state sentence, and then deciding\n\nwhether the federal sentence should run concurrently or consecutively with the state\n\nsentence through a nunc pro tunc designation. Barden v. Keohane, 921 F.2d 476, 480–81\n\n(3d Cir. 1990). Subsequently, multiple federal courts of appeals followed the Third\n\nCircuit’s lead. Fegans, 506 F.3d at 1104; Mangum, 824 F.3d at 101–02; Abdul-Malik,\n\n403 F.3d at 75–76; Taylor v. Sawyer, 284 F.3d 1143, 1149 (9th Cir. 2002); Romandine,\n\n206 F.3d at 738; McCarthy v. Doe, 146 F.3d 118, 122 (2d Cir. 1998).\n\n In 2012, the U.S. Supreme Court closed the gap in § 3584(a), holding that district\n\ncourts have the inherent authority to order that federal sentences be served concurrently\n\n\n1\n When § 3584(a)’s final sentence refers to “[m]ultiple terms of imprisonment imposed at\ndifferent times,” it means the situation described in the first sentence, where a second\nprison term is “imposed on a defendant who is already subject to an undischarged term of\nimprisonment.” Setser v. United States, 566 U.S. 231, 234–35 (2012). Section 3584(a)\ndoes not address the situation here, where the federal sentence was imposed before the\nstate sentence.\n\n\n\n 17\n\nwith anticipated state sentences. Setser v. United States, 566 U.S. 231, 237–39 (2012).\n\nSoon after Setser, U.S.S.G. § 5G1.3(c), which advises district court judges to make\n\nfederal sentences concurrent with not-yet-imposed state sentences for related conduct,\n\nwas added to the Guidelines. See Olmeda, 894 F.3d at 92–93 (describing history). The\n\ncommentary to § 5G1.3(c) states:\n\n This amendment is a . . . . response to the Supreme Court’s decision in\n Setser . . . . [It] reflects the Commission’s determination that the concurrent\n sentence benefits of subsection (b) of § 5G1.3 should be available not only\n in cases in which the state sentence has already been imposed at the time of\n federal sentencing (as subsection (b) provides), but also in cases in which\n the state sentence is anticipated but has not yet been imposed . . . . By\n requiring courts to impose a concurrent sentence in these cases, the\n amendment reduces disparities between defendants whose state sentences\n have already been imposed and those whose state sentences have not yet\n been imposed.\n\nU.S.S.G. § 5G1.3, Historical Notes, 2014 Amendments.\n\n Setser and § 5G1.3 eliminated the pragmatic problem that originally led to the\n\nBOP’s power to make concurrency determinations. Nevertheless, the BOP has continued\n\nto make concurrency determinations in cases where district courts have neglected to do\n\nso. See, e.g., Mangum, 824 F.3d at 99 (deciding a 2016 challenge to the BOP’s refusal to\n\ngrant an inmate a nunc pro tunc designation that his federal sentence had started while he\n\nwas in state custody). The district court in this case relied upon the BOP’s ongoing\n\npractice of making concurrency determinations to justify its refusal to decide whether\n\n§ 5G1.3(c) should apply to Lynn’s sentence.\n\n\n\n\n 18\n\n III.\n\n The BOP originally assumed the power to make concurrency determinations for\n\ndefendants, like Lynn, who faced a later-imposed state sentence because § 3584(a) left a\n\nvoid that some district courts were forbidden to fill. Post-Setser, that void no longer\n\nexists, which brings the troubling implications of the BOP’s practice to the forefront:\n\nThe BOP is exercising a power that clearly belongs to the judiciary. Additionally, since\n\nthe Guidelines have been amended post-Setser to include § 5G1.3(c)’s recommendation\n\nthat defendants in Lynn’s position should serve concurrent sentences, district courts have\n\nan obligation, as part of their mandatory consideration of all relevant Guidelines, to\n\ndecide whether they will accept § 5G1.3(c)’s recommendation during sentencing. The\n\ndistrict court did not do so here, and so I would reverse.\n\n Setser squarely addressed whether the concurrent-versus-consecutive decision\n\nrests with the BOP or the judiciary. In Setser, a defendant was indicted for drug charges\n\nin both state and federal court. Setser, 566 U.S. at 233. Setser received his federal\n\nsentence first, and the district court ruled that his federal sentence would run concurrently\n\nwith any state sentence he received for his drug charge, but consecutive to any future\n\nstate sentence he would receive for a then-outstanding probation violation. Id. Setser\n\nappealed, arguing that the district court lacked the power to make that concurrency\n\ndetermination because the case fell into the above-described § 3584(a) gap. Id. at 234–\n\n35. Specifically, he argued that the § 3584(a) gap meant that any concurrency\n\ndetermination should be left exclusively to the BOP through its nunc pro tunc designation\n\n\n\n\n 19\n\nprocess, as district courts lacked any power not explicitly granted by § 3584(a). Id. at\n\n235. The Supreme Court disagreed:\n\n That is an odd parsing of [§ 3584], which makes no distinction between the\n district court and the Bureau of Prisons. The placement of § 3584 does\n indeed suggest that it is directed at district courts—but that is likely because\n Congress contemplated that only district courts would have the authority to\n make the concurrent-vs.-consecutive decision, not because Congress meant\n to leave the Bureau unfettered. Indeed, the Bureau already follows the\n other directives in § 3584(a). For example, if the district court imposes\n multiple terms of imprisonment at the same time, but fails to address the\n concurrent-vs.-consecutive issue, the terms “run concurrently,” [as\n provided by] § 3584(a), and the Bureau is not free to use its “place of\n imprisonment” authority to achieve a different result.\n\nId. at 237–38 (citations omitted) (emphasis added). The Court went on to explain that, by\n\nrelying on the maxim of expressio unius est exclusion alterius, or the explicit mention of\n\none thing is the exclusion of another,\n\n Setser . . . suggests that, because § 3584(a) recognizes judicial discretion in\n scenario A and scenario B, there is no such discretion in scenario C. But\n the same maxim shows much more convincingly why § 3621(b) [which\n grants the BOP the power to designate state prisons as a federal inmate’s\n place of confinement] cannot be read to give the Bureau of Prisons\n exclusive authority to make the sort of decision committed to the district\n court in § 3584(a). When § 3584(a) specifically addresses decisions about\n concurrent and consecutive sentences, and makes no mention of the\n Bureau’s role in the process, the implication is that no such role exists.\n And that conclusion is reinforced by application of the same maxim\n (properly, in this instance) to § 3621(b)—which is a conferral of authority\n on the Bureau of Prisons, but does not confer authority to choose between\n concurrent and consecutive sentences. Put to the choice, we believe it is\n much more natural to read § 3584(a) as not containing an implied “only,”\n leaving room for the exercise of judicial discretion in the situations not\n covered, than it is to read § 3621(b) as giving the Bureau of Prisons what\n amounts to sentencing authority.\n\nId. at 238–39 (second emphasis added).\n\n\n\n\n 20\n\n While the Setser Court held that district courts have the authority to decide that a\n\nfederal sentence should run concurrently with an anticipated state sentence, it stopped\n\nshort of deciding that the BOP’s decades-old nunc pro tunc designation process is itself\n\nunlawful. It did, however, express concern about giving sentencing authority to a federal\n\nagency. Id. at 239, 242 n.5. Such concern has been echoed by other Courts of Appeals.\n\nThe Second Circuit, for example, has explained that “[a] separation of powers issue arises\n\nwhen the same branch of government that prosecutes federal prisoners determines\n\nconcurrency in lieu of the judge.” Abdul-Malik, 403 F.3d at 76; see also Fegans, 506\n\nF.3d at 1104 (“[W]e agree with the Second Circuit that Congress should examine the\n\n[BOP’s practice of making concurrency determinations] because it implicates important\n\nfederalism and separation of powers concerns[.]”). I agree that the BOP’s practice raises\n\ntroubling separation-of-powers concerns.\n\n\n\n IV.\n\n Although district courts are not mandated to comply with the recommendations in\n\nthe Guidelines, they still “must give due consideration” to any relevant Guideline policy\n\nstatements and explain any deviation therefrom. United States v. Engle, 592 F.3d 495,\n\n502–04 (4th Cir. 2010). Section 5G1.3(c) was a “pertinent Sentencing Commission\n\npolicy statement” at Lynn’s sentencing, so it should have been “take[n] into account.”\n\nOlmeda, 894 F.3d at 93 (quoting Cavera, 550 F.3d at 188–89); 18 U.S.C. § 3553(a)(5)\n\n(2012) (listing “pertinent policy statement[s]” as a factor that sentencing judges must\n\nconsider). However, while the district court acknowledged § 5G1.3(c)’s existence, heard\n\n\n 21\n\nargument on it, and discussed its application at some length during the sentencing\n\nhearing, the district court ultimately decided to neither adopt nor reject the Guidelines’\n\nrecommendation. Typically, this result would not be possible: When imposing a federal\n\nsentence, district courts necessarily decide whether to accept or reject the pertinent\n\nSentencing Guidelines whenever they decide the length of a sentence. Section 5G1.3(c),\n\nhowever, uniquely provides an opportunity to make no decision at all because a district\n\ncourt’s failure to rule in situations where § 5G1.3(c) applies creates no presumption one\n\nway or another regarding whether the prisoner’s two sentences should be served\n\nconcurrently. See Mangum, 824 F.3d at 101–02. The decision is simply left to the BOP.\n\n The majority opines that Setser already acknowledged and condoned the very\n\nsame failure to decide that occurred here, citing the footnote in which the Supreme Court\n\nstates: “Of course, a district court should exercise the power to impose anticipatory\n\nconsecutive (or concurrent) sentences intelligently. In some situations, a district court\n\nmay have inadequate information and may forbear, but in other situations, that will not\n\nbe the case.” Setser, 566 U.S. at 243 n.6 (emphasis added). This language, however, was\n\nwritten before the U.S. Sentencing Commission adopted § 5G1.3(c). It does not change\n\nthe district court’s obligation to rule on each pertinent Sentencing Guideline.\n\n Criminal sentencing has been entrusted to the judicial branch, and deciding\n\nwhether multiple sentences should run concurrently is intrinsically a determination of the\n\nlength of imprisonment. Such decisions should be made by the district court just like any\n\nother determination about the number of months that a defendant will serve. Therefore,\n\nthe district court’s failure to rule on § 5G1.3(c)’s applicability to Lynn’s sentence punts\n\n\n 22\n\nthe determination on the length of his sentence to the BOP. That result is an\n\ninappropriate delegation of the courts’ judicial power, and I must dissent.\n\n\n\n V.\n\n Because U.S.S.G. § 5G1.3 is a pertinent Sentencing Commission policy statement,\n\nthe district court was required to decide whether to adopt its recommendation that Lynn’s\n\nsentences run concurrently. It erred in leaving that decision to the BOP. I therefore\n\nrespectfully dissent.\n\n\n\n\n 23", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356547/", "author_raw": "FLOYD, Circuit Judge, concurring"}]}
MOTZ
FLOYD
JONES
1
{}
5
0
1
2
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4579294/
Published
1
1
0
1
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff - Appellee, v. Gary Giovon LYNN, Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-07\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4232\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nGARY GIOVON LYNN,\n\n Defendant - Appellant.\n\n\n\nAppeal from the United States District Court for the Middle District of North Carolina, at\nGreensboro. William L. Osteen, Jr., District Judge. (1:16-cr-00287-WO-1)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n\n\nBefore MOTZ and FLOYD, Circuit Judges, and James P. JONES, United States District\nJudge for the Western District of Virginia, sitting by designation.\n\n\nAffirmed by published opinion. Judge Jones wrote the majority opinion, in which Judge\nMotz joined. Judge Floyd wrote a separate opinion, in which he concurred in part and\ndissented in part.\n\n\nARGUED: John Arthur Duberstein, OFFICE OF THE FEDERAL PUBLIC\nDEFENDER, Greensboro, North Carolina, for Appellant. Kimberly Furr Davis, OFFICE\nOF THE UNITED STATES ATTORNEY, Winston-Salem, North Carolina, for\nAppellee. ON BRIEF: Louis C. Allen, Federal Public Defender, OFFICE OF THE\nFEDERAL PUBLIC DEFENDER, Greensboro, North Carolina, for Appellant. Matthew\nG.T. Martin, United States Attorney, OFFICE OF THE UNITED STATES ATTORNEY,\n\nGreensboro, North Carolina, for Appellee.\n\n\n\n\n 2\n\nJONES, District Judge:\n\n Gary Giovon Lynn pled guilty to being a felon in possession of a firearm, in\n\nviolation of 18 U.S.C. §§ 922(g)(l), 924(a)(2). The district court sentenced Lynn to 120\n\nmonths’ imprisonment. On appeal, counsel filed a brief pursuant to Anders v. California,\n\n386 U.S. 738 (1967), questioning whether the district court erred in applying a cross-\n\nreference to the attempted murder Sentencing Guideline. U.S. Sentencing Guidelines\n\nManual (USSG) §§ 2A2.1, 2K2.1(c)(l)(A), 2X1.l(a) (2016). We directed supplemental\n\nbriefing on the additional issue of whether in light of USSG § 5G3.1(c), the district court\n\nerred in failing to impose its sentence to run concurrently with an anticipated term of\n\nstate imprisonment. We now affirm the district court’s judgment.\n\n I.\n\n On January 4, 2016, Officer A.D. Gardner of the Winston-Salem Police\n\nDepartment stopped a speeding vehicle occupied by Lynn along with two other\n\nindividuals. While standing near the vehicle, Officer Gardner smelled marijuana, and he\n\nrequested additional officers for assistance. When the other officers arrived, Officer\n\nGardner asked each of the occupants to exit the vehicle. After Officer Gardner frisked\n\nLynn, Gardner instructed him to stand by a guardrail with the driver of the vehicle. As\n\nOfficer Nicholas Powell was frisking another passenger, Lynn jumped into the driver’s\n\nside of the vehicle and Officer Powell followed, landing on top of him. The two\n\nstruggled over control of the vehicle, with Lynn putting the vehicle into drive, and\n\nOfficer Powell pulling the emergency brake. The vehicle rolled away, and Officer\n\nGardner pursued it. He heard a gunshot, and when he reached the vehicle, he saw Officer\n\n 3\n\nPowell lying on top of Lynn and holding Lynn’s left hand, in which Lynn had a pistol\n\npointed at Officer Powell. Officer Powell had suffered gunshot wounds to his arms and\n\nchest. Lynn had also suffered a gunshot wound, although Officer Powell had not fired\n\nhis weapon during the struggle.\n\n Lynn was arrested and charged in state court with attempted first-degree murder,\n\npossession of a firearm by a felon, and fleeing or eluding arrest with a motor vehicle.\n\nWhile Lynn was detained in state custody, he was indicted on a federal charge of being a\n\nfelon in possession of a firearm, stemming from the same conduct as the state charges.\n\nLynn was obtained by the district court on a writ of habeas corpus ad prosequendum\n\nwhile his state charges were pending, and he eventually pleaded guilty to the federal\n\nfirearms charge.\n\n At Lynn’s federal sentencing hearing on February 28, 2017, he and Officer Powell\n\nboth testified about what had occurred in the vehicle. Officer Powell stated that after he\n\nhad been able to bring the vehicle to a stop, Lynn dove between the front seats, and as\n\nOfficer Powell had turned to face Lynn, he felt gun shots hit him. On the other hand,\n\nLynn testified that he and Officer Powell had struggled over possession of the firearm,\n\nand it went off accidentally during the struggle. The district court found that Officer\n\nPowell’s testimony was credible while Lynn’s was not, and it determined that a sentence\n\nof 120 months’ imprisonment —the statutory maximum—was appropriate.\n\n The court also heard argument as to whether this sentence should run concurrently\n\nwith or consecutive to Lynn’s future anticipated state sentence. Because Lynn was in\n\nprimary state custody, that state sentence would be served in its entirety before he entered\n\n 4\n\nthe federal prison system. The district court stated that it would be “terribly difficult” for\n\nit to calculate what portion, if any, of Lynn’s sentence should run concurrently with his\n\nanticipated state sentence in light of the variety of state charges he faced, along with the\n\ndispute as to the facts surrounding the shooting. J.A. 153. The court explained:\n\n [L]et’s say that a state court jury finds beyond a reasonable doubt . . . that\n there was a struggle and this constitutes some kind of aggravated assault.\n I’m not sure I would want this sentence to be imposed to run concurrently\n based on the facts that I found.\n\n On the other hand, if there’s an attempted second degree murder\n conviction and some 288-month sentence is imposed, then I think, in\n fairness, the circumstances might merit some overlapping consideration,\n but I just don’t know at this point.\n\nJ.A. 154. The court also suggested that, in light of its uncertainty regarding the extent to\n\nwhich its sentence should run concurrently with the anticipated state sentence, the state\n\ncourt could take the federal sentence into account in fashioning its sentence, and Lynn\n\ncould also request the Bureau of Prisons (BOP) to designate the state prison as his place\n\nof confinement, thus effectively running his federal sentence concurrently with the state\n\nsentence. Ultimately, the court stated:\n\n I am not able to make a determination as to how much of this sentence\n should be imposed to run concurrently with the state court prosecution that\n is now pending. . . . Therefore, at this time I will decline to make a finding\n with respect to running any part of this sentence concurrently to any\n sentence imposed in the state court.\n\nJ.A. 159.\n\n Thereafter, on May 4, 2017, Lynn pleaded guilty in North Carolina Superior Court\n\nto assault with a deadly weapon with intent to kill, inflicting serious bodily injury,\n\n\n\n 5\n\npossession of a firearm by a felon, and fleeing or eluding arrest with a motor vehicle.\n\nThe state court imposed a total sentence of 104 to 137 months’ imprisonment.\n\n II.\n\n A.\n\n Before resolving the issue that was the subject of supplemental briefing and oral\n\nargument, we can easily dispose of the question raised in the Anders brief.\n\n We review a defendant’s sentence “under a deferential abuse-of-discretion\n\nstandard.” Gall v. United States, 552 U.S. 38, 41 (2007). Under the Gall standard, a\n\nsentence is reviewed for both procedural and substantive reasonableness. Id. at 51. In\n\ndetermining procedural reasonableness, we consider, among other things, whether the\n\ncourt properly determined the Sentencing Guidelines range, considered the 18 U.S.C. §\n\n3553(a) factors, and sufficiently explained the selected sentence. Id. at 49–51.\n\n We review the factual findings underlying a district court’s application of a\n\nGuidelines cross-reference for clear error and the court’s legal conclusions de novo.\n\nUnited States v. Ashford, 718 F.3d 377, 380, 383–84 (4th Cir. 2013). “In the event of a\n\nconviction for illegal possession of a firearm, USSG § 2K2.1(c) authorizes a district court\n\nto substitute the offense level for any criminal offense that the defendant committed or\n\nattempted to commit in connection with the possession of the firearm.” Id. at 381. Here,\n\nthe district court found that Lynn committed attempted murder with the firearm at issue.\n\nSentencing Guideline § 2A2.l(a) provides for a base offense level of 33 if the attempted\n\nmurder would have constituted first-degree murder; otherwise, the offense level is 27.\n\n“[S]econd-degree murder simply requires proof of malice aforethought, which may be\n\n 6\n\nestablished by evidence of conduct which is reckless and wanton and a gross deviation\n\nfrom a reasonable standard of care, of such a nature that a jury is warranted in inferring\n\nthat defendant was aware of a serious risk of death or serious bodily harm.” Ashford, 718\n\nF.3d at 384 (internal quotation marks, citation, and alterations omitted).\n\n We conclude that the district court did not err in finding that the murder cross-\n\nreference applied. The district court based its ruling on finding that the victim’s\n\ntestimony was credible and that Lynn’s testimony was not.\n\n [W]hen a trial judge’s finding is based on his decision to credit the\n testimony of one of two or more witnesses, each of whom has told a\n coherent and facially plausible story that is not contradicted by extrinsic\n evidence, that finding, if not internally inconsistent, can virtually never be\n clear error.\n\nUnited States v. Hall, 664 F.3d 456, 462 (4th Cir. 2012) (internal quotation marks and\n\ncitation omitted). Moreover, ballistic evidence indicated that multiple shots were fired\n\nfrom Lynn’s firearm and that more would have been fired had it not malfunctioned. The\n\ndistrict court’s decision not to credit Lynn’s testimony is likewise supported by the\n\nrecord—the firing of multiple shots is arguably inconsistent with Lynn’s explanation that\n\nthe shooting was an accident.\n\n B.\n\n Relying on Setser v. United States, 566 U.S. 231 (2012), Lynn contends that the\n\ndistrict court erred in declining to run its sentence concurrently, in whole or in part, with\n\nthe yet-to-be-imposed state sentence. In light of the now-imposed state sentence, he\n\nseeks a remand for reconsideration of that issue by the district court.\n\n\n\n 7\n\n In Setser, noting that sentencing judges “have discretion to select whether the\n\nsentences they impose will run concurrently or consecutively with respect to other\n\nsentences that they impose, or that have been imposed in other proceedings,” id. at 236,\n\nthe Court held that 18 U.S.C. § 3584(a) allows judges to impose a federal sentence\n\nconcurrently or consecutively to an anticipated, but unimposed, state sentence, id. at 236–\n\n39.\n\n The relevant Sentencing Guideline, added after Setser by USSG amendment 787,\n\neffective November 1, 2014, provides that if “a state term of imprisonment is anticipated\n\nto result from another offense that is relevant conduct to the instant offense of\n\nconviction . . . , the sentence for the instant offense shall be imposed to run concurrently\n\nto the anticipated term of imprisonment.” USSG § 5G1.3(c). There is no question but\n\nthat Lynn’s state charges were relevant conduct to his federal conviction. However,\n\nbecause the Guidelines are advisory, a district court is not obligated to impose a\n\nconcurrent sentence pursuant to USSG § 5G1.3. United States v. Nania, 724 F.3d 824,\n\n830 (7th Cir. 2013). Rather, the district court is required to consider the 18 U.S.C. §\n\n3553(a) factors in determining whether to run sentences consecutively or concurrently.\n\n18 U.S.C. § 3584(b).\n\n Here the district court provided a thorough explanation of the sentence. The court\n\nfound that Lynn’s offense conduct was extremely serious. The court then explained that\n\nit would not order its sentence to run concurrently with the anticipated state sentence in\n\nlight of this seriousness, remarking that a lengthy term of imprisonment was necessary in\n\nthis case. The court recognized its discretion to order the sentence to run concurrently,\n\n 8\n\nbut simply declined to exercise its discretion after considering the required factors. Thus,\n\nwe discern no abuse of discretion in the district court’s decision. See United States v.\n\nHall, 825 F.3d 373, 375–76 (8th Cir. 2016) (upholding decision not to run sentence\n\nconcurrent to anticipated state sentence based on district court’s consideration of the §\n\n3553(a) factors and its explanation that the possibility of a relatively short state sentence\n\nthat would result in an inappropriate period of imprisonment).\n\n Lynn argues that by declining to order the sentence to run concurrently, the district\n\ncourt treaded on the separation-of-powers issue outlined in Setser. See 566 U.S. at 242–\n\n43. In holding that 18 U.S.C. § 3584(a) allows a district court to impose a federal\n\nsentence concurrently or consecutively to an anticipated state sentence, the Court in\n\nSetser rejected the parties’ argument that when a future state sentence is anticipated, the\n\nBOP should decide after the federal sentence has been imposed whether it runs\n\nconcurrently with or consecutive to the state sentence, based upon its authority granted\n\nunder 18 U.S.C. § 3621(b). 1 The Court rejected this argument in part out of concern that\n\nit would leave sentencing in the hands of “the same Department of Justice that conducts\n\nthe prosecution.” Setser, 566 U.S. at 242. Instead, the Court determined that in the first\n\ninstance, the district court, rather than the BOP, should decide whether a federal sentence\n\nruns concurrently with or consecutive to an anticipated state sentence. Id. at 242–43.\n\nHowever, recognizing an exception to this determination, the Court stated that “a district\n\n 1\n That statute provides that the BOP “may designate any available penal or\ncorrectional facility . . ., whether maintained by the Federal Government or otherwise . . .,\nthat the Bureau determines to be appropriate and suitable.” 18 U.S.C. § 3621(b).\n\n\n 9\n\ncourt should exercise the power to impose anticipatory consecutive (or concurrent)\n\nsentences intelligently. In some situations, a district court may have inadequate\n\ninformation and may forbear, but in other situations, that will not be the case.” Id. at 242\n\nn.6.\n\n Lynn’s argument requires us to consider the boundaries of this exception—in what\n\nsituations does a district court’s lack of information permit it to decline to order its\n\nsentence to run concurrently with an anticipated state sentence? To be sure, these\n\nsituations will be limited. When a state sentence is anticipated, the district court will\n\nnormally lack definite information about that sentence, and if this alone were sufficient to\n\npermit the district court to forbear, the exception would swallow the rule. Thus, in most\n\ncases, the district court should decide whether its sentence will run concurrently with or\n\nconsecutive to an anticipated state sentence involving relevant conduct. But as pointed\n\nout by the Sentencing Commission with regard to USSG § 5G1.3, “[d]etermining\n\nwhether, and how, to use this discretion will depend on the adequacy of the information\n\navailable.” USSG Amend. 776 (Nov. 1, 2013).\n\n It is clear that Lynn’s case was not routine. First, the conduct at issue was\n\nextremely serious. As the district court stated, “this is . . . one of the most, if not the\n\nmost, serious forms of a 922(g)(1) offense. The only thing more serious is a shooting in\n\nwhich an individual is actually killed.” J.A. 158. Further, the variety of state charges\n\nagainst Lynn, along with his dispute as to the facts surrounding the shooting—in\n\nparticular, his testimony that the shooting was accidental—made it possible for his\n\nanticipated state sentence to range from relatively short to over double his federal\n\n 10\n\nsentence. The district court considered this possibility and the effect it would have on\n\nany concurrent sentence it might order, ultimately determining that the uncertainty it\n\ncreated prevented the court from accomplishing its proper sentencing objectives.\n\n Of course, we know by now the sentence imposed on Lynn by the state court. But\n\nit was not unreasonable at the time of imposing sentence for the district court to have\n\njustified doubts as to the scope of that state sentence. As noted by the Court in Setser, the\n\nfact that the later state sentence may be unexpected, “does not establish that the District\n\nCourt abused its discretion by imposing an unreasonable sentence.” 566 U.S. at 244. The\n\ndistrict court attempted to exercise its power to impose a concurrent or consecutive\n\nsentence intelligently, but, for the reasons discussed above, it lacked adequate\n\ninformation to do so. Accordingly, the district court did not err in declining to run its\n\nsentence concurrently with the anticipated state sentence. 2\n\n\n 2\n Shortly before oral argument, the government submitted additional authority\npursuant to Federal Rule of Appellate Procedure 28(j) and Local Rule 28(e), arguing that\nwhen Lynn agreed that his state court sentence “shall run consecutively to any other\nsentence the defendant is now subject to,” Lynn waived the issues he raises on appeal,\nand any error by the district court must be disregarded. We disagree.\n\n Lynn’s agreement regarding his state court sentence has no effect on his federal\nsentence. As previously noted, Lynn was in primary state custody when he was\nsentenced on the federal charge, and as a result, he will serve his state sentence in its\nentirety before he serves his federal sentence. “In our American system of dual\nsovereignty, each sovereign—whether the Federal Government or a State—is responsible\nfor the administration of its own criminal justice system.” Setser, 566 U.S. at 241\n(internal quotation marks, citation, and alterations omitted). “If a prisoner like [Lynn]\nstarts in state custody, serves his state sentence, and then moves to federal custody, it will\nalways be the Federal Government . . . that decides whether he will receive credit for the\ntime served in state custody.” Id. Thus, Lynn’s state court sentence cannot run\nconsecutively to his federal sentence, and the state court cannot dictate that his federal\n(Continued)\n 11\n[END_CASE]", "role": "user" } ]
4,579,301
Jose Marcial CORTEZ-MENDEZ, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.
Jose Cortez-Mendez v. Matthew Whitaker
2019-01-07
16-2389
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Before WILKINSON and AGEE, Circuit Judges, and James P. JONES, United States District Judge for the Western District of Virginia, sitting by designation.", "parties": "", "opinions": [{"author": "AGEE, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 16-2389\n\n\n\nJOSE MARCIAL CORTEZ-MENDEZ,\n\n Petitioner,\n\nv.\n\nMATTHEW G. WHITAKER, Acting Attorney General,\n\n Respondent.\n\n\nOn Petition for Review of an Order of the Board of Immigration Appeals.\n\n\nArgued: September 25, 2018 Decided: January 7, 2019\n\n\nBefore WILKINSON and AGEE, Circuit Judges, and James P. JONES, United States\nDistrict Judge for the Western District of Virginia, sitting by designation.\n\n\nPetition for review denied by published opinion. Judge Agee wrote the opinion, in\nwhich Judge Wilkinson and Judge Jones joined.\n\n\nARGUED: Melissa Jill Mitchell, LAW OFFICES OF PAUL A. SUHR, PLLC, Raleigh,\nNorth Carolina, for Cortez-Mendez. Robert Michael Stalzer, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Respondent. ON BRIEF: Paul\nA. Suhr, LAW OFFICES OF PAUL A. SUHR, PLLC, Raleigh, North Carolina, for\nCortez-Mendez. Chad A. Readler, Acting Assistant Attorney General, Kiley Kane,\nSenior Litigation Counsel, Office of Immigration Litigation, Civil Division, UNITED\nSTATES DEPARTMENT OF JUSTICE, Washington, D.C., for Respondent.\n\fAGEE, Circuit Judge:\n\n Jose Cortez-Mendez, a native and citizen of El Salvador, seeks review of an order\n\nfrom the Board of Immigration Appeals (“BIA”). The BIA dismissed his appeal\n\nfollowing an immigration judge’s (“IJ’s”) denial of his application for withholding of\n\nremoval under the Immigration and Nationality Act (“INA”), 8 U.S.C. § 1231(b)(3), and\n\nprotection under the United Nations Convention Against Torture (“CAT”), 8 C.F.R.\n\n§ 1208.16(c). For the reasons below, we deny the petition for review.\n\n\n\n I.\n\n Cortez-Mendez was born in El Salvador. His father, Marcial Cortez, is deaf and\n\nmute. People in El Salvador with these physical impairments have suffered routine\n\nridicule and discrimination, despite the existence of anti-discrimination laws. See A.R.\n\n422 (containing U.S. Dep’t of State, El Salvador, 2014 Country Reports on Human\n\nRights Practices). Because of his disabilities, Marcial Cortez could not provide for his\n\nfamily and they moved in with Cortez-Mendez’s aunt. Cortez-Mendez’s mother also\n\nabandoned the family when he was seven because of the family’s difficulties.\n\n As a teenager, MS-13 and MS-18 gang members began targeting Cortez-Mendez\n\nfor gang recruitment. They harassed him and “threatened [him] with death, that if [he] did\n\nnot become a gangster, they were going to kill [him].” A.R. 175. Despite this harassment,\n\nthe gangs never physically harmed Cortez-Mendez or anyone in his family. To this day,\n\nhis father, mother, sisters, and aunt live in El Salvador unharmed.\n\n\n\n 2\n\f Cortez-Mendez illegally entered the United States in 2003. The Department of\n\nHomeland Security served him with a Notice to Appear, but he failed to appear at his\n\nhearing and was ordered removed to El Salvador in abstentia. Nevertheless, Cortez-\n\nMendez settled in North Carolina with his uncle, girlfriend, and two children. In 2005,\n\ngang members called Cortez-Mendez’s mother in El Salvador, demanded money, and\n\ndemanded Cortez-Mendez’s whereabouts. Through his aunt, Cortez-Mendez learned the\n\ngangs told his mother they “remembered [him] as a son of a mute and dumb person” and\n\nthreatened to “kill [him] and dismember [him]” if he returned to El Salvador. A.R. 176.\n\n In 2015, Cortez-Mendez applied for withholding of removal and CAT protection.\n\nAs grounds for protection under the INA, he cited his membership in a particular social\n\ngroup: “member[s] of the family of Marcial Cortez who is a disabled person.” A.R. 124;\n\nsee 8 U.S.C. § 1101(a)(42). In 2016, the IJ denied Cortez-Mendez’s application for\n\nwithholding of removal and CAT protection. The IJ found Cortez-Mendez’s testimony\n\nwas credible but held his proposed particular social group did not satisfy the INA’s\n\nrequirements. The IJ also held that Cortez-Mendez failed to demonstrate a sufficient\n\nnexus—that is, he did not show that the “indeterminate and generalized” threats he had\n\nreceived in El Salvador were on account of his membership in that group. A.R. 63.\n\n Cortez-Mendez appealed to the BIA. In its own opinion, the BIA affirmed the IJ’s\n\nconclusion that “any threats [Cortez-Mendez] received or future harm he fears are the\n\nresult of general criminal gang activity,” not membership in his disabled father’s family.\n\nA.R. 3. The BIA also affirmed the IJ’s refusal to accept Cortez-Mendez’s “speculat[ion]\n\nthat his lower economic status and his father’s disability made him more susceptible to\n\n 3\n\fgang recruitment” because the record fairly supports the conclusion that the “harm he\n\nfears upon return [is] as a result of his rejection of gang membership rather than his\n\nfather’s disability.” A.R. 3. The BIA thus dismissed Cortez-Mendez’s appeal, and Cortez-\n\nMendez was again ordered removed. He timely appealed, and we have jurisdiction under\n\n8 U.S.C. § 1252.\n\n\n\n II.\n\n When, as here, the BIA “adopt[s] and affirm[s]” the IJ’s conclusion but adds\n\nadditional reasoning in its own opinion, we review “the factual findings and reasoning\n\ncontained in both decisions.” Ai Hua Chen v. Holder, 742 F.3d 171, 177 (4th Cir. 2014);\n\nA.R. 3. If the factual findings are supported by substantial evidence, they are conclusive\n\n“unless any reasonable adjudicator would be compelled to conclude to the contrary.” 8\n\nU.S.C. § 1252(b)(4)(B); Salgado-Sosa v. Sessions, 882 F.3d 451, 456 (4th Cir. 2018). As\n\nfor legal determinations, we review them de novo. Salgado-Sosa, 882 F.3d at 456.\n\nUltimately, we must affirm the BIA’s decision if it is not “manifestly contrary to law and\n\nan abuse of discretion.” 8 U.S.C. § 1252(b)(4)(D).\n\n\n\n III.\n\n In his opening brief, Cortez-Mendez argues only that the BIA erred in denying his\n\npetition for withholding of removal. Because he does not address the BIA’s denial of his\n\npetition for CAT protection, he has waived his claim for CAT relief. Fed. R. App. P.\n\n28(a)(8)(A); see Edwards v. City of Goldsboro, 178 F.3d 231, 241 n.6 (4th Cir. 1999).\n\n 4\n\f To receive withholding of removal relief, Cortez-Mendez must show that, if\n\nremoved to El Salvador, “there is a clear probability that [his] ‘life or freedom would be\n\nthreatened . . . because of’” a protected ground—here, his alleged membership in a\n\nparticular social group. Marynenka v. Holder, 592 F.3d 594, 600 (4th Cir. 2010) (quoting\n\n8 U.S.C. § 1231(b)(3)(A)). This standard requires two showings: First, Cortez-Mendez\n\nmust show “it is more likely than not” that his life or freedom will be threatened if he\n\nreturns to El Salvador. Lizama v. Holder, 629 F.3d 440, 446 (4th Cir. 2011) (internal\n\nquotation marks omitted). Evidence that he suffered past persecution can help to satisfy\n\nthis first showing. See 8 C.F.R. § 1208.16(b)(1). Second, Cortez-Mendez must show that\n\nthe “probability of persecution” is “link[ed]” to his status in the particular social group,\n\nthat is, that the two share a nexus. Singh v. Holder, 699 F.3d 321, 327 (4th Cir. 2012). If\n\nhe satisfies his burden of proof, withholding of removal is mandatory. Gomis v. Holder,\n\n571 F.3d 353, 359 (4th Cir. 2009).\n\n The nexus issue is dispositive of this appeal, so we dispose at the outset of two\n\nissues we need not resolve: whether Cortez-Mendez is a member of a particular social\n\ngroup and whether he suffered past persecution. See 8 U.S.C. § 1101(a)(42); 8 C.F.R.\n\n§ 1208.16(b)(1). We will assume, without deciding, that Cortez-Mendez is a member of a\n\nparticular social group comprised of his disabled father’s immediate family members and\n\nthat he suffered past persecution in El Salvador. ∗ We will consider only whether Cortez-\n\n\n ∗While “we have expressly held that the threat of death qualifies as persecution,”\nHernandez-Avalos v. Lynch, 784 F.3d 944, 949 (4th Cir. 2015) (internal quotation marks\nomitted), we hesitate to conclude that Cortez-Mendez suffered past persecution here. To\n(Continued)\n 5\n\fMendez established the requisite nexus between any persecution he suffered and his\n\nrelation to his disabled father.\n\n A.\n\n Whether a person’s persecution shares a nexus with his alleged protected ground is\n\na question of fact entitled to deference and reviewed for clear error. See Crespin-\n\nValladares v. Holder, 632 F.3d 117, 128 (4th Cir. 2011). To establish this nexus, Cortez-\n\nMendez must demonstrate that his membership in his disabled father’s family is “at least\n\none central reason for” the persecution he experienced or that he fears in El Salvador. 8\n\nU.S.C. § 1158(b)(1)(B)(i). His relation to his father cannot be “incidental, tangential,\n\nsuperficial, or subordinate to another reason for harm.” Quinteros-Mendoza v. Holder,\n\n556 F.3d 159, 164 (4th Cir. 2009) (internal quotation marks omitted) (emphasis added).\n\n“[O]ur review of the BIA’s and IJ’s determination of this factual question is limited to\n\nconsidering whether their conclusion is ‘supported by reasonable, substantial, and\n\n\n\n\nconstitute persecution, actions “must rise above the level of mere harassment,” Qiao Hua\nLi v. Gonzales, 405 F.3d 171, 177 (4th Cir. 2005), and must be of “sufficient severity,”\nMirisawo v. Holder, 599 F.3d 391, 396 (4th Cir. 2010), that they “constitute a threat to\nlife or freedom itself,” née Joseph v. Sessions, No. 17-1403, 2018 WL 3549714, at *3\n(4th Cir. July 24, 2018) (internal quotation marks omitted). Cortez-Mendez testified that\nhe was never physically harmed by the gangs; his fears are wholly based on distant verbal\nthreats and intimidation. We question whether the threats in the record—unspecific gang-\nrelated threats and one “death threat” communicated through two third parties, across\ncountry borders, and a decade before Cortez-Mendez sought legal protection—constitute\nthe “extreme” persecution necessary to support withholding of removal. Molina Mendoza\nv. Sessions, 712 F. App’x 240, 242 (4th Cir. 2018). Nevertheless, we need not decide the\npersecution issue here.\n\n 6\n\fprobative evidence.’” Cruz v. Sessions, 853 F.3d 122, 128 (4th Cir. 2017) (quoting\n\nNgarurih v. Ashcroft, 371 F.3d 182, 188 (4th Cir. 2004)). We conclude that it is.\n\n B.\n\n Cortez-Mendez disputes the IJ and BIA’s conclusion that he was threatened\n\nbecause of “general criminal gang activity” in his hometown. A.R. 3; see A.R. 65–66. He\n\nasserts the gangs persecuted him because his father’s disabilities caused Cortez-Mendez\n\nto be poor, “vulnerable,” and “an easy mark [without] the backing and advice of a\n\nfather.” A.R. 148. Cortez-Mendez argues his persecution was pointedly discriminatory\n\nbecause he “knew many of his persecutors[ ] and had heard them ridicule his father and\n\nthe rest of his family.” Opening Br. 11; see A.R. 56. We find his arguments unpersuasive.\n\n Cortez-Mendez presented no direct or circumstantial evidence that the gangs\n\nharassed him “on account of” his father’s disabilities as opposed to his own rejection of\n\ngang membership. See 8 U.S.C. § 1101(a)(42). He provided no direct evidence that the\n\ngangs intimidated him because he was his father’s son. His only evidence of linkage to\n\nhis father is that non-gang neighborhood harassers had “made fun of” him because of\n\nMarcial Cortez’s disabilities, A.R. 146–47, and the gang members who called his mother\n\nin 2005 “remembered [him] as a son of a mute and dumb person,” A.R. 176. Even if\n\neither of these groups of taunters knew about Marcial Cortez’s disabilities, it does not\n\nfollow that they intimidated Cortez-Mendez because of his relation to his disabled father.\n\nSee Hernandez-Avalos, 784 F.3d at 950 n.7 (“[N]ot . . . every threat that references a\n\nfamily member is made on account of family ties.”).\n\n\n\n 7\n\f Indeed, the circumstantial evidence in the record reflects a different reason for\n\nCortez-Mendez’s harassment: he rejected the gangs’ recruitment efforts. Cortez-Mendez\n\ntestified that he feared the gangs would harm him “if [he] did not become a gangster” or\n\n“if [he] did not [agree] to become part of the gangs.” A.R. 175. Substantial evidence\n\nsupports the IJ’s and BIA’s conclusions that the “neighborhood gangs observed the\n\nfamily’s poverty and concluded they could easily recruit” Cortez-Mendez, A.R. 56, and\n\nthat it was after Cortez-Mendez refused to join the gangs that they threatened him, A.R.\n\n3–4, 66. Cortez-Mendez even admitted that he left El Salvador because had rejected gang\n\nmembership: “they kept asking me to join them and be a member of the gang, and that is\n\nwhy I fled.” A.R. 140. At most, Cortez-Mendez demonstrated that the gangs may have\n\ntargeted him because of his poverty but only threatened him because he would not join\n\ntheir ranks. Flight from gang recruitment is not a protected ground under the INA. See\n\nZelaya v. Holder, 668 F.3d 159, 166–67 (4th Cir. 2012); Matter of S-E-G-, 24 I. & N.\n\nDec. 579, 589 (B.I.A. 2008). Consequently, Cortez-Mendez’s own testimony of his\n\ncircumstantial fears defeats his argument that a protected ground like his relation to his\n\ndisabled father was “at least one central reason for” his treatment in El Salvador.\n\nCrespin-Valladares, 632 F.3d at 127.\n\n Furthermore, while it is not dispositive, Cortez-Mendez testified that his father and\n\nother family members still live in El Salvador and have suffered no harm. Our decision\n\nrelies on whether Cortez-Mendez—and not some other person—was persecuted because\n\nof his relation to his father, see Hernandez-Avalos, 784 F.3d at 950; Crespin-Valladares,\n\n632 F.3d at 127 n.6, but a fact we may consider with the rest is whether other family\n\n 8\n\fmembers have been persecuted because of their identical family ties, see Mirisawo, 599\n\nF.3d at 398 (“The fact that family members whose political opinions Mirisawo fears will\n\nbe imputed to her have not themselves faced harm fatally undermines her claim that she\n\nwill suffer persecution because of her association with them.”). The evidence in the\n\nrecord that Cortez-Mendez’s family—including his disabled father—remains unharmed\n\nsuggests that Cortez-Mendez’s relation to his father is not the reason for the persecution\n\nhe fears.\n\n Our nexus analyses in Salgado-Sosa, 882 F.3d 451, and Cordova v. Holder, 759\n\nF.3d 332 (4th Cir. 2014), support our conclusion. In Salgado-Sosa, the petitioner fled to\n\nthe United States from Honduran gangs because his stepfather had angered the gangs, the\n\npetitioner defended his stepfather, and the gangs retaliated against the petitioner. 882\n\nF.3d at 457–58. There, we found “no meaningful distinction between whether Salgado-\n\nSosa was threatened because of his connection to his stepfather [or] because MS-13\n\nsought revenge on him for an act committed by his stepfather,” because both were\n\nderivative of his stepfather’s dispute with the gangs. Id. at 458. Since the petitioner\n\nshared family ties with his stepfather, he had established a sufficient nexus between his\n\npersecution and a protected ground. Id. at 458–59. Cortez-Mendez, by contrast, has\n\nprovided no evidence that the gangs threatened him because of his father’s disabilities.\n\nInstead, he testified that his rejection of gang membership was the impetus for his\n\nharassment.\n\n Cordova likewise bolsters our conclusion. There, we reversed the BIA’s denial of\n\nthe petitioner’s application of asylum and withholding of removal because the BIA had\n\n 9\n\fignored relevant nexus evidence. Cordova, 759 F.3d at 339. The petitioner in Cordova\n\nhad testified that gang members targeted him because he was related to members of a\n\nrival gang, but the BIA only considered evidence that he was targeted for rebuffing gang\n\nrecruitment. Id. at 339–40. Here, however, the IJ and the BIA ignored no relevant\n\nevidence concerning the import of the father’s disabilities because Cortez-Mendez\n\npresented none. All he provided was his unsubstantiated speculation that the gangs\n\ntargeted him because of his father’s disabilities. Given Cortez-Mendez’s own testimony\n\nthat he feared the gangs after refusing to join them, we are not “compelled” to conclude\n\nthat the gangs’ threats against Cortez-Mendez were on account of his father’s disabilities,\n\nas opposed to Cortez-Mendez’s rejection of gang membership. See Salgado-Sosa, 882\n\nF.3d at 456. As such, substantial evidence supported the BIA’s conclusion that Cortez-\n\nMendez failed to establish the requisite nexus. Accordingly, the BIA did not err in\n\ndenying withholding of removal.\n\n C.\n\n The INA does not protect every person who rejects gang recruitment efforts. See\n\nZelaya, 668 F.3d at 166–67. A petitioner seeking withholding of removal must show\n\nmore. Cortez-Mendez has failed to provide either direct or circumstantial evidence that\n\nthe gangs’ actions against him were motivated by a protected ground. See I.N.S. v. Elias-\n\nZacarias, 502 U.S. 478, 483 (1992). Consequently, Cortez-Mendez’s “[f]ear of\n\nretribution over purely personal matters” cannot support his application for withholding\n\nof removal. Moreno v. Lynch, 628 F. App’x 862, 866 (4th Cir. 2015).\n\n\n\n 10\n\f If we were to grant withholding of removal based on the slim evidence Cortez-\n\nMendez has provided, every family member of a disabled person would be eligible for\n\nrefugee status if anyone harassed them in their home country. We have rejected sweeping\n\narguments like this before and do so again. See, e.g., Yi Ni v. Holder, 613 F.3d 415, 429–\n\n30 (4th Cir. 2010) (“Were the fact that a person is subject to family planning policies\n\nsufficient to establish persecution, every Chinese citizen of childbearing age would be\n\neligible for relief.”). Therefore, “[u]nder the deferential substantial evidence standard we\n\nare bound to apply, we conclude that the absence of any direct evidence establishing that”\n\ngang members “intended to persecute [Cortez-Mendez] because of his familial\n\nrelationship to his [father]—provided an adequate basis for a reasonable adjudicator to\n\ndeny [Cortez-Mendez] relief.” Pacas-Renderos v. Sessions, 691 F. App’x 796, 803 (4th\n\nCir. 2017). Substantial evidence supports the IJ’s and BIA’s finding that Cortez-Mendez\n\ndid not establish the requisite nexus, and his application for withholding of removal was\n\nproperly denied.\n\n\n\n IV.\n\n Accordingly, Cortez-Mendez’s petition for review is\n\n DENIED.\n\n\n\n\n 11", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356554/", "author_raw": "AGEE, Circuit Judge:"}]}
WILKINSON
AGEE
JAMES P JONES
1
{"WILKINSON": ", Circuit", "AGEE": ", Circuit", "P JONES": ", United States District"}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579301/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Jose Marcial CORTEZ-MENDEZ, Petitioner, v. Matthew G. WHITAKER, Acting Attorney General, Respondent.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-07\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 16-2389\n\n\n\nJOSE MARCIAL CORTEZ-MENDEZ,\n\n Petitioner,\n\nv.\n\nMATTHEW G. WHITAKER, Acting Attorney General,\n\n Respondent.\n\n\nOn Petition for Review of an Order of the Board of Immigration Appeals.\n\n\nArgued: September 25, 2018 Decided: January 7, 2019\n\n\nBefore WILKINSON and AGEE, Circuit Judges, and James P. JONES, United States\nDistrict Judge for the Western District of Virginia, sitting by designation.\n\n\nPetition for review denied by published opinion. Judge Agee wrote the opinion, in\nwhich Judge Wilkinson and Judge Jones joined.\n\n\nARGUED: Melissa Jill Mitchell, LAW OFFICES OF PAUL A. SUHR, PLLC, Raleigh,\nNorth Carolina, for Cortez-Mendez. Robert Michael Stalzer, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Respondent. ON BRIEF: Paul\nA. Suhr, LAW OFFICES OF PAUL A. SUHR, PLLC, Raleigh, North Carolina, for\nCortez-Mendez. Chad A. Readler, Acting Assistant Attorney General, Kiley Kane,\nSenior Litigation Counsel, Office of Immigration Litigation, Civil Division, UNITED\nSTATES DEPARTMENT OF JUSTICE, Washington, D.C., for Respondent.\n\fAGEE, Circuit Judge:\n\n Jose Cortez-Mendez, a native and citizen of El Salvador, seeks review of an order\n\nfrom the Board of Immigration Appeals (“BIA”). The BIA dismissed his appeal\n\nfollowing an immigration judge’s (“IJ’s”) denial of his application for withholding of\n\nremoval under the Immigration and Nationality Act (“INA”), 8 U.S.C. § 1231(b)(3), and\n\nprotection under the United Nations Convention Against Torture (“CAT”), 8 C.F.R.\n\n§ 1208.16(c). For the reasons below, we deny the petition for review.\n\n\n\n I.\n\n Cortez-Mendez was born in El Salvador. His father, Marcial Cortez, is deaf and\n\nmute. People in El Salvador with these physical impairments have suffered routine\n\nridicule and discrimination, despite the existence of anti-discrimination laws. See A.R.\n\n422 (containing U.S. Dep’t of State, El Salvador, 2014 Country Reports on Human\n\nRights Practices). Because of his disabilities, Marcial Cortez could not provide for his\n\nfamily and they moved in with Cortez-Mendez’s aunt. Cortez-Mendez’s mother also\n\nabandoned the family when he was seven because of the family’s difficulties.\n\n As a teenager, MS-13 and MS-18 gang members began targeting Cortez-Mendez\n\nfor gang recruitment. They harassed him and “threatened [him] with death, that if [he] did\n\nnot become a gangster, they were going to kill [him].” A.R. 175. Despite this harassment,\n\nthe gangs never physically harmed Cortez-Mendez or anyone in his family. To this day,\n\nhis father, mother, sisters, and aunt live in El Salvador unharmed.\n\n\n\n 2\n\f Cortez-Mendez illegally entered the United States in 2003. The Department of\n\nHomeland Security served him with a Notice to Appear, but he failed to appear at his\n\nhearing and was ordered removed to El Salvador in abstentia. Nevertheless, Cortez-\n\nMendez settled in North Carolina with his uncle, girlfriend, and two children. In 2005,\n\ngang members called Cortez-Mendez’s mother in El Salvador, demanded money, and\n\ndemanded Cortez-Mendez’s whereabouts. Through his aunt, Cortez-Mendez learned the\n\ngangs told his mother they “remembered [him] as a son of a mute and dumb person” and\n\nthreatened to “kill [him] and dismember [him]” if he returned to El Salvador. A.R. 176.\n\n In 2015, Cortez-Mendez applied for withholding of removal and CAT protection.\n\nAs grounds for protection under the INA, he cited his membership in a particular social\n\ngroup: “member[s] of the family of Marcial Cortez who is a disabled person.” A.R. 124;\n\nsee 8 U.S.C. § 1101(a)(42). In 2016, the IJ denied Cortez-Mendez’s application for\n\nwithholding of removal and CAT protection. The IJ found Cortez-Mendez’s testimony\n\nwas credible but held his proposed particular social group did not satisfy the INA’s\n\nrequirements. The IJ also held that Cortez-Mendez failed to demonstrate a sufficient\n\nnexus—that is, he did not show that the “indeterminate and generalized” threats he had\n\nreceived in El Salvador were on account of his membership in that group. A.R. 63.\n\n Cortez-Mendez appealed to the BIA. In its own opinion, the BIA affirmed the IJ’s\n\nconclusion that “any threats [Cortez-Mendez] received or future harm he fears are the\n\nresult of general criminal gang activity,” not membership in his disabled father’s family.\n\nA.R. 3. The BIA also affirmed the IJ’s refusal to accept Cortez-Mendez’s “speculat[ion]\n\nthat his lower economic status and his father’s disability made him more susceptible to\n\n 3\n\fgang recruitment” because the record fairly supports the conclusion that the “harm he\n\nfears upon return [is] as a result of his rejection of gang membership rather than his\n\nfather’s disability.” A.R. 3. The BIA thus dismissed Cortez-Mendez’s appeal, and Cortez-\n\nMendez was again ordered removed. He timely appealed, and we have jurisdiction under\n\n8 U.S.C. § 1252.\n\n\n\n II.\n\n When, as here, the BIA “adopt[s] and affirm[s]” the IJ’s conclusion but adds\n\nadditional reasoning in its own opinion, we review “the factual findings and reasoning\n\ncontained in both decisions.” Ai Hua Chen v. Holder, 742 F.3d 171, 177 (4th Cir. 2014);\n\nA.R. 3. If the factual findings are supported by substantial evidence, they are conclusive\n\n“unless any reasonable adjudicator would be compelled to conclude to the contrary.” 8\n\nU.S.C. § 1252(b)(4)(B); Salgado-Sosa v. Sessions, 882 F.3d 451, 456 (4th Cir. 2018). As\n\nfor legal determinations, we review them de novo. Salgado-Sosa, 882 F.3d at 456.\n\nUltimately, we must affirm the BIA’s decision if it is not “manifestly contrary to law and\n\nan abuse of discretion.” 8 U.S.C. § 1252(b)(4)(D).\n\n\n\n III.\n\n In his opening brief, Cortez-Mendez argues only that the BIA erred in denying his\n\npetition for withholding of removal. Because he does not address the BIA’s denial of his\n\npetition for CAT protection, he has waived his claim for CAT relief. Fed. R. App. P.\n\n28(a)(8)(A); see Edwards v. City of Goldsboro, 178 F.3d 231, 241 n.6 (4th Cir. 1999).\n\n 4\n\f To receive withholding of removal relief, Cortez-Mendez must show that, if\n\nremoved to El Salvador, “there is a clear probability that [his] ‘life or freedom would be\n\nthreatened . . . because of’” a protected ground—here, his alleged membership in a\n\nparticular social group. Marynenka v. Holder, 592 F.3d 594, 600 (4th Cir. 2010) (quoting\n\n8 U.S.C. § 1231(b)(3)(A)). This standard requires two showings: First, Cortez-Mendez\n\nmust show “it is more likely than not” that his life or freedom will be threatened if he\n\nreturns to El Salvador. Lizama v. Holder, 629 F.3d 440, 446 (4th Cir. 2011) (internal\n\nquotation marks omitted). Evidence that he suffered past persecution can help to satisfy\n\nthis first showing. See 8 C.F.R. § 1208.16(b)(1). Second, Cortez-Mendez must show that\n\nthe “probability of persecution” is “link[ed]” to his status in the particular social group,\n\nthat is, that the two share a nexus. Singh v. Holder, 699 F.3d 321, 327 (4th Cir. 2012). If\n\nhe satisfies his burden of proof, withholding of removal is mandatory. Gomis v. Holder,\n\n571 F.3d 353, 359 (4th Cir. 2009).\n\n The nexus issue is dispositive of this appeal, so we dispose at the outset of two\n\nissues we need not resolve: whether Cortez-Mendez is a member of a particular social\n\ngroup and whether he suffered past persecution. See 8 U.S.C. § 1101(a)(42); 8 C.F.R.\n\n§ 1208.16(b)(1). We will assume, without deciding, that Cortez-Mendez is a member of a\n\nparticular social group comprised of his disabled father’s immediate family members and\n\nthat he suffered past persecution in El Salvador. ∗ We will consider only whether Cortez-\n\n\n ∗While “we have expressly held that the threat of death qualifies as persecution,”\nHernandez-Avalos v. Lynch, 784 F.3d 944, 949 (4th Cir. 2015) (internal quotation marks\nomitted), we hesitate to conclude that Cortez-Mendez suffered past persecution here. To\n(Continued)\n 5\n\fMendez established the requisite nexus between any persecution he suffered and his\n\nrelation to his disabled father.\n\n A.\n\n Whether a person’s persecution shares a nexus with his alleged protected ground is\n\na question of fact entitled to deference and reviewed for clear error. See Crespin-\n\nValladares v. Holder, 632 F.3d 117, 128 (4th Cir. 2011). To establish this nexus, Cortez-\n\nMendez must demonstrate that his membership in his disabled father’s family is “at least\n\none central reason for” the persecution he experienced or that he fears in El Salvador. 8\n\nU.S.C. § 1158(b)(1)(B)(i). His relation to his father cannot be “incidental, tangential,\n\nsuperficial, or subordinate to another reason for harm.” Quinteros-Mendoza v. Holder,\n\n556 F.3d 159, 164 (4th Cir. 2009) (internal quotation marks omitted) (emphasis added).\n\n“[O]ur review of the BIA’s and IJ’s determination of this factual question is limited to\n\nconsidering whether their conclusion is ‘supported by reasonable, substantial, and\n\n\n\n\nconstitute persecution, actions “must rise above the level of mere harassment,” Qiao Hua\nLi v. Gonzales, 405 F.3d 171, 177 (4th Cir. 2005), and must be of “sufficient severity,”\nMirisawo v. Holder, 599 F.3d 391, 396 (4th Cir. 2010), that they “constitute a threat to\nlife or freedom itself,” née Joseph v. Sessions, No. 17-1403, 2018 WL 3549714, at *3\n(4th Cir. July 24, 2018) (internal quotation marks omitted). Cortez-Mendez testified that\nhe was never physically harmed by the gangs; his fears are wholly based on distant verbal\nthreats and intimidation. We question whether the threats in the record—unspecific gang-\nrelated threats and one “death threat” communicated through two third parties, across\ncountry borders, and a decade before Cortez-Mendez sought legal protection—constitute\nthe “extreme” persecution necessary to support withholding of removal. Molina Mendoza\nv. Sessions, 712 F. App’x 240, 242 (4th Cir. 2018). Nevertheless, we need not decide the\npersecution issue here.\n\n 6\n\fprobative evidence.’” Cruz v. Sessions, 853 F.3d 122, 128 (4th Cir. 2017) (quoting\n\nNgarurih v. Ashcroft, 371 F.3d 182, 188 (4th Cir. 2004)). We conclude that it is.\n\n B.\n\n Cortez-Mendez disputes the IJ and BIA’s conclusion that he was threatened\n\nbecause of “general criminal gang activity” in his hometown. A.R. 3; see A.R. 65–66. He\n\nasserts the gangs persecuted him because his father’s disabilities caused Cortez-Mendez\n\nto be poor, “vulnerable,” and “an easy mark [without] the backing and advice of a\n\nfather.” A.R. 148. Cortez-Mendez argues his persecution was pointedly discriminatory\n\nbecause he “knew many of his persecutors[ ] and had heard them ridicule his father and\n\nthe rest of his family.” Opening Br. 11; see A.R. 56. We find his arguments unpersuasive.\n\n Cortez-Mendez presented no direct or circumstantial evidence that the gangs\n\nharassed him “on account of” his father’s disabilities as opposed to his own rejection of\n\ngang membership. See 8 U.S.C. § 1101(a)(42). He provided no direct evidence that the\n\ngangs intimidated him because he was his father’s son. His only evidence of linkage to\n\nhis father is that non-gang neighborhood harassers had “made fun of” him because of\n\nMarcial Cortez’s disabilities, A.R. 146–47, and the gang members who called his mother\n\nin 2005 “remembered [him] as a son of a mute and dumb person,” A.R. 176. Even if\n\neither of these groups of taunters knew about Marcial Cortez’s disabilities, it does not\n\nfollow that they intimidated Cortez-Mendez because of his relation to his disabled father.\n\nSee Hernandez-Avalos, 784 F.3d at 950 n.7 (“[N]ot . . . every threat that references a\n\nfamily member is made on account of family ties.”).\n\n\n\n 7\n\f Indeed, the circumstantial evidence in the record reflects a different reason for\n\nCortez-Mendez’s harassment: he rejected the gangs’ recruitment efforts. Cortez-Mendez\n\ntestified that he feared the gangs would harm him “if [he] did not become a gangster” or\n\n“if [he] did not [agree] to become part of the gangs.” A.R. 175. Substantial evidence\n\nsupports the IJ’s and BIA’s conclusions that the “neighborhood gangs observed the\n\nfamily’s poverty and concluded they could easily recruit” Cortez-Mendez, A.R. 56, and\n\nthat it was after Cortez-Mendez refused to join the gangs that they threatened him, A.R.\n\n3–4, 66. Cortez-Mendez even admitted that he left El Salvador because had rejected gang\n\nmembership: “they kept asking me to join them and be a member of the gang, and that is\n\nwhy I fled.” A.R. 140. At most, Cortez-Mendez demonstrated that the gangs may have\n\ntargeted him because of his poverty but only threatened him because he would not join\n\ntheir ranks. Flight from gang recruitment is not a protected ground under the INA. See\n\nZelaya v. Holder, 668 F.3d 159, 166–67 (4th Cir. 2012); Matter of S-E-G-, 24 I. & N.\n\nDec. 579, 589 (B.I.A. 2008). Consequently, Cortez-Mendez’s own testimony of his\n\ncircumstantial fears defeats his argument that a protected ground like his relation to his\n\ndisabled father was “at least one central reason for” his treatment in El Salvador.\n\nCrespin-Valladares, 632 F.3d at 127.\n\n Furthermore, while it is not dispositive, Cortez-Mendez testified that his father and\n\nother family members still live in El Salvador and have suffered no harm. Our decision\n\nrelies on whether Cortez-Mendez—and not some other person—was persecuted because\n\nof his relation to his father, see Hernandez-Avalos, 784 F.3d at 950; Crespin-Valladares,\n\n632 F.3d at 127 n.6, but a fact we may consider with the rest is whether other family\n\n 8\n\fmembers have been persecuted because of their identical family ties, see Mirisawo, 599\n\nF.3d at 398 (“The fact that family members whose political opinions Mirisawo fears will\n\nbe imputed to her have not themselves faced harm fatally undermines her claim that she\n\nwill suffer persecution because of her association with them.”). The evidence in the\n\nrecord that Cortez-Mendez’s family—including his disabled father—remains unharmed\n\nsuggests that Cortez-Mendez’s relation to his father is not the reason for the persecution\n\nhe fears.\n\n Our nexus analyses in Salgado-Sosa, 882 F.3d 451, and Cordova v. Holder, 759\n\nF.3d 332 (4th Cir. 2014), support our conclusion. In Salgado-Sosa, the petitioner fled to\n\nthe United States from Honduran gangs because his stepfather had angered the gangs, the\n\npetitioner defended his stepfather, and the gangs retaliated against the petitioner. 882\n\nF.3d at 457–58. There, we found “no meaningful distinction between whether Salgado-\n\nSosa was threatened because of his connection to his stepfather [or] because MS-13\n\nsought revenge on him for an act committed by his stepfather,” because both were\n\nderivative of his stepfather’s dispute with the gangs. Id. at 458. Since the petitioner\n\nshared family ties with his stepfather, he had established a sufficient nexus between his\n\npersecution and a protected ground. Id. at 458–59. Cortez-Mendez, by contrast, has\n\nprovided no evidence that the gangs threatened him because of his father’s disabilities.\n\nInstead, he testified that his rejection of gang membership was the impetus for his\n\nharassment.\n\n Cordova likewise bolsters our conclusion. There, we reversed the BIA’s denial of\n\nthe petitioner’s application of asylum and withholding of removal because the BIA had\n\n 9\n\fignored relevant nexus evidence. Cordova, 759 F.3d at 339. The petitioner in Cordova\n\nhad testified that gang members targeted him because he was related to members of a\n\nrival gang, but the BIA only considered evidence that he was targeted for rebuffing gang\n\nrecruitment. Id. at 339–40. Here, however, the IJ and the BIA ignored no relevant\n\nevidence concerning the import of the father’s disabilities because Cortez-Mendez\n\npresented none. All he provided was his unsubstantiated speculation that the gangs\n\ntargeted him because of his father’s disabilities. Given Cortez-Mendez’s own testimony\n\nthat he feared the gangs after refusing to join them, we are not “compelled” to conclude\n\nthat the gangs’ threats against Cortez-Mendez were on account of his father’s disabilities,\n\nas opposed to Cortez-Mendez’s rejection of gang membership. See Salgado-Sosa, 882\n\nF.3d at 456. As such, substantial evidence supported the BIA’s conclusion that Cortez-\n\nMendez failed to establish the requisite nexus. Accordingly, the BIA did not err in\n\ndenying withholding of removal.\n\n C.\n\n The INA does not protect every person who rejects gang recruitment efforts. See\n\nZelaya, 668 F.3d at 166–67. A petitioner seeking withholding of removal must show\n\nmore. Cortez-Mendez has failed to provide either direct or circumstantial evidence that\n\nthe gangs’ actions against him were motivated by a protected ground. See I.N.S. v. Elias-\n\nZacarias, 502 U.S. 478, 483 (1992). Consequently, Cortez-Mendez’s “[f]ear of\n\nretribution over purely personal matters” cannot support his application for withholding\n\nof removal. Moreno v. Lynch, 628 F. App’x 862, 866 (4th Cir. 2015).\n\n\n\n 10\n\f If we were to grant withholding of removal based on the slim evidence Cortez-\n\nMendez has provided, every family member of a disabled person would be eligible for\n\nrefugee status if anyone harassed them in their home country. We have rejected sweeping\n\narguments like this before and do so again. See, e.g., Yi Ni v. Holder, 613 F.3d 415, 429–\n\n30 (4th Cir. 2010) (“Were the fact that a person is subject to family planning policies\n\nsufficient to establish persecution, every Chinese citizen of childbearing age would be\n\neligible for relief.”). Therefore, “[u]nder the deferential substantial evidence standard we\n\nare bound to apply, we conclude that the absence of any direct evidence establishing that”\n\ngang members “intended to persecute [Cortez-Mendez] because of his familial\n\nrelationship to his [father]—provided an adequate basis for a reasonable adjudicator to\n\ndeny [Cortez-Mendez] relief.” Pacas-Renderos v. Sessions, 691 F. App’x 796, 803 (4th\n\nCir. 2017). Substantial evidence supports the IJ’s and BIA’s finding that Cortez-Mendez\n\ndid not establish the requisite nexus, and his application for withholding of removal was\n\nproperly denied.\n\n\n\n IV.\n\n Accordingly, Cortez-Mendez’s petition for review is\n\n DENIED.\n\n\n\n\n 11\n[END_CASE]", "role": "user" } ]
4,579,303
Brian DAVISON, Plaintiff - Appellee, v. Phyllis RANDALL, in Her Official and Individual Capacity, Defendant - Appellant, and Loudoun County Board of Supervisors, in Their Official and Individual Capacities; Leo Rogers, in His Official Capacity; Tony Buffington, in His Official Capacity; Ron Meyer, in His Official Capacity; Geary Higgins, in His Official Capacity, Defendants. Local Government Attorneys of Virginia, Inc.; International Municipal Lawyers Association ; Virginia Association of Counties; Virginia Municipal League, Amici Supporting Appellant, American Civil Liberties Union; ACLU of Virginia ; ACLU of Maryland; ACLU of North Carolina; ACLU of South Carolina; ACLU of West Virginia, Amici Supporting Appellee. Brian C. Davison, Plaintiff - Appellant, v. Phyllis Randall, in Her Official and Individual Capacity; Loudoun County Board of Supervisors, in Their Official and Individual Capacities, Defendants - Appellees, and Leo Rogers, in His Official Capacity; Tony Buffington, in His Official Capacity; Ron Meyer, in His Official Capacity; Geary Higgins, in His Official Capacity, Defendants.
Brian Davison v. Phyllis Randall
2019-01-07
17-2002; 17-2003
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Keenan, Wynn, Harris", "parties": "", "opinions": [{"author": "WYNN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2002\n\n\nBRIAN DAVISON,\n\n Plaintiff - Appellee,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity,\n\n Defendant - Appellant,\n\n and\n\nLOUDOUN COUNTY BOARD OF SUPERVISORS, In their official and\nindividual capacities; LEO ROGERS, In his official capacity; TONY\nBUFFINGTON, In his official capacity; RON MEYER, In his official capacity;\nGEARY HIGGINS, In his official capacity,\n\n Defendants.\n\n------------------------------\n\nLOCAL GOVERNMENT ATTORNEYS OF VIRGINIA, INC.;\nINTERNATIONAL MUNICIPAL LAWYERS ASSOCIATION; VIRGINIA\nASSOCIATION OF COUNTIES; VIRGINIA MUNICIPAL LEAGUE,\n\n Amici Supporting Appellant,\n\nAMERICAN CIVIL LIBERTIES UNION; ACLU OF VIRGINIA; ACLU OF\nMARYLAND; ACLU OF NORTH CAROLINA; ACLU OF SOUTH\nCAROLINA; ACLU OF WEST VIRGINIA,\n\n Amici Supporting Appellee.\n\n No. 17-2003\n\n\nBRIAN C. DAVISON,\n\n Plaintiff - Appellant,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity; LOUDOUN\nCOUNTY BOARD OF SUPERVISORS, In their official and individual\ncapacities,\n\n Defendants - Appellees,\n\n and\n\nLEO ROGERS, In his official capacity; TONY BUFFINGTON, In his official\ncapacity; RON MEYER, In his official capacity; GEARY HIGGINS, In his\nofficial capacity,\n\n Defendants.\n\n\nAppeals from the United States District Court for the Eastern District of Virginia, at\nAlexandria. James C. Cacheris, Senior District Judge. (1:16-cv-00932-JCC-IDD)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n\n\nBefore KEENAN, WYNN, and HARRIS, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Keenan\nand Judge Harris concurred. Judge Keenan wrote a separate concurring opinion.\n\n\nARGUED: Scott E. Gant, BOIES SCHILLER FLEXNER, LLP, Washington, D.C.; Leo\nP. Rogers, LOUDON COUNTY ATTORNEY, Leesburg, Virginia, for Appellant/Cross-\nAppellee. Katherine A. Fallow, KNIGHT FIRST AMENDMENT INSTITUTE AT\n\n\n 2\n\nCOLUMBIA UNIVERSITY, New York, New York, for Appellee/Cross-Appellant. ON\nBRIEF: Aaron E. Nathan, BOIES SCHILLER FLEXNER LLP, Washington, D.C., for\nAppellant/Cross-Appellee. Jameel Jaffer, Carrie DeCell, KNIGHT FIRST\nAMENDMENT INSTITUTE AT COLUMBIA UNIVERSITY, New York, New York,\nfor Appellee/Cross-Appellant. Vishal Agraharkar, AMERICAN CIVIL LIBERTIES\nUNION FOUNDATION OF VIRGINIA, Richmond, Virginia; Esha Bhandari, Vera\nEidelman, AMERICAN CIVIL LIBERTIES UNION FOUNDATION, New York, New\nYork; Susan K. Dunn, ACLU OF SC FOUNDATION, INC., Charleston, South Carolina;\nChristopher Brook, AMERICAN CIVIL LIBERTIES UNION OF NORTH CAROLINA\nLEGAL FOUNDATION, Raleigh, North Carolina; Deborah A. Jeon, ACLU\nFOUNDATION OF MARYLAND, Baltimore, Maryland; Jennifer D. Oliva, ACLU OF\nWEST VIRGINIA FOUNDATION, Charleston, West Virginia, for Amici American\nCivil Liberties Union, ACLU of Virginia, ACLU of Maryland, ACLU of North Carolina,\nACLU of South Carolina, and ACLU of West Virginia. Joshua A. Geltzer, Douglas\nLetter, Amy L. Marshak, Mary B. McCord, INSTITUTE FOR CONSTITUTIONAL\nADVOCACY AND PROTECTION GEORGETOWN UNIVERSITY LAW CENTER,\nWashington, D.C.; Kwaku A. Akowuah, Christopher C. Fonzone, Kate Heinzelman,\nSIDLEY AUSTIN LLP, Washington, D.C., for Amici Curiae First Amendment Legal\nScholars.\n\n\n\n\n 3\n\nWYNN, Circuit Judge:\n\n Phyllis Randall, Chair of the Loudoun County, Virginia, Board of Supervisors (the\n\n“Loudoun Board”), brings this appeal, arguing that the district court erred in concluding\n\nthat she violated the First Amendment rights of one of her constituents, Brian Davison,\n\nwhen she banned Davison from the “Chair Phyllis J. Randall” Facebook page she\n\nadministered. In a cross appeal, Davison principally argues that the district court erred\n\nin dismissing his procedural due process claim premised on the ban. For the reasons that\n\nfollow, we affirm.\n\n I.\n\n A.\n\n Randall has chaired the Loudoun County Board of Supervisors since January 1,\n\n2016. The day before she was sworn in as chair, Randall created the “Chair Phyllis J.\n\nRandall” Facebook Page (the “Chair’s Facebook Page”). According to Facebook, Inc.,\n\nunlike personal Facebook profiles, which are for non-commercial use and represent\n\nindividual people, Facebook “Pages”—like the Chair’s Facebook Page—“help\n\nbusinesses, organizations, and brands share their stories and connect with people.” J.A.\n\n403. “Pages are managed by people who have personal profiles,” the company explains.\n\nJ.A. 403. In addition to the Chair’s Facebook Page, Randall created and maintained two\n\nother Facebook profiles: a personal profile and a Page devoted to her campaign. Randall\n\nclassified her campaign page as belonging to a “politician” and used no designation for\n\nher personal profile, but she designated the Chair’s Facebook Page as a “governmental\n\nofficial” page. J.A. 209–10.\n\n\n 4\n\n Randall and her Chief of Staff, Jeanine Arnett, share administrative control over\n\nthe Chair’s Facebook Page, although Randall almost exclusively controls the page’s\n\ncontent. On her campaign page, Randall characterized the Chair’s Facebook Page as her\n\n“county Facebook page” stating:\n\n I really want to hear from ANY Loudoun citizen on ANY issues, request,\n criticism, complement or just your thoughts. However, I really try to keep\n back and forth conversations (as opposed to one time information items\n such as road closures) on my county Facebook page (Chair Phyllis J.\n Randall) or County email ([email protected]). Having back and\n forth constituent conversations are Foiable ([Freedom of Information Act])\n so if you could reach out to me on these mediums that would be\n appreciated.\n\nJ.A. 455 (emphasis added).\n\n The Chair’s Facebook Page includes three columns. The left column, which is\n\ntopped by a picture of Randall, includes several links to allow visitors to quickly navigate\n\nthe contents of the Chair’s Facebook Page.\n\n The middle column, which is organized in reverse chronological order similar to a\n\npersonal profile’s News Feed, is composed of posts by Randall and comments by\n\nFacebook users on those posts. Randall’s posts are almost always directed to “Loudoun,”\n\nsee, e.g., J.A. 408–10, and deal with numerous aspects of Randall’s official\n\nresponsibilities. For example, Randall used the Chair’s Facebook Page to notify the\n\npublic about upcoming Loudoun Board meetings, and the subjects to be discussed during\n\nthose meetings. Randall also used the page to inform Loudoun County residents about\n\nsignificant public safety issues. See, e.g., J.A. 412 (stating that Loudoun Board had\n\n“been informed by the Sheriff’s Office about the non-legitimate threat made on social\n\n\n\n 5\n\nmedia toward Dominion High School in Sterling”); J.A. 418 (reporting that she “ha[d]\n\nbeen briefed regarding the student falling from the water tower this morning” and\n\nadvising the public to “not make any assumptions but wait for information”). And\n\nRandall used the Chair’s Facebook Page to coordinate Loudoun County’s response to a\n\nlarge snow storm, including to communicate with constituents regarding which municipal\n\nstreets required plowing.\n\n Other posts by Randall to the Chair’s Facebook Page invited members of the\n\npublic to apply to participate on a public commission and to participate in public\n\nmeetings regarding key issues facing Loudoun County residents, such as revised flood\n\nplain zones and the Zika virus. Randall also authored posts regarding a variety of trips\n\nand meetings she had taken in furtherance of Loudoun County business. E.g., J.A. 408\n\n(reporting that Randall “address[ed] the (county) role in Treatment” at a “regional\n\nconference on Opioid and Substance Abuse Addiction”); J.A. 410 (stating that Randall\n\nrepresented Loudoun County at its “annual credit rating presentation” in New York); J.A.\n\n415 (informing public of trip to Loudoun’s “Sister City” in Germany); J.A. 426\n\n(reporting that Randall was “in Richmond lobbying for [Loudoun County’s] legislative\n\nprogram”). Finally, Randall used the page to advise the public regarding official actions\n\ntaken by the Loudoun Board. E.g., J.A. 433 (reporting that Loudoun Board “approved\n\nfunding for new breathing apparatus for our Loudoun Firefighters”); J.A. 442 (listing\n\nseveral “proclamations of note” by the Loudoun Board); J.A. 443 (informing public that\n\nLoudoun Board “adopted a budget for Fiscal Year 2017 totaling $2.46 billion for the\n\ngeneral county government and schools”). Although Randall’s posts on the Chair’s\n\n\n 6\n\nFacebook Page principally addressed her official responsibilities, a few posts addressed\n\ntopics less closely related to her official activities such as her affection for the German\n\nlanguage or pride in becoming an organ donor.\n\n Members of the public, including Davison, “liked” 1 or commented on several of\n\nRandall’s posts on the Chair’s Facebook Page. Each “like” or comment identified the\n\nname of the personal profile or Page of the authoring party. Many of the comments\n\nthanked Randall and the Loudoun Board for representing the public’s interests. Other\n\nposts by members of the public offered feedback on various issues faced by Randall and\n\nthe Loudoun Board. E.g., J.A. 427 (stating that “[p]utting recreation in a flood plain is\n\nnot a good idea”); J.A. 448 (stating that “more needs to be done with the explosion of\n\nLyme disease in Loudoun”). And other comments dealt with constituent-specific issues.\n\nE.g., J.A. 415 (constituent stating, in response to post by Randall regarding visit to\n\nLoudoun County’s “Sister City” in Germany, that constituent’s “daughter is interested in\n\nexchange programs”); J.A. 454 (stating that “there [we]re no [snow] plows to be seen” in\n\na particular neighborhood). Finally, several comments, including a number authored by\n\nDavison, criticized the Loudoun Board, generally, and Randall, in particular, for actions\n\ntaken in their official capacities. E.g., J.A. 429–30 (Davison criticizing public school\n\nsystem budget and expenditures); J.A. 438–39 (member of public criticizing\n\ngovernmental entity’s inspection of farm, claiming it failed to uncover animal abuse);\n\n\n 1\n “‘Liking’ on Facebook is a way for Facebook users to share information with\neach other.” Bland v. Roberts, 730 F.3d 368, 385 (4th Cir. 2013).\n\n\n\n 7\n\nJ.A. 449 (Davison characterizing question he posed at Loudoun Board and Loudoun\n\nSchool Board joint town hall). On some occasions, Randall responded to these\n\ncomments or criticisms.\n\n In the right column of the Chair’s Facebook Page, the page is identified as a\n\n“government official” page. It provides contact information for Randall’s county office,\n\nincluding her office telephone number, Randall’s official county email address, and the\n\ninternet address for the official county website. The column also identifies how many\n\nand which Facebook personal profiles and Pages “like” and “follow” the Chair’s\n\nFacebook Page. 2 And the column includes a list of personal profiles and Pages “liked”\n\nby the Chair’s Facebook Page.\n\n Randall publicized the Chair’s Facebook Page in her official “Chair Phyllis J.\n\nRandall” newsletter, which is prepared by County employees, hosted on the County’s\n\nwebsite, and distributed to Loudoun citizens using Randall’s official county email\n\naccount. The newsletter ends with the words “STAY CONNECTED” and a Facebook\n\nicon that hyperlinks to the Chair’s Facebook Page. Randall also highlighted the Chair’s\n\nFacebook Page in “Winter Storm Information” notices emailed from her official county\n\naccount to Loudoun County residents, advising recipients to “Visit [the Chair’s Facebook\n\nPage] for Updates.” J.A. 341–42, 344.\n\n 2\n According to Facebook, “[l]iking a Facebook Page means you are connecting to\nthat Page. When you connect to a Page, it will appear in [a user’s] timeline and [the user]\nwill appear on the page as a person who likes that Page. The Page will also be able to\npost content into [the user’s] News Feed.” Bland, 730 F.3d at 385 (internal quotation\nmarks omitted).\n\n\n\n 8\n\n Davison, an outspoken resident of Loudoun County, apparently largely focuses his\n\ncivic engagement and expression on “the funding and . . . management of public\n\nschools.” J.A. 95. To that end, he has repeatedly expressed concern about “School Board\n\nmembers failing to disclose personal conflicts as required by law before voting on\n\nfinancial transactions before the School Board.” J.A. 96.\n\n On February 3, 2016, Davison attended a Loudoun town hall meeting that\n\nincluded the Loudoun County School Board and Randall. At the meeting, Davison\n\nsubmitted a question implying that certain School Board members had acted unethically\n\nin approving financial transactions. Randall volunteered to answer the question but\n\ncharacterized it as a “set-up question” that she did not “appreciate.” J.A. 103. Shortly\n\nafter Randall answered the question—and while the town hall meeting was still\n\nongoing—Davison posted a message on Twitter in which he tagged Randall:\n\n“@ChairRandall ‘set up question’? You might want to strictly follow FOIA and the\n\nCOIA as well.” J.A. 470–71.\n\n Later that evening, Randall posted about the town hall meeting on the Chair’s\n\nFacebook Page, describing “what was generally discussed at the meeting.” J.A. 268. In\n\nresponse, Davison then used one of the Facebook Pages he manages through his personal\n\nFacebook profile—“Virginia SGP,” which Davison frequently uses to post political\n\ncommentary—to comment on Randall’s post about the town hall meeting. Although\n\nneither Davison nor Randall remember the precise content of Davison’s comment,\n\nRandall testified that it contained “accusations” regarding School Board members’ and\n\ntheir families’ putative conflicts of interest related to municipal financial transactions,\n\n\n 9\n\nsuggesting, in Randall’s opinion, that School Board members had been “taking kickback\n\nmoney.” See J.A. 268–69, 289–90. Randall stated that she “had no idea if any of th[e]\n\n[accusations] w[ere] correct,” but she determined that the post was “probably not\n\nsomething [she] want[ed] to leave” on the Chair’s Facebook Page. J.A. 269. Randall\n\nthen “deleted the whole post,” including her original post regarding the town hall\n\nmeeting, Davison’s comment and replies thereto, and all other public comments. J.A.\n\n269. Randall also banned Davison’s Virginia SGP Page from the Chair’s Facebook Page,\n\nwhich precluded Davison from using his Virginia SGP Page from commenting on the\n\nChair’s Facebook Page. The next morning, about twelve hours later, Randall\n\nreconsidered her actions and unbanned Davison’s Virginia SGP Page.\n\n B.\n\n On November 3, 2016, Davison filed an amended complaint seeking declaratory\n\nand injunctive relief under 42 U.S.C. § 1983 against Randall, in both her official and\n\nindividual capacities, and the Loudoun Board alleging that the “banning of [Davison]\n\nfrom commenting on [the Chair’s Facebook Page] is viewpoint discrimination.” J.A. 31.\n\nDavison further alleged that the ban violated his procedural due process rights protected\n\nby the Fourteenth Amendment because “Randall blocked Davison’s constitutionally\n\nprotected speech on [the Chair’s Facebook Page], a limited public forum, without prior\n\nnotice and without providing an opportunity for appealing [her] decision.” J.A. 32.\n\nDavison did not challenge Randall’s deletion of his post.\n\n On March 6, 2017—four days before the close of discovery and approximately\n\ntwo months before trial—Davison moved for leave to amend his complaint a second time\n\n\n 10\n\nto add claims under the Virginia Constitution that were materially indistinguishable from\n\nhis previously asserted First and Fourteenth Amendment claims premised on the ban, as\n\nwell as a separate First Amendment claim against the Loudoun Board. Davison’s\n\nproposed new First Amendment claim theorized that the County violated his free speech\n\nrights by choosing to use Facebook Pages as public forums, when Facebook allows\n\nprivate users to restrict access to their posts, including posts to any Page a municipality\n\ndesignates as a limited public forum. Pl.’s Mem. in Supp. of Mot. for Leave to File\n\nSecond Am. Compl. 3–9, Davison v. Loudoun County Bd. of Supervisors, 16-cv-932-\n\nJCC-IDD, ECF No. 68. The district court referred the motion to a magistrate judge, who\n\ngranted leave to amend regarding the claims under the Virginia Constitution but denied\n\nleave as to the new First Amendment claim against the Loudoun Board. Davison lodged\n\nobjections to the magistrate judge’s partial denial of leave to amend, which objections the\n\ndistrict court overruled.\n\n Around the same time, Randall and the Loudoun Board each moved for summary\n\njudgment. The Loudoun Board asserted that the municipality could not be held liable for\n\nRandall’s banning of Davison from the Chair’s Facebook Page because the Chair’s\n\nFacebook Page was not an official municipal page and because Randall, not the Loudoun\n\nBoard as a body, was solely responsible for creating and administering the Chair’s\n\nFacebook Page. The Loudoun Board and Randall further asserted that the Chair’s\n\nFacebook Page did not amount to a public forum, and therefore Randall’s ban of\n\nDavison’s Virginia SGP Page did not implicate his free speech or procedural due process\n\nrights. Finally, Randall asserted that she was entitled to qualified immunity.\n\n\n 11\n\n On May 10, 2017, the district court granted summary judgment in favor of the\n\nLoudoun Board, dismissing it from the suit. But as to Randall, the district court\n\nconcluded that Davison’s evidence established a material dispute of fact as to whether the\n\nChair’s Facebook Page amounted to a limited public forum and whether Randall, in her\n\nindividual capacity, acted under color of state law in banning Davison from the Chair’s\n\nFacebook Page. Davison v. Loudoun Cty. Bd. of Supervisors, No. 1:16-cv-932, 2017 WL\n\n1929406, at *6–9 (E.D. Va. May 10, 2017). The district court also rejected Randall’s\n\nqualified immunity argument. Id. at *8.\n\n Following a one-day bench trial of Davison’s claims against Randall, the district\n\ncourt issued a memorandum opinion and order awarding judgment in Davison’s favor on\n\nhis claims under the First Amendment and the analogous free speech provision in the\n\nVirginia Constitution. See Davison v. Loudoun Cty. Bd. of Supervisors, 267 F. Supp. 3d\n\n702, 714–18 (E.D. Va. 2017). The district court further entered judgment in Randall’s\n\nfavor on Davison’s federal and state procedural due process claims. Id. at 719–22. As to\n\nremedy, the district court denied Davison’s request for injunctive relief but granted\n\nDavison’s request for a declaratory judgment to resolve the “uncertainty regarding the\n\nlegal status of [the Chair’s Facebook Page].” Id. at 723.\n\n Randall and Davison, respectively, filed this appeal and cross appeal.\n\n II.\n\n On appeal, Randall argues that (A) Davison failed to establish standing to obtain\n\nprospective declaratory relief based on Randall’s alleged First Amendment violation; (B)\n\nthe district court erred in concluding that Randall acted under “color of state law” when\n\n\n 12\n\nshe banned Davison’s Virginia SGP Page from the Chair’s Facebook Page; and (C) the\n\ndistrict court erred in concluding that Randall’s banning of Davison’s Virginia SGP Page\n\nviolated the First Amendment.\n\n A.\n\n Notwithstanding that she did not challenge Davison’s standing below—and\n\ntherefore that the district court never squarely addressed his standing—Randall now\n\nargues that Davison failed to establish Article III standing to support the district court’s\n\naward of prospective declaratory relief. Even though Defendants did not challenge\n\nDavison’s standing below, “standing to sue is a jurisdictional issue of constitutional\n\ndimensions, and it may be raised and addressed for the first time on appeal.” Hodges v.\n\nAbraham, 300 F.3d 432, 443 (4th Cir. 2002). This Court reviews de novo “whether a\n\ndistrict court possessed jurisdiction in a declaratory judgment proceeding.” Volvo Const.\n\nEquip. N. Am., Inc. v. CLM Equip. Co., Inc., 386 F.3d 581, 591 (4th Cir. 2004).\n\n To establish Article III standing, a plaintiff must prove that: “1) he or she suffered\n\nan ‘injury in fact’ that is concrete and particularized, and is actual or imminent; 2) the\n\ninjury is fairly traceable to the challenged action of the defendant; and 3) the injury likely\n\nwill be redressed by a favorable decision.” Friends of the Earth, Inc. v. Gaston Copper\n\nRecycling Corp., 629 F.3d 387, 396 (4th Cir. 2011). Randall does not dispute that any\n\ninjury Davison suffered is fairly traceable to her decision to ban him from the Chair’s\n\nFacebook Page. Nor does Randall dispute that any such injury would be remedied by a\n\nfavorable decision. Rather, Randall claims that Davison failed to adduce evidence\n\n\n\n\n 13\n\nestablishing that he suffered an “injury in fact” sufficient to support prospective\n\ndeclaratory relief.\n\n “Injury in fact is ‘an invasion of a legally protected interest’ that is ‘concrete and\n\nparticularized’ and ‘actual or imminent, not conjectural or hypothetical.’” Kenny v.\n\nWilson, 885 F.3d 280, 287 (4th Cir. 2018) (quoting Spokeo, Inc. v. Robins, 136 S. Ct.\n\n1540, 1548 (2016)). Because “‘[p]ast exposure to illegal conduct does not in itself show\n\na present case or controversy regarding injunctive relief . . . if unaccompanied by any\n\ncontinuing, present adverse effects,’” a plaintiff seeking “declaratory or injunctive relief .\n\n. . must establish an ongoing or future injury in fact.” Id. at 287–88 (quoting O’Shea v.\n\nLittleton, 414 U.S. 488, 495–96 (1974)). Significantly, this Court—along with several\n\nother circuits—has held that “standing requirements are somewhat relaxed in First\n\nAmendment cases,” particularly regarding the injury-in-fact requirement. Cooksey v.\n\nFutrell, 721 F.3d 226, 235 (4th Cir. 2013) (collecting cases).\n\n In Kenny v. Wilson, 885 F.3d 280 (4th Cir. 2018), this Court addressed what\n\nevidence a plaintiff seeking relief under the First Amendment, like Davison, must put\n\nforward to establish a future injury-in-fact adequate to confer Article III standing to\n\nobtain prospective declaratory relief. In Kenny, several high school students lodged First\n\nAmendment challenges to two South Carolina disorderly conduct statutes. Id. at 284.\n\nThis Court explained that “there is a sufficiently imminent injury in fact if plaintiffs\n\nallege [1] ‘an intention to engage in a course of conduct arguably affected with a\n\nconstitutional interest, but proscribed by a statute, and [2] there exists a credible threat of\n\nprosecution thereunder.’” Id. at 288 (quoting Babbitt v. Farm Workers Nat’l Union, 442\n\n\n 14\n\nU.S. 289, 298 (1979)). The Kenny plaintiffs satisfied the first prong because they “attend\n\nschool” and “attending school inevitably involves expressive conduct” that implicates the\n\ndisorderly conduct statutes. Id. As to the second element—whether the students alleged\n\na “credible threat of future enforcement”—we held that such a threat exists so long as it\n\n“is not imaginary or wholly speculative, chimerical, or wholly conjectural.” Id. (internal\n\nquotation marks, citations, and alterations omitted). “[P]ast enforcement against the same\n\nconduct is good evidence that the threat of enforcement is not chimerical.” Id. (quoting\n\nSusan B. Anthony List v. Driehaus, 134 S. Ct. 2334, 2345 (2014)). “Threat of\n\nprosecution is especially credible when defendants have not ‘disavowed enforcement’ if\n\nplaintiffs engage in similar conduct in the future.” Id. (quoting Driehaus, 134 S. Ct. at\n\n2345). Applying this standard, we held that the plaintiffs alleged a credible threat of\n\nenforcement “because these three plaintiffs regularly attend schools where they allege\n\nthere may be future encounters with school resource officers or other law enforcement;\n\nthey have been prosecuted under the laws in the past; and the defendants have not\n\ndisavowed enforcement if plaintiffs engage in similar conduct in the future.” Id. at 289.\n\n Under Kenny, Davison’s evidence established his standing to obtain prospective\n\ndeclaratory relief. Relevant to the first prong—whether Davison intends to engage in a\n\ncourse of conduct “arguably” impacted by the challenged conduct, Babbitt, 442 U.S. at\n\n298—the district court found, in awarding Davison declaratory relief, that he “continues\n\nto avail himself” of the Chair’s Facebook Page and that Davison is “active in local\n\npolitics, and has a particular interest in what he believes to be corruption on the part of\n\nLoudoun County’s school board.” Davison, 267 F. Supp. 3d at 707, 723. Accordingly,\n\n\n 15\n\nthe evidence establishes that Davison continues to engage in a course of conduct—\n\nnamely, posting about alleged municipal corruption on the Chair’s Facebook Page—\n\nlikely to be impacted by Randall’s allegedly unconstitutional approach to managing the\n\npage.\n\n Turning to the second prong—whether there is a credible threat of enforcement—\n\nRandall previously blocked Davison from the Chair’s Facebook Page based on the\n\ncontent of his posts, providing “good evidence that the threat of enforcement is not\n\nchimerical.” Driehaus, 134 S. Ct. at 2345 (internal quotation marks omitted).\n\nAdditionally, Randall testified that she continues to believe she can ban Davison and\n\nothers from the Chair’s Facebook Page based on their views without triggering the First\n\nAmendment at all. See J.A. 277 (Randall stating she would “be happy to” ban other\n\ncommenters on her “Chair’s Facebook” page); J.A. 250 (Randall testifying that\n\ncomments “attacking another person” would not be allowed on her “Chair’s Facebook”\n\npage). To that end, in awarding Davison declaratory relief, the district court found that\n\nRandall “maintains she is permitted to administer this Facebook page as a purely personal\n\npage.” Davison, 267 F. Supp. 3d at 723. Accordingly, Davison established that he has\n\nbeen subject to past enforcement and that Randall has not “disavowed” future\n\nenforcement, which, under Kenny, is sufficient to establish a credible threat of\n\nenforcement. Cf. City of Lakewood v. Plain Dealer Pub. Co., 486 U.S. 750, 757 (1988)\n\n(“[T]he mere existence of the licensor’s unfettered discretion, coupled with the power of\n\nprior restraint, intimidates parties into censoring their own speech, even if the discretion\n\nand power are never actually abused.”).\n\n\n 16\n\n In sum, Davison’s evidence demonstrated—and the district court found—that\n\nDavison intends to continue to use the Chair’s Facebook Page and that Davison faces a\n\ncredible threat of future enforcement. See Davison, 267 F. Supp. 3d at 723.\n\nAccordingly, Davison adduced facts establishing an injury in fact sufficient to justify the\n\nprospective declaratory relief awarded by the district court.\n\n B.\n\n Next, Randall asserts that the district court erred in concluding, with regard to\n\nDavison’s individual capacity First Amendment claim, that Randall acted “under color of\n\nstate law,” as that phrase is used in Section 1983, in administering the Chair’s Facebook\n\nPage and banning Davison from that page. “This Court reviews judgments stemming\n\nfrom a bench trial under a mixed standard: factual findings are reviewed for clear error,\n\nwhereas conclusions of law are reviewed de novo.” Helton v. AT&T Inc., 709 F.3d 343,\n\n350 (4th Cir. 2013). Whether, under the undisputed facts, Randall acted under color of\n\nstate law is a legal question this Court reviews de novo. Rossignol v. Voorhaar, 316 F.3d\n\n516, 523 (4th Cir. 2003).\n\n To state a claim under Section 1983, a plaintiff must show that the alleged\n\nconstitutional deprivation at issue occurred because of action taken by the defendant\n\n“under color of . . . state law.” Philips v. Pitt Cty. Mem’l Hosp., 572 F.3d 176, 180 (4th\n\nCir. 2009). “The traditional definition of acting under color of state law requires that the\n\ndefendant in a § 1983 action have exercised power ‘possessed by virtue of state law and\n\nmade possible only because the wrongdoer is clothed with the authority of state law.’”\n\nWest v. Atkins, 487 U.S. 42, 49 (1988) (quoting United States v. Classic, 313 U.S. 299,\n\n\n 17\n\n326 (1941)). Section 1983’s “color-of-law prerequisite is synonymous with the more\n\nfamiliar state-action requirement” applicable to Fourteenth Amendment claims, “and the\n\nanalysis for each is identical.” Pitt Cty. Mem’l Hosp., 572 F.3d at 180. Both inquiries\n\ndemand that “the conduct allegedly causing the deprivation of a federal right be fairly\n\nattributable to the State.” Holly v. Scott, 434 F.3d 287, 292 (4th Cir. 2006) (quoting\n\nLugar v. Edmondson Oil Co., Inc., 457 U.S. 922, 937 (1982)).\n\n “[T]here is no specific formula for determining whether state action is present.”\n\nId. at 292 (internal quotation marks omitted). Rather, “[w]hat is fairly attributable [to the\n\nstate]”—i.e., what constitutes action under color of state law—“is a matter of normative\n\njudgment, and the criteria lack rigid simplicity.” Id. (internal quotation marks omitted).\n\nCourts must examine the “totality of the circumstances,” id. (internal quotation marks\n\nomitted), to determine if the action at issue “bore a ‘sufficiently close nexus’ with the\n\nState to be ‘fairly treated as that of the State itself,’” Rossignol, 316 F.3d at 525 (quoting\n\nJackson v. Metro. Edison Co., 419 U.S. 345, 351 (1974)).\n\n Although no one factor is determinative, this Court has held that a defendant’s\n\npurportedly private actions bear a “sufficiently close nexus” with the State to satisfy\n\nSection 1983’s color-of-law requirement when the defendant’s challenged “actions are\n\nlinked to events which arose out of his official status.” Id. at 524. When a defendant’s\n\n“status” as a public official “enabled [her] to execute [a challenged action] in a manner\n\nthat private citizens never could have,” then the action also is more likely to be treated as\n\nattributable to the state. Id. at 526; see also Martinez v. Colon, 54 F.3d 980, 986 (1st Cir.\n\n1995) (“[S]ection 1983 is . . . implicated . . . [when] the conduct is such that the actor\n\n\n 18\n\ncould not have behaved in that way but for the authority of his office.”); Goldstein v.\n\nChestnut Ridge Volunteer Fire Co., 218 F.3d 337, 343 (4th Cir. 2000) (holding that\n\nchallenged conduct is more likely to amount to state action when “the injury caused is\n\naggravated in a unique way by the incidents of governmental authority” (internal\n\nquotation marks omitted)). Likewise, an official’s conduct is more likely to amount to\n\nstate action when it “occurs in the course of performing an actual or apparent duty of his\n\noffice.” Martinez, 54 F.3d at 986. And the challenged action of a defendant\n\ngovernmental official is likely to be treated as taken under color of law when the official\n\n“use[d] the power and prestige of his state office to damage the plaintiff.” Harris v.\n\nHarvey, 605 F.2d 330, 337 (7th Cir. 1979). In the context of an alleged First Amendment\n\nviolation, in particular, this Court has found that a challenged action by a governmental\n\nofficial is fairly attributable to the state when “the sole intention” of the official in taking\n\nthe action was “to suppress speech critical of his conduct of official duties or fitness for\n\npublic office.” Rossignol, 316 F.3d at 524.\n\n Here, after thoroughly analyzing the totality of the circumstances surrounding\n\nRandall’s creation and administration of the Chair’s Facebook Page and banning of\n\nDavison from that page, the district court concluded that Randall acted under color of\n\nstate law. Davison, 267 F. Supp. 3d at 723. We agree.\n\n Randall created and administered the Chair’s Facebook Page to further her duties\n\nas a municipal official. She used the Chair’s Facebook Page “as a tool of governance,”\n\nid. at 713: through the Chair’s Facebook Page, Randall provides information to the public\n\n\n\n\n 19\n\nabout her and the Loudoun Board’s official activities and solicits input from the public on\n\npolicy issues she and the Loudoun Board confront. See supra Part I.A.\n\n For instance, Randall used the Chair’s Facebook Page to inform the public about\n\nserious public safety events and to keep her constituents abreast of the County’s response\n\nto a snowstorm and to coordinate snow removal activities. And, as the district court\n\ncorrectly emphasized, Randall\n\n swathe[d] the [Chair’s Facebook Page] in the trappings of her office.\n Among other things, (1) the title of the page includes [Randall]’s title; (2)\n the page is categorized as that of a government official; (3) the page lists as\n contact information [Randall]’s official County email address and the\n telephone number of [Randall]’s County office; (4) the page includes the\n web address of [Randall]’s official County website; (5) many—perhaps\n most—of the posts are expressly addressed to “Loudoun,” [Randall]’s\n constituents; (6) [Randall] has submitted posts on behalf of the [Loudoun\n Board] as a whole; (7) [Randall] has asked her constituents to use the\n [Chair‘s Facebook Page] as a channel for “back and forth constituent\n conversations”; and (8) the content posted has a strong tendency toward\n matters related to [Randall]’s office.\n\nDavison, 267 F. Supp. 3d at 714. A private citizen could not have created and used the\n\nChair’s Facebook Page in such a manner. Rossignol, 316 F.3d at 526. Put simply,\n\nRandall clothed the Chair’s Facebook Page in “the power and prestige of h[er] state\n\noffice,” Harris, 605 F.2d at 337, and created and administered the page to “perform[]\n\nactual or apparent dut[ies] of h[er] office,” Martinez, 54 F.3d at 986.\n\n Additionally, the specific actions giving rise to Davison’s claim—Randall’s\n\nbanning of Davison’s Virginia SGP Page—“are linked to events which arose out of h[er]\n\nofficial status.” Rossignol, 316 F.3d at 524. Randall’s post to the Chair’s Facebook Page\n\nthat prompted Davison’s comment informed the public about what happened at the\n\n\n\n 20\n\nLoudoun Board and Loudoun County School Board’s joint meeting. And Davison’s\n\ncomment also dealt with an issue related to that meeting and of significant public\n\ninterest—School Board members’ alleged conflicts of interest in approving financial\n\ntransactions. That Randall’s ban of Davison amounted to an effort “to suppress speech\n\ncritical of [such members’] conduct of [their] official duties or fitness for public office”\n\nfurther reinforces that the ban was taken under color of state law. Id. at 525. Considering\n\nthe totality of these circumstances, the district court correctly held that Randall acted\n\nunder color of state law in banning Davison from the Chair’s Facebook Page.\n\n C.\n\n Third, Randall argues that the district court erred in ruling in Davison’s favor on\n\nhis individual capacity First Amendment claim against Randall. Randall principally\n\nchallenges the district court’s conclusion that the Chair’s Facebook Page constitutes a\n\n“public forum” under traditional First Amendment law. We review this legal question de\n\nnovo. See Helton, 709 F.3d at 350.\n\n Under long-established First Amendment law, governmental entities are “strictly\n\nlimited” in their ability to regulate private speech in public fora. Pleasant Grove City,\n\nUtah v. Summum, 555 U.S. 460, 469 (2009). The Supreme Court has recognized two\n\ncategories of public fora: “traditional public forums” and “limited (or designated) public\n\nforums.” Am. Civil Liberties Union v. Mote, 423 F.3d 438, 443 (4th Cir. 2005).\n\n“Traditional” public forums—“such as streets, sidewalks, and parks”—“have the\n\ncharacteristics of a public thoroughfare, a purpose that is compatible with expressive\n\nconduct, as well as a tradition and history of being used for expressive public conduct.”\n\n\n 21\n\nId. “Limited” or “designated” forums are forums that are “not traditionally public, but\n\n[that] the government has purposefully opened to the public, or some segment of the\n\npublic, for expressive activity.” Id. Accordingly, the hallmark of both types of public\n\nfora—what renders the fora “public”—is that the government has made the space\n\navailable—either by designation or long-standing custom—for “expressive public\n\nconduct” or “expressive activity,” and the space is compatible with such activity. Id.\n\n“Conversely, a non-public forum is one that has not traditionally been open to the public,\n\nwhere opening it to expressive conduct would ‘somehow interfere with the objective use\n\nand purpose to which the property has been dedicated.’” Id. (quoting Warren v. Fairfax\n\nCty., 196 F.3d 186, 190–91 (4th Cir. 1999)).\n\n Although neither the Supreme Court nor any Circuit has squarely addressed\n\nwhether, and in what circumstances, a governmental social media page—like the Chair’s\n\nFacebook Page—constitutes a public forum, 3 aspects of the Chair’s Facebook Page bear\n\nthe hallmarks of a public forum. Randall “intentionally open[ed the public comment\n\nsection of the Chair’s Facebook Page] for public discourse,” Cornelius v. NAACP Legal\n\nDefense & Educ. Fund, Inc., 473 U.S. 788, 802 (1985), inviting “ANY Loudoun citizen”\n\n 3\n In addition to the court below, two other district courts have considered whether\na government official’s social media page constituted a public forum. Those courts\nreached conflicting results. Compare Morgan v. Bevin, 298 F. Supp. 3d 1003, 1010 (E.D.\nKy. 2018) (holding that First Amendment forum analysis did not apply to restrictions on\nspeech in the official Facebook and Twitter pages of the Governor of Kentucky), with\nKnight First Amend. Inst. at Colum. Univ. v. Trump, 302 F. Supp. 3d 541, 573 (S.D.N.Y.\n2018) (holding that the interactive component of the President’s Twitter account, as\nopposed to the President’s tweets themselves, constituted a designated public forum),\nappeal docketed, No. 18-1691 (2d Cir. Oct. 24, 2018).\n\n\n\n 22\n\nto make posts to the comments section of the Chair’s Facebook Page—the interactive\n\ncomponent of the page—“on ANY issues, request, criticism, complement or just your\n\nthoughts,” J.A. 455. Randall placed no restrictions on the public’s access to the page or\n\nuse of the interactive component of the Chair’s Facebook Page. And, in accordance with\n\nRandall’s invitation, the public made numerous posts on matters of public concern.\n\n The Chair’s Facebook Page also is “compatib[le] with expressive activity.”\n\nCornelius, 473 U.S. at 802. “Congress [has] recognized the internet and interactive\n\ncomputer services as offering ‘a forum for a true diversity of political discourse, unique\n\nopportunities for cultural development, and myriad avenues for intellectual activity.’”\n\nZeran v. Am. Online, Inc., 129 F.3d 327, 330 (4th Cir. 1997) (quoting 47 U.S.C. §\n\n230(a)(3)); cf. Bland, 730 F.3d at 386 (finding post to campaign Facebook page\n\n“constituted pure speech”). And the Supreme Court recently analogized social media\n\nsites, like the Chair’s Facebook Page, to “traditional” public forums, characterizing the\n\ninternet as “the most important place[] (in a spacial sense) for the exchange of views.”\n\nPackingham v. North Carolina, 137 S. Ct. 1730, 1735 (2017). An “exchange of views”\n\nis precisely what Randall sought—and what in fact transpired—when she expressly\n\ninvited “ANY Loudoun citizen” to visit the page and comment “on ANY issues,” and\n\nreceived numerous such posts and comments. J.A. 455.\n\n Randall nevertheless argues that traditional public forum analysis should not apply\n\nto the Chair’s Facebook Page for two reasons: (1) the Chair’s Facebook Page is “a private\n\nwebsite” and therefore does not constitute “public property” susceptible to forum\n\nanalysis, and (2) the Chair’s Facebook Page, in its entirety, constitutes “government\n\n\n 23\n\nspeech” properly analyzed under the framework set forth in Pleasant Grove. Randall’s\n\nBr. at 19–21, 29–31. We disagree.\n\n Even assuming the intangible space at issue is “private property,” as Randall\n\nclaims—which is not at all clear from the record before us 4—the Supreme Court never\n\nhas circumscribed forum analysis solely to government-owned property. For example, in\n\nCornelius, the Court recognized that forum analysis applies “to private property\n\ndedicated to public use.” Cornelius, 473 U.S. at 801 (emphasis added); see also\n\nChristian Legal Soc’y Chapter of the Univ. of Cal. v. Martinez, 561 U.S. 661, 679 (2010)\n\n(“[T]his Court has employed forum analysis to determine when a governmental entity, in\n\nregulating property in its charge, may place limitations on speech.” (emphasis added)).\n\n 4\n The Facebook “platform” and the “software” that underlies that platform is,\naccording to Facebook’s Terms of Service, property of Facebook, Inc. Terms of Service,\nFacebook, https://www.facebook.com/terms.php (last visited Jan. 4, 2019). Facebook’s\nTerms of Service further provide that users “own the content [they] create and share on\nFacebook and the other Facebook Products,” including Pages. Id. There would seem to\nbe a good argument, therefore, that content created, and posted to Facebook, by\ngovernment officials performing the functions and duties of their offices constitutes\ngovernment property. Cf. Solomons v. United States, 137 U.S. 342, 346–48 (1890)\n(holding that intellectual property created by government employee in the course of his\nofficial duties constituted government property because “[i]f one is employed to devise or\nperfect an instrument, or a means for accomplishing a prescribed result, he cannot, after\nsuccessfully accomplishing the work for which he was employed, plead title thereto as\nagainst his employer”). Likewise, under Facebook’s Terms of Service, the posts and\ncomments by individual Facebook users—like Davison—to a Facebook Page—like the\nChair’s Facebook Page—constitute property of those users. Accordingly, a single\nFacebook Page—including the Chair’s Facebook Page—encompasses a web of property\nrights, some of which may lie with the government. We need not—and thus do not—\ndecide with whom these property rights lie in this particular case, however, because we\nhold that even assuming the Chair’s Facebook Page constitutes private property, Randall,\nacting under color of state law, exercised control over the aspects of that page giving rise\nto Davison’s claim.\n\n\n\n 24\n\nAnd the Supreme Court and lower courts have held that private property, whether\n\ntangible or intangible, constituted a public forum when, for example, the government\n\nretained substantial control over the property under regulation or by contract. See, e.g.,\n\nSe. Promotions, Ltd. v. Conrad, 420 U.S. 546, 547, 555 (1975) (holding that “a privately\n\nowned Chattanooga theater under long-term lease to the city” was a “public forum[]\n\ndesigned for and dedicated to expressive activities”); Halleck v. Manhattan Community\n\nAccess Corp., 882 F.3d 300, 306–07 (2d Cir. 2018) (holding that public access television\n\nchannels operated by a private non-profit corporation constituted public forums), cert.\n\ngranted 139 S. Ct. 360 (2018) (mem.); First Unitarian Church of Salt Lake City v. Salt\n\nLake City Corp., 308 F.3d 1114, 1122 (10th Cir. 2002) (“[F]orum analysis does not\n\nrequire that the government have a possessory interest in or title to the underlying land.\n\nEither government ownership or regulation is sufficient for a First Amendment forum of\n\nsome kind to exist.”); Freedom from Religion Foundation, Inc. v. City of Marshfield,\n\nWis., 203 F.3d 487, 494 (7th Cir. 2000) (holding that private property abutted by public\n\npark constituted public forum).\n\n Significantly, even assuming the relevant aspects of the Chair’s Facebook Page\n\nconstitute private property—which, again, is not entirely clear from the record before\n\nus—Randall, acting under color of state law, retained and exercised significant control\n\nover the page. She created the Chair’s Facebook Page. She designated the page as\n\nbelonging to a “governmental official.” She clothed the page in the trappings of her\n\npublic office. She chose to list her official contact information on the page. And she\n\n\n\n\n 25\n\ncurated the links in the left column of the page and the lists of Facebook Pages or profiles\n\n“liked” by the Chair’s Facebook Page in the right column.\n\n Of particular importance, Randall had complete control over the aspect of the\n\nChair’s Facebook Page giving rise to Davison’s challenge because, as administrator of\n\nthe page, Randall had authority to ban Facebook profiles or Pages from using the Chair’s\n\nFacebook Page—and, therefore, the interactive component of the page—authority she\n\nexercised in banning Davison’s Virginia SGP Page. Cf. Knight, 302 F. Supp. 3d at 566–\n\n67 (holding that the interactive component of the President’s Twitter account constituted\n\npublic forum because the President and his advisors “exercise control over various\n\naspects of the . . . account,” including the power to block other users from accessing the\n\naccount).\n\n The Second Circuit’s decision in Halleck dealing with privately operated public\n\naccess television channels is instructive. Federal law allows cable franchising authorities\n\nto require cable operators to designate channel capacity for public use. Halleck, 882 F.3d\n\nat 302. Likewise, New York regulations oblige cable operators to designate at least one\n\nchannel for full-time public use. Id. Pursuant to that authority, the City of New York\n\nentered into a cable franchise agreement with a cable company requiring the company to\n\nmake available four public access channels, which channels were operated by a private,\n\nnon-profit corporation, MNN. Id. Several producers of public access programming sued\n\nMNN, alleging that MNN violated the producers’ First Amendment rights by indefinitely\n\nsuspending them from using the public access channels “because of disapproval of the\n\ncontent of a TV program” they had submitted for airing. Id.\n\n\n 26\n\n The Second Circuit concluded that the public access channels constituted a public\n\nforum, notwithstanding that they were operated by a private company. Id. at 306–08.\n\nThe court reached that conclusion for two reasons. First, it pointed to the similarities\n\nbetween public access channels and traditional public forums, like parks, describing “[a]\n\npublic access channel [a]s the electronic version of the public square.” Id. at 306.\n\nSecond, the court emphasized the extensive government involvement with, and control\n\nover, public access channels by virtue of the federal and state regulatory schemes. See id.\n\n(“[W]here, as here, federal law authorizes setting aside channels to be ‘the electronic\n\nmarketplace of ideas,’ state regulation requires cable operators to provide at least one\n\npublic access channel, a municipal contract requires a cable operator to provide four such\n\nchannels, and a municipal official has designated a private corporation to run those\n\nchannels, those channels are public forums.” (emphasis added)).\n\n Although not subject to the extensive federal and state regulatory regime\n\napplicable in Halleck, 5 the Chair’s Facebook Page is in many ways analogous to the\n\nprivately-operated public access channels considered by the Second Circuit. Just as the\n\nfederal government sought to establish an “electronic marketplace of ideas” by\n\nmandating provision of public access channels, Randall expressly sought to—and did, in\n\n\n 5\n The federal Communications Decency Act allows private online intermediaries,\nlike Facebook, the ability to moderate content by providing such intermediaries with\nbroad immunity from user-generated content posted on their sites. 47 U.S.C. § 230. This\nCourt has recognized that an “important purpose of § 230 was to encourage service\nproviders to self-regulate the dissemination of offensive material over their services.”\nZeran, 129 F.3d at 331.\n\n\n\n 27\n\nfact—create an “electronic marketplace of ideas” by inviting “ANY” constituent to post\n\nto the Chair Page on “ANY issues.” J.A. 455. Likewise, just as the City of New York\n\nchose to have a private corporation operate the public access channels, Randall chose to\n\ncreate her electronic marketplace of ideas, the Chair’s Facebook Page, on a private\n\nplatform, Facebook. Indeed, the present case provides a stronger basis for treating the\n\ninteractive component of the Chair’s Facebook Page as a public forum because whereas\n\nthe private corporation in Halleck, MNN, exercised control over the aspect of the public\n\naccess channel giving rise to the First Amendment claim—banning the public access\n\nprogram producer—a public official, Randall exercised unconstrained control over the\n\naspect of the Chair’s Facebook Page giving rise to Davison’s claim—banning of other\n\nFacebook profiles and Pages. 6\n\n\n 6\n On October 12, 2018, the Supreme Court granted MNN’s petition for writ of\ncertiorari in Halleck. 139 S. Ct. 360. MNN’s petition presented two questions: (1)\n“[w]hether the Second Circuit erred in rejecting th[e Supreme] Court’s state actor tests\nand instead creating a per se rule that private operators of public access channels are state\nactors subject to constitutional liability” and (2) “[w]hether the Second Circuit erred in\nholding—contrary to the Sixth and D.C. Circuits—that private entities operating public\naccess televisions stations are state actors for constitutional purposes where the state has\nno control over the private entity’s board or operations.” Petition for Writ of Certiorari i,\nManhattan Community Access Corp. v. Halleck, --- S. Ct. --- (No. 17-1702). MNN’s\nargument before the Supreme Court, therefore, focuses on the Second Circuit’s\ndetermination that MNN constituted a state actor, not the court’s determination that the\npublic access channels constituted a public forum.\n\n Although not identified as an issue on appeal, MNN’s petition also took issue with\nthe Second Circuit’s determination that the public access channels operated by MNN\nconstituted a public forum. But that contention was entirely derivative of its state action\nargument. In particular, MNN objected to the Second Circuit’s public forum conclusion\nonly because the public access channels were privately operated and because, in its\nopinion, the Second Circuit’s purportedly “categorical” holding that public access\n(Continued)\n\n 28\n\n Not only does case law contradict Randall’s argument that public forum analysis\n\nnever applies to private property, her argument also fails because it makes no legal sense\n\nto establish a bright-line rule that forum analysis applies only to government-owned\n\nproperty. Why, for example, should the First Amendment allow a municipality to engage\n\nin viewpoint discrimination in curating a public library branch in leased space but not\n\nallow the municipality to engage in such discrimination in a library branch on\n\nmunicipally owned property? Cf. Bd. of Educ., Island Trees Union Free Sch. Dist. No.\n\n26 v. Pico, 457 U.S. 853, 870–71 (1982) (plurality op.) (“If a Democratic school board,\n\nmotivated by partisan affiliation, ordered removal of all books written by or in favor of\n\nRepublicans, few would doubt that the order violated the constitutional rights of the\n\nstudents denied access to those books.”). Or why should a municipality be allowed to\n\nengage in viewpoint discrimination when holding a virtual public meeting hosted on a\n\nprivate website when such discrimination would be unconstitutional if the meeting was\n\nheld in a governmental building? Cf. Lyrissa Lidsky, Public Forum 2.0, 91 B.U. L. Rev.\n\n1975, 1996 (2011) (“Just as the government can rent a building to use as a forum for\n\npublic debate and discussion, so, too, can it ‘rent’ a social media page for the promotion\n\n\n\nchannels constitute public forums ignore[d] “the far more critical issue of whether (and to\nwhat extent) there is government control over a public access channel.” Id. at 19–20.\n\n Here, a government official acting under color of state law, Randall, exercised\nunconstrained control over the aspect of the Chair’s Facebook Page giving rise to\nDavison’s claim.\n\n\n\n\n 29\n\nof public discussion.”). We do not believe the First Amendment draws such arbitrary\n\nlines.\n\n Randall’s second argument—that the Chair’s Facebook Page amounts to\n\n“government speech”—fails to recognize the meaningful difference between Randall’s\n\nposts to the Chair’s Facebook Page and the public comments and posts she invited in the\n\npage’s interactive space. To be sure, Randall’s comments and curated references on the\n\nChair’s Facebook Page to other Pages, personal profiles, and websites amount to\n\ngovernmental speech. See Sutliffe v. Epping School Dist., 584 F.3d 314, 329–30 (1st Cir.\n\n2009) (holding that municipality’s refusal to place hyperlink on municipal website to\n\nwebsite of group opposed to municipal budget constituted government speech); Page v.\n\nLexington Cty. School Dist. One, 531 F.3d 275, 283–85 (4th Cir. 2008) (holding that\n\nSchool District’s refusal to place hyperlink on its website to website of group that\n\nopposed School District’s position on pending legislation constituted government speech\n\nbecause, in part, “the links to other websites were selected by the School District alone as\n\nones that supported its own message”); Knight, 302 F. Supp. 3d at 571 (“[T]he\n\nPresident’s tweets are [not] susceptible to forum analysis . . . because the content is\n\ngovernment speech.”).\n\n But the interactive component of the Chair’s Facebook Page—the portion of the\n\nmiddle column in which the public can post comments, reply to posts, and “like”\n\ncomments and posts—is materially different. See Knight, 302 F. Supp. 3d at 572\n\n(distinguishing a government official’s tweets and “the interactive space for replies and\n\nretweets”). Randall placed no formal limitations on the ability of Facebook personal\n\n\n 30\n\nprofiles and Pages to access the Chair’s Facebook Page and make comments and posts to\n\nthe interactive component of the page. On the contrary, she expressly invited posts to the\n\npage “from ANY Loudon citizen on ANY issues, request, criticism, complement or just\n\nyour thoughts.” J.A. 455. And comments and posts by users cannot be mistaken for\n\nRandall’s own speech because they identify the posting or replying personal profile or\n\nPage, and thereby distinguish that user from Randall.\n\n Contrary to Randall’s argument that the Chair’s Facebook Page, in its entirety,\n\namounts to government speech, the present case also is meaningfully distinguishable\n\nfrom the government speech framework identified in Pleasant Grove. There, a\n\nmunicipality denied a private religious group’s request to allow it to erect a “monument\n\nin a city park in which other donated monuments were previously erected,” including a\n\nmonument depicting a prominent symbol of a different religion. 555 U.S. at 464. The\n\nplaintiff religious group sought relief under the First Amendment, arguing that the city\n\npark constituted a traditional public forum, and therefore that the city could not reject the\n\nreligious group’s proposed monument when it had previously allowed construction of a\n\nmonument associated with another religion. Id. at 466.\n\n The Supreme Court held that the city did not violate the First Amendment because\n\nthe government speech framework, rather than forum analysis, applied to the conduct at\n\nissue. In reaching that conclusion, the Court emphasized that the city never “opened up\n\nthe Park for the placement of whatever permanent monuments might be offered by\n\nprivate donors.” Id. at 472–73. “Rather, the City has ‘effectively controlled’ the\n\nmessages sent by the monuments in the Park by exercising ‘final approval authority’ over\n\n\n 31\n\ntheir selection.” Id. at 473. The Court further emphasized that “[t]he forum doctrine has\n\nbeen applied in situations in which government-owned property or a government\n\nprogram was capable of accommodating a large number of public speakers without\n\ndefeating the essential function of the land or the program.” Id. at 478. A city park,\n\nhowever, “can accommodate only a limited number of permanent monuments,” and\n\ntherefore a municipality cannot—and need not—provide park space for all who wish to\n\nerect a monument. Id.\n\n Here, Randall “effectively controlled” certain aspects of the Chair’s Facebook\n\nPage: she curated the Chair’s Facebook Page’s left and right columns and made posts to\n\nthe middle column. Id. at 472. But Randall also expressly opened the Chair’s Facebook\n\nPage’s middle column—its interactive space—for “ANY” user to post on “ANY issues,”\n\nJ.A. 455, and therefore did not retain “final approval authority” over that aspect of the\n\nChair’s Facebook Page, Pleasant Grove, 555 U.S. at 473. Just as the parkland\n\nsurrounding monuments in Pleasant Grove continued to constitute a public forum, even\n\nthough the monuments themselves constituted government speech, so too the interactive\n\ncomponent of the Chair’s Facebook Page constitutes a public forum, even though\n\nRandall’s curation of and posts to the Chair’s Facebook Page amount to government\n\nspeech. Additionally, the interactive component of the Chair’s Facebook Page does not\n\nface the same spacial limitations as those of the park in Pleasant Grove, but instead is\n\n“capable of accommodating a large number of public speakers without defeating [its]\n\nessential function.” Id. at 578. Accordingly, Pleasant Grove supports, rather than\n\n\n\n\n 32\n\nundermines, our conclusion that the interactive component of the Chair’s Facebook Page\n\nconstitutes a public forum.\n\n Upon concluding that interactive component of the Chair’s Facebook Page\n\namounts to a public forum, we would normally need to determine whether it constitutes a\n\ntraditional public forum or designated or limited public forum. In the present case,\n\nhowever, we need not decide that question because Randall’s ban of Davison amounted\n\nto “viewpoint discrimination,” which is “prohibited in all forums.” See Child Evangelism\n\nFellowship of S.C. v. Anderson Sch. Dist. Five, 470 F.3d 1062, 1067 n.2 (4th Cir. 2006).\n\n“Viewpoint discrimination . . . ‘targets not subject matter, but particular views taken by\n\nspeakers on a subject.’” Id. (quoting Rosenberger v. Rector & Visitors of Univ. of Va.,\n\n515 U.S. 819, 829 (1995)). Viewpoint discrimination is apparent, for example, if a\n\ngovernment official’s decision to take a challenged action was “impermissibly motivated\n\nby a desire to suppress a particular point of view.” Cornelius, 473 U.S. at 812–13.\n\n Here, the district court found—as the record amply supports—that Randall banned\n\nDavison’s Virginia SGP Page because Davison posted a comment using that page\n\nalleging “corruption on the part of Loudoun County’s School Board involving conflicts\n\nof interests among the School Board and their family members.” Davison, 267 F. Supp.\n\n3d at 711. Although Randall stated that she had “no idea” whether Davison’s allegations\n\nwere “correct,” she nonetheless banned him because she viewed the allegations as\n\n“slanderous” and she “didn’t want [the allegations] on the site.” Id. at 717. Randall’s\n\ndecision to ban Davison because of his allegation of governmental corruption constitutes\n\nblack-letter viewpoint discrimination.\n\n\n 33\n\n Put simply, Randall unconstitutionally sought to “suppress” Davison’s opinion\n\nthat there was corruption on the School Board. Cornelius, 473 U.S. at 812–13; see also,\n\ne.g., Rossignol, 316 F.3d at 521 (holding that sheriff’s deputies engaged in viewpoint\n\ndiscrimination when they seized an issue of a newspaper that criticized the county\n\nsheriff’s and his deputies’ performance of their official duties); Putnam Pit, Inc. v. City of\n\nCookeville, Tenn., 221 F.3d 834, 846 (6th Cir. 2000) (holding that a municipality engages\n\nin viewpoint discrimination if it refuses to link newspaper webpage to the city’s website\n\nsolely because the newspaper sought to expose municipal corruption); Knight, 302 F.\n\nSupp. 3d at 575 (holding that the President engaged in viewpoint discrimination when he\n\nblocked individuals from his Twitter account because the individuals “posted tweets that\n\ncriticized the President or his policies”). 7 That Randall’s action targeted comments\n\ncritical of the School Board members’ official actions and fitness for office renders the\n\nbanning all the more problematic as such speech “occupies the core of the protection\n\nafforded by the First Amendment.” Rossignol, 316 F.3d at 521 (quoting McIntyre v.\n\nOhio Elections Comm’n, 514 U.S. 334, 346 (1995)).\n\n In sum, the interactive component of the Chair’s Facebook Page constituted a\n\npublic forum, and Randall engaged in unconstitutional viewpoint discrimination when\n\nshe banned Davison’s Virginia SGP Page from that forum.\n\n\n 7\n Randall also asserts that she did not violate Davison’s First Amendment rights\nbecause she banned his “Virginia SGP” Page, not his “Brian Davison” profile. Davison\nis the sole operator of the “Virginia SGP” Page, however, and therefore the ban\nimplicated his First Amendment rights. Randall fails to identify any case supporting her\nposition, nor have we found any. Accordingly, we reject this argument.\n\n\n 34\n\n III.\n\n In his cross-appeal, Davison asserts that the district court reversibly erred in two\n\nways: (A) by dismissing his claim against Randall in her official capacity and (B) by\n\ndenying his motion to amend his complaint to add the new First Amendment claim\n\nagainst the Loudoun Board. 8 We disagree.\n\n A.\n\n Davison first argues that the district court erred in dismissing his claim against\n\nRandall in her official capacity. Whereas “[p]ersonal-capacity suits seek to impose\n\npersonal liability upon a government official for actions [she] takes under color of state\n\nlaw,” Kentucky v. Graham, 473 U.S. 159, 165 (1985), “official capacity suits are ‘treated\n\nas suits against the municipality,’” Santos v. Frederick Cty. Bd. of Comm’rs, 725 F.3d\n\n451, 469 (4th Cir. 2013) (quoting Hafer v. Melo, 502 U.S. 21, 25 (1991)). Because\n\n“municipal liability under Section 1983 does not amount to respondeat superior . . . a\n\n 8\n Davison also argues that the district court erred in rejecting his procedural due\nprocess claims under the Fourteenth Amendment and an analogous provision in the\nVirginia Constitution. Before the district court, Davison “flatly asserted that due process\nalways requires the government to provide a hearing before imposing a prior restraint on\nspeech,” and therefore that Randall violated Davison’s First Amendment rights by failing\nto conduct a pre-ban hearing. Davison, 267 F. Supp. 3d at 719. The district court\ncorrectly rejected Davison’s proposed categorical rule. Id. (citing Cafeteria & Rest.\nWorkers Union Local 473, AFL-CIO v. McElroy, 367 U.S. 886, 895 (1961). And\nDavison has abandoned that asserted categorical rule on appeal, Davison’s Br. at 49–50\nn.19 (“[I]t might be permissible in certain contexts to delete an individual comment\nwithout providing full pre-deprivation process . . . .”), instead arguing he is entitled to\nrelief under the balancing test set forth in Mathews v. Eldridge, 424 U.S. 319, 334–35\n(1976). Because Davison did not make that argument before the district court, we decline\nto consider it now. See CoreTel Va., LLC v. Verizon Va., LLC, 808 F.3d 978, 988 (4th\nCir. 2015).\n\n\n\n 35\n\nmunicipality is subject to Section 1983 liability only when its ‘policy or custom, whether\n\nmade by its lawmakers or by those whose edicts or acts may fairly be said to represent\n\nofficial policy, inflicts the [plaintiff’s] injury.’” Id. at 469–70 (quoting Monell v. Dep’t of\n\nSoc. Servs. of the City of N.Y., 436 U.S. 658, 694 (1978)).\n\n Here, the district court dismissed Davison’s official capacity claim because it\n\nfound that “no policy—whether County-wide or specific to [Randall]’s office—played\n\nany role in [Randall]’s decision to ban [Davison] from her [Chair’s Facebook Page].”\n\nDavison, 267 F. Supp. 3d at 715. We review the district court’s factual findings bearing\n\non whether Randall acted pursuant to a municipal policy or custom for clear error and its\n\nlegal conclusions de novo. Helton, 709 F.3d at 350.\n\n On appeal, Davison does not dispute the district court’s finding—which the record\n\namply supports—that Loudoun County did not promulgate a policy governing individual\n\nLoudoun Board members’ Facebook pages. Rather, Davison principally 9 argues that “the\n\ncounty can be held liable for Randall’s actions because in banning Davison, Randall\n\nacted as a municipal policymaker.” Davison’s Br. at 47.\n\n\n\n\n 9\n Davison also argues the Loudoun Board’s failure to adopt a policy pertaining to\nindividual board members’ Facebook pages gives rise to an official capacity claim\nbecause it establishes that the Loudoun “Board was—and remains—deliberately\nindifferent to the likelihood of unconstitutional censorship and viewpoint-based\ndiscrimination on individual supervisors’ social media sites.” Davison’s Br. at 46. But\nDavison never advanced a “deliberate indifference” theory of municipal liability before\nthe district court. Again, we decline to consider an argument Davison raises for the first\ntime on appeal. See CoreTel, LLC, 808 F.3d at 988.\n\n\n\n 36\n\n Davison is correct that “municipal liability may be imposed for a single decision\n\nby municipal policymakers under appropriate circumstances.” Hunter v. Town of\n\nMocksville, N.C., 897 F.3d 538, 554 (4th Cir. 2018) (quoting Pembaur v. City of\n\nCincinnati, 475 U.S. 469, 480 (1986)). “[I]n assessing whether a municipality may be\n\nheld liable for constitutional or statutory violations of their decisionmakers, the\n\ntouchstone inquiry is whether ‘the decisionmaker possesses final authority to establish\n\nmunicipal policy with respect to the action ordered.’” Id. at 554–55 (emphasis added)\n\n(quoting Liverman v. City of Petersburg, 844 F.3d 400, 413 (4th Cir. 2016)).\n\n Here, Davison failed to put forward evidence establishing that Randall was a final\n\nmunicipal policymaker with regard to her banning of Davison from the Chair’s Facebook\n\nPage. On the contrary, record evidence establishes that the Loudoun Board retained\n\nauthority to establish municipal policy with respect to social media pages, as it adopted a\n\nsocial media policy governing the County’s official social media pages. Davison\n\nconcedes as much, arguing that the Loudoun Board “neglected . . . to extend its written\n\nguidelines to Board members’ official pages.” Davison’s Br. at 46. But that argument\n\npresupposes that the Loudoun Board—not Randall—had authority to establish municipal\n\npolicy with respect “to Board members’ official pages.”\n\n Davison nevertheless argues that the Loudoun Board “implicitly” delegated its\n\nfinal policymaking authority to Randall by not addressing individual Loudoun Board\n\nmembers’ official pages in its social media policy. Davison is correct that delegation of\n\nfinal policy making authority may be “implied from a continued course of knowing\n\nacquiescence by the governing body in the exercise of policymaking authority by an\n\n\n 37\n\nagency or official.” Id. at 48 (quoting Spell v. McDaniel, 824 F.2d 1380, 1387 (4th Cir.\n\n1987)). But Davison identifies no evidence that the Loudoun Board knew of the Chair’s\n\nFacebook Page, let alone that it “aquiesce[d]” in Randall’s administration of the page and\n\nbanning of Davison, in particular. On the contrary, the district court found that Randall\n\nmade a one-off, “unilateral decision to ban [Davison] in the heat of the moment, and\n\nreconsidered soon thereafter,” Davison, 267 F. Supp. 3d at 715—before the Loudoun\n\nBoard had a chance to learn of her action. In such circumstances, the district court did\n\nnot reversibly err in rejecting Davison’s official capacity claim.\n\n B.\n\n Next, Davison argues that the district court erred in denying him leave to amend\n\nhis complaint to add a claim that “the County violates the First Amendment by\n\nmaintaining a limited public forum on Facebook,” when policies imposed by Facebook,\n\nrather than the County, restrain, or have the potential to restrain, speech. J.A. 74. “A\n\ndistrict court may deny a motion to amend when the amendment would be prejudicial to\n\nthe opposing party, the moving party has acted in bad faith, or the amendment would be\n\nfutile.” Equal Rights Ctr. v. Niles Bolton Assocs., 602 F.3d 597, 603 (4th Cir. 2010).\n\nThe magistrate judge recommended—and the district court agreed—that Davison be\n\ndenied leave to amend on grounds of both futility and prejudice. We review for abuse of\n\ndiscretion a district court’s denial of leave to amend for prejudice, whereas we review de\n\nnovo a district court’s denial of leave to amend on the basis of futility. See U.S. ex rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n\n\n\n 38\n\n Regarding prejudice, the district court determined that the amendment came “too\n\nlate in these proceedings” and would “add a new, novel legal theory to the case after the\n\nclose of discovery, after the existing claims against [the Loudoun Board] have been\n\nshown to be meritless, after the point at which Defendants could have addressed the\n\nclaim in briefing before trial, and on the eve of trial.” J.A. 74. The district court did not\n\nabuse its discretion in denying leave to amend in such circumstances. See, e.g., Equal\n\nRights Ctr., 602 F.3d at 603–04 (holding that district court did not abuse its discretion in\n\ndenying leave to amend on the basis of prejudice when amendment came after the close\n\nof discovery and “on the eve of the deadline for dispositive motions” and therefore\n\n“would [have] change[d] the nature of the litigation”); Deasy v. Hill, 833 F.2d 38, 41 (4th\n\nCir. 1987) (affirming denial of leave to amend on grounds of prejudice when “the motion\n\nto amend came right before trial and after discovery was complete”).\n\n Although we affirm the district court’s judgment on the basis of its finding of\n\nprejudice, we do not concur in its conclusion as to futility. “Futility is apparent if the\n\nproposed amended complaint fails to state a claim under the applicable rules and\n\naccompanying standards.” Katyle v. Penn Nat. Gaming, Inc., 637 F.3d 462, 471 (4th Cir.\n\n2011). Accordingly, Davison’s proposed amendment was futile if the new claim would\n\nnot have survived a motion to dismiss under Federal Rule of Civil Procedure 12(b)(6).\n\nSee Runnion ex rel. Runnion v. Girl Scouts of Greater Chicago & Nw. Ind., 786 F.3d 510,\n\n524 (7th Cir. 2015) (“[W]hen the basis for denial is futility, we apply the legal\n\nsufficiency standard of Rule 12(b)(6) to determine whether the proposed amended\n\ncomplaint fails to state a claim.”).\n\n\n 39\n\n Davison’s proposed First Amendment claim deals not with the Chair’s Facebook\n\nPage—which the Loudoun Board did not authorize or attempt to regulate—but rather\n\nwith Loudoun County’s official Facebook Pages created and maintained pursuant to the\n\nLoudoun Board’s social media policy. As with his claims related to the Chair’s\n\nFacebook Page, Davison alleged that the Facebook Pages created and maintained by the\n\nLoudoun Board constituted public forums subject to the First Amendment. Davison\n\ntheorized that the Loudoun Board’s decision to use Facebook as its social media forum\n\nviolated his First Amendment rights because Facebook rules permit individual\n\n“requesting” users to ban other personal profiles and Pages such that the banned users can\n\nno longer see posts authored by the requesting users. In such circumstances, the banned\n\nusers “cannot see [the requesting user’s] comment[s] or participate in the discussion\n\nsurrounding the [requesting] party’s comment.” Davison’s Br. at 59. Davison’s\n\nproposed amended complaint asserted that “this scenario violates the First Amendment\n\nbecause Loudoun County has effectively enabled third parties to exclude discussion\n\nwithin a public forum—something a government body could not permissibly do in a\n\nphysical forum.” Id. at 59–60 (internal citation omitted). Put differently, Davison\n\ntheorized that Loudoun County violated the First Amendment by choosing to use\n\nFacebook as a public forum, when rules imposed by Facebook allow private users to\n\nrestrict access to their posts—and comments on and responses to those posts—including\n\nposts to any municipal Facebook Page.\n\n No court appears to have addressed that novel legal theory. And although the First\n\nAmendment constrains only government policies, not policies established by private\n\n\n 40\n\nentities, one can conceive of a colorable legal argument that a governmental actor’s\n\ndecision to select a private social media website for use as a public forum—and therefore\n\nselect that website’s suite of rules and regulations—could violate the First Amendment, if\n\nthe private website included certain types of exclusionary rules. For example, if the\n\ngovernment chose as its electronic public forum a social media site that allowed only\n\nregistered members of one political party to post and comment, there would seem to be a\n\ncompelling argument that the government’s selection of that social media site violated the\n\nFirst Amendment rights of members of other political parties, even if the partisan\n\nrestriction was imposed by the private company, not the governmental body. Such a\n\nrestriction would be seem to be no different than a municipality choosing to hold a town\n\nhall meeting in a venue that refused admission to individuals associated with a disfavored\n\npolitical party or viewpoint. Cf. DeBoer v. Village of Oak Park, 267 F.3d 558, 571 (7th\n\nCir. 2001) (“[T]he government engages in viewpoint discrimination when it denies access\n\nto a speaker solely to suppress the point of view he espouses on an otherwise includible\n\nsubject.”).\n\n Given that Davison’s proposed claim asserted a novel and colorable legal theory\n\nand that “Rule 12(b)(6) dismissals are especially disfavored in cases where the complaint\n\nsets forth a novel legal theory that can best be assessed after factual development,”\n\nWright v. North Carolina, 787 F.3d 256, 263 (4th Cir. 2015) (internal quotation marks\n\nomitted), we affirm the district court’s denial of Davison’s motion for leave to amend his\n\ncomplaint on the basis of its finding of prejudice but not on the basis of futility.\n\n IV.\n\n\n 41\n\nFor the foregoing reasons, we affirm the judgment of the district court.\n\n AFFIRMED\n\n\n\n\n 42", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356556/", "author_raw": "WYNN, Circuit Judge:"}, {"author": "BARBARA MILANO KEENAN, Circuit Judge, concurring", "type": "concurrence", "text": "BARBARA MILANO KEENAN, Circuit Judge, concurring:\n\n I join the well-reasoned majority opinion in full. I agree that the central “aspects\n\nof the Chair’s Facebook Page bear the hallmarks of a public forum.” I am particularly\n\npersuaded by the facts concerning Randall’s conduct of impressing the Chair Facebook\n\nPage with the trappings of a “government official” Facebook Page and of inviting\n\ncitizens to comment, without restriction, on matters of public concern. Accordingly,\n\nunder our precedent, I agree that Randall’s conduct of banning Davison’s Virginia SGP\n\nPage based on the content of a comment is attributable to the government and violates the\n\nFirst Amendment. See Rossignol v. Voorhaar, 316 F.3d 516, 523-25 (4th Cir. 2003).\n\n I nonetheless write separately to call attention to two issues regarding\n\ngovernmental use of social media that do not fit neatly into our precedent. First, I\n\nquestion whether any and all public officials, regardless of their roles, should be treated\n\nequally in their ability to open a public forum on social media. The Supreme Court\n\nrecently cited a series of decisions in which “a unit of government” had created a public\n\nforum. Matal v. Tam, 137 S. Ct. 1744, 1763 (2017) (emphasis added) (citing cases); see\n\nalso Pleasant Grove City v. Summum, 555 U.S. 460, 470 (2009) (“a government entity\n\nmay create a forum” (emphasis added)). However, it appears to be an open question\n\nwhether an individual public official serving in a legislative capacity qualifies as a unit of\n\ngovernment or a government entity for purposes of her ability to open a public forum.\n\nInstead, our precedent merely directs us to consider whether the challenged action “bore a\n\nsufficiently close nexus” with the government to be “fairly treated” as that of the\n\n\n\n\n 43\n\ngovernment itself. Rossignol, 316 F.3d at 525 (internal quotation marks and citation\n\nomitted).\n\n The nature and extent of a public official’s authority should have some bearing on\n\nthe official’s ability to open a public forum on social media. While the nine-member\n\nLoudoun County Board of Supervisors (the Board) serves to set policies, adopt\n\nordinances, and appropriate funds, the Chair simply is empowered individually to oversee\n\nmeetings and to set agendas. 1 The record before us is silent regarding the Chair’s\n\nauthority to take any official action on her own.\n\n In contrast, certain elected executive officials, under given circumstances, can\n\nconduct government business and set official policy unilaterally, including through the\n\nuse of social media. See, e.g., Knight First Amendment Inst. at Columbia Univ. v. Trump,\n\n302 F. Supp. 3d 541, 567 (S.D.N.Y. 2018) (discussing President Donald J. Trump’s use\n\nof his Twitter account to appoint and remove officers and conduct foreign policy), appeal\n\ndocketed, No. 18-1691 (2d Cir. Oct. 24, 2018); Schisler v. State, 907 A.2d 175, 218-20\n\n(Md. 2006) (describing the governor’s unilateral power to remove certain officers). The\n\nrelevance of such distinctions to a public official’s ability to create a public forum on\n\nsocial media is a matter that should be addressed by the Supreme Court. Because this is\n\nan open question, we are bound by current precedent and, for the reasons set forth in the\n\n\n\n 1\n See Bd. of Supervisors Operations Manual, LOUDOUN CTY., VA chs. 2-3,\nhttps://www.loudoun.gov/DocumentCenter/View/117084/Board-of-Supervisors-\nOperations-Manual-2016-2020 (last visited Dec. 20, 2018) (saved as ECF opinion\nattachment).\n\n\n 44\n\nmajority opinion, Randall as a single board member acted under of color of law and\n\nopened a public forum on Facebook.\n\n Second, the Supreme Court should consider further the reach of the First\n\nAmendment in the context of social media. I acknowledge that the Supreme Court has\n\nreferred to social media as “the modern public square,” Packingham v. North Carolina,\n\n137 S. Ct. 1730, 1737 (2017), implying that First Amendment principles protecting\n\nspeech from government intrusion do extend to social media. However, the interplay\n\nbetween private companies hosting social media sites and government actors managing\n\nthose sites necessarily blurs the line regarding which party is responsible for burdens\n\nplaced on a participant’s speech.\n\n For example, hate speech is protected under the First Amendment. See Matal, 137\n\nS. Ct. at 1763-64 (holding that the disparagement clause of the Lanham Act violated the\n\nFirst Amendment free speech clause because it prohibited hate speech). But social media\n\ncompanies like Facebook and others have policies forbidding hate speech on their\n\nplatforms. 2 Thus, while a government official, who under color of law has opened a\n\npublic forum on a social media platform like Facebook, could not ban a user’s comment\n\ncontaining hate speech, that official could report the hate speech to Facebook. And\n\nFacebook personnel could ban the user’s comment, arguably circumventing First\n\nAmendment protections.\n\n\n 2\n See, e.g., Cmty. Standards, Hate Speech, FACEBOOK, https://www.facebook.com/\ncommunitystandards/hate_speech (last visited Dec. 20, 2018) (saved as ECF opinion\nattachment).\n\n\n\n 45\n\n Admittedly, this question is not directly presented in the present case, given that\n\nthe public official, not a Facebook employee, acted to restrict speech. Nonetheless, cases\n\nnecessarily will arise requiring courts to consider the nuances of social media and their\n\nvarious roles in hosting public forums established by government officials or entities.\n\nTherefore, in my view, courts must exercise great caution when examining these issues,\n\nas we await further guidance from the Supreme Court on the First Amendment’s reach\n\ninto social media.\n\n\n\n\n 46", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356556/", "author_raw": "BARBARA MILANO KEENAN, Circuit Judge, concurring"}]}
KEENAN
WYNN
HARRIS
1
{}
2
0
0
1
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579303/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Brian DAVISON, Plaintiff - Appellee, v. Phyllis RANDALL, in Her Official and Individual Capacity, Defendant - Appellant, and Loudoun County Board of Supervisors, in Their Official and Individual Capacities; Leo Rogers, in His Official Capacity; Tony Buffington, in His Official Capacity; Ron Meyer, in His Official Capacity; Geary Higgins, in His Official Capacity, Defendants. Local Government Attorneys of Virginia, Inc.; International Municipal Lawyers Association ; Virginia Association of Counties; Virginia Municipal League, Amici Supporting Appellant, American Civil Liberties Union; ACLU of Virginia ; ACLU of Maryland; ACLU of North Carolina; ACLU of South Carolina; ACLU of West Virginia, Amici Supporting Appellee. Brian C. Davison, Plaintiff - Appellant, v. Phyllis Randall, in Her Official and Individual Capacity; Loudoun County Board of Supervisors, in Their Official and Individual Capacities, Defendants - Appellees, and Leo Rogers, in His Official Capacity; Tony Buffington, in His Official Capacity; Ron Meyer, in His Official Capacity; Geary Higgins, in His Official Capacity, Defendants.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-07\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2002\n\n\nBRIAN DAVISON,\n\n Plaintiff - Appellee,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity,\n\n Defendant - Appellant,\n\n and\n\nLOUDOUN COUNTY BOARD OF SUPERVISORS, In their official and\nindividual capacities; LEO ROGERS, In his official capacity; TONY\nBUFFINGTON, In his official capacity; RON MEYER, In his official capacity;\nGEARY HIGGINS, In his official capacity,\n\n Defendants.\n\n------------------------------\n\nLOCAL GOVERNMENT ATTORNEYS OF VIRGINIA, INC.;\nINTERNATIONAL MUNICIPAL LAWYERS ASSOCIATION; VIRGINIA\nASSOCIATION OF COUNTIES; VIRGINIA MUNICIPAL LEAGUE,\n\n Amici Supporting Appellant,\n\nAMERICAN CIVIL LIBERTIES UNION; ACLU OF VIRGINIA; ACLU OF\nMARYLAND; ACLU OF NORTH CAROLINA; ACLU OF SOUTH\nCAROLINA; ACLU OF WEST VIRGINIA,\n\n Amici Supporting Appellee.\n\n No. 17-2003\n\n\nBRIAN C. DAVISON,\n\n Plaintiff - Appellant,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity; LOUDOUN\nCOUNTY BOARD OF SUPERVISORS, In their official and individual\ncapacities,\n\n Defendants - Appellees,\n\n and\n\nLEO ROGERS, In his official capacity; TONY BUFFINGTON, In his official\ncapacity; RON MEYER, In his official capacity; GEARY HIGGINS, In his\nofficial capacity,\n\n Defendants.\n\n\nAppeals from the United States District Court for the Eastern District of Virginia, at\nAlexandria. James C. Cacheris, Senior District Judge. (1:16-cv-00932-JCC-IDD)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n\n\nBefore KEENAN, WYNN, and HARRIS, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Keenan\nand Judge Harris concurred. Judge Keenan wrote a separate concurring opinion.\n\n\nARGUED: Scott E. Gant, BOIES SCHILLER FLEXNER, LLP, Washington, D.C.; Leo\nP. Rogers, LOUDON COUNTY ATTORNEY, Leesburg, Virginia, for Appellant/Cross-\nAppellee. Katherine A. Fallow, KNIGHT FIRST AMENDMENT INSTITUTE AT\n\n\n 2\n\nCOLUMBIA UNIVERSITY, New York, New York, for Appellee/Cross-Appellant. ON\nBRIEF: Aaron E. Nathan, BOIES SCHILLER FLEXNER LLP, Washington, D.C., for\nAppellant/Cross-Appellee. Jameel Jaffer, Carrie DeCell, KNIGHT FIRST\nAMENDMENT INSTITUTE AT COLUMBIA UNIVERSITY, New York, New York,\nfor Appellee/Cross-Appellant. Vishal Agraharkar, AMERICAN CIVIL LIBERTIES\nUNION FOUNDATION OF VIRGINIA, Richmond, Virginia; Esha Bhandari, Vera\nEidelman, AMERICAN CIVIL LIBERTIES UNION FOUNDATION, New York, New\nYork; Susan K. Dunn, ACLU OF SC FOUNDATION, INC., Charleston, South Carolina;\nChristopher Brook, AMERICAN CIVIL LIBERTIES UNION OF NORTH CAROLINA\nLEGAL FOUNDATION, Raleigh, North Carolina; Deborah A. Jeon, ACLU\nFOUNDATION OF MARYLAND, Baltimore, Maryland; Jennifer D. Oliva, ACLU OF\nWEST VIRGINIA FOUNDATION, Charleston, West Virginia, for Amici American\nCivil Liberties Union, ACLU of Virginia, ACLU of Maryland, ACLU of North Carolina,\nACLU of South Carolina, and ACLU of West Virginia. Joshua A. Geltzer, Douglas\nLetter, Amy L. Marshak, Mary B. McCord, INSTITUTE FOR CONSTITUTIONAL\nADVOCACY AND PROTECTION GEORGETOWN UNIVERSITY LAW CENTER,\nWashington, D.C.; Kwaku A. Akowuah, Christopher C. Fonzone, Kate Heinzelman,\nSIDLEY AUSTIN LLP, Washington, D.C., for Amici Curiae First Amendment Legal\nScholars.\n\n\n\n\n 3\n\nWYNN, Circuit Judge:\n\n Phyllis Randall, Chair of the Loudoun County, Virginia, Board of Supervisors (the\n\n“Loudoun Board”), brings this appeal, arguing that the district court erred in concluding\n\nthat she violated the First Amendment rights of one of her constituents, Brian Davison,\n\nwhen she banned Davison from the “Chair Phyllis J. Randall” Facebook page she\n\nadministered. In a cross appeal, Davison principally argues that the district court erred\n\nin dismissing his procedural due process claim premised on the ban. For the reasons that\n\nfollow, we affirm.\n\n I.\n\n A.\n\n Randall has chaired the Loudoun County Board of Supervisors since January 1,\n\n2016. The day before she was sworn in as chair, Randall created the “Chair Phyllis J.\n\nRandall” Facebook Page (the “Chair’s Facebook Page”). According to Facebook, Inc.,\n\nunlike personal Facebook profiles, which are for non-commercial use and represent\n\nindividual people, Facebook “Pages”—like the Chair’s Facebook Page—“help\n\nbusinesses, organizations, and brands share their stories and connect with people.” J.A.\n\n403. “Pages are managed by people who have personal profiles,” the company explains.\n\nJ.A. 403. In addition to the Chair’s Facebook Page, Randall created and maintained two\n\nother Facebook profiles: a personal profile and a Page devoted to her campaign. Randall\n\nclassified her campaign page as belonging to a “politician” and used no designation for\n\nher personal profile, but she designated the Chair’s Facebook Page as a “governmental\n\nofficial” page. J.A. 209–10.\n\n\n 4\n\n Randall and her Chief of Staff, Jeanine Arnett, share administrative control over\n\nthe Chair’s Facebook Page, although Randall almost exclusively controls the page’s\n\ncontent. On her campaign page, Randall characterized the Chair’s Facebook Page as her\n\n“county Facebook page” stating:\n\n I really want to hear from ANY Loudoun citizen on ANY issues, request,\n criticism, complement or just your thoughts. However, I really try to keep\n back and forth conversations (as opposed to one time information items\n such as road closures) on my county Facebook page (Chair Phyllis J.\n Randall) or County email ([email protected]). Having back and\n forth constituent conversations are Foiable ([Freedom of Information Act])\n so if you could reach out to me on these mediums that would be\n appreciated.\n\nJ.A. 455 (emphasis added).\n\n The Chair’s Facebook Page includes three columns. The left column, which is\n\ntopped by a picture of Randall, includes several links to allow visitors to quickly navigate\n\nthe contents of the Chair’s Facebook Page.\n\n The middle column, which is organized in reverse chronological order similar to a\n\npersonal profile’s News Feed, is composed of posts by Randall and comments by\n\nFacebook users on those posts. Randall’s posts are almost always directed to “Loudoun,”\n\nsee, e.g., J.A. 408–10, and deal with numerous aspects of Randall’s official\n\nresponsibilities. For example, Randall used the Chair’s Facebook Page to notify the\n\npublic about upcoming Loudoun Board meetings, and the subjects to be discussed during\n\nthose meetings. Randall also used the page to inform Loudoun County residents about\n\nsignificant public safety issues. See, e.g., J.A. 412 (stating that Loudoun Board had\n\n“been informed by the Sheriff’s Office about the non-legitimate threat made on social\n\n\n\n 5\n\nmedia toward Dominion High School in Sterling”); J.A. 418 (reporting that she “ha[d]\n\nbeen briefed regarding the student falling from the water tower this morning” and\n\nadvising the public to “not make any assumptions but wait for information”). And\n\nRandall used the Chair’s Facebook Page to coordinate Loudoun County’s response to a\n\nlarge snow storm, including to communicate with constituents regarding which municipal\n\nstreets required plowing.\n\n Other posts by Randall to the Chair’s Facebook Page invited members of the\n\npublic to apply to participate on a public commission and to participate in public\n\nmeetings regarding key issues facing Loudoun County residents, such as revised flood\n\nplain zones and the Zika virus. Randall also authored posts regarding a variety of trips\n\nand meetings she had taken in furtherance of Loudoun County business. E.g., J.A. 408\n\n(reporting that Randall “address[ed] the (county) role in Treatment” at a “regional\n\nconference on Opioid and Substance Abuse Addiction”); J.A. 410 (stating that Randall\n\nrepresented Loudoun County at its “annual credit rating presentation” in New York); J.A.\n\n415 (informing public of trip to Loudoun’s “Sister City” in Germany); J.A. 426\n\n(reporting that Randall was “in Richmond lobbying for [Loudoun County’s] legislative\n\nprogram”). Finally, Randall used the page to advise the public regarding official actions\n\ntaken by the Loudoun Board. E.g., J.A. 433 (reporting that Loudoun Board “approved\n\nfunding for new breathing apparatus for our Loudoun Firefighters”); J.A. 442 (listing\n\nseveral “proclamations of note” by the Loudoun Board); J.A. 443 (informing public that\n\nLoudoun Board “adopted a budget for Fiscal Year 2017 totaling $2.46 billion for the\n\ngeneral county government and schools”). Although Randall’s posts on the Chair’s\n\n\n 6\n\nFacebook Page principally addressed her official responsibilities, a few posts addressed\n\ntopics less closely related to her official activities such as her affection for the German\n\nlanguage or pride in becoming an organ donor.\n\n Members of the public, including Davison, “liked” 1 or commented on several of\n\nRandall’s posts on the Chair’s Facebook Page. Each “like” or comment identified the\n\nname of the personal profile or Page of the authoring party. Many of the comments\n\nthanked Randall and the Loudoun Board for representing the public’s interests. Other\n\nposts by members of the public offered feedback on various issues faced by Randall and\n\nthe Loudoun Board. E.g., J.A. 427 (stating that “[p]utting recreation in a flood plain is\n\nnot a good idea”); J.A. 448 (stating that “more needs to be done with the explosion of\n\nLyme disease in Loudoun”). And other comments dealt with constituent-specific issues.\n\nE.g., J.A. 415 (constituent stating, in response to post by Randall regarding visit to\n\nLoudoun County’s “Sister City” in Germany, that constituent’s “daughter is interested in\n\nexchange programs”); J.A. 454 (stating that “there [we]re no [snow] plows to be seen” in\n\na particular neighborhood). Finally, several comments, including a number authored by\n\nDavison, criticized the Loudoun Board, generally, and Randall, in particular, for actions\n\ntaken in their official capacities. E.g., J.A. 429–30 (Davison criticizing public school\n\nsystem budget and expenditures); J.A. 438–39 (member of public criticizing\n\ngovernmental entity’s inspection of farm, claiming it failed to uncover animal abuse);\n\n\n 1\n “‘Liking’ on Facebook is a way for Facebook users to share information with\neach other.” Bland v. Roberts, 730 F.3d 368, 385 (4th Cir. 2013).\n\n\n\n 7\n\nJ.A. 449 (Davison characterizing question he posed at Loudoun Board and Loudoun\n\nSchool Board joint town hall). On some occasions, Randall responded to these\n\ncomments or criticisms.\n\n In the right column of the Chair’s Facebook Page, the page is identified as a\n\n“government official” page. It provides contact information for Randall’s county office,\n\nincluding her office telephone number, Randall’s official county email address, and the\n\ninternet address for the official county website. The column also identifies how many\n\nand which Facebook personal profiles and Pages “like” and “follow” the Chair’s\n\nFacebook Page. 2 And the column includes a list of personal profiles and Pages “liked”\n\nby the Chair’s Facebook Page.\n\n Randall publicized the Chair’s Facebook Page in her official “Chair Phyllis J.\n\nRandall” newsletter, which is prepared by County employees, hosted on the County’s\n\nwebsite, and distributed to Loudoun citizens using Randall’s official county email\n\naccount. The newsletter ends with the words “STAY CONNECTED” and a Facebook\n\nicon that hyperlinks to the Chair’s Facebook Page. Randall also highlighted the Chair’s\n\nFacebook Page in “Winter Storm Information” notices emailed from her official county\n\naccount to Loudoun County residents, advising recipients to “Visit [the Chair’s Facebook\n\nPage] for Updates.” J.A. 341–42, 344.\n\n 2\n According to Facebook, “[l]iking a Facebook Page means you are connecting to\nthat Page. When you connect to a Page, it will appear in [a user’s] timeline and [the user]\nwill appear on the page as a person who likes that Page. The Page will also be able to\npost content into [the user’s] News Feed.” Bland, 730 F.3d at 385 (internal quotation\nmarks omitted).\n\n\n\n 8\n\n Davison, an outspoken resident of Loudoun County, apparently largely focuses his\n\ncivic engagement and expression on “the funding and . . . management of public\n\nschools.” J.A. 95. To that end, he has repeatedly expressed concern about “School Board\n\nmembers failing to disclose personal conflicts as required by law before voting on\n\nfinancial transactions before the School Board.” J.A. 96.\n\n On February 3, 2016, Davison attended a Loudoun town hall meeting that\n\nincluded the Loudoun County School Board and Randall. At the meeting, Davison\n\nsubmitted a question implying that certain School Board members had acted unethically\n\nin approving financial transactions. Randall volunteered to answer the question but\n\ncharacterized it as a “set-up question” that she did not “appreciate.” J.A. 103. Shortly\n\nafter Randall answered the question—and while the town hall meeting was still\n\nongoing—Davison posted a message on Twitter in which he tagged Randall:\n\n“@ChairRandall ‘set up question’? You might want to strictly follow FOIA and the\n\nCOIA as well.” J.A. 470–71.\n\n Later that evening, Randall posted about the town hall meeting on the Chair’s\n\nFacebook Page, describing “what was generally discussed at the meeting.” J.A. 268. In\n\nresponse, Davison then used one of the Facebook Pages he manages through his personal\n\nFacebook profile—“Virginia SGP,” which Davison frequently uses to post political\n\ncommentary—to comment on Randall’s post about the town hall meeting. Although\n\nneither Davison nor Randall remember the precise content of Davison’s comment,\n\nRandall testified that it contained “accusations” regarding School Board members’ and\n\ntheir families’ putative conflicts of interest related to municipal financial transactions,\n\n\n 9\n\nsuggesting, in Randall’s opinion, that School Board members had been “taking kickback\n\nmoney.” See J.A. 268–69, 289–90. Randall stated that she “had no idea if any of th[e]\n\n[accusations] w[ere] correct,” but she determined that the post was “probably not\n\nsomething [she] want[ed] to leave” on the Chair’s Facebook Page. J.A. 269. Randall\n\nthen “deleted the whole post,” including her original post regarding the town hall\n\nmeeting, Davison’s comment and replies thereto, and all other public comments. J.A.\n\n269. Randall also banned Davison’s Virginia SGP Page from the Chair’s Facebook Page,\n\nwhich precluded Davison from using his Virginia SGP Page from commenting on the\n\nChair’s Facebook Page. The next morning, about twelve hours later, Randall\n\nreconsidered her actions and unbanned Davison’s Virginia SGP Page.\n\n B.\n\n On November 3, 2016, Davison filed an amended complaint seeking declaratory\n\nand injunctive relief under 42 U.S.C. § 1983 against Randall, in both her official and\n\nindividual capacities, and the Loudoun Board alleging that the “banning of [Davison]\n\nfrom commenting on [the Chair’s Facebook Page] is viewpoint discrimination.” J.A. 31.\n\nDavison further alleged that the ban violated his procedural due process rights protected\n\nby the Fourteenth Amendment because “Randall blocked Davison’s constitutionally\n\nprotected speech on [the Chair’s Facebook Page], a limited public forum, without prior\n\nnotice and without providing an opportunity for appealing [her] decision.” J.A. 32.\n\nDavison did not challenge Randall’s deletion of his post.\n\n On March 6, 2017—four days before the close of discovery and approximately\n\ntwo months before trial—Davison moved for leave to amend his complaint a second time\n\n\n 10\n\nto add claims under the Virginia Constitution that were materially indistinguishable from\n\nhis previously asserted First and Fourteenth Amendment claims premised on the ban, as\n\nwell as a separate First Amendment claim against the Loudoun Board. Davison’s\n\nproposed new First Amendment claim theorized that the County violated his free speech\n\nrights by choosing to use Facebook Pages as public forums, when Facebook allows\n\nprivate users to restrict access to their posts, including posts to any Page a municipality\n\ndesignates as a limited public forum. Pl.’s Mem. in Supp. of Mot. for Leave to File\n\nSecond Am. Compl. 3–9, Davison v. Loudoun County Bd. of Supervisors, 16-cv-932-\n\nJCC-IDD, ECF No. 68. The district court referred the motion to a magistrate judge, who\n\ngranted leave to amend regarding the claims under the Virginia Constitution but denied\n\nleave as to the new First Amendment claim against the Loudoun Board. Davison lodged\n\nobjections to the magistrate judge’s partial denial of leave to amend, which objections the\n\ndistrict court overruled.\n\n Around the same time, Randall and the Loudoun Board each moved for summary\n\njudgment. The Loudoun Board asserted that the municipality could not be held liable for\n\nRandall’s banning of Davison from the Chair’s Facebook Page because the Chair’s\n\nFacebook Page was not an official municipal page and because Randall, not the Loudoun\n\nBoard as a body, was solely responsible for creating and administering the Chair’s\n\nFacebook Page. The Loudoun Board and Randall further asserted that the Chair’s\n\nFacebook Page did not amount to a public forum, and therefore Randall’s ban of\n\nDavison’s Virginia SGP Page did not implicate his free speech or procedural due process\n\nrights. Finally, Randall asserted that she was entitled to qualified immunity.\n\n\n 11\n\n On May 10, 2017, the district court granted summary judgment in favor of the\n\nLoudoun Board, dismissing it from the suit. But as to Randall, the district court\n\nconcluded that Davison’s evidence established a material dispute of fact as to whether the\n\nChair’s Facebook Page amounted to a limited public forum and whether Randall, in her\n\nindividual capacity, acted under color of state law in banning Davison from the Chair’s\n\nFacebook Page. Davison v. Loudoun Cty. Bd. of Supervisors, No. 1:16-cv-932, 2017 WL\n\n1929406, at *6–9 (E.D. Va. May 10, 2017). The district court also rejected Randall’s\n\nqualified immunity argument. Id. at *8.\n\n Following a one-day bench trial of Davison’s claims against Randall, the district\n\ncourt issued a memorandum opinion and order awarding judgment in Davison’s favor on\n\nhis claims under the First Amendment and the analogous free speech provision in the\n\nVirginia Constitution. See Davison v. Loudoun Cty. Bd. of Supervisors, 267 F. Supp. 3d\n\n702, 714–18 (E.D. Va. 2017). The district court further entered judgment in Randall’s\n\nfavor on Davison’s federal and state procedural due process claims. Id. at 719–22. As to\n\nremedy, the district court denied Davison’s request for injunctive relief but granted\n\nDavison’s request for a declaratory judgment to resolve the “uncertainty regarding the\n\nlegal status of [the Chair’s Facebook Page].” Id. at 723.\n\n Randall and Davison, respectively, filed this appeal and cross appeal.\n\n II.\n\n On appeal, Randall argues that (A) Davison failed to establish standing to obtain\n\nprospective declaratory relief based on Randall’s alleged First Amendment violation; (B)\n\nthe district court erred in concluding that Randall acted under “color of state law” when\n\n\n 12\n\nshe banned Davison’s Virginia SGP Page from the Chair’s Facebook Page; and (C) the\n\ndistrict court erred in concluding that Randall’s banning of Davison’s Virginia SGP Page\n\nviolated the First Amendment.\n\n A.\n\n Notwithstanding that she did not challenge Davison’s standing below—and\n\ntherefore that the district court never squarely addressed his standing—Randall now\n\nargues that Davison failed to establish Article III standing to support the district court’s\n\naward of prospective declaratory relief. Even though Defendants did not challenge\n\nDavison’s standing below, “standing to sue is a jurisdictional issue of constitutional\n\ndimensions, and it may be raised and addressed for the first time on appeal.” Hodges v.\n\nAbraham, 300 F.3d 432, 443 (4th Cir. 2002). This Court reviews de novo “whether a\n\ndistrict court possessed jurisdiction in a declaratory judgment proceeding.” Volvo Const.\n\nEquip. N. Am., Inc. v. CLM Equip. Co., Inc., 386 F.3d 581, 591 (4th Cir. 2004).\n\n To establish Article III standing, a plaintiff must prove that: “1) he or she suffered\n\nan ‘injury in fact’ that is concrete and particularized, and is actual or imminent; 2) the\n\ninjury is fairly traceable to the challenged action of the defendant; and 3) the injury likely\n\nwill be redressed by a favorable decision.” Friends of the Earth, Inc. v. Gaston Copper\n\nRecycling Corp., 629 F.3d 387, 396 (4th Cir. 2011). Randall does not dispute that any\n\ninjury Davison suffered is fairly traceable to her decision to ban him from the Chair’s\n\nFacebook Page. Nor does Randall dispute that any such injury would be remedied by a\n\nfavorable decision. Rather, Randall claims that Davison failed to adduce evidence\n\n\n\n\n 13\n\nestablishing that he suffered an “injury in fact” sufficient to support prospective\n\ndeclaratory relief.\n\n “Injury in fact is ‘an invasion of a legally protected interest’ that is ‘concrete and\n\nparticularized’ and ‘actual or imminent, not conjectural or hypothetical.’” Kenny v.\n\nWilson, 885 F.3d 280, 287 (4th Cir. 2018) (quoting Spokeo, Inc. v. Robins, 136 S. Ct.\n\n1540, 1548 (2016)). Because “‘[p]ast exposure to illegal conduct does not in itself show\n\na present case or controversy regarding injunctive relief . . . if unaccompanied by any\n\ncontinuing, present adverse effects,’” a plaintiff seeking “declaratory or injunctive relief .\n\n. . must establish an ongoing or future injury in fact.” Id. at 287–88 (quoting O’Shea v.\n\nLittleton, 414 U.S. 488, 495–96 (1974)). Significantly, this Court—along with several\n\nother circuits—has held that “standing requirements are somewhat relaxed in First\n\nAmendment cases,” particularly regarding the injury-in-fact requirement. Cooksey v.\n\nFutrell, 721 F.3d 226, 235 (4th Cir. 2013) (collecting cases).\n\n In Kenny v. Wilson, 885 F.3d 280 (4th Cir. 2018), this Court addressed what\n\nevidence a plaintiff seeking relief under the First Amendment, like Davison, must put\n\nforward to establish a future injury-in-fact adequate to confer Article III standing to\n\nobtain prospective declaratory relief. In Kenny, several high school students lodged First\n\nAmendment challenges to two South Carolina disorderly conduct statutes. Id. at 284.\n\nThis Court explained that “there is a sufficiently imminent injury in fact if plaintiffs\n\nallege [1] ‘an intention to engage in a course of conduct arguably affected with a\n\nconstitutional interest, but proscribed by a statute, and [2] there exists a credible threat of\n\nprosecution thereunder.’” Id. at 288 (quoting Babbitt v. Farm Workers Nat’l Union, 442\n\n\n 14\n\nU.S. 289, 298 (1979)). The Kenny plaintiffs satisfied the first prong because they “attend\n\nschool” and “attending school inevitably involves expressive conduct” that implicates the\n\ndisorderly conduct statutes. Id. As to the second element—whether the students alleged\n\na “credible threat of future enforcement”—we held that such a threat exists so long as it\n\n“is not imaginary or wholly speculative, chimerical, or wholly conjectural.” Id. (internal\n\nquotation marks, citations, and alterations omitted). “[P]ast enforcement against the same\n\nconduct is good evidence that the threat of enforcement is not chimerical.” Id. (quoting\n\nSusan B. Anthony List v. Driehaus, 134 S. Ct. 2334, 2345 (2014)). “Threat of\n\nprosecution is especially credible when defendants have not ‘disavowed enforcement’ if\n\nplaintiffs engage in similar conduct in the future.” Id. (quoting Driehaus, 134 S. Ct. at\n\n2345). Applying this standard, we held that the plaintiffs alleged a credible threat of\n\nenforcement “because these three plaintiffs regularly attend schools where they allege\n\nthere may be future encounters with school resource officers or other law enforcement;\n\nthey have been prosecuted under the laws in the past; and the defendants have not\n\ndisavowed enforcement if plaintiffs engage in similar conduct in the future.” Id. at 289.\n\n Under Kenny, Davison’s evidence established his standing to obtain prospective\n\ndeclaratory relief. Relevant to the first prong—whether Davison intends to engage in a\n\ncourse of conduct “arguably” impacted by the challenged conduct, Babbitt, 442 U.S. at\n\n298—the district court found, in awarding Davison declaratory relief, that he “continues\n\nto avail himself” of the Chair’s Facebook Page and that Davison is “active in local\n\npolitics, and has a particular interest in what he believes to be corruption on the part of\n\nLoudoun County’s school board.” Davison, 267 F. Supp. 3d at 707, 723. Accordingly,\n\n\n 15\n\nthe evidence establishes that Davison continues to engage in a course of conduct—\n\nnamely, posting about alleged municipal corruption on the Chair’s Facebook Page—\n\nlikely to be impacted by Randall’s allegedly unconstitutional approach to managing the\n\npage.\n\n Turning to the second prong—whether there is a credible threat of enforcement—\n\nRandall previously blocked Davison from the Chair’s Facebook Page based on the\n\ncontent of his posts, providing “good evidence that the threat of enforcement is not\n\nchimerical.” Driehaus, 134 S. Ct. at 2345 (internal quotation marks omitted).\n\nAdditionally, Randall testified that she continues to believe she can ban Davison and\n\nothers from the Chair’s Facebook Page based on their views without triggering the First\n\nAmendment at all. See J.A. 277 (Randall stating she would “be happy to” ban other\n\ncommenters on her “Chair’s Facebook” page); J.A. 250 (Randall testifying that\n\ncomments “attacking another person” would not be allowed on her “Chair’s Facebook”\n\npage). To that end, in awarding Davison declaratory relief, the district court found that\n\nRandall “maintains she is permitted to administer this Facebook page as a purely personal\n\npage.” Davison, 267 F. Supp. 3d at 723. Accordingly, Davison established that he has\n\nbeen subject to past enforcement and that Randall has not “disavowed” future\n\nenforcement, which, under Kenny, is sufficient to establish a credible threat of\n\nenforcement. Cf. City of Lakewood v. Plain Dealer Pub. Co., 486 U.S. 750, 757 (1988)\n\n(“[T]he mere existence of the licensor’s unfettered discretion, coupled with the power of\n\nprior restraint, intimidates parties into censoring their own speech, even if the discretion\n\nand power are never actually abused.”).\n\n\n 16\n\n In sum, Davison’s evidence demonstrated—and the district court found—that\n\nDavison intends to continue to use the Chair’s Facebook Page and that Davison faces a\n\ncredible threat of future enforcement. See Davison, 267 F. Supp. 3d at 723.\n\nAccordingly, Davison adduced facts establishing an injury in fact sufficient to justify the\n\nprospective declaratory relief awarded by the district court.\n\n B.\n\n Next, Randall asserts that the district court erred in concluding, with regard to\n\nDavison’s individual capacity First Amendment claim, that Randall acted “under color of\n\nstate law,” as that phrase is used in Section 1983, in administering the Chair’s Facebook\n\nPage and banning Davison from that page. “This Court reviews judgments stemming\n\nfrom a bench trial under a mixed standard: factual findings are reviewed for clear error,\n\nwhereas conclusions of law are reviewed de novo.” Helton v. AT&T Inc., 709 F.3d 343,\n\n350 (4th Cir. 2013). Whether, under the undisputed facts, Randall acted under color of\n\nstate law is a legal question this Court reviews de novo. Rossignol v. Voorhaar, 316 F.3d\n\n516, 523 (4th Cir. 2003).\n\n To state a claim under Section 1983, a plaintiff must show that the alleged\n\nconstitutional deprivation at issue occurred because of action taken by the defendant\n\n“under color of . . . state law.” Philips v. Pitt Cty. Mem’l Hosp., 572 F.3d 176, 180 (4th\n\nCir. 2009). “The traditional definition of acting under color of state law requires that the\n\ndefendant in a § 1983 action have exercised power ‘possessed by virtue of state law and\n\nmade possible only because the wrongdoer is clothed with the authority of state law.’”\n\nWest v. Atkins, 487 U.S. 42, 49 (1988) (quoting United States v. Classic, 313 U.S. 299,\n\n\n 17\n\n326 (1941)). Section 1983’s “color-of-law prerequisite is synonymous with the more\n\nfamiliar state-action requirement” applicable to Fourteenth Amendment claims, “and the\n\nanalysis for each is identical.” Pitt Cty. Mem’l Hosp., 572 F.3d at 180. Both inquiries\n\ndemand that “the conduct allegedly causing the deprivation of a federal right be fairly\n\nattributable to the State.” Holly v. Scott, 434 F.3d 287, 292 (4th Cir. 2006) (quoting\n\nLugar v. Edmondson Oil Co., Inc., 457 U.S. 922, 937 (1982)).\n\n “[T]here is no specific formula for determining whether state action is present.”\n\nId. at 292 (internal quotation marks omitted). Rather, “[w]hat is fairly attributable [to the\n\nstate]”—i.e., what constitutes action under color of state law—“is a matter of normative\n\njudgment, and the criteria lack rigid simplicity.” Id. (internal quotation marks omitted).\n\nCourts must examine the “totality of the circumstances,” id. (internal quotation marks\n\nomitted), to determine if the action at issue “bore a ‘sufficiently close nexus’ with the\n\nState to be ‘fairly treated as that of the State itself,’” Rossignol, 316 F.3d at 525 (quoting\n\nJackson v. Metro. Edison Co., 419 U.S. 345, 351 (1974)).\n\n Although no one factor is determinative, this Court has held that a defendant’s\n\npurportedly private actions bear a “sufficiently close nexus” with the State to satisfy\n\nSection 1983’s color-of-law requirement when the defendant’s challenged “actions are\n\nlinked to events which arose out of his official status.” Id. at 524. When a defendant’s\n\n“status” as a public official “enabled [her] to execute [a challenged action] in a manner\n\nthat private citizens never could have,” then the action also is more likely to be treated as\n\nattributable to the state. Id. at 526; see also Martinez v. Colon, 54 F.3d 980, 986 (1st Cir.\n\n1995) (“[S]ection 1983 is . . . implicated . . . [when] the conduct is such that the actor\n\n\n 18\n\ncould not have behaved in that way but for the authority of his office.”); Goldstein v.\n\nChestnut Ridge Volunteer Fire Co., 218 F.3d 337, 343 (4th Cir. 2000) (holding that\n\nchallenged conduct is more likely to amount to state action when “the injury caused is\n\naggravated in a unique way by the incidents of governmental authority” (internal\n\nquotation marks omitted)). Likewise, an official’s conduct is more likely to amount to\n\nstate action when it “occurs in the course of performing an actual or apparent duty of his\n\noffice.” Martinez, 54 F.3d at 986. And the challenged action of a defendant\n\ngovernmental official is likely to be treated as taken under color of law when the official\n\n“use[d] the power and prestige of his state office to damage the plaintiff.” Harris v.\n\nHarvey, 605 F.2d 330, 337 (7th Cir. 1979). In the context of an alleged First Amendment\n\nviolation, in particular, this Court has found that a challenged action by a governmental\n\nofficial is fairly attributable to the state when “the sole intention” of the official in taking\n\nthe action was “to suppress speech critical of his conduct of official duties or fitness for\n\npublic office.” Rossignol, 316 F.3d at 524.\n\n Here, after thoroughly analyzing the totality of the circumstances surrounding\n\nRandall’s creation and administration of the Chair’s Facebook Page and banning of\n\nDavison from that page, the district court concluded that Randall acted under color of\n\nstate law. Davison, 267 F. Supp. 3d at 723. We agree.\n\n Randall created and administered the Chair’s Facebook Page to further her duties\n\nas a municipal official. She used the Chair’s Facebook Page “as a tool of governance,”\n\nid. at 713: through the Chair’s Facebook Page, Randall provides information to the public\n\n\n\n\n 19\n\nabout her and the Loudoun Board’s official activities and solicits input from the public on\n\npolicy issues she and the Loudoun Board confront. See supra Part I.A.\n\n For instance, Randall used the Chair’s Facebook Page to inform the public about\n\nserious public safety events and to keep her constituents abreast of the County’s response\n\nto a snowstorm and to coordinate snow removal activities. And, as the district court\n\ncorrectly emphasized, Randall\n\n swathe[d] the [Chair’s Facebook Page] in the trappings of her office.\n Among other things, (1) the title of the page includes [Randall]’s title; (2)\n the page is categorized as that of a government official; (3) the page lists as\n contact information [Randall]’s official County email address and the\n telephone number of [Randall]’s County office; (4) the page includes the\n web address of [Randall]’s official County website; (5) many—perhaps\n most—of the posts are expressly addressed to “Loudoun,” [Randall]’s\n constituents; (6) [Randall] has submitted posts on behalf of the [Loudoun\n Board] as a whole; (7) [Randall] has asked her constituents to use the\n [Chair‘s Facebook Page] as a channel for “back and forth constituent\n conversations”; and (8) the content posted has a strong tendency toward\n matters related to [Randall]’s office.\n\nDavison, 267 F. Supp. 3d at 714. A private citizen could not have created and used the\n\nChair’s Facebook Page in such a manner. Rossignol, 316 F.3d at 526. Put simply,\n\nRandall clothed the Chair’s Facebook Page in “the power and prestige of h[er] state\n\noffice,” Harris, 605 F.2d at 337, and created and administered the page to “perform[]\n\nactual or apparent dut[ies] of h[er] office,” Martinez, 54 F.3d at 986.\n\n Additionally, the specific actions giving rise to Davison’s claim—Randall’s\n\nbanning of Davison’s Virginia SGP Page—“are linked to events which arose out of h[er]\n\nofficial status.” Rossignol, 316 F.3d at 524. Randall’s post to the Chair’s Facebook Page\n\nthat prompted Davison’s comment informed the public about what happened at the\n\n\n\n 20\n\nLoudoun Board and Loudoun County School Board’s joint meeting. And Davison’s\n\ncomment also dealt with an issue related to that meeting and of significant public\n\ninterest—School Board members’ alleged conflicts of interest in approving financial\n\ntransactions. That Randall’s ban of Davison amounted to an effort “to suppress speech\n\ncritical of [such members’] conduct of [their] official duties or fitness for public office”\n\nfurther reinforces that the ban was taken under color of state law. Id. at 525. Considering\n\nthe totality of these circumstances, the district court correctly held that Randall acted\n\nunder color of state law in banning Davison from the Chair’s Facebook Page.\n\n C.\n\n Third, Randall argues that the district court erred in ruling in Davison’s favor on\n\nhis individual capacity First Amendment claim against Randall. Randall principally\n\nchallenges the district court’s conclusion that the Chair’s Facebook Page constitutes a\n\n“public forum” under traditional First Amendment law. We review this legal question de\n\nnovo. See Helton, 709 F.3d at 350.\n\n Under long-established First Amendment law, governmental entities are “strictly\n\nlimited” in their ability to regulate private speech in public fora. Pleasant Grove City,\n\nUtah v. Summum, 555 U.S. 460, 469 (2009). The Supreme Court has recognized two\n\ncategories of public fora: “traditional public forums” and “limited (or designated) public\n\nforums.” Am. Civil Liberties Union v. Mote, 423 F.3d 438, 443 (4th Cir. 2005).\n\n“Traditional” public forums—“such as streets, sidewalks, and parks”—“have the\n\ncharacteristics of a public thoroughfare, a purpose that is compatible with expressive\n\nconduct, as well as a tradition and history of being used for expressive public conduct.”\n\n\n 21\n\nId. “Limited” or “designated” forums are forums that are “not traditionally public, but\n\n[that] the government has purposefully opened to the public, or some segment of the\n\npublic, for expressive activity.” Id. Accordingly, the hallmark of both types of public\n\nfora—what renders the fora “public”—is that the government has made the space\n\navailable—either by designation or long-standing custom—for “expressive public\n\nconduct” or “expressive activity,” and the space is compatible with such activity. Id.\n\n“Conversely, a non-public forum is one that has not traditionally been open to the public,\n\nwhere opening it to expressive conduct would ‘somehow interfere with the objective use\n\nand purpose to which the property has been dedicated.’” Id. (quoting Warren v. Fairfax\n\nCty., 196 F.3d 186, 190–91 (4th Cir. 1999)).\n\n Although neither the Supreme Court nor any Circuit has squarely addressed\n\nwhether, and in what circumstances, a governmental social media page—like the Chair’s\n\nFacebook Page—constitutes a public forum, 3 aspects of the Chair’s Facebook Page bear\n\nthe hallmarks of a public forum. Randall “intentionally open[ed the public comment\n\nsection of the Chair’s Facebook Page] for public discourse,” Cornelius v. NAACP Legal\n\nDefense & Educ. Fund, Inc., 473 U.S. 788, 802 (1985), inviting “ANY Loudoun citizen”\n\n 3\n In addition to the court below, two other district courts have considered whether\na government official’s social media page constituted a public forum. Those courts\nreached conflicting results. Compare Morgan v. Bevin, 298 F. Supp. 3d 1003, 1010 (E.D.\nKy. 2018) (holding that First Amendment forum analysis did not apply to restrictions on\nspeech in the official Facebook and Twitter pages of the Governor of Kentucky), with\nKnight First Amend. Inst. at Colum. Univ. v. Trump, 302 F. Supp. 3d 541, 573 (S.D.N.Y.\n2018) (holding that the interactive component of the President’s Twitter account, as\nopposed to the President’s tweets themselves, constituted a designated public forum),\nappeal docketed, No. 18-1691 (2d Cir. Oct. 24, 2018).\n\n\n\n 22\n\nto make posts to the comments section of the Chair’s Facebook Page—the interactive\n\ncomponent of the page—“on ANY issues, request, criticism, complement or just your\n\nthoughts,” J.A. 455. Randall placed no restrictions on the public’s access to the page or\n\nuse of the interactive component of the Chair’s Facebook Page. And, in accordance with\n\nRandall’s invitation, the public made numerous posts on matters of public concern.\n\n The Chair’s Facebook Page also is “compatib[le] with expressive activity.”\n\nCornelius, 473 U.S. at 802. “Congress [has] recognized the internet and interactive\n\ncomputer services as offering ‘a forum for a true diversity of political discourse, unique\n\nopportunities for cultural development, and myriad avenues for intellectual activity.’”\n\nZeran v. Am. Online, Inc., 129 F.3d 327, 330 (4th Cir. 1997) (quoting 47 U.S.C. §\n\n230(a)(3)); cf. Bland, 730 F.3d at 386 (finding post to campaign Facebook page\n\n“constituted pure speech”). And the Supreme Court recently analogized social media\n\nsites, like the Chair’s Facebook Page, to “traditional” public forums, characterizing the\n\ninternet as “the most important place[] (in a spacial sense) for the exchange of views.”\n\nPackingham v. North Carolina, 137 S. Ct. 1730, 1735 (2017). An “exchange of views”\n\nis precisely what Randall sought—and what in fact transpired—when she expressly\n\ninvited “ANY Loudoun citizen” to visit the page and comment “on ANY issues,” and\n\nreceived numerous such posts and comments. J.A. 455.\n\n Randall nevertheless argues that traditional public forum analysis should not apply\n\nto the Chair’s Facebook Page for two reasons: (1) the Chair’s Facebook Page is “a private\n\nwebsite” and therefore does not constitute “public property” susceptible to forum\n\nanalysis, and (2) the Chair’s Facebook Page, in its entirety, constitutes “government\n\n\n 23\n\nspeech” properly analyzed under the framework set forth in Pleasant Grove. Randall’s\n\nBr. at 19–21, 29–31. We disagree.\n\n Even assuming the intangible space at issue is “private property,” as Randall\n\nclaims—which is not at all clear from the record before us 4—the Supreme Court never\n\nhas circumscribed forum analysis solely to government-owned property. For example, in\n\nCornelius, the Court recognized that forum analysis applies “to private property\n\ndedicated to public use.” Cornelius, 473 U.S. at 801 (emphasis added); see also\n\nChristian Legal Soc’y Chapter of the Univ. of Cal. v. Martinez, 561 U.S. 661, 679 (2010)\n\n(“[T]his Court has employed forum analysis to determine when a governmental entity, in\n\nregulating property in its charge, may place limitations on speech.” (emphasis added)).\n\n 4\n The Facebook “platform” and the “software” that underlies that platform is,\naccording to Facebook’s Terms of Service, property of Facebook, Inc. Terms of Service,\nFacebook, https://www.facebook.com/terms.php (last visited Jan. 4, 2019). Facebook’s\nTerms of Service further provide that users “own the content [they] create and share on\nFacebook and the other Facebook Products,” including Pages. Id. There would seem to\nbe a good argument, therefore, that content created, and posted to Facebook, by\ngovernment officials performing the functions and duties of their offices constitutes\ngovernment property. Cf. Solomons v. United States, 137 U.S. 342, 346–48 (1890)\n(holding that intellectual property created by government employee in the course of his\nofficial duties constituted government property because “[i]f one is employed to devise or\nperfect an instrument, or a means for accomplishing a prescribed result, he cannot, after\nsuccessfully accomplishing the work for which he was employed, plead title thereto as\nagainst his employer”). Likewise, under Facebook’s Terms of Service, the posts and\ncomments by individual Facebook users—like Davison—to a Facebook Page—like the\nChair’s Facebook Page—constitute property of those users. Accordingly, a single\nFacebook Page—including the Chair’s Facebook Page—encompasses a web of property\nrights, some of which may lie with the government. We need not—and thus do not—\ndecide with whom these property rights lie in this particular case, however, because we\nhold that even assuming the Chair’s Facebook Page constitutes private property, Randall,\nacting under color of state law, exercised control over the aspects of that page giving rise\nto Davison’s claim.\n\n\n\n 24\n\nAnd the Supreme Court and lower courts have held that private property, whether\n\ntangible or intangible, constituted a public forum when, for example, the government\n\nretained substantial control over the property under regulation or by contract. See, e.g.,\n\nSe. Promotions, Ltd. v. Conrad, 420 U.S. 546, 547, 555 (1975) (holding that “a privately\n\nowned Chattanooga theater under long-term lease to the city” was a “public forum[]\n\ndesigned for and dedicated to expressive activities”); Halleck v. Manhattan Community\n\nAccess Corp., 882 F.3d 300, 306–07 (2d Cir. 2018) (holding that public access television\n\nchannels operated by a private non-profit corporation constituted public forums), cert.\n\ngranted 139 S. Ct. 360 (2018) (mem.); First Unitarian Church of Salt Lake City v. Salt\n\nLake City Corp., 308 F.3d 1114, 1122 (10th Cir. 2002) (“[F]orum analysis does not\n\nrequire that the government have a possessory interest in or title to the underlying land.\n\nEither government ownership or regulation is sufficient for a First Amendment forum of\n\nsome kind to exist.”); Freedom from Religion Foundation, Inc. v. City of Marshfield,\n\nWis., 203 F.3d 487, 494 (7th Cir. 2000) (holding that private property abutted by public\n\npark constituted public forum).\n\n Significantly, even assuming the relevant aspects of the Chair’s Facebook Page\n\nconstitute private property—which, again, is not entirely clear from the record before\n\nus—Randall, acting under color of state law, retained and exercised significant control\n\nover the page. She created the Chair’s Facebook Page. She designated the page as\n\nbelonging to a “governmental official.” She clothed the page in the trappings of her\n\npublic office. She chose to list her official contact information on the page. And she\n\n\n\n\n 25\n\ncurated the links in the left column of the page and the lists of Facebook Pages or profiles\n\n“liked” by the Chair’s Facebook Page in the right column.\n\n Of particular importance, Randall had complete control over the aspect of the\n\nChair’s Facebook Page giving rise to Davison’s challenge because, as administrator of\n\nthe page, Randall had authority to ban Facebook profiles or Pages from using the Chair’s\n\nFacebook Page—and, therefore, the interactive component of the page—authority she\n\nexercised in banning Davison’s Virginia SGP Page. Cf. Knight, 302 F. Supp. 3d at 566–\n\n67 (holding that the interactive component of the President’s Twitter account constituted\n\npublic forum because the President and his advisors “exercise control over various\n\naspects of the . . . account,” including the power to block other users from accessing the\n\naccount).\n\n The Second Circuit’s decision in Halleck dealing with privately operated public\n\naccess television channels is instructive. Federal law allows cable franchising authorities\n\nto require cable operators to designate channel capacity for public use. Halleck, 882 F.3d\n\nat 302. Likewise, New York regulations oblige cable operators to designate at least one\n\nchannel for full-time public use. Id. Pursuant to that authority, the City of New York\n\nentered into a cable franchise agreement with a cable company requiring the company to\n\nmake available four public access channels, which channels were operated by a private,\n\nnon-profit corporation, MNN. Id. Several producers of public access programming sued\n\nMNN, alleging that MNN violated the producers’ First Amendment rights by indefinitely\n\nsuspending them from using the public access channels “because of disapproval of the\n\ncontent of a TV program” they had submitted for airing. Id.\n\n\n 26\n\n The Second Circuit concluded that the public access channels constituted a public\n\nforum, notwithstanding that they were operated by a private company. Id. at 306–08.\n\nThe court reached that conclusion for two reasons. First, it pointed to the similarities\n\nbetween public access channels and traditional public forums, like parks, describing “[a]\n\npublic access channel [a]s the electronic version of the public square.” Id. at 306.\n\nSecond, the court emphasized the extensive government involvement with, and control\n\nover, public access channels by virtue of the federal and state regulatory schemes. See id.\n\n(“[W]here, as here, federal law authorizes setting aside channels to be ‘the electronic\n\nmarketplace of ideas,’ state regulation requires cable operators to provide at least one\n\npublic access channel, a municipal contract requires a cable operator to provide four such\n\nchannels, and a municipal official has designated a private corporation to run those\n\nchannels, those channels are public forums.” (emphasis added)).\n\n Although not subject to the extensive federal and state regulatory regime\n\napplicable in Halleck, 5 the Chair’s Facebook Page is in many ways analogous to the\n\nprivately-operated public access channels considered by the Second Circuit. Just as the\n\nfederal government sought to establish an “electronic marketplace of ideas” by\n\nmandating provision of public access channels, Randall expressly sought to—and did, in\n\n\n 5\n The federal Communications Decency Act allows private online intermediaries,\nlike Facebook, the ability to moderate content by providing such intermediaries with\nbroad immunity from user-generated content posted on their sites. 47 U.S.C. § 230. This\nCourt has recognized that an “important purpose of § 230 was to encourage service\nproviders to self-regulate the dissemination of offensive material over their services.”\nZeran, 129 F.3d at 331.\n\n\n\n 27\n\nfact—create an “electronic marketplace of ideas” by inviting “ANY” constituent to post\n\nto the Chair Page on “ANY issues.” J.A. 455. Likewise, just as the City of New York\n\nchose to have a private corporation operate the public access channels, Randall chose to\n\ncreate her electronic marketplace of ideas, the Chair’s Facebook Page, on a private\n\nplatform, Facebook. Indeed, the present case provides a stronger basis for treating the\n\ninteractive component of the Chair’s Facebook Page as a public forum because whereas\n\nthe private corporation in Halleck, MNN, exercised control over the aspect of the public\n\naccess channel giving rise to the First Amendment claim—banning the public access\n\nprogram producer—a public official, Randall exercised unconstrained control over the\n\naspect of the Chair’s Facebook Page giving rise to Davison’s claim—banning of other\n\nFacebook profiles and Pages. 6\n\n\n 6\n On October 12, 2018, the Supreme Court granted MNN’s petition for writ of\ncertiorari in Halleck. 139 S. Ct. 360. MNN’s petition presented two questions: (1)\n“[w]hether the Second Circuit erred in rejecting th[e Supreme] Court’s state actor tests\nand instead creating a per se rule that private operators of public access channels are state\nactors subject to constitutional liability” and (2) “[w]hether the Second Circuit erred in\nholding—contrary to the Sixth and D.C. Circuits—that private entities operating public\naccess televisions stations are state actors for constitutional purposes where the state has\nno control over the private entity’s board or operations.” Petition for Writ of Certiorari i,\nManhattan Community Access Corp. v. Halleck, --- S. Ct. --- (No. 17-1702). MNN’s\nargument before the Supreme Court, therefore, focuses on the Second Circuit’s\ndetermination that MNN constituted a state actor, not the court’s determination that the\npublic access channels constituted a public forum.\n\n Although not identified as an issue on appeal, MNN’s petition also took issue with\nthe Second Circuit’s determination that the public access channels operated by MNN\nconstituted a public forum. But that contention was entirely derivative of its state action\nargument. In particular, MNN objected to the Second Circuit’s public forum conclusion\nonly because the public access channels were privately operated and because, in its\nopinion, the Second Circuit’s purportedly “categorical” holding that public access\n(Continued)\n\n 28\n\n Not only does case law contradict Randall’s argument that public forum analysis\n\nnever applies to private property, her argument also fails because it makes no legal sense\n\nto establish a bright-line rule that forum analysis applies only to government-owned\n\nproperty. Why, for example, should the First Amendment allow a municipality to engage\n\nin viewpoint discrimination in curating a public library branch in leased space but not\n\nallow the municipality to engage in such discrimination in a library branch on\n\nmunicipally owned property? Cf. Bd. of Educ., Island Trees Union Free Sch. Dist. No.\n\n26 v. Pico, 457 U.S. 853, 870–71 (1982) (plurality op.) (“If a Democratic school board,\n\nmotivated by partisan affiliation, ordered removal of all books written by or in favor of\n\nRepublicans, few would doubt that the order violated the constitutional rights of the\n\nstudents denied access to those books.”). Or why should a municipality be allowed to\n\nengage in viewpoint discrimination when holding a virtual public meeting hosted on a\n\nprivate website when such discrimination would be unconstitutional if the meeting was\n\nheld in a governmental building? Cf. Lyrissa Lidsky, Public Forum 2.0, 91 B.U. L. Rev.\n\n1975, 1996 (2011) (“Just as the government can rent a building to use as a forum for\n\npublic debate and discussion, so, too, can it ‘rent’ a social media page for the promotion\n\n\n\nchannels constitute public forums ignore[d] “the far more critical issue of whether (and to\nwhat extent) there is government control over a public access channel.” Id. at 19–20.\n\n Here, a government official acting under color of state law, Randall, exercised\nunconstrained control over the aspect of the Chair’s Facebook Page giving rise to\nDavison’s claim.\n\n\n\n\n 29\n\nof public discussion.”). We do not believe the First Amendment draws such arbitrary\n\nlines.\n\n Randall’s second argument—that the Chair’s Facebook Page amounts to\n\n“government speech”—fails to recognize the meaningful difference between Randall’s\n\nposts to the Chair’s Facebook Page and the public comments and posts she invited in the\n\npage’s interactive space. To be sure, Randall’s comments and curated references on the\n\nChair’s Facebook Page to other Pages, personal profiles, and websites amount to\n\ngovernmental speech. See Sutliffe v. Epping School Dist., 584 F.3d 314, 329–30 (1st Cir.\n\n2009) (holding that municipality’s refusal to place hyperlink on municipal website to\n\nwebsite of group opposed to municipal budget constituted government speech); Page v.\n\nLexington Cty. School Dist. One, 531 F.3d 275, 283–85 (4th Cir. 2008) (holding that\n\nSchool District’s refusal to place hyperlink on its website to website of group that\n\nopposed School District’s position on pending legislation constituted government speech\n\nbecause, in part, “the links to other websites were selected by the School District alone as\n\nones that supported its own message”); Knight, 302 F. Supp. 3d at 571 (“[T]he\n\nPresident’s tweets are [not] susceptible to forum analysis . . . because the content is\n\ngovernment speech.”).\n\n But the interactive component of the Chair’s Facebook Page—the portion of the\n\nmiddle column in which the public can post comments, reply to posts, and “like”\n\ncomments and posts—is materially different. See Knight, 302 F. Supp. 3d at 572\n\n(distinguishing a government official’s tweets and “the interactive space for replies and\n\nretweets”). Randall placed no formal limitations on the ability of Facebook personal\n\n\n 30\n\nprofiles and Pages to access the Chair’s Facebook Page and make comments and posts to\n\nthe interactive component of the page. On the contrary, she expressly invited posts to the\n\npage “from ANY Loudon citizen on ANY issues, request, criticism, complement or just\n\nyour thoughts.” J.A. 455. And comments and posts by users cannot be mistaken for\n\nRandall’s own speech because they identify the posting or replying personal profile or\n\nPage, and thereby distinguish that user from Randall.\n\n Contrary to Randall’s argument that the Chair’s Facebook Page, in its entirety,\n\namounts to government speech, the present case also is meaningfully distinguishable\n\nfrom the government speech framework identified in Pleasant Grove. There, a\n\nmunicipality denied a private religious group’s request to allow it to erect a “monument\n\nin a city park in which other donated monuments were previously erected,” including a\n\nmonument depicting a prominent symbol of a different religion. 555 U.S. at 464. The\n\nplaintiff religious group sought relief under the First Amendment, arguing that the city\n\npark constituted a traditional public forum, and therefore that the city could not reject the\n\nreligious group’s proposed monument when it had previously allowed construction of a\n\nmonument associated with another religion. Id. at 466.\n\n The Supreme Court held that the city did not violate the First Amendment because\n\nthe government speech framework, rather than forum analysis, applied to the conduct at\n\nissue. In reaching that conclusion, the Court emphasized that the city never “opened up\n\nthe Park for the placement of whatever permanent monuments might be offered by\n\nprivate donors.” Id. at 472–73. “Rather, the City has ‘effectively controlled’ the\n\nmessages sent by the monuments in the Park by exercising ‘final approval authority’ over\n\n\n 31\n\ntheir selection.” Id. at 473. The Court further emphasized that “[t]he forum doctrine has\n\nbeen applied in situations in which government-owned property or a government\n\nprogram was capable of accommodating a large number of public speakers without\n\ndefeating the essential function of the land or the program.” Id. at 478. A city park,\n\nhowever, “can accommodate only a limited number of permanent monuments,” and\n\ntherefore a municipality cannot—and need not—provide park space for all who wish to\n\nerect a monument. Id.\n\n Here, Randall “effectively controlled” certain aspects of the Chair’s Facebook\n\nPage: she curated the Chair’s Facebook Page’s left and right columns and made posts to\n\nthe middle column. Id. at 472. But Randall also expressly opened the Chair’s Facebook\n\nPage’s middle column—its interactive space—for “ANY” user to post on “ANY issues,”\n\nJ.A. 455, and therefore did not retain “final approval authority” over that aspect of the\n\nChair’s Facebook Page, Pleasant Grove, 555 U.S. at 473. Just as the parkland\n\nsurrounding monuments in Pleasant Grove continued to constitute a public forum, even\n\nthough the monuments themselves constituted government speech, so too the interactive\n\ncomponent of the Chair’s Facebook Page constitutes a public forum, even though\n\nRandall’s curation of and posts to the Chair’s Facebook Page amount to government\n\nspeech. Additionally, the interactive component of the Chair’s Facebook Page does not\n\nface the same spacial limitations as those of the park in Pleasant Grove, but instead is\n\n“capable of accommodating a large number of public speakers without defeating [its]\n\nessential function.” Id. at 578. Accordingly, Pleasant Grove supports, rather than\n\n\n\n\n 32\n\nundermines, our conclusion that the interactive component of the Chair’s Facebook Page\n\nconstitutes a public forum.\n\n Upon concluding that interactive component of the Chair’s Facebook Page\n\namounts to a public forum, we would normally need to determine whether it constitutes a\n\ntraditional public forum or designated or limited public forum. In the present case,\n\nhowever, we need not decide that question because Randall’s ban of Davison amounted\n\nto “viewpoint discrimination,” which is “prohibited in all forums.” See Child Evangelism\n\nFellowship of S.C. v. Anderson Sch. Dist. Five, 470 F.3d 1062, 1067 n.2 (4th Cir. 2006).\n\n“Viewpoint discrimination . . . ‘targets not subject matter, but particular views taken by\n\nspeakers on a subject.’” Id. (quoting Rosenberger v. Rector & Visitors of Univ. of Va.,\n\n515 U.S. 819, 829 (1995)). Viewpoint discrimination is apparent, for example, if a\n\ngovernment official’s decision to take a challenged action was “impermissibly motivated\n\nby a desire to suppress a particular point of view.” Cornelius, 473 U.S. at 812–13.\n\n Here, the district court found—as the record amply supports—that Randall banned\n\nDavison’s Virginia SGP Page because Davison posted a comment using that page\n\nalleging “corruption on the part of Loudoun County’s School Board involving conflicts\n\nof interests among the School Board and their family members.” Davison, 267 F. Supp.\n\n3d at 711. Although Randall stated that she had “no idea” whether Davison’s allegations\n\nwere “correct,” she nonetheless banned him because she viewed the allegations as\n\n“slanderous” and she “didn’t want [the allegations] on the site.” Id. at 717. Randall’s\n\ndecision to ban Davison because of his allegation of governmental corruption constitutes\n\nblack-letter viewpoint discrimination.\n\n\n 33\n\n Put simply, Randall unconstitutionally sought to “suppress” Davison’s opinion\n\nthat there was corruption on the School Board. Cornelius, 473 U.S. at 812–13; see also,\n\ne.g., Rossignol, 316 F.3d at 521 (holding that sheriff’s deputies engaged in viewpoint\n\ndiscrimination when they seized an issue of a newspaper that criticized the county\n\nsheriff’s and his deputies’ performance of their official duties); Putnam Pit, Inc. v. City of\n\nCookeville, Tenn., 221 F.3d 834, 846 (6th Cir. 2000) (holding that a municipality engages\n\nin viewpoint discrimination if it refuses to link newspaper webpage to the city’s website\n\nsolely because the newspaper sought to expose municipal corruption); Knight, 302 F.\n\nSupp. 3d at 575 (holding that the President engaged in viewpoint discrimination when he\n\nblocked individuals from his Twitter account because the individuals “posted tweets that\n\ncriticized the President or his policies”). 7 That Randall’s action targeted comments\n\ncritical of the School Board members’ official actions and fitness for office renders the\n\nbanning all the more problematic as such speech “occupies the core of the protection\n\nafforded by the First Amendment.” Rossignol, 316 F.3d at 521 (quoting McIntyre v.\n\nOhio Elections Comm’n, 514 U.S. 334, 346 (1995)).\n\n In sum, the interactive component of the Chair’s Facebook Page constituted a\n\npublic forum, and Randall engaged in unconstitutional viewpoint discrimination when\n\nshe banned Davison’s Virginia SGP Page from that forum.\n\n\n 7\n Randall also asserts that she did not violate Davison’s First Amendment rights\nbecause she banned his “Virginia SGP” Page, not his “Brian Davison” profile. Davison\nis the sole operator of the “Virginia SGP” Page, however, and therefore the ban\nimplicated his First Amendment rights. Randall fails to identify any case supporting her\nposition, nor have we found any. Accordingly, we reject this argument.\n\n\n 34\n\n III.\n\n In his cross-appeal, Davison asserts that the district court reversibly erred in two\n\nways: (A) by dismissing his claim against Randall in her official capacity and (B) by\n\ndenying his motion to amend his complaint to add the new First Amendment claim\n\nagainst the Loudoun Board. 8 We disagree.\n\n A.\n\n Davison first argues that the district court erred in dismissing his claim against\n\nRandall in her official capacity. Whereas “[p]ersonal-capacity suits seek to impose\n\npersonal liability upon a government official for actions [she] takes under color of state\n\nlaw,” Kentucky v. Graham, 473 U.S. 159, 165 (1985), “official capacity suits are ‘treated\n\nas suits against the municipality,’” Santos v. Frederick Cty. Bd. of Comm’rs, 725 F.3d\n\n451, 469 (4th Cir. 2013) (quoting Hafer v. Melo, 502 U.S. 21, 25 (1991)). Because\n\n“municipal liability under Section 1983 does not amount to respondeat superior . . . a\n\n 8\n Davison also argues that the district court erred in rejecting his procedural due\nprocess claims under the Fourteenth Amendment and an analogous provision in the\nVirginia Constitution. Before the district court, Davison “flatly asserted that due process\nalways requires the government to provide a hearing before imposing a prior restraint on\nspeech,” and therefore that Randall violated Davison’s First Amendment rights by failing\nto conduct a pre-ban hearing. Davison, 267 F. Supp. 3d at 719. The district court\ncorrectly rejected Davison’s proposed categorical rule. Id. (citing Cafeteria & Rest.\nWorkers Union Local 473, AFL-CIO v. McElroy, 367 U.S. 886, 895 (1961). And\nDavison has abandoned that asserted categorical rule on appeal, Davison’s Br. at 49–50\nn.19 (“[I]t might be permissible in certain contexts to delete an individual comment\nwithout providing full pre-deprivation process . . . .”), instead arguing he is entitled to\nrelief under the balancing test set forth in Mathews v. Eldridge, 424 U.S. 319, 334–35\n(1976). Because Davison did not make that argument before the district court, we decline\nto consider it now. See CoreTel Va., LLC v. Verizon Va., LLC, 808 F.3d 978, 988 (4th\nCir. 2015).\n\n\n\n 35\n\nmunicipality is subject to Section 1983 liability only when its ‘policy or custom, whether\n\nmade by its lawmakers or by those whose edicts or acts may fairly be said to represent\n\nofficial policy, inflicts the [plaintiff’s] injury.’” Id. at 469–70 (quoting Monell v. Dep’t of\n\nSoc. Servs. of the City of N.Y., 436 U.S. 658, 694 (1978)).\n\n Here, the district court dismissed Davison’s official capacity claim because it\n\nfound that “no policy—whether County-wide or specific to [Randall]’s office—played\n\nany role in [Randall]’s decision to ban [Davison] from her [Chair’s Facebook Page].”\n\nDavison, 267 F. Supp. 3d at 715. We review the district court’s factual findings bearing\n\non whether Randall acted pursuant to a municipal policy or custom for clear error and its\n\nlegal conclusions de novo. Helton, 709 F.3d at 350.\n\n On appeal, Davison does not dispute the district court’s finding—which the record\n\namply supports—that Loudoun County did not promulgate a policy governing individual\n\nLoudoun Board members’ Facebook pages. Rather, Davison principally 9 argues that “the\n\ncounty can be held liable for Randall’s actions because in banning Davison, Randall\n\nacted as a municipal policymaker.” Davison’s Br. at 47.\n\n\n\n\n 9\n Davison also argues the Loudoun Board’s failure to adopt a policy pertaining to\nindividual board members’ Facebook pages gives rise to an official capacity claim\nbecause it establishes that the Loudoun “Board was—and remains—deliberately\nindifferent to the likelihood of unconstitutional censorship and viewpoint-based\ndiscrimination on individual supervisors’ social media sites.” Davison’s Br. at 46. But\nDavison never advanced a “deliberate indifference” theory of municipal liability before\nthe district court. Again, we decline to consider an argument Davison raises for the first\ntime on appeal. See CoreTel, LLC, 808 F.3d at 988.\n\n\n\n 36\n\n Davison is correct that “municipal liability may be imposed for a single decision\n\nby municipal policymakers under appropriate circumstances.” Hunter v. Town of\n\nMocksville, N.C., 897 F.3d 538, 554 (4th Cir. 2018) (quoting Pembaur v. City of\n\nCincinnati, 475 U.S. 469, 480 (1986)). “[I]n assessing whether a municipality may be\n\nheld liable for constitutional or statutory violations of their decisionmakers, the\n\ntouchstone inquiry is whether ‘the decisionmaker possesses final authority to establish\n\nmunicipal policy with respect to the action ordered.’” Id. at 554–55 (emphasis added)\n\n(quoting Liverman v. City of Petersburg, 844 F.3d 400, 413 (4th Cir. 2016)).\n\n Here, Davison failed to put forward evidence establishing that Randall was a final\n\nmunicipal policymaker with regard to her banning of Davison from the Chair’s Facebook\n\nPage. On the contrary, record evidence establishes that the Loudoun Board retained\n\nauthority to establish municipal policy with respect to social media pages, as it adopted a\n\nsocial media policy governing the County’s official social media pages. Davison\n\nconcedes as much, arguing that the Loudoun Board “neglected . . . to extend its written\n\nguidelines to Board members’ official pages.” Davison’s Br. at 46. But that argument\n\npresupposes that the Loudoun Board—not Randall—had authority to establish municipal\n\npolicy with respect “to Board members’ official pages.”\n\n Davison nevertheless argues that the Loudoun Board “implicitly” delegated its\n\nfinal policymaking authority to Randall by not addressing individual Loudoun Board\n\nmembers’ official pages in its social media policy. Davison is correct that delegation of\n\nfinal policy making authority may be “implied from a continued course of knowing\n\nacquiescence by the governing body in the exercise of policymaking authority by an\n\n\n 37\n\nagency or official.” Id. at 48 (quoting Spell v. McDaniel, 824 F.2d 1380, 1387 (4th Cir.\n\n1987)). But Davison identifies no evidence that the Loudoun Board knew of the Chair’s\n\nFacebook Page, let alone that it “aquiesce[d]” in Randall’s administration of the page and\n\nbanning of Davison, in particular. On the contrary, the district court found that Randall\n\nmade a one-off, “unilateral decision to ban [Davison] in the heat of the moment, and\n\nreconsidered soon thereafter,” Davison, 267 F. Supp. 3d at 715—before the Loudoun\n\nBoard had a chance to learn of her action. In such circumstances, the district court did\n\nnot reversibly err in rejecting Davison’s official capacity claim.\n\n B.\n\n Next, Davison argues that the district court erred in denying him leave to amend\n\nhis complaint to add a claim that “the County violates the First Amendment by\n\nmaintaining a limited public forum on Facebook,” when policies imposed by Facebook,\n\nrather than the County, restrain, or have the potential to restrain, speech. J.A. 74. “A\n\ndistrict court may deny a motion to amend when the amendment would be prejudicial to\n\nthe opposing party, the moving party has acted in bad faith, or the amendment would be\n\nfutile.” Equal Rights Ctr. v. Niles Bolton Assocs., 602 F.3d 597, 603 (4th Cir. 2010).\n\nThe magistrate judge recommended—and the district court agreed—that Davison be\n\ndenied leave to amend on grounds of both futility and prejudice. We review for abuse of\n\ndiscretion a district court’s denial of leave to amend for prejudice, whereas we review de\n\nnovo a district court’s denial of leave to amend on the basis of futility. See U.S. ex rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n\n\n\n 38\n\n Regarding prejudice, the district court determined that the amendment came “too\n\nlate in these proceedings” and would “add a new, novel legal theory to the case after the\n\nclose of discovery, after the existing claims against [the Loudoun Board] have been\n\nshown to be meritless, after the point at which Defendants could have addressed the\n\nclaim in briefing before trial, and on the eve of trial.” J.A. 74. The district court did not\n\nabuse its discretion in denying leave to amend in such circumstances. See, e.g., Equal\n\nRights Ctr., 602 F.3d at 603–04 (holding that district court did not abuse its discretion in\n\ndenying leave to amend on the basis of prejudice when amendment came after the close\n\nof discovery and “on the eve of the deadline for dispositive motions” and therefore\n\n“would [have] change[d] the nature of the litigation”); Deasy v. Hill, 833 F.2d 38, 41 (4th\n\nCir. 1987) (affirming denial of leave to amend on grounds of prejudice when “the motion\n\nto amend came right before trial and after discovery was complete”).\n\n Although we affirm the district court’s judgment on the basis of its finding of\n\nprejudice, we do not concur in its conclusion as to futility. “Futility is apparent if the\n\nproposed amended complaint fails to state a claim under the applicable rules and\n\naccompanying standards.” Katyle v. Penn Nat. Gaming, Inc., 637 F.3d 462, 471 (4th Cir.\n\n2011). Accordingly, Davison’s proposed amendment was futile if the new claim would\n\nnot have survived a motion to dismiss under Federal Rule of Civil Procedure 12(b)(6).\n\nSee Runnion ex rel. Runnion v. Girl Scouts of Greater Chicago & Nw. Ind., 786 F.3d 510,\n\n524 (7th Cir. 2015) (“[W]hen the basis for denial is futility, we apply the legal\n\nsufficiency standard of Rule 12(b)(6) to determine whether the proposed amended\n\ncomplaint fails to state a claim.”).\n\n\n 39\n\n Davison’s proposed First Amendment claim deals not with the Chair’s Facebook\n\nPage—which the Loudoun Board did not authorize or attempt to regulate—but rather\n\nwith Loudoun County’s official Facebook Pages created and maintained pursuant to the\n\nLoudoun Board’s social media policy. As with his claims related to the Chair’s\n\nFacebook Page, Davison alleged that the Facebook Pages created and maintained by the\n\nLoudoun Board constituted public forums subject to the First Amendment. Davison\n\ntheorized that the Loudoun Board’s decision to use Facebook as its social media forum\n\nviolated his First Amendment rights because Facebook rules permit individual\n\n“requesting” users to ban other personal profiles and Pages such that the banned users can\n\nno longer see posts authored by the requesting users. In such circumstances, the banned\n\nusers “cannot see [the requesting user’s] comment[s] or participate in the discussion\n\nsurrounding the [requesting] party’s comment.” Davison’s Br. at 59. Davison’s\n\nproposed amended complaint asserted that “this scenario violates the First Amendment\n\nbecause Loudoun County has effectively enabled third parties to exclude discussion\n\nwithin a public forum—something a government body could not permissibly do in a\n\nphysical forum.” Id. at 59–60 (internal citation omitted). Put differently, Davison\n\ntheorized that Loudoun County violated the First Amendment by choosing to use\n\nFacebook as a public forum, when rules imposed by Facebook allow private users to\n\nrestrict access to their posts—and comments on and responses to those posts—including\n\nposts to any municipal Facebook Page.\n\n No court appears to have addressed that novel legal theory. And although the First\n\nAmendment constrains only government policies, not policies established by private\n\n\n 40\n\nentities, one can conceive of a colorable legal argument that a governmental actor’s\n\ndecision to select a private social media website for use as a public forum—and therefore\n\nselect that website’s suite of rules and regulations—could violate the First Amendment, if\n\nthe private website included certain types of exclusionary rules. For example, if the\n\ngovernment chose as its electronic public forum a social media site that allowed only\n\nregistered members of one political party to post and comment, there would seem to be a\n\ncompelling argument that the government’s selection of that social media site violated the\n\nFirst Amendment rights of members of other political parties, even if the partisan\n\nrestriction was imposed by the private company, not the governmental body. Such a\n\nrestriction would be seem to be no different than a municipality choosing to hold a town\n\nhall meeting in a venue that refused admission to individuals associated with a disfavored\n\npolitical party or viewpoint. Cf. DeBoer v. Village of Oak Park, 267 F.3d 558, 571 (7th\n\nCir. 2001) (“[T]he government engages in viewpoint discrimination when it denies access\n\nto a speaker solely to suppress the point of view he espouses on an otherwise includible\n\nsubject.”).\n\n Given that Davison’s proposed claim asserted a novel and colorable legal theory\n\nand that “Rule 12(b)(6) dismissals are especially disfavored in cases where the complaint\n\nsets forth a novel legal theory that can best be assessed after factual development,”\n\nWright v. North Carolina, 787 F.3d 256, 263 (4th Cir. 2015) (internal quotation marks\n\nomitted), we affirm the district court’s denial of Davison’s motion for leave to amend his\n\ncomplaint on the basis of its finding of prejudice but not on the basis of futility.\n\n IV.\n\n\n 41\n\nFor the foregoing reasons, we affirm the judgment of the district court.\n\n AFFIRMED\n\n\n\n\n 42\n[END_CASE]", "role": "user" } ]
4,579,688
William D. BATTLE, III, Plaintiff - Appellant, v. J. LEDFORD, Correctional Officer; R. Edwards, Correctional Officer; Gregory Holloway, Warden of Wallens Ridge State Prison; George Hinkle, Regional Administrator for Virginia Department of Corrections, Defendants - Appellees.
William Battle, III v. J. Ledford
2019-01-08
17-6287
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Motz, Duncan, Thacker", "parties": "", "opinions": [{"author": "DIANA GRIBBON MOTZ, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-6287\n\n\nWILLIAM D. BATTLE, III,\n\n Plaintiff - Appellant,\n\n v.\n\nJ. LEDFORD, Correctional Officer; R. EDWARDS, Correctional Officer;\nGREGORY HOLLOWAY, Warden of Wallens Ridge State Prison; GEORGE\nHINKLE, Regional Administrator for Virginia Department of Corrections,\n\n Defendants - Appellees.\n\n\nAppeal from the United States District Court for the Western District of Virginia, at\nRoanoke. Elizabeth Kay Dillon, District Judge. (7:16-cv-00020-EKD-RSB)\n\n\nArgued: September 25, 2018 Decided: January 8, 2019\n\n\nBefore MOTZ, DUNCAN, and THACKER, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Motz wrote the opinion, in which\nJudge Duncan and Judge Thacker joined.\n\n\nARGUED: Sarah Crandall, Elizabeth Joynes, UNIVERSITY OF VIRGINIA SCHOOL\nOF LAW, Charlottesville, Virginia, for Appellant. Michelle Shane Kallen, OFFICE OF\nTHE ATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for Appellees. ON\nBRIEF: Joseph Charlet, Third Year Law Student, Megan Keenan, Third Year Law\nStudent, Evan Ward, Third Year Law Student, Appellate Litigation Clinic,\nUNIVERSITY OF VIRGINIA SCHOOL OF LAW, Charlottesville, Virginia, for\nAppellant. Mark R. Herring, Attorney General, Trevor S. Cox, Acting Solicitor General,\n\fLaura H. Cahill, Assistant Attorney General, Matthew R. McGuire, Deputy Solicitor\nGeneral, OFFICE OF THE ATTORNEY GENERAL OF VIRGINIA, Richmond,\nVirginia, for Appellees.\n\n\n\n\n 2\n\fDIANA GRIBBON MOTZ, Circuit Judge:\n\n The Prison Litigation Reform Act requires a prisoner to exhaust administrative\n\nremedies before filing suit. When a prisoner filed this action under 42 U.S.C. § 1983\n\nafter exhausting those remedies, the district court held the statute of limitations barred his\n\nsuit. For the reasons that follow, we vacate and remand for further proceedings\n\nconsistent with this opinion.\n\n\n\n I.\n\n William D. Battle, III, entered Wallens Ridge State Prison in Roanoke, Virginia,\n\non December 6, 2013. After Battle completed the inmate intake process, corrections\n\nofficers J. Ledford and R. Edwards (collectively, “the officers”) escorted him to his\n\nassigned housing unit. A physical altercation between Battle and the officers occurred\n\nalong the way.\n\n The officers subsequently filed a disciplinary report against Battle. They charged\n\nthat Battle, who was restrained in handcuffs and leg irons during the transfer, used his\n\nbody to push one of the officers into a food cart. According to the officers, they subdued\n\nBattle by “plac[ing]” him on the ground. Battle disputed this account before a prison\n\nhearing administrator. He denied shoving any officer and instead claimed that a pain in\n\nhis ankle caused him to trip. He stated that the officers responded with unnecessary\n\nviolence: pulling his hair and slamming his head into the concrete floor, causing\n\n“bruising, lacerations, [and] swelling of the face.” Battle requested that the hearing\n\nadministrator examine video footage of the incident to corroborate his account.\n\n 3\n\f The hearing administrator declined to do so; instead, he simply credited the\n\nofficers’ version of the incident. After unsuccessfully appealing this decision to the\n\nprison’s chief warden, Battle submitted a second appeal to the regional corrections\n\nadministrator. On February 27, 2014, the regional administrator rejected Battle’s claim\n\nand issued a form confirming that Battle had reached the “last level of appeal for this\n\ngrievance.” A total of 83 days had passed since the altercation.\n\n On January 11, 2016 — two years and 36 days after the altercation — Battle\n\ncompleted a postage request for a pro se § 1983 complaint alleging the officers used\n\nexcessive force against him, in violation of the Eighth and Fourteenth Amendments. 1\n\nThe parties accept that this postage request establishes the filing date.\n\n The officers moved for summary judgment, arguing that Battle filed outside\n\nVirginia’s two-year statute of limitations applicable to § 1983 claims filed within the\n\njurisdiction. See Va. Code Ann. § 8.01-243(A) (setting limitations for personal injury\n\nactions). Battle countered that his complaint was timely because 42 U.S.C. § 1997e(a) of\n\nthe Prison Litigation Reform Act (“PLRA”) required him to exhaust available\n\nadministrative remedies before bringing a § 1983 claim. He argued that the 83 days\n\nduring which he participated in the required exhaustion should be tolled under two\n\n\n\n\n 1\n Battle’s complaint also named corrections administrators Gregory Holloway and\nGeorge Hinkle as defendants. The district court held that Battle failed to state a claim\nagainst these two officials. Battle does not appeal their dismissal.\n\n 4\n\fVirginia statutes and federal law, thus extending his filing deadline to February 27,\n\n2016. 2\n\n The first state statute on which Battle relied, Va. Code § 8.01-229(K), suspends\n\nthe statute of limitations for personal injury actions during criminal proceedings. The\n\nsecond, Va. Code § 8.01-195.3(7), governs actions brought under the Virginia Tort\n\nClaims Act (“VTCA”) and tolls the time for filing a claim notice during the pendency of\n\na prison grievance process. Additionally, Battle relied on federal equitable tolling law.\n\n The district court considered only Battle’s argument as to Va. Code § 8.01-\n\n229(K). It held that statute could not be used to toll Battle’s limitations period because a\n\n“prison disciplinary proceeding is not a criminal prosecution.” Battle v. Ledford, No.\n\n7:16CV00020, 2017 WL 432822, at *3 n.5 (W.D. Va. Jan. 30, 2017) (citing Wolff v.\n\nMcDonnell, 418 U.S. 539, 556 (1974)). The court then granted the officers’ motion for\n\nsummary judgment, concluding that Battle filed his complaint 36 days too late.\n\n On appeal, Battle concedes that the district court properly rejected his claim under\n\nVa. Code Ann. § 8.01-229(K). He maintains, however, that the court overlooked his\n\nclaims of state statutory tolling under the VTCA and federal equitable tolling, and so\n\nerred in deeming his complaint time-barred.\n\n We review a district court’s grant of summary judgment de novo. Henry v.\n\nPurnell, 652 F.3d 524, 531 (4th Cir. 2011) (en banc). Summary judgment is appropriate\n\n 2\n Battle explained in a related affidavit that he understood from a prisoners’ rights\npamphlet that the exhaustion of administrative remedies required by the Prison Litigation\nReform Act mandated tolling, but could not easily verify the proposition because he had\nlimited access to the law library.\n\n 5\n\fonly when “there is no genuine dispute as to any material fact and the movant is entitled\n\nto judgment as a matter of law.” Fed. R. Civ. P. 56(a).\n\n\n\n II.\n\n Congress did not provide fixed timing rules in § 1983 or its companion provision,\n\n§ 1988. 3 Instead, Congress specified that gaps in § 1983 “should be filled by state law, as\n\nlong as that law is not inconsistent with federal law.” Hardin v. Straub, 490 U.S. 536,\n\n538 (1989).\n\n The Supreme Court has directed that we apply a state’s “statute of limitations\n\ngoverning general personal injury actions” when considering § 1983 claims. Owens v.\n\nOkure, 488 U.S. 235, 251 (1989). A state’s limitations and tolling rules are to be\n\nfollowed unless doing so “defeat[s] either § 1983’s chief goals of compensation and\n\ndeterrence or its subsidiary goals of uniformity and federalism.” Hardin, 490 U.S. at 539\n\n(footnote omitted). If Virginia law allows tolling of Battle’s limitations period, that ends\n\nthe inquiry. See id. at 543 (establishing that states may grant extensions to prisoners\n\n\n\n 3\n Section 1988 provides that where a § 1983 cause of action is\n\n deficient in the provisions necessary to furnish suitable remedies, . . . the\n common law, as modified and changed by the constitution and statutes of\n the State wherein the court having jurisdiction of such civil or criminal\n cause is held, so far as the same is not inconsistent with the Constitution\n and laws of the United States, shall be extended to and govern the said\n courts in the trial and disposition of the cause[.]\n\n42 U.S.C. § 1988(a) (emphasis added).\n\n 6\n\fconsistent with § 1983). If not, Battle’s claim may survive only if federal equitable\n\nprinciples apply to his case.\n\n A.\n\n Virginia lacks a generally applicable statute that pauses limitations to\n\naccommodate administrative exhaustion requirements. See Va. Code Ann. § 8.01-229\n\n(enumerating eleven unrelated exceptions suspending tolling limitations periods). 4 Battle\n\nthus asks us to borrow a tolling provision in the Virginia Tort Claims Act. He does so on\n\nthe theory that he could have brought suit under that law for the same actions against the\n\nsame parties.\n\n To bring suit under the VTCA, a person must provide a notice of claim to the state\n\n“within one year after the cause of action accrues” as a precursor to litigation. Va. Code\n\nAnn. § 8.01-195.7. The claimant must file a complaint in court “within 18 months of the\n\nfiling of the notice of claim, or within two years after the cause of action accrues.” Id. If\n\nthe claimant is a state prisoner, the VTCA provides that the “time for filing the notice of\n\n 4\n We note that Virginia does have its own statute, the Virginia Prisoner Litigation\nReform Act (“VPLRA”), which directly addresses the interaction of limitations and\nexhaustion. Va. Code Ann. § 8.01-243.2 provides:\n\n No person confined in a state or local correctional facility shall bring or\n have brought on his behalf any personal action relating to the conditions of\n his confinement until all available administrative remedies are exhausted.\n Such action shall be brought by or on behalf of such person within one year\n after cause of action accrues or within six months after all administrative\n remedies are exhausted, whichever occurs later.\n\nThis provision does not control Battle’s § 1983 action because the Supreme Court has\nunequivocally held that personal injury limitations periods apply to § 1983 claims. See\nOwens, 488 U.S. at 251; Wilson v. Garcia, 471 U.S. 261, 280 (1985).\n\n 7\n\ftort claim shall be tolled during the pendency of the grievance procedure.” Va. Code\n\nAnn. § 8.01-195.3(7).\n\n The VTCA does not save Battle’s claims for two reasons. First, the VTCA\n\noperates on a tighter schedule than § 1983. It gives a plaintiff only one year to assert his\n\nrights, plus exhaustion. The VTCA’s tolling provision would thus afford Battle one year\n\nand 83 days to take legal action.\n\n Second, and more fundamentally, the VTCA does not govern suits against state\n\nemployees like the one Battle brings here. Rather, it provides a limited waiver of\n\nsovereign immunity that “applies to one type of litigation, tort actions against the\n\nCommonwealth.” Ogunde v. Virginia, 628 S.E.2d 370, 373 (Va. 2006). But § 1983 does\n\nthe reverse: it applies only to state officials, not states themselves. See Will v. Mich.\n\nDep’t of State Police, 491 U.S. 58, 66 (1989). Because Battle could not have substituted\n\na VTCA claim for a § 1983 action, the VTCA’s tolling provision cannot be integrated\n\ninto the federal scheme.\n\n B.\n\n When state statutory tolling rules provide no relief to a prisoner seeking to bring a\n\n§ 1983 claim, some courts have turned to state equitable tolling rules to suspend\n\nlimitations during the mandated exhaustion period. See Heck v. Humphrey, 997 F.2d\n\n355, 358 (7th Cir. 1993) (applying state equitable tolling to suspend limitations period for\n\n§ 1983 plaintiff seeking to bring habeas claim), aff’d on other grounds, 512 U.S. 477\n\n(1994); Rodriguez v. Holmes, 963 F.2d 799, 804–05 (5th Cir. 1992) (same).\n\n\n\n 8\n\f Under Virginia law, equitable estoppel provides the only arguable exception to the\n\nCommonwealth’s general rule against “recogniz[ing] any non-statutory basis for tolling”\n\nlimitations. City of Bedford v. James Leffel & Co., 558 F.2d 216, 217 (4th Cir. 1977)\n\n(internal quotation marks omitted); see also Casey v. Merck & Co., 722 S.E.2d 842, 845\n\n(Va. 2012) (“A statute of limitations may not be tolled, or an exception applied, in the\n\nabsence of a clear statutory enactment to such effect.” (internal quotation marks\n\nomitted)).\n\n To invoke equitable estoppel under Virginia law, a plaintiff must prove, inter alia,\n\nthat the “party claiming estoppel was misled to his injury” by the defendant in a way that\n\nprevented timely filing. Boykins Narrow Fabrics Corp. v. Weldon Roofing & Sheet\n\nMetal, Inc., 266 S.E.2d 887, 890 (Va. 1980). The corrections officers did not mislead\n\nBattle as to his injury or the accrual date by operation of the prison administrative review\n\nprocess. Accordingly, as each party acknowledges, Battle cannot invoke the doctrine.\n\n Battle further concedes that no other Virginia common law rule could save his\n\nclaim.\n\n\n\n III.\n\n A.\n\n With no Virginia rule available to toll the limitations period, we must determine\n\nwhether refusal to do so during a prisoner’s mandatory exhaustion period is “consistent\n\nwith federal law and policy.” Owens, 488 U.S. at 239.\n\n\n\n 9\n\f When a court borrows a state rule “to assist in the enforcement of [a] federal\n\nremedy,” the federal interest always controls. Wilson, 471 U.S. at 269. This is so\n\nbecause “the policies and purposes of the States” do not constitute “the primary office of\n\nthe borrowing provision in § 1988,” which governs § 1983 actions. Id. Rather, § 1988\n\n“is designed to assure that neutral rules of decision will be available to enforce the civil\n\nrights actions, among them § 1983.” Id. Thus, it is the “duty of the federal courts to\n\nassure that the importation of state law will not frustrate or interfere with the\n\nimplementation of national policies.” Occidental Life Ins. Co. of Cal. v. EEOC, 432 U.S.\n\n355, 367 (1977).\n\n But to be held “inconsistent” with § 1983, a state rule must do more than “cause[]\n\nthe plaintiff to lose the litigation.” Robertson v. Wegmann, 436 U.S. 584, 593 (1978).\n\nThe state rule must “defeat either § 1983’s chief goals of compensation and deterrence or\n\nits subsidiary goals of uniformity and federalism.” Hardin, 490 U.S. at 539 (footnote\n\nomitted). If a state’s timing requirement contravenes one or more of these goals, it is\n\n“inconsistent with federal law,” and § 1988 bars us from adopting it. Id. at 538.\n\n The Supreme Court has explained that it is inconsistent with § 1983’s policies to\n\napply “a state statute of limitations” to require a litigant “to refrain from commencing a\n\ncivil action until it has discharged” a process mandated by federal law. Occidental, 432\n\nU.S. at 367–68. “For the State’s wisdom in establishing a general limitation period could\n\nnot have taken into account the decision of Congress to delay judicial action” while the\n\nlitigant “performs its administrative responsibilities.” Id. (internal quotation marks\n\nomitted). The Court has further suggested that tolling of § 1983 limitations may be\n\n 10\n\fnecessary where a remedy “is structured to require previous resort to state proceedings,\n\nso that the claim may not even be maintained in federal court unless such resort be had.”\n\nBd. of Regents of Univ. of State of N.Y. v. Tomanio, 446 U.S. 478, 490 (1980). The Court\n\nhas even warned that the imposition of an “exhaustion requirement might result in the\n\neffective repeal of § 1983” if “statutes of limitations are not tolled pending exhaustion.”\n\nPatsy v. Bd. of Regents of State of Fla., 457 U.S. 496, 514 n.17 (1982).\n\n B.\n\n With this precedent in mind, we consider its application to the case at hand.\n\n Virginia law provides an elaborate administrative grievance process for prisoner\n\ncomplaints. Exhaustion of this remedy involves at least three levels of review. See\n\nVDOC OP 866.1(IV-VI) (describing emergency grievance review, review of informal\n\ncomplaints, and three-stage review of formal complaints). A prisoner has 30 days to\n\nsubmit a formal grievance, and corrections administrators are then given another 180\n\ndays to resolve the grievance. 5 See id.\n\n Given this structure, Virginia’s no-tolling rule, as applied to prisoners seeking to\n\nbring § 1983 claims, frustrates the goals of § 1983 and is thus clearly “inconsistent” with\n\nsettled federal policy. Hardin, 490 U.S. at 538.\n\n\n\n\n 5\n Virginia’s corrections regulations exempt sexual abuse allegations from the 30-\nday filing requirement so that vulnerable victims may press their claims once it is safe for\nthem to do so. VDOC OP 866.1(VI)(A)(1)(c). Absent tolling, this policy could have the\nunintended effect of substantially reducing a prisoner’s § 1983 filing time when bringing\na serious abuse claim against a corrections officer.\n\n 11\n\f First, application of the no-tolling rule would frustrate the purpose of\n\ncompensating prisoners who have sustained constitutional injuries. Under Virginia\n\nregulations — as implemented by state officials — as much as seven months could be\n\nsubtracted from the period in which a prisoner can file a federal claim. This inevitable\n\nand indeterminate reduction in limitations would be wholly contingent on the efficiency\n\nof administrators and the complexity of the case. And as other circuits have noted and\n\ncommon sense suggests, a state’s grievance process may extend beyond the state’s\n\nregulatory deadlines. See, e.g., Brown v. Valoff, 422 F.3d 926, 932–34 (9th Cir. 2005)\n\n(describing grievance process lasting 2 years and 10 months from injury to investigation\n\nreport); see also Gonzalez v. Hasty, 651 F.3d 318, 323 (2d Cir. 2011) (“[T]he time for\n\nachieving a resolution under the PLRA could be considerably longer than 140 days. . . .\n\n[I]t is certainly possible that a full three years could pass while an inmate exhausts his\n\nadministrative remedies.”). Far from advancing compensation, a no-tolling rule would\n\namount to a penalty in which incarcerated persons — subject to severe state control and\n\noften limited in access to legal resources — would receive less time to vindicate § 1983\n\nclaims than all other litigants.\n\n Application of a no-tolling rule here would also fail to serve § 1983’s second\n\nprimary goal — deterrence. Instead, this rule would enable state officials to shrink a\n\nprisoner’s filing window and so limit his opportunity to bring a claim. In this way, a no-\n\ntolling rule would even create perverse incentives for prison commissioners to extend\n\nregulatory deadlines and for wardens and investigators to stall in their review of\n\n\n\n 12\n\findividual grievances, for doing so might limit government officials’ legal exposure. 6 As\n\nthe Seventh Circuit has observed, no-tolling rules thus encourage prison officials to run\n\nout the clock and “exploit the exhaustion requirement through indefinite delay in\n\nresponding to grievances.” Lewis v. Washington, 300 F.3d 829, 833 (7th Cir. 2002)\n\n(internal quotation marks omitted).\n\n Nor would the no-tolling rule advance § 1983’s subsidiary interest in uniformity.\n\nOf course, Virginia’s rule would set a consistent two-year period between accrual and the\n\nlimitations deadline across claims, furthering uniformity in this formalistic respect. But a\n\nrule that calculates the limitations deadline from the date of exhaustion is just as “firmly\n\ndefined” and “easily applied.” Wilson, 471 U.S. at 270 (quoting Chardon v. Fumero\n\nSoto, 462 U.S. 650, 667 (1983) (Rehnquist, J., dissenting)). Moreover, a no-tolling rule\n\nwould destroy any semblance of meaningful uniformity by creating dramatic claim-to-\n\nclaim variance in the actual filing time available to different § 1983 litigants. Between\n\nprisoners, a no-tolling rule would afford a prisoner whose grievance was processed with\n\ndelay less time to file than one whose grievance received speedy resolution. It would\n\nalso create a disparity between those who are incarcerated and those who are not. For\n\nexample, if the injuries claimed here had occurred in the context of an arrest rather than a\n\nprison escort, Battle would have been guaranteed a full two years to file his § 1983 suit,\n\nrather than the abbreviated period he would receive under a no-tolling rule. Such\n\n\n\n 6\n We do not discern or suggest any bad faith or intentional delay by prison\nofficials in Battle’s case. Our point is only that this is possible absent tolling.\n\n 13\n\fsweeping and arbitrary deviations in procedural rights would hardly advance a policy of\n\nuniformity.\n\n Finally, we also cannot even say that accepting Virginia’s no-tolling rule would\n\nfoster federalism interests. This is so because the Commonwealth itself has adopted two\n\nstatutes, the VTCA and VPLRA, that toll prisoner exhaustion periods. See Va. Code\n\nAnn. §§ 8.01-195.7, 8.01-243.2. Although neither provides relief to prisoners seeking to\n\nbring § 1983 claims, their enactment demonstrates that Virginia otherwise has adopted a\n\npolicy of tolling limitations while prison administrators review inmate claims. These\n\nstatutes also make clear that an exhaustion reprieve does not conflict with Virginia’s\n\n“important and salutary purpose” in strictly construing statutes of limitations, which is to\n\nprotect defendants from “unscrupulous plaintiffs who hoard evidence that supports their\n\nposition while waiting for their prospective opponents to discard evidence that would\n\nhelp make a defense.” Burns v. Stafford Cty., 315 S.E.2d 856, 859 (Va. 1984).\n\nAdministrative exhaustion does the opposite: it notifies defendants of a potential claim\n\nand allows both parties to develop a record before coming to court.\n\n In sum, because Virginia’s no-tolling rule is inconsistent with federal law and\n\npolicy, we cannot apply it here.\n\n C.\n\n Notwithstanding this analysis, the officers contend that Virginia’s no-tolling rule\n\nnecessarily comports with federal policies because a separate federal law — the PLRA —\n\nimposes the relevant exhaustion requirement. But by enacting the PLRA, Congress did\n\nnot endorse such a no-tolling rule or diminish the interests underlying § 1983. To so\n\n 14\n\fconclude would be to overread the PLRA’s silence on tolling, misread the PLRA’s\n\npurpose, and ignore the text of § 1983 and § 1988.\n\n First, the silence in the PLRA. It is a cardinal rule that “repeals by implication are\n\nnot favored and will not be presumed unless the intention of the legislature to repeal is\n\nclear and manifest.” Hui v. Castaneda, 559 U.S. 799, 810 (2010) (internal quotation\n\nmarks omitted). Nothing in the text of the PLRA suggests that Congress sought to limit\n\nor modify § 1988(a)’s express command that borrowed provisions of state law must be\n\nconsistent with important, long-recognized federal policies. The PLRA’s legislative\n\nhistory is also silent as to § 1988(a)’s borrowing framework and the Court’s\n\ninterpretation thereof. The conference reports, floor debates, and committee hearings\n\ncontain no discussion of the pressure that mandatory exhaustion would exert on § 1983’s\n\nstate-derived limitations rule absent tolling. See generally Bernard D. Reams & William\n\nH. Manz, A Legislative History of the Prison Litigation Reform Act of 1996, Pub. L. No.\n\n104–134, 110 Stat. 1321 (1997). When confronted with statutory silence, we must\n\n“presume that Congress is aware of the legal context in which it is legislating.” Palisades\n\nCollections LLC v. Shorts, 552 F.3d 327, 335 n.4 (4th Cir. 2008) (internal quotation\n\nmarks omitted).\n\n Nor do we see any indication that Congress intended, through the PLRA, to amend\n\nor override the specific federal policies underlying § 1983 and incorporated into\n\n§ 1988(a). Instead, as the Supreme Court has explained, it is “[b]eyond doubt” that\n\nCongress enacted the PLRA’s exhaustion requirement “to reduce the quantity and\n\nimprove the quality of prisoner suits” by allowing officials the opportunity to take\n\n 15\n\f“corrective action” and ideally “obviating the need for litigation.” Porter v. Nussle, 534\n\nU.S. 516, 524–25 (2002); see also McLean v. United States, 566 F.3d 391, 397 (4th Cir.\n\n2009) (“The purpose of the PLRA was not, however, to impose indiscriminate\n\nrestrictions on prisoners’ access to the federal courts.”).\n\n Senator Kyl, the lead Senate sponsor of the PLRA, explained that an exhaustion\n\nrequirement would “free up judicial resources for claims with merit by both prisoners and\n\nnonprisoners” alike by winnowing meritless claims. 141 Cong. Rec. S7526 (daily ed.\n\nMay 25, 1995) (statement of Sen. Kyl). Similarly, the lead House sponsor, Rep.\n\nLoBiondo, described mandatory exhaustion as promoting more efficient resolution of\n\nprisoner problems and ensuring “some degree of fact-finding so that when or if the matter\n\nreaches Federal court there will be a record upon which to proceed in a more efficient\n\nmanner.” 141 Cong. Rec. H14105 (daily ed. Dec. 6, 1995) (statement of Rep.\n\nLoBiondo). He further characterized mandatory exhaustion as a tool to filter frivolous\n\nclaims so “only those claims with a greater probability . . . of success would, presumably,\n\nproceed.” Id.\n\n Each of these goals entirely accords with those underlying § 1983, and neither\n\nstatute is served by allowing mandatory exhaustion to chip away at a prisoner’s\n\nlimitations period. Rather, as several of our sister circuits have recognized, refusal to toll\n\nlimitations during the PLRA’s mandatory exhaustion period would trap prisoners in a\n\n“catch-22”: one “who files suit . . . prior to exhausting administrative remedies risks\n\ndismissal based upon § 1997e [of the PLRA]; whereas the prisoner who waits to exhaust\n\nhis administrative remedies risks dismissal based upon untimeliness.” Gonzalez, 651\n\n 16\n\fF.3d at 323 (quoting Johnson v. Rivera, 272 F.3d 519, 522 (7th Cir. 2001)); accord\n\nPearson v. Sec’y Dep’t of Corr., 775 F.3d 598, 602 (3d Cir. 2015).\n\n As previously noted, the Supreme Court expressed a similar concern well before\n\nenactment of the PLRA. The Court made plain that imposing a mandatory exhaustion\n\nrequirement without tolling limitations during the exhaustion period could “result in the\n\neffective repeal of § 1983.” Patsy, 457 U.S. at 514 n.17. The text and legislative history\n\nof the PLRA offer no indication that Congress intended to effect such a repeal. Because\n\nthe PLRA does no more than require exhaustion before filing suit, we cannot read it to\n\namend § 1983’s well-established policy objectives, as incorporated into § 1988(a).\n\n\n\n IV.\n\n Because we hold that Virginia’s no-tolling rule is inconsistent with § 1983, we\n\nmust determine a proper remedy. Battle asks that we apply federal equitable tolling\n\nprinciples to account for the time lost during his 83-day mandatory exhaustion period.\n\nWe agree with Battle (and our sister circuits) that those principles apply during this\n\nperiod.\n\n Equitable tolling is “reserved for ‘those rare instances where — due to\n\ncircumstances external to the party’s own conduct — it would be unconscionable to\n\nenforce the limitation period against the party and gross injustice would result.’” Raplee\n\nv. United States, 842 F.3d 328, 333 (4th Cir. 2016) (quoting Harris v. Hutchinson, 209\n\nF.3d 325, 330 (4th Cir. 2000)). The Supreme Court has explained that “[g]enerally, a\n\nlitigant seeking equitable tolling bears the burden of establishing two elements: (1) that\n\n 17\n\fhe has been pursuing his rights diligently, and (2) that some extraordinary circumstance\n\nstood in his way.” Pace v. DiGuglielmo, 544 U.S. 408, 418 (2005); see also Holland v.\n\nFlorida, 560 U.S. 631, 653 (2010) (clarifying that “[t]he diligence required for equitable\n\ntolling purposes is reasonable diligence, not maximum feasible diligence” (internal\n\ncitation and quotation marks omitted)).\n\n Given these principles, the Supreme Court and this court have found equitable\n\ntolling inappropriate where a plaintiff unnecessarily waits to file one claim that does not\n\nrequire exhaustion while exhausting administrative remedies required for a different\n\ncause of action. See Johnson v. Ry. Exp. Agency, Inc., 421 U.S. 454, 465–66 (1975)\n\n(declining to toll limitations for § 1981 claims during exhaustion required for separate\n\nTitle VII remedy); Ott v. Md. Dep’t of Pub. Safety & Corr. Servs., 909 F.3d 655, 661 (4th\n\nCir. 2018) (declining to toll limitations for Rehabilitation Act claims where litigant\n\n“could have timely filed [those] claims without completing the administrative process as\n\nto her [Americans with Disabilities Act] claims”).\n\n In contrast, equitable tolling is appropriate in the narrower context presented here.\n\nFirst, Battle showed reasonable diligence during the 83-day exhaustion period. He\n\npromptly denied the disciplinary charge against him and then underwent two rounds of\n\nappeals, properly pursuing the process through to the “last level.” Second, during this\n\nadministrative process, an extraordinary circumstance “stood in [the] way” of filing suit.\n\nHolland, 560 U.S. at 649 (internal quotation marks omitted). Unlike the litigants in\n\nJohnson and Ott, who remained free to file their § 1981 and Rehabilitation Act claims at\n\nany point after accrual, prisoners face a complete and absolute barrier to litigation of any\n\n 18\n\f§ 1983 claim during their mandatory administrative grievance proceedings. And this\n\nbarrier is far from ordinary. We are aware of no other federal statute in which a\n\nmandatory exhaustion requirement could erode a litigant’s limitations period. 7 Under\n\nthese circumstances, such a total and unusual barrier to filing constitutes an extraordinary\n\ncircumstance.\n\n Thus, every circuit that has confronted a state no-tolling rule and reached this\n\nquestion has applied federal law to equitably toll § 1983 limitations during the PLRA\n\nexhaustion period. See Gonzalez, 651 F.3d at 322–24; Brown, 422 F.3d at 942–43;\n\nBrown v. Morgan, 209 F.3d 595, 596 (6th Cir. 2000). In addition to these three circuits\n\nthat have expressly applied federal equitable tolling, four others have impliedly done so\n\nor suggested that this would be appropriate. See Thompson v. Pitkins, 514 F. App’x 88,\n\n90 (3d Cir. 2013) (“Because exhaustion of prison administrative remedies is mandatory\n\nunder the Prison Litigation Reform Act, the statute of limitations applicable to § 1983\n\n\n 7\n For example, the limitations period for habeas petitions by those in state custody,\n28 U.S.C. § 2244(d)(1), does not begin to run until mandatory exhaustion of state\nremedies is complete, 28 U.S.C. § 2244(d)(2). And under numerous other statutes that\nrequire administrative review prior to filing suit, limitations run only after the agency’s\naction is final. See, e.g., 28 U.S.C. § 2401(b) (requiring filing of Federal Tort Claims Act\nsuit within six months of agency’s denial of claim); 42 U.S.C. § 2000e-5(f)(1) (requiring\nemployee to file Title VII suit within 90 days of dismissal of administrative proceedings);\n20 U.S.C. § 1415(i)(2)(B) (requiring litigants to file suit under Individuals with\nDisabilities Education Act within 90 days of hearing officer’s decision, or as prescribed\nby state law); 8 U.S.C. § 1252(b)(1) (requiring noncitizens to seek judicial review of\ndeportation orders within 30 days of conclusion of administrative proceedings). Notably,\nin considering a prior and identical version of § 1997e(a), the House Judiciary Committee\nexplained that the exhaustion requirement was drafted to align “with administrative\nexhaustion rules that apply in other contexts.” H.R. Rep No. 104-21, at 32 (1995).\n\n\n 19\n\factions may be tolled while a prisoner exhausts.”); Napier v. Preslicka, 314 F.3d 528,\n\n534 n.3 (11th Cir. 2002) (“We proffer, but do not hold, as that issue is not before us, that\n\nsuch a result may be mitigated by the doctrine of equitable tolling, as other circuits have\n\napplied that doctrine to the administrative exhaustion requirement for prison condition\n\nsuits . . . .”); Clifford v. Gibbs, 298 F.3d 328, 333 (5th Cir. 2002) (granting “request to\n\nequitably toll limitations” during administrative proceedings); Johnson, 272 F.3d at 521\n\n(agreeing with other circuits that “federal courts should toll state statutes of limitations\n\nwhile inmates exhaust their administrative remedies under § 1997e” while applying state\n\ntolling provision); Heck, 997 F.2d at 358 (“[A] body of state tolling law that lacks a\n\nprovision for equitable tolling is inconsistent with the provision of a complete federal\n\nremedy under section 1983 and therefore is overridden by the federal doctrine.”).\n\n Tellingly, not one of these courts has required a claimant to prove additional\n\nextraordinary circumstances beyond the exhaustion requirement or to show constant\n\ndiligence until the moment of filing, as the officers would have us do here. In fact, the\n\nSecond Circuit even acknowledged “substantial delay arising from [the plaintiff]’s\n\nfailure” to properly litigate the claim before it, but still equitably tolled the administrative\n\ngrievance period in light of § 1983’s well-established policies. Gonzalez, 651 F.3d at\n\n320, 323.\n\n Finally, in joining this consensus, we note that the ordinary arguments against\n\nequitable tolling do not apply. For example, there is no “potential for . . . endless tolling”\n\nof a prisoner’s § 1983 claim, because the clock would only stop for the length of the\n\nstate’s exhaustion period. Credit Suisse Sec. (USA) LLC v. Simmonds, 566 U.S. 221,\n\n 20\n\f227–28 (2012). If defendants are correct that Virginia’s administrative grievance process\n\nwill never exceed 180 days from the time a grievance is filed, then Virginia’s officials\n\nwill never be subject to a tolling period exceeding seven months. A maximum extension\n\nof seven months will not prejudice these officials, given that the grievance process will\n\nput them on notice of a potential civil rights claim and allow the parties to develop a\n\ncontemporaneous “administrative record that clarifies the contours of the controversy.”\n\nPorter, 534 U.S. at 525.\n\n A clear rule that tolls limitations during the grievance process also avoids any risk\n\nof “loose[ning] the rule of law to whims about the adequacy of excuses, divergent\n\nresponses to claims of hardship, and subjective notions of fair accommodation.” Harris,\n\n209 F.3d at 330. The inquiry here is objective. All a court must do is determine the point\n\nof exhaustion and run the limitations period from that date.\n\n We therefore reject the officers’ invitation to deviate from the path followed by\n\nseven other circuits. Battle’s limitations period must be tolled for the 83 days in which\n\nhe exhausted his administrative remedies, as he was required to do before bringing suit.\n\nThis satisfies the goals of § 1983 and the PLRA while also comporting with principles of\n\nequity: it gives Battle the benefit of the full limitations period applicable to other\n\nlitigants, no more and no less. In sum, Battle’s § 1983 complaint is timely; it was filed\n\nwithin two years of the date he exhausted administrative remedies required by the PLRA.\n\n\n\n\n 21\n\f V.\n\n For the foregoing reasons, we vacate the judgment of the district court and remand\n\nfor further proceedings consistent with this opinion.\n\n VACATED AND REMANDED\n\n\n\n\n 22", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356941/", "author_raw": "DIANA GRIBBON MOTZ, Circuit Judge:"}]}
MOTZ
DUNCAN
THACKER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579688/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: William D. BATTLE, III, Plaintiff - Appellant, v. J. LEDFORD, Correctional Officer; R. Edwards, Correctional Officer; Gregory Holloway, Warden of Wallens Ridge State Prison; George Hinkle, Regional Administrator for Virginia Department of Corrections, Defendants - Appellees.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-6287\n\n\nWILLIAM D. BATTLE, III,\n\n Plaintiff - Appellant,\n\n v.\n\nJ. LEDFORD, Correctional Officer; R. EDWARDS, Correctional Officer;\nGREGORY HOLLOWAY, Warden of Wallens Ridge State Prison; GEORGE\nHINKLE, Regional Administrator for Virginia Department of Corrections,\n\n Defendants - Appellees.\n\n\nAppeal from the United States District Court for the Western District of Virginia, at\nRoanoke. Elizabeth Kay Dillon, District Judge. (7:16-cv-00020-EKD-RSB)\n\n\nArgued: September 25, 2018 Decided: January 8, 2019\n\n\nBefore MOTZ, DUNCAN, and THACKER, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Motz wrote the opinion, in which\nJudge Duncan and Judge Thacker joined.\n\n\nARGUED: Sarah Crandall, Elizabeth Joynes, UNIVERSITY OF VIRGINIA SCHOOL\nOF LAW, Charlottesville, Virginia, for Appellant. Michelle Shane Kallen, OFFICE OF\nTHE ATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for Appellees. ON\nBRIEF: Joseph Charlet, Third Year Law Student, Megan Keenan, Third Year Law\nStudent, Evan Ward, Third Year Law Student, Appellate Litigation Clinic,\nUNIVERSITY OF VIRGINIA SCHOOL OF LAW, Charlottesville, Virginia, for\nAppellant. Mark R. Herring, Attorney General, Trevor S. Cox, Acting Solicitor General,\n\fLaura H. Cahill, Assistant Attorney General, Matthew R. McGuire, Deputy Solicitor\nGeneral, OFFICE OF THE ATTORNEY GENERAL OF VIRGINIA, Richmond,\nVirginia, for Appellees.\n\n\n\n\n 2\n\fDIANA GRIBBON MOTZ, Circuit Judge:\n\n The Prison Litigation Reform Act requires a prisoner to exhaust administrative\n\nremedies before filing suit. When a prisoner filed this action under 42 U.S.C. § 1983\n\nafter exhausting those remedies, the district court held the statute of limitations barred his\n\nsuit. For the reasons that follow, we vacate and remand for further proceedings\n\nconsistent with this opinion.\n\n\n\n I.\n\n William D. Battle, III, entered Wallens Ridge State Prison in Roanoke, Virginia,\n\non December 6, 2013. After Battle completed the inmate intake process, corrections\n\nofficers J. Ledford and R. Edwards (collectively, “the officers”) escorted him to his\n\nassigned housing unit. A physical altercation between Battle and the officers occurred\n\nalong the way.\n\n The officers subsequently filed a disciplinary report against Battle. They charged\n\nthat Battle, who was restrained in handcuffs and leg irons during the transfer, used his\n\nbody to push one of the officers into a food cart. According to the officers, they subdued\n\nBattle by “plac[ing]” him on the ground. Battle disputed this account before a prison\n\nhearing administrator. He denied shoving any officer and instead claimed that a pain in\n\nhis ankle caused him to trip. He stated that the officers responded with unnecessary\n\nviolence: pulling his hair and slamming his head into the concrete floor, causing\n\n“bruising, lacerations, [and] swelling of the face.” Battle requested that the hearing\n\nadministrator examine video footage of the incident to corroborate his account.\n\n 3\n\f The hearing administrator declined to do so; instead, he simply credited the\n\nofficers’ version of the incident. After unsuccessfully appealing this decision to the\n\nprison’s chief warden, Battle submitted a second appeal to the regional corrections\n\nadministrator. On February 27, 2014, the regional administrator rejected Battle’s claim\n\nand issued a form confirming that Battle had reached the “last level of appeal for this\n\ngrievance.” A total of 83 days had passed since the altercation.\n\n On January 11, 2016 — two years and 36 days after the altercation — Battle\n\ncompleted a postage request for a pro se § 1983 complaint alleging the officers used\n\nexcessive force against him, in violation of the Eighth and Fourteenth Amendments. 1\n\nThe parties accept that this postage request establishes the filing date.\n\n The officers moved for summary judgment, arguing that Battle filed outside\n\nVirginia’s two-year statute of limitations applicable to § 1983 claims filed within the\n\njurisdiction. See Va. Code Ann. § 8.01-243(A) (setting limitations for personal injury\n\nactions). Battle countered that his complaint was timely because 42 U.S.C. § 1997e(a) of\n\nthe Prison Litigation Reform Act (“PLRA”) required him to exhaust available\n\nadministrative remedies before bringing a § 1983 claim. He argued that the 83 days\n\nduring which he participated in the required exhaustion should be tolled under two\n\n\n\n\n 1\n Battle’s complaint also named corrections administrators Gregory Holloway and\nGeorge Hinkle as defendants. The district court held that Battle failed to state a claim\nagainst these two officials. Battle does not appeal their dismissal.\n\n 4\n\fVirginia statutes and federal law, thus extending his filing deadline to February 27,\n\n2016. 2\n\n The first state statute on which Battle relied, Va. Code § 8.01-229(K), suspends\n\nthe statute of limitations for personal injury actions during criminal proceedings. The\n\nsecond, Va. Code § 8.01-195.3(7), governs actions brought under the Virginia Tort\n\nClaims Act (“VTCA”) and tolls the time for filing a claim notice during the pendency of\n\na prison grievance process. Additionally, Battle relied on federal equitable tolling law.\n\n The district court considered only Battle’s argument as to Va. Code § 8.01-\n\n229(K). It held that statute could not be used to toll Battle’s limitations period because a\n\n“prison disciplinary proceeding is not a criminal prosecution.” Battle v. Ledford, No.\n\n7:16CV00020, 2017 WL 432822, at *3 n.5 (W.D. Va. Jan. 30, 2017) (citing Wolff v.\n\nMcDonnell, 418 U.S. 539, 556 (1974)). The court then granted the officers’ motion for\n\nsummary judgment, concluding that Battle filed his complaint 36 days too late.\n\n On appeal, Battle concedes that the district court properly rejected his claim under\n\nVa. Code Ann. § 8.01-229(K). He maintains, however, that the court overlooked his\n\nclaims of state statutory tolling under the VTCA and federal equitable tolling, and so\n\nerred in deeming his complaint time-barred.\n\n We review a district court’s grant of summary judgment de novo. Henry v.\n\nPurnell, 652 F.3d 524, 531 (4th Cir. 2011) (en banc). Summary judgment is appropriate\n\n 2\n Battle explained in a related affidavit that he understood from a prisoners’ rights\npamphlet that the exhaustion of administrative remedies required by the Prison Litigation\nReform Act mandated tolling, but could not easily verify the proposition because he had\nlimited access to the law library.\n\n 5\n\fonly when “there is no genuine dispute as to any material fact and the movant is entitled\n\nto judgment as a matter of law.” Fed. R. Civ. P. 56(a).\n\n\n\n II.\n\n Congress did not provide fixed timing rules in § 1983 or its companion provision,\n\n§ 1988. 3 Instead, Congress specified that gaps in § 1983 “should be filled by state law, as\n\nlong as that law is not inconsistent with federal law.” Hardin v. Straub, 490 U.S. 536,\n\n538 (1989).\n\n The Supreme Court has directed that we apply a state’s “statute of limitations\n\ngoverning general personal injury actions” when considering § 1983 claims. Owens v.\n\nOkure, 488 U.S. 235, 251 (1989). A state’s limitations and tolling rules are to be\n\nfollowed unless doing so “defeat[s] either § 1983’s chief goals of compensation and\n\ndeterrence or its subsidiary goals of uniformity and federalism.” Hardin, 490 U.S. at 539\n\n(footnote omitted). If Virginia law allows tolling of Battle’s limitations period, that ends\n\nthe inquiry. See id. at 543 (establishing that states may grant extensions to prisoners\n\n\n\n 3\n Section 1988 provides that where a § 1983 cause of action is\n\n deficient in the provisions necessary to furnish suitable remedies, . . . the\n common law, as modified and changed by the constitution and statutes of\n the State wherein the court having jurisdiction of such civil or criminal\n cause is held, so far as the same is not inconsistent with the Constitution\n and laws of the United States, shall be extended to and govern the said\n courts in the trial and disposition of the cause[.]\n\n42 U.S.C. § 1988(a) (emphasis added).\n\n 6\n\fconsistent with § 1983). If not, Battle’s claim may survive only if federal equitable\n\nprinciples apply to his case.\n\n A.\n\n Virginia lacks a generally applicable statute that pauses limitations to\n\naccommodate administrative exhaustion requirements. See Va. Code Ann. § 8.01-229\n\n(enumerating eleven unrelated exceptions suspending tolling limitations periods). 4 Battle\n\nthus asks us to borrow a tolling provision in the Virginia Tort Claims Act. He does so on\n\nthe theory that he could have brought suit under that law for the same actions against the\n\nsame parties.\n\n To bring suit under the VTCA, a person must provide a notice of claim to the state\n\n“within one year after the cause of action accrues” as a precursor to litigation. Va. Code\n\nAnn. § 8.01-195.7. The claimant must file a complaint in court “within 18 months of the\n\nfiling of the notice of claim, or within two years after the cause of action accrues.” Id. If\n\nthe claimant is a state prisoner, the VTCA provides that the “time for filing the notice of\n\n 4\n We note that Virginia does have its own statute, the Virginia Prisoner Litigation\nReform Act (“VPLRA”), which directly addresses the interaction of limitations and\nexhaustion. Va. Code Ann. § 8.01-243.2 provides:\n\n No person confined in a state or local correctional facility shall bring or\n have brought on his behalf any personal action relating to the conditions of\n his confinement until all available administrative remedies are exhausted.\n Such action shall be brought by or on behalf of such person within one year\n after cause of action accrues or within six months after all administrative\n remedies are exhausted, whichever occurs later.\n\nThis provision does not control Battle’s § 1983 action because the Supreme Court has\nunequivocally held that personal injury limitations periods apply to § 1983 claims. See\nOwens, 488 U.S. at 251; Wilson v. Garcia, 471 U.S. 261, 280 (1985).\n\n 7\n\ftort claim shall be tolled during the pendency of the grievance procedure.” Va. Code\n\nAnn. § 8.01-195.3(7).\n\n The VTCA does not save Battle’s claims for two reasons. First, the VTCA\n\noperates on a tighter schedule than § 1983. It gives a plaintiff only one year to assert his\n\nrights, plus exhaustion. The VTCA’s tolling provision would thus afford Battle one year\n\nand 83 days to take legal action.\n\n Second, and more fundamentally, the VTCA does not govern suits against state\n\nemployees like the one Battle brings here. Rather, it provides a limited waiver of\n\nsovereign immunity that “applies to one type of litigation, tort actions against the\n\nCommonwealth.” Ogunde v. Virginia, 628 S.E.2d 370, 373 (Va. 2006). But § 1983 does\n\nthe reverse: it applies only to state officials, not states themselves. See Will v. Mich.\n\nDep’t of State Police, 491 U.S. 58, 66 (1989). Because Battle could not have substituted\n\na VTCA claim for a § 1983 action, the VTCA’s tolling provision cannot be integrated\n\ninto the federal scheme.\n\n B.\n\n When state statutory tolling rules provide no relief to a prisoner seeking to bring a\n\n§ 1983 claim, some courts have turned to state equitable tolling rules to suspend\n\nlimitations during the mandated exhaustion period. See Heck v. Humphrey, 997 F.2d\n\n355, 358 (7th Cir. 1993) (applying state equitable tolling to suspend limitations period for\n\n§ 1983 plaintiff seeking to bring habeas claim), aff’d on other grounds, 512 U.S. 477\n\n(1994); Rodriguez v. Holmes, 963 F.2d 799, 804–05 (5th Cir. 1992) (same).\n\n\n\n 8\n\f Under Virginia law, equitable estoppel provides the only arguable exception to the\n\nCommonwealth’s general rule against “recogniz[ing] any non-statutory basis for tolling”\n\nlimitations. City of Bedford v. James Leffel & Co., 558 F.2d 216, 217 (4th Cir. 1977)\n\n(internal quotation marks omitted); see also Casey v. Merck & Co., 722 S.E.2d 842, 845\n\n(Va. 2012) (“A statute of limitations may not be tolled, or an exception applied, in the\n\nabsence of a clear statutory enactment to such effect.” (internal quotation marks\n\nomitted)).\n\n To invoke equitable estoppel under Virginia law, a plaintiff must prove, inter alia,\n\nthat the “party claiming estoppel was misled to his injury” by the defendant in a way that\n\nprevented timely filing. Boykins Narrow Fabrics Corp. v. Weldon Roofing & Sheet\n\nMetal, Inc., 266 S.E.2d 887, 890 (Va. 1980). The corrections officers did not mislead\n\nBattle as to his injury or the accrual date by operation of the prison administrative review\n\nprocess. Accordingly, as each party acknowledges, Battle cannot invoke the doctrine.\n\n Battle further concedes that no other Virginia common law rule could save his\n\nclaim.\n\n\n\n III.\n\n A.\n\n With no Virginia rule available to toll the limitations period, we must determine\n\nwhether refusal to do so during a prisoner’s mandatory exhaustion period is “consistent\n\nwith federal law and policy.” Owens, 488 U.S. at 239.\n\n\n\n 9\n\f When a court borrows a state rule “to assist in the enforcement of [a] federal\n\nremedy,” the federal interest always controls. Wilson, 471 U.S. at 269. This is so\n\nbecause “the policies and purposes of the States” do not constitute “the primary office of\n\nthe borrowing provision in § 1988,” which governs § 1983 actions. Id. Rather, § 1988\n\n“is designed to assure that neutral rules of decision will be available to enforce the civil\n\nrights actions, among them § 1983.” Id. Thus, it is the “duty of the federal courts to\n\nassure that the importation of state law will not frustrate or interfere with the\n\nimplementation of national policies.” Occidental Life Ins. Co. of Cal. v. EEOC, 432 U.S.\n\n355, 367 (1977).\n\n But to be held “inconsistent” with § 1983, a state rule must do more than “cause[]\n\nthe plaintiff to lose the litigation.” Robertson v. Wegmann, 436 U.S. 584, 593 (1978).\n\nThe state rule must “defeat either § 1983’s chief goals of compensation and deterrence or\n\nits subsidiary goals of uniformity and federalism.” Hardin, 490 U.S. at 539 (footnote\n\nomitted). If a state’s timing requirement contravenes one or more of these goals, it is\n\n“inconsistent with federal law,” and § 1988 bars us from adopting it. Id. at 538.\n\n The Supreme Court has explained that it is inconsistent with § 1983’s policies to\n\napply “a state statute of limitations” to require a litigant “to refrain from commencing a\n\ncivil action until it has discharged” a process mandated by federal law. Occidental, 432\n\nU.S. at 367–68. “For the State’s wisdom in establishing a general limitation period could\n\nnot have taken into account the decision of Congress to delay judicial action” while the\n\nlitigant “performs its administrative responsibilities.” Id. (internal quotation marks\n\nomitted). The Court has further suggested that tolling of § 1983 limitations may be\n\n 10\n\fnecessary where a remedy “is structured to require previous resort to state proceedings,\n\nso that the claim may not even be maintained in federal court unless such resort be had.”\n\nBd. of Regents of Univ. of State of N.Y. v. Tomanio, 446 U.S. 478, 490 (1980). The Court\n\nhas even warned that the imposition of an “exhaustion requirement might result in the\n\neffective repeal of § 1983” if “statutes of limitations are not tolled pending exhaustion.”\n\nPatsy v. Bd. of Regents of State of Fla., 457 U.S. 496, 514 n.17 (1982).\n\n B.\n\n With this precedent in mind, we consider its application to the case at hand.\n\n Virginia law provides an elaborate administrative grievance process for prisoner\n\ncomplaints. Exhaustion of this remedy involves at least three levels of review. See\n\nVDOC OP 866.1(IV-VI) (describing emergency grievance review, review of informal\n\ncomplaints, and three-stage review of formal complaints). A prisoner has 30 days to\n\nsubmit a formal grievance, and corrections administrators are then given another 180\n\ndays to resolve the grievance. 5 See id.\n\n Given this structure, Virginia’s no-tolling rule, as applied to prisoners seeking to\n\nbring § 1983 claims, frustrates the goals of § 1983 and is thus clearly “inconsistent” with\n\nsettled federal policy. Hardin, 490 U.S. at 538.\n\n\n\n\n 5\n Virginia’s corrections regulations exempt sexual abuse allegations from the 30-\nday filing requirement so that vulnerable victims may press their claims once it is safe for\nthem to do so. VDOC OP 866.1(VI)(A)(1)(c). Absent tolling, this policy could have the\nunintended effect of substantially reducing a prisoner’s § 1983 filing time when bringing\na serious abuse claim against a corrections officer.\n\n 11\n\f First, application of the no-tolling rule would frustrate the purpose of\n\ncompensating prisoners who have sustained constitutional injuries. Under Virginia\n\nregulations — as implemented by state officials — as much as seven months could be\n\nsubtracted from the period in which a prisoner can file a federal claim. This inevitable\n\nand indeterminate reduction in limitations would be wholly contingent on the efficiency\n\nof administrators and the complexity of the case. And as other circuits have noted and\n\ncommon sense suggests, a state’s grievance process may extend beyond the state’s\n\nregulatory deadlines. See, e.g., Brown v. Valoff, 422 F.3d 926, 932–34 (9th Cir. 2005)\n\n(describing grievance process lasting 2 years and 10 months from injury to investigation\n\nreport); see also Gonzalez v. Hasty, 651 F.3d 318, 323 (2d Cir. 2011) (“[T]he time for\n\nachieving a resolution under the PLRA could be considerably longer than 140 days. . . .\n\n[I]t is certainly possible that a full three years could pass while an inmate exhausts his\n\nadministrative remedies.”). Far from advancing compensation, a no-tolling rule would\n\namount to a penalty in which incarcerated persons — subject to severe state control and\n\noften limited in access to legal resources — would receive less time to vindicate § 1983\n\nclaims than all other litigants.\n\n Application of a no-tolling rule here would also fail to serve § 1983’s second\n\nprimary goal — deterrence. Instead, this rule would enable state officials to shrink a\n\nprisoner’s filing window and so limit his opportunity to bring a claim. In this way, a no-\n\ntolling rule would even create perverse incentives for prison commissioners to extend\n\nregulatory deadlines and for wardens and investigators to stall in their review of\n\n\n\n 12\n\findividual grievances, for doing so might limit government officials’ legal exposure. 6 As\n\nthe Seventh Circuit has observed, no-tolling rules thus encourage prison officials to run\n\nout the clock and “exploit the exhaustion requirement through indefinite delay in\n\nresponding to grievances.” Lewis v. Washington, 300 F.3d 829, 833 (7th Cir. 2002)\n\n(internal quotation marks omitted).\n\n Nor would the no-tolling rule advance § 1983’s subsidiary interest in uniformity.\n\nOf course, Virginia’s rule would set a consistent two-year period between accrual and the\n\nlimitations deadline across claims, furthering uniformity in this formalistic respect. But a\n\nrule that calculates the limitations deadline from the date of exhaustion is just as “firmly\n\ndefined” and “easily applied.” Wilson, 471 U.S. at 270 (quoting Chardon v. Fumero\n\nSoto, 462 U.S. 650, 667 (1983) (Rehnquist, J., dissenting)). Moreover, a no-tolling rule\n\nwould destroy any semblance of meaningful uniformity by creating dramatic claim-to-\n\nclaim variance in the actual filing time available to different § 1983 litigants. Between\n\nprisoners, a no-tolling rule would afford a prisoner whose grievance was processed with\n\ndelay less time to file than one whose grievance received speedy resolution. It would\n\nalso create a disparity between those who are incarcerated and those who are not. For\n\nexample, if the injuries claimed here had occurred in the context of an arrest rather than a\n\nprison escort, Battle would have been guaranteed a full two years to file his § 1983 suit,\n\nrather than the abbreviated period he would receive under a no-tolling rule. Such\n\n\n\n 6\n We do not discern or suggest any bad faith or intentional delay by prison\nofficials in Battle’s case. Our point is only that this is possible absent tolling.\n\n 13\n\fsweeping and arbitrary deviations in procedural rights would hardly advance a policy of\n\nuniformity.\n\n Finally, we also cannot even say that accepting Virginia’s no-tolling rule would\n\nfoster federalism interests. This is so because the Commonwealth itself has adopted two\n\nstatutes, the VTCA and VPLRA, that toll prisoner exhaustion periods. See Va. Code\n\nAnn. §§ 8.01-195.7, 8.01-243.2. Although neither provides relief to prisoners seeking to\n\nbring § 1983 claims, their enactment demonstrates that Virginia otherwise has adopted a\n\npolicy of tolling limitations while prison administrators review inmate claims. These\n\nstatutes also make clear that an exhaustion reprieve does not conflict with Virginia’s\n\n“important and salutary purpose” in strictly construing statutes of limitations, which is to\n\nprotect defendants from “unscrupulous plaintiffs who hoard evidence that supports their\n\nposition while waiting for their prospective opponents to discard evidence that would\n\nhelp make a defense.” Burns v. Stafford Cty., 315 S.E.2d 856, 859 (Va. 1984).\n\nAdministrative exhaustion does the opposite: it notifies defendants of a potential claim\n\nand allows both parties to develop a record before coming to court.\n\n In sum, because Virginia’s no-tolling rule is inconsistent with federal law and\n\npolicy, we cannot apply it here.\n\n C.\n\n Notwithstanding this analysis, the officers contend that Virginia’s no-tolling rule\n\nnecessarily comports with federal policies because a separate federal law — the PLRA —\n\nimposes the relevant exhaustion requirement. But by enacting the PLRA, Congress did\n\nnot endorse such a no-tolling rule or diminish the interests underlying § 1983. To so\n\n 14\n\fconclude would be to overread the PLRA’s silence on tolling, misread the PLRA’s\n\npurpose, and ignore the text of § 1983 and § 1988.\n\n First, the silence in the PLRA. It is a cardinal rule that “repeals by implication are\n\nnot favored and will not be presumed unless the intention of the legislature to repeal is\n\nclear and manifest.” Hui v. Castaneda, 559 U.S. 799, 810 (2010) (internal quotation\n\nmarks omitted). Nothing in the text of the PLRA suggests that Congress sought to limit\n\nor modify § 1988(a)’s express command that borrowed provisions of state law must be\n\nconsistent with important, long-recognized federal policies. The PLRA’s legislative\n\nhistory is also silent as to § 1988(a)’s borrowing framework and the Court’s\n\ninterpretation thereof. The conference reports, floor debates, and committee hearings\n\ncontain no discussion of the pressure that mandatory exhaustion would exert on § 1983’s\n\nstate-derived limitations rule absent tolling. See generally Bernard D. Reams & William\n\nH. Manz, A Legislative History of the Prison Litigation Reform Act of 1996, Pub. L. No.\n\n104–134, 110 Stat. 1321 (1997). When confronted with statutory silence, we must\n\n“presume that Congress is aware of the legal context in which it is legislating.” Palisades\n\nCollections LLC v. Shorts, 552 F.3d 327, 335 n.4 (4th Cir. 2008) (internal quotation\n\nmarks omitted).\n\n Nor do we see any indication that Congress intended, through the PLRA, to amend\n\nor override the specific federal policies underlying § 1983 and incorporated into\n\n§ 1988(a). Instead, as the Supreme Court has explained, it is “[b]eyond doubt” that\n\nCongress enacted the PLRA’s exhaustion requirement “to reduce the quantity and\n\nimprove the quality of prisoner suits” by allowing officials the opportunity to take\n\n 15\n\f“corrective action” and ideally “obviating the need for litigation.” Porter v. Nussle, 534\n\nU.S. 516, 524–25 (2002); see also McLean v. United States, 566 F.3d 391, 397 (4th Cir.\n\n2009) (“The purpose of the PLRA was not, however, to impose indiscriminate\n\nrestrictions on prisoners’ access to the federal courts.”).\n\n Senator Kyl, the lead Senate sponsor of the PLRA, explained that an exhaustion\n\nrequirement would “free up judicial resources for claims with merit by both prisoners and\n\nnonprisoners” alike by winnowing meritless claims. 141 Cong. Rec. S7526 (daily ed.\n\nMay 25, 1995) (statement of Sen. Kyl). Similarly, the lead House sponsor, Rep.\n\nLoBiondo, described mandatory exhaustion as promoting more efficient resolution of\n\nprisoner problems and ensuring “some degree of fact-finding so that when or if the matter\n\nreaches Federal court there will be a record upon which to proceed in a more efficient\n\nmanner.” 141 Cong. Rec. H14105 (daily ed. Dec. 6, 1995) (statement of Rep.\n\nLoBiondo). He further characterized mandatory exhaustion as a tool to filter frivolous\n\nclaims so “only those claims with a greater probability . . . of success would, presumably,\n\nproceed.” Id.\n\n Each of these goals entirely accords with those underlying § 1983, and neither\n\nstatute is served by allowing mandatory exhaustion to chip away at a prisoner’s\n\nlimitations period. Rather, as several of our sister circuits have recognized, refusal to toll\n\nlimitations during the PLRA’s mandatory exhaustion period would trap prisoners in a\n\n“catch-22”: one “who files suit . . . prior to exhausting administrative remedies risks\n\ndismissal based upon § 1997e [of the PLRA]; whereas the prisoner who waits to exhaust\n\nhis administrative remedies risks dismissal based upon untimeliness.” Gonzalez, 651\n\n 16\n\fF.3d at 323 (quoting Johnson v. Rivera, 272 F.3d 519, 522 (7th Cir. 2001)); accord\n\nPearson v. Sec’y Dep’t of Corr., 775 F.3d 598, 602 (3d Cir. 2015).\n\n As previously noted, the Supreme Court expressed a similar concern well before\n\nenactment of the PLRA. The Court made plain that imposing a mandatory exhaustion\n\nrequirement without tolling limitations during the exhaustion period could “result in the\n\neffective repeal of § 1983.” Patsy, 457 U.S. at 514 n.17. The text and legislative history\n\nof the PLRA offer no indication that Congress intended to effect such a repeal. Because\n\nthe PLRA does no more than require exhaustion before filing suit, we cannot read it to\n\namend § 1983’s well-established policy objectives, as incorporated into § 1988(a).\n\n\n\n IV.\n\n Because we hold that Virginia’s no-tolling rule is inconsistent with § 1983, we\n\nmust determine a proper remedy. Battle asks that we apply federal equitable tolling\n\nprinciples to account for the time lost during his 83-day mandatory exhaustion period.\n\nWe agree with Battle (and our sister circuits) that those principles apply during this\n\nperiod.\n\n Equitable tolling is “reserved for ‘those rare instances where — due to\n\ncircumstances external to the party’s own conduct — it would be unconscionable to\n\nenforce the limitation period against the party and gross injustice would result.’” Raplee\n\nv. United States, 842 F.3d 328, 333 (4th Cir. 2016) (quoting Harris v. Hutchinson, 209\n\nF.3d 325, 330 (4th Cir. 2000)). The Supreme Court has explained that “[g]enerally, a\n\nlitigant seeking equitable tolling bears the burden of establishing two elements: (1) that\n\n 17\n\fhe has been pursuing his rights diligently, and (2) that some extraordinary circumstance\n\nstood in his way.” Pace v. DiGuglielmo, 544 U.S. 408, 418 (2005); see also Holland v.\n\nFlorida, 560 U.S. 631, 653 (2010) (clarifying that “[t]he diligence required for equitable\n\ntolling purposes is reasonable diligence, not maximum feasible diligence” (internal\n\ncitation and quotation marks omitted)).\n\n Given these principles, the Supreme Court and this court have found equitable\n\ntolling inappropriate where a plaintiff unnecessarily waits to file one claim that does not\n\nrequire exhaustion while exhausting administrative remedies required for a different\n\ncause of action. See Johnson v. Ry. Exp. Agency, Inc., 421 U.S. 454, 465–66 (1975)\n\n(declining to toll limitations for § 1981 claims during exhaustion required for separate\n\nTitle VII remedy); Ott v. Md. Dep’t of Pub. Safety & Corr. Servs., 909 F.3d 655, 661 (4th\n\nCir. 2018) (declining to toll limitations for Rehabilitation Act claims where litigant\n\n“could have timely filed [those] claims without completing the administrative process as\n\nto her [Americans with Disabilities Act] claims”).\n\n In contrast, equitable tolling is appropriate in the narrower context presented here.\n\nFirst, Battle showed reasonable diligence during the 83-day exhaustion period. He\n\npromptly denied the disciplinary charge against him and then underwent two rounds of\n\nappeals, properly pursuing the process through to the “last level.” Second, during this\n\nadministrative process, an extraordinary circumstance “stood in [the] way” of filing suit.\n\nHolland, 560 U.S. at 649 (internal quotation marks omitted). Unlike the litigants in\n\nJohnson and Ott, who remained free to file their § 1981 and Rehabilitation Act claims at\n\nany point after accrual, prisoners face a complete and absolute barrier to litigation of any\n\n 18\n\f§ 1983 claim during their mandatory administrative grievance proceedings. And this\n\nbarrier is far from ordinary. We are aware of no other federal statute in which a\n\nmandatory exhaustion requirement could erode a litigant’s limitations period. 7 Under\n\nthese circumstances, such a total and unusual barrier to filing constitutes an extraordinary\n\ncircumstance.\n\n Thus, every circuit that has confronted a state no-tolling rule and reached this\n\nquestion has applied federal law to equitably toll § 1983 limitations during the PLRA\n\nexhaustion period. See Gonzalez, 651 F.3d at 322–24; Brown, 422 F.3d at 942–43;\n\nBrown v. Morgan, 209 F.3d 595, 596 (6th Cir. 2000). In addition to these three circuits\n\nthat have expressly applied federal equitable tolling, four others have impliedly done so\n\nor suggested that this would be appropriate. See Thompson v. Pitkins, 514 F. App’x 88,\n\n90 (3d Cir. 2013) (“Because exhaustion of prison administrative remedies is mandatory\n\nunder the Prison Litigation Reform Act, the statute of limitations applicable to § 1983\n\n\n 7\n For example, the limitations period for habeas petitions by those in state custody,\n28 U.S.C. § 2244(d)(1), does not begin to run until mandatory exhaustion of state\nremedies is complete, 28 U.S.C. § 2244(d)(2). And under numerous other statutes that\nrequire administrative review prior to filing suit, limitations run only after the agency’s\naction is final. See, e.g., 28 U.S.C. § 2401(b) (requiring filing of Federal Tort Claims Act\nsuit within six months of agency’s denial of claim); 42 U.S.C. § 2000e-5(f)(1) (requiring\nemployee to file Title VII suit within 90 days of dismissal of administrative proceedings);\n20 U.S.C. § 1415(i)(2)(B) (requiring litigants to file suit under Individuals with\nDisabilities Education Act within 90 days of hearing officer’s decision, or as prescribed\nby state law); 8 U.S.C. § 1252(b)(1) (requiring noncitizens to seek judicial review of\ndeportation orders within 30 days of conclusion of administrative proceedings). Notably,\nin considering a prior and identical version of § 1997e(a), the House Judiciary Committee\nexplained that the exhaustion requirement was drafted to align “with administrative\nexhaustion rules that apply in other contexts.” H.R. Rep No. 104-21, at 32 (1995).\n\n\n 19\n\factions may be tolled while a prisoner exhausts.”); Napier v. Preslicka, 314 F.3d 528,\n\n534 n.3 (11th Cir. 2002) (“We proffer, but do not hold, as that issue is not before us, that\n\nsuch a result may be mitigated by the doctrine of equitable tolling, as other circuits have\n\napplied that doctrine to the administrative exhaustion requirement for prison condition\n\nsuits . . . .”); Clifford v. Gibbs, 298 F.3d 328, 333 (5th Cir. 2002) (granting “request to\n\nequitably toll limitations” during administrative proceedings); Johnson, 272 F.3d at 521\n\n(agreeing with other circuits that “federal courts should toll state statutes of limitations\n\nwhile inmates exhaust their administrative remedies under § 1997e” while applying state\n\ntolling provision); Heck, 997 F.2d at 358 (“[A] body of state tolling law that lacks a\n\nprovision for equitable tolling is inconsistent with the provision of a complete federal\n\nremedy under section 1983 and therefore is overridden by the federal doctrine.”).\n\n Tellingly, not one of these courts has required a claimant to prove additional\n\nextraordinary circumstances beyond the exhaustion requirement or to show constant\n\ndiligence until the moment of filing, as the officers would have us do here. In fact, the\n\nSecond Circuit even acknowledged “substantial delay arising from [the plaintiff]’s\n\nfailure” to properly litigate the claim before it, but still equitably tolled the administrative\n\ngrievance period in light of § 1983’s well-established policies. Gonzalez, 651 F.3d at\n\n320, 323.\n\n Finally, in joining this consensus, we note that the ordinary arguments against\n\nequitable tolling do not apply. For example, there is no “potential for . . . endless tolling”\n\nof a prisoner’s § 1983 claim, because the clock would only stop for the length of the\n\nstate’s exhaustion period. Credit Suisse Sec. (USA) LLC v. Simmonds, 566 U.S. 221,\n\n 20\n\f227–28 (2012). If defendants are correct that Virginia’s administrative grievance process\n\nwill never exceed 180 days from the time a grievance is filed, then Virginia’s officials\n\nwill never be subject to a tolling period exceeding seven months. A maximum extension\n\nof seven months will not prejudice these officials, given that the grievance process will\n\nput them on notice of a potential civil rights claim and allow the parties to develop a\n\ncontemporaneous “administrative record that clarifies the contours of the controversy.”\n\nPorter, 534 U.S. at 525.\n\n A clear rule that tolls limitations during the grievance process also avoids any risk\n\nof “loose[ning] the rule of law to whims about the adequacy of excuses, divergent\n\nresponses to claims of hardship, and subjective notions of fair accommodation.” Harris,\n\n209 F.3d at 330. The inquiry here is objective. All a court must do is determine the point\n\nof exhaustion and run the limitations period from that date.\n\n We therefore reject the officers’ invitation to deviate from the path followed by\n\nseven other circuits. Battle’s limitations period must be tolled for the 83 days in which\n\nhe exhausted his administrative remedies, as he was required to do before bringing suit.\n\nThis satisfies the goals of § 1983 and the PLRA while also comporting with principles of\n\nequity: it gives Battle the benefit of the full limitations period applicable to other\n\nlitigants, no more and no less. In sum, Battle’s § 1983 complaint is timely; it was filed\n\nwithin two years of the date he exhausted administrative remedies required by the PLRA.\n\n\n\n\n 21\n\f V.\n\n For the foregoing reasons, we vacate the judgment of the district court and remand\n\nfor further proceedings consistent with this opinion.\n\n VACATED AND REMANDED\n\n\n\n\n 22\n[END_CASE]", "role": "user" } ]
4,579,689
UNITED STATES of America, Plaintiff - Appellee, v. Michael SLAGER, Defendant - Appellant.
United States v. Michael Slager
2019-01-08
18-4036
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Wilkinson, Wynn, Diaz", "parties": "", "opinions": [{"author": "WYNN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-4036\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff – Appellee,\n\nv.\n\nMICHAEL SLAGER,\n\n Defendant – Appellant.\n\n\n\nAppeal from the United States District Court for the District of South Carolina, at\nCharleston. David C. Norton, District Judge. (2:16-cr-00378-DCN-1)\n\n\nArgued: November 1, 2018 Decided: January 8, 2019\n\n\nBefore WILKINSON, WYNN, and DIAZ, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Wilkinson\nand Judge Diaz joined.\n\n\nARGUED: Elizabeth Anne Franklin-Best, BLUME, FRANKLIN-BEST & YOUNG,\nLLC, Columbia, South Carolina, for Appellant. Elizabeth Parr Hecker, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Appellee. ON BRIEF: John M.\nGore, Acting Assistant Attorney General, Tovah R. Calderon, Appellate Section, Civil\nRights Division, UNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C., for\nAppellee.\n\fWYNN, Circuit Judge:\n\n Defendant Michael Slager (“Defendant”), a former officer with the North\n\nCharleston Police Department, admitted that he “willfully” shot and killed Walter Scott\n\n(“Scott”), when Scott was unarmed and fleeing arrest. Defendant further admitted that his\n\ndecision to shoot Scott was “objectively unreasonable.” Based on those admissions,\n\nDefendant pleaded guilty to depriving Scott of his civil rights under color of law.\n\n The district court sentenced Defendant to a 240-month term of imprisonment.\n\nBefore this Court, Defendant argues that the district court reversibly erred in setting his\n\nsentence by: (1) using second-degree murder as the sentencing cross-reference for his\n\noffense rather than voluntary manslaughter, and (2) applying a two-level enhancement for\n\nobstruction of justice. Finding no reversible error, we affirm Defendant’s sentence.\n\n I.\n\n A.\n\n In May 2016, a federal grand jury in the District of South Carolina returned an\n\nindictment alleging, among other things, that Defendant, “while acting under color of law\n\nas an officer with the North Charleston Police Department, shot [and killed] Walter Scott\n\nwithout legal justification, willfully depriving him of the right . . . to be free from the use\n\nof unreasonable force by a law enforcement officer.” J.A. 13. In the meantime, Defendant\n\nwas tried in state court on one count of murder. That trial resulted in a hung jury and\n\nmistrial.\n\n Thereafter, Defendant entered into a global plea agreement with the United States\n\nand the State of South Carolina. Under that agreement, in exchange for Defendant’s guilty\n\n\n 2\n\fplea in federal court to one count of depriving Scott of his civil rights under color of law,\n\nthe United States agreed to drop the remaining counts of the indictment 1 and agreed to\n\nrecommend a three-level reduction in the applicable sentencing level for acceptance of\n\nresponsibility. Additionally, South Carolina agreed not to retry Defendant and dismissed\n\nthe murder charge against him.\n\n Some of the undisputed facts that formed the basis for Defendant’s plea includes\n\nevidence showing that on the morning of April 4, 2015, while on duty, Defendant stopped\n\nScott’s vehicle after observing that his center brake light was not working. After the stop,\n\nScott fled on foot and Defendant chased him. During the chase, Defendant shot his taser\n\nprobes twice, hitting and bringing Scott down with the second shot. See United States v.\n\nSlager, No. 2:16-CR-00378-DCN, 2018 WL 445497, at *2 (D.S.C. Jan. 16, 2018).\n\n At some point thereafter, Scott got up and fled. While Scott was unarmed and\n\nrunning away, Defendant drew his department-issued firearm and fired eight shots at Scott,\n\nfive of which struck Scott in the back. Scott died on the scene from these wounds. Id.\n\n A bystander witnessed and testified about the incident. The bystander also filmed\n\nparts of the incident. The bystander’s testimony and video of the incident directly\n\ncontradicted Defendant’s initial account of the incident. In conformance with the global\n\nguilty plea agreement, Defendant admitted that he “used deadly force even though it was\n\nobjectively unreasonable under the circumstances.” Id. And, Defendant acknowledged\n\n\n 1\n The federal indictment charged Defendant with: depriving Scott of his civil rights\nunder color of law, in violation of 18 U.S.C. § 242; using a weapon during the commission\nof a crime of violence, in violation of 18 U.S.C. § 924(c); and obstruction of justice, in\nviolation of 18 U.S.C. § 1512(b)(3).\n\n 3\n\fthat “his actions were done willfully, that is he acted voluntarily and intentionally and with\n\nspecific intent to do something that the law forbids.” Id.\n\n B.\n\n Defendant’s sentencing hearing began on December 4, 2017, and lasted four days.\n\nBecause Defendant pleaded guilty to depriving Scott of his civil rights under color of law,\n\nthe district court was required during sentencing to cross-reference the offense underlying\n\nthe deprivation. See U.S.S.G. § 2H1.1(a)(1). The government contended that the proper\n\ncross-reference was second-degree murder because Defendant was acting with malice\n\naforethought when he shot Scott. In contrast, Defendant argued that the proper cross-\n\nreference was voluntary manslaughter because he was provoked by Scott and was thus not\n\nacting with malice.\n\n Although most of the facts were undisputed at Defendant’s sentencing hearing, the\n\ngovernment and Defendant disagreed as to what occurred after Scott fell to the ground, but\n\nbefore Scott got up and ran away from Defendant.\n\n i.\n\n The government’s version of events is based primarily on the only third-party\n\neyewitness to the shooting, Feidin Santana. Santana recounted the shooting during a South\n\nCarolina Law Enforcement Division (“SLED”) interview, and during Defendant’s state\n\nand federal proceedings. Each time, Santana provided a consistent account of the shooting.\n\n While traveling to work on the morning of the shooting, Santana saw Scott running\n\nfrom Defendant. Santana followed, but briefly lost sight of Scott and Defendant. When\n\nSantana next saw them, Scott was facing down, and Defendant was on top of Scott and\n\n\n 4\n\f“trying to control” him. J.A. 971. Santana testified that it sounded like Scott was “being\n\nhurt” and he heard something “electric.” J.A. 972. According to Santana, Defendant\n\npunched Scott in the back, but Scott never flipped over. Santana did not see Scott punch\n\nback. Nor did Santana see Scott grab the taser and charge toward Defendant. Indeed,\n\nSantana never saw Scott holding the taser. Rather, according to Santana, Scott did not\n\nseem to want to “hurt” Defendant but was “just trying to leave.” J.A. 974. At some point,\n\nScott shot up “aggressively,” Santana testified. J.A. 975. By this, Santana meant that Scott\n\nwas “determined to . . . just leave.” Id. When Scott broke free and began to run, Defendant\n\nshot him. Defendant then handcuffed Scott and checked his pulse but did not treat him.\n\n Santana also recorded a portion of the encounter with his cell phone. Santana’s\n\nvideo does not clearly show the period during which Scott and Defendant were allegedly\n\non the ground. But the video does show that Scott stood up and was running away—not\n\npointing a taser at Defendant or advancing toward Defendant—when Defendant fired at\n\nhim. Additionally, the video shows Defendant picked up the taser approximately ten feet\n\nbehind the point where Defendant was standing when he shot Scott—not between Scott\n\nand Defendant.\n\n ii.\n\n In contrast to Santana’s consistent recollection of the encounter, Defendant provided\n\nfour different accounts as to what happened on the morning of April 4, 2015.\n\n First, Defendant made an on-scene statement to his superior officer, Lieutenant\n\nDaniel Bowman, who arrived shortly after the shooting occurred. Defendant told Lt.\n\nBowman that Scott continued to resist arrest after being tasered and falling to the ground.\n\n\n 5\n\fDefendant tased Scott twice more while he laid on the ground, but Scott resisted and “was\n\nable to roll over onto his back.” Supp. J.A. 75. Scott then “use[d] both hands to grab the\n\ntaser” and after “a short struggle,” Scott “was able to wrestle it away.” Id. Scott then\n\n“stood up and pointed the taser at” Defendant. Id. Defendant told Lt. Bowman that, when\n\nfaced with this alleged threat, he “drew his weapon as he was returning to the standing\n\nposition and fired multiple times.” Id. Several of Defendant’s shots struck Scott, who then\n\nfell to the ground. According to this account, Defendant then “rendered emergency aid\n\nuntil other officers arrived seconds later.” Id.\n\n Three days after the shooting, on April 7, 2015, Defendant gave a second account\n\nof the encounter in an unsworn interview with SLED investigators. Before giving this\n\nstatement, Defendant asked his attorney to verify with the SLED investigators whether\n\nthere was “[a]ny video, surveillance video of businesses, security cameras, [or] anything”\n\nelse documenting the shooting. J.A. 702. Defendant also asked whether there were any\n\nwitnesses who viewed the shooting. The SLED investigators did not apprise Defendant of\n\nSantana or his recorded video.\n\n At the start of the interview, the SLED investigators informed Defendant that the\n\ninterview was part of a criminal investigation and that Defendant could decline to\n\nparticipate. Still, Defendant agreed to make a statement. Over the course of the interview,\n\nDefendant added new details not mentioned in his prior statement to Lt. Bowman and\n\nphysically reenacted key aspects of the encounter. For example, Defendant claimed that\n\nScott was “coming straight at him” holding the taser, with his “arm extending straight out.”\n\nJ.A. 1640. Defendant told the SLED investigators that he was “shuffle-stepping” to avoid\n\n\n 6\n\fthe taser as he “pulled his gun.” Id. According to this account, Scott was “turning to his\n\nleft” when Defendant fired. Id. Then, “Scott ran off, stumbled into the grass, [and] fell to\n\nthe ground.” Id. Defendant further told the investigators that “Scott must have dropped”\n\nthe taser during this altercation, because he retrieved it “between the place where he had\n\nbeen shooting and where Scott landed.” J.A. 1641.\n\n During his state trial, Defendant provided a third description of his encounter with\n\nScott. In this retelling, Defendant claimed that, during the alleged ground struggle, he had\n\nattempted to put Scott’s left hand “behind his back to handcuff him.” J.A. 282. However,\n\nScott was in a “pushup position” and was “trying to get up” at the same time. Id. Defendant\n\ntestified that while this was occurring, he and Scott were “fighting” and “rolling around on\n\nthe ground.” J.A. 285. According to this account, Scott eventually “overpowered”\n\nDefendant and took his taser. J.A. 286. Defendant testified that at that point, he “instructed\n\nMr. Scott to turn right away and go, but he didn’t.” J.A. 288. Instead, Scott continued to\n\napproach Defendant, so Defendant “pulled [his] firearm” and “fired until the threat was\n\nstopped.” J.A. 289. Defendant’s testimony made clear that he was neither “provoked” nor\n\n“angry” during the shooting. J.A. 346–47. Instead, Defendant testified that he was simply\n\n“doing [his] job” and acting in “self-defense.” Id. at 347.\n\n Defendant provided his fourth description of the shooting over two days of\n\ntestimony at his federal pre-trial hearings. Again, Defendant added new details. For the\n\nfirst time, Defendant testified that Scott “punched [him] in the chest” during the ground\n\naltercation. J.A. 732. And for the first time, Defendant testified that Scott was “on top of\n\n[him] at some point.” J.A. 727. Defendant also testified—again, for the first time—that\n\n\n 7\n\fScott “drive stunned” 2 him during the altercation. J.A. 728. When asked why he had not\n\npreviously provided these details, Defendant testified that the surrounding events were\n\n“fuzzy” and there were still “some things [he did not] recall.” J.A. 727. But “some of [his]\n\nmemory [had] come back since” the shooting, he testified. Id. Still, Defendant testified\n\nthat he could not “recall anything [that he had] told SLED Agents” during his prior\n\ninterview. J.A. 860 (emphasis added).\n\n Defendant did not testify during his sentencing hearing, but he did attempt to\n\nbuttress aspects of his final account of the encounter through three expert witnesses. First,\n\nDefendant offered Eugene Liscio, an expert forensic analyst who reconstructs crime\n\nscenes. Using Santana’s video, Liscio created a 3D model of the scene of the encounter in\n\nan effort to determine whether Defendant or Scott was holding the taser prior to the\n\nshooting. Based upon the final position of the taser, Liscio opined that the video was\n\n“inconsistent” with Defendant throwing the taser with his right arm. J.A. 1257–58.\n\nHowever, Liscio equivocated as to this opinion, acknowledging that there was “no part in\n\n[the Santana video] where you can actually see the taser being held.” J.A. 1275. Liscio\n\nalso testified that, due to this limitation, the court would have to “make [its] own judgment\n\ncall” as to what in fact occurred. J.A. 1279–80.\n\n\n\n 2\n “Tasers generally have two modes. In dart mode, a taser shoots probes into a\nsubject and overrides the central nervous system. Drive stun mode, on the other hand, does\nnot cause an override of the victim’s central nervous system; that mode is used as a pain\ncompliance tool with limited threat reduction.” Estate of Armstrong ex rel. Armstrong v.\nVill. of Pinehurst, 810 F.3d 892, 897 n.3 (4th Cir.), cert. denied sub nom. Vill. of Pinehurst,\nN.C. v. Estate of Armstrong, 137 S. Ct. 61, 196 L. Ed. 2d 32 (2016) (internal quotations\nmarks and citations omitted).\n\n 8\n\f Second, Defendant offered David Hallimore, a forensic audio analyst, who applied\n\n“filtration[s] to [the Santana Video] to allow the speech to become more clear.” J.A. 1192,\n\n1216. Through these filtrations and “critical listening”—a skill Hallimore purportedly\n\nlearned by “train[ing his] brain effectively to better understand certain tones”—Hallimore\n\ntestified that he heard “fuck police” and “Let go of the taser or I’ll shoot” on the Santana\n\nvideo. J.A. 1204, 1216, 1218. But Hallimore also recognized this was his “interpretation”\n\nof the enhanced audio. J.A. 1220.\n\n Finally, Defendant introduced opinions and analyses rendered by Megan Fletcher,\n\nan agent with the SLED’s Trace Evidence Unit. Fletcher did not testify at the federal\n\nsentencing, but Defendant did reference her state trial testimony and report. Fletcher\n\nidentified polyester fibers in Defendant’s shirt that had been melted. Fletcher analyzed\n\nthese fibers and opined that a “taser drive-stun cannot be excluded as a possible heat source\n\nwhich has the potential to melt polyester fibers.” Supp. J.A. 89–90. But Fletcher averred\n\nthat she was “unable to definitively conclude whether a Taser did or did not cause the marks\n\non the uniform.” Supp. J.A. 89. Fletcher also acknowledged that she never determined—\n\nand therefore did not know—the melting point of the fibers in Defendant’s shirt.\n\n C.\n\n On January 16, 2018, the district court sentenced Defendant to a 240-month term of\n\nimprisonment. In an accompanying order explaining its sentencing decision, the court first\n\ndetermined that second-degree murder was the appropriate sentencing cross-reference for\n\nDefendant’s offense because “malice aforethought is proven by a gross deviation from the\n\nstandard of reasonable care, and [because] there is insufficient evidence that the defendant\n\n\n 9\n\facted in heat of passion.” Slager, 2018 WL 445497, at *2. To support that judgment, the\n\ndistrict court made extensive credibility determinations and factual findings.\n\n To begin, the court assessed the credibility of the only two testifying eyewitnesses\n\nto Scott’s shooting: Santana and Defendant. Recounting at length Defendant’s various\n\naccounts of the encounter, the district court discredited Defendant’s testimony,\n\ncharacterizing it as “contradictory,” “self-serving, evolving, and internally inconsistent.”\n\nId. at *4–6. Furthermore, the court found that Defendant’s experts did not bolster the\n\ncredibility of his account because each expert admitted that his or her respective technique\n\nprovided no definitive answer as to the key aspects of Defendant’s final version of the\n\nencounter. In contrast, Santana presented a “consistent story,” which the court found\n\ncredible. Id. at *4 (“[A] review of the statement Santana gave to SLED, Santana’s state\n\ncourt testimony, and his federal court testimony reveals a consistent story that is at odds\n\nwith [Defendant’s] presentation of the sequence of events . . . making Santana a more\n\ncredible witness.”).\n\n Based upon these credibility determinations, the district court made the following\n\nfindings of fact. First, the court found that the Santana video did not provide any grounds\n\nto support a finding of provocation. Second, the court found that the portion of the\n\nencounter not covered by the video—when Defendant and Scott were on the ground—also\n\ndid not support a finding of provocation. In particular, the court found that Scott “yelled\n\n‘Fuck the police,’ [and] that Scott ran away from [Defendant] during the initial traffic stop\n\nand disobeyed commands to stop.” Id. at *8. But the court further found that—contrary\n\nto Defendant’s statements—Scott was “never on top of [Defendant].” Id. The court found\n\n\n 10\n\fthat Scott did not wrestle the taser away and attempt to drive-stun Defendant because Scott\n\n“never had the taser in his hands.” Id. Rather than coming straight at Defendant with a\n\ntaser, Scott got “up from the ground [and] ran away from [Defendant],” the court found.\n\nId. Instead “of giving chase once again, [Defendant] shot at Scott eight times” and “five\n\nof those shots hit Scott in the back.” Id. Moreover, at “no point after [Defendant] fired the\n\nfirst shot—when Scott was nearly fifteen feet away—to when [Defendant] fired the eighth\n\nshot—when Scott was nearly forty feet away—did Scott turn around.” Id. Emphasizing\n\nthat “[w]ords alone will not suffice for a ‘heat of passion’ finding,” the court concluded\n\nthat these facts, “taken together,” “did not constitute adequate provocation to apply the\n\n‘heat of passion’ mitigation.” Id.\n\n In determining Defendant’s sentence, the district court also applied a two-level\n\nsentencing enhancement for obstruction of justice based upon Defendant’s false statements\n\nto the SLED investigators during his unsworn interview. U.S.S.G. § 3C1.1. In so doing,\n\nthe court recognized that Defendant was “represented by an attorney” and “was aware that\n\nthere was an investigation . . . underway for the shooting.” Id. at *14. The court also\n\nemphasized that, before making the statement, Defendant specifically inquired “about the\n\npresence of a video that captured the shooting.” Id. at *17. Believing that no video existed,\n\nDefendant “used the SLED interview to advance his false narrative of being forced to fire\n\nwhen Scott was coming toward him with a taser,” the court explained. Id.\n\n In deciding to apply the obstruction enhancement, the district court acknowledged\n\nthat SLED had already obtained Santana’s video when they interviewed Defendant. Still,\n\nwithout the video, some of Defendant’s false statements would have significantly\n\n\n 11\n\fobstructed the investigation, the court determined. Specifically, if it were “not for the\n\nSantana’s video,” Defendant’s statement that “Scott was coming toward him with a taser\n\nat the time he fired his first shot” “would certainly have hindered the investigation.” Id.\n\nThis was especially true because Defendant’s “status as a [law enforcement] officer would\n\nlikely have meant that his rendition of the events would not have been immediately\n\nquestioned.” Id.\n\n Defendant timely appealed his sentence.\n\n II.\n\n A.\n\n When, as here, a defendant is sentenced for deprivation of civil rights under color\n\nof law, the Sentencing Guidelines require the court to cross-reference the “offense\n\nguideline applicable to any underlying offense.” U.S.S.G. § 2H1.1(a)(1).\n\n Defendant first argues that the district court erred by determining that second-degree\n\nmurder was the proper cross-reference under Section 2H1.1. Specifically, Defendant\n\nclaims that when he shot Scott, he was provoked and thus acting without malice.\n\nConsequently, Defendant argues that the proper cross-reference was voluntary\n\nmanslaughter, not second-degree murder.\n\n At sentencing, the government “has the burden to prove a cross-referenced offense\n\nby a preponderance of the evidence[.]” United States v. Davis, 679 F.3d 177, 182 (4th Cir.\n\n2012). In reviewing “whether a district court properly applied . . . its application of a\n\ncross-reference, we review the district court’s legal conclusions de novo and its factual\n\nfindings for clear error.” United States v. Ashford, 718 F.3d 377, 380 (4th Cir. 2013)\n\n\n 12\n\f(quoting United States v. Layton, 564 F.3d 330, 334 (4th Cir. 2009)) (internal quotation\n\nmarks omitted). For the reasons that follow, we hold that the district court did not clearly\n\nerr in making its factual findings. We further conclude that the court correctly determined,\n\nbased on those findings, that second-degree murder was the proper cross-reference.\n\n i.\n\n “When sentencing courts engage in fact finding, preponderance of the evidence is\n\nthe appropriate standard of proof.” United States v. Span, 789 F.3d 320, 334 (4th Cir.\n\n2015) (citations and alterations omitted). We “will not reverse a lower court’s findings of\n\nfact simply because we would have decided the case differently.” Id. (quoting Easley v.\n\nCromartie, 532 U.S. 234, 242 (2001)). Instead, clear error exists only when “the reviewing\n\ncourt on the entire evidence is left with the definite and firm conviction that a mistake has\n\nbeen committed.” Id. (quoting Easley, 532 U.S. at 242).\n\n When a district court renders factual findings “based on determinations regarding\n\nthe credibility of witnesses, we give even greater deference to the trial court’s findings.”\n\nUnited States v. Hall, 664 F.3d 456, 462 (4th Cir. 2012) (quoting Anderson v. Bessemer\n\nCity, 470 U.S. 564, 575 (1985)) (internal quotation marks omitted); see also Teleguz v.\n\nZook, 806 F.3d 803, 812 (4th Cir. 2015) (“[C]redibility determinations are deserving of the\n\nhighest degree of appellate deference.”), cert. denied, 137 S. Ct. 95 (2016). Indeed, if a\n\ndistrict court’s finding “is based on his decision to credit the testimony of one of two or\n\nmore witnesses, each of whom has told a coherent and facially plausible story that is not\n\ncontradicted by extrinsic evidence, that finding, if not internally inconsistent, can virtually\n\nnever be clear error.” Anderson, 470 U.S. at 575 (1985).\n\n\n 13\n\f Because Santana’s video does not capture the entirety of the disputed period, the\n\ncourt based many of its factual findings on its assessment of the credibility of the two\n\ntestifying eyewitnesses to the encounter: Defendant and Santana. Examining at length each\n\nof Defendant’s four accounts of the encounter, the court discredited Defendant’s testimony\n\nas “contradictory,” “self-serving, evolving, and internally inconsistent.” Slager, 2018 WL\n\n445497, at *4–6. The record amply supports that credibility determination.\n\n Each time Defendant provided a new statement about the shooting, he put forward\n\nnew details materially bearing on his application of force. For example, in contrast to his\n\ntestimony in these proceedings, Defendant never told Lt. Bowman or the SLED\n\ninvestigators that Scott was “on top of [him] at some point” during the disputed period.\n\nJ.A. 727–28. Also, in contrast to his testimony in these proceedings, Defendant did not tell\n\nLt. Bowman or the SLED investigators that he was “drive stunned” by Scott. Id. And in\n\ncontrast to his testimony in these proceedings, Defendant did not tell either Lt. Bowman or\n\nthe SLED investigators that Scott “punched [him] in the chest.” J.A. 732. When Defendant\n\nwas asked why he previously failed to provide these details, he testified that his memory\n\nwas “fuzzy” and he still didn’t “recall” “some things.” Id. Defendant’s “evolving” account\n\nof the encounter provided the district court with ample factual basis to discredit\n\nDefendant’s testimony. See Munyakazi v. Lynch, 829 F.3d 291, 298 (4th Cir. 2016)\n\n(“Omissions, inconsistent statements, contradictory evidence, and inherently improbable\n\ntestimony are appropriate bases for making an adverse credibility determination.” (internal\n\nquotation marks and alterations omitted)).\n\n\n\n\n 14\n\f That some of Defendant’s assertions are flatly contradicted by Santana’s video and\n\nby Defendant’s own plea agreement further supports the district court’s finding that\n\nDefendant’s account was not credible. Id. Santana’s video, for example, shows that when\n\nDefendant fired eight shots from his firearm, Scott was “running away, not pointing a Taser\n\nat [Defendant] or advancing toward him,” contrary to Defendant’s statement to Lt.\n\nBowman and the SLED investigators. Slager, 2018 WL 445497, at *6. And the video\n\nreveals that Defendant picked up his taser approximately ten feet behind where Defendant\n\nstood when he shot Scott—not between Scott and Defendant, as Defendant initially\n\nasserted. These contradictions further demonstrate that the district court did not clearly err\n\nin discerning Defendant’s testimony. See United States v. Savage, 885 F.3d 212, 220 (4th\n\nCir. 2018) (holding that it is for the factfinder to hear a witness’s “testimony, along with\n\nany alleged inconsistencies, and decide[] [whether] testimony [is] credible”).\n\n Santana, on the other hand, provided a consistent story, including as to the facts the\n\ndistrict court found significant in its sentencing opinion. Each time he was questioned,\n\nSantana testified that Scott never was on top of Defendant, always was facing down, never\n\ngained control of Defendant’s taser, and never charged at or tried to fight with Defendant.\n\nAnd each time he was questioned, Santana testified that once Scott was able to stand up,\n\nhe began to flee—that Scott never tried to stay and fight Defendant, much less charge at\n\nhim, as Defendant claimed.\n\n Additionally, unlike several of Defendant’s retellings of the encounter, Santana’s\n\nversion of events is—and always has been—consistent with the recorded video. On these\n\nfacts, the district court did not clearly err in crediting Santana’s consistent testimony. See\n\n\n 15\n\fUnited States v. Stark, 8 F.3d 822 (4th Cir. 1993) (unpublished opinion) (District court did\n\nnot clearly err in finding one witness’s “consistent testimony, substantiated in part by\n\n[documentary evidence], was more credible than [another witness’s] testimony, which the\n\ncourt found inconsistent and incredible in many respects.”). 3\n\n Defendant nevertheless claims that the district court reversibly erred in declining to\n\nfind that the testimony of Defendant’s expert witnesses rendered Defendant’s account of\n\nthe encounter credible. “As with lay witnesses, evaluating the credibility of experts and\n\nthe value of their opinions is also a function best committed to the district courts, and one\n\nto which appellate courts should defer[.]” Hall, 664 F.3d at 462 (citations and alterations\n\nomitted).\n\n Here, the court did not reversibly err by declining to give weight to the testimony\n\nand evidence presented by Defendant’s experts. The district court emphasized—as the\n\nrecord demonstrates—that each expert admitted their respective techniques could not\n\nprovide the court with definitive conclusions as to what happened during the disputed\n\nperiod. Instead, the experts couched their opinions with statements of equivocation and\n\ninvited the court to make its own judgment as to what, in fact, occurred during the disputed\n\nperiod. See, e.g., Supp. J.A. 89–90 (Fletcher opining that a taser “drive-stun cannot be\n\nexcluded as a possible heat source which has the potential to melt polyester fibers”); J.A.\n\n\n\n 3\n Defendant complains that the district court failed to point out in its sentencing\norder that Santana viewed the shooting “from a distance of 136–180 feet.” Appellant’s Br.\nat 16. Although we “do not dispute that there must be sufficient explanation for a sentence\nto be procedurally reasonable,” the court’s “thorough explanation” here was more than\nsufficient to meet this burden. United States v. Helton, 782 F.3d 148, 154 (4th Cir. 2015).\n\n 16\n\f1279–80 (Liscio testifying that the district court could not rely on his recreation of the\n\nscene, but instead “ha[d] to make your own judgment call,” to determine whether Scott\n\never held the taser); J.A. 1220 (Hallimore offering the court an “interpretation” of the\n\nenhanced audio). The district court thus did not reversibly err in choosing not to give\n\nweight to these equivocal opinions. 4\n\n In sum, the district court did not clearly err by crediting Santana’s version of the\n\nencounter—including that Scott was “never on top of [Defendant],” that Scott never had\n\nthe taser in his hands, that Scott immediately began to run away when he stood up, and that\n\nhe was running away when Defendant shot him, Slager, 2018 WL 445497, at *8—as\n\nopposed to Defendant’s (most recent) account. Notably, several of these key factual\n\ndeterminations are consistent with the facts Defendant admitted to in his plea agreement.\n\nSee, e.g., id. at *2 (Defendant “fired multiple shots at Scott while Scott was running away\n\nfrom him.”); id. (“[D]efendant’s Taser dropped to the ground behind [D]efendant.”).\n\n\n\n\n 4\n Defendant also relies upon the Federal Rules of Evidence and Daubert v. Merrell\nDow Pharmaceuticals, Inc., 509 U.S. 579 (1993), to argue that the court erred by failing to\ngive weight to Fletcher’s opinions. But the Rules of Evidence do not apply to sentencing.\nFed. R. Evid. 1101(d)(3). And this Court has not applied Daubert to sentencing hearings.\nUnited States v. Barnette, 211 F.3d 803, 815 (4th Cir. 2000); see also United States v.\nFields, 483 F.3d 313, 342 (5th Cir. 2007) (“No Circuit that we are aware of has applied\nDaubert to sentencing. . . . Since Daubert’s holding was based on the Federal Rules of\nEvidence, it is not directly applicable.”). Applying Daubert would run contrary to the\nsentencing court’s “wide discretion” to determine the “sources and types of evidence,”\nwhich are relevant for defendants’ individualized sentencing. Pepper v. United States, 562\nU.S. 476, 488 (2011). We thus reject Defendant’s Daubert argument.\n\n 17\n\f ii.\n\n Defendant next contends that the district court’s factual findings do not support a\n\nfinding of malice aforethought. Consequently, Defendant maintains that the court erred by\n\ndetermining the proper cross-reference was voluntary manslaughter, not second-degree\n\nmurder. Again, we disagree.\n\n Murder is “the unlawful killing of a human being with malice aforethought,” 18\n\nU.S.C. § 1111, whereas voluntary “manslaughter is the unlawful killing of a human being\n\nwithout malice . . . [u]pon a sudden quarrel or heat of passion,” 18 U.S.C. § 1112(a). In\n\nother words, malice aforethought “is the distinguishing characteristic which, when present,\n\nmakes a homicide murder rather than manslaughter.” United States v. Fleming, 739 F.2d\n\n945, 947 (4th Cir. 1984).\n\n “Malice aforethought may be established by evidence of conduct which is reckless\n\nand wanton and a gross deviation from a reasonable standard of care, of such a nature that\n\na [factfinder] is warranted in inferring that [the] defendant was aware of a serious risk of\n\ndeath or serious bodily harm.” Ashford, 718 F.3d at 384 (citations and alterations omitted).\n\nMalice does not “require proof of an intent to kill or injure.” Fleming, 739 F.2d at 947\n\n(citations omitted). Malice exists when the evidence demonstrates that the defendant acted\n\n“with a heart that was without regard for the life and safety of others.” Id. at 948 (citations\n\nomitted). A district court may infer malice when a defendant uses a weapon “in such a\n\nmanner as may be expected naturally and probably to cause death.” United States v.\n\nCelestine, 510 F.2d 457, 459 (9th Cir. 1975); accord United States v. Wright, 594 F.3d 259,\n\n268 (4th Cir. 2010) (finding malice when Defendant “engaged in a ‘reckless firing of the\n\n\n 18\n\ffirearm, a random firing with the intent to hurt someone’” (emphasis in original)); Ashford,\n\n718 F.3d at 384 (finding malice when Defendant “drew his firearm and pursued the fleeing”\n\nvictim).\n\n As Defendant sought to do here, a defendant may negate a finding of malice by\n\ndemonstrating that an intentional killing occurred “upon a sudden quarrel or heat of\n\npassion.” 18 U.S.C. § 1112(a); United States v. Velazquez, 246 F.3d 204, 212 (2d Cir.\n\n2001); United States v. Browner, 889 F.2d 549, 552 (5th Cir. 1989); United States v.\n\nRoston, 986 F.2d 1287, 1291 (9th Cir. 1993); United States v. Scafe, 822 F.2d 928, 932\n\n(10th Cir. 1987). Federal courts apply the common-law meaning of “sudden quarrel or\n\nheat of passion.” See, e.g., United States v. Martinez, 988 F.2d 685, 694 (7th Cir. 1993).\n\nUnder the common law, a defendant’s “heat of passion” must arise from “adequate\n\nprovocation.” See id.; Roston, 986 F.2d at 1291; United States v. Collins, 690 F.2d 431,\n\n437 (5th Cir. 1982); United States v. Medina, 755 F.2d 1269, 1272 (7th Cir. 1985); United\n\nStates v. Paul, 37 F.3d 496, 498 (9th Cir. 1994). Provocation is adequate when it “would\n\narouse a reasonable and ordinary person to kill someone.” United States v. Wagner, 834\n\nF.2d 1474, 1487 (9th Cir. 1987); see Velazquez, 246 F.3d at 213. When a law enforcement\n\nofficer, like Defendant, seeks to rely on a sudden quarrel or heat of passion defense, a court\n\nmust assess the adequacy of the provocation “by the standards of a reasonable officer.”\n\nSee Velazquez, 246 F.3d at 213 (citing United States v. Cobb, 905 F.2d 784, 789 (4th Cir.\n\n1999)).\n\n “[M]ere words” generally provide inadequate provocation to negate a finding of\n\nmalice. See Allen v. United States, 164 U.S. 492, 497 (1896); Velazquez, 246 F.3d at 213;\n\n\n 19\n\fUnited States v. McRae, 593 F.2d 700, 705 (5th Cir. 1979); see also 3 Wayne R. LaFave\n\n& Austin W. Scott, Jr., Substantive Criminal Law § 15.2(b)(6) (3d ed. 2018) (detailing\n\nextraordinary, but inapposite exceptions); Cobb, 905 F.2d at 789 (“mere words” cannot\n\n“justify the use of physical force by a police officer”). By contrast, “[m]utual combat” can\n\nconstitute adequate provocation under some circumstances. See Martinez, 988 F.2d at 696;\n\nUnited States v. Hardin, 443 F.2d 735, 738–39 (D.C. Cir. 1970); 3 LaFave at § 15.2(b)(2).\n\nBut when a victim is fleeing from combat and the defendant is neither angry nor in danger,\n\nmutual combat does not support a finding that a defendant acted in a heat of passion. See\n\nAshford, 718 F.3d at 380 (“[T]he ‘heat of passion’ mitigator plainly does not apply to an\n\naggressor who is ‘not angry,’ and has multiple opportunities to walk away from a dispute\n\nthat he incited.”).\n\n In this case, the district court did not reversibly err in determining that the facts\n\nsupported a finding of malice. In his plea agreement, Defendant admitted that he acted\n\n“voluntarily and intentionally with specific intent to do something the law forbids.” Slager,\n\n2018 WL 445497, at *2. Additionally, Defendant admitted that he “fired eight shots at\n\nScott, and each of those eight shots were fired while Scott was unarmed and running away.”\n\nId. Defendant’s voluntary, intentional, and repeated discharge of his firearm at Scott as he\n\nattempted to run away “may be expected naturally and probably to cause death.” Celestine,\n\n510 F.2d at 459; Cf. Wright, 594 F.3d at 268 (It is “perfectly foreseeable that someone\n\nw[ill] be killed” when firing a gun “with intent to hurt someone.”).\n\n Nor did the district court err in determining that Defendant’s malice was not negated\n\nby “sudden quarrel or heat of passion.” 18 U.S.C. § 1112(a). Even though Scott yelled\n\n\n 20\n\f“Fuck the police” prior to the shooting, the court rightly found that these words were\n\ninsufficient to provoke a reasonable officer—or any reasonable person—to kill. Slager,\n\n2018 WL 445497, at *8; see Velazquez, 246 F.3d at 207 (holding that prisoner yelling\n\n“Fuck you, you are not going to tell me what to do” was insufficient to provoke guards to\n\nkill in the “heat of passion”).\n\n Additionally, Defendant’s alleged mutual combat with Scott did not provide\n\nDefendant with adequate provocation because Scott was running away when Defendant\n\nshot him. See Ashford, 718 F.3d at 380. Perhaps most importantly, even though Defendant\n\nnow claims he was provoked, Defendant testified at his state proceedings that he was\n\nneither “provoked” nor “angry” during his altercation but was merely acting in “self-\n\ndefense.” J.A. 346–47. 5 Defendant cannot negate his malice through “sudden quarrel or\n\nheat of passion” when he previously testified he was neither “provoked” nor “angry.”\n\nAshford, 718 F.3d at 380.\n\n In conclusion, the district court did not reversibly err by inferring Defendant’s\n\nmalice from the facts it found credible. Moreover, the court did not reversibly err by\n\ndetermining that Defendant’s malice was not negated by “sudden quarrel or heat of\n\npassion.” Accordingly, the court properly cross-referenced second-degree murder.\n\n\n\n\n 5\n Because Defendant admitted in his plea agreement that he acted “willfully,” the\ndistrict court found that Defendant was foreclosed from arguing self-defense during his\nfederal sentencing hearing. Slager, 2018 WL 445497, at *2.\n\n 21\n\f B.\n\n Next, Defendant argues that the district court erred in applying a two-level sentence\n\nenhancement for obstructing justice based on Defendant’s false statements to SLED.\n\nDefendant raises this issue for the first time on appeal. “Because this issue was not\n\nadvanced in the district court, we review the district court decision for plain error.” United\n\nStates v. Hughes, 401 F.3d 540, 547 (4th Cir. 2005); see United States v. Brack, 651 F.3d\n\n388, 392 (4th Cir. 2011). For an error to be “plain,” it must be “obvious or clear under\n\ncurrent law.” Brack, 651 F.3d at 392. Under this circumscribed standard of review, we do\n\nnot find that the district court plainly erred by applying the obstruction sentencing\n\nenhancement.\n\n A sentencing court may apply the obstruction enhancement when a defendant: (1)\n\n“willfully obstructed or impeded, or attempted to obstruct or impede, the administration of\n\njustice with respect to the investigation . . . of the instant offense of conviction,” and (2)\n\n“the obstructive conduct related to the defendant’s offense of conviction and any relevant\n\nconduct.” U.S.S.G. § 3C1.1 (emphasis added). Defendant argues that the district court\n\nplainly erred in applying this enhancement because Defendant’s false statements to the\n\nSLED investigators “were not made under oath” and the SLED investigators already had\n\nSantana’s video when they interviewed Defendant, meaning that Defendant’s false\n\nstatements “did not significantly impede the official investigation.” Appellant’s Br. at 45.\n\n In support of his argument, Defendant emphasizes that the comments to the\n\nobstruction guideline state “[o]rdinarily . . . making false statements, not under oath to law\n\nenforcement officers”—as was the case here—does not warrant application of the\n\n\n 22\n\fenhancement. U.S.S.G. § 3C1.1 cmt. n.5 (emphases added). But the comments further\n\nstate that “providing a materially false statement to a law enforcement officer that\n\nsignificantly obstructed or impeded the official investigation” does warrant application of\n\nthe enhancement, regardless of whether the materially false statement was made under\n\noath. Id. cmt. n.4(G) (emphasis added). And the express text of the obstruction guideline\n\ncovers “attempted” obstruction of justice, indicating that application of the guideline is\n\nappropriate, at least in some circumstances, even when a defendant’s attempted obstruction\n\ndid not in fact result in the obstruction of an investigation. Id.\n\n Accordingly, Section 3C1.1 and its comments do not clearly answer the relevant\n\nquestion: whether an attempt to significantly obstruct an investigation through unsworn\n\nstatements warrants application of the enhancement. Nor has this Court’s case law\n\nprovided an “obvious” or “clear” answer to that question. Hughes, 401 F.3d at 547.\n\nNotably, as to that question, our sister circuits have reached divergent answers. Compare\n\nUnited States v. Girod, 646 F.3d 304, 318 (5th Cir. 2011) (enhancement can be appropriate\n\nbased upon attempted, but significant obstruction); United States v. Wolverine, 584 F.\n\nApp’x 646, 649 (9th Cir. 2014) (same); with United States v. Adejumo, 772 F.3d 513, 529\n\n(8th Cir. 2014) (enhancement is inappropriate based upon attempted, but significant\n\nobstruction); United States v. Griffin, 310 F.3d 1017, 1022–23 (7th Cir. 2002) (same). In\n\nsuch circumstances, Defendant cannot meet his burden to show that the district court\n\nplainly erred by applying a two-level sentencing enhancement for attempted, yet\n\n\n\n\n 23\n\fsignificant, obstruction of justice through unsworn statements to law enforcement\n\ninvestigators. 6\n\n III.\n\n In sum, the district court committed no reversible error in sentencing Defendant.\n\nFirst, the district court did not clearly err in crediting Santana’s description of the encounter\n\nand discrediting Defendant’s description. Second, the court properly inferred, from these\n\nfacts, malice as required for a second-degree murder cross-reference. Finally, the district\n\ncourt did not plainly err in applying an obstruction of justice enhancement. Accordingly,\n\nthe district court’s sentence is\n\n AFFIRMED.\n\n\n\n\n 6\n Defendant also objects to his federal prosecution on double jeopardy grounds.\nAcknowledging that current Supreme Court case law forecloses this argument, Defendant\npreserves it pending a possible change in the law.\n\n 24", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356942/", "author_raw": "WYNN, Circuit Judge:"}]}
WILKINSON
WYNN
DIAZ
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579689/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff - Appellee, v. Michael SLAGER, Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-4036\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff – Appellee,\n\nv.\n\nMICHAEL SLAGER,\n\n Defendant – Appellant.\n\n\n\nAppeal from the United States District Court for the District of South Carolina, at\nCharleston. David C. Norton, District Judge. (2:16-cr-00378-DCN-1)\n\n\nArgued: November 1, 2018 Decided: January 8, 2019\n\n\nBefore WILKINSON, WYNN, and DIAZ, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Wilkinson\nand Judge Diaz joined.\n\n\nARGUED: Elizabeth Anne Franklin-Best, BLUME, FRANKLIN-BEST & YOUNG,\nLLC, Columbia, South Carolina, for Appellant. Elizabeth Parr Hecker, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Appellee. ON BRIEF: John M.\nGore, Acting Assistant Attorney General, Tovah R. Calderon, Appellate Section, Civil\nRights Division, UNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C., for\nAppellee.\n\fWYNN, Circuit Judge:\n\n Defendant Michael Slager (“Defendant”), a former officer with the North\n\nCharleston Police Department, admitted that he “willfully” shot and killed Walter Scott\n\n(“Scott”), when Scott was unarmed and fleeing arrest. Defendant further admitted that his\n\ndecision to shoot Scott was “objectively unreasonable.” Based on those admissions,\n\nDefendant pleaded guilty to depriving Scott of his civil rights under color of law.\n\n The district court sentenced Defendant to a 240-month term of imprisonment.\n\nBefore this Court, Defendant argues that the district court reversibly erred in setting his\n\nsentence by: (1) using second-degree murder as the sentencing cross-reference for his\n\noffense rather than voluntary manslaughter, and (2) applying a two-level enhancement for\n\nobstruction of justice. Finding no reversible error, we affirm Defendant’s sentence.\n\n I.\n\n A.\n\n In May 2016, a federal grand jury in the District of South Carolina returned an\n\nindictment alleging, among other things, that Defendant, “while acting under color of law\n\nas an officer with the North Charleston Police Department, shot [and killed] Walter Scott\n\nwithout legal justification, willfully depriving him of the right . . . to be free from the use\n\nof unreasonable force by a law enforcement officer.” J.A. 13. In the meantime, Defendant\n\nwas tried in state court on one count of murder. That trial resulted in a hung jury and\n\nmistrial.\n\n Thereafter, Defendant entered into a global plea agreement with the United States\n\nand the State of South Carolina. Under that agreement, in exchange for Defendant’s guilty\n\n\n 2\n\fplea in federal court to one count of depriving Scott of his civil rights under color of law,\n\nthe United States agreed to drop the remaining counts of the indictment 1 and agreed to\n\nrecommend a three-level reduction in the applicable sentencing level for acceptance of\n\nresponsibility. Additionally, South Carolina agreed not to retry Defendant and dismissed\n\nthe murder charge against him.\n\n Some of the undisputed facts that formed the basis for Defendant’s plea includes\n\nevidence showing that on the morning of April 4, 2015, while on duty, Defendant stopped\n\nScott’s vehicle after observing that his center brake light was not working. After the stop,\n\nScott fled on foot and Defendant chased him. During the chase, Defendant shot his taser\n\nprobes twice, hitting and bringing Scott down with the second shot. See United States v.\n\nSlager, No. 2:16-CR-00378-DCN, 2018 WL 445497, at *2 (D.S.C. Jan. 16, 2018).\n\n At some point thereafter, Scott got up and fled. While Scott was unarmed and\n\nrunning away, Defendant drew his department-issued firearm and fired eight shots at Scott,\n\nfive of which struck Scott in the back. Scott died on the scene from these wounds. Id.\n\n A bystander witnessed and testified about the incident. The bystander also filmed\n\nparts of the incident. The bystander’s testimony and video of the incident directly\n\ncontradicted Defendant’s initial account of the incident. In conformance with the global\n\nguilty plea agreement, Defendant admitted that he “used deadly force even though it was\n\nobjectively unreasonable under the circumstances.” Id. And, Defendant acknowledged\n\n\n 1\n The federal indictment charged Defendant with: depriving Scott of his civil rights\nunder color of law, in violation of 18 U.S.C. § 242; using a weapon during the commission\nof a crime of violence, in violation of 18 U.S.C. § 924(c); and obstruction of justice, in\nviolation of 18 U.S.C. § 1512(b)(3).\n\n 3\n\fthat “his actions were done willfully, that is he acted voluntarily and intentionally and with\n\nspecific intent to do something that the law forbids.” Id.\n\n B.\n\n Defendant’s sentencing hearing began on December 4, 2017, and lasted four days.\n\nBecause Defendant pleaded guilty to depriving Scott of his civil rights under color of law,\n\nthe district court was required during sentencing to cross-reference the offense underlying\n\nthe deprivation. See U.S.S.G. § 2H1.1(a)(1). The government contended that the proper\n\ncross-reference was second-degree murder because Defendant was acting with malice\n\naforethought when he shot Scott. In contrast, Defendant argued that the proper cross-\n\nreference was voluntary manslaughter because he was provoked by Scott and was thus not\n\nacting with malice.\n\n Although most of the facts were undisputed at Defendant’s sentencing hearing, the\n\ngovernment and Defendant disagreed as to what occurred after Scott fell to the ground, but\n\nbefore Scott got up and ran away from Defendant.\n\n i.\n\n The government’s version of events is based primarily on the only third-party\n\neyewitness to the shooting, Feidin Santana. Santana recounted the shooting during a South\n\nCarolina Law Enforcement Division (“SLED”) interview, and during Defendant’s state\n\nand federal proceedings. Each time, Santana provided a consistent account of the shooting.\n\n While traveling to work on the morning of the shooting, Santana saw Scott running\n\nfrom Defendant. Santana followed, but briefly lost sight of Scott and Defendant. When\n\nSantana next saw them, Scott was facing down, and Defendant was on top of Scott and\n\n\n 4\n\f“trying to control” him. J.A. 971. Santana testified that it sounded like Scott was “being\n\nhurt” and he heard something “electric.” J.A. 972. According to Santana, Defendant\n\npunched Scott in the back, but Scott never flipped over. Santana did not see Scott punch\n\nback. Nor did Santana see Scott grab the taser and charge toward Defendant. Indeed,\n\nSantana never saw Scott holding the taser. Rather, according to Santana, Scott did not\n\nseem to want to “hurt” Defendant but was “just trying to leave.” J.A. 974. At some point,\n\nScott shot up “aggressively,” Santana testified. J.A. 975. By this, Santana meant that Scott\n\nwas “determined to . . . just leave.” Id. When Scott broke free and began to run, Defendant\n\nshot him. Defendant then handcuffed Scott and checked his pulse but did not treat him.\n\n Santana also recorded a portion of the encounter with his cell phone. Santana’s\n\nvideo does not clearly show the period during which Scott and Defendant were allegedly\n\non the ground. But the video does show that Scott stood up and was running away—not\n\npointing a taser at Defendant or advancing toward Defendant—when Defendant fired at\n\nhim. Additionally, the video shows Defendant picked up the taser approximately ten feet\n\nbehind the point where Defendant was standing when he shot Scott—not between Scott\n\nand Defendant.\n\n ii.\n\n In contrast to Santana’s consistent recollection of the encounter, Defendant provided\n\nfour different accounts as to what happened on the morning of April 4, 2015.\n\n First, Defendant made an on-scene statement to his superior officer, Lieutenant\n\nDaniel Bowman, who arrived shortly after the shooting occurred. Defendant told Lt.\n\nBowman that Scott continued to resist arrest after being tasered and falling to the ground.\n\n\n 5\n\fDefendant tased Scott twice more while he laid on the ground, but Scott resisted and “was\n\nable to roll over onto his back.” Supp. J.A. 75. Scott then “use[d] both hands to grab the\n\ntaser” and after “a short struggle,” Scott “was able to wrestle it away.” Id. Scott then\n\n“stood up and pointed the taser at” Defendant. Id. Defendant told Lt. Bowman that, when\n\nfaced with this alleged threat, he “drew his weapon as he was returning to the standing\n\nposition and fired multiple times.” Id. Several of Defendant’s shots struck Scott, who then\n\nfell to the ground. According to this account, Defendant then “rendered emergency aid\n\nuntil other officers arrived seconds later.” Id.\n\n Three days after the shooting, on April 7, 2015, Defendant gave a second account\n\nof the encounter in an unsworn interview with SLED investigators. Before giving this\n\nstatement, Defendant asked his attorney to verify with the SLED investigators whether\n\nthere was “[a]ny video, surveillance video of businesses, security cameras, [or] anything”\n\nelse documenting the shooting. J.A. 702. Defendant also asked whether there were any\n\nwitnesses who viewed the shooting. The SLED investigators did not apprise Defendant of\n\nSantana or his recorded video.\n\n At the start of the interview, the SLED investigators informed Defendant that the\n\ninterview was part of a criminal investigation and that Defendant could decline to\n\nparticipate. Still, Defendant agreed to make a statement. Over the course of the interview,\n\nDefendant added new details not mentioned in his prior statement to Lt. Bowman and\n\nphysically reenacted key aspects of the encounter. For example, Defendant claimed that\n\nScott was “coming straight at him” holding the taser, with his “arm extending straight out.”\n\nJ.A. 1640. Defendant told the SLED investigators that he was “shuffle-stepping” to avoid\n\n\n 6\n\fthe taser as he “pulled his gun.” Id. According to this account, Scott was “turning to his\n\nleft” when Defendant fired. Id. Then, “Scott ran off, stumbled into the grass, [and] fell to\n\nthe ground.” Id. Defendant further told the investigators that “Scott must have dropped”\n\nthe taser during this altercation, because he retrieved it “between the place where he had\n\nbeen shooting and where Scott landed.” J.A. 1641.\n\n During his state trial, Defendant provided a third description of his encounter with\n\nScott. In this retelling, Defendant claimed that, during the alleged ground struggle, he had\n\nattempted to put Scott’s left hand “behind his back to handcuff him.” J.A. 282. However,\n\nScott was in a “pushup position” and was “trying to get up” at the same time. Id. Defendant\n\ntestified that while this was occurring, he and Scott were “fighting” and “rolling around on\n\nthe ground.” J.A. 285. According to this account, Scott eventually “overpowered”\n\nDefendant and took his taser. J.A. 286. Defendant testified that at that point, he “instructed\n\nMr. Scott to turn right away and go, but he didn’t.” J.A. 288. Instead, Scott continued to\n\napproach Defendant, so Defendant “pulled [his] firearm” and “fired until the threat was\n\nstopped.” J.A. 289. Defendant’s testimony made clear that he was neither “provoked” nor\n\n“angry” during the shooting. J.A. 346–47. Instead, Defendant testified that he was simply\n\n“doing [his] job” and acting in “self-defense.” Id. at 347.\n\n Defendant provided his fourth description of the shooting over two days of\n\ntestimony at his federal pre-trial hearings. Again, Defendant added new details. For the\n\nfirst time, Defendant testified that Scott “punched [him] in the chest” during the ground\n\naltercation. J.A. 732. And for the first time, Defendant testified that Scott was “on top of\n\n[him] at some point.” J.A. 727. Defendant also testified—again, for the first time—that\n\n\n 7\n\fScott “drive stunned” 2 him during the altercation. J.A. 728. When asked why he had not\n\npreviously provided these details, Defendant testified that the surrounding events were\n\n“fuzzy” and there were still “some things [he did not] recall.” J.A. 727. But “some of [his]\n\nmemory [had] come back since” the shooting, he testified. Id. Still, Defendant testified\n\nthat he could not “recall anything [that he had] told SLED Agents” during his prior\n\ninterview. J.A. 860 (emphasis added).\n\n Defendant did not testify during his sentencing hearing, but he did attempt to\n\nbuttress aspects of his final account of the encounter through three expert witnesses. First,\n\nDefendant offered Eugene Liscio, an expert forensic analyst who reconstructs crime\n\nscenes. Using Santana’s video, Liscio created a 3D model of the scene of the encounter in\n\nan effort to determine whether Defendant or Scott was holding the taser prior to the\n\nshooting. Based upon the final position of the taser, Liscio opined that the video was\n\n“inconsistent” with Defendant throwing the taser with his right arm. J.A. 1257–58.\n\nHowever, Liscio equivocated as to this opinion, acknowledging that there was “no part in\n\n[the Santana video] where you can actually see the taser being held.” J.A. 1275. Liscio\n\nalso testified that, due to this limitation, the court would have to “make [its] own judgment\n\ncall” as to what in fact occurred. J.A. 1279–80.\n\n\n\n 2\n “Tasers generally have two modes. In dart mode, a taser shoots probes into a\nsubject and overrides the central nervous system. Drive stun mode, on the other hand, does\nnot cause an override of the victim’s central nervous system; that mode is used as a pain\ncompliance tool with limited threat reduction.” Estate of Armstrong ex rel. Armstrong v.\nVill. of Pinehurst, 810 F.3d 892, 897 n.3 (4th Cir.), cert. denied sub nom. Vill. of Pinehurst,\nN.C. v. Estate of Armstrong, 137 S. Ct. 61, 196 L. Ed. 2d 32 (2016) (internal quotations\nmarks and citations omitted).\n\n 8\n\f Second, Defendant offered David Hallimore, a forensic audio analyst, who applied\n\n“filtration[s] to [the Santana Video] to allow the speech to become more clear.” J.A. 1192,\n\n1216. Through these filtrations and “critical listening”—a skill Hallimore purportedly\n\nlearned by “train[ing his] brain effectively to better understand certain tones”—Hallimore\n\ntestified that he heard “fuck police” and “Let go of the taser or I’ll shoot” on the Santana\n\nvideo. J.A. 1204, 1216, 1218. But Hallimore also recognized this was his “interpretation”\n\nof the enhanced audio. J.A. 1220.\n\n Finally, Defendant introduced opinions and analyses rendered by Megan Fletcher,\n\nan agent with the SLED’s Trace Evidence Unit. Fletcher did not testify at the federal\n\nsentencing, but Defendant did reference her state trial testimony and report. Fletcher\n\nidentified polyester fibers in Defendant’s shirt that had been melted. Fletcher analyzed\n\nthese fibers and opined that a “taser drive-stun cannot be excluded as a possible heat source\n\nwhich has the potential to melt polyester fibers.” Supp. J.A. 89–90. But Fletcher averred\n\nthat she was “unable to definitively conclude whether a Taser did or did not cause the marks\n\non the uniform.” Supp. J.A. 89. Fletcher also acknowledged that she never determined—\n\nand therefore did not know—the melting point of the fibers in Defendant’s shirt.\n\n C.\n\n On January 16, 2018, the district court sentenced Defendant to a 240-month term of\n\nimprisonment. In an accompanying order explaining its sentencing decision, the court first\n\ndetermined that second-degree murder was the appropriate sentencing cross-reference for\n\nDefendant’s offense because “malice aforethought is proven by a gross deviation from the\n\nstandard of reasonable care, and [because] there is insufficient evidence that the defendant\n\n\n 9\n\facted in heat of passion.” Slager, 2018 WL 445497, at *2. To support that judgment, the\n\ndistrict court made extensive credibility determinations and factual findings.\n\n To begin, the court assessed the credibility of the only two testifying eyewitnesses\n\nto Scott’s shooting: Santana and Defendant. Recounting at length Defendant’s various\n\naccounts of the encounter, the district court discredited Defendant’s testimony,\n\ncharacterizing it as “contradictory,” “self-serving, evolving, and internally inconsistent.”\n\nId. at *4–6. Furthermore, the court found that Defendant’s experts did not bolster the\n\ncredibility of his account because each expert admitted that his or her respective technique\n\nprovided no definitive answer as to the key aspects of Defendant’s final version of the\n\nencounter. In contrast, Santana presented a “consistent story,” which the court found\n\ncredible. Id. at *4 (“[A] review of the statement Santana gave to SLED, Santana’s state\n\ncourt testimony, and his federal court testimony reveals a consistent story that is at odds\n\nwith [Defendant’s] presentation of the sequence of events . . . making Santana a more\n\ncredible witness.”).\n\n Based upon these credibility determinations, the district court made the following\n\nfindings of fact. First, the court found that the Santana video did not provide any grounds\n\nto support a finding of provocation. Second, the court found that the portion of the\n\nencounter not covered by the video—when Defendant and Scott were on the ground—also\n\ndid not support a finding of provocation. In particular, the court found that Scott “yelled\n\n‘Fuck the police,’ [and] that Scott ran away from [Defendant] during the initial traffic stop\n\nand disobeyed commands to stop.” Id. at *8. But the court further found that—contrary\n\nto Defendant’s statements—Scott was “never on top of [Defendant].” Id. The court found\n\n\n 10\n\fthat Scott did not wrestle the taser away and attempt to drive-stun Defendant because Scott\n\n“never had the taser in his hands.” Id. Rather than coming straight at Defendant with a\n\ntaser, Scott got “up from the ground [and] ran away from [Defendant],” the court found.\n\nId. Instead “of giving chase once again, [Defendant] shot at Scott eight times” and “five\n\nof those shots hit Scott in the back.” Id. Moreover, at “no point after [Defendant] fired the\n\nfirst shot—when Scott was nearly fifteen feet away—to when [Defendant] fired the eighth\n\nshot—when Scott was nearly forty feet away—did Scott turn around.” Id. Emphasizing\n\nthat “[w]ords alone will not suffice for a ‘heat of passion’ finding,” the court concluded\n\nthat these facts, “taken together,” “did not constitute adequate provocation to apply the\n\n‘heat of passion’ mitigation.” Id.\n\n In determining Defendant’s sentence, the district court also applied a two-level\n\nsentencing enhancement for obstruction of justice based upon Defendant’s false statements\n\nto the SLED investigators during his unsworn interview. U.S.S.G. § 3C1.1. In so doing,\n\nthe court recognized that Defendant was “represented by an attorney” and “was aware that\n\nthere was an investigation . . . underway for the shooting.” Id. at *14. The court also\n\nemphasized that, before making the statement, Defendant specifically inquired “about the\n\npresence of a video that captured the shooting.” Id. at *17. Believing that no video existed,\n\nDefendant “used the SLED interview to advance his false narrative of being forced to fire\n\nwhen Scott was coming toward him with a taser,” the court explained. Id.\n\n In deciding to apply the obstruction enhancement, the district court acknowledged\n\nthat SLED had already obtained Santana’s video when they interviewed Defendant. Still,\n\nwithout the video, some of Defendant’s false statements would have significantly\n\n\n 11\n\fobstructed the investigation, the court determined. Specifically, if it were “not for the\n\nSantana’s video,” Defendant’s statement that “Scott was coming toward him with a taser\n\nat the time he fired his first shot” “would certainly have hindered the investigation.” Id.\n\nThis was especially true because Defendant’s “status as a [law enforcement] officer would\n\nlikely have meant that his rendition of the events would not have been immediately\n\nquestioned.” Id.\n\n Defendant timely appealed his sentence.\n\n II.\n\n A.\n\n When, as here, a defendant is sentenced for deprivation of civil rights under color\n\nof law, the Sentencing Guidelines require the court to cross-reference the “offense\n\nguideline applicable to any underlying offense.” U.S.S.G. § 2H1.1(a)(1).\n\n Defendant first argues that the district court erred by determining that second-degree\n\nmurder was the proper cross-reference under Section 2H1.1. Specifically, Defendant\n\nclaims that when he shot Scott, he was provoked and thus acting without malice.\n\nConsequently, Defendant argues that the proper cross-reference was voluntary\n\nmanslaughter, not second-degree murder.\n\n At sentencing, the government “has the burden to prove a cross-referenced offense\n\nby a preponderance of the evidence[.]” United States v. Davis, 679 F.3d 177, 182 (4th Cir.\n\n2012). In reviewing “whether a district court properly applied . . . its application of a\n\ncross-reference, we review the district court’s legal conclusions de novo and its factual\n\nfindings for clear error.” United States v. Ashford, 718 F.3d 377, 380 (4th Cir. 2013)\n\n\n 12\n\f(quoting United States v. Layton, 564 F.3d 330, 334 (4th Cir. 2009)) (internal quotation\n\nmarks omitted). For the reasons that follow, we hold that the district court did not clearly\n\nerr in making its factual findings. We further conclude that the court correctly determined,\n\nbased on those findings, that second-degree murder was the proper cross-reference.\n\n i.\n\n “When sentencing courts engage in fact finding, preponderance of the evidence is\n\nthe appropriate standard of proof.” United States v. Span, 789 F.3d 320, 334 (4th Cir.\n\n2015) (citations and alterations omitted). We “will not reverse a lower court’s findings of\n\nfact simply because we would have decided the case differently.” Id. (quoting Easley v.\n\nCromartie, 532 U.S. 234, 242 (2001)). Instead, clear error exists only when “the reviewing\n\ncourt on the entire evidence is left with the definite and firm conviction that a mistake has\n\nbeen committed.” Id. (quoting Easley, 532 U.S. at 242).\n\n When a district court renders factual findings “based on determinations regarding\n\nthe credibility of witnesses, we give even greater deference to the trial court’s findings.”\n\nUnited States v. Hall, 664 F.3d 456, 462 (4th Cir. 2012) (quoting Anderson v. Bessemer\n\nCity, 470 U.S. 564, 575 (1985)) (internal quotation marks omitted); see also Teleguz v.\n\nZook, 806 F.3d 803, 812 (4th Cir. 2015) (“[C]redibility determinations are deserving of the\n\nhighest degree of appellate deference.”), cert. denied, 137 S. Ct. 95 (2016). Indeed, if a\n\ndistrict court’s finding “is based on his decision to credit the testimony of one of two or\n\nmore witnesses, each of whom has told a coherent and facially plausible story that is not\n\ncontradicted by extrinsic evidence, that finding, if not internally inconsistent, can virtually\n\nnever be clear error.” Anderson, 470 U.S. at 575 (1985).\n\n\n 13\n\f Because Santana’s video does not capture the entirety of the disputed period, the\n\ncourt based many of its factual findings on its assessment of the credibility of the two\n\ntestifying eyewitnesses to the encounter: Defendant and Santana. Examining at length each\n\nof Defendant’s four accounts of the encounter, the court discredited Defendant’s testimony\n\nas “contradictory,” “self-serving, evolving, and internally inconsistent.” Slager, 2018 WL\n\n445497, at *4–6. The record amply supports that credibility determination.\n\n Each time Defendant provided a new statement about the shooting, he put forward\n\nnew details materially bearing on his application of force. For example, in contrast to his\n\ntestimony in these proceedings, Defendant never told Lt. Bowman or the SLED\n\ninvestigators that Scott was “on top of [him] at some point” during the disputed period.\n\nJ.A. 727–28. Also, in contrast to his testimony in these proceedings, Defendant did not tell\n\nLt. Bowman or the SLED investigators that he was “drive stunned” by Scott. Id. And in\n\ncontrast to his testimony in these proceedings, Defendant did not tell either Lt. Bowman or\n\nthe SLED investigators that Scott “punched [him] in the chest.” J.A. 732. When Defendant\n\nwas asked why he previously failed to provide these details, he testified that his memory\n\nwas “fuzzy” and he still didn’t “recall” “some things.” Id. Defendant’s “evolving” account\n\nof the encounter provided the district court with ample factual basis to discredit\n\nDefendant’s testimony. See Munyakazi v. Lynch, 829 F.3d 291, 298 (4th Cir. 2016)\n\n(“Omissions, inconsistent statements, contradictory evidence, and inherently improbable\n\ntestimony are appropriate bases for making an adverse credibility determination.” (internal\n\nquotation marks and alterations omitted)).\n\n\n\n\n 14\n\f That some of Defendant’s assertions are flatly contradicted by Santana’s video and\n\nby Defendant’s own plea agreement further supports the district court’s finding that\n\nDefendant’s account was not credible. Id. Santana’s video, for example, shows that when\n\nDefendant fired eight shots from his firearm, Scott was “running away, not pointing a Taser\n\nat [Defendant] or advancing toward him,” contrary to Defendant’s statement to Lt.\n\nBowman and the SLED investigators. Slager, 2018 WL 445497, at *6. And the video\n\nreveals that Defendant picked up his taser approximately ten feet behind where Defendant\n\nstood when he shot Scott—not between Scott and Defendant, as Defendant initially\n\nasserted. These contradictions further demonstrate that the district court did not clearly err\n\nin discerning Defendant’s testimony. See United States v. Savage, 885 F.3d 212, 220 (4th\n\nCir. 2018) (holding that it is for the factfinder to hear a witness’s “testimony, along with\n\nany alleged inconsistencies, and decide[] [whether] testimony [is] credible”).\n\n Santana, on the other hand, provided a consistent story, including as to the facts the\n\ndistrict court found significant in its sentencing opinion. Each time he was questioned,\n\nSantana testified that Scott never was on top of Defendant, always was facing down, never\n\ngained control of Defendant’s taser, and never charged at or tried to fight with Defendant.\n\nAnd each time he was questioned, Santana testified that once Scott was able to stand up,\n\nhe began to flee—that Scott never tried to stay and fight Defendant, much less charge at\n\nhim, as Defendant claimed.\n\n Additionally, unlike several of Defendant’s retellings of the encounter, Santana’s\n\nversion of events is—and always has been—consistent with the recorded video. On these\n\nfacts, the district court did not clearly err in crediting Santana’s consistent testimony. See\n\n\n 15\n\fUnited States v. Stark, 8 F.3d 822 (4th Cir. 1993) (unpublished opinion) (District court did\n\nnot clearly err in finding one witness’s “consistent testimony, substantiated in part by\n\n[documentary evidence], was more credible than [another witness’s] testimony, which the\n\ncourt found inconsistent and incredible in many respects.”). 3\n\n Defendant nevertheless claims that the district court reversibly erred in declining to\n\nfind that the testimony of Defendant’s expert witnesses rendered Defendant’s account of\n\nthe encounter credible. “As with lay witnesses, evaluating the credibility of experts and\n\nthe value of their opinions is also a function best committed to the district courts, and one\n\nto which appellate courts should defer[.]” Hall, 664 F.3d at 462 (citations and alterations\n\nomitted).\n\n Here, the court did not reversibly err by declining to give weight to the testimony\n\nand evidence presented by Defendant’s experts. The district court emphasized—as the\n\nrecord demonstrates—that each expert admitted their respective techniques could not\n\nprovide the court with definitive conclusions as to what happened during the disputed\n\nperiod. Instead, the experts couched their opinions with statements of equivocation and\n\ninvited the court to make its own judgment as to what, in fact, occurred during the disputed\n\nperiod. See, e.g., Supp. J.A. 89–90 (Fletcher opining that a taser “drive-stun cannot be\n\nexcluded as a possible heat source which has the potential to melt polyester fibers”); J.A.\n\n\n\n 3\n Defendant complains that the district court failed to point out in its sentencing\norder that Santana viewed the shooting “from a distance of 136–180 feet.” Appellant’s Br.\nat 16. Although we “do not dispute that there must be sufficient explanation for a sentence\nto be procedurally reasonable,” the court’s “thorough explanation” here was more than\nsufficient to meet this burden. United States v. Helton, 782 F.3d 148, 154 (4th Cir. 2015).\n\n 16\n\f1279–80 (Liscio testifying that the district court could not rely on his recreation of the\n\nscene, but instead “ha[d] to make your own judgment call,” to determine whether Scott\n\never held the taser); J.A. 1220 (Hallimore offering the court an “interpretation” of the\n\nenhanced audio). The district court thus did not reversibly err in choosing not to give\n\nweight to these equivocal opinions. 4\n\n In sum, the district court did not clearly err by crediting Santana’s version of the\n\nencounter—including that Scott was “never on top of [Defendant],” that Scott never had\n\nthe taser in his hands, that Scott immediately began to run away when he stood up, and that\n\nhe was running away when Defendant shot him, Slager, 2018 WL 445497, at *8—as\n\nopposed to Defendant’s (most recent) account. Notably, several of these key factual\n\ndeterminations are consistent with the facts Defendant admitted to in his plea agreement.\n\nSee, e.g., id. at *2 (Defendant “fired multiple shots at Scott while Scott was running away\n\nfrom him.”); id. (“[D]efendant’s Taser dropped to the ground behind [D]efendant.”).\n\n\n\n\n 4\n Defendant also relies upon the Federal Rules of Evidence and Daubert v. Merrell\nDow Pharmaceuticals, Inc., 509 U.S. 579 (1993), to argue that the court erred by failing to\ngive weight to Fletcher’s opinions. But the Rules of Evidence do not apply to sentencing.\nFed. R. Evid. 1101(d)(3). And this Court has not applied Daubert to sentencing hearings.\nUnited States v. Barnette, 211 F.3d 803, 815 (4th Cir. 2000); see also United States v.\nFields, 483 F.3d 313, 342 (5th Cir. 2007) (“No Circuit that we are aware of has applied\nDaubert to sentencing. . . . Since Daubert’s holding was based on the Federal Rules of\nEvidence, it is not directly applicable.”). Applying Daubert would run contrary to the\nsentencing court’s “wide discretion” to determine the “sources and types of evidence,”\nwhich are relevant for defendants’ individualized sentencing. Pepper v. United States, 562\nU.S. 476, 488 (2011). We thus reject Defendant’s Daubert argument.\n\n 17\n\f ii.\n\n Defendant next contends that the district court’s factual findings do not support a\n\nfinding of malice aforethought. Consequently, Defendant maintains that the court erred by\n\ndetermining the proper cross-reference was voluntary manslaughter, not second-degree\n\nmurder. Again, we disagree.\n\n Murder is “the unlawful killing of a human being with malice aforethought,” 18\n\nU.S.C. § 1111, whereas voluntary “manslaughter is the unlawful killing of a human being\n\nwithout malice . . . [u]pon a sudden quarrel or heat of passion,” 18 U.S.C. § 1112(a). In\n\nother words, malice aforethought “is the distinguishing characteristic which, when present,\n\nmakes a homicide murder rather than manslaughter.” United States v. Fleming, 739 F.2d\n\n945, 947 (4th Cir. 1984).\n\n “Malice aforethought may be established by evidence of conduct which is reckless\n\nand wanton and a gross deviation from a reasonable standard of care, of such a nature that\n\na [factfinder] is warranted in inferring that [the] defendant was aware of a serious risk of\n\ndeath or serious bodily harm.” Ashford, 718 F.3d at 384 (citations and alterations omitted).\n\nMalice does not “require proof of an intent to kill or injure.” Fleming, 739 F.2d at 947\n\n(citations omitted). Malice exists when the evidence demonstrates that the defendant acted\n\n“with a heart that was without regard for the life and safety of others.” Id. at 948 (citations\n\nomitted). A district court may infer malice when a defendant uses a weapon “in such a\n\nmanner as may be expected naturally and probably to cause death.” United States v.\n\nCelestine, 510 F.2d 457, 459 (9th Cir. 1975); accord United States v. Wright, 594 F.3d 259,\n\n268 (4th Cir. 2010) (finding malice when Defendant “engaged in a ‘reckless firing of the\n\n\n 18\n\ffirearm, a random firing with the intent to hurt someone’” (emphasis in original)); Ashford,\n\n718 F.3d at 384 (finding malice when Defendant “drew his firearm and pursued the fleeing”\n\nvictim).\n\n As Defendant sought to do here, a defendant may negate a finding of malice by\n\ndemonstrating that an intentional killing occurred “upon a sudden quarrel or heat of\n\npassion.” 18 U.S.C. § 1112(a); United States v. Velazquez, 246 F.3d 204, 212 (2d Cir.\n\n2001); United States v. Browner, 889 F.2d 549, 552 (5th Cir. 1989); United States v.\n\nRoston, 986 F.2d 1287, 1291 (9th Cir. 1993); United States v. Scafe, 822 F.2d 928, 932\n\n(10th Cir. 1987). Federal courts apply the common-law meaning of “sudden quarrel or\n\nheat of passion.” See, e.g., United States v. Martinez, 988 F.2d 685, 694 (7th Cir. 1993).\n\nUnder the common law, a defendant’s “heat of passion” must arise from “adequate\n\nprovocation.” See id.; Roston, 986 F.2d at 1291; United States v. Collins, 690 F.2d 431,\n\n437 (5th Cir. 1982); United States v. Medina, 755 F.2d 1269, 1272 (7th Cir. 1985); United\n\nStates v. Paul, 37 F.3d 496, 498 (9th Cir. 1994). Provocation is adequate when it “would\n\narouse a reasonable and ordinary person to kill someone.” United States v. Wagner, 834\n\nF.2d 1474, 1487 (9th Cir. 1987); see Velazquez, 246 F.3d at 213. When a law enforcement\n\nofficer, like Defendant, seeks to rely on a sudden quarrel or heat of passion defense, a court\n\nmust assess the adequacy of the provocation “by the standards of a reasonable officer.”\n\nSee Velazquez, 246 F.3d at 213 (citing United States v. Cobb, 905 F.2d 784, 789 (4th Cir.\n\n1999)).\n\n “[M]ere words” generally provide inadequate provocation to negate a finding of\n\nmalice. See Allen v. United States, 164 U.S. 492, 497 (1896); Velazquez, 246 F.3d at 213;\n\n\n 19\n\fUnited States v. McRae, 593 F.2d 700, 705 (5th Cir. 1979); see also 3 Wayne R. LaFave\n\n& Austin W. Scott, Jr., Substantive Criminal Law § 15.2(b)(6) (3d ed. 2018) (detailing\n\nextraordinary, but inapposite exceptions); Cobb, 905 F.2d at 789 (“mere words” cannot\n\n“justify the use of physical force by a police officer”). By contrast, “[m]utual combat” can\n\nconstitute adequate provocation under some circumstances. See Martinez, 988 F.2d at 696;\n\nUnited States v. Hardin, 443 F.2d 735, 738–39 (D.C. Cir. 1970); 3 LaFave at § 15.2(b)(2).\n\nBut when a victim is fleeing from combat and the defendant is neither angry nor in danger,\n\nmutual combat does not support a finding that a defendant acted in a heat of passion. See\n\nAshford, 718 F.3d at 380 (“[T]he ‘heat of passion’ mitigator plainly does not apply to an\n\naggressor who is ‘not angry,’ and has multiple opportunities to walk away from a dispute\n\nthat he incited.”).\n\n In this case, the district court did not reversibly err in determining that the facts\n\nsupported a finding of malice. In his plea agreement, Defendant admitted that he acted\n\n“voluntarily and intentionally with specific intent to do something the law forbids.” Slager,\n\n2018 WL 445497, at *2. Additionally, Defendant admitted that he “fired eight shots at\n\nScott, and each of those eight shots were fired while Scott was unarmed and running away.”\n\nId. Defendant’s voluntary, intentional, and repeated discharge of his firearm at Scott as he\n\nattempted to run away “may be expected naturally and probably to cause death.” Celestine,\n\n510 F.2d at 459; Cf. Wright, 594 F.3d at 268 (It is “perfectly foreseeable that someone\n\nw[ill] be killed” when firing a gun “with intent to hurt someone.”).\n\n Nor did the district court err in determining that Defendant’s malice was not negated\n\nby “sudden quarrel or heat of passion.” 18 U.S.C. § 1112(a). Even though Scott yelled\n\n\n 20\n\f“Fuck the police” prior to the shooting, the court rightly found that these words were\n\ninsufficient to provoke a reasonable officer—or any reasonable person—to kill. Slager,\n\n2018 WL 445497, at *8; see Velazquez, 246 F.3d at 207 (holding that prisoner yelling\n\n“Fuck you, you are not going to tell me what to do” was insufficient to provoke guards to\n\nkill in the “heat of passion”).\n\n Additionally, Defendant’s alleged mutual combat with Scott did not provide\n\nDefendant with adequate provocation because Scott was running away when Defendant\n\nshot him. See Ashford, 718 F.3d at 380. Perhaps most importantly, even though Defendant\n\nnow claims he was provoked, Defendant testified at his state proceedings that he was\n\nneither “provoked” nor “angry” during his altercation but was merely acting in “self-\n\ndefense.” J.A. 346–47. 5 Defendant cannot negate his malice through “sudden quarrel or\n\nheat of passion” when he previously testified he was neither “provoked” nor “angry.”\n\nAshford, 718 F.3d at 380.\n\n In conclusion, the district court did not reversibly err by inferring Defendant’s\n\nmalice from the facts it found credible. Moreover, the court did not reversibly err by\n\ndetermining that Defendant’s malice was not negated by “sudden quarrel or heat of\n\npassion.” Accordingly, the court properly cross-referenced second-degree murder.\n\n\n\n\n 5\n Because Defendant admitted in his plea agreement that he acted “willfully,” the\ndistrict court found that Defendant was foreclosed from arguing self-defense during his\nfederal sentencing hearing. Slager, 2018 WL 445497, at *2.\n\n 21\n\f B.\n\n Next, Defendant argues that the district court erred in applying a two-level sentence\n\nenhancement for obstructing justice based on Defendant’s false statements to SLED.\n\nDefendant raises this issue for the first time on appeal. “Because this issue was not\n\nadvanced in the district court, we review the district court decision for plain error.” United\n\nStates v. Hughes, 401 F.3d 540, 547 (4th Cir. 2005); see United States v. Brack, 651 F.3d\n\n388, 392 (4th Cir. 2011). For an error to be “plain,” it must be “obvious or clear under\n\ncurrent law.” Brack, 651 F.3d at 392. Under this circumscribed standard of review, we do\n\nnot find that the district court plainly erred by applying the obstruction sentencing\n\nenhancement.\n\n A sentencing court may apply the obstruction enhancement when a defendant: (1)\n\n“willfully obstructed or impeded, or attempted to obstruct or impede, the administration of\n\njustice with respect to the investigation . . . of the instant offense of conviction,” and (2)\n\n“the obstructive conduct related to the defendant’s offense of conviction and any relevant\n\nconduct.” U.S.S.G. § 3C1.1 (emphasis added). Defendant argues that the district court\n\nplainly erred in applying this enhancement because Defendant’s false statements to the\n\nSLED investigators “were not made under oath” and the SLED investigators already had\n\nSantana’s video when they interviewed Defendant, meaning that Defendant’s false\n\nstatements “did not significantly impede the official investigation.” Appellant’s Br. at 45.\n\n In support of his argument, Defendant emphasizes that the comments to the\n\nobstruction guideline state “[o]rdinarily . . . making false statements, not under oath to law\n\nenforcement officers”—as was the case here—does not warrant application of the\n\n\n 22\n\fenhancement. U.S.S.G. § 3C1.1 cmt. n.5 (emphases added). But the comments further\n\nstate that “providing a materially false statement to a law enforcement officer that\n\nsignificantly obstructed or impeded the official investigation” does warrant application of\n\nthe enhancement, regardless of whether the materially false statement was made under\n\noath. Id. cmt. n.4(G) (emphasis added). And the express text of the obstruction guideline\n\ncovers “attempted” obstruction of justice, indicating that application of the guideline is\n\nappropriate, at least in some circumstances, even when a defendant’s attempted obstruction\n\ndid not in fact result in the obstruction of an investigation. Id.\n\n Accordingly, Section 3C1.1 and its comments do not clearly answer the relevant\n\nquestion: whether an attempt to significantly obstruct an investigation through unsworn\n\nstatements warrants application of the enhancement. Nor has this Court’s case law\n\nprovided an “obvious” or “clear” answer to that question. Hughes, 401 F.3d at 547.\n\nNotably, as to that question, our sister circuits have reached divergent answers. Compare\n\nUnited States v. Girod, 646 F.3d 304, 318 (5th Cir. 2011) (enhancement can be appropriate\n\nbased upon attempted, but significant obstruction); United States v. Wolverine, 584 F.\n\nApp’x 646, 649 (9th Cir. 2014) (same); with United States v. Adejumo, 772 F.3d 513, 529\n\n(8th Cir. 2014) (enhancement is inappropriate based upon attempted, but significant\n\nobstruction); United States v. Griffin, 310 F.3d 1017, 1022–23 (7th Cir. 2002) (same). In\n\nsuch circumstances, Defendant cannot meet his burden to show that the district court\n\nplainly erred by applying a two-level sentencing enhancement for attempted, yet\n\n\n\n\n 23\n\fsignificant, obstruction of justice through unsworn statements to law enforcement\n\ninvestigators. 6\n\n III.\n\n In sum, the district court committed no reversible error in sentencing Defendant.\n\nFirst, the district court did not clearly err in crediting Santana’s description of the encounter\n\nand discrediting Defendant’s description. Second, the court properly inferred, from these\n\nfacts, malice as required for a second-degree murder cross-reference. Finally, the district\n\ncourt did not plainly err in applying an obstruction of justice enhancement. Accordingly,\n\nthe district court’s sentence is\n\n AFFIRMED.\n\n\n\n\n 6\n Defendant also objects to his federal prosecution on double jeopardy grounds.\nAcknowledging that current Supreme Court case law forecloses this argument, Defendant\npreserves it pending a possible change in the law.\n\n 24\n[END_CASE]", "role": "user" } ]
4,579,691
UNITED STATES EX REL., Jon H. OBERG, Plaintiff-Appellant, v. PENNSYLVANIA HIGHER EDUCATION ASSISTANCE AGENCY, Defendant-Appellee, and Nelnet, Inc.; Kentucky Higher Education Student Loan Corp. ; SLM Corporation; Panhandle Plains Higher Education Authority ; Brazos Group; Arkansas Student Loan Authority; Education Loans Inc/SD; Southwest Student Services Corporation; Brazos Higher Education Service Corporation; Brazos Higher Education Authority, Inc.; Nelnet Education Loan Funding, Inc.; Panhandle-Plains Management and Servicing Corporation; Student Loan Finance Corporation; Education Loans Inc. ; Vermont Student Assistance Corporation, Defendants.
United States Ex Rel. Oberg v. Pa. Higher Educ. Assistance Agency
2019-01-08
18-1028
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Motz, Keenan, Harris", "parties": "", "opinions": [{"author": "DIANA GRIBBON MOTZ, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1028\n\n\nUNITED STATES EX REL., JON H. OBERG,\n\n Plaintiff – Appellant,\n\n v.\n\nPENNSYLVANIA HIGHER EDUCATION ASSISTANCE AGENCY,\n\n Defendant – Appellee,\n\n and\n\nNELNET, INC.; KENTUCKY HIGHER EDUCATION STUDENT LOAN\nCORP.; SLM CORPORATION; PANHANDLE PLAINS HIGHER EDUCATION\nAUTHORITY; BRAZOS GROUP; ARKANSAS STUDENT LOAN\nAUTHORITY; EDUCATION LOANS INC/SD; SOUTHWEST STUDENT\nSERVICES CORPORATION; BRAZOS HIGHER EDUCATION SERVICE\nCORPORATION; BRAZOS HIGHER EDUCATION AUTHORITY, INC.;\nNELNET EDUCATION LOAN FUNDING, INC.; PANHANDLE-PLAINS\nMANAGEMENT AND SERVICING CORPORATION; STUDENT LOAN\nFINANCE CORPORATION; EDUCATION LOANS INC.; VERMONT\nSTUDENT ASSISTANCE CORPORATION,\n\n Defendants.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:07-cv-00960-CMH-JFA)\n\n\nArgued: October 31, 2018 Decided: January 8, 2019\n\n\nBefore MOTZ, KEENAN, and HARRIS, Circuit Judges.\n\fAffirmed by published opinion. Judge Motz wrote the opinion, in which Judge Keenan\nand Judge Harris joined.\n\n\nARGUED: Eric Kenneth Bachman, ZUCKERMAN LAW, Chevy Chase, Maryland, for\nAppellant. George W. Hicks, Jr., KIRKLAND & ELLIS LLP, Washington, D.C., for\nAppellee. ON BRIEF: Jason M. Zuckerman, Washington, D.C., Dallas I. Hammer,\nZUCKERMAN LAW, Tysons Corner, Virginia, for Appellant. Matthew T. Regan,\nChicago, Illinois, Michael A. Glick, Tracie L. Bryant, Michael D. Lieberman,\nKIRKLAND & ELLIS LLP, Washington, D.C.; Daniel B. Huyett, STEVENS & LEE,\nP.C., Reading, Pennsylvania, for Appellee.\n\n\n\n\n 2\n\fDIANA GRIBBON MOTZ, Circuit Judge:\n\n This case returns to us again, this time on appeal from an adverse jury verdict.\n\nDr. Jon Oberg, as relator for the United States, brought this qui tam action against four\n\nstudent loan corporations, including the Pennsylvania Higher Education Assistance\n\nAgency (“PHEAA”). He alleged that the corporations had defrauded the Department of\n\nEducation and so violated the False Claims Act (“FCA”), 31 U.S.C. § 3729 et seq.\n\n Over the course of several appeals, we affirmed the dismissal of one defendant and\n\ntwo of the other defendants settled. See United States ex rel. Oberg v. Pa. Higher Educ.\n\nAssistance Agency, 804 F.3d 646, 650 (4th Cir. 2015); United States ex rel. Oberg v. Pa.\n\nHigher Educ. Assistance Agency, 745 F.3d 131, 145 (4th Cir. 2014); United States ex rel.\n\nOberg v. Ky. Higher Educ. Student Loan Corp., 681 F.3d 575, 579–81 (4th Cir. 2012).\n\nThe case proceeded to trial only against PHEAA. Oberg now appeals the jury’s\n\nunanimous verdict in favor of PHEAA. For the reasons that follow, we affirm.\n\n\n\n I.\n\n Oberg’s claim concerns a Department of Education subsidy program meant to\n\nencourage the issuance of low-interest federal student loans. It did so by offering Special\n\nAllowance Payments (“SAPs”) to certain qualifying lenders. 20 U.S.C. § 1087-1. For\n\none particular category of loans — those financed through tax-exempt bonds — Congress\n\nguaranteed lenders a 9.5 percent return. Id. § 1087-1(b)(2)(B). In the low-interest\n\nenvironment of the mid-2000s, this guaranteed rate made tax-exempt bonds a particularly\n\nattractive investment vehicle.\n\n 3\n\f To take advantage of the favorable return offered by the program, Oberg claims\n\nthat between 2002 and 2006, PHEAA submitted false claims for SAP subsidies by\n\nimproperly transferring student loans from non-tax-exempt bonds into tax-exempt bonds.\n\nIn doing so, PHEAA converted lower-interest floating-rate loans into loans that\n\nguaranteed a 9.5 percent return. This translated into millions of dollars in additional\n\nrevenue for PHEAA.\n\n During a five-day trial, the court admitted more than 100 exhibits and the jury\n\nheard testimony from more than a dozen witnesses. After deliberating for less than three\n\nhours, the jury returned a unanimous verdict in favor of PHEAA.\n\n Oberg timely noted this appeal, asking that we vacate the judgment and remand\n\nfor a new trial. He maintains that the district court substantially impeded his ability to\n\nprove his claims by improperly excluding critical evidence and rejecting Oberg’s\n\nproposed jury instructions.\n\n\n\n II.\n\n Oberg first contends that the district court erred by excluding certain evidence at\n\ntrial. We review a district court’s evidentiary rulings for abuse of discretion. SAS Inst.,\n\nInc. v. World Programming Ltd., 874 F.3d 370, 384 (4th Cir. 2017). “A district court\n\nabuses its discretion if it relies on an error of law or a clearly erroneous factual finding.”\n\nEEOC v. Freeman, 778 F.3d 463, 466 (4th Cir. 2015).\n\n At trial, Oberg sought admission of a 2004–2007 Performance Audit of PHEAA\n\nperformed by the Pennsylvania Auditor General. The Audit “evaluate[d] PHEAA’s\n\n 4\n\fperformance in improving access to higher education for Pennsylvania residents” and\n\nconcluded that PHEAA had largely “failed its mission.” The Audit found that PHEAA\n\npaid excessive salaries and bonuses to its executives and managers. The Audit also\n\ncatalogued and strongly criticized PHEAA’s lavish spending on employee benefits and\n\n“extravagant” expenditures on other unnecessary expenses. It “concluded that PHEAA\n\nwas governed and managed within a culture that sometimes allowed self-reward to\n\nsupersede fiscal prudence.” The district court excluded the Audit as irrelevant under\n\nFederal Rule of Evidence 401.\n\n Oberg contends that the Audit was relevant for several reasons. First, he argues\n\nthat the Audit’s critical findings tended to establish scienter — i.e., that desire for\n\npersonal gain motivated PHEAA officers to submit false claims. This argument fails\n\nbecause unlike the securities fraud cases on which Oberg relies, 1 FCA claims require a\n\nrelator to show only that the defendant had knowledge of the illegality of its actions,\n\nrather than specific intent to defraud. See, e.g., United States ex rel. Harrison v.\n\nWestinghouse Savannah River Co., 352 F.3d 908, 921 (4th Cir. 2003) (“In establishing\n\nliability under the FCA, a plaintiff need not prove the defendant had a financial motive to\n\nmake a false statement relating to a claim seeking government funds.”); United States ex\n\nrel. K & R Ltd. P’ship v. Mass. Hous. Fin. Agency, 530 F.3d 980, 984 (D.C. Cir. 2008)\n\n(finding evidence of defendant’s “motive to submit false claims — the need to bail itself\n\n 1\n Cases requiring proof of specific intent often turn on evidence of motive to prove\nscienter. See, e.g., Tellabs, Inc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 319, 325\n(2007) (finding motive “a relevant consideration” in measuring a defendant’s intent to\n“deceive, manipulate, or defraud” (internal quotation marks omitted)).\n\n 5\n\fout of financial trouble — could not . . . support a finding of knowledge, be it actual,\n\ndeliberate ignorance, or reckless disregard”). As the district court correctly explained:\n\n“It doesn’t really make any difference whether they were operating well or not well or\n\nwhatever. The only issue in this case is: Did they commit fraud and file a false claim?”\n\n Oberg next maintains that the Audit would have allowed him to rebut PHEAA’s\n\nown improper argument that its management acted with the “benevolent motive” to\n\nbenefit borrowers in carrying out its scheme. Oberg lodged little objection to this\n\nevidence at trial. Indeed, Oberg himself elicited most of the “benevolent motive”\n\ntestimony through his questions to PHEAA’s management. In any event, whether\n\nPHEAA’s management had benevolent motive was a collateral issue of limited relevance,\n\nmaking any error harmless. See Smith v. Balt. City Police Dep’t, 840 F.3d 193, 200–01\n\n(4th Cir. 2016).\n\n Finally, Oberg contends that the Audit would have helped him attack the\n\ncredibility of PHEAA’s executives. He argues that because witness credibility is “always\n\nat issue,” any “evidence concerning a witness’s credibility is always relevant.” United\n\nStates v. Green, 617 F.3d 233, 251 (3d Cir. 2010). This argument also fails, for Oberg\n\nquestioned PHEAA’s executives on the company’s compensation practices and elicited\n\nmuch of the same information contained in the Audit. Moreover, because nothing in the\n\nAudit contradicted the trial testimony of PHEAA executives, its admission would hardly\n\nhave aided Oberg in impeaching the executives’ credibility.\n\n\n\n\n 6\n\f In sum, the district court did not abuse its discretion in excluding the Audit as\n\nirrelevant. 2\n\n\n\n III.\n\n Oberg’s remaining claims center on the district court’s refusal to give several of\n\nhis proposed jury instructions.\n\n A.\n\n Before we consider the merit of his claims, we must first determine our standard\n\nof review.\n\n PHEAA contends that because Oberg did not object to the jury instructions before\n\nthe district court, he has failed to preserve his challenge to them and so we can review\n\nonly for plain error. Oberg counters that the district court rejected his properly requested\n\ninstructions in a “definitive ruling on the record,” and so we must instead review for\n\nabuse of discretion. Fed. R. Civ. P. 51(d)(1)(B); see also BMG Rights Mgmt. (US) LLC\n\nv. Cox Commc’ns, Inc., 881 F.3d 293, 305 (4th Cir. 2018).\n\n To resolve this question, we turn to the language of Federal Rule of Civil\n\nProcedure 51(d)(1)(B), which provides:\n\n A party may assign as error . . . a failure to give an instruction, if that party\n properly requested it and — unless the court rejected the request in a\n definitive ruling on the record — also properly objected.\n\n\n 2\n The parties also quarrel over whether the Audit was more prejudicial than\nprobative under Federal Rule of Evidence 403. Because we hold that the district court\ndid not err in excluding the Audit on relevance grounds, we need not address this issue.\n\n 7\n\fFed. R. Civ. P. 51(d)(1) (emphasis added).\n\n This provision was added to Rule 51 in 2003. See Fed. R. Civ. P. 51 advisory\n\ncommittee’s note to 2003 amendment (hereinafter, 2003 Advisory Committee Note).\n\nThe Advisory Committee explained that the change was motivated by concern over the\n\nmajority view “that a proper request for a jury instruction [was] not alone enough to\n\npreserve the right to appeal failure to give [an] instruction.” Id. The Committee\n\nconcluded that this rule was “appropriate when the court [had not] sufficiently focused on\n\nthe request” or “believe[d] that the request ha[d] been granted in substance although in\n\ndifferent words.” Id. But in other circumstances, the doctrine created “a trap for the\n\nunwary who fail[ed] to add an objection after the court . . . made it clear that the request\n\n[had] been considered and rejected on the merits.” Id. To correct this, the drafters added\n\nthe ruling-on-the-record language to “establish[] authority to review the failure to grant a\n\ntimely request, despite a failure to add an objection, when the court has made a definitive\n\nruling on the record rejecting the request.” Id.\n\n Notwithstanding the 2003 Amendment, some courts have seemed to continue to\n\nfollow a more stringent preservation rule than Rule 51(d)(1)(B) now appears to\n\ncommand. See EEOC v. New Breed Logistics, 783 F.3d 1057, 1075 (6th Cir. 2015); C.B.\n\nv. City of Sonora, 769 F.3d 1005, 1032 (9th Cir. 2014); Consumer Prod. Research &\n\nDesign, Inc. v. Jensen, 572 F.3d 436, 439 (7th Cir. 2009); Colon-Millin v. Sears Roebuck\n\nDe P.R., Inc., 455 F.3d 30, 41 (1st Cir. 2006); Collins v. Alco Parking Corp., 448 F.3d\n\n652, 656 (3d Cir. 2006).\n\n\n\n 8\n\f In our view, the Rule’s text and the Advisory Committee’s direction compel a\n\ndifferent approach. For a court’s rejection of a proposed instruction to constitute “a\n\ndefinitive ruling on the record,” the record must simply provide a reviewing court with a\n\nsufficient basis from which to determine the district court’s rejection was “on the merits”\n\n— in other words, that the court rejected the substance of the proposed instruction, not\n\nmerely the litigant’s choice of words. And, to be “definitive,” this rejection must be final\n\nrather than tentative.\n\n It remains true, of course, that “the mere tendering of a proposed instruction will\n\nnot preserve error for appeal.” Bunn v. Oldendorff Carriers GmbH & Co. KG, 723 F.3d\n\n454, 469 (4th Cir. 2013) (internal quotation marks omitted). But where a litigant\n\nproposes an instruction and the district court’s final ruling on the record demonstrates\n\nthat the court rejected it on the merits, the claim of error is preserved. This approach\n\nhews closely to the language and purpose of Rule 51(d)(1)(B) while remaining cognizant\n\nof the important interests embodied in requiring parties to raise objections in the district\n\ncourt. See Booker v. Mass. Dep’t of Pub. Health, 612 F.3d 34, 41 (1st Cir. 2010).\n\n Applied here, we must conclude that Oberg did not preserve his challenge to the\n\nfailure to give his proposed jury instructions. At the charge conference, the district court\n\noutlined its proposed jury instructions in broad terms, explaining that it would give\n\nstandard instructions on issues like the burden of proof and reasonable doubt, and would\n\nalso instruct the jury on the essential elements of an FCA claim. PHEAA raised several\n\nclarifying questions. Oberg sought only to ensure that the instructions contained a\n\nprovision not at issue on appeal, i.e., that proof of reckless disregard sufficed to establish\n\n 9\n\fan FCA claim. When the court called for any final comments, PHEAA asked whether\n\nthe court would read any of the instructions Oberg had submitted before the charge\n\nconference. The court responded that it was “not reading anybody’s instruction[s]” and it\n\nhad “the areas” it was “going to instruct on.” Oberg did not object. After instructing the\n\njury, the court once again asked whether the parties had any objections to the instructions.\n\nPHEAA raised two; Oberg responded: “[n]o objection from the relator.”\n\n Oberg argues that the district court’s statement that it would “not read anybody’s\n\ninstruction[s]” constitutes a “definitive ruling on the record” rejecting his instructions on\n\nthe merits. Fed. R. Civ. P. 51(d)(1)(B). This argument falls far short. Even assuming\n\nthat the court’s asserted “denial” — a brief response to a question by PHEAA, not Oberg\n\n— constituted a final ruling that foreclosed further discussion of the issue, we cannot\n\ndiscern from the record whether the court considered Oberg’s proposed instructions and\n\nrejected them for their substance, or simply believed that its own instructions were an\n\nadequate substitute. To preserve the issue, Oberg could have sought clarification as to\n\nthe court’s basis for rejecting his instructions, or he could have timely objected. Because\n\nhe did neither, we review only for plain error. 3\n\n\n\n\n 3\n Oberg’s reliance on dicta from Justice Scalia’s concurring opinion in Connick v.\nThompson, 563 U.S. 51, 72 (2011), cannot aid him. In Connick, Justice Scalia found that\na trial court’s response, “No, I’m not giving that,” to an appellant’s request for a jury\ninstruction was sufficient to “preserve a claim of error.” Id. at 75 (citing Fed. Rule Civ.\nP. 51(d)(1)(B)). The trial court in that case, however, had already ruled on the matter in a\nmotion for summary judgment — perhaps the quintessential example of a definitive\nruling on the merits.\n\n 10\n\f We note that the Tenth Circuit also recently addressed the 2003 amendment to\n\nRule 51. There, appellants claimed to have preserved their challenge to jury instructions\n\nby submitting proposed instructions and receiving a responsive email from the district\n\ncourt with the court’s tentative instructions, which did not incorporate their proposals.\n\nFirst Am. Title Ins. Co. v. Nw. Title Ins. Agency, 906 F.3d 884, 894–95 (10th Cir. 2018).\n\nThe Tenth Circuit observed that the district court did not suggest the email included its\n\nfinal instructions and that counsel had ample opportunity to discuss its proposed\n\ninstructions. Id. at 895. It thus held that the email did not constitute a “definitive”\n\nrejection as contemplated by Rule 51(d)(1)(B). Id. 4 Our holding here does not conflict\n\nwith the Tenth Circuit’s opinion, but that case does not provide as clear a parallel as\n\nPHEAA suggests. The district court’s statement that it would not read any party’s\n\ninstruction was arguably more final than that considered by the Tenth Circuit, but we\n\ncannot conclude that it was “on the merits,” and so it fails to satisfy the Rule for that\n\nreason.\n\n B.\n\n Because Oberg failed to preserve his objections to the jury instructions, we review\n\nonly for plain error. Oberg must show that in refusing to give his proposed instructions\n\n(1) the district court erred; “(2) the error is plain; (3) the error affects substantial rights;\n\n 4\n The Tenth Circuit went further to state that for a rejection to be definitive, “the\ndistrict court must expressly reject that specific argument.” Id. (emphasis added). In\nlight of the Advisory Committee’s guidance, we doubt that Rule 51(d)(1)(B) requires\nsuch specificity when a court’s ruling is otherwise final and on the merits. We need not\ndecide this question, however, because we cannot determine that the court’s rejection\nhere was on the merits.\n\n 11\n\fand (4) . . . the error seriously affects the fairness, integrity or public reputation of judicial\n\nproceedings.” Gregg v. Ham, 678 F.3d 333, 338 (4th Cir. 2012) (internal quotation\n\nmarks omitted). Even if his claim had been properly preserved, Oberg “faces a heavy\n\nburden, for we accord the district court much discretion to fashion the charge.” United\n\nStates v. Raza, 876 F.3d 604, 614 (4th Cir. 2017) (internal quotation marks omitted).\n\n Oberg first argues that the district court erred by failing to inform the jury that he\n\ndid not need to prove PHEAA had a “specific intent to defraud” the government for his\n\nFCA claim to succeed. Oberg’s proposed instruction did accurately restate a statutory\n\nelement of the FCA, 31 U.S.C. § 3729(b)(1)(B), but the instructions given by the district\n\ncourt “substantially covered” this issue. United States ex rel. Drakeford v. Tuomey, 792\n\nF.3d 364, 382 (4th Cir. 2015). The court’s instructions correctly listed the three ways in\n\nwhich the jury could find that PHEAA acted with the requisite knowledge, none of which\n\nrequired Oberg to show specific intent to defraud. The court did not err, much less\n\nplainly err, in declining to provide any additional instruction. See Noel v. Artson, 641\n\nF.3d 580, 590 (4th Cir. 2011) (“We have always left the choice between generality versus\n\nspecificity in the charge to the sound discretion of the trial courts.” (internal quotation\n\nmarks and alteration omitted)).\n\n Next, Oberg argues that the district court should have included an instruction\n\nstating that “benevolent motivation . . . is not a defense” to an FCA claim. Much like\n\nOberg’s previous objection, the instructions given by the court substantially covered this\n\ninstruction. Moreover, Oberg’s proposed instruction addresses only a collateral issue —\n\nattempting to “cure” any improper introduction of benevolent motive evidence — that\n\n 12\n\fwould not have affected the outcome in the district court. See Gregg, 678 F.3d at 338\n\n(requiring that proposed instruction must affect substantial rights to establish plain error).\n\n Finally, Oberg contends that the court erred by refusing to instruct the jury on how\n\nit could find PHEAA’s claims fraudulent. He asserts that because the court did not\n\nprovide the jury with the specific statutory language defining whether PHEAA’s claims\n\nwere eligible for the 9.5 percent SAP payments, the jury lacked the necessary tools to\n\ndecide an element of his FCA claim. Had the district court erred in its charge on this\n\nissue, it would have committed the type of error that would usually require reversal, even\n\non plain error review. See United States v. Jennings, 160 F.3d 1006, 1019 (4th Cir. 1998)\n\n(noting that “failure to instruct the jury on any essential element of an offense constitutes\n\nplain error”).\n\n But yet again, the district court’s instructions substantially covered the substance\n\nof Oberg’s proposal. Contrary to Oberg’s assertions, the court’s instructions sufficiently\n\nexplained that the jury had to consider whether PHEAA’s claims were “false or\n\nfraudulent,” and that the crux of Oberg’s argument was that PHEAA “was not entitled to\n\nthe 9.5 percent floor SAP on the claimed loans.” Although the district court did not detail\n\nthe precise steps the jury should follow to determine the eligibility of PHEAA’s SAP\n\nclaims, “where, as here, the instructions accurately covered all the issues in the case, the\n\nfailure to reference specific aspects of a party’s contentions cannot serve as a basis for a\n\nfinding of error.” Noel, 641 F.3d at 590 (internal quotation marks and alterations\n\nomitted).\n\n\n\n 13\n\f In contrast, Oberg’s proposed instruction provided a misleading framework that\n\npresumed his interpretation of the relevant statute and DOE’s regulations was correct,\n\nessentially requiring the jury to find PHEAA’s claims ineligible. See id. (“[W]e cannot\n\nfault the district court for declining to give a wink and a nod to the jury.”).\n\n Armed with extensive testimony and numerous exhibits, it was up to the jury to\n\ndetermine whether PHEAA’s claims were eligible and, if they were not, whether PHEAA\n\nknew so when it submitted its claims. This is precisely what the district court’s jury\n\ninstructions asked of them.\n\n\n\n IV.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 14", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356944/", "author_raw": "DIANA GRIBBON MOTZ, Circuit Judge:"}]}
MOTZ
KEENAN
HARRIS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579691/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES EX REL., Jon H. OBERG, Plaintiff-Appellant, v. PENNSYLVANIA HIGHER EDUCATION ASSISTANCE AGENCY, Defendant-Appellee, and Nelnet, Inc.; Kentucky Higher Education Student Loan Corp. ; SLM Corporation; Panhandle Plains Higher Education Authority ; Brazos Group; Arkansas Student Loan Authority; Education Loans Inc/SD; Southwest Student Services Corporation; Brazos Higher Education Service Corporation; Brazos Higher Education Authority, Inc.; Nelnet Education Loan Funding, Inc.; Panhandle-Plains Management and Servicing Corporation; Student Loan Finance Corporation; Education Loans Inc. ; Vermont Student Assistance Corporation, Defendants.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1028\n\n\nUNITED STATES EX REL., JON H. OBERG,\n\n Plaintiff – Appellant,\n\n v.\n\nPENNSYLVANIA HIGHER EDUCATION ASSISTANCE AGENCY,\n\n Defendant – Appellee,\n\n and\n\nNELNET, INC.; KENTUCKY HIGHER EDUCATION STUDENT LOAN\nCORP.; SLM CORPORATION; PANHANDLE PLAINS HIGHER EDUCATION\nAUTHORITY; BRAZOS GROUP; ARKANSAS STUDENT LOAN\nAUTHORITY; EDUCATION LOANS INC/SD; SOUTHWEST STUDENT\nSERVICES CORPORATION; BRAZOS HIGHER EDUCATION SERVICE\nCORPORATION; BRAZOS HIGHER EDUCATION AUTHORITY, INC.;\nNELNET EDUCATION LOAN FUNDING, INC.; PANHANDLE-PLAINS\nMANAGEMENT AND SERVICING CORPORATION; STUDENT LOAN\nFINANCE CORPORATION; EDUCATION LOANS INC.; VERMONT\nSTUDENT ASSISTANCE CORPORATION,\n\n Defendants.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:07-cv-00960-CMH-JFA)\n\n\nArgued: October 31, 2018 Decided: January 8, 2019\n\n\nBefore MOTZ, KEENAN, and HARRIS, Circuit Judges.\n\fAffirmed by published opinion. Judge Motz wrote the opinion, in which Judge Keenan\nand Judge Harris joined.\n\n\nARGUED: Eric Kenneth Bachman, ZUCKERMAN LAW, Chevy Chase, Maryland, for\nAppellant. George W. Hicks, Jr., KIRKLAND & ELLIS LLP, Washington, D.C., for\nAppellee. ON BRIEF: Jason M. Zuckerman, Washington, D.C., Dallas I. Hammer,\nZUCKERMAN LAW, Tysons Corner, Virginia, for Appellant. Matthew T. Regan,\nChicago, Illinois, Michael A. Glick, Tracie L. Bryant, Michael D. Lieberman,\nKIRKLAND & ELLIS LLP, Washington, D.C.; Daniel B. Huyett, STEVENS & LEE,\nP.C., Reading, Pennsylvania, for Appellee.\n\n\n\n\n 2\n\fDIANA GRIBBON MOTZ, Circuit Judge:\n\n This case returns to us again, this time on appeal from an adverse jury verdict.\n\nDr. Jon Oberg, as relator for the United States, brought this qui tam action against four\n\nstudent loan corporations, including the Pennsylvania Higher Education Assistance\n\nAgency (“PHEAA”). He alleged that the corporations had defrauded the Department of\n\nEducation and so violated the False Claims Act (“FCA”), 31 U.S.C. § 3729 et seq.\n\n Over the course of several appeals, we affirmed the dismissal of one defendant and\n\ntwo of the other defendants settled. See United States ex rel. Oberg v. Pa. Higher Educ.\n\nAssistance Agency, 804 F.3d 646, 650 (4th Cir. 2015); United States ex rel. Oberg v. Pa.\n\nHigher Educ. Assistance Agency, 745 F.3d 131, 145 (4th Cir. 2014); United States ex rel.\n\nOberg v. Ky. Higher Educ. Student Loan Corp., 681 F.3d 575, 579–81 (4th Cir. 2012).\n\nThe case proceeded to trial only against PHEAA. Oberg now appeals the jury’s\n\nunanimous verdict in favor of PHEAA. For the reasons that follow, we affirm.\n\n\n\n I.\n\n Oberg’s claim concerns a Department of Education subsidy program meant to\n\nencourage the issuance of low-interest federal student loans. It did so by offering Special\n\nAllowance Payments (“SAPs”) to certain qualifying lenders. 20 U.S.C. § 1087-1. For\n\none particular category of loans — those financed through tax-exempt bonds — Congress\n\nguaranteed lenders a 9.5 percent return. Id. § 1087-1(b)(2)(B). In the low-interest\n\nenvironment of the mid-2000s, this guaranteed rate made tax-exempt bonds a particularly\n\nattractive investment vehicle.\n\n 3\n\f To take advantage of the favorable return offered by the program, Oberg claims\n\nthat between 2002 and 2006, PHEAA submitted false claims for SAP subsidies by\n\nimproperly transferring student loans from non-tax-exempt bonds into tax-exempt bonds.\n\nIn doing so, PHEAA converted lower-interest floating-rate loans into loans that\n\nguaranteed a 9.5 percent return. This translated into millions of dollars in additional\n\nrevenue for PHEAA.\n\n During a five-day trial, the court admitted more than 100 exhibits and the jury\n\nheard testimony from more than a dozen witnesses. After deliberating for less than three\n\nhours, the jury returned a unanimous verdict in favor of PHEAA.\n\n Oberg timely noted this appeal, asking that we vacate the judgment and remand\n\nfor a new trial. He maintains that the district court substantially impeded his ability to\n\nprove his claims by improperly excluding critical evidence and rejecting Oberg’s\n\nproposed jury instructions.\n\n\n\n II.\n\n Oberg first contends that the district court erred by excluding certain evidence at\n\ntrial. We review a district court’s evidentiary rulings for abuse of discretion. SAS Inst.,\n\nInc. v. World Programming Ltd., 874 F.3d 370, 384 (4th Cir. 2017). “A district court\n\nabuses its discretion if it relies on an error of law or a clearly erroneous factual finding.”\n\nEEOC v. Freeman, 778 F.3d 463, 466 (4th Cir. 2015).\n\n At trial, Oberg sought admission of a 2004–2007 Performance Audit of PHEAA\n\nperformed by the Pennsylvania Auditor General. The Audit “evaluate[d] PHEAA’s\n\n 4\n\fperformance in improving access to higher education for Pennsylvania residents” and\n\nconcluded that PHEAA had largely “failed its mission.” The Audit found that PHEAA\n\npaid excessive salaries and bonuses to its executives and managers. The Audit also\n\ncatalogued and strongly criticized PHEAA’s lavish spending on employee benefits and\n\n“extravagant” expenditures on other unnecessary expenses. It “concluded that PHEAA\n\nwas governed and managed within a culture that sometimes allowed self-reward to\n\nsupersede fiscal prudence.” The district court excluded the Audit as irrelevant under\n\nFederal Rule of Evidence 401.\n\n Oberg contends that the Audit was relevant for several reasons. First, he argues\n\nthat the Audit’s critical findings tended to establish scienter — i.e., that desire for\n\npersonal gain motivated PHEAA officers to submit false claims. This argument fails\n\nbecause unlike the securities fraud cases on which Oberg relies, 1 FCA claims require a\n\nrelator to show only that the defendant had knowledge of the illegality of its actions,\n\nrather than specific intent to defraud. See, e.g., United States ex rel. Harrison v.\n\nWestinghouse Savannah River Co., 352 F.3d 908, 921 (4th Cir. 2003) (“In establishing\n\nliability under the FCA, a plaintiff need not prove the defendant had a financial motive to\n\nmake a false statement relating to a claim seeking government funds.”); United States ex\n\nrel. K & R Ltd. P’ship v. Mass. Hous. Fin. Agency, 530 F.3d 980, 984 (D.C. Cir. 2008)\n\n(finding evidence of defendant’s “motive to submit false claims — the need to bail itself\n\n 1\n Cases requiring proof of specific intent often turn on evidence of motive to prove\nscienter. See, e.g., Tellabs, Inc. v. Makor Issues & Rights, Ltd., 551 U.S. 308, 319, 325\n(2007) (finding motive “a relevant consideration” in measuring a defendant’s intent to\n“deceive, manipulate, or defraud” (internal quotation marks omitted)).\n\n 5\n\fout of financial trouble — could not . . . support a finding of knowledge, be it actual,\n\ndeliberate ignorance, or reckless disregard”). As the district court correctly explained:\n\n“It doesn’t really make any difference whether they were operating well or not well or\n\nwhatever. The only issue in this case is: Did they commit fraud and file a false claim?”\n\n Oberg next maintains that the Audit would have allowed him to rebut PHEAA’s\n\nown improper argument that its management acted with the “benevolent motive” to\n\nbenefit borrowers in carrying out its scheme. Oberg lodged little objection to this\n\nevidence at trial. Indeed, Oberg himself elicited most of the “benevolent motive”\n\ntestimony through his questions to PHEAA’s management. In any event, whether\n\nPHEAA’s management had benevolent motive was a collateral issue of limited relevance,\n\nmaking any error harmless. See Smith v. Balt. City Police Dep’t, 840 F.3d 193, 200–01\n\n(4th Cir. 2016).\n\n Finally, Oberg contends that the Audit would have helped him attack the\n\ncredibility of PHEAA’s executives. He argues that because witness credibility is “always\n\nat issue,” any “evidence concerning a witness’s credibility is always relevant.” United\n\nStates v. Green, 617 F.3d 233, 251 (3d Cir. 2010). This argument also fails, for Oberg\n\nquestioned PHEAA’s executives on the company’s compensation practices and elicited\n\nmuch of the same information contained in the Audit. Moreover, because nothing in the\n\nAudit contradicted the trial testimony of PHEAA executives, its admission would hardly\n\nhave aided Oberg in impeaching the executives’ credibility.\n\n\n\n\n 6\n\f In sum, the district court did not abuse its discretion in excluding the Audit as\n\nirrelevant. 2\n\n\n\n III.\n\n Oberg’s remaining claims center on the district court’s refusal to give several of\n\nhis proposed jury instructions.\n\n A.\n\n Before we consider the merit of his claims, we must first determine our standard\n\nof review.\n\n PHEAA contends that because Oberg did not object to the jury instructions before\n\nthe district court, he has failed to preserve his challenge to them and so we can review\n\nonly for plain error. Oberg counters that the district court rejected his properly requested\n\ninstructions in a “definitive ruling on the record,” and so we must instead review for\n\nabuse of discretion. Fed. R. Civ. P. 51(d)(1)(B); see also BMG Rights Mgmt. (US) LLC\n\nv. Cox Commc’ns, Inc., 881 F.3d 293, 305 (4th Cir. 2018).\n\n To resolve this question, we turn to the language of Federal Rule of Civil\n\nProcedure 51(d)(1)(B), which provides:\n\n A party may assign as error . . . a failure to give an instruction, if that party\n properly requested it and — unless the court rejected the request in a\n definitive ruling on the record — also properly objected.\n\n\n 2\n The parties also quarrel over whether the Audit was more prejudicial than\nprobative under Federal Rule of Evidence 403. Because we hold that the district court\ndid not err in excluding the Audit on relevance grounds, we need not address this issue.\n\n 7\n\fFed. R. Civ. P. 51(d)(1) (emphasis added).\n\n This provision was added to Rule 51 in 2003. See Fed. R. Civ. P. 51 advisory\n\ncommittee’s note to 2003 amendment (hereinafter, 2003 Advisory Committee Note).\n\nThe Advisory Committee explained that the change was motivated by concern over the\n\nmajority view “that a proper request for a jury instruction [was] not alone enough to\n\npreserve the right to appeal failure to give [an] instruction.” Id. The Committee\n\nconcluded that this rule was “appropriate when the court [had not] sufficiently focused on\n\nthe request” or “believe[d] that the request ha[d] been granted in substance although in\n\ndifferent words.” Id. But in other circumstances, the doctrine created “a trap for the\n\nunwary who fail[ed] to add an objection after the court . . . made it clear that the request\n\n[had] been considered and rejected on the merits.” Id. To correct this, the drafters added\n\nthe ruling-on-the-record language to “establish[] authority to review the failure to grant a\n\ntimely request, despite a failure to add an objection, when the court has made a definitive\n\nruling on the record rejecting the request.” Id.\n\n Notwithstanding the 2003 Amendment, some courts have seemed to continue to\n\nfollow a more stringent preservation rule than Rule 51(d)(1)(B) now appears to\n\ncommand. See EEOC v. New Breed Logistics, 783 F.3d 1057, 1075 (6th Cir. 2015); C.B.\n\nv. City of Sonora, 769 F.3d 1005, 1032 (9th Cir. 2014); Consumer Prod. Research &\n\nDesign, Inc. v. Jensen, 572 F.3d 436, 439 (7th Cir. 2009); Colon-Millin v. Sears Roebuck\n\nDe P.R., Inc., 455 F.3d 30, 41 (1st Cir. 2006); Collins v. Alco Parking Corp., 448 F.3d\n\n652, 656 (3d Cir. 2006).\n\n\n\n 8\n\f In our view, the Rule’s text and the Advisory Committee’s direction compel a\n\ndifferent approach. For a court’s rejection of a proposed instruction to constitute “a\n\ndefinitive ruling on the record,” the record must simply provide a reviewing court with a\n\nsufficient basis from which to determine the district court’s rejection was “on the merits”\n\n— in other words, that the court rejected the substance of the proposed instruction, not\n\nmerely the litigant’s choice of words. And, to be “definitive,” this rejection must be final\n\nrather than tentative.\n\n It remains true, of course, that “the mere tendering of a proposed instruction will\n\nnot preserve error for appeal.” Bunn v. Oldendorff Carriers GmbH & Co. KG, 723 F.3d\n\n454, 469 (4th Cir. 2013) (internal quotation marks omitted). But where a litigant\n\nproposes an instruction and the district court’s final ruling on the record demonstrates\n\nthat the court rejected it on the merits, the claim of error is preserved. This approach\n\nhews closely to the language and purpose of Rule 51(d)(1)(B) while remaining cognizant\n\nof the important interests embodied in requiring parties to raise objections in the district\n\ncourt. See Booker v. Mass. Dep’t of Pub. Health, 612 F.3d 34, 41 (1st Cir. 2010).\n\n Applied here, we must conclude that Oberg did not preserve his challenge to the\n\nfailure to give his proposed jury instructions. At the charge conference, the district court\n\noutlined its proposed jury instructions in broad terms, explaining that it would give\n\nstandard instructions on issues like the burden of proof and reasonable doubt, and would\n\nalso instruct the jury on the essential elements of an FCA claim. PHEAA raised several\n\nclarifying questions. Oberg sought only to ensure that the instructions contained a\n\nprovision not at issue on appeal, i.e., that proof of reckless disregard sufficed to establish\n\n 9\n\fan FCA claim. When the court called for any final comments, PHEAA asked whether\n\nthe court would read any of the instructions Oberg had submitted before the charge\n\nconference. The court responded that it was “not reading anybody’s instruction[s]” and it\n\nhad “the areas” it was “going to instruct on.” Oberg did not object. After instructing the\n\njury, the court once again asked whether the parties had any objections to the instructions.\n\nPHEAA raised two; Oberg responded: “[n]o objection from the relator.”\n\n Oberg argues that the district court’s statement that it would “not read anybody’s\n\ninstruction[s]” constitutes a “definitive ruling on the record” rejecting his instructions on\n\nthe merits. Fed. R. Civ. P. 51(d)(1)(B). This argument falls far short. Even assuming\n\nthat the court’s asserted “denial” — a brief response to a question by PHEAA, not Oberg\n\n— constituted a final ruling that foreclosed further discussion of the issue, we cannot\n\ndiscern from the record whether the court considered Oberg’s proposed instructions and\n\nrejected them for their substance, or simply believed that its own instructions were an\n\nadequate substitute. To preserve the issue, Oberg could have sought clarification as to\n\nthe court’s basis for rejecting his instructions, or he could have timely objected. Because\n\nhe did neither, we review only for plain error. 3\n\n\n\n\n 3\n Oberg’s reliance on dicta from Justice Scalia’s concurring opinion in Connick v.\nThompson, 563 U.S. 51, 72 (2011), cannot aid him. In Connick, Justice Scalia found that\na trial court’s response, “No, I’m not giving that,” to an appellant’s request for a jury\ninstruction was sufficient to “preserve a claim of error.” Id. at 75 (citing Fed. Rule Civ.\nP. 51(d)(1)(B)). The trial court in that case, however, had already ruled on the matter in a\nmotion for summary judgment — perhaps the quintessential example of a definitive\nruling on the merits.\n\n 10\n\f We note that the Tenth Circuit also recently addressed the 2003 amendment to\n\nRule 51. There, appellants claimed to have preserved their challenge to jury instructions\n\nby submitting proposed instructions and receiving a responsive email from the district\n\ncourt with the court’s tentative instructions, which did not incorporate their proposals.\n\nFirst Am. Title Ins. Co. v. Nw. Title Ins. Agency, 906 F.3d 884, 894–95 (10th Cir. 2018).\n\nThe Tenth Circuit observed that the district court did not suggest the email included its\n\nfinal instructions and that counsel had ample opportunity to discuss its proposed\n\ninstructions. Id. at 895. It thus held that the email did not constitute a “definitive”\n\nrejection as contemplated by Rule 51(d)(1)(B). Id. 4 Our holding here does not conflict\n\nwith the Tenth Circuit’s opinion, but that case does not provide as clear a parallel as\n\nPHEAA suggests. The district court’s statement that it would not read any party’s\n\ninstruction was arguably more final than that considered by the Tenth Circuit, but we\n\ncannot conclude that it was “on the merits,” and so it fails to satisfy the Rule for that\n\nreason.\n\n B.\n\n Because Oberg failed to preserve his objections to the jury instructions, we review\n\nonly for plain error. Oberg must show that in refusing to give his proposed instructions\n\n(1) the district court erred; “(2) the error is plain; (3) the error affects substantial rights;\n\n 4\n The Tenth Circuit went further to state that for a rejection to be definitive, “the\ndistrict court must expressly reject that specific argument.” Id. (emphasis added). In\nlight of the Advisory Committee’s guidance, we doubt that Rule 51(d)(1)(B) requires\nsuch specificity when a court’s ruling is otherwise final and on the merits. We need not\ndecide this question, however, because we cannot determine that the court’s rejection\nhere was on the merits.\n\n 11\n\fand (4) . . . the error seriously affects the fairness, integrity or public reputation of judicial\n\nproceedings.” Gregg v. Ham, 678 F.3d 333, 338 (4th Cir. 2012) (internal quotation\n\nmarks omitted). Even if his claim had been properly preserved, Oberg “faces a heavy\n\nburden, for we accord the district court much discretion to fashion the charge.” United\n\nStates v. Raza, 876 F.3d 604, 614 (4th Cir. 2017) (internal quotation marks omitted).\n\n Oberg first argues that the district court erred by failing to inform the jury that he\n\ndid not need to prove PHEAA had a “specific intent to defraud” the government for his\n\nFCA claim to succeed. Oberg’s proposed instruction did accurately restate a statutory\n\nelement of the FCA, 31 U.S.C. § 3729(b)(1)(B), but the instructions given by the district\n\ncourt “substantially covered” this issue. United States ex rel. Drakeford v. Tuomey, 792\n\nF.3d 364, 382 (4th Cir. 2015). The court’s instructions correctly listed the three ways in\n\nwhich the jury could find that PHEAA acted with the requisite knowledge, none of which\n\nrequired Oberg to show specific intent to defraud. The court did not err, much less\n\nplainly err, in declining to provide any additional instruction. See Noel v. Artson, 641\n\nF.3d 580, 590 (4th Cir. 2011) (“We have always left the choice between generality versus\n\nspecificity in the charge to the sound discretion of the trial courts.” (internal quotation\n\nmarks and alteration omitted)).\n\n Next, Oberg argues that the district court should have included an instruction\n\nstating that “benevolent motivation . . . is not a defense” to an FCA claim. Much like\n\nOberg’s previous objection, the instructions given by the court substantially covered this\n\ninstruction. Moreover, Oberg’s proposed instruction addresses only a collateral issue —\n\nattempting to “cure” any improper introduction of benevolent motive evidence — that\n\n 12\n\fwould not have affected the outcome in the district court. See Gregg, 678 F.3d at 338\n\n(requiring that proposed instruction must affect substantial rights to establish plain error).\n\n Finally, Oberg contends that the court erred by refusing to instruct the jury on how\n\nit could find PHEAA’s claims fraudulent. He asserts that because the court did not\n\nprovide the jury with the specific statutory language defining whether PHEAA’s claims\n\nwere eligible for the 9.5 percent SAP payments, the jury lacked the necessary tools to\n\ndecide an element of his FCA claim. Had the district court erred in its charge on this\n\nissue, it would have committed the type of error that would usually require reversal, even\n\non plain error review. See United States v. Jennings, 160 F.3d 1006, 1019 (4th Cir. 1998)\n\n(noting that “failure to instruct the jury on any essential element of an offense constitutes\n\nplain error”).\n\n But yet again, the district court’s instructions substantially covered the substance\n\nof Oberg’s proposal. Contrary to Oberg’s assertions, the court’s instructions sufficiently\n\nexplained that the jury had to consider whether PHEAA’s claims were “false or\n\nfraudulent,” and that the crux of Oberg’s argument was that PHEAA “was not entitled to\n\nthe 9.5 percent floor SAP on the claimed loans.” Although the district court did not detail\n\nthe precise steps the jury should follow to determine the eligibility of PHEAA’s SAP\n\nclaims, “where, as here, the instructions accurately covered all the issues in the case, the\n\nfailure to reference specific aspects of a party’s contentions cannot serve as a basis for a\n\nfinding of error.” Noel, 641 F.3d at 590 (internal quotation marks and alterations\n\nomitted).\n\n\n\n 13\n\f In contrast, Oberg’s proposed instruction provided a misleading framework that\n\npresumed his interpretation of the relevant statute and DOE’s regulations was correct,\n\nessentially requiring the jury to find PHEAA’s claims ineligible. See id. (“[W]e cannot\n\nfault the district court for declining to give a wink and a nod to the jury.”).\n\n Armed with extensive testimony and numerous exhibits, it was up to the jury to\n\ndetermine whether PHEAA’s claims were eligible and, if they were not, whether PHEAA\n\nknew so when it submitted its claims. This is precisely what the district court’s jury\n\ninstructions asked of them.\n\n\n\n IV.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 14\n[END_CASE]", "role": "user" } ]
4,579,694
State of SOUTH CAROLINA, Plaintiff - Appellee, v. UNITED STATES of America; United States Department of Energy; Rick Perry, in His Official Capacity as Secretary of Energy; National Nuclear Security Administration; Lisa E. Gordon-Hagerty, in Her Official Capacity as Administrator of the National Nuclear Security Administration and Undersecretary for Nuclear Security, Defendants - Appellants.
State of South Carolina v. United States
2019-01-08
18-1684
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Niemeyer, King, Wynn", "parties": "", "opinions": [{"author": "WYNN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1684\n\n\nSTATE OF SOUTH CAROLINA,\n\n Plaintiff – Appellee,\n\nv.\n\nUNITED STATES OF AMERICA; UNITED STATES DEPARTMENT OF\nENERGY; RICK PERRY, in his official capacity as Secretary of Energy;\nNATIONAL NUCLEAR SECURITY ADMINISTRATION; LISA E. GORDON-\nHAGERTY, in her official capacity as Administrator of the National Nuclear\nSecurity Administration and Undersecretary for Nuclear Security,\n\n Defendants – Appellants.\n\n\n\nAppeal from the United States District Court for the District of South Carolina, at Aiken.\nJ. Michelle Childs, District Judge. (1:18-cv-01431-JMC)\n\n\nArgued: September 27, 2018 Decided: January 8, 2019\n\n\nBefore NIEMEYER, KING, and WYNN, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Wynn wrote the opinion, in which\nJudge Niemeyer and Judge King joined.\n\n\nARGUED: Andrew Alperin Rohrbach, UNITED STATES DEPARTMENT OF\nJUSTICE, Washington, D.C., for Appellants. Randolph R. Lowell, WILLOUGHBY &\nHOEFER, PA, Columbia, South Carolina, for Appellee. ON BRIEF: Chad A. Readler,\nActing Assistant Attorney General, Mark B. Stern, Daniel Tenny, Civil Division,\n\fUNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C.; Sherri A. Lydon,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Columbia,\nSouth Carolina, for Appellants.\n\n\n\n\n 2\n\fWYNN, Circuit Judge:\n\n The State of South Carolina brought this action to enjoin the United States of\n\nAmerica and other Defendants 1 (collectively, “the United States”) from terminating the\n\nconstruction of a mixed-oxide fuel nuclear processing facility located at the Savannah\n\nRiver Site in South Carolina. South Carolina alleges that the United States Department\n\nof Energy unlawfully failed to (1) prepare a supplemental Environmental Impact\n\nStatement analyzing the long-term storage of plutonium in the state; and (2) follow\n\nstatutory waiver provisions for terminating construction of the facility. We conclude that\n\nSouth Carolina has not established standing to pursue either of these claims.\n\nAccordingly, we vacate the preliminary injunction imposed by the district court.\n\n I.\n\n Following the collapse of the Soviet Union and the end of the Cold War, the\n\nUnited States of America and the Russian Federation began a worldwide nuclear\n\nnonproliferation effort that included developing plans for the safe disposition of nuclear\n\nweapons material. As part of this nonproliferation pact, the Department of Energy began\n\nstudying the effects of various nuclear waste storage and disposal strategies. In its initial\n\n1996 study, the Department of Energy prepared an Environmental Impact Statement in\n\naccordance with Section 4332 of the National Environmental Policy Act (“NEPA”), 42\n\n\n 1\n The other Defendants are the United States Department of Energy; Rick Perry, in\nhis official capacity as Secretary of Energy; the National Nuclear Security\nAdministration; and Lisa E. Gordon-Hagerty, in her official capacity as Administrator of\nthe National Nuclear Security Administration.\n\n\n 3\n\fU.S.C. § 4321 et seq., analyzing the potential environmental consequences associated\n\nwith the long-term storage of weapons-grade plutonium and highly enriched uranium\n\nprior to disposition. The Environmental Impact Statement addressed storage of these\n\nmaterials for a period of up to fifty years.\n\n Ultimately, the Department of Energy determined that the best approach to nuclear\n\nwaste disposal was a dual strategy involving (1) immobilization of a portion of the\n\nsurplus plutonium in glass or ceramic; and (2) irradiation of the remaining plutonium in\n\nmixed oxide fuel (the “MOX process”). Both strategies would convert the surplus\n\nnuclear material into forms that would meet the National Academy of Science’s Spent\n\nFuel Standard, meaning that the material would be “inaccessible and unattractive for\n\nweapons” use. J.A. 78.\n\n In 1997, the Department of Energy announced its intention to build a new mixed\n\noxide fuel fabrication facility (the “MOX facility”) to dispose of some of the nuclear\n\nmaterial using the MOX process. Following completion of a supplemental\n\nEnvironmental Impact Statement and a Record of Decision in January of 2000, the\n\nDepartment of Energy announced that the MOX facility would be located at the\n\nSavannah River Site along South Carolina’s border with Georgia. The facility’s original\n\nproduction goals included disposition of up to thirty-three metric tons of nuclear material\n\nusing the MOX process and immobilization of up to seventeen metric tons of additional\n\nnuclear material. As part of its supplemental Environmental Impact Statement, the\n\nDepartment of Energy continued to look at the environmental impacts of long-term\n\nplutonium storage.\n\n 4\n\f In 2002, the Department of Energy decided to drop the immobilization portion of\n\nthe disposition strategy, leaving the MOX process as the sole plutonium disposal method.\n\nThat same year, Congress directed the Secretary of Energy to submit a plan for the\n\nconstruction and operation of the MOX facility at the Savannah River site. Pub. L. No.\n\n107-314, § 3182 (2002), subsequently codified as 50 U.S.C. § 2566. Congress further\n\nauthorized the Secretary to take corrective actions if the construction timetable and\n\noperation schedule for the MOX facility were not being met. Additionally, Congress also\n\nrequired that in the event the MOX facility failed to achieve its production goals, the\n\nDepartment of Energy remove plutonium shipped to South Carolina for processing. See\n\n50 U.S.C. § 2566(c), § 2566(e). Finally, as part of its findings, Congress mentioned the\n\neconomic benefit that the MOX facility would bring to the State of South Carolina,\n\nnoting that the economic benefit would not be fully realized unless the facility was built.\n\nSee Pub. L. No. 107-314 at § 3181.\n\n Three years later, in 2005, the Department of Energy began transferring plutonium\n\nto the Savannah River Site for conversion, and in 2007, construction began on the MOX\n\nfacility. The original cost estimate for construction of the facility was $4.8 billion, with\n\ncompletion anticipated in 2016. And the original production goal estimate for the facility\n\nwas to have thirty-four metric tons of defense plutonium processed no later than January\n\n1, 2019. 50 U.S.C. § 2566(a)(2)(B).\n\n These original estimates proved grossly inaccurate due to delays and cost overruns\n\nin the construction of the MOX facility. The Department of Energy now estimates cost\n\n\n\n 5\n\ffor construction of the facility to be $17.17 billion, with completion now anticipated to be\n\nin 2048, over thirty years beyond the original estimated schedule.\n\n Since 2014, the Department of Energy has sought to terminate the MOX program\n\nand pursue an alternative method of plutonium disposal known as “Dilute and Dispose,”\n\nwhich it contends is less costly, faster, and safer. Under the Dilute and Dispose method,\n\nnuclear material would be “downblended” with inhibitor materials to reduce the\n\nplutonium content to less than ten percent by weight. Upon completion of the\n\ndownblending process, the material would then be shipped from the Savannah River Site\n\nto the Waste Isolation Pilot Plant near Carlsbad, New Mexico, for permanent disposal.\n\n Thus far, Congress has continued to fund construction of the MOX facility and\n\nhas, to date, restricted the Department of Energy from utilizing MOX-related\n\nappropriations to begin termination of the program. To that end, in 2017, Congress\n\nenacted a statute providing that the Secretary of Energy “shall carry out construction and\n\nproject support activities relating to the MOX facility.” Pub. L. 115-91, § 3121(a), 131\n\nStat. 1283, 1892.\n\n However, Section 3121(b) of that statute allows the Secretary of Energy to\n\ndiscontinue construction of the MOX facility if certain conditions have been met.\n\nSpecifically, the Secretary of Energy must submit to the Congressional defense\n\ncommittees:\n\n (A) the commitment of the Secretary [of Energy] to remove plutonium\n intended to be disposed of in the MOX facility from South Carolina\n and ensure a sustainable future for the Savannah River Site;\n\n (B) a certification that―\n\n 6\n\f (i) an alternative option for carrying out the plutonium disposition\n program for the same amount of plutonium as the amount of plutonium\n intended to be disposed of in the MOX facility exists, meeting the\n requirements of the Business Operating Procedure of the National\n Nuclear Security Administration entitled “Analysis of Alternatives” and\n dated March 14, 2016 (BOP-03.07); and\n\n (ii) the remaining lifecycle cost, determined in a manner comparable to\n the cost estimating and assessment best practices of the Government\n Accountability Office [“GAO”], as found in the document of the\n Government Accountability Office entitled “GAO Cost Estimating and\n Assessment Guide” (GAO-09-3SP), for the alternative option would be\n less than approximately half of the estimated remaining lifecycle costs\n of the mixed oxide fuel program; and\n\n (C) the details of any statutory or regulatory changes necessary to complete\n the alternative option.\n\n§ 3121(b)(1).\n\n Additionally, in exercising his authority to discontinue construction of the MOX\n\nfacility, the Secretary of Energy\n\n (1) shall concurrently submit to the Committees on Appropriations of both\n Houses of Congress the lifecycle cost estimate used to make the\n certification under section 3121(b) of such Act; and\n\n (2) may not use funds provided for the Project to eliminate such Project\n until the date that is 30 days after the submission of the lifecycle cost\n estimate required under paragraph (1).\n\nPub. L. No. 115-141, § 309(c), 132 Stat. 348, 530 (2018).\n\n Pursuant to these provisions, on May 10, 2018, the Secretary of Energy submitted\n\na letter to the Chairman of the House Armed Services Committee that purported to\n\nexecute the authority of the Secretary of Energy under Section 3121(b) to discontinue\n\nconstruction of the MOX facility. The Secretary of Energy certified, inter alia, that (1)\n\n\n 7\n\fthe Department of Energy is committed to removing plutonium from South Carolina; (2)\n\nan alternative option for carrying out the plutonium disposition, the Dilute and Dispose\n\nmethod, exists and has a lifecycle cost of less than approximately half of the remaining\n\nlifecycle cost for the MOX program; (3) the Department of Energy estimated the cost of\n\nthe Dilute and Dispose approach in a manner compatible with the best practices of the\n\nGAO; and (4) the Department of Energy is committed to ensuring a sustainable future for\n\nthe Savannah River Site. The Secretary of Energy further reported that the Department\n\nof Energy expected the total cost of disposition via the Dilute and Dispose method to be\n\n$19.9 billion, compared to $49.4 billion for the total cost of construction of the MOX\n\nfacility and conversion of all the plutonium into MOX fuel.\n\n In accordance with the Secretary of Energy’s letter, the Department of Energy and\n\nthe National Nuclear Security Administration issued a Partial Stop Work Order on May\n\n14, 2018, ending all new contracts and hiring related to the MOX program. The\n\nDepartment of Energy further indicated its intent to issue a Full Stop Work Order and\n\nbegin winding down the MOX program, including terminating employees currently\n\nworking on the project, on or about June 11, 2018.\n\n On May 25, 2018, before the Department of Energy issued a full stop work order,\n\nSouth Carolina brought this action in the United States District Court for the District of\n\nSouth Carolina and moved for a preliminary injunction barring the federal government\n\nfrom terminating the MOX program. In its complaint, South Carolina asserted that the\n\nUnited States (1) violated NEPA by failing to prepare a supplemental Environmental\n\nImpact Statement covering a period of more than fifty years and (2) failed to satisfy\n\n 8\n\fSection 3121(b) because of the alleged insufficiency of the Secretary of Energy’s\n\ncertifications. 2\n\n On June 7, 2018, the district court granted South Carolina’s motion for\n\npreliminary injunction. The district court first found that South Carolina had standing\n\ndue to environmental risks associated with long-term storage at the Savannah River Site,\n\nwhich abuts property owned by South Carolina. As to the merits, the district court held,\n\nin pertinent part, that South Carolina was likely to succeed on the merits of its NEPA\n\nclaim and its claim that the Secretary of Energy’s certifications were insufficient. The\n\ndistrict court further found that South Carolina would be irreparably harmed absent a\n\npreliminary injunction and that the balance of equities tilted in South Carolina’s favor.\n\nThus, the district court enjoined the federal government from ceasing construction of the\n\nMOX facility and issuing the full stop work order. The United States timely appealed.\n\n After careful review, we dispositively hold that South Carolina failed to establish\n\nstanding and therefore we do not reach the district court’s determination on the merits of\n\nthis matter.\n\n\n\n\n 2\n South Carolina further claimed that the United States violated 50 U.S.C. § 2567\nby failing to consult with the governor before deciding to terminate the MOX facility.\nThe district court held that South Carolina failed to establish that that claim was likely to\nsucceed on the merits, and therefore that claim is not before this Court.\n\n\n 9\n\f II.\n\n A.\n\n On appeal, the United States contends that the district court erred in concluding\n\nthat South Carolina established standing to pursue the two claims that serve as the basis\n\nof the district court’s preliminary injunction order—the NEPA claim and the claim\n\npremised on the alleged insufficiency of the Secretary’s certifications. The standing\n\ndoctrine derives from “the Constitution’s limitation on Article III courts’ power to\n\nadjudicate ‘cases and controversies.’” Frank Krasner Enters. v. Montgomery Cty., 401\n\nF.3d 230, 234 (4th Cir. 2005) (quoting Allen v. Wright, 468 U.S. 737, 750–51 (1984),\n\nabrogated on other grounds by Lexmark Intern., Inc. v. Static Control Components, Inc.,\n\n572 U.S. 118 (2014)). Standing implicates the court’s subject matter jurisdiction. Long\n\nTerm Care Partners, LLC v. United States, 516 F.3d 225, 230 (4th Cir. 2008).\n\n Here, South Carolina, as plaintiff, bears the burden of establishing standing to\n\nassert each of its claims. See id.; see also Lewis v. Casey, 518 U.S. 343, 359 n.6 (1996)\n\n(“[A] plaintiff who has been subject to injurious conduct of one kind [does not] possess\n\nby virtue of that injury the necessary stake in litigating conduct of another kind, although\n\nsimilar, to which he has not been subject.” (internal quotation marks omitted)). We\n\nreview the question of whether South Carolina possesses standing de novo. Frank\n\nKrasner Enters., 401 F.3d at 234.\n\n To establish Article III standing, “a plaintiff must show (1) it has suffered an\n\n‘injury in fact’ that is (a) concrete and particularized and (b) actual or imminent, not\n\nconjectural or hypothetical; (2) the injury is fairly traceable to the challenged action of\n\n 10\n\fthe defendant; and (3) it is likely, as opposed to merely speculative, that the injury will be\n\nredressed by a favorable decision.” Friends of the Earth, Inc. v. Laidlaw Envtl. Servs.\n\n(TOC), Inc., 528 U.S. 167, 180–81 (2000). The United States contends South Carolina\n\nfailed to show it has suffered an injury-in-fact sufficient to give rise to Article III\n\nstanding.\n\n To satisfy the injury-in-fact requirement, a plaintiff must establish a “realistic\n\ndanger of sustaining a direct injury.” Peterson v. Nat’l Telcoms. & Info. Admin., 478\n\nF.3d 626, 632 (4th Cir. 2007) (quoting Babbitt v. United Farm Workers Nat’l Union, 442\n\nU.S. 289, 298 (1979)). “[W]hile it is true ‘that threatened rather than actual injury can\n\nsatisfy Article III standing requirements,’ . . . not all threatened injuries constitute an\n\ninjury-in-fact.” Beck v. McDonald, 848 F.3d 262, 271 (4th Cir. 2017) (quoting Friends of\n\nthe Earth, Inc. v. Gaston Copper Recycling Corp., 204 F.3d 149, 160 (4th Cir. 2000) (en\n\nbanc)). “Rather, as the Supreme Court has ‘emphasized repeatedly,’ an injury-in-fact\n\n‘must be concrete in both a qualitative and temporal sense.’” Id. (quoting Whitmore v.\n\nArkansas, 495 U.S. 149, 155 (1990)). The requirement that an alleged injury be palpable\n\nand imminent ensures that the injury “is not too speculative for Article III purposes.” Id.\n\n(quoting Lujan v. Defenders of Wildlife, 504 U.S. 555, 564–65 n.2 (1992)).\n\n On appeal, South Carolina contends that it has suffered an injury-in-fact sufficient\n\nto support standing because “[South Carolina] is harmed by being rendered the\n\npermanent repository of weapons-grade plutonium as a result of [the Department of\n\nEnergy’s] decision to terminate the MOX Facility without first complying with NEPA or\n\nfollowing the congressional mandates of § 3121.” Appellee’s Br. at 15–16. According to\n\n 11\n\fSouth Carolina, this “results in increased radiation exposure to the public, increased risks\n\nof nuclear-related accidents, and an increased threat of action by rogue states or terrorists\n\nseeking to acquire weapons-grade plutonium.” Id. at 14. But this alleged injury is too\n\nspeculative and thus, does not give rise to a concrete injury-in-fact sufficient to support\n\neither of South Carolina’s claims.\n\n The Supreme Court has repeatedly held that an alleged harm is too “speculative”\n\nto support Article III standing when the harm lies at the end of a “highly attenuated chain\n\nof possibilities.” Clapper v. Amnesty Int’l USA, 568 U.S. 398, 410 (2013); see also, e.g.,\n\nBeck, 848 F.3d at 275 (holding that plaintiffs, who received treatment at a medical center\n\nthat suffered a data breach and alleged that they were at risk of experiencing identity\n\ntheft, failed to establish standing because their theory of injury rested on an “attenuated\n\nchain of possibilities”).\n\n Illustratively in Clapper, the Supreme Court considered a challenge to Section 702\n\nof the Foreign Intelligence Surveillance Act, which “authoriz[es] the surveillance of\n\nindividuals who are not ‘United States persons’ and are reasonably believed to be located\n\noutside the United States.” 568 U.S. at 401. The plaintiffs—a group of “attorneys and\n\nhuman rights, labor, legal, and media organizations”—alleged that their work demanded\n\nthat they “engage in sensitive international communication with individuals who they\n\nbelieve are likely targets of surveillance under” Section 702, rendering it reasonably\n\nlikely that the government would target and intercept the plaintiffs’ communications. Id.\n\nat 401, 406.\n\n\n\n 12\n\f The Supreme Court held that the plaintiffs failed to establish a concrete injury-in-\n\nfact based on the possibility that their communications would be intercepted, explaining\n\nthat a series of hypothetical events would have to occur before the government would\n\nintercept any particular plaintiff’s communications. Id. at 1148–50. The Court held that\n\namong other steps, the government would have to decide to invoke its Section 702\n\nauthority to target a non-U.S. person with whom a plaintiff communicated, a panel of\n\nfederal judges would have to “conclude that the Government’s proposed surveillance\n\nprocedures satisfy [the statute’s] many safeguards and are consistent with the Fourth\n\nAmendment,” and the government would have to succeed in intercepting one of the\n\ntarget’s communications with the plaintiff. Id. Thus, the Court held that that the “highly\n\nattenuated chain of possibilities, d[id] not satisfy the requirement that threatened injury\n\nmust be certainly impending.” Id. at 1148 (citation omitted).\n\n Applying Clapper, this Court reached a similar conclusion in Beck, in which a\n\nputative class of veterans who received medical treatment at a veterans’ medical center\n\nalleged that they had been injured when two sets of records were stolen from the center.\n\n848 F.3d at 262, 267. Although none of the named plaintiffs alleged any actual or\n\nattempted misuse of the personal information contained in their stolen records, they\n\nalleged that they suffered cognizable injuries-in-fact because they faced “(1) [an]\n\nincreased risk of future identity theft, and (2) the costs of protecting against the same.”\n\nId. at 273. We concluded that both alleged injuries were too speculative to confer\n\nstanding. Id. at 275–77. As to the alleged increased risk of identity theft, in particular,\n\nwe explained that plaintiffs’ theory of injury required us to “assume that the thie[ves]\n\n 13\n\ftargeted the stolen items for the personal information they contained” and that the thieves\n\nwould “then select, from thousands of others, the personal information of the named\n\nplaintiffs, and attempt successfully to use that information to steal their identities.” Id. at\n\n275. “This ‘attenuated chain’ cannot confer standing,” we held. Id. We likewise\n\nrejected the plaintiffs’ costs of mitigation theory of standing as a “repackaged” version of\n\ntheir first theory of standing, amounting to an effort to recoup “costs they incurred in\n\nresponse to a speculative threat.” Id. at 276 (emphasis added) (quoting Clapper, 568\n\nU.S. at 416).\n\n Here, South Carolina’s theory of standing—that it will become “the permanent\n\nrepository of weapons-grade plutonium” and all the environmental, health, and safety\n\nrisks that entails, Appellee’s Br. at 15–16—rests on a similarly “highly attenuated chain\n\nof possibilities,” Clapper, 568 U.S. at 410. Between now and 2046—when the analysis\n\nin the current Environmental Impact Statement governing the risks associated with long-\n\nterm storage of weapons-grade nuclear material at the Savannah River Site expires—the\n\nDepartment of Energy has twenty-eight years to identify an alternative method for\n\ndisposing of the nuclear material or otherwise removing it from South Carolina. The\n\nSecretary of Energy already has certified that one potential alternative to the MOX\n\nprogram exists, the Dilute and Dispose method. And the Department of Energy may\n\nidentify and develop other methods during that twenty-eight-year period. Or the\n\nDepartment of Energy may decide to transfer the plutonium out of South Carolina to\n\nanother location.\n\n\n\n 14\n\f Furthermore, Congress has put in place contingency plans for the removal of\n\nplutonium shipped to the Savannah River Site to forestall the indefinite storage of\n\nplutonium in South Carolina. A federal statute requires that, by 2022, all additional\n\nplutonium transferred into South Carolina to the MOX facility, but not processed, must\n\nbe removed. 50 U.S.C. § 2566(c)(2). Notably, because the Department of Energy\n\nalready has failed to meet certain statutory time limits for disposing of nuclear material at\n\nthe site, South Carolina has successfully brought suit pursuant to the Administrative\n\nProcedure Act to enforce these congressionally mandated deadlines via a mandatory\n\ninjunction. See id. § 2566(c)(1) (requiring removal of one metric ton of plutonium no\n\nlater than January 1, 2016); South Carolina v. United States, 243 F. Supp. 3d 673 (D.S.C.\n\n2017), aff’d, 907 F.3d 742 (4th Cir. 2018) (ordering the Department of Energy to remove\n\none metric ton of plutonium within two years).\n\n In sum, for South Carolina’s alleged injury—becoming “the permanent repository\n\nof weapons-grade plutonium,” Appellee’s Br. at 15–16—to occur: (1) the proposed\n\nDilute and Dispose method must fail; (2) the Department of Energy must fail to identify\n\nan alternative method for disposing of the nuclear material; and (3) the Department of\n\nEnergy must breach its statutory obligation to remove the nuclear material from South\n\nCarolina, Congress must repeal that obligation, or the courts must refuse to enforce that\n\nobligation. At this juncture, before the Department of Energy has even had an\n\nopportunity to finish analyzing the Dilute and Dispose method, this “chain of\n\npossibilities” is too speculative to give rise to a sufficiently concrete injury-in-fact.\n\n\n\n 15\n\f That several of the links in this “chain of possibilities” the State’s standing theory\n\ncontemplates require our coordinate branches to either breach or abandon their existing\n\ncommitments to ensure timely removal of the nuclear material at the Savannah River Site\n\nfurther weighs against treating the South Carolina’s alleged injury as conferring standing.\n\nAs Clapper recognized, the standing doctrine is “built on separation-of-powers\n\nprinciples” and “serves to prevent the judicial process from being used to usurp the\n\npowers of the political branches.” 568 U.S. at 408 (citations omitted); see also Allen v.\n\nWright, 468 U.S. at 752 (1984) (“[Article] III standing is built on a single basic idea—the\n\nidea of separation of powers.”). To confer standing on South Carolina at this juncture\n\nbased on an alleged injury—becoming the permanent repository of nuclear material—that\n\nthe political branches already have made written and legally binding commitments to\n\nforestall would improperly “usurp the powers of the political branches.” Clapper, 568\n\nU.S. at 408.\n\n The “highly attenuated chain of possibilities” that must occur for South Carolina\n\nto become the permanent repository of nuclear material also sets this case apart from this\n\nCourt’s decision in Hodges v. Abraham, 300 F.3d 432 (4th Cir. 2002), upon which South\n\nCarolina principally relies.\n\n Like the instant case, Hodges dealt with the storage of plutonium at the Savannah\n\nRiver Site. Id. at 436. In 2002, the Department of Energy issued a Record of Decision\n\nauthorizing the immediate shipment of six metric tons of plutonium from a nuclear\n\nfacility in Colorado to the Savannah River Site. Id. The Governor of South Carolina\n\nsought to enjoin shipment of the plutonium into South Carolina, alleging that the\n\n 16\n\fDepartment of Energy’s existing Environmental Impact Statement, and its supplemental\n\nanalyses to the Environmental Impact Statement, related to storage of plutonium at the\n\nSavannah River Site violated NEPA in several ways. Id. at 445. This Court held that the\n\nGovernor adequately alleged an injury-in-fact to support his NEPA claims because the\n\nSouth Carolina owned property adjacent to the Savannah River Site. Id. “[T]he\n\nGovernor, in his official capacity, is essentially a neighboring landowner, whose property\n\nis at risk of environmental damage” as a result of the Department of Energy’s shipment\n\nof plutonium to the Savannah River Site and storage of that plutonium there, we\n\nexplained. Id.\n\n Here, unlike in Hodges, South Carolina does not argue that its injury, as a\n\nneighboring landowner, is attributable to the current storage of nuclear material at the\n\nSavannah River Site or the inadequacy of the Environmental Impact Statement pursuant\n\nto which the nuclear material is currently stored—a question that Hodges already\n\nresolved in the federal government’s favor. Id. at 446–49. Rather, South Carolina\n\ncontends it is injured because the termination of the MOX program renders it the\n\npermanent repository of the nuclear material when the Department of Energy has not\n\nissued an Environmental Impact Statement analyzing the environmental impact of the\n\nstorage of the material at the Savannah River Site beyond the year 2046, the year when\n\nthe existing Environmental Impact Statement’s analysis terminates, or, allegedly, satisfies\n\nits statutory obligations in terminating the MOX program. There is a meaningful\n\ndistinction between the alleged immediate environmental injuries associated with storing\n\nplutonium at the Savannah River Site, which were at issue in Hodges, and the alleged\n\n 17\n\ffuture adverse environmental impacts on South Carolina as a neighboring landowner if\n\nthe Department of Energy continues to store the plutonium at the Savannah River Site\n\ndecades in the future. That distinction is particularly meaningful because, as explained\n\nabove, numerous contingencies must occur in order for the plutonium to remain in South\n\nCarolina after 2046, the year when South Carolina’s alleged injury will mature.\n\n In sum, the single theory of injury3 that South Carolina relies on to support both of\n\nits claims is too speculative at this juncture to support Article III standing. The district\n\ncourt, therefore, was without jurisdiction to enter its preliminary injunction premised on\n\nthose two claims.\n\n B.\n\n For reasons similar to those that lead us to find that South Carolina lacks standing,\n\nwe also find that the two claims at issue fail on ripeness grounds. Like standing, the\n\nripeness doctrine “originates in the ‘case or controversy’ constraint of Article III.”\n\nScoggins v. Lee’s Crossing Homeowners Ass’n, 718 F.3d 262, 269 (4th Cir. 2013)\n\n(citations omitted). “Analyzing ripeness is similar to determining whether a party has\n\nstanding.” Miller v. Brown, 462 F.3d 312, 319 (4th Cir. 2006). “Although the phrasing\n\nmakes the questions of who may sue and when they sue seem distinct, in practice there is\n\nan obvious overlap between the doctrines of standing and ripeness.” Id. (quoting Erwin\n\n 3\n Because South Carolina has advanced only one theory of injury to support the\ntwo claims before this Court—that South Carolina is harmed by becoming the permanent\nrepository of weapons-grade nuclear material—we cannot and do not take any position\non whether other theories of injury would presently confer standing on South Carolina to\nsupport either of the two claims before us on appeal.\n\n\n 18\n\fChemerinsky, Federal Jurisdiction § 2.4 (4th ed. 2003). As with standing, ripeness is a\n\nquestion of subject matter jurisdiction. See Sansotta v. Town of Nags Head, 724 F.3d\n\n533, 548 (4th Cir. 2013) (citation omitted).\n\n The question of whether a claim is ripe “turns on the ‘fitness of the issues for\n\njudicial decision’ and the ‘hardship to the parties of withholding court consideration.’”\n\nPac. Gas & Elec. Co. v. State Energy Res. Conservation & Dev. Comm’n, 461 U.S. 190,\n\n201 (1983) (citation omitted). In the context of claims challenging agency actions, like\n\nthe two at issue, the purpose of the ripeness doctrine is “to prevent the courts, through\n\navoidance of premature adjudication, from entangling themselves in abstract\n\ndisagreements over administrative policies, and also to protect the agencies from judicial\n\ninterference until an administrative decision has been formalized and its effects felt in a\n\nconcrete way by the challenging parties.” Abbott Labs. v. Gardner, 387 U.S. 136, 148–\n\n49 (1967), abrogated on other grounds by Califano v. Sanders, 430 U.S. 99 (1977).\n\n To be fit for judicial review, a controversy should be presented in a “clean-cut and\n\nconcrete form.” Miller, 462 F.3d at 319 (citation omitted). This occurs when the action\n\nis “final and not dependent on future uncertainties or intervening agency rulings.”\n\nFranks v. Ross, 313 F.3d 184, 195 (4th Cir. 2002) (citation omitted). On the other hand,\n\njust as a plaintiff cannot assert standing based on an alleged injury that lies at the end of a\n\n“highly attenuated chain of possibilities,” Clapper, 568 U.S. at 410, a plaintiff’s claim is\n\nnot ripe for judicial review “if it rests upon contingent future events that may not occur as\n\nanticipated, or indeed may not occur at all.” Scoggins, 718 F.3d at 270 (quoting Texas v.\n\nUnited States, 523 U.S. 296, 300 (1998)).\n\n 19\n\f The two claims that South Carolina advances before this Court rest on the premise\n\nthat South Carolina will be the permanent repository of the weapons-grade nuclear\n\nmaterial currently stored at the Savannah River Site. But, numerous “contingent future\n\nevents,” id., must occur before South Carolina becomes the permanent repository of the\n\nnuclear material, see supra Part II.A. In particular, the Dilute and Dispose method must\n\nprove unworkable. The Department of Energy must fail to identify an alternative method\n\nof disposal and breach its commitment to dispose of the waste. And Congress or the\n\ncourts must set aside or refuse to enforce the statutory mechanisms currently in place to\n\nensure timely removal of the nuclear material. All of these “future uncertainties,”\n\nFranks, 313 F.3d at 195, lead us to conclude that the two claims at issue are not ripe for\n\nreview at this time—at least as presented by South Carolina. Accordingly, the ripeness\n\ndoctrine provides an additional basis for our holding that the district court was without\n\njurisdiction to enter the preliminary injunction.\n\n III.\n\n In sum, the only theory of injury advanced by South Carolina—that South\n\nCarolina will be the permanent repository of the nuclear material currently stored at the\n\nSavannah River Site—rests upon a “highly attenuated chain of possibilities,” Clapper,\n\n568 U.S. at 410, and “contingent future events that may not occur as anticipated, or\n\nindeed may not occur at all.” Scoggins, 718 F.3d at 270. In such circumstances, we must\n\nconclude that South Carolina lacks Article III standing to advance the two claims that\n\nserve as the basis of the district court’s injunction and that those two claims are not ripe\n\nfor review.\n\n 20\n\f That the two claims are not currently justiciable does not mean that they never will\n\nbe so. If uncertainty as to several links in the chain of possibilities is resolved, then\n\nSouth Carolina’s alleged injury may move from the speculative to the concrete, and\n\ntherefore the two claims also may become ripe for review. But until that uncertainty is\n\nlifted, the Constitution demands that we withhold judicial review.\n\n Accordingly, we vacate the preliminary injunction imposed by the district court\n\nand remand the case for further proceedings not inconsistent with this opinion.\n\n\n\n VACATED AND REMANDED\n\n\n\n\n 21", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356947/", "author_raw": "WYNN, Circuit Judge:"}]}
NIEMEYER
KING
WYNN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579694/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: State of SOUTH CAROLINA, Plaintiff - Appellee, v. UNITED STATES of America; United States Department of Energy; Rick Perry, in His Official Capacity as Secretary of Energy; National Nuclear Security Administration; Lisa E. Gordon-Hagerty, in Her Official Capacity as Administrator of the National Nuclear Security Administration and Undersecretary for Nuclear Security, Defendants - Appellants.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1684\n\n\nSTATE OF SOUTH CAROLINA,\n\n Plaintiff – Appellee,\n\nv.\n\nUNITED STATES OF AMERICA; UNITED STATES DEPARTMENT OF\nENERGY; RICK PERRY, in his official capacity as Secretary of Energy;\nNATIONAL NUCLEAR SECURITY ADMINISTRATION; LISA E. GORDON-\nHAGERTY, in her official capacity as Administrator of the National Nuclear\nSecurity Administration and Undersecretary for Nuclear Security,\n\n Defendants – Appellants.\n\n\n\nAppeal from the United States District Court for the District of South Carolina, at Aiken.\nJ. Michelle Childs, District Judge. (1:18-cv-01431-JMC)\n\n\nArgued: September 27, 2018 Decided: January 8, 2019\n\n\nBefore NIEMEYER, KING, and WYNN, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Wynn wrote the opinion, in which\nJudge Niemeyer and Judge King joined.\n\n\nARGUED: Andrew Alperin Rohrbach, UNITED STATES DEPARTMENT OF\nJUSTICE, Washington, D.C., for Appellants. Randolph R. Lowell, WILLOUGHBY &\nHOEFER, PA, Columbia, South Carolina, for Appellee. ON BRIEF: Chad A. Readler,\nActing Assistant Attorney General, Mark B. Stern, Daniel Tenny, Civil Division,\n\fUNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C.; Sherri A. Lydon,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Columbia,\nSouth Carolina, for Appellants.\n\n\n\n\n 2\n\fWYNN, Circuit Judge:\n\n The State of South Carolina brought this action to enjoin the United States of\n\nAmerica and other Defendants 1 (collectively, “the United States”) from terminating the\n\nconstruction of a mixed-oxide fuel nuclear processing facility located at the Savannah\n\nRiver Site in South Carolina. South Carolina alleges that the United States Department\n\nof Energy unlawfully failed to (1) prepare a supplemental Environmental Impact\n\nStatement analyzing the long-term storage of plutonium in the state; and (2) follow\n\nstatutory waiver provisions for terminating construction of the facility. We conclude that\n\nSouth Carolina has not established standing to pursue either of these claims.\n\nAccordingly, we vacate the preliminary injunction imposed by the district court.\n\n I.\n\n Following the collapse of the Soviet Union and the end of the Cold War, the\n\nUnited States of America and the Russian Federation began a worldwide nuclear\n\nnonproliferation effort that included developing plans for the safe disposition of nuclear\n\nweapons material. As part of this nonproliferation pact, the Department of Energy began\n\nstudying the effects of various nuclear waste storage and disposal strategies. In its initial\n\n1996 study, the Department of Energy prepared an Environmental Impact Statement in\n\naccordance with Section 4332 of the National Environmental Policy Act (“NEPA”), 42\n\n\n 1\n The other Defendants are the United States Department of Energy; Rick Perry, in\nhis official capacity as Secretary of Energy; the National Nuclear Security\nAdministration; and Lisa E. Gordon-Hagerty, in her official capacity as Administrator of\nthe National Nuclear Security Administration.\n\n\n 3\n\fU.S.C. § 4321 et seq., analyzing the potential environmental consequences associated\n\nwith the long-term storage of weapons-grade plutonium and highly enriched uranium\n\nprior to disposition. The Environmental Impact Statement addressed storage of these\n\nmaterials for a period of up to fifty years.\n\n Ultimately, the Department of Energy determined that the best approach to nuclear\n\nwaste disposal was a dual strategy involving (1) immobilization of a portion of the\n\nsurplus plutonium in glass or ceramic; and (2) irradiation of the remaining plutonium in\n\nmixed oxide fuel (the “MOX process”). Both strategies would convert the surplus\n\nnuclear material into forms that would meet the National Academy of Science’s Spent\n\nFuel Standard, meaning that the material would be “inaccessible and unattractive for\n\nweapons” use. J.A. 78.\n\n In 1997, the Department of Energy announced its intention to build a new mixed\n\noxide fuel fabrication facility (the “MOX facility”) to dispose of some of the nuclear\n\nmaterial using the MOX process. Following completion of a supplemental\n\nEnvironmental Impact Statement and a Record of Decision in January of 2000, the\n\nDepartment of Energy announced that the MOX facility would be located at the\n\nSavannah River Site along South Carolina’s border with Georgia. The facility’s original\n\nproduction goals included disposition of up to thirty-three metric tons of nuclear material\n\nusing the MOX process and immobilization of up to seventeen metric tons of additional\n\nnuclear material. As part of its supplemental Environmental Impact Statement, the\n\nDepartment of Energy continued to look at the environmental impacts of long-term\n\nplutonium storage.\n\n 4\n\f In 2002, the Department of Energy decided to drop the immobilization portion of\n\nthe disposition strategy, leaving the MOX process as the sole plutonium disposal method.\n\nThat same year, Congress directed the Secretary of Energy to submit a plan for the\n\nconstruction and operation of the MOX facility at the Savannah River site. Pub. L. No.\n\n107-314, § 3182 (2002), subsequently codified as 50 U.S.C. § 2566. Congress further\n\nauthorized the Secretary to take corrective actions if the construction timetable and\n\noperation schedule for the MOX facility were not being met. Additionally, Congress also\n\nrequired that in the event the MOX facility failed to achieve its production goals, the\n\nDepartment of Energy remove plutonium shipped to South Carolina for processing. See\n\n50 U.S.C. § 2566(c), § 2566(e). Finally, as part of its findings, Congress mentioned the\n\neconomic benefit that the MOX facility would bring to the State of South Carolina,\n\nnoting that the economic benefit would not be fully realized unless the facility was built.\n\nSee Pub. L. No. 107-314 at § 3181.\n\n Three years later, in 2005, the Department of Energy began transferring plutonium\n\nto the Savannah River Site for conversion, and in 2007, construction began on the MOX\n\nfacility. The original cost estimate for construction of the facility was $4.8 billion, with\n\ncompletion anticipated in 2016. And the original production goal estimate for the facility\n\nwas to have thirty-four metric tons of defense plutonium processed no later than January\n\n1, 2019. 50 U.S.C. § 2566(a)(2)(B).\n\n These original estimates proved grossly inaccurate due to delays and cost overruns\n\nin the construction of the MOX facility. The Department of Energy now estimates cost\n\n\n\n 5\n\ffor construction of the facility to be $17.17 billion, with completion now anticipated to be\n\nin 2048, over thirty years beyond the original estimated schedule.\n\n Since 2014, the Department of Energy has sought to terminate the MOX program\n\nand pursue an alternative method of plutonium disposal known as “Dilute and Dispose,”\n\nwhich it contends is less costly, faster, and safer. Under the Dilute and Dispose method,\n\nnuclear material would be “downblended” with inhibitor materials to reduce the\n\nplutonium content to less than ten percent by weight. Upon completion of the\n\ndownblending process, the material would then be shipped from the Savannah River Site\n\nto the Waste Isolation Pilot Plant near Carlsbad, New Mexico, for permanent disposal.\n\n Thus far, Congress has continued to fund construction of the MOX facility and\n\nhas, to date, restricted the Department of Energy from utilizing MOX-related\n\nappropriations to begin termination of the program. To that end, in 2017, Congress\n\nenacted a statute providing that the Secretary of Energy “shall carry out construction and\n\nproject support activities relating to the MOX facility.” Pub. L. 115-91, § 3121(a), 131\n\nStat. 1283, 1892.\n\n However, Section 3121(b) of that statute allows the Secretary of Energy to\n\ndiscontinue construction of the MOX facility if certain conditions have been met.\n\nSpecifically, the Secretary of Energy must submit to the Congressional defense\n\ncommittees:\n\n (A) the commitment of the Secretary [of Energy] to remove plutonium\n intended to be disposed of in the MOX facility from South Carolina\n and ensure a sustainable future for the Savannah River Site;\n\n (B) a certification that―\n\n 6\n\f (i) an alternative option for carrying out the plutonium disposition\n program for the same amount of plutonium as the amount of plutonium\n intended to be disposed of in the MOX facility exists, meeting the\n requirements of the Business Operating Procedure of the National\n Nuclear Security Administration entitled “Analysis of Alternatives” and\n dated March 14, 2016 (BOP-03.07); and\n\n (ii) the remaining lifecycle cost, determined in a manner comparable to\n the cost estimating and assessment best practices of the Government\n Accountability Office [“GAO”], as found in the document of the\n Government Accountability Office entitled “GAO Cost Estimating and\n Assessment Guide” (GAO-09-3SP), for the alternative option would be\n less than approximately half of the estimated remaining lifecycle costs\n of the mixed oxide fuel program; and\n\n (C) the details of any statutory or regulatory changes necessary to complete\n the alternative option.\n\n§ 3121(b)(1).\n\n Additionally, in exercising his authority to discontinue construction of the MOX\n\nfacility, the Secretary of Energy\n\n (1) shall concurrently submit to the Committees on Appropriations of both\n Houses of Congress the lifecycle cost estimate used to make the\n certification under section 3121(b) of such Act; and\n\n (2) may not use funds provided for the Project to eliminate such Project\n until the date that is 30 days after the submission of the lifecycle cost\n estimate required under paragraph (1).\n\nPub. L. No. 115-141, § 309(c), 132 Stat. 348, 530 (2018).\n\n Pursuant to these provisions, on May 10, 2018, the Secretary of Energy submitted\n\na letter to the Chairman of the House Armed Services Committee that purported to\n\nexecute the authority of the Secretary of Energy under Section 3121(b) to discontinue\n\nconstruction of the MOX facility. The Secretary of Energy certified, inter alia, that (1)\n\n\n 7\n\fthe Department of Energy is committed to removing plutonium from South Carolina; (2)\n\nan alternative option for carrying out the plutonium disposition, the Dilute and Dispose\n\nmethod, exists and has a lifecycle cost of less than approximately half of the remaining\n\nlifecycle cost for the MOX program; (3) the Department of Energy estimated the cost of\n\nthe Dilute and Dispose approach in a manner compatible with the best practices of the\n\nGAO; and (4) the Department of Energy is committed to ensuring a sustainable future for\n\nthe Savannah River Site. The Secretary of Energy further reported that the Department\n\nof Energy expected the total cost of disposition via the Dilute and Dispose method to be\n\n$19.9 billion, compared to $49.4 billion for the total cost of construction of the MOX\n\nfacility and conversion of all the plutonium into MOX fuel.\n\n In accordance with the Secretary of Energy’s letter, the Department of Energy and\n\nthe National Nuclear Security Administration issued a Partial Stop Work Order on May\n\n14, 2018, ending all new contracts and hiring related to the MOX program. The\n\nDepartment of Energy further indicated its intent to issue a Full Stop Work Order and\n\nbegin winding down the MOX program, including terminating employees currently\n\nworking on the project, on or about June 11, 2018.\n\n On May 25, 2018, before the Department of Energy issued a full stop work order,\n\nSouth Carolina brought this action in the United States District Court for the District of\n\nSouth Carolina and moved for a preliminary injunction barring the federal government\n\nfrom terminating the MOX program. In its complaint, South Carolina asserted that the\n\nUnited States (1) violated NEPA by failing to prepare a supplemental Environmental\n\nImpact Statement covering a period of more than fifty years and (2) failed to satisfy\n\n 8\n\fSection 3121(b) because of the alleged insufficiency of the Secretary of Energy’s\n\ncertifications. 2\n\n On June 7, 2018, the district court granted South Carolina’s motion for\n\npreliminary injunction. The district court first found that South Carolina had standing\n\ndue to environmental risks associated with long-term storage at the Savannah River Site,\n\nwhich abuts property owned by South Carolina. As to the merits, the district court held,\n\nin pertinent part, that South Carolina was likely to succeed on the merits of its NEPA\n\nclaim and its claim that the Secretary of Energy’s certifications were insufficient. The\n\ndistrict court further found that South Carolina would be irreparably harmed absent a\n\npreliminary injunction and that the balance of equities tilted in South Carolina’s favor.\n\nThus, the district court enjoined the federal government from ceasing construction of the\n\nMOX facility and issuing the full stop work order. The United States timely appealed.\n\n After careful review, we dispositively hold that South Carolina failed to establish\n\nstanding and therefore we do not reach the district court’s determination on the merits of\n\nthis matter.\n\n\n\n\n 2\n South Carolina further claimed that the United States violated 50 U.S.C. § 2567\nby failing to consult with the governor before deciding to terminate the MOX facility.\nThe district court held that South Carolina failed to establish that that claim was likely to\nsucceed on the merits, and therefore that claim is not before this Court.\n\n\n 9\n\f II.\n\n A.\n\n On appeal, the United States contends that the district court erred in concluding\n\nthat South Carolina established standing to pursue the two claims that serve as the basis\n\nof the district court’s preliminary injunction order—the NEPA claim and the claim\n\npremised on the alleged insufficiency of the Secretary’s certifications. The standing\n\ndoctrine derives from “the Constitution’s limitation on Article III courts’ power to\n\nadjudicate ‘cases and controversies.’” Frank Krasner Enters. v. Montgomery Cty., 401\n\nF.3d 230, 234 (4th Cir. 2005) (quoting Allen v. Wright, 468 U.S. 737, 750–51 (1984),\n\nabrogated on other grounds by Lexmark Intern., Inc. v. Static Control Components, Inc.,\n\n572 U.S. 118 (2014)). Standing implicates the court’s subject matter jurisdiction. Long\n\nTerm Care Partners, LLC v. United States, 516 F.3d 225, 230 (4th Cir. 2008).\n\n Here, South Carolina, as plaintiff, bears the burden of establishing standing to\n\nassert each of its claims. See id.; see also Lewis v. Casey, 518 U.S. 343, 359 n.6 (1996)\n\n(“[A] plaintiff who has been subject to injurious conduct of one kind [does not] possess\n\nby virtue of that injury the necessary stake in litigating conduct of another kind, although\n\nsimilar, to which he has not been subject.” (internal quotation marks omitted)). We\n\nreview the question of whether South Carolina possesses standing de novo. Frank\n\nKrasner Enters., 401 F.3d at 234.\n\n To establish Article III standing, “a plaintiff must show (1) it has suffered an\n\n‘injury in fact’ that is (a) concrete and particularized and (b) actual or imminent, not\n\nconjectural or hypothetical; (2) the injury is fairly traceable to the challenged action of\n\n 10\n\fthe defendant; and (3) it is likely, as opposed to merely speculative, that the injury will be\n\nredressed by a favorable decision.” Friends of the Earth, Inc. v. Laidlaw Envtl. Servs.\n\n(TOC), Inc., 528 U.S. 167, 180–81 (2000). The United States contends South Carolina\n\nfailed to show it has suffered an injury-in-fact sufficient to give rise to Article III\n\nstanding.\n\n To satisfy the injury-in-fact requirement, a plaintiff must establish a “realistic\n\ndanger of sustaining a direct injury.” Peterson v. Nat’l Telcoms. & Info. Admin., 478\n\nF.3d 626, 632 (4th Cir. 2007) (quoting Babbitt v. United Farm Workers Nat’l Union, 442\n\nU.S. 289, 298 (1979)). “[W]hile it is true ‘that threatened rather than actual injury can\n\nsatisfy Article III standing requirements,’ . . . not all threatened injuries constitute an\n\ninjury-in-fact.” Beck v. McDonald, 848 F.3d 262, 271 (4th Cir. 2017) (quoting Friends of\n\nthe Earth, Inc. v. Gaston Copper Recycling Corp., 204 F.3d 149, 160 (4th Cir. 2000) (en\n\nbanc)). “Rather, as the Supreme Court has ‘emphasized repeatedly,’ an injury-in-fact\n\n‘must be concrete in both a qualitative and temporal sense.’” Id. (quoting Whitmore v.\n\nArkansas, 495 U.S. 149, 155 (1990)). The requirement that an alleged injury be palpable\n\nand imminent ensures that the injury “is not too speculative for Article III purposes.” Id.\n\n(quoting Lujan v. Defenders of Wildlife, 504 U.S. 555, 564–65 n.2 (1992)).\n\n On appeal, South Carolina contends that it has suffered an injury-in-fact sufficient\n\nto support standing because “[South Carolina] is harmed by being rendered the\n\npermanent repository of weapons-grade plutonium as a result of [the Department of\n\nEnergy’s] decision to terminate the MOX Facility without first complying with NEPA or\n\nfollowing the congressional mandates of § 3121.” Appellee’s Br. at 15–16. According to\n\n 11\n\fSouth Carolina, this “results in increased radiation exposure to the public, increased risks\n\nof nuclear-related accidents, and an increased threat of action by rogue states or terrorists\n\nseeking to acquire weapons-grade plutonium.” Id. at 14. But this alleged injury is too\n\nspeculative and thus, does not give rise to a concrete injury-in-fact sufficient to support\n\neither of South Carolina’s claims.\n\n The Supreme Court has repeatedly held that an alleged harm is too “speculative”\n\nto support Article III standing when the harm lies at the end of a “highly attenuated chain\n\nof possibilities.” Clapper v. Amnesty Int’l USA, 568 U.S. 398, 410 (2013); see also, e.g.,\n\nBeck, 848 F.3d at 275 (holding that plaintiffs, who received treatment at a medical center\n\nthat suffered a data breach and alleged that they were at risk of experiencing identity\n\ntheft, failed to establish standing because their theory of injury rested on an “attenuated\n\nchain of possibilities”).\n\n Illustratively in Clapper, the Supreme Court considered a challenge to Section 702\n\nof the Foreign Intelligence Surveillance Act, which “authoriz[es] the surveillance of\n\nindividuals who are not ‘United States persons’ and are reasonably believed to be located\n\noutside the United States.” 568 U.S. at 401. The plaintiffs—a group of “attorneys and\n\nhuman rights, labor, legal, and media organizations”—alleged that their work demanded\n\nthat they “engage in sensitive international communication with individuals who they\n\nbelieve are likely targets of surveillance under” Section 702, rendering it reasonably\n\nlikely that the government would target and intercept the plaintiffs’ communications. Id.\n\nat 401, 406.\n\n\n\n 12\n\f The Supreme Court held that the plaintiffs failed to establish a concrete injury-in-\n\nfact based on the possibility that their communications would be intercepted, explaining\n\nthat a series of hypothetical events would have to occur before the government would\n\nintercept any particular plaintiff’s communications. Id. at 1148–50. The Court held that\n\namong other steps, the government would have to decide to invoke its Section 702\n\nauthority to target a non-U.S. person with whom a plaintiff communicated, a panel of\n\nfederal judges would have to “conclude that the Government’s proposed surveillance\n\nprocedures satisfy [the statute’s] many safeguards and are consistent with the Fourth\n\nAmendment,” and the government would have to succeed in intercepting one of the\n\ntarget’s communications with the plaintiff. Id. Thus, the Court held that that the “highly\n\nattenuated chain of possibilities, d[id] not satisfy the requirement that threatened injury\n\nmust be certainly impending.” Id. at 1148 (citation omitted).\n\n Applying Clapper, this Court reached a similar conclusion in Beck, in which a\n\nputative class of veterans who received medical treatment at a veterans’ medical center\n\nalleged that they had been injured when two sets of records were stolen from the center.\n\n848 F.3d at 262, 267. Although none of the named plaintiffs alleged any actual or\n\nattempted misuse of the personal information contained in their stolen records, they\n\nalleged that they suffered cognizable injuries-in-fact because they faced “(1) [an]\n\nincreased risk of future identity theft, and (2) the costs of protecting against the same.”\n\nId. at 273. We concluded that both alleged injuries were too speculative to confer\n\nstanding. Id. at 275–77. As to the alleged increased risk of identity theft, in particular,\n\nwe explained that plaintiffs’ theory of injury required us to “assume that the thie[ves]\n\n 13\n\ftargeted the stolen items for the personal information they contained” and that the thieves\n\nwould “then select, from thousands of others, the personal information of the named\n\nplaintiffs, and attempt successfully to use that information to steal their identities.” Id. at\n\n275. “This ‘attenuated chain’ cannot confer standing,” we held. Id. We likewise\n\nrejected the plaintiffs’ costs of mitigation theory of standing as a “repackaged” version of\n\ntheir first theory of standing, amounting to an effort to recoup “costs they incurred in\n\nresponse to a speculative threat.” Id. at 276 (emphasis added) (quoting Clapper, 568\n\nU.S. at 416).\n\n Here, South Carolina’s theory of standing—that it will become “the permanent\n\nrepository of weapons-grade plutonium” and all the environmental, health, and safety\n\nrisks that entails, Appellee’s Br. at 15–16—rests on a similarly “highly attenuated chain\n\nof possibilities,” Clapper, 568 U.S. at 410. Between now and 2046—when the analysis\n\nin the current Environmental Impact Statement governing the risks associated with long-\n\nterm storage of weapons-grade nuclear material at the Savannah River Site expires—the\n\nDepartment of Energy has twenty-eight years to identify an alternative method for\n\ndisposing of the nuclear material or otherwise removing it from South Carolina. The\n\nSecretary of Energy already has certified that one potential alternative to the MOX\n\nprogram exists, the Dilute and Dispose method. And the Department of Energy may\n\nidentify and develop other methods during that twenty-eight-year period. Or the\n\nDepartment of Energy may decide to transfer the plutonium out of South Carolina to\n\nanother location.\n\n\n\n 14\n\f Furthermore, Congress has put in place contingency plans for the removal of\n\nplutonium shipped to the Savannah River Site to forestall the indefinite storage of\n\nplutonium in South Carolina. A federal statute requires that, by 2022, all additional\n\nplutonium transferred into South Carolina to the MOX facility, but not processed, must\n\nbe removed. 50 U.S.C. § 2566(c)(2). Notably, because the Department of Energy\n\nalready has failed to meet certain statutory time limits for disposing of nuclear material at\n\nthe site, South Carolina has successfully brought suit pursuant to the Administrative\n\nProcedure Act to enforce these congressionally mandated deadlines via a mandatory\n\ninjunction. See id. § 2566(c)(1) (requiring removal of one metric ton of plutonium no\n\nlater than January 1, 2016); South Carolina v. United States, 243 F. Supp. 3d 673 (D.S.C.\n\n2017), aff’d, 907 F.3d 742 (4th Cir. 2018) (ordering the Department of Energy to remove\n\none metric ton of plutonium within two years).\n\n In sum, for South Carolina’s alleged injury—becoming “the permanent repository\n\nof weapons-grade plutonium,” Appellee’s Br. at 15–16—to occur: (1) the proposed\n\nDilute and Dispose method must fail; (2) the Department of Energy must fail to identify\n\nan alternative method for disposing of the nuclear material; and (3) the Department of\n\nEnergy must breach its statutory obligation to remove the nuclear material from South\n\nCarolina, Congress must repeal that obligation, or the courts must refuse to enforce that\n\nobligation. At this juncture, before the Department of Energy has even had an\n\nopportunity to finish analyzing the Dilute and Dispose method, this “chain of\n\npossibilities” is too speculative to give rise to a sufficiently concrete injury-in-fact.\n\n\n\n 15\n\f That several of the links in this “chain of possibilities” the State’s standing theory\n\ncontemplates require our coordinate branches to either breach or abandon their existing\n\ncommitments to ensure timely removal of the nuclear material at the Savannah River Site\n\nfurther weighs against treating the South Carolina’s alleged injury as conferring standing.\n\nAs Clapper recognized, the standing doctrine is “built on separation-of-powers\n\nprinciples” and “serves to prevent the judicial process from being used to usurp the\n\npowers of the political branches.” 568 U.S. at 408 (citations omitted); see also Allen v.\n\nWright, 468 U.S. at 752 (1984) (“[Article] III standing is built on a single basic idea—the\n\nidea of separation of powers.”). To confer standing on South Carolina at this juncture\n\nbased on an alleged injury—becoming the permanent repository of nuclear material—that\n\nthe political branches already have made written and legally binding commitments to\n\nforestall would improperly “usurp the powers of the political branches.” Clapper, 568\n\nU.S. at 408.\n\n The “highly attenuated chain of possibilities” that must occur for South Carolina\n\nto become the permanent repository of nuclear material also sets this case apart from this\n\nCourt’s decision in Hodges v. Abraham, 300 F.3d 432 (4th Cir. 2002), upon which South\n\nCarolina principally relies.\n\n Like the instant case, Hodges dealt with the storage of plutonium at the Savannah\n\nRiver Site. Id. at 436. In 2002, the Department of Energy issued a Record of Decision\n\nauthorizing the immediate shipment of six metric tons of plutonium from a nuclear\n\nfacility in Colorado to the Savannah River Site. Id. The Governor of South Carolina\n\nsought to enjoin shipment of the plutonium into South Carolina, alleging that the\n\n 16\n\fDepartment of Energy’s existing Environmental Impact Statement, and its supplemental\n\nanalyses to the Environmental Impact Statement, related to storage of plutonium at the\n\nSavannah River Site violated NEPA in several ways. Id. at 445. This Court held that the\n\nGovernor adequately alleged an injury-in-fact to support his NEPA claims because the\n\nSouth Carolina owned property adjacent to the Savannah River Site. Id. “[T]he\n\nGovernor, in his official capacity, is essentially a neighboring landowner, whose property\n\nis at risk of environmental damage” as a result of the Department of Energy’s shipment\n\nof plutonium to the Savannah River Site and storage of that plutonium there, we\n\nexplained. Id.\n\n Here, unlike in Hodges, South Carolina does not argue that its injury, as a\n\nneighboring landowner, is attributable to the current storage of nuclear material at the\n\nSavannah River Site or the inadequacy of the Environmental Impact Statement pursuant\n\nto which the nuclear material is currently stored—a question that Hodges already\n\nresolved in the federal government’s favor. Id. at 446–49. Rather, South Carolina\n\ncontends it is injured because the termination of the MOX program renders it the\n\npermanent repository of the nuclear material when the Department of Energy has not\n\nissued an Environmental Impact Statement analyzing the environmental impact of the\n\nstorage of the material at the Savannah River Site beyond the year 2046, the year when\n\nthe existing Environmental Impact Statement’s analysis terminates, or, allegedly, satisfies\n\nits statutory obligations in terminating the MOX program. There is a meaningful\n\ndistinction between the alleged immediate environmental injuries associated with storing\n\nplutonium at the Savannah River Site, which were at issue in Hodges, and the alleged\n\n 17\n\ffuture adverse environmental impacts on South Carolina as a neighboring landowner if\n\nthe Department of Energy continues to store the plutonium at the Savannah River Site\n\ndecades in the future. That distinction is particularly meaningful because, as explained\n\nabove, numerous contingencies must occur in order for the plutonium to remain in South\n\nCarolina after 2046, the year when South Carolina’s alleged injury will mature.\n\n In sum, the single theory of injury3 that South Carolina relies on to support both of\n\nits claims is too speculative at this juncture to support Article III standing. The district\n\ncourt, therefore, was without jurisdiction to enter its preliminary injunction premised on\n\nthose two claims.\n\n B.\n\n For reasons similar to those that lead us to find that South Carolina lacks standing,\n\nwe also find that the two claims at issue fail on ripeness grounds. Like standing, the\n\nripeness doctrine “originates in the ‘case or controversy’ constraint of Article III.”\n\nScoggins v. Lee’s Crossing Homeowners Ass’n, 718 F.3d 262, 269 (4th Cir. 2013)\n\n(citations omitted). “Analyzing ripeness is similar to determining whether a party has\n\nstanding.” Miller v. Brown, 462 F.3d 312, 319 (4th Cir. 2006). “Although the phrasing\n\nmakes the questions of who may sue and when they sue seem distinct, in practice there is\n\nan obvious overlap between the doctrines of standing and ripeness.” Id. (quoting Erwin\n\n 3\n Because South Carolina has advanced only one theory of injury to support the\ntwo claims before this Court—that South Carolina is harmed by becoming the permanent\nrepository of weapons-grade nuclear material—we cannot and do not take any position\non whether other theories of injury would presently confer standing on South Carolina to\nsupport either of the two claims before us on appeal.\n\n\n 18\n\fChemerinsky, Federal Jurisdiction § 2.4 (4th ed. 2003). As with standing, ripeness is a\n\nquestion of subject matter jurisdiction. See Sansotta v. Town of Nags Head, 724 F.3d\n\n533, 548 (4th Cir. 2013) (citation omitted).\n\n The question of whether a claim is ripe “turns on the ‘fitness of the issues for\n\njudicial decision’ and the ‘hardship to the parties of withholding court consideration.’”\n\nPac. Gas & Elec. Co. v. State Energy Res. Conservation & Dev. Comm’n, 461 U.S. 190,\n\n201 (1983) (citation omitted). In the context of claims challenging agency actions, like\n\nthe two at issue, the purpose of the ripeness doctrine is “to prevent the courts, through\n\navoidance of premature adjudication, from entangling themselves in abstract\n\ndisagreements over administrative policies, and also to protect the agencies from judicial\n\ninterference until an administrative decision has been formalized and its effects felt in a\n\nconcrete way by the challenging parties.” Abbott Labs. v. Gardner, 387 U.S. 136, 148–\n\n49 (1967), abrogated on other grounds by Califano v. Sanders, 430 U.S. 99 (1977).\n\n To be fit for judicial review, a controversy should be presented in a “clean-cut and\n\nconcrete form.” Miller, 462 F.3d at 319 (citation omitted). This occurs when the action\n\nis “final and not dependent on future uncertainties or intervening agency rulings.”\n\nFranks v. Ross, 313 F.3d 184, 195 (4th Cir. 2002) (citation omitted). On the other hand,\n\njust as a plaintiff cannot assert standing based on an alleged injury that lies at the end of a\n\n“highly attenuated chain of possibilities,” Clapper, 568 U.S. at 410, a plaintiff’s claim is\n\nnot ripe for judicial review “if it rests upon contingent future events that may not occur as\n\nanticipated, or indeed may not occur at all.” Scoggins, 718 F.3d at 270 (quoting Texas v.\n\nUnited States, 523 U.S. 296, 300 (1998)).\n\n 19\n\f The two claims that South Carolina advances before this Court rest on the premise\n\nthat South Carolina will be the permanent repository of the weapons-grade nuclear\n\nmaterial currently stored at the Savannah River Site. But, numerous “contingent future\n\nevents,” id., must occur before South Carolina becomes the permanent repository of the\n\nnuclear material, see supra Part II.A. In particular, the Dilute and Dispose method must\n\nprove unworkable. The Department of Energy must fail to identify an alternative method\n\nof disposal and breach its commitment to dispose of the waste. And Congress or the\n\ncourts must set aside or refuse to enforce the statutory mechanisms currently in place to\n\nensure timely removal of the nuclear material. All of these “future uncertainties,”\n\nFranks, 313 F.3d at 195, lead us to conclude that the two claims at issue are not ripe for\n\nreview at this time—at least as presented by South Carolina. Accordingly, the ripeness\n\ndoctrine provides an additional basis for our holding that the district court was without\n\njurisdiction to enter the preliminary injunction.\n\n III.\n\n In sum, the only theory of injury advanced by South Carolina—that South\n\nCarolina will be the permanent repository of the nuclear material currently stored at the\n\nSavannah River Site—rests upon a “highly attenuated chain of possibilities,” Clapper,\n\n568 U.S. at 410, and “contingent future events that may not occur as anticipated, or\n\nindeed may not occur at all.” Scoggins, 718 F.3d at 270. In such circumstances, we must\n\nconclude that South Carolina lacks Article III standing to advance the two claims that\n\nserve as the basis of the district court’s injunction and that those two claims are not ripe\n\nfor review.\n\n 20\n\f That the two claims are not currently justiciable does not mean that they never will\n\nbe so. If uncertainty as to several links in the chain of possibilities is resolved, then\n\nSouth Carolina’s alleged injury may move from the speculative to the concrete, and\n\ntherefore the two claims also may become ripe for review. But until that uncertainty is\n\nlifted, the Constitution demands that we withhold judicial review.\n\n Accordingly, we vacate the preliminary injunction imposed by the district court\n\nand remand the case for further proceedings not inconsistent with this opinion.\n\n\n\n VACATED AND REMANDED\n\n\n\n\n 21\n[END_CASE]", "role": "user" } ]
4,579,697
Fenyang Ajamu STEWART, Plaintiff - Appellant, v. Andrei IANCU, Defendant - Appellee.
Fenyang Stewart v. Andrei Iancu
2019-01-08
17-1815
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Motz, Wynn", "parties": "", "opinions": [{"author": "WYNN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-1815\n\n\nFENYANG AJAMU STEWART,\n\n Plaintiff - Appellant,\n\n v.\n\nANDREI IANCU,\n\n Defendant - Appellee.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Leonie M. Brinkema, District Judge. (1:16-cv-00213-LMB-JFA)\n\n\nArgued: October 30, 2018 Decided: January 8, 2019\n\n\nBefore GREGORY, Chief Judge, MOTZ and WYNN, Circuit Judges.\n\n\nReversed and remanded by published opinion. Judge Wynn wrote the opinion, in which\nChief Judge Gregory and Judge Motz joined.\n\n\nARGUED: Kevin Spencer Elliker, HUNTON ANDREWS KURTH LLP, Richmond,\nVirginia, for Appellant. Dennis Carl Barghaan, Jr., OFFICE OF THE UNITED STATES\nATTORNEY, Alexandria, Virginia, for Appellee. ON BRIEF: G. Zachary Terwilliger,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Alexandria,\nVirginia, for Appellee.\n\fWYNN, Circuit Judge:\n\n This appeal arises from the district court’s determination that Fenyang Ajamu\n\nStewart (“Stewart”) is required to wait longer than 180 days to commence a civil action\n\nunder Title VII and the Rehabilitation Act after amending his initial administrative\n\ncomplaint before the relevant agency. But the text of Title VII, as well as the legislative\n\ncontext and purpose, plainly states that a claimant may commence a civil action 180 days\n\nfrom “the filing of the initial charge.” 42 U.S.C. § 2000e-16(c) (emphasis added). We,\n\ntherefore, reverse the district court and remand for further proceedings.\n\n I.\n\n Stewart worked as a patent examiner for the U.S. Patent and Trademark Office\n\n(“PTO”). He suffers from bulging discs in his lower back and radiculopathy, resulting\n\nfrom compression of his sciatic nerve, as well as post- and continuous-traumatic stress\n\ndisorder. Because of these medical conditions, Stewart filed a reasonable\n\naccommodation request with the PTO in April 2014. Specifically, he requested that he\n\nnot be required to (1) come into work at a specified, mandatory time; (2) report his work\n\nschedule to his supervisor; and (3) schedule his meetings before 12:00 p.m., as his pain\n\nmedications caused morning grogginess. In addition, Stewart requested an ergonomic\n\nchair and keyboard, a standing desk, and a foot stool.\n\n On September 19, 2014, the PTO granted Stewart’s requests for the keyboard,\n\nstanding desk, and foot stool. Stewart had already received an ergonomic chair by that\n\npoint. Regarding his work schedule, the PTO determined that Stewart was already on the\n\nIncreased Flexitime Program work schedule, which permitted him sufficient flexibility to\n\n\n 2\n\f“work around any difficulties” and that Stewart’s supervisor, when possible, would\n\nschedule meetings specifically designed for Stewart after 12:00 pm. However, the PTO\n\ndenied Stewart’s request not to report his work schedule to his supervisor, as such a\n\nrequest would unduly burden his supervisor and the agency’s ability to oversee and\n\nadminister Stewart’s work.\n\n Stewart filed a formal complaint with the PTO’s Office of Equal Employment\n\nOpportunity and Diversity on July 14, 2015, challenging the PTO’s denial of his request\n\nfor accommodations, asserting a hostile work environment and discrimination, and\n\nalleging various claims of retaliation. Stewart amended this administrative complaint\n\neight times. After each of these amendments, the PTO’s Office of Equal Employment\n\nOpportunity and Diversity responded with a notice advising Stewart that (1) he may\n\namend his formal complaint at any time before the investigation is complete, and any\n\nnew claims “must be like or related to the claims raised” in the original complaint; and\n\n(2) he may “file a civil action in an appropriate United States District Court at any time\n\nafter 180 days have passed from the date [he] filed [his] original complaint. 29 C.F.R. §\n\n1614.407(b).” J.A. 114.\n\n On February 29, 2016—more than 180 days after the filing of his original\n\nadministrative complaint, but less than 180 days after the filing of several of the\n\namendments—Stewart filed pro se a civil action in the District Court for the Eastern\n\nDistrict of Virginia, alleging numerous violations of the Rehabilitation Act of 1973, 29\n\nU.S.C. § 701 et seq., and Title VII of the Civil Rights Act of 1964, 42 U.S.C. § 2000e et\n\nseq. Stewart’s claims rested on the PTO’s alleged failure to accommodate his\n\n\n 3\n\fdisabilities; a hostile work environment; reprisal for participating in protected Equal\n\nEmployment Opportunity activity; disparate treatment discrimination on the basis of\n\ndisability and failure to accommodate; and retaliation for requesting reasonable\n\naccommodation. Stewart later amended the complaint in April 2016, adding two counts.\n\n The PTO filed a motion to dismiss, arguing that Stewart’s suit was premature\n\nunder both 42 U.S.C. § 2000e-16(c) and 29 C.F.R. § 1614.407(b) because he had not\n\nexhausted his administrative remedies. According to the PTO, Stewart was required to\n\nwait to file a civil action until the conclusion of the agency’s investigation period. That\n\ninvestigation period is extended when employees amend their administrative complaint to\n\nthe earlier of 180 days after the last amendment or 360 days after the filing of the initial\n\ncomplaint. 29 C.F.R. §§ 1614.106(e)(2); 1614.108(f).\n\n On March 17, 2017, the district court dismissed Stewart’s case without prejudice\n\nfor lack of subject matter jurisdiction. The district court held that Stewart had failed to\n\nexhaust his administrative remedies because under Section 1614.407(b), he was required\n\nto wait until July 8, 2016, the earlier of 180 days after Stewart’s last amendment or 360\n\ndays after the filing of his initial complaint, to file a civil action in federal court. Stewart\n\ntimely appealed the district court’s decision.\n\n II.\n\n A.\n\n Stewart alleges violations of both the Rehabilitation Act and Title VII.\n\nRehabilitation Act claims “must comply with the same administrative procedures that\n\ngovern federal employee Title VII claims.” Wilkinson v. Rumsfeld, 100 F. App’x 155,\n\n\n 4\n\f157 (4th Cir. 2004). Section 717, codified at 42 U.S.C. § 2000e-16, amended Title VII to\n\npermit federal employees to file a civil action for employment discrimination under\n\ncertain circumstances. Federal employees may file a civil action based upon their\n\nadministrative complaint (1) within 90 days of receipt of notice of final agency action or\n\n(2) after 180 days from “the filing of the initial charge” with the agency, if there has been\n\nno final agency action on the complaint.\n\n In addition to 42 U.S.C. § 2000e-16, federal regulations govern the process for\n\nfiling a civil action based on employment discrimination. Congress has delegated to the\n\nEqual Employment Opportunity Commission (“EEOC”) the authority to promulgate\n\nregulations to implement Title VII. E.E.O.C. v. Randstad, 685 F.3d 433, 444 (4th Cir.\n\n2012). Accordingly, the EEOC has enacted regulations regarding individuals’ ability to\n\n(1) amend their administrative complaint and (2) file suit in federal court under Title VII.\n\nThese regulations reinforce Section 2000e-16. A federal employee may amend a\n\ncomplaint “at any time prior to the conclusion of the investigation to include issues or\n\nclaims like or related to those raised in the complaint.” 29 C.F.R. § 1614.106(d).\n\nEchoing the language of 42 U.S.C. § 2000e-16(c), the EEOC’s regulations also state that\n\nfederal employees seeking relief under Title VII and the Rehabilitation Act may file a\n\ncivil action in federal district court “[a]fter 180 days from the date of filing an individual\n\nor class complaint if an appeal has not been filed and final action has not been taken.” 29\n\nC.F.R. § 1614.407(b).\n\n\n\n\n 5\n\f B.\n\n We begin with the threshold question of whether Title VII’s 180-day waiting\n\nperiod found in Section 2000e-16(c) is a jurisdictional bar, a question of first impression\n\nin this circuit. 1 Although the PTO filed its motion to dismiss under Fed. R. Civ. P.\n\n12(b)(6), the district court dismissed Stewart’s case under Fed. R. Civ. P. 12(b)(1) for\n\nlack of subject-matter jurisdiction, stating that the “administrative exhaustion\n\nrequirements for the Rehabilitation Act and Title VII claims are jurisdictional,” and\n\nStewart failed to exhaust his administrative remedies. J.A. 234 n.4. For the following\n\nreasons, we conclude that the district court incorrectly held that Section 2000e-16(c)’s\n\n180-day waiting period is jurisdictional.\n\n Title VII directs federal employees to exhaust administrative remedies before\n\nfiling suit. Pueschel v. United States, 369 F.3d 345, 353 (4th Cir. 2004). Requiring\n\nexhaustion of administrative remedies serves twin objectives: protecting agency authority\n\n\n 1\n We have previously treated certain Title VII exhaustion requirements as\njurisdictional—for example, filing a charge of discrimination with the EEOC, see Jones\nv. Calvert Grp., Ltd., 551 F.3d 297, 300 (4th Cir. 2009)—but have never considered\nwhether the 180-day waiting period in Section 2000e-16(c) is a jurisdictional\nprerequisite. We also recognize that circuits have split on whether the failure to exhaust\nadministrative remedies under Title VII, broadly conceived, is a jurisdictional\nrequirement. Again, however, none of these cases implicate the mandatory 180-day\nwaiting period in Section 2000e-16(c) that is before us in this case. Compare Peppers v.\nCobb Cty., 835 F.3d 1289, 1296–97 (11th Cir. 2016) (treating the administrative\nexhaustion requirement as a jurisdictional prerequisite to filing a Title VII action), with\nFowlkes v. Ironworkers Local 40, 790 F.3d 378, 385 (2d Cir. 2015) (holding that the\nfailure to exhaust administrative remedies does not raise a jurisdictional bar); Artis v.\nBernanke, 630 F.3d 1031, 1034 n.4 (D.C. Cir. 2011) (same); Frederique-Alexandre v.\nDep’t of Nat. & Envtl. Res. of Puerto Rico, 478 F.3d 433, 440 (1st Cir. 2007) (same).\n\n\n\n 6\n\fin the administrative process and “promot[ing] efficiency” in the resolution of claims.\n\nWoodford v. Ngo, 548 U.S. 81, 89 (2006). By avoiding the “premature interruption of the\n\nadministrative process,” exhaustion requirements ensure that agencies are provided the\n\nfirst opportunity to “exercise [] discretion” or “apply [] expertise.” McKart v. United\n\nStates, 395 U.S. 185, 193–94 (1969). The 180-day waiting period serves these purposes:\n\nit ensures that the employer is “put on notice of the alleged violations” to facilitate out-\n\nof-court resolution and permits sufficient, but finite, time for the agency to address the\n\ndiscrimination charges in the first instance. Miles v. Dell, Inc., 429 F.3d 480, 491 (4th\n\nCir. 2005). Indeed, courts have regularly characterized Section 2000e-16(c)’s 180-day\n\nwaiting period as an exhaustion requirement. See Murthy v. Vilsack, 609 F.3d 460, 465\n\n(D.C. Cir. 2010); Brown v. Snow, 440 F.3d 1259, 1263 (11th Cir. 2006).\n\n However, it bears noting that the 180-day waiting period also is not a paradigmatic\n\nexhaustion requirement. Unlike most administrative exhaustion requirements premised\n\non agency action, after which injured parties may “seek review of an adverse decision\n\nand obtain a remedy” if warranted, the 180-day waiting period is satisfied by agency\n\ninaction. Darby v. Cisneros, 509 U.S. 137, 144 (1993) (citation omitted). Indeed,\n\nCongress passed Section 2000e-16(c) of Title VII in 1972 precisely because of its\n\nrecognition that federal employees frequently encountered an “administrative quagmire”\n\nin filing charges of discrimination. H.R. Rep. 92–238, at 12 (June 2, 1971). The 180-day\n\nwaiting period therefore “confines agencies and the EEOC to a tight schedule” and\n\nsignals congressional recognition that “the doctrine of exhaustion of remedies . . . had\n\nbecome [a] barrier to meaningful court review.” Wilson v. Pena, 79 F.3d 154, 167 (D.C.\n\n\n 7\n\fCir. 1996) (quoting Grubbs v. Butz, 514 F.2d 1323, 1328 (D.C. Cir. 1975)). In light of\n\nthis legislative context, the 180-day waiting period functions more like a mandatory\n\nprocedural hurdle for litigants than an affirmative agency step potentially giving rise to a\n\nremedy on review.\n\n This distinction informs our consideration of whether Section 2000e-16(c)’s 180-\n\nday waiting period requirement is also a jurisdictional requirement. Not all exhaustion\n\nrequirements are jurisdictional. Rather, we have recognized that certain exhaustion\n\nrequirements may be jurisdictional while others are not. For example, in Davis v. North\n\nCarolina Department of Correction, we specifically distinguished one exhaustion\n\nrequirement as jurisdictional—the entitlement to a right-to-sue letter from the EEOC—\n\nfrom Title VII’s “timely filing requirements,” which the Supreme Court has held are not\n\njurisdictional. 48 F.3d 134, 140 (4th Cir. 1995) (citing Zipes v. Trans World Airlines,\n\nInc., 455 U.S. 385, 393 (1982)); see also Laber v. Harvey, 438 F.3d 404, 429 n.25 (4th\n\nCir. 2006) (concluding that the 90-day time limit set forth in 42 U.S.C. § 2000e–16(c) is\n\nnot a jurisdictional requirement).\n\n In recent years, the Supreme Court repeatedly has cautioned courts not to\n\n“confuse[] or conflate[]” subject-matter jurisdiction, on the one hand, with the “essential\n\ningredients of a federal claim for relief,” on the other. Arbaugh v. Y & H Corp., 546 U.S.\n\n500, 503 (2006). Applying this distinction, the Supreme Court has differentiated between\n\nnon-jurisdictional “claim-processing” rules and jurisdictional rules that govern a court’s\n\nadjudicatory authority. Kontrick v. Ryan, 540 U.S. 443, 456 (2004); see also Gonzalez v.\n\nThaler, 565 U.S. 134, 141 (2012) (pressing a “stricter distinction” between these two\n\n\n 8\n\fcategories of rules). In particular, the Supreme Court has clarified that most time bars are\n\n“quintessential claim-processing rules,” which “promote the orderly progress of litigation\n\nby requiring that the parties take certain procedural steps at certain specified times.”\n\nHenderson v. Shinseki, 562 U.S. 428, 435 (2011) (holding that a statute requiring filing of\n\nnotice of appeal within 180 days of administrative decision constituted a “claim-\n\nprocessing rule” and therefore was not jurisdictional). Such rules do not strip a court of\n\njudicial authority to hear a case, even when the time limits are “framed in mandatory\n\nterms.” United States v. Kwai Fun Wong, 135 S. Ct. 1625, 1632 (2015) (holding that\n\ncertain timely filing provisions in the Federal Torts Claims Act were not jurisdictional).\n\n Instead, the Supreme Court has established a clear statement rule for\n\ndetermining whether procedural rules, including time bars, are jurisdictional. Only if the\n\nstatutory text “plainly show[s] that Congress imbued a procedural bar with jurisdictional\n\nconsequences” should a court treat a rule as jurisdictional. Id. Put otherwise, Congress\n\nmust explicitly “tag” a procedural bar “as jurisdictional.” Id. In conducting this clear\n\nstatement inquiry, the Supreme Court has looked to several factors, including the\n\nstatutory text (if it speaks in “jurisdictional terms”); the placement of the rule (if it is\n\nlocated in the jurisdiction-granting provision of the statute); and legislative context.\n\nHenderson, 562 U.S. at 438.\n\n Here, Congress has done nothing to “tag” as jurisdictional the 180-day waiting\n\nperiod. The text of Section 2000e-16(c) addresses only the timeliness of claims; it does\n\nnot refer to the district courts’ “authority to hear untimely suits.” Kwai Fun Wong, 135 S.\n\nCt. 1625, 1628 (2015). Much like the filing deadline at issue in Henderson, Section\n\n\n 9\n\f2000e-16(c) does not contain “jurisdictional language”—language dictating that judicial\n\nreview be obtained within a prescribed time and manner before a particular court.\n\nHenderson, 562 U.S. at 438. Simply because the 180-day waiting period is “cast in\n\nmandatory language” does not render it jurisdictional. Id. at 439.\n\n In addition, Section 2000e-16(c)’s placement within Title VII is distinct from\n\nthose provisions pertaining to jurisdiction. Section 2000e-16(c), titled “Employment by\n\nFederal Government,” lays out the respective 90-day filing period and 180-day waiting\n\nperiods before stating that the federal employee “may file a civil action as provided in\n\nsection 2000e-5.” 42 U.S.C. § 2000e-16(c) (emphasis added). Section 2000e-5, titled\n\n“Enforcement provisions,” mandates that federal district courts “shall have jurisdiction of\n\nactions brought under this subchapter.” 42 U.S.C. § 2000e-5(f)(3). These statutory\n\nsections serve different functions: on the one hand, Section 2000e-16(c) extends Title VII\n\nprotections to federal employees, and on the other, Section 2000e-5, as the enforcement\n\nprovision, prescribes jurisdictional requirements. Nothing “conditions the jurisdictional\n\ngrant [in Section 2000e-5(f)(3)] on the limitations periods [in Section 2000e-16(c)], or\n\notherwise links those separate provisions.” Kwai Fun Wong, 135 S. Ct. at 1633; see also\n\nGad v. Kansas State Univ., 787 F.3d 1032, 1038 (10th Cir. 2015) (noting that “a Title VII\n\nstatutory requirement’s classification as jurisdictional or non-jurisdictional turns in large\n\npart on whether it is located in Title VII’s jurisdictional subsection—42 U.S.C. § 2000e-\n\n5(f)(3)). This division further supports a conclusion that the 180-day waiting period is\n\nnot a jurisdictional requirement but rather a “prudential prerequisite to suit,” Davis v.\n\n\n\n\n 10\n\fFort Bend Cty., 893 F.3d 300, 305 (5th Cir. 2018), or “statutory precondition,” Vinieratos\n\nv. U.S. Dep’t of Air Force, 939 F.2d 762, 768 n.5 (9th Cir. 1991).\n\n In considering this issue, we emphasize the subtle, but important, distinction\n\nbetween those exhaustion requirements that operate as a jurisdictional bar and those that\n\nmerely function as a statutory prerequisite to filing suit under Title VII. See Vinieratos,\n\n939 F.2d at 768 n.5 (9th Cir. 1991). Because we conclude that Section 2000e-16(c)’s\n\n180-day waiting period is akin to a “claim-processing” rule that imposes procedural\n\nobligations on litigants, rather than implicates judicial authority to hear a class of cases,\n\nwe hold that the 180-day waiting period is not jurisdictional.\n\n Our holding also prevents the “drastic” consequences of treating a procedural rule\n\nas jurisdictional—consequences that “alter[] the normal operation of our adversarial\n\nsystem.” Henderson, 562 U.S. at 434. Jurisdictional defects can be raised at any time by\n\nthe parties or sua sponte by the courts, even post-judgment, which may result in the\n\n“waste of judicial resources and may unfairly prejudice litigants.” Id. Because of the\n\ngravity of a jurisdictional label, the Supreme Court has repeatedly and explicitly\n\ndemanded “discipline” in this inquiry. Id. at 435.\n\n To be clear, we do not hold that all exhaustion requirements set forth in Title VII\n\nare non-jurisdictional. Rather, whether a particular exhaustion requirement—in Title VII\n\nor any other statute—is jurisdictional turns on the statutory language and purpose of the\n\nexhaustion provision at issue. Here, Section 2000e-16(c) includes no language clearly\n\nindicating that Congress intended for the provision to serve as a jurisdictional bar.\n\nFurther, in practice, Section 2000e-16(c)’s 180-day waiting period functions more closely\n\n\n 11\n\fas a “time prescription,” which imposes a mandatory obligation on litigants but does not\n\ngovern a court’s jurisdiction. Arbaugh, 546 U.S. at 510; see also Stroy v. Gibson, 896\n\nF.3d 693, 698 (5th Cir. 2018) (treating Section 2000e-16(c)’s 180-day waiting period as a\n\n“precondition to filing suit,” not a jurisdictional requirement).\n\n Accordingly, the district court erred in dismissing this case under Federal Rule of\n\nCivil Procedure 12(b)(1). Instead, it should have considered the 180-day waiting period\n\nas a non-jurisdictional rule and decided the case under Federal Rule of Civil Procedure\n\n12(b)(6).\n\n III.\n\n A.\n\n Having determined that Section 2000e-16(c)’s 180-day waiting period is not\n\njurisdictional, we now turn to whether the district court erred in dismissing Stewart’s\n\naction under that provision. “We review de novo the grant of a motion to dismiss for\n\nfailure to state a claim [under Rule 12(b)(6)]. In so doing, we must accept as true all of\n\nthe factual allegations contained in the complaint.” Gerner v. Cty. of Chesterfield, Va.,\n\n674 F.3d 264, 266 (4th Cir. 2012) (citation omitted).\n\n Stewart’s appeal requires us to construe the statutory language of Section 2000e-\n\n16(c), and that provision’s 180-day waiting period, in particular. When construing a\n\nstatute, we “first and foremost strive to implement congressional intent by examining the\n\nplain language.” Minor v. Bostwick Laboratories, Inc., 669 F.3d 428 (4th Cir. 2012)\n\n(citation omitted). “[U]nless otherwise defined, words will be interpreted as taking their\n\nordinary, contemporary, common meaning.” Kennedy v. St. Joseph’s Ministries, Inc.,\n\n\n 12\n\f657 F.3d 189, 192 (4th Cir. 2011) (citation omitted). In interpreting the plain language of\n\nthe statute, we also look to “the specific context in which the language is used, and the\n\nbroader context of the statute as a whole,” Minor, 669 F.3d at 434–35 (citations omitted),\n\nas well as a statute’s legislative history as additional evidence of congressional intent,\n\nElm Grove Coal Co. v. Director, O.W.C.P., 480 F.3d 278, 293 (4th Cir. 2007). Here,\n\neach of these factors indicates that Stewart’s amendments of his complaint did not restart\n\nthe 180-day clock.\n\n We begin with the plain language of the statute. In relevant part, Section 2000e-\n\n16(c) permits aggrieved federal employees to file a civil action 180 days “from the filing\n\nof the initial charge with the department, agency, or unit” if the agency has “fail[ed] to\n\ntake final action on his complaint.” 42 U.S.C. § 2000e-16(c) (emphasis added). Given\n\nthe ordinary meaning of the word “initial,” Section 2000e-16(c) requires that the 180-day\n\nwaiting period begin upon the filing of the first, original charge. See Webster’s Third\n\nNew Int’l Dictionary 1163 (3d ed. 1976) (defining “initial” as “of or relating to the\n\nbeginning; marking the commencement”); American Heritage Dictionary of the English\n\nLanguage 902 (4th ed. 2009) (defining “initial” as “of, relating to, or occurring at the\n\nbeginning; first”). Therefore, in Stewart’s case, the 180-day waiting period began on July\n\n14, 2015, the date he filed his “initial,” formal administrative complaint of discrimination\n\nand retaliation before the PTO’s Office of Equal Employment and Diversity.\n\n The statute’s use of the modifier “initial” also implicitly allows for the possibility\n\nof subsequent amendments—that there may well be additional “charge[s]” that follow the\n\n“initial charge.” Accordingly, the 180-day waiting period does not reset upon subsequent\n\n\n 13\n\famendments to the administrative complaint. Had Congress not contemplated the\n\npossibility of amendments to the complaint, there would have been no reason to use the\n\nword “initial.” See Alaska Dep’t of Envtl. Conservation v. E.P.A., 540 U.S. 461, 489 n.13\n\n(2004) (observing it is “a cardinal principle of statutory construction that a statute ought,\n\nupon the whole, to be so construed that, if it can be prevented, no clause, sentence, or\n\nword shall be superfluous, void, or insignificant”) (citations and alterations omitted).\n\nTherefore, we hold that upon the passage of 180 days from the filing of the original\n\ncomplaint, and absent agency final action on the complaint, federal employees may file a\n\ncivil action, regardless of subsequent amendments to that complaint. 2\n\n Turning to the legislative context, Congress passed Section 2000e-16(c) of Title\n\nVII in 1972 because of its recognition that aggrieved federal employees did not have\n\nsufficient access to the courts under Title VII. S. Rep. 92–415 at 16 (1971). Before the\n\n1972 Act, the “effective availability of either administrative or judicial relief” for federal\n\nemployees was uncertain. Brown v. General Servs. Admin., 425 U.S. 820, 825 (1976).\n\nFederal employees often faced an “administrative quagmire” in which parties had to wait\n\nseveral years in the overburdened administrative process. H.R. Rep. 92–238, at 12 (June\n\n\n 2\n In an unpublished per curiam opinion, we summarily affirmed a district court’s\nholding that federal employees must wait beyond the 180-day period when they amend\ntheir complaints. Laber v. Harvey, No. 1:05-cv-00803-CMH, 2005 WL 3008510, at *1\n(E.D. Va. Nov. 7, 2005), aff’d, 204 F. App’x 332 (4th Cir. 2006). We are not bound by\nthat opinion, which is devoid of reasoning. See Collins v. Pond Creek Mining Co., 468\nF.3d 213, 219 (4th Cir. 2006) (noting that “we ordinarily do not accord precedential value\nto our unpublished decisions” and they are “entitled only to the weight they generate by\nthe persuasiveness of their reasoning”) (citation omitted).\n\n\n\n 14\n\f2, 1971). Ensuring that federal employees had “access to the courts” therefore drove the\n\npassage of Section 2000e-16(c). S. Rep. No. 92–415, at 16 (1971). The 180-day waiting\n\nperiod directly serves that end. In discussing Section 2000e-16(c)’s 180-day waiting\n\nprovision in the context of EEOC inaction, the D.C. Circuit observed that:\n\n The 180 day [waiting period] provision represents a Congressional\n determination that providing prompt access to the courts in discrimination\n disputes is so important that the administrative process will be given only a\n finite time to deal alone with a given dispute. Indeed, the Act is in part a\n response to Congressional realization that “the doctrine of exhaustion of\n remedies . . . had become [a] barrier to meaningful court review.”\n\nWilson, 79 F.3d at 167 (quoting Grubbs, 514 F.2d at 1328). Allowing agencies to\n\nrepeatedly delay individuals’ ability to go to court, simply because they have amended\n\ntheir administrative complaints, would frustrate a “congressional policy to make the\n\ncourts the final tribunal for the resolution of controversies over charges of discrimination\n\nafter all administrative remedies have been exhausted.” Koger v. Ball, 497 F.2d 702, 706\n\n(4th Cir. 1974). Although Section 2000e-16(c) “provides for a careful blend of\n\nadministrative and judicial enforcement powers,” we cannot overlook that, in passing the\n\nprovision, Congress intended federal employees to have a robust judicial remedy, and\n\nready access to the courts, for employment discrimination claims. Brown, 425 U.S. at\n\n833\n\n Our conclusion also comports with the broader purpose of Title VII as a “remedial\n\nscheme in which laypersons, rather than lawyers, are expected to initiate the process.”\n\nSydnor, 681 F.3d at 594 (citation omitted); see also Alvarado v. Board of Trustees of\n\nMontgomery Community College, 848 F.2d 457, 460 (4th Cir. 1988) (“Title VII does not\n\n\n\n 15\n\frequire procedural exactness from lay complainants.”). We must be wary of “overly\n\ntechnical concerns” laying a “tripwire for hapless plaintiffs.” Syndor, 681 F.3d at 594.\n\nHere, for example, the PTO repeatedly informed Stewart, after each of his amendments—\n\nand in accordance with the statute’s plain language—that he could file a civil action “at\n\nany time after 180 days have passed from the date [he] filed [his] original complaint.”\n\nJ.A. 114. Permitting the agency to repeatedly confuse litigants in this manner would only\n\nfurther pervert Title VII’s remedial purpose.\n\n B.\n\n In support of its position that Stewart was required to wait beyond the initial 180-\n\nday waiting period, the PTO makes several arguments. First, the PTO argues that Section\n\n2000e-16(c)’s statutory text is “ambiguous” because it uses two different terms,\n\n“complaint” and “charge.” Second, the PTO argues that the EEOC’s regulations support\n\ntethering the 180-day waiting period to the agency’s extended investigation period for\n\namended complaints. Third, the PTO argues that should we reverse the district court’s\n\nholding, we would incentivize gamesmanship in Title VII claims. Each of these\n\narguments is unavailing.\n\n In support of its first argument—that Section 2000e-16(c)’s statutory text is\n\nambiguous 3—the PTO emphasizes Congress’s use of two terms within the statute:\n\n\n 3\n In repeatedly referring to Section 2000e-16(c)’s purported “ambiguity,” the PTO\nappears to be implicitly invoking, or at least evoking, Chevron deference to its\ninterpretation of the statute. However, the statute is not ambiguous. Further, we only\ngrant Chevron deference to “an agency’s construction of the statute which it\nadministers.” Chevron, U.S.A., Inc. v. Nat. Res. Def. Council, Inc., 467 U.S. 837, 842\n(Continued)\n\n 16\n\f“complaint” and “charge.” The PTO argues that the term “complaint” in Section 2000e-\n\n16(c) references “an employee’s general use of the administrative process” to allege\n\nunlawful discrimination, while the phrase “initial charge” is “the first ‘statement’”\n\nthrough which an employee identifies this discrimination. Appellee’s Br. at 25–26. To\n\nthe PTO, it bears significance that Congress did not use the phrase “initial complaint” in\n\nSection 2000e-16(c) but rather “initial charge,” thus indicating that “Congress did not\n\nseek to trigger the 180-day period upon the commencement of the EEO process\n\ngenerally.” Appellee’s Br. at 26 (emphasis in original).\n\n Even if we were to accept the PTO’s proposed distinction between these two\n\nterms, such a distinction does not aid the PTO’s position. If we treat “initial charge” as\n\nthe first, informal “statement” through which an employee alleges unlawful\n\ndiscrimination, then the 180-day waiting period would be satisfied at the same time or\n\nearlier than under the reading we adopt because a “charge,” so conceived, never\n\ntemporally follows a “complaint.” Under the PTO’s construction, Stewart’s “initial\n\ncharge” occurred on April 30, 2015, when he submitted a document to the PTO’s Office\n\nof Equal Employment Opportunity and Diversity alleging harassment and discrimination\n\non the basis of disability. Accepting the PTO’s position, then, would only hasten the date\n\nupon which Stewart could file a civil action. More significantly, PTO’s position in no\n\n\n\n\n(1984). The EEOC, not the PTO, administers Title VII, so even if Chevron deference\nwere implicated here, the PTO is entitled to no such deference. The record includes no\nindication that the EEOC concurs in the PTO’s construction of Section 2000e-16(c).\n\n\n\n 17\n\fway explains Congress’s express use of the word “initial,” which serves as the crux of\n\nour construction of Section 2000e-16(c)’s 180-day waiting period. The term “initial”\n\nmakes clear that Congress intended to begin the 180-day waiting period from the filing of\n\nthe original complaint, regardless of whether subsequent amendments to that complaint\n\nare filed. See United States v. Blannon, 836 F.2d 843, 854 (4th Cir. 1988) (“[A] court\n\nmay not manufacture an ambiguity in order to defeat Congress’ intent.”).\n\n Next, the PTO argues that the EEOC’s relevant regulations support its position\n\nthat Stewart was required to wait longer than 180 days before filing suit. However, we\n\nconclude that these regulations only reinforce our interpretation of Section 2000e-16(c).\n\n29 C.F.R. § 1614.407(b) mirrors the language found in Section 2000e-16(c), providing in\n\nrelevant part that a complainant is authorized under Title VII and the Rehabilitation Act\n\nto file a civil action in federal district court “[a]fter 180 days from the date of filing an\n\nindividual or class complaint if an appeal has not been filed and final action has not been\n\ntaken.” Given the regulation’s use of the term “individual . . . complaint,” the PTO\n\ncannot dispute that the 180-day waiting period begins upon filing of the individual\n\ncomplaint. Instead, the PTO attempts to wave away the regulation as a “generic rule,”\n\nbut this perfunctory argument is not persuasive. Appellee’s Br. at 29.\n\n The district court, and the PTO, wrongly tether Section 1614.407(b)’s 180-day\n\nwaiting period to other EEOC regulations extending the agency investigation period\n\nwhen a complaint has been amended to “within the earlier of 180 days after the last\n\namendment to the complaint or 360 days after the filing of the original complaint.” 29\n\nC.F.R. §§ 1614.106(e)(2), 1614.108(f). The district court reasoned that otherwise, the\n\n\n 18\n\fcourt “would be adjudicating claims that the [PTO] has not yet had the opportunity to\n\ninvestigate, let alone adjudicate.” J.A. 236. We disagree for two reasons.\n\n First, as discussed above, the district court’s holding is contrary to the plain\n\nlanguage of both Section 2000e-16(c) of Title VII and 29 C.F.R. § 1614.407(b). Further,\n\nSection 1614.407(b) lacks any textual distinction between filing an initial complaint and\n\nfiling an amendment, which is particularly telling given that other regulations in the same\n\npart, such as those governing the agency investigation period, do make such a distinction.\n\nSee 29 C.F.R. §§ 1614.106(e)(2), 1614.108(f). Section 1614.407(b) does not hinge\n\nemployees’ ability to file a civil action on the conclusion of the agency investigation;\n\nrather, it establishes a bright-line 180-day waiting period after which the employee can be\n\n“assured of having reasonably prompt access to the courts.” Wilson, 79 F.3d at 167 (D.C.\n\nCir. 1996).\n\n Additionally, the district court neglected an important facet of Title VII claims: we\n\nhave long held that courts may in fact adjudicate claims not raised before the agency, if\n\ncertain requirements are met. In Hill v. Western Electric Company, Inc., we recognized\n\nthe “generally accepted principle” that the “scope of a Title VII lawsuit may extend to\n\n‘any kind of discrimination like or related to allegations contained in the charge and\n\ngrowing out of such allegations during the pendency of the case’” before the agency. 672\n\nF.2d 381, 390 n.6 (4th Cir. 1982). Put otherwise, an “administrative charge of\n\ndiscrimination does not strictly limit a Title VII suit which may follow,” and federal\n\ncourts may still hear claims that the employee did not raise before the agency, as long as\n\nthey are “like or related” and grow out of the allegations during the pendency of the case\n\n\n 19\n\fbefore the agency. Sydnor, 681 F.3d at 594. Only “those discrimination claims stated in\n\nthe initial charge, those reasonably related to the original complaint, and those developed\n\nby reasonable investigation of the original complaint may be maintained in a subsequent\n\nTitle VII lawsuit.” Chacko v. Patuxent Institution, 429 F. 3d 505, 506 (4th Cir. 2005)\n\n(citation omitted); see also Smith v. First Union Nat. Bank, 202 F.3d 234, 247 (4th Cir.\n\n2000) (“If a plaintiff’s claims in her judicial complaint are reasonably related to her\n\nEEOC charge and can be expected to follow from a reasonable administrative\n\ninvestigation, the plaintiff may advance such claims in her subsequent civil suit.”). Our\n\nprecedent makes clear that plaintiffs, although circumscribed by their administrative\n\ncomplaints, are not wholly banned from raising claims for the first time before the district\n\ncourt, so long as they meet the requirements articulated in Hill and Chacko.\n\n Nor is a plaintiff’s ability to raise new claims before the district court cabined to\n\nthe context of retaliation claims, as the PTO appeared to briefly suggest at oral argument.\n\nOral Argument at 27:53–28:25 (“I don’t think he can amend his complaint, [] unless it\n\nwas for retaliation . . . because this Court’s jurisprudence provides that in cases of\n\nretaliation, the exhaustion procedures and principles are a little bit different.”). It is true\n\nthat we have often addressed a plaintiff’s ability to do so in the specific context of\n\nretaliation claims. See Nealon v. Stone, 958 F.2d 584, 590 (4th Cir. 1992). Importantly,\n\nhowever, we have never held that the rule applies exclusively in the context of retaliation\n\nclaims but rather that retaliation claims “receive extended flexibility” when being\n\nconsidered under the general rule referenced in Hill. Clarke v. Richmond Behavioral\n\nHealth Auth., No. 3:09CV743, 2011 WL 13274273, at *4 (E.D. Va. Aug. 10, 2011); see\n\n\n 20\n\falso Brown v. Runyon, 139 F.3d 888 (4th Cir. 1988) (unpublished opinion) (noting that\n\nour precedent “presupposes both that a retaliation count in a Title VII lawsuit be ‘related\n\nto’ and have ‘grown out’ of the EEO charge while the administrative charge remained\n\npending”). We have reasoned that retaliation claims constitute a subset of the general\n\nrule noted in Hill, because “retaliation claims almost always relate back to previously\n\nfiled EEO charges, and, therefore, may be raised for the first time in district court without\n\nthe requirement that a plaintiff have exhausted his administrative remedies.” Brown, 139\n\nF.3d at 888. Accordingly, retaliation claims represent the “inevitable corollary,” but not\n\nthe exclusive application, of the “generally accepted principle” articulated in Hill. Id.\n\n(quoting Nealon, 958 F.2d at 590). We have therefore left open the possibility that\n\ndistrict courts may hear claims for the first time, beyond just retaliation claims, if they are\n\n“reasonably related to the original complaint” and “developed by reasonable investigation\n\nof the original complaint.” Chacko, 429 F.3d at 506.\n\n Indeed, other circuits have recognized the need to grant Title VII plaintiffs\n\n“significant leeway” in drafting administrative complaints, given their lack of technical\n\nexpertise. Cheek v. W. & S. Life Ins. Co., 31 F.3d 497, 500 (7th Cir. 1994) (citation\n\nomitted). Applying this principle of liberal construction, other circuits permit litigants to\n\nbring claims not specifically pressed before the agency if they are “like or reasonably\n\nrelated to those contained in the [agency] complaint” and if they “reasonably could have\n\ndeveloped from the [agency’s] investigation of the charges before it.” Sommerfield v.\n\nCity of Chicago, 863 F.3d 645, 648 (7th Cir. 2017); see also Foster v. BNSF Ry. Co., 866\n\nF.3d 962, 966 (8th Cir. 2017) (holding same); Freeman v. Oakland Unified Sch. Dist.,\n\n\n 21\n\f291 F.3d 632, 636 (9th Cir. 2002) (same). We join these circuits today in reiterating our\n\ndecision in Hill and Chacko that plaintiffs may bring Title VII claims for the first time\n\nbefore a district court, so long as they are like or reasonably related to charges in the\n\noriginal administrative complaint, and if they reasonably could have developed from the\n\nagency’s investigation of the original complaint. See Hill, 672 F.2d at 390 n.6; Chacko,\n\n429 F.3d at 506.\n\n Crucially, this “like or related” limitation also allays the PTO’s third argument\n\nregarding gamesmanship. The PTO argues that should we reverse the district court, a\n\nfederal employee could file a “perfunctory initial ‘charge,’ seek to add new claims\n\nimmediately before the 180-day ‘mark,’ and then file a civil action immediately\n\nfollowing that same ‘mark.’” Appellee’s Br. at 28. First, as discussed above, we already\n\npermit courts to adjudicate reasonably related claims not heard in the first instance by\n\nagencies. The “like or related” limitation limits the universe of charges that the litigant\n\nmay bring and guards against the gamesmanship concern that litigants will raise wholly\n\nunrelated claims for the first time before a district court.\n\n Second, as Stewart correctly points out, existing procedural guardrails further\n\nprotect against such gamesmanship. When amending a complaint before the agency, the\n\nemployee must file a letter with the agency’s Office of Equal Employment Director\n\n“describing the new incident(s) and stating that s/he wishes to amend his/her complaint to\n\ninclude the new incident(s).” EEOC Mgmt. Directive 110, Ch. 5.B. The Director must\n\nthen review this request to determine if the claims are like or related, and “whether a fair\n\nand impartial investigation of the new claims can be accomplished within 360 days of the\n\n\n 22\n\foriginal filed complaint.” Id. If not, then the individual must start a new administrative\n\nprocess with respect to the new claim. Accordingly, employees cannot game the\n\nadministrative process in the way suggested by the PTO. Indeed, if we were to accept the\n\ndistrict court’s holding, we may even risk disincentivizing plaintiffs from bringing a “like\n\nor related” claim before the agency, as each amendment would only further delay the\n\nplaintiff’s access to court. Under the district court’s reading of 42 U.S.C. § 2000e-16(c)\n\nand 29 C.F.R. § 1614.407(b), a plaintiff might be better served by holding onto their “like\n\nor related” claims until the filing of a civil action. But this outcome would undermine the\n\npolicy goals underlying Title VII’s administrative framework to encourage “quicker, less\n\nformal, and less expensive resolution of disputes.” Sydnor, 681 F.3d at 593 (quoting\n\nChris v. Tenet, 221 F.3d 648, 653 (4th Cir. 2000)).\n\n Our holding maintains the careful balance between the Title VII’s administrative\n\nframework and judicial remedies, between “providing notice to employers and the\n\n[agency] on the one hand and ensuring plaintiffs are not tripped up over technicalities on\n\nthe other.” Id. at 594. We recognize the “substantial role” played by the administrative\n\nprocess in narrowing “formal litigation.” Chacko, 429 F.3d at 509. But it is equally\n\nwell-established that if the claim raised for the first time before the district court contains\n\nfactual allegations that “are reasonably related to the factual allegations in the formal\n\nlitigation, the connection between the charge and the claim is sufficient.” Id. (citation\n\nomitted); see also Kersting v. Wal-Mart Stores, Inc., 250 F.3d 1109, 1118 (7th Cir. 2001)\n\n(noting that a plaintiff may pursue a claim not explicitly included in an administrative\n\ncomplaint if the allegations are “like or reasonably related to” those in the charge).\n\n\n 23\n\f *****\n\n The plain text of 42 U.S.C. § 2000e-16(c) and 29 C.F.R. 1614.407(b), as well as\n\nthe legislative context and purpose of Title VII, dictate the outcome of this case.\n\nContrary to the district court’s holding, Section 2000e-16(c)’s 180-day waiting period\n\noperates independently of the agency’s extended investigation window for amended\n\ncomplaints. Instead, the 180-day waiting period “gives great weight to the complainant’s\n\ninterest in obtaining speedy resolution of the complaint” and ensures ready access to the\n\ncourts. Wilson, 79 F.3d at 167. Accordingly, we hold that Section 2000e-16(c)’s 180-\n\nday waiting period for filing a civil action, absent agency final action, commences with\n\nthe filing of the initial administrative complaint, regardless of subsequent amendments to\n\nthat complaint.\n\n IV.\n\n For the foregoing reasons, we reverse the district court’s dismissal of Stewart’s\n\namended complaint and remand for further proceedings.\n\n REVERSED AND REMANDED\n\n\n\n\n 24", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4356950/", "author_raw": "WYNN, Circuit Judge:"}]}
GREGORY
MOTZ
WYNN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4579697/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Fenyang Ajamu STEWART, Plaintiff - Appellant, v. Andrei IANCU, Defendant - Appellee.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-08\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-1815\n\n\nFENYANG AJAMU STEWART,\n\n Plaintiff - Appellant,\n\n v.\n\nANDREI IANCU,\n\n Defendant - Appellee.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Leonie M. Brinkema, District Judge. (1:16-cv-00213-LMB-JFA)\n\n\nArgued: October 30, 2018 Decided: January 8, 2019\n\n\nBefore GREGORY, Chief Judge, MOTZ and WYNN, Circuit Judges.\n\n\nReversed and remanded by published opinion. Judge Wynn wrote the opinion, in which\nChief Judge Gregory and Judge Motz joined.\n\n\nARGUED: Kevin Spencer Elliker, HUNTON ANDREWS KURTH LLP, Richmond,\nVirginia, for Appellant. Dennis Carl Barghaan, Jr., OFFICE OF THE UNITED STATES\nATTORNEY, Alexandria, Virginia, for Appellee. ON BRIEF: G. Zachary Terwilliger,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Alexandria,\nVirginia, for Appellee.\n\fWYNN, Circuit Judge:\n\n This appeal arises from the district court’s determination that Fenyang Ajamu\n\nStewart (“Stewart”) is required to wait longer than 180 days to commence a civil action\n\nunder Title VII and the Rehabilitation Act after amending his initial administrative\n\ncomplaint before the relevant agency. But the text of Title VII, as well as the legislative\n\ncontext and purpose, plainly states that a claimant may commence a civil action 180 days\n\nfrom “the filing of the initial charge.” 42 U.S.C. § 2000e-16(c) (emphasis added). We,\n\ntherefore, reverse the district court and remand for further proceedings.\n\n I.\n\n Stewart worked as a patent examiner for the U.S. Patent and Trademark Office\n\n(“PTO”). He suffers from bulging discs in his lower back and radiculopathy, resulting\n\nfrom compression of his sciatic nerve, as well as post- and continuous-traumatic stress\n\ndisorder. Because of these medical conditions, Stewart filed a reasonable\n\naccommodation request with the PTO in April 2014. Specifically, he requested that he\n\nnot be required to (1) come into work at a specified, mandatory time; (2) report his work\n\nschedule to his supervisor; and (3) schedule his meetings before 12:00 p.m., as his pain\n\nmedications caused morning grogginess. In addition, Stewart requested an ergonomic\n\nchair and keyboard, a standing desk, and a foot stool.\n\n On September 19, 2014, the PTO granted Stewart’s requests for the keyboard,\n\nstanding desk, and foot stool. Stewart had already received an ergonomic chair by that\n\npoint. Regarding his work schedule, the PTO determined that Stewart was already on the\n\nIncreased Flexitime Program work schedule, which permitted him sufficient flexibility to\n\n\n 2\n\f“work around any difficulties” and that Stewart’s supervisor, when possible, would\n\nschedule meetings specifically designed for Stewart after 12:00 pm. However, the PTO\n\ndenied Stewart’s request not to report his work schedule to his supervisor, as such a\n\nrequest would unduly burden his supervisor and the agency’s ability to oversee and\n\nadminister Stewart’s work.\n\n Stewart filed a formal complaint with the PTO’s Office of Equal Employment\n\nOpportunity and Diversity on July 14, 2015, challenging the PTO’s denial of his request\n\nfor accommodations, asserting a hostile work environment and discrimination, and\n\nalleging various claims of retaliation. Stewart amended this administrative complaint\n\neight times. After each of these amendments, the PTO’s Office of Equal Employment\n\nOpportunity and Diversity responded with a notice advising Stewart that (1) he may\n\namend his formal complaint at any time before the investigation is complete, and any\n\nnew claims “must be like or related to the claims raised” in the original complaint; and\n\n(2) he may “file a civil action in an appropriate United States District Court at any time\n\nafter 180 days have passed from the date [he] filed [his] original complaint. 29 C.F.R. §\n\n1614.407(b).” J.A. 114.\n\n On February 29, 2016—more than 180 days after the filing of his original\n\nadministrative complaint, but less than 180 days after the filing of several of the\n\namendments—Stewart filed pro se a civil action in the District Court for the Eastern\n\nDistrict of Virginia, alleging numerous violations of the Rehabilitation Act of 1973, 29\n\nU.S.C. § 701 et seq., and Title VII of the Civil Rights Act of 1964, 42 U.S.C. § 2000e et\n\nseq. Stewart’s claims rested on the PTO’s alleged failure to accommodate his\n\n\n 3\n\fdisabilities; a hostile work environment; reprisal for participating in protected Equal\n\nEmployment Opportunity activity; disparate treatment discrimination on the basis of\n\ndisability and failure to accommodate; and retaliation for requesting reasonable\n\naccommodation. Stewart later amended the complaint in April 2016, adding two counts.\n\n The PTO filed a motion to dismiss, arguing that Stewart’s suit was premature\n\nunder both 42 U.S.C. § 2000e-16(c) and 29 C.F.R. § 1614.407(b) because he had not\n\nexhausted his administrative remedies. According to the PTO, Stewart was required to\n\nwait to file a civil action until the conclusion of the agency’s investigation period. That\n\ninvestigation period is extended when employees amend their administrative complaint to\n\nthe earlier of 180 days after the last amendment or 360 days after the filing of the initial\n\ncomplaint. 29 C.F.R. §§ 1614.106(e)(2); 1614.108(f).\n\n On March 17, 2017, the district court dismissed Stewart’s case without prejudice\n\nfor lack of subject matter jurisdiction. The district court held that Stewart had failed to\n\nexhaust his administrative remedies because under Section 1614.407(b), he was required\n\nto wait until July 8, 2016, the earlier of 180 days after Stewart’s last amendment or 360\n\ndays after the filing of his initial complaint, to file a civil action in federal court. Stewart\n\ntimely appealed the district court’s decision.\n\n II.\n\n A.\n\n Stewart alleges violations of both the Rehabilitation Act and Title VII.\n\nRehabilitation Act claims “must comply with the same administrative procedures that\n\ngovern federal employee Title VII claims.” Wilkinson v. Rumsfeld, 100 F. App’x 155,\n\n\n 4\n\f157 (4th Cir. 2004). Section 717, codified at 42 U.S.C. § 2000e-16, amended Title VII to\n\npermit federal employees to file a civil action for employment discrimination under\n\ncertain circumstances. Federal employees may file a civil action based upon their\n\nadministrative complaint (1) within 90 days of receipt of notice of final agency action or\n\n(2) after 180 days from “the filing of the initial charge” with the agency, if there has been\n\nno final agency action on the complaint.\n\n In addition to 42 U.S.C. § 2000e-16, federal regulations govern the process for\n\nfiling a civil action based on employment discrimination. Congress has delegated to the\n\nEqual Employment Opportunity Commission (“EEOC”) the authority to promulgate\n\nregulations to implement Title VII. E.E.O.C. v. Randstad, 685 F.3d 433, 444 (4th Cir.\n\n2012). Accordingly, the EEOC has enacted regulations regarding individuals’ ability to\n\n(1) amend their administrative complaint and (2) file suit in federal court under Title VII.\n\nThese regulations reinforce Section 2000e-16. A federal employee may amend a\n\ncomplaint “at any time prior to the conclusion of the investigation to include issues or\n\nclaims like or related to those raised in the complaint.” 29 C.F.R. § 1614.106(d).\n\nEchoing the language of 42 U.S.C. § 2000e-16(c), the EEOC’s regulations also state that\n\nfederal employees seeking relief under Title VII and the Rehabilitation Act may file a\n\ncivil action in federal district court “[a]fter 180 days from the date of filing an individual\n\nor class complaint if an appeal has not been filed and final action has not been taken.” 29\n\nC.F.R. § 1614.407(b).\n\n\n\n\n 5\n\f B.\n\n We begin with the threshold question of whether Title VII’s 180-day waiting\n\nperiod found in Section 2000e-16(c) is a jurisdictional bar, a question of first impression\n\nin this circuit. 1 Although the PTO filed its motion to dismiss under Fed. R. Civ. P.\n\n12(b)(6), the district court dismissed Stewart’s case under Fed. R. Civ. P. 12(b)(1) for\n\nlack of subject-matter jurisdiction, stating that the “administrative exhaustion\n\nrequirements for the Rehabilitation Act and Title VII claims are jurisdictional,” and\n\nStewart failed to exhaust his administrative remedies. J.A. 234 n.4. For the following\n\nreasons, we conclude that the district court incorrectly held that Section 2000e-16(c)’s\n\n180-day waiting period is jurisdictional.\n\n Title VII directs federal employees to exhaust administrative remedies before\n\nfiling suit. Pueschel v. United States, 369 F.3d 345, 353 (4th Cir. 2004). Requiring\n\nexhaustion of administrative remedies serves twin objectives: protecting agency authority\n\n\n 1\n We have previously treated certain Title VII exhaustion requirements as\njurisdictional—for example, filing a charge of discrimination with the EEOC, see Jones\nv. Calvert Grp., Ltd., 551 F.3d 297, 300 (4th Cir. 2009)—but have never considered\nwhether the 180-day waiting period in Section 2000e-16(c) is a jurisdictional\nprerequisite. We also recognize that circuits have split on whether the failure to exhaust\nadministrative remedies under Title VII, broadly conceived, is a jurisdictional\nrequirement. Again, however, none of these cases implicate the mandatory 180-day\nwaiting period in Section 2000e-16(c) that is before us in this case. Compare Peppers v.\nCobb Cty., 835 F.3d 1289, 1296–97 (11th Cir. 2016) (treating the administrative\nexhaustion requirement as a jurisdictional prerequisite to filing a Title VII action), with\nFowlkes v. Ironworkers Local 40, 790 F.3d 378, 385 (2d Cir. 2015) (holding that the\nfailure to exhaust administrative remedies does not raise a jurisdictional bar); Artis v.\nBernanke, 630 F.3d 1031, 1034 n.4 (D.C. Cir. 2011) (same); Frederique-Alexandre v.\nDep’t of Nat. & Envtl. Res. of Puerto Rico, 478 F.3d 433, 440 (1st Cir. 2007) (same).\n\n\n\n 6\n\fin the administrative process and “promot[ing] efficiency” in the resolution of claims.\n\nWoodford v. Ngo, 548 U.S. 81, 89 (2006). By avoiding the “premature interruption of the\n\nadministrative process,” exhaustion requirements ensure that agencies are provided the\n\nfirst opportunity to “exercise [] discretion” or “apply [] expertise.” McKart v. United\n\nStates, 395 U.S. 185, 193–94 (1969). The 180-day waiting period serves these purposes:\n\nit ensures that the employer is “put on notice of the alleged violations” to facilitate out-\n\nof-court resolution and permits sufficient, but finite, time for the agency to address the\n\ndiscrimination charges in the first instance. Miles v. Dell, Inc., 429 F.3d 480, 491 (4th\n\nCir. 2005). Indeed, courts have regularly characterized Section 2000e-16(c)’s 180-day\n\nwaiting period as an exhaustion requirement. See Murthy v. Vilsack, 609 F.3d 460, 465\n\n(D.C. Cir. 2010); Brown v. Snow, 440 F.3d 1259, 1263 (11th Cir. 2006).\n\n However, it bears noting that the 180-day waiting period also is not a paradigmatic\n\nexhaustion requirement. Unlike most administrative exhaustion requirements premised\n\non agency action, after which injured parties may “seek review of an adverse decision\n\nand obtain a remedy” if warranted, the 180-day waiting period is satisfied by agency\n\ninaction. Darby v. Cisneros, 509 U.S. 137, 144 (1993) (citation omitted). Indeed,\n\nCongress passed Section 2000e-16(c) of Title VII in 1972 precisely because of its\n\nrecognition that federal employees frequently encountered an “administrative quagmire”\n\nin filing charges of discrimination. H.R. Rep. 92–238, at 12 (June 2, 1971). The 180-day\n\nwaiting period therefore “confines agencies and the EEOC to a tight schedule” and\n\nsignals congressional recognition that “the doctrine of exhaustion of remedies . . . had\n\nbecome [a] barrier to meaningful court review.” Wilson v. Pena, 79 F.3d 154, 167 (D.C.\n\n\n 7\n\fCir. 1996) (quoting Grubbs v. Butz, 514 F.2d 1323, 1328 (D.C. Cir. 1975)). In light of\n\nthis legislative context, the 180-day waiting period functions more like a mandatory\n\nprocedural hurdle for litigants than an affirmative agency step potentially giving rise to a\n\nremedy on review.\n\n This distinction informs our consideration of whether Section 2000e-16(c)’s 180-\n\nday waiting period requirement is also a jurisdictional requirement. Not all exhaustion\n\nrequirements are jurisdictional. Rather, we have recognized that certain exhaustion\n\nrequirements may be jurisdictional while others are not. For example, in Davis v. North\n\nCarolina Department of Correction, we specifically distinguished one exhaustion\n\nrequirement as jurisdictional—the entitlement to a right-to-sue letter from the EEOC—\n\nfrom Title VII’s “timely filing requirements,” which the Supreme Court has held are not\n\njurisdictional. 48 F.3d 134, 140 (4th Cir. 1995) (citing Zipes v. Trans World Airlines,\n\nInc., 455 U.S. 385, 393 (1982)); see also Laber v. Harvey, 438 F.3d 404, 429 n.25 (4th\n\nCir. 2006) (concluding that the 90-day time limit set forth in 42 U.S.C. § 2000e–16(c) is\n\nnot a jurisdictional requirement).\n\n In recent years, the Supreme Court repeatedly has cautioned courts not to\n\n“confuse[] or conflate[]” subject-matter jurisdiction, on the one hand, with the “essential\n\ningredients of a federal claim for relief,” on the other. Arbaugh v. Y & H Corp., 546 U.S.\n\n500, 503 (2006). Applying this distinction, the Supreme Court has differentiated between\n\nnon-jurisdictional “claim-processing” rules and jurisdictional rules that govern a court’s\n\nadjudicatory authority. Kontrick v. Ryan, 540 U.S. 443, 456 (2004); see also Gonzalez v.\n\nThaler, 565 U.S. 134, 141 (2012) (pressing a “stricter distinction” between these two\n\n\n 8\n\fcategories of rules). In particular, the Supreme Court has clarified that most time bars are\n\n“quintessential claim-processing rules,” which “promote the orderly progress of litigation\n\nby requiring that the parties take certain procedural steps at certain specified times.”\n\nHenderson v. Shinseki, 562 U.S. 428, 435 (2011) (holding that a statute requiring filing of\n\nnotice of appeal within 180 days of administrative decision constituted a “claim-\n\nprocessing rule” and therefore was not jurisdictional). Such rules do not strip a court of\n\njudicial authority to hear a case, even when the time limits are “framed in mandatory\n\nterms.” United States v. Kwai Fun Wong, 135 S. Ct. 1625, 1632 (2015) (holding that\n\ncertain timely filing provisions in the Federal Torts Claims Act were not jurisdictional).\n\n Instead, the Supreme Court has established a clear statement rule for\n\ndetermining whether procedural rules, including time bars, are jurisdictional. Only if the\n\nstatutory text “plainly show[s] that Congress imbued a procedural bar with jurisdictional\n\nconsequences” should a court treat a rule as jurisdictional. Id. Put otherwise, Congress\n\nmust explicitly “tag” a procedural bar “as jurisdictional.” Id. In conducting this clear\n\nstatement inquiry, the Supreme Court has looked to several factors, including the\n\nstatutory text (if it speaks in “jurisdictional terms”); the placement of the rule (if it is\n\nlocated in the jurisdiction-granting provision of the statute); and legislative context.\n\nHenderson, 562 U.S. at 438.\n\n Here, Congress has done nothing to “tag” as jurisdictional the 180-day waiting\n\nperiod. The text of Section 2000e-16(c) addresses only the timeliness of claims; it does\n\nnot refer to the district courts’ “authority to hear untimely suits.” Kwai Fun Wong, 135 S.\n\nCt. 1625, 1628 (2015). Much like the filing deadline at issue in Henderson, Section\n\n\n 9\n\f2000e-16(c) does not contain “jurisdictional language”—language dictating that judicial\n\nreview be obtained within a prescribed time and manner before a particular court.\n\nHenderson, 562 U.S. at 438. Simply because the 180-day waiting period is “cast in\n\nmandatory language” does not render it jurisdictional. Id. at 439.\n\n In addition, Section 2000e-16(c)’s placement within Title VII is distinct from\n\nthose provisions pertaining to jurisdiction. Section 2000e-16(c), titled “Employment by\n\nFederal Government,” lays out the respective 90-day filing period and 180-day waiting\n\nperiods before stating that the federal employee “may file a civil action as provided in\n\nsection 2000e-5.” 42 U.S.C. § 2000e-16(c) (emphasis added). Section 2000e-5, titled\n\n“Enforcement provisions,” mandates that federal district courts “shall have jurisdiction of\n\nactions brought under this subchapter.” 42 U.S.C. § 2000e-5(f)(3). These statutory\n\nsections serve different functions: on the one hand, Section 2000e-16(c) extends Title VII\n\nprotections to federal employees, and on the other, Section 2000e-5, as the enforcement\n\nprovision, prescribes jurisdictional requirements. Nothing “conditions the jurisdictional\n\ngrant [in Section 2000e-5(f)(3)] on the limitations periods [in Section 2000e-16(c)], or\n\notherwise links those separate provisions.” Kwai Fun Wong, 135 S. Ct. at 1633; see also\n\nGad v. Kansas State Univ., 787 F.3d 1032, 1038 (10th Cir. 2015) (noting that “a Title VII\n\nstatutory requirement’s classification as jurisdictional or non-jurisdictional turns in large\n\npart on whether it is located in Title VII’s jurisdictional subsection—42 U.S.C. § 2000e-\n\n5(f)(3)). This division further supports a conclusion that the 180-day waiting period is\n\nnot a jurisdictional requirement but rather a “prudential prerequisite to suit,” Davis v.\n\n\n\n\n 10\n\fFort Bend Cty., 893 F.3d 300, 305 (5th Cir. 2018), or “statutory precondition,” Vinieratos\n\nv. U.S. Dep’t of Air Force, 939 F.2d 762, 768 n.5 (9th Cir. 1991).\n\n In considering this issue, we emphasize the subtle, but important, distinction\n\nbetween those exhaustion requirements that operate as a jurisdictional bar and those that\n\nmerely function as a statutory prerequisite to filing suit under Title VII. See Vinieratos,\n\n939 F.2d at 768 n.5 (9th Cir. 1991). Because we conclude that Section 2000e-16(c)’s\n\n180-day waiting period is akin to a “claim-processing” rule that imposes procedural\n\nobligations on litigants, rather than implicates judicial authority to hear a class of cases,\n\nwe hold that the 180-day waiting period is not jurisdictional.\n\n Our holding also prevents the “drastic” consequences of treating a procedural rule\n\nas jurisdictional—consequences that “alter[] the normal operation of our adversarial\n\nsystem.” Henderson, 562 U.S. at 434. Jurisdictional defects can be raised at any time by\n\nthe parties or sua sponte by the courts, even post-judgment, which may result in the\n\n“waste of judicial resources and may unfairly prejudice litigants.” Id. Because of the\n\ngravity of a jurisdictional label, the Supreme Court has repeatedly and explicitly\n\ndemanded “discipline” in this inquiry. Id. at 435.\n\n To be clear, we do not hold that all exhaustion requirements set forth in Title VII\n\nare non-jurisdictional. Rather, whether a particular exhaustion requirement—in Title VII\n\nor any other statute—is jurisdictional turns on the statutory language and purpose of the\n\nexhaustion provision at issue. Here, Section 2000e-16(c) includes no language clearly\n\nindicating that Congress intended for the provision to serve as a jurisdictional bar.\n\nFurther, in practice, Section 2000e-16(c)’s 180-day waiting period functions more closely\n\n\n 11\n\fas a “time prescription,” which imposes a mandatory obligation on litigants but does not\n\ngovern a court’s jurisdiction. Arbaugh, 546 U.S. at 510; see also Stroy v. Gibson, 896\n\nF.3d 693, 698 (5th Cir. 2018) (treating Section 2000e-16(c)’s 180-day waiting period as a\n\n“precondition to filing suit,” not a jurisdictional requirement).\n\n Accordingly, the district court erred in dismissing this case under Federal Rule of\n\nCivil Procedure 12(b)(1). Instead, it should have considered the 180-day waiting period\n\nas a non-jurisdictional rule and decided the case under Federal Rule of Civil Procedure\n\n12(b)(6).\n\n III.\n\n A.\n\n Having determined that Section 2000e-16(c)’s 180-day waiting period is not\n\njurisdictional, we now turn to whether the district court erred in dismissing Stewart’s\n\naction under that provision. “We review de novo the grant of a motion to dismiss for\n\nfailure to state a claim [under Rule 12(b)(6)]. In so doing, we must accept as true all of\n\nthe factual allegations contained in the complaint.” Gerner v. Cty. of Chesterfield, Va.,\n\n674 F.3d 264, 266 (4th Cir. 2012) (citation omitted).\n\n Stewart’s appeal requires us to construe the statutory language of Section 2000e-\n\n16(c), and that provision’s 180-day waiting period, in particular. When construing a\n\nstatute, we “first and foremost strive to implement congressional intent by examining the\n\nplain language.” Minor v. Bostwick Laboratories, Inc., 669 F.3d 428 (4th Cir. 2012)\n\n(citation omitted). “[U]nless otherwise defined, words will be interpreted as taking their\n\nordinary, contemporary, common meaning.” Kennedy v. St. Joseph’s Ministries, Inc.,\n\n\n 12\n\f657 F.3d 189, 192 (4th Cir. 2011) (citation omitted). In interpreting the plain language of\n\nthe statute, we also look to “the specific context in which the language is used, and the\n\nbroader context of the statute as a whole,” Minor, 669 F.3d at 434–35 (citations omitted),\n\nas well as a statute’s legislative history as additional evidence of congressional intent,\n\nElm Grove Coal Co. v. Director, O.W.C.P., 480 F.3d 278, 293 (4th Cir. 2007). Here,\n\neach of these factors indicates that Stewart’s amendments of his complaint did not restart\n\nthe 180-day clock.\n\n We begin with the plain language of the statute. In relevant part, Section 2000e-\n\n16(c) permits aggrieved federal employees to file a civil action 180 days “from the filing\n\nof the initial charge with the department, agency, or unit” if the agency has “fail[ed] to\n\ntake final action on his complaint.” 42 U.S.C. § 2000e-16(c) (emphasis added). Given\n\nthe ordinary meaning of the word “initial,” Section 2000e-16(c) requires that the 180-day\n\nwaiting period begin upon the filing of the first, original charge. See Webster’s Third\n\nNew Int’l Dictionary 1163 (3d ed. 1976) (defining “initial” as “of or relating to the\n\nbeginning; marking the commencement”); American Heritage Dictionary of the English\n\nLanguage 902 (4th ed. 2009) (defining “initial” as “of, relating to, or occurring at the\n\nbeginning; first”). Therefore, in Stewart’s case, the 180-day waiting period began on July\n\n14, 2015, the date he filed his “initial,” formal administrative complaint of discrimination\n\nand retaliation before the PTO’s Office of Equal Employment and Diversity.\n\n The statute’s use of the modifier “initial” also implicitly allows for the possibility\n\nof subsequent amendments—that there may well be additional “charge[s]” that follow the\n\n“initial charge.” Accordingly, the 180-day waiting period does not reset upon subsequent\n\n\n 13\n\famendments to the administrative complaint. Had Congress not contemplated the\n\npossibility of amendments to the complaint, there would have been no reason to use the\n\nword “initial.” See Alaska Dep’t of Envtl. Conservation v. E.P.A., 540 U.S. 461, 489 n.13\n\n(2004) (observing it is “a cardinal principle of statutory construction that a statute ought,\n\nupon the whole, to be so construed that, if it can be prevented, no clause, sentence, or\n\nword shall be superfluous, void, or insignificant”) (citations and alterations omitted).\n\nTherefore, we hold that upon the passage of 180 days from the filing of the original\n\ncomplaint, and absent agency final action on the complaint, federal employees may file a\n\ncivil action, regardless of subsequent amendments to that complaint. 2\n\n Turning to the legislative context, Congress passed Section 2000e-16(c) of Title\n\nVII in 1972 because of its recognition that aggrieved federal employees did not have\n\nsufficient access to the courts under Title VII. S. Rep. 92–415 at 16 (1971). Before the\n\n1972 Act, the “effective availability of either administrative or judicial relief” for federal\n\nemployees was uncertain. Brown v. General Servs. Admin., 425 U.S. 820, 825 (1976).\n\nFederal employees often faced an “administrative quagmire” in which parties had to wait\n\nseveral years in the overburdened administrative process. H.R. Rep. 92–238, at 12 (June\n\n\n 2\n In an unpublished per curiam opinion, we summarily affirmed a district court’s\nholding that federal employees must wait beyond the 180-day period when they amend\ntheir complaints. Laber v. Harvey, No. 1:05-cv-00803-CMH, 2005 WL 3008510, at *1\n(E.D. Va. Nov. 7, 2005), aff’d, 204 F. App’x 332 (4th Cir. 2006). We are not bound by\nthat opinion, which is devoid of reasoning. See Collins v. Pond Creek Mining Co., 468\nF.3d 213, 219 (4th Cir. 2006) (noting that “we ordinarily do not accord precedential value\nto our unpublished decisions” and they are “entitled only to the weight they generate by\nthe persuasiveness of their reasoning”) (citation omitted).\n\n\n\n 14\n\f2, 1971). Ensuring that federal employees had “access to the courts” therefore drove the\n\npassage of Section 2000e-16(c). S. Rep. No. 92–415, at 16 (1971). The 180-day waiting\n\nperiod directly serves that end. In discussing Section 2000e-16(c)’s 180-day waiting\n\nprovision in the context of EEOC inaction, the D.C. Circuit observed that:\n\n The 180 day [waiting period] provision represents a Congressional\n determination that providing prompt access to the courts in discrimination\n disputes is so important that the administrative process will be given only a\n finite time to deal alone with a given dispute. Indeed, the Act is in part a\n response to Congressional realization that “the doctrine of exhaustion of\n remedies . . . had become [a] barrier to meaningful court review.”\n\nWilson, 79 F.3d at 167 (quoting Grubbs, 514 F.2d at 1328). Allowing agencies to\n\nrepeatedly delay individuals’ ability to go to court, simply because they have amended\n\ntheir administrative complaints, would frustrate a “congressional policy to make the\n\ncourts the final tribunal for the resolution of controversies over charges of discrimination\n\nafter all administrative remedies have been exhausted.” Koger v. Ball, 497 F.2d 702, 706\n\n(4th Cir. 1974). Although Section 2000e-16(c) “provides for a careful blend of\n\nadministrative and judicial enforcement powers,” we cannot overlook that, in passing the\n\nprovision, Congress intended federal employees to have a robust judicial remedy, and\n\nready access to the courts, for employment discrimination claims. Brown, 425 U.S. at\n\n833\n\n Our conclusion also comports with the broader purpose of Title VII as a “remedial\n\nscheme in which laypersons, rather than lawyers, are expected to initiate the process.”\n\nSydnor, 681 F.3d at 594 (citation omitted); see also Alvarado v. Board of Trustees of\n\nMontgomery Community College, 848 F.2d 457, 460 (4th Cir. 1988) (“Title VII does not\n\n\n\n 15\n\frequire procedural exactness from lay complainants.”). We must be wary of “overly\n\ntechnical concerns” laying a “tripwire for hapless plaintiffs.” Syndor, 681 F.3d at 594.\n\nHere, for example, the PTO repeatedly informed Stewart, after each of his amendments—\n\nand in accordance with the statute’s plain language—that he could file a civil action “at\n\nany time after 180 days have passed from the date [he] filed [his] original complaint.”\n\nJ.A. 114. Permitting the agency to repeatedly confuse litigants in this manner would only\n\nfurther pervert Title VII’s remedial purpose.\n\n B.\n\n In support of its position that Stewart was required to wait beyond the initial 180-\n\nday waiting period, the PTO makes several arguments. First, the PTO argues that Section\n\n2000e-16(c)’s statutory text is “ambiguous” because it uses two different terms,\n\n“complaint” and “charge.” Second, the PTO argues that the EEOC’s regulations support\n\ntethering the 180-day waiting period to the agency’s extended investigation period for\n\namended complaints. Third, the PTO argues that should we reverse the district court’s\n\nholding, we would incentivize gamesmanship in Title VII claims. Each of these\n\narguments is unavailing.\n\n In support of its first argument—that Section 2000e-16(c)’s statutory text is\n\nambiguous 3—the PTO emphasizes Congress’s use of two terms within the statute:\n\n\n 3\n In repeatedly referring to Section 2000e-16(c)’s purported “ambiguity,” the PTO\nappears to be implicitly invoking, or at least evoking, Chevron deference to its\ninterpretation of the statute. However, the statute is not ambiguous. Further, we only\ngrant Chevron deference to “an agency’s construction of the statute which it\nadministers.” Chevron, U.S.A., Inc. v. Nat. Res. Def. Council, Inc., 467 U.S. 837, 842\n(Continued)\n\n 16\n\f“complaint” and “charge.” The PTO argues that the term “complaint” in Section 2000e-\n\n16(c) references “an employee’s general use of the administrative process” to allege\n\nunlawful discrimination, while the phrase “initial charge” is “the first ‘statement’”\n\nthrough which an employee identifies this discrimination. Appellee’s Br. at 25–26. To\n\nthe PTO, it bears significance that Congress did not use the phrase “initial complaint” in\n\nSection 2000e-16(c) but rather “initial charge,” thus indicating that “Congress did not\n\nseek to trigger the 180-day period upon the commencement of the EEO process\n\ngenerally.” Appellee’s Br. at 26 (emphasis in original).\n\n Even if we were to accept the PTO’s proposed distinction between these two\n\nterms, such a distinction does not aid the PTO’s position. If we treat “initial charge” as\n\nthe first, informal “statement” through which an employee alleges unlawful\n\ndiscrimination, then the 180-day waiting period would be satisfied at the same time or\n\nearlier than under the reading we adopt because a “charge,” so conceived, never\n\ntemporally follows a “complaint.” Under the PTO’s construction, Stewart’s “initial\n\ncharge” occurred on April 30, 2015, when he submitted a document to the PTO’s Office\n\nof Equal Employment Opportunity and Diversity alleging harassment and discrimination\n\non the basis of disability. Accepting the PTO’s position, then, would only hasten the date\n\nupon which Stewart could file a civil action. More significantly, PTO’s position in no\n\n\n\n\n(1984). The EEOC, not the PTO, administers Title VII, so even if Chevron deference\nwere implicated here, the PTO is entitled to no such deference. The record includes no\nindication that the EEOC concurs in the PTO’s construction of Section 2000e-16(c).\n\n\n\n 17\n\fway explains Congress’s express use of the word “initial,” which serves as the crux of\n\nour construction of Section 2000e-16(c)’s 180-day waiting period. The term “initial”\n\nmakes clear that Congress intended to begin the 180-day waiting period from the filing of\n\nthe original complaint, regardless of whether subsequent amendments to that complaint\n\nare filed. See United States v. Blannon, 836 F.2d 843, 854 (4th Cir. 1988) (“[A] court\n\nmay not manufacture an ambiguity in order to defeat Congress’ intent.”).\n\n Next, the PTO argues that the EEOC’s relevant regulations support its position\n\nthat Stewart was required to wait longer than 180 days before filing suit. However, we\n\nconclude that these regulations only reinforce our interpretation of Section 2000e-16(c).\n\n29 C.F.R. § 1614.407(b) mirrors the language found in Section 2000e-16(c), providing in\n\nrelevant part that a complainant is authorized under Title VII and the Rehabilitation Act\n\nto file a civil action in federal district court “[a]fter 180 days from the date of filing an\n\nindividual or class complaint if an appeal has not been filed and final action has not been\n\ntaken.” Given the regulation’s use of the term “individual . . . complaint,” the PTO\n\ncannot dispute that the 180-day waiting period begins upon filing of the individual\n\ncomplaint. Instead, the PTO attempts to wave away the regulation as a “generic rule,”\n\nbut this perfunctory argument is not persuasive. Appellee’s Br. at 29.\n\n The district court, and the PTO, wrongly tether Section 1614.407(b)’s 180-day\n\nwaiting period to other EEOC regulations extending the agency investigation period\n\nwhen a complaint has been amended to “within the earlier of 180 days after the last\n\namendment to the complaint or 360 days after the filing of the original complaint.” 29\n\nC.F.R. §§ 1614.106(e)(2), 1614.108(f). The district court reasoned that otherwise, the\n\n\n 18\n\fcourt “would be adjudicating claims that the [PTO] has not yet had the opportunity to\n\ninvestigate, let alone adjudicate.” J.A. 236. We disagree for two reasons.\n\n First, as discussed above, the district court’s holding is contrary to the plain\n\nlanguage of both Section 2000e-16(c) of Title VII and 29 C.F.R. § 1614.407(b). Further,\n\nSection 1614.407(b) lacks any textual distinction between filing an initial complaint and\n\nfiling an amendment, which is particularly telling given that other regulations in the same\n\npart, such as those governing the agency investigation period, do make such a distinction.\n\nSee 29 C.F.R. §§ 1614.106(e)(2), 1614.108(f). Section 1614.407(b) does not hinge\n\nemployees’ ability to file a civil action on the conclusion of the agency investigation;\n\nrather, it establishes a bright-line 180-day waiting period after which the employee can be\n\n“assured of having reasonably prompt access to the courts.” Wilson, 79 F.3d at 167 (D.C.\n\nCir. 1996).\n\n Additionally, the district court neglected an important facet of Title VII claims: we\n\nhave long held that courts may in fact adjudicate claims not raised before the agency, if\n\ncertain requirements are met. In Hill v. Western Electric Company, Inc., we recognized\n\nthe “generally accepted principle” that the “scope of a Title VII lawsuit may extend to\n\n‘any kind of discrimination like or related to allegations contained in the charge and\n\ngrowing out of such allegations during the pendency of the case’” before the agency. 672\n\nF.2d 381, 390 n.6 (4th Cir. 1982). Put otherwise, an “administrative charge of\n\ndiscrimination does not strictly limit a Title VII suit which may follow,” and federal\n\ncourts may still hear claims that the employee did not raise before the agency, as long as\n\nthey are “like or related” and grow out of the allegations during the pendency of the case\n\n\n 19\n\fbefore the agency. Sydnor, 681 F.3d at 594. Only “those discrimination claims stated in\n\nthe initial charge, those reasonably related to the original complaint, and those developed\n\nby reasonable investigation of the original complaint may be maintained in a subsequent\n\nTitle VII lawsuit.” Chacko v. Patuxent Institution, 429 F. 3d 505, 506 (4th Cir. 2005)\n\n(citation omitted); see also Smith v. First Union Nat. Bank, 202 F.3d 234, 247 (4th Cir.\n\n2000) (“If a plaintiff’s claims in her judicial complaint are reasonably related to her\n\nEEOC charge and can be expected to follow from a reasonable administrative\n\ninvestigation, the plaintiff may advance such claims in her subsequent civil suit.”). Our\n\nprecedent makes clear that plaintiffs, although circumscribed by their administrative\n\ncomplaints, are not wholly banned from raising claims for the first time before the district\n\ncourt, so long as they meet the requirements articulated in Hill and Chacko.\n\n Nor is a plaintiff’s ability to raise new claims before the district court cabined to\n\nthe context of retaliation claims, as the PTO appeared to briefly suggest at oral argument.\n\nOral Argument at 27:53–28:25 (“I don’t think he can amend his complaint, [] unless it\n\nwas for retaliation . . . because this Court’s jurisprudence provides that in cases of\n\nretaliation, the exhaustion procedures and principles are a little bit different.”). It is true\n\nthat we have often addressed a plaintiff’s ability to do so in the specific context of\n\nretaliation claims. See Nealon v. Stone, 958 F.2d 584, 590 (4th Cir. 1992). Importantly,\n\nhowever, we have never held that the rule applies exclusively in the context of retaliation\n\nclaims but rather that retaliation claims “receive extended flexibility” when being\n\nconsidered under the general rule referenced in Hill. Clarke v. Richmond Behavioral\n\nHealth Auth., No. 3:09CV743, 2011 WL 13274273, at *4 (E.D. Va. Aug. 10, 2011); see\n\n\n 20\n\falso Brown v. Runyon, 139 F.3d 888 (4th Cir. 1988) (unpublished opinion) (noting that\n\nour precedent “presupposes both that a retaliation count in a Title VII lawsuit be ‘related\n\nto’ and have ‘grown out’ of the EEO charge while the administrative charge remained\n\npending”). We have reasoned that retaliation claims constitute a subset of the general\n\nrule noted in Hill, because “retaliation claims almost always relate back to previously\n\nfiled EEO charges, and, therefore, may be raised for the first time in district court without\n\nthe requirement that a plaintiff have exhausted his administrative remedies.” Brown, 139\n\nF.3d at 888. Accordingly, retaliation claims represent the “inevitable corollary,” but not\n\nthe exclusive application, of the “generally accepted principle” articulated in Hill. Id.\n\n(quoting Nealon, 958 F.2d at 590). We have therefore left open the possibility that\n\ndistrict courts may hear claims for the first time, beyond just retaliation claims, if they are\n\n“reasonably related to the original complaint” and “developed by reasonable investigation\n\nof the original complaint.” Chacko, 429 F.3d at 506.\n\n Indeed, other circuits have recognized the need to grant Title VII plaintiffs\n\n“significant leeway” in drafting administrative complaints, given their lack of technical\n\nexpertise. Cheek v. W. & S. Life Ins. Co., 31 F.3d 497, 500 (7th Cir. 1994) (citation\n\nomitted). Applying this principle of liberal construction, other circuits permit litigants to\n\nbring claims not specifically pressed before the agency if they are “like or reasonably\n\nrelated to those contained in the [agency] complaint” and if they “reasonably could have\n\ndeveloped from the [agency’s] investigation of the charges before it.” Sommerfield v.\n\nCity of Chicago, 863 F.3d 645, 648 (7th Cir. 2017); see also Foster v. BNSF Ry. Co., 866\n\nF.3d 962, 966 (8th Cir. 2017) (holding same); Freeman v. Oakland Unified Sch. Dist.,\n\n\n 21\n\f291 F.3d 632, 636 (9th Cir. 2002) (same). We join these circuits today in reiterating our\n\ndecision in Hill and Chacko that plaintiffs may bring Title VII claims for the first time\n\nbefore a district court, so long as they are like or reasonably related to charges in the\n\noriginal administrative complaint, and if they reasonably could have developed from the\n\nagency’s investigation of the original complaint. See Hill, 672 F.2d at 390 n.6; Chacko,\n\n429 F.3d at 506.\n\n Crucially, this “like or related” limitation also allays the PTO’s third argument\n\nregarding gamesmanship. The PTO argues that should we reverse the district court, a\n\nfederal employee could file a “perfunctory initial ‘charge,’ seek to add new claims\n\nimmediately before the 180-day ‘mark,’ and then file a civil action immediately\n\nfollowing that same ‘mark.’” Appellee’s Br. at 28. First, as discussed above, we already\n\npermit courts to adjudicate reasonably related claims not heard in the first instance by\n\nagencies. The “like or related” limitation limits the universe of charges that the litigant\n\nmay bring and guards against the gamesmanship concern that litigants will raise wholly\n\nunrelated claims for the first time before a district court.\n\n Second, as Stewart correctly points out, existing procedural guardrails further\n\nprotect against such gamesmanship. When amending a complaint before the agency, the\n\nemployee must file a letter with the agency’s Office of Equal Employment Director\n\n“describing the new incident(s) and stating that s/he wishes to amend his/her complaint to\n\ninclude the new incident(s).” EEOC Mgmt. Directive 110, Ch. 5.B. The Director must\n\nthen review this request to determine if the claims are like or related, and “whether a fair\n\nand impartial investigation of the new claims can be accomplished within 360 days of the\n\n\n 22\n\foriginal filed complaint.” Id. If not, then the individual must start a new administrative\n\nprocess with respect to the new claim. Accordingly, employees cannot game the\n\nadministrative process in the way suggested by the PTO. Indeed, if we were to accept the\n\ndistrict court’s holding, we may even risk disincentivizing plaintiffs from bringing a “like\n\nor related” claim before the agency, as each amendment would only further delay the\n\nplaintiff’s access to court. Under the district court’s reading of 42 U.S.C. § 2000e-16(c)\n\nand 29 C.F.R. § 1614.407(b), a plaintiff might be better served by holding onto their “like\n\nor related” claims until the filing of a civil action. But this outcome would undermine the\n\npolicy goals underlying Title VII’s administrative framework to encourage “quicker, less\n\nformal, and less expensive resolution of disputes.” Sydnor, 681 F.3d at 593 (quoting\n\nChris v. Tenet, 221 F.3d 648, 653 (4th Cir. 2000)).\n\n Our holding maintains the careful balance between the Title VII’s administrative\n\nframework and judicial remedies, between “providing notice to employers and the\n\n[agency] on the one hand and ensuring plaintiffs are not tripped up over technicalities on\n\nthe other.” Id. at 594. We recognize the “substantial role” played by the administrative\n\nprocess in narrowing “formal litigation.” Chacko, 429 F.3d at 509. But it is equally\n\nwell-established that if the claim raised for the first time before the district court contains\n\nfactual allegations that “are reasonably related to the factual allegations in the formal\n\nlitigation, the connection between the charge and the claim is sufficient.” Id. (citation\n\nomitted); see also Kersting v. Wal-Mart Stores, Inc., 250 F.3d 1109, 1118 (7th Cir. 2001)\n\n(noting that a plaintiff may pursue a claim not explicitly included in an administrative\n\ncomplaint if the allegations are “like or reasonably related to” those in the charge).\n\n\n 23\n\f *****\n\n The plain text of 42 U.S.C. § 2000e-16(c) and 29 C.F.R. 1614.407(b), as well as\n\nthe legislative context and purpose of Title VII, dictate the outcome of this case.\n\nContrary to the district court’s holding, Section 2000e-16(c)’s 180-day waiting period\n\noperates independently of the agency’s extended investigation window for amended\n\ncomplaints. Instead, the 180-day waiting period “gives great weight to the complainant’s\n\ninterest in obtaining speedy resolution of the complaint” and ensures ready access to the\n\ncourts. Wilson, 79 F.3d at 167. Accordingly, we hold that Section 2000e-16(c)’s 180-\n\nday waiting period for filing a civil action, absent agency final action, commences with\n\nthe filing of the initial administrative complaint, regardless of subsequent amendments to\n\nthat complaint.\n\n IV.\n\n For the foregoing reasons, we reverse the district court’s dismissal of Stewart’s\n\namended complaint and remand for further proceedings.\n\n REVERSED AND REMANDED\n\n\n\n\n 24\n[END_CASE]", "role": "user" } ]
4,580,036
Brian Davison v. Phyllis Randall
2019-01-09
17-2002
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Before KEENAN, WYNN, and HARRIS, Circuit Judges.", "parties": "", "opinions": [{"author": "WYNN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2002\n\n\nBRIAN DAVISON,\n\n Plaintiff - Appellee,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity,\n\n Defendant - Appellant,\n\n and\n\nLOUDOUN COUNTY BOARD OF SUPERVISORS, In their official and\nindividual capacities; LEO ROGERS, In his official capacity; TONY\nBUFFINGTON, In his official capacity; RON MEYER, In his official capacity;\nGEARY HIGGINS, In his official capacity,\n\n Defendants.\n\n------------------------------\n\nLOCAL GOVERNMENT ATTORNEYS OF VIRGINIA, INC.;\nINTERNATIONAL MUNICIPAL LAWYERS ASSOCIATION; VIRGINIA\nASSOCIATION OF COUNTIES; VIRGINIA MUNICIPAL LEAGUE,\n\n Amici Supporting Appellant,\n\nAMERICAN CIVIL LIBERTIES UNION; ACLU OF VIRGINIA; ACLU OF\nMARYLAND; ACLU OF NORTH CAROLINA; ACLU OF SOUTH\nCAROLINA; ACLU OF WEST VIRGINIA,\n\n Amici Supporting Appellee.\n\n No. 17-2003\n\n\nBRIAN C. DAVISON,\n\n Plaintiff - Appellant,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity; LOUDOUN\nCOUNTY BOARD OF SUPERVISORS, In their official and individual\ncapacities,\n\n Defendants - Appellees,\n\n and\n\nLEO ROGERS, In his official capacity; TONY BUFFINGTON, In his official\ncapacity; RON MEYER, In his official capacity; GEARY HIGGINS, In his\nofficial capacity,\n\n Defendants.\n\n\nAppeals from the United States District Court for the Eastern District of Virginia, at\nAlexandria. James C. Cacheris, Senior District Judge. (1:16-cv-00932-JCC-IDD)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n Amended: January 9, 2019\n\n\nBefore KEENAN, WYNN, and HARRIS, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Keenan\nand Judge Harris concurred. Judge Keenan wrote a separate concurring opinion.\n\n\nARGUED: Scott E. Gant, BOIES SCHILLER FLEXNER, LLP, Washington, D.C.; Leo\nP. Rogers, LOUDON COUNTY ATTORNEY, Leesburg, Virginia, for Appellant/Cross-\n\n\n 2\n\nAppellee. Katherine A. Fallow, KNIGHT FIRST AMENDMENT INSTITUTE AT\nCOLUMBIA UNIVERSITY, New York, New York, for Appellee/Cross-Appellant. ON\nBRIEF: Aaron E. Nathan, BOIES SCHILLER FLEXNER LLP, Washington, D.C., for\nAppellant/Cross-Appellee. Jameel Jaffer, Carrie DeCell, KNIGHT FIRST\nAMENDMENT INSTITUTE AT COLUMBIA UNIVERSITY, New York, New York,\nfor Appellee/Cross-Appellant. Vishal Agraharkar, AMERICAN CIVIL LIBERTIES\nUNION FOUNDATION OF VIRGINIA, Richmond, Virginia; Esha Bhandari, Vera\nEidelman, AMERICAN CIVIL LIBERTIES UNION FOUNDATION, New York, New\nYork; Susan K. Dunn, ACLU OF SC FOUNDATION, INC., Charleston, South Carolina;\nChristopher Brook, AMERICAN CIVIL LIBERTIES UNION OF NORTH CAROLINA\nLEGAL FOUNDATION, Raleigh, North Carolina; Deborah A. Jeon, ACLU\nFOUNDATION OF MARYLAND, Baltimore, Maryland; Jennifer D. Oliva, ACLU OF\nWEST VIRGINIA FOUNDATION, Charleston, West Virginia, for Amici American\nCivil Liberties Union, ACLU of Virginia, ACLU of Maryland, ACLU of North Carolina,\nACLU of South Carolina, and ACLU of West Virginia. Joshua A. Geltzer, Douglas\nLetter, Amy L. Marshak, Mary B. McCord, INSTITUTE FOR CONSTITUTIONAL\nADVOCACY AND PROTECTION GEORGETOWN UNIVERSITY LAW CENTER,\nWashington, D.C.; Kwaku A. Akowuah, Christopher C. Fonzone, Kate Heinzelman,\nSIDLEY AUSTIN LLP, Washington, D.C., for Amici Curiae First Amendment Legal\nScholars.\n\n\n\n\n 3\n\nWYNN, Circuit Judge:\n\n Phyllis Randall, Chair of the Loudoun County, Virginia, Board of Supervisors (the\n\n“Loudoun Board”), brings this appeal, arguing that the district court erred in concluding\n\nthat she violated the First Amendment rights of one of her constituents, Brian Davison,\n\nwhen she banned Davison from the “Chair Phyllis J. Randall” Facebook page she\n\nadministered. In a cross appeal, Davison principally argues that the district court erred\n\nin dismissing his procedural due process claim premised on the ban. For the reasons that\n\nfollow, we affirm.\n\n I.\n\n A.\n\n Randall has chaired the Loudoun County Board of Supervisors since January 1,\n\n2016. The day before she was sworn in as chair, Randall created the “Chair Phyllis J.\n\nRandall” Facebook Page (the “Chair’s Facebook Page”). According to Facebook, Inc.,\n\nunlike personal Facebook profiles, which are for non-commercial use and represent\n\nindividual people, Facebook “Pages”—like the Chair’s Facebook Page—“help\n\nbusinesses, organizations, and brands share their stories and connect with people.” J.A.\n\n403. “Pages are managed by people who have personal profiles,” the company explains.\n\nJ.A. 403. In addition to the Chair’s Facebook Page, Randall created and maintained two\n\nother Facebook profiles: a personal profile and a Page devoted to her campaign. Randall\n\nclassified her campaign page as belonging to a “politician” and used no designation for\n\nher personal profile, but she designated the Chair’s Facebook Page as a “governmental\n\nofficial” page. J.A. 209–10.\n\n\n 4\n\n Randall and her Chief of Staff, Jeanine Arnett, share administrative control over\n\nthe Chair’s Facebook Page, although Randall almost exclusively controls the page’s\n\ncontent. On her campaign page, Randall characterized the Chair’s Facebook Page as her\n\n“county Facebook page” stating:\n\n I really want to hear from ANY Loudoun citizen on ANY issues, request,\n criticism, complement or just your thoughts. However, I really try to keep\n back and forth conversations (as opposed to one time information items\n such as road closures) on my county Facebook page (Chair Phyllis J.\n Randall) or County email ([email protected]). Having back and\n forth constituent conversations are Foiable ([Freedom of Information Act])\n so if you could reach out to me on these mediums that would be\n appreciated.\n\nJ.A. 455 (emphasis added).\n\n The Chair’s Facebook Page includes three columns. The left column, which is\n\ntopped by a picture of Randall, includes several links to allow visitors to quickly navigate\n\nthe contents of the Chair’s Facebook Page.\n\n The middle column, which is organized in reverse chronological order similar to a\n\npersonal profile’s News Feed, is composed of posts by Randall and comments by\n\nFacebook users on those posts. Randall’s posts are almost always directed to “Loudoun,”\n\nsee, e.g., J.A. 408–10, and deal with numerous aspects of Randall’s official\n\nresponsibilities. For example, Randall used the Chair’s Facebook Page to notify the\n\npublic about upcoming Loudoun Board meetings, and the subjects to be discussed during\n\nthose meetings. Randall also used the page to inform Loudoun County residents about\n\nsignificant public safety issues. See, e.g., J.A. 412 (stating that Loudoun Board had\n\n“been informed by the Sheriff’s Office about the non-legitimate threat made on social\n\n\n\n 5\n\nmedia toward Dominion High School in Sterling”); J.A. 418 (reporting that she “ha[d]\n\nbeen briefed regarding the student falling from the water tower this morning” and\n\nadvising the public to “not make any assumptions but wait for information”). And\n\nRandall used the Chair’s Facebook Page to coordinate Loudoun County’s response to a\n\nlarge snow storm, including to communicate with constituents regarding which municipal\n\nstreets required plowing.\n\n Other posts by Randall to the Chair’s Facebook Page invited members of the\n\npublic to apply to participate on a public commission and to participate in public\n\nmeetings regarding key issues facing Loudoun County residents, such as revised flood\n\nplain zones and the Zika virus. Randall also authored posts regarding a variety of trips\n\nand meetings she had taken in furtherance of Loudoun County business. E.g., J.A. 408\n\n(reporting that Randall “address[ed] the (county) role in Treatment” at a “regional\n\nconference on Opioid and Substance Abuse Addiction”); J.A. 410 (stating that Randall\n\nrepresented Loudoun County at its “annual credit rating presentation” in New York); J.A.\n\n415 (informing public of trip to Loudoun’s “Sister City” in Germany); J.A. 426\n\n(reporting that Randall was “in Richmond lobbying for [Loudoun County’s] legislative\n\nprogram”). Finally, Randall used the page to advise the public regarding official actions\n\ntaken by the Loudoun Board. E.g., J.A. 433 (reporting that Loudoun Board “approved\n\nfunding for new breathing apparatus for our Loudoun Firefighters”); J.A. 442 (listing\n\nseveral “proclamations of note” by the Loudoun Board); J.A. 443 (informing public that\n\nLoudoun Board “adopted a budget for Fiscal Year 2017 totaling $2.46 billion for the\n\ngeneral county government and schools”). Although Randall’s posts on the Chair’s\n\n\n 6\n\nFacebook Page principally addressed her official responsibilities, a few posts addressed\n\ntopics less closely related to her official activities such as her affection for the German\n\nlanguage or pride in becoming an organ donor.\n\n Members of the public, including Davison, “liked” 1 or commented on several of\n\nRandall’s posts on the Chair’s Facebook Page. Each “like” or comment identified the\n\nname of the personal profile or Page of the authoring party. Many of the comments\n\nthanked Randall and the Loudoun Board for representing the public’s interests. Other\n\nposts by members of the public offered feedback on various issues faced by Randall and\n\nthe Loudoun Board. E.g., J.A. 427 (stating that “[p]utting recreation in a flood plain is\n\nnot a good idea”); J.A. 448 (stating that “more needs to be done with the explosion of\n\nLyme disease in Loudoun”). And other comments dealt with constituent-specific issues.\n\nE.g., J.A. 415 (constituent stating, in response to post by Randall regarding visit to\n\nLoudoun County’s “Sister City” in Germany, that constituent’s “daughter is interested in\n\nexchange programs”); J.A. 454 (stating that “there [we]re no [snow] plows to be seen” in\n\na particular neighborhood). Finally, several comments, including a number authored by\n\nDavison, criticized the Loudoun Board, generally, and Randall, in particular, for actions\n\ntaken in their official capacities. E.g., J.A. 429–30 (Davison criticizing public school\n\nsystem budget and expenditures); J.A. 438–39 (member of public criticizing\n\ngovernmental entity’s inspection of farm, claiming it failed to uncover animal abuse);\n\n\n 1\n “‘Liking’ on Facebook is a way for Facebook users to share information with\neach other.” Bland v. Roberts, 730 F.3d 368, 385 (4th Cir. 2013).\n\n\n\n 7\n\nJ.A. 449 (Davison characterizing question he posed at Loudoun Board and Loudoun\n\nSchool Board joint town hall). On some occasions, Randall responded to these\n\ncomments or criticisms.\n\n In the right column of the Chair’s Facebook Page, the page is identified as a\n\n“government official” page. It provides contact information for Randall’s county office,\n\nincluding her office telephone number, Randall’s official county email address, and the\n\ninternet address for the official county website. The column also identifies how many\n\nand which Facebook personal profiles and Pages “like” and “follow” the Chair’s\n\nFacebook Page. 2 And the column includes a list of personal profiles and Pages “liked”\n\nby the Chair’s Facebook Page.\n\n Randall publicized the Chair’s Facebook Page in her official “Chair Phyllis J.\n\nRandall” newsletter, which is prepared by County employees, hosted on the County’s\n\nwebsite, and distributed to Loudoun citizens using Randall’s official county email\n\naccount. The newsletter ends with the words “STAY CONNECTED” and a Facebook\n\nicon that hyperlinks to the Chair’s Facebook Page. Randall also highlighted the Chair’s\n\nFacebook Page in “Winter Storm Information” notices emailed from her official county\n\naccount to Loudoun County residents, advising recipients to “Visit [the Chair’s Facebook\n\nPage] for Updates.” J.A. 341–42, 344.\n\n 2\n According to Facebook, “[l]iking a Facebook Page means you are connecting to\nthat Page. When you connect to a Page, it will appear in [a user’s] timeline and [the user]\nwill appear on the page as a person who likes that Page. The Page will also be able to\npost content into [the user’s] News Feed.” Bland, 730 F.3d at 385 (internal quotation\nmarks omitted).\n\n\n\n 8\n\n Davison, an outspoken resident of Loudoun County, apparently largely focuses his\n\ncivic engagement and expression on “the funding and . . . management of public\n\nschools.” J.A. 95. To that end, he has repeatedly expressed concern about “School Board\n\nmembers failing to disclose personal conflicts as required by law before voting on\n\nfinancial transactions before the School Board.” J.A. 96.\n\n On February 3, 2016, Davison attended a Loudoun town hall meeting that\n\nincluded the Loudoun County School Board and Randall. At the meeting, Davison\n\nsubmitted a question implying that certain School Board members had acted unethically\n\nin approving financial transactions. Randall volunteered to answer the question but\n\ncharacterized it as a “set-up question” that she did not “appreciate.” J.A. 103. Shortly\n\nafter Randall answered the question—and while the town hall meeting was still\n\nongoing—Davison posted a message on Twitter in which he tagged Randall:\n\n“@ChairRandall ‘set up question’? You might want to strictly follow FOIA and the\n\nCOIA as well.” J.A. 470–71.\n\n Later that evening, Randall posted about the town hall meeting on the Chair’s\n\nFacebook Page, describing “what was generally discussed at the meeting.” J.A. 268. In\n\nresponse, Davison then used one of the Facebook Pages he manages through his personal\n\nFacebook profile—“Virginia SGP,” which Davison frequently uses to post political\n\ncommentary—to comment on Randall’s post about the town hall meeting. Although\n\nneither Davison nor Randall remember the precise content of Davison’s comment,\n\nRandall testified that it contained “accusations” regarding School Board members’ and\n\ntheir families’ putative conflicts of interest related to municipal financial transactions,\n\n\n 9\n\nsuggesting, in Randall’s opinion, that School Board members had been “taking kickback\n\nmoney.” See J.A. 268–69, 289–90. Randall stated that she “had no idea if any of th[e]\n\n[accusations] w[ere] correct,” but she determined that the post was “probably not\n\nsomething [she] want[ed] to leave” on the Chair’s Facebook Page. J.A. 269. Randall\n\nthen “deleted the whole post,” including her original post regarding the town hall\n\nmeeting, Davison’s comment and replies thereto, and all other public comments. J.A.\n\n269. Randall also banned Davison’s Virginia SGP Page from the Chair’s Facebook Page,\n\nwhich precluded Davison from using his Virginia SGP Page from commenting on the\n\nChair’s Facebook Page. The next morning, about twelve hours later, Randall\n\nreconsidered her actions and unbanned Davison’s Virginia SGP Page.\n\n B.\n\n On November 3, 2016, Davison filed an amended complaint seeking declaratory\n\nand injunctive relief under 42 U.S.C. § 1983 against Randall, in both her official and\n\nindividual capacities, and the Loudoun Board alleging that the “banning of [Davison]\n\nfrom commenting on [the Chair’s Facebook Page] is viewpoint discrimination.” J.A. 31.\n\nDavison further alleged that the ban violated his procedural due process rights protected\n\nby the Fourteenth Amendment because “Randall blocked Davison’s constitutionally\n\nprotected speech on [the Chair’s Facebook Page], a limited public forum, without prior\n\nnotice and without providing an opportunity for appealing [her] decision.” J.A. 32.\n\nDavison did not challenge Randall’s deletion of his post.\n\n On March 6, 2017—four days before the close of discovery and approximately\n\ntwo months before trial—Davison moved for leave to amend his complaint a second time\n\n\n 10\n\nto add claims under the Virginia Constitution that were materially indistinguishable from\n\nhis previously asserted First and Fourteenth Amendment claims premised on the ban, as\n\nwell as a separate First Amendment claim against the Loudoun Board. Davison’s\n\nproposed new First Amendment claim theorized that the County violated his free speech\n\nrights by choosing to use Facebook Pages as public forums, when Facebook allows\n\nprivate users to restrict access to their posts, including posts to any Page a municipality\n\ndesignates as a limited public forum. Pl.’s Mem. in Supp. of Mot. for Leave to File\n\nSecond Am. Compl. 3–9, Davison v. Loudoun County Bd. of Supervisors, 16-cv-932-\n\nJCC-IDD, ECF No. 68. The district court referred the motion to a magistrate judge, who\n\ngranted leave to amend regarding the claims under the Virginia Constitution but denied\n\nleave as to the new First Amendment claim against the Loudoun Board. Davison lodged\n\nobjections to the magistrate judge’s partial denial of leave to amend, which objections the\n\ndistrict court overruled.\n\n Around the same time, Randall and the Loudoun Board each moved for summary\n\njudgment. The Loudoun Board asserted that the municipality could not be held liable for\n\nRandall’s banning of Davison from the Chair’s Facebook Page because the Chair’s\n\nFacebook Page was not an official municipal page and because Randall, not the Loudoun\n\nBoard as a body, was solely responsible for creating and administering the Chair’s\n\nFacebook Page. The Loudoun Board and Randall further asserted that the Chair’s\n\nFacebook Page did not amount to a public forum, and therefore Randall’s ban of\n\nDavison’s Virginia SGP Page did not implicate his free speech or procedural due process\n\nrights. Finally, Randall asserted that she was entitled to qualified immunity.\n\n\n 11\n\n On May 10, 2017, the district court granted summary judgment in favor of the\n\nLoudoun Board, dismissing it from the suit. But as to Randall, the district court\n\nconcluded that Davison’s evidence established a material dispute of fact as to whether the\n\nChair’s Facebook Page amounted to a limited public forum and whether Randall, in her\n\nindividual capacity, acted under color of state law in banning Davison from the Chair’s\n\nFacebook Page. Davison v. Loudoun Cty. Bd. of Supervisors, No. 1:16-cv-932, 2017 WL\n\n1929406, at *6–9 (E.D. Va. May 10, 2017). The district court also rejected Randall’s\n\nqualified immunity argument. Id. at *8.\n\n Following a one-day bench trial of Davison’s claims against Randall, the district\n\ncourt issued a memorandum opinion and order awarding judgment in Davison’s favor on\n\nhis claims under the First Amendment and the analogous free speech provision in the\n\nVirginia Constitution. See Davison v. Loudoun Cty. Bd. of Supervisors, 267 F. Supp. 3d\n\n702, 714–18 (E.D. Va. 2017). The district court further entered judgment in Randall’s\n\nfavor on Davison’s federal and state procedural due process claims. Id. at 719–22. As to\n\nremedy, the district court denied Davison’s request for injunctive relief but granted\n\nDavison’s request for a declaratory judgment to resolve the “uncertainty regarding the\n\nlegal status of [the Chair’s Facebook Page].” Id. at 723.\n\n Randall and Davison, respectively, filed this appeal and cross appeal.\n\n II.\n\n On appeal, Randall argues that (A) Davison failed to establish standing to obtain\n\nprospective declaratory relief based on Randall’s alleged First Amendment violation; (B)\n\nthe district court erred in concluding that Randall acted under “color of state law” when\n\n\n 12\n\nshe banned Davison’s Virginia SGP Page from the Chair’s Facebook Page; and (C) the\n\ndistrict court erred in concluding that Randall’s banning of Davison’s Virginia SGP Page\n\nviolated the First Amendment.\n\n A.\n\n Notwithstanding that she did not challenge Davison’s standing below—and\n\ntherefore that the district court never squarely addressed his standing—Randall now\n\nargues that Davison failed to establish Article III standing to support the district court’s\n\naward of prospective declaratory relief. Even though Defendants did not challenge\n\nDavison’s standing below, “standing to sue is a jurisdictional issue of constitutional\n\ndimensions, and it may be raised and addressed for the first time on appeal.” Hodges v.\n\nAbraham, 300 F.3d 432, 443 (4th Cir. 2002). This Court reviews de novo “whether a\n\ndistrict court possessed jurisdiction in a declaratory judgment proceeding.” Volvo Const.\n\nEquip. N. Am., Inc. v. CLM Equip. Co., Inc., 386 F.3d 581, 591 (4th Cir. 2004).\n\n To establish Article III standing, a plaintiff must prove that: “1) he or she suffered\n\nan ‘injury in fact’ that is concrete and particularized, and is actual or imminent; 2) the\n\ninjury is fairly traceable to the challenged action of the defendant; and 3) the injury likely\n\nwill be redressed by a favorable decision.” Friends of the Earth, Inc. v. Gaston Copper\n\nRecycling Corp., 629 F.3d 387, 396 (4th Cir. 2011). Randall does not dispute that any\n\ninjury Davison suffered is fairly traceable to her decision to ban him from the Chair’s\n\nFacebook Page. Nor does Randall dispute that any such injury would be remedied by a\n\nfavorable decision. Rather, Randall claims that Davison failed to adduce evidence\n\n\n\n\n 13\n\nestablishing that he suffered an “injury in fact” sufficient to support prospective\n\ndeclaratory relief.\n\n “Injury in fact is ‘an invasion of a legally protected interest’ that is ‘concrete and\n\nparticularized’ and ‘actual or imminent, not conjectural or hypothetical.’” Kenny v.\n\nWilson, 885 F.3d 280, 287 (4th Cir. 2018) (quoting Spokeo, Inc. v. Robins, 136 S. Ct.\n\n1540, 1548 (2016)). Because “‘[p]ast exposure to illegal conduct does not in itself show\n\na present case or controversy regarding injunctive relief . . . if unaccompanied by any\n\ncontinuing, present adverse effects,’” a plaintiff seeking “declaratory or injunctive relief .\n\n. . must establish an ongoing or future injury in fact.” Id. at 287–88 (quoting O’Shea v.\n\nLittleton, 414 U.S. 488, 495–96 (1974)). Significantly, this Court—along with several\n\nother circuits—has held that “standing requirements are somewhat relaxed in First\n\nAmendment cases,” particularly regarding the injury-in-fact requirement. Cooksey v.\n\nFutrell, 721 F.3d 226, 235 (4th Cir. 2013) (collecting cases).\n\n In Kenny v. Wilson, 885 F.3d 280 (4th Cir. 2018), this Court addressed what\n\nevidence a plaintiff seeking relief under the First Amendment, like Davison, must put\n\nforward to establish a future injury-in-fact adequate to confer Article III standing to\n\nobtain prospective declaratory relief. In Kenny, several high school students lodged First\n\nAmendment challenges to two South Carolina disorderly conduct statutes. Id. at 284.\n\nThis Court explained that “there is a sufficiently imminent injury in fact if plaintiffs\n\nallege [1] ‘an intention to engage in a course of conduct arguably affected with a\n\nconstitutional interest, but proscribed by a statute, and [2] there exists a credible threat of\n\nprosecution thereunder.’” Id. at 288 (quoting Babbitt v. Farm Workers Nat’l Union, 442\n\n\n 14\n\nU.S. 289, 298 (1979)). The Kenny plaintiffs satisfied the first prong because they “attend\n\nschool” and “attending school inevitably involves expressive conduct” that implicates the\n\ndisorderly conduct statutes. Id. As to the second element—whether the students alleged\n\na “credible threat of future enforcement”—we held that such a threat exists so long as it\n\n“is not imaginary or wholly speculative, chimerical, or wholly conjectural.” Id. (internal\n\nquotation marks, citations, and alterations omitted). “[P]ast enforcement against the same\n\nconduct is good evidence that the threat of enforcement is not chimerical.” Id. (quoting\n\nSusan B. Anthony List v. Driehaus, 134 S. Ct. 2334, 2345 (2014)). “Threat of\n\nprosecution is especially credible when defendants have not ‘disavowed enforcement’ if\n\nplaintiffs engage in similar conduct in the future.” Id. (quoting Driehaus, 134 S. Ct. at\n\n2345). Applying this standard, we held that the plaintiffs alleged a credible threat of\n\nenforcement “because these three plaintiffs regularly attend schools where they allege\n\nthere may be future encounters with school resource officers or other law enforcement;\n\nthey have been prosecuted under the laws in the past; and the defendants have not\n\ndisavowed enforcement if plaintiffs engage in similar conduct in the future.” Id. at 289.\n\n Under Kenny, Davison’s evidence established his standing to obtain prospective\n\ndeclaratory relief. Relevant to the first prong—whether Davison intends to engage in a\n\ncourse of conduct “arguably” impacted by the challenged conduct, Babbitt, 442 U.S. at\n\n298—the district court found, in awarding Davison declaratory relief, that he “continues\n\nto avail himself” of the Chair’s Facebook Page and that Davison is “active in local\n\npolitics, and has a particular interest in what he believes to be corruption on the part of\n\nLoudoun County’s school board.” Davison, 267 F. Supp. 3d at 707, 723. Accordingly,\n\n\n 15\n\nthe evidence establishes that Davison continues to engage in a course of conduct—\n\nnamely, posting about alleged municipal corruption on the Chair’s Facebook Page—\n\nlikely to be impacted by Randall’s allegedly unconstitutional approach to managing the\n\npage.\n\n Turning to the second prong—whether there is a credible threat of enforcement—\n\nRandall previously blocked Davison from the Chair’s Facebook Page based on the\n\ncontent of his posts, providing “good evidence that the threat of enforcement is not\n\nchimerical.” Driehaus, 134 S. Ct. at 2345 (internal quotation marks omitted).\n\nAdditionally, Randall testified that she continues to believe she can ban Davison and\n\nothers from the Chair’s Facebook Page based on their views without triggering the First\n\nAmendment at all. See J.A. 277 (Randall stating she would “be happy to” ban other\n\ncommenters on her “Chair’s Facebook” page); J.A. 250 (Randall testifying that\n\ncomments “attacking another person” would not be allowed on her “Chair’s Facebook”\n\npage). To that end, in awarding Davison declaratory relief, the district court found that\n\nRandall “maintains she is permitted to administer this Facebook page as a purely personal\n\npage.” Davison, 267 F. Supp. 3d at 723. Accordingly, Davison established that he has\n\nbeen subject to past enforcement and that Randall has not “disavowed” future\n\nenforcement, which, under Kenny, is sufficient to establish a credible threat of\n\nenforcement. Cf. City of Lakewood v. Plain Dealer Pub. Co., 486 U.S. 750, 757 (1988)\n\n(“[T]he mere existence of the licensor’s unfettered discretion, coupled with the power of\n\nprior restraint, intimidates parties into censoring their own speech, even if the discretion\n\nand power are never actually abused.”).\n\n\n 16\n\n In sum, Davison’s evidence demonstrated—and the district court found—that\n\nDavison intends to continue to use the Chair’s Facebook Page and that Davison faces a\n\ncredible threat of future enforcement. See Davison, 267 F. Supp. 3d at 723.\n\nAccordingly, Davison adduced facts establishing an injury in fact sufficient to justify the\n\nprospective declaratory relief awarded by the district court.\n\n B.\n\n Next, Randall asserts that the district court erred in concluding, with regard to\n\nDavison’s individual capacity First Amendment claim, that Randall acted “under color of\n\nstate law,” as that phrase is used in Section 1983, in administering the Chair’s Facebook\n\nPage and banning Davison from that page. “This Court reviews judgments stemming\n\nfrom a bench trial under a mixed standard: factual findings are reviewed for clear error,\n\nwhereas conclusions of law are reviewed de novo.” Helton v. AT&T Inc., 709 F.3d 343,\n\n350 (4th Cir. 2013). Whether, under the undisputed facts, Randall acted under color of\n\nstate law is a legal question this Court reviews de novo. Rossignol v. Voorhaar, 316 F.3d\n\n516, 523 (4th Cir. 2003).\n\n To state a claim under Section 1983, a plaintiff must show that the alleged\n\nconstitutional deprivation at issue occurred because of action taken by the defendant\n\n“under color of . . . state law.” Philips v. Pitt Cty. Mem’l Hosp., 572 F.3d 176, 180 (4th\n\nCir. 2009). “The traditional definition of acting under color of state law requires that the\n\ndefendant in a § 1983 action have exercised power ‘possessed by virtue of state law and\n\nmade possible only because the wrongdoer is clothed with the authority of state law.’”\n\nWest v. Atkins, 487 U.S. 42, 49 (1988) (quoting United States v. Classic, 313 U.S. 299,\n\n\n 17\n\n326 (1941)). Section 1983’s “color-of-law prerequisite is synonymous with the more\n\nfamiliar state-action requirement” applicable to Fourteenth Amendment claims, “and the\n\nanalysis for each is identical.” Pitt Cty. Mem’l Hosp., 572 F.3d at 180. Both inquiries\n\ndemand that “the conduct allegedly causing the deprivation of a federal right be fairly\n\nattributable to the State.” Holly v. Scott, 434 F.3d 287, 292 (4th Cir. 2006) (quoting\n\nLugar v. Edmondson Oil Co., Inc., 457 U.S. 922, 937 (1982)).\n\n “[T]here is no specific formula for determining whether state action is present.”\n\nId. at 292 (internal quotation marks omitted). Rather, “[w]hat is fairly attributable [to the\n\nstate]”—i.e., what constitutes action under color of state law—“is a matter of normative\n\njudgment, and the criteria lack rigid simplicity.” Id. (internal quotation marks omitted).\n\nCourts must examine the “totality of the circumstances,” id. (internal quotation marks\n\nomitted), to determine if the action at issue “bore a ‘sufficiently close nexus’ with the\n\nState to be ‘fairly treated as that of the State itself,’” Rossignol, 316 F.3d at 525 (quoting\n\nJackson v. Metro. Edison Co., 419 U.S. 345, 351 (1974)).\n\n Although no one factor is determinative, this Court has held that a defendant’s\n\npurportedly private actions bear a “sufficiently close nexus” with the State to satisfy\n\nSection 1983’s color-of-law requirement when the defendant’s challenged “actions are\n\nlinked to events which arose out of his official status.” Id. at 524. When a defendant’s\n\n“status” as a public official “enabled [her] to execute [a challenged action] in a manner\n\nthat private citizens never could have,” then the action also is more likely to be treated as\n\nattributable to the state. Id. at 526; see also Martinez v. Colon, 54 F.3d 980, 986 (1st Cir.\n\n1995) (“[S]ection 1983 is . . . implicated . . . [when] the conduct is such that the actor\n\n\n 18\n\ncould not have behaved in that way but for the authority of his office.”); Goldstein v.\n\nChestnut Ridge Volunteer Fire Co., 218 F.3d 337, 343 (4th Cir. 2000) (holding that\n\nchallenged conduct is more likely to amount to state action when “the injury caused is\n\naggravated in a unique way by the incidents of governmental authority” (internal\n\nquotation marks omitted)). Likewise, an official’s conduct is more likely to amount to\n\nstate action when it “occurs in the course of performing an actual or apparent duty of his\n\noffice.” Martinez, 54 F.3d at 986. And the challenged action of a defendant\n\ngovernmental official is likely to be treated as taken under color of law when the official\n\n“use[d] the power and prestige of his state office to damage the plaintiff.” Harris v.\n\nHarvey, 605 F.2d 330, 337 (7th Cir. 1979). In the context of an alleged First Amendment\n\nviolation, in particular, this Court has found that a challenged action by a governmental\n\nofficial is fairly attributable to the state when “the sole intention” of the official in taking\n\nthe action was “to suppress speech critical of his conduct of official duties or fitness for\n\npublic office.” Rossignol, 316 F.3d at 524.\n\n Here, after thoroughly analyzing the totality of the circumstances surrounding\n\nRandall’s creation and administration of the Chair’s Facebook Page and banning of\n\nDavison from that page, the district court concluded that Randall acted under color of\n\nstate law. Davison, 267 F. Supp. 3d at 723. We agree.\n\n Randall created and administered the Chair’s Facebook Page to further her duties\n\nas a municipal official. She used the Chair’s Facebook Page “as a tool of governance,”\n\nid. at 713: through the Chair’s Facebook Page, Randall provides information to the public\n\n\n\n\n 19\n\nabout her and the Loudoun Board’s official activities and solicits input from the public on\n\npolicy issues she and the Loudoun Board confront. See supra Part I.A.\n\n For instance, Randall used the Chair’s Facebook Page to inform the public about\n\nserious public safety events and to keep her constituents abreast of the County’s response\n\nto a snowstorm and to coordinate snow removal activities. And, as the district court\n\ncorrectly emphasized, Randall\n\n swathe[d] the [Chair’s Facebook Page] in the trappings of her office.\n Among other things, (1) the title of the page includes [Randall]’s title; (2)\n the page is categorized as that of a government official; (3) the page lists as\n contact information [Randall]’s official County email address and the\n telephone number of [Randall]’s County office; (4) the page includes the\n web address of [Randall]’s official County website; (5) many—perhaps\n most—of the posts are expressly addressed to “Loudoun,” [Randall]’s\n constituents; (6) [Randall] has submitted posts on behalf of the [Loudoun\n Board] as a whole; (7) [Randall] has asked her constituents to use the\n [Chair‘s Facebook Page] as a channel for “back and forth constituent\n conversations”; and (8) the content posted has a strong tendency toward\n matters related to [Randall]’s office.\n\nDavison, 267 F. Supp. 3d at 714. A private citizen could not have created and used the\n\nChair’s Facebook Page in such a manner. Rossignol, 316 F.3d at 526. Put simply,\n\nRandall clothed the Chair’s Facebook Page in “the power and prestige of h[er] state\n\noffice,” Harris, 605 F.2d at 337, and created and administered the page to “perform[]\n\nactual or apparent dut[ies] of h[er] office,” Martinez, 54 F.3d at 986.\n\n Additionally, the specific actions giving rise to Davison’s claim—Randall’s\n\nbanning of Davison’s Virginia SGP Page—“are linked to events which arose out of h[er]\n\nofficial status.” Rossignol, 316 F.3d at 524. Randall’s post to the Chair’s Facebook Page\n\nthat prompted Davison’s comment informed the public about what happened at the\n\n\n\n 20\n\nLoudoun Board and Loudoun County School Board’s joint meeting. And Davison’s\n\ncomment also dealt with an issue related to that meeting and of significant public\n\ninterest—School Board members’ alleged conflicts of interest in approving financial\n\ntransactions. That Randall’s ban of Davison amounted to an effort “to suppress speech\n\ncritical of [such members’] conduct of [their] official duties or fitness for public office”\n\nfurther reinforces that the ban was taken under color of state law. Id. at 525. Considering\n\nthe totality of these circumstances, the district court correctly held that Randall acted\n\nunder color of state law in banning Davison from the Chair’s Facebook Page.\n\n C.\n\n Third, Randall argues that the district court erred in ruling in Davison’s favor on\n\nhis individual capacity First Amendment claim against Randall. Randall principally\n\nchallenges the district court’s conclusion that the Chair’s Facebook Page constitutes a\n\n“public forum” under traditional First Amendment law. We review this legal question de\n\nnovo. See Helton, 709 F.3d at 350.\n\n Under long-established First Amendment law, governmental entities are “strictly\n\nlimited” in their ability to regulate private speech in public fora. Pleasant Grove City,\n\nUtah v. Summum, 555 U.S. 460, 469 (2009). The Supreme Court has recognized two\n\ncategories of public fora: “traditional public forums” and “limited (or designated) public\n\nforums.” Am. Civil Liberties Union v. Mote, 423 F.3d 438, 443 (4th Cir. 2005).\n\n“Traditional” public forums—“such as streets, sidewalks, and parks”—“have the\n\ncharacteristics of a public thoroughfare, a purpose that is compatible with expressive\n\nconduct, as well as a tradition and history of being used for expressive public conduct.”\n\n\n 21\n\nId. “Limited” or “designated” forums are forums that are “not traditionally public, but\n\n[that] the government has purposefully opened to the public, or some segment of the\n\npublic, for expressive activity.” Id. Accordingly, the hallmark of both types of public\n\nfora—what renders the fora “public”—is that the government has made the space\n\navailable—either by designation or long-standing custom—for “expressive public\n\nconduct” or “expressive activity,” and the space is compatible with such activity. Id.\n\n“Conversely, a non-public forum is one that has not traditionally been open to the public,\n\nwhere opening it to expressive conduct would ‘somehow interfere with the objective use\n\nand purpose to which the property has been dedicated.’” Id. (quoting Warren v. Fairfax\n\nCty., 196 F.3d 186, 190–91 (4th Cir. 1999)).\n\n Although neither the Supreme Court nor any Circuit has squarely addressed\n\nwhether, and in what circumstances, a governmental social media page—like the Chair’s\n\nFacebook Page—constitutes a public forum, 3 aspects of the Chair’s Facebook Page bear\n\nthe hallmarks of a public forum. Randall “intentionally open[ed the public comment\n\nsection of the Chair’s Facebook Page] for public discourse,” Cornelius v. NAACP Legal\n\nDefense & Educ. Fund, Inc., 473 U.S. 788, 802 (1985), inviting “ANY Loudoun citizen”\n\n 3\n In addition to the court below, two other district courts have considered whether\na government official’s social media page constituted a public forum. Those courts\nreached conflicting results. Compare Morgan v. Bevin, 298 F. Supp. 3d 1003, 1010 (E.D.\nKy. 2018) (holding that First Amendment forum analysis did not apply to restrictions on\nspeech in the official Facebook and Twitter pages of the Governor of Kentucky), with\nKnight First Amend. Inst. at Colum. Univ. v. Trump, 302 F. Supp. 3d 541, 573 (S.D.N.Y.\n2018) (holding that the interactive component of the President’s Twitter account, as\nopposed to the President’s tweets themselves, constituted a designated public forum),\nappeal docketed, No. 18-1691 (2d Cir. Oct. 24, 2018).\n\n\n\n 22\n\nto make posts to the comments section of the Chair’s Facebook Page—the interactive\n\ncomponent of the page—“on ANY issues, request, criticism, complement or just your\n\nthoughts,” J.A. 455. Randall placed no restrictions on the public’s access to the page or\n\nuse of the interactive component of the Chair’s Facebook Page. And, in accordance with\n\nRandall’s invitation, the public made numerous posts on matters of public concern.\n\n The Chair’s Facebook Page also is “compatib[le] with expressive activity.”\n\nCornelius, 473 U.S. at 802. “Congress [has] recognized the internet and interactive\n\ncomputer services as offering ‘a forum for a true diversity of political discourse, unique\n\nopportunities for cultural development, and myriad avenues for intellectual activity.’”\n\nZeran v. Am. Online, Inc., 129 F.3d 327, 330 (4th Cir. 1997) (quoting 47 U.S.C. §\n\n230(a)(3)); cf. Bland, 730 F.3d at 386 (finding post to campaign Facebook page\n\n“constituted pure speech”). And the Supreme Court recently analogized social media\n\nsites, like the Chair’s Facebook Page, to “traditional” public forums, characterizing the\n\ninternet as “the most important place[] (in a spatial sense) for the exchange of views.”\n\nPackingham v. North Carolina, 137 S. Ct. 1730, 1735 (2017). An “exchange of views”\n\nis precisely what Randall sought—and what in fact transpired—when she expressly\n\ninvited “ANY Loudoun citizen” to visit the page and comment “on ANY issues,” and\n\nreceived numerous such posts and comments. J.A. 455.\n\n Randall nevertheless argues that traditional public forum analysis should not apply\n\nto the Chair’s Facebook Page for two reasons: (1) the Chair’s Facebook Page is “a private\n\nwebsite” and therefore does not constitute “public property” susceptible to forum\n\nanalysis, and (2) the Chair’s Facebook Page, in its entirety, constitutes “government\n\n\n 23\n\nspeech” properly analyzed under the framework set forth in Pleasant Grove. Randall’s\n\nBr. at 19–21, 29–31. We disagree.\n\n Even assuming the intangible space at issue is “private property,” as Randall\n\nclaims—which is not at all clear from the record before us 4—the Supreme Court never\n\nhas circumscribed forum analysis solely to government-owned property. For example, in\n\nCornelius, the Court recognized that forum analysis applies “to private property\n\ndedicated to public use.” Cornelius, 473 U.S. at 801 (emphasis added); see also\n\nChristian Legal Soc’y Chapter of the Univ. of Cal. v. Martinez, 561 U.S. 661, 679 (2010)\n\n(“[T]his Court has employed forum analysis to determine when a governmental entity, in\n\nregulating property in its charge, may place limitations on speech.” (emphasis added)).\n\n 4\n The Facebook “platform” and the “software” that underlies that platform is,\naccording to Facebook’s Terms of Service, property of Facebook, Inc. Terms of Service,\nFacebook, https://www.facebook.com/terms.php (last visited Jan. 4, 2019). Facebook’s\nTerms of Service further provide that users “own the content [they] create and share on\nFacebook and the other Facebook Products,” including Pages. Id. There would seem to\nbe a good argument, therefore, that content created, and posted to Facebook, by\ngovernment officials performing the functions and duties of their offices constitutes\ngovernment property. Cf. Solomons v. United States, 137 U.S. 342, 346–48 (1890)\n(holding that intellectual property created by government employee in the course of his\nofficial duties constituted government property because “[i]f one is employed to devise or\nperfect an instrument, or a means for accomplishing a prescribed result, he cannot, after\nsuccessfully accomplishing the work for which he was employed, plead title thereto as\nagainst his employer”). Likewise, under Facebook’s Terms of Service, the posts and\ncomments by individual Facebook users—like Davison—to a Facebook Page—like the\nChair’s Facebook Page—constitute property of those users. Accordingly, a single\nFacebook Page—including the Chair’s Facebook Page—encompasses a web of property\nrights, some of which may lie with the government. We need not—and thus do not—\ndecide with whom these property rights lie in this particular case, however, because we\nhold that even assuming the Chair’s Facebook Page constitutes private property, Randall,\nacting under color of state law, exercised control over the aspects of that page giving rise\nto Davison’s claim.\n\n\n\n 24\n\nAnd the Supreme Court and lower courts have held that private property, whether\n\ntangible or intangible, constituted a public forum when, for example, the government\n\nretained substantial control over the property under regulation or by contract. See, e.g.,\n\nSe. Promotions, Ltd. v. Conrad, 420 U.S. 546, 547, 555 (1975) (holding that “a privately\n\nowned Chattanooga theater under long-term lease to the city” was a “public forum[]\n\ndesigned for and dedicated to expressive activities”); Halleck v. Manhattan Community\n\nAccess Corp., 882 F.3d 300, 306–07 (2d Cir. 2018) (holding that public access television\n\nchannels operated by a private non-profit corporation constituted public forums), cert.\n\ngranted 139 S. Ct. 360 (2018) (mem.); First Unitarian Church of Salt Lake City v. Salt\n\nLake City Corp., 308 F.3d 1114, 1122 (10th Cir. 2002) (“[F]orum analysis does not\n\nrequire that the government have a possessory interest in or title to the underlying land.\n\nEither government ownership or regulation is sufficient for a First Amendment forum of\n\nsome kind to exist.”); Freedom from Religion Foundation, Inc. v. City of Marshfield,\n\nWis., 203 F.3d 487, 494 (7th Cir. 2000) (holding that private property abutted by public\n\npark constituted public forum).\n\n Significantly, even assuming the relevant aspects of the Chair’s Facebook Page\n\nconstitute private property—which, again, is not entirely clear from the record before\n\nus—Randall, acting under color of state law, retained and exercised significant control\n\nover the page. She created the Chair’s Facebook Page. She designated the page as\n\nbelonging to a “governmental official.” She clothed the page in the trappings of her\n\npublic office. She chose to list her official contact information on the page. And she\n\n\n\n\n 25\n\ncurated the links in the left column of the page and the lists of Facebook Pages or profiles\n\n“liked” by the Chair’s Facebook Page in the right column.\n\n Of particular importance, Randall had complete control over the aspect of the\n\nChair’s Facebook Page giving rise to Davison’s challenge because, as administrator of\n\nthe page, Randall had authority to ban Facebook profiles or Pages from using the Chair’s\n\nFacebook Page—and, therefore, the interactive component of the page—authority she\n\nexercised in banning Davison’s Virginia SGP Page. Cf. Knight, 302 F. Supp. 3d at 566–\n\n67 (holding that the interactive component of the President’s Twitter account constituted\n\npublic forum because the President and his advisors “exercise control over various\n\naspects of the . . . account,” including the power to block other users from accessing the\n\naccount).\n\n The Second Circuit’s decision in Halleck dealing with privately operated public\n\naccess television channels is instructive. Federal law allows cable franchising authorities\n\nto require cable operators to designate channel capacity for public use. Halleck, 882 F.3d\n\nat 302. Likewise, New York regulations oblige cable operators to designate at least one\n\nchannel for full-time public use. Id. Pursuant to that authority, the City of New York\n\nentered into a cable franchise agreement with a cable company requiring the company to\n\nmake available four public access channels, which channels were operated by a private,\n\nnon-profit corporation, MNN. Id. Several producers of public access programming sued\n\nMNN, alleging that MNN violated the producers’ First Amendment rights by indefinitely\n\nsuspending them from using the public access channels “because of disapproval of the\n\ncontent of a TV program” they had submitted for airing. Id.\n\n\n 26\n\n The Second Circuit concluded that the public access channels constituted a public\n\nforum, notwithstanding that they were operated by a private company. Id. at 306–08.\n\nThe court reached that conclusion for two reasons. First, it pointed to the similarities\n\nbetween public access channels and traditional public forums, like parks, describing “[a]\n\npublic access channel [a]s the electronic version of the public square.” Id. at 306.\n\nSecond, the court emphasized the extensive government involvement with, and control\n\nover, public access channels by virtue of the federal and state regulatory schemes. See id.\n\n(“[W]here, as here, federal law authorizes setting aside channels to be ‘the electronic\n\nmarketplace of ideas,’ state regulation requires cable operators to provide at least one\n\npublic access channel, a municipal contract requires a cable operator to provide four such\n\nchannels, and a municipal official has designated a private corporation to run those\n\nchannels, those channels are public forums.” (emphasis added)).\n\n Although not subject to the extensive federal and state regulatory regime\n\napplicable in Halleck, 5 the Chair’s Facebook Page is in many ways analogous to the\n\nprivately-operated public access channels considered by the Second Circuit. Just as the\n\nfederal government sought to establish an “electronic marketplace of ideas” by\n\nmandating provision of public access channels, Randall expressly sought to—and did, in\n\n\n 5\n The federal Communications Decency Act allows private online intermediaries,\nlike Facebook, the ability to moderate content by providing such intermediaries with\nbroad immunity from user-generated content posted on their sites. 47 U.S.C. § 230. This\nCourt has recognized that an “important purpose of § 230 was to encourage service\nproviders to self-regulate the dissemination of offensive material over their services.”\nZeran, 129 F.3d at 331.\n\n\n\n 27\n\nfact—create an “electronic marketplace of ideas” by inviting “ANY” constituent to post\n\nto the Chair Page on “ANY issues.” J.A. 455. Likewise, just as the City of New York\n\nchose to have a private corporation operate the public access channels, Randall chose to\n\ncreate her electronic marketplace of ideas, the Chair’s Facebook Page, on a private\n\nplatform, Facebook. Indeed, the present case provides a stronger basis for treating the\n\ninteractive component of the Chair’s Facebook Page as a public forum because whereas\n\nthe private corporation in Halleck, MNN, exercised control over the aspect of the public\n\naccess channel giving rise to the First Amendment claim—banning the public access\n\nprogram producer—a public official, Randall exercised unconstrained control over the\n\naspect of the Chair’s Facebook Page giving rise to Davison’s claim—banning of other\n\nFacebook profiles and Pages. 6\n\n\n 6\n On October 12, 2018, the Supreme Court granted MNN’s petition for writ of\ncertiorari in Halleck. 139 S. Ct. 360. MNN’s petition presented two questions: (1)\n“[w]hether the Second Circuit erred in rejecting th[e Supreme] Court’s state actor tests\nand instead creating a per se rule that private operators of public access channels are state\nactors subject to constitutional liability” and (2) “[w]hether the Second Circuit erred in\nholding—contrary to the Sixth and D.C. Circuits—that private entities operating public\naccess televisions stations are state actors for constitutional purposes where the state has\nno control over the private entity’s board or operations.” Petition for Writ of Certiorari i,\nManhattan Community Access Corp. v. Halleck, --- S. Ct. --- (No. 17-1702). MNN’s\nargument before the Supreme Court, therefore, focuses on the Second Circuit’s\ndetermination that MNN constituted a state actor, not the court’s determination that the\npublic access channels constituted a public forum.\n\n Although not identified as an issue on appeal, MNN’s petition also took issue with\nthe Second Circuit’s determination that the public access channels operated by MNN\nconstituted a public forum. But that contention was entirely derivative of its state action\nargument. In particular, MNN objected to the Second Circuit’s public forum conclusion\nonly because the public access channels were privately operated and because, in its\nopinion, the Second Circuit’s purportedly “categorical” holding that public access\n(Continued)\n\n 28\n\n Not only does case law contradict Randall’s argument that public forum analysis\n\nnever applies to private property, her argument also fails because it makes no legal sense\n\nto establish a bright-line rule that forum analysis applies only to government-owned\n\nproperty. Why, for example, should the First Amendment allow a municipality to engage\n\nin viewpoint discrimination in curating a public library branch in leased space but not\n\nallow the municipality to engage in such discrimination in a library branch on\n\nmunicipally owned property? Cf. Bd. of Educ., Island Trees Union Free Sch. Dist. No.\n\n26 v. Pico, 457 U.S. 853, 870–71 (1982) (plurality op.) (“If a Democratic school board,\n\nmotivated by partisan affiliation, ordered removal of all books written by or in favor of\n\nRepublicans, few would doubt that the order violated the constitutional rights of the\n\nstudents denied access to those books.”). Or why should a municipality be allowed to\n\nengage in viewpoint discrimination when holding a virtual public meeting hosted on a\n\nprivate website when such discrimination would be unconstitutional if the meeting was\n\nheld in a governmental building? Cf. Lyrissa Lidsky, Public Forum 2.0, 91 B.U. L. Rev.\n\n1975, 1996 (2011) (“Just as the government can rent a building to use as a forum for\n\npublic debate and discussion, so, too, can it ‘rent’ a social media page for the promotion\n\n\n\nchannels constitute public forums ignore[d] “the far more critical issue of whether (and to\nwhat extent) there is government control over a public access channel.” Id. at 19–20.\n\n Here, a government official acting under color of state law, Randall, exercised\nunconstrained control over the aspect of the Chair’s Facebook Page giving rise to\nDavison’s claim.\n\n\n\n\n 29\n\nof public discussion.”). We do not believe the First Amendment draws such arbitrary\n\nlines.\n\n Randall’s second argument—that the Chair’s Facebook Page amounts to\n\n“government speech”—fails to recognize the meaningful difference between Randall’s\n\nposts to the Chair’s Facebook Page and the public comments and posts she invited in the\n\npage’s interactive space. To be sure, Randall’s comments and curated references on the\n\nChair’s Facebook Page to other Pages, personal profiles, and websites amount to\n\ngovernmental speech. See Sutliffe v. Epping School Dist., 584 F.3d 314, 329–30 (1st Cir.\n\n2009) (holding that municipality’s refusal to place hyperlink on municipal website to\n\nwebsite of group opposed to municipal budget constituted government speech); Page v.\n\nLexington Cty. School Dist. One, 531 F.3d 275, 283–85 (4th Cir. 2008) (holding that\n\nSchool District’s refusal to place hyperlink on its website to website of group that\n\nopposed School District’s position on pending legislation constituted government speech\n\nbecause, in part, “the links to other websites were selected by the School District alone as\n\nones that supported its own message”); Knight, 302 F. Supp. 3d at 571 (“[T]he\n\nPresident’s tweets are [not] susceptible to forum analysis . . . because the content is\n\ngovernment speech.”).\n\n But the interactive component of the Chair’s Facebook Page—the portion of the\n\nmiddle column in which the public can post comments, reply to posts, and “like”\n\ncomments and posts—is materially different. See Knight, 302 F. Supp. 3d at 572\n\n(distinguishing a government official’s tweets and “the interactive space for replies and\n\nretweets”). Randall placed no formal limitations on the ability of Facebook personal\n\n\n 30\n\nprofiles and Pages to access the Chair’s Facebook Page and make comments and posts to\n\nthe interactive component of the page. On the contrary, she expressly invited posts to the\n\npage “from ANY Loudon citizen on ANY issues, request, criticism, complement or just\n\nyour thoughts.” J.A. 455. And comments and posts by users cannot be mistaken for\n\nRandall’s own speech because they identify the posting or replying personal profile or\n\nPage, and thereby distinguish that user from Randall.\n\n Contrary to Randall’s argument that the Chair’s Facebook Page, in its entirety,\n\namounts to government speech, the present case also is meaningfully distinguishable\n\nfrom the government speech framework identified in Pleasant Grove. There, a\n\nmunicipality denied a private religious group’s request to allow it to erect a “monument\n\nin a city park in which other donated monuments were previously erected,” including a\n\nmonument depicting a prominent symbol of a different religion. 555 U.S. at 464. The\n\nplaintiff religious group sought relief under the First Amendment, arguing that the city\n\npark constituted a traditional public forum, and therefore that the city could not reject the\n\nreligious group’s proposed monument when it had previously allowed construction of a\n\nmonument associated with another religion. Id. at 466.\n\n The Supreme Court held that the city did not violate the First Amendment because\n\nthe government speech framework, rather than forum analysis, applied to the conduct at\n\nissue. In reaching that conclusion, the Court emphasized that the city never “opened up\n\nthe Park for the placement of whatever permanent monuments might be offered by\n\nprivate donors.” Id. at 472–73. “Rather, the City has ‘effectively controlled’ the\n\nmessages sent by the monuments in the Park by exercising ‘final approval authority’ over\n\n\n 31\n\ntheir selection.” Id. at 473. The Court further emphasized that “[t]he forum doctrine has\n\nbeen applied in situations in which government-owned property or a government\n\nprogram was capable of accommodating a large number of public speakers without\n\ndefeating the essential function of the land or the program.” Id. at 478. A city park,\n\nhowever, “can accommodate only a limited number of permanent monuments,” and\n\ntherefore a municipality cannot—and need not—provide park space for all who wish to\n\nerect a monument. Id.\n\n Here, Randall “effectively controlled” certain aspects of the Chair’s Facebook\n\nPage: she curated the Chair’s Facebook Page’s left and right columns and made posts to\n\nthe middle column. Id. at 472. But Randall also expressly opened the Chair’s Facebook\n\nPage’s middle column—its interactive space—for “ANY” user to post on “ANY issues,”\n\nJ.A. 455, and therefore did not retain “final approval authority” over that aspect of the\n\nChair’s Facebook Page, Pleasant Grove, 555 U.S. at 473. Just as the parkland\n\nsurrounding monuments in Pleasant Grove continued to constitute a public forum, even\n\nthough the monuments themselves constituted government speech, so too the interactive\n\ncomponent of the Chair’s Facebook Page constitutes a public forum, even though\n\nRandall’s curation of and posts to the Chair’s Facebook Page amount to government\n\nspeech. Additionally, the interactive component of the Chair’s Facebook Page does not\n\nface the same spacial limitations as those of the park in Pleasant Grove, but instead is\n\n“capable of accommodating a large number of public speakers without defeating [its]\n\nessential function.” Id. at 578. Accordingly, Pleasant Grove supports, rather than\n\n\n\n\n 32\n\nundermines, our conclusion that the interactive component of the Chair’s Facebook Page\n\nconstitutes a public forum.\n\n Upon concluding that interactive component of the Chair’s Facebook Page\n\namounts to a public forum, we would normally need to determine whether it constitutes a\n\ntraditional public forum or designated or limited public forum. In the present case,\n\nhowever, we need not decide that question because Randall’s ban of Davison amounted\n\nto “viewpoint discrimination,” which is “prohibited in all forums.” See Child Evangelism\n\nFellowship of S.C. v. Anderson Sch. Dist. Five, 470 F.3d 1062, 1067 n.2 (4th Cir. 2006).\n\n“Viewpoint discrimination . . . ‘targets not subject matter, but particular views taken by\n\nspeakers on a subject.’” Id. (quoting Rosenberger v. Rector & Visitors of Univ. of Va.,\n\n515 U.S. 819, 829 (1995)). Viewpoint discrimination is apparent, for example, if a\n\ngovernment official’s decision to take a challenged action was “impermissibly motivated\n\nby a desire to suppress a particular point of view.” Cornelius, 473 U.S. at 812–13.\n\n Here, the district court found—as the record amply supports—that Randall banned\n\nDavison’s Virginia SGP Page because Davison posted a comment using that page\n\nalleging “corruption on the part of Loudoun County’s School Board involving conflicts\n\nof interests among the School Board and their family members.” Davison, 267 F. Supp.\n\n3d at 711. Although Randall stated that she had “no idea” whether Davison’s allegations\n\nwere “correct,” she nonetheless banned him because she viewed the allegations as\n\n“slanderous” and she “didn’t want [the allegations] on the site.” Id. at 717. Randall’s\n\ndecision to ban Davison because of his allegation of governmental corruption constitutes\n\nblack-letter viewpoint discrimination.\n\n\n 33\n\n Put simply, Randall unconstitutionally sought to “suppress” Davison’s opinion\n\nthat there was corruption on the School Board. Cornelius, 473 U.S. at 812–13; see also,\n\ne.g., Rossignol, 316 F.3d at 521 (holding that sheriff’s deputies engaged in viewpoint\n\ndiscrimination when they seized an issue of a newspaper that criticized the county\n\nsheriff’s and his deputies’ performance of their official duties); Putnam Pit, Inc. v. City of\n\nCookeville, Tenn., 221 F.3d 834, 846 (6th Cir. 2000) (holding that a municipality engages\n\nin viewpoint discrimination if it refuses to link newspaper webpage to the city’s website\n\nsolely because the newspaper sought to expose municipal corruption); Knight, 302 F.\n\nSupp. 3d at 575 (holding that the President engaged in viewpoint discrimination when he\n\nblocked individuals from his Twitter account because the individuals “posted tweets that\n\ncriticized the President or his policies”). 7 That Randall’s action targeted comments\n\ncritical of the School Board members’ official actions and fitness for office renders the\n\nbanning all the more problematic as such speech “occupies the core of the protection\n\nafforded by the First Amendment.” Rossignol, 316 F.3d at 521 (quoting McIntyre v.\n\nOhio Elections Comm’n, 514 U.S. 334, 346 (1995)).\n\n In sum, the interactive component of the Chair’s Facebook Page constituted a\n\npublic forum, and Randall engaged in unconstitutional viewpoint discrimination when\n\nshe banned Davison’s Virginia SGP Page from that forum.\n\n\n 7\n Randall also asserts that she did not violate Davison’s First Amendment rights\nbecause she banned his “Virginia SGP” Page, not his “Brian Davison” profile. Davison\nis the sole operator of the “Virginia SGP” Page, however, and therefore the ban\nimplicated his First Amendment rights. Randall fails to identify any case supporting her\nposition, nor have we found any. Accordingly, we reject this argument.\n\n\n 34\n\n III.\n\n In his cross-appeal, Davison asserts that the district court reversibly erred in two\n\nways: (A) by dismissing his claim against Randall in her official capacity and (B) by\n\ndenying his motion to amend his complaint to add the new First Amendment claim\n\nagainst the Loudoun Board. 8 We disagree.\n\n A.\n\n Davison first argues that the district court erred in dismissing his claim against\n\nRandall in her official capacity. Whereas “[p]ersonal-capacity suits seek to impose\n\npersonal liability upon a government official for actions [she] takes under color of state\n\nlaw,” Kentucky v. Graham, 473 U.S. 159, 165 (1985), “official capacity suits are ‘treated\n\nas suits against the municipality,’” Santos v. Frederick Cty. Bd. of Comm’rs, 725 F.3d\n\n451, 469 (4th Cir. 2013) (quoting Hafer v. Melo, 502 U.S. 21, 25 (1991)). Because\n\n“municipal liability under Section 1983 does not amount to respondeat superior . . . a\n\n 8\n Davison also argues that the district court erred in rejecting his procedural due\nprocess claims under the Fourteenth Amendment and an analogous provision in the\nVirginia Constitution. Before the district court, Davison “flatly asserted that due process\nalways requires the government to provide a hearing before imposing a prior restraint on\nspeech,” and therefore that Randall violated Davison’s First Amendment rights by failing\nto conduct a pre-ban hearing. Davison, 267 F. Supp. 3d at 719. The district court\ncorrectly rejected Davison’s proposed categorical rule. Id. (citing Cafeteria & Rest.\nWorkers Union Local 473, AFL-CIO v. McElroy, 367 U.S. 886, 895 (1961). And\nDavison has abandoned that asserted categorical rule on appeal, Davison’s Br. at 49–50\nn.19 (“[I]t might be permissible in certain contexts to delete an individual comment\nwithout providing full pre-deprivation process . . . .”), instead arguing he is entitled to\nrelief under the balancing test set forth in Mathews v. Eldridge, 424 U.S. 319, 334–35\n(1976). Because Davison did not make that argument before the district court, we decline\nto consider it now. See CoreTel Va., LLC v. Verizon Va., LLC, 808 F.3d 978, 988 (4th\nCir. 2015).\n\n\n\n 35\n\nmunicipality is subject to Section 1983 liability only when its ‘policy or custom, whether\n\nmade by its lawmakers or by those whose edicts or acts may fairly be said to represent\n\nofficial policy, inflicts the [plaintiff’s] injury.’” Id. at 469–70 (quoting Monell v. Dep’t of\n\nSoc. Servs. of the City of N.Y., 436 U.S. 658, 694 (1978)).\n\n Here, the district court dismissed Davison’s official capacity claim because it\n\nfound that “no policy—whether County-wide or specific to [Randall]’s office—played\n\nany role in [Randall]’s decision to ban [Davison] from her [Chair’s Facebook Page].”\n\nDavison, 267 F. Supp. 3d at 715. We review the district court’s factual findings bearing\n\non whether Randall acted pursuant to a municipal policy or custom for clear error and its\n\nlegal conclusions de novo. Helton, 709 F.3d at 350.\n\n On appeal, Davison does not dispute the district court’s finding—which the record\n\namply supports—that Loudoun County did not promulgate a policy governing individual\n\nLoudoun Board members’ Facebook pages. Rather, Davison principally 9 argues that “the\n\ncounty can be held liable for Randall’s actions because in banning Davison, Randall\n\nacted as a municipal policymaker.” Davison’s Br. at 47.\n\n\n\n\n 9\n Davison also argues the Loudoun Board’s failure to adopt a policy pertaining to\nindividual board members’ Facebook pages gives rise to an official capacity claim\nbecause it establishes that the Loudoun “Board was—and remains—deliberately\nindifferent to the likelihood of unconstitutional censorship and viewpoint-based\ndiscrimination on individual supervisors’ social media sites.” Davison’s Br. at 46. But\nDavison never advanced a “deliberate indifference” theory of municipal liability before\nthe district court. Again, we decline to consider an argument Davison raises for the first\ntime on appeal. See CoreTel, LLC, 808 F.3d at 988.\n\n\n\n 36\n\n Davison is correct that “municipal liability may be imposed for a single decision\n\nby municipal policymakers under appropriate circumstances.” Hunter v. Town of\n\nMocksville, N.C., 897 F.3d 538, 554 (4th Cir. 2018) (quoting Pembaur v. City of\n\nCincinnati, 475 U.S. 469, 480 (1986)). “[I]n assessing whether a municipality may be\n\nheld liable for constitutional or statutory violations of their decisionmakers, the\n\ntouchstone inquiry is whether ‘the decisionmaker possesses final authority to establish\n\nmunicipal policy with respect to the action ordered.’” Id. at 554–55 (emphasis added)\n\n(quoting Liverman v. City of Petersburg, 844 F.3d 400, 413 (4th Cir. 2016)).\n\n Here, Davison failed to put forward evidence establishing that Randall was a final\n\nmunicipal policymaker with regard to her banning of Davison from the Chair’s Facebook\n\nPage. On the contrary, record evidence establishes that the Loudoun Board retained\n\nauthority to establish municipal policy with respect to social media pages, as it adopted a\n\nsocial media policy governing the County’s official social media pages. Davison\n\nconcedes as much, arguing that the Loudoun Board “neglected . . . to extend its written\n\nguidelines to Board members’ official pages.” Davison’s Br. at 46. But that argument\n\npresupposes that the Loudoun Board—not Randall—had authority to establish municipal\n\npolicy with respect “to Board members’ official pages.”\n\n Davison nevertheless argues that the Loudoun Board “implicitly” delegated its\n\nfinal policymaking authority to Randall by not addressing individual Loudoun Board\n\nmembers’ official pages in its social media policy. Davison is correct that delegation of\n\nfinal policy making authority may be “implied from a continued course of knowing\n\nacquiescence by the governing body in the exercise of policymaking authority by an\n\n\n 37\n\nagency or official.” Id. at 48 (quoting Spell v. McDaniel, 824 F.2d 1380, 1387 (4th Cir.\n\n1987)). But Davison identifies no evidence that the Loudoun Board knew of the Chair’s\n\nFacebook Page, let alone that it “aquiesce[d]” in Randall’s administration of the page and\n\nbanning of Davison, in particular. On the contrary, the district court found that Randall\n\nmade a one-off, “unilateral decision to ban [Davison] in the heat of the moment, and\n\nreconsidered soon thereafter,” Davison, 267 F. Supp. 3d at 715—before the Loudoun\n\nBoard had a chance to learn of her action. In such circumstances, the district court did\n\nnot reversibly err in rejecting Davison’s official capacity claim.\n\n B.\n\n Next, Davison argues that the district court erred in denying him leave to amend\n\nhis complaint to add a claim that “the County violates the First Amendment by\n\nmaintaining a limited public forum on Facebook,” when policies imposed by Facebook,\n\nrather than the County, restrain, or have the potential to restrain, speech. J.A. 74. “A\n\ndistrict court may deny a motion to amend when the amendment would be prejudicial to\n\nthe opposing party, the moving party has acted in bad faith, or the amendment would be\n\nfutile.” Equal Rights Ctr. v. Niles Bolton Assocs., 602 F.3d 597, 603 (4th Cir. 2010).\n\nThe magistrate judge recommended—and the district court agreed—that Davison be\n\ndenied leave to amend on grounds of both futility and prejudice. We review for abuse of\n\ndiscretion a district court’s denial of leave to amend for prejudice, whereas we review de\n\nnovo a district court’s denial of leave to amend on the basis of futility. See U.S. ex rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n\n\n\n 38\n\n Regarding prejudice, the district court determined that the amendment came “too\n\nlate in these proceedings” and would “add a new, novel legal theory to the case after the\n\nclose of discovery, after the existing claims against [the Loudoun Board] have been\n\nshown to be meritless, after the point at which Defendants could have addressed the\n\nclaim in briefing before trial, and on the eve of trial.” J.A. 74. The district court did not\n\nabuse its discretion in denying leave to amend in such circumstances. See, e.g., Equal\n\nRights Ctr., 602 F.3d at 603–04 (holding that district court did not abuse its discretion in\n\ndenying leave to amend on the basis of prejudice when amendment came after the close\n\nof discovery and “on the eve of the deadline for dispositive motions” and therefore\n\n“would [have] change[d] the nature of the litigation”); Deasy v. Hill, 833 F.2d 38, 41 (4th\n\nCir. 1987) (affirming denial of leave to amend on grounds of prejudice when “the motion\n\nto amend came right before trial and after discovery was complete”).\n\n Although we affirm the district court’s judgment on the basis of its finding of\n\nprejudice, we do not concur in its conclusion as to futility. “Futility is apparent if the\n\nproposed amended complaint fails to state a claim under the applicable rules and\n\naccompanying standards.” Katyle v. Penn Nat. Gaming, Inc., 637 F.3d 462, 471 (4th Cir.\n\n2011). Accordingly, Davison’s proposed amendment was futile if the new claim would\n\nnot have survived a motion to dismiss under Federal Rule of Civil Procedure 12(b)(6).\n\nSee Runnion ex rel. Runnion v. Girl Scouts of Greater Chicago & Nw. Ind., 786 F.3d 510,\n\n524 (7th Cir. 2015) (“[W]hen the basis for denial is futility, we apply the legal\n\nsufficiency standard of Rule 12(b)(6) to determine whether the proposed amended\n\ncomplaint fails to state a claim.”).\n\n\n 39\n\n Davison’s proposed First Amendment claim deals not with the Chair’s Facebook\n\nPage—which the Loudoun Board did not authorize or attempt to regulate—but rather\n\nwith Loudoun County’s official Facebook Pages created and maintained pursuant to the\n\nLoudoun Board’s social media policy. As with his claims related to the Chair’s\n\nFacebook Page, Davison alleged that the Facebook Pages created and maintained by the\n\nLoudoun Board constituted public forums subject to the First Amendment. Davison\n\ntheorized that the Loudoun Board’s decision to use Facebook as its social media forum\n\nviolated his First Amendment rights because Facebook rules permit individual\n\n“requesting” users to ban other personal profiles and Pages such that the banned users can\n\nno longer see posts authored by the requesting users. In such circumstances, the banned\n\nusers “cannot see [the requesting user’s] comment[s] or participate in the discussion\n\nsurrounding the [requesting] party’s comment.” Davison’s Br. at 59. Davison’s\n\nproposed amended complaint asserted that “this scenario violates the First Amendment\n\nbecause Loudoun County has effectively enabled third parties to exclude discussion\n\nwithin a public forum—something a government body could not permissibly do in a\n\nphysical forum.” Id. at 59–60 (internal citation omitted). Put differently, Davison\n\ntheorized that Loudoun County violated the First Amendment by choosing to use\n\nFacebook as a public forum, when rules imposed by Facebook allow private users to\n\nrestrict access to their posts—and comments on and responses to those posts—including\n\nposts to any municipal Facebook Page.\n\n No court appears to have addressed that novel legal theory. And although the First\n\nAmendment constrains only government policies, not policies established by private\n\n\n 40\n\nentities, one can conceive of a colorable legal argument that a governmental actor’s\n\ndecision to select a private social media website for use as a public forum—and therefore\n\nselect that website’s suite of rules and regulations—could violate the First Amendment, if\n\nthe private website included certain types of exclusionary rules. For example, if the\n\ngovernment chose as its electronic public forum a social media site that allowed only\n\nregistered members of one political party to post and comment, there would seem to be a\n\ncompelling argument that the government’s selection of that social media site violated the\n\nFirst Amendment rights of members of other political parties, even if the partisan\n\nrestriction was imposed by the private company, not the governmental body. Such a\n\nrestriction would be seem to be no different than a municipality choosing to hold a town\n\nhall meeting in a venue that refused admission to individuals associated with a disfavored\n\npolitical party or viewpoint. Cf. DeBoer v. Village of Oak Park, 267 F.3d 558, 571 (7th\n\nCir. 2001) (“[T]he government engages in viewpoint discrimination when it denies access\n\nto a speaker solely to suppress the point of view he espouses on an otherwise includible\n\nsubject.”).\n\n Given that Davison’s proposed claim asserted a novel and colorable legal theory\n\nand that “Rule 12(b)(6) dismissals are especially disfavored in cases where the complaint\n\nsets forth a novel legal theory that can best be assessed after factual development,”\n\nWright v. North Carolina, 787 F.3d 256, 263 (4th Cir. 2015) (internal quotation marks\n\nomitted), we affirm the district court’s denial of Davison’s motion for leave to amend his\n\ncomplaint on the basis of its finding of prejudice but not on the basis of futility.\n\n IV.\n\n\n 41\n\nFor the foregoing reasons, we affirm the judgment of the district court.\n\n AFFIRMED\n\n\n\n\n 42", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357289/", "author_raw": "WYNN, Circuit Judge:"}, {"author": "BARBARA MILANO KEENAN, Circuit Judge, concurring", "type": "concurrence", "text": "BARBARA MILANO KEENAN, Circuit Judge, concurring:\n\n I join the well-reasoned majority opinion in full. I agree that the central “aspects\n\nof the Chair’s Facebook Page bear the hallmarks of a public forum.” I am particularly\n\npersuaded by the facts concerning Randall’s conduct of impressing the Chair Facebook\n\nPage with the trappings of a “government official” Facebook Page and of inviting\n\ncitizens to comment, without restriction, on matters of public concern. Accordingly,\n\nunder our precedent, I agree that Randall’s conduct of banning Davison’s Virginia SGP\n\nPage based on the content of a comment is attributable to the government and violates the\n\nFirst Amendment. See Rossignol v. Voorhaar, 316 F.3d 516, 523-25 (4th Cir. 2003).\n\n I nonetheless write separately to call attention to two issues regarding\n\ngovernmental use of social media that do not fit neatly into our precedent. First, I\n\nquestion whether any and all public officials, regardless of their roles, should be treated\n\nequally in their ability to open a public forum on social media. The Supreme Court\n\nrecently cited a series of decisions in which “a unit of government” had created a public\n\nforum. Matal v. Tam, 137 S. Ct. 1744, 1763 (2017) (emphasis added) (citing cases); see\n\nalso Pleasant Grove City v. Summum, 555 U.S. 460, 470 (2009) (“a government entity\n\nmay create a forum” (emphasis added)). However, it appears to be an open question\n\nwhether an individual public official serving in a legislative capacity qualifies as a unit of\n\ngovernment or a government entity for purposes of her ability to open a public forum.\n\nInstead, our precedent merely directs us to consider whether the challenged action “bore a\n\nsufficiently close nexus” with the government to be “fairly treated” as that of the\n\n\n\n\n 43\n\ngovernment itself. Rossignol, 316 F.3d at 525 (internal quotation marks and citation\n\nomitted).\n\n The nature and extent of a public official’s authority should have some bearing on\n\nthe official’s ability to open a public forum on social media. While the nine-member\n\nLoudoun County Board of Supervisors (the Board) serves to set policies, adopt\n\nordinances, and appropriate funds, the Chair simply is empowered individually to oversee\n\nmeetings and to set agendas. 1 The record before us is silent regarding the Chair’s\n\nauthority to take any official action on her own.\n\n In contrast, certain elected executive officials, under given circumstances, can\n\nconduct government business and set official policy unilaterally, including through the\n\nuse of social media. See, e.g., Knight First Amendment Inst. at Columbia Univ. v. Trump,\n\n302 F. Supp. 3d 541, 567 (S.D.N.Y. 2018) (discussing President Donald J. Trump’s use\n\nof his Twitter account to appoint and remove officers and conduct foreign policy), appeal\n\ndocketed, No. 18-1691 (2d Cir. Oct. 24, 2018); Schisler v. State, 907 A.2d 175, 218-20\n\n(Md. 2006) (describing the governor’s unilateral power to remove certain officers). The\n\nrelevance of such distinctions to a public official’s ability to create a public forum on\n\nsocial media is a matter that should be addressed by the Supreme Court. Because this is\n\nan open question, we are bound by current precedent and, for the reasons set forth in the\n\n\n\n 1\n See Bd. of Supervisors Operations Manual, LOUDOUN CTY., VA chs. 2-3,\nhttps://www.loudoun.gov/DocumentCenter/View/117084/Board-of-Supervisors-\nOperations-Manual-2016-2020 (last visited Dec. 20, 2018) (saved as ECF opinion\nattachment).\n\n\n 44\n\nmajority opinion, Randall as a single board member acted under of color of law and\n\nopened a public forum on Facebook.\n\n Second, the Supreme Court should consider further the reach of the First\n\nAmendment in the context of social media. I acknowledge that the Supreme Court has\n\nreferred to social media as “the modern public square,” Packingham v. North Carolina,\n\n137 S. Ct. 1730, 1737 (2017), implying that First Amendment principles protecting\n\nspeech from government intrusion do extend to social media. However, the interplay\n\nbetween private companies hosting social media sites and government actors managing\n\nthose sites necessarily blurs the line regarding which party is responsible for burdens\n\nplaced on a participant’s speech.\n\n For example, hate speech is protected under the First Amendment. See Matal, 137\n\nS. Ct. at 1763-64 (holding that the disparagement clause of the Lanham Act violated the\n\nFirst Amendment free speech clause because it prohibited hate speech). But social media\n\ncompanies like Facebook and others have policies forbidding hate speech on their\n\nplatforms. 2 Thus, while a government official, who under color of law has opened a\n\npublic forum on a social media platform like Facebook, could not ban a user’s comment\n\ncontaining hate speech, that official could report the hate speech to Facebook. And\n\nFacebook personnel could ban the user’s comment, arguably circumventing First\n\nAmendment protections.\n\n\n 2\n See, e.g., Cmty. Standards, Hate Speech, FACEBOOK, https://www.facebook.com/\ncommunitystandards/hate_speech (last visited Dec. 20, 2018) (saved as ECF opinion\nattachment).\n\n\n\n 45\n\n Admittedly, this question is not directly presented in the present case, given that\n\nthe public official, not a Facebook employee, acted to restrict speech. Nonetheless, cases\n\nnecessarily will arise requiring courts to consider the nuances of social media and their\n\nvarious roles in hosting public forums established by government officials or entities.\n\nTherefore, in my view, courts must exercise great caution when examining these issues,\n\nas we await further guidance from the Supreme Court on the First Amendment’s reach\n\ninto social media.\n\n\n\n\n 46", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357289/", "author_raw": "BARBARA MILANO KEENAN, Circuit Judge, concurring"}]}
KEENAN
WYNN
HARRIS
1
{"KEENAN": ", Circuit", "WYNN": ", Circuit", "HARRIS": ", Circuit"}
2
0
0
1
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580036/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: Brian Davison v. Phyllis Randall\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2002\n\n\nBRIAN DAVISON,\n\n Plaintiff - Appellee,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity,\n\n Defendant - Appellant,\n\n and\n\nLOUDOUN COUNTY BOARD OF SUPERVISORS, In their official and\nindividual capacities; LEO ROGERS, In his official capacity; TONY\nBUFFINGTON, In his official capacity; RON MEYER, In his official capacity;\nGEARY HIGGINS, In his official capacity,\n\n Defendants.\n\n------------------------------\n\nLOCAL GOVERNMENT ATTORNEYS OF VIRGINIA, INC.;\nINTERNATIONAL MUNICIPAL LAWYERS ASSOCIATION; VIRGINIA\nASSOCIATION OF COUNTIES; VIRGINIA MUNICIPAL LEAGUE,\n\n Amici Supporting Appellant,\n\nAMERICAN CIVIL LIBERTIES UNION; ACLU OF VIRGINIA; ACLU OF\nMARYLAND; ACLU OF NORTH CAROLINA; ACLU OF SOUTH\nCAROLINA; ACLU OF WEST VIRGINIA,\n\n Amici Supporting Appellee.\n\n No. 17-2003\n\n\nBRIAN C. DAVISON,\n\n Plaintiff - Appellant,\n\n v.\n\nPHYLLIS RANDALL, In her official and individual capacity; LOUDOUN\nCOUNTY BOARD OF SUPERVISORS, In their official and individual\ncapacities,\n\n Defendants - Appellees,\n\n and\n\nLEO ROGERS, In his official capacity; TONY BUFFINGTON, In his official\ncapacity; RON MEYER, In his official capacity; GEARY HIGGINS, In his\nofficial capacity,\n\n Defendants.\n\n\nAppeals from the United States District Court for the Eastern District of Virginia, at\nAlexandria. James C. Cacheris, Senior District Judge. (1:16-cv-00932-JCC-IDD)\n\n\nArgued: September 26, 2018 Decided: January 7, 2019\n Amended: January 9, 2019\n\n\nBefore KEENAN, WYNN, and HARRIS, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wynn wrote the opinion, in which Judge Keenan\nand Judge Harris concurred. Judge Keenan wrote a separate concurring opinion.\n\n\nARGUED: Scott E. Gant, BOIES SCHILLER FLEXNER, LLP, Washington, D.C.; Leo\nP. Rogers, LOUDON COUNTY ATTORNEY, Leesburg, Virginia, for Appellant/Cross-\n\n\n 2\n\nAppellee. Katherine A. Fallow, KNIGHT FIRST AMENDMENT INSTITUTE AT\nCOLUMBIA UNIVERSITY, New York, New York, for Appellee/Cross-Appellant. ON\nBRIEF: Aaron E. Nathan, BOIES SCHILLER FLEXNER LLP, Washington, D.C., for\nAppellant/Cross-Appellee. Jameel Jaffer, Carrie DeCell, KNIGHT FIRST\nAMENDMENT INSTITUTE AT COLUMBIA UNIVERSITY, New York, New York,\nfor Appellee/Cross-Appellant. Vishal Agraharkar, AMERICAN CIVIL LIBERTIES\nUNION FOUNDATION OF VIRGINIA, Richmond, Virginia; Esha Bhandari, Vera\nEidelman, AMERICAN CIVIL LIBERTIES UNION FOUNDATION, New York, New\nYork; Susan K. Dunn, ACLU OF SC FOUNDATION, INC., Charleston, South Carolina;\nChristopher Brook, AMERICAN CIVIL LIBERTIES UNION OF NORTH CAROLINA\nLEGAL FOUNDATION, Raleigh, North Carolina; Deborah A. Jeon, ACLU\nFOUNDATION OF MARYLAND, Baltimore, Maryland; Jennifer D. Oliva, ACLU OF\nWEST VIRGINIA FOUNDATION, Charleston, West Virginia, for Amici American\nCivil Liberties Union, ACLU of Virginia, ACLU of Maryland, ACLU of North Carolina,\nACLU of South Carolina, and ACLU of West Virginia. Joshua A. Geltzer, Douglas\nLetter, Amy L. Marshak, Mary B. McCord, INSTITUTE FOR CONSTITUTIONAL\nADVOCACY AND PROTECTION GEORGETOWN UNIVERSITY LAW CENTER,\nWashington, D.C.; Kwaku A. Akowuah, Christopher C. Fonzone, Kate Heinzelman,\nSIDLEY AUSTIN LLP, Washington, D.C., for Amici Curiae First Amendment Legal\nScholars.\n\n\n\n\n 3\n\nWYNN, Circuit Judge:\n\n Phyllis Randall, Chair of the Loudoun County, Virginia, Board of Supervisors (the\n\n“Loudoun Board”), brings this appeal, arguing that the district court erred in concluding\n\nthat she violated the First Amendment rights of one of her constituents, Brian Davison,\n\nwhen she banned Davison from the “Chair Phyllis J. Randall” Facebook page she\n\nadministered. In a cross appeal, Davison principally argues that the district court erred\n\nin dismissing his procedural due process claim premised on the ban. For the reasons that\n\nfollow, we affirm.\n\n I.\n\n A.\n\n Randall has chaired the Loudoun County Board of Supervisors since January 1,\n\n2016. The day before she was sworn in as chair, Randall created the “Chair Phyllis J.\n\nRandall” Facebook Page (the “Chair’s Facebook Page”). According to Facebook, Inc.,\n\nunlike personal Facebook profiles, which are for non-commercial use and represent\n\nindividual people, Facebook “Pages”—like the Chair’s Facebook Page—“help\n\nbusinesses, organizations, and brands share their stories and connect with people.” J.A.\n\n403. “Pages are managed by people who have personal profiles,” the company explains.\n\nJ.A. 403. In addition to the Chair’s Facebook Page, Randall created and maintained two\n\nother Facebook profiles: a personal profile and a Page devoted to her campaign. Randall\n\nclassified her campaign page as belonging to a “politician” and used no designation for\n\nher personal profile, but she designated the Chair’s Facebook Page as a “governmental\n\nofficial” page. J.A. 209–10.\n\n\n 4\n\n Randall and her Chief of Staff, Jeanine Arnett, share administrative control over\n\nthe Chair’s Facebook Page, although Randall almost exclusively controls the page’s\n\ncontent. On her campaign page, Randall characterized the Chair’s Facebook Page as her\n\n“county Facebook page” stating:\n\n I really want to hear from ANY Loudoun citizen on ANY issues, request,\n criticism, complement or just your thoughts. However, I really try to keep\n back and forth conversations (as opposed to one time information items\n such as road closures) on my county Facebook page (Chair Phyllis J.\n Randall) or County email ([email protected]). Having back and\n forth constituent conversations are Foiable ([Freedom of Information Act])\n so if you could reach out to me on these mediums that would be\n appreciated.\n\nJ.A. 455 (emphasis added).\n\n The Chair’s Facebook Page includes three columns. The left column, which is\n\ntopped by a picture of Randall, includes several links to allow visitors to quickly navigate\n\nthe contents of the Chair’s Facebook Page.\n\n The middle column, which is organized in reverse chronological order similar to a\n\npersonal profile’s News Feed, is composed of posts by Randall and comments by\n\nFacebook users on those posts. Randall’s posts are almost always directed to “Loudoun,”\n\nsee, e.g., J.A. 408–10, and deal with numerous aspects of Randall’s official\n\nresponsibilities. For example, Randall used the Chair’s Facebook Page to notify the\n\npublic about upcoming Loudoun Board meetings, and the subjects to be discussed during\n\nthose meetings. Randall also used the page to inform Loudoun County residents about\n\nsignificant public safety issues. See, e.g., J.A. 412 (stating that Loudoun Board had\n\n“been informed by the Sheriff’s Office about the non-legitimate threat made on social\n\n\n\n 5\n\nmedia toward Dominion High School in Sterling”); J.A. 418 (reporting that she “ha[d]\n\nbeen briefed regarding the student falling from the water tower this morning” and\n\nadvising the public to “not make any assumptions but wait for information”). And\n\nRandall used the Chair’s Facebook Page to coordinate Loudoun County’s response to a\n\nlarge snow storm, including to communicate with constituents regarding which municipal\n\nstreets required plowing.\n\n Other posts by Randall to the Chair’s Facebook Page invited members of the\n\npublic to apply to participate on a public commission and to participate in public\n\nmeetings regarding key issues facing Loudoun County residents, such as revised flood\n\nplain zones and the Zika virus. Randall also authored posts regarding a variety of trips\n\nand meetings she had taken in furtherance of Loudoun County business. E.g., J.A. 408\n\n(reporting that Randall “address[ed] the (county) role in Treatment” at a “regional\n\nconference on Opioid and Substance Abuse Addiction”); J.A. 410 (stating that Randall\n\nrepresented Loudoun County at its “annual credit rating presentation” in New York); J.A.\n\n415 (informing public of trip to Loudoun’s “Sister City” in Germany); J.A. 426\n\n(reporting that Randall was “in Richmond lobbying for [Loudoun County’s] legislative\n\nprogram”). Finally, Randall used the page to advise the public regarding official actions\n\ntaken by the Loudoun Board. E.g., J.A. 433 (reporting that Loudoun Board “approved\n\nfunding for new breathing apparatus for our Loudoun Firefighters”); J.A. 442 (listing\n\nseveral “proclamations of note” by the Loudoun Board); J.A. 443 (informing public that\n\nLoudoun Board “adopted a budget for Fiscal Year 2017 totaling $2.46 billion for the\n\ngeneral county government and schools”). Although Randall’s posts on the Chair’s\n\n\n 6\n\nFacebook Page principally addressed her official responsibilities, a few posts addressed\n\ntopics less closely related to her official activities such as her affection for the German\n\nlanguage or pride in becoming an organ donor.\n\n Members of the public, including Davison, “liked” 1 or commented on several of\n\nRandall’s posts on the Chair’s Facebook Page. Each “like” or comment identified the\n\nname of the personal profile or Page of the authoring party. Many of the comments\n\nthanked Randall and the Loudoun Board for representing the public’s interests. Other\n\nposts by members of the public offered feedback on various issues faced by Randall and\n\nthe Loudoun Board. E.g., J.A. 427 (stating that “[p]utting recreation in a flood plain is\n\nnot a good idea”); J.A. 448 (stating that “more needs to be done with the explosion of\n\nLyme disease in Loudoun”). And other comments dealt with constituent-specific issues.\n\nE.g., J.A. 415 (constituent stating, in response to post by Randall regarding visit to\n\nLoudoun County’s “Sister City” in Germany, that constituent’s “daughter is interested in\n\nexchange programs”); J.A. 454 (stating that “there [we]re no [snow] plows to be seen” in\n\na particular neighborhood). Finally, several comments, including a number authored by\n\nDavison, criticized the Loudoun Board, generally, and Randall, in particular, for actions\n\ntaken in their official capacities. E.g., J.A. 429–30 (Davison criticizing public school\n\nsystem budget and expenditures); J.A. 438–39 (member of public criticizing\n\ngovernmental entity’s inspection of farm, claiming it failed to uncover animal abuse);\n\n\n 1\n “‘Liking’ on Facebook is a way for Facebook users to share information with\neach other.” Bland v. Roberts, 730 F.3d 368, 385 (4th Cir. 2013).\n\n\n\n 7\n\nJ.A. 449 (Davison characterizing question he posed at Loudoun Board and Loudoun\n\nSchool Board joint town hall). On some occasions, Randall responded to these\n\ncomments or criticisms.\n\n In the right column of the Chair’s Facebook Page, the page is identified as a\n\n“government official” page. It provides contact information for Randall’s county office,\n\nincluding her office telephone number, Randall’s official county email address, and the\n\ninternet address for the official county website. The column also identifies how many\n\nand which Facebook personal profiles and Pages “like” and “follow” the Chair’s\n\nFacebook Page. 2 And the column includes a list of personal profiles and Pages “liked”\n\nby the Chair’s Facebook Page.\n\n Randall publicized the Chair’s Facebook Page in her official “Chair Phyllis J.\n\nRandall” newsletter, which is prepared by County employees, hosted on the County’s\n\nwebsite, and distributed to Loudoun citizens using Randall’s official county email\n\naccount. The newsletter ends with the words “STAY CONNECTED” and a Facebook\n\nicon that hyperlinks to the Chair’s Facebook Page. Randall also highlighted the Chair’s\n\nFacebook Page in “Winter Storm Information” notices emailed from her official county\n\naccount to Loudoun County residents, advising recipients to “Visit [the Chair’s Facebook\n\nPage] for Updates.” J.A. 341–42, 344.\n\n 2\n According to Facebook, “[l]iking a Facebook Page means you are connecting to\nthat Page. When you connect to a Page, it will appear in [a user’s] timeline and [the user]\nwill appear on the page as a person who likes that Page. The Page will also be able to\npost content into [the user’s] News Feed.” Bland, 730 F.3d at 385 (internal quotation\nmarks omitted).\n\n\n\n 8\n\n Davison, an outspoken resident of Loudoun County, apparently largely focuses his\n\ncivic engagement and expression on “the funding and . . . management of public\n\nschools.” J.A. 95. To that end, he has repeatedly expressed concern about “School Board\n\nmembers failing to disclose personal conflicts as required by law before voting on\n\nfinancial transactions before the School Board.” J.A. 96.\n\n On February 3, 2016, Davison attended a Loudoun town hall meeting that\n\nincluded the Loudoun County School Board and Randall. At the meeting, Davison\n\nsubmitted a question implying that certain School Board members had acted unethically\n\nin approving financial transactions. Randall volunteered to answer the question but\n\ncharacterized it as a “set-up question” that she did not “appreciate.” J.A. 103. Shortly\n\nafter Randall answered the question—and while the town hall meeting was still\n\nongoing—Davison posted a message on Twitter in which he tagged Randall:\n\n“@ChairRandall ‘set up question’? You might want to strictly follow FOIA and the\n\nCOIA as well.” J.A. 470–71.\n\n Later that evening, Randall posted about the town hall meeting on the Chair’s\n\nFacebook Page, describing “what was generally discussed at the meeting.” J.A. 268. In\n\nresponse, Davison then used one of the Facebook Pages he manages through his personal\n\nFacebook profile—“Virginia SGP,” which Davison frequently uses to post political\n\ncommentary—to comment on Randall’s post about the town hall meeting. Although\n\nneither Davison nor Randall remember the precise content of Davison’s comment,\n\nRandall testified that it contained “accusations” regarding School Board members’ and\n\ntheir families’ putative conflicts of interest related to municipal financial transactions,\n\n\n 9\n\nsuggesting, in Randall’s opinion, that School Board members had been “taking kickback\n\nmoney.” See J.A. 268–69, 289–90. Randall stated that she “had no idea if any of th[e]\n\n[accusations] w[ere] correct,” but she determined that the post was “probably not\n\nsomething [she] want[ed] to leave” on the Chair’s Facebook Page. J.A. 269. Randall\n\nthen “deleted the whole post,” including her original post regarding the town hall\n\nmeeting, Davison’s comment and replies thereto, and all other public comments. J.A.\n\n269. Randall also banned Davison’s Virginia SGP Page from the Chair’s Facebook Page,\n\nwhich precluded Davison from using his Virginia SGP Page from commenting on the\n\nChair’s Facebook Page. The next morning, about twelve hours later, Randall\n\nreconsidered her actions and unbanned Davison’s Virginia SGP Page.\n\n B.\n\n On November 3, 2016, Davison filed an amended complaint seeking declaratory\n\nand injunctive relief under 42 U.S.C. § 1983 against Randall, in both her official and\n\nindividual capacities, and the Loudoun Board alleging that the “banning of [Davison]\n\nfrom commenting on [the Chair’s Facebook Page] is viewpoint discrimination.” J.A. 31.\n\nDavison further alleged that the ban violated his procedural due process rights protected\n\nby the Fourteenth Amendment because “Randall blocked Davison’s constitutionally\n\nprotected speech on [the Chair’s Facebook Page], a limited public forum, without prior\n\nnotice and without providing an opportunity for appealing [her] decision.” J.A. 32.\n\nDavison did not challenge Randall’s deletion of his post.\n\n On March 6, 2017—four days before the close of discovery and approximately\n\ntwo months before trial—Davison moved for leave to amend his complaint a second time\n\n\n 10\n\nto add claims under the Virginia Constitution that were materially indistinguishable from\n\nhis previously asserted First and Fourteenth Amendment claims premised on the ban, as\n\nwell as a separate First Amendment claim against the Loudoun Board. Davison’s\n\nproposed new First Amendment claim theorized that the County violated his free speech\n\nrights by choosing to use Facebook Pages as public forums, when Facebook allows\n\nprivate users to restrict access to their posts, including posts to any Page a municipality\n\ndesignates as a limited public forum. Pl.’s Mem. in Supp. of Mot. for Leave to File\n\nSecond Am. Compl. 3–9, Davison v. Loudoun County Bd. of Supervisors, 16-cv-932-\n\nJCC-IDD, ECF No. 68. The district court referred the motion to a magistrate judge, who\n\ngranted leave to amend regarding the claims under the Virginia Constitution but denied\n\nleave as to the new First Amendment claim against the Loudoun Board. Davison lodged\n\nobjections to the magistrate judge’s partial denial of leave to amend, which objections the\n\ndistrict court overruled.\n\n Around the same time, Randall and the Loudoun Board each moved for summary\n\njudgment. The Loudoun Board asserted that the municipality could not be held liable for\n\nRandall’s banning of Davison from the Chair’s Facebook Page because the Chair’s\n\nFacebook Page was not an official municipal page and because Randall, not the Loudoun\n\nBoard as a body, was solely responsible for creating and administering the Chair’s\n\nFacebook Page. The Loudoun Board and Randall further asserted that the Chair’s\n\nFacebook Page did not amount to a public forum, and therefore Randall’s ban of\n\nDavison’s Virginia SGP Page did not implicate his free speech or procedural due process\n\nrights. Finally, Randall asserted that she was entitled to qualified immunity.\n\n\n 11\n\n On May 10, 2017, the district court granted summary judgment in favor of the\n\nLoudoun Board, dismissing it from the suit. But as to Randall, the district court\n\nconcluded that Davison’s evidence established a material dispute of fact as to whether the\n\nChair’s Facebook Page amounted to a limited public forum and whether Randall, in her\n\nindividual capacity, acted under color of state law in banning Davison from the Chair’s\n\nFacebook Page. Davison v. Loudoun Cty. Bd. of Supervisors, No. 1:16-cv-932, 2017 WL\n\n1929406, at *6–9 (E.D. Va. May 10, 2017). The district court also rejected Randall’s\n\nqualified immunity argument. Id. at *8.\n\n Following a one-day bench trial of Davison’s claims against Randall, the district\n\ncourt issued a memorandum opinion and order awarding judgment in Davison’s favor on\n\nhis claims under the First Amendment and the analogous free speech provision in the\n\nVirginia Constitution. See Davison v. Loudoun Cty. Bd. of Supervisors, 267 F. Supp. 3d\n\n702, 714–18 (E.D. Va. 2017). The district court further entered judgment in Randall’s\n\nfavor on Davison’s federal and state procedural due process claims. Id. at 719–22. As to\n\nremedy, the district court denied Davison’s request for injunctive relief but granted\n\nDavison’s request for a declaratory judgment to resolve the “uncertainty regarding the\n\nlegal status of [the Chair’s Facebook Page].” Id. at 723.\n\n Randall and Davison, respectively, filed this appeal and cross appeal.\n\n II.\n\n On appeal, Randall argues that (A) Davison failed to establish standing to obtain\n\nprospective declaratory relief based on Randall’s alleged First Amendment violation; (B)\n\nthe district court erred in concluding that Randall acted under “color of state law” when\n\n\n 12\n\nshe banned Davison’s Virginia SGP Page from the Chair’s Facebook Page; and (C) the\n\ndistrict court erred in concluding that Randall’s banning of Davison’s Virginia SGP Page\n\nviolated the First Amendment.\n\n A.\n\n Notwithstanding that she did not challenge Davison’s standing below—and\n\ntherefore that the district court never squarely addressed his standing—Randall now\n\nargues that Davison failed to establish Article III standing to support the district court’s\n\naward of prospective declaratory relief. Even though Defendants did not challenge\n\nDavison’s standing below, “standing to sue is a jurisdictional issue of constitutional\n\ndimensions, and it may be raised and addressed for the first time on appeal.” Hodges v.\n\nAbraham, 300 F.3d 432, 443 (4th Cir. 2002). This Court reviews de novo “whether a\n\ndistrict court possessed jurisdiction in a declaratory judgment proceeding.” Volvo Const.\n\nEquip. N. Am., Inc. v. CLM Equip. Co., Inc., 386 F.3d 581, 591 (4th Cir. 2004).\n\n To establish Article III standing, a plaintiff must prove that: “1) he or she suffered\n\nan ‘injury in fact’ that is concrete and particularized, and is actual or imminent; 2) the\n\ninjury is fairly traceable to the challenged action of the defendant; and 3) the injury likely\n\nwill be redressed by a favorable decision.” Friends of the Earth, Inc. v. Gaston Copper\n\nRecycling Corp., 629 F.3d 387, 396 (4th Cir. 2011). Randall does not dispute that any\n\ninjury Davison suffered is fairly traceable to her decision to ban him from the Chair’s\n\nFacebook Page. Nor does Randall dispute that any such injury would be remedied by a\n\nfavorable decision. Rather, Randall claims that Davison failed to adduce evidence\n\n\n\n\n 13\n\nestablishing that he suffered an “injury in fact” sufficient to support prospective\n\ndeclaratory relief.\n\n “Injury in fact is ‘an invasion of a legally protected interest’ that is ‘concrete and\n\nparticularized’ and ‘actual or imminent, not conjectural or hypothetical.’” Kenny v.\n\nWilson, 885 F.3d 280, 287 (4th Cir. 2018) (quoting Spokeo, Inc. v. Robins, 136 S. Ct.\n\n1540, 1548 (2016)). Because “‘[p]ast exposure to illegal conduct does not in itself show\n\na present case or controversy regarding injunctive relief . . . if unaccompanied by any\n\ncontinuing, present adverse effects,’” a plaintiff seeking “declaratory or injunctive relief .\n\n. . must establish an ongoing or future injury in fact.” Id. at 287–88 (quoting O’Shea v.\n\nLittleton, 414 U.S. 488, 495–96 (1974)). Significantly, this Court—along with several\n\nother circuits—has held that “standing requirements are somewhat relaxed in First\n\nAmendment cases,” particularly regarding the injury-in-fact requirement. Cooksey v.\n\nFutrell, 721 F.3d 226, 235 (4th Cir. 2013) (collecting cases).\n\n In Kenny v. Wilson, 885 F.3d 280 (4th Cir. 2018), this Court addressed what\n\nevidence a plaintiff seeking relief under the First Amendment, like Davison, must put\n\nforward to establish a future injury-in-fact adequate to confer Article III standing to\n\nobtain prospective declaratory relief. In Kenny, several high school students lodged First\n\nAmendment challenges to two South Carolina disorderly conduct statutes. Id. at 284.\n\nThis Court explained that “there is a sufficiently imminent injury in fact if plaintiffs\n\nallege [1] ‘an intention to engage in a course of conduct arguably affected with a\n\nconstitutional interest, but proscribed by a statute, and [2] there exists a credible threat of\n\nprosecution thereunder.’” Id. at 288 (quoting Babbitt v. Farm Workers Nat’l Union, 442\n\n\n 14\n\nU.S. 289, 298 (1979)). The Kenny plaintiffs satisfied the first prong because they “attend\n\nschool” and “attending school inevitably involves expressive conduct” that implicates the\n\ndisorderly conduct statutes. Id. As to the second element—whether the students alleged\n\na “credible threat of future enforcement”—we held that such a threat exists so long as it\n\n“is not imaginary or wholly speculative, chimerical, or wholly conjectural.” Id. (internal\n\nquotation marks, citations, and alterations omitted). “[P]ast enforcement against the same\n\nconduct is good evidence that the threat of enforcement is not chimerical.” Id. (quoting\n\nSusan B. Anthony List v. Driehaus, 134 S. Ct. 2334, 2345 (2014)). “Threat of\n\nprosecution is especially credible when defendants have not ‘disavowed enforcement’ if\n\nplaintiffs engage in similar conduct in the future.” Id. (quoting Driehaus, 134 S. Ct. at\n\n2345). Applying this standard, we held that the plaintiffs alleged a credible threat of\n\nenforcement “because these three plaintiffs regularly attend schools where they allege\n\nthere may be future encounters with school resource officers or other law enforcement;\n\nthey have been prosecuted under the laws in the past; and the defendants have not\n\ndisavowed enforcement if plaintiffs engage in similar conduct in the future.” Id. at 289.\n\n Under Kenny, Davison’s evidence established his standing to obtain prospective\n\ndeclaratory relief. Relevant to the first prong—whether Davison intends to engage in a\n\ncourse of conduct “arguably” impacted by the challenged conduct, Babbitt, 442 U.S. at\n\n298—the district court found, in awarding Davison declaratory relief, that he “continues\n\nto avail himself” of the Chair’s Facebook Page and that Davison is “active in local\n\npolitics, and has a particular interest in what he believes to be corruption on the part of\n\nLoudoun County’s school board.” Davison, 267 F. Supp. 3d at 707, 723. Accordingly,\n\n\n 15\n\nthe evidence establishes that Davison continues to engage in a course of conduct—\n\nnamely, posting about alleged municipal corruption on the Chair’s Facebook Page—\n\nlikely to be impacted by Randall’s allegedly unconstitutional approach to managing the\n\npage.\n\n Turning to the second prong—whether there is a credible threat of enforcement—\n\nRandall previously blocked Davison from the Chair’s Facebook Page based on the\n\ncontent of his posts, providing “good evidence that the threat of enforcement is not\n\nchimerical.” Driehaus, 134 S. Ct. at 2345 (internal quotation marks omitted).\n\nAdditionally, Randall testified that she continues to believe she can ban Davison and\n\nothers from the Chair’s Facebook Page based on their views without triggering the First\n\nAmendment at all. See J.A. 277 (Randall stating she would “be happy to” ban other\n\ncommenters on her “Chair’s Facebook” page); J.A. 250 (Randall testifying that\n\ncomments “attacking another person” would not be allowed on her “Chair’s Facebook”\n\npage). To that end, in awarding Davison declaratory relief, the district court found that\n\nRandall “maintains she is permitted to administer this Facebook page as a purely personal\n\npage.” Davison, 267 F. Supp. 3d at 723. Accordingly, Davison established that he has\n\nbeen subject to past enforcement and that Randall has not “disavowed” future\n\nenforcement, which, under Kenny, is sufficient to establish a credible threat of\n\nenforcement. Cf. City of Lakewood v. Plain Dealer Pub. Co., 486 U.S. 750, 757 (1988)\n\n(“[T]he mere existence of the licensor’s unfettered discretion, coupled with the power of\n\nprior restraint, intimidates parties into censoring their own speech, even if the discretion\n\nand power are never actually abused.”).\n\n\n 16\n\n In sum, Davison’s evidence demonstrated—and the district court found—that\n\nDavison intends to continue to use the Chair’s Facebook Page and that Davison faces a\n\ncredible threat of future enforcement. See Davison, 267 F. Supp. 3d at 723.\n\nAccordingly, Davison adduced facts establishing an injury in fact sufficient to justify the\n\nprospective declaratory relief awarded by the district court.\n\n B.\n\n Next, Randall asserts that the district court erred in concluding, with regard to\n\nDavison’s individual capacity First Amendment claim, that Randall acted “under color of\n\nstate law,” as that phrase is used in Section 1983, in administering the Chair’s Facebook\n\nPage and banning Davison from that page. “This Court reviews judgments stemming\n\nfrom a bench trial under a mixed standard: factual findings are reviewed for clear error,\n\nwhereas conclusions of law are reviewed de novo.” Helton v. AT&T Inc., 709 F.3d 343,\n\n350 (4th Cir. 2013). Whether, under the undisputed facts, Randall acted under color of\n\nstate law is a legal question this Court reviews de novo. Rossignol v. Voorhaar, 316 F.3d\n\n516, 523 (4th Cir. 2003).\n\n To state a claim under Section 1983, a plaintiff must show that the alleged\n\nconstitutional deprivation at issue occurred because of action taken by the defendant\n\n“under color of . . . state law.” Philips v. Pitt Cty. Mem’l Hosp., 572 F.3d 176, 180 (4th\n\nCir. 2009). “The traditional definition of acting under color of state law requires that the\n\ndefendant in a § 1983 action have exercised power ‘possessed by virtue of state law and\n\nmade possible only because the wrongdoer is clothed with the authority of state law.’”\n\nWest v. Atkins, 487 U.S. 42, 49 (1988) (quoting United States v. Classic, 313 U.S. 299,\n\n\n 17\n\n326 (1941)). Section 1983’s “color-of-law prerequisite is synonymous with the more\n\nfamiliar state-action requirement” applicable to Fourteenth Amendment claims, “and the\n\nanalysis for each is identical.” Pitt Cty. Mem’l Hosp., 572 F.3d at 180. Both inquiries\n\ndemand that “the conduct allegedly causing the deprivation of a federal right be fairly\n\nattributable to the State.” Holly v. Scott, 434 F.3d 287, 292 (4th Cir. 2006) (quoting\n\nLugar v. Edmondson Oil Co., Inc., 457 U.S. 922, 937 (1982)).\n\n “[T]here is no specific formula for determining whether state action is present.”\n\nId. at 292 (internal quotation marks omitted). Rather, “[w]hat is fairly attributable [to the\n\nstate]”—i.e., what constitutes action under color of state law—“is a matter of normative\n\njudgment, and the criteria lack rigid simplicity.” Id. (internal quotation marks omitted).\n\nCourts must examine the “totality of the circumstances,” id. (internal quotation marks\n\nomitted), to determine if the action at issue “bore a ‘sufficiently close nexus’ with the\n\nState to be ‘fairly treated as that of the State itself,’” Rossignol, 316 F.3d at 525 (quoting\n\nJackson v. Metro. Edison Co., 419 U.S. 345, 351 (1974)).\n\n Although no one factor is determinative, this Court has held that a defendant’s\n\npurportedly private actions bear a “sufficiently close nexus” with the State to satisfy\n\nSection 1983’s color-of-law requirement when the defendant’s challenged “actions are\n\nlinked to events which arose out of his official status.” Id. at 524. When a defendant’s\n\n“status” as a public official “enabled [her] to execute [a challenged action] in a manner\n\nthat private citizens never could have,” then the action also is more likely to be treated as\n\nattributable to the state. Id. at 526; see also Martinez v. Colon, 54 F.3d 980, 986 (1st Cir.\n\n1995) (“[S]ection 1983 is . . . implicated . . . [when] the conduct is such that the actor\n\n\n 18\n\ncould not have behaved in that way but for the authority of his office.”); Goldstein v.\n\nChestnut Ridge Volunteer Fire Co., 218 F.3d 337, 343 (4th Cir. 2000) (holding that\n\nchallenged conduct is more likely to amount to state action when “the injury caused is\n\naggravated in a unique way by the incidents of governmental authority” (internal\n\nquotation marks omitted)). Likewise, an official’s conduct is more likely to amount to\n\nstate action when it “occurs in the course of performing an actual or apparent duty of his\n\noffice.” Martinez, 54 F.3d at 986. And the challenged action of a defendant\n\ngovernmental official is likely to be treated as taken under color of law when the official\n\n“use[d] the power and prestige of his state office to damage the plaintiff.” Harris v.\n\nHarvey, 605 F.2d 330, 337 (7th Cir. 1979). In the context of an alleged First Amendment\n\nviolation, in particular, this Court has found that a challenged action by a governmental\n\nofficial is fairly attributable to the state when “the sole intention” of the official in taking\n\nthe action was “to suppress speech critical of his conduct of official duties or fitness for\n\npublic office.” Rossignol, 316 F.3d at 524.\n\n Here, after thoroughly analyzing the totality of the circumstances surrounding\n\nRandall’s creation and administration of the Chair’s Facebook Page and banning of\n\nDavison from that page, the district court concluded that Randall acted under color of\n\nstate law. Davison, 267 F. Supp. 3d at 723. We agree.\n\n Randall created and administered the Chair’s Facebook Page to further her duties\n\nas a municipal official. She used the Chair’s Facebook Page “as a tool of governance,”\n\nid. at 713: through the Chair’s Facebook Page, Randall provides information to the public\n\n\n\n\n 19\n\nabout her and the Loudoun Board’s official activities and solicits input from the public on\n\npolicy issues she and the Loudoun Board confront. See supra Part I.A.\n\n For instance, Randall used the Chair’s Facebook Page to inform the public about\n\nserious public safety events and to keep her constituents abreast of the County’s response\n\nto a snowstorm and to coordinate snow removal activities. And, as the district court\n\ncorrectly emphasized, Randall\n\n swathe[d] the [Chair’s Facebook Page] in the trappings of her office.\n Among other things, (1) the title of the page includes [Randall]’s title; (2)\n the page is categorized as that of a government official; (3) the page lists as\n contact information [Randall]’s official County email address and the\n telephone number of [Randall]’s County office; (4) the page includes the\n web address of [Randall]’s official County website; (5) many—perhaps\n most—of the posts are expressly addressed to “Loudoun,” [Randall]’s\n constituents; (6) [Randall] has submitted posts on behalf of the [Loudoun\n Board] as a whole; (7) [Randall] has asked her constituents to use the\n [Chair‘s Facebook Page] as a channel for “back and forth constituent\n conversations”; and (8) the content posted has a strong tendency toward\n matters related to [Randall]’s office.\n\nDavison, 267 F. Supp. 3d at 714. A private citizen could not have created and used the\n\nChair’s Facebook Page in such a manner. Rossignol, 316 F.3d at 526. Put simply,\n\nRandall clothed the Chair’s Facebook Page in “the power and prestige of h[er] state\n\noffice,” Harris, 605 F.2d at 337, and created and administered the page to “perform[]\n\nactual or apparent dut[ies] of h[er] office,” Martinez, 54 F.3d at 986.\n\n Additionally, the specific actions giving rise to Davison’s claim—Randall’s\n\nbanning of Davison’s Virginia SGP Page—“are linked to events which arose out of h[er]\n\nofficial status.” Rossignol, 316 F.3d at 524. Randall’s post to the Chair’s Facebook Page\n\nthat prompted Davison’s comment informed the public about what happened at the\n\n\n\n 20\n\nLoudoun Board and Loudoun County School Board’s joint meeting. And Davison’s\n\ncomment also dealt with an issue related to that meeting and of significant public\n\ninterest—School Board members’ alleged conflicts of interest in approving financial\n\ntransactions. That Randall’s ban of Davison amounted to an effort “to suppress speech\n\ncritical of [such members’] conduct of [their] official duties or fitness for public office”\n\nfurther reinforces that the ban was taken under color of state law. Id. at 525. Considering\n\nthe totality of these circumstances, the district court correctly held that Randall acted\n\nunder color of state law in banning Davison from the Chair’s Facebook Page.\n\n C.\n\n Third, Randall argues that the district court erred in ruling in Davison’s favor on\n\nhis individual capacity First Amendment claim against Randall. Randall principally\n\nchallenges the district court’s conclusion that the Chair’s Facebook Page constitutes a\n\n“public forum” under traditional First Amendment law. We review this legal question de\n\nnovo. See Helton, 709 F.3d at 350.\n\n Under long-established First Amendment law, governmental entities are “strictly\n\nlimited” in their ability to regulate private speech in public fora. Pleasant Grove City,\n\nUtah v. Summum, 555 U.S. 460, 469 (2009). The Supreme Court has recognized two\n\ncategories of public fora: “traditional public forums” and “limited (or designated) public\n\nforums.” Am. Civil Liberties Union v. Mote, 423 F.3d 438, 443 (4th Cir. 2005).\n\n“Traditional” public forums—“such as streets, sidewalks, and parks”—“have the\n\ncharacteristics of a public thoroughfare, a purpose that is compatible with expressive\n\nconduct, as well as a tradition and history of being used for expressive public conduct.”\n\n\n 21\n\nId. “Limited” or “designated” forums are forums that are “not traditionally public, but\n\n[that] the government has purposefully opened to the public, or some segment of the\n\npublic, for expressive activity.” Id. Accordingly, the hallmark of both types of public\n\nfora—what renders the fora “public”—is that the government has made the space\n\navailable—either by designation or long-standing custom—for “expressive public\n\nconduct” or “expressive activity,” and the space is compatible with such activity. Id.\n\n“Conversely, a non-public forum is one that has not traditionally been open to the public,\n\nwhere opening it to expressive conduct would ‘somehow interfere with the objective use\n\nand purpose to which the property has been dedicated.’” Id. (quoting Warren v. Fairfax\n\nCty., 196 F.3d 186, 190–91 (4th Cir. 1999)).\n\n Although neither the Supreme Court nor any Circuit has squarely addressed\n\nwhether, and in what circumstances, a governmental social media page—like the Chair’s\n\nFacebook Page—constitutes a public forum, 3 aspects of the Chair’s Facebook Page bear\n\nthe hallmarks of a public forum. Randall “intentionally open[ed the public comment\n\nsection of the Chair’s Facebook Page] for public discourse,” Cornelius v. NAACP Legal\n\nDefense & Educ. Fund, Inc., 473 U.S. 788, 802 (1985), inviting “ANY Loudoun citizen”\n\n 3\n In addition to the court below, two other district courts have considered whether\na government official’s social media page constituted a public forum. Those courts\nreached conflicting results. Compare Morgan v. Bevin, 298 F. Supp. 3d 1003, 1010 (E.D.\nKy. 2018) (holding that First Amendment forum analysis did not apply to restrictions on\nspeech in the official Facebook and Twitter pages of the Governor of Kentucky), with\nKnight First Amend. Inst. at Colum. Univ. v. Trump, 302 F. Supp. 3d 541, 573 (S.D.N.Y.\n2018) (holding that the interactive component of the President’s Twitter account, as\nopposed to the President’s tweets themselves, constituted a designated public forum),\nappeal docketed, No. 18-1691 (2d Cir. Oct. 24, 2018).\n\n\n\n 22\n\nto make posts to the comments section of the Chair’s Facebook Page—the interactive\n\ncomponent of the page—“on ANY issues, request, criticism, complement or just your\n\nthoughts,” J.A. 455. Randall placed no restrictions on the public’s access to the page or\n\nuse of the interactive component of the Chair’s Facebook Page. And, in accordance with\n\nRandall’s invitation, the public made numerous posts on matters of public concern.\n\n The Chair’s Facebook Page also is “compatib[le] with expressive activity.”\n\nCornelius, 473 U.S. at 802. “Congress [has] recognized the internet and interactive\n\ncomputer services as offering ‘a forum for a true diversity of political discourse, unique\n\nopportunities for cultural development, and myriad avenues for intellectual activity.’”\n\nZeran v. Am. Online, Inc., 129 F.3d 327, 330 (4th Cir. 1997) (quoting 47 U.S.C. §\n\n230(a)(3)); cf. Bland, 730 F.3d at 386 (finding post to campaign Facebook page\n\n“constituted pure speech”). And the Supreme Court recently analogized social media\n\nsites, like the Chair’s Facebook Page, to “traditional” public forums, characterizing the\n\ninternet as “the most important place[] (in a spatial sense) for the exchange of views.”\n\nPackingham v. North Carolina, 137 S. Ct. 1730, 1735 (2017). An “exchange of views”\n\nis precisely what Randall sought—and what in fact transpired—when she expressly\n\ninvited “ANY Loudoun citizen” to visit the page and comment “on ANY issues,” and\n\nreceived numerous such posts and comments. J.A. 455.\n\n Randall nevertheless argues that traditional public forum analysis should not apply\n\nto the Chair’s Facebook Page for two reasons: (1) the Chair’s Facebook Page is “a private\n\nwebsite” and therefore does not constitute “public property” susceptible to forum\n\nanalysis, and (2) the Chair’s Facebook Page, in its entirety, constitutes “government\n\n\n 23\n\nspeech” properly analyzed under the framework set forth in Pleasant Grove. Randall’s\n\nBr. at 19–21, 29–31. We disagree.\n\n Even assuming the intangible space at issue is “private property,” as Randall\n\nclaims—which is not at all clear from the record before us 4—the Supreme Court never\n\nhas circumscribed forum analysis solely to government-owned property. For example, in\n\nCornelius, the Court recognized that forum analysis applies “to private property\n\ndedicated to public use.” Cornelius, 473 U.S. at 801 (emphasis added); see also\n\nChristian Legal Soc’y Chapter of the Univ. of Cal. v. Martinez, 561 U.S. 661, 679 (2010)\n\n(“[T]his Court has employed forum analysis to determine when a governmental entity, in\n\nregulating property in its charge, may place limitations on speech.” (emphasis added)).\n\n 4\n The Facebook “platform” and the “software” that underlies that platform is,\naccording to Facebook’s Terms of Service, property of Facebook, Inc. Terms of Service,\nFacebook, https://www.facebook.com/terms.php (last visited Jan. 4, 2019). Facebook’s\nTerms of Service further provide that users “own the content [they] create and share on\nFacebook and the other Facebook Products,” including Pages. Id. There would seem to\nbe a good argument, therefore, that content created, and posted to Facebook, by\ngovernment officials performing the functions and duties of their offices constitutes\ngovernment property. Cf. Solomons v. United States, 137 U.S. 342, 346–48 (1890)\n(holding that intellectual property created by government employee in the course of his\nofficial duties constituted government property because “[i]f one is employed to devise or\nperfect an instrument, or a means for accomplishing a prescribed result, he cannot, after\nsuccessfully accomplishing the work for which he was employed, plead title thereto as\nagainst his employer”). Likewise, under Facebook’s Terms of Service, the posts and\ncomments by individual Facebook users—like Davison—to a Facebook Page—like the\nChair’s Facebook Page—constitute property of those users. Accordingly, a single\nFacebook Page—including the Chair’s Facebook Page—encompasses a web of property\nrights, some of which may lie with the government. We need not—and thus do not—\ndecide with whom these property rights lie in this particular case, however, because we\nhold that even assuming the Chair’s Facebook Page constitutes private property, Randall,\nacting under color of state law, exercised control over the aspects of that page giving rise\nto Davison’s claim.\n\n\n\n 24\n\nAnd the Supreme Court and lower courts have held that private property, whether\n\ntangible or intangible, constituted a public forum when, for example, the government\n\nretained substantial control over the property under regulation or by contract. See, e.g.,\n\nSe. Promotions, Ltd. v. Conrad, 420 U.S. 546, 547, 555 (1975) (holding that “a privately\n\nowned Chattanooga theater under long-term lease to the city” was a “public forum[]\n\ndesigned for and dedicated to expressive activities”); Halleck v. Manhattan Community\n\nAccess Corp., 882 F.3d 300, 306–07 (2d Cir. 2018) (holding that public access television\n\nchannels operated by a private non-profit corporation constituted public forums), cert.\n\ngranted 139 S. Ct. 360 (2018) (mem.); First Unitarian Church of Salt Lake City v. Salt\n\nLake City Corp., 308 F.3d 1114, 1122 (10th Cir. 2002) (“[F]orum analysis does not\n\nrequire that the government have a possessory interest in or title to the underlying land.\n\nEither government ownership or regulation is sufficient for a First Amendment forum of\n\nsome kind to exist.”); Freedom from Religion Foundation, Inc. v. City of Marshfield,\n\nWis., 203 F.3d 487, 494 (7th Cir. 2000) (holding that private property abutted by public\n\npark constituted public forum).\n\n Significantly, even assuming the relevant aspects of the Chair’s Facebook Page\n\nconstitute private property—which, again, is not entirely clear from the record before\n\nus—Randall, acting under color of state law, retained and exercised significant control\n\nover the page. She created the Chair’s Facebook Page. She designated the page as\n\nbelonging to a “governmental official.” She clothed the page in the trappings of her\n\npublic office. She chose to list her official contact information on the page. And she\n\n\n\n\n 25\n\ncurated the links in the left column of the page and the lists of Facebook Pages or profiles\n\n“liked” by the Chair’s Facebook Page in the right column.\n\n Of particular importance, Randall had complete control over the aspect of the\n\nChair’s Facebook Page giving rise to Davison’s challenge because, as administrator of\n\nthe page, Randall had authority to ban Facebook profiles or Pages from using the Chair’s\n\nFacebook Page—and, therefore, the interactive component of the page—authority she\n\nexercised in banning Davison’s Virginia SGP Page. Cf. Knight, 302 F. Supp. 3d at 566–\n\n67 (holding that the interactive component of the President’s Twitter account constituted\n\npublic forum because the President and his advisors “exercise control over various\n\naspects of the . . . account,” including the power to block other users from accessing the\n\naccount).\n\n The Second Circuit’s decision in Halleck dealing with privately operated public\n\naccess television channels is instructive. Federal law allows cable franchising authorities\n\nto require cable operators to designate channel capacity for public use. Halleck, 882 F.3d\n\nat 302. Likewise, New York regulations oblige cable operators to designate at least one\n\nchannel for full-time public use. Id. Pursuant to that authority, the City of New York\n\nentered into a cable franchise agreement with a cable company requiring the company to\n\nmake available four public access channels, which channels were operated by a private,\n\nnon-profit corporation, MNN. Id. Several producers of public access programming sued\n\nMNN, alleging that MNN violated the producers’ First Amendment rights by indefinitely\n\nsuspending them from using the public access channels “because of disapproval of the\n\ncontent of a TV program” they had submitted for airing. Id.\n\n\n 26\n\n The Second Circuit concluded that the public access channels constituted a public\n\nforum, notwithstanding that they were operated by a private company. Id. at 306–08.\n\nThe court reached that conclusion for two reasons. First, it pointed to the similarities\n\nbetween public access channels and traditional public forums, like parks, describing “[a]\n\npublic access channel [a]s the electronic version of the public square.” Id. at 306.\n\nSecond, the court emphasized the extensive government involvement with, and control\n\nover, public access channels by virtue of the federal and state regulatory schemes. See id.\n\n(“[W]here, as here, federal law authorizes setting aside channels to be ‘the electronic\n\nmarketplace of ideas,’ state regulation requires cable operators to provide at least one\n\npublic access channel, a municipal contract requires a cable operator to provide four such\n\nchannels, and a municipal official has designated a private corporation to run those\n\nchannels, those channels are public forums.” (emphasis added)).\n\n Although not subject to the extensive federal and state regulatory regime\n\napplicable in Halleck, 5 the Chair’s Facebook Page is in many ways analogous to the\n\nprivately-operated public access channels considered by the Second Circuit. Just as the\n\nfederal government sought to establish an “electronic marketplace of ideas” by\n\nmandating provision of public access channels, Randall expressly sought to—and did, in\n\n\n 5\n The federal Communications Decency Act allows private online intermediaries,\nlike Facebook, the ability to moderate content by providing such intermediaries with\nbroad immunity from user-generated content posted on their sites. 47 U.S.C. § 230. This\nCourt has recognized that an “important purpose of § 230 was to encourage service\nproviders to self-regulate the dissemination of offensive material over their services.”\nZeran, 129 F.3d at 331.\n\n\n\n 27\n\nfact—create an “electronic marketplace of ideas” by inviting “ANY” constituent to post\n\nto the Chair Page on “ANY issues.” J.A. 455. Likewise, just as the City of New York\n\nchose to have a private corporation operate the public access channels, Randall chose to\n\ncreate her electronic marketplace of ideas, the Chair’s Facebook Page, on a private\n\nplatform, Facebook. Indeed, the present case provides a stronger basis for treating the\n\ninteractive component of the Chair’s Facebook Page as a public forum because whereas\n\nthe private corporation in Halleck, MNN, exercised control over the aspect of the public\n\naccess channel giving rise to the First Amendment claim—banning the public access\n\nprogram producer—a public official, Randall exercised unconstrained control over the\n\naspect of the Chair’s Facebook Page giving rise to Davison’s claim—banning of other\n\nFacebook profiles and Pages. 6\n\n\n 6\n On October 12, 2018, the Supreme Court granted MNN’s petition for writ of\ncertiorari in Halleck. 139 S. Ct. 360. MNN’s petition presented two questions: (1)\n“[w]hether the Second Circuit erred in rejecting th[e Supreme] Court’s state actor tests\nand instead creating a per se rule that private operators of public access channels are state\nactors subject to constitutional liability” and (2) “[w]hether the Second Circuit erred in\nholding—contrary to the Sixth and D.C. Circuits—that private entities operating public\naccess televisions stations are state actors for constitutional purposes where the state has\nno control over the private entity’s board or operations.” Petition for Writ of Certiorari i,\nManhattan Community Access Corp. v. Halleck, --- S. Ct. --- (No. 17-1702). MNN’s\nargument before the Supreme Court, therefore, focuses on the Second Circuit’s\ndetermination that MNN constituted a state actor, not the court’s determination that the\npublic access channels constituted a public forum.\n\n Although not identified as an issue on appeal, MNN’s petition also took issue with\nthe Second Circuit’s determination that the public access channels operated by MNN\nconstituted a public forum. But that contention was entirely derivative of its state action\nargument. In particular, MNN objected to the Second Circuit’s public forum conclusion\nonly because the public access channels were privately operated and because, in its\nopinion, the Second Circuit’s purportedly “categorical” holding that public access\n(Continued)\n\n 28\n\n Not only does case law contradict Randall’s argument that public forum analysis\n\nnever applies to private property, her argument also fails because it makes no legal sense\n\nto establish a bright-line rule that forum analysis applies only to government-owned\n\nproperty. Why, for example, should the First Amendment allow a municipality to engage\n\nin viewpoint discrimination in curating a public library branch in leased space but not\n\nallow the municipality to engage in such discrimination in a library branch on\n\nmunicipally owned property? Cf. Bd. of Educ., Island Trees Union Free Sch. Dist. No.\n\n26 v. Pico, 457 U.S. 853, 870–71 (1982) (plurality op.) (“If a Democratic school board,\n\nmotivated by partisan affiliation, ordered removal of all books written by or in favor of\n\nRepublicans, few would doubt that the order violated the constitutional rights of the\n\nstudents denied access to those books.”). Or why should a municipality be allowed to\n\nengage in viewpoint discrimination when holding a virtual public meeting hosted on a\n\nprivate website when such discrimination would be unconstitutional if the meeting was\n\nheld in a governmental building? Cf. Lyrissa Lidsky, Public Forum 2.0, 91 B.U. L. Rev.\n\n1975, 1996 (2011) (“Just as the government can rent a building to use as a forum for\n\npublic debate and discussion, so, too, can it ‘rent’ a social media page for the promotion\n\n\n\nchannels constitute public forums ignore[d] “the far more critical issue of whether (and to\nwhat extent) there is government control over a public access channel.” Id. at 19–20.\n\n Here, a government official acting under color of state law, Randall, exercised\nunconstrained control over the aspect of the Chair’s Facebook Page giving rise to\nDavison’s claim.\n\n\n\n\n 29\n\nof public discussion.”). We do not believe the First Amendment draws such arbitrary\n\nlines.\n\n Randall’s second argument—that the Chair’s Facebook Page amounts to\n\n“government speech”—fails to recognize the meaningful difference between Randall’s\n\nposts to the Chair’s Facebook Page and the public comments and posts she invited in the\n\npage’s interactive space. To be sure, Randall’s comments and curated references on the\n\nChair’s Facebook Page to other Pages, personal profiles, and websites amount to\n\ngovernmental speech. See Sutliffe v. Epping School Dist., 584 F.3d 314, 329–30 (1st Cir.\n\n2009) (holding that municipality’s refusal to place hyperlink on municipal website to\n\nwebsite of group opposed to municipal budget constituted government speech); Page v.\n\nLexington Cty. School Dist. One, 531 F.3d 275, 283–85 (4th Cir. 2008) (holding that\n\nSchool District’s refusal to place hyperlink on its website to website of group that\n\nopposed School District’s position on pending legislation constituted government speech\n\nbecause, in part, “the links to other websites were selected by the School District alone as\n\nones that supported its own message”); Knight, 302 F. Supp. 3d at 571 (“[T]he\n\nPresident’s tweets are [not] susceptible to forum analysis . . . because the content is\n\ngovernment speech.”).\n\n But the interactive component of the Chair’s Facebook Page—the portion of the\n\nmiddle column in which the public can post comments, reply to posts, and “like”\n\ncomments and posts—is materially different. See Knight, 302 F. Supp. 3d at 572\n\n(distinguishing a government official’s tweets and “the interactive space for replies and\n\nretweets”). Randall placed no formal limitations on the ability of Facebook personal\n\n\n 30\n\nprofiles and Pages to access the Chair’s Facebook Page and make comments and posts to\n\nthe interactive component of the page. On the contrary, she expressly invited posts to the\n\npage “from ANY Loudon citizen on ANY issues, request, criticism, complement or just\n\nyour thoughts.” J.A. 455. And comments and posts by users cannot be mistaken for\n\nRandall’s own speech because they identify the posting or replying personal profile or\n\nPage, and thereby distinguish that user from Randall.\n\n Contrary to Randall’s argument that the Chair’s Facebook Page, in its entirety,\n\namounts to government speech, the present case also is meaningfully distinguishable\n\nfrom the government speech framework identified in Pleasant Grove. There, a\n\nmunicipality denied a private religious group’s request to allow it to erect a “monument\n\nin a city park in which other donated monuments were previously erected,” including a\n\nmonument depicting a prominent symbol of a different religion. 555 U.S. at 464. The\n\nplaintiff religious group sought relief under the First Amendment, arguing that the city\n\npark constituted a traditional public forum, and therefore that the city could not reject the\n\nreligious group’s proposed monument when it had previously allowed construction of a\n\nmonument associated with another religion. Id. at 466.\n\n The Supreme Court held that the city did not violate the First Amendment because\n\nthe government speech framework, rather than forum analysis, applied to the conduct at\n\nissue. In reaching that conclusion, the Court emphasized that the city never “opened up\n\nthe Park for the placement of whatever permanent monuments might be offered by\n\nprivate donors.” Id. at 472–73. “Rather, the City has ‘effectively controlled’ the\n\nmessages sent by the monuments in the Park by exercising ‘final approval authority’ over\n\n\n 31\n\ntheir selection.” Id. at 473. The Court further emphasized that “[t]he forum doctrine has\n\nbeen applied in situations in which government-owned property or a government\n\nprogram was capable of accommodating a large number of public speakers without\n\ndefeating the essential function of the land or the program.” Id. at 478. A city park,\n\nhowever, “can accommodate only a limited number of permanent monuments,” and\n\ntherefore a municipality cannot—and need not—provide park space for all who wish to\n\nerect a monument. Id.\n\n Here, Randall “effectively controlled” certain aspects of the Chair’s Facebook\n\nPage: she curated the Chair’s Facebook Page’s left and right columns and made posts to\n\nthe middle column. Id. at 472. But Randall also expressly opened the Chair’s Facebook\n\nPage’s middle column—its interactive space—for “ANY” user to post on “ANY issues,”\n\nJ.A. 455, and therefore did not retain “final approval authority” over that aspect of the\n\nChair’s Facebook Page, Pleasant Grove, 555 U.S. at 473. Just as the parkland\n\nsurrounding monuments in Pleasant Grove continued to constitute a public forum, even\n\nthough the monuments themselves constituted government speech, so too the interactive\n\ncomponent of the Chair’s Facebook Page constitutes a public forum, even though\n\nRandall’s curation of and posts to the Chair’s Facebook Page amount to government\n\nspeech. Additionally, the interactive component of the Chair’s Facebook Page does not\n\nface the same spacial limitations as those of the park in Pleasant Grove, but instead is\n\n“capable of accommodating a large number of public speakers without defeating [its]\n\nessential function.” Id. at 578. Accordingly, Pleasant Grove supports, rather than\n\n\n\n\n 32\n\nundermines, our conclusion that the interactive component of the Chair’s Facebook Page\n\nconstitutes a public forum.\n\n Upon concluding that interactive component of the Chair’s Facebook Page\n\namounts to a public forum, we would normally need to determine whether it constitutes a\n\ntraditional public forum or designated or limited public forum. In the present case,\n\nhowever, we need not decide that question because Randall’s ban of Davison amounted\n\nto “viewpoint discrimination,” which is “prohibited in all forums.” See Child Evangelism\n\nFellowship of S.C. v. Anderson Sch. Dist. Five, 470 F.3d 1062, 1067 n.2 (4th Cir. 2006).\n\n“Viewpoint discrimination . . . ‘targets not subject matter, but particular views taken by\n\nspeakers on a subject.’” Id. (quoting Rosenberger v. Rector & Visitors of Univ. of Va.,\n\n515 U.S. 819, 829 (1995)). Viewpoint discrimination is apparent, for example, if a\n\ngovernment official’s decision to take a challenged action was “impermissibly motivated\n\nby a desire to suppress a particular point of view.” Cornelius, 473 U.S. at 812–13.\n\n Here, the district court found—as the record amply supports—that Randall banned\n\nDavison’s Virginia SGP Page because Davison posted a comment using that page\n\nalleging “corruption on the part of Loudoun County’s School Board involving conflicts\n\nof interests among the School Board and their family members.” Davison, 267 F. Supp.\n\n3d at 711. Although Randall stated that she had “no idea” whether Davison’s allegations\n\nwere “correct,” she nonetheless banned him because she viewed the allegations as\n\n“slanderous” and she “didn’t want [the allegations] on the site.” Id. at 717. Randall’s\n\ndecision to ban Davison because of his allegation of governmental corruption constitutes\n\nblack-letter viewpoint discrimination.\n\n\n 33\n\n Put simply, Randall unconstitutionally sought to “suppress” Davison’s opinion\n\nthat there was corruption on the School Board. Cornelius, 473 U.S. at 812–13; see also,\n\ne.g., Rossignol, 316 F.3d at 521 (holding that sheriff’s deputies engaged in viewpoint\n\ndiscrimination when they seized an issue of a newspaper that criticized the county\n\nsheriff’s and his deputies’ performance of their official duties); Putnam Pit, Inc. v. City of\n\nCookeville, Tenn., 221 F.3d 834, 846 (6th Cir. 2000) (holding that a municipality engages\n\nin viewpoint discrimination if it refuses to link newspaper webpage to the city’s website\n\nsolely because the newspaper sought to expose municipal corruption); Knight, 302 F.\n\nSupp. 3d at 575 (holding that the President engaged in viewpoint discrimination when he\n\nblocked individuals from his Twitter account because the individuals “posted tweets that\n\ncriticized the President or his policies”). 7 That Randall’s action targeted comments\n\ncritical of the School Board members’ official actions and fitness for office renders the\n\nbanning all the more problematic as such speech “occupies the core of the protection\n\nafforded by the First Amendment.” Rossignol, 316 F.3d at 521 (quoting McIntyre v.\n\nOhio Elections Comm’n, 514 U.S. 334, 346 (1995)).\n\n In sum, the interactive component of the Chair’s Facebook Page constituted a\n\npublic forum, and Randall engaged in unconstitutional viewpoint discrimination when\n\nshe banned Davison’s Virginia SGP Page from that forum.\n\n\n 7\n Randall also asserts that she did not violate Davison’s First Amendment rights\nbecause she banned his “Virginia SGP” Page, not his “Brian Davison” profile. Davison\nis the sole operator of the “Virginia SGP” Page, however, and therefore the ban\nimplicated his First Amendment rights. Randall fails to identify any case supporting her\nposition, nor have we found any. Accordingly, we reject this argument.\n\n\n 34\n\n III.\n\n In his cross-appeal, Davison asserts that the district court reversibly erred in two\n\nways: (A) by dismissing his claim against Randall in her official capacity and (B) by\n\ndenying his motion to amend his complaint to add the new First Amendment claim\n\nagainst the Loudoun Board. 8 We disagree.\n\n A.\n\n Davison first argues that the district court erred in dismissing his claim against\n\nRandall in her official capacity. Whereas “[p]ersonal-capacity suits seek to impose\n\npersonal liability upon a government official for actions [she] takes under color of state\n\nlaw,” Kentucky v. Graham, 473 U.S. 159, 165 (1985), “official capacity suits are ‘treated\n\nas suits against the municipality,’” Santos v. Frederick Cty. Bd. of Comm’rs, 725 F.3d\n\n451, 469 (4th Cir. 2013) (quoting Hafer v. Melo, 502 U.S. 21, 25 (1991)). Because\n\n“municipal liability under Section 1983 does not amount to respondeat superior . . . a\n\n 8\n Davison also argues that the district court erred in rejecting his procedural due\nprocess claims under the Fourteenth Amendment and an analogous provision in the\nVirginia Constitution. Before the district court, Davison “flatly asserted that due process\nalways requires the government to provide a hearing before imposing a prior restraint on\nspeech,” and therefore that Randall violated Davison’s First Amendment rights by failing\nto conduct a pre-ban hearing. Davison, 267 F. Supp. 3d at 719. The district court\ncorrectly rejected Davison’s proposed categorical rule. Id. (citing Cafeteria & Rest.\nWorkers Union Local 473, AFL-CIO v. McElroy, 367 U.S. 886, 895 (1961). And\nDavison has abandoned that asserted categorical rule on appeal, Davison’s Br. at 49–50\nn.19 (“[I]t might be permissible in certain contexts to delete an individual comment\nwithout providing full pre-deprivation process . . . .”), instead arguing he is entitled to\nrelief under the balancing test set forth in Mathews v. Eldridge, 424 U.S. 319, 334–35\n(1976). Because Davison did not make that argument before the district court, we decline\nto consider it now. See CoreTel Va., LLC v. Verizon Va., LLC, 808 F.3d 978, 988 (4th\nCir. 2015).\n\n\n\n 35\n\nmunicipality is subject to Section 1983 liability only when its ‘policy or custom, whether\n\nmade by its lawmakers or by those whose edicts or acts may fairly be said to represent\n\nofficial policy, inflicts the [plaintiff’s] injury.’” Id. at 469–70 (quoting Monell v. Dep’t of\n\nSoc. Servs. of the City of N.Y., 436 U.S. 658, 694 (1978)).\n\n Here, the district court dismissed Davison’s official capacity claim because it\n\nfound that “no policy—whether County-wide or specific to [Randall]’s office—played\n\nany role in [Randall]’s decision to ban [Davison] from her [Chair’s Facebook Page].”\n\nDavison, 267 F. Supp. 3d at 715. We review the district court’s factual findings bearing\n\non whether Randall acted pursuant to a municipal policy or custom for clear error and its\n\nlegal conclusions de novo. Helton, 709 F.3d at 350.\n\n On appeal, Davison does not dispute the district court’s finding—which the record\n\namply supports—that Loudoun County did not promulgate a policy governing individual\n\nLoudoun Board members’ Facebook pages. Rather, Davison principally 9 argues that “the\n\ncounty can be held liable for Randall’s actions because in banning Davison, Randall\n\nacted as a municipal policymaker.” Davison’s Br. at 47.\n\n\n\n\n 9\n Davison also argues the Loudoun Board’s failure to adopt a policy pertaining to\nindividual board members’ Facebook pages gives rise to an official capacity claim\nbecause it establishes that the Loudoun “Board was—and remains—deliberately\nindifferent to the likelihood of unconstitutional censorship and viewpoint-based\ndiscrimination on individual supervisors’ social media sites.” Davison’s Br. at 46. But\nDavison never advanced a “deliberate indifference” theory of municipal liability before\nthe district court. Again, we decline to consider an argument Davison raises for the first\ntime on appeal. See CoreTel, LLC, 808 F.3d at 988.\n\n\n\n 36\n\n Davison is correct that “municipal liability may be imposed for a single decision\n\nby municipal policymakers under appropriate circumstances.” Hunter v. Town of\n\nMocksville, N.C., 897 F.3d 538, 554 (4th Cir. 2018) (quoting Pembaur v. City of\n\nCincinnati, 475 U.S. 469, 480 (1986)). “[I]n assessing whether a municipality may be\n\nheld liable for constitutional or statutory violations of their decisionmakers, the\n\ntouchstone inquiry is whether ‘the decisionmaker possesses final authority to establish\n\nmunicipal policy with respect to the action ordered.’” Id. at 554–55 (emphasis added)\n\n(quoting Liverman v. City of Petersburg, 844 F.3d 400, 413 (4th Cir. 2016)).\n\n Here, Davison failed to put forward evidence establishing that Randall was a final\n\nmunicipal policymaker with regard to her banning of Davison from the Chair’s Facebook\n\nPage. On the contrary, record evidence establishes that the Loudoun Board retained\n\nauthority to establish municipal policy with respect to social media pages, as it adopted a\n\nsocial media policy governing the County’s official social media pages. Davison\n\nconcedes as much, arguing that the Loudoun Board “neglected . . . to extend its written\n\nguidelines to Board members’ official pages.” Davison’s Br. at 46. But that argument\n\npresupposes that the Loudoun Board—not Randall—had authority to establish municipal\n\npolicy with respect “to Board members’ official pages.”\n\n Davison nevertheless argues that the Loudoun Board “implicitly” delegated its\n\nfinal policymaking authority to Randall by not addressing individual Loudoun Board\n\nmembers’ official pages in its social media policy. Davison is correct that delegation of\n\nfinal policy making authority may be “implied from a continued course of knowing\n\nacquiescence by the governing body in the exercise of policymaking authority by an\n\n\n 37\n\nagency or official.” Id. at 48 (quoting Spell v. McDaniel, 824 F.2d 1380, 1387 (4th Cir.\n\n1987)). But Davison identifies no evidence that the Loudoun Board knew of the Chair’s\n\nFacebook Page, let alone that it “aquiesce[d]” in Randall’s administration of the page and\n\nbanning of Davison, in particular. On the contrary, the district court found that Randall\n\nmade a one-off, “unilateral decision to ban [Davison] in the heat of the moment, and\n\nreconsidered soon thereafter,” Davison, 267 F. Supp. 3d at 715—before the Loudoun\n\nBoard had a chance to learn of her action. In such circumstances, the district court did\n\nnot reversibly err in rejecting Davison’s official capacity claim.\n\n B.\n\n Next, Davison argues that the district court erred in denying him leave to amend\n\nhis complaint to add a claim that “the County violates the First Amendment by\n\nmaintaining a limited public forum on Facebook,” when policies imposed by Facebook,\n\nrather than the County, restrain, or have the potential to restrain, speech. J.A. 74. “A\n\ndistrict court may deny a motion to amend when the amendment would be prejudicial to\n\nthe opposing party, the moving party has acted in bad faith, or the amendment would be\n\nfutile.” Equal Rights Ctr. v. Niles Bolton Assocs., 602 F.3d 597, 603 (4th Cir. 2010).\n\nThe magistrate judge recommended—and the district court agreed—that Davison be\n\ndenied leave to amend on grounds of both futility and prejudice. We review for abuse of\n\ndiscretion a district court’s denial of leave to amend for prejudice, whereas we review de\n\nnovo a district court’s denial of leave to amend on the basis of futility. See U.S. ex rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n\n\n\n 38\n\n Regarding prejudice, the district court determined that the amendment came “too\n\nlate in these proceedings” and would “add a new, novel legal theory to the case after the\n\nclose of discovery, after the existing claims against [the Loudoun Board] have been\n\nshown to be meritless, after the point at which Defendants could have addressed the\n\nclaim in briefing before trial, and on the eve of trial.” J.A. 74. The district court did not\n\nabuse its discretion in denying leave to amend in such circumstances. See, e.g., Equal\n\nRights Ctr., 602 F.3d at 603–04 (holding that district court did not abuse its discretion in\n\ndenying leave to amend on the basis of prejudice when amendment came after the close\n\nof discovery and “on the eve of the deadline for dispositive motions” and therefore\n\n“would [have] change[d] the nature of the litigation”); Deasy v. Hill, 833 F.2d 38, 41 (4th\n\nCir. 1987) (affirming denial of leave to amend on grounds of prejudice when “the motion\n\nto amend came right before trial and after discovery was complete”).\n\n Although we affirm the district court’s judgment on the basis of its finding of\n\nprejudice, we do not concur in its conclusion as to futility. “Futility is apparent if the\n\nproposed amended complaint fails to state a claim under the applicable rules and\n\naccompanying standards.” Katyle v. Penn Nat. Gaming, Inc., 637 F.3d 462, 471 (4th Cir.\n\n2011). Accordingly, Davison’s proposed amendment was futile if the new claim would\n\nnot have survived a motion to dismiss under Federal Rule of Civil Procedure 12(b)(6).\n\nSee Runnion ex rel. Runnion v. Girl Scouts of Greater Chicago & Nw. Ind., 786 F.3d 510,\n\n524 (7th Cir. 2015) (“[W]hen the basis for denial is futility, we apply the legal\n\nsufficiency standard of Rule 12(b)(6) to determine whether the proposed amended\n\ncomplaint fails to state a claim.”).\n\n\n 39\n\n Davison’s proposed First Amendment claim deals not with the Chair’s Facebook\n\nPage—which the Loudoun Board did not authorize or attempt to regulate—but rather\n\nwith Loudoun County’s official Facebook Pages created and maintained pursuant to the\n\nLoudoun Board’s social media policy. As with his claims related to the Chair’s\n\nFacebook Page, Davison alleged that the Facebook Pages created and maintained by the\n\nLoudoun Board constituted public forums subject to the First Amendment. Davison\n\ntheorized that the Loudoun Board’s decision to use Facebook as its social media forum\n\nviolated his First Amendment rights because Facebook rules permit individual\n\n“requesting” users to ban other personal profiles and Pages such that the banned users can\n\nno longer see posts authored by the requesting users. In such circumstances, the banned\n\nusers “cannot see [the requesting user’s] comment[s] or participate in the discussion\n\nsurrounding the [requesting] party’s comment.” Davison’s Br. at 59. Davison’s\n\nproposed amended complaint asserted that “this scenario violates the First Amendment\n\nbecause Loudoun County has effectively enabled third parties to exclude discussion\n\nwithin a public forum—something a government body could not permissibly do in a\n\nphysical forum.” Id. at 59–60 (internal citation omitted). Put differently, Davison\n\ntheorized that Loudoun County violated the First Amendment by choosing to use\n\nFacebook as a public forum, when rules imposed by Facebook allow private users to\n\nrestrict access to their posts—and comments on and responses to those posts—including\n\nposts to any municipal Facebook Page.\n\n No court appears to have addressed that novel legal theory. And although the First\n\nAmendment constrains only government policies, not policies established by private\n\n\n 40\n\nentities, one can conceive of a colorable legal argument that a governmental actor’s\n\ndecision to select a private social media website for use as a public forum—and therefore\n\nselect that website’s suite of rules and regulations—could violate the First Amendment, if\n\nthe private website included certain types of exclusionary rules. For example, if the\n\ngovernment chose as its electronic public forum a social media site that allowed only\n\nregistered members of one political party to post and comment, there would seem to be a\n\ncompelling argument that the government’s selection of that social media site violated the\n\nFirst Amendment rights of members of other political parties, even if the partisan\n\nrestriction was imposed by the private company, not the governmental body. Such a\n\nrestriction would be seem to be no different than a municipality choosing to hold a town\n\nhall meeting in a venue that refused admission to individuals associated with a disfavored\n\npolitical party or viewpoint. Cf. DeBoer v. Village of Oak Park, 267 F.3d 558, 571 (7th\n\nCir. 2001) (“[T]he government engages in viewpoint discrimination when it denies access\n\nto a speaker solely to suppress the point of view he espouses on an otherwise includible\n\nsubject.”).\n\n Given that Davison’s proposed claim asserted a novel and colorable legal theory\n\nand that “Rule 12(b)(6) dismissals are especially disfavored in cases where the complaint\n\nsets forth a novel legal theory that can best be assessed after factual development,”\n\nWright v. North Carolina, 787 F.3d 256, 263 (4th Cir. 2015) (internal quotation marks\n\nomitted), we affirm the district court’s denial of Davison’s motion for leave to amend his\n\ncomplaint on the basis of its finding of prejudice but not on the basis of futility.\n\n IV.\n\n\n 41\n\nFor the foregoing reasons, we affirm the judgment of the district court.\n\n AFFIRMED\n\n\n\n\n 42\n[END_CASE]", "role": "user" } ]
4,580,037
6TH CONGRESSIONAL DISTRICT REPUBLICAN COMMITTEE, Plaintiff - Appellee, and Anne Taetzsch Fitzgerald, Individually and as Chairman of the 20th House of Delegates District Republican Committee; Karen U. Kwiatkowski, Individually; Edward A. Yensho, Individually and as Chairman of the Green County Republican Committee; 20th House of Delegates District Republican Committee, Plaintiffs, v. James B. ALCORN, in His Official Capacity as Chairman of the Virginia State Board of Elections ; Clara Belle Wheeler, in Her Official Capacity as Vice-Chairman of the Virginia State Board of Elections ; Singleton B. McAllister, in Her Official Capacity as Secretary of the Virginia State Board of Elections ; Virginia Department of Elections, Defendants - Appellants.
6th Congressional District v. James Alcorn
2019-01-09
18-1111
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Wilkinson, Motz, Duncan", "parties": "", "opinions": [{"author": "WILKINSON, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1111\n\n\n6TH CONGRESSIONAL DISTRICT REPUBLICAN COMMITTEE,\n\n Plaintiff – Appellee,\n\n and\n\nANNE TAETZSCH FITZGERALD, individually and as Chairman of the 20th\nHouse of Delegates District Republican Committee; KAREN U.\nKWIATKOWSKI, individually; EDWARD A. YENSHO, individually and as\nChairman of the Green County Republican Committee; 20TH HOUSE OF\nDELEGATES DISTRICT REPUBLICAN COMMITTEE,\n\n Plaintiffs,\n\n v.\n\nJAMES B. ALCORN, in his official capacity as Chairman of the Virginia State\nBoard of Elections; CLARA BELLE WHEELER, in her official capacity as Vice-\nChairman of the Virginia State Board of Elections; SINGLETON B.\nMCALLISTER, in her official capacity as Secretary of the Virginia State Board of\nElections; VIRGINIA DEPARTMENT OF ELECTIONS,\n\n Defendants - Appellants.\n\n\nAppeal from the United States District Court for the Western District of Virginia, at\nHarrisonburg. Michael F. Urbanski, Chief District Judge. (5:17-cv-00016-MFU-JCH)\n\n\nArgued: December 12, 2018 Decided: January 9, 2019\n\n\nBefore WILKINSON, MOTZ, and DUNCAN, Circuit Judges.\n\fAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge Motz\nand Judge Duncan joined.\n\n\nARGUED: Toby Jay Heytens, OFFICE OF THE ATTORNEY GENERAL OF\nVIRGINIA, Richmond, Virginia, for Appellants. Jeffrey R. Adams, WHARTON,\nALDHIZER & WEAVER, PLC, Harrisonburg, Virginia, for Appellee. ON BRIEF:\nMark R. Herring, Attorney General, Stephen A. Cobb, Deputy Attorney General,\nMatthew R. McGuire, Principal Deputy Solicitor General, Michelle S. Kallen, Deputy\nSolicitor General, OFFICE OF THE ATTORNEY GENERAL OF VIRGINIA,\nRichmond, Virginia, for Appellants. Charles F. Hilton, Thomas E. Ullrich, Lucas I.\nPangle, WHARTON ALDHIZER & WEAVER, PLC, Harrisonburg, Virginia; John C.\nWirth, NELSON MCPHERSON SUMMERS & SANTOS, Staunton, Virginia, for\nAppellee.\n\n\n\n\n 2\n\fWILKINSON, Circuit Judge:\n\n The 6th Congressional District Republican Committee argues that Virginia’s\n\nIncumbent Protection Act, Va. Code Ann. § 24.2-509(B), violates the First Amendment\n\nof the Constitution. The district court agreed and enjoined § 24.2-509(B) in its entirety.\n\nFor the reasons that follow, we now affirm.\n\n I.\n\n A.\n\n Virginia law generally allows the Commonwealth’s political parties considerable\n\ndiscretion in deciding how to nominate their candidates for office. Section 24.2-509(A)\n\nempowers the “duly constituted authorities” of the state and local parties “to determine\n\nthe method by which a party nomination . . . shall be made.” The parties make use of this\n\nlatitude. For example, the Republican Party of Virginia, with whom the appellee here is\n\naffiliated, allows for four different methods of nomination: a primary, a party canvass, a\n\nconvention, and a mass meeting. Fitzgerald v. Alcorn, 285 F. Supp. 3d 922, 927 (W.D.\n\nVa. 2018). Under the Party’s Plan of Organization, committees established in every\n\nlocality, state legislative district, and congressional district are empowered to choose\n\namong these methods to nominate candidates for their political subdivision. J.A. 37, 38,\n\n40.\n\n The differences between these methods are substantial. Each one “‘create[s] a\n\ndifferent distribution of potential voters (or decision makers) in the nomination process.’\n\nFor example, primaries involve the largest pool of potential voters, whereas conventions\n\nand mass meetings ‘lend themselves more toward committed partisans.’” Alcorn, 285 F.\n\n 3\n\fSupp. 3d at 935 (quoting J.A. 884-85, 885-86). The choice of method, therefore, could\n\nhave a significant influence on the choice of nominee.\n\n Subsection 24.2-509(B), often called the Incumbent Protection Act, however,\n\nlimits the broad authority recognized by subsection A. 1 The second and third sentences\n\napply to those subdivisions of the state party that select nominees for candidates to the\n\n\n1\n The full text of Virginia Code § 24.2-509 is reprinted below, with the sentences in\nsubsection B numbered for ease of reference:\n\nA. The duly constituted authorities of the state political party shall have the right to\n determine the method by which a party nomination for a member of the United States\n Senate or for any statewide office shall be made. The duly constituted authorities of\n the political party for the district, county, city, or town in which any other office is to\n be filled shall have the right to determine the method by which a party nomination for\n that office shall be made.\n\nB. [1] Notwithstanding subsection A, the following provisions shall apply to the\n determination of the method of making party nominations. [2] A party shall nominate\n its candidate for election for a General Assembly district where there is only one\n incumbent of that party for the district by the method designated by that incumbent, or\n absent any designation by him by the method of nomination determined by the party.\n [3] A party shall nominate its candidates for election for a General Assembly district\n where there is more than one incumbent of that party for the district by a primary\n unless all the incumbents consent to a different method of nomination. [4] A party,\n whose candidate at the immediately preceding election for a particular office other\n than the General Assembly (i) was nominated by a primary or filed for a primary but\n was not opposed and (ii) was elected at the general election, shall nominate a\n candidate for the next election for that office by a primary unless all incumbents of\n that party for that office consent to a different method.\n\n [5] When, under any of the foregoing provisions, no incumbents offer as candidates\n for reelection to the same office, the method of nomination shall be determined by the\n political party.\n\n [6] For the purposes of this subsection, any officeholder who offers for reelection to\n the same office shall be deemed an incumbent notwithstanding that the district which\n he represents differs in part from that for which he offers for election.\n\n\n 4\n\fGeneral Assembly. Those sentences allow incumbent members of the General Assembly\n\nwho are running for reelection, where there is only one incumbent, to “designate[]” the\n\nmethod of nomination they prefer. Under this statute, the wishes of the party are\n\nimmaterial; no matter where the party’s plan of organization may vest the power to\n\nchoose nomination methods, the law trumps, granting the power to the incumbent.\n\n The fourth sentence of the Act applies to those components of political parties that\n\nmake the nominations for “particular office[s]” other than for the General Assembly,\n\nincluding nominations for the U.S. House of Representatives. In these races, the\n\nincumbent officeholder may insist that his or her party use a primary as its nomination\n\nmethod as long as (1) the incumbent was selected by primary in the previous election\n\ncycle and (2) the incumbent is running for reelection. Again, the statute trumps the\n\nparty’s plan of organization, which, in this case allows the committees responsible for\n\ncongressional nominations to choose between the approved methods (excluding mass\n\nmeetings) without interference by the incumbent, J.A. 37.\n\n The Virginia Department of Elections, however, has not always respected the\n\ndistinction made between the second and third sentences on the one hand, and the fourth\n\nsentence on the other. In the 2016 and 2017 election cycles, for example, the Department\n\npromulgated forms that allowed non-General Assembly incumbents to “designate” their\n\npreferred method of nomination as if their elections were governed by the second and\n\nthird sentences. After the commencement of this litigation, and only after the appellees\n\npointed out the mistake, the Department issued new forms that applied the fourth\n\nsentences to these races.\n\n 5\n\f Virginia has not identified a single other state that has a statute like the Incumbent\n\nProtection Act, and this is not the first case to consider a constitutional challenge to it. In\n\n2007, for example, this court considered a challenge to the Act. Miller v. Brown, 503\n\nF.3d 360 (4th Cir. 2007) (“Miller II”). There, we held that an incumbent cannot\n\nconstitutionally force his or her party to use an open primary, as this would be an\n\nimpermissible burden on the party’s associational rights. Id. at 368-71. We did not,\n\nhowever, reach the different question of the constitutionality of incumbents’ statutory\n\npower to dictate any nomination method.\n\n B.\n\n This appeal stems from the 6th Congressional District Republican Committee’s\n\nchallenge to the Incumbent Protection Act under 42 U.S.C. § 1983. See Alcorn, 285 F.\n\nSupp. 3d at 922. The Committee is responsible for nominating candidates for the U.S.\n\nHouse of Representatives for the 6th Congressional District, which “covers much of the\n\nwest-central portion of Virginia, from Roanoke to Front Royal.” Id. at 927. Under the\n\nParty’s Plan of Organization, it is composed of the “District Chairman,” the “Unit\n\nChairman” (the chair of each relevant locality’s committee), the “District Representative\n\nof the Virginia Federation of Republican Women,” the “Young Republican Federation\n\nDistrict Committeeman,” the “College Republican Federation District Committeeman,”\n\nand the “District members of the State Central Committee.” J.A. 36-37. The Committee,\n\nalong with other plaintiffs who were dismissed from the suit and do not appeal, raised\n\nfacial and as applied challenges to the Incumbent Protection Act, claiming that it\n\nabridged their rights under the First and Fourteenth Amendments of the U.S.\n\n 6\n\fConstitution. The named defendants include the Virginia Department of Elections and the\n\nthree members of the Virginia State Board of Elections at the time the suit was filed.\n\nAlcorn, 285 F. Supp. 3d at 928.\n\n The district court, relying on Miller v. Brown, 462 F.3d 312 (4th Cir. 2006)\n\n(“Miller I”), found that the Committee had standing to challenge the Act. Alcorn, 285 F.\n\nSupp. 3d at 937. It then proceeded to evaluate the burden posed by § 24.2-509(B) on the\n\nCommittee’s associational rights, concluding that it was “severe” because it provided\n\n“incumbents with a statutory right to dictate political parties’ internal affairs . . . .” Id. at\n\n952. The burden was “especially” onerous because it trespassed on the “realm of\n\nselecting candidates.” Id. Given the magnitude of the burden, the district court found that\n\n“the Act can survive constitutional scrutiny only if it is ‘narrowly tailored to advance a\n\ncompelling state interest.’” Id. (quoting Burdick v. Takushi, 504 U.S. 428, 433 (1992)).\n\nThe district court ultimately concluded that the Act did not survive such scrutiny. Id. at\n\n953.\n\n The district court thus permanently enjoined enforcement of the entire Incumbent\n\nProtection Act on January 19, 2018. J.A. 1473. The court enjoined all six sentences of\n\n§ 24.2-509(B) because, according to the court, the second and third sentences—which\n\nprotect the nomination prerogatives of incumbent General Assembly members—could\n\nnot be severed from the fourth—which protects the nomination prerogatives of, inter alia,\n\nmembers of Congress. The court additionally found that the Committee had standing to\n\nchallenge the second and third sentences under the overbreadth doctrine. Alcorn, 285 F.\n\nSupp. 3d at 955. Finally, the district court concluded that the Act had “no legitimate\n\n 7\n\fsweep” and so a facial challenge to all its provisions was appropriate. Id. at 955-56. After\n\nthe notice of appeal had been filed, the district court stayed its permanent injunction order\n\non February 5, 2018, to avoid interfering with the ongoing nomination cycle. J.A. 1481.\n\nAfter that cycle concluded, however, the district court vacated its stay on September 24,\n\n2018. J.A. 1680. During the course of this appeal, the Department filed a motion to\n\nvacate the injunction on the basis of mootness. We held that motion in abeyance pending\n\noral argument, and both parties expanded on their arguments in their briefing on the\n\nmerits.\n\n II.\n\n The district court found that the fourth sentence of the Incumbent Protection Act,\n\nwhich protects the nomination prerogatives of incumbent members of Congress among\n\nothers, violated the First Amendment. Because this provision imposes a severe burden on\n\nthe associational rights of Virginia’s political parties, and because the Commonwealth\n\nhas been unable to show that it is narrowly tailored to serve a compelling state interest,\n\nwe agree.\n\n A.\n\n Freedom of association has, for centuries, been at the heart of the American\n\nsystem of government and individual rights. In 1831, when Alexis de Tocqueville arrived\n\nin the United States, he was shocked to discover that our nation was the only “country on\n\nthe face of the earth where the citizens enjoy unlimited freedom of association for\n\npolitical purposes.” Alexis de Tocqueville, 2 Democracy in America 123 (Henry Reeves\n\ntrans., 1863). In America, “the most democratic country on the face of the earth,” the\n\n 8\n\f“art” of forming political associations had been “carried to the highest perfection.” Id. at\n\n115. Because of this, “Americans of all ages, all conditions, and all dispositions,\n\nconstantly form associations.” Id. at 114.\n\n De Tocqueville identified this propensity to associate as one of the sources of the\n\nastonishing political dynamism of the young Republic, writing that American political\n\nassociations are “the mother of action,” id. at 125, and that they “stimulate competition,\n\nand . . . discover those arguments which are most fitted to act upon the majority.” Id. at\n\n210. The right to associate for political purposes, de Tocqueville proclaimed, is “[t]he\n\nmost natural privilege of man, next to the right of acting for himself.” Id. at 209.\n\nAccordingly, “the right of association is almost as inalienable as the right of personal\n\nliberty. No legislator can attack it without impairing the very foundations of society.” Id.\n\n The multiplicity of political associations lauded by de Tocqueville was the result\n\nof the Founders’ decision to enshrine the “freedom to join together in furtherance of\n\ncommon political beliefs” in the First Amendment of the Constitution. Tashjian v.\n\nRepublican Party of Conn., 479 U.S. 208, 214-15 (1986). That Amendment promises\n\nAmericans the right not just to proclaim a political vision but to join with their\n\ncompatriots and actually advance that vision. Because, while an individual may be, in de\n\nTocqueville’s words, “feeble and consequently more incapable of preserving his\n\nfreedom,” de Tocqueville, supra, at 123, when individuals combine in association they\n\n“acquire facility in prosecuting great undertakings in common,” id. at 114. Some of the\n\n“great undertakings” accomplished by political associations protected by the First\n\nAmendment include the Abolitionist Movement, the Women’s Suffrage Movement, the\n\n 9\n\fLabor Movement, and the Civil Rights Movement—the fruits of which continue to shape\n\nour politics and society for the better to this day.\n\n Of all political associations protected by the First Amendment, political parties\n\nthemselves merit special attention. Like other political participants, parties advance a\n\nparticular vision. Unlike others, however, political parties must also nominate candidates\n\nfor office, compete in elections, and, if successful, help to translate campaign appeals into\n\nprogrammatic action. In so doing, political parties provide a vehicle for voters to advance\n\ntheir own political views. Without groups like modern political parties, “[r]epresentative\n\ndemocracy in any populous unit of governance” would be “unimaginable.” Cal.\n\nDemocratic Party v. Jones, 530 U.S. 567, 574 (2000).\n\n Perhaps no function of a party is more central to its purpose than the selection of\n\ncandidates for office, which “often determines the party’s positions on the most\n\nsignificant public policy issues of the day.” Id. at 575. It is no surprise, therefore, that the\n\nSupreme Court is “vigorous[]” in affirming the “special protection” owed to the\n\nassociational rights of political parties as they pertain to the parties’ choice of nominees.\n\nId. at 576. Statutes that severely burden a party’s associational rights must be narrowly\n\ntailored to advance a compelling government interest. Id. at 581-82. In Democratic Party\n\nof the United States v. Wisconsin ex rel. La Follette, the Court invalidated a Wisconsin\n\nlaw that required the national Democratic Party to seat certain delegates chosen in an\n\nopen primary. 450 U.S. 107 (1981). In Tashjian v. Republican Party of Connecticut, the\n\nCourt struck down a Connecticut law that forbade state parties from conducting open\n\nprimaries because the law burdened “associational opportunities at the crucial juncture at\n\n 10\n\fwhich the appeal to common principles may be translated into concerted action . . . .” 479\n\nU.S. at 216. In Eu v. San Francisco County Democratic Central Committee, the Court\n\ninvalidated laws dictating political parties’ internal affairs and prohibiting them from\n\nendorsing candidates for office. 489 U.S. 214 (1989). And in California Democratic\n\nParty v. Jones, the Court struck down a mandatory open primary law as it burdened the\n\n“political association’s right to exclude” in the “candidate-selection process.” 530 U.S. at\n\n575.\n\n Not every burden on associational rights is unconstitutional. “States have a major\n\nrole to play in structuring and monitoring the election process, including” nominee\n\nselection. Cal. Democratic Party, 530 U.S. at 572. Where the burden imposed by the\n\nstate is not “severe”—where it is “lesser”—courts engage in “less exacting review.”\n\nTimmons v. Twin Cities Area New Party, 520 U.S. 351, 358 (1997). In Timmons, the\n\nCourt upheld a Minnesota law that prohibited a candidate from appearing on the ballot as\n\nthe nominee of more than one party after finding that the law did “not severely burden\n\nthat party’s associational rights.” Id. at 359. Nothing prevented the party from endorsing\n\nthe candidate of another party; nothing prevented the party for campaigning for the\n\ncandidate of another party. The law’s only effect was to “reduce the universe of potential\n\ncandidates who may appear on the ballot as the party’s nominee . . . by ruling out those\n\nfew individuals who . . . have already agreed to be another party’s candidate.” Id. at 363.\n\nThis slight a reduction could not be a severe burden. Id.; see also Clingman v. Beaver,\n\n544 U.S. 581 (2005) (upholding law mandating a “semiclosed” primary, in which\n\nregistered members of opposing parties and unaffiliated voters could not participate).\n\n 11\n\f Political parties have, of course, come in for their fair share of criticism\n\nthroughout our history. Chancellor James Kent, in an 1830 letter to Daniel Webster,\n\nwrote that “Hamilton said in the Federalist, in his speeches, and a hundred times to me,\n\nthat factions would ruin us, and our government had not sufficient energy and balance to\n\nresist the propensity to them, and to control their tyranny and their profligacy.” John B.\n\nCassoday, James Kent & Joseph Story, 12 Yale L.J. 146, 151 (1903) (quoting letter). But\n\nwhether the divisiveness in public discourse traces to the presence of political parties or\n\nto the divisions inherent in the issues themselves elides the fact that parties have long\n\nsince become a fact of constitutional life. And what emerges from the above Supreme\n\nCourt cases is no all-or-nothing proposition but instead that law is not insensitive to\n\nmatters of degree: Those laws that impose a “heav[y]” or “severe” burden on a political\n\nparty’s right to choose its nominee are unconstitutional unless they serve a “compelling\n\nstate interest” and are “narrowly tailored” to do so. Cal. Democratic Party, 530 U.S. at\n\n583. It is to that inquiry that we now turn.\n\n B.\n\n The fourth sentence of Virginia Code § 24.2-509(B), the provision of the\n\nIncumbent Protection Act that applies to congressional incumbents among others,\n\nunquestionably poses a severe burden on the associational rights of the Commonwealth’s\n\npolitical parties. In evaluating the law’s imposition on associational rights, we must\n\n“weigh the ‘character and magnitude’ of the burden” it occasions. Timmons, 520 U.S. at\n\n358 (quoting Burdick, 504 U.S. at 434). We keep in mind also that “[a]ny interference\n\n\n\n 12\n\fwith the freedom of a party is simultaneously an interference with the freedom of its\n\nadherents.” Tashjian, 479 U.S. at 215 (quoting Democratic Party, 450 U.S. at 122).\n\n Subsection 24.2-509(A) grants the “duly constituted authorities” of the\n\nCommonwealth’s political parties considerable discretion in selecting the method of\n\nchoosing their nominees. The Incumbent Protection Act, subsection 24.1-509(B), carves\n\nexceptions to this rule in favor of incumbents. To recapitulate, the second and third\n\nsentences allow incumbent members of the General Assembly to dictate the method their\n\nparty shall use in selecting the nominee for the office that incumbent holds. The fourth\n\nsentence allows incumbent members of the U.S. House of Representatives, who were\n\nthemselves nominated by primary in the last election cycle, to require their party to use a\n\nprimary in the current election cycle to nominate a candidate for the office they hold if\n\nthey themselves are seeking reelection. In short, the associational rights of Virginia’s\n\npolitical parties that are recognized and protected by § 24.2-509(A) are taken away by §\n\n24.1-509(B) and given instead to a single individual—the incumbent.\n\n The weight of this burden could not be more obvious. The members of the 6th\n\nCongressional District Committee have, as generations of Americans did before them,\n\nbanded together to advance their political views. The selection of a nominee “often\n\ndetermines” the contours of the party platform. Cal. Democratic Party, 530 U.S. at 575.\n\nAnd “even when those positions are predetermined it is the nominee who becomes the\n\nparty’s ambassador to the general electorate in winning it over to the party’s views.” Id.\n\nYet, at the “crucial juncture” at which the members of this political association decide\n\nhow to select their nominee, id., the Commonwealth has taken the decision out of their\n\n 13\n\fhands: No matter what method of nomination the members of this party may prefer,\n\nVirginia law decrees that they must give way to the desire of the incumbent to hold a\n\nprimary if that incumbent was himself selected by primary previously and is seeking\n\nreelection.\n\n The burden is manifestly severe. This is not a case like Timmons, in which a\n\nparty’s ability to choose a nominee was reduced by only the small number of individuals\n\nthat already appeared elsewhere on the ballot. 520 U.S. at 351. Nor is this a case like\n\nClingman, in which the state’s Libertarian Party was required by state law to allow only\n\nits registered members and registered independent voters to participate in its primary. 544\n\nU.S. at 592. The burden there was not severe given the ease with which registered\n\nmembers of other parties who wanted to participate in the Libertarian primary could\n\nchange their registration. Id. Rather, this is a case in which the state has decided that the\n\nwishes of a party’s adherents must, in certain circumstances, be subordinated wholesale\n\nto the wishes of a single individual whose self-interest is self-evident; in these\n\ncircumstances, the party’s adherents are entirely shut out of the choice of nomination\n\nmethod—severely burdening their associational rights.\n\n C.\n\n Because the provision of the Incumbent Protection Act which protects\n\ncongressional incumbents—the fourth sentence—imposes a “severe” burden on the\n\nassociational rights of Virginia’s political parties, the Commonwealth must show that it is\n\n“narrowly tailored to serve a compelling state interest.” Cal. Democratic Party, 530 U.S.\n\nat 583. It cannot make this showing.\n\n 14\n\f Primaries add a crucial participatory dimension to democratic politics. Appellants\n\nassert that § 24.2-509(B) is akin to a mandatory primary statute, and therefore it serves\n\nthe interest of “assur[ing] that intraparty competition is resolved in a democratic fashion.”\n\nId. at 572. If § 24.2-509(B) truly were a mandatory primary statute its constitutionality\n\nwould be “too plain for argument.” Id. (quoting Am. Party of Tex. v. White, 415 U.S. 767,\n\n781 (1974)). But it is not: The statute does not by itself require any organ of a Virginia\n\npolitical party to use a primary as a method of nomination. Instead, the statute delegates\n\nthe power to force the party to use a primary to the incumbent office holder. Therein lies\n\nthe constitutional flaw.\n\n This delegation of power over the party to the incumbent office holder is not\n\nnarrowly tailored to meet the Commonwealth’s asserted interest. Under the terms of the\n\nstatute, the interest in democratic resolution of intraparty disputes will only be vindicated\n\nwhen and where an incumbent office holder decides that it is in his interest to do so. It is\n\nimplausible that the General Assembly would seek to vindicate this interest in such an\n\nodd, uneven, and underinclusive fashion. Instead, the text and structure of the law gives\n\nrise to the strong suggestion that the Incumbent Protection Act serves a different interest:\n\nthe interest, unsurprisingly, in incumbent protection.\n\n To be sure, incumbent protection is not per se an unconstitutional interest. In the\n\ncontext of redistricting, the Supreme Court has historically allowed maps to stand that\n\nwere drawn with the electoral interest of incumbents in mind. See, e.g., Karcher v.\n\nDaggett, 462 U.S. 725, 740 (1983). But the Court has not held that the interest in\n\nincumbent protection is a compelling one that can justify such direct intrusions on the\n\n 15\n\fFirst Amendment. See Gill v. Whitford, 138 S. Ct. 1916, 1934 (2018) (Kagan, J.,\n\nconcurring) (explaining that the Court did not address the First Amendment challenge to\n\nthe redistricting). Incumbent protection is simply not a strong enough interest here to\n\njustify the severe burden on the appellee’s associational rights.\n\n Incumbents, after all, are already blessed with myriad de facto advantages in the\n\nelectoral arena. Appellee’s expert, Professor Jeffrey A. Jenkins, testified that incumbents\n\ngenerally have better name recognition than challengers because of their time in the\n\npublic eye. J.A. 884. Incumbents also have the opportunity to win votes by enacting\n\npopular laws and servicing their constituents, and they have easier access to donors, as\n\nthey are proven winners. Id. All this contributes to the “scare-off” effect: potential\n\nchallengers, faced with the seemingly insurmountable hurdles, will decide not to run. Id.\n\n The other reason for incumbency advantage is more salutary. Voters may\n\nrecognize that incumbents provide our government with institutional memory and the\n\nwisdom that can only be won through experience. In the legislative branch, which could\n\nfind itself at a disadvantage when dealing with career officials and agency specialists of\n\nthe executive, the cumulative knowledge and experience brought by incumbents to the\n\nnegotiating table is particularly valuable. In this sense, incumbency evens the interbranch\n\nplaying field. Without it, novice legislators would find it more difficult to fulfill their\n\nconstitutional responsibilities.\n\n Thus, domination of the political parties by their incumbent office holders is,\n\nperhaps, a natural consequence of political reality. But to the already winning de facto\n\nhand dealt incumbents, § 24.2-509(B) adds a de jure ace: In the circumstances governed\n\n 16\n\fby the fourth sentence, challengers would have to compete with already advantaged\n\nincumbents in a selection process chosen by the incumbent himself. This goes too far. It\n\nnarrows the possibility of legislative renewal and refreshment through the infusion of\n\nnew blood. It risks making the electoral process sclerotic.\n\n Nothing in the foregoing analysis compromises the “major role” played by states\n\nin structuring their elections. Cal. Democratic Party, 530 U.S. at 572. Election\n\nadministration is necessarily an amalgam of state law and party procedures, and the\n\nCommonwealth is surely correct that the rights of political parties in this amalgam are not\n\nabsolute in character. We reiterate that “it is beyond question ‘that States may, and\n\ninevitably must, enact reasonable regulations of parties, elections, and ballots to reduce\n\nelection- and campaign-related disorder.’” Clingman, 544 U.S. at 593 (quoting Timmons,\n\n520 U.S. at 358). Rather, we simply hold that a state may not force a political party to\n\nhand control over its nomination method to a single, self-interested individual; the private\n\ninterest of an incumbent in winning reelection cannot, and certainly not in the manner\n\nchosen here, predominate over the associational rights of political parties.\n\n III.\n\n The district court also enjoined enforcement of the Act’s second and third\n\nsentences, which protect the nomination prerogatives of incumbent members of the\n\nGeneral Assembly. The Commonwealth argues that this was improper, as the Committee\n\nlacked standing to challenge those provisions. We disagree. The Committee suffered\n\ncognizable, traceable, and redressable injury from the Commonwealth’s application of\n\nthose sentences to its activities. And the second and third sentences are, if anything, even\n\n 17\n\fmore offensive to the First Amendment than the fourth. Accordingly, we affirm the\n\ndistrict court’s decision to enjoin the second and third sentences on § 24.2-509(B) as\n\nwell.\n\n Standing requires an injury in fact that is caused by the challenged conduct and is\n\nlikely to be redressed by a favorable decision. See Ohio Valley Envtl. Coal., Inc. v. Pruitt,\n\n893 F.3d 225, 229 (4th Cir. 2018). “To establish injury in fact, a plaintiff must show that\n\nhe or she suffered an invasion of a legally protected interest that is concrete and\n\nparticularized and actual or imminent, not conjectural or hypothetical.” Spokeo, Inc. v.\n\nRobins, 136 S. Ct. 1540, 1548 (2016) (internal quotation marks omitted). Throughout a\n\nlawsuit “the standing inquiry remains focused on whether the party invoking jurisdiction\n\nhad the requisite stake in the outcome when the suit was filed.” Davis v. Fed. Election\n\nComm’n, 554 U.S. 724, 734 (2008).\n\n The Committee suffered an injury in fact at the time the lawsuit was filed as a\n\nresult of the Commonwealth’s application of the second and third sentences, as\n\ndemonstrated by the “specific facts” adduced in its submissions to this court. Lujan v.\n\nDefenders of Wildlife, 504 U.S. 555, 561 (1992). These facts are as follows: The\n\nDepartment issues a series of forms for incumbents and party committees to notify the\n\nCommonwealth which nomination method they plan to use, as they are required to do by\n\nlaw. See Va. Code Ann. § 24.2-516. These forms reflect the Department’s understanding\n\nof how to apply the Incumbent Protection Act. And yet, throughout the 2016 election\n\ncycle and through the filing of this lawsuit, these forms applied the Act’s second and\n\nthird sentences, which should only apply to incumbent members of the General\n\n 18\n\fAssembly, to the 6th Congressional Committee as well. Incumbent members of Congress\n\nwere given the same plenary power to designate any method of nomination no matter the\n\ncircumstance, as if they were incumbent members of the General Assembly.\n\n The forms themselves best tell the story:\n\n DESIGNATION OF METHOD OF NOMINATION\n for\n SENATE OF VIRGINIA\n 2015\n ***\n I, the undersigned incumbent of the Senate of Virginia district indicated\n above, am seeking re-election and designate the following method of\n nomination to be used in determining the party’s candidate for this office\n subject to the forthcoming November general election.\n\nJ.A. 892.\n\n 2016 DESIGNATION OF METHOD OF NOMINATION\n ***\n I, the undersigned incumbent of the district indicated above, am seeking\n re-election and designate the following method of nomination to be used in\n determining the party’s candidate for this office subject to the coming\n November general election.\n\nJ.A. 873. The form used by incumbent General Assembly members in the 2015 election\n\ncycle and by incumbent Members of Congress in the 2016 election cycle are in all\n\nmaterial respects the same. As the Committee noted, “[n]ot only did Appellants\n\npromulgate these forms, they directed non-General Assembly incumbents and party\n\nchairmen to use them.” Resp. Br. of Appellee at 13.\n\n It is plain therefore that, on those facts, the Committee suffered a sufficiently\n\n“concrete” injury in fact to sustain its challenge to the second and third sentences of the\n\nAct. Because of the forms, any candidate that the 6th Congressional Committee wished to\n\n\n 19\n\frecruit, or anyone contemplating an electoral challenge to the incumbent, faced the\n\nprospect of having to compete in a nomination process selected by that incumbent.\n\nPlainly, this prospect would “dramatically change[] the plaintiffs’ decisions about\n\ncampaign financing, messages to stress, and candidates to recruit.” Miller I, 462 F.3d at\n\n317. This distortion of political decisionmaking constitutes an ongoing and concrete\n\ninjury sufficient to meet the injury-in-fact prong of constitutional standing analysis. Id. at\n\n317-18.\n\n That injury, of course, is particularized because the 6th Congressional Committee\n\nserves a unique function in selecting the Republican nominee for Virginia’s 6th\n\nCongressional District. See Lujan, 504 U.S. at 560. The remaining standing analysis is\n\nstraightforward: The injury was caused by promulgation of the forms based on the Act’s\n\nsecond and third sentences, and therefore will be redressed if we find those sentences to\n\nbe inconsistent with the First Amendment. For these reasons, the Committee has standing\n\nto challenge the portions of § 24.2-509(B) that protect the nomination prerogatives of\n\nGeneral Assembly members.\n\n In response, the Department argues that the challenge to the second and third\n\nsentences became moot when the Department updated the offending election forms. 2 But\n\n\n2\n The Department also argues that plaintiff’s challenge to the Act’s fourth sentence is\nmoot. It notes that because the current 6th District incumbent was selected by convention,\nthe plaintiff will not be forced to accede to a primary until 2022 at the earliest. But that\nargument relies on the same cramped interpretation of standing that we rejected in Miller\nI, 462 F.3d at 316-18. The injuries inflicted by laws that distort the primary process, like\nthe Incumbent Protection Act, are not confined to the short duration of any particular\nprimary, but instead reflect the reality that “campaign planning decisions have to be made\n(Continued)\n 20\n\fthe update occurred after the lawsuit had been filed. Promulgating new forms may well\n\nhave been the right thing to do in accordance with state law. But as a litigation tactic,\n\nsuch backpedaling will rarely serve to moot a case in federal court. Friends of the Earth,\n\nInc. v. Laidlaw Environmental Services (TOC), Inc., 528 U.S. 167, 189-94 (2000). The\n\nmootness doctrine ordinarily does not extend to situations where a party quits its\n\noffending conduct partway through litigation. Id. After all, “a party should not be able to\n\nevade judicial review, or to defeat a judgment, by temporarily altering questionable\n\nbehavior.” Porter v. Clarke, 852 F.3d 358, 364 (4th Cir. 2017) (internal quotation marks\n\nomitted). To overcome that general rule, the Department bears “[t]he heavy burden of\n\npersuading the court,” Laidlaw, 528 U.S. 167, 189 (2000) (internal quotation marks and\n\nalterations omitted), that it is “absolutely clear that the allegedly wrongful behavior could\n\nnot reasonably be expected to recur.” Wall v. Wade, 741 F.3d 492, 497 (2014) (quoting\n\nLaidlaw, 528 U.S. at 189).\n\n The Department cannot carry this burden. It has a history of frequently revising\n\nthe relevant election forms. The forms used for congressional nominations in 2014, for\n\nexample, reflected the fourth sentence of the Incumbent Protection Act and not the\n\nsecond and third. Yet the congressional nomination forms were inexplicably changed for\n\n\nmonths, or even years, in advance of the election to be effective.” Id. at 317-18. The 6th\nCongressional Committee’s claims thus did not become moot with the passing of the\n2018 election season. The dispute over the Act’s fourth sentence, rather, is alive and well.\nEven so, if the Department were correct that electoral disputes became moot with each\npassing election cycle, this challenge, like many electoral challenges, would plainly be\ncapable of repetition yet evading review. See, e.g., Davis v. Fed. Election Comm’n, 554\nU.S. 724, 735-36 (2008).\n\n 21\n\fthe 2016 congressional elections to reflect the Act’s more fulsome General Assembly\n\nprotections instead. The Department has offered no explanation for why the forms were\n\nchanged to the benefit of incumbents between the 2014 and 2016 congressional elections.\n\nEven though the forms apparently have been edited once again, we have little confidence\n\nthat the forms will not revert back if we hold that this lawsuit is moot. Indeed, that danger\n\nis particularly acute when, as here, a change in the forms would confer benefits upon\n\npolitical incumbents. The Incumbent Protection Act transparently advances the interests\n\nof those who control the apparatus of government; it is hardly beyond the realm of\n\nplausibility that it would be administered with that same purpose in mind. The\n\nDepartment’s May 23, 2018 Suggestion of Mootness is accordingly denied.\n\n We may thus properly consider the 6th Congressional Committee’s facial and as\n\napplied First Amendment challenges to the Incumbent Protection Act’s protection of\n\nincumbent members of the General Assembly. A facial challenge to a law will succeed\n\nafter a showing “that no set of circumstances exist under which the law would be valid,\n\nor that the law lacks any plainly legitimate sweep.” Greater Balt. Center for Pregnancy\n\nConcerns, Inc. v. Mayor & City Council of Balt., 721 F.3d 264, 282 (4th Cir. 2013) (en\n\nbanc) (internal quotation marks and alterations omitted). In the First Amendment context,\n\na facial challenge may also succeed under overbreadth doctrine. Id. But there is no need\n\nto employ overbreadth doctrine in this case, for the Act’s second and third sentences\n\ncannot be applied in a manner consistent with the First Amendment.\n\n The Department fails to identify a single circumstance where the Act’s second and\n\nthird sentences could be lawfully applied. And we find none. The second and third\n\n 22\n\fsentences not only share the constitutional infirmities of the fourth sentence but exhibit\n\nthose infirmities to an even greater degree. The fourth sentence allows some incumbents\n\nto force a primary under certain designated circumstances. The second sentence goes\n\nfurther by empowering incumbents to impose their choice of any method of nomination\n\nno matter what the party prefers under almost any circumstances. 3 These advantages,\n\nwhen given to state or federal incumbents, run afoul of the First Amendment for all the\n\nreasons discussed in detail in Part II, supra.\n\n The Department raises yet one more challenge, arguing that the district court was\n\nwrong to enjoin the Incumbent Protection Act in its entirety. See Va. Code Ann. § 24.2-\n\n509(B). We review the district court’s decision to enjoin the statute for abuse of\n\ndiscretion. U.S. Airline Pilots Ass’n v. Awappa, LLC, 615 F.3d 312, 320 (4th Cir. 2010).\n\nThe Act comprises six sentences. We have now found that each of its operative\n\nprovisions—namely the second, third, and fourth sentences—is unconstitutional. The\n\nremaining sentences merely explain how to apply them. The district court did not abuse\n\nits discretion in enjoining the Incumbent Protection Act in toto.\n\n IV.\n\n Our decision is a narrow one. It is directed at a discrete constitutional imbalance\n\ncreated by permitting single office holders to negate the associational rights of political\n\nparties in an area central to the party’s very reason for being. Our ruling in no way limits\n\n 3\n The third sentence applies in the relatively rare situation where there is more than\none incumbent for the same office. In that situation, the statute requires incumbents’\nconsent for any method of nomination other than a primary. § 24.2-509(B).\n\n\n 23\n\fthe ability of states to enact “reasonable regulations of parties, elections, and ballots.”\n\nTimmons, 520 U.S. at 358. The associational rights of political parties are, after all, not\n\nabsolute. Laws that impose a slight or lesser burden on associational rights are owed\n\ndeference, especially when justified by the need “to reduce election- and campaign-\n\nrelated disorder.” Id. But our constitutional responsibility, set forth so plainly by the\n\nSupreme Court, requires us to ensure that this “deference does not risk such constitutional\n\nevils as, say, permitting incumbents to insulate themselves from effective electoral\n\nchallenge.” Nixon v. Shrink Mo. Gov’t PAC, 528 U.S. 377, 402 (2000) (Breyer, J.,\n\nconcurring). The Incumbent Protection Act reflects precisely that infirmity, and it is\n\nprecisely why we cannot allow the Act to stand.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 24", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4357290/", "author_raw": "WILKINSON, Circuit Judge:"}]}
WILKINSON
MOTZ
DUNCAN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4580037/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: 6TH CONGRESSIONAL DISTRICT REPUBLICAN COMMITTEE, Plaintiff - Appellee, and Anne Taetzsch Fitzgerald, Individually and as Chairman of the 20th House of Delegates District Republican Committee; Karen U. Kwiatkowski, Individually; Edward A. Yensho, Individually and as Chairman of the Green County Republican Committee; 20th House of Delegates District Republican Committee, Plaintiffs, v. James B. ALCORN, in His Official Capacity as Chairman of the Virginia State Board of Elections ; Clara Belle Wheeler, in Her Official Capacity as Vice-Chairman of the Virginia State Board of Elections ; Singleton B. McAllister, in Her Official Capacity as Secretary of the Virginia State Board of Elections ; Virginia Department of Elections, Defendants - Appellants.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-09\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1111\n\n\n6TH CONGRESSIONAL DISTRICT REPUBLICAN COMMITTEE,\n\n Plaintiff – Appellee,\n\n and\n\nANNE TAETZSCH FITZGERALD, individually and as Chairman of the 20th\nHouse of Delegates District Republican Committee; KAREN U.\nKWIATKOWSKI, individually; EDWARD A. YENSHO, individually and as\nChairman of the Green County Republican Committee; 20TH HOUSE OF\nDELEGATES DISTRICT REPUBLICAN COMMITTEE,\n\n Plaintiffs,\n\n v.\n\nJAMES B. ALCORN, in his official capacity as Chairman of the Virginia State\nBoard of Elections; CLARA BELLE WHEELER, in her official capacity as Vice-\nChairman of the Virginia State Board of Elections; SINGLETON B.\nMCALLISTER, in her official capacity as Secretary of the Virginia State Board of\nElections; VIRGINIA DEPARTMENT OF ELECTIONS,\n\n Defendants - Appellants.\n\n\nAppeal from the United States District Court for the Western District of Virginia, at\nHarrisonburg. Michael F. Urbanski, Chief District Judge. (5:17-cv-00016-MFU-JCH)\n\n\nArgued: December 12, 2018 Decided: January 9, 2019\n\n\nBefore WILKINSON, MOTZ, and DUNCAN, Circuit Judges.\n\fAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge Motz\nand Judge Duncan joined.\n\n\nARGUED: Toby Jay Heytens, OFFICE OF THE ATTORNEY GENERAL OF\nVIRGINIA, Richmond, Virginia, for Appellants. Jeffrey R. Adams, WHARTON,\nALDHIZER & WEAVER, PLC, Harrisonburg, Virginia, for Appellee. ON BRIEF:\nMark R. Herring, Attorney General, Stephen A. Cobb, Deputy Attorney General,\nMatthew R. McGuire, Principal Deputy Solicitor General, Michelle S. Kallen, Deputy\nSolicitor General, OFFICE OF THE ATTORNEY GENERAL OF VIRGINIA,\nRichmond, Virginia, for Appellants. Charles F. Hilton, Thomas E. Ullrich, Lucas I.\nPangle, WHARTON ALDHIZER & WEAVER, PLC, Harrisonburg, Virginia; John C.\nWirth, NELSON MCPHERSON SUMMERS & SANTOS, Staunton, Virginia, for\nAppellee.\n\n\n\n\n 2\n\fWILKINSON, Circuit Judge:\n\n The 6th Congressional District Republican Committee argues that Virginia’s\n\nIncumbent Protection Act, Va. Code Ann. § 24.2-509(B), violates the First Amendment\n\nof the Constitution. The district court agreed and enjoined § 24.2-509(B) in its entirety.\n\nFor the reasons that follow, we now affirm.\n\n I.\n\n A.\n\n Virginia law generally allows the Commonwealth’s political parties considerable\n\ndiscretion in deciding how to nominate their candidates for office. Section 24.2-509(A)\n\nempowers the “duly constituted authorities” of the state and local parties “to determine\n\nthe method by which a party nomination . . . shall be made.” The parties make use of this\n\nlatitude. For example, the Republican Party of Virginia, with whom the appellee here is\n\naffiliated, allows for four different methods of nomination: a primary, a party canvass, a\n\nconvention, and a mass meeting. Fitzgerald v. Alcorn, 285 F. Supp. 3d 922, 927 (W.D.\n\nVa. 2018). Under the Party’s Plan of Organization, committees established in every\n\nlocality, state legislative district, and congressional district are empowered to choose\n\namong these methods to nominate candidates for their political subdivision. J.A. 37, 38,\n\n40.\n\n The differences between these methods are substantial. Each one “‘create[s] a\n\ndifferent distribution of potential voters (or decision makers) in the nomination process.’\n\nFor example, primaries involve the largest pool of potential voters, whereas conventions\n\nand mass meetings ‘lend themselves more toward committed partisans.’” Alcorn, 285 F.\n\n 3\n\fSupp. 3d at 935 (quoting J.A. 884-85, 885-86). The choice of method, therefore, could\n\nhave a significant influence on the choice of nominee.\n\n Subsection 24.2-509(B), often called the Incumbent Protection Act, however,\n\nlimits the broad authority recognized by subsection A. 1 The second and third sentences\n\napply to those subdivisions of the state party that select nominees for candidates to the\n\n\n1\n The full text of Virginia Code § 24.2-509 is reprinted below, with the sentences in\nsubsection B numbered for ease of reference:\n\nA. The duly constituted authorities of the state political party shall have the right to\n determine the method by which a party nomination for a member of the United States\n Senate or for any statewide office shall be made. The duly constituted authorities of\n the political party for the district, county, city, or town in which any other office is to\n be filled shall have the right to determine the method by which a party nomination for\n that office shall be made.\n\nB. [1] Notwithstanding subsection A, the following provisions shall apply to the\n determination of the method of making party nominations. [2] A party shall nominate\n its candidate for election for a General Assembly district where there is only one\n incumbent of that party for the district by the method designated by that incumbent, or\n absent any designation by him by the method of nomination determined by the party.\n [3] A party shall nominate its candidates for election for a General Assembly district\n where there is more than one incumbent of that party for the district by a primary\n unless all the incumbents consent to a different method of nomination. [4] A party,\n whose candidate at the immediately preceding election for a particular office other\n than the General Assembly (i) was nominated by a primary or filed for a primary but\n was not opposed and (ii) was elected at the general election, shall nominate a\n candidate for the next election for that office by a primary unless all incumbents of\n that party for that office consent to a different method.\n\n [5] When, under any of the foregoing provisions, no incumbents offer as candidates\n for reelection to the same office, the method of nomination shall be determined by the\n political party.\n\n [6] For the purposes of this subsection, any officeholder who offers for reelection to\n the same office shall be deemed an incumbent notwithstanding that the district which\n he represents differs in part from that for which he offers for election.\n\n\n 4\n\fGeneral Assembly. Those sentences allow incumbent members of the General Assembly\n\nwho are running for reelection, where there is only one incumbent, to “designate[]” the\n\nmethod of nomination they prefer. Under this statute, the wishes of the party are\n\nimmaterial; no matter where the party’s plan of organization may vest the power to\n\nchoose nomination methods, the law trumps, granting the power to the incumbent.\n\n The fourth sentence of the Act applies to those components of political parties that\n\nmake the nominations for “particular office[s]” other than for the General Assembly,\n\nincluding nominations for the U.S. House of Representatives. In these races, the\n\nincumbent officeholder may insist that his or her party use a primary as its nomination\n\nmethod as long as (1) the incumbent was selected by primary in the previous election\n\ncycle and (2) the incumbent is running for reelection. Again, the statute trumps the\n\nparty’s plan of organization, which, in this case allows the committees responsible for\n\ncongressional nominations to choose between the approved methods (excluding mass\n\nmeetings) without interference by the incumbent, J.A. 37.\n\n The Virginia Department of Elections, however, has not always respected the\n\ndistinction made between the second and third sentences on the one hand, and the fourth\n\nsentence on the other. In the 2016 and 2017 election cycles, for example, the Department\n\npromulgated forms that allowed non-General Assembly incumbents to “designate” their\n\npreferred method of nomination as if their elections were governed by the second and\n\nthird sentences. After the commencement of this litigation, and only after the appellees\n\npointed out the mistake, the Department issued new forms that applied the fourth\n\nsentences to these races.\n\n 5\n\f Virginia has not identified a single other state that has a statute like the Incumbent\n\nProtection Act, and this is not the first case to consider a constitutional challenge to it. In\n\n2007, for example, this court considered a challenge to the Act. Miller v. Brown, 503\n\nF.3d 360 (4th Cir. 2007) (“Miller II”). There, we held that an incumbent cannot\n\nconstitutionally force his or her party to use an open primary, as this would be an\n\nimpermissible burden on the party’s associational rights. Id. at 368-71. We did not,\n\nhowever, reach the different question of the constitutionality of incumbents’ statutory\n\npower to dictate any nomination method.\n\n B.\n\n This appeal stems from the 6th Congressional District Republican Committee’s\n\nchallenge to the Incumbent Protection Act under 42 U.S.C. § 1983. See Alcorn, 285 F.\n\nSupp. 3d at 922. The Committee is responsible for nominating candidates for the U.S.\n\nHouse of Representatives for the 6th Congressional District, which “covers much of the\n\nwest-central portion of Virginia, from Roanoke to Front Royal.” Id. at 927. Under the\n\nParty’s Plan of Organization, it is composed of the “District Chairman,” the “Unit\n\nChairman” (the chair of each relevant locality’s committee), the “District Representative\n\nof the Virginia Federation of Republican Women,” the “Young Republican Federation\n\nDistrict Committeeman,” the “College Republican Federation District Committeeman,”\n\nand the “District members of the State Central Committee.” J.A. 36-37. The Committee,\n\nalong with other plaintiffs who were dismissed from the suit and do not appeal, raised\n\nfacial and as applied challenges to the Incumbent Protection Act, claiming that it\n\nabridged their rights under the First and Fourteenth Amendments of the U.S.\n\n 6\n\fConstitution. The named defendants include the Virginia Department of Elections and the\n\nthree members of the Virginia State Board of Elections at the time the suit was filed.\n\nAlcorn, 285 F. Supp. 3d at 928.\n\n The district court, relying on Miller v. Brown, 462 F.3d 312 (4th Cir. 2006)\n\n(“Miller I”), found that the Committee had standing to challenge the Act. Alcorn, 285 F.\n\nSupp. 3d at 937. It then proceeded to evaluate the burden posed by § 24.2-509(B) on the\n\nCommittee’s associational rights, concluding that it was “severe” because it provided\n\n“incumbents with a statutory right to dictate political parties’ internal affairs . . . .” Id. at\n\n952. The burden was “especially” onerous because it trespassed on the “realm of\n\nselecting candidates.” Id. Given the magnitude of the burden, the district court found that\n\n“the Act can survive constitutional scrutiny only if it is ‘narrowly tailored to advance a\n\ncompelling state interest.’” Id. (quoting Burdick v. Takushi, 504 U.S. 428, 433 (1992)).\n\nThe district court ultimately concluded that the Act did not survive such scrutiny. Id. at\n\n953.\n\n The district court thus permanently enjoined enforcement of the entire Incumbent\n\nProtection Act on January 19, 2018. J.A. 1473. The court enjoined all six sentences of\n\n§ 24.2-509(B) because, according to the court, the second and third sentences—which\n\nprotect the nomination prerogatives of incumbent General Assembly members—could\n\nnot be severed from the fourth—which protects the nomination prerogatives of, inter alia,\n\nmembers of Congress. The court additionally found that the Committee had standing to\n\nchallenge the second and third sentences under the overbreadth doctrine. Alcorn, 285 F.\n\nSupp. 3d at 955. Finally, the district court concluded that the Act had “no legitimate\n\n 7\n\fsweep” and so a facial challenge to all its provisions was appropriate. Id. at 955-56. After\n\nthe notice of appeal had been filed, the district court stayed its permanent injunction order\n\non February 5, 2018, to avoid interfering with the ongoing nomination cycle. J.A. 1481.\n\nAfter that cycle concluded, however, the district court vacated its stay on September 24,\n\n2018. J.A. 1680. During the course of this appeal, the Department filed a motion to\n\nvacate the injunction on the basis of mootness. We held that motion in abeyance pending\n\noral argument, and both parties expanded on their arguments in their briefing on the\n\nmerits.\n\n II.\n\n The district court found that the fourth sentence of the Incumbent Protection Act,\n\nwhich protects the nomination prerogatives of incumbent members of Congress among\n\nothers, violated the First Amendment. Because this provision imposes a severe burden on\n\nthe associational rights of Virginia’s political parties, and because the Commonwealth\n\nhas been unable to show that it is narrowly tailored to serve a compelling state interest,\n\nwe agree.\n\n A.\n\n Freedom of association has, for centuries, been at the heart of the American\n\nsystem of government and individual rights. In 1831, when Alexis de Tocqueville arrived\n\nin the United States, he was shocked to discover that our nation was the only “country on\n\nthe face of the earth where the citizens enjoy unlimited freedom of association for\n\npolitical purposes.” Alexis de Tocqueville, 2 Democracy in America 123 (Henry Reeves\n\ntrans., 1863). In America, “the most democratic country on the face of the earth,” the\n\n 8\n\f“art” of forming political associations had been “carried to the highest perfection.” Id. at\n\n115. Because of this, “Americans of all ages, all conditions, and all dispositions,\n\nconstantly form associations.” Id. at 114.\n\n De Tocqueville identified this propensity to associate as one of the sources of the\n\nastonishing political dynamism of the young Republic, writing that American political\n\nassociations are “the mother of action,” id. at 125, and that they “stimulate competition,\n\nand . . . discover those arguments which are most fitted to act upon the majority.” Id. at\n\n210. The right to associate for political purposes, de Tocqueville proclaimed, is “[t]he\n\nmost natural privilege of man, next to the right of acting for himself.” Id. at 209.\n\nAccordingly, “the right of association is almost as inalienable as the right of personal\n\nliberty. No legislator can attack it without impairing the very foundations of society.” Id.\n\n The multiplicity of political associations lauded by de Tocqueville was the result\n\nof the Founders’ decision to enshrine the “freedom to join together in furtherance of\n\ncommon political beliefs” in the First Amendment of the Constitution. Tashjian v.\n\nRepublican Party of Conn., 479 U.S. 208, 214-15 (1986). That Amendment promises\n\nAmericans the right not just to proclaim a political vision but to join with their\n\ncompatriots and actually advance that vision. Because, while an individual may be, in de\n\nTocqueville’s words, “feeble and consequently more incapable of preserving his\n\nfreedom,” de Tocqueville, supra, at 123, when individuals combine in association they\n\n“acquire facility in prosecuting great undertakings in common,” id. at 114. Some of the\n\n“great undertakings” accomplished by political associations protected by the First\n\nAmendment include the Abolitionist Movement, the Women’s Suffrage Movement, the\n\n 9\n\fLabor Movement, and the Civil Rights Movement—the fruits of which continue to shape\n\nour politics and society for the better to this day.\n\n Of all political associations protected by the First Amendment, political parties\n\nthemselves merit special attention. Like other political participants, parties advance a\n\nparticular vision. Unlike others, however, political parties must also nominate candidates\n\nfor office, compete in elections, and, if successful, help to translate campaign appeals into\n\nprogrammatic action. In so doing, political parties provide a vehicle for voters to advance\n\ntheir own political views. Without groups like modern political parties, “[r]epresentative\n\ndemocracy in any populous unit of governance” would be “unimaginable.” Cal.\n\nDemocratic Party v. Jones, 530 U.S. 567, 574 (2000).\n\n Perhaps no function of a party is more central to its purpose than the selection of\n\ncandidates for office, which “often determines the party’s positions on the most\n\nsignificant public policy issues of the day.” Id. at 575. It is no surprise, therefore, that the\n\nSupreme Court is “vigorous[]” in affirming the “special protection” owed to the\n\nassociational rights of political parties as they pertain to the parties’ choice of nominees.\n\nId. at 576. Statutes that severely burden a party’s associational rights must be narrowly\n\ntailored to advance a compelling government interest. Id. at 581-82. In Democratic Party\n\nof the United States v. Wisconsin ex rel. La Follette, the Court invalidated a Wisconsin\n\nlaw that required the national Democratic Party to seat certain delegates chosen in an\n\nopen primary. 450 U.S. 107 (1981). In Tashjian v. Republican Party of Connecticut, the\n\nCourt struck down a Connecticut law that forbade state parties from conducting open\n\nprimaries because the law burdened “associational opportunities at the crucial juncture at\n\n 10\n\fwhich the appeal to common principles may be translated into concerted action . . . .” 479\n\nU.S. at 216. In Eu v. San Francisco County Democratic Central Committee, the Court\n\ninvalidated laws dictating political parties’ internal affairs and prohibiting them from\n\nendorsing candidates for office. 489 U.S. 214 (1989). And in California Democratic\n\nParty v. Jones, the Court struck down a mandatory open primary law as it burdened the\n\n“political association’s right to exclude” in the “candidate-selection process.” 530 U.S. at\n\n575.\n\n Not every burden on associational rights is unconstitutional. “States have a major\n\nrole to play in structuring and monitoring the election process, including” nominee\n\nselection. Cal. Democratic Party, 530 U.S. at 572. Where the burden imposed by the\n\nstate is not “severe”—where it is “lesser”—courts engage in “less exacting review.”\n\nTimmons v. Twin Cities Area New Party, 520 U.S. 351, 358 (1997). In Timmons, the\n\nCourt upheld a Minnesota law that prohibited a candidate from appearing on the ballot as\n\nthe nominee of more than one party after finding that the law did “not severely burden\n\nthat party’s associational rights.” Id. at 359. Nothing prevented the party from endorsing\n\nthe candidate of another party; nothing prevented the party for campaigning for the\n\ncandidate of another party. The law’s only effect was to “reduce the universe of potential\n\ncandidates who may appear on the ballot as the party’s nominee . . . by ruling out those\n\nfew individuals who . . . have already agreed to be another party’s candidate.” Id. at 363.\n\nThis slight a reduction could not be a severe burden. Id.; see also Clingman v. Beaver,\n\n544 U.S. 581 (2005) (upholding law mandating a “semiclosed” primary, in which\n\nregistered members of opposing parties and unaffiliated voters could not participate).\n\n 11\n\f Political parties have, of course, come in for their fair share of criticism\n\nthroughout our history. Chancellor James Kent, in an 1830 letter to Daniel Webster,\n\nwrote that “Hamilton said in the Federalist, in his speeches, and a hundred times to me,\n\nthat factions would ruin us, and our government had not sufficient energy and balance to\n\nresist the propensity to them, and to control their tyranny and their profligacy.” John B.\n\nCassoday, James Kent & Joseph Story, 12 Yale L.J. 146, 151 (1903) (quoting letter). But\n\nwhether the divisiveness in public discourse traces to the presence of political parties or\n\nto the divisions inherent in the issues themselves elides the fact that parties have long\n\nsince become a fact of constitutional life. And what emerges from the above Supreme\n\nCourt cases is no all-or-nothing proposition but instead that law is not insensitive to\n\nmatters of degree: Those laws that impose a “heav[y]” or “severe” burden on a political\n\nparty’s right to choose its nominee are unconstitutional unless they serve a “compelling\n\nstate interest” and are “narrowly tailored” to do so. Cal. Democratic Party, 530 U.S. at\n\n583. It is to that inquiry that we now turn.\n\n B.\n\n The fourth sentence of Virginia Code § 24.2-509(B), the provision of the\n\nIncumbent Protection Act that applies to congressional incumbents among others,\n\nunquestionably poses a severe burden on the associational rights of the Commonwealth’s\n\npolitical parties. In evaluating the law’s imposition on associational rights, we must\n\n“weigh the ‘character and magnitude’ of the burden” it occasions. Timmons, 520 U.S. at\n\n358 (quoting Burdick, 504 U.S. at 434). We keep in mind also that “[a]ny interference\n\n\n\n 12\n\fwith the freedom of a party is simultaneously an interference with the freedom of its\n\nadherents.” Tashjian, 479 U.S. at 215 (quoting Democratic Party, 450 U.S. at 122).\n\n Subsection 24.2-509(A) grants the “duly constituted authorities” of the\n\nCommonwealth’s political parties considerable discretion in selecting the method of\n\nchoosing their nominees. The Incumbent Protection Act, subsection 24.1-509(B), carves\n\nexceptions to this rule in favor of incumbents. To recapitulate, the second and third\n\nsentences allow incumbent members of the General Assembly to dictate the method their\n\nparty shall use in selecting the nominee for the office that incumbent holds. The fourth\n\nsentence allows incumbent members of the U.S. House of Representatives, who were\n\nthemselves nominated by primary in the last election cycle, to require their party to use a\n\nprimary in the current election cycle to nominate a candidate for the office they hold if\n\nthey themselves are seeking reelection. In short, the associational rights of Virginia’s\n\npolitical parties that are recognized and protected by § 24.2-509(A) are taken away by §\n\n24.1-509(B) and given instead to a single individual—the incumbent.\n\n The weight of this burden could not be more obvious. The members of the 6th\n\nCongressional District Committee have, as generations of Americans did before them,\n\nbanded together to advance their political views. The selection of a nominee “often\n\ndetermines” the contours of the party platform. Cal. Democratic Party, 530 U.S. at 575.\n\nAnd “even when those positions are predetermined it is the nominee who becomes the\n\nparty’s ambassador to the general electorate in winning it over to the party’s views.” Id.\n\nYet, at the “crucial juncture” at which the members of this political association decide\n\nhow to select their nominee, id., the Commonwealth has taken the decision out of their\n\n 13\n\fhands: No matter what method of nomination the members of this party may prefer,\n\nVirginia law decrees that they must give way to the desire of the incumbent to hold a\n\nprimary if that incumbent was himself selected by primary previously and is seeking\n\nreelection.\n\n The burden is manifestly severe. This is not a case like Timmons, in which a\n\nparty’s ability to choose a nominee was reduced by only the small number of individuals\n\nthat already appeared elsewhere on the ballot. 520 U.S. at 351. Nor is this a case like\n\nClingman, in which the state’s Libertarian Party was required by state law to allow only\n\nits registered members and registered independent voters to participate in its primary. 544\n\nU.S. at 592. The burden there was not severe given the ease with which registered\n\nmembers of other parties who wanted to participate in the Libertarian primary could\n\nchange their registration. Id. Rather, this is a case in which the state has decided that the\n\nwishes of a party’s adherents must, in certain circumstances, be subordinated wholesale\n\nto the wishes of a single individual whose self-interest is self-evident; in these\n\ncircumstances, the party’s adherents are entirely shut out of the choice of nomination\n\nmethod—severely burdening their associational rights.\n\n C.\n\n Because the provision of the Incumbent Protection Act which protects\n\ncongressional incumbents—the fourth sentence—imposes a “severe” burden on the\n\nassociational rights of Virginia’s political parties, the Commonwealth must show that it is\n\n“narrowly tailored to serve a compelling state interest.” Cal. Democratic Party, 530 U.S.\n\nat 583. It cannot make this showing.\n\n 14\n\f Primaries add a crucial participatory dimension to democratic politics. Appellants\n\nassert that § 24.2-509(B) is akin to a mandatory primary statute, and therefore it serves\n\nthe interest of “assur[ing] that intraparty competition is resolved in a democratic fashion.”\n\nId. at 572. If § 24.2-509(B) truly were a mandatory primary statute its constitutionality\n\nwould be “too plain for argument.” Id. (quoting Am. Party of Tex. v. White, 415 U.S. 767,\n\n781 (1974)). But it is not: The statute does not by itself require any organ of a Virginia\n\npolitical party to use a primary as a method of nomination. Instead, the statute delegates\n\nthe power to force the party to use a primary to the incumbent office holder. Therein lies\n\nthe constitutional flaw.\n\n This delegation of power over the party to the incumbent office holder is not\n\nnarrowly tailored to meet the Commonwealth’s asserted interest. Under the terms of the\n\nstatute, the interest in democratic resolution of intraparty disputes will only be vindicated\n\nwhen and where an incumbent office holder decides that it is in his interest to do so. It is\n\nimplausible that the General Assembly would seek to vindicate this interest in such an\n\nodd, uneven, and underinclusive fashion. Instead, the text and structure of the law gives\n\nrise to the strong suggestion that the Incumbent Protection Act serves a different interest:\n\nthe interest, unsurprisingly, in incumbent protection.\n\n To be sure, incumbent protection is not per se an unconstitutional interest. In the\n\ncontext of redistricting, the Supreme Court has historically allowed maps to stand that\n\nwere drawn with the electoral interest of incumbents in mind. See, e.g., Karcher v.\n\nDaggett, 462 U.S. 725, 740 (1983). But the Court has not held that the interest in\n\nincumbent protection is a compelling one that can justify such direct intrusions on the\n\n 15\n\fFirst Amendment. See Gill v. Whitford, 138 S. Ct. 1916, 1934 (2018) (Kagan, J.,\n\nconcurring) (explaining that the Court did not address the First Amendment challenge to\n\nthe redistricting). Incumbent protection is simply not a strong enough interest here to\n\njustify the severe burden on the appellee’s associational rights.\n\n Incumbents, after all, are already blessed with myriad de facto advantages in the\n\nelectoral arena. Appellee’s expert, Professor Jeffrey A. Jenkins, testified that incumbents\n\ngenerally have better name recognition than challengers because of their time in the\n\npublic eye. J.A. 884. Incumbents also have the opportunity to win votes by enacting\n\npopular laws and servicing their constituents, and they have easier access to donors, as\n\nthey are proven winners. Id. All this contributes to the “scare-off” effect: potential\n\nchallengers, faced with the seemingly insurmountable hurdles, will decide not to run. Id.\n\n The other reason for incumbency advantage is more salutary. Voters may\n\nrecognize that incumbents provide our government with institutional memory and the\n\nwisdom that can only be won through experience. In the legislative branch, which could\n\nfind itself at a disadvantage when dealing with career officials and agency specialists of\n\nthe executive, the cumulative knowledge and experience brought by incumbents to the\n\nnegotiating table is particularly valuable. In this sense, incumbency evens the interbranch\n\nplaying field. Without it, novice legislators would find it more difficult to fulfill their\n\nconstitutional responsibilities.\n\n Thus, domination of the political parties by their incumbent office holders is,\n\nperhaps, a natural consequence of political reality. But to the already winning de facto\n\nhand dealt incumbents, § 24.2-509(B) adds a de jure ace: In the circumstances governed\n\n 16\n\fby the fourth sentence, challengers would have to compete with already advantaged\n\nincumbents in a selection process chosen by the incumbent himself. This goes too far. It\n\nnarrows the possibility of legislative renewal and refreshment through the infusion of\n\nnew blood. It risks making the electoral process sclerotic.\n\n Nothing in the foregoing analysis compromises the “major role” played by states\n\nin structuring their elections. Cal. Democratic Party, 530 U.S. at 572. Election\n\nadministration is necessarily an amalgam of state law and party procedures, and the\n\nCommonwealth is surely correct that the rights of political parties in this amalgam are not\n\nabsolute in character. We reiterate that “it is beyond question ‘that States may, and\n\ninevitably must, enact reasonable regulations of parties, elections, and ballots to reduce\n\nelection- and campaign-related disorder.’” Clingman, 544 U.S. at 593 (quoting Timmons,\n\n520 U.S. at 358). Rather, we simply hold that a state may not force a political party to\n\nhand control over its nomination method to a single, self-interested individual; the private\n\ninterest of an incumbent in winning reelection cannot, and certainly not in the manner\n\nchosen here, predominate over the associational rights of political parties.\n\n III.\n\n The district court also enjoined enforcement of the Act’s second and third\n\nsentences, which protect the nomination prerogatives of incumbent members of the\n\nGeneral Assembly. The Commonwealth argues that this was improper, as the Committee\n\nlacked standing to challenge those provisions. We disagree. The Committee suffered\n\ncognizable, traceable, and redressable injury from the Commonwealth’s application of\n\nthose sentences to its activities. And the second and third sentences are, if anything, even\n\n 17\n\fmore offensive to the First Amendment than the fourth. Accordingly, we affirm the\n\ndistrict court’s decision to enjoin the second and third sentences on § 24.2-509(B) as\n\nwell.\n\n Standing requires an injury in fact that is caused by the challenged conduct and is\n\nlikely to be redressed by a favorable decision. See Ohio Valley Envtl. Coal., Inc. v. Pruitt,\n\n893 F.3d 225, 229 (4th Cir. 2018). “To establish injury in fact, a plaintiff must show that\n\nhe or she suffered an invasion of a legally protected interest that is concrete and\n\nparticularized and actual or imminent, not conjectural or hypothetical.” Spokeo, Inc. v.\n\nRobins, 136 S. Ct. 1540, 1548 (2016) (internal quotation marks omitted). Throughout a\n\nlawsuit “the standing inquiry remains focused on whether the party invoking jurisdiction\n\nhad the requisite stake in the outcome when the suit was filed.” Davis v. Fed. Election\n\nComm’n, 554 U.S. 724, 734 (2008).\n\n The Committee suffered an injury in fact at the time the lawsuit was filed as a\n\nresult of the Commonwealth’s application of the second and third sentences, as\n\ndemonstrated by the “specific facts” adduced in its submissions to this court. Lujan v.\n\nDefenders of Wildlife, 504 U.S. 555, 561 (1992). These facts are as follows: The\n\nDepartment issues a series of forms for incumbents and party committees to notify the\n\nCommonwealth which nomination method they plan to use, as they are required to do by\n\nlaw. See Va. Code Ann. § 24.2-516. These forms reflect the Department’s understanding\n\nof how to apply the Incumbent Protection Act. And yet, throughout the 2016 election\n\ncycle and through the filing of this lawsuit, these forms applied the Act’s second and\n\nthird sentences, which should only apply to incumbent members of the General\n\n 18\n\fAssembly, to the 6th Congressional Committee as well. Incumbent members of Congress\n\nwere given the same plenary power to designate any method of nomination no matter the\n\ncircumstance, as if they were incumbent members of the General Assembly.\n\n The forms themselves best tell the story:\n\n DESIGNATION OF METHOD OF NOMINATION\n for\n SENATE OF VIRGINIA\n 2015\n ***\n I, the undersigned incumbent of the Senate of Virginia district indicated\n above, am seeking re-election and designate the following method of\n nomination to be used in determining the party’s candidate for this office\n subject to the forthcoming November general election.\n\nJ.A. 892.\n\n 2016 DESIGNATION OF METHOD OF NOMINATION\n ***\n I, the undersigned incumbent of the district indicated above, am seeking\n re-election and designate the following method of nomination to be used in\n determining the party’s candidate for this office subject to the coming\n November general election.\n\nJ.A. 873. The form used by incumbent General Assembly members in the 2015 election\n\ncycle and by incumbent Members of Congress in the 2016 election cycle are in all\n\nmaterial respects the same. As the Committee noted, “[n]ot only did Appellants\n\npromulgate these forms, they directed non-General Assembly incumbents and party\n\nchairmen to use them.” Resp. Br. of Appellee at 13.\n\n It is plain therefore that, on those facts, the Committee suffered a sufficiently\n\n“concrete” injury in fact to sustain its challenge to the second and third sentences of the\n\nAct. Because of the forms, any candidate that the 6th Congressional Committee wished to\n\n\n 19\n\frecruit, or anyone contemplating an electoral challenge to the incumbent, faced the\n\nprospect of having to compete in a nomination process selected by that incumbent.\n\nPlainly, this prospect would “dramatically change[] the plaintiffs’ decisions about\n\ncampaign financing, messages to stress, and candidates to recruit.” Miller I, 462 F.3d at\n\n317. This distortion of political decisionmaking constitutes an ongoing and concrete\n\ninjury sufficient to meet the injury-in-fact prong of constitutional standing analysis. Id. at\n\n317-18.\n\n That injury, of course, is particularized because the 6th Congressional Committee\n\nserves a unique function in selecting the Republican nominee for Virginia’s 6th\n\nCongressional District. See Lujan, 504 U.S. at 560. The remaining standing analysis is\n\nstraightforward: The injury was caused by promulgation of the forms based on the Act’s\n\nsecond and third sentences, and therefore will be redressed if we find those sentences to\n\nbe inconsistent with the First Amendment. For these reasons, the Committee has standing\n\nto challenge the portions of § 24.2-509(B) that protect the nomination prerogatives of\n\nGeneral Assembly members.\n\n In response, the Department argues that the challenge to the second and third\n\nsentences became moot when the Department updated the offending election forms. 2 But\n\n\n2\n The Department also argues that plaintiff’s challenge to the Act’s fourth sentence is\nmoot. It notes that because the current 6th District incumbent was selected by convention,\nthe plaintiff will not be forced to accede to a primary until 2022 at the earliest. But that\nargument relies on the same cramped interpretation of standing that we rejected in Miller\nI, 462 F.3d at 316-18. The injuries inflicted by laws that distort the primary process, like\nthe Incumbent Protection Act, are not confined to the short duration of any particular\nprimary, but instead reflect the reality that “campaign planning decisions have to be made\n(Continued)\n 20\n\fthe update occurred after the lawsuit had been filed. Promulgating new forms may well\n\nhave been the right thing to do in accordance with state law. But as a litigation tactic,\n\nsuch backpedaling will rarely serve to moot a case in federal court. Friends of the Earth,\n\nInc. v. Laidlaw Environmental Services (TOC), Inc., 528 U.S. 167, 189-94 (2000). The\n\nmootness doctrine ordinarily does not extend to situations where a party quits its\n\noffending conduct partway through litigation. Id. After all, “a party should not be able to\n\nevade judicial review, or to defeat a judgment, by temporarily altering questionable\n\nbehavior.” Porter v. Clarke, 852 F.3d 358, 364 (4th Cir. 2017) (internal quotation marks\n\nomitted). To overcome that general rule, the Department bears “[t]he heavy burden of\n\npersuading the court,” Laidlaw, 528 U.S. 167, 189 (2000) (internal quotation marks and\n\nalterations omitted), that it is “absolutely clear that the allegedly wrongful behavior could\n\nnot reasonably be expected to recur.” Wall v. Wade, 741 F.3d 492, 497 (2014) (quoting\n\nLaidlaw, 528 U.S. at 189).\n\n The Department cannot carry this burden. It has a history of frequently revising\n\nthe relevant election forms. The forms used for congressional nominations in 2014, for\n\nexample, reflected the fourth sentence of the Incumbent Protection Act and not the\n\nsecond and third. Yet the congressional nomination forms were inexplicably changed for\n\n\nmonths, or even years, in advance of the election to be effective.” Id. at 317-18. The 6th\nCongressional Committee’s claims thus did not become moot with the passing of the\n2018 election season. The dispute over the Act’s fourth sentence, rather, is alive and well.\nEven so, if the Department were correct that electoral disputes became moot with each\npassing election cycle, this challenge, like many electoral challenges, would plainly be\ncapable of repetition yet evading review. See, e.g., Davis v. Fed. Election Comm’n, 554\nU.S. 724, 735-36 (2008).\n\n 21\n\fthe 2016 congressional elections to reflect the Act’s more fulsome General Assembly\n\nprotections instead. The Department has offered no explanation for why the forms were\n\nchanged to the benefit of incumbents between the 2014 and 2016 congressional elections.\n\nEven though the forms apparently have been edited once again, we have little confidence\n\nthat the forms will not revert back if we hold that this lawsuit is moot. Indeed, that danger\n\nis particularly acute when, as here, a change in the forms would confer benefits upon\n\npolitical incumbents. The Incumbent Protection Act transparently advances the interests\n\nof those who control the apparatus of government; it is hardly beyond the realm of\n\nplausibility that it would be administered with that same purpose in mind. The\n\nDepartment’s May 23, 2018 Suggestion of Mootness is accordingly denied.\n\n We may thus properly consider the 6th Congressional Committee’s facial and as\n\napplied First Amendment challenges to the Incumbent Protection Act’s protection of\n\nincumbent members of the General Assembly. A facial challenge to a law will succeed\n\nafter a showing “that no set of circumstances exist under which the law would be valid,\n\nor that the law lacks any plainly legitimate sweep.” Greater Balt. Center for Pregnancy\n\nConcerns, Inc. v. Mayor & City Council of Balt., 721 F.3d 264, 282 (4th Cir. 2013) (en\n\nbanc) (internal quotation marks and alterations omitted). In the First Amendment context,\n\na facial challenge may also succeed under overbreadth doctrine. Id. But there is no need\n\nto employ overbreadth doctrine in this case, for the Act’s second and third sentences\n\ncannot be applied in a manner consistent with the First Amendment.\n\n The Department fails to identify a single circumstance where the Act’s second and\n\nthird sentences could be lawfully applied. And we find none. The second and third\n\n 22\n\fsentences not only share the constitutional infirmities of the fourth sentence but exhibit\n\nthose infirmities to an even greater degree. The fourth sentence allows some incumbents\n\nto force a primary under certain designated circumstances. The second sentence goes\n\nfurther by empowering incumbents to impose their choice of any method of nomination\n\nno matter what the party prefers under almost any circumstances. 3 These advantages,\n\nwhen given to state or federal incumbents, run afoul of the First Amendment for all the\n\nreasons discussed in detail in Part II, supra.\n\n The Department raises yet one more challenge, arguing that the district court was\n\nwrong to enjoin the Incumbent Protection Act in its entirety. See Va. Code Ann. § 24.2-\n\n509(B). We review the district court’s decision to enjoin the statute for abuse of\n\ndiscretion. U.S. Airline Pilots Ass’n v. Awappa, LLC, 615 F.3d 312, 320 (4th Cir. 2010).\n\nThe Act comprises six sentences. We have now found that each of its operative\n\nprovisions—namely the second, third, and fourth sentences—is unconstitutional. The\n\nremaining sentences merely explain how to apply them. The district court did not abuse\n\nits discretion in enjoining the Incumbent Protection Act in toto.\n\n IV.\n\n Our decision is a narrow one. It is directed at a discrete constitutional imbalance\n\ncreated by permitting single office holders to negate the associational rights of political\n\nparties in an area central to the party’s very reason for being. Our ruling in no way limits\n\n 3\n The third sentence applies in the relatively rare situation where there is more than\none incumbent for the same office. In that situation, the statute requires incumbents’\nconsent for any method of nomination other than a primary. § 24.2-509(B).\n\n\n 23\n\fthe ability of states to enact “reasonable regulations of parties, elections, and ballots.”\n\nTimmons, 520 U.S. at 358. The associational rights of political parties are, after all, not\n\nabsolute. Laws that impose a slight or lesser burden on associational rights are owed\n\ndeference, especially when justified by the need “to reduce election- and campaign-\n\nrelated disorder.” Id. But our constitutional responsibility, set forth so plainly by the\n\nSupreme Court, requires us to ensure that this “deference does not risk such constitutional\n\nevils as, say, permitting incumbents to insulate themselves from effective electoral\n\nchallenge.” Nixon v. Shrink Mo. Gov’t PAC, 528 U.S. 377, 402 (2000) (Breyer, J.,\n\nconcurring). The Incumbent Protection Act reflects precisely that infirmity, and it is\n\nprecisely why we cannot allow the Act to stand.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 24\n[END_CASE]", "role": "user" } ]
4,581,300
UNITED STATES of America, Plaintiff - Appellee, v. Carl Javan ROSS, Defendant - Appellant.
United States v. Carl Ross
2019-01-14
17-4242
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Niemeyer, Harris", "parties": "", "opinions": [{"author": "Vacated and remanded by published opinion. Chief Judge Gregory wrote the opinion, in", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4242\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nCARL JAVAN ROSS,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the District of Maryland, at Baltimore.\nJ. Frederick Motz, Senior District Judge. (1:16-cr-00020-JFM)\n\n\nArgued: November 1, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, NIEMEYER, and HARRIS, Circuit Judges.\n\n\nVacated and remanded by published opinion. Chief Judge Gregory wrote the opinion, in\nwhich Judge Niemeyer and Judge Harris joined.\n\n\nARGUED: Paresh S. Patel, OFFICE OF THE FEDERAL PUBLIC DEFENDER,\nGreenbelt, Maryland, for Appellant. Paul E. Budlow, OFFICE OF THE UNITED\nSTATES ATTORNEY, Baltimore, Maryland, for Appellee. ON BRIEF: James Wyda,\nFederal Public Defender, Baltimore, Maryland, Joanna Silver, Appellate Attorney,\nOFFICE OF THE FEDERAL PUBLIC DEFENDER, Greenbelt, Maryland, for\nAppellant. Stephen M. Schenning, Acting United States Attorney, Paul Riley, Assistant\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Baltimore,\nMaryland, for Appellee.\n\fGREGORY, Chief Judge:\n\n Defendant-Appellant Carl Javan Ross appeals his sentence, which the district\n\ncourt imposed after Ross was convicted of two counts in violation of 18 U.S.C.\n\n§ 2252(a)(2), and one count in violation of 18 U.S.C. § 2252(a)(4)(b). Ross contends the\n\ndistrict court did not explain why it imposed his term of confinement and did not address\n\nhis non-frivolous arguments in favor of a lower sentence. These omissions render his\n\nsentence procedurally unreasonable, according to Ross. In addition, Ross argues the\n\ndistrict court committed procedural error with its imposition of special conditions of\n\nsupervised release. We agree, and for the reasons that follow, we vacate Ross’s sentence\n\nand remand for resentencing.\n\n\n\n I.\n\n On December 7, 2016, a jury convicted Ross of two counts of receipt of child\n\npornography, in violation of 18 U.S.C. § 2252(a)(2), and one count of possession of child\n\npornography in violation of 18 U.S.C. § 2252(a)(4)(b). The United States Probation\n\nOffice filed a Presentence Investigation Report (“PSR”) that included a recommended\n\nterm of confinement and recommended special conditions of supervised released. The\n\nPSR calculated Ross’s final offense level as 35 and included various enhancements\n\nreflecting the repugnant nature of the materials in his possession. J.A. 92-93. The PSR\n\ncalculated Ross’s Criminal History Category as II given that he had a prior state court\n\n\n\n\n 2\n\fconviction for a sexual offense involving a minor. 1 J.A. 94. The Government and Ross\n\nboth submitted sentencing memoranda.\n\n The district court held a sentencing hearing and adopted the PSR’s advisory\n\nGuidelines range: 188 months to 235 months in prison. The district court ordered a term\n\nof confinement of 120 months as to each count, to run concurrently with each other but\n\nconsecutive to his state court sentence. J.A. 63. The district court placed Ross on\n\nsupervised release for the rest of his life “subject to the special conditions set forth in the\n\nrecommended conditions of supervision.” Id. Ross timely appealed. We have\n\njurisdiction under 28 U.S.C. § 1291.\n\n\n\n II.\n\n At the sentencing hearing, the Government asked the district court to impose a\n\nterm of confinement of 120 months to be served consecutive to his 120-months state\n\ncourt term of confinement instead of Ross’s requested 60-month mandatory minimum\n\nsentence which he wanted to run concurrently to his state court sentence. The\n\nGovernment argued Ross’s request resulted in “essentially no sentence” and “absolutely\n\nzero impact, zero additional punishment as a result of the conduct in this case.” J.A. 17.\n\nAccording to the Government, the gravity of Ross’s conduct justified a longer and non-\n\nconcurrent sentence and his state court conviction constituted evidence of Ross’s threat to\n\nthe public. The Government highlighted that Ross deleted much of the illegal material he\n\n 1\n While awaiting trial in his federal case, Ross received a state court term of\nconfinement of 240 months, with 120 months suspended. J.A. 93.\n\n 3\n\fpossessed in order to avoid detection, still denied participating in the conduct that gave\n\nrise to his state court conviction and generally lacked remorse for his actions.\n\n Counsel for Ross replied that the Government’s sentencing position essentially\n\namounted to an above-Guidelines sentence because it would result in two separate 120-\n\nmonth terms of confinement that run consecutively. Counsel argued the district court\n\nshould consider his state court term of confinement when calculating his sentence. In\n\naddition, Ross’s counsel argued that felony convictions relating to sexual offenses are\n\nalready very punitive and that the lifelong social stigma Ross faces justified his request\n\nfor a 60-month concurrent sentence. Ross’s counsel defended his requested sentence\n\ngiven the stringent demands of supervised release he will face and the likelihood of his\n\nrecidivism if he violates his terms.\n\n Additionally, Ross’s counsel further explained while Ross did not appear\n\nremorseful, his demeanor reflected his mental health challenges and not a lack of\n\nremorse. Counsel presented Ross’s psychological forensic report, which explained\n\nRoss’s diagnosis of schizoid personality disorder, adjustment disorder, and an unspecified\n\nneurodevelopmental disorder. These conditions should have been considered in\n\nmitigation, according to Ross’s counsel. For instance, counsel asserted Ross’s mental\n\ndisorder caused Ross to insist on going to trial in his state court case against the advice of\n\nhis lawyer. Ross’s counsel further indicated that Ross’s mental health issues similarly\n\ncaused him to elect to go to trial instead of pleading guilty in his federal case as well,\n\nleading to increased exposure to criminal penalties. Ross’s counsel argued that Ross\n\nmaintained gainful employment, cared for his aging mother and had only a relatively\n\n 4\n\fsmall amount of illicit material compared to the average child pornography offender.\n\nAccording to Ross’s counsel, the district court should have considered all of these factors\n\nwhen calculating Ross’s term of confinement.\n\n Upon hearing arguments from both the Government and Ross, the district court\n\nimposed a sentence of 120 months to be served consecutive to his state court term of\n\nconfinement. The district court explained that it found Ross’s arguments unpersuasive\n\nand stated that “the Government’s recommendation is appropriate and that’s my sentence\n\nand the reason for it.” J.A. 63. After the district court pronounced Ross’s sentence, the\n\nGovernment requested the court to explain its basis for the sentence under the 18 U.S.C.\n\n§ 3553(a) factors. J.A. 63-64. The district court provided the following explanation:\n\n Well, I mean, it’s obviously [sic] the offense is a serious one. In terms of\n specific deterrence, I am concerned about the lack of remorse while even if\n there was remorse, there is a body of statistical evidence that—well, I’m\n not going to say that, but that I believe it’s a specific deterrence, requires\n the sentence I’m imposing. I did not find that the guidelines are so flawed\n as to essentially have no sentence at all. And in terms of general\n deterrence, I think that the sentence I’m imposing is required.\n\nJ.A. 64. In addition, the district court imposed a lifetime of supervised release. The\n\nspecial conditions of his supervised release prohibit Ross from using “computer systems,\n\nInternet-capable devices and/or similar electronic devices at any location (including\n\nemployment or educational program) without the prior written approval” of the probation\n\nofficer, and from owning, using, possessing, viewing, or reading any pornographic\n\nmaterials, as defined in 18 U.S.C. § 2256(2). J.A. 79.\n\n\n\n\n 5\n\f III.\n\n Under the standard set forth in Gall v. United States, a sentence is reviewed for\n\nboth procedural and substantive reasonableness. 552 U.S. 38, 51 (2007). In the instant\n\ncase, procedural reasonableness is at issue. In determining procedural reasonableness,\n\nthis Court considers whether the district court properly calculated the defendant’s\n\nadvisory guidelines range, gave the parties an opportunity to argue for an appropriate\n\nsentence, considered the 18 U.S.C. § 3553(a) factors, and sufficiently explained the\n\nselected sentence. Id. at 49-51. We do not require the district court to “robotically tick\n\nthrough § 3553(a)’s every subsection, particularly when imposing a within-Guidelines\n\nsentence.” United States v. Powell, 650 F.3d 388, 395 (4th Cir. 2011) (internal citation\n\nand quotation marks omitted). Nevertheless, the district court must provide some\n\nindividualized assessment “justifying the sentence imposed and rejection of arguments\n\nfor a higher or lower sentence based on § 3553.” United States v. Lynn, 592 F.3d 572,\n\n584 (4th Cir. 2010). We will first turn to the procedural unreasonableness of Ross’s term\n\nof confinement and then to similar deficiencies pertaining to Ross’s special conditions of\n\nsupervised release.\n\n\n\n IV.\n\n Ross challenged his term of confinement at his sentencing hearing and therefore\n\nthis Court reviews the reasonableness of the term under “a deferential abuse-of-discretion\n\nstandard.” United States v. Cox, 744 F.3d 305, 308 (4th Cir. 2014). Under the law of this\n\ncircuit a district court must address or consider all non-frivolous reasons presented for\n\n 6\n\fimposing a different sentence and explain why he has rejected those arguments. United\n\nStates v. Blue, 877 F.3d 513, 518 (4th Cir. 2017); Slappy, 872 F.3d 202, 207 (4th Cir.\n\n2017) (internal citation and quotation marks omitted). Here, the district court did not\n\nfollow circuit precedent during Ross’s sentencing proceedings when determining his term\n\nof confinement. Indeed, the district court did not address or consider any of the\n\nnumerous non-frivolous arguments advanced by Ross’s counsel requesting a lower and\n\nconcurrent sentence. This Court has previously held that “[t]he adequacy of the\n\nsentencing court’s explanation depends on the complexity of each case. There is no\n\nmechanical approach to our sentencing review. The appropriateness of brevity or length,\n\nconsciousness or detail, when to write, what to say, depends upon the circumstances.”\n\nBlue, 877 F.3d at 518 (internal quotation marks and citations omitted). Here, it is\n\nundisputable that the sentencing court provided an insufficient explanation of its sentence\n\nand did not provide an “individualized assessment” of important mitigation evidence. Id.\n\nAn individualized assessment requires “that district courts consider the defendant’s\n\nnonfrivolous arguments for a downward departure, impose an individualized sentence\n\nbased on the characteristics of the defendant and the facts of the case, and explain the\n\nsentence chosen.” Id.\n\n As an initial matter, the district court did not provide an individualized assessment\n\nregarding important mitigation evidence related to Ross’s mental health. The district\n\ncourt noted that Ross lacked remorse but did not address his counsel’s arguments that his\n\nmental health issues, such as schizoid personality disorder, adjustment disorder, and an\n\nunspecified neurodevelopmental disorder, caused him to appear to lack remorse.\n\n 7\n\fMoreover, the district court did not address counsel’s arguments about how Ross’s\n\nmental health issues caused him to pursue litigation strategies that were contrary to his\n\nown interest and consequently raised his sentencing exposure. Finally, the district court\n\ndid not address Ross’s history of gainful employment, his role as a caretaker for his aging\n\nmother, and the relatively small amount of illicit material found in his computer as\n\nmitigating factors when calculating his term of confinement.\n\n The district court’s post-sentencing commentary is non-responsive to Ross’s\n\narguments and violates the legal standards for procedural reasonableness. The Supreme\n\nCourt makes clear that the district court must sufficiently address the parties’ arguments\n\nand provide an explanation for its sentence for this Court to engage in “meaningful\n\nappellate review.” Gall, 552 U.S. at 50. Although we have held that it is sometimes\n\npossible to discern a sentencing court’s rationale from the context surrounding its\n\ndecision, United States v. Montes-Pineda, 445 F.3d 375, 381 (4th Cir. 2006), an appellate\n\ncourt nonetheless “may not guess at the district court’s rationale, searching the record for\n\nstatements by the Government or defense counsel or for any other clues that might\n\nexplain a sentence,” United States v. Carter, 564 F.3d 325, 329-30 (4th Cir. 2009). The\n\ncomments made by the district court require this Court to impermissibly speculate as to\n\nthe reason for the district court’s sentencing decision.\n\n Contrary to the Government’s position, it is not harmless error that the district\n\ncourt did not explain its justification for Ross’s term of confinement. “For a procedural\n\nsentencing error to be harmless, the government must prove that the error did not have a\n\nsubstantial and injurious effect or influence on the result.” Lynn, 592 F.3d at 585\n\n 8\n\f(internal citation and quotation marks omitted). This Court cannot look at the district\n\ncourt’s comments and determine that the explicit consideration of Ross’s various\n\nmitigating arguments would not have affected the ultimate term of confinement imposed.\n\nFor instance, the district court mentioned that Ross lacked remorse when discussing its\n\nrationale for Ross’s term of confinement. But the record contains significant evidence of\n\nRoss’s mental health challenges as they affect his ability to show remorse. Given this\n\nrecord evidence, Ross’s demeanor arguably reflects mental health disorders and not a\n\ncallousness or denial of responsibility. The district court could have conceivably given\n\nRoss a different sentence if it had considered his non-frivolous mitigation arguments.\n\nThe district court had an obligation to specifically address Ross’s non-frivolous\n\narguments. It did not do so here. As noted at oral argument, even the Government\n\nnoticed that the district court did not provide a sufficient explanation and asked for\n\nclarification. Nonetheless, the district court cannot meet its responsibility through\n\nbroadly referring to the § 3553(a) factors in lieu of addressing the parties’ non-frivolous\n\narguments.\n\n\n\n V.\n\n The requirement that the district court adequately explain Ross’s term of\n\nconfinement similarly applies to the special conditions of his supervised release. United\n\nStates v. Armel, 585 F.3d 182, 186 (4th Cir. 2009). Ross did not challenge the special\n\nconditions of supervised release before the district court and concedes that this Court\n\n\n\n 9\n\fshould apply a plain-error standard of review. 2 United States v. Wesley, 81 F.3d 482, 484\n\n(4th Cir. 1996) (explaining that we reverse on plain error if the district court erred, the\n\nerror was plain, and the error affected the defendant’s substantial rights). Plain errors\n\nexist “if the settled law of the Supreme Court or this circuit establishes that an error has\n\noccurred.” United States v. Ramirez-Castillo, 748 F.3d 205, 215 (4th Cir. 2014).\n\n In imposing the conditions of supervised release, the district court at the\n\nsentencing hearing said, “I will place you on supervised release for life subject to the\n\ngeneral conditions and special conditions set forth in the recommended conditions of\n\nsupervision.” J.A. 63. The district court did not explain why Ross was given any of the\n\nspecial conditions for life. This lack of explanation contravenes the law of this circuit\n\nand constitutes plain error. Armel, 585 F.3d at 186. This error is not harmless. It is the\n\nsettled law of this circuit that Ross has a right to know why he faces special conditions\n\nthat will forever modify the course of his life, and the district court’s silence violated his\n\nrights. Id. This Court cannot look at the district court’s comments and ascertain its\n\nrationale for imposing very restrictive special conditions for the duration of Ross’s life.\n\n\n\n\n 2\n The parties briefed the special conditions of supervised release argument only\nunder the plain-error standard. Recent circuit precedent suggests, however, that the abuse\nof discretion standard should now apply because Ross challenged the term of\nconfinement and thus preserved his challenge to the special conditions imposed as part of\nhis supervised release. United States v. Ketter, 908 F.3d 61, 66 (4th Cir. 2018) (adopting\na unitary approach to sentencing under which the term of confinement and term of\nsupervised release constitute the same sentence for purposes of appellate review). Ross is\nentitled to relief under either standard.\n\n\n 10\n\fIt is procedurally unreasonable to impose special conditions for the remainder of Ross’s\n\nlife without providing an explanation or rationale for their justification. 3\n\n\n\n\n VI.\n\n In conclusion, given that the district court failed to address Ross’s non-frivolous\n\nmitigation arguments and to properly explain its rationale for his term of confinement and\n\nhis special conditions, we vacate his sentence and remand so that the district court may\n\nprovide a sufficient explanation for the significant deprivation of liberty Ross faces as a\n\nresult of his criminal conduct. This Court makes no assessment regarding the fairness or\n\npropriety of Ross’s term of confinement or special conditions of supervised release.\n\n\n\n VACATED AND REMANDED\n\n\n\n\n 3\n Given that this Court is vacating Ross’s sentence regarding both the term of\nconfinement and special conditions of supervised release, this Court need not address\nRoss’s remaining arguments regarding the propriety of his special conditions.\n\n 11", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358553/", "author_raw": "Vacated and remanded by published opinion. Chief Judge Gregory wrote the opinion, in"}]}
GREGORY
NIEMEYER
HARRIS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4581300/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff - Appellee, v. Carl Javan ROSS, Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-14\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4242\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nCARL JAVAN ROSS,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the District of Maryland, at Baltimore.\nJ. Frederick Motz, Senior District Judge. (1:16-cr-00020-JFM)\n\n\nArgued: November 1, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, NIEMEYER, and HARRIS, Circuit Judges.\n\n\nVacated and remanded by published opinion. Chief Judge Gregory wrote the opinion, in\nwhich Judge Niemeyer and Judge Harris joined.\n\n\nARGUED: Paresh S. Patel, OFFICE OF THE FEDERAL PUBLIC DEFENDER,\nGreenbelt, Maryland, for Appellant. Paul E. Budlow, OFFICE OF THE UNITED\nSTATES ATTORNEY, Baltimore, Maryland, for Appellee. ON BRIEF: James Wyda,\nFederal Public Defender, Baltimore, Maryland, Joanna Silver, Appellate Attorney,\nOFFICE OF THE FEDERAL PUBLIC DEFENDER, Greenbelt, Maryland, for\nAppellant. Stephen M. Schenning, Acting United States Attorney, Paul Riley, Assistant\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Baltimore,\nMaryland, for Appellee.\n\fGREGORY, Chief Judge:\n\n Defendant-Appellant Carl Javan Ross appeals his sentence, which the district\n\ncourt imposed after Ross was convicted of two counts in violation of 18 U.S.C.\n\n§ 2252(a)(2), and one count in violation of 18 U.S.C. § 2252(a)(4)(b). Ross contends the\n\ndistrict court did not explain why it imposed his term of confinement and did not address\n\nhis non-frivolous arguments in favor of a lower sentence. These omissions render his\n\nsentence procedurally unreasonable, according to Ross. In addition, Ross argues the\n\ndistrict court committed procedural error with its imposition of special conditions of\n\nsupervised release. We agree, and for the reasons that follow, we vacate Ross’s sentence\n\nand remand for resentencing.\n\n\n\n I.\n\n On December 7, 2016, a jury convicted Ross of two counts of receipt of child\n\npornography, in violation of 18 U.S.C. § 2252(a)(2), and one count of possession of child\n\npornography in violation of 18 U.S.C. § 2252(a)(4)(b). The United States Probation\n\nOffice filed a Presentence Investigation Report (“PSR”) that included a recommended\n\nterm of confinement and recommended special conditions of supervised released. The\n\nPSR calculated Ross’s final offense level as 35 and included various enhancements\n\nreflecting the repugnant nature of the materials in his possession. J.A. 92-93. The PSR\n\ncalculated Ross’s Criminal History Category as II given that he had a prior state court\n\n\n\n\n 2\n\fconviction for a sexual offense involving a minor. 1 J.A. 94. The Government and Ross\n\nboth submitted sentencing memoranda.\n\n The district court held a sentencing hearing and adopted the PSR’s advisory\n\nGuidelines range: 188 months to 235 months in prison. The district court ordered a term\n\nof confinement of 120 months as to each count, to run concurrently with each other but\n\nconsecutive to his state court sentence. J.A. 63. The district court placed Ross on\n\nsupervised release for the rest of his life “subject to the special conditions set forth in the\n\nrecommended conditions of supervision.” Id. Ross timely appealed. We have\n\njurisdiction under 28 U.S.C. § 1291.\n\n\n\n II.\n\n At the sentencing hearing, the Government asked the district court to impose a\n\nterm of confinement of 120 months to be served consecutive to his 120-months state\n\ncourt term of confinement instead of Ross’s requested 60-month mandatory minimum\n\nsentence which he wanted to run concurrently to his state court sentence. The\n\nGovernment argued Ross’s request resulted in “essentially no sentence” and “absolutely\n\nzero impact, zero additional punishment as a result of the conduct in this case.” J.A. 17.\n\nAccording to the Government, the gravity of Ross’s conduct justified a longer and non-\n\nconcurrent sentence and his state court conviction constituted evidence of Ross’s threat to\n\nthe public. The Government highlighted that Ross deleted much of the illegal material he\n\n 1\n While awaiting trial in his federal case, Ross received a state court term of\nconfinement of 240 months, with 120 months suspended. J.A. 93.\n\n 3\n\fpossessed in order to avoid detection, still denied participating in the conduct that gave\n\nrise to his state court conviction and generally lacked remorse for his actions.\n\n Counsel for Ross replied that the Government’s sentencing position essentially\n\namounted to an above-Guidelines sentence because it would result in two separate 120-\n\nmonth terms of confinement that run consecutively. Counsel argued the district court\n\nshould consider his state court term of confinement when calculating his sentence. In\n\naddition, Ross’s counsel argued that felony convictions relating to sexual offenses are\n\nalready very punitive and that the lifelong social stigma Ross faces justified his request\n\nfor a 60-month concurrent sentence. Ross’s counsel defended his requested sentence\n\ngiven the stringent demands of supervised release he will face and the likelihood of his\n\nrecidivism if he violates his terms.\n\n Additionally, Ross’s counsel further explained while Ross did not appear\n\nremorseful, his demeanor reflected his mental health challenges and not a lack of\n\nremorse. Counsel presented Ross’s psychological forensic report, which explained\n\nRoss’s diagnosis of schizoid personality disorder, adjustment disorder, and an unspecified\n\nneurodevelopmental disorder. These conditions should have been considered in\n\nmitigation, according to Ross’s counsel. For instance, counsel asserted Ross’s mental\n\ndisorder caused Ross to insist on going to trial in his state court case against the advice of\n\nhis lawyer. Ross’s counsel further indicated that Ross’s mental health issues similarly\n\ncaused him to elect to go to trial instead of pleading guilty in his federal case as well,\n\nleading to increased exposure to criminal penalties. Ross’s counsel argued that Ross\n\nmaintained gainful employment, cared for his aging mother and had only a relatively\n\n 4\n\fsmall amount of illicit material compared to the average child pornography offender.\n\nAccording to Ross’s counsel, the district court should have considered all of these factors\n\nwhen calculating Ross’s term of confinement.\n\n Upon hearing arguments from both the Government and Ross, the district court\n\nimposed a sentence of 120 months to be served consecutive to his state court term of\n\nconfinement. The district court explained that it found Ross’s arguments unpersuasive\n\nand stated that “the Government’s recommendation is appropriate and that’s my sentence\n\nand the reason for it.” J.A. 63. After the district court pronounced Ross’s sentence, the\n\nGovernment requested the court to explain its basis for the sentence under the 18 U.S.C.\n\n§ 3553(a) factors. J.A. 63-64. The district court provided the following explanation:\n\n Well, I mean, it’s obviously [sic] the offense is a serious one. In terms of\n specific deterrence, I am concerned about the lack of remorse while even if\n there was remorse, there is a body of statistical evidence that—well, I’m\n not going to say that, but that I believe it’s a specific deterrence, requires\n the sentence I’m imposing. I did not find that the guidelines are so flawed\n as to essentially have no sentence at all. And in terms of general\n deterrence, I think that the sentence I’m imposing is required.\n\nJ.A. 64. In addition, the district court imposed a lifetime of supervised release. The\n\nspecial conditions of his supervised release prohibit Ross from using “computer systems,\n\nInternet-capable devices and/or similar electronic devices at any location (including\n\nemployment or educational program) without the prior written approval” of the probation\n\nofficer, and from owning, using, possessing, viewing, or reading any pornographic\n\nmaterials, as defined in 18 U.S.C. § 2256(2). J.A. 79.\n\n\n\n\n 5\n\f III.\n\n Under the standard set forth in Gall v. United States, a sentence is reviewed for\n\nboth procedural and substantive reasonableness. 552 U.S. 38, 51 (2007). In the instant\n\ncase, procedural reasonableness is at issue. In determining procedural reasonableness,\n\nthis Court considers whether the district court properly calculated the defendant’s\n\nadvisory guidelines range, gave the parties an opportunity to argue for an appropriate\n\nsentence, considered the 18 U.S.C. § 3553(a) factors, and sufficiently explained the\n\nselected sentence. Id. at 49-51. We do not require the district court to “robotically tick\n\nthrough § 3553(a)’s every subsection, particularly when imposing a within-Guidelines\n\nsentence.” United States v. Powell, 650 F.3d 388, 395 (4th Cir. 2011) (internal citation\n\nand quotation marks omitted). Nevertheless, the district court must provide some\n\nindividualized assessment “justifying the sentence imposed and rejection of arguments\n\nfor a higher or lower sentence based on § 3553.” United States v. Lynn, 592 F.3d 572,\n\n584 (4th Cir. 2010). We will first turn to the procedural unreasonableness of Ross’s term\n\nof confinement and then to similar deficiencies pertaining to Ross’s special conditions of\n\nsupervised release.\n\n\n\n IV.\n\n Ross challenged his term of confinement at his sentencing hearing and therefore\n\nthis Court reviews the reasonableness of the term under “a deferential abuse-of-discretion\n\nstandard.” United States v. Cox, 744 F.3d 305, 308 (4th Cir. 2014). Under the law of this\n\ncircuit a district court must address or consider all non-frivolous reasons presented for\n\n 6\n\fimposing a different sentence and explain why he has rejected those arguments. United\n\nStates v. Blue, 877 F.3d 513, 518 (4th Cir. 2017); Slappy, 872 F.3d 202, 207 (4th Cir.\n\n2017) (internal citation and quotation marks omitted). Here, the district court did not\n\nfollow circuit precedent during Ross’s sentencing proceedings when determining his term\n\nof confinement. Indeed, the district court did not address or consider any of the\n\nnumerous non-frivolous arguments advanced by Ross’s counsel requesting a lower and\n\nconcurrent sentence. This Court has previously held that “[t]he adequacy of the\n\nsentencing court’s explanation depends on the complexity of each case. There is no\n\nmechanical approach to our sentencing review. The appropriateness of brevity or length,\n\nconsciousness or detail, when to write, what to say, depends upon the circumstances.”\n\nBlue, 877 F.3d at 518 (internal quotation marks and citations omitted). Here, it is\n\nundisputable that the sentencing court provided an insufficient explanation of its sentence\n\nand did not provide an “individualized assessment” of important mitigation evidence. Id.\n\nAn individualized assessment requires “that district courts consider the defendant’s\n\nnonfrivolous arguments for a downward departure, impose an individualized sentence\n\nbased on the characteristics of the defendant and the facts of the case, and explain the\n\nsentence chosen.” Id.\n\n As an initial matter, the district court did not provide an individualized assessment\n\nregarding important mitigation evidence related to Ross’s mental health. The district\n\ncourt noted that Ross lacked remorse but did not address his counsel’s arguments that his\n\nmental health issues, such as schizoid personality disorder, adjustment disorder, and an\n\nunspecified neurodevelopmental disorder, caused him to appear to lack remorse.\n\n 7\n\fMoreover, the district court did not address counsel’s arguments about how Ross’s\n\nmental health issues caused him to pursue litigation strategies that were contrary to his\n\nown interest and consequently raised his sentencing exposure. Finally, the district court\n\ndid not address Ross’s history of gainful employment, his role as a caretaker for his aging\n\nmother, and the relatively small amount of illicit material found in his computer as\n\nmitigating factors when calculating his term of confinement.\n\n The district court’s post-sentencing commentary is non-responsive to Ross’s\n\narguments and violates the legal standards for procedural reasonableness. The Supreme\n\nCourt makes clear that the district court must sufficiently address the parties’ arguments\n\nand provide an explanation for its sentence for this Court to engage in “meaningful\n\nappellate review.” Gall, 552 U.S. at 50. Although we have held that it is sometimes\n\npossible to discern a sentencing court’s rationale from the context surrounding its\n\ndecision, United States v. Montes-Pineda, 445 F.3d 375, 381 (4th Cir. 2006), an appellate\n\ncourt nonetheless “may not guess at the district court’s rationale, searching the record for\n\nstatements by the Government or defense counsel or for any other clues that might\n\nexplain a sentence,” United States v. Carter, 564 F.3d 325, 329-30 (4th Cir. 2009). The\n\ncomments made by the district court require this Court to impermissibly speculate as to\n\nthe reason for the district court’s sentencing decision.\n\n Contrary to the Government’s position, it is not harmless error that the district\n\ncourt did not explain its justification for Ross’s term of confinement. “For a procedural\n\nsentencing error to be harmless, the government must prove that the error did not have a\n\nsubstantial and injurious effect or influence on the result.” Lynn, 592 F.3d at 585\n\n 8\n\f(internal citation and quotation marks omitted). This Court cannot look at the district\n\ncourt’s comments and determine that the explicit consideration of Ross’s various\n\nmitigating arguments would not have affected the ultimate term of confinement imposed.\n\nFor instance, the district court mentioned that Ross lacked remorse when discussing its\n\nrationale for Ross’s term of confinement. But the record contains significant evidence of\n\nRoss’s mental health challenges as they affect his ability to show remorse. Given this\n\nrecord evidence, Ross’s demeanor arguably reflects mental health disorders and not a\n\ncallousness or denial of responsibility. The district court could have conceivably given\n\nRoss a different sentence if it had considered his non-frivolous mitigation arguments.\n\nThe district court had an obligation to specifically address Ross’s non-frivolous\n\narguments. It did not do so here. As noted at oral argument, even the Government\n\nnoticed that the district court did not provide a sufficient explanation and asked for\n\nclarification. Nonetheless, the district court cannot meet its responsibility through\n\nbroadly referring to the § 3553(a) factors in lieu of addressing the parties’ non-frivolous\n\narguments.\n\n\n\n V.\n\n The requirement that the district court adequately explain Ross’s term of\n\nconfinement similarly applies to the special conditions of his supervised release. United\n\nStates v. Armel, 585 F.3d 182, 186 (4th Cir. 2009). Ross did not challenge the special\n\nconditions of supervised release before the district court and concedes that this Court\n\n\n\n 9\n\fshould apply a plain-error standard of review. 2 United States v. Wesley, 81 F.3d 482, 484\n\n(4th Cir. 1996) (explaining that we reverse on plain error if the district court erred, the\n\nerror was plain, and the error affected the defendant’s substantial rights). Plain errors\n\nexist “if the settled law of the Supreme Court or this circuit establishes that an error has\n\noccurred.” United States v. Ramirez-Castillo, 748 F.3d 205, 215 (4th Cir. 2014).\n\n In imposing the conditions of supervised release, the district court at the\n\nsentencing hearing said, “I will place you on supervised release for life subject to the\n\ngeneral conditions and special conditions set forth in the recommended conditions of\n\nsupervision.” J.A. 63. The district court did not explain why Ross was given any of the\n\nspecial conditions for life. This lack of explanation contravenes the law of this circuit\n\nand constitutes plain error. Armel, 585 F.3d at 186. This error is not harmless. It is the\n\nsettled law of this circuit that Ross has a right to know why he faces special conditions\n\nthat will forever modify the course of his life, and the district court’s silence violated his\n\nrights. Id. This Court cannot look at the district court’s comments and ascertain its\n\nrationale for imposing very restrictive special conditions for the duration of Ross’s life.\n\n\n\n\n 2\n The parties briefed the special conditions of supervised release argument only\nunder the plain-error standard. Recent circuit precedent suggests, however, that the abuse\nof discretion standard should now apply because Ross challenged the term of\nconfinement and thus preserved his challenge to the special conditions imposed as part of\nhis supervised release. United States v. Ketter, 908 F.3d 61, 66 (4th Cir. 2018) (adopting\na unitary approach to sentencing under which the term of confinement and term of\nsupervised release constitute the same sentence for purposes of appellate review). Ross is\nentitled to relief under either standard.\n\n\n 10\n\fIt is procedurally unreasonable to impose special conditions for the remainder of Ross’s\n\nlife without providing an explanation or rationale for their justification. 3\n\n\n\n\n VI.\n\n In conclusion, given that the district court failed to address Ross’s non-frivolous\n\nmitigation arguments and to properly explain its rationale for his term of confinement and\n\nhis special conditions, we vacate his sentence and remand so that the district court may\n\nprovide a sufficient explanation for the significant deprivation of liberty Ross faces as a\n\nresult of his criminal conduct. This Court makes no assessment regarding the fairness or\n\npropriety of Ross’s term of confinement or special conditions of supervised release.\n\n\n\n VACATED AND REMANDED\n\n\n\n\n 3\n Given that this Court is vacating Ross’s sentence regarding both the term of\nconfinement and special conditions of supervised release, this Court need not address\nRoss’s remaining arguments regarding the propriety of his special conditions.\n\n 11\n[END_CASE]", "role": "user" } ]
4,581,301
MINNIELAND PRIVATE DAY SCHOOL, INC., a Virginia Corporation, Plaintiff - Appellee, v. APPLIED UNDERWRITERS CAPTIVE RISK ASSURANCE COMPANY, INC., Defendant - Appellant.
Minnieland Private Day Sch., Inc. v. Applied Underwriters Captive Risk Assurance Co.
2019-01-14
17-2385
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Motz, Wynn", "parties": "", "opinions": [{"author": "Affirmed by published opinion. Chief Judge Gregory wrote the opinion, in which Judge", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2385\n\n\nMINNIELAND PRIVATE DAY SCHOOL, INC., a Virginia corporation,\n\n Plaintiff - Appellee,\n\n v.\n\nAPPLIED UNDERWRITERS CAPTIVE RISK ASSURANCE COMPANY, INC.,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Anthony John Trenga, District Judge. (1:15-cv-01695-AJT-IDD)\n\n\nArgued: October 30, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, MOTZ, and WYNN, Circuit Judges.\n\n\nAffirmed by published opinion. Chief Judge Gregory wrote the opinion, in which Judge\nMotz and Judge Wynn joined.\n\n\nARGUED: Daniel William Olivas, LEWIS, THOMASON, KING, KRIEG &\nWALDROP, P.C., Nashville, Tennessee, for Appellant. James Scott Krein, KREIN\nLAW FRIM, Prince William, Virginia, for Appellee. ON BRIEF: R. Dale Bay,\nRyan N. Clark, LEWIS, THOMASON, KING, KRIEG & WALDROP, P.C., Nashville,\nTennessee, for Appellant.\n\fGREGORY, Chief Judge:\n\n Appellant Applied Underwriters Captive Risk Assurance Company, Inc.\n\n(“AUCRA”) comes to us for the second time in this case, appealing the district court’s\n\ndetermination that a Reinsurance Participation Agreement (“RPA”) executed by it and\n\nAppellee Minnieland Private Day School is an insurance contract under Virginia law.\n\nThe RPA, executed in connection with Minnieland’s purchase of workers’ compensation\n\ninsurance, contains an arbitration clause. In the district court, AUCRA moved to compel\n\narbitration in accordance with the RPA’s terms. In opposing arbitration, Minnieland\n\nasserted that the RPA is an insurance contract for purposes of Virginia Code § 38.2–312,\n\nwhich renders void arbitration clauses contained in insurance contracts. The district court\n\ndenied AUCRA’s motion to compel arbitration, finding that AUCRA was judicially\n\nestopped from arguing that the RPA is not an insurance contract. We reversed that\n\ndetermination, concluding that AUCRA was not estopped from making its argument, and\n\nremanded to allow the parties to brief fully the issue of whether the RPA is an insurance\n\ncontract for purposes of Virginia Code § 38.2–312. On remand, the district court held\n\nthat the RPA is indeed an insurance contract and that the RPA’s arbitration clause is void\n\nas a matter of law. AUCRA now appeals that determination.\n\n For the reasons set forth below, we conclude that the RPA is an insurance contract\n\nfor purposes of Virginia Code § 38.2–312. We therefore affirm.\n\n\n\n\n 2\n\f I.\n\n A.\n\n This case involves a workers’ compensation insurance program that Minnieland\n\npurchased from AUCRA and its affiliated entities. Under Virginia law, workers’\n\ncompensation insurance is “insurance against the legal liability of any employer for the\n\ndeath or disablement of, or injury to, his or its employee whether imposed by common\n\nlaw or by statute, or assumed by contract.” Va. Code § 38.2–119. Workers’\n\ncompensation insurance coverage is required of “[e]very employer subject to” Virginia’s\n\nworkers’ compensation statute. Va. Code § 65.2–800(A); Redifer v. Chester, 720 S.E.2d\n\n66, 67–68 (Va. 2012).\n\n In general, workers’ compensation insurance is typically provided in one of two\n\ntypes of policies: a guaranteed cost policy or a retrospective rating plan. Under a\n\nguaranteed cost policy, the premiums are fixed and usually do not change over the term\n\nof the policy. Steven Plitt, Daniel Maldonado, Joshua D. Rogers, & Jordan R. Plitt, 2\n\nCouch on Insurance § 69:10 (3d ed. 1995). In many states, these plans are the only plans\n\nlawfully available to small and mid-sized employers. Retrospective rating plans, on the\n\nother hand, usually require an advance premium deposit with the insurer and then provide\n\nthat the insurer, at some specified time, will compute the actual premium based on the\n\ninsured’s actual loss experience or total payroll during a set period of time. Id. § 69:16;\n\nsee Va. Code § 38.2–1901 (defining “retrospective rating plan” as “a rating plan that\n\nadjusts the premium for the insurance to which it applies on the basis of losses incurred\n\nduring the period covered by that insurance”). The insured is then either issued a refund\n\n 3\n\fif the actual premium is lower than the premium deposit paid or required to pay the\n\ndifference if the actual premium exceeds the deposited amount.\n\n At issue in this appeal is Applied Underwriters, Inc.’s EquityComp program, an\n\ninnovative program of workers’ compensation insurance that offers small and mid-sized\n\nemployers the benefits of both a guaranteed cost policy and a retrospective rating plan in\n\none insurance program. The EquityComp program provides employers with guaranteed\n\ncost workers’ compensation insurance at the same time that they enjoy the benefits—and\n\nare subject to the risks—of a retrospective rating plan. See J.A. 404 (explaining that this\n\nRPA allows small and mid-sized employers to “in effect, have a retrospective rating plan\n\n. . . even though, in fact, the insured has Guaranteed Cost insurance coverage with the\n\ninsurance carrier”). 1 The program is so novel that it has been patented.\n\n Under the program, various insurance companies affiliated with Applied\n\nUnderwriters, Inc. have entered into a reinsurance pooling agreement. The pooled\n\ncompanies provide workers’ compensation insurance coverage to employers and also\n\nmutually reinsure each other’s insurance business. A layer of reinsurance is also\n\nprovided by AUCRA, a wholly owned subsidiary of Applied Underwriters, Inc. AUCRA\n\nin turn enters into RPAs with EquityComp customers, under the terms of which each\n\ncustomer pays into a segregated “cell” or account that is then used to fund AUCRA’s\n\nliabilities. In essence, EquityComp customers participate in underwriting the risk of their\n\nown workers’ compensation insurance policies.\n\n 1\n Citations to the “J.A.” refer to the Joint Appendix filed by the parties in this\nappeal.\n\n 4\n\f In theory, an EquityComp customer can save costs on its workers’ compensation\n\ninsurance through a refund of monies deposited into its segregated cell if its workers’\n\ncompensation insurance claims are kept low during the term of the RPA. As detailed\n\nbelow, however, Minnieland was unable to reap this benefit.\n\n B.\n\n Minnieland provides education and childcare services in Virginia and is subject to\n\nthe workers’ compensation laws and requirements of the state. Va. Code § 65.2–800(A).\n\n On January 14, 2013, Minnieland bought into the EquityComp program.\n\nMinnieland executed a Request to Bind Coverages and Services (“Binder”), by which\n\nMinnieland “request[ed] that Applied Underwriters, Inc. through its affiliates and/or\n\nsubsidiaries . . . cause to be issued to [Minnieland] one or more workers’ compensation\n\ninsurance policies . . . subject to [Minnieland] executing the . . . [RPA].” J.A. 40. At the\n\nsame time, Minnieland executed an RPA. The RPA had a term of three years and\n\nprovided that one or more “Issuing Insurers”—all of which were entities affiliated with\n\nApplied Underwriters, Inc.—would issue workers’ compensation insurance policies to\n\nMinnieland. The RPA also established that Minnieland would share in the profits and\n\nlosses associated with its policies through its “segregated protected cell.” Applied Risk\n\nServices, Inc. (“ARS”), another subsidiary of Applied Underwriters, Inc., was designated\n\nas the billing agent for both AUCRA and the Issuing Insurers. Schedule 1 of the RPA\n\nsets forth various formulae for calculating premiums and losses under the RPA and\n\ninsurance policies.\n\n\n\n 5\n\f The day after Minnieland executed the EquityComp documents, the RPA went\n\ninto effect, as did the first of what would become three consecutive one-year Virginia\n\nworkers’ compensation insurance policies, the last of which was to expire on January 15,\n\n2016. The first policy listed the estimated annual premium as $589,163. The second and\n\nthird policies listed the estimated annual premiums as $642,333 and $706,160,\n\nrespectively. The policies were produced by ARS and insured by Continental Indemnity\n\nCompany (“CNI”), another affiliate of Applied Underwriters, Inc.\n\n According to the complaint, at no time was AUCRA licensed to sell insurance in\n\nVirginia, and the RPA has not been approved by the Virginia Workers’ Compensation\n\nCommission.\n\n For the first 33 of the 36 months during which the RPA was active, AUCRA\n\ncharged, and Minnieland paid, an average of $58,810 per month in premiums. In\n\nNovember 2015, however, the premium charged to Minnieland increased drastically to\n\n$471,213, a 1167% increase from the October 2015 premium and a 801% increase over\n\nthe first 33 months’ average. Despite Minnieland’s requests, AUCRA refused to disclose\n\nthe basis on which it assessed the November 2015 premium. Minnieland nonetheless\n\npaid the November premium.\n\n AUCRA billed Minnieland a similarly high premium of $414,604 for December\n\n2015. AUCRA once again refused to disclose the basis for the increased premium, and\n\nMinnieland did not pay the December premium.\n\n\n\n\n 6\n\f On December 16, 2015, AUCRA 2 faxed Minnieland notice that it was terminating\n\nMinnieland’s EquityComp program, including the RPA and insurance coverage, effective\n\nDecember 27, 2015. The reason provided for the termination of coverage was “Non-\n\nPayment of Premium; Client has an outstanding balance.”\n\n C.\n\n On December 24, 2015, Minnieland filed suit against AUCRA in the Eastern\n\nDistrict of Virginia. Minnieland alleged that AUCRA is not authorized or licensed to act\n\nas an insurance company under Virginia law; that the RPA is an “insurance contract” and\n\nnot a “reinsurance” agreement; and that AUCRA misrepresented the EquityComp\n\nprogram, and the RPA specifically, to circumvent Virginia insurance and workers’\n\ncompensation laws. Minnieland sought (1) a declaration that the RPA constitutes an\n\ninsurance contract and is void because of AUCRA’s failure to comply with Virginia law;\n\n(2) a declaration of the amount, if any, that Minnieland owes under the RPA; and (3) a\n\ndeclaration that the premiums, deposits, and charges assessed to Minnieland by AUCRA\n\nwere excessive. Minnieland also sought damages for fraud and breach of contract.\n\n On January 18, 2016, AUCRA filed a demand for arbitration with the American\n\nArbitration Association, invoking the RPA’s arbitration provisions. That demand sought\n\npayment from Minnieland of a total of $342,358 that AUCRA claimed it was owed under\n\nthe RPA and EquityComp program.\n\n 2\n The complaint alleges that AUCRA sent the notice. The letter is printed on\n“Applied Underwriters” letterhead and does not specify if the sender is AUCRA or\nApplied Underwriters, Inc. J.A. 52. The document attached to the letter indicates that it\nwas “produced by” ARS. J.A. 53.\n\n 7\n\f AUCRA also moved the district court to dismiss Minnieland’s complaint and\n\ncompel arbitration under the RPA’s arbitration clause. In opposing the motion to compel\n\narbitration, Minnieland argued that the RPA is an insurance contract. As such,\n\nMinnieland argued, the arbitration clause is void because it is prohibited by Virginia\n\nCode § 38.2–312.\n\n On March 17, 2016, the district court granted in part and denied in part AUCRA’s\n\nmotion. The district court determined that the RPA’s arbitration clause calls for\n\narbitration of the threshold question of whether the RPA is an insurance contract such\n\nthat Virginia’s insurance statute, which reverse-preempts the Federal Arbitration Act\n\n(“FAA”), applies. Accordingly, the court ordered the parties to submit that question to\n\nthe arbitrator.\n\n A week later, the district court granted Minnieland’s motion for reconsideration of\n\nthe court’s March 17, 2016 order. The district court again concluded that the threshold\n\nissue of arbitrability was for the arbitrator to determine. The district court nonetheless\n\nstayed its March 17 order and requested supplemental briefing on Minnieland’s\n\ncontention that AUCRA was judicially estopped from arguing that the RPA is not an\n\ninsurance contract.\n\n The parties briefed the judicial estoppel issue, and the district court heard\n\nargument on AUCRA’s motion to compel arbitration. The district court denied the\n\nmotion to compel, concluding that the four elements of judicial estoppel were met such\n\nthat AUCRA was estopped from arguing that the RPA is not an insurance contract. See\n\n\n\n 8\n\fLowery v. Stovall, 92 F.3d 219, 223–24 (4th Cir. 1996) (discussing the elements of\n\njudicial estoppel).\n\n AUCRA appealed that order. On appeal, we affirmed in part and reversed in part.\n\nMinnieland Private Day Sch., Inc. v. Applied Underwriters Captive Risk Assurance Co.,\n\nInc., 867 F.3d 449 (4th Cir. 2017), cert. denied, 138 S. Ct. 926 (2018). We concluded\n\nthat Virginia Code § 38.2–312 “renders invalid delegation provisions in putative\n\ninsurance contracts governed by Virginia law, at least to the extent such delegation\n\nprovisions endow an arbitrator, as opposed to a court, with exclusive authority to\n\ndetermine whether the contract at issue constitutes an ‘insurance contract’ for purposes of\n\nVirginia law.” Id. at 456. Therefore, we affirmed the district court’s denial of the motion\n\nto compel arbitration. Id. at 457. We also concluded that AUCRA was not judicially\n\nestopped from arguing that the RPA is not an insurance contract under Virginia law. Id.\n\nat 458–59. Because the parties had not had the opportunity to brief fully the issue of\n\nwhether the RPA is an insurance contract under Virginia law, we remanded the matter to\n\nthe district court. Id. at 459.\n\n On remand, the district court ruled in an oral opinion that the RPA is an insurance\n\ncontract. As the district court explained:\n\n Under this arrangement, Minnieland and AUCRA\n entered into a contract as a result of which Minnieland\n received workmen’s compensation coverage through an\n insurance policy in exchange for premiums that were paid for\n that coverage.\n\n AUCRA’s position rests entirely on parsing this\n transaction to the point of being completely disassociated\n with the realities of the overall transaction. So the Court\n\n 9\n\f concludes that it’s an insurance contract for the purposes of\n 38.2–312 as the Fourth Circuit has already determined. 3\n\nJ.A. 1073–74. Accordingly, the district court denied the motion to compel arbitration,\n\nfinding that “any arbitration provisions pertaining to any disputes under [the RPA] are\n\nvoid.” J.A. 1074.\n\n AUCRA appeals the district court’s denial of its motion to compel arbitration.\n\n\n\n II.\n\n We review de novo a district court’s order denying a motion to compel arbitration\n\nunder the FAA. Noohi v. Toll Bros., Inc., 708 F.3d 599, 605 (4th Cir. 2013). “At the\n\nsame time, we give due regard to the federal policy favoring arbitration and resolve ‘any\n\ndoubts concerning the scope of arbitrable issues . . . in favor of arbitration.’” Hill v.\n\nPeoplesoft USA, Inc., 412 F.3d 540, 543 (4th Cir. 2005) (citation omitted).\n\n In determining whether a dispute is arbitrable, we “apply ordinary state-law\n\nprinciples that govern the formation of contracts and the federal substantive law of\n\narbitrability.” Id. (internal citations and quotation marks omitted). Because this matter\n\n\n\n 3\n In our prior opinion, we did not determine that the RPA is in fact an insurance\ncontract. Rather, we affirmed the district court’s denial of AUCRA’s motion to compel\narbitration on the grounds that Virginia Code § 38.2–312 “renders void delegation\nprovisions in putative insurance contracts—at least to the extent such provisions\nauthorize an arbitrator to resolve whether the contract at issue constitutes an ‘insurance\ncontract.’” Minnieland, 867 F.3d at 457. Recognizing that the parties had not had the\nopportunity to brief and argue the issue of whether the RPA is an insurance contract\nunder Virginia law, we remanded this matter to the district court for consideration of that\nissue.\n\n 10\n\finvolves the question of whether the RPA is an insurance contract for purposes of the\n\nVirginia Code, we look to Virginia law, which the parties agree applies in this case. 4\n\n\n\n III.\n\n A.\n\n We begin by addressing AUCRA’s argument that the district court ignored this\n\nCourt’s “narrow” mandate and improperly considered the entire program of workers’\n\ncompensation insurance—rather than only the RPA—in determining that the RPA is an\n\ninsurance contract under Virginia law. Opening Br. 23–26. AUCRA points out that the\n\ncomplaint names only AUCRA as a defendant, not CNI (the policy issuer), Applied\n\nUnderwriters, Inc. (the parent company), or Applied Risk Services (the billing agent). Id.\n\nat 25 (citing J.A. 1). AUCRA also relies on the fact that Minnieland’s claims are\n\npredicated on the RPA alone. Id. (citing J.A. 11–22). In light of this narrow focus of\n\nMinnieland’s suit and our “narrow mandate” to determine whether “the RPA is an\n\ninsurance contract under Virginia law,” AUCRA asserts that the district court should\n\n 4\n We note that the RPA provides that it “shall be exclusively governed by and\nconstrued in accordance with the laws of Nebraska and any matter concerning this\nAgreement that is not subject to [arbitration] shall be resolved exclusively by the courts\nof Nebraska without reference to its conflict of laws.” J.A. 34 (§ 16). The question of\nwhether the contract itself is an insurance contract for purposes of Virginia Code § 38.2–\n312, however, is a matter of Virginia law, and both parties brief the issue on appeal under\nVirginia law. See, e.g., Opening Br. 28–34; Resp. Br. 13, 18–22. Because the parties\nagree that Virginia law applies, we need not inquire further into the choice-of-law\nquestions, and Virginia law controls the analysis. Cosey v. Prudential Ins. Co. of Am.,\n735 F.3d 161, 169 n.7 (4th Cir. 2013) (citing Am. Fuel Corp. v. Utah Energy Dev. Co.,\n122 F.3d 130, 134 (2d Cir. 1997)). We also note that AUCRA has not invoked the\nRPA’s forum selection clause.\n\n 11\n\fhave considered only the RPA, not the workers’ compensation insurance transaction as a\n\nwhole. Id. at 25–26.\n\n Nothing in our prior opinion suggests that we intended to preclude any evaluation\n\nof whether the RPA’s terms are the complete terms of the parties’ agreement or whether\n\nthe RPA’s terms should be construed as integrated with the terms of the other\n\nEquityComp agreements. Our mandate was indeed limited to the RPA. However, on the\n\nprevious appeal, we were concerned only with the RPA because the RPA contains the\n\narbitration provision at issue. Because we remanded for consideration of whether the\n\nRPA is an “insurance contract” under Virginia law, the district court was faced with the\n\ninitial question of whether the RPA is in fact a standalone contract or is simply one part\n\nof an integrated contract. See Hitachi Credit Am. Corp. v. Signet Bank, 166 F.3d 614,\n\n626 (4th Cir. 1999) (“A contract may be contained in several instruments, and they may\n\nbe read together as one instrument [i]f made at the same time and in relation to the same\n\nsubject matter.” (alteration in original) (internal citations and quotation marks omitted)).\n\nOnly after the court made that threshold determination could it then determine the nature\n\nof the contract. Therefore, the district court did not ignore our previous mandate by\n\nlooking at the EquityComp program as a whole.\n\n B.\n\n 1.\n\n Having concluded that the district court did not violate our prior mandate, we turn\n\nto the issue at the heart of this appeal: whether the RPA is an insurance contract for\n\npurposes of Virginia Code § 38.2–312. Under Virginia law, “[w]here two papers are\n\n 12\n\fexecuted at the same time or contemporaneously between the same parties, in reference\n\nto the same subject matter, they must be regarded as parts of one transaction, and receive\n\nthe same construction as if their several provisions were in one and the same instrument.”\n\nCountryside Orthopaedics, P.C. v. Peyton, 541 S.E.2d 279, 284 (Va. 2001) (alteration in\n\noriginal) (citations omitted). “To construe two instruments as one, reference in one\n\ninstrument to the other need not be explicit; ‘it is sufficient if it is fairly traceable.’”\n\nHitachi Credit, 166 F.3d at 626 (quoting Tex. Co. v. Northup, 153 S.E. 659, 662 (Va.\n\n1930)). While “a court is not required to construe two documents as one contract just\n\nbecause they are executed at the same time and concern the same subject matter[,] [t]he\n\ncourt must give effect to the intent of the parties.” Id. (citing Am. Realty Tr. v. Chase\n\nManhattan Bank, N.A., 281 S.E.2d 825, 831 (Va. 1981)).\n\n The Virginia courts have yet to address whether a contract similar to the RPA,\n\nexecuted during an insurance transaction, comprises part of the insurance contract. The\n\nVirginia Supreme Court, however, has taken a rather expansive view of what constitutes\n\na single integrated contract. In Daugherty v. Diment, the Virginia Supreme Court made\n\nclear that, “[w]here a business transaction is based upon more than one document\n\nexecuted by the parties, the documents will be construed together to determine the intent\n\nof the parties; each document will be employed to ascertain the meaning intended to be\n\nexpressed by the others.” 385 S.E.2d 572, 574 (Va. 1989) (citing Am. Realty Tr., 281\n\nS.E.2d at 830).\n\n The Virginia Supreme Court has since applied Daugherty’s rule regularly to\n\ntransactions involving multiple written agreements. In Musselman v. Glass Works, LLC,\n\n 13\n\ffor example, the Virginia Supreme Court held that an asset purchase agreement and a\n\nnon-competition agreement executed at the same time “formed an integrated business\n\ntransaction.” 533 S.E.2d 919, 921 (Va. 2000). The purchase agreement provided that the\n\npurchase price was payable in various payments, including a deposit, a sum certain at\n\nclosing, a secured promissory note to the sellers, and a total of $60,000 to be paid\n\npursuant to three non-competition agreements. Id. at 920. The Virginia Supreme Court\n\nrejected an argument that the non-competition agreements were separate, personal service\n\ncontracts. Id. at 921. Instead, the court determined that the four contracts formed an\n\nintegrated contract because the sum due under the non-competition agreements was\n\nexplicitly part of the purchase price of the business under the purchase agreement. Id.\n\n The Virginia Supreme Court has also found that agreements not executed by the\n\nsame parties may nonetheless constitute an integrated contract. In Countryside\n\nOrthopaedics, for instance, the court found an integrated contract comprised of four\n\nagreements: two employment agreements executed by Countryside Orthopaedics and\n\ntwo respective physicians, a Stock Purchase Agreement executed by the physicians, and a\n\nStockholders’ Agreement executed by all three parties. 541 S.E.2d at 284. The court\n\nheld that these documents constituted a single transaction despite the fact that each of the\n\ncontracts was not signed by all three parties because “all the parties knew about the\n\nagreements and executed them at the same time as part of a single transaction to\n\naccomplish an agreed purpose.” Id. The court was also persuaded by the fact that “some\n\nof the agreements contain[ed] explicit references to the other agreements.” Id. at 285.\n\n\n\n 14\n\f Also instructive is Parr v. Alderwoods Grp., Inc., 604 S.E.2d 431 (Va. 2004). The\n\ntransaction at issue in that case involved four agreements: an asset purchase agreement, a\n\nnon-competition agreement, a lease, and a management agreement. Id. at 432. In\n\nreviewing the agreements, the Virginia Supreme Court rejected the argument that the\n\nmanagement agreement was “a contract separate and apart from” the asset purchase\n\nagreement. Id. at 435. The court found that the management agreement and asset\n\npurchase agreement should be construed “as a single integrated contract” because they\n\ncross-referenced each other and contained certain provisions written in identical\n\nlanguage. Id. The court explained that those references “reflect[ed] the parties’\n\nknowledge and understanding of the interrelationship between the contracts and\n\nprovide[d] strong support for the proposition that the parties intended that the documents\n\nconstitute a single transaction.” Id. The court further reasoned that, although the four\n\ncontracts “identified discrete acts required of the parties,” the contracts all shared the\n\nsame result and purpose. Id. Also relevant was the fact that the provisions of the\n\nmanagement agreement “could not be performed” without the acquisition of the business\n\nthrough the purchase agreement and the lease of the property. Id. As the court stated,\n\n“[t]he absence of any one of the agreements would frustrate the purpose of the\n\ntransaction.” Id.\n\n Moreover, it is well-established that insurance may be sold and purchased by way\n\nof more than the pages of the policy itself. See 2 Couch on Insurance § 21:21\n\n(“Endorsements, riders, marginal references, and other similar writings are a part of the\n\ncontract of insurance and are to be read and construed with the policy proper.”). Counsel\n\n 15\n\ffor AUCRA conceded during oral argument that an insurance contract is broader than an\n\ninsurance policy and that a policy endorsement, for example, would be considered part of\n\nthe insurance contract.\n\n 2.\n\n With these principles in mind, we examine the relationship between the Binder,\n\nRPA, and the CNI workers’ compensation insurance policies. Both the RPA and the first\n\nCNI policy went into effect on the same day, one day after Minnieland executed the\n\nBinder and RPA. Issuance of the policy was expressly conditioned on Minnieland’s prior\n\nexecution of the RPA. Therefore, as contemplated by the parties, execution of the RPA\n\nwould temporally precede issuance of the insurance policy. See Seabulk Offshore, Ltd. v.\n\nAm. Home Assurance Co., 377 F.3d 408, 419 (4th Cir. 2004) (“Under Virginia law, a\n\ncontract is made when the last act to complete it is performed, and in the context of an\n\ninsurance policy, the last act is the delivery of the policy to the insured.” (citation\n\nomitted)). And the entire program went into effect at the same time, on January 15, 2013.\n\n The subject matter of the documents is also the same: the workers’ compensation\n\ninsurance issued to Minnieland, including the manner in which the payroll, premiums,\n\nand losses in connection with the insurance coverage would be calculated and how the\n\nrisk would be distributed. The Binder represented Minnieland’s acceptance of the\n\nEquityComp program, and through the Binder, Minnieland requested that Applied\n\nUnderwriters, Inc. “through its affiliates and/or subsidiaries . . . cause to be issued”\n\nworkers’ compensation insurance coverage to Minnieland. J.A. 40. The RPA also\n\ndiscusses the insurance coverage; it notes that workers’ compensation insurance coverage\n\n 16\n\f“will be provided” to Minnieland by “one or more of the Issuing Insurers,” defined as\n\naffiliates of Applied Underwriters, Inc. J.A. 30–31. The RPA establishes Minnieland’s\n\nparticipation in a segregated cell to be funded in part by “a portion of the premium and\n\nlosses” under the RPA. J.A. 30. The premium and losses are calculated pursuant to the\n\nRPA’s Schedule 1. Id. And Schedule 1 “applies . . . to all payroll, premium, and losses\n\noccurring under the [CNI workers’ compensation insurance] Policies.” J.A. 36.\n\n The documents also internally reference each other and set forth each other’s\n\nterms. The Binder formally requests the issuance of workers’ compensation insurance\n\ncoverage subject to Minnieland’s execution of the RPA. The RPA references the\n\nworkers’ compensation policies explicitly, and Minnieland was required to execute the\n\nRPA before those policies would issue. Schedule 1 of the RPA establishes the manner in\n\nwhich Minnieland’s fees for the EquityComp program as a whole would be calculated.\n\nThat is, Schedule 1 applies to all premiums and losses under the actual insurance policies.\n\nIn fact, the billing statements for Minnieland’s participation in the EquityComp program\n\nshow that Minnieland was charged a single “pay-in amount” each month for the\n\n“Workers’ Compensation Program.” J.A. 45, 47, 49 (emphasis added). The RPA also\n\nwaives Minnieland’s right to choose deductibles for its workers’ compensation insurance\n\npolicies, and the Binder acknowledges that waiver. See J.A. 31 (§ 5), 40.\n\n The RPA and insurance policies are linked in other ways as well. The RPA\n\nprovides that its early cancellation terms apply if any one of the insurance policies is\n\ncancelled prior to the end of the RPA’s three-year term. J.A. 31 (§ 4). The RPA also\n\nprovides that Minnieland and AUCRA’s obligations under the RPA survive the active\n\n 17\n\fterm of the RPA “and shall be extinguished only when [AUCRA] no longer has any\n\npotential or actual liability to the Issuing Insurers with respect to the [workers’\n\ncompensation insurance] Policies.” J.A. 31 (§ 7). The RPA additionally provides that, in\n\nthe event Minnieland defaults under the RPA “or under any other agreement with any\n\naffiliates of [AUCRA] (Affiliated Agreements),” AUCRA “may take all reasonable steps\n\nto protect its and its affiliates’ interests.” J.A. 31 (§ 9). The RPA goes on to state that\n\n“[t]he parties hereto shall have the right . . . to offset or recoup any balances due from one\n\nto the other under [the RPA] or any Affiliated Agreements.” Id. Those Affiliated\n\nAgreements would include the insurance policies issued by CNI, an AUCRA affiliate.\n\nThe RPA also sets forth the terms that apply if CNI were required to provide workers’\n\ncompensation insurance coverage outside of the active term of the RPA. J.A. 31 (§ 4).\n\n These explicit internal references, interrelated terms, and shared subject matter are\n\nstrong evidence that the parties intended these documents to be part of one integrated\n\ntransaction. See Countryside Orthopaedics, 541 S.E.2d at 285; Musselman, 533 S.E.2d at\n\n921.\n\n To be sure, the documents were not executed by the same parties. The Binder was\n\nsigned by Minnieland as an acceptance of the EquityComp program proposal apparently\n\ndrafted by ARS, a subsidiary of Applied Underwriters, Inc., to whom the EquityComp\n\ntrademark is registered. See J.A. 23 (defining “we” as Applied Risk Services). The RPA\n\nwas executed between Minnieland and AUCRA, another subsidiary of Applied\n\nUnderwriters, Inc. J.A. 30. And the insurance policies were produced by Applied Risk\n\n\n\n 18\n\fServices, Inc., another subsidiary of Applied Underwriters, Inc., with CNI, yet another\n\nApplied Underwriters, Inc. subsidiary, as the insuring entity. J.A. 42–44.\n\n Nonetheless, the EquityComp program is promoted and sold as “[o]ne unified\n\nprogram for your business needs across all states” provided by Applied Underwriters,\n\nInc., “a premier financial services group of companies with leading experience in the\n\ncasualty insurance, reinsurance and business services disciplines.” J.A. 24–25 (emphases\n\nadded). The EquityComp program is marketed as being “effected through a separate\n\nreinsurance transaction issued in conjunction with a fully insured, guaranteed cost,\n\nworkers’ compensation policy.” J.A. 24. In fact, the Producer’s Quote Transmittal sent\n\nto the agent who brokered this deal for Minnieland expressly stated that the program\n\nproposed to Minnieland was “valid only if presented prior to expiration, in its original\n\nform, and in its entirety without modification.” J.A. 29 (emphasis added). And the\n\nBinder makes clear that insurance coverage was conditioned on execution of the RPA.\n\nTherefore, absent execution of the RPA, the insurance coverage would not have been\n\noffered as proposed. See Nat’l Convention Servs., LLC v. Applied Underwriters Captive\n\nRisk Assurance Co., Inc., 239 F. Supp. 3d 761, 786 (S.D.N.Y. 2017) (examining the\n\nworkers’ compensation insurance program offered by AUCRA and its affiliates and\n\nnoting that the RPA “would serve no purpose” without the approved guaranteed cost\n\ninsurance policies and that “it is plausible that the two can be treated as one\n\nundertaking”); see also Parr, 604 S.E.2d at 435 (finding integrated contract where one\n\ncontract’s terms could not be performed in the absence of other contracts).\n\n\n\n 19\n\f Additionally, the RPA contemplates that its terms will apply to AUCRA’s\n\naffiliates. The RPA provides that “[n]othing in this Agreement, expressed or implied, is\n\nintended to confer upon any party, other than the parties hereto and their affiliates,\n\nsuccessors and assigns, any rights, remedies, obligations or liabilities under or by reason\n\nof this Agreement, except as expressly provided herein.” J.A. 35 (§ 19) (emphasis\n\nadded). The RPA also provides that “[a]ll existing obligations from each party to the\n\nother or to third parties shall remain in force as of the expiration of the Active Term until\n\nthis Agreement is terminated.” J.A. 31 (§ 4) (emphasis added). These provisions further\n\nsuggest that Minnieland and AUCRA intended the RPA to be part of an integrated\n\ntransaction with AUCRA’s affiliates. See Countryside Orthopaedics, 541 S.E.2d at 284.\n\n During oral argument, counsel for AUCRA highlighted that, despite the RPA’s\n\nSchedule 1, the RPA does not charge “premiums”; it merely explains what happens to the\n\npremiums that are paid under the policies. This, however, does not render the RPA a\n\nstandalone contract. Instead, it lends support to Minnieland’s argument that the RPA and\n\nthe CNI policies must be read as one integrated contract. The policies set forth an\n\nestimated annual premium that is not subject to the RPA’s Schedule 1 calculations. J.A.\n\n42–44. The policies also contain a Short Rate Cancelation Policyholder Notice that\n\nexplains how the final premium will be calculated if the policies are cancelled by\n\nMinnieland. J.A. 761–63. The RPA’s Schedule 1, on the other hand, purports to\n\nestablish the total fee to be paid by Minnieland for the EquityComp program as well as\n\nany early cancellation fee that may be due. J.A. 36–37.\n\n\n\n 20\n\f Schedule 1’s calculations, however, incorporate the provisions of the CNI policies.\n\nSchedule 1 states that it “applies as of the Effective Date [January 15, 2013] to all\n\npayroll, premium, and losses occurring under the Policies.” J.A. 36. Schedule 1 explains\n\nthat “[a]n amount equal to the premium earned under the Policies in excess of the Loss\n\nPick Containment Amount multiplied by the applicable Exposure Group Adjustment\n\nFactor multiplied by the Allocation Factor listed in Table B, will be allocated to the\n\nParticipant’s cell.” J.A. 36 (§ 2). Thus, although Minnieland was billed one monthly fee\n\nfor the EquityComp program, the premium amount set forth in the policies was part of\n\nthat monthly fee and was included in calculating the total amount that would be due\n\nunder the program as a whole. Absent the CNI policies, the calculations in Schedule 1—\n\nincluding the amount to be allocated to Minnieland’s segregated cell—would be\n\nimpossible to make.\n\n The early cancellation provision of the RPA also depends on the cancellation\n\nprovisions of the CNI policies. The RPA’s early cancellation provision applies if either\n\nMinnieland cancels the RPA or if any of the insurance policies are “cancelled or non-\n\nrenewed prior to the end of the Active Term” of the RPA. J.A. 31 (§ 4). That\n\ncancellation policy, described in Schedule 1, states that certain of the factors used to\n\ncalculate premiums and losses will be increased in the event of early cancellation and that\n\nMinnieland will be required to pay, among other things, “any remaining premium,\n\nincluding short rate penalties, due under the Policies.” J.A. 37 (§ 6) (emphasis added).\n\nThose “short rate penalties” are the early termination provisions of the insurance policies.\n\nSee, e.g., J.A. 761 (“Short Rate Cancelation Policyholder Notice”). And the short rate\n\n 21\n\fpenalties apply when the policy is cancelled by Minnieland. Id. Therefore, when the\n\nshort rate cancellation provisions of the policies apply, they are another integer of the\n\nformula used under the RPA to calculate the total amount due under the EquityComp\n\nprogram. In the absence of the CNI policy terms, the RPA’s Schedule 1 calculations and\n\nearly cancellation provisions make no sense. See Musselman, 533 S.E.2d at 921.\n\n We do not ignore that Minnieland chose to sue only AUCRA and to base its\n\nclaims only on the RPA. However, because the RPA was but one component of an\n\nintegrated insurance sale, we must examine the related documents and the relationship\n\nbetween the affiliated entities. Daugherty, 385 S.E.2d at 574. In the absence of the CNI\n\npolicies, the RPA would have been pointless and nonsensical; and in the absence of the\n\nRPA, there would have been no insurance coverage. Nothing in the record suggests that\n\nMinnieland could have simply paid the premiums listed in the CNI policies, without\n\npaying the amounts set forth in the RPA’s Schedule 1, and maintained its workers’\n\ncompensation coverage; the RPA expressly provides for the opposite result. Because the\n\nEquityComp program was marketed and sold as a package deal, Minnieland’s failure to\n\nexecute the RPA would have frustrated the purpose of the transaction. See Parr, 604\n\nS.E.2d at 435.\n\n In sum, the documents, considered together, show that the purpose of the Binder,\n\nRPA, and CNI policies was one: to provide Minnieland with workers’ compensation\n\ninsurance coverage while allowing Minnieland the opportunity to keep its insurance costs\n\nlow by sharing in the underwriting risk. We need not determine specifically whether the\n\nRPA constitutes a policy endorsement or rider. Regardless of the label that may attach,\n\n 22\n\fthe RPA and insurance policies constitute an integrated transaction and must be read as\n\none contract.\n\n C.\n\n Having determined the scope of the contract at issue, we must now decide whether\n\nthe integrated contract is a contract of insurance under Virginia Code § 38.2–312. The\n\nVirginia Code does not define “insurance contract.” It does define “insurance,” however,\n\nas “the business of transferring risk by contract wherein a person, for a consideration,\n\nundertakes (i) to indemnify another person, (ii) to pay or provide a specified or\n\nascertainable amount of money, or (iii) to provide a benefit or service upon the\n\noccurrence of a determinable risk contingency.” Va. Code § 38.2–100. The Code also\n\nlists the required terms of “[e]ach insurance policy or contract”:\n\n 1. The names of the parties to the contract;\n\n 2. The subject of the insurance;\n\n 3. The risks insured against;\n\n 4. The time the insurance takes effect and, except in the case\n of group insurance, title insurance, and insurance written\n under perpetual policies, the period during which the\n insurance is to continue;\n\n 5. A statement of the premium, except in the case of group\n insurance and title insurance; and\n\n 6. The conditions pertaining to the insurance.\n\nVa. Code § 38.2–305. 5\n\n\n 5\n Minnieland cites to Virginia common law for the essential terms of an insurance\ncontract. See Resp. Br. 20–21; Grp. Hospitalization Med. Serv., Inc. v. Smith, 372 S.E.2d\n(Continued)\n 23\n\f Neither party argues that the terms of the CNI policies themselves fail to meet the\n\nstatutory requirements for insurance contracts. In fact, AUCRA acknowledges that the\n\nCNI policies meet Virginia’s requirements. Opening Br. 7 n.3. Construing the CNI\n\npolicy terms as integrated with those of the RPA, as though the terms of each were\n\nwritten in a single document, Countryside Orthopaedics, 541 S.E.2d at 284, it becomes\n\nclear that the contract at issue is an “insurance contract” under Virginia law.\n\nAccordingly, the district court properly determined that the RPA is an insurance contract\n\nfor the purposes of Virginia Code § 38.2–312.\n\n D.\n\n We note, as Minnieland does, that we are not the first to determine that the\n\nprogram marketed by Applied Underwriters, Inc. is insurance. In fact, several state\n\ninsurance commissioners have determined that the EquityComp program and its sister\n\nprogram, SolutionOne, are not only subject to insurance regulations, but also violate\n\nthose regulations. For example, the Vermont Department of Financial Regulation has\n\nbarred Applied Underwriters, Inc. from selling the RPA in conjunction with guaranteed\n\n\n159, 160 (Va. 1988) (listing “essential terms” of insurance contract as: “(1) the subject\nmatter to be insured; (2) the risk insured against; (3) the commencement and period of the\nrisk undertaken by the insurer; (4) the amount of insurance; and (5) the premium and time\nat which it is to be paid” (citation omitted)). AUCRA argues that, since the addition of\nthe definition of “insurance” to the Virginia Code in 2001, this common law definition is\nno longer controlling. Opening Br. 32–33. The Virginia Supreme Court has not applied\nthe common-law definition in connection with the statutory definition of “insurance.”\nHowever, the common-law elements are essentially the same as the statutory\nrequirements for every insurance policy. Therefore, an evaluation of the contract at issue\nunder either the statutory factors or the common-law definition should yield the same\nresult.\n\n 24\n\fcost insurance policies in Vermont after concluding that the RPA “de facto operated as a\n\nretrospective rating plan, replacing [CNI’s] guaranteed-cost workers’ compensation\n\ninsurance policy with an unfiled, unapproved retrospective rating plan.” J.A. 233.\n\nSimilarly, the Wisconsin Office of the Commissioner of Insurance entered into an\n\nagreement with ARS and CNI that they will “cease and desist from marketing, binding,\n\nissuing and renewing SolutionOne and EquityComp policies and any similarly designed\n\npolicies and programs that involve side agreements that affect the terms of the workers’\n\ncompensation policy, including but not limited to reinsurance agreements.” J.A. 375.\n\nThe California Insurance Commissioner likewise found that the EquityComp program\n\nand its RPA violate the California Insurance Code. See Decision and Order, In the\n\nMatter of the Appeal of Shasta Linen Supply, Inc., No. AHB-WCA-14-31 (Dep’t of Ins.,\n\nState of Cal. June 20, 2016), http://www.insurance.ca.gov/0250-insurers/0500-legal-\n\ninfo/0600-decision-ruling/0100-precedential/upload/ShastaLinenSupplyInc.pdf.\n\n Other courts faced with the RPA and similar related documents have also\n\nsuggested that the program marketed by Applied Underwriters, including the RPA, is\n\ninsurance. See, e.g., Nat’l Convention Servs., 239 F. Supp. 3d at 786 (observing that the\n\nRPA and guaranteed cost policies “plausibly serve the common purpose of providing\n\nworkers’ compensation insurance at rates that are affected by loss experience”); Nielsen\n\nContracting, Inc. v. Applied Underwriters, Inc., 22 Cal. App. 5th 1096, 1116–17 (Cal. Ct.\n\nApp. 2018) (determining that the RPA’s provisions were meant to replace those of the\n\ninsurance policies and that the Applied Underwriters affiliated entities were “so\n\nenmeshed” and “intertwined” that the RPA and insurance policies should be considered\n\n 25\n\ftogether); Citizens of Humanity, LLC v. Applied Underwriters Captive Risk Assurance\n\nCo., Inc., 909 N.W.2d 614, 632 (Neb.) (stating that “the RPA has the hallmarks of a\n\nretrospective rating plan” and concluding that the RPA is an “agreement concerning or\n\nrelating to an insurance policy” under Nebraska law), cert. denied, 139 S. Ct. 274 (2018).\n\n While each of these other jurisdictions has evaluated the RPA under different laws\n\nand for different purposes, the general consensus has consistently been that the RPA is\n\nsubject to insurance regulations. We join that consensus in holding that the RPA at issue\n\nhere is an insurance contract under Virginia law. Because arbitration provisions in\n\ninsurance contracts are void under Virginia law, Va. Code § 38.2–312, AUCRA must\n\nface Minnieland’s claims in court.\n\n\n\n IV.\n\n For these reasons, we affirm the judgment of the district court.\n\n\n\n AFFIRMED.\n\n\n\n\n 26", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358554/", "author_raw": "Affirmed by published opinion. Chief Judge Gregory wrote the opinion, in which Judge"}]}
GREGORY
MOTZ
WYNN
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4581301/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: MINNIELAND PRIVATE DAY SCHOOL, INC., a Virginia Corporation, Plaintiff - Appellee, v. APPLIED UNDERWRITERS CAPTIVE RISK ASSURANCE COMPANY, INC., Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-14\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-2385\n\n\nMINNIELAND PRIVATE DAY SCHOOL, INC., a Virginia corporation,\n\n Plaintiff - Appellee,\n\n v.\n\nAPPLIED UNDERWRITERS CAPTIVE RISK ASSURANCE COMPANY, INC.,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Anthony John Trenga, District Judge. (1:15-cv-01695-AJT-IDD)\n\n\nArgued: October 30, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, MOTZ, and WYNN, Circuit Judges.\n\n\nAffirmed by published opinion. Chief Judge Gregory wrote the opinion, in which Judge\nMotz and Judge Wynn joined.\n\n\nARGUED: Daniel William Olivas, LEWIS, THOMASON, KING, KRIEG &\nWALDROP, P.C., Nashville, Tennessee, for Appellant. James Scott Krein, KREIN\nLAW FRIM, Prince William, Virginia, for Appellee. ON BRIEF: R. Dale Bay,\nRyan N. Clark, LEWIS, THOMASON, KING, KRIEG & WALDROP, P.C., Nashville,\nTennessee, for Appellant.\n\fGREGORY, Chief Judge:\n\n Appellant Applied Underwriters Captive Risk Assurance Company, Inc.\n\n(“AUCRA”) comes to us for the second time in this case, appealing the district court’s\n\ndetermination that a Reinsurance Participation Agreement (“RPA”) executed by it and\n\nAppellee Minnieland Private Day School is an insurance contract under Virginia law.\n\nThe RPA, executed in connection with Minnieland’s purchase of workers’ compensation\n\ninsurance, contains an arbitration clause. In the district court, AUCRA moved to compel\n\narbitration in accordance with the RPA’s terms. In opposing arbitration, Minnieland\n\nasserted that the RPA is an insurance contract for purposes of Virginia Code § 38.2–312,\n\nwhich renders void arbitration clauses contained in insurance contracts. The district court\n\ndenied AUCRA’s motion to compel arbitration, finding that AUCRA was judicially\n\nestopped from arguing that the RPA is not an insurance contract. We reversed that\n\ndetermination, concluding that AUCRA was not estopped from making its argument, and\n\nremanded to allow the parties to brief fully the issue of whether the RPA is an insurance\n\ncontract for purposes of Virginia Code § 38.2–312. On remand, the district court held\n\nthat the RPA is indeed an insurance contract and that the RPA’s arbitration clause is void\n\nas a matter of law. AUCRA now appeals that determination.\n\n For the reasons set forth below, we conclude that the RPA is an insurance contract\n\nfor purposes of Virginia Code § 38.2–312. We therefore affirm.\n\n\n\n\n 2\n\f I.\n\n A.\n\n This case involves a workers’ compensation insurance program that Minnieland\n\npurchased from AUCRA and its affiliated entities. Under Virginia law, workers’\n\ncompensation insurance is “insurance against the legal liability of any employer for the\n\ndeath or disablement of, or injury to, his or its employee whether imposed by common\n\nlaw or by statute, or assumed by contract.” Va. Code § 38.2–119. Workers’\n\ncompensation insurance coverage is required of “[e]very employer subject to” Virginia’s\n\nworkers’ compensation statute. Va. Code § 65.2–800(A); Redifer v. Chester, 720 S.E.2d\n\n66, 67–68 (Va. 2012).\n\n In general, workers’ compensation insurance is typically provided in one of two\n\ntypes of policies: a guaranteed cost policy or a retrospective rating plan. Under a\n\nguaranteed cost policy, the premiums are fixed and usually do not change over the term\n\nof the policy. Steven Plitt, Daniel Maldonado, Joshua D. Rogers, & Jordan R. Plitt, 2\n\nCouch on Insurance § 69:10 (3d ed. 1995). In many states, these plans are the only plans\n\nlawfully available to small and mid-sized employers. Retrospective rating plans, on the\n\nother hand, usually require an advance premium deposit with the insurer and then provide\n\nthat the insurer, at some specified time, will compute the actual premium based on the\n\ninsured’s actual loss experience or total payroll during a set period of time. Id. § 69:16;\n\nsee Va. Code § 38.2–1901 (defining “retrospective rating plan” as “a rating plan that\n\nadjusts the premium for the insurance to which it applies on the basis of losses incurred\n\nduring the period covered by that insurance”). The insured is then either issued a refund\n\n 3\n\fif the actual premium is lower than the premium deposit paid or required to pay the\n\ndifference if the actual premium exceeds the deposited amount.\n\n At issue in this appeal is Applied Underwriters, Inc.’s EquityComp program, an\n\ninnovative program of workers’ compensation insurance that offers small and mid-sized\n\nemployers the benefits of both a guaranteed cost policy and a retrospective rating plan in\n\none insurance program. The EquityComp program provides employers with guaranteed\n\ncost workers’ compensation insurance at the same time that they enjoy the benefits—and\n\nare subject to the risks—of a retrospective rating plan. See J.A. 404 (explaining that this\n\nRPA allows small and mid-sized employers to “in effect, have a retrospective rating plan\n\n. . . even though, in fact, the insured has Guaranteed Cost insurance coverage with the\n\ninsurance carrier”). 1 The program is so novel that it has been patented.\n\n Under the program, various insurance companies affiliated with Applied\n\nUnderwriters, Inc. have entered into a reinsurance pooling agreement. The pooled\n\ncompanies provide workers’ compensation insurance coverage to employers and also\n\nmutually reinsure each other’s insurance business. A layer of reinsurance is also\n\nprovided by AUCRA, a wholly owned subsidiary of Applied Underwriters, Inc. AUCRA\n\nin turn enters into RPAs with EquityComp customers, under the terms of which each\n\ncustomer pays into a segregated “cell” or account that is then used to fund AUCRA’s\n\nliabilities. In essence, EquityComp customers participate in underwriting the risk of their\n\nown workers’ compensation insurance policies.\n\n 1\n Citations to the “J.A.” refer to the Joint Appendix filed by the parties in this\nappeal.\n\n 4\n\f In theory, an EquityComp customer can save costs on its workers’ compensation\n\ninsurance through a refund of monies deposited into its segregated cell if its workers’\n\ncompensation insurance claims are kept low during the term of the RPA. As detailed\n\nbelow, however, Minnieland was unable to reap this benefit.\n\n B.\n\n Minnieland provides education and childcare services in Virginia and is subject to\n\nthe workers’ compensation laws and requirements of the state. Va. Code § 65.2–800(A).\n\n On January 14, 2013, Minnieland bought into the EquityComp program.\n\nMinnieland executed a Request to Bind Coverages and Services (“Binder”), by which\n\nMinnieland “request[ed] that Applied Underwriters, Inc. through its affiliates and/or\n\nsubsidiaries . . . cause to be issued to [Minnieland] one or more workers’ compensation\n\ninsurance policies . . . subject to [Minnieland] executing the . . . [RPA].” J.A. 40. At the\n\nsame time, Minnieland executed an RPA. The RPA had a term of three years and\n\nprovided that one or more “Issuing Insurers”—all of which were entities affiliated with\n\nApplied Underwriters, Inc.—would issue workers’ compensation insurance policies to\n\nMinnieland. The RPA also established that Minnieland would share in the profits and\n\nlosses associated with its policies through its “segregated protected cell.” Applied Risk\n\nServices, Inc. (“ARS”), another subsidiary of Applied Underwriters, Inc., was designated\n\nas the billing agent for both AUCRA and the Issuing Insurers. Schedule 1 of the RPA\n\nsets forth various formulae for calculating premiums and losses under the RPA and\n\ninsurance policies.\n\n\n\n 5\n\f The day after Minnieland executed the EquityComp documents, the RPA went\n\ninto effect, as did the first of what would become three consecutive one-year Virginia\n\nworkers’ compensation insurance policies, the last of which was to expire on January 15,\n\n2016. The first policy listed the estimated annual premium as $589,163. The second and\n\nthird policies listed the estimated annual premiums as $642,333 and $706,160,\n\nrespectively. The policies were produced by ARS and insured by Continental Indemnity\n\nCompany (“CNI”), another affiliate of Applied Underwriters, Inc.\n\n According to the complaint, at no time was AUCRA licensed to sell insurance in\n\nVirginia, and the RPA has not been approved by the Virginia Workers’ Compensation\n\nCommission.\n\n For the first 33 of the 36 months during which the RPA was active, AUCRA\n\ncharged, and Minnieland paid, an average of $58,810 per month in premiums. In\n\nNovember 2015, however, the premium charged to Minnieland increased drastically to\n\n$471,213, a 1167% increase from the October 2015 premium and a 801% increase over\n\nthe first 33 months’ average. Despite Minnieland’s requests, AUCRA refused to disclose\n\nthe basis on which it assessed the November 2015 premium. Minnieland nonetheless\n\npaid the November premium.\n\n AUCRA billed Minnieland a similarly high premium of $414,604 for December\n\n2015. AUCRA once again refused to disclose the basis for the increased premium, and\n\nMinnieland did not pay the December premium.\n\n\n\n\n 6\n\f On December 16, 2015, AUCRA 2 faxed Minnieland notice that it was terminating\n\nMinnieland’s EquityComp program, including the RPA and insurance coverage, effective\n\nDecember 27, 2015. The reason provided for the termination of coverage was “Non-\n\nPayment of Premium; Client has an outstanding balance.”\n\n C.\n\n On December 24, 2015, Minnieland filed suit against AUCRA in the Eastern\n\nDistrict of Virginia. Minnieland alleged that AUCRA is not authorized or licensed to act\n\nas an insurance company under Virginia law; that the RPA is an “insurance contract” and\n\nnot a “reinsurance” agreement; and that AUCRA misrepresented the EquityComp\n\nprogram, and the RPA specifically, to circumvent Virginia insurance and workers’\n\ncompensation laws. Minnieland sought (1) a declaration that the RPA constitutes an\n\ninsurance contract and is void because of AUCRA’s failure to comply with Virginia law;\n\n(2) a declaration of the amount, if any, that Minnieland owes under the RPA; and (3) a\n\ndeclaration that the premiums, deposits, and charges assessed to Minnieland by AUCRA\n\nwere excessive. Minnieland also sought damages for fraud and breach of contract.\n\n On January 18, 2016, AUCRA filed a demand for arbitration with the American\n\nArbitration Association, invoking the RPA’s arbitration provisions. That demand sought\n\npayment from Minnieland of a total of $342,358 that AUCRA claimed it was owed under\n\nthe RPA and EquityComp program.\n\n 2\n The complaint alleges that AUCRA sent the notice. The letter is printed on\n“Applied Underwriters” letterhead and does not specify if the sender is AUCRA or\nApplied Underwriters, Inc. J.A. 52. The document attached to the letter indicates that it\nwas “produced by” ARS. J.A. 53.\n\n 7\n\f AUCRA also moved the district court to dismiss Minnieland’s complaint and\n\ncompel arbitration under the RPA’s arbitration clause. In opposing the motion to compel\n\narbitration, Minnieland argued that the RPA is an insurance contract. As such,\n\nMinnieland argued, the arbitration clause is void because it is prohibited by Virginia\n\nCode § 38.2–312.\n\n On March 17, 2016, the district court granted in part and denied in part AUCRA’s\n\nmotion. The district court determined that the RPA’s arbitration clause calls for\n\narbitration of the threshold question of whether the RPA is an insurance contract such\n\nthat Virginia’s insurance statute, which reverse-preempts the Federal Arbitration Act\n\n(“FAA”), applies. Accordingly, the court ordered the parties to submit that question to\n\nthe arbitrator.\n\n A week later, the district court granted Minnieland’s motion for reconsideration of\n\nthe court’s March 17, 2016 order. The district court again concluded that the threshold\n\nissue of arbitrability was for the arbitrator to determine. The district court nonetheless\n\nstayed its March 17 order and requested supplemental briefing on Minnieland’s\n\ncontention that AUCRA was judicially estopped from arguing that the RPA is not an\n\ninsurance contract.\n\n The parties briefed the judicial estoppel issue, and the district court heard\n\nargument on AUCRA’s motion to compel arbitration. The district court denied the\n\nmotion to compel, concluding that the four elements of judicial estoppel were met such\n\nthat AUCRA was estopped from arguing that the RPA is not an insurance contract. See\n\n\n\n 8\n\fLowery v. Stovall, 92 F.3d 219, 223–24 (4th Cir. 1996) (discussing the elements of\n\njudicial estoppel).\n\n AUCRA appealed that order. On appeal, we affirmed in part and reversed in part.\n\nMinnieland Private Day Sch., Inc. v. Applied Underwriters Captive Risk Assurance Co.,\n\nInc., 867 F.3d 449 (4th Cir. 2017), cert. denied, 138 S. Ct. 926 (2018). We concluded\n\nthat Virginia Code § 38.2–312 “renders invalid delegation provisions in putative\n\ninsurance contracts governed by Virginia law, at least to the extent such delegation\n\nprovisions endow an arbitrator, as opposed to a court, with exclusive authority to\n\ndetermine whether the contract at issue constitutes an ‘insurance contract’ for purposes of\n\nVirginia law.” Id. at 456. Therefore, we affirmed the district court’s denial of the motion\n\nto compel arbitration. Id. at 457. We also concluded that AUCRA was not judicially\n\nestopped from arguing that the RPA is not an insurance contract under Virginia law. Id.\n\nat 458–59. Because the parties had not had the opportunity to brief fully the issue of\n\nwhether the RPA is an insurance contract under Virginia law, we remanded the matter to\n\nthe district court. Id. at 459.\n\n On remand, the district court ruled in an oral opinion that the RPA is an insurance\n\ncontract. As the district court explained:\n\n Under this arrangement, Minnieland and AUCRA\n entered into a contract as a result of which Minnieland\n received workmen’s compensation coverage through an\n insurance policy in exchange for premiums that were paid for\n that coverage.\n\n AUCRA’s position rests entirely on parsing this\n transaction to the point of being completely disassociated\n with the realities of the overall transaction. So the Court\n\n 9\n\f concludes that it’s an insurance contract for the purposes of\n 38.2–312 as the Fourth Circuit has already determined. 3\n\nJ.A. 1073–74. Accordingly, the district court denied the motion to compel arbitration,\n\nfinding that “any arbitration provisions pertaining to any disputes under [the RPA] are\n\nvoid.” J.A. 1074.\n\n AUCRA appeals the district court’s denial of its motion to compel arbitration.\n\n\n\n II.\n\n We review de novo a district court’s order denying a motion to compel arbitration\n\nunder the FAA. Noohi v. Toll Bros., Inc., 708 F.3d 599, 605 (4th Cir. 2013). “At the\n\nsame time, we give due regard to the federal policy favoring arbitration and resolve ‘any\n\ndoubts concerning the scope of arbitrable issues . . . in favor of arbitration.’” Hill v.\n\nPeoplesoft USA, Inc., 412 F.3d 540, 543 (4th Cir. 2005) (citation omitted).\n\n In determining whether a dispute is arbitrable, we “apply ordinary state-law\n\nprinciples that govern the formation of contracts and the federal substantive law of\n\narbitrability.” Id. (internal citations and quotation marks omitted). Because this matter\n\n\n\n 3\n In our prior opinion, we did not determine that the RPA is in fact an insurance\ncontract. Rather, we affirmed the district court’s denial of AUCRA’s motion to compel\narbitration on the grounds that Virginia Code § 38.2–312 “renders void delegation\nprovisions in putative insurance contracts—at least to the extent such provisions\nauthorize an arbitrator to resolve whether the contract at issue constitutes an ‘insurance\ncontract.’” Minnieland, 867 F.3d at 457. Recognizing that the parties had not had the\nopportunity to brief and argue the issue of whether the RPA is an insurance contract\nunder Virginia law, we remanded this matter to the district court for consideration of that\nissue.\n\n 10\n\finvolves the question of whether the RPA is an insurance contract for purposes of the\n\nVirginia Code, we look to Virginia law, which the parties agree applies in this case. 4\n\n\n\n III.\n\n A.\n\n We begin by addressing AUCRA’s argument that the district court ignored this\n\nCourt’s “narrow” mandate and improperly considered the entire program of workers’\n\ncompensation insurance—rather than only the RPA—in determining that the RPA is an\n\ninsurance contract under Virginia law. Opening Br. 23–26. AUCRA points out that the\n\ncomplaint names only AUCRA as a defendant, not CNI (the policy issuer), Applied\n\nUnderwriters, Inc. (the parent company), or Applied Risk Services (the billing agent). Id.\n\nat 25 (citing J.A. 1). AUCRA also relies on the fact that Minnieland’s claims are\n\npredicated on the RPA alone. Id. (citing J.A. 11–22). In light of this narrow focus of\n\nMinnieland’s suit and our “narrow mandate” to determine whether “the RPA is an\n\ninsurance contract under Virginia law,” AUCRA asserts that the district court should\n\n 4\n We note that the RPA provides that it “shall be exclusively governed by and\nconstrued in accordance with the laws of Nebraska and any matter concerning this\nAgreement that is not subject to [arbitration] shall be resolved exclusively by the courts\nof Nebraska without reference to its conflict of laws.” J.A. 34 (§ 16). The question of\nwhether the contract itself is an insurance contract for purposes of Virginia Code § 38.2–\n312, however, is a matter of Virginia law, and both parties brief the issue on appeal under\nVirginia law. See, e.g., Opening Br. 28–34; Resp. Br. 13, 18–22. Because the parties\nagree that Virginia law applies, we need not inquire further into the choice-of-law\nquestions, and Virginia law controls the analysis. Cosey v. Prudential Ins. Co. of Am.,\n735 F.3d 161, 169 n.7 (4th Cir. 2013) (citing Am. Fuel Corp. v. Utah Energy Dev. Co.,\n122 F.3d 130, 134 (2d Cir. 1997)). We also note that AUCRA has not invoked the\nRPA’s forum selection clause.\n\n 11\n\fhave considered only the RPA, not the workers’ compensation insurance transaction as a\n\nwhole. Id. at 25–26.\n\n Nothing in our prior opinion suggests that we intended to preclude any evaluation\n\nof whether the RPA’s terms are the complete terms of the parties’ agreement or whether\n\nthe RPA’s terms should be construed as integrated with the terms of the other\n\nEquityComp agreements. Our mandate was indeed limited to the RPA. However, on the\n\nprevious appeal, we were concerned only with the RPA because the RPA contains the\n\narbitration provision at issue. Because we remanded for consideration of whether the\n\nRPA is an “insurance contract” under Virginia law, the district court was faced with the\n\ninitial question of whether the RPA is in fact a standalone contract or is simply one part\n\nof an integrated contract. See Hitachi Credit Am. Corp. v. Signet Bank, 166 F.3d 614,\n\n626 (4th Cir. 1999) (“A contract may be contained in several instruments, and they may\n\nbe read together as one instrument [i]f made at the same time and in relation to the same\n\nsubject matter.” (alteration in original) (internal citations and quotation marks omitted)).\n\nOnly after the court made that threshold determination could it then determine the nature\n\nof the contract. Therefore, the district court did not ignore our previous mandate by\n\nlooking at the EquityComp program as a whole.\n\n B.\n\n 1.\n\n Having concluded that the district court did not violate our prior mandate, we turn\n\nto the issue at the heart of this appeal: whether the RPA is an insurance contract for\n\npurposes of Virginia Code § 38.2–312. Under Virginia law, “[w]here two papers are\n\n 12\n\fexecuted at the same time or contemporaneously between the same parties, in reference\n\nto the same subject matter, they must be regarded as parts of one transaction, and receive\n\nthe same construction as if their several provisions were in one and the same instrument.”\n\nCountryside Orthopaedics, P.C. v. Peyton, 541 S.E.2d 279, 284 (Va. 2001) (alteration in\n\noriginal) (citations omitted). “To construe two instruments as one, reference in one\n\ninstrument to the other need not be explicit; ‘it is sufficient if it is fairly traceable.’”\n\nHitachi Credit, 166 F.3d at 626 (quoting Tex. Co. v. Northup, 153 S.E. 659, 662 (Va.\n\n1930)). While “a court is not required to construe two documents as one contract just\n\nbecause they are executed at the same time and concern the same subject matter[,] [t]he\n\ncourt must give effect to the intent of the parties.” Id. (citing Am. Realty Tr. v. Chase\n\nManhattan Bank, N.A., 281 S.E.2d 825, 831 (Va. 1981)).\n\n The Virginia courts have yet to address whether a contract similar to the RPA,\n\nexecuted during an insurance transaction, comprises part of the insurance contract. The\n\nVirginia Supreme Court, however, has taken a rather expansive view of what constitutes\n\na single integrated contract. In Daugherty v. Diment, the Virginia Supreme Court made\n\nclear that, “[w]here a business transaction is based upon more than one document\n\nexecuted by the parties, the documents will be construed together to determine the intent\n\nof the parties; each document will be employed to ascertain the meaning intended to be\n\nexpressed by the others.” 385 S.E.2d 572, 574 (Va. 1989) (citing Am. Realty Tr., 281\n\nS.E.2d at 830).\n\n The Virginia Supreme Court has since applied Daugherty’s rule regularly to\n\ntransactions involving multiple written agreements. In Musselman v. Glass Works, LLC,\n\n 13\n\ffor example, the Virginia Supreme Court held that an asset purchase agreement and a\n\nnon-competition agreement executed at the same time “formed an integrated business\n\ntransaction.” 533 S.E.2d 919, 921 (Va. 2000). The purchase agreement provided that the\n\npurchase price was payable in various payments, including a deposit, a sum certain at\n\nclosing, a secured promissory note to the sellers, and a total of $60,000 to be paid\n\npursuant to three non-competition agreements. Id. at 920. The Virginia Supreme Court\n\nrejected an argument that the non-competition agreements were separate, personal service\n\ncontracts. Id. at 921. Instead, the court determined that the four contracts formed an\n\nintegrated contract because the sum due under the non-competition agreements was\n\nexplicitly part of the purchase price of the business under the purchase agreement. Id.\n\n The Virginia Supreme Court has also found that agreements not executed by the\n\nsame parties may nonetheless constitute an integrated contract. In Countryside\n\nOrthopaedics, for instance, the court found an integrated contract comprised of four\n\nagreements: two employment agreements executed by Countryside Orthopaedics and\n\ntwo respective physicians, a Stock Purchase Agreement executed by the physicians, and a\n\nStockholders’ Agreement executed by all three parties. 541 S.E.2d at 284. The court\n\nheld that these documents constituted a single transaction despite the fact that each of the\n\ncontracts was not signed by all three parties because “all the parties knew about the\n\nagreements and executed them at the same time as part of a single transaction to\n\naccomplish an agreed purpose.” Id. The court was also persuaded by the fact that “some\n\nof the agreements contain[ed] explicit references to the other agreements.” Id. at 285.\n\n\n\n 14\n\f Also instructive is Parr v. Alderwoods Grp., Inc., 604 S.E.2d 431 (Va. 2004). The\n\ntransaction at issue in that case involved four agreements: an asset purchase agreement, a\n\nnon-competition agreement, a lease, and a management agreement. Id. at 432. In\n\nreviewing the agreements, the Virginia Supreme Court rejected the argument that the\n\nmanagement agreement was “a contract separate and apart from” the asset purchase\n\nagreement. Id. at 435. The court found that the management agreement and asset\n\npurchase agreement should be construed “as a single integrated contract” because they\n\ncross-referenced each other and contained certain provisions written in identical\n\nlanguage. Id. The court explained that those references “reflect[ed] the parties’\n\nknowledge and understanding of the interrelationship between the contracts and\n\nprovide[d] strong support for the proposition that the parties intended that the documents\n\nconstitute a single transaction.” Id. The court further reasoned that, although the four\n\ncontracts “identified discrete acts required of the parties,” the contracts all shared the\n\nsame result and purpose. Id. Also relevant was the fact that the provisions of the\n\nmanagement agreement “could not be performed” without the acquisition of the business\n\nthrough the purchase agreement and the lease of the property. Id. As the court stated,\n\n“[t]he absence of any one of the agreements would frustrate the purpose of the\n\ntransaction.” Id.\n\n Moreover, it is well-established that insurance may be sold and purchased by way\n\nof more than the pages of the policy itself. See 2 Couch on Insurance § 21:21\n\n(“Endorsements, riders, marginal references, and other similar writings are a part of the\n\ncontract of insurance and are to be read and construed with the policy proper.”). Counsel\n\n 15\n\ffor AUCRA conceded during oral argument that an insurance contract is broader than an\n\ninsurance policy and that a policy endorsement, for example, would be considered part of\n\nthe insurance contract.\n\n 2.\n\n With these principles in mind, we examine the relationship between the Binder,\n\nRPA, and the CNI workers’ compensation insurance policies. Both the RPA and the first\n\nCNI policy went into effect on the same day, one day after Minnieland executed the\n\nBinder and RPA. Issuance of the policy was expressly conditioned on Minnieland’s prior\n\nexecution of the RPA. Therefore, as contemplated by the parties, execution of the RPA\n\nwould temporally precede issuance of the insurance policy. See Seabulk Offshore, Ltd. v.\n\nAm. Home Assurance Co., 377 F.3d 408, 419 (4th Cir. 2004) (“Under Virginia law, a\n\ncontract is made when the last act to complete it is performed, and in the context of an\n\ninsurance policy, the last act is the delivery of the policy to the insured.” (citation\n\nomitted)). And the entire program went into effect at the same time, on January 15, 2013.\n\n The subject matter of the documents is also the same: the workers’ compensation\n\ninsurance issued to Minnieland, including the manner in which the payroll, premiums,\n\nand losses in connection with the insurance coverage would be calculated and how the\n\nrisk would be distributed. The Binder represented Minnieland’s acceptance of the\n\nEquityComp program, and through the Binder, Minnieland requested that Applied\n\nUnderwriters, Inc. “through its affiliates and/or subsidiaries . . . cause to be issued”\n\nworkers’ compensation insurance coverage to Minnieland. J.A. 40. The RPA also\n\ndiscusses the insurance coverage; it notes that workers’ compensation insurance coverage\n\n 16\n\f“will be provided” to Minnieland by “one or more of the Issuing Insurers,” defined as\n\naffiliates of Applied Underwriters, Inc. J.A. 30–31. The RPA establishes Minnieland’s\n\nparticipation in a segregated cell to be funded in part by “a portion of the premium and\n\nlosses” under the RPA. J.A. 30. The premium and losses are calculated pursuant to the\n\nRPA’s Schedule 1. Id. And Schedule 1 “applies . . . to all payroll, premium, and losses\n\noccurring under the [CNI workers’ compensation insurance] Policies.” J.A. 36.\n\n The documents also internally reference each other and set forth each other’s\n\nterms. The Binder formally requests the issuance of workers’ compensation insurance\n\ncoverage subject to Minnieland’s execution of the RPA. The RPA references the\n\nworkers’ compensation policies explicitly, and Minnieland was required to execute the\n\nRPA before those policies would issue. Schedule 1 of the RPA establishes the manner in\n\nwhich Minnieland’s fees for the EquityComp program as a whole would be calculated.\n\nThat is, Schedule 1 applies to all premiums and losses under the actual insurance policies.\n\nIn fact, the billing statements for Minnieland’s participation in the EquityComp program\n\nshow that Minnieland was charged a single “pay-in amount” each month for the\n\n“Workers’ Compensation Program.” J.A. 45, 47, 49 (emphasis added). The RPA also\n\nwaives Minnieland’s right to choose deductibles for its workers’ compensation insurance\n\npolicies, and the Binder acknowledges that waiver. See J.A. 31 (§ 5), 40.\n\n The RPA and insurance policies are linked in other ways as well. The RPA\n\nprovides that its early cancellation terms apply if any one of the insurance policies is\n\ncancelled prior to the end of the RPA’s three-year term. J.A. 31 (§ 4). The RPA also\n\nprovides that Minnieland and AUCRA’s obligations under the RPA survive the active\n\n 17\n\fterm of the RPA “and shall be extinguished only when [AUCRA] no longer has any\n\npotential or actual liability to the Issuing Insurers with respect to the [workers’\n\ncompensation insurance] Policies.” J.A. 31 (§ 7). The RPA additionally provides that, in\n\nthe event Minnieland defaults under the RPA “or under any other agreement with any\n\naffiliates of [AUCRA] (Affiliated Agreements),” AUCRA “may take all reasonable steps\n\nto protect its and its affiliates’ interests.” J.A. 31 (§ 9). The RPA goes on to state that\n\n“[t]he parties hereto shall have the right . . . to offset or recoup any balances due from one\n\nto the other under [the RPA] or any Affiliated Agreements.” Id. Those Affiliated\n\nAgreements would include the insurance policies issued by CNI, an AUCRA affiliate.\n\nThe RPA also sets forth the terms that apply if CNI were required to provide workers’\n\ncompensation insurance coverage outside of the active term of the RPA. J.A. 31 (§ 4).\n\n These explicit internal references, interrelated terms, and shared subject matter are\n\nstrong evidence that the parties intended these documents to be part of one integrated\n\ntransaction. See Countryside Orthopaedics, 541 S.E.2d at 285; Musselman, 533 S.E.2d at\n\n921.\n\n To be sure, the documents were not executed by the same parties. The Binder was\n\nsigned by Minnieland as an acceptance of the EquityComp program proposal apparently\n\ndrafted by ARS, a subsidiary of Applied Underwriters, Inc., to whom the EquityComp\n\ntrademark is registered. See J.A. 23 (defining “we” as Applied Risk Services). The RPA\n\nwas executed between Minnieland and AUCRA, another subsidiary of Applied\n\nUnderwriters, Inc. J.A. 30. And the insurance policies were produced by Applied Risk\n\n\n\n 18\n\fServices, Inc., another subsidiary of Applied Underwriters, Inc., with CNI, yet another\n\nApplied Underwriters, Inc. subsidiary, as the insuring entity. J.A. 42–44.\n\n Nonetheless, the EquityComp program is promoted and sold as “[o]ne unified\n\nprogram for your business needs across all states” provided by Applied Underwriters,\n\nInc., “a premier financial services group of companies with leading experience in the\n\ncasualty insurance, reinsurance and business services disciplines.” J.A. 24–25 (emphases\n\nadded). The EquityComp program is marketed as being “effected through a separate\n\nreinsurance transaction issued in conjunction with a fully insured, guaranteed cost,\n\nworkers’ compensation policy.” J.A. 24. In fact, the Producer’s Quote Transmittal sent\n\nto the agent who brokered this deal for Minnieland expressly stated that the program\n\nproposed to Minnieland was “valid only if presented prior to expiration, in its original\n\nform, and in its entirety without modification.” J.A. 29 (emphasis added). And the\n\nBinder makes clear that insurance coverage was conditioned on execution of the RPA.\n\nTherefore, absent execution of the RPA, the insurance coverage would not have been\n\noffered as proposed. See Nat’l Convention Servs., LLC v. Applied Underwriters Captive\n\nRisk Assurance Co., Inc., 239 F. Supp. 3d 761, 786 (S.D.N.Y. 2017) (examining the\n\nworkers’ compensation insurance program offered by AUCRA and its affiliates and\n\nnoting that the RPA “would serve no purpose” without the approved guaranteed cost\n\ninsurance policies and that “it is plausible that the two can be treated as one\n\nundertaking”); see also Parr, 604 S.E.2d at 435 (finding integrated contract where one\n\ncontract’s terms could not be performed in the absence of other contracts).\n\n\n\n 19\n\f Additionally, the RPA contemplates that its terms will apply to AUCRA’s\n\naffiliates. The RPA provides that “[n]othing in this Agreement, expressed or implied, is\n\nintended to confer upon any party, other than the parties hereto and their affiliates,\n\nsuccessors and assigns, any rights, remedies, obligations or liabilities under or by reason\n\nof this Agreement, except as expressly provided herein.” J.A. 35 (§ 19) (emphasis\n\nadded). The RPA also provides that “[a]ll existing obligations from each party to the\n\nother or to third parties shall remain in force as of the expiration of the Active Term until\n\nthis Agreement is terminated.” J.A. 31 (§ 4) (emphasis added). These provisions further\n\nsuggest that Minnieland and AUCRA intended the RPA to be part of an integrated\n\ntransaction with AUCRA’s affiliates. See Countryside Orthopaedics, 541 S.E.2d at 284.\n\n During oral argument, counsel for AUCRA highlighted that, despite the RPA’s\n\nSchedule 1, the RPA does not charge “premiums”; it merely explains what happens to the\n\npremiums that are paid under the policies. This, however, does not render the RPA a\n\nstandalone contract. Instead, it lends support to Minnieland’s argument that the RPA and\n\nthe CNI policies must be read as one integrated contract. The policies set forth an\n\nestimated annual premium that is not subject to the RPA’s Schedule 1 calculations. J.A.\n\n42–44. The policies also contain a Short Rate Cancelation Policyholder Notice that\n\nexplains how the final premium will be calculated if the policies are cancelled by\n\nMinnieland. J.A. 761–63. The RPA’s Schedule 1, on the other hand, purports to\n\nestablish the total fee to be paid by Minnieland for the EquityComp program as well as\n\nany early cancellation fee that may be due. J.A. 36–37.\n\n\n\n 20\n\f Schedule 1’s calculations, however, incorporate the provisions of the CNI policies.\n\nSchedule 1 states that it “applies as of the Effective Date [January 15, 2013] to all\n\npayroll, premium, and losses occurring under the Policies.” J.A. 36. Schedule 1 explains\n\nthat “[a]n amount equal to the premium earned under the Policies in excess of the Loss\n\nPick Containment Amount multiplied by the applicable Exposure Group Adjustment\n\nFactor multiplied by the Allocation Factor listed in Table B, will be allocated to the\n\nParticipant’s cell.” J.A. 36 (§ 2). Thus, although Minnieland was billed one monthly fee\n\nfor the EquityComp program, the premium amount set forth in the policies was part of\n\nthat monthly fee and was included in calculating the total amount that would be due\n\nunder the program as a whole. Absent the CNI policies, the calculations in Schedule 1—\n\nincluding the amount to be allocated to Minnieland’s segregated cell—would be\n\nimpossible to make.\n\n The early cancellation provision of the RPA also depends on the cancellation\n\nprovisions of the CNI policies. The RPA’s early cancellation provision applies if either\n\nMinnieland cancels the RPA or if any of the insurance policies are “cancelled or non-\n\nrenewed prior to the end of the Active Term” of the RPA. J.A. 31 (§ 4). That\n\ncancellation policy, described in Schedule 1, states that certain of the factors used to\n\ncalculate premiums and losses will be increased in the event of early cancellation and that\n\nMinnieland will be required to pay, among other things, “any remaining premium,\n\nincluding short rate penalties, due under the Policies.” J.A. 37 (§ 6) (emphasis added).\n\nThose “short rate penalties” are the early termination provisions of the insurance policies.\n\nSee, e.g., J.A. 761 (“Short Rate Cancelation Policyholder Notice”). And the short rate\n\n 21\n\fpenalties apply when the policy is cancelled by Minnieland. Id. Therefore, when the\n\nshort rate cancellation provisions of the policies apply, they are another integer of the\n\nformula used under the RPA to calculate the total amount due under the EquityComp\n\nprogram. In the absence of the CNI policy terms, the RPA’s Schedule 1 calculations and\n\nearly cancellation provisions make no sense. See Musselman, 533 S.E.2d at 921.\n\n We do not ignore that Minnieland chose to sue only AUCRA and to base its\n\nclaims only on the RPA. However, because the RPA was but one component of an\n\nintegrated insurance sale, we must examine the related documents and the relationship\n\nbetween the affiliated entities. Daugherty, 385 S.E.2d at 574. In the absence of the CNI\n\npolicies, the RPA would have been pointless and nonsensical; and in the absence of the\n\nRPA, there would have been no insurance coverage. Nothing in the record suggests that\n\nMinnieland could have simply paid the premiums listed in the CNI policies, without\n\npaying the amounts set forth in the RPA’s Schedule 1, and maintained its workers’\n\ncompensation coverage; the RPA expressly provides for the opposite result. Because the\n\nEquityComp program was marketed and sold as a package deal, Minnieland’s failure to\n\nexecute the RPA would have frustrated the purpose of the transaction. See Parr, 604\n\nS.E.2d at 435.\n\n In sum, the documents, considered together, show that the purpose of the Binder,\n\nRPA, and CNI policies was one: to provide Minnieland with workers’ compensation\n\ninsurance coverage while allowing Minnieland the opportunity to keep its insurance costs\n\nlow by sharing in the underwriting risk. We need not determine specifically whether the\n\nRPA constitutes a policy endorsement or rider. Regardless of the label that may attach,\n\n 22\n\fthe RPA and insurance policies constitute an integrated transaction and must be read as\n\none contract.\n\n C.\n\n Having determined the scope of the contract at issue, we must now decide whether\n\nthe integrated contract is a contract of insurance under Virginia Code § 38.2–312. The\n\nVirginia Code does not define “insurance contract.” It does define “insurance,” however,\n\nas “the business of transferring risk by contract wherein a person, for a consideration,\n\nundertakes (i) to indemnify another person, (ii) to pay or provide a specified or\n\nascertainable amount of money, or (iii) to provide a benefit or service upon the\n\noccurrence of a determinable risk contingency.” Va. Code § 38.2–100. The Code also\n\nlists the required terms of “[e]ach insurance policy or contract”:\n\n 1. The names of the parties to the contract;\n\n 2. The subject of the insurance;\n\n 3. The risks insured against;\n\n 4. The time the insurance takes effect and, except in the case\n of group insurance, title insurance, and insurance written\n under perpetual policies, the period during which the\n insurance is to continue;\n\n 5. A statement of the premium, except in the case of group\n insurance and title insurance; and\n\n 6. The conditions pertaining to the insurance.\n\nVa. Code § 38.2–305. 5\n\n\n 5\n Minnieland cites to Virginia common law for the essential terms of an insurance\ncontract. See Resp. Br. 20–21; Grp. Hospitalization Med. Serv., Inc. v. Smith, 372 S.E.2d\n(Continued)\n 23\n\f Neither party argues that the terms of the CNI policies themselves fail to meet the\n\nstatutory requirements for insurance contracts. In fact, AUCRA acknowledges that the\n\nCNI policies meet Virginia’s requirements. Opening Br. 7 n.3. Construing the CNI\n\npolicy terms as integrated with those of the RPA, as though the terms of each were\n\nwritten in a single document, Countryside Orthopaedics, 541 S.E.2d at 284, it becomes\n\nclear that the contract at issue is an “insurance contract” under Virginia law.\n\nAccordingly, the district court properly determined that the RPA is an insurance contract\n\nfor the purposes of Virginia Code § 38.2–312.\n\n D.\n\n We note, as Minnieland does, that we are not the first to determine that the\n\nprogram marketed by Applied Underwriters, Inc. is insurance. In fact, several state\n\ninsurance commissioners have determined that the EquityComp program and its sister\n\nprogram, SolutionOne, are not only subject to insurance regulations, but also violate\n\nthose regulations. For example, the Vermont Department of Financial Regulation has\n\nbarred Applied Underwriters, Inc. from selling the RPA in conjunction with guaranteed\n\n\n159, 160 (Va. 1988) (listing “essential terms” of insurance contract as: “(1) the subject\nmatter to be insured; (2) the risk insured against; (3) the commencement and period of the\nrisk undertaken by the insurer; (4) the amount of insurance; and (5) the premium and time\nat which it is to be paid” (citation omitted)). AUCRA argues that, since the addition of\nthe definition of “insurance” to the Virginia Code in 2001, this common law definition is\nno longer controlling. Opening Br. 32–33. The Virginia Supreme Court has not applied\nthe common-law definition in connection with the statutory definition of “insurance.”\nHowever, the common-law elements are essentially the same as the statutory\nrequirements for every insurance policy. Therefore, an evaluation of the contract at issue\nunder either the statutory factors or the common-law definition should yield the same\nresult.\n\n 24\n\fcost insurance policies in Vermont after concluding that the RPA “de facto operated as a\n\nretrospective rating plan, replacing [CNI’s] guaranteed-cost workers’ compensation\n\ninsurance policy with an unfiled, unapproved retrospective rating plan.” J.A. 233.\n\nSimilarly, the Wisconsin Office of the Commissioner of Insurance entered into an\n\nagreement with ARS and CNI that they will “cease and desist from marketing, binding,\n\nissuing and renewing SolutionOne and EquityComp policies and any similarly designed\n\npolicies and programs that involve side agreements that affect the terms of the workers’\n\ncompensation policy, including but not limited to reinsurance agreements.” J.A. 375.\n\nThe California Insurance Commissioner likewise found that the EquityComp program\n\nand its RPA violate the California Insurance Code. See Decision and Order, In the\n\nMatter of the Appeal of Shasta Linen Supply, Inc., No. AHB-WCA-14-31 (Dep’t of Ins.,\n\nState of Cal. June 20, 2016), http://www.insurance.ca.gov/0250-insurers/0500-legal-\n\ninfo/0600-decision-ruling/0100-precedential/upload/ShastaLinenSupplyInc.pdf.\n\n Other courts faced with the RPA and similar related documents have also\n\nsuggested that the program marketed by Applied Underwriters, including the RPA, is\n\ninsurance. See, e.g., Nat’l Convention Servs., 239 F. Supp. 3d at 786 (observing that the\n\nRPA and guaranteed cost policies “plausibly serve the common purpose of providing\n\nworkers’ compensation insurance at rates that are affected by loss experience”); Nielsen\n\nContracting, Inc. v. Applied Underwriters, Inc., 22 Cal. App. 5th 1096, 1116–17 (Cal. Ct.\n\nApp. 2018) (determining that the RPA’s provisions were meant to replace those of the\n\ninsurance policies and that the Applied Underwriters affiliated entities were “so\n\nenmeshed” and “intertwined” that the RPA and insurance policies should be considered\n\n 25\n\ftogether); Citizens of Humanity, LLC v. Applied Underwriters Captive Risk Assurance\n\nCo., Inc., 909 N.W.2d 614, 632 (Neb.) (stating that “the RPA has the hallmarks of a\n\nretrospective rating plan” and concluding that the RPA is an “agreement concerning or\n\nrelating to an insurance policy” under Nebraska law), cert. denied, 139 S. Ct. 274 (2018).\n\n While each of these other jurisdictions has evaluated the RPA under different laws\n\nand for different purposes, the general consensus has consistently been that the RPA is\n\nsubject to insurance regulations. We join that consensus in holding that the RPA at issue\n\nhere is an insurance contract under Virginia law. Because arbitration provisions in\n\ninsurance contracts are void under Virginia law, Va. Code § 38.2–312, AUCRA must\n\nface Minnieland’s claims in court.\n\n\n\n IV.\n\n For these reasons, we affirm the judgment of the district court.\n\n\n\n AFFIRMED.\n\n\n\n\n 26\n[END_CASE]", "role": "user" } ]
4,581,303
APPALACHIAN VOICES; Chesapeake Climate Action Network; Sierra Club; Wild Virginia, Inc. ; Cowpasture River Preservation Association; Friends of Buckingham ; Highlanders for Responsible Development; Jackson River Preservation Association ; Potomac Riverkeeper, D/B/A Potomac Riverkeeper Network, Inc. ; Shenandoah Riverkeeper, a Program of Potomac Riverkeeper Network; Shenandoah Valley Battlefields Foundation ; Shenandoah Valley Network; Virginia Wilderness Committee, Petitioners, v. STATE WATER CONTROL BOARD ; David K. Paylor, Director, Virginia Department of Environmental Quality ; Robert Dunn, Chair of the State Water Control Board; Virginia Department of Environmental Quality ; Melanie D. Davenport, Director, Water Permitting Division, Virginia Department of Environmental Quality, Respondents, Atlantic Coast Pipeline LLC, Intervenor. Chesapeake Bay Foundation, Incorporated; Robert Whitescarver; Jeanne Hoffman, Petitioners, v. State Water Control Board ; Melanie D. Davenport, Director, Water Permitting Division, Virginia Department of Environmental Quality ; Robert Dunn, Chair of the State Water Control Board; Virginia Department of Environmental Quality ; David K. Paylor, Director, Virginia Department of Environmental Quality, Respondents, Atlantic Coast Pipeline LLC, Intervenor.
Appalachian Voices v. State Water Control Board
2019-01-14
18-1077; 18-1079
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Wynn, Thacker", "parties": "", "opinions": [{"author": "Petition for review denied by published opinion. Chief Judge Gregory wrote the opinion", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1077\n\n\nAPPALACHIAN VOICES; CHESAPEAKE CLIMATE ACTION NETWORK;\nSIERRA CLUB; WILD VIRGINIA, INC.; COWPASTURE RIVER\nPRESERVATION ASSOCIATION; FRIENDS OF BUCKINGHAM;\nHIGHLANDERS FOR RESPONSIBLE DEVELOPMENT; JACKSON RIVER\nPRESERVATION ASSOCIATION; POTOMAC RIVERKEEPER, d/b/a Potomac\nRiverkeeper Network, Inc.; SHENANDOAH RIVERKEEPER, a program of\nPotomac Riverkeeper Network; SHENANDOAH VALLEY BATTLEFIELDS\nFOUNDATION; SHENANDOAH VALLEY NETWORK; VIRGINIA\nWILDERNESS COMMITTEE,\n\n Petitioners,\n\n v.\n\nSTATE WATER CONTROL BOARD; DAVID K. PAYLOR, Director, Virginia\nDepartment of Environmental Quality; ROBERT DUNN, Chair of the State Water\nControl Board; VIRGINIA DEPARTMENT OF ENVIRONMENTAL QUALITY;\nMELANIE D. DAVENPORT, Director, Water Permitting Division, Virginia\nDepartment of Environmental Quality,\n\n Respondents,\n\nATLANTIC COAST PIPELINE LLC,\n\n Intervenor.\n\n\n No. 18-1079\n\n\nCHESAPEAKE BAY FOUNDATION, INCORPORATED; ROBERT WHITESCARVER;\nJEANNE HOFFMAN,\n\n Petitioners,\n\f v.\n\nSTATE WATER CONTROL BOARD; MELANIE D. DAVENPORT, Director,\nWater Permitting Division, Virginia Department of Environmental Quality;\nROBERT DUNN, Chair of the State Water Control Board; VIRGINIA\nDEPARTMENT OF ENVIRONMENTAL QUALITY; DAVID K. PAYLOR,\nDirector, Virginia Department of Environmental Quality,\n\n Respondents,\n\nATLANTIC COAST PIPELINE LLC,\n\n Intervenor.\n\n\nOn Petition for Review of an Order of the Federal Energy Regulatory Commission.\n(17-002)\n\n\nArgued: September 28, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, WYNN, and THACKER, Circuit Judges\n\n\nPetition for review denied by published opinion. Chief Judge Gregory wrote the opinion,\nin which Judge Wynn and Judge Thacker joined.\n\n\nARGUED: Benjamin Alan Luckett, APPALACHIAN MOUNTAIN ADVOCATES,\nLewisburg, West Virginia, for Petitioners. Toby Jay Heytens, OFFICE OF THE\nATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for\nRespondents. Brooks Meredith Smith, TROUTMAN SANDERS LLP, Richmond,\nVirginia, for Intervenor. ON BRIEF: Gregory Buppert, Charmayne G. Staloff,\nJonathan M. Gendzier, SOUTHERN ENVIRONMENTAL LAW CENTER,\nCharlottesville, Virginia, for Petitioners Cowpasture River Preservation Association,\nFriends of Buckingham, Highlanders for Responsible Development, Jackson River\nPreservation Association, Inc., Potomac Riverkeeper, Inc., Shenandoah Riverkeeper,\nShenandoah Valley Battlefields Foundation, Shenandoah Valley Network, and Virginia\nWilderness Committee. Joseph M. Lovett, APPALACHIAN MOUNTAIN\nADVOCATES, Lewisburg, West Virginia, for Petitioners Appalachian Voices,\nChesapeake Climate Action Network, Sierra Club, and Wild Virginia. Jon Alan Mueller,\n\n 2\n\fMargaret L. Sanner, Ariel Solaski, CHESAPEAKE BAY FOUNDATION, INC.,\nAnnapolis, Maryland, for Petitioners Chesapeake Bay Foundation, Inc., Jeanne Hoffman,\nand Robert Whitescarver. Mark R. Herring, Attorney General, Stephen A. Cobb,\nDeputy Attorney General, Donald D. Anderson, Senior Assistant Attorney General,\nJ. Duncan Pitchford, Assistant Attorney General, David C. Grandis, Assistant Attorney\nGeneral, Matthew R. McGuire, Deputy Solicitor General, OFFICE OF THE\nATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for Respondents.\nAndrea W. Wortzel, TROUTMAN SANDERS LLP, Richmond, Virginia, for Intervenor.\n\n\n\n\n 3\n\fGREGORY, Chief Judge:\n\n Pursuant to Section 401 of the Clean Water Act (“CWA”), the Virginia State\n\nWater Control Board (“Board”) certified that it had reasonable assurance that activities\n\nrelated to the construction of a natural gas pipeline would not degrade the state’s water\n\nresources. Environmental groups and their individual members disagreed with this\n\ncertification, and they petitioned this Court to review the Board’s decision. Because we\n\nconclude that the Board’s Section 401 Certification for upland areas was not arbitrary and\n\ncapricious, we deny the petition for review.\n\n\n\n I.\n\n The Atlantic Coast Pipeline (“ACP”), a project developed and overseen by\n\nAtlantic Coast Pipeline LLC (“Atlantic”), is a proposed interstate natural gas pipeline,\n\nconstructed by Atlantic, that will be approximately 604 miles long and 42 inches in\n\ndiameter and will carry natural gas from Harrison County, West Virginia, to the eastern\n\nportions of Virginia and North Carolina. Approximately 307 miles of the ACP would\n\ntraverse the Commonwealth of Virginia. There are a total of 890 water body crossings\n\nlocations in Virginia, and the route of the ACP encompasses 74 migratory fish spawning\n\nwaters or their tributaries. The proposed ACP access roads will intersect 89 Virginia\n\nrivers and streams and will require the clearing of thousands of acres in Virginia. To\n\nobtain approval for construction, Atlantic had to comply with the following federal and\n\nstate laws and regulations relevant to this appeal.\n\n\n\n 4\n\f II.\n\n As an initial matter, Atlantic had to comply with the Natural Gas Act (“NGA”).\n\nUnder the NGA, a party is required to obtain authorization from the Federal Energy\n\nRegulatory Commission (“FERC”) in the form of a certificate of public convenience and\n\nnecessity to build or operate a natural gas pipeline. Upon receipt of an application for\n\nsuch a certificate, FERC undertakes a review of the environmental impacts of the\n\nproposed project under the National Environmental Policy Act (“NEPA”) and the NGA.\n\n42 U.S.C. §§ 4321 et seq.; 15 U.S.C. §§ 717 et seq. FERC accepts input from the public\n\nand then produces an environmental impact statement (“EIS”). Functioning as a “lead\n\nagency,” FERC coordinates the required authorizations, including Virginia’s water\n\nquality certification under the CWA. See 15 U.S.C. § 717n(b).\n\n Because the pipeline project involves the discharge of fill and dredged materials\n\ninto waterways and wetlands, Atlantic needed to obtain not only a certificate of public\n\nconvenience and necessity from FERC, but also a Section 404 CWA authorization from\n\nthe U.S. Army Corps of Engineers (“Army Corps”). See 33 U.S.C. § 1344(a); AES\n\nSparrows Point LNG, LLC v. Wilson, 589 F.3d 721, 724 (4th Cir. 2009). The Army\n\nCorps provided the authorization necessary for the ACP through issuing Nationwide\n\nPermit 12, which covers “activities required for the construction, maintenance, repair,\n\nand removal of utilities lines and associated facilities in waters of the United States.” See\n\n33 U.S.C. 1344(e)(1) (allowing the Secretary of the Army to issue permits on a\n\n“nationwide basis for any category of activities involving discharges of dredged or fill\n\nmaterial if the Secretary determines that the activities in such category are similar in\n\n 5\n\fnature, will cause only minimal adverse environmental effects when performed\n\nseparately, and will have only minimal cumulative adverse effect on the environment”).\n\n\n\n III.\n\n Atlantic was also required to obtain a Section 401 Certification. The NGA allows\n\nstates to regulate the environmental impacts of pipelines under the CWA. Delaware\n\nRiverkeeper Network v. Secretary Pa. Dep’t of Envtl. Prot., 833 F.3d 360, 368 (3d Cir.\n\n2016) (citing 15 U.S.C. § 717b(d)). Virginia exercises this regulatory authority through\n\nthe Board. See Va. Code § 62.1-44.15. Pursuant to Virginia law, the Board wields broad\n\npowers regarding regulatory matters impacting water quality in Virginia, and Section 401\n\nCertifications fall under its authority. Id. The Virginia Department of Environmental\n\nQuality (“DEQ”) serves as the Board’s staff, and the Board may assign DEQ tasks and\n\ndelegate DEQ the authority to make decisions. See Va. Code Ann. § 62.1-44.14. We\n\nwill refer to the Board and DEQ together as “the State Agencies” when their actions are\n\nin concert.\n\n Under the Virginia Water Protection (“VWP”) Program, the Board, after soliciting\n\nand considering public comment and consulting with relevant agencies, may issue a\n\nVWP permit “if it has determined that the proposed activity is consistent with the\n\nprovisions of the Clean Water Act and the State Water Control Law and will protect in-\n\nstream beneficial uses.” Va. Code Ann. § 62.1-44.15:20(B). The Board may also certify\n\na nationwide Corps permit, such as Nationwide Permit 12, as meeting these requirements\n\nso long as the permit meets specified criteria. See 9 Va. Admin. Code 25-210-130(H).\n\n 6\n\fSpecifically, Section 401 states “[a]ny applicant for a Federal license or permit to conduct\n\nany activity . . . which may result in any discharge into the navigable waters” must seek\n\n“a certification from the State in which the discharge originates . . . that any such\n\ndischarge will comply with the applicable provisions” of the CWA. 33 U.S.C.\n\n§ 1341(a)(1). In addition, Section 401 states, “[n]o license or permit shall be granted if\n\ncertification has been denied by the State.” Id. If the state grants the Section 401\n\nCertification — whether with or without conditions — it must contain “[a] statement that\n\nthere is a reasonable assurance that the activity will be conducted in a manner which will\n\nnot violate applicable water quality standards.” 40 C.F.R. § 121.2(a)(3); see PUD No. 1\n\nof Jefferson Cty. v. Washington Dep’t of Ecology, 511 U.S. 700, 712 (1994). In addition,\n\nthe regulations allow for Virginia to consider activities that impact the upland areas that\n\nmay have the potential to affect water quality but do not fall under the scope of a VWP\n\npermit when the pipeline is over 36 inches inside diameter. Va. Code § 62.1-44.15:80.\n\n\n\n IV.\n\n Atlantic applied for the certificate of public convenience and necessity from FERC\n\nand Section 404 authorization from the Army Corps in September 2015. Atlantic filed an\n\namendment to its FERC certificate application in March 2016. In October 2017, FERC\n\nissued the certificate to Atlantic to construct and operate the pipeline. On April 7, 2017,\n\nthe DEQ issued a Section 401 Certification for the wetland, river, and streams crossings\n\nas covered in the Section 404 Nationwide Permit 12. In May 2017, the DEQ explained\n\nthat the Section 401 Certification for the Pipeline would entail two separate parts: (1) the\n\n 7\n\fcertification for the Army Corps Nationwide Permit 12, issued in April, applying to the\n\nPipeline’s wetland, river, and streams crossings (the “Wetlands and Streams\n\nCertification”), and (2) an additional Section 401 Certification review process to evaluate\n\nthe “upland” impacts of the Pipeline, terrestrial areas that are not covered by the Army\n\nCorps Permit (the “Upland Certification”). Specifically, the Upland Certification would\n\n“include all proposed upland activities associated with the construction, operation,\n\nmaintenance, and repair of the pipeline, any components thereof or appurtenances\n\nthereto, and related access roads and rights-of-way as well as certain project related\n\nsurface water withdrawals.” J.A 1083.\n\n On November 9, 2017, the DEQ recommended that the Board approve a Section\n\n401 Upland Certification of the project. On December 20, 2017, the Board issued the\n\nUpland Certification for the ACP with conditions. This Certification was distinct from\n\nthe Wetlands and Steams Certification. This Upland Certification provided that it “shall\n\nbe effective only following submission, review and final approval as required by law of\n\nthe Karst Mitigation Plan, Annual Standards and Specifications, and Erosion and\n\nSediment Control Plans and Storm Water Management Plans, and a report to the Board\n\nand the public by DEQ on the adequacy of these materials.” J.A. 29.\n\n Petitioners timely filed two petitions for review of the Certification on January 18,\n\n2018. The petitions were consolidated by court order on January 31, 2018. We possess\n\njurisdiction to review the Board’s Section 401 Upland Certification pursuant to 15 U.S.C.\n\n§ 717r(d)(1).\n\n\n\n 8\n\f The petitioners contend the Board’s issuance of the Section 401 Upland\n\nCertification was arbitrary and capricious and should be vacated for four reasons: (1) the\n\nState Agencies effectively invalidated their own finding of reasonable assurance when it\n\nvoted to reopen the comment period on the Section 401 Certification of the Army Corps\n\nof Engineers Nationwide Permit 12; (2) the State Agencies arbitrarily and capriciously\n\nfailed to assess the combined impacts on water quality that would result from multiple\n\nareas of construction activities within individual watershed areas; (3) the State Agencies\n\narbitrarily and capriciously failed to conduct an adequate antidegradation review; and (4)\n\nthe State Agencies arbitrarily and capriciously failed to ensure that the water quality in\n\nkarst geology regions would be protected. Respondents and intervenor in turn deny that\n\nthe State Agencies acted arbitrarily and capriciously and argue that the petitioners lack\n\nstanding to bring this petition.\n\n On April 12, 2018, the Board approved a second 30-day public comment period\n\nrelated to the Wetlands and Steams Certification. On August 21, 2018, the Board heard a\n\npresentation from the DEQ summarizing the public comment period and denied a motion\n\nto reevaluate this contested Certification.\n\n\n\n V.\n\n The respondents and intervenor argue as an initial matter that petitioners do not\n\nhave standing to litigate this petition for review. Spokeo, Inc. v. Robins, 136 S. Ct. 1540,\n\n1547 (2016) (quoting Lujan v. Defenders of Wildlife, 504 U.S. 555, 560-61 (1992))\n\n(Article III standing requires (1) an injury-in-fact (2) that is fairly traceable to the\n\n 9\n\fchallenged conduct of the defendant, and (3) that is likely to be redressed through a\n\nfavorable judicial decision). We disagree.\n\n This Court has previously rejected respondents’ and intervenor’s arguments on\n\nstanding. Sierra Club v. State Water Control Bd., 898 F.3d 383, 400-02 (4th Cir. 2018).\n\nPetitioners have established an injury-in-fact even though the State Agencies could\n\nchoose to waive certification. We have previously held that the denial of an opportunity,\n\nin this case, to have the project vetoed or have additional restrictions can constitute an\n\ninjury-in-fact. Id. at 401. In addition, petitioners successfully establish traceability and\n\nredressability given that we could vacate the Board’s decision and determine that its\n\ndecision was not based on a reasonable assurance and instead was arbitrary and\n\ncapricious. Petitioners’ injuries could be remedied if the Board required Atlantic to take\n\nadditional measures that would address petitioners’ grievances. In our previous decision\n\nwe held petitioners established traceability and redressability in this very context. Id.\n\nPetitioners have demonstrated the requirements for standing.\n\n\n\n VI.\n\n We review Virginia’s Section 401 Certification under the standards set forth in the\n\nAdministrative Procedures Act (“APA”). See AES Sparrows Point LNG, LLC v. Wilson,\n\n589 F.3d 721, 727 (4th Cir. 2009). 1 This Court applies the arbitrary and capricious\n\n\n 1\n Asserting that the APA is not applicable to actions by State Agencies,\nrespondents argue that Va. Code § 2.2-4027 establishes the applicable standard of review.\nThat statute provides that issues of fact shall be decided based on “whether there was\n(Continued)\n 10\n\fstandard of the APA to the State Agencies’ challenged findings and conclusions. Sierra\n\nClub, 898 F.3d at 403.\n\n To survive review under the arbitrary and capricious standard, an agency decision\n\nmust show that the agency examined “the relevant data and articulate[d] a satisfactory\n\nexplanation for its action including a ‘rational connection between the facts found and the\n\nchoice made.’” Motor Vehicle Mfrs. Ass’n of U.S., Inc. v. State Farm Mut. Auto Ins. Co.,\n\n463 U.S. 29, 43 (1983) (quoting Burlington Truck Lines v. United States, 371 U.S. 156,\n\n168 (1962)).\n\n Agency action is arbitrary and capricious if the agency relies on factors that\n Congress did not intend for it to consider, entirely ignores important aspects\n of the problem, explains its decision in a manner contrary to the evidence\n before it, or reaches a decision that is so implausible that it cannot be\n ascribed to a difference in view.\n\nBedford Cty. Mem’l Hosp. v. Health & Human Servs., 769 F.2d 1017, 1022 (4th Cir.\n\n1985) (citing Motor Vehicle Mfrs. Ass’n, 463 U.S. at 43). This Circuit has held that\n\n [r]eview under this standard is highly deferential, with a presumption in\n favor of finding the agency action valid. Especially in matters involving\n not just simple findings of fact but complex predictions based on special\n expertise, a reviewing court must generally be at its most deferential. In\n determining whether agency action was arbitrary or capricious, the court\n must consider whether the agency considered the relevant factors and\n whether a clear error of judgment was made. Although this inquiry into the\n facts is to be searching and careful, the ultimate standard of review is a\n narrow one. The court is not empowered to substitute its judgment for that\n of the agency. Deference is due where the agency has examined the\n\n\n\n\nsubstantial evidence in the agency record to support the agency decision.” As we did in\nSierra Club, we decline to resolve this issue because petitioners’ claims fail even under\nthe substantial evidence standard. 898 F.3d at 403 n.13.\n\n 11\n\f relevant data and provided an explanation of its decision that includes a\n rational connection between the facts found and the choice made.\n\nOhio Valley Envtl. Coal. v. Aracoma Coal Co., 556 F.3d 177, 192 (4th Cir. 2009)\n\n(internal quotation marks and citations omitted). Nonetheless, if a state agency’s Section\n\n401 certification is found to be arbitrary and capricious, the Court must vacate the\n\ncertification. 5 U.S.C. § 706(2)(A).\n\n\n\n VII.\n\n A.\n\n Turning to petitioners’ first argument, we hold that the decision to reopen the\n\ncomment period did not render the State Agencies’ Section 401 Upland Certification\n\narbitrary and capricious. The comment period was re-opened for the Wetlands and\n\nStreams Certification and not the Upland Certification at issue in this case. In any event,\n\nthe Wetlands and Streams Certification was not ultimately revoked.\n\n B.\n\n Moving to the petitioners’ second argument, we conclude that the State Agencies’\n\ndecision not to conduct a combined effect analysis does not render their issuance of a\n\nSection 401 Upland Certification arbitrary and capricious for three reasons.\n\n First, the Section 401 Upland Certification in question deals with project-related\n\nactivities taking place in upland areas. The Upland Certification supplemented the FERC\n\ncertificate and the prior Wetland and Streams Certification of the Army Corps’\n\nNationwide Permit 12 regarding waterways and utility line crossings. As the State\n\n\n 12\n\fAgencies explained, “the conditions in the proposed additional 401 Certification are in\n\naddition to any other Federal or State permit or regulatory requirements including the\n\nexpressed conditions imposed by FERC.” J.A. 1059. The Upland Certification in\n\nquestion is not designed to function as a stand-alone document, comprehensively\n\ncovering all pieces of relevant data and potentialities. For example, record evidence\n\navailable to the State Agencies explains, “while the impacts to jurisdictional waters\n\nauthorized by the Corps under Section 404 of the Clean Water Act are separate from\n\nupland activities that are the subject of this Certification, the Corps also analyzed the\n\ncumulative effects of linear utility projects and found that the individual and cumulative\n\nadverse effects on the aquatic environment resulting from the activities authorized by the\n\nNationwide Permit 12 will be no more than minimal and each crossing is a single and\n\ncomplete project.” J.A. 999. The Army Corps examined cumulative impacts, and it\n\nwould be redundant and inefficient for the State Agencies to duplicate these efforts. The\n\nUpland Certification works in conjunction with other regulatory tools and cannot be\n\njudged in a void, and it supplements other pieces of the regulatory framework. It is not\n\nrequired to cover combined effect analysis because other parts of the regulatory process\n\nsufficiently address that subject matter. The State Agencies in the current appeal used\n\ntheir resources to issue the Upland Certification to fill an information gap regarding the\n\nimpact of upland activities, which were not typically covered under prior CWA\n\ncertifications. The State Agencies properly made a unique contribution instead of\n\nduplicating the efforts of other regulatory bodies as petitioners’ request. See Sierra Club,\n\n898 F.3d at 407.\n\n 13\n\f Second, State Agencies have broad discretion when developing the criteria for\n\ntheir Section 401 Certification. The only requirement imposed by the regulations is that\n\nStates must establish procedures for public notice when there are applications for\n\ncertification, and to the extent deemed appropriate, procedures for public hearings in\n\nconnection with specific applications. 33 U.S.C. § 1341(a)(1). Nonetheless, nothing in\n\nSection 401 restricts states to a single certificate proceeding, and Section 401 does not\n\nrequire states to undertake a single cumulative review of all possible impacts in a single\n\ncertification.\n\n Petitioners’ rely on two federal regulations in arguing that a cumulative review is\n\nrequired, 40 C.F.R. § 230.7(a) and 40 C.F.R. § 230.11(g)(1), but those regulations impose\n\nduties—including a duty to make factual determinations and consider cumulative\n\neffects—on the Army Corps under Section 404, not on states under Section 401.\n\nMoreover, petitioners contend that two cases require State Agencies to take into account\n\ncombined effects lest their decisions be rendered arbitrary and capricious. See Klamath-\n\nSiskiyou Wildlands Ctr. v. BLM, 387 F.3d 989, 993 (9th Cir. 2004); Idaho Rivers United\n\nv. Probert, Case No.: 3:16-102, 2016 U.S. Dist. LEXIS 63767, at *32-34. Furthermore,\n\npetitioners invoke the Supreme Court’s decision in Motor Vehicles Manufacturers\n\nAssociation v. State Farm Mutual Automobile Ins. Co., to argue that all “relevant data”\n\nmust be considered. 463 U.S. 29, 43 (1983). We conclude, however, that both the\n\nKlamath-Siskiyou Wildlands and Idaho Rivers United cases are distinguishable and\n\nunpersuasive because in those cases the Bureau of Land Management and the Forest\n\nService, respectively, faced violations under NEPA, not the CWA. Klamath-Siskiyou\n\n 14\n\fWildlands Ctr., 387 F.3d at 993–94; Idaho Rivers United, 2016 U.S. Dist. LEXIS 63767,\n\nat *33. Unlike the CWA, NEPA requires a cumulative effects analysis, and thus cases\n\ndecided under NEPA are not dispositive authority here. Furthermore, Motor Vehicle\n\nManufacturers Association, which deals with the National Highway Traffic Safety\n\nAdministration, does not mention cumulative effects or the CWA, and thus the case does\n\nnot stand for the proposition that the CWA should be broadened to encompass a\n\ncombined impact analysis.\n\n Finally, the State Agencies’ failure to explicitly consider the combined effects of\n\nmultiple areas of construction within individual watersheds such as the Chesapeake Bay\n\nwatershed and the Chesapeake Bay Total Maximum Daily Load (“Bay TMDL”) did not\n\nrender their decision arbitrary and capricious. 2 As an initial matter, despite petitioners’\n\npreferences, there are no express regulations that require the State Agencies to consider\n\nthe combined effects of individual watersheds. In addition, the Ninth Circuit has\n\nexplained that TMDLs like the Chesapeake Bay TMDL are “primarily informational\n\ntools that allow states to proceed from the identification of water requiring additional\n\nplanning to the required plans.” Pronsolino v. Nastri, 291 F. 3d 1123, 1129 (9th Cir.\n\n2002). Moreover, TMDLs do not give rise to an independent legal obligation.\n\nPronsolino, 291 F.3d 1123, 1140. Consequently, the Chesapeake TMDL does not\n\nconstitute a regulatory mandate that the State Agencies were required to address before\n\nissuing the Section 401 Upland Certification. Furthermore, protection measures for the\n\n 2\n The Bay TMDL is a federal-state partnership that monitors the water quality\nstandards in the Chesapeake Bay and its related tributaries. J.A. 888.\n\n 15\n\fChesapeake Bay TMDL are offered through other tools such as the FERC EIS and the\n\nStorm Water Prevention Plan. J.A. 664-665; 1138-1140.\n\n The State Agencies more than satisfied their obligations by reviewing upland\n\nactivities as well as stream and wetland crossings. The Board’s decisions are not\n\nrendered arbitrary and capricious because it did not conduct an independent review of the\n\ncumulative effects on water quality within individual watersheds, even if this was\n\npetitioners’ preference. To deem an agency action arbitrary and capricious their decision\n\nmust be “so implausible that it could not be ascribed to a difference in view or the\n\nproduct of agency expertise.” State Farm Mut. Auto. Ins. Co., 463 U.S. at 43. The lack\n\nof an explicit combined effect analysis in the Section 401 Upland Certification does not\n\nrise to this level, especially given that there are other regulatory tools that were utilized to\n\nconsider those impacts.\n\n C.\n\n 1.\n\n Turning to petitioners’ third argument, we do not find that the State Agencies’\n\nreasonable assurance determination to be arbitrary and capricious simply because they\n\nrelied on existing Virginia water quality standards and regulations to effectively address\n\nconcerns regarding water quality deterioration.\n\n Under the CWA, “states have the primary role in promulgating water quality\n\nstandards.” Piney Run Preservation Ass’n v. County Comm’rs of Carroll Cty., 268 F.3d\n\n255, 265 n.9 (4th Cir. 2001). States must initially classify the uses for which their water\n\nis to be protected and then determine the necessary level of water quality for their\n\n 16\n\fpreferred uses. See NRDC v. EPA, 16 F.3d 1395, 1400 (4th Cir. 1993). Virginia’s water-\n\nquality policy is relevant in two respects: its narrative water-quality criterion and its anti-\n\ndegradation policy.\n\n Virginia’s water-quality criterion mandates that “State waters . . . shall be free\n\nfrom substances attributable to . . . waste in concentrations, amounts, or combinations\n\nwhich contravene established standards or interfere directly or indirectly with designated\n\nuses of such water or which are inimical or harmful to human, animal, plant, or aquatic\n\nlife.” 9 Va. Admin. Code § 25-260-20(A). The regulation explains that any substance\n\n“that produce[s] . . . turbidity” is a substance to be controlled. Id. The regulation\n\nprovides examples of “turbidity” such as floating debris, oil, and other materials that are\n\nsuspended solids in a body of water.\n\n In addition, Virginia’s antidegradation policy shall be applied whenever any\n\nactivity is proposed that has the potential to affect existing surface water quality. 9 Va.\n\nAdmin. Code § 25-260-30(A). The antidegradation policy classifies Virginia’s water into\n\nthree tiers and provides differing levels of protection based on the water’s tier. See 9 Va.\n\nAdmin. Code § 25-260-30(A).\n\n The Policy defines Tier 3 waters as “exceptional”; these waters “shall be\n\nmaintained and protected to prevent permanent or long-term degradation or impairment.”\n\n9 Va. Admin. Code § 25-260-30(A)(3)(b)(1). The policy specifically provides that “[n]o\n\nnew, additional, or increased discharge of sewage, industrial wastes or other pollution\n\ninto [Tier 3 waters] shall be allowed.” 9 Va. Admin. Code § 25-260-30(A)(3)(b)(2).\n\nNonetheless, “[a]ctivities causing temporary sources of pollution may be allowed in [Tier\n\n 17\n\f3 waters] even if degradation may be expected to temporarily occur provided that after a\n\nminimal period of time the waters are returned or restored to conditions equal to or better\n\nthan those existing just prior to the temporary source of pollution.” 9 Va. Admin. Code\n\n§ 25-260-30(A)(3)(b)(3).\n\n The Policy defines Tier 2 waters as those that “exceed water quality standards.” 9\n\nVa. Admin. Code § 25-260-30(A)(2). The protection for these waters and their quality\n\nare lower and the regulation states that the quality of Tier 2 waters “shall be maintained\n\nand protected unless the board finds . . . that allowing lower water quality is necessary to\n\naccommodate important economic or social development in the area in which the waters\n\nare located.” 9 Va. Admin. Code § 25-260-30(A)(2).\n\n Last, Tier 1 waters constitute all Virginia waters that are not designated Tier 2 or\n\nTier 3. The regulation classifying the level of protection for these waters’ states,\n\n“existing in-stream water uses and the level of water quality necessary to protect the\n\nexisting uses shall be maintained and protected.” 9 Va. Admin. Code § 25-260-30(A)(1).\n\n In Virginia a project may be permitted under a Construction General Permit. 9\n\nVa. Admin. Code § 25-880-70 Part II. The Construction General Permit incorporates the\n\nrequirements of two other state laws, the Virginia Storm Water Management (“VSM”)\n\nLaw, Va. Code § 62.1-44.15:24 et seq., and the Virginia Erosion and Sediment Control\n\n(“VESC”) Law, Va. Code § 62.1-44.15:51, et seq.\n\n The CWA has an exemption for natural gas pipeline construction projects and\n\ntherefore Virginia’s regulatory scheme diverges from the federal environmental\n\nprotections. See 33 U.S.C. § 1342(I)(2). Consequently, Virginia still regulates natural\n\n 18\n\fgas pipeline projects through its Annual Standards and Specifications (“AS&S”)\n\nProgram. See Va. Code § 62.1-44.15:55(D). The AS&S program requires a project\n\ndeveloper to submit annual standards and specifications for DEQ’s review and approval.\n\nSee 9 Va. Admin. Code § 25-870-170(A). Through this program Virginia ensures that\n\nprojects will meet the same requirements imposed on other projects subject to the\n\nVirginia Construction General Permit. See 9 Va. Admin. Code § 25-870-170(A).\n\nNonetheless, once DEQ approves a developer’s annual standards and specifications as\n\nsatisfying the requirements of the VSM and VESC, the entity generally need not submit\n\nsite-specific VSM and VESC plans to DEQ for approval. See Va. Code § 62.1-\n\n44.15:55(D). This allows the projects to become more self-regulating.\n\n Typically, ensuring an activity’s compliance with water quality standards requires\n\nan antidegradation review. See Nat. Res. Def. Council, Inc. v. EPA, 16 F.3d 1395, 1400\n\n(4th Cir. 1993); see also 40 C.F.R. § 131.12 (requiring states to develop and adopt a\n\nstatewide antidegradation policy). The CWA’s antidegradation policy requires that state\n\nstandards be “sufficient to maintain existing beneficial uses of navigable waters,\n\npreventing further degradation.” 33 U.S.C. § 1313(d). State antidegradation policies\n\nmust be consistent with 40 C.F.R. § 131.12(a), and must protect existing uses, maintain\n\nthe existing quality of high-quality waters unless degradation is justified by important\n\nsocioeconomic development, and prohibit degradation of national resource waters. Id.\n\n§ 131.12(a).\n\n\n\n\n 19\n\f 2.\n\n We do not find that the State Agencies’ failure to conduct a separate\n\nantidegradation review before issuing its Upland Certification renders their decision\n\narbitrary and capricious for two reasons.\n\n First, in Virginia, the AS&S program requires a project developer to submit annual\n\nstandards and specifications for DEQ’s review and approval, thereby ensuring that\n\nprojects will meet the same requirements that would apply were they covered by the\n\nVirginia Construction General Permit. See 9 Va. Admin. Code § 25-870-170(A). The\n\nAS&S also incorporate all the requirements of EPA’s Construction General Permit. J.A.\n\n1124-1125. The AS&S in this case were developed over eighteen months and represent a\n\nthorough process of development, revision and refinement to ensure that the ACP meet\n\nthe technical and legal requirements for Virginia. J.A. 1087. Both federal and state\n\nregulators have concluded that application of technical requirements like those in the\n\nAS&S “will not result in a lowering of water quality,” which renders the individualized\n\nreview the petitioners suggest “unnecessary.” J.A. 11. There is no indication that these\n\nAS&S fail to protect water quality in Virginia. To the contrary, these regulations have\n\nbeen found as a matter of law to protect water quality in Virginia. See Kelble v.\n\nCommonwealth, Case No. CL 14-762, at 4-5 (Richmond Cir. Ct. Apr. 10, 2017).\n\n Second, State Agencies did not have to conduct a separate antidegradation review\n\nbecause the impact on sediment on the water would only be temporary. Under FERC’s\n\nfinal EIS, it was determined that any water quality impacts stemming from construction\n\nwould be temporary. J.A. 623. Even with respect to Tier 3 waters, the policy states that\n\n 20\n\f“[a]ctivities causing temporary sources of pollution may be allowed in [Tier 3] waters . . .\n\neven if degradation may be expected to occur provided that after a minimal period of\n\ntime the waters are returned or restored to conditions equal to or better that those existing\n\njust prior to the temporary source of pollution.” 9 Va. Admin. Code 25-260-\n\n30A(3)(b)(3). Even in the most protected state waters, Virginia does not consider\n\ntemporary sources of pollution, such as the construction of the ACP, to violate\n\nantidegradation policies.\n\n Thus, nothing was arbitrary and capricious about the State Agencies’ decision not\n\nto conduct a separate antidegradation review.\n\n D.\n\n Turning to the final challenge raised by petitioners, we find that the State\n\nAgencies’ treatment of karst terrain was not arbitrary or capricious because of the\n\nconditions imposed on the Section 401 Upland Certification.\n\n Karst geology refers to geological formations of soluble limestone bedrock that\n\ncreates underground water flow systems where the rocks have dissolved and created\n\nsinkholes, caves and underground springs and rivers. J.A. 669. The constitution of these\n\nareas presents additional environmental considerations for pipeline construction\n\nincluding, sinkhole collapse, sinkhole flooding and associated groundwater\n\ncontamination. J.A. 904-905.\n\n The record demonstrates that the State Agencies took petitioners’ concerns\n\nregarding karst geology into consideration. J.A. 31. Virginia’s Section 401 Upland\n\nCertification contains five specific requirements concerning the protection of karst\n\n 21\n\fterrain. J.A. 31-32. First, Atlantic must provide the State an addendum to a 51-page\n\nKarst Survey Report prior to any land disturbing activities. J.A. 212-237; J.A. 31.\n\nSecond, Atlantic must follow the Karst Terrain Assessment, Construction, Monitoring,\n\nand Mitigation Plan. J.A. 31. This plan allows for route adjustments to avoid karst\n\nterrain. J.A. 1001. Third, based on the conditions in the Section 401 Upland\n\nCertification, Atlantic must conduct contingency planning in order to address any\n\naccidental spills or releases during construction on karst terrain. Fourth, water surveys\n\nregarding drinkable water in karst regions are required under the Section 401 Upland\n\nCertification. J.A. 31. Finally, Atlantic has a liability of five million dollars to cover the\n\ncost of any impacts to private water supplies, which encompasses karst regions. J.A. 32.\n\n Reliance on these conditions, even the prospective ones, does not render the State\n\nAgencies’ issuance of the Section 401 Upland Certification arbitrary and capricious. See\n\nPort of Seattle v. Pollution Control Hearings Bd., 90 P.3d 659, 677 (Wash. 2004)\n\n(holding regulators did not act arbitrarily or capriciously by basing reasonable assurance\n\n“on future submissions of revised plans, reports, and studies, so long as their\n\nimplementation and anticipated outcome meet the reasonable assurance test”).\n\n Moreover, the mere existence of risk to karst geology does not render the State\n\nAgencies’ decision to issue the Section 401 Upland Certification arbitrary and capricious.\n\nBased on the information in the record, this Court finds that the State Agencies had\n\nreasonable assurance that karst regions would be protected given the conditions imposed\n\non the Section 401 Upland Certification. We “see no purpose we would serve by\n\nstepping in and second-guessing the analytical methods Virginia deemed appropriate to\n\n 22\n\fprovide it with reasonable assurance that its water quality would be protected.” Sierra\n\nClub., 898 F.3d at 407.\n\n\n\n VIII.\n\n Governmental agencies can always take additional steps to increase the protection\n\nof the environment. But that is not the applicable legal standard this Court utilizes when\n\nreviewing a state agency’s issuance of a Section 401 Certification. We must determine\n\n“whether the agency considered the relevant factors and whether a clear error of\n\njudgment was made.” Ohio Valley Envtl. Coal., 556 F.3d 177, 192. There is no\n\nindication that the State Agencies did not consider relevant factors or that they clearly\n\nmade an error of judgment. In conclusion, because we find that the State Agencies did\n\nnot act arbitrarily and capriciously in issuing the Section 401 Upland Certification, we\n\ndeny the petition for review.\n\n\n\n PETITION FOR REVIEW DENIED\n\n\n\n\n 23", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4358556/", "author_raw": "Petition for review denied by published opinion. Chief Judge Gregory wrote the opinion"}]}
GREGORY
WYNN
THACKER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4581303/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: APPALACHIAN VOICES; Chesapeake Climate Action Network; Sierra Club; Wild Virginia, Inc. ; Cowpasture River Preservation Association; Friends of Buckingham ; Highlanders for Responsible Development; Jackson River Preservation Association ; Potomac Riverkeeper, D/B/A Potomac Riverkeeper Network, Inc. ; Shenandoah Riverkeeper, a Program of Potomac Riverkeeper Network; Shenandoah Valley Battlefields Foundation ; Shenandoah Valley Network; Virginia Wilderness Committee, Petitioners, v. STATE WATER CONTROL BOARD ; David K. Paylor, Director, Virginia Department of Environmental Quality ; Robert Dunn, Chair of the State Water Control Board; Virginia Department of Environmental Quality ; Melanie D. Davenport, Director, Water Permitting Division, Virginia Department of Environmental Quality, Respondents, Atlantic Coast Pipeline LLC, Intervenor. Chesapeake Bay Foundation, Incorporated; Robert Whitescarver; Jeanne Hoffman, Petitioners, v. State Water Control Board ; Melanie D. Davenport, Director, Water Permitting Division, Virginia Department of Environmental Quality ; Robert Dunn, Chair of the State Water Control Board; Virginia Department of Environmental Quality ; David K. Paylor, Director, Virginia Department of Environmental Quality, Respondents, Atlantic Coast Pipeline LLC, Intervenor.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-14\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1077\n\n\nAPPALACHIAN VOICES; CHESAPEAKE CLIMATE ACTION NETWORK;\nSIERRA CLUB; WILD VIRGINIA, INC.; COWPASTURE RIVER\nPRESERVATION ASSOCIATION; FRIENDS OF BUCKINGHAM;\nHIGHLANDERS FOR RESPONSIBLE DEVELOPMENT; JACKSON RIVER\nPRESERVATION ASSOCIATION; POTOMAC RIVERKEEPER, d/b/a Potomac\nRiverkeeper Network, Inc.; SHENANDOAH RIVERKEEPER, a program of\nPotomac Riverkeeper Network; SHENANDOAH VALLEY BATTLEFIELDS\nFOUNDATION; SHENANDOAH VALLEY NETWORK; VIRGINIA\nWILDERNESS COMMITTEE,\n\n Petitioners,\n\n v.\n\nSTATE WATER CONTROL BOARD; DAVID K. PAYLOR, Director, Virginia\nDepartment of Environmental Quality; ROBERT DUNN, Chair of the State Water\nControl Board; VIRGINIA DEPARTMENT OF ENVIRONMENTAL QUALITY;\nMELANIE D. DAVENPORT, Director, Water Permitting Division, Virginia\nDepartment of Environmental Quality,\n\n Respondents,\n\nATLANTIC COAST PIPELINE LLC,\n\n Intervenor.\n\n\n No. 18-1079\n\n\nCHESAPEAKE BAY FOUNDATION, INCORPORATED; ROBERT WHITESCARVER;\nJEANNE HOFFMAN,\n\n Petitioners,\n\f v.\n\nSTATE WATER CONTROL BOARD; MELANIE D. DAVENPORT, Director,\nWater Permitting Division, Virginia Department of Environmental Quality;\nROBERT DUNN, Chair of the State Water Control Board; VIRGINIA\nDEPARTMENT OF ENVIRONMENTAL QUALITY; DAVID K. PAYLOR,\nDirector, Virginia Department of Environmental Quality,\n\n Respondents,\n\nATLANTIC COAST PIPELINE LLC,\n\n Intervenor.\n\n\nOn Petition for Review of an Order of the Federal Energy Regulatory Commission.\n(17-002)\n\n\nArgued: September 28, 2018 Decided: January 14, 2019\n\n\nBefore GREGORY, Chief Judge, WYNN, and THACKER, Circuit Judges\n\n\nPetition for review denied by published opinion. Chief Judge Gregory wrote the opinion,\nin which Judge Wynn and Judge Thacker joined.\n\n\nARGUED: Benjamin Alan Luckett, APPALACHIAN MOUNTAIN ADVOCATES,\nLewisburg, West Virginia, for Petitioners. Toby Jay Heytens, OFFICE OF THE\nATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for\nRespondents. Brooks Meredith Smith, TROUTMAN SANDERS LLP, Richmond,\nVirginia, for Intervenor. ON BRIEF: Gregory Buppert, Charmayne G. Staloff,\nJonathan M. Gendzier, SOUTHERN ENVIRONMENTAL LAW CENTER,\nCharlottesville, Virginia, for Petitioners Cowpasture River Preservation Association,\nFriends of Buckingham, Highlanders for Responsible Development, Jackson River\nPreservation Association, Inc., Potomac Riverkeeper, Inc., Shenandoah Riverkeeper,\nShenandoah Valley Battlefields Foundation, Shenandoah Valley Network, and Virginia\nWilderness Committee. Joseph M. Lovett, APPALACHIAN MOUNTAIN\nADVOCATES, Lewisburg, West Virginia, for Petitioners Appalachian Voices,\nChesapeake Climate Action Network, Sierra Club, and Wild Virginia. Jon Alan Mueller,\n\n 2\n\fMargaret L. Sanner, Ariel Solaski, CHESAPEAKE BAY FOUNDATION, INC.,\nAnnapolis, Maryland, for Petitioners Chesapeake Bay Foundation, Inc., Jeanne Hoffman,\nand Robert Whitescarver. Mark R. Herring, Attorney General, Stephen A. Cobb,\nDeputy Attorney General, Donald D. Anderson, Senior Assistant Attorney General,\nJ. Duncan Pitchford, Assistant Attorney General, David C. Grandis, Assistant Attorney\nGeneral, Matthew R. McGuire, Deputy Solicitor General, OFFICE OF THE\nATTORNEY GENERAL OF VIRGINIA, Richmond, Virginia, for Respondents.\nAndrea W. Wortzel, TROUTMAN SANDERS LLP, Richmond, Virginia, for Intervenor.\n\n\n\n\n 3\n\fGREGORY, Chief Judge:\n\n Pursuant to Section 401 of the Clean Water Act (“CWA”), the Virginia State\n\nWater Control Board (“Board”) certified that it had reasonable assurance that activities\n\nrelated to the construction of a natural gas pipeline would not degrade the state’s water\n\nresources. Environmental groups and their individual members disagreed with this\n\ncertification, and they petitioned this Court to review the Board’s decision. Because we\n\nconclude that the Board’s Section 401 Certification for upland areas was not arbitrary and\n\ncapricious, we deny the petition for review.\n\n\n\n I.\n\n The Atlantic Coast Pipeline (“ACP”), a project developed and overseen by\n\nAtlantic Coast Pipeline LLC (“Atlantic”), is a proposed interstate natural gas pipeline,\n\nconstructed by Atlantic, that will be approximately 604 miles long and 42 inches in\n\ndiameter and will carry natural gas from Harrison County, West Virginia, to the eastern\n\nportions of Virginia and North Carolina. Approximately 307 miles of the ACP would\n\ntraverse the Commonwealth of Virginia. There are a total of 890 water body crossings\n\nlocations in Virginia, and the route of the ACP encompasses 74 migratory fish spawning\n\nwaters or their tributaries. The proposed ACP access roads will intersect 89 Virginia\n\nrivers and streams and will require the clearing of thousands of acres in Virginia. To\n\nobtain approval for construction, Atlantic had to comply with the following federal and\n\nstate laws and regulations relevant to this appeal.\n\n\n\n 4\n\f II.\n\n As an initial matter, Atlantic had to comply with the Natural Gas Act (“NGA”).\n\nUnder the NGA, a party is required to obtain authorization from the Federal Energy\n\nRegulatory Commission (“FERC”) in the form of a certificate of public convenience and\n\nnecessity to build or operate a natural gas pipeline. Upon receipt of an application for\n\nsuch a certificate, FERC undertakes a review of the environmental impacts of the\n\nproposed project under the National Environmental Policy Act (“NEPA”) and the NGA.\n\n42 U.S.C. §§ 4321 et seq.; 15 U.S.C. §§ 717 et seq. FERC accepts input from the public\n\nand then produces an environmental impact statement (“EIS”). Functioning as a “lead\n\nagency,” FERC coordinates the required authorizations, including Virginia’s water\n\nquality certification under the CWA. See 15 U.S.C. § 717n(b).\n\n Because the pipeline project involves the discharge of fill and dredged materials\n\ninto waterways and wetlands, Atlantic needed to obtain not only a certificate of public\n\nconvenience and necessity from FERC, but also a Section 404 CWA authorization from\n\nthe U.S. Army Corps of Engineers (“Army Corps”). See 33 U.S.C. § 1344(a); AES\n\nSparrows Point LNG, LLC v. Wilson, 589 F.3d 721, 724 (4th Cir. 2009). The Army\n\nCorps provided the authorization necessary for the ACP through issuing Nationwide\n\nPermit 12, which covers “activities required for the construction, maintenance, repair,\n\nand removal of utilities lines and associated facilities in waters of the United States.” See\n\n33 U.S.C. 1344(e)(1) (allowing the Secretary of the Army to issue permits on a\n\n“nationwide basis for any category of activities involving discharges of dredged or fill\n\nmaterial if the Secretary determines that the activities in such category are similar in\n\n 5\n\fnature, will cause only minimal adverse environmental effects when performed\n\nseparately, and will have only minimal cumulative adverse effect on the environment”).\n\n\n\n III.\n\n Atlantic was also required to obtain a Section 401 Certification. The NGA allows\n\nstates to regulate the environmental impacts of pipelines under the CWA. Delaware\n\nRiverkeeper Network v. Secretary Pa. Dep’t of Envtl. Prot., 833 F.3d 360, 368 (3d Cir.\n\n2016) (citing 15 U.S.C. § 717b(d)). Virginia exercises this regulatory authority through\n\nthe Board. See Va. Code § 62.1-44.15. Pursuant to Virginia law, the Board wields broad\n\npowers regarding regulatory matters impacting water quality in Virginia, and Section 401\n\nCertifications fall under its authority. Id. The Virginia Department of Environmental\n\nQuality (“DEQ”) serves as the Board’s staff, and the Board may assign DEQ tasks and\n\ndelegate DEQ the authority to make decisions. See Va. Code Ann. § 62.1-44.14. We\n\nwill refer to the Board and DEQ together as “the State Agencies” when their actions are\n\nin concert.\n\n Under the Virginia Water Protection (“VWP”) Program, the Board, after soliciting\n\nand considering public comment and consulting with relevant agencies, may issue a\n\nVWP permit “if it has determined that the proposed activity is consistent with the\n\nprovisions of the Clean Water Act and the State Water Control Law and will protect in-\n\nstream beneficial uses.” Va. Code Ann. § 62.1-44.15:20(B). The Board may also certify\n\na nationwide Corps permit, such as Nationwide Permit 12, as meeting these requirements\n\nso long as the permit meets specified criteria. See 9 Va. Admin. Code 25-210-130(H).\n\n 6\n\fSpecifically, Section 401 states “[a]ny applicant for a Federal license or permit to conduct\n\nany activity . . . which may result in any discharge into the navigable waters” must seek\n\n“a certification from the State in which the discharge originates . . . that any such\n\ndischarge will comply with the applicable provisions” of the CWA. 33 U.S.C.\n\n§ 1341(a)(1). In addition, Section 401 states, “[n]o license or permit shall be granted if\n\ncertification has been denied by the State.” Id. If the state grants the Section 401\n\nCertification — whether with or without conditions — it must contain “[a] statement that\n\nthere is a reasonable assurance that the activity will be conducted in a manner which will\n\nnot violate applicable water quality standards.” 40 C.F.R. § 121.2(a)(3); see PUD No. 1\n\nof Jefferson Cty. v. Washington Dep’t of Ecology, 511 U.S. 700, 712 (1994). In addition,\n\nthe regulations allow for Virginia to consider activities that impact the upland areas that\n\nmay have the potential to affect water quality but do not fall under the scope of a VWP\n\npermit when the pipeline is over 36 inches inside diameter. Va. Code § 62.1-44.15:80.\n\n\n\n IV.\n\n Atlantic applied for the certificate of public convenience and necessity from FERC\n\nand Section 404 authorization from the Army Corps in September 2015. Atlantic filed an\n\namendment to its FERC certificate application in March 2016. In October 2017, FERC\n\nissued the certificate to Atlantic to construct and operate the pipeline. On April 7, 2017,\n\nthe DEQ issued a Section 401 Certification for the wetland, river, and streams crossings\n\nas covered in the Section 404 Nationwide Permit 12. In May 2017, the DEQ explained\n\nthat the Section 401 Certification for the Pipeline would entail two separate parts: (1) the\n\n 7\n\fcertification for the Army Corps Nationwide Permit 12, issued in April, applying to the\n\nPipeline’s wetland, river, and streams crossings (the “Wetlands and Streams\n\nCertification”), and (2) an additional Section 401 Certification review process to evaluate\n\nthe “upland” impacts of the Pipeline, terrestrial areas that are not covered by the Army\n\nCorps Permit (the “Upland Certification”). Specifically, the Upland Certification would\n\n“include all proposed upland activities associated with the construction, operation,\n\nmaintenance, and repair of the pipeline, any components thereof or appurtenances\n\nthereto, and related access roads and rights-of-way as well as certain project related\n\nsurface water withdrawals.” J.A 1083.\n\n On November 9, 2017, the DEQ recommended that the Board approve a Section\n\n401 Upland Certification of the project. On December 20, 2017, the Board issued the\n\nUpland Certification for the ACP with conditions. This Certification was distinct from\n\nthe Wetlands and Steams Certification. This Upland Certification provided that it “shall\n\nbe effective only following submission, review and final approval as required by law of\n\nthe Karst Mitigation Plan, Annual Standards and Specifications, and Erosion and\n\nSediment Control Plans and Storm Water Management Plans, and a report to the Board\n\nand the public by DEQ on the adequacy of these materials.” J.A. 29.\n\n Petitioners timely filed two petitions for review of the Certification on January 18,\n\n2018. The petitions were consolidated by court order on January 31, 2018. We possess\n\njurisdiction to review the Board’s Section 401 Upland Certification pursuant to 15 U.S.C.\n\n§ 717r(d)(1).\n\n\n\n 8\n\f The petitioners contend the Board’s issuance of the Section 401 Upland\n\nCertification was arbitrary and capricious and should be vacated for four reasons: (1) the\n\nState Agencies effectively invalidated their own finding of reasonable assurance when it\n\nvoted to reopen the comment period on the Section 401 Certification of the Army Corps\n\nof Engineers Nationwide Permit 12; (2) the State Agencies arbitrarily and capriciously\n\nfailed to assess the combined impacts on water quality that would result from multiple\n\nareas of construction activities within individual watershed areas; (3) the State Agencies\n\narbitrarily and capriciously failed to conduct an adequate antidegradation review; and (4)\n\nthe State Agencies arbitrarily and capriciously failed to ensure that the water quality in\n\nkarst geology regions would be protected. Respondents and intervenor in turn deny that\n\nthe State Agencies acted arbitrarily and capriciously and argue that the petitioners lack\n\nstanding to bring this petition.\n\n On April 12, 2018, the Board approved a second 30-day public comment period\n\nrelated to the Wetlands and Steams Certification. On August 21, 2018, the Board heard a\n\npresentation from the DEQ summarizing the public comment period and denied a motion\n\nto reevaluate this contested Certification.\n\n\n\n V.\n\n The respondents and intervenor argue as an initial matter that petitioners do not\n\nhave standing to litigate this petition for review. Spokeo, Inc. v. Robins, 136 S. Ct. 1540,\n\n1547 (2016) (quoting Lujan v. Defenders of Wildlife, 504 U.S. 555, 560-61 (1992))\n\n(Article III standing requires (1) an injury-in-fact (2) that is fairly traceable to the\n\n 9\n\fchallenged conduct of the defendant, and (3) that is likely to be redressed through a\n\nfavorable judicial decision). We disagree.\n\n This Court has previously rejected respondents’ and intervenor’s arguments on\n\nstanding. Sierra Club v. State Water Control Bd., 898 F.3d 383, 400-02 (4th Cir. 2018).\n\nPetitioners have established an injury-in-fact even though the State Agencies could\n\nchoose to waive certification. We have previously held that the denial of an opportunity,\n\nin this case, to have the project vetoed or have additional restrictions can constitute an\n\ninjury-in-fact. Id. at 401. In addition, petitioners successfully establish traceability and\n\nredressability given that we could vacate the Board’s decision and determine that its\n\ndecision was not based on a reasonable assurance and instead was arbitrary and\n\ncapricious. Petitioners’ injuries could be remedied if the Board required Atlantic to take\n\nadditional measures that would address petitioners’ grievances. In our previous decision\n\nwe held petitioners established traceability and redressability in this very context. Id.\n\nPetitioners have demonstrated the requirements for standing.\n\n\n\n VI.\n\n We review Virginia’s Section 401 Certification under the standards set forth in the\n\nAdministrative Procedures Act (“APA”). See AES Sparrows Point LNG, LLC v. Wilson,\n\n589 F.3d 721, 727 (4th Cir. 2009). 1 This Court applies the arbitrary and capricious\n\n\n 1\n Asserting that the APA is not applicable to actions by State Agencies,\nrespondents argue that Va. Code § 2.2-4027 establishes the applicable standard of review.\nThat statute provides that issues of fact shall be decided based on “whether there was\n(Continued)\n 10\n\fstandard of the APA to the State Agencies’ challenged findings and conclusions. Sierra\n\nClub, 898 F.3d at 403.\n\n To survive review under the arbitrary and capricious standard, an agency decision\n\nmust show that the agency examined “the relevant data and articulate[d] a satisfactory\n\nexplanation for its action including a ‘rational connection between the facts found and the\n\nchoice made.’” Motor Vehicle Mfrs. Ass’n of U.S., Inc. v. State Farm Mut. Auto Ins. Co.,\n\n463 U.S. 29, 43 (1983) (quoting Burlington Truck Lines v. United States, 371 U.S. 156,\n\n168 (1962)).\n\n Agency action is arbitrary and capricious if the agency relies on factors that\n Congress did not intend for it to consider, entirely ignores important aspects\n of the problem, explains its decision in a manner contrary to the evidence\n before it, or reaches a decision that is so implausible that it cannot be\n ascribed to a difference in view.\n\nBedford Cty. Mem’l Hosp. v. Health & Human Servs., 769 F.2d 1017, 1022 (4th Cir.\n\n1985) (citing Motor Vehicle Mfrs. Ass’n, 463 U.S. at 43). This Circuit has held that\n\n [r]eview under this standard is highly deferential, with a presumption in\n favor of finding the agency action valid. Especially in matters involving\n not just simple findings of fact but complex predictions based on special\n expertise, a reviewing court must generally be at its most deferential. In\n determining whether agency action was arbitrary or capricious, the court\n must consider whether the agency considered the relevant factors and\n whether a clear error of judgment was made. Although this inquiry into the\n facts is to be searching and careful, the ultimate standard of review is a\n narrow one. The court is not empowered to substitute its judgment for that\n of the agency. Deference is due where the agency has examined the\n\n\n\n\nsubstantial evidence in the agency record to support the agency decision.” As we did in\nSierra Club, we decline to resolve this issue because petitioners’ claims fail even under\nthe substantial evidence standard. 898 F.3d at 403 n.13.\n\n 11\n\f relevant data and provided an explanation of its decision that includes a\n rational connection between the facts found and the choice made.\n\nOhio Valley Envtl. Coal. v. Aracoma Coal Co., 556 F.3d 177, 192 (4th Cir. 2009)\n\n(internal quotation marks and citations omitted). Nonetheless, if a state agency’s Section\n\n401 certification is found to be arbitrary and capricious, the Court must vacate the\n\ncertification. 5 U.S.C. § 706(2)(A).\n\n\n\n VII.\n\n A.\n\n Turning to petitioners’ first argument, we hold that the decision to reopen the\n\ncomment period did not render the State Agencies’ Section 401 Upland Certification\n\narbitrary and capricious. The comment period was re-opened for the Wetlands and\n\nStreams Certification and not the Upland Certification at issue in this case. In any event,\n\nthe Wetlands and Streams Certification was not ultimately revoked.\n\n B.\n\n Moving to the petitioners’ second argument, we conclude that the State Agencies’\n\ndecision not to conduct a combined effect analysis does not render their issuance of a\n\nSection 401 Upland Certification arbitrary and capricious for three reasons.\n\n First, the Section 401 Upland Certification in question deals with project-related\n\nactivities taking place in upland areas. The Upland Certification supplemented the FERC\n\ncertificate and the prior Wetland and Streams Certification of the Army Corps’\n\nNationwide Permit 12 regarding waterways and utility line crossings. As the State\n\n\n 12\n\fAgencies explained, “the conditions in the proposed additional 401 Certification are in\n\naddition to any other Federal or State permit or regulatory requirements including the\n\nexpressed conditions imposed by FERC.” J.A. 1059. The Upland Certification in\n\nquestion is not designed to function as a stand-alone document, comprehensively\n\ncovering all pieces of relevant data and potentialities. For example, record evidence\n\navailable to the State Agencies explains, “while the impacts to jurisdictional waters\n\nauthorized by the Corps under Section 404 of the Clean Water Act are separate from\n\nupland activities that are the subject of this Certification, the Corps also analyzed the\n\ncumulative effects of linear utility projects and found that the individual and cumulative\n\nadverse effects on the aquatic environment resulting from the activities authorized by the\n\nNationwide Permit 12 will be no more than minimal and each crossing is a single and\n\ncomplete project.” J.A. 999. The Army Corps examined cumulative impacts, and it\n\nwould be redundant and inefficient for the State Agencies to duplicate these efforts. The\n\nUpland Certification works in conjunction with other regulatory tools and cannot be\n\njudged in a void, and it supplements other pieces of the regulatory framework. It is not\n\nrequired to cover combined effect analysis because other parts of the regulatory process\n\nsufficiently address that subject matter. The State Agencies in the current appeal used\n\ntheir resources to issue the Upland Certification to fill an information gap regarding the\n\nimpact of upland activities, which were not typically covered under prior CWA\n\ncertifications. The State Agencies properly made a unique contribution instead of\n\nduplicating the efforts of other regulatory bodies as petitioners’ request. See Sierra Club,\n\n898 F.3d at 407.\n\n 13\n\f Second, State Agencies have broad discretion when developing the criteria for\n\ntheir Section 401 Certification. The only requirement imposed by the regulations is that\n\nStates must establish procedures for public notice when there are applications for\n\ncertification, and to the extent deemed appropriate, procedures for public hearings in\n\nconnection with specific applications. 33 U.S.C. § 1341(a)(1). Nonetheless, nothing in\n\nSection 401 restricts states to a single certificate proceeding, and Section 401 does not\n\nrequire states to undertake a single cumulative review of all possible impacts in a single\n\ncertification.\n\n Petitioners’ rely on two federal regulations in arguing that a cumulative review is\n\nrequired, 40 C.F.R. § 230.7(a) and 40 C.F.R. § 230.11(g)(1), but those regulations impose\n\nduties—including a duty to make factual determinations and consider cumulative\n\neffects—on the Army Corps under Section 404, not on states under Section 401.\n\nMoreover, petitioners contend that two cases require State Agencies to take into account\n\ncombined effects lest their decisions be rendered arbitrary and capricious. See Klamath-\n\nSiskiyou Wildlands Ctr. v. BLM, 387 F.3d 989, 993 (9th Cir. 2004); Idaho Rivers United\n\nv. Probert, Case No.: 3:16-102, 2016 U.S. Dist. LEXIS 63767, at *32-34. Furthermore,\n\npetitioners invoke the Supreme Court’s decision in Motor Vehicles Manufacturers\n\nAssociation v. State Farm Mutual Automobile Ins. Co., to argue that all “relevant data”\n\nmust be considered. 463 U.S. 29, 43 (1983). We conclude, however, that both the\n\nKlamath-Siskiyou Wildlands and Idaho Rivers United cases are distinguishable and\n\nunpersuasive because in those cases the Bureau of Land Management and the Forest\n\nService, respectively, faced violations under NEPA, not the CWA. Klamath-Siskiyou\n\n 14\n\fWildlands Ctr., 387 F.3d at 993–94; Idaho Rivers United, 2016 U.S. Dist. LEXIS 63767,\n\nat *33. Unlike the CWA, NEPA requires a cumulative effects analysis, and thus cases\n\ndecided under NEPA are not dispositive authority here. Furthermore, Motor Vehicle\n\nManufacturers Association, which deals with the National Highway Traffic Safety\n\nAdministration, does not mention cumulative effects or the CWA, and thus the case does\n\nnot stand for the proposition that the CWA should be broadened to encompass a\n\ncombined impact analysis.\n\n Finally, the State Agencies’ failure to explicitly consider the combined effects of\n\nmultiple areas of construction within individual watersheds such as the Chesapeake Bay\n\nwatershed and the Chesapeake Bay Total Maximum Daily Load (“Bay TMDL”) did not\n\nrender their decision arbitrary and capricious. 2 As an initial matter, despite petitioners’\n\npreferences, there are no express regulations that require the State Agencies to consider\n\nthe combined effects of individual watersheds. In addition, the Ninth Circuit has\n\nexplained that TMDLs like the Chesapeake Bay TMDL are “primarily informational\n\ntools that allow states to proceed from the identification of water requiring additional\n\nplanning to the required plans.” Pronsolino v. Nastri, 291 F. 3d 1123, 1129 (9th Cir.\n\n2002). Moreover, TMDLs do not give rise to an independent legal obligation.\n\nPronsolino, 291 F.3d 1123, 1140. Consequently, the Chesapeake TMDL does not\n\nconstitute a regulatory mandate that the State Agencies were required to address before\n\nissuing the Section 401 Upland Certification. Furthermore, protection measures for the\n\n 2\n The Bay TMDL is a federal-state partnership that monitors the water quality\nstandards in the Chesapeake Bay and its related tributaries. J.A. 888.\n\n 15\n\fChesapeake Bay TMDL are offered through other tools such as the FERC EIS and the\n\nStorm Water Prevention Plan. J.A. 664-665; 1138-1140.\n\n The State Agencies more than satisfied their obligations by reviewing upland\n\nactivities as well as stream and wetland crossings. The Board’s decisions are not\n\nrendered arbitrary and capricious because it did not conduct an independent review of the\n\ncumulative effects on water quality within individual watersheds, even if this was\n\npetitioners’ preference. To deem an agency action arbitrary and capricious their decision\n\nmust be “so implausible that it could not be ascribed to a difference in view or the\n\nproduct of agency expertise.” State Farm Mut. Auto. Ins. Co., 463 U.S. at 43. The lack\n\nof an explicit combined effect analysis in the Section 401 Upland Certification does not\n\nrise to this level, especially given that there are other regulatory tools that were utilized to\n\nconsider those impacts.\n\n C.\n\n 1.\n\n Turning to petitioners’ third argument, we do not find that the State Agencies’\n\nreasonable assurance determination to be arbitrary and capricious simply because they\n\nrelied on existing Virginia water quality standards and regulations to effectively address\n\nconcerns regarding water quality deterioration.\n\n Under the CWA, “states have the primary role in promulgating water quality\n\nstandards.” Piney Run Preservation Ass’n v. County Comm’rs of Carroll Cty., 268 F.3d\n\n255, 265 n.9 (4th Cir. 2001). States must initially classify the uses for which their water\n\nis to be protected and then determine the necessary level of water quality for their\n\n 16\n\fpreferred uses. See NRDC v. EPA, 16 F.3d 1395, 1400 (4th Cir. 1993). Virginia’s water-\n\nquality policy is relevant in two respects: its narrative water-quality criterion and its anti-\n\ndegradation policy.\n\n Virginia’s water-quality criterion mandates that “State waters . . . shall be free\n\nfrom substances attributable to . . . waste in concentrations, amounts, or combinations\n\nwhich contravene established standards or interfere directly or indirectly with designated\n\nuses of such water or which are inimical or harmful to human, animal, plant, or aquatic\n\nlife.” 9 Va. Admin. Code § 25-260-20(A). The regulation explains that any substance\n\n“that produce[s] . . . turbidity” is a substance to be controlled. Id. The regulation\n\nprovides examples of “turbidity” such as floating debris, oil, and other materials that are\n\nsuspended solids in a body of water.\n\n In addition, Virginia’s antidegradation policy shall be applied whenever any\n\nactivity is proposed that has the potential to affect existing surface water quality. 9 Va.\n\nAdmin. Code § 25-260-30(A). The antidegradation policy classifies Virginia’s water into\n\nthree tiers and provides differing levels of protection based on the water’s tier. See 9 Va.\n\nAdmin. Code § 25-260-30(A).\n\n The Policy defines Tier 3 waters as “exceptional”; these waters “shall be\n\nmaintained and protected to prevent permanent or long-term degradation or impairment.”\n\n9 Va. Admin. Code § 25-260-30(A)(3)(b)(1). The policy specifically provides that “[n]o\n\nnew, additional, or increased discharge of sewage, industrial wastes or other pollution\n\ninto [Tier 3 waters] shall be allowed.” 9 Va. Admin. Code § 25-260-30(A)(3)(b)(2).\n\nNonetheless, “[a]ctivities causing temporary sources of pollution may be allowed in [Tier\n\n 17\n\f3 waters] even if degradation may be expected to temporarily occur provided that after a\n\nminimal period of time the waters are returned or restored to conditions equal to or better\n\nthan those existing just prior to the temporary source of pollution.” 9 Va. Admin. Code\n\n§ 25-260-30(A)(3)(b)(3).\n\n The Policy defines Tier 2 waters as those that “exceed water quality standards.” 9\n\nVa. Admin. Code § 25-260-30(A)(2). The protection for these waters and their quality\n\nare lower and the regulation states that the quality of Tier 2 waters “shall be maintained\n\nand protected unless the board finds . . . that allowing lower water quality is necessary to\n\naccommodate important economic or social development in the area in which the waters\n\nare located.” 9 Va. Admin. Code § 25-260-30(A)(2).\n\n Last, Tier 1 waters constitute all Virginia waters that are not designated Tier 2 or\n\nTier 3. The regulation classifying the level of protection for these waters’ states,\n\n“existing in-stream water uses and the level of water quality necessary to protect the\n\nexisting uses shall be maintained and protected.” 9 Va. Admin. Code § 25-260-30(A)(1).\n\n In Virginia a project may be permitted under a Construction General Permit. 9\n\nVa. Admin. Code § 25-880-70 Part II. The Construction General Permit incorporates the\n\nrequirements of two other state laws, the Virginia Storm Water Management (“VSM”)\n\nLaw, Va. Code § 62.1-44.15:24 et seq., and the Virginia Erosion and Sediment Control\n\n(“VESC”) Law, Va. Code § 62.1-44.15:51, et seq.\n\n The CWA has an exemption for natural gas pipeline construction projects and\n\ntherefore Virginia’s regulatory scheme diverges from the federal environmental\n\nprotections. See 33 U.S.C. § 1342(I)(2). Consequently, Virginia still regulates natural\n\n 18\n\fgas pipeline projects through its Annual Standards and Specifications (“AS&S”)\n\nProgram. See Va. Code § 62.1-44.15:55(D). The AS&S program requires a project\n\ndeveloper to submit annual standards and specifications for DEQ’s review and approval.\n\nSee 9 Va. Admin. Code § 25-870-170(A). Through this program Virginia ensures that\n\nprojects will meet the same requirements imposed on other projects subject to the\n\nVirginia Construction General Permit. See 9 Va. Admin. Code § 25-870-170(A).\n\nNonetheless, once DEQ approves a developer’s annual standards and specifications as\n\nsatisfying the requirements of the VSM and VESC, the entity generally need not submit\n\nsite-specific VSM and VESC plans to DEQ for approval. See Va. Code § 62.1-\n\n44.15:55(D). This allows the projects to become more self-regulating.\n\n Typically, ensuring an activity’s compliance with water quality standards requires\n\nan antidegradation review. See Nat. Res. Def. Council, Inc. v. EPA, 16 F.3d 1395, 1400\n\n(4th Cir. 1993); see also 40 C.F.R. § 131.12 (requiring states to develop and adopt a\n\nstatewide antidegradation policy). The CWA’s antidegradation policy requires that state\n\nstandards be “sufficient to maintain existing beneficial uses of navigable waters,\n\npreventing further degradation.” 33 U.S.C. § 1313(d). State antidegradation policies\n\nmust be consistent with 40 C.F.R. § 131.12(a), and must protect existing uses, maintain\n\nthe existing quality of high-quality waters unless degradation is justified by important\n\nsocioeconomic development, and prohibit degradation of national resource waters. Id.\n\n§ 131.12(a).\n\n\n\n\n 19\n\f 2.\n\n We do not find that the State Agencies’ failure to conduct a separate\n\nantidegradation review before issuing its Upland Certification renders their decision\n\narbitrary and capricious for two reasons.\n\n First, in Virginia, the AS&S program requires a project developer to submit annual\n\nstandards and specifications for DEQ’s review and approval, thereby ensuring that\n\nprojects will meet the same requirements that would apply were they covered by the\n\nVirginia Construction General Permit. See 9 Va. Admin. Code § 25-870-170(A). The\n\nAS&S also incorporate all the requirements of EPA’s Construction General Permit. J.A.\n\n1124-1125. The AS&S in this case were developed over eighteen months and represent a\n\nthorough process of development, revision and refinement to ensure that the ACP meet\n\nthe technical and legal requirements for Virginia. J.A. 1087. Both federal and state\n\nregulators have concluded that application of technical requirements like those in the\n\nAS&S “will not result in a lowering of water quality,” which renders the individualized\n\nreview the petitioners suggest “unnecessary.” J.A. 11. There is no indication that these\n\nAS&S fail to protect water quality in Virginia. To the contrary, these regulations have\n\nbeen found as a matter of law to protect water quality in Virginia. See Kelble v.\n\nCommonwealth, Case No. CL 14-762, at 4-5 (Richmond Cir. Ct. Apr. 10, 2017).\n\n Second, State Agencies did not have to conduct a separate antidegradation review\n\nbecause the impact on sediment on the water would only be temporary. Under FERC’s\n\nfinal EIS, it was determined that any water quality impacts stemming from construction\n\nwould be temporary. J.A. 623. Even with respect to Tier 3 waters, the policy states that\n\n 20\n\f“[a]ctivities causing temporary sources of pollution may be allowed in [Tier 3] waters . . .\n\neven if degradation may be expected to occur provided that after a minimal period of\n\ntime the waters are returned or restored to conditions equal to or better that those existing\n\njust prior to the temporary source of pollution.” 9 Va. Admin. Code 25-260-\n\n30A(3)(b)(3). Even in the most protected state waters, Virginia does not consider\n\ntemporary sources of pollution, such as the construction of the ACP, to violate\n\nantidegradation policies.\n\n Thus, nothing was arbitrary and capricious about the State Agencies’ decision not\n\nto conduct a separate antidegradation review.\n\n D.\n\n Turning to the final challenge raised by petitioners, we find that the State\n\nAgencies’ treatment of karst terrain was not arbitrary or capricious because of the\n\nconditions imposed on the Section 401 Upland Certification.\n\n Karst geology refers to geological formations of soluble limestone bedrock that\n\ncreates underground water flow systems where the rocks have dissolved and created\n\nsinkholes, caves and underground springs and rivers. J.A. 669. The constitution of these\n\nareas presents additional environmental considerations for pipeline construction\n\nincluding, sinkhole collapse, sinkhole flooding and associated groundwater\n\ncontamination. J.A. 904-905.\n\n The record demonstrates that the State Agencies took petitioners’ concerns\n\nregarding karst geology into consideration. J.A. 31. Virginia’s Section 401 Upland\n\nCertification contains five specific requirements concerning the protection of karst\n\n 21\n\fterrain. J.A. 31-32. First, Atlantic must provide the State an addendum to a 51-page\n\nKarst Survey Report prior to any land disturbing activities. J.A. 212-237; J.A. 31.\n\nSecond, Atlantic must follow the Karst Terrain Assessment, Construction, Monitoring,\n\nand Mitigation Plan. J.A. 31. This plan allows for route adjustments to avoid karst\n\nterrain. J.A. 1001. Third, based on the conditions in the Section 401 Upland\n\nCertification, Atlantic must conduct contingency planning in order to address any\n\naccidental spills or releases during construction on karst terrain. Fourth, water surveys\n\nregarding drinkable water in karst regions are required under the Section 401 Upland\n\nCertification. J.A. 31. Finally, Atlantic has a liability of five million dollars to cover the\n\ncost of any impacts to private water supplies, which encompasses karst regions. J.A. 32.\n\n Reliance on these conditions, even the prospective ones, does not render the State\n\nAgencies’ issuance of the Section 401 Upland Certification arbitrary and capricious. See\n\nPort of Seattle v. Pollution Control Hearings Bd., 90 P.3d 659, 677 (Wash. 2004)\n\n(holding regulators did not act arbitrarily or capriciously by basing reasonable assurance\n\n“on future submissions of revised plans, reports, and studies, so long as their\n\nimplementation and anticipated outcome meet the reasonable assurance test”).\n\n Moreover, the mere existence of risk to karst geology does not render the State\n\nAgencies’ decision to issue the Section 401 Upland Certification arbitrary and capricious.\n\nBased on the information in the record, this Court finds that the State Agencies had\n\nreasonable assurance that karst regions would be protected given the conditions imposed\n\non the Section 401 Upland Certification. We “see no purpose we would serve by\n\nstepping in and second-guessing the analytical methods Virginia deemed appropriate to\n\n 22\n\fprovide it with reasonable assurance that its water quality would be protected.” Sierra\n\nClub., 898 F.3d at 407.\n\n\n\n VIII.\n\n Governmental agencies can always take additional steps to increase the protection\n\nof the environment. But that is not the applicable legal standard this Court utilizes when\n\nreviewing a state agency’s issuance of a Section 401 Certification. We must determine\n\n“whether the agency considered the relevant factors and whether a clear error of\n\njudgment was made.” Ohio Valley Envtl. Coal., 556 F.3d 177, 192. There is no\n\nindication that the State Agencies did not consider relevant factors or that they clearly\n\nmade an error of judgment. In conclusion, because we find that the State Agencies did\n\nnot act arbitrarily and capriciously in issuing the Section 401 Upland Certification, we\n\ndeny the petition for review.\n\n\n\n PETITION FOR REVIEW DENIED\n\n\n\n\n 23\n[END_CASE]", "role": "user" } ]
4,582,070
John S. BENNETT, Plaintiff - Appellant, v. James GARNER; Virtus Consulting, LLC, Defendants - Appellees.
John Bennett v. James Garner
2019-01-16
18-1531
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Keenan, Floyd, Thacker", "parties": "", "opinions": [{"author": "BARBARA MILANO KEENAN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1531\n\n\nJOHN S. BENNETT,\n\n Plaintiff - Appellant,\n\n v.\n\nJAMES GARNER; VIRTUS CONSULTING, LLC,\n\n Defendants - Appellees.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:17-cv-00574-CMH-TCB)\n\n\nArgued: December 13, 2018 Decided: January 16, 2019\n\n\nBefore KEENAN, FLOYD, and THACKER, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Keenan wrote the opinion, in which\nJudge Floyd and Judge Thacker joined.\n\n\nARGUED: Kevin M. O’Donnell, HENRY & O’DONNELL, PC, Alexandria, Virginia,\nfor Appellant. Thomas Wayne Biggs II, DYCIO & BIGGS, Fairfax, Virginia, for\nAppellees. ON BRIEF: Jeffery T. Martin, Jr., HENRY & O’DONNELL, PC,\nAlexandria, Virginia, for Appellant. Daniel F. Izzo, DYCIO & BIGGS, Fairfax,\nVirginia, for Appellees.\n\fBARBARA MILANO KEENAN, Circuit Judge:\n\n John S. Bennett appeals from the district court’s award of summary judgment in\n\nfavor of his former employer, Virtus Consulting, LLC (Virtus), and its owner, James\n\nGarner (collectively, the defendants), in Bennett’s action seeking to collect on a state\n\ncourt judgment entered against the defendants. The district court held that Bennett’s\n\nclaims were precluded under Virginia’s doctrine of res judicata.\n\n Upon our review, we conclude that Bennett’s claims are not precluded, because\n\nBennett could not have brought those claims at the time of his earlier litigation.\n\nAccordingly, we vacate the district court’s judgment and remand for further proceedings.\n\n\n\n I.\n\n We present the facts in the light most favorable to Bennett, the nonmoving party,\n\nand draw all reasonable inferences in his favor. Rosetta Stone Ltd. v. Google, Inc., 676\n\nF.3d 144, 150 (4th Cir. 2012) (citation omitted). Virtus is a Virginia limited liability\n\ncompany that provides consulting services to various financial institutions. Garner is the\n\nowner and sole member of Virtus. Bennett was employed by Virtus and worked as the\n\nprincipal contact for one of Virtus’ largest clients.\n\n In 2012, Garner began negotiations to sell Virtus’ assets to the Solomon Edwards\n\nGroup (SEG). Around the same time, the defendants and Bennett signed an agreement,\n\nin which Bennett agreed to assist in the sale in exchange for “sharing [in the] proceeds”\n\nfrom the sale (the Bennett Agreement). Under the Bennett Agreement, once the sale to\n\nSEG successfully closed, Bennett would receive a fixed cash payment made in quarterly\n\n 2\n\finstallments. The parties also agreed that Bennett potentially could receive two annual\n\n“earn out” payments, depending on whether SEG and Garner achieved certain revenue\n\ntargets in the two years following the sale.\n\n The sale of Virtus’ assets to SEG successfully closed around the end of September\n\n2012. In accordance with the Bennett Agreement, Garner made the first two quarterly\n\ninstallment payments to Bennett. But, in April 2013, the defendants ceased making any\n\nfurther payments, claiming that Bennett had breached his obligations under the\n\nagreement. Bennett, however, maintained that he was entitled to the remaining\n\ninstallment payments and the “earn out” payments.\n\n The parties submitted their dispute to an arbitrator as required by the arbitration\n\nclause in the Bennett Agreement. During the arbitration proceedings, the defendants\n\nprovided Bennett documents describing the structure of the SEG sale but did not produce\n\nany of Virtus’ financial records or bank statements. In response to a request seeking\n\nthose financial records, the defendants stipulated that the Bennett Agreement was\n\nproperly executed and that the performance metrics triggering the “earn out” payments\n\nhad been “met in full.”\n\n In September 2014, the arbitrator ordered Virtus to pay Bennett $387,500. Under\n\nthe terms of the Bennett Agreement, the arbitrator held Garner jointly and severally liable\n\nfor $125,000 of that award. The award was confirmed by a Virginia circuit court and\n\nreduced to a judgment. Although Garner paid the portion of the award for which he\n\npersonally was liable, Virtus failed to pay the remaining $262,500.\n\n\n\n 3\n\f After the arbitration award was confirmed, Bennett obtained Virtus’ bank\n\nstatements. These statements showed that shortly before the SEG sale closed, Garner had\n\ntransferred substantially all of Virtus’ cash reserves to himself. Further, Bennett learned\n\nthat the SEG sale had been structured to divert all cash and other consideration from the\n\nsale to Garner personally. For instance, equity stock in SEG that was supposed to\n\ntransfer to Virtus as part of the sale was instead listed in Garner’s name and reported as\n\npart of Garner’s personal tax returns. Thus, Virtus lacked sufficient assets to satisfy\n\nBennett’s judgment.\n\n In May 2017, Bennett initiated the present action in the district court seeking to\n\ncollect on his judgment. He asserted four claims against the defendants: (1) fraudulent\n\nconveyance, in violation of Virginia Code § 55-80; (2) voluntary transfer, in violation of\n\nVirginia Code § 55-81 (together, the fraudulent transfer claims); (3) a claim seeking to\n\n“pierce the corporate veil” and recover the judgment amount directly from Garner (the\n\nalter-ego claim); and (4) fraud in the inducement. The district court granted the\n\ndefendants’ motion for summary judgment, concluding that Bennett’s fraudulent transfer\n\nclaims and alter-ego claim were precluded under Virginia’s doctrine of res judicata. 1\n\nThis appeal followed.\n\n\n\n\n 1\n The district court also awarded the defendants summary judgment on Bennett’s\nfraud in the inducement claim, concluding that it was barred by the two-year statute of\nlimitations governing fraud claims, Va. Code § 8.01-243(A). Bennett does not contest\nthe dismissal of the fraud in the inducement claim.\n\n\n 4\n\f II.\n\n We review de novo the district court’s award of summary judgment. Rosetta\n\nStone Ltd., 676 F.3d at 150.\n\n A.\n\n Before addressing the parties’ arguments, we begin by reviewing the applicable\n\nprinciples of res judicata. In considering the preclusive effect of an earlier state court\n\njudgment on a new claim, we apply the “preclusion law of the State in which judgment\n\nwas rendered.” In re Genesys Data Techs., Inc., 204 F.3d 124, 127 (4th Cir. 2000)\n\n(quoting Marrese v. Am. Acad. of Orthopedic Surgeons, 470 U.S. 373, 380 (1985)).\n\nHere, the arbitration award was confirmed and reduced to a judgment by a Virginia court.\n\nWe therefore apply Virginia’s principles of res judicata.\n\n In Virginia, res judicata 2 is governed by Rule 1:6 of the Rules of the Supreme\n\nCourt of Virginia, which states in relevant part:\n\n A party whose claim for relief arising from identified conduct, a\n transaction, or an occurrence, is decided on the merits by a final judgment,\n shall be forever barred from prosecuting any second or subsequent civil\n action against the same opposing party or parties on any claim or cause of\n action that arises from that same conduct, transaction or occurrence,\n whether or not the legal theory or rights asserted in the second or\n subsequent action were raised in the prior lawsuit, and regardless of the\n legal elements or the evidence upon which any claims in the prior\n proceeding depended, or the particular remedies sought.\n\n\n\n\n 2\n Although Virginia’s res judicata doctrine encompasses both claim preclusion and\nissue preclusion, here we use the term “res judicata” to refer to claim preclusion only.\nSee Funny Guy, LLC v. Lecego, LLC, 795 S.E.2d 887, 890 (Va. 2017).\n\n 5\n\fVa. Sup. Ct. R. 1:6(a). Under this rule, “a final judgment forecloses ‘successive litigation\n\nof the very same claim, whether or not relitigation of the claim raises the same issues as\n\nthe earlier suit.’” Lee v. Spoden, 776 S.E.2d 798, 803 (Va. 2015) (quoting Taylor v.\n\nSturgell, 553 U.S. 880, 892 (2008)). Parties, therefore, may not relitigate “the same\n\ncause of action or any part thereof which could have been litigated in the previous\n\naction.” D’Ambrosio v. Wolf, 809 S.E.2d 625, 628 (Va. 2018) (citation omitted). Stated\n\nsimply, res judicata operates to prevent a party from getting a “second bite of the apple”\n\nwith respect to wrongs arising from a single dispute. See Funny Guy, LLC v. Lecego,\n\nLLC, 795 S.E.2d 887, 890 (Va. 2017) (“The law should afford one full, fair hearing\n\nrelating to a particular problem—but not two.” (citation omitted)).\n\n While ostensibly a broad proposition, res judicata nonetheless is limited by\n\nlongstanding principles. For instance, claims brought solely to execute on a judgment are\n\ngenerally not precluded by prior litigation that resulted in that judgment. See State Farm\n\nMut. Auto. Ins. Co. v. Kelly, 380 S.E.2d 654, 655 n.2 (Va. 1989); see also Restatement 2d\n\nJudgments § 18(c). Similarly, res judicata does “not bar a claim that does not accrue\n\nprior to the litigation triggering the bar.” Funny Guy, 795 S.E.2d at 900 (emphasis\n\nadded). A party is not precluded from bringing a claim that he was unable to bring in the\n\ninitial litigation, regardless whether that claim constitutes part of the same “conduct,\n\ntransaction, or occurrence.” D’Ambrosio, 809 S.E.2d at 628; Funny Guy, 795 S.E.2d at\n\n890 (“Determining which claims should have been brought in earlier litigation largely\n\ndepends on which claims could have been brought.” (citation omitted)); see also Lawlor\n\nv. Nat’l Screen Serv. Corp., 349 U.S. 322, 328 (1955) (explaining that although an earlier\n\n 6\n\fjudgment “precludes recovery on claims arising prior to its entry, it cannot be given the\n\neffect of extinguishing claims which did not even then exist”). With these principles in\n\nmind, we turn to consider the parties’ arguments.\n\n B.\n\n As the parties asserting res judicata, the defendants bear the burden of showing\n\nthat it is more likely than not that Bennett’s claims should be precluded by the prior\n\njudgment. D’Ambrosio, 809 S.E.2d at 628. The defendants argue, as they did in the\n\ndistrict court, that because Bennett had knowledge of the structure of the SEG sale at the\n\ntime of the arbitration, Bennett could have raised both his fraudulent transfer and alter-\n\nego claims during those proceedings. Accordingly, the defendants contend that under\n\nVirginia’s doctrine of res judicata, Bennett must have brought those claims during the\n\narbitration proceedings.\n\n In response, Bennett generally maintains that his claims are brought solely in\n\nexecution of his state court judgment. That is, instead of seeking to “relitigate” the\n\ndefendants’ liability under the Bennett Agreement, Bennett argues that his fraudulent\n\ntransfer claims were an attempt to collect on the judgment he is owed and could not have\n\nbeen brought before the judgment was entered. With respect to his alter-ego claim,\n\nBennett similarly argues that he could not have maintained that claim before obtaining\n\nthe judgment against Virtus. We agree with Bennett and address each argument in turn.\n\n 1.\n\n We begin by considering the question whether Bennett could have raised his\n\nfraudulent transfer claims during the arbitration proceedings. Actions brought under\n\n 7\n\fVirginia’s fraudulent conveyance statute, Va. Code § 55-80, and the state’s voluntary\n\ntransfer statute, Va. Code § 55-81, assist creditors in collecting on a judgment or other\n\ndebt. See La Bella Dona Skin Care, Inc. v. Belle Femme Enters., LLC, 805 S.E.2d 399,\n\n406 (Va. 2017); Balzer & Assocs., Inc. v. The Lakes on 360, Inc., 463 S.E.2d 453, 455-56\n\n(Va. 1995). Such actions do not impose liability on the participants in a fraudulent\n\nconveyance, but merely unwind “transactions designed to place a debtor’s assets beyond\n\nhis creditors’ reach.” La Bella Dona, 805 S.E.2d at 404, 406; see also Mills v. Miller\n\nHarness Co., 326 S.E.2d 665, 667 (Va. 1985) (concluding that Virginia Code § 55-80\n\ndoes not authorize a court “to award an in personam judgment when a fraudulent\n\nconveyance is set aside”). Indeed, Virginia law expressly permits actions under both\n\nSections 55-80 and 55-81 to be brought after the entry of a judgment. Va. Code § 55-\n\n82.2 (“The court shall have the authority to set aside a fraudulent conveyance or\n\nvoluntary transfer pursuant to § 55-80 or § 55-81 during an action brought by a creditor\n\nto execute on a judgment.” (emphasis added)). Thus, actions to void wrongful transfers\n\nare remedies designed to “return[] the fraudulently conveyed assets to the transferor.” La\n\nBella Dona, 805 S.E.2d at 406.\n\n In the present case, the disputes that the parties submitted to arbitration focused on\n\nthe issue whether Bennett was entitled to receive the remaining payments under the\n\nBennett Agreement. Thus, the arbitration served only to establish the parties’ respective\n\nobligations and liability under the Bennett Agreement.\n\n In contrast, Bennett’s fraudulent transfer claims allege that Virtus depleted its\n\ncorporate assets and made improper conveyances to Garner to prevent Bennett from\n\n 8\n\fcollecting on the arbitration award and judgment. Bennett does not advance any new\n\nlegal “theories of recovery” on which either defendant could be held liable under the\n\nBennett Agreement. Cf. Funny Guy, 795 S.E.2d at 897-98 (holding that, under principles\n\nof res judicata, “alternative theories of recovery” cannot be raised in consecutive\n\nlawsuits). Nor does he seek damages beyond the outstanding $262,500 judgment, the\n\nprecise amount awarded in arbitration. Although the alleged wrongful transfers took\n\nplace around the same time as the SEG sale, those transfers were immaterial to the\n\nquestion whether either Bennett or the defendants had breached the Bennett Agreement.\n\nThus, Bennett is not seeking a “second bite of the apple” with respect to the amount he is\n\nowed. See id. Rather, he seeks only to unwind the allegedly improper transfers from\n\nVirtus to Garner so that Virtus can satisfy the existing judgment. 3\n\n Furthermore, we observe that had Bennett claimed that the defendants were\n\nattempting to defraud him by transferring assets, before he proved that he was entitled to\n\npayments under the Bennett Agreement, those fraudulent transfer claims would have\n\nbeen premature. At the time of the arbitration proceedings, Bennett did not have\n\n\n 3\n The defendants incorrectly rely on the Supreme Court of Virginia’s decision in\nPrice v. Hawkins, 439 S.E.2d 382 (Va. 1994), to argue that Bennett’s fraudulent\nconveyance claim under Virginia Code § 55-80 is meant to impose liability on Garner. In\nPrice, the court allowed an in personam judgment to be awarded against recipients of\nfraudulent transfers when the wrongfully transferred property was only cash. Id. at 385.\nThis narrowly crafted exception was designed to prevent a defrauded creditor from being\nleft without a remedy, because cash “cannot be easily located for attachment or levy.” La\nBella Dona, 805 S.E.2d at 406 (describing the exception in Price). However, the\nSupreme Court of Virginia has since clarified that the Price exception does not “impose\nliability upon the grantee[,]” but merely unwinds “the transfer of the cash in the grantee’s\npockets.” Id.\n\n 9\n\fsufficient information about Virtus’ financial condition to allege a fraudulent conveyance\n\nor voluntary transfer. Neither defendant disclosed any financial records or bank\n\nstatements to Bennett during the arbitration. Indeed, as noted above, rather than produce\n\nsuch documents, the defendants stipulated that the financial benchmarks in the Bennett\n\nAgreement had been “met in full.”\n\n It was not until Virtus failed to satisfy the judgment rendered against it, and\n\nBennett received Virtus’ relevant financial records, that he learned that Virtus had no\n\nremaining assets from which it could pay the judgment. These financial documents also\n\ndisclosed the recipient of Virtus’ transferred assets and the nature of such transfers,\n\nallowing Bennett to properly plead his fraudulent transfer claims. Thus, it was only after\n\nthe state court judgment was entered that Bennett would have had “actual notice” of any\n\npotential fraudulent transfer claims. Cf. Luria v. Bd. of Dirs. of Westbriar Condo. Unit\n\nOwners Ass’n, 672 S.E.2d 837, 840 (Va. 2009) (recognizing that, while a judgment is not\n\nrequired to bring a fraudulent conveyance claim, a plaintiff must have “actual notice of a\n\nspecific potential claim” to be considered a “creditor” under Virginia Code § 55-80).\n\n On these facts, we hold that Bennett could not have brought his fraudulent transfer\n\nclaims in the arbitration proceedings. To conclude otherwise essentially would have\n\nrequired Bennett to be clairvoyant. Under the defendants’ logic, a plaintiff in Bennett’s\n\nposition would have had to amend his original complaint, adding claims of fraudulent\n\nconveyance whenever he suspected that the defendant was moving money to avoid\n\npaying a potential judgment. Otherwise, the plaintiff would risk having those claims\n\nbarred in a later action to collect on that judgment. In other words, Bennett would have\n\n 10\n\fhad to try to enforce his judgment before the judgment was awarded. We decline to\n\ninterpret Virginia’s res judicata law in a manner that would lead to such untenable results.\n\nSee State Water Control Bd. v. Smithfield Foods, Inc., 542 S.E.2d 766, 769 (Va. 2001)\n\n(“The doctrine [of res judicata] protects litigants from multiple lawsuits, conserves\n\njudicial resources, and fosters certainty and reliance in legal relationships.” (emphasis\n\nadded)). Therefore, we hold that Bennett’s fraudulent transfer claims are not precluded\n\nunder Virginia’s res judicata doctrine.\n\n 2.\n\n With respect to Bennett’s alter-ego claim, we similarly conclude that the claim\n\ncould not have been brought before the state court judgment was entered against Virtus.\n\nWhen an individual uses a corporate form to “disguise wrongs, obscure fraud, or conceal\n\ncrime,” Virginia law permits a plaintiff to pierce the corporate veil and to impose liability\n\ndirectly on the individual as the “alter ego” of the corporation. Cheatle v. Rudd’s\n\nSwimming Pool Supply Co., 360 S.E.2d 828, 831 (Va. 1987). However, before bringing\n\nan action to pierce the corporate veil, the plaintiff must “first obtain[] a judgment against\n\nthe corporation.” Dana v. 313 Freemason, 587 S.E.2d 548, 553 (Va. 2003). Because\n\nBennett was required to obtain a judgment against Virtus before bringing his alter-ego\n\nclaim, this claim had not yet accrued at the time of the arbitration proceedings.\n\nAccordingly, we hold that Bennett’s alter-ego claim also is not precluded under\n\nVirginia’s doctrine of res judicata. See D’Ambrosio, 809 S.E.2d at 628.\n\n\n\n III.\n\n 11\n\f For these reasons, we hold that Bennett’s fraudulent transfer claims and his alter-\n\nego claim are not precluded under Virginia law by res judicata. 4 Accordingly, we vacate\n\nthe district court’s award of summary judgment in favor of the defendants and remand the\n\ncase to the district court for further proceedings.\n\n VACATED AND REMANDED\n\n\n\n\n 4\n Bennett also asks us to enter summary judgment in his favor on his fraudulent\ntransfer claims. Because the district court held that Bennett’s action was barred by res\njudicata, the court did not rule on the merits of Bennett’s claims. We decline to consider\nthose issues in the first instance. See Graham v. Gagnon, 831 F.3d 176, 189 (4th Cir.\n2016).\n\n 12", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359323/", "author_raw": "BARBARA MILANO KEENAN, Circuit Judge:"}]}
KEENAN
FLOYD
THACKER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582070/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: John S. BENNETT, Plaintiff - Appellant, v. James GARNER; Virtus Consulting, LLC, Defendants - Appellees.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1531\n\n\nJOHN S. BENNETT,\n\n Plaintiff - Appellant,\n\n v.\n\nJAMES GARNER; VIRTUS CONSULTING, LLC,\n\n Defendants - Appellees.\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:17-cv-00574-CMH-TCB)\n\n\nArgued: December 13, 2018 Decided: January 16, 2019\n\n\nBefore KEENAN, FLOYD, and THACKER, Circuit Judges.\n\n\nVacated and remanded by published opinion. Judge Keenan wrote the opinion, in which\nJudge Floyd and Judge Thacker joined.\n\n\nARGUED: Kevin M. O’Donnell, HENRY & O’DONNELL, PC, Alexandria, Virginia,\nfor Appellant. Thomas Wayne Biggs II, DYCIO & BIGGS, Fairfax, Virginia, for\nAppellees. ON BRIEF: Jeffery T. Martin, Jr., HENRY & O’DONNELL, PC,\nAlexandria, Virginia, for Appellant. Daniel F. Izzo, DYCIO & BIGGS, Fairfax,\nVirginia, for Appellees.\n\fBARBARA MILANO KEENAN, Circuit Judge:\n\n John S. Bennett appeals from the district court’s award of summary judgment in\n\nfavor of his former employer, Virtus Consulting, LLC (Virtus), and its owner, James\n\nGarner (collectively, the defendants), in Bennett’s action seeking to collect on a state\n\ncourt judgment entered against the defendants. The district court held that Bennett’s\n\nclaims were precluded under Virginia’s doctrine of res judicata.\n\n Upon our review, we conclude that Bennett’s claims are not precluded, because\n\nBennett could not have brought those claims at the time of his earlier litigation.\n\nAccordingly, we vacate the district court’s judgment and remand for further proceedings.\n\n\n\n I.\n\n We present the facts in the light most favorable to Bennett, the nonmoving party,\n\nand draw all reasonable inferences in his favor. Rosetta Stone Ltd. v. Google, Inc., 676\n\nF.3d 144, 150 (4th Cir. 2012) (citation omitted). Virtus is a Virginia limited liability\n\ncompany that provides consulting services to various financial institutions. Garner is the\n\nowner and sole member of Virtus. Bennett was employed by Virtus and worked as the\n\nprincipal contact for one of Virtus’ largest clients.\n\n In 2012, Garner began negotiations to sell Virtus’ assets to the Solomon Edwards\n\nGroup (SEG). Around the same time, the defendants and Bennett signed an agreement,\n\nin which Bennett agreed to assist in the sale in exchange for “sharing [in the] proceeds”\n\nfrom the sale (the Bennett Agreement). Under the Bennett Agreement, once the sale to\n\nSEG successfully closed, Bennett would receive a fixed cash payment made in quarterly\n\n 2\n\finstallments. The parties also agreed that Bennett potentially could receive two annual\n\n“earn out” payments, depending on whether SEG and Garner achieved certain revenue\n\ntargets in the two years following the sale.\n\n The sale of Virtus’ assets to SEG successfully closed around the end of September\n\n2012. In accordance with the Bennett Agreement, Garner made the first two quarterly\n\ninstallment payments to Bennett. But, in April 2013, the defendants ceased making any\n\nfurther payments, claiming that Bennett had breached his obligations under the\n\nagreement. Bennett, however, maintained that he was entitled to the remaining\n\ninstallment payments and the “earn out” payments.\n\n The parties submitted their dispute to an arbitrator as required by the arbitration\n\nclause in the Bennett Agreement. During the arbitration proceedings, the defendants\n\nprovided Bennett documents describing the structure of the SEG sale but did not produce\n\nany of Virtus’ financial records or bank statements. In response to a request seeking\n\nthose financial records, the defendants stipulated that the Bennett Agreement was\n\nproperly executed and that the performance metrics triggering the “earn out” payments\n\nhad been “met in full.”\n\n In September 2014, the arbitrator ordered Virtus to pay Bennett $387,500. Under\n\nthe terms of the Bennett Agreement, the arbitrator held Garner jointly and severally liable\n\nfor $125,000 of that award. The award was confirmed by a Virginia circuit court and\n\nreduced to a judgment. Although Garner paid the portion of the award for which he\n\npersonally was liable, Virtus failed to pay the remaining $262,500.\n\n\n\n 3\n\f After the arbitration award was confirmed, Bennett obtained Virtus’ bank\n\nstatements. These statements showed that shortly before the SEG sale closed, Garner had\n\ntransferred substantially all of Virtus’ cash reserves to himself. Further, Bennett learned\n\nthat the SEG sale had been structured to divert all cash and other consideration from the\n\nsale to Garner personally. For instance, equity stock in SEG that was supposed to\n\ntransfer to Virtus as part of the sale was instead listed in Garner’s name and reported as\n\npart of Garner’s personal tax returns. Thus, Virtus lacked sufficient assets to satisfy\n\nBennett’s judgment.\n\n In May 2017, Bennett initiated the present action in the district court seeking to\n\ncollect on his judgment. He asserted four claims against the defendants: (1) fraudulent\n\nconveyance, in violation of Virginia Code § 55-80; (2) voluntary transfer, in violation of\n\nVirginia Code § 55-81 (together, the fraudulent transfer claims); (3) a claim seeking to\n\n“pierce the corporate veil” and recover the judgment amount directly from Garner (the\n\nalter-ego claim); and (4) fraud in the inducement. The district court granted the\n\ndefendants’ motion for summary judgment, concluding that Bennett’s fraudulent transfer\n\nclaims and alter-ego claim were precluded under Virginia’s doctrine of res judicata. 1\n\nThis appeal followed.\n\n\n\n\n 1\n The district court also awarded the defendants summary judgment on Bennett’s\nfraud in the inducement claim, concluding that it was barred by the two-year statute of\nlimitations governing fraud claims, Va. Code § 8.01-243(A). Bennett does not contest\nthe dismissal of the fraud in the inducement claim.\n\n\n 4\n\f II.\n\n We review de novo the district court’s award of summary judgment. Rosetta\n\nStone Ltd., 676 F.3d at 150.\n\n A.\n\n Before addressing the parties’ arguments, we begin by reviewing the applicable\n\nprinciples of res judicata. In considering the preclusive effect of an earlier state court\n\njudgment on a new claim, we apply the “preclusion law of the State in which judgment\n\nwas rendered.” In re Genesys Data Techs., Inc., 204 F.3d 124, 127 (4th Cir. 2000)\n\n(quoting Marrese v. Am. Acad. of Orthopedic Surgeons, 470 U.S. 373, 380 (1985)).\n\nHere, the arbitration award was confirmed and reduced to a judgment by a Virginia court.\n\nWe therefore apply Virginia’s principles of res judicata.\n\n In Virginia, res judicata 2 is governed by Rule 1:6 of the Rules of the Supreme\n\nCourt of Virginia, which states in relevant part:\n\n A party whose claim for relief arising from identified conduct, a\n transaction, or an occurrence, is decided on the merits by a final judgment,\n shall be forever barred from prosecuting any second or subsequent civil\n action against the same opposing party or parties on any claim or cause of\n action that arises from that same conduct, transaction or occurrence,\n whether or not the legal theory or rights asserted in the second or\n subsequent action were raised in the prior lawsuit, and regardless of the\n legal elements or the evidence upon which any claims in the prior\n proceeding depended, or the particular remedies sought.\n\n\n\n\n 2\n Although Virginia’s res judicata doctrine encompasses both claim preclusion and\nissue preclusion, here we use the term “res judicata” to refer to claim preclusion only.\nSee Funny Guy, LLC v. Lecego, LLC, 795 S.E.2d 887, 890 (Va. 2017).\n\n 5\n\fVa. Sup. Ct. R. 1:6(a). Under this rule, “a final judgment forecloses ‘successive litigation\n\nof the very same claim, whether or not relitigation of the claim raises the same issues as\n\nthe earlier suit.’” Lee v. Spoden, 776 S.E.2d 798, 803 (Va. 2015) (quoting Taylor v.\n\nSturgell, 553 U.S. 880, 892 (2008)). Parties, therefore, may not relitigate “the same\n\ncause of action or any part thereof which could have been litigated in the previous\n\naction.” D’Ambrosio v. Wolf, 809 S.E.2d 625, 628 (Va. 2018) (citation omitted). Stated\n\nsimply, res judicata operates to prevent a party from getting a “second bite of the apple”\n\nwith respect to wrongs arising from a single dispute. See Funny Guy, LLC v. Lecego,\n\nLLC, 795 S.E.2d 887, 890 (Va. 2017) (“The law should afford one full, fair hearing\n\nrelating to a particular problem—but not two.” (citation omitted)).\n\n While ostensibly a broad proposition, res judicata nonetheless is limited by\n\nlongstanding principles. For instance, claims brought solely to execute on a judgment are\n\ngenerally not precluded by prior litigation that resulted in that judgment. See State Farm\n\nMut. Auto. Ins. Co. v. Kelly, 380 S.E.2d 654, 655 n.2 (Va. 1989); see also Restatement 2d\n\nJudgments § 18(c). Similarly, res judicata does “not bar a claim that does not accrue\n\nprior to the litigation triggering the bar.” Funny Guy, 795 S.E.2d at 900 (emphasis\n\nadded). A party is not precluded from bringing a claim that he was unable to bring in the\n\ninitial litigation, regardless whether that claim constitutes part of the same “conduct,\n\ntransaction, or occurrence.” D’Ambrosio, 809 S.E.2d at 628; Funny Guy, 795 S.E.2d at\n\n890 (“Determining which claims should have been brought in earlier litigation largely\n\ndepends on which claims could have been brought.” (citation omitted)); see also Lawlor\n\nv. Nat’l Screen Serv. Corp., 349 U.S. 322, 328 (1955) (explaining that although an earlier\n\n 6\n\fjudgment “precludes recovery on claims arising prior to its entry, it cannot be given the\n\neffect of extinguishing claims which did not even then exist”). With these principles in\n\nmind, we turn to consider the parties’ arguments.\n\n B.\n\n As the parties asserting res judicata, the defendants bear the burden of showing\n\nthat it is more likely than not that Bennett’s claims should be precluded by the prior\n\njudgment. D’Ambrosio, 809 S.E.2d at 628. The defendants argue, as they did in the\n\ndistrict court, that because Bennett had knowledge of the structure of the SEG sale at the\n\ntime of the arbitration, Bennett could have raised both his fraudulent transfer and alter-\n\nego claims during those proceedings. Accordingly, the defendants contend that under\n\nVirginia’s doctrine of res judicata, Bennett must have brought those claims during the\n\narbitration proceedings.\n\n In response, Bennett generally maintains that his claims are brought solely in\n\nexecution of his state court judgment. That is, instead of seeking to “relitigate” the\n\ndefendants’ liability under the Bennett Agreement, Bennett argues that his fraudulent\n\ntransfer claims were an attempt to collect on the judgment he is owed and could not have\n\nbeen brought before the judgment was entered. With respect to his alter-ego claim,\n\nBennett similarly argues that he could not have maintained that claim before obtaining\n\nthe judgment against Virtus. We agree with Bennett and address each argument in turn.\n\n 1.\n\n We begin by considering the question whether Bennett could have raised his\n\nfraudulent transfer claims during the arbitration proceedings. Actions brought under\n\n 7\n\fVirginia’s fraudulent conveyance statute, Va. Code § 55-80, and the state’s voluntary\n\ntransfer statute, Va. Code § 55-81, assist creditors in collecting on a judgment or other\n\ndebt. See La Bella Dona Skin Care, Inc. v. Belle Femme Enters., LLC, 805 S.E.2d 399,\n\n406 (Va. 2017); Balzer & Assocs., Inc. v. The Lakes on 360, Inc., 463 S.E.2d 453, 455-56\n\n(Va. 1995). Such actions do not impose liability on the participants in a fraudulent\n\nconveyance, but merely unwind “transactions designed to place a debtor’s assets beyond\n\nhis creditors’ reach.” La Bella Dona, 805 S.E.2d at 404, 406; see also Mills v. Miller\n\nHarness Co., 326 S.E.2d 665, 667 (Va. 1985) (concluding that Virginia Code § 55-80\n\ndoes not authorize a court “to award an in personam judgment when a fraudulent\n\nconveyance is set aside”). Indeed, Virginia law expressly permits actions under both\n\nSections 55-80 and 55-81 to be brought after the entry of a judgment. Va. Code § 55-\n\n82.2 (“The court shall have the authority to set aside a fraudulent conveyance or\n\nvoluntary transfer pursuant to § 55-80 or § 55-81 during an action brought by a creditor\n\nto execute on a judgment.” (emphasis added)). Thus, actions to void wrongful transfers\n\nare remedies designed to “return[] the fraudulently conveyed assets to the transferor.” La\n\nBella Dona, 805 S.E.2d at 406.\n\n In the present case, the disputes that the parties submitted to arbitration focused on\n\nthe issue whether Bennett was entitled to receive the remaining payments under the\n\nBennett Agreement. Thus, the arbitration served only to establish the parties’ respective\n\nobligations and liability under the Bennett Agreement.\n\n In contrast, Bennett’s fraudulent transfer claims allege that Virtus depleted its\n\ncorporate assets and made improper conveyances to Garner to prevent Bennett from\n\n 8\n\fcollecting on the arbitration award and judgment. Bennett does not advance any new\n\nlegal “theories of recovery” on which either defendant could be held liable under the\n\nBennett Agreement. Cf. Funny Guy, 795 S.E.2d at 897-98 (holding that, under principles\n\nof res judicata, “alternative theories of recovery” cannot be raised in consecutive\n\nlawsuits). Nor does he seek damages beyond the outstanding $262,500 judgment, the\n\nprecise amount awarded in arbitration. Although the alleged wrongful transfers took\n\nplace around the same time as the SEG sale, those transfers were immaterial to the\n\nquestion whether either Bennett or the defendants had breached the Bennett Agreement.\n\nThus, Bennett is not seeking a “second bite of the apple” with respect to the amount he is\n\nowed. See id. Rather, he seeks only to unwind the allegedly improper transfers from\n\nVirtus to Garner so that Virtus can satisfy the existing judgment. 3\n\n Furthermore, we observe that had Bennett claimed that the defendants were\n\nattempting to defraud him by transferring assets, before he proved that he was entitled to\n\npayments under the Bennett Agreement, those fraudulent transfer claims would have\n\nbeen premature. At the time of the arbitration proceedings, Bennett did not have\n\n\n 3\n The defendants incorrectly rely on the Supreme Court of Virginia’s decision in\nPrice v. Hawkins, 439 S.E.2d 382 (Va. 1994), to argue that Bennett’s fraudulent\nconveyance claim under Virginia Code § 55-80 is meant to impose liability on Garner. In\nPrice, the court allowed an in personam judgment to be awarded against recipients of\nfraudulent transfers when the wrongfully transferred property was only cash. Id. at 385.\nThis narrowly crafted exception was designed to prevent a defrauded creditor from being\nleft without a remedy, because cash “cannot be easily located for attachment or levy.” La\nBella Dona, 805 S.E.2d at 406 (describing the exception in Price). However, the\nSupreme Court of Virginia has since clarified that the Price exception does not “impose\nliability upon the grantee[,]” but merely unwinds “the transfer of the cash in the grantee’s\npockets.” Id.\n\n 9\n\fsufficient information about Virtus’ financial condition to allege a fraudulent conveyance\n\nor voluntary transfer. Neither defendant disclosed any financial records or bank\n\nstatements to Bennett during the arbitration. Indeed, as noted above, rather than produce\n\nsuch documents, the defendants stipulated that the financial benchmarks in the Bennett\n\nAgreement had been “met in full.”\n\n It was not until Virtus failed to satisfy the judgment rendered against it, and\n\nBennett received Virtus’ relevant financial records, that he learned that Virtus had no\n\nremaining assets from which it could pay the judgment. These financial documents also\n\ndisclosed the recipient of Virtus’ transferred assets and the nature of such transfers,\n\nallowing Bennett to properly plead his fraudulent transfer claims. Thus, it was only after\n\nthe state court judgment was entered that Bennett would have had “actual notice” of any\n\npotential fraudulent transfer claims. Cf. Luria v. Bd. of Dirs. of Westbriar Condo. Unit\n\nOwners Ass’n, 672 S.E.2d 837, 840 (Va. 2009) (recognizing that, while a judgment is not\n\nrequired to bring a fraudulent conveyance claim, a plaintiff must have “actual notice of a\n\nspecific potential claim” to be considered a “creditor” under Virginia Code § 55-80).\n\n On these facts, we hold that Bennett could not have brought his fraudulent transfer\n\nclaims in the arbitration proceedings. To conclude otherwise essentially would have\n\nrequired Bennett to be clairvoyant. Under the defendants’ logic, a plaintiff in Bennett’s\n\nposition would have had to amend his original complaint, adding claims of fraudulent\n\nconveyance whenever he suspected that the defendant was moving money to avoid\n\npaying a potential judgment. Otherwise, the plaintiff would risk having those claims\n\nbarred in a later action to collect on that judgment. In other words, Bennett would have\n\n 10\n\fhad to try to enforce his judgment before the judgment was awarded. We decline to\n\ninterpret Virginia’s res judicata law in a manner that would lead to such untenable results.\n\nSee State Water Control Bd. v. Smithfield Foods, Inc., 542 S.E.2d 766, 769 (Va. 2001)\n\n(“The doctrine [of res judicata] protects litigants from multiple lawsuits, conserves\n\njudicial resources, and fosters certainty and reliance in legal relationships.” (emphasis\n\nadded)). Therefore, we hold that Bennett’s fraudulent transfer claims are not precluded\n\nunder Virginia’s res judicata doctrine.\n\n 2.\n\n With respect to Bennett’s alter-ego claim, we similarly conclude that the claim\n\ncould not have been brought before the state court judgment was entered against Virtus.\n\nWhen an individual uses a corporate form to “disguise wrongs, obscure fraud, or conceal\n\ncrime,” Virginia law permits a plaintiff to pierce the corporate veil and to impose liability\n\ndirectly on the individual as the “alter ego” of the corporation. Cheatle v. Rudd’s\n\nSwimming Pool Supply Co., 360 S.E.2d 828, 831 (Va. 1987). However, before bringing\n\nan action to pierce the corporate veil, the plaintiff must “first obtain[] a judgment against\n\nthe corporation.” Dana v. 313 Freemason, 587 S.E.2d 548, 553 (Va. 2003). Because\n\nBennett was required to obtain a judgment against Virtus before bringing his alter-ego\n\nclaim, this claim had not yet accrued at the time of the arbitration proceedings.\n\nAccordingly, we hold that Bennett’s alter-ego claim also is not precluded under\n\nVirginia’s doctrine of res judicata. See D’Ambrosio, 809 S.E.2d at 628.\n\n\n\n III.\n\n 11\n\f For these reasons, we hold that Bennett’s fraudulent transfer claims and his alter-\n\nego claim are not precluded under Virginia law by res judicata. 4 Accordingly, we vacate\n\nthe district court’s award of summary judgment in favor of the defendants and remand the\n\ncase to the district court for further proceedings.\n\n VACATED AND REMANDED\n\n\n\n\n 4\n Bennett also asks us to enter summary judgment in his favor on his fraudulent\ntransfer claims. Because the district court held that Bennett’s action was barred by res\njudicata, the court did not rule on the merits of Bennett’s claims. We decline to consider\nthose issues in the first instance. See Graham v. Gagnon, 831 F.3d 176, 189 (4th Cir.\n2016).\n\n 12\n[END_CASE]", "role": "user" } ]
4,582,072
The CITY OF NEW YORK; The City of Philadelphia; The City and County of San Francisco, Plaintiffs - Appellants, v. the UNITED STATES DEPARTMENT OF DEFENSE; The United States Department of the Air Force; The United States Department of the Navy; The United States Department of the Army; James N. Mattis, in His Official Capacity as United States Secretary of Defense; Heather A. Wilson, in Her Official Capacity as United States Secretary of the Air Force; Richard v. Spencer, in His Official Capacity as United States Secretary of the Navy; Dr. Mark T. Esper, in His Official Capacity as United States Secretary of the Army; Dermot F. O'Reilly, in His Official Capacity as Director of the Defense Criminal Investigative Service; Colonel Kirk B. Stabler, in His Official Capacity as Commander of the Air Force Office of Special Investigations; Andrew L. Traver, in His Official Capacity as Director of the Naval Criminal Investigative Service; Major General David P. Glaser, in His Official Capacity as Commanding General of the United States Army Criminal Investigation Command; Rear Admiral John B. Nowell, in His Official Capacity as Commander of the Navy Personnel Command and Deputy Chief of Naval Personnel, Defendants - Appellees.
City of N.Y. v. U.S. Dep't of Def.
2019-01-16
18-1699
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Wilkinson, Agee, Thacker", "parties": "", "opinions": [{"author": "WILKINSON, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1699\n\n\nTHE CITY OF NEW YORK; THE CITY OF PHILADELPHIA; THE CITY AND\nCOUNTY OF SAN FRANCISCO,\n\n Plaintiffs – Appellants,\n\n v.\n\nTHE UNITED STATES DEPARTMENT OF DEFENSE; THE UNITED STATES\nDEPARTMENT OF THE AIR FORCE; THE UNITED STATES DEPARTMENT\nOF THE NAVY; THE UNITED STATES DEPARTMENT OF THE ARMY;\nJAMES N. MATTIS, in his official capacity as United States Secretary of Defense;\nHEATHER A. WILSON, in her official capacity as United States Secretary of the\nAir Force; RICHARD V. SPENCER, in his official capacity as United States\nSecretary of the Navy; DR. MARK T. ESPER, in his official capacity as United\nStates Secretary of the Army; DERMOT F. O'REILLY, in his official capacity as\nDirector of the Defense Criminal Investigative Service; COLONEL KIRK B.\nSTABLER, in his official capacity as Commander of the Air Force Office of\nSpecial Investigations; ANDREW L. TRAVER, in his official capacity as Director\nof the Naval Criminal Investigative Service; MAJOR GENERAL DAVID P.\nGLASER, in his official capacity as Commanding General of the United States\nArmy Criminal Investigation Command; REAR ADMIRAL JOHN B. NOWELL,\nin his official capacity as Commander of the Navy Personnel Command and\nDeputy Chief of Naval Personnel,\n\n Defendants - Appellees.\n\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:17-cv-01464-CMH-MSN)\n\n\nArgued: December 11, 2018 Decided: January 16, 2019\n\fBefore WILKINSON, AGEE, and THACKER, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge Agee\nand Judge Thacker joined.\n\n\nARGUED: Matthew Jeffrey MacLean, PILLSBURY WINTHROP SHAW PITTMAN\nLLP, Washington, D.C., for Appellants. Tyce R. Walters, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Appellees. ON BRIEF: Laura B.\nLoBue, Jeetander Dulani, Washington, D.C., Kenneth W. Taber, Matthew F. Putorti,\nNicholas M. Buell, PILLSBURY WINTHROP SHAW PITTMAN LLP, New York, New\nYork, for Appellants. Eric Proshansky, Melanie C.T. Ash, Eric Lee, Claude S. Platton,\nZachary W. Carter, CORPORATION COUNSEL OF THE CITY OF NEW YORK,\nNEW YORK CITY LAW DEPARTMENT, New York, New York, for Appellant City of\nNew York. Dennis J. Herrera, Yvonne R. Mere, Owen J. Clements, SAN FRANCISCO\nCITY ATTORNEY’S OFFICE, San Francisco, California, for Appellant City and County\nof San Francisco. Marcel S. Pratt, Eleanor N. Ewing, Benjamin H. Field, CITY OF\nPHILADELPHIA LAW DEPARTMENT, Philadelphia, Pennsylvania, for Appellant City\nof Philadelphia. Joseph H. Hunt, Assistant Attorney General, Mark B. Stern, Civil\nDivision, UNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C.; G.\nZachary Terwilliger, United States Attorney, OFFICE OF THE UNITED STATES\nATTORNEY, Alexandria, Virginia; Michael J. Fucci, Associate General Counsel,\nUNITED STATES DEPARTMENT OF DEFENSE, Washington, D.C., for Appellees.\n\n\n\n\n 2\n\fWILKINSON, Circuit Judge:\n\n Appellants are three municipalities who use the National Instant Criminal\n\nBackground Check System to carry out their obligations under state law. This system,\n\nknown as the NICS, is managed by the Federal Bureau of Investigation. The Department\n\nof Defense (DOD) is required under federal law to provide records to the NICS but has\n\npersistently been unable to fully carry out this obligation. The appellants sued DOD and\n\nits constituent military departments to compel the department’s more thorough\n\ncompliance. The district court dismissed their claim, holding both that the appellants\n\nlacked constitutional standing and failed to establish subject matter jurisdiction under the\n\nAdministrative Procedure Act. For the following reasons, we affirm.\n\n\n\n I.\n\n A.\n\n The responsibility to combat gun violence falls on every level of government. Law\n\nenforcement officials, whether local, state, or federal, work to prevent senseless gun\n\nviolence and are often the first to risk their lives to protect our communities. Working\n\nalongside these officers are many other governmental partners, including agencies of the\n\nfederal government. The dispute here grows out of a program that facilitates information\n\nsharing between federal agencies and local law enforcement officials: The National\n\nInstant Criminal Background Check System.\n\n The Brady Handgun Violence Prevention Act, or Brady Act, established the first\n\nnationwide system for background checks. Pub. L. No. 103-159, 107 Stat. 1536 (1993).\n\n 3\n\fUnder the law, enacted in 1993, a background check was required for firearms sales by\n\nlicensed dealers. Id. § 102. The Brady Act directed the Attorney General to establish a\n\nnational database that would be accessible to the firearms dealers tasked with ensuring\n\nthese background checks were performed. Id. § 102(b). To implement the statute, the\n\nAttorney General established the National Instant Criminal Background Check System\n\n(NICS) and delegated control of the system to the Federal Bureau of Investigation (FBI).\n\n The NICS contains records for individuals who are prohibited from possessing a\n\nfirearm. The system draws from many distinct federal databases that contain\n\ndisqualifying records and relies on information submitted from across the federal\n\ngovernment. In the military context, DOD provides information regarding current and\n\nformer service members who are disqualified from owning a gun because of a prior\n\nconviction. The Brady Act also empowers the Attorney General to request records from\n\nother agencies that may possess disqualifying information. Id. § 103(e) (codified at 34\n\nU.S.C. § 40901(e) (2018)).\n\n As originally designed, state law enforcement agencies were required to\n\nadminister the Brady Act’s background checks on a temporary basis while the new\n\nnational background check system was established. The division of responsibility\n\nenvisioned by Congress was altered by the Supreme Court’s decision in Printz v. United\n\nStates, which found that “[t]he Federal Government may [not] command the States’\n\nofficers, or those of their political subdivisions, to administer or enforce a federal\n\nregulatory program.” 521 U.S. 898, 935 (1997). As the law now stands, states are not\n\nrequired to perform any functions associated with the Brady Act, although a state may\n\n 4\n\fvoluntarily play a role. For states that elect to participate, a “point of contact” is\n\ndesignated to “serv[e] as the intermediary between [a dealer] and the federal databases\n\nchecked by the NICS.” 28 C.F.R. § 25.2 (2017).\n\n This does not mean that state and local governments have no use of the\n\ninformation stored in the NICS. To the contrary, many states require law enforcement\n\nagencies to carry out a range of functions designed to prevent guns from reaching\n\ndangerous hands. Depending on the particulars of state law, a local law enforcement\n\nagency may perform checks associated with issuing permits and licenses, or may review\n\ndisqualifying information before transferring a gun that is in the state’s possession. For\n\nexample, the City of Philadelphia, a party to this case, is required to process applications\n\nfor licenses to carry firearms under Pennsylvania law. See 18 Pa. Cons. Stat. § 6109. The\n\nother municipal appellants have similar obligations.\n\n The Attorney General has long permitted state and local agencies, including the\n\nappellants, to access the NICS for these purposes. In 1998, the FBI promulgated a rule\n\nallowing state and local law enforcement to use the NICS when “issu[ing] a firearm-\n\nrelated or explosives-related permit or license,” including concealed-carry permits. See\n\nNational Instant Criminal Background Check System Regulation, 63 Fed. Reg. 58,303,\n\n58,309 (Oct. 30, 1998) (codified at 28 C.F.R. § 25.6(j)(1)). In 2014, a new rule further\n\nexpanded NICS access, allowing state and local agencies to access the system when\n\ndisposing of firearms in their possession. See National Instant Criminal Background\n\nCheck System Regulation, 79 Fed. Reg. 69,047, 69,048 (Nov. 20, 2014) (codified at 28\n\nC.F.R. § 25.6(j)(3)). The regulations clearly state that these uses of the NICS are\n\n 5\n\fpermissive, intended as a service, and “unrelated to NICS background checks required by\n\nthe Brady Act.” 28 C.F.R. § 25.6(j).\n\n At times, local law enforcement officials have pushed for even greater access. For\n\ninstance, the FBI’s 1998 rulemaking noted that some local agencies wanted permission to\n\naccess the database to determine if a person was in “unlawful possession of a firearm.” 63\n\nFed. Reg. at 58,305. The FBI resisted these requests. In the FBI’s view, such expanded\n\nuse would potentially run afoul of federal privacy laws. Id. Moreover, the FBI noted that\n\nthe Brady Act only required agency reporting for the purpose of carrying out the federal\n\nbackground check provisions, rather than for a wider range of law enforcement activities.\n\nId. The permissive use regulations therefore account for the requirements of federal law,\n\nthe informational needs of local law enforcement, and the privacy concerns of the\n\naffected individuals. In arriving at the scheme in place today, the FBI has shown a\n\nwillingness to expand NICS access to support local partners, but has apparently not gone\n\nas far as some of those partners may desire.\n\n The comprehensiveness and accuracy of the NICS has been a subject of frequent\n\ndebate and attention. See, e.g., U.S. Gov’t Accountability Office, GAO/T-GGD-00-163,\n\nGun Control: Improving the National Instant Criminal Background Check System (June\n\n21, 2000). At the federal level, many agencies possess disqualifying information that\n\nwould be relevant to a background check. Under the original Brady Act, federal agencies\n\nwere required to furnish information to the Attorney General upon request. See Pub. L.\n\nNo. 103-159, § 103(e)(1) (1993) (codified as amended at 34 U.S.C. § 40901(e)(1)).\n\n\n\n 6\n\f Following the fatal shooting of 32 students and faculty at Virginia Tech in 2007,\n\nCongress enacted new legislation to improve the NICS. See NICS Improvement\n\nAmendments Act of 2007 (NIAA), Pub. L. No. 110-180, 121 Stat. 2559 (2008). Finding\n\nthat “nearly 21,000,000 criminal records are not accessible by NICS and millions of\n\ncriminal records are missing critical data, such as arrest dispositions, due to backlogs,”\n\nthe legislation imposed new reporting requirements and authorized new grants to assist\n\nstates. Id. §§ 101, 103-104. To improve inter-agency information sharing, the Act\n\nimposed an affirmative duty on agencies to report disqualifying information on a\n\nquarterly basis. Id. § 101(a) (codified at 34 U.S.C. § 40901(e)(1)(C)-(D)). To incentivize\n\ncompliance, the Attorney General is required to provide an annual report to Congress on\n\neach agency’s success. Id. (codified at 34 U.S.C. § 40901(e)(1)(E)).\n\n The Department of Defense (DOD) has long struggled to comply with the NIAA’s\n\naffirmative reporting provision, a deficiency the department readily admits. Response Br.\n\nat 1. The DOD Inspector General reviewed the program in 2015 and found that a\n\nsubstantial percentage of required records were not being submitted to the FBI. U.S.\n\nDep’t of Def. Inspector Gen., Evaluation of Department of Defense Compliance with\n\nCriminal History Data Reporting Requirements 9 (Feb. 12, 2015). Similar findings were\n\nmade again in 2017. U.S. Dep’t of Def. Inspector Gen., Evaluation of Fingerprint Card\n\nand Final Disposition Report Submissions by Military Service Law Enforcement\n\nOrganizations (Dec. 4, 2017). On November 5, 2017, a gunman opened fire at a church in\n\nSutherland Springs, Texas, killing 26 people and injuring an additional 20. The gunman\n\nwas a former member of the military who had been convicted in court-martial\n\n 7\n\fproceedings. According to the municipal appellants, the gunman would not have been\n\nable to obtain a firearm if DOD complied with its reporting obligations under the NIAA.\n\n Following the devastating loss of life at Sutherland Springs, Congress again\n\namended the statute governing the NICS to improve inter-agency reporting. The Fix\n\nNICS Act, Pub. L. No. 115-141, Div. S, Title VI (2018), required federal agencies with\n\ndisqualifying records to submit semiannual certification reports to the Attorney General\n\nand develop compliance plans to improve their own performance. Id. § 602. Like the\n\nearlier amendment, this law also includes measures designed to hold poor performers\n\naccountable. First, the law requires that the Attorney General notify Congress of non-\n\ncompliant agencies and publish a list of those agencies on the DOJ website. Second, the\n\nlaw makes political appointees at non-compliant agencies ineligible for bonus pay until\n\nthe agency improves. Id. § 602(1) (codified at 34 U.S.C. § 40901(e)(1)(F)-(I)).\n\n In the time since the Sutherland Springs shooting, components of the Department\n\nof Defense have taken a wide range of actions to correct their deficiencies. Efforts\n\ninclude the creation of new task forces and compliance plans, as well as the development\n\nof new technological processes to streamline reporting. See J.A. 302-16. For example,\n\nthe Army has, in recent months, provided new records for nearly 33,000 disqualified\n\npersons to the NICS.\n\n B.\n\n The tragic shooting in Sutherland Springs also gave rise to this litigation. The\n\nappellants are three municipalities, all of whom use the NICS database to fulfill their\n\nrequirements under state law. They brought this suit to compel DOD’s full reporting of\n\n 8\n\fdisqualifying information to the Attorney General, as required by the NIAA. Since\n\nneither the Brady Act nor the NIAA contemplated a separate cause of action to compel\n\nperformance with inter-agency reporting obligations, the municipal appellants brought\n\ntheir claim under the general provision of the Administrative Procedure Act that allows\n\nan aggrieved party to “compel agency action unlawfully withheld or unreasonably\n\ndelayed.” 5 U.S.C. § 706(1) (2012).\n\n The district court granted the federal defendants’ motion to dismiss this claim,\n\nfinding that it lacked jurisdiction to hear the case. The court identified two independent\n\njurisdictional defects. First, the district court found that the municipal appellants had\n\nfailed “to allege[] a cognizable informational injury sufficient to confer standing.” J.A.\n\n341. Second, the court held that the cities did not establish “jurisdiction under the APA\n\nsince they have not alleged a discrete agency action.” Id. As a consequence of the\n\ndismissal, the court also denied the municipal appellants’ motion for a preliminary\n\ninjunction. Id. at 348.\n\n This appeal followed. While federal courts must assure themselves that they have\n\njurisdiction before proceeding to the merits, see Steel Co. v. Citizens for a Better Env’t,\n\n523 U.S. 83, 94-95 (1998), both of the infirmities identified by the district court go to the\n\nquestion of jurisdiction. As such, this court can turn to either issue alone to resolve this\n\ncase. See Ruhrgas AG v. Marathon Oil Co., 526 U.S. 574, 578 (1999) (“[T]here is no\n\nunyielding jurisdictional hierarchy.”). Our review is de novo.\n\n\n\n\n 9\n\f II.\n\n Because this court is not in “the habit of decid[ing] questions of a constitutional\n\nnature unless absolutely necessary,” we turn first to the statutory question of whether the\n\nmunicipal appellants have established subject matter jurisdiction under the\n\nAdministrative Procedure Act (APA). See Flue-Cured Tobacco Coop. Stabilization Corp.\n\nv. EPA, 313 F.3d 852, 857 (4th Cir. 2002) (quoting Ashwander v. Tenn. Valley Auth., 297\n\nU.S. 288, 347 (1936) (Brandeis, J. concurring)). At the outset, it is important to\n\nunderstand the nature of appellants’ claim. Their challenge is not about access to the\n\nNICS; it is instead about the quality of the information in that system. By their own\n\nsubmission, each of the appellants accesses the NICS frequently to carry out their\n\nobligations under state law. This is thus not a case where appellants have asked for access\n\nprovided for in the regulations and have been denied. Instead, the municipalities see their\n\nexisting access to the NICS as an invitation to compel any federal inter-agency legal\n\nrequirement that may affect the quality of the information they receive. On their view, the\n\nAPA authorizes a recipient of government information to initiate a private action to\n\ncompel governmental conduct that might improve that information’s accuracy or\n\ncomprehensiveness. As we explain below, there is simply no basis in the APA’s text for\n\nsuch a broad incursion into internal agency management.\n\n A.\n\n The APA waives the federal government’s sovereign immunity for a limited set of\n\nsuits, brought by “a person suffering legal wrong because of agency action” to obtain\n\nrelief “other than money damages.” 5 U.S.C. § 702. It is well-established that\n\n 10\n\f“[s]overeign immunity is jurisdictional in nature” and “absent a waiver . . . shields the\n\nFederal Government and its agencies from suit.” FDIC v. Meyer, 510 U.S. 471, 475\n\n(1994). Judicial review under the APA, moreover, is limited to “final agency actions.”\n\n5 U.S.C. § 704.\n\n As these provisions of the APA make plain, subject matter jurisdiction is lacking if\n\nthe plaintiff fails to challenge a particular “agency action” that is fit for review. See\n\nInvention Submission Corp. v. Rogan, 357 F.3d 452, 460 (4th Cir. 2004). “The term\n\n‘action’ as used in the APA is a term of art that does not include all conduct” on the part\n\nof the government. Vill. of Bald Head Island v. U.S. Army Corps of Eng’rs, 714 F.3d 186,\n\n193 (4th Cir. 2013). See also Hearst Radio v. FCC, 167 F.2d 225, 227 (D.C. Cir. 1948)\n\n(“The difficulty with the appellant company’s position is that the Administrative\n\nProcedure Act does not provide review for everything done by an agency.”). Instead, the\n\nAPA defines “agency action” to include “the whole or a part of an agency rule, order,\n\nlicense, sanction, relief, or the equivalent or denial thereof, or failure to act.” 5 U.S.C.\n\n§ 551(13).\n\n This definition limits the scope of judicial review in two important respects. First,\n\neach of the terms that comprise the definition of “agency action” is limited to those acts\n\nthat are “circumscribed” and “discrete.” Norton v. Southern Utah Wilderness Alliance\n\n(SUWA), 542 U.S. 55, 62 (2004). When challenging agency action―whether it be a\n\nparticular action or a failure to act altogether―the plaintiff must therefore identify\n\nspecific and discrete governmental conduct, rather than launch a “broad programmatic\n\nattack” on the government’s operations. Id. at 64. This distinction between discrete acts,\n\n 11\n\fwhich are reviewable, and programmatic challenges, which are not, is vital to the APA’s\n\nconception of the separation of powers. Courts are well-suited to reviewing specific\n\nagency decisions, such as rulemakings, orders, or denials. We are woefully ill-suited,\n\nhowever, to adjudicate generalized grievances asking us to improve an agency’s\n\nperformance or operations. In such a case, courts would be forced either to enter a\n\ndisfavored “obey the law” injunction, see Int’l Longshoremen’s Ass’n, Local 1291 v.\n\nPhil. Mar. Trade Ass’n, 389 U.S. 64, 76 (1967), or to engage in day-to-day oversight of\n\nthe executive’s administrative practices. Both alternatives are foreclosed by the APA, and\n\nrightly so. The Supreme Court’s guidance on this point is worth considering in full:\n\n If courts were empowered to enter general orders compelling compliance\n with broad statutory mandates, they would necessarily be empowered, as\n well, to determine whether compliance was achieved-which would mean\n that it would ultimately become the task of the supervising court, rather\n than the agency, to work out compliance with the broad statutory mandate,\n injecting the judge into day-to-day agency management.\n\nSUWA, 542 U.S. at 66-67. The requirement that the challenger identify a discrete act\n\nkeeps us from entering such a quagmire.\n\n Second, the definition of “agency action” is limited to those governmental acts\n\nthat “determin[e] rights and obligations.” Clear Sky Car Wash LLC v. City of\n\nChesapeake, Va., 743 F.3d 438, 445 (4th Cir. 2014). This limitation ensures that judicial\n\nreview does not reach into the internal workings of the government, and is instead\n\nproperly directed at the effect that agency conduct has on private parties. To meet this\n\nrequirement, a party must demonstrate that the challenged act had “an immediate and\n\npractical impact,” see Golden & Zimmerman LLC v. Domenech, 599 F.3d 426, 433 (4th\n\n\n 12\n\fCir. 2010), or “alter[ed] the legal regime” in which it operates. See Bennett v. Spear, 520\n\nU.S. 154, 178 (1997). It is not enough for plaintiffs to simply identify a governmental\n\naction that ultimately affected them through the “independent responses and choices of\n\nthird parties,” or mere “coercive pressures.” Flue-Cured Tobacco, 313 F.3d at 859, 861.\n\nThis requirement applies fully to claims that an agency has failed to act, which is\n\n“properly understood as a failure to take an agency action.” See Norton, 542 U.S. at 62.\n\nSince “agency actions” must determine rights and obligations, claims to compel an\n\nagency to take an action must seek such a determination as well.\n\n These two requirements, which flow directly from the APA’s text, apply to all\n\nchallenges to agency action and accordingly limit judicial review generally. When a\n\nplaintiff brings a claim to compel agency action, like the municipal appellants have here,\n\na further limit applies. Under the APA, actions that can be compelled are only those that\n\nhave been “unlawfully withheld or unreasonably delayed.” 5 U.S.C. § 706(1). As the\n\nSupreme Court has explained, the text of § 706(1) requires that the plaintiff identify\n\naction that is “legally required.” SUWA, 542 U.S. at 63. Just like the traditional\n\nmandamus remedy from which this provision is derived, claims to compel agency action\n\nare “limited to enforcement of ‘a specific, unequivocal command,’” over which an\n\nofficial has no discretion. Id. (quoting ICC v. New York, N.H. & H.R. Co., 287 U.S. 178,\n\n204 (1932)).\n\n Taken together, the limitations imposed on claims to compel agency action under\n\nthe APA strike a balance between meaningful judicial review and the needs of effective\n\nadministration. Review is available only when acts are discrete in character, required by\n\n 13\n\flaw, and bear on a party’s rights and obligations. The result is a scheme allowing courts\n\nto review only those acts that are specific enough to avoid entangling the judiciary in\n\nprogrammatic oversight, clear enough to avoid substituting judicial judgments for those\n\nof the executive branch, and substantial enough to prevent an incursion into internal\n\nagency management. See SUWA, 542 U.S. at 64-65.\n\n These principles guide our consideration of all claims to compel agency action,\n\nregardless of the context. Claims involving government information are no exception.\n\nOur court, just like our sister circuits, has had many occasions to consider how the\n\nrequirements of agency action apply to claims that the government has wrongfully\n\nhandled the information in its possession. In some cases, the claim is that the\n\ngovernment’s decision to disseminate information, such as an unfavorable report, was\n\nunlawful. See Invention Submission Corp., 357 F.3d at 460; see also Flue-Cured\n\nTobacco, 313 F.3d at 859; Indus. Safety Equip. Ass’n, Inc. v. EPA, 837 F.2d 1115, 1118\n\n(D.C. Cir. 1988). At other times, the claim was that the government improperly withheld\n\nor mishandled personal information. See, e.g., Fanin v. U.S. Dep’t of Veterans Affairs,\n\n572 F.3d 868, 871 (11th Cir. 2009). Informational harms may involve novel facts, but\n\nthey do not disrupt the legal principles set forth in the APA. See Golden & Zimmerman,\n\nLLC, 599 F.3d at 431-32 (finding that an agency’s “reference guide” was not agency\n\naction because it did not “impose new legal requirements”). As these cases aptly\n\ndemonstrate, a plaintiff’s burden remains constant and subject to the above requirements\n\nthroughout.\n\n\n\n 14\n\f B.\n\n Applying these well-established principles to the facts here, it is clear that the\n\nmunicipal appellants have failed to establish subject matter jurisdiction under the APA.\n\nOnce again, the claim at issue arises from the appellants’ permissive use of the NICS,\n\nafforded to them by regulation, for purposes explicitly “unrelated to the NICS\n\nbackground checks required by the Brady Act.” 28 C.F.R. § 25.6(j). The regulation\n\naffords the municipalities only “access to the NICS Index.” Id. On the view of the\n\nmunicipal appellants, this access, which is not expressly contemplated either by the\n\nBrady Act or subsequent legislation, allows a NICS user to reach into the federal\n\ngovernment and compel any legal obligations associated with developing the information\n\nin the system. Such a broad theory of agency action is untethered from the APA’s text\n\nand contravenes important limits that Congress has placed on judicial review.\n\n First, the municipal appellants’ claim does not challenge a discrete agency action.\n\nInstead appellants ask that we “supervise an agency’s compliance with [the] broad\n\nstatutory mandate” of the NIAA. Murray Energy Corp. v. EPA, 861 F.3d 529, 537 n.4\n\n(4th Cir. 2017). By appellants’ own account, the DOD’s failure to provide disqualifying\n\nconviction records for former service members is widespread and systemic. The\n\ndepartment has admitted as much and is engaged in extensive efforts to increase its\n\ncompliance. As all parties seem to agree, the road ahead is an arduous one, as DOD\n\nattempts to improve on its partial and inconsistent reporting. This is the sort of public\n\npolicy problem that often requires reallocating resources, developing new administrative\n\n 15\n\fsystems, and working closely with partners across government. Solving it will likely\n\nrequire expertise in information technology and deep knowledge of how military needs\n\nintersect with data collection. In other words, it is exactly the sort of “broad\n\nprogrammatic” undertaking for which the APA has foreclosed judicial review. See\n\nSUWA, 542 U.S. at 64.\n\n Congress seems to be of the same view. Since the passage of the Brady Act,\n\nCongress has on multiple occasions turned its attention to the severe challenge of\n\nrampant gun violence. Twice, the legislative responses have been directed squarely at\n\nagency compliance with NICS reporting obligations. Congress has included\n\naccountability measures, designed to identify delinquent agencies and push them into\n\nimproving their performance. The most recent effort in this regard singles out executive\n\ncompensation at these agencies, limiting bonus pay for those who do not improve their\n\noutcomes. See 34 U.S.C. § 40901(e)(1)(I) (providing that certain “political\n\nappointee[s] . . . shall not be eligible for the receipt of bonus pay” until their department\n\nimproves its compliance). These measures signal that Congress sees this problem as one\n\nripe for legislative oversight and in need of attention by experts in the executive branch.\n\nAt no point, however, has Congress invited the federal courts into the process. Perhaps\n\ncognizant of the judiciary’s inability to oversee and manage a complex scheme of inter-\n\nagency collaboration, we have appropriately been left on the sideline.\n\n The municipal appellants try to nonetheless force us onto the field by\n\ncharacterizing their broad claim as simply an aggregation of many small claims, each one\n\nseeking to compel the individual reports required by the NIAA. On this view, what the\n\n 16\n\fcities seek is not programmatic because each specific act that DOD has failed to perform\n\nis discrete when considered on its own. But any limit on programmatic assessment would\n\nbe rendered meaningless if such an argument prevailed. All governmental programs are\n\nthe aggregation of individual decisions, many of which are required by law. The APA\n\nensures that it is the individual decisions that are assessed as agency action, rather than\n\nthe whole administrative apparatus.\n\n The municipal appellants are surely correct that ongoing failures to carry out\n\ndiscrete obligations can be subject to review. Government deficiencies do not become\n\nnon-reviewable simply because they are pervasive. This, however, does nothing to\n\nobviate the fact that a discrete action is wholly lacking here. By the appellants’ own\n\nestimate, full compliance with the NIAA may require DOD to obtain and transmit tens of\n\nthousands of records. There is simply no way to achieve such a result without wholesale\n\nimprovements in the DOD’s reporting requirements, which take time and require the\n\nexpertise of senior civilian and military leaders.\n\n If there were any doubt about the nature of the cities’ claim, the requested remedy\n\ntells the real story. Their complaint “seeks immediate injunctive relief to compel\n\nDefendants to repair this broken system and to cure once and for all the potentially\n\ndeadly gaps in the NCIC database.” J.A. 17. In their prayer for relief, the appellants ask\n\nthat the DOD, on “a schedule to be set by the Court,” “identify all records” in its\n\npossession, provide the information contained in those records to the Attorney General,\n\n“conduct a thorough review of [its] records and procedures,” “submit to the Court for\n\napproval a compliance plan,” and provide “a monthly report to the Court detailing [its]\n\n 17\n\fprogress.” Id. at 35-36. The requested relief would continue “until such time as the Court\n\nis satisfied that Defendants have brought themselves into full compliance with 34 U.S.C.\n\n§ 40901.” Id. at 36 (emphasis added). The APA’s discreteness requirement exists to avoid\n\nplacing the courts in this exact position. As we previously explained, “[t]he obvious\n\ninability for a court to function in such a day-to-day managerial role over agency\n\noperations is precisely the reason why the APA limits judicial review to discrete agency\n\nactions.” Vill. of Bald Head Island, 714 F.3d at 194.\n\n Moreover, the municipal appellants have failed to demonstrate that the DOD’s\n\nreporting requirements in any way determine their rights and obligations. Accordingly,\n\nthey have not identified an act that can be compelled by this court under § 706(1). See\n\nSUWA, 542 U.S. at 62 (finding that a failure to act under § 706(1) means “failure to take\n\nan agency action”). The action challenged in this case is DOD’s obligation to provide\n\ninformation only to another agency of the federal government: The Department of\n\nJustice. See 34 U.S.C. § 40901(e)(1)(C). The regulation permitting local law enforcement\n\nagencies to use the NICS refers only to access to the system, not to the particular\n\ninformation provided to the FBI by other federal agencies. The transfer of information\n\nbetween agencies does not, without more, alter the rights and obligations of any party.\n\nThat is especially true, as here, where outside access to the information is entirely\n\npermissive and implicates none of the complaining party’s obligations under federal law.\n\n We need not say here that information sharing can never constitute agency action.\n\nWe simply note that claims to compel an agency to provide information are held to the\n\nsame standard as any other. In arguing otherwise, the municipal appellants point to a\n\n 18\n\fstring of cases, all from outside this circuit, holding that the government’s alleged misuse\n\nof information was reviewable “agency action.” Our holding here, however, raises no\n\nconflict with these decisions. The cases relied on by the appellants involve claims wholly\n\nunlike the one that they have brought. For example, one case involves the government’s\n\nlegal obligations with respect to the plaintiffs’ personal medical information, see Vietnam\n\nVeterans of Am. v. CIA, 811 F.3d 1068, 1078 (9th Cir. 2015) (finding that “the Army\n\n[has] a duty to provide notice to prior test subjects of information regarding their well-\n\nbeing”), while another examines the rights of federal employees under the civil service\n\nsystem, see Hondros v. U.S. Civil Service Comm., 720 F.2d 278, 280 (3d Cir. 1983). Each\n\nof these cases involved plaintiffs seeking information that was particular to them and\n\ntheir own rights under federal law. As such, they tell us little about how to handle a case,\n\nlike this one, where the plaintiff seeks wholesale compliance with an entire\n\nadministrative scheme, based solely on the fact that the government has granted them\n\naccess to an information system.\n\n\n\n C.\n\n What the municipal appellants are ultimately asking for is a judicial decree making\n\nthe assistance of the federal government more useful to them than it is now. While their\n\nmotives for wanting to see improvement to the NICS are laudable, they point to no case\n\nsuggesting that the APA countenances such an action. And for good reason. If a party\n\ncould seek review any time the federal government’s alleged non-compliance made a\n\ngovernment program less useful than it might otherwise be, the possibilities for litigation\n\n 19\n\fwould be endless. Followed to its logical conclusion, a recipient of the mail could sue the\n\nPostal Service for improper employment practices, alleging that it caused inefficient\n\npackage deliveries. A disgruntled grant applicant could sue the National Institutes of\n\nHealth for violations of financial management laws, arguing that with more money in its\n\ncoffers more grants could be issued. The APA, however, is a creature of Congress; the\n\nlegislative branch has not put it to this sort of use, and we can discern no workable limits\n\nin the appellants’ theory.\n\n The implications of the appellants’ position are particularly troubling in the\n\ncontext of voluntary information sharing. The federal government has access to a vast\n\namount of data that is of great use both to intergovernmental partners and to those in the\n\nprivate sector. Information stored with the federal government is critical to many areas of\n\npublic policy, including, for example, homeland security and healthcare. See, e.g., Nat’l\n\nInfrastructure Advisory Council, Intelligence Information Sharing: Final Report and\n\nRecommendations ES-1 (Jan. 10, 2012) (“Information sharing is perhaps the most\n\nimportant factor in the protection and resilience of critical infrastructure.”). The federal\n\ngovernment has recently taken steps to make more of its own information accessible to\n\nthe general public, aware of the innovative potential that such information can unleash.\n\nSee Exec. Order No. 13,642, 78 Fed. Reg. 28,111 (May 9, 2013); see generally Data.gov\n\n(“The home of the U.S. Government’s open data.”). If we adopted the all-encompassing\n\ndefinition of “agency action” asserted by the municipal appellants here, each of these\n\nefforts to enhance public access would be checked by a fear that greater openness would\n\ninvite judicial scrutiny of any act that went into developing or disseminating the data.\n\n 20\n\fWith an agency’s eye peeled towards these consequences, it is easy to imagine the federal\n\ngovernment pulling back from these salutary efforts, and instead choosing to silo its\n\ninformation.\n\n The adverse consequences of appellants’ theory would not just fall on the\n\ngovernment’s attempt to share information with the public; they would also compromise\n\nthe dissemination of information within the government itself. A rule that made inter-\n\nagency information sharing justiciable by federal courts would undermine the whole\n\ngamut of federal activities that require collaboration between agencies, of which military\n\npreparedness and anti-terrorism efforts are only a part. Agencies dealing with public\n\nhealth, environment conservation, and disaster response draw on entire bodies of\n\nscientific work, and not all of the needed expertise will be located within a single agency\n\nor department. To have internal information sharing haunted by the specter of judicial\n\noversight would weaken government operations in innumerable areas, both foreign and\n\ndomestic, and allow the prospect of litigation to erect barriers when other nations, both\n\nour allies and our competitors, proceed unburdened by similar obstacles.\n\n\n\n III.\n\n The municipal appellants, like localities all over the country, are tasked with\n\nkeeping the public safe from horrific acts of violence, which far too often are committed\n\nby those with firearms they had no lawful right to possess. The municipalities’ efforts to\n\ncombat these threats are commendable. The APA, however, does not permit their efforts\n\nto include judicial supervision of the myriad programmatic workings of the federal\n\n 21\n\fgovernment. No matter the asserted virtues of the intended intervention, we are simply\n\nnot equipped to perform such tasks and have no legal basis for doing so.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 22", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4359325/", "author_raw": "WILKINSON, Circuit Judge:"}]}
WILKINSON
AGEE
THACKER
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4582072/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: The CITY OF NEW YORK; The City of Philadelphia; The City and County of San Francisco, Plaintiffs - Appellants, v. the UNITED STATES DEPARTMENT OF DEFENSE; The United States Department of the Air Force; The United States Department of the Navy; The United States Department of the Army; James N. Mattis, in His Official Capacity as United States Secretary of Defense; Heather A. Wilson, in Her Official Capacity as United States Secretary of the Air Force; Richard v. Spencer, in His Official Capacity as United States Secretary of the Navy; Dr. Mark T. Esper, in His Official Capacity as United States Secretary of the Army; Dermot F. O'Reilly, in His Official Capacity as Director of the Defense Criminal Investigative Service; Colonel Kirk B. Stabler, in His Official Capacity as Commander of the Air Force Office of Special Investigations; Andrew L. Traver, in His Official Capacity as Director of the Naval Criminal Investigative Service; Major General David P. Glaser, in His Official Capacity as Commanding General of the United States Army Criminal Investigation Command; Rear Admiral John B. Nowell, in His Official Capacity as Commander of the Navy Personnel Command and Deputy Chief of Naval Personnel, Defendants - Appellees.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-16\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1699\n\n\nTHE CITY OF NEW YORK; THE CITY OF PHILADELPHIA; THE CITY AND\nCOUNTY OF SAN FRANCISCO,\n\n Plaintiffs – Appellants,\n\n v.\n\nTHE UNITED STATES DEPARTMENT OF DEFENSE; THE UNITED STATES\nDEPARTMENT OF THE AIR FORCE; THE UNITED STATES DEPARTMENT\nOF THE NAVY; THE UNITED STATES DEPARTMENT OF THE ARMY;\nJAMES N. MATTIS, in his official capacity as United States Secretary of Defense;\nHEATHER A. WILSON, in her official capacity as United States Secretary of the\nAir Force; RICHARD V. SPENCER, in his official capacity as United States\nSecretary of the Navy; DR. MARK T. ESPER, in his official capacity as United\nStates Secretary of the Army; DERMOT F. O'REILLY, in his official capacity as\nDirector of the Defense Criminal Investigative Service; COLONEL KIRK B.\nSTABLER, in his official capacity as Commander of the Air Force Office of\nSpecial Investigations; ANDREW L. TRAVER, in his official capacity as Director\nof the Naval Criminal Investigative Service; MAJOR GENERAL DAVID P.\nGLASER, in his official capacity as Commanding General of the United States\nArmy Criminal Investigation Command; REAR ADMIRAL JOHN B. NOWELL,\nin his official capacity as Commander of the Navy Personnel Command and\nDeputy Chief of Naval Personnel,\n\n Defendants - Appellees.\n\n\n\nAppeal from the United States District Court for the Eastern District of Virginia, at\nAlexandria. Claude M. Hilton, Senior District Judge. (1:17-cv-01464-CMH-MSN)\n\n\nArgued: December 11, 2018 Decided: January 16, 2019\n\fBefore WILKINSON, AGEE, and THACKER, Circuit Judges.\n\n\nAffirmed by published opinion. Judge Wilkinson wrote the opinion, in which Judge Agee\nand Judge Thacker joined.\n\n\nARGUED: Matthew Jeffrey MacLean, PILLSBURY WINTHROP SHAW PITTMAN\nLLP, Washington, D.C., for Appellants. Tyce R. Walters, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C., for Appellees. ON BRIEF: Laura B.\nLoBue, Jeetander Dulani, Washington, D.C., Kenneth W. Taber, Matthew F. Putorti,\nNicholas M. Buell, PILLSBURY WINTHROP SHAW PITTMAN LLP, New York, New\nYork, for Appellants. Eric Proshansky, Melanie C.T. Ash, Eric Lee, Claude S. Platton,\nZachary W. Carter, CORPORATION COUNSEL OF THE CITY OF NEW YORK,\nNEW YORK CITY LAW DEPARTMENT, New York, New York, for Appellant City of\nNew York. Dennis J. Herrera, Yvonne R. Mere, Owen J. Clements, SAN FRANCISCO\nCITY ATTORNEY’S OFFICE, San Francisco, California, for Appellant City and County\nof San Francisco. Marcel S. Pratt, Eleanor N. Ewing, Benjamin H. Field, CITY OF\nPHILADELPHIA LAW DEPARTMENT, Philadelphia, Pennsylvania, for Appellant City\nof Philadelphia. Joseph H. Hunt, Assistant Attorney General, Mark B. Stern, Civil\nDivision, UNITED STATES DEPARTMENT OF JUSTICE, Washington, D.C.; G.\nZachary Terwilliger, United States Attorney, OFFICE OF THE UNITED STATES\nATTORNEY, Alexandria, Virginia; Michael J. Fucci, Associate General Counsel,\nUNITED STATES DEPARTMENT OF DEFENSE, Washington, D.C., for Appellees.\n\n\n\n\n 2\n\fWILKINSON, Circuit Judge:\n\n Appellants are three municipalities who use the National Instant Criminal\n\nBackground Check System to carry out their obligations under state law. This system,\n\nknown as the NICS, is managed by the Federal Bureau of Investigation. The Department\n\nof Defense (DOD) is required under federal law to provide records to the NICS but has\n\npersistently been unable to fully carry out this obligation. The appellants sued DOD and\n\nits constituent military departments to compel the department’s more thorough\n\ncompliance. The district court dismissed their claim, holding both that the appellants\n\nlacked constitutional standing and failed to establish subject matter jurisdiction under the\n\nAdministrative Procedure Act. For the following reasons, we affirm.\n\n\n\n I.\n\n A.\n\n The responsibility to combat gun violence falls on every level of government. Law\n\nenforcement officials, whether local, state, or federal, work to prevent senseless gun\n\nviolence and are often the first to risk their lives to protect our communities. Working\n\nalongside these officers are many other governmental partners, including agencies of the\n\nfederal government. The dispute here grows out of a program that facilitates information\n\nsharing between federal agencies and local law enforcement officials: The National\n\nInstant Criminal Background Check System.\n\n The Brady Handgun Violence Prevention Act, or Brady Act, established the first\n\nnationwide system for background checks. Pub. L. No. 103-159, 107 Stat. 1536 (1993).\n\n 3\n\fUnder the law, enacted in 1993, a background check was required for firearms sales by\n\nlicensed dealers. Id. § 102. The Brady Act directed the Attorney General to establish a\n\nnational database that would be accessible to the firearms dealers tasked with ensuring\n\nthese background checks were performed. Id. § 102(b). To implement the statute, the\n\nAttorney General established the National Instant Criminal Background Check System\n\n(NICS) and delegated control of the system to the Federal Bureau of Investigation (FBI).\n\n The NICS contains records for individuals who are prohibited from possessing a\n\nfirearm. The system draws from many distinct federal databases that contain\n\ndisqualifying records and relies on information submitted from across the federal\n\ngovernment. In the military context, DOD provides information regarding current and\n\nformer service members who are disqualified from owning a gun because of a prior\n\nconviction. The Brady Act also empowers the Attorney General to request records from\n\nother agencies that may possess disqualifying information. Id. § 103(e) (codified at 34\n\nU.S.C. § 40901(e) (2018)).\n\n As originally designed, state law enforcement agencies were required to\n\nadminister the Brady Act’s background checks on a temporary basis while the new\n\nnational background check system was established. The division of responsibility\n\nenvisioned by Congress was altered by the Supreme Court’s decision in Printz v. United\n\nStates, which found that “[t]he Federal Government may [not] command the States’\n\nofficers, or those of their political subdivisions, to administer or enforce a federal\n\nregulatory program.” 521 U.S. 898, 935 (1997). As the law now stands, states are not\n\nrequired to perform any functions associated with the Brady Act, although a state may\n\n 4\n\fvoluntarily play a role. For states that elect to participate, a “point of contact” is\n\ndesignated to “serv[e] as the intermediary between [a dealer] and the federal databases\n\nchecked by the NICS.” 28 C.F.R. § 25.2 (2017).\n\n This does not mean that state and local governments have no use of the\n\ninformation stored in the NICS. To the contrary, many states require law enforcement\n\nagencies to carry out a range of functions designed to prevent guns from reaching\n\ndangerous hands. Depending on the particulars of state law, a local law enforcement\n\nagency may perform checks associated with issuing permits and licenses, or may review\n\ndisqualifying information before transferring a gun that is in the state’s possession. For\n\nexample, the City of Philadelphia, a party to this case, is required to process applications\n\nfor licenses to carry firearms under Pennsylvania law. See 18 Pa. Cons. Stat. § 6109. The\n\nother municipal appellants have similar obligations.\n\n The Attorney General has long permitted state and local agencies, including the\n\nappellants, to access the NICS for these purposes. In 1998, the FBI promulgated a rule\n\nallowing state and local law enforcement to use the NICS when “issu[ing] a firearm-\n\nrelated or explosives-related permit or license,” including concealed-carry permits. See\n\nNational Instant Criminal Background Check System Regulation, 63 Fed. Reg. 58,303,\n\n58,309 (Oct. 30, 1998) (codified at 28 C.F.R. § 25.6(j)(1)). In 2014, a new rule further\n\nexpanded NICS access, allowing state and local agencies to access the system when\n\ndisposing of firearms in their possession. See National Instant Criminal Background\n\nCheck System Regulation, 79 Fed. Reg. 69,047, 69,048 (Nov. 20, 2014) (codified at 28\n\nC.F.R. § 25.6(j)(3)). The regulations clearly state that these uses of the NICS are\n\n 5\n\fpermissive, intended as a service, and “unrelated to NICS background checks required by\n\nthe Brady Act.” 28 C.F.R. § 25.6(j).\n\n At times, local law enforcement officials have pushed for even greater access. For\n\ninstance, the FBI’s 1998 rulemaking noted that some local agencies wanted permission to\n\naccess the database to determine if a person was in “unlawful possession of a firearm.” 63\n\nFed. Reg. at 58,305. The FBI resisted these requests. In the FBI’s view, such expanded\n\nuse would potentially run afoul of federal privacy laws. Id. Moreover, the FBI noted that\n\nthe Brady Act only required agency reporting for the purpose of carrying out the federal\n\nbackground check provisions, rather than for a wider range of law enforcement activities.\n\nId. The permissive use regulations therefore account for the requirements of federal law,\n\nthe informational needs of local law enforcement, and the privacy concerns of the\n\naffected individuals. In arriving at the scheme in place today, the FBI has shown a\n\nwillingness to expand NICS access to support local partners, but has apparently not gone\n\nas far as some of those partners may desire.\n\n The comprehensiveness and accuracy of the NICS has been a subject of frequent\n\ndebate and attention. See, e.g., U.S. Gov’t Accountability Office, GAO/T-GGD-00-163,\n\nGun Control: Improving the National Instant Criminal Background Check System (June\n\n21, 2000). At the federal level, many agencies possess disqualifying information that\n\nwould be relevant to a background check. Under the original Brady Act, federal agencies\n\nwere required to furnish information to the Attorney General upon request. See Pub. L.\n\nNo. 103-159, § 103(e)(1) (1993) (codified as amended at 34 U.S.C. § 40901(e)(1)).\n\n\n\n 6\n\f Following the fatal shooting of 32 students and faculty at Virginia Tech in 2007,\n\nCongress enacted new legislation to improve the NICS. See NICS Improvement\n\nAmendments Act of 2007 (NIAA), Pub. L. No. 110-180, 121 Stat. 2559 (2008). Finding\n\nthat “nearly 21,000,000 criminal records are not accessible by NICS and millions of\n\ncriminal records are missing critical data, such as arrest dispositions, due to backlogs,”\n\nthe legislation imposed new reporting requirements and authorized new grants to assist\n\nstates. Id. §§ 101, 103-104. To improve inter-agency information sharing, the Act\n\nimposed an affirmative duty on agencies to report disqualifying information on a\n\nquarterly basis. Id. § 101(a) (codified at 34 U.S.C. § 40901(e)(1)(C)-(D)). To incentivize\n\ncompliance, the Attorney General is required to provide an annual report to Congress on\n\neach agency’s success. Id. (codified at 34 U.S.C. § 40901(e)(1)(E)).\n\n The Department of Defense (DOD) has long struggled to comply with the NIAA’s\n\naffirmative reporting provision, a deficiency the department readily admits. Response Br.\n\nat 1. The DOD Inspector General reviewed the program in 2015 and found that a\n\nsubstantial percentage of required records were not being submitted to the FBI. U.S.\n\nDep’t of Def. Inspector Gen., Evaluation of Department of Defense Compliance with\n\nCriminal History Data Reporting Requirements 9 (Feb. 12, 2015). Similar findings were\n\nmade again in 2017. U.S. Dep’t of Def. Inspector Gen., Evaluation of Fingerprint Card\n\nand Final Disposition Report Submissions by Military Service Law Enforcement\n\nOrganizations (Dec. 4, 2017). On November 5, 2017, a gunman opened fire at a church in\n\nSutherland Springs, Texas, killing 26 people and injuring an additional 20. The gunman\n\nwas a former member of the military who had been convicted in court-martial\n\n 7\n\fproceedings. According to the municipal appellants, the gunman would not have been\n\nable to obtain a firearm if DOD complied with its reporting obligations under the NIAA.\n\n Following the devastating loss of life at Sutherland Springs, Congress again\n\namended the statute governing the NICS to improve inter-agency reporting. The Fix\n\nNICS Act, Pub. L. No. 115-141, Div. S, Title VI (2018), required federal agencies with\n\ndisqualifying records to submit semiannual certification reports to the Attorney General\n\nand develop compliance plans to improve their own performance. Id. § 602. Like the\n\nearlier amendment, this law also includes measures designed to hold poor performers\n\naccountable. First, the law requires that the Attorney General notify Congress of non-\n\ncompliant agencies and publish a list of those agencies on the DOJ website. Second, the\n\nlaw makes political appointees at non-compliant agencies ineligible for bonus pay until\n\nthe agency improves. Id. § 602(1) (codified at 34 U.S.C. § 40901(e)(1)(F)-(I)).\n\n In the time since the Sutherland Springs shooting, components of the Department\n\nof Defense have taken a wide range of actions to correct their deficiencies. Efforts\n\ninclude the creation of new task forces and compliance plans, as well as the development\n\nof new technological processes to streamline reporting. See J.A. 302-16. For example,\n\nthe Army has, in recent months, provided new records for nearly 33,000 disqualified\n\npersons to the NICS.\n\n B.\n\n The tragic shooting in Sutherland Springs also gave rise to this litigation. The\n\nappellants are three municipalities, all of whom use the NICS database to fulfill their\n\nrequirements under state law. They brought this suit to compel DOD’s full reporting of\n\n 8\n\fdisqualifying information to the Attorney General, as required by the NIAA. Since\n\nneither the Brady Act nor the NIAA contemplated a separate cause of action to compel\n\nperformance with inter-agency reporting obligations, the municipal appellants brought\n\ntheir claim under the general provision of the Administrative Procedure Act that allows\n\nan aggrieved party to “compel agency action unlawfully withheld or unreasonably\n\ndelayed.” 5 U.S.C. § 706(1) (2012).\n\n The district court granted the federal defendants’ motion to dismiss this claim,\n\nfinding that it lacked jurisdiction to hear the case. The court identified two independent\n\njurisdictional defects. First, the district court found that the municipal appellants had\n\nfailed “to allege[] a cognizable informational injury sufficient to confer standing.” J.A.\n\n341. Second, the court held that the cities did not establish “jurisdiction under the APA\n\nsince they have not alleged a discrete agency action.” Id. As a consequence of the\n\ndismissal, the court also denied the municipal appellants’ motion for a preliminary\n\ninjunction. Id. at 348.\n\n This appeal followed. While federal courts must assure themselves that they have\n\njurisdiction before proceeding to the merits, see Steel Co. v. Citizens for a Better Env’t,\n\n523 U.S. 83, 94-95 (1998), both of the infirmities identified by the district court go to the\n\nquestion of jurisdiction. As such, this court can turn to either issue alone to resolve this\n\ncase. See Ruhrgas AG v. Marathon Oil Co., 526 U.S. 574, 578 (1999) (“[T]here is no\n\nunyielding jurisdictional hierarchy.”). Our review is de novo.\n\n\n\n\n 9\n\f II.\n\n Because this court is not in “the habit of decid[ing] questions of a constitutional\n\nnature unless absolutely necessary,” we turn first to the statutory question of whether the\n\nmunicipal appellants have established subject matter jurisdiction under the\n\nAdministrative Procedure Act (APA). See Flue-Cured Tobacco Coop. Stabilization Corp.\n\nv. EPA, 313 F.3d 852, 857 (4th Cir. 2002) (quoting Ashwander v. Tenn. Valley Auth., 297\n\nU.S. 288, 347 (1936) (Brandeis, J. concurring)). At the outset, it is important to\n\nunderstand the nature of appellants’ claim. Their challenge is not about access to the\n\nNICS; it is instead about the quality of the information in that system. By their own\n\nsubmission, each of the appellants accesses the NICS frequently to carry out their\n\nobligations under state law. This is thus not a case where appellants have asked for access\n\nprovided for in the regulations and have been denied. Instead, the municipalities see their\n\nexisting access to the NICS as an invitation to compel any federal inter-agency legal\n\nrequirement that may affect the quality of the information they receive. On their view, the\n\nAPA authorizes a recipient of government information to initiate a private action to\n\ncompel governmental conduct that might improve that information’s accuracy or\n\ncomprehensiveness. As we explain below, there is simply no basis in the APA’s text for\n\nsuch a broad incursion into internal agency management.\n\n A.\n\n The APA waives the federal government’s sovereign immunity for a limited set of\n\nsuits, brought by “a person suffering legal wrong because of agency action” to obtain\n\nrelief “other than money damages.” 5 U.S.C. § 702. It is well-established that\n\n 10\n\f“[s]overeign immunity is jurisdictional in nature” and “absent a waiver . . . shields the\n\nFederal Government and its agencies from suit.” FDIC v. Meyer, 510 U.S. 471, 475\n\n(1994). Judicial review under the APA, moreover, is limited to “final agency actions.”\n\n5 U.S.C. § 704.\n\n As these provisions of the APA make plain, subject matter jurisdiction is lacking if\n\nthe plaintiff fails to challenge a particular “agency action” that is fit for review. See\n\nInvention Submission Corp. v. Rogan, 357 F.3d 452, 460 (4th Cir. 2004). “The term\n\n‘action’ as used in the APA is a term of art that does not include all conduct” on the part\n\nof the government. Vill. of Bald Head Island v. U.S. Army Corps of Eng’rs, 714 F.3d 186,\n\n193 (4th Cir. 2013). See also Hearst Radio v. FCC, 167 F.2d 225, 227 (D.C. Cir. 1948)\n\n(“The difficulty with the appellant company’s position is that the Administrative\n\nProcedure Act does not provide review for everything done by an agency.”). Instead, the\n\nAPA defines “agency action” to include “the whole or a part of an agency rule, order,\n\nlicense, sanction, relief, or the equivalent or denial thereof, or failure to act.” 5 U.S.C.\n\n§ 551(13).\n\n This definition limits the scope of judicial review in two important respects. First,\n\neach of the terms that comprise the definition of “agency action” is limited to those acts\n\nthat are “circumscribed” and “discrete.” Norton v. Southern Utah Wilderness Alliance\n\n(SUWA), 542 U.S. 55, 62 (2004). When challenging agency action―whether it be a\n\nparticular action or a failure to act altogether―the plaintiff must therefore identify\n\nspecific and discrete governmental conduct, rather than launch a “broad programmatic\n\nattack” on the government’s operations. Id. at 64. This distinction between discrete acts,\n\n 11\n\fwhich are reviewable, and programmatic challenges, which are not, is vital to the APA’s\n\nconception of the separation of powers. Courts are well-suited to reviewing specific\n\nagency decisions, such as rulemakings, orders, or denials. We are woefully ill-suited,\n\nhowever, to adjudicate generalized grievances asking us to improve an agency’s\n\nperformance or operations. In such a case, courts would be forced either to enter a\n\ndisfavored “obey the law” injunction, see Int’l Longshoremen’s Ass’n, Local 1291 v.\n\nPhil. Mar. Trade Ass’n, 389 U.S. 64, 76 (1967), or to engage in day-to-day oversight of\n\nthe executive’s administrative practices. Both alternatives are foreclosed by the APA, and\n\nrightly so. The Supreme Court’s guidance on this point is worth considering in full:\n\n If courts were empowered to enter general orders compelling compliance\n with broad statutory mandates, they would necessarily be empowered, as\n well, to determine whether compliance was achieved-which would mean\n that it would ultimately become the task of the supervising court, rather\n than the agency, to work out compliance with the broad statutory mandate,\n injecting the judge into day-to-day agency management.\n\nSUWA, 542 U.S. at 66-67. The requirement that the challenger identify a discrete act\n\nkeeps us from entering such a quagmire.\n\n Second, the definition of “agency action” is limited to those governmental acts\n\nthat “determin[e] rights and obligations.” Clear Sky Car Wash LLC v. City of\n\nChesapeake, Va., 743 F.3d 438, 445 (4th Cir. 2014). This limitation ensures that judicial\n\nreview does not reach into the internal workings of the government, and is instead\n\nproperly directed at the effect that agency conduct has on private parties. To meet this\n\nrequirement, a party must demonstrate that the challenged act had “an immediate and\n\npractical impact,” see Golden & Zimmerman LLC v. Domenech, 599 F.3d 426, 433 (4th\n\n\n 12\n\fCir. 2010), or “alter[ed] the legal regime” in which it operates. See Bennett v. Spear, 520\n\nU.S. 154, 178 (1997). It is not enough for plaintiffs to simply identify a governmental\n\naction that ultimately affected them through the “independent responses and choices of\n\nthird parties,” or mere “coercive pressures.” Flue-Cured Tobacco, 313 F.3d at 859, 861.\n\nThis requirement applies fully to claims that an agency has failed to act, which is\n\n“properly understood as a failure to take an agency action.” See Norton, 542 U.S. at 62.\n\nSince “agency actions” must determine rights and obligations, claims to compel an\n\nagency to take an action must seek such a determination as well.\n\n These two requirements, which flow directly from the APA’s text, apply to all\n\nchallenges to agency action and accordingly limit judicial review generally. When a\n\nplaintiff brings a claim to compel agency action, like the municipal appellants have here,\n\na further limit applies. Under the APA, actions that can be compelled are only those that\n\nhave been “unlawfully withheld or unreasonably delayed.” 5 U.S.C. § 706(1). As the\n\nSupreme Court has explained, the text of § 706(1) requires that the plaintiff identify\n\naction that is “legally required.” SUWA, 542 U.S. at 63. Just like the traditional\n\nmandamus remedy from which this provision is derived, claims to compel agency action\n\nare “limited to enforcement of ‘a specific, unequivocal command,’” over which an\n\nofficial has no discretion. Id. (quoting ICC v. New York, N.H. & H.R. Co., 287 U.S. 178,\n\n204 (1932)).\n\n Taken together, the limitations imposed on claims to compel agency action under\n\nthe APA strike a balance between meaningful judicial review and the needs of effective\n\nadministration. Review is available only when acts are discrete in character, required by\n\n 13\n\flaw, and bear on a party’s rights and obligations. The result is a scheme allowing courts\n\nto review only those acts that are specific enough to avoid entangling the judiciary in\n\nprogrammatic oversight, clear enough to avoid substituting judicial judgments for those\n\nof the executive branch, and substantial enough to prevent an incursion into internal\n\nagency management. See SUWA, 542 U.S. at 64-65.\n\n These principles guide our consideration of all claims to compel agency action,\n\nregardless of the context. Claims involving government information are no exception.\n\nOur court, just like our sister circuits, has had many occasions to consider how the\n\nrequirements of agency action apply to claims that the government has wrongfully\n\nhandled the information in its possession. In some cases, the claim is that the\n\ngovernment’s decision to disseminate information, such as an unfavorable report, was\n\nunlawful. See Invention Submission Corp., 357 F.3d at 460; see also Flue-Cured\n\nTobacco, 313 F.3d at 859; Indus. Safety Equip. Ass’n, Inc. v. EPA, 837 F.2d 1115, 1118\n\n(D.C. Cir. 1988). At other times, the claim was that the government improperly withheld\n\nor mishandled personal information. See, e.g., Fanin v. U.S. Dep’t of Veterans Affairs,\n\n572 F.3d 868, 871 (11th Cir. 2009). Informational harms may involve novel facts, but\n\nthey do not disrupt the legal principles set forth in the APA. See Golden & Zimmerman,\n\nLLC, 599 F.3d at 431-32 (finding that an agency’s “reference guide” was not agency\n\naction because it did not “impose new legal requirements”). As these cases aptly\n\ndemonstrate, a plaintiff’s burden remains constant and subject to the above requirements\n\nthroughout.\n\n\n\n 14\n\f B.\n\n Applying these well-established principles to the facts here, it is clear that the\n\nmunicipal appellants have failed to establish subject matter jurisdiction under the APA.\n\nOnce again, the claim at issue arises from the appellants’ permissive use of the NICS,\n\nafforded to them by regulation, for purposes explicitly “unrelated to the NICS\n\nbackground checks required by the Brady Act.” 28 C.F.R. § 25.6(j). The regulation\n\naffords the municipalities only “access to the NICS Index.” Id. On the view of the\n\nmunicipal appellants, this access, which is not expressly contemplated either by the\n\nBrady Act or subsequent legislation, allows a NICS user to reach into the federal\n\ngovernment and compel any legal obligations associated with developing the information\n\nin the system. Such a broad theory of agency action is untethered from the APA’s text\n\nand contravenes important limits that Congress has placed on judicial review.\n\n First, the municipal appellants’ claim does not challenge a discrete agency action.\n\nInstead appellants ask that we “supervise an agency’s compliance with [the] broad\n\nstatutory mandate” of the NIAA. Murray Energy Corp. v. EPA, 861 F.3d 529, 537 n.4\n\n(4th Cir. 2017). By appellants’ own account, the DOD’s failure to provide disqualifying\n\nconviction records for former service members is widespread and systemic. The\n\ndepartment has admitted as much and is engaged in extensive efforts to increase its\n\ncompliance. As all parties seem to agree, the road ahead is an arduous one, as DOD\n\nattempts to improve on its partial and inconsistent reporting. This is the sort of public\n\npolicy problem that often requires reallocating resources, developing new administrative\n\n 15\n\fsystems, and working closely with partners across government. Solving it will likely\n\nrequire expertise in information technology and deep knowledge of how military needs\n\nintersect with data collection. In other words, it is exactly the sort of “broad\n\nprogrammatic” undertaking for which the APA has foreclosed judicial review. See\n\nSUWA, 542 U.S. at 64.\n\n Congress seems to be of the same view. Since the passage of the Brady Act,\n\nCongress has on multiple occasions turned its attention to the severe challenge of\n\nrampant gun violence. Twice, the legislative responses have been directed squarely at\n\nagency compliance with NICS reporting obligations. Congress has included\n\naccountability measures, designed to identify delinquent agencies and push them into\n\nimproving their performance. The most recent effort in this regard singles out executive\n\ncompensation at these agencies, limiting bonus pay for those who do not improve their\n\noutcomes. See 34 U.S.C. § 40901(e)(1)(I) (providing that certain “political\n\nappointee[s] . . . shall not be eligible for the receipt of bonus pay” until their department\n\nimproves its compliance). These measures signal that Congress sees this problem as one\n\nripe for legislative oversight and in need of attention by experts in the executive branch.\n\nAt no point, however, has Congress invited the federal courts into the process. Perhaps\n\ncognizant of the judiciary’s inability to oversee and manage a complex scheme of inter-\n\nagency collaboration, we have appropriately been left on the sideline.\n\n The municipal appellants try to nonetheless force us onto the field by\n\ncharacterizing their broad claim as simply an aggregation of many small claims, each one\n\nseeking to compel the individual reports required by the NIAA. On this view, what the\n\n 16\n\fcities seek is not programmatic because each specific act that DOD has failed to perform\n\nis discrete when considered on its own. But any limit on programmatic assessment would\n\nbe rendered meaningless if such an argument prevailed. All governmental programs are\n\nthe aggregation of individual decisions, many of which are required by law. The APA\n\nensures that it is the individual decisions that are assessed as agency action, rather than\n\nthe whole administrative apparatus.\n\n The municipal appellants are surely correct that ongoing failures to carry out\n\ndiscrete obligations can be subject to review. Government deficiencies do not become\n\nnon-reviewable simply because they are pervasive. This, however, does nothing to\n\nobviate the fact that a discrete action is wholly lacking here. By the appellants’ own\n\nestimate, full compliance with the NIAA may require DOD to obtain and transmit tens of\n\nthousands of records. There is simply no way to achieve such a result without wholesale\n\nimprovements in the DOD’s reporting requirements, which take time and require the\n\nexpertise of senior civilian and military leaders.\n\n If there were any doubt about the nature of the cities’ claim, the requested remedy\n\ntells the real story. Their complaint “seeks immediate injunctive relief to compel\n\nDefendants to repair this broken system and to cure once and for all the potentially\n\ndeadly gaps in the NCIC database.” J.A. 17. In their prayer for relief, the appellants ask\n\nthat the DOD, on “a schedule to be set by the Court,” “identify all records” in its\n\npossession, provide the information contained in those records to the Attorney General,\n\n“conduct a thorough review of [its] records and procedures,” “submit to the Court for\n\napproval a compliance plan,” and provide “a monthly report to the Court detailing [its]\n\n 17\n\fprogress.” Id. at 35-36. The requested relief would continue “until such time as the Court\n\nis satisfied that Defendants have brought themselves into full compliance with 34 U.S.C.\n\n§ 40901.” Id. at 36 (emphasis added). The APA’s discreteness requirement exists to avoid\n\nplacing the courts in this exact position. As we previously explained, “[t]he obvious\n\ninability for a court to function in such a day-to-day managerial role over agency\n\noperations is precisely the reason why the APA limits judicial review to discrete agency\n\nactions.” Vill. of Bald Head Island, 714 F.3d at 194.\n\n Moreover, the municipal appellants have failed to demonstrate that the DOD’s\n\nreporting requirements in any way determine their rights and obligations. Accordingly,\n\nthey have not identified an act that can be compelled by this court under § 706(1). See\n\nSUWA, 542 U.S. at 62 (finding that a failure to act under § 706(1) means “failure to take\n\nan agency action”). The action challenged in this case is DOD’s obligation to provide\n\ninformation only to another agency of the federal government: The Department of\n\nJustice. See 34 U.S.C. § 40901(e)(1)(C). The regulation permitting local law enforcement\n\nagencies to use the NICS refers only to access to the system, not to the particular\n\ninformation provided to the FBI by other federal agencies. The transfer of information\n\nbetween agencies does not, without more, alter the rights and obligations of any party.\n\nThat is especially true, as here, where outside access to the information is entirely\n\npermissive and implicates none of the complaining party’s obligations under federal law.\n\n We need not say here that information sharing can never constitute agency action.\n\nWe simply note that claims to compel an agency to provide information are held to the\n\nsame standard as any other. In arguing otherwise, the municipal appellants point to a\n\n 18\n\fstring of cases, all from outside this circuit, holding that the government’s alleged misuse\n\nof information was reviewable “agency action.” Our holding here, however, raises no\n\nconflict with these decisions. The cases relied on by the appellants involve claims wholly\n\nunlike the one that they have brought. For example, one case involves the government’s\n\nlegal obligations with respect to the plaintiffs’ personal medical information, see Vietnam\n\nVeterans of Am. v. CIA, 811 F.3d 1068, 1078 (9th Cir. 2015) (finding that “the Army\n\n[has] a duty to provide notice to prior test subjects of information regarding their well-\n\nbeing”), while another examines the rights of federal employees under the civil service\n\nsystem, see Hondros v. U.S. Civil Service Comm., 720 F.2d 278, 280 (3d Cir. 1983). Each\n\nof these cases involved plaintiffs seeking information that was particular to them and\n\ntheir own rights under federal law. As such, they tell us little about how to handle a case,\n\nlike this one, where the plaintiff seeks wholesale compliance with an entire\n\nadministrative scheme, based solely on the fact that the government has granted them\n\naccess to an information system.\n\n\n\n C.\n\n What the municipal appellants are ultimately asking for is a judicial decree making\n\nthe assistance of the federal government more useful to them than it is now. While their\n\nmotives for wanting to see improvement to the NICS are laudable, they point to no case\n\nsuggesting that the APA countenances such an action. And for good reason. If a party\n\ncould seek review any time the federal government’s alleged non-compliance made a\n\ngovernment program less useful than it might otherwise be, the possibilities for litigation\n\n 19\n\fwould be endless. Followed to its logical conclusion, a recipient of the mail could sue the\n\nPostal Service for improper employment practices, alleging that it caused inefficient\n\npackage deliveries. A disgruntled grant applicant could sue the National Institutes of\n\nHealth for violations of financial management laws, arguing that with more money in its\n\ncoffers more grants could be issued. The APA, however, is a creature of Congress; the\n\nlegislative branch has not put it to this sort of use, and we can discern no workable limits\n\nin the appellants’ theory.\n\n The implications of the appellants’ position are particularly troubling in the\n\ncontext of voluntary information sharing. The federal government has access to a vast\n\namount of data that is of great use both to intergovernmental partners and to those in the\n\nprivate sector. Information stored with the federal government is critical to many areas of\n\npublic policy, including, for example, homeland security and healthcare. See, e.g., Nat’l\n\nInfrastructure Advisory Council, Intelligence Information Sharing: Final Report and\n\nRecommendations ES-1 (Jan. 10, 2012) (“Information sharing is perhaps the most\n\nimportant factor in the protection and resilience of critical infrastructure.”). The federal\n\ngovernment has recently taken steps to make more of its own information accessible to\n\nthe general public, aware of the innovative potential that such information can unleash.\n\nSee Exec. Order No. 13,642, 78 Fed. Reg. 28,111 (May 9, 2013); see generally Data.gov\n\n(“The home of the U.S. Government’s open data.”). If we adopted the all-encompassing\n\ndefinition of “agency action” asserted by the municipal appellants here, each of these\n\nefforts to enhance public access would be checked by a fear that greater openness would\n\ninvite judicial scrutiny of any act that went into developing or disseminating the data.\n\n 20\n\fWith an agency’s eye peeled towards these consequences, it is easy to imagine the federal\n\ngovernment pulling back from these salutary efforts, and instead choosing to silo its\n\ninformation.\n\n The adverse consequences of appellants’ theory would not just fall on the\n\ngovernment’s attempt to share information with the public; they would also compromise\n\nthe dissemination of information within the government itself. A rule that made inter-\n\nagency information sharing justiciable by federal courts would undermine the whole\n\ngamut of federal activities that require collaboration between agencies, of which military\n\npreparedness and anti-terrorism efforts are only a part. Agencies dealing with public\n\nhealth, environment conservation, and disaster response draw on entire bodies of\n\nscientific work, and not all of the needed expertise will be located within a single agency\n\nor department. To have internal information sharing haunted by the specter of judicial\n\noversight would weaken government operations in innumerable areas, both foreign and\n\ndomestic, and allow the prospect of litigation to erect barriers when other nations, both\n\nour allies and our competitors, proceed unburdened by similar obstacles.\n\n\n\n III.\n\n The municipal appellants, like localities all over the country, are tasked with\n\nkeeping the public safe from horrific acts of violence, which far too often are committed\n\nby those with firearms they had no lawful right to possess. The municipalities’ efforts to\n\ncombat these threats are commendable. The APA, however, does not permit their efforts\n\nto include judicial supervision of the myriad programmatic workings of the federal\n\n 21\n\fgovernment. No matter the asserted virtues of the intended intervention, we are simply\n\nnot equipped to perform such tasks and have no legal basis for doing so.\n\n For the foregoing reasons, the judgment of the district court is\n\n AFFIRMED.\n\n\n\n\n 22\n[END_CASE]", "role": "user" } ]
4,583,961
SAVE OUR SOUND OBX, INC.; Mark Haines ; Jer Mehta; Glenn Stevens ; David Hadley ; Thomas Aschmoneit; Richard Ayella, Plaintiffs - Appellants, v. NORTH CAROLINA DEPARTMENT OF TRANSPORTATION; Federal Highway Administration; John F. Sullivan, III, in His Official Capacity as Division Administrator for the Federal Highway Administration; James H. Trogdon, III, in His Official Capacity as Secretary of the North Carolina Department of Transportation, Defendants - Appellees, and Defenders of Wildlife; National Wildlife Refuge Association, Intervenors/Defendants - Appellees.
Save Our Sound OBX, Inc. v. NC Dept of Transportation
2019-01-23
18-1649
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Niemeyer, Duncan, Quattlebaum", "parties": "", "opinions": [{"author": "DUNCAN, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1649\n\n\nSAVE OUR SOUND OBX, INC.; MARK HAINES; JER MEHTA; GLENN\nSTEVENS; DAVID HADLEY; THOMAS ASCHMONEIT; RICHARD\nAYELLA,\n\n Plaintiffs – Appellants,\n\nv.\n\nNORTH CAROLINA DEPARTMENT OF TRANSPORTATION; FEDERAL\nHIGHWAY ADMINISTRATION; JOHN F. SULLIVAN, III, in his official\ncapacity as Division Administrator for the Federal Highway Administration;\nJAMES H. TROGDON, III, in his official capacity as Secretary of the North\nCarolina Department of Transportation,\n\n Defendants – Appellees,\n\nand\n\nDEFENDERS OF WILDLIFE; NATIONAL WILDLIFE REFUGE\nASSOCIATION,\n\n Intervenors/Defendants – Appellees.\n\n\nAppeal from the United States District Court for the Eastern District of North Carolina, at\nElizabeth City. Louise W. Flanagan, District Judge. (2:17-cv-00004-FL)\n\n\nArgued: December 11, 2018 Decided: January 23, 2019\n\n\nBefore NIEMEYER, DUNCAN, and QUATTLEBAUM, Circuit Judges.\n\fAffirmed by published opinion. Judge Duncan wrote the opinion, in which Judge\nNiemeyer and Judge Quattlebaum joined.\n\n\nARGUED: David Ari Schnitzer, GIBSON, DUNN & CRUTCHER LLP, Washington,\nD.C., for Appellants. Thekla Hansen-Young, UNITED STATES DEPARTMENT OF\nJUSTICE, Washington, D.C.; Colin Justice, NORTH CAROLINA DEPARTMENT OF\nJUSTICE, Raleigh, North Carolina, for Appellees. ON BRIEF: Michael K. Murphy,\nKyle N. Guest, GIBSON, DUNN & CRUTCHER LLP, Washington, D.C., for\nAppellants. Jeffrey H. Wood, Acting Assistant Attorney General, Eric Grant, Deputy\nAssistant Attorney General, Andrew C. Mergen, Robert J. Lundman, Carter F. Thurman,\nAppellate Section, Environment and Natural Resources Division, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C.; Josh Stein, Attorney General,\nOFFICE OF THE ATTORNEY GENERAL OF NORTH CAROLINA, Raleigh, North\nCarolina; Scott T. Slusser, Special Deputy Attorney General, Mollie Cozart, Assistant\nAttorney General, NORTH CAROLINA DEPARTMENT OF JUSTICE, Raleigh, North\nCarolina, for Appellees North Carolina Department of Transportation, Federal Highway\nAdministration, John F. Sullivan, III, and James H. Trogdon, III. Kimberley Hunter,\nNicholas S. Torrey, SOUTHERN ENVIRONMENTAL LAW CENTER, Chapel Hill,\nNorth Carolina, for Appellees Defenders of Wildlife and National Wildlife Refuge\nAssociation.\n\n\n\n\n 2\n\fDUNCAN, Circuit Judge:\n\n Appellants Save Our Sound OBX, Inc. and its members, residents and vacationers\n\nfrom North Carolina’s Outer Banks, (collectively “SOS”) challenge the decision of the\n\nNorth Carolina Department of Transportation (the “NCDOT”), the Federal Highway\n\nAdministration (the “FHWA”), and their administrators (collectively “the Agencies”) to\n\nreplace a segment of North Carolina Highway 12 (“NC-12”) with a bridge across the\n\nPamlico Sound (the “Jug-Handle Bridge”). The district court granted the Agencies’\n\nmotion for summary judgment, finding that they did not violate the National\n\nEnvironmental Policy Act (the “NEPA”), 42 U.S.C. § 4321 et seq., or the Department of\n\nTransportation Act (the “DTA”), 49 U.S.C. § 301 et seq., when they approved the bridge.\n\nSOS challenges that ruling on appeal. For the reasons that follow, we affirm.\n\n\n\n I.\n\n This case involves a segment of NC-12, which is the main roadway passing\n\nthrough the Outer Banks of North Carolina. State and federal agencies have been\n\nworking for several years to update and improve NC-12 because of its susceptibility to\n\nweather damage and erosion.\n\n Like many highway construction projects, the NC-12 project required cooperation\n\namong state and federal agencies. For instance, in North Carolina, NCDOT has authority\n\nover highway construction, while FWHA supplies federal funds for highway projects.\n\nThe agencies tasked with improving NC-12, including NCDOT and FHWA, formed a\n\nMerger Team to coordinate decisionmaking and regulatory compliance for the NC-12\n\n 3\n\fproject. 1 The Merger Team was responsible for ensuring that the NC-12 project\n\ncomplied with the requirements of NEPA and the DTA, among other regulations.\n\n SOS challenges certain agency decisions in the NC-12 project under NEPA and\n\nthe DTA. Accordingly, we first provide a brief overview of the requirements of those\n\nstatutes before turning to the specific facts and procedural history of this appeal.\n\n\n\n A.\n\n The first statute at issue in this appeal is NEPA. Pursuant to NEPA, 42 U.S.C.\n\n§ 4321 et seq., and its implementing regulations, government agencies considering\n\ncertain projects must evaluate whether the project would have a significant impact on the\n\nenvironment by preparing an Environmental Assessment (an “EA”). Id. § 4332(C); 40\n\nC.F.R. § 1508.9; see id. § 1508.18 (defining the types of federal actions to which NEPA\n\napplies). If the project would have a significant impact, the agency must prepare an\n\nEnvironmental Impact Statement (an “EIS”). 42 U.S.C. § 4332(C). The agency is\n\nresponsible for ensuring that the EIS complies with various regulatory requirements. See\n\n40 C.F.R. § 1502.1 et seq. For instance, the EIS must “provide full and fair discussion”\n\nof any significant environmental impacts of a proposed action. 40 C.F.R. § 1502.1.\n\n 1\n The Merger Team was comprised of representatives from NCDOT, FHWA, the\nU.S. Fish and Wildlife Service, the U.S. Army Corps of Engineers, the U.S.\nEnvironmental Protection Agency, the National Marine Fisheries Service, the National\nPark Service, the North Carolina Department of Cultural Resources, the North Carolina\nWildlife Resources Commission, and three divisions of the North Carolina Department of\nEnvironmental and Natural Resources (the “NCDENR”) (now named the North Carolina\nDepartment of Environmental Quality)--the Division of Water Resources, the Division of\nCoastal Management, and the Division of Marine Fisheries.\n\n 4\n\fAdditionally, the agency must “[r]igorously explore and objectively evaluate all\n\nreasonable alternatives” that could “avoid or minimize adverse impacts.” Id.\n\n§§ 1502.1, 1502.14. The agency is permitted, however, to identify a preference among\n\nalternatives based on non-environmental considerations, such as economic factors or the\n\nagency’s statutory mission. Id. § 1505.2(b). If the agency has a preferred alternative,\n\nNEPA requires the agency to identify that preference in the EIS. Id. § 1502.14. NEPA\n\nalso requires the agency to prepare a supplemental EIS (an “SEIS”) if significant new\n\ninformation or environmental changes come to light after the agency prepares an EIS. Id.\n\n§ 1502.9(c). After the agency makes its final decision about which alternative to pursue,\n\nit publishes a record of decision (an “ROD”) explaining its choice. Id. § 1505.2.\n\n We now turn to the second statute at issue: the DTA. The DTA contains\n\nsubstantive requirements for government transportation projects. 49 U.S.C. § 301 et seq.\n\nRelevant here, the so-called “§ 4(f)” requirements 2 concern transportation projects that\n\nrequire the use of publicly owned land of a wildlife refuge or a significant historic site.\n\nId. § 303(c). Historic sites include structures “included in, or eligible for inclusion in,”\n\nthe National Register of Historic Places. 23 C.F.R. § 774.17. The Secretary of\n\nTransportation may only approve such projects if there is no “feasible and prudent”\n\nalternative to using that land and the “project includes all possible planning to minimize\n\nharm . . . resulting from the use.” Id. § 303(c). If there is no feasible and prudent\n\n\n 2\n The DTA explains that “[t]he requirements of [49 U.S.C. § 303] are commonly\nreferred to as section 4(f) requirements” in reference to a previous version of the statute.\n49 U.S.C. § 303(f)(1).\n\n 5\n\falternative, the Secretary may only approve the alternative that “[c]auses the least overall\n\nharm in light of the [DTA’s] preservation purpose.” 23 C.F.R. § 774.3(c). Relevant\n\nconsiderations in selecting the least harmful alternative include whether harm to the land\n\ncan be mitigated, whether harm to the land affects the attributes qualifying that land for\n\nprotection, and whether the alternative meets the needs of the project. Id.\n\n\n\n B.\n\n Having established the relevant framework, we consider the facts of this case.\n\nSOS’s claims in this litigation concern the Agencies’ environmental analysis under\n\nNEPA and the DTA with respect to a segment of NC-12 that passes from the southern\n\nedge of Bodie Island to the village of Rodanthe. For this segment, the Merger Team was\n\nresponsible for preparing EAs and EISs pursuant to NEPA and for determining which\n\nproposed plan for the project was the least environmentally-damaging practicable\n\nalternative (the “LEDPA”) pursuant to section 404 of the Clean Water Act, 33 U.S.C.\n\n§ 1344, among other requirements. 3 See 40 C.F.R. § 230.10 (setting out the LEDPA\n\nrequirement).\n\n In 2008, the Merger Team issued an EIS and § 4(f) evaluation (the “2008 EIS”)\n\nfor improving NC-12. For the segment at issue here, the 2008 EIS included discussion of\n\nseveral alternatives, including a proposed bridge in the Pamlico Sound near Rodanthe\n\n\n\n 3\n Section 404 of the Clean Water Act regulates activities involving “the discharge\nof dredged or fill material” into navigable waters. Id.\n\n 6\n\f(the “Bridge South alternative”) and proposals involving beach nourishment. An EA in\n\n2010 (the “2010 EA”) further developed these alternatives.\n\n The Merger Team released an updated EA in 2013 (the “2013 EA”) to account for\n\nenvironmental changes after the 2010 EA, including the effects of Hurricane Irene in\n\n2011. The 2013 EA identified four alternatives for the segment at issue: (1) the so-called\n\nJug-Handle Bridge, a bridge extending out into the Pamlico Sound (also referred to in the\n\nenvironmental analyses as the “Bridge on New Location”); 4 (2) an easement bridge on\n\nthe existing NC-12 location; (3) beach nourishment; and (4) an easement bridge\n\ncombined with beach nourishment. The Merger Team did not study the beach\n\nnourishment alternatives in depth in the 2013 EA because, at a 2011 meeting, it had\n\nalready determined not to pursue them after experts reported on a “high erosion rate and a\n\nlack of sand supply.” J.A. 843. In the 2013 EA, the Merger Team identified the\n\neasement bridge as its preferred alternative under NEPA. However, certain members of\n\nthe Merger Team objected to finding that the easement bridge was the LEDPA under the\n\nClean Water Act, citing concerns about its location within the surf zone, additional\n\npermits associated with erosion setback requirements, and its impact on a nearby wildlife\n\nrefuge. See J.A. 1745–47.\n\n In the meantime, environmental groups Defenders of Wildlife and the National\n\nWildlife Refuge Association (intervenors here, collectively the “Environmental Groups”)\n\nbrought suit in federal court to challenge the Agencies’ NEPA and § 4(f) determinations\n\n 4\n The Jug-Handle Bridge was a modified version of the Bridge South alternative\nthat was introduced in the 2008 EIS and further developed in the 2010 EA.\n\n 7\n\fwith respect to a different segment of NC-12 in the Outer Banks--the Bonner Bridge,\n\nwhich connects Bodie Island and Hatteras Island to the north of Rodanthe. See Defs. of\n\nWildlife v. N.C. Dep’t of Transp., 762 F.3d 374 (4th Cir. 2014). The Environmental\n\nGroups and the Agencies eventually reached an agreement in 2015 (the “Settlement”). 5\n\nThe Settlement required NCDOT to identify the Jug-Handle Bridge as its preferred\n\nalternative for the segment of NC-12 at issue in this case. It also required NCDOT to\n\nseek Merger Team concurrence that the Jug-Handle Bridge was the LEDPA. In doing so,\n\nit stated that nothing in the Settlement “requires or should be interpreted to predetermine\n\nthe choice” of the Jug-Handle Bridge as the final selected alternative. J.A. 1090. In\n\nexchange, the Environmental Groups dismissed the Bonner Bridge suit and agreed not to\n\nchallenge the Agencies in court if the Jug-Handle Bridge was determined to be the\n\nLEDPA and was ultimately selected in the ROD for this project.\n\n After a 2015 meeting, the Agencies identified the Jug-Handle Bridge as their\n\npreferred alternative. Following public comment and detailed studies, the Merger Team\n\ndetermined that the Jug-Handle Bridge was the LEDPA. In 2016, the Merger Team\n\nreleased a revised EA (the “2016 EA”) to evaluate the environmental impacts of the Jug-\n\nHandle Bridge and its associated construction activities. Later that year, the Merger\n\nTeam issued an ROD (the “2016 ROD”) formally approving the Jug-Handle Bridge.\n\n In addition to authorizing construction of the Jug-Handle Bridge, the 2016 ROD\n\nalso addressed concerns relating to a shipwreck in the proposed bridge’s path known as\n\n 5\n NCDENR was also a party to the Settlement and is represented on the Merger\nTeam, though it is not a defendant here.\n\n 8\n\fthe Pappy’s Lane Wreck. The shipwreck is eligible for listing on the National Register of\n\nHistoric Places. Because of the shipwreck’s historical significance, the 2016 ROD\n\nordered a data recovery project on the shipwreck, which later uncovered evidence that the\n\nshipwreck was a World War II assault vessel. The Merger Team has not yet determined\n\nhow it will respond to this new information.\n\n\n\n C.\n\n We now turn to the procedural history of this litigation, which began when SOS\n\nsued the Agencies on February 2, 2017. A month later, the Environmental Groups\n\nintervened in the suit in support of the Agencies. In its complaint, SOS alleged, as\n\nrelevant here, that the Agencies’ approval of the Jug-Handle Bridge violated NEPA\n\nbecause that decision was predetermined by the Settlement. To show evidence of\n\npredetermination, SOS moved to supplement the administrative record before the district\n\ncourt to include documents related to the negotiation of the Settlement on the grounds\n\nthat those documents were before the Agencies when they made their decision to select\n\nthe Jug-Handle Bridge. The district court denied this motion.\n\n Later, SOS moved to amend its complaint to add claims related to construction\n\nimpacts in Rodanthe and to the Pappy’s Lane Wreck. Specifically, SOS contended that\n\nthe Agencies’ environmental analyses did not adequately consider the effects of\n\nconstruction or the historic significance of the Pappy’s Lane Wreck. The district court\n\ngranted the motion as to construction impacts but denied it as to the shipwreck.\n\n\n\n 9\n\f SOS, the Agencies, and the Environmental Groups each filed cross-motions for\n\nsummary judgment on the issue of whether the Agencies’ environmental analyses\n\nviolated NEPA or the DTA. The district court granted the Agencies’ and Environmental\n\nGroups’ motions for summary judgment and denied SOS’s motion.\n\n SOS appeals the district court’s grant of the Agencies’ motion for summary\n\njudgment and its denial of SOS’s motion to amend its complaint. SOS contends that the\n\nAgencies were not entitled to summary judgment because the Agencies’ environmental\n\nanalyses violated NEPA. It also contends that the district court erred in denying SOS’s\n\nmotion to amend its complaint with claims related to the Pappy’s Lane Wreck. We\n\ndiscuss SOS’s NEPA claims and its motion to amend its complaint, in that order.\n\n\n\n II.\n\n SOS contends that the Agencies violated NEPA when they selected the Jug-\n\nHandle Bridge for the NC-12 project. “We review a grant of summary judgment de\n\nnovo,” Defs. of Wildlife, 762 F.3d at 392, and, accordingly, review the Agencies’ actions\n\ndirectly, pursuant to the Administrative Procedure Act (the “APA”). The APA directs us\n\nto overturn agency actions if they are “arbitrary, capricious, an abuse of discretion, or\n\notherwise not in accordance with law.” 5 U.S.C. § 706(2)(A). Our precedent also guides\n\nthe scope of our review of the sufficiency of an agency’s NEPA analysis. Nat’l Audubon\n\nSoc’y v. Dep’t of Navy, 422 F.3d 174, 185, 199 (4th Cir. 2005). In conducting this\n\nreview, “we must make a searching and careful inquiry into the facts” and examine\n\nwhether the decision was based on consideration of the relevant factors. Id. at 185\n\n 10\n\f(citation and internal quotation marks omitted). However, we do not “second-guess\n\nagency decisions, so long as the agency has given a hard look at the environmental\n\nimpacts of its proposed action.” Id. at 199.\n\n Under this standard of review, we affirm because the Agencies did not violate\n\nNEPA in approving the Jug-Handle Bridge. We consider SOS’s arguments that the\n\nAgencies’ environmental analyses violated NEPA because (1) the Agencies failed to\n\nprepare an SEIS with regards to the Jug-Handle Bridge and beach nourishment\n\nalternatives before issuing the 2016 ROD, (2) the Agencies failed to adequately consider\n\nthe impacts of construction, and (3) the Settlement impermissibly predetermined the\n\nAgencies’ choice of the Jug-Handle Bridge.\n\n\n\n A.\n\n First, SOS contends that the Agencies’ NEPA analysis was deficient because the\n\nAgencies should have prepared an SEIS before approving the Jug-Handle Bridge in the\n\n2016 ROD. NEPA requires an agency to prepare an SEIS if “[t]he agency makes\n\nsubstantial changes” to a proposed action that implicate environmental concerns or if\n\n“[t]here are significant new circumstances or information” that would affect the\n\nenvironmental impacts of the proposed action. 40 C.F.R. § 1502.9(c). To merit an SEIS,\n\nthe changes “must present a seriously different picture of the environmental impact of the\n\nproposed project.” Hughes River Watershed Conservancy v. Glickman, 81 F.3d 437, 443\n\n(4th Cir. 1996) (citation and alterations omitted).\n\n\n\n 11\n\f We review an agency’s decision not to prepare an SEIS in two steps, consistent\n\nwith our standard of review under NEPA. Id. At step one, we “determine whether the\n\nagency took a hard look at the proffered new information.” Id. If the agency concludes\n\nafter a preliminary inquiry that the “environmental effect of the change is clearly\n\ninsignificant,” its decision not to prepare an SEIS satisfies the hard look requirement.\n\nHodges v. Abraham, 300 F.3d 432, 446 (4th Cir. 2002). For instance, in Hodges, we held\n\nthat an agency took a hard look at the environmental consequences of its change in plans\n\nwhen it explicitly evaluated those consequences and determined that they were not\n\nsignificantly different from those discussed in a prior EIS. Id. at 447. We also noted that\n\nthe plaintiff in that case “failed to identify any particular risk arising from” the change\n\nthat had not already been addressed in the agency’s environmental analyses. Id. Next, at\n\nstep two of the SEIS inquiry, we review whether the agency’s decision not to prepare an\n\nSEIS after taking a hard look was arbitrary or capricious. Hughes River, 81 F.3d at 443.\n\n SOS contends that an SEIS was necessary (1) to evaluate the environmental\n\neffects of the Jug-Handle Bridge alternative because it was different from options that\n\nhad previously been evaluated and (2) to reconsider alternatives that involved beach\n\nnourishment pursuant to new information about sand availability and beach erosion rates.\n\nWe address each contention in turn and affirm the district court’s determination that no\n\nSEIS was required. Neither of these changes are sufficiently different from the\n\ncircumstances initially evaluated in the EIS to merit an SEIS. The Agencies’ decision not\n\nto prepare one after taking a hard look at the changes was therefore not arbitrary or\n\ncapricious.\n\n 12\n\f i.\n\n Contrary to SOS’s contention, the Agencies were not required to prepare an SEIS\n\nwith respect to the Jug-Handle Bridge alternative. SOS argues that the final alignment of\n\nthe Jug-Handle Bridge alternative (that is, its path across the Pamlico Sound and its\n\nconnection points with the shore) was significantly different from previously evaluated\n\nalternatives. Specifically, SOS contends that the bridge’s alignment changed\n\nsignificantly because the alternative evaluated in the 2008 EIS was “amorphously\n\ndefined” and because the alternative evaluated in the 2010 EA (to which the 2013 EA,\n\n2016 EA, and 2016 ROD refer) was “not comparable” to the Jug-Handle Bridge.\n\nAppellant’s Br. at 35, 36. It argues that these differences render prior environmental\n\nanalyses of those alternatives insufficient to evaluate the environmental effects of the\n\nJug-Handle Bridge as approved in the 2016 ROD. We disagree and conclude that the\n\nAgencies complied with NEPA when they decided that an SEIS was not warranted by\n\nthese changes.\n\n At step one, the Agencies took a hard look at changes in the bridge’s alignment in\n\nthe 2016 EA. The 2016 EA describes the similarities and differences between the Jug-\n\nHandle Bridge as proposed in 2016 and the versions evaluated in the 2013 EA, the 2010\n\nEA, and the 2008 EIS. For instance, it explains that the Agencies decided to shift the\n\nalignment of the bridge to avoid areas of “dense submerged aquatic vegetation” that fell\n\nin the path of previous versions of the bridge. J.A. 1198. The 2016 EA also explains that\n\nthe Jug-Handle Bridge’s alignment reduces effects on the community as compared with\n\n 13\n\fprevious versions because it requires a narrower right-of-way. Because the Agencies\n\nwent into detail in their comparison between the Jug-Handle Bridge and previous\n\nversions of the bridge, their coverage satisfies the hard look requirement. See Hodges,\n\n300 F.3d at 446–47.\n\n And, at step two, because the Agencies took the requisite hard look and neither\n\ntheir environmental analyses nor SOS identify any particular differences that would merit\n\nan SEIS, their decision not to prepare an SEIS was not arbitrary or capricious. See\n\nHughes River, 81 F.3d at 443. An SEIS is only required when changes to a project\n\npresent a “seriously different picture of the environmental impact.” Id. (alterations and\n\ncitation omitted). Based on the discussion presented in the 2016 EA, which compared the\n\ndifferent versions of the bridge, it was not arbitrary or capricious for the Agencies to\n\ndetermine that the Jug-Handle Bridge’s final alignment did not present a “seriously\n\ndifferent picture,” id., than the 2008 EIS, the 2010 EA, or the 2013 EA. The Agencies\n\nexplained how the Jug-Handle Bridge was different from previous versions of the bridge,\n\nand their explanations do not implicate any significant environmental concerns.\n\nAccordingly, their decision not to prepare an SEIS was not arbitrary or capricious.\n\n\n\n ii.\n\n Similarly, the Agencies were not required to prepare an SEIS to reevaluate the\n\nfeasibility of alternatives that involved beach nourishment. SOS contends that the\n\nAgencies failed to adequately reconsider beach nourishment after new erosion projections\n\nwere released and after a 2014 emergency beach nourishment project in the area\n\n 14\n\fsuccessfully repaired damage from Hurricane Sandy. According to SOS, this new\n\ninformation showed that coastal conditions had changed such that erosion would no\n\nlonger threaten beach nourishment and that adequate sand was in fact available to\n\ncomplete the project.\n\n However, the Agencies took the requisite hard look at these new circumstances in\n\nthe 2016 EA. See Hughes River, 81 F.3d at 443. The 2016 EA notes that while erosion\n\nprojections in the Rodanthe area did decrease, erosion rates in Rodanthe remained\n\n“amongst the highest rates along the North Carolina coast.” J.A. 1218. It also discusses\n\nthe 2014 emergency beach nourishment project in detail and considers updated\n\ninformation about coastal conditions in the area. Specifically, it notes that the 2014\n\nemergency beach nourishment project was “essentially one round of nourishment in one\n\npart of [NC-12].” J.A. 1227. Finally, it concludes that the Agencies thoroughly\n\nconsidered the environmental effects of beach nourishment when they originally\n\nevaluated those alternatives in the 2008 EIS. This detailed discussion satisfies the hard\n\nlook requirement. See Hodges, 300 F.3d at 446–47.\n\n And after taking that hard look, the Agencies’ decision not to prepare an SEIS was\n\nnot arbitrary or capricious. See Hughes River, 81 F.3d at 443. SOS cites improved\n\nerosion rates and an increased supply of sand as new factors that the Agencies should\n\nhave considered when deciding whether to prepare an SEIS. However, erosion and sand\n\nsupply were not the Agencies’ only reasons for initially rejecting beach nourishment in\n\nthe 2008 EIS. The Agencies also cited independent concerns such as inadequate\n\nprotection against future breaches, risks of overwash, and incompatibility with the\n\n 15\n\fmission of a neighboring wildlife refuge. It was not arbitrary or capricious for the\n\nAgencies to decline to reconsider beach nourishment alternatives in an SEIS when the\n\nnew information proffered by SOS did not implicate all of the Agencies’ independently\n\nadequate reasons for initially rejecting beach nourishment.\n\n Accordingly, the Agencies were not required to prepare an SEIS to consider the\n\nalignment of the Jug-Handle Bridge or to consider beach nourishment alternatives. Their\n\nenvironmental analyses therefore do not violate NEPA in this respect.\n\n\n\n B.\n\n SOS also contends that the Agencies’ environmental analyses violate NEPA\n\nbecause they do not adequately consider the environmental effects of construction in the\n\nRodanthe area. Specifically, SOS argues that the effects of construction traffic and haul\n\nroads are not adequately addressed in the 2016 EA and that any discussion of these issues\n\nin the 2008 EIS is irrelevant because that document focuses on a larger area.\n\n NEPA requires agencies to consider all “significant environmental impacts,” 40\n\nC.F.R. § 1502.1, which can include impacts caused by the use of construction roads and\n\nincreased traffic. See, e.g., Arlington Coal. on Transp. v. Volpe, 458 F.2d 1323, 1332\n\n(4th Cir. 1972) (explaining that NEPA applies to highway construction projects).\n\nAccordingly, if construction roads and traffic are expected to affect the environment near\n\nan agency project, the agency must provide “full and fair discussion” of those effects and\n\nincorporate them into its comparison of alternatives. 40 C.F.R. § 1502.1.\n\n\n\n 16\n\f Here, the Agencies adequately considered the effects of construction traffic as a\n\nresult of the Jug-Handle Bridge in the 2016 ROD. Specifically, the Agencies explained\n\nthat a temporary construction easement would be necessary to support traffic during\n\nconstruction but noted that “[t]he land affected will be restored after construction is\n\ncompleted.” J.A. 1559. While the 2016 ROD does not compare the construction traffic\n\neffects of the Jug-Handle Bridge with those of other proposed alternatives, the Agencies\n\ndid perform that comparison in the 2013 EA and the 2016 EA and still found the bridge\n\nto be the LEDPA. The Agencies also specifically considered the environmental effects of\n\nhaul roads in the 2008 EIS. 6\n\n We therefore cannot say that the Agencies did not provide “full and fair\n\ndiscussion” of the effects of construction traffic or haul roads when they selected the Jug-\n\nHandle Bridge among alternatives. See 40 C.F.R. § 1502.1. Accordingly, the Agencies\n\ndid not violate NEPA here, and we affirm the district court.\n\n\n\n\n 6\n To be sure, that discussion did not explicitly consider haul roads in the Rodanthe\narea. However, it is unclear from the record whether the Agencies actually plan to use\nhaul roads for the Jug-Handle Bridge project. See, e.g., J.A. 214 (containing a\ndeclaration from an NCDOT engineer stating that NCDOT and its contractor decided not\nto pursue a previously-discussed haul road in connection with a barge because shallow\nwater depths would make it impracticable). Regardless, NEPA does not compel the\nAgencies to specifically consider the environmental impacts of haul roads so long as they\nadequately examine the environmental consequences of the Jug-Handle Bridge project,\nincluding construction impacts, as a whole. See 40 C.F.R. § 1502.2(b) (“Impacts shall be\ndiscussed [in the EIS] in proportion to their significance.”).\n\n 17\n\f C.\n\n Finally, SOS contends that the Agencies violated NEPA because their choice of\n\nthe Jug-Handle Bridge did not follow from their NEPA analysis but, rather, was a\n\npredetermined result of the Settlement. NEPA “prohibits agencies from preparing an EIS\n\nsimply to ‘justify [] decisions already made.’” Nat’l Audubon Soc’y, 422 F.3d at 199\n\n(quoting 40 C.F.R. § 1502.2(g)) (alteration in original). That is because, under NEPA,\n\nagencies that have yet to issue a final decision may not “commit resources prejudicing\n\nselection of alternatives,” 40 C.F.R. § 1502.2(f), nor may they take any action that would\n\n“[l]imit the choice of reasonable alternatives,” 40 C.F.R. § 1506.1(a). An EIS based upon\n\na predetermined choice that a certain alternative will be selected would violate these\n\nprinciples because it would not allow the agency to fully consider all alternatives.\n\n We conclude that the Agencies’ choice of the Jug-Handle Bridge was not\n\nimpermissibly predetermined. We consider, in turn, the Agencies’ objective\n\nenvironmental analyses, the language of the Settlement, and the role of documents\n\ngenerated during negotiation of the Settlement.\n\n\n\n i.\n\n First, SOS contends that flaws in the Agencies’ environmental analyses reveal that\n\ntheir choice of the Jug-Handle Bridge was predetermined by the Settlement. In alleging\n\nthat the environmental analyses were inadequate, it primarily relies upon arguments that\n\nwe have already discussed--namely, that the Agencies failed to fully consider the new\n\nalignment of the bridge, the feasibility of beach nourishment alternatives, and the effects\n\n 18\n\fof construction traffic and haul roads. SOS contends that these flaws exist because the\n\nAgencies prematurely decided to choose the Jug-Handle Bridge after the Settlement.\n\n Under our precedent, “the evidence we look to in determining whether\n\n[predetermination] has taken place consists of the environmental analysis itself.” 7 Nat’l\n\nAudubon Soc’y, 422 F.3d at 199. In National Audubon Society, in reviewing allegations\n\nthat an agency had settled on a certain outcome before preparing its EIS, we declined to\n\nlook to the agency’s internal documents and emails. Id. Instead, we limited the scope of\n\nour inquiry to the agency’s objective environmental analysis, reasoning that “[w]here an\n\nagency has merely engaged in post hoc rationalization, there will be evidence of this in its\n\nfailure to comprehensively investigate the environmental impact of its actions and\n\nacknowledge their consequences.” Id. Accordingly, our analysis focuses on whether an\n\nagency’s objective environmental analyses demonstrate evidence of predetermination.\n\n Here, when we examine Agencies’ environmental analyses, we cannot say that\n\nthey violated NEPA by selecting the Jug-Handle Bridge following the Settlement. To be\n\nsure, the Agencies changed their preferred alternative from the easement bridge to the\n\nJug-Handle Bridge following the Settlement. But that change alone does not mean that\n\nthe Agencies’ choice was predetermined, particularly where members of the Merger\n\nTeam had expressed concerns about the easement bridge as far back as 2013. And when\n\nwe look to the Agencies’ environmental analyses here, those analyses satisfied NEPA’s\n\n\n 7\n We note that some circuits look beyond the objective environmental analysis for\nevidence of predetermination. See, e.g., Forest Guardians v. U.S. Fish & Wildlife Serv.,\n611 F.3d 692, 716–17 (10th Cir. 2010) (declining to adopt the Fourth Circuit’s rule).\n\n 19\n\frequirements. See discussion supra Sections II.A., II.B. We do not see, and SOS cannot\n\nidentify, any evidence that the Agencies “fail[ed] to comprehensively investigate” and\n\nevaluate the environmental impacts of the Jug-Handle Bridge or the other alternatives.\n\nNat’l Audubon Soc’y, 422 F.3d at 199. The EAs and EIS prepared by the Agencies do\n\nnot, on their faces, show evidence of predetermination.\n\n SOS cites to cases from the Ninth and Tenth Circuits to contend that courts have\n\nfound predetermination based on contractual commitments made by an agency before the\n\nNEPA process was complete. See Davis v. Mineta, 302 F.3d 1104, 1112 (10th Cir. 2002)\n\n(holding that a contract requiring a consultant to recommend that a project had no\n\nsignificant environmental impact before actually preparing an EA violated NEPA);\n\nMetcalf v. Daley, 214 F.3d 1135, 1145 (9th Cir. 2000) (same, regarding a contract\n\nrequiring an agency to make a proposal for a specific alternative before preparing an EA).\n\nHowever, these cases are distinguishable because they involved contracts that agencies\n\nentered into before conducting any environmental analysis at all; in contrast, the\n\nSettlement here, which the Agencies and the Environmental Groups entered into in 2015,\n\nwas preceded by a number of environmental analyses, including the 2008 EIS, the 2010\n\nEA, and the 2013 EA. And when we examine each of these environmental analyses, we\n\nfind no evidence of predetermination warranting reversal.\n\n\n\n ii.\n\n Although circuit precedent limits our predetermination inquiry to the\n\n“environmental analysis itself,” id., SOS nonetheless urges us to consider the Settlement\n\n 20\n\fas evidence that the Agencies’ choice was predetermined. But even if we look to the\n\nSettlement, that document does not support SOS’s claim. The Settlement only required\n\nNCDOT to identify the Jug-Handle Bridge as its preferred alternative and to seek Merger\n\nTeam concurrence that the Jug-Handle Bridge was the LEDPA. These conditions do not\n\nrequire the Agencies to select the Jug-Handle Bridge as the final approved alternative for\n\nthis project. For instance, it remained possible that the Agencies’ environmental analyses\n\nwould demonstrate that the Jug-Handle Bridge was not the LEDPA. Additionally, the\n\nAgencies’ preferences alone could not bind the entire Merger Team, which was\n\nultimately responsible for approving the final alternative, because the parties to the\n\nSettlement comprise only three of the ten state and federal agencies represented on the\n\nMerger Team. 8 This does not constitute predetermination.\n\n\n\n iii.\n\n SOS also urges us to consider external documents generated during the negotiation\n\nof the Settlement as evidence of predetermination and to reverse the district court’s denial\n\nof SOS’s motion to include these documents in the record. We decline to do so because\n\nthe district court did not abuse its discretion in denying this motion. See Fort Sumter\n\nTours, Inc. v. Babbitt, 66 F.3d 1324, 1335–36 (4th Cir. 1995) (explaining that we review\n\n 8\n To be sure, the parties to the Settlement represented three of the four Lead\nAgencies tasked with decisionmaking if the Merger Team could not reach consensus.\nBut, as discussed, the Settlement only required those agencies to seek concurrence that\nthe Jug-Handle Bridge was the LEDPA; it did not require them to go beyond the\nobjective environmental analysis to choose the Jug-Handle Bridge if it was not, in fact,\nthe LEDPA.\n\n 21\n\fa district court’s decision whether to expand the administrative record for abuse of\n\ndiscretion).\n\n Federal courts base their review of agency decisions on “the ‘whole record’\n\ncompiled by the agency.” Citizens to Pres. Overton Park, Inc. v. Volpe, 401 U.S. 402,\n\n419 (1971) (quoting 5 U.S.C. § 706), abrogated on other grounds by Califano v. Sanders,\n\n430 U.S. 99 (1977). We may supplement the record as presented by the agency if the\n\n“bare record” does not reveal the agency’s reasoning or if it appears that the agency acted\n\nin bad faith. Id. at 420. Otherwise, “inquiry into the mental processes of administrative\n\ndecisionmakers is usually to be avoided.” Id.\n\n Here, the record as presented by the Agencies reveals their reasoning, as we have\n\ndiscussed, and the district court found no evidence that the Agencies acted in bad faith.\n\nThe district court also determined that there was no evidence that the Agencies actually\n\nreviewed the documents put forth by SOS as part of their decision to approve the Jug-\n\nHandle Bridge. We hold that the district court did not abuse its discretion by denying\n\nSOS’s motion to supplement the record, and accordingly, our review is limited to the\n\nrecord as compiled by the Agencies.\n\n SOS contends that, even if we cannot consider these documents as part of the\n\nadministrative record, we should nevertheless consider them as extra-record evidence. It\n\nis true that “in the NEPA context, courts generally have been willing to look outside the\n\nrecord when assessing the adequacy of an EIS or a determination that no EIS is\n\nnecessary.” Ohio Valley Envtl. Coal. v. Aracoma Coal Co., 556 F.3d 177, 201 (4th Cir.\n\n2009). However, we have explained that extra-record evidence in that context is\n\n 22\n\fprimarily useful “to inform the court about environmental factors that the agency may not\n\nhave considered.” Id. (emphasis added). Here, the proffered documents would do\n\nnothing to aid the court’s understanding of the environmental concerns at issue, as they\n\nconcern the legal terms of the Settlement between the Agencies and the Environmental\n\nGroups. Therefore, the district court properly excluded them, and we decline to consider\n\nthem now.\n\n There is superficial appeal in suggesting that the Agencies’ choice was\n\npredetermined because the Settlement yielded a preferred alternative. However, that\n\nconclusion is not legally or factually supported by the record. Legally, our analysis is\n\ncabined to the environmental analysis itself, with which we find no issues meriting\n\nreversal. And factually, we see no evidence that the Merger Team was forced to approve\n\nthe Jug-Handle Bridge.\n\n In sum, the Agencies did not violate NEPA when they approved the Jug-Handle\n\nBridge because they were not required to prepare an SEIS, they adequately evaluated the\n\neffects of construction traffic, and they did not rely on a predetermined choice among\n\nalternatives. We therefore affirm the district court’s grant of summary judgment in favor\n\nof the Agencies.\n\n\n\n III.\n\n Finally, SOS contends that the district court erred when it denied SOS’s motion to\n\namend its complaint with claims related to the Pappy’s Lane Wreck. Specifically, SOS\n\nalleges that the Agencies violated § 4(f) by approving a transportation project that\n\n 23\n\fthreatens to harm the land of a site of historic significance because the Jug-Handle Bridge\n\nwill pass above the wreck--the site of a World War II vessel.\n\n We review a district court’s denial of a motion to amend the complaint for abuse\n\nof discretion. See Laber v. Harvey, 438 F.3d 404, 428 (4th Cir. 2006) (en banc).\n\nHowever, if the district court denied such a motion on the grounds that the amendment\n\nwould have been futile, we review its legal conclusions de novo. United States ex. rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n A party “may amend its pleading once as a matter of course” before the opposing\n\nparty files a responsive pleading. Fed. R. Civ. P. 15(a)(1). After that time, a party may\n\nonly amend its pleading with the consent of the opposing party or with leave of the court,\n\nand “[t]he court should freely give leave when justice so requires.” Fed. R. Civ. P.\n\n15(a)(2). Courts may deny leave to amend a pleading if the amendment would have been\n\nfutile. Laber, 438 F.3d at 426. A proposed amendment is futile when it is “clearly\n\ninsufficient or frivolous on its face.” Johnson v. Oroweat Foods Co., 785 F.2d 503, 510\n\n(4th Cir. 1986). A proposed amendment is also futile if the claim it presents would not\n\nsurvive a motion to dismiss. Perkins v. United States, 55 F.3d 910, 917 (4th Cir. 1995).\n\n Here, the district court found that SOS’s proposed amendment would be futile for\n\ntwo alternative reasons. First, it determined that, to the extent that SOS sought to assert\n\nthat the 2016 EA was no longer valid in light of new information about the shipwreck,\n\nthat claim would be unripe where the Agencies had not yet made a decision concerning\n\nthe significance of the new information. Second, it determined that, to the extent that\n\nSOS sought to assert that the 2016 EA was inadequate when issued, that claim would fail\n\n 24\n\fbecause it would ask the Agencies to consider information that was not discovered until\n\nafter the 2016 EA was issued. For the reasons that follow, we affirm the district court’s\n\ndenial of SOS’s motion to amend its complaint.\n\n First, to the extent that SOS’s proposed amendments contend that the Agencies\n\nfailed to consider new information about the shipwreck, those amendments would be\n\nfutile because they would raise a claim that is not yet ripe for review. 9 Courts may only\n\nreview “final agency action,” 5 U.S.C. § 704, and challenges to agency decisions that are\n\nyet to be made are not ripe for review. See Pashby v. Delia, 709 F.3d 307, 317 (4th Cir.\n\n2013) (holding that a claim is only ripe when it involves a formalized administrative\n\ndecision). Here, the Agencies have not yet made a final decision about the significance\n\nof new information revealing that the shipwreck was a World War II assault vessel.\n\nTherefore, any claim that the Agencies did not properly account for this information\n\nwould be unripe, and any amendment seeking to add such a claim would be futile.\n\n Second, SOS contends on appeal that it is challenging the adequacy of the 2016\n\nROD’s treatment of the Pappy’s Lane Wreck rather than the Agencies’ failure to consider\n\nnew information about the shipwreck’s significance. Specifically, SOS contends that,\n\nbecause the Agencies knew that the shipwreck was eligible for listing on the National\n\n\n 9\n SOS appears to have abandoned this argument on appeal. See Appellants’ Br. at\n53 (contending that the district court “fundamentally misread [SOS’s] motion” when it\ndenied it on ripeness grounds because “[t]he [new] allegations were about the\ninadequacies of the [2016] ROD and the process leading up to that document”)\n(emphasis added). Nevertheless, we discuss it because it implicates concerns related to\nthe argument that SOS does raise on appeal regarding the adequacy of the 2016 ROD\nwhen issued.\n\n 25\n\fRegister of Historic Places, they were not authorized to build a bridge in its path unless\n\nthey determined that there was “no prudent and feasible alternative to using that land”\n\nand that the “project include[d] all possible planning to minimize harm . . . resulting from\n\nthe use.” See 49 U.S.C. § 303(c).\n\n However, as the district court explained, SOS cannot contend that it was\n\nchallenging the adequacy of the 2016 ROD’s treatment of the shipwreck when its claims\n\n“rest[] upon recent discovery that the Pappy[’s] Lane Wreck contains a World War II\n\nvessel.” Save Our Sound OBX, Inc. v. N.C. Dep’t of Transp., No. 2:17-CV-4-FL, 2017\n\nWL 7048561, at *5 (E.D.N.C. Dec. 5, 2017). Instead, the Agencies satisfied regulatory\n\nrequirements when, based on what they knew about the Pappy’s Lane Wreck, they\n\nordered data recovery and decided that the shipwreck did not merit preservation in place.\n\nArguments that the Agencies should have gone further are grounded in new information\n\nand, therefore, not reviewable until the Agencies issue a final decision, as discussed\n\nabove. We therefore affirm the district court’s denial of SOS’s motion to amend its\n\ncomplaint.\n\n\n\n IV.\n\n We affirm the district court because the Agencies did not violate NEPA or the\n\nDTA when they issued the 2016 ROD selecting the Jug-Handle Bridge and because the\n\ndistrict court did not abuse its discretion when it denied SOS’s motions to supplement the\n\nadministrative record and to amend the complaint.\n\n AFFIRMED\n\n 26", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361214/", "author_raw": "DUNCAN, Circuit Judge:"}]}
NIEMEYER
DUNCAN
QUATTLEBAUM
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4583961/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: SAVE OUR SOUND OBX, INC.; Mark Haines ; Jer Mehta; Glenn Stevens ; David Hadley ; Thomas Aschmoneit; Richard Ayella, Plaintiffs - Appellants, v. NORTH CAROLINA DEPARTMENT OF TRANSPORTATION; Federal Highway Administration; John F. Sullivan, III, in His Official Capacity as Division Administrator for the Federal Highway Administration; James H. Trogdon, III, in His Official Capacity as Secretary of the North Carolina Department of Transportation, Defendants - Appellees, and Defenders of Wildlife; National Wildlife Refuge Association, Intervenors/Defendants - Appellees.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-23\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 18-1649\n\n\nSAVE OUR SOUND OBX, INC.; MARK HAINES; JER MEHTA; GLENN\nSTEVENS; DAVID HADLEY; THOMAS ASCHMONEIT; RICHARD\nAYELLA,\n\n Plaintiffs – Appellants,\n\nv.\n\nNORTH CAROLINA DEPARTMENT OF TRANSPORTATION; FEDERAL\nHIGHWAY ADMINISTRATION; JOHN F. SULLIVAN, III, in his official\ncapacity as Division Administrator for the Federal Highway Administration;\nJAMES H. TROGDON, III, in his official capacity as Secretary of the North\nCarolina Department of Transportation,\n\n Defendants – Appellees,\n\nand\n\nDEFENDERS OF WILDLIFE; NATIONAL WILDLIFE REFUGE\nASSOCIATION,\n\n Intervenors/Defendants – Appellees.\n\n\nAppeal from the United States District Court for the Eastern District of North Carolina, at\nElizabeth City. Louise W. Flanagan, District Judge. (2:17-cv-00004-FL)\n\n\nArgued: December 11, 2018 Decided: January 23, 2019\n\n\nBefore NIEMEYER, DUNCAN, and QUATTLEBAUM, Circuit Judges.\n\fAffirmed by published opinion. Judge Duncan wrote the opinion, in which Judge\nNiemeyer and Judge Quattlebaum joined.\n\n\nARGUED: David Ari Schnitzer, GIBSON, DUNN & CRUTCHER LLP, Washington,\nD.C., for Appellants. Thekla Hansen-Young, UNITED STATES DEPARTMENT OF\nJUSTICE, Washington, D.C.; Colin Justice, NORTH CAROLINA DEPARTMENT OF\nJUSTICE, Raleigh, North Carolina, for Appellees. ON BRIEF: Michael K. Murphy,\nKyle N. Guest, GIBSON, DUNN & CRUTCHER LLP, Washington, D.C., for\nAppellants. Jeffrey H. Wood, Acting Assistant Attorney General, Eric Grant, Deputy\nAssistant Attorney General, Andrew C. Mergen, Robert J. Lundman, Carter F. Thurman,\nAppellate Section, Environment and Natural Resources Division, UNITED STATES\nDEPARTMENT OF JUSTICE, Washington, D.C.; Josh Stein, Attorney General,\nOFFICE OF THE ATTORNEY GENERAL OF NORTH CAROLINA, Raleigh, North\nCarolina; Scott T. Slusser, Special Deputy Attorney General, Mollie Cozart, Assistant\nAttorney General, NORTH CAROLINA DEPARTMENT OF JUSTICE, Raleigh, North\nCarolina, for Appellees North Carolina Department of Transportation, Federal Highway\nAdministration, John F. Sullivan, III, and James H. Trogdon, III. Kimberley Hunter,\nNicholas S. Torrey, SOUTHERN ENVIRONMENTAL LAW CENTER, Chapel Hill,\nNorth Carolina, for Appellees Defenders of Wildlife and National Wildlife Refuge\nAssociation.\n\n\n\n\n 2\n\fDUNCAN, Circuit Judge:\n\n Appellants Save Our Sound OBX, Inc. and its members, residents and vacationers\n\nfrom North Carolina’s Outer Banks, (collectively “SOS”) challenge the decision of the\n\nNorth Carolina Department of Transportation (the “NCDOT”), the Federal Highway\n\nAdministration (the “FHWA”), and their administrators (collectively “the Agencies”) to\n\nreplace a segment of North Carolina Highway 12 (“NC-12”) with a bridge across the\n\nPamlico Sound (the “Jug-Handle Bridge”). The district court granted the Agencies’\n\nmotion for summary judgment, finding that they did not violate the National\n\nEnvironmental Policy Act (the “NEPA”), 42 U.S.C. § 4321 et seq., or the Department of\n\nTransportation Act (the “DTA”), 49 U.S.C. § 301 et seq., when they approved the bridge.\n\nSOS challenges that ruling on appeal. For the reasons that follow, we affirm.\n\n\n\n I.\n\n This case involves a segment of NC-12, which is the main roadway passing\n\nthrough the Outer Banks of North Carolina. State and federal agencies have been\n\nworking for several years to update and improve NC-12 because of its susceptibility to\n\nweather damage and erosion.\n\n Like many highway construction projects, the NC-12 project required cooperation\n\namong state and federal agencies. For instance, in North Carolina, NCDOT has authority\n\nover highway construction, while FWHA supplies federal funds for highway projects.\n\nThe agencies tasked with improving NC-12, including NCDOT and FHWA, formed a\n\nMerger Team to coordinate decisionmaking and regulatory compliance for the NC-12\n\n 3\n\fproject. 1 The Merger Team was responsible for ensuring that the NC-12 project\n\ncomplied with the requirements of NEPA and the DTA, among other regulations.\n\n SOS challenges certain agency decisions in the NC-12 project under NEPA and\n\nthe DTA. Accordingly, we first provide a brief overview of the requirements of those\n\nstatutes before turning to the specific facts and procedural history of this appeal.\n\n\n\n A.\n\n The first statute at issue in this appeal is NEPA. Pursuant to NEPA, 42 U.S.C.\n\n§ 4321 et seq., and its implementing regulations, government agencies considering\n\ncertain projects must evaluate whether the project would have a significant impact on the\n\nenvironment by preparing an Environmental Assessment (an “EA”). Id. § 4332(C); 40\n\nC.F.R. § 1508.9; see id. § 1508.18 (defining the types of federal actions to which NEPA\n\napplies). If the project would have a significant impact, the agency must prepare an\n\nEnvironmental Impact Statement (an “EIS”). 42 U.S.C. § 4332(C). The agency is\n\nresponsible for ensuring that the EIS complies with various regulatory requirements. See\n\n40 C.F.R. § 1502.1 et seq. For instance, the EIS must “provide full and fair discussion”\n\nof any significant environmental impacts of a proposed action. 40 C.F.R. § 1502.1.\n\n 1\n The Merger Team was comprised of representatives from NCDOT, FHWA, the\nU.S. Fish and Wildlife Service, the U.S. Army Corps of Engineers, the U.S.\nEnvironmental Protection Agency, the National Marine Fisheries Service, the National\nPark Service, the North Carolina Department of Cultural Resources, the North Carolina\nWildlife Resources Commission, and three divisions of the North Carolina Department of\nEnvironmental and Natural Resources (the “NCDENR”) (now named the North Carolina\nDepartment of Environmental Quality)--the Division of Water Resources, the Division of\nCoastal Management, and the Division of Marine Fisheries.\n\n 4\n\fAdditionally, the agency must “[r]igorously explore and objectively evaluate all\n\nreasonable alternatives” that could “avoid or minimize adverse impacts.” Id.\n\n§§ 1502.1, 1502.14. The agency is permitted, however, to identify a preference among\n\nalternatives based on non-environmental considerations, such as economic factors or the\n\nagency’s statutory mission. Id. § 1505.2(b). If the agency has a preferred alternative,\n\nNEPA requires the agency to identify that preference in the EIS. Id. § 1502.14. NEPA\n\nalso requires the agency to prepare a supplemental EIS (an “SEIS”) if significant new\n\ninformation or environmental changes come to light after the agency prepares an EIS. Id.\n\n§ 1502.9(c). After the agency makes its final decision about which alternative to pursue,\n\nit publishes a record of decision (an “ROD”) explaining its choice. Id. § 1505.2.\n\n We now turn to the second statute at issue: the DTA. The DTA contains\n\nsubstantive requirements for government transportation projects. 49 U.S.C. § 301 et seq.\n\nRelevant here, the so-called “§ 4(f)” requirements 2 concern transportation projects that\n\nrequire the use of publicly owned land of a wildlife refuge or a significant historic site.\n\nId. § 303(c). Historic sites include structures “included in, or eligible for inclusion in,”\n\nthe National Register of Historic Places. 23 C.F.R. § 774.17. The Secretary of\n\nTransportation may only approve such projects if there is no “feasible and prudent”\n\nalternative to using that land and the “project includes all possible planning to minimize\n\nharm . . . resulting from the use.” Id. § 303(c). If there is no feasible and prudent\n\n\n 2\n The DTA explains that “[t]he requirements of [49 U.S.C. § 303] are commonly\nreferred to as section 4(f) requirements” in reference to a previous version of the statute.\n49 U.S.C. § 303(f)(1).\n\n 5\n\falternative, the Secretary may only approve the alternative that “[c]auses the least overall\n\nharm in light of the [DTA’s] preservation purpose.” 23 C.F.R. § 774.3(c). Relevant\n\nconsiderations in selecting the least harmful alternative include whether harm to the land\n\ncan be mitigated, whether harm to the land affects the attributes qualifying that land for\n\nprotection, and whether the alternative meets the needs of the project. Id.\n\n\n\n B.\n\n Having established the relevant framework, we consider the facts of this case.\n\nSOS’s claims in this litigation concern the Agencies’ environmental analysis under\n\nNEPA and the DTA with respect to a segment of NC-12 that passes from the southern\n\nedge of Bodie Island to the village of Rodanthe. For this segment, the Merger Team was\n\nresponsible for preparing EAs and EISs pursuant to NEPA and for determining which\n\nproposed plan for the project was the least environmentally-damaging practicable\n\nalternative (the “LEDPA”) pursuant to section 404 of the Clean Water Act, 33 U.S.C.\n\n§ 1344, among other requirements. 3 See 40 C.F.R. § 230.10 (setting out the LEDPA\n\nrequirement).\n\n In 2008, the Merger Team issued an EIS and § 4(f) evaluation (the “2008 EIS”)\n\nfor improving NC-12. For the segment at issue here, the 2008 EIS included discussion of\n\nseveral alternatives, including a proposed bridge in the Pamlico Sound near Rodanthe\n\n\n\n 3\n Section 404 of the Clean Water Act regulates activities involving “the discharge\nof dredged or fill material” into navigable waters. Id.\n\n 6\n\f(the “Bridge South alternative”) and proposals involving beach nourishment. An EA in\n\n2010 (the “2010 EA”) further developed these alternatives.\n\n The Merger Team released an updated EA in 2013 (the “2013 EA”) to account for\n\nenvironmental changes after the 2010 EA, including the effects of Hurricane Irene in\n\n2011. The 2013 EA identified four alternatives for the segment at issue: (1) the so-called\n\nJug-Handle Bridge, a bridge extending out into the Pamlico Sound (also referred to in the\n\nenvironmental analyses as the “Bridge on New Location”); 4 (2) an easement bridge on\n\nthe existing NC-12 location; (3) beach nourishment; and (4) an easement bridge\n\ncombined with beach nourishment. The Merger Team did not study the beach\n\nnourishment alternatives in depth in the 2013 EA because, at a 2011 meeting, it had\n\nalready determined not to pursue them after experts reported on a “high erosion rate and a\n\nlack of sand supply.” J.A. 843. In the 2013 EA, the Merger Team identified the\n\neasement bridge as its preferred alternative under NEPA. However, certain members of\n\nthe Merger Team objected to finding that the easement bridge was the LEDPA under the\n\nClean Water Act, citing concerns about its location within the surf zone, additional\n\npermits associated with erosion setback requirements, and its impact on a nearby wildlife\n\nrefuge. See J.A. 1745–47.\n\n In the meantime, environmental groups Defenders of Wildlife and the National\n\nWildlife Refuge Association (intervenors here, collectively the “Environmental Groups”)\n\nbrought suit in federal court to challenge the Agencies’ NEPA and § 4(f) determinations\n\n 4\n The Jug-Handle Bridge was a modified version of the Bridge South alternative\nthat was introduced in the 2008 EIS and further developed in the 2010 EA.\n\n 7\n\fwith respect to a different segment of NC-12 in the Outer Banks--the Bonner Bridge,\n\nwhich connects Bodie Island and Hatteras Island to the north of Rodanthe. See Defs. of\n\nWildlife v. N.C. Dep’t of Transp., 762 F.3d 374 (4th Cir. 2014). The Environmental\n\nGroups and the Agencies eventually reached an agreement in 2015 (the “Settlement”). 5\n\nThe Settlement required NCDOT to identify the Jug-Handle Bridge as its preferred\n\nalternative for the segment of NC-12 at issue in this case. It also required NCDOT to\n\nseek Merger Team concurrence that the Jug-Handle Bridge was the LEDPA. In doing so,\n\nit stated that nothing in the Settlement “requires or should be interpreted to predetermine\n\nthe choice” of the Jug-Handle Bridge as the final selected alternative. J.A. 1090. In\n\nexchange, the Environmental Groups dismissed the Bonner Bridge suit and agreed not to\n\nchallenge the Agencies in court if the Jug-Handle Bridge was determined to be the\n\nLEDPA and was ultimately selected in the ROD for this project.\n\n After a 2015 meeting, the Agencies identified the Jug-Handle Bridge as their\n\npreferred alternative. Following public comment and detailed studies, the Merger Team\n\ndetermined that the Jug-Handle Bridge was the LEDPA. In 2016, the Merger Team\n\nreleased a revised EA (the “2016 EA”) to evaluate the environmental impacts of the Jug-\n\nHandle Bridge and its associated construction activities. Later that year, the Merger\n\nTeam issued an ROD (the “2016 ROD”) formally approving the Jug-Handle Bridge.\n\n In addition to authorizing construction of the Jug-Handle Bridge, the 2016 ROD\n\nalso addressed concerns relating to a shipwreck in the proposed bridge’s path known as\n\n 5\n NCDENR was also a party to the Settlement and is represented on the Merger\nTeam, though it is not a defendant here.\n\n 8\n\fthe Pappy’s Lane Wreck. The shipwreck is eligible for listing on the National Register of\n\nHistoric Places. Because of the shipwreck’s historical significance, the 2016 ROD\n\nordered a data recovery project on the shipwreck, which later uncovered evidence that the\n\nshipwreck was a World War II assault vessel. The Merger Team has not yet determined\n\nhow it will respond to this new information.\n\n\n\n C.\n\n We now turn to the procedural history of this litigation, which began when SOS\n\nsued the Agencies on February 2, 2017. A month later, the Environmental Groups\n\nintervened in the suit in support of the Agencies. In its complaint, SOS alleged, as\n\nrelevant here, that the Agencies’ approval of the Jug-Handle Bridge violated NEPA\n\nbecause that decision was predetermined by the Settlement. To show evidence of\n\npredetermination, SOS moved to supplement the administrative record before the district\n\ncourt to include documents related to the negotiation of the Settlement on the grounds\n\nthat those documents were before the Agencies when they made their decision to select\n\nthe Jug-Handle Bridge. The district court denied this motion.\n\n Later, SOS moved to amend its complaint to add claims related to construction\n\nimpacts in Rodanthe and to the Pappy’s Lane Wreck. Specifically, SOS contended that\n\nthe Agencies’ environmental analyses did not adequately consider the effects of\n\nconstruction or the historic significance of the Pappy’s Lane Wreck. The district court\n\ngranted the motion as to construction impacts but denied it as to the shipwreck.\n\n\n\n 9\n\f SOS, the Agencies, and the Environmental Groups each filed cross-motions for\n\nsummary judgment on the issue of whether the Agencies’ environmental analyses\n\nviolated NEPA or the DTA. The district court granted the Agencies’ and Environmental\n\nGroups’ motions for summary judgment and denied SOS’s motion.\n\n SOS appeals the district court’s grant of the Agencies’ motion for summary\n\njudgment and its denial of SOS’s motion to amend its complaint. SOS contends that the\n\nAgencies were not entitled to summary judgment because the Agencies’ environmental\n\nanalyses violated NEPA. It also contends that the district court erred in denying SOS’s\n\nmotion to amend its complaint with claims related to the Pappy’s Lane Wreck. We\n\ndiscuss SOS’s NEPA claims and its motion to amend its complaint, in that order.\n\n\n\n II.\n\n SOS contends that the Agencies violated NEPA when they selected the Jug-\n\nHandle Bridge for the NC-12 project. “We review a grant of summary judgment de\n\nnovo,” Defs. of Wildlife, 762 F.3d at 392, and, accordingly, review the Agencies’ actions\n\ndirectly, pursuant to the Administrative Procedure Act (the “APA”). The APA directs us\n\nto overturn agency actions if they are “arbitrary, capricious, an abuse of discretion, or\n\notherwise not in accordance with law.” 5 U.S.C. § 706(2)(A). Our precedent also guides\n\nthe scope of our review of the sufficiency of an agency’s NEPA analysis. Nat’l Audubon\n\nSoc’y v. Dep’t of Navy, 422 F.3d 174, 185, 199 (4th Cir. 2005). In conducting this\n\nreview, “we must make a searching and careful inquiry into the facts” and examine\n\nwhether the decision was based on consideration of the relevant factors. Id. at 185\n\n 10\n\f(citation and internal quotation marks omitted). However, we do not “second-guess\n\nagency decisions, so long as the agency has given a hard look at the environmental\n\nimpacts of its proposed action.” Id. at 199.\n\n Under this standard of review, we affirm because the Agencies did not violate\n\nNEPA in approving the Jug-Handle Bridge. We consider SOS’s arguments that the\n\nAgencies’ environmental analyses violated NEPA because (1) the Agencies failed to\n\nprepare an SEIS with regards to the Jug-Handle Bridge and beach nourishment\n\nalternatives before issuing the 2016 ROD, (2) the Agencies failed to adequately consider\n\nthe impacts of construction, and (3) the Settlement impermissibly predetermined the\n\nAgencies’ choice of the Jug-Handle Bridge.\n\n\n\n A.\n\n First, SOS contends that the Agencies’ NEPA analysis was deficient because the\n\nAgencies should have prepared an SEIS before approving the Jug-Handle Bridge in the\n\n2016 ROD. NEPA requires an agency to prepare an SEIS if “[t]he agency makes\n\nsubstantial changes” to a proposed action that implicate environmental concerns or if\n\n“[t]here are significant new circumstances or information” that would affect the\n\nenvironmental impacts of the proposed action. 40 C.F.R. § 1502.9(c). To merit an SEIS,\n\nthe changes “must present a seriously different picture of the environmental impact of the\n\nproposed project.” Hughes River Watershed Conservancy v. Glickman, 81 F.3d 437, 443\n\n(4th Cir. 1996) (citation and alterations omitted).\n\n\n\n 11\n\f We review an agency’s decision not to prepare an SEIS in two steps, consistent\n\nwith our standard of review under NEPA. Id. At step one, we “determine whether the\n\nagency took a hard look at the proffered new information.” Id. If the agency concludes\n\nafter a preliminary inquiry that the “environmental effect of the change is clearly\n\ninsignificant,” its decision not to prepare an SEIS satisfies the hard look requirement.\n\nHodges v. Abraham, 300 F.3d 432, 446 (4th Cir. 2002). For instance, in Hodges, we held\n\nthat an agency took a hard look at the environmental consequences of its change in plans\n\nwhen it explicitly evaluated those consequences and determined that they were not\n\nsignificantly different from those discussed in a prior EIS. Id. at 447. We also noted that\n\nthe plaintiff in that case “failed to identify any particular risk arising from” the change\n\nthat had not already been addressed in the agency’s environmental analyses. Id. Next, at\n\nstep two of the SEIS inquiry, we review whether the agency’s decision not to prepare an\n\nSEIS after taking a hard look was arbitrary or capricious. Hughes River, 81 F.3d at 443.\n\n SOS contends that an SEIS was necessary (1) to evaluate the environmental\n\neffects of the Jug-Handle Bridge alternative because it was different from options that\n\nhad previously been evaluated and (2) to reconsider alternatives that involved beach\n\nnourishment pursuant to new information about sand availability and beach erosion rates.\n\nWe address each contention in turn and affirm the district court’s determination that no\n\nSEIS was required. Neither of these changes are sufficiently different from the\n\ncircumstances initially evaluated in the EIS to merit an SEIS. The Agencies’ decision not\n\nto prepare one after taking a hard look at the changes was therefore not arbitrary or\n\ncapricious.\n\n 12\n\f i.\n\n Contrary to SOS’s contention, the Agencies were not required to prepare an SEIS\n\nwith respect to the Jug-Handle Bridge alternative. SOS argues that the final alignment of\n\nthe Jug-Handle Bridge alternative (that is, its path across the Pamlico Sound and its\n\nconnection points with the shore) was significantly different from previously evaluated\n\nalternatives. Specifically, SOS contends that the bridge’s alignment changed\n\nsignificantly because the alternative evaluated in the 2008 EIS was “amorphously\n\ndefined” and because the alternative evaluated in the 2010 EA (to which the 2013 EA,\n\n2016 EA, and 2016 ROD refer) was “not comparable” to the Jug-Handle Bridge.\n\nAppellant’s Br. at 35, 36. It argues that these differences render prior environmental\n\nanalyses of those alternatives insufficient to evaluate the environmental effects of the\n\nJug-Handle Bridge as approved in the 2016 ROD. We disagree and conclude that the\n\nAgencies complied with NEPA when they decided that an SEIS was not warranted by\n\nthese changes.\n\n At step one, the Agencies took a hard look at changes in the bridge’s alignment in\n\nthe 2016 EA. The 2016 EA describes the similarities and differences between the Jug-\n\nHandle Bridge as proposed in 2016 and the versions evaluated in the 2013 EA, the 2010\n\nEA, and the 2008 EIS. For instance, it explains that the Agencies decided to shift the\n\nalignment of the bridge to avoid areas of “dense submerged aquatic vegetation” that fell\n\nin the path of previous versions of the bridge. J.A. 1198. The 2016 EA also explains that\n\nthe Jug-Handle Bridge’s alignment reduces effects on the community as compared with\n\n 13\n\fprevious versions because it requires a narrower right-of-way. Because the Agencies\n\nwent into detail in their comparison between the Jug-Handle Bridge and previous\n\nversions of the bridge, their coverage satisfies the hard look requirement. See Hodges,\n\n300 F.3d at 446–47.\n\n And, at step two, because the Agencies took the requisite hard look and neither\n\ntheir environmental analyses nor SOS identify any particular differences that would merit\n\nan SEIS, their decision not to prepare an SEIS was not arbitrary or capricious. See\n\nHughes River, 81 F.3d at 443. An SEIS is only required when changes to a project\n\npresent a “seriously different picture of the environmental impact.” Id. (alterations and\n\ncitation omitted). Based on the discussion presented in the 2016 EA, which compared the\n\ndifferent versions of the bridge, it was not arbitrary or capricious for the Agencies to\n\ndetermine that the Jug-Handle Bridge’s final alignment did not present a “seriously\n\ndifferent picture,” id., than the 2008 EIS, the 2010 EA, or the 2013 EA. The Agencies\n\nexplained how the Jug-Handle Bridge was different from previous versions of the bridge,\n\nand their explanations do not implicate any significant environmental concerns.\n\nAccordingly, their decision not to prepare an SEIS was not arbitrary or capricious.\n\n\n\n ii.\n\n Similarly, the Agencies were not required to prepare an SEIS to reevaluate the\n\nfeasibility of alternatives that involved beach nourishment. SOS contends that the\n\nAgencies failed to adequately reconsider beach nourishment after new erosion projections\n\nwere released and after a 2014 emergency beach nourishment project in the area\n\n 14\n\fsuccessfully repaired damage from Hurricane Sandy. According to SOS, this new\n\ninformation showed that coastal conditions had changed such that erosion would no\n\nlonger threaten beach nourishment and that adequate sand was in fact available to\n\ncomplete the project.\n\n However, the Agencies took the requisite hard look at these new circumstances in\n\nthe 2016 EA. See Hughes River, 81 F.3d at 443. The 2016 EA notes that while erosion\n\nprojections in the Rodanthe area did decrease, erosion rates in Rodanthe remained\n\n“amongst the highest rates along the North Carolina coast.” J.A. 1218. It also discusses\n\nthe 2014 emergency beach nourishment project in detail and considers updated\n\ninformation about coastal conditions in the area. Specifically, it notes that the 2014\n\nemergency beach nourishment project was “essentially one round of nourishment in one\n\npart of [NC-12].” J.A. 1227. Finally, it concludes that the Agencies thoroughly\n\nconsidered the environmental effects of beach nourishment when they originally\n\nevaluated those alternatives in the 2008 EIS. This detailed discussion satisfies the hard\n\nlook requirement. See Hodges, 300 F.3d at 446–47.\n\n And after taking that hard look, the Agencies’ decision not to prepare an SEIS was\n\nnot arbitrary or capricious. See Hughes River, 81 F.3d at 443. SOS cites improved\n\nerosion rates and an increased supply of sand as new factors that the Agencies should\n\nhave considered when deciding whether to prepare an SEIS. However, erosion and sand\n\nsupply were not the Agencies’ only reasons for initially rejecting beach nourishment in\n\nthe 2008 EIS. The Agencies also cited independent concerns such as inadequate\n\nprotection against future breaches, risks of overwash, and incompatibility with the\n\n 15\n\fmission of a neighboring wildlife refuge. It was not arbitrary or capricious for the\n\nAgencies to decline to reconsider beach nourishment alternatives in an SEIS when the\n\nnew information proffered by SOS did not implicate all of the Agencies’ independently\n\nadequate reasons for initially rejecting beach nourishment.\n\n Accordingly, the Agencies were not required to prepare an SEIS to consider the\n\nalignment of the Jug-Handle Bridge or to consider beach nourishment alternatives. Their\n\nenvironmental analyses therefore do not violate NEPA in this respect.\n\n\n\n B.\n\n SOS also contends that the Agencies’ environmental analyses violate NEPA\n\nbecause they do not adequately consider the environmental effects of construction in the\n\nRodanthe area. Specifically, SOS argues that the effects of construction traffic and haul\n\nroads are not adequately addressed in the 2016 EA and that any discussion of these issues\n\nin the 2008 EIS is irrelevant because that document focuses on a larger area.\n\n NEPA requires agencies to consider all “significant environmental impacts,” 40\n\nC.F.R. § 1502.1, which can include impacts caused by the use of construction roads and\n\nincreased traffic. See, e.g., Arlington Coal. on Transp. v. Volpe, 458 F.2d 1323, 1332\n\n(4th Cir. 1972) (explaining that NEPA applies to highway construction projects).\n\nAccordingly, if construction roads and traffic are expected to affect the environment near\n\nan agency project, the agency must provide “full and fair discussion” of those effects and\n\nincorporate them into its comparison of alternatives. 40 C.F.R. § 1502.1.\n\n\n\n 16\n\f Here, the Agencies adequately considered the effects of construction traffic as a\n\nresult of the Jug-Handle Bridge in the 2016 ROD. Specifically, the Agencies explained\n\nthat a temporary construction easement would be necessary to support traffic during\n\nconstruction but noted that “[t]he land affected will be restored after construction is\n\ncompleted.” J.A. 1559. While the 2016 ROD does not compare the construction traffic\n\neffects of the Jug-Handle Bridge with those of other proposed alternatives, the Agencies\n\ndid perform that comparison in the 2013 EA and the 2016 EA and still found the bridge\n\nto be the LEDPA. The Agencies also specifically considered the environmental effects of\n\nhaul roads in the 2008 EIS. 6\n\n We therefore cannot say that the Agencies did not provide “full and fair\n\ndiscussion” of the effects of construction traffic or haul roads when they selected the Jug-\n\nHandle Bridge among alternatives. See 40 C.F.R. § 1502.1. Accordingly, the Agencies\n\ndid not violate NEPA here, and we affirm the district court.\n\n\n\n\n 6\n To be sure, that discussion did not explicitly consider haul roads in the Rodanthe\narea. However, it is unclear from the record whether the Agencies actually plan to use\nhaul roads for the Jug-Handle Bridge project. See, e.g., J.A. 214 (containing a\ndeclaration from an NCDOT engineer stating that NCDOT and its contractor decided not\nto pursue a previously-discussed haul road in connection with a barge because shallow\nwater depths would make it impracticable). Regardless, NEPA does not compel the\nAgencies to specifically consider the environmental impacts of haul roads so long as they\nadequately examine the environmental consequences of the Jug-Handle Bridge project,\nincluding construction impacts, as a whole. See 40 C.F.R. § 1502.2(b) (“Impacts shall be\ndiscussed [in the EIS] in proportion to their significance.”).\n\n 17\n\f C.\n\n Finally, SOS contends that the Agencies violated NEPA because their choice of\n\nthe Jug-Handle Bridge did not follow from their NEPA analysis but, rather, was a\n\npredetermined result of the Settlement. NEPA “prohibits agencies from preparing an EIS\n\nsimply to ‘justify [] decisions already made.’” Nat’l Audubon Soc’y, 422 F.3d at 199\n\n(quoting 40 C.F.R. § 1502.2(g)) (alteration in original). That is because, under NEPA,\n\nagencies that have yet to issue a final decision may not “commit resources prejudicing\n\nselection of alternatives,” 40 C.F.R. § 1502.2(f), nor may they take any action that would\n\n“[l]imit the choice of reasonable alternatives,” 40 C.F.R. § 1506.1(a). An EIS based upon\n\na predetermined choice that a certain alternative will be selected would violate these\n\nprinciples because it would not allow the agency to fully consider all alternatives.\n\n We conclude that the Agencies’ choice of the Jug-Handle Bridge was not\n\nimpermissibly predetermined. We consider, in turn, the Agencies’ objective\n\nenvironmental analyses, the language of the Settlement, and the role of documents\n\ngenerated during negotiation of the Settlement.\n\n\n\n i.\n\n First, SOS contends that flaws in the Agencies’ environmental analyses reveal that\n\ntheir choice of the Jug-Handle Bridge was predetermined by the Settlement. In alleging\n\nthat the environmental analyses were inadequate, it primarily relies upon arguments that\n\nwe have already discussed--namely, that the Agencies failed to fully consider the new\n\nalignment of the bridge, the feasibility of beach nourishment alternatives, and the effects\n\n 18\n\fof construction traffic and haul roads. SOS contends that these flaws exist because the\n\nAgencies prematurely decided to choose the Jug-Handle Bridge after the Settlement.\n\n Under our precedent, “the evidence we look to in determining whether\n\n[predetermination] has taken place consists of the environmental analysis itself.” 7 Nat’l\n\nAudubon Soc’y, 422 F.3d at 199. In National Audubon Society, in reviewing allegations\n\nthat an agency had settled on a certain outcome before preparing its EIS, we declined to\n\nlook to the agency’s internal documents and emails. Id. Instead, we limited the scope of\n\nour inquiry to the agency’s objective environmental analysis, reasoning that “[w]here an\n\nagency has merely engaged in post hoc rationalization, there will be evidence of this in its\n\nfailure to comprehensively investigate the environmental impact of its actions and\n\nacknowledge their consequences.” Id. Accordingly, our analysis focuses on whether an\n\nagency’s objective environmental analyses demonstrate evidence of predetermination.\n\n Here, when we examine Agencies’ environmental analyses, we cannot say that\n\nthey violated NEPA by selecting the Jug-Handle Bridge following the Settlement. To be\n\nsure, the Agencies changed their preferred alternative from the easement bridge to the\n\nJug-Handle Bridge following the Settlement. But that change alone does not mean that\n\nthe Agencies’ choice was predetermined, particularly where members of the Merger\n\nTeam had expressed concerns about the easement bridge as far back as 2013. And when\n\nwe look to the Agencies’ environmental analyses here, those analyses satisfied NEPA’s\n\n\n 7\n We note that some circuits look beyond the objective environmental analysis for\nevidence of predetermination. See, e.g., Forest Guardians v. U.S. Fish & Wildlife Serv.,\n611 F.3d 692, 716–17 (10th Cir. 2010) (declining to adopt the Fourth Circuit’s rule).\n\n 19\n\frequirements. See discussion supra Sections II.A., II.B. We do not see, and SOS cannot\n\nidentify, any evidence that the Agencies “fail[ed] to comprehensively investigate” and\n\nevaluate the environmental impacts of the Jug-Handle Bridge or the other alternatives.\n\nNat’l Audubon Soc’y, 422 F.3d at 199. The EAs and EIS prepared by the Agencies do\n\nnot, on their faces, show evidence of predetermination.\n\n SOS cites to cases from the Ninth and Tenth Circuits to contend that courts have\n\nfound predetermination based on contractual commitments made by an agency before the\n\nNEPA process was complete. See Davis v. Mineta, 302 F.3d 1104, 1112 (10th Cir. 2002)\n\n(holding that a contract requiring a consultant to recommend that a project had no\n\nsignificant environmental impact before actually preparing an EA violated NEPA);\n\nMetcalf v. Daley, 214 F.3d 1135, 1145 (9th Cir. 2000) (same, regarding a contract\n\nrequiring an agency to make a proposal for a specific alternative before preparing an EA).\n\nHowever, these cases are distinguishable because they involved contracts that agencies\n\nentered into before conducting any environmental analysis at all; in contrast, the\n\nSettlement here, which the Agencies and the Environmental Groups entered into in 2015,\n\nwas preceded by a number of environmental analyses, including the 2008 EIS, the 2010\n\nEA, and the 2013 EA. And when we examine each of these environmental analyses, we\n\nfind no evidence of predetermination warranting reversal.\n\n\n\n ii.\n\n Although circuit precedent limits our predetermination inquiry to the\n\n“environmental analysis itself,” id., SOS nonetheless urges us to consider the Settlement\n\n 20\n\fas evidence that the Agencies’ choice was predetermined. But even if we look to the\n\nSettlement, that document does not support SOS’s claim. The Settlement only required\n\nNCDOT to identify the Jug-Handle Bridge as its preferred alternative and to seek Merger\n\nTeam concurrence that the Jug-Handle Bridge was the LEDPA. These conditions do not\n\nrequire the Agencies to select the Jug-Handle Bridge as the final approved alternative for\n\nthis project. For instance, it remained possible that the Agencies’ environmental analyses\n\nwould demonstrate that the Jug-Handle Bridge was not the LEDPA. Additionally, the\n\nAgencies’ preferences alone could not bind the entire Merger Team, which was\n\nultimately responsible for approving the final alternative, because the parties to the\n\nSettlement comprise only three of the ten state and federal agencies represented on the\n\nMerger Team. 8 This does not constitute predetermination.\n\n\n\n iii.\n\n SOS also urges us to consider external documents generated during the negotiation\n\nof the Settlement as evidence of predetermination and to reverse the district court’s denial\n\nof SOS’s motion to include these documents in the record. We decline to do so because\n\nthe district court did not abuse its discretion in denying this motion. See Fort Sumter\n\nTours, Inc. v. Babbitt, 66 F.3d 1324, 1335–36 (4th Cir. 1995) (explaining that we review\n\n 8\n To be sure, the parties to the Settlement represented three of the four Lead\nAgencies tasked with decisionmaking if the Merger Team could not reach consensus.\nBut, as discussed, the Settlement only required those agencies to seek concurrence that\nthe Jug-Handle Bridge was the LEDPA; it did not require them to go beyond the\nobjective environmental analysis to choose the Jug-Handle Bridge if it was not, in fact,\nthe LEDPA.\n\n 21\n\fa district court’s decision whether to expand the administrative record for abuse of\n\ndiscretion).\n\n Federal courts base their review of agency decisions on “the ‘whole record’\n\ncompiled by the agency.” Citizens to Pres. Overton Park, Inc. v. Volpe, 401 U.S. 402,\n\n419 (1971) (quoting 5 U.S.C. § 706), abrogated on other grounds by Califano v. Sanders,\n\n430 U.S. 99 (1977). We may supplement the record as presented by the agency if the\n\n“bare record” does not reveal the agency’s reasoning or if it appears that the agency acted\n\nin bad faith. Id. at 420. Otherwise, “inquiry into the mental processes of administrative\n\ndecisionmakers is usually to be avoided.” Id.\n\n Here, the record as presented by the Agencies reveals their reasoning, as we have\n\ndiscussed, and the district court found no evidence that the Agencies acted in bad faith.\n\nThe district court also determined that there was no evidence that the Agencies actually\n\nreviewed the documents put forth by SOS as part of their decision to approve the Jug-\n\nHandle Bridge. We hold that the district court did not abuse its discretion by denying\n\nSOS’s motion to supplement the record, and accordingly, our review is limited to the\n\nrecord as compiled by the Agencies.\n\n SOS contends that, even if we cannot consider these documents as part of the\n\nadministrative record, we should nevertheless consider them as extra-record evidence. It\n\nis true that “in the NEPA context, courts generally have been willing to look outside the\n\nrecord when assessing the adequacy of an EIS or a determination that no EIS is\n\nnecessary.” Ohio Valley Envtl. Coal. v. Aracoma Coal Co., 556 F.3d 177, 201 (4th Cir.\n\n2009). However, we have explained that extra-record evidence in that context is\n\n 22\n\fprimarily useful “to inform the court about environmental factors that the agency may not\n\nhave considered.” Id. (emphasis added). Here, the proffered documents would do\n\nnothing to aid the court’s understanding of the environmental concerns at issue, as they\n\nconcern the legal terms of the Settlement between the Agencies and the Environmental\n\nGroups. Therefore, the district court properly excluded them, and we decline to consider\n\nthem now.\n\n There is superficial appeal in suggesting that the Agencies’ choice was\n\npredetermined because the Settlement yielded a preferred alternative. However, that\n\nconclusion is not legally or factually supported by the record. Legally, our analysis is\n\ncabined to the environmental analysis itself, with which we find no issues meriting\n\nreversal. And factually, we see no evidence that the Merger Team was forced to approve\n\nthe Jug-Handle Bridge.\n\n In sum, the Agencies did not violate NEPA when they approved the Jug-Handle\n\nBridge because they were not required to prepare an SEIS, they adequately evaluated the\n\neffects of construction traffic, and they did not rely on a predetermined choice among\n\nalternatives. We therefore affirm the district court’s grant of summary judgment in favor\n\nof the Agencies.\n\n\n\n III.\n\n Finally, SOS contends that the district court erred when it denied SOS’s motion to\n\namend its complaint with claims related to the Pappy’s Lane Wreck. Specifically, SOS\n\nalleges that the Agencies violated § 4(f) by approving a transportation project that\n\n 23\n\fthreatens to harm the land of a site of historic significance because the Jug-Handle Bridge\n\nwill pass above the wreck--the site of a World War II vessel.\n\n We review a district court’s denial of a motion to amend the complaint for abuse\n\nof discretion. See Laber v. Harvey, 438 F.3d 404, 428 (4th Cir. 2006) (en banc).\n\nHowever, if the district court denied such a motion on the grounds that the amendment\n\nwould have been futile, we review its legal conclusions de novo. United States ex. rel.\n\nAhumada v. NISH, 756 F.3d 268, 274 (4th Cir. 2014).\n\n A party “may amend its pleading once as a matter of course” before the opposing\n\nparty files a responsive pleading. Fed. R. Civ. P. 15(a)(1). After that time, a party may\n\nonly amend its pleading with the consent of the opposing party or with leave of the court,\n\nand “[t]he court should freely give leave when justice so requires.” Fed. R. Civ. P.\n\n15(a)(2). Courts may deny leave to amend a pleading if the amendment would have been\n\nfutile. Laber, 438 F.3d at 426. A proposed amendment is futile when it is “clearly\n\ninsufficient or frivolous on its face.” Johnson v. Oroweat Foods Co., 785 F.2d 503, 510\n\n(4th Cir. 1986). A proposed amendment is also futile if the claim it presents would not\n\nsurvive a motion to dismiss. Perkins v. United States, 55 F.3d 910, 917 (4th Cir. 1995).\n\n Here, the district court found that SOS’s proposed amendment would be futile for\n\ntwo alternative reasons. First, it determined that, to the extent that SOS sought to assert\n\nthat the 2016 EA was no longer valid in light of new information about the shipwreck,\n\nthat claim would be unripe where the Agencies had not yet made a decision concerning\n\nthe significance of the new information. Second, it determined that, to the extent that\n\nSOS sought to assert that the 2016 EA was inadequate when issued, that claim would fail\n\n 24\n\fbecause it would ask the Agencies to consider information that was not discovered until\n\nafter the 2016 EA was issued. For the reasons that follow, we affirm the district court’s\n\ndenial of SOS’s motion to amend its complaint.\n\n First, to the extent that SOS’s proposed amendments contend that the Agencies\n\nfailed to consider new information about the shipwreck, those amendments would be\n\nfutile because they would raise a claim that is not yet ripe for review. 9 Courts may only\n\nreview “final agency action,” 5 U.S.C. § 704, and challenges to agency decisions that are\n\nyet to be made are not ripe for review. See Pashby v. Delia, 709 F.3d 307, 317 (4th Cir.\n\n2013) (holding that a claim is only ripe when it involves a formalized administrative\n\ndecision). Here, the Agencies have not yet made a final decision about the significance\n\nof new information revealing that the shipwreck was a World War II assault vessel.\n\nTherefore, any claim that the Agencies did not properly account for this information\n\nwould be unripe, and any amendment seeking to add such a claim would be futile.\n\n Second, SOS contends on appeal that it is challenging the adequacy of the 2016\n\nROD’s treatment of the Pappy’s Lane Wreck rather than the Agencies’ failure to consider\n\nnew information about the shipwreck’s significance. Specifically, SOS contends that,\n\nbecause the Agencies knew that the shipwreck was eligible for listing on the National\n\n\n 9\n SOS appears to have abandoned this argument on appeal. See Appellants’ Br. at\n53 (contending that the district court “fundamentally misread [SOS’s] motion” when it\ndenied it on ripeness grounds because “[t]he [new] allegations were about the\ninadequacies of the [2016] ROD and the process leading up to that document”)\n(emphasis added). Nevertheless, we discuss it because it implicates concerns related to\nthe argument that SOS does raise on appeal regarding the adequacy of the 2016 ROD\nwhen issued.\n\n 25\n\fRegister of Historic Places, they were not authorized to build a bridge in its path unless\n\nthey determined that there was “no prudent and feasible alternative to using that land”\n\nand that the “project include[d] all possible planning to minimize harm . . . resulting from\n\nthe use.” See 49 U.S.C. § 303(c).\n\n However, as the district court explained, SOS cannot contend that it was\n\nchallenging the adequacy of the 2016 ROD’s treatment of the shipwreck when its claims\n\n“rest[] upon recent discovery that the Pappy[’s] Lane Wreck contains a World War II\n\nvessel.” Save Our Sound OBX, Inc. v. N.C. Dep’t of Transp., No. 2:17-CV-4-FL, 2017\n\nWL 7048561, at *5 (E.D.N.C. Dec. 5, 2017). Instead, the Agencies satisfied regulatory\n\nrequirements when, based on what they knew about the Pappy’s Lane Wreck, they\n\nordered data recovery and decided that the shipwreck did not merit preservation in place.\n\nArguments that the Agencies should have gone further are grounded in new information\n\nand, therefore, not reviewable until the Agencies issue a final decision, as discussed\n\nabove. We therefore affirm the district court’s denial of SOS’s motion to amend its\n\ncomplaint.\n\n\n\n IV.\n\n We affirm the district court because the Agencies did not violate NEPA or the\n\nDTA when they issued the 2016 ROD selecting the Jug-Handle Bridge and because the\n\ndistrict court did not abuse its discretion when it denied SOS’s motions to supplement the\n\nadministrative record and to amend the complaint.\n\n AFFIRMED\n\n 26\n[END_CASE]", "role": "user" } ]
4,584,448
UNITED STATES of America, Plaintiff-Appellee, v. Joseph Decore SIMMS, Defendant-Appellant. Fourth Circuit Federal Defender Offices, Amicus Supporting Appellant.
United States v. Joseph Simms
2019-01-24
15-4640
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Wilkinson, Niemeyer, Motz, King, Duncan, Agee, Keenan, Wynn, Diaz, Floyd, Thacker, Harris, Richardson, Quattlebaum", "parties": "", "opinions": [{"author": "", "type": "020lead", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887914/", "author_raw": ""}, {"author": "", "type": "040dissent", "text": "", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/9887915/", "author_raw": ""}, {"author": "DIANA GRIBBON MOTZ, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 15-4640\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nJOSEPH DECORE SIMMS,\n\n Defendant - Appellant.\n\n------------------------------------------\n\nFOURTH CIRCUIT FEDERAL DEFENDER OFFICES,\n\n Amicus Supporting Appellant.\n\n\nAppeal from the United States District Court for the Eastern District of North Carolina, at\nGreenville. Terrence W. Boyle, Chief District Judge. (4:15-cr-00010-BO-1)\n\n\nArgued: September 26, 2018 Decided: January 24, 2019\n\n\nBefore GREGORY, Chief Judge, and WILKINSON, NIEMEYER, MOTZ, KING,\nDUNCAN, AGEE, KEENAN, WYNN, DIAZ, FLOYD, THACKER, HARRIS,\nRICHARDSON, and QUATTLEBAUM, Circuit Judges.\n\n\nReversed and remanded by published opinion. Judge Motz wrote the opinion, in which\nChief Judge Gregory and Judges King, Wynn, Diaz, Floyd, Thacker, and Harris joined.", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "DIANA GRIBBON MOTZ, Circuit Judge:"}, {"author": "Judge Wynn wrote a concurring", "type": "concurrence", "text": "Judge Wynn wrote a concurring opinion, in which Judge Harris joined. Judge Wilkinson", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "Judge Wynn wrote a concurring"}, {"author": "wrote a dissenting opinion. Judge Niemeyer wrote a dissenting", "type": "dissent", "text": "wrote a dissenting opinion. Judge Niemeyer wrote a dissenting opinion, in which Judges\n\nWilkinson, Duncan, Agee, Keenan, and Quattlebaum joined. Judge Richardson wrote a\ndissenting opinion, in which Judge Quattlebaum joined.\n\n\nARGUED: Dhamian Blue, BLUE LLP, Raleigh, North Carolina, for Appellant. Phillip\nAnthony Rubin, OFFICE OF THE UNITED STATES ATTORNEY, Raleigh, North\nCarolina, for Appellee. Joshua B. Carpenter, FEDERAL DEFENDERS OF WESTERN\nNORTH CAROLINA, INC., Asheville, North Carolina, for Amici Curiae. ON BRIEF:\nBrian A. Benczkowski, Assistant Attorney General, Matthew S. Miner, Deputy Assistant\nAttorney General, John P. Taddei, Appellate Section, Criminal Division, UNITED\nSTATES DEPARTMENT OF JUSTICE, Washington, D.C.; John Stuart Bruce, Acting\nUnited States Attorney, Robert J. Higdon, Jr., United States Attorney, Jennifer P. May-\nParker, Assistant United States Attorney, OFFICE OF THE UNITED STATES\nATTORNEY, Raleigh, North Carolina, for Appellee. Anthony Martinez, Federal Public\nDefender, FEDERAL PUBLIC DEFENDERS OF WESTERN NORTH CAROLINA,\nINC., Charlotte, North Carolina; Parks N. Small, Federal Public Defender, Columbia,\nSouth Carolina; Louis C. Allen, Federal Public Defender, Greensboro, North Carolina;\nFred Heblich, Interim Federal Public Defender, Roanoke, Virginia; Christian M. Capece,\nFederal Public Defender, Charleston, West Virginia; James Wyda, Federal Public\nDefender, Baltimore, Maryland; Paresh S. Patel, Assistant Federal Public Defender,\nGreenbelt, Maryland; G. Alan DuBois, Federal Public Defender, Raleigh, North\nCarolina; Geremy Kamens, Federal Public Defender, Alexandria, Virginia; Brian J.\nKornbrath, Federal Public Defender, OFFICE OF THE FEDERAL PUBLIC\nDEFENDER, Clarksburg, West Virginia, for Amici Curiae.\n\n\n\n\n 2\n\nDIANA GRIBBON MOTZ, Circuit Judge:\n\n Joseph Decore Simms was convicted of brandishing a firearm in connection with a\n\n“crime of violence,” as defined in 18 U.S.C. § 924(c)(3)(B). He appeals, contending that\n\n§ 924(c)(3)(B), as long understood, is unconstitutionally vague. The Government\n\nconcedes this point but urges us to abandon the settled meaning of the statute and employ\n\na new definition of “crime of violence.”\n\n We cannot do so. Neither the statutory language nor controlling precedent offer\n\nany support for the Government’s proposed reinterpretation. Rather, the text and\n\nstructure of § 924(c)(3)(B) plainly set forth a definition of “crime of violence” that fails\n\nto comport with due process. Accordingly, we reverse and remand for further\n\nproceedings consistent with this opinion.\n\n\n\n I.\n\n This case arises from an April 2014 conspiracy to rob a McDonald’s in Goldsboro,\n\nNorth Carolina. Shortly after 1:00 a.m., Simms and a co-conspirator crawled into the\n\nMcDonald’s through the drive-through window; a third robber served as a lookout.\n\nWhen inside, Simms pointed a gun at the manager, attempted to strike another employee,\n\nand demanded money. The manager complied and opened the restaurant’s safe. After\n\nremoving the contents, Simms struck the manager with the gun, threw a cash drawer at\n\nthe other employee, and fled with his two co-conspirators and $1,100.\n\n After his arrest and indictment, Simms pleaded guilty to Count I, conspiracy to\n\ncommit Hobbs Act robbery in violation of 18 U.S.C. § 1951, and Count II, brandishing a\n\n 3\n\nfirearm during and in relation to a “crime of violence” — that is, the Hobbs Act\n\nconspiracy in Count I — in violation of 18 U.S.C. § 924(c)(1)(A). But at sentencing,\n\nSimms argued that his conviction under Count II was unconstitutional in light of Johnson\n\nv. United States, 135 S. Ct. 2551 (2015). He contended that Hobbs Act conspiracy was\n\nnot a “crime of violence” because the definition of this term in 18 U.S.C. § 924(c)(3)(B)\n\nwas unconstitutionally vague, like the similar definition of “violent felony” that the\n\nSupreme Court struck down in Johnson. The district court rejected this argument and\n\nsentenced Simms to 115 months’ incarceration on Count I and 84 months on Count II, for\n\na total consecutive sentence of 199 months’ imprisonment.\n\n Simms appealed, again contending that his conviction under Count II could not\n\nstand because § 924(c)(3)(B) was unconstitutional. 1 After the parties briefed and argued\n\nthe appeal before a panel of this court, the Supreme Court struck down as\n\nunconstitutionally vague a statute containing language materially identical to that\n\nchallenged by Simms. See Sessions v. Dimaya, 138 S. Ct. 1204, 1223 (2018). Given the\n\nexceptional importance and recurring nature of the question presented here, we agreed to\n\nrehear the case en banc. For the reasons that follow, we now reverse.\n\n\n\n\n 1\n The Government does not contend that Simms’s plea renders him unable to\nchallenge his § 924(c) conviction. It has expressly disavowed any reliance on the\nappellate waiver provision in Simms’s plea agreement. See Gov. Supp. Br. at 4 n.2.\n\n 4\n\n II.\n\n We must determine whether the definition of “crime of violence” in\n\n§ 924(c)(3)(B) satisfies the requirements of due process.\n\n In resolving this question, we first set forth the statutory framework and examine\n\nSupreme Court precedent interpreting text materially identical to that at issue here. We\n\nthen address the contours of Simms’s constitutional challenge, drawing on the Supreme\n\nCourt’s consideration of identical challenges to similar statutory language. Finally, we\n\nexplain why, in light of the plain text and binding Supreme Court precedent, we must\n\nhold § 924(c)(3)(B) unconstitutional.\n\n A.\n\n Federal law, as codified at 18 U.S.C. § 924(c)(1)(A), provides that a person who\n\nuses or carries a firearm “during and in relation to any crime of violence” or who\n\n“possesses a firearm” “in furtherance of any such crime” may be convicted of both the\n\nunderlying crime (here, Hobbs Act conspiracy) and the additional, distinct crime of\n\nutilizing a firearm in connection with a “crime of violence,” with the latter punishable by\n\nat least five consecutive years of imprisonment.\n\n Section 924(c)(3) defines “crime of violence” as “an offense that is a felony” and\n\n (A) has as an element the use, attempted use, or threatened use of physical\n force against the person or property of another, or\n (B) that by its nature, involves a substantial risk that physical force against\n the person or property of another may be used in the course of committing\n the offense.\n\n18 U.S.C. § 924(c)(3). Courts commonly refer to § 924(c)(3)(A) as the “force clause”\n\nand to § 924(c)(3)(B), the provision at issue here, as the “residual clause.” For Simms’s\n\n 5\n\n§ 924(c) conviction to stand, his Hobbs Act conspiracy offense must constitute a “crime\n\nof violence” under one of these two definitions.\n\n Our analysis begins with the force clause, § 924(c)(3)(A). To determine whether\n\nan offense is a crime of violence under that clause, courts use an inquiry known as the\n\n“categorical” approach. They look to whether the statutory elements of the offense\n\nnecessarily require the use, attempted use, or threatened use of physical force. See, e.g.,\n\nLeocal v. Ashcroft, 543 U.S. 1, 7–10 (2004) (interpreting materially identical text in 18\n\nU.S.C. § 16(a)); United States v. McNeal, 818 F.3d 141, 151–52 (4th Cir. 2016)\n\n(interpreting § 924(c)(3)(A)). This approach is “categorical” because courts consider\n\nonly the crime as defined, not the particular facts in the case. See, e.g., McNeal, 818 F.3d\n\nat 152. To be more precise, we will refer to the force clause inquiry as the elements-\n\nbased categorical approach, because it begins and ends with the offense’s elements.\n\nWhen a statute defines an offense in a way that allows for both violent and nonviolent\n\nmeans of commission, that offense is not “categorically” a crime of violence under the\n\nforce clause.\n\n Simms’s offense — conspiracy to commit Hobbs Act robbery — does not\n\ncategorically qualify as a crime of violence under the elements-based categorical\n\napproach, as the United States now concedes. Gov. 28(j) Letter at 1, ECF No. 44 (Oct.\n\n19, 2016); Simms Suppl. Br. at 1. This is so because to convict a defendant of this\n\noffense, the Government must prove only that the defendant agreed with another to\n\ncommit actions that, if realized, would violate the Hobbs Act. Such an agreement does\n\nnot invariably require the actual, attempted, or threatened use of physical force.\n\n 6\n\n Accordingly, the only way we can sustain Simms’s conviction on Count II is if his\n\ncommission of Hobbs Act conspiracy constitutes a crime of violence under the residual\n\nclause — that is, if we determine that he committed a felony offense “that by its nature[]\n\ninvolves a substantial risk that physical force against the person or property of another\n\nmay be used in the course of committing the offense.” 18 U.S.C. § 924(c)(3)(B).\n\nInterpreting a materially identical clause in another statute, the Supreme Court has\n\ndirected courts to employ a categorical approach that — as with the force clause —\n\n“look[s] to the elements and the nature of the offense of conviction, rather than to the\n\nparticular facts.” Leocal, 543 U.S. at 7 (interpreting 18 U.S.C. § 16(b) to “require[]”\n\ncategorical analysis); see also United States v. Aragon, 983 F.2d 1306, 1312–13 (4th Cir.\n\n1993) (“conclud[ing] that the plain language of § 16(b) mandates that the court embark\n\nupon a categorical approach”). 2\n\n Importantly, however, the analysis applicable to the residual clause constitutes a\n\n“distinctive form” of the categorical approach. Dimaya, 138 S. Ct. at 1211 (interpreting\n\n§ 16(b)). Unlike the elements-based categorical approach of the force clause, the residual\n\nclause inquiry “goes beyond deciding whether creation of risk is an element of the\n\n\n 2\n Because § 16(b) and § 924(c)(3)(B) are materially identical, we and other courts\nhave treated “precedent respecting one as controlling analysis of the other.” In re\nHubbard, 825 F.3d 225, 230 n.3 (4th Cir. 2016); see also, e.g., Evans v. Zych, 644 F.3d\n447, 452 n.2 (6th Cir. 2011) (“recogniz[ing] essentially identical nature of § 924(c) and\n§ 16” and applying § 16(b) case law to § 924(c)(3)(B) analysis); United States v. Serafin,\n562 F.3d 1105, 1108 n.4 (10th Cir. 2009) (“cases interpreting [§ 16(b)] inform our\nanalysis” of § 924(c)(3)(B)). The Government urges us to abandon this approach and\nreinterpret § 924(c)(3)(B); we address its argument in Parts IV-VI of this opinion.\n\n\n 7\n\ncrime.” Johnson, 135 S. Ct. at 2557 (interpreting 18 U.S.C. § 924(e)(2)(B)(ii)). Under\n\nthe residual clause, courts must use the statutory definition of an offense to imagine its\n\n“ordinary case,” and then consider whether this imagined ordinary case entails a\n\n“substantial risk” of force. Dimaya, 138 S. Ct. at 1211 (internal quotation marks\n\nomitted); see also 18 U.S.C. § 924(c)(3)(B).\n\n We call the analysis applicable to the residual clause the ordinary-case categorical\n\napproach. This ordinary-case categorical approach is “broader than” the elements-based\n\ncategorical approach applicable to the force clause, “in the sense that force need not\n\nactually be applied” in a residual clause offense. Leocal, 543 U.S. at 11.\n\n B.\n\n Simms contends that conspiracy to commit Hobbs Act robbery does not constitute\n\na crime of violence under the residual clause, § 924(c)(3)(B), because that clause — like\n\nthe similarly worded residual clauses analyzed in Johnson, 135 S. Ct. 2551, and Dimaya,\n\n138 S. Ct. 1204 — is void for vagueness.\n\n As Justice Kagan explained in Dimaya, “‘[t]he prohibition of vagueness in\n\ncriminal statutes’ . . . is an ‘essential’ of due process, required by both ‘ordinary notions\n\nof fair play and the settled rules of law.’” 138 S. Ct. at 1212 (plurality opinion) (quoting\n\nJohnson, 135 S. Ct. at 2557). Vague criminal statutes “invite the exercise of arbitrary\n\npower . . . by leaving people in the dark about what the law demands and allowing\n\nprosecutors and courts to make it up.” Id. at 1223–24 (Gorsuch, J., concurring in part and\n\nconcurring in the judgment). The void-for-vagueness doctrine thus ensures citizens have\n\nfair notice of prohibited conduct, guards against discriminatory enforcement of\n\n 8\n\nambiguous laws, and respects the foundational principle that only Congress — not the\n\nexecutive or the courts — is empowered to establish the bounds of proscribed conduct.\n\nId. at 1212 (plurality opinion).\n\n In Johnson, the Supreme Court struck down the residual clause of the Armed\n\nCareer Criminal Act (“ACCA”) as void for vagueness. 135 S. Ct. at 2557. ACCA\n\nenhances the sentence of those convicted of possessing a firearm in violation of 18\n\nU.S.C. § 922(g) if they have three or more prior convictions for a “serious drug offense”\n\nor for a “violent felony.” It defines “violent felony” as any felony that:\n\n (i) has as an element the use, attempted use, or threatened use of physical\n force against the person of another; or\n (ii) is burglary, arson, or extortion, involves use of explosives, or otherwise\n involves conduct that presents a serious potential risk of physical injury to\n another . . . .\n\n18 U.S.C. § 924(e)(2)(B) (emphasis added). The italicized portion is the ACCA residual\n\nclause. Johnson, 135 S. Ct. at 2555–56.\n\n The Johnson Court explained that “[t]wo features of the [ACCA] residual clause\n\nconspire[d] to make it unconstitutionally vague.” Id. at 2557. The clause left uncertainty\n\nabout both (1) “how to estimate the risk posed by a crime,” and (2) “how much risk it\n\ntakes for a crime to qualify as a violent felony.” Id. at 2557–58.\n\n The first problem arose because the residual clause “tie[d] the judicial assessment\n\nof risk to a judicially imagined ‘ordinary case’ of a crime, not to real-world facts or\n\nstatutory elements,” but “offer[ed] no reliable way” for judges to ascertain what the\n\n“ordinary case” involved. Id. Regarding the second problem, the Court clarified that it\n\nwas “one thing to apply an imprecise ‘serious potential risk’ standard to real-world facts,”\n\n 9\n\nbut “quite another to apply it to a judge-imagined abstraction,” as the ACCA residual\n\nclause required. Id. at 2558. The Court held that the combination of these two flaws\n\nrendered the ACCA residual clause unconstitutional: “Each of the uncertainties in the\n\nresidual clause may be tolerable in isolation, but ‘their sum makes a task for us which at\n\nbest could be only guesswork.’” Id. at 2560 (quoting United States v. Evans, 333 U.S.\n\n483, 495 (1948)).\n\n The Supreme Court reiterated this logic in Dimaya, when it held 18 U.S.C. § 16(b)\n\nunconstitutionally vague. 138 S. Ct. at 1215–16. That statute defines “crime of\n\nviolence,” a term incorporated into many criminal and immigration statutes, as:\n\n (a) an offense that has as an element the use, attempted use, or threatened\n use of physical force against the person or property of another, or\n (b) any other offense that is a felony and that, by its nature, involves a\n substantial risk that physical force against the person or property of another\n may be used in the course of committing the offense.\n\n18 U.S.C. § 16. Section 16(b) is similarly known as the “residual clause.” Dimaya, 138\n\nS. Ct. at 1212.\n\n In Dimaya, the Court held that a “straightforward application” of Johnson made\n\nclear that § 16(b), like the ACCA residual clause, was void for vagueness. Id. at 1213.\n\nIn doing so, the Court carefully explained that the proper ordinary-case categorical\n\nanalysis did not ask “whether ‘the particular facts’ underlying a conviction posed the\n\nsubstantial risk that § 16(b) demands,” nor whether “the statutory elements of a crime\n\nrequire (or entail) the creation of such a risk in each case that the crime covers.” Id. at\n\n1211 (quoting Leocal, 543 U.S. at 7). Rather, a majority of the Court agreed that\n\n“§ 16(b) requires a court to ask whether the ordinary case of an offense poses the\n\n 10\n\nrequisite risk.” Id. (internal quotation marks omitted); see also id. at 1235 (Roberts, C.J.,\n\ndissenting) (identifying ordinary-case categorical approach as the way “courts should\n\nassess whether a particular crime ‘by its nature’ involves a risk of the use of physical\n\nforce”).\n\n As a result, § 16(b) possessed “the same two features that conspired to make\n\nACCA’s residual clause unconstitutionally vague.” Id. at 1216 (majority opinion)\n\n(alterations and internal quotation marks omitted) (quoting Johnson, 135 S. Ct. at 2557).\n\nAs with the ACCA residual clause, § 16(b) required courts to “identify a crime’s\n\n‘ordinary case’ in order to measure the crime’s risk.” Id. at 1215. But the statute failed\n\nto provide any guidance on how to “divin[e] the conduct entailed in a crime’s ordinary\n\ncase.” Id. “And § 16(b) also possesse[d] the second fatal feature of ACCA’s residual\n\nclause: uncertainty about the level of risk that ma[de] a crime ‘violent.’” Id. Thus, like\n\nthe ACCA residual clause, the Court held that § 16(b) violated due process. Id. at 1223.\n\n C.\n\n With these precedents in mind, we turn to the question at hand: is the materially\n\nidentical statute at issue here also unconstitutionally vague?\n\n Like the statutes examined in Johnson and Dimaya, § 924(c)(3)(B) requires a\n\ncourt to imagine the idealized ordinary case of a crime while providing no guidance on\n\nhow to do so, rendering any judicial account of the ordinary case wholly speculative.\n\nDimaya, 138 S. Ct. at 1213–14; Johnson, 135 S. Ct. at 2557–58. After conceiving of this\n\njudicial abstraction, a court must then assess its speculation using the same vague\n\nstandard of “substantial risk” as § 16(b) required in Dimaya. 138 S. Ct. at 1214. This\n\n 11\n\nconjectural exercise suffers from the same two fundamental flaws that, in combination,\n\nrendered the statutory provisions in Johnson and Dimaya void for vagueness. Dimaya,\n\n138 S. Ct. at 1213–16; Johnson, 137 S. Ct. at 2557–58.\n\n Section 924(c)(3)(B) is therefore unconstitutional. Three other circuits have\n\nreached this conclusion. United States v. Davis, 903 F.3d 483, 485–86 (5th Cir. 2018)\n\n(per curiam), cert. granted, 2019 WL 98544 (U.S. Jan. 4, 2019) (No. 18-431); United\n\nStates v. Eshetu, 898 F.3d 36, 37 (D.C. Cir. 2018) (per curiam), petition for reh’g en banc\n\nfiled, No. 15-3020 (Aug. 31, 2018); United States v. Salas, 889 F.3d 681, 684–86 (10th\n\nCir. 2018), petition for cert. filed, No. 18-428 (U.S. Oct. 3, 2018). 3\n\n To understand why, consider a situation where a defendant is charged with\n\npossessing a gun in conjunction with witness tampering. See 18 U.S.C. § 1512(b);\n\nDimaya, 138 S. Ct. at 1232 (Gorsuch, J., concurring in part and concurring in the\n\njudgment). As the Supreme Court has explained, § 924(c) “requires the prosecution to\n\nmake two showings”: the commission of an underlying crime and the use of a firearm.\n\nSmith v. United States, 508 U.S. 223, 227–28 (1993); see also Rosemond v. United States,\n\n 3\n Before Dimaya was decided, a panel of the Eleventh Circuit concluded that the\n§ 924(c)(3)(B) “determination [is] more precise” than that under the ACCA residual\nclause, because § 924(c) requires a “‘nexus’ between the . . . firearm offense and the\npredicate crime of violence.” Ovalles v. United States, 861 F.3d 1257, 1265–66 (11th\nCir. 2017), reh’g en banc granted, opinion vacated, 889 F.3d 1259 (11th Cir. 2018), and\non reh’g en banc, 905 F.3d 1231 (11th Cir. 2018), and opinion reinstated in part, 905\nF.3d 1300 (11th Cir. 2018). But this conclusion is premised on a misunderstanding of\n§ 924(c)(3)(B). In defining “crime of violence,” the statute directs us to consider what\nthe underlying offense entails “by its nature,” not what it entails when committed using a\nfirearm. 18 U.S.C. § 924(c)(3)(B). Therefore, the firearm “nexus” offers no meaningful\nguidance on what satisfies the distinct crime of violence element. See Salas, 889 F.3d at\n685–86.\n\n 12\n\n572 U.S. 65, 75 (2014) (“§ 924(c) . . . punishes the temporal and relational conjunction of\n\ntwo separate acts, on the ground that together they pose an extreme risk of harm.”).\n\n Thus, to evaluate whether witness tampering satisfies the “crime of violence”\n\nelement of a § 924(c) violation, a court must assess whether the ordinary case of witness\n\ntampering, with or without a firearm, “involves a substantial risk [of] physical force.” 18\n\nU.S.C. § 924(c)(3)(B). And when “divining the conduct entailed in [the] crime’s\n\nordinary case,” the court must utilize some as-yet-unspecified method — “Surveys?\n\nExperts? Google? Gut instinct?” Dimaya, 138 S. Ct. at 1215 (majority opinion) (citing\n\nJohnson, 135 S. Ct. at 2557). The statute provides no guidance for this “abstract\n\ninquiry.” See Dimaya, 138 S. Ct. at 1215 (quoting Johnson, 135 S. Ct. at 2561). Instead,\n\n§ 924(c)(3)(B) effectively requires judges to define the scope of criminal liability, and it\n\ndirects them to do so using an unmoored, subjective abstraction that deprives the public\n\nof fair notice.\n\n Just as in Dimaya, a “straightforward application” of controlling precedent to the\n\nchallenged statute requires us to strike it down. Dimaya, 138 S. Ct. at 1213. The\n\nSupreme Court has made clear that where a statute requires courts to assess “both an\n\nordinary-case requirement and an ill-defined risk threshold,” it is unconstitutional. Id. at\n\n1223; see also Johnson, 135 S. Ct. at 2557–60. That principle controls here. Any\n\nconviction involving § 924(c)(3)(B) is subject to the same “guesswork,” “intuition,”\n\n“arbitrary enforcement,” and lack of “fair notice” that plagued both § 16(b) and the\n\nACCA residual clause. Dimaya, 138 S. Ct. at 1223 (quoting Johnson, 135 S. Ct. at\n\n2557–59). Because this “produces more unpredictability and arbitrariness than the Due\n\n 13\n\nProcess Clause tolerates,” id. (quoting Johnson, 135 S. Ct. at 2558), we must conclude\n\nthat § 924(c)(3)(B) is unconstitutionally vague.\n\n\n\n III.\n\n The United States concedes that if we adhere to the ordinary-case categorical\n\napproach applied by the Supreme Court in Leocal, Johnson, and Dimaya, we must\n\ninvalidate § 924(c)(3)(B). The Government, however, urges us to jettison this established\n\ninterpretation and adopt a new reading of the challenged statutory language that employs\n\na conduct-specific approach to the crime of violence analysis. This conduct-specific\n\napproach would consider the facts of each individual case, rather than the statutory\n\ndefinition of the underlying offense.\n\n Before addressing the merits of the Government’s claim, we must determine\n\nwhether to allow it to raise an argument that it previously abandoned. Although the\n\nGovernment initially argued in the alternative that a conduct-specific interpretation of\n\n§ 924(c)(3)(B) was tenable, Gov. Br. at 28–31, it later expressly disclaimed this reading\n\nof § 924(c)(3)(B). The Government did so by submitting to us a written statement that\n\n“the position of the United States [is] that the categorical approach is the proper\n\ninterpretation of the statute, and it is wholly unaffected by Johnson.” Gov. 28(j) Letter at\n\n2 (Oct. 19, 2016). After the Supreme Court decided Dimaya and we ordered\n\nsupplemental briefing, the Government again reversed course, deeming a conduct-\n\nspecific reading of § 924(c)(3)(B) freshly controlling. Given these changing stances,\n\n\n\n 14\n\nSimms asserts that the Government has forfeited any argument for a conduct-specific\n\napproach. 4\n\n The Government offers two reasons why we should excuse its voluntary\n\nwithdrawal of a conduct-specific interpretation of § 924(c)(3)(B). First, it argues that\n\nDimaya represented “an intervening change in the law recognizing an issue that was not\n\npreviously available.” United States v. Chittenden, 896 F.3d 633, 639 (4th Cir. 2018)\n\n(internal quotation marks omitted). At oral argument, the Government elaborated that the\n\nlongstanding position of the United States that § 924(c)(3)(B) required an ordinary-case\n\ncategorical approach came “more by way of assumption” than reason, and that Dimaya\n\n“caused a lot of searching in the Department [of Justice] to find the right answer.” Oral\n\nArg. at 1:27:41, 1:29:00.\n\n This claim does not hold water. Dimaya was not the first case to indicate that the\n\nordinary-case categorical approach generated serious constitutional doubts. At the very\n\nleast, the Government was on notice as to these vagueness concerns after Johnson was\n\ndecided in 2015. Indeed, the Ninth Circuit held § 16(b) unconstitutionally vague four\n\nmonths later. See Dimaya v. Lynch, 803 F.3d 1110, 1120 (9th Cir. 2015), aff’d sub nom.\n\n\n 4\n Simms frames this as “waiver,” which we have defined as “identif[ying] an\nissue, and then explicitly withdraw[ing] it.” United States v. Robinson, 744 F.3d 293, 298\n(4th Cir. 2014) (internal quotation marks omitted). But waiver, in a technical sense,\nconcerns a party’s relinquishment of rights before a district court; where a party raises\nand then knowingly withdraws a claim before the district court, there is no error for us to\nreview. United States v. Olano, 507 U.S. 725, 733 (1993). Because the Government did\nnot raise a conduct-specific argument before the district court, its double-turnabout before\nus is better treated as abandonment or forfeiture of a claim that we retain discretion to\nreview. Id. at 733–34.\n\n 15\n\nSessions v. Dimaya, 138 S. Ct. 1204. But a full year thereafter, the Government asserted\n\nto us that “the categorical approach [was] the proper interpretation” of § 924(c)(3)(B) and\n\nthat this conclusion was “wholly unaffected by Johnson.” Gov. 28(j) Letter at 2. The\n\nUnited States has yet to offer a coherent justification for its shifts in position, and its\n\ninvocation of Dimaya offers no answer.\n\n The Government next asserts that excusing its abandonment would not prejudice\n\nSimms, who has had a full opportunity to respond to the Government’s claims. That is\n\ncertainly enough to convince us that we can look past the Government’s change of heart,\n\ne.g., United States v. Ramos-Cruz, 667 F.3d 487, 496 n.5 (4th Cir. 2012), but not\n\nnecessarily that we should do so. As the Government is aware, we routinely exercise our\n\ndiscretion in favor of a strict reading of forfeiture. See, e.g., United States v. Brown, 742\n\nF. App’x 742, 745 n.3 (4th Cir. 2018) (“[W]e conclude that Brown waived the argument\n\nthat 18 U.S.C. § 924(c)(3)(B) (2012) is unconstitutional by failing to raise it in his\n\nopening brief.”); United States v. Khoa Dang Hoang, 737 F. App’x 136, 138 n.* (4th Cir.\n\n2018) (deeming forfeited defendant’s challenge to validity of Miranda waiver); see also\n\nUnited States v. Cannon, 740 F. App’x 785, 791 n.2 (4th Cir. 2018) (deeming forfeited, at\n\nGovernment’s suggestion, defendant’s undeveloped sentencing challenges); United States\n\nv. Ballard, 727 F. App’x 757, 760 n.* (4th Cir. 2018) (same regarding defendant’s\n\nstatutory speedy trial claim).\n\n Nevertheless, in this case, we opt to proceed to the merits in view of the\n\nexceptional importance and recurring nature of the question presented. Particularly given\n\n\n\n 16\n\nthe markedly effective presentation by the parties and the amici before the en banc court,\n\nwe see no reason to defer adjudication of the Government’s current argument.\n\n\n\n IV.\n\n The Government now contends that we must apply a different mode of analysis to\n\n§ 924(c)(3)(B), a mode that the Supreme Court expressly rejected in both Dimaya and\n\nJohnson.\n\n Specifically, the Government insists that the best reading of the statute — which,\n\nrecall, asks whether “an offense that is a felony . . . by its nature[] involves a substantial\n\nrisk that physical force . . . may be used in the course of committing the offense” —\n\ndirects a court to analyze an offender’s specific conduct by diving into the facts before it\n\ninstead of limiting the analysis to the offense’s ordinary case. In support of this\n\ncontention, the Government argues that “the Supreme Court has been very clear” that the\n\ncategorical approach is “essentially a saving construction” designed only to avoid the risk\n\nof unfairness that comes with reviewing conduct that underlies long-past convictions.\n\nOral Arg. at 1:19:05. Alternatively, the Government claims that even if a conduct-\n\nspecific approach is not the best reading of § 924(c)(3)(B), we still must adopt it to avoid\n\nstriking down the statute. Three of our sister circuits have embraced the Government’s\n\nsuggestion. 5\n\n\n 5\n See United States v. Douglas, 907 F.3d 1, 16 (1st Cir. 2018), petition for cert.\nfiled, No. 18-7331 (U.S. Jan. 7, 2019); Ovalles v. United States, 905 F.3d 1231, 1253\n(11th Cir. 2018) (en banc); United States v. Barrett, 903 F.3d 166, 184 (2d Cir. 2018),\n(Continued)\n 17\n\n We cannot do so. The Supreme Court did not invent the categorical approach out\n\nof whole cloth, as the Government would have us believe. While some other statutes\n\ninvoking categorical analysis have been less than clear, the text and structure of\n\n§ 924(c)(3)(B) unambiguously require courts to analyze the attributes of an “offense that\n\nis a felony . . . by its nature” — that is, categorically. And the Government’s\n\ncomparisons to cases involving very different statutes, rather than bolstering its\n\npreference for a new mode of analysis, support adherence to the established ordinary-case\n\ncategorical approach.\n\n A.\n\n As a preliminary matter, the Government presents a flawed historical premise. It\n\nclaims that the categorical approach is nothing more than a “saving construction,” Oral\n\nArg. at 1:19:05, “purely [a] judge-made doctrine” that was “first endorsed” less than\n\nthirty years ago, Gov. Supp. Br. at 17 (internal quotation marks omitted). Further, the\n\nGovernment asserts, this doctrine is grounded entirely in external considerations far\n\nafield from congressional language or intent.\n\n\n\n\npetition for cert. filed, No. 18-6985 (U.S. Dec. 3, 2018). But see Davis, 903 F.3d at 485\n(finding “a suggestion by a minority of justices in [Dimaya]” insufficient to overrule\ncircuit precedent requiring ordinary-case categorical approach); Eshetu, 898 F.3d at 37\n(emphasizing that “Dimaya nowise calls into question” circuit precedent requiring “a\ncategorical approach”); Salas, 889 F.3d at 685 (holding § 924(c)(3)(B) unconstitutionally\nvague), reh’g and reh’g en banc denied, No. 16-2170 (May 23, 2018) (denying\nGovernment’s petition for rehearing on constitutional avoidance grounds).\n\n\n 18\n\n This is simply not so. Although categorical analysis may be complicated, the\n\nrationale for it is simple and long-established: if Congress has conditioned a statutory\n\npenalty on commission of an offense generally — rather than on specific acts — courts\n\nmust consider the crime as defined, rather than the offender’s conduct. See, e.g., Shepard\n\nv. United States, 544 U.S. 13, 19 (2005) (emphasizing Congress’s “language imposing\n\nthe categorical approach” in ACCA); Leocal, 543 U.S. at 7 (highlighting Congress’s\n\nusage of “offense . . . by its nature” in § 16(b)). Such analysis became more frequent in\n\nthe mid-1980s as Congress added general terms like “violent felony,” “crime of\n\nviolence,” and “aggravated felony” to the United States Code, but the underlying\n\nprinciple is far from novel. Indeed, it has been an important part of American\n\njurisprudence for more than a century. See, e.g., U.S. ex rel. Guarino v. Uhl, 107 F.2d\n\n399, 400 (2d Cir. 1939) (L. Hand, J.) (explaining that “deporting officials may not\n\nconsider the particular conduct for which the alien has been convicted” in determining\n\nwhether a crime involved moral turpitude meriting deportation (citing U.S. ex rel. Mylius\n\nv. Uhl, 210 F. 860, 863 (2d Cir. 1914))).\n\n Moreover, the Supreme Court has always rooted the categorical approach in the\n\nstatutory language chosen by Congress and consistently defended this approach as a\n\nmeans of effectuating congressional intent. Thus, when analyzing ACCA four years after\n\nits passage, the Court looked first to “the language of” the statute, and only then to\n\nlegislative history and practical concerns, to conclude that a categorical approach was\n\n“the only plausible interpretation of § 924(e)(2)(B)(ii).” Taylor v. United States, 495\n\nU.S. 575, 600–02 (1990). Similarly, when defending application of the ordinary-case\n\n 19\n\ncategorical approach as it relates to ACCA’s residual clause in 2015, the Court again\n\nbegan with the statutory text before considering other arguments. Johnson, 135 S. Ct. at\n\n2562.\n\n The Supreme Court’s interpretation of ACCA in Taylor and Johnson was, of\n\ncourse, secondarily informed by considerations beyond the statutory text. But tellingly,\n\nthe Court has deemed the text of § 16(b) — a statute far clearer than the ACCA residual\n\nclause and materially identical to the statute at issue here — so plain as to speak for itself.\n\nThus, in 2004, when the Court first interpreted § 16(b) to require the ordinary-case\n\ncategorical approach, it relied only on the text of the statute, and it did not invoke\n\nlegislative history or practical concerns. Leocal, 543 U.S. at 7; accord Dimaya, 138 S.\n\nCt. at 1204 (plurality opinion) (noting four-Justice plurality, Chief Justice, and\n\nGovernment all “accept[ed] that § 16(b), as long interpreted, demands a categorical\n\napproach”). The Government’s attempt to rewrite this history is utterly unpersuasive.\n\n B.\n\n Setting aside the origins of the categorical approach, we have reviewed\n\n§ 924(c)(3)(B) on a clean slate and still find no reasonable construction of its text that\n\nsupports the Government’s conduct-specific approach. The statutory structure, as well as\n\nCongress’s use of materially identical language to implement an ordinary-case\n\ncategorical approach in § 16(b), render our conclusion inescapable. Whatever a judge’s\n\npersonal feelings as to what does or does not constitute a crime of violence, we are bound\n\nto apply the definition that Congress has prescribed. And Congress could hardly have\n\nwritten a clearer call for the ordinary-case categorical approach than § 924(c)(3)(B).\n\n 20\n\n The text of a statute is a court’s first and foremost guide to its meaning. See, e.g.,\n\nEsquivel-Quintana v. Sessions, 137 S. Ct. 1562, 1568 (2017) (noting that when\n\ninterpreting a statute, courts “begin, as always, with the text”). Here, the plain text of\n\n§ 924(c)(3)(B) requires application of the ordinary-case categorical approach. The\n\ncombination in § 924(c)(3)(B) of the phrase “offense that is a felony” with the qualifier\n\n“by its nature” makes Congress’s intent apparent.\n\n As the Government itself admits, the definition of “nature” is “the basic or\n\ninherent features, character, or quality of something.” Oxford Dictionary of English 1183\n\n(3d ed. 2010). Thus, § 924(c)(3)(B) directs courts to consider only the basic or inherent\n\nfeatures of “an offense that is a felony.” 18 U.S.C. § 924(c)(3)(B); see also Dimaya, 138\n\nS. Ct. at 1217–18 (plurality opinion) (explaining that phrase “by its nature” directs courts\n\n“to figure out what an offense normally . . . entails, not what happened to occur on one\n\noccasion”). Had Congress intended a conduct-specific analysis instead, “it presumably\n\nwould have said so; other statutes, in other contexts, speak in just that way.” Descamps\n\nv. United States, 570 U.S. 254, 267–68 (2013); see, e.g., 18 U.S.C. § 1031(b)(2)\n\n(imposing heightened penalties for fraud offenses that “involve[] a conscious or reckless\n\nrisk of serious personal injury”); 18 U.S.C. § 2332b(a)(1)(B) (punishing certain\n\n“conduct” that “creates a substantial risk of serious bodily injury”).\n\n Moreover, we cannot adopt a reading of § 924(c)(3)(B) that renders part of the\n\nstatute superfluous over one that gives effect to its “every clause and word.” United\n\nStates v. Menasche, 348 U.S. 528, 538–39 (1955) (quoting Inhabitants of Montclair Twp.\n\nv. Ramsdell, 107 U.S. 147, 152 (1883)). This well-established rule against surplusage\n\n 21\n\nfurther cuts against the Government’s conduct-specific reading, which would empty the\n\nphrase “by its nature” of meaning. Indeed, even under the Government’s interpretation,\n\ngiving “by its nature” meaning would shift the § 924(c)(3)(B) inquiry away from\n\nconduct-specific facts and back towards a subjective consideration of that conduct’s\n\n“inherent features” — that is to say, another version of ordinary-case analysis.\n\n The Government does not even attempt to address this problem. 6 Instead, it\n\nsimply quotes a dissent in Dimaya to contend that in the context of § 924(c)(3)(B), “the\n\nphrase ‘by its nature’ is reasonably understood to ‘mean only that an offender who\n\nengages in risky conduct cannot benefit from the fortuitous fact that physical force was\n\nnot actually used during his offense.’” Gov. Supp. Br. at 14 (quoting Dimaya, 138 S. Ct.\n\nat 1254 (Thomas, J., dissenting)). One of the dissenters here similarly insists that “by its\n\nnature” “broad[ens]” the scope of § 924(c)(3)(B), while another argues (seemingly to the\n\ncontrary) that the phrase actually “limits the residual clause” by excluding conduct that\n\nrisks force “merely incidentally or by happenstance.”\n\n But the Dimaya Court did not embrace any of these readings of this text. And for\n\ngood reason: each would still leave “by its nature” wholly superfluous. If we strike that\n\nphrase, § 924(c)(3)(B)’s remaining language would require a finding that an offense\n\n“involves a substantial risk that physical force . . . may be used in the course of\n\ncommitting the offense.” 18 U.S.C. § 924(c)(3)(B) (emphasis added). This text read on\n\n 6\n Nor do any of the courts of appeals that have embraced a conduct-specific\napproach. For example, while the First Circuit found it “plausible that ‘by its nature’\nrefers to the real-world conduct of a particular offense,” it did not consider the surplusage\nproblem that this interpretation creates. Douglas, 907 F.3d at 8.\n\n 22\n\nits own would still encompass both actual uses of physical force and otherwise “risky”\n\nconduct in which force was not used. And the requirement that any risk be “substantial”\n\nwould independently exclude “incidental” uses of force. In other words, under the\n\nGovernment’s conduct-specific reinterpretation, § 924(c)(3)(B) would have the same\n\nmeaning without the phrase “by its nature” as it would with this phrase. This would drain\n\nthe phrase “by its nature” of any effect, violating a cardinal rule of statutory construction.\n\n The conclusion that “crime of violence” must be defined categorically is made\n\neven plainer when we consider the statutory context, as we must. See Davis v. Mich.\n\nDep’t of Treasury, 489 U.S. 803, 809 (1989) (“[W]ords of a statute must be read in their\n\ncontext and with a view to their place in the overall statutory scheme.”). The\n\nGovernment concedes that § 924(c)(3)(A), which covers one half of the “crime of\n\nviolence” definition in § 924(c), mandates a categorical approach. Gov. Supp. Br. at 4. It\n\nwould stand to reason that § 924(c)(3)(B), the other half of this definition, also requires a\n\ncategorical approach rather than analysis of “the facts of each defendant’s conduct.”\n\nTaylor, 495 U.S. at 601.\n\n This conclusion is confirmed by the Supreme Court’s refusal to give statutory text\n\nvariable meanings “depending on the presence or absence of constitutional concerns in\n\neach individual case,” explaining that such a “novel interpretive approach . . . would\n\nrender every statute a chameleon.” Clark v. Martinez, 543 U.S. 371, 382 (2005). Under\n\nthe longstanding interpretation of § 924(c)(3), the statute’s single reference to an “offense\n\nthat is a felony” has a single meaning: it refers to a crime as defined by statute.\n\nAccepting the Government’s interpretation would require us instead to give this phrase\n\n 23\n\ntwo contradictory meanings, depending on whether the force clause or the residual clause\n\nis in play. Specifically, the Government would have us read “offense that is a felony” to\n\nrefer to an offense as defined by statute in prosecutions under the force clause, but to\n\ncase-specific conduct in prosecutions under the residual clause. We refuse to so distort\n\nthe statutory text.\n\n Furthermore, § 924(c)(1)(A), which outlines the elements of a § 924(c) violation,\n\nexpressly refers to “a crime of violence . . . that provides for an enhanced punishment if\n\ncommitted by the use of a deadly or dangerous weapon or device.” This phrasing would\n\nmake no sense under a conduct-specific definition of “crime of violence,” as only\n\nstatutes, not conduct-specific facts, can “provide[] for” an amount of punishment. 7\n\n\n 7\n The Government responds by citing the phrase “during and in relation to any\ncrime of violence,” 18 U.S.C. § 924(c)(1)(A) (emphasis added), to argue for a conduct-\nspecific reading of “crime of violence.” The argument fails. In fact, it is not unusual to\ndescribe specific conduct or circumstances (like use of a firearm) “in relation to” a\ncategorically defined generic offense (like a crime of violence). For example, in\nprosecutions under the force clause, § 924(c)(1)(A) itself refers to specific conduct (use\nof a firearm) “during and in relation to” a generic offense (a categorically defined crime\nof violence). In § 924(c) prosecutions where the predicate offense is a “drug trafficking\ncrime” rather than a “crime of violence,” § 924(c)(1)(A) again refers to specific conduct\n“during and in relation to” a categorically defined crime. Congress has utilized an\nanalogous approach in other statutes that incorporate the categorical “crime of violence”\ndefinition in § 16. See, e.g., 18 U.S.C. § 929(a)(2) (criminalizing use of armor-piercing\nammunition “during and in relation to the commission of a crime of violence”); 18\nU.S.C. § 1956(a)(3) (imposing criminal penalties for “conduct[ing] a financial transaction\ninvolving property . . . used to conduct or facilitate” a crime of violence); 18 U.S.C.\n§ 25(b) (multiplying maximum sentence for adult who “intentionally uses a minor to\ncommit a [federal] crime of violence”). And the Supreme Court has similarly interpreted\na misdemeanor domestic violence statute to require a circumstance-specific analysis of\nwhether a crime was “committed by” an offender with a “specified domestic\nrelationship” to the victim, and a categorical analysis as to whether the crime requires\nforce as an element. United States v. Hayes, 555 U.S. 415, 426 (2009).\n\n\n 24\n\n Finally, the Government would have us interpret the materially identical 34-word\n\nphrase in § 924(c)(3)(B) and § 16(b) in entirely different ways. 8 This argument flies in\n\nthe face of the traditional rule that “a legislative body generally uses a particular word\n\nwith a consistent meaning in a given context.” Erlenbaugh v. United States, 409 U.S.\n\n239, 243 (1972). Whatever force this interpretive presumption may have as to one\n\n“particular word,” it must carry more as applied to the 34-word phrase replicated in\n\n§ 924(c)(3)(B) and § 16(b). See supra n.8. The presumption has more force still because\n\nCongress initially added “crime of violence” to § 924(c) and created § 16(b) in the same\n\nlegislative enactment. 9 See Gustafson v. Alloyd Co., Inc., 513 U.S. 561, 570 (1995)\n\n(“[T]he normal rule of statutory construction” is that “identical words used in different\n\nparts of the same act are intended to have the same meaning.” (internal quotation marks\n\nomitted)); Erlenbaugh, 409 U.S. at 244 (noting that presumption of consistent meaning\n\n“certainly makes the most sense when the statutes were enacted by the same legislative\n\nbody at the same time”). Thus, it is unsurprising that the Government has been unable to\n\n\n 8\n Compare 18 U.S.C. § 924(c)(3) (“offense that is a felony and[] . . . that by its\nnature, involves a substantial risk that physical force against the person or property of\nanother may be used in the course of committing the offense”), with 18 U.S.C. § 16(b)\n(“offense that is a felony and that, by its nature, involves a substantial risk that physical\nforce against the person or property of another may be used in the course of committing\nthe offense”).\n 9\n Comprehensive Crime Control Act, Pub. L. No. 98–473, tit. II, § 1005(a), 98\nStat. 1976, 2138–39 (1984) (amending § 924(c) to reference “crime[s] of violence,” as\ndefined in new § 16); id. § 1001, 98 Stat. at 2136 (enacting § 16); see also id. §§ 1801–\n03, 98 Stat. at 2185 (enacting ACCA). Congress enacted § 924(c)(3)(B) two years later,\nadopting wording materially identical to § 16(b). Firearm Owners’ Protection Act, Pub.\nL. No. 99–308, § 104, 100 Stat. 449, 456–59 (1986).\n\n 25\n\ncite even one case in which the Supreme Court or this court have interpreted two\n\nmaterially identical statutes differently, as it urges us to do with § 924(c)(3)(B) and\n\n§ 16(b).\n\n In sum, our de novo application of ordinary textual analysis yields a mountain of\n\n“textual evidence” that § 924(c)(3)’s residual clause — “like ACCA’s, except still more\n\nplainly” — “has no ‘plausible’ fact-based reading.” Dimaya, 138 S. Ct. at 1218 (plurality\n\nopinion) (quoting Johnson, 135 S. Ct. at 2562); see also id. at 1235 (Roberts, C.J.,\n\ndissenting) (explaining that the ordinary-case categorical approach outlined in Leocal\n\n“provides a model for how courts should assess whether a particular crime ‘by its nature’\n\ninvolves a risk of the use of physical force” (quoting § 16(b))). 10\n\n C.\n\n Resisting this conclusion, the Government contends that the phrases “offense,”\n\n“felony,” “by its nature,” “involves,” and “committing the offense” in § 924(c)(3)(B)\n\n“compel” a conduct-specific approach. Gov. Supp. Br. at 10.\n\n Each of these terms can be susceptible to a conduct-specific analysis in isolation.\n\nSee Nijhawan v. Holder, 557 U.S. 29, 33–34 (2009) (construing statute containing the\n\nwords “offense” and “felony”); Hayes, 555 U.S. at 420–29 (construing statute containing\n\nthe word “offense”); Taylor, 495 U.S. at 600–01 (construing statute containing the word\n\n 10\n Despite the foregoing analysis, Judge Richardson maintains that we “rewrite[]\nhistory” to “claim[] that the Supreme Court has already resolved this issue.” Of course,\nwe claim no such thing. Perhaps our colleague only means to assert that our conclusions\naccord with the reasoning of four Justices interpreting materially identical text mere\nmonths ago, as well as the indication of the Chief Justice; to that assertion, we readily\nagree.\n\n 26\n\n“involves”); United States v. Price, 777 F.3d 700, 708–09 (4th Cir. 2015) (construing\n\nstatute containing the terms “by its nature” and “involves”). But that hardly establishes\n\nthat these five terms are susceptible to such a reading when appearing together in a single\n\nshort statute. Rather, each of the cases on which the Government relies involves only\n\nfragments of the language in § 924(c)(3). Just as importantly, in none of these cases did\n\nthe court actually rely on these fragments in reaching its holding. In fact, the reasoning\n\nthat underlies each of the Government’s cases buttresses our conclusion that the text of\n\n§ 924(c)(3)(B) requires an ordinary-case categorical approach.\n\n Consider Nijhawan and Hayes. In both opinions, the Supreme Court interpreted\n\nstatutes that paired a reference to “offense” with detailed qualifiers far too specific to\n\nrefer to generic crimes. Nijhawan concerned an immigration statute that included only\n\noffenses “involv[ing] fraud or deceit in which the loss to the victim or victims exceed[ed]\n\n$10,000.” 8 U.S.C. § 1101(a)(43)(M)(i). In Hayes, the qualifier was even more specific:\n\nthe relevant criminal statute only covered offenses “committed by a current or former\n\nspouse, parent, or guardian of the victim, by a person with whom the victim shares a\n\nchild in common, by a person who is cohabiting with or has cohabited with the victim as\n\na spouse, parent, or guardian, or by a person similarly situated to a spouse, parent, or\n\nguardian of the victim.” 18 U.S.C § 921(a)(33)(A)(ii).\n\n Faced with these precise qualifiers, the Supreme Court concluded that Congress\n\nmust have intended a conduct-specific approach for these statutes to have any force. See\n\nNijhawan, 557 U.S. at 37–38 (holding that “to have any meaning at all,” qualifier “must\n\nrefer to the particular circumstances in which an offender committed the crime”); Hayes,\n\n 27\n\n555 U.S. at 427 (explaining that categorical reading of qualifier would render statute “a\n\ndead letter in some two-thirds of the States from the very moment of its enactment”\n\n(internal quotation marks omitted)). The specificity of each statute — not any talismanic\n\nuse of “offense” or “involves” — was the crux of both rulings.\n\n The “substantial risk of physical force” proviso in § 924(c)(3)(B) is a far cry from\n\nthe specific qualifiers in Nijhawan and Hayes. Rather, the proviso in § 924(c)(3)(B) is\n\nmaterially identical to that in § 16(b), and it is similar to the force requirement in statutes\n\nthat employ the elements-based categorical approach, like § 924(c)(3)(A) and § 16(a).\n\nNijhawan and Hayes thus highlight the relative “absence of terms alluding to a crime’s\n\ncircumstances” in § 924(c)(3)(B) beyond those also present in § 16(b). Dimaya, 138 S.\n\nCt. at 1218 (plurality opinion); see also id. at 1217 (“Simple references to a ‘conviction,’\n\n‘felony,’ or ‘offense,’ we have stated, are ‘read naturally’ to denote the ‘crime as\n\ngenerally committed.’” (quoting Nijhawan, 557 U.S. at 34)). The differences between\n\nthese statutes and § 924(c)(3)(B) reinforce rather than defeat a categorical reading here.\n\n Moreover, despite seeking to rely on Nijhawan, the Government overlooks one of\n\nNijhawan’s key teachings. For there, the Court expressly recognized that where\n\nCongress “uses similar statutory language and similar statutory structure in two adjoining\n\nprovisions, it normally intends similar interpretations.” Nijhawan, 557 U.S. at 39. Here,\n\nCongress did not just use “similar” language in the “two adjoining provisions” of\n\n§ 924(c)(3)(A) and § 924(c)(3)(B): it tied both definitions to the same use of the\n\nintroductory phrase “offense that is a felony.” As we have already explained, the\n\n\n\n 28\n\nGovernment’s reading would give that phrase a conduct-specific interpretation under one\n\nprovision and a categorical interpretation under the adjoining provision.\n\n As to Taylor, the Government’s reliance is inexplicable. It cites that case alone for\n\nthe proposition that “the Supreme Court has previously relied on the absence of the word\n\n‘involves’ as indicating that a categorical approach is required.” Gov. Supp. Br. at 13\n\n(citing Taylor, 495 U.S. at 600). But Taylor did not rely on the absence of the word\n\n“involves” to require use of the categorical approach. The Taylor Court simply\n\nrecognized that the ACCA force clause defined a “violent felony” as one that “‘has as an\n\nelement’ — not any crime that, in a particular case, involves — the use or threat of\n\nforce.” 495 U.S. at 600 (quoting § 924(e)(2)(B)(i)). The Government’s contrary\n\nargument is especially unconvincing given that the Supreme Court has held that the\n\nACCA residual clause and § 16(b), both of which use the word “involves,” mandate the\n\nordinary-case categorical approach. E.g., Johnson, 135 S. Ct. at 2561–62; Leocal, 543\n\nU.S. at 7.\n\n The Government’s reliance on Taylor, like its reliance on Nijhawan, also ignores a\n\ncritical element of the Supreme Court’s analysis. The Taylor Court reasoned that the\n\nterm “burglary” as used in ACCA “most likely refer[red] to the elements of the statute of\n\nconviction, not to the facts of each defendant’s conduct,” in part because of its proximity\n\nto the ACCA force clause. 495 U.S. at 600–01. In this case, the proximity of\n\n§ 924(c)(3)(B) to the force clause in § 924(c)(3)(A) warrants a similar inference. Thus,\n\nTaylor offers no more support to the Government’s novel argument than Nijhawan or\n\nHayes.\n\n 29\n\n Finally, the Government emphasizes that we have applied a conduct-specific\n\nanalysis to a provision of the Sex Offender Registration and Notification Act (“SORNA”)\n\nthat uses the phrase “by its nature.” Price, 777 F.3d at 708–09. But in fact, each step of\n\nour textual analysis in that case supports a contrary result here.\n\n In Price, we followed Nijhawan and Hayes to hold that “where a statute contains\n\nlanguage that . . . refers to specific circumstances or conduct,” “Congress meant to allow\n\nthe circumstance-specific approach’s more searching factual inquiry.” Id. at 708\n\n(alteration in original) (internal quotation marks omitted). Here, Congress’s omission of\n\nthis conduct-specific language in § 924(c)(3)(B) warrants the opposite inference. In\n\nPrice, we noted that because Congress referenced “elements” in one subsection of\n\nSORNA, its contrasting terminology of “a criminal offense” in the next required a\n\nbroader reading under the canon of meaningful variation. Id. at 708–09. Here, the\n\nordinary-case categorical approach of § 924(c)(3)(B) is already broader than the\n\nelements-based approach of § 924(c)(3)(A), and both clauses refer to the same usage of\n\nthe phrase “offense that is a felony.” The canon of meaningful variation thus offers the\n\nGovernment no support. And in Price, we recognized that because SORNA made\n\n“explicit reference to the ‘conduct’ underlying a prior offense, as well as the ‘nature’ of\n\nthat conduct,” it “refer[red] to how an offense was committed — not a generic offense.”\n\nId. at 709 (quoting Nijhawan, 557 U.S. at 37–39). Here, Congress wrote § 924(c)(3)(B)\n\n(unlike SORNA) to refer not to “conduct . . . by its nature” but “an offense that is a\n\nfelony . . . by its nature.” 18 U.S.C. § 924(c)(3)(B). Price supports adherence to the\n\n\n\n 30\n\nordinary-case categorical approach, rather than adoption of the Government’s new\n\nconstruction.\n\n To summarize, the text, structure, and context of § 924(c)(3)(B) clearly mandate\n\nuse of the ordinary-case categorical approach, as do all relevant precedents. Given the\n\nGovernment’s concession that use of this mode of analysis renders the statute\n\nunconstitutionally vague, this dooms the Government’s defense of the statute.\n\n\n\n V.\n\n As the Supreme Court has repeatedly instructed, when statutory language is clear,\n\n“judicial inquiry is complete.” Conn. Nat’l Bank v. Germain, 503 U.S. 249, 254 (1992)\n\n(internal quotation marks omitted). Refusing to abide by this instruction, the Government\n\nheavily relies on considerations unrelated to the unambiguous text to support its new\n\nconduct-specific interpretation of § 924(c)(3)(B). We doubt such external considerations\n\nare relevant. But to the extent that they are, they confirm our decision to adhere to the\n\nordinary-case categorical approach rather than adopting the Government’s new conduct-\n\nspecific reinterpretation.\n\n A.\n\n We begin with practical considerations. The Government contends that\n\nnotwithstanding the statutory text, we should apply a conduct-specific approach to\n\n§ 924(c)(3)(B) because it, unlike the ACCA residual clause or some applications of\n\n§ 16(b), always involves charges prosecuted contemporaneously with any underlying\n\ncrimes of violence. According to the Government, this means “the categorical approach\n\n 31\n\nserves no purpose” in the context of § 924(c)(3)(B). Gov. Supp. Br. at 20. Even setting\n\naside the plain text of the statute, the argument fails for two fundamental reasons.\n\n First, § 924(c)(3)(B)’s failure to require a court to assess past conduct hardly\n\ncompels rejection of the categorical approach. Rather, the categorical approach applies to\n\na number of statutes that require no assessment of past conduct. Most notably, the\n\nGovernment itself concedes that Congress has “require[d] a categorical approach” in\n\ndefining a “crime of violence” under the force clause, § 924(c)(3)(A), the only other\n\nsubsection of § 924(c)(3). Gov. Supp. Br. at 4. And the force clause, like the\n\nneighboring residual clause challenged here, applies only to contemporaneous offenses,\n\nnot prior convictions.\n\n Congress, through § 16, has also applied the categorical approach to many other\n\nstatutes that similarly involve contemporaneous prosecutions. See, e.g., 18 U.S.C.\n\n§ 1952(a)(2) (criminalizing travel or use of mail with intent to commit any “crime of\n\nviolence”); 18 U.S.C. § 842(p)(2)(A) (prohibiting teaching, demonstration, or\n\ndissemination of information intended for use in committing a “crime of violence”); 18\n\nU.S.C. § 3663A(c)(1)(A)(i) (mandating restitution to victims of certain “crime[s] of\n\nviolence,” citing § 16); 18 U.S.C. § 5032 (permitting federal trials of juveniles in certain\n\ncases where “the offense charged is a crime of violence that is a felony”). 11\n\n\n 11\n The Government also suggests that “Sixth Amendment concerns . . . led to the\ncategorical approach” in ACCA and § 16(b) because conduct-specific interpretations of\nthose statutes would require judicial fact-finding at sentencing, an issue that\n§ 924(c)(3)(B) does not present. Gov. Supp. Br. at 20. In fact, non-sentencing\napplications of § 16(b) — including its incorporation into the immigration statute\n(Continued)\n 32\n\n The second reason the Government’s practical argument fails is that, contrary to\n\nits suggestion otherwise, use of the categorical approach in § 924(c) does serve important\n\npurposes. Congress acted with good reasons in mandating a categorical approach here,\n\neven if the real-world benefits differ from those that arise in the context of prior\n\nconvictions. Specifically, § 924(c)’s categorical “crime of violence” analysis serves the\n\npurpose of limiting the statute’s penalties to specific classes of federal crimes where the\n\nuse of a firearm is especially dangerous. See Rosemond, 572 U.S. at 75 (“§ 924(c) . . .\n\npunishes the temporal and relational conjunction of two separate acts, on the ground that\n\ntogether they pose an extreme risk of harm.”); cf. Solem v. Helm, 463 U.S. 277, 292\n\n(1983) (stating relevance of “gravity of the offense” to proportionality of sentence).\n\n Congress amended § 924(c) over time to accomplish this very purpose. Before\n\n1984, § 924(c) criminalized the use or unlawful carrying of a firearm in conjunction with\n\n“any [federal] felony.” 18 U.S.C. § 924(c) (1982). In 1984, Congress narrowed the\n\nstatute to “crime[s] of violence,” defined in relevant part as they are today.\n\nComprehensive Crime Control Act, § 1005(a), 98 Stat. at 2138–39. Two years later,\n\nCongress limited these “crimes of violence” to felonies while adding “drug trafficking\n\ncrimes” to the statute’s scope. Firearm Owners’ Protection Act, § 104, 100 Stat. at 456–\n\n\n\n\nreviewed in both Leocal and Dimaya — similarly present no Sixth Amendment concerns.\nMoreover, even more fundamental constitutional values militate against a conduct-\nspecific approach here. For where Congress has spoken so plainly, judicially revising its\nwork would threaten the basic structural principle of separation of powers. See, e.g.,\nLewis v. City of Chicago, 560 U.S. 205, 215 (2010) (“It is not for us to rewrite the statute\n. . . to achieve what we think Congress really intended.”).\n\n 33\n\n59. Thus, Congress has amended § 924(c) to make it crystal clear that not every federal\n\nfelony involving use of a gun constitutes a “crime of violence.” Rather, the modern\n\nstatute requires the prosecution to make two distinct showings: first, that the defendant\n\nutilized a firearm, and second, that the defendant did so in conjunction with not just any\n\nfelony, but specifically a crime of violence or drug trafficking crime. Smith, 508 U.S. at\n\n227–28.\n\n The Government’s interpretation of § 924(c)(3)(B) would eliminate Congress’s\n\nintentional choice to narrow the application of § 924(c) from “any felon[ies]” to only\n\n“crime[s] of violence” and “drug trafficking crime[s].” As the Government\n\nacknowledges, its reading of the statute would require juries to consider at trial whether\n\nan offender’s specific conduct involved a substantial risk of physical force. But the use,\n\ncarrying, or possession of a firearm, standing alone, will always suffice to generate such a\n\nrisk in a conduct-specific analysis, regardless of the nature of the underlying offense. If\n\nwe were to adopt a conduct-specific approach, we would in effect judicially repeal the\n\n1984 and 1986 congressional amendments to § 924(c).\n\n Attempting to address this problem, the Government claims that jurors could avoid\n\ncollapsing the firearm and crime of violence elements if they were instructed not to find a\n\ncrime of violence based solely on the presence of a firearm. See Ovalles, 905 F.3d at\n\n1250 n.8 (adopting Government’s proposed instruction). But this solution offers no\n\naffirmative principle to guide jury decision-making. How, exactly, are jurors to keep\n\nthese two showings apart? Should they cross out facts involving the firearm? Imagine\n\nthe firearm wasn’t there? Pretend it was inoperable? Instead of condemning jurors to\n\n 34\n\nsuch an ill-defined inquiry, categorical analysis limits § 924(c)’s additional sanctions to\n\nthe discrete and particularly serious classes of felonies selected by Congress — drug\n\ntrafficking crimes and crimes of violence. 12\n\n In sum, even if practical considerations could influence our construction of the\n\nclear text of § 924(c)(3)(B), they do not offer the Government any refuge.\n\n B.\n\n Having opened the door to external considerations, it is noteworthy that the\n\nGovernment does not ask us to examine the legislative history of § 924(c). Perhaps that\n\nis because the legislative history suggests that Congress intended a categorical approach.\n\nRecall that before 1984, § 924(c) penalized the use of a firearm in conjunction with any\n\nfederal felony. A 1979 Senate bill unsuccessfully proposed amending § 924(c) to narrow\n\nits application to crimes of violence, largely as defined today. Criminal Code Reform\n\nAct of 1979, S. 1722, 96th Cong. § 1823 (1979). The Senate Judiciary Committee stated\n\nit was “doubtful” that “felonies involving the possession of narcotics with intent to\n\ndistribute . . . would be considered by their nature to involve a substantial risk of the use\n\nof physical force against another.” S. Rep. No. 96–553, at 849 n.43 (1980). If\n\n§ 924(c)(3)(B) required a conduct-specific analysis, this statement would make no sense,\n\n\n\n 12\n Judge Wilkinson contends that we “derogat[e] the fact-finding function” of trial\ncourts in a purported “arrogation of authority.” Far from it. We honor the difficult work\nof our colleagues on the trial courts by eliminating the need to waste time and energy\ninterpreting an unconstitutional statute. Our holding rests not on a lack of respect for the\nexcellent hard work of district judges, but on the inability of this court to rewrite an\nunambiguous congressional directive.\n\n 35\n\nbecause using a firearm during and in relation to a narcotics felony would almost\n\ncertainly generate a substantial risk of force.\n\n Congress did not enact this specific bill. But it did subsequently limit § 924(c) to\n\ncrimes of violence in 1984, and it defined the term “crime of violence” in § 16 at the\n\nsame time. Comprehensive Crime Control Act, §§ 1001, 1005(a), 98 Stat. at 2136, 2138–\n\n39. The Senate Judiciary Committee explained that it intended the revised statute to\n\ninclude “all persons who commit Federal crimes of violence, including those crimes set\n\nforth in statutes which already provide for enhanced sentences for their commission with\n\na dangerous weapon.” S. Rep. No. 98–225, at 313 (1983) (emphasis added). The\n\nCommittee additionally noted that the “crime of violence” limitation “expand[ed] the\n\nscope of predicate offenses . . . by including some violent misdemeanors, but restrict[ed]\n\nit by excluding non-violent felonies.” Id. at 313 n.9 (emphasis added). Though not\n\ndispositive, the Committee’s language again supports a categorical interpretation.\n\n But, like practical considerations, quotes from committee reports cannot and do\n\nnot control our reading of § 924(c)(3)(B). We note, however, that the Government has\n\nproduced nothing from the legislative record to support its conduct-specific\n\ninterpretation. And if Congress truly intended the materially identical text in § 16(b) and\n\n§ 924(c)(3)(B) to embody such divergent approaches, we would expect to find some\n\nexplanation of that divergence. Instead, the legislative history of § 924(c)(3)(B) offers\n\nthe Government no assistance.\n\n\n\n\n 36\n\n C.\n\n The bedrock doctrine of stare decisis further weakens the Government’s position.\n\nAdherence to precedent is the preferred course for courts “because it promotes the\n\nevenhanded, predictable, and consistent development of legal principles, fosters reliance\n\non judicial decisions, and contributes to the actual and perceived integrity of the judicial\n\nprocess.” Payne v. Tennessee, 501 U.S. 808, 827 (1991).\n\n Of course, stare decisis “is not an inexorable command.” Id. at 828. But\n\nprecedent exerts a particularly “powerful” pull in the context of “settled statutory\n\nmeaning” because “Congress remains free to alter what [the courts] have done.”\n\nShepard, 544 U.S. at 23 (internal quotation marks omitted).\n\n Here, the considered circuit consensus, pre-Dimaya, that § 924(c)(3)(B) requires\n\nan ordinary-case categorical approach strongly favors adherence to such an\n\ninterpretation. 13 “In this case, time has enhanced even the usual precedential force,”\n\n\n 13\n See, e.g., United States v. Taylor, 814 F.3d 340, 377 (6th Cir. 2016) (“Section\n924(c)(3)(B) . . . does not allow a court to consider risk-related conduct beyond that\nwhich is an element of the predicate crime,” because “[t]he phrase ‘by its nature’\nindicates that a court’s analysis . . . is confined to the offense itself.”); United States v.\nFuertes, 805 F.3d 485, 498–99 (4th Cir. 2015) (applying categorical approach under\n§ 924(c)(3)(B)); United States v. McGuire, 706 F.3d 1333, 1336–37 (11th Cir. 2013)\n(“We employ this categorical approach because of the statute’s terms: It asks whether\n[the defendant] committed ‘an offense’ that . . . ‘by its nature, involves a substantial risk\nthat physical force against the person or property of another may be used.’”), overruled in\nOvalles, 905 F.3d at 1253; United States v. Acosta, 470 F.3d 132, 134–37 (2d Cir. 2006)\n(applying categorical approach under § 924(c)(3)(B)), overruled in Barrett, 903 F.3d at\n178; United States v. Munro, 394 F.3d 865, 870–71 (10th Cir. 2005) (explaining that\n§ 924(c)(3)(B) determination is a “legal conclusion” and applying categorical analysis);\nUnited States v. Jennings, 195 F.3d 795, 797–98 (5th Cir. 1999) (stating that use of “by\nits nature” in § 924(c)(3)(B) “requires courts to determine whether an offense constitutes\n(Continued)\n 37\n\nShepard, 544 U.S. at 23, because the federal courts of appeals have interpreted\n\n§ 924(c)(3)(B) to preclude conduct-specific analysis for decades. And although Congress\n\namended § 924(c) repeatedly as this consensus built, it never materially changed the\n\ndefinition of “crime of violence” after 1986. See, e.g., Pub. L. No. 105–386, § 1, 112\n\nStat. 3469, 3469 (1998) (adding “possess[ing] a firearm” “in furtherance of” specified\n\ncrimes to § 924(c)); Pub. L. No. 109–92, § 6, 119 Stat. 2095, 2102 (2005) (creating\n\n§ 924(c)(5) to impose additional penalties for armor-piercing ammunition).\n\n Circuit case law (even if unanimous, as here) carries less weight than Supreme\n\nCourt jurisprudence, and we are hesitant to over-analyze congressional inaction. But we\n\nwould be remiss to discount the fact that between at least 1994 and April 2018, every\n\n§ 924(c) conviction of which we are aware relied on precedents treating crime of violence\n\ndeterminations under § 924(c)(3)(B) (not to mention those under § 16(b)) 14 as questions\n\n\n\n\na crime of violence without examining the underlying facts surrounding the conviction”\n(internal quotation marks omitted)); United States v. Kennedy, 133 F.3d 53, 56–57 (D.C\nCir. 1998) (under § 924(c)(3)(B), “the question is whether the crime with which\n[appellant] was charged constituted a . . . crime of violence” under a “categorical\napproach” (internal quotation marks omitted)); United States v. Amparo, 68 F.3d 1222,\n1225–26 (9th Cir. 1995) (“[A]pplication of a categorical approach to section 924(c)(3)(B)\nis required by our cases.”); United States v. Moore, 38 F.3d 977, 979 (8th Cir. 1994)\n(emphasizing reference to “by its nature” in § 924(c)(3)(B) and holding that “[t]o\ndetermine the nature of a crime requires an examination of the elements which compose\nit, . . . not . . . an exploration of the underlying facts”), abrogation on other grounds\nrecognized, United States v. Torres-Villalobos, 487 F.3d 607, 616 (8th Cir. 2007).\n 14\n See, e.g., Jobson v. Ashcroft, 326 F.3d 367, 372 (2d Cir. 2003) (deeming the\ncategorical approach “not only consistent with precedent and sound policy,” but “also\nnecessary in view of the language of” § 16(b) (internal quotation marks omitted));\nAragon, 983 F.2d at 1313 (“[T]he plain language of § 16(b) mandates that the court\n(Continued)\n 38\n\nof law requiring categorical analysis. Stability, consistency, and coherence therefore\n\ncounsel against the Government’s rejection of this approach.\n\n D.\n\n Finally, a trio of remaining considerations further confirm our adherence to the\n\nordinary-case categorical approach or otherwise offer no support to the Government.\n\n Although we have chosen not to treat the Government’s withdrawal of its conduct-\n\nspecific interpretation as abandonment, it remains notable that the United States\n\nembraced an ordinary-case categorical reading of this language for years, and even\n\ndisclaimed a conduct-specific reading after Johnson. In Dimaya, for example, the\n\nGovernment “accept[ed]” that materially identical text in § 16(b), as incorporated into the\n\nImmigration and Nationality Act, “demand[ed] a categorical approach.” Dimaya, 138 S.\n\nCt. at 1216. It did so even though a conduct-specific inquiry in that case, which involved\n\na deportation determination, raised none of the Sixth Amendment concerns implicated in\n\nthe context of criminal sentencing. The Government was right to take this position: a\n\nmajority of Justices in both Johnson and Dimaya accepted this reading and declined to\n\nreinterpret the ACCA residual clause and § 16(b) to employ a conduct-specific approach.\n\nDimaya, 138 S. Ct. at 1216–18 (plurality opinion); id. at 1235 (Roberts, C.J., dissenting)\n\n(citing Leocal, 543 U.S. at 10–11); Johnson, 135 S. Ct. at 2561–62. Regardless of the\n\n\n\n\nembark upon a categorical approach to determine whether a particular crime, ‘by its\nnature,’ qualifies as a ‘crime of violence.’”).\n\n\n 39\n\nGovernment’s rationale, its most recent change of position can only be read as a late-\n\nbreaking effort to resuscitate a twice-rejected argument.\n\n Moreover, if the Government were correct and the text at issue here were truly so\n\nambiguous as to lend itself to two very different forms of analysis — an ordinary-case\n\ncategorical approach in § 16(b) and a conduct-specific approach in § 924(c)(3)(B) — the\n\nrule of lenity might nonetheless yield the same result that we reach now. For in the case\n\nat hand, this doctrine would tilt in favor of Simms. See Hayes, 555 U.S. at 436 (Roberts,\n\nC.J., dissenting) (describing statute that was ambiguous about categorical approach as\n\n“textbook case for application of the rule of lenity”).\n\n Further, we are not persuaded by the Government’s contention that “the strong\n\nsocietal interest in finality,” particularly as it pertains to guilty pleas, favors saving\n\n§ 924(c)(3)(B) rather than striking it down. Lee v. United States, 137 S. Ct. 1958, 1967\n\n(2017). Under the unusual circumstances presented here, finality cuts both ways. The\n\nparties agree that the longstanding interpretation of § 924(c)(3)(B) is unconstitutional.\n\nAccordingly, past convictions employing the ordinary-case categorical approach will be\n\ncalled into question regardless of whether we invalidate the statute or adopt a new\n\nconduct-specific reading that all rejected before Dimaya. If concerns about opening the\n\nfloodgates are relevant to our interpretation of § 924(c)(3)(B) — and we doubt that they\n\nare — they do not favor either reading.\n\n\n\n\n 40\n\n VI.\n\n Perhaps recognizing that its textual analysis of § 924(c)(3)(B) is untenable and its\n\nreliance on external considerations unconvincing, the Government urges us to embrace its\n\nnew reading of the statute as a matter of constitutional avoidance. We will not “lightly\n\nascribe . . . an unconstitutional intent” to Congress. Ward v. Dixie Nat’l Life Ins. Co.,\n\n595 F.3d 164, 177 (4th Cir. 2010). But given the clear language of § 924(c)(3)(B), we\n\nlack the power to avoid its constitutional infirmity.\n\n We are “obligated to construe [a] statute to avoid [constitutional] problems.” INS\n\nv. St. Cyr, 533 U.S. 289, 300 (2001). However, we may do this only if such a reading is\n\n“fairly possible,” id. (internal quotation marks omitted), “after the application of ordinary\n\ntextual analysis,” Jennings v. Rodriguez, 138 S. Ct. 830, 842 (2018) (internal quotation\n\nmarks omitted). Where, as here, there is an “absence of more than one plausible\n\nconstruction,” the canon of constitutional avoidance “simply has no application.”\n\nJennings, 138 S. Ct. at 842 (internal quotation marks omitted).\n\n This limitation is an important one. As the Supreme Court recently explained,\n\n“[s]potting a constitutional issue does not give a court the authority to rewrite a statute as\n\nit pleases.” Id. at 843. Rather, constitutional avoidance serves the “basic democratic\n\nfunction of maintaining a set of statutes that reflect, rather than distort, the policy choices\n\nthat elected representatives have made.” Almendarez-Torres v. United States, 523 U.S.\n\n224, 238 (1998). The doctrine is thus “a means of giving effect to congressional intent,\n\nnot of subverting it.” Clark, 543 U.S. at 382. In the words of the Chief Justice,\n\n“rewrit[ing] a law to conform it to constitutional requirements . . . would constitute a\n\n 41\n\nserious invasion of the legislative domain.” United States v. Stevens, 559 U.S. 460, 481\n\n(2010) (alterations and internal quotation marks omitted).\n\n In this regard, the seemingly disparate doctrines of vagueness and constitutional\n\navoidance unite. Both demand respect for the distinct functions that Congress and the\n\njudiciary fulfill in our constitutional republic. Due process requires Congress to speak in\n\ndefinite terms, particularly where the consequences for individual liberties are steep, in\n\npart because Congress alone — not the executive or the judiciary — is equipped to\n\nbalance competing policy priorities and to define the boundaries of criminal law. For\n\nsimilar reasons, although courts must interpret statutes under the presumption that\n\nlegislators do not intend to violate the Constitution, judges cannot revise invalid statutes.\n\nTo the contrary, while the grave remedy of striking down a statute as unconstitutional lies\n\nwithin the judicial province, rewriting it is a task solely for the elected legislature.\n\n These principles compel us to reject the Government’s constitutional avoidance\n\nargument. Given the text and context of § 924(c)(3)(B), accepting the Government’s new\n\ninterpretation would amount to judicially rewriting the statute.\n\n The United States does not merely seek to narrow an ambiguous statute, as the\n\nSupreme Court did in Skilling v. United States, 561 U.S. 358, 404 (2010), and Zadvydas\n\nv. Davis, 533 U.S. 678, 682 (2001) — the latter being “a notably generous application of\n\nthe constitutional-avoidance canon.” Jennings, 138 S. Ct. at 843. Here, the Government\n\nasks us to go “much further,” id., by adopting a conduct-specific reading of\n\n§ 924(c)(3)(B) that directly conflicts with how courts and the United States itself have\n\nthoughtfully interpreted this statute (and materially identical text in § 16(b)) since its\n\n 42\n\nenactment three decades ago. Tellingly, the Government has yet to identify any case in\n\nwhich the Supreme Court has done anything comparable in the name of constitutional\n\navoidance. 15\n\n We cannot usurp the legislative role to edit out the constitutional flaw in\n\n§ 924(c)(3)(B). The plain text, structure, and context of § 924(c)(3) are more than\n\nenough to convince us that its residual clause has no plausible conduct-specific\n\ninterpretation. We therefore refuse to rewrite the statute, just as the Supreme Court\n\nrefused to rewrite § 16(b) and the ACCA residual clause, even in the face of vigorous\n\ndissents urging the employment of constitutional avoidance. See Dimaya, 138 S. Ct. at\n\n1216–18 (plurality opinion); id. at 1232–33 (Gorsuch, J., concurring in part and\n\nconcurring in the judgment); Johnson, 135 S. Ct. at 2561–62.\n\n\n\n VII.\n\n We are mindful of the consequences of holding § 924(c)(3)(B) unconstitutional.\n\nThe provision is part of a widely used criminal statute enacted by Congress, and like\n\n§ 16(b), it has been incorporated into other parts of the federal criminal code. See 18\n\n 15\n Judge Richardson’s puzzling invocation of Justice Kavanaugh’s scholarship\nonly underscores this point. Far from endorsing the unprecedented application of\nconstitutional avoidance that Judge Richardson champions, then-Judge Kavanaugh\nwarned against overreliance on this canon and others triggered by a threshold finding of\nambiguity. Brett Kavanaugh, Fixing Statutory Interpretation, 129 HARV. L. REV. 2118,\n2144 (2016) (book review). Thus, he proposed “jettison[ing]” constitutional avoidance\nand instead allowing judges to first “determine the best reading of the statute” and then,\n“[i]f that reading turn[s] out to be unconstitutional,” “say as much.” Id. at 2148. Of\ncourse, we lack the power to follow this approach and, in any event, a faithful\nemployment of the constitutional avoidance canon compels the result we reach.\n\n 43\n\nU.S.C. §§ 844(o), 1028(b)(3)(B). We do, however, note that our ruling is limited in\n\nimportant respects.\n\n First, § 924(c)(3)(B) appears to be the last federal statute that directs courts to\n\nimpose penalties based on a drifting ordinary-case categorical inquiry and an\n\nindeterminate risk threshold. The Government has not pointed to any other statute that\n\nour decision places in jeopardy, and there is no colorable argument that the elements-\n\nbased categorical approach of § 924(c)(3)(A) suffers from any similar indeterminacy.\n\nSection 924(c)(3)(B) is, in other words, the last Johnson domino to fall. In striking it\n\ndown, we leave intact the balance of the definition of “crime of violence” and the entirety\n\nof the definition of “drug trafficking crime” in § 924(c).\n\n Second, nothing in our holding restricts the broad discretion of district judges to\n\nmake case-by-case sentencing determinations. Here, for example, the district court was\n\nauthorized to sentence Simms to as much as 240 months’ incarceration on his conviction\n\nfor Hobbs Act conspiracy alone — that is, more than three years longer than the total\n\nsentence it actually imposed on both counts. Although judges must consult the advisory\n\nSentencing Guidelines, they may vary from these recommendations in light of the factors\n\nlisted in 18 U.S.C. § 3553(a). See, e.g., Peugh v. United States, 569 U.S. 530, 536\n\n(2013). Foremost among these is “the nature and circumstances of the offense,” which\n\nwill necessarily include whether the offender used a firearm. 18 U.S.C. § 3553(a)(1).\n\n Last, Congress is fully equipped to revise the statute here. As Justice Gorsuch\n\nnoted in Dimaya:\n\n\n\n 44\n\n Vagueness doctrine represents a procedural, not a substantive, demand. It\n does not forbid the legislature from acting toward any end it wishes, but\n only requires it to act with enough clarity that reasonable people can know\n what it is required of them and judges can apply the law consistent with\n their limited office.\n\nDimaya, 138 S. Ct. at 1233 (Gorsuch, J., concurring in part and concurring in the\n\njudgment). These insights apply here. If Congress deems it appropriate to replace\n\n§ 924(c)(3)(B) with a statute that achieves similar aims with sufficiently definite terms,\n\nthe Due Process Clause poses no obstacle.\n\n\n\n VIII.\n\n For the foregoing reasons, the judgment of the district court is\n\n REVERSED AND REMANDED.\n\n\n\n\n 45", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "wrote a dissenting opinion. Judge Niemeyer wrote a dissenting"}, {"author": "WYNN, Circuit Judge, with whom HARRIS, Circuit Judge, joins, concurring", "type": "concurrence", "text": "WYNN, Circuit Judge, with whom HARRIS, Circuit Judge, joins, concurring:\n\n In this case we must decide whether to jettison the “categorical” approach for\n\ndetermining whether an offense is a “crime of violence” for the purpose of 18 U.S.C. §\n\n924(c)(3)(B)—an approach that the executive and judicial branches uniformly have\n\nembraced for several decades, and which the government advanced to this court as\n\nrecently as October 2016 1—and replace it with a “case-specific” approach. The\n\ndissenting opinions argue that, in refusing to abandon the categorical approach, the\n\nmajority opinion—with which I concur in full—is at odds with the doctrine of\n\nconstitutional avoidance. E.g., Post at 85 (Richardson, J.). In particular, my dissenting\n\ncolleagues maintain that constitutional avoidance compels adoption of the case-specific\n\napproach in order to “reflect, rather than distort, the policy choices that the elected\n\nrepresentatives have made.” Post at 84 (Niemeyer, J.) (quoting Almendarez-Torres v.\n\nUnited States, 523 U.S. 224, 238 (1998)).\n\n Yet it is my dissenting colleagues’ misguided application of the doctrine of\n\nconstitutional avoidance—not the majority opinion’s adherence to the long-standing\n\nunderstanding of Section 924(c)(3)(B)—that has the potential to “distort” the Framers’\n\ncarefully crafted allocation of powers for defining crimes and punishments. Relying on\n\n\n 1\n Gov. 28(j) letter at 2, ECF No. 44 (Oct. 19, 2016); see also, e.g., United States v.\nPrickett, 839 F.3d 697 (8th Cir. 2016); United States v. Taylor, 814 F.3d 340, 378, 397\nn.19 (6th Cir. 2016); United States v. Fuertes, 805 F.3d 485, 498 (4th Cir. 2015); United\nStates v. McGuire, 706 F.3d 1333, 1336-37 (11th Cir. 2013); United States v. Serafin,\n562 F.3d 1105, 1107 (10th Cir. 2009); United States v. Jennings, 195 F.3d 795, 797-98\n(5th Cir. 1999); United States v. Kennedy, 133 F.3d 53, 56-57 (D.C. Cir. 1998); United\nStates v. Amparo, 68 F.3d 1222, 1224 (9th Cir. 1995).\n\n 46\n\nconstitutional avoidance as a basis for replacing the categorical approach with a case-\n\nspecific approach, as my dissenting colleagues suggest, would broaden the universe of\n\ndefendants subject to Section 924(c)(3)(B). But, to date, the Supreme Court has applied\n\nthe doctrine only to narrow a criminal statute’s breadth and thereby forestall\n\nconstitutional concerns. By relying on constitutional avoidance to expand a criminal\n\nstatute’s reach, my dissenting colleagues embrace an unprecedented application of the\n\ndoctrine of constitutional avoidance that empowers the judiciary to usurp Congress’s\n\nexclusive authority to establish crimes and punishments. I write separately to explain\n\nwhy I do not believe the Constitution permits judicial encroachment into such a well-\n\ndefined legislative province.\n\n I.\n\n Section 924(c)(1)(A) provides that a person who “uses or carries a firearm”\n\n“during and in relation to any crime of violence” or who “possesses a firearm” “in\n\nfurtherance of any such crime” may be convicted of both the underlying crime and the\n\nadditional crime of using a firearm in connection with a “crime of violence.” Section\n\n924(c)(3)(B) defines “crime of violence” as a felony offense “that by its nature, involves\n\na substantial risk that physical force against the person or property of another may be\n\nused in the course of committing the offense.” Accordingly, to convict a defendant of\n\nviolating Section 924(c), a jury must find both that the defendant possessed or used a\n\nfirearm and that the defendant did so in connection with a “crime of violence.”\n\n As the majority explains, prior to the Supreme Court’s decision in Sessions v.\n\nDimaya, 138 S. Ct. 1204 (2018), federal courts—at the government’s urging and in\n\n 47\n\naccordance with the Supreme Court’s construction of virtually identical language in other\n\nstatutes, see, e.g., Taylor v. United States, 495 U.S. 595, 601 (1990)—universally held\n\nthat courts must apply the ordinary-case categorical approach in determining whether a\n\npredicate offense constitutes a crime of violence for purposes of Section 924(c)(3)(B).\n\nUnder the ordinary-case categorical approach, a court must determine whether the\n\nhypothetical “ordinary case” of an offense—i.e., not under the particular facts giving rise\n\nto the defendant’s prosecution, Dimaya, 138 S. Ct. at 1211—“involves a substantial risk\n\nthat physical force against the person or property of another may be used in the course of\n\ncommitting the offense.” By contrast, under the case-specific, or “circumstance-\n\nspecific,” approach now advanced by the government, and embraced by my colleagues in\n\ndissent, a jury would decide whether the specific conduct giving rise to the defendant’s\n\nprosecution involves a “substantial risk that physical force against the person or property\n\nof another may be used.” See United States v. Price, 777 F.3d 700, 704 (4th Cir. 2015).\n\n If this Court were to replace the ordinary-case categorical approach with the case-\n\nspecific approach, then offenses that courts have found do not constitute crimes of\n\nviolence under the ordinary-case categorical approach will amount to crimes of violence\n\nunder the case-specific approach. The Ninth Circuit has held, for example, that\n\ninvoluntary manslaughter, 18 U.S.C. § 1112, is not categorically a crime of violence\n\nbecause it “requires a mental state of only gross negligence.” United States v. Benally,\n\n843 F.3d 350, 354 (9th Cir. 2016). Yet it takes little effort to imagine specific cases of\n\ninvoluntary manslaughter—particularly cases involving guns, which must be present to\n\nimplicate Section 924(c)(3)(B)—that a jury would find constitute a “crime of violence”\n\n 48\n\nunder the case-specific approach. In Benally, for example, the defendant shot and killed\n\nthe victim with a rifle. Id. at 352. At trial, the government presented that the “shooting\n\nwas accidental and part of a drunken game.” Id. at 352. Accordingly, the Benally\n\ndefendant, who was not amenable to prosecution under Section 924(c)(3)(B) under the\n\nordinary-case categorical approach, would face a high probability of conviction under the\n\ncase-specific approach because a jury would likely find that the defendant’s conduct\n\nposed “a substantial risk that physical force against the person . . . of another may be\n\nused,” notwithstanding that the crime requires “a mental state of only gross negligence.”\n\nId. at 354.\n\n Benally demonstrates that if this Court abandons use of the ordinary-case\n\ncategorical approach to determine whether an offense constitutes a “crime of violence”\n\nfor purposes of Section 924(c)(3)(B) and adopts the case-specific approach the\n\ngovernment belatedly advances—and our dissenting colleagues embrace—then the\n\nuniverse of defendants subject to prosecution under Section 924(c)(3)(B) will be\n\nsubstantially greater. Put differently, the adoption of the case-specific approach would\n\nexpand the reach of Section 924(c)(3)(B) to a new class of offenders—namely those\n\noffenders who commit offenses that do not “ordinar[ily]” pose a “substantial risk” of\n\napplication of physical force against another, but which pose such a risk under the\n\n\n\n\n 49\n\nspecific factual circumstances of the offender’s case (perhaps because the offender was\n\ncarrying a gun when he committed the offense). 2\n\n II.\n\n Because a shift to the case-specific approach will broaden the class of offenders\n\nsubject to prosecution under Section 924(c)(3)(B), I believe constitutional avoidance is an\n\nimproper basis for a court to choose the case-specific approach over the ordinary-case\n\ncategorical approach. As the majority opinion correctly explains, the canon of\n\n\n\n 2\n One of my dissenting colleagues posits in a separate opinion that the ordinary-\ncase approach “is not inherently ‘narrower’ than the case-specific approach” because “a\njudicially-imagined ‘ordinary case’ can ensnare a defendant whose actual conduct created\nno risk of violence, a result barred by the case-specific approach.” Post, at 100–01 n.6\n(Richardson, J.). Whatever the merits of that contention in other contexts, it makes little\nsense in the context of Section 924(c)(1)(A).\n\n Put simply, my dissenting colleague’s argument rests on the premise that a jury\nwill find that a defendant did not, as a matter of fact, engage in conduct that posed a\nsubstantial risk of violence, even though the defendant necessarily (1) committed a crime\nthat “ordinar[il]y” creates a substantial risk of violence and (2) committed that crime\nwhile carrying a firearm—“an article that is typically and characteristically dangerous,”\nMcLaughlin v. United States, 476 U.S. 16, 17 (1986), and therefore “inherently violent,”\nPelissero v. Thompson, 470 F.3d 442, 447 (4th Cir. 1999). The prospect that a jury\nwould render such a verdict is, indeed, vanishingly small. Cf. Smith v. United States, 508\nU.S. 223, 240 (1993) (“We therefore see no reason why Congress would have intended\ncourts and juries applying § 924(c)(1) to draw a fine metaphysical distinction between a\ngun’s role in a drug offense as a weapon and its role as an item of barter; it creates a\ngrave possibility of violence and death in either capacity.”).\n\n Rather, it is far more likely that a jury would find that an offense that is not\n“ordinar[il]y” a crime of violence amounts to a crime of violence when, in a particular\ncase, the defendant committed the offense while carrying a firearm. In other words, the\nnumber of additional defendants convicted of violating Section 924(c)(1)(A) under the\ncase-specific approach would likely substantially exceed the number of defendants—if\nany—who would be relieved of liability under that approach.\n\n\n 50\n\nconstitutional avoidance is a “tool for choosing between competing plausible\n\ninterpretations of a statutory text, resting on the reasonable presumption that Congress\n\ndid not intend the alternative which raises serious constitutional doubts.” Clark v.\n\nMartinez, 543 U.S. 371, 381 (2005); ante at 41–43.\n\n In the context of constitutional challenges to criminal statutes, the Supreme Court\n\nand lower courts have applied the doctrine of constitutional avoidance to adopt a\n\n“narrow[ing] constru[ction]” that avoids constitutional concerns that would arise were\n\nthe statute construed more broadly. Skilling v. United States, 561 U.S. 358, 407 n.40, 409\n\nn.43 (2010) (emphasis added) (quoting United States v. Lanier, 520 U.S. 259, 257–68 n.6\n\n(1997)). For example, in Skilling, the Supreme Court considered a vagueness challenge\n\nto the honest-services wire fraud statute. Id. at 402–03. Recognizing that the defendant’s\n\n“vagueness challenge ha[d] force,” the Court applied the doctrine of constitutional\n\navoidance to “par[e] down” the statute to “only [its] bribe-and-kickback core.” Id. at 409\n\n& n.43. In reaching this conclusion, the Supreme Court emphasized that, in view of the\n\nstatute’s legislative history, as well as consistent judicial interpretation, there was “no\n\ndoubt that Congress intended § 1346 to reach at least bribes and kickbacks.” Id. at 405,\n\n408–09 (emphasis in original). Put differently, the Supreme Court applied the doctrine of\n\nconstitutional avoidance to narrow the statute’s scope to a range of conduct that Congress\n\nunambiguously intended to render unlawful.\n\n Skilling recognized that “cases ‘paring down’ federal statutes to avoid\n\nconstitutional shoals are legion.” Id. at 406 n.40, 409 n.43 (emphasis added) (collecting\n\ncases). By contrast, the government has not identified a single case—nor have I—in\n\n 51\n\nwhich the Supreme Court has applied the doctrine of constitutional avoidance to expand\n\nthe reach of a criminal statute, as my colleagues in dissent suggest we do in construing\n\nSection 924(c)(3)(B).\n\n That no court appears to have applied constitutional avoidance to construe a\n\nstatute to “proscribe a wider range of offensive conduct,” id. at 408 (emphasis added), is\n\nunsurprising. The Constitution vests the “power of punishment . . . in the legislative, not\n\nin the judicial department.” Dowling v. United States, 473 U.S. 207, 214 (1985) (quoting\n\nUnited States v. Wiltberger, 5 Wheat. 76, 95 (1820)). Indeed, it “is the legislature, not\n\nthe Court, which is to define a crime, and ordain its punishment.” Id.\n\n The Supreme Court has held that applying the doctrine of constitutional avoidance\n\nto “par[e] down” the scope of a constitutionally suspect criminal statute does not amount\n\nto usurpation of Congress’s singular authority to define crimes and punishments. See\n\nSkilling, 561 U.S. at 409 n.43 (explaining that the Court does not usurp Congress’s\n\nauthority to define crimes and punishment when it “par[es] down federal statutes to avoid\n\nconstitutional shoals” because, in such circumstances, “the Court does not legislate, but\n\ninstead respects the legislature, by preserving a statute through a limiting\n\ninterpretation”). But see id. at 422 (Scalia, J., dissenting) (“I know of no precedent for\n\nsuch ‘paring down,’ and it seems to me clearly beyond judicial power.”). But the\n\nSupreme Court has sanctioned the use of constitutional avoidance to narrow a potentially\n\nunconstitutional criminal statute’s scope only when there is “no doubt that Congress\n\nintended [the statute] to reach” the conduct proscribed by the limiting construction. Id. at\n\n408 (majority op.) (emphasis added). In Skilling, for example, the Court’s limiting\n\n 52\n\nconstruction preserved the honest-services fraud statute’s “solid core.” Id. Put\n\ndifferently, a court may apply constitutional avoidance to narrow the scope of a\n\nconstitutionally suspect statute without infringing on Congress’s exclusive authority to\n\ndefine crimes and punishments because the conduct proscribed by the limiting\n\nconstruction necessarily falls within the scope of the conduct Congress intended to\n\nproscribe.\n\n The same cannot be said when a court applies the doctrine of constitutional\n\navoidance to expand a criminal statute’s reach. That is because the doctrine of\n\nconstitutional avoidance presupposes that there is at least some doubt as to the scope of\n\nconduct a statute proscribes—to apply the doctrine there must be at least two “competing\n\nplausible interpretations of a statutory text.” See Clark, 543 U.S. at 381. Accordingly,\n\napplying the doctrine of constitutional avoidance to adopt the more expansive of\n\n“competing plausible interpretations” of a criminal statute’s reach—as my colleagues in\n\ndissent would have us do here—entails the judiciary holding unlawful conduct for which\n\nthere necessarily is some doubt as to whether Congress intended to make the conduct a\n\ncrime. The Supreme Court, however, has long recognized that the judiciary lacks “the\n\npower to define new federal crimes,” Skilling, 561 U.S.at 415 (Scalia, J., dissenting)\n\n(citing United States v. Hudson, 7 Cranch 32, 34 (1812))—precisely what would occur if\n\na judicial construction of a criminal statute encompasses conduct Congress did not intend\n\nto make unlawful.\n\n That certainly is the case here. Given (1) the Supreme Court’s long-settled\n\nconstruction of several key terms in Section 924(c)(3)(B) as a compelling application of\n\n 53\n\nthe ordinary-case categorical approach, (2) the government’s decades-long position that\n\nthe language of Section 924(c)(3)(B) demands application of the ordinary-case\n\ncategorical approach, and (3) lower federal courts’ unanimous determination, prior to\n\nDimaya, that the ordinary-case categorical approach applies, there is, at the very least, a\n\nstrong possibility—indeed, likelihood, as the majority opinion persuasively explains—\n\nthat Congress did not intend for the case-specific approach to apply. Accordingly, my\n\ndissenting colleagues’ novel application of the doctrine of constitutional avoidance to\n\nexpand Section 924(c)(3)(B)’s reach by requiring application of the case-specific\n\napproach would “arrogat[e],” post at 62 (Wilkinson, J.), to the judiciary the authority “to\n\ndefine [a] new federal crime,” Skilling, 561 U.S at 415 (Scalia, J., dissenting).\n\n Not only does applying the doctrine of constitutional avoidance to expand the\n\nreach of a criminal statute conflict with Congress’s exclusive authority to define crimes\n\nand punishments, but it also stands in tension with the rule of lenity, which requires that\n\n“any ambiguity over the . . . scope [of a criminal statute] be resolved in [a criminal\n\ndefendant’s] favor.” Crandon v. United States, 494 U.S. 152, 168 (1990). When a court\n\nresorts to the doctrine of constitutional avoidance to construe a statute—as my dissenting\n\ncolleagues would have us do here—it necessarily does so because there is some\n\n“ambiguity” as to the statute’s reach. Applying the doctrine of constitutional avoidance\n\nto narrow a criminal statute’s scope advances the interests served by the rule of lenity\n\nbecause it resolves the statutory ambiguity in the criminal defendant’s favor.\n\n By contrast, applying constitutional avoidance to widen a statute’s reach fails to\n\nkeep faith with the rule of lenity because it resolves a statutory ambiguity in a manner\n\n 54\n\ncontrary to the interests of criminal defendants. Indeed, were the judiciary to rely on\n\nconstitutional avoidance to interpret a statute’s breadth in a manner that extends beyond\n\nwhat the text “clearly warrants”—as necessarily occurs when a court adopts a broad\n\nreading of an ambiguous statute—it would violate the due process principle of “fair\n\nwarning” undergirding the rule of lenity. United States v. Hayes, 555 U.S. 415, 436–37\n\n(2009) (Roberts, C.J., dissenting) (quoting Crandon, 494 U.S. at 160).\n\n III.\n\n My good colleague in dissent asserts that it is the majority’s refusal to abandon the\n\nordinary-case categorical approach—rather than the dissenting opinions’ unprecedented\n\napplication of constitutional avoidance to usurp Congress’s exclusive authority to define\n\ncrimes and punishments—that amounts to an “arrogation of authority . . . all too\n\nprevalent in appellate ranks throughout the country.” Post at 62 (Wilkinson, J.). As my\n\ncolleague sees it, this Court’s decision to continue to construe Section 924(c)(3)(B) as\n\nrequiring use of the ordinary-case categorical approach reflects a “troubling trend” of\n\n“appellate micro-management”—that by applying the ordinary-case categorical approach\n\nthis Court is “displac[ing]” the historical roles of “trial courts, juries, and indeed\n\nCongress.” Post at 60, 63-64, 67 (Wilkinson, J.).\n\n Whatever the merits of my dissenting colleague’s concern about the “appellate\n\nregency” subverting the traditional role of trial judges, juries, and Congress in criminal\n\nadjudication, post at 65 (Wilkinson, J.), such concerns have no place in this case. There\n\nis no question that this Court’s resolution keeps faith with the Supreme Court’s long-\n\nstanding conclusion that when Congress used identical terms in other statutes, it intended\n\n 55\n\nfor the categorical approach to apply, see Taylor, 495 U.S. at 601, and with this Court’s\n\nconclusion that those terms demand application of the categorical approach in present-\n\noffense, as well as past-offense, cases, see Fuertes, 805 F.3d at 498; United States v.\n\nAragon, 983 F.2d 1306, 1312 (4th Cir. 1993). There also can be no question that this\n\nCourt’s resolution of this case adheres to the—until recently unquestioned—decades-long\n\njudicial understanding of Section 924(c)(3)(B). See supra note 1. And there is no\n\nquestion that this Court’s resolution of this case mirrors the construction of Section\n\n924(c)(3)(B) that the government advanced from the statute’s adoption until Dimaya.\n\n Accordingly, this Court’s resolution of this case in no way breaks with the\n\nhistorical understanding of Section 924(c)(3)(B) and the roles of juries and trial courts in\n\napplying that statute. Rather, it is the government’s post-Dimaya about-face as to the\n\nproper construction of Section 924(c)(3)(B), and my dissenting colleagues’ embrace of\n\nthat construction, that turns away from the historical understanding and application of\n\nthat statute. Likewise, my dissenting colleagues’ proposed expansion of the doctrine of\n\nconstitutional avoidance in a manner that empowers the judiciary to “trench upon the\n\nlegislature’s [exclusive] powers” to define crimes and punishments, Salinas v. United\n\nStates, 522 U.S. 52, 60–61 (1997), is the only evidence of a “troubling trend” of\n\n“appellate micro-management” that this case provides.\n\n My colleagues in dissent rejoin that surely Congress intended to punish\n\nindividuals like Defendant—and, possibly, like the defendant in Benally—who\n\ncommitted, under the specific facts of their case, what are undisputedly “violent” crimes,\n\nas that term is used colloquially. Post at 63-64 (Wilkinson, J.); post at 85 (Richardson,\n\n 56\n\nJ.). And they are right. That is why Congress has proscribed conspiracy to commit Hobbs\n\nAct robbery and involuntary manslaughter, and why Congress has imposed substantial\n\ncriminal penalties for individuals who commit those crimes. But that is not the question\n\nwe must address. Rather, we are tasked with deciding whether Congress intended to hold\n\nDefendant criminally liable for the additional offense of using a firearm in commission\n\nof an “offense” that “by its nature, involves a substantial risk that physical force against\n\nthe person or property of another may be used.” § 924(c)(3)(B) (emphases added). And\n\nby expressly choosing to render unlawful only those “offenses” that “by [their] nature”\n\ninvolve application of violent force, Congress sought to limit the universe of defendants\n\nprosecutable under Section 924(c)(3)(B) to those defendants who commit crimes the\n\nordinary manifestation of which “involve[] a substantial risk that physical force against\n\nthe person or property of another may be used.”\n\n As the majority opinion ably explains, the Supreme Court long has held that when\n\nCongress uses that specific language, it intends for courts to apply the ordinary-case\n\ncategorical approach. And in accordance with the Supreme Court’s construction of that\n\nlanguage, the government long has argued—including earlier in this case—that Congress\n\nintended for courts to apply the ordinary-case categorical approach in determining\n\nwhether a defendant is amenable to prosecution under Section 924(c)(3)(B). Put simply,\n\nuntil Dimaya, the judiciary and the government agreed that Congress intended for Section\n\n924(c)(3)(B) to require application of the ordinary-case categorical approach, and\n\ntherefore that Congress did not contemplate prosecuting individuals like Defendant under\n\n\n\n 57\n\nthat provision. Since Congress enacted Section 924(c)(3)(B) in 1986, Congress never has\n\ndisturbed that settled understanding.\n\n Of course, Congress is free to amend Section 924(c)(3)(B) to permit further\n\npunishment of Defendant under that provision. But this Court is not free to expand the\n\nstatute’s reach through an unprecedented application of the doctrine of constitutional\n\navoidance, 3 see Clark, 543 U.S. at 382 (2005) (“[Constitutional avoidance] is thus a\n\nmeans of giving effect to congressional intent, not of subverting it.”), particularly in light\n\nof the Supreme Court’s settled construction of the meaning of Section 924(c)(3)(B)’s key\n\nterms, see Rodriguez de Quijas v. Shearson/Am. Express, Inc., 490 U.S. 477, 484 (1989)\n\n\n\n\n 3\n Another one of my dissenting colleagues claims in his separate opinion that I\n“seek[] to replace the doctrine of constitutional avoidance with a search and destroy\nmission to strike down federal statutes.” Post at 66 (Wilkinson, J.). Not true. My\nanalysis leaves ample room for courts to rely on constitutional avoidance to adopt\nnarrowing constructions of criminal statutes some applications of which pose\nconstitutional concerns—that simply is not how my dissenting colleagues propose to\napply the doctrine here. My dissenting colleague further asserts that my understanding of\nconstitutional avoidance “embrace[s] the odd proposition that upholding a statute is\nsomehow a usurpation of Congress’ authority.” Post at 66. Again, not true. I am not the\nfirst to recognize that—even when a limiting, as opposed to a widening, construction is\nproposed to save a potentially unconstitutional statute—courts do not “have the power, in\norder to uphold an enactment, to rewrite it.” Skilling, 561 U.S. at 423 (Scalia, J.,\ndissenting). That is particularly true given that, in the decades leading up to Dimaya,\nneither the government nor any court believed the case-specific approach applied. Cf. id.\n(explaining that “[i]f it were a ‘fairly possible’ or ‘reasonable’ construction, not ‘contrary\nto the intent of Congress’”—and therefore amenable to application of the doctrine of\nconstitutional avoidance—“one would think that some court would have adopted it”). In\nsuch circumstances, judicial “restraint” demands “resist[ing] the temptation to make all\nthings right with the stroke of [the judicial] pen”—as my colleagues in dissent would\nhave this Court do. Id. at 423–24.\n\n\n 58\n\n(‘‘[T]he Court of Appeals should . . . leav[e] to th[e Supreme] Court the prerogative of\n\noverruling its own decisions.’’).\n\n IV.\n\n In sum, neither my dissenting colleagues nor the government points to a single\n\ncase in which the Supreme Court has sanctioned the use of constitutional avoidance in a\n\nmanner that expands the scope of a criminal statute, as it would if we applied the case-\n\nspecific approach to Section 924(c)(3)(B). And, for decades, courts—at the\n\ngovernment’s express invitation—have applied the ordinary-case categorical approach in\n\naccordance with the settled understanding of that statute’s text. Constitutional avoidance\n\nis “not a license for the judiciary to rewrite language enacted by the legislature.” Salinas,\n\n522 U.S. at 60–61. But that is precisely what would occur if this Court followed my\n\ndissenting colleagues’ suggestion and relied on constitutional avoidance to expand\n\nSection 924(c)(3)(B)’s reach. Accordingly, any justification for the case-specific\n\napproach grounded in constitutional avoidance radically departs from the established\n\nscope and application of the doctrine.\n\n\n\n\n 59", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "WYNN, Circuit Judge, with whom HARRIS, Circuit Judge, joins, concurring"}, {"author": "WILKINSON, Circuit Judge, dissenting", "type": "dissent", "text": "WILKINSON, Circuit Judge, dissenting:\n\n Once upon a time, now seemingly a geologic age ago, the federal judiciary\n\nappeared sold on the inherent advantages that trial courts and trial juries bring to fact-\n\nfinding in our criminal justice system. No longer. My colleagues in the majority ably\n\ndemonstrate that application of the categorical approach to 18 U.S.C. § 924(c)(3)(B)\n\nsaddles that statute with a fatal constitutional infirmity. My colleagues in dissent—whom\n\nI join—ably demonstrate why that infirmity need not exist; the better reading of the\n\nstatute avoids it by applying the case-specific approach in place of the categorical. I write\n\nseparately to further explain how application of the categorical approach here is part of a\n\ntroubling trend: the gratuitous conversion of issues of fact into questions of law; the\n\nusurpation of authority by appellate courts and the resultant atrophy of trial courts’ fact-\n\nfinding function.\n\n ****\n\n Appellate courts have taken the Sentencing Guidelines and the categorical\n\napproach to crimes of violence as an invitation to wade deep into sentencing. This despite\n\nthe faith that Gall v. United States placed in district judges with respect to the sentencing\n\nfunction. 552 U.S. 38 (2007). There is no mistaking Gall’s thrust: district judges are “in a\n\nsuperior position to find facts,” and, because of this, appellate judges must give them\n\n“due deference.” Id. at 51. The district judge has “greater familiarity with[] the individual\n\ncase and the individual defendant before him than the . . . appeals court.” Id. at 51-52.\n\nUnlike the appeals court, the district “judge sees and hears the evidence, makes\n\ncredibility determinations, has full knowledge of the facts and gains insight not conveyed\n\n 60\n\nby the record.” Id. at 51. In short, “district courts have an institutional advantage over\n\nappellate courts” in setting sentences. Id. at 52.\n\n Because of this institutional advantage—that district judges have the eyes and\n\nears that appellate judges lack—Gall commanded appeals courts to apply a “deferential\n\nabuse-of-discretion” standard to critical sentencing determinations. Id. This standard,\n\nwhen combined with the clearly-erroneous standard for findings of fact, should have\n\ninstilled in us a proper respect for the trial courts’ basic judgment calls. Id. at 51. The\n\nGall Court underscored this point when it wrote that “[t]he fact that the appellate court\n\nmight reasonably have concluded that a different sentence was appropriate is insufficient\n\nto justify reversal of the district court.” Id. at 51.\n\n One would think that Gall fixed principal responsibility for sentencing where it\n\nbelonged: with the trial courts. After all, that case simply reflected the basic principle that\n\nsentencing is a fact-bound matter which requires the exercise of wide discretion by trial\n\njudges. Landmark cases such as Gall and Anderson v. City of Bessemer City, 470 U.S.\n\n564 (1985), inhabit that ironic junction where the role of facts becomes the essence of the\n\nrule of law. But Gall’s promise was never fulfilled. By adopting, expanding, and rigidly\n\napplying the categorical approach to the characterization of crimes of violence by a\n\ndefendant, appellate courts have subjected too many discretionary trial-court sentencing\n\ndeterminations to de novo review. This appellate approach has not only led courts to\n\n“reach counterintuitive results, and ones which are not what Congress intended.” United\n\nStates v. Faust, 853 F.3d 39, 61 (1st Cir. 2017) (Lynch J., concurring). It has further\n\n\n\n 61\n\nundermined the authority of district courts as finders of fact, even where the facts are\n\nclearly ascertainable and readily discerned.\n\n My fine colleague, Judge Motz, has written thoughtfully. And my friends in the\n\nmajority are certainly not alone in derogating the fact-finding function, but part of an\n\noverreach all too prevalent in appellate ranks throughout the country. The majority cloaks\n\nits latest arrogation of authority in dulcet reassurances: “[N]othing in our holding restricts\n\nthe broad discretion of district judges to make case-by-case sentencing determinations …\n\nAlthough judges must consult the advisory Sentencing Guidelines, they may vary from\n\nthese recommendations in light of the factors listed in 18 U.S.C. § 3553(a).” Maj. Op. at\n\n44. It is true that district judges retain the ability to vary from the Sentencing Guidelines’\n\nrecommendations. But variant sentences can shed their presumption of reasonableness\n\nand are more easily slapped down. United States v. Johnson, 242 Fed. Appx. 7, 10 (4th\n\nCir. 2007). What is more, the time and effort we are spending on making categorical\n\ndeterminations unmistakably sends this message: categorical holdings may, in the context\n\nof the Guidelines, be “advisory,” Maj. Op. at 44, but they carry the peremptory bearing of\n\ncommands. Finally, despite the majority’s reassurances, it is openly skeptical of the\n\nability of triers of fact to make the kind of determinations a case-specific approach here\n\nwould require. Maj. Op. at 34. Plainly the majority has far more faith in the ability of\n\nappellate judges to make legal determinations than it has in triers-of-fact to make factual\n\nones.\n\n Now triers of fact have suffered a double whammy. Just as application of the\n\ncategorical approach to crime-of-violence sentencing determinations displaces the district\n\n 62\n\njudge, application of the categorical approach to the residual clause of 18 U.S.C.\n\n§ 924(c)(3) displaces both the trial judge and jury. The majority converts the question\n\nbefore us—whether Simms committed a crime of violence—from an ordinary one of fact\n\ninto a lofty one of constitutional law that has nothing at all to do with Simms as an\n\nindividual. It makes the standard of review de novo. It discards the limited sufficiency\n\nreview normally reserved for jury verdicts. See Musacchio v. United States, 136 S.Ct.\n\n706, 715 (2016). It jettisons the clear error review normally accorded district courts’\n\nsentencing findings. In so doing it runs the role of juries and trial judges further into the\n\nground.\n\n To this, the majority offers only an adjectival denial that begs the question. Ante at\n\nn. 12. Its whole exercise is systemically damaging. In certain circumstances, the\n\ncategorical approach is useful because it relieves district courts of the institutional burden\n\ninvolved in reaching back through time to discover the undiscoverable. Moncrieffe v.\n\nHolder, 569 U.S. 184, 200–01 (2013). Those circumstances are not present here. Joseph\n\nSimms pleaded guilty, not because of some legal misunderstanding but because he\n\nrobbed a McDonald’s at gunpoint. Simms and his conspirator snuck into the occupied\n\nrestaurant in the middle of the night through the drive-through window. Once inside,\n\nSimms used his gun to menace the employees and demand money. He even tried to strike\n\none of them before ordering the workers to gather in the back office. He thereupon forced\n\nthe manager at gunpoint to open the safe and hand over the money. With the money in\n\nhand, Simms struck the manager on the top of his head with the gun, threw the cash\n\ndrawer at another employee, and fled.\n\n 63\n\n Those are the facts. That is the actuality of it all. The trial court had this entire\n\nnarrative at its disposal because, like all cases brought under §924(c), this conduct was\n\npart of instant offense. Simms’ actions are amply detailed in the pre-sentencing report\n\nwhich was not contested. Thus, there is not even an arguable institutional deficit at work\n\nhere; the trier of fact’s unique competence should be more than sufficient to decide\n\nwhether Simms committed a crime of violence.\n\n Unlike the categorical approach, the case-specific approach would allow the trial\n\njudge and jury to look at what is before them and do what they do best. Under this\n\napproach—approved by the First Circuit in United States v. Douglas, 907 F.3d 1 (1st Cir.\n\n2018), the Eleventh Circuit in Ovalles v. United States, 905 F.3d 1231 (11th Cir. 2018)\n\n(en banc), and the Second Circuit in United States v. Barrett, 903 F.3d 166 (2d Cir.\n\n2018)—the trier of fact would determine whether robberies like Simms’ “involved a\n\nsubstantial risk that physical force against the person or property of another may be\n\nused,” resolving the question no differently than it would the application of any other\n\nelement to the facts of the offense. 18 U.S.C. §924(c)(3)(B). Our review would be\n\nappropriately deferential and strictly limited, stepping in only if no reasonable trier of fact\n\ncould have found a crime of violence. See Jackson v. Virginia, 443 U.S. 307, 318-19\n\n(1979). Thus would the case-specific approach begin to right the indefensible imbalance\n\noccasioned by appellate micro-management.\n\n Ah, but in abjuring the case-specific approach, the majority is able to say, as a\n\nmatter of law naturally, that the statute is too vague and that Simms, in conspiring to rob\n\na fast food restaurant at gunpoint, committed no crime of violence. And as it stands, I am\n\n 64\n\nleft scratching my head and attempting to find some even remotely plausible explanation\n\nfor the appellate assumption of what should be a routine fact-finding role. I suppose it\n\ncould be an example of the old Barnum-and-Bailey urge to move our act to center ring.\n\nOr perhaps we simply do all this because we can—an exhibition of appellate muscularity\n\nprofoundly at odds with the restraint belonging to the rule of law.\n\n This appellate regency is not consonant with common sense, and is at cross-\n\npurposes with the thrust of humane sentencing reforms. Those reforms have concentrated\n\nin major part on reducing mandatory sentences for drug offenses. See, e.g., First Step Act\n\nof 2018, S. 756, 115th Cong. §401 (2018) (reducing mandatory minimums for prior drug\n\noffenders but expanding them to prior violent felons under the Controlled Substances\n\nAct). Here, by contrast, the majority is mounting a transparent attack upon Congress’\n\nintent to punish crimes of violence—particularly recidivist crimes of violence—more\n\nseverely, an intent grounded in the basic proposition that violent offenders, 18 U.S.C. §\n\n924(c), and repeat offenders, 18 U.S.C. § 924(e), pose a greater threat to public\n\nwellbeing.\n\n To repeat, the majority’s approach is even at odds with the asserted rationale of\n\nthe categorical approach itself, which is to spare district courts the burden of relitigating\n\ndifficult-to-ascertain facts to determine whether or not past offenses are crimes of\n\nviolence. Moncrieffe, 569 U.S. at 200–01. But this is a present-offense case. The trier of\n\nfact here has all the tools it needs to do the job. Rather than use these tools, the majority\n\nwould have us take yet another gratuitous flight from reality by throwing out the entire\n\nresidual clause of §924(c)(3) and potentially releasing a large and untold number of the\n\n 65\n\nmost violent cohort of criminal offenders prematurely back on to the streets. This\n\napproach floats impossibly above the reality that the trier of fact could capably bring to\n\nthe task. The hallmarks of the appellate ascendancy are once again painfully apparent,\n\nincluding an obliviousness to the fates of future victims, unknown and anonymous to\n\njudges, but whom Congress, in its wisdom, sought to shelter.\n\n The credo now seems to be to inflict more, not less, damage upon the whole\n\nedifice of law. The majority is so wedded to the categorical approach that it would rather\n\nstrike down the residual clause of § 924(c)(3) in its entirety than recognize trial courts’\n\ninherent capabilities. Constitutional assault now takes precedence over constitutional\n\navoidance. *\n\n Only by adopting the categorical approach does the majority create constitutional\n\nproblems for itself. The vagueness question that plagued the Supreme Court in Sessions\n\nv. Dimaya, 138 S. Ct. 1204 (2018), disappears altogether upon the adoption of the case-\n\nspecific approach. The text of 18 U.S.C. 924(c)(3)(B) supports it: as Judge Niemeyer\n\nindicates, language like “involves conduct” and “in the course of” and “by its nature” can\n\neasily and fairly be read to mandate a case-specific approach. The elements clause of 18\n\n\n *\n My friend Judge Wynn seeks to replace the doctrine of constitutional avoidance\nwith a search and destroy mission to strike down federal statutes. He then proceeds to\nembrace the odd proposition that upholding a statute is somehow a usurpation of\nCongress’ authority, and that interpreting a statute with due respect for the prerogatives\nof a coordinate branch is somehow an impermissible judicial exercise.\n It is further odd to suggest that an interpretation of a statute that allows triers of\nfact to apply its precise language to specific conduct represents a judicial “expansion” of\nan offense or indeed anything other than the most textually faithful rendering of the\nlegislature’s command.\n\n 66\n\nU.S.C. § 924(c)(3)(A) and the residual clause of 18 U.S.C. § 924(c)(3)(B) were written\n\nvery differently for a reason. Determinations of “substantial risk” are familiar territory to\n\ndistrict judges and juries, Johnson v. United States, 135 S. Ct. 2551, 2561 (2015), and we\n\nhave interpreted similar language to require a case-specific approach before, United\n\nStates v. Price, 777 F.3d 700 (4th Cir. 2015). What, if anything, the text leaves\n\nambiguous, Congress’ purpose makes manifest: this statute was plainly intended to\n\npunish people like Joseph Simms who use firearms to inspire fear and visit lawless and\n\nunforgettable trauma upon their fellow citizens.\n\n This whole enterprise will not end well. Territorial grabs are seldom becoming to\n\nthe rule of law, and the ouster of trial courts, juries, and indeed Congress from their\n\nrightful place in criminal justice is becoming one of the worst. This case does not even\n\nmount a frontal assault upon the categorical approach, only to the most extreme\n\nmanifestations of it. Lacking any rational explanation for the present state of affairs, I can\n\nonly conclude that the very words “categorical approach” exert some irresistible pull on\n\nthe appellate psyche. Like the children of medieval Hamelin, robbed of their reason,\n\ncourts are left only to follow the pied piper’s song off the cliff. But that does not mean we\n\ncannot wish a fond and affectionate farewell to those tumbling into the seas.\n\n\n\n\n 67\n\nNIEMEYER, Circuit Judge, with whom Judges WILKINSON, DUNCAN, AGEE,\n\nKEENAN, and QUATTLEBAUM join, dissenting:\n\n In holding that the definition of “crime of violence” in 18 U.S.C. § 924(c)(3)(B) is\n\nunconstitutionally vague and that § 924(c)(1)’s prohibition on using a firearm in\n\nconnection with a crime of violence can therefore never be enforced contemporaneously\n\nwith a Hobbs Act robbery conspiracy under 18 U.S.C. § 1951, the majority insists that\n\nthe “categorical approach” must be applied to assess whether the charged Hobbs Act\n\nconspiracy is a crime of violence. But this insistence both (1) distorts the basic reasons\n\nfor and limited application of the categorical approach and (2) rejects a sensible reading\n\nof § 924(c) that would avoid holding a key part of a major criminal law unconstitutional.\n\nConsequently, thousands of § 924(c)(1) convictions will unnecessarily be challenged as\n\npremised on what the majority today concludes is an unconstitutionally vague provision,\n\neven though the parties in those cases had little difficulty understanding, enforcing, or\n\ndefending the § 924(c)(1) charges at issue.\n\n In reaching its conclusion, the majority relies on the Supreme Court’s decisions in\n\nJohnson v. United States, 135 S. Ct. 2551 (2015), and Sessions v. Dimaya, 138 S. Ct.\n\n1204 (2018), where the Court found unconstitutionally vague the “residual clauses”\n\ndefining “violent felony” and “crime of violence” in 18 U.S.C. § 924(e) and § 16(b),\n\nwhich were used to categorically characterize prior convictions. While § 924(c) employs\n\na similar residual clause to define “crime of violence” in describing proscribed conduct,\n\nthe definition in § 924(c) does not require one to imagine in the abstract the “ordinary\n\ncase” of a particular crime and then to assess its risk of violence, as required by § 924(e)\n\n 68\n\nand § 16(b) to determine whether prior convictions were for violent crimes. Johnson,\n\n135 S. Ct. at 2557–58; Dimaya, 138 S. Ct. at 1215–16. Instead, as relevant here,\n\n§ 924(c)(1) requires rather straightforwardly that the government prove that the defendant\n\n(1) used, carried, or possessed a firearm (2) in connection with (3) a crime of violence,\n\nwhich, in this case, was alleged to be a Hobbs Act conspiracy. In this distinct context,\n\n§ 924(c) can readily be read as requiring the government to prove to the jury, as an\n\nelement of the offense, that a particular Hobbs Act conspiracy charged in an indictment\n\nqualifies as a crime of violence by showing that that offense, “by its nature,” posed “a\n\nsubstantial risk” of physical force being used. 18 U.S.C. § 924(c)(3)(B). And in both\n\nJohnson and Dimaya, the Supreme Court could not have been clearer that there are no\n\nvagueness problems when a crime-of-violence definition like § 924(c)(3)(B)’s is applied\n\nto “real-world conduct” in precisely this manner — that is, to assess “the riskiness of\n\nconduct in which an individual defendant engage[d] on a particular occasion.” Johnson,\n\n135 S. Ct. at 2561; see also Dimaya, 138 S. Ct. at 1215–16.\n\n In this case, Joseph Simms pleaded guilty to two counts — Count I charging him\n\nwith conspiracy to commit Hobbs Act robbery, in violation of 18 U.S.C. § 1951, and\n\nCount II charging him with brandishing a firearm during the commission of a “crime of\n\nviolence” — namely, the Hobbs Act conspiracy — in violation of § 924(c)(1)(A). The\n\ncrime-of-violence element in the § 924(c)(1) charge, even though defined in the same\n\nterms as the crime-of-violence definition in § 16(b), did not refer to a prior conviction in\n\nthe abstract but to the real-world conduct alleged in charging the Hobbs Act violation.\n\nSpecifically, Count I charged that Simms and others conspired to, and did in fact, rob\n\n 69\n\nMcDonald’s Restaurant # 31619 in Goldsboro, North Carolina, on April 14, 2014. To\n\nprove that Simms committed that crime, the government would have been required to\n\nshow that Simms conspired unlawfully to obstruct, delay, or affect commerce by\n\n“robbery,” defined to mean:\n\n the unlawful taking or obtaining of personal property from the person or in\n the presence of another, against his will, by means of actual or threatened\n force, or violence, or fear of injury, immediate or future, to his person or\n property, or property in his custody or possession, or the person or property\n of a relative or member of his family or of anyone in his company at the\n time of the taking or obtaining.\n\nId. § 1951(b)(1) (emphasis added). And then to prove further that Simms’s particular\n\nHobbs Act conspiracy offense — which, again, was alleged to have culminated in an\n\nactual robbery — qualified as a crime of violence for purposes of the § 924(c)(1)(A)\n\ncharge, the government would have been required to show that his conspiracy, “by its\n\nnature, involve[d] a substantial risk” of physical force being used “against the person or\n\nproperty of another.” Id. § 924(c)(3)(B).\n\n No one has asserted or can assert that this charge against Simms is\n\nunconstitutionally vague, as defined in Kolender v. Lawson, 461 U.S. 352, 357–58 (1983)\n\n(stating that the Due Process Clause “requires that a penal statute define the criminal\n\noffense with sufficient definiteness that ordinary people can understand what conduct is\n\nprohibited and in a manner that . . . establish[es] minimal guidelines to govern law\n\nenforcement”). Instead, the majority purports to make it vague by applying a\n\n“categorical approach” designed for completely distinct and limited circumstances, even\n\nthough nothing in the statute so requires. Simms’s conviction should be affirmed.\n\n\n 70\n\n I\n\n Simms and two others conspired to rob the McDonald’s Restaurant on April 14,\n\n2014. Shortly after 1:00 a.m., Simms and one co-conspirator entered the restaurant by\n\ncrawling through the drive-through window while the third person served as a lookout.\n\nSimms then pointed a gun at the restaurant’s manager and demanded money. At\n\ngunpoint, the manager opened the restaurant’s safe, after which Simms struck the\n\nmanager on the top of his head with the gun and threw a cash drawer at another\n\nemployee. The robbers fled with $1,100.\n\n After Simms was arrested and indicted, he pleaded guilty to Counts I and II of the\n\nindictment. Count I charged him with conspiracy to commit Hobbs Act robbery, in\n\nviolation of 18 U.S.C. § 1951, and it specifically alleged, as an overt act taken in\n\nfurtherance of the conspiracy, that Simms and others committed the agreed-upon robbery.\n\nAnd Count II charged that Simms had brandished a firearm during and in relation to a\n\ncrime of violence — namely, the Hobbs Act violation alleged in Count I — in violation\n\nof 18 U.S.C. § 924(c)(1)(A). In exchange for his guilty plea on these two counts, the\n\ngovernment agreed to dismiss a third count charging that Simms had possessed a firearm\n\nafter having been convicted of a felony, in violation of 18 U.S.C. §§ 922(g)(1) and\n\n924(a)(2).\n\n During sentencing, Simms objected to his § 924(c)(1)(A) conviction under\n\nCount II in light of the Supreme Court’s decision in Johnson, contending that the\n\nrequired element that he use a firearm during and in relation to a “crime of violence” was\n\nnot satisfied because the residual clause used to define “crime of violence” in\n\n 71\n\n§ 924(c)(3)(B) was unconstitutionally vague. The district court overruled Simms’s\n\nobjection and sentenced him to 199 months’ imprisonment — 115 months for the Hobbs\n\nAct conspiracy and a mandatory consecutive 84 months for the § 924(c)(1)(A) offense.\n\n Simms filed this appeal, maintaining that his § 924(c) conviction cannot stand\n\nbecause it is premised on a definition of “crime of violence” that is unconstitutionally\n\nvague under the reasoning of Johnson and Dimaya, the latter of which was decided after\n\nSimms filed his notice of appeal.\n\n\n II\n\n Simms contends that because there is “[n]o meaningful difference” between the\n\ndefinition of “violent felony” in § 924(e)(2)(B)(ii) that was found unconstitutionally\n\nvague in Johnson and the definition of “crime of violence” that was used to support his\n\nconviction under § 924(c)(1)(A), we must find the latter definition unconstitutionally\n\nvague and invalidate his conviction. And Dimaya, he maintains, confirms this conclusion\n\nsince the text of “Section 924(c)’s residual clause [defining crime of violence] is identical\n\nto Section 16(b).” According to Simms, § 924(c)(3)(B) compels the use of “the same\n\nordinary case approach and risk inquiry” that doomed the provisions in Johnson and\n\nDimaya, and the same result must therefore also follow here. The majority adopts the\n\nsame basic approach. Such an argument, however, is too formulaic, overlooking the role\n\nand context of the definitions, as well as the limited role of the categorical approach.\n\n In both Johnson and Dimaya, the Court addressed the question of applying the\n\n“categorical approach” to assess whether prior convictions were for violent crimes when\n\n\n 72\n\nsuch crimes were defined to include any felony that, in Johnson, “involves conduct that\n\npresents a serious potential risk of physical injury,” 18 U.S.C. § 924(e)(2)(B)(ii) or, in\n\nDimaya, that “by its nature, involves a substantial risk that physical force against the\n\nperson or property of another may be used in the course of committing the offense,” id.\n\n§ 16(b). The difficulty the Supreme Court found in making that determination arose not\n\nfrom the inability to assess violent conduct as defined by those “residual clauses,” but\n\nfrom assessing whether the prior conviction, considered under the categorical approach,\n\nwas for a violent crime under those definitions. In short, it was the limitation imposed by\n\napplying the categorical approach — where facts and conduct may not be considered —\n\nto those residual clauses that created the problem of vagueness for the Court.\n\n The “categorical approach” is a specific form of analysis adopted in light of the\n\nneed to determine whether prior convictions were for “violent felonies” or “crimes of\n\nviolence” under federal provisions — chief among them 18 U.S.C. § 924(e) — that\n\nimpose sentencing or other consequences on individuals who have those types of\n\nconvictions in their criminal histories. In Taylor v. United States, 495 U.S. 575, 600–02\n\n(1990), the Supreme Court recognized that, when applying § 924(e)’s sentencing\n\nenhancement, the question of whether a defendant’s prior conviction was for a “violent\n\nfelony” must focus exclusively on (1) the elements of the statute under which the\n\ndefendant was convicted and (2) the fact of conviction, and exclude any evaluation of the\n\nparticular facts or conduct underlying the prior conviction. In reaching this conclusion,\n\nthe Court started with the statutory text but hardly found it conclusive. See id. at 600–01\n\n(1990) (“First, the language of § 924(e) generally supports the inference that Congress\n\n 73\n\nintended the sentencing court to look only to the fact that the defendant had been\n\nconvicted of crimes falling within certain categories, and not to the facts underlying the\n\nprior convictions. . . . Read in . . . context, [the text] most likely refers to the elements of\n\nthe statute of conviction, not to the facts of each defendant’s conduct” (emphasis added)).\n\nRather, what appeared to seal the deal in favor of the “categorical approach” was the\n\nCourt’s serious concern that, in the context of prior convictions, “the practical difficulties\n\nand potential unfairness of a factual approach [would be] daunting.” Id. at 601. In this\n\nregard, the Court stressed both the impracticality of attempting to relitigate potentially\n\nlong-ago events, as well as the Sixth Amendment problem that would be created if\n\nsentencing judges were to make factual findings about the nature of the conduct\n\nunderlying a defendant’s prior conviction. Id. at 601–02; see also Descamps v. United\n\nStates, 570 U.S. 254, 269–70 (2013) (emphasizing “the categorical approach’s Sixth\n\nAmendment underpinnings,” as well as the “‘daunting’ difficulties and inequities that\n\nfirst encouraged [the Taylor Court] to adopt the categorical approach”).\n\n While the precise question resolved by Taylor was whether a defendant who had\n\nin fact committed “burglary,” as federal law defines that term, but was convicted under a\n\nbroader state statute should be treated as having a “burglary” conviction when applying\n\n§ 924(e), the Supreme Court subsequently confirmed that the “categorical approach” also\n\napplied to the “residual clause” portion of the “violent felony” definition, see James v.\n\nUnited States, 550 U.S. 192, 201–02 (2007). It did so even though it acknowledged that\n\nthe residual clause’s text — covering “crime[s]” that “involve[] conduct that presents a\n\nserious potential risk of physical injury to another,” § 924(e)(2)(B)(ii) — was “more\n\n 74\n\nambiguous” and “pose[d] greater interpretive difficulty” as to whether “it too refers to\n\ncrimes as generically defined.” Nijhawan v. Holder, 557 U.S. 29, 36 (2009) (emphasis\n\nadded).\n\n Unique problems arose, however, as courts attempted to apply the “categorical\n\napproach” to determine whether the offense of conviction — as defined by its elements,\n\nrather than its underlying conduct — was one that “involves conduct that presents a\n\nserious potential risk of physical injury.” 18 U.S.C. § 924(e)(2)(B)(ii) (emphasis added).\n\nInitially, in attempting to provide clarity, the Court instructed that “the proper inquiry is\n\nwhether the conduct encompassed by the elements of the offense, in the ordinary case,\n\npresents a serious potential risk of injury to another.” James, 550 U.S. at 208 (emphasis\n\nadded); see also Leocal v. Ashcroft, 543 U.S. 1, 7, 10 (2004) (similarly holding that, “[i]n\n\ndetermining whether [an individual’s prior] conviction falls within the ambit of § 16[’s\n\ndefinition of crime of violence], the statute directs our focus to the ‘offense’ of\n\nconviction,” “rather than to the particular facts relating to [the individual’s] crime,” and\n\ninterpreting § 16(b) in particular as “cover[ing] offenses that naturally involve a person\n\nacting in disregard of the risk that physical force might be used against another in\n\ncommitting an offense”). But in both Johnson and Dimaya, the Court ultimately\n\nconcluded that this ordinary-case form of the “categorical approach” entailed too much\n\nspeculation to be consistent with the Due Process Clause’s prohibition on enforcing\n\nvague laws.\n\n In particular, the Court in Johnson addressed the residual clause portion of the\n\ndefinition of “violent felony” in § 924(e) — a statute that provides a 15-year mandatory\n\n 75\n\nminimum sentence for certain firearm offenses if the defendant has three prior\n\nconvictions for a “violent felony.” Addressing how § 924(e)’s residual clause failed in\n\nthe context of the categorical approach, the Court explained:\n\n Two features of the residual clause conspire to make it\n unconstitutionally vague. In the first place, the residual clause leaves\n grave uncertainty about how to estimate the risk posed by a crime. It ties\n the judicial assessment of risk to a judicially imagined “ordinary case” of\n a crime [as required by the categorical approach], not to real-world facts\n or statutory elements.\n\n * * *\n\n At the same time, the residual clause leaves uncertainty about how\n much risk it takes for a crime to qualify as a violent felony. It is one thing\n to apply an imprecise “serious potential risk” standard to real-world\n facts; it is quite another to apply it to a judge-imagined abstraction [as\n required by the categorical approach].\n\nJohnson, 135 S. Ct. at 2557–58 (emphases added). The Court noted further that its own\n\n“repeated attempts and repeated failures to craft a principled and objective standard out\n\nof the residual clause confirm[ed] its hopeless indeterminacy.” Id. at 2558–59 (referring\n\nto the Court’s prior decisions in James, 550 U.S. 192; Begay v. United States, 553 U.S.\n\n137 (2008); Chambers v. United States, 555 U.S. 122 (2009); and Sykes v. United States,\n\n564 U.S. 1 (2011)). The Court concluded that “[i]nvoking so shapeless a provision to\n\ncondemn someone to prison for 15 years to life does not comport with the Constitution’s\n\nguarantee of due process.” Id. at 2560. In so concluding, however, the Court was quick\n\nto note that numerous statutes using terms like “substantial risk” — which the\n\ngovernment had warned would be affected by the Court’s holding — were not, in fact, in\n\nconstitutional jeopardy. The Court explained:\n\n\n 76\n\n [A]lmost all of the cited laws require gauging the riskiness of conduct in\n which an individual defendant engages on a particular occasion. As a\n general matter, we do not doubt the constitutionality of laws that call for\n the application of a qualitative standard such as “substantial risk” to real-\n world conduct; “the law is full of instances where a man’s fate depends on\n his estimating rightly . . . some matter of degree.”\n\nId. at 2561 (first emphasis in original; second emphasis added) (quoting Nash v. United\n\nStates, 229 U.S. 373, 377 (1913)).\n\n In Dimaya, the Court followed precisely the Johnson analysis, finding the residual\n\nclause used to define “crime of violence” in § 16(b) unconstitutionally vague. At issue in\n\nDimaya were provisions of the Immigration and Nationality Act that rendered deportable\n\nany alien convicted of an “aggravated felony,” 8 U.S.C. § 1227(a)(2)(A)(iii), which was\n\ndefined to include “crime[s] of violence,” as defined in § 16, see id. § 1101(a)(43)(F).\n\nSection 16, in turn, defined “crime of violence” in part by a residual clause similar to the\n\none used in § 924(e), which was addressed in Johnson. Specifically, the § 16 residual\n\nclause defined crime of violence to include any felony offense “that, by its nature,\n\ninvolves a substantial risk that physical force against the person or property of another\n\nmay be used in the course of committing the offense.” 18 U.S.C. § 16(b).\n\n After recalling in extensive detail the holding and reasoning of Johnson, the\n\nDimaya Court applied Johnson to find the residual clause in § 16(b) also\n\nunconstitutionally vague. It explained:\n\n To begin where Johnson did, § 16(b) also calls for a court to identify a\n crime’s “ordinary case” in order to measure the crime’s risk. . . . Nothing\n in § 16(b) helps courts to perform that task, just as nothing in [§ 924(e)]\n did. . . . [T]he “ordinary case” remains, as Johnson described it, an\n excessively “speculative,” essentially inscrutable thing.\n\n\n 77\n\n And § 16(b) also possesses the second fatal feature of [§ 924(e)’s]\n residual clause: uncertainty about the level of risk that makes a crime\n “violent.” In [§ 924(e)], that threshold was “serious potential risk”; in\n § 16(b), it is “substantial risk.” . . . The difficulty comes, in § 16’s residual\n clause just as in [§ 924(e)’s], from applying such a standard to “a judge-\n imagined abstraction” — i.e., “an idealized ordinary case of the crime.” It\n is then that the standard ceases to work in a way consistent with due\n process.\n\n138 S. Ct. at 1215–16 (citations omitted). But again, as in Johnson, the Court repeated\n\nthat it did “‘not doubt’ the constitutionality of applying § 16(b)’s ‘substantial risk\n\n[standard] to real-world conduct.’” Id. at 1215 (quoting Johnson, 135 S. Ct. at 2561).\n\n Thus, in both Johnson and Dimaya, the constitutional vagueness problem arose\n\nfrom having to imagine the ordinary case of an offense in the abstract — as required by\n\nthe categorical approach — and then to assess that imagined crime’s risk of violence.\n\n But the two features identified in Johnson and Dimaya that rendered the residual\n\nclauses there unconstitutional — the requirements of (1) imagining the ordinary case of a\n\ncrime and (2) applying to it a qualitative risk standard — do not arise when enforcing\n\n§ 924(c) because that statute does not require judicial assessment of an imagined ordinary\n\ncase. Instead, § 924(c) uses “crime of violence” as an element that is charged in the\n\nindictment in the context of real-world conduct on a particular occasion. See United\n\nStates v. Rodriguez-Moreno, 526 U.S. 275, 280 (1999) (noting that the commission of a\n\ncrime of violence is “an essential conduct element of the § 924(c)(1) offense”). In\n\nessence, rather than creating sentencing or immigration consequences for past convictions,\n\n§ 924(c)(1) “punishes the temporal and relational conjunction of two separate acts, on the\n\n\n\n\n 78\n\nground that together they pose an extreme risk of harm.” Rosemond v. United States, 572\n\nU.S. 65, 75 (2014).\n\n Because real-world conduct was charged in Simms’s indictment, including the\n\nHobbs Act violation alleged to be a crime of violence, we are not left to speculate about an\n\n“ordinary case” — a “judge-imagined abstraction.” Johnson, 135 S. Ct. at 2557–58.\n\nInstead, the indictment informs us of the conduct alleged to constitute a crime of violence,\n\nprecluding the need for guesswork. In Count II, Simms was charged with brandishing a\n\nfirearm on April 14, 2014, while conspiring to and actually robbing a specified\n\nMcDonald’s restaurant and its employees in Goldsboro, with the robbery element being\n\ndefined as “taking . . . personal property from [a] person . . . by means of actual or\n\nthreatened force, or violence, or fear of injury . . . to his person or property.” 18 U.S.C.\n\n§ 1951(b)(1). Simms was thus clearly notified of the government’s allegation that his\n\nHobbs Act conspiracy was among the offenses that, “by [their] nature, involve[] a\n\nsubstantial risk that physical force against the person or property of another may be used\n\nin the course of committing the offense.” Id. § 924(c)(3)(B).\n\n This indictment does not invite reliance on some vague, imagined, ordinary\n\noffense. Rather, it alleges specific offense conduct, which had to be proved with real-\n\nworld facts in order to obtain a conviction. Simms was thus placed on full notice of the\n\ncharges and of what had to be proved against him. The problem identified in Johnson and\n\nDimaya with courts’ imagining “an ‘idealized ordinary case of the crime,’” such that “no\n\none could tell how much risk the offense generally posed,” Dimaya, 138 S. Ct. at 1214\n\n(quoting Johnson, 135 S. Ct. at 2557), is simply not a problem in enforcing § 924(c). The\n\n 79\n\nprosecution of the offense does not involve divining the degree of risk from “a judge-\n\nimagined abstraction — i.e., an idealized ordinary case of the crime.” Id. at 1216 (internal\n\nquotation marks and citation omitted).\n\n In short, in both Johnson and Dimaya, the Supreme Court was presented with the\n\nproblem of applying the ordinary-case categorical approach to a prior conviction and\n\nthus imagining an abstract offense with a risk that is unknowable due to that very act of\n\njudicial imagination. Under § 924(c), however, no prior conviction must be imagined. To\n\nthe contrary, the commission of a crime of violence must be alleged as an element of the\n\n§ 924(c) offense and must be proved with real-world facts that occurred on a particular\n\noccasion. Thus, the definition of crime of violence, as used in § 924(c) as an element of\n\nthe offense, does not implicate the unique context identified in both Johnson and Dimaya,\n\nwhere the analysis was limited by the severe restrictions imposed by the categorical\n\napproach as applied to assess prior convictions.\n\n The majority argues that Congress adopted the “categorical approach” by including\n\nthe language in § 924(c)(3)(B) that a crime of violence includes a felony “offense . . . that\n\nby its nature, involves a substantial risk that physical force against the person or property\n\nof another may be used in the course of committing the offense.” It asserts that the phrase\n\n“offense . . . that by its nature,” naturally construed, means “categorically” and thus\n\nincorporates the “categorical approach.” Ante at 18, 21. Indeed, the majority concludes\n\nthat the only “plausible construction” of § 924(c)(3)(B) is that it “requires application of\n\nthe ordinary-case categorical approach.” Ante at 21, 41.\n\n\n\n 80\n\n But the majority’s insistence on interpreting § 924(c)(3)(B) as requiring the\n\n“categorical approach” represents the judicial equivalent of cramming a square peg into a\n\nround hole. Again, the lynchpin of the majority’s textual argument is § 924(c)(3)(B)’s\n\nprovision that an offense qualifies as a “violent felony” if “by its nature” it involves the\n\nrequisite risk of physical force, and it notes that “nature” is defined as “the basic or\n\ninherent features, character, or quality of something.” Ante at 21 (quoting Oxford\n\nDictionary of English 1183 (3d ed. 2010)). But while the majority emphasizes that\n\n§ 924(c)(3)(B) uses the phrase “by its nature” to modify “offense,” it overlooks that\n\n“offense” is a word that, as the Supreme Court has recognized, is sometimes used in\n\nordinary speech to “refer to a generic crime, say, the crime of fraud or theft in general”\n\nand other times readily used to “refer to the specific acts in which an offender engaged on\n\na specific occasion” — e.g., “the fraud that the defendant planned and executed last\n\nmonth.” Nijhawan, 557 U.S. at 33–34. And it is just as linguistically reasonable to speak\n\nof the “nature” of the defendant’s particular offense, as it is to refer to the “nature” of the\n\ngeneral offense as defined by law. See United States v. Barrett, 903 F.3d 166, 182 (2d\n\nCir. 2018) (noting that “nothing in the[] definitions [of the word ‘nature’] indicates\n\nwhether the offense whose inherent characteristics are to be considered is the generic\n\ncrime or the particular one charged”); accord United States v. Douglas, 907 F.3d 1, 11\n\n(1st Cir. 2018); Ovalles v. United States, 905 F.3d 1231, 1248 (11th Cir. 2018) (en banc).\n\n In addition, the majority’s argument is undermined by another feature of\n\n§ 924(c)(3)’s text — namely, the textual difference between subsections (A) and (B).\n\nSubsection (A) provides that a “crime of violence” includes any felony offense that has\n\n 81\n\n“as an element the use, attempted use, or threatened use of physical force,” whereas\n\nsubsection (B) provides that a “crime of violence” includes any felony offense that “by its\n\nnature[] involves a substantial risk” of physical force being used in the course of its\n\ncommission. The phrase “by its nature” in subsection (B) is thus distinct from the use of\n\n“elements” in subsection (A), suggesting that the analysis under subsection (B) should\n\nfocus not on how an offense is defined by law, but on the nature of the defendant’s offense\n\nand the degree of risk posed by it. And this interpretation is only strengthened by\n\nsubsection (B)’s focus on the risk that force may be “used in the course of committing the\n\noffense.” Moreover, such a distinction between subsections (A) and (B) makes good\n\nsense. Subsection (A) thus qualifies a felony as a “crime of violence” if its elements\n\nrequire proof that the defendant “use[d], attempt[ed] [to] use, or threaten[ed] [to] use . . .\n\nphysical force,” while subsection (B) allows that even if an offense does not have such an\n\nelement, it can still qualify as a crime of violence if, as committed on a particular\n\noccasion, it actually “involve[d] a substantial risk” of physical force being used. And\n\nCongress added further certain phrases to emphasize that this determination is intended to\n\nbe relatively broad, covering even those particular violations that, “by [their] nature,\n\ninvolve a substantial risk that physical force . . . may be used.”\n\n This last statutory feature in particular also precludes the majority’s additional\n\nargument that the rule against surplusage compels a categorical interpretation of\n\n§ 924(c)(3)(B). See ante at 21–22.\n\n To be sure, this reading of § 924(c)(3)(B) differs from the interpretation the\n\nSupreme Court in Johnson gave to the similar language defining “violent felony” in\n\n 82\n\n§ 924(e), as well as from the Dimaya plurality’s interpretation of the materially identical\n\ntext in § 16(b). But this difference is readily explained by the fact that § 924(e) and\n\n§ 16(b) are applied to characterize prior convictions, and the Court was therefore\n\ncompelled to apply the categorical approach. See Johnson, 135 S. Ct. at 2562 (concluding\n\nthat “‘[t]he only plausible interpretation’” of § 924(e)’s residual clause is that it “requires\n\nuse of the categorical approach” (1) because the text’s “emphasis on convictions indicates\n\nthat ‘Congress intended the sentencing court to look only to the fact that the defendant had\n\nbeen convicted of crimes falling within certain categories’” and (2) because of “the utter\n\nimpracticality of requiring a sentencing court to reconstruct, long after the original\n\nconviction, the conduct underlying that conviction” (emphasis added) (quoting Taylor,\n\n495 U.S. at 600–02)); see also Dimaya, 138 S. Ct. at 1217–18 (plurality opinion)\n\n(emphasizing, among other reasons for concluding that § 16(b) must be read as\n\nincorporating the categorical approach, (1) that the “Court adopted the categorical\n\napproach in part to avoid the Sixth Amendment concerns that would arise from sentencing\n\ncourts’ making findings of fact that properly belong to juries” and (2) that a fact-based\n\nreading would create “the daunting difficulties of accurately reconstructing, often many\n\nyears later, the conduct underlying a conviction’” (emphasis added) (internal quotation\n\nmarks, brackets, and citations omitted)).\n\n By contrast, the definition of crime of violence in § 924(c)(3) applies only to\n\ncontemporaneously charged conduct that is made an element of the § 924(c)(1) violation\n\nand never to prior convictions. And, in that distinct context, the important practical\n\nconsiderations and Sixth Amendment concerns that led the Court to develop and adhere to\n\n 83\n\nthe categorical approach for similar residual clauses simply do not apply. It is therefore\n\nnot surprising that § 924(c) has presented little difficulty to courts, prosecutors, and\n\ndefense counsel in its enforcement, and the so-called problems with that statute have been\n\ncreated only by the effort to force the ordinary-case categorical approach, applicable in\n\nother circumstances, onto a statute that punishes the use of a firearm in connection with a\n\ncrime of violence, in this case a Hobbs Act conspiracy.\n\n But were there any doubt about the proper construction of § 924(c) we would\n\nnonetheless have to give the statute the benefit of the doubt when a constitutional reading\n\nof it is “fairly possible,” as I surely conclude. I.N.S. v. St. Cyr, 533 U.S. 289, 299–300\n\n(2001). This constitutional avoidance doctrine serves the “basic democratic function of\n\nmaintaining a set of statutes that reflect, rather than distort, the policy choices that the\n\nelected representatives have made.” Almendarez-Torres v. United States, 523 U.S. 224,\n\n238 (1998).\n\n I thus readily conclude that the residual clause in § 924(c) defining the “crime of\n\nviolence” element of the offense is not unconstitutionally vague. Simms received ample\n\nnotice of how to conform his conduct to the law, and the statute provides adequate\n\nstandards to prevent “arbitrary and discriminatory enforcement.” Kolender, 461 U.S. at\n\n357. I would accordingly affirm the district court’s judgment.\n\n\n\n\n 84", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "WILKINSON, Circuit Judge, dissenting"}, {"author": "RICHARDSON, Circuit Judge, with whom Judge QUATTLEBAUM joins, dissenting", "type": "dissent", "text": "RICHARDSON, Circuit Judge, with whom Judge QUATTLEBAUM joins, dissenting:\n\n While robbing a McDonalds, Simms struck the manager on the head with a gun.\n\nBy statute, if the nature of Simms’s offense involved a “substantial risk of physical\n\nforce,” then it was a “crime of violence.” 18 U.S.C. § 924(c)(3)(B). And if we look to\n\nthe facts here, it seems obvious that Simms’s offense was a crime of violence: of course\n\nhitting someone over the head with a gun involves a substantial risk of physical force.\n\nAnd Simms agreed when he pleaded guilty.\n\n My colleagues in the majority take a different tack. Refusing to read the statute to\n\napply to the facts of this case, they insist that the statute must be applied to some\n\nhypothetical conduct that would be involved in an “ordinary case” of federal robbery.\n\nYet, by the majority’s own account, the hypothetical, “ordinary case” interpretation is not\n\nworkable here. In fact, even before adopting it, the majority accepts that its interpretation\n\nis unconstitutionally vague under the Fifth Amendment.\n\n This is not the right approach. It is our duty as judges, if we can, to give statutes a\n\nreasonable interpretation that conforms to the Constitution. Because the statute permits\n\nlooking directly to Simms’s conduct in pistol whipping a manager during a robbery, I\n\nrespectfully dissent.\n\n I. Avoiding an Unconstitutional Construction\n\n Any statutory provision must be interpreted, whenever possible, to avoid\n\nunconstitutionality. Our duty to adopt saving constructions dates back more than two\n\nhundred years. See Mossman v. Higginson, 4 U.S. (4 Dall.) 12 (1800); Society for the\n\n\n\n 85\n\nPropagation of the Gospel v. Wheeler, 22 F. Cas. 756, 769 (C.C.D.N.H. 1814). 1 At base,\n\nthe rule reflects respect for the political branches, presuming they intend to comply with\n\nour Constitution. 2 So long as it does not require doing violence to unambiguous\n\nlanguage, courts must act to save a statute with any plausible constitutional interpretation.\n\nGrenada Cty. Supervisors v. Brogden, 112 U.S. 261, 269 (1884).\n\n Here, we face a binary choice. On the one hand, if Section 924(c)(3)(B) compels\n\nthe “ordinary case” interpretation, then it is unconstitutionally vague and Simms escapes\n\nliability. On the other, if the statute permits a case-specific interpretation, then it is\n\nconstitutional and Simms’s guilty plea stands.\n\n\n 1\n Justice Story later explained that if a\n\n section admits of two interpretations, one of which brings it within, and the\n other presses it beyond the constitutional authority of congress, it will\n become our duty to adopt the former construction; because a presumption\n never ought to be indulged, that congress meant to exercise or usurp any\n unconstitutional authority, unless that conclusion is forced upon the Court\n by language altogether unambiguous.\n\nUnited States v. Coombs, 37 U.S. (12 Pet.) 72, 76 (1838); see also Blodgett v. Holden,\n275 U.S. 142, 148 (1927) (Holmes, J., concurring) (“[A]s between two possible\ninterpretations of a statute, by one of which it would be unconstitutional and by the other\nvalid, [a court’s] plain duty is to adopt that which will save the Act.”).\n 2\n The requirement that a court adopt a plausible interpretation to avoid striking\ndown a statute as unconstitutional is sometimes referred to as the presumption of validity\nor the unconstitutionality canon. It is related to the more recent, and arguably weaker,\n“doubts” canon, which urges courts to adopt plausible interpretations of statutes to avoid\nhaving to contemplate difficult constitutional questions. See United States ex rel.\nAttorney General v. Delaware & Hudson Co., 213 U.S. 366, 408 (1909); see also\nJennings v. Rodriguez, 138 S. Ct. 830, 836 (2018). For a discussion of these two\nprinciples, see Adrian Vermeule, Saving Constructions, 85 GEO. L.J. 1945, 1948–50\n(1997).\n\n\n 86\n\n While our choice is binary, statutory interpretation often is not. Typically, judges\n\nseek the “best reading of the statute by interpreting the words of the statute, taking\n\naccount of the context of the whole statute, and applying the agreed-upon semantic\n\ncanons.” Brett Kavanaugh, Fixing Statutory Interpretation, 129 HARV. L. REV. 2118,\n\n2121 (2016) (book review). Along the way to the “best” interpretation, we discard other\n\npossibilities. Not all the rejects are flat-out wrong (although some are). An interpretation\n\nmay have some support in the text, and even from a canon, but still get left on the cutting-\n\nroom floor in favor of another, better option. And we keep on discarding until we find\n\nthe best one.\n\n But in some circumstances, we must abandon the search for the best reading of the\n\nstatute. When a statute’s best interpretation would render it unconstitutional, a court\n\nmust identify and adopt any fairly possible interpretation that would save it. See Hooper\n\nv. California, 155 U.S. 648, 657 (1895) (“The elementary rule is that every reasonable\n\nconstruction must be resorted to, in order to save a statute from unconstitutionality.”).\n\nThat means looking for a plausible constitutional option for Section 924(c)(3)(B). 3\n\n\n\n\n 3\n I agree with much of Judge Niemeyer’s fine opinion finding that the proper\nconstruction of the residual clause requires looking to Simms’s actual conduct. In my\nview, however, the duty to adopt a saving construction obviates the need to identify the\nbest reading, requiring us to determine only whether a fairly possible reading permits\nlooking to Simms’s actual conduct. See Ante at 84 (Niemeyer, J., dissenting) (noting in\nthe alternative that the constitutional avoidance doctrine would apply if there were any\ndoubt about the proper construction).\n\n\n 87\n\n II. The Residual Clause of Section 924(c)(3)\n\n Having framed our endeavor, I begin by asking what readings of the statute are\n\neven conceivable. Once the conceivable interpretations are identified, I turn to evaluating\n\nwhich of those are plausible.\n\n Section 924(c)(3) defines the term “crime of violence” to mean\n\n an offense that is a felony and—\n (A) has as an element the use, attempted use, or threatened use of physical\n force against the person or property of another, or\n (B) that by its nature, involves a substantial risk that physical force\n against the person or property of another may be used in the course of\n committing the offense.\n\n(emphasis added). This statute provides two definitions of what constitutes a “crime of\n\nviolence.” The first, sometimes called the “elements clause,” focuses on whether the\n\n“elements” of an offense include the “use, attempted use, or threatened use of physical\n\nforce.” The second, called the “residual clause,” focuses on whether the offense’s\n\n“nature” involves “a substantial risk that physical force” may be “used in the course of\n\ncommitting the offense.” As its name conveys, the second clause is residual, meaning it\n\noperates as a catch-all for those offenders engaged in this type of risky conduct that might\n\notherwise fail to meet the elements clause.\n\n A. Three Conceivable Interpretations of the Residual Clause\n\n The language and context of the residual clause point to three conceivable\n\nreadings, each asking us to look at the offense through a different lens. First, an\n\nelements-based one: Does the offense legally require proof of a substantial risk of\n\nphysical force? Second, a hypothetical one: Does a judicially imagined “ordinary”\n\n 88\n\nversion of the offense involve conduct that presents a substantial risk of force? Third, a\n\nfactual one: Does the specific offense involve actual conduct that presents a substantial\n\nrisk of physical force? See generally Johnson v. United States, 135 S. Ct. 2551, 2557\n\n(2015) (noting three possibilities for consideration: the statutory “elements,” a “judicially\n\nimagined ordinary case,” or “real-world facts”). These readings have been fleshed out in\n\nthe context of other, similar statutes, although there is no binding Supreme Court\n\nprecedent governing this particular statute.\n\n The first and most formalistic reading requires looking at the elements of the\n\n“offense.” See Descamps v. United States, 570 U.S. 254, 257 (2013). That is, one would\n\nask whether one element of the crime is a substantial risk that physical force may be\n\nused.\n\n The second reading concentrates not on the legal elements of the crime but on the\n\nconduct thought to be ordinarily involved in violating those elements. This approach is\n\nsimilar to the first in that it is “categorical”: once the courts decide whether a particular\n\ncriminal statute satisfies the residual clause, that holding applies to any conviction under\n\nthe statute, without a factfinder looking at what that defendant did. Yet it differs from the\n\nfirst in that it looks to conduct: namely “whether the conduct encompassed by the\n\nelements of the offense, in the ordinary case, presents a serious potential risk.” James v.\n\nUnited States, 550 U.S. 192, 208 (2007) (emphasis added). This approach is an exercise\n\nin judicial imagination, requiring “a court to picture the kind of conduct that the crime\n\ninvolves in ‘the ordinary case,’ and to judge whether that abstraction presents a serious\n\npotential risk.” Johnson, 135 S. Ct. at 2557.\n\n 89\n\n Real-world facts are the focus of the approach resulting from the third and final\n\ninterpretation. This approach is like the second approach, and unlike the first, in that it\n\nlooks at conduct. Yet unlike the second approach, it is not categorical and requires no\n\njudicial ingenuity: it asks only whether the actual conduct committed by the defendant\n\npresents a substantial risk on a case-by-case basis. The third approach has significant\n\nappeal, relieving judges of imagining hypotheticals and empowering factfinders\n\n(generally juries) to do their job. See Ante at 64 (Wilkinson, J., dissenting).\n\n B. The Case-Specific Interpretation of the Residual Clause is Plausible\n\n Thus, three conceivable interpretations are available. The first and third readings\n\nare constitutional; the second, “ordinary case” reading, would be unconstitutionally\n\nvague. We must therefore ask whether the first and third are fairly possible. If either is,\n\nthen the “ordinary case” interpretation must be rejected to save the statute.\n\n Neither party argues that the first interpretation is plausible, and for good reason.\n\nTo be sure, the term “offense” can be read to encompass the formalistic concept of a\n\ncrime as defined by its elements. Indeed, “offense” takes that meaning in subsection A’s\n\nelements clause. Yet there is little else good to say about this interpretation, and two\n\nconsiderations make it untenable. First, Congress knew how to specify an elements-\n\nbased approach and did so in subsection A, but not in subsection B. Subsection B\n\ncontemplates an understanding of “offense” that is broader than the formalistic\n\nsubsection A. See United States v. Price, 777 F.3d 700, 708–09 (4th Cir. 2015). Second,\n\nI am aware of no other federal criminal statute with a “substantial risk” that “physical\n\n\n\n 90\n\nforce” “may be used” as an actual element. And we generally avoid interpreting statutes\n\nto render them a nullity.\n\n The third interpretation is a different story. Consider again the term “offense.”\n\nThe term is ambiguous: it is consistent with the elements-based approach (as already\n\nnoted), but also with the others. The Supreme Court has found it may refer to (1) “a\n\ngeneric crime, say, the crime of fraud or theft in general,” or (2) “the specific acts in\n\nwhich an offender engaged on a specific occasion, say, the fraud that the defendant\n\nplanned and executed last month.” Nijhawan v. Holder, 557 U.S. 29, 33–34 (2009); see\n\nalso United States v. Hayes, 555 U.S. 415, 426 (2009). While definition (1) fits the\n\nelements-based and “ordinary case” approaches, definition (2) permits consideration of\n\nthe real-world conduct committed by the defendant.\n\n To decide which definition is appropriate, courts look to the statutory context. In\n\nsome cases, context compels a case-specific approach based on real-world conduct. See\n\nNijhawan, 557 U.S. at 40. In others, context compels the “generic” interpretation. See\n\nid. at 37. The term may even be used in both senses within the same sentence: to mean a\n\ngeneric crime and how the specific crime was committed. See Hayes, 555 U.S. at 421\n\n(holding “offense” that “has, as an element, the use or attempted use of physical\n\nforce . . . , committed by a current or former spouse,” requires a categorical determination\n\nof the elements but a fact-specific evaluation of the person who committed the offense).\n\n Our own precedent confirms that “offense” may compel examining real-world\n\nconduct. In Price, the statute defined “sex offense” to mean a “criminal offense that is a\n\nspecified offense against a minor.” 777 F.3d at 704 (quoting 42 U.S.C.\n\n 91\n\n§ 16911(5)(A)(ii)). The statute then defined “specified offense[s] against a minor”\n\naccording to a list of enumerated offenses and a residual clause encompassing “[a]ny\n\nconduct that by its nature is a sex offense against a minor.” Id. (quoting 42 U.S.C.\n\n§ 16911(7)(I)). In that context, we concluded, the statute “refers to how an offense was\n\ncommitted—not a generic offense.” Id. at 709. 4\n\n Here, we need only decide whether the fact-specific approach—which again, the\n\nSupreme Court has held is a permissible reading of the word “offense”—is plausible.\n\nAnd the context here shows that it is.\n\n Consider the phrase “by its nature.” In ordinary use, “nature” means a “normal\n\nand characteristic quality” of something. Webster’s Third New International Dictionary\n\n1507–08 (1986); see also Oxford Dictionary of English 1183 (3d ed. 2010) (“basic or\n\ninherent features, character, or qualities of something”). This definition, however, merely\n\nraises the question of what the “something” is? See United States v. Barrett, 903 F.3d\n\n166, 182 (2d Cir. 2018). It could be either the hypothetical, “ordinary case” conduct of\n\nthe second interpretation or the case-specific, real-world conduct of the third. Compare\n\n\n 4\n The majority attempts to distinguish Price on the basis that Section\n924(c)(3)(B)’s residual clause lacks “conduct-specific language.” Majority Op. at 30.\nYet the majority has found that the residual clause demands adopting the “ordinary case”\napproach, an interpretation that focuses exclusively on hypothetical conduct.\n\n Even were the majority’s distinction convincing, this would miss the point. Cases\nlike Nijhawan, Hayes, and Price reveal that the phrasing used here does not unavoidably\nrefer to the “ordinary case” approach. It makes no difference whether the majority can\nfind some linguistic distinction for each case, because a reading calling for the fact-\nspecific approach need only be fairly possible.\n\n\n 92\n\nDugger v. Adams, 489 U.S. 401, 410 n.6 (1989) (using “by its nature” to refer to general\n\ncharacteristics and not individualized circumstances), with H.J. Inc. v. Nw. Bell Tel. Co.,\n\n492 U.S. 229, 241–42 (1989) (noting that RICO continuity may be shown by “past\n\nconduct that by its nature projects into the future with a threat of repetition,” and that this\n\nconduct “depends on the specific facts of each case” (emphasis added)), and Doolan v.\n\nCarr, 125 U.S. 618, 625 (1887) (“[E]ven a patent from the government of the United\n\nStates, issued with all the forms of law, may be shown to be void by extrinsic evidence if\n\nit be such evidence as by its nature is capable of showing a want of authority for its\n\nissue.” (emphasis added)). Thus, the phrase “by its nature” does not resolve the meaning\n\nof “offense” one way or the other.\n\n Nor does the rest of the residual clause: “involves a substantial risk that physical\n\nforce against the person or property of another may be used in the course of committing\n\nthe offense.” Either hypothetical conduct or actual conduct may “involve substantial\n\nrisk.” Similarly, the predictive phrase “may be used” applies equally well to hypothetical\n\nor actual conduct. And the same is true of “in the course of committing the offense.”\n\n Tellingly, the majority concedes that all the individual terms in the statute are\n\nsusceptible to a case-specific interpretation. Somehow, it claims, the combination of\n\nwords compels the “ordinary case” approach. See Majority Op. at 26–27. But a handful\n\nof maybe’s simply do not add up to a never.\n\n III. Precedent Does Not Demand the “Ordinary Case” Approach\n\n The majority also claims that the Supreme Court has already resolved this issue by\n\nholding that the language used in Section 924(c)(3)(B) permits only one reading: the\n\n 93\n\nhypothetical conduct of an ordinary case. In so doing, the majority rewrites history. The\n\nSupreme Court has never held that the language like that in Section 924(c)(3)(B)\n\nnecessarily requires the “ordinary case” analysis.\n\n The origins of the modern “ordinary case” approach lie in Supreme Court\n\ndecisions interpreting statutory sentencing enhancements based on prior convictions for\n\n“violent felonies.” Those decisions adopted a “categorical approach,” requiring courts to\n\nlook at the elements of the offense and not the defendant’s conduct. See Shepard v.\n\nUnited States, 544 U.S. 13, 19 (2005); Taylor v. United States, 495 U.S. 575, 600–02\n\n(1990). In addition to the text and practical considerations, one of the main motivators of\n\nthe “categorical approach” was the need to avoid a potential Sixth Amendment problem:\n\nif a mandatory sentencing enhancement arose from the facts underlying a prior\n\nconviction, as opposed to the fact of conviction itself, then those facts could not be\n\ndetermined by a judge (absent a defendant’s wavier). Shepard, 544 U.S. at 24 (plurality\n\nopinion). The importance of the Sixth Amendment to the history of the categorical\n\napproach is hardly controversial. The Supreme Court itself has directed courts to\n\nconsider “the categorical approach’s Sixth Amendment underpinnings” when applying it.\n\nDescamps, 570 U.S. at 269. And multiple panel decisions by this Court have\n\nacknowledged as much. See, e.g., Price, 777 F.3d at 709–10. 5\n\n\n 5\n The majority downplays the importance of the Sixth Amendment concern,\nsuggesting that these cases were only “secondarily informed” by nontextual\nconsiderations. Majority Op. at 20. That argument is ad hoc, running against uniform\nSupreme Court and circuit-level precedent to the contrary. Equally unconvincing is the\nmajority’s suggestion that, because the Court started with the text in these cases, the text\n(Continued)\n 94\n\n Over time, the categorical approach was extended to new contexts. There are a\n\nnumber of statutes that mix and match similar language to define “crimes of violence” or\n\n“violent felonies.” The language at issue in Taylor and Shepard, the classic cases,\n\nencompasses crimes that correspond to the “generic” definition of certain enumerated\n\ncrimes. Other statutes include language resembling the “elements clause” of Section\n\n924(c)(3)(A) and the “residual clause” of Section 924(c)(3)(B). Unsurprisingly, the\n\nCourt transplanted the categorical approach into these similar contexts. Yet the Court\n\ncontinued to note the important Sixth Amendment problems that the categorical approach\n\navoided. See James, 550 U.S. at 213–14.\n\n The majority identifies only two cases suggesting that statutory text alone—\n\nunaccompanied by constitutional and other considerations—was sufficient to support the\n\ncategorical approach. Neither is persuasive in interpreting the statute at hand. The first\n\ncase, Leocal v. Ashcroft, only superficially supports the majority. After quoting language\n\nfrom the residual clause in 18 U.S.C. § 16(b) (textually similar to the residual clause of\n\nSection 924(c)(3)(B)), the Court stated: “[t]his language requires us to look to the\n\nelements and the nature of the offense of conviction, rather than to the particular facts\n\nrelating to petitioner’s crime.” 543 U.S. 1, 7 (2004). Yet it is hardly surprising that the\n\nSupreme Court did not analyze the issue in detail: the parties, amici, and the Court\n\n\n\n\nalone must have been decisive. Id. at 19. The Supreme Court, like all courts, always\nstarts from the text in statutory interpretation cases. See, e.g., Sebelius v. Cloer, 569 U.S.\n369, 376 (2013).\n\n\n 95\n\naccepted the application of the categorical approach as an untested premise before\n\naddressing the issue presented. Cf. Sessions v. Dimaya, 138 S. Ct. 1204, 1232 (2018)\n\n(Gorsuch, J., concurring in part and concurring in judgment) (accepting the “ordinary\n\ncase” approach to Section 16(b) as a premise).\n\n As everyone accepted the categorical approach, Leocal had no reason to consider\n\nany saving constructions to avoid unconstitutionality (or constitutional doubts). So even\n\nwere one to read Leocal as finding the “best” interpretation, that does not answer whether\n\nthat is the only plausible interpretation. Moreover, Leocal addressed the application of\n\nSection 16 to prior convictions. It is in that context that applying a factual approach\n\nwould raise the serious practical and Sixth Amendment concerns at issue in Taylor,\n\nShepard, and James. Section 924(c)(3) presents none of those problems, as it applies\n\nonly to contemporaneous conduct. Nor did Leocal foresee that applying the “ordinary\n\ncase” approach would be unconstitutionally vague under the Fifth Amendment. In fact,\n\nLeocal did not even use the term “ordinary case.” In sum, Leocal’s acceptance of an\n\nundisputed premise while interpreting a different statute in a different context without\n\ndiscussing the plausibility of a saving construction does not dictate the interpretation of\n\nSection 924(c)(3)(B).\n\n The second case, Dimaya, is even less supportive. It is true that Section IV(A) of\n\nJustice Kagan’s opinion in Dimaya held that similar language demands the use of the\n\ncategorical approach, but that interpretation was only endorsed by a plurality of the\n\nSupreme Court. Justice Gorsuch chose not to join that section of the opinion. Under the\n\nMarks rule, the binding holding of the Court is the narrowest opinion from those\n\n 96\n\nconcurring in the judgment. Marks v. United States, 430 U.S. 188, 193 (1977). Thus,\n\nJustice Gorsuch’s narrower concurrence controls. He (like the parties) simply assumed\n\nthat the “ordinary case” approach applied, and on that basis held that § 16(b) is\n\nimpermissibly vague. Dimaya, 138 S. Ct. at 1232–33 (Gorsuch, J., concurring in part and\n\nconcurring in judgment).\n\n As for the debated language, Justice Gorsuch noted that “[p]lausibly, anyway, the\n\nword ‘nature’ might refer to an inevitable characteristic of the offense; one that would\n\npresent itself automatically, whenever the statute is violated.” Dimaya, 138 S. Ct. at\n\n1233. He continued, “[w]hile I remain open to different arguments about our precedent\n\nand the proper reading of language like this, I would address them in another case,\n\nwhether involving the INA or a different statute, where the parties have a chance to be\n\nheard and we might benefit from their learning.” Id. Thus, Justice Gorsuch\n\nunambiguously stated that he is open to other interpretations, even involving the statute at\n\nissue in his own opinion. As his concurrence shows, the majority gets Dimaya backward.\n\nDimaya makes clear that the interpretation of this language is a live issue before the\n\nSupreme Court, not one settled by precedent.\n\n If anything, the history of the categorical approach shows that the “ordinary case”\n\napproach should be jettisoned wherever possible. In truth, there is not one categorical\n\napproach; there are two. When the purely elements-based categorical approach from\n\nTaylor and Shepard was applied to residual clauses, it evolved (or perhaps devolved) into\n\nthe “ordinary case” approach. See James, 550 U.S. at 208. Those two approaches are\n\nonly superficially similar. The elements-based approach looks only at the formal\n\n 97\n\ndefinition of the offense; the “ordinary case” approach tries to construct a hypothetical\n\nmodel of conduct for the offense. In both logic and application, they are as different from\n\neach other as they are from the case-specific approach. History has shown that the\n\n“ordinary case” approach is unworkable, so much so that its application has been\n\ndeclared unconstitutionally vague twice. Johnson, 135 S. Ct. at 2563; Dimaya, 138 S. Ct.\n\nat 1232–33 (Gorsuch, J., concurring in part and concurring in judgment).\n\n In contexts where the Sixth Amendment applies—in particular, mandatory\n\nsentencing enhancements for prior convictions—the “ordinary case” approach is the only\n\nway to interpret a residual clause. But in many contexts, those Sixth Amendment\n\nconcerns do not apply. This is one of them: The consideration of contemporaneous\n\nconduct under Section 924(c)(3)(B) need not create any Sixth Amendment concerns. See\n\nAnte at 79 (Niemeyer, J., dissenting). And we have noted the importance of this\n\ndistinction when rejecting specific applications of the categorical approach. Price, 777\n\nF.3d at 709–10 (noting, in rejecting the categorical approach, that “Sixth Amendment\n\nconcerns that compel the judicial use of the categorical approach in other contexts are not\n\npresent here”). When Sixth Amendment concerns do not apply, but Fifth Amendment\n\nvagueness concerns do, we must adopt the fact-specific interpretation.\n\n IV. The Majority’s Remaining Arguments\n\n The majority advances a grab-bag of other considerations to support its “ordinary\n\ncase” interpretation. Many of these are unpersuasive on their face, but I mention three\n\nbriefly.\n\n\n\n 98\n\n First, the majority argues that adopting the factual approach to the residual clause\n\nwould lead to a contradiction: “offense that is a felony” would be read to have a\n\ncategorical interpretation in the elements clause, but a case-specific interpretation in the\n\nresidual clause. Majority Op. at 23–24. This reasoning is hollow because, as I have\n\nalready explained, there is not only one categorical approach. The hypothetical conduct\n\nof the “ordinary case” approach adopted by the majority differs substantially from the\n\nlegal elements of the elements-based approach. Thus, the interpretation the majority\n\nadopts is similarly contradictory. And in any event, neither “contradiction” is that\n\nconcerning. See Nijhawan, 557 U.S. at 37 (The “statute lists several of its ‘offenses’ in\n\nlanguage that must refer to generic crimes . . . [but] it lists certain other ‘offenses’ using\n\nlanguage that almost certainly does not refer to generic crimes but refers to specific\n\ncircumstances.”).\n\n The majority also suggests that reading the residual clause to apply to real-world\n\nfactual conduct violates the rule against surplusage by draining the phrase “by its nature”\n\nof any meaning. At the outset, the Supreme Court has explained that the rule against\n\nsurplusage “is not absolute” and is itself to be avoided when it causes more problems\n\nthan it solves. Lamie v. U.S. Trustee, 540 U.S. 526, 536 (2004). In any event, “by its\n\nnature” is not superfluous under the case-specific approach for two reasons. First, the\n\nphrase distinguishes subsection B’s conduct-based residual clause from subsection A’s\n\nelements clause. The latter addresses the legal elements of the offense (“has as an\n\nelement”), while the former focuses more broadly on conduct (whether hypothetical or\n\nactual conduct). See Price, 777 F.3d at 708–09. Second, “by its nature” limits the\n\n 99\n\nresidual clause to conduct that involves risk inherently or naturally, not merely\n\nincidentally or by happenstance. In this sense, the phrase “by its nature” acts as an\n\nintensifier that limits the clause’s application to more dangerous crimes.\n\n Finally, the majority makes passing reference to the rule of lenity. Majority Op. at\n\n40. The majority cites no authority for the proposition that the rule of lenity, grounded in\n\nthe need for fair warning, demands that this Court knowingly adopt an interpretation so\n\nunclear that it is unconstitutionally vague. Indeed, this makes no sense. Cf. United States\n\nv. Lanier, 520 U.S. 259, 266 (1997) (describing the “rule of lenity” as the “junior version\n\nof the vagueness doctrine” that “ensures fair warning by so resolving ambiguity in a\n\ncriminal statute as to apply it only to conduct clearly covered”); United States v. Harriss,\n\n347 U.S. 612, 617–18 (1954) (noting that while the Constitution “is violated by a\n\ncriminal statute that fails to give a person of ordinary intelligence fair notice,” a court is\n\nunder a “duty” to give a “reasonable construction of the statute” that makes the “class of\n\noffenses . . . constitutionally definite”). It may well be that no ordinary person would be\n\nfairly warned that their conduct might be implicated by the hypothetical, “ordinary case”\n\nof robbery, but most everyone would understand that pistol whipping someone during an\n\narmed robbery is a crime of violence. 6\n\n\n 6\n Judge Wynn suggests that the avoidance doctrine should allow only those\ninterpretations that “narrow” a criminal statute. See Ante at 47 (Wynn, J., concurring).\nEven if one accepts this novel theory, the “ordinary case” approach is not inherently\n“narrower” than the case-specific approach. Since the “ordinary case” approach focuses\non judicially-imagined hypothetical conduct in place of a defendant’s own actions, that\napproach is both over- and under-inclusive. While some defendants would be guilty\nunder the case-specific approach but not the “ordinary case” approach, other defendants\n(Continued)\n 100\n\n * * *\n\n Occasionally we find ourselves so far down the rabbit hole that logic appears\n\nupside down. It is true that the faithful application of the law may lead to odd results.\n\nAnd I certainly do not fault the majority for following its analysis to this seemingly\n\nnonsensical result. For good judges must be willing to reach results that go against their\n\npreferences when those results are dictated by principles or precedent.\n\n But judges are also required to exercise restraint. Voiding an act of Congress is an\n\nextraordinary exercise of judicial power, and accordingly, such power should only be\n\ninvoked when it is incumbent upon us to do so. Here, the statute plausibly permits\n\nlooking directly at Simms’s conduct in pistol whipping a manager during a robbery in\n\ndetermining whether his conduct qualified as a crime of violence under the residual\n\n\n\n\nwould find themselves in the exact reverse position. These latter defendants, whose\nactual conduct did not create a substantial risk of violence, would be guilty when\nevaluated under the guise of a hypothetical ordinary case. Assuming it matters, I cannot\nas an empirical matter reasonably identify whether the former group is larger than the\nlatter. Cf. Dimaya, 138 S. Ct. at 1232 (Gorsuch, J., concurring in part and concurring in\njudgment) (rhetorically asking whether “a conviction for witness tampering ordinarily\ninvolve[s] a threat to the kneecaps or just the promise of a bribe”).\n Moreover, the concurrence’s characterization of what it means to “expand” a\nstatute’s reach is perverse. A judicially-imagined “ordinary case” can ensnare a\ndefendant whose actual conduct created no risk of violence, a result barred by the case-\nspecific approach. It is the “ordinary case” approach that expands the statute to cover\nhypothetical conduct imagined by a court. And this is why the “ordinary case” approach\nis unconstitutionally vague. A far more precise approach is to let juries determine guilt\nbased on the real actions taken by the defendant. See Harriss, 347 U.S. at 618 (noting the\nduty to make the “class of offenses . . . constitutionally definite”). It is entirely proper to\nreplace an unworkable, unconstitutionally vague interpretation with a readily-\ncomprehensible, textually-supported interpretation, even if that interpretation would\n“expand” liability by clarifying which conduct falls within the statute and which does not.\n\n 101\n\nclause. We are therefore required to adopt that reading. For these reasons, I respectfully\n\ndissent.\n\n\n\n\n 102", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4361701/", "author_raw": "RICHARDSON, Circuit Judge, with whom Judge QUATTLEBAUM joins, dissenting"}]}
GREGORY
WILKINSON
NIEMEYER
2
MOTZ; KING; DUNCAN; AGEE; KEENAN; WYNN; DIAZ; FLOYD; THACKER; HARRIS; RICHARDSON; QUATTLEBAUM
{}
8
0
4
2
2
null
https://www.courtlistener.com/api/rest/v4/clusters/4584448/
Published
1
1
0
0
1
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff-Appellee, v. Joseph Decore SIMMS, Defendant-Appellant. Fourth Circuit Federal Defender Offices, Amicus Supporting Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-24\nOpinion type: majority\nHas dissenting opinion: Yes\nHas concurring opinion: Yes\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 15-4640\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nJOSEPH DECORE SIMMS,\n\n Defendant - Appellant.\n\n------------------------------------------\n\nFOURTH CIRCUIT FEDERAL DEFENDER OFFICES,\n\n Amicus Supporting Appellant.\n\n\nAppeal from the United States District Court for the Eastern District of North Carolina, at\nGreenville. Terrence W. Boyle, Chief District Judge. (4:15-cr-00010-BO-1)\n\n\nArgued: September 26, 2018 Decided: January 24, 2019\n\n\nBefore GREGORY, Chief Judge, and WILKINSON, NIEMEYER, MOTZ, KING,\nDUNCAN, AGEE, KEENAN, WYNN, DIAZ, FLOYD, THACKER, HARRIS,\nRICHARDSON, and QUATTLEBAUM, Circuit Judges.\n\n\nReversed and remanded by published opinion. Judge Motz wrote the opinion, in which\nChief Judge Gregory and Judges King, Wynn, Diaz, Floyd, Thacker, and Harris joined.\n[END_CASE]", "role": "user" } ]
4,584,957
UNITED STATES of America, Plaintiff - Appellee, v. Johnny Sylvester EDGELL, Defendant - Appellant.
United States v. Johnny Edgell
2019-01-25
17-4432
U.S. Court of Appeals for the Fourth Circuit
{"judges": "Gregory, Niemeyer, Harris", "parties": "", "opinions": [{"author": "PAMELA HARRIS, Circuit Judge:", "type": "010combined", "text": "PUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4432\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nJOHNNY SYLVESTER EDGELL,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for Northern District of West Virginia, at\nClarksburg. Irene M. Keeley, Senior District Judge. (1:16-cr-00045-IMK-MJA-1)\n\n\nArgued: November 1, 2018 Decided: January 25, 2019\n\n\nBefore GREGORY, Chief Judge, NIEMEYER and HARRIS, Circuit Judges.\n\n\nSentence vacated and case remanded by published opinion. Judge Harris wrote the\nopinion, in which Chief Judge Gregory and Judge Niemeyer joined.\n\n\nARGUED: Linn Richard Walker, OFFICE OF THE FEDERAL PUBLIC DEFENDER,\nClarksburg, West Virginia, for Appellant. Stephen Donald Warner, OFFICE OF THE\nUNITED STATES ATTORNEY, Elkins, West Virginia, for Appellee. ON BRIEF:\nKristen M. Leddy, Research and Writing Specialist, OFFICE OF THE FEDERAL\nPUBLIC DEFENDER, Clarksburg, West Virginia, for Appellant. William J. Powell,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Wheeling,\nWest Virginia, for Appellee.\n\fPAMELA HARRIS, Circuit Judge:\n\n After negotiating a plea agreement with the government, Johnny Sylvester Edgell\n\npleaded guilty to one count of possessing a firearm as an unlawful drug user and one count\n\nof distributing methamphetamine. In exchange for that plea, the government agreed to a\n\nstipulation limiting Edgell’s total drug conduct to “less than five (5) grams of substances\n\ncontaining a detectable amount of methamphetamine,” J.A. 193, which corresponded to an\n\nadvisory sentencing range of 10 to 16 months’ imprisonment. But after the agreement was\n\nsigned, the government received lab results showing that the substances in question were\n\nactual methamphetamine, and once the government shared that information with the\n\nprobation office, Edgell’s sentencing range increased to 30 to 37 months. At sentencing,\n\nthe government advocated for a sentence consistent with that elevated range, and Edgell\n\nwas sentenced to 30 months in prison.\n\n Edgell contends that the government breached his plea agreement in two respects:\n\nfirst, by disclosing the post-plea lab report to the probation office and sentencing court; and\n\nsecond, by failing to honor the agreement at sentencing, and instead advocating for a\n\nsentence inconsistent with its original stipulation. We cannot agree that the government\n\nbreached its plea agreement by disclosing relevant and accurate information to the\n\nsentencing court. But we agree with Edgell that the government’s conduct at the sentencing\n\nhearing denied him the benefit of his bargain. Given the government’s breach, we vacate\n\nEdgell’s sentence and remand for resentencing before a different district judge.\n\n\n\n I.\n\n 2\n\f Following three controlled buys in July 2015, Johnny Sylvester Edgell was indicted\n\nby a federal grand jury on three counts of distributing methamphetamine, in violation of\n\n21 U.S.C. §§ 841(a)(1) and 841(b)(1)(C), and one count of unlawfully possessing a firearm,\n\nin violation of 18 U.S.C. §§ 922(g)(3) and 924(a)(2).\n\n Edgell and the government negotiated a plea agreement. For his part, Edgell agreed\n\nto plead guilty to the single firearm charge and to one count of distributing\n\nmethamphetamine. In exchange, the government agreed to a stipulation that Edgell’s drug\n\nconduct involved “less than five (5) grams of substances containing a detectable amount\n\nof methamphetamine” – that is, substances of a lower purity level than actual\n\nmethamphetamine. J.A. 193. Pursuant to that stipulation, Edgell’s advisory sentencing\n\nrange would be 10 to 16 months’ imprisonment. 1 The government additionally agreed to\n\n“recommend that any sentence of incarceration imposed . . . be at the lowest end of the\n\napplicable guideline range,” J.A. 193, and to dismiss the remaining counts of the\n\nindictment.\n\n The plea agreement also contained certain reservations. First, it specified that the\n\nsentencing court was not bound by the parties’ stipulations and was not required to accept\n\n\n\n 1\n While the plea agreement did not specify the resulting sentencing range, the parties\ndo not dispute that the agreement contemplated a range of 10 to 16 months’ imprisonment.\nThe agreement’s drug conduct stipulation produces a base offense level of 12. See\nU.S.S.G. § 2D1.1(c)(14). Considering the relevant adjustments – including a two-level\nenhancement for his possession of a dangerous weapon and a two-level reduction for\nacceptance of responsibility, see U.S.S.G. §§ 2D1.1(b)(1), 3E1.1 – and Edgell’s Category\nI criminal history, Edgell’s advisory sentencing range under the agreement indeed would\nhave been 10 to 16 months. See U.S.S.G. ch. 5, pt. A (sentencing table).\n\n\n 3\n\fthem. The agreement also reserved the government’s “right to provide to the Court and\n\nthe United States Probation Office . . . relevant information including defendant’s\n\nbackground, criminal record, offense charged in the indictment and other pertinent data . .\n\n. as will enable the Court to exercise its sentencing discretion,” and “to respond to any\n\nquestions raised by the Court, to correct any inaccuracies or inadequacies in the anticipated\n\npre-sentence report, and to respond to any written or oral statements made by the Court, by\n\ndefendant or his counsel.” J.A. 194.\n\n At the time the government entered into its agreement with Edgell, it had requested,\n\nbut not yet received, a laboratory analysis of the substances distributed by Edgell. When\n\nthat laboratory report was returned to the government – only after the agreement was\n\nfinalized – it revealed that the substances in question were not merely “substances\n\ncontaining a detectable amount of methamphetamine,” as the parties had stipulated, J.A.\n\n193, but instead actual methamphetamine. The government disclosed that information to\n\nthe probation office, which incorporated it into its Presentence Report (PSR), attributing\n\n3.5344 grams of actual methamphetamine to Edgell. As a result, the PSR calculated\n\nEdgell’s guidelines sentencing range as 30 to 37 months’ imprisonment, rather than the 10\n\nto 16 months anticipated under the plea agreement. 2 In light of that discrepancy, the PSR\n\nsuggested that a downward variance might be appropriate.\n\n\n\n\n 2\n Edgell’s new drug conduct resulted in an offense level of 20. See U.S.S.G. §\n2D1.1(c)(10). Edgell received a two-level enhancement for possessing a dangerous\nweapon under U.S.S.G. § 2D1.1(b)(1) and a three-level reduction for acceptance of\nresponsibility under U.S.S.G. § 3E1.1(b), for a total offense level of 19. Combined with\n(Continued)\n 4\n\f At sentencing, the district court acknowledged that the PSR’s factual findings and\n\nsentencing calculations were “certainly different from . . . the parties’ expectation from the\n\nplea agreement.” J.A. 91. Nevertheless, and without objection from either party, the court\n\nadopted the PSR’s advisory guidelines range of 30 to 37 months.\n\n Consistent with the PSR’s suggestion, Edgell requested a downward variance. The\n\ngovernment did not join Edgell’s request. Nor did it recommend a sentence consistent with\n\nthe agreed-upon stipulation as to drug conduct and the corresponding 10 to 16 months\n\nsentencing range. Instead, purporting to follow its commitments under the plea agreement,\n\nthe government advocated for a sentence at the “low end” of the guidelines range adopted\n\nby the court, or 30 months’ imprisonment. J.A. 108. The court followed the government’s\n\nrecommendation and sentenced Edgell to 30 months’ imprisonment, to be followed by a\n\nterm of three years of supervised release. Edgell timely appealed.\n\n\n\n II.\n\n Edgell contends the government breached its plea agreement by disclosing the post-\n\nagreement lab results to the probation office and the sentencing court, and by failing at\n\nsentencing to honor the agreement’s explicit drug conduct stipulation – that he was\n\nresponsible for distributing “less than five (5) grams of substances containing a detectable\n\namount of methamphetamine,” J.A. 193. Because Edgell did not challenge the\n\n\n\n\nhis Category I criminal history, the resulting sentencing range was 30 to 37 months’\nimprisonment. See U.S.S.G. ch. 5, pt. A (sentencing table).\n\n 5\n\fgovernment’s purported breach of the plea agreement before the district court, we review\n\nhis claim for plain error. United States v. Tate, 845 F.3d 571, 575 (4th Cir. 2017) (citing\n\nFed. R. Crim. P. 52(b)). Under that standard, Edgell must show that the government plainly\n\nbreached its plea agreement with him and that the breach both affected his substantial rights\n\nand called into question the fairness, integrity, or public reputation of judicial proceedings.\n\nSee United States v. Dawson, 587 F.3d 640, 645 (4th Cir. 2009). For the reasons given\n\nbelow, we find that Edgell has satisfied that demanding standard.\n\n A.\n\n We first consider whether the government breached the clear requirements of its\n\nplea agreement with Edgell. “Plea agreements are grounded in contract law,” and as with\n\nany contract, each party is entitled to receive the benefit of his bargain. Tate, 845 F.3d at\n\n575. While “we employ traditional principles of contract law as a guide” in enforcing plea\n\nagreements, “we nonetheless give plea agreements greater scrutiny than we would apply\n\nto a commercial contract because a defendant’s fundamental and constitutional rights are\n\nimplicated when he is induced to plead guilty by reason of a plea agreement.” United\n\nStates v. Warner, 820 F.3d 678, 683 (4th Cir. 2016) (internal quotation marks and brackets\n\nomitted). At a minimum, “when a plea rests in any significant degree on a promise or\n\nagreement of the prosecutor, so that it can be said to be part of the inducement or\n\nconsideration, such promise must be fulfilled.” Santobello v. New York, 404 U.S. 257, 262\n\n(1971).\n\n Here, Edgell maintains that his plea agreement rested on the government’s promise\n\nto limit his relevant drug conduct to “less than five (5) grams of substances containing a\n\n 6\n\fdetectable amount of methamphetamine,” J.A. 193, and the associated sentencing range,\n\nand that he was denied the benefit of his bargain when the government breached that\n\npromise. Specifically, Edgell challenges both the government’s disclosure of the post-\n\nagreement lab results to the probation office and sentencing court, and the government’s\n\nfailure at sentencing to defend or advocate in any way for the parties’ drug conduct\n\nstipulation. We address each of these challenges in turn.\n\n To the extent Edgell contends that the government breached its plea agreement by\n\ndisclosing lab results to the probation office and court, we must disagree. The government\n\nhas a “duty to furnish complete and accurate information at sentencing,” and we have\n\nexpressed doubt as to whether a plea agreement may abridge that duty. United States v.\n\nCrisp, 817 F.2d 256, 259 (4th Cir. 1987). Other courts of appeals, too, have emphasized\n\nthat even where a plea agreement binds the government to certain sentencing\n\nrecommendations, the government retains a duty “to ensure that the court has complete and\n\naccurate information, enabling the court to impose an appropriate sentence.” United States\n\nv. Maldonado, 215 F.3d 1046, 1052 (9th Cir. 2000); see also United States v. Casillas, 853\n\nF.3d 215, 218 (5th Cir. 2017) (government may not “stand mute in the face of factual\n\ninaccuracies or [] withhold relevant factual information from the court” (internal quotation\n\nmarks omitted)); United States v. Ubiles-Rosario, 867 F.3d 277, 283 (1st Cir. 2017) (“[A]\n\nplea agreement may not abridge the [government’s] solemn obligation to provide relevant\n\ninformation to the sentencing court.” (internal quotation marks omitted)).\n\n Indeed, consistent with this understanding, Edgell’s plea agreement does not purport\n\nto limit or override the government’s duty of candor to the court. Instead, it recognizes\n\n 7\n\fthat duty, and expressly reserves the government’s “right to provide to the Court and the\n\nUnited States Probation Office . . . relevant information including defendant’s background,\n\ncriminal record, offense charged in the indictment and other pertinent data . . . as will enable\n\nthe Court to exercise its sentencing discretion.” J.A. 194. The government’s disclosure of\n\nthe lab results, which went directly to the offense charged in the indictment and to Edgell’s\n\nbase offense calculation, was thus consistent with both the parties’ plea agreement and the\n\ngovernment’s broader duty to provide complete and accurate information to the sentencing\n\ncourt.\n\n But the government did more than that here. And we agree with Edgell that the\n\ngovernment crossed the line and breached its plea agreement when it failed at sentencing\n\nto honor its drug conduct stipulation. As one court of appeals to consider this precise\n\nquestion has explained, “Although the Government has a duty to provide the sentencing\n\ncourt with relevant factual information and to correct misstatements, it may not hide behind\n\nthis duty to advocate a position that contradicts its promises in a plea agreement.” United\n\nStates v. Munoz, 408 F.3d 222, 227 (5th Cir. 2005). Instead, the government must carefully\n\nbalance its duty of candor to the sentencing court with the sometimes competing – but\n\nequally solemn – duty to honor its commitments under a plea agreement. See United States\n\nv. Saxena, 229 F.3d 1, 5 (1st Cir. 2000). And as courts that have addressed the question\n\nagree, this balance is achieved where the government makes the necessary disclosures to\n\nthe sentencing court, but nevertheless “continue[s] to advocate for acceptance of the\n\nagreement.” Casillas, 853 F.3d at 218; see also United States v. Franco–Lopez, 312 F.3d\n\n984, 993 (9th Cir. 2002) (“We conclude that the government did not breach the plea\n\n 8\n\fagreement by providing information to the Probation Department regarding [the\n\ndefendant’s] criminal activity while recommending successfully to the district court that it\n\nnot rely on that information in sentencing.”); Saxena, 229 F.3d at 7 (finding no breach\n\nwhere the government disclosed information inconsistent with the plea agreement, but\n\nnevertheless “resolutely stood by the bottom-line recommendation that [it] had committed\n\nto make”).\n\n The government failed to strike the necessary balance here. At sentencing, the\n\ngovernment did not “continue to advocate for acceptance,” Casillas, 853 F.3d at 218, of its\n\nagreement with Edgell. It did not ask the court to impose a sentence consistent with the 10\n\nto 16 months range that corresponded to its drug conduct stipulation. It did not join in\n\nEdgell’s request for a downward variance. And it did not otherwise encourage the court to\n\nconsider in any way the factual stipulation to which it agreed in exchange for Edgell’s\n\nguilty plea. Instead, the government affirmatively undermined the plea agreement by\n\nrequesting a sentence inconsistent with its stipulation, effectively tripling its recommended\n\nsentence from the 10 months anticipated under the plea agreement to the 30 months at the\n\nlow end of the post-lab report range calculated by the PSR. 3\n\n\n 3\n We appreciate the awkward situation the government faced at sentencing;\nbalancing the competing duties of candor to the court and adherence to a plea agreement\ncan be a difficult task under circumstances like these. But this is not the first case in which\na prosecutor was required to walk that line. In United States v. Saxena, 229 F.3d 1, 4 (1st\nCir. 2000), for instance, the government had agreed in a plea agreement to recommend a\nsentence of 24 months’ imprisonment, consistent with an anticipated sentencing range of\n24 to 30 months. At sentencing, however, it disclosed to the court post-plea activities by\nthe defendant that led the court to adopt a higher guidelines range of 33 to 41 months. Id.\nat 4–5. But when it came time to make a sentencing recommendation, the prosecutor\n(Continued)\n 9\n\f At oral argument, the government suggested for the first time that its sentencing\n\nrecommendation did not breach the plea agreement because Edgell “assumed the risk” that\n\nit would discover the actual nature of the substances he distributed. But it was the\n\ngovernment, of course, that knew of an outstanding lab report and nevertheless decided to\n\ngo forward with the plea agreement without waiting for the results, thus assuming precisely\n\nthe risk that materialized: that the lab report ultimately would come back with information\n\ninconsistent with the agreement’s drug conduct stipulation. The government’s apparent\n\nmisjudgment about the importance of the lab report is not grounds for relieving the\n\ngovernment of its obligations under the plea agreement.\n\n Moreover, the government’s assumption-of-risk argument misconstrues the very\n\nnature of plea agreements. Plea agreements, as any contract, bind one party to do\n\nsomething the other party desires in exchange for some benefit. United States v. Bownes,\n\n405 F.3d 634, 636 (7th Cir. 2005). Here, the government agreed to the drug conduct\n\nstipulation, which came with a corresponding sentencing range of 10 to 16 months, and to\n\n\ncontinued to advocate for the 24 months to which the parties had agreed, explaining to the\ncourt:\n\n The government’s recommendation in this case is pursuant to our plea\n agreement. And I’m well aware, your Honor, of the fact that my\n recommendation is below what the Court has determined the guidelines\n applicable to be. Nonetheless, bound by that agreement the government does\n recommend a sentence of 24 months which, of course, was based on the\n calculations [of] the parties.\n\nId. at 7. Because it “resolutely stood by” a sentencing recommendation consistent with its\nplea agreement, the First Circuit concluded in Saxena, the government had not breached\nthe agreement, notwithstanding its disclosure of post-plea information to the court. Id. at\n7–8.\n\n 10\n\frecommend a sentence at the bottom of the applicable range. In return, Edgell relieved the\n\ngovernment of its burden to prove his guilt beyond a reasonable doubt and eliminated the\n\nneed for the government to expend its resources on a full criminal trial. Both parties bound\n\nthemselves to their respective commitments, and each “assume[d] the risk of future\n\nchanges in circumstances in light of which [their] bargain may prove to have been a bad\n\none.” Id. Just as we often enforce plea agreements against criminal defendants even in the\n\nface of subsequent, favorable changes in the law, see, e.g., United States v. Archie, 771\n\nF.3d 217, 222 (4th Cir. 2014), so, too, must we enforce plea agreements that may later\n\nprove less advantageous than the government had anticipated.\n\n The government’s failure at sentencing to stand by its drug conduct stipulation, and\n\nits recommendation of a sentence inconsistent with that stipulation, denied Edgell a central\n\nbenefit of his bargain. It follows that the government breached its plea agreement with\n\nEdgell. See Santobello, 404 U.S. at 262. And because the government’s duties pursuant\n\nto the plea agreement were sufficiently clear – that is, the drug conduct stipulation was\n\nunambiguous – that error was plain. Cf. Puckett v. United States, 556 U.S. 129, 143 (2009)\n\n(“Not all breaches [of plea agreements] will be clear or obvious. Plea agreements are not\n\nalways models of draftsmanship, so the scope of the Government’s commitments will on\n\noccasion be open to doubt.”). Edgell therefore satisfies the initial requirements of plain\n\nerror review.\n\n B.\n\n Having found that the government plainly breached its plea agreement at\n\nsentencing, we next consider whether that breach affected Edgell’s substantial rights. A\n\n 11\n\fbreach of a plea agreement affects a defendant’s substantial rights only if it prejudices the\n\ndefendant. Puckett, 556 U.S. at 135. And a defendant suffers no prejudice where (1) he\n\nobtained the benefits of the plea agreement despite the government’s breach – that is, where\n\nhe nevertheless received the sentence the prosecutor promised to request – or (2) “he likely\n\nwould not have obtained those benefits in any event.” Id. at 141–42. Where the record\n\ndoes not reflect either of the above circumstances, “we are free to conclude that the\n\ndefendant has shown a reasonable probability, based on the appellate record as a whole,\n\nthat but for the error he would have received a more favorable sentence.” Dawson, 587\n\nF.3d at 645 (internal quotation marks omitted).\n\n Edgell has made the requisite showing of potential prejudice. First, there is no\n\nquestion that Edgell did not receive the benefit of his bargain: He was sentenced to 30\n\nmonths’ imprisonment, a sentence that far exceeded the sentencing range that would have\n\nresulted from the drug conduct stipulation in the parties’ plea agreement. Second, we\n\ncannot conclude from this record that, had the government honored the plea agreement,\n\nthere would have been no benefit to Edgell. It is true that, under the plea agreement, the\n\nsentencing court was not bound by the parties’ stipulation, 4 and the court did voice a\n\n\n\n\n 4\n That the court was not bound by the drug conduct stipulation, of course, does not\nexcuse the government from its commitments under the agreement. The parties “did intend\nfor the stipulation to bind the government, and it is the government’s breach of that\nagreement that is the focus of our inquiry.” United States v. Boatner, 966 F.2d 1575, 1579\n(11th Cir. 1992); see also United States v. Normil, 129 F.3d 1261, at *4 (4th Cir. 1997)\n(unpublished table decision) (“To the extent that a stipulation entered by the government\nis essential to the defendant’s bargain, it is binding. This is true even if the court is not\nbound by the stipulation.” (citation omitted)).\n\n 12\n\fconcern that the plea agreement – and the sentencing range it contemplated – did not\n\naccount for the severity of Edgell’s offenses. But at the same time, the district court made\n\nclear that it was considering a sentence well below the 30 to 37 months range it had\n\nadopted. And in the end, it adopted precisely the sentence the government recommended:\n\n30 months. Had the government instead urged the court to impose a sentence consistent\n\nwith its plea agreement, or joined in Edgell’s request for a downward variance, then the\n\ncourt may well have taken the government’s position into account and arrived at a sentence\n\nwithin, or at least closer to, the sentencing range anticipated by the plea agreement. Edgell\n\nthus has “demonstrated a reasonable probability that the outcome of his sentencing would\n\nhave been different had the government made the appropriate recommendation.” Dawson,\n\n587 F.3d at 646; cf. United States v. Navarro, 817 F.3d 494, 501 (7th Cir. 2016) (“[C]ases\n\nwhere we have found that the defendant failed to prove the prejudice prong are ones in\n\nwhich the record compellingly reflects the sentencing court was not influenced by the\n\ngovernment’s recommendation.”). Accordingly, we find that the government’s breach of\n\nthe plea agreement affected Edgell’s substantial rights.\n\n C.\n\n We similarly find that the government’s breach of the plea agreement seriously\n\naffected the “fairness, integrity, or public reputation of judicial proceedings,” Puckett, 556\n\nU.S. at 135 (internal quotation marks omitted). The Supreme Court has cautioned that this\n\nprong of plain error “is meant to be applied on a case-specific and fact-intensive basis,”\n\nand is not automatically satisfied whenever the government breaches a plea agreement. Id.\n\nat 142–43. “Nevertheless, . . . courts have recognized that the Government’s breach of a\n\n 13\n\fplea agreement constitutes a particularly egregious error that, in the absence of strong\n\ncountervailing factors, seriously affects the fairness, integrity, or public reputation of\n\njudicial proceedings.” United States v. Kirkland, 851 F.3d 499, 505 (5th Cir. 2017)\n\n(emphasis added) (collecting cases). This is so because “[t]he breach of a promise made\n\nto induce a defendant to enter a guilty plea – and thereby waive important constitutional\n\nrights – harms not only the defendant, but . . . involves the honor of the government, [and]\n\npublic confidence in the fair administration of justice.” United States v. Lewis, 633 F.3d\n\n262, 269 (4th Cir. 2011) (internal quotation marks omitted); see also United States v.\n\nPeglera, 33 F.3d 412, 414 (4th Cir. 1994) (“Because a government that lives up to its\n\ncommitments is the essence of liberty under law, the harm generated by allowing the\n\ngovernment to forego its plea bargain obligations is one which cannot be tolerated.”).\n\n Here, the government does not contest that its purported breach affects the integrity,\n\nfairness, or public reputation of plea agreements and judicial proceedings generally.\n\nAccordingly, because Edgell has shown the government failed to honor its clear\n\ncommitments under his plea agreement and the government fails to provide even a single\n\ncountervailing factor, we find Edgell has satisfied the final requirement of plain error\n\nreview.\n\n\n\n III.\n\n Having found that the government breached the plea agreement and that the breach\n\nconstitutes plain and reversible error, the only remaining issue is the appropriate remedy.\n\n“In most cases in which the Government has breached its agreement with the defendant,\n\n 14\n\fwe prefer to leave the fashioning of appropriate relief to the sound discretion of the district\n\ncourt.” United States v. Wood, 378 F.3d 342, 350 n.6 (4th Cir. 2004) (internal quotation\n\nmarks omitted). Where, however, the defendant does not seek to withdraw his guilty plea\n\nand instead requests only “the lesser relief of specific performance of the agreement[,] . . .\n\nthen the court should honor that election,” and “remand with the direction that the\n\ndefendant ‘be resentenced by a different judge.’” Warner, 820 F.3d at 685 (quoting\n\nSantobello, 404 U.S. at 263). 5\n\n Because Edgell seeks only specific performance, we will honor his election.\n\n\n\n IV.\n\n For the foregoing reasons, we find the government breached its plea agreement with\n\nEdgell and that this breach constitutes reversible plain error. We do not doubt that the\n\ngovernment’s breach was the result of inadvertence rather than bad faith, but Edgell\n\nnonetheless was denied the benefit of his bargain. Accordingly, we vacate Edgell’s\n\nsentence and remand the case for resentencing before a different district judge.\n\n\n\n SENTENCE VACATED AND CASE REMANDED\n\n\n\n 5\n When specific performance is elected by a defendant, resentencing always takes\nplace before a different judge. See Peglera, 33 F.3d at 415 (“We remand the case to a\ndifferent district judge for resentencing as we are required to do.”) As the Supreme Court\nhas emphasized, that standard remedy “is in no sense to question the fairness of the\nsentencing judge,” Santobello, 404 U.S. at 263, and our decision today should not be\nunderstood as a “reflection on [Edgell’s] trial judge, who handled the case admirably under\nthe circumstances,” Peglera, 33 F.3d at 415.\n\n 15", "resource_uri": "https://www.courtlistener.com/api/rest/v4/opinions/4362210/", "author_raw": "PAMELA HARRIS, Circuit Judge:"}]}
GREGORY
NIEMEYER
HARRIS
1
{}
1
0
0
0
1
null
https://www.courtlistener.com/api/rest/v4/clusters/4584957/
Published
1
0
0
0
0
2,019
1
[ { "content": "You are an expert legal coding assistant trained to classify U.S. federal Courts of Appeals\ncases using an adaptation of the Supreme Court Database (SCDB_2023_01) codebook. You follow the coding procedure\nin the codebook step by step and use the precise definitions of terms presented in the codebook below.\n\nYour task: Given metadata and text for a single federal appellate case, output a single JSON\nobject that encodes the following variables:\n\n- Petitioner (name, description, and general category)\n- Respondent (name, description, and general category)\n- Disposition of Case\n- Winning Party\n- Issue Area\n- Legal Provisions\n- Decision Direction\n- Lower Court Direction\n- Declaration of Unconstitutionality\n- Method (panel, en banc, or rehearing)\n- Who Appealed (original plaintiff vs. defendant)\n- Dissent Basis (procedural vs. merits — only if dissent exists)\n- Concurrence Type (regular vs. special/result-only — only if concurrence exists)\n- Concurrence Basis (procedural vs. merits — only if concurrence exists)\n\nYou are working with U.S. Courts of Appeals, not the Supreme Court. Apply the SCDB coding\nrules as closely as possible, treating the **Court of Appeals as \"the Court\"** and assuming\nthat the **lower court is, e.g., a federal district court** whose decision is being reviewed.\n\nTo encode these variables, start by determining the petitioner and respondent, following the\ninstructions in Section 3.1. Then, find the disposition of the case and code it according\nto Section 3.2. Knowing the disposition will guide your next step: determining if the petitioner\nwas the winning party, following the directions in Section 3.3. Next, use the overall opinion content\nto code the issue area as described in Section 3.4. This step will also inform the legal provisions\ncoding as laid out in Section 3.5. With the winning party, disposition, and issue area fixed,\ncarefully and precisely follow the directions in Section 3.6 to assign a decision direction for the opinion.\nBased on that decision direction and the disposition, you can assign a lower court direction as well,\nfollowing Section 3.7. Finally, justify your decisions in the manner described below.\n\n==================================================\n1. INPUT FORMAT\n==================================================\n\nYou will receive input in two sections:\n\n[CASE_METADATA]\nCase name: <case name as in the caption>\nCourt: <name of the Court of Appeals, e.g. \"United States Court of Appeals for the Ninth Circuit\">\nDate decided: <YYYY-MM-DD or best approximation>\nOpinion type: <e.g. \"majority\", \"per curiam\", \"on-the-merits\", \"rehearing\", \"en banc\", etc.>\nHas dissenting opinion: <Yes or No, based on whether the input data contains a separate dissent>\nHas concurring opinion: <Yes or No, based on whether the input data contains a separate concurrence>\nAdditional notes: <any other metadata or summary, if provided>\n\n[CASE_TEXT]\n<full or excerpted opinion text here>\n[END_CASE]\n\nUse both metadata and text to code the variables. If metadata and text conflict, prefer the\nsubstantive discussion in the opinion.\n\n==================================================\n2. OUTPUT FORMAT\n==================================================\n\nYou must output ONLY a single JSON object with exactly these keys:\n\n- \"petitioner\"\n- \"respondent\"\n- \"case_disposition\"\n- \"winning_party\"\n- \"issue_area\"\n- \"legal_provisions\"\n- \"decision_direction\"\n- \"lower_court_direction\"\n- \"declaration_of_unconstitutionality\"\n- \"method\"\n- \"who_appealed\"\n- \"dissent_basis\" (only if the case has a dissenting opinion)\n- \"concurrence_type\" (only if the case has a concurring opinion)\n- \"concurrence_basis\" (only if the case has a concurring opinion)\n- \"justification\"\n\nSchema:\n\n- \"petitioner\": {\n \"name\": string, // short party name from caption; usually the appellant\n \"description\": string, // role and identity, e.g. \"federal criminal defendant appealing conviction\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"respondent\": {\n \"name\": string,\n \"description\": string, // e.g. \"United States as appellee\", \"private employer\", \"federal agency\"\n \"category\": integer, // 1–7 general litigant type (see Section 3.1)\n \"category_label\": string // label for the category code\n }\n\n- \"case_disposition\": {\n \"code\": integer, // must be one of the codes below\n \"label\": string\n }\n\n- \"winning_party\": {\n \"code\": integer, // 0, 1, or 2 as defined below\n \"label\": string\n }\n\n- \"issue_area\": {\n \"code\": integer, // 1–14 from the list below\n \"label\": string // short description of the main issue area\n }\n\n- \"issue_area_alt\": {\n \"code\": integer, // 1–14; your best non-Misc alternative if issue_area.code == 13, else same as issue_area.code\n \"label\": string\n }\n\n- \"legal_provisions\": [\n {\n \"area_code\": integer, // 1–9 (law area codes below)\n \"area_label\": string,\n \"provision_text\": string // e.g. \"Fourth Amendment, search and seizure\", \"18 U.S.C. § 924(c)\"\n },\n ...\n ]\n\n- \"decision_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"lower_court_direction\": {\n \"code\": integer, // 1, 2, or 3 as defined below\n \"label\": string\n }\n\n- \"declaration_of_unconstitutionality\": {\n \"code\": integer, // 0 or 1 (see Section 3.8)\n \"label\": string // \"no\" or \"yes\"\n }\n\n- \"method\": {\n \"code\": integer, // 1–4 (see Section 3.9)\n \"label\": string\n }\n\n- \"who_appealed\": {\n \"code\": integer, // 1–4 (see Section 3.10)\n \"label\": string\n }\n\n- \"dissent_basis\": { // ONLY include if \"Has dissenting opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"concurrence_type\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"code\": integer, // 1–3 (see Section 3.12)\n \"label\": string\n }\n\n- \"concurrence_basis\": { // ONLY include if \"Has concurring opinion: Yes\" in metadata\n \"procedural\": integer, // 0–3 (see Section 3.11)\n \"merits\": integer // 0–3 (see Section 3.11)\n }\n\n- \"justification\": string // 2–4 sentences summarizing why you chose these codes.\n // You MUST explicitly say: (a) who won and why, (b) what issue_area.code is,\n // (c) how that combination implied the decision_direction.code you chose, and\n // (d) why the lower_court_direction is the same as or opposite to decision_direction.\n\nYour entire response must be exactly one JSON object in this schema and nothing else.\n\n==================================================\n3. VARIABLE INTERPRETATION\n==================================================\n\n3.1 Petitioner and Respondent\n\n- Use the case caption, opinion type, and text to determine who is appealing.\n- Petitioner = the party seeking relief in the Court of Appeals (typically the appellant).\n- Respondent = the party opposing the appeal (typically the appellee).\n- The \"name\" should be a reasonably short label from the caption.\n- The \"description\" should describe their role and identity (e.g., \"federal prisoner challenging sentence\",\n \"state official in civil-rights suit\", \"private corporation defendant\", \"federal agency\").\n\nFor each party, also assign a \"category\" code using this 7-category typology:\n\n1 = private business or corporation (including partnerships, sole proprietorships)\n2 = nonprofit organization, interest group, or union (as an institutional party)\n3 = federal government (including U.S. as party, federal agencies like DOJ, IRS, EPA, SEC, NLRB, etc.)\n4 = sub-state government (city, county, municipality, school district, local official)\n5 = state government (state, governor, state agency, state official in official capacity)\n6 = tribal government or Indian nation\n7 = natural person (individual, including pro se litigants and individual officials sued personally)\n\nChoose the category based on who the party IS, not what kind of case it is. When a government\nofficial is sued in their official capacity, code them as the relevant government level (3, 4, or 5).\nWhen sued in their personal/individual capacity, code them as 7 (natural person).\n\n\n3.2 Disposition of Case\n\nCodes (Songer-style numbering):\n\n1 = affirmed (includes modified and affirmed)\n2 = reversed\n3 = reversed and remanded\n4 = vacated and remanded\n5 = affirmed in part, reversed (or vacated) in part\n6 = affirmed in part, reversed (or vacated) in part, and remanded\n7 = vacated\n8 = petition denied or appeal dismissed\n9 = stay, petition, or motion granted\n10 = certification to or from a lower court\n11 = affirmed, vacated, and remanded (without reversal)\n0 = no disposition\n\n- Use the text and opinion type (majority, rehearing, etc.) to identify what the Court of Appeals actually did.\n- Only choose options 3, 4, or 6 if the opinion contains explicit instructions to remand the matter to the lower court\n or original authority (the word \"remand\" must appear in the opinion text).\n- For rehearing petitions, be explicit about whether the petition is granted (9), denied (8), or leads to modification\n or vacatur (7) of the prior judgment.\n- If the Court takes no substantive action on the merits (e.g., purely procedural opinion), use 0 (\"no disposition\").\n\n\n3.3 Winning Party\n\nCodes:\n\n0 = no favorable disposition for petitioning party apparent\n1 = petitioning party received a favorable disposition\n2 = favorable disposition for petitioning party unclear\n\n- Treat the **petitioner** as the party seeking relief in the Court of Appeals.\n- A \"favorable disposition\" is one that materially improves the petitioner's position relative to the lower court judgment\n (e.g., reversal, vacatur, remand requiring relief, sentence reduction).\n- For mixed outcomes (e.g., affirmed in part and reversed in part), assess whether, on balance, the petitioner is better off.\n If clearly better off, use 1; if clearly not better off, use 0; if ambiguous, use 2.\n- Note that an outcome favoring the petitioning party may be either an affirmation (if the lower court had ruled in favor of the petitioner)\n OR a reversal (if the lower court had ruled against the petitioner). You should focus on whether the petitioner is better off,\n regardless of the case disposition.\n\n\n3.4 Issue Area\n\nChoose exactly one code and label from this list, based on the main legal/policy issue in the appeal:\n\n1 = Criminal Procedure\n (e.g., search and seizure, arrest, interrogation, right to counsel, trial and sentencing rules, habeas)\n\n2 = Civil Rights\n (e.g., equal protection, discrimination based on race or other protected traits, voting rights, school desegregation)\n\n3 = First Amendment\n (e.g., freedom of speech, press, association, religion, and related expression claims)\n\n4 = Due Process\n (e.g., non-criminal procedural fairness, property or liberty deprivations, economic regulation challenges framed as due process)\n\n5 = Privacy\n (e.g., contraception, abortion, family relationships, intimate or sexual privacy, personal autonomy)\n\n6 = Attorneys\n (e.g., attorney's fees, sanctions, bar admission and discipline, representation issues)\n\n7 = Unions\n (e.g., labor relations, union membership and internal affairs, collective bargaining, union security)\n\n8 = Economic Activity\n (e.g., antitrust, securities, regulation of business, commercial law, bankruptcy, financial regulation)\n\n9 = Judicial Power\n (e.g., jurisdiction, standing, mootness, justiciability, sovereign immunity, standards of review, appellate procedure)\n\n10 = Federalism\n (e.g., conflicts between federal and state authority, preemption, Tenth Amendment issues, state sovereign immunity vs federal power)\n\n11 = Interstate Relations\n (e.g., disputes between states, boundary and water disputes, interstate compacts and obligations)\n\n12 = Federal Taxation\n (e.g., federal income, corporate, estate, excise, and other federal tax issues)\n\n13 = Miscellaneous\n (cases that genuinely do not fit any other issue area — see IMPORTANT note below)\n\n14 = Private Action\n (e.g., private law disputes in property, contracts, torts, wills, estates, and similar matters)\n\nPick the **single best** issue area based on what the Court of Appeals treats as the central question.\nIf multiple areas appear, choose the one most emphasized in the reasoning.\n\nIMPORTANT — AVOID MISCELLANEOUS (13):\n\nCode 13 should be used ONLY as a genuine last resort when NO other category applies even\napproximately. Before choosing 13, reconsider the following common mappings:\n\n - Medical malpractice, products liability, personal injury, breach of contract,\n admiralty, property disputes → 14 (Private Action)\n - Workers' compensation (LHWCA, FELA, Longshore Act) → 7 (Unions) or 14 (Private Action)\n - Bankruptcy, securities, antitrust, business regulation → 8 (Economic Activity)\n - Social Security, disability, welfare benefits → 2 (Civil Rights)\n - Attorneys' fees, bar discipline → 6 (Attorneys)\n - Federal preemption of state law → 10 (Federalism)\n - Procedural rehearing or jurisdictional questions → 9 (Judicial Power)\n - Separation of powers, legislative veto → 13 (Miscellaneous) — this is a genuine use\n\nIf you DO choose issue_area.code = 13, you MUST also fill in \"issue_area_alt\" with your\nbest-guess alternative code (the closest non-Misc category). If issue_area.code is not 13,\nset \"issue_area_alt\" to the same code and label as \"issue_area\".\n\nISSUE AREA TIEBREAKING RULES:\n\nWhen a case implicates more than one issue area, apply these rules to select the primary one:\n\n- Criminal Procedure (1) vs. Civil Rights (2): If the court's holding concerns criminal\n conviction, sentencing, or procedure itself (e.g., suppression of evidence, habeas review of\n a conviction), use 1 even if discrimination or civil-rights statutes are mentioned. Use 2\n only when the holding primarily addresses whether discriminatory treatment occurred or whether\n a civil-rights statute was violated.\n\n- Criminal Procedure (1) vs. Due Process (4): If the party is a criminal defendant raising\n due-process claims about trial procedure, sentencing, or conditions of confinement, use 1.\n Use 4 only when the due-process claim arises in a non-criminal context (e.g., government\n termination of benefits, property seizure in a civil case).\n\n- Judicial Power (9) vs. any other area: Many cases discuss jurisdiction, standing, or\n justiciability before reaching the merits. Use 9 ONLY when the court's holding is\n primarily about whether it has the power to hear the case — i.e., the court resolves a\n jurisdictional or justiciability question and that resolution IS the outcome. If the court\n establishes jurisdiction and then rules on the merits, use the substantive merits area instead.\n\n- Economic Activity (8) vs. Federalism (10): If the holding is about whether a federal\n statute preempts state regulation, use 10. If the holding is about the substance of a\n federal regulatory scheme (e.g., upholding or striking down an EPA rule on the merits),\n use 8.\n\n- Civil Rights (2) vs. Due Process (4): If the claim involves alleged discrimination under\n equal protection or a civil-rights statute, use 2. Use 4 only when the claim is about\n procedural fairness or property/liberty deprivation without an underlying discrimination\n allegation.\n\n\n3.5 Legal Provisions\n\nFor each major legal provision the Court of Appeals applies or interprets, add an entry to \"legal_provisions\".\n\nLaw Area codes (SCDB varLawArea):\n\n1 = Constitution (original text)\n An Article or Section of the original Constitution (not an Amendment).\n Examples: Article I (congressional power), Article II (executive power),\n Article III (judicial power), Supremacy Clause, Commerce Clause, Full Faith\n and Credit Clause, Contracts Clause.\n\n2 = Constitutional Amendment\n Any Amendment to the Constitution, including the Bill of Rights.\n Examples: First Amendment (speech, religion), Fourth Amendment (search and\n seizure), Fifth Amendment (due process, takings, self-incrimination), Sixth\n Amendment (right to counsel, jury trial), Eighth Amendment (cruel and unusual\n punishment), Fourteenth Amendment (equal protection, due process).\n\n3 = Federal Statute\n A statute enacted by Congress, cited by title and section of the U.S. Code or\n by its popular name. This is the most common category.\n Examples: 42 U.S.C. § 1983 (civil rights), 28 U.S.C. § 1331 (federal question\n jurisdiction), Title VII of the Civil Rights Act, Sherman Act § 1 (antitrust),\n 18 U.S.C. § 924(c) (firearms), ERISA, CERCLA, ADA, FOIA, Sentencing Guidelines.\n\n4 = Court Rules\n Federal Rules of Civil Procedure, Criminal Procedure, Evidence, or Appellate\n Procedure, as well as local circuit rules.\n Examples: Fed. R. Civ. P. 12(b)(6) (failure to state a claim), Fed. R. Civ. P.\n 56 (summary judgment), Fed. R. Crim. P. 11 (plea agreements), Fed. R. Evid. 403\n (prejudicial evidence).\n\n5 = Other\n Common law doctrines, equitable principles, or other legal authorities not fitting\n the categories above.\n Examples: common law fraud, maritime law (general), equitable estoppel, doctrine\n of laches, implied contracts.\n\n6 = Infrequently litigated statutes\n Federal statutes that appear rarely in appellate litigation and are not well-known\n by popular name. Use this when the statute is obscure or highly specialized.\n Examples: Railway Labor Act, Packers and Stockyards Act, Suits in Admiralty Act,\n obscure provisions of the Internal Revenue Code.\n\n8 = State or local law or regulation\n A state statute, state constitutional provision, local ordinance, or state/local\n regulation. Use this when the court applies or interprets state or local law rather\n than federal law.\n Examples: state tort law, state contract law, state criminal statute, local zoning\n ordinance, state environmental regulation.\n\n9 = No Legal Provision\n The opinion does not meaningfully rely on any identifiable legal provision. Very\n rare — use only when the court's analysis is purely factual or procedural without\n citing specific legal authority.\n\nFor each entry:\n- `area_code`: choose the single best area for the provision.\n- `area_label`: the corresponding label (e.g., \"Constitution\", \"Federal Statute\").\n- `provision_text`: identify the specific provision (e.g., \"Fourth Amendment, search and seizure\",\n \"42 U.S.C. § 1983\", \"Federal Rule of Civil Procedure 12(b)(6)\", \"state tort law\").\n\nInclude the one to three provisions central to the court's analysis. If the opinion does not meaningfully\nrely on any legal provision (very rare), use a single entry with area_code 9 and a brief explanation.\n\nDistinguishing area codes:\n- If the court interprets the CONSTITUTION ITSELF (e.g., Commerce Clause), use 1.\n- If the court interprets a CONSTITUTIONAL AMENDMENT (e.g., Fourth Amendment), use 2.\n- If the court interprets a FEDERAL STATUTE (the most common scenario), use 3.\n- If the dispute is about a PROCEDURAL RULE (e.g., Rule 12(b)(6) motion), use 4.\n- Use 8 for STATE LAW even if the case is in federal court on diversity jurisdiction.\n- Use 5 for common law doctrines that are not codified in any statute or rule.\n- Use 6 only for genuinely obscure federal statutes that would not be recognized by name.\n\n\n3.6 Decision Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\n>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>\nCRITICAL: The codes \"conservative\" and \"liberal\" are MECHANICAL LABELS defined by the SCDB\ncodebook. They are NOT your own assessment of political ideology. You MUST apply them exactly\nas the lookup table below specifies, even when the result seems counterintuitive. For example,\na decision favoring a taxpayer over the IRS is ALWAYS coded conservative (1) in a Federal\nTaxation case, regardless of the policy context. A decision upholding a government regulation\nis ALWAYS coded liberal (2) in an Economic Activity case, even if the regulation benefits\nbusiness. Do NOT let your general understanding of politics override these rules.\n<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<\n\nDIRECTION LOOKUP TABLE — apply mechanically based on issue_area.code and who benefits:\n\nissue_area.code | benefiting side | direction\n----------------|------------------------------------------------------------|----------\n1 (Crim. Pro.) | accused / convicted person / criminal defendant | 2 (liberal)\n1 (Crim. Pro.) | prosecution / law enforcement / government | 1 (conservative)\n2 (Civ. Rts.) | civil rights or civil liberties claimant | 2 (liberal)\n2 (Civ. Rts.) | government defendant / party opposing civil rights claim | 1 (conservative)\n3 (1st Amend.) | person asserting First Amendment protections | 2 (liberal)\n3 (1st Amend.) | government restricting speech, press, religion, etc. | 1 (conservative)\n4 (Due Proc.) | individual challenging deprivation of liberty or property | 2 (liberal)\n4 (Due Proc.) | government upholding deprivation | 1 (conservative)\n5 (Privacy) | person asserting privacy / autonomy / reproductive choice | 2 (liberal)\n5 (Privacy) | government restricting privacy or autonomy | 1 (conservative)\n7 (Unions) | union / workers / collective bargaining interests | 2 (liberal)\n7 (Unions) | employer / management / anti-union interests | 1 (conservative)\n8 (Econ. Act.) | workers, consumers, injured parties, environment, govt | 2 (liberal)\n | regulation, or small entities against large business |\n8 (Econ. Act.) | employers, large business, property owners, deregulation | 1 (conservative)\n9 (Jud. Power) | broader court access / standing / review | 2 (liberal)\n9 (Jud. Power) | narrower court access / standing / review | 1 (conservative)\n10 (Federalism) | federal authority over state authority | 2 (liberal)\n10 (Federalism) | state sovereignty over federal power | 1 (conservative)\n12 (Fed. Tax.) | United States / IRS / federal taxing authority | 2 (liberal)\n12 (Fed. Tax.) | taxpayer | 1 (conservative)\n11,14 | use 3 (unspecifiable) unless decision clearly aligns | 3 (unspecifiable)\n | with one of the patterns above |\n\nPROCEDURE: You MUST FIRST determine who won the case (winning_party), THEN identify the\nissue_area, and LAST look up the decision_direction from the table above by matching the\nissue_area.code with the side that benefited. Do NOT reason about direction from first\nprinciples — use the table.\n\nIf, after applying the table, you cannot determine which side benefited, use 3 (unspecifiable).\n\n\n3.6.1 Worked Examples\n\nThe following three examples demonstrate correct mechanical application of the direction\nlookup table, including cases where the SCDB coding may seem counterintuitive:\n\nEXAMPLE A — Federal Taxation (issue_area.code = 12)\n\n Facts: A taxpayer appeals an IRS assessment to the Court of Appeals. The court reverses the\n Tax Court, holding that the taxpayer's deductions were proper and the assessment was incorrect.\n\n Coding:\n issue_area.code = 12 (Federal Taxation)\n winning_party.code = 1 (petitioner/taxpayer received favorable disposition)\n decision_direction = 1 (conservative) ← taxpayer won; lookup table row for code 12\n says \"taxpayer → 1 (conservative)\"\n\n NOTE: Even though the taxpayer prevailed against the government, the SCDB mechanically\n codes this as conservative (1) because the taxpayer benefited.\n\n\nEXAMPLE B — Criminal Procedure (issue_area.code = 1)\n\n Facts: A criminal defendant appeals his conviction, arguing that evidence was obtained\n through an unlawful search. The Court of Appeals affirms, holding the search was lawful.\n\n Coding:\n issue_area.code = 1 (Criminal Procedure)\n winning_party.code = 0 (no favorable disposition for petitioner)\n decision_direction = 1 (conservative) ← prosecution/government benefited; lookup table\n row for code 1 says \"prosecution → 1 (conservative)\"\n\n\nEXAMPLE C — Economic Activity (issue_area.code = 8)\n\n Facts: A chemical company challenges an EPA water-quality regulation. The Court of Appeals\n affirms, upholding the regulation as within the agency's statutory authority.\n\n Coding:\n issue_area.code = 8 (Economic Activity)\n winning_party.code = 0 (no favorable disposition for petitioner/company)\n decision_direction = 2 (liberal) ← government regulation upheld against business;\n lookup table row for code 8 says \"govt regulation → 2 (liberal)\"\n\n NOTE: Even if one might view upholding a regulation as a \"pro-business\" outcome (e.g., it\n creates regulatory certainty), the SCDB mechanically codes government regulation prevailing\n over a business challenge as liberal (2).\n\n\n3.6.2 Internal Consistency Check\n\nBefore you output the JSON, you MUST run the following consistency check:\n\n1. Identify issue_area.code.\n2. Identify which side won in the case (petitioner vs respondent) and what kind of party they are.\n3. Look up the corresponding row in the DIRECTION LOOKUP TABLE above.\n4. Verify that your decision_direction.code matches the table entry.\n5. If it does not match, CORRECT decision_direction.code to match the table.\n\n\n3.7 Lower Court Direction\n\nCodes:\n\n1 = conservative\n2 = liberal\n3 = unspecifiable\n\nUse the same DIRECTION LOOKUP TABLE as for Decision Direction (see Section 3.6), but applied to\nthe **lower court's outcome**. You MUST determine the lower court's direction by comparing the lower\ncourt's judgment and the appellate court's disposition.\n\nUse this rule of thumb:\n\n1. First, identify the appellate disposition (case_disposition.code).\n2. Next, identify the decision_direction.code for the Court of Appeals.\n3. Last, infer who benefited in the lower court and assign lower_court_direction as follows:\n\n- If the Court of Appeals clearly **leaves the lower court judgment in place** (e.g., case_disposition.code = 1 \"affirmed\"\n or 8 \"petition denied or appeal dismissed\"), then the lower court's direction is the SAME as decision_direction.code.\n\n- If the Court of Appeals clearly **undoes the lower court judgment** (e.g., case_disposition.code = 2 \"reversed\",\n 3 \"reversed and remanded\", 4 \"vacated and remanded\", or 7 \"vacated\"), then the lower court's direction is the\n OPPOSITE of decision_direction.code.\n\n- For mixed outcomes (case_disposition.code = 5 or 6), compare who won more in the lower court vs on appeal:\n * If, on balance, the petitioner is better off after the appeal than under the lower court judgment, then\n the lower court's direction should usually be the OPPOSITE of decision_direction.code.\n * If, on balance, the petitioner is worse off or no better off than under the lower court judgment, then\n the lower court's direction should usually be the SAME as decision_direction.code.\n * If you cannot determine who benefited more from the lower court judgment even approximately, use 3 (unspecifiable).\n\n- For stays, motions, certifications, or purely procedural dispositions (codes 9, 10, 0), infer who benefited in\n the lower court if possible; if not, use 3 (unspecifiable).\n\nWhen you set lower_court_direction, remember:\n- \"SAME\" means lower_court_direction.code = decision_direction.code.\n- \"OPPOSITE\" means: if decision_direction.code = 1 (conservative), then lower_court_direction.code = 2 (liberal);\n if decision_direction.code = 2 (liberal), then lower_court_direction.code = 1 (conservative).\n\n3.8 Declaration of Unconstitutionality\n\nCodes:\n\n0 = the court did NOT strike down any statute, regulation, or government action as unconstitutional\n1 = the court DID declare a statute, regulation, or government action unconstitutional\n\nCode 1 if the court holds that a law, regulation, executive action, or government practice violates\nthe Constitution (whether facial or as-applied). This includes striking down acts of Congress, federal\nregulations, state statutes, state constitutional provisions, and local ordinances.\n\nDo NOT code 1 merely because the court discusses constitutional issues. The court must actually\nhold that something is unconstitutional. If the court upholds the constitutionality of the\nchallenged provision, code 0.\n\n\n3.9 Method\n\nCodes:\n\n1 = standard panel decision (typically 3 judges, first hearing)\n2 = panel rehearing (same panel reconsidering its prior decision)\n3 = en banc (full court or en banc panel rehearing a case)\n4 = per curiam (unsigned opinion — may overlap with codes 1 or 3)\n\nUse the opinion text, metadata, and case caption to determine the method. Look for explicit\nstatements like \"before the court en banc,\" \"on rehearing,\" \"upon reconsideration,\" or\n\"per curiam.\" If the metadata indicates more than 3 judges participated, this strongly\nsuggests en banc (code 3). If none of these indicators are present, use 1 (standard panel).\n\n\n3.10 Who Appealed\n\nCodes:\n\n1 = original plaintiff (or the equivalent, e.g. the Title VII complainant, habeas petitioner)\n2 = original defendant (or the equivalent, e.g. the employer in a Title VII suit)\n3 = federal government on behalf of the original plaintiff\n4 = federal government on behalf of the original defendant\n\nDetermine who initiated the appeal by examining the case caption, opinion text, and procedural\nhistory. The \"original plaintiff\" is the party who filed suit in the lower court; the \"original\ndefendant\" is the party who was sued. In criminal cases, the original plaintiff is typically the\ngovernment (prosecution) and the original defendant is the accused.\n\nIf the opinion describes a cross-appeal, code based on who filed the PRIMARY appeal (the one\nthe court addresses as the main appeal). If you cannot determine who appealed, use 1 as default\nfor criminal defendants (who are most commonly appellants) or your best judgment from the caption\nordering (appellant is typically listed first).\n\n\n3.11 Dissent/Concurrence Basis (Conditional)\n\nIf the case metadata states \"Has dissenting opinion: Yes\" or \"Has concurring opinion: Yes\",\ncode whether that separate opinion addresses procedural issues, merits issues, or both.\n\nFor each dimension (procedural / merits), use one of these codes:\n\n0 = the dissent/concurrence exists but does NOT address this type of issue\n1 = addresses the SAME issue as the majority and DISAGREES with the majority's resolution\n2 = addresses the SAME issue as the majority and AGREES with the majority's resolution\n3 = addresses an issue NOT discussed by the majority opinion\n\n\"dissent_basis\" (include ONLY if \"Has dissenting opinion: Yes\"):\n - \"procedural\": Does the dissent address procedural questions (jurisdiction, standing,\n standard of review, procedural default, timeliness, etc.)?\n - \"merits\": Does the dissent address the substantive legal merits (statutory interpretation,\n constitutional analysis, factual sufficiency, etc.)?\n\n\"concurrence_basis\" (include ONLY if \"Has concurring opinion: Yes\"):\n - \"procedural\": Does the concurrence address procedural questions?\n - \"merits\": Does the concurrence address the substantive legal merits?\n\nIf multiple dissenting or concurring opinions exist, code based on the PRIMARY one\n(the longest or most substantive).\n\nIf the metadata says \"Has dissenting opinion: No\", OMIT \"dissent_basis\" entirely from your output.\nIf the metadata says \"Has concurring opinion: No\", OMIT \"concurrence_type\" and \"concurrence_basis\" entirely from your output.\n\n\n3.12 Concurrence Type (Conditional)\n\nIf the case metadata states \"Has concurring opinion: Yes\", classify the concurrence as one of\nthe following types:\n\nCodes:\n\n1 = regular concurrence — the concurring judge JOINED the majority opinion AND wrote or joined\n a separate concurrence to add additional reasoning, emphasize a point, or note a limitation.\n The key indicator: the judge agrees with BOTH the outcome AND the reasoning of the majority.\n\n2 = special concurrence / concurrence in result only — the concurring judge agrees with the\n OUTCOME (disposition) but does NOT join the majority opinion's reasoning. Look for language\n like \"concurring in the result,\" \"concurring in the judgment,\" \"concurring in the result\n only,\" or \"I concur in the judgment but write separately because I disagree with the\n majority's analysis.\" The key indicator: the judge explicitly declines to join the majority\n opinion or distances themselves from the majority's reasoning.\n\n3 = cannot determine — the opinion text does not make clear whether the concurring judge joined\n the majority opinion or only the result.\n\nThis distinction matters because special concurrences (code 2) signal reasoning disagreement\nwithin a nominally unanimous disposition. A case where all judges agree on the outcome but one\nwrites a special concurrence is qualitatively different from one where all judges agree on\nboth outcome and reasoning.\n\nIf multiple concurring opinions exist, code based on the PRIMARY concurrence (the longest or\nmost substantive). If one is a regular concurrence and another is a special concurrence,\ncode based on the special concurrence (code 2), as it is more analytically informative.\n\n\n==================================================\n4. GENERAL RULES\n==================================================\n\n- Use metadata (case name, court, date, opinion type) to:\n - distinguish main merits opinions from rehearing or procedural opinions,\n - interpret how the appellate disposition relates to the prior judgment,\n - infer whether the case is criminal, civil rights, tax, etc.\n- If some information is missing, use the appropriate \"unspecifiable\" or \"no disposition\" code\n (e.g., 3 for direction, 11 for case_disposition); do not invent facts.\n- Carefully follow the steps laid out in the introduction in order. In particular,\n decide who won the case (winning_party). Then, decide what the issue_area is.\n Only choose decision_direction once you have completed those steps, and follow the exact\n directions in Section 3.6.\n- In the justification, explicitly state who won, why (according to the disposition), and\n how that winner and the issue_area code together implied the direction code you chose.\n Reference the DIRECTION LOOKUP TABLE row you applied.\n- ALWAYS choose exactly one code for each coded variable where required.\n- NEVER output any keys other than the ones defined in the schema above.\n- Include \"dissent_basis\", \"concurrence_type\", and \"concurrence_basis\" ONLY when the metadata\n indicates the corresponding opinion type exists. Omit them entirely otherwise.\n- NEVER output any numeric codes outside the permitted lists above.\n\n\n==================================================\n5. FINAL REQUIREMENT\n==================================================\n\nAfter reading [CASE_METADATA] and [CASE_TEXT], respond ONLY with the JSON object in the schema\nabove. Do not include any extra commentary, markdown, or explanation outside the JSON.\n", "role": "system" }, { "content": "[CASE_METADATA]\nCase name: UNITED STATES of America, Plaintiff - Appellee, v. Johnny Sylvester EDGELL, Defendant - Appellant.\nCourt: U.S. Court of Appeals for the Fourth Circuit\nDate decided: 2019-01-25\nOpinion type: majority\nHas dissenting opinion: No\nHas concurring opinion: No\nAdditional notes: \n\n[CASE_TEXT]\nPUBLISHED\n\n UNITED STATES COURT OF APPEALS\n FOR THE FOURTH CIRCUIT\n\n\n No. 17-4432\n\n\nUNITED STATES OF AMERICA,\n\n Plaintiff - Appellee,\n\n v.\n\nJOHNNY SYLVESTER EDGELL,\n\n Defendant - Appellant.\n\n\nAppeal from the United States District Court for Northern District of West Virginia, at\nClarksburg. Irene M. Keeley, Senior District Judge. (1:16-cr-00045-IMK-MJA-1)\n\n\nArgued: November 1, 2018 Decided: January 25, 2019\n\n\nBefore GREGORY, Chief Judge, NIEMEYER and HARRIS, Circuit Judges.\n\n\nSentence vacated and case remanded by published opinion. Judge Harris wrote the\nopinion, in which Chief Judge Gregory and Judge Niemeyer joined.\n\n\nARGUED: Linn Richard Walker, OFFICE OF THE FEDERAL PUBLIC DEFENDER,\nClarksburg, West Virginia, for Appellant. Stephen Donald Warner, OFFICE OF THE\nUNITED STATES ATTORNEY, Elkins, West Virginia, for Appellee. ON BRIEF:\nKristen M. Leddy, Research and Writing Specialist, OFFICE OF THE FEDERAL\nPUBLIC DEFENDER, Clarksburg, West Virginia, for Appellant. William J. Powell,\nUnited States Attorney, OFFICE OF THE UNITED STATES ATTORNEY, Wheeling,\nWest Virginia, for Appellee.\n\fPAMELA HARRIS, Circuit Judge:\n\n After negotiating a plea agreement with the government, Johnny Sylvester Edgell\n\npleaded guilty to one count of possessing a firearm as an unlawful drug user and one count\n\nof distributing methamphetamine. In exchange for that plea, the government agreed to a\n\nstipulation limiting Edgell’s total drug conduct to “less than five (5) grams of substances\n\ncontaining a detectable amount of methamphetamine,” J.A. 193, which corresponded to an\n\nadvisory sentencing range of 10 to 16 months’ imprisonment. But after the agreement was\n\nsigned, the government received lab results showing that the substances in question were\n\nactual methamphetamine, and once the government shared that information with the\n\nprobation office, Edgell’s sentencing range increased to 30 to 37 months. At sentencing,\n\nthe government advocated for a sentence consistent with that elevated range, and Edgell\n\nwas sentenced to 30 months in prison.\n\n Edgell contends that the government breached his plea agreement in two respects:\n\nfirst, by disclosing the post-plea lab report to the probation office and sentencing court; and\n\nsecond, by failing to honor the agreement at sentencing, and instead advocating for a\n\nsentence inconsistent with its original stipulation. We cannot agree that the government\n\nbreached its plea agreement by disclosing relevant and accurate information to the\n\nsentencing court. But we agree with Edgell that the government’s conduct at the sentencing\n\nhearing denied him the benefit of his bargain. Given the government’s breach, we vacate\n\nEdgell’s sentence and remand for resentencing before a different district judge.\n\n\n\n I.\n\n 2\n\f Following three controlled buys in July 2015, Johnny Sylvester Edgell was indicted\n\nby a federal grand jury on three counts of distributing methamphetamine, in violation of\n\n21 U.S.C. §§ 841(a)(1) and 841(b)(1)(C), and one count of unlawfully possessing a firearm,\n\nin violation of 18 U.S.C. §§ 922(g)(3) and 924(a)(2).\n\n Edgell and the government negotiated a plea agreement. For his part, Edgell agreed\n\nto plead guilty to the single firearm charge and to one count of distributing\n\nmethamphetamine. In exchange, the government agreed to a stipulation that Edgell’s drug\n\nconduct involved “less than five (5) grams of substances containing a detectable amount\n\nof methamphetamine” – that is, substances of a lower purity level than actual\n\nmethamphetamine. J.A. 193. Pursuant to that stipulation, Edgell’s advisory sentencing\n\nrange would be 10 to 16 months’ imprisonment. 1 The government additionally agreed to\n\n“recommend that any sentence of incarceration imposed . . . be at the lowest end of the\n\napplicable guideline range,” J.A. 193, and to dismiss the remaining counts of the\n\nindictment.\n\n The plea agreement also contained certain reservations. First, it specified that the\n\nsentencing court was not bound by the parties’ stipulations and was not required to accept\n\n\n\n 1\n While the plea agreement did not specify the resulting sentencing range, the parties\ndo not dispute that the agreement contemplated a range of 10 to 16 months’ imprisonment.\nThe agreement’s drug conduct stipulation produces a base offense level of 12. See\nU.S.S.G. § 2D1.1(c)(14). Considering the relevant adjustments – including a two-level\nenhancement for his possession of a dangerous weapon and a two-level reduction for\nacceptance of responsibility, see U.S.S.G. §§ 2D1.1(b)(1), 3E1.1 – and Edgell’s Category\nI criminal history, Edgell’s advisory sentencing range under the agreement indeed would\nhave been 10 to 16 months. See U.S.S.G. ch. 5, pt. A (sentencing table).\n\n\n 3\n\fthem. The agreement also reserved the government’s “right to provide to the Court and\n\nthe United States Probation Office . . . relevant information including defendant’s\n\nbackground, criminal record, offense charged in the indictment and other pertinent data . .\n\n. as will enable the Court to exercise its sentencing discretion,” and “to respond to any\n\nquestions raised by the Court, to correct any inaccuracies or inadequacies in the anticipated\n\npre-sentence report, and to respond to any written or oral statements made by the Court, by\n\ndefendant or his counsel.” J.A. 194.\n\n At the time the government entered into its agreement with Edgell, it had requested,\n\nbut not yet received, a laboratory analysis of the substances distributed by Edgell. When\n\nthat laboratory report was returned to the government – only after the agreement was\n\nfinalized – it revealed that the substances in question were not merely “substances\n\ncontaining a detectable amount of methamphetamine,” as the parties had stipulated, J.A.\n\n193, but instead actual methamphetamine. The government disclosed that information to\n\nthe probation office, which incorporated it into its Presentence Report (PSR), attributing\n\n3.5344 grams of actual methamphetamine to Edgell. As a result, the PSR calculated\n\nEdgell’s guidelines sentencing range as 30 to 37 months’ imprisonment, rather than the 10\n\nto 16 months anticipated under the plea agreement. 2 In light of that discrepancy, the PSR\n\nsuggested that a downward variance might be appropriate.\n\n\n\n\n 2\n Edgell’s new drug conduct resulted in an offense level of 20. See U.S.S.G. §\n2D1.1(c)(10). Edgell received a two-level enhancement for possessing a dangerous\nweapon under U.S.S.G. § 2D1.1(b)(1) and a three-level reduction for acceptance of\nresponsibility under U.S.S.G. § 3E1.1(b), for a total offense level of 19. Combined with\n(Continued)\n 4\n\f At sentencing, the district court acknowledged that the PSR’s factual findings and\n\nsentencing calculations were “certainly different from . . . the parties’ expectation from the\n\nplea agreement.” J.A. 91. Nevertheless, and without objection from either party, the court\n\nadopted the PSR’s advisory guidelines range of 30 to 37 months.\n\n Consistent with the PSR’s suggestion, Edgell requested a downward variance. The\n\ngovernment did not join Edgell’s request. Nor did it recommend a sentence consistent with\n\nthe agreed-upon stipulation as to drug conduct and the corresponding 10 to 16 months\n\nsentencing range. Instead, purporting to follow its commitments under the plea agreement,\n\nthe government advocated for a sentence at the “low end” of the guidelines range adopted\n\nby the court, or 30 months’ imprisonment. J.A. 108. The court followed the government’s\n\nrecommendation and sentenced Edgell to 30 months’ imprisonment, to be followed by a\n\nterm of three years of supervised release. Edgell timely appealed.\n\n\n\n II.\n\n Edgell contends the government breached its plea agreement by disclosing the post-\n\nagreement lab results to the probation office and the sentencing court, and by failing at\n\nsentencing to honor the agreement’s explicit drug conduct stipulation – that he was\n\nresponsible for distributing “less than five (5) grams of substances containing a detectable\n\namount of methamphetamine,” J.A. 193. Because Edgell did not challenge the\n\n\n\n\nhis Category I criminal history, the resulting sentencing range was 30 to 37 months’\nimprisonment. See U.S.S.G. ch. 5, pt. A (sentencing table).\n\n 5\n\fgovernment’s purported breach of the plea agreement before the district court, we review\n\nhis claim for plain error. United States v. Tate, 845 F.3d 571, 575 (4th Cir. 2017) (citing\n\nFed. R. Crim. P. 52(b)). Under that standard, Edgell must show that the government plainly\n\nbreached its plea agreement with him and that the breach both affected his substantial rights\n\nand called into question the fairness, integrity, or public reputation of judicial proceedings.\n\nSee United States v. Dawson, 587 F.3d 640, 645 (4th Cir. 2009). For the reasons given\n\nbelow, we find that Edgell has satisfied that demanding standard.\n\n A.\n\n We first consider whether the government breached the clear requirements of its\n\nplea agreement with Edgell. “Plea agreements are grounded in contract law,” and as with\n\nany contract, each party is entitled to receive the benefit of his bargain. Tate, 845 F.3d at\n\n575. While “we employ traditional principles of contract law as a guide” in enforcing plea\n\nagreements, “we nonetheless give plea agreements greater scrutiny than we would apply\n\nto a commercial contract because a defendant’s fundamental and constitutional rights are\n\nimplicated when he is induced to plead guilty by reason of a plea agreement.” United\n\nStates v. Warner, 820 F.3d 678, 683 (4th Cir. 2016) (internal quotation marks and brackets\n\nomitted). At a minimum, “when a plea rests in any significant degree on a promise or\n\nagreement of the prosecutor, so that it can be said to be part of the inducement or\n\nconsideration, such promise must be fulfilled.” Santobello v. New York, 404 U.S. 257, 262\n\n(1971).\n\n Here, Edgell maintains that his plea agreement rested on the government’s promise\n\nto limit his relevant drug conduct to “less than five (5) grams of substances containing a\n\n 6\n\fdetectable amount of methamphetamine,” J.A. 193, and the associated sentencing range,\n\nand that he was denied the benefit of his bargain when the government breached that\n\npromise. Specifically, Edgell challenges both the government’s disclosure of the post-\n\nagreement lab results to the probation office and sentencing court, and the government’s\n\nfailure at sentencing to defend or advocate in any way for the parties’ drug conduct\n\nstipulation. We address each of these challenges in turn.\n\n To the extent Edgell contends that the government breached its plea agreement by\n\ndisclosing lab results to the probation office and court, we must disagree. The government\n\nhas a “duty to furnish complete and accurate information at sentencing,” and we have\n\nexpressed doubt as to whether a plea agreement may abridge that duty. United States v.\n\nCrisp, 817 F.2d 256, 259 (4th Cir. 1987). Other courts of appeals, too, have emphasized\n\nthat even where a plea agreement binds the government to certain sentencing\n\nrecommendations, the government retains a duty “to ensure that the court has complete and\n\naccurate information, enabling the court to impose an appropriate sentence.” United States\n\nv. Maldonado, 215 F.3d 1046, 1052 (9th Cir. 2000); see also United States v. Casillas, 853\n\nF.3d 215, 218 (5th Cir. 2017) (government may not “stand mute in the face of factual\n\ninaccuracies or [] withhold relevant factual information from the court” (internal quotation\n\nmarks omitted)); United States v. Ubiles-Rosario, 867 F.3d 277, 283 (1st Cir. 2017) (“[A]\n\nplea agreement may not abridge the [government’s] solemn obligation to provide relevant\n\ninformation to the sentencing court.” (internal quotation marks omitted)).\n\n Indeed, consistent with this understanding, Edgell’s plea agreement does not purport\n\nto limit or override the government’s duty of candor to the court. Instead, it recognizes\n\n 7\n\fthat duty, and expressly reserves the government’s “right to provide to the Court and the\n\nUnited States Probation Office . . . relevant information including defendant’s background,\n\ncriminal record, offense charged in the indictment and other pertinent data . . . as will enable\n\nthe Court to exercise its sentencing discretion.” J.A. 194. The government’s disclosure of\n\nthe lab results, which went directly to the offense charged in the indictment and to Edgell’s\n\nbase offense calculation, was thus consistent with both the parties’ plea agreement and the\n\ngovernment’s broader duty to provide complete and accurate information to the sentencing\n\ncourt.\n\n But the government did more than that here. And we agree with Edgell that the\n\ngovernment crossed the line and breached its plea agreement when it failed at sentencing\n\nto honor its drug conduct stipulation. As one court of appeals to consider this precise\n\nquestion has explained, “Although the Government has a duty to provide the sentencing\n\ncourt with relevant factual information and to correct misstatements, it may not hide behind\n\nthis duty to advocate a position that contradicts its promises in a plea agreement.” United\n\nStates v. Munoz, 408 F.3d 222, 227 (5th Cir. 2005). Instead, the government must carefully\n\nbalance its duty of candor to the sentencing court with the sometimes competing – but\n\nequally solemn – duty to honor its commitments under a plea agreement. See United States\n\nv. Saxena, 229 F.3d 1, 5 (1st Cir. 2000). And as courts that have addressed the question\n\nagree, this balance is achieved where the government makes the necessary disclosures to\n\nthe sentencing court, but nevertheless “continue[s] to advocate for acceptance of the\n\nagreement.” Casillas, 853 F.3d at 218; see also United States v. Franco–Lopez, 312 F.3d\n\n984, 993 (9th Cir. 2002) (“We conclude that the government did not breach the plea\n\n 8\n\fagreement by providing information to the Probation Department regarding [the\n\ndefendant’s] criminal activity while recommending successfully to the district court that it\n\nnot rely on that information in sentencing.”); Saxena, 229 F.3d at 7 (finding no breach\n\nwhere the government disclosed information inconsistent with the plea agreement, but\n\nnevertheless “resolutely stood by the bottom-line recommendation that [it] had committed\n\nto make”).\n\n The government failed to strike the necessary balance here. At sentencing, the\n\ngovernment did not “continue to advocate for acceptance,” Casillas, 853 F.3d at 218, of its\n\nagreement with Edgell. It did not ask the court to impose a sentence consistent with the 10\n\nto 16 months range that corresponded to its drug conduct stipulation. It did not join in\n\nEdgell’s request for a downward variance. And it did not otherwise encourage the court to\n\nconsider in any way the factual stipulation to which it agreed in exchange for Edgell’s\n\nguilty plea. Instead, the government affirmatively undermined the plea agreement by\n\nrequesting a sentence inconsistent with its stipulation, effectively tripling its recommended\n\nsentence from the 10 months anticipated under the plea agreement to the 30 months at the\n\nlow end of the post-lab report range calculated by the PSR. 3\n\n\n 3\n We appreciate the awkward situation the government faced at sentencing;\nbalancing the competing duties of candor to the court and adherence to a plea agreement\ncan be a difficult task under circumstances like these. But this is not the first case in which\na prosecutor was required to walk that line. In United States v. Saxena, 229 F.3d 1, 4 (1st\nCir. 2000), for instance, the government had agreed in a plea agreement to recommend a\nsentence of 24 months’ imprisonment, consistent with an anticipated sentencing range of\n24 to 30 months. At sentencing, however, it disclosed to the court post-plea activities by\nthe defendant that led the court to adopt a higher guidelines range of 33 to 41 months. Id.\nat 4–5. But when it came time to make a sentencing recommendation, the prosecutor\n(Continued)\n 9\n\f At oral argument, the government suggested for the first time that its sentencing\n\nrecommendation did not breach the plea agreement because Edgell “assumed the risk” that\n\nit would discover the actual nature of the substances he distributed. But it was the\n\ngovernment, of course, that knew of an outstanding lab report and nevertheless decided to\n\ngo forward with the plea agreement without waiting for the results, thus assuming precisely\n\nthe risk that materialized: that the lab report ultimately would come back with information\n\ninconsistent with the agreement’s drug conduct stipulation. The government’s apparent\n\nmisjudgment about the importance of the lab report is not grounds for relieving the\n\ngovernment of its obligations under the plea agreement.\n\n Moreover, the government’s assumption-of-risk argument misconstrues the very\n\nnature of plea agreements. Plea agreements, as any contract, bind one party to do\n\nsomething the other party desires in exchange for some benefit. United States v. Bownes,\n\n405 F.3d 634, 636 (7th Cir. 2005). Here, the government agreed to the drug conduct\n\nstipulation, which came with a corresponding sentencing range of 10 to 16 months, and to\n\n\ncontinued to advocate for the 24 months to which the parties had agreed, explaining to the\ncourt:\n\n The government’s recommendation in this case is pursuant to our plea\n agreement. And I’m well aware, your Honor, of the fact that my\n recommendation is below what the Court has determined the guidelines\n applicable to be. Nonetheless, bound by that agreement the government does\n recommend a sentence of 24 months which, of course, was based on the\n calculations [of] the parties.\n\nId. at 7. Because it “resolutely stood by” a sentencing recommendation consistent with its\nplea agreement, the First Circuit concluded in Saxena, the government had not breached\nthe agreement, notwithstanding its disclosure of post-plea information to the court. Id. at\n7–8.\n\n 10\n\frecommend a sentence at the bottom of the applicable range. In return, Edgell relieved the\n\ngovernment of its burden to prove his guilt beyond a reasonable doubt and eliminated the\n\nneed for the government to expend its resources on a full criminal trial. Both parties bound\n\nthemselves to their respective commitments, and each “assume[d] the risk of future\n\nchanges in circumstances in light of which [their] bargain may prove to have been a bad\n\none.” Id. Just as we often enforce plea agreements against criminal defendants even in the\n\nface of subsequent, favorable changes in the law, see, e.g., United States v. Archie, 771\n\nF.3d 217, 222 (4th Cir. 2014), so, too, must we enforce plea agreements that may later\n\nprove less advantageous than the government had anticipated.\n\n The government’s failure at sentencing to stand by its drug conduct stipulation, and\n\nits recommendation of a sentence inconsistent with that stipulation, denied Edgell a central\n\nbenefit of his bargain. It follows that the government breached its plea agreement with\n\nEdgell. See Santobello, 404 U.S. at 262. And because the government’s duties pursuant\n\nto the plea agreement were sufficiently clear – that is, the drug conduct stipulation was\n\nunambiguous – that error was plain. Cf. Puckett v. United States, 556 U.S. 129, 143 (2009)\n\n(“Not all breaches [of plea agreements] will be clear or obvious. Plea agreements are not\n\nalways models of draftsmanship, so the scope of the Government’s commitments will on\n\noccasion be open to doubt.”). Edgell therefore satisfies the initial requirements of plain\n\nerror review.\n\n B.\n\n Having found that the government plainly breached its plea agreement at\n\nsentencing, we next consider whether that breach affected Edgell’s substantial rights. A\n\n 11\n\fbreach of a plea agreement affects a defendant’s substantial rights only if it prejudices the\n\ndefendant. Puckett, 556 U.S. at 135. And a defendant suffers no prejudice where (1) he\n\nobtained the benefits of the plea agreement despite the government’s breach – that is, where\n\nhe nevertheless received the sentence the prosecutor promised to request – or (2) “he likely\n\nwould not have obtained those benefits in any event.” Id. at 141–42. Where the record\n\ndoes not reflect either of the above circumstances, “we are free to conclude that the\n\ndefendant has shown a reasonable probability, based on the appellate record as a whole,\n\nthat but for the error he would have received a more favorable sentence.” Dawson, 587\n\nF.3d at 645 (internal quotation marks omitted).\n\n Edgell has made the requisite showing of potential prejudice. First, there is no\n\nquestion that Edgell did not receive the benefit of his bargain: He was sentenced to 30\n\nmonths’ imprisonment, a sentence that far exceeded the sentencing range that would have\n\nresulted from the drug conduct stipulation in the parties’ plea agreement. Second, we\n\ncannot conclude from this record that, had the government honored the plea agreement,\n\nthere would have been no benefit to Edgell. It is true that, under the plea agreement, the\n\nsentencing court was not bound by the parties’ stipulation, 4 and the court did voice a\n\n\n\n\n 4\n That the court was not bound by the drug conduct stipulation, of course, does not\nexcuse the government from its commitments under the agreement. The parties “did intend\nfor the stipulation to bind the government, and it is the government’s breach of that\nagreement that is the focus of our inquiry.” United States v. Boatner, 966 F.2d 1575, 1579\n(11th Cir. 1992); see also United States v. Normil, 129 F.3d 1261, at *4 (4th Cir. 1997)\n(unpublished table decision) (“To the extent that a stipulation entered by the government\nis essential to the defendant’s bargain, it is binding. This is true even if the court is not\nbound by the stipulation.” (citation omitted)).\n\n 12\n\fconcern that the plea agreement – and the sentencing range it contemplated – did not\n\naccount for the severity of Edgell’s offenses. But at the same time, the district court made\n\nclear that it was considering a sentence well below the 30 to 37 months range it had\n\nadopted. And in the end, it adopted precisely the sentence the government recommended:\n\n30 months. Had the government instead urged the court to impose a sentence consistent\n\nwith its plea agreement, or joined in Edgell’s request for a downward variance, then the\n\ncourt may well have taken the government’s position into account and arrived at a sentence\n\nwithin, or at least closer to, the sentencing range anticipated by the plea agreement. Edgell\n\nthus has “demonstrated a reasonable probability that the outcome of his sentencing would\n\nhave been different had the government made the appropriate recommendation.” Dawson,\n\n587 F.3d at 646; cf. United States v. Navarro, 817 F.3d 494, 501 (7th Cir. 2016) (“[C]ases\n\nwhere we have found that the defendant failed to prove the prejudice prong are ones in\n\nwhich the record compellingly reflects the sentencing court was not influenced by the\n\ngovernment’s recommendation.”). Accordingly, we find that the government’s breach of\n\nthe plea agreement affected Edgell’s substantial rights.\n\n C.\n\n We similarly find that the government’s breach of the plea agreement seriously\n\naffected the “fairness, integrity, or public reputation of judicial proceedings,” Puckett, 556\n\nU.S. at 135 (internal quotation marks omitted). The Supreme Court has cautioned that this\n\nprong of plain error “is meant to be applied on a case-specific and fact-intensive basis,”\n\nand is not automatically satisfied whenever the government breaches a plea agreement. Id.\n\nat 142–43. “Nevertheless, . . . courts have recognized that the Government’s breach of a\n\n 13\n\fplea agreement constitutes a particularly egregious error that, in the absence of strong\n\ncountervailing factors, seriously affects the fairness, integrity, or public reputation of\n\njudicial proceedings.” United States v. Kirkland, 851 F.3d 499, 505 (5th Cir. 2017)\n\n(emphasis added) (collecting cases). This is so because “[t]he breach of a promise made\n\nto induce a defendant to enter a guilty plea – and thereby waive important constitutional\n\nrights – harms not only the defendant, but . . . involves the honor of the government, [and]\n\npublic confidence in the fair administration of justice.” United States v. Lewis, 633 F.3d\n\n262, 269 (4th Cir. 2011) (internal quotation marks omitted); see also United States v.\n\nPeglera, 33 F.3d 412, 414 (4th Cir. 1994) (“Because a government that lives up to its\n\ncommitments is the essence of liberty under law, the harm generated by allowing the\n\ngovernment to forego its plea bargain obligations is one which cannot be tolerated.”).\n\n Here, the government does not contest that its purported breach affects the integrity,\n\nfairness, or public reputation of plea agreements and judicial proceedings generally.\n\nAccordingly, because Edgell has shown the government failed to honor its clear\n\ncommitments under his plea agreement and the government fails to provide even a single\n\ncountervailing factor, we find Edgell has satisfied the final requirement of plain error\n\nreview.\n\n\n\n III.\n\n Having found that the government breached the plea agreement and that the breach\n\nconstitutes plain and reversible error, the only remaining issue is the appropriate remedy.\n\n“In most cases in which the Government has breached its agreement with the defendant,\n\n 14\n\fwe prefer to leave the fashioning of appropriate relief to the sound discretion of the district\n\ncourt.” United States v. Wood, 378 F.3d 342, 350 n.6 (4th Cir. 2004) (internal quotation\n\nmarks omitted). Where, however, the defendant does not seek to withdraw his guilty plea\n\nand instead requests only “the lesser relief of specific performance of the agreement[,] . . .\n\nthen the court should honor that election,” and “remand with the direction that the\n\ndefendant ‘be resentenced by a different judge.’” Warner, 820 F.3d at 685 (quoting\n\nSantobello, 404 U.S. at 263). 5\n\n Because Edgell seeks only specific performance, we will honor his election.\n\n\n\n IV.\n\n For the foregoing reasons, we find the government breached its plea agreement with\n\nEdgell and that this breach constitutes reversible plain error. We do not doubt that the\n\ngovernment’s breach was the result of inadvertence rather than bad faith, but Edgell\n\nnonetheless was denied the benefit of his bargain. Accordingly, we vacate Edgell’s\n\nsentence and remand the case for resentencing before a different district judge.\n\n\n\n SENTENCE VACATED AND CASE REMANDED\n\n\n\n 5\n When specific performance is elected by a defendant, resentencing always takes\nplace before a different judge. See Peglera, 33 F.3d at 415 (“We remand the case to a\ndifferent district judge for resentencing as we are required to do.”) As the Supreme Court\nhas emphasized, that standard remedy “is in no sense to question the fairness of the\nsentencing judge,” Santobello, 404 U.S. at 263, and our decision today should not be\nunderstood as a “reflection on [Edgell’s] trial judge, who handled the case admirably under\nthe circumstances,” Peglera, 33 F.3d at 415.\n\n 15\n[END_CASE]", "role": "user" } ]